[c-nsp] OSPF adj cycling FULL to LOADING?

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ziti Bake wrote:
> I've been asked for more detail on the routers and
> configs.  
> Here are the relative bits of router config for each
> end:
> 
> At location "A" (Sup720 swrouter):
> 
> 
>>interface GigabitEthernet8/1
>> description Location A, Core LAN
>> ip address 10.0.1.200 255.255.255.0
>> ip ospf authentication-key kungpaosquid
>> load-interval 30
>>
>>interface GigabitEthernet8/16
>> description metro ethernet handoff, Location A
>> no ip address
>> mls qos vlan-based
>> switchport
>> switchport trunk encapsulation dot1q
>> switchport trunk allowed vlan 101-199
>> switchport mode trunk
>> switchport nonegotiate
>>
>>interface Vlan123
>> description Ethernet MAN to Location B
>> ip address 192.168.1.249 255.255.255.252
>>

Which ports are included in VLAN 123?  I don't see any native VLAN on Gig8/16.

Is the metroE connection really a point-to-point or are there other routers
 in the mix?  If really a point-to-point, you should define as such to
eliminate DR election and change the LSA from a network LSA to a router LSA.


>>router ospf 1
>> log-adjacency-changes
>> network 10.0.1.0 0.0.0.255 area 0.0.0.0
> 
> 
> I added one command to enable OSPF over the MAN:
> 
>>! NEW COMMAND:
>> network 192.168.1.248 0.0.0.3 area 0.0.0.0
> 
> 
> 
> At location "B" (Sup2 swrouter):
> 
> 
>>interface GigabitEthernet2/1
>> description Ethernet MAN handoff, Location B
>> no ip address
>> mls qos vlan-based
>> switchport
>> switchport trunk encapsulation dot1q
>> switchport trunk allowed vlan 101-199
>> switchport mode trunk
>> switchport nonegotiate
>> no cdp enable
>>
>>interface GigabitEthernet1/1
>> description Location B, remoteLAN
>> ip address 192.168.1.2 255.255.255.0
>> ip route-cache flow
>> ip ospf authentication-key amazingcontraption
>> load-interval 30
>> no cdp enable
>>
>>interface Vlan123
>> description Ethernet MAN to Location A
>> ip address 192.168.1.250 255.255.255.252
>>
>>router ospf 1
>> log-adjacency-changes
>> area 10.0.0.0 authentication message-digest
>> network 192.168.1.0 0.0.0.255 area 10.0.0.0
> 
> 
> I added the same new command to bring-up area 0 over
> the MAN:
> 
>>! NEW COMMAND:
>> network 192.168.1.248 0.0.0.3 area 0.0.0.0
> 
> 
> 
> There was no tweaking of timers, etc.
> 
> The only odd thing I can see, is that the router in
> Location B was not connected to Area 0 before.  It was
> only in area 10.  This MAN link  provides a second ABR
> between area 10 and area 0.   
> 
> 

Perhaps a little more info on the topology would help.

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDb+z1E1XcgMgrtyYRAom/AKC+UDvXn/1Rf0uuKEJO25fz6rNDkwCbBbf2
9aOQL+6gHX1y1iibsL9IZ3I=
=/VTQ
-----END PGP SIGNATURE-----