Guest

Preview Tool

Cisco Bug: CSCul88393 - Update Overview Section in Layer 2 Configuration Guide for Nexus 5K/6K

Last Modified

Feb 01, 2017

Products (1)

  • Cisco Nexus 5000 Series Switches

Known Affected Releases

6.0(2)N4(1)

Description (partial)

Symptom:
This bug requests to make the followings changes in the Overview Section in Layer 2 Switching Configuration Guide.

The URL for N5K is as follows:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5500/sw/layer2/6x/b_5500_Layer2_Config_602N12_chapter_01.html

The URL for N6K is as follows:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus6000/sw/layer2/6x/b_6k_Layer2_Config_602N12_chapter_01.html

1. Under Layer 2 Ethernet Switching Overview, change
"The device solves congestion problems caused by high-bandwidth devices and a large number of users by assigning each device (for example, a server) to its own 10-, 100-, 1000-Mbps, or 10-Gigabit collision domain. "
to
"The device solves congestion problems caused by high-bandwidth devices and a large number of users by assigning each device (for example, a server) to its own domain. "

2. Under VLAN, change
"All ports, including the management port, are assigned to the default VLAN (VLAN1) when the device first comes up."
to
"All ports are assigned to the default VLAN (VLAN1) when the device first comes up."

3. Under STP Extensions, change
"Loop Guard—Loop Guard prevents the nondesignated ports from transitioning to the STP forwarding state, which prevents loops in the network."
to
"Loop guard helps prevent bridging loops that could occur because of a unidirectional link failure on a point-to-point link."

4. Under STP Extensions, change
"Root Guard—Root Guard prevents the port from becoming the root in an STP topology. "
to
The root guard feature prevents a port from becoming root port or blocked port. If a port configured for root guard receives a superior BPDU, the port immediately goes to the root-inconsistent (blocked) state.

Conditions:
This bug applies to up to 6.0(2)U1.1b Configuration Guide
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.