OSPF routes not becomming active until a router has failed

From: AdamWoodland (AdamWoodland_at_discussions.microsoft.com)
Date: 12/15/04

Next message: Desmond Lee: "RE: work throughs"
Previous message: John Pugh: "Re: ACL Permissions"
Messages sorted by: [ date ] [ thread ]

Date: Wed, 15 Dec 2004 08:07:06 -0800

Hi, the problem we have is that we have two Windows 2003 servers (standard
edition) with RRAS installed, dual networked, talking to two Cisco 2600
routers (IOS 12.1.25). I administer the servers, switches and network up to
the FastEthernet ports on the Cisco routers, at which point a third-party
takes over. No firewalls are involved and the switches are configured not to
block any traffic.

IP Addresses:

Server A : 10.36.16.20 & 10.36.17.20
Server B : 10.36.16.29 & 10.36.17.29
Router A : 10.36.16.5 & 10.36.17.5
Router B : 10.36.16.6 & 10.36.17.6

Subnet mask is /24.

There are two Cisco catalyst switches, not directly connected to each other.
Each server has one connection into each switch, and each router has a
connection into each switch. This gives us two distinct LANS, we call them X
(10.36.16.0/24) and Y (10.36.17.0/24), and each LAN having four OSPF devices
+ one switch connected.

The routers, as well as having the two FastEthernet interfaces, have a
serial connection to other routers remotely. The routers, and the other
routers down the serial line, talk BGP to the outside world and these routes
are redistributed to the two servers on all interfaces. Router A
redistributes them with a metric of 50 and B with a metric of 100, to force
the routes via Router A normally. They are all in the same area, 0 (or
0.0.0.0 on the server), no authentication. The servers have a router priority
of ‘0’; the rest of the setup is default. The Cisco routers will always be
the DR or BDR.

Under normal circumstances everything is fine, all four devices see each
other, form adjacencies, and the link state databases appear correct. During
all the tests the adjacencies have always been correct.

The problem is that if the serial interface goes down (i.e. it's pulled out)
on the primary router, then whilst the routing table on the secondary router
updates correctly, the servers don't. Using ethereal and Windows event
logging the updates from the primary router are received and are processed
and what happens is that on the server, the routes via the primary router
(with a metric of 50) disappear, and disappear from the link state database
soon after, however the link state database still contains information for
the secondary router, yet this information isn't put into the routing table,
the only OSPF routes in the routing table are the two local LANs. The Windows
event log doesn't show anything about the new (from the secondary router)
routes being added.

If we disconnect both FastEthernets from the primary router, or the router
is powered off, then the routes correctly come into the routing table, with
their correct metric (test performed with both serial connected and
disconnected for reference purposes).

When we have the network in fully connected order, disconnecting the serial
port on the secondary router (so not affecting traffic) and reconnecting the
interfaces cause the correct OSPF updates to be sent out, confirmed by
looking at the windows event log and the primary Cisco router's database.

Another test that was successful was disconnecting the active route used by
the primary router. Under normal circumstances where everything is connected,
the routes to the primary server go via 10.36.17.5 (as opposed to 16.5).
Disconnecting this interface by pulling the cable means that the servers
correctly reconfigure to use the 16.5 address.

Through our testing, the only way we can get the secondary router's routes
to be used, is by removing the primary router from the network (pull cables
or power off). All other tests we've done resulted in the secondary routes
not becoming active (when they should have).

We have also done some of these tests with the Y LAN cables disconnected
from the servers, and the problem still happens.

Currently the system is "live" so testing every little idea isn't feasible.
It worked when it was being tested when it wasn't live, but when it when to
site it stopped working. Nothing has changed except when being tested in the
factory, the router setup down the serial links of the Cisco routers was
different, and used EIGRP, which was redistributed by OSPF (the remote route
information was the same, as was the local IP addresses). We have Ethereal
and Windows event logs of most tests should they be of any use.

Server reboots don't make a difference.

I haven't found anything on the Microsoft nor Cisco websites that seem to be
of help. A search via Google has been equally helpful. So anything that could
explain this behaviour and how to solve it would be much appreciated.

I have below a few Window event log lists, that may be of some help. More is
available on request. Information in brackets is information from me and not
actual log information.

Failing Se0 on primary router:

(10:57:05 Fail Se0 on primary router)
10:57:05 T8: DELETED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.120 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.112 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.104 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:57:05 T8: DELETED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (0.0.0.0)
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.96 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.40 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.104 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.48 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.112 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.56 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.120 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.0 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.64 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.8 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.72 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.16 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.80 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.24 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.88 router
10.36.16.5
10:58:53 N3: LSA of MaxAge flushed: type LS_ASE LSID 10.201.4.32 router
10.36.16.5
(10:59:11 Reconnect Se0 on primary router)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.120 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.120 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.112 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.112 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.104 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.104 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.96 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.88 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.80 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.72 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.64 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.56 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.48 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.40 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.32 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.24 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.16 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.8 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)
10:59:46 T5: Received new LSA - type LS_ASE LSID 10.201.4.0 router
10.36.16.5 neighbor 10.36.16.5
10:59:46 T7: ADDED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.17.5 (10.36.17.0)

Primary router being turned off and rebooted:

