[Xorp-users] adding/removing interfaces with xorp-cli

[Atanu Ghosh]

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> I still have the problem I reported yesterday where
    Ben> the one ospf doesn't seem to realize the remote ospf
    Ben> instance has changed when I logically move the interface
    Ben> to a new remote xorp...

    Atanu> After you have moved the links could you send the output of "show
    Atanu> interfaces" from both ends of a "broken" link?

    Ben> Router-8 is the one that did not have config change to it (but had
    Ben> it's connection to router 2 moved to router 1.)  It appears to think
    Ben> it is still connected to router 2.

    Ben> Since this is all sort of virtual on a single machine, it's
    Ben> possible it *is* somehow talking to router 2, but router-2
    Ben> certainly doesn't seem to know about it.

    Ben> [root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20008; xorpsh
    Ben> Welcome to XORP on lanforge-33-46
    Ben> root at lanforge-33-46> show ospf4 neighbor
    Ben> Address         Interface             State      ID              Pri  Dead
    Ben> 10.4.0.7         rddVR45/rddVR45        Full      127.1.0.2        128    36
    Ben> root at lanforge-33-46> show interfaces
    Ben> my_discard/my_discard: Flags:<ENABLED> mtu 0
    Ben> physical index 0
    Ben> rddVR45/rddVR45: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.4.0.2 subnet 10.4.0.0/24 broadcast 10.4.0.255
    Ben> physical index 154
    Ben> ether 0:89:d6:d6:9a:42
    Ben> rddVR5/rddVR5: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255
    Ben> physical index 99
    Ben> ether 0:16:94:2e:4a:1f
    Ben> root at lanforge-33-46> quit
    Ben> [root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20001; xorpsh
    Ben> Welcome to XORP on lanforge-33-46
    Ben> root at lanforge-33-46> show ospf4 neighbor
    Ben> Address         Interface             State      ID              Pri  Dead
    Ben> 10.0.0.1         rddVR1/rddVR1          Full      127.1.0.2        128    35
    Ben> 10.4.0.2         rddVR44/rddVR44        Init      127.1.0.8        128    36
    Ben> root at lanforge-33-46> show interfaces
    Ben> my_discard/my_discard: Flags:<ENABLED> mtu 0
    Ben> physical index 0
    Ben> rddVR1/rddVR1: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.0.0.2 subnet 10.0.0.0/24 broadcast 10.0.0.255
    Ben> physical index 95
    Ben> ether 0:ec:14:a9:b8:b7
    Ben> rddVR44/rddVR44: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.4.0.7 subnet 10.4.0.0/24 broadcast 10.4.0.255
    Ben> physical index 156
    Ben> ether 0:4d:6:d3:45:21
    Ben> root at lanforge-33-46> quit

The default configuration for OSPF has a router dead interval
(router-dead-interval) of 40 seconds. Only after 40 seconds has elapsed
during which time no hello or other messages have been received by a
router will the state of a neighbour change. The last field in the "show
ospf4 neighbour" is the router dead interval counting down. The state
remaining for 40 seconds after a link change should be expected. After
40 seconds the state should go to down. If you were moving physical
cables around then the disconnecting of the cable from the interface
would be detected by the FEA and OSPF would be informed, in which case
the state would move immediately to down.

>From what you say it seems that no new adjacencies are formed after
moving a link. I would enable tracing in OSPF and/or use tcpdump to see
if hello messages are being exchanged.

    Atanu.