Understanding I-Fabric Component IDs

Addition and removal of I-Fabric components is based on a device ID scheme. Understanding the ID scheme will help you to effectively add and remove components within the I-Fabric. Execute the device -l command to obtain a typical listing of components and their IDs:

/opt/terraspring/sbin/device -l 

Example output:

 DEVICE_ID  PARENT_ID STATUS   FARM_ID  TYPE 
         2          - USED     -        rf:cisco-rf (cisco RouterFabric)
      3002          - USED     -        cpu:sun-svr-420R-idb (Sun 420R) 
     50001          - USED     -        sf:stiletto-sf (Sun StilettoSwitchFabric)
     50100          - USED     103      cpu:sun-svr-blade (- -) 
     50101          - USED     102      cpu:sun-svr-blade (- -) 
     50102          - USED     101      cpu:sun-svr-blade (- -) 
     50113          - NEW      -        cpu:sun-svr-blade (- -) 
     50115          - FREE     -        cpu:sun-svr-blade (- -) 
     50150      50001 USED     -        sw:stiletto-sw (- -) 
     50160          - USED     -        pwr:stiletto-pwr (- -) 
10 devices found.

The IDs of the chassis components define the chassis to which they belong. Chassis component IDs have five digits. The second and third digits represent the chassis ID. The fourth and fifth digits represent the chassis component's ID. For example, all devices with the ID 503xx belong to a chassis with the ID 50300.

For each chassis , the IDs 5yy00 through 5yy15 are reserved for server blades, IDs 5yy50 and 5yy51 are reserved for switches, and ID 5yy60 is reserved for the system and switch controller (SSC). For example, for the fifth chassis the IDs in the following table would be assigned:

IDs 50000 through 59999 are reserved for chassis components. Do not assign any other devices to those IDs.

The chassis itself is not listed in the CPDB as a device. In that sense, a chassis has a “virtual” ID that is the same as the ID of the S0 blade if one exists.