I had an interesting issue this morning... migrating an eBGP peer from an Avaya Ethernet Routing Switch 8600 to a Cisco Nexus 7010.
I tried to use a legacy access-list but the NX-OS wouldn't hear of it so I had to use prefix-lists instead along with route-maps.
ip prefix-list SIEMENS-TEST-ROUTE seq 5 permit 172.16.0.0/16 le 32
route-map SIEMENS-TEST permit 10
match ip address prefix-list SIEMENS-TEST-ROUTE
router ospf 1
redistribute bgp 102 route-map SIEMENS-TEST
The route in BGP was 172.16.10.0/24 so it took me a while to figure out the syntax for the prefix-list so the 172.16.0.0/16 was interpreted as a range and not a literal route.
I can see the route in the other backbone switches via OSPF but I don't see the route in the OSPF table of the originating Cisco 7010 switch. Is that normal, I'm not sure myself...
sw-n7010-ccr-a(config-router)# show ip route 172.16.0.0/16 longer-prefixes
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
172.16.1.0/24, ubest/mbest: 1/0
*via 10.103.127.83, Eth1/3, [110/50], 2w0d, ospf-1, type-1
172.16.3.0/24, ubest/mbest: 1/0
*via 10.103.127.83, Eth1/3, [110/50], 5w6d, ospf-1, type-1
172.16.10.0/24, ubest/mbest: 1/0
*via 10.103.124.13, Eth1/4, [20/0], 03:01:05, bgp-102, external, tag 64600
172.16.31.0/24, ubest/mbest: 1/0
*via 10.103.127.83, Eth1/3, [110/50], 26w1d, ospf-1, type-1
Anyone else used BGP on the NX-OS platform?
Cheers!
