Commands For Routing Policy

8.1 Commands for Routing Policy

8.1.1 ip prefix-list description

Command: ip prefix-list <list-name> description <description>
no ip prefix-list <list-name> description
Function: Configure the prefix-list description. The no command deletes the description contents.
Parameters:

  • <list -name>: name of the prefix-list.
  • <description>: description of contents.

Command mode: Global Mode
Default: None.
Usage guide: This command can be used to describe a prefix-list. For example, the command can be used to describe the applications in the prefix-list.
Example: Configure the prefix-list descriptions.

active500EM#config terminal
active500EM(config)#ip prefix-list 3 description This list is used by BGP

 

8.1.2 ip prefix-list seq

Command: ip prefix-list <list-name> [seq <sequence-number>] <deny|permit> { any | <ip-addr/mask-length> } [ge <min-prefix-len>] [le <max-prefix-len>] no ip prefix-list <list-name> [seq <sequence-number>] <deny|permit> { any | <ip-addr/mask-length> } [ge <min-prefix-len>] [le <max-prefix-len>] Function: Configure the prefix-list. The no command deletes the prefix-list.
Parameters:

  • <list -name>: name of the prefix-list.
  • seq: Sequence number of an entry with the following parameters
  • <sequence-number>: sequence number. Range is <1-4294967295>.
  • deny: deny this route.
  • permit: permit this route.
  • any: can be used with all packets with any prefix as well as any mask length.
  • <ip-addr/mask-length>: IP prefix address and length (in dotted decimal notation A.B.C.D/M).
  • ge: means greater than or equal to the default.
  • <min-prefix-len>: minimum prefix length. The valid length is between 0 and 32.
  • le: means less than or equal to.
  • <max-prefix-len>: maximum prefix length. The valid length is between 0 and 32.

Command mode: Global Mode
Default: None.
Usage guide: A prefix-list is identified by a prefix-list name. Each prefix-list may include several items each of which independently specifies a matching scope of network prefix-list types identified by a sequence-number. Sequence-number specifies the matching sequence in the prefix-list. In the matching process, the switch verifies the sequence number in ascending order. Once the conditions are met, the prefix-list filter is passed (without proceeding to the next item in the sequence). At least one item in match mode should be set to ?permit? when more than one prefix-list item is defined. The deny mode items can be previously defined in order to remove the non-matching routing messages. If all items are set to deny mode, then none of the routes will pass the filter of the prefix-list. A ?permit 0.0.0.0/0 ge 0 le 32? item can be defined after several defined ?deny mode? items in order to grant passage for all other routing messages.
Example: Configure the prefix-list.

active500EM#config terminal
active500EM(config)#ip prefix-list mylist seq 12345 deny 10.0.0.0/8 ge 14 le 22

 

8.1.3 ip prefix-list sequence-number

Command: ip prefix-list sequence-number
no ip prefix-list sequence-number
Function: Enable the sequence-number auto-create function. The no command closes the prefix-list sequence-number.
Parameters: None.
Command mode: Global Mode
Default: Enabled.
Usage guide: This command can be used to close the prefix-list sequence-number.
Example:Enable the sequence-number auto-creation function.

active500EM(config)#no ip prefix-list sequence-number

 

8.1.4 match as-path

Command: match as-path <list-name>
no match as-path [<list-name>] Function: Configure the AS path domain to match the BGP routing messages. The no command deletes this configuration.
Parameters:

  • <list-name>: name of access-list.

Command mode: Route-map Mode
Default: None.
Usage guide: This command matches the BGP routing message AS path domains based on the rules specified in the as-path list. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the AS path domain for matching the BGP routing messages.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match as-path 60

 

8.1.5 match community

Command: match community <community-list-name | community-list-num> [exact-match] no match community [<community-list-name | community-list-num> [exact-match]] Function: Configure BGP routing messages community attributes. The no command deletes this configuration.
Parameters:

  • <community-list-name >: community-list name.
  • <community-list-num>: community-list sequence number. The valid range is between1 and 99 (Standard ACL) or 100 and 199 (Extended ACL).
  • [exact-match]: means precise matching.

Command mode: Route-map Mode
Default: None.
Usage guide: This command matches the BGP routing messages community attributes based on the rules specified in the community list. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the BGP routing messages community attributes.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match community 100 exact-match

 

8.1.6 match interface

