It looks like bgpd has a problem with validating nexthop on new interfaces
when they are created.
A flap of the interface or restarting bgpd makes nexthop validate.
I have only tested with vlan interfaces.
Router up and running:
cr203-STO# bgpctl sh
Neighbor AS MsgRcvd MsgSent OutQ Up/Down
State/PrefixRcvd
192.168.30.10 65000 6 26 0 00:01:40 0
10.1.1.14 65000 61 52 0 00:01:54 23
10.1.1.1 65000 61 53 0 00:01:54 18
172.16.1.5 65000 63 61 0 00:01:53 18
cr203-STO# bgpctl sh next
Nexthop State
10.1.1.14 valid vlan16 UP, Ethernet, unknown
172.16.1.5 valid vlan12 UP, Ethernet, unknown
10.1.1.1 valid vlan13 UP, Ethernet, unknown
cr203-STO#
New interface created:
cr203-STO# ifconfig vlan26 create
cr203-STO# ifconfig vlan26 vlan 26 vlandev pcn1
cr203-STO# ifconfig vlan26 10.1.1.37 netmask 255.255.255.252
New peering added (remote peer uses set nexthop self):
cr203-STO# bgpctl reload
reload request sent.
cr203-STO# bgpctl sh
Neighbor AS MsgRcvd MsgSent OutQ Up/Down
State/PrefixRcvd
10.1.1.38 65000 36 36 0 00:01:10 22 <<<<
New peering
192.168.30.10 65000 14 43 0 00:05:14 0
10.1.1.14 65000 132 128 0 00:05:28 23
10.1.1.1 65000 133 130 0 00:05:28 18
172.16.1.5 65000 136 141 0 00:05:27 18
cr203-STO# bgpctl sh next
Nexthop State
10.1.1.38 invalid vlan26 <<<< New peering
10.1.1.14 valid vlan16 UP, Ethernet, unknown
172.16.1.5 valid vlan12 UP, Ethernet, unknown
10.1.1.1 valid vlan13 UP, Ethernet, unknown
cr203-STO#
Flap interface:
cr203-STO# ifconfig vlan26 down
cr203-STO# ifconfig vlan26 up
cr203-STO# bgpctl sh next
Nexthop State
10.1.1.38 valid vlan26 UP, Ethernet, unknown <<<< Looking
good
10.1.1.14 valid vlan16 UP, Ethernet, unknown
172.16.1.5 valid vlan12 UP, Ethernet, unknown
10.1.1.1 valid vlan13 UP, Ethernet, unknown
cr203-STO#
/Tony
--
Tony Sarendal - [EMAIL PROTECTED]
IP/Unix
-= The scorpion replied,
"I couldn't help it, it's my nature" =-
