Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


IPLC Specifications

The Integrated Photonic Line Card (IPLC) is designed to be installed in a PTX3000 router chassis. Architecturally, this card can be plugged into either the FPC or the PIC slot. For control and management purposes, the card behaves exactly similar to an FPC in the PTX3000 router. IPLC uses the same Processor Mezzanine Board (PMB) as the PTX Series router FPCs, although not as a daughter card. Due to mechanical and physical considerations, the PMB is designed onto the card directly. The card supports 100G wavelengths, and contains 32 ports on the faceplate. The IPLC uses an extension card to support an additional 32 ports. The IPLC might also have external DCMs to compensate for incoming dispersion on 10G wavelengths.

The IPLC also supports an OSC channel. This is an in-band channel used to communicate with ILAs and other optical nodes in the line system that are not directly accessible over the Data Communications Network (DCN). DCN is an ITU terminology for a device that provides network telemetry to remote network elements for the purpose of operations and network element management. OSC framing logic is implemented in the FPGA. Performance monitoring of analog data and alarms is supported.

You can set an explicit configuration to associate an IPLC with an expansion card, to increase the number of ports from 32 to 64. You can add an expansion card to the residing on the same chassis. There can be only one association between one IPLC and one expansion card. For example, the IPLC in slot 0 can be associated with expansion card in slot 2. After IPLC slot 0 is associated with expansion card in slot, you cannot create another association between IPLC slot 0 and expansion card in slot 4. This setting is disallowed at the CLI configuration level itself. A corresponding alarm is triggered and an SNMP trap generated on a failure condition.

With only the specification of the configuration settings, it is not guaranteed that the express-in association are added to an optical IPLC. Junos OS needs to validate if the express-in port on the optical IPLC has been connected to the express-in port of the valid IPLC’s express-in port, and the express-in ports are UP on both the IPLCs. Only after the validation is successful, express-in ports are moved to the UP state on the optical IPLC. A corresponding alarm is triggered and an SNMP trap is generated on a failure condition.