Command: match interface <interface-name >
no match interface [<interface-name >] Function: Configure to match the interfaces. The no command deletes this configuration.
Parameters:

  • ?<interface-name>?: interface name.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match according to the next-hop messages in the route. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed. This command is only used in RIP and OSPF protocols.
Example: Configure to match the interfaces.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match interface vlan1

 

8.1.7 match ip

Command: match ip {address | next-hop} {<ip-acl-name> | <ip-acl-num> | prefix-list <list-name> }
no match ip {address | next-hop} [<ip-acl-name> | <ip-acl-num> | prefix-list <list-name>] Function: Configure the routing prefix or next-hop. The no command deletes this configuration.
Parameters:

  • address: matching the routing prefix.
  • next-hop: matching the routing next-hop
  • <ip-acl-name>: IP access-list name.
  • <ip-acl-num>: IP access-list sequence number. The valid range is between 1 and 199 or 1300 and 2699 (extension scope).
  • prefix-list: the matching should follow the prefix-list rules.
  • <list-name>: prefix-list name.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match based on the next-hop message or routing prefix in the route. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the routing prefix or next-hop.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match ip address prefix-list mylist

 

8.1.8 match ipv6 address

Command: match ipv6 address { <ipv6-acl-name> | prefix-list <list-name> }
no match ipv6 address [<ipv6-acl-name | prefix-list list-name>] Function: Configures ipv6 routing prefix. The no command removes the configuration.
Parameters:

  • address : routing prefix to be matched.
  • <ipv6-acl-name>: IPv6 access list name.
  • <list-name>: when the prefix-list is configured, the list name to be matched.

Command mode: Route-map Mode
Default : None.
Usage guide: When this command is enabled, the prefix-list in the routing table will be used for routing decisions. If there is a match, the ?permit? or ?deny? action in the route map will be performed.
Example:Configure the IPv6 routing prefix.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match ipv6 address prefix-list mylist

 

8.1.9 match ipv6 next-hop

Command:match ipv6 next-hop <ipv6-address>
no match ipv6 next-hop [<ipv6-address>] Function: Configure the next hop for IPv6 routing. The no command disables the configuration.
Parameters:

  • next-hop : next station for routing.
  • <ipv6-address>: IPv6 address for the IP address of the interface on the next station.

Command mode: Route-map Mode
Default: None.
Usage guide: If this command is configured, packets will be delivered according to the next hop information in the routing table. If there is a match, then the ?permit? or ?deny? action in the route map will be performed.
Example:Configure the next hop for ipv6 routing.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match ipv6 next-hop 2000::1

 

8.1.10 match metric

Command: match metric <metric-val>
no match metric [<metric-val>] Function: Match the metric value in the routing message. The no command deletes the configuration.
Parameters:

  • <metric-val >: metric value. The valid range is between 0 and 4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match based on the metric value in the route. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Match the metric value in the routing message.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match metric 60

 

8.1.11 match origin

Command: match origin {egp | igp | incomplete}
no match origin {egp | igp | incomplete}
Function: Configure the match with the origin of the BGP routing message. The no command deletes the configuration.
Parameters:

  • egp: route is learned from the external gateway protocols.
  • igp: route is learned from the internal gateway protocols.
  • incomplete: route origin is uncertain.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match based on the origin message in the BGP route. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the match with the origin of the BGP routing message.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match origin egp

 

8.1.12 match route-type

Command: match route-type external {type-1 | type-2}
no match route-type external [type-1 | type-2] Function: Configure the match with the OSPF routing message route type. The no command deletes the configuration.
Parameters:

  • type-1: match with the OSPF type 1 external route.
  • type-2: match with the OSPF type 2 external route.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match according to OSPF route type (OSPF AS-external LSA type is either type 1 or type 2). If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the match with the OSPF routing message route type.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match route-type external type-1

 

8.1.13 match tag

Command: match tag <tag-val>
no match tag [<tag-val>] Function: Configure the matching of the OSPF routing message tag domain. The no command deletes this configuration.
Parameters:

  • <tag-val>: tag value. The valid range is between 0 and 4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: This command performs a match according to the tag value in the OSPF route. If the match is successful, then the ?permit? or ?deny? action in the route-map is performed.
Example: Configure the matching of the OSPF routing messagetag domain.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match tag 60

 

8.1.14 route-map

