09-27-2012 08:19 AM
Hi all
I have a strange behavior between 2 FI and 2 nexus 5k configured as VPC , From a remote location and from my desktop I can ping odd ip and not even , from an other desktop in the same LAN the reverse, for both the tracert are good.
The only solution is to shutdown ports 1/1-2 on nexus A or FI A and in that case both desktops can ping both IP.
All seems OK, no log error , no error on interface , I give below some commands
What thing to know is that the nexus b has a L3 card , not the Nexus A , In fact I am waiting for a spare L3 daughter card.
On both NexusI have such configuration and status
interface port-channel201
description ucs-Fab-a
switchport mode trunk
switchport trunk native vlan 999
spanning-tree port type edge trunk
vpc 201
UCSM-PARIS-A(SSI153000ST)
Eth1/1 129 S I s UCS-FI-6248UP Eth1/11
UCSM-PARIS-A(SSI153000ST)
Eth1/2 174 S I s UCS-FI-6248UP Eth1/12
sh port-channel summary
201 Po201(SU) Eth LACP Eth1/1(P) Eth1/2(P)
sh mac address-table dynamic | i 1010
* 1010 0025.b5c9.481e dynamic 0 F F Po201
* 1010 0025.b5c9.481f dynamic 10 F F Po201
sh ip arp
10.203.136.21 00:01:05 0025.b5c9.481f Vlan1010
10.203.136.22 00:12:43 0025.b5c9.481e Vlan1010
On both FI A have such configuration and status
terface port-channel201
description U: Uplink
switchport mode trunk
pinning border
switchport trunk native vlan 999
switchport trunk allowed vlan 1,104,999,1010-1013,1020-1021,1500-1502,1510-151
2,1550-1552,1560-1561,1600-1602,1610-1619
speed 10000
sh port-channel summary
201 Po201(SU) Eth LACP Eth1/9(P) Eth1/10(P) Eth1/11(P)
Eth1/12(P)
sh mac address-table dynamic
* 1010 0025.b5c9.481e dynamic 0 F F Po201
* 1010 0025.b5c9.481f dynamic 0 F F Po201
sh cdp nei
E2RTR001(SSI1608085E) Eth1/9 120 S I s N5K-C5548UP Eth1/1
E2RTR001(SSI1608085E) Eth1/10 120 S I s N5K-C5548UP Eth1/2
E2RTR002(SSI16080F17) Eth1/11 151 R S I s N5K-C5548UP Eth1/1
E2RTR002(SSI16080F17) Eth1/12 136 R S I s N5K-C5548UP Eth1/2
Any ideas, A configuration I forgot on FI ?
Regards .
09-27-2012 10:56 AM
Do you use the 5548-L3 for any routing? Note that having asymetric routing in vPC pair of Nexus 5500s is not supported and yields unexpected forwarding behavior.
09-27-2012 11:14 AM
In fact in the probem I described the path is Esx -> FAB A - > N5K-A (for layer 2) -> N5K-B (for L3) -> routing to the LAN
And what you told me is that such configuration is not supported with VPC configuration , so I need to wait to receive the L3 card for the N5k-A. and check later if I have the same problem.
thanks
09-27-2012 03:15 PM
Correct.. You should not see this problem once you install L3 module in the N5K-A and implement a gateway redundancy protocol.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide