Edge-Core ES4624-SFP Programming manual

Content
www.edge-core.com
ES4624-SFP/ES4626-SFP
Routing Management
Guide

2
Content
CHAPTER 1 ROUTING PROTOCOL ...........................................................................................4
1.1 ROUTING PROTOCOL OVERVIEW.............................................................................................4
1.1.1 Routing Table.................................................................................................................5
1.2 IPROUTING POLICY................................................................................................................6
1.2.1 Introduction to Routing Policy........................................................................................6
1.2.2 IP Routing Policy Configuration Task List......................................................................7
1.2.3 Commands for Routing Policy.....................................................................................12
1.2.4 Configuration Examples ..............................................................................................24
1.2.5 Troubleshooting...........................................................................................................25
1.3 STATIC ROUTE......................................................................................................................28
1.3.1 Introduction to Static Route .........................................................................................28
1.3.2 Introduction to Default Route.......................................................................................29
1.3.3 Static Route Configuration Task List............................................................................29
1.3.4 Commands for Static Route.........................................................................................30
1.3.5 Configuration Examples ..............................................................................................32
1.4 RIP......................................................................................................................................33
1.4.1 Introduction to RIP.......................................................................................................33
1.4.2 RIP Configuration Task List.........................................................................................34
1.4.3 Commands for RIP......................................................................................................41
1.4.4 RIP Examples..............................................................................................................56
1.4.5 RIP Troubleshooting....................................................................................................59
1.5 RIPNG .................................................................................................................................65
1.5.1 Introduction to RIPng...................................................................................................65
1.5.2 RIPng Configuration Task List.....................................................................................67
1.5.3 Commands For RIPng.................................................................................................71
1.5.4 RIPng Configuration Examples
...................................................................................77
1.5.5 RIPng Troubleshooting................................................................................................80
1.6 OSPF..................................................................................................................................85
1.6.1 Introduction to OSPF...................................................................................................85
1.6.2 OSPF Configuration Task List.....................................................................................89
1.6.3 Commands for OSPF ..................................................................................................94
1.6.4 OSPF Example.......................................................................................................... 116
1.6.5 OSPF Troubleshooting..............................................................................................125
1.7 OSPFV3............................................................................................................................136
1.7.1 Introduction to OSPFv3.............................................................................................136

3
1.7.2 OSPFv3 Configuration Task List ...............................................................................140
1.7.3 Commands for OSPFV3............................................................................................145
1.7.4 OSPFv3 Examples....................................................................................................155
1.7.5 OSPFv3 Troubleshooting..........................................................................................157
1.8 BGP..................................................................................................................................167
1.8.1 BGP Introduction .......................................................................................................167
1.8.2 BGP Configuration Task List......................................................................................170
1.8.3 Commands for BGP ..................................................................................................183
1.8.4 Configuration Examples of BGP................................................................................219
1.8.5 BGP Troubleshooting ................................................................................................228
1.9 MBGP4+...........................................................................................................................241
1.9.1 MBGP4+ Introduction................................................................................................241
1.9.2 MBGP4+ Configures Mission List .............................................................................241
1.9.3 Command For BGP4+...............................................................................................243
1.9.4 MBGP4+ Examples...................................................................................................244
1.9.5 MBGP4+ Troubleshooting.........................................................................................246
CHAPTER 2 BLACK HOLE ROUTING MANUAL ...................................................................247
2.1 INTRODUCTION TO BLACK HOLE ROUTING...........................................................................247
2.2 IPV4BLACK HOLE ROUTING CONFIGURATION TASKS...........................................................247
2.3 IPV6BLACK HOLE ROUTING CONFIGURATION TASK.............................................................247
2.4 BLACK HOLE ROUTING COMMAND.......................................................................................248
2.4.1 ip route null0..............................................................................................................248
2.4.2 ipv6 route null0 ..........................................................................................................248
2.5 BLACK HOLE ROUTING CONFIGURATION EXMAPLE ..............................................................249
2.6 BLACK HOLE ROUTING TROUBLE SHOOTING .......................................................................251
CHAPTER 3 ECMP CONFIGURATION ....................................................................................252
3.1 INTRODUCTION TO ECMP...................................................................................................252
3.2 ECMP CONFIGURATION TASK LIST......................................................................................252
3.3 COMMANDS FOR ECMP .....................................................................................................253
3.3.1 maximum-paths.........................................................................................................253
3.4 ECMP TYPICAL EXAMPLE...................................................................................................253
3.4.1 Static Route Implements ECMP................................................................................253
3.4.2 OSPF Implements ECMP..........................................................................................254

