Nexus 7000 vpc peer-gateway

timcalkins · ‎09-27-2011

We have run into an issue between a couple of N7Ks in a vPC topology. We have the N7Ks set up with the "vpc peer-gateway" and we have several SVI's between them running HSRP. The issue is that we have a situation in which 4 of the SVIs on the one N7K B switch (vpc secondary) the N7K is not longer acting as a gateway, only the A switch is the active gateway. All of the other SVIs are able to still use both N7Ks as a gateway.

Here is the output that has me concerned:

On the A Switch:

G 2201 0026.9802.20c1 static - F F sup-eth1(R)

G 2202 0026.9802.20c1 static - F F sup-eth1(R)

G 931 0026.9802.20c1 static - F F sup-eth1(R)

G 2211 0026.9802.20c1 static - F F sup-eth1(R)

G 932 0026.9802.20c1 static - F F sup-eth1(R)

on the B switch:

* 2201 0026.9802.20c1 static - F F vPC Peer-Link

* 2202 0026.9802.20c1 static - F F vPC Peer-Link

* 931 0026.9802.20c1 static - F F vPC Peer-Link

G 2211 0026.9802.20c1 static - F F vPC Peer-Link(R)

* 932 0026.9802.20c1 static - F F vPC Peer-Link

For those 4 vlans the B switch is not acting as a gateway.

Has anyone had this experience, I am tempted to do a "shut" and "no shut" to bounce the SVI and see if it starts forwarding again.

I am hesitant as I am not sure if this will fix the gateway issue and do not want to introduce any other problems.

Any ideas?

Jerry Ye · ‎09-27-2011

What NXOS version are you running?

Regards,

jerry

timcalkins · ‎09-27-2011

we are using 4.2(3)

Jerry Ye · ‎09-27-2011

I believe you are hitting this bug:

CSCtf91507

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtf91507

the fix is intergrated in 4.2.6 or above. I would suggested you to upgrade the N7Ks to 4.2.6 or 4.2.8.

HTH,

jerry

timcalkins · ‎09-28-2011

excellent, thanks.

Found also that shutting the SVI forced the peer switch to become the gateway, then "no shut" to the primary switch and both are acting as gateway again.