There are currently two generations of S-Series fabric module. The S-Series S130, S150, and S155 modules belong to the first generation. For the remainder of this discussion, this module grouping is identified as S130/150/155. The second generation consists of the S-Series S140 and S180 modules. This module grouping is identified as S140/180. These two fabric generations have capability differences that are not compatible with each other. Where allowed, mixed systems will modify the capabilities of the S140/180 modules. You need to be aware of the supported configurations for these two S-Series fabric generations when installing modules into an S-Series physical chassis. Once a supported module configuration is determined, an appropriate compatibility mode must be set to assure that all module configurations operate at supported levels.
The two S-Series fabric versions are not compatible. Both fabric module versions can not be installed in a mixed configuration on the same physical chassis. You can mix versions of I/O modules in the same chassis, but if an S140/180 I/O module exists in the chassis, only S180 fabric modules can be installed in that chassis.
There are two exception to mixing I/O version modules in the same chassis:
Once S-Series version module restrictions are met, you must assure that an appropriate compatibility mode is configured for the system. There are three compatibility mode settings: auto, v1, and v2.
Auto compatibility mode: When configured, the auto fabric compatibility mode actively determines the appropriate V1 or V2 setting for the system only when booting for the first time in a cleared (default) configuration state. Based upon the hardware installed at boot time, the appropriate fabric compatibility mode is operationally set and persists across subsequent system boots. If subsequent hardware changes occur requiring a module compatibility mode change, the module compatibility mode does not get changed, and any new hardware not appropriate to the current operational compatibility mode remains non-operational upon system boot. If changes that are not compatible with the current configuration occur subsequent to an initial auto compatibility mode boot, the appropriate v1 or v2 compatibility mode must be administratively entered, unless an action has occurred that causes the auto setting to be reset to its initial state.
The auto compatibility mode is in its initial state under the following conditions:
Note
Chassis compatibility mode defaults to auto. You do not need to modify this default setting so long as you either do not modify the module configuration in the chassis or the modification of the module configuration is appropriate to the current operational chassis compatibility mode. The current operational chassis compatibility mode is displayed in the show chassis compatibility-mode command output.When displaying chassis compatibility mode information, the display indicates both the admin setting and the operational setting. In auto compatibility mode, the admin display field will display auto. The operational setting will display the compatibility mode that auto mode selected during a clear config system boot: either v1 or v2. When in admin auto compatibility mode, use the show chassis compatibility-mode command to determine the selected operational chassis compatibility mode.
V1 compatibility mode: V1 compatibility mode is specified for chassis that have only S130/150/155 modules installed or for chassis with supported mixed version modules installed. See Fabric and I/O Module Restrictions for restrictions associated with mixed version module configurations. S140/180 modules in a mixed configuration operate at a modified capability level in order to co-exist with the S130/150/155 modules installed in the chassis.
V2 compatibility mode: V2 compatibility mode is specified for chassis that have only S140/180 modules. Should an S130/150/155 module be present when the operational compatibility mode is set to v2, the S130/150/155 modules will not become active.
Note
When administratively changing the compatibility mode to a mode that will change the current operational compatibility mode an appropriate warning displays and the system resets.There are two possible operational modes when installing S-Series modules: v1 and v2. S130/150/155 modules can only operate in v1 mode. S140/180 modules are capable of operating in v1 mode with modified capabilities, allowing compatible operation with S130/150/155 modules, or in v2 mode taking full advantage of the module‘s capabilities. You can determine the compatibility mode capabilities of an installed S-Series module using the show chassis compatibility-mode capabilities command.
Hardware interconnect ports can only be used if both chassis are set to v2 compatibility mode. Software assisted connectivity ports must be used if either physical chassis compatibility mode is set to v1.
See VSB Interconnect Link Configuration for a bonding mode and interconnect port discussion.
This example shows how to set the chassis compatibility mode for chassis index 1 with a mixed configuration to auto:
System(rw)->set chassis compatibility-mode auto System(rw)->show chassis compatibility-mode chassis-index 1 Chassis Index: 1 Current Fabric Compatibility Admin Mode: auto
Current Fabric Compatibility Oper Mode: v1
This example shows how to set the chassis compatibility mode for chassis index 2 containing all S180 modules to v2:
System(rw)->set chassis compatibility-mode v2 chassis-index 2 System(rw)->show chassis compatibility-mode chassis-index 2 Chassis Index: 2 Current Fabric Compatibility Admin Mode: v2 Current Fabric Compatibility Oper Mode: v2
Print
this page
Email this topic
Feedback
View PDF
Download EPUB