4
Chapter 1 Routing Protocol
1.1 Routing Protocol Overview
To communicate with a remote host over the Internet, a host must choose a proper route via
a set of routers or Layer3 switches.
Both routers and layer3 switches calculate the route using CPU, the difference is that layer3
switch adds the calculated route to the switch chip and forward by the chip at wire speed, while
the router always store the calculated route in the route table or route buffer, and data forwarding
is performed by the CPU. For this reason, although both routers and switches can perform route
selection, layer3 switches have great advantage over routers in data forwarding. The following
describes basic principle and methods used in layer3 switch route selection.
In route selection, the responsibility of each layer3 switch is to select a proper midway route
according to the destination of the packet received; and send the packet to the next layer3switch
until the last layer3 switch in the route send the packet to the destination host. A route is the path
selected by each layer3 switch to pass the packet to the next layer3 switch. Route can be
grouped into direct route, static route and dynamic route.
Direct route refer to the path directly connects to the layer3 switch, and can be obtained with
no calculation.
Static route is the manually specified path to a network or a host; static route cannot be
changed freely. The advantage of static route is simple and consistent, and it can limit illegal
route modification, and is convenient for load balance and route backup. However, as this is set
manually, it is not suitable for mid- or large-scale networks for the route in such conditions are
too huge and complex.
Dynamic route is the path to a network or a host calculated by the layer3 switch according to
the routing protocols enabled. If the next hop layer3 switch in the path is not reachable, layer3
switch will automatically discard the path to that next hop layer3 switch and choose the path
through other layer3 switches.
There are two dynamic routing protocols: Interior Gateway Protocol (IGP) and Exterior
Gateway protocol (EGP). IGP is the protocol used to calculate the route to a destination inside
an autonomous system. IGP supported by ES4624-SFP/ES4626-SFP switch include RIP and
OSPF, RIP and OSRF can be configured according to the requirement.
ES4624-SFP/ES4626-SFPswitch supports running several IGPdynamic routing protocols at the
same time. Or, other dynamic routing protocols and static route can be introduced to a dynamic
routing protocol, so that multiple routing protocols can be associated.
EGP is used to exchange routing information among different autonomous systems, such as

5
BGP protocol. EGP supported by ES4624-SFP/ES4626-SFP switch include BGP-4, BGP-4+.
1.1.1 Routing Table
As mentioned before, layer3 switch is mainly used to establish the route from the current
layer3 switch to a network or a host, and to forward packets according to the route. Each layer3
switch has its own route table containing all routes used by that switch. Each route entry in the
route table specifies the physical port should be used for forwarding packet to reach a
destination host or the next hop layer3 switch to the host.
The route table mainly consists of the following:
Destination address: used to identify the destination address or destination network of an IP
packet.
Network mask: used together with destination address to identify the destination host or the
network the layer3 switch resides. Network mask consists of several consecutive binary 1's, and
usually in the format of dotted decimal (an address consists of 1 to 4 255’s.) When “AND” the
destination address with network mask, we can get the network address for the destination host
or the network the layer3 switch resides. For example, the network address of a host or the
segment the layer3 switch resides with a destination address of 200.1.1.1 and mask
255.255.255.0 is 200.1.1.0.
Output interface: specify the interface of layer3 switch to forward IP packets.
IP address of the next layer3 switch (next hop): specify the next layer3 switch the IP packet
will pass.
Route entry priority: There may be several different next hop routes leading to the same
destination. Those routes may be discovered by different dynamic routing protocols or static
routes manually configured. The entry with the highest priority (smallest value) becomes the
current best route. The user can configure several routes of different priority to the same
destination; layer3 switch will choose one route for IP packet forwarding according to the priority
order.
To prevent too large route table, a default route can be set. Once route table look up fails,
the default route will be chosen for forwarding packets.
The table below describes the routing protocols supported by ES4624-SFP/ES4626-SFP
switch and the default route look up priority value.
Routing Protocols or route type
Default priority value
Direct route
0
OSPF
110
Static route
1
RIP
120
OSPF ASE
150

