Configuration rules might apply to PICs installed on standard Enhanced FPCs on the following routing platforms: M5, M10, M20, M40, M40e, M160, M320, J20, T320, and T640.
Configuration rules do not apply to PICs installed in the following routers or FPCs:
When you upgrade the JUNOS software, a warning appears if any configuration rules affect your PIC combinations. If you continue the installation, the PICs appear to be online (the LEDs are on), but the JUNOS software cannot enable them and they cannot pass traffic. As a workaround, you need to plan which PICs to install on the Enhanced FPCs or PIC slots on your routing platform. For specific information about PIC combination rules, consult Technical Bulletin PSN-2007-01-023. Go to http://www.juniper.net/customers/support and click Technical Bulletins. On the JTAC Technical Bulletins web page, enter PSN-2007-01-023 in the Search field, select the CS Technical Bulletin ID radio button, and click Search.
Path MTU discovery is enabled by default. To disable path MTU discovery for all GRE tunnels, include the no-gre-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To disable path MTU discovery for all IPIP tunnels, include the no-ipip-path-mtu-discovery statement at the [edit system internet-options] hierarchy level. To disable path MTU discovery for a specific tunnel, include the no-path-mtu-discovery statement at the [edit interfaces interface-name unit logical-unit-number tunnel] hierarchy level. Path MTU discovery requires that you configure the tunnel-level statement and the system-level statement simultaneously. [System Basics]
You can also configure an IP address as the packet gateway controller (PGC) name. However, the IP address is not used for the connection to the PGC. To configure an IP address for the PGC name, include the gateway-controller statement at the [edit services pgcp gateway gateway-name] hierarchy level. [Services Interfaces]
NAT addresses—When configuring network address translation (NAT), if you specify the following addresses that do not match the NAT flow or NAT rule, the corresponding traffic is dropped:
[Services Interfaces]
Label aggregation for route reflectors in Layer 3 VPNs—To work with route reflectors in Layer 3 VPN networks, the Juniper Networks M10i router aggregates a set of incoming labels only in these cases:
<configuration>
<class-of-service> <interfaces> <name>fe-0/0/0</name>
<!- - tag elements for other statements -
-> </interfaces> <interfaces> <name>ge-0/0/0</name>
<!- - tag elements for other statements -
-> </interfaces> </class-of-service> </configuration>
/configuration/class-of-service/interfaces[name='fe-0/0/0']/* /configuration/class-of-service/interfaces[name='ge-0/0/0']/*
The JUNOS XML and X-Path equivalents for JUNOS Release 8.5 and later are as follows:
<configuration> <class-of-service>
<interfaces> <interface> <name>fe-0/0/0</name>
<!- - tag elements for other statements -
-> </interface> <interface>
<name>ge-0/0/0</name> <!- - tag elements
for other statements - -> </interface>
</interfaces> </class-of-service> </configuration> /configuration/class-of-service/interfaces/interface[name='fe-0/0/0']/*
/configuration/class-of-service/interfaces/interface[name='ge-0/0/0']/*
The CLI syntax is not changing for CoS interfaces. [JUNOS XML API Configuration Reference]
On the MX-series router, to enable ingress class-of-service (CoS) capabilities for the enhanced queueing Dense Port Concentrator (DPC), you must perform the following steps:
[Class of Service]