Interfaces And Routing - Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note

Known Limitations in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
Copyright © 2010, Juniper Networks, Inc.
SRX240 Services Gateway
SRX650 Services Gateway
16-port GPIM
24-port GPIMs
On SRX650 devices, the T1/E1 GPIMs (2 or 4 port version) do not work in Junos OS
release 9.6R1. This issue is resolved in Junos OS Release 9.6R2 and later releases, but
if you roll back to the 9.6R1 image, this issue is still seen.
The SRX220 Services Gateway does not support the 1-port SFP Mini-PIM.

Interfaces and Routing

On SRX210 devices, the link goes down after an FPGA upgrade is performed. As a
workaround, run the
restart fpc
On SRX240 High Memory devices, traffic might stop between SRX240 device and
CISCO switch due to link mode mismatch. As a workaround, Juniper Networks
recommends setting auto-negotiation parameters on both ends to the same value.
On SRX100 devices, the link goes down when you upgrade FPGA on 1xGE SFP. As a
workaround, run the
restart fpc
On SRX210 devices with VDLS2, ATM COS VBR-related functionality cannot be tested
because of lack of support from the vendor.
On SRX210 High Memory devices, IGMP v2 JOINS messages are dropped on an IRB
interface. As a workaround, enable IGMP snooping to use IGMP over IRB interfaces.
On J Series devices, the DS3 interface do not have an option to configure
multilink-frame-relay-uni-nni (MFR).
On SRX210, SRX220 and SRX240 devices, every time the VDSL2 PIM is restarted in
the ADSL mode, the first packet passing through the PIM is dropped.
On SRX240 Low Memory devices and SRX240 High Memory devices, the RPM server
operation does not work when the probe is configured with the option
.
destination-interface
Link Layer Discovery Protocol (LLDP)—The following are the LLDP limitations:
On J Series devices, LLDP is not supported on routed ports.
On SRX Series and J Series devices, LLDP over
On SRX Series and J Series devices, LLDP is supported only on interface unit 0.
In J Series xDSL PIMs, mapping between IP CoS and ATM CoS is not supported. If the
user configures IP CoS in conjunction with ATM CoS, the logical interface level shaper
matching the ATM CoS rate must be configured to avoid congestion drops in SAR.
Example:
set interfaces at-5/0/0 unit 0 vci 1.110
set interfaces at-5/0/0 unit 0 shaping cbr 62400 ATM COS
set class-of-service interfaces at-5/0/0 unit 0 scheduler-map sche_map IP COS
command.
command and restart the FPC.
interfaces is not supported.
ae
137