6
IBGP
200
EBGP
20
Unknown route
255
1.2 IP Routing Policy
1.2.1 Introduction to Routing Policy
Some policies have to be applied when the router publishing and receiving routing
messages so to filter routing messages, such as only receiving or publishing routing messages
meets the specified conditions. A routing protocol maybe need redistribute other routing
messages found by other protocols such as OSPF so to increase its own routing knowledge;
when the router redistributing routing messages from other routing protocols there may be only
part of the qualified routing messages is needed, and some properties may have to be
configured to suit this protocol.
To achieve routing policy, first we have to define the characteristics of the routing messages
to be applied with routing policies, namely define a group matching rules. We can configure by
different properties in the routing messages such as destination address, the router address
publishing the routing messages. The matching rules can be previously configured to be applied
in the routing publishing, receiving and distributing policies.
Five filters are provided in ES4624-SFP/ES4626-SFP switch: route-map, acl, as-path,
community-list and ip-prefix for use. We will introduce each filter in following sections:
1. route-map
For matching certain properties of the specified routing information and setting some routing
properties when the conditions are fulfilled.
Route-map is for controlling and changing the routing messages while also controlling the
redistribution among routes. A route-map consists of a series of match and set commands in
which the match command specifies the conditions required matching, and the set command
specifies the actions to be taken when matches. The route-map is also for controlling route
publishing among different route process. It can also used on policy routing which select
different routes for the messages other than the shortest route.
A group matches and set clauses make up a node. A route-map may consist of several
nodes each of which is a unit for matching test. We match among nodes with by
sequence-number. Match clauses define matching rules. The matching objects are some
properties of routing messages. Different match clause in the same node is “and” relation
logically, which means the matching test of a node, will not be passed until conditions in its entire
match clause are matched. Set clause specifies actions, namely configure some properties of

7
routing messages after the matching test is passed.
Different nodes in a route-map is an “or” relation logically. The system checks each node of
the route-map in turn and once certain node test is passed the route-map test will be passed
without taking the next node test.
2. access control list(acl)
ACL (Access Control Lists) is a data packet filter mechanism in the switch. The switch
controls the network access and secure the network service by permitting or denying certain
data packet transmtting out from or into the network. Users can establish a group of rules by
certain messages in the packet, in which each rule to be applied on certain amount of matching
messages: permit or deny. The users can apply these rules to the entrance or exit of specified
switch, with which data stream in certain direction on certain port would have to follow the
specified ACL rules in-and-out the switch. Please refer to chapter “ACL Configuration”.
3. Ip-prefix list
The ip-prefix list acts similarly to acl while more flexible and more understandable. The
match object of ip-prefix is the destination address messages field of routing messages when
applied in routing messages filtering.
An ip-prefix is identified by prefix list name. Each prefix list may contain multiple items, each
of which specifies a matching range of a network prefix type and identifies with a
sequence-number which specifies the matching check order of ip-prefix.
In the process of matching, the switch check each items identified by sequence-number in
ascending order and the filter will be passed once certain items is matched( without checking
rest items)
4. Autonomic system path information access-list as-path
The autonomic system path information access-list as-path is only used in BGP. In the BGP
routing messages packet there is an autonomic system path field (in which autonomic system
path the routing messages passes through is recorded). As-path is specially for specifying
matching conditions for autonomic system path field.
As for relevant as-path configurations, please refer to the ip as-path command in BGP
configuration.
5. community-list
Community-list is only for BGP. There is a community property field in the BGP routing
messages packet for identifying a community. The community list is for specifying matching
conditions for Community-list field.
As for relevant Community-list configuration, please refer to the ip as-path command in BGP
configuration
1.2.2 IP Routing Policy Configuration Task List

