Bgp; Bgp/Mpls Vpns; B-Ras - Juniper JUNOSE SOFTWARE 10.2.2 - RELEASE NOTES 6-4-2010 Release Note

For e series broadband services routers
Table of Contents

Advertisement

BGP

BGP/MPLS VPNs

B-RAS

Configuring CAC and bulk-configured VCs on the same ATM interface was
supported in previous JUNOSe Software releases. As a result, If you are
upgrading to the current JUNOSe release from a lower-numbered release,
configurations that use CAC and bulk configuration on the same ATM interface
continue to work. However, we recommend that you disable CAC on these ATM
interfaces to ensure continued compatibility with future JUNOSe releases.
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
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.
Release 10.2.2
13
Known Behavior

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 10.2.2

Table of Contents