Professional Documents
Culture Documents
1
Table Of Contents
CLI Commands
Switch CLI validation commands
Return to Full Switch mode
CLI Commands
CLI Commands
This section provides a list of the most common commands and their output for the
examples used in this guide. These examples are from the final topology with two
VxRail clusters deployed, as shown in the SmartFabric topology with connections to
VxRail nodes and external network figure.
General commands
show version
Leaf and spine switches must be running a supported version of SmartFabric OS10.
Run the show version command to check the operating system version. SmartFabric
OS10 is available on Dell Digital Locker (account required).
Note: See the Dell Networking Support & Interoperability Matrix for supported
versions..
Run the command show license status to verify license installation. The License
Type: field should indicate PERPETUAL. If an evaluation license is installed,
licenses purchased from Dell are available for download on Dell Digital Locker.
Installation instructions are provided in the Dell SmartFabric OS10 User Guide on
Dell Networking OS10 Info Hub.
CLI Commands
Leaf1A# show license status
System Information
---------------------------------------------------------
Vendor Name : Dell EMC
Product Name : S5248F-ON
Hardware Version : A01
Platform Name : x86_64-dellemc_s5248f_c3538-r0
PPID : CN046MRJCES0089K0015
Service Tag : 690ZZP2
Product Base :
Product Serial Number:
Product Part Number :
License Details
----------------
Software : OS10-Enterprise
Version : 10.5.4.4
License Type : PERPETUAL
License Duration: Unlimited
License Status : Active
License location: /mnt/license/690ZZP2.lic
---------------------------------------------------------
The show interface status | grep up command is used to verify required interfaces
are up, and links are established at their appropriate speeds. In this example, ports
1/1/1-1/1/4 are VxRail nodes, port 1/1/9:1 is a jump host, ports 1/1/49-1/1/52 are the
VLTi, ports 1/1/53-1/1/54 are uplinks to the external network, and ports 1/1/55-1/1/56
are uplinks to the spines.
CLI Commands
Eth 1/1/52 up 100G full -
Eth 1/1/53 up 100G full -
Eth 1/1/54 up 100G full -
Eth 1/1/55 up 100G full -
Eth 1/1/56 up 100G full -
The show port-channel summary command is used to view port channel numbers,
interfaces used, and status. Port channel 1 (number may vary) is the L2 uplink to the
external network, if used. Port channels 96 through 97 (numbers may vary) are
automatically created spine uplinks. The VLTi is automatically configured as a static
LAG using port channel 1000. Ports 1/1/53 and 1/1/54 are port channel members,
and (P) indicates each is up and active.
The show virtual network command is used to view virtual networks, VLANs, and
interfaces assigned to each VLAN. Port channel 1 (number may vary) is the L2
uplink to the external network if configured. Port channel 1000 is the VLTi. Interfaces
1/1/1-1/1/3 are connected to the VxRail nodes in the first cluster. Interface 1/1/4 is
connected to the VxRail node in the second cluster. Interface 1/1/9:1, shown under
VLAN 1811, is the jump host port.
Note: The jump host port was moved from VLAN 4091 to VLAN 1811 during VxRail
deployment.
CLI Commands
Virtual Network: 1811
VLTi-VLAN: 1811
Members:
Untagged: ethernet1/1/9:1
VLAN 1811: port-channel1, port-channel1000, ethernet1/1/1, ethernet1/1/2, ethern
et1/1/3, ethernet1/1/4
VxLAN Virtual Network Identifier: 1811
Source Interface: loopback2(172.30.0.0)
Remote-VTEPs (flood-list): 172.30.0.3(CP)
CLI Commands
VLTi-VLAN: 1822
Members:
VLAN 1822: port-channel1000, ethernet1/1/4
VxLAN Virtual Network Identifier: 1822
Source Interface: loopback2(172.30.0.0)
Remote-VTEPs (flood-list): 172.30.0.3(CP)
CLI Commands
VLTi-VLAN: 4091
Members:
Untagged: ethernet1/1/1, ethernet1/1/2, ethernet1/1/3, ethernet1/1/4
VLAN 4091: port-channel1000
VxLAN Virtual Network Identifier: 4091
Source Interface: loopback2(172.30.0.0)
Remote-VTEPs (flood-list): 172.30.0.1(CP),172.30.0.2(CP),172.30.0.3(CP)
The show lldp neighbors command is useful for identifying connected equipment.
Interfaces 1/1/1-4 are connected to the VxRail nodes, and Interface 1/1/9:1 is
connected to the jump host. Interfaces 1/1/53-54 are connected to the external
network, and 1/1/55-56 are connected to the spines. Mgmt1/1/1 is connected to the
OOB management switch.
Note: If an entry is not shown for the jump host, port 1/1/9:1 in the above example,
the jump host may be connected to the other leaf switch, or the NIC on the jump host
CLI Commands
does not have LLDP enabled. This is not required and may be ignored.
Run the show ip interface brief command to verify connected interfaces are up, and
IP addresses are configured correctly.
In the output below, interfaces 1/1/1-1/1/4 are connected to the VxRail nodes, 1/1/49-
1/1/52 are the VLTi, 1/1/53-1/1/54 are L3 uplinks to the external switches, and
1/1/55-1/1/56 are connections to the Spine switches. IP addresses assigned to
VLANs 4000-4094 and Loopback interfaces are for SFS internal use. The remaining
IP addresses shown are configured in the steps in this guide. VLAN 4090, Loopback
1, and Loopback 2 are automatically configured by SFS. VLAN 4090 is used for
iBGP, Loopback 1 is the router ID, and Loopback 2 is the VTEP IP address.
Note: Unused interfaces have been removed from the output for brevity.
CLI Commands
Virtual-network 1811 172.18.11.253/24 YES manual up up
Virtual-network 3939 unassigned YES unset up up
Run the show ip bgp summary command to verify that BGP is up for each neighbor.
When BGP is up, uptime is shown in the Up/Down column. The neighbors for Leaf1A
shown in the output below are Leaf1B, External-A, and External-B.
show ip route
With L3 uplinks, the show ip route command is used to ensure the leaf switches
have routes to the external network, 172.19.11.0/24 in this example, to reach the
DNS server. This BGP-discovered route is shown in the output below.
10
CLI Commands
B EX 172.16.0.14/31 via 172.16.0.5 20/0 20:01:20
via 172.16.0.9
B EX 172.16.0.16/31 via 172.16.0.5 20/0 21:05:24
B EX 172.16.0.18/31 via 172.16.0.9 20/0 19:57:31
C 172.16.128.0/32 via 172.16.128.0 loopback1 0/0 23:56:45
B IN 172.16.128.1/32 via 172.16.0.1 200/0 20:58:03
B EX 172.16.128.2/32 via 172.16.0.5 20/0 21:05:24
B EX 172.16.128.3/32 via 172.16.0.9 20/0 19:57:31
B EX 172.16.128.4/32 via 172.16.0.5 20/0 20:01:20
via 172.16.0.9
B EX 172.16.128.5/32 via 172.16.0.5 20/0 20:01:20
via 172.16.0.9
C 172.18.11.0/24 via 172.18.11.253 virtual-network1811 0/0 22:03:09
B EX 172.19.11.0/24 via 192.168.1.0 20/0 23:22:36
via 192.168.2.0
C 172.30.0.0/32 via 172.30.0.0 loopback2 0/0 23:56:48
B EX 172.30.0.1/32 via 172.16.0.5 20/0 21:05:24
B EX 172.30.0.2/32 via 172.16.0.9 20/0 19:57:31
B EX 172.30.0.3/32 via 172.16.0.5 20/0 20:01:20
via 172.16.0.9
C 192.168.1.0/31 via 192.168.1.1 ethernet1/1/53 0/0 23:23:39
B IN 192.168.1.2/31 via 172.16.0.1 200/0 20:58:03
C 192.168.2.0/31 via 192.168.2.1 ethernet1/1/54 0/0 23:22:54
B IN 192.168.2.2/31 via 172.16.0.1 200/0 20:58:03
VLT commands
show vlt domain_id
11
CLI Commands
Delay-Restore timer : 90 seconds
Peer-Routing : Disabled
Peer-Routing-Timeout timer : 0 seconds
Multicast peer-routing timer : 300 seconds
VLTi Link Status
port-channel1000 : up
This command is used to verify VLT peers are communicating on the backup link
over the OOB management network. The Destination is the management IP address
of the peer. The Peer Heartbeat status must be Up.
This command highlights any potential configuration issues between VLT peers. All
items must indicate No mismatch.
Peer-routing mismatch:
No mismatch
VLAN mismatch:
No mismatch
12
CLI Commands
VLT Virtual Network Mismatch:
Virtual Network Name Mismatch:
No mismatch
EVPN Mismatch:
EVPN Mode Mismatch:
No mismatch
NVE Mismatch:
No mismatch
13
CLI Commands
Codes: SE - Static Entry Mismatch
DT - DAI Trust Mismatch
ST - Snooping Trust Mismatch
SAV - Source-Address-Validation Mismatch
ARP - ARP Inspection Mismatch
VS - VLAN Snooping Mismatch
Interface Interface Snooping Configuration Mismatch
---------------------------------------------------------------------
Multicast routing mismatches:
Global status:
Parameter VRF Local Peer
---------------------------------------------------------------------
No mismatch
To delete the existing switch configuration and go from SmartFabric mode back to
Full Switch mode, run the following commands on each switch:
The switch reboots into Full Switch mode. The mode can be verified with the
following command:
14
CLI Commands