OPERATIONAL DEFECT DATABASE
...
...
After adding a member to an fport (NPV to NPIV) san-port-channel, the traffic stops flowing over the san-port-channel. When the problem is hit, MAC entry for the san-port-channel is getting deleted due to which the packets are not getting forwarded on N6K. Example: N56128# show platform fwm info hw-stm | i San-po1 1.2 8c60.4f86.1fa7 San-po1 1:2100:0 0:0:1 2.a.bc.0.0.1c (e:0) (San-po1 is case sensitive) When san-port-channel line is missing there will be no traffic flow accross the san-port-channel.
Nexus 6000 or Nexus 5600 in NPV mode.
If the problem is already happening, then shut, no shut the port-channel from the NPIV switch. To prevent the problem from happening, do not place the fibre channel interfaces in a port-channel. If one of the fc interfaces flaps, the host will suspend I/O and log back into the fabric through a different uplink and resume I/O.
After removing the workaround with no port-channel load-balance ethernet source-dest-port, the problem may not be easily reproduced.
When a san-port-chaannel member is flapped from the other side of NP link, before doing "member-port addition to san-port-channel" programming in hardware, traffic can come on that member-port. So, hardware will detect that the traffic is received on FC port instead of san-port-channel based on the existing STM table entry created for redirecting FC traffic via NP link. Fix Description: If the FC port belongs to san-port-channel, consider san-port-channel's FC LIF instead of member-port's LIF while dealing with MAC address entry into STM table.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
