JunosE 11.0.2 Release Notes
26
Known Behavior
IS-IS
When IS-IS is configured on a static PPP interface, the IS-IS neighbor does not
come up if you remove the IP address from the interface and then add the IP
address back to the interface.
Work-around:
When you remove and add back the IP address, you must also
remove the IS-IS configuration from the interface and then add the
configuration back to the interface by issuing the
no router isis
and
router isis
commands.
When you run IS-IS on back-to-back virtual routers (VRs) in an
IS-IS-over-bridged-Ethernet configuration and do not configure different IS-IS
priority levels on each VR, a situation can occur in which both VRs elect
themselves as the designated intermediate system (DIS) for the same network
segment.
This situation occurs because the router uses the same MAC address on all
bridged Ethernet interfaces by default. When both VRs have the same (that is,
the default) IS-IS priority level, the router must use the MAC address assigned
to each interface to determine which router becomes the DIS. Because each
interface in an IS-IS-over-bridged-Ethernet configuration uses the same MAC
address, however, the router cannot properly designate the DIS for the network
segment. As a result, both VRs elect themselves as the DIS for the same
network segment, and the configuration fails. [Defect ID 72367]
Work-around:
To ensure proper election of the DIS when you configure IS-IS
over bridged Ethernet for back-to-back VRs, we recommend that you use the
isis network point-to-point
command in Interface Configuration mode to
configure IS-IS to operate using point-to-point (P2P) connections on a broadcast
circuit when only two routers (or, in this case, two VRs) are on the circuit.
Issuing this command tears down the current existing IS-IS adjacency in that
link and reestablishes a new adjacency.
L2TP
L2TP peer resynchronization enables an L2TP failed endpoint to resynchronize
with its peer non-failed endpoint. The JunosE Software supports failover
protocol and silent failover peer resynchronization methods. If you configure
the silent failover method, you must keep the following considerations in mind:
PPP keepalives—To ensure resynchronization of the session database, PPP
keepalives must be enabled on the L2TP data path. Without PPP
keepalives, silent failover might disconnect an established session if there
is no user traffic during failover recovery.
Asymmetric routes on different line modules—Asymmetric routes whose
receive and transmit paths use I/O paths on different line modules can
result in improperly handled line module control packets. If your network
does include this type of asymmetric route, tunnels using these routes
might fail to recover properly.
