Microsoft-Windows-RasRoutingProtocols-BGP

52 events across 3 channels

Event IDTitleChannel
1Operational
1BGP peering manually started for peer %1.Operational
2Operational
2BGP peering manually started for peer %1 of routing domain %2.Operational
3Operational
3BGP peering manually stopped for peer %1.Operational
4Operational
4BGP peering manually stopped for peer %1 of routing domain %2.Operational
5Operational
5BGP peering established for peer %1.Operational
6Operational
6BGP peering established for peer %1 of routing domain %2.Operational
7Operational
7BGP peering session disconnected for peer %1 : %2.Operational
8Operational
8BGP peering session disconnected for peer %1 of routing domain %2 : %3.Operational
9Operational
9BGP peering state changed to %1 for peer %2.Debug
10Operational
10BGP peering state changed to %1 for peer %2 of routing domain %3.Debug
11Operational
11Maximum prefix limit reached for peer %1.Operational
12Operational
12Maximum prefix limit reached for peer %1 of routing domain %2.Operational
13Operational
13BGP peering attempt failed for peer %1 : %2.Operational
14Operational
14BGP peering attempt failed for peer %1 of routing domain %2 : %3.Operational
15Operational
15BGP peering collision detected for peer %1.Operational
16Operational
16BGP peering collision detected for peer %1 of routing domain %2.Operational
17Operational
17HoldTime set to %1 sec for peer %2.Operational
18Operational
18HoldTime set to %1 sec for peer %2 of routing domain %3.Operational
19Operational
19TCP connection attempt failed for BGP peer %1.Debug
20Operational
20TCP connection attempt failed for BGP peer %1 of routing domain %2.Debug
21Operational
21Cannot resolve next-hop %1 for destination %2, learned from peer %3.Debug
22Operational
22Cannot resolve next-hop %1 for destination %2, learned from peer %3 of routing …Debug
23Operational
23Routes to %1, learned from peer %2 were discarded because of ingress routing …Debug
24Operational
24Routes to %1, learned from peer %2 of routing domain %3 were discarded because …Debug
25Operational
25Routes to %1, were suppressed from advertisement to peer %2 because of egress …Debug
26Operational
26Routes to %1, were suppressed from advertisement to peer %2 of routing domain %3 …Debug

Event ID 1 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 1 — BGP peering manually started for peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering manually started for peer %1.

Fields

NameDescription
Arg1

Event ID 2 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 2 — BGP peering manually started for peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering manually started for peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 3 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 3 — BGP peering manually stopped for peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering manually stopped for peer %1.

Fields

NameDescription
Arg1

Event ID 4 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 4 — BGP peering manually stopped for peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering manually stopped for peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 5 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 5 — BGP peering established for peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering established for peer %1.

Fields

NameDescription
Arg1

Event ID 6 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 6 — BGP peering established for peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering established for peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 7 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 7 — BGP peering session disconnected for peer %1 : %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering session disconnected for peer %1 : %2.

Fields

NameDescription
Arg1
Arg2

Event ID 8 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 8 — BGP peering session disconnected for peer %1 of routing domain %2 : %3.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering session disconnected for peer %1 of routing domain %2 : %3.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 9 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 9 — BGP peering state changed to %1 for peer %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

BGP peering state changed to %1 for peer %2.

Fields

NameDescription
Arg1
Arg2

Event ID 10 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 10 — BGP peering state changed to %1 for peer %2 of routing domain %3.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

BGP peering state changed to %1 for peer %2 of routing domain %3.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 11 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 11 — Maximum prefix limit reached for peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

Maximum prefix limit reached for peer %1.

Fields

NameDescription
Arg1

Event ID 12 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 12 — Maximum prefix limit reached for peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

Maximum prefix limit reached for peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 13 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 13 — BGP peering attempt failed for peer %1 : %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering attempt failed for peer %1 : %2.

Fields

NameDescription
Arg1
Arg2

Event ID 14 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 14 — BGP peering attempt failed for peer %1 of routing domain %2 : %3.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering attempt failed for peer %1 of routing domain %2 : %3.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 15 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 15 — BGP peering collision detected for peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering collision detected for peer %1.

Fields

NameDescription
Arg1

Event ID 16 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 16 — BGP peering collision detected for peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

BGP peering collision detected for peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 17 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 17 — HoldTime set to %1 sec for peer %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

HoldTime set to %1 sec for peer %2.

Fields

NameDescription
Arg1
Arg2

Event ID 18 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 18 — HoldTime set to %1 sec for peer %2 of routing domain %3.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Message

HoldTime set to %1 sec for peer %2 of routing domain %3.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 19 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1

Event ID 19 — TCP connection attempt failed for BGP peer %1.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

TCP connection attempt failed for BGP peer %1.

Fields

NameDescription
Arg1

Event ID 20 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 20 — TCP connection attempt failed for BGP peer %1 of routing domain %2.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

TCP connection attempt failed for BGP peer %1 of routing domain %2.

Fields

NameDescription
Arg1
Arg2

Event ID 21 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 21 — Cannot resolve next-hop %1 for destination %2, learned from peer %3.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Cannot resolve next-hop %1 for destination %2, learned from peer %3. Skipping this route for BGP best path selection until the next-hop is resolvable.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 22 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3
Arg4

Event ID 22 — Cannot resolve next-hop %1 for destination %2, learned from peer %3 of routing domain %4.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Cannot resolve next-hop %1 for destination %2, learned from peer %3 of routing domain %4. Skipping this route for BGP best path selection until the next-hop is resolvable.

Fields

NameDescription
Arg1
Arg2
Arg3
Arg4

Event ID 23 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 23 — Routes to %1, learned from peer %2 were discarded because of ingress routing policy.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Routes to %1, learned from peer %2 were discarded because of ingress routing policy.

Fields

NameDescription
Arg1
Arg2

Event ID 24 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 24 — Routes to %1, learned from peer %2 of routing domain %3 were discarded because of ingress routing policy.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Routes to %1, learned from peer %2 of routing domain %3 were discarded because of ingress routing policy.

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 25 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2

Event ID 25 — Routes to %1, were suppressed from advertisement to peer %2 because of egress routing policy.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Routes to %1, were suppressed from advertisement to peer %2 because of egress routing policy.

Fields

NameDescription
Arg1
Arg2

Event ID 26 —

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Operational

Fields

NameDescription
Arg1
Arg2
Arg3

Event ID 26 — Routes to %1, were suppressed from advertisement to peer %2 of routing domain %3 because of egress routing policy.

Provider
Microsoft-Windows-RasRoutingProtocols-BGP
Channel
Debug

Message

Routes to %1, were suppressed from advertisement to peer %2 of routing domain %3 because of egress routing policy.

Fields

NameDescription
Arg1
Arg2
Arg3