Configuring a Mode in Which BGP4+ Path Attributes Are Processed
To enhance reliability, you can configure a special mode in which BGP4+ path attributes are processed.
Usage Scenario
A BGP4+ Update message contains various path attributes. If a local device receives Update messages containing malformed path attributes, the involved BGP4+ sessions may flap. To resolve this issue and enhance reliability, configure a special mode in which a device processes specified BGP4+ path attributes in received Update messages. Special modes indicate those that are not defined in a standard protocol.
This configuration may cause the specified path attributes to be dropped or the routes carrying the specified path attributes to be withdrawn. Therefore, exercise caution when you perform this configuration.
The peer path-attribute-treat command configuration takes effect immediately for the routes received after the command is run. However, for the routes received before the command is run, the configuration can take effect only after the refresh bgp command is run.
Procedure
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
BGP is started (with the local AS number specified), and the BGP view is displayed.
- Run peer ipv6-address as-number as-number
The IPv6 address of a peer and the number of the AS where the peer resides are specified.
- Run ipv6-family unicast
The BGP-IPv6 unicast address family view is displayed.
- Run peer peerIpv6Addr path-attribute-treat attribute-id { id [ to id2 ] } &<1-255> { discard | withdraw | treat-as-unknown }
A mode in which the device processes specified BGP4+ path attributes in received Update messages is configured.
- Run commit
The configuration is committed.