Command: route-map <map-name> {deny | permit} <sequence-num>
no route-map <map-name> [{deny | permit} <sequence-num>] Function: Configure the route-map and enter the route-map mode. The no command deletes the route-map configuration.
Parameters:

  • <map-name>: the route-map name.
  • permit: sets route-map matching mode to permit mode.
  • deny sets route-map matching mode to permit mode (set sub will not be executed under this mode).
  • <sequence-num>: the route-map sequence number, ranging between 1-65535.

Command mode: Global Mode
Default: None.
Usage guide: A route-map may consist of several nodes, each of which has a checkpoint. The checkpoint sequence among nodes is identified by the sequence-number. ?Permit? means the node filter will be passed if the subsets match on the current route. All the subsets of this node will be passed without entering the checkpoint in the next node. If the subsets do not match, they proceed to the checkpoint in the next node. When a route-map is used for filtering routing messages, routing messages that cannot pass a node checkpoint will be denied by the route-map. If all nodes in the route-map are set to deny, all routing messages should pass that route-map.
Example: Configure the route-map for the active500EM.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#match as-path 60
active500EM(config-route-map)#set weight 30

 

8.1.15 set aggregator

Command: set aggregator as <as-number> <ip-addr>
no set aggregator as [<as-number> <ip-addr>] Function: Assign an AS number to the BGP aggregator. The no command deletes this configuration.
Parameters:

  • <as-number>: AS number.
  • <ip-addr>: IP address of the aggregator. The valid format is decimal notation.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause must first be defined.
Example: Assign an AS number to the BGP aggregator.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set aggregator as 200 10.1.1.1

 

8.1.16 set as-path

Command: set as-path prepend <as-num>
no set as-path prepend [<as-num>] Function: Add AS numbers in the BGP routing message AS path domain. The no command deletes this configuration.
Parameters:

  • <as-num>: AS number. The valid range is from 1 to 4294967295. The valid format is decimal notation (such as 6553700) or delimiter method (such as 100.100). Circulating the inputting of several numbers is available.

Command mode: Route-map Mode
Default: None.
Usage guide: Add an AS number in the BGP AS domain. The AS path length should be lengthened to the best neighbor path option. To use this command, one match clause must first be defined.
Example: Add AS numbers to the BGP routing message AS path domain.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set as-path prepend 200 100.100

 

8.1.17 set atomic-aggregate

Command: set atomic-aggregate
no set atomic-aggregate
Function: Configure the atomic aggregate attributes. The no command deletes this configuration.
Parameters: None.
Command mode: Route-map Mode
Default: None.
Usage guide: The BGP informs other BGPs by the atomic aggregate attributes. The local system selects a sub-specified route. To use this command, one match clause must first be defined.
Example: Configure the atomic aggregate attributes.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set atomic-aggregate

 

8.1.18 set comm-list

Command: set comm-list { <community-list-name> | <community-list-num> } delete
no set comm-list { <community-list-name> | <community-list-num> } delete
Function: Configures the deletion of the community attributes in the inbound or outbound routing messages. The no command deletes the configuration.
Parameters:

  • <community-list-name >: community list name.
  • <community-list-num>: community listsequence number. The valid range is between 1 and 99 (standard community list) or 100 and 199 (extended community list).

Command mode: route-map mode
Default: None.
Example: Configure the deletion of the community attributes in the inbound or outbound routing messages.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set comm-list 100 delete

 

8.1.19 set community

Command: set community [AA:NN] [internet] [local-AS] [no-advertise] [no-export] [none] [additive] no set community [AA:NN] [internet] [local-AS] [no-advertise] [no-export] [none] [additive] Function: Configures the BGP routing message community attributes. The no command deletes this configuration.
Parameters:

  • [AA:NN]: the community attribute value.
  • [internet]: the internet scope.
  • [local-AS]: this route does not announce outside the local AS (but can announce among the sub AS within the group).
  • [no-advertise]: this route does not send to any neighbor.
  • [no-export]: this route does not send to EBGP neighbors.
  • [none]: delete the community attributes from the prefix of this route.
  • [additive]: add existing community attributes.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause should be defined first.
Example: Configure the BGP routing message community attributes.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set community local-as additive

 

8.1.20 set extcommunity

Command: set extcommunity {rt | soo} <AA:NN>
no set extcommunity {rt | soo} [<AA:NN>] Function: Configure the BGP routing message extended community attributes. The no command deletes this configuration.
Parameters:

  • rt: route target.
  • soo: site of origin.
  • <AA:NN>: value of community attributes. The valid range is from 1 to 4294967295 and the valid format is decimal notation (such as 6553700) or delimiter (such as 100.100). NN is a random two byte number.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause must first be defined.