8
1、Define route-map
2、Define the match clause in route-map
3、Define the set clause in route-map
4、Define address prefix list
1. Define route-map
Command
Explanation
Global mode
route-map <map_name>
{deny | permit}
<sequence_num>
no route-map <map_name>
[{deny | permit}
<sequence_num>]
Configure route-
map; the
no route-map
<map_name>
[{deny |
permit}
<sequence_num>]
command deletes the
route-map
2. Define the match clause in route-map
Command
Explanation
Route-map configuration mode
match as-path <list-name>
no match as-path [<list-name>]
Match the autonomous
system as path access-list
the BGP route passes
through; the
no match
as-path [<list-name>]
command deletes match
condition
match community <community-list-nam
e |
community-list-num > [exact-match]
no match community [<community-list-nam
e |
community-list-num > [exact-match]]
Match a community
property access-
list. The
no match community
[<community-list-nam
e |
community-list-num >
[exact-match]] command
deletes match condition
match interface <interface-name >
no match interface [<interface-name >]
Match by ports; The no
match interface
[<interface-nam
e >]
command deletes match
condition

9
match ip <address | next-hop> <ip-acl-nam
e |
ip-acl-num | prefix-list list-name>
no match ip <address | next-hop> [<ip-acl-name |
ip-acl-num | prefix-list [list-name]>]
Match th
e address or
next-hop; The
no match
ip <address | next-hop>
[<ip-acl-nam
e |
ip-acl-num | prefix-list
[list-name]>] command
deletes match condition
match metric <metric-val >
no match metric [<metric-val >]
Match the routing metric
value; The
no match
metric [<metric-val >]
command deletes match
condition
match origin <egp | igp | incomplete >
no match origin [<egp | igp | incomplete >]
Match the route origin;
The no match origin
[<egp | igp |
incomplete >] command
deletes match condition
match route-type external <type-1 | type-2 >
no match route-type external [<type-1 | type-2 >]
Match the route type; The
no match route-type
external [<type-
1 |
type-2 >] command
deletes match condition
match tag <tag-val >
no match tag [<tag-val >]
Match the route tag; The
no match tag [<tag-val >]
command deletes match
condition
3. Define the match clause in route-map
Command
Explanation
Route-map configuration mode
set aggregator as <as-number> <ip_addr>
no set aggregator as [<as-number> <ip_addr>]
Distribute
an AS No. for
BGP aggregator; The no
set aggregator as
[<as-number>
<ip_addr>] command
deletes the configuration

10
set as-path prepend <as-num>
no set as-path prepend [<as-num>]
Add a specified AS No.
before the BGP routing
messages as-path series;
The no set as-path
prepend [<as-num>]
command deletes the
configuration
set atomic-aggregate
no set atomic-aggregate
Configure the BGP atomic
aggregate property; The
no set atomic-aggregate
command deletes the
configuration
set comm-list <community-list-name |
community-list-num > delete
no set comm-list <community-list-nam
e |
community-list-num > delete
Delete BGP community list
value; The
no set
comm-list
<community-list-nam
e |
community-list-num >
delete
command deletes
the configuration
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]
Configure BGP community
list value; The
no set
community [AA:NN]
[internet] [local-AS]
[no-advertise]
[no-
export] [none]
[additive] command
deletes the configuration
set extcommunity <rt | soo> <AA:NN>
no set extcommunity <rt | soo> [<AA:NN>]
Configure BGP extended
community list property;
The
no set
extcommunity <rt | soo>
[<AA:NN>] command
deletes the configuration
set ip next-hop <ip_addr>
no set ip next-hop [<ip_addr>]
Set next-hop IP address;
The no set ip next-hop
[<ip_addr>] command
deletes the configuration

11
set local-preference <pre_val>
no set local-preference [<pre_val>]
Set local preference; The
no set local-preference
[<pre_val>] command
deletes the configuration
set metric < +/- metric_val | metric_val>
no set metric [+/- metric_val | metric_val]
Set routing metric value;
The no set metric [+/-
metric_val | metric_val]
command delet
es the
configuration
set metric-type <type-1 | type-2>
no set metric-type [<type-1 | type-2>]
Set OSPF metric type;
The no set metric-type
[<type-1 | type-2>]
command deletes the
configuration
set origin <egp | igp | incomplete >
no set origin [<egp | igp | incomplete >]
Set BGP routing origin;
The
no set origin [<egp |
igp | incomplete >]
command deletes the
configuration
set originator-id <ip_addr>
no set originator-id [<ip_addr>]
Set routing originator ID;
The no set originator-id
[<ip_addr>] command
deletes the configuration
set tag <tag_val>
no set tag [<tag_val>]
Set OSPF routing tag
value; The
no set tag
[<tag_val>] command
deletes the configuration
set vpnv4 next-hop <ip_addr>
no set vpnv4 next-hop [<ip_addr>]
Set BGP VPNv4 next-hop
address; the no set vpnv4
next-hop [<ip_addr>]
command deletes the
configuration
set weight <weight_val>
no set weight [<weight_val>]
Set BGP routing weight;
The
no set weight
[<weight_val>] command
deletes the configuration
4. Define address prefix list

