07-05-2011 02:31 PM - edited 03-07-2019 01:06 AM
Sorry, this issue was because I hadn't added the layer 3 daughter card to the second Nexus 5k. I stepped away from the project and overlooked that detail.
I've setup a pair of 5548s with a peer link between them and have added one fex so far to each. I setup a port channel and vpc from each of the fexs. There is no vpc or connection between the fexs, only at the host, which in this case is a router with 2 ethernet interfaces configured in a port channel. I have HSRP running on both of the 5ks. When the HSRP primary nexus is up everything is fine. As soon as I down the link between the host and the fex connected to the primary HSRP Nexus, connectivity to the virtual gateway is lost. Connectivity between the 2 5ks seems a little flaky. I'm not always able to ping, as is the case right now, from one of the HSRP interfaces to the other HSRP interface of the 2nd 5k. Attached is what I think is the relevant pieces of the config.
host----fex---Nexus5k
\ |
\ |
fex---Nexus5k
thank you,
Bill
07-05-2011 02:50 PM
Hi Bill,
Can you post the vPC configuration?
vpc domain xxx
...
...
Also, is there any next hop devices beyond the N5Ks? Meaning L3 hops.
Regards,
jerry
07-05-2011 03:08 PM
Is the vPC up ?
Sent from Cisco Technical Support iPhone App
07-06-2011 07:42 AM
You think you have a mistake in your configuration:
1/ the two ip i underline in your config have to be diferent in each, otherwise you use the same ip in the same subnet.
Extract form your config:
Nexus A:
interface Vlan1141
no shutdown
ip address 172.21.14.2/26
hsrp version 2
hsrp 1141
mac-address 0000.0000.AAAA
preempt
priority 150
ip 172.21.14.1
Nexus B:
interface Vlan1141
no shutdown
ip address 172.21.14.2/26
hsrp version 2
hsrp 1141
mac-address 0000.0000.AAAA
preempt
priority 150
ip 172.21.14.1
2/ You used preemt but you have no track configured, it means you hsrp will switchover only if your link between fall, i think you should add some track.
Here is the cisco doc for nexus
Can you check if your HSRP switchover work when you disconnect with: show hsrp
configure terminal
2. track object-id interface interface-type number {{ip | ipv6} routing | line-protocol}
3. track object-id {ip | ipv6} route ip-prefix/length reachability
4. interface interface-type slot/port
5. hsrp group-number [ipv4 | ipv6]
6. priority [value]
7. track object-number [decrement value]
8. preempt [delay [minimum seconds] [reload seconds] [sync seconds]]
9. (Optional) show hsrp interface interface-type number
10. (Optional) copy running-config startup-config
from cisco doc here.
Here is my two observation but i think the vPC can be the source of your problem too.
Regards,
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: