Reset Search
 

 

Article

S-Series module not joining chassis with error: The legacy module in slot X cannot run in V2 compatibility mode.

« Go Back

Information

 
TitleS-Series module not joining chassis with error: The legacy module in slot X cannot run in V2 compatibility mode.
Symptoms
  • S-Series module not joining chassis with error: The legacy module in slot X cannot run in V2 compatibility mode.
  • Example of error seen on chassis:
<3>System[4]The legacy module in slot X cannot run in V2 compatibility mode.
Environment
  • S-Series
  • 08.xx firmware
  • S140 / S180 / S130 / S150 / S155 Class hardware
Cause
S140/S180 Fabric Modules do not operate with S130/S150/S155 I/O modules installed without changing compatibility mode
Resolution
Compatibility mode must be changed to V1 compatibility mode with the following command (Requires reboot of chassis):
set chassis compatibility-mode v1

Compatibility mode explained:
Compatibility mode establishes the type of signaling that will be used on the backplane between modules. It affects the way the S180 fabric operates (fixed vs variable cells and no bonding header vs bonding header). Compatibility mode version one (v1) must be used whenever the chassis has a legacy S130/S150/S155 card installed. Compatibility mode version two (v2) should be used when all of the modules are 140/S180 class.

By default compatibility mode is automatically established upon first boot up of 7.99.06 or greater 7.99 images (factory images) and 8.11 FW and newer, or any time the configuration is lost (clear config, switch 7 on all fabrics, all new fabrics) or the following commands are issued clear chassis compatibility, ‘set chassis compatibility auto [chassis-id]’.
The automatic assignment occurs once at boot time and when established the operational compatibility mode will be sticky and persist through various HW changes, or until the configuration is manually changed or cleared. (Chassis-id may be omitted on systems with bonding disabled and will default to chassis1 on bonding systems.)
There are several reasons a compatibility setting would need to be manipulated.

1. If an existing S180 class chassis has an S130 or S150 I/O module added, the chassis compatibility mode will need to change from v2 to v1. The S130/S150 I/O module will be prevented from joining the system until the compatibility mode is set to v1 for the chassis. 

2. If a combined HW class chassis has all of the legacy S130/S150 class HW removed the compatibility setting should be manually changed to v2. When configured in v2 mode the fabrics run with different signaling. When possible the HW should be configured in v2mode. 

3. VSB considerations: Each physical chassis operates with its own compatibility setting. When selecting the appropriate compatibility mode setting you must consider the HW population of the individual physical chassis participating in the bond. (not the logical combined bonded chassis) a. If a S140/S180 only chassis is to be bonded to a S150/S155/S130 chassis the S140/S180 should have a compatibility setting of v2 and the S150/S155/S130 class chassis will have a v1 setting. 
b. A similar consideration must be made when a S3-S130 class chassis is to bond to a S3-S140 chassis. The compatibility setting for the S3-S140 should be v2 and the S130-S3 will use the v1 setting.
 

 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255