12
Command
Explanation
Global mode
ip prefix-list <list_name> description <description>
no ip prefix-list <list_name> description
Describe the prefix list;
The no ip prefix-list
<list_name
> description
command deletes the
configuration
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]>]
Set the prefix list; The no
ip prefix-list <list_name>
[seq
<sequence_number>]
[<deny | permit> < any |
ip_addr/mask_length [ge
min_prefix_len][le
max_prefix_len]>]
command deletes the
configuration
ip prefix-list sequence-number
no ip prefix-list sequence-number
Enable the
sequence-number
auto-creation function, the
“no ip prefix-list
sequence-number”
command close the
prefix-list
sequence-number.
1.2.3 Commands for Routing Policy
1.2.3.1 ip prefix-list description
Command: ip prefix-list <list_name> description <description>
no ip prefix-list <list_name> description
Function: Configure the description of the prefix-list. The “no ip prefix-list <list_name>
description“ command deletes the description contents.
Parameter: <list _name> is the name of the prefix-list, <description> is the description
contents
Default: None.
Command Mode: Global Mode

13
Usage Guide: This command can be used for explaining and describing a prefix-list, e.g. the
application and attention matters of the prefix-list
Example:
Switch#config terminal
Switch(config)#ip prefix-list 3 description This list is used by BGP
1.2.3.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 ip prefix-list <list_name> [seq
<sequence_number>] [<deny | permit> < any | ip_addr/mask_length [ge <min_prefix_len>]
[le <max_prefix_len>]>]” command deletes the prefix-list.
Parameter: <list _name> is the name of prefix-list, “seq” shows the following parameters is the
sequence number, <sequence_number>is the sequence number, “deny” means deny this
route, “permit” means permit this route, “any” means adaptive to all packets with any prefix as
well as any mask length, ip_addr/mask_length shows the prefix address (dotted decimal
notation) and the length of mask, “ge” means greater than or equal to, <min_prefix_len> is the
minimum length of prefix to be matched（ranging between 0～32）, “le” means less than or equal
to, <max_prefix_len> is the maximum length of prefixto be matched（ranging between 0～32）.
Default: None.
Command Mode: Global Mode
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 type which is
identified with a sequence-number. sequence-number specifies the sequence of matching check
in the prefix-list. In the matching process the switch check in turn every items identified by
“sequence-number” ascending. Once certain item obtains the conditions then the prefix-list filter
is passed (without proceeding into the next item check)
Attentions should be paid on that at least one item match mode should be “permit” when
more than one prefix-list items is defined. The deny mode items can be previously defined so to
remove the unsuitable routing messages fast. However if all items are at deny mode then none
of the routes would be able to pass the filter of this prefix-list. We here can define a “permit
0.0.0.0/0 ge 0 le 32” item after several defined “deny mode” items so to grant the passage for all
other routing messages.
Example:
Switch#config terminal
Switch(config)#ip prefix-list mylist seq 12345 deny 10.0.0.0/8 le 22 ge 14

14
1.2.3.3 ip prefix-list sequence-number
Command: ip prefix-list sequence-number
no ip prefix-list sequence-number
Function: Enable the sequence-number auto-creation function, the “no ip prefix-list
sequence-number” command close the prefix-list sequence-number.
Parameter：None.
Default: Sequence-number auto-creation enabled.
Command Mode: Global Mode
Usage Guide: The command can be used to close the prefix-list sequence-number.
Example: Close the prefix-list sequence-number.
Switch(config)#no ip prefix-list sequence-number
1.2.3.4 match as-path
Command: match as-path <list-name>
no match as-path [<list-name>]
Function: Configure the AS path domain for matching the BGP routing messages. The “no
match as-path [<list-name>]” delete this configuration.
Parameter: <list-name > is the name of access-list
Command Mode: route-map mode
Usage Guide: This command matches the AS path domain of the BGP routing message
following the rules specified in the as-path list. If the matching succeeded, then the “permit” or
“deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match as-path 60
1.2.3.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 the community attributes of BGP routing messages. The “no match
community [<community-list-name | community-list-num > [exact-match]]” command
deletes this configuration.
Parameter: <community-list-name> is the name of the community-list,
<community-list-num>is the community-list sequence number, ranging between 1～99

15
（Standard ACL）or 100～199（Extended ACL）, [exact-match] means precise matching.
Command Mode: route-map mode
Usage Guide: This command matches the community attributes of the BGP routing message
following the rules specified in the community list. If the matching succeeded, then the “permit”
or “deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match community 100 exact-match
1.2.3.6 match interface
Command: match interface <interface-name >
no match interface [<interface-name >]
Function: Configure to match the interfaces. The “no match interface
[<interface-name >]“ deletes this configuration.
Parameter: “<interface-name >“ is the name of the interface.
Command Mode: route-map mode
Usage Guide: This command matches according to the next-hop messages in the route. If the
matching succeeded, then the “permit” or “deny” action in the route-map is performed. This
command is only used in RIP and OSPF protocols.
Example: Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match interface vlan1
1.2.3.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 match ip <address | next-hop>
[<ip-ACL-name | ip-ACL-num | prefix-list list-name>]” deletes this configuration.
Parameter: <address > means matching the routing prefix, <next-hop>means matching the
routing next-hop, <ip-ACL-name > is the name of ip access-list, <ip-ACL-num > is the ip
access-list sequence number, ranging between 1～199 or 1300～2699（extension scope）,
prefix-list means the matching should follow the prefix-list rules, list-name is the name of
prefix-list.
Command Mode: route-map mode
Usage Guide: This command matches according to the next-hop messages or routing prefix in

16
the route. If the matching succeeded, then the “permit” or “deny” action in the route-map is
performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match ip address prefix-list mylist
1.2.3.8 match metric
Command: match metric <metric-val >
no match metric [<metric-val >]
Function: Match the metric value in the routing message. The “no match metric
[<metric-val >]” deletes the configuration.
Parameter: <metric-val > is the metric value, ranging between 0～4294967295.
Command Mode: route-map mode
Usage Guide: This command matches according to metric value in the route. If the matching
succeeded, then the “permit” or “deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match metric 60
1.2.3.9 match origin
Command: match origin <egp | igp | incomplete >
no match origin <egp | igp | incomplete >
Function: Configure to matching with the origin of the BGP routing message. The “no match
origin <egp | igp | incomplete >“ deletes the configuration.
Parameter: egp means the route is learnt from the external gateway protocols, igp means the
route is learnt from the internal gateway protocols, incomplete means the route origin is
uncertain.
Command Mode: route-map mode
Usage Guide: This command matches according to origin message in the BGP route. If the
matching succeeded, then the “permit” or “deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match origin egp
1.2.3.10 match route-type

17
Command: match route-type external <type-1 | type-2 >
no match route-type external [<type-1 | type-2 >]
Function: Configure to matching with the route type of OSPF routing message. The “no match
route-type external [<type-1 | type-2 >]” deletes the configuration.
Parameter: type-1 means match with the OSPF type 1 external route, type-2 means match with
the OSPF type 2 external route.
Command Mode: route-map mode
Usage Guide: This command matches according to the type of OSPF routes （OSPF
AS-external LSA type is either type 1 or type 2）. If the matching succeeded, then the “permit” or
“deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match route-type external type-1
1.2.3.11 match tag
Command: match tag <tag-val >
no match tag [<tag-val >]
Function: Configure to matching with the tag domain of the OSPF routing message. The “no
match tag [<tag-val >]” deletes this configuration.
Parameter: <tag-val > is the tag value, ranging between 0～4294967295.
Command Mode: route-map mode
Usage Guide: This command matches according to the tag value in the OSPF route. If the
matching succeeded, then the “permit” or “deny” action in the route-map is performed.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match tag 60
1.2.3.12 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 entering the route-map mode. The “no route-map
<map_name> [{deny | permit} <sequence_num>]” command deletes route-map.
Parameter: <map_name> is the name of route-map, 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> is the route-map sequence number, ranging between 1～
65535.

18
Default: None
Command Mode: Global Mode
Usage Guide: A route-map may consist of several nodes each of which is a check unit. The
check sequence among nodes is identified by sequence-number. “permit” means the node filter
will be passed if all match subs are obtained by current route and then further all the set sub of
this node will be executed without entering the check in the next node; if the match subs can not
be met, the proceed to the check in next node. Relation among different node should be “or”,
namely one node check passed then the route filter is passed when the switch checks each
node in turn in the route-map.
Attentions should be paid on that at least one node match mode should be “permit” when
more than one node is defined. When a route-map is used for filtering routing messages, if
certain routing message can not pass any node check, then it is considered denied by the
route-map. If all nodes in the route-map are set to deny mode, then all routing message should
not be able to pass that route-map.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#match as-path 60
Switch(config-route-map)#set weight 30
1.2.3.13 set aggregator
Command: set aggregator as <as-number> <ip_addr>
no set aggregator as [<as-number> <ip_addr>]
Function: Assign an AS number for BGP aggregator. The “no set aggregator as
[<as-number> <ip_addr>]” deletes this configuration.
Parameter: <as-number > is the AS number, <ip_addr> is the ip address of the aggregator
shown in decimal notation.
Command Mode: route-map mode
Usage Guide: To use this command, one match clause should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set aggregator as 200 10.1.1.1
1.2.3.14 set as-path
Command: set as-path prepend <as-num>
no set as-path prepend [<as-num>]
Function: Add AS numbers in the AS path domain of the BGP routing message. The “no set

19
as-path prepend [<as-num>]” command deletes this configuration.
Parameter: <as-num > is the AS number, ranging from 1 to 4294967295, it can be shown in
decimal notation (such as 6553700) or delimiter method (such as 100.100), circulating inputting
several numbers is available.
Command Mode: route-map mode
Usage Guide: To add AS number in the As domain of the BGP, the AS path length should be
lengthened so to affect the best neighbor path option. To use this command, one match clause
should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set as-path prepend 200 100.100
1.2.3.15 set atomic-aggregate
Command: set atomic-aggregate
no set atomic-aggregate
Function: Configure the atomic aggregate attributes. The “no set atomic-aggregate” command
deletes this configuration.
Parameter: None
Command Mode: route-map mode
Usage Guide: The BGP informs other BGP speaker by the atomic aggregate attributes. Local
system selects a sub-specified route other than the more specified routes included in it. To use
this command, one match clause should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set atomic-aggregate
1.2.3.16 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: Configure to delete the community attributes from the inbound or outbound routing
messages. The “no set comm-list <community-list-name | community-list-num > delete”
command deletes the configuration.
Parameter: <community-list-name > is the name of community list, <community-list-num >
is the sequence number of communitylist, ranging between 1～99（standard community list）or
100～199（extended community list）.
Command Mode: route-map mode

20
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set comm-list 100 delete
1.2.3.17 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: Configure the community attributes of the BGP routing message. The “no set
community [AA:NN] [internet] [local-AS] [no-advertise] [no-export] [none] [additive]”
command deletes this configuration.
Parameter: [AA:NN]is the communityattribute value, [internet] is the internet scope, [local-AS]
means this route do not announce outside the local AS (but can announce among the sub AS
within the confederation), [no-advertise] means this route do not send to any neighbor,
[no-export] means this route do not send to EBGP neighbors, [none] means delete the
community attributes from the prefix of this route, [additive] means add following existing
community attributes.
Command Mode: route-map mode
Usage Guide: To use this command, one match clause should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set community local-as additive
1.2.3.18 set extcommunity
Command: set extcommunity <rt | soo> <AA:NN>
no set extcommunity <rt | soo> [<AA:NN>]
Function: Configure the extended community attributes of the BGP routing message. The “no
set extcommunity <rt | soo> [<AA:NN>]” command deletes this configuration.
Parameter: <rt>is the route target, <soo> is the site of origin, <AA:NN>is the value of
community attributes, amongst AA is AS number, ranging from 1 to 4294967295, it can be shown
in decimal notation (such as 6553700) or delimiter method (such as 100.100), NN is a random
two byte number.
Command Mode: route-map mode
Usage Guide: To use this command, one match clause should at first be defined.
Example: Set rt as 100:10.