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

[PTX] Up time for IFD links vary on FPC Type3 with PTX3000

0

0

Article ID: KB33479 KB Last Updated: 17 Dec 2018Version: 1.0
Summary:

In the topology with FPC Type3 and IPLC (Integrated Photonic Line Card), when PTX3000-1 FPC3 (slot 8) is turned on, all the et-8/0/* status will appear to be "up", but not all comes "up" at the same time. Some are delayed up to 2 minutes until all the alarms are cleared, then the interfaces come "up".

Symptoms:

Test topology

            PTX3000-1                              PTX3000-2 
 +-------+             +--------+      +--------+             +-------+
 |       |et-8/0/0-----+        |      |        +-----et-8/0/0|       |
 | FPC3  |et-8/0/1-----+ IPLC   |      | IPLC   +-----et-8/0/1| FPC3  |
 |(slot8)|et-8/0/2-----+(slot15)+------+(slot15)+-----et-8/0/2|(slot8)|
 |       |et-8/0/3-----+        |      |        +-----et-8/0/3|       |
 |       |et-8/0/4-----+        |      |        +-----et-8/0/4|       |
 +-------+             +--------+      +--------+             +-------+
 FPC3-SFF-PTX-1X       OPT3-SFF-PTX     OPT3-SFF-PTX        FPC3-SFF-PTX-1X

 

PTX3000-1 messages

Sep 25 11:12:04  PTX3000-1 mib2d[63093]: SNMP_TRAP_LINK_UP: ifIndex 520, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/0  ---+
Sep 25 11:12:07  PTX3000-1 /kernel: et-8/0/2 link 0: Asserting alarm(s) otu-bdi                                                       |
Sep 25 11:12:07  PTX3000-1 /kernel: et-8/0/2 link 0: Clearing alarm(s) lof                                                            |
Sep 25 11:12:08  PTX3000-1 /kernel: et-8/0/1 link 0: Clearing alarm(s) otu-bdi                                                        |
Sep 25 11:12:12  PTX3000-1 /kernel: et-8/0/2 link 0: Clearing alarm(s) otu-bdi                                                        |
Sep 25 11:12:15  PTX3000-1 /kernel: et-8/0/4 link 0: Asserting alarm(s) otu-bdi                                                      104 seconds
Sep 25 11:12:15  PTX3000-1 /kernel: et-8/0/4 link 0: Clearing alarm(s) lof                                                            |
Sep 25 11:12:20  PTX3000-1 /kernel: et-8/0/4 link 0: Clearing alarm(s) otu-bdi                                                        |
Sep 25 11:12:33  PTX3000-1 mib2d[63093]: SNMP_TRAP_LINK_UP: ifIndex 521, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/1     |
Sep 25 11:13:01  PTX3000-1 mib2d[63093]: SNMP_TRAP_LINK_UP: ifIndex 522, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/2     |
Sep 25 11:13:22  PTX3000-1 mib2d[63093]: SNMP_TRAP_LINK_UP: ifIndex 523, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/3     |
Sep 25 11:13:48  PTX3000-1 mib2d[63093]: SNMP_TRAP_LINK_UP: ifIndex 524, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/4  ---+


PTX3000-2 messages

Sep 25 11:11:35  PTX3000-2 mib2d[35989]: SNMP_TRAP_LINK_UP: ifIndex 553, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/0  ---+
Sep 25 11:11:44  PTX3000-2 /kernel: et-8/0/0 link 0: Clearing alarm(s) los                                                            |
Sep 25 11:11:47  PTX3000-2 mib2d[35989]: SNMP_TRAP_LINK_UP: ifIndex 578, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/3     |
Sep 25 11:11:59  PTX3000-2 mib2d[35989]: SNMP_TRAP_LINK_UP: ifIndex 568, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/1    36 seconds
Sep 25 11:12:01  PTX3000-2 /kernel: et-8/0/3 link 0: Clearing alarm(s) los                                                            |
Sep 25 11:12:03  PTX3000-2 mib2d[35989]: SNMP_TRAP_LINK_UP: ifIndex 571, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/2     |
Sep 25 11:12:11  PTX3000-2 mib2d[35989]: SNMP_TRAP_LINK_UP: ifIndex 579, ifAdminStatus up(1), ifOperStatus up(1), ifName et-8/0/4  ---+
Sep 25 11:12:13  PTX3000-2 /kernel: et-8/0/1 link 0: Clearing alarm(s) los 
Sep 25 11:12:17  PTX3000-2 /kernel: et-8/0/2 link 0: Clearing alarm(s) los 
Sep 25 11:12:24  PTX3000-2 /kernel: et-8/0/4 link 0: Clearing alarm(s) los
 

PTX3000-1

FPC 8            REV 46   750-057064   ACPR8528          FPC3-SFF-PTX-1X
  CPU                     BUILTIN      BUILTIN           SMPC PMB
  PIC 0          REV 29   750-059747   ACPL1738          5X100GE DWDM CFP2-ACO
    Xcvr 0       REV 01   740-062357   1DJBZ11200S       OTN-100G-LH
    Xcvr 1       REV 01   740-062357   1DJBZ11300V       OTN-100G-LH
    Xcvr 2       REV 01   740-062357   1DJBZ12500M       OTN-100G-LH
    Xcvr 3       REV 01   740-062357   1DJBZ12500K       OTN-100G-LH
    Xcvr 4       REV 01   740-062357   1DJBZ113006       OTN-100G-LH
FPC 15           REV 05   740-068675   3D1I7100002       OPT3-SFF-PTX
  CPU                     BUILTIN      BUILTIN           SMPC PMB

PTX3000-2

FPC 8            REV 46   750-057064   BCAE8006          FPC3-SFF-PTX-1X
  CPU                     BUILTIN      BUILTIN           SMPC PMB
  PIC 0          REV 29   750-059747   ACPL1742          5X100GE DWDM CFP2-ACO
    Xcvr 0       REV 01   740-062357   1DJBZ10800M       OTN-100G-LH
    Xcvr 1       REV 01   740-062357   1DJBZ11300X       OTN-100G-LH
    Xcvr 2       REV 01   740-062357   1DJBZ10500K       OTN-100G-LH
    Xcvr 3       REV 01   740-062357   1DJBZ114001       OTN-100G-LH
    Xcvr 4       REV 01   740-062357   1DJBZ12500H       OTN-100G-LH
FPC 15           REV 05   740-068675   3D1I7130001       OPT3-SFF-PTX
  CPU                     BUILTIN      BUILTIN           SMPC PMB
Solution:

This is expected behavior as per the hardware implementation.  The Cordoba DWDM links need to perform successful QEF (Quasi Error Free) for optimal values, which is expected to take time. In order for QEF on a DWDM link to succeed, it depends on the SKY ASIC as well as the ACO (Analogue Coherent Optics).

If the optimal values are not reached, then the QEF restarts to reach the optimal value. Thus, the link coming up time varies based on when the link has successfully completed link training in the complete host path. Each reboot will show slightly different times.

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