Example: Set route target as 100:10

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set extcommunity rt 100:10

Set site of origin as 200.200:10

active500EM(config)#route-map r1 permit 10
active500EM(config-route-map)#set extcommunity soo 200.200:10

 

8.1.21 set ip next-hop

Command: set ip next-hop <ip-addr>
no set ip next-hop [<ip-addr>] Function: Configure the next-hop of the route. The no command deletes the configuration.
Parameters:

  • <ip-addr >: the IP address of the next-hop. Values are shown in dotted decimal notation.

Command mode: Route-map Mode
Default: None.
Usage guide: Configure the next-hop of the route.
Example: Configure the next-hop of the route on the active500EM.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set ip next-hop 10.2.2.2

 

8.1.22 set local-preference

Command: set local-preference <pre-val>
no set local-preference [<pre-val>] Function: Configure the BGP route local priority. The no command deletes this configuration.
Parameters:

  • <pre-val>: value of the local priority. The valid range is between 0 and 4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: The local priority attribute is the priority level of a route. A route with a higher local priority level, when compared with other routes of the same destination, will be used first. The local priority validates only within this AS and will not be transported to EBGP neighbors. To use this command, one match clause should first be defined.
Example: Configure the BGP route local priority.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set local-preference 60

 

8.1.23 set metric

Command: set metric < metric-val>
no set metric [< metric-val>] Function: Configure the metric value of the route. The no command deletes the configuration.
Parameters:

  • <metric-val >: the metric value, ranging between 1-4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: The metric value affects the path option from external neighbors to local AS. A lower metric value means a higher priority. Under normal circumstances, only the path metric value of the neighbors of the same AS will be compared. To extend the comparison to the metric values of different neighbor paths, the BGP always-compare-med command should be configured. To use this command, one match clause should be defined.
Example: Configure the metric value of the route.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set metric 60

 

8.1.24 set metric-type

Command: set metric-type {type-1 | type-2}
no set metric-type [type-1 | type-2] Function: Configure the OSPF routing message metric type. The no command deletes this configuration.
Parameters:

  • type-1: matches the OSPF type 1 external route.
  • type-2: matches the OSPF type 2 external route.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause should first be defined.
Example: Configure the OSPF routing message metric type.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set metric-type type-1

 

8.1.25 set origin

Command: set origin {egp | igp | incomplete}
no set origin [egp | igp | incomplete] Function: Configure the BGP routing message origin code. The no command deletes this configuration.
Parameters:

  • egp: the route is learned from the external gateway protocols.
  • igp: the route is learned from the internal gateway protocols.
  • incomplete: the route origin is uncertain.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause should first be defined.
Example: Configure the BGP routing message origin code.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set origin egp

 

8.1.26 set originator-id

Command: set originator-id <ip-addr>
no set originator-id [<ip-addr>] Function: Configure the BGP routing message origin IP address. The no command deletes the configuration.
Parameters:

  • <ip-addr>: route source IP address. The valid format is dotted decimal notation.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause should first be defined.
Example: Configure the BGP routing message origin IP address.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set originator-id 10.1.1.1

 

8.1.27 set tag

Command: set tag <tag-val>
no set tag [<tag-val>] Function: Configure the OSPF routing message tag domain. The no command deletes this configuration.
Parameters:

  • <tag-val>: tag value. The valid range is between 0 and 4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: There is a route-tag domain at the AS-external-LSA type LSA. The domain is normally identified by other routing protocols. To use this command, one match clause should first be defined.
Example: Configure the OSPF routing message tag domain.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set tag 60

 

8.1.28 set vpnv4 next-hop

Command: set vpnv4 next-hop <ip-addr>
no set vpnv4 next-hop [<ip-addr>] Function: Configure the BGP VPNv4 routing message next-hop. The no command deletes the configuration.
Parameters:

  • <ip-addr>: VPNv4 route next-hop ip address. The valid format is decimal notation.

Command mode: Route-map Mode
Default: None.
Usage guide: To use this command, one match clause should first be defined.
Example: Configure the BGP VPNv4 routing message next-hop.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set vpnv4 next-hop 10.1.1.1

 

8.1.29 set weight

