Support Support Downloads Knowledge Base Case Manager My Juniper 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

[SRX] Major alarm 'FPC x misconfig' ; 'FPC not supported on platform' as offline reason

0

0

Article ID: KB35966 KB Last Updated: 22 Jun 2020Version: 1.0
Summary:

This article explains the meaning of the 'FPC x misconfig' major alarm on SRX series devices. It also provides details on how to overcome the alarm.

Symptoms:

Active Alarm:

user@host> show chassis alarms no-forwarding
4 alarms currently active
Alarm time               Class  Description
2020-05-11 04:18:10 UTC  Major  FPC 3 misconfig
2020-05-11 04:18:10 UTC  Major  FPC 2 misconfig
2020-05-11 04:18:10 UTC  Major  FPC 1 misconfig
2020-05-11 04:18:10 UTC  Major  FPC 0 misconfig
Solution:

On SRX1400 device series, the FPC 0 slot is called the SYSIO card. The services gateway receives data from the various physical interfaces on the I/O card (IOC) or System I/O card (SYSIOC). Incoming data is passed through the SYSIOC to a Network and Services Processing Card (NSPC), and back to the outgoing port through the SYSIOC.

user@host> show chassis hardware detail | match FPC
FPC 0            REV 17   x   x          SRX1k 1GE SYSIO
FPC 1            REV 19   x   x          SRX3k SPC
FPC 2            REV 18   x   x          SRX3k 16xGE SFP
FPC 3            REV 19   x   x          SRX3k NPC

The status of other FPCs depend on FPC 0. In case FPC 0 goes down, all other FPCs will go offline and will not function until FPC 0 is properly functioning. The sequence of alarms looks like the follwoing:

May 11 04:18:10  <Truncated> alarmd[1307]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 0 misconfig
May 11 04:18:10  <Truncated> craftd[1237]:  Major alarm set, FPC 0 misconfig

May 11 04:18:10  <Truncated> chassisd[1235]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 1 offline: Hardware authentication failure
May 11 04:18:10  <Truncated> alarmd[1307]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 1 misconfig
May 11 04:18:10  <Truncated> craftd[1237]:  Major alarm set, FPC 1 misconfig
May 11 04:18:10  <Truncated> chassisd[1235]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 2 offline: Hardware authentication failure
May 11 04:18:10  <Truncated> alarmd[1307]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 2 misconfig
May 11 04:18:10  <Truncated> craftd[1237]:  Major alarm set, FPC 2 misconfig
May 11 04:18:10  <Truncated> chassisd[1235]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 3 offline: Hardware authentication failure
May 11 04:18:10  <Truncated> alarmd[1307]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 3 misconfig
May 11 04:18:10  <Truncated> craftd[1237]:  Major alarm set, FPC 3 misconfig

As you can see from the above logs, once FPC 0 goes offline, all other FPCs go offline one by one. This is because the SYSIO card provides fixed I/O ports for the base system and is an important element of the data plane. It provides a data path connectivity between the NSPC and the IOC. Once the connecting part is faulty, the data plane connectivity breaks, causing the rest of the FPCs to go offline. Also, the SYSIO card is responsible for providing power to the rest of the cards. 

The FPCS would be offlined due to "FPC not supported on Platform" reason for offline.

root@<Truncated>1> show chassis fpc detail no-forwarding
Slot 0 information:
  State                                 Offline
  Reason:                               FPC not supported on platform
  Temperature                        27
  Total CPU DRAM                      0 MB
  Total RLDRAM                        0 MB
  Total DDR DRAM                      0 MB
  Max Power Consumption               0 Watts
Slot 1 information:
  State                                 Offline
  Reason:                               FPC not supported on platform
  Temperature                        26
  Total CPU DRAM                      0 MB
  Total RLDRAM                        0 MB
  Total DDR DRAM                      0 MB
  Max Power Consumption               0 Watts
Slot 2 information:
  State                                 Offline
  Reason:                               FPC not supported on platform
  Temperature                        25
  Total CPU DRAM                      0 MB
  Total RLDRAM                        0 MB
  Total DDR DRAM                      0 MB
  Max Power Consumption               0 Watts
Slot 3 information:
  State                                 Offline
  Reason:                               FPC not supported on platform
  Temperature                        26
 Total CPU DRAM                      0 MB
  Total RLDRAM                        0 MB
  Total DDR DRAM                      0 MB
  Max Power Consumption               0 Watts

FPC Status:

root@xxxxxxx> show chassis fpc pic-status    
node0:
Slot 0   Present      SRX1k 1GE SYSIO
Slot 1   Present      SRX3k SPC
Slot 2   Present      SRX3k 16xGE SFP
Slot 3   Present      BUILTIN NPC

To resolve this condition on SRX1400 devices, please follow the steps below:

  1. Verify if the issue exists with FPC 0:

    a. Verify the environment conditions. If FPC 0 is in Failed/Present/Check/Testing state, it is most probably an error with the FPC.
    b. Verify the LED status for FPC 0. If the LED status is Red, this indicates an issue with FPC 0.
  2. Restart FPC slot 0 (SYSIO card):

    user@host> request chassis fpc (offline | online | restart) slot slot-number

    Here, 

    user@host> request chassis fpc restart slot 0
  3. Reseat Manually

    Reseat FPC 0 manually on the device. This will ensure that the FRU re-initiates as soon as power is re-introduced into it.

    Refer to the technical documentation on Replacing the SYSIOC on the SRX1400 Services Gateway. Although this document explains replacement, the same steps will hold true for reseat. In place of using a new SYSIO card as mentioned in the document, you must use the same card that is in the chassis and follow the steps.

  4. Replacement:

    If step 1 and step 2 does not work, it is most likely that the issue is with FPC 0. Then replace FPC 0 and check if the new FPC 0 (SYSIO) helps eliminate all alarms on the system.

    Contact JTAC for help with a replacement if needed.

Related Links

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