System - Juniper JUNOSE SOFTWARE 10.2.2 - RELEASE NOTES 6-4-2010 Release Note

System

A packet-triggered subscriber interface is created when the router receives a
packet with an IP source address that does not match any entries in the
demultiplexer table. When the router detects an unmatched packet, it generates
a trigger event that determines whether to create a dynamic subscriber
interface or configure an existing interface. To configure packet detection on
the router, use the ip auto-detect ip-subscriber command.
ERX routers display different behavior from E120 routers and E320 routers
when reporting modules as inactive.
ERX routers report a module as inactive when either:
The I/O module is not present
The primary line module is fully booted and ready to resume operation. In
this case, the standby is currently providing services.
E120 routers and E320 routers report a module as inactive when either:
The primary line module has no IOAs.
The primary line module has IOAs, but they have failed diagnostics.
The standby line module has taken over for the primary line module, and
has control of the IOAs.
Because E120 and E320 routers can accommodate up to two IOAs per slot, at
least one IOA must be online. If the second IOA fails, the line module is still
online, but does not use both IOAs. You can ensure that every module is up and
active in the system and not in a failed state by issuing the show version all
command.
In a router with a redundancy group that does not span quadrants (for example,
a three-slot redundancy group that spans slots 0, 1, and 2 in an ERX1410
chassis), the potential bandwidth of the redundant module is erroneously
included in the quadrant bandwidth calculation. The show utilization
command might indicate that the bandwidth is exceeded for modules in that
group. [Defect ID 31034]
When you copy the running configuration to NVS, the E Series router verifies
whether it has available space equal to at least twice the size of the .cnf file. If
the space is insufficient, you cannot complete the copy. [Defect ID 40655]
Work-around: Make sufficient space on the NVS by deleting .rel or .cnf files.
You cannot delete the ipInterface log after you delete the corresponding IP
interface. This does not prevent you from adding filters to other interfaces, nor
does it prevent you from adding a filter to the same interface if you re-create it
after deletion. [Defect ID 34842/45063]
Work-around: Remove the filter before you remove the interface. Alternatively,
if you remove the interface first, then you must remove all filters associated
with all IP interfaces.
Release 10.2.2
33
Known Behavior