H3C Technologies H3C S12500-X Series Switches - Manual (Page 147)

136
Step Command Remarks
5. Enable the BGP AS number
substitution function. peer { ip-address | group-name }
substitute-as
By default, BGP AS number
substitution is disabled.
For more information about this
command, see Layer 3—IP Routing
Command Reference.
Enabling SNMP notifications for MPLS L3VPN
This feature enables generating SNMP notifications for MPLS L3VPN when important events occur (for
example, when the maximum number of routes in a VPN instance is exceeded), as defined in RFC 4382.
The generated SNMP notifications are sent to the SNMP module. The SNMP module determines how to
output the notifications according to the configured output rules.
For more information about SNMP notifications, see Network Management and Monitoring
Configuration Guide.
To enable SNMP notifications for MPLS L3VPN:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable SNMP notifications for
MPLS L3VPN.
snmp-agent trap enable l3vpn
By default, SNMP notifications for
MPLS L3VPN are enabled.
Displaying and maintaining MPLS L3VPN
You can soft-reset or reset BGP sessions to apply new BGP configurations. A soft reset operation updates
BGP routing information without tearing down BGP connections. A reset operation updates BGP routing
information by tearing down, and then reestablishing BGP connections. Soft reset requires that BGP
peers have route refresh capability.
Use the following commands to soft reset or reset BGP sessions:
Task Command Remarks
Soft reset BGP sessions for VPNv4
address family.
refresh bgp { ip-address | all | external |
group group-name | internal } { export |
import } vpnv4 [ vpn-instance
vpn-instance-name ]
Available in user view.
Reset BGP sessions for VPNv4
address family.
reset bgp { as-number | ip-address | all |
external | internal | group group-name }
vpnv4 [ vpn-instance vpn-instance-name ]
Available in user view.
Use the following commands to display MPLS L3VPN: