Once the first Fabric Interconnect is configured, the secondary Fabric Interconnect requires very minimum configuration. It will detect the primary Fabric Interconnect through the L1/L2 connections and pull the remaining configuration from it. To configure the second Fabric Interconnect, connect its console using a serial connection. Configure the Fabric Interconnect using the following steps:
- Choose the installation method:
Enter the installation method (console/gui)? Console
- If the physical cabling is done accurately, the secondary Fabric Interconnect will automatically be detected. Type y to configure it as secondary:
Installer has detected the presence of a peer switch.
This switch will be added to the cluster. Continue?[y/n] y
- Use the same password as configured for the primary Fabric Interconnect:
Enter the admin password of the peer switch: password
- Enter the management IP address:
Mgmt0 IPv4 address: 172.16.1.11
- Enter the subnet mask:
Mgmt0 IPv4 netmask: 255.255.255.0
- Save the configuration:
Apply and save the configuration (select 'no' if you
want to re-enter)? (yes/no): yes
Note that the number of configuration steps for the secondary Fabric Interconnect is far less than that for the primary Fabric Interconnect. The secondary Fabric Interconnect automatically acquires all the configuration information from the primary Fabric Interconnect.
If the Fabric Interconnect was initially configured as standalone (a POC deployment), it can be converted to be a cluster-aware configuration using the following steps.
Connect to the Fabric Interconnect using the serial console or SSH connection. Once connected, apply the following commands:
- Connect to the CLI local management interface:
FI-A# connect local-mgmt
- Type in enable cluster with the shared cluster IP:
FI-A(local-mgmt)# enable cluster 172.16.1.12
- Type in yes to configure clustering. Note that once a standalone Fabric Interconnect is converted to a cluster, it cannot be converted back to the standalone state:
This command will enable cluster mode on this setup.
You cannot change it back to stand-alone. Are you sure you
want to continue? (yes/no) : yes
- Once the standalone Fabric Interconnect is converted to the primary cluster peer, configure the second Fabric Interconnect following the same steps but for the secondary Fabric Interconnect.