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

SFP index in PFE starts at 1, while port numbering starts at 0

0

0

Article ID: KB33782 KB Last Updated: 15 Jan 2019Version: 2.0
Summary:
Upon inserting a SFP into port 0/0 of MIC-3D-20GE-SFP, the following is printed:
fpc1 MIC(1/0)(1): SFP plugged in

This can be confusing, as the interface name is ge-1/0/0, not ge-1/0/1.
Symptoms:
Consider this hardware:
FPC 1            REV 21   750-031088   ZX7000            MPC Type 2 3D Q
  MIC 0          REV 16   750-049846   CAGV8000          3D 20x 1GE(LAN)-E,SFP
    PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) -E  SFP
      Xcvr 0     REV 01   740-013111   8177000           SFP-T
      Xcvr 4     REV 01   740-038291   PTA1AAA           SFP-T
    PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) -E  SFP
      Xcvr 8     REV 02   740-011613   AM0926SAAAA       SFP-SX


Which creates these interfaces:
ge-1/0/0
ge-1/0/4
ge-1/1/8


When inserting a SFP, messages are printed:
fpc1 MIC(1/0)(1): SFP plugged in
fpc1 MIC(1/0)(2): SFP plugged in
fpc1 MIC(1/1)(3): SFP plugged in

 
Cause:
This comes from the FPC's view of the SFP index, which does not have a 0 index to begin, so port 1 is index 2:
NPC1(lab-MX480-RE0 vty)# show sfp list   
...
Index   Name             Presence     ID Eprom  PNO         SNO          calibr   Toxic
-----   --------------   ----------   --------  ----------  ----------- -------  -------
    1      MIC(1/0)(0)      Present   Complete  740-013111  8177047           Unknown
    2      MIC(1/0)(4)      Present   Complete  740-038291  PTA1CBE           Unknown
    3      MIC(1/1)(8)      Present   Complete  740-011613  AM0926SBX2V     int    Unknown


If SFP's are not installed in order, the indexes may be out of order as well, so it is necessary to check this command when reading the FPC syslog.
Solution:
Take note of log entries which start with "fpc1" or similar, as these lines come directly from the 'pfe notice' syslog configuration. As such, some knowledge of how the FPC indexes the SFP's is needed. It may also be helpful to check these commands:
show chassis pic
show chassis hardware


Other platforms do not have this problem, like MX204.
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