Line Module Redundancy; Mlppp - Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

Line Module Redundancy

MLPPP

NAT dynamic translation generation affects the LNS session creation time.
When NAT dynamic translations and LNS sessions are created simultaneously,
NAT dominates the CPU cycles of the tunnel-service module, resulting in a
delay in the LNS session creation rate. The LNS session creation rate returns to
its normal rate when NAT dynamic translations are no longer being generated.
[Defect ID 53191]
Work-around: When signaling performance must be optimal, avoid the
simultaneous configuration of NAT and LNS.
If you create an L2TP destination profile profileName, establish tunnels with the
profile, and then remove the profile, you cannot subsequently create another
destination profile using that same profileName until all the tunnels drain from
the previous instance of this destination profile. If you do not wait, the E Series
router displays a message similar to the following:
l2tp: Discarding incoming sccrq from vr default, remote address 192.168.100.1 -
no destination profile.
If you do not want to wait for the tunnels to drain, use a different name for the
destination profile. [Defect ID 32973]
On E120 routers and E320 routers, redundant IOAs have a temperature sensor,
and the show environment all command lists the temperature of IOAs in their
associated slots.
On ERX routers, redundant I/O modules do not have a temperature sensor.
Therefore, the show environment all command output lists the primary I/O
module temperature in the slot of the line module that is responsible for the I/O
module.
When you install an ES2-S1 Redundancy IOA with a hardware revision number
of -02 or less in slot 0 or slot 11 of the E320 router or in slot 0 or the E120
router, do not install an OCx/STMx ATM IOA or an OCx/STMx POS IOA in the
lower (E320) or left (E120) adapter bay of slot 1 or slot 12. When the spare line
module is controlling another slot and you revert back to the primary line
module, the ATM or POS IOAs can become unusable or cause the line module
to reset. [Defect ID 69760]
Work-around: This problem is not present for ES2-S1 Redundancy IOAs with a
hardware revision number of -03 or higher.
Do not configure both MLPPP fragmentation (with the ppp fragmentation
command) and IP fragmentation of L2TP packets (with the ip mtu command)
on the same interface. Instead, you must choose only one of the fragmentation
configurations by setting it to the necessary value and set the other
fragmentation configuration to the maximum allowable value.
Release 10.0.3
25
Known Behavior