Description

This article provides information on how to identify if a line card is not functional in EX8200 due to an unsupported Junos version, which is installed on it.

Symptoms

How to identify if a line card is not functional in EX8200 due to an unsupported Junos version, which is installed on it.

Solution

When any new model of line card is inserted in an existing EX8200 chassis, Routing Engines should be running the supported Junos version. Otherwise, the line card will not be properly recognized.

The following sample is the output of the commands to show the behavior of the EX 8200 switch, when line cards with unsupported versions are installed. When the show chassis hardware command is issued, the line card is not recognized; as shown below:

user@switch> show chassis hardware detail no-forwarding

user@switch>show chassis hardware
Hardware inventory:
Item            Version       Part number   Serial number    Description
Chassis         REV 09                      CAXXXXXXXXXX     EX8208
Backplane       REV 09        710-022044    BTXXXXXXXXXX     EX8208-BP-S
CB 0            REV 23        710-020635    BEXXXXXXXXXX     EX8208-SRE320  
   Routing Engine   0           BUILTIN       BUILTIN        RE-EX8208
   da0    1992 MB  ST72682                    02100000       Hard Disk
CB 1            REV 23        710-020635    BEXXXXXXXXXX     EX8208-SRE320
   Routing Engine 1             BUILTIN       BUILTIN        RE-EX8208
   da0    1992 MB ST72682                     02100000       Hard Disk
CB 2            REV 13        710-021502    AZXXXXXXXXXX     EX8208-SF320
FPC 0           REV 03        710-036594    GSXXXXXXXXXX
  CPU
FPC 1           REV 03        710-036594    GSXXXXXXXXXX
  CPU
FPC 2           REV 03        710-036594    GSXXXXXXXXXX
CPU
FPC 3           REV 03        710-036594    GSXXXXXXXXXX
CPU
FPC 4           REV 03        710-036594    GSXXXXXXXXXX

When the show chassis fpc command is used, it displays no power, as shown below:

user@switch> show chassis fpc 
                                  Temp             CPU Utilization (%)              Memory        Utilization (%)
Slot    State                (C)                 Total Interrupt                  DRAM (MB)     Heap Buffer
0        Offline        ---No power---
1        Offline        ---No power---
2        Offline        ---No power---
3        Offline        ---No power---
4        Offline        ---No power---
5        Empty
6        Empty
7        Empty
You can also notice the following log messages, which state that the FPC is detached or the chassisd has an unsupported FPC:
May 11 16:29:00 user1 chassisd[773]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)
May 11 16:29:00 user1 chassisd[773]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(1)
May 11 16:29:00 user1 chassisd[773]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(2)
May 11 16:29:00 user1 chassisd[773]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(3)
May 11 16:29:00 user1 chassisd[773]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(4)
May 11 16:29:01 user1 chassisd[773]: CHASSISD_UNSUPPORTED_FPC: FPC with I2C ID of 0xb0d is not supported
May 11 16:29:02 user1 chassisd[773]: CHASSISD_UNSUPPORTED_FPC: FPC with I2C ID of 0xb0d is not supported
May 11 16:29:02 user1 chassisd[773]: CHASSISD_UNSUPPORTED_FPC: FPC with I2C ID of 0xb0d is not supported
May 11 16:29:10 user1 craftd[775]: Minor alarm set, CB 0 Fabric Chip 1 Not Online
May 11 16:29:10 user1 alarmd[774]: Alarm cleared: CB color=YELLOW, class=CHASSIS, reason=CB 0 Fabric Chip 1 Not Online
May 11 16:29:10 user1 craftd[775]: Minor alarm cleared, CB 0 Fabric Chip 1 Not Online