- Preface
- New and Changed Information
- About Cisco Nexus Fabric Manager
- Switch Management
- Foreign Device Management
- Interface Management
- Host-Facing and Border Port Channel Management
- Host-Facing and Border Port Channel Member Management
- Broadcast Domain Management
- Gateway Management
- Tenant VRF Management
- Switch Software Management
- User Management
- Profile Management
- Fault Management
- Rack Management
- Topology Management
- System Management
- Enabling TLS 1.1 or Earlier for the Cisco Nexus Fabric Manager
- System Password Reset
About Cisco Nexus Fabric Manager
This chapter contains the following sections:
- Overview
- Supported Platforms
- Supported Software
- Supported and Unsupported Topologies
- Supported Browsers
- Accessing the Cisco Nexus Fabric Manager
- First-Time Login
- Resetting the Cisco Nexus Fabric Manager System Root Password
- About the GUI
- Extra CLI Commands
Overview
The Cisco Nexus Fabric Manager is a system designed to highly simplify and optimize the full lifecycle management of a switch fabric based on the Cisco Nexus 9000 Series switches. The Cisco Nexus Fabric Manager provides point-and-click methods for performing fabric management tasks such as adding, removing, and configuring network components. The configurable network components include switchpools, switches, switch interfaces, foreign devices (such as hosts), virtual routing and forwarding topologies (VRFs), port channels and broadcast domains.
The Cisco Nexus Fabric Manager user interface leverages an intuitive Navigation menu to easily move between the main functions of the system. The main system functions include switchpools, profiles, faults, racks, VRFs, images, upgrades, and authentication.
The Cisco Nexus Fabric Manager also introduces Auto Fabric Provisioning (AFP), which enables the Cisco Nexus Fabric Manager to manage switches that have not yet received any configuration. Through AFP, you can specify the initial switch configuration using the desired management IP address, username, password, and Cisco NX-OS software release. Your initial configuration is automatically applied to the device before being imported into the switchpool.
For installation information, see the Cisco Nexus Fabric Manager Quick Start Guide. Once the Cisco Nexus Fabric Manager is up and running, you can begin adding and configuring user accounts and network components.
Supported Platforms
The Cisco Nexus Fabric Manager supports the following hardware:
Model |
Product ID |
---|---|
Nexus 9500 |
|
Model |
Product ID |
---|---|
Cisco Nexus 9200 Modules |
|
Model |
Product ID |
---|---|
Cisco Nexus 2348TQ 10GE |
N2K-C2348TQ-10GE |
Cisco Nexus 2348TQ-E 10GE |
N2K-C2348TQ-E |
Cisco Nexus 2348UPQ 10GE |
N2K-C2348UPQ |
Cisco Nexus 2332TQ 10GE |
N2K-C2332TQ-10GT |
Cisco Nexus 2248PQ 10GE |
N2K-C2248PQ |
Cisco Nexus 2248TP GE |
N2K-C2248TP |
Cisco Nexus 2248TP-E |
N2K-C2248TP-E |
Cisco Nexus 2232PP 10GE |
N2K-C2232PP |
Cisco Nexus 2232TM 10GE |
N2K-C2232TM |
Cisco Nexus 2224TP GE |
N2K-C2224TP |
Note | In Cisco Nexus Fabric Manager 1.2(x) releases, the maximum number of supported fabric extenders is four per leaf switch. |
Supported Software
The Cisco Nexus Fabric Manager supports the following software:
-
Cisco NX-OS 7.0(3)I2(2e)
Note
NX-OS patch required.
-
Cisco NX-OS 7.0(3)I2(3) (NXOS patch required)
-
Cisco NX-OS 7.0(3)I2(4)
-
Cisco NX-OS 7.0(3)I2(5)
-
Cisco NX-OS 7.0(3)I3(1)
-
Cisco NX-OS 7.0(3)I4(1)
-
Cisco NX-OS 7.0(3)I4(2)
-
Cisco NX-OS 7.0(3)I4(3)
-
Cisco NX-OS 7.0(3)I4(4)
-
Cisco NX-OS 7.0(3)I4(5)
-
Cisco NX-OS 7.0(3)I4(6)
-
Cisco NX-OS 7.0(3)I5(2)
-
Cisco NX-OS 7.0(3)I6(1)
Supported and Unsupported Topologies
Supported Fabric Topologies
- 2-tier leaf spine architecture
- Border leaf switches
Note
May require a CLI configuration to enable required external routing functionality. - Host-facing and border vPCs are supported and require a physical link between leaf switch pairs to facilitate a vPC peer link.
Note
Leveraging connectivity from leaf-to-spine-to-leaf for a vPC peer link is not currently supported, as this is a current NX-OS restriction.
Unsupported Fabric Topologies
- Border spine switches
- Multi-homed Nexus 2000 (FEX) configurations, as this is a current NX-OS restriction.
- The use of VLAN 1 is not supported as either part of the Cisco Nexus Fabric Manager's managed configuration or as a manual addition to the CLI configuration of any switch. VLAN 1 must remain unused.
Supported Browsers
The Cisco Nexus Fabric Manager supports the browsers listed in the table below.
Browser |
Version |
---|---|
Google Chrome |
Latest regular release |
Mozilla Firefox |
Latest regular release |
Accessing the Cisco Nexus Fabric Manager
After installation, the Cisco Nexus Fabric Manager login window is accessed by entering the Cisco Nexus Fabric Manager IP address in a web browser. When the login window appears, enter your username and password credentials.
Note |
|
First-Time Login
The Cisco Nexus Fabric Manager first-time login credentials are entered by an admin. For the first-time login, enter the default admin username with the password that was specified during the installation.
After logging in successfully, see User Management to change the password and add user accounts.
Resetting the Cisco Nexus Fabric Manager System Root Password
This section explains how to reset the system password for the Cisco Nexus Fabric Manager Release 1.2(1) and earlier and Release 1.2(2) and later.
- Resetting the System Password in Release 1.2(2) and Later
- Resetting the System Password in Release 1.2(1) and Earlier
Resetting the System Password in Release 1.2(2) and Later
This section explains how to reset the system password for Cisco Nexus Fabric Manager Release 1.2(2) and later releases.
Step 1 | Open the vSphere client and log in to the Cisco Nexus Fabric Manager appliance host (root). |
Step 2 | From the vSphere client, right-click on the Cisco Nexus Fabric Manager virtual machine and choose Open Console. |
Step 3 | From the vSphere client, right-click on the Cisco Nexus Fabric Manager virtual machine and choose Power > Restart Guest. When prompted, click Yes to confirm the reboot. |
Step 4 | From to the console window, click the black field (the prompt becomes a dot) and begin pressing the Down Arrow key repeatedly as the Cisco Nexus Fabric Manager VM begins to start up (during the VMware window). The GNU GRUB window will appear. |
Step 5 | Use the Up Arrow and Down Arrow keys to highlight the Cisco NFM Version <Version Number>—Password Recovery option. |
Step 6 | When prompted, enter a new password. When prompted, re-enter the password to confirm. The system will boot normally. |
What to Do Next
After the Cisco Nexus Fabric Manager starts, verify the password change by logging in to root on the console and entering the new password.
Resetting the System Password in Release 1.2(1) and Earlier
This section explains how to reset the system password for Cisco Nexus Fabric Manager Release 1.2(1) and earlier releases.
Step 1 | Open the vSphere client and log in to the Cisco Nexus Fabric Manager appliance host. | ||
Step 2 | From the vSphere client, click the + symbol to open the VM menu. | ||
Step 3 | From the vSphere client, right-click on the Cisco Nexus Fabric Manager virtual machine and choose Open Console. | ||
Step 4 | From the vSphere client, right-click on the Cisco Nexus Fabric Manager virtual machine and choose Power > Restart Guest. When prompted, click Yes to confirm the reboot. | ||
Step 5 | From to the console window, click in the black field (the prompt becomes a dot) and begin pressing the Down Arrow key repeatedly as the Cisco Nexus Fabric Manager VM begins to start up (VMware screen). | ||
Step 6 | When the GNU GRUB window appears, press the e key. | ||
Step 7 | Use the Up Arrow and Down Arrow keys to highlight the option that begins with the word Kernel then press the Enter key. Your cursor is placed at the end of a line with editable text. | ||
Step 8 | Replace the last two words in the line with the word debug and press the Enter key. | ||
Step 9 | From the GNU GRUB window, press the b key to boot. You are taken to a new window with a prompt. | ||
Step 10 | At the prompt, enter the following commands:
# mkdir /mnt/gentoo ; mount /dev/sda2 /mnt/gentoo # /mnt/gentoo/rootfs/usr/local/bin/RecoverRootPassword.sh | ||
Step 11 | When prompted, enter the new password. After entering the password, you are prompted to re-enter the password for confirmation.
|
What to Do Next
After the Cisco Nexus Fabric Manager starts, verify the password change by logging in to root on the console and entering the new password.
About the GUI
The Cisco Nexus Fabric Manager is divided into groups of related function windows that enable you to access and manage different network components. You move between the function windows using the Navigation menu icon. Some function windows also have a Settings drop-down menu icon. The Settings drop-down menu contains options that pertain only to the components of the window you have open. The components, such as switches, foreign devices, broadcast domains, interfaces, profiles, and user accounts, are displayed in the function windows as tiles. Each function window that displays tiles also contains an Actions bar, which is used to filter your tiles. This section describes the menu and tile icons and provides an overview for filtering your component tiles.
Understanding the Icons
This section provides a brief overview of the commonly used icons in the Cisco Nexus Fabric Manager interface.
Filtering Your Component Icons
All of the function windows with tiles or topology nodes contain an Actions bar, which enables you to filter and sort your tiles and the foreign device topology nodes. The Actions bar filter options differ depending on the window you are accessing. This section provides a general overview of the various filter options that are available.
Extra CLI Commands
The following explains how the extra CLI commands configuration within switch objects and profiles are implemented in the Cisco Nexus Fabric Manager. The following steps outline when CLI configuration that is entered via the Extra CLI commands field is installed in a newly imported switch:
-
AFP bootstrapping of switches (if switches are imported via AFP).
-
Switches are imported into the switch pool in monitored state.
-
Switches are moved into managed state.
-
Extra CLI commands are pushed to the switches.
-
A Cisco Nexus Fabric Manager generated configuration for the underlay and overlay are pushed to the switches.
-
Note | In Cisco Nexus Fabric Manager Release 1.3(1), new CLI command fields within switch objects, called Pre-provisioning and Post-provisioning CLI, are introduced in section /fill in section here/. They are prefix and suffix configuration that are appended to the staging configuration as part of the AFP bootstrapping of switches in step 1" |
For switches that are already imported and in managed mode, the following outlines how changes to the Extra CLI commands section are pushed to the switch:
-
Saving a change to the Extra CLI commands section in a switch modal.
-
Saving a change in a switch profile modal.
-
When a switch becomes reachable after being unreachable.
-
When transitioning a switch from monitored to managed.
How do you know when the configuration has been applied?
-
Go to the switch object Details window, scroll to the CLI COMMANDS section and verify a configuration change was recently pushed. To verify that specific commands were accepted by the switch, bring up the switch CLI and verify the running configuration.
No command syntax validation is done by the Cisco Nexus Fabric Manager. When erroneous extra CLI commands are applied, a switch object fault is generated in response to the switch generated errors.
The Cisco Nexus Fabric Manager does not trigger a reboot when extra CLI commands are applied. If you have a command that requires a reboot, the reboot must to be done manually.
Note | When removing commands from the Extra CLI Command section or disabling the section, CLI commands added by the feature are not removed from the switches themselves. These commands can either be removed at the switch CLI or by entering the required CLI commands to remove configuration (eg. prefix commands with no) and save these to the Extra CLI Commands section. Keep in mind the simple no prefix might not remove all added CLI configuration. Refer to the NX-OS configuration guides for the required syntax. |