Ipsec - Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

For e series broadband services routers
Table of Contents

Advertisement

Release 10.0.3
IP interface statistics become inconsistent when a slot is reset, because some
traffic (such as control traffic) might be destined for the SRP module and is
therefore counted elsewhere. [Defect ID 26697]
When a router configured with PIM on a virtual router undergoes multiple
warm restarts, the router subsequently hangs when an IP profile is configured.
[Defect ID 176470]
The ip route permanent command does not work properly. [Defect ID 34303]
Work-around: Issue the ip alwaysup command to prevent the route from being
removed from the IP routing table after the interface is shut down.
Logical port 20 on the ES2-S3 GE-20 IOA is reserved for the hardware multicast
packet replication feature. Logical port 20 and the hardware multicast
replication feature are not supported on the ES2-S3 GE-20 IOA in this release.
[Defect ID 84727]
If you have a large configuration on a hybrid module combination (OC3/STM-1
GE/FE line module with the OC3-2 GE APS I/O module), boot from NVS, and
issue the slot erase command before booting has completed, the line module
resets. [Defect ID 64104]
Work-around: To recover from the error, issue the slot reload command
anytime after the module begins to reset.
When MPLS and IS-IS are configured on Ethernet interfaces, you cannot delete
the interface after the IP address is removed. This issue is not a problem on
Ethernet VLAN interfaces. [Defect ID 66813]
Deleting a VRF with 32,000 static subscriber interfaces fails to complete.
[Defect ID 82670]
Work-around: Use a macro to delete all static subscriber interfaces before you
delete a VRF.

IPSec

In a network where you use the tunnel signalling command to specify that the
security parameters and keys are configured manually for IPSec tunnels
between VRs, the line modules reset when you delete and then re-create the
IPSec tunnels. If you attempt to configure the tunnels again after the modules
come back up, the line modules reset again.
Work-around: Configure the IPSec tunnels to use ISASKMP/IKE to negotiate SA
and establish keys. [Defect ID 178304]
IPSec tunnels created over Fast Ethernet interfaces fail to come up. [Defect ID
179256]
Work-around: After you create the tunnel, bounce the tunnel interface by
issuing the shutdown/no shutdown command sequence. The tunnel comes up
successfully.
41
Known Problems and Limitations

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 10.0.3

Table of Contents