Stateful Srp Switchover (High Availability) And Ip Tunnels; Subscriber Management - Juniper JUNOSE 11.0.2 - RELEASE NOTES Release Note

For e series broadband services routers
Table of Contents

Advertisement

JunosE 11.0.2 Release Notes

Stateful SRP Switchover (High Availability) and IP Tunnels

Subscriber Management

52
Known Problems and Limitations
A packet loss sometimes occurs during stateful SRP switchover when you use
the ping command on a router that is configured for OSPF graceful restart, and
is connected to a helper router in the OSPF IPv6 broadcast network and
another helper router in the OSPF IPv6 backbone area. [Defect ID 181470]
ERX7xx model, ERX14xx model, or ERX310 router:
When you use the ping command with the IPv6 address of the helper
router in the multicast area as the destination address and the
loopback address of the helper router in the backbone area as the
source address, a packet loss of 2 seconds occurs for the first stateful
SRP switchover. However, no packet loss occurs for successive stateful
SRP switchovers.
When you use the ping command with the IPv6 address of the helper
router in the broadcast network as the destination address and no
source address when stateful SRP switchover is performed the first
time, an identical packet loss occurs. In this case too, no packet loss
occurs during subsequent switchovers.
E120 router or E320 router
When you use the ping command with the IPv6 address of the helper
router in the broadcast network as the destination address and the
loopback address of the helper router in the backbone area as the
source address, no packet loss occurs.
When you use the ping command with the IPv6 address of the helper
router in the multicast area as the destination address and no source
address, a packet loss of 1–2 seconds sometimes occurs during stateful
SRP switchovers.
When a dynamic GRE tunnel interface for Mobile IP relocates between SM
modules because the original SM reloads, Mobile IP deletes the relocated tunnel
interface. [Defect ID 178399]
When a subscriber has subscribed for a service, service session accounting
records always contains a default Acct-Terminate-Cause value of 10. This value
remains unchanged even after you use the terminate-code command to
configure a custom mapping between application terminate reasons and
RADIUS Acct-Terminate-Cause attributes. [Defect ID 181043]

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOSE 11.0.2 - RELEASE NOTES and is the answer not in the manual?

Questions and answers

Table of Contents