Specifications

Using Secure Shell 2
ExtremeWare XOS 11.0 Concepts Guide 47
Connecting to Another Host Using TFTP
You can TFTP from the current CLI session to another host using the following command:
tftp [<host_name> | <ip_address>] {-v <vr_name>} [-g | -p] [{-l <local_file>} {-r
<remote_file>} | {-r <remote_file>} {-l <local_file>}]
The TFTP session defaults to port 69.
For example, to connect to a remote TFTP server with an IP address of 10.123.45.67 and “get” or retrieve
an ExtremeWare XOS configuration file named XOS1.cfg from that host, use the following command:
tftp 10.123.45.67 -g -r XOS1.cfg
When you “get” the file via TFTP, the switch saves the file to the primary MSM. If the switch detects a
backup MSM in the running state, the file is replicated to the backup MSM.
To view the files you retrieved, enter the ls command at the command prompt.
Using Secure Shell 2
Secure Shell 2 (SSH2) is a feature of ExtremeWare XOS that allows you to encrypt Telnet session data
between a network administrator using SSH2 client software and the switch or to send encrypted data
from the switch to an SSH2 client on a remote system.
Up to eight active SSH2 sessions can run on the switch concurrently.
For detailed information about SSH2, see Chapter 10, “Security.”
System Redundancy
If you install two MSMs in the chassis, one assumes the role of master (primary) and the other assumes
the role of backup. The master MSM provides all of the switch management functions including
bringing up and programming the I/O modules, running the bridging and routing protocols, and
configuring the switch. The master MSM also synchronizes the backup MSM in case it needs to take
over the management functions if the master MSM fails.
Table 10 describes the terms associated with system redundancy.
Table 10: System redundancy terms
Term Description
Active
configuration
The configuration currently running on the switch is the active configuration. This configuration
can be different from the last saved configuration.
Backup The backup MSM receives checkpoint data from the master and waits for a failover to occur.
Checkpointing The process of automatically copying the active state from the master to the backup that allows
for state recovery if the master fails.
Device Manager The Device Manager runs on every node and is responsible for monitoring and controlling all of
the devices in the system.
Failover The operation that occurs when the master MSM passes control over to the current backup
MSM.