Bgp/Mpls Vpns; B-Ras - Juniper JUNOSE 11.0.2 - RELEASE NOTES Release Note

JunosE 11.0.2 Release Notes

BGP/MPLS VPNs

B-RAS

14
Known Behavior
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.
Pool groups are not supported; although the ip local pool group command
appears in the CLI, it is not supported.
If the router is under a heavy load, the show profile command might take
longer than usual to execute.
Work-around: You can either delay examination of profiles until the router is
less busy, or save a copy of the profile to a text file off the router.