Command: set weight <weight-val>
no set weight [<weight-val>] Function: Configure the weight of BGP routing messages. The no command deletes this configuration.
Parameters:

  • <weight-val>: weight value, ranging between 0-4294967295.

Command mode: Route-map Mode
Default: None.
Usage guide: Weight facilitates the identification of the best path. While there are several routes to the same destination, the one with higher priority is preferred. To use this command, the match clause should be defined.
Example: Configure the weight of BGP routing messages.

active500EM#config terminal
active500EM(config)#route-map r1 permit 5
active500EM(config-route-map)#set weight 60

 

8.1.30 show ip prefix-list

Command: show ip prefix-list [<list-name> [<ip-addr/len> [first-match | longer] | seq <sequence-number>]] Function: Show by prefix-list names.
Parameters:

  • <list-name>: prefix-list name.
  • <ip-addr/len>: prefix IP address and the mask length.
  • first-match: stands for the first route table matched with a specified IP address.
  • longer: longer prefix required.
  • seq: show by sequence number.
  • <sequence-number>: sequence number. The valid range is between 0 and 4294967295.

Command mode: Admin Mode
Default: None.
Usage guide: All prefix-list will be listed when no prefix-list name is specified.
Example: Show by prefix-list names.

active500EM#show ip prefix-list
ip prefix-list 1: 1 entries
deny any
ip prefix-list mylist: 1 entries
deny 1.1.1.1/8
active500EM#show ip prefix-list mylist 1.1.1.1/8
seq 5 deny 1.1.1.1/8 (hit count: 0, recount: 0)
Displayed information Explanation
ip prefix-list mylist: 1 entries Show a prefix-list named mylist which includes 1 entry.
seq 5 deny 1.1.1.1/8 (hit count: 0, recount: 0) Show the prefix-list contents sequence numbered 5. hit count: 0 means being hit 0 times.recount: 0 means referred 0 times.

 

8.1.31 show ip prefix-list (detail | summary)

Command: show ip prefix-list [ {detail | summary} [<list-name>] ] Function: Display the contents of the prefix list.
Parameters:

  • detail: when detail is enabled, prefix-list details will be displayed.
  • summary: when summary is enabled, only a prefix-list summary will be displayed.
  • <list-name>: name of the prefix list.

Command mode: Privileged Mode and Configuration Mode
Default: None.
Usage guide: If no prefix list name is specified, all the prefix lists will be displayed.
Example: Display the contents of the prefix list.

active500EM#show ip prefix-list detail mylist
ip prefix-list mylist:
count: 2, range entries: 0, sequences: 5 - 10
seq 5 deny 1.1.1.1/8 (hit count: 0, refcount: 0)
seq 10 permit 2.2.2.2/8 (hit count: 0, refcount: 0)
active500EM#show ip prefix-list summary mylist
ip prefix-list mylist:
count: 2, range entries: 0, sequences: 5 ? 10
Displayed information Explanation
ip prefix-list mylist: Display the prefix list named mylist.
count: 2, range entries: 0, sequences: 5 – 10 count : 2 means there are two prefix list instances. sequences: 5-10 means the sequence number. 5 is the starting sequence number. 10 is the ending number.
deny 1.1.1.1/8 (hit count: 0, refcount: 0) deny 1.1.1.1/8 is the content of the prefix list. hit count:0 means the rule has been matched zero times. And refcount:0 means the rule is referenced zero times.

 

8.1.32 show route-map

Command: show route-map
Function: Display the route-map information.
Parameters: None.
Command mode: Admin Mode
Default: None.
Usage guide: Displays the route-map information.
Example: Display the route-map for the active500EM.

active500EM# show route-map
route-map a, deny, sequence 10
Match clauses:
as-path 60
Set clauses:
metric 10
Displayed information Explanation
route-map a, deny, sequence 10 route-map a means the name of route map is a, deny means the deny mode, sequence 10 means the sequence number is 10
Match clauses: Match sub
as-path 60 Detailed contents in the Match sub
Set clauses: Set sub
metric 10 Detailed content in the Set clause

 

8.1.33 show router-id

Command: show router-id
Function: Show the content of the router-id.
Parameters: None.
Command mode: Admin and Configuration Mode
Default: None.
Usage guide: Shows the content of the router-id.
Examples: Show the content of the router-id.

active500EM#show router-id
Router ID: 20.1.1.1 (automatic)
active500EM#show router-id
Router ID: 20.1.1.2 (config)

 


Return to Controller Wired CLI Table of Contents