1. Home
    2. /
  2. Manuals
    3. /
  3. D-Link
    4. /
  4. DGS-3612
    5. /
  5. 70
Page 346 / 757 Scroll up to view Page 341 - 345
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
342
DGS-3627:admin# delete ip standard access_list list_name List1
Command: delete ip standard access_list list_name List1
Success.
DGS-3627:admin#
show ip standard access_list
Purpose
This command is used to show the information of access list.
Syntax
show ip standard access_list {<list_name 16>}
Description
This command is used to show the information of an access list.
Parameters
<list_name>
- The name of the access list.
Restrictions
None.
Example usage:
Show the information of an access list named “List1”:
DGS-3627:admin# config ip standard access_list List1 add 10.10.10.0/24 permit
Command:4# config ip standard access_list List1 add 10.10.10.0/24 permit
Success.
DGS-3627:admin# show ip standard access_list List1
Command:4# show ip standard access_list List1
IP standard Access_list:
List1
Total entries number
:
1
filter : permit 10.10.10.0/24
Total Access_list number :
1
DGS-3627:admin#
clear ip prefix_list counter
Purpose
To clear prefix list hit counters.
Syntax
clear ip prefix_list counter [list_name <list_name 16> {<network_address>} | all]
Description
This command is used to clear prefix list hit counters. The hit count is a value indicating the
number of matches to a specific prefix list entry.
Parameters
<list_name 16>
- Name of the prefix list from which the hit count is to be cleared.
<network_address>
- Specifies that IPv4 network which the hit count is to be cleared.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To clear prefix list counters for the prefix list named “first_list” that matches the 192.168.10.0/24 prefix:
Page 347 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
343
DGS-3627:admin# clear ip prefix_list counter first_list 192.168.10.0/24
Command: clear ip prefix_list counter first_list 192.168.10.0/24
Success.
DGS-3627:admin#
create route_map
Purpose
This command is used to create a route map or add and delete sequences to a route map.
Syntax
create route_map <map_name 16>
Description
A route map can have multiple rule entries, each with a different sequence number.
When creating a route map, a sequence ID of 10 will be added to the route map
If the sequence number is not specified, it will be automatically given.
The automatically given sequence number will be a multiple of 10.
Parameters
<map_name 16>
- The route map name.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To create a route map named “map1” and add one sequence ID of 20 to the route map:
DGS-3627:admin# create
route_map map1
Command:4# create
route_map map1
Success.
DGS-3627:admin# config route_map map1 add sequence 20
Command:4# config route_map map1 add sequence 20
Success.
DGS-3627:admin#
delete route_map
Purpose
This command is used to delete a route map configuration.
Syntax
delete route_map [map_name <map_name 16>{all_sequence} | all]
Description
This command is used to delete a route map configuration.
Parameters
<map_name 16>
- The route map name.
all_sequence
- Remove all sequence entries from the route map. The route map is not
deleted.
all
- Use to delete all route_maps.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To delete the route map named “map1”:
Page 348 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
344
DGS-3627:admin# delete route_map map_name map1
Command: delete route_map map_name map1
Success.
DGS-3627:admin#
show route_map
Purpose
This command is used o show a route map configuration.
Syntax
show route_map {<map_name 16>}
Description
This command is used to show a route map configuration.
Parameters
<map_name 16>
- Route map name.
Restrictions
None.
Example usage:
To show the route map named “map1”:
DGS-3627:admin# show route_map map1
Command:4# show route_map map1
route_map :
map1
--------------------------
sequence : 10
(Permit)
Match clauses:
Set clauses:
-----------------
sequence : 20
(Permit)
Match clauses:
Set clauses:
DGS-3627:admin#
config route_map
Purpose
Used to configure the route map or add/delete sequences to the route map.
Syntax
config route_map <map_name 16> [add | delete] sequence <value 1-65535 > {[deny |
permit]}
Description
A route map can have multiple rule entries, each with a different sequence number.
When creating a route map, a sequence ID of 10 will be added to the route map.
If the sequence number is not specified, it will be automatically given.
The automatically given sequence number will be a multiple of 10.
If permit/deny is not specified, permit is implied.
Parameters
<map_name 16>
- The route map name.
<value 1-65535>
- The sequence number for the route map rule.
permit
- Specifies to permit the route if the rule is matched
deny
- Specifies to deny the route if the rule is matched.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
Page 349 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
345
To configure a route map named “map1” and add one sequence ID of 20 to the route map:
DGS-3627:admin# config route_map map1 add sequence 20
Command:4# config route_map map1 add sequence 20
Success.
DGS-3627:admin#
config route_map sequence
Purpose
To define the conditions for redistributing routes from one routing protocol into another, or to
enable policy routing, use the route map command in global configuration mode and the
match and set command in route map configuration modes.
Syntax
config route_map <map_name 16> sequence <value 1-65535> match [add | delete]
[as_path <list_name 16 > | community_list <list_name 16> {exact} | ip address
<list_name 16> | ip address prefix_list <list_name 16> | ip next_hop <list_name 16> | ip
next_hop prefix_list <list_name 16> | metric <value 0-4294967294>] [<portlist> | all]
max_entry [<value 1-n> | no_limit]
Description
Route map can be used for redistribution or used as an inbound or outbound BGP session
filter.
A route map can have multiple rules; each rule is associated with a sequence number.
If one sequence entry is matched, then the following entries will not be checked.
A rule is formed by two parts, the match part and the set part. The match part defines the
match condition for the rule, and the set part defines the action that will be taken if the rule is
matched.
If a rule only has the set part defined but has no match part, then the rule will permit all, and
set part will take effect.
If a rule only has the match part defined but has no set part, and then if the rule is matched,
no action will be taken. If a rule has multiple match statements, then all the statements must
be matched in order for the rule to be matched.
If a rule has multiple set statements, then all the set will be applied if the rule is matched.
If the sequence number is not specified for the defined rule entry, the sequence number will
be automatically given. The automatically given sequence number will be a multiple of 10.
Therefore, if the defined rule is the first rule in the route map, the automatically given
sequence number will be 10. If the defined rule is not the first rule in the route map, the
sequence number will be the number that is a multiple of 10 and larger than the largest
sequence number of existing rules in the route map.
Parameters
<map_name 16>
- The route map name.
<value 1-65535>
- Specifies the sequence number for the rule. This is the number that
indicates the position a new route map will have in the list of route maps already configured
with the same name. Default: 10.
match deny
- Specifies to deny the route if the rule is matched.
match permit
- Specifies to permit the route if the rule is matched.
match as_path
- Specifies to match the AS path of the route against the AS path list.
The AS path list specified here needs to be a sub-list of the AS path list associated with the
route.
match community_list
- Specify to match the community of the route against the community
string.
exact
- All of the communities and only those communities specified must be present.
match ip address
- Specify to match the route according to the access list.
match ip address prefix_list
- Specify to match the route according to the prefix list.
Page 350 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
346
config route_map sequence
match ip next_hop
- Specify to match the next hop of the route according to the access list.
match ip next_hop prefix_list
- Specify to match the next hop of the route according to the
prefix list.
match metric
- Specify to match the metric of the route.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the route map match access list “ac_list1” and set the metric to 50:
DGS-3627:admin# config route_map map1 sequence 10 match add ip address ac_list1
Command:4# config route_map map1 sequence 10 match add ip address ac_list1
DGS-3627:admin# config route_map map1 sequence 10 set add metric 50
Command:4# config route_map map1 sequence 10 set add metric 50
Success.
DGS-3627:admin#
config route_map sequence set
Purpose
To define the conditions for redistributing routes from one routing protocol into another, or to
enable policy routing, use the route_map command in global configuration mode and the
match and set commands in route map configuration modes.
Syntax
config route_map <map_name 16> sequence <value 1-65535> set [add | delete]
[next_hop [<ipaddr> | peer_address ] | metric < uint 0-4294967294> | local_preference <
uint 0-4294967295> | weight <value 0-65535> | as_path <aspath_list> | community {<
communit_set 80 > | internet | no_export | no_advertise | local_as} {additive} |
origin[egp | igp | incomplete] | dampening <min 1-45> <value 1-20000> <value 1-
20000><min 1-255> <min 1-45>]
Description
Route map can be used for redistribution or used as an inbound or outbound BGP session
filter.
A route map can have multiple rules; each rule is associated with a sequence number.
If one sequence entry is matched, then the following entries will not be checked.
A rule is formed by two parts, the match part and the set part. The match part defines the
match condition for the rule, and the set part defines the action that will be taken if the rule is
matched.
If a rule only has the set part defined but has no match part, then the rule will permit all, and
set part will take effect.
If a rule only has the match part defined but has no set part, and then if the rule is matched,
no action will be taken. If a rule has multiple match statements, then all the statements must
be matched in order for the rule to be matched.
If a rule has multiple set statements, then all the set will be applied if the rule is matched.
If the sequence number is not specified for the defined rule entry, the sequence number will
be automatically given. The automatically given sequence number will be a multiple of 10.
Therefore, if the defined rule is the first rule in the route map, the automatically given
sequence number will be 10. If the defined rule is not the first rule in the route map, the
sequence number will be the number that is a multiple of 10 and larger than the largest
sequence number of the existing rule in the route map.

Rate

4.5 / 5 based on 2 votes.

Popular D-Link Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top