Guest

Preview Tool

Cisco Bug: CSCvi49478 - Same port# on different FEX can not ping if connected through M3

Last Modified

Jun 12, 2018

Products (21)

  • Cisco Nexus 7000 Series Switches
  • Cisco MDS 9124 Multilayer Fabric Switch
  • Cisco Nexus 7000 10-Slot Switch
  • Cisco MDS 9710 Multilayer Director
  • Cisco MDS 9250i Multiservice Fabric Switch
  • Cisco Nexus 7000 4-Slot Switch
  • Cisco MDS 9148S 16G Multilayer Fabric Switch
  • Cisco MDS 9222i Multiservice Modular Switch
  • Cisco Nexus 7700 6-Slot Switch
  • Cisco MDS 9509 Multilayer Director
View all products in Bug Search Tool Login Required

Known Affected Releases

8.1(1)

Description (partial)

Symptom:
Unicast traffic doesn't work between two FEXes connected to M3 and same port number (same source vif). Eg 101/1/1 and 102/1/1


Same port # set up:::::::: (101/1/5 and 103/1/5)

F340.06.17-3800-6#

F340.06.17-3800-6#ping 172.16.0.204

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.0.204, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)



F340.06.17-3800-6#ping 172.16.0.200 <<<------(ping to SVI works ok, all the time)

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.0.200, timeout is 2 seconds:

.!!!!

Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms

F340.06.17-3800-6#

Conditions:
Both FEXes are connected to same asic instance of M3 LC.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.