Dell EMC Abstract

Quick start and interoperability guide to assist with the

Networking OS10 installation, upgrade, and set up of in-band and out-of-
band management, authentication, and interoperability
Enterprise Edition between Dell-Dell and Dell-OEM devices.
Quick Start Guide

1
 
Table of contents 
Installation and upgrades
Management
 Virtual LAN
 Native VLAN
 Spanning Tree
 Port Channels
 Virtual Link Trunk
 Static Route

2
  To begin the installation or upgrade process, ensure that
Installation and the OS10EE image to be installed is acquired and that a
upgrades proper connection to the switch is present. Network
services such as DHCP, TFTP, and FTP, or a USB device,
must be ready to accommodate the process as required.

 The new downloaded OS10EE file will be in a .tar

(archived) format and will need to be unarchived and
the contents copied to an accessible location

 Connect a serial cable and terminal emulator to the

console serial port on the switch. The serial port settings
can be found in the Installation Guide for your switch
model.

3
Installation and
upgrades Dell EMC Networking S4148F-ON front view

Dell EMC Networking S3048-ON front view

Dell EMC Networking S4148F-ON rear view

4
  Connect a serial cable and terminal emulator to the
Installation and console serial port on the switch. The serial port
upgrades settings can be found in the Installation Guide for your
switch model. For example, the S4100-ON serial port
settings are 115200, 8 data bits, and no parity.

 Connect the management port to the network if you

prefer downloading the image over the network. Use
the Installation Guide for your switch model for more
information onsetting up the management port.

 Keep regular backups of switch configurations

somewhere off of the switch, and before performing
OS updates or changes.

5
  A management network allows administrators to
Management remotely access all switches on the network for
configuring, managing, and analyzing traffic. This
prevents having to be physically present at each
switch in order to manage it. There are two
prevalent approaches for network management: in-
band and out-of-band (OOB).

 The method used for management should be

carefully considered when designing a network.
Switches that use in-band management may
become inaccessible if parts of the network are
down, but can take advantage of security features
such as those provided by access control,

6
Management
(Topology)

7
  Each switch managed through OOB requires an IP
Management (Out- address on its OOB port. The exact command for
Of-Band) setting the OOB management port depends on the
switch hardware and operating system.

 Cable the OOB port to connect to the management

network. Use the ping command from a remote
switch or management station to test connectivity to
the switch.

 To quickly verify management access, SSH or telnet

into the switch from a remote device. SSH is enabled
by default on OS10EE. Telnet is disabled by default.

8
  Similar to OOB, in-band may be used for
administrative management (SSH, Telnet, TFTP, etc.)
Management (In- as well as SNMP management, monitoring, and
system logging.
Band)
 One or more ports on a switch may be enabled for
in-band management. A minimum of one port is
necessary for the switch itself to be managed
through the in-band network.

9
  Use the ping command from a remote switch or
management station to test connectivity to the
Management (In- switch’s in-band management port.

Band)  In-band management may also be configured using

a VLAN dedicated for management. An IP address is
assigned to the VLAN on each switch in order to
access the switch.

10
  Using the serial console port is a third method to
managing switches on the network.
Management
(Serial)  It allows administrators to gain access to the switch
on the network while the switch is booting and
allows them to view the boot process.

 The serial port is not an Ethernet port and therefore

cannot be configured with an IP address or accept
SSH.

 Once an administrator uses the serial port to initially

configure a switch, the serial port is generally
considered only as a secondary backup for
management purposes.
11
  A virtual LAN (VLAN) is used to partition the switch into
Virtual LAN two or more logical switches to allow for grouping of
end devices into logical groups. Such groups typically
consist of devices or users running the same
applications.

 Once a VLAN is created, ports may be assigned to it.

End devices connected to these ports can communicate
with each other over this common VLAN.

 To allow devices on a VLAN on one switch to

communicate with devices on the same VLAN on
another switch, a trunk port has to be created between
the two switches. Trunk ports are used to pass VLAN
traffic from one switch to the next, and across the entire
network.

12
Virtual LAN
(Topology)

13
  An interface in trunk mode forwards all VLAN traffic
Native LAN by default. For more control over where traffic goes
on the network, an administrator can restrict a trunk
port to only pass traffic of certain VLANs.

 The default VLAN 1 is the native VLAN for OS10EE.

Use the commands below to change the native VLAN
to a different VLAN.

14
  The Spanning Tree Protocol (STP) in Ethernet networks
Spanning Tree is used to build a loop-free logical topology to prevent
bridge loops which result in broadcast storms.

 Virtually all topologies should implement spanning

tree. When a loop is detected, spanning tree
automatically shuts down an interface or port channel

 There are multiple spanning tree protocols supported

in OS10EE including Rapid Spanning Tree Protocol
(RSTP), Rapid Per-VLAN Spanning Tree+ (RPVST+),
and Multiple Spanning Tree (MST).

15
Spanning Tree
(Topology)

16
  There are several global and port level configuration
Spanning Tree commands for spanning tree. Global commands are
(Levels) used to enable/disable spanning tree on the entire
switch, whereas port level commands are used to
limit or supplement spanning tree features on
individual ports.

 A port level command often used with spanning tree

is the edge command. While in interface
configuration mode, the edge command allows the
devices that are plugged in to not participate in
spanning tree blocking and learning states, and
thereby allows these ports to go immediately into a
forwarding state.

17
  A port channel, also known as a LAG, or link
Port Channels aggregation, increases bandwidth and provides
failover redundancy between two switches.

 The port channel is created using two or more cables

between the devices. Use two cables to double
bandwidth, three cables to triple bandwidth, or four
cables to quadruple bandwidth.

18
  ports with the same speed are a best practice when
Port Channels combining to form the port channel.

 OS10EE supports up to 128 port channels with up to

32 ports (per switch) per channel.

19
  Virtual Link Trunking (VLT) may be used for
Virtual Link Trunk connecting top-of-rack (ToR) switches or leaf
switches in a leaf and pine topology.

20
  Virtual Link Trunking (VLT) offers end devices (such
Virtual Link Trunk as servers) a redundant, load-balancing connection
to the core-network in a loop-free environment.

 The VLT Interconnect (VLTi) is the physical link

(cables and ports) used to form the VLT domain
between the pair of switches.

 For backup destination, use the IP address of the

management interface of the VLT peer switch.

21
  OS10 supports IPv4 addressing including variable-
Static Route length subnetting mask (VLSM), Address Resolution
Protocol (ARP), static routing, and routing protocols.

 You can also use supernetting, which increases the

number of subnets. You can add a mask to the IP
address to separate the network and host portions of
the IP address to add a subnet.

 You need to configure IPv4 routing for IP hosts to

communicate with one another in the same network,
or in different networks.

22
  OS10 installs a static route if the next hop is on a
Static Route directly connected subnet.

 A next-hop that is not on the directly connected

subnet which recursively resolves to a next-hop on
the interface's configured subnet also automatically
configures.

 When the interface goes down, OS10 withdraws the

route. When the interface comes up, OS10 reinstalls
the route.

23