cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
201
Views
1
Helpful
1
Replies

mismatched NSSA option bit between IOS-XE and NX-OS

dr_9356
Level 1
Level 1

I am attempting to bring up OSPF between a Cat8000v router and a Nexus9000 switch, we currently have Cat8000v router peering to physical ISR-4000 with no issues. I am simply trying to change the ospf peer from the ISR to a n9000.

We use NSSA between the current devices (IOS-XE to IOS-XE), and it works perfectly. But if I translate the config to my N9000 device, it just constantly spams:

*Jan 2 18:46:57.044: OSPF-1000 HELLO Gi3: Rcv hello from 10.1.1.2 area 1000 10.1.1.2
*Jan 2 18:46:57.044: OSPF-1000 HELLO Gi3: Hello from 10.1.1.2 with mismatched NSSA option bit

 I will mention, if I remove the "area 1000 nssa" config from both devices the peering comes up instantly. Am I just using the nssa config on the n9k wrong, or missing something on it?

Current cat8000k config:

router ospf 1000
area 1000 nssa
passive-interface default
no passive-interface GigabitEthernet1
network 10.1.1.1 0.0.0.0 area 100

And the config on the new n9k:

router ospf new-ospf
area 1000 nssa default-information-originate
passive-interface default
vrf RED
capability vrf-lite

interface Vlan1000
no shutdown
vrf member RED
no ip redirects
ip address 10.1.1.2
no ip ospf passive-interface
ip router ospf RED area 1000

Again, I have to stress that if I remove the "area 1000 nssa" config lines, everything comes up immediately. So I don't believe this is an issue with vrfs, vlans, etc... Of course I cannot change the area type to non-nssa without massive other changes, so I'd really like to avoid that. Thanks all

1 Accepted Solution

Accepted Solutions

dr_9356
Level 1
Level 1

Sometimes talking to the rubber ducky is the best option.

For anyone that noticed right away my blunder, I needed to put the nssa config under the vrf in the n9k config.

So the solution was:

router ospf new-ospf
passive-interface default
vrf RED
passive-interface default
area 1000 nssa default-information-originate
capability vrf-lite

 

View solution in original post

1 Reply 1

dr_9356
Level 1
Level 1

Sometimes talking to the rubber ducky is the best option.

For anyone that noticed right away my blunder, I needed to put the nssa config under the vrf in the n9k config.

So the solution was:

router ospf new-ospf
passive-interface default
vrf RED
passive-interface default
area 1000 nssa default-information-originate
capability vrf-lite

 

Review Cisco Networking for a $25 gift card