(11:11:13 Primary router powered off)
11:11:52 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:11:52 T2: Neighbor 10.36.16.5 Event: Inactivity Timer State change
Full->Down
11:11:53 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:11:53 T2: Neighbor 10.36.17.5 Event: Inactivity Timer State change
Full->Down
11:11:53 T7: ADDED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.120 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.112 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.104 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T7: ADDED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Metric 100 Nexthop 10.36.17.6 (10.36.17.0)
11:11:53 T8: DELETED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.120 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.112 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.104 (255.255.255.248) Type
LS_ASE. Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:11:53 T8: DELETED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Metric was 50 Nexthop 10.36.17.5 (255.255.255.0)
11:15:01 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:15:59 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:15:59 T2: Neighbor 10.36.17.5 Event: Reset Adjacency State change
Exch Start->2 Way
11:15:59 T3: Backup Designated Router changed on network: 10.36.17.20
10.36.16.5->0.0.0.0
11:15:59 T2: Neighbor 10.36.17.5 Event: Two Way Received State change
Init->Exch Start
11:15:59 T2: Neighbor 10.36.17.5 Event: Adjacency OK State change 2
Way->Exch Start
11:15:59 T3: Backup Designated Router changed on network: 10.36.17.20
0.0.0.0->10.36.16.5
11:15:59 T2: Neighbor 10.36.17.5 Event: Hello Received State change
Down->Init
11:15:59 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:15:59 T2: Neighbor 10.36.16.5 Event: Reset Adjacency State change
Exch Start->2 Way
11:15:59 T3: Backup Designated Router changed on network: 10.36.16.20
10.36.16.5->0.0.0.0
11:15:59 T2: Neighbor 10.36.16.5 Event: Two Way Received State change
Init->Exch Start
11:15:59 T2: Neighbor 10.36.16.5 Event: Adjacency OK State change 2
Way->Exch Start
11:15:59 T3: Backup Designated Router changed on network: 10.36.16.20
0.0.0.0->10.36.16.5
11:15:59 T2: Neighbor 10.36.16.5 Event: Hello Received State change
Down->Init
11:16:06 T7: ADDED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.120 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.112 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.104 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
11:16:06 T7: ADDED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Metric 50 Nexthop 10.36.16.5 (10.36.16.0)
(11:16:08 Approximate time routes returned for primary router, as seen
from server A)
11:16:09 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:16:09 T2: Neighbor 10.36.17.5 Event: Adjacency OK State change 2
Way->Exch Start
11:16:09 T3: Backup Designated Router changed on network: 10.36.17.20
0.0.0.0->10.36.16.5
11:16:09 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:16:09 T2: Neighbor 10.36.16.5 Event: Adjacency OK State change 2
Way->Exch Start
11:16:09 T3: Backup Designated Router changed on network: 10.36.16.20
0.0.0.0->10.36.16.5
11:16:11 T6: CHANGED Route to 10.201.4.32 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.88 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.24 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.80 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.16 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.72 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.8 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.64 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.0 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.120 (255.255.255.248) Type
LS_ASE. Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New
nexthop 10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.56 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.112 (255.255.255.248) Type
LS_ASE. Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New
nexthop 10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.48 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.104 (255.255.255.248) Type
LS_ASE. Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New
nexthop 10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.40 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 T6: CHANGED Route to 10.201.4.96 (255.255.255.248) Type LS_ASE.
Old metric 50 New metric 50 Old Nexthop 10.36.16.5 (10.36.16.0) New nexthop
10.36.17.5 (10.36.17.0)
11:16:11 C3: Packet Rejected: SOURCE NEIGHBOR IN WRONG STATE src
10.36.16.5 state Exch Start type Link State Update
11:16:11 C3: Packet Rejected: SOURCE NEIGHBOR IN WRONG STATE src
10.36.17.5 state Exch Start type Link State Update
11:16:12 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:16:12 T2: Neighbor 10.36.16.5 Event: Loading Done State change
Loading->Full
11:16:12 T2: Neighbor 10.36.16.5 Event: Exchange Done State change
Exchange->Loading
11:16:12 T2: Neighbor 10.36.16.5 Event: Negotiation Done State change
Exch Start->Exchange
11:16:13 T4: Originating new LSA - type LS_RTR LSID 10.36.16.20 router
10.36.16.20
11:16:13 T2: Neighbor 10.36.17.5 Event: Loading Done State change
Loading->Full
11:16:13 T2: Neighbor 10.36.17.5 Event: Exchange Done State change
Exchange->Loading
11:16:13 T2: Neighbor 10.36.17.5 Event: Negotiation Done State change
Exch Start->Exchange

Next message: Desmond Lee: "RE: work throughs"
Previous message: John Pugh: "Re: ACL Permissions"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: Route Maps with HSRP
... >Has anyone ever used route-maps that set the next hop to an HSRP ... >address of another router where the router setting the ... >nexthop is in the that particular HSRP group? ...
(comp.dcom.sys.cisco)
BGP prepending and local preference question
... preference and AS prepending will take care of this but BGP is not my ... network x.x.x.0 0.0.0.255 area 0 ... router bgp myasnumber ... neighbor b.b.b.b distribute-list ADVERTISE out ...
(comp.dcom.sys.cisco)
Re: P2P over wireless LAN
... I'm just getting into filesharing, while my neighbor, I suspect, has tons ... If my neighbor and I run the same P2P software, such as limewire, and I ... the router, ...
(Fedora)
Re: Internet Connection Sharing and Hurricane Katrina
... Turning off the router functions should allow the router to operate as a ... I would assume that you have both asked your neighbor if he/she ... > can pick up one of my neighbors wireless network if I hang the antenna ... > but am having trouble with the Internet Connection Sharing. ...
(microsoft.public.win2000.networking)
Re: BGP And Load Balancing With Two Routers
... If the network isn't advertised by Sprint, then traffic will have to go ... > Router A and B, then interconnect with a patch cable. ... As Qwest is only a 10Meg pipe I would like to ... > neighbor 160.81.248.77 description ebgp link to sprint ...
(comp.dcom.sys.cisco)