Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Chassis

  • Enabling runtime hot-swap of LMICs (MX304)—We support graceful insertion and removal of line-card MICs (LMICs) on the MX304 device during runtime. You can use the new CLI command set chassis fpc slot mic slot power off to power off the MIC. You can power on the MIC by deleting this power-off configuration. Power management operations on multiple LMICs occur sequentially. To view the MIC status, you can use the new command show chassis fpc mic-status.

    [See fpc (Chassis), request chassis mic, show chassis fpc, and show chassis hardware.]

  • Runtime hot-swap of LMICs allows monitoring services to gracefully stop and restart (MX304)—Monitoring services such as inline active flow monitoring, inline monitoring services, video monitoring, Routing-Engine-based sampling, and FlowTapLite gracefully stop when you take the Packet Forwarding Engine offline and replace the line-card MIC (LMIC). These services gracefully become operational again after you've replaced the LMIC and brought the Packet Forwarding Engine back online. You can use the new CLI command set chassis fpc slot mic slot power off to take the Packet Forwarding Engine offline. You can bring the Packet Forwarding Engine back online by deleting this power-off configuration.

    [See fpc (Chassis), request chassis mic, show chassis fpc, and show chassis hardware.]

  • Effects of runtime hot-swap of LMICs on port mirroring (MX304)—Hot-swapping line-card MICs (LMICs) causes the Packet Forwarding Engine to go offline and come back online again. Port mirroring reacts to the hot-swap of LMICs in the following ways:

    • If the Packet Forwarding Engine hosting the output mirroring destination interface (MDI) goes offline, traffic from the input mirroring interface is not mirrored. Mirroring resumes when the Packet Forwarding Engine hosting the MDI comes back online.

    • In a port-mirroring next-hop-group or next-hop-subgroup scenario, if a Packet Forwarding Engine hosting MDIs goes offline, the MDIs associated with the offline Packet Forwarding Engine are pruned from the member list. Those associated MDIs are added back to the member list when the Packet Forwarding Engine hosting the MDIs comes back online.

    • If the Packet Forwarding Engine hosting the mirroring interface goes offline, traffic entering, leaving, and mirrored at the interface stops. Ingress and egress mainline traffic and mirroring resume when the Packet Forwarding Engine hosting the mirroring interface comes back online.

    [See fpc (Chassis), request chassis mic, show chassis fpc, and show chassis hardware.]

  • Optics EM policy support (MX10004 and MX10008)—The Junos Environment Monitoring (EM) policy now includes optics temperature sensors for MX10004 and MX10008 routers with MX10K-LC9600 line card. The policy includes the following features::

    • The Optics EM policy incorporates periodically polled temperature readings of optical modules in the system to automatically manage the fan speed

    • Junos OS will automatically trigger optics shutdown for 100GbE and 400GbE optics when the Fire Shutdown threshold is breached. Auto-recovery is not supported for optics disabled by the EM policy. To re-enable the optics, use the request interface optics-reset command or perform soft optics insertion and removal (OIR).

    • The Optics EM policy is enabled by default on all 100GbE and 400GbE optics that are Multi-source Agreements (MSA) compliant and support diagnostic EEPROM with temperature monitoring. This policy is not applicable for loopback optics and direct attach copper (DAC) cables.

    To disable EM policy, use the following CLI command:

    • set chassis fpc fpc_slot pic pic_slot port port_no no-temperature-monitoring

      It explicitly disables the EM policy on specific WAN ports.

    To view temperature threshold values and fan speed, use the following CLI commands:

    • show chassis temperature-thresholds displays the optics temperature threshold values.

    • show chassis environment displays the optics temperature.

    • show chassis fan displays the fan status and speed

    [See temperature-sensor.]

  • Low-power mode environment monitoring policy profile for noise reduction (MX10004 and MX10008)—We provide support to reduce the operational noise levels when you use 100GbE ports on MX10004 and MX10008 devices with the LC9600 line card installed. With this feature, you can maintain low device noise levels without compromising cooling efficiency. Use the set chassis fpc-empolicy-profile low-power-mode command to enable this feature. You can then use the show chassis temperature-thresholds or show chassis fan command to view the updated fan speed details.

    [See Low-Power Mode EM Policy Profile for Noise Reduction.]