Cisco Fabric Manager; Resolved Caveats-Cisco Nx-Os Release 4.0(0)N1(1); Command; Switch - Cisco AJ732A - MDS 9134 Fabric Switch Release Note

Cisco Fabric Manager

S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
•
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1)
This was the first release of Cisco NX-OS for Nexus 5000 Series switches. There are no resolved caveats
for this release.
Cisco Fabric Manager
Beginning with Cisco Fabric Manager release 3.4(1a), Nexus 5000 Series switches are supported by
Fabric Manager.
If you are deploying Nexus 5000 Series switches with FCoE, you should operate Fabric Manager in
Display FCoE mode. Display FCoE mode displays additional tree nodes, menu items, toolbar buttons,
and topology nodes and links related to FCoE. To convert to Display FCoE mode, edit the
server.properties file to set the display FCoE property to true.
For additional information about Fabric Manager, see Cisco Nexus 5000 Series Switch Fabric Manager
Software Configuration Guide, Release 4.0
The following sections apply to Fabric Manager support for Nexus 5000 series switches:
•
•
Limitations
This section lists the Cisco Fabric Manager limitations related to managing Nexus 5000 series switches.
Ethernet Configuration
You cannot configure physical Ethernet interfaces using Fabric Manager or Device Manager. You must
configure physical Ethernet interfaces using CLI commands.
SPAN
You cannot use Device Manager to configure Ethernet or virtual Ethernet interfaces as SPAN source
ports or to configure Ethernet interfaces as destination ports. The workaround is to configure SPAN
using CLI commands.
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
24
no lldp receive
no lldp transmit
CSCsq36609
Symptom: For a virtual Ethernet or virtual Fibre Channel interface configured as a SPAN source,
changing the interface administrative state results in a memory leak. Deleting and adding SPAN
sessions also causes memory leaks. The memory leaks eventually cause a switch reboot.
Workaround: Avoid using virtual Ethernet and virtual Fibre Channel interfaces as SPAN sources.
Avoid deleting and adding SPAN sessions.
Limitations, page 24
Caveats, page 25
OL-16601-01