Bgp; Bgp/Mpls Vpns - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - RELEASE NOTES 2010-11-09 Release Note

JunosE 11.3.0 Release Notes

BGP

BGP/MPLS VPNs

16 Known Behavior
When you configure an ATM PVC where PCR = SCR and maximum burst size is zero,

the CLI returns an error indicating the burst size is invalid and it does not create the
VC.
Work-around: Configure a CBR or a UBR plus PCR to create the circuit with the same
parameters, depending on the desired priority for the traffic. CBR has a high priority
and UBR plus PCR has a medium priority.
The E Series router does not include the link-local IPv6 address in the next-hop field

of an MP-BGP update message carrying IPv6 routing information over IPv4 transport.
This behavior is compliant with RFC 2545 but might have interoperability issues with
other implementations that depend on a link-local IPv6 address in the next-hop field
on a directly connected external BGP peering.
Work-around: Enable EBGP multihop configuration on the remote (non–Juniper
Networks) peer.
The following message might be displayed under certain conditions:

bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting inbound
TCP connection
The message is generated when an unconfigured peer attempts to establish a TCP
session with an E Series router and a valid route to the source address of the peer is
absent from the router's routing table.
If a valid route exists in the routing table, the following message is displayed when an
unconfigured peer attempts to establish a TCP session with an E Series router;
X.X.X.X is the source address of the unconfigured peer:
NOTICE 08/29/2001 16:50:11 bgpConnections (default,X.X.X.X): Inbound connection refused
- no peer X.X.X.X configured in core
In a scaled environment, we recommend that you increase the hold timers for the

following protocols to appropriate values, based on the level of complexity of the
network and scaling settings, so as to enable graceful restart to be completed
successfully. [Defect ID 184974]
 BGP
 IS-IS
 LDP
 OSPF
 RSVP
For a sample configuration scenario that illustrates how to configure hold timers for
successful graceful restart in a scaled environment, see JunosE BGP and MPLS
Configuration Guide, Chapter 1, Configuring BGP Routing.
NAT does not function properly with secondary routing table lookup (fallback

global) or global export mapping on the VRF.
Copyright © 2010, Juniper Networks, Inc.