494
Configuring an IPv6 prefix list
If all items are set to deny mode, no routes can pass the IPv6 prefix list. To permit unmatched IPv6
routes, you must configure the permit :: 0 less-equal 128 item following multiple deny items.
To configure an IPv6 prefix list:
1. Enter system view.
system-view
N/A
2. Configure an IPv6
prefix list.
ipv6 prefix-list
prefix-list-name [
index
index-number ] {
deny
|
permit
} ipv6-address
{ prefix-length |
inverse
inverse-prefix-length
[
greater-equal
min-prefix-length ] [
less-equal
max-prefix-length ] }
By default, no IPv6
prefix lists exist.
Configuring an AS path list
You can configure multiple items for an AS path list that is identified by a number. The relationship
between the items is logical OR. A route matches the AS path list if it matches one item in the list.
To configure an AS path list:
1. Enter system view.
system-view
N/A
2. Configure an AS path
list.
ip as-path
as-path-number {
deny
|
permit
} regular-expression
By default, no AS path lists exist.
Configuring a community list
You can configure multiple items for a community list that is identified by a number. The relationship
between the items is logical OR. A route matches the community list if it matches one item in the list.
To configure a community list:
1. Enter system view.
system-view
N/A
2. Configure a community
list.
• Configure a basic community list:
ip community-list { basic-comm-list-num |
basic basic-comm-list-name } { deny | permit }
[ community-number&<1-32> | aa:nn&<1-32> ]
[ internet | no-advertise | no-export |
no-export-subconfed ] *
• Configure an advanced community list:
ip community-list { adv-comm-list-num |
advanced adv-comm-list-name } { deny |
permit } regular-expression
By default, no
community lists exist.
To Next Page
Loading...
Need help?
General