Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX9200] How to check for alarms on CB 0 Fabric Chip 1

0

0

Article ID: KB31496 KB Last Updated: 21 Aug 2020Version: 2.0
Summary:

This article aims to assist with troubleshooting alarms and other problems related to the EX9200 Fabric Plane using a step-by-step approach.

 

Symptoms:
  1. Check for the chassis alarm:

root@lab_1> show chassis alarms no-forwarding
1 alarms currently active

Alarm time               Class  Description
2017-01-26 10:11:21 UTC  Minor  Check CB 0 Fabric Chip 1
‚Äč2017-01-26 10:11:22 UTC  Minor  Check CB 1 Fabric Chip 1 
  1. Review Fabric-related log messages:

Feb  8 10:25:37  sh-mad6-a alarmd[2863]: Alarm cleared: CB color=YELLOW, class=CHASSIS, reason=CB 0 Fabric Chip 0 Not Online
Feb  8 10:25:37  sh-mad6-a craftd[1906]: Minor alarm cleared, CB 0 Fabric Chip 0 Not Online

 

Solution:

Perform the following steps to troubleshoot:

  1. Run the command “show chassis alarms” and check for alarms in “Check” state. In the following outputs, the Fabric chip 1 on CB 0 is showing Check state at the indicated time stamps:

root@switch> show chassis alarms no-forwarding
1 alarms currently active

Alarm time               Class  Description
2017-01-26 10:11:21 UTC  Minor  Check CB 0 Fabric Chip 1 
  1. Check the status of the Fabric planes by using the command “show chassis fabric summary”:

root@switch> show chassis fabric summary
Plane   State    Uptime
0      Online   12 days, 22 hours, 4 minutes, 11 seconds
1      Online   12 days, 22 hours, 4 minutes, 3 seconds
2      Online   12 days, 22 hours, 4 minutes, 3 seconds
3      Check    12 days, 22 hours, 3 minutes, 54 seconds <<<< In the Check state
4      Spare    12 days, 22 hours, 3 minutes, 54 seconds
5      Spare    12 days, 22 hours, 3 minutes, 46 seconds
6      Spare    12 days, 22 hours, 3 minutes, 46 seconds
7      Spare    12 days, 22 hours, 3 minutes, 37 seconds  

Note: The above outputs were taken from EX9208, which has 8 Fabric planes; however, EX9214 has 6 Fabric planes.

  1. The above outputs show that there is an issue either with CB (Control Board) or the FPC. In order to isolate this problem, identify which planes are reporting errors by using the output of “show chassis fabric fpcs”:

root@switch> show chassis fabric fpcs
FPC 3
  PFE #0
      Plane 0: Plane enabled
      Plane 1: Plane enabled
      Plane 2: Plane enabled
      Plane 3: Link error   <<<< Link Errors
      Plane 4: Links ok
      Plane 5: Unused
      Plane 6: Links ok
      Plane 7: Unused  
  1. Re-seat FPC3 to see if the link errors are cleared. If you see link errors after re-seating the FPC, then remove FPC3 from the chassis and check if the alarm is cleared.

  2. If the link errors are not cleared after re-seating the FPC, then check for CRC errors by using the following commands:

root@switch>request pfe execute command “show syslog messages” target fpc3 | no-more

The above command will display any error messages for the FPC; eg: LUCHIP error, CRC error and so on.

root@switch> request pfe execute command "show hsl2 statistics" target fpc3                                                                                                                                                                                                                    Cell Received (last)           CRC Errors (last)   
                                                                                                  --------------------------------------------------------------------------------------------------                                                                                                                                 
LUCHIP(0) channel statistics :                                                                                                
LUCHIP(0)-chan-rx-0 <= MQCHIP(0)-chan-tx-4        11178230907409  (15744291)        6  (6)
LUCHIP(0)-chan-rx-1 <= MQCHIP(0)-chan-tx-5        11178230907409  (15744291)        0  (0)
MQCHIP(0) channel statistics :
MQCHIP(0)-chan-rx-2 <= LUCHIP(0)-chan-tx-2        12277729041520  (17282590)        0  (0)
MQCHIP(0)-chan-rx-3 <= LUCHIP(0)-chan-tx-3        12277729041520  (17282590)        0  (0)
MQCHIP(0)-chan-rx-7 <= remote/unknown                 4859558696  (2205210399)      0  (0)
MQCHIP(0)-chan-rx-8 <= remote/unknown                 4859558696  (2205210399)      0  (0)
MQCHIP(0)-chan-rx-28 <= remote/unknown                4859553940  (2205210175)      0  (0)
MQCHIP(0)-chan-rx-29 <= remote/unknown                4859553940  (2205210175)      0  (0)
MQCHIP(0)-chan-rx-62 <= IXCHIP(0)-chan-tx-3        4176642473379  (5885305)         0  (0)                   
IXCHIP(0) channel statistics :
IXCHIP(0)-chan-rx-0 <= MQCHIP(0)-chan-tx-68        4176814478555  (5886227)         0  (0)  

Run this command 4-5 times each at 1 minute intervals and see if the CRC errors are increasing. If the CRC errors are incrementing, then the issue is with the FPC (linecard).

  1. If the link errors are cleared after re-seating the FPC but the chassis alarms continue to show up, then re-seat CB0.

  2. If the alarms do not go away after re-seating the Control Board, then swap the CB with a spare working CB to isolate the issue with the CB or the chassis.

  3. If the alarms remain after swapping the Control Board with a working Control Board, then the issue could be with the chassis. If alarm goes away after replacing the CB, then the issue is with the CB.

If issues continue to persist even after performing the above steps, contact Support for further assistance.

 

Modification History:

2020-08-21: Article reviewed for accuracy; no changes required; article valid and relevant.

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search