Install the Reference Configuration File (RCF)
You can install the RCF after setting up the Nexus 92300YC switch for the first time.
The examples in this procedure use the following switch and node nomenclature:
-
The names of the two Cisco switches are
cs1
andcs2
. -
The node names are
node1
andnode2
. -
The cluster LIF names are
node1_clus1
andnode1_clus2
for node1 andnode2_clus1
andnode2_clus2
for node2. -
The
cluster1::*>
prompt indicates the name of the cluster. -
The cluster ports on each node are named
e0a
ande0b
.See the Hardware Universe^ for the actual cluster ports supported on your platform.
-
The Inter-Switch Links (ISLs) supported for the Nexus 92300YC switches are ports 1/65 and 1/66.
-
The node connections supported for the Nexus 92300YC switches are ports 1/1 through 1/66.
-
The examples in this procedure use two nodes. These nodes use two 10GbE cluster interconnect ports
e0a
ande0b
. See the Hardware Universe to verify the correct cluster ports on your platforms.
-
You must have the current RCF.
-
The cluster must be fully functioning (there should be no errors in the logs or similar issues).
-
You must have checked or set your desired boot configuration in the RCF to reflect the desired boot images if you are installing only NX-OS and keeping your current RCF version.
-
If you need to change the boot configuration to reflect the current boot images, you must do so before reapplying the RCF so that the correct version is instantiated on future reboots.
-
You must have consulted the switch compatibility table on the Cisco Ethernet switch page for the supported ONTAP, NX-OS, and RCF versions.
-
There can be command dependencies between the command syntax in the RCF and that found in versions of NX-OS.
The procedure requires the use of both ONTAP commands and Cisco Nexus 9000 Series Switches commands; ONTAP commands are used unless otherwise indicated.
The command outputs might vary depending on different releases of ONTAP.
-
Connect the cluster switch to the management network.
-
Use the ping command to verify connectivity to the server hosting the RCF.
This example verifies that the switch can reach the server at IP address 172.19.2.1:
cs2# ping 172.19.2.1 Pinging 172.19.2.1 with 0 bytes of data: Reply From 172.19.2.1: icmp_seq = 0. time= 5910 usec.
-
Copy the RCF to the Nexus 92300YC switch:
cs2# copy sftp: bootflash: vrf management Enter source filename: /code/Nexus_92300YC_RCF_v1.0.2.txt Enter hostname for the sftp server: 172.19.2.1 Enter username: user1 Outbound-ReKey for 172.19.2.1:22 Inbound-ReKey for 172.19.2.1:22 user1@172.19.2.1's password: sftp> progress Progress meter enabled sftp> get /code/Nexus_92300YC_RCF_v1.0.2.txt /bootflash/nxos.9.2.2.bin /code/Nexus_92300YC_R 100% 9687 530.2KB/s 00:00 sftp> exit Copy complete, now saving to disk (please wait)... Copy complete.
-
Merge the RCF with the running-config of the switch:
cs2# copy bootflash:Nexus_92300YC_RCF_v1.0.2.txt running-config Disabling ssh: as its enabled right now: generating ecdsa key(521 bits)...... generated ecdsa key Enabling ssh: as it has been disabled this command enables edge port type (portfast) by default on all interfaces. You should now disable edge port type (portfast) explicitly on switched ports leading to hubs, switches and bridges as they may create temporary bridging loops. Edge port type (portfast) should only be enabled on ports connected to a single host. Connecting hubs, concentrators, switches, bridges, etc... to this interface when edge port type (portfast) is enabled, can cause temporary bridging loops. Use with CAUTION Edge Port Type (Portfast) has been configured on Ethernet1/1 but will only have effect when the interface is in a non-trunking mode. ... Copy complete, now saving to disk (please wait)... Copy complete.
-
Verify on the switch that the RCF has been merged successfully:
show running-config
cs2# show running-config !Command: show running-config !Running configuration last done at: Wed Apr 10 06:32:27 2019 !Time: Wed Apr 10 06:36:00 2019 version 9.2(2) Bios:version 05.33 switchname cs2 vdc cs2 id 1 limit-resource vlan minimum 16 maximum 4094 limit-resource vrf minimum 2 maximum 4096 limit-resource port-channel minimum 0 maximum 511 limit-resource u4route-mem minimum 248 maximum 248 limit-resource u6route-mem minimum 96 maximum 96 limit-resource m4route-mem minimum 58 maximum 58 limit-resource m6route-mem minimum 8 maximum 8 feature lacp no password strength-check username admin password 5 $5$HY9Kk3F9$YdCZ8iQJ1RtoiEFa0sKP5IO/LNG1k9C4lSJfi5kesl 6 role network-admin ssh key ecdsa 521 banner motd # * * * Nexus 92300YC Reference Configuration File (RCF) v1.0.2 (10-19-2018) * * * * Ports 1/1 - 1/48: 10GbE Intra-Cluster Node Ports * * Ports 1/49 - 1/64: 40/100GbE Intra-Cluster Node Ports * * Ports 1/65 - 1/66: 40/100GbE Intra-Cluster ISL Ports * * *
-
Save the running configuration so that it becomes the startup configuration when you reboot the switch:
cs2# copy running-config startup-config [] 100% Copy complete, now saving to disk (please wait)... Copy complete.
-
For ONTAP 9.6P8 and later, enable the Ethernet switch health monitor log collection feature for collecting switch-related log files, using the commands:
system cluster-switch log setup-password
andsystem cluster-switch log enable-collection
cluster1::*> system cluster-switch log setup-password Enter the switch name: <return> The switch name entered is not recognized. Choose from the following list: cs1 cs2 cluster1::*> system cluster-switch log setup-password Enter the switch name: cs1 RSA key fingerprint is e5:8b:c6:dc:e2:18:18:09:36:63:d9:63:dd:03:d9:cc Do you want to continue? {y|n}::[n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system cluster-switch log setup-password Enter the switch name: cs2 RSA key fingerprint is 57:49:86:a1:b9:80:6a:61:9a:86:8e:3c:e3:b7:1f:b1 Do you want to continue? {y|n}:: [n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system cluster-switch log enable-collection Do you want to enable cluster log collection for all nodes in the cluster? {y|n}: [n] y Enabling cluster switch log collection. cluster1::*>
-
Reboot the switch and verify that the running configuration is correct:
reload
cs2# reload This command will reboot the system. (y/n)? [n] y