Configuracion Switch Zyxel PDF
Configuracion Switch Zyxel PDF
Configuracion Switch Zyxel PDF
Copyright © 2011
Copyright
ZyXEL © 2013 ZyXEL
Communications Communications Corporation
Corporation
IMPORTANT!
READ CAREFULLY BEFORE USE.
KEEP THIS GUIDE FOR FUTURE REFERENCE.
This is a Reference Guide for a series of products. Not all products support all firmware features.
Screenshots, graphics and commands in this book may differ slightly from your product due to
differences in your product firmware or your computer operating system. Every effort has been made
to ensure that the information in this manual is accurate.
Related Documentation
• User’s Guide
The User’s Guide explains how to use the Web Configurator to configure the Switch.
Please refer to www.zyxel.com for product specific User Guides and product certifications.
Document Conventions
Warnings and Notes
These are how warnings and notes are shown in this CLI Reference Guide.
Warnings tell you about things that could harm you or your device. See your
User’s Guide for product specific warnings.
Notes tell you other important information (for example, other things you may
need to configure or helpful tips) or recommendations.
Syntax Conventions
This manual follows these general conventions:
• ZyXEL’s switches may be referred to as the “Switch”, the “device”, the “system” or the
“product” in this Reference Guide.
• Units of measurement may denote the “metric” value or the “scientific” value. For
example, “k” for kilo may denote “1000” or “1024”, “M” for mega may denote “1000000”
or “1048576” and so on.
Command descriptions follow these conventions:
• Commands are in courier new font.
• Required input values are in angle brackets <>; for example, ping <ip> means that you
must specify an IP address for this command.
• Optional fields are in square brackets []; for instance show logins [name], the name
field is optional.
The following is an example of a required field within an optional field: snmp-server
[contact <system contact>], the contact field is optional. However, if you
use contact, then you must provide the system contact information.
• Lists (such as <port-list>) consist of one or more elements separated by commas.
Each element might be a single value (1, 2, 3, ...) or a range of values (1-2, 3-5, ...)
separated by a dash.
• The | (bar) symbol means “or”.
• italic terms represent user-defined input values; for example, in snmp-server
[contact <system contact>], system contact can be replaced by the
administrator’s name.
• A key stroke is denoted by square brackets and uppercase text, for example, [ENTER]
means the “Enter” or “Return” key on your keyboard.
The Table title identifies commands or the specific feature that the commands configure.
The COMMAND column shows the syntax of the command.
• If a command is not indented, you run it in the enable or config mode. See Chapter 2 on
page 17 for more information on command modes.
• If a command is indented, you run it in a sub-command mode.
The DESCRIPTION column explains what the command does. It also identifies legal input
values, if necessary.
The M column identifies the mode in which you run the command.
• E: The command is available in enable mode. It is also available in user mode if the
privilege level (P) is less than 13.
• C: The command is available in config (not indented) or one of the sub-command modes
(indented).
The P column identifies the privilege level of the command. If you don’t have a high enough
privilege level you may not be able to view or execute some of the commands. See Chapter 2
on page 17 for more information on privilege levels.
Contents Overview
Introduction ............................................................................................................................ 11
11
12
C HA PT E R 1
How to Access and Use the CLI
This chapter introduces the command line interface (CLI).
1.1.2 Telnet
1 Connect your computer to one of the Ethernet ports.
2 Open a Telnet session to the Switch’s IP address. If this is your first login, use the default
values.
Table 3 Default Management IP Address
SETTING DEFAULT VALUE
IP Address 192.168.1.1
Subnet Mask 255.255.255.0
Make sure your computer IP address is in the same subnet, unless you are accessing the
Switch through one or more routers.
1.1.3 SSH
1 Connect your computer to one of the Ethernet ports.
2 Use a SSH client program to access the Switch. If this is your first login, use the default
values in Table 3 on page 13 and Table 4 on page 14. Make sure your computer IP
address is in the same subnet, unless you are accessing the Switch through one or more
routers.
1.2 Logging in
Use the administrator username and password. If this is your first login, use the default values.
Table 4 Default User Name and Password
SETTING DEFAULT VALUE
User Name admin
Password 1234
The Switch automatically logs you out of the management interface after five
minutes of inactivity. If this happens to you, simply log back in again.
You should save your changes after each CLI session. All unsaved
configuration changes are lost once you restart the Switch.
• Using vendor-specific attributes in an external authentication server. See the User’s Guide
for more information.
The admin account has a privilege level of 14, so the administrator can run every command.
You cannot change the privilege level of the admin account.
sysname> enable
Password: 123456
sysname#
The default enable password is 1234. Use this command to set the enable password.
password <password>
<password> consists of 1-32 alphanumeric characters. For example, the following
command sets the enable password to 123456. See Chapter 87 on page 339 for more
information about this command.
The password is sent in plain text and stored in the Switch’s buffers. Use this command to set
the cipher password for password encryption.
password cipher <password>
<password> consists of 32 alphanumeric characters. For example, the following command
encrypts the enable password with a 32-character cipher password. See Chapter 52 on page
229 for more information about this command.
In the following example, the login account user0 has a privilege level of 0 but knows that the
password for privilege level 13 is pswd13. Afterwards, the session’s privilege level is 13,
instead of 0, and the session changes to enable mode.
sysname> enable 13
Password: pswd13
sysname#
Users cannot use this command until you create passwords for specific privilege levels. Use
the following command to create passwords for specific privilege levels.
password <password> privilege <0-14>
<password> consists of 1-32 alphanumeric characters. For example, the following
command sets the password for privilege level 13 to pswd13. See Chapter 87 on page 339 for
more information about this command.
Each command is usually in one and only one mode. If a user wants to run a particular
command, the user has to change to the appropriate mode. The command modes are organized
like a tree, and users start in enable mode. The following table explains how to change from
one mode to another.
Table 8 Changing Between Command Modes for Privilege Levels 13-14
MODE ENTER MODE LEAVE MODE
enable -- --
config configure exit
config-interface interface port-channel <port-list> exit
config-mvr mvr <1-4094> exit
config-vlan vlan <1-4094> exit
config-route-domain interface route domain <ip-address>/<mask-bits> exit
config-dvmrp router dvmrp exit
config-igmp router igmp exit
config-ospf router ospf <router-id> exit
config-rip router rip exit
config-vrrp router vrrp network <ip-address>/<mask-bits> exit
vr-id <1~7> uplink-gateway <ip-address>
sysname# help
Commands available:
help
logout
exit
history
enable <0-14>
enable <cr>
.
.
traceroute <ip|host-name> [vlan <vlan-id>][..]
traceroute help
ssh <1|2> <[user@]dest-ip> <cr>
ssh <1|2> <[user@]dest-ip> [command </>]
sysname#
3 Copy and paste the results into a text editor of your choice. This creates a list of all the
executable commands in the user and enable modes.
4 Type configure and press [ENTER]. This takes you to the config mode.
5 Type help and press [ENTER]. A list is displayed which shows all the commands
available in config mode and all the sub-commands. The sub-commands are preceded by
the command necessary to enter that sub-command mode. For example, the command
name <name-str> as shown next, is preceded by the command used to enter the
config-vlan sub-mode: vlan <1-4094>.
sysname# help
.
.
no arp inspection log-buffer logs
no arp inspection filter-aging-time
no arp inspection <cr>
vlan <1-4094>
vlan <1-4094> name <name-str>
vlan <1-4094> normal <port-list>
vlan <1-4094> fixed <port-list>
6 Copy and paste the results into a text editor of your choice. This creates a list of all the
executable commands in config and the other submodes, for example, the config-vlan
mode.
sysname# configure
sysname(config)# admin-password t1g2y7i9 t1g2y7i9
It is recommended you change the default enable password. You can encrypt
the password with a cipher password. See Chapter 52 on page 229 for more
information.
sysname# configure
sysname(config)# password k8s8s3dl0
sysname# configure
sysname(config)# no multi-login
sysname# configure
sysname(config)# vlan 1
sysname(config-vlan)# ip address default-management 172.16.0.1 255.255.255.0
Afterwards, you have to use the new IP address to access the Switch.
sysname# configure
sysname(config)# ip address 10.10.10.1 255.255.255.0
sysname(config)# ip address default-gateway 10.10.10.254
See Chapter 87 on page 339 for more information about these attributes.
Current configuration:
vlan 1
name 1
normal ""
fixed 1-9
forbidden ""
untagged 1-9
ip address default-management 172.16.37.206 255.255.255.0
ip address default-gateway 172.16.37.254
exit
27
28
C HA PT E R 4
AAA Commands
Use these commands to configure authentication, authorization and accounting on the Switch.
sysname#
This example looks at log messages that were generated by ARP packets and that have not
been sent to the syslog server yet.
This example displays whether ports are trusted or untrusted ports for ARP inspection.
sysname# configure
sysname(config)# interface port-channel 8
sysname(config-interface)# arp-learning arp-request
See Section 8.2 on page 42 and Section 8.3 on page 43 for examples.
See also Chapter 79 on page 313 for information on how to use trTCM (Two Rate Three Color
Marker) to control traffic flow.
sysname# configure
sysname(config)# bandwidth-control
sysname(config)# interface port-channel 1
sysname(config-interface)# bandwidth-limit egress 5000
sysname(config-interface)# bandwidth-limit ingress 4000
sysname(config-interface)# exit
sysname(config)# exit
sysname# configure
sysname(config)# interface port-channel 1
sysname(config-interface)# no bandwidth-limit egress
sysname(config-interface)# exit
sysname(config)# exit
sysname# configure
sysname(config)# bandwidth-control
sysname(config)# interface port-channel 1
sysname(config-interface)# bandwidth-limit cir
sysname(config-interface)# bandwidth-limit cir 4000
sysname(config-interface)# bandwidth-limit pir
sysname(config-interface)# bandwidth-limit pir 5000
sysname(config-interface)# exit
sysname(config)# exit
Current configuration:
interface port-channel 1
bandwidth-limit cir 4000
bandwidth-limit cir
bandwidth-limit pir 5000
bandwidth-limit pir
• Some models use a single command (bmstorm-limit) to control the combined rate of
broadcast, multicast and DLF packets accepted on Switch ports.
• Other models use three separate commands (broadcast-limit, multicast-
limit, dlf-limit) to control the number of individual types of packets accepted on
Switch ports.
See Section 9.2 on page 46 and Section 9.3 on page 46 for examples.
sysname# configure
sysname(config)# storm-control
sysname(config)# interface port-channel 1
sysname(config-interface)# bmstorm-limit
sysname(config-interface)# bmstorm-limit 128
sysname(config-interface)# exit
sysname(config)# exit
sysname# configure
sysname(config)# storm-control
sysname(config)# interface port-channel 1
sysname(config-interface)# broadcast-limit
sysname(config-interface)# broadcast-limit 128
sysname(config-interface)# multicast-limit
sysname(config-interface)# multicast-limit 256
sysname(config-interface)# dlf-limit
sysname(config-interface)# dlf-limit 64
sysname(config)# exit
sysname# show interfaces config 1 bstorm-control
Broadcast Storm Control Enabled: Yes
The figure shown below is an example of a connection fault between switches in the service
provider’s network. CFM can be used to identify and management this kind of connection
problem.
CFM sends pro-active Connectivity Check (CC) packets between two CFM-aware devices in
the same MD (Maintenance Domain) network. An MA (Maintenance Association) defines a
VLAN and associated ports on the device under an MD level. In this MA, a port can be an
MEP (Maintenance End Point) port or an MIP (Maintenance Intermediate Point) port.
• MEP port - has the ability to send pro-active connectivity check (CC) packets and get
other MEP port information from neighbor switches’ CC packets within an MA.
• MIP port - only forwards the CC packets.
• Loopback test - similar to using “ping” in Microsoft DOS mode to check connectivity
from your computer to a host. In a loopback test, a MEP port sends a LBM (Loop Back
Message) to a MIP port and checks for an LBR (Loop Back Response). If no response is
received, there might be a connectivity fault between them.
• Link trace test - similar to using “tracert” in the Microsoft DOS mode to check
connectivity from your computer to a host. A link trace test provides additional
connectivity fault analysis to get more information on where the fault is. In a link trace
test, a MEP port sends a LTM (Link Trace Message) to a MIP port and checks for an LTR
(Link Trace Response). If an MIP or MEP port does not respond to the source MEP, this
may indicate a fault. Administrators can take further action to check the fault and resume
services according to the line connectivity status report.
An example is shown next. A user cannot access the Internet. To check the problem, the
administrator starts the link trace test from A which is an MEP port to B which is also an MEP
port. Each aggregation MIP port between aggregated devices responds to the LTM packets and
also forwards them to the next port. A fault occurs at port C. A discovers the fault since it only
gets the LTR packets from the ports before port C.
show ethernet cfm local stack mep Displays the specified MEP’s MEP-CCM database E 13
<mep-id> ma <ma-index> md <md- information. Each MEP maintains an MEP CCM
index> mep-ccmdb [remote-mep <mep- database which stores information about remote MEPs in
id>] the MA when receiving CCMs.
show ethernet cfm local stack mip Displays a list of the MIP(s). E 13
show ethernet cfm local stack mip Displays the MIP-CCM database. E 13
mip-ccmdb
show ethernet cfm remote Displays a list of MA(s), MEP(s) and the remote MEP(s) E 13
under the configured MD(s).
show ethernet cfm virtual-mac Displays all virtual MAC addresses. E 13
show ethernet cfm virtual-mac port Displays the MAC address(es) of the specified port(s). E 13
<port-list>
sysname# config
sysname(config)# ethernet cfm md 1 format string name MD1 level 1
sysname(config)# ethernet cfm ma 2 format string name MA2 md 1 primary-
vlan 2
sysname(config-ma)# exit
sysname(config)# exit
sysname# write memory
This example deletes MA2 (with MA index 2) from MD1 (with MD index 1).
sysname# config
sysname(config)# no ethernet cfm ma 2 md 1
sysname(config)# exit
sysname# write mem
This example creates MA3 (with MA index 3 and VLAN ID 123) under MD1, and associates
port 1 as an MEP port with MEP ID 301 in the specified CFM domain. This also sets MHF
(MIP half function) to default to have the Switch automatically create MIPs for this MA and
on the ports belonging to this MA's VLAN when there are no lower configured MD levels or
there is a MEP at the next lower configured MD level on the port. This also sets a remote MEP
in MA3.
sysname# config
sysname(config)# ethernet cfm ma 3 format string name MA3 md 1 primary-vlan
123
sysname(config-ma)# mep 301 interface port-channel 1 direction up priority 2
sysname(config-ma)# mep 301 interface port-channel 1 direction up priority 2
cc-enable
sysname(config-ma)# mhf-creation default
sysname(config-ma)# remote-mep 117
sysname(config-ma)# exit
sysname(config)# exit
sysname# write mem
This example lists all CFM domains. In this example, only one MD (MD1) is configured. The
MA3 with the associated MEP port 1 is under this MD1.
This example starts a loopback test and displays the test result on the console.
This example displays all neighbors’ MEP port information in the MIP-CCM databases.
This example assigns a virtual MAC address to port 3 and displays the MAC addresses of the
ports 2 ~ 4. The assigned virtual MAC address should be unique in both the Switch and the
network to which it belongs.
sysname# config
sysname(config)# interface port-channel 3
sysname(config-interface)# ethernet cfm virtual-mac 00:19:cb:12:34:56
sysname(config-interface)# exit
sysname(config)# exit
sysname# show ethernet cfm virtual-mac port 2-4
Virtual MACPort MAC
---- -----------------
2 00:19:cb:00:00:02
3 00:19:cb:12:34:56
4 00:19:cb:00:00:02
sysname#
This example sets the Switch to carry its host name and management IP address 192.168.100.1
in CFM packets.
sysname# config
sysname(config)# ethernet cfm management-address-domain ip 192.168.100.1
This example shows remote MEP database information. The remote MEP has been configured
to carry its host name and a specified IP address in CFM packets.
The following table shows some other common Ethernet types and the corresponding protocol
number.
Table 32 Common Ethernet Types and Protocol Number
ETHERNET TYPE PROTOCOL NUMBER
IP ETHII 0800
X.75 Internet 0801
NBS Internet 0802
ECMA Internet 0803
Chaosnet 0804
X.25 Level 3 0805
XNS Compat 0807
Banyan Systems 0BAD
BBN Simnet 5208
IBM SNA 80D5
AppleTalk AARP 80F3
In an IPv4 packet header, the “Protocol” field identifies the next level protocol. The following
table shows some common IPv4 protocol types and the corresponding protocol number. Refer
to http://www.iana.org/assignments/protocol-numbers for a complete list.
Table 33 Common IPv4Protocol Types and Protocol Numbers
PROTOCOL TYPE PROTOCOL NUMBER
ICMP 1
TCP 6
UDP 17
EGP 8
L2TP 115
sysname# config
sysname(config)# classifier VLAN3 vlan 3
sysname(config)# exit
sysname# show classifier
Index Active Name Rule
1 Yes VLAN3 VLAN = 3;
This example creates a classifier (Class1) for packets which have a source MAC address of
11:22:33:45:67:89 and are received on port 1. You can then use the policy command and the
name Class1 to apply policy rules to this traffic flow. See the policy example in Chapter 54 on
page 235.
sysname# config
sysname(config)# classifier Class1 source-mac 11:22:33:45:67:89 source-port
1
sysname(config)# exit
sysname# show classifier
Index Active Name Rule
1 Yes Class1 SrcMac = 11:22:33:45:67:89; S...
sysname# configure
sysname(config)# cluster 1
sysname(config)# cluster name CManage
sysname(config)# exit
sysname# show cluster candidates
Clustering Candidates:
Index Candidates(MAC/HostName/Model)
0 00:13:49:00:00:01/ES-2108PWR/ES-2108PWR
1 00:13:49:00:00:02/GS-3012/GS-3012
2 00:19:cb:00:00:02/ES-3124/ES-3124
sysname# configure
sysname(config)# cluster member 00:13:49:00:00:01 password 1234
sysname(config)# cluster member 00:13:49:00:00:02 password 1234
sysname(config)# exit
sysname# show cluster member
Clustering member status:
Index MACAddr Name Status
1 00:13:49:00:00:01 ES-2108PWR Online
2 00:13:49:00:00:02 GS-3012 Online
This example logs in to the CLI of member 00:13:49:00:00:01, looks at the current firmware
version on the member Switch, logs out of the member’s CLI, and returns to the CLI of the
manager.
sysname# configure
sysname(config)# cluster rcommand 00:13:49:00:00:01
Connected to 127.0.0.2
Escape character is '^]'.
Password: ****
Copyright (c) 1994 - 2007 ZyXEL Communications Corp.
Closed
sysname(config)#
sysname# configure
sysname(config)# time date 06/04/2007
sysname(config)# time timezone -600
sysname(config)# time daylight-saving-time
sysname(config)# time daylight-saving-time start-date second Sunday
--> March 2
sysname(config)# time daylight-saving-time end-date first Sunday
--> November 2
sysname(config)# time 13:24:00
sysname(config)# exit
sysname# show time
Current Time 13:24:03 (UTC-05:00 DST)
Current Date 2007-06-04
Time Configuration
-----------------------------
Time Zone :UTC -600
Time Sync Mode :USE_DAYTIME
Time Server IP Address :172.16.37.10
14.1 Overview
A traditional Ethernet network is best-effort, that is, frames may be dropped due to network
congestion. FCoE (Fiber Channel over Ethernet) transparently encapsulates fiber channel
traffic into Ethernet, so that you don’t need separate fiber channel and Ethernet switches.
Data Center Bridging (DCB) enhances Ethernet technology to adapt to the FCoE. It supports
lossless Ethernet traffic (no frames discarded when there is network congestion) and can
allocate bandwidth for different traffic classes, based on IEEE802.1p priority with a
guaranteed minimum bandwidth. LAN traffic (large number of flows and not latency-
sensitive), SAN traffic (Storage Area Network, large packet sizes and requires lossless
performance), and IPC traffic (Inter-Process Communication, latency-sensitive messages) can
share the same physical connection while still having their own priority and guaranteed
minimum bandwidth.
You should configure DCB on any port that has both Ethernet and fiber channel traffic.
• Application priority is used to globally assign a priority to all FCoE traffic on the Switch.
• DCBX (Data Center Bridging capability eXchange, IEEE 802.1Qaz -2011) uses LLDP
(Link Layer Discovery Protocol) to advertize PFC, ETS and application priority
information between switches. PFC information should be consistent between connected
switches, so PFC can be configured automatically using DCBX.
The following table describes user-input values available in multiple commands for this
feature.
Table 41 dcb User-input Values
COMMAND DESCRIPTION
<priority-list> Possible values range from 0 to 7.
<port-list> Possible values range from 1 to the number of ports on your Switch.
<id> Possible values for traffic class ID range from 1 to 100. 0 is a default traffic
class and cannot be modified or deleted.
<tc-idN> The traffic class ID for priority N (0 to 7). The traffic class ID range is from 1 to
100.
<name> Up to 32 printable ASCII characters. Names with spaces must be enclosed in
quotes. For example, “My Class”.
<weight> Possible values range from 1 to 127 for unicast or multicast weights.
Possible values range from 1 to 100 for WFQ traffic class weight.
14.2.1 PFC
PFC should be configured the same on connected switch ports. If DCBX is used, then one
switch port must be configured to accept network configuration from the peer switch port
(auto). If both switch ports are configured to accept configuration (auto on both switch
ports), then the configuration of the switch port with the lowest MAC address hex value sum is
used.
The following table lists the commands for this feature.
Table 42 priority-flow-control Command Summary
COMMAND DESCRIPTION M P
interface port-channel <port-list> Enters config-interface mode for the specified port(s). C 13
priority-flow-control Enables PFC on the specified port(s). C 13
no priority-flow-control Disables PFC on the specified port(s). C 13
priority-flow-control auto Sets the port to accept PFC configuration from the C 13
connected Switch port.
priority-flow-control priority Sets the priority value(s) on the specified port(s). C 13
<priority-list>
no priority-flow-control Clears the priority value(s) on the specified port(s). C 13
priority
switchA# configure
switchA(config)# interface port-channel 1
switchA(config-interface)# priority-flow-control auto
switchA(config-interface)# priority-flow-control priority 2
switchB# configure
switchB(config)# interface port-channel 1
switchB(config-interface)# priority-flow-control
switchB(config-interface)# priority-flow-control priority 3-5
Use the show command to see the PFC configuration. Operation-Priority shows whether
switch A is using switch B’s configured priorities or not.
In the following example, Switch A is using Switch B’s configured priorities.
In the following example, Switch A is NOT using Switch B’s configured priorities.
This is an example showing how many pause frames of certain priorities were temporarily
stopped (transmitted or received) on port 1.
sysname#
14.2.3 ETS
An IEEE 802.1p priority is assigned to a traffic class with guaranteed minimum bandwidth. A
traffic class can use SP (Strict Priority) or WFQ (Weighted Fair Queue) queuing method.
Available link bandwidth is reserved first for SP traffic. The guaranteed minimum bandwidth
for non-SP traffic (WFQ) is its weight value by remaining available bandwidth. If a non-strict-
priority-traffic-class does not consume its allocated bandwidth, other non-strict-priority-
traffic-classes can share the unused bandwidth according to the weight ratio.
The guaranteed minimum bandwidth for both SAN and LAN traffic is 2.5Gbps with a link
bandwidth of 10Gbps.
Table 45 ETS Example Traffic Bandwidths
INCOMING TRAFFIC GUARANTEED OUTGOING TRAFFIC
NAME BANDWIDTH (GBPS) MINIMUM BANDWIDTH BANDWIDTH (GBPS)
Default 5 5 (SP) 5
SAN 3 (10-5) * (50/(50+50)) = 2.5
2.5
LAN 4 (10-5) * (50/(50+50)) = 2.5
2.5
Create and name traffic class IDs, with weights for the non-SP traffic type.
sysname# configure
sysname(config)# traffic-class 1 scheduler ets 50 name LAN
sysname(config)# traffic-class 2 scheduler ets 50 name SAN
Next, configure a port for traffic class(es) and bind priorities to traffic classes on a port. In the
next example, we configure port 1 and bind priorities 0, 1 and 2 to traffic class 2 (LAN), 3, 4,
5 and 6 to class 1 (SAN) and 7 to class 0, the default traffic class.
Table 46 ETS Example Priority Traffic Class ID Mapping
PRIORITY TRAFFIC CLASS ID NAME
0 2 LAN
1 2 LAN
2 2 LAN
3 1 SAN
4 1 SAN
5 1 SAN
6 1 SAN
7 0 Default
switchA# configure
switchA(config)# lldp dcbx application ether-type fcoe priority 3
Application priority can then be used in conjunction with ETS and PFC as shown in the
following examples.
This is an application priority command example with PFC.
sysname# configure
sysname(config)# traffic-class 3 scheduler ets 40 name ethernet
sysname (config)# traffic-class 4 scheduler ets 60 name fcoe
sysname (config)# interface port-channel 6
sysname (config-interface)# ets
sysname (config-interface)# ets traffic-class binding 0 0 0 4 3 3 0 0
sysname (config-interface)# unicast-nonunicast-weight 100 100
14.2.7 DCBX
DCBX uses LLDP (Link Layer Discovery Protocol) to exchange PFC, ETS and application
priority information between switches. PFC information should be consistent between
switches, so this can be configured automatically using DCBX.
See Chapter 37 on page 179 for more information on LLDP.
In order for switches to exchange information, they must send their type-length values (TLVs)
in order to be able to read each other’s information.
The following table lists the commands for this feature.
Table 49 dcbx Command Summary
COMMAND DESCRIPTION M P
interface port-channel <port-list> Enters config-interface mode for the specified port(s). C 13
lldp org-specific-tlv dot1 Enables the sending of ETS TLVs on the specified C 13
dcbx-ets-configuration port(s).
lldp org-specific-tlv dot1 Enables the sending of PFC TLVs on the specified C 13
dcbx-pfc-configuration port(s).
lldp org-specific-tlv dot1 Enables the sending of application priority TLVs on the C 13
dcbx-application-priority specified port(s).
sysname# configure
sysname(config)# lldp
interface port-channel 2
sysname(config-interface)# lldp admin-status tx-rx
sysname(config-interface)# lldp org-specific-tlv dot1 dcbx-ets-
configuration
sysname(config-interface)# lldp org-specific-tlv dot1 dcbx-pfc-
configuration
sysname(config-interface)# lldp org-specific-tlv dot1 dcbx-application-
priority
sysname(config-interface)#exit
sysname(config)# exit
sysname#
DHCP Server:
192.168.1.100
VLAN1 VLAN2
This example shows how to configure the Switch for this configuration. DHCP relay agent
information option 82 is also enabled.
sysname# configure
sysname(config)# dhcp smart-relay
sysname(config)# dhcp smart-relay helper-address 192.168.1.100
sysname(config)# dhcp smart-relay option
sysname(config)# exit
sysname# show dhcp smart-relay
DHCP Relay Agent Configuration
Active: Yes
Remote DHCP Server 1:192.168.1.100
Remote DHCP Server 2: 0.0.0.0
Remote DHCP Server 3: 0.0.0.0
Option82: Enable Option82Inf: Disable
In this example, there are two VLANs (VIDs 1 and 2) in a campus network. Two DHCP
servers are installed to serve each VLAN. The Switch forwards DHCP requests from the
dormitory rooms (VLAN 1) to the DHCP server with IP address 192.168.1.100. DHCP
requests from the academic buildings (VLAN 2) are sent to the other DHCP server with IP
address 172.16.10.100.
DHCP: 192.168.1.100
VLAN 1
This example shows how to configure these DHCP servers. The VLANs are already
configured.
sysname# configure
sysname(config)# dhcp relay 1 helper-address 192.168.1.100
sysname(config)# dhcp relay 2 helper-address 172.16.10.100
sysname(config)# exit
In this example, the Switch is a DHCP server for clients on VLAN 1 and VLAN 2. The DHCP
clients in VLAN 1 are assigned IP addresses in the range 192.168.1.100 to 192.168.1.200 and
clients on VLAN 2 are assigned IP addresses in the range 172.16.1.30 to 172.16.1.130.
VLAN 1 VLAN 2
This example shows how to configure the DHCP server for VLAN 1 with the configuration
shown in Figure 5 on page 82. It also provides the DHCP clients with the IP address of the
default gateway and the DNS server.
sysname# configure
sysname(config)# dhcp server 1 starting-address 192.168.1.100
255.255.255.0 size-of-client-ip-pool 100 default-gateway 192.168.1.1
primary-dns 192.168.5.1
A B
172.16.1.254
10.10.10.254
C D E
clear cpu-protection interface Resets the “Total Drop” counters for the specified port(s) to E 13
port-channel <port-list> cause zero (0). You can see the counter using the show cpu-
<ARP|BPDU|IGMP> protection command. The “Total Drops” means the
number of ARP, BPDU or IGMP packets that have been
dropped due to the Error Disable feature in rate-
limitation mode.
reset cpu-protection interface Sets the specified port(s) to handle all ARP, BPDU or IGMP E 13
port-channel <port-list> cause packets in stead of ignoring them, if the port(s) are in
<ARP|BPDU|IGMP> inactive-reason mode (set by using the errdisable
detet cause command).
show cpu-protection interface Shows the CPU Protection settings and the number of ARP, E 13
port-channel <port-list> BPDU and/or IGMP packets that has been dropped by the
Error Disable feature for the specified port(s).
systemname# config
systemname(config)# interface port-channel 7
systemname(config-interface)# cpu-protection cause ARP rate-limit 100
systemname(config-interface)# exit
systemname(config)# errdisable detect cause ARP
systemname(config)# errdisable detect cause ARP mode inactive-port
systemname(config)# exit
systemname# show cpu-protection interface port-channel 7
Port : 7
This example enables the disabled port recovery function and the recovery timer for the
loopguard feature on the Switch. If a port is shut down due to the specified reason, the Switch
activates the port 300 seconds (the default value) later. This example also shows the number of
the disabled port(s) and the time left before the port(s) becomes active.
sysname# configure
sysname(config)# errdisable recovery
sysname(config)# errdisable recovery cause loopguard
sysname(config)# exit
sysname# show errdisable recovery
Errdisable Recovery Status:Enable
interface port-channel <port- Enters config-interface mode for the specified port(s). C 13
list>
ethernet oam Enables Ethernet OAM on the port(s). C 13
no ethernet oam Disables Ethernet OAM on the port(s). C 13
ethernet oam mode Specifies the OAM mode on the ports. C 13
<active|passive> active: Allows the port to issue and respond to Ethernet
OAM commands.
passive: Allows the port to respond to Ethernet OAM
commands.
ethernet oam remote-loopback Sets the Switch to ignore loopback commands received on C 13
ignore-rx the ports.
ethernet oam remote-loopback Enables the remote loopback feature on the ports. C 13
supported
no ethernet oam remote- Sets the Switch to process loopback commands received on C 13
loopback ignore-rx the ports.
no ethernet oam remote- Disables the remote loopback feature on the ports. C 13
loopback supported
no ethernet oam mode Resets the OAM mode to the default value. C 13
sysname# configure
sysname(config)# ethernet oam
sysname(config)# interface port-channel 7
sysname(config-interface)# ethernet oam
sysname(config-interface)# ethernet oam mode active
sysname(config-interface)# exit
sysname(config)# exit
Operational status:
Link status : Down
Info. revision : 3
Parser state : Forward
Discovery state : Active Send Local
Local Remote
------------- -----------------------------------------
Port Mode MAC Addr OUI Mode Config
----- ------- ----------------- ------ ------- --------
1 Active
sysname# configure
sysname(config)# external-alarm 1 name dooropen
sysname(config)# exit
sysname# show external-alarm
External Alarm 1
External Alarm 2
External Alarm 3
External Alarm 4
GARP Timer
------------------------
Join Timer :200
Leave Timer :600
Leave All Timer :10000
sysname# configure
sysname(config)# garp join 300 leave 800 leaveall 11000
sysname(config)# exit
sysname# show garp
GARP Timer
------------------------
Join Timer :300
Leave Timer :800
Leave All Timer :11000
Not all Switches supports Green Ethernet completely. Some may only support
EEE.
EEE
• Active displays when EEE is enabled and the EEE port is up
• Inactive displays when EEE is enabled but the EEE port is down or the device
connected to this port does not support EEE
• Unsupported means the Switch cannot display the status.
• - means EEE is not enabled
Short reach
• Normal means short reach has not reduced the power on this link
• Low power means short reach has reduced the power on this link
• Unsupported means the Switch cannot display the status.
• - means short reach is not enabled
sysname#
The following example shows how to configure short reach if the Switch supports short reach
per port
sysname# configure
sysname(config)# green-ethernet short-reach
sysname# configure
sysname(config)# interface port-channel 1-4
sysname(config-interface)# green-ethernet short-reach
The following example shows the display for short reach if the Switch supports short reach per
port and showing the status
GVRP Support
-----------------------
gvrpEnable = YES
gvrpPortEnable:
sysname# configure
sysname(config)# interface port-channel 1-5
sysname(config-interface)# no gvrp
sysname(config-interface)# exit
sysname(config)# exit
113
MVR Commands (219)
114
C HA PT E R 26
HTTPS Server Commands
Use these commands to configure the HTTPS server on the Switch.
Statistics:
Total connects : 0
Current connects : 0
Connects that finished: 0
Renegotiate requested : 0
Session cache items : 0
Session cache hits : 0
Session cache misses : 0
Session cache timeouts: 0
Sessions:
Remote IP Port Local IP Port SSL bytes Sock bytes
port-access-authenticator Sets the number of seconds the Switch waits for client's C 13
<port-list> supp-timeout <30- response to the challenge request before sending a request
65535> again.
port-access-authenticator Sets the number of seconds the Switch waits before re- C 13
<port-list> tx-period <1-65535> sending an identity request to clients on the listed ports.
port-access-authenticator Sets a subscriber to periodically re-enter his or her username C 13
<port-list> reauthenticate and password to stay connected to a specified port.
port-access-authenticator Specifies how often (in seconds) a client has to re-enter the C 13
<port-list> reauth-period <1- username and password to stay connected to the specified
65535> port(s).
sysname(config)# no port-access-authenticator
sysname(config)# no port-access-authenticator 1,3-5 reauthenticate
sysname(config)# no port-access-authenticator 1,6-7
• Configures the IP interface 172.16.1.1 with subnet mask 255.255.255.0 to route IGMP
version 3 packets.
show interfaces config <port- Displays the IGMP leave mode of the specified port(s). E 3
list> igmp-snooping leave-mode
show interfaces config <port- Displays the IGMP querier mode of the specified port(s). E 3
list> igmp-snooping query-mode
interface port-channel <port- Enters config-interface mode for the specified port(s). C 13
list>
igmp-snooping fast-leave- Set the IGMP snooping fast leave timeout (in miliseconds) the C 13
timeout <200-6348800> Switch uses to update the forwarding table for the port(s).
This defines how many seconds the Switch waits for an IGMP
report before removing an IGMP snooping membership entry
when an IGMP leave message is received on this port from a
host.
igmp-snooping filtering Assigns the specified IGMP filtering profile to the port(s). If C 13
profile <name> IGMP filtering is enabled on the Switch, the port(s) can only
join the multicast groups in the specified profile.
igmp-snooping group-limited Enables the group limiting feature for IGMP snooping. You C 13
must enable IGMP snooping as well.
igmp-snooping group-limited Sets how the Switch deals with the IGMP reports when the C 13
action <deny|replace> maximum number of the IGMP groups a port can join is
reached.
deny: The Switch drops any new IGMP join report received
on this port until an existing multicast forwarding table entry is
aged out.
replace: The Switch replaces an existing entry in the
multicast forwarding table with the new IGMP report(s)
received on this port.
igmp-snooping group-limited Sets the maximum number of multicast groups allowed. C 13
number <number> number: 0-255
igmp-snooping leave-mode Sets the Switch to remove an IGMP snooping membership C 13
<normal|immediate|fast> entry immediately (immediate) or wait for an IGMP report
before the normal (normal) or fast (fast) leave timeout
when an IGMP leave message is received on this port from a
host.
igmp-snooping leave-timeout Set the IGMP snooping normal leave timeout (in miliseconds) C 13
<200-6348800> the Switch uses to update the forwarding table for the port(s).
This defines how many seconds the Switch waits for an IGMP
report before removing an IGMP snooping membership entry
when an IGMP leave message is received on this port from a
host.
sysname(config)# igmp-snooping
sysname(config)# igmp-snooping host-timeout 30
sysname(config)# igmp-snooping unknown-multicast-frame drop
sysname# configure
sysname(config)# igmp-snooping
sysname(config)# interface port-channel 1
sysname(config-interface)# igmp-snooping group-limited
sysname(config-interface)# igmp-snooping group-limited number 5
sysname(config-interface)# exit
sysname(config)# exit
sysname# show interfaces config 1 igmp-snooping group-limited
Port Enable Max Multicast Group
1 YES 5
sysname# configure
sysname(config)# igmp-snooping filtering
sysname(config)# igmp-snooping filtering profile example1 start-address
--> 224.255.255.0 end-address 225.255.255.255
sysname(config)# interface port-channel 1-4
sysname(config-interface)# igmp-snooping filtering profile example1
sysname(config-interface)# exit
sysname(config)# exit
sysname# configure
sysname(config)# igmp-filtering
sysname(config)# igmp-filtering profile example1 start-address
--> 224.255.255.0 end-address 225.255.255.255
sysname(config)# interface port-channel 1-4
sysname(config-interface)# igmp-filtering profile example1
sysname(config-interface)# exit
sysname(config)# exit
sysname# config
sysname(config)# interface route-domain 192.168.1.1/24
sysname(config-if)#
This example shows the UDP statistics and listener ports. See RFC 1213 for more information.
ip source binding arp-freeze Create static bindings from previously learned ARP entries C 13
vlan <vlan-list> containing the specified VLAN ID and add them in the IP
source guard static binding table.
ip source binding <mac-addr> Creates a static binding for ARP inspection. C 13
vlan <vlan-id> <ip> [interface
port-channel <interface-id>]
no ip source binding <mac-addr> Removes the specified static binding. C 13
vlan <vlan-id>
Interface ID
In IPv6, an interface ID is a 64-bit identifier. It identifies a physical interface (for example, an
Ethernet port) or a virtual interface (for example, the management IP address for a VLAN).
One interface should have a unique interface ID.
Link-local Address
A link-local address uniquely identifies a device on the local network (the LAN). It is similar
to a “private IP address” in IPv4. You can have the same link-local address on multiple
interfaces on a device. A link-local unicast address has a predefined prefix of fe80::/10. The
link-local unicast address format is as follows.
Table 91 Link-local Unicast Address Format
1111 1110 10 0 Interface ID
10 bits 54 bits 64 bits
Global Address
A global address uniquely identifies a device on the Internet. It is similar to a “public IP
address” in IPv4. The global address format as follows.
Table 92 Global Address Format
001 Global ID Subnet ID Interface ID
3 bits 45 bits 16 bits 64 bits
The global ID is the network identifier or prefix of the address and is used for routing. This
may be assigned by service providers.
The subnet ID is a number that identifies the subnet of a site.
Multicast Addresse
In IPv6, multicast addresses provide the same functionality as IPv4 broadcast addresses.
Broadcasting is not supported in IPv6. A multicast address allows a host to send packets to all
hosts in a multicast group.
Multicast scope allows you to determine the size of the multicast group. A multicast address
has a predefined prefix of ff00::/8. The following table describes some of the predefined
multicast addresses.
The following table describes the multicast addresses which are reserved and can not be
assigned to a multicast group.
MULTICAST ADDRESS
FF00:0:0:0:0:0:0:0
FF01:0:0:0:0:0:0:0
FF02:0:0:0:0:0:0:0
FF03:0:0:0:0:0:0:0
FF04:0:0:0:0:0:0:0
FF05:0:0:0:0:0:0:0
FF06:0:0:0:0:0:0:0
FF07:0:0:0:0:0:0:0
FF08:0:0:0:0:0:0:0
FF09:0:0:0:0:0:0:0
FF0A:0:0:0:0:0:0:0
FF0B:0:0:0:0:0:0:0
FF0C:0:0:0:0:0:0:0
FF0D:0:0:0:0:0:0:0
FF0E:0:0:0:0:0:0:0
FF0F:0:0:0:0:0:0:0
Loopback
A loopback address (0:0:0:0:0:0:0:1 or ::1) allows a host to send packets to itself. It is similar
to “127.0.0.1” in IPv4.
Unspecified
An unspecified address (0:0:0:0:0:0:0:0 or ::) is used as the source address when a device does
not have its own address. It is similiar to “0.0.0.0” in IPv4.
EUI-64
The EUI-64 (Extended Unique Identifier) defined by the IEEE (Institute of Electrical and
Electronics Engineers) is an interface ID format designed to adapt with IPv6. It is derived from
the 48-bit (6-byte) Ethernet MAC address as shown next. EUI-64 inserts the hex digits fffe
between the third and fourth bytes of the MAC address and complements the seventh bit of the
first byte of the MAC address. See the following example.
MAC 00 : 13 : 49 : 12 : 34 : 56
EUI-64 02 : 13 : 49 : FF : FE : 12 : 34 : 56
Stateless Autoconfiguration
With stateless autoconfiguration in IPv6, addresses can be uniquely and automatically
generated. Unlike DHCPv6 (Dynamic Host Configuration Protocol version six) which is used
in IPv6 stateful autoconfiguration, the owner and status of addresses don’t need to be
maintained by a DHCP server. Every IPv6 device is able to generate its own and unique IP
address automatically when IPv6 is initiated on its interface. It combines the prefix and the
interface ID (generated from its own Ethernet MAC address, see Interface ID and EUI-64) to
form a complete IPv6 address.
When IPv6 is enabled on a device, its interface automatically generates a link-local address
(beginning with fe80).
When the interface is connected to a network with a router and the ipv6 address
autoconfig command is issued on the Switch, it generates 1another address which
combines its interface ID and global and subnet information advertised from the router. This is
a routable global IP address.
DHCPv6
The Dynamic Host Configuration Protocol for IPv6 (DHCPv6, RFC 3315) is a server-client
protocol that allows a DHCP server to assign and pass IPv6 network addresses, prefixes and
other configuration information to DHCP clients. DHCPv6 servers and clients exchange
DHCP messages using UDP.
Each DHCP client and server has a unique DHCP Unique IDentifier (DUID), which is used
for identification when they are exchanging DHCPv6 messages. The DUID is generated from
the MAC address, time, vendor assigned ID and/or the vendor's private enterprise number
registered with the IANA. It should not change over time even after you reboot the device.
Identity Association
An Identity Association (IA) is a collection of addresses assigned to a DHCP client, through
which the server and client can manage a set of related IP addresses. Each IA must be
associated with exactly one interface. The DHCP client uses the IA assigned to an interface to
obtain configuration from a DHCP server for that interface. Each IA consists of a unique IAID
and associated IP information.
The IA type is the type of address in the IA. Each IA holds one type of address. IA_NA means
an identity association for non-temporary addresses and IA_TA is an identity association for
temporary addresses. An IA_NA option contains the T1 and T2 fields, but an IA_TA option
does not. The DHCPv6 server uses T1 and T2 to control the time at which the client contacts
with the server to extend the lifetimes on any addresses in the IA_NA before the lifetimes
expire. After T1, the client sends the server (S1) (from which the addresses in the IA_NA were
obtained) a Renew message. If the time T2 is reached and the server does not respond, the
client sends a Rebind message to any available server (S2). For an IA_TA, the client may send
a Renew or Rebind message at the client's discretion.
T2
T1
ICMPv6
Internet Control Message Protocol for IPv6 (ICMPv6 or ICMP for IPv6) is defined in RFC
4443. ICMPv6 has a preceding Next Header value of 58, which is different from the value
used to identify ICMP for IPv4. ICMPv6 is an integral part of IPv6. IPv6 nodes use ICMPv6
to report errors encountered in packet processing and perform other diagnostic functions, such
as "ping".
IPv6 Cache
An IPv6 host is required to have a neighbor cache, destination cache, prefix list and default
router list. The Switch maintains and updates its IPv6 caches constantly using the information
from response messages. In IPv6, the Switch configures a link-local address automatically,
and then sends a neighbor solicitation message to check if the address is unique. If there is an
address to be resolved or verified, the Switch also sends out a neighbor solicitation message.
When the Switch receives a neighbor advertisement in response, it stores the neighbor’s link-
layer address in the neighbor cache. When the Switch uses a router solicitation message to
query for a router and receives a router advertisement message, it adds the router’s information
to the neighbor cache, prefix list and destination cache. The Switch creates an entry in the
default router list cache if the router can be used as a default router.
When the Switch needs to send a packet, it first consults the destination cache to determine the
next hop. If there is no matching entry in the destination cache, the Switch uses the prefix list
to determine whether the destination address is on-link and can be reached directly without
passing through a router. If the address is onlink, the address is considered as the next hop.
Otherwise, the Switch determines the next-hop from the default router list or routing table.
Once the next hop IP address is known, the Switch looks into the neighbor cache to get the
link-layer address and sends the packet when the neighbor is reachable. If the Switch cannot
find an entry in the neighbor cache or the state for the neighbor is not reachable, it starts the
address resolution process. This helps reduce the number of IPv6 solicitation and
advertisement messages.
MLD Messages
A multicast router or switch periodically sends general queries to MLD hosts to update the
multicast forwarding table. When an MLD host wants to join a multicast group, it sends an
MLD Report message for that address.
An MLD Done message is equivalent to an IGMP Leave message. When an MLD host wants
to leave a multicast group, it can send a Done message to the router or switch. If the leave
mode is not set to immediate, the router or switch sends a group-specific query to the port
on which the Done message is received to determine if other devices connected to this port
should remain in the group.
Proxy
Snooping
USP
DSP
MLD Snooping-Proxy
MLD snooping-proxy is a ZyXEL-proprietary feature. IPv6 MLD proxy allows only one
upstream interface on a switch, while MLD snooping-proxy supports more than one upstream
port on a switch. The upstream port in MLD snooping-proxy can report group changes to a
connected multicast router and forward MLD messages to other upstream ports. This helps
especially when you want to have a network that uses STP to provide backup links between
switches and also performs MLD snooping and proxy functions. MLD snooping-proxy, like
MLD proxy, can minimize MLD control messages and allow better network performance.
In MLD snooping-proxy, if one upstream port is learned via snooping, all other upstream ports
on the same device will be added to the same group. If one upstream port requests to leave a
group, all other upstream ports on the same device will also be removed from the group.
In the following MLD snooping-proxy example, all connected upstream ports (1 ~7) are
treated as one interface. The connection between ports 8 and 9 is blocked by STP to break the
loop. If there is one query from a router (X) or MLD Done or Report message from any
upstream port, it will be broadcast to all connected upstream ports.
X
Query
1
2
9
3 8
4 7
Report
5 6
Done
ipv6 address dhcp client Sets the Switch to obtain DNS server IPv6 addresses or a C 13
option <[dns][domain-list]> list of domain names from the DHCP server.
no ipv6 Disables IPv6 in this VLAN. C 13
no ipv6 address <ipv6- Removes a specified static global address. C 13
address>/<prefix>
no ipv6 address <ipv6- Removes a specified static global address whose C 13
address>/<prefix> eui-64 interface ID was generated using the EUI-64 format.
no ipv6 address <ipv6- Removes a specified static link-local address. C 13
address>/<prefix> link-local
no ipv6 address autoconfig Disables IPv6 address autoconfiguration in this VLAN. C 13
no ipv6 address default- Removes the default gateway address for this VLAN. C 13
gateway
no ipv6 address dhcp client Disables the DHCP client feature in this VLAN. C 13
no ipv6 address dhcp client sets the Switch to not include a Rapid Commit option in its C 13
[rapid-commit] DHCPv6 Solicit messag for this VLAN.
no ipv6 address dhcp client Sets the Switch to not obtain the DNS server information C 13
option from the DHCP server.
no ipv6 address dhcp client Sets the Switch to not obtain DNS server IPv6 addresses C 13
option <[dns][domain-list]> or a list of domain names from the DHCP server.
restart ipv6 dhcp client vlan <1- Sets the Switch to send a Release message for the E 13
4094> assigned IPv6 address to the DHCP server and start
DHCP message exchange again.
show ipv6 Displays IPv6 settings in all VLANs on the Switch. E 3
ipv6 mld snooping-proxy vlan Sets the fast leave timeout (in miliseconds) for the C 13
<vlan-id> downstream interface specified downstream port(s).
port-channel <port-list> fast- This defines how many seconds the Switch waits for an
leave-timeout <2-16775168> MLD report before removing an MLD snooping
membership entry (learned on a downstream port) when
an MLD Done message is received on this port from a
host.
ipv6 mld snooping-proxy vlan Set the MLD snooping normal leave timeout (in C 13
<vlan-id> downstream interface miliseconds) the Switch uses to update the forwarding
port-channel <port-list> leave- table for the specified downstream port(s).
timeout <2-16775168> This defines how many seconds the Switch waits for an
MLD report before removing an MLD snooping
membership entry (learned on a downstream port) when
an MLD Done message is received on this port from a
host.
ipv6 mld snooping-proxy vlan Sets the leave mode for the specified downstream port(s) C 13
<vlan-id> downstream interface in a specified VLAN.
port-channel <port-list> mode This specifies whether Switch removes an MLD snooping
<immediate | normal | fast> membership entry (learned on a downstream port)
immediately (immediate) or wait for an MLD report
before the normal (normal) or fast (fast) leave timeout
when an MLD leave message is received on this port from
a host.
ipv6 mld snooping-proxy vlan Sets the amount of time (in miliseconds) between general C 13
<vlan-id> downstream query- query messages sent by the downstream port.
interval <1000-31744000>
ipv6 mld snooping-proxy vlan Sets the maximum time (in miliseconds) that the Switch C 13
<vlan-id> downstream query-max- waits for a response to a general query message sent by
response-time <1000-25000> the downstream port.
sysname# config
sysname(config)# interface vlan 1
sysname(config-vlan)# ipv6
sysname(config-vlan)# exit
sysname(config)# exit
sysname# show ipv6 vlan 1
VLAN : 1 (VLAN1)
IPv6 is enabled.
MTU is 1500 bytes.
ICMP error messages limited to 10 every 100 milliseconds.
Stateless Address Autoconfiguration is disabled.
Link-Local address is fe80::219:cbff:fe6f:9159 [preferred]
Global unicast address(es):
Joined group address(es):
ff02::2
ff01::1
ff02::1
ff02::1:ff6f:9159
ND DAD is enabled, number of DAD attempts: 1
ND NS-interval is 1000 milliseconds
ND reachable time is 30000 milliseconds
ND router advertised managed config flag is disable
ND router advertised other config flag is disable
ND router advertisements are sent every 200 to 600 seconds
ND router advertisements lifetime 1800 seconds
This example shows how to manually configure two IPv6 addresses (one uses the EUI-64
format, one doesn’t) in VLAN 1, and then display the result. Before using ipv6 address
commands, you have to enable IPv6 in the VLAN and this has the Switch generate a link-local
address for the interface.
There are three addresses created in total for VLAN 1. The address
“2001:db8:c18:1:219:cbff:fe00:1/64” is created with the interface ID “219:cbff:fe00:1“
generated using the EUI-64 format. The address “2001:db8:c18:1::12b/64” is created exactly
the same as what you entered in the command.
sysname# config
sysname(config)# interface vlan 1
sysname(config-vlan)# ipv6
sysname(config-vlan)# ipv6 address 2001:db8:c18:1::127/64 eui-64
sysname(config-vlan)# ipv6 address 2001:db8:c18:1::12b/64
sysname(config-vlan)# exit
sysname(config)# exit
sysname# show ipv6
VLAN : 1 (VLAN1)
IPv6 is enabled.
MTU is 1500 bytes.
ICMP error messages limited to 10 every 100 milliseconds.
Stateless Address Autoconfiguration is disabled.
Link-Local address is fe80::219:cbff:fe00:1 [preferred]
Global unicast address(es):
2001:db8:c18:1::12b/64 [preferred]
2001:db8:c18:1:219:cbff:fe00:1/64 [preferred]
Joined group address(es):
ff02::1:ff00:12b
ff02::2
ff01::1
ff02::1
ff02::1:ff6f:9159
ND DAD is enabled, number of DAD attempts: 1
ND NS-interval is 1000 milliseconds
ND reachable time is 30000 milliseconds
ND router advertised managed config flag is disable
ND router advertised other config flag is disable
ND router advertisements are sent every 200 to 600 seconds
ND router advertisements lifetime 1800 seconds
This example shows the Switch owns (L displays in the T field) two manually configured
(permanent) IP addresses, 2001::1234 and fe80::219:cbff:fe00:1. It also displays a neighbor
fe80::2d0:59ff:feb8:103c in VLAN 1 is reachable from the Switch.
S: reachable(R),stale(S),delay(D),probe(P),invalid(IV),incomplete(I),unknown(?)
T: local(L),dynamic(D),static(S),other(O)
This example sends ping requests to an Ethernet device with IPv6 address
fe80::2d0:59ff:feb8:103c in VLAN 1. The device also responds the pings.
This example configures a static IPv6 route to forward packets with IPv6 prefix 2100:: and
prefix length 64 to the gateway with IPv6 address fe80::219:cbff:fe01:101 in VLAN 1.
sysname# config
sysname(config)# ipv6 route 2100::/64 fe80::219:cbff:fe01:101 vlan 1
sysname(config)# exit
sysname# show ipv6 route
Terminology:
C - Connected, S - Static
Destination/Prefix Length Type
Next Hop Interface
------------------------------------------------------------
2001:db8:c18:1::/64 C
:: VLAN1
2100::/64 S
fe80::219:cbff:fe01:101 VLAN1
sysname#
C:\>ipv6 install
Installing...
Succeeded.
C:\>ipconfig
Windows IP Configuration
IPv6 is installed and enabled by default in Windows Vista. Use the “ipconfig” command to
check your automatic configured IPv6 address as well. You should see at least one IPv6
address available for the interface on your computer.
http://fe80--1234-5678-1s4.ipv6-literal.net.
A global address Use http://[address]
Windows A link-local address For example, http://[fe80--1234-5678-1]
Vista
A global address
This example shows you how to access the Switch using HTTP on Windows XP.
1 Make sure you have enabled IPv6 on your computer (see Section 35.4). Use the
ipconfig command in the command prompt to check the IPv6 address on your
computer. The example uses an interface with address “fe80::2d0:59ff:feb8:103c” to
access the Switch. So its Ethernet interface identifier is %4 and will be used later to
make a ping.
C:\>ipconfig
Windows IP Configuration
2 Check the Switch IPv6 address(es) you want to ping. In this example, there are two IPv6
addresses in VLAN 1. One is a link-local address (fe80::219:cbff:fe00:1/64) and the
other one is a global address (2001::1234/64).
VLAN ID : 1
IPv6 Status : Enable
3 In order to access the Switch through its link-local address, do the address convertion
(See Table 103 on page 171).
3a Use a dash “-” to replace each colon “:” in an IPv6 address. Then the address
becomes:
fe80--219-cbff-fe00-1
3b In the step 1, the Ethernet interface identifier you want to use to connect to the
Switch is “%4”. Replace the percentage character “%” with “s” and then append it to
the address. The address becomes:
fe80--219-cbff-fe00-1s4
3c Append “.ipv6-literal.net” at the end. The address becomes:
fe80--219-cbff-fe00-1s4.ipv6-literal.net
4 Alternatively, you can use the global address to access the Switch. Type http://
[2001::1234] on your browser and the login page appears.
sysname# configure
sysname(config)# l2protocol-tunnel
sysname(config)# l2protocol-tunnel mac 00:10:23:45:67:8e
sysname(config)#
This example enables L2PT for STP, CDP and VTP packets on port 3. It also sets L2PT mode
to access for this port.
This example displays L2PT settings and status on port 3. You can also see how many CDP,
STP, VTP, LACP, PAgP and UDLD packets received on this port are encapsulated,
decapsulated or dropped.
Status : Running
Layer 2 Protocol Tunneling: Enable
Destination MAC Address: 00:10:23:45:67:8e
sysname# configure
sysname(config)# lldp
sysname(config)# interface port-channel 2
sysname(config-interface)# lldp admin-status tx-rx
sysname(config-interface)# lldp basic-tlv management-address
sysname(config-interface)# lldp basic-tlv port-description
sysname(config-interface)# lldp basic-tlv system-description
sysname(config-interface)# exit
sysname(config)# exit
sysname# show lldp config interface port-channel 2
LLDP Port Configuration:
Port AdminStatus Notification BasicTLV Dot1TLV Dot3TLV
2 tx-rx Disable P-D-M -- ----
Basic TLV Flags: (P)Port Description, (N)System Name, (D)System
Description
(C)System Capabilities, (M)Management Address
802.1 TLV Flags: (P)Port & Protocol VLAN ID, (V)Port VLAN ID
802.3 TLV Flags: (L)Link Aggregation, (M)MAC/PHY Configuration/Status
(F)Maximun Frame Size, (P)Power Via MDI
sysname# show lldp config
LLDP Global Configuration:
Active: Yes
Transmit Interval: 30 seconds
Transmit Hold: 4
Transmit Delay: 2 seconds
Reinitialize Delay: 2 seconds
sysname#
sysname#
sysname#
sysname#
This example shows local Switch (the Switch you’re accessing) LLDP information
sysname#
This example shows local Switch (the Switch you’re accessing) LLDP information on a port.
sysname#
This example shows remote Switch (the Switch connected to the port on the Switch you’re
accessing) LLDP information.
sysname# configure
sysname(config)# ip load-sharing
sysname(config)# ip load-sharing sip-dip
sysname(config)#
sysname# configure
sysname(config)# logins username user2 password 1234 privilege 13
sysname(config)# exit
sysname# show logins
Login Username Privilege
1 user2 13
2 0
3 0
4 0
sysname# configure
sysname(config)# loopguard
sysname(config)# interface port-channel 1-3
sysname(config-interface)# loopguard
sysname(config-interface)# exit
sysname(config)# exit
sysname# show loopguard
LoopGuard Status: Enable
You also need to configure a RADIUS server (see Chapter 62 on page 263).
See also Chapter 27 on page 119 for IEEE 802.1x port authentication commands and Chapter
56 on page 241 for port security commands.
sysname(config)# mac-authentication
sysname(config)# mac-authentication nameprefix clientName
sysname(config)# mac-authentication password Lech89
sysname(config)# interface port-channel 1-5
sysname(config-interface)# mac-authentication
sysname(config-interface)# exit
sysname(config)# exit
sysname# show mac-authentication
NamePrefix: clientName
Password: Lech89
Update Time: None
Deny Number: 0
Use the running configuration commands to look at the current MAC filter
settings. See Chapter 66 on page 275.
• Some models allow you to specify a filter rule and discard all packets with the specified
MAC address (source or destination) and VID.
• Other models allow you to choose whether you want to discard traffic originating from the
specified MAC address and VID (src), sent to the specified MAC address (dst) or both.
See Section 44.2 on page 202 and Section 44.3 on page 202 for examples.
Use the mac commands to look at the current mac-forward settings. See
Chapter 42 on page 197.
Use the running configuration commands to look at the current mirror settings.
See Chapter 66 on page 275.
sysname(config)# mirror-port
sysname(config)# mirror-port 3
sysname(config)# interface port-channel 1,4-6
sysname(config-interface)# mirror
sysname(config-interface)# mirror dir egress
This example displays the mirror settings of the Switch after you configured in the example
above.
In this example, we enable MRSTP on ports 21-24. Port 24 is connected to the host while ports
21-23 are connected to another switch.
sysname(config)# configure
sysname(config)# spanning-tree mode MRSTP
sysname(config)# mrstp 1
sysname(config)# mrstp interface 21-24
sysname(config)# no mrstp interface 21-23 edge-port
mstp instance <number> interface port- Sets the priority for the specified ports. Priority C 13
channel <port-list> priority <0-255> decides which port should be disabled when more
than one port forms a loop in a Switch. Ports with a
higher priority numeric value are disabled first.
This example shows the current CIST configuration (MSTP instance 0).
(p)CIST_RRootID: 8000-001349aefb7a
(q)CIST_RRootPathCost: 0
This example adds the Switch to the MST region MSTRegionNorth. MSTRegionNorth is on
revision number 1. In MSTRegionNorth, VLAN 2 is in MST instance 1, and VLAN 3 is in
MST instance 2.
sysname# configure
sysname(config)# mstp
sysname(config)# mstp configuration-name MSTRegionNorth
sysname(config)# mstp revision 1
sysname(config)# mstp instance 1 vlan 2
sysname(config)# mstp instance 2 vlan 3
sysname(config)# exit
sysname(config)# mvr 3
sysname(config-mvr)# name multivlan
sysname(config-mvr)# source-port 2,3,5
sysname(config-mvr)# receiver-port 6-8
sysname(config-mvr)# mode dynamic
sysname(config-mvr)# group ipgroup start-address 224.0.0.1 end-address
--> 224.0.0.255
sysname(config-mvr)# exit
221
Syslog Commands (301)
222
C HA PT E R 51
OSPF Commands
This chapter explains how to use commands to configure the Open Shortest Path First (OSPF)
routing protocol on the Switch.
Area 1
Area 0
Backbone
IP: 172.16.1.1
A
This example enables OSPF on the Switch, sets the router ID to 172.16.1.1, configures an
OSPF area ID as 0.0.0.0 (backbone) and enables simple authentication.
This example configures an OSPF interface for the 172.16.1.1/24 network and specifies to use
simple authentication with the key 1234abcd. The priority for the Switch is also set to 1, as
this router should participate in router elections.
In this example, the Switch (Z) is a redistributor between a RIP network and an OSPF
network. It summarizes 4 routing entries 192.168.8.0/24 ~ 192.168.11.0/24 (learned from RIP
router A) into 192.168.8.0/22 and then sends it to OSPF router B.
Redistributor
192.168.8.0/24
192.168.9.0/24 192.168.8.0/22
192.168.10.0/24
192.168.11.0/24
This example shows you how to enable the redistribution for RIP protocol and then show all
redistribution entries.
sysname# config
sysname(config)# router ospf 172.16.1.1
sysname(config-ospf)# redistribute rip metric-type 1 metric 123
sysname(config-ospf)# exit
sysname(config)# exit
sysname# show ip ospf database
From the example above, the third octet of all the four network IP addresses is 00001000,
00001001, 00001010, 000001011 respectively. The first 4 digits (000010) are the common
part among these IP addresses. So 192.168.8.0/22 can be used to represent all of the 4
networks. The following example shows you how to configure the OSPF summary address
and then show all redistribution entries.
sysname# config
sysname(config)# router ospf 172.16.1.1
sysname(config-ospf)# summary-address 192.168.8.0 255.255.252.0
sysname(config-ospf)# exit
sysname(config)# exit
sysname# show ip ospf database
sysname# configure
sysname(config)# pwr interface 1-4
sysname(config)# pwr usagethreshold 25
sysname(config)# pwr mibtrap
sysname(config)# exit
This example shows the current status and configuration of Power over Ethernet.
GS2200# sh pwr
PoE Mode : Classification mode
Total Power:220.0(W)
Consuming Power:0.0(W)
Allocated Power:0.0 (W)
Remaining Power:220.0(W)
Averaged Junction Temperature: 38 (c), 98 (f).
Port State PD Class Priority Consumption (mW) MaxPower(mW)
---- ------ --- ----- -------- ---------------- ------------
1 Enable off 0 Low 0 0
2 Enable off 0 Low 0 0
3 Enable off 0 Low 0 0
4 Enable off 0 Low 0 0
5 Enable off 0 Low 0 0
6 Enable off 0 Low 0 0
7 Enable off 0 Low 0 0
8 Enable off 0 Low 0 0
9 Enable off 0 Low 0 0
10 Enable off 0 Low 0 0
11 Enable off 0 Low 0 0
12 Enable off 0 Low 0 0
13 Enable off 0 Low 0 0
14 Enable off 0 Low 0 0
15 Enable off 0 Low 0 0
16 Enable off 0 Low 0 0
17 Enable off 0 Low 0 0
18 Enable off 0 Low 0 0
19 Enable off 0 Low 0 0
20 Enable off 0 Low 0 0
21 Enable off 0 Low 0 0
22 Enable off 0 Low 0 0
23 Enable off 0 Low 0 0
24 Enable off 0 Low 0 0
This example creates a policy (Policy1) for the traffic flow identified via classifier Class1 (see
the classifier example in Chapter 11 on page 59). This policy forwards Class1 packets to port
8.
Configure layer-3 classifiers before you configure policy routing. See Chapter
11 on page 59 for more information on classifiers.
sysname# configure
sysname(config)# classifier Class-1 source-ip 192.168.2.13 mask-bits 24
sysname(config)# ip policy-route Profile-1 sequence 5 permit classifier
Class-1 next-hop 10.1.1.99
sysname(config)# exit
sysname# show ip policy-route
ActiveProfile Name Sequence State Classifier
-----------------------------------------------------------------
Yes Profile-1 5 permit Class-1
It is not recommended you disable both port security and MAC address
learning because this will result in many broadcasts.
sysname# configure
sysname(config)# port-security
sysname(config)# port-security 1
sysname(config)# no port-security 1 learn inactive
sysname(config)# port-security 1 address-limit 5
sysname(config)# exit
sysname# show port-security 1
Port Security Active : YES
Port Active Address Learning Limited Number of Learned MAC Address
01 Y Y 5
The Switch will drop all PPPoE discovery packets if you enable the PPPoE
intermediate agent and there are no trusted ports.
• The Switch discards PADO and PADS packets which are sent from a PPPoE server but
received on an untrusted port.
sysname# configure
sysname(config)# pppoe intermediate-agent
sysname(config)# no pppoe intermediate-agent
sysname# configure
sysname(config)# pppoe intermediate-agent vlan 2
sysname(config)# pppoe intermediate-agent vlan 5,9,11
sysname(config)# pppoe intermediate-agent vlan 1 circuit-id
sysname(config)# pppoe intermediate-agent vlan 3,6 remote-id
sysname(config)# no pppoe intermediate-agent vlan 2-10
sysname(config)# no pppoe intermediate-agent vlan 1 circuit-id
sysname(config)# no pppoe intermediate-agent vlan 3,6 remote-id
sysname# configure
sysname(config)# interface port-channel 3
sysname(config-interface)# pppoe intermediate-agent trust
sysname(config-interface)# no pppoe intermediate-agent trust
This example is more advanced. It assumes a PPPoE IA client is connected to port 2 and a
PPPoE IA server is connected to port 5. If we want PPPoE IA to work, port 2 and port 5 must
be belong to the some VLAN and the PPPoE IA must be enabled globally and in this
corresponding VLAN. We also need to set port 5 as trust port. Then the last thing we need to
do is to decide which sub-options the received PADI, PADR, or PADT packet needs to carry.
Here, assume both circuit-id and remote-id should be carried.
sysname# configure
sysname(config)# vlan 2
sysname(config-vlan)# fixed 2,5
sysname(config-vlan)# untagged 2,5
sysname(config-vlan)# exit
sysname(config)# pppoe intermediate-agent
sysname(config)# pppoe intermediate-agent vlan 2
sysname(config)# interface port-channel 2
sysname(config-interface)# pvid 2
sysname(config-interface)#exit
sysname(config)# interface port-channel 5
sysname(config-interface)# pvid 2
sysname(config-interface)# pppoe intermediate-agent trust
sysname(config-interface)#exit
sysname(config)# pppoe intermediate-agent vlan 2 circuit-id
sysname(config)# pppoe intermediate-agent vlan 2 remote-id
sysname# configure
sysname(config)# pppoe intermediate-agent
sysname(config)# pppoe intermediate-agent format-type access-node-
identifier string test
sysname(config)# pppoe intermediate-agent vlan 1
sysname(config)# pppoe intermediate-agent vlan 1 circuit-id
sysname(config)# pppoe intermediate-agent vlan 1 remote-id
sysname(config)# interface port-channel 5
sysname(config-interface)# pppoe intermediate-agent trust
sysname(config-interface)#exit
This is a variation of the previous one and uses the same initial setup (client on port 2, server
on port 5).
sysname# configure
sysname(config)# pppoe intermediate-agent
sysname(config)# pppoe intermediate-agent format-type identifier-string
string PrivateTest option spv delimiter /
sysname(config)# pppoe intermediate-agent vlan 1
sysname(config)# pppoe intermediate-agent vlan 1 circuit-id
sysname(config)# pppoe intermediate-agent vlan 1 remote-id
sysname(config)# interface port-channel 5
sysname(config-interface)# pppoe intermediate-agent trust
sysname(config-interface)#exit
Because we didn't assign the appended string for remote-id in examples 1 and 2, the Switch
appends a string to carry the client's MAC address as default. If we want the remote-id to carry
the "ForPortVlanRemoteIdTest" information for a specific VLAN on a port, we can add the
following configuration:
sysname# configure
sysname(config)# interface port-channel 2
sysname(config-interface)# pppoe intermediate-agent vlan 1 format-type
remote-id string ForPortVlanRemoteIdTest
sysname(config-interface)# exit
Similarly, we can let the circuit-id carry the information which we configure:
sysname# configure
sysname(config)# interface port-channel 2
sysname(config-interface)# pppoe intermediate-agent vlan 1 format-type
circuit-id string ForPortVlanCircuitIdTest
sysname(config-interface)# exit
Additionally, we can let the circuit-id or remote-id carry the user-configured information from
a specific port whose priority is less than the specific VLAN on a port setting:
sysname# configure
sysname(config)# interface port-channel 2
sysname(config-interface)# pppoe intermediate-agent format-type circuit-
id string ForPortCircuitIdTest
sysname(config-interface)# pppoe intermediate-agent format-type remote-
id string ForPortRemoteIdTest
sysname(config-interface)# exit
Since we didn't assign the appended string for remote-id in example 1 and 2, it will carry the
client's MAC address as default.
2 6 10
VLAN 123
Isolated ports: 2 ~ 6
Promiscuous port: 10
If you change the VLAN settings, make sure you keep at least one port in the
promiscuous port list for a VLAN with private VLAN enabled. Otherwise, this
VLAN is blocked from the whole network.
sysname# configure
sysname(config)# private-vlan name pvlan-123 vlan 123 promiscuous-port 7-8
sysname(config)# exit
sysname# show private-vlan
Private VLAN: 123 Active: Yes
Name Promiscuous Port
------------ --------------------------
pvlan-123 7-8
sysname#
This example sets a private VLAN rule (pvlan-111) that applies to VLAN 111. Ports 1, 2 and
24 belong to VLAN 111. Ports 1 and 2 are added to the isolated port list automatically and
cannot communicate with each other. Port 24 is the uplink port and also the promiscuour port
in this VLAN. The isolated ports in VLAN 111 can send and receive traffic from the uplink
port 24. This example also shows all private VLAN rules configured on the Switch.
sysname# configure
sysname(config)# private-vlan name pvlan-111 vlan 111
sysname(config)# exit
sysname# show private-vlan
Private VLAN: 111 Active: Yes
Name Promiscuous Port
------------ --------------------------
pvlan-111 24
sysname#
• Primary: Ports in a Primary VLAN are promiscuous and they can communicate with all
promiscuous ports in the same primary VLAN, and all ports in associated community and
isolated VLANs. They cannot communicate with ports in different primary VLANs.
• Community: Ports in a Community VLAN can communicate with promiscuous ports in an
associated Primary VLAN and other community ports in the same Community VLAN. They
cannot communicate with ports in Isolated VLANs, non-associated Primary VLAN
promiscuous ports nor community ports in different Community VLANs.
• Isolated: Ports in an Isolated VLAN can communicate with promiscuous ports in an
associated Primary VLAN only. They cannot communicate with other isolated ports in the
same Isolated VLAN, non-associated Primary VLAN promiscuous ports nor any
community ports.
Tagged private VLANs can span switches but trunking ports must be VLAN-trunking ports.
Primary PVLAN 100 is then mapped to port 2 on the Switch and outgoing frames from port 2 will be
tagged
sysname# configure
sysname(config)# vlan 100
sysname(config-vlan)# private-vlan primary
sysname(config-vlan)# exit
sysname(config)# vlan 101
sysname(config-vlan)# private-vlan community
sysname(config-vlan)# exit
sysname(config)# vlan 102
sysname(config-vlan)# private-vlan isolated
sysname(config-vlan)# exit
sysname(config)# vlan 100
sysname(config-vlan)# private-vlan association 101
sysname(config-vlan)# private-vlan association 101,102
sysname(config-vlan)# exit
sysname(config)# exit
sysname# show vlan private-vlan
Private Vlan:
Primary Secondary Type Ports
------- --------- ---------- --------------------
100 Primary
100 102 Isolated
100 101 Community
sysname#
ysname# configure
sysname(config)# interface port-channel 2
sysname(config-interface)# private-vlan mode promiscuous association 100-->
dot1q tagged
sysname(config-interface)#exit
sysname(config)#
• Some models allow you to select a queuing method on a port-by-port basis. For example,
port 1 can use Strictly Priority Queuing and ports 2-8 can use Weighted Round Robin.
• Other models allow you to specify one queuing method for all the ports at once.
Check your User’s Guide for queuing algorithms supported by your model.
• Strictly Priority Queuing (SPQ) - services queues based on priority only. As traffic
comes into the Switch, traffic on the highest priority queue, Q7 is transmitted first. When
that queue empties, traffic on the next highest-priority queue, Q6 is transmitted until Q6
empties, and then traffic is transmitted on Q5 and so on. If higher priority queues never
empty, then traffic on lower priority queues never gets sent.
Switch models which have only 4 queues, support a limited version of SPQ.
The highest level queue is serviced using SPQ and the remaining queues use
WRR queuing.
• Weighted Fair Queuing (WFQ)- guarantees each queue's minimum bandwidth based on
its bandwidth weight (portion) when there is traffic congestion. WFQ is activated only
when a port has more traffic than it can handle. Queues with larger weights get more
guaranteed bandwidth than queues with smaller weights. This queuing mechanism is
highly efficient in that it divides any available bandwidth across the different traffic
queues. By default, the weight for Q0 is 1, for Q1 is 2, for Q2 is 3, and so on. Guaranteed
bandwidth is calculated as follows:
For example, using the default setting, Q0 on Port 1 gets a guaranteed bandwidth of:
• Weighted Round Robin Scheduling (WRR) - services queues on a rotating basis and is
activated only when a port has more traffic than it can handle. A queue is a given an
amount of bandwidth based on the queue weight value. Queues with larger weights get
more service than queues with smaller weights. This queuing mechanism is highly
efficient in that it divides any available bandwidth across the different traffic queues and
returns to queues that have not yet emptied.
• Hybrid Mode: WRR & SPQ or WFQ & SPQ - some switch models allow you to
configure higher priority queues to use SPQ and use WRR or WFQ for the lower level
queues.
sysname(config)# wfq
sysname(config)# interface port-channel 1-5
sysname(config-interface)# weight 1 2 3 4 12 13 14 15
This example configures the Switch to use WRR as a queueing method but configures the
Gigabit ports 9-12 to use SPQ for queues 5, 6 and 7.
sysname(config)# wrr
sysname(config)# interface port-channel 9-12
sysname(config-interface)# ge-spq 5
sysname# configure
sysname(config)# radius-server mode index-priority
sysname(config)# radius-server host 1 172.16.10.10
sysname(config)# radius-server host 2 172.16.10.11
sysname(config)# radius-accounting host 1 172.16.10.11
sysname(config)# exit
sysname# configure
sysname(config)# remote-management 1 start-addr 172.16.37.0 end-addr
--> 172.16.37.255 service telnet ftp http icmp ssh https
sysname(config)# remote-management 2 start-addr 192.168.10.1 end-addr
--> 192.168.10.1 service snmp
sysname(config)# exit
This example disables all SNMP and ICMP access to the Switch.
sysname# configure
sysname(config)# no service-control snmp
sysname(config)# no service-control icmp
sysname(config)# exit
ras# config
ras(config)# rmon event eventtable 2 log trap public owner operator
description test
ras(config)# exit
ras# show rmon event eventtable 2
Event 2 owned by operator is valid
eventType: logandtrap
eventCommunity: public
eventDescription: test
interval This is the time interval (in seconds) between data samplings.
-integer
absolute This is the method of obtaining the sample value and calculating the value to be
|delta compared against the thresholds.
• absolute - the sampling value of the selected variable will be compared directly
with the thresholds.
• delta - the last sampling value of the selected variable will be subtracted from
the current sampling value first. Then use the difference to compare with the
thresholds.
startup- Specify when the Switch should generate an alarm regarding to the rising and/or
alarm falling thresholds.
• risingAlarm - the Switch generates an alarm if the sampling value (or
calculated value) is greater than or equal to the rising threshold.
• fallingAlarm - the Switch generates an alarm if the sampling value (or
calculated value) is less than or equal to the falling threshold.
• risingOrFallingAlarm - the Switch generates an alarm either when the
sampling value (or calculated value) is greater than or equal to the rising
threshold or when the sampling value (or calculated value) is less than or equal to
the falling threshold.
rising- Specify an integer for the rising threshold. When a value that is greater or equal to
integer this threshold, the Switch generates an alarm.
rising- Specify an event’s index number (between 0 and 65535). The Switch will take the
event- corresponding action of the selected event for the rising alarm. Set this to 0 if you do
index not want to take any action for the alarm.
falling- Specify an integer for the falling threshold. When a value that is smaller or equal to
integer this threshold, the Switch generates an alarm.
falling- Specify an event’s index number (between 0 and 65535). The Switch will take the
event- corresponding action of the selected event for the falling alarm. Set this to 0 if you do
index not want to take any action for the alarm.
This example shows you how to configure an alarm using the following settings:
• alarm index number: 2
• variable: getting the number of errored packets received on port 1
• how often to get a data sample: every 60 seconds
• sampling method: delta
• when to send an alarm: when the value is higher than the rising threshold
• the rising threshold: 50
• which event’s action should be taken for the rising alarm: 2 (see Section 65.3.1 on page
271)
• the falling threshold: 0
• which event’s action should be taken for the falling alarm: 0 (see Section 65.3.1 on page
271)
• who will handle this alarm: operator
ras# config
ras(config)# rmon alarm alarmtable 2 variable ifInErrors.1 interval 60
sample-type delta startup-alarm rising rising-threshold 50 2 falling-
threshold 0 2 owner operator
ras(config)# exit
ras# show rmon alarm alarmtable
Alarm 2 owned by operator is valid
alarmVariable: ifInErrors.1
alarmInterval: 60
alarmSampleType: delta
alarmStartupAlarm: rising
alarmRisingThreshold: 50
alarmRisingEventIndex: 2
alarmFallingThreshold: 0
alarmFallingEventIndex: 0
Last value monitored: 0
ras#
ras# config
ras(config)# rmon statistics etherstats 1 port-channel 12
ras(config)# exit
ras# show rmon statistics etherstats index 1
Statistics 1 owned by is valid
Monitor on interface port-channel 12
etherStatsDropEvents: 0
etherStatsOctets: 1576159
etherStatsPkts: 19861
etherStatsBroadcastPkts: 16721
etherStatsMulticastPkts: 1453
etherStatsCRCAlignErrors: 2
etherStatsUndersizePkts: 0
etherStatsOversizePkts: 0
etherStatsFragments: 0
etherStatsJabbers: 0
etherStatsCollisions: 0
Packet length distribution:
64: 17952
65-127: 666
128-255: 671
256-511: 509
512-1023: 26
1024-1518: 37
ras#
ras# config
ras(config)# rmon history historycontrol 1 buckets 10 interval 10 port-
channel 12
ras(config)# exit
ras# show rmon history historycontrol index 1
History control 1 owned by is valid
Monitors interface port-channel 12 every 10 sec.
historyControlBucketsRequested: 10
historyControlBucketsGranted: 10
Monitored history 1:
Monitored at 0 days 00h:08m:59s
etherHistoryIntervalStart: 539
etherHistoryDropEvents: 0
etherHistoryOctets: 667217
etherHistoryPkts: 7697
etherHistoryBroadcastPkts: 5952
etherHistoryMulticastPkts: 505
etherHistoryCRCAlignErrors: 2
etherHistoryUndersizePkts: 0
etherHistoryOversizePkts: 0
etherHistoryFragments: 0
etherHistoryJabbers: 0
etherHistoryCollisions: 0
etherHistoryUtilization: 72
Monitored history 2:
Monitored at 0 days 00h:09m:08s
etherHistoryIntervalStart: 548
etherHistoryDropEvents: 0
etherHistoryOctets: 673408
etherHistoryPkts: 7759
etherHistoryBroadcastPkts: 5978
etherHistoryMulticastPkts: 519
etherHistoryCRCAlignErrors: 2
etherHistoryUndersizePkts: 0
etherHistoryOversizePkts: 0
etherHistoryFragments: 0
etherHistoryJabbers: 0
etherHistoryCollisions: 0
etherHistoryUtilization: 0
ras#
copy running-config help Provides more information about the specified command. E 13
copy running-config slot <slot> Clones (copies) the attributes from the specified slot to other E 13
<slot-list> slots.
copy running-config slot <slot> Copies the specified attributes from one slot to other slots. E 13
<slot-list> [bandwidth-limit
...]
erase running-config Resets the Switch to the factory default settings. E 13
erase running-config interface Resets to the factory default settings on a per-port basis and E 13
port-channel <port-list> optionally on a per-feature configuration basis.
[<attribute> [<...>]]
erase running-config help Provides more information about the specified command. E 13
sync running-config Uses the current configuration on the active management E 13
card to update the current configuration on the standby
management card.
This example copies all attributes of port 1 to port 2 and copies selected attributes (active,
bandwidth limit and STP settings) from port 1 to ports 5-8
sysname(config)# sflow
sysname(config)# sflow collector 10.1.1.58 udp-port 6343
sysname(config)# interface port-channel 1,2,3,4
sysname(config-interface)# sflow
sysname(config-interface)# sflow collector 10.1.1.58 poll-interval 120
sample-rate 2500
sysname(config-interface)# exit
sysname(config)# exit
sysname# show sflow
sFlow version: 5
sFlow Global Information:
sFlow Status: Active
index Collector Address UDP port
----- ----------------- --------
1 10.1.1.58 6343
B
Isolated ports: 2~6
Root port: 7
Designated port: 8
C
Smart isolation allows you to prevent isolated ports on different switches from transmitting
traffic to each other. After you enable RSTP/MRSTP and smart isolation on the Switch, the
designated port(s) will be added to the isolated port list. In the following example, switch A is
the root bridge. Switch B’s root port 7 connects to switch A and switch B’s designated port 8
connects to switch C. Traffic from isolated ports on switch B can only be sent through non-
isolated port 1 or root port 7 to switch A. This prevents isolated ports on switch B sending
traffic through designated port 8 to switch C. Traffic received on designated port 8 from
switch C will not be forwarded to any other isolated ports on switch B.
B
Before Smart Isolation:
Isolated ports: 2~6
Root port: 7
Designated port: 8
After Smart Isolation:
Isolated ports: 2~6, 8
C
Root port: 7
Designated port: 8
You should enable RSTP or MRSTP before you can use smart isolation on the Switch. If the
network topology changes, the Switch automatically updates the isolated port list with the
latest designated port information.
The uplink port connected to the Internet should be the root port. Otherwise,
with smart isolation enabled, the isolated ports cannot access the Internet.
sysname# configure
sysname(config)# spanning-tree mode rstp
sysname(config)# spanning-tree
sysname(config)# spanning-tree priority 32768
sysname(config)# spanning-tree 3-5, 7-8
sysname(config)# vlan 200
sysname(config-vlan)# fixed 3-5, 7-8
sysname(config-vlan)# untagged 3-5, 7-8
sysname(config-vlan)# exit
sysname(config)# private-vlan name pvlan-200 vlan 200 promiscuous-port 7-8
sysname(config)# smart-isolation
sysname(config)# exit
sysname# show smart-isolation
smart isolation enable
Private VLAN:
Original VLAN:
VLAN 200
isolated 3-5
promiscuous 7-8
sysname#
[General Setting]
SNMP Version : v2c
Get Community : public
Set Community : public
Trap Community : public
[ Trap Destination ]
Index Version IP Port Username
----- ------- ------------ ---- --------
1 v2c 0.0.0.0 162
2 v2c 0.0.0.0 162
3 v2c 0.0.0.0 162
4 v2c 0.0.0.0 162
This example shows you how to display all SNMP user information on the Switch.
[ User Information ]
Index Name SecurityLevel GroupName
----- ------ ------------- --------------
1 admin noauth admin
sysname(config)# spanning-tree
sysname(config)# spanning-tree priority 0
sysname(config)# spanning-tree hello-time 4 maximum-age 20 forward-delay
--> 15
sysname(config)# spanning-tree 5 path-cost 150
sysname(config)# spanning-tree 5 priority 20
In this example, we enable RSTP on ports 21-24. Port 24 is connected to the host while ports
21-23 are connected to another switch
sysname(config)# configure
sysname(config)# spanning-tree
sysname(config)# spanning-tree 21-24
sysname(config)# no spanning-tree 21-23 edge-port
Sessions:
Proto Serv Remote IP Port Local IP Port Bytes In
Bytes Out
This example removes a static multicast forwarding rule with multicast MAC address
(01:00:5e:06:01:46) which belongs to VLAN 1.
This example creates a static multicast forwarding rule. The rule forwards frames with
destination MAC address 01:00:5e:00:00:06 to ports 10~12 in VLAN 1.
sysname# configure
sysname(config)# multicast-forward name AAA mac 01:00:5e:00:00:06 vlan 1
interface port-channel 10-12
In this routing table, you can create an active static route if the <next-hop-ip> is in
172.16.37.0/24 or 127.0.0.0/16. You cannot create an active static route to other IP addresses.
For example, you cannot create an active static route that routes traffic for 192.168.10.1/24 to
192.168.1.1.
sysname# configure
sysname(config)# ip route 192.168.10.1 255.255.255.0 192.168.1.1
Error : The Action is failed. Please re-configure setting.
sysname# configure
sysname(config)# ip route 192.168.10.1 255.255.255.0 192.168.1.1 inactive
You can create an active static route that routes traffic for 192.168.10.1/24 to 172.16.37.254.
sysname# configure
sysname(config)# ip route 192.168.10.1 255.255.255.0 172.16.37.254
sysname(config)# exit
sysname# show ip route static
Idx Active Name Dest. Addr. Subnet Mask Gateway Addr.
Metric
01 Y static 192.168.10.1 255.255.255.0 172.16.37.254 1
subnet-based-vlan name <name> Specifies the name, IP address, subnet mask, source-port C 13
source-ip <ip> mask-bits <mask- and VLAN ID of the subnet based VLAN you want to
bits> source-port <port> vlan configure along with the priority you want to assign to the
<vlan-id> priority <0-7> outgoing frames for this VLAN.
303
304
C HA PT E R 76
TACACS+ Commands
Use these commands to configure external TACACS+ (Terminal Access Controller Access-
Control System Plus) servers.
Different models support different numbers of trunks (T1, T2, ...). This chapter
uses a model that supports six trunks (from T1 to T6).
sysname(config)# trunk t1
sysname(config)# trunk t1 interface 5-8
This example disables trunk one (T1) and removes ports 1, 3, 4, and 5 from trunk two (T2).
sysname(config)# no trunk T1
sysname(config)# no trunk T2 interface 1,3-5
ID: 2
[(0000,00-00-00-00-00-00,0000,00,0000)][(0000,00-00-00-00-00-00
-->,0000,00,0000)]
LINKS :
SYNCS :
ID: 3
[(0000,00-00-00-00-00-00,0000,00,0000)][(0000,00-00-00-00-00-00
--> ,0000,00,0000)]
LINKS :
SYNCS :
sysname(config)# trtcm
sysname(config)# trtcm mode color-aware
sysname(config)# interface port-channel 1-5
sysname(config-interface)# trtcm
sysname(config-interface)# trtcm cir 4000
sysname(config-interface)# trtcm pir 4500
sysname(config-interface)# trtcm dscp green 7
sysname(config-interface)# trtcm dscp yellow 22
sysname(config-interface)# trtcm dscp red 44
sysname(config-interface)# exit
sysname(config)# exit
sysname# show running-config interface port-channel 1 trtcm
Building configuration...
Current configuration:
interface port-channel 1
trtcm
trtcm cir 4000
trtcm pir 4500
trtcm dscp green 7
trtcm dscp yellow 22
trtcm dscp red 44
exit
This examples activates trTCM on the Switch with the following settings :
• Enable trTCM on the Switch
• Enable Diffserv on the Switch
• Set the Switch to inspect the DSCP value of packets (color-aware mode)
• Create a trTCM DSCP profile with the name “abc”, and set DSCP value 1 for green
packets, 2 for yellow packets, 3 for red packets
• Associate the profile “abc” with port 1
• Enable trTCM on port 1
• Enable Diffserv on port 1
• Set the Committed Information Rate (CIR) to 4000 Kpbs
• Set the Peak Information Rate (PIR) to 4500 Kbps
• Display the settings of this example
sysname# config
sysname(config)# trtcm
sysname(config)# diffserv
sysname(config)# trtcm mode color-aware
sysname(config)# trtcm dscp profile abc dscp green 1 yellow 2 red 3
sysname(config)# interface port-channel 1
sysname(config-interface)# trtcm
sysname(config-interface)# diffserv
sysname(config-interface)# trtcm dscp profile abc
sysname(config-interface)# trtcm cir 4000
sysname(config-interface)# trtcm pir 4500
sysname(config-interface)# exit
sysname(config)# exit
sysname # show running-config
Building configuration...
Current configuration:
vlan 1
name 1
normal ""
fixed 1-28
forbidden ""
untagged 1-28
ip address default-management 192.168.1.1 255.255.255.0
exit
trtcm
trtcm mode color-aware
trtcm dscp profile abc dscp green 1 yellow 2 red 3
interface port-channel 1
diffserv
trtcm
trtcm cir 4000
trtcm pir 4500
trtcm dscp profile abc
exit
diffserv
sysname #
The following section lists the commands for the ingress checking feature
• Some models enable or disable VLAN ingress checking on all the ports via the vlan1q
ingress-check command.
• Other models enable or disable VLAN ingress checking on each port individually via the
ingress-check command in the config-interface mode.
Table 186 vlan1q ingress-check Command Summary
COMMAND DESCRIPTION M P
show vlan1q ingress-check Displays ingress check settings on the Switch. E 3
vlan1q ingress-check Enables ingress checking on the Switch. The Switch discards C 13
incoming frames on a port for VLANs that do not include this
port in its member set.
no vlan1q ingress-check Disables ingress checking on the Switch. C 13
You can not enable VLAN mapping and VLAN stacking at the same time.
sysname# configure
sysname(config)# vlan-mapping
sysname(config)# vlan-mapping name test interface port-channel 4 vlan 123
translated-vlan 234 priority 3
sysname(config)#
sysname# configure
sysname(config)# interface port-channel 4
sysname(config-interface)# vlan-mapping
sysname(config-interface)# exit
sysname(config)#
VLAN 24 VLAN 24
Customer A Customer A
SPN
x A: 37, 24 y
B: 48, 24
VLAN 24 VLAN 24
Customer B Customer B
This example shows how to configure ports 1 and 2 on the Switch to tag incoming frames with
the service provider’s VID of 37 (ports are connected to customer A network). This example
also shows how to set the priority for ports 1 and 2 to 3.
sysname(config)# vlan-stacking
sysname(config)# interface port-channel 1-2
sysname(config-interface)# vlan-stacking role access
sysname(config-interface)# vlan-stacking spvid 37
sysname(config-interface)# vlan-stacking priority 3
sysname(config-interface)# exit
sysname(config)# exit
sysname# show vlan-stacking
Switch Vlan Stacking Configuration
Operation: active
STPID: 0x8100
X 172.16.1.1
PVID = 200
VRID = 1
Ethernet
B
PVID = 200
172.16.1.10
10.10.1.253
Priority = 100
PVID = 100
This example shows how to create the IP routing domains and configure the Switch to act as
router A in the topology shown in Figure 11 on page 336.
sysname# config
sysname(config)# vlan 100
sysname(config-vlan)# fixed 1-4
sysname(config-vlan)# untagged 1-4
sysname(config-vlan)# ip address 10.10.1.252 255.255.255.0
sysname(config-vlan)# exit
sysname(config) interface port-channel 1-4
sysname(config-interface)# pvid 100
sysname(config-interface)# exit
sysname(config)# vlan 200
sysname(config-vlan)# fixed 24-28
sysname(config-vlan)# untagged 24-28
sysname(config-vlan)# ip address 172.16.1.1 255.255.255.0
sysname(config-vlan)# exit
sysname(config)# interface port-channel 24-28
sysname(config-interface)# pvid 200
sysname(config-interface)# exit
sysname(config)# router vrrp network 10.10.1.252/24 vr-id 1 uplink-gateway
172.16.1.200
sysname(config-vrrp)# name VRRP-networkA
sysname(config-vrrp)# priority 200
sysname(config-vrrp)# interval 2
sysname(config-vrrp)# primary-virtual-ip 10.10.1.254
sysname(config-vrrp)# exit
sysname(config)#
This example shows how to create the IP routing domains and configure the Switch to act as
router B in the topology shown in Figure 11 on page 336.
sysname# config
sysname(config)# vlan 100
sysname(config-vlan)# fixed 1-4
sysname(config-vlan)# untagged 1-4
sysname(config-vlan)# ip address 10.10.1.253 255.255.255.0
sysname(config-vlan)# exit
sysname(config) interface port-channel 1-4
sysname(config-interface)# pvid 100
sysname(config-interface)# exit
sysname(config)# vlan 200
sysname(config-vlan)# fixed 24-28
sysname(config-vlan)# untagged 24-28
sysname(config-vlan)# ip address 172.16.1.10 255.255.255.0
sysname(config-vlan)# exit
sysname(config)# interface port-channel 24-28
sysname(config-interface)# pvid 200
sysname(config-interface)# exit
sysname(config)# router vrrp network 10.10.1.253/24 vr-id 1 uplink-gateway
172.16.1.200
sysname(config-vrrp)# name VRRP-networkB
sysname(config-vrrp)# interval 2
sysname(config-vrrp)# primary-virtual-ip 10.10.1.254
sysname(config-vrrp)# exit
sysname(config)#
sysname# cable-diagnostics 7
port 7
cable diagnostics result
pairA: Ok
pairB: Ok
This example sends Ping requests to an Ethernet device with IP address 172.16.37.254.
This example shows the current status of the various alarms in the Switch.
This example looks at the current sensor readings from various places in the hardware.The
display for your Switch may be different.
Customer Part
PSU Serial Number Number & Revision Manufacturing Fan Air Flow
---- ------------- ----------------- ------------ -------------
PSU1 DIYD11M00CN 20110124 front-to-back
PSU2 DIYD11M00DV 20110125 front-to-back
This example displays run-time SFP (Small Form Facter Pluggable) parameters on ports 9 (the
first SFP port 0, with an SFP transceiver installed) and 10 (the second SFP port 1, no SFP
transceiver installed) on the Switch. You can also see the alarm and warning threasholds for
temperature, voltage, transmission bias, transmission and receiving power as shown.
SFP : 0
Part Number : SFP-SX-DDM
Series Number : S081113001132
Revision : V1.0
Transceiver : 1000BASE-SX
Temperature(C) Alarm(80.00 ~ 0.00), Warning(75.00 ~ 5.00), Current(38.00)
Voltage(V) Alarm(3.50 ~ 3.10), Warning(3.45 ~ 3.15), Current(3.37)
Tx Bias(mA) Alarm(100.05 ~ 1.00), Warning(90.04 ~ 2.00), Current(5.25)
Tx Power(dBm) Alarm(-2.99 ~ -8.98), Warning(-3.49 ~ -8.48), Current(-6.05)
Rx Power(dBm) Alarm(-2.99 ~ -18.01), Warning(-3.49 ~ -17.39), Current(-4.24)
SFP : 1
Not Available
This example displays run-time SFP (Small Form Facter Pluggable) parameters on port 21 on
the Switch. You can also see the alarm and warning threasholds for temperature, voltage,
transmission bias, transmission and receiving power as shown.
Port : 21 (SFP)
Vendor : ZyXEL
Part Number : SFP-LX-10-D
Series Number : S081133000074
Revision : V1.0
Date Code : 2008-08-11
Transceiver : 1000BASE-LX
This example displays the firmware version the Switch is currently using..
351
352
A PPENDIX A
Default Values
Some commands, particularly no commands, reset settings to their default values. The
following table identifies the default values for these settings.
Table 206 Default Values for Reset Commands
COMMAND DEFAULT VALUE
no aaa authentication enable Method 1: enable
Method 2: none
Method 3: none
no aaa authentication login Method 1: local
Method 2: none
Method 3: none
no aaa accounting update 0 minutes
no arp inspection filter-aging- 300 seconds
time
no arp inspection log-buffer 32 messages
entries
no arp inspection log-buffer 5 syslog messages
logs 1 second
no radius-server <index> IP address: 0.0.0.0
Port number: 1812
Key: blank
no radius-accounting <index> IP address: 0.0.0.0
Port number: 1813
Key: blank
Copyright
Copyright © 2013 by ZyXEL Communications Corporation.
The contents of this publication may not be reproduced in any part or as a whole, transcribed,
stored in a retrieval system, translated into any language, or transmitted in any form or by any
means, electronic, mechanical, magnetic, optical, chemical, photocopying, manual, or
otherwise, without the prior written permission of ZyXEL Communications Corporation.
Published by ZyXEL Communications Corporation. All rights reserved.
Disclaimer
ZyXEL does not assume any liability arising out of the application or use of any products, or
software described herein. Neither does it convey any license under its patent rights nor the
patent rights of others. ZyXEL further reserves the right to make changes in any products
described herein without notice. This publication is subject to change without notice.
Trademarks
ZyNOS (ZyXEL Network Operating System) is a registered trademark of ZyXEL
Communications, Inc. Other trademarks mentioned in this publication are used for
identification purposes only and may be properties of their respective owners.
Certifications
Federal Communications Commission (FCC) Interference Statement
This device complies with Part 15 of FCC rules. Operation is subject to the following two
conditions:
• This device may not cause harmful interference.
• This device must accept any interference received, including interference that may cause
undesired operations.
FCC Warning
This device has been tested and found to comply with the limits for a Class A digital switch,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a commercial environment. This device generates,
uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of
this device in a residential area is likely to cause harmful interference in which case the user
will be required to correct the interference at his own expense.
CE Mark Warning:
This is a class A product. In a domestic environment this product may cause radio interference
in which case the user may be required to take adequate measures.
Notices
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
CLASS 1 LASER PRODUCT
APPAREIL A LASER DE CLASS 1
PRODUCT COMPLIES WITH 21 CFR 1040.10 AND 1040.11.
PRODUIT CONFORME SELON 21 CFR 1040.10 ET 1040.11.
Viewing Certifications
1 Go to http://www.zyxel.com.
2 Select your product on the ZyXEL home page to go to that product's page.
3 Select the certification you wish to view from this page.
whatever extent it shall deem necessary to restore the product or components to proper
operating condition. Any replacement will consist of a new or re-manufactured functionally
equivalent product of equal or higher value, and will be solely at the discretion of ZyXEL.
This warranty shall not apply if the product has been modified, misused, tampered with,
damaged by an act of God, or subjected to abnormal working conditions.
Note
Repair or replacement, as provided under this warranty, is the exclusive remedy of the
purchaser. This warranty is in lieu of all other warranties, express or implied, including any
implied warranty of merchantability or fitness for a particular use or purpose. ZyXEL shall in
no event be held liable for indirect or consequential damages of any kind to the purchaser.
To obtain the services of this warranty, contact your vendor. You may also refer to the
warranty policy for the region in which you bought the device at http://www.zyxel.com/web/
support_warranty_info.php.
Registration
Register your product online to receive e-mail notices of firmware upgrades and information
at www.zyxel.com.
Index of Commands
ma-index ......................................................................... 51
md-index ......................................................................... 51
mep <mep-id> interface port-channel <port> direction <up|down> priority <0-7> .... 53
mep <mep-id> interface port-channel <port> direction <up|down> priority <0-7> cc-enable
53
mep <mep-id> interface port-channel <port> direction <up|down> priority <0-7> inactive
53
mep-id ........................................................................... 51
mhf-creation < none | default | explicit> ........................................ 53
mirror .......................................................................... 205
mirror dir <ingress|egress|both> ................................................ 206
mirror-filter egress mac <mac-addr> ............................................. 206
mirror-filter egress type <all|dest|src> ........................................ 206
mirror-filter ingress mac <mac-addr> ............................................ 206
mirror-filter ingress type <all|dest|src> ....................................... 206
mirror-port ..................................................................... 205
mirror-port <port-num> .......................................................... 205
mode <dynamic|compatible> ....................................................... 219
mode zynos ...................................................................... 341
mrstp <tree-index> .............................................................. 209
mrstp <tree-index> hello-time <1-10> maximum-age <6-40> forward-delay <4-30> .... 209
mrstp <tree-index> priority <0-61440> ........................................... 209
mrstp interface <port-list> ..................................................... 209
mrstp interface <port-list> edge-port ........................................... 210
mrstp interface <port-list> path-cost <1-65535> ................................. 210
mrstp interface <port-list> priority <0-255> .................................... 210
mrstp interface <port-list> tree-index <tree-index> ............................. 210
mstp ............................................................................ 211
mstp configuration-name <name> .................................................. 211
mstp hello-time <1-10> maximum-age <6-40> forward-delay <4-30> .................. 211
mstp instance <number> interface port-channel <port-list> ....................... 212
mstp instance <number> interface port-channel <port-list> path-cost <1-65535> ... 212
mstp instance <number> interface port-channel <port-list> priority <0-255> ...... 212
mstp instance <number> priority <0-61440> ....................................... 212
mstp instance <number> vlan <vlan-list> ......................................... 212
mstp interface port-channel <port-list> edge-port ............................... 211
mstp max-hop <1-255> ............................................................ 211
mstp revision <0-65535> ......................................................... 211
multicast-forward name <name> mac <mac-addr> vlan <vlan-id> inactive ............ 293
multicast-forward name <name> mac <mac-addr> vlan <vlan-id> interface port-channel <port-
list> .................................................................... 293
multicast-limit .................................................................. 46
multicast-limit <pkt/s> .......................................................... 46
multi-login ..................................................................... 217
mvr <1-4094> .................................................................... 339
mvr <vlan-id> ................................................................... 219
name <name> ..................................................................... 219
name <name> ..................................................................... 318
name <name> ..................................................................... 335
name <port-name-string> ......................................................... 137
network <ip-addr/bits> area <area-id> ........................................... 225
no aaa accounting commands ....................................................... 30
no aaa accounting dot1x .......................................................... 30
no aaa accounting exec ........................................................... 30
no aaa accounting system ......................................................... 30
no aaa accounting update ......................................................... 29
no aaa accounting update ........................................................ 353
no aaa authentication enable ..................................................... 29
no aaa authentication enable .................................................... 353
no diffserv ...................................................................... 87
no display aaa <[authentication][authorization][server]> ......................... 89
no display user <[system][snmp]> ................................................. 89
no dlf-limit ..................................................................... 46
no egress set <port-list> ....................................................... 243
no errdisable detect cause <ARP|BPDU|IGMP> ....................................... 94
no errdisable recovery ........................................................... 94
no errdisable recovery cause <loopguard|ARP|BPDU|IGMP> ........................... 94
no ethernet cfm .................................................................. 54
no ethernet cfm ma <ma-index> md <md-index> ...................................... 54
no ethernet cfm management-address-domain ........................................ 54
no ethernet cfm md <md-index> .................................................... 54
no ethernet cfm virtual-mac ...................................................... 54
no ethernet oam .................................................................. 97
no ethernet oam .................................................................. 98
no ethernet oam mode ............................................................. 98
no ethernet oam remote-loopback ignore-rx ........................................ 98
no ethernet oam remote-loopback supported ........................................ 98
no ets traffic-class binding ..................................................... 75
no external-alarm <index> ....................................................... 103
no external-alarm all ........................................................... 103
no fixed <port-list> ............................................................ 318
no flow-control ................................................................. 138
no forbidden <port-list> ........................................................ 318
no green-ethernet auto-power-down ............................................... 108
no green-ethernet auto-power-down ............................................... 108
no green-ethernet eee ........................................................... 108
no green-ethernet eee ........................................................... 108
no green-ethernet short-reach ................................................... 108
no green-ethernet short-reach ................................................... 108
no group ........................................................................ 219
no group <name-str> ............................................................. 219
no gvrp ......................................................................... 111
no hybrid-spq ................................................................... 261
no igmp-filtering ............................................................... 135
no igmp-filtering profile ....................................................... 135
no igmp-filtering profile <name> ................................................ 135
no igmp-filtering profile <name> start-address <ip> end-address <ip> ............ 135
no igmp-group-limited ........................................................... 131
no igmp-immediate-leave ......................................................... 131
no igmp-snooping ................................................................ 127
no igmp-snooping 8021p-priority ................................................. 127
no igmp-snooping filtering ...................................................... 127
no igmp-snooping filtering profile .............................................. 131
no igmp-snooping filtering profile <name> ....................................... 127
no igmp-snooping filtering profile <name> start-address <ip> end-address <ip> ... 127
no igmp-snooping group-limited .................................................. 131
no igmp-snooping leave-proxy .................................................... 128
no igmp-snooping querier ........................................................ 128
no igmp-snooping report-proxy ................................................... 128
no igmp-snooping vlan <vlan-id> ................................................. 129
no inactive ..................................................................... 138
no inactive ..................................................................... 219
no inactive ..................................................................... 318
no inactive ..................................................................... 335
no inactive ....................................................................... 5
no ingress-check ................................................................ 319
no install slot <slot> .......................................................... 341
no interface <port-num> ......................................................... 138