Cisco Nexus Fabric Manager Release Notes for Administrators, Release 1.2(2)
Available Languages
Cisco Nexus Fabric Manager Release Notes for Administrators, Release 1.2(2)
This document describes the features, bugs, and limitations for Cisco Nexus Fabric Manager. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section.
Table 1 shows the online change history for this document.
Table 1. Online History Change
| Date |
Description |
| November 11, 2016 |
Created the Release Notes for Release 1.2(2) |
Contents
■ Caveats
■ Obtaining Documentation and Submitting a Service Request
Introduction
The Cisco Nexus Fabric Manager (NFM) is a product designed to simplify fabric lifecycle management requirements for users requiring easier options than switch-by-switch offerings such as CLI and element managers. The NFM provides a simple point-n-click web-based user interface to a fabric-aware management engine that can build and manage fabrics based on simplified user requests. The NFM bears the heavy lifting of creating, installing, and maintaining proper fabric-wide switch configurations to deliver on these simplified requests. The NFM, being fabric-aware, also understands how the fabric should operate and can monitor and take actions within the fabric throughout its lifecycle to ensure optimal fabric operation. You can focus on workflows associated with delivering business-enabling applications and leave the complexity of building and managing the fabric to the NFM.
Behind the scenes, the NFM implements a self-managed VXLAN-based topology incorporating an EVPN control plane. This choice of technology ensures a future-proofed fabric delivering service for today and tomorrow’s requirements in an open manner.
Supported Platforms
· Cisco Nexus 9500 Series switches
· Cisco Nexus 9300 Series switches
· Cisco Nexus 9200 Series switches
· Cisco Nexus 2000 Series Fabric Extenders
Supported NX-OS Releases
Table 2 Supported NX-OS Releases
| 7.0(3)I4(1), 7.0(3)I4(2), 7.0(3)I4(3), 7.0(3)I4(4) |
These releases are supported. |
| 7.0(3)I3(1) |
This release is supported. |
| 7.0(3)I2(4) |
This release is supported. |
| 7.0(3)I2(3) |
This release is supported only if the patch for CSCuy96592 is loaded. This release does not support the Nexus Fabric Manager Auto Fabric Provisioning (AFP) feature. |
| 7.0(3)I2(2e) |
This release is supported. |
Limitations
The following are the known limitations for Cisco Nexus Fabric Manager:
· The NFM does not support border-spine configurations.
· The maximum number of gateways for a fabric of 20 switches or less is 50. The maximum number of gateways for a fabric greater than 20 or up to 50 is 20.
· The maximum number of leaf switches within a supported fabric is 50.
· The maximum number of host-facing interfaces within the fabric connected to devices such as physical servers, firewalls, and load balancers is 2,400. For example, a dual-homed host would count as two host-facing attachments.
· The maximum number of discovered foreign devices is 1,200. A discovered device is any foreign device that has been discovered by the NFM through either CDP or LLDP and results in a created foreign object (host or networking device) within the NFM. A device that is connected to a leaf switch (host or networking device) that does not provide CDP or LLDP information and is enabled through a manual interface role assignment (host-facing or border) does not count towards this limit.
· The maximum number of configurable broadcast domains is limited to 500.
· The Cisco Nexus 2000 Series of fabric extenders (FEX) is supported in a limited fashion. FEX Fabric interfaces must be configured on the CLI, and then host interfaces are shown and can be managed within the Cisco Nexus Fabric Manager.
· The Cisco Unified Compute System B-Series (UCS) fabric interconnect module is discoverable by the NFM. However, any compute blades behind it are not represented within the NFM topology.
· After an upgrade from a 1.1 release, the allowed range of BGP autonomous system numbers are reduced from a 4-byte to a 2-byte autonomous system. During an upgrade, any AS number greater than the limit 65535 will be converted to 65535. AS numbers should be manually checked by the administrator and modified according to their preferences before using the system due to any change to the BGP AS results in a disruptive change to the fabric.
· If using the browser Firefox, there may be an additional password prompt when logging in for the first time after a password change. This only occurs in Firefox, and once the user credentials are provided then the login process is complete.
Caveats
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products.
Note: You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. if you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
■ Known NX-OS Issues that Might Impact Cisco Nexus Fabric Manager Functionality
■ Resolved Caveats - Cisco Nexus Fabric Manager, Release 1.2(2)
■ Open Caveats – Cisco Nexus Fabric Manager, Release 1.2(2)
Known NX-OS Issues that Might Impact Cisco Nexus Fabric Manager Functionality
The following table describes how these NX-OS issues impact NFM. Please consult the NX-OS release notes for more details
Table 5. Cisco Nexus Fabric Manager, Release 1.2(2) – Known NX-OS Issues
| Record Number |
Release Note Enclosure |
| · Synopsis: A Nexus 9K switch auto-provisioned using Auto Fabric Provisioning my refuse to authenticate after successful first boot. · Symptoms: The switch shows SearchFailed after successful provisioning using Auto Fabric Provisioning. Login at the console or authentication through NFM does not work. · Conditions: The switch was auto-provisioned using Auto Fabric Provisioning feature of Cisco NFM. · Workarounds: There is no known workaround. The only way out of this situation is to reclaim the switch using recovery mode, write erase to put the switch back into POAP mode and retry by entering a different password for the switch object inside of NFM. |
|
| · Synopsis: Cisco Nexus 9000 series switches become unable to save startup configuration. · Symptoms: Recurring faults are reported on one or more switches with the command ‘copy running-config startup-config’ failing with the error ‘Configuration update aborted: request was aborted’. · Conditions: A backing for a logical gateway is created or modified, which caused the ‘no ip redirects’ to be issued for a SVI on a switch. As an example, this problem can be triggered by removing or changing the VRF of a logical gateway. · Workarounds: Manually execute the command ‘no ip redirects’ on the backing of the logical gateway on the switch. |
|
| · Synopsis: Duplicate foreign switches (FSW) would be discovered. · Symptoms: In the switchpool, a foreign switch (FSW) for the same switch will appear twice. · Conditions: If on the switch, ‘ip domain-name x’ is set, the system name does not match for CDP or LLDP advertisements for the switch. · Workarounds: Remove ‘ip domain-lookup’ and ‘ip domain-name x’ on the switch and reload it. On NFM delete the duplicate entries. |
|
| · Synopsis: Certain VRF changes may not take effect on the switch. · Symptoms: VRF creation does not succeed, or a VRF does not get updates after a name change. NFM reports faults on the switches related to VRF commands that report ‘Requested object does not exist’. · Conditions: No known conditions, the failure appears to be sporadic. · Workarounds: No workaround, but retrying the operation using the reconcile button may help. |
Note: If using the Nexus C93108YC or C93108TC-EX fixed switches or the N9K-X9732C-EX line card for the Nexus 9500 modular switch , an extra command is required before switches are to be managed by the NFM. The following command must be entered on each switch at the CLI, followed by a switch reboot, and cannot be automated by the Nexus Fabric Manager.
switch# system routing template-vxlan-scale
To verify this command has been properly applied to applicable switches and a reboot has been preformed, run the following command on the switch CLI:
switch# show system routing mode
Configured System Routing Mode: Vxlan Scale
Applied System Routing Mode: Vxlan Scale
“Configured” indicates the command has been applied, and “Applied” indicates the reboot has occurred.
Resolved Caveats – Cisco Nexus Fabric Manager Release 1.2(2)
The following table lists the Resolved Caveats in Cisco Nexus Fabric Manager, Release 1.2(2). Click the Record Number to access the Bug Search Tool and see additional information about the bug.
To see the most up-to-date list of Resolved Caveats, go to:
Table 6. Cisco Nexus Fabric Manager, Release 1.2(2) – Resolved Caveats
| Record Number |
Bug Headline |
| After a 1.1(2) to 1.2(1) upgrade some objects report references to deleted objects |
|
| Apache Commons FileUpload HTTP Request Header Value Handling Denial of Service Vulnerability |
|
| Changing admin state on switch interface has impact on neighbor expired flag even if the cable was pulled |
|
| Importing a new switch in an existing large environment is very slow |
|
| Interface part of a port channel is marked as unreachable after a switch software upgrade happens |
|
| New connections created if DHCP server and NFM coexist |
|
| Port channel member interface states are not live updated |
|
| Switch editing: cannot clear text fields if they are profiled |
|
| Switch unreachable after upgrade from 1.1(2a) to 1.2(1) |
|
| UI hangs or is extremely slow on topology and switch interfaces |
|
| When one or more spine switches fail, traffic may be disrupted after a switch reconcile operation |
Open Caveats – Cisco Nexus Fabric Manager Release 1.2(2)
The following table lists descriptions of open bugs in Cisco Nexus Fabric Manager, Release 1.2(2). You can use the record number to search the Cisco Bug Search Tool for details about the bug.
To see the most up-to-date list of Open Caveats, go to:
Table 7. Cisco Nexus Fabric Manager, Release 1.2(2) – Open Caveats
| Record Number |
Bug Headline |
| A fault is created for a switch with "lldp receive" CLI failure |
|
| Applying a filter expression sometimes gives unexpected results |
|
| Changing VRF and removing IP address simultaneously can result in configuration error on the switch |
|
| CLI window sometimes doesn't display all lines of output |
|
| Conflicting foreign device briefly appears |
|
| Django request.session Record Creation Denial of Service Vulnerability |
|
| Interface operational MAC address no longer gets updated |
|
| Interfaces filtered on role "unknown" but tiles show different text |
|
| Logical port channel with interfaces from two switches may not have member interfaces operational |
|
| NFM cannot resolve "CLI execution" faults |
|
| Port channels get rebuilt on monitored to managed mode transition |
|
| Switchpool available VLANs becomes 0 after editing switchpool settings |
|
| Switchpool MTU change causes some members of a vPC to become inactive |
|
| The fault "neighborMismatch" is flooded at times |
|
| Transitioning unconfigured switch to managed may cause some port channels to be improperly deployed |
|
| Updating object memberships seems to show an object being created |
|
| User is allowed to set the same IP address on the same VRF on different interfaces |
Related Documentation
Related documentation for the Cisco Nexus Fabric Manager:
Cisco Nexus Fabric Manager
Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide, Release 7.x
Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 7.x
Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 7.x
Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide, Release 7.x
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments to cnfm-docfeedback@cisco.com. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2015-2016 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)