Guia de Comandos
Guia de Comandos
Guia de Comandos
204.4284.31
Legal Notice
LEGAL NOTICE
Although every precaution has been taken in the preparation of this document, DATACOM
takes no responsibility for possible errors or omissions, and it will accept no obligation
for damages resulting from the use of the information contained in this manual. The
specifications provided in this manual are subject to changes without notice, and they
will not be recognized as any kind of contract.
WARRANTY
This product is warranted against material and workmanship defects for the period spec-
ified in the sales invoice.
The warranty only includes the repair and replacement of defective components and
parts without any resulting burden to the customer. Defects resulting from the following
are not covered: improper use of device, faulty electrical power network, nature-related
events (lightning discharges, for instance), failure in devices connected to this product,
installations with improper grounding or repairs made by personnel not authorized by
DATACOM.
This warranty does not cover repairs at the customer’s facilities. Equipment must be
forwarded for repairs to DATACOM.
CONTACTS
Technical Support
DATACOM offers a technical support call center to support customers during configura-
tion and use of its equipment, and also to provide a technical assistance for product
maintenance and repair.
e-mail: suporte@datacom.ind.br
website: www.datacom.ind.br/en/support
General Information
DATACOM
+55 51 3933-3000
PRODUCT DOCUMENTATION
This manual is part of a set of documents prepared to provide all necessary information
about DATACOM products, whether you are a buyer, administrator, manager or operator.
Command Reference - Provides all the commands related to the product (only
in English)
Hardware Platform
Visit the DATACOM website to locate related documentation for a product or contact
Customer Support (see Contacts).
This guide provides command line interface (CLI) related information. This document
describes how to use the CLI and it also covers initial configurations, those normally
needed after hardware installation.
The document was designed to serve as a source of eventual queries. Therefore, it does
not need be read sequentially. This guide provides command reference for each of the
CLI commands available on the DmOS.
It is assumed that the individual or individuals managing any aspect of this product have
basic understanding of Ethernet and Telecommunications networks.
Intended Audience
The User Guide of each product is intended for Network Administrators and other quali-
fied service personnel responsible for deploying, operating and maintaining the DmOS.
Conventions
In order to improve the agreement, the following conventions are made throughout this
guide:
Icons Convention
This symbols means that, case the procedure was not correctly fol-
Warning
lowed, may exist electrical shock risk.
This symbol means that this text is very important and, if the orien-
Caution
tations were not correct followed, it may cause damage or hazard.
A caution type notice calls attention to conditions that, if not avoided, may
damage or destroy hardware or software.
A warning type notice calls attention to conditions that, if not avoided, could
result in death or serious injury.
Text Convention
This guide uses these text conventions to convey instructions and information:
Convention Description
The text convention shown above differs from Command Line Interface syntax
convention. See the convention related to commands on Command Syntax.
Table of Contents
Chapter 1: Product Concept 11
Chapter 3: Management 22
CLI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
NETCONF
NMS (DmView)
Each of the management methods enables you to configure, manage, and control the
software locally or remotely using in-band or out-of-band mechanisms. Management is
standards-based, with configuration parameters and a private MIB providing control for
functions not completely specified in the MIBs.
Supported Platforms
Command Syntax
Command Modes
SUPPORTED PLATFORMS
Consult Hardware and Software Compatibility in Release Notes to check supported plat-
forms.
COMMAND SYNTAX
A command is one or more words that might be followed by one or more parameters.
Parameters can be required or optional values.
Some commands, such as show ip route or clear mac address-table, do not require
parameters. Other commands, such as aaa authentication, require that you supply a
value after the command. You must type the parameter values in a specific order, and
optional parameters follow required parameters. The following example describes the
aaa authentication command syntax:
user and password are parameters and represent required options that user must
enter after the command keyword.
username and password are required parameters that user must enter after the
user and password keywords, respectively.
The Command Reference lists each command by the command name and provides a
brief description of the command. Each command reference also contains the following
information:
Format: shows the command keywords and the required and optional parameters.
Mode: identifies the command mode you must be in to access the command.
Default: shows the default value, if any, of a configurable setting on the device.
The show commands also contain a description of the information that the command
shows.
Parameter values might be names (strings) or numbers. Spaces could be used as part
of a name parameter only for line<N> parameters, without any kind of delimiter. For
example, the expression System Name with Spaces will be recognized as a unique value
when used as a parameter for the command snmp-server contact. Empty strings are
not valid user-defined strings.
The no keyword is a specific form of an existing command and does not represent a new
or distinct command. Almost every configuration command has a no form. In general,
use the no form to reverse the action of a command or reset a value back to the de-
fault. For example, the no shutdown configuration command reverses the shutdown of
an interface. Use the command without the keyword no to re-enable a disabled feature
or to enable a feature that is disabled by default. Only the configuration commands are
available in the no form.
Many CLI show commands include considerable content to display to the user. This
can make output confusing and cumbersome to parse through to find the information
of desired importance. The CLI Output Filtering feature allows the user, not only when
executing CLI show display commands, but specially on these cases, to optionally specify
arguments to filter the CLI output to display only desired information. The result is to
simplify the display and make it easier for the user to find the information the user is
interested in.
Pagination Control
When pagination is enabled, press the return key to advance a single line,
press q, Q or Ctrl+C to stop pagination, press g or G to continue up to the end
of the output, or press any other key to advance a whole page. These keys
are not configurable.
Output Filtering
"Grep"-like control for modifying the displayed output to only show the user-
desired content.
Filter displayed output to only include lines including and following a spec-
ified string match.
Example: The following shows an example of the extensions made to the CLI commands
for the Output Filtering feature.
COMMAND MODES
The CLI groups the commands into modes, according to the command function. Each of
the command modes supports specific software commands. The commands in a partic-
ular mode will not to be available until you switch to that given mode. You can execute
Operational commands in the Configure commands mode by usign the do keyword.
Command completion finishes spelling the command when you type enough letters of a
command to uniquely identify the command keyword. Once you have entered enough
letters, press the TAB key to complete the word or press SPACE BAR and let that system
resolves the command directly from the short version.
Command abbreviation allows you to execute a command when you have entered there
are enough letters to uniquely identify the command. You must enter all of the required
keywords and parameters before you enter the command.
DmOS# re
Possible completions:
reboot Reboot the system
reboot-forced Reboot the system without any checks
request Request system operations
The TAB key will complete the command if there is only one candidate com-
mand. Otherwise, a list of all possible commands will be showed.
If you enter a command and the system is unable to execute it, an error message ap-
pears. Table 1: CLI Error Messages describes the most common CLI error messages.
syntax error: unknown Indicates that the value inserted there is not for the com-
element mand.
Table 2: CLI Editing Conventions describes the key combinations you can use to edit
commands or increase the speed of command entry.
Enter a question mark (?) at the command prompt to display the commands available in
the current mode.
DmOS# ?
Possible completions:
autowizard Automatically query for mandatory elements
clear Clear equipment settings and counters
commit Confirm a pending commit
compare Compare running configuration to another configuration
or a file
complete-on-space Enable/disable completion on space
config Manipulate software configuration information
copy Copy files to a remote server
display-level Configure show command display level
exit Exit the management session
DM4610(config)# ?
Possible completions:
aaa Configure authentication, authorization and accounting
alias Create command alias.
anti-ip-spoofing anti ip-spoofing configuration
clear Clear equipment settings and counters
clock Set the system clock
Enter a question mark (?) after each word you enter to display available command
keywords or parameters.
<cr>
You can also enter a question mark (?) after typing one or more characters of a word to
list the available command or parameters that begin with the letters, as shown in the
following example:
DmOS# show i?
Possible completions:
interface Status information about interfaces
inventory Physical inventory information
ip Display ip information
ipv6 Display ipv6 information
| Output modifiers
<cr>
You can access the CLI by using a direct console connection or by using a SSH connection
from a remote management host.
To establish a terminal connection using console interface (VT100), a proper serial cable
(provided with the equipment) must be connected between the equipment terminal port
and the PC serial port.
Take care to avoid potential difference between RJ45 pin 4 from Switch (signal ground)
and DB9 pin 5 from the PC. If it occurs, it may cause damages to the PC and to the
equipment’s serial interfaces.
To access the terminal, select the serial port of your preference and set the following
values on the VT100 emulator (factory default values of equipment):
Data: 8 bits
Parity: none
Once the access was successful, a login screen must appear. The login factory defaults
are:
User: admin
Password:
For the initial connection, you could use also a SSH client, connecting an Ethernet port of
your PC to the management port of the switch (10/100Base-T) and accessing the default
IP address: 192.168.0.25 (with a 255.255.255.0 subnet mask and without a default gate-
way), with the same credentials of VT100 terminal. You can set the network configuration
information manually, or you can configure the system to accept these settings from a
DHCP server on your network. For more information, see Network Interface Commands.
specialCharactersCli
Character Description
If it is necessary to use the characters above on a string, put the string between double-
quotes (“).
CHAPTER 3: MANAGEMENT
This chapter describes the commands related to management access in the DmOS CLI.
CLI SETTINGS
This topic describes the available settings used in a command-line interface (CLI) ses-
sion. Changes on these settings are applied only to the current session.
debug
Description
This command is used to enable or to disable debug messages. The debug messages
are printed only on the user session that enabled the debugs and these messages are
not logged. After user logout, the user session is closed and all enabled debugs of that
session are automatically disabled.
Supported Platforms
Syntax
Parameters
enable
Value: N/A
disable
Description: Disable the specified list of debug commands or disable all de-
bug commands enabled in the current user session.
Value: N/A
link-status
Value: N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Use the debug enable command to see the debug messages of a command or a list
of commands. And use the debug disable to see no more debug messages of all
commands or of some commands.
The use of debug enable with many commands over serial interface may cause the
session to become unresponsive to user intervention. Consider this before issuing the
respective command.
Hardware restrictions
N/A
display-defaults
Description
Shows default values as comments when showing the configuration. This setting is valid
for the current session only.
Supported Platforms
Syntax
display-defaults {true|false}
Parameters
{true|false}
Default
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
If show-defaults is set to true, the default values, if available, are shown as comments
after the actual parameter value:
Examples:
# display-defaults true
# show running-config aaa
aaa user admin
password $1$SzCHCSOa$IiVcIUUino2s12Wk1Rdwa/
group admin ! audit
!
# show running-config mac-address-table
mac-address-table
aging-time 600 ! 600
!
Note that even if the parameter is set to the default value, it is shown again in the com-
ment.
This command takes effect for the current session only, if the change is to be made per-
sistent, use command “session display-defaults” or “user <username> session display-
defaults” instead.
Hardware restrictions
N/A
screen-resize
Description
Adjust the screen size following the current size of screen being used. If the screen size
is changed the command must be run again.
Supported Platforms
Syntax
screen-resize
Parameters
N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
# screen-resize
In configuration mode:
(config)# do screen-resize
N/A
Hardware restrictions
N/A
session
Description
Supported Platforms
Syntax
Parameters
complete-on-space {true|false}
ignore-leading-space {true|false}
idle-timeout seconds
Description: Maximum idle time before being logged out. Use 0 (zero) for for
infinity.
Value: 0-8192
paginate {true|false}
history size
Value: 0-8192
display-defaults {true|false}
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
N/A
This command sets the default settings for new sessions. It can be overridden by the
corresponding configuration in operational mode or “user <username> session” com-
mands. Use “show cli” command in operational mode to check the actual values.
Hardware restrictions
N/A
user
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
user-name
Description: Name of the user for which the CLI options are being set.
Value: Text
description description
Value: Text
alias alias_name
Value: Text
expansion command
Value: Text
session
Value: N/A
complete-on-space {true|false}
ignore-leading-space {true|false}
idle-timeout seconds
Description: Maximum idle time before being logged out. Use 0 (zero) for
infinity.
Value: 0-8192
paginate {true|false}
history size
Value: 0-8192
display-defaults {true|false}
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
N/A
This command sets the default settings for a specified user. It can be overridden by
the corresponding configuration in operational mode. Use “show cli” command in opera-
tional mode to check the actual values. There is no check whether the user exists or not
in database. This allows remote logged users to have a customized CLI environment.
Hardware restrictions
N/A
INTERFACES
This topic describes the commands related to management interfaces such as com-
mands to configure console and Management-Ethernet (outband).
interface mgmt
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface
Value: chassis/slot/port
vrf vrf-name
Description: Specifies the name of the VRF this interface will be associated
with. Currently, it is possible to configure only the VRF ‘mgmt’.
Value: string.
description if-description
Value: a.b.c.d/x.
ipv6 enable
Value: N/A
Value: x:x:x:x::x/y.
eui-64
Description: Sets 64-bit Extended Unique Identifier for specific IPv6 prefix on
management interface.
Value: N/A
ipv6 nd ra suppress
Value: N/A
Value: x:x:x:x::x/y.
Value: N/A
Value: N/A
Description: When disabled, indicates that this prefix can be used for on-link
determination on management interface.
Value: N/A
Value: Must be no less than 4 seconds and no greater than 1800 sec-
onds.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
It is possible the use of only one IPv4 address and/or two IPv6 addresses on management
interface.
Command to configure IPv6 addresses will be available only if ipv6 enable is set for
interface. Example below shows that IPv6 address configuration option appears after
ipv6 enable is set.
(config-mgmt-1/1/1)# ipv6 ?
Possible completions:
enable Enable IPv6 on interface
!
(config-mgmt-1/1/1)# ipv6 enable
!
(config-mgmt-1/1/1)# ipv6 ?
Possible completions:
address IPv6 address
enable Enable IPv6 on interface
!
Example:
This example shows all management interfaces:
# show running-config interface mgmt all
interface mgmt 1/1/1
ipv4 address 192.168.0.25/24
ipv6 enable
ipv6 address 2001:db8::10/32
!
Or in configuration mode:
(config)# show interface mgmt all
interface mgmt 1/1/1
ipv4 address 192.168.0.25/24
ipv6 enable
ipv6 address 2001:db8::10/32
!
If no VRF is explicitly associated with the mgmt interface, it is associated with the global
VRF by default. The following example shows how to associate a management interface
with the ‘mgmt’ VRF:
(config-mgmt-1/1/1)# ?
Possible completions:
vrf Assign a VRF instance to the interface
!
(config-mgmt-1/1/1)# vrf ?
Possible completions:
<WORD> VPN Routing/Forwarding instance name
mgmt
!
(config-mgmt-1/1/1)# vrf mgmt
(config-mgmt-1/1/1)# commit
Commit complete.
Once the VRF associated with the mgmt interface is changed, any route in the previous
VRF using it as output interface will be uninstalled. In order to keep the connectivity, you
will need to configure the routes in the new VRF.
Hardware restrictions
N/A
CONFIGURATION
This topic describes the commands related to configuration management such as com-
mands to backup or view the running-config content.
banner login
Description
This configuration represents the banner displayed when accessing the equipment via
console, SSH or Telnet. This banner will be displayed before username and password
prompts.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
banner-text
Description: A text message representing the banner that will be shown be-
fore login on the equipment. The text can contain special char-
acters including line breaks () and tabulations ().
Default
None
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
\n - New line
\t - Horizontal tab
\\ - Backslash
Example:
There are two ways to configure the login banner, the multiline mode and single line
mode. In single line mode the banner text must be written in one line, if using spaces
quotation marks will be required, to include line breaks use and to include tabs use . It
is recommend to always include a line break at the end to avoid having the login prompt
concatenated to the banner.
# config
Entering configuration mode terminal
(config)# banner login "**************** BANNER ****************"
(config)# commit
Commit complete.
It is possible to use the command show banner login to check how the banner will be
displayed.
To use multi-line mode, press Enter after banner login and use ctrl-D when finished.
# config
Entering configuration mode terminal
(config)# banner login
(<Hit <cr> to enter in multi-line mode. Alternatively, enter a text between double quotes.
Remember to insert a line break at the end. See command reference for examples.
Maximum length of 3240 characters.>):
[Multiline mode, exit with ctrl-D.]
> ***********************************************************************************
> *** Only authorized personnel are allowed to access this piece of equipment. ***
> *** Others are urged to log off IMMEDIATELY. ***
> *** ***
> *** Somente pessoal autorizado pode acessar este equipamento. ***
> *** Outros, por favor, desconectar IMEDIATAMENTE. ***
> *** ***
> ***********************************************************************************
> ctrl-D
(config)# commit
Commit complete.
(config)# exit
# show banner login
Login banner will be displayed as shown inside <>
<
***********************************************************************************
*** Only authorized personnel are allowed to access this piece of equipment. ***
*** Others are urged to log off IMMEDIATELY. ***
*** ***
*** Somente pessoal autorizado pode acessar este equipamento. ***
*** Outros, por favor, desconectar IMEDIATAMENTE. ***
*** ***
***********************************************************************************
>
DM4610#
| | | |/ /\ \ | | / /\ \| | | | | | |\/| |
| |__| / ____ \| |/ ____ \ |___| |__| | | | |
|_____/_/ \_\_/_/ \_\_____\____/|_| |_|
>
#
Depending on the SSH client software and locale configuration, UTF-8 characters may
not be displayed correctly in login banner text.
Hardware restrictions
None.
clear
Description
Used to remove all configuration changes that were not committed, in other words, all
uncommitted modifications made are discarded, returning the system to the state after
the last commit.
Supported Platforms
Syntax
clear
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
This example shows how to use the clear command. Modify the system configuration. In
the example below, the management IP address is changed.
# config
Entering configuration mode terminal
(config)# show interface
interface mgmt 1/1/1
ipv4 address 192.168.0.25/24
!
(config)# interface mgmt 1/1/1
(config-mgmt-1/1/1)# no ipv4 address
(config-mgmt-1/1/1)# ipv4 address 10.4.16.134/22
(config-mgmt-1/1/1)# exit
(config)# show interface
interface mgmt 1/1/1
ipv4 address 10.4.16.134/22
!
(config)#
Clear all existing modifications.
(config)# clear
All configuration changes will be lost. Proceed? [yes, NO] yes
(config)#
(config)# show interface
interface mgmt 1/1/1
ipv4 address 192.168.0.25/24
!
(config)#
Hardware restrictions
N/A
commit
Description
Supported Platforms
Syntax
Parameters
and-quit
Value: N/A
no-confirm
Value: N/A
comment text
Value: Text
label text
Description: (Optional) Associates a label with the commit. The label can
later be seen when examining rollback files.
Value: Text
persist-id id
Value: Text
save-running file-name
Default
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
N/A
N/A
Hardware restrictions
N/A
commit
Description
Command used to confirm or abort a pending confirmed commit (see commit con-
firmed command for more details)
Supported Platforms
Syntax
Parameters
abort
Value: N/A
confirm
Value: N/A
persist-id id
Value: Text
Output Terms
Output Description
Shows a message
Examples of this command are displayed in the Usage Guidelines
indicating the
field
commit status
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
The examples below shows how to use the command commit. Example 1 - Sequence of
commands using commit confirm:
# config exclusive
Entering configuration mode exclusive
Warning: uncommitted changes will be discarded on exit
(config)# hostname TESTE-COMM
(config)# commit confirmed 1
Warning: The configuration will be reverted if you exit the CLI without
performing the commit operation within 1 minutes.
N/A
Hardware restrictions
N/A
commit abort
Description
Supported Platforms
Syntax
Parameters
persist-id id
Default
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
N/A
N/A
Hardware restrictions
N/A
commit check
Description
Used to validate the modifications made on the candidate-config. Syntax validation, in-
tegrity restrictions, YANG model validation points and coherence callbacks are assessed.
Supported Platforms
Syntax
commit check
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Examples:
This example shows how to use the commit check command. It includes a few addi-
tional steps only for better understanding.
Trying to configure mgmt interface ipv4 address as loopback address it is not allowed.
# config
DmOS(config)# interface mgmt 1/1/1
DmOS(config-mgmt-1/1/1)# show # existing configured IP
interface mgmt 1/1/1
ipv4 address 10.4.16.129/22
!
DmOS(config-mgmt-1/1/1)# ipv4 address 127.0.0.1/8
DmOS(config-mgmt-1/1/1)# exit
DmOS(config)# commit check
Failed: ’interface mgmt 1/1/1 ipv4 address’ (value "127.0.0.1/8"): IPv4 address
cannot be configured as loopback address
N/A
Hardware restrictions
N/A
commit confirmed
Description
Used to copy the current candidate-config to the running-config with a timeout. If the
commit command is not executed before the timeout expires, then the configuration
will be reverted to the configuration that was active before the command was issued.
Supported Platforms
Syntax
commit confirmed [ timeout [persist id] [ comment text ] [ label text ] [ save-
running file-name ] [persist-id id] ]
Parameters
timeout
Value: 0-71582788
Default Value: 10
persist id
Value: Text
comment text
Value: Text
label text
Description: Associates a label with the commit. The label can be later veri-
fied when, for example, displaying the stored commit list.
Value: Text
save-running file-name
persist-id id
Value: Text
Default
Undo the commited changes after the default timeout (10 minutes).
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
The pending commit will be aborted if the CLI session is terminated before confirming
the commit, unless the persist argument is given. In the latter case, a future session
may confirm the pending confirmed commit by supplying the persist id as an argument
to the commit command using the persist-id parameter. During the period this pend-
ing commit exists, access to exclusive sessions are not allowed. Configurations from
terminal sessions are allowed, but if the pending commit is aborted all changes will be
lost.
Hardware restrictions
N/A
compare file
Description
Command used to compare the running-config with a configuration previously saved into
a file. The differences are marked with diff notation:
Supported Platforms
Syntax
Parameters
config-file-name
Value: Text
pathfilter
Value: Text
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
The option ‘brief’ was removed. The command will always show only the
4.4
differences, not the whole configuration.
Usage Guidelines
This example shows how to use the compare file command. It includes a few additional
steps only for better understanding.
Example:
When TACACS+ authorization is enabled and the user is allowed to execute the com-
mand compare file the comparison will be performed in 2 different ways, depending on
the config file format:
a) If the config is stored in text format, which is the default format, the comparison will be
done based on the user permission to execute each command present in the config-
file. Thus, commands not allowed to be executed by the user will generate an error
message in the comparison output.
Hardware restrictions
N/A
config
Description
Used to enter the equipment configuration mode and change its configurations.
Supported Platforms
Syntax
Parameters
terminal
Value: N/A
exclusive
Value: N/A
Default
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
Extra care must be taken with simultaneous edition (e.g. two or more opened sessions
editing the same configuration) see commit command for more information.
Hardware restrictions
N/A
file
Description
Supported Platforms
Syntax
Parameters
delete file-name
list
Value: N/A
show file-name
Description: Displays the content of a file. The file name must be provided.
edit file-name
Description: Edits an existent file or creates a new one, if it does not already
exist. The provided file name is limited to 255 characters and
must not start with “.”, “-”, nor contain file paths.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
This example shows how to use the file command with each of the available parame-
ters. It includes a few additional steps only for better understanding. List the system
user files.
# file list
#
Save a user configuration file and then, use the “file list” command to check if it was
saved.
# config
Entering configuration mode terminal
(config)# save users_cfg aaa user
N/A
Hardware restrictions
N/A
hostname
Description
This configuration represents the hostname of the equipment being configured. The
configured value can be visualized in three different places. Consulting the equipment
configuration through the protocols SNMP and NETCONF and looking at the CLI prompt.
Supported Platforms
Syntax
hostname name
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
name
Value: N/A
Default
DM4610
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to use the hostname command. It includes a few additional
steps only for better understanding.
DM4610# config
Entering configuration mode terminal
DM4610(config)# hostname HOST-001
DM4610(config)# commit
Commit complete.
HOST-001(config)#
HOST-001(config)# exit
HOST-001#
Not available.
Hardware restrictions
Not available.
load factory-config
Description
Supported Platforms
Syntax
load factory-config
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to use the load factory-config command and preserve the man-
agement configuration.
# config
Entering configuration mode terminal
(config)# load factory-config
Loading.
Done.
(config)# interface mgmt 1/1/1
(config-mgmt-1/1/1)# ipv4 address 192.0.2.10/24
(config)# commit
Commit complete.
This command does not automatically commit the loaded configuration. The user must
explicitly run the commit command in order to apply the loaded configuration on the
running-config.
The user must be careful to apply the factory configuration. It may cause the loss
of the device management, because the IP address will be reset to the default value
(192.168.0.25/24).
Hardware restrictions
N/A
load merge
Description
Command used to merge the content of a file with the current configuration.
Supported Platforms
Syntax
Parameters
file
Value: Text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Examples:
A new user ‘datacom’ is created and stored together with ‘admin’ in the ‘users_cfg’
file. This file contains only ‘aaa user’ settings.
A new user is created and the ‘datacom’ user is changed and the load merge command
is used to restore its value. Note that the new user is not affected.
password $1$z9a2TqCc$23midDa3BihfOZlt86YfC1
group admin
!
aaa user newuser
password $1$z9a2dtIk$23midDa3BihfOZlt86YfC1
!
...
(config)#
This command does not automatically commit the loaded configuration. The user must
explicitly run the commit command in order to apply the loaded configuration on the
running-config.
A valid file must exist in order to execute this command. It can be a XML file or a
text file with CLI commands.
Configuration not present in the file will not be affected by this command.
When TACACS+ authorization is enabled and the user is allowed to execute the com-
mand load merge the merging will be performed based on all commands present in
the file if it is stored in xml format. Otherwise, if it is stored in text format, which is the
default format, the merge will be done individually for each command present in the file
based on the user permission to execute it. Thus, commands not allowed to be executed
by the user can affect the merge requiring the operation to be aborted.
Hardware restrictions
N/A
load override
Description
The current configuration is deleted and a new configuration is loaded from file.
Supported Platforms
Syntax
Parameters
file
Value: Text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Examples:
The initial configuration of equipment is stored in the ‘all_cfg’ file and then the man-
agement IP is changed.
# config
Entering configuration mode terminal
(config)# show aaa
aaa user admin
password $1$uYMZohDj$gP/QPHc1kog5k6IopHNQh/
group admin
!
(config)# save all_cfg
The ‘load override’ command is used to restore the original configuration. Note that the
new user is removed.
(config-user-datacom)# exit
(config)# load override all_cfg
Loading.
188 bytes parsed in 0.09 sec (1.93 KiB/sec)
(config)# show aaa
aaa user admin
password $1$uYMZohDj$gP/QPHc1kog5k6IopHNQh/
group admin
!
(config)#
This command does not automatically commit the loaded configuration. The user must
explicitly run the commit command in order to apply the loaded configuration on the
running-config.
A valid file must exist in order to execute this command. It can be a XML file or a text
file with CLI commands, but it MUST contain the complete configuration of the device, all
missing configuration will be deleted, the equipment operation may be compromised. In
some cases, the commit may fail if critical configuration is missing.
When TACACS+ authorization is enabled and the user is allowed to execute the com-
mand load override the overriding will be performed based on all commands present
in the file if it is stored in xml format. Otherwise, if it is stored in text format, which is
the default format, the overriding will be done individually for each command present in
the file based on the user permission to execute it. Thus, commands not allowed to be
executed will not remain in the candidate config, resulting in a partial configuration to
be committed.
Hardware restrictions
N/A
resolved
Description
Supported Platforms
Syntax
resolved
Parameters
N/A
Output Terms
Output Description
Displays a
warning message
Examples of this command are displayed in the Usage Guidelines
informing about
field.
the configuration
conflict.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Open 2 ssh sessions with the same equipment and access the configuration prompt from
interface gigabit 1/1/1:
(config)# interface gigabit-ethernet 1/1/1
(config-gigabit-ethernet-1/1/1)#
On ssh session 01, change the advertising-abilities as following:
(config-gigabit-ethernet-1/1/1)# advertising-abilities 1Gfull 100Mful
On ssh session 02, change the advertising-abilities as following and commit:
(config-gigabit-ethernet-1/1/1)# advertising-abilities 100Mfull
(config-gigabit-ethernet-1/1/1)# commit
Commit complete.
Go back to ssh session 01 and try to commit. The system shall return the following
message:
(config-gigabit-ethernet-1/1/1)# commit
Aborted: there are conflicts.
--------------------------------------------------------------------------
Resolve needed before configuration can be committed. View conflicts with
the command ’show configuration’ and execute the command ’resolved’ when done,
or exit configuration mode to abort.
Conflicting configuration items are indicated with a leading ’!’
Conflicting users: admin
It is possible to check the conflicting configuration by executing the command below:
(config-gigabit-ethernet-1/1/1)# show configuration
! advertising-abilities 100Mfull 1Gfull
Finally, to solve this conflict an apply the configuration, execute the command sequence
below:
(config)# resolved
(config)# commit
Commit complete.
(config)# interface gigabit-ethernet 1/1/1
(config-gigabit-ethernet-1/1/1)# show
interface gigabit-ethernet 1/1/1
no shutdown
negotiation
duplex full
speed 1G
advertising-abilities 100Mfull 1Gfull
mdix normal
!
N/A
Hardware restrictions
N/A
rollback configuration
Description
Supported Platforms
Syntax
Parameters
number
Value: 0-64
Default Value: 0
Default
Return the current configuration to the most recently committed configuration, without
activating it.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
These examples show how to use the rollback configuration command. It includes a few
additional steps only for better understanding.
Examples:
Generating and visualizing the rollback files. First, it shows the configuration commit
list to illustrate the system’s current state.
# config
Entering configuration mode terminal
(config)# show configuration commit list
1970-01-01 07:28:32
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10051 admin cli 1970-01-01 07:28:12
1 10050 admin cli 1970-01-01 07:01:59
2 10049 admin cli 1970-01-01 06:29:00
3 10048 admin cli 1970-01-01 06:28:36
4 10047 admin cli 1970-01-01 05:36:01
5 10046 admin cli 1970-01-01 01:49:10
6 10045 admin cli 1970-01-01 01:45:42
7 10044 admin cli 1970-01-01 01:42:42
8 10042 admin cli 1970-01-01 01:32:03
9 10041 admin cli 1970-01-01 01:30:24
10
... 10040 admin cli 1970-01-01 01:24:45
Then, it configures two different alias and commit them assigning a label. Next, it creates
more two alias and also commit them with another label.
(config)# alias cmd-alias01 expansion test1
(config-alias-cmd-alias01)# exit
(config)# alias cmd-alias02 expansion test2
(config-alias-cmd-alias02)# exit
(config)# commit comment "add cmd-alias 1/2"
Commit complete.
(config)# alias cmd-alias03 expansion test3
(config-alias-cmd-alias03)# exit
(config)# alias cmd-alias04 expansion test4
(config-alias-cmd-alias04)# exit
(config)# commit comment "add cmd-alias 3/4"
Commit complete.
(config)# show configuration commit list
1970-01-01 07:30:56
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10053 admin cli 1970-01-01 07:30:49 add cmd-alias 3/4
1 10052 admin cli 1970-01-01 07:30:23 add cmd-alias 1/2
2 10051 admin cli 1970-01-01 07:28:12
3 10050 admin cli 1970-01-01 07:01:59
4 10049 admin cli 1970-01-01 06:29:00
5 10048 admin cli 1970-01-01 06:28:36
6 10047 admin cli 1970-01-01 05:36:01
7 10046 admin cli 1970-01-01 01:49:10
8 10045 admin cli 1970-01-01 01:45:42
9 10044 admin cli 1970-01-01 01:42:42
10
... 10042 admin cli 1970-01-01 01:32:03
Finally, the command sequence below uses the rollback command to return the current
configuration to a previously committed configuration. In this case, the last 2 commits
(0 and 1) are rolled back.
(config)# rollback configuration 1
(config)# commit
Commit complete.
As a result, all alias specific configurations (previously configured in this example) were
removed from the system.
(config)# show configuration running alias
% No entries found.
The system stores a limited number of rollback files (65). If the maximum number is
reached, then the oldest configuration is removed before creating a new one. The most
recently committed configuration (the running configuration) is number 0, the next most
recent is number 1, etc.
This command does not automatically commit the rolled back configuration. The user
must explicitly run the commit command in order to apply the configuration.
When a firmware upgrade is performed some commands might have been modified and
the use of rollback command might fail if the rollback contains commands modified be-
tween firmware versions. In this case it is recommended to execute the configuration
step by step again.
When TACACS+ authorization is enabled and the user is allowed to execute the com-
mand rollback configuration the operation will be done independent from the user
permission to execute the commands in the rollback files.
Hardware restrictions
N/A
rollback selective
Description
Supported Platforms
Syntax
Parameters
number
Value: 0-64
Default Value: 0
Default
Return the current configuration to the most recently committed configuration, without
activating it.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
These examples show how to use the rollback selective command. It includes a few ad-
ditional steps only for better understanding.
Examples:
Generating and visualizing the rollback files. First, it shows the configuration commit
list to illustrate the system’s current state.
# config
Entering configuration mode terminal
(config)# show configuration commit list
1970-01-01 07:28:32
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10051 admin cli 1970-01-01 07:28:12
1 10050 admin cli 1970-01-01 07:01:59
2 10049 admin cli 1970-01-01 06:29:00
3 10048 admin cli 1970-01-01 06:28:36
4 10047 admin cli 1970-01-01 05:36:01
5 10046 admin cli 1970-01-01 01:49:10
6 10045 admin cli 1970-01-01 01:45:42
7 10044 admin cli 1970-01-01 01:42:42
8 10042 admin cli 1970-01-01 01:32:03
9 10041 admin cli 1970-01-01 01:30:24
10
... 10040 admin cli 1970-01-01 01:24:45
Then, it configures two different alias and commit them assigning a label. Next, it creates
more two alias and also commit them with another label.
(config)# alias cmd-alias01 expansion test1
(config-alias-cmd-alias01)# exit
(config)# alias cmd-alias02 expansion test2
(config-alias-cmd-alias02)# exit
(config)# commit comment "add cmd-alias 1/2"
Commit complete.
(config)# alias cmd-alias03 expansion test3
(config-alias-cmd-alias03)# exit
(config)# alias cmd-alias04 expansion test4
(config-alias-cmd-alias04)# exit
(config)# commit comment "add cmd-alias 3/4"
Commit complete.
(config)# show configuration commit list
1970-01-01 07:30:56
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10053 admin cli 1970-01-01 07:30:49 add cmd-alias 3/4
1 10052 admin cli 1970-01-01 07:30:23 add cmd-alias 1/2
2 10051 admin cli 1970-01-01 07:28:12
3 10050 admin cli 1970-01-01 07:01:59
4 10049 admin cli 1970-01-01 06:29:00
5 10048 admin cli 1970-01-01 06:28:36
6 10047 admin cli 1970-01-01 05:36:01
7 10046 admin cli 1970-01-01 01:49:10
8 10045 admin cli 1970-01-01 01:45:42
9 10044 admin cli 1970-01-01 01:42:42
10
... 10042 admin cli 1970-01-01 01:32:03
Finally, the command sequence below uses the rollback selective command to return the
current configuration to a previously committed configuration. In this case, the “commit
1” is rolled back.
(config)# rollback selective 1
(config)# commit
Commit complete.
The system stores a limited number of rollback files (65). If the maximum number is
reached, then the oldest configuration is removed before creating a new one. The most
recently committed configuration (the running configuration) is number 0, the next most
recent is number 1, etc.
This command does not automatically commit the rolled back configuration. The user
must explicitly run the commit command in order to apply the configuration.
When a firmware upgrade is performed some commands might have been modified and
the use of rollback command might fail if the rollback contains commands modified be-
tween firmware versions. In this case it is recommended to execute the configuration
step by step again.
When TACACS+ authorization is enabled and the user is allowed to execute the command
rollback selective the operation will be done independent from the user permission to
execute the commands present in the selected commit.
Hardware restrictions
N/A
save
Description
Supported Platforms
Syntax
Parameters
file
Value: Text
xml
Value: N/A
pathfilter
Value: Text
Default
Save the whole configuration using the same format as visualized in show command.
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The following examples show how to use the save command with each parameter.
Examples:
The command sequence below, shows how to save the current configuration into a file
named cfg001.
# config
(config)# save cfg001
(config)# exit
# file show cfg001
aaa user admin
password $1$BuQV.kcR$JkYGm./9vB8LJ5bjCjEpk1
group admin
!
router static 0.0.0.0/0 next-hop 10.4.16.1
!
...
interface gpon 1/1/7
upstream-fec
downstream-fec
no shutdown
!
interface gpon 1/1/8
upstream-fec
downstream-fec
no shutdown
!
The command sequence below, shows how to save the current configuration into a file
named cfg002, using xml format.
# config
(config)# save cfg002 xml
(config)# exit
# file show cfg002
<config xmlns="http://tail-f.com/ns/config/1.0">
<bfd xmlns="http://tail-f.com/ns/bfd-stub">
<stub>
</stub>
</bfd>
<config xmlns="urn:dmos">
<interface>
<gigabit-ethernet xmlns="urn:dmos:dmos-interface-ethernet">
<id>1/1/1</id>
<shutdown>false</shutdown>
<negotiation>true</negotiation>
<duplex>full</duplex>
<speed>1G</speed>
<advertising-abilities>1Gfull</advertising-abilities>
<mdix>normal</mdix>
</gigabit-ethernet>
...
<dot1q xmlns="http://tail-f.com/ns/example/vlan-manager">
<vlan>
<vlan-id>1</vlan-id>
<interface>
<interface-name>gigabit-ethernet 1/1/9</interface-name>
</interface>
</vlan>
</dot1q>
The command sequence below, shows how to save a partial configuration into a file
named cfg003.
# config
(config)# save cfg003 dot1q
Saving dot1q
(config)# exit
# file show cfg003
dot1q
vlan 1
interface gigabit-ethernet 1/1/9
!
!
!
The command sequence below, shows how to save a partial configuration into a file
named cfg004, using xml format.
# config
(config)# save cfg004 xml dot1q
Saving parts of the configuration.
(config)# exit
# file show cfg004
<config xmlns="http://tail-f.com/ns/config/1.0">
<dot1q xmlns="http://tail-f.com/ns/example/vlan-manager">
<vlan>
<vlan-id>1</vlan-id>
<interface>
<interface-name>gigabit-ethernet 1/1/9</interface-name>
</interface>
</vlan>
</dot1q>
N/A
Hardware restrictions
N/A
show
Description
Used to display all running configuration (applied by commits) without the default values.
It can be used to display all fields when editing a subgroup configuration (e.g. a specific
user in users configuration).
Supported Platforms
Syntax
show { pathfilter }
Parameters
pathfilter
Value: Text
Output Terms
Output Description
Displays
information Examples of this command are displayed in the Usage Guidelines
about the system field
configuration
Default
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
Example 1:
(config)# show
aaa user admin
password $1$UoyZaDJS$aUxgMRkWXhhKCRmzqwasd/
group admin
!
alias bla
expansion bla7
!
bfd
!
interface mgmt 1/1/1
ipv4 address 10.4.16.132/22
!
router static 0.0.0.0/0 next-hop 10.4.16.1
!
snmp agent enabled
snmp agent version v2c
snmp agent version v3
snmp agent max-message-size 50000
snmp community public
sec-name public
!
snmp notify std_v1_trap
tag std_v1_trap
!
snmp notify std_v2_inform
tag std_v2_inform
type inform
!
snmp notify std_v2_trap
tag std_v2_trap
!
Example 2:
(config)# show aaa
aaa user admin
password $1$UoyZaDJS$aUxgMRkWXhhKCRmzqwasd/
group admin
!
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
login
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
None.
Hardware restrictions
None.
show configuration
Description
Supported Platforms
Syntax
Parameters
this
Value: N/A
diff
Value: N/A
merge
Value: N/A
pathfilter
Value: Text
Output Terms
Output Description
Displays the
difference between
the candidate
Examples of this command are displayed in the Usage Guidelines
and commited
field
configurations
for the specified
module.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
If the candidate configuration is empty, the equipment shall return the message stated
below:
Now, to clarify the purpose and operation of this command, the example below will
perform a change in the configuration. In this case, the gigabit-ethernet 1/1/1 interface
was activated.
Then, it is possible to verify the diference between the candidate and commited con-
figuration.
And if the user wants to check this difference using diff notation:
N/A
Hardware restrictions
N/A
Description
Used to display the content of a commit file. A commit file is saved with new config-
urations any time a commit command is performed. These files can also be used in a
rollback command.
Supported Platforms
Syntax
Parameters
diff
Description: Marks the changes between running-config and rollback file us-
ing the diff notation.
Value: N/A
id
Value: Number
pathfilter
Value: Text
Output Terms
Output Description
Displays the
Examples of this command are displayed in the Usage Guidelines
content of a
field.
commit file.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
These examples show how to use the show configuration commit changes command. It
includes a few additional steps only for better understanding.
Examples:
Showing changes that were committed for a given commit id (id = 0):
(config)#
(config)# show configuration commit changes 0
!
! Created by: admin
! Date: 1970-01-01 00:04:55
! Client: cli
!
aaa user datacom_1
password $1$VmUU06GU$Cf36xMHMikZBXDxgwYsXW0
group admin
!
aaa user datacom_2
password $1$5dZ1FwQD$2SF8Q6K7pHMGnd7xGLWhS1
group admin
!
Showing changes that were committed for a given commit id (id = 1):
(config)#
(config)# show configuration commit changes 1
!
! Created by: admin
! Date: 1970-01-01 00:04:44
! Client: cli
!
router static 0.0.0.0/0 next-hop 10.4.16.1
!
Showing changes that were committed for a given commit id (id = 2):
(config)#
(config)# show configuration commit changes 2
!
! Created by: admin
! Date: 1970-01-01 00:04:33
! Client: cli
!
interface mgmt 1/1/1
no ipv4 address
ipv4 address 10.4.16.132/22
!
Showing the changes between running-config and rollback file (id = 0) using the diff
notation:
(config)#
(config)# show configuration commit changes diff 0
!
! Created by: admin
! Date: 1970-01-01 00:04:55
! Client: cli
!
+aaa user datacom_1
+ password $1$VmUU06GU$Cf36xMHMikZBXDxgwYsXW0
+ group admin
+!
+aaa user datacom_2
+ password $1$5dZ1FwQD$2SF8Q6K7pHMGnd7xGLWhS1
+ group admin
+!
Showing the changes between running-config and rollback file (id = 0) to a specific
configuration (aaa) using the diff notation:
(config)#
(config)# show configuration commit changes diff 0 aaa user datacom_2
!
! Created by: admin
! Date: 1970-01-01 00:04:55
! Client: cli
!
+aaa user datacom_2
+ password $1$5dZ1FwQD$2SF8Q6K7pHMGnd7xGLWhS1
+ group admin
+!
(config)#
N/A
Hardware restrictions
N/A
Description
Shows a list including all configuration commits stored in the commit database.
Supported Platforms
Syntax
Parameters
num
Description: Number of commit IDs (beginning with the most recent commit)
that will be displayed
pathfilter
Description: Specifies a filter to display only commit IDs that contain a spe-
cific configuration
Value: Text
Output Terms
Output Description
The output
displays the
Examples of this command are displayed in the Usage Guidelines
commit IDs that
field
are available for
rollback
Default
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Use the show configuration commit list command to list the commit IDs (up to 65) that
are available for rollback. The newest 65 commits are stored by the system. As new
commit IDs are added, the oldest commit IDs are discarded.
Examples:
2016-01-01 09:02:07
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10068 admin cli 2015-03-26 16:17:40
1 10067 admin cli 2015-03-26 16:15:03
2 10066 oper cli 2015-03-26 16:13:35
3 10065 admin cli 2015-03-26 14:43:03
4 10059 oper cli 2015-03-26 14:09:34
5 10058 oper cli 2015-03-26 13:55:31
6 10056 oper cli 2015-03-26 13:54:25
7 10054 admin cli 2015-03-26 13:45:39
8 10053 admin cli 2015-03-26 13:45:00
9 10051 admin cli 2015-03-26 13:43:26
10 10044 admin cli 2015-03-25 14:33:31
11 10043 admin cli 2015-03-25 14:32:47
12 10042 admin cli 2015-03-25 11:30:25
It is also possible to limit the number of commits displayed in the command output, by
using the num parameter. The example below, shows the last 3 configuration commits
executed by the user.
(config)# show configuration commit list 3
2016-01-01 09:03:44
SNo. ID User Client Time Stamp Label Comment
~~~~ ~~ ~~~~ ~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~
0 10068 admin cli 2015-03-26 16:17:40
1 10067 admin cli 2015-03-26 16:15:03
2 10066 oper cli 2015-03-26 16:13:35
N/A
Hardware restrictions
N/A
Description
Used to display the changes applied after a specific commit file is used in a rollback
command.
Supported Platforms
Syntax
Parameters
diff
Value: N/A
id
Value: Number
Output Terms
Output Description
Displays the
changes applied
after a specific Examples of this command are displayed in the Usage Guidelines
commit file is field.
used in a rollback
command.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
These examples show how to use the show configuration rollback changes command. It
includes a few additional steps only for better understanding.
Examples:
When a firmware upgrade is performed some commands might have been modified
and the use of rollback command might fail if the rollback contains commands modified
between firmware versions. In this case it is recommended to execute the configuration
step by step again.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
pathfilter
Value: Text
Output Terms
Output Description
Displays
the running
configuration Examples of this command are displayed in the Usage Guidelines
without its field.
default values.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
These examples shows how to use the show configuration running command.
# config
Entering configuration mode terminal
(config)# show configuration running
aaa user admin
password $1$DMOzVTxJ$pczOpWZo2hIU1Or0VUfce.
group admin
!
interface mgmt 1/1/1
ipv4 address 192.168.0.25/24
!
snmp agent enabled
snmp agent version v2c
snmp agent version v3
snmp agent max-message-size 50000
snmp community public
sec-name public
!
snmp vacm group public
member public
sec-model [ v2c ]
!
access v2c no-auth-no-priv
read-view root
write-view root
notify-view root
!
...
(config)#
# config
Entering configuration mode terminal
(config)# show configuration running interface
interface mgmt 1/1/1
N/A
Hardware restrictions
N/A
show running-config
Description
Used to display all the current configurations (applied by commits). The configurations
with default values will not be displayed.
Supported Platforms
Syntax
Parameters
pathfilter
Value: Text
Output Terms
Output Description
Displays
the running
configuration Examples of this command are displayed in the Usage Guidelines
without its field.
default values.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
top
Description
Used to exit to the top level of configuration mode or execute a command at the top
level of the configuration.
Supported Platforms
Syntax
top [ command ]
Parameters
command
Value: Text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
This examples shows how to use the top command. Exit to the top level of configuration
mode.
# config
Entering configuration mode terminal
(config)# aaa user config
(config-user-config)# top
(config)#
Execute a command at the top level of the configuration. In this example the command
“interface l3 L3-name” is executed at the top of configuration creating a new interface
but keep the actual configuration level.
# config
Entering configuration mode terminal
(config)#aaa user config
(config-user-config)# top interface l3 L3-name
(config-user-config)#
(config-user-config)# show interface l3
interface l3 L3-name
!
(config-user-config)#
Execute the command top and enter in other configuration level. In this example using
“;” is possible to execute top command and enter at interface l3 configuration level.
# config
Entering configuration mode terminal
(config)#aaa user config
(config-user-config)# top ; interface l3 L3-name
(config-l3-L3-name)#
N/A
Hardware restrictions
N/A
FIRMWARE
This topic describes the commands related to firmware management such as commands
to identify current version or to execute an upgrade.
Description
This command is used to download a remotely stored ONU firmware file and store it
localy.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
protocol://A.B.C.D/path/fw_name
Description: Download and store an ONU firmware file in the local device
to be used in a remote device ONU update. This parameter
specifies the ‘protocol’ (available protocol is TFTP); the remote
server address ‘A.B.C.D’ (IPv4 address); and the path and name
‘path/fw_name’ of the firmware stored in the remote server.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Use the request firmware onu add command to download and store a new ONU firmware
file in the local device.
There is up to 106 MB available for ONU firmware files in the equipment flash memory.
Hardware restrictions
N/A
Description
This command is used to remove a ONU firmware file stored in the local device.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
filename
Description: Delete an ONU firmware file stored in the local device. This
parameter specifies the name of the ONU firmware file to be
removed.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Use the request firmware onu remove command to delete a downloaded ONU firmware
file from the local device.
N/A
Hardware restrictions
N/A
DIAGNOSTICS
This topic describes the commands related to management diagnostic such as com-
mands to verify some interface connection, to check CPU usage or to execute a traffic
mirror.
clear core-dump
Description
Supported Platforms
Syntax
Parameters
filename
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
clear counters
Description
Clear statistics counters for User-Defined Counter instances. If no parameters are given
all user-defined counters will be cleared.
Supported Platforms
Syntax
Parameters
ingress
Description: Clear counters of ingress stage. If no IDs are given all counters
of ingress stage will be cleared.
Value: N/A
egress
Description: Clear counters of egress stage. If no IDs are given all counters
of egress stage will be cleared.
Value: N/A
id counter-id
Value: 1 - 512
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has ingress counters 1, 3, 5 and 7 and egress counters 2, 4, 6 and
8 configured.
# show counters
INGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
1 One 6546 octets
3 Three 47984 octets
5 Five 1321 octets
7 Seven 71211 octets
EGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
2 Two 19655 octets
4 Four 75203 octets
6 Six 5616 octets
8 Eight 39458 octets
EGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
2 Two 19655 octets
4 Four 75203 octets
6 Six 5616 octets
8 Eight 39458 octets
It is possible to clear multiple counters by using range syntax, so let’s clear egress coun-
ters from ID 4 up to ID 8. Note that in that range there are non-existent counters and
they are going to be ignored:
# clear counters egress id 4-8
Counter ID 5 doesn’t exist. Skipping...
Counter ID 7 doesn’t exist. Skipping...
# show counters
INGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
1 One 0 octets
3 Three 0 octets
5 Five 1321 octets
7 Seven 0 octets
EGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
2 Two 19655 octets
4 Four 0 octets
6 Six 0 octets
8 Eight 0 octets
The clear operation is valid for all user interfaces. That means that a clear operation
done through CLI, for example, will affect the values shown in all other user interfaces
too i.e. SNMP and NETCONF.
Hardware restrictions
None
clear statistics
Description
Supported Platforms
Syntax
Parameters
interface-name
Value: { { gigabit-ethernet |
**ten-gigabit-ethernet** | **twenty-five-gigabit-ethernet** |
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The CLI and Netconf values are subject to this command and should not be used for
accounting or billing.
Once issued, this command will set all counters to 0 on the network interface interface-
name, on the CLI and NetConf access interfaces. Other access interfaces will not be
cleared by this command. The values on these access interfaces should not be used for
accounting or billing (see usage guidelines).
Hardware restrictions
N/A
copy core-dump
Description
Copies a core-dump file using the TFTP or SCP protocol to valid host.
Supported Platforms
Syntax
Parameters
filename
protocol
ip-address
username
password
Description: Specify the source ip address or the interface name where core
dump file should be send through.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Changed parameters order and included ‘scp’ option for protocol param-
2.2
eter.
Usage Guidelines
To copy core-dump file to existing remote host using TFTP protocol as in the example
below.
To copy core-dump file to existing remote host using SCP protocol as in the example be-
low.
To copy core-dump file to existing remote host using SCP protocol and IPv6 as in the
example below.
To copy core-dump file to existing remote host using TFTP protocol and source ip address
as in the example below.
To copy core-dump file to existing remote host using TFTP protocol and source interface
N/A
Hardware restrictions
N/A
copy file
Description
Supported Platforms
Syntax
Parameters
local-filename
Description: Name of local file to be copied to remote host. Names are lim-
ited to 255 characters and must not start with ‘.’ and ‘-’.
protocol
ip-address
remote-path
remote-filename
username login
Description: Specifies the login name to access a remote host. Use this only
when protocol is scp.
password pass
Description: Specifies the login password to access a remote host. Use this
only when protocol is scp.
port number
Value: 0-65535.
rename name
Description: Specifies the name to save file on device or remote host. Names
are limited to 255 characters and must not start with ‘.’ and ‘-’.
Description: Specifies the source ip address or the interface name from which
transfer should be started.
or
interface - name of the management or l3 interface in l3-<name>,
mgmt-<c>/<s>/<p> format.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
To copy file to existing remote host using SCP protocol in a specific folder.
# copy file test scp://1.2.1.1/dir/ username user password pass
Transfer complete.
#
To copy file to existing remote host using SCP protocol in a specific folder and a specific
port.
# copy file test scp://1.2.1.1/dir/ username user password pass port 200
Transfer complete.
#
To copy file to existing remote host using TFTP protocol in a specific folder.
# copy file test tftp://1.2.1.1/dir/
Transfer complete.
#
To copy file to existing remote host using TFTP protocol and rename the file.
# copy file test tftp://1.2.1.1 rename test_renamed
Transfer complete.
#
To copy file from existing remote host using TFTP protocol without rename.
# copy file tftp://1.2.1.1 test
Transfer complete.
#
To copy file from existing remote host using TFTP protocol and rename the file.
# copy file tftp://1.2.1.1 test rename test_renamed
Transfer complete.
#
To copy file from existing remote host using TFTP protocol with source IPv4 address.
# copy file tftp://1.2.1.1 test source 1.1.1.1
Transfer complete.
#
To copy file from existing remote host using TFTP protocol with source interface-name.
# copy file tftp://1.2.1.1 test source mgmt-1/1/1
Transfer complete.
#
To copy file from existing remote IPv6 host using TFTP protocol with source IPv6 address.
# copy file tftp://2001::DB8::10 test source 2001:DB8::1
Transfer complete.
#
N/A
Hardware restrictions
N/A
copy mibs
Description
Copies a compressed file containing the device MIB files via the TFTP or SCP protocol to
a remote host.
Supported Platforms
Syntax
Parameters
protocol
ip-address
username
password
Description: Specifies the source IP address or the interface name from which
the transfer should be initiated.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Copying MIBs to a remote host using IPv6 and the SCP protocol:
Copying MIBs to a remote host using the TFTP protocol and a source IP address:
Copying MIBs to a remote host using the SCP protocol and a source interface name:
N/A
Hardware restrictions
N/A
counters
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
ingress
Value: N/A
egress
Value: N/A
id counter-id
Value: 1 - 512
type octets
Value: octets
description counter-description
vlan vlan-id
Value: 1 - 4094
inner-vlan vlan-id
Value: 1 - 4094
interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Counters can be created specifying multiple interfaces to count only the traffic in the
specified interfaces.
Examples:
The following example creates one counter instance to count the number of octets on
the ingress side of VLAN 100 and interfaces gigabit-ethernet-1/1/4 and gigabit-ethernet-
1/1/5.
# config
Entering configuration mode terminal
(config)# counters
(counters)# ingress id 12
(counters-ingress-12)# vlan 100
(counters-ingress-12)# interface gigabit-ethernet-1/1/4
(counters-ingress-12)# interface gigabit-ethernet-1/1/5
(counters-ingress-12)# commit
Commit complete.
(counters-ingress-12)#
With ACL: Ingress counters increment even for packets dropped by Ingress ACLs.
With VLAN Mapping: For packets which Action Replace has been applied the inner-VLAN
considered by the Ingress Counter is the VLAN that has just been replaced.
Hardware restrictions
On DM4270, DM4775, DM4770 and DM4380 series: it is not allowed to create an egress
counter for an interface + VLAN when the interface is an untagged member of the VLAN.
On DM4270, DM4775, DM4770 and DM4380 series: Layer 2 Control Protocol tunneled
packets are counted twice on matching ingress counters.
interface utilization
Description
Supported Platforms
Syntax
Parameters
interface-name
l1
Value: N/A
l2
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
Display L1 and L2 bandwidth of all available interfaces.
#show interface utilization
Repetition Mode
For monitoring the bandwidth it is useful to use this command within the <repeat>
command:
Filtering interfaces:
This command also has a property to refine and only display some interfaces.
Some filters are:
^ | Matches the beginning of a string.
[abc] | Character class, which matches any of the characters abc. Character
ranges are specified by a pair of characters separated by a.
r* | Matches zero or more rs.
Match exactly an interface (pressing <tab> button will display all possible interfaces):
#show interface utilization gigabit-ethernet-1/1/1
Filter for forty-gigabit-ethernet interfaces (when available):
#show interface utilization forty*
Filter for interfaces presents in chassis 1 and slot 2 (when available):
#show interface utilization *1/2/*
Filter for forty-gigabit-ethernet interfaces and ten-gigabit-ethernet (when available):
#show interface utilization [ft]*
Filter for any interfaces presents in chassis 1 and any slot (when available):
#show interface utilization *1/*/*
Filter for a range of interfaces presents in chassis 1 and slot 2 (when available):
#show interface utilization *1/2/2-5
Filter for some interfaces presents in chassis 1 and slot 2 (when available):
#show interface utilization *1/2/2,7,10
When the interval between the two last executions of this command is less than 1
minute, the measured and displayed bandwidth is the mean bandwidth during this inter-
val. When the interval is greater than 1 minute, the displayed value is the instantaneous
bandwidth. When this command is executed in more than one user session at the same
time, the bandwidth value displayed is not guaranteed to be accurate. For more accu-
rate results, use this command with <repeat> option in a single user session (See Usage
Guidelines).
Hardware restrictions
N/A
monitor session
Description
Supported Platforms
Syntax
monitor session id
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
monitor session id
Value: 1
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet.
traffic-type
Value: rx | tx | all
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
#config
Entering configuration mode terminal
(config)# monitor session 1
(monitor-session-1)# destination interface gigabit-ethernet-1/1/1
(monitor-session-1-destination)# exit
(monitor-session-1)# source interface ten-gigabit-ethernet-1/1/1 tx
(monitor-session-source-interface-gigabit-ethernet-1/1/1)# top
(config)# commit
Commit complete.
(config)#
When adding a source interface to the monitor session, the default behaviour is to mon-
itor its received traffic. Inside the interface configuration tree, the command tx or all will
change the monitored traffic type.
A LAG and its members cannot be used as source interfaces in the same monitor
session.
The mirrored traffic is subjected to the QoS and shaping rules of the destination inter-
face.
Hardware restrictions
N/A
ping
Description
Ping is a utility that uses the ICMP protocol to test connectivity between IP networks
devices.
Supported Platforms
Syntax
ping ipv4-address [ vrf name | size number | count number | interval time | fragment
type | tos number | source {ip-address | interface} ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
ipv4-address
Value: a.b.c.d
vrf name
size number
Value: 0 - 65507
count number
Value: 1 - 1000000000
Default Value: 5.
interval number
fragment type
tos number
Value: 0 - 255
Description: Specify the source IP address or the interface name from which
packets should be sent.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The following example demonstrates how to use the ping command without any param-
eter. It will send 5 ICMP probes to the destination host.
# ping 10.0.121.80
PING 10.0.121.80 (10.0.121.80) 56(84) bytes of data.
64 bytes from 10.0.121.80: icmp_seq=1 ttl=64 time=0.015 ms
64 bytes from 10.0.121.80: icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from 10.0.121.80: icmp_seq=3 ttl=64 time=0.019 ms
64 bytes from 10.0.121.80: icmp_seq=4 ttl=64 time=0.033 ms
64 bytes from 10.0.121.80: icmp_seq=5 ttl=64 time=0.036 ms
--- 10.0.121.80 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.015/0.027/0.036/0.009 ms
The following example demonstrates how to use the ping command with the “count”
parameter:
The following example demonstrates how to use the ping command with the “size” pa-
rameter:
The following example demonstrates how to use the ping command with the “source”
parameter using ip address:
The following example demonstrates how to use the ping command with the “source”
parameter using interface name:
N/A
Hardware restrictions
N/A
ping6
Description
Ping6 is a utility that uses the ICMPv6 protocol to test connectivity between IP networks
devices.
Supported Platforms
Syntax
ping6 ipv6-address [ size number | count number | interval time | tos number |
source {ip-address | interface} ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
ipv6-address
Value: X:X:X:X::X.
size number
Value: 0 - 65507
count number
Value: 1 - 1000000000
Default Value: 5.
interval number
tos number
Value: 0 - 255
Description: Specify the source IP address or the interface name from which
packets should be sent.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The following example demonstrates how to use the ping6 command without any pa-
rameter. It will send 5 ICMPv6 probes to the destination host:
# ping6 2001:DB8::1
PING 2001:DB8::1(2001:DB8::1) 56 data bytes
64 bytes from 2001:DB8::1: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 2001:DB8::1: icmp_seq=2 ttl=64 time=0.028 ms
64 bytes from 2001:DB8::1: icmp_seq=3 ttl=64 time=0.038 ms
64 bytes from 2001:DB8::1: icmp_seq=4 ttl=64 time=0.038 ms
64 bytes from 2001:DB8::1: icmp_seq=5 ttl=64 time=0.051 ms
--- 2001:DB8::1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.027/0.036/0.051/0.010 ms
The following example demonstrates how to use the ping6 command with the “count”
parameter:
The following example demonstrates how to use the ping6 command with the “size”
parameter:
The following example demonstrates how to use the ping6 command with the “source”
The following example demonstrates how to use the ping6 command with the “source”
parameter using interface name:
N/A
Hardware restrictions
N/A
show alarm
Description
Supported Platforms
Syntax
show alarm
Parameters
N/A
Output Terms
Output Description
Name Name of the alarm, prefixed with ’*’ when the alarm is unstable.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
N/A
Hardware restrictions
N/A
show core-dump
Description
Supported Platforms
Syntax
show core-dump
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
show counters
Description
Supported Platforms
Syntax
Parameters
ingress
Value: N/A
egress
Value: N/A
id counter-id
Value: 1 - 256
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has an ingress and an egress user defined counter configured, the
command could result in the following output:
# show counters
INGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
1 vlan100 1024 octets
EGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
1 vlan100 2048 octets
The output of the command when the user specifies the ingress counter-id 1 could look
like this:
# show counters ingress id 1
INGRESS COUNTERS
ID DESCRIPTION VALUE TYPE
--------------------------------
1 vlan100 1024 octets
The values presented by this command are accumulated since the last time the operator
issued a clear command.
Hardware restrictions
The maximum counter value is restricted by the width of the hardware counter storage.
Description
Supported Platforms
Syntax
Parameters
interface-name
Value: {{
Output Terms
Output Description
Output Description
The amount of packets that entered the network interface with errors
In Errors
Out Octets The amount of octets that exited the network interface
Out Broadcast Pkts The amount of packets that exited the network interface to a broad-
cast address
Out Multicast Pkts The amount of packets that exited the network interface to a multi-
cast address
Out Errors The amount of packets with errors in the egress block
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The values presented by this command are accumulated since the last time the opera-
tor issued a clear statistics interface-name command. Because of this, these values
should not be used for accounting or billing. A sample usage of the command is pre-
sented below:
> show interface gigabit-ethernet 1/1/1 statistics
Counter Value
--------------------------
In Octets : 0
In Unicast Pkts : 0
In Broadcast Pkts : 0
In Multicast Pkts : 0
In Discards : 0
In Errors : 0
In Unknown Protos : 0
Out Octets : 0
Out Unicast Pkts : 0
Out Broadcast Pkts : 0
Out Multicast Pkts : 0
Out Discards : 0
Out Errors : 0
The values presented via CLI and Netconf should not be used for accounting or billing
(see usage guidelines for more information).
Hardware restrictions
The maximum counter value is restricted by the width of the hardware counter storage.
Description
Displays information about CPU usage including the overall CPU load per chassi and slot
on the equipment.
Supported Platforms
Syntax
show system cpu [ detail | chassis chassis-id [ slot slot-id [ { load | core [ core-id ]
}]]
Parameters
detail
Value: None.
chassis chassis-id
Value: 1.
slot slot-id
Value: 1.
load
Value: None.
core core-id
Value: 0-1.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Displaying load average of all CPUs, in particular slot, in different interval of time:
Displaying the load average, and also detailed information per-core for each chassis and
slot:
Some minutes after system initialization, the percentage is zero because no information
was generated yet.
Hardware restrictions
None.
Description
Displays system memory information and usage statistics useful for monitoring and trou-
bleshooting.
Supported Platforms
Syntax
Parameters
detail
Value: None.
chassis chassis-id
Value: 1.
slot slot-id
Value: 1.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Release Modification
Usage Guidelines
Report detailed memory information of the line card on slot 1 of chassis 1. There are
four consolidation intervals expressing the trend line of memory consumption in the last
thirty minutes. On non-modular equipments the values for chassi and slot are fixed at 1.
Report detailed memory information of line cards on chassis 1. There are four consolida-
tion intervals expressing the trend line of memory consumption in the last thirty minutes
Report detailed memory information of the entire system. There are four consolidation
intervals expressing the trend line of memory consumption in the last thirty minutes.
None.
Hardware restrictions
None.
Description
Supported Platforms
Syntax
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
The command “uptime” was replaced by “show system uptime”. The old
1.10
command was kept for compatibility.
Usage Guidelines
N/A
N/A
Hardware restrictions
N/A
show tech-support
Description
Supported Platforms
Syntax
Parameters
tech-support
gpon
infra
l2
l3
mpls
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The following example shows how to use the show tech-support without parameters, it
will show all technical support informations:
The following example shows how to use the show tech-support with gpon option, it
will show gpon information more infrastructure informations:
The following example shows how to use the show tech-support with infra option, it
will show infrastructure informations:
The following example shows how to use the show tech-support with l2 option, it will
show layer 2 information more infrastructure informations:
The following example shows how to use the show tech-support with l3 option, it will
show layer 3 information more infrastructure informations:
N/A
Hardware restrictions
N/A
traceroute
Description
Traceroute is a utility for displaying all the hops to reach a destination and measuring
transit delays of packets across an Internet Protocol (IP) network.
Supported Platforms
Syntax
Parameters
ipv4-address
Value: a.b.c.d
vrf name
Description: Specify the source IP address or the interface name from which
packets should be sent.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
# traceroute 10.1.147.55
traceroute to 10.1.147.55 (10.1.147.55), 30 hops max, 60 byte packets
1 10.1.8.1 (10.1.8.1) 1.255 ms 5.530 ms 6.095 ms
2 10.1.63.18 (10.1.63.18) 1.172 ms 2.871 ms 3.436 ms
3 10.1.63.110 (10.1.63.110) 5.423 ms 10.524 ms 12.045 ms
4 10.1.147.55 (10.1.147.55) 0.321 ms 0.326 ms 0.313 ms
The following example demonstrates how to use the traceroute command with the “source”
parameter using interface name:
The following example demonstrates how to use the traceroute command with the “source”
parameter using IP address:
The following example demonstrates how to use the traceroute command with the “vrf”
parameter:
N/A
Hardware restrictions
N/A
traceroute6
Description
Traceroute is a utility for displaying all the hops to reach a destination and measuring
transit delays of packets across an Internet Protocol version 6 (IPv6) network.
Supported Platforms
Syntax
traceroute6 ipv6-address
Parameters
ipv6-address
Value: X:X:X:X::X
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
# traceroute6 2002::1
traceroute to 2002::1 (2002::1) from 2001::1, 30 hops max, 16 byte packets
1 2001::2 (2001::2) 11.438 ms 2.072 ms 1.962 ms
2 2002::1 (2002::1) 1.172 ms 1.327 ms 1.113 ms
As link-local addresses are not routable, the traceroute command with this kind of ad-
dress must fail.
# traceroute6 fe80::204:dfff:fecc:25cb
connect: Invalid argument
N/A
Hardware restrictions
N/A
SNMP
This topic describes the commands related to configuration and use of Simple Network
Management Protocol (SNMP) such as commands to configure communities or to enable
traps.
snmp agent
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
context vrf-name
[ disabled | enabled ]
engine-id
Description: Configures the SNMP agent Engine ID. It is a local and unique
identifier to be used for communication with SNMPv3 Agents
and Managers.
enterprise-number number
Value: 0-4294967295.
from-mac-address mac-address
Value: xx:xx:xx:xx:xx:xx.
from-text text
other string
ip { a.b.c.d | x:x:x:x::x }
max-message-size size
Description: Configures the maximum SNMP agent message size that can be
sent or received.
Value: 484-214748364.
udp-port port
Description: Sets the UDP protocol port to be used for communication with
the SNMP Agents and Managers.
version { v1 | v2c | v3 }
Description: Configures the SNMP agent version. The options are SNMP ver-
sion 1, SNMP version 2c and SNMP version 3. More than one
option can be configured.
Value: { v1 | v2c | v3 }
udp-port port
Description: Port on which SNMP will listen for requests on this interface.
Default
disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
4.4 Removed the option no for SNMP agent enabled and disabled.
Usage Guidelines
This command can be executed directly via CLI. The listen interface allows the configu-
ration of a list of interfaces to listen for SNMP requests. This configuration can be used
for managing SNMP on a VRF.
Example:
This example shows how to configure the SNMP agent using version 2c.
# configure terminal
Entering configuration mode terminal
(config)# snmp agent version v2c
(config)# snmp agent ip 10.1.0.1
(config)# snmp agent enabled
(config)# commit
Commit complete.
This example shows how to configure the SNMP agent listen interfaces.
# configure terminal
Entering configuration mode terminal
(config)# snmp agent listen interface l3-vrf-blue
(config-interface-l3-vrf-blue)# commit
Commit complete.
The SNMP version 3 requires an engine ID. The Enterprise number 3709 is assigned
by IANA to Teracom Telematica Ltda. Be very careful when using a different udp-port
for SNMP agent listen interface in order to avoid conflicts with other protocols, such as
DHCP (67/68), TFTP (69). In these cases SNMP agent listen interface might work but it
can interfere in other protocols. The exception is NTP port (123), that is forbidden to be
used, since it will not work. SNMP agent will always listen on 161 port, even when a listen
interface is configured for another port. In such cases, both ports can be used for SNMP
service. In order to use SNMP agent with VRF mgmt, use SNMP agent IP with the same
IPv4 address as configured in out-of-band management interface (interface mgmt X/Y/Z).
SNMP agent listen interface will only use the interface primary IP address. Secondary IP
address is not supported.
Hardware restrictions
N/A
snmp community
Description
Configures the SNMP communities to be used with managers and agents using version
SNMPv1 or SNMPv2c.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
index
context-map context
name community_name
Value: String.
sec-name security-name
target-tag identifier
Value: String.
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Up to 32 communities can be created.
Example:
N/A
Hardware restrictions
N/A
snmp notify
Description
Configures the SNMP notification for a specific target defined by tag identifier.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
name
tag identifier
Value: String.
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Up to 32 entries can be created. SNMP
notifications can be sent as traps or inform requests. SNMP traps are unconfirmed noti-
fications. SNMP informs are confirmed notifications.
Example:
This example shows how to configure the SNMP notification for the target std_v1_trap.
# configure terminal
Entering configuration mode terminal
(config)# snmp notify std_v1_trap
(config-notify-std_v1_trap)# tag std_v1_trap
(config-notify-std_v1_trap)# commit
Commit complete.
N/A
Hardware restrictions
N/A
snmp system
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
contact text
location loc
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
snmp target
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
name
ip { a.b.c.d | x:x:x:x::x }
usm
user-name name
{ v1 | v2c }
Value: v1 or v2c.
sec-name security-name
engine-id end-id
retries num-retries
Value: 0 - 255.
Default Value: 3.
tag tag-list
Description: (Optional) Specifies the target tag list. A list must be between
brackets “[" and “]”.
Value: String.
timeout time
Value: 0-4294967295.
udp-port port
Description: (Optional) Sets the UDP protocol port to be used for communi-
cation with the SNMP target entity.
Value: 0-65532.
vrf vrf-name
Description: (Optional) Specifies the name of VRF which the target can be
reached.
Value: String.
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Up to 32 entries can be created.
Example:
The parameter engine-id must indicate an Engine ID identifier present in the snmp
usm remote configuration.
Take special care when configuring a different UDP port from default (162), since it must
not conflict with well-known protocols or services, such as SNTP (123) and Syslog (514).
Hardware restrictions
N/A
snmp traps
Description
This configuration allows the selection of traps that will be sent to the snmp target.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
config-commit
Value: N/A
cpu-core
Value: N/A
cpu-load
Value: N/A
link-status
Value: N/A
login-fail
Value: N/A
login-success
Value: N/A
Default
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Hardware restrictions
N/A
snmp usm
Description
Supported Platforms
Syntax
snmp usm { local | remote engine-id } user name [ auth { md5 | sha } { key hexlist
| password pw } [ priv { aes | des } { key hexlist | password pw } ] | security-name
sec-name ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
user name
key hexlist
password pw
security-name sec-name
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Up to 32 local and remote entries can
be created.
Example:
This example shows how to configure a local user based security model.
# configure terminal
Entering configuration mode terminal
(config)# snmp usm local user public
(config-user-public)# auth sha password 12345678
(config-user-public)# commit
Commit complete.
N/A
Hardware restrictions
N/A
snmp vacm
Description
Configures the SNMP group or MIB view based access control model.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
group grp-name
member member-name
access { context }
Description: Configures the SNMP context under which the access rights are
applied.
Description: (Optional) Configures the group access list under which the ac-
cess rights are applied based on the security model.
view view-name
subtree oid
{ excluded | included }
Description: The SNMP family subtree action for this MIB view.
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Up to 32 groups or views can be created.
Example:
This example shows how to configure a SNMP MIB view access control.
# configure terminal
Entering configuration mode terminal
(config)# snmp vacm view root
(config-view-root)# subtree 1.3
(config-subtree-1.3)# included
(config-subtree-1.3)# commit
Commit complete.
N/A
Hardware restrictions
N/A
LICENSE
license
Description
Supported Platforms
Syntax
Parameters
license feature
{ disabled | enabled }
key key
Value: String.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. Please contact the support to consult
the licensable features and how to obtain a key to disable or enable them.
Example:
N/A
Hardware restrictions
N/A
show license
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4370,
DM4610, DM4615, DM4360, DM4380, DM4775, DM4770.
Syntax
show license
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
History
Release Modification
The show command was modified to include the number of licenses avail-
4.9
able for a given feature.
Usage Guidelines
To show the list of licensed features available the following command can be used:
If the number of licenses is not applicable to the feature, “N/A” is displayed.
#show license
Feature Status Number of Licenses
---------- ---------- ------------------
mpls enabled N/A
speed-100g-ports enabled 5
The example below shows the command output when the license is disabled:
#show license
Feature Status Number of Licenses
---------- ---------- ------------------
mpls disabled N/A
speed-100g-ports disabled N/A
N/A
Hardware restrictions
N/A
CHAPTER 4: INTERFACES
This chapter describes the commands related to management of interfaces in the DmOS
CLI.
ETHERNET
This topic describes the commands related to management of Ethernet interfaces such
as commands to configure speed or to disable the interface.
interface forty-gigabit-ethernet
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: chassis/slot/port
Chassis is equal to 1, slot is equal to 1 and port needs to be 1
or 2.
Value: N/A
speed
Value: 40G.
duplex
Value: full.
mdix
Value: normal.
flow-control
advertising-abilities
Description: Set the speed, duplex and flow control modes that will be ad-
vertised on negotiation protocol (for forty-gigabit-ethernet this
option is not available).
description
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command should be used to configure the forty gigabit Ethernet interfaces.
Example:
This example is apllied to id equal to 1/1/1. This id correspond to chassis 1, slot 1 and
port 1.
To set description
Hardware restrictions
interface gigabit-ethernet
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: chassis/slot/port
Chassis is equal to 1, slot is equal to 1 and port needs to be in
the range 1 to 12.
shutdown
Value: N/A
negotiation
Value: N/A
speed
Default Value: 1G for optical ports and 100M for electrical ports.
duplex
Value: full.
mdix
flow-control
advertising-abilities
Description: Set the speed, duplex and flow control modes that will be ad-
vertised on negotiation protocol.
description
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Examples:
These examples are apllied to id equal to 1/1/9. This id correspond to chassis 1, slot
1 and port 9.
To shutdown port
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# shutdown
To enable negotiation
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# negotiation
To set duplex
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# duplex full
To set description
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# description "test interface name"
Or
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# description test_interface_name
Hardware restrictions
interface hundred-gigabit-ethernet
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: chassis/slot/port
Chassis is equal to 1, slot is equal to 1 and port needs to be 1
or 2.
shutdown
Value: N/A
negotiation
Value: N/A
speed
duplex
Value: full.
mdix
Value: normal.
flow-control
mtu
description
fec
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command should be used to configure the hundred gigabit Ethernet interfaces.
Example:
To set description
DM4270(config)# interface hundred-gigabit-ethernet 1/1/1
DM4270(config-hundred-gigabit-ethernet-1/1/1)# description "test interface name"
To set mtu
DM4270(config)# interface hundred-gigabit-ethernet 1/1/1
DM4270(config-hundred-gigabit-ethernet-1/1/1)# mtu 1500
To set fec
DM4270(config)# interface hundred-gigabit-ethernet 1/1/1
DM4270(config-hundred-gigabit-ethernet-1/1/1)# fec cl91
Hardware restrictions
interface ten-gigabit-ethernet
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: chassis/slot/port
Chassis is equal to 1, slot is equal to 1 and port needs to be 1
or 2.
shutdown
Value: N/A
speed
Value: 10G.
duplex
Value: full.
mdix
Value: normal.
flow-control
advertising-abilities
Description: Set the speed, duplex and flow control modes that will be ad-
vertised on negotiation protocol (for ten-gigabit-ethernet this
option is not available).
description
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command should be used to configure the ten gigabit Ethernet interfaces.
Example:
This example is apllied to id equal to 1/1/1. This id correspond to chassis 1, slot 1 and
port 1.
To set description
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# description "test interface name"
Or
DM4610(config)# interface gigabit-ethernet 1/1/9
DM4610(config-gigabit-ethernet-1/1/9)# description test_interface_name
Hardware restrictions
interface twenty-five-gigabit-ethernet
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: chassis/slot/port
Chassis is equal to 1, slot is equal to 1 and port needs to be 1
or 2.
shutdown
Value: N/A
speed
duplex
Value: full.
mdix
Value: normal.
flow-control
mtu
description
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command should be used to configure the twenty-five gigabit Ethernet interfaces.
Example:
To set description
DM4665(config)# interface twenty-five-gigabit-ethernet 1/1/1
DM4665(config-twenty-five-gigabit-ethernet-1/1/1)# description "test interface name"
To set mtu
DM4665(config)# interface twenty-five-gigabit-ethernet 1/1/1
DM4665(config-twenty-five-gigabit-ethernet-1/1/1)# mtu 1500
Hardware restrictions
Description
Description of interfaces.
Supported Platforms
Syntax
Parameters
interface-type
Output Terms
Output Description
CHASSIS ID/SLOT
Interface id referencing chassis/slot/port respectively.
ID/ PORT ID
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
# show interface description
Gigabit Ethernet Interfaces:
CHASSIS
ID/SLOT
ID/PORT
ID Description
--------------------------------------------
1/1/1 My_pretty_name_for_this_interface
1/1/2 LINK_X
1/1/3 -
1/1/4 -
1/1/5 -
1/1/6 -
1/1/7 -
1/1/8 -
1/1/9 -
1/1/10 -
1/1/11 -
1/1/12 -
1/1/13 -
1/1/14 -
1/1/15 -
1/1/16 -
1/1/17 -
1/1/18 -
1/1/19 -
1/1/20 -
1/1/21 -
1/1/22 -
1/1/23 -
1/1/24 -
Ten Gigabit Ethernet Interfaces:
ID/SLOT
ID/PORT
ID Description
------------------------------
1/1/1 A_short_description
1/1/2 -
1/1/3 -
1/1/4 -
Forty Gigabit Ethernet Interfaces:
ID/SLOT
ID/PORT
ID Description
----------------------
1/1/1 UPLINK
1/1/2 -
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
id
Value: chassis/slot/port
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
DM4270# show interface forty-gigabit-ethernet 1/1/1
interface forty-gigabit-ethernet 1/1/1
Configuration:
--------------
Port admin : Enabled
Negotiation : Disabled
Speed : 40G
Duplex : full
Flow-Control : Disabled
MDIX : normal
MTU : 12262
Status:
-------
Link Status : Up
Speed/Duplex : 40Gfull
Flow Control : Disabled
MDIX : Normal
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
id
Value: chassis/slot/port
Output Terms
Output Description
Advertising
The configured advertising abilities.
Abilities
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
DM4050# show interface gigabit-ethernet 1/1/24
interface gigabit-ethernet 1/1/24
Configuration:
--------------
Port admin : Enabled
Negotiation : Enabled
Advertising Abilities : [ 10Mfull 100Mfull 1Gfull ]
MDIX : auto
MTU : 16338
Status:
-------
Link Status : Up
Speed/Duplex : 1Gfull
Flow Control : Disabled
MDIX : Xover
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
id
Value: chassis/slot/port
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
DM4270# show interface hundred-gigabit-ethernet 1/1/1
interface hundred-gigabit-ethernet 1/1/1
Configuration:
--------------
Port admin : Enabled
Negotiation : Disabled
Speed : 100G
Duplex : full
Flow-Control : Disabled
MDIX : normal
FEC : off
MTU : 12262
Status:
-------
Link Status : Up
Speed/Duplex : 100Gfull
Flow Control : Disabled
MDIX : Normal
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
interface-type
Output Terms
Output Description
CHASSIS ID/SLOT
Interface id referencing chassis/slot/port respectively.
ID/ PORT ID
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Release Modification
Usage Guidelines
Example:
# show interface link
Gigabit Ethernet Interfaces:
CHASSIS
ID/SLOT
ID/PORT Disabled Blocked Parent
ID Link Shutdown Speed Duplex by by LAG
-------------------------------------------------------------------
1/1/1 Down false - - [ LAG ] - lag-1
1/1/2 Down false - - - - -
1/1/3 Down false - - - - -
1/1/4 Down false - - - - -
1/1/5 Down false - - - - -
1/1/6 Down false - - - - -
1/1/7 Down false - - - - -
1/1/8 Down false - - - - -
1/1/9 Down false - - - - -
1/1/10 Down false - - - - -
1/1/11 Down false - - - - -
1/1/12 Down false - - - - -
1/1/13 Down false - - - - -
1/1/14 Down false - - [ LAG ] - lag-1
1/1/15 Down false - - [ LAG ] - lag-1
1/1/16 Up false 1G full - [ LBD ] -
1/1/17 Down false - - - - -
1/1/18 Up false 1G full - - -
1/1/19 Down false - - - - -
1/1/20 Up false 1G full - [ CFM ] -
1/1/21 Down false - - - - -
1/1/22 Down false - - - - -
1/1/23 Down false - - - - -
1/1/24 Down false - - - - -
Ten Gigabit Ethernet Interfaces:
CHASSIS
ID/SLOT
ID/PORT Disabled Blocked Parent
ID Link Shutdown Speed Duplex by by LAG
-------------------------------------------------------------------
1/1/1 Down false - - [ LAG ] - lag-2
1/1/2 Down false - - - - -
1/1/3 Down false - - - - -
1/1/4 Down false - - [ LAG ] - lag-2
Forty Gigabit Ethernet Interfaces:
CHASSIS
ID/SLOT
ID/PORT Disabled Blocked Parent
ID Link Shutdown Speed Duplex by by LAG
-----------------------------------------------------------------------
1/1/1 Up false 40G full - [ EFM,CFM ] -
1/1/2 Up false 40G full - - -
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
id
Value: chassis/slot/port
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
id
Value: chassis/slot/port
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
DM4665# show interface twenty-five-gigabit-ethernet 1/1/1
interface twenty-five-gigabit-ethernet 1/1/1
Configuration:
--------------
Port admin : Enabled
Negotiation : Disabled
Speed : 25G
Duplex : full
Flow-Control : Disabled
MDIX : normal
MTU : 12262
Status:
-------
Link Status : Up
Speed/Duplex : 25Gfull
Flow Control : Disabled
MDIX : Normal
N/A
Hardware restrictions
N/A
L3
This topic describes the commands related to management of L3 logical interfaces such
as commands to configure IP address and bind it to lower layer interface, e.g., VLAN.
interface l3
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
if-name
description if-description
Value: a.b.c.d/x.
Value: a.b.c.d/x.
ipv6 enable
Value: N/A
Value: x:x:x:x::x/y.
eui-64
Description: Sets 64-bit Extended Unique Identifier for specific IPv6 prefix on
logical interface.
Value: N/A
ip-mtu mtu-size
Value: 68-9000.
lower-layer-if if-type
Value: { vlan }
if-id
vlan-link-detect enabled
Value: N/A
vlan-link-detect disabled
Value: N/A
ipv6 nd ra suppress
Value: N/A
Value: x:x:x:x::x/y.
Value: N/A
Value: N/A
Description: When disabled, indicates that this prefix can be used for on-link
determination on L3 interface.
Value: N/A
Value: Must be no less than 4 seconds and no greater than 1800 sec-
onds.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The name of L3 logical interface must be unique across interfaces and it will be used as
key to be referenced from other features.
It is possible the use of one primary IPv4 address, up to three secondary IPv4 addresses
and two IPv6 addresses per L3 logical interface. The products DM4370 and DM4360
support only one secondary IPv4 address.
Command to configure IPv6 addresses will be available only if ipv6 enable is set for
interface. Example below shows that IPv6 address configuration option appears after
ipv6 enable is set.
(config-l3-test)# ipv6 ?
Possible completions:
enable Enable IPv6 on interface
!
(config-l3-test)# ipv6 enable
!
(config-l3-test)# ipv6 ?
Possible completions:
address IPv6 address
enable Enable IPv6 on interface
!
Currently it is only possible to associate the logical interface with lower layer of type
VLAN.
To find which L3 logical interface is configured with a specific IPv4 address or a specific
VLAN ID, it is possible to use the commands showed in the example below.
Example:
This example shows how to find an L3 logical interface using an IPv4 address as pa-
rameter:
# show running-config interface l3 | include -b 2 192.168.1.1
5-interface l3 example2
6- lower-layer-if vlan 200
7: ipv4 address 192.168.1.1/24
Or in configuration mode:
(config)# show interface l3 | include -b 2 192.168.1.1
5-interface l3 example2
6- lower-layer-if vlan 200
7: ipv4 address 192.168.1.1/24
This example shows how to find an L3 logical interface using a VLAN ID as parameter:
# show running-config interface l3 | include -b 1 -a 1 "vlan 300"
9-interface l3 example3
10: lower-layer-if vlan 300
11- ipv4 address 192.168.2.1/24
Or in configuration mode:
(config)# show interface l3 | include -b 1 -a 1 "vlan 300"
9-interface l3 example3
10: lower-layer-if vlan 300
11- ipv4 address 192.168.2.1/24
The ip-mtu is restricted to control plane. Therefore, it does not have any effect on the
data plane.
Hardware restrictions
N/A
interface l3 vrf
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
if-name
vrf vrf-name
Description: Specifies the name of the VRF this interface will be associated
with. It is not possible to associate the VRF ‘mgmt’ to an L3
interface. Also, the VRF ‘global’ cannot be directly configured
as it is the default VRF when no VRF is associated.
Value: string.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
If no VRF is explicitly associated with the L3 interface, it is associated with the global
VRF by default. The following example shows how to associate an L3 interface with the
‘test_vrf’ VRF:
(config-l3-vlan100)# ?
Possible completions:
vrf Assign a VRF instance to the interface
!
(config-l3-vlan100)# vrf ?
Possible completions:
<WORD> VPN Routing/Forwarding instance name
test_vrf
!
(config-l3-vlan100)# vrf test_vrf
(config-l3-vlan100)# commit
Commit complete.
Once the VRF associated with an L3 interface is changed, any route in the previous VRF
using it as output interface will be uninstalled. In order to keep the connectivity, you will
need to configure the routes in the new VRF.
Hardware restrictions
N/A
show ip interface
Description
Shows the list of interfaces configured with IPv4 addresses and associated information.
Supported Platforms
Syntax
Parameters
vrf vrf-name
brief
Value: N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the global IPv4 interfaces, the following command can be used:
Example:
To show interfaces configured with IPv4 addresses in all VRFs, the following
command can be used:
Example:
To show interfaces configured with IPv4 addresses in a specific VRF, the following
command can be used:
Example:
N/A
Hardware restrictions
N/A
Description
Shows the list of interfaces configured with IPv6 addresses and associated information.
Supported Platforms
Syntax
Parameters
vrf vrf-name
brief
Value: N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the IPv6 interface brief, the following command can be used:
Example:
To show interfaces configured with IPv6 addresses in all VRFs, the following
command can be used:
Example:
To show interfaces configured with IPv6 addresses in a specific VRF, the following
command can be used:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show router VRRP operational information brief, the following command can
be used:
Example:
N/A
Hardware restrictions
N/A
LOOPBACK
This topic describes the commands related to management of Loopback logical inter-
faces such as commands to configure IP address.
interface loopback
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: 0-7.
description if-description
Value: a.b.c.d/x.
ipv6 enable
Value: N/A
Value: x:x:x:x::x/y.
eui-64
Description: Sets 64-bit Extended Unique Identifier for specific IPv6 prefix on
interface loopback.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The identifier of Loopback logical interface must be within the valid range of 0 and 7.
It is possible the use of only one IPv4 per Loopback logical interface and two IPv6 ad-
dresses
To find which Loopback logical interface is configured with a specific IPv4 address, it is
possible to use the commands showed in the example below.
Example:
This example shows how to find a Loopback logical interface using address as parameter:
# show running-config interface loopback all | include -b 2 200.200.200.1
3-interface loopback 3
4: ipv4 address 200.200.200.1/32
Or in configuration mode:
(config)# show interface loopback all | include -b 2 200.200.200.1
3-interface loopback 3
4: ipv4 address 200.200.200.1/32
This example shows how to find Loopback logical interface IPv6 addresses:
# show ipv6 interface brief
Interface-name Logical-interface Address Scope State
-----------------------------------------------------------------
loopback 0 loopback 0 2001:db8::1/32 global active
Command to configure IPv6 addresses will be available only if ipv6 enable is set for
interface. Example below shows that IPv6 address configuration option appears after
ipv6 enable is set.
(config-loopback-4)# ipv6 ?
Possible completions:
enable Enable IPv6 on interface
!
(config-loopback-4)# ipv6 enable
!
(config-loopback-4)# ipv6 ?
Possible completions:
address IPv6 address
enable Enable IPv6 on interface
!
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
id
Value: 0-7.
vrf vrf-name
Description: Specifies the name of the VRF this interface will be associated
with. It is not possible to associate the VRF ‘mgmt’ to a loop-
back interface. Also, the VRF ‘global’ cannot be directly config-
ured as it is the default VRF when no VRF is associated.
Value: string.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
If no VRF is explicitly associated with the loopback interface, it is associated with the
global VRF by default. The following example shows how to associate a loopback inter-
face with the ‘test_vrf’ VRF:
(config-loopback-7)# ?
Possible completions:
vrf Assign a VRF instance to the interface
!
(config-loopback-7)# vrf ?
Possible completions:
<WORD> VPN Routing/Forwarding instance name
test_vrf
!
(config-loopback-7)# vrf test_vrf
(config-loopback-7)# commit
Commit complete.
N/A
Hardware restrictions
N/A
MAC LEARNING
This topic describes the commands related to management of learning conditions such
as commands to configure the aging or to inspect the MAC address table.
clear mac-address-table
Description
The clear mac-address-table command is used to clear entries learned by the switch.
Supported Platforms
Syntax
clear mac-address-table
Parameters
interface interface-name
Default
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
# clear mac-address-table
Clear confirmation will be asked for the user, once this is a permanent action.
Hardware restrictions
N/A
mac-address-table aging-time
Description
The mac-address-table aging-time command is used to set the global maximum time
that MAC table entries will be stored in the MAC address table without a hit.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
aging-time
Value: 20 to 2000000
0 disables MAC address aging
Default
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
(config)#
(config)# mac-address-table aging time 500
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
learning
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
(config)#
(config)# mac-address-table interface gigabit-ethernet-1/1/1 learning enabled
This command clears all dynamically learned MAC entries on the configured interface.
Be careful disabling MAC address learning when storm control unicast is configured on
the same interface, it may occur a data loss due to DLF packet flood.
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4270, DM4775, DM4770,
DM4380.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
entries
Value: 0 to 16000
0 to disable MAC address learning and data traffic
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
(config)#
(config)# mac-address-table interface gigabit-ethernet-1/1/1 limit maximum 10
This command clears all dynamically learned MAC entries on the configured interface, so
a momentaneous data loss can occur.
When used within the vlan mac-limit, the most restrictive rule will be considered.
Hardware restrictions
N/A
Description
The mac-address-table vlan vlan-id limit command is used to set the maximum MAC
address table entries that can be learned for the specified VLAN.
Supported Platforms
This command is not supported in the following platforms: DM4270, DM4775, DM4770,
DM4380.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: { 1 to 4094 }
entries
Value: 0 to 16000
0 to disable MAC address learning and data traffic
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
(config)#
(config)# mac-address-table vlan 15 limit maximum 10
This command clears all dynamically learned MAC entries on the configured VLAN, so a
momentaneous data loss can occur.
When used within the interface mac-limit, the most restrictive rule will be considered.
Hardware restrictions
N/A
show mac-address-table
Description
Supported Platforms
Syntax
show mac-address-table
Parameters
None
Value: N/A
interface interface-name
mac-address address
Value: XX:XX:XX:XX:XX:XX
vlan vlan-id
Value: 1-4094
type entry-type
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
VLAN
This topic describes the commands related to the management of 802.1Q Virtual Bridged
LAN and to the management of VLAN extensions such as commands to configure Q-in-Q,
dynamic VLANs and VLAN Translations.
dot1q vlan
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1 - 4094
name vlan-name
Value: 1 - 32 characters
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
When entering the VLAN configuration tree, the VLAN itself is created if it does not exist.
VLANs can be created in ranges, or list. The following command will create VLANs from
10 to 20 and VLAN 30 and assing a name to all of them:
The following command will destroy the VLAN and its members:
VLANs must be created before being used by others features on their configurations.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1 - 4094
interface interface-name
tag-mode
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The following command adds gigabit-ethernet 1/1/1 interface tagged in the VLAN 1:
Hardware restrictions
N/A
show vlan
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
membership
Value: N/A
detail
Value: N/A
vlan id
Value: 1-4094
Output Terms
Output Description
Port state of the interface for this vlan. Can be set by protocolos such
PORT STATE as RSTP, EAPS and ERPS. The possible states are Disabled, Learning,
Forwarding and Blocked.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
switchport acceptable-frame-types
Description
This configuration allows the interface to choose between tagged, untagged and all
frames to be accepted. By default all frames either tagged with a IEEE 802.1Q header or
not are accepted.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
acceptable-frame-types type-value
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The example below shows the configuration of acceptable-frame-types for a given inter-
face.
# config
Entering configuration mode terminal
(config)# switchport interface gigabit-ethernet-1/1/1
(config-switchport-gigabit-ethernet-1/1/1)# acceptable-frame-types tagged
(config-switchport-gigabit-ethernet-1/1/1)# commit
Commit complete.
Hardware restrictions
N/A
switchport native-vlan
Description
Defines a native VLAN ID to be added in all untagged packets received in ingress mode
in the given interface.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
vlan-id native-vlan-id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
To configure a native-vlan the interface must be either valid and untagged member of
the VLAN ID being used for native vlan. The VLAN ID which will be added must exists.
The example below shows the creation of a native-vlan for the given interface.
# config
Entering configuration mode terminal
(config)# dot1q vlan 100
(config-vlan-100)# interface gigabit-ethernet-1/1/1
(config-dot1q-interface-gigabit-ethernet-1/1/1)# untagged
(config-vlan-100)# top
(config)# switchport interface gigabit-ethernet-1/1/1
(config-switchport-gigabit-ethernet-1/1/1)# native-vlan vlan-id 100
(config-switchport-interface-native-vlan)# commit
Commit complete.
successfully.
When an invalid interface or VLAN ID is used, the user is warned about the error during
commit step.
Hardware restrictions
N/A
switchport pcp
Description
Defines a 802.1p priority (PCP) to be added for untagged packets or for QinQ packets
within the native VLAN-ID.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
pcp pcp-value
Value: 0-7
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The example below shows the configuration of a pcp for the given interface.
# config
Entering configuration mode terminal
(config)# dot1q vlan 100
(config-vlan-100)# interface gigabit-ethernet-1/1/1
(config-dot1q-interface-gigabit-ethernet-1/1/1)# untagged
(config-vlan-100)# top
(config)# switchport interface gigabit-ethernet-1/1/1
(config-switchport-gigabit-ethernet-1/1/1)# native-vlan vlan-id 100
(config-switchport-interface-native-vlan)# exit
(config-switchport-gigabit-ethernet-1/1/1)# pcp 2
(config-switchport-interface-pcp)# commit
Commit complete.
Hardware restrictions
N/A
switchport qinq
Description
Enables VLAN QinQ mode for the packets received on this interface. When enabled, the
received packets will get an extra IEEE 802.1Q header, that is created using the native
VLAN ID and default values for TPID (0x8100), priority code point(0) and drop eligible
information (0). Usually this enclosing VLAN ID is usually refered as S-VLAN.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
qinq
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The interface must have a valid configuration for native VLAN. The example below shows
the configuration of QinQ for a given interface and its pre-conditions.
# config
Entering configuration mode terminal
(config)# dot1q vlan 50
(config-vlan-50)# interface gigabit-ethernet-1/1/1 untagged
(config-dot1q-interface-gigabit-ethernet-1/1/1)# top
(config)# switchport interface gigabit-ethernet-1/1/1
(config-switchport-gigabit-ethernet-1/1/1)# native-vlan vlan-id 50
(config-switchport-interface-native-vlan)# exit
(config-switchport-gigabit-ethernet-1/1/1)# qinq
(config-switchport-gigabit-ethernet-1/1/1)# commit
Commit complete.
When an invalid interface or VLAN ID is used, the user is warned about the error during
commit step.
Hardware restrictions
N/A
switchport tpid
Description
Configures tag protocol identifier(TPID) accepted for VLAN tagged frames. Only frames
received with the configured TPID are considered as tagged frames. Also, tagged frames
sent by the configured interface will have the configured TPID.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
tpid tpid-value
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The example below shows the configuration of TPID for a given interface.
# config
Entering configuration mode terminal
(config)# switchport interface gigabit-ethernet-1/1/1
(config-switchport-gigabit-ethernet-1/1/1)# tpid 0x88a8
(config-switchport-gigabit-ethernet-1/1/1)# commit
Commit complete.
Hardware restrictions
N/A
vlan-mapping
Description
Create or update VLAN mapping rules to add or replace a VLAN tags when match criteria
is met.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
stage
rule rule-name
match
Description: Parameters after match and before action describe the type
of flow selected to be modified.
Value: N/A
Value: 1 - 4094
inner-action replace
Value: replace
Description: VLAN ID that will be added or replaced into the outer VLAN tag
of the packet.
Value: 1 - 4094
Description: VLAN ID that will be replaced into the inner VLAN tag of the
packet.
The value copy may be configured, and it will keep the current
VLAN ID in the inner VLAN tag.
pcp pcp
Description: VLAN PCP (802.1p) field value that will be added into packet for
outer or inner VLAN tag. It can be the numeric priority value or
the copy from the PCP value from the existing VLAN tag.
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Remove restriction of using action add without QinQ enabled for DM4270,
5.10
DM4775, DM4770 and DM4380 series.
Usage Guidelines
To configure a VLAN mapping rule the interface must be a valid one. Also, the VLAN that
will replace the original one in the VLAN tag must exist. The example below shows the
creation of a rule with replace action.
# config
(config)# dot1q vlan 100
(config-vlan-100)# interface gigabit-ethernet-1/1/1
(config-interface-gigabit-ethernet-1/1/1)# top
(config)# vlan-mapping interface gigabit-ethernet-1/1/1 ingress rule RULE1
(config-rule-RULE1)# match vlan vlan-id 1 action replace vlan vlan-id 100
(config-rule-RULE1)# commit
Commit complete.
(config-rule-RULE1)# end
#
Hardware restrictions
DM4050 and DM4250 series do not support PCP copy on ingress rules.
DM4050 and DM4250 series do not support inner-action.
On DM4270, DM4775, DM4770 and DM4380 series, VLAN mapping rules do not act over
packets modified by ACL.
On DM4270, DM4775, DM4770 and DM4380 series, VLANs associated with L3 interfaces
cannot be used for ingress VLAN Mapping rules when there is no QinQ enabled, except
when both the match and action VLANs are the same.
On DM4270, DM4775, DM4770 and DM4380 series, VLAN mapping rules with action add
do not act over double-tagged packets when the ingress interface has QinQ disabled.
LINK AGGREGATION
clear lacp
Description
The clear lacp command is used to reset statistics about Link Aggregation Control Pro-
tocol (LACP).
Supported Platforms
Syntax
Parameters
all
Value: N/A
lag id id
Value: 1-32
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
It is only possible to clear statistics for link-aggregations controlled by LACP, i.e., link-
aggregations configured in active or passive modes.
Hardware restrictions
N/A
link-aggregation
Description
Link aggregation bundles individual ethernet links into a single logical link. It may be
used for redundancy or to expand bandwidth capacity. It is controlled by Link Aggrega-
tion Control Protocol (LACP).
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
system-priority priority
Value: 0-65535
Description: Sets the global load balance hash function for enhanced and
dynamic mode.
Value: 1-32
load-balance type
maximum-active links
Value: 1-16
Default Value: 16
minimum-active links
Description: Sets the minimum number of links required to bring up this LAG
interface.
If less interfaces are active than the minimum-active links, the
LAG interface itself will be considered inactive. The maximum
value for this parameter may be lower depending on the prod-
uct model.
Value: 1-16
Default Value: 1
mode lacp-mode
period period-interval
Description: Sets the interval period of LACP for this LAG, short ( 1s ) or long
( 30s ).
Short option allows a faster link detection/recovery.
Preferably both nodes must be set with the same value.
description
interface interface-name
port-priority priority
Value: 0-65535
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
Example:
In active or passive modes the interface selection criteria follows the following path
of comparisons: System Priority -> System MAC -> Port Priority -> Port ID. In priority
comparisons, numerically lower values have higher priority.
This means that the interfaces of the equipment with lower System Priority will be used
for standby selection, according to it’s Port Priority and Port ID. If System Priority is the
same on both equipments, the equipment with lower System MAC will use it’s interfaces
to decide standby selection, according to it’s Port Priority and Port ID.
Hardware restrictions
When load-balance enhanced is used, the platform DM4050 only supports non-unicast
(broadcast, multicast and unknown unicast) load-balance based on source and desti-
nation MAC addresses. Others load-balance criteria like source and destination IP and
TCP/UDP ports are not available.
show link-aggregation
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
extensive
Value: N/A
interfaces
Value: N/A
lacp
Value: N/A
statistics
Value: N/A
Output Terms
Output Description
Indicates whether this LAG member is active in the LAG. The possi-
bles values are:
active - the member is aggregated in the LAG.
Indicates the operation mode for a LAG, three options are available:
static - LAG is configured statically by user;
Output Description
LACPDUs
Indicates the number of sent or received PDUs in an interface.
Sent/Received
Indicates the elapse time (in seconds) since the statistics of this in-
Cleared(s)
terface were cleared.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
SPANNING-TREE
show spanning-tree
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
Output Terms
Output Description
Cost (Root ID) The cost configured for a port from Root.
Hello Time Time interval that the root bridge will generate BPDUs.
The maximum length of time that passes before a bridge port saves
Max Age
its configuration BPDU information.
Bridge ID Designated Bridge ID used for sending and receiving STP BPDUs.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
Designated
Interface Port Prio Cost Sts Cost Bridge ID Port
--------- ---- ---- ---- --- ---- ----------------------- ----
gigabit-ethernet-1/1/1 0 128 100 DIS 0 0 00:00:00:00:00:00 0
N/A
Hardware restrictions
N/A
spanning-tree
Description
The Spanning Tree Protocol (STP) is a network protocol that prevents loops from occurring
in the network topology. Spanning tree also allows a network design to include redundant
links to provide automatic backup paths.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
bridge-priority priority
Description: The bridge priority for this instance. When using the MSTP
mode, this parameter is used as the CIST bridge priority.
Value: 0-61440
forward-delay seconds
Value: 4-30
Default Value: 15
hello-time seconds
Description: Value that all bridges will use for the hello time if this bridge is
acting as root.
Value: 1-10
Default Value: 2
Description: Value that all bridges will use for the max age of BPDUs if this
bridge is acting as root.
Value: 6-40
Default Value: 20
mode version
name identifier
revision number
Value: 0-65535
Default Value: 0
Description: The value used by port to limit the maximum BPDU transmis-
sion rate.
Value: 1-10
Default Value: 6
Description: Value that all bridges will use for the max age of BPDUs if this
bridge is acting as root.
Value: 6-40
Default Value: 20
Value: 6-40
Default Value: 20
interface name
cost number
Value: 1-200000000
port-priority number
Value: 0-240
link-type type
restricted-role
Description: Restricted role configuration for the port. Also known as root
guard. When enable for an interface that would be choosen as
root port, this interface will be blocked instead.
Value: N/A
restricted-tcn
Description: Restricts the propagation of topology changes for the port. Topol-
ogy change notifications received on the interface are not prop-
agated to other interfaces.
Value: N/A
edge-port
Description: Administrative edge port configuration for the port. When con-
figured, auto-edge configuration is ignored.
Value: N/A
auto-edge
Value: N/A
bpdu-guard
Description: Enables bpdu-guard for the port. When enable, if an edge port
receives a BPDU, the port role is set to disable and port state
is set to discarding. Bpdu-guard parameter only can be set if
edge-port is also set.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
The maximum age timer controls the maximum length of time that passes before a
bridge port saves its configuration BPDU information. The switch that is at the periphery
of the network does not time out the root information under stable conditions. So, the
maximum age requires the coherence (2x(hello-time) <= age <= 2x(forward-delay - 1)).
Hardware restrictions
N/A
spanning-tree mst
Description
Supported Platforms
Syntax
spanning-tree mst id [priority priority] [vlan vlans] [interface name [cost number]
[port-priority number]]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mst id
Value: 1-64
priority priority
Value: 0-61440
vlan vlans
Description: Sets the list of protected VLANs of this MST instance. Ranges
of VLANs or single VLAN are allowed and can be combined to
specify the set of protected VLANs
Value: 1-4094
Example: protected-vlans 1-3,5,7-9
interface name
cost number
Description: Path cost configuration for the port in this MST instance.
Value: 1-200000000
port-priority number
Value: 0-240
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
ERPS
This topic describes the commands related to management of G.8032 ERPS topologies
such as commands to configure the RPL or to inspect the protection status.
erps ring
Description
Supported Platforms
Syntax
erps ring ring-name timers [ guard milliseconds | hold-off milliseconds | wtr minutes
]*
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Description: Sets a textual name for this ERPS ring instance, according to
the network manager’s choice. Valid characters are A-Z, a-z,
0-9 and + _ - “.
Description: Sets the ring identifier used for control traffic (ERPS PDUs).
Value: 1-239
Description: Sets the VLAN used for control traffic (ERPS PDUs).
Value: 1-4094
Description: Sets the list of VLANs protected by this ERPS ring instance.
VLAN ranges or single VLANs are allowed and can be combined
to specify the set of protected VLANs.
Value: 1-4094
Example: protected-vlans 1-3,5,7-9
Description: Sets the R-APS level of PDUs exchanged by this ring instance.
Value: 0-7
Default Value: 0
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet, lag.
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet, lag.
Description: Sets the ring instance’s virtual-channel. Only port1 can be set
as virtual-channel. This configuration is available only when
ring-type parameter is set to sub-ring and node parameter is
set to interconnection.
Value: 1-4094
Description: Sets the RPL role of the first ring instance’s port.
Description: Sets the RPL role of the second ring instance’s port.
Default Value: 0
Value: 1-12
Default Value: 5
Description: Sets the node-type for this ring instance. This configuration is
available only when ring-type parameter is set to sub-ring.
Description: Sets the parent-ring for this ring instance. This configuration is
available only when ring-type parameter is set to sub-ring.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
(erps-ring-timers)#hold-off 2000
(erps-ring-timers)#exit
(erps-ring-Foo)#port0 interface ten-gigabit-ethernet-1/1/1
(erps-ring-port0)#exit
(erps-ring-Foo)#port1 interface lag-1
(erps-ring-port1)#top
(config)#commit
Commit complete.
(config)#
Changes on specific configurations will cause a protocol reset for the affected rings,
namely: ring ID and control VLAN. Traffic on the protected VLANs will be affected.
Before mounting a physical ring, please consider disabling, in the node that is going
to be designated as the RPL owner node, the port that represents the RPL end point.
To add a new protected VLAN, you must add it to the protected VLANs list of the ERPS
ring before adding the ring ports to the VLAN domain (dot1q vlan id interface name).
Before removing a VLAN from the ERPS list of protected VLANs, you must first remove
the ring ports from that VLAN domain (no dot1q vlan id interface name).
To physically add a new node in the ERPS ring, it is recommended to disable (shut-
down) the adjacent port of the neighbors’ nodes of the ring node that is being added.
After making all the connections and configurations of the new ring node, enable (no
shutdown) the adjacent ports to finish the procedure.
To physically remove a node from the ERPS ring, it is recommended to disable (shut-
down) the adjacent port of the neighbors’ nodes of the ring node that is being re-
moved. After the ring node removal, enable (no shutdown) the adjacent ports to finish
the procedure.
The ports of an ERPS ring must be members, and the only members, of its control-vlan.
A control-vlan of an ERPS ring cannot exist in the protected-vlan list of any ERPS ring
or EAPS domain.
The protected-vlan list of an ERPS ring cannot overlap the protected-vlan list of another
ERPS ring or EAPS domain.
The same protected-vlan list can be used in different ERPS rings or EAPS domains as
long as the protected ports are different.
Hardware restrictions
N/A
show erps
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Description: This parameter displays all that the brief parameter displays
plus a table listing the the number of protected VLANs, the ring
ports, and their RPL roles. When no parameter is given the show
command displays the same content of detail parameter.
Value: N/A
Output Terms
Output Description
Output Description
CONTROL VLAN The VLAN used for ERPS control packets, in this ring instance.
The current state of the ring instance. The possible states are Init,
STATE
Idle, Protection, ManualSwitch, ForcedSwitch, and Pending.
The RPL role of the second ring instance’s port. Possible values are
PORT0 RPL ROLE
owner, neighbor, and none.
The state of the port. Possible values are Forward, Blocked, Data
PORT0 STATE
Blocked, Control Channel Blocked and Unknown.
PORT0 LOCAL
Inform if the port has a local failure. Possible values are Yes and No.
FAILURE
The RPL role of the second ring instance’s port. Possible values are
PORT1 RPL ROLE
owner, neighbor, and none.
The state of the port. Possible values are Forward, Blocked, Data
PORT1 STATE
Blocked, Control Channel Blocked and Unknown.
PORT1 LOCAL
Inform if the port has a local failure. Possible values are Yes and No.
FAILURE
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has 5 ring instances, the brief status command could result in the
following output:
# show erps brief
RING CONTROL PORT0 PORT1
NAME ID VLAN STATE STATE STATE
------------------------------------------------------
MyRing1 1 11 Protection Forward Blocked
MyRing2 2 21 Idle Forward Blocked
MyRing3 15 151 Protection Forward Forward
MyRing4 15 152 Protection Forward Forward
MyRing5 3 31 Pending Forward Blocked
#
None
Hardware restrictions
None
EAPS
This topic describes the commands related to management of EAPS topologies such as
commands to configure the protected VLANs or to inspect the protection status.
eaps
Description
The current implementation follows the EAPS version 1.3 described as a Internet-Draft,
which includes some enhancements over the EAPS version 1 described by RFC 3619.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
eaps domain
Value: 0-63
control-vlan vlan-id
Description: Sets the VLAN used for control traffic (EAPS PDUs). This VLAN
cannot be used for data traffic.
Value: 1-4094
failtime seconds
Value: 1-60
Default Value: 3
failtime-action action-type
Value: { send-alert }
hellotime seconds
Value: 1-60
Default Value: 1
Description: Sets the EAPS mode of this ring node. A ring is allowed to have
a single Master node and multiple Transit nodes.
name identifier
Description: Set a textual name for this EAPS domain, according to the net-
work manager’s choice. Valid characters are A-Z, a-z, 0-9 and
+_-"
Value: NA
Default Value: NA
primary interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet, lag.
secondary interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet, lag.
protected-vlans vlans
Description: Sets the list of protected VLANs of this EAPS domain. Ranges
of VLANs or single VLAN are allowed and can be combined to
specify the set of protected VLANs
Value: 1-4094
Example: protected-vlans 1-3,5,7-9
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Changes on specific configurations will cause a protocol reset for the affected domains,
namely: primary or secondary port, control-vlan and mode. Traffic on the protected
VLANs will be affected.
Before mounting a physical ring, please consider disabling the secondary port of the
Master node.
To add a new protected VLAN, you must add it to the protected VLAN list of the EAPS
domain before adding the ring ports to the VLAN domain (dot1q vlan id interface
name).
Before removing a VLAN from the EAPS list of protected VLANs, you must first remove
the ring ports from that VLAN domain (no dot1q vlan id interface name).
To physically add a new node in the EAPS ring, it is recommended to disable (shut-
down) the adjacent port of the neighbors nodes of the ring node that is being added.
After making all the connections and configurations of the new ring node, enable (no
shutdown) the adjacent ports to finish the procedure.
To physically remove a node from the EAPS ring, it is recommended to disable (shut-
down) the adjacent port of the neighbors nodes of the ring node that is being removed.
After the ring node removal, enable (no shutdown) the adjacent ports to finish the pro-
cedure.
Hardware restrictions
N/A
show eaps
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Description: This parameter displays all that the brief parameter displays
plus a table listing the protected VLANs and both the primary
and secondary ports. When no parameter is given the show
command displays the same content of detail parameter.
Value: N/A
Output Terms
Output Description
The current state of the domain. The possible states are Idle, Init,
State
Complete, Failed, Pre Forwarding, Links Down and Links Up.
The state of the domain’s primary port, where Up and Down refer
Primary port state
to port link status and Enable and Blocked refer to the port traffic
block state.
The state of the domain’s secondary port, where Up and Down refer
Secondary port
to port link status and Enable and Blocked refer to the port traffic
state
block state.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the domains 0, 1, 2, 3, 4, 5 and 63 created, let’s see the brief
information:
# show eaps brief
PRIMARY PORT SECONDARY
ID NAME STATE MODE STATE PORT STATE
----------------------------------------------------------------------------
0 My-Eaps-Domain-0 Idle transit Down Blocked Down Blocked
1 My-Eaps-Domain-1 Init master Up Enabled Up Blocked
2 My-Eaps-Domain-2 Complete master Up Enabled Up Blocked
3 My-Eaps-Domain-3 Failed master Down Enabled Up Blocked
4 My-Eaps-Domain-4 Pre Forwarding transit Up Enabled Up Blocked
5 My-Eaps-Domain-5 Links Down transit Up Enabled Down Blocked
63 My-Eaps-Domain-63 Links Up transit Up Enabled Up Enabled
#
None
Hardware restrictions
None
CONTROL PROTOCOLS
This topic describes the commands related to management of control protocol such as
commands to enable PDU tunnel, drop, peer and forward of some specific protocol.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
protocols
Value: { extended | lacp | marker | oam | stp | pvst | lldp | pagp | udld
| cdp | vtp | eaps | erps | gvrp | dot1x }
action action-type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Added support for LLDP tunneling and action Forward for extended tun-
4.9
neling.
5.2 Added support for tunneling protocols PAGP, UDLD, CDP and VTP.
5.4 Added support for tunneling protocols EAPS, ERPS, GVRP and Dot1x.
Usage Guidelines
When action parameter is configured as tunnel, the equipment will not be in accordance
with the “Frame Filtering” section from IEEE 802.1Q standard.
Features such as STP, EAPS and others that have their controls protocols packets im-
pacted will not work together with action tunnel.
ACL action “deny” does not affect tunneled packets.
When enabling Protocol tunnelings for an access interface, it is recommended to config-
ure the same tunneling modes for all access interfaces within the same VLAN.
Hardware restrictions
N/A
layer2-control-protocol tunnel-mac
Description
Allows to set the destination MAC address for tunneled packets on modes LACP, Marker,
OAM and STP.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
tunnel-mac mac
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
layer2-control-protocol tunnel-priority
Description
Allows to set the PCP (802.1p) and QoS Scheduler Queue for tunneled packets.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
tunnel-priority priority
Description: Set PCP (802.1p) and QoS Scheduler Queue for tunneled pack-
ets.
Value: { 0-7 }
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The tunnel-priority takes precedence over the priority from ACL action “set pcp”.
Hardware restrictions
N/A
Description
Command used to configure PDU on preexisting VLAN configured with service/VLAN TLS.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1 - 4094
protocols
Value: extended
action action-type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
This command was deprecated. From this version on, all service VLAN
4.2
TLS have forward action by default.
Usage Guidelines
VLAN must be created and configured as service/VLAN TLS to use this functionality. The
commit of a configuration with a PDU action (drop or forward) with a non existing VLAN or
with a VLAN not configured properly (without service/VLAN TLS configuration) will result
in an error message and the configuration will not be applied. This command supports
up to 186 actions, however it depends on platform and services configured.
To configure extended protocols to forward:
(config)# layer2-control-protocol
(l2cp)# vlan 100
(l2cp-vlan-100)# extended action forward
To remove configuration:
(config)# layer2-control-protocol
(l2cp)# no vlan 100
When action parameter is configured as forward (transparent), the equipment will not
be in accordance with the “Frame Filtering” section from IEEE 802.1Q standard.
Hardware restrictions
N/A
LOOPBACK DETECTION
loopback-detection
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
destination-address address
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-ethernet.
timer time
Description: Set the time interval to be waited before unblock the interface.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The Loopback Detection can be enabled on Ethernet interfaces to detect loop failures
caused by RX/TX fiber loop or loops in neighbor networks.
# config
(config)# loopback-detection interface gigabit-ethernet-1/1/1
(config-lbd-interface-gigabit-ethernet-1/1/1)# timer 30
(config-lbd-interface-gigabit-ethernet-1/1/1)# commit
Commit complete.
(config-lbd-interface-gigabit-ethernet-1/1/1)# end
#
(config-lbd-interface-ten-gigabit-ethernet-1/1/1)# commit
Commit complete.
(config-lbd-interface-ten-gigabit-ethernet-1/1/1)# end
#
Link Aggregation Group (LAG) or LAG interfaces themselves. In this case LACP can be used
to prevent loops.
Hardware restrictions
N/A
Description
Display information about Loopback Detection status and configuration. This show only
present ports that are configured for Loopback Detection.
Supported Platforms
Syntax
Parameters
port
Value: N/A
all
Description: Shows the Loopback Detection status for all enabled interfaces.
Value: N/A
loopback
Description: Shows only the Loopback Detection status for the desired port.
Value: N/A
timeout
Description: Shows only the time that the port still needs to wait in non-loop
status to unblock.
Value: N/A
unblock-time
Description: Shows only the configured time to unblock a port after the loop
state clearance.
Value: N/A
Output Terms
Output Description
The configured time to unblock a port after the loop state clearance.
UNBLOCK TIME
The time that the port still needs to wait in non-loop status to un-
TIMEOUT
block.
The status of loopback detection for the port. Can be YES for looped,
LOOPBACK
or NO for non-loop.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the following ports configured for Loopback detection.
# show running-config loopback-detection
loopback-detection
destination-address alternative
interface ten-gigabit-ethernet-1/1/1
timer 10
!
!
#
None
Hardware restrictions
None
link-flap
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-ethernet.
Description: Set the time interval to monitor the transitions of interface link
state after the first one.
Description: Set the time interval without new transitions to wait before
restoring the interface to the previous state.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The Link Flap Detection can be enabled on Ethernet interfaces to avoid link status prop-
agation on unstable links.
# config
(config)# link-flap interface gigabit-ethernet-1/1/1
N/A
Hardware restrictions
N/A
show link-flap
Description
Displays information about Link Flap Detection status and configuration. This command
only shows interfaces that are configured for Link Flap Detection.
Supported Platforms
Syntax
Parameters
interface
Description: The interface whose Link Flap Detection status should be shown.
Value: N/A
all
Description: Shows the Link Flap Detection status for all enabled interfaces.
Value: N/A
config-interval
Description: Shows the configured detection time interval for the specified
interface.
Value: N/A
config-restore-timeout
Description: Shows the configured restore time interval for the specified in-
terface.
Value: N/A
config-transitions
Value: N/A
detected-transitions
Description: Shows the number of transitions detected for the specified in-
terface.
Value: N/A
detection-timeout
Description: Show the remaining time before resetting the transitions counter
if the specified interface does not enter link flap state.
Value: N/A
link-flap
Description: Shows the Link Flap Detection state for the specified interface.
Value: N/A
restore-timeout
Value: N/A
Output Terms
Output Description
Configured
The configured detection time interval.
Interval
Configured restore
The configured restore timeout.
timeout
Detected
The number of transitions detected.
Transitions
Restore Timeout Remaining time without transitions before unblocking the interface.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the following interface configured for Link Flap Detection.
# show running-config link-flap
link-flap
interface ten-gigabit-ethernet-1/1/1
detection transitions 5
detection interval 25
detection restore-timeout 65
!
!
#
None
Hardware restrictions
None
HOLD TIME
hold-time
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-ethernet.
down time
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The hold-time configuration can be enabled on Ethernet interfaces to delay the link down
processing.
# config
(config)# hold-time interface gigabit-ethernet-1/1/1
(config-interface-gigabit-ethernet-1/1/1)# down 500
(config-interface-gigabit-ethernet-1/1/1)# commit
Commit complete.
(config-interface-gigabit-ethernet-1/1/1)# end
#
N/A
Hardware restrictions
N/A
BASIC
This topic describes the commands related to management of basic routing such as
commands to configure the ARP behavior or Static Routes.
clear ip host-table
Description
Supported Platforms
Syntax
Parameters
ip-address a.b.c.d
Description: Clear host with specified IP address from system ARP cache.
Value: a.b.c.d.
intf l3-if
Description: Clear all hosts with specified L3 interface from system ARP cache.
port port-if
vrf vrf-name
Description: Clear all hosts with specified VRF name from system ARP cache.
When no VRF is specified, the clear will be performed on the
global VRF.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Clearing the ARP cache table of the system forces the deletion of all dynamically learned
entries, except those that are next-hop. Next-hop entries will be probed and refreshed.
After executing this command it is possible to ensure the correct mapping between
learned IP addresses with their corresponding MAC addresses.
Hardware restrictions
N/A
ip arp aging-time
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
value
Description: Specifies the time in seconds that an ARP entry stays in cache.
Value: 200-1000000.
Default
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The aging-time ensures that the ARP cache does not retain learned entries that are no
longer used.
To configure ARP aging-time the following command can be used:
Example:
For longer aging-time periods, the ARP cache can retain entries that are no longer used.
And as you reduce the ARP timeout, your network resolution traffic can increase. The
general recommended value for aging-time is the configured default value, which is 1
hour (3600 seconds).
Hardware restrictions
N/A
prefix-list
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
prefix-list name
Value: N/A
seq seq-number
Value: 1-4294967295.
action
Description: The action permit allows a matched prefix. The action deny
denies a matched prefix.
address prefix
le prefix-len
Value: 1-128.
ge prefix-len
Value: 1-128.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a prefix list that only permits the network address
50.50.50.0/24.
(config)# prefix-list TEST
(config-prefix-list-TEST)# seq 10
(config-seq-10)# address 50.50.50.0/24
(config-seq-10)# commit
Commit complete.
This example shows how to configure a prefix list which allows both prefixes 60.60.60.0/24
and 60.60.60.0/25.
(config)# prefix-list TEST_RANGE
(config-prefix-list-TEST_RANGE)# seq 20
(config-seq-20)# address 60.60.60.0/24 ge 24 le 25
(config-seq-20)# commit
Commit complete.
This example shows how to configure a prefix list that denies the network address
60.60.60.0/24 but allows the others.
(config)# prefix-list TEST_DENY
(config-prefix-list-TEST_DENY)# seq 20
(config-seq-20)# action deny
(config-seq-20)# address 60.60.60.0/24
(config-seq-20)# exit
(config-prefix-list-TEST_DENY)# seq 30
(config-seq-30)# address 0.0.0.0/0 le 32
(config-seq-30)# commit
Commit complete.
This example shows how to configure a prefix list that denies the network address
2001::/64 but allows the others.
(config)# prefix-list TEST_DENY
(config-prefix-list-TEST_DENY)# seq 20
(config-seq-20)# action deny
(config-seq-20)# address 2001::/64
(config-seq-20)# exit
(config-prefix-list-TEST_DENY)# seq 30
(config-seq-30)# address ::/0 le 128
(config-seq-30)# commit
Commit complete.
When the prefix list is associated with a route map the permit or deny action configura-
tion of the prefix list entry is ignored.
In case of prefix list directly associated with a BGP neighbor and no permit action matches
are found, all routes will be denied. Therefore, it is necessary to add an additional
sequence with a clause to permit the other routes by setting a matching all address
(0.0.0.0/0 le 32).
Notice that a route policy associated with a neighbor have precedence over a prefix list
directly associated with it.
If there is no route refresh capability support any update on the prefix list configuration
that is associated with a BGP neighbor will cause its BGP session to be restarted.
Updates on prefix-lists associated with a neighbor or with a route map will trigger either
route-refresh or update messages. Route-refresh messages request to the neighbor the
sending of all its prefixes. Differently from a route-refresh message the sending of up-
date messages is an optimization because only the prefixes not included on the previous
BGP update will be advertised.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf-name
Description: Specifies the name of the VRF this IPv4 route will be associated
with.
Value: N/A
a.b.c.d/x
next-hop a.b.c.d
Description: Specifies the IPv4 address of the next hop for this static route.
administrative-distance distance
Value: 1-255.
Default Value: 1.
administrative-status status
interface interface-name
black-hole
Description: Specifies that all traffic to IPv4 network address must be dis-
carded.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
2.4 This command was changed to support IPv6, VRF and output interface.
Usage Guidelines
Currently are supported up to 1000 IPv4 static routes. If IPv6 static routes are configured,
the following constraint must be considered:
Example:
Example:
This example shows how to configure an IPv4 static route in VRF green.
(config)# router static vrf green address-family ipv4
(config-static-vrf-ipv4)# 203.0.113.0/24 next-hop 198.51.100.254
(config-static-vrf-ipv4-203.0.113.0/24-198.51.100.254)# commit
Commit complete.
Example:
This example shows how to configure an IPv4 static route with administrative distance.
(config)# router static address-family ipv4
(config-static-ipv4)# 203.0.113.0/24 next-hop 198.51.100.254
(config-static-ipv4-203.0.113.0/24-198.51.100.254)# administrative-distance 2
(config-static-ipv4-203.0.113.0/24-198.51.100.254)# commit
Commit complete.
Example:
This example shows how to configure an IPv4 static route with black-hole.
(config)# router static address-family ipv4
(config-static-ipv4)# 203.0.113.0/24 black-hole
(config-static-ipv4-203.0.113.0/24-black-hole)# commit
Commit complete.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
x:x:x:x::x/y
next-hop x:x:x:x::x
Description: Specifies the IPv6 address of the next hop for this static route.
administrative-distance distance
Value: 1-255.
Default Value: 1.
administrative-status status
interface interface-name
black-hole
Description: Specifies that all traffic to IPv6 network address must be dis-
carded.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
Currently are supported up to 500 IPv6 static routes. If IPv4 static routes are configured,
the following constraint must be considered:
Example:
Example:
This example shows how to configure an IPv6 static route with administrative distance.
(config)# router static address-family ipv6
(config-static-ipv6)# 2001:db8::/64 next-hop 2001:db8:1::1
(config-static-ipv6-2001:db8::/64-2001:db8:1::1)# administrative-distance 2
(config-static-ipv6-2001:db8::/64-2001:db8:1::1)# commit
Commit complete.
Example:
This example shows how to configure an IPv6 static route with black-hole.
(config)# router static address-family ipv6
(config-static-ipv6)# 2001:db8::/64 black-hole
(config-static-ipv6-2001:db8::/64-black-hole)# commit
Commit complete.
N/A
Hardware restrictions
N/A
show ip fib
Description
Supported Platforms
Syntax
show ip fib [ vrf { vrf-name | all } ] { brief } [ network ip-address | state route-state
]
Parameters
vrf vrf-name
brief
Value: N/A
network ip-address
Description: IPv4 address and mask network used to filter the output.
Value: a.b.c.d/x
state route-state
Output Terms
Output Description
VRF-name Display the VRF name associated with the IPv4 route.
Display the destination IPv4 address and mask of the remote net-
Network
work.
Next-hop Display the IPv4 address of the next router to the remote network.
Display the route state. The active state represents installed routes,
the inactive state represents unsupported routes that will not be in-
State
stalled and the pending state represents valid routes currently not
installed due to a hardware limitation.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show IPv4 FIB information, the following command can be used:
Example:
Filter by Network:
Example:
Filter by State:
Example:
Filter by VRF:
Example:
Depending on the number of routes installed, the execution of the command may take a
while.
Hardware restrictions
N/A
show ip host-table
Description
Supported Platforms
Syntax
Parameters
vrf vrf-name
brief
Value: N/A
address ip-address
Value: a.b.c.d
mac mac-address
type host-type
Output Terms
Output Description
Physical interface Display the physical interface on which the respective host is asso-
ciated.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of hosts the following command can be used:
Example:
To show the the list of hosts of all VRFs the following command can be used:
Example:
To show the the list of hosts of an specific VRF the following command can be used:
Example:
Filter by IP:
Example:
Filter by MAC:
Example:
Filter by Type:
Example:
N/A
Hardware restrictions
N/A
show ip rib
Description
Supported Platforms
Syntax
show ip rib [bgp | connected | destination ip-address | ospf | static | vrf name ]
Parameters
bgp
Value: N/A
connected
Value: N/A
destination ip-address
Value: a.b.c.d/x
ospf
Value: N/A
static
Value: N/A
vrf name
Output Terms
Output Description
Indicates the type and the protocol that derived the route. The leg-
Type
end codes are displayed at the beginning of each report.
Next-hop Indicates the address of the next router to the remote network.
Age Indicates the time period since this route was last updated.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
show ip route
Description
Supported Platforms
Syntax
Parameters
bgp
Value: N/A
connected
Value: N/A
destination ip-address
Value: a.b.c.d/x
ospf
Value: N/A
static
Value: N/A
summary
Value: N/A
vrf name
Output Terms
Output Description
Indicates the type and the protocol that derived the route. The leg-
Type
end codes are displayed at the beginning of each report.
Next-hop Indicates the address of the next router to the remote network.
Age Indicates the time period since this route was last updated.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
Right after switch initialization the route table will be empty, because it takes a while to
be populated.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show ipv6 fib [ vrf { vrf-name | all } ] { brief } [ network ipv6-address | state
route-state ]
Parameters
vrf vrf-name
brief
Value: N/A
network ipv6-address
Description: IPv6 address and mask network used to filter the output.
Value: x:x:x:x::x/y
state route-state
Output Terms
Output Description
VRF-name Display the VRF name associated with the IPv6 route.
Display the destination IPv6 address and mask of the remote net-
Network
work.
Next-hop Display the IPv6 address of the next router to the remote network.
Display the route state. The active state represents installed routes,
the inactive state represents unsupported routes that will not be in-
State
stalled and the pending state represents valid routes currently not
installed due to a hardware limitation.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show IPv6 FIB information, the following command can be used:
Example:
Filter by Network:
Example:
Filter by State:
Example:
Filter by VRF:
Example:
Depending on the number of routes installed, the execution of the command may take a
while.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show ipv6 host-table [ vrf { vrf-name | all } ] { brief } [ address ipv6-address | mac
{ mac-address | incomplete } | type host-type ]
Parameters
vrf vrf-name
brief
Value: N/A
address ipv6-address
Value: x:x:x:x::x/y
mac mac-address
type host-type
Output Terms
Output Description
MAC Display the MAC addresses associated with host IPv6 addresses.
Physical interface Display the physical interface on which the respective host is asso-
ciated.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of hosts the following command can be used:
Example:
To show the the list of hosts of all VRFs the following command can be used:
Example:
To show the the list of hosts of an specific VRF the following command can be used:
Example:
It is possible to filter the results by IPv6 address, MAC address, and Type.
Filter by MAC:
Example:
Filter by Type:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show ipv6 rib [bgp | connected | destination ip-address | ospf | static | vrf vrf-name
]
Parameters
bgp
Value: N/A
connected
Value: N/A
destination ip-address
Value: x:x:x:x::x/x
ospf
Value: N/A
static
Value: N/A
vrf vrf-name
Output Terms
Output Description
Indicates the type and the protocol that derived the route. The leg-
Type
end codes are displayed at the beginning of each report.
Indicates the destination IPv6 address and mask of the remote net-
Dest Address/Mask
work.
Next-hop Indicates the address of the next router to the remote network.
Age Indicates the time period since this route was last updated.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
These examples show how to use the show ipv6 rib command.
# show ipv6 rib
Type Codes: C - connected, S - static, L - local, O - OSPF, B - BGP
E1 - OSPF external type 1, E2 - OSPF external type 2, IA - OSPF inter area,
Output Interface Codes: DC - directly connected
Type Dest Address/Mask Next-hop Age AD Metric Output Interface
------ --------------------- ----------------- -------- --- ------ ----------------
C 2001:db8:100::/64 2001:db8:100::1 00:11:45 0 0 l3-vlan 100
L 2001:db8:100::1/128 :: 00:11:45 0 0 DC
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show ipv6 route [bgp | connected | destination ip-address | ospf | static | sum-
mary | vrf vrf-name ]
Parameters
bgp
Value: N/A
connected
Value: N/A
destination ip-address
Value: x:x:x:x::x/x
ospf
Value: N/A
static
Value: N/A
summary
Value: N/A
vrf vrf-name
Output Terms
Output Description
Indicates the type and the protocol that derived the route. The leg-
Type
end codes are displayed at the beginning of each report.
Indicates the destination IPv6 address and mask of the remote net-
Dest Address/Mask
work.
Next-hop Indicates the address of the next router to the remote network.
Age Indicates the time period since this route was last updated.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
These examples show how to use the show ipv6 route command.
# show ipv6 route
Type Codes: C - connected, S - static, L - local, O - OSPF, B - BGP
E1 - OSPF external type 1, E2 - OSPF external type 2, IA - OSPF inter area,
Output Interface Codes: DC - directly connected
Type Dest Address/Mask Next-hop Age AD Metric Output Interface
------ --------------------- ----------------- -------- --- ------ ----------------
C 2001:db8:100::/64 2001:db8:100::1 00:11:29 0 0 l3-vlan 100
L 2001:db8:100::1/128 :: 00:11:29 0 0 DC
S 2001:db8:2010::/64 :: 00:00:03 1 0 black-hole
C 2001:db8:2020::/64 2001:db8:2020::1 00:00:03 0 0 mgmt-1/1/1
L 2001:db8:2020::1/128 :: 00:00:03 0 0 DC
S 2001:db8:2030::/64 2001:db8:2020::2 00:00:04 1 0 mgmt-1/1/1
# show ipv6 route summary
IPv6 routing table name is Default-IPv6-Routing-Table
Family Total routes
ipv6 6
# show ipv6 route destination 2001:db8:2010::/64
Routing entry for 2001:db8:2010:: (mask 64)
Known via ’static’, distance 1, metric 0
Redistributing via static
Last update from :: 00:00:03 ago
Routing Descriptor Blocks:
:: directly connected, via black-hole 00:00:03 ago
Route metric is 0
# show ipv6 route vrf green
Type Codes: C - connected, S - static, L - local, O - OSPF, B - BGP
E1 - OSPF external type 1, E2 - OSPF external type 2, IA - OSPF inter area,
Output Interface Codes: DC - directly connected
Type Dest Address/Mask Next-hop Age AD Metric Output Interface
------ ------------------ --------- -------- --- ------ ----------------
C fd01::/16 fd01::1 00:03:03 0 0 l3-vlan 101
L fd01::1/128 :: 00:03:04 0 0 DC
#
Right after switch initialization the route table will be empty, because it takes a while to
be populated.
Hardware restrictions
N/A
BFD
This topic describes the commands related to management of BFD such as commands
to configure the BFD parameters or to inspect the sessions status.
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4250, DM4610,
DM4615.
Syntax
Parameters
brief
Value: N/A
Output Terms
Output Description
Proto Indicates the client protocol which is protected by this BFD session.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
BGP
This topic describes the commands related to management of BGP topologies such as
commands to configure the BGP parameters or to inspect the protocol status.
Description
Supported Platforms
Syntax
Parameters
vrf name
ip IP address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat (IPv6 is not supported when the VRF filter is used).
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to restart a BGP neighbor from a BGP router specifying a neigh-
bor ip address.
# clear bgp neighbor ip 50.50.50.1
This example shows how to restart all BGP neighbors from a BGP router.
# clear bgp neighbor
If no VRF parameter is included, the action will be executed only for the BGP on the
global VRF. The VRF parameter accepts a VRF name, the global VRF or all VRFs.
This example shows how to restart all BGP neighbors on a specific VRF.
# clear bgp neighbor vrf GREEN
To restart all BGP neighbors for all VRFs, the following command can be used.
# clear bgp neighbor vrf all
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
vrf name
ip IP address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat (IPv6 is not supported when the VRF filter is used).
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to perform soft reset in a specific BGP neighbor.
# clear bgp soft ip 50.50.50.1
This example shows how to perform a soft reset in all BGP sessions.
# clear bgp soft
If no VRF parameter is included, the action will be executed only for the BGP on the
global VRF. The VRF parameter accepts a VRF name, the global VRF or all VRFs.
This example shows how to soft restart all BGP sessions on a specific VRF.
# clear bgp soft vrf GREEN
To soft restart all BGP sessions for all VRFs, the following command can be used.
# clear bgp soft vrf all
For neighbors that do not support the route refresh capability a Cease Notification mes-
sage will be sent instead causing BGP session to restart.
Hardware restrictions
N/A
router bgp
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
address-family vpnv4
unicast
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the router BGP VPNv4 unicast address family sup-
port.
(config)# router bgp 65000
(config-bgp-65000)# address-family vpnv4 unicast
(config-address-family-vpnv4/unicast)# commit
Commit complete.
Changes on the address family will impact the router BGP capabilities. It also causes a
flap in the established BGP sessions.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
unicast
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the router BGP IPv4 unicast address family support.
(config)# router bgp 65000
(config-bgp-65000)# address-family ipv4 unicast
(config-address-family-ipv4/unicast)# commit
Commit complete.
This example shows how to enable the router BGP IPv6 unicast address family support.
(config)# router bgp 65000
(config-bgp-65000)# address-family ipv6 unicast
(config-address-family-ipv6/unicast)# commit
Commit complete.
Changes on the address family will impact the router BGP capabilities. It also causes a
flap in the established BGP sessions.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
as-size length
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the Router BGP Autonomous system(AS) size.
(config)# router bgp 65000 as-size two-octets
(config-bgp-65000)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
bgp cluster-id id
Description: Specifies the BGP Cluster-ID for this Router in IPv4 address for-
mat.
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
Value: 0-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP default local preference.
(config)# router bgp 65000 bgp default-local-preference 150
(config-bgp-65000)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Enables the BGP neighbor VPNv4 address family support and enters in mode configura-
tion.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Value: a.b.c.d
Description: Enables the BGP neighbor address family mode support and
enters in mode configuration.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the BGP neighbor VPNv4 unicast address family sup-
port.
(config)# router bgp 65000
(config-bgp-65000)# neighbor 1.1.10.2
(config-neighbor-1.1.10.2)# address-family vpnv4 unicast
(config-address-family-ipv4/unicast)# commit
Commit complete.
Changes on the address family will impact the BGP neighbor capabilities. It also causes
a flap in the established BGP neighbor session.
Hardware restrictions
N/A
Description
Enables the BGP neighbor address family support and enters in mode configuration.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
Description: Enables the BGP neighbor address family mode support and
enters in mode configuration.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the BGP neighbor IPv4 unicast address family support.
(config)# router bgp 65000
(config-bgp-65000)# neighbor 1.1.10.2
(config-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-address-family-ipv4/unicast)# commit
Commit complete.
This example shows how to enable the BGP neighbor IPv6 unicast address family support.
(config)# router bgp 65000
Changes on the address family will impact the BGP neighbor capabilities. It also causes
a flap in the established BGP neighbor session.
Hardware restrictions
N/A
Description
Associates a prefix list with a BGP neighbor for export or import based on the address
family.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
export-prefix-list prfx-name
Description: Specifies the prefix list for export to be directly associated with
the BGP neighbor. Use the no form to remove this parameter.
import-prefix-list prfx-name
Description: Specifies the prefix list for import to be directly associated with
the BGP neighbor. Use the no form to remove this parameter.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Changes on the behavior when a prefix list and a route policy are associ-
3.0
ated with a neighbor.
Usage Guidelines
Example:
This example shows how to associate the prefix list for export named PRX_LIST_EXPORT
with a BGP neighbor. This prefix list must be previously created.
(config)# router bgp 65000
(config-bgp-65000)# neighbor 1.1.10.2
(config-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-address-family-ipv4/unicast)# export-prefix-list PRX_LIST_EXPORT
(config-address-family-ipv4/unicast)# commit
This example shows how to associate the prefix list for import named PRX_LIST_IMPORT
with a BGP neighbor. This prefix list must be previously created.
(config)# router bgp 65000
(config-bgp-65000)# neighbor 1.1.10.2
(config-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-address-family-ipv4/unicast)# import-prefix-list PRX_LIST_IMPORT
(config-address-family-ipv4/unicast)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP neighbor administrative status in the
neighbor command tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# administrative-status down
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
description text
Value: string.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a BGP neighbor description in the neighbor com-
mand tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# description "Remote bgp peer"
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configure the maximum hop count to reach a BGP neighbor not directly connected.
Supported Platforms
Syntax
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
ebgp-multihop hop-count
Value: 1-255.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP neighbor ebgp-multihop in the neighbor
command tree.
(config)# router bgp 65000 neighbor 50.50.50.1 remote-as 66000
(config-neighbor-50.50.50.1)# ebgp-multihop 2
(config-neighbor-50.50.50.1)# commit
For security reasons, please note that this parameter is automatically configured to 1
for eBGP and 255 for iBGP sessions, unless it was manually configured. But if neighbor
mode changes (to iBGP or eBGP) and ebgp-multihop has not been changed, it will be
automatically updated according to the new mode.
Hardware restrictions
N/A
Description
Configures the BGP neighbor to use its own address as next hop in the advertised routes.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
next-hop-self
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP neighbor next hop self in the neighbor
command tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# next-hop-self
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
password pwd
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. The same password must be applied for
both BGP peers.
Example:
This example shows how to configure the BGP neighbor password in the neighbor com-
mand tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# password pwdTest
(config-neighbor-50.50.50.1)# commit
This example shows the configuration of a neighbor password using an already encrypted
password.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# password "hls:2922743918:337ZpL=Z"
(config-neighbor-50.50.50.1)# commit
This example shows the configuration of a neighbor password using special characters
(i.e: " " , “?” , “!” , “;”). Please note that it is necessary to use double quotation marks
in this case.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# password "pwd?test:2"
(config-neighbor-50.50.50.1)# commit
Password must be enclosed in double quotation marks if special characters were used
(i.e: " " , “?” , “!” , “;”). Note that in an established BGP session if password is configured
or changed the session will be restarted.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
remote-as as-number
Value: 1-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a neighbor remote Autonomous System(AS) num-
ber after entering in the neighbor command tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# remote-as 65001
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
route-policy rp-name
Description: Specifies the route policy to be associated with the BGP neigh-
bor.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to associate the route policy named RP_INTERNET with a BGP
neighbor. This route policy must be previously created.
(config)# router bgp 101
(config-bgp-101)# neighbor 1.1.10.2
(config-neighbor-1.1.10.2)# route-policy RP_INTERNET
(config-neighbor-1.1.10.2)# commit
If there is no route refresh capability support any update on the route policy configuration
that is associated with a BGP neighbor will cause its BGP session to be restarted.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
route-reflector option
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure route-reflector after entering in the neighbor com-
mand tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# route-reflector client
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configure the hold time interval for the session with the neighbor.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
Description: Specifies the hold time interval to use when negotiating a con-
nection with the neighbor.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. The hold time interval must be greater
than or equal to the keepalive interval. Indeed, it is recommended that the hold time
is 3 times the interval at which keepalive messages are sent. A zeroed value means an
infinite time. If the hold time interval is set to zero, the keepalive interval must be set to
zero as well.
Example:
This example shows how to configure the BGP neighbor hold time interval in the neighbor
command tree.
(config)# router bgp 65000 neighbor 50.50.50.1 remote-as 66000
(config-neighbor-50.50.50.1)# timers hold-time 90
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configure the keepalive interval for the session with the neighbor.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
Value: 0-21845.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. The keepalive interval must be lower
than or equal to the hold-time interval. Indeed, it is recommended that the hold time is
3 times the interval at which keepalive messages are sent. A zeroed value for keepalive
timer disables the sending of keepalive messages. In this case, the hold-time interval
must be set to zero as well.
The router automatically adjusts the effective keepalive timer based on the configured
values, according to the following formula:
As example, if the configured and negotiated hold-time are both 150 and keepalive is
configured to 60:
keepalive = 150 / 2
keepalive = 75
Example:
This example shows how to configure the BGP neighbor keepalive interval in the neighbor
command tree.
(config)# router bgp 65000 neighbor 50.50.50.1 remote-as 66000
(config-neighbor-50.50.50.1)# timers keepalive 30
(config-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the BGP neighbor source address to be used during the session establish-
ment.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Description: Specifies the BGP neighbor address in IPv4 or IPv6 address for-
mat.
update-source-address address
Description: Specifies the BGP neighbor source address in IPv4 or IPv6 ad-
dress format.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP neighbor IPv4 source address in the neigh-
bor command tree.
(config)# router bgp 65000 neighbor 50.50.50.1
(config-neighbor-50.50.50.1)# update-source-address 100.100.100.1
(config-neighbor-50.50.50.1)# commit
Commit complete.
This example shows how to configure the BGP neighbor IPv6 source address in the neigh-
bor command tree.
(config)# router bgp 65000 neighbor 2222::2
(config-neighbor-2222::2)# update-source-address 2002::1
(config-neighbor-2222::2)# commit
Commit complete.
N/A
Hardware restrictions
N/A
Description
Inserts a network present locally in the routing table into BGP domain and advertises it
to the neighbor, when that network exactly matches a given prefix.
Supported Platforms
Syntax
Parameters
as-number
Value: 1-4294967295.
Description: Specifies that the network prefix entry is from IPv4 address fam-
ily.
Value: N/A
address a.b.c.d/x
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to create a list of 2 network prefixes to be redistributed into
BGP domain.
(config)# router bgp 65000
(config-bgp-65000)# network address-family ipv4 address 40.40.40.240/28
(config-network/ipv4)# exit
(config-bgp-65000)# network address-family ipv4 address 80.80.128.0/17
(config-network/ipv4)# commit
The network inserted into BGP domain will have its path attribute origin set as IGP. The
network will be advertised to the neighbors only if it is already present in the routing
table. That means, there must be a route learned using local or connected networks,
static routes, or a dynamic IGP such as OSPF.
Hardware restrictions
N/A
Description
Inserts a network present locally in the routing table into BGP domain and advertises it
to the neighbor, when that network exactly matches a given prefix.
Supported Platforms
Syntax
Parameters
as-number
Value: 1-4294967295.
Description: Specifies that the network prefix entry is from IPv6 address fam-
ily.
Value: N/A
address x:x:x:x::x/y
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to create a list of 2 network prefixes to be redistributed into
BGP domain.
(config)# router bgp 65000
(config-bgp-65000)# network address-family ipv6 address 1111::1/128
(config-network/ipv6)# exit
(config-bgp-65000)# network address-family ipv6 address 2222::2/128
(config-network/ipv6)# commit
The network inserted into BGP domain will have its path attribute origin set as IGP. The
network will be advertised to the neighbors only if it is already present in the routing
table. That means, there must be a route learned using local or connected networks,
static routes, or a dynamic IGP such as OSPF.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router bgp as-number prefix-list name seq seq-number [ permit | deny ] address-
family ipv4 unicast [ address prefix ] [ le prefix-len ] [ ge prefix-len]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
prefix-list name
Value: N/A
seq seq-number
Value: 1-4294967295.
permit
Value: N/A
deny
Value: N/A
Value: N/A
address prefix
Value: a.b.c.d/x.
le prefix-len
Value: 1-32.
ge prefix-len
Value: 1-32.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Changes on the behavior when a prefix list and a route policy are associ-
3.0
ated with a neighbor.
This Command was deprecated. From this version on, the prefix list is
4.6 configured in the config level. For further information please see Prefix
List command.
Usage Guidelines
Example:
This example shows how to configure a prefix list that permits the network address
50.50.50.0/24.
(config)# router bgp 101
(config-bgp-101)# prefix-list TEST
(config-prefix-list-TEST)# seq 10
(config-seq-10)# address-family ipv4 unicast
(config-unicast)# address 50.50.50.0/24
(config-unicast)# commit
Commit complete.
This example shows how to configure a prefix list with a permitted prefix range from
This example shows how to configure a prefix list that denies the network address
60.60.60.0/24 but allows the others.
(config)# router bgp 101
(config-bgp-101)# prefix-list TEST_DENY
(config-prefix-list-TEST_DENY)# seq 20
(config-seq-20)# deny
(config-seq-20)# address-family ipv4 unicast
(config-unicast)# address 60.60.60.0/24
(config-unicast)# exit
(config-seq-20)# exit
(config-prefix-list-TEST_DENY)# seq 30
(config-seq-30)# address-family ipv4 unicast
(config-unicast)# address 0.0.0.0/0 ge 1 le 32
(config-unicast)# commit
Commit complete.
When the prefix list is associated with a route map the permit or deny configuration of
the prefix list entry is ignored.
In case of prefix list directly associated with a BGP neighbor and no permit matches are
found, all routes will be denied. Therefore, it is necessary to add an additional sequence
with a clause to permit the other routes by setting a matching all address (0.0.0.0/0 ge
1 le 32).
Notice that when there is a route policy importing a route map associated with a neighbor
the prefix list for import directly associated with it will be ignored. The same precedence
applies to the case when both are set for export.
If there is no route refresh capability support any update on the prefix list configuration
that is associated with a BGP neighbor will cause its BGP session to be restarted.
Updates on prefix-lists associated with a neighbor or with a route map will trigger either
route-refresh or update messages. Route-refresh messages request to the neighbor the
sending of all its prefixes. Differently from a route-refresh message the sending of update
messages is an optimization because only the prefixes not included on the previous BGP
update will be advertised.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
redistribute connected
Description: Redistributes connected routes into the domain of this BGP router.
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this BGP router.
Value: N/A
redistribute ospf
Description: Redistributes ospf routes into the domain of this BGP router.
Value: N/A
address-family ipv4
Value: N/A
address-family ipv6
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a redistribution of all IPv4 static routes.
# router bgp 65000 redistribute static address-family ipv4
(config-redistribute-static/ipv4)# commit
This example shows how to configure a redistribution of all IPv4 connected routes.
# router bgp 65000 redistribute connected address-family ipv4
(config-redistribute-connected/ipv4)# commit
This example shows how to configure a redistribution of all IPv4 ospf routes.
# router bgp 65000 redistribute ospf address-family ipv4
(config-redistribute-ospf/ipv4)# commit
This example shows how to configure a redistribution of all IPv6 static routes.
# router bgp 65000 redistribute static address-family ipv6
(config-redistribute-static/ipv6)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
redistribute connected
Description: Redistributes connected routes into the domain of this BGP router.
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this BGP router.
Value: N/A
redistribute ospf
Description: Redistributes ospf routes into the domain of this BGP router.
Value: N/A
address-family ipv4
Value: N/A
address-family ipv6
Value: N/A
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Redistributes only the routes that match the specified address into the domain of this
BGP router.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
redistribute connected
Description: Redistributes connected routes into the domain of this BGP router.
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this BGP router.
Value: N/A
address-family ipv4
Value: N/A
match-address a.b.c.d/x
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a route redistribution which matches a single IPv4
address prefix.
N/A
Hardware restrictions
N/A
Description
Redistributes only the routes that match the specified address into the domain of this
BGP router.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
redistribute connected
Description: Redistributes connected routes into the domain of this BGP router.
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this BGP router.
Value: N/A
address-family ipv6
Value: N/A
match-address x:x:x:x::x/y
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a route redistribution which matches a single IPv6
address prefix.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
route-map rmap-name
Value: N/A
seq-number
Value: 1-4294967295.
Description: A reference for all route map sequences. This option allows edition
or deletion of all route map sequences simultaneously.
Value: N/A
action
Description: When action permit is used in case of match of any criteria the route
is allowed to be redistributed and the set of actions is performed. When
action deny is used in case of match of any criteria the route is rejected
and no further processing is performed.
match-as-path as-path
Description: Regular expression to match BGP AS paths (write regex using POSIX ex-
tended standard ensuring the use of double quote in order to avoid prob-
lems with special characters)
match-med med
Value: 0-4294967295.
match-origin origin
set-local-preference value
Value: 0-2147483647.
set-med med
Value: 0-4294967295.
Default Value: 0.
set-origin origin
set-prepend-local-as num-times
Description: Prepends the AS number to the AS path the number of times specified
by num-times.
Value: 1-254.
continue seq-number
Description: Continues the route map on a different sequence number. The sequence
number must exist and be higher than the current one. The continue
parameter can only be used with permit sequences of route map.
Value: 1-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The route map must be associated with a route policy in order to be applied to a neighbor.
The route refresh capability in router BGP is required to avoid BGP sessions to be restarted.
Example:
This example shows how to configure a route map with matching for a prefix list and
setting of local preference.
(config)# router bgp 101
(config-bgp-101)# route-map RMAP 10
(config-route-map-RMAP/10)# match-ip nlri prefix-list PRX_LIST
(config-route-map-RMAP/10)# set-local-preference 200
(config-route-map-RMAP/10)# commit
This example shows how to configure all sequences of a route map simultaneously to
perform a deny action.
(config)# router bgp 101
(config-bgp-101)# route-map RMAP 10
(config-route-map-RMAP/10)# exit
(config-bgp-101)# route-map RMAP 20
(config-route-map-RMAP/20)# exit
(config-bgp-101)# route-map RMAP *
(config-route-map-RMAP/*)# action deny
(config-route-map-RMAP/*)# commit
Specific sequence (all three values should appear in this exact order)
(config-route-map-RMAP/10)# match-as-path "333.100.444"
Path does not contain 333 (see impacts and precautions for more details about deny
rules)
(config-route-map-RMAP/10)# match-as-path "(333)"
(config-route-map-RMAP/10)# action deny
(config-route-map-RMAP/10)# exit
(config-bgp-101)# route-map RMAP 20
(config-route-map-RMAP/20)# commit
When a route map is not specified, routes are automatically permitted by default. How-
ever, if a route map is created but no matching clauses are found, all routes will be
denied. In this case it is necessary to add an additional sequence without any clause in
order to permit all other routes.
If there is no route refresh capability support any update on the route map configuration
that is associated with a BGP neighbor will cause its BGP session to be restarted.
Updates on route map associated with a neighbor through a route policy will trigger
either route-refresh or update messages. Route-refresh messages request to the neigh-
bor the sending of all its prefixes. Differently from a route-refresh message the sending
of update messages is an optimization because only the prefixes not included on the
previous BGP update will be advertised.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
route-map rmap-name
Value: N/A
seq-number
Value: 1-4294967295.
Description: A reference for all route map sequences. This option allows edition
or deletion of all route map sequences simultaneously.
Value: N/A
match-community communities
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a match for communities.
(config)# router bgp 100
(config-bgp-100)# route-map RMAP 10
(config-route-map-RMAP/10)# match-community 200:123
(config-route-map-RMAP/10)# route-map RMAP 11
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
route-map rmap-name
Value: N/A
seq-number
Value: 1-4294967295.
Description: A reference for all route map sequences. This option allows edition
or deletion of all route map sequences simultaneously.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a community for prefixes.
(config)# router bgp 100
(config-bgp-100)# route-map RMAP 10
(config-route-map-RMAP/10)# set-community 100:123
(config-route-map-RMAP/10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
route-map rmap-name
Value: N/A
seq-number
Value: 1-4294967295.
Description: A reference for all route map sequences. This option allows edition
or deletion of all route map sequences simultaneously.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a community action for prefixes.
(config)# router bgp 100
(config-bgp-100)# route-map RMAP 10
(config-route-map-RMAP/10)# set-community 100:123
(config-route-map-RMAP/10)# set-community-action remove-all-and-set
(config-route-map-RMAP/10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
route-policy rp-name
Value: String
import-route-map rmap-name
Description: Specifies the route map that will be used for route imports.
Value: String
export-route-map rmap-name
Description: Specifies the route map that will be used for route exports.
Value: String
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
If there is no route refresh capability support any update on the route policy configuration
that is associated with a BGP neighbor will cause its BGP session to be restarted.
Updates on route policy associated with a neighbor will trigger either route-refresh or
update messages. Route-refresh messages request to the neighbor the sending of all its
prefixes. Differently from a route-refresh message the sending of update messages is an
optimization because only the prefixes not included on the previous BGP update will be
advertised.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
as-number
Value: 1-4294967295.
router-id id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to associate a VRF with the router BGP.
(config)# router bgp 65000 vrf example
(config-vrf-example)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
address-family ipv4
unicast
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the router BGP IPv4 unicast address family support.
(config)# router bgp 65000 vrf red
(config-bgp-vrf)# address-family ipv4 unicast
(config-bgp-vrf-address-family-ipv4/unicast)# commit
Commit complete.
Changes on the address family will impact the router BGP capabilities. It also causes a
flap in the established BGP sessions.
Hardware restrictions
N/A
Description
Redistributes routes from the VRF into the domain of this BGP router.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name address-family ipv4 unicast redistribute {connected
| ospf | static}
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
Value: N/A
redistribute connected
Description: Redistributes VRF connected routes into the domain of this BGP
router.
Value: N/A
redistribute ospf
Description: Redistributes VRF OSPF routes into the domain of this BGP router.
Value: N/A
redistribute static
Description: Redistributes VRF static routes into the domain of this BGP router.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a redistribution of all IPv4 connected routes from
VRF example.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute connected
(config-bgp-vrf-address-family-redist-connected)# commit
This example shows how to configure a redistribution of all OSPF routes from VRF ex-
ample.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute ospf
(config-bgp-vrf-address-family-redist-ospf)# commit
This example shows how to configure a redistribution of all IPv4 static routes from VRF
example.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute static
(config-bgp-vrf-address-family-redist-static)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name address-family ipv4 unicast redistribute {connected
| static } administrative-status { up | down }
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
Value: N/A
redistribute connected
Description: Redistributes VRF connected routes into the domain of this BGP
router.
Value: N/A
redistribute static
Description: Redistributes VRF static routes into the domain of this BGP router.
Value: N/A
administrative-status { up | down }
Value: up or down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to deactivate the redistribution of IPv4 connected routes from
VRF example.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute connected
(config-bgp-vrf-address-family-redist-static)# administrative-status down
(config-bgp-vrf-address-family-redist-static)# commit
This example shows how to deactivate the redistribution of IPv4 static routes from VRF
example.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute static
(config-bgp-vrf-address-family-redist-static)# administrative-status down
(config-bgp-vrf-address-family-redist-static)# commit
N/A
Hardware restrictions
N/A
Description
Redistributes only the routes from VRF that match the specified address into the domain
of this BGP router.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name address-family ipv4 unicast redistribute {connected
| static} match-address a.b.c.d/x
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
Value: N/A
redistribute connected
Description: Redistributes VRF connected routes into the domain of this BGP
router.
Value: N/A
redistribute static
Description: Redistributes VRF static routes into the domain of this BGP router.
Value: N/A
match-address a.b.c.d/x
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure redistribution of IPv4 connected routes from VRF
example which matches a single IPv4 address prefix.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute connected
(config-bgp-vrf-address-family-redist-connected)# match-address 10.1.0.0/24
(config-bgp-vrf-address-family-redist-connected)# commit
This example shows how to configure redistribution of IPv4 static routes from VRF ex-
ample which matches a single IPv4 address prefix.
# router bgp 65000 vrf example address-family ipv4 unicast redistribute static
(config-bgp-vrf-address-family-redist-static)# match-address 10.1.0.0/24
(config-bgp-vrf-address-family-redist-static)# commit
N/A
Hardware restrictions
N/A
Description
Inserts a network present locally in the routing table into BGP VRF domain and advertises
it to the neighbor, when that network exactly matches a given prefix.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name address-family ipv4 unicast network a.b.c.d/x
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
Value: N/A
network a.b.c.d/x
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to create a list of 2 network prefixes to be redistributed into
BGP domain in a VRF.
(config)# router bgp 65000
(config-bgp-65000)# vrf red
(config-bgp-vrf-red)# address-family ipv4 unicast
(config-bgp-vrf-address-family-ipv4/unicast)# network 40.40.40.240/28
(config-network-40.40.40.240/28)# top
(config)# router bgp 65000 vrf red address-family ipv4 unicast network 80.80.128.0/17
(config-network-80.80.128.0/17)# commit
The network inserted into BGP domain will have its path attribute origin set as IGP. The
network will be advertised to the neighbors only if it is already present in the VRF routing
table. That means, there must be a route learned using local or connected networks or
static routes.
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a neighbor for a BGP VRF router.
(config)# router bgp 65000
(config-bgp-65000)# vrf red
(config-bgp-vrf-red)# neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Enables the BGP VRF neighbor address family support and enters in mode configuration.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name neighbor address address-family ipv4 unicast
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Description: Specifies the BGP VRF neighbor address in IPv4 address format.
Value: a.b.c.d.
Description: Enables the BGP VRF neighbor address family mode support
and enters in mode configuration.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the IPv4 unicast address family support for a BGP
VRF neighbor.
(config)# router bgp 65000 vrf red
(config-bgp-vrf-red)# neighbor 1.1.10.2
(config-bgp-vrf-neighbor-1.1.10.2)# remote-as 65000
(config-bgp-vrf-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# commit
Changes on the address family will impact the BGP neighbor capabilities. It also causes
a flap in the established BGP neighbor session.
Hardware restrictions
N/A
Description
When receiving routes from the respective neighbor, this option allows the installation
of routes with local Autonomous System(AS) number present in AS path.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name neighbor address address-family ipv4 unicast
allow-as-in number-of-occurrences
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Description: Specifies the BGP VRF neighbor address in IPv4 address format.
Value: a.b.c.d.
Description: Enables the BGP VRF neighbor address family mode support
and enters in mode configuration.
allow-as-in number-of-occurrences
Value: 0-10.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure allow-as-in to accept routes with up to five lo-
cal AS occurrences in AS path.
(config)# router bgp 65000 vrf red
(config-bgp-vrf-red)# neighbor 1.1.10.2
(config-bgp-vrf-neighbor-1.1.10.2)# remote-as 65001
(config-bgp-vrf-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# allow-as-in 5
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# commit
N/A
Hardware restrictions
N/A
Description
When advertising routes to the respective neighbor, this option replaces the remote
Autonomous System(AS) number occurrences in AS path by the local AS number.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
router bgp as-number vrf vrf-name neighbor address address-family ipv4 unicast
as-override
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Description: Specifies the BGP VRF neighbor address in IPv4 address format.
Value: a.b.c.d.
Description: Enables the BGP VRF neighbor address family mode support
and enters in mode configuration.
as-override
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure as-override for a BGP VRF neighbor.
(config)# router bgp 65000 vrf red
(config-bgp-vrf-red)# neighbor 1.1.10.2
(config-bgp-vrf-neighbor-1.1.10.2)# remote-as 65001
(config-bgp-vrf-neighbor-1.1.10.2)# address-family ipv4 unicast
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# as-override
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# commit
N/A
Hardware restrictions
N/A
Description
Associates a prefix list with a BGP neighbor in a VRF for export or import based on the
address family.
Supported Platforms
Syntax
router bgp as-number vrf vrf-name neighbor address address-family ipv4 unicast
[export-prefix-list prfx-name] [import-prefix-list prfx-name]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
neighbor address
Value: a.b.c.d.
vrf vrf-name
export-prefix-list prfx-name
Description: Specifies the prefix list for export to be directly associated with
the BGP neighbor. Use the no form to remove this parameter.
import-prefix-list prfx-name
Description: Specifies the prefix list for import to be directly associated with
the BGP neighbor. Use the no form to remove this parameter.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to associate the prefix list for export named PRXE with a BGP
neighbor. This prefix list must be previously created.
(config)# router bgp 65000
(config-bgp-65000)# vrf red
(config-bgp-vrf-red)# neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# address-family ipv4 unicast
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# export-prefix-list PRXE
This example shows how to associate the prefix list for import named PRXI with a BGP
neighbor. This prefix list must be previously created.
(config)# router bgp 65000
(config-bgp-65000)# vrf red
(config-bgp-vrf-red)# neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# address-family ipv4 unicast
(config-bgp-vrf-neighbor-address-family-ipv4/unicast)# import-prefix-list PRXI
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Value: a.b.c.d.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the administrative status for a BGP VRF neigh-
bor.
(config)# router bgp 65000 vrf red neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# remote-as 65001
(config-bgp-vrf-neighbor-50.50.50.1)# administrative-status down
(config-bgp-vrf-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the BGP VRF neighbor to use its own address as next hop in the advertised
routes.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Value: a.b.c.d.
next-hop-self
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP VRF neighbor to use its own address
as next hop in the advertised routes.
(config)# router bgp 65000 vrf red neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# next-hop-self
(config-bgp-vrf-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the BGP VRF neighbor password to be used in the Message Digest 5 (MD5)
algorithm for TCP authentication.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Value: a.b.c.d.
password pwd
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the BGP VRF neighbor password using a plain
text. This password is shown encrypted after the commit.
(config)# router bgp 65000 vrf green neighbor 50.50.50.1 remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# password pwdTest
(config-bgp-vrf-neighbor-50.50.50.1)# commit
This example shows how to configure the BGP VRF neighbor password using an en-
crypted password.
(config)# router bgp 65000 vrf green neighbor 50.50.50.1 remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# password "hls:2922743918:337ZpL=Z"
(config-bgp-vrf-neighbor-50.50.50.1)# commit
This example shows how to configure the BGP VRF neighbor password using special
characters (i.e: " " , “?” , “!” , “;”). Please note that it is necessary to use double
quotation marks in this case.
(config)# router bgp 65000 vrf green neighbor 50.50.50.1 remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# password "pwd?test:2"
(config-bgp-vrf-neighbor-50.50.50.1)# commit
Password must be enclosed in double quotation marks if special characters were used
(i.e: " " , “?” , “!” , “;”).
Note that in an established BGP session if password is configured or changed the session
will be restarted.
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Description: Specifies the BGP VRF neighbor address in IPv4 address format.
Value: a.b.c.d.
remote-as as-number
Value: 1-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a remote Autonomous System (AS) number for
a VRF neighbor.
(config)# router bgp 65000 vrf red neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# remote-as 65000
(config-bgp-vrf-neighbor-50.50.50.1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the BGP VRF neighbor source address to be used during the session estab-
lishment.
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
neighbor address
Value: a.b.c.d.
update-source-address address
Description: Specifies the BGP neighbor source address in IPv4 address for-
mat.
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example show how to configure the source address for a BGP VRF neighbor in the
neighbor command tree.
(config)# router bgp 65000 vrf red neighbor 50.50.50.1
(config-bgp-vrf-neighbor-50.50.50.1)# update-source-address 100.100.100.1
(config-bgp-vrf-neighbor-50.50.50.1)# commit
Commit complete.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
as-number
Value: 1-4294967295.
vrf vrf-name
router-id id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
When the router-id for the BGP router in the VRF is not configured, the global BGP router-
id is used.
Example:
This example shows how to configure the router-id for the BGP router in the VRF red.
(config)# router bgp 65000 vrf red router-id 1.1.1.1
(config-bgp-65000)# commit
N/A
Hardware restrictions
N/A
show ip bgp
Description
Supported Platforms
Syntax
Parameters
vrf name
Output Terms
Output Description
VRF Name Indicates the VRF name for the current BGP instance.
BGP router
Indicates the router identifier of BGP.
identifier
Output Description
Eligible routes The number of prefixes received that are eligible to become active.
V BGP version.
How long the neighbor is in the established state or since the last
time it was established. When zeroed, the session were never es-
Up/Down
tablished. See the usage guidelines of this command for information
about time counter format.
The BGP neighbor state while the session is not established or the
State/PfxRcd number of prefixes received from the neighbor if the session is al-
ready established.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The time counter format is showed using only three units progressively:
Example:
This example shows summarized information about BGP routers on global VRF.
# show ip bgp
BGP router identifier 1.1.10.1, local AS number 101, Admin Status: up
ipv4 unicast statistics:
iBGP routes in : 1 eBGP routes in : 0 Eligible routes : 0
Ineligible routes : 1 Active routes : 0 Advertised routes : 0
ipv6 unicast statistics:
This example shows summarized information about all BGP routers on VRFs.
N/A
Hardware restrictions
N/A
Description
Shows information about communities received from neighbors and included in the BGP
routing table.
Supported Platforms
Syntax
Parameters
community
Value: N/A
network ip-address
Output Terms
Output Description
LocPrf Indicates the route local preference value. The default value is 100.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
This example shows how to use this command to list all communities.
This example shows how to use this command to filter a specific community.
This example shows how to use this command to filter a specific network.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show ip bgp [ vrf name ] neighbor [ ip-address | summary | brief | detail | extensive
]
Parameters
vrf name
ip-address
summary
Value: N/A
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
Output Terms
Output Description
Port Indicates the remote and local TCP ports used in this connection.
Elapsed time since the last BGP Update message was received from
Last received the neighbor. If no Update messages were received, this value re-
Update message mains zeroed. See the usage guidelines of this command for infor-
mation about time counter format.
Output Description
Elapsed time since the last BGP message was received from the
Last received neighbor. If no BGP messages were received, this value remains
message zeroed. See the usage guidelines of this command for information
about time counter format.
How long the neighbor is in the established state or since the last
time it was established. When zeroed, the session was never estab-
Up/Down time
lished. See the usage guidelines of this command for information
about time counter format.
Time interval in seconds for the hold timer established with the
Hold time
neighbor.
Time interval in seconds for the keepalive timer established with the
Keepalive
neighbor.
Address family Address family IPv4 Unicast capability was advertised and/or re-
IPv4 Unicast ceived.
Address family Address family IPv6 Unicast capability was advertised and/or re-
IPv6 Unicast ceived.
Four Bytes AS
Four Bytes AS Number capability was advertised and/or received.
Number
Output Description
Route Refresh
Route Refresh Cisco capability was advertised and/or received.
Cisco
Total: the number of all BGP message types exchanged with the
neighbor.
BGP transitions The total number of times the state transitioned into established
established state for this neighbor.
Output Description
Last BGP event The last BGP event which was used to transition the BGP state.
Selected local The local address used by the transport connection for the peering
address session.
Selected local The local port used by the transport connection for the peering ses-
port sion.
Selected remote The remote port used by the transport connection for the peering
port session.
Peer prefix The number of prefixes exchanged with the peer classified according
counters to the performed action.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The time counter format is showed using only three units progressively:
When the command does not provide any VRF filter, only the information about the BGP in
the global VRF will be displayed.
Example:
This example shows how to use the show ip bgp neighbor brief command.
Please note that for sessions not established the Port value is zero.
To show just the entry with Remote IP address 100.100.100.1, the following command
must be used:
To order neighbor entries by the Remote address column, the following command must
be used:
This example shows how to use the show ip bgp neighbor detail command.
This example shows how to use the show ip bgp neighbor extensive command.
Received: 1 Sent: 1
Accepted: 1 Advertised: 1
Rejected: 0 Active: 0
Local AS: 300;
Local address: 2222::2; Admin: enable; BGP state: established;
BGP Version: 4; Remote address: 1111::1; Remote AS: 200;
Last received update message: 01:00:18;
Last received message: 00:00:53;
Up/Down time: 01:06:33;
Neighbor ID: 1.1.1.1;
Hold time: 180 secs;
Keepalive: 60 secs;
Neighbor capabilities:
Address family IPv4 Unicast: advertised
Address family IPv6 Unicast: advertised and received
Four Bytes AS Number: advertised and received
Route Refresh: advertised and received
Route Refresh Cisco: advertised and received
Message counters:
Type Sent Received
---- ---- --------
Open 2 2
Notification 0 1
Update 0 11
Keepalive 203 203
Route refresh 0 0
Total 205 217
Connect retries: 2; BGP transitions established: 2;
Last BGP state: Established; Last BGP event: received-keepalive;
Selected local address: 2222::2;
Selected local port: 39015; Selected remote port: 179;
Peer prefix counters:
ipv4 unicast:
Received: 0 Sent: 0
Accepted: 0 Advertised: 0
Rejected: 0 Active: 0
Peer prefix counters:
ipv6 unicast:
Received: 5 Sent: 0
Accepted: 3 Advertised: 0
Rejected: 2 Active: 3
This command shows brief information about neighbors from the given VRF (red, in the
example).
This command shows just summary information about neighbors from all VRFs.
For sessions not established the Local/Remote Port value will display zero and Local Ad-
dress will display “0.0.0.0”.
Hardware restrictions
N/A
Description
Shows information about prefixes received from neighbors and included in the BGP rout-
ing table.
Supported Platforms
Syntax
Parameters
vrf name
destination prefix
Output Terms
Output Description
VRF Name Indicates the VRF name for the current BGP instance.
Output Description
LocPrf Indicates the route local preference value. The default value is 100.
Learned from Indicates the IP address from where this entry was learned from.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
This example shows how to use this command to list prefixes learned on VRF Global.
Please note the different status code for entries “221.10.0.19/19” since one was selected
as best path due to higher local preference.
# show ip bgp prefixes
Status codes: s suppressed; d damped; h history; * valid; > best; i - internal;
S Stale;
Origin codes: i - IGP; e - EGP; ? - incomplete;
Network Next Hop Metric LocPrf Weight Learned from Path
-------------------------------------------------------------------------------
*> 221.10.0.0/19 172.16.78.1 0 200 0 172.16.78.1 65001 ?
*> 221.10.0.0/20 172.16.78.1 0 100 0 172.16.78.1 65001 ?
* 221.10.0.0/19 172.16.78.3 0 100 0 172.16.78.3 65001 ?
*> 221.10.16.0/20 172.16.78.3 0 100 0 172.16.78.3 65001 ?
*>i 2001::/64 2002::3 0 100 0 1111::1 i
*>i 2002::/64 1111::1 0 100 0 1111::1 i
* i 5050::/64 8009::2 0 100 0 1111::1 i
*>i 8009::/64 1111::1 0 100 0 1111::1 i
To show just the network 221.10.16.0/20 entry, use the following destination filter:
Similarly, to search for all networks that start with 221.10.X.X, this filter could be used:
This example shows how to use this command to list prefixes learned on all VRFs includ-
ing VRF global.
N/A
Hardware restrictions
N/A
Description
Shows information about incoming and outgoing BGP labels for each prefix on a Virtual
Private Network IPv4 (VPNv4).
Supported Platforms
This command is not supported in the following platforms: DM4610, DM4615, DM4050,
DM4250.
Syntax
Parameters
vrf name
vpnv4 labels
Description: Shows the incoming and outgoing labels for each prefix on a
VPNv4.
Value: N/A
Output Terms
Output Description
VRF Name Indicates the VRF name for the current BGP instance.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This command can be used to show information about the prefixes and respective in-
coming and outgoing labels on a VPNv4.
Example:
This example shows how to use this command to display all prefixes and the respec-
tive labels related to VRF global.
To show the VPNv4 information for all VRFs the following command can be used:
To show the VPNv4 information for a specific VRF the following command can be used:
N/A
Hardware restrictions
N/A
OSPF
This topic describes the commands related to management of OSPF topologies such as
commands to configure the OSPF parameters or to inspect the protocol status.
clear ospf
Description
Supported Platforms
Syntax
Parameters
neighbor
Value: N/A
neighbor ip neighbor-ip
Description: Clears only neighbor information for the specified OSPF neigh-
bor.
Value: 0.0.0.0-255.255.255.255.
Description: Clears only neighbor information for the specified OSPF process
ID.
Value: 1-65535.
process process-id
Description: Clears OSPF information for the specified OSPF process ID.
Value: 1-65535.
statistics interface
Value: N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
The command “clear ospf process” will restart all OSPF adjacencies from the specified
router instance. The command “clear ospf neighbor” will restart all OSPF adjacencies if
neighbor address was not specified.
Hardware restrictions
N/A
router ospf
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified.
It is not possible to associate the VRF ‘mgmt’ with an OSPF
router. For platforms with VRF restrictions, only the VRF ‘global’
is available.
Value: string.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area-id
Default Value: 0.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area-id
Default Value: 0.
interface-name
Description: Specifies L3 and loopback interfaces for the OSPF router. The
L3 and loopback interfaces must be created before the commit.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name administrative-
status status
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
Value: L3 interface.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# area 0.0.0.0
(config-area-0.0.0.0)# interface l3-vlan100 administrative-status down
(config-ospf-area-intf-l3-vlan100)# commit
N/A
Hardware restrictions
N/A
Description
Configures the authentication type for an OSPF interface. Only one type of authentication
may be configured.
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name authen-
tication { md5 | none | simple-password } [authentication-key-id key-id]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
Value: L3 interface.
Value: 0-255.
Default Value: 0.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the authentication key for an OSPF interface. This command is only available
after an authentication type of MD5 or simple password has been configured.
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name authentication-
key key
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
Value: L3 interface.
authentication-key key
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4250, DM4610,
DM4615.
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name bfd
session-type type
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
Description: Configures BFD session-type for this OSPF interface. The none
type means BFD is disabled for this OSPF interface. The de-
sired type means BFD is enabled right after the OSPF session
establishment and will be used to monitor the session. In case
of session type mismatch between the two endpoints, the OSPF
may be run on this interface ignoring BFD state.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
When the session type is changed from desired to none, the OSPF session may flap.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name cost cost
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
cost cost
Value: 1-65535
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures how long the OSPF process will wait before declaring a neighbor down if it
stops receiving Hello packets.
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name dead-
interval {seconds | minimal fast-hello-multiplier multiplier}
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
dead-interval seconds
Value: 1-65535.
Value: 3-20.
Default Value: 5.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
A mismatch in the OSPF dead-intervals between neighbors will not permit the adjacency
to be established or cause it to goes down.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name hello-
interval seconds
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
hello-interval seconds
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# area 0.0.0.0
(config-area-0.0.0.0)# interface l3-vlan100 hello-interval 20
(config-ospf-area-intf-l3-vlan100)# commit
A mismatch in the OSPF hello-intervals between neighbors will not permit the adjacency
to be established or cause it to goes down.
Hardware restrictions
N/A
Description
Disables OSPF Maximum Transmission Unit (MTU) mismatch detection on received Database
Description (DBD) packets.
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name mtu-
ignore
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
mtu-ignore
Value: N/A
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface l3-interface-name network-
type type
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
interface l3-interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
network-type type
Description: Defines the network type to be used for this interface. For
broadcast, the interface must be connected to a broadcast net-
work. For point-to-point, the connection is between a single
source and a single destination.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface interface-name passive
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
Default Value: 0.
interface interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
passive
Value: N/A
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# area 0.0.0.0
(config-area-0.0.0.0)# interface l3-vlan100 passive
(config-ospf-area-intf-l3-vlan100)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id interface l3-interface-name router-
priority priority
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
interface l3-interface-name
Description: Specifies L3 interface for the OSPF router. The L3 interface must
be created before the commit.
router-priority priority
Description: Defines the router priority value, which determines the desig-
nated router for the specific network.
Value: 0-255.
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id nssa [no-summary | suppress-
external]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
nssa
Description: Defines the OSPF area as NSSA. It is not possible to define the
backbone area (area-id 0 or 0.0.0.0) or a stub area as NSSA.
Value: N/A
no-summary
Value: N/A
suppress-external
Description: When the NSSA ABR is also an ASBR, prevents it from originat-
ing Type-7 LSAs into the NSSA for redistributed external routes.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] area area-id range ip mask [advertise | not-
advertise]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
range ip mask
Description: Specifies the IP address and mask portion of the range. All inter-
area network addresses that match the specified area range are
summarized.
Value: N/A
ip
Value: 0.0.0.0-255.255.255.255.
mask
Value: 0.0.0.0-255.255.255.255.
advertise
Value: N/A
not-advertise
Value: N/A
Default
advertise.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
area area-id
stub
Description: Defines the OSPF router area as stub area. It is not possible to
define the backbone area (area-id 0 or 0.0.0.0) as a stub area.
Value: N/A
no-summary
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the prefix-list to filter prefixes advertisement from route table into OSPF do-
main.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
export-prefix-list prefix-list-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to associate the prefix-list named PRX_LIST_EXPORT for export
with an OSPF router. This prefix-list must be previously created.
(config)# router ospf 1
(config-ospf-1-vrf-global)# export-prefix-list PRX_LIST_EXPORT
(config-ospf-1-vrf-global)# commit
This command only works on the prefixes redistributed by the ASBR into OSPF.
Hardware restrictions
N/A
Description
Configures the prefix-list to filter the installation of incoming OSPF prefixes on route
table.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
import-prefix-list prefix-list-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to associate the prefix-list for import named PRX_LIST_IMPORT
with an OSPF router. This prefix-list must be previously created.
(config)# router ospf 1
(config-ospf-1-vrf-global)# import-prefix-list PRX_LIST_IMPORT
(config-ospf-1-vrf-global)# commit
Note that once a prefix-list is associated to the OSPF router all other prefixes are denied,
i.e., they are not installed on HW. But, even if not installed to HW, it does not affect
network topology: prefixes are added to OSPF database and are still forwarded to other
neighbors.
Hardware restrictions
N/A
Description
Configures the maximum number of equal-cost multi-paths (ECMP) for each OSPF router
process.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
Value: 1-16.
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the maximum number of paths of a router ospf.
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# maximum paths 4
(config-ospf-1-vrf-global)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4250, DM4610,
DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command can be executed directly via CLI. This command requires a license to be
used. Please contact the support for further information.
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] redistribute {bgp [metric metric-value] | con-
nected | static} [match-address a.b.c.d/x]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
redistribute bgp
Description: Redistributes BGP routes into the domain of this OSPF router.
Value: N/A
redistribute connected
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this OSPF router.
Value: N/A
match-address a.b.c.d/x
metric
Description: Allows to set the metric that will be carried from BGP process to
OSPF process. The default metric value is 1.
Value: 1-16777214.
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Example:
This example shows how to configure a metric for the redistributed routes from BGP.
It allows managing the metric selection criteria in the OSPF database.
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# redistribute bgp
(config-redistribute-connected)# metric 1000
(config-redistribute-connected)# exit
(config-ospf-1-vrf-global)# commit
Redistributed routes always use metric-type 2 and the metric value is the original value
of the external route.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
router-id id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Changing the OSPF router-id will restart the OSPF router process.
Hardware restrictions
N/A
Description
Configures the minimum interval in which the same link-state advertisement (LSA) from
OSPF neighbors is accepted by a router OSPF.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
lsa-arrival delay
Description: Specifies the minimum delay between accepting the same LSA
in milliseconds.
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
hold-interval interval
Description: Specifies the minimum delay between originating the same LSA
in milliseconds.
Value: 0-600000.
max-interval interval
Value: 0-600000.
start-interval interval
Description: Specifies the start delay to generate the first LSA occurrence in
milliseconds.
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a router ospf timers throttle lsa-originate.
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# timers throttle
(config-throttle)# lsa-originate hold-interval 1000
(config-throttle)# lsa-originate max-interval 10000
(config-throttle)# lsa-originate start-interval 500
(config-throttle)# commit
N/A
Hardware restrictions
N/A
Description
Configures the scheduling for Shortest Path First (SPF) calculations of a OSPF router.
Supported Platforms
Syntax
router ospf process-id [vrf vrf-name] timers throttle spf hold-interval interval |
max-interval interval | start-interval interval
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
vrf vrf-name
Description: Specifies the name of the VRF this router will be associated
with. The VRF ‘global’ is implied if no parameter is specified. It
is not possible to associate the VRF ‘mgmt’ with an OSPF router.
Value: string.
hold-interval interval
Value: 0-600000.
max-interval interval
Description: Specifies the maximum wait time for SPF calculation in millisec-
onds.
Value: 0-600000.
start-interval interval
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a router ospf timers throttle spf.
# config terminal
Entering configuration mode terminal
(config)# router ospf 1
(config-ospf-1-vrf-global)# timers throttle
(config-throttle)# spf hold-interval 1000
(config-throttle)# spf max-interval 10000
(config-throttle)# spf start-interval 500
(config-throttle)# commit
N/A
Hardware restrictions
N/A
show ip ospf
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
process-id
Value: 1-65535.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
process-id
Value: 1-65535.
area-id
link-state-id
Description: Shows only information identified by the specified Link State ID.
Value: 0.0.0.0-255.255.255.255.
brief
Value: N/A
detail
Value: N/A
adv-router adv-router-id
Value: 0.0.0.0-255.255.255.255.
opaque-area
Value: N/A
asbr
Value: N/A
external
Value: N/A
network
Value: N/A
router
Value: N/A
self-originate
Description: Shows only information about self-originated LSAs (from the lo-
cal router).
Value: N/A
summary
Value: N/A
type-5
Value: N/A
type-11
Value: N/A
Output Terms
Output Description
Advertising router
Indicates the advertising router.
Output Description
Advertisement
Indicates the length in bytes of the LSA.
length
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
statistics
Value: N/A
interface-ip
Value: 0.0.0.0-255.255.255.255.
process-id
Value: 1-65535.
Output Terms
Output Description
Output Description
Indicate the number of OSPF packet header ‘bad source’ errors de-
bad-source
tected on each interface.
Output Description
Indicates the number of OSPF packets with an invalid type field re-
rx-invalid
ceived on each interface.
Output Description
Indicates the number of packets that OSPF could not send on each
tx-failed
interface.
Indicates the number of bytes sent in packets that OSPF could not
tx-failed-byte
send on each interface.
Output Description
tx-hello Indicates the number of OSPF Hello packets sent on each interface.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
Router-ID
Value: 0.0.0.0-255.255.255.255.
process-id
Value: 1-65535.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
OSPFV3
This topic describes the commands related to management of OSPFv3 topologies such
as commands to configure the OSPFv3 parameters or to inspect the protocol status.
clear ospfv3
Description
Supported Platforms
Syntax
Parameters
process process-id
Description: Clears OSPFv3 information for the specified OSPFv3 process ID.
Value: 1-65535.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
This command will restart all OSPFv3 adjacencies from the specified router instance.
Hardware restrictions
N/A
router ospfv3
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area-id
Default Value: 0.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area-id
Default Value: 0.
interface-name
Description: Specifies L3 and loopback interfaces for the Router OSPFv3. The
L3 and loopback interfaces must be created before the commit.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
Value: L3 interface.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
cost cost
Value: 1-65535
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures how long the OSPFv3 process will wait before declaring a neighbor down if it
stops receiving Hello packets.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
dead-interval seconds
Value: 2-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
A mismatch in the OSPFv3 dead-intervals between neighbors will not permit the adja-
cency to be established or cause it to goes down.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
hello-interval seconds
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
A mismatch in the OSPFv3 hello-intervals between neighbors will not permit the adja-
cency to be established or cause it to goes down.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
mtu-ignore
Value: N/A
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
interface l3-interface-name
network-type type
Description: Defines the network type to be used for this interface. For point-
to-point, the connection is between a single source and a single
destination.
Value: point-to-point.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
Default Value: 0.
interface interface-name
passive
Value: N/A
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Passive interfaces neither establish adjacencies nor send OSPFv3 updates, but it is still
advertised as part of the OSPFv3 routing domain. Commands to configure the passive
interface.
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area area-id
range x:x:x:x::x/y
Description: Specifies the IPv6 network portion of the range. All inter-area
network addresses that match the specified area range are sum-
marized.
advertise
Value: N/A
not-advertise
Value: N/A
Default
advertise.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the maximum number of equal-cost multi-paths (ECMP) for the OSPFv3 router
process.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
Value: 1-16.
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the maximum number of paths of a router ospfv3.
# config terminal
Entering configuration mode terminal
(config)# router ospfv3 1
(config-ospfv3-1)# maximum paths 4
(config-ospfv3-1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
redistribute connected
Value: N/A
redistribute static
Description: Redistributes static routes into the domain of this OSPFv3 router.
Value: N/A
match-address x:x:x:x::x/x
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Redistributed routes always use metric-type 2 and the metric value is the original value
of the external route.
Hardware restrictions
N/A
Description
Configures the minimum interval in which the same link-state advertisement (LSA) from
OSPFv3 neighbors is accepted by a router OSPFv3.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
lsa-arrival
Description: Specifies the minimum delay between accepting the same LSA
in milliseconds.
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
hold-interval
Description: Specifies the minimum delay between originating the same LSA
in milliseconds.
Value: 0-600000.
max-interval
Value: 0-600000.
start-interval
Description: Specifies the start delay to generate the first LSA occurrence in
milliseconds.
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a router ospf timers throttle lsa-originate.
# config terminal
Entering configuration mode terminal
(config)# router ospfv3 1
(config-ospfv3-1)# timers throttle
N/A
Hardware restrictions
N/A
Description
Configures the scheduling for Shortest Path First (SPF) calculations of a router OSPFv3.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
hold-interval
Value: 0-600000.
max-interval
Description: Specifies the maximum wait time for SPF calculation in millisec-
onds.
Value: 0-600000.
start-interval
Value: 0-600000.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a router ospfv3 timers throttle spf.
# config terminal
Entering configuration mode terminal
(config)# router ospfv3 1
(config-ospfv3-1)# timers throttle
(config-throttle)# spf hold-interval 1000
(config-throttle)# spf max-interval 10000
(config-throttle)# spf start-interval 500
(config-throttle)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
router-id id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Changing the OSPFv3 router-id will restart the OSPFv3 router process.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
process-id
Value: 1-65535.
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
1.1.1.1 3 up up 1
# show ipv6 ospf brief
Router-ID Version Admin Op-status Routing-process
--------------- ------- ----- --------- ---------------
1.1.1.1 3 up up 1
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
process-id
Value: 1-65535.
area-id
inter-area-prefix
Value: N/A
inter-area-router
Value: N/A
intra-area-prefix
Value: N/A
router
Value: N/A
adv-router adv-router-id
Value: 0.0.0.0-255.255.255.255.
self-originate
Description: Shows only information about self-originated LSAs (from the lo-
cal router).
Value: N/A
link-state-id
Description: Shows only information identified by the specified Link State ID.
Value: 0.0.0.0-255.255.255.255.
brief
Value: N/A
detail
Value: N/A
external
Value: N/A
link
Value: N/A
Output Terms
Output Description
Advertisement
Indicates the length in bytes of the LSA.
length
Output Description
Advertising router
Indicates the advertising router.
Indicates the bits that represent various router roles within the
Bits
OSPFv3 domain.
Destination
Indicates the router-ID of the destination router.
Router-ID
Forwarding Address
Indicates the forwarding address.
Interface IP
Indicates the interface IPv6 address.
address
Link-local
Indicates the originating router’s link-local interface address.
Interface Address
Output Description
Neighbor
Indicates the remote neighbor interface ID.
interface-ID
Neighbor router-ID
Indicates the router-ID from the neighbor router.
Number of
Indicates the number of OSPFv3 interfaces on the router.
interfaces
Number of prefixes
Indicates the number of prefixes present into the LSA.
Referenced
advertising router Indicates the originating router-ID.
Referenced LS Type Indicates the type of LSA to which these prefixes are associated with.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
These examples show how to use show commands for OSPFv3 database information.
The full prefixes list can be viewed in the intra-area LSAs using the show ipv6 ospf
database detail command.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
Router-ID
Value: 0.0.0.0-255.255.255.255.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
VRRP
This topic describes the commands related to management of VRRP topologies such as
commands to configure the VRRP parameters or to inspect the protocol status.
router vrrp
Description
Supported Platforms
Syntax
router vrrp
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
Value: x:x:x:x::x.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Examples:
This example shows how to configure virtual IPv4 address for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# address 10.10.10.1
(config-vrrp-if-address-family-10)# commit
This example shows how to configure virtual IPv6 link-local address and virtual IPv6
address for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan101
(config-vrrp-if)# address-family ipv6
(config-vrrp-if-address-family)# vr-id 11
(config-vrrp-if-address-family-11)# address link-local auto-configuration
(config-vrrp-if-address-family-11)# address 2001:db8::1
(config-vrrp-if-address-family-11)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the administrative status for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# administrative-status down
(config-vrrp-if-address-family-10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
advertisement-interval interval
Value: 1-40.
Default Value: 1.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the advertisement interval for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# advertisement-interval 40
(config-vrrp-if-address-family-10)# commit
Low maximum advertisement interval will generate messages at a high rate and may
affect bandwidth throughput.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the simple text password authentication for a
VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# authentication simple-text test123
(config-vrrp-if-address-family-10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
preempt preempt
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the preemption for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# preempt false
(config-vrrp-if-address-family-10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
priority priority
Value: 1-254.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Priority value of 255 will be automatically assigned to the VRRP router address owner.
Example:
This example shows how to configure the priority for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# priority 150
(config-vrrp-if-address-family-10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
Value: 1-253.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the track interface and decrement for a VRRP
router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# track decrement 60
(config-vrrp-if-address-family-10)# track interface l3-uplink1
(config-vrrp-if-address-family-10)# track interface l3-uplink2
(config-vrrp-if-address-family-10)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Description: Specifies the address family for which VRRP will be enabled on
this interface.
vr-id id
Value: 1-255.
version vrrp-version
Value: v2 | v3.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This this command will be available only for IPv4 address family.
Examples:
This example shows how to configure protocol version for a VRRP router.
(config)# router vrrp
(config-vrrp)# interface l3-vlan100
(config-vrrp-if)# address-family ipv4
(config-vrrp-if-address-family)# vr-id 10
(config-vrrp-if-address-family-10)# version v2
(config-vrrp-if-address-family-10)# commit
Changing the VRRP router protocol version will restart the VRRP router process.
Hardware restrictions
N/A
PBR
This topic describes the commands related to management of PBR topologies such as
commands to configure the PBR parameters or to inspect the protocol status.
router pbr
Description
Create policy-based rules that are applied before the normal layer 3 routing. Also allows
enforcing the L3 routing as a rule exception.
Supported Platforms
Syntax
Parameters
id
Value: 1-64
priority rule_priority
Description: The PBR rule priority. Lower values have higher priority. Must
be unique between all PBR rules. Priority is a mandatory con-
figuration.
Value: 0-255
description description_string
Description: The PBR rule description. A user field to help identify the rule
meaning. Enclose the content in double quotes for multi word
description.
Description: A PBR rule match for source IPv4 host or subnet address. Any
packet with source IP (or masked range) that matches with the
configured one will be forwarded by the PBR rule. For a single
IP match, the mask can be ommited. At least one match type
(source, destination or interface) must be provided.
Description: A PBR rule match for destination IPv4 host or subnet address.
Any packet with destination IP (or range) that matches with the
configured one will be forwarded by the PBR rule. For a single
IP match, the mask can be ommited. At least one match type
(source, destination or interface) must be provided.
Description: A PBR rule match for input interface names. Any packet that
enters the switch trough any of the named interfaces will be
forwarded by the PBR rule. Several interfaces can be configured
in the rule. At least one match type (source, destination or
interface) must be provided.
action l3-routing
Description: A PBR rule action that overrides another PBR rule, by enforcing
the use of the L3-routing. This can be used to add an exception
to a much broader rule. This kind of exception must have a
higher priority than the rule it is meant to override. Only one
action type (l3-routing, next-hop) must be provided.
Value: none
Description: A PBR rule action that forwards all matched traffic to an spe-
cific host. Only one action type (l3-routing, next-hop) must be
provided.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
“Client X”
With priority 10
Example:
“Client X”
With priority 5
Example:
“Client Z”
With priority 20
Destinated to IP 172.20.100.100
N/A
Hardware restrictions
N/A
Description
Display information about Policy-based routes status and configuration. When ommited
the rule-id, the show displays all configured rules status.
Supported Platforms
Syntax
Parameters
rule-id
Value: N/A
Output Terms
Output Description
Priority The Priority of the rule. Lower values are applied first.
The Source IP that should match (in the packets) to the rule be en-
Match Source IP
forced.
Match Destination The Destination IP that should match (in the packets) to the rule be
IP enforced.
Output Description
The Inbound interface(s) that should match (in the packets) to the
Match Interface
rule be enforced.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
#
</code> <newline>
When the rule id is specified:
# show router pbr 1
Match Match Action Hardware
ID Priority Source IP Dest. IP Match Interface Next-Hop Status Description
--------------------------------------------------------------------------------------------------------
1 1 - 3.3.3.3/24 gigabit-ethernet-1/1/1 1.1.1.1 installing -
hundred-gigabit-ethernet-1/1/1
#
None
Hardware restrictions
None
VRF
This topic describes the commands related to management of VRF topologies such as
commands to configure the VRF parameters or to inspect the protocol status.
vrf
Description
Creates a VRF.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf-name
Description: Specifies the name of the VRF. Only accepts alphanumeric char-
acters, ‘_’ and ‘-’.
description vrf-description
Description: Specifies the description of the VRF. It may point out a more
meaningful text about its purpose.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Use the vrf command to create a new virtual routing forwarding instance for the system.
There are two VRFs already created, global is the default VRF and mgmt is a VRF dedi-
cated to out-of-band management interface. Neither of them can be changed or deleted.
Example:
This example shows how to configure a new VRF named “green” for the system.
(config)# vrf green
(config)# commit
Commit complete.
The overall number of available VRFs includes both the system’s reserved global and
mgmt. The word all is reserved for VRF filter purposes, thus no VRF named all can be
created.
Hardware restrictions
The following platforms support only the system VRFs global and mgmt:
DM4050
DM4610
DM4615
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf-name
Description: Specifies the name of the VRF. Only accepts alphanumeric char-
acters, ‘_’ and ‘-’.
address-family { ipv4 }
unicast
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This example shows how to configure an address-family ipv4 unicast in the VRF.
(config)# vrf green address-family ipv4 unicast
(config-address-family-ipv4/unicast)# commit
N/A
Hardware restrictions
N/A
vrf rd
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf-name
Description: Specifies the name of the VRF. Only accepts alphanumeric char-
acters, ‘_’ and ‘-’.
rd { ASN:nn | IPv4:nn }
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a new route distinguisher in ASN:nn format.
(config)# vrf green rd 65000:1000
(config-vrf-green)# commit
This example shows how to configure a new route distinguisher in IPv4:nn format.
(config)# vrf green rd 10.20.2.3:1000
(config-vrf-green)# commit
Route distinguisher must be unique in the system. The VRFs global and mgmt do not
support route distinguisher configuration.
Hardware restrictions
N/A
vrf route-target
Description
Supported Platforms
This command is not supported in the following platforms: DM4050, DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf-name
Description: Specifies the name of the VRF. Only accepts alphanumeric char-
acters, ‘_’ and ‘-’.
address-family { ipv4 }
unicast
route-target export
Value: N/A
route-target import
Value: N/A
route-target-number
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This example shows how to configure a route target in ASN:nn format to be exported.
((config-vrf-red))# address-family ipv4 unicast route-target export 1:2
(config-route-target-export/1:2)# commit
This example shows how to configure a route target in ASN:nn format to be imported.
((config-vrf-red))# address-family ipv4 unicast route-target import 1:4
(config-route-target-import/1:4)# commit
N/A
Hardware restrictions
N/A
CHAPTER 7: MPLS
This chapter describes the commands related to management of MPLS topologies in the
DmOS CLI. MPLS features are available under specific license control. Please contact the
Technical Support for further information.
INFRA
This topic describes the commands related to management of basic MPLS infrastructure
such as commands to configure MPLS generic behavior parameters.
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
action action
in-label label
in-protocol protocol
out-label label
out-protocol protocol
outgoing-interface l3-interface
Value: l3-vlan id
status status
Output Terms
Output Description
Prefix or
Display the LSP prefix or Tunnel-Name associated with MPLS entry.
Tunnel-Name
Display the outgoing vlan interface for the MPLS traffic associated
Out interface
with entry.
Output Description
Display the MPLS outgoing vlan interface for the MPLS traffic associ-
ated with entry.
Active: indicates entry is active.
Status
Pending: indicates entry has installation pending due neighbor
resolution.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of MPLS entries installed on data plane the following command
can be used:
Example:
Filter by Prefix:
Example:
Filter by Action:
Example:
Filter by In Label:
Example:
Filter by In Protocol:
Example:
Example:
Filter by Status:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Parameters
backup backup
destination dest
id id
in-label label
in-vlan vlan
instance instance
name name
out-label label
out-vlan vlan
status status
Output Terms
Output Description
Destination Display the IPV4 address associated with tunnel interface entry.
Instance Display the tunnel instance associated with tunnel interface entry.
Display status of the backup instance associated with the tunnel in-
terface.
available: Backup is current available.
Backup
in-use: Backup is current in use.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
It is possible to filter the results by ID, Name, Destination, Instance, In label, In VLAN,
Out label, Out VLAN, Backup, and Status.
Filter by ID:
Example:
Filter by Name:
Example:
Filter by Destination:
Example:
Filter by Instance:
Example:
Filter by In Label:
Example:
Filter by In VLAN:
Example:
Filter by Backup:
Example:
Filter by Status:
Example:
N/A
Hardware restrictions
N/A
Description
Show detailed RSVP-TE tunnel information for a single instance (by name or id).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Parameters
id id
name name
Output Terms
Output Description
Output Description
Src Display the IPV4 address associated with tunnel interface entry.
Display the status of the active tunnel instance. Contains the Admin,
Status
Oper, Role and Dir information.
Path option Describes all the paths defined for the tunnel.
Path-option
Display the index of the path.
attribute
Output Description
profile Display the name of the affinity profile associated with the path.
Tunnel LSP:
Display the Inlabel of the tunnel path.
Inlabel
Tunnel LSP:
Display the Outlabel of the tunnel path.
Outlabel
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Use the command to show the detailed information of a tunnel (by id):
Example:
Use the command to show the detailed information of a tunnel (by name):
Example:
For unnamed tunnels (they receive a default name but can’t be queried by name) use
the show by id:
Example:
N/A
Hardware restrictions
N/A
L2VPN
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vpls-group name
vpn-name name
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To clear the VPLS counters values the following command can be used:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vpls-group name
vpn-name name
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To clear the VPWS counters values the following command can be used:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vpls-group name
vpn-name name
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To clear the L2VPN VPLS mac-address values the following commands can be used:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the MPLS L2VPN Pseudowire status log.
# config
(config)# mpls l2vpn
(config-l2vpn)# logging pw-status
(config-vpn-Name)# commit
N/A
Hardware restrictions
N/A
Description
The Group ID field is a textual string arbitrary value that is assigned to a group of Virtual
Private LAN Services (VPLS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
A textual string to uniquely identify a Virtual Private LAN Services (VPLS) that supports
Layer 2 VPN technology and provides multi-point Layer 2 connectivity for customers.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private LAN Services (VPLS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
administrative-status status
Description: Activates (up) or deactivates (down) the Virtual Private LAN Ser-
vices (VPLS).
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies a virtual bridge that connects the multiple access circuits together.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies the access interfaces to be attached inside a Virtual Private LAN Services (VPLS)
bridge-domain.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
access-interface id
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Vlan-mapping rules do not have effect over vpn access ports because the latter takes
precedence over the former.
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private LAN Services (VPLS)
access interface.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
access-interface id
administrative-status status
Description: Activates (up) or deactivates (down) the Virtual Private LAN Ser-
vices (VPLS) acess interface.
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn bridge-domain access-interface administrative-
status.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Name)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle-bd)# access-interface gigabit-ethernet-1/1/1
(config-access-interface-gigabit-ethernet-1/1/1)# administrative-status down
(config-access-interface-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the encapsulation of customer VLANs (C-VLANs) on a Virtual Private LAN Ser-
vices (VPLS) access interface.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
access-interface id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn bridge-domain access-interface encap-
sulation dot1q.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle-bd)# qinq
(config-vpn-Seattle-bd)# access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# encapsulation dot1q 5,10-15,20
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
access-interface id
encapsulation untagged
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn bridge-domain access-interface encap-
sulation untagged.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle)# qinq
(config-vpn-Seattle-bd)# access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# encapsulation untagged
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private LAN Services (VPLS)
bridge-domain.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
administrative-status status
Description: Activates (up) or deactivates (down) the Virtual Private LAN Ser-
vices (VPLS) bridge-domain.
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies the explicit Maximum Transmission Unit(MTU) of the Virtual Private LAN Ser-
vices(VPLS) bridge-domain.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
bridge-mtu value
Value: 64 - 9198.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the bridge-mtu value that explicitly specifies the
MTU value used by the VPLS.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle-bd)# bridge-mtu 64
(config-vpn-Seattle-bd)# commit
Make sure to set an appropriate MTU to account for all the encapsulation overhead that
will take place on your MPLS backbone to avoid packet drop. When the MTU is not
explicitly configured by this command the value set on this VPLS is the lowest MTU value
of the attached physical access interfaces.
Hardware restrictions
N/A
Description
Configures the Virtual Private LAN Services (VPLS) bridge-domain to match a specific
802.1Q VLAN packets (VLAN-based).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
dot1q id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
To configure a VLAN-based VPLS bridge-domain, perform this task on the provider edge
routers:
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle-bd)# dot1q 23
(config-vpn-Seattle-bd)# commit
A VPLS bridge-domain and a Layer 2 bridge-domain that have the same Dot1Q identifier
cannot share interfaces.
Hardware restrictions
N/A
Description
Configures the maximum limit of MAC addresses that can be learned on a Virtual Private
LAN Services (VPLS) bridge-domain.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4360, DM4370,
DM4610, DM4615.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
mac-limit value
Value: 1 - 32767.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Although mac-limit configuration is per VPN, MAC address table is common for all of them
in hardware. Therefore, according to the mac-limit value, one or a few VPNs can already
consume all the MAC address table entries.
Hardware restrictions
N/A
Description
Enable Selective Encapsulation QinQ mode for VPLS. This mode allows the configuration
of multiple VLANs in the access-interface encapsulation command in order to set
up a Selective Encapsulation VPN. This mode requires the vfi pw-type to be vlan and
contain the service-delimiting VLAN which will be stacked up top into the frame along
with the ingressed access VLANs.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
qinq
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a Selective Encapsulation VPN QinQ mode.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# bridge-domain
(config-vpn-Seattle-bd)# qinq
(config-vpn-Seattle-bd)# access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# encapsulation dot1q 5,10-15,20
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Enable the Transparent LAN Service (TLS) mode on a Virtual Private LAN Services (VPLS)
bridge-domain.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
bridge-domain
Value: N/A
transparent-lan-service
Description: Enable the Transparent LAN Service (TLS) mode on a VPLS bridge-
domain.
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies a textual string containing information about the Virtual Private LAN Services
(VPLS) entity.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
description text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies a Virtual Forwarding Instance (VFI) that connects multiples neighbors together.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies the IPv4 address to uniquely identify a Virtual Private LAN Services (VPLS)
neighbor.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private LAN Services (VPLS)
neighbor.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpls-group text vpn text vfi neighbor id administrative-status status
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
administrative-status status
Description: Activates (up) or deactivates (down) the Virtual Private LAN Ser-
vices (VPLS) neighbor.
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn vfi neighbor administrative-status.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# vfi
(config-vfi)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# administrative-status down
(config-neighbor-30.30.30.30)# commit
N/A
Hardware restrictions
N/A
Description
Specifies the pseudo-wire (PW) ID, a non-zero identifier that distinguishes between two
MPLS peers from the others. To connect two attachment circuits through a PW, you need
to associate each one with the same PW ID. This configuration is mandatory for neighbor
enabling.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
pw-id id
Value: 1-4294967294.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn vfi neighbor pw-id.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# vfi
(config-vfi)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-id 222
(config-neighbor-30.30.30.30)# commit
N/A
Hardware restrictions
N/A
Description
Specifies mechanisms to load-balance the traffic over the Virtual Private LAN Services(VPLS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
pw-load-balance
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a load-balance mechanism over VPLS traffic.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Name)# vpn Seattle
(config-vpn-Seattle)# vfi
(config-vfi)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-load-balance
(config-pw-load-balance)# commit
N/A
Hardware restrictions
N/A
Description
Specifies the Flow-Aware Transport(FAT) that provides the capability to identify individual
flows within a VPLS. This provides the routers the ability to use these flows to load-
balance traffic.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpls-group text vpn text vfi neighbor id pw-load-balance flow-label
value
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
pw-load-balance
Value: N/A
flow-label value
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Make sure that both edges on the VPN have a consistently FAT configuration.
Hardware restrictions
N/A
Description
Specifies the explicitly signalization of the Maximum Transmission Unit(MTU) on the Vir-
tual Private LAN Services(VPLS) neighbor.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpls-group text vpn text vfi neighbor id pw-mtu value
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
pw-mtu value
Value: 64 - 9198.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn vfi neighbor pw-mtu value that explic-
itly specifies the MTU value used on the VPLS neighbor signalization.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# vfi
(config-vfi)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-mtu 64
(config-neighbor-30.30.30.30)# commit
The pw-mtu configuration is used by the signalization process, signaling purpose only.
For packet dropping, check the access interface MTU.
When the pw-mtu is not explicitly configured by this command the MTU value signaled
by this VPLS is the same as the access interface MTU value.
Hardware restrictions
N/A
Description
Control the pseudowire (PW) split-horizon group to prevents/allows packets received from
a PW from being forwarded into another PW. This technique is important for creating
loop-free paths in a full-meshed network.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpls-group text vpn text vfi neighbor id split-horizon command
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
split-horizon command
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn vfi neighbor split-horizon.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# vfi
(config-vfi)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# split-horizon disable
(config-neighbor-30.30.30.30)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpls-group text vpn text vfi neighbor id tunnel-interface interface
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
neighbor id
Value: a.b.c.d.
tunnel-interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
vfi
Value: N/A
pw-type type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn vfi pw-type ethernet. In this mode, all
Ethernet frames received on the attachment circuit will be transmitted on a single PW.
This service corresponds to PW type 0x0005 “Ethernet”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# pw-type ethernet
(config-vpn-Seattle)# commit
This example shows how to configure the vpn vfi pw-type vlan. This mode uses access
dot1q id as a service-delimiting tag to map input Ethernet frames to respective PWs and
corresponds to PW type 0x0004 “Ethernet Tagged Mode”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# pw-type vlan
(config-vpn-Seattle)# commit
This example shows how to configure the vpn neighbor pw-type vlan with a explicit
VLAN Id. This mode uses a explicit service-delimiting tag to map input Ethernet frames
to respective PWs and corresponds to PW type 0x0004 “Ethernet Tagged Mode”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpls-group Washington
(config-vpls-group-Washington)# vpn Seattle
(config-vpn-Seattle)# pw-type vlan 22
(config-vpn-Seattle)# commit
The pw-type must be selected in such a way that it matches both ends of the VPLS
neighbors.
Hardware restrictions
N/A
Description
The Group ID field is a textual string arbitrary value that is assigned to a group of pseudo-
wire (PW).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
A textual string to uniquely identify a Virtual Private Wire Services (VPWS). A VPWS con-
nection deploys a Layer 2 service over MPLS to build a point-to-point topology connection
attaching end customer sites in a VPN.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Hardware restrictions
N/A
Description
Specifies the access interface for a Virtual Private Wire Services (VPWS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
access-interface id
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Vlan-mapping rules do not have effect over vpn access ports because the latter takes
precedence over the former.
Hardware restrictions
N/A
Description
Configures the desired administrative status on an access interface for a Virtual Private
Wire Services (VPWS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
access-interface id
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Enables the Virtual Private Wire Services(VPWS) access interface to match specific 802.1Q
VLAN packets (VLAN-based).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
access-interface intf-id
dot1q id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
To configure a VLAN-based VPWS, perform this task on the provider edge routers:
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)#access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# dot1q 23
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpws-group text vpn text access-interface intf-id encapsulation dot1q
values
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
access-interface intf-id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn access-interface encapsulation dot1q.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Washington)# vpn Seattle
(config-vpn-Seattle)# qinq
(config-vpn-Seattle)# access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# encapsulation dot1q 5,10-15,20
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Specifies the explicit Maximum Transmission Unit(MTU) of the Virtual Private Wire Ser-
vices(VPWS) access interface.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
mpls l2vpn vpws-group text vpn text access-interface intf-id mtu value
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
access-interface intf-id
mtu value
Description: Specifies the explicit MTU used by the VPWS access interface.
Value: 64 - 9198.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
To configure an explicit access interface MTU on a VPWS, perform this task on the
provider edge routers:
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)#access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# mtu 64
(config-access-port-gigabit-ethernet-1/1/1)# commit
Make sure to set an appropriate MTU to account for all the encapsulation overhead that
will take place on your MPLS backbone to avoid packet drop. When the mtu is not
explicitly configured by this command the mtu value set on this VPWS is the same one
set on the access interface. For a service-port access interface, mtu must be set to 2000
or less.
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private Wire Services (VPWS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
description text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies the IPv4 address to uniquely identify a Virtual Private Wire Services (VPWS)
neighbor.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the desired administrative status on a Virtual Private Wire Services (VPWS)
neighbor.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies the pseudo-wire (PW) ID, a non-zero identifier that distinguishes between two
MPLS peers from the others. To connect two attachment circuits through a PW, you need
to associate each one with the same PW ID. This configuration is mandatory for neighbor
enabling.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
pw-id id
Value: 1-4294967294.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Specifies mechanisms to load-balance the traffic over the Virtual Private Wire Services(VPWS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
pw-load-balance
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a load-balance mechanism over VPWS traffic.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-load-balance
(config-pw-load-balance)# commit
N/A
Hardware restrictions
N/A
Description
Specifies the Flow-Aware Transport(FAT) that provides the capability to identify individual
flows within a VPWS. This provides the routers the ability to use these flows to load-
balance traffic.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
pw-load-balance
Value: N/A
flow-label value
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Make sure that both edges on the VPN have a consistently FAT configuration.
Hardware restrictions
N/A
Description
Specifies the explicitly signalization of the Maximum Transmission Unit(MTU) on the Vir-
tual Private Wire Services(VPWS).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
pw-mtu value
Value: 64 - 9198.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn neighbor pw-mtu value that explicitly
specifies the MTU value used on the VPWS signalization.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-mtu 64
(config-neighbor-30.30.30.30)# commit
Make sure to set an appropriate MTU to account for all the encapsulation overhead that
will take place on your MPLS backbone to avoid packet drop. When the pw mtu is not
explicitly configured by this command the mtu value signaled by this VPWS is the same
as the access interface mtu value.
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
pw-type type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the vpn neighbor pw-type ethernet. In this mode,
all Ethernet frames received on the attachment circuit will be transmitted on a single PW.
This service corresponds to PW type 0x0005 “Ethernet”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-type ethernet
(config-neighbor-30.30.30.30)# commit
This example shows how to configure the vpn neighbor pw-type vlan. This mode uses
access dot1q id as a service-delimiting tag to map input Ethernet frames to respective
PWs and corresponds to PW type 0x0004 “Ethernet Tagged Mode”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-type vlan
(config-neighbor-30.30.30.30)# commit
This example shows how to configure the vpn neighbor pw-type vlan with a explicit
VLAN Id. This mode uses a explicit service-delimiting tag to map input Ethernet frames
to respective PWs and corresponds to PW type 0x0004 “Ethernet Tagged Mode”.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Name)# vpn Seattle
(config-vpn-Name)# neighbor 30.30.30.30
(config-neighbor-30.30.30.30)# pw-type vlan 22
(config-neighbor-30.30.30.30)# commit
The pw-type must be selected in such a way that it matches both ends of the VPWS.
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
neighbor id
Value: a.b.c.d.
tunnel-interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Enable Selective Encapsulation QinQ mode for VPWS. This mode allows the configuration
of multiple VLANs in the access-interface encapsulation command in order to set up
a Selective Encapsulation VPN. This mode requires the neighbor pw-type to be vlan
and contain the service-delimiting VLAN which will be stacked up top into the frame
along with the ingressed access VLANs.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vpn text
qinq
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a Selective Encapsulation VPN QinQ mode.
# config
(config)# mpls l2vpn
(config-l2vpn)# vpws-group Washington
(config-vpws-group-Washington)# vpn Seattle
(config-vpn-Seattle)# qinq
(config-vpn-Seattle)# access-interface gigabit-ethernet-1/1/1
(config-access-port-gigabit-ethernet-1/1/1)# encapsulation dot1q 5,10-15,20
(config-access-port-gigabit-ethernet-1/1/1)# commit
N/A
Hardware restrictions
N/A
Description
Displays the L2VPN counters values since the last clear mpls l2vpn counters command.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vpws-group name
Description: Use Group name to filter the Virtual Private Wire Services (VPWS)
groups.
vpls-group name
Description: Use Group name to filter the Virtual Private LAN Services (VPLS)
groups.
vpn-name name
access-interface name
Output Terms
Output Description
Sent Display the number of packets sent by the L2VPN access interface.
Output Description
Sent Display the number of packets sent by the L2VPN uplink interface.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To displays the L2VPN counters values since the last clear mpls l2vpn counters command
the following command can be used:
Example:
It is possible to filter the results by VPWS Group and VPN Name.
# show mpls l2vpn counters vpls-group Texas vpn-name Houston access-interface service-port-1
VPLS-Group: Texas, VPN-Name: Houston, State: created
Segment-1: bridge-domain, Status: up
service-port-1, State: created
Statistics:
Packets: Received: 42, Sent: 42
Segment-2: Virtual Forwarding Instance, Status: up
200.200.200.2, Pw-ID: 101, State: created
Statistics:
Packets: Received: 42, Sent: 42
# show mpls l2vpn counters vpls-group Texas vpn-name Houston access-interface gigabit-ethernet-1/1/5
VPLS-Group: Texas, VPN-Name: Houston, State: created
Segment-1: bridge-domain, Status: up
gigabit-ethernet-1/1/5, State: created
Statistics:
Packets: Received: 42, Sent: 42
Segment-2: Virtual Forwarding Instance, Status: up
200.200.200.2, Pw-ID: 101, State: created
Statistics:
Packets: Received: 42, Sent: 42
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vpws-group name
vpn-name name
vpn-state state
seg1-id gigabit-ethernet
Value: gigabit/ten-gigabit-ethernet
seg1-state state
seg2-id ipv4-prefix
Value: a.b.c.d
local-label label
remote-label label
seg2-state state
pw-id id
Value: pw id
pw-type type
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of MPLS L2VPN installed on data plane the following command
can be used:
Example:
It is possible to filter the results by VPWS Group, VPN Name, VPN State, Segment-1 Id,
Access State, Segment-2 Id, Pw-ID, Local Label, Remote Label and Neighbor State.
Filter by Pw-ID:
Example:
Filter by Pw-Type:
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
show mpls l2vpn vpls-group [ brief | detail ] [ vpls-group name | vpn-name name
]
Parameters
brief
Value: N/A
detail
Description: Shows detailed information about the L2VPN (VPLS) control plane.
Value: N/A
vpls-group name
vpn-name name
Output Terms
Output Description
Displays the MPLS access interface status associated with that entry.
up: The interface is ready to pass packets.
Segment-1 State
down: The interface is admin down and deprogrammed.
Status Displays the MPLS VPN status associated with that entry.
Output Description
Displays the VPLS bridge-domain Dot1q VLAN Id that is set for the
Dot1q
VPN’s bridge-domain.
Encapsulation Displays the set of C-VLANs that are encapsulated on the VPLS ac-
Dot1q cess interface.
MPLS VC labels Displays the exchanged labels information for VPLS service.
Remote access
interface state Displays the neighbor access interface operational state.
Up Time Displays the total time that the PW has been Up and running.
Output Description
VPLS-Group Displays the VPLS group name associated with that entry.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of MPLS L2VPN present on control plane the following command
can be used:
Example:
- - 200.200.20.20 20 dow
- - 200.200.200.123 123 dow
---------- ---------- ------ ------------------------------- ----- --------------- ---------- ---
To simply show the detailed list of MPLS L2VPN present on control plane the following
command can be used:
It is possible to filter the results by VPLS Group or VPN Name.
Example:
Bridge-MTU: 1555
Dot1q: 92
AC: forty-gigabit-ethernet-1/1/1.92; Admin status: down; Oper state: down;
MTU: 1555;
AC: forty-gigabit-ethernet-1/1/2.92; Admin status: up; Oper state: up;
MTU: 1555;
AC: lag-1.92; Admin status: up; Oper state: up;
MTU: 1555;
VFI: Admin status: up; Oper state: up;
Pw-type: vlan 4000;
Signalling protocol: ldp;
PW: Neighbor address: 200.200.200.2; Admin status: up; Oper state: up;
Up time: 0 days 0 hours 0 minutes 24 seconds;
Last state change time: Wed Sep 12 13:13:44 2018;
Pw-ID: 92; Pw-MTU: 1555; Tunnel interface: ldp;
FAT: Flow-label receive: true; Flow-label transmit: false;
Split-horizon: enabled;
Remote access interface state: up;
MPLS VC labels: Local: 18; Remote: 18;
MTU: Local: 1555; Remote: 1555;
PW: Neighbor address: 200.200.200.4; Admin status: up; Oper state: up;
Up time: 0 days 0 hours 0 minutes 24 seconds;
Last state change time: Wed Sep 12 13:13:44 2018;
Pw-ID: 91; Pw-MTU: 1999; Tunnel interface: ldp;
FAT: Flow-label receive: false; Flow-label transmit: true;
Split-horizon: enabled;
Remote access interface state: up;
MPLS VC labels: Local: 33; Remote: 16;
MTU: Local: 1999; Remote: 1999;
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
show mpls l2vpn vpws-group brief [ group-name | vpn-name name ] detail [ group-
name | vpn-name name ]
Parameters
brief
group-name
vpn-name name
detail
group-name
vpn-name name
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show the list of MPLS L2VPN present on control plane the following command
can be used:
Example:
To simply show the detailed list of MPLS L2VPN present on control plane the following
command can be used:
Example:
N/A
Hardware restrictions
N/A
L3VPN
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
vrf vrf-name
Output Terms
Output Description
Output Description
Display the MPLS action performed on data plane by the L3VPN entry.
none: no action associated with entry.
In Label Display the incoming label associated with the L3VPN entry.
Out Label Display the outgoing label associated with the L3VPN entry.
Display the outgoing interface for the MPLS traffic associated with
Out Interface the L3VPN entry. The outgoing interface could be an access VRF or
the uplink tunnel.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
To simply show MPLS L3VPN information, the following command can be used:
Example:
Filter by VRF:
Example:
N/A
Hardware restrictions
N/A
RSVP
interface tunnel-te
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
interface tunnel-te id
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure an MPLS Traffic Engineering Tunnel interface.
# config
(config)# interface tunnel-te 1
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
description text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
destination addr
Value: a.b.c.d.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
name text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
A tunnel interface can have six path options associated with different priorities. The
path option with a lower priority value is tried first. If this path is unavailable in the CSPF
database, the next path option with lower priority value is tried.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
path-option prio
Value: 1-255.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
path-option prio
Value: 1-255.
status
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to disable and enable a specific tunnel interface path-option.
# config
(config)# interface tunnel-te 1
(config-tunnel-te-1)# path-option 1 disable
(config-tunnel-te-1)# commit
(config-tunnel-te-1)# path-option 1 enable
(config-tunnel-te-1)# commit
N/A
Hardware restrictions
N/A
Description
Set of attributes that are associated with the dynamic path-option. The CSPF uses these
attributes information on the tunnel ingress to determine whether the path can be es-
tablished for a specific destination or not.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface tunnel-te id
Value: 1-65535.
path-option prio
Value: 1-255.
Description: Specifies the attributes that are associated with a dynamic path-
option. The attribute-set must be created in the mpls traffic-eng
configuration.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
mpls rsvp
Description
Enable Resource Reservation Protocol (RSVP) that provides traffic management capabil-
ities.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
mpls rsvp
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls rsvp
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls rsvp
Value: N/A
interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
mpls traffic-eng
Description
Enable MPLS traffic engineering that ensures Quality of Service (QoS) for data transmis-
sion.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
mpls traffic-eng
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Affinity flags attribute configured to define a path option. The path will be valid if any
link to a destination does not have any affinity-flag bits in the CSPF calculation base.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the path option attribute-set to exclude any affinity-
flag bits.
# config
(config)# mpls traffic-eng
(config-traffic-eng)# attribute-set
(config-attribute-set)# path-option Seattle
(config-path-option-Seattle)# affinity-flags exclude-any 0xa
(config-path-option-Seattle)# commit
A path can have different affinity statements associated at the same time.
Hardware restrictions
N/A
Description
Affinity flags attribute configured to define a path option. The path will be valid if each
link to a destination has the same affinity-flag bits in the CSPF calculation base.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the path option attribute-set to include all affinity-
flag bits.
# config
(config)# mpls traffic-eng
(config-traffic-eng)# attribute-set
(config-attribute-set)# path-option Seattle
(config-path-option-Seattle)# affinity-flags include-all 0xa
(config-path-option-Seattle)# commit
A path can have different affinity statements associated at the same time.
Hardware restrictions
N/A
Description
Affinity flags attribute configured to define a path option. The path will be valid if all links
to a destination have at least one affinity-flag bit in the CSPF calculation base.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the path option attribute-set to include any affinity-
flag bits.
# config
(config)# mpls traffic-eng
(config-traffic-eng)# attribute-set
(config-attribute-set)# path-option Seattle
(config-path-option-Seattle)# affinity-flags include-any 0xa
(config-path-option-Seattle)# commit
A path can have different affinity statements associated at the same time.
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable MPLS traffic engineering capabilities in an L3 in-
terface.
# config
(config)# mpls traffic-eng
(config-traffic-eng)# attribute-set
(config-attribute-set)# interface l3-vlan1
(config-interface-l3-vlan1)# commit
N/A
Hardware restrictions
N/A
Description
Enable affinity-flag bits in a specific L3 interface. The IGP advertises the affinity-flag to
devices in the same IGP area. Then the CSPF on the ingress uses this information to
determine whether a link can be used to establish an RSVP-TE path or not.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
interface interface-name
affinity-flags flag
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable MPLS traffic engineering capabilities in an L3 in-
terface.
# config
(config)# mpls traffic-eng
(config-traffic-eng)# attribute-set
(config-attribute-set)# interface l3-vlan1
(config-interface-l3-vlan1)# affinity-flags 0xa
(config-interface-l3-vlan1)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mpls traffic-eng
Value: N/A
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
LDP
This topic describes the commands related to management of Label Distribution Protocol
such as commands to configure LDP parameters or to inspect the protocol status.
Description
Configures a LSR-ID that uniquely identifies the label switch router (LSR) within the net-
work and enables MPLS LDP in the device. This configuration is mandatory to enable LDP
in the device.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
The loopback interface to be used as an LDP LSR identifier must be previously created.
In addition, it must be configured with an IPv4 address and a /32 netmask.
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
interface-name
Description: Specifies the L3 interfaces for LDP basic discovery. The L3 in-
terfaces must be created.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable LDP basic discovery on the interface.
# config
(config)# mpls ldp lsr-id loopback-1 interface l3-vlan1
(config-interface-l3-vlan1)# commit
The l3 interface to be used for LDP basic discovery must be previously created. In addi-
tion, it must be configured with an IPv4 address.
Hardware restrictions
N/A
Description
Configures the Hello hold timer for this LDP Basic Discovery.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
interface-name
Description: Specifies the L3 interfaces for LDP basic discovery. The L3 in-
terfaces must be created.
hello-holdtime
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the LDP interface Hello holdtime.
# config
(config)# mpls ldp lsr-id loopback-1
(config-lsr-id-loopback-1)# interface l3-vlan1
(config-interface-l3-vlan1)# hello-holdtime 20
(config-interface-l3-vlan1)# commit
N/A
Hardware restrictions
N/A
Description
Configures the Keep alive hold timer for this LDP Basic Discovery.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
interface-name
Description: Specifies the L3 interfaces for LDP basic discovery. The L3 in-
terfaces must be created.
keep-alive-holdtime
Description: Keep alive hold timer for the LDP Basic Discovery.
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the LDP interface Keep alive holdtime.
# config
(config)# mpls ldp lsr-id loopback-1
(config-lsr-id-loopback-1)# interface l3-vlan1
(config-interface-l3-vlan1)# keep-alive-holdtime 50
(config-interface-l3-vlan1)# commit
N/A
Hardware restrictions
N/A
Description
Enables LDP extended discovery with the specified internetwork layer address.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
address
Description: The internetwork layer address used for the extended discov-
ery.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable LDP extended discovery with the specified inter-
network layer address.
# config
(config)# mpls ldp lsr-id loopback-1 neighbor targeted 9.9.9.9
(config-neighbor-9.9.9.9)# commit
N/A
Hardware restrictions
N/A
Description
Configures the Hello hold timer for this LDP Extended Discovery.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
address
Description: The value of the internetwork layer address used for the Ex-
tended Discovery.
hello-holdtime
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the Keep alive hold timer for this LDP Extended Discovery.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
address
Description: The value of the internetwork layer address used for the Ex-
tended Discovery.
keep-alive-holdtime
Description: Keep alive hold timer for the LDP Extended Discovery.
Value: 1-65535.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
loopback-name
Description: Specifies a loopback interface for the label switching router. The
loopback interface must be created.
address
Description: The value of the internetwork layer address used for the Ex-
tended Discovery.
password pwd
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows the configuration of a neighbor password using an already encrypted
password.
# config
(config)# mpls ldp lsr-id loopback-1
(config-lsr-id-loopback-1)# neighbor targeted 9.9.9.9
This example shows the configuration of a neighbor password using special characters
(i.e: " " , “?” , “!” , “;”). Please note that it is necessary to use double quotation marks
in this case.
# config
(config)# mpls ldp lsr-id loopback-1
(config-lsr-id-loopback-1)# neighbor targeted 9.9.9.9
(config-neighbor-50.50.50.1)# password "pwd?test:2"
(config-neighbor-50.50.50.1)# commit
Password must be enclosed in double quotation marks if special characters were used
(i.e: " " , “?” , “!” , “;”). Note that in an established LDP session if password is configured
or changed the session will be restarted.
Hardware restrictions
N/A
Description
This command shows a list of all labels present in LDP database, including non-selected
labels, marked with NS, which are not installed. (not used to forward packets).
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
prefix ipv4-prefix
Value: a.b.c.d/x
Output Terms
Output Description
ID of a downstream LSR from which a label was received for this FEC
DownStream LSR-ID
via a MPLS LDP label mapping message.
Output Description
Indicates the state of a specific FEC. Entries marked with NS are not
State
installed (not used to forward packets).
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Every label mapping received from a peer LSR is retained regardless of whether the LSR
is the active next hop for the advertised mapping or not. Only the label received from
the current next hop will be installed. This command can be executed directly via CLI.
This command requires a license to be used. Please contact the support for further in-
formation.
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
brief
Value: N/A
detail
Description: The full output of this command displays general status infor-
mation about the established LDP sessions (status, role, up-
time, remaining keepalive hold time, etc.), negotiated session
timer values, and the addresses advertised by the neighbors
through LDP Address Messages.
Value: N/A
Output Terms
Output Description
LDP-ID Indicates the label space value of the MPLS LDP neighbor.
State Indicates the adjacency state with the MPLS LDP neighbor.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
20.20.20.20
Adjacency: 20.20.20.20:0; - Basic Discovery Mechanism
Adjacency discovery hello hold time: 15s;
Local discovery hello hold time: 15s;
Negotiated discovery hello hold time: 15s;
Remaining hello hold time: 14s;
Adjacency: 20.20.20.20:0; - Extended Discovery Mechanism
Adjacency discovery hello hold time: 45s;
Local discovery hello hold time: 45s;
Negotiated discovery hello hold time: 45s;
Remaining hello hold time: 39s;
N/A
Hardware restrictions
N/A
Description
Shows information about the current control-plane configuration state of several LDP
parameters.
Supported Platforms
This command is supported only in the following platforms: DM4170, DM4270, DM4360,
DM4370, DM4380, DM4610, DM4615, DM4775, DM4770.
Syntax
Parameters
brief
Value: N/A
Output Terms
Output Description
Encapsulation mode
Indicates the MPLS LDP encapsulation mode.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
CHAPTER 8: MULTICAST
This chapter describes the commands related to management of Multicast protocols in
the DmOS CLI.
IGMP SNOOPING
This topic describes the CLI commands related to the IGMP snooping functionality. The
IGMP snooping feature allows a network switch to listen to the IGMP protocol messages
exchanged between routers and hosts, with the purpose of identifying which host ports
are interested on a specific multicast traffic, and sending that traffic only to those ports.
Description
Supported Platforms
Syntax
Parameters
instance
Value: N/A
instance-id
Value: 1-8.
interface
Value: N/A
interface-name
Description: Name of the interface that will have its statistics cleared.
instance instance-id
Value: 1-8.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
administrative-status
Value: N/A
up
Value: N/A
down
Value: N/A
Default
up.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
bridge-domain id bridge-domain-id
Value: N/A
id bridge-domain-id
Value: 1-4093.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
administrative-status
Value: N/A
up
Value: N/A
down
Value: N/A
Default
up.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
group-limit limit
Value: 0-3000.
Default
0.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
ignore
Value: N/A
igmp-v1
Value: N/A
igmp-v2
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the immediate leave on an interface. In immediate leave mode, the group
membership on an interface is immediately deleted right after receiving an IGMP Leave
message i.e. any group-specific or group-and-source queries is not sent before deleting
the entry.
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
interface interface-name
immediate-leave
Value: N/A
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the interval of time in seconds between the group-specific query messages
on an interface. The group-specific-query messages have their Max Response time set to
the value of the last member query interval. If no Reports are received after the response
time of the last query expires, the group is removed.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
last-member-query
Value: N/A
interval seconds
Value: 1-25.
Default
1.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the maximum response time on an interface. It specifies the maximum al-
lowed time which the host interface is expected to reply to an IGMP General Query mes-
sage. In addition, it is applied along with other timers to modify the group membership
interval (robustness-variable x query-interval + max-response-time).
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
interface interface-name
max-response-time seconds
Value: 1-25.
Default
10.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
mrouter
Value: N/A
always
Value: N/A
learn-queries
Value: N/A
never
Value: N/A
Default
learn-queries.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the query interval on an interface. It specifies the frequency at which the
IGMP General Query messages are sent from an interface. In addition, it is applied along
with other timers to modify the group membership interval (robustness-variable x query-
interval + max-response-time).
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
interface interface-name
query-interval seconds
Value: 125-3600.
Default
125.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures the value of robustness-variable which allows tuning for the expected packet
loss on a subnetwork. The robustness-variable modifies certain IGMP message intervals
for IGMPv2 and IGMPv3. By increasing its value, the packet loss tolerance is increased,
but the leave latency in the subnetwork is also increased.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-id
Value: 1-8.
interface interface-name
robustness-variable variable
Value: N/A
Default
2.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
interface interface-name
version version
Value: 1-3.
Default
3.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
Output Terms
Output Description
IGMP Snooping
Indicates the IGMP snooping instance.
Instance
Bridge Domain Indicates the bridge domain type and its ID.
Administrative Indicates the administrative state of the IGMP snooping instance (en-
State able/disable).
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
instance-id
Value: 1-8.
ipv4-address
Value: a.b.c.d.
interface-name
Output Terms
Output Description
Indicates the amount of time (in seconds) that the multicast group
Uptime
membership is active.
Indicates the amount of time (in seconds) for the multicast group
Expires membership to become inactive, if no other IGMP report messages
is received on the interface.
Output Description
Indicates the IP address of the last host to report that multicast group
Last Reporter
membership.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Shows which interfaces are multicast router interfaces, host interfaces, or capable of
being either of them.
Supported Platforms
Syntax
Parameters
instance-id
Value: 1-8.
interface-name
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
instance-id
Description: Filters the command output by the provided IGMP snooping in-
stance ID.
Value: 1-8.
interface-name
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
instance-id
Description: Filters the command output by the provided IGMP snooping in-
stance ID.
Value: 1-8.
Output Terms
Output Description
Indicates the number of each IGMP message type sent and received
IGMP messages
by the IGMP snooping instance.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
QOS POLICER
This topic describes the commands related to Policer and Meter such as commands to
configure CIR and PIR or to inspect bandwidth rates.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Value: 1 - 1280
interface interface-name
Description: Interface the policer instance refers to. Multiple interfaces may
be specified, and the policer bandwidth will be shared in this
case.
profile profile-name
Description: Name of the policer profile created with qos policer profile.
vlan vlan-id
Value: 1 - 4094
pcp pcp
Value: 0-7
inner-vlan vlan-id
Value: 1 - 4094
inner-pcp pcp
Value: 0-7
dscp dscp
Value: 0 - 63 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33
| af41 | af42 | af43 | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef
name instance-name
counters
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Added support for GPON interfaces and added support for filtering the
4.6
traffic by inner-VLAN and inner-pcp.
Usage Guidelines
Examples:
The following example creates one policer instance to police shared bandwidth between
two interfaces.
#config
Entering configuration mode terminal
(config)# qos policer instance 1
(policer-instance-1)# interface lag-1
(policer-instance-1)# interface ten-gigabit-ethernet-1/5/2
(policer-instance-1)# profile profile1
(policer-instance-1)# vlan 100-102,110
(policer-instance-1)# counters enabled
(policer-instance-1)# top
(config)# commit
Commit complete.
(config)#
The following example creates two policer instances to police the same interfaces but as
exclusive bandwidths instead of shared.
#config
Entering configuration mode terminal
(config)# qos policer instance 1
(policer-instance-1)# interface lag-1
(policer-instance-1)# profile profile1
(policer-instance-1)# pcp 1
(policer-instance-1)# top
(config)# qos policer instance 2
(policer-instance-2)# interface ten-gigabit-ethernet-1/5/2
(policer-instance-2)# profile profile1
(policer-instance-2)# pcp 1-3
(policer-instance-2)# counters enabled
(policer-instance-1)# top
(config)# commit
Commit complete.
(config)#
The priority of a Policer instance is determined by its matching filters. For example, an
instance with matching filter by PCP has higher priority than an instance with matching
filter by VLAN.
From higher to lower, the priority order is: inner-PCP, PCP, DSCP, inner-VLAN, VLAN.
Instances with multiple matching filters will follow the same priority order. E.g.: The
instance with matching filters VLAN 100, PCP 5 and inner-VLAN 500 has higher priority
than the instance with matching filter VLAN 100 and inner-VLAN 500. A packet with VLAN
100, PCP 5 and inner-VLAN 500 will be accounted by the first Policer instance, while a
packet with VLAN 100, PCP 0 and inner-VLAN 500 will be accounted by the second Policer.
Hardware restrictions
On DM4050, the Policer matching filters do not consider the possible packet modifica-
tions due to ACLs rules.
On DM4270, DM4775, DM4770 and DM4380 series: it is not possible to classify the
packets by VLAN when applying an Egress Policer in an interface which is an untagged
member of that VLAN.
On DM4775 and DM4770 series: policer instances cannot contain different speed inter-
faces.
Description
Create and configure a policer profile for ingress and egress Ethernet traffic policing.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mode
cir committed-rate
Value: 0 - 100,000,000
cbs committed-burst
Value: 0 - 268,435,456
eir excess-rate
Value: 0 - 100,000,000
ebs excess-burst
Value: 0 - 268,435,456
pir peak-rate
Value: 0 - 100,000,000
pbs peak-burst
Value: 0 - 268,435,456
stage
actions green
actions yellow
actions red
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
4.7 Added support for configuring action set-dscp with RFC2474 classes.
Usage Guidelines
Example:
The following example demonstrates how to create a policer profile. This policer will
make red-marked packets be dropped at ingress stage.
#config
Entering configuration mode terminal
(config)# qos policer profile pol1
(policer-profile-pol1)# mode flow
(policer-profile-pol1)# stage ingress
(policer-profile-pol1)# parameters cbs 100000
(policer-profile-pol1)# parameters cir 1000000
(policer-profile-pol1)# actions red drop
(policer-profile-pol1)# top
(config)# commit
Commit complete.
(config)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has a policer profile named foo configured with the flow mode, the
command could result in the following output:
# show qos policer
INSTANCE
ID PROFILE MODE STAGE CIR EIR PIR FORWARDED DROPPED
-----------------------------------------------------------------------
1 foo flow ingress 10000 - - 2000 100
2 foo flow ingress 10000 - - 5000 200
Note: When a counter is disabled or unsupported it is displayed as ’-’
The values presented by this command are accumulated since the last time the operator
issued a clear command.
Hardware restrictions
On DM461x, the dropped counters on the egress stage are not supported.
Description
Supported Platforms
Syntax
Parameters
N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has four policer instances, the command could result in the follow-
ing output:
N/A
Hardware restrictions
N/A
This topic describes the commands related to QoS Packet Scheduler such as commands
to configure Strict Priority or Early Discard at individual queues, and commands to set
rate limits at egress interfaces.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-identification
Value: interface-type-chassis/slot/port
Where interface-type can assume gigabit-ethernet, ten-gigabit-
ethernet, forty-gigabit-ethernet or gpon.
scheduler-profile profile-name
Value: String
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command associates a QoS Scheduler Profile to a specific interface. To set a QoS
Scheduler Profile to an interface you have to first create the QoS Scheduler Profile:
Using SP for a queue’s weight could cause starvation for other queues.
Hardware restrictions
None
qos scheduler-profile
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
profile-name
Description: The QoS Scheduler profile identifier. This value is used to dis-
tinguish the various profiles. It’s possible to create up to 500
different profiles.
Value: String
mode
queue
Value: 0-7
weight
Value: 1-100 | SP
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command is used to define a QoS Scheduler Profile. After it’s done, it’s necessary
to associate the profile to an interface in order to the QoS profile take effect over the
outgoing traffic of the interface.
Each profile can have only one scheduling mode at a time. Once the mode is set it
enables the queues’ creation and configuration. Each mode must have all its queues
created and configured with a weight. The weight represents the percentage of avail-
able bandwidth, and the sum of the weights must be 100.
The current supported scheduling mode is WFQ (Weighted Fair Queue), which balances
the egress traffic according to the weights set in its queues. The scheduling is based on
bytes.
To configure a QoS Scheduler Profile the first thing to do is to create the profile:
DM4610(config)# qos scheduler-profile testXYZ
DM4610(config-profile-testXYZ)#
Using SP for a queue’s weight could cause starvation for other queues.
To remove a profile it’s necessary to remove all interfaces assignments to the referred
profile.
So in the following scenario to remove myProfile1 we have to:
DMOS(config)# show full-configuration
qos interface gigabit-ethernet 1/1/1
scheduler-profile myProfile1
!
qos interface gigabit-ethernet 1/1/2
scheduler-profile myProfile2
!
qos scheduler-profile myProfile1
mode wfq
(...)
!
qos scheduler-profile myProfile2
mode wfq
(...)
!
DMOS(config)# qos interface gigabit-ethernet 1/1/1
DMOS(config-qos-interface-gigabit-ethernet 1/1/1)# no scheduler-profile
DMOS(config-qos-interface-gigabit-ethernet 1/1/1)# top
DMOS(config)# no qos scheduler-profile myProfile1
DMOS(config)# commit
Commit complete.
DMOS(config)#
Hardware restrictions
N/A
rate-limit
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
egress
Value: N/A
ingress
Value: N/A
bandwidth value
Value: 100-100000000
burst value
Value: 2-2000
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
This command is located inside qos node. So, to configure a rate limit into an interface
follow these steps:
Now access the rate limit configuration informing the traffic flow to be limited. Suppose
egress traffic:
DmOS(config-qos-interface-gigabit-ethernet-1/1/1)# rate-limit egress
DmOS(config-rate-limit-egress)#
Now configure the bandwidth and burst to limit the interface. Both parameters are
required. At the end of configuration, commit it:
DmOS(config-rate-limit-egress)# bandwidth 64000
DmOS(config-rate-limit-egress)# burst 1024
DmOS(config-rate-limit-egress)# commit
Commit complete.
DmOS(config-rate-limit-egress)#
N/A
Hardware restrictions
ingress rate-limit is not supported on DM4270, DM4775, DM4770 and DM4380 series.
STORM CONTROL
This topic describes the commands related to Storm Control such as commands to con-
figure multicast, broadcast and unknown unicast(DLF) rate limits.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-identification
Value: interface-type-chassis/slot/port
Where interface-type can assume gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet or lag.
broadcast percent
Value: 0.01-100.00
multicast percent
Value: 0.01-100.00
unicast percent
Value: 0.01-100.00
Default
Disabled
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
The following commands enable storm-control for ingress traffic on interface gigabit-
ethernet-1/1/1, with rate-limit of 0.5% of interface’s nominal speed for broadcast pack-
ets, 10% for unknown multicast packets and 1% for unknown unicast (DLF) packets:
Precede the command with no to disable Storm Control. The following commands disable
Storm Control multicast for interface gigabit-ethernet-1/1/1, and then disable all types of
Storm Control for the same interface:
Enabling Storm Control may result in unexpected lost of packets. You can use the com-
mand: show interface interface-identification statistics to verify possible dropped
packets.
Hardware restrictions
N/A
BASIC ACLS
This topic describes the commands related to management of ACLs such as commands
to configure match criteria or actions.
access-list acl-profile
Description
This command is used to create or enter an Access List Profile. The profile can contain
multiple ACL entries used to specify match and action criteria. ACL profiles have priorities
among them. An ACL profile must have at least one ACL entry configured. For a profile
to take effect, it needs to be applied to an interface. L2 profiles always have priority over
L3 profiles.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
stage
type
name
Value: Text
priority
Description: The ACL profile priority, being 0 the highest priority. L2 pro-
files can have priorities from 0 to 255 and L3 profiles can have
priorities from 256 to 511.
Value: 0-511
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Creating a L2 Access List Profile at ingress stage with name my_acl_profile and priority
0:
(config)# access-list
(config-acl)# acl-profile ingress l2 my_acl_profile
(config-acl-profile-l2-my_acl_profile)# priority 0
Adding an entry to the profile:
(config-acl-profile-l2-my_acl_profile)# access-list-entry 0 action deny
(config-access-list-entry-0)# match vlan 10
Apply the profile to an interface so the profile can take effect:
(config)# access-list interface gigabit-ethernet-1/1/1 ingress my_acl_profile
ACL Rules created with L2 profiles will match only pure Ethernet headers. If the Ethernet
header is encapsulated over any protocol, the rule will not apply.
ACL Rules created with L3 profiles will match only L3 packets encapsulated over Ethernet
header (i.e. if the L3 packet is encapsulated over PPPoE, or other non Ethernet L2 header,
the match will not apply).
Hardware restrictions
N/A
access-list interface
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet, gpon, cpu-port.
stage
Value: ingress
profile-name
Value: Text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Given a profile named l2-ingress-acl, the following sequence of commands will apply it
on port gigabit-ethernet-1/1/1:
(config)# access-list
(config-acl)# interface gigabit-ethernet-1/1/1 ingress l2-ingress-acl
(config-acl)# commit
You can apply the same profile to several interfaces. You can also apply more than one
profile to the same interface.
Every device has a different amount of ACL resources to be used. The resources are
consumed when the profile is applied to an interface. Please refer to the hardware
restriction section for more information about how they operate on each hardware.
Hardware restrictions
The maximum number of ACL rules will depend on the amount of entries applied to all
interfaces. DM4610 supports up to 256 entries per profile type (L2 or L3) applied to all
interfaces. For instance, when a L2 profile with 128 entries is applied to two interfaces,
no new L2 rules will be allowed to be applied.
access-list protection
Description
This command is used to apply a given ACL profile to the traffic with CPU destination.
It is aimed to allow the user to protect the CPU from malicious traffic data.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
stage
Value: cpu
profile-name
Value: Text
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
To protect the CPU, it is recommended to create an access-list with a White List that
blocks all the access to a certain TCP/UDP Destination-Port, and accept connection only
from trusted sources: Example:
#config
Entering configuration mode terminal
(config)# access-list
(config-acl)# acl-profile cpu l3 whitelist
(config-acl-profile-l3-whitelist)# priority 0
(config-acl-profile-l3-whitelist)# access-list-entry 0 action permit
(config-access-list-entry-0)# match source-ipv4-address 10.10.0.1
(config-access-list-entry-0)# exit
(config-acl-profile-l3-whitelist)# access-list-entry 1 action permit
(config-access-list-entry-0)# match source-ipv4-address 10.10.1.0/24
(config-access-list-entry-0)# exit
(config-acl-profile-l3-whitelist)# access-list-entry 100 action deny
(config-access-list-entry-0)# match destination-port ssh
(config-access-list-entry-0)# top
(config)# access-list
(config-acl)# protection cpu whitelist
(config-acl)# commit
Every device has a different amount of ACL resources to be used. The resources on cpu
stage are consumed when the profile is applied as a protection profile.
Hardware restrictions
N/A
access-list-entry
Description
Manages Access List Entries at an Access List Profile. Access list entries must contain at
least one match and one action.
Supported Platforms
Syntax
access-list-entry entry-id
access-list-entry entry-id action {deny | permit | copy pcp | set pcp pcp | set
inner-pcp pcp }
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
entry-id
Description: The ACL entry identifier. This value will be used as the relative
priority among other ACL entries from the same ACL profile,
being 0 the highest priority.
Value: 0-255
Value: xx:xx:xx:xx:xx:xx
Description: A wildcard mask for the source MAC address of a match. This
mask is sometimes referred to as an inverse mask because a 1
and 0 mean the opposite of what they mean in a subnet (net-
work) mask. Only bits corresponding to “0” are considered from
MAC. Bits with “1” are ignored.
This match is only available if a match for a source MAC address
has been configured.
Value: xx:xx:xx:xx:xx:xx
Value: xx:xx:xx:xx:xx:xx
Value: xx:xx:xx:xx:xx:xx
Value: 0-7
Value: 1-4094
Value: 0-7
Value: 1-4094
Value: 0-63 | 0 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 |
af33 | af41 | af42 | af43 | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 |
ef
Description: The IPv4 Type of Service or IPv6 Traffic Class for a match.
Remark: ToS match can not be configured with DSCP match in
the same entry.
Value: 0-255
Value: 0-255
action deny
Description: Action to deny, i.e. drop any packets matching the filter.
Value: N/A
action permit
Description: Action to permit, i.e. allow any packets that was blocked by a
deny rule.
Value: N/A
Description: Action to copy the PCP field value from inner VLAN tag of the
frame to the outer VLAN tag.
Value: N/A
Description: Action to set or replace the PCP field value of the frame with
parameter set in action.
This action also schedules the packet to a QoS scheduling queue.
Please refer to the QoS chapters for more information about the
QoS features.
Value: 0-7
Description: Action to set or replace the PCP field value of the inner VLAN
tag in frame with parameter set in action.
Value: 0-7
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Removed actions set DSCP and set queue. Added action permit. Re-
1.1
moved match interface.
5.0 Added new stage cpu, and matches source-port and ttl
Usage Guidelines
As ACL entries must be in an ACL profile, it is necessary first to create an Access List
Profile. The profile needs a stage, type, priority and name. In this case the stage is
ingress, the type is L2, the name is l2-ingress-acl and the priority 0:
(config)# access-list acl-profile ingress l2 l2-ingress-acl
(config-acl-profile-l2-l2-ingress-acl)# priority 0
Then it is possible to add matches and actions, for instance, to deny all ingress traffic
with VLAN tag 10:
(config-access-list-entry-2)# match vlan 10
(config-access-list-entry-2)# action deny
It is possible to augment this entry with more matches of type L2. For instance, adding
a match to the source MAC address with a mask will start blocking only traffic from that
VLAN with the specified set of MAC addresses.
(config-access-list-entry-2)#
match source-mac-address 00:00:00:00:00:ad
match source-mac-address-mask ff:ff:ff:ff:ff:00
In this case, the match specifies all MAC addresses that ends with the ad octet.
In the end, you must apply the profile created to an interface for the entry to take effect.
(config)# access-list
(config-acl)# interface gigabit-ethernet-1/1/1 ingress l2-ingress-acl
(config-acl)# commit
After the commit, all packets arriving on interface gigabit-ethernet-1/1/1 with a VLAN tag
of 10 and source MAC address ending in ad will be dropped.
None
Hardware restrictions
show acl-resources
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
extensive
Value: N/A
interface
Value: N/A
interface-name
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has a total of 256 entries for ingress L2 ACLs, 256 entries for ingress
L3 ACLs and 256 entries for CPU L3 ACLs, and the following configuration is applied:
DmOS# show running-config
access-list
interface gigabit-ethernet-1/1/1
ingress testL2
!
interface gigabit-ethernet-1/1/2
ingress testL2 testL3-OneEntry
!
interface gigabit-ethernet-1/1/3
ingress testL2 testL3-OneEntry testL3-ZeroEntries
!
acl-profile ingress l2 testL2
priority 0
access-list-entry 0
action permit
!
access-list-entry 1
action permit
!
!
acl-profile ingress l3 testL3-OneEntry
priority 256
access-list-entry 0
action permit
!
!
acl-profile ingress l3 testL3-ZeroEntries
priority 257
!
acl-profile cpu l3 cpuL3
priority 1
access-list-entry 0
action permit
!
access-list-entry 1
action permit
!
access-list-entry 2
action permit
!
!
Note that the testL3-ZeroEntries does not count towards Used L3 entries just because
it does not have any entry inside it.
--------------------------------------------------------------
TOTAL 3
=================================
= gigabit-ethernet-1/1/1 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
=================================
= gigabit-ethernet-1/1/2 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
ACL Ingress L3 Profile Used entries
------------------------------------------------ ------------
testL3-OneEntry 1
--------------------------------------------------------------
TOTAL 1
=================================
= gigabit-ethernet-1/1/3 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
ACL Ingress L3 Profile Used entries
------------------------------------------------ ------------
testL3-OneEntry 1
testL3-ZeroEntries 0
--------------------------------------------------------------
TOTAL 1
When it’s necessary to display only information about the interfaces, or about a specific
interface, it’s possible to use show acl-resources interface or show acl-resources
interface interface-name. These commands can also be followed by detail and exten-
sive marks:
DmOS# show acl-resources interface detail
Interface Used L2 Entries Used L3 Entries
----------------------------- --------------- ---------------
gigabit-ethernet-1/1/1 2
gigabit-ethernet-1/1/2 2 1
gigabit-ethernet-1/1/3 2 1
----------------------------- --------------- ---------------
TOTAL 6 2
DmOS# show acl-resources interface extensive
=================================
= gigabit-ethernet-1/1/1 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
=================================
= gigabit-ethernet-1/1/2 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
ACL Ingress L3 Profile Used entries
------------------------------------------------ ------------
testL3-OneEntry 1
--------------------------------------------------------------
TOTAL 1
=================================
= gigabit-ethernet-1/1/3 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
ACL Ingress L3 Profile Used entries
------------------------------------------------ ------------
testL3-OneEntry 1
testL3-ZeroEntries 0
--------------------------------------------------------------
TOTAL 1
DmOS# show acl-resources interface gigabit-ethernet-1/1/1 detail
Interface Used L2 Entries Used L3 Entries
----------------------------- --------------- ---------------
gigabit-ethernet-1/1/1 2
DmOS# show acl-resources interface gigabit-ethernet-1/1/1 extensive
=================================
= gigabit-ethernet-1/1/1 =
=================================
ACL Ingress L2 Profile Used entries
------------------------------------------------ ------------
testL2 2
--------------------------------------------------------------
TOTAL 2
N/A
Hardware restrictions
AAA
aaa authentication-next-method-on-fail
Description
Command to instruct AAA to use the next authentication method defined in the authen-
tication order list, even when the current method returns a FAIL response. By default,
AAA proceeds to the next authentication method only when there is an ERROR, which
means that the security server has not responded to an authentication query. Because
of this, no authentication has been attempted. A FAIL response means that the user has
not met the criteria contained in the security server authentication database to be suc-
cessfully authenticated. In order to force local user authentication in this situation, for
example, authentication-next-method-on-fail must be enabled and local authentication
must be present in the authentication order list.
Supported Platforms
Syntax
aaa authentication-next-method-on-fail
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
DM4160# config
Entering configuration mode terminal
DM4610(config)# aaa authentication-next-method-on-fail
For local authentication, the next method is always tried on failure. But it is not recom-
mended to use local before other methods on the authentication order list.
Hardware restrictions
N/A
aaa authentication-order
Description
Command to set user authentication Order. The order must be set using brackets and
separated by spaces.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
local
Value: N/A.
radius
Value: N/A.
tacacs
Value: N/A.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
2.4 Added note for local authentication when the user is not present.
Usage Guidelines
After configuring the remote servers, authentication order must be set to determine in
which order users will be authenticated. Using brackets allows user to replace older con-
figurations.
DM4160# config
Entering configuration mode terminal
DM4610(config)# aaa authentication-order [ local radius tacacs ]
For local authentication when the user is not present the next authentication method will
be attempted. For radius or tacacs the next method is used only if there is no connection
to the server.
Hardware restrictions
N/A
aaa authentication-type
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
tacacs
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
To authenticate users using TACACS the correct authentication type must be selected.
The selected authentication type will be applied to all TACACS servers.
DM4160# config
Entering configuration mode terminal
DM4610(config)# aaa authentication-type tacacs ascii
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
aaa server radius server name host IPv4address shared-secret secret [ authen-
tication ] [ accounting ] [ retries number of retries ] [ authentication-port port
number ] [ accounting-port port number ] [ source { ipv4 address IPv4address |
interface interface-name } ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
server name
host IPv4address
Value: a.b.c.d
shared-secret secret
Description: Configures a secret that is shared with the server and used to
validate the transaction.
authentication
Value: N/A
accounting
Value: N/A
Value: 1-5
Default Value: 3
Value: 0-65535
Value: 0-65535
Description: Specifies the source IPv4 address from which Radius server con-
nection will be established.
Value: a.b.c.d
Description: Specifies the interface whose IP address will be used for all out-
going RADIUS packets. Interface must have an IPv4 address
configured and cannot be associated with a VRF.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
DM4160# config
Entering configuration mode terminal
DM4610(config)# aaa server radius rad01
DM4610(config-radius-rad01)# host 10.1.1.1
DM4610(config-radius-rad01)# shared-secret dmos-radius
DM4610(config-radius-rad01)# authentication
DM4610(config-radius-rad01)# accounting
Example: This example shows how to configure an IPv4 source address for a remote
Radius server.
DM4160# config
Entering configuration mode terminal
DM4610(config)# aaa server radius rad01
DM4610(config-radius-rad01)# source ipv4 address 1.1.1.1
If the IPv4 source address parameter is not a configured IPv4 address of any interface,
the Radius requests will not be sent to the server.
Hardware restrictions
None
Description
Supported Platforms
Syntax
aaa server tacacs server name host IPv4address shared-secret secret [ authenti-
cation ] [ authorization ] [ accounting ] [ timeout timeout time ] [ authentication-
port port number ] [ authentication-type type ] [ source { ipv4 address IPv4address
| interface interface-name } ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
server name
host IPv4address
Value: a.b.c.d
shared-secret secret
Description: Configures a secret that is shared with the server and used to
validate the transaction.
authentication
Value: N/A
authorization
Value: N/A
accounting
Value: N/A
Value: 0-255
Default Value: 5
Value: 0-65535
authentication-type type
Description: Specifies the source IPv4 address from which TACACS+ server
connection will be established.
Value: a.b.c.d
Description: Specifies the interface whose IP address will be used for all out-
going TACACS+ packets. In the case a loopback interface is
selected, it cannot be associated with a VRF.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The remote servers must be previously configured before enabling the remote authenti-
cation on the equipment.
The system supports up to 5 TACACS+ servers, that means 4 redundant servers. Once a
server is reached for authorization, this server will be preferred for the command autho-
rization until it is unreachable. If this server becomes unreachable the list of servers will
be inspected to return the next available server for authorization.
When there is a TACACS+ server with authentication and without authorization config-
ured, the authorization level will be performed by user group. This group is mapped from
the user privilege level present in the TACACS+ server used for authentication.
Example: This example shows how to set a remote TACACS+ server for authentica-
tion, authorization and accounting services.
# config
Entering configuration mode terminal
(config)# aaa server tacacs tac01
(config-tacacs-tac01)# host 10.1.1.1
(config-tacacs-tac01)# shared-secret dmos-tacacs
(config-tacacs-tac01)# authentication
(config-tacacs-tac01)# authorization
(config-tacacs-tac01)# accounting
(config-tacacs-tac01)# commit
Example: This example shows how to use insert to add new server with the desired
priority.
Example: This example shows how to use move to change the server priority.
(config)# commit
Commit complete.
(config)# show aaa server
aaa server tacacs tac3
host 3.3.3.3
shared-secret $7$oSm7YUa2o6c+secJrARZhQ==
!
aaa server tacacs tac2
host 2.2.2.2
shared-secret $7$IVkBhwucZ66bhXM+00Vzzw==
!
aaa server tacacs tac1
host 1.1.1.1
shared-secret $7$kkfWsrXallbrgAQDad3S7w==
!
It is not recommended the configuration of the same user on both local host and remote
authentication server when the group permission is different. Otherwise, the user au-
thentication will be done and its privilege level will follow the higher permission.
Currently, commands authorization and accounting via NETCONF are not supported.
However, the authorization and accounting level will be performed by user group. This
group is based on the user privilege level present in the TACACS+ server used for au-
thentication. A privilege level of 15 is mapped to the admin group, otherwise the user is
mapped to the audit group.
Hardware restrictions
N/A
aaa user
Description
The AAA user command is used to create local users to access the device.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
username
new password
old password
confirm password
password password
group group
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Users with admin access can change any user password and every user can change it’s
own password.
DM4610# config
Entering configuration mode terminal
DM4610(config)# aaa user audit password audit group audit
Login via serial has a 128 characters limitation to username and password.
Hardware restrictions
N/A
id
Description
Command to show authenticated user and groups as well as user privilege level
Supported Platforms
Syntax
id
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
DM4160# id
user = admin(0), gid=0, groups=admin
N/A
Hardware restrictions
N/A
who
Description
Supported Platforms
Syntax
who
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
DM4160# who
Session User Context From Proto Date Mode
*12 admin cli 127.0.0.1 console 00:03:05 operational
N/A
Hardware restrictions
N/A
PORT SECURITY
anti-ip-spoofing
Description
ARP packets;
PPP connections;
TLS connections;
ARP packets;
Supported Platforms
Syntax
anti-ip-spoofing
interface interface-name-chassis/slot/port or id
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
allowed-ip
Value: None.
all
Value: None.
ipv4-all
Description: Inform that all IPv4 addresses in any VLAN will be permitted by
device.
Value: None.
ipv6-all
Description: Inform that all IPv6 addresses in any VLAN will be permitted by
device.
Value: None.
vlan vid
Value: 1-4094
mac mac-address
Description: Source MAC address of the client that will be permitted by de-
vice.
Value: XX:XX:XX:XX:XX:XX
Default
None.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Please note that all allowed-ip rules of this interface will be removed too.
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#no interface gigabit-ethernet-1/1/1
(config-ip-spoofing)#commit
To allow all IPv4 addresses in any VLAN on a gigabit interface, the following command
must be issued:
Please note that all allowed-ip rules for IPv4 addresses on this interface will be removed
too and that all IPv6 addresses will be blocked.
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#interface gigabit-ethernet-1/1/1
(config-ip-spoofing-gigabit-ethernet-1/1/1)#allowed-ip ipv4-all
(config-ip-spoofing-gigabit-ethernet-1/1/1)#commit
To allow the client with IPv4 address 10.0.0.1, using VLAN id 10 on the service-port 1, to
have the traffic pemitted, the following command must be issued:
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#interface service-port-1
(config-ip-spoofing-service-port-1)#allowed-ip ipv4 address
10.0.0.1 vlan 10
(config-ip-spoofing-service-port-1)#commit
To allow the traffic from client with IP address 10.0.0.1 and MAC address F0:7D:00:00:00:01,
using VLAN id 10 on the service-port 1, the following command must be issued:
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing-service-port-1)#allowed-ip ipv4 address
10.0.0.1 vlan 10 mac F0:7D:00:00:00:01
(config-ip-spoofing-service-port-1)#commit
To allow the client with any IPv4 address on the service-port 2, to have the traffic pemit-
ted, the following command must be issued:
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#interface service-port-2
(config-ip-spoofing-service-port-2)#allowed-ip ipv4-all
(config-ip-spoofing-service-port-2)#commit
To allow the traffic from client with any IPv6 address on the service-port 1, the following
command must be issued:
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#interface service-port-1
(config-ip-spoofing-service-port-2)#allowed-ip ipv6-all
(config-ip-spoofing-service-port-2)#commit
To allow the client with any IP address on the service-port 1, to have the traffic pemitted,
the following command must be issued:
(config)#
(config)#anti-ip-spoofing
(config-ip-spoofing)#interface service-port-1
(config-ip-spoofing-service-port-2)#allowed-ip all
(config-ip-spoofing-service-port-2)#commit
To check if the configuration was applied, issue the show running-config command:
#show running-config
anti-ip-spoofing
interface service-port-1
allowed-ip ipv4 10.0.0.1 vlan 10
!
interface service-port-2
allowed-ip all
!
!
Clients that use static IP address configuration shall have an allowed-ip configuration,
otherwise its traffic won’t pass through the device.
An interface with anti-ip-spoofing enabled will drop any IP traffic, will just allow ARP
packets and traffic with IP addresses configured by allowed-ip or received by DHCP con-
nections.
TLS and PPP traffic will not be affected by anti-ip-spoofing configuration.
For (ten-)gigabit-ethernet intefaces with anti-ip-spoofing enabled, just ARP packets and
traffic with IP addresses configured by allowed-ip will be accepted.
Anti-ip-spoofing should not be enabled for interfaces being used as Uplink interfaces, it
was designed to be used in access-like interfaces.
The misuse of anti-ip-spoofing feature with uplink-like interfaces can stop all traffic on
it.
Allowed-ip configuration will not work with service-ports without match and action con-
figuration (VLAN translate).
Hardware restrictions
For DM46xx family, the maximum number of allowed IP addresses is 1024. However,
this limit is shared with DHCP entries. It means that equipment will be limited to 1024
connections (Static plus DHCP assigned addresses).
show allowed-ip
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mac mac-address
vlan vlan-id
address ip-address
interface interface-name-chassis/slot/port
entry-type type
status entry-status
Output Terms
Output Description
VLAN Display the VLAN ids associated with the allowed IP entries.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
History
Release Modification
Usage Guidelines
To simply show the list of all allowed IP entries the following command can be used:
#show allowed-ip
It is possible to filter the results by MAC address, IP address, VLAN id, interface, entry
type and status.
Filter by MAC:
#show allowed-ip mac 44:55:33:22:11:00
Filter by IP:
#show allowed-ip address 10.0.0.1
Filter by Interface:
#show allowed-ip interface gigabit-ethernet-1/1/1
Filter by VLAN:
Filter by Status:
#show allowed-ip status active
N/A
Hardware restrictions
N/A
This topic describes the commands related to management of fault detection using CFM
or Y.1731 such as commands to configure and inspect Maintenance End Points (MEPs),
CCM rates or to execute on-demand Ethernet link trace.
Description
Supported Platforms
Syntax
oam cfm delay-measurement probe id session id [count value] [pcp value] [interval
value] [size value]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
probe id
Value: 1 - 512
interval minutes
Value: 1 - 1440
Default Value: 1
md id
ma id
mep id
Value: 1 - 8191
remote-mep id
Value: 1 - 8191
session id
Value: 1-8
count value
Value: 1 - 1024
Default Value: 10
pcp value
Description: PCP (priority code point) value used in the 802.1Q VLAN tag.
Value: 0-7
interval value
Default Value: 1s
size value
Value: 64 - 9000
Default Value: 64
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Considering the following scenario, with local MEP 11 and remote MEP 12:
# config
(config)# dot1q vlan 10,20,30
(config-vlan-10,20,30)# interface gigabit-ethernet-1/1/2
(config-dot1q-interface-gigabit-ethernet-1/1/2)# top
(config)# oam
(oam)# cfm
(cfm)# md CFM_MD
(cfm-md-CFM_MD)# level 3
(cfm-md-CFM_MD)# ma CFM_MA
(cfm-ma-CFM_MA)# ccm-interval 1s
(cfm-ma-CFM_MA)# remote-meps 12
(cfm-ma-CFM_MA)# vlan-list 10,20,30
(cfm-ma-CFM_MA)# primary-vlan-id 20
(cfm-ma-CFM_MA)# mep 10
(cfm-mep-11)# interface gigabit-ethernet-1/1/2
(cfm-mep-11)# direction up
(cfm-mep-11)# primary-vlan-id 10
(cfm-mep-11)# commit
In this example, local MEP 11 will run two delay-measurement sessions to remote MEP
12 every 20 minutes. The first session sends 5 frames with 128 bytes every second to
monitor PCP 3, which is tipycally used for voice applications:
(config)# oam cfm delay-measurement probe 1 md CFM_MD ma CFM_MA mep 11
remote-mep 12 interval 20
(cfm-dm-probe-1)# session 1 interval 1s count 5 size 128 pcp 3
A second session is used to monitor PCP 1, which usually has the lowest network priority,
and will use a different interval and packet size:
(cfm-dm-probe-2)# session 2 interval 10s count 15 size 512 pcp 1
To see the consolidated statistics of session 1, run the following command:
# show oam cfm delay-measurement probe 1 session 1
LAST LAST LAST ALL ALL ALL
AVG AVG LOSS LAST PCP AVG AVG LOSS ALL PCP
DELAY JITTER RATIO MISMATCH DELAY JITTER RATIO MISMATCH
SESSION PCP (us) (us) % RATIO % (us) (us) % RATIO %
------------------------------------------------------------------------------
1 3 4493 784 0 0 4493 784 0 0
N/A
Hardware restrictions
N/A
cfm ma
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
md id
ma id
ccm-interval interval
primary-vlan-id vlan-id
Value: 1 - 4094
vlan-list vlan-ids
Value: 1 - 4094
remote-meps mep-ids
Description: Configure the remote MEPs in the MA. Ranges of MEP IDs or
single MEP ID are allowed and can be combined to specify the
remote MEP list.
Example: remote-meps 1-3,5,7-9
Value: 1 - 8191
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
One-line like command is also supported. The example below shows the creation of
another MA.
# config
(config)# dot1q vlan 10
(config-vlan-10)# top
(config)# oam cfm md CFM_MD level 1 ma CFM_MA2 ccm-interval 10s
vlan-list 10 primary-vlan-id 10 remote-meps 2-10
(cfm-ma-CFM_MA2)# commit
Commit complete.
(cfm-ma-CFM_MA2)# end
#
The VLANs in the VLAN list monitored by the MA need to be configured in the equip-
ment for the configuration to be committed successfully.
Hardware restrictions
N/A
cfm ma ais
Description
Configure transmission and reception of Alarm Indication Signal (AIS) frames for a given
Maintenance Association (MA).
When transmission is enabled, AIS frames are transmitted when a fault is detected, re-
gardless of any alarm configuration and report.
When AIS alarm suppression is enabled, alarms are not reported if AIS frames are re-
ceived.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
md id
ma id
Description: Destination MD level of the sent AIS packets. The target level
must be greater than the MD level where the AIS is configured.
Value: 1-7
Default Value: 1s
Description: PCP (802.1p priority) to be used on VLAN Tags for AIS packets.
Value: 0-7
Default Value: 7
Description: List of inner VLANs (second VLAN TAGs) which the AIS must be
sent with. A copy of the packet is sent with each inner VLAN.
The outer VLAN is the MEP’s primary-vlan.
Leave it blank when an inner VLAN is unnecessary.
VLAN ranges or single VLANs are allowed and can be combined.
Value: 1 - 4094
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
To configure AIS transmission it is necessary to create a valid MA and configure all pa-
rameters of AIS transmission. AIS reception takes the alarm-suppression parameter only.
Transmission and reception can be configured independently.
# config
(config)# dot1q vlan 10,20,30
(config-vlan-10,20,30)# top
(config)# oam
(oam)# cfm
(cfm)# md CFM_MD
(cfm-md-CFM_MD)# level 1
(cfm-md-CFM_MD)# ma CFM_MA1
(cfm-ma-CFM_MA1)# ccm-interval 1s
(cfm-ma-CFM_MA1)# vlan-list 10,20,30
(cfm-ma-CFM_MA1)# primary-vlan-id 20
(cfm-ma-CFM_MA1)#ais transmission
(cfm-ais-tx)# level 3
(cfm-ais-tx)# interval 1min
(cfm-ais-tx)# vlan-list 10
(cfm-ais-tx)# vlan-priority 1
(cfm-ais-rx)# ais reception
(cfm-ais-rx)# alarm-suppression
(cfm-ma-CFM_MA1)# remote-meps 10-15
(cfm-ma-CFM_MA1)# commit
Commit complete.
(cfm-ma-CFM_MA1)# end
#
N/A
Hardware restrictions
N/A
cfm md
Description
Enables Connectivity Fault Management (CFM) and create a Maintenance Domain (MD).
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
md id
level md-level
Value: 0-7
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
One-line like command is also supported. The example below shows the creation of
another MD.
# config
(config)# oam cfm md CFM_MD2 level 6
(cfm-md-CFM_MD2)# commit
Commit complete.
(cfm-md-CFM_MD2)# end
#
N/A
Hardware restrictions
N/A
cfm mep
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
md id
ma id
mep id
Value: 1 - 8191
interface interface-name
direction direction
Description: Set the direction in which the MEP faces on the interface.
Value: { up | down }
primary-vlan-id vlan-id
Value: 1 - 4094
inner-vlan-id vlan-id
Description: Specify the inner VLAN ID (second tag) for this MEP.
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
One-line like command is also supported. The example below shows the creation of
another MEP.
# config
(config)# dot1q vlan 1 interface gigabit-ethernet-1/1/10
(config-dot1q-interface-gigabit-ethernet-1/1/10)# top
(config)# oam cfm md CFM_MD level 3 ma CFM_MA ccm-interval 1s
vlan-list 1 primary-vlan-id 1 mep 2 interface gigabit-ethernet-1/1/10
direction down primary-vlan-id 1
(cfm-mep-2)# commit
Commit complete.
(cfm-mep-2)# end
#
The MEP is part of an MA and a valid MA configuration is required for the configuration
to be committed successfully.
The primary VLAN ID must be present in the parent MA’s VLAN list.
MEPs configured with direction down do not respect VLAN Mapping rules.
Hardware restrictions
N/A
Description
Configure the Continuity Check Messages (CCM) generation, fault detection and fault
notification.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
md id
ma id
mep id
Value: 1 - 8191
cci-enabled
Value: N/A
lowest-fault-priority-defect fault-type
Description: Set the lowest priority defect that is allowed to generate a Fault
Alarm.
fault-alarm-time time
Description: Set the time (in milliseconds) before a Fault Alarm is issued
(100ms step).
fault-reset-time time
Description: Set the time (in milliseconds) before resetting a Fault Alarm
(100ms step).
fault-action action
Description: Set the action when this MEP enters in fail state, as controlled
by the Continuity Check lowest-fault-priority-defect configura-
tion.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
(cfm-mep-1-cci)# end
#
One-line like command is also supported. The example below shows the configuration in
another MEP.
# config
(config)# dot1q vlan 50 interface gigabit-ethernet-1/1/1
(config-dot1q-interface-gigabit-ethernet-1/1/1)# top
(config)# oam cfm md CFM_MD level 0 ma CFM_MA ccm-interval 1s
vlan-list 50 primary-vlan-id 50 mep 2 interface gigabit-ethernet-1/1/4
direction down primary-vlan-id 50 continuity-check cci-enabled
(cfm-mep-2-cci)# commit
Commit complete.
(cfm-mep-2-cci)# end
#
Fault Alarm is priority based, so a given value will enable all the values below it:
remote-rdi - Enable fault alarm notification for all errors
remote-mac-error - Enable fault alarm notification for remote MEPs with Port Status or
Interface Status failure and all errors below
remove-invalid-ccm - Enable fault alarm notification for remote MEPs without connec-
tivity or remote MEP FSM receiving invalid CCMs and all errors below
invalid-ccm - Enable fault alarm notification for reception of invalid CCMs and cross-
connection CCMs
cross-connect-ccm - Enable fault alarm notification only for reception of cross-connection
CCMs
CCMs generation is part of MEP and a valid MEP configuration is required for the con-
figuration to be committed successfully.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
clear oam cfm statistics [md md-id] [ma ma-id] [mep mep-id]
Parameters
md md-id
Value: N/A
ma ma-id
Value: N/A
mep mep-id
Value: N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
None
Hardware restrictions
None
delay-measurement
Description
Trigger a delay-measurement session from a local MEP to a remote MEP in order to collect
network statistics such as delay and jitter.
Supported Platforms
Syntax
Parameters
md id
ma id
mep id
Description: Local MEP ID. Only an already created local MEP is accepted.
Value: 1 - 8191
remote-mep id
Description: Remote MEP ID. Only an already created remote MEP is ac-
cepted.
Value: 1 - 8191
count value
Value: 1 - 1024
Default Value: 10
pcp value
Description: PCP (priority code point) value used in the 802.1Q VLAN tag.
Value: 0-7
Default Value: 0
interval value
Default Value: 1s
size value
Value: 64 - 9000
Default Value: 64
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
In order to start a delay-measurement session, the CFM Maintenance Domain (MD), the
Maintenance Association (MA) with at least one remote Maintenance Endpoint (MEP),
and the local MEP must be previously configured.
The example below shows the creation of the entities, as mentioned earlier in the con-
figuration:
# config
(config)# dot1q vlan 10,20,30
(config-vlan-10,20,30)# top
(config)# oam
(oam)# cfm
(cfm)# md CFM_MD
(cfm-md-CFM_MD)# level 1
(cfm-md-CFM_MD)# ma CFM_MA
(cfm-ma-CFM_MA)# ccm-interval 1s
(cfm-ma-CFM_MA)# vlan-list 10,20,30
(cfm-ma-CFM_MA)# primary-vlan-id 20
(cfm-ma-CFM_MA)# remote-meps 10-15
(cfm-ma-CFM_MA)# mep 1
(cfm-mep-1)# interface gigabit-ethernet-1/1/2
(cfm-mep-1)# direction down
(cfm-mep-1)# primary-vlan-id 10
(cfm-mep-1)# commit
(cfm-ma-CFM_MA1)# commit
Commit complete.
(cfm-ma-CFM_MA1)# end
#
The remote MEP must also be known. Therefore, at least one valid CCM must be received
from the remote MEP before starting a session.
The delay-measurement replies are shown interactively, and the session summary is
provided in the end:
Hardware restrictions
N/A
linktrace
Description
Trigger a linktrace.
Supported Platforms
Syntax
Parameters
md id
ma id
mep id
Description: Local MEP unique identifier inside the MA. Only an already cre-
ated Local MEP is accepted.
Value: 1 - 8191
remote-mep id
Description: Remote MEP unique identifier inside the MA. Only an already
created Remote MEP is accepted.
Value: 1 - 8191
ttl value
Value: 2 - 255
Default Value: 64
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
In order to start a linktrace operation, the CFM Maintenance Domain (MD), the Mainte-
nance Association (MA) with at least one remote Maintenance Endpoint (MEP) and the
local MEP must be previously configured.
The example below shows the creation of the aforementioned elements in the config-
uration:
# config
(config)# dot1q vlan 10,20,30
(config-vlan-10,20,30)# top
(config)# oam
(oam)# cfm
(cfm)# md CFM_MD
(cfm-md-CFM_MD)# level 1
(cfm-md-CFM_MD)# ma CFM_MA
(cfm-ma-CFM_MA)# ccm-interval 1s
(cfm-ma-CFM_MA)# vlan-list 10,20,30
(cfm-ma-CFM_MA)# primary-vlan-id 20
(cfm-ma-CFM_MA)# remote-meps 10-15
(cfm-ma-CFM_MA)# mep 1
(cfm-mep-1)# interface gigabit-ethernet-1/1/2
(cfm-mep-1)# direction down
(cfm-mep-1)# primary-vlan-id 10
(cfm-mep-1)# commit
(cfm-ma-CFM_MA1)# commit
Commit complete.
(cfm-ma-CFM_MA1)# end
#
The remote MEP must also be known. Therefore, at least one valid CCM must be received
from the remote MEP before starting a linktrace session.
The linktrace result will be displayed interactively, but can also be seen with the com-
mand:
# show oam cfm linktrace
A linktrace is automatically started by a local MEP to a remote MEP when three con-
secutive Continuity Check Messages are missed from that remote MEP.
Hardware restrictions
N/A
loopback
Description
Supported Platforms
Syntax
Parameters
md id
ma id
mep id
Description: Local MEP unique identifier inside the MA. Only an already cre-
ated Local MEP is accepted.
Value: 1 - 8191
remote-mep id
Description: Remote MEP unique identifier inside the MA. Only an already
created Remote MEP is accepted.
Value: 1 - 8191
count value
Value: 1 - 1024
Default Value: 10
size value
Value: 64 - 16383
Default Value: 64
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
In order to start a loopback operation, the CFM Maintenance Domain (MD), the Mainte-
nance Association (MA) with at least one remote Maintenance Endpoint (MEP) and the
local MEP must be previously configured.
The example below shows the creation of the aforementioned elements in the config-
uration:
# config
(config)# dot1q vlan 10,20,30
(config-vlan-10,20,30)# top
(config)# oam
(oam)# cfm
(cfm)# md CFM_MD
(cfm-md-CFM_MD)# level 1
(cfm-md-CFM_MD)# ma CFM_MA
(cfm-ma-CFM_MA)# ccm-interval 1s
(cfm-ma-CFM_MA)# vlan-list 10,20,30
(cfm-ma-CFM_MA)# primary-vlan-id 20
(cfm-ma-CFM_MA)# remote-meps 10-15
(cfm-ma-CFM_MA)# mep 1
(cfm-mep-1)# interface gigabit-ethernet-1/1/2
(cfm-mep-1)# direction down
(cfm-mep-1)# primary-vlan-id 10
(cfm-mep-1)# commit
(cfm-ma-CFM_MA1)# commit
Commit complete.
(cfm-ma-CFM_MA1)# end
#
The remote MEP must also be known. Therefore, at least one valid CCM must be received
from the remote MEP before starting a loopback session.
Loopback replies are shown as they are received, and a session summary is presented
when it is terminated.
Loopback session started to 00:04:df:01:02:03
Reply from 00:04:df:01:02:03, transaction 1
Reply from 00:04:df:01:02:03, transaction 2
Reply from 00:04:df:01:02:03, transaction 3
Reply from 00:04:df:01:02:03, transaction 4
Reply from 00:04:df:01:02:03, transaction 5
Reply from 00:04:df:01:02:03, transaction 6
Reply from 00:04:df:01:02:03, transaction 7
Reply from 00:04:df:01:02:03, transaction 8
Reply from 00:04:df:01:02:03, transaction 9
Reply from 00:04:df:01:02:03, transaction 10
Session summary:
Expected 10 replies, received 10 with valid order and 0 out of order.
Replies with wrong payload: 0.
N/A
Hardware restrictions
N/A
Description
Display consolidated delay-measurement statistics for the specified probe and session.
If no probe is specified, all probes are shown. If no session is specified for a given probe,
all sessions probe sessions are shown. For each session, consolidated statistics of the
last 10 executions are saved and rotated to discard the oldest results.
Supported Platforms
Syntax
Parameters
probe id
Value: 1 - 512
session id
Value: 1-8
Output Terms
Output Description
Average delay for all frames of the most recent execution of this
LAST AVG DELAY
session.
Minimum delay for all frames of the most recent execution of this
LAST MIN DELAY
session.
Maximum delay for all frames of the most recent execution of this
LAST MAX DELAY
session.
Average jitter for all frames of the most recent execution of this ses-
LAST AVG JITTER
sion.
Minimum jitter for all frames of the most recent execution of this
LAST MIN JITTER
session.
Maximum jitter for all frames of the most recent execution of this
LAST MAX JITTER
session.
Frame loss ratio (missing replies) for the most recent execution of
LAST LOSS RATIO
this session.
LAST PCP MISMATCH Ratio of frames received with PCP value that is not equal to the trans-
RATIO mitted value for the most recent execution of this session..
ALL AVG DELAY Average delay for all frames for all execution of this session.
ALL MIN DELAY Minimum delay for all frames for all execution of this session.
ALL MAX DELAY Maximum delay for all frames for all execution of this session.
Output Description
ALL AVG JITTER Average jitter for all frames for all execution of this session.
ALL MIN JITTER Minimum jitter for all frames for all execution of this session.
ALL MAX JITTER Maximum jitter for all frames for all execution of this session.
ALL LOSS RATIO Frame loss ratio (missing replies) for all execution of this session.
ALL PCP MISMATCH Ratio of frames received with PCP value that is not equal to the trans-
RATIO mitted value for all execution of this session.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Detailed show:
DM4050# show oam cfm delay-measurement probe 1 session 1 detail
LAST LAST LAST LAST LAST LAST LAST ALL ALL ALL ALL
AVG MIN MAX AVG MIN MAX LOSS LAST PCP AVG MIN MAX AVG
DELAY DELAY DELAY JITTER JITTER JITTER RATIO MISMATCH DELAY DELAY DELAY JITTER
SESSION PCP (us) (us) (us) (us) (us) (us) % RATIO % (us) (us) (us) (us)
--------------------------------------------------------------------------------------------------------
1 1 4892 3176 7063 940 524 1144 0 0 4892 3176 7063 940
Simplified show:
DM4050# show oam cfm delay-measurement probe 1 session 2
LAST LAST LAST ALL ALL ALL
AVG AVG LOSS LAST PCP AVG AVG LOSS ALL PCP
DELAY JITTER RATIO MISMATCH DELAY JITTER RATIO MISMATCH
SESSION PCP (us) (us) % RATIO % (us) (us) % RATIO %
------------------------------------------------------------------------------
2 2 4635 330 0 0 4635 330 0 0
None
Hardware restrictions
None
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Description: This parameter displays all that the brief parameter displays
plus some current configurations. These include Level, Primary
VLAN ID, VLAN List, CCM Interval, Remote MEP IDs, Interface,
Direction, Fault Alarm Time and Fault Reset Time. When no pa-
rameter is given the show command displays the same content
of detail parameter.
Value: N/A
statistics
Description: This parameter displays the statistics related to local the MEPs,
including the number of received CCMs with sequence errors,
Value: N/A
Output Terms
Output Description
Defects Show all defects detected by state machines in this local MEP.
Highest Priority
Show the highest priority defect presented in this configuration.
Defect
TX Interface The link status of the interface where the local MEP is configured.
Status TLV This status can be Up or Down.
Blocking state that CFM applies to the interface on which the Down
MEP is attached. When fault-action is block-port, this status can be
Block State:
Blocked or Forwarding. Status N/A is presented if fault-action is not
configured.
Output Description
The link status of the port where the local MEP is configured. Cur-
TX Port Status TLV
rently this status only shows “Not present” and will be implemented
in the future.
Output Description
RX Seq Error Count Number of received Continuity Check Messages with sequence num-
ber errors.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the following CFM configuration: md Domain level 5 ma Associ-
ation primary-vlan-id 1 vlan-list 1 ccm-interval 1s remote-meps 2 mep 1 interface gigabit-
ethernet-1/1/9 direction down primary-vlan-id 1 continuity-check cci-enabled lowest-fault-
priority-defect remote-mac-error fault-action block-port. Let’s see the brief information:
# show oam cfm local brief | notab
oam cfm local
md Domain
ma Association
mep 1
mac-address 00:04:df:40:9c:1b
tx-rdi False
defects -
highest-priority-defect -
tx-interface-status-tlv Up
block-state Forwarding
tx-port-status-tlv "Not Present"
#
None
Hardware restrictions
None
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Description: This parameter displays all that the brief parameter displays.
When no parameter is given the show command displays the
same content of detail parameter.
Value: N/A
statistics
Description: This parameter displays the statistics related to the MEPs, in-
cluding the sequence number of the Continuity Check Message
that was last received from this remote MEP.
Value: N/A
Output Terms
Output Description
The operational state of the Remote MEP. ‘Failed’ means that a local
MEP is missing Continuity Check Messages from this remote MEP.
State
‘OK’ means that valid Continuity Check Messages from this remote
MEP are being received with the expected periodicity.
RX Interface The link status of the interface where the remote MEP is configured.
Status TLV This status can be Up or Down
RX Port Status TLV The link status of the port where the remote MEP is configured. This
status can be Up or Blocked.
The time past since last state change occurred. If current remote
MEP state is ‘OK’, this time since the MEP recovered from a failure.
Last State Change
If the current remote MEP state is ‘Failed’, this is the time since the
failure occurred.
RX Last Seq Num Last received Continuity Check Messages sequence number.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the following CFM configuration: md Domain level 5 ma Associ-
ation primary-vlan-id 1 vlan-list 1 ccm-interval 1s remote-meps 2 mep 1 interface gigabit-
ethernet-1/1/9 direction down primary-vlan-id 1 continuity-check cci-enabled lowest-fault-
priority-defect remote-mac-error. Let’s see the brief information:
# show oam cfm remote brief | notab
oam cfm remote
md Domain
ma Association
local-mep 1
remote-mep 2
mac-address 00:04:df:61:25:49
rx-rdi False
state Ok
rx-interface-status-tlv Up
rx-port-status-tlv "Not Present"
last-state-change "1min 41s ago"
rx-sender-id ""
#
mac-address 00:04:df:61:25:49
rx-rdi False
state Ok
rx-interface-status-tlv Up
rx-port-status-tlv "Not Present"
last-state-change "1min 52s ago"
rx-sender-id ""
#
None
Hardware restrictions
None
ACTIVATION TEST
This topic describes the commands related to management of activation test features
such as commands to configure RFC2544 generator or traffic loop with MAC swap sup-
port.
traffic-loop
Description
Create traffic loopback to test and verify the transmit and receive ports.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
traffic-loop id
Value: 1-8
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet.
destination-mac-address mac-address
Value: xx:xx:xx:xx:xx:xx
source-mac-address mac-address
Value: xx:xx:xx:xx:xx:xx
vlan vlan-id
Value: 1 - 4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Release Modification
Usage Guidelines
Example:
Hardware restrictions
N/A
EFM
This topic describes the commands related to the management of transport layer func-
tions between network elements such as commands to monitor the link status or detect
remote failures.
efm
Description
Ethernet in the First Mile configuration according to the specification described in IEEE
802.3ah-2004.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-ethernet.
mode working-mode
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The EFM can be enabled on Ethernet interfaces to monitor link operation and improve
fault isolation on a network.
# config
(config)# oam efm interface gigabit-ethernet-1/1/1
(config-oam-efm-interface-gigabit-ethernet-1/1/1)# mode passive
(config-oam-efm-interface-gigabit-ethernet-1/1/1)# commit
Commit complete.
(config-oam-efm-interface-gigabit-ethernet-1/1/1)# end
#
N/A
Hardware restrictions
N/A
Description
Display information about EFM status and configuration. This show only presents ports
that are configured for EFM.
Supported Platforms
Syntax
Parameters
port
Value: N/A
Output Terms
Output Description
LOCAL DISCOVERY
The local status of the EFM discovery process.
STATUS
Output Description
LOCAL CRITICAL The event indicating if an unspecified critical event has occurred on
EVENT local physical link.
REMOTE DISCOVERY
The remote status of the EFM discovery process.
STATUS
REMOTE CRITICAL The event indicating if an unspecified critical event has occurred on
EVENT remote physical link.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has the following ports configured for EFM.
# show running-config oam efm
efm
interface ten-gigabit-ethernet-1/1/1
mode active
!
!
#
None
Hardware restrictions
None
LLDP
This topic describes the commands related to management of link layer discovery pro-
tocol such as commands to configure optional TLVs or to inspect neighbor’s information.
lldp
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, twenty-five-gigabit-ethernet, forty-gigabit-ethernet,
hundred-gigabit-ethernet.
admin-status status
notification
Value: N/A
tlvs-tx tlv
message-fast-tx seconds
Value: 1-3600
Default Value: 1
message-tx-hold-multiplier ttl-multiplier
Description: Sets the TTL value that is carried in transmitted LLDP frames. It
is used as a multiplier for message-tx-interval.
Value: 2-10
Default Value: 4
message-tx-interval seconds
Value: 5-32768
Default Value: 30
notification-interval seconds
Value: 5-3600
Default Value: 30
reinit-delay seconds
Value: 1-10
Default Value: 2
tx-credit-max frames
Value: 1-100
Default Value: 5
tx-fast-init transmissions
Description: Sets the number of LLDP frames that are transmitted during a
fast transmission period.
Value: 1-8
Default Value: 4
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure LLDP with port-description and system-name TLVs
transmission disabled.
# config
Entering configuration mode terminal
(config)# lldp
(lldp)# message-fast-tx 100
(lldp)# message-tx-hold-multiplier 5
(lldp)# message-tx-interval 20
(lldp)# notification-interval 10
(lldp)# reinit-delay 5
(lldp)# tx-credit-max 50
(lldp)# tx-fast-init 5
(lldp)# interface gigabit-ethernet-1/1/1
(lldp-gigabit-ethernet-1/1/1)# admin-status tx-only
(lldp-gigabit-ethernet-1/1/1)# notification
(lldp-gigabit-ethernet-1/1/1)# no tlvs-tx port-description
(lldp-gigabit-ethernet-1/1/1)# no tlvs-tx system-name
(lldp-gigabit-ethernet-1/1/1)# top
(config)# commit
Commit complete.
(config)#
All optional TLVs are transmitted to neighbors by default. To disable the transmission of
a specific TLV use the no tlvs-tx command.
Hardware restrictions
Description
Supported Platforms
Syntax
Parameters
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, forty-gigabit-ethernet, hundred-gigabit-ethernet.
detail
Value: N/A
statistics
Value: N/A
Output Terms
Output Description
The value that indicates the basis for the chassis ID entity that is
CHASSIS ID SUBTYPE
listed in the chassis ID field. For the local system this value is mac-
address.
The specific identifier for the chassis in this system. For the local
CHASSIS ID
system it is represented by the system MAC.
The description of this network entity. Includes the full name and
SYSTEM DESCRIPTION
version identification of the local system’s hardware type, software
operating system and networking software.
SYSTEM
CAPABILITIES The primary functions supported by the local system.
SUPPORTED
SYSTEM
CAPABILITIES The primary functions enabled on the local system.
ENABLED
The value that indicates the basis for the identifier that is listed in
PORT ID SUBTYPE
the port ID field. For the local system this value is interface-name.
REMOTE TABLE
Total number of neighbors inserted in the LLDP remote table.
INSERTS
Output Description
REMOTE TABLE
Total number of neighbors deleted in the LLDP remote table.
DELETES
REMOTE TABLE
Total number of neighbors aged out in the LLDP remote table.
AGEOUTS
PDU LENGTH ERRORS The number of LLDPDU length errors recorded on a given interface.
DISCARDED TLVS
Current number of discarded TLVs on a given interface.
COUNT
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has 2 interfaces the command could result in the following output:
# show lldp local
lldp local chassis-id-subtype mac-address
lldp local chassis-id 00:04:DF:60:D0:18
lldp local system-name ""
lldp local system-description "Local System Description"
lldp local system-capabilities-supported bridge,router
lldp local system-capabilities-enabled bridge
PORT ID
INTERFACE NAME SUBTYPE ...
--------------------------------------- ...
gigabit-ethernet-1/1/1 interface-name ...
gigabit-ethernet-1/1/2 interface-name ...
PORT ID PORT DESCRIPTION
------------------------------------------------
gigabit-ethernet-1/1/1 Gigabit Ethernet Port 1
gigabit-ethernet-1/1/2 Gigabit Ethernet Port 2
None
Hardware restrictions
None
Description
Supported Platforms
Syntax
Parameters
interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-
ethernet, forty-gigabit-ethernet, hundred-gigabit-ethernet.
brief
Value: N/A
detail
Description: This parameter displays all that the brief parameter displays
plus system capabilities supported, system capabilities enabled,
port ID subtype and port ID from neighbors. When no param-
eter is given the show command displays the same content of
brief parameter.
Value: N/A
management
Value: N/A
unknown-tlvs
Description: This parameter displays the unknown TLVs received from neigh-
bors.
Value: N/A
Output Terms
Output Description
The value that indicates the basis for the chassis ID entity that
CHASSIS ID SUBTYPE is listed in the chassis ID field. Possible values are chassis-
component, interface-alias, port-component, mac-address, network-
address, interface-name and local.
The neighbor’s description. Includes the full name and version iden-
SYSTEM DESCRIPTION
tification of the system’s hardware type, software operating system
and networking software.
Output Description
SYSTEM
CAPABILITIES The primary functions supported by the neighbor.
SUPPORTED
SYSTEM
CAPABILITIES The functions enabled on the neighbor.
ENABLED
The value that indicates the basis for the identifier that is listed in
the port ID field. Possible values are interface-alias, port-component,
PORT ID SUBTYPE
mac-address, network-address, interface-name, agent-circuit-id and
local.
ADDRESS SUBTYPE The type of the management address listed in the address field.
The value that indicates the numbering method used for defining the
INTERFACE ID
interface ID field. Possible values are unknown, if-index and system-
SUBTYPE
port-number.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has 2 interfaces with a neighbor attached at each one of them, the
command could result in the following output:
# show lldp neighbors
NEIGHBOR CHASSIS ID CHASSIS ...
LOCAL INTERFACE ID SUBTYPE ID ...
------------------------------------------------------------- ...
gigabit-ethernet-1/1/1 1 chassis-component 4 ...
gigabit-ethernet-1/1/2 2 chassis-component 4 ...
SYSTEM NAME PORT DESCRIPTION
------------------------------
DmSwitch Ethernet Port 12
DmSwitch Ethernet Port 15
SYSTEM SYSTEM
CAPABILITIES CAPABILITIES ...
SYSTEM NAME SYSTEM DESCRIPTION SUPPORTED ENABLED ...
------------------------------------------------------------- ...
DmSwitch Switch Description bridge bridge ...
DmSwitch Switch Description bridge bridge ...
PORT ID
SUBTYPE PORT ID PORT DESCRIPTION
----------------------------------------------------------
interface-name gigabit-ethernet-1/1/12 Ethernet Port 12
interface-name gigabit-ethernet-1/1/15 Ethernet Port 15
None
Hardware restrictions
None
TWAMP
This topic describes the commands related to management of Active Measurement Pro-
tocol such as commands to configure and inspect OWAMP, TWAMP Generator or TWAMP
Reflector.
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
Output Terms
Output Description
Client address Display the TWAMP Control-Client IP address for this connection.
Display the IP address from the current device used by the TWAMP
Server address
Server on this connection.
Display the TCP port used by the TWAMP Server to initiate this con-
Server port
nection.
State | Connection Display state of the TWAMP-Control connection. States may be: un-
state known, connecting, established, active or finished.
Connection
Display the TWAMP-Control connection identifier.
identifier
VRF name Display the name of VRF instance assigned to TWAMP reflector.
Inactive
connection timeout Display the timeout to close the connection if no packet is received.
Test Session
Display the timeout to close the connection if no packet is received.
Number
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This example below demonstrates two TWAMP-Control sessions. The first session is de-
activated, and the second is running at the moment of the show.
Example:
connecting: the TWAMP-Control session parameters are being negotiated by the Server
and Control-Client.
unknown: unknown state. Either an error occured or it was not possible to determine
the current TWAMP-Control session state
Former TWAMP-Control sessions will appear in this show with state closed.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A
detail
Value: N/A
Output Terms
Output Description
Sender address Display the TWAMP Control-Client IP address for this session.
Output Description
Display the IP address from the current device used by the TWAMP
Reflector address
Session-Reflector on this TWAMP-Test session.
State | Test Display state of the TWAMP-Test session. States may be: unknown,
session state inactive, active.
VRF name Display the name of VRF instance assigned to TWAMP reflector.
Test RX packets
Display the total of received packets with error.
error
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This example below demonstrates two TWAMP-Test sessions. The first TWAMP-Test ses-
sion is deactivated, and the second is running at the moment of the show.
Example:
Closed TWAMP-Test sessions will appear in these shows with state finished.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
connection-id
Value: 1 - 255
brief
Value: N/A
test-session
Value: N/A
test-session-statistics
Value: N/A
Output Terms
Output Description
Administrative
Display the TWAMP connection administrative status configured.
Status
Display the IP address from the current device used by the TWAMP
Server IP
Server on this connection.
Display the TCP port used by the TWAMP Server to initiate this con-
Server port
nection.
VRF name Display the name of VRF instance assigned to TWAMP connection.
Output Description
Last-connection-start-time
Display date and time of last TWAMP-Control connection started.
Last-connection-stop-time
Display date and time of last TWAMP-Control connection finished.
Packet Size Display the packet size configured for this TWAMP-Test session.
Display the UDP minimum port configured for this TWAMP-Test ses-
Min Port
sion.
Display the UDP maximum port configured for this TWAMP-Test ses-
Max Port
sion.
Output Description
Minimum Delay Display the minimum delay value identified during the test.
Maximum Delay Display the maximum delay value identified during the test.
Average Delay Display the average delay value identified during the test.
Minimum Jitter Display the minimum jitter value identified during the test.
Maximum Jitter Display the maximum jitter value identified during the test.
Average Jitter Display the average jitter value identified during the test.
Loss Ratio Display the percentage of packets lost during the test.
Packets Sent Display the number of packets sent during the test.
Packets Received Display the number of packets received during the test.
Packets Error Display the number of packets with errors received during test.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This example below demonstrates the show oam twamp sender connection brief.
Example:
This example below demonstrates the show oam twamp sender connection test-session.
Example:
Reflector IP : 192.168.0.25
Reflector Port : 30119
VRF name : global
DSCP : 0 (CS0)
Packet Size : 64
Min Port : 1024
Max Port : 655351
----------------------------------------------------
#
This example below demonstrates the show oam twamp sender connection test-session-
statistics.
Example:
N/A
Hardware restrictions
N/A
twamp reflector
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to enable the TWAMP Session-Reflector on this device.
(config)# oam twamp reflector
(twamp-reflector)# commit
The TWAMP Session-Reflector will respond to any reachable IP address configured in the
device. This includes the management interface, any L3 logical interface or loopback
interface given they are reachable by the TWAMP controller. To restrict which IP ad-
dresses should be allowed to start a test session, use the command twamp reflector
client-address.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
administrative-status status
Value: up | down.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
N/A
Hardware restrictions
N/A
Description
Configures a list of IP addresses allowed to start a TWAMP-Test session with this reflector.
This list works as a whitelist ACL.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to allow an IP address to start a TWAMP-Test session with this
reflector.
(config)# oam twamp reflector
(twamp-reflector)# ipv4 client-address 192.168.1.1
(config-client-address-192.168.1.1)# commit
N/A
Hardware restrictions
N/A
Description
Configures a list of IP networks allowed to start a TWAMP-Test session with this reflector.
This command is similar to twamp reflector client-address but allows any IP inside the
configured network to start a test session. This list works as a whitelist ACL.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to allow any IP on a network to start a TWAMP-Test session
with this Session-Reflector.
(config)# oam twamp reflector
(twamp-reflector)# ipv4 client-network 192.168.1.0/24
(config-client-network-192.168.1.0/24)# commit
N/A
Hardware restrictions
N/A
Description
Configures which TCP port will listen for connections on this TWAMP Session-Reflector.
Note that the TWAMP Session-Reflector must be disabled to allow the change of the port
number.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
port port-number
Description: Set the TCP port number that will be listening for new TWAMP-
Control connections.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to change the TWAMP Session-Reflector listening TCP port.
(config)# oam twamp reflector
(twamp-reflector)# port 50000
(twamp-reflector)# commit
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vrf vrf-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to assign the VRF to TWAMP reflector on this device.
(config)# oam twamp reflector
(twamp-reflector)# vrf red
(twamp-reflector)# commit
Commit complete.
(twamp-reflector)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
administrative-status status
Value: up | down.
Default Value: up
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the global administrative status of TWAMP Control-
Client on this device.
(config)# oam twamp sender administrative-status down
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the TWAMP Control-Client connection on this de-
vice.
(config)# oam twamp sender connection 1
(config-connection-1)#
(config-connection-1)# ipv4 source-address 192.168.0.26
(config-source-address-192.168.0.26)# exit
(config-connection-1)# ipv4 target-address 192.168.0.25
(config-target-address-192.168.0.25)# exit
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
administrative-status status
Value: up | down.
Default Value: up
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the administrative status of TWAMP Control-Client
connection on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# administrative-status down
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
number-of-packets number
Value: 1 - 65535
Default Value: 50
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the number of packets used on every TWAMP-Test
session on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# number-of-packets 100
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
server-port
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the server port of the TWAMP Control-Client con-
nection on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# server-port 1024
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-session
Value: 1 - 255
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the TWAMP-Test sessions on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# test-session 1
(config-test-session-1)# ipv4 source-address 192.168.0.26
(config-source-address-192.168.0.26)# exit
(config-test-session-1)# ipv4 target-address 192.168.0.25
(config-target-address-192.168.0.25)# exit
(config-test-session-1)# commit
Commit complete.
(config-test-session-1)#
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-session test-session ID
Value: 1 - 255
Value: 0 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34
| 36 | 38 | 40 | 46 | 48 | 56
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the DSCP used in TWAMP-Test session on this de-
vice.
(config)# oam twamp sender connection 1
(config-connection-1)# test-session 1
(config-test-session-1)# dscp 56
(config-test-session-1)# commit
Commit complete.
(config-test-session-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-session test-session ID
Value: 1 - 255
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the UDP maximum port of a TWAMP-Test session
on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# test-session 1
(config-test-session-1)# max-port 6500
(config-test-session-1)# commit
Commit complete.
(config-test-session-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-session test-session ID
Value: 1 - 255
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the UDP minimum port of a TWAMP-Test session on
this device.
(config)# oam twamp sender connection 1
(config-connection-1)# test-session 1
(config-test-session-1)# min-port 2048
(config-test-session-1)# commit
Commit complete.
(config-test-session-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-session test-session ID
Value: 1 - 255
packet-size size
Value: 64 - 65535
Default Value: 64
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the packet size used in a TWAMP-Test session
on this device.
(config)# oam twamp sender connection 1
(config-connection-1)# test-session 1
(config-test-session-1)# packet-size 128
(config-test-session-1)# commit
Commit complete.
(config-test-session-1)#
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
test-interval interval
Value: 0 - 65535
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the TWAMP Control-Client connection on this de-
vice.
(config)# oam twamp sender connection 1
(config-connection-1)# test-interval 60
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
All TWAMP-Test sessions of a connection will start after test-interval counting. Before the
first round of tests the state of all TWAMP-Test sessions will show – indicating that tests
don’t run yet.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
connection-id
Value: 1 - 255
vrf vrf-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to assign the VRF to TWAMP Control-Client connection.
(config)# oam twamp sender connection 1
(config-connection-1)# vrf red
(config-connection-1)# commit
Commit complete.
(config-connection-1)#
N/A
Hardware restrictions
N/A
SFLOW
This topic describes the commands related to the configuration of sFlow Protocol.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
agent ipv4 ip
Value: a.b.c.d
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the IP address (identifier) of sFlow agent.
(config)# oam
(oam)# sflow agent ipv4 192.168.0.26
(sflow)# commit
Commit complete.
N/A
Hardware restrictions
N/A
sflow collector
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
name
ipv4 address
Value: a.b.c.d
enabled
Value: n/a
disabled
Value: n/a
max-datagram-size size
Value: 200-9116
port value
Value: 1-65535
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Example:
This example shows how to configure a sFlow collector UDP port and maximum data-
gram size.
(config)# oam
(oam)# sflow collector collector_1
(config-sflow-collector-collector_1)# port 32768
(config-sflow-collector-collector_1)# max-datagram-size 4500
(config-sflow-collector-collector_1)# commit
Commit complete.
(config-sflow-collector-collector_1)#
The maximum datagram size must take into account the maximum header size con-
figured at the interfaces, otherwise samples may be dropped. Also, if those values are
close enough to each other, it may happen to have sFlow datagrams with 0 (zero) sam-
ples sent to collector.
Hardware restrictions
N/A
sflow interface
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
interface
Value: String
flow-sampling-rate rate
Description: Specifies the interface sampling rate in the format 1/rate. Flow
sampling average of 1 out of N packets transmitted or received
on the port.
max-header-size size
Value: 64-512
flow-sampling-collector collector-name
Value: String
counter-sampling-collector collector-name
Value: String
counter-sampling-interval interval
Value: 2-3600
Default Value: 20
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
Example:
Example:
This example shows how to configure the maximum header size in a monitored inter-
face.
(config)# oam
(oam)# sflow
(sflow-collector-collector_1)# interface gigabit-ethernet-1/1/1
(sflow-gigabit-ethernet-1/1/1)# max-header-size 256
(sflow-gigabit-ethernet-1/1/1)# commit
Commit complete.
(sflow-gigabit-ethernet-1/1/1)#
You can use ranges and wildcards to edit more than one interface at once. Note that
range operations do not add new interfaces, they only act on already added interfaces.
(config)# oam
(oam)# sflow
(sflow)# collector collector_1 ipv4 10.1.1.1
(sflow-collector-collector_1)# interface gigabit-ethernet-1/1/1
(sflow-gigabit-ethernet-1/1/1)# interface gigabit-ethernet-1/1/3
(sflow-gigabit-ethernet-1/1/3)# interface ten-gigabit-ethernet-1/1/1
(sflow-ten-gigabit-ethernet-1/1/1)# exit
(sflow)# interface gigabit-ethernet-1/1/1-3
(sflow-gigabit-ethernet-1/1/1-3)# flow-sampling-rate 5000
(sflow-gigabit-ethernet-1/1/1-3)# interface ten-gigabit-ethernet-1/1/*
(sflow-ten-gigabit-ethernet-1/1/*)# flow-sampling-rate 40000
(sflow-gigabit-ethernet-1/1/1)# commit
Commit complete.
(sflow-gigabit-ethernet-1/1/1)# top
(config)# show oam sflow
oam
sflow
interface gigabit-ethernet-1/1/1
flow-sampling-rate 5000
!
interface gigabit-ethernet-1/1/2
flow-sampling-rate 5000
!
interface gigabit-ethernet-1/1/3
flow-sampling-rate 5000
!
interface ten-gigabit-ethernet-1/1/1
flow-sampling-rate 40000
!
!
!
Example:
This example shows how to configure an interface to send counter samples to a counter
collector.
(config)# oam
(oam)# sflow
(sflow)# collector collector_1 ipv4 10.1.1.1
(sflow-collector-collector_1)# interface gigabit-ethernet-1/1/1
(sflow-gigabit-ethernet-1/1/1)# counter-sampling-collector collector_1
(sflow-gigabit-ethernet-1/1/1)# counter-sampling-interval 10
(sflow-gigabit-ethernet-1/1/1)# commit
Commit complete.
(sflow-gigabit-ethernet-1/1/1)#
Once an interface and collector are configured in sFlow, it starts sampling on that inter-
face with default sampling rate. In order to disable the sampling, the user must remove
the interface or collector from sFlow. Some sample packets can be dropped if the maxi-
mum datagram size does not take into account the maximum header size.
For egress flow sampling, only unicast packets are sent to sflow collector. Multicast,
broadcast and unknown unicast packets are not supported in the egress direction.
Hardware restrictions
N/A
This topic describes the commands related to Remote Devices Management (RDM) such
as commands to allow remote control by a master device.
remote-devices
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
mode operational-mode
Value: slave
interface interface-name
Value: interface-type-chassis/slot/port
Examples of interface-type: gigabit-ethernet, ten-gigabit-ethernet.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
RDM can be enabled on Ethernet interfaces to allow the remote control by a master
device. EFM protocol must be enabled on the interface to allow the configuration.
# config
(config)# oam efm interface gigabit-ethernet-1/1/1
(config-oam-efm-interface-gigabit-ethernet-1/1/1)# mode passive
(config-oam-efm-interface-gigabit-ethernet-1/1/1)# top
(config)# remote-devices interface gigabit-ethernet-1/1/1
(rdm-gigabit-ethernet-1/1/1)# commit
Commit complete.
(rdm-gigabit-ethernet-1/1/1)# end
#
N/A
Hardware restrictions
N/A
show remote-devices
Description
Display information about RDM status and configuration. This show only presents ports
that are configured for RDM.
Supported Platforms
Syntax
Parameters
port
Value: N/A
Output Terms
Output Description
RECEIVED IP
IP address configuration received from remote equipment.
ADDRESS
RECEIVED DEFAULT Default Gateway address configuration received from remote equip-
GATEWAY ment.
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Given the equipment has established the communication with another equipment through
RDM protocol and the following port configured for RDM.
# show running-config remote-devices
remote-devices
interface gigabit-ethernet-1/1/1
!
!
#
None
Hardware restrictions
None
NTP
This topic describes the commands related to management of Network Time Protocol
such as commands to configure an external NTP Server or to inspect the system clock.
clock
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
timezone name
Description: Set a friendly name for the timezone. Any value will be ac-
cepted.
timezone offset
Description: Define an offset from UTC for the show system clock com-
mand.
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
clock timezone is used to describe the current device location and its offset from
UTC (a value of 0 defines that the device should output times in UTC); show system
clock displays the current system clock, using the offset information provided by clock
timezone.
Usage example:
DM4610# config
DM4610(config)# clock timezone Brazil -3
DM4610(config)# commit
Commit complete.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
date
Value: YYYYMMDD
time
Description: Set the clock time, in “hh:mm:ss” format. The clock must be
set in a 24-hour format.
Value: hh:mm:ss
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
The command syntax was modified from “set clock” to “set system
1.8
clock”.
Usage Guidelines
Usage example:
N/A
Hardware restrictions
N/A
show sntp
Description
Supported Platforms
Syntax
Parameters
brief
Value: N/A.
Output Terms
Output Description
Output Description
Offset Relative time of the server clock to the local clock (in milliseconds).
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Usage example:
*Field in seconds if not specified, otherwise ’h’ for hours and ’m’ for minutes.
Note that if SNTP authentication fail the server will be shown as unreachable like Server
IP 1.1.1.3 on table above.
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
N/A
Output Terms
Output Description
Current date and Displays the Current date and time in “YYYY-MM-DD HH:MM:SS
time UTC[offset] [Timezone-name]” format
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
The command syntax was modified from “show clock” to “show system
clock”.
Date and time display format for “show system clock” command was
1.8
changed from “[day of the week] [month] [day] HH:MM:SS (timezone
name/UTC[offset])” to “YYYY-MM-DD HH:MM:SS UTC[offset] [Timezone-
name]”.
Usage Guidelines
Usage example:
N/A
Hardware restrictions
N/A
sntp
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
authenticate
Value: None
client
Value: None
min-poll poll-interval
max-poll poll-interval
Description: Specifies the source IPv4 address from which NTP server con-
nection will be established.
Value: a.b.c.d
Description: Specifies the source IPv6 address from which NTP server con-
nection will be established.
Value: X:X:X:X::X
Description: Specifies the source interface from which NTP server connec-
tion will be established.
server IP address
Description: Sets the IP address of a NTP server the SNTP Client is allowed
to synchronize with. Max number of servers is six.
key key ID
Value: 1-4294967295.
authentication-key key ID
Value: 1-4294967295.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Since the parameters min-poll and max-poll are defined using an exponent in power of
two, in accordance to RFC 5905, the following table exemplifies the exponent converted
value in different time units for a better comprehension of its impact in the configura-
tion.
Both the source ip address and source interface fields specify the source of NTP
+-------------+-------------+
| Exponent | Time |
+-------------+-------------+
| 3 | 8s |
| 4 | 16s |
| 5 | 32s |
| 6 | 1m04s |
| 7 | 2m08s |
| 8 | 4m16s |
| 9 | 8m32s |
| 10 | 17m04s |
| 11 | 34m08s |
| 12 | 1h08m16s |
| 13 | 2h16m32s |
| 14 | 4h33m04s |
| 15 | 9h06m08s |
| 16 | 18h12m16s |
| 17 | 36h24m32s |
+-------------+-------------+
Example:
Enable ntp to server 172.22.110.101 with a polling interval between 32 (2ˆ5) and 256
(2ˆ8) seconds:
# config
(config)# sntp client
(config)# sntp authenticate
(config)# sntp authentication-key 1 md5 "¨
?![:]21476a8*x"
(config)# sntp min-poll 5
(config)# sntp max-poll 8
(config)# sntp server 172.22.110.101 key 1
(config)# commit
Commit complete.
Enable ntp to server 2001:DB8::1 with a polling interval between 8 (2ˆ3) and 16 (2ˆ4)
seconds:
# config
(config)# sntp client
(config)# sntp authenticate
(config)# sntp authentication-key 1 md5 "¨
?![:]21476a8*x"
(config)# sntp min-poll 3
(config)# sntp max-poll 4
(config)# sntp server 2001:DB8::1 key 1
(config)# commit
Commit complete.
The source IP address field is only valid in the global vrf context. It does not work in the
scope of a user VRF, use source interface instead.
When source interface is used, the NTP transaction is in unsymmetric mode, i.e. the
source and destination ports of NTP packets are different. This is described in RFC 958,
inside 5. Protocol Operation, 5.1. Protocol Modes.
When there are two or more servers configured on sntp and these servers are accessible
through different l3 interfaces on the same VRF, no matter the l3 interface chosen to be
the source interface.
Hardware restrictions
N/A
OLT
This topic describes the global commands related to GPON OLT, service-port and service-
vlan.
aes-key-exchange
Description
Supported Platforms
Syntax
aes-key-exchange { interval }
Parameters
aes-key-exchange interval
Description: The time interval for the AES Key Exchange procedure.
Default
N/A
Command Mode
Configuration mode
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# gpon 1/1
(config-gpon-1/1)# aes-key-exchange 30
None
Hardware restrictions
N/A
Description
This command clears the statistics for a GPON interface, ONU Ethernet or ONU GEM port.
Supported Platforms
Syntax
Parameters
id
onu-id
ethernet-port
Value: Number: 1 to 4.
gem-port
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Removed no longer valid ONU ethernet and GEM port statistics parame-
1.8
ters.
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# clear interface statistics gpon 1/1/1
All statistics counters for the selected GPON interface, ONU Ethernet or ONU GEM port
will be erased.
Hardware restrictions
N/A
interface gpon
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
upstream-fec
Value: None.
downstream-fec
Value: None.
Description: Configures the minimum logical distance from OLT to ONU (in
km).
The difference between maximum and minimum distance must
be at least 20 km and cannot exceed 40 km.
Value: 0-40
Default Value: 0
Description: Configures the maximum logical distance from OLT to ONU (in
km).
The difference between maximum and minimum distance must
be at least 20 km and cannot exceed 40 km.
Value: 0-60
Default Value: 40
shutdown
Value: None.
description
Description: Set the interface description or alias. Valid characters are A-Z,
a-z, 0-9 and - _ / + * @
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
To set interface gpon parameters is necessary to enter in the interface gpon menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)#
To set description
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# description "test interface name"
Or
(config-gpon-1/1/1)# description test_interface_name
On shutdown, the GPON interface will be disabled affecting ongoing data traffic. The
user must enter ‘interface gpon <id>’ mode to issue other interface commands.
When configuring PON link reach max-distance, take special care to give a room of 5km
considering the farthest ONU. For example, if the farthest ONU is at 20km, set reach
max-distance to 25km.
Hardware restrictions
N/A
load default-gpon-profiles
Description
Loads the default GPON profiles, which allow a quick configuration of GPON features.
Supported Platforms
Syntax
load default-gpon-profiles
load default-gpon-profiles-bridge
load default-gpon-profiles-router
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The commands create all default GPON profiles that are required to add ONUs to the
configuration database. That is, the user have to neither create the profiles nor select
them on the ONU. There are different sets of profiles for different applications.
There are three different sets of GPON profiles that can be loaded.
1) load default-gpon-profiles-bridge: suitable for bridge ONUs.
2) load default-gpon-profiles-router: suitable for router ONUs.
3) load default-gpon-profiles: suitable for bridge or router ONUs. Contains a line-profile
that supports bridge (ethernet-uni) or router (veip). The OLT will skip any of the flow
mappings (see line profile) if the ONU does not support it.
# config
Entering configuration mode terminal
(config)# show configuration this
% No configuration changes found.
(config)# load default-gpon-profiles-?
Possible completions:
default-gpon-profiles-bridge Load the default GPON profiles for bridge ONUs
default-gpon-profiles-router Load the default GPON profiles for router ONUs
(config)# load default-gpon-profiles-bridge
Loading.
Done.
(config)# show configuration this
profile gpon bandwidth-profile DEFAULT-BANDWIDTH
traffic type-4 max-bw 1106944
!
profile gpon line-profile DEFAULT-LINE
upstream-fec
tcont 1 bandwidth-profile DEFAULT-BANDWIDTH
gem 1
tcont 1 priority 1
map any-ethernet
ethernet any vlan any cos any
!
!
gem 2
tcont 1 priority 0
map any-iphost
iphost vlan any cos any
!
!
!
(config)# commit
Commit complete.
(config)#
# config
Entering configuration mode terminal
(config)# interface gpon 1/1/3
(config-gpon-1/1/3)# onu 7
(config-gpon-onu-7)# show configuration this
interface gpon 1/1/3
onu 7
line-profile DEFAULT-LINE
!
!
(config-gpon-onu-7)# serial-number DTCM12345678
(config-gpon-onu-7)# show configuration this
interface gpon 1/1/3
onu 7
serial-number DTCM12345678
line-profile DEFAULT-LINE
!
!
(config-gpon-onu-7)# commit
Commit complete.
(config-gpon-onu-7)#
Example: Editing profiles before the commit, to make them suitable for a different
application.
# config
Entering configuration mode terminal
(config)# load default-gpon-profiles-router
Loading.
Done.
(config)# show configuration this
profile gpon bandwidth-profile DEFAULT-BANDWIDTH
traffic type-4 max-bw 1106944
!
profile gpon line-profile DEFAULT-LINE
upstream-fec
tcont 1 bandwidth-profile DEFAULT-BANDWIDTH
gem 1
tcont 1 priority 1
map any-veip
veip 1 vlan any cos any
!
!
gem 2
tcont 1 priority 0
map any-iphost
iphost vlan any cos any
!
!
!
Edit the Bandwidth Profiles with a different traffic type and bandwidth:
(config)# profile gpon bandwidth-profile DEFAULT-BANDWIDTH
(config-bandwidth-profile-DEFAULT-BANDWIDTH)# traffic type-1 fixed-bw 5120
(config-bandwidth-profile-DEFAULT-BANDWIDTH)# top
(config)# profile gpon line-profile DEFAULT-LINE
(config-line-profile-DEFAULT-LINE)# gem 1
(config-line-prof-gem-1)# no map any-veip
(config-line-prof-gem-1)# map veip-300
(config-line-prof-gem-map-veip-300)# veip 1 vlan 300 cos any
It is advised to use only one of the commands at a time, as running more than one will
merge the configurations, potentially creating non-functional configurations.
Hardware restrictions
N/A
onu-auto-provisioning
Description
Supported Platforms
Syntax
onu-auto-provisioning service-port sp-id gem gem port match vlan vlan-id { user-
vlan | any } action { vlan { add vlan-id vid | replace vlan-id vid } } [ inner-vlan
replace vlan-id vid ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
enable
Value: None
ipv4 dhcp
Value: None
Value: 1-4094
Value: 0-7
line-profile line-profile-name
rg-profile rg-profile-name
service-profile service-profile-name
snmp-profile snmp-profile-name
sp-id
Value: 1-16
Description: The name of the GEM Port where the service-port must apply.
Value: 1-16
Description: The value of the user VLAN where the service-port must apply.
Description: Adds, replaces or allow a transparent flow for the matched VLAN
on network side. add vlan-id vid: Adds the vid VLAN to the
packets matched by the user-VLAN; replace vlan-id vid: Re-
places the vid VLAN in the packets matched by the user-VLAN;
Value: 1-4094
Description: Replaces the inner-VLAN for the matched VLAN on network side.
replace vlan-id vid: Replaces the vid VLAN in the packets
matched by the user-VLAN;
Value: 1-4094
ethernet ethernet-uni-id
Description: Specify an ethernet UNI that must be created by the ONU auto
provisioning function. Required in order to monitor SNMP OIDs
for the ethernet UNI.
Value: 1-4
Value: 1-4094
Description: Configures the VLAN ID and CoS for the untagged traffic in the
ONU ethernet UNI.
Value: 0-7
Default Value: 0
veip veip-id
Description: Specify a VEIP that must be created by the ONU auto provision-
ing function.
Value: 1
Value: 1-4094
Description: Configures the VLAN ID and CoS to be added for the untagged
traffic in the ONU VEIP.
Value: 0-7
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
The following configuration will enable auto provisioning feature and make auto provi-
sioned ONUs with one traffic flow.
Example:
Example:
Example:
Example:
When auto provisioning is enabled, ONUs are added automatically to database upon an
ONU discovery.
It is possible that the database configuration may be rejected due to some database
validation, such as maximum number of ONUs in the PON link was reached, PON link
bandwidth exceeded etc.
In those cases, an alarm per GPON interface is raised. The reject cause will be present
in the user logs.
Once solved the problem, the alarm will be cleared and new ONUs can be added auto-
matically again.
If upstream FEC is enabled on the line profile used for auto provisioning, it must also be
enabled on all PON links.
When using auto provisioning it is recommended to use T-CONT traffic type 4, which has
no assured or fixed bandwidths. Using any other type, and depending on the values
configured, the PON link may run out of bandwidth and new ONUs will not be correctly
provisioned.
IMPORTANT NOTE 1: Avoid entering in configuration prompt by using “config exclusive”.
Using this mode may cause undesired behavior once auto provisioning feature does
commits into the database. Mode “config exclusive” is recommended when ONU config-
uration must be changed manually by the operator, preventing auto provisioning feature
to add ONUs concurrently.
IMPORTANT NOTE 2: Even when using default configuration mode, upon commit, the
following message may be displayed: “Aborted: the configuration database is locked by
session 59 dummy tcp (system from 127.0.0.1). . . ”. This means that there was a commit
concurrency with the auto provisioning feature. Try to run commit again.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
profile gpon line-profile profile-name gem gem-id map map-name [ ethernet {vlan
{ vlan-id | any} cos { cos-val | any } }
profile gpon line-profile profile-name gem gem-id map map-name [ iphost { vlan {
vlan-id | any} cos { cos-val | any } }
profile gpon line-profile profile-name gem gem-id map map-name [ veip veip-id
{vlan { vlan-id | any} cos { cos-val | any } }
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
line-profile profile-name
tcont tcont-id
Value: 1-6.
bandwidth-profile bandwidth-profile-name
priority priority-value
Value: 0-7.
Default Value: 0.
gem-traffic-profile profile-name
upstream-fec
Value: None.
gem gem-id
Value: 1-16.
map map-name
iphost
Value: None.
veip { veip-id }
1.
Description: VLAN ID to be mapped to a GEM port. To use all VLAN IDs, set
any. Use value any in conjunction with service-port match any
for untagged traffic.
Description: CoS values that will be taken into account by the GEM port. To
use all CoS values, set any. The syntax for a range is 0-3, to use
the CoS values 0 to 3, or 1,2,4 to use the CoS 1, 2 and 4.
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
1.4 The the maximum GEM ID value was changed from 40 to 16.
Usage Guidelines
Create a Bandwidth Profile before binding to a T-CONT by using command profile gpon
bandwidth-profile bandwidth-profile-name and configure a traffic type. See bandwidth-
profile page.
Bind a Bandwidth Profile to a T-CONT before mapping GEM ports.
To set interface line profile is necessary to enter in the line profile menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon line-profile lineProfName
(config-line-profile-lineProfName)#
The mapping of Ethernet ports to a GEM port is done through line profile menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon line-profile lineProfName
(config-line-profile-lineProfName)#tcont 1 bandwidth-profile bw1
(config-line-profile-lineProfName)#gem 1
(config-line-prof-gem-1)#gem 1
(config-line-prof-gem-1)# tcont 1 priority 0
(config-line-prof-gem-1)# map map1
(config-line-prof-gem-map-map1)# ethernet 1 vlan 400 cos 0
Example:
The mapping of IPHOST port to a GEM port is done through line profile menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon line-profile lineProfName
(config-line-profile-lineProfName)#tcont 1 bandwidth-profile bw1
(config-line-profile-lineProfName)#gem 1
(config-line-prof-gem-1)#gem 1
(config-line-prof-gem-1)# tcont 1 priority 0
(config-line-prof-gem-1)# map map1
(config-line-prof-gem-map-map1)# iphost vlan 400 cos 0
The mapping of VEIP port to a GEM port is done through line profile menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon line-profile lineProfName
(config-line-profile-lineProfName)#tcont 1 bandwidth-profile bw1
(config-line-profile-lineProfName)#gem 1
(config-line-prof-gem-1)#gem 1
(config-line-prof-gem-1)# tcont 1 priority 0
(config-line-prof-gem-1)# map map1
(config-line-prof-gem-map-map1)# veip 1 vlan 500 cos 0
Some third-party ONUs may not support native VLAN configuration on Ethernet UNI. To
use untagged traffic set line-profile match VLAN to any and use service-port match any
with action add, this will work as a native VLAN on the service-port.
The sum of the rates of the bandwidth-profiles of the line-profile must not exceed the
ponlink capacity (1.25 Gbps).
For DM4610 platform, line profile cannot have more than 3 TCONTs with bandwidth traffic
type 2 to 5 and 3 TCONTs with bandwidth traffic type 1.
For DM4610-HW2/DM4615 platforms, line profile cannot have more than 4 TCONTs with
bandwidth traffic type 2 to 5 and 3 TCONTs with bandwidth traffic type 1.
Configuring one gem map with vlan any and another gem map, with the same ports,
with a specific vlan will result in undefined behavior because it is not guaranteed which
mapping will match first.
It is also not valid to use vlan any on more than one gem map for the same group
of ports.
When using an ONU with more than one Ethernet interface, the group of ports in a gem
map should not have an intersection with another gem map, though it can be the same.
It is recommended to use only one gem map for each GEM port because some ONUs
may not support configuring more than one mapping for each GEM. With the exception
of having a gem map for Ethernet and one for VEIP on the same GEM port, because the
ONU will effectively only use one of them.
Hardware restrictions
None
rg-one-shot-prov
Description
Supported Platforms
Syntax
rg-one-shot-prov
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# gpon 1/1
(config-gpon-1/1)# rg-one-shot-prov
To re-provision RG Profile to ONU, the command rg-reprovision, available on the onu config-
uration tree, must be used.
Hardware restrictions
N/A
Description
Command used to configure service flood blocking on preexisting VLAN type n:1.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1 - 4094
block traffic-type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
VLAN must be created and configured to type n:1 to configure a service block for it. The
commit of a configuration with a service block on a non existing VLAN will result in an
error message and the configuration won’t be applied.
Changing service type to other than n:1 will erase any previous service block configura-
tion.
Default behaviour of VLANs is not to block any traffic.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1 - 4094
type service-type
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
VLAN must be created to configure a service for it. The commit of a configuration with a
service type on a non existing VLAN will result in an error message and the configuration
won’t be applied.
Some packets might be lost when this configuration is applied due to changes on VLAN
behavior.
Only with pre-existing VLANs the configuration commit will be successful.
Hardware restrictions
N/A
service-port
Description
Individualizes the data flow for each user, allowing the passthrough of this traffic and
even do VLAN translation on it. It is used to connect the network side and the user
device side.
Supported Platforms
Syntax
service-port rule-id
service-port new
gpon ponlink onu onu-id gem gem port [ match vlan vlan-id { user-vlan | any }
action { vlan { add vlan-id vid | replace vlan-id vid } } [ inner-vlan replace vlan-
id vid ] ] [ description description-text ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
service-port rule-id
Value: 1-16777215
service-port new
Value: None.
gpon ponlink
Value: chassi/slot/port
onu onu-id
Value: 0-127
Description: The name of the GEM Port where the service-port must apply.
Value: 1-16
Description: The value of the user VLAN where the service-port must apply.
Description: Adds, replaces or allow a transparent flow for the matched VLAN
on network side. add vlan-id vid: Adds the vid VLAN to the
packets matched by the user-VLAN, if using match any this will
work as a native VLAN; replace vlan-id vid: Replaces the vid
VLAN in the packets matched by the user-VLAN;
Value: 1-4094
Description: Replaces the inner-VLAN for the matched VLAN on network side.
replace vlan-id vid: Replaces the vid VLAN in the packets
matched by the user-VLAN;
Value: 1-4094
description description-text
Value: Text up to 128 characters. Valid characters are A-Z, a-z, 0-9,
space and . - _ / + * @.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
The line breaks between commands below service-port when shown run-
5.8
ning configuration was removed.
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# service-port 1 gpon 1/1/1 onu 1 gem 1 match vlan vlan-id 10
action vlan replace vlan-id 100
Some third-party ONUs may not support native VLAN on Ethernet UNI, a possible workaround
is to use match vlan vlan-id any with action vlan add, thus doing the native VLAN on
the service-port. Note that it is also necessary to use vlan any on the line-profile for the
ONU used on this service-port for untagged traffic to work.
To use a service-port as an access port for a MPLS tunnel, VLAN translate must not be
configured.
Example:
# configure terminal
Entering configuration mode terminal
(config)# service-port 1 gpon 1/1/1 onu 1 gem 1
Service-port parameters can be entered in a line after service-port command. Use “new”
to select the first free index automatically.
Example:
# configure terminal
Entering configuration mode terminal
(config)# service-port 1
(config-service-port-1)# gpon 1/1/1 onu 1 gem 1 match vlan vlan-id 10 action vlan replace vlan-id 100 de
(config)# service-port new
(config-service-port-2)# gpon 1/1/1 onu 2 gem 1 match vlan vlan-id 10 action vlan replace vlan-id 100 de
A gem port that is associated to a service-port used for MPLS services should not be
used in other service-ports.
Service-ports without match and action configuration must be used only for MPLS ser-
vices.
Hardware restrictions
None
Description
Displays GPON interface information. Regarding the discovered ONUs show operation,
an ONU is only displayed if it discovered in the GPON port but not provisioned. Once an
ONU is provisioned, it is no longer displayed.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
chassis/slot/port
brief
statistics
detail
discovered-onus
Value: N/A
Output Terms
Output Description
Physical interface
Name and status of the GPON interface.
Logical reach Show the interface differential logical reach (in kilometers).
Allocated upstream
Header for the types of bandwidth allocated.
bandwidth
Fixed + Assured Allocated bandwidth of both Fixed and Assured types added.
Output Description
Available upstream
Header for the types of available upstream bandwidth.
bandwidth
CBR BW Available fixed bandwidth (traffic type-1 and type-5) in the ponlink.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Release Modification
Usage Guidelines
It is not supported to use commas in the key wildcard in gpon interface discovered-onus
show option (
show interface gpon 1/1/2,3,4 discovered-onus
).
Hardware restrictions
N/A
ONU PROFILES
This topic describes the ONU profiles commands related to ONU traffic configuration,
such as line and service profiles.
Description
The bandwidth-profile is used to enter in bandwidth-profile mode and manage the dy-
namic allocation of bandwidth for upstream flow. In this mode is possible to choose the
traffic type between type-1 to type-5.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
bandwidth-profile profile-name
Description: Name of the profile to create. Must be unique for all bandwidth-
profiles. Can have up to 48 characters.
traffic type-1
traffic type-2
traffic type-3
traffic type-4
traffic type-5
Description: Fixed + assured + max bandwidth. Type-5 defines the user will
have a guaranteed bandwidth, an assured bandwidth that can
fixed-bw fixed-bandwidth
Value: type-1:
Number from 512 to 442752 kbit/s in steps of 64.
type-5:
Number from 128 to 442752 kbit/s in steps of 64.
assured-bw assured-bandwidth
max-bw max-bandwidth
Description: Max bandwidth defines the bandwith the user can reach.
Value: type-3:
Number from 384 to 1106816 kbit/s in steps of 64.
type-4:
Number from 128 to 1106944 kbit/s in steps of 64.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
When using traffic type-3, maximum bandwidth must be greater than or equal to assured
bandwidth + 128 kbit/s.
When using traffic type-5, assured bandwidth must be greater than or equal to fixed
bandwidth + 128 kbit/s and max bandwidth must be greater or equal to fixed + assured
+ 128 kbit/s.
When using DM4610HW2 and traffic type-3, maximum bandwidth must be greater than
or equal to assured bandwidth + 256 kbit/s.
When using DM4610HW2 and traffic type-5, assured bandwidth must be greater than
or equal to fixed bandwidth + 256 kbit/s and max bandwidth must be greater or equal
to fixed + assured + 256 kbit/s.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon bandwidth-profile bwProfName
(config-bandwidth-profile-bwProfName)# traffic type-1 fixed-bw 512
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
gem-traffic-profile profile-name
cir rate
Value: 64-2499968
eir rate
Value: 0-2499904
upstream-gem-priority priority-value
Value: 0-7
Default Value: 0
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config terminal
Entering configuration mode terminal
(config)# profile gpon gem-traffic-profile gemTrProfName
(config-gem-traffic-profile-gemTrProfName)# cir 10240
(config-gem-traffic-profile-gemTrProfName)# eir 5120
(config-gem-traffic-profile-gemTrProfName)# upstream-gem-priority 2
Some ONU models may not support GEM traffic profile. Check the ONU datasheet for
reference.
Hardware restrictions
N/A
Description
The media-profile command is used to configure media parameters for VoIP services,
allowing the user to set a priority ordered codec list, where is set the codec type, packet-
period and silence-suppression for each entry on the list. Media-profile command is also
used to enable/disable out-of-band DTMF, configure the target of the jitter buffer, and
the maximum depth of the jitter buffer.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
media-profile media-profile-name
codec-order order-index
Value: 1-4
type codec-type
packet-period packet-period-value
silence-suppression
Value: None.
Value: N/A
Description: Configure the ONU to use its internal default value for the max-
imum jitter buffer.
Value: N/A
oob-dtmf
Value: None.
pstn-protocol-variant country-code-value
Value: AGO | ARE | ARG | AUS | AUT | BEL | BOL | BRA | CHE | CHL |
CHN | COL | CYP | CZH | DEU | DNK | ECU | EGY | ESP | FIN | FRA
| GBR | GHA | HKG | HUN | IND | IRL | ITA | JPN | KOR | MAR | MEX
| NLD | NOR | NZL | PER | POL | PRY | ROU | SVK | SVN | SWE |
TUN | TWN | URY | USA | VEN | ZAF.
Default
None.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config
Entering configuration mode terminal
(config)# profile gpon media-profile mediaName
(config-media-profile-mediaName)# pstn-protocol-variant BRA
(config-media-profile-mediaName)# jitter target dynamic-buffer
(config-media-profile-mediaName)# jitter maximum buffer 30000
(config-media-profile-mediaName)# codec-order 1
(config-codec-order-1)# type pcma
(config-codec-order-1)# codec-order 2
(config-codec-order-2)# type g723
(config-codec-order-2)# codec-order 3
(config-codec-order-3)# type g729
(config-codec-order-3)# codec-order 4
(config-codec-order-4)# type pcmu
(config-codec-order-4)# packet-period 20
First check the ONU capabilities before configuring the codec list, because some ONU
models do not support all the codecs listed. There must be 4 codecs configured in a
Media Profile.
When there is no pstn-protocol-variant configured, the ONU must use its internal default.
Hardware restrictions
None.
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
onu-profile profile-name
veip veip-ports
Value: 1
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example (configuring an ONU profile with 4 Ethernet ports and 2 POTS ports):
# config
Entering configuration mode terminal
(config)# profile gpon onu-profile onuProfName
(config-onu-profile-onuProfName)# ethernet 4
(config-onu-profile-onuProfName)# pots 2
# config
Entering configuration mode terminal
(config)# profile gpon onu-profile onuProfName2
(config-onu-profile-onuProfName2)# veip 1
N/A
Hardware restrictions
N/A
Description
The rg-profile (residential gateway) is used to enter in rg-profile mode and manage the
ONU DM984-42x WAN, LAN and WLAN configuration through the OLT. DM985-100 ONU
also supports the rg-profile configuration, but some parameters may not be fully sup-
ported. Check DM985-100 release notes for reference. The no profile gpon rg-profile
command is used to delete a specific RG profile.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
rg-profile profile-name
wan-pppoe-connection connection-name
firewall
Value: None.
fullcone-nat
Value: None.
multicast-proxy { igmp }
Description: Enables IGMP multicast proxy for the PPPoE WAN interface. IGMP
multicast source must be enabled too.
Value: None.
multicast-source { igmp }
Description: Enables IGMP multicast source for the PPPoE WAN interface.
Value: None.
nat
Value: None.
password password
username username
service-name service-name
Value: 1-4094.
Value: 0-7.
Default Value: 0.
wlan wlan-name
Value: wl0 (refers to the physical wlan interface), wl0-vap1 (Virtual ac-
cess point 1), wl0-vap2 (Virtual access point 2), wl0-vap3 (Vir-
tual access point 3).
Description: Enables automatic fill of WLAN interface SSID, which in this case
will be equal to the associated ONU serial number.
Value: None.
wpa-passphrase wpa-passphrase
ipv4 dhcp
Value: a.b.c.d
Value: a.b.c.d
itf-grouping dhcp-server
Value: None.
Description: Starting IP address for the DHCP pool on LAN side. If no value is
specified and the DHCP server is enabled, the default generated
by the ONU will be used.
Value: a.b.c.d
Description: Ending IP address for the DHCP pool on LAN side. If no value is
specified and the DHCP server is enabled, the default generated
by the ONU will be used.
Value: a.b.c.d
itf-grouping igmp-snooping
Value: None.
Value: a.b.c.d
Value: a.b.c.d
Description: Sets the ports that will be members of this interface grouping.
vlan vlan-id
Value: 1-4094.
cos cos
Value: 0-7.
Default Value: 0.
ip-filtering priority
Description: Create an IP filtering rule with the given priority. The highest
priority is 0.
Value: 0-7.
filtering-type
Value: incoming.
action act
Value: permit.
Value: 1-65535.
Value: 1-65535.
Value: 1-65535.
Value: 1-65535.
Value: 1-65535.
Value: 1-65535.
Description: Enables automatic fill of the ONU user (level support or user)
WEB login credential, which in this case will be equal to the
associated ONU serial number.
Value: None.
Description: Set ONU user (level support or user) WEB login credential.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
When associated with an ONU, the OLT will apply all configuration present in the RG pro-
file to specified DM984-42x/DM985-100 ONU, erasing any other WAN configuration, and
their dependencies, made through its WEB interface.
Some parameters can be specified per ONU basis, overriding the values in the RG profile.
See the ‘onu’ command for reference.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon rg-profile MY_PLAN
(config-rg-profile-MY_PLAN)# wan-pppoe-connection pppoe_1
(config-wan-pppoe-connection-pppoe_1)# vlan-mux vlan 100
(config-wan-pppoe-connection-pppoe_1)# nat
(config-wan-pppoe-connection-pppoe_1)# ip-filtering 0 incoming action permit
(config-ip-filtering-0)# match protocol tcp/udp destination-port range start 2000 stop 3000
(config-ip-filtering-0)# itf-grouping
(config-itf-grouping)# ipv4-address 192.168.0.1 netmask 255.255.255.0
(config-itf-grouping)# dhcp-server-address-pool start-address 192.168.0.2 end-address 192.168.0.254
(config-itf-grouping)# ports eth1
(config-itf-grouping)# ports eth2
(config-itf-grouping)# ports eth3
(config-itf-grouping)# ports eth4
(config-itf-grouping)# ports wl0
(config-itf-grouping)# ports wl0-vap1
(config-itf-grouping)# exit
(config-wan-pppoe-connection-pppoe_1)# exit
(config-rg-profile-MY_PLAN)# wlan wl0-vap1
(config-wlan-wl0-vap1)# ssid custom test
(config-wlan-wl0-vap1)# wpa-encryption tkip+aes
(config-wlan-wl0-vap1)# wpa-passphrase teste123
Editing this profile will cause all associated ONUs to be reconfigured causing traffic loss.
If the IP connection is configured for static IP address mode, the static IP address must
be configured in the related ONU override settings.
The ONU has a default interface grouping which will always aggregate all ports and
WANs that are not included in other groupings. IP address for this default grouping is
192.168.0.1 and DHCP server is enabled. As new interface groupings are created, the
ONU will automatically assign IPs 192.168.2.1, 192.168.3.1 and so on, if no custom value
is configured. When configuring the custom IP address of an interface grouping to an IP
192.168.X.X, it is necessary to be aware of possible conflicts with the default grouping,
or with other groupings which don’t have a custom IP configured.
The names of WLAN ports on interface grouping are a little bit different from the ONU
DM984-42X web interface. The WLAN port wl0 is referred to wlan0 and the wl0-vap1 port
is referred to wl0_Guest1. The port wl0-vap1 only can be present on a interface grouping
Hardware restrictions
N/A
Description
The service-profile command is used to create an ONU service profile. This profile config-
ures ONU capability and the parameters related to services. These parameters include
the user’s ONU and VLAN.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
service-profile profile-name
Value: Text.
onu-profile profile-name
Value: Text.
Default
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon service-profile servProfName
(config-service-profile-servProfName)#
Hardware restrictions
N/A
Description
The sip-agent-profile command is used to enter in SIP Agent profile mode and set the
SIP server configuration, such as registrar address, proxy server address and outbound
proxy server address.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
sip-agent-profile expires-timeout
Value: 20-604800
sip-agent-profile sip-agent-profile-name
registrar registrar-address
proxy-server proxy-server-address
outbound-proxy outbound-proxy-address
Default
None.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# config
Hardware restrictions
None.
Description
Defines which OIDs will be available for SNMP monitoring of GPON objects.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
snmp-profile profile-name
if-alias
Value: None
if-name
Value: None
if-type
Value: None
if-descr
Value: None
if-admin-status
Value: None
if-oper-status
Value: None
if-onu-power-tx
Value: None
if-onu-power-rx
Value: None
if-onu-sysuptime
Value: None
statistics-in-octets
Value: None
statistics-in-ucast-pkts
Value: None
statistics-in-multicast-pkts
Value: None
statistics-in-broadcast-pkts
Value: None
statistics-in-discards
Value: None
statistics-in-errors
Value: None
statistics-in-unknown-protos
Value: None
statistics-out-octets
Value: None
statistics-out-ucast-pkts
Value: None
statistics-out-multicast-pkts
Value: None
statistics-out-broadcast-pkts
Value: None
statistics-out-discards
Value: None
statistics-out-errors
Value: None
statistics-in-bw-usage
Value: None
statistics-out-bw-usage
Value: None
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
# config
Entering configuration mode terminal
(config)# profile gpon snmp-profile snmpProfName
(config-snmp-profile-snmpProfName)# if-admin-status
# config
Entering configuration mode terminal
(config)# profile gpon snmp-profile snmpProfName
(config-snmp-profile-snmpProfName)# statistics-in-bw-usage
(config-snmp-profile-snmpProfName)# statistics-out-bw-usage
Some OIDs (such as if-type/if-descr) are enabled by default and cannot be removed from
the profile.
Hardware restrictions
N/A
Description
The tr069-acs-profile command is used to configure parameters for access to TR069 ACS
(Auto Configuration Server). This allows the ONU to be managed and upgraded by a
TR069 ACS. The no profile gpon tr069-acs-profile command is used to delete a specific
TR069 ACS profile.
Supported Platforms
Syntax
url url
username username
password password
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
tr069-acs-profile profile-name
Description: Name of the profile to create. Must be unique within all TR069
profiles. Can have up to 48 characters.
url url
username username
password password
Default
N/A
Command Mode
Configuration mode
History
Release Modification
Usage Guidelines
When associated with an ONU, the OLT will apply all configuration present in the TR069
ACS profile to specified ONU.
Example:
# configure terminal
Entering configuration mode terminal
(config)# profile gpon tr069-acs-profile MY_PROF
(config-rg-profile-MY_PROF)# url http://myacs.com:7547
(config-rg-profile-MY_PROF)# username admin
(config-rg-profile-MY_PROF)# password admin
Editing this profile will cause all associated ONUs to be reconfigured causing traffic loss.
Hardware restrictions
N/A
vlan-mapping
Description
The VLAN-mapping command is part of the service-profile structure and is used to add
VLAN IDs and CoS values to packets.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
name
symmetric
Value: None
ethernet ethernet-ports
veip veip-idx
Value: Number: 1.
match
Description: Parameters after match and before action describe the type
of flow that the rule applies to.
Value: None
Description: CoS value to be matched, or any in case all CoS values apply.
action
Value: None.
Value: None.
Description: New VLAN ID for the VLAN tag, or copy-vlan in case the original
VLAN ID should be kept.
Description: New CoS value for the VLAN tag, or copy-vlan in case the orig-
inal CoS value should be kept.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
5.8 This command supports creating VLAN mapping rules for VEIP.
Usage Guidelines
A range of ports:
To actually apply the VLAN mapping rules, the service-profile must be selected on the
ONU and the interface must be created.
VLAN mapping rules will only be applied to ONUs that configured the service-profile
containing the rules.
A VLAN mapping rule will only be applied if the target interface (Ethernet UNI, VEIP) is
present in the ONU configuration.
Hardware restrictions
N/A
ONU
This topic describes the commands related to ONU such as commands to authenticate
an ONU and configure its UNIs.
Description
Adds, modifies, removes, activates or deactivates an ONU as well as assigns profiles and
configures Ethernet/POTS/VEIP UNI.
Supported Platforms
Syntax
interface gpon <chassis/slot/port> onu onu-id veip veip-port [ native vlan { vlan-
id vlan-val | cos cos-val } ]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
onu onu-id
Value: 0-127
name onu-name
serial-number onu-name
password password
service-profile service-profile-name
line-profile line-profile-name
rg-profile rg-profile-name
rg-profile-override-settings
Value: N/A.
wan-pppoe-connection pppoe-connection-name
username username
password password
wan-ip-connection ip-connection-name
Value: a.b.c.d/x
Value: a.b.c.d
wlan wlan-name
wpa-passphrase wpa-passphrase
Description: Override WPA passphrase of the WLAN interface inside the re-
lated rg-profile.
ssid ssid
Description: Override SSID name of the WLAN interface inside the related
rg-profile.
ethernet ethernet-port
Value: 1-4
Value: 1-4094
Value: 0-7
Default Value: 0
native downstream-mode
negotiation
Value: None
shutdown
Value: None
snmp all
Description: Enables SNMP monitoring for the ONU. This command enables
the ONU to report all available OIDs, including Ethernet UNI
counters.
Value: None
snmp real-time
Description: Enables real-time SNMP monitoring for the ONU Ethernet UNI
counters.
Value: None
mac-limit mac-limit-value
Value: 1-255
description
Description: Set the interface description or alias. Valid characters are A-Z,
a-z, 0-9 and - _ / + * @
Value: 1-4094
Value: 0-7
Description: Configures an IP address for the ONU. The subnet mask prefix
must be passed.
Value: a.b.c.d/x
Value: a.b.c.d
Value: 1-4094
Value: 0-7
pots pots-port
Value: 1-4
display-name display-name
username user-name
Description: Indicates the user name for the SIP user authentication.
password password
user-part-aor user-part-aor
media-profile media-profile-name
sip-agent-profile sip-agent-profile-name
veip veip-port
Value: 1.
Value: 1-4094
Value: 0-7
Default Value: 0
tr069-acs-profile tr069-acs-profile-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
2.4 Command ‘snmp profile’ and ‘snmp real-time’ options were added.
Usage Guidelines
To set interface gpon onu parameters is necessary to enter in the interface gpon onu
menu.
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu 1
(config-gpon-onu-1)# ethernet 1
(config-ethernet-1)# description test_interface_name
To configure a RG profile and override SSID and wpa-passphrase for the WLAN interface:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu 1
(config-gpon-onu-1)# rg-profile MY_RG_PROFILE
(config-gpon-onu-1)# rg-profile-override-settings
(config-gpon-onu-1-rg-...)# wlan wl0 wpa-passphrase MY_PASSWORD ssid MY_SSID
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu 1
(config-gpon-onu-1)# tr069-acs-profile MY_TR069_PROFILE
Some third-party ONUs may not support the use of a native VLAN on the Ethernet UNI.
As a workaround the service-port may be configured to work as a native VLAN (match
“any” plus action “add” operation).
Configuring a serial-number and/or password must match with gpon authentication method
command defined configuration.
Binding a valid SIP agent profile is mandatory when configuring ONU POTS interfaces.
Even if SNMP (all or profile) configured, Ethernet UNI SNMP counters are published each
15 minutes.
If Ethernet UNI SNMP counters needs to be updated more frequently, turn on real-time
update.
When real-time SNMP update is enabled, Ethernet UNI SNMP counters are published
continuously, being updated with a higher frequency. This frequency is inversely propor-
tional to the number of ONUs configured and the number of ONUs with real-time update
enabled.
Up to 32 ONUs can have real-time SNMP monitoring turned on globally.
It is recommended that the polling interval by the external monitoring tool should be 5
minutes or higher.
In order to monitor SNMP OIDs for a given Ethernet UNI, an entry must be created with
the ethernet ethernet-port command.
RG profile will only work for DM984-42x and DM985-100 ONU models.
When overriding RG profile settings, only the selected parameters will be overridden
while others will come from the associated RG profile.
If the RG profile contains IP connections with static IP address mode, the static IP ad-
dress for each connection must be configured in the override settings.
When using a TR069 ACS profile, ensure that the ONU has an IP path already config-
ured for this service.
Hardware restrictions
None
onu-auth-method
Description
Defines the method that will be used to authenticate an ONU. This configuration is ap-
plied to the gpon-card as a whole, affecting all its ONUs.
Supported Platforms
Syntax
Parameters
serial-number
Value: None
password
Value: None
serial-number-and-password
Value: None
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# gpon 1/1
(config-gpon-1/1)# onu-auth-method password
None
Hardware restrictions
N/A
onu-enable
Description
Supported Platforms
Syntax
Parameters
onu-enable all
Value: None
onu-enable serial-number
Description: Only the ONU with the given serial number will be enabled.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu-enable all
Depending on the reason why the ONU was disabled, it may not become enabled when
this command is issued. This command merely attempts to enable an ONU.
Hardware restrictions
N/A
onu-force-status-update
Description
Supported Platforms
Syntax
Parameters
onu onu-id
Value: A registered ONU ID. See command ‘onu’ for range information.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
In scenarios with hundreds of ONUs, status polling can take a long time to update a given
ONU status. This command can be used to force a particular ONU to update its status.
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu-force-status-update onu 1
In the example above, execute “show interface onu 1/1/1 onu 1” to check the updated
status.
It is expected that the ONU status might be updated a few seconds after the command
is executed.
Hardware restrictions
N/A
onu-reset
Description
Supported Platforms
Syntax
Parameters
onu onu-id
Value: A registered ONU ID. See command ‘onu’ for range information.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu-reset onu 1
The refered ONU will be reset, affecting ongoing data traffic. Only works on configured
and connected ONUs.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
Value: chassis/slot/port
onu onu-id
Value: 0-127
Default
None
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
Use the cancel command to cancel the firmware installation in one or in all ONUs in a
given gpon interface. Example:
# configure terminal
Entering configuration mode terminal
(config)# request firmware onu cancel interface gpon 1/1/1 onu 1
None
Hardware restrictions
None
Description
Installs the firmware image to an ONU. For in-band-upgrade option, only DM984-42x
ONU model is currently supported.
Supported Platforms
Syntax
Parameters
filename
Value: chassis/slot/port
onu onu-id
Value: 0-127
in-band-upgrade
Value: None
model onu-model
Value: dm984-42x
ip-address ipv4-address
Value: a.b.c.d
username onu-username
password onu-password
Default
None
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Config
History
Release Modification
Usage Guidelines
Use install filename interface command to install the firmware at some ONU con-
nected to a GPON interface. For this option, use the cancel command to stop the oper-
ation.
Example:
Examples:
Succeeded operation:
# request firmware onu install fwName in-band-upgrade model dm984-42x
ip-address 192.168.10.10 username anon password rightpass
in-band-upgrade succeeded for 192.168.10.10
Failed operation:
# request firmware onu install fwName in-band-upgrade model dm984-42x
ip-address 192.168.10.10 username anon password wrongpass
in-band-upgrade FAILED for 192.168.10.10 (not authorized)
When upgrading using the interface operation mode, it is the operator responsibil-
ity to check if the selected ONU (or ONUs) is (are) compatible with the selected ONU
firmware file. The OLT will not check this compatibility, even though most of ONU models
have the capability of performing this function. In these cases, ONU firmware transfer
will fail and the ONU will remain in the previous state.
When upgrading using the in-band-upgrade operation mode, the addressed ONU’s
model will be read and compared with the selected model in the command. In case
of mismatch, the command will be refused.
Only one firmware file can be used at a time globally in the equipment. That is, if the
operator is upgrading a given ONU model, another upgrade with a different firmware file
cannot happen while the all other transfers finish. In other words, once started one or
more ONU firmware file transfers, the operator needs to wait for all of them to complete
in order to start a new one with a different ONU firmware file.
Hardware restrictions
None
rg-reprovision
Description
Supported Platforms
Syntax
rg-reprovision
Parameters
N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu 1
(config-gpon-onu-1)# rg-reprovision
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1
(config-gpon-1/1/1)# onu *
(config-gpon-onu-*)# rg-reprovision
Example:
# configure terminal
Entering configuration mode terminal
(config)# interface gpon 1/1/1-8
(config-gpon-1/1/1-8)# onu *
(config-gpon-onu-*)# rg-reprovision
This command will reprovision the ONU and configurations made via the ONU web inter-
face might be erased.
Hardware restrictions
N/A
show firmware
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
onu
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
chassis/slot/port
onu onu-id
version
Value: N/A
optical-info
Value: N/A
brief
Value: N/A
Output Terms
Output Description
Shows the timestamp of the last time the selected ONU has its status
Last updated
published to the database.
ID ID of the ONU.
Distance Approximate ONU logical distance (in kilometers) from the OLT.
Output Description
IPv4 default
ONU IP-Host IPv4 default gateway.
gateway
RG One Shot
Indicates the time that RG Profile was provisioned at ONU.
Provision
Shows if the ONU has snmp enabled and the SNMP profile when ap-
SNMP
plicable.
Allocated
Type and amount of bandwidth allocated for the ONU.
bandwidth
Output Description
Software Download
ONU firmware upgrade state.
State
Rx Optical Power
Rx power level in dBms.
-dBm-
Tx Optical Power
Tx power level in dBms.
-dBm-
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Release Modification
Usage Guidelines
Itf ONU ID Serial Number Oper State Software Download State Name
-------- ------ ------------- ---------- -------------------------- ---------------------------
1/1/1 1 CIGG12345671 Up Complete ONU1
1/1/1 2 CIGG12345672 Up Complete ONU2
1/1/3 1 CIGG12345673 Up Complete ONU3
1/1/4 1 CIGG12345674 Up Complete ONU4
1/1/4 5 CIGG12345675 Up Complete ONU5
It is not supported to use a key pattern in both ONU and gpon interface IDs (
show interface gpon * onu *
).
It is not supported to use ONU ID key pattern together with brief/optical-info/version
options (
show interface gpon 1/1/1 onu * brief
).
In some scenarios, the ONU logical distance cannot be retrieved correctly and it will be
shown as N/A. This behavior can happen specially when the configured PON link max-
imum distance is close to the ONU logical distance, for example, when the ONU is at
20km distant and PON link maximum distance is configured to 21km.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
chassis/slot/port
onu-id
ethernet-port
brief
statistics
detail
Output Terms
Output Description
Physical interface
Name and status of the GPON interface.
Status Negotiation
Negotiated Speed and Duplex.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
When using detail option, it will override other show options passed. For example, if the
operator runs “show interface gpon 1/1/1 onu 1 ethernet 1 brief detail”, “show interface
gpon 1/1/1 onu 1 ethernet 1 statistics detail” or “show interface gpon 1/1/1 onu 1 ether-
net 1 brief detail statistics” only detail option will be shown.
The same way, statistics option will override the default “show interface gpon 1/1/1 onu
1 ethernet 1” or it will have precedence over brief option in “show interface gpon 1/1/1
onu 1 ethernet 1 brief statistics” outputs as well.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
show interface gpon chassis/slot/port onu [ onu-id ] gem [ gem-id ] [ brief | statistics
]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
chassis/slot/port
onu-id
gem-id
brief
statistics
Output Terms
Output Description
Operation status
Operational status.
is
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
1.4 The the maximum GEM ID value was changed from 40 to 16.
Usage Guidelines
It is not supported to use a key pattern in gpon interface IDs. For example:
Hardware restrictions
N/A
MANAGEMENT
This topic describes the commands related to use of management clients such as com-
mands to open a telnet or SSH connection to a remote device.
assistant-task
Description
Supported Platforms
Syntax
assistant-task task-name action watch cli-cmd cli-cmd match match cli-file file-
name regex regex [disable-after-match]
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
task-name
Value: N/A
cli-file file-name
Description: File containing CLI commands. Special characters are not al-
lowed in the file or in the file name. Must be an ASCII file.
enabled
Description: Enables the assistant-task. This parameter takes effect only for
scheduled actions.
Value: N/A
disabled
Value: N/A
schedule recursive
Value: N/A
schedule once
Value: N/A
day day
Value: 1-31
hour hour
Value: 0-23
Default Value: 0
minute minute
Value: 0-59
Default Value: 0
month month
Value: 1-12
weekday weekday
second second
Value: 0-59
Default Value: 0
run-now
Value: N/A
watch
Value: N/A
cli-cmd cli-cmd
match match
Description: Match and its related actions to be executed when a regex pat-
tern is found.
regex regex
disable-after-match
Value: N/A
Default
N/A
Command Mode
Configuration mode
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Example:
First of all you must create a CLI command file and transfer it to the equipment. Al-
ternatively, it is possible to edit or create a new file using the ‘file edit <filename>’
command. Remember that the ‘config’ command must be included in the file to enter
the configure mode.
When saving files, use the ‘save overwrite’ option to avoid being asked about existing
files. The example below shows a file that can be used to save a configuration backup
and send it to a tftp server.
# file show backup.cli
show running-config | save overwrite backup.cfg
copy file backup.cfg tftp://10.1.1.1
#
Assistant task runs in non-interactive mode, so there is no need to include the confir-
mation response in the command file. Older DmOS versions, such as 4.10.2, required
the confirmation response to be included. This will not work anymore. Operators need to
remove all confirmation responses from existing cli command files, using file edit com-
mand, otherwise the assistant task may return a failure during its execution.
Configure a task to be run from Monday to Friday, except Thursday, at 8am and 6pm. It
is possible to provide a combination of range and list:
# config
Entering configuration mode terminal
(config)# assistant-task backup
(config-assistant-task-backup)# action cli-file backup.cli
(config-assistant-task-backup)# schedule recursive hour 8,18
(config-assistant-task-backup)# schedule recursive weekday 1-3,5
(config)# commit
Commit complete.
(config)# commit
Commit complete.
Run a configured task immediately to test if it is running correctly. The run-now com-
mand will work even if the task is disabled. After executing this command, use the show
assistant-task command to see the command result.
# config
Entering configuration mode terminal
(config)# assistant-task backup
(config-assistant-task-backup)# action cli-file backup.cli
(config-assistant-task-backup)# schedule recursive day 1
(config-assistant-task-backup)# commit
Commit complete.
(config-assistant-task-backup)# run-now
(config-assistant-task-backup)# top; exit
# show assistant-task backup last-success output
Last successful execution - Thu Aug 29 09:23:35 -03 2019
<
Transfer complete.
>
It is possible to inspect currently running tasks by using the show command. Running
tasks can also be interrupted by disabling them:
# show assistant-task
TASK
NAME LAST START LAST FAILURE LAST SUCCESS STATUS
--------------------------------------------------------------------------------------------
backup Tue Aug 20 23:00:00 -03 2019 - - running
# config
(config)# assistant-task backup
(config-assistant-task-backup)# disabled
(config-assistant-task-backup)# commit
(config-assistant-task-backup)# top ; exit
# show assistant-task
TASK
NAME LAST START LAST FAILURE LAST SUCCESS STATUS
--------------------------------------------------------------------------------------------
backup Tue Aug 20 23:00:00 -03 2019 - - disabled
Configure a task to be run every second (no time/date specified) checking a link health
and when a problem occurs changes the link interface.
# file show connectTo1.cli
config
no dot1q vlan 500
dot1q vlan 500
no interface 1/1/10
interface 1/1/9
commit
top
exit
#
# file show connectTo2.cli
config
no dot1q vlan 500
dot1q vlan 500
no interface 1/1/9
interface 1/1/10
commit
top
exit
#
# config
Entering configuration mode terminal
(config)# assistant-task vlanSwitch
(config-assistant-task-vlanSwitch)# schedule recursive minute * hour * second 0-59
(config-assistant-task-vlanSwitch)# action watch cli-cmd "ping 10.1.1.2 | include
\"100% packet l\" | count ; show running-config dot1q vlan 500 |
include ethernet ;"
(config-assistant-task-vlanSwitch)# action watch match M0
(config-assistant-task-match-M0)# cli-file connectTo1.cli
(config-assistant-task-match-M0)# regex ".*Count: 1 lines.*.*1/1/10"
(config-assistant-task-match-M0)# exit
(config-assistant-task-vlanSwitch)# action watch match M1
(config-assistant-task-match-M1)# cli-file connectTo2.cli
(config-assistant-task-match-M1)# regex ".*Count: 1 lines.*.*1/1/9"
(config-assistant-task-match-M1)# exit
(config-assistant-task-vlanSwitch)# commit
Commit complete.
Schedule example to run an assistant task at 00:00 on the first day of every month:
(config)# assistant-task example
(config-assistant-task-example)# schedule recursive minute 0 hour 0 day 1 month *
Commands executed by the assistant-task feature are executed by special users called
batch_<task_name>. This user may appear in logs depending on the commands present
in the CLI file.
Tasks configured to run only once will be automatically disabled after executed. It is
possible to reschedule it to run at a later date by enabling it again.
ATTENTION: When saving files in the CLI script, be careful not to let them grow indefi-
nitely to avoid using all available memory. Use copy-file to transfer it to another machine
Hardware restrictions
N/A
logout
Description
Terminates a specific session or all CLI and NETCONF sessions of a specific user. If no
session or user is specified, the current session is terminated. If the terminated session
held the configure exclusive lock, it will be released.
Supported Platforms
Syntax
Parameters
session session-id
Value: Integer value representing the session ID, which can be ob-
tained by using command “who” or by pressing <TAB>.
user user-name
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Before using this command, use command “who” to check the existing sessions. The
session marked with a “*" is the current one.
Example:
Hardware restrictions
N/A
show assistant-task
Description
Supported Platforms
Syntax
Parameters
task-name
last-start
Value: N/A
last-failure
Value: N/A
last-success
Value: N/A
task-status
output
Description: Shows the task output between “< >”(may be empty depend-
ing on the executed task).
Value: N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The examples below show how to use the command show assistant-task.
Example:
# show assistant-task
TASK
NAME LAST START LAST FAILURE LAST SUCCESS STATUS
---------------------------------------------------------------------------------------------
task_1 Fri Aug 20 08:46:00 -03 2019 Tue Aug 20 10:00:15 -03 2019 - idle
task_2 Fri Aug 21 06:11:00 -03 2019 - - running
N/A
Hardware restrictions
N/A
show ssh-server
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
public-key
Value: No value.
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
ssh
Description
“SSH” is an utility whose purpose is to allow the user to connect to a remote network
host or device through a secure encrypted connection, after the connection has been
established it is possible to execute commands on the remote destination host or device.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
username@
Value: N/A
ipv4-address
Value: N/A
port port-number
Value: 1-65535
Default Value: 22
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The following example shows how to use the ssh command with all options:
The following example shows how to use the ssh command without server port, it will
use the default value (22):
The following example uses only ip address, it will use the logged user and the default
port:
N/A
Hardware restrictions
N/A
ssh-server
Description
Secure shell (SSH) server, for secure access from remote hosts.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
type
size
Description: Specifies the size of key to create. The option only present in
keys of the type rsa.
Value: 1024-2048
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
Hardware restrictions
N/A
ssh-server
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
legacy-support
Description: Support for ssh clients running openssh versions older than 7.0.
Value: N/A
max-connections max-connections-number
Description: Defines the maximum number of SSH connections via CLI for
each address family. NETCONF access connections are handled
separately.
Value: 1-16
Default Value: 8
port port-number
Value: 22 | 1024-65535
Default Value: 22
Default
N/A.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
1.8.2 Added support for ssh clients running openssh versions older than 7.0.
Usage Guidelines
Example:
Example:
This example shows how to return the number of ssh max-connection to the default
value.
(config)# no ssh-server max-connections
(config)# commit
Commit complete.
Example:
This example shows how to return the port number of ssh to the default value.
(config)# no ssh-server port
(config)# commit
The following warnings were generated:
’ssh-server port’: New SSH connections must use the configured port.
Proceed? [yes,no] yes
Commit complete.
When legacy-support is enabled, a deprecated key exchange algorithm will be used. This
can bring security vulnerabilities.
Hardware restrictions
None.
telnet
Description
“TELNET” is a network protocol which uses TCP to stablish a connection with the desti-
nation host. Through TELNET it is possible to run programs, transmit data and execute
many other remote administration tasks such as changing various settings on a device.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
host
Value: None.
port port-number
Default Value: 23
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The following example shows how to use the telnet command with all options:
The following example shows how to use the telnet command without server port, it
will use the default value (23):
N/A
Hardware restrictions
N/A
telnet-server
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
enabled
Value: N/A
disabled
Value: N/A
max-connections max-connections-number
Description: Defines the maximum number of Telnet connections via CLI for
each address family.
Value: 1-16
Default Value: 8
port port-number
Value: 23 | 1024-65535
Default Value: 23
Default
Disabled.
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Enable example:
# config
(config)# telnet-server enabled
(config)# commit
Commit complete.
Disable example:
# config
(config)# telnet-server disabled
(config)# commit
Commit complete.
This example shows how to return the number of telnet max-connection to the default
value.
(config)# no telnet-server max-connections
(config)# commit
Commit complete.
This example shows how to return the port number of telnet to the default value.
DM4400(config)# no telnet-server port
DM4400(config)# Commit
Commit complete.
None.
Hardware restrictions
None.
who
Description
Supported Platforms
Syntax
who
Parameters
N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
(config)# do who
Session User Context From Proto Date Mode
27 admin cli 192.168.0.10 tcp 20:41:25 config-exclusive
26 admin netconf 192.168.0.26 ssh 20:55:29 operational
*25 admin cli 127.0.0.1 console 20:41:23 config-terminal
N/A
Hardware restrictions
N/A
SYSTEM
This topic describes the commands related to the device management such as com-
mands of reboot and stacking.
card-model
Description
Supported Platforms
Syntax
Parameters
card-model card_model
Description: Identifies the model of the card that will be used by DmOS.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
The DM4270 has a flexible interface set composed of 24 10 Gbps Ethernet interfaces
and four interfaces that can be used in two physical configurations:
- three 100 Gbps interfaces;
- four 40 Gbps interfaces.
This design results in the two supported card-models: 24XS+3CX and 24XS+4QX.
The “card-model” command selects which interface set will be used and takes effect af-
ter the factory configuration is automatically loaded and the device is rebooted.
This command will cause the factory-config to be loaded and will reboot the device im-
mediately. Be aware that this operation will cause loss of remote management access.
Hardware restrictions
N/A
clear log
Description
Supported Platforms
Syntax
clear log
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
N/A
N/A
Hardware restrictions
N/A
log
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Description: This parameter allows you to set the minimum log level to be
persisted.
Value: N/A
syslog ip-address
vrf vrf-name
Description: (Optional) Specifies the name of VRF which the syslog server
can be reached.
Value: String.
port port
Description: (Optional) Specifies the port that syslog server is listening for
UDP syslog messages.
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Enable syslog to server 172.22.110.101, associate to vrf green and configure a UDP port
# config
(config)# vrf green
(config-vrf-green)# dot1q vlan 100
(config-vlan-100)# interface l3 l3
(config-l3-l3)# lower-layer-if vlan 100
(config-l3-l3)# ipv4 address 172.22.110.10/24
(config-l3-l3)# vrf green
(config-l3-l3)# log syslog 172.22.110.101 vrf green port 5000
(config)# commit
Commit complete.
N/A
Hardware restrictions
N/A
reboot
Description
Supported Platforms
Syntax
reboot
Parameters
N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Release Modification
Usage Guidelines
This command is to be used when the user wants to restart the entire system. For restart-
ing the system in cases when the system can not be restarted using this command, see
the reboot-forced command.
This command is safe because it only restarts the system after terminating its activities
that includes storing the remaining data and unmounting the partitions.
None
Hardware restrictions
None
reboot-forced
Description
Supported Platforms
Syntax
reboot-forced
Parameters
N/A
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Release Modification
Usage Guidelines
This command is to be used when the user wants to restart the system despite any soft-
ware hang problem that may happen, which would prevent the system of being restarted
using the reboot command.
It may cause permanent loss of configuration or other data, because a critical operation
can be interrupted. It can happen if the equipment was restarted during a configuration
commit or firmware activation, for example. Use only if the reboot command fails.
Hardware restrictions
None
show inventory
Description
This command displays the system inventory information, including the part number,
hardware version, serial number and other relevant information.
Supported Platforms
Syntax
Parameters
chassis chassis_id
Value: 1
brief
Value: N/A
factory-codes
Value: N/A
macs
Description: Shows the MAC addresses of all ports of the chassis or a specific
card.
Value: N/A
transceivers
Value: N/A
slot slot_id
port port_type
Description: Identifies the desired type of port present on the card. If the
value of this parameter is ‘*’ or ‘ ’, a list of all ports of the card
will be shown. This will be dependent on the product being
managed. The values below are for Dm4610.
port_type port_id
Value: 1-12
Output Terms
Output Description
Port type Port type of the interface, which may be Electrical or Transceiver
Transceiver
Presence and inventory information of the transceiver
information
Output Description
Fiber Type Transceiver supported fiber type, e.g., Single Mode, Multimode.
Ethernet standards
Transceiver supportted ethernet standards
Digital
Diagnostics Transceiver digital diagnostics thresholds
thresholds
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
The user can display information about chassis, slots, ports and transceivers. Please see
below examples of usage for each type of inventory information in display.
Hardware restrictions
N/A
show log
Description
Supported Platforms
Syntax
Parameters
component {components}*
Value: {components}*
severity {severities}*
Description: If this filter is used, only messages generated with the speci-
fied severities will be displayed. More than one severity can be
filtered at the same time.
tail {number_of_logs}
Value: 1-65535.
Default Value: 10
Output Terms
Output Description
Time of log entry in the format: hh:mm:ss.ddd (3 digits for the deci-
Time
mal fraction of a second).
An identifier for the functionality which the log message refers to.
Component
Each log Component comprises a set of Message Codes.
The name of the operational system process that generated the log
ProcessName
message. It may not be unique.
The ID of the operational system process that generated the log mes-
PID sage. It is unique inside the corresponding slot. It may not be unique
across a multi-CPU system.
The log message itself, which may contain fixed and variable parts,
Text
describing an event.
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
New format for logs output. Added MessageCode, ProcessName and PID
1.8
fields.
1.12 Added the parameter ‘tail’ that allows to show only the last logs.
Usage Guidelines
Card inserted in slot 1/PSU1 (model: Not supported, serial number: 3047195)
2015-07-23 00:02:15.914 : 1/1 : <Notice> %CARDMGR-CARD_INSERTED : card-mgr[2032] :
Card inserted in slot 1/FAN (model: DM4610 FAN, serial number: Not available)
2015-07-23 00:05:36.545 : 1/1 : <Info> %AAA-GROUP_ASSIGN : authenticationd[2060] :
User [admin]: Was assigned to groups: admin.
The use of show log or another verbose command under serial interface may cause
the session to become unresponsive to user intervention (until the command finishes its
execution). Consider this before executing the respective command.
Hardware restrictions
N/A
show platform
Description
This command is used to show information about the system cards, like firmware version
and status.
Supported Platforms
Syntax
Parameters
chassis chassis_id
Description: Chassis identifier. If the value of this parameter is ‘*’ a list of all
present chassis will be shown. Currently only one chassis_id is
supported.
Value: 1
detail
Value: N/A
slot slot_id
Output Terms
Output Description
Default
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
1.2 The command was changed and the detail option was introduced.
Usage Guidelines
The user can display status, role and firmware version information about all chassis and
cards present at the system. Some of the information for it can be found at other com-
mands, like show inventory and show firmware, so this is the place to summarize it and
display it in a concise form.
Hardware restrictions
N/A
Description
Supported Platforms
Syntax
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
This command should be used when the user wants to identify the reason of the last
(most recent) system reboot.
This information remains available until the next reboot, and then it gets overwritten.
This status is logged in user logs, and is available through SNMP.
None
Hardware restrictions
None
DHCP
This topic describes the commands related to management of DHCP Server and Relay
such as commands to configure DHCP Pools and timers or to inspect the devices con-
nected to local server.
dhcp l2-relay
Description
DHCP L2 Relay is responsible for the insertion of DHCP information option 82 field as
specified in Section 3.9.1/TR-101 and 5.7/TR-156.
This function only works for packets switched among GPON service-ports and uplink eth-
ernet ports. Packets switched among ethernet ports are forwarded transparently.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
vlan vlan-id
Value: 1-4094
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
# config
(config)# dhcp l2-relay vlan 15
(config)# commit
Commit complete.
# config
(config)# dhcp l2-relay vlan 1-10
(config)# commit
Commit complete.
Usage example of configuring a list containing the VLAN IDs 1, 10 and 15:
# config
(config)# dhcp relay vlan 1,10,15
(config)# commit
Commit complete.
For backward compability purposes, ‘dhcp relay vlan’ command is mapped to ‘dhcp l2-
relay vlan’.
Avoid setting dhcp l2-relay to a VLAN configured as ‘service vlan type tls’, since it will
disable DHCP traffic inspection.
When DHCP relay is turned on for a given VLAN, it monitors for DHCP packets of all
service-ports running over this VLAN.
After the DHCP session is properly established, a filter is installed at HW level to allow
traffic on the respective service-port for the particular assigned IPv4 address.
If there is no renew within the assigned lease time, the filter is removed, blocking all user
traffic for the particular service-port.
DHCP relay supports only DHCPv4. DHCPv6 packets are forwarded transparently without
information option insertion.
Server DHCP packets (such as DHCPACK) received on service-ports are silent discarded.
DHCP L2 relay inserts information option 82 with suboption 1 and suboption 2, with
the following content as defined in R-127/TR-156:
1) Suboption 1 - Agent Circuit ID:
<hostname> eth <slot>/<pon-id>/<onu-id>/0/<gem-id>:<vlan-id>
Example for VLAN 333, gem 2, onu 55, PON link 1/1/3:
DM4610 eth 1/3/55/0/2:333
2) Suboption 2 - Remote Circuit ID:
Contains the ONU name configured under the ONU configuration path.
Hardware restrictions
N/A
dhcp relay
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
instance-name
Description: Specifies a list of DHCP servers that will be used by the DHCP
relay agent to forward DHCP client messages. Up to 16 DHCP
server IPv4 addresses can be specified.
interface interface-name
information check
Description: If enabled, DHCP Relay will check for a valid option 82 coming
from DHCP server packets and drop them in case they don’t
contain an option 82.
This configuration is valid only for drop and replace information
policies and when information option is enabled. When informa-
tion policy is set to keep mode, check configuration is ignored,
that is, no verification is performed.
Value: N/A
information option
Description: When enabled, instructs the DHCP Relay agent to add DHCP op-
tion 82 to DHCP client packets. DHCP relay agent will strip off
option 82 from packets arriving from the DHCP server before
sending them back to the user side.
Option 82 circuit-ID is filled with the physical interface short
name from which the DHCP client packet arrived plus the VLAN
information.
That is, circuit-ID will have the format <itf-name>:<vlan-id>,
for example “1ge-1/1/1:4012”, “10ge-1/1/1:4012”, “40ge-1/1/1:4012”,
“100ge-1/1/1:4012”.
Option 82 remote-ID is always equal to the in-band manage-
ment MAC/hardware address of the switch.
Value: N/A
information trust-all
Description: Instructs the DHCP relay agent to trust DHCP client packets con-
taining information option 82 but without GIADDR set.
Value: N/A
information policy
Description: Configures the information option 82 strategy for the DHCP re-
lay agent instance.
Policy behavior:
keep:
replace:
drop:
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a DHCP Relay for VLAN 200 relaying client requests
to VLAN 300 with DHCP option 82 turned on.
(config)# dot1q vlan 200
(config-vlan-200)# interface gigabit-ethernet-1/1/1-24
(config-dot1q-interface-gigabit-ethernet-1/1/1-24)# top
(config)# dot1q vlan 300
(config-vlan-300)# interface ten-gigabit-ethernet-1/1/1-2
(config-dot1q-interface-ten-gigabit-ethernet-1/1/1-2)# top
(config)# interface l3 itf-vlan200
(config-l3-itf-vlan200)# ipv4 address 192.168.1.25/24
(config-l3-itf-vlan200)# lower-layer-if vlan 200
(config-l3-itf-vlan200)# top
(config)# interface l3 itf-vlan300
(config-l3-itf-vlan300)# ipv4 address 10.1.1.25/24
(config-l3-itf-vlan300)# lower-layer-if vlan 300
(config-l3-itf-vlan300)# top
(config)# dhcp relay test
(dhcp-relay-test)# server ipv4 10.1.1.100
(config-ipv4-10.1.1.100)# exit
(dhcp-relay-test)# information option
(dhcp-relay-test)# interface l3-itf-vlan200
(config-interface-l3-itf-vlan200)# exit
Following the settings above, this configuration shows how to configure a switch to relay
DHCP client messages with VLAN 200 coming from an OLT with DHCP option 82 relay
agent turned on.
(config)# dhcp relay test
(dhcp-relay-test)# information policy keep
(dhcp-relay-test)# information trust-all
The maximum number of DHCP relay instances will be limited to the maximum L3 inter-
faces allowed.
In scenarios with a very high load of DHCP messages, the system can experience an
increase of CPU usage for a period of time until DHCP sessions are established.
It is not possible to set a specific source IP or source interface to be used to send relayed
packets to the DHCP server. DmOS will set the source IP address of the interface from
which the target network is reachable.
Information option is filled with the physical interface name, regardless this interface is
a part of a link aggregation or not.
For platforms that have service vlan configuration (such as OLTs), DHCP relay cannot be
turned on for a TLS service vlan.
Hardware restrictions
N/A
Description
Configure interface specific settings related to the DHCP Relay Agent function.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
if-option interface-name
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure a DHCP Relay for VLAN 200 relaying client re-
quests to VLAN 300 with DHCP option 82 turned on. For gigabit-ethernet-1/1/1, interface
is configured as trusted and with keep information policy. This configuration can be used
to relay DHCP client messages coming from an OLT with DHCP option 82 relay agent
turned on which is connected to gigabit-ethernet-1/1/1.
(config)# dot1q vlan 200
(config-vlan-200)# interface gigabit-ethernet-1/1/1-24
(config-dot1q-interface-gigabit-ethernet-1/1/1-24)# top
(config)# dot1q vlan 300
(config-vlan-300)# interface ten-gigabit-ethernet-1/1/1-2
(config-dot1q-interface-ten-gigabit-ethernet-1/1/1-2)# top
(config)# interface l3 itf-vlan200
(config-l3-itf-vlan200)# ipv4 address 192.168.1.25/24
(config-l3-itf-vlan200)# lower-layer-if vlan 200
(config-l3-itf-vlan200)# top
(config)# interface l3 itf-vlan300
(config-l3-itf-vlan300)# ipv4 address 10.1.1.25/24
(config-l3-itf-vlan300)# lower-layer-if vlan 300
(config-l3-itf-vlan300)# top
(config)# dhcp relay test
(dhcp-relay-test)# server ipv4 10.1.1.100
(config-ipv4-10.1.1.100)# exit
(dhcp-relay-test)# information option
(dhcp-relay-test)# interface l3-itf-vlan200
(config-interface-l3-itf-vlan200)# exit
(config-relay-tste)# if-option gigabit-ethernet-1/1/1
(config-if-option-gigabit-ethernet-1/1/1)# information option
(config-if-option-gigabit-ethernet-1/1/1)# information policy keep
(config-if-option-gigabit-ethernet-1/1/1)# information trust-all
(config-if-option-gigabit-ethernet-1/1/1)# exit
N/A
Hardware restrictions
N/A
PPP
This topic describes the commands related to management of PPP services such as com-
mands to configure PPPoE or PPP CHAP.
intermediate-agent Chassi/Slot/Port
Description
Supported Platforms
Syntax
intermediate-agent Chassi/Slot/Port
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Chassi/Slot/Port
Value: 1/1/1
Output Terms
Output Description
None None.
Default
Command Mode
Configuration mode
Required Privileges
History
Release Modification
Usage Guidelines
None
None
Hardware restrictions
None
pppoe
Description
This module contains definitions for the PPPoE(Point-to-Point Protocol over Ethernet)
Supported Platforms
Syntax
pppoe
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
None
Description: None
Value: None
Output Terms
Output Description
None None.
Default
Command Mode
Configuration mode
Required Privileges
History
Release Modification
Usage Guidelines
None
None
Hardware restrictions
None
Description
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
Chassi/Slot/Port
Value: 1/1/1
Output Terms
Output Description
Default
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
History
Release Modification
Usage Guidelines
None
None
Hardware restrictions
None
ENVIRONMENT
show environment
Description
Supported Platforms
Syntax
Parameters
chassis_id
Value: 1
slot_id
Value: 1 or FAN
Output Description
Chassis/Slot/Id Indicates the physical location of the sensor inside the equipment.
Chassis/Slot/Fan-ID
Indicates the physical location of the fan inside the equipment.
Indicates the current status of the measured fan (NORMAL for ade-
quate operation, LOW when its speed is lower than expected for ad-
Fan Status
equate operation, ERROR when is not possible to read the tachome-
ter’s value and FAIL when the fan status reports a failure).
Indicates the current status of the PSUs (OK for adequate operation,
POWER INPUT FAILURE when there is no external power, FUSE FAIL-
PSU Status
URE when the Fuse is blown, and ERROR when is not possible to read
the PSU status)
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This command is available when there are sensors or fans at hardware. Use slot param-
eter to filter the output or let unspecified slots to see all cards info.
Example:
Keep the fans module clear for the proper air flow.
Keep the air filter of the fans module clean.
Hardware restrictions
Description
Shows the status, digital diagnostics and basic information of all present transceivers.
Supported Platforms
Syntax
Parameters
interface_type
interface_id
Value: chassis/slot/port
digital-diagnostics
Value: N/A
status
Value: N/A
Output Terms
Output Description
Alarm Thresholds Range in which data values can vary before alarm
Warning Thresholds
Range in which data values can vary before warning
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Examples:
-----------------------------------------------------------------------------
gpon 1/1/2 | 41.64 C | 3.27 V | 0.0 mA |-39.99 dBm | 8.15 dBm
gpon 1/1/8 | 36.24 C | 3.29 V | 0.0 mA | 8.16 dBm | 3.92 dBm
-----------------------------------------------------------------------------
Show the status and the digital diagnostics of all forty-gigabit-ethernet transceivers
DM4170# show interface transceivers forty-gigabit-ethernet
----------------------------------------------------
Transceiver ID | Tx-Fault | Rx-LOS
----------------------------------------------------
forty-gigabit-ethernet 1/1/1:1 | No | No
forty-gigabit-ethernet 1/1/1:2 | No | No
forty-gigabit-ethernet 1/1/1:3 | No | No
forty-gigabit-ethernet 1/1/1:4 | No | No
forty-gigabit-ethernet 1/1/2:1 | No | No
forty-gigabit-ethernet 1/1/2:2 | No | No
forty-gigabit-ethernet 1/1/2:3 | No | No
forty-gigabit-ethernet 1/1/2:4 | No | No
----------------------------------------------------
---------------------------------------------------------------------------------------------------
Transceiver ID | Temperature | Voltage 3.3V | Current | Tx-Power | Rx-Power
---------------------------------------------------------------------------------------------------
forty-gigabit-ethernet 1/1/1 | 36.05 C | 3.26 V | N/A | N/A | N/A
forty-gigabit-ethernet 1/1/1:1 | N/A | N/A | 24.02 mA | -2.18 dBm | -1.27 dBm
forty-gigabit-ethernet 1/1/1:2 | N/A | N/A | 25.03 mA | -1.61 dBm | -0.92 dBm
forty-gigabit-ethernet 1/1/1:3 | N/A | N/A | 25.03 mA | -2.22 dBm | -0.91 dBm
forty-gigabit-ethernet 1/1/1:4 | N/A | N/A | 26.04 mA | -1.33 dBm | -0.6 dBm
forty-gigabit-ethernet 1/1/2 | 32.4 C | 3.26 V | N/A | N/A | N/A
forty-gigabit-ethernet 1/1/2:1 | N/A | N/A | 23.94 mA | -1.57 dBm | -1.46 dBm
forty-gigabit-ethernet 1/1/2:2 | N/A | N/A | 24.02 mA | -1.52 dBm | -1.29 dBm
forty-gigabit-ethernet 1/1/2:3 | N/A | N/A | 25.7 mA | -1.87 dBm | -1.29 dBm
forty-gigabit-ethernet 1/1/2:4 | N/A | N/A | 26.71 mA | -1.69 dBm | -0.82 dBm
---------------------------------------------------------------------------------------------------
N/A
Hardware restrictions
RESOURCES
forwarding-resources
Description
Forwarding resources configuration changes the switch forwarding table allocation pro-
file, allowing to choose between L2 or L3 priority operation modes.
Supported Platforms
This command is supported only in the following platforms: DM4270, DM4380, DM4770,
DM4775.
Syntax
Parameters
profile profile-name
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Admin
History
Release Modification
Usage Guidelines
Example:
This example shows how to update the forwarding table allocation profile to extended-ip.
# forwarding-resources profile extended-ip
This change will take effect on next reboot.
# reboot
Are you sure? [no,yes] yes
Changing the forwarding table allocation profile requires a reboot for the new profile to
take effect.
Hardware restrictions
The presence of this command is conditioned by hardware support. Not all profiles may
be available for all models. The maximum capacity of each entry type for each profile is
also hardware dependent.
show forwarding-resources
Description
Supported Platforms
This command is supported only in the following platforms: DM4270, DM4380, DM4770,
DM4775.
Syntax
show forwarding-resources
Parameters
N/A
Output Terms
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
This example shows the command output when the default profile is active and the
extended-mac is marked for the next reboot.
# show forwarding-resources
Profile Name MAC IPv4 IPv6/64 IPv6/128 Running Startup
-------------------------------------------------------------------
default 128000 128000 32000 4000 true false
extended-ip 32000 168000 42000 10000 false false
extended-mac 288000 16000 4000 1000 false true
N/A
Hardware restrictions
The presence of this command is conditioned by hardware support. Not all profiles may
be available for all models. The maximum capacity of each entry type for each profile is
also hardware dependent.
This topic describes the commands related to CPU Denial of Service (DoS) Protection.
cpu-dos-protect global
Description
Update the maximum number of packets per second that the CPU should accept. Ex-
ceeding traffic will be discarded.
Supported Platforms
Syntax
Parameters
max-pps
Default Value: The default value depends on the hardware platform. See the
hardware restrictions below.
Default
N/A
Command Mode
Configuration mode
Config
History
Release Modification
Usage Guidelines
Example:
Please select the maximum number of packets per second wisely, according to the active
features and protocols. Using a value that is too low might cause the application to
malfunction due to missing packets. In turn, picking an excessively high value might
cause CPU overload during attacks or network loops, for instance.
Hardware restrictions
The default value for DM4770 is 3000 packets per second. For other platforms, the
default value is 900 packets per second.
cpu-dos-protect protocols
Description
Update the maximum number of packets per second per protocol that the CPU should
accept. Exceeding traffic will be discarded.
Supported Platforms
Syntax
Use the no form to revert this command. For further information about the no form, read
the chapter Using the "No" Form of a Command.
Parameters
protocol_name
Value: List of supported protocols: arp, bfd, bgp, cfm, dhcp, eaps, erps,
igmp, in-band-mgmt, lbd, lldp, mpls-ldp, ospf, pppoe, slow-
protocols, stp, ttl-1, tunneling, vrrp-ipv4, vrrp-ipv6.
max-pps max-pps-value
Value: 1 - 5000
Default
N/A
Command Mode
Configuration mode
Required Privileges
Config
History
Release Modification
Usage Guidelines
Example:
This example shows how to configure the protocol maximum rate limit for ARP proto-
col.
# cpu-dos-protect protocols <protocol_name> max-pps 1500
# cpu-dos-protect protocols arp max-pps 1500
(cpu-dos-protect)# commit
Commit complete.
(cpu-dos-protect)#
Please select the maximum number of packets per second wisely, according to the active
features and protocols. Using a value that is too low might cause the application to
malfunction due to missing packets. In turn, picking an excessively high value might
cause CPU overload during attacks or network loops, for instance.
Hardware restrictions
None
show cpu-dos-protect
Description
Supported Platforms
Syntax
show cpu-dos-protect
Parameters
N/A
Output Terms
Output Description
Output Description
Default
N/A
Command Mode
Operational mode. It is possible to execute this command also in the Configuration mode
by using the do keyword before the command.
Required Privileges
Audit
History
Release Modification
Usage Guidelines
Example:
# show cpu-dos-protect
MAX RX DISCARDED RX DISCARDED
QUEUE PROTOCOL PPS OCTETS OCTETS PKTS PKTS
----------------------------------------------------------------
2 ARP 100 3168 0 47 0
6 LLDP 900 0 0 0 0
7 LBD 900 0 0 0 0
8 TTL-1 (L3) 50 1904 0 28 0
9 IN_BAND-MGMT 900 25334 0 319 0
16 DHCP 900 0 0 0 0
17 PPPoE 900 0 0 0 0
18 IGMP 100 0 0 0 0
19 TUNNELING 900 0 0 0 0
21 CFM 900 0 0 0 0
24 OSPF 400 18118 0 177 0
25 MPLS-LDP 400 0 0 0 0
27 BGP 250 0 0 0 0
28 VRRP-IPv4 900 0 0 0 0
29 VRRP-IPv6 900 0 0 0 0
30 BFD 900 38258 0 517 0
32 STP 900 0 0 0 0
33 ERPS 900 0 0 0 0
34 EAPS 900 0 0 0 0
35 SLOW-PROTOCOLS 900 0 0 0 0
None
Hardware restrictions
None
A
aaa authentication-next-method-on-fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
aaa authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
aaa authentication-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
aaa server radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
aaa server tacacs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
aaa user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
access-list acl-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
access-list interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1220
access-list protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
access-list-entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1226
aes-key-exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1433
anti-ip-spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264
assistant-task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574
B
banner login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
C
card-model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609
cfm delay-measurement probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
cfm ma. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1280
cfm ma ais . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
cfm md. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1288
cfm mep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290
cfm mep continuity-check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1294
clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
clear bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
clear bgp soft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
clear core-dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
clear counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
clear interface statistics gpon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435
clear ip host-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
clear lacp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340
clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1612
clear mac-address-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
D
debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
delay-measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
dhcp l2-relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
dhcp relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639
dhcp relay if-option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644
display-defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
dot1q vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
dot1q vlan interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
E
eaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
efm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
erps ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366
H
hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
I
id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1260
interface forty-gigabit-ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
interface gigabit-ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
interface gpon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1438
interface gpon onu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1525
interface hundred-gigabit-ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
interface l3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
interface l3 vrf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
interface loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
interface loopback vrf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
interface mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
interface ten-gigabit-ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
interface tunnel-te . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
interface tunnel-te administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
interface tunnel-te description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1054
interface tunnel-te destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1056
interface tunnel-te name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
interface tunnel-te path-option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
interface tunnel-te path-option dynamic attribute-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
interface twenty-five-gigabit-ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
interface utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
intermediate-agent ChassiSlotPort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
ip arp aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
L
layer2-control-protocol interface protocols action action-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
layer2-control-protocol tunnel-mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
layer2-control-protocol tunnel-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
M
mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
mac-address-table interface learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301
mac-address-table interface limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
mac-address-table vlan limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
monitor session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
mpls l2vpn logging pw-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
mpls l2vpn vpls-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
mpls l2vpn vpls-group vpn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
mpls l2vpn vpls-group vpn administrative-status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .900
mpls l2vpn vpls-group vpn bridge-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
mpls l2vpn vpls-group vpn bridge-domain access-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
mpls l2vpn vpls-group vpn bridge-domain access-interface administrative-status . . . . . . . 909
mpls l2vpn vpls-group vpn bridge-domain access-interface encapsulation dot1q . . . . . . . . 912
mpls l2vpn vpls-group vpn bridge-domain access-interface encapsulation untagged. . . .915
mpls l2vpn vpls-group vpn bridge-domain administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . 918
mpls l2vpn vpls-group vpn bridge-domain bridge-mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
mpls l2vpn vpls-group vpn bridge-domain dot1q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
mpls l2vpn vpls-group vpn bridge-domain mac-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
mpls l2vpn vpls-group vpn bridge-domain qinq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
mpls l2vpn vpls-group vpn bridge-domain transparent-lan-service . . . . . . . . . . . . . . . . . . . . . . . . 933
mpls l2vpn vpls-group vpn description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
mpls l2vpn vpls-group vpn vfi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
O
onu-auth-method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
onu-auto-provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1446
onu-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
onu-force-status-update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
onu-reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
P
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
ping6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
pppoe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649
prefix-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
profile gpon bandwidth-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
profile gpon gem-traffic-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
profile gpon line-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453
profile gpon media-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487
Q
qos interface scheduler-profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1203
qos policer instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187
qos policer profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
qos scheduler-profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1206
R
rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1617
reboot-forced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619
remote-devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1413
request firmware onu add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
request firmware onu cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
request firmware onu install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
request firmware onu remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
rg-one-shot-prov . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1460
rg-reprovision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553
rollback configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
rollback selective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
router bgp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .470
router bgp address-family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
router bgp administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
router bgp as-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
router bgp bgp cluster-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
router bgp bgp default-local-preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
router bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
router bgp neighbor address-family . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
router bgp neighbor address-family prefix-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
router bgp neighbor administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
router bgp neighbor description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
S
save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
screen-resize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
service vlan block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462
service vlan type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464
service-port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1466
session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
set system clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
sflow agent ipv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
sflow collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
sflow interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
show acl-resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1235
show alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
T
telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1601
telnet-server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1603
top . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
traceroute6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
traffic-loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324
twamp reflector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
twamp reflector administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
twamp reflector client-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
twamp reflector client-network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367
twamp reflector port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369
twamp reflector vrf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1371
twamp sender administrative-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
twamp sender connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
twamp sender connection number-of-packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
twamp sender connection server-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
twamp sender connection test-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
twamp sender connection test-session dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387
twamp sender connection test-session max-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
twamp sender connection test-session min-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1393
twamp sender connection test-session packet-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
twamp sender connection vrf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
U
user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
V
vlan-mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520
vrf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .860
vrf address-family ipv4 unicast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .863
vrf rd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
W
who . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606