Juniper JUNOS OS 10.4 - RELEASE NOTES - Vpns

•
RPD_MC_CFG_PREFIX_LEN_SHORT
•
RPD_MSDP_CFG_SA_LIMITS_CONFLICT
•
RPD_MSDP_CFG_SRC_INVALID
•
RPD_MVPN_CFG_PREFIX_LEN_SHORT
•
RPD_PLCY_CFG_COMMUNITY_FAIL
•
RPD_PLCY_CFG_FWDCLASS_OVERRIDDEN
•
RPD_PLCY_CFG_IFALL_NOMATCH
•
RPD_PLCY_CFG_PARSE_GEN_FAIL
•
RPD_PLCY_CFG_PREFIX_LEN_SHORT
•
RPD_RSVP_COS_CFG_WARN
•
RPD_RT_INST_IMPORT_PLCY_WARNING
•
RPD_OSPF_IF_COST_CHANGE
•
RPD_OSPF_TOPO_IF_COST_CHANGE
•
RPD_VPLS_INTF_NOT_IN_SITE
[System Log]
•
Added interface information to BFD session up/down system log tags—Added peer
address information for BFDD_TRAP_MHOP_STATE_DOWN and
BFDD_TRAP_MHOP_STATE_UP.
[System Log]
VPNs
•
Disable TTL propagation behavior for the routes in a VRF routing instance—Enables
you to control TTL decrementing for individual VPNs. In prior releases, Junos OS enabled
control of TTL behavior only at the router level for all LDP-signaled and all
RSVP-signaled label-switched paths. With this feature, you can control the behavior
on individual VPN routes. To configure, include the vrf-propagate-ttl or
no-vrf-propagate-ttl statement at the [edit routing-instances instance-name] hierarchy
level. The instance-specific behavior overrides the router behavior configured at the
[edit protocols mpls] hierarchy level with the no-propagate-ttl statement. The show
route extensive and show route detail commands display the TTL action for each VRF
routing instance.
[VPNs]
•
Support for Layer 3 VPN composite next hops and a larger number of Layer 3 VPN
labels on T Series routers—Layer 3 VPN composite next hops can now be enabled on
T Series routers with Enhanced Scaling FPCs by including the l3vpn-composite-nexthop
statement at the [edit routing options] or [edit logical-systems logical-system-name
Copyright © 2010, Juniper Networks, Inc.34
JUNOS OS 10.4 Release Notes