Vdsl2 Dslam Vx Md3024 User Manual
Vdsl2 Dslam Vx Md3024 User Manual
This guide provides helpful information and instruction on how to configure VX-MD3024 system. All users should
carefully read this guide before handling this product and follow all instructions. For reader comprehension, this manual
contains detailed descriptions and practical examples of product configuration. This guide also provides the
information you need to configure Layer 2, Layer 3 features and VDSL features on your system. The system
administrator should be familiar with the concepts and terminology of Ethernet and Local Area Network (LAN) and
should have technical networking experience and professional knowledge about network equipment.
For detailed information about the VX-MD3024, contact the customer center at the www.versatek.com home page.
You can obtain the document about the VX-MD3024 and various information with questions.
Organization
This guide is organized into these chapters:
Chapter 1, “Overview,” lists the software features of the release and provides examples of how the
Chapter 2, “Using the Command Line Interface” describes how to access the command modes, use the
command line interface (CLI), and describes CLI messages that you might receive. It also describes how
to get help, abbreviate commands, use no and default forms of commands, use command history and
how to search and filter the output of show and more commands.
Chapter 3, “Connecting to System and Assigning IP Address,” describes how to connect system and
Chapter 4, “Configuring System Environment,” explains how to configure system environment, manage
configurations and check the system. It also describes how to restart your system and make a
Chapter 5, “Configuring VDSL Feature,” describes how to configure the vdsl feature of each line. It also
explains how to upgrade modem image by using automatic and manual methods.
Chapter 6, “Configuring Switch Port Characteristics,” defines the type of Layer 2 and Layer 3 interfaces
on the system. It describes the interface command and provides procedures for configuring physical
interfaces.
Chapter 7, “Configuring VLAN,” describes how to create and maintain VLANs. It includes information
about the VLAN database, VLAN configuration modes. And it describes also how to add interfaces to a
Chapter 8, “Configuring STP,” describes how to configure the Spanning Tree Protocol (STP) on your
system.
Chapter 9, “Configuring DHCP,” describes how to configure the Dynamic Host Configuration Protocol
(DHCP) server and relay agent. It describes also how to configure DHCP snooping features those are
Chapter 10, “Configuring Layer 2 Multicasting,” describes how to configure Internet Group Management
Chapter 11, “Configuring IP Multicast Routing,” describes how to configure IP multicast routing. It
describes how to use and configure the Internet Group Management Protocol (IGMP) and IGMP Proxy.
Chapter 12, “Configuring filter with ACL,” describes how to configure filters on your system by creating IP
Chapter 13, “Configuring QoS,” describes how to configure standard quality of service (QoS) on your
system. With this feature, you can preferential treatment to certain types traffic.
Chapter 14, “Configuring SNMP,” describes how to configure the Simple Network Management Protocol
(SNMP). It describes how to configure community strings, enable trap managers and traps.
Chapter 15, “Configuring System Message Logging,” describes how to configure system message
logging. It describes how to change the message display destination device, limit the type of messages
sent.
Conventions
This publication uses the following conventions to convey instructions and information. Please be aware
Notation Description
{} Braces ({ }) group required choices, and vertical bar ( | ) separate the alternative elements.
Braces and vertical bars within square brackets ([ { | } ]) mean a required choice within an
[{ | }]
optional element.
boldface screen
screen
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained
in this manual.
Caution Means reader be careful. In this situation, you might do something that could result equipment
damage or loss of data.
This chapter describes the feature of VX-MD3024 system. It contains the following sections.
Features
1.1 Features
This section describes the features supported in the VX-MD3024.
Performance
9 Auto-sensing of port speed and auto-negotiation of duplex mode on all switch ports for optimizing
bandwidth
9 Per-Port storm control for preventing broadcast, multicast, and unicast storms
Manageability
9 DHCP (Dynamic Host Configuration Protocol), which automatically assigns IP address to clients,
accessed to network. You can effectively utilize limited IP source and lower cost to manage
network because DHCP server manages all IP addresses from center.
9 DHCP relay agent information (option 82) for subscriber identification and IP address
management
9 Support FTP and TFTP for administering software upgrades and configuration information
management.
9 Network Time Protocol (NTP) for providing a consistent timestamp to all systems from an external
source
9 In-band management access through up to five simultaneous Telnet connections for multiple
command-line interface (CLI)-based sessions over the network.
9 In-band management access for up to five simultaneous, encrypted Secure Shell (SSH)
connections for multiple CLI-based sessions over the network.
9 In-band management access through Simple Network Management Protocol (SNMP) version 1
and 2c get and set requests.
9 Out-of-band management access through system console port to a directly attached terminal or to
a Console Server port which connected with the neighbor system.
9 Port entry guarantees for every subscribers connected with EX-5124B to get the same IP address
always. This feature makes you manage your subscribers more efficiently.
Redundancy
9 IEEE 802.1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free
network. STP has these features:
− UplinkFast for fast convergence after a spanning-tree topology change and for achieving load
balancing between redundant uplinks.
9 Support for VLAN Ids in the full 1 to 4094 range allowed by the IEEE 802.1Q standard
Security
9 Access host feature provides limited access from only allowed hosts those are configured with IP
address for Telnet, SNMP and SSH.
9 Bridge Protocol Data Unit (BPDU) guard for shutting down a Port Fast-configured port when an
invalid configuration occurs.
9 DHCP snooping for limiting and identifying MAC addresses and IP addresses of the stations
allowed to access the port.
9 ARP snooping protection for filtering invalid ARP packets those are sent from station which does
not have a valid IP address from the DHCP server with valid method.
9 Classification
9 Policing
− Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow
− Egress Policing and Scheduling of Egress Queues. Four egress queues on all switch ports.
These queues can either be configured with the Weighted Round Robin (WRR) scheduling
algorithm or configured with one queue as strict priority queue and the other three queues for
WRR. The strict priority queue must be empty before the other three queues are serviced.
You can use the strict priority queue for mission-critical and time-sensitive traffic
Layer 3 Support
9 IP routing between VLANs (inter-VLAN routing) for full Layer 3 routing between two or more
VLANs, allowing each VLAN to maintain its own autonomous data-link domain
9 Fallback bridging for forwarding non-IP traffic between two or more VLANs
9 Static IP routing for manually building a routing table of network path information
9 Protocol-Independent Multicast sparse mode (PIM-SM) for multicast routing within the network.
Monitoring
9 Syslog facility for logging system messages about authentication or authorization errors, resource
issues, and time-out events
9 Traffic counters those monitor the ingress or egress packet counters about various packet types.
9 VDSL event reporter and error counters those monitor the status of the line between CO and
CPEs and link status
The following picture is an example of network construction using VX-MD3024. It is able to provide data
[ Example Configuration]
This chapter describes CLI (Command Line Interface) that you can use to configure your systems. It
Command Modes
Getting Help
Abbreviating Commands
you depend on which mode you are currently in. Enter a question mark (?) at the system prompt to
When you login successfully, you begin in user mode, often called user EXEC mode. Only a limited
To have access to all commands, you must enter Enable mode, often called privileged EXEC mode.
Normally, you must enter a password to enter Enable mode. From this mode, you can enter any
You can configure system functions for general system management and SNMP before configuring
specific protocol or specific function. From global configuration mode, you can enter interface
Using the configuration modes (global, interface, and line), you can make changes to the running
configuration. If you save the configuration, these commands are stored and used when the system
reboots.
The following table describes the main command modes, how to access each one, and the prompt
you see in that mode.The examples in the table use the host name VX-MD3024.
each command mode. You can also obtain a list of associated keywords and arguments for any
command.
VX-MD3024# ?
Exec commands:
clear Reset functions
configure Enter configuration mode
console-server execute console server
copy Copy
debug Debugging functions (see also 'undebug')
disable Turn off privileged mode command
enable Turn on privileged mode command
exit End current mode and down to previous mode
help Description of the interactive help system
kill Kill(or terminate) Telnet or SSH Session
logout Exit from the EXEC
no Negate a command or set its defaults
ping Send echo messages
quit Exit current mode and down to previous mode
reload Halt and perform a cold restart
remove Remove file
restart Restart routing protocol
show Show running system information
start-shell Start shell
telnet Open a telnet connection
()
Note Question mark (?) will not be seen in the screen and you do not need to press Enter key to display
You can find out commands starting with specific character string. Input the specific string and
question mark without space. The following is an example of finding out commands starting with co in
DUT-1# co?
configure Enter configuration mode
console-server execute console server
copy Copy
Also, it is possible to view variables you should input following after commands. After inputting the
command you need, make one space and input question mark. The following is an example of viewing
variables after the command copy. Please note that you must make one space after inputting.
DUT-1# copy ?
config Configuration file
cpe-os-image CPE's OS Image
os-image OS Image
example shows how to enter the show running-config command in Enable mode.
DUT-1# sh run
command history, you use up and down arrow key ( or ). When you press the up arrow key ( ),
the latest command you used will be seen one by one.
The following is an example of calling command history after using several commands. After using
these commands in order: show clock Æ configure terminal Æ interface fe1.1 Æ exit, press the up
arrow key ( ) and then you will see the commands from lastest one: exit Æ interface fe1.1 Æ
configure terminal Æ show clock.
To use this functionality, enter a show or more command followed by the pipe character (|), one of the
keywords, begin, include, or exclude, and an expression that you want to search for or filter out:
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain
output are not displayed, but the lines that contain Output are displayed.
This example shows how to include in the output display only lines where the expression state
appears:
Feature Setting
Data 8 bit
System Login
the ensure
username:
“ ”
“ ”
username: root
password: <1234>
DUT-1>
Changing Password
Command Description
Step 3 Enter the password Enter the current password and new password to
change.
Step 5 write memory (Optional) Save your entries in the configuration file.
Note You can make password from at least 1 characters up to 31 characters. Please avoid similar one
withlogin ID.
Note The password you enter will not be seen in the terminal, so please be careful. You need to enter the
password twice not to make mistake.
Command Description
Step 2 enable password Define a new password or change an existing password for
access to Enable mode.
Step 3 Enter the enable mode password Enter new password and confirm it.
Step 5 write memory (Optional) Save your entries in the configuration file.
“ ”
Password Encryption
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
Command Description
Step 2 line console line-num Enter the console-line configuration mode. You must set
or line-num to 0, because the system supports only one
Console session.
line vty line-num
Enter the VTY-line configuration mode. Select line-num to
configure telnet session.
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1(config-line)#exec-timeout 20 0
DUT-1(config-line)#end
DUT-1#write memory
[OK]
DUT-1#
Note You can access system through up to 3 telnet sessions simultaneously by default. You can change
the maximum number of allowed telnet sessions up to 5.
User Management
ing
and
Command Description
Step 3 Enter Password Specify the password for the user and confirm
Step 6 write memory (Optional) Save your entries in the configuration file.
‘ ’ ‘ ’
Note The password you enter will not be seen in the screen, so please be careful not to make mistake.
‘ ’
Telnet Access
Command Description
Command Description
a location
Command Description
“ ”
Command Description
Note You can show the login history only, when you configure the logging process to store the information
first.
Command Descriptioin
Step 2 line vty start-line end-line Enter the VTY-line configuration mode. Specify the range of
or line number with start-line and end-line
line ssh start-line end-line Enter the SSH-line configuration mode. Specify the range of
line number with start-line and end-line
Step 4 write memory (Optional) Save your entries in the configuration file.
[OK]
DUT-1#
Note By default, VX-MD3024 system is configured to Layer 2 mode and all of physical ports included in
VLAN1.1 interface.
“ ”
Command Description
Step 2 interface if-name Enter interface configuration mode. Specify the layer 3
interface to assign IP address.
Step 3 ip address ip-address/subnet-mask Assign IP address and subnet mask to the layer 3
interface.
Step 6 write memory (Optional) Save your entries in the configuration file.
DHCP Client
Command Description
Step 2 interface interface-id Enter interface configuration mode, and enter the Layer
3 interface to configure. The interface must be a Layer 3
interface.
Step 5 write memory (Optional) Save your entries in the configuration file.
Command Description
Step 2 ip route ip-address/subnet-mask {ip-address Establish static route. Specify IP address range of the
| interface-name} remote network and the interface or IP address of the
next-hop router.
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip route 100.1.1.0/24 192.168.40.254
DUT-1(config)#ip route 100.2.2.0/24 192.168.40.254
DUT-1(config)#end
DUT-1#show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip route 0.0.0.0/0 192.168.40.254
DUT-1(config)#end
DUT-1#write
[OK]
DUT-1#
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no ip route 100.1.1.0/24 192.168.40.254
DUT-1(config)#no ip route 100.2.2.0/24
DUT-1(config)#end
DUT-1#write
[OK]
DUT-1#
This chapter describes how to configure system environment such as configuring host name and
setting date and time and so on. This chapter contains following sections
Beginning in Enable mode, follow these steps to configure date and time on your system.
Command Descriptioin
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to set the system clock to 1:41 p.m. on November 24, 2005:
To display the time and date configuration, use the show clock command in Enable mode. This
example shows how to display the system clock.
NTP (Network Time Protocol) can be used to configure your systems to 1/1000 second to guarantee
the exact time on networks. The System and NTP server constantly transmit the message each other
to converge the correct time. It is very important to configure exact time to the system so that the
system operates properly. The details about NTP will be given at STD and RFC 1119.
Beginning in Enable mode, follow these steps to configure NTP on your system.
Command Description
Step 2 ntp server ip-address Specify NTP server’s IP address. You can configure
several NTP server by repeating this command.
Step 3 ntp query-interval <1-43200> Configure the period try to send NTP packet to the NTP
server. The range is 1 to 43200, and the unit is minutes.
Step 6 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the system to synchronize its system clock with the clock of the
NTP server at IP address 203.255.112.96 and configure the period to synchronize to 10 minutes. And
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ntp server 203.255.112.96
DUT-1(config)#ntp query-interval 10
DUT-1(config)#service ntp
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
To display the NTP configuration on your system, use the show ntp command in Enable mode. This
example shows how to display NTP server configuration.
DUT-1#show ntp
+ NTP Service : Enabled
+ NTP Query Interval : 10 minutes
+ NTP Server List :
203.255.112.96
DUT-1#
Configuring Time-Zone
You can configure Time-zone to your system. You must check Time-zone that you can configure..
The following table shows the kinds of Time-zone, which can configure to the system and a main
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure time zone as Seoul and displaying the system clock.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#clock time-zone gmt-plus 9
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#show clock
2005-11-24 14:37:21 GMT+0900
DUT-1#
Host name displayed on prompt is necessary to distinguish each device connected to network. In
order to configure or change host name of switch, use the hostname command in global configuration
mode.
Beginning in Enable mode, follow these steps to set the hostname of your system.
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
When you set the system name, it is also used as the system prompt. To return to the default
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#hostname DSLAM
DSLAM(config)#exit
DSLAM#write memory
[OK]
DSLAM#
The default TTL value of the system is 64 generally. Thus the TTL value of the IP packets sent from
your system is 64 when you use ping or telnet on your system. But sometimes you should set the
After you set the default TTL value to 128, the TTL of all packets sent from your system is set to 128.
Beginning in privileged EXEC mode, follow these steps to configure the default TTL value of your
system.
Command Description
Step 2 ip ttl ttl-value Specify the TTL value to configure. The default value is 64
and the range is 1 to 255.
Step 5 write memory (Optional) Save your entries in the configuration file.
You can use the show ip ttl command in Privileged EXEC mode to display the TTL value configured in
your system.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip ttl 128
DUT-1(config)#end
DUT-1#show running-config
(output truncated)
clock time-zone gmt-plus 9
!
ip ttl 128
!
(output truncated)
DUT-1#write memory
[OK]
DUT-1#
You can use the redirection keyword to store the output to the specified file when you enter a
command. You can display the output files generated by using redirection function and remove the
files. And you can transfer the redirection files to the FTP or TFTP server using the copy command.
Use the following Privileged EXEC commands to display, remove and copy the output file generated
by using redirection.
Command Description
show redirect-output Display the redirection file lists stored in your system.
show redirect-output file-name Display the contents of the specified redirection file.
copy redirect-output src-file-name tftp ip- Transfer the specified redirection file to the TFTP
address dest-file-name server.
copy redirect-output src-file-name tftp ip- Transfer the specified redirection file to the FTP
address user-id passwd dest-path server.
You can check the configuration settings you entered or changes you made by entering Enable mode.
DUT-1#show running-config
!
service password-encryption
!
hostname DUT-1
!
username root password 8 4D1rxNdkiu1Eg
(output truncated)
line console 0
exec-timeout 0 0
line vty 0 2
exec-timeout 0 0
line ssh 0 1
!
end
After you change system configuration, you must store it to the startup configuration in Flash memory.
If you do not store the changed configuration, the changed configuration will be lost when you restart
your system.
To store the configuration or changes you have made to your startup configuration in Flash memory,
Command Description
copy config running-config startup- Save your entries in the configuration file.
config
Two commands described the above table do the same function. This example shows how to save the
TELLION#write memory
[OK]
TELLION#
You can remove the configuration changes one by one. Occasionally, you want to clear all of the
configuration you have changed. To clear the configuration file of your system, use the following
Command Description
copy config factory-default-config clear the configuration file and make new
startup-config configuration file with the factory default mode.
OK..
startup-config would be applied AFTER system reboot.
DUT-1 #
may
To clear the configuration except IP address, VLAN, and routing information, use the following
Command Description
copy config default-config startup-config Clear the configuration except the IP addresses,
VLAN and static routing information.
This example shows how to clear the configuration except IP address assigned to the interfaces,
VLAN, and routing information on the system.
You can save the running configuration to the backup configuration file. You can also use the backup
configuration file to recover system, when the configuration of your system is corrupted. Also you can
To save the running configuration to the backup configuration file, use the following command in
Enable mode.
Command Description
This example shows how to save your configuration to the backup configuration file.
You can recover the configuration by using the backup configuration file that was saved already. To
recover the configuration file with the backup configuration, use the following command in Enable
mode.
Command Description
copy config backup-config name startup- Restore the configuration with the backup
config configuration file whose file name is name.
This example shows how to store the configuration to the backup configuration file named tellion.conf.
You can copy, erase and display the stored backup configuration files.
To copy the backup configuration file to another backup file, use the following command in Enable
mode.
Command Description
copy config backup-config name1 Copy the backup configuration file name1 to name
backup-config name2 2.
To delete the backup configuration file, use the following command in Enable mode.
Command Description
remove backup-config name Erase the backup configuration file named name.
To display the backup configuration files, use the following command in Enable mode.
Command Description
This example shows how to copy, delete and display the backup configuration file. The first statement
copy the backup configuration file named tellion.conf to the other backup configuration file named
test.conf. The second statement displays the backup configuration file lists and the third statement
You can configure the system by using configuration files you create or download from a TFTP or a
FTP server. You can upload the backup configuration files to a TFTP server or a FTP server for
storage.
To download or upload a configuration file by using TFTP, use the following command in Enable mode.
Command Description
copy config backup-config name1 ftp ip- Uploads the backup configuration file to a FTP
address user-id passwd name2 server.
copy config backup-config name1 tftp ip- Uploads the backup configuration file to a TFTP
address name2 server.
copy config ftp ip-address user-id passwd Downloads a configuration file from a FTP server.
name1 backup-config name2
copy config tftp ip-address name1 backup- Downloads a configuration file from a TFTP server.
config name2
Before you begin to download or upload the backup configuration file using FTP or TFTP, you must
check the FTP server or TFTP server is properly configured. You must check the system has a
This example shows how to upload the backup configuration file named tellion.conf to the TFTP server
whose IP address is 192.168.100.51 and download the backup configuration file named test.conf from
Always check the system to prevent issues from occuring. Administrators should not only be aware of
the system status but should also check if configurations are correctly changed. This section includes the
following functions with command.
You can use the ping command in Enable mode to check if your system is correctly connected to
the network.
In order to do ping test for checking network connection to the peer system, use the following
Command Description
The following is an example of a ping test to check the network connection with 192.168.10.2.
DUT-1#ping 192.168.10.2
PING 192.168.10.2 (192.168.10.2) from 192.168.40.201 : 56(84) bytes of data.
64 bytes from 192.168.10.2: icmp_seq=1 ttl=254 time=0.902 ms
64 bytes from 192.168.10.2: icmp_seq=2 ttl=254 time=0.770 ms
64 bytes from 192.168.10.2: icmp_seq=3 ttl=254 time=0.777 ms
64 bytes from 192.168.10.2: icmp_seq=4 ttl=254 time=0.786 ms
Extended Ping
When you enter the ping command, your system tries to send the ICMP Echo messages continuously
until you enter the Ctrl + C Key in the previous TOS version. You should not use the ping
command in the input file to be used to execute automatic CLI from this weak point.
When you enter the ping command in TOS 2.0.8, your system tries to send ICMP Echo messages just
4 times and finishes the command basically. You can configure also the count to try to send ICMP
Echo messages and configure the size of the ICMP Echo messages to be sent.
When you use the ping command to confirm the connection status between your system and the
other system, use the following command options in Privileged EXEC mode.
Command Description
ping ip-address Try to send ICMP Echo messages 4 times to the specified
IP address.
ping ip-address count count Try to send ICMP Echo messages the number of specified
times.
For count, specify the number of times to try to send.
ping ip-address size size Try to send ICMP messages of which length is specified 4
times.
For size, specify the length of the ICMP Echo message to
be sent. If you do not specify the size, the length of the
ICMP Echo message would be 56 by default. The range is
0 to 65507.
ping ip-address count count size size Specify the number of times to try to send and the size of
the ICMP Echo messages
For count, specify the number of times to try to send.
For size, specify the length of the ICMP Echo message to
be sent. If you do not specify the size, the length of the
ICMP Echo message would be 56 by default. The range is
0 to 65507.
You can discover the routes that packets will actually take when traveling to their destinations. To do
this, the traceroute command sends probe packets and displays the round-trip time for each node. If
the timer goes off before a response comes in, an asterisk (*) is printed on the screen.
Command Description
DUT-1#traceroute 192.168.10.2
traceroute to 192.168.10.2 (192.168.10.2), 30 hops max, 40 byte packets
1 192.168.40.254 (192.168.40.254) 1.019 ms 1.788 ms 0.964 ms
2 192.168.10.2 (192.168.10.2) 1.34 ms * 1.128 ms
DUT-1#
Dump Packet
You can dump the header of packets sent from your system and received on your system using the
dump-packet command in Privileged EXEC mode. Use the following Privileged EXEC commands to
Command Description
dump-packet {interface-name | any} Dump the packets received on the specified interface or sent
to the interface.
For interface-name, specify the interface dumping packets.
You can specify Layer 2 interface or Layer 3 interface. If you
use any keyword instead of interface name, you can dump all
packets on every interfaces.
dump-packet {interface-name | any} ethernet Dump the packets of which the source MAC address is same
{mac-address | any } with specified MAC address on the specified interface.
If you set any keyword instead of a specific MAC address, it
means the MAC address field is don’t care.
dump-packet {interface-name | any} ethernet Dump the packets of which the source MAC address is same
{src-mac-address | any } {dest-mac-address | with src-mac-address and the destination MAC address is
any } same with dest-mac-address also on the specified interface.
If you set any keyword instead of a specific MAC address, it
means the MAC address field is don’t care.
dump-packet {interface-name | any} {arp | Dump the ARP, DHCP, ICMP, IGMP or IP packets of which the
dhcp | icmp | igmp | ip | multicast} {src-ip- source IP address is same with src-ip-address on the specified
address | any } If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.interface.
dump-packet {interface-name | any} {arp | Dump the ARP, DHCP, ICMP, IGMP or IP packets of which the
dhcp | icmp | igmp | ip | multicast} {src-ip- source IP address is same with src-ip-address and the
address | any } {dest-ip-address | any } destination IP address is same with dest-ip-address on the
specified interface.
If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.
dump-packet {interface-name | any} {tcp | Dump the TCP or UDP packets of which the source IP address
udp} ip { src-ip-address | any } is same with src-ip-address on specified interface.
If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.
dump-packet {interface-name | any} {tcp | Dump the TCP or UDP packets of which the source IP address
udp} ip { src-ip-address | any } { dest-ip- is same with src-ip-address and the destination IP address is
address | any } same with dest-ip-address on specified interface.
If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.
dump-packet {interface-name | any} {tcp | Dump the TCP or UDP packets of which the source IP address
udp} ip { src-ip-address | any } { dest-ip- and the destination IP address is same with specified IP
address | any } portnum {port-number | any } addresses and the source port number is same with specified
one.
If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.
dump-packet {interface-name | any} {tcp | Dump the TCP or UDP packets of which the source IP address
udp} ip { src-ip-address | any } { dest-ip- and the destination IP address is same with specified IP
address | any } portnum {port-number | any } addresses and the source port number and the destination
{port-number | any } number are same with specified numbers.
If you set any keyword instead of a specific IP address, it
means the IP address field is don’t care.
dump-packet {interface-name | any} {tcp | Dump the UDP or TCP packets of which the source port
udp} portnum {port-number | any } number is same with the specified one.
dump-packet {interface-name | any} {tcp | Dump the UDP or TCP packets of which the source port
udp} portnum {port-number | any } {port- number and the destination number port are same with the
number | any } specified ports.
Before you use the dump-packet command to dump the packets matched in the condition you specified,
you can configure that the Ethernet header of the packets to dump could be displayed. Beginning in
Privileged EXEC mode, follow these steps to display the Ethernet header of the dumping packets also
Command Description
Step 5 write memory (Optional) Save your entries in the configuration file.
You can dump the packets with the raw packet data. Beginning the Privileged EXEC mode, follow
these steps to configure whether the raw data will be displayed or not
Command Description
Step 2 dump-packet raw-data display-length Configure the option of the dump-packet command to
display raw data of the dumping packets.
For display-length, specify the length of raw data to
display.
Step 5 write memory (Optional) Save your entries in the configuration file.
If you don’t want to show the raw data of the packets to be dumped, use the no dump-packet raw-
When you run the dump-packet command, the system dumps the number of packets configured and
it would print out a prompt and return to waiting status to process the next command.
Beginning in Privileged EXEC mode, follow these steps to configure the number of packets to dump
Command Description
Step 2 dump-packet count number Configure the number of packets to dump when you run the
dump-packet command.
For number, specify the number of packets to dump. The
default value is 1024 and the range is 1 to 8192.
Step 5 write memory (Optional) Save your entries in the configuration file.
You can display the MAC table information to find a system that has a specific MAC address is
To display the MAC address table, use the following command in Enable mode.
Command Description
DUT-1#show bridge
bridge VLAN port MAC Discard Type
1 10 ge1 0000.f076.ccc0 N Dynamic
1 10 ge1 0001.0257.2a49 N Dynamic
1 10 ge1 0001.028c.5ee9 N Dynamic
1 10 ge1 0001.0297.6915 N Dynamic
1 10 ge1 0002.4427.1af9 N Dynamic
(output truncated)
DUT-1#
MAC addresses are recorded in MAC table can be divided to kinds of type. One type is dynamic MAC
address which is recorded in MAC address automatically by using source MAC address passing the
port. And the other is static MAC address that is recorded in MAC table manually. A static MAC
address is not deleted until you delete the MAC address manually. The static MAC address remains in
Beginning in Enable mode, follow these steps to add a static MAC address on your system.
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to add a static MAC address, and display MAC table.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 1 address 000e.dc31.0011 forward fe1.1
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#show bridge
bridge VLAN port MAC Discard Type
1 1 fe1.1 000e.dc31.0011 N Static
1 10 ge1 0000.f076.ccc0 N Dynamic
1 10 ge1 0001.0257.2a49 N Dynamic
(output truncated!)
DUT-1#
To remove a MAC address in the MAC table, use the following command in Enable mode.
Command Description
clear mac address-table {dynamic | static} Delete all dynamic or static MAC addresses in a
bridge bridge-id specified bridge-id.
clear mac address-table {dynamic | static} Delete all dynamic or static MAC addresses in a
interface interface-id bridge bridge-id specified interface.
clear mac address-table {dynamic | static} Delete all dynamic or static MAC addresses in a
vlan vlan-id bridge bridge-id specified VLAN.
The system records MAC table to prevent broadcast packets from transmitting. And unnecessary MAC
address that does not response during specified time is deleted from the MAC table automatically. The
Command Description
Step 2 bridge 1 ageing-time seconds Specify the aging time. The default value is 300
seconds. The range is 10 to 1000000.
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the ageing time to 800 seconds.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
You can add ARP entries to the ARP table, and remove a entry from the ARP table on your system.
Beginning in Enable mode, follow these steps to add an ARP entry (IP address and MAC address) to
ARP table.
Command Description
Step 2 arp ip-address mac-address Add an ARP entry which is composed of a IP Address
and a MAC address manually.
For ip-address, specify IP address.
For mac-address, specify MAC address.
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to add an ARP entry whose IP address is 192.168.40.101 and MAC address
is 00:0E:DC:31:00:AA.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#arp 192.168.40.101 00:0e:dc:31:00:aa
DUT-1(config)#exit
DUT-1#write memory
DUT-1#
Beginning in Enable mode, follow these steps to delete an ARP entry from the ARP table.
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to delete an ARP entry whose IP Address is 192.168.40.101.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no arp 192.168.40.101
DUT-1(config)#exit
DUT-1#write memory
DUT-1#
To display ARP entries in the ARP table, use the following command in Enable mode.
Command Description
DUT-1#show arp
---------------------------------------------------------------------------
Address HWtype HWaddress Flags Mask Iface
---------------------------------------------------------------------------
192.168.40.101 ether 00:0E:DC:31:00:12 CM vlan1.10
192.168.40.254 ether 00:01:02:57:2A:49 C vlan1.10
---------------------------------------------------------------------------
* Flags: C=complete, P=published, M=manual
---------------------------------------------------------------------------
You can show the time how long your system has been running after booting.
To display running time of your system, use the following command in Enable mode.
Command Description
DUT-1#show uptime
8 Hour(s) 5 Minute(s) 48 Second(s) Elapsed
DUT-1#
You can show the average CPU utilization of your system. To display CPU utilization, use the following
Command Description
DUT-1#show cpu-load
MeasureTime CPU-Load
-------------------------------------------------------------------------
5 Sec 1.60 %
1 Min 1.06 %
10 Min 0.89 %
DUT-1#
You can show the memory utilization of your system. To display memory utilization, use the following
Command Description
DUT-1#show memory
Total : 246730752 bytes
Used : 181493760 bytes(73.56 %)
Free : 65236992 bytes
---------------------------------------------------------------------------
DUT-1#
You can show the system image version, the time creating system image, and size of the system
Image running in your system. To display the information of the system image, use the following
Command Description
DUT-1#show version
TOS version : 2.1.7
You can store two OS image on your system, and you can select a booting OS image. Before you
To display the information of each OS image in the flash memory, use the following command in
Enable mode.
Command Description
show os-image flash flash-id Display the information of OS images in the flash
memory.
For flash-id, specify the flash memory area number.
The range is 1 to 2.
The following is an example displaying the information of the OS image in the flash memory area 1.
You can show the internal temperature of the system and the status of the FAN. To display the system
Command Description
The following is an example displaying the FAN status, internal temperature, and the external FAN and
DUT-1#
It is possible that a system tries to send ping packets continuously increase too much the utilization of
CPU. Therefore you can set the interval between ping packets to reduce the CPU utilization.
Beginning in Enable mode, follow these steps to set the interval between ping packets.
Command Description
Step 2 gateway-ping-check interval interval Set the interval between ping tests
For interval, specify the ping test interval. The range is
10 to 86400. The default interval is 30 seconds.
Step 4 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#gateway-ping-check interval 60
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
Beginning in Enable mode, follow these steps to set the ping fail threshold count.
Command Description
Step 2 gateway-ping-check check-count count Configure the ping fail threshold count to restart system.
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the ping fail threshold count to 3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#gateway-ping-check check-count 3
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
Beginning in Enable mode, follow these steps to configure the lockout period.
Command Description
Step 2 gateway-ping-check period period Configure the lockout period for locking out the ping
monitoring function.
The default lockout period is 86400 seconds. The range
is 100 to 259200.
Step 4 write memory (Optional) Save your entries in the configuration file.
The system manages the rebooting history information during lockout period you have configured. The
This example shows how to set the lockout period to 7200 seconds.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#gateway-ping-check period 7200
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
You can configure also the maximum reset count to lockout. The system counts the reset count by
ping fail to lockout ping monitoring function. If the reset count of the system is over the allowed
maximum reset count, the system locks out the ping monitoring function.
Beginning in Enable mode, follow these steps to configure the maximum reset count.
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
This example shows how to set the maximum reset count during lockout period to 3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#gateway-ping-check max-reset 3
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
The default the ping monitoring status is disabled. You can enable the ping monitoring function.
Beginning in Enable mode, follow these steps to enable the ping monitoring function.
Command Description
Step 4 write memory (Optional) Save your entries in the configuration file.
To disable the ping monitoring function, use the no service gateway-ping-check command in global
configuration mode. This example shows how to enable the ping monitoring function.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#service gateway-ping-check
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#
After being locked out the ping monitoring function, you should enable the ping monitoring function
again manually by using CLI command to make the ping monitoring function enable.
You can show the ping monitoring status of your system. To display the ping monitoring status, use the
Command Description
The following shows the example displaying the ping monitoring status.
DUT-1#show gateway-ping-check
+ Gateway ping check : ENABLED
- Ping Interval(*) : 100 seconds
- Checking count(*) : 3
- Maximum Reset Count(*) : 3
- Checking Period(*) : 7200 seconds
c.f.) (*) means non-default values
+ Gateway information
- Default gateway #1 IP : 192.168.40.254
-> the last pinging is success
+ System reset by gateway ping check information
- System reset is unlocked
system reset due to gateway ping fail(2005/10/27 11:12:09)
DUT-1#
Rebooting System
Command Description
“ ”
“ ”
DUT-1#reload
configuration is changed..
save configuration? (y/N): y
[OK]
reboot system? (y/n): n
DUT-1#
To display which OS image is current booting OS image and which OS image will be used at next
Command Description
DUT-1#show os-image
Current Booted OS Image : FLASH Bank 1
Next-time-Boot OS Image : FLASH Bank 1
DUT-1#
You can find the current using OS image is stored in Flash Bank 1 and it will be used for next time also.
You can change the next time booting OS image. Before you select the next time booting OS image,
you should check the information of OS images stored in each flash bank. You can select the next time
booting OS image with flash bank number or the name of the OS image.
To select the next time booting OS image, use the following command in global configuration mode.
Command Description
boot-os-image flash flash-id Select the next time booting OS image with flash
bank number.
For flash-id, specify the flash bank number. The
range is 1 to 2.
boot-os-image image-name image-name Select the next time booting OS image with the
name of the OS image.
For image-name, specify the name of the OS
image
This example shows how to select the next time boot OS image to the flash bank 2.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#boot-os-image flash 2
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#show os-image
*******************************************************************
OS Image Information
*******************************************************************
Current Booted OS Image : FLASH Bank 1
Next-time-Boot OS Image : FLASH Bank 2
-------------------------------------------------------------------
DUT-1#
This example shows how to select the next time boot OS image with the name of the OS image.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#boot-os-image image-name PPC405EP-EX2124P v06.06.08-2251
DUT-1(config)#exit
DUT-1#write memory
[OK]
DUT-1#show os-image
Current Booted OS Image : FLASH Bank 1
Next-time-Boot OS Image : FLASH Bank 1
DUT-1#
You can schedule a rebooting system to occur on the system at a later time (for example, late at night
or during the weekend when the system is used less), or you can synchronize a reboot network-wide
To configure you system to reboot at a later time, use one of the following commands in Enable mode.
Command Description
reload at year month day hour minute Schedule a rebooting system to take affect at the
specified time.
DUT-1#reload in 2 30
DUT-1#
DUT-1#reload at 2006 11 25 3 30
DUT-1#
You can cancel the scheduled rebooting. To cancel the rebooting schedule, use the following
Commands Description
You can show the scheduled rebooting information. To display the scheduled rebooting information,
Command Description
This example shows how to display the scheduled rebooting information and cancel a scheduled
reboot.
DUT-1#show reload
+ System is reloaded at 2006-11-30 11:20:00(YYYY-MM-DD HH:MM)
+ executed after 98 days 21 hours 11 minutes 57 seconds
DUT-1#no reload at
DUT-1#
CLI execution function to run a sequence of commands periodically or at the specified time every day.
To configure the automatic CLI execution function, supports the following functions.
You must write an input file in which a series of commands to execute are written, to configure the
automatic CLI execution function. And you should download the input file to your system using FTP or
TFTP protocol from the server. Use the following Privileged EXEC commands to download the input
Command Description
copy autocmd-input tftp ip-address src-file- Download the input file from a TFTP server.
name dest-file-name For ip-address, specify the IP address of a TFTP
server.
For src-file-name, specify the input file name in the
TFTP server.
For dest-file-name, specify the destination file name
will be stored in the system.
copy autocmd-input ftp ip-address user-id Download the input file from a FTP server.
password src-file-name dest-file-name For ip-address, specify the IP address of a FTP
server.
For user-id, specify an user-id that will be used for
downloading from the FTP server.
For password, specify the password of the user on
the FTP server.
For src-file-name, specify the input file name in the
FTP server.
For dest-file-name, specify the destination file name
stored in your system.
You need the result file that includes the results created by execution the commands specified in the
input file to monitor your system status or the results of executed commands. Thus you can configure
your system to upload the result file to the FTP or TFTP server. Use the following Privileged EXEC
commands to configure your system to upload the result file after executing the commands specified in
input file.
Command Description
copy autocmd-output src-file-name tftp ip- Uploads the result file to a TFTP server.
address dest-file-name For ip-address, specify the IP address of a TFTP
server.
For src-file-name, specify the output file name to
upload to the TFTP server.
For dest -path, specify the destination directory
name to store it on the TFTP server.
copy autocmd-output src-file-name ftp ip- Uploads the result file to a FTP server.
address user-id password dest-path For ip-address, specify the IP address of a FTP
server.
For user-id, specify an user-id that will be used for
uploading to the FTP server.
For password, specify the password of the user on
the FTP server.
For src-file-name, specify the output file name to
upload to the FTP server.
For dest-path, specify the destination directory
name to store it on the FTP server.
After downloading the input file to your system, you can configure the commands specified in the input
file to be executed once a day at the specified time or once at the specified time. And you can
schedule that the commands are executed every specific interval and execute the commands directly.
To configure the commands specified in the input file to be executed once a day at the specified time,
Command Description
autocmd input-file every hour minute [output- Configure the commands in the specified input file
file| no-output] [tftp ip-address] to be executed once a day at every specific time
and upload the result file to the TFTP server.
For input-file, specify the file name of the input file
including commands list to execute at every
specified time.
For hour, specify the hour to execute the
commands listed in the input-file. The range is 0 to
23.
For minute, specify the minute to execute the
commands. The range is 0 to 59.
For output-file, specify the output file name
including the results displayed by the executed
commands. If the output-file is not specified, the
system automatically generate an output-file of
which the name is IP address + input file name +
the execution time. The IP address of the
automatically generated output file name is the IP
address of the vlan of which vlan ID is lowest on
the system.
You can send the output file to the specified TFTP
server after finishing the execution of the command
list in the input file automatically. The output file will
be removed automatically after sending it
successfully. If you don’t specify the tftp server, the
output file would not be uploaded to the server and
the output file will be stored in your system. You
can upload the output file the other time when you
want to send it to a server. And the output file will
be kept until your system is reloaded.
For no-output, specify this keyword instead of the
output file name to make no output file.
For ip-address, specify the IP address of a TFTP
server.
autocmd input-file every hour minute [output- Configure the commands specified in the input file
file| no-output] [ftp ip-address user-id to be executed once a day at every specific time
password path] and upload the result file to the FTP server.
For input-file, specify the file name of the input file
including command list to execute at the specified
time every day.
For hour and minute, specify the time to execute
the command listed in the input-file.
For output-file, specify the output file name
including the results displayed by executed
command. If the output-file is not specified, the
system automatically generate an output-file of
which the name is IP address + input file name +
the execution time. The IP address of the
generated output file name is the IP address of the
vlan of which vlan ID is lowest on the system.
You can send the output file to the specified FTP
server after finishing the execution of the command
list in the input file automatically.
For no-output, specify this keyword instead of the
output file name to make no output file.
For ip-address, specify the IP address of a FTP
server.
For user-id, specify an user-id that will be used for
downloading in the FTP server.
For password, specify the password of the user in
the FTP server.
For path, specify the directory name in which the
output file is stored.
To configure the commands specified in the input file to be executed once at the specified time, use
Command Description
autocmd input-file at year month day hour Configure the commands specified in the input file
minute [output-file| no-output] [tftp ip-address] to be executed once at the specific time and upload
the result file to the TFTP server.
For input-file, specify the file name of the input file
including commands list to execute at the specified
time.
For year, specify the year to execute the
commands listed in the input file. The range is 2000
to 2035.
For month, specify the month to execute the
commands. The range is 1 to 12.
For day, specify the day to execute the commands.
The range is 1 to 31.
For hour, specify the hour to execute the
commands. The range is 0 to 23.
For minute, specify the minute to execute the
commands. The range is 0 to 59.
For output-file, specify the output file name
including the results displayed by executed
commands. If the output-file is not specified, the
system automatically generate an output-file of
which the name is IP address + input file name +
the execution time. The IP address of the
generated output file name is the IP address of the
vlan of which vlan ID is lowest on the system.
You can send the output file to the specified TFTP
server after finishing the execution of the command
list in the input file automatically. The output file will
be removed automatically after sending it
successfully. If you don’t specify the tftp server, the
output file would not be uploaded to the server and
the output file will be stored in your system. You
can upload the output file the other time when you
want to send it to a server. And the output file will
be kept until your system is reloaded.
For no-output, specify this keyword instead of the
output file name to make no output file.
For ip-address, specify the IP address of a TFTP
server.
autocmd input-file file at year month day hour Configure the commands specified in the input file
minute [output-file| no-output] [ftp ip-address to be executed once at the specific time and upload
user-id password path] the result file to the FTP server. If you don’t specify
the FTP server, the result file would not transfer to
the FTP server.
To configure the commands specified in the input file to be executed every interval periodically, use the
Command Description
autocmd input-file interval hour minute Configure the commands specified in the input file
[output-file| no-output] [tftp ip-address] to be executed every interval periodically and
upload the result file to the TFTP server after
execution. If you don’t specify the TFTP server, the
result file would not transfer to the TFTP server.
For input-file, specify the file name of the input file
including commands list to execute every interval
time.
For hour, specify the hour of the interval to execute
the commands. The range is 0 to 23.
For minute, specify the minute of the interval to
execute the commands. The range is 0 to 59.
For output-file, specify the output file name
including the results displayed by executed
commands. If the output-file is not specified, the
system automatically generate an output-file of
which the name is IP address + input file name +
the execution time. The IP address of the
generated output file name is the IP address of the
vlan of which vlan ID is lowest on the system.
You can send the output file to the specified TFTP
server after finishing the execution of the command
list in the input file automatically. The output file will
be removed automatically after sending it
successfully. If you don’t specify the tftp server, the
output file would not be uploaded to the server and
the output file will be stored in your system. You
can upload the output file the other time when you
want to send it to a server. And the output file will
be kept until your system is reloaded.
For no-output, specify this keyword instead of the
output file name to make no output file.
For ip-address, specify the IP address of a TFTP
server.
autocmd input-file interval hour minute Configure the commands specified in the input file
[output-file| no-output] [ftp ip-address user-id to be executed every interval periodically and
password path] upload the result file to the FTP server after
execution. If you don’t specify the FTP server, the
You can also configure the commands specified in the input file to be executed directly. To configure
the commands specified in the input file to be executed immediately, use the following Privileged
EXEC commands.
Command Description
autocmd input-file [output-file | terminal | no- Execute the commands specified in the input file
output] immediately.
For input-file, specify the file name of the input file
including commands list to execute.
When you make the input file with the commands to execute automatically, sometimes you need the
special method make a command that use each other file name with a same string. For example,
when you write the input file to upload the configuration file of your system to a FTP server to backup
the configuration file periodically, you might want to store the configuration file of each system to each
This special string can be used only in the input file to execute automatic CLI. If you use the special
You can use the following string to replace the special string to the IP address of your system.
These examples show how to replace the special string to the file names applying replacement rule in
the system which the IP address of VLAN1.1 is 192.168.0.100 and the IP address of VLAN1.10 is
192.168.10.11 in.
Config_$ipaddr$_Test Config_192.168.0.100_Test
Config_$ipaddr:vlan1.10$_Test Config_192.168.10.11_Test
If the specified VLAN is not assigned IP address, the command including a special string would be
failed automatically.
Special Commands
Sometimes when you make your input file to be used to execute automatic CLI, you need a special
command to wait for the duration without any action before executes the next command. You can use
the following Privileged EXEC command to specify the delay time in the input file.
Command Description
sleep delay Wait for the specified duration without any action.
For delay, specify the time delay to wait to execute
the next command. The unit of the delay is
seconds. And the range is 0 to 86400.
This command can be used on all command
modes.
When you make the input file including the command to reload your system, you should not use the
reload command. Thus you need the other reload command to use that command in the input file. The
following is the new command to reload your system without your confirmation and this command can
Command Description
You can display the information related with the automatic CLI execution to manage the automatic CLI.
And you can show the information of downloaded input files to be used for automatic CLI execution
To display the scheduled automatic CLI execution, use the following Privileged EXEC command.
Command Description
This example shows how to display the information of automatic CLI. You can find the input file name,
the scheduling type, scheduled execution time and the output file name. The scheduling type
describes whether the automatic CLI executes once a day at every specified time or once. And you
can see whether the output file is already sent to the FTP or TFTP server.
DUT-1#show autocmd
Input filename Type Execution time Output filename
---------------------------------------------------------------------------
autoIn Intervally ----/--/-- 00:10:00 test_out(*)
This example shows how to display the detailed information of automatic CLI scheduled. You can
show the information of a FTP or TFTP server in which the result file would be stored.
c.f.> (*) means the output file would be removed after transferring
DUT-1#
To display the downloaded input files and the result files, use the following Privileged EXEC
commands.
Command Description
show autocmd input-file file-name Display the contents of the specified input file that is
downloaded to execute automatic CLI.
show autocmd output-file Display the result files those are generated by
executing the automatic CLI.
show autocmd output-file file-name Display the contents of the specified result file that is
generated by executing automatic CLI.
You can configure your system chooses to totally ignore all ICMP Echo requests. If you configure the
ICMP Echo reply function to deny, you and others will be unable to ping your system.
Beginning in Privileged EXEC mode, follow these steps to configure your system to deny all ICMP
Echo request.
Command Description
Step 2 ip icmp echo all [deny|allow] Configure whether your system reply to the all received
ICMP Echo requests or not. By default, your system will
send the ICMP Echo reply messages, if you don’t configure
anything.
If you configure this function to deny mode, your system will
not reply to the ICMP Echo requests.
Step 5 write memory (Optional) Save your entries in the configuration file.
This configuration works precisely the same as ignoring ICMP Echo requests except that it will only
ignore those ICMP messages sent to broadcast or multicast addresses. It should be quite obvious why
this is good, it would among other things stop this specific host from being part of smurf attacks and
likely problems. Broadcast pings are generally bad unless you are using this to find out how many
hosts on your network(s) are up or not. This function is default turn off.
Beginning in Privileged EXEC mode, follow these steps to enable this function.
Command Description
Step 2 ip icmp echo broadcast Configure your system to ignore those ICMP messages sent
[deny|allow] to broadcast or multicast addresses.
By default, this function turns off.
Step 5 write memory (Optional) Save your entries in the configuration file.
The ICMP rate limit is the maximum rate at which your system generates ICMP messages of the types
specified by the ip icmp ratelimit field global configuration command. The configured value is the
interval that your system has to wait between sending two such messages. Therefore zero means no
limit. And The unit of this value is ms (millisecond) and if you set the ICMP rate limit to 1000ms, it
Beginning in Privileged EXEC mode, follow these steps to configure the ICMP rate limit.
Command Description
Step 2 ip icmp ratelimit interval interval Configure the interval that your system has to wait between
sending two ICMP messages.
The default value is 1000ms and the range is 1 to
2147483647.
Step 5 write memory (Optional) Save your entries in the configuration file.
You can configure the ICMP types should be rate limited with the value that is configured by the ip
icmp ratelimit interval global configuration command. For all ICMP types you selected the rate limit is
applied. Thus the other ICMP packets which is not selected by you are allowed though the sending
rate is exceed. You can select one or more ICMP types to apply the sending rate limit.
An attacker could cause a correctly operating host or router to flood a victim with ICMP replies by
sending it packets that generate replies back to the source address of the victim. It is important in
some cases to send such replies, but hardly ever important to generate them at a very high rate.
Beginning in Privileged EXEC mode, follow these steps to configure the ICMP types to apply the ICMP
rate limit.
Command Description
Step 2 ip icmp ratelimit field {add-mask- Configure the ICMP types to apply the ICMP rate limit.
req | add-mask-resp | dest-unreach
| echo-req | echo-resp | info-req |
info-resp | param-problem | redirect
| source-quench | time-exceed |
timestamp-req|timestamp-resp}
Step 5 write memory (Optional) Save your entries in the configuration file.
You can configure the destination unreachable ICMP filtering function of each Layer 3 interface. When
you disable sending function of the destination unreachable ICMP packets, the system can not send
the destination unreachable ICMP packets through the Layer 3 interface. And when you disable
receiving function of the destination unreachable ICMP packets, those packets received from the
specified Layer 3 interface are automatically discarded. The default configuration is enable sending
and receiving the destination unreachable ICMP packets of all Layer 3 interfaces.
Beginning in Privileged EXEC mode, follow these steps to configure whether you allow a Layer 3
Command Description
Step 3 ip icmp dest-unreachable {rx | tx} Configure sending or receiving function of the destination
{deny | allow} unreachable ICMP packets
For {tx|rx}, select the direction to apply filtering function.
For deny, specify to discard the destination unreachable
ICMP packets.
For allow, specify to allow the destination unreachable
ICMP packets.
Step 6 write memory (Optional) Save your entries in the configuration file
You can configure whether you accept the redirect ICMP packets from a Layer 3 interface or not. And
also you can configure whether the system sends the redirect ICMP packets to a Layer 3 interface or
not. The default configuration is enable sending and receiving the redirect ICMP packets of all Layer 3
interfaces.
Beginning in Privileged EXEC mode, follow these steps to configure whether you allow a Layer 3
Command Description
Step 2 interface interface-name Enter interface configuration mode and specify the Layer 3
interface name.
Step 3 ip icmp redirect {rx | tx} {deny | Configure sending or receiving function of the redirect ICMP
allow} packets.
For {tx|rx}, select the direction to apply filtering function.
For deny, specify to discard the redirect ICMP packets.
For allow, specify to allow the redirect ICMP packets.
Step 6 write memory (Optional) Save your entries in the configuration file
You can display the ICMP control status configured on your system. Use the following command to
Command Description
DUT-1#show ip icmp
+ Ignore ICMP Echo All : Disabled
+ Ignore ICMP Echo Broadcast : Enabled
param-problem
addr-mask-req
The TCP (Transmission Control Protocol) Header includes URG, ACK, PSH, RST, SYN, and FIN flags.
You can control RST and SYN Flag of TCP packets for system security.
The RST flag informs the peer systems those try to connect with your system about the fact the
requested port is not open. But hackers use the function to search the IP address of operating system
in the network. You can configure the function sending RST flag packets to prevent your system from
sending reply packets set RST flags to the hacker system. By default, your system allows sending
Beginning in Privileged EXEC mode, follow these steps to configure the RST Flag sending function.
Command Description
Step 2 ip tcp rst tx {permit | discard} Configure whether you allow sending RST packets.
Step 5 write memory (Optional) Save your entries in the configuration file
The TCP protocol use reliable connection unlike UDP. Thus the TCP protocol needs “3 Way
Host A Host B
SYN (1000)
ACK (4001)
[3 Way Handshaking]
A client sends SYN packet requesting connection to the server. The server received SYN packet
sends SYN packet and ACK packet to allow the connection request. After the client receive those
packets, it send ACK packet to the server and the connection is established finally. After the
connection is established with 3 Way Handshaking procedures, the data can be exchanged.
The above procedure is basic flow of TCP connection. But A hacker (Host A) sends SYN packet and
receives response (SYN + ACK) from the server (Host B), it does not send the ACK packet. Then the
server sent SYN and ACK packets waits the response from the client (Host A) and keeps the
connection with “Half Open“ Status. The server initialize the connection in a period (75 seconds). But
the connection is kept in the Incomplete Connection Queue during the period.
Generally, a Hacker sends SYN packet with randomly selected source IP address continuously and
the server received these packets add a connection created by the SYN packet to the Incomplete
Connection Queue and sends the response packet. But the hacker does not send any reply packets.
The size of the server’s Incomplete Connection Queue increase continuously, finally the server cannot
support more TCP connection. The server cannot reply to the normal connection requests in this
EX-2108BD contains the mechanism to protect it from SYN flooding attack. The system sends SYN
and Cookies instead of a sequence number when the protection mechanism enables. Then it only
Beginning in Privileged EXEC mode, follow these steps to configure the SYN Cookies function.
Command Description
Step 2 ip tcp syncookie Enable SYN Cookies function. The default configuration is
disable.
Step 5 write memory (Optional) Save your entries in the configuration file
To disable the SYN Cookies function, use the no ip tcp syncookie command in global configuration
mode.
This chapter describes how to configure VDSL on your system and how to inquire to it’s configure and
status.
If you do not use VDSL Interface, configure administrative status of VDSL Interface to disable. If you set
the administrative state of a VDSL interface to disable, the VDSL interface does not try to make a
connection with a modem. If the link status of the interface is already connected, the link would be
To reuse the disabled VDSL Interface, you can change the administrative status of the interface to
enable status.
Beginning in Enable mode, follow these steps to configure the administrative status of a VDSL
interface.
Commands Descriptions
Step 2 vdsl interface ifname Identify a specific interface for configuration, and
enter interface configuration mode.
This example shows how to set the administrative status of the VDSL interface 1.1 to disable.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl interface 1.1
DUT-1(config-vdsl-if)#shutdown
DUT-1(config-vdsl-if)#end
DUT-1#show running-config vdsl interface 1.1
!
vdsl interface 1.1
service-conf-profile default
service-alarm-profile default
shutdown
!
DUT-1#write memory
On VDSL system, configure first the VDSL configuration profiles those have various configuration
values of each VDSL line parameter. And you can apply the pre-configured VDSL configuration profile
to each VDSL interface. The VDSL configuration profile has configuring information on the transmit rate
of upstream and downstream, target SNR margin, minimum SNR margin, and band-plan and so on. For
detailed description of configuring the VDSL configuration profile, refer to Chapter 5.3, “Configuring
When you apply a VDSL configuration profile to a VDSL Interface, the configuration parameters of the
VDSL interface depend on the value defined in the VDSL configuration profile. Namely, the VDSL
interface use the transmitting rate upstream and downstream, target SNR margin, and bandplan value
defined in the applied VDSL configuration profile to link with CPE. If you apply a new VDSL
configuration profile to the VDSL interface that is already linked on, it will restart link connection
procedure with the new configuration values those are defined in the newly assigned VDSL
configuration profile.
Beginning in Enable mode, follow these steps to apply VDSL configuration profile to a VDSL interface.
Commands Descriptions
Step 2 vdsl interface ifname Identify a specific interface for configuration, and
enter interface configuration mode.
This example shows how to set VDSL configuring Profile to VDSL Interface 1.1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl interface 1.1
DUT-1(config-vdsl-if)#service-conf-profile example
DUT-1(config-vdsl-if)#end
DUT-1#show running-config vdsl interface 1.1
!
vdsl interface 1.1
service-conf-profile example
service-alarm-profile default
!
DUT-1#write memory
On VDSL system, configure first the VDSL alarm profiles those have various parameters for alarm
threshold values. And you can apply the pre-configured VDSL alarm profile to each VDSL interface like
as the VDSL configuration profile. The VDSL alarm profile has configured threshold value of the Errored
Second (ES), Severely Errored Second (SES), and UnAvailable Second (UAS) count. For detailed
description of configuring the VDSL alarm profile, refer to Chapter 5.4, “Configuring VDSL alarm
profile.”
After you apply a specific VDSL alarm profile to a VDSL interface, when the alarm count is over the
Beginning in Enable mode, follow these steps to apply a VDSL alarm profile to a VDSL interface.
Commands Descriptions
Step 2 vdsl interface ifname Identify a specific interface for configuration, and
enter interface configuration mode.
Step 6 write memory (Optional) Save your entries in the configuration file.
This example shows how to set VDSL alarm profile to VDSL interface 1.1..
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl interface 1.1
DUT-1(config-vdsl-if)#service-alarm-profile example
DUT-1(config-vdsl-if)#end
DUT-1#
Applying VDSL configuring profile to VDSL Interface, the VDSL interface tries to link on according to the
specified configuration profile. You can initialize the link status to link on again with the specified
configuration profile when the link status is not stable or the SNR margin value of the interface is not
enough.
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl interface 1.1
DUT-1(config-vdsl-if)#init
DUT-1(config-vdsl-if)#end
DUT-1#show vdsl interface 1.1 brief
PORT PROTECTION ADMIN LINK DS PAYLOAD RATE US PAYLOAD RATE
1.1 - ENABLED TRAINING 0 kbps 0 kbps
In this example, the link status of the VDSL Interface 1.1 is training status as above. In a second the link
To display the VDSL line information, use the following commands in Enable mode.
Commands Descriptions
show vdsl interface [ifname] brief Display brief information of VDSL Interface
show vdsl interface [ifname] detail Display detailed information of VDSL Interface
show vdsl interface [ifname] phy Display physical layer information of VDSL
interface.
DUT-1#
DUT-1#
The following is an example displaying transmitting Bit-Loading information of VDSL interface 1.1.
Note The display command of Bit-Loading Information need a lot of data exchanges between devices,
which cause in time delay to get. Sometimes, it happens timeout if the time delay is over 30 seconds.
If you set the administrative status of unused VDSL interface to disable, you can get the Bit-Loading
information more fast.
To display the counter information of VDSL Interface, follow these commands in Enable mode.
Commans Description
show vdsl interface [ifname] counters Display the Ethernet counter information.
show vdsl interface [ifname] 15min-pm-log Display the 15 minutes PM log information.
show vdsl interface [ifname] 24hrs-pm-log Display the 1 day PM log information.
The following is an example displaying the Ethernet counter of VDSL interface 1.1.
To initialize the counter information of VDSL interface, use the following command in Enable mode.
Commands Descriptions
clear vdsl interface [ifname] counters Initialize the Ethernet counter of VDSL
Interface.
clear vdsl interface [ifname] pm-counters Initialize the PM counter of VDSL interface.
clear vdsl interface [ifname] 15min-pm-log Initialize the 15 minutes PM log of VDSL
interface.
clear vdsl interface [ifname] 24hrs-pm-log Initialize the 24 hours PM log of VDSL
interface.
This example shows how to initialize the Ethernet counter of VDSL Interface 1.1.
DUT-1#
This example shows how to initialize 15 minutes PM log of VDSL Interface 1.1.
This example shows how to initialize 24 hours PM log of VDSL Interface 1.1.
To display the modem information of VDSL interface, use the following command in Enable mode.
Commands Descriptions
show vdsl interface [ifname] Display the link status between modem and PC. The
modem-status information contains link status, duplex mode, pause
control status and the number of pause frame received
from PC.
show vdsl interface [ifname] Display the information for the modem image.
modem-image
The following is an example displaying the link status between modem and PC of VDSL interface 1.1.
The following is an example displaying the modem counters of the interface VDSL 1.1.
The modem is able to contain two modem firmware images. Sometimes, you would like to know the
information of modem firmware images stored in the mode. A modem image’s status is active means
The following is an example displaying the modem image information of the VDSL interface 1.1.
The following is an example displaying the modem upgrade status of the VDSL interface 1.1.
In the above example, the modem that is connected with VDSL Interface1.1 is on upgrading, and the
other modem that is connected with VDSL Interface1.2 is finished it. But the modem must be restarted
to use the upgraded modem image. The other modems have not been upgraded.
Note You must load the modem firmware image to the system buffer before you start upgrading modem
image. If it is not loaded, you can show the message that the modem image is not ready and the
modem image upgrade would be stopped.
Commans Descriptions
Step 2 vdsl interface [ifname] Identify a specific interface for configuration, and enter
interface configuration mode.
VDSL Modem can have two bank to store modem image. When you upgrade modem image, the
upgraded modem image is stored at the bank selected alternatively. And the new upgraded modem
image is activated automatically. Normally you don’t need specify which modem image is activate. But,
if you want to downgrade modem image, you can set the already stored modem image to be activate
manually.
Beginning in Enable mode, follow these steps to set the specified modem image to be activate.
Commands Descriptions
Step 2 vdsl interface ifname Identify a specific interface for configuration, and enter
interface configuration mode.
Step 3 activate modem-image later Change the activated modem image. Whenever you enter
or this command, the activated modem image would be
changed alternatively.
activate modem-image now
For later, means changing only activated image not
restarting modem.
For now, means changing activated image and restarting
modem.
Step 5 show vdsl interface [ifname] Verify modem image information of the specified VDSL
modem-image interface.
This example shows how to change the activating modem image of VDSL interface 1.1 and verify the
results.
1 R,A 1.0.4r9
2 1.0.4r12
You can find the activate modem image is changed after entering the activate modem-image
command in interface configuration mode.
Provisioning every parameters on every VDSL interface may become burdensome. Moreover most
lines are provisioned identically with the same set of parameters. To simplify the provisioning process,
VX-MD3024 system makes use of VDSL configuration profiles. A profile is a set of parameters that can
VDSL configuration profile consists of the transmit rate of upstream and downstream, target SNR
On VDSL System, one or more VDSL interfaces may be configured to share parameters of a single
profile by applying a VDSL configuration profile to VDSL interface. If you apply a VDSL configuration
profile to a VDSL interface, the interface refer to the parameters those are defined in VDSL
configuration profile when the interface try to link on. If you apply new VDSL configuration profile to the
interface of which link status is on, the interface retry to link on with new applied parameters.
Default Setting
Feature
Downstream Upstream
Beginning in Enable mode, follow these steps to create new VDSL configuration profile.
Commands Descriptions
Step 2 vdsl conf-profile profile-name Identify a specific configuration profile for configuration,
and enter VDSL configuration profile mode.
If the specified configuration profile is not exist in your
system, a new configuration profile would be created.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to create new VDSL configuration profile as “example”.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl conf-profile example
% vdsl conf-profile "example" is newly created
DUT-1(config-conf-profile)#end
DUT-1#show vdsl conf-profile-list
-------+------------------------------------------
INDEX | PROFILE NAME
-------+------------------------------------------
01 | default
02 | example
-------+------------------------------------------
DUT-1#write memory
[OK]
DUT-1#
Note When you enter VDSL configuration profile mode, you can show the message that inform you that a
new VDSL configuration profile is created. That means the specified configuration profile is not exist
on the system and a new configuration profile is created. No message shown means the specified
configuration profile is exist.
Beginning in Enable mode, follow these steps to delete VDSL configuration profile.
Commands Descriptions
Step 2 no vdsl conf-profile profile-name Delete the specified VDSL configuration profile
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no vdsl conf-profile example
DUT-1(config)#end
DUT-1#show vdsl conf-profile-list
-------+------------------------------------------
Beginning in Enable mode, follow these steps to configure VDSL configuration profile.
The following steps show the procedure to change every configuration items of VDSL configuration
profile, you can use selectively for only needed items during step 3 to step 12.
Commands Descriptions
Step 10 data-rate {downstream | upstream} Configure the maximum data rate and minimum data
{slow-channel | fast-channel} rate of the slow channel or fast channel.
max-data-rate min-data-rate For max-data-rate, specify the maximum data rate.
The range is 0 to 200000kbps.
For min-data-rate, specify the minimum data rate. The
range is 0 to 200000kbps
Step 11 snr-margin {downstream | upstream} Configure target SNR margin and minimum SNR
target-snr-margin min-snr-margin margin of each direction of the VDSL line.
For target-snr-margin, specify target SNR margin. The
range is 0 to 31.0 dB
For min-snr-margin, specify minimum SNR margin.
The range is 0 to 31.0 dB
Step 12 interleave-delay {downstream | upstream} Configure interleave delay of each direction of VDSL
delay interface.
For delay, specify the interleaving delay. The range is
0 to 50.0ms.
Step 15 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the VDSL configuration file. In this example, sets the maximum
data rate of downstream slow-channel to 50000 kbps, and the minimum data rate to 64 kbps. And
configures the target SNR margin to 5dB and the minimum SNR margin to 3dB.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl conf-profile example
DUT-1(config-conf-profile)#data-rate downstream slow-channel 50048 64
DUT-1(config-conf-profile)#data-rate upstream slow-channel 50048 64
DUT-1(config-conf-profile)#snr-margin downstream 5 3
DUT-1(config-conf-profile)#snr-margin upstream 5 3
DUT-1(config-conf-profile)#end
DUT-1#show vdsl conf-profile example
===========================================================
VDSL CONF PROFILE: [02] example
-----------------------------------------------------------
BAND PLAN : 998-640-30000 100/100
BAND CONFIG : ISDN Safe Mode
UPBO MODE : OFF
RATE ADAPTATION MODE : Startup
PSD MASK LEVEL : ANNEX-F
DSL Mode : Slow Only
xDSL Line Type : xDSL-AUTO-DETECT
DS / US Slow Max Data Rate : 50048 kbps / 50048 kbps
DS / US Slow Min Data Rate : 64 kbps / 64 kbps
DS / US Target Noise Margin : 5.0 dB / 5.0 dB
DS / US Min Noise Margin : 3.0 dB / 3.0 dB
DS / US Max Interleave Delay : 2.0 ms / 2.0 ms
DUT-1#write memory
[OK]
DUT-1#
To display the information of VDSL configuration profile, use the following commands in Enable mode.
Commands Descriptions
show vdsl conf-profile [profile-name] Display parameter values of the specified VDSL
configuration profile.
This example shows how to display the VDSL configuration profile list.
This example shows how to display parameter values of the VDSL configuration profile named as
“example”.
===========================================================
VDSL CONF PROFILE: [02] example
-----------------------------------------------------------
BAND PLAN : 998-640-30000 100/100
BAND CONFIG : ISDN Safe Mode
UPBO MODE : OFF
RATE ADAPTATION MODE : Startup
PSD MASK LEVEL : ANNEX-F
DSL Mode : Slow Only
xDSL Line Type : xDSL-AUTO-DETECT
DS / US Slow Max Data Rate : 50048 kbps / 50048 kbps
DS / US Slow Min Data Rate : 64 kbps / 64 kbps
DS / US Target Noise Margin : 5.0 dB / 5.0 dB
DS / US Min Noise Margin : 3.0 dB / 3.0 dB
DS / US Max Interleave Delay : 2.0 ms / 2.0 ms
DS / US Min Protection : 0.0 usec / 0.0 usec
RFI NOTCH : NONE
You can configure VDSL alarm profile and apply it to each VDSL interface as VDSL configuration profile.
Threshold values of the following PM monitoring counters are defined in VDSL alarm profile. The
system monitors each PM counters every seconds. When a PM counter exceeds the defined threshold
By default, there is one alarm profile named as “default” in the system. The following table shows the
default VDSL alarm profile configuration. The parameters of “default” alarm profile are set to the
following default values. If you create a new alarm profile, the parameter values of that alarm profile are
ES threshold 700
Beginning in Enable mode, follow these steps to create a VDSL alarm profile.
Comands Description
Step 2 vdsl alarm-profile profile-name Identify a specific alarm profile for configuration, and
enter VDSL alarm profile mode.
If the specified alarm profile is not exist in your system, a
new alarm profile would be created.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to create new VDSL alarm profile as “example”.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl alarm-profile example
% vdsl alarm-profile "example" is newly created
DUT-1(config-alarm-profile)#end
DUT-1#show vdsl alarm-profile
ALARM PROFILE NAME | LOFS LOSS LOLS LPRS ES SES UAS InitFailureNoti
default | 700 700 700 700 700 700 700 Disable
example | 700 700 700 700 700 700 700 Disable
DUT-1#write memory
[OK]
DUT-1#
Note If new alarm profile is created, a message of new profile created is shown. No message shown means
already the specified alarm profile is exist.
Commands Discriptions
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no vdsl alarm-profile example
DUT-1(config)#end
DUT-1#show vdsl alarm-profile
ALARM PROFILE NAME | LOFS LOSS LOLS LPRS ES SES UAS InitFailureNoti
default | 700 700 700 700 700 700 700 Disable
DUT-1#write memory
[OK]
DUT-1#
The following steps show the procedure to configure every PM counters of VDSL alarm profile. You can
use selectively for only needed PM counters during step 3 to step 10.
Commands Descriptions
Step 2 vdsl alarm-profile profile-name Identify a specific alarm profile for configuring, and
enter VDSL alarm profile mode.
If the specified alarm profile is not exist in your
system, a new alarm profile would be created.
Step 3 base profile-name Copy alarm profile from other alarm profile.
For profile-name, means the name of the source
alarm profile.
Step 12 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure threshold value of ES and SES to 50 for each.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl alarm-profile example
DUT-1(config-alarm-profile)#es-threshold 50
DUT-1(config-alarm-profile)#ses-threshold 50
DUT-1(config-alarm-profile)#end
DUT-1#write memory
[OK]
DUT-1#
To display the information of configured alarm profile, use the following command in Enable mode.
Commands Description
show vdsl alarm-profile [profile-name] Display the information of specified alarm profile.
There will be a demand of upgrading modem image depending on improvement of modem performance or
Two kind of modem upgrading methods are supported by VX-MD3024 system. The one is automatic
To upgrade vdsl modem image, first you should download modem image to system by using FTP or
TFTP from remote server that the modem image is located in.
After downloading the modem image, you must load the downloaded modem image to the vdsl buffer located
in the vdsl device driver. The modem upgrade process is able to use only the modem image stored in vdsl
buffer.
After loading the modem image, you can upgrade the modem image automatically or manually. When you
enable the automatic modem upgrade function, your system automatically starts to upgrade all of
modem sequentially. If you don’t enable automatic modem upgrade function, you should enter the
Note When the modem image upgrading procedure have finished, the new modem image is stored at one
of two banks in the modem. And the status of new modem image becomes activate status. The
activate modem image will be used at booting time of modem. If you want for the modem to be
operated with upgraded modem image, restart the modem.
After loading modem image to upgrade and enable automatic modem upgrade function, the system
starts automatic modem upgrade for modems those are connected with each VDSL line. The system
compares loaded modem image and the current modem image, upgrades the modem that has not
same modem image automatically. If a modem image is not loaded at vdsl buffer in device driver,
automatic modem upgrade function does not start although you enable automatic modem upgrade
Beginning in Enable mode, follow these steps to configure automatic modem upgrade function.
Commands Description
Step 1 copy cpe-os-image tftp server-ip Download modem image from remote FTP server.
src-filename dest-filename or
or Download modem image from remote TFTP server.
copy cpe-os-image ftp server-ip user-id
password src-filename dest-filename
This example shows how to prepare modem image and enable automatic modem upgrade function.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl prepare cpeImage
DUT-1(config)#vdsl auto-modem-upgrade
DUT-1(config)#end
DUT-1#show vdsl modem-upgrade detail
--------------------------------------------------------
AUTOMATIC MODEM UPGRADE : ENABLED
MODEM IMAGE VERSION : 1.0.4r9
--------------------------------------------------------
PORT STATUS DESCRIPTION
1.1 O upgrade done
1.2 X need upgrade
1.3 X need upgrade
1.4 X need upgrade
1.5 - link down
1.6 X need upgrade
(Output Truncated)
3.5 X need upgrade
3.6 X need upgrade
3.7 X need upgrade
3.8 O upgrade done
--------------------------------------------------------
DUT-1#
Beginning in Enable mode, follow these steps to start modem upgrade function manually.
Commands Descriptions
Step 1 copy cpe-os-image tftp server-ip Download modem image from remote FTP server.
src-filename dest-filename or
or Download modem image from remote TFTP server.
copy cpe-os-image ftp server-ip user-id
Step 3 vdsl prepare-modem-image filename Load modem image to vdsl buffer in device driver.
Step 4 vdsl interface ifname Identify a specific interface for configuration, and enter
interface configuration mode.
This example shows how to prepare modem image and start modem upgrade manually.
EWL means the distance calculated by using electrical characteristics between system and VDSL
modem. Thus this value can be differences from real distance depending on the electrical quality of
lines. You can show EWL information in output displayed by the show vdsl interface command in
Enable mode. You can configure the unit of EWL to meter or feet. By default, the default EWL unit is
meter.
Beginning in Enable mode, follow these steps to configure the unit of EWL.
Commands Descriptions
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Initializing BME
When a VDSL line card put into mal-functional error by software trouble, you can recover the VDSL line
Beginning in Enable mode, follow these steps to initialize VDSL line card.
Commands Descriptions
Step 3 show vdsl unit-status Display the status of BME in the specified VDSL line
card.
This example shows how to initialize VDSL line card whose number is 3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vdsl init-unit 3
Are you sure to initialize VLB #3? (y/n):y
% VLB #3 is being initialized.
DUT-1(config)#end
DUT-1#show vdsl unit-status
VLB NUMBER ADMIN STATUS ATTACH STATUS RUNNING STATUS
1 UP O RUN
2 UP X DOWN
3 UP O RUN
4 UP X DOWN
DUT-1#
Note It takes about 30 seconds to initialize BME. You can verify that the BME initializing procedure is
finished with the show vdsl bme-status command. When you show the status of BME is ‘running’,
the procedure is finished.
This chapter describes the type of switch port and how to configure basic function of auto-negotiation,
transmit speed, flow control etc., also how to configure maximum allowed MAC address limitation,
Name of Interface
System 1 on 1.
Gigabit ethernet port of VX-MD3204 system marked ge1 and ge2. The eight switch ports connected
with VDSL port are divided into two groups. Each group has four switch ports. Therefore switch ports
are marked as fe1.1, fe1.2, fe1.3, fe1.4, fe2.1, fe2.2, fe2.3 and fe2.4.
Speed Auto
To display the configuration of basic function of switch port, use the following command in Enable
mode.
Commands Descriptions
show interface config status [interface- Display the configuration of basic function of every
name] switch port
For interface-name, specify the switch port name to
display the configuration of switch port. If you don’t
specify interface-name, display the configuration of
every switch port.
Beginning in Enable mode, follow these steps to enable or disable a layer 2 interface.
Step 2 interface interface-name Enter interface configuration mode and the physical
interface identification.
Step 6 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#no shutdown
DUT-1(config-if)#end
DUT-1#show running-config interface fe1.1
interface fe1.1
switchport
bridge-group 1
switchport mode access
!
DUT-1#write memory
[OK]
DUT-1#
Only unidirectional communication is possible on half duplex mode and bi-directional communication is
possible on full duplex mode to transmit packet for two ways. By transmitting packet for two ways,
To configure duplex mode of Gigabit Ethernet port, use the following command in interface
configuration mode.
Commands Descriptions
duplex {auto | full | half} Enter the duplex parameter for the interface.
The default duplex mode is auto.
If you configure the duplex mode of a specific interface to auto mode, the auto-negotiation function
would be enabled and the duplex mode and speed of the interface is configured depend on the duplex
mode or speed of the peer interface. To disable the auto-negotiation function, configure the duplex
Note You can configure the duplex mode of only Gigabit Ethernet port on VX-MD3024 system. The other
interfaces (fe1.1 ~ fe2.4) are connected to VDSL interfaces directly. Those operate according to only
pre-configured mode even though you configure the duplex mode of those interfaces.
Beginning in Enable mode, follow these steps to configure duplex mode of Gigabit Ethernet ports.
Commands Descriptions
Step 2 interface interface-name Enter interface configuration mode and the physical
interface identification.
Step 3 duplex {auto | full | half} Enter the duplex parameter for the interface.
The default duplex mode is auto.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure duplex mode of ge1 port to full.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface ge1
DUT-1(config-if)#duplex full
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
Ethernet interfaces on the system operate in 10, 100, 1000 Mbps. You can configure interface speed
To configure port speed of Gigabit Ethernet interface, use the following command in interface
configuration mode.
Commands Description
bandwidth {10m |100m|1g} Enter the appropriate speed parameter for the
interface
The default bandwidth configuration is auto.
If you configure the speed of an interface to auto, the auto-negotiation function would be enabled and
the duplex mode and speed of the interface is configured depend on the duplex mode or speed of the
peer interface. To disable the auto-negotiation function, configure the speed to 10M, 100M or 1G.
Beginning in Enable mode, follow these steps to configure port speed of Gigabit Ethernet port.
Commands Description
Step 2 interface interface-name Enter interface configuration mode and the physical
interface identification.
Step 3 bandwidth {10M | 100M | 1G} Enter the appropriate speed parameter for the interface
The default bandwidth configuration is auto.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure port speed of ge1 port to 100 Mbps.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface ge1
DUT-1(config-if)#bandwidth 100m
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing
congested nodes to pause link operation at the other end. If one port experiences congestion and
cannot receive any more traffic, it notifies the other port to stop sending until the condition clears.
When the local device detects any congestion at its end, it can notify the link partner or the remote
device of the congestion by sending a pause frame. Upon receipt of a pause frame, the remote device
stops sending any data packets, that prevents any loss of data packets during the congestion period.
To configure flow control an interface, use the following command in interface configuration mode.
Commands Descriptions
flowcontrol {receive|send} {on | off}} Configure the flow control mode for the port.
receive on and send on: Flow control operates in
both directions; both the local and the remote devices
can send pause frames to show link congestion.
receive on and send off: The port can not send
pause frames but can operate with an attached
device that is required to or can send pause frames;
the port can receive pause frames.
receive off and send on: The port sends pause
frames if the remote device supports flow control but
cannot receive pause frames from the remote device.
receive off and send off: Flow control does not
Beginning in Enable mode, follow these steps to configure flow control on an interface:
Commands Descriptions
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 3 flowcontrol {receive | send} {on | off} Configure the flow control mode for the port.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to turn on all flow control on Gigabit Ethernet interface ge1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface ge1
DUT-1(config-if)#flow control receive on
DUT-1(config-if)#flow control send on
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
To display flow control status on a physical port, use the following command in Enable mode.
Commands Descriptions
show flowcontrol interface interface- Display configured flow control status on a specified
name physical port.
The following is an example displaying flow control status on the interface fe1.1.
This section describes how to configure to switch port and type of switch port.
9 Access Port
9 Hybrid Port
9 Trunk Port
Each physical port of VX-MD3024 can operate as Layer 2 interface and Layer 3. By default, all
Beginning in Enable mode, follow these steps to configure an interface to Layer 2 interface (switch
port).
Commands Descriptions
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the fe1.1 interface to switch port.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#switchport
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
You can configure an interface to Layer 3 interface (Routed port) by using the no switchport
command. All Layer 3 interfaces require an IP address to route traffic.
This example shows how to configure ge1 port to router port and IP address to 192.168.30.200.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface ge1
DUT-1(config-if)#no switchport
DUT-1(config-if)#ip address 192.168.30.200/24
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
VX-MD3024 system supports fallback bridging function. With fallback bridging, the system bridges
together two or more VLANs or routed ports, essentially connecting multiple VLANs within one bridge
domain. Fallback bridging forwards traffic that the system does not route and forwards traffic belonging
To assign a switch port to a bridge group, use the following command in interface configuration mode.
Commands Descriptions
A switch port should be assigned to only one bridge group to provide Layer 2 service. By default, all
Note To reduce complexity of system management, it is preferable to configure only one bridge group on
your system, if possible.
Access Port
An access port belongs to and carries the traffic of only one VLAN. Traffic is received and sent in
native formats with no VLAN tagging. Traffic arriving on an access port is assumed to belong to the
To configure a switch port to access port, use the following command in interface configuration mode.
Commands Descriptions
switchport mode access Configure the type of switch port to access port.
If the filtering function is enabled on an access port, it forwards only untagged frames and discards
Beginning in Enable mode, follow these steps to configure a switch port to access port, and configure
filtering function.
Commands Description
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 4 bridge-group bridge-id Assign the switch port to a specified bridge group.
Step 5 switchport mode access Configure the switch port mode to access port.
Step 6 switchport mode access ingress-filter Enable or disable ingress filtering function of the access
{enable | disable} port.
Step 9 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure fe1.1 interface to access port and enable ingress filtering
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode access
DUT-1(config-if)#switchport mode access ingress-filter enable
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#show running-config interface fe1.1
!
interface fe1.1
switchport
bridge-group 1
switchport mode access
switchport mode access ingress-filter enable
!
DUT-1#
Hybrid Port
A Hybrid port can treat both of tagged and untagged frames. A hybrid port carries the traffic of multiple
VLANs. Received frames in a hybrid port are classified based on the VLAN characteristics and then
To configure a switch port to hybrid port, use the following command in interface configuration mode.
Commands Description
switchport mode hybrid acceptable-frame- Set the switch port acceptable frame types.
type {all | vlan-tagged} all: Accept all frames received.
vlan-tagged: Accept only classified frames which belong to
the port's member set.
The default value is all.
switchport mode hybrid ingress-filter Set the ingress filtering for received frames. Received
[{enable | disable}] frames that cannot be classified in the previous step based
on the acceptable frame type parameter are discarded.
The default configuration of ingress-filter function is
disable.
no switchport hybrid Reset the mode of switch port to access that is default.
On the above commands, the default value of acceptable-frame-type is all and the default value of
ingress-filter is disable . Thus the result of using only the switchport mode hybrid command is that
the ingress filtering is off, and that all frame types are classified and accepted.
Beginning in Enable mode, follow these steps to configure a switch port to hybrid port, and enable
Commands Description
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 4 bridge-group bridge-id Assign the switch port to a specified bridge group.
Step 5 switchport mode hybrid Configure the switch port mode to hybrid port.
Step 6 switchport mode hybrid acceptable- Configure the allowed frame type.
frame-type {vlan-tagged | all} all: Accept all frames received.
vlan-tagged: Accept only classified frames which
belong to the port's member set.
The default value is all.
Step 7 switchport mode hybrid ingress-filter Set the ingress filtering for received frames. Received
{enable | disable} frames that cannot be classified in the previous step
based on the acceptable frame type parameter are
discarded.
The default configuration of ingress-filter function is
disable.
Step 10 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure fe1.4 port to hybrid port and enable ingress filtering function. On
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.4
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode hybrid
DUT-1(config-if)#switchport mode hybrid ingress-filter enable
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.4
!
interface fe2.4
switchport
bridge-group 1
switchport mode hybrid
switchport mode hybrid ingress-filter enable
switchport mode hybrid acceptable-frame-type all
!
DUT-1#write memory
[OK]
DUT-1#
Trunk Port
A trunk port carries the traffic of multiple VLANs and supports simultaneous tagged and untagged
traffic. A trunk port is assigned a default Port VLAN ID (PVID), and all untagged traffic travels on the
port default PVID. All untagged traffic and tagged traffic with a NULL VLAN ID are assumed to belong
to the port default PVID. A packet with a VLAN ID equal to the outgoing port default PVID is sent
To configure switch port mode to trunk port, use the following commands on interface configuration
mode.
Commands Descriptions
switchport mode trunk Set the switching characteristics of the switch port as trunk
and specify tagged frames only
switchport mode trunk ingress-filter Set the ingress filtering for the frames received.
[{enable | disable}] For enable, set the ingress filtering for received frames.
Received frames that cannot be classified based on the
acceptable frame type parameter are discarded.
For disable, turn off ingress filtering to accept frames that do
not meet the classification criteria.
The default value is disable.
no switchport trunk Reset the mode of switch port to access that is default.
If you set the ingress filtering to enable, received frames that cannot be classified based on the
Beginning in Enable mode, follow these steps to configure filtering function of trunk port.
Commands Description
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 4 bridge-group bridge-id Assign the switch port to a specified bridge group.
Step 5 switchport mode trunk Configure the switch port mode to trunk port.
Step 6 switchport mode trunk ingress-filter Enable or disable ingress filtering function on the switch
{enable | disable} port.
Step 9 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure fe2.4 port to trunk port and enable ingress filtering function.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.4
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode trunk
DUT-1(config-if)#switchport mode trunk ingress-filter enable
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.4
!
interface fe2.4
switchport
bridge-group 1
switchport mode trunk
switchport mode trunk ingress-filter enable
!
DUT-1#write memory
[OK]
DUT-1#
this case, you need to consider not only the number of PCs in network but also devices such as
switches in the network. For your system, you have to lock the port like MAC filtering before
To limit the maximum number of users connectable to a switch port, use the following command on
Commands Descriptions
mac limit limit-num Configure the number of MAC address connectable to the specified port.
The default configuration is no limitation of maximum number of MAC address.
no mac limit Delete limitation of number of MAC address to the specified port.
This example shows how to configure limitation of number of MAC address on fe1.1 port to 4.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#mac limit 4
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
line. In this event, traffic from every multicast group being joined in shall be transmitted to the
connected switch port and the other traffic of subscriber can be affected by the multicast traffic. To
solve this issue, you can set the maximum allowed multicast group limit per switch port on your system.
If you set the maximum allowed multicast group limit, the subscriber’s terminal can join only in limited
To set the maximum number of multicast group limit per switch port, use the following command on
Commands Descriptions
multicast group-limit limit-num Set the maximum allowed number of multicast group limit for the
interface. By default, there is no limitation of multicast group on
switch port.
no multicast group-limit Clear the maximum allowed number of multicast group limit for the
switch port.
This example shows how to set the maximum allowed multicast group limit of interface fe1.1 to 3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#multicast group-limit 3
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
can prevent a certain port to monopolize whole bandwidth so that all ports can use bandwidth equally.
You can configure egress and ingress bandwidth to be same and to be different.
To configure rate limit of switch port, use the following command on interface configuration mode.
Commands Descriptions
ratelimit {ingress | egress} bandwidth Configure the allowed bandwidth for the switch port. You can
rate burst burst-rate configure ingress and egress direction bandwidth separately.
ingress configures bandwidth to input direction, egress configures
bandwidth to output direction.
bandwidth rate configures allowable average transmit rate.
burst burst-rate configures allowed peak transmit rate.
no ratelimit {ingress | egress} Clear the configured bandwidth for the switch port.
When you set the bandwidth limitation function, you can configure it for the ingress and egress
direction separately. You can also configure not only maximum allowed bandwidth but also maximum
allowed burst. The maximum bandwidth means allowable average data rate, and the burst means
Note When you configure bandwidth on VX-MD3024, you can configure rate by bps unit. Also you can use
k (Kbps), m (Mbps), g (Gbps) unit for your convenience
Note When you configure burst on VX-MD3024, you can configure burst-rate by kbps unit. You can
configure Burst value to only multiples of 32kbps.
Beginning in Enable mode, follow these steps to configure maximum allowed bandwidth of a specified
switch port.
Commands Descriptions
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 3 ratelimit {ingress | egress} bandwidth Limiting Bandwidth of concerned Interface. Pointing out
rate burst burst-rate Ingress or egress, Bandwidth to Sending and Receiving
Traffic can be limited. burst-rate can be configured for th
Step 5 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure bandwidth limit of ingress traffic on the switch port fe1.1, and
burst to 32 Kbps.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#ratelimit ingress bandwidth 10m burst 32
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
To display the configured bandwidth limit of every switch port, use the show interface config
This example shows how to display the configured bandwidth limit of every switch port.
is called “mirror test port” and a port to be monitored is called “monitored port”. Traffics transmitted
from monitored port are copied and sent to mirror test port so that you can monitor it.
To configure port mirroring on VX-MD3024, use the following command on interface configuration
Commands Dscriptions
Commands Descriptions
Step 2 interface interface-name Enter interface configuration mode and the physical
interface to be configured.
Step 3 mirror interface interface-name direction Configuring Interface and Traffic Direction for Monitoring
{both | receive | transmit}
Step 6 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure port mirror function. In this example, interface ge2 is mirror test
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface ge2
DUT-1(config-if)#mirror interface fe1.1 direction receive
DUT-1(config-if)#mirror interface fe1.2 direction receive
DUT-1(config-if)#end
DUT-1#show mirror
----------------------------------------------------------
Mirror Test Port Name: ge2
Mirror option: Enabled
Mirror direction: receive
Monitored Port Name: fe1.1
----------------------------------------------------------
Mirror Test Port Name: ge2
Mirror option: Enabled
Mirror direction: receive
Monitored Port Name: fe1.2
----------------------------------------------------------
DUT-1#write memory
[OK]
DUT-1#
unicast storm on one of the physical interfaces. A LAN storm occurs when packets flood the LAN,
creating excessive traffic and degrading network performance. Errors in the protocol-stack
Storm control (or traffic suppression) monitors incoming traffic statistics over a time period and
compares the measurement with a predefined suppression level threshold. The threshold represents
the percentage of the total available bandwidth of the port. The system supports separate storm
control thresholds for broadcast, multicast, and unicast traffic. If the threshold of a traffic type is
reached, further traffic of that type is suppressed until the incoming traffic falls below the threshold
level.
By default, unicast, broadcast, and multicast storm control is disabled on the system; that is, the
Beginning in Enable mode, follow these steps to enable a particular type of storm control:
Commands Description
Step 2 interface interface-name Specify the type and number of the physical interface to
configure, and enter interface configuration mode.
Step 3 storm-control broadcast level Specify the broadcast traffic suppression level for an
level[.level] interface as a percentage of total bandwidth. The level
can be from 1 to 100; the optional fraction of a level can
be from 0 to 99. A threshold value of 100 percent
means that no limit is placed on broadcast traffic.
Step 4 storm-control multicast level level[.level] Specify the multicast traffic suppression level for an
interface as a percentage of total bandwidth. The level
can be from 1 to 100; the optional fraction of a level can
be from 0 to 99. A threshold value of 100 percent
means that no limit is placed on multicast traffic.
Step 5 storm-control dlf level level[.level] Specify the DLF (Destination Lookup Failure) traffic
suppression level for an interface as a percentage of
total bandwidth. The level can be from 1 to 100; the
optional fraction of a level can be from 0 to 99. A
threshold value of 100 percent means that no limit is
placed on multicast traffic.
Step 7 show storm-control [interface-name] Verify the storm control suppression levels set on the
interface for the specified traffic type. If you do not enter
a traffic type, broadcast storm control settings are
displayed.
Step 8 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure Multicast Storm control value to fe1.1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#storm-control multicast level 70.5
DUT-1(config-if)#end
DUT-1#show storm-control fe1.1
Port BcastLevel BcastDiscards McastLevel McastDiscards DlfLevel DlfDiscards
------------------------------------------------------------------------------
fe1.1 100. 0% 0 70. 5% 0 100. 0% 0
To disable storm control, use the following command on interface configuration mode.
Commans Descriptions
This example shows how to disable multicast storm control on interface fe1.1 and verify the
configuration.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#no storm-control multicast level
DUT-1(config-if)#end
DUT-1#show storm-control fe1.1
Port BcastLevel BcastDiscards McastLevel McastDiscards DlfLevel DlfDiscards
------- ---------- ------------- ---------- ------------- -------- ----------
fe1.1 100. 0% 0 100. 0% 0 100. 0% 0
other to communicate between computers. However, in case ISP(Internet Service Provider) provides
internet communication through LAN service to specific area such as apartments, customer’s
In this case, without NetBIOS filtering, customers’ data may be opened to each other even though the
data should be kept. In order to keep customer’s information and prevent sharing information in the
Beginning in Enable mode, follow these steps to enable NetBEUI/NetBIOS filtering function.
Commans Descriptions
Step 2 interface interface-name Specify the type and number of the physical interface to
configure, and enter interface configuration mode.
Step 8 write memory (Optional) Save your entries in the configuration mode.
This example shows how to enable NetBEUI and NetBIOS filter on switch port fe1.1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#netbeui-filtering
DUT-1(config-if)#nbipx-filtering
DUT-1(config-if)#end
DUT-1#show running-config interface fe1.1
!
interface fe1.1
switchport
bridge-group 1
switchport mode access
nbipx-filtering
netbeui-filtering
!
To disable NetBEUI and NetBIOS filter, use the following command on interface configuration mode.
Commands Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#no netbeui-filtering
DUT-1(config-if)#no nbipx-filtering
DUT-1(config-if)#end
DUT-1#show running-config interface fe1.1
!
interface fe1.1
switchport
bridge-group 1
switchport mode access
!
the other counters that are defined in IF-MIB and RMON-MIB. You can clear the interface counters
This section describes following items concerning to displaying on static information and Initializing
Function
To display average traffic load of each interface, use the following command on Enable mode.
Command Description
show interface statistics packet-rate Display average traffic load of a specified interface.
interface-name
This example shows how to display average traffic load of interface ge1.
You can show the raw packet counters classified by SNMP MIB type. The packet counter information
that you can get with the show interface statistics counters command and the traffic load information
that you can get with the show interface statistics packet rate command are provided by calculating
To display raw packet counters per SNMP standard group, use the following command on Enable
mode.
Commands Description
show interface statistics interface- Display raw packet counters of each kind of SNMP MIB group
name of specified port.
show interface statistics snmp Display raw packet counters of specified SNMP MIB group of
{additional | rfc1213 | rfc1493 | rfc1757 | the port.
rfc2233 | rfc2665} interface-name You can specify SNMP MIB group with following type:
rfc1213: IF-MIB in the MIB-II
rfc1493: Bridge-MIB
rfc1757: RMON-MIB
rfc2233: IF-MIB using SMIv2
rfc2665: EtherLike-MIB
additional: Out of SNMP Standard
This example shows how to display raw packet counters that are defined on rfc1213 of interface ge1.
You can clear the raw packet counter classified by SNMP MIB group. All traffic counter and average
traffic load information provided by VX-MD3024 system is calculated with these raw packet counters:
thus if you clear the raw packet counters, the counter information and traffic load information would be
To clear raw packet counters per SNMP MIB group, use the following command on Enable mode.
Command Description
clear interface statistics snmp Clear the raw packet counters of a interface.
interface-name
This example shows how to clear raw packet counters of interface ge1.
Commands Descriptions
Step 3 vlan vlan-id bridge bridge-id [name Add a VLAN by assigning a number to it. The range is 2 to
vlan-name] 4094.
If no name is entered for the VLAN, the default is to
append the vlan-id with leading zeros to the word VLAN.
For example, VLAN0004 is a default VLAN name for
VLAN 4.
Step 4 vlan vlan-id bridge bridge-id state Configure the status of VLAN.
{active | suspend} For state {active | suspend}, set the status of the VLAN.
The VLAN those status is suspend do not forward
packets.
Step 7 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vlan database
DUT-1(config-vlan)#vlan 250 bridge 1 name test_vlan
DUT-1(config-vlan)#end
DUT-1#
Commands Descriptions
Step 3 no vlan vlan-id bridge bridge-id Remove the VLAN by entering the VLAN ID.
Step 6 write memory (Optional) Save your entries the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#vlan database
DUT-1(config-vlan)#no vlan 250 bridge 1
DUT-1(config-vlan)#end
DUT-1#
Commands Descriptions
Step 4 bridge-group bridge-id Assign the switch port to a specified bridge group.
Step 5 switchport mode access Define the VLAN membership mode for the port (Layer 2
access port)
Step 6 switchport vlan access vlan-id Assign the port to a VLAN. Valid VLAN IDs are 2 to 4094;
do not enter leading zeros.
Step 9 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode access
DUT-1(config-if)#switchport access vlan 100
DUT-1(config-if)#end
DUT-1#
Commands Descriptions
switchport hybrid vlan vlan-id Set default VLAN ID of a hybrid port. By default, the default
VLAN ID of a hybrid port is 1 (system default VLAN).
no switchport hybrid vlan Remove the default VLAN ID of a hybrid port. At this time the
default VLAN ID of the hybrid port becomes 1.
Commands Descriptions
switchport hybrid allowed vlan all Allow all VLANs to transmit and receive through the hybrid
port.
switchport hybrid allowed vlan none Allow no VLANs to transmit and receive through the hybrid
port.
switchport hybrid allowd vlan add vlan-id Add a VLAN to the member set.
egress-tagged {enable | disable} For egress-tagged {enable|disable}, configure the egress
packet from a hybrid port to be untagged or tagged packet.
switchport hybrid allowd vlan remove Remove a VLAN from the member set.
vlan-id
Commands Descriptions
Step 4 bridge-group bridge-id Assign the switch port to a specified bridge group.
Step 5 switchport mode hybrid Configure the switch port’s mode to hybrid.
Step 6 switchport vlan hybrid vlan-id Set the default VLAN of the hybrid port.
Step 7 switchport vlan hybrid allowed vlan (Optional) Add a VLAN to the member set. For egress-
add vlan-id egress-tagged {enable | tagged {enable|disable}, configure the egress packet from
disable} a hybrid port to be untagged or tagged packet.
Step 8 switchport vlan hybrid allowed vlan (Optional) Remove a VLAN from the member set.
remove vlan-id
Step 11 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.1
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode hybrid
DUT-1(config-if)#switchport hybrid vlan 100
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.1
!
interface fe2.1
switchport
bridge-group 1
switchport mode hybrid
switchport hybrid vlan 100
switchport mode hybrid acceptable-frame-type all
switchport hybrid allowed vlan add 100 egress-tagged disable
!
DUT-1#
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.1
DUT-1(config-if)#switchport hybrid allowed vlan add 10 egress-tagged enable
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.1
!
interface fe2.1
switchport
bridge-group 1
switchport mode hybrid
switchport hybrid vlan 100
switchport mode hybrid acceptable-frame-type all
switchport hybrid allowed vlan add 10 egress-tagged enable
switchport hybrid allowed vlan add 100 egress-tagged disable
!
DUT-1#
Commands Descriptions
switchport trunk allowed vlan all Allow all VLANs to transmit and receive through the trunk port.
switchport trunk allowed vlan none Allow no VLANs to transmit and receive through the trunk port.
switchport trunk allowd vlan add vlan-id Add a VLAN to transmit and receive through the trunk port.
switchport trunk allowd vlan remove vlan- Remove a VLAN from transmit and receive through the trunk
id port.
switchport trunk allowd vlan except vlan- All VLANs, except the VLAN for which the ID is specified, are
id part of its ports member set.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.1
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 1
DUT-1(config-if)#switchport mode trunk
DUT-1(config-if)#switchport trunk allowed vlan add 10
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.1
!
interface fe2.1
switchport
bridge-group 1
switchport mode trunk
switchport trunk allowed vlan add 10
!
DUT-1#
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.1
DUT-1(config-if)#switchport trunk allowed vlan remove 10
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.1
!
interface fe2.1
switchport
bridge-group 1
switchport mode trunk
!
DUT-1#
Commands Descriptions
switchport trunk native vlan vlan-id Specify the native VLAN for trunk port.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe2.1
DUT-1(config-if)#switchport trunk allowed vlan add 100
DUT-1(config-if)#switchport trunk native vlan 100
DUT-1(config-if)#end
DUT-1#show running-config interface fe2.1
!
interface fe2.1
switchport
bridge-group 1
switchport mode trunk
switchport trunk allowed vlan add 100
switchport trunk native vlan 100
!
DUT-1#
Displaying VLAN
Commands Descriptions
This chapter describes how to configure the Spanning Tree Protocol (STP) on your system.
STP Overview
STP is a Layer 2 link management protocol that provides path redundancy while preventing loops in
the network. For a Layer 2 Ethernet network to function properly, only one active path can exist
between any two stations. Spanning-tree operation is transparent to end stations, which cannot detect
whether they are connected to a single LAN segment or a switched LAN of multiple segments.
When you create fault-tolerant internetworks, you must have a loop-free path between all nodes in a
network. The spanning-tree algorithm calculates the best loop-free path throughout a switched Layer 2
network. Switches send and receive spanning-tree frames, called bridge protocol data units (BPDUs),
at regular intervals. The switches do not forward these frames, but use the frames to construct a loop-
free path.
Multiple active paths among end stations cause loops in the network. If a loop exists in the network,
end stations might receive duplicate messages. Switches might also learn end-station MAC addresses
Spanning Tree defines a tree with a root switch and a loop-free path from the root to all switches in the
Layer 2 network. Spanning tree forces redundant data paths into a standby (blocked) state. If a
network segment in the spanning tree fails and a redundant path exists, the spanning-tree algorithm
When two interfaces on a switch are part of a loop, the spanning-tree port priority and path cost
settings determine which interface is put in the forwarding state and which is put in the blocking state.
The port priority value represents the location of an interface in the network topology and how well it is
located to pass traffic. The path cost value represents media speed.
All switches in the Layer 2 network participating in spanning tree gather information about other
switches in the network through an exchange of BPDU data messages. This exchange of messages
For each VLAN, the switch with the highest switch priority (the lowest numerical priority value) is
elected as the root switch. If all switches are configured with the default priority (32768), the switch
with the lowest MAC address in the VLAN becomes the root switch. The switch priority value occupies
When you change the switch priority value, you change the probability that the switch will be elected
as the root switch. Configuring a higher value decreases the probability; a lower value increases the
probability.
The root switch is the logical center of the spanning-tree topology in a switched network. All paths that
are not needed to reach the root switch from anywhere in the switched network are placed in the
BPDUs contain information about the sending switch and its ports, including switch and MAC address,
switch priority, port priority, and path cost. Spanning tree uses this information to elect the root switch
and root port for the switched network and the root port and designated port for each switched
segment.
In the below figure, Switch A is elected as the root switch because the switch priority of all the
switches is set to the default (32768) and Switch A has the lowest MAC address. However, because of
traffic patterns, number of forwarding interfaces, or link types, Switch A might not be the ideal root
switch. By increasing the priority (lowering the numerical value) of the ideal switch so that it becomes
the root switch, you force a spanning-tree recalculation to form a new topology with the ideal switch as
the root
DP
DP D
A
RP DP DP
DP
RP
RP
B C
RP = Root Port
DP = Designated Port
When the spanning-tree topology is calculated based on default parameters, the path between source
and destination end stations in a switched network might not be ideal. For instance, connecting higher-
speed links to an interface that has a higher number than the root port can cause a root-port change.
For example, assume that one port on Switch B is a Gigabit Ethernet link and that another port on
Switch B (a Fast Ethernet link) is the root port. Network traffic might be more efficient over the Gigabit
Ethernet link. By changing the spanning-tree port priority on the Gigabit Ethernet interface to a higher
priority (lower numerical value) than the root port, the Gigabit Ethernet interface becomes the new root
port.
Propagation delays can occur when protocol information passes through a switched LAN. As a result,
topology changes can take place at different times and at different places in a switched network. When
an interface transitions directly from nonparticipation in the spanning tree topology to the forwarding
state, it can create temporary data loops. Interfaces must wait for new topology information to
propagate through the switched LAN before starting to forward frames. They must allow the frame
lifetime to expire for forwarded frames that have used the old topology.
Each Layer 2 interface on a switch using spanning tree exists in one of these states
9 –
9 –
9 –
9 –
The below figure illustrates how an interface moves through the states.
Pow er-on
initialization
Blocking
State
Listening
D isabled
State
State
Learning
State
Forw arding
State
When you power up the system, STP is enabled by default, and every interface in the switch, VLAN or
network goes through the blocking state and the transitory states of listening and learning. Spanning
When the spanning-tree algorithm places a Layer 2 interface in the forwarding state, this process
occurs:
1. The interface is in the listening state while spanning tree waits for protocol information to
2. While spanning tree waits the forward-delay timer to expire, it moves the interface to the
3. In the learning state, the interface continues to block frame forwarding as the switch learns end-
4. When the forward-delay timer expires, spanning tree moves the interface to the forwarding
forwards non-IP protocols such as DECnet between two or more VLAN bridge domains or routed ports.
The VLAN-bridge STP allows the bridge groups to form a spanning tree on top of the individual VLAN
spanning trees to prevent loops from forming if there are multiple connections among VLANs. It also
prevents the individual spanning trees from the VLANs being bridged from collapsing into a single
spanning tree.
Fallback Bridging
With fallback bridging, the switch bridges together two or more VLANs or routed ports, essentially
connecting multiple VLANs within one bridge domain. Fallback bridging forwards traffic that the switch
does not route and forwards traffic belonging to a nonroutable protocol such as DECnet.
Fallback bridging does not allow the spanning trees from the VLANs being bridged to collapse; each
VLAN has its own spanning-tree instance and a separate spanning tree, called the VLAN-bridge
spanning tree, which runs on top of the bridge group to prevent loops.
A VLAN bridge domain is represented with switch virtual interface (SVI). A set of SVIs and routed ports
(which do not have any VLANs associated with them) can be configured (grouped together) to form a
bridge group. Recall that an SVI represents a VLAN of switch ports as one interface to the routing or
A bridge group is an internal organization of network interfaces on a system. Bridge groups can not be
used to identify traffic switched within the bridge group outside the switch on which they are defined.
Bridge groups on the same switch function as distinct bridges; that is, bridged traffic and bridge
protocol data units (BPDUs) are not exchanged between different bridge groups on a system. An
interface can be member of only one bridge group. Use a bridge group for each separately bridged
bridge groups. All interfaces in the same group belong to the same bridge domain. A maximum of 32
Beginning in Enable mode, follows these steps to create bridge group and assign an interface to it.
Command Description
Step 2 bridge bridge-group protocol ieee Assign a bridge group number, and specify the VLAN-bridge
vlan-bridge spanning tree protocol to run in the bridge group.
For bridge-group, specify the bridge group number.The range
is 1 to 32.
Frames are bridged only among interfaces in the same group.
Step 3 interface interface-id Enter interface configuration mode, and specify the interface
on which you want to assign the bridge group
Step 4 bridge-group bridge-group Assign the interface to the bridge group created in Step 2.
By default, the interface is assigned to bridge group 1. An
interface can be assigned to only one bridge group.
Step 7 write memory (Optional) Save your entries in the configuration file.
To remove a bridge group, use the no bridge bridge-group global configuration command. To remove
an interface from a bridge group and to remove the bridge group, use the no bridge-group bridge-
group interface configuration command.
This example shows how to create bridge group 10, to specify the VLAN-bridge STP to run in the
bridge group. It assignes the interface fe1.1 to the bridge group and assigns to VLAN 100.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 10 protocol ieee vlan-bridge
DUT-1(config)#vlan database
DUT-1(config-vlan)#vlan 100 bridge 10
DUT-1(config-vlan)#exit
DUT-1(config)#interface fe1.1
DUT-1(config-if)#switchport
DUT-1(config-if)#bridge-group 10
DUT-1(config-if)#switchport mode access
DUT-1(config-if)#switchport access vlan 100
DUT-1(config-if)#end
DUT-1#
You can globally configure the priority of an individual system when two switches tie for position as the
root switch, or you can configure the likelihood that a switch will be selected as the root switch. This
Beginning in Enable mode, follow these steps to change the switch priority.
Command Description
Step 2 bridge bridge-group priority number Change the priority of the system.
For bridge-grouop, specify the bridge group number. The
range is 1 to 32.
For number, enter a number from 0 to 61440. The default
is 32768. The lower the number, the more likely the
system will be chosen as the root.
Step 5 write memory (Optional) Save your entry in the configuration file.
This example shows how to set the switch priority to 4096 for bridge group 1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 1 priority 4096
DUT-1(config)#
If a loop occurs, spanning tree uses the port priority when selecting an interface to put into the
forwarding state. You can assign higher priority values (lower numerical values) to interfaces that you
want selected first and lower priority values (higher numerical values) that you want selected last. If all
interfaces have the same priority value, spanning tree puts the interface with the lowest interface
Beginning in Enable mode, follow these steps to configure the port priority of an interface.
Command Descriptioin
Step 2 interface interface-id Enter interface configuration mode, and specify the
interface to set the priority.
range is 1 to 32.
For number, enter a number from 0 to 255. The lower
number, the more likely that the interface on the system
will be chosen as the root. The default is 128.
Step 6 write memory (Optional) Save your entry in the configuration file.
This example shows how to change the priority of the interface fe1.1 to 32 in bridge group 1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#bridge-group 1 priority 32
DUT-1(config-if)#end
DUT-1#
The spanning tree path cost default value is derived from the media speed of an interface. If a loop
occurs, spanning tree uses cost when selecting an interface to put in the forwarding sate. You can
assign lower cost values to interfaces that you want selected first and higher cost values that you want
selected last. If all interfaces have the same cost value, spanning tree puts the interface with the
lowest interface number in the forwarding state and blocks the other interfaces.
By convention, the path cost is 1000/data rate of the attached LAN, in Mbps.
Command Description
Step 6 write memory (Optional) Save your entry in the configuration file.
Below table shows the path cost value according to link speed
1 Gbps 4 3 - 10 IEEE
To return to the default path cost, use the no bridge-group bridge-group path-cost interface
configuration command.
This example shows how to change the path cost on the interface fe1.1 in bridge group 1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#bridge-group 1 path-cost 20
DUT-1(config-if)#end
DUT-1#write memory
[OK]
DUT-1#
You can configure the interval between the generation of configuration messages by the root switch by
Beginning in Enable mode, follow these steps to configure the hello time.
Command Description
Step 2 bridge bridge-group hello-time Specify the interval between hello BPDUs.
seconds For bridge-group, specify the bridge group number. The
range is 1 to 32.
For seconds, enter a number from 1 to 10. The default is 2
seconds.
Step 5 write memory (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group hello-time global configuration
command.
This example shows how to change the hello interval to 5 seconds in bridge group 1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 1 hello-time 5
DUT-1(config)#end
DUT-1#
The Forward-delay interval is the amount of time spent listening for topology change information after
an interface has been activated for switching and before forwarding actually begins.
Beginning in Enable mode, follow these steps to change the forward-delay intervals:
Command Description
Step 2 bridge bridge-group forward-time Specify the interval between hello BPDUs.
seconds For bridge-group, specify the bridge group number. The
range is 1 to 32.
For seconds, enter a number from 4 to 30. The default is
15 seconds.
Step 5 write memory (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group forward-time global configuration
command.
This example shows how to change the forward-delay interval to 20 seconds in bridge group1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 1 forward-time 20
DUT-1(config)#end
DUT-1#
If a system does not receive BPDUs from the root switch within a specified interval, it tries to
Beginning in Enable mode, follow these steps to change the maximum-age time.
Command Descriptioni
Step 2 bridge bridge-group max-age seconds Specify the interval between hello BPDUs.
For bridge-group, specify the bridge group number. The
range is 1 to 32.
For seconds, enter a number from 6 to 40. The default is
20 seconds.
Step 5 write memory (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group max-age global configuration
command.
This example shows how to change the maximum-age time to 15 in bridge group 1.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#bridge 1 max-age 15
DUT-1(config)#end
DUT-1#
Command Description
This example shows how to display the spanning tree information of the system.
DUT-1#show spanning-tree
% 1: spanning tree disabled
% 1: root path cost 0 - priority 32768
% 1: forward-time 11 - hello-time 5 - max-age 20 - root port 0
% 1: root id 8000000edc005300
% 1: bridge id 8000000edc005300
% 1: hello timer 0 - tcn timer 0 - topo change timer 0
% 1: 0 topology changes - last topology change Thu Jan 1 00:00:00 1970
% 1: portfast bpdu-filter disabled
% 1: portfast bpdu-guard disabled
% 1: portfast errdisable timeout disabled
% 1: portfast errdisable timeout interval 1 sec
% ge2: port 28 - id 801c - path cost 20000000 - designated cost 0
% ge2: designated port id 801c - state Forwarding - priority 128
% ge2: designated root 8000000edc005300
% ge2: designated bridge 8000000edc005300
% ge2: forward-timer 0 - hold-timer 0 - msg age timer 0
% ge2: forward-transitions 1
% ge2: portfast disabled
% ge2: portfast bpdu-guard default - Current portfast bpdu-guard off
% ge2: portfast bpdu-filter default - Current portfast bpdu-filter off
% ge2: no root guard configured - Current root guard off
(output truncated)
This chapter describes how to configure the Dynamic Host Configuration Protocol (DHCP).
dynamically. You can configure the global characteristics and each subnet’s feature of the DHCP
server.
To configure the DHCP server feature, first configure IP addresses that the DHCP server would assign
to requesting clients, and configure information to transmit to the clients. IP address configuration
9
9
9
9
9
9
9
9
Configuration procedures for transmitting information to the clients are described in the following
sections.
9
9
9
9
9
9
9
9
9
Global configuration procedures setting the all of the DHCP subnet are described in the following
sections.
9
9
9
9
DHCP subnet is an object that is related with each network address. For example, in order to assign
an IP address belonging to 192.168.31.0/24 to the clients, you must create a subnet first and configure
the network address of the subnet. There is no limit of number of DHCP subnet on your system.
You can configure a DHCP subnet with a name that is a symbolic string (such as “test”). Configuring a
DHCP subnet places you in DHCP subnet configuration mode – identified by the (dhcp-config)#
prompt – from which you can configure subnet parameters (for example, the network address and
Command Description
Step 2 ip dhcp subnet subnet-name Assign the name of the DHCP subnet to create.
If you enter the subnet name that is already exist, you can configure features of the DHCP subnet on
the DHCP subnet mode. And if you enter a new subnet name, a new subnet would be created and you
can move to the DHCP subnet mode to configure features of the new DHCP subnet.
This example shows how to create a DHCP subnet and display it.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
subnet "test" is newly created
DUT-1(dhcp-config)#end
DUT-1#show ip dhcp
dhcp server disabled
“ ”
The first thing to configure a DHCP subnet is assigning network address of the subnet. The available
IP addresses that the DHCP server may assign to clients shall be included in the network address of
the subnet.
Beginning in Enable mode, follow these steps to configure network address of DHCP subnet.
Command Description
Step 2 ip dhcp subnet subnet-name Enter DHCP subnet configuration mode and assign the
name of the DHCP subnet.
This example shows how to configure the network address of DHCP subnet named test to
192.168.31.0/24.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#network 192.168.31.0/24
DUT-1(dhcp-config)#end
You can configure DHCP address pool to assign to clients. The IP addresses including in this DHCP
address pool are dynamically assigned to clients. You can find the Static IP address assigning method
and per port IP address assigning method (Port-Entry function) in the following sections.
Beginning in Enable mode, follow these steps to configure DHCP address pool.
Commands Description
Step 2 ip dhcp subnet subnet-name Enter DHCP subnet configuration mode and
assign the name of the DHCP subnet.
Step 3 pool pool-name ip A.B.C.D [A.B.C.D] Assign the name of the DHCP address pool
and IP address range to assign to the clients.
For pool-name, specify the DHCP address
pool.
For A.B.C.D [A.B.C.D], specify the range of IP
addresses to assign to the clients. You can set
only one IP address in this field.
Step 4 pool pool-name subnet-mask A.B.C.D Set the subnet mask of a specified DHCP
address pool. If you don’t enter this command,
the DHCP address pool use the network mask
of the DHCP subnet.
For A.B.C.D, specify the subnet mask.
You must configure the network address of a DHCP subnet before configuring DHCP address pool.
And you can configure only the IP address range of the DHCP address pool included in network
For example, you can assign only the IP address range from192.168.31.0 to 192.168.31.255 to the
DHCP address pool within the network of which network address is 192.168.31.0/24.
This example shows how to configure address 192.168.31.2 and the range between 192.168.31.10
and 192.168.31.99 to the DHCP address pool in the DHCP subnet named test.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#pool testpool ip 192.168.31.2
DUT-1(dhcp-config)#pool testpool ip 192.168.31.10 192.168.31.99
DUT-1(dhcp-config)#end
An address binding is a mapping between the IP address and Media Access Control (MAC) address of
Manual bindings are IP addresses that have been manually mapped to the MAC addresses of hosts
that are found in the DHCP database. Manual bindings are stored in the configuration on the DHCP
server. Manual bindings are just special address pools. There is no limit on the number of manual
bindings but you can only configure one manual binding per host pool.
Automatic bindings are IP addresses that have been automatically mapped to the MAC addresses of
hosts that are found in the DHCP database. Automatic bindings are stored on a remote host called
database agent. The bindings are saved as text records for easy maintenance.
To configure a manual binding, first create a DHCP address pool, then specify the IP address and
hardware address of the client. The hardware address is the MAC address.
Commands Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure manual binding that the static IP address is 192.168.31.5 and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#static ip 192.168.31.5 mac 00:01:02:03:04:05
DUT-1(dhcp-config)#end
DUT-1#
You can configure the IP address to be assigned to the specific port with port entry function.
Beginning in Enable mode, follow these steps to configure port entry function.
Commands Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and places
you in DHCP subnet configuration mode –
identified by the (dhcp-config)# prompt.
Step 3 port-entry if-name A.B.C.D [A.B.C.D] Specify the assigning IP address range to the
[vendor-id vendor-id] specific interface.
For if-name, specify the name of the L2 interface.
For A.B.C.D A.B.C.D, specify the IP address range
assigned to the interface.
For vendor-id, specify the vendor identifier that is
string type.
As you configure port entry function, the vendor ID item is optional. If you specify vendor ID of an
interface, only the client that has vendor ID in the interface can be assigned the specified IP address in
the port-entry configuration. If you don’t specify vendor ID, the client connected in the interface can be
This example shows how to configure port entry function that the range of IP address from
192.168.31.100 to 192.168.31 to be assigned to the clients those are connected to the physical port
fe1.4.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#port-entry fe1.4 192.168.31.100 192.168.31.103
DUT-1(dhcp-config)#end
DUT-1#
The next example shows how to configure port entry function that IP address range between
192.168.31.104 and 192.168.31.105 to be assigned to the clients having vender ID “MSFT 5.0” and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#port-entry fe1.4 192.168.31.104 192.168.31.105 vendor-id
MSFT 5.0
DUT-1(dhcp-config)#end
There are three types of IP address assigning method as of dynamic binding, manual binding and
Following figure shows steps how to find out proper IP addresses when the system received IP
If the DHCP server received IP address request from clients, it examine list of the static IP address
first. It checks whether the static IP address is defined in the configuration and if static IP address is
defined and the requesting client’s MAC address is same, then assign the static IP address to the
client.
If the client’s MAC address is not configured with the static IP address in the DHCP server
configuration, DHCP server checks that the interface which IP address request received from is
defined in the port-entry configuration. There is two kind of type of port-entry configuration. One is
defined with vendor ID, and the other is defined without vendor ID. If the port-entry is defined with
vendor ID, the DHCP server only assign IP address defined in port-entry to the client when the vendor
ID of the client is same with the vendor ID of the defined in the port-entry. If there is not port-entry
which has the same vendor ID with the client’s vendor ID, DHCP server find the port-entry without
vendor ID definition. If there is any port-entry without vendor ID definition for the interface that is
connected to the client, it assigns the IP address defined in the port-entry to the client. But if there is
not port-entry without vendor ID definition, the assigning IP address procedure is failed.
If the port-entry is not configured to the physical interface with which the client is connected, assign an
IP address in the dynamic address pool to the client. If all of the IP addresses in the dynamic address
pool are already allocated to the other clients, assigning IP address procedure is failed. And the DHCP
server checks whether the IP address that is assigned but not used by client is exist or not. If you
enable this checking function, the unused IP address will be assigned to the client which requests IP
Beginning in Enable mode, follow these steps to activate DHCP server function.
Command Description
To deactivate DHCP server function, use no service dhcp command in global configuration mode.
This example shows how to enable DHCP server function and display the status of DHCP server.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#service dhcp
DUT-1(config)#end
DUT-1#show ip dhcp
dhcp server enabled
dhcp server running now
dhcp subnet list: test
Number of ARP packets for IP Address confirmimg : NOT DOING
Denied interface:NONE
Lease Limits :
NONE.
ping-check : disabled
arp-check : disabled
DUT-1#
You can display the information of address binding with the various conditions. Beginning in Enable
description
show ip dhcp bind-info ip A.B.C.D [A.B.C.D] Display only the binding information which has
[detail] the address included in the specified address
range.
show ip dhcp bind-info subnet subnet-name Display only the binding information of which
[detail] address is assigned in the specified subnet.
show ip dhcp bind-info status { active | free | Display the IP addresses of which status is the
show ip dhcp bind-info type { dynamic | port-entry Display the binding information of which the
| static } [detail] address assigning method is same with the
specified binding method.
show ip dhcp bind-info statistics Display only the statistics of address binding.
This example shows how to display information of address binding of which IP address is included in
Basically, only one IP address shall be assigned to a client that has a MAC address. But sometimes,
several IP addresses can be assigned to a client with a MAC address. To prevent a client with a MAC
address be assigned several IP address from the DHCP server, you can configure that only one IP
Beginning in Enable mode, follow these steps to configure only one IP address is assigned to the
Command Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
After DHCP client has booted, the client begins sending packets to its default router. The IP address of
the default router should be on the same subnet as the client. Beginning in Enable mode, follow these
Command Description
Step 2 ip dhcp subnet subne-tname Creates a name for the DHCP subnet and places you
in DHCP subnet configuration mode – identified by
the (dhcp-config)# prompt.
Step 3 default-router A.B.C.D Specifies the IP address of the default router for a
DHCP client.
This example shows how to configure the IP address of the default router for a DHCP client
to192.168.31.254.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#default-router 192.168.31.254
DUT-1(dhcp-config)#end
DUT-1#
By default, each IP address assigned by a DHCP server comes with a one-day lease, which is the
amount of time that the address is valid. Beginning in Enable mode, follow these steps to change the
Command Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
Step 3 lease { <day> <hour> <minute> <second> | Specifies the duration of the lease. The default
infinite } is a one-day lease.
This example shows how to configure IP address lease time to1 hour and 20 minutes.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#lease 0 1 20 0
DUT-1(dhcp-config)#end
DUT-1#
Log server is DHCP option 7. It specifies the IP address of SYSLOG server that the client should send
error messages and other logging information. Beginning in Enable mode, follow these steps to
Comman Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure IP address of log server to 100.10.10.254 and 100.10.11.254.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#log-server 100.10.10.254
DUT-1(dhcp-config)#log-server 100.10.11.254
DUT-1(dhcp-config)#end
DUT-1#
Configuring Merit-dump
Merit-dump is DHCP option 14. Merit-dump configuration specifies the path of the file dumped when it
Beginning in Enable mode, follow these steps to configure a merit dump for a DHCP client.
Command Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure the path of merit-dump to “/etc/merit” to the client .
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#merit-dump /etc/merit
DUT-1(dhcp-config)#end
DUT-1#
Configuring Root-path
Root-path configuring is DHCP option 17. It specifies the path name that contains the root disk of the
client. The path is formatted as ASCII text. For this option type, data used for a value is ASCII
character text.
Beginning in Enable mode, follow these steps to configure a root path for a DHCP client.
Command Description
Step 2 ip dhcp subnet subnet-name Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#root-path /home/user
DUT-1(dhcp-config)#end
DUT-1#show ip dhcp subnet test
Subnet test(index = 1) :
network: 192.168.31.0/24
interface : not configured
IP address Pool(s) :
Pool "testpool"
Subnet Mask : 255.255.255.0
IP Address Range(s):
192.168.31.2
192.168.31.10 ~ 192.168.31.99
lease <days:hours:minutes:seconds> <0:1:20:0>
no domain is defined
no dns-servers
default-router(s): 192.168.31.254
static IP Assignment :
192.168.31.5 <-> 00:01:02:03:04:05
no ntp servers
Log Server List : 100.10.10.254, 100.10.11.254,
no DHCP Max Message Size
merit-dump : /etc/merit
root path : /home/user
port-entry Trusted Vendor ID : none
port-entry for fe1.4
Vendor-ID : MSFT 5.0
IP Address :
192.168.31.104 ~ 192.168.31.105
port-entry for fe1.4
Vendor-ID : NOT SPECIFIED
IP Address :
192.168.31.100 ~ 192.168.31.103
one-lease-per-client is enabled
DUT-1#
NTP server is DHCP option 42. It specifies the IP addresses in the order of preference for Network
Beginning in Enable mode, follow these steps to configure the IP address of NTP server for a DHCP
client.
Command Description
Step 2 ip dhcp subnet subnetname Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure IP address of NTP server to 132.11.23.55 and 132.11.23.56 to
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#ntp-server 132.11.23.55
DUT-1(dhcp-config)#ntp-server 132.11.23.56
DUT-1(dhcp-config)#end
DUT-1#
Maximum length of DHCP massage is DHCP option 57. This configuration specifies the maximum
Beginning in Enable mode, follow these steps to configure the maximum length of DHCP message for
a DHCP client.
Command Description
Step 2 ip dhcp subnet subnetname Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure maximum length of DHCP massage to 10000.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#max-message-size 10000
DUT-1(dhcp-config)#end
DUT-1#
DHCP clients query DNS servers when they need to correlate host names to IP addresses.
Beginning in Enable mode, follow these steps to configure the DNS servers that are available to a
DHCP client.
Command Description
Step 2 ip dhcp subnet subnetname Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
This example shows how to configure IP address of DNS server to 168.126.63.1 and 168.126.63.2 to
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#dns-server 168.126.63.1
DUT-1(dhcp-config)#dns-server 168.126.63.2
DUT-1(dhcp-config)#end
DUT-1#
The domain name of a DHCP client places the client in the general grouping of networks that make up
the domain.
Beginning in Enable mode, follow these steps to configure a domain name string for the client.
Command Description
Step 2 ip dhcp subnet subnetname Creates a name for the DHCP subnet and
places you in DHCP subnet configuration
mode – identified by the (dhcp-config)#
prompt.
Step 3 domain-name <domainname> Specifies the domain name for the client.
This example shows how to configure the domain name of the client to versatek.com.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp subnet test
DUT-1(dhcp-config)#domain-name versatek.com
DUT-1(dhcp-config)#end
DUT-1#
You can configure the limitation of the allowed number of IP address per physical interface. By default,
Beginning in Enable mode, follow these steps to configure the allowed number of IP address for the
physical interface.
Command Description
Step 2 ip dhcp lease-limit <if-name> <max-ip> Specifies the allowed number of IP address for
the interface.
For if-name, specifies the interface name.
For max-ip, specifies the maximum allowed
number of IP address.
This example shows how to configure maximum allowed number of IP address for the physical port
fe1.1 to 40.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp lease-limit fe1.1 40
DUT-1(config)#end
DUT-1#show ip dhcp
dhcp server enabled
dhcp server running now
dhcp subnet list: test
Number of ARP packets for IP Address confirmimg : NOT DOING
Denied interface:NONE
Lease Limits :
physical interface fe1.1 limited maximum 40 IP(s)
ping-check : disabled
arp-check : disabled
DUT-1#
Basically, DHCP server configuring is enable to every L3 interface. But you can disable the DHCP
Beginning in Enable mode, follow these steps to disable DHCP server function of a L3 interface.
Command Description
This example shows how to configure “eth0” of L3 interface to be out of DHCP server function and
display it.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp deny-interface eth0
DUT-1(config)#end
DUT-1#show ip dhcp
dhcp server enabled
dhcp server running now
dhcp subnet list: test
Number of ARP packets for IP Address confirmimg : NOT DOING
Denied interface: eth0
Lease Limits :
physical interface fe1.1 limited maximum 40 IP(s)
ping-check : disabled
arp-check : disabled
DUT-1#
You can configure the DHCP server of your system to confirm the using IP address of clients when
Beginning in Enable mode, follow these steps to configure the validation function of already assigned
IP address usability.
Command Description
When dynamic IP pool is used out and a new request of IP address from new client, your system
sends ARP request packets about already assigned IP address by every 1 second. If the ARP reply
packet is not received, it shall be judged abnormal client and change the IP address’s status to free.
Thus this IP address can be assigned to the client that request an IP address next time.
This example shows how to configure the number of ARP packet used for confirming IP address to 5.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp address-confirm-by-arp 5
DUT-1(config)#end
DUT-1#show ip dhcp
dhcp server enabled
dhcp server running now
dhcp subnet list: test
Number of ARP packets for IP Address confirmimg : 5
Denied interface: eth0
Lease Limits :
physical interface fe1.1 limited maximum 40 IP(s)
ping-check : disabled
arp-check : disabled
DUT-1#
When IP address shall be assigned to a client, there’ll be a possibility for any other client to use the IP
address illegally. If this IP address is assigned to a client, the client cannot be made a communication
by this collision IP address. To avoid this status, you can configure the confirming function that checks
whether the IP address is in use by other client with ARP or ICMP ping packets. If you enable the IP
address checking function with ARP packets, the DHCP server sends specified number of ARP
packets to a pool address before assigning the address to a requesting client. If the ping is
unanswered, the DHCP server assumes (with a high probability) that the address is not in use and
Beginning in Enable mode, follow these steps to enable and specify the number of ARP packets send
Command Description
Step 2 ip dhcp arp-check <count> Specifies the number of ARP packets the
DHCP server sends to a pool address before
assigning the address to q requesting client.
To enable and specify the number of ICMP ping packets send to the pool address before assigning the
Command Description
Step 2 ip dhcp ping-check <count> Specifies the number of ICMP ping packets the
DHCP server sends to a pool address before
assigning the address to q requesting client.
Both of ARP and ICMP ping cannot be used at the same time to check the using of IP address. And
This example shows how to configure the number of ping packets the DHCP server should send to the
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp ping-check 5
DUT-1(config)#end
DUT-1#show ip dhcp
dhcp server enabled
dhcp server running now
dhcp subnet list: test
Number of ARP packets for IP Address confirmimg : 5
Denied interface: eth0
Lease Limits :
physical interface fe1.1 limited maximum 40 IP(s)
ping-check : enabled(request 5 times)
arp-check : disabled
DUT-1#
clients. The DHCP Relay agent function relays the DHCP requests from clients to the DHCP server of
−
−
A DHCP relay agent is any device that forwards DHCP packets between clients and servers when they
are not on the same physical subnet. Relay agent forwarding is distinct from the normal forwarding of
an IP router, when IP datagrams are transparently switched between networks. By contrast, relay
agents receive DHCP messages and the generate a new DHCP message to send on another interface.
If the DHCP server and the DHCP clients are on different networks or subnets, you must configure the
switch with the ip dhcp-relay A.B.C.D command in global configuration mode. The general rule is to
configure the command on Layer 3 interface closest to the client. The address used in the ip dhcp-
realy A.B.C,D command can be a specific DHCP server IP address, or it can be the network address if
other DHCP servers on the destination network segment. Using the network address enables any
Beginning in Enable mode, follow these steps to specify the packet forwarding address.
Command Description
address
To remove the DHCP packet forwarding address, use the no ip dhcp-relay A.B.C.D global
configuration command.
This example shows how to configure the IP address of DHCP to 10.10.10.254, 10.10.20.254, and
10.10.30.254.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-relay 10.10.10.254
DUT-1(config)#ip dhcp-relay 10.10.20.254
DUT-1(config)#ip dhcp-relay 10.10.30.254
DUT-1(config)#end
DUT-1#show ip dhcp-relay
DHCP Relay Service : Disabled
Beginning in Enable mode, follow these steps to enable the DHCP relay agent.
Command Description
Step 2 service dhcp-relay Enable the DHCP relay agent on your system.
By default, this feature is not enabled.
To disable the DHCP relay agent, use the no service dhcp-relay global configuration command.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#service dhcp-relay
DUT-1(config)#end
DUT-1#show ip dhcp-relay
DHCP Relay Service : Enabled
9
9
9
9
9
9
9
9
9
9
9
9
9
DHCP snooping is a DHCP security feature that provides network security by filtering using
unassigned IP address by DHCP server and by building and maintaining a DHCP Snooping binding
The DHCP snooping lease entry contains the MAC address, the IP address, the remaining lease time,
the binding type, and the physical interface. A DHCP lease entry shall be deleted automatically when
the client release the IP address explicitly or expired lease time. And you can create a DHCP snooping
lease entry by manual. The maximum number of lease entry per physical interface is 4 and this
number includes not only dynamic entry but also static least entry.
When the DHCP snooping mode turn into normal mode, only the clients registered in DHCP snooping
lease entry can make a communication through your system. In the normal mode, your system permits
only packets that have registered source IP address in the DHCP snooping lease entry and DHCP
packets. And the ARP packet of which the sender IP address is the registered IP address and source
MAC address is the registered MAC address shall be permitted. The other packets shall be discarded.
DHCP snoop mode shall be normal mode, passing mode, and permit mode. You can configure the
DHCP snoop mode per port basis. The following table summary the characteristics of the DHCP
snooping mode.
Permit mode If the DHCP snooping mode of a physical interface is permit mode, all
kind of packets received from this interface are allowed. The DHCP
snooping mode of the interface will be automatically moved to normal
mode, when the mode transition timer expired or when the mode
transition trigger happed. If you set the initial DHCP snoop mode of a
physical interface, the DHCP snooping mode of the interface starts from
permit mode after system initialization.
Passing mode All of the packets received from the interface of which the DHCP snooping
mode is passing mode are allowed. In this mode, the mode transition
timer do not work.
After at least one IP address is registered in the DHCP snooping lease
entry, the DHCP snooping mode of the interface move to the normal mode
automatically.
You can configure this mode to be initial mode of a physical interface. In
this case, the DHCP snooping mode of the interface starts from passing
mode after system initialization.
Normal mode Only the DHCP packets and the packets that has the source IP address
and the hardware address registered in the DHCP snooping lease entry
are allowed in this mode.
The DHCP snooping mode is able to move to the other DHCP snooping
mode by only user command. If you set the initial DHCP snooping mode
The following figure describes the DHCP snooping mode transition of a physical interface.
Permit
Mode Expire mode transition timer or
Happen mode transition trigger
System Up Normal
Mode
As above figure, each physical port’s DHCP snooping mode is configured divided into current mode
and initial mode. When the DHCP snooping function is enabled after initializing system, the DHCP
snooping mode of each physical interface starts from permit mode or passing mode according to the
initial DHCP snooping mode configured by you. The initial mode is the starting DHCP snooping mode
of the physical interface, the first mode of the physical interface becomes the initial mode after
rebooting system. The current mode is related with real working method of the DHCP snooping
function. The current mode is able to transit to the other mode after the mode transition timer expire or
After reboot your system, the physical interface of which the initial mode is configured to permitting
mode start with permit mode. In this case all of packets received from the physical interface are
allowed. After the mode transition timer is expired, the DHCP snooping mode is automatically moved
to normal mode, and only packets those have allowed IP address will be allowed in the interface. And
after the mode transition trigger condition has happened, the DHCP snooping mode is changed to
normal mode also. By default, the mode transition timer is 1800 seconds, and the mode transition
trigger is 2.
After reboot your system, the physical interface of which initial mode is configured to passing mode do
work as same as the interface of which initial mode is permitting mode. But the DHCP snooping mode
of the physical interface would not change to the normal mode by expiring the transition timer. In this
mode, the DHCP snooping mode only change to the normal mode after at least one lease entry is
You can configure the initial mode of the physical interface to only the passing mode and permit mode.
This limit is added to escape the blocking service problem that can be reached because the clients do
As above, the DHCP snooping mode automatically transit to the proper mode and you can configure
the DHCP snooping mode. And you can configure that the DHCP snooping mode would not be
changed automatically.
Beginning in Enable mode, follow these steps to enable the DHCP snooping globally.
Command Description
To disable DHCP snooping globally, use the no service dhcp-snoop global configuration command.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#service dhcp-snoop
DUT-1(config)#end
Beginning in Enable mode, follow these steps to enable the DHCP snooping on physical interface.
Command Description
To disable DHCP snooping on a physical interface, use the ip dhcp-snoop if-name command on
global configuration mode.
By default, the DHCP snooping status of the downstream link which are fe1.1 ~ fe3.8 is enable, and
one of the upstream link which are ge1 and ge2 is disable. This example shows how to disable DHCP
snoop function of fe1.3 and fe1.4 interface and display the result status.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no ip dhcp-snoop fe1.3
DUT-1(config)#no ip dhcp-snoop fe1.4
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
-------------------------------------------------------------------------
fe1.1 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe1.2 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe1.3 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.4 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
(omitted)
fe3.4 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.6 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.7 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.8 ENABLE Permit Normal N/A / 1800 4 2 0 ON
ge1 DISABLE Permit Permit N/A / 1800 4 2 0 ON
ge2 DISABLE Permit Permit N/A / 1800 4 2 0 ON
DUT-1#
Beginning in Enable mode, follow these steps to configure the DHCP snooping mode of physical
interface.
Command Description
Step 2 ip dhcp-snoop <if-name> mode { normal | Configure the DHCP snooping mode to the
passing | permit } [manually] specified mode.
For if-name, specify the physical interface to
configure DHCP snooping mode.
For {normal | passing | permit}, specify the
DHCP snooping mode to configure.
For manually, specify this keyword for the
DHCP snooping mode to stick to the specified
mode after configuring the DHCP snooping
mode. If you don’t specify this keyword, the
DHCP snooping mode automatically changed
to the other mode by DHCP snooping mode
transition condition.
When you configure the DHCP snooping mode of a physical interface to the passing mode or the
permit mode, if you use the keyword manually, the DHCP snooping mode of the interface would not
change to the normal mode in spite of expiring the mode transition timer or happening mode transition
condition.
And if you configure the DHCP snooping mode with manually keyword, when the configuration could
be stored in configuration file and the DHCP snooping mode will be in use in the next booting time.
This example shows how to configure the DHCP snooping mode of the physical interface fe1.1 to the
permit mode manually and to configure one of the physical interface fe1.2 to the passing mode without
manually keyword.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe1.1 mode permit manually
DUT-1(config)#ip dhcp-snoop fe1.2 mode passing
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
-------------------------------------------------------------------------
fe1.1 ENABLE Permit Permit * N/A / 1800 4 2 0 ON
fe1.2 ENABLE Permit Passing N/A / 1800 4 2 0 ON
fe1.3 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.4 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
(omitted)
fe3.4 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.6 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.7 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.8 ENABLE Permit Normal N/A / 1800 4 2 0 ON
ge1 DISABLE Permit Permit N/A / 1800 4 2 0 ON
ge2 DISABLE Permit Permit N/A / 1800 4 2 0 ON
DUT-1#
In the above example, the * mark means the DHCP snooping mode of the interface is configured
manually and the DHCP snooping mode will not transit to other mode automatically.
Beginning in Enable mode, follow these steps to configure the DHCP snooping initial mode of a
physical interface.
Command Description
Step 2 ip dhcp-snoop <ifname> init-mode { passing | Configure the DHCP snooping initial mode of a
This example shows how to the DHCP snooping initial mode of the physical interface fe1.1 and fe1.2
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe1.1 init-mode passing
DUT-1(config)#ip dhcp-snoop fe1.2 init-mode passing
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
---------------------------------------------------------------------------
fe1.1 ENABLE Passing Permit * N/A / 1800 4 2 0 ON
fe1.2 ENABLE Passing Passing N/A / 1800 4 2 0 ON
fe1.3 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.4 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe1.6 ENABLE Permit Normal N/A / 1800 4 2 0 ON
(omitted)
fe3.6 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.7 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.8 ENABLE Permit Normal N/A / 1800 4 2 0 ON
ge1 DISABLE Permit Permit N/A / 1800 4 2 0 ON
ge2 DISABLE Permit Permit N/A / 1800 4 2 0 ON
DUT-1#
Beginning in Enable mode, follow these steps to enable ARP snooping function of a physical interface.
Command Description
To disable ARP snooping function of a physical interface, use the no ip arp-snoop if-name command
in global configuration mode.
This example shows how to disable the ARP snooping function of the physical interface fe1.1 and
fe1.2.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#no ip arp-snoop fe1.1
DUT-1(config)#no ip arp-snoop fe1.2
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
---------------------------------------------------------------------------
fe1.1 ENABLE Passing Permit * N/A / 1800 4 2 0 OFF
fe1.2 ENABLE Passing Passing N/A / 1800 4 2 0 OFF
fe1.3 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.4 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
(omitted)
fe3.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.6 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.7 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.8 ENABLE Permit Normal N/A / 1800 4 2 0 ON
ge1 DISABLE Permit Permit N/A / 1800 4 2 0 ON
ge2 DISABLE Permit Permit N/A / 1800 4 2 0 ON
DUT-1#
When the DHCP snooping mode of a physical interface is the permit mode, the mode transition timer
is used for the DHCP snooping mode to remain in the permit mode during specified duration. By
default, the mode transition timer is 1800 seconds. If you change the value of the mode transition timer,
the timer will restart. If the DHCP snooping mode of a physical interface is not the permit mode, just
the value of the timer would be changed and the timer would not work.
Beginning in Enable mode, follow these steps to configure the value of mode transition timer.
Command Description
Step 2 ip dhcp-snoop <if-name> mode-transition-timer Set the mode transition timer of the specified
<timeout> physical interface.
For if-name, specify the physical interface to
configure the mode transition timer.
For timeout, specify the timeout value.
This example shows how to configure the mode transition timer of the physical interface fe2.4 of which
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe2.4 mode-transition-timer 5000
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
---------------------------------------------------------------------------
fe1.1 ENABLE Passing Permit * N/A / 1800 4 2 0 OFF
fe1.2 ENABLE Passing Passing N/A / 1800 4 2 0 OFF
(omitted)
fe2.3 ENABLE Permit Normal N/A / 1800 4 2 0 ON
This example shows how to configure the mode transition timer of the physical interface fe2.1 of which
the current DHCP snooping mode is the normal mode to 1000 seconds.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe2.1 mode-transition-timer 1000
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
--------------------------------------------------------------------------
fe1.1 ENABLE Passing Permit * N/A / 1800 4 2 0 OFF
fe1.2 ENABLE Passing Passing N/A / 1800 4 2 0 OFF
fe1.3 DISABLE Permit Permit N/A / 1800 4 2 0 ON
fe1.4 DISABLE Permit Permit N/A / 1800 4 2 0 ON
(omitted)
fe2.1 ENABLE Permit Normal N/A / 1000 4 2 0 ON
fe2.2 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe2.3 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe2.4 ENABLE Permit Normal N/A / 5000 4 2 0 ON
fe2.5 ENABLE Permit Normal N/A / 1800 4 2 0 ON
(omitted)
fe3.7 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe3.8 ENABLE Permit Normal N/A / 1800 4 2 0 ON
ge1 DISABLE Permit Permit N/A / 1800 4 2 0 ON
ge2 DISABLE Permit Permit N/A / 1800 4 2 0 ON
DUT-1#
When the current DHCP snooping mode of a physical interface is the permit mode, the mode
transition trigger is used for the DHCP snooping mode of the interface to be changed to the normal
mode after the specified DHCP lease entry is registered in the DHCP snooping lease entry table. The
mode transition trigger condition would work when the current DHCP snooping mode of the physical
Beginning in Enable mode, follow these steps to configure the mode transition trigger condition of a
physical interface.
Command Description
Step 2 ip dhcp-snoop <ifname> mode-transition-trigger Set the mode transition trigger condition of the
<trigger> specified physical interface.
For if-name, specify the physical interface to
configure the mode transition trigger condition.
For trigger, specify the count of the mode
transition trigger condition.
This example shows how to configure the mode transition trigger of the physical interface fe2.3 to 4.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe2.3 mode-transition-trigger 4
DUT-1(config)#end
DUT-1#show ip dhcp-snoop
DHCP Snooping Service : Enabled
Port Status InitMode CurMode TransTimer MaxLease Trg Trged ARPSnp
--------------------------------------------------------------------------
(omitted)
fe2.1 ENABLE Permit Normal N/A / 1000 4 2 0 ON
fe2.2 ENABLE Permit Normal N/A / 1800 4 2 0 ON
fe2.3 ENABLE Permit Normal N/A / 1800 4 4 0 ON
This example shows how to display the DHCP snooping lease entry.
The above example shows that client of which hardware address is 00:0E:DC:31:01:02 is assigned
the IP address 192.168.31.99 and the IP address would be expired after 81103 seconds in the
physical interface fe2.1. The last column means that the filter that is composed of the source IP
address and the source hardware address in the DHCP snooping lease entry work normally. In other
words, the packets of which the source IP address and the source hardware address are not match
with the addresses in the DHCP snooping lease entry would be discard. If the value of this field is ‘NO’,
the current DHCP snooping mode of the physical interface is not normal mode, and all of the packets
You can add a static DHCP snooping lease entry to a physical interface. If you add a static DHCP
snooping lease entry, it will remain in the existence after rebooting your system and it will not expire
the expiration timer because the static DHCP lease entry’s expiration timer do not work.
Beginning in Enable mode, follow these steps to add a static DHCP snooping lease entry.
Command Description
Step 2 ip dhcp-snoop <if-name> static-lease-entry Add the specified static DHCP snooping lease
A.B.C.D [XX:XX:XX:XX:XX:XX] entry to a physical interface.
For if-name, specify the physical interface to
add the new static DHCP snooping lease
entry.
For A.B.C.D, specify the IP address of adding
static DHCP snooping lease entry.
For XX:XX:XX:XX:XX:XX, specify the
hardware address of adding static DHCP
snooping lease entry. This is the optional.
When you add the DHCP snooping lease entry, you may not the hardware address of the static DHCP
snooping lease entry. It is the optional information. When you add a new static DHCP snooping lease
entry to a physical interface, If you don’t specify the hardware address of the static entry, the ARP
snooping function of the interface would not work as though the ARP snooping of the interface is
enable.
This example shows how to add the static DHCP snooping lease entry of which the IP address is
192.168.31.253 to the physical interface fe2.2. And it also shows how to add the static DHCP snooping
lease entry of which the IP address is 192.168.31.252 and the hardware address is
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip dhcp-snoop fe2.2 static-lease-entry 192.168.31.253
DUT-1(config)#ip dhcp-snoop fe2.2 static-lease-entry 192.168.31.252
00:0E:DC:31:01:99
DUT-1(config)#end
DUT-1#show ip dhcp-snoop lease-entry
IP Address MAC Address Mode Port ExpLeft Filter
--------------------------------------------------------------------
192.168.31.99 00:0E:DC:31:01:02 DYNAMIC fe2.1 81023 YES
192.168.31.252 00:0E:DC:31:01:99 Static fe2.2 N/A YES
192.168.31.253 00:00:00:00:00:00 Static fe2.2 N/A YES
DUT-1#
To remove the DHCP snooping lease entry of a physical interface, use the following command in the
Command Description
Step 1 clear ip dhcp-snoop lease-entry <ifname> Delete the specified DHCP snooping lease
A.B.C.D [XX:XX:XX:XX:XX:XX] entry.
For if-name, specify the physical interface to
delete the DHCP snooping lease entry.
For A.B.C.D, specify the IP address of deleting
DHCP snooping lease entry.
For XX:XX:XX:XX:XX:XX, specify the
hardware address of deleting DHCP snooping
lease entry. This is the optional.
This example shows how to delete the DHCP snooping lease entry of which IP address is
192.168.31.252 and the hardware address is 00:0E:DC:31:01:99 on the physical interface fe2.2.
The Chapter 10 describes how to use CLI commands to configure IGMP snooping and IGMP proxy
In general, the L2 switch, when multicast traffic is processed as unknown MAC address or broadcast
frame, result in the flooding of multicast traffic to all ports in that VLAN. In order to manage effectively
unnecessary resources of the switch built in the DSLAM VX-MD3024, the switch can use IGMP
IGMP snooping can be used to constrain the flooding of multicast traffic to all ports in that VLAN by
configuring the built-in L2 interfaces so that multicast traffic is switched to only those interfaces
IGMP snooping requires the built-in switch to snoop on the IGMP transmissions between the ports and
the router and to keep track of multicast groups and member ports. When the switch receives an IGMP
Report message from a port for a particular multicast group, the switch adds the port number to the
forwarding table entry; when it receives an IGMP Leave Group message from a port, it removes the
port from the table entry. It also periodically deletes entries if it does not receive IGMP membership
their content. To enable IGMP snooping on the system to discover external multicast routers, the
Layer 3 interfaces on the routers in the VLAN must already have been for configured for multicast
routing.
You can globally enable or disable IGMP snooping. When globally enabled or disabled, it is also
enabled or disabled in all existing VLAN interfaces. IGMP snooping can be enabled and disabled on a
per-VLAN basis. When IGMP snooping is globally enabled or disabled, the system can execute IGMP
snooping.
Global IGMP snooping overrides the VLAN IGMP snooping. If global snooping is disabled, you cannot
enable VLAN snooping. If global snooping is enabled, you can enable or disable VLAN snooping.
Beginning in Enable mode, follow these steps to globally enable IGMP snooping.
Command Description
Step 2 ip igmp snooping Globally enable IGMP snooping in all existing VLAN
interfaces.
This example shows how to enable and verify globally IGMP snooping when all existing VLAN, VLAN
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping
DUT-1(config)#end
DUT-1#show ip igmp snooping
IGMP Snooping is globally enabled
IGMP Snooping Proxy is disabled
Bridge 1: VLAN 1
IGMP Snooping enabled
IGMP Snooping Robustness-value is 2
IGMP snooping query interval is 125000 ms
IGMP snooping Startup query interval is 31250 ms
IGMP snooping max query response time is 100 cs
IGMP Snooping last member query interval is 1000 ms
IGMP Snooping last member query count is 2
IGMP snooping other querier timeout interval is 255000 ms
IGMP snooping group membership interval is 260000 ms
IGMP snooping v1 router present timeout is 400000 ms
IGMP snooping interface fe1.1 version 2
IGMP snooping interface fe1.2 version 2
IGMP snooping interface fe1.3 version 2
IGMP snooping interface fe1.4 version 2
(output truncated)
Bridge 1: VLAN 2
IGMP Snooping enabled
IGMP Snooping Robustness-value is 2
IGMP snooping query interval is 125000 ms
(output truncated)
DUT-1#
Beginning in Enable mode, follow these steps to configure IGMP snooping on a VLAN interface, in
Command Description
Step 2 ip igmp snooping vlan (default | <2- Enable IGMP Snooping on the VLAN interface
4094>) bridge <1-32>
This example shows how to enable and verify IGMP snooping on the VLAN interface.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping vlan default bridge 1
DUT-1(config)#ip igmp snooping vlan 2 bridge 1
DUT-1(config)#end
DUT-1#show ip igmp snooping vlan default bridge 1
IGMP Snooping is globally enabled
IGMP Snooping Proxy is disabled
Bridge 1: VLAN 1
IGMP Snooping enabled
IGMP Snooping Robustness-value is 2
IGMP snooping query interval is 125000 ms
IGMP snooping Startup query interval is 31250 ms
IGMP snooping max query response time is 100 cs
IGMP Snooping last member query interval is 1000 ms
IGMP Snooping last member query count is 2
IGMP snooping other querier timeout interval is 255000 ms
IGMP snooping group membership interval is 260000 ms
IGMP snooping v1 router present timeout is 400000 ms
IGMP snooping interface fe1.1 version 2
IGMP snooping interface fe1.2 version 2
IGMP snooping interface fe1.3 version 2
IGMP snooping interface fe1.4 version 2
()
DUT-1#
If the built-in switch connects with a multicast router on the VLAN IGMP snooping is enabled, IGMP
Report and Leave messages must be forwarded to the multicast router on the VLAN. The port
connected to the multicast router is named the multicast router port or mrouter port.
Multicast router port or mrouter port can be configured automatically or manually. The learn’t mrouter
is configured automatically when the system receives IGMP Query message. The configured mrouter
Beginning in Enable mode, follow these steps to configure IGMP snooping Mrouter port.
Command Description
Step 2 ip igmp snooping mrouter interface if- Specify the Layer 2 interface to the IGMP Snooping
name mrouter
This example shows how to specify the ge1 port on the VLAN1.1 to mrouter port and verify the
mrouter ports on the system. In this example, you can show the learn’t mrouter that is configured by
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping mrouter interface ge1
DUT-1(config)#end
DUT-1#show ip igmp snooping mrouter
Bridge 1:
VLAN: 1 Igmp Snooping Enabled
The IGMP querier transmits IGMP general query messages and IGMP group specific messages. It
sends the IGMP general query message on the constant interval (IGMP query interval) and sends
IGMP group specific query message when it removes multicast group by receiving IGMP leave
message on that multicast group. When the IGMP querier receives IGMP query message from the
multicast router in the VLAN, the IGMP querier function is disabled the constant period (other querier
timer) on the VLAN. If the IGMP querier is disabled, it uses only the IGMP query message from the
router’s IGMP query messages. This is named querier selection function. Therefore there is only one
Beginning in Enable mode, follow these steps to configure IGMP snooping querier in the VLAN.
Command Description
Step 2 ip igmp snooping querier vlan (default | Enable IGMP snooping querier in the VLAN
<2-4094>) bridge <1-32>
Step 4 show ip igmp snooping querier Verify that the IGMP snooping querier is enabled on the
VLAN interface.
This example shows how to configure and verify IGMP snooping querier in the VLAN1.1 and VLAN1.3.
The case of VLAN1.3 is an example enabling other querier on receiving IGMP query message from
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping querier vlan default bridge 1
DUT-1(config)#ip igmp snooping querier vlan 3 bridge 1
DUT-1(config)#end
DUT-1#show ip igmp snooping querier
Bridge 1 : VLAN 1
IGMP Snooping querier is enabled
Bridge 1 : VLAN 2
IGMP Snooping querier is disabled
Bridge 1 : VLAN 3
IGMP Snooping other-querier enabled
DUT-1#
When the IGMP snooping receives IGMP leave message, it acts IGMP leave process after waiting for
the constant interval (Last Member Query Interval * Last Member Query Count). If you want to process
IGMP leave procedure without waiting the constant interval, you must configure IGMP snooping fast-
leave.
The reason using IGMP snooping fast leave is to prevent a loss of bandwidth when the change of
IGMP group occurs frequently (eg. Channel Zapping). When the downstream port is stacked in fast
leave configuration and two or more hosts are joined in that port, IGMP leave of a host can result in
multicast service disruption problem. For resolving this problem, VX-MD3024 manages per-port and
You can configure IGMP snooping fast-leave in per-VLAN and per-port. The per-VLAN configuration is
To configure the IGMP snooping fast-leave, follow these steps in Enable mode.
Command Description
Step 2 Ip igmp snooping fast-leave vlan Enable IGMP Snooping Fast-Leave for the VLAN
(default|<2-4094>) bridge <1-32>
Step 4 ip igmp snooping fast-leave Enable IGMP Snooping Fast-Leave for the Layer 2
interface
Step 6 show ip igmp snooping fast-leave Display the configured IGMP Snooping Fast-Leave
This example shows how to configure the IGMP snooping fast-leave on VLAN1.1 and VLAN1.2 and
release the IGMP snooping fast-leave for fe2.1 and fe2.2 on the VLAN1.2.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping fast-leave vlan default bridge 1
DUT-1(config)#ip igmp snooping fast-leave vlan 2 bridge 1
DUT-1(config)#interface fe2.1
DUT-1(config-if)#no ip igmp snooping fast-leave
DUT-1(config-if)#exit
DUT-1(config)#interface fe2.2
DUT-1(config-if)#no ip igmp snooping fast-leave
DUT-1(config-if)#end
DUT-1#show ip igmp snooping fast-leave
Bridge 1 : VLAN 1
IGMP Snooping fast-leave is enabled
fe1.1 enabled
fe1.2 enabled
fe1.3 enabled
fe1.4 enabled
(output truncated)
ge1 enabled
Bridge 1 : VLAN 2
IGMP Snooping fast-leave is enabled
fe2.1 disabled
fe2.2 disabled
fe2.3 enabled
fe2.4 enabled
fe2.5 enabled
fe2.6 enabled
(output truncated)
DUT-1#
The IGMP snooping process uses the following parameters for setting the timer value.
When the switch receives the IGMP leave message (not in fast-leave state), it removes a port from the
IGMP snooping group. At that time, the IGMP snooping leave timeout value is determined by the last
member query interval and the last member query count. This shows how to calculate the IGMP
snooping leave timeout, and default and range of last member query interval and last member query
count.
Beginning in Enable mode, follow these steps how to configure the last member query interval value.
Command Description
Step 2 ip igmp snooping last-member-query- Configure the Last Member Query Interval in the VLAN.
interval <1000-25500> vlan (default|<2-
4094>) bridge <1-32>
This example shows how to configure the last member query interval; 2000msec in the VLAN1.1 and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping last-member-query-interval 2000 vlan default
bridge 1
DUT-1(config)#ip igmp snooping last-member-query-interval 4000 vlan 3
bridge 1
DUT-1(config)#end
DUT-1#show ip igmp snooping last-member-query-interval
Bridge 1 : VLAN 1
IGMP Snooping last-member-query-interval is 2000 ms
Bridge 1 : VLAN 2
IGMP Snooping last-member-query-interval is 1000 ms
Bridge 1 : VLAN 3
IGMP Snooping last-member-query-interval is 4000 ms
DUT-1#
Beginning in Enable mode, follow these steps how to configure the last member query count.
Command Description
Step 2 ip igmp snooping last-member-query- Configure the Last Member Query Count in the VLAN
count <2-7> vlan (default|<2-4094>)
bridge <1-32>
This example shows how to configure the last member query count 4 in the VLAN1.1 and 5 in the
VLAN1.3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping last-member-query-count 4 vlan default
bridge 1
DUT-1(config)#ip igmp snooping last-member-query-count 5 vlan 3 bridge 1
DUT-1(config)#end
DUT-1#show ip igmp snooping last-member-query-count
Bridge 1 : VLAN 1
IGMP Snooping last-member-query-count is 4
Bridge 1 : VLAN 2
IGMP Snooping last-member-query-count is 2
Bridge 1 : VLAN 3
IGMP Snooping last-member-query-count is 5
DUT-1#
The robustness variable in the IGMP snooping enable mode affects the startup query interval, other
querier interval and group membership interval. The startup query interval means the switch sends the
IGMP general query message on a quarter of query interval cycle when starting the IGMP querier of
the VLAN, and the group membership interval means the effective time of the group when generating
This shows how to determine the startup query interval, other querier interval and group membership
interval.
Beginning in Enable mode, follow these steps how to configure the robustness variable.
Command Description
Step 2 ip igmp snooping robustness-value <2-7> Configure Robustness Variable in the VLAN
This example shows the value of robustness variable as 3 in the VLAN1.1 and 4 in the VLAN1.3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping robustness-value 3 vlan default bridge 1
DUT-1(config)#ip igmp snooping robustness-value 4 vlan 3 bridge 1
DUT-1(config)#end
DUT-1#show ip igmp snooping
IGMP Snooping is globally enabled
IGMP Snooping Proxy is disabled
Bridge 1: VLAN 1
IGMP Snooping enabled
IGMP Snooping Robustness-value is 3
IGMP Snooping querier enabled
IGMP snooping query interval is 125000 ms
IGMP snooping Startup query interval is 31250 ms
IGMP snooping max query response time is 1000 cs
IGMP Snooping last member query interval is 2000 ms
IGMP Snooping last member query count is 4
IGMP snooping other querier timeout interval is 380000 ms
IGMP snooping group membership interval is 385000 ms
IGMP snooping v1 router present timeout is 400000 ms
IGMP snooping interface fe1.1 version 2
IGMP snooping interface fe1.2 version 2
IGMP snooping interface fe1.3 version 2
IGMP snooping interface fe1.4 version 2
(output truncated)
Bridge 1: VLAN 3
IGMP Snooping enabled
IGMP Snooping Robustness-value is 4
IGMP Snooping other-querier enabled
IGMP snooping query interval is 125000 ms
IGMP snooping Startup query interval is 31250 ms
IGMP snooping max query response time is 1000 cs
IGMP Snooping last member query interval is 4000 ms
IGMP Snooping last member query count is 5
IGMP snooping other querier timeout interval is 505000 ms
The other querier interval means the time stopping the IGMP querier in the VLAN when receiving the
IGMP general query from the multicast router. The other querier interval is affected by the robustness
variable, query interval and query max-response timeout, and can be configured directly by setting the
value.
This shows how to determine the other querier interval. The default, minimum and maximum values
are as follows.
Beginning in Enable mode, follow these steps how to configure the other querier interval.
Command Description
Step 2 ip igmp snooping other-querier-interval Configure Other Querier Interval in the VLAN
<60000-300000> vlan (default|<2-4094>)
bridge <1-32>
This shows how to configure the other querier interval 120000msec in the VLAN1.1 and 150000msec
in the VLAN1.3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping other-querier-interval 120000 vlan default
bridge 1
DUT-1(config)#ip igmp snooping other-querier-interval 150000 vlan 3 bridge
1
DUT-1(config)#end
DUT-1#show ip igmp snooping other-querier-interval
Bridge 1 : VLAN 1
IGMP Snooping other-querier-interval is 120000 ms
Bridge 1 : VLAN 2
IGMP Snooping other-querier-interval is 255000 ms
Bridge 1 : VLAN 3
IGMP Snooping other-querier-interval is 150000 ms
DUT-1#
The query interval means the cycle sending the IGMP general query in the VLAN on which the querier
is configured.
This shows the default, minimum and maximum values of query interval.
Beginning in Enable mode, follow these steps how to configure the query interval value.
Command Description
Step 2 ip igmp snooping query-interval <1000- Configure Query Interval value in the VLAN
180000000> vlan (default|<2-4094>)
bridge <1-32>
This shows how to configure the query interval in the VLAN; 60000msec in the VLAN1.1 and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping query-interval 60000 vlan default bridge 1
DUT-1(config)#ip igmp snooping query-interval 250000 vlan 3 bridge 1
DUT-1(config)#end
DUT-1#
The query max response time means the effective time of the query sent by the querier. For that query,
only IGMP report message sent in the query max response time which is used for index of the other
This shows the default, minimum and maximum values of query max response time.
Beginning Enable mode, follow these steps how to configure the query max response time value.
Command Description
Step 2 ip igmp snooping query-max-response- Configure Query Max Response Time in the VLAN.
time <100-24000> vlan (default|<2-
4094>) bridge <1-32>
This example shows how to the query max response time 100csec in the VLAN1.1 and 2000csec in
the VLAN1.3.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping max-response-time 100 vlan default bridge 1
DUT-1(config)#ip igmp snooping max-response-time 2000 vlan 3 bridge 1
DUT-1(config)#end
DUT-1#
Command Description
Step 2 show ip igmp snooping mrouter Display Mrouter information of IGMP Snooping
This example shows how to display the IGMP snooping global information and IGMP snooping
Mrouter information.
Command Description
Step 1 show ip igmp snooping groups Display the IGMP Snooping group
Command Description
Step 1 show ip igmpV2 snooping statistics Display the statistics information of IGMP Snooping
DUT-1#
messages. The IGMP proxy enables Mrouter port to acts the IGMP report process, not forward the
IGMP query message to ports in the VLAN when the switch receives the IGMP query from Mrouter.
This IGMP report names the IGMP proxy report. The switch sends the IGMP query message to hosts
using its querier in that VLAN, and sends the IGMP report/leave message to Mrouter only when
generating or removing new group.
VX-MD3024 uses the IGMP snooping proxy for reducing unnecessary IGMP related processes in
upstream router. When using the IGMP proxy, the IP address must be assigned in the VLAN.
VX-MD3024 supports proxy report, report/leave suppression functions for the IGMP snooping proxy.
mode, follow these steps for configuring the IGMP snooping proxy.
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp snooping proxy
DUT-1(config)#end
DUT-1#show ip igmp snooping
IGMP Snooping is globally enabled
IGMP Snooping Proxy is enabled
Bridge 1: VLAN 1
IGMP Snooping enabled
IGMP Snooping Robustness-value is 3
IGMP Snooping querier enabled
IGMP Snooping fast-leave is enabled
IGMP snooping query interval is 60000 ms
IGMP snooping Startup query interval is 15000 ms
IGMP snooping max query response time is 100 cs
IGMP Snooping last member query interval is 2000 ms
IGMP Snooping last member query count is 4
IGMP snooping other querier timeout interval is 120000 ms
IGMP snooping group membership interval is 181000 ms
IGMP snooping v1 router present timeout is 400000 ms
IGMP snooping interface fe1.1 version 2
IGMP snooping interface fe1.2 version 2
IGMP snooping interface fe1.3 version 2
IGMP snooping interface fe1.4 version 2
IGMP snooping interface fe1.5 version 2
IGMP snooping interface fe1.6 version 2
(output truncated)
Bridge 1: VLAN 2
IGMP Snooping enabled
IGMP Snooping Robustness-value is 2
(output truncated)
IGMP Version 1
224.3.3.3
Unsolicited report
IGMPv1
IGMP Non-querier
Querier
Router 1 Router 2
IGMP Version 2
9 –
9 –
9 –
9 –
224.1.1.1 224.1.1.1
Host 1 Host 2 Host 3
3. IGMPv2
1.Leave-group
membership
message sent
report for
to 224.0.0.2
224.1.1.1
2. Send gorup-specific
query to 224.1.1.1
Router
IGMPv2
Querier
Command Description
Step 3 interface if-name Specify the Layer 3 interface on which you want to
enable multicast routing, and enter interface
configuration mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip multicast-routing
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip multicast-routing
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip multicast-routing
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.3
DUT-1(config-if)#ip multicast-routing
DUT-1(config-if)#exit
DUT-1(config)#end
DUT-1#show ip igmp interface
Interface vlan1.1
IGMP Active, Querier, Default version 2
Internet address is 1.1.1.254
IGMP query interval is 125 seconds
IGMP Startup query interval is 31 seconds
IGMP querier timeout is 255 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 milliseconds
Group Membership interval is 260 seconds
Unsolicited Report interval is 10 seconds
Robustness Variable is 2
(omitted)
DUT-1#
Command Description
Step 2 interface if-name Specify the Layer 3 interface on which you want to
enable IGMP mrouter, and enter interface configuration
mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.3
DUT-1(config-if)#ip igmp mrouter
DUT-1(config-if)#end
DUT-1#show ip igmp upstream-interface
IGMP Upstream-Interface
Inteface vlan1.3.
DUT-1#show ip igmp downstream-interface
IGMP Downstream-Interfaces
Interface vlan1.1
Interface vlan1.2
DUT-1#
Command Description
Step 2 interface if-name Specify the L3 interface on which you want to configure
the IGMP fast-leave and enter interface configuration
mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp fast-leave
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.3
DUT-1(config-if)#ip igmp fast-leave
DUT-1(config-if)#end
DUT-1#show ip igmp interface
Interface vlan1.1
IGMP Enabled, Active, Querier, Configured for version 2
Internet address is 1.1.1.254
IGMP query interval is 125 seconds
IGMP Startup query interval is 31 seconds
IGMP querier timeout is 255 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 milliseconds
IGMP fast-leave enabled
Group Membership interval is 260 seconds
Unsolicited Report interval is 10 seconds
Robustness Variable is 2
(omitted)
DUT-1#
Command Description
Step 2 interface if-name Specify the L3 interface on which you want to configure
IGMP last member query interface and enter interface
configuration mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp last-member-query-interval 2000
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip igmp last-member-query-interval 4000
DUT-1(config-if)#exit
DUT-1(config)#end
DUT-1#
Command Description
Step 2 interface if-name Specify the L3 interface on which you want to configure
IGMP last-member-query-count and enter interface
configuration mode
Step 3 ip igmp last-member-query-count <2-7> Configure IGMP last member query count
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp last-member-query-count 4
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip igmp last-member-query-count 5
DUT-1(config-if)#end
command purpose
Step 2 interface if-name Specify the L3 interface on which you want to configure
IGMP last-member-query-count and enter interface
configuration mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp robustness-variable 3
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
Command Description
Step 2 interface if-name Specify the L3 interface to ne configured and enter the
interface configuration mode
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp querier-timeout 120
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip igmp querier-timeout 150
DUT-1(config-if)#end
DUT-1#
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp query-interval 60
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip igmp query-interval 250
DUT-1(config-if)#exit
DUT-1(config)#end
DUT-1#
Command Description
Step 3 ip igmp query-max-response-time <1- Configure IGMP query max response time.
240>
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface vlan1.1
DUT-1(config-if)#ip igmp query-max-response-time 1
DUT-1(config-if)#exit
DUT-1(config)#interface vlan1.2
DUT-1(config-if)#ip igmp query-max-response-time 20
DUT-1(config-if)#end
Command Description
Step 2 show ip igmp upstream-interface Display IGMP upstream (mrouter) interface information
Command Description
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip igmp proxy
DUT-1(config)#end
DUT-1#show ip igmp proxy
IGMP Proxy is Enabled.
DUT-1#
Applying ACL
Caution You cannot apply more than one IP access list and one MAC access list to a Layer 2 interface. If an
IP access list or MAC access list is already configured on a Layer 2 interface and you apply a new IP
access list or MAC access list to the interface, the new ACL replaces the previously configured one.
Creating IP ACL
Command Description
Step 2a ip access-list access-list-name Define an IP access list and the access conditions.
{deny | permit} protocol The access-list-name is a alphanumeric string.
source source-wildcard
Enter deny or permit to specify whether to deny or to permit the
destination destination-wildcard
packet if conditions are matched.
[{precedence precedence | tos tos
| dscp dscp | cos cos}] For protocol, enter the name or number of an IP protocol: icmp,
igmp, udp, tcp or ip or an integer in the range 0 to 255
representing an IP protocol number. To match any Internet
Command Description
protocol (including ICMP, TCP and UDP) use the keyword ip.
The source is the number of the network or host from which the
packet is sent.
The source-wildcard applies wildcard bits to the source.
The destination is the network or host number to which the
packet is sent.
The destination-wildcard applies wildcard bits to the destination.
Source, source-wildcard, destination, destination-wildcard can be
specified as:
The 32 bit quantity in dotted-decimal format.
The keyword any for 0.0.0.0 255.255.255.255 (any host).
The keyword host for a single host 0.0.0.0.
The other keywords are optional and have these meanings.
precedence: Enter to match packets with a precedence level
specified as a number from 0 to 7.
tos: Enter to match by type of service level, specified by a
number from 0 to 15.
cos: Enter to match packets with the CoS Value specified by a
number from 0 to 7.
dscp: Enter to match packets with the DSCP value specified by
a number from 0 to 63.
or ip access-list access-list-name Define an IP access list using an abbreviation for a source and
{deny | permit} protocol source wildcard of source 0.0.0.0 and an abbreviation for a
host source host destination destination and destination wildcard of destination 0.0.0.0.
[{precedence precedence | tos tos You can use the host keyword in place of source and destination
| dscp dscp | cos cos}] wildcard or mask.
Step 2b ip access-list access-list-name You can enter tcp or udp in the protocol field to create TCP
{deny | permit} {tcp | udp } [ihl access list and UDP access list.
Command Description
header-length] source source- The parameters are the same as those described in Step 2a with
wildcard [eq port] destination these exceptions:
destination-wildcard [eq port] (Optional) Enter ihl header-length to specify the length of the IP
[{precedence precedence | tos tos Header.
| dscp dscp | cos cos}]
(Optional) Enter eq port to compare source (if positioned after
source source-wildcard) or destination (if positioned after
destination destination-wildcard) port.
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip access-list telnet_filter deny tcp 171.69.198.0 0.0.0.255
172.20.52.0 0.0.0.255 eq telnet
DUT-1(config)#ip access-list telnet_filter permit tcp any any
DUT-1(config)#end
DUT-1#show ip access-list
VERSA IP access list telnet_filter
deny tcp 171.69.198.0 0.0.0.255 172.20.52.0 0.0.0.255 eq 23
permit tcp any any
DUT-1#
Command Description
Step 2 interface interface-id Identify a specific interface for configuration, and enter interface
configuration mode.
Step 3 ip access-group access-list-name Control access to the specified interface by using the IP access
in list.
Step 6 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#ip access-group telnet_filter in
DUT-1(config-if)#end
DUT-1#show running-config interface fe1.1
!
interface fe1.1
switchport
bridge-group 1
switchport mode access
ip access-group telnet_filter in
!
DUT-1#
Command Description
Step 2 mac access-list access-list-name Define an MAC access list and the access conditions.
{permit | deny} {any | host source The access-list-name specifies the name of MAC access list.
MAC address | source MAC
Enter deny or permit to specify whether to deny or to permit the
address mask } {any | host
packet if conditions are matched.
destination MAC address |
destination MAC address mask } Specify any source MAC address, source MAC address with a
[ethertype] [cos cos] mask or a specific host source MAC address and any
destination MAC address, destination MAC address with a mask,
or a specific destination MAC address.
(Optional) You can also enter these options:
- ethertype: An arbitrary EtherType number of a packet with
Ethernet II or SNAP encapsulation in hex.
- cos cos: An IEEE 802.1Q cost of service number from 0 to
7 used to set priority.
Command Description
Step 5 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#mac access-list mac_filter permit any any 0x0806
DUT-1(config)#end
DUT-1#show mac access-list
VERSA MAC access list mac_filter
permit any any 0x0806
DUT-1#
Step 2 interface interface-id Identify a specific interface for configuration, and enter interface
configuration mode.
Step 3 mac access-group access-list- Control access to the specified interface by using the MAC
name in access list.
Step 6 write memory (Optional) Save your entries in the configuration file.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#interface fe1.1
DUT-1(config-if)#mac access-group mac_filter in
DUT-1(config-if)#end
DUT-1#show running-config interface fe1.1
!
interface fe1.1
switchport
bridge-group 1
switchport mode access
mac access-group mac_filter in
ip access-group telnet_filter in
!
DUT-1#
This chapter describes how to configure quality of service (QoS) by using standard QoS command.
priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic
When you configure QoS, you can select specific network traffic, prioritize it according to its relative
preferential treatment. Implementing QoS in your network makes network performance more
The QoS mechanism specifies that each packet is classified upon entry into the network. The
classification is carried in the IP packet header, using 6 bits from the deprecated IP type of service
(TOS) field to carry the classification (class) information. Classification can also be carried in the Layer
2 frame. These special bits in the Layer 2 frame or in the Layer 3 packet are described here.
9
−
9
−
−
−
D T R C Class Selector
To provide the same forwarding treatment to packets with the same class information and different
treatment to packets with different class information, all switches and routers that access the Internet
rely on class information. Class information in the packet can be assigned by end hosts or by switches
or routers along the way, based on a configured policy, detailed examination of the packet, or both.
Detailed examination of the packet is expected to happen closer to the network edge so that core
Switches and routers along the path can use class information to limit the amount of resources
allocated per traffic class. The behavior of an individual device when handling traffic in the DiffServ
architecture is called per-hop behavior. If all devices along a path provide a consistent per-hop
The following figure shows the basic QoS model. Actions at the ingress interface include classifying
Actions at ingress
Packet Packet
In out
Buffer Queue
Policer Marker
Classifier Manager Scheduler
Traffic Manager
Actions at egress
criteria for classifying traffic into several classes. A policy map consists of classes which have actions
Class Maps
You can use IP ACL and MAC ACLs to define a group of packets with the same characteristics (class).
In the QoS context, the permit and deny actions in the access control entries (ACEs) have different
A class map is a mechanism that you use to name and to isolate a specific traffic flow (or class) from
all other traffic. The class map defines the criteria used to match against a specific traffic flow to further
classify it. The criteria can include matching the access group defined by ACL, matching a specific list
of DSCP or IP precedence values, or matching a specific list of VLAN IDs. If you have more than one
type of traffic that you want to classify, you can create another class map and use a different name.
After a packet is matched against the class-map criteria, you further classify it through the use of a
policy map.
Policy Maps
After a traffic class has been defined with the ACL, you can attach a policy to it. A policy might contain
A policy map specifies which traffic class to act on. Actions can include trusting the CoS, DSCP, or IP
precedence values in the traffic class; setting a specific DSCP or IP precedence value in the traffic
class; or specifying the traffic bandwidth limitations and the action to take when the traffic is out of
profile.
The following table shows the default QoS configuration when QoS is disabled.
Default CoS -
Queuing -
The following table shows the default QoS configuration when QoS is enabled.
Before beginning the QoS configuration, you should be aware of this information:
−
−
By default, QoS is disabled on the system, which means that the system offers best-effort service to
each packet regardless of the packet contents or size. All CoS values map to egress queue 1 with tail-
Command Description
Step 5 write memory (Optional) Save your entries in the configuration file.
After QoS is enabled, the default settings are as shown in “Default QoS Configuration” section.
To disable QoS, use the no service qos command in global configuration mode.
Configuring a QoS policy typically requires classifying traffic into classes, configuring policies applied
9
9
9
You can classify IP traffic by using IP ACLs; you can classify non-IP traffic by using Layer 2 MAC
ACLs.
Beginning in Enable mode, follow these steps to create an IP ACL for IP traffic
Command Description
Step 3 ip access-list access-list-name Define an IP access list and the access conditions.
{deny | permit} protocol The access-list-name is a alphanumeric string.
source source-wildcard
Enter deny or permit to specify whether to deny or to permit the
destination destination-wildcard
packet if conditions are matched.
[{precedence precedence | tos tos
| dscp dscp | cos cos}] For protocol, enter the name or number of an IP protocol: icmp,
igmp, udp, tcp or ip or an integer in the range 0 to 255
representing an IP protocol number. To match any Internet
protocol (including ICMP, TCP and UDP) use the keyword ip.
The source is the number of the network or host from which the
packet is sent
The source-wildcard applies wildcard bits to the source.
The destination is the network or host number to which the
packet is sent.
The destination-wildcard applies wildcard bits to the destination.
Source, source-wildcard, destination, destination-wildcard can be
specified as:
The 32 bit quantity in dotted-decimal format.
The keyword any for 0.0.0.0 255.255.255.255 (any host).
The keyword host for a single host 0.0.0.0.
The other keywords are optional and have these meanings.
precedence: Enter to match packets with a precedence level
specified as a number from 0 to 7.
tos: Enter to match by type of service level, specified by a
number from 0 to 15.
cos: Enter to match packets with the CoS Value specified by a
number from 0 to 7.
dscp: Enter to match packets with the DSCP value specified by
Command Description
Step 6 write memory (Optional) Save your entries in the configuration file.
To delete an access list, use the no access-list access-list-name command in global configuration
mode.
This example shows how to create IP ACL that permits IP traffic with a DSCP value set to 32 from any
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip access-list dscp_filter permit ip any any dscp 32
DUT-1(config)#end
DUT-1#
This example shows how to create an ACL that permit IP traffic with a precedence value 5 from a
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip access-list prec_filter permit ip host 10.1.1.1 host
10.1.1.2 precedence 5
DUT-1(config)#end
DUT-1#
You use the class map global configuration command to name and to isolate a specific traffic flow (or
class) from all other traffic. The class map defines the criteria to use to match against a specific traffic
flow to further classify it. Match statements can include criterion such as an ACL, IP precedence
values, or DSCP values. The match criterion is defined with one match statement entered within the
Beginning in Enable mode, follow these steps to create a class map and to define the match criterion
Command Description
Step 3 ip access-list access-list-name Create an IP ACL for IP traffic or a Layer 2 MAC ACL for non-IP
{deny | permit} protocol traffic, repeating the commands as many times as necessary.
source source-wildcard For more detail information, see the Chapter 12, “Configuring
destination destination-wildcard Filter by Using ACL”
or Note When creating an access list, remember that, by default,
mac access-list access-list-name the end of the access list contains an implicit deny statement for
{permit | deny} source MAC everything if it did not find a match before reaching the end.
address mask destination MAC
address mask [ethertype] [cos cos]
Step 4 class-map class-map-name Create a class map, and enter class-map configuration mode.
By default, no class maps are defined.
For class-map-name, specify the name of the class map.
Step 5 match {access-group acl-name | Define the match criterion to classify traffic.
ip dscp dscp-list | ip precedence By default, no match criterion is defined.
ip-precedence-list}
Only one match criterion per class map is supported, and only
one ACL per class map is supported.
- For access-group acl-name, specify the name of the ACL
created in Step 3
- For ip dscp dscp-list, enter a list of up to 4 IP DSCP values
to match against incoming packets. Separate each value
with a space. The range is 0 to 63.
- For ip precedence ip-precedence-list, enter a list of up to 4
Command Description
Step 8 write memory (Optional) Save your entries in the configuration file.
To delete an existing class map, use the no class-map class-map-name command in global
configuration mode. To remove a match criterion, use the no match {access-group acl-name | ip
This example shows how to configure the class map called class1. The class1 has one match criterion,
whose name is test_a . It permits traffic that matches a DSCP value of 10 from any host to any
destination.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip access-list test_acl permit ip any any dscp 10
DUT-1(config)#class-map class1
new class-map(class1) created
DUT-1(config-class-map)#match ip access-group test_acl
DUT-1(config-class-map)#end
DUT-1#
A Policy Map specifies which traffic class to act on. Actions can include trusting the CoS, DSCP, or IP
precedence values in the traffic class; setting a specific DSCP or IP precedence value in the traffic
class; and specifying the traffic bandwidth limitations for each matched traffic class (policer) and the
Only one policy map per interface per direction is supported. You can apply the same policy map to
Command Description
Step 3 ip access-list access-list-name Create an IP ACL for IP traffic or a Layer 2 MAC ACL for non-IP
{deny | permit} protocol traffic, repeating the commands as many times as necessary.
source source-wildcard For more detail information, see the Chapter 12, “Configuring
destination destination-wildcard Filter by Using ACL”
or Note When creating an access list, remember that, by default,
mac access-list access-list-name the end of the access list contains an implicit deny statement for
{permit | deny} source MAC everything if it did not find a match before reaching the end
address mask destination MAC
address mask [ethertype] [cos cos]
Step 4 class-map class-map-name Create a class map to classify traffic as necessary. For more
information, see “Classifying Traffic by Using Class Map”.
Step 5 policy-map policy-map-name Create a policy map by entering the policy map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 6 class class-map-name Define a traffic classification, and enter policy-map class
configuration mdoe.
By default, no policy map class-maps are defined.
If a traffic class has already been defined by using the class-
map global configuration mode, specify its name for class-map-
name in this command.
Step 7 trust {cos | ip-precedence} Configure the trust state, which selects the value that QoS uses
as the source of the internal priority value.
This command is mutually exclusive with the set command
within the same policy map. If you enter the trust command,
then skip Step 7.
The keywords have these meanings:
- cos: QoS derives the internal priority value by using the
received or default port CoS value.
- ip-precedence: QoS derives the internal priority value by
using the IP precedence value from the ingress packet
Step 8 set {drop-precedence | cos new- Classify IP traffic by setting a new value in the packet.
cos | ip dscp new-dscp | ip - drop-precedence: Enable drop-precedence function.
Command Description
precedence new-precedence} - For cos new-cos: Enter a new CoS value to be assigned to
the classified traffic. The range is 0 to 7.
- For ip dscp new-dscp: Enter a new DSCP value to be
assigned to the classified traffic. The range is 0 to 63.
- For ip precedence new-precedence: enter a new IP-
precedence value to be assigned to the classified traffic. The
range is 0 to 7.
Step 9 police rate-kbps burst-kbits Define a policer for the classified traffic.
exceed-action {drop | mark dscp - For rate-kbps, specify average allowed traffic rate in kbps.
new-dscp | mark drop- The range is 64 to 1048512. You can select values which
precedence} are 64 times only.
- For burst-kbits, specify the normal burst size in kilo bits. The
range is 32 to 4096. You can select the values which are 32
times only.
Note Although the command-line help strings show a large
range of values, the rate-kbps option cannot exceed the
configured port speed.
Step 12 interface interface-id Enter interface configuration mode, and specify the interface to
attach to the policy map.
Valid interfaces include physical interfaces.
Step 13 service-policy {input policy-map- Apply a policy map to the input or output of a particular interface.
name | output policy-map-name} Only one policy map per interface per direction is supported.
- Use input policy-map-name to apply the specified policy-
map to the input of an interface.
- Use output policy-map-name to apply the specified policy-
Command Description
Step 16 write memory (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name command in global
configuration mode. To return to the default trust state, use the no trust command in policy-map
configuration command. To remove an assigned DSCP or IP precedence value, use the no set {drop-
command in policy-map configuration mode. To remove an existing policer, use the no police
command in policy-map configuration mode. To remove the policy map and interface association, use
This example shows how to create a policy map and attach it to an ingress interface. In the
configuration, the IP ACL permits traffic with an IP precedence of 4 from any host destined for the host
at 224.0.0.5. For traffic matching this classification, the DSCP value in the incoming packet is set to 63.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#ip access-list test_acl1 permit tcp any host 224.0.0.5
precedence 4
DUT-1(config)#class-map ipclass1
new class-map(ipclass1) created
DUT-1(config-class-map)#match ip access-group test_acl1
DUT-1(config-class-map)#exit
DUT-1(config)#policy-map ip_pol1
new policy-map(ip_pol1) created
DUT-1(config-policy-map)#class ipclass1
DUT-1(config-pmap-class)#set ip dscp 63
DUT-1(config-pmap-class)#exit
DUT-1(config-policy-map)#exit
DUT-1(config)#interface fe2.1
DUT-1(config-if)#service-policy input ip_pol1
DUT-1(config-if)#end
DUT-1#
This example shows how to create a Layer 2 MAC ACL with two permit statements and attach it to an
ingress interface. The first permit statement allows traffic from the host with MAC address
0001.0000.0001 destined for the host with MAC address 0002.0000.0001. The second permit
statement allows from the host with MAC address 0001.0000.0002 destined for the host with MAC
address 0002.0000.0002.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#mac access-list maclist1 permit host 0001.0000.0001 host
0002.0000.0001
DUT-1(config)#mac access-list maclist1 permit host 0001.0000.0002 host
0002.0000.0002
DUT-1(config)#mac access-list maclist2 permit host 0001.0000.0003 host
0002.0000.0003
DUT-1(config)#mac access-list maclist2 permit host 0001.0000.0004 host
0002.0000.0004
DUT-1(config)#class-map macclass1
new class-map(macclass1) created
DUT-1(config-class-map)#match mac access-group maclist1
DUT-1(config-class-map)#exit
DUT-1(config)#class-map macclass2
new class-map(macclass2) created
DUT-1(config-class-map)#match mac access-group maclist2
DUT-1(config-class-map)#exit
DUT-1(config)#policy-map macpolicy1
new policy-map(macpolicy1) created
DUT-1(config-policy-map)#class macclass1
DUT-1(config-pmap-class)#set cos 7
DUT-1(config-pmap-class)#exit
DUT-1(config-policy-map)#class macclass2
DUT-1(config-pmap-class)#set cos 4
DUT-1(config-pmap-class)#exit
DUT-1(config-policy-map)#exit
DUT-1(config)#interface fe2.2
DUT-1(config-if)#service-policy input macpolicy1
DUT-1(config-if)#end
DUT-1#
information.
9
9
You can configure the CoS-Queue Map. Beginning in Enable mode, follow these steps to map CoS
Command Description
Step 3 qos cos-queue map cos cos Map assigned a CoS value to select one of the egress queue.
queue queue-id The default map has these values:
- CoS 0, 1: selects Queue 1
- CoS 2, 3: selects Queue 2
- CoS 4, 5: selects Queue 3
- CoS 6, 7: selects Queue 4
For cos, specify the CoS value that select a queue. The range is
0 to 7
For queue-id, specify the ID of the egress queue. The range is 1
to 4.
Step 6 write memory (Optional) Save your entries in the configuration file.
To return the default CoS-to-egress-queue map, use the no cos-queue map command in global
configuration mode.
This example shows how to map CoS values 6 and 7 to queue 1, 4 and 5 to queue 2, 2 and 3 to
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#qos cos-queue map cos 7 queue 0
DUT-1(config)#qos cos-queue map cos 6 queue 0
DUT-1(config)#qos cos-queue map cos 5 queue 1
DUT-1(config)#qos cos-queue map cos 4 queue 1
DUT-1(config)#qos cos-queue map cos 3 queue 2
DUT-1(config)#qos cos-queue map cos 2 queue 2
DUT-1(config)#qos cos-queue map cos 1 queue 3
DUT-1(config)#qos cos-queue map cos 0 queue 3
DUT-1(config)#end
DUT-1#show qos cos-queue-map
Cos-Queue Map(Queues in use: 4)
0 - 3
1 - 3
2 - 2
3 - 2
4 - 1
5 - 1
6 - 0
7 - 0
DUT-1#
VX-MD3024 System supports two types of queue scheduling method. The one is Strict Priority Queue
(SPQ) and the other is Weighted Round Robin (WRR). The default queue scheduling method is SPQ.
Beginning in Enable mode, follow these steps to configure the queue scheduling method.
Command Description
Command Description
Step 3 qos scheduling spq Select the queue scheduling method to SPQ.
The default queue scheduling method is SPQ.
Step 4 qos scheduling wrr weight Select the queue scheduling method to WRR and assign WRR
weight0 weight1 weight2 weight3 weights to the egress queue.
For weight0 weight1 weight2 weight3, enter the ratio, which
determines the ratio of the frequency in which the WRR
scheduler dequeues packets. Separate each value with white
space. The range is 1 to 15.
Step 7 write memory (Optional) Save your entries in the configuration file.
This example shows how to configure the weight ratio of the WRR scheduler running on the egress
queues. In this example, four queues are used and the ratio of the bandwidth allocated for each queue
is 1/(1+2+3+4), 2/(1+2+3+4), 3/(1+2+3+4), and 4/(1+2+3+4), which is 1/10, 1/5, 3/10, and 2/5 for
queues 1, 2, 3, and 4.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#qos scheduling wrr weight 1 2 3 4
DUT-1(config)#end
DUT-1#
Command Description
show class-map [class-map-name] Display QoS class maps, which define the match criteria to
classify traffic.
show policy-map [policy-map-name] Display QoS policy maps, which define classificataion criteria
for incoming traffic.
show qos [{cos-queue-map | Display QoS information, including QoS status, the
congestion-ctrl | scheduling}] configuration of queue scheduling method and the weight of
each queue and the CoS-to-egress queue map.
If you specify the category that you want to show, the specified
information would be displayed.
DUT-1#show policy-map
Policy-map ip_pol1
class ipclass1 [match ip access-group test_acl1]
set ip dscp 63
Policy-map macpolicy1
class macclass1 [match mac access-group maclist1]
set cos 7
class macclass2 [match mac access-group maclist2]
set cos 4
DUT-1#
DUT-1#show qos
Queuing Mode: SPQ
This chapter describes how to configure Simple Network Management Protocol (SNMP) on your
system.
managers and agents. The SNMP system consists of an SNMP manager, an SNMP agent, and a
management information base (MIB). The SNMP manager can be part of a network management
system (NMS). The agent and MIB reside on the system. To configure SNMP on the system, you
The SNMP agent contains MIB variables whose values the SNMP manager can request or change. A
manager can get a value from an agent or store a value into the agent. The agent gathers data from
the MIB, the repository for information about device parameters and network data. The agent can also
An agent can send unsolicited traps to the manager. Traps are messages alerting the SNMP manager
to a condition on the network. Traps can mean improper user authentication, restarts, link status (up or
SNMP Messages
SNMP Community
SNMP Notifications
The SNMP agent is a network management module running in the managed device. The SNMP agent
− Get a MIB variable: The SNMP agent initiates this function in response to a request from the
NMS. The agent retrieves the value of the requested MIB variable and responds to the NMS
with that value.
− Set a MIB variable: The SNMP agent initiates this function in response to a message from the
NMS. The SNMP agent changes the value of the MIB variable to the value requested by the
NMS.
The SNMP agent also sends unsolicited trap messages to notify an NMS that a significant event has
occurred on the agent. Examples of traps conditions include, but are not limited to, when a port or
module goes up or down, when spanning-tree topology changes occur, and when authentication
failures occur.
The MIB is the information base, the SNMP agent must keep available for the managers. This
information base contains objects whose values provide information on the status of the checked
system or objects whose values can be modified by a manager to control the system. Each object is
identified by an Object ID (OID). There are two kinds of MIBs, standard MIB and enterprise-specific
MIB.
SNMP Manager is an integrated management module which collects information from SNMP agent
and sometimes sends warning messages depending on the each SNMP agent relations. In other
words, the actual data is collected from SNMP agent and this data will be processed by management
module and saved. To request information or configuration changes, respond to requests, and send
unsolicited alerts, the SNMP manger and SNMP agent use the four messages (Get, GetNext, Set,
trap).
SNMP Messages
The SNMP manager and SNMP agent use the following SNMP messages to request information or
− Trap Message
Get-Request Message is the basic SNMP request message. Sent by an SNMP manager, it requests
information about a single MIB entry on an SNMP agent. For example, the amount of free drive space.
GetNext-Request Message is an extended type of request message that can be used to browse the
entire tree of management objects. When processing a Get-next request for a particular object, the
agent returns the identity and value of the object which logically follows the object from the request.
The Get-next request is useful for dynamic tables, such as an internal IP route table.
If write access is permitted, Set-Request message can be used to send and assign an updated MIB
( ) Trap Message
An unsolicited message sent by an SNMP agent to an SNMP manager when the agent detects that a
certain type of event has occurred locally on the managed device. For example, a trap message might
SNMP Community
SNMP community strings authenticate access to MIB objects and function as embedded passwords.
In order for the NMS to access the system, the community string definitions on the NMS must match at
Read Only (RO) Gives read access to authorized management stations to all objects in the
MIB, but does not allow write access.
Read Write (RW) Gives read and write access to authorized management stations to all
objects in the MIB.
SNMP Notifications
SNMP allows the system to send notification to SNMP managers when particular events occur. SNMP
notification can be sent as traps. Use the snmp trap-receiver commands to specify whether to send
SNMP notifications as traps.
information.
Configuring Community
SNMP Trap Source Interface None configured. If SNMP trap source interface is not defined,
the source IP address of each trap message’s is the IP
address of routed interface.
Configuring Community
You use the SNMP community string to define the relationship between the SNMP manager and the
agent. The community string acts like a password to permit access to the agent on the system.
Beginning in Enable mode, follow these steps to configure a community string on the system.
Command Descriptioin
Step 5 write memory (Optional) Save your entries in the configuration file.
To remove a specific community string, use the no snmp community string command in global
configuration mode.
This example shows how to assign the string everyone to SNMP, to allow read-only access, and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#snmp community everyone readonly
DUT-1(config)#snmp community administrator readwrite
DUT-1(config)#end
DUT-1#
Trap receiver is the SNMP manager station to receive traps from an SNMP agent. Trap is the message
sent by an SNMP agent to an NMS to indicate the occurrence of a significant event, such as a
specifically defined condition or a threshold that was reached. By default, no trap receiver is
configured. To receive the trap generated on your managed device using NMS, you must add the NMS
as a trap receiver. You can specify up to 8 trap receivers on the VX-MD3024 system.
Command Description
Step 2 snmp trap-receiver ip-address Specify the recipient of an SNMP trap operation.
community-string For ip-address, specify IP address of the targeted
recipient.
For community-string, enter the password-like community
string sent with the notification operation.
Step 5 write memory (Optional) Save your entries in the configuration file.
To remove the specified trap receiver, use the no snmp trap-receiver ip-address command in global
configuration mode.
This example shows how to add a SNMP trap receiver whose IP address is 192.168.100.100 and
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#snmp trap-receiver 192.168.100.100 public
DUT-1(config)#end
DUT-1#
There are many kinds of SNMP trap messages provided by SNMP on the VX-MD3024 system -
2. cpu-utilization-trap is shown when the cpu utilization threshold configured by user excess.
Also when CPU utilization is down under the threshold, trap message will be sent to inform it.
DHCP server. Also when DHCP server starts and stops, this trap message will be sent to
inform it.
4. ip-permit-denied trap is shown when the host which has unauthorized IP address access your
system.
connected again.
excess. Also when memory utilization is down under the threshold, trap message will be sent
to inform it.
However, it may be inefficient work if all these trap messages are too frequently sent. Therefore, user
Use the following commands in global configuration mode to configure kinds of trap messages that
Command Description
To block each kinds of trap messages to send a configured trap receiver, use the following commands
Command Description
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#snmp trap config-change-trap
DUT-1(config)#end
DUT-1#
VX-MD3024 system can have several Layer 3 interface and IP address is assigned to the Layer 3
interfaces. Normally, to manage your network effectively you might use only one IP address that
But, if there are several Layer 3 interfaces on your system, the source IP address of trap message that
is sent from your system can be selected different IP address according to the routing information. In
this case, when you receive trap messages on your NMS, you cannot identify which device sent it.
In order to solve this problem, you can configure the interface that is used for source IP address of all
Beginning in Enable mode, follow these steps to configure the source interface of trap messages on
your system.
Command Description
Step 2 snmp trap-source-interface interface- Configure the source interface of trap messages.
name For interface-name, specify the name of the interface
used for source interface of the SNMP trap messages.
Step 5 write memory (Optional) Save your entries in the configuration file.
To remove the configured source interface of trap message, use the no snmp trap-source-interface
command in global configuration mode. To display the source interface of trap message information,
This example shows how to configure the source interface of trap message to vlan1.10, and verify the
configuration.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#snmp trap-source-interface vlan1.10
DUT-1(config)#end
DUT-1#show snmp trap-receiver
**************************************************************************
SNMP Trap Receiver List
**************************************************************************
ID Community IP Address
--------------------------------------------------------------------------
1 public 192.168.100.100
2 public 210.121.174.215
--------------------------------------------------------------------------
+ SNMP Trap source interface : vlan1.10(192.168.40.201)
--------------------------------------------------------------------------
DUT-1#
Command Description
show snmp trap Displays the configuring status of each kind of trap messages.
show snmp trap-receiver Displays the configured trap receivers and the source interface
and source IP address that is configured to be used in trap
messages.
This example shows how to display the configured SNMP community strings.
The chapter 15 describes how to configure system message logging on your system.
commands to the logging process. The logging process performs function distribute log messages to
various destinations like as local buffer, NVRAM, terminal and remote syslog server and so on. The
Users can configure kind and class of messages to be forwarded to console or other destinations, and
configure sender address of log message to forward outside as a specific interface address. And in
case of storing log messages in the system, you can configure maximum buffer size according to limit
of buffer or NVRAM size. The buffer is circular, so newer messages overwrite older messages after the
buffer is full.
You can configure facility and class of log message in order to store specific log messages. You can
configure also the facility of each kind of log message to the facility you want.
You can show log messages stored in the internal buffer and NVRAM through telnet or console, and
You can configure location of system message logging. The location of message logging can be
divided internal buffer, system terminal or remote syslog server. The system internal buffer can be
divided internal buffer that removes log messages in rebooting and nvram that maintains log messages
in rebooting. You can configure the log messages received to display to the system console, all telnet
terminals and user-connected telnet terminal.
Beginning in Enable mode, use the following commands to specify the location to log system
messages.
command purpose
Step 2 syslog local {buffer | nvram} Log messages to the internal buffer
- Messages stored in the buffer can be removed in
rebooting
- Messages stored in the nvram can be maintained in
rebooting
Step 4 syslog remote ip-address Forward system messages to the remote syslog server
Step 7 write memory (Optional) Save your entries to the configuration file
To disable logging to the console, use the no syslog terminal console command on global
configuration mode, To disable logging to the nvram, use the no syslog local nvram command on
global configuration mode.
This example shows how to configure message logging to the internal buffer and the syslog server of
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#syslog local buffer
DUT-1(config)#syslog remote 192.168.100.100
DUT-1(config)#end
DUT-1#show syslog
+ syslog remote source-interface : default
+ syslog local max-entry-size : buffer = 1000, NVRAM = 760
+ syslog configuration
Facility Severity Target
----------------------------------------------------------------------------
all debug Local System(buffer)
all debug Remote System(192.168.100.100)
DUT-1#
You cannot log all system messages because the limitation of memory size. You can configure the
maximum entry size of the buffer or nvram according to the size of internal local buffer and nvram. The
buffer is implemented with circular method, so newer message overwrite older message after the buffer
is full.
To configure the maximum message entry size according to the location, use the following commands
Command Description
syslog local buffer max-entry-size number Configure the maximum message entry size of local
buffer. The range is from 1 to 10,000, and the default
value is 1,000.
syslog local nvram max-entry-size number Configure the maximum message entry size of nvram.
The range is from 1 to 760, and the default value is
760..
To configure the number of maximum message entries of local buffer and nvram as the default, use the
no syslog local buffer max-entry-size commands, and the no syslog local nvram max-entry-size
command in global configuration mode.
This example shows how to configure the number of maximum message entries in local buffer as 2000
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#syslog local buffer max-entry-size 2000
DUT-1(config)#syslog local nvram max-entry-size 500
DUT-1(config)#end
DUT-1#write memory
[OK]
DUT-1#
You can limit messages displayed to the selected device by specifying the facility and the severity level
of the messages.
When you define destination device to the log messages, to limit messages displayed to the selected
Command Description
syslog local {buffer | nvram} [facility facility- Save system messages to the local buffer
name severity level] - The messages stored in buffer are deleted in rebooting.
- The messages stored in nvram are maintained after
rebooting.
Configure the facility and severity level of the log message
to be saved in local buffer.
- The facility is configured to all and severity level is
configured to debug if not specify the facility and severity.
syslog terminal {console | telnet | this- Limit messages logged to the terminal.
session} [facility facility-name severity level] - The console limits the messages logged to the system
console.
- The telnet limits the messages logged to all telnet
terminal connected the system.
- The this-session limits the messages logged to only
terminal connected to current user.
Configure the facility and severity level of the logging
messages to be saved in local buffer.
- The facility is configured to all and severity level is
configured to debug if not specify the facility and severity.
syslog remote ip-address [facility facility-name Limit messages logged to the remote syslog server.
severity level] Configure the facility and severity level of the log
messages to be saved in local buffer.
- The facility is configured to all and severity level is
configured to debug if not specify the facility and severity.
kern Kernel
You can configure several conditions of the system messages logged to the same destinations at the
same time.
This example shows how to configure location of the log messages as local buffer and display all
system messages on condition that facility type is local0 and severity level is higher than information,
and on condition that facility type is daemon and severity level is higher than error.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
VX-MD3024 performs various functions related on multiplayer switch, operation, administration and
maintenance, and so on. The system messages generated by these functions are classified as daemon
In case that you want to save the system messages related on specific functions of them, VX-MD3024
supports to change the facility configuration of system messages generated by the functions. The
You can configure the facility for the following functions in the system log profiles.
The facility of the default log profile is configured to daemon for all functions described above.
Beginning in Enable mode, follow these steps to configure facility for all functions defined in log profile
by user.
command purpose
Step 4 command facility facility-name Configure the facility for command messages
Step 5 dhcp-server facility facility-name Configure the facility for dhcp-server messages
Step 6 dhcp-snoop facility facility-name Configure the facility for dhcp-snoop messages
Step 7 stp facility facility-name Configure the facility for stp messages
Step 8 system-oam facility facility-name Configure the facility for system-oam messages
Step 9 user-session facility facility-name Configure the facility for user-session messages
Step 10 vdsl facility facility-name Configure the facility for vdsl messages
Step 13 write memory (Optional) Save your entries in the configuration file
This example shows how to configure the facility for alarm messages to local0 and the facility for
DUT-1#configure terminal
To display the logging configuration of the facility for the system message, use the following command
in Enable mode.
Command Description
The following example shows how to display the configuration of the facility in the log-profile.
DUT-1#show log-profile
Logging Type Facility
----------------------------------------------------------------------------
dhcp-server daemon
alarm daemon
system-oam daemon
command daemon
user-session daemon
dhcp-snoop daemon
vdsl daemon
stp daemon
DUT-1#
When two or more Layer 3 interfaces exist on your system and IP addresses are assigned for each
Layer 3 interface, the source IP address of syslog messages can be assigned differently according to
route information of destination IP address. In general, users can easily manage the received log
messages when source IP address is assigned to the representative IP address registered in the
system.
You can configure only IP address of specific Layer 3 interface to IP address of the syslog source
Beginning in Enable mode, follow these steps to configure syslog source interface.
Command Description
Step 2 syslog remote source-interface Configure the source interface of syslog message
interface-name The interface-name is the Layer 3 interface that used for
source IP address when sending syslog messages.
Step 5 write memory (Optional) Save your entries in the configuration file.
To set the syslog source interface to the default configuration, use the no syslog remote source-
This example shows how to configure the syslog source interface to the Layer 3 interface which is the
VLAN1.10.
DUT-1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DUT-1(config)#syslog remote source-interface vlan1.10
DUT-1(config)#end
DUT-1#
Command Description
The following is an example displaying the logging configuration of the system message.
DUT-1#show syslog
+ syslog remote source-interface : vlan1.10(192.168.40.201)
+ syslog local max-entry-size : buffer = 100, NVRAM = 500
+ syslog configuration
Facility Severity Target
--------------------------------------------------------------------
daemon err Local System(buffer)
local0 info Local System(buffer)
Beginning in Enable mode, use the following command in order to verify the system log messages
Command Description
show log buffer type [oldest-first] Display the system log messages stored in the local buffer.
- For type, select a type of {alarm | command | dhcp-server |
dhcp-snoop | ospf | pim | rip | stp | system-oam | user-session |
vdsl | all}.
- If you add oldest-first keyword, you can show the log message
from the oldest one. If you skip oldest-first, you can show the log
message from the newest one.
show log nvram type [oldest-first] Display the system log message stored in nvram.
- Select a type of {alarm | command | dhcp-server | dhcp-snoop |
ospf | pim | rip | stp | system-oam | user-session | vdsl | all}.
- If you add oldest-first keyword, you can show the log message
from the oldest one. If you skip oldest-first, you can show the log
message from the newest one.
This example shows how to display the system log messages stored in local buffer.
following command in order to delete the log message stored in the system.
Command Description
clear log buffer [type] Delete the log message stored in local buffer.
- To delete only specified type of log messages, select a type of
{alarm | command | dhcp-server | dhcp-snoop | ospf | pim | rip |
stp | system-oam | user-session | vdsl | all}.
- If you skip type, you can delete all log messages.
clear log nvram [type] Delete the log message stored in nvram.
- To delete only specified type of log messages, select a type of
{alarm | command | dhcp-server | dhcp-snoop | ospf | pim | rip |
stp | system-oam | user-session | vdsl | all}.
- If you skip type, you can delete all log messages.
This example shows how to delete only log messages related to user-session of the log messages in
(RADIUS), which provides detailed accounting information and flexible administrative control over
authentication and authorization processes. RADIUS is facilitated through AAA and can be enabled
9 Understanding RADIUS
9 RADIUS Operation
9 Configuring RADIUS
Understanding RADIUS
RADIUS is a distributed client/server system that secures networks against unauthorized access.
RADIUS clients run on VX-MD3024. Clients send authentication requests to a central RADIUS server,
which contains all user authentication and network service access information. The RADIUS host is
normally a multiuser system running RADIUS server software from Livingston, Merit, Microsoft, or
another software provider. For more information, refer to the RADIUS server documentation.
z Networks with multiple-vendor access servers, each supporting RADIUS. For example, access
servers from several vendors use a single RADIUS server-based security database. In an IP-
based network with multiple vendors’ access servers; dial-in users are authenticated through a
RADIUS server that has been customized to work with the Kerberos security system.
z Turnkey network security environments in which applications support the RADIUS protocol, such
as in an access environment that uses a smart card access control system. In one case, RADIUS
has been used with Enigma’s security cards to validate users and to grant access to network
resources.
z Networks already using RADIUS. You can add a switch containing a RADIUS client to the network.
z Network in which the user must only access a single service. Using RADIUS, you can control user
access to a single host, to a single utility such as Telnet, or to the network through a protocol such
as IEEE 802.1X.
z Networks that require resource accounting. You can use RADIUS accounting independently of
RADIUS authentication or authorization. The RADIUS accounting functions allow data to be sent
at the start and end of services, showing the amount of resources (such as time, packets, bytes,
and so forth) used during the session. An Internet service provider might use a freeware-based
version of RADIUS access control and accounting software to meet special security and billing
needs.
z Multiprotocol access environments. RADIUS does not support AppleTalk Remote Access (ARA),
NetBIOS Frame Control Protocol (NBFCP), NetWare Asynchronous Services Interface (NASI), or
z Networks using a variety of services. RADIUS generally binds a user to one service model.
RADIUS Operation
When a user attempts to log in and authenticate to a switch that is access controlled by a RADIUS
2. The username and encrypted password are sent over the network to the RADIUS server.
3. The user receives one of these responses from the RADIUS server:
The ACCEPT or REJECT response is bundled with additional data that is used for privileged EXEC or
network authorization. Users must first successfully complete RADIUS authentication before
proceeding to RADIUS authorization, if it is enabled. The additional data included with the ACCEPT or
z Connection parameters, including the host or client IP address, access list, and user timeouts
Configuring RADIUS
This section describes how to configure your system to support RADIUS. At a minimum, you must
identify the host or hosts that run the RADIUS server software and define the method lists for RADIUS
authentication. You can optionally define method lists for RADIUS authorization and accounting.
A method list defines the sequence and methods to be used to authenticate, to authorize, or to keep
accounts on a user. You can use method lists to designate one or more security protocols to be used
(such as TACACS+ or local username lookup), thus ensuring a backup system if the initial method
fails. The software uses the first method listed to authenticate, to authorize, or to keep accounts on
users; if that method does not respond, the software selects the next method in the list. This process
continues until there is successful communication with a listed method or the method list is exhausted.
You should have access to and should configure a RADIUS server before configuring RADIUS
To prevent a lapse in security, you cannot configure RADIUS through a network management
application. When enabled, RADIUS can authenticate users accessing the system through the CLI.
− Key string
− Timeout period
− Retransmission value
You identify RADIUS security servers by their IP address or their IP address and specific UDP port
numbers. The combination of the IP address and the UDP port number creates a unique identifier,
allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service.
This unique identifier enables RADIUS requests to be sent to multiple UDP ports on a server at the
same IP address.
If two different host entries on the same RADIUS server are configured for the same service—for
example, accounting—the second host entry configured acts as a fail-over backup to the first one.
Using this example, if the first host entry fails to provide accounting services, the system tries the
second host entry configured on the same device for accounting services. (The RADIUS host entries
A RADIUS server and the switch use a shared secret text string to encrypt passwords and exchange
responses. To configure RADIUS to use the AAA security commands, you must specify the host
running the RADIUS server daemon and a secret text (key) string that it shares with the system.
The timeout, retransmission, and encryption key values can be configured globally for all RADIUS
servers, on a per-server basis, or in some combination of global and per-server settings. To apply
these settings globally to all RADIUS servers communicating with the system, use the three unique
server key. To apply these values on a specific RADIUS server, use the radius-server host global
configuration command.
Beginning in privileged EXEC mode, follow these steps to configure per-server RADIUS server
Command Description
Step 2 radius-server host ip-address [default | Specify the IP address of the remote RADIUS server host.
[auth-port port-number] (Optional) default: If you use default without specific auth-
[timeout seconds] port, timeout, retries and key information, the specified host
[retries retries] would use the pre-defined default values.
Note
The key is a text string that must match the encryption key
Step 5 write memory (Optional) Save your entries in the configuration file.
To remove the specified RADIUS server, use the no radius-server host ip-address global
configuration command.
This example shows how to configure one RADIUS server to be used for default auth-port, retry
counts and how to display the configured RADIUS server information on the system.
DUT-1#configure terminal
DUT-1(config)#service aaa
DUT-1(config)#radius-server host 192.168.2.244 default
DUT-1(config)#end
DUT-1#show aaa radius
**************************************************************************
RADIUS server information
**************************************************************************
RADIUS group 1 used
--------------------------------------------------------------------------
index | server group information
--------------------------------------------------------------------------
0 | group name : NULL
| secret key : versatek_secret
To configure AAA authentication, you define a named list of authentication methods and then apply
that list to various interfaces. The method list defines the types of authentication to be performed and
the sequence in which they are performed; it must be applied to a specific interface before any of the
defined authentication methods are performed. The only exception is the default method list (which, by
coincidence, is named default). The default method list is automatically applied to all interfaces except
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a
backup system for authentication in case the initial method fails. The software uses the first method
listed to authenticate users; if that method fails to respond, the software selects the next authentication
method in the method list. This process continues until there is successful communication with a listed
authentication method or until all defined methods are exhausted. If authentication fails at any point in
this cycle—meaning that the security server or local username database responds by denying the user
access—the authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication. This
procedure is required.
radius { all | group_name } | authentication are used only if the previous method
returns an error, not if it fails.
tacacs { all | group_name } }
Select one of these methods:
- local : Use the line password for authentication.
- radius : Use RADIUS authentication. Before you can
use this authentication method, you must configure the
RADIUS server. In this case, if you select all key-word,
the system tries to all defined RADIUS server on your
system. If you specify a group-name, the system would try
only the RADIUS servers included in the radius group.
- tacacs: Use TACACS+ authentication. Before you can
use this authentication method, you must configure the
TACACS+ server. If you select all key-word, the system
tries to all defined TACACS+ servers on your system. If
you specify a group-name, the system would try only the
TACACS+ servers included in the tacacs group.
- none: Do not use any authentication for login.
Step 4 line { console | vty } line-number Enter line configuration mode, and configure the lines to
[ending-line-number] which you want to apply the authentication list.
Step 5 login authentication { default | list- Apply the authentication list to a line or set of lines.
name } - If you specify default, use the default list created with
the aaa authentication login command.
- For list-name, specify the list created with the aaa
authentication login command.
Step 8 write memory (Optional) Save your entries in the configuration file.
authentication, use the no aaa authentication login global configuration command. To either disable
RADIUS authentication for login or to return to default values, use the no login authentication line
configuration command.
This example shows how to configure RADIUS server to be used at first time and local password at
DUT-1#configure terminal
DUT-1(config)#service aaa
DUT-1(config)#aaa authentication login default 1st radius all 2nd local 3rd
none
DUT-1(config)#line vty 0 4
DUT-1(config-line)#login authentication default
DUT-1(config-line)#end
This example shows how to display the configured login policy list.
This example shows how to display the configured login policy per line.
Beginning in privileged EXEC mode, follow these steps to configure global communication settings
Step 2 radius-server key string Specify the shared secret text string used between the
system and all RADIUS servers.
Note
The key is a text string that must match the encryption key
used on the RADIUS server. Always configure the key as
the last item in the radius-server host command. Leading
spaces are ignored, but spaces within and at the end of
the key are used. If you use spaces in your key, do not
enclose the key in quotation marks unless the quotation
marks are part of the key.
Step 3 radius-server retries retries Specify the number of times the system sends each
RADIUS request to the server before giving up. The
default is 3; the range 1 to 1000.
Step 4 radius-server timeout seconds Specify the number of seconds a system waits for a reply
to a RADIUS request before resending the request. The
default is 5 seconds; the range is 1 to 1000.
Step 7 write memory (Optional) Save your entries in the configuration file.
To return to the default setting for the retransmit and timeout, use the no forms of these commands.
You can configure the system to use AAA server groups to group existing server hosts for
authentication. You select a subset of the configured server hosts and use them for a particular
service. The server group is used with a global server-host list, which lists the IP addresses of the
Server groups also can include multiple host entries for the same server if each entry has a unique
identifier (the combination of the IP address and UDP port number), allowing different ports to be
individually defined as RADIUS hosts providing a specific AAA service. If you configure two different
host entries on the same RADIUS server for the same service, (for example, accounting), the second
You use the server group server configuration command to associate a particular server with a defined
group server. You can either identify the server by its IP address or identify multiple host instances or
Beginning in privileged EXEC mode, follow these steps to define the AAA server group and associate
Step 2 radius-server host ip-address [default | Specify the IP address of the remote RADIUS server host.
([auth-port port-number] (Optional) default: If you use default without specific auth-
[timeout seconds] port, timeout, retries and key information, the specified host
[retries retries] would use the pre-defined default values.
Note
The key is a text string that must match the encryption key
used on the RADIUS server. Always configure the key as
the last item in the radius-server host command. Leading
spaces are ignored, but spaces within and at the end of
the key are used. If you use spaces in your key, do not
enclose the key in quotation marks unless the quotation
marks are part of the key.
Step 4 aaa group server radius group-name Define the AAA server-group with a group name.
This command puts the system in a server group
configuration mode.
Step 5 server ip-address Associate a particular RADIUS server with the defined
server group. Repeat this step for each RADIUS server in
the AAA server group.
Each server in the group must be previously defined in
Step 2.
Step 8 write memory (Optional) Save your entries in the configuration file.
To remove the specified RADIUS server, use the no radius-server host ip-address global
configuration command. To remove a server group from the configuration list, use the no aaa group
server radius group-name global configuration command. To remove the IP address of a RADIUS
In this example, the system is configured to recognize two different RADIUS group servers (group1
and group2). The second host entry acts as a fail-over backup to the first entry.
DUT-1#configure terminal
VX-MD3024(config)#radius-server host 192.168.10.11 auth-port 1000
VX-MD3024(config)#radius-server host 192.168.20.22 auth-port 1745
DUT-1(config)#service aaa
DUT-1(config)#aaa group server radius group1
VX-MD3024(config-aaa-group)#server 192.168.10.11
VX-MD3024(config-aaa-group)#exit
VX-MD3024(config)#aaa group server radius group2
VX-MD3024(config-aaa-group)#server 192.168.20.22
DUT-1(config-aaa-group)#end
DUT-1#
To display the configured RADIUS server list and RADIUS group-list, use the show aaa radius
privileged EXEC command. To display the configured login policy per line, use the show aaa line-
System Plus (TACACS+), which provides flexible administrative control over authentication and
9 TACACS+ Operation
9 Configuring TACACS+
Understanding TACACS+
TACACS+ is a security application that provides centralized validation of users attempting to gain
access to your switch. TACACS+ services are maintained in a database on a TACACS+ daemon
typically running on a UNIX or Windows NT workstation. You should have access to and should
configure a TACACS+ server before the configuring TACACS+ features on your switch.
TACACS+ provides for separate and modular authentication, authorization, and accounting facilities.
TACACS+ allows for a single access control server (the TACACS+ daemon) to provide each service—
authentication, authorization, and accounting—independently. Each service can be tied into its own
database to take advantage of other services available on that server or on the network, depending on
TACACS+ Operation
When a user attempts a simple ASCII login by authenticating to a switch using TACACS+, this
process occurs:
1. When the connection is established, the switch contacts the TACACS+ daemon to obtain a
username prompt, which is then displayed to the user. The user enters a username, and the
switch then contacts the TACACS+ daemon to obtain a password prompt. The switch displays the
password prompt to the user, the user enters a password, and the password is then sent to the
TACACS+ daemon. TACACS+ allows a conversation to be held between the daemon and the
user until the daemon receives enough information to authenticate the user. The daemon prompts
for a username and password combination, but can include other items, such as the user’s
2. The system eventually receives one of these responses from the TACACS+ daemon:
b. REJECT - The user is not authenticated. The user can be denied access or is
c. ERROR - An error occurred at some time during authentication with the daemon or in
the network connection between the daemon and the system if an ERROR response
is received, the system typically tries to use an alternative method for authenticating
the user.
3. If TACACS+ authorization is required, the TACACS+ daemon is again contacted, and it returns an
contains data in the form of attributes that direct the EXEC or NETWORK session for that user,
z Connection parameters, including the host or client IP address, access list, and user timeouts
Configuring TACACS+
This section describes how to configure your switch to support TACACS+. At a minimum, you must
identify the host or hosts maintaining the TACACS+ daemon and define the method lists for TACACS+
authentication. You can optionally define method lists for TACACS+ authorization and accounting. A
method list defines the sequence and methods to be used to authenticate, to authorize, or to keep
accounts on a user. You can use method lists to designate one or more security protocols to be used,
thus ensuring a backup system if the initial method fails. The software uses the first method listed to
authenticate, to authorize, or to keep accounts on users; if that method does not respond, the software
selects the next method in the list. This process continues until there is successful communication with
To prevent a lapse in security, you cannot configure TACACS+ through a network management
application. When enabled, TACACS+ can authenticate users accessing the switch through the CLI.
( ) Identifying the TACACS+ Server Host and Setting the Authentication Key
You can configure the system to use a single server or AAA server groups to group existing server
hosts for authentication. You can group servers to select a subset of the configured server hosts and
use them for a particular service. The server group is used with a global server-host list and contains
Beginning in privileged EXEC mode, follow these steps to identify the IP host or host maintaining
Step 2 tacacs-server host ip-address [ default Identify the IP host maintaining a TACACS+ server. Enter
| [auth-port port-number] this command multiple times to create a list of preferred
[timeout seconds] hosts. The software searches for hosts in the order in
which you specify them.
[key string] ]
(Optional) default: If you use default without specific auth-
port, timeout, retries and key information, the specified
host would use the pre-defined default values.
(Optional) For auth-port port-number, specify a server
port number. The default is port 49. the range is 1 to
65535.
(Optional) For timeout seconds, specify a time in seconds
the system waits for a response from the daemon before it
times out and declares an error. The default is 5 seconds.
The range is 1 to 1000 seconds.
(Optional) For key string, specify the encryption key for
encrypting and decrypting all traffic between the system
and the TACACS+ daemon. You must configure the same
key on the TACACS+ daemon for encryption to be
Step 4 aaa group server tacacs group-name (Optional) Define the AAA server-group with a group
name.
This command puts the system in a server group sub-
configuration mode.
Step 5 write memory (Optional) Save your entries in the configuration file.
To remove the specified TACACS+ server address, use the no tacacs-server host ip-address global
configuration command. To remove a server group from the configuration list, use the no aaa group
server tacacs group-name global configuration command. To remove the IP address of a TACACS+
To configure AAA authentication, you define a named list of authentication methods and then apply
that list to various interfaces. The method list defines the types of authentication to be performed and
the sequence in which they are performed; it must be applied to a specific interface before any of the
defined authentication methods are performed. The only exception is the default method list (which, by
coincidence, is named default). The default method list is automatically applied to all interfaces except
those that have a named method list explicitly defined. A defined method list overrides the default
method list.
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a
backup system for authentication in case the initial method fails. The software uses the first method
method in the method list. This process continues until there is successful communication with a listed
authentication method or until all defined methods are exhausted. If authentication fails at any point in
this cycle—meaning that the security server or local username database responds by denying the user
access—the authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication:
Step 3 aaa authentication login ( default | Create a login authentication method list.
list_name ) To create a default list that is used when a named list is
1st { local | not specified in the login authentication command, use
radius { all | group_name } | the default keyword followed by the methods that are to
be used in default situations. The default method list is
tacacs { all | group_name } }
automatically applied to all interfaces.
2nd { none | local |
For list-name, specify a character string to name the list
radius { all | group_name } | you are creating.
tacacs { all | group_name } } You can specify the actual method the authentication
3rd { none | local | algorithm tries to 3 times. The additional methods of
radius { all | group_name } | authentication are used only if the previous method
returns an error, not if it fails.
tacacs { all | group_name } }
Select one of these methods:
- local: Use the line password for authentication.
- radius: Use RADIUS authentication. Before you can use
this authentication method, you must configure the
RADIUS server. In this case, if you select all key-word,
the system tries to all defined RADIUS server on your
system. If you specify a group-name, the system would try
only the RADIUS servers included in the radius group.
- tacacs: Use TACACS+ authentication. Before you can
use this authentication method, you must configure the
TACACS+ server. If you select all key-word, the system
tries to all defined TACACS+ servers on your system. If
you specify a group-name, the system would try only the
TACACS+ servers included in the tacacs group.
Step 4 line { console | vty } line-number Enter line configuration mode, and configure the lines to
[ending-line-number] which you want to apply the authentication list.
Step 5 login authentication { default | list- Apply the authentication list to a line or set of lines.
name }
- If you specify default, use the default list created with
the aaa authentication login command.
- For list-name, specify the list created with the aaa
authentication login command.
Step 10 write memory (Optional) Save your entries in the configuration file.
To disable AAA, use the "no service aaa global" configuration command. To disable AAA
authentication, use the no aaa authentication login global configuration command. To either disable
RADIUS authentication for login or to return to default values, use the no login authentication line
configuration command.
To display TACACS+ server and server group lists, use the show aaa tacacs privileged EXEC
command.