|
Feature |
Product |
Release introduced |
|---|---|---|
|
Linux kernel version Important:
For VSP 4450 Series, VSP 7200 Series, VSP 8200, and VSP 8400 Series, kernel version 4.9 has special upgrade considerations the first time you upgrade to a release that supports it. You must first upgrade to a stepping-stone release, 6.1.x , before you upgrade to the release with the new kernel. |
5420 Series |
4.14 as of VOSS 8.4 |
|
5520 Series |
4.14 as of VOSS 8.2.5 |
|
|
VSP 4450 Series |
4.9 as of VOSS 7.0 |
|
|
VSP 4900 Series |
4.14 as of VOSS 8.1 |
|
|
VSP 7200 Series |
4.9 as of VOSS 7.0 |
|
|
VSP 7400 Series |
4.14 as of VOSS 8.0 |
|
|
VSP 8200 Series |
4.9 as of VOSS 7.0 |
|
|
VSP 8400 Series |
4.9 as of VOSS 7.0 |
|
|
VSP 8600 Series |
4.9 as of VSP 8600 8.0 |
|
|
XA1400 Series |
4.14 as of VOSS 8.1 |
The switch goes through a boot sequence before it becomes fully operational. After you turn on power to the switch, the system starts.
The boot sequence consists of the following stages:
Note
Extreme Networks offers universal hardware products that support more than one Network Operating System (NOS) personality. The first time you start a universal hardware product, the boot sequence can be different from what is documented in this section. The boot sequence documented in this section assumes a NOS selection of VOSS is already established. For more information on NOS personalities, see Network Operating System Personalities.
The following figure shows a summary of the boot sequence.
Depending on the Linux kernel used, the boot image is stored either in a boot flash partition, Secure Digital (SD), or Solid State Drive (SSD) flash card. The boot image includes the boot loader, and the Linux kernel and applications.
The boot location contains two versions of the boot image: a committed version (the primary release) and a backup version. A committed version is one that is marked as good (if you can start the system using that version). The system automatically uses the backup version if the system fails the first time you start with a new version.
The switch can install a maximum of six releases but can only load one of two—a primary (committed) release or a backup release.
Note
You can store up to six software releases on the 5520 Series. If you have six releases already stored on the switch, you are prompted to remove one release before you can proceed to add and activate a new software release. You can store a maximum of two software releases on the 5420 Series. If you attempt to add a third software release, the software displays a confirmation to overwrite the non-primary release. You can also use the software add <filename> -y to bypass the confirmation question and automatically overwrite the non-primary release.
The system saves software image files to the /intflash/release/ directory.
After loading the primary release, the CPU and basic system devices, such as the console port, initializes. Depending on the hardware platform, the console port displays as console or 10101. At this stage, the I/O ports are not available; the system does not initialize the I/O ports until the port sends configuration data.
Important
Zero Touch Deployment does not function if primary or secondary configuration files exist.After the system loads the primary release and the switch is in a Zero Touch Deployment-ready configuration mode, the switch automatically deploys without intervention.
For more information, see Zero Touch Deployment.
After the system loads the primary release, it identifies the location and file name of the primary configuration file. You can save this file in internal flash.
If the primary configuration file does not exist, the system looks for the backup configuration file, as identified by version.cfg. If this file does not exist, the system initiates Zero Touch functionality on the switch that enables Zero Touch Fabric Configuration. For more information, see Zero Touch Fabric Configuration.
Note
Exception: for VSP 8600 Series and XA1400 Series, if the configuration file does not exist, the system loads the factory-default configuration, which is the equivalent of using the boot config flags factorydefaults command.
The switch configuration consists of higher-level functionality, including:
Chassis configuration
Port configuration
Virtual LAN (VLAN) configuration
Routing configuration
IP address assignments
Remote monitoring (RMON) configuration
The default switch configuration in Zero Touch Fabric Configuration mode includes the following:
Shortest Path Bridging MAC (SPBM) instance is created.
Intermediate System-to-Intermediate System (IS-IS) is enabled.
All ports are enabled and operating in Auto-sense mode.
The switch issues DHCP requests on the out-of-band (OOB) management port and the management VLAN.
The default switch configuration in factory default mode includes the following:
A single, port-based default VLAN with a VLAN identification number of 1
No interface assigned IP addresses
Traffic priority for all ports configured to normal priority
All ports as untagged ports
Default communication protocol settings for the console port. For more information about these protocol settings, see System Connections.
In the configuration file, statements preceded by both the number sign (#) and exclamation point (!) load prior to the general configuration parameters. Statements preceded by only the number sign are comments meant to add clarity to the configuration; they do not load configuration parameters. The following table illustrates the difference between these two statement formats.
|
Sample statement |
Action |
|---|---|
|
# software version : 4.0.0.0 |
Adds clarity to the configuration by identifying the software version. |
|
#!no boot config flags sshd |
Configures the flag to the false condition, prior to loading the general configuration. |
You can change the boot sequence in the following ways:
Change the primary designations for file sources.
Change the file names from the default values. You can store several versions of the configuration file and specify a particular one by file name. The specified configuration file only gets loaded when the chassis starts. To load a new configuration file, you need to restart the system.
Start the system without loading an existing configuration file so that the system uses the factory default configuration. You can do this by running the boot config flags factorydefaults command.
The factorydefaults boot flag removes the runtime, primary, and backup configuration files, resets all local default user account passwords, and removes all digital certificates. The Radsec, IPsec, IKE, OSPF, SNMP, SSL, SSH, OVSDB, and NTP files are also removed. The CLI displays a warning that the configurations, passwords, and files will be reset, and the system logs an informational message. The configuration and file removals occur during the next boot sequence when the factorydefaults boot flag is enabled. After the switch reboots, the security mode setting is retained. To enable Zero Touch Onboarding after a factorydefaults boot, reboot the switch again without saving a configuration.
Start the system in Zero Touch Deployment mode, which includes Zero Touch Fabric Configuration. For more information, see Zero Touch Deployment.
After the switch is operational, you can use the runtime commands to perform configuration and management functions necessary to manage the system. These functions include the following
Resetting or restarting the switch
Adding, deleting, and displaying address resolution protocol (ARP) table entries
Pinging another network device
Viewing and configuring variables for the entire system and for individual ports
Configuring and displaying MultiLink Trunking (MLT) parameters
Creating and managing port-based VLANs or policy-based VLANs
To access the runtime environment you need a connection from a PC or terminal to the switch. You can use a direct connection to the switch through the console port or remotely through Telnet, rlogin, or Secure Shell (SSH) sessions.
Note
rlogin is only supported on VSP 8600 Series.
Important
Before you attempt to access the switch using one of the preceding methods, ensure you first enable the corresponding daemon flags.