# ADLINK PacketManager Configuration Guide

Manual Revision: 1.1

Revision Date: August 16, 2017

Part Number: 50-1G042-1010

# Preface

Copyright 2016, 2017 ADLINK Technology, Inc.

This document contains proprietary information protected by copyright. All rights are reserved. No part of this manual may be reproduced by any mechanical, electronic, or other means in any form without prior written permission of the manufacturer.

# Disclaimer

The information in this document is subject to change without prior notice in order to improve reliability, design, and function and does not represent a commitment on the part of the manufacturer. In no event will the manufacturer be liable for direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the product or documentation, even if advised of the possibility of such damages.

# Environmental Responsibility

ADLINK is committed to fulfill its social responsibility to global environmental preservation through compliance with the European Union's Restriction of Hazardous Substances (RoHS) directive and Waste Electrical and Electronic Equipment (WEEE) directive. Environmental protection is a top priority for ADLINK. We have enforced measures to ensure that our products, manufacturing processes, components, and raw materials have as little impact on the environment as possible. When products are at their end of life, our customers are encouraged to dispose of them in accordance with the product disposal and/or recovery programs prescribed by their nation or company.

# Trademarks

Product names mentioned herein are used for identification purposes only and may be trademarks and/or registered trademarks of their respective companies.

Revision History

<table><tr><td>Rev</td><td>Date</td><td>Description</td></tr><tr><td>1.00</td><td>22/03/2016</td><td>Initial release</td></tr><tr><td>1.1</td><td>16/08/2017</td><td>Add LLDP, SNMP, VRRP, LBG and CMM configuration notes; update for MXN-3610/MXN-4100; removed contents for processor boards.</td></tr></table>

# Table of Contents

# Preface.

# 1 Scope ................ 5

1.1 Manual Scope . 5
1.2 Audience . 5
1.3 Products .. 5

# 2 Introduction .............. 6

2.1 Control Plane Software for Switch Blades... 6
2.2 Data Plane Software for x86 Blades .

# 3 Command Line Interface (CLI)..... 8

# 4 Login ............... 9

# 5 Configuration ................ ... 10

5.1 Installation and Upgrade . . 10
5.2 View Mode . 11

5.2.1 Get Help . 11
5.2.2 Enter Configure Mode . . 12
5.2.3 Exit PacketManager Shell . . 13
5.2.4 Show System Information .. . 13
5.2.5 Display Who is on VTY.. . 16

# 5.3 Configure Mode.. . 17

5.3.1 Password.. . 19
5.3.2 Port Configuration ... . 21
5.3.3 IP Configuration.... . 38
5.3.4 ACL Configuration ... . 41
5.3.5 L2 Configuration... . 48
5.3.6 STP Configuration ... . 50
5.3.7 RSTP Configuration ... . 57
5.3.8 Route Configuration .. . 64
5.3.9 Trunk Configuration.. . 69
5.3.10 LBG Configuration . . 76

5.3.11 VLAN Configuration . . 80
5.3.12 IGMP Snooping Configuration .. . 86
5.3.13 IGMP Proxy Configuration ... . 96
5.3.14 Quality of Service (QoS) Configuration... .. 102
5.3.15 VRRP Configuration... . 102
5.3.16 LLDP configuration .... . 106
5.3.17 SNMP Configuration .. . 109
5.3.18 Event log configuration .... .. 111
5.3.19 RPC CMM Configuration .. . 113
5.3.20 Transceiver module configuration.. .. 119

# 6 DHCP.......... .. 121

6.1 DHCP SEVER CONFIG. . 121

6.1.1 Server Configuration .. . 121
6.1.2 Client configuration.. . 124

6.2 DHCP RELAY CONFIG . . 124

6.2.1 Network topology.. . 124
6.2.2 Server Configuration . 124
6.2.3 Relay Configuration.. . 127
6.2.4 Client Configuration.. 128

7 Boot Configuration File ...... ... 129
8 Glossary ......... ... 132

# Getting Service..... ... 136

# 1 Scope

# 1.1 Manual Scope

Administrators and users of the PacketManager software package can manage and monitor the network via a command line interface (CLI), either through a Telnet connection or by direct access through a serial port on the PacketManager equipped system.

This PacketManager Configuration Guide documents the commands used to configure PacketManager for monitoring network traffic and events.

# 1.2 Audience

This manual is intended for:

Technical staff responsible for the configuration, provisioning, and management of network devices and services
Network operations center personnel who manage and monitor PacketManager equipment alarms and events

The document assumes that users of PacketManager equipment are familiar with CLIs in general and particularly with network management software and telecom equipment and terminology.

# 1.3 Products

This manual is for use with the following ADLINK products and PacketManager versions:

aTCA-3430 PacketManager\_3430\_V1.1\_s.729.tar.gz
• aTCA-3710 PacketManager\_3710\_V1.1\_s.729.tar.gz
• aTCA-N700 PacketManager\_n700\_V1.1\_s.729.tar.gz
cPCI-6X10 PacketManager\_6s10\_V1.1\_s.74.tar
• CSA-7400 PacketManager\_7400\_V1.0\_s.659.tar.gz (MXN-3610)
MXN-0410 PacketManager\_0410\_V1.1\_s.74.tar
MXN-4100 PacketManager\_4100\_V1.0\_s.659.tar.gz

# 2 Introduction

Due to the exponential growth of data traffic, service operators need increased levels of switching and fast forwarding bandwidth to keep up with rapidly growing operational demands. ADLINK has developed its own network traffic management software, PacketManager, to allow customers to configure, manage and monitor ADLINK switch blades.

Designed to support a variety of hardware architectures, including Broadcom switches and Intel® Red Rock Canyon switch, ADLINK PacketManager provides a common suite of configuration tools and programming interfaces to make transparent the differences in hardware among platforms.

![This diagram depicts a layered network software architecture stack, organized vertically from top to bottom.\n\n**Top Layer:**\n*   **Applications**: A header box containing the text '(Load Balancer, Flow Classifier, DPI, NGFW, Traffic Offloader, Gateway...)'.\n\n**Middle Layer (Labeled 'SW' on the right edge):**\nThis layer is divided into two main columns:\n\n*   **Left Column (Control Plane):**\n    *   A box labeled **Control Plane** containing stacked blocks:\n        *   **CLI/API/SNMP**\n        *   **ACL** and **Route Protocols** (side-by-side)\n        *   **VRRP** and **IGMP** (side-by-side)\n        *   **LLDP** and **STP** (side-by-side)\n        *   **LACP** and **VLAN** (side-by-side)\n        *   **Port Manager**\n    *   Below this is a box labeled **Linux**.\n\n*   **Right Column (Data Plane):**\n    *   A box labeled **Data Plane** containing:\n        *   **Hyperscan**\n        *   Vertical blocks labeled **IPv4/IPv6**, **MPLS**, and **L2**\n        *   **User Space TCP/IP Stack**\n        *   **nDPI** (located below Hyperscan)\n        *   **Vector Packet Processing (VPP)** and **Libuinet** (located at the bottom of this column).\n\n**Bottom Layer (Labeled 'HW' on the right edge):**\n*   A row of hardware/driver blocks at the base:\n    *   **BCM (Broadcom)**\n    *   **RRC (Intel)**\n    *   **DPDK (IA)**](.packetmanager-manual-en-20170818-v2/947c387942daba91a06edcbf8b403a9f676724af7c05a86844528daff9d71faf.jpg)

Figure 1: ADLINK PacketManager Software Architecture

# 2.1 Control Plane Software for Switch Blades

Built using the Linux operating system as a foundation, the PacketManager control plane includes the most commonly used Layer 2/3/4 protocols, including VLAN, LAG, IGMP, STP, RIP, OSPF, ISIS and ACL. By enabling these higher protocols, the control plane also takes ownership of updating the protocol state/information, including port state/statistics, ARP/routing tables, and relative protocols states, and then synchronizes these data with the switch chipsets.

For easy deployment and management, ADLINK PacketManager not only provides a friendly command line interface (CLI), but also includes remote procedure call (RPC) based APIs to allow further customization and integration with the customers’ management systems.

In addition to general monitoring and management, the control plane also allows customers to define their own policies based on pre-defined rules to control actions taken on matched packets, such as drop, mirror, or forwarding.

# 2.2 Data Plane Software for x86 Blades

In contrast to the control plane, ADLINK has integrated and validated open source data plane software that provides a fast path to process packets on x86 blades with DPDK.

nDPI and Hyperscan can be used to build packet processing applications that need deep packet inspection or application identification functions.

The VPP stack can be used as the basis for a Load Balancer, a Firewall, an IDS, or a Host Stack. At a high level, the software stack provides:

• Fast lookup tables for routes, bridge entries
• Arbitrary n-tuple classifiers
• Out of the box production quality switch/router functionality

If a user-space TCP/IP stack is required on top of DPDK, ADLINK has validated Libuinet, a library version of FreeBSD's TCP/IP stack with additional components.

# 3 Command Line Interface (CLI)

ADLINK PacketManager supports a utility program that enables remote network management, including object configuration and service provisioning. The utility program uses a command line interface (CLI) to communicate with the platform.

The CLI is organized into a number of command modes and submodes in which related functions are grouped in a hierarchical tree structure. System maintenance and configuration commands are reserved for users with administrator privileges, while users with lower access levels only have privileges to perform provisioning tasks or view statistics and status information.

# 4 Login

Users can login to the system via Telnet connection to the interface port on the PacketManager software package. During installation of a blade supporting PacketManager, an IP address must be assigned to the IP parameters of the system. Following initial configuration and after connection to the LAN is established, the user can login to the system IP address via Telnet and use the CLI to perform remote platform management and service provisioning.

The following example illustrates a Telnet connection provided by Microsoft Windows. Any Telnet client can be used. To open a CLI session using Telnet:

1. Click the Windows Start button and select Run.
2. Type telnet and the system IP address assigned to the blade. For example, “telnet 172.162.16.8”

![Run\nType the name of a program, folder, document, or\nInternet resource, and Windows will open it for you.\nOpen: telnet 172.162.16.8\nOK	Cancel	Browse...](.packetmanager-manual-en-20170818-v2/e37f1418144a68164028a03bfd1b3c1d941f02ccc73ae596c99909ef569e7d7a.jpg)

3. Click OK to open a command line window.
4. Type your user name and password as prompted. If you are logging in for the first time, use the default user name and password (“root” and “root”).

# 5 Configuration

This chapter describes PacketManager features for Switch Blades and guides you through the software configuration procedures. Configuration examples are also provided to help you to apply software features in different network scenarios.

# 5.1 Installation and Upgrade

The following procedure is for PacketManager application installation and upgrade on the PacketManager platform.

1. Transfer the file " PacketManager\_xxxx\_xxxx.tar.gz " to the blade and extract it.

[root@atca-3710:/home]# ls

PacketManager\_xxxx\_V1.1.0.tar.gz

[root@atca-3710:/homeatca-3710]# tar -xzvf PacketManager\_xxxx\_V1.1.0.tar.gz

2. Run the script “install.sh” to install the PacketManager application.

[root@atca-3710:/home]# cd PacketManager\_xxxx\_V1.1.0

[root@atca-3710:/home/ PacketManager\_xxxx\_V1.1.0]# ./install.sh

Old start-up config will be cleared. Please make sure that it has been backuped!

Continue to install? (y/n): y

Stopping Broadcom Switch Software .OK

Begin to install...

Starting Broadcom Switch Software ....... OK

3. Run the script “uninstall.sh” to remove the PacketManager application. cPCI-6S10 and MXN-0410 can’t support uninstall.

# Note:

We can add permissions to the software folder before beginning the installation if the permission denied alarm is raised.

[root@atca-3710:/home]# chmod -R 777 PacketManager\_xxxx\_V1.1.0

To enter Configure Mode use the command enable and default password adlink. The display will not echo the password. After entering Configure Mode successfully, the prompt will change from ">" to "#".

```txt
ADLINK> enable
Password:
ADLINK#
```

Note: The passwords you enter do NOT echo on the screen.

# 5.2 View Mode

View Mode provides limited privileges for users. Users can only read system information and version and have no write privileges.

# 5.2.1 Get Help

Entering a question mark “?” at the system prompt displays a list of commands or subcommands available for the current command mode. You can also type a “?” in the middle of a command line to view the list of valid arguments or parameters needed to complete the command.

Get online help

<table><tr><td>Description</td><td colspan="3">Type “?” to get online help</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">?</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Get help after logging in.

```txt
ADLINK>
enable Turn on privileged mode command
quit Leave switch manager shell
show Show running system information
who Display who is on vty
ADLINK>
```

Note: The question mark “?” you enter is a non-display character and will not echo on the command line.

# 5.2.2 Enter Configure Mode

The following command allows you to enter Configure Mode.

Enter enable configure mode

<table><tr><td>Description</td><td colspan="3">Enter enable configure mode.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">enable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Enter enable configure mode after logging in.

```txt
ADLINK> enable
Password:
ADLINK#
```

The default password is “adlink”.

# 5.2.3 Exit PacketManager Shell

The following command allows you to exit PacketManager.

Exit shell

<table><tr><td>Description</td><td colspan="3">Exit from the PacketManager shell in view mode.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">quit</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Exit from the shell.

```txt
ADLINK>
ADLINK> quit
Connection closed by foreign host.
```

# 5.2.4 Show System Information

The following commands are available for displaying system information.

Show system information

<table><tr><td>Description</td><td colspan="3">Show brief information about the system.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show system</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Show brief system information on 3710.

<table><tr><td colspan="2">show system</td></tr><tr><td>Device ID</td><td>: 18</td></tr><tr><td>Device Revision</td><td>: 0</td></tr><tr><td>Firmware Revision</td><td>: 1.9</td></tr><tr><td>IPMI Version</td><td>: 1.5</td></tr><tr><td>Manufacturer ID</td><td>: 24339</td></tr><tr><td>Manufacturer Name</td><td>: Unknown (0x5F13)</td></tr><tr><td>Product ID</td><td>: 14096 (0x3710)</td></tr><tr><td>Product Name</td><td>: Unknown (0x3710)</td></tr><tr><td>Device Available</td><td>: yes</td></tr><tr><td>Provides Device SDRs</td><td>: yes</td></tr><tr><td>Fabric Port Number</td><td>: 1 - 25</td></tr></table>

Show brief system information on 6s10.

<table><tr><td colspan="2">cpci-6s10&gt; show system</td></tr><tr><td>Device ID</td><td>: 18</td></tr><tr><td>Manufacturer ID</td><td>: 24339</td></tr><tr><td>Manufacturer Name</td><td>: Unknown (0x5F13)</td></tr><tr><td>Product ID</td><td>: 21267 (0x5313)</td></tr><tr><td>Product Name</td><td>: Unknown (0x5313)</td></tr><tr><td>Device Available</td><td>: yes</td></tr><tr><td>Provides Device SDRs</td><td>: yes</td></tr><tr><td>Fabric Port Number</td><td>: 2 - 29</td></tr></table>

Show version information

<table><tr><td>Description</td><td colspan="3">Show version information of software and firmware.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show version</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Show version.

<table><tr><td colspan="2">ADLINK&gt; show version</td></tr><tr><td>OS version</td><td>: Linux localhost.localdomain 3.10.0-229.el7.x86_64 #1 SMP Fri</td></tr><tr><td colspan="2">Mar 6 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux</td></tr><tr><td>ADLINK sdk Version</td><td>: PacketManager_7400_V1.0_s.655</td></tr><tr><td>Support Board</td><td>: CAS-7400</td></tr><tr><td>Build on</td><td>: Oct 20 2016 03:32:53</td></tr></table>

Show history

<table><tr><td>Description</td><td colspan="3">Show platform information.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show platform</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Show platform information

ADLINK> show platform

mxn\_3610\_1610

ADLINK>

Show Platform

<table><tr><td>Description</td><td colspan="3">Show the command line history.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show history</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Show the command line history.

```txt
ADLINK> show history
show version
ADLINK> show history
show version
show history
ADLINK>
```

# 5.2.5 Display Who is on VTY

Since multiple users can log into the CLI at the same time, a command is provided to show who is logged in.

Display who is on VTY

<table><tr><td>Description</td><td colspan="3">Display who is on VTY.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">who</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Display who is on VTY.

```txt
ADLINK> who
vty[9] connected from 127.0.0.1.
ADLINK>
```

# 5.3 Configure Mode

Configure Mode provides more privileges than View Mode. Users can configure VLAN, TRUNK, ACL and other functions in Configure Mode to meet their requirements.

The following command allows you to exit the current mode.

Exit current mode

<table><tr><td>Description</td><td colspan="3">Exit from the current mode and go to the next higher level menu.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">exit</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Exit from configure mode to view mode.

```txt
atca-3710# exit
atca-3710>
```

Write

<table><tr><td>Description</td><td colspan="3">Write the current configuration to the default file.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">write</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Write the current configuration to the default file “/etc/vty.conf”.

<table><tr><td>ADLINK# writeConfiguration saved.</td></tr><tr><td>ADLINK#</td></tr></table>

Restore

<table><tr><td>Description</td><td colspan="3">Clear the default configuration file.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">restore</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Clear the default configuration file “/etc/vty.conf”.

<table><tr><td>ADLINK#</td></tr><tr><td>ADLINK# restore</td></tr><tr><td>ADLINK#</td></tr></table>

Export

<table><tr><td>Description</td><td colspan="3">Export current configuration to “/home/vty.conf”.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">export current-configure</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

Export current configuration to “/home/vty.conf”.

```txt
ADLINK# export current-configure
Export current configure to /home/vty.conf
ADLINK#
```

Import

<table><tr><td>Description</td><td colspan="4">Import the saved configuration file.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">import FILE_PATH</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>FILE_PATH</td><td colspan="3">The configure file path, e.g.:/home/vty.conf.</td></tr></table>

# Example

Import the configuration file “/home/vty.conf”.

```txt
ADLINK# import /home/vty.conf
Import success, please restart the board to take effect.
ADLINK#
```

# 5.3.1 Password

Users can enter Configure Mode by inputting the correct password. The default password is “adlink”, and you can change it as below.

The following command allows you to change the password.

Modify password

<table><tr><td>Description</td><td colspan="4">Modify the enable password.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">password xxxxx</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>xxxxx</td><td colspan="3">The new password string.</td></tr></table>

# Example

Modify the password, and login to Configure Mode with the new password.

<table><tr><td>ADLINK # password 123456</td></tr><tr><td>ADLINK # exit</td></tr><tr><td>ADLINK &gt; enable</td></tr><tr><td>Password: &lt;now use 123456 to enter enable node&gt;</td></tr><tr><td>ADLINK #</td></tr></table>

Delete password

<table><tr><td>Description</td><td colspan="3">Delete the enable password.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">delete password</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NA</td></tr></table>

# Example

delete the password, and login to Configure Mode with no password.

<table><tr><td>ADLINK # delete password</td></tr><tr><td>ADLINK # exit</td></tr><tr><td>ADLINK &gt; enable</td></tr><tr><td>ADLINK #</td></tr></table>

# 5.3.2 Port Configuration

The following commands are available for configuring port parameters.

Show port counters

<table><tr><td>Description</td><td colspan="4">Show the traffic counters of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">show port PORT_LIST|PORT_ID counters [nozero]</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>nozero</td><td colspan="3">Optional parameter. This parameter is added to hide those zero items.</td></tr></table>

# Example

Show port counters .

<table><tr><td colspan="3">ADLINK(fabric)# show port xe1 counters</td></tr><tr><td colspan="3">Statistics of port xe1 --</td></tr><tr><td>RX Octets</td><td>:</td><td>410(Byte)</td></tr><tr><td>RX Pkts(total)</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Pkts Without Err</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Unicast</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Bcast</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Mcast</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Err</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Oversize</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Discards</td><td>:</td><td>5(packets)</td></tr><tr><td>R64</td><td>:</td><td>0(packets)</td></tr><tr><td>R65to127</td><td>:</td><td>410(packets)</td></tr><tr><td>R128-255</td><td>:</td><td>0(packets)</td></tr><tr><td>R256-511</td><td>:</td><td>0(packets)</td></tr><tr><td>R512-1023</td><td>:</td><td>0(packets)</td></tr><tr><td>R1024-1518</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Octets</td><td>:</td><td>3465(Byte)</td></tr><tr><td>TX Pkts Without Err</td><td>:</td><td>36(packets)</td></tr><tr><td>TX Unicast</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Bcast</td><td>:</td><td>1(packets)</td></tr><tr><td>TX Mcast</td><td>:</td><td>35(packets)</td></tr><tr><td>TX Discards</td><td>:</td><td>0(packets)</td></tr><tr><td>Time since last clear</td><td>:</td><td>2095600(ms)</td></tr></table>

<table><tr><td colspan="3">ADLINK(fabric)# show port xe1 counters nozero</td></tr><tr><td colspan="3">Statistics of port xe1 --</td></tr><tr><td>RX Octets</td><td>:</td><td>410(Byte)</td></tr><tr><td>RX Pkts(total)</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Pkts Without Err</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Mcast</td><td>:</td><td>5(packets)</td></tr><tr><td>RX Discards</td><td>:</td><td>5(packets)</td></tr><tr><td>R65to127</td><td>:</td><td>410(packets)</td></tr><tr><td>TX Octets</td><td>:</td><td>3465(Byte)</td></tr><tr><td>TX Pkts Without Err</td><td>:</td><td>36(packets)</td></tr><tr><td>TX Bcast</td><td>:</td><td>1(packets)</td></tr><tr><td>TX Mcast</td><td>:</td><td>35(packets)</td></tr><tr><td>Time since last clear</td><td>:</td><td>2109818(ms)</td></tr></table>

Clear port counters

<table><tr><td>Description</td><td colspan="4">Clear the traffic counters of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">clear port PORT_LIST|PORT_ID counters</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr></table>

# Example

Clear port counters .

<table><tr><td colspan="3">ADLINK(fabric)# clear port xe1 counters</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1 counters</td></tr><tr><td colspan="3">Statistics of port xe1 --</td></tr><tr><td>RX Octets</td><td>:</td><td>0(Byte)</td></tr><tr><td>RX Pkts(total)</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Pkts Without Err</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Unicast</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Bcast</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Mcast</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Err</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Oversize</td><td>:</td><td>0(packets)</td></tr><tr><td>RX Discards</td><td>:</td><td>0(packets)</td></tr><tr><td>R64</td><td>:</td><td>0(packets)</td></tr><tr><td>R65to127</td><td>:</td><td>0(packets)</td></tr><tr><td>R128-255</td><td>:</td><td>0(packets)</td></tr><tr><td>R256-511</td><td>:</td><td>0(packets)</td></tr><tr><td>R512-1023</td><td>:</td><td>0(packets)</td></tr><tr><td>R1024-1518</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Octets</td><td>:</td><td>0(Byte)</td></tr><tr><td>TX Pkts Without Err</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Unicast</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Bcast</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Mcast</td><td>:</td><td>0(packets)</td></tr><tr><td>TX Discards</td><td>:</td><td>0(packets)</td></tr><tr><td>Time since last clear</td><td>:</td><td>6073(ms)</td></tr></table>

Show port

<table><tr><td>Description</td><td colspan="4">Show the status of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">show port PORT_LIST|PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Optional parameter. If there is no port list, it will show the general status of all ports. Otherwise, it will show the detailed status of the specified ports.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr></table>

# Example

Show port status.

<table><tr><td colspan="7">ADLINK(fabric)# show port</td></tr><tr><td>PORT</td><td>LINK</td><td>SPEED</td><td>DUPLEX</td><td>AUTONEG</td><td>STP-STATE</td><td>PAUSE MTU</td></tr><tr><td colspan="7">---+---+---+---+---+---+---+---+---</td></tr><tr><td>xe1</td><td>up</td><td>10G</td><td>full</td><td>No</td><td>Forward</td><td>TX RX 1536</td></tr><tr><td>xe2</td><td>down</td><td>0M</td><td>full</td><td>No</td><td>Forward</td><td>TX RX 1536</td></tr><tr><td>xe3</td><td>down</td><td>0M</td><td>full</td><td>No</td><td>Forward</td><td>TX RX 1536</td></tr><tr><td>xe4</td><td>down</td><td>0M</td><td>full</td><td>No</td><td>Forward</td><td>TX RX 1536</td></tr><tr><td>xe5</td><td>down</td><td>0M</td><td>full</td><td>No</td><td>Forward</td><td>TX RX 1536</td></tr><tr><td colspan="7">...</td></tr></table>

Show port status (cont’d).

ADLINK(fabric)# show port xe1

Information of port xe1 --

Name : ADLINK-1

Admin status : Enable

Auto-neg : Off

Link speed : 10000M

Vlan filter : None

Default VLAN : 100

Untag Vlan Cnt : 1

Tagged Vlan Cnt: 0

MTU : 1536

Qinq mode : external

Mac learn : Enable

Mcast limit : Disable

Bcast limit : Enable

DLF limit : Enable

TxPause : Enable

RxPause : Enable

ADLINK(fabric)#

Link status : Up

Duplex mode : Full

Stp state : Forward

Default COS : 0

Untag Vlan No : 100

Mcast max rate : 0 Mbps

Bcast max rate : 89 Mbps

DLF max rate : 478 Mbps

Port enable/disable

<table><tr><td>Description</td><td colspan="4">Set the port admin status of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID enable|disable</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>Enable|disable</td><td colspan="3">Set the admin status of ports to be enable or disable.</td></tr></table>

# Example

Port enable and disable.

<table><tr><td>ADLINK(fabric)# port xe1 enableADLINK(fabric)# show port xe1Information of port xe1 --Name : xe1Admin status : Enable Auto-neg : OffLink speed : 10000M ...ADLINK(fabric)# port xe1 disableADLINK(fabric)# show port xe1Information of port xe1 --Name : xe1Admin status : Disable Auto-neg : OffLink speed : 0M ...</td><td>Link status : UpDuplex mode : FullLink status : DownDuplex mode : Full</td></tr></table>

Port autoneg enable/disable

<table><tr><td>Description</td><td colspan="3">Set the AutoNeg status of ports.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">port PORT_LIST|PORT_ID autoneg enable|disable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="2">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>enable|disable</td><td colspan="2">Set the AutoNeg status of ports to be enable or disable.Note that Enabling autonegotiation is ineffective unless the link partner also has autonegotiation enabled.If autonegotiation is disabled, you must set the line speed of the physical port.</td></tr></table>

# Example

Set port autoneg status.

<table><tr><td colspan="3">ADLINK(fabric)# port xe1 autoneg enable</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="3">Information of port xe1 --</td></tr><tr><td colspan="3">Name : xe1</td></tr><tr><td>Admin status : Enable</td><td colspan="2">Link status : Up</td></tr><tr><td>Auto-neg : On</td><td colspan="2"></td></tr><tr><td>Link speed : 10000M</td><td colspan="2">Duplex mode : Full</td></tr><tr><td colspan="3">....</td></tr><tr><td colspan="3">ADLINK(fabric)# port xe1 autoneg disable</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="3">Information of port xe1 --</td></tr><tr><td colspan="3">Name : xe1</td></tr><tr><td>Admin status : Enable</td><td colspan="2">Link status : Up</td></tr><tr><td>Auto-neg : Off</td><td colspan="2"></td></tr><tr><td>Link speed : 10000M</td><td colspan="2">Duplex mode : Full</td></tr><tr><td colspan="3">...</td></tr></table>

Set port default vlan

<table><tr><td>Description</td><td colspan="4">Set the default vlan id of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID pvlan &lt;1-4094&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>&lt;1-4094&gt;</td><td colspan="3">Default vlan id. 1 to 4094 is legal value. When a packet coming in without vlan, it will be added a vlan. The vlan id is the ingress port&#x27;s default vlan.</td></tr></table>

# Example

Set the default vlan id of ports.

<table><tr><td colspan="3">ADLINK(fabric)# port xe1 pvlan 100</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="3">Information of port xe1 --</td></tr><tr><td colspan="3">Name : xe1</td></tr><tr><td>Admin status : Enable</td><td colspan="2">Link status : Down</td></tr><tr><td colspan="3">Auto-neg : Off</td></tr><tr><td>Link speed : 0M</td><td colspan="2">Duplex mode : Full</td></tr><tr><td>Vlan filter : None</td><td colspan="2">Stp state : Forward</td></tr><tr><td>Default VLAN : 100</td><td colspan="2">Default COS : 0</td></tr><tr><td colspan="3">...</td></tr></table>

Show port QiniQ mode

<table><tr><td>Description</td><td colspan="4">Set the QiniQ mode of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID qinq mode STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>STRING</td><td colspan="3">None | internal | external are legal string.None: disable QiniQ.Internal: pvid add to the internal and use internal vid forwarding.External: pvid add to the external and use external vid forwarding.</td></tr></table>

# Example

Set ports QiniQ mode .

<table><tr><td colspan="2">DLINK(fabric)# port xe1 qinq mode external</td></tr><tr><td colspan="2">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="2">Information of port xe1 --</td></tr><tr><td colspan="2">Name : xe1</td></tr><tr><td>Admin status : Enable</td><td>Link status : Down</td></tr><tr><td colspan="2">Auto-neg : Off</td></tr><tr><td>Link speed : 0M</td><td>Duplex mode : Full</td></tr><tr><td>Vlan filter : None</td><td>Stp state : Forward</td></tr><tr><td>Default VLAN : 1</td><td>Default COS : 0</td></tr><tr><td colspan="2">Untag Vlan Cnt : 0</td></tr><tr><td colspan="2">Tagged Vlan Cnt: 0</td></tr><tr><td colspan="2">MTU : 1536</td></tr><tr><td colspan="2">Qinq mode : external</td></tr><tr><td colspan="2">...</td></tr></table>

Set port mac\_learn status

<table><tr><td>Description</td><td colspan="4">Set the mac_learn status of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID mac_learn STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>STRING</td><td colspan="3">enbale | disable are legal string. If the status is enable, the source mac of the packets coming in the port will be added into the L2 table.Otherwise, the source mac will not be added into the L2 table.</td></tr></table>

# Example

Set port mac\_learn status.

<table><tr><td colspan="2">ADLINK(fabric)# port xe1 mac_learn disable</td></tr><tr><td colspan="2">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="2">Information of port xe1 --</td></tr><tr><td colspan="2">Name : xe1</td></tr><tr><td colspan="2">...</td></tr><tr><td colspan="2">Tagged Vlan Cnt: 0</td></tr><tr><td colspan="2">MTU : 1536</td></tr><tr><td colspan="2">Qinq mode : external</td></tr><tr><td colspan="2">Mac learn : Disable</td></tr><tr><td colspan="2">...</td></tr></table>

Set port pause status

<table><tr><td>Description</td><td colspan="4">Set the pause status of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID txpause | rxpause STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>txpause | rxpause</td><td colspan="3">Tx or rx pause to set.</td></tr><tr><td>STRING</td><td colspan="3">Enable | disable are legal string.</td></tr></table>

# Example

Set port pause status.

<table><tr><td colspan="3">ADLINK(fabric)# port xe1 txpause disable</td></tr><tr><td colspan="3">ADLINK(fabric)# port xe1 rxpause enable</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="3">Information of port xe1 --</td></tr><tr><td colspan="3">Name : xe1</td></tr><tr><td colspan="3">...</td></tr><tr><td>Mcast limit : Disable</td><td colspan="2">Mcast max rate : 0 Mbps</td></tr><tr><td>Bcast limit : Disable</td><td colspan="2">Bcast max rate : 0 Mbps</td></tr><tr><td>DLF limit : Disable</td><td colspan="2">DLF max rate : 0 Mbps</td></tr><tr><td>TxPause : Disable</td><td colspan="2"></td></tr><tr><td>RxPause : Enable</td><td colspan="2"></td></tr><tr><td>ADLINK(fabric)#</td><td colspan="2"></td></tr></table>

Set port storm control

<table><tr><td>Description</td><td colspan="4">Set the storm control of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID rate bcast| mcast| dlf disable|enable&lt;35-40000&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="4">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>bcast| mcast| dlf</td><td colspan="3">Traffic type. DLF mean dest mac address lookup failed.</td></tr><tr><td>Disable|enable</td><td colspan="3">Disable: disable the storm control function.Enable: enable the storm control function.</td></tr><tr><td>&lt;35-40000&gt;</td><td colspan="3">Storm control value, the unit is Mbit. Note that the actual value will be the nearest value supported by the hardware. It can be got by the CMD “show port”.</td></tr></table>

# Example

Set the storm control of ports.

<table><tr><td colspan="3">ADLINK(fabric)# port xe1 rate dlf enable 100</td></tr><tr><td colspan="3">ADLINK(fabric)# port xe1 rate mcast enable 200</td></tr><tr><td colspan="3">ADLINK(fabric)# port xe1 rate bcast enable 300</td></tr><tr><td colspan="3">ADLINK(fabric)# show port xe1</td></tr><tr><td colspan="3">Information of port xe1 --</td></tr><tr><td colspan="3">Name : xe1</td></tr><tr><td>Admin status : Enable</td><td colspan="2">Link status : Down</td></tr><tr><td colspan="3">...</td></tr><tr><td>Mcast limit : Enable</td><td colspan="2">Mcast max rate : 179 Mbps</td></tr><tr><td>Bcast limit : Enable</td><td colspan="2">Bcast max rate : 299 Mbps</td></tr><tr><td>DLF limit : Enable</td><td colspan="2">DLF max rate : 89 Mbps</td></tr><tr><td colspan="3">...</td></tr></table>

Set port MTU

<table><tr><td>Description</td><td colspan="4">Set the MTU of ports.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID mtu &lt;0-15360&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>&lt;0-15360&gt;</td><td colspan="3">The value of MTU. Note that the actual value will be the nearest value can be divided exactly by 4.</td></tr></table>

# Example

Set port MTU value.

```txt
ADLINK(fabric)# port xe1 mtu 12345
ADLINK(fabric)# show port xe1
Information of port xe1 --
Name : xe1
...
MTU : 12348
...
```

Set port description

<table><tr><td>Description</td><td colspan="4">Set the description of a port.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID name STRING | clear</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>PORT_ID</td><td colspan="3">Eg: xe1.</td></tr><tr><td>STRING</td><td colspan="3">Set port description as the string. The max length of the string is 31.</td></tr><tr><td>clear</td><td colspan="3">Clear the description of the port.</td></tr></table>

# Example

Set port name.

```txt
ADLINK(fabric)# port xe1 name uplink_port
ADLINK(fabric)# show port xe1
Information of port xe1 --
Name : uplink_port
...
ADLINK(fabric)# port xe1 name clear
ADLINK(fabric)# show port xe1
Information of port xe1 --
Name : xe1
...
```

Set port mirror

<table><tr><td>Description</td><td colspan="3">Set the mirror of port.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">port PORT_LIST|PORT_ID mirror-to PORT_ID ingress| egress|both</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="2">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted. One SrcPort can only be mirrored once.</td></tr><tr><td>ingress| egress|both</td><td colspan="2">Ingress: mirror the ingress traffic of the SrcPort to the DstPort.Egress: mirror the egress traffic of the SrcPort to the DstPort.Both: mirror both the ingress and egress traffic of the SrcPort to the DstPort.</td></tr></table>

# Example

Set port mirror.

<table><tr><td colspan="3">ADLINK(fabric)# port xe1 mirror-to xe2 ingress</td></tr><tr><td colspan="3">ADLINK(fabric)# port xe1 mirror-to xe3 egress</td></tr><tr><td colspan="3">ADLINK(fabric)# show port mirror</td></tr><tr><td>SRC_PORT</td><td>DST_PORT</td><td>MODE</td></tr><tr><td>xe1</td><td>xe3</td><td>egress</td></tr><tr><td colspan="3">ADLINK(fabric)#</td></tr></table>

Clear port mirror

<table><tr><td>Description</td><td colspan="4">clear the mirror of port.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">port PORT_LIST|PORT_ID mirror clear</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_LIST|PORT_ID</td><td colspan="3">Port id list or port id. Eg: xe1 or xe1,xe3 or xe1-xe3.Note: for cPCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>Clear</td><td colspan="3">Clear the mirror of the srcport.</td></tr></table>

# Example

Clear port mirror.

```txt
ADLINK(fabric)# show port mirror
SRC_PORT DST_PORT MODE
xe1 xe2 ingress,
xe2 xe3 ingress,
ADLINK(fabric)# port xe1 mirror clear
ADLINK(fabric)# show port mirror
SRC_PORT DST_PORT MODE
xe2 xe3 ingress,
ADLINK(fabric)#
```

Show port mirror

<table><tr><td>Description</td><td colspan="3">Show the mirror info of all ports.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show port mirror</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">None</td></tr></table>

# Example

Show ports mirror info.

```txt
ADLINK(fabric)# port xe1 mirror-to xe2 ingress
ADLINK(fabric)# port xe2 mirror-to xe3 egress
ADLINK(fabric)# show port mirror
SRC_PORT DST_PORT MODE
xe1 xe2 ingress,
xe2 xe3 egress,
ADLINK(fabric)#
```

# 5.3.3 IP Configuration

The switch provides IPv4, IPv6 address and MAC address configuration functions on the physical network interface card and logical vlan-interface.

Set IPv4 vlan-interface

<table><tr><td>Description</td><td colspan="4">Set a vlan-interface with IPV4 address.</td></tr><tr><td>Prerequisite</td><td colspan="4">Add port(s) to the VLAN</td></tr><tr><td>Syntax</td><td colspan="4">ip vlan-interface VLAN_ID address IP_ADDR_MASK</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VLAN_ID</td><td colspan="3">The vlan id that set vlan-interface ip address.</td></tr><tr><td>IP_ADDR_MASK</td><td colspan="3">Ipv4 address with mask. Such as 10.10.10.1/24.</td></tr></table>

# Example

Add some ports to vlan 100 and set the vlan-interface ipv4 address..

```shell
ADLINK(fabric)# vlan add 100 xe2-xe3 untag
ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24
ADLINK(fabric)# show running-config
#Wrote on Wed Sep 28 05:18:45 2016
!
fabric
    ##Fabric vlan-config
    vlan add 100 xe2-xe3 untag
    ##Fabric L3_intf-config
    ip vlan-interface 100 address 10.10.10.1/24
!
#End
```

Set IPv6 vlan-interface

<table><tr><td>Description</td><td colspan="4">Set a vlan-interface with ipv6 address.</td></tr><tr><td>Prerequisite</td><td colspan="4">Add port(s) to the vlan</td></tr><tr><td>Syntax</td><td colspan="4">ip -6 vlan-interface VLAN_ID address IPV6_ADDR_MASK</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VLAN_ID</td><td colspan="3">The vlan id that set vlan-interface ip address.</td></tr><tr><td>IPV6_ADDR_MASK</td><td colspan="3">IPv6 address with mask. Such as: 234e:0:4567::3d / 64/</td></tr></table>

# Example

Add some ports to vlan 100 and set the vlan-interface ipv6 address..

```shell
ADLINK(fabric)# vlan add 100 xe2-xe3 untag
ADLINK(fabric)# ip -6 vlan-interface 100 address 234e:0:4567::3d/64
ADLINK(fabric)# show running-config
#Wrote on Thu Sep 29 02:12:17 2016
!
fabric
    ##Fabric vlan-config
    vlan add 100 xe2-xe3 untag
    ##Fabric L3_intf-config
    ip -6 vlan-interface 100 address 234e:0:4567::3d/64
!
#End
ADLINK(fabric)#
```

Note: In order to reduce the CPU load, we have to close the IPv6 by default. So if you need to use IPv6, please enable it first. You can use the script “bin/adlink\_ipv6\_set.sh” in the Installation package to enable or disable IPv6.

Delete IP vlan-interface

<table><tr><td>Description</td><td colspan="4">Delete a vlan-interface.</td></tr><tr><td>Prerequisite</td><td colspan="4">Add port(s) to the vlan and set the vlan-interface IP address</td></tr><tr><td>Syntax</td><td colspan="4">no ip vlan-interface VLAN_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VLAN_ID</td><td colspan="3">The VLAN ID of the -interface to delete.</td></tr></table>

# Example

Add some ports to VLAN 100 and set the vlan-interface ip address. Then, delete the vlan-interface.

```fortran
ADLINK(fabric)# vlan add 100 xe2-xe3 untag
ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24
ADLINK(fabric)# show running-config
#Wrote on Wed Sep 28 05:18:45 2016
!
fabric
    ##Fabric vlan-config
    vlan add 100 xe2-xe3 untag

    ##Fabric L3_intf-config
    ip vlan-interface 100 address 10.10.10.1/24

!
#End
ADLINK(fabric)# no ip vlan-interface 100
ADLINK(fabric)# show running-config
#Wrote on Wed Sep 28 05:18:45 2016
!
fabric
    ##Fabric vlan-config
    vlan add 100 xe2-xe3 untag
!
#End
ADLINK(fabric)#
```

Show IP vlan-interface

<table><tr><td>Description</td><td colspan="3">Show the vlan-interface status.</td></tr><tr><td>Prerequisite</td><td colspan="3">Add port(s) to the vlan and set vlan-interface</td></tr><tr><td>Syntax</td><td colspan="3">show ip vlan-interface</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">None</td></tr></table>

# Example

Add some ports to VLAN 100 and set the vlan-interface ip address. Then, show vlan-interface.

```txt
ADLINK(fabric)# vlan add 100 xe2-xe3 untag
ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24
ADLINK(fabric)# ADLINK(fabric)# show ip vlan-interface
Interface VLAN-100 : status UP , IP: 10.10.10.1 , Mask: 255.255.255.0
ADLINK(fabric)#
```

# 5.3.4 ACL Configuration

Access Control Lists (ACLs) provide an optional control capability that allows or disallows transport from certain source or to certain destination addresses. An access control list (ACL) is a set of rules (or permit or deny statements) for identifying traffic based on criteria such as source IP address, destination IP address, and port number.

ACLs are primarily used for packet filtering. A packet filter drops packets that match a deny rule and permits packets that match a permit rule. The following commands are available for ACL.

ACL add

<table><tr><td>Description</td><td colspan="3">Add an ACL.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">acl add &lt;0-1&gt; ACTION QUALIFIER ...</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>&lt;0-1&gt;</td><td>ACL rule priority, 0 means high priority, 1 means low priority. If the</td></tr><tr><td>ACTION</td><td colspan="2">[=param0][/param1]. Please use “acl list actions” to show the actions supported.</td></tr><tr><td>QUALIFIER</td><td colspan="2">[=data][/mask]. There can be 1~8 qualifiers. Please use “acl list qualifiers” to show the qualifiers supported.</td></tr></table>

# Example

Add an ACL rule to make all packets with source IP in the 10.10.10.0 network segment redirect to port xe0.

```txt
atca-3710# acl add 0 redirectport=xe0 srcip=10.10.10.10/255.255.255.0
atca-3710# show acl
index priority action qualifiers......
0 0 RedirectPort=xe0 SrcIp=10.10.10.10/255.255.255.0
```

ACL delete

<table><tr><td>Description</td><td colspan="4">Delete an ACL.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">acl delete &lt;0-1023&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;0-1023&gt;</td><td colspan="3">The acl rule id which will be deleted. It can be got by the CMD “show acl”.</td></tr></table>

# Example

Delete an acl.

```txt
ADLINK(fabric)# acl add 0 redirectport=xe1 srcip=1.2.3.4 dstip=10.1.1.2 import=xe2
ADLINK(fabric)# show acl
index priority action qualifiers......
0 0 redirectPort=xe1 SrcIp=1.2.3.4 DstIp=10.1.1.2 InPort=xe2
ADLINK(fabric)# acl delete 0
ADLINK(fabric)# show acl
index priority action qualifiers......
ADLINK(fabric)#
```

ACL clear

<table><tr><td>Description</td><td colspan="4">Clear the whole acl table</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">acl clear</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>None</td><td colspan="3"></td></tr></table>

# Example

Clear the whole acl table.

```txt
ADLINK(fabric)# acl add 0 redirectport=xe1 srcip=1.2.3.4 dstip=10.1.1.2 import=xe2
ADLINK(fabric)# show acl
index priority action qualifiers......
0 0 redirectPort=xe1 SrcIp=1.2.3.4 DstIp=10.1.1.2 InPort=xe2
ADLINK(fabric)# acl clear
ADLINK(fabric)# show acl
index priority action qualifiers......
ADLINK(fabric)#
```

ACL list actions

<table><tr><td>Description</td><td colspan="3">show the Legal actions supported.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">acl list actions</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">None</td></tr></table>

Table 1 Actions Table

<table><tr><td>Type</td><td>Description</td></tr><tr><td>drop</td><td>Drop the packet.</td></tr><tr><td>RedirectPort</td><td>Forwarding the packet to the port such as XE x.</td></tr><tr><td>RedirectTrunk</td><td>Forwarding the packet to the trunk x.</td></tr><tr><td>OuterVlanNew</td><td>Modify the outer VLAN ID.</td></tr></table>

# Example

ACL list actions.

<table><tr><td colspan="2">ADLINK(fabric)# acl list actions</td></tr><tr><td>Action type</td><td>param0/param1,example</td></tr><tr><td>redirectPort</td><td>redirect packet to a port.eg:redirectPort=xe1</td></tr><tr><td>RedirectTrunk</td><td>redirect packet to a trunk,eg:redirecttrunk=1</td></tr><tr><td>Drop</td><td>drop the packe,eg:drop</td></tr><tr><td>OuterVlanNew</td><td>modify the outervlan id to a new id.eg:OuterVlanNew=1024</td></tr><tr><td>ADLINK(fabric)#</td><td></td></tr></table>

ACL list qualifiers

<table><tr><td>Description</td><td colspan="3">Show the legal qualifiers supported.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">acl list qualifiers</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">None</td></tr></table>

Table 2 Qualifiers Table

<table><tr><td>Type</td><td>Description</td></tr><tr><td>INPORTS</td><td>Filter for the port ID a packet comes from..</td></tr><tr><td>SRCIP</td><td>Filter for source IP address of a packet.</td></tr><tr><td>DSTIP</td><td>Filter for destination IP address of a packet.</td></tr><tr><td>IPPROTOCOL</td><td>Filter for IP protocol (such as 0x06 for TCP) of a packet.</td></tr><tr><td>L4SRCPORT</td><td>Filter for L4 source port of a packet.</td></tr><tr><td>L4DSTPORT</td><td>Filter for L4 destination port of a packet.</td></tr><tr><td>SRCMAC</td><td>Filter for source MAC address of a packet.</td></tr><tr><td>DSTMAC</td><td>Filter for destination MAC address of a packet.</td></tr><tr><td>ETHERTYPE</td><td>Filter for Ethernet type (such as 0x0806 for ARP) of a packet.</td></tr><tr><td>INNERVLAN</td><td>Filter for the inner VLAN ID of a packet.</td></tr><tr><td>OUTERVLAN</td><td>Filter for the outer VLAN ID of a packet.</td></tr></table>

# Example

ACL list qualifiers.

<table><tr><td colspan="2">ADLINK(fabric)# acl list qualifiers</td></tr><tr><td>Qualifier type</td><td>data/mask,example</td></tr><tr><td>SrcIp</td><td>IPv4 Address/IPv4 Address mask,eg:srcip=10.1.1.0/255.255.255.0</td></tr><tr><td>DstIp</td><td>IPv4 Address/IPv4 Address mask,eg:dstip=10.1.1.0/255.255.255.0</td></tr><tr><td>InPort</td><td>Ports,eg:import=xe1</td></tr><tr><td>OuterVlan</td><td>16-bit VLAN data/16-bit mask.12-bitmask is used for vlan id.eg:outervlan=1024/0x0fff</td></tr><tr><td>InnerVlan</td><td>16-bit VLAN data/16-bit mask..12-bitmask is used for vlan id.eg:innervlan=1024/0x0fff</td></tr><tr><td>IpProtocol</td><td>IpProtocol/8-bit mask,eg:ipprotocol=6/0xff</td></tr><tr><td>L4SrcPort</td><td>TCP/UDP port/16-bit mask,eg:l4srcport=80/0xffff</td></tr><tr><td>L4DstPort</td><td>TCP/UDP port/16-bit mask,leg:l4dstport=80/0xffff</td></tr><tr><td>SrcMac</td><td>macaddr&lt;/mask&gt;,eg:srcmac=0x001122334455/0xffffffff</td></tr><tr><td>DstMac</td><td>macaddr&lt;/mask&gt;,eg:dstmac=0x001122334455/0xffffffff</td></tr></table>

Show acl

<table><tr><td>Description</td><td colspan="3">Show the acl table</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show acl</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">None</td></tr></table>

# Example

Show the ACL table.

```txt
ADLINK(fabric)# acl add 0 redirectport=xe1 srcip=1.2.3.4 dstip=10.1.1.2 import=xe2
ADLINK(fabric)# show acl
index priority action qualifiers......
0 0 redirectPort=xe1 SrcIp=1.2.3.4 DstIp=10.1.1.2 InPort=xe2
ADLINK(fabric)#
```

ACL UDF Add

<table><tr><td>Description</td><td colspan="4">Add an ACL UDF.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">acl udf set &lt;0-5&gt; l4header</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>&lt;0-5&gt;</td><td colspan="3">ACL UDF priority, 5 means the highest priority, 0 means the lowest priority.</td></tr><tr><td>OFFSET_LIST</td><td colspan="3">Word(4 byte) offset list .eg:0,2-3,14</td></tr><tr><td>PROTOCOL</td><td colspan="3">L4 protocol . eg: 17 for UDP 6 for TCP</td></tr></table>

# Example

Add an ACL rule to make all packets with L4 user udp data’ the second word is 0x01020304 and source/destination port is 777’s packet will redirect to port xe1.

```txt
ADLINK(fabric)# acl udf set 1 l4header 1 17 777
ADLINK(fabric)# show udf 1
udf_id    protocol    port    offset
    1    17    777    1
ADLINK(fabric)# acl add 1 redirectport=xe1 offset1=0x01020304
ADLINK(fabric)# show acl
index priority action qualifiers......
0    1    redirectPort=xe1 offset1=0x04030201/0xffffffff
ADLINK(fabric)#
```

ACL UDF Delete

<table><tr><td>Description</td><td colspan="4">Delete an ACL UDF.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">acl udf delete &lt;0-5&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;0-5&gt;</td><td colspan="3">ACL UDF priority, 5 means the highest priority, 0 means the lowest priority.</td></tr></table>

# Example

Delete an ACL rule

```txt
ADLINK(fabric)#
ADLINK(fabric)# acl udf set 1 l4header 1 17 777
ADLINK(fabric)# acl udf del 1
ADLINK(fabric)#
```

# 5.3.5 L2 Configuration

A device maintains a MAC address table for frame forwarding. Each entry in this table indicates the MAC address of a connected device, to which interface this device is connected and to which VLAN the interface belongs. After adding a MAC address into the L2 table, the packets with that MAC address can be forwarded to the destination by the L2 table directly rather than by broadcasting.

Show MAC

<table><tr><td>Description</td><td colspan="3">Show the MAC address table entries.</td></tr><tr><td>Prerequisite</td><td colspan="3">N/A</td></tr><tr><td>Syntax</td><td colspan="3">show mac</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-3710</td><td>aTCA-3710</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

```txt
ADLINK(fabric)# show mac
MacAddress vlan port type
38:22:d6:72:b1:63 1 xe1 Dynamic
Total: 1 item(s).
```

l2 init

<table><tr><td>Description</td><td colspan="3">Initialize the mac address table.</td></tr><tr><td>Prerequisite</td><td colspan="3">N/A</td></tr><tr><td>Syntax</td><td colspan="3">I2 init</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-3710</td><td>aTCA-3710</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

ADLINK(fabric)# l2 init ADLINK(fabric)# show mac Total: 0 item(s).

l2 add

<table><tr><td>Description</td><td colspan="4">add a mac entry to mac address table.</td></tr><tr><td>Prerequisite</td><td colspan="4">N/A</td></tr><tr><td>Syntax</td><td colspan="4">I2 add MAC_ADDR PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-3710</td><td>aTCA-3710</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>MAC_ADDR</td><td colspan="3">The L2 mac address.</td></tr><tr><td>PORT_ID</td><td colspan="3">port id,e.g:xe1</td></tr><tr><td></td><td colspan="3">Indicate the mac entry attribute, static or dynamic.</td></tr></table>

# Example

ADLINK(fabric)# l2 add 00:30:64:00:00:99 1 xe1 static ADLINK(fabric)# show mac MacAddress vlan port type 00:30:64:00:00:99 1 xe1 Static Total: 1 item(s).

L2 delete

<table><tr><td>Description</td><td colspan="4">delete mac entry from mac address table.</td></tr><tr><td>Prerequisite</td><td colspan="4">there&#x27;s mac entries in mac address table.</td></tr><tr><td>Syntax</td><td colspan="4">I2 delete MAC_ADDR &lt;1-4094&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-3710</td><td>aTCA-3710</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>MAC_ADDR</td><td colspan="3">The L2 mac address.</td></tr><tr><td>&lt;1-4094&gt;</td><td colspan="3">Vlan id.</td></tr></table>

# Example

```txt
ADLINK(fabric)# show mac
MacAddress vlan port type
00:30:64:00:00:99 1 xe1 Static
Total: 1 item(s).
ADLINK(fabric)# l2 delete 00:30:64:00:00:99 1
ADLINK(fabric)# show mac
Total: 0 item(s).
```

# 5.3.6 STP Configuration

The primary goal in using Spanning Tree Protocol (STP) is to prevent loops in a network, where the same packets might be resent to the same recipients. Use of STP is optional depending on the needs of the service provider. STP feature now just applies to cPCI-6S10 and MXN-0410.

STP add-bridge

<table><tr><td>Description</td><td colspan="4">Add a bridge for the STP system, you can only create just one bridge</td></tr><tr><td>Prerequisite</td><td colspan="4">No bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp add-bridge STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr></table>

STP del-bridge

<table><tr><td>Description</td><td colspan="4">Delete a bridge from the STP system</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp del-bridge STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr></table>

STP add-interface

<table><tr><td>Description</td><td colspan="4">Add interface to the existing bridge</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp add-interface STRING PORT_LIST</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>PORT_LIST</td><td colspan="3">Specifies the port list</td></tr></table>

STP del-interface

<table><tr><td>Description</td><td colspan="4">Delete interface from the existing bridge</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp del-interface STRING PORT_LIST</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>PORT_LIST</td><td colspan="3">Specifies the port list</td></tr></table>

STP set-bridge-priority

<table><tr><td>Description</td><td colspan="4">Set the bridge priority, default value is 32768</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-bridge-priority STRING VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the bridge priority, in step of 4096 within 0~61440</td></tr></table>

STP set-forward-delay

<table><tr><td>Description</td><td colspan="4">Set the bridge forward delay time, default value is 15s</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-forward-delay STRING VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the bridge forward delay time within 4~30.The value should follow: (2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1))</td></tr></table>

STP set-hello-time

<table><tr><td>Description</td><td colspan="4">Set BPDU hello time, default value is 2s</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-hello-time STRING VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the BPDU hello time within 1~10.The value should follow: ( 2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1) )</td></tr></table>

STP set-max-age-time

<table><tr><td>Description</td><td colspan="4">Set the max message age time, default value is 20s</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-max-age-time STRING VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the bridge max age time within 6~40.The value should follow: ( 2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1) )</td></tr></table>

STP set-path-cost

<table><tr><td>Description</td><td colspan="4">Set the port&#x27;s path cost</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-path-cost STRING PORT_ID VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>PORT_ID</td><td colspan="3">Specifies the port id</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the port&#x27;s path cost with 1~100</td></tr></table>

STP set-port-priority

<table><tr><td>Description</td><td colspan="4">Set the port&#x27;s priority, default value is 32</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-port-priority STRING PORT_ID VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>PORT_ID</td><td colspan="3">Specifies the port id</td></tr><tr><td>VALUE</td><td colspan="3">Specifies the port&#x27;s priority in range 0~48 and a multiply of 16</td></tr></table>

STP set-state

<table><tr><td>Description</td><td colspan="4">Set the bridge&#x27;s state</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp set-state STRING (on|off)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STRING</td><td colspan="3">Specifies the bridge name</td></tr><tr><td>on/off</td><td colspan="3">Specifies the bridge state to on/off</td></tr></table>

STP show

<table><tr><td>Description</td><td colspan="3">Show the currents bridge&#x27;s bridge id ,bridge state and ports</td></tr><tr><td>Prerequisite</td><td colspan="3">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="3">stp show</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3"></td></tr></table>

STP show-stp

<table><tr><td>Description</td><td colspan="4">Show the currents bridge&#x27;s detail information, including the bridge and ports</td></tr><tr><td>Prerequisite</td><td colspan="4">Bridge exists</td></tr><tr><td>Syntax</td><td colspan="4">stp show-stp STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>STRING</td><td colspan="3">Bridge name</td></tr></table>

# Example

Enable the STP feature for port ge0-ge2 and xe0 .

<table><tr><td colspan="5">This is example runs at cpci-6s10</td></tr><tr><td colspan="5">cpci-6s10(fabric) # stp add-bridge br0</td></tr><tr><td colspan="5">cpci-6s10(fabric)# stp add-interface br0 ge0-ge2</td></tr><tr><td colspan="5">cpci-6s10(fabric)# stp add-interface br0 xe0</td></tr><tr><td colspan="5">cpci-6s10(fabric)# stp set-state br0 on</td></tr><tr><td colspan="5">cpci-6s10(fabric)# stp show</td></tr><tr><td>bridge name</td><td>bridge id</td><td>STP enabled</td><td>interfaces</td><td></td></tr><tr><td>br0</td><td>8000.4e1d212fb2bb</td><td>yes</td><td>ge0</td><td></td></tr><tr><td></td><td></td><td></td><td>ge1</td><td></td></tr><tr><td></td><td></td><td></td><td>ge2</td><td></td></tr><tr><td></td><td></td><td></td><td>xe0</td><td></td></tr><tr><td>cpci-6s10(fabric)# stp del-interface</td><td>br0 xe0</td><td></td><td></td><td></td></tr><tr><td>cpci-6s10(fabric)# stp del-interface</td><td>br0 ge1</td><td></td><td></td><td></td></tr><tr><td>cpci-6s10(fabric)# stp del-interface</td><td>br0 ge2</td><td></td><td></td><td></td></tr><tr><td colspan="5">cpci-6s10(fabric)# stp show</td></tr><tr><td>bridge name</td><td>bridge id</td><td>STP enabled</td><td>interfaces</td><td></td></tr><tr><td>br0</td><td>8000.000000200001</td><td>yes</td><td>ge0</td><td></td></tr><tr><td>cpci-6s10(fabric)# stp show-stp</td><td>br0</td><td></td><td></td><td></td></tr><tr><td colspan="5">br0</td></tr><tr><td>bridge id</td><td>8000.000000200001</td><td></td><td></td><td></td></tr><tr><td>designated root</td><td>8000.000000200001</td><td></td><td></td><td></td></tr><tr><td>root port</td><td>0</td><td>path cost</td><td>0</td><td></td></tr><tr><td>max age</td><td>20.00</td><td>bridge max age</td><td>20.00</td><td></td></tr><tr><td>hello time</td><td>2.00</td><td>bridge hello time</td><td>2.00</td><td></td></tr><tr><td>forward delay</td><td>15.00</td><td>bridge forward delay</td><td>15.00</td><td></td></tr><tr><td>ageing time</td><td>300.02</td><td></td><td></td><td></td></tr><tr><td>hello timer</td><td>1.58</td><td>tcn timer</td><td>0.00</td><td></td></tr><tr><td>topology change timer</td><td>0.00</td><td>gc timer</td><td>73.70</td><td></td></tr><tr><td colspan="5">flags</td></tr><tr><td colspan="5">ge0 (1)</td></tr><tr><td>port id</td><td>8001</td><td>state</td><td>disabled</td><td></td></tr><tr><td>designated root</td><td>8000.000000200001</td><td>path cost</td><td>100</td><td></td></tr><tr><td>designated bridge</td><td>8000.000000200001</td><td>message age timer</td><td>0.00</td><td></td></tr><tr><td>designated port</td><td>8001</td><td>forward delay timer</td><td>0.00</td><td></td></tr><tr><td>designated cost</td><td>0</td><td>hold timer</td><td>0.00</td><td></td></tr><tr><td>port priority</td><td>32</td><td></td><td></td><td></td></tr><tr><td colspan="5">flags</td></tr></table>

# 5.3.7 RSTP Configuration

Rapid Spanning Tree Protocol (RSTP) is an enhancement to Spanning Tree Protocol (STP). It provides significantly faster spanning tree convergence than STP. RSTP was designed to be backwards-compatible with standard STP. RSTP applies to aTCA-3710, aTCA-n700, aTCA-3430, MXN-3610/MXN-4100.

Spanning-tree

<table><tr><td>Description</td><td colspan="4">Show the currents bridge&#x27;s bridge id ,bridge state and ports</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree (enable | disable)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>Enable</td><td colspan="3">Enable the RSTP feature. All of the ports will be added to the STP domain automatically.</td></tr><tr><td>Disable</td><td colspan="3">Disable the RSTP feature.</td></tr></table>

Spanning-tree force-version

<table><tr><td>Description</td><td colspan="4">Force the STP domain works at STP or RSTP mode. The default mode is RSTP.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree force-version (STP | RSTP)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>STP</td><td colspan="3">802.1d STP mode.</td></tr><tr><td>RSTP</td><td colspan="3">802.1w RSTP mode</td></tr></table>

Spanning-tree forward-delay

<table><tr><td>Description</td><td colspan="4">Set the forward delay time. Default value is 15s.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree forward-delay VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VALUE</td><td colspan="3">Limit to 2~30 and should follow (2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1))</td></tr></table>

Spanning-tree hello-time

<table><tr><td>Description</td><td colspan="4">Set the BPDU hello time. Default value is 2s</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree hello-time VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VALUE</td><td colspan="3">Limit to 1~10 and should follow ( 2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1) )</td></tr></table>

Spanning-tree max-age

<table><tr><td>Description</td><td colspan="4">Set the max age time. Default value is 20s</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree max-age VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VALUE</td><td colspan="3">Limit to 6~40 and should follow (2*(Hello-time +1) &lt;= Max-Age &lt;= 2*(Forward-Delay - 1))</td></tr></table>

Spanning-tree path-cost

<table><tr><td>Description</td><td colspan="4">Set the port&#x27;s path cost</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree path-cost port PORT_ID VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_ID</td><td colspan="3">Port identifier like xe1 or xe2</td></tr><tr><td>VALUE</td><td colspan="3">Path cost value, limit to 1~200000000</td></tr></table>

Spanning-tree port-edge

<table><tr><td>Description</td><td colspan="4">Specific the port is an edge port. This allows the port to transition to Forwarding state without delay. As soon as the STP domain detects a BPDU coming to an edge port, the port becomes a non-edge port.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree port-edge port PORT_ID (yes|no)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>PORT_ID</td><td colspan="3">Port identifier like xe1 or xe2</td></tr><tr><td>Yes</td><td colspan="3">Set the port to be an edge port</td></tr><tr><td>no</td><td colspan="3">Set the port not to be an edge port</td></tr></table>

Spanning-tree port-mcheck

<table><tr><td>Description</td><td colspan="4">This command force the specific to send out RSTP BPDUs. This allows for switches that are running RSTP to establish their connection quickly and for switches running 802.1D STP to be identified</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree port-mcheck port PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_ID</td><td colspan="3">Port identifier like xe1 or xe2</td></tr></table>

Spanning-tree port-stp

<table><tr><td>Description</td><td colspan="4">Enable or disable the port list for use by spanning tree</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree port-stp port PORT_LIST (enable | disable)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>PORT_LIST</td><td colspan="3">Port identifier list like xe1 or xe1-xe2</td></tr><tr><td>Enable</td><td colspan="3">Enable. This is default value.</td></tr><tr><td>Disable</td><td colspan="3">Disable</td></tr></table>

Spanning-tree port-p2p

<table><tr><td>Description</td><td colspan="4">This parameter is used to tell the port if it is connected to a point-to-point link, such as to another switch or bridge or to an end node (“yes”). This parameter should be set to “no” for all ports that are connected to a hub, which is a shared LAN segment. You can also set this parameter to “auto” and the switch will automatically set the “no” value on all ports that it detects are not running at full duplex.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree port-p2p port PORT_ID (yes | no|auto)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="4">Options</td><td>PORT_ID</td><td colspan="3">Port identifier like xe1 or xe2</td></tr><tr><td>yes</td><td colspan="3">yes</td></tr><tr><td>no</td><td colspan="3">no</td></tr><tr><td>auto</td><td colspan="3">Auto set the port’s P2P status</td></tr></table>

Spanning-tree port-priority

<table><tr><td>Description</td><td colspan="4">Set the port&#x27;s priority. Default value is 32</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree port-priority port PORT_ID VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>PORT_ID</td><td colspan="3">Port identifier like xe1 or xe2</td></tr><tr><td>VALUE</td><td colspan="3">Port priority within 0~240 and in step of 16</td></tr></table>

Spanning-tree priority

<table><tr><td>Description</td><td colspan="4">Set the spanning tree bridge priority. Default value is 32768</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">spanning-tree priority VALUE</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VALUE</td><td colspan="3">Bridge priority limit to 0~61400 and in step of 4096</td></tr></table>

Spanning-tree show

<table><tr><td>Description</td><td colspan="3">Show spanning tree information</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">spanning-tree show</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3"></td></tr></table>

# Example

Enable the spanning-tree and do some configuration.

ADLINK(fabric)# spanning-tree enable

ADLINK(fabric)# spanning-tree priority 4096

ADLINK(fabric)# spanning-tree path-cost port xe1 20

ADLINK(fabric)# spanning-tree port-p2p port xe1 no

ADLINK(fabric)# spanning-tree port-stp port xe2 disable

ADLINK(fabric)#spanning-tree port-priority port xe3 16

ADLINK(fabric)# spanning-tree show

-SPANNING TREE information in STP domain ------------

Designated Root : 00:30:64:2a:56:4b

Designated Root Priority : 4096

Designated Root Path Cost : 0

Root Port : none

Root Max Age 20 Hello Time 2 Forward Delay 15

Bridge ID Mac Address : 00:30:64:2a:56:4b

Bridge ID Priority : 4096

Bridge ForceVersion : RSTP

Bridge Max Age 20 Hello Time 2 Forward Delay 15

Time since topology change: 465 seconds

Topology change count: 0

--------- All ports information in STP domain ----------

Name pri cost role span-state link p2p edge Desi-bridge-id Dcost D-port rx\_cfg\_bpdu rx\_rstp\_bpdu rx\_tcn\_bpdu

xe1 128 20 Dis Discarding N N N 0 0 0 0 0

xe2 128 2000 None None N Y N 0 0 0 0 0

xe3 16 2000 Dis Discarding N Y N 0 0 0 0 0

xe4 128 2000 Dis Discarding N Y N 0 0 0 0 0

xe5 128 2000 Dis Discarding N Y N 0 0 0 0 0

xe6 128 2000 Dis Discarding N Y N 0 0 0 0 0

# 5.3.8 Route Configuration

Without a default route, a packet with no matching routing entry is discarded and an ICMP destination-unreachable packet is sent to the source. After adding a route into the routing table, the packets can be forwarded to the destination by that route.

The following commands are available for route configuration.

IPv4 route add

<table><tr><td>Description</td><td colspan="4">Add an IPv4 route entry.</td></tr><tr><td>Prerequisite</td><td colspan="4">Set the vlan interface IP address.</td></tr><tr><td>Syntax</td><td colspan="4">route add IP_ADDR_MASK GATEWAY_IP METRIC</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>IP_ADDR_MASK</td><td colspan="3">IP address with mask length. Eg: 10.10.10.0/24</td></tr><tr><td>GATEWAY_IP</td><td colspan="3">Gateway ip address. It must be the real ip address in the same subnet of the vlan interface&#x27;s IP address in an outer server/router.</td></tr><tr><td>METRIC</td><td colspan="3">The metric number of the route entry.</td></tr></table>

# Example

Set the vlan interface IP address and add a route entry.

<table><tr><td colspan="8">ADLINK(fabric)# vlan add 100 xe1 untag</td></tr><tr><td colspan="8">ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24</td></tr><tr><td colspan="8">ADLINK(fabric)# route add 100.1.1.0/24 10.10.10.2 100</td></tr><tr><td colspan="8">ADLINK(fabric)# show route</td></tr><tr><td>Index</td><td>Dstip</td><td>Mask</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Status</td></tr><tr><td>0</td><td>100.1.1.0</td><td>255.255.255.0</td><td>10.10.10.2</td><td>100</td><td>Static</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td>1</td><td>10.10.10.0</td><td>255.255.255.0</td><td>*</td><td>0</td><td>Direct</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td colspan="8">ADLINK(fabric)#</td></tr></table>

IPv4 route delete

<table><tr><td>Description</td><td colspan="4">delete an IPv4 route entry.</td></tr><tr><td>Prerequisite</td><td colspan="4">Add an IPv4 route entry.</td></tr><tr><td>Syntax</td><td colspan="4">route delete IP_ADDR_MASK GATEWAY_IP METRIC</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>IP_ADDR_MASK</td><td colspan="3">IP address with mask length. Eg: 10.10.10.0/24</td></tr><tr><td>GATEWAY_IP</td><td colspan="3">Gateway ip address.</td></tr><tr><td>METRIC</td><td colspan="3">The metric number of the route entry.</td></tr></table>

# Example

Delete a route entry.

<table><tr><td colspan="8">ADLINK(fabric)# vlan add 100 xe1 untag</td></tr><tr><td colspan="8">ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24</td></tr><tr><td colspan="8">ADLINK(fabric)# route add 100.1.1.0/24 10.10.10.2 100</td></tr><tr><td colspan="8">ADLINK(fabric)# show route</td></tr><tr><td>Index</td><td>Dstip</td><td>Mask</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Status</td></tr><tr><td>0</td><td>100.1.1.0</td><td>255.255.255.0</td><td>10.10.10.2</td><td>100</td><td>Static</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td>1</td><td>10.10.10.0</td><td>255.255.255.0</td><td>*</td><td>0</td><td>Direct</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td colspan="8">ADLINK(fabric)# route delete 100.1.1.0/24 10.10.10.2 100</td></tr><tr><td colspan="8">ADLINK(fabric)# show route</td></tr><tr><td>Index</td><td>Dstip</td><td>Mask</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Status</td></tr><tr><td>0</td><td>100.1.1.0</td><td>255.255.255.</td><td>10.10.10.2</td><td>100</td><td>Static</td><td>sw0.vlan.100</td><td>Chip</td></tr></table>

IPv4 route show

<table><tr><td>Description</td><td colspan="4">show the IPv4 route table.</td></tr><tr><td>Prerequisite</td><td colspan="4">Set the vlan interface IP address.</td></tr><tr><td>Syntax</td><td colspan="4">show route</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>N/A</td><td colspan="3"></td></tr></table>

# Example

Set the vlan interface IP address and add a route entry.

<table><tr><td colspan="8">ADLINK(fabric)# vlan add 100 xe1 untag</td></tr><tr><td colspan="8">ADLINK(fabric)# ip vlan-interface 100 address 10.10.10.1/24</td></tr><tr><td colspan="8">ADLINK(fabric)# route add 100.1.1.0/24 10.10.10.2 100</td></tr><tr><td colspan="8">ADLINK(fabric)# show route</td></tr><tr><td>Index</td><td>Dstip</td><td>Mask</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Status</td></tr><tr><td>0</td><td>100.1.1.0</td><td>255.255.255.0</td><td>10.10.10.2</td><td>100</td><td>Static</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td>1</td><td>10.10.10.0</td><td>255.255.255.0</td><td>*</td><td>0</td><td>Direct</td><td>sw0.vlan.100</td><td>Chip</td></tr><tr><td colspan="8">ADLINK(fabric)#</td></tr></table>

IPv6 route add

<table><tr><td>Description</td><td colspan="4">Add an IPv6 route entry.</td></tr><tr><td>Prerequisite</td><td colspan="4">Set the vlan interface IP address.</td></tr><tr><td>Syntax</td><td colspan="4">route -6 add IP6_ADDR_MASK GATEWAY_IP_6 METRIC</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>IP6_ADDR_MASK_6</td><td colspan="3">IPV6 address with mask length. Eg: 10.10.10.0/24</td></tr><tr><td>GATEWAY_IP_6</td><td colspan="3">Gateway ip6 address. It must be the real ip6 address in the same subnet of the vlan interface&#x27;s IP address in an outer server/router.</td></tr><tr><td>METRIC</td><td colspan="3">The metric number of the route entry.</td></tr></table>

# Example

Show route table.

<table><tr><td colspan="7">ADLINK(fabric)# ip -6 vlan-interface 100 address 2001:0db8:0:f101::1/64</td></tr><tr><td colspan="7">ADLINK(fabric)# route -6 add 2000::/3 2001:0db8:0:f101::2 100</td></tr><tr><td colspan="7">ADLINK(fabric)# show route -6</td></tr><tr><td>Index Dstip/Mask_len</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Satus</td><td></td></tr><tr><td>0 ffff:fe3f:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>1 b80d:120:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>2 0:80fe::ff66:3002:3422:11fe/128</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>3 0:20::/3</td><td>b80d:120:1f1::200:0</td><td>100</td><td>Static</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td colspan="7">ADLINK(fabric)#</td></tr></table>

IPv6 route delete

<table><tr><td>Description</td><td colspan="4">Delete an IPv6 route entry.</td></tr><tr><td>Prerequisite</td><td colspan="4">Add an IPv6 route entry.</td></tr><tr><td>Syntax</td><td colspan="4">route delete IP6_ADDR_MASK GATEWAY_IP METRIC</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>IP6_ADDR_MASK_6</td><td colspan="3">IPV6 address with mask length. Eg: 10.10.10.0/24</td></tr><tr><td>GATEWAY_IP_6</td><td colspan="3">Gateway ip6 address. It must be the real ip6 address in the same subnet of the vlan interface&#x27;s IP address in an outer server/router.</td></tr><tr><td>METRIC</td><td colspan="3">The metric number of the route entry.</td></tr></table>

# Example

Delete a route entry.

<table><tr><td colspan="7">ADLINK(fabric)# route -6 add 2000::/3 2001:0db8:0:f101::2 100</td></tr><tr><td colspan="7">ADLINK(fabric)# show route -6</td></tr><tr><td>Index Dstip/Mask_len</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Satus</td><td></td></tr><tr><td>0 ffff:fe3f:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>1 b80d:120:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>2 0:80fe::ff66:3002:3422:11fe/128</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>3 0:20::/3</td><td colspan="2">b80d:120:1f1::200:0 100</td><td>Static</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td colspan="7">ADLINK(fabric)# route -6 del 2000::/3 2001:0db8:0:f101::2 100</td></tr><tr><td colspan="7">ADLINK(fabric)# show route -6</td></tr><tr><td>Index Dstip/Mask_len</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Satus</td><td></td></tr><tr><td>0 ffff:fe3f:1f1::/64</td><td>::</td><td>255</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>1 b80d:120:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>2 0:80fe::ff66:3002:3422:11fe/128</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan,100</td><td>Kernel</td><td></td></tr><tr><td>3 0:20::/3</td><td colspan="2">b80d:120:1f1::200:0 100</td><td>Static</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td colspan="7">ADLINK(fabric)#</td></tr></table>

IPv6 route show

<table><tr><td>Description</td><td colspan="4">Show the IPv6 route table.</td></tr><tr><td>Prerequisite</td><td colspan="4">Set the vlan interface IP6 address.</td></tr><tr><td>Syntax</td><td colspan="4">show route -6</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>N/A</td><td colspan="3"></td></tr></table>

# Example

Set the vlan interface IP address and add a route entry.

<table><tr><td colspan="7">ADLINK(fabric)# ip -6 vlan-interface 100 address 2001:0db8:0:f101::1/64</td></tr><tr><td colspan="7">ADLINK(fabric)# route -6 add 2000::/3 2001:0db8:0:f101::2 100</td></tr><tr><td colspan="7">ADLINK(fabric)# show route -6</td></tr><tr><td>Index Dstip/Mask_len</td><td>Gateway</td><td>Metric</td><td>type</td><td>Iface</td><td>Satus</td><td></td></tr><tr><td>0 ffff:fe3f:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>1 b80d:120:1f1::/64</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>2 0:80fe::ff66:3002:3422:11fe/128</td><td>::</td><td>256</td><td>Direct</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td>3 0:20::/3</td><td colspan="2">b80d:120:1f1::200:0 100</td><td>Static</td><td>sw0.vlan.100</td><td>Kernel</td><td></td></tr><tr><td colspan="7">ADLINK(fabric)#</td></tr></table>

# 5.3.9 Trunk Configuration

Trunks, which are also known as link aggregation groups (LAGs), allow you to combine multiple full-duplex Ethernet links into a single logical link. Network devices treat the aggregation as if it is a single link, which increases fault tolerance and provides load sharing.

Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad) that allows you to bundle several physical ports together to form a single logical channel. LACP allows a switch to negotiate an automatic bundle by sending LACP packets to the peer.

# Note:

The following commands should be performed before creating LACP configuration.

acl add 0 redirectport=cpu0 etherType=0x8809

acl add 0 redirectport=cpu0 etherType=0x86dd

Add a new trunk

<table><tr><td>Description</td><td colspan="4">Add a new trunk.</td></tr><tr><td>Prerequisite</td><td colspan="4">NULL</td></tr><tr><td>Syntax</td><td colspan="4">trunk add lacp|manual &lt;1-8&gt;|&lt;0-7&gt;[&lt;0-65535&gt;]</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>lacp|manual</td><td colspan="3">Indicate the trunk mode, manual or lacp.Note:cPCI-6S10 and MXN-0410, only manual is accepted.</td></tr><tr><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr><tr><td>[&lt;0-65535&gt;]</td><td colspan="3">Trunk priority.It is only used for LACP trunk.For MXN-3610/MXN-4100, the priority is a global value.</td></tr></table>

# Example

Delete a route entry.

ADLINK(fabric)# trunk add manual 1

Trunk 1 added.

ADLINK(fabric)# trunk add lacp 8

Trunk 8 added.

Remove an existing trunk

<table><tr><td>Description</td><td colspan="4">Remove a trunk</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exists.</td></tr><tr><td>Syntax</td><td colspan="4">trunk delete &lt;1-8&gt;|&lt;0-7&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr></table>

# Example

Delete a trunk.

ADLINK(fabric)# trunk 1 delete

Remove all trunks

<table><tr><td>Description</td><td colspan="3">Remove all trunks.</td></tr><tr><td>Prerequisite</td><td colspan="3">The trunk exists.</td></tr><tr><td>Syntax</td><td colspan="3">trunk destroy</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">NULL</td></tr></table>

# Example

Delete all trunks.

ADLINK(fabric)# trunk destroy

Add port into a trunk

<table><tr><td>Description</td><td colspan="4">Add port into a specified trunk</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exists.</td></tr><tr><td>Syntax</td><td colspan="4">trunk &lt;1-8&gt;|&lt;0-7&gt; add PORT_ID (|pri &lt;0-255&gt;)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr><tr><td></td><td>PORT_ID</td><td colspan="3">a single port name.eg:xe1</td></tr><tr><td></td><td>&lt;0-255&gt;</td><td colspan="3">port priority only for LACP mode, the default priority is 0x7f.</td></tr></table>

# Example

Add port into a trunk.

ADLINK(fabric)# trunk 3 add xe1

Remove port from a trunk

<table><tr><td>Description</td><td colspan="4">Remove port from a trunk.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist with ports in it</td></tr><tr><td>Syntax</td><td colspan="4">trunk &lt;1-8&gt;|&lt;0-7&gt; del PORT_ID (|pri &lt;0-255&gt;)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr><tr><td></td><td>PORT_ID</td><td colspan="3">a single port name.eg:xe1</td></tr></table>

# Example

Delete port from a trunk.

ADLINK(fabric)# trunk 3 delete xe1

Set m+n mode on a lacp trunk

<table><tr><td>Description</td><td colspan="4">set a max active link num. for a lacp trunk.</td></tr><tr><td>Prerequisite</td><td colspan="4">The lacp trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">trunk &lt;1-8&gt;|&lt;0-7&gt; set-active &lt;1-8&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr><tr><td></td><td>&lt;1-8&gt;</td><td colspan="3">the max active link num. of a lacp trunk.</td></tr></table>

# Example

set a max active link num. for a lacp trunk.

ADLINK(fabric)# trunk 3 set active 4 operation succeed.

Set trunk balance type

<table><tr><td>Description</td><td colspan="4">Set trunk balance type.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">trunk &lt;1-8&gt;|&lt;0-7&gt; balance-type &lt;0-7&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-8&gt;|&lt;0-7&gt;</td><td colspan="3">For MXN-3610/MXN-4100, the ID is &lt;1-8&gt;. For others, the ID is &lt;0-7&gt;.</td></tr><tr><td></td><td>&lt;0-7&gt;</td><td colspan="3">Specifies a trunk balance type.</td></tr></table>

# Example

set the balance-type of a trunk.

ADLINK(fabric)# Trunk 1 balance-type 7 operation succeed.

Set trunk L4port attribute

<table><tr><td>Description</td><td colspan="4">Set l4port protocol hash on/off.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">trunk l4port</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3">on/off the specified protocol for hash calculation.</td></tr></table>

# Example

Set l4port protocol hash on/off.

ADLINK(fabric)# trunk l4port enable operation succeed.

Set trunk balance config

<table><tr><td>Description</td><td colspan="4">Set trunk balance type.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">trunk balance-config set (src-mac|dst-mac|ether-type|vlan-id|src-ip|dst-ip|protocol|tcp-udp-src-port|tcp-udp-dst-port) (on|off)</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td colspan="2">aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td colspan="2">cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="2">(src-mac|dst-mac|ether-type|vlan-id|src-ip|dst-ip|protocol|tcp-udp-src-port|tcp-udp-dst-port)</td><td colspan="2">Specifies the packet field used as a trunk balance hash key.</td></tr><tr><td></td><td colspan="2">(on|off)</td><td colspan="2">enable or disable. All of the field is enabled by default.</td></tr></table>

# Example

set a max active link num. for a lacp trunk.

ADLINK(fabric)# trunk balance-config set src-mac on operation succeed.

Show trunk balance config

<table><tr><td>Description</td><td colspan="4">show trunk balance config.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">1.show trunk balance-config2.trunk balance-config show</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td colspan="2">aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td colspan="2">cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="2">(src-mac|dst-mac|ether-type|vlan-id|src-ip|dst-ip|protocol|tcp-udp-src-port|tcp-udp-dst-port)</td><td colspan="2">Specifies the packet field used as a trunk balance hash key.</td></tr><tr><td></td><td colspan="2">(on|off)</td><td colspan="2">enable or disable. All of the field is enabled by default.</td></tr></table>

# Example

Show the trunk balance-config status.

<table><tr><td colspan="2">ADLINK(fabric)# trunk balance-config show</td></tr><tr><td>field</td><td>status</td></tr><tr><td>src-mac</td><td>on</td></tr><tr><td>dst-mac</td><td>off</td></tr><tr><td>ether-type</td><td>off</td></tr><tr><td>vlan-id</td><td>off</td></tr><tr><td>vlan-pri</td><td>off</td></tr><tr><td>src-ip</td><td>on</td></tr><tr><td>dst-ip</td><td>on</td></tr><tr><td>protocol</td><td>on</td></tr><tr><td>tcp-udp-src-port</td><td>on</td></tr><tr><td>tcp-udp-dst-port</td><td>on</td></tr><tr><td>cp-udp-dst-port</td><td>on</td></tr><tr><td>ADLINK(fabric)#</td><td></td></tr></table>

Set LACP system priority

<table><tr><td>Description</td><td colspan="4">Set the LACP trunk system priority.</td></tr><tr><td>Prerequisite</td><td colspan="4">The trunk exist.</td></tr><tr><td>Syntax</td><td colspan="4">trunk lacp-sys-pri &lt;1-127&gt;</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td colspan="2">aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td colspan="2">cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="2">&lt;1-127&gt;</td><td colspan="2">Specifies the LACP system priority value. 1 is the highest.</td></tr></table>

# Example

Set the lacp trunk system priority.

ADLINK(fabric)# trunk lacp-sys-pri 2

# 5.3.10 LBG Configuration

Load balancing group provides a more flexible way to dispatch traffic than trunk; any logical port can be added, like VF on the PEP port.

As of now, Packet Manager only supports equal distribution, layer 3, 4 header hash.

Port failover is handled automatically.

Add a new LBG

<table><tr><td>Description</td><td colspan="4">Create a new load balancing group.</td></tr><tr><td>Prerequisite</td><td colspan="4">NULL</td></tr><tr><td>Syntax</td><td colspan="4">lbg add</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td></td><td colspan="3">Group number to create. &lt;1-65535&gt;</td></tr><tr><td></td><td colspan="3">Total hash bin number, can be 0-16, 32, 64, 128, 256, 512, 1024, 2048, 4096, if 0, default value 128 will be used.</td></tr></table>

# Example

Add a new LBG.

ADLINK(fabric)# lbg add 1 16 LBG 1 added. ADLINK(fabric)#

Delete a LBG

<table><tr><td>Description</td><td colspan="4">Delete a load-balancing group.</td></tr><tr><td>Prerequisite</td><td colspan="4">Target LBG should exist.</td></tr><tr><td>Syntax</td><td colspan="4">lbg del</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3">Group number to delete. &lt;1-65535&gt;</td></tr></table>

# Example

Delete an LBG.

ADLINK(fabric)# lbg del 1 LBG 1 deleted. ADLINK(fabric)#

Add a port to LBG

<table><tr><td>Description</td><td colspan="3">Add a port to existing load balancing group.</td></tr><tr><td>Prerequisite</td><td colspan="3">Target LBG should exist.</td></tr><tr><td>Syntax</td><td colspan="3">lbg port add</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td></td><td colspan="2">Target LBG index. &lt;1-65535&gt;</td></tr><tr><td></td><td colspan="2">Logical port number to be added into the LBG. Such as 1, 4141.</td></tr><tr><td></td><td colspan="2"></td></tr></table>

# Example

Add a port to some LBG.

ADLINK(fabric)# lbg port add 1 4141 active Added port 4141 to LBG 1. active ADLINK(fabric)#

Delete a port from LBG

<table><tr><td>Description</td><td colspan="3">Delete a port from load balancing group.</td></tr><tr><td>Prerequisite</td><td colspan="3">Target LBG should exist; Target port should belong to the LBG.</td></tr><tr><td>Syntax</td><td colspan="3">lbg port del</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td></td><td colspan="2">Target LBG index. &lt;1-65535&gt;</td></tr><tr><td></td><td colspan="2">Logical port number to be deleted from the LBG.</td></tr></table>

# Example

Add a port to some LBG.

ADLINK(fabric)# lbg port del 1 4141 Deleted port 4141 from LBG 1. ADLINK(fabric)#

Set hashing properties for all LBGs

<table><tr><td>Description</td><td colspan="4">Set L34 hashing properties for all load balancing groups.</td></tr><tr><td>Prerequisite</td><td colspan="4">NULL</td></tr><tr><td>Syntax</td><td colspan="4">lbg hash34 set</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td></td><td colspan="3">Hash calculation field to set, includinguse_sip Include SIP in hash computationuse_dip Include DIP in hash computationuse_l4src Use L4SRC if L4 protocol is enableduse_l4dst Use L4DST if L4 protocol is enableduse_prot Enable L4 protocol in hash computationsymmetric SIP/DIP and L4SRC/L4DST fields aresymmetrized prior to hashinguse_tcp Use L4SRC/L4DST when L4 protocol is TCPuse_udp Use L4SRC/L4DST when L4 protocol is UDP</td></tr><tr><td></td><td colspan="3">If corresponding field is included in hash calculation.</td></tr></table>

# Example

Enable symmetric hash for all LBGs.

ADLINK(fabric)# lbg hash34 set symmetric on LBG hash field is set. ADLINK(fabric)#

lbg show

<table><tr><td>Description</td><td colspan="4">Show lbg group info</td></tr><tr><td>Prerequisite</td><td colspan="4">NULL</td></tr><tr><td>Syntax</td><td colspan="4">lbg show</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3"></td></tr></table>

# Example

Show lbg info

![| LBG list end..... | Value |\n| ----------------- | ----- |\n| 1                 | 18    |\n| 18                | active |\n| up                | up    |](.packetmanager-manual-en-20170818-v2/4eab64579f085a298525e8683ee7e325ad6740a4d7824be7813b845bc7c640ad.jpg)

# 5.3.11 VLAN Configuration

Ethernet is a network technology based on the Carrier Sense Multiple Access/Collision Detect (CSMA/CD) mechanism. Because the medium is shared, collisions and excessive broadcasts are common on Ethernet networks. To address the issue, virtual LAN (VLAN) was introduced to break a LAN down into separate VLANs.

Virtual LAN (VLAN) support to a Layer 2 switch offers some of the benefits of both bridging and routing. Like a bridge, a VLAN switch forwards traffic based on the Layer 2 header, which is fast, and like a router, it partitions the network into logical segments, which provides better administration, security and management of multicast traffic. Virtual Local Area Networks (VLANs) are used to provide connectivity between ports and other entities in the Switch System and across Ethernet Virtual Connections across Ethernet Networks.

Note: Since of historical reasons, our VLAN module has a different command format in cPCI-6s10 and MXN-0410.

VLAN enable

<table><tr><td>Description</td><td colspan="4">enable a vlan</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan VID (enable|disable)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr><tr><td>enable</td><td colspan="3">Create the specific VLAN</td></tr><tr><td>disable</td><td colspan="3">Delete the specific VLAN</td></tr></table>

Add Associate-MAC address to a VLAN

<table><tr><td>Description</td><td colspan="4">Associate a MAC address to a VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan associate-mac add VID MAC_ADDRESS prio cos_valuevlan associate-mac add VID MAC_ADDRESS</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr><tr><td>MAC_ADDRESS</td><td colspan="3">Specifies the MAC address in formatxx:xx:xx:xx:xx:xx.</td></tr><tr><td>cos_value</td><td colspan="3">Specifies the cos value for the matched packet</td></tr></table>

Delete Associate-MAC address to a VLAN

<table><tr><td>Description</td><td colspan="4">Delete the association of a MAC address from a VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan associate-mac del MAC_ADDRESS</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>MAC_ADDRESS</td><td colspan="3">Specifies the MAC address</td></tr></table>

Set VLAN name

<table><tr><td>Description</td><td colspan="4">Name a VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan name set VID STRING</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr><tr><td>STRING</td><td colspan="3">Specifies the VLAN name.</td></tr></table>

Clear VLAN name

<table><tr><td>Description</td><td colspan="4">Remove the name of a VLAN. The name will be set to “null”</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan name clear VID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr></table>

Add port to a VLAN

<table><tr><td>Description</td><td colspan="4">Add port or port list to a VLAN in tag or untag mode</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan add VID PORT_LIST|PORT_ID (tag|untag)</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>VID</td><td colspan="3">Specifies the VLAN id, if the VLAN ID not exists, you should enable the vlan first on cPCI-6S10 and MXN-0410. For other platforms, it will be created automatically on.</td></tr><tr><td>PORT_LIST|PORTID</td><td colspan="3">Specifies the port or port list that want to add to VLAN. For PCI-6S10 and MXN-0410, only one port id is accepted.</td></tr><tr><td>(tag|untag)</td><td colspan="3">tag or untag mode for the port list.</td></tr></table>

Delete ports from VLAN

<table><tr><td>Description</td><td colspan="4">Delete port or port list from a VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan del VID PORT_LIST|PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr><tr><td>PORT_LIST|PORTID</td><td colspan="3">Specifies the port or port list that want to add to VLAN. For PCI-6S10 and MXN-0410, only one port id is accepted.</td></tr></table>

Remove VLAN

<table><tr><td>Description</td><td colspan="4">Delete an existing VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">vlan remove VID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VID</td><td colspan="3">Specifies the VLAN id</td></tr></table>

Show VLAN

<table><tr><td>Description</td><td colspan="4">Show an existing VLAN</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">show vlan [VID]</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VID</td><td colspan="3">Specifies the VLAN id.If there is no VID, all VLANs created will be shown.</td></tr></table>

Show VLAN associated MAC

<table><tr><td>Description</td><td colspan="4">Show an existing VLAN associate-MAC</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">show vlan associate-mac [VID]</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VID</td><td colspan="3">Specifies the VLAN id.If there is no VID, all VLANs created will be shown.</td></tr></table>

# Example

1) Create a VLAN with VLAN ID of 2. Set port xe2 and xe3 as untag port and add them into VLAN.

This is example runs at aTCA-3710

ADLINK (fabric)# vlan add 2 xe2 untag

ADLINK (fabric)# vlan add 2 xe3 untag

ADLINK (fabric)# vlan name set 2 hello

ADLINK (fabric)# show vlan 2

vlan 2, name hello, ports xe2-xe3, untagged xe2-xe3.

ADLINK (fabric)# vlan del 2 xe2

ADLINK (fabric)# show vlan 2

vlan 2, name hello, ports xe3, untagged xe3.

ADLINK (fabric)# vlan remove 2

ADLINK (fabric)# show vlan 2

vlan 2 ports NULL, untagged NULL.

This is example runs at cpci-6s10

cpci-6s10(fabric)# vlan 2 enable

cpci-6s10(fabric)# vlan 2 port xe2 untag

cpci-6s10(fabric)# vlan 2 port xe3 untag

cpci-6s10(fabric)# show vlan 2

Name : VLAN 2

Administrative State: enabled

Member ports : xe2-xe3

Untagged ports : xe2-xe3

cpci-6s10(fabric)# no vlan 2 port xe2

cpci-6s10(fabric)# show vlan 2

Name : VLAN 2

Administrative State: enabled

Member ports : xe3

Untagged ports : xe3

# 2) Associate MAC with a VLAN.

<table><tr><td colspan="2">This is example runs at aTCA-3710</td></tr><tr><td colspan="2">ADLINK(fabric)# vlan associate mac 2 00:11:22:33:44:55 prio 1</td></tr><tr><td colspan="2">ADLINK(fabric)# vlan associate mac 2 00:11:22:33:44:66</td></tr><tr><td colspan="2">ADLINK(fabric)# show vlan associate mac</td></tr><tr><td colspan="2">MAC 00:11:22:33:44:55 -- vlan: 2, pri: 1</td></tr><tr><td colspan="2">MAC 00:11:22:33:44:66 -- vlan: 2, pri: 0</td></tr><tr><td colspan="2">ADLINK(fabric)# no vlan associate mac 00:11:22:33:44:55</td></tr><tr><td colspan="2">ADLINK(fabric)# show vlan associate mac</td></tr><tr><td colspan="2">MAC 00:11:22:33:44:66 -- vlan: 2, pri: 0</td></tr></table>

# 5.3.12 IGMP Snooping Configuration

IGMP snooping is the process of listening to Internet Group Management Protocol (IGMP) network traffic. The feature allows a network switch to listen in on the IGMP conversation between hosts and routers. By listening to these conversations the switch maintains a map of which links need which IP multicast streams. Multicasts may be filtered from the links which do not need them and thus controls which ports receive specific multicast traffic.

The following commands are available for IGMP Snooping configuration.

IGMP snooping enable

<table><tr><td>Description</td><td colspan="3">Enable IGMP snooping protocol.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">igmp-snooping enable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Enable the IGMP snooping protocol.

```txt
ADLINK(fabric)#
ADLINK(fabric)# igmp-snooping enable
ADLINK(fabric)#
```

Note: Cannot start IGMP snooping and proxy simultaneously!

IGMP snooping disable

<table><tr><td>Description</td><td colspan="3">Disable IGMP snooping protocol.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">igmp-snooping disable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Disable the IGMP snooping protocol.

```txt
ADLINK(fabric)#
ADLINK(fabric)# igmp-snooping disable
ADLINK(fabric)#
```

IGMP snooping add-query-port

<table><tr><td>Description</td><td colspan="4">Add IGMP snooping query port</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable.</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping add-query-port PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_ID</td><td colspan="3">Port id, eg: xe1.</td></tr></table>

# Example

IGMP snooping add query port.

<table><tr><td>ADLINK(fabric)# igmp-snooping add-query-port port xe1</td></tr><tr><td>ADLINK(fabric)# igmp-snooping del-query-port xe12</td></tr><tr><td>ADLINK(fabric)# igmp-snooping show query-port-config</td></tr><tr><td>Configured query portList:</td></tr><tr><td>xe1</td></tr><tr><td>xe12</td></tr><tr><td>ADLINK(fabric)# ADLINK(fabric)#</td></tr></table>

IGMP snooping del-query-port

<table><tr><td>Description</td><td colspan="4">Delete IGMP snooping query port</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable.</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping del-query-port port PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_ID</td><td colspan="3">Port id, eg: xe1.</td></tr></table>

# Example

IGMP snooping add query port.

<table><tr><td>ADLINK(fabric)# igmp-snooping show query-port-config</td></tr><tr><td>Configured query portList:</td></tr><tr><td>xe1</td></tr><tr><td>xe12</td></tr><tr><td>ADLINK(fabric)# ADLINK(fabric)#</td></tr><tr><td>ADLINK(fabric)# igmp-snooping del-query-port xe12</td></tr><tr><td>ADLINK(fabric)# igmp-snooping show query-port-config</td></tr><tr><td>Configured query portList:</td></tr><tr><td>xe1</td></tr><tr><td>ADLINK(fabric)# ADLINK(fabric)#</td></tr></table>

IGMP snooping add-router-port

<table><tr><td>Description</td><td colspan="4">Add IGMP snooping query port</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable.Add port to the VLAN.</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping add-router-port vlan VLAN_ID port PORT_ID &lt; multicast-group-address IP_ADDR&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>VLAN_ID</td><td colspan="3">Vlan id, eg: 100.</td></tr><tr><td>PORT_ID</td><td colspan="3">Port id, eg:xe1.</td></tr><tr><td>IP_ADDR</td><td colspan="3">IP address. This is an optional parameters.</td></tr></table>

# Example

Add IGMP snooping router port.

<table><tr><td>ADLINK(fabric)#</td><td>igmp-snooping</td><td>add-router-port</td><td>vlan</td><td>100</td><td>port</td><td>xe1</td></tr><tr><td colspan="7">multicast-group-address 239.1.1.1</td></tr><tr><td>ADLINK(fabric)#</td><td>igmp-snooping</td><td>add-router-port</td><td>vlan</td><td>100</td><td>port</td><td>xe1</td></tr><tr><td>ADLINK(fabric)#</td><td>ADLINK(fabric)#</td><td>igmp-snooping</td><td>show</td><td colspan="3">router-port-config</td></tr><tr><td>VLAN</td><td colspan="6">router port</td></tr><tr><td>100</td><td colspan="6">xe1</td></tr><tr><td colspan="7">ADLINK(fabric)#</td></tr></table>

IGMP snooping del-router-port

<table><tr><td>Description</td><td colspan="4">Delete IGMP snooping query port.</td></tr><tr><td>Prerequisite</td><td colspan="4">None</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping del-router-port vlan VLAN_ID port PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VLAN_ID</td><td colspan="3">Vlan id, eg: 100.</td></tr><tr><td>PORT_ID</td><td colspan="3">Port id, eg:xe1.</td></tr></table>

# Example

Delete IGMP router port.

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping del-router-port vlan 100 port xe1</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show router-port-config</td></tr><tr><td colspan="2">VLAN router port</td></tr><tr><td colspan="2">ADLINK(fabric)#</td></tr></table>

IGMP snooping group-life

<table><tr><td>Description</td><td colspan="4">Set IGMP snooping group-life</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable.</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping group-life &lt;10-1000&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;10-1000&gt;</td><td colspan="3">Group life time value.&lt;10-1000&gt; seconds</td></tr></table>

# Example

Set IGMP snooping group life.

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping group-life 100</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show config</td></tr><tr><td>GROUP LIFE:</td><td>100</td></tr><tr><td>QUERY INTERVAL:</td><td>125</td></tr><tr><td colspan="2">...</td></tr><tr><td colspan="2">ADLINK(fabric)#</td></tr></table>

IGMP snooping query-interval

<table><tr><td>Description</td><td colspan="4">Set IGMP snooping query-interval value.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping query-interval &lt;10-300&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;10-300&gt;</td><td colspan="3">Query interval value &lt;10-300&gt; seconds\n&quot;</td></tr></table>

# Example

Set IGMP snooping query-interval value..

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping query-interval 100</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show config</td></tr><tr><td>GROUP LIFE:</td><td>100</td></tr><tr><td>QUERY INTERVAL:</td><td>100</td></tr><tr><td>RESPONSE TIME:</td><td>10</td></tr></table>

IGMP snooping response-time

<table><tr><td>Description</td><td colspan="4">Set IGMP snooping response time value.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping response-time &lt;10-25&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;10-25&gt;</td><td colspan="3">Host response timeout value, &lt;10-25&gt; seconds.</td></tr></table>

# Example

Set IGMP snooping response time value.

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping response-time 15</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show config</td></tr><tr><td>GROUP LIFE:</td><td>100</td></tr><tr><td>QUERY INTERVAL:</td><td>100</td></tr><tr><td>RESPONSE TIME:</td><td>15</td></tr><tr><td>ROBUSTNESS:</td><td>2</td></tr><tr><td>ADLINK(fabric)#</td><td></td></tr></table>

IGMP snooping robustness

<table><tr><td>Description</td><td colspan="4">Set IGMP snooping robustness value.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping robustness &lt;1-100&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-100&gt;</td><td colspan="3">Robustness variable value &lt;1-100&gt;</td></tr></table>

# Example

Set IGMP snooping robustness value.

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping robustness 50</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show config</td></tr><tr><td>GROUP LIFE:</td><td>100</td></tr><tr><td>QUERY INTERVAL:</td><td>100</td></tr><tr><td>RESPONSE TIME:</td><td>15</td></tr><tr><td>ROBUSTNESS:</td><td>50</td></tr><tr><td>ADLINK(fabric)#</td><td></td></tr></table>

IGMP snooping set-mc-flood-mode

<table><tr><td>Description</td><td colspan="4">Set IGMP snooping mc-flood-mode</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping set-mc-flood-mode VLAN_ID mode &quot; &lt;0-2&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="2">Options</td><td>VLAN_ID</td><td colspan="3">Vlan id, eg:100.</td></tr><tr><td>&lt;0-2&gt;</td><td colspan="3">0:Flood all multicast packets; 1:Flood unknown multicast packets.; 2:Drop unknown multicast packets.</td></tr></table>

# Example

Set IGMP snooping mc-flood-mode.

<table><tr><td>ADLINK(fabric)# igmp-snooping set-mc-flood-mode 100 mode 0</td></tr><tr><td>ADLINK(fabric)# igmp-snooping set-mc-flood-mode 200 mode 1</td></tr><tr><td>ADLINK(fabric)# igmp-snooping set-mc-flood-mode 300 mode 2</td></tr><tr><td>ADLINK(fabric)# igmp-snooping show mc-flood-mode</td></tr><tr><td>Configured vlan mc flood mode list:vlan multicast flood mode 0, Broadcast all multicast packets.100vlan multicast flood mode 1, Broadcast unknown multicast packets.200vlan multicast flood mode 2, Drop unknown multicast packets.300ADLINK(fabric)#</td></tr></table>

IGMP snooping show

<table><tr><td>Description</td><td colspan="4">Show IGMP snooping configuration.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping showconfig|query-port-config|router-port-config|mc-flood-mode</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>config</td><td colspan="3">Show the value of GROUP LIFE,QUERY INTERVAL,RESPONSE TIME and ROBUSTNESS.</td></tr><tr><td>query-port-config</td><td colspan="3">Show the query-port configuration.</td></tr><tr><td>router-port-config</td><td colspan="3">Show the router-port configuration.</td></tr><tr><td></td><td>mc-flood-mode</td><td colspan="3">Show the multicast flood mode configuration.</td></tr></table>

# Example

Show IGMP snooping configuration..

<table><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show config</td></tr><tr><td>GROUP LIFE:</td><td>100</td></tr><tr><td>QUERY INTERVAL:</td><td>100</td></tr><tr><td>RESPONSE TIME:</td><td>15</td></tr><tr><td>ROBUSTNESS:</td><td>50</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show query-port-config</td></tr><tr><td colspan="2">Configured query portList:</td></tr><tr><td colspan="2">xe1</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show router-port-config</td></tr><tr><td>VLAN</td><td>router port</td></tr><tr><td>100</td><td>xe1</td></tr><tr><td colspan="2">ADLINK(fabric)# igmp-snooping show mc-flood-mode</td></tr><tr><td colspan="2">Configured vlan mc flood mode list:</td></tr><tr><td>vlan multicast flood mode</td><td>0, Broadcast all multicast packets.</td></tr><tr><td>100</td><td></td></tr><tr><td>vlan multicast flood mode</td><td>1, Broadcast unknown multicast packets.</td></tr><tr><td>200</td><td></td></tr><tr><td>vlan multicast flood mode</td><td>2, Drop unknown multicast packets.</td></tr><tr><td>300</td><td></td></tr><tr><td>ADLINK(fabric)#</td><td></td></tr></table>

IGMP snooping show group

<table><tr><td>Description</td><td colspan="4">Show IGMP snooping group information.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP snooping is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-snooping show group</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>N/A</td><td colspan="3"></td></tr></table>

# Example

Show IGMP snooping group information

```txt
ADLINK(fabric)#
ADLINK(fabric)#
ADLINK(fabric)# igmp-snooping show group
VLAN GROUP PORT LIST
1 239.1.1.10 xe1 xe3
ADLINK(fabric)#
ADLINK(fabric)#
```

# 5.3.13 IGMP Proxy Configuration

The Switch Platform supports multicast forwarding as a bandwidth-efficient method to provide point-to-multipoint broadcast video. Thesimple Internet Group Management Protocol (IGMP) is sufficient to control the multicast forwarding. In brief, IGMP builds a per-group forwarding tree. With this multicast forwarding tree, a single copy of any IP multicast packet from a particular sender will pass through port regardless of how many receivers are on the tree.

To connect to a wider multicast network, a multicast router interface can be explicitly configured using the proxy command. In most cases, it is through a WAN port on OLC, but this need not be the case. When a switch is IGMP-enabled, it acts as a proxy client on the router interface by performing the host portion of the IGMP protocol.

IGMP proxy enable

<table><tr><td>Description</td><td colspan="3">Enable IGMP proxy protocol.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">igmp-proxy enable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Enable the IGMP proxy protocol.

```txt
ADLINK(fabric)#
ADLINK(fabric)# igmp-proxy enable
ADLINK(fabric)#
```

Note: Cannot start IGMP snooping and proxy simultaneously!

IGMP proxy disable

<table><tr><td>Description</td><td colspan="3">Disable IGMP proxy protocol.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">igmp-proxy disable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Disable the IGMP proxy protocol.

```txt
ADLINK(fabric)#
ADLINK(fabric)# igmp-proxy disable
ADLINK(fabric)#
```

Note: Cannot start IGMP snooping and proxy simultaneously!

IGMP proxy fast leave enable

<table><tr><td>Description</td><td colspan="3">Enable IGMP proxy fast leave.</td></tr><tr><td>Prerequisite</td><td colspan="3">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="3">igmp-proxy fast-leave enable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Set IGMP proxy fast leave enable..

```txt
ADLINK(fabric)# igmp-proxy fast-leave enable
ADLINK(fabric)#
```

IGMP proxy fast leave disable

<table><tr><td>Description</td><td colspan="3">Disable IGMP proxy fast leave.</td></tr><tr><td>Prerequisite</td><td colspan="3">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="3">igmp-proxy fast-leave disable</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr></table>

# Example

Set IGMP proxy fast leave disable.

ADLINK(fabric)# igmp-proxy fast-leave disable ADLINK(fabric)#

IGMP proxy robust count set

<table><tr><td>Description</td><td colspan="4">Set IGMP proxy robust count number.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-proxy robust-count &lt;1-10&gt;</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>&lt;1-10&gt;</td><td colspan="3">Count value (Default: 2).</td></tr></table>

# Example

Set IGMP proxy robust count number..

ADLINK(fabric)# ADLINK(fabric)# igmp-proxy robust-count 3 ADLINK(fabric)#

IGMP proxy up link port set

<table><tr><td>Description</td><td colspan="4">Set IGMP proxy uplink port.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-proxy uplink-port PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_ID</td><td colspan="3">Port id, eg:xe1.</td></tr></table>

# Example

Set IGMP proxy uplink port.

<table><tr><td>ADLINK(fabric)#</td></tr><tr><td>ADLINK(fabric)# igmp-proxy uplink-port xe1</td></tr><tr><td>ADLINK(fabric)# ADLINK(fabric)# igmp-proxy show uplink</td></tr><tr><td>IGMP proxy uplink port: xe1.</td></tr><tr><td>IGMP proxy uplink VLAN: 1.</td></tr><tr><td>ADLINK(fabric)#</td></tr></table>

IGMP proxy uplink vlan set

<table><tr><td>Description</td><td colspan="4">Set IGMP proxy uplink vlan id.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-proxy uplink-vlan VLAN_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VLAN_ID</td><td colspan="3">VLAN ID, eg:100.</td></tr></table>

# Example

Set IGMP proxy uplink vlan id.

ADLINK(fabric)# igmp-proxy uplink-vlan 100 ADLINK(fabric)# ADLINK(fabric)# igmp-proxy show uplink IGMP proxy uplink port: xe1. IGMP proxy uplink VLAN: 100. ADLINK(fabric)#

IGMP proxy VLAN interface add

<table><tr><td>Description</td><td colspan="4">Add IGMP vlan interface.</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP proxy is enable.VLAN interface is set.</td></tr><tr><td>Syntax</td><td colspan="4">igmp-proxy vlan-interface add VLAN_ID</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>VLAN_ID</td><td colspan="3">VLAN ID, eg:100</td></tr></table>

# Example

Add IGMP vlan interface.

ADLINK(fabric)# vlan add 100 xe1 untag ADLINK(fabric)# ip vlan-interface 100 address 10.1.1.1/24 ADLINK(fabric)# igmp-proxy vlan-interface add 100 ADLINK(fabric)# igmp-proxy show vlan-interface IGMP proxy Service VLANs : 100 ADLINK(fabric)#

IGMP proxy show

<table><tr><td>Description</td><td colspan="4">show IGMP proxy configuration..</td></tr><tr><td>Prerequisite</td><td colspan="4">IGMP proxy is enable</td></tr><tr><td>Syntax</td><td colspan="4">igmp-proxy show group|uplink|vlan-interface</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>group</td><td colspan="3">Show the Multicast group information.</td></tr><tr><td>uplink</td><td colspan="3">Show the uplink port and uplink vlan.</td></tr><tr><td>vlan-interface</td><td colspan="3">Show the VLAN interface.</td></tr></table>

# Example

Show IGMP proxy configuration.

ADLINK(fabric)# igmp-proxy show group

Group Expire VID PORT

ADLINK(fabric)# ADLINK(fabric)# igmp-proxy show uplink

IGMP proxy uplink port: xe1.

IGMP proxy uplink VLAN: 100.

ADLINK(fabric)# igmp-proxy show vlan-interface

IGMP proxy Service VLANs : 100

ADLINK(fabric)#

# Notes:

The following rules should be followed when using IGMP proxy configuration.

1. IGMP-Proxy service should be enabled on each vlan-interface;
2. Both host-side & router-side vlan-interfaces have to enable IGMP proxy;
3. Support only one uplink port & one uplink vlan;
4. IGMP proxy & IGMP snooping cannot be enabled at the same time;
5. TTL of ingress multicast flow should be bigger than 1 (2 or larger);

# Example

Set the VLAN ID and port for the proxy.

```txt
atca-3710(fabric)# ip igmp proxy
atca-3710(fabric)# ip igmp-proxy uplink-port xe0
atca-3710(fabric)# ip igmp-proxy uplink-vlan 10
atca-3710(fabric)# ip igmp-proxy vlan-interface 10
atca-3710(fabric)#
atca-3710(fabric)# show ip igmp-proxy
group Multicast group information
uplink Proxy uplink information
vlan-interface Proxy service VLAN information
atca-3710(fabric)# show ip igmp-proxy uplink
IGMP proxy uplink port: xe0.
IGMP proxy uplink VLAN: 10.
```

# 5.3.14 Quality of Service (QoS) Configuration

Quality of Service (QoS) is no longer supported by PacketManager.

# 5.3.15 VRRP Configuration

VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses.

Add a virtual router

<table><tr><td>Description</td><td colspan="3">Add a virtual route on a specified VLAN interface.</td></tr><tr><td>Prerequisite</td><td colspan="3">The target VLAN and its IP have been built.</td></tr><tr><td>Syntax</td><td colspan="3">vrrp add vrid &lt;1-255&gt; vlan &lt;1-4094&gt; vrip A.B.C.D</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;1-255&gt; Specifies the virtual router id.&lt;1-4094&gt; Specifies the vlan id.A.B.C.D Specifies the virtual router ip address.</td></tr><tr><td>Output</td><td colspan="3">Information about operation result.</td></tr></table>

Example

<table><tr><td colspan="2">ADLINK(fabric)# vrrp add vrid 1 vlan 22 vrip 160.1.1.101</td></tr><tr><td colspan="2">add virtual route succeed!</td></tr><tr><td colspan="2">ADLINK(fabric)# show vrrp</td></tr><tr><td colspan="2">----</td></tr><tr><td colspan="2">virtual route id: 1</td></tr><tr><td colspan="2">ip address: 160.1.1.101</td></tr><tr><td colspan="2">mac address: 00:00:5e:00:01:01</td></tr><tr><td colspan="2">current state: master</td></tr><tr><td colspan="2">priority: 100</td></tr><tr><td colspan="2">preempt: on</td></tr><tr><td colspan="2">adver_int: 1s</td></tr><tr><td colspan="2">auth mode: none</td></tr></table>

Remove a virtual router

<table><tr><td>Description</td><td colspan="3">Remove a virtual route on a specified VLAN interface.</td></tr><tr><td>Prerequisite</td><td colspan="3">A virtual router has been built.</td></tr><tr><td>Syntax</td><td colspan="3">vrrp del vrid &lt;1-255&gt;</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;1-255&gt; Specifies the virtual router id.</td></tr><tr><td>Output</td><td colspan="3">Information about operation result.</td></tr></table>

# Example

ADLINK(fabric)# vrrp del vrid 1 rmv virtual route succeed!

Set virtual router priority

<table><tr><td>Description</td><td colspan="3">Set a virtual router priority value.</td></tr><tr><td>Prerequisite</td><td colspan="3">A virtual router has been built.</td></tr><tr><td>Syntax</td><td colspan="3">vrrp vrid &lt;1-255&gt; priority &lt;1-254&gt;</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;1-255&gt; Specifies the virtual router id.&lt;1-254&gt; Specifies the virtual router priority value.</td></tr><tr><td>Output</td><td colspan="3">Information about operation result.</td></tr></table>

# Example

ADLINK(fabric)# vrrp vrid 1 priority 99

set virtual route priority succeed!

ADLINK(fabric)# show vrrp

---------- ----------

virtual route id: 1

ip address: 160.1.1.101

mac address: 00:00:5e:00:01:01

current state: master

priority: 99

preempt: on

adver\_int: 1s

auth mode: none

Set virtual router preemption on/off

<table><tr><td>Description</td><td colspan="3">Set a virtual router preemption switch on/off</td></tr><tr><td>Prerequisite</td><td colspan="3">A virtual router has been built.</td></tr><tr><td>Syntax</td><td colspan="3">vrrp vrid &lt;1-255&gt; preemption</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;1-255&gt; Specifies the virtual router id.&lt;on/off&gt; Specifies the virtual router preemption switch state on/off.</td></tr><tr><td>Output</td><td colspan="3">Information about operation result.</td></tr></table>

# Example

```m4
ADLINK(fabric)# vrrp vrid 1 preemption off
set virtual preemption off succeed!
ADLINK(fabric)# show vrrp

virtual route id: 1
ip address: 160.1.1.101
mac address: 00:00:5e:00:01:01
current state: master
priority: 99
preempt: off
adver_int: 1s
auth mode: none
ADLINK(fabric)#
```

# 5.3.16 LLDP configuration

lldp show

<table><tr><td>Description</td><td colspan="3">Display LLDP info about local or neighbors.</td></tr><tr><td>Prerequisite</td><td colspan="3">LLDP has been resumed.</td></tr><tr><td>Syntax</td><td colspan="3">lldp show</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">indicate the target.</td></tr><tr><td>Output</td><td colspan="3">information about the target chassis.</td></tr></table>

# Example

```txt
ADLINK(fabric)# lldp show local
LOCAL CHASSIS:
----
CHASSISID: 00:30:64:43:eb:9d
SYSNAME: localhost
SYSDESC: Linux 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 x86_64
MGMTIP: fe80::230:64ff:fe13:3383
----
```

lldp pause

<table><tr><td>Description</td><td colspan="3">To stop LLDP feature with no more lldp PDU receive or send.</td></tr><tr><td>Prerequisite</td><td colspan="3">LLDP has been resumed.</td></tr><tr><td>Syntax</td><td colspan="3">Ildp resume</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Output</td><td colspan="3">N/A</td></tr></table>

lldp resume

<table><tr><td>Description</td><td colspan="3">To start receiving and sending LLDP PDU again.</td></tr><tr><td>Prerequisite</td><td colspan="3">LLDP has been paused</td></tr><tr><td>Syntax</td><td colspan="3">Ildp resume</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Output</td><td colspan="3">N/A</td></tr></table>

lldp txinterval

<table><tr><td>Description</td><td colspan="3">To set LLDP txinterval value.</td></tr><tr><td>Prerequisite</td><td colspan="3">LLDP has been resumed.</td></tr><tr><td>Syntax</td><td colspan="3">lldp txinterval &lt;5-32768&gt;</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;5-32768&gt; indicate the txinterval value.</td></tr><tr><td>Output</td><td colspan="3">operation result</td></tr></table>

# Example

ADLINK(fabric)# lldp txinterval 6 set lldp tx\_interval successfully!

lldp txhold

<table><tr><td>Description</td><td colspan="3">To set LLDP txhold value.</td></tr><tr><td>Prerequisite</td><td colspan="3">LLDP has been resumed.</td></tr><tr><td>Syntax</td><td colspan="3">vrrp txhold &lt;2-10&gt;</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">&lt;2-10&gt; indicate the lldp txhold value.</td></tr><tr><td>Output</td><td colspan="3">operation result.</td></tr></table>

# Example

ADLINK(fabric)# lldp txhold 3 set lldp tx\_hold successfully!

lldp update

<table><tr><td>Description</td><td colspan="3">To refresh neighbor information by sending a LLDP PDU immediately.</td></tr><tr><td>Prerequisite</td><td colspan="3">Ildp has been resumed.</td></tr><tr><td>Syntax</td><td colspan="3">Ildp update</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Output</td><td colspan="3">N/A</td></tr></table>

# 5.3.17 SNMP Configuration

SNMP is an application-layer protocol that provides a message format for communication between managers and agents. The SNMP system consists of an SNMP manager, an SNMP agent, and a MIB.

The SNMP manager can be part of a network management system (NMS). The agent and MIB reside on the switch. To configure SNMP on the switch, you define the relationship between the manager and the agent.

The SNMP agent contains MIB variables whose values the SNMP manager can request or change. A manager can get a value from an agent or store a value into the agent. The agent gathers data from the MIB, the repository for information about device parameters and network data. The agent can also respond to a manager’s requests to get or set data.

An agent can send unsolicited traps to the manager. Traps are messages alerting the SNMP manager to a condition on the network. Traps can mean improper user authentication, restarts, link status (up or down), MAC address tracking, closing of a TCP connection, loss of connection to a neighbor, or other significant events.

# SNMP Versions

This software release supports these SNMP versions:

• SNMPv1—The Simple Network Management Protocol, a Full Internet Standard, defined in
RFC 1157.
SNMPv2C replaces the Party-based Administrative and Security Framework of SNMPv2Classic with the community-string-based Administrative Framework of SNMPv2C while retaining the bulk retrieval and improved error handling of SNMPv2Classic. It has these features:
• SNMPv2—Version 2 of the Simple Network Management Protocol, a Draft Internet Standard,
defined in RFCs 1902 through 1907.
SNMPv2C—The community-string-based Administrative Framework for SNMPv2, an Experimental Internet Protocol defined in RFC 1901.
SNMPv3—Version 3 of the SNMP is an interoperable standards-based protocol defined in RFCs 2273 to 2275. SNMPv3 provides secure access to devices by authenticating and encrypting packets over the network and includes these security features:

– Message integrity—ensuring that a packet was not tampered with in transit
– Authentication—determining that the message is from a valid source
Encryption—mixing the contents of a package to prevent it from being read by an unauthorized source.

Both SNMPv1 and SNMPv2C use a community-based form of security. The community of managers able to access the agent’s MIB is defined by an IP address access control list and password.

SNMPv2C includes a bulk retrieval mechanism and more detailed error message reporting to management stations. The bulk retrieval mechanism retrieves tables and large quantities of information, minimizing the number of round-trips required. The SNMPv2C improved error-handling includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes in SNMPv2C report the error type.

SNMPv3 provides for both security models and security levels. A security model is an authentication strategy set up for a user and the group within which the user resides. A security level is the permitted level of security within a security model. A combination of the security level and the security model determine which security mechanism is used when handling an SNMP packet. Available security models are SNMPv1, SNMPv2C, and SNMPv3.

# Using SNMP to Access MIB Variables

An example of an NMS is the MibBrowser as network management software. MibBrowser software uses the switch MIB variables to set device variables and to poll devices on the network for specific information. The results of a poll can be displayed as a graph and analyzed to troubleshoot internetworking problems, increase network performance, verify the configuration of devices, monitor traffic loads, and more.

As shown in Figure 25-1, the SNMP agent gathers data from the MIB. The agent can send traps, or notification of certain events, to the SNMP manager, which receives and processes the traps. Traps alert the SNMP manager to a condition on the network such as improper user authentication, restarts, link status (up or down), MAC address tracking, and so forth. The SNMP agent also responds to MIB-related queries sent by the SNMP manager in get-request, get-next-request, and set-request format.

![The diagram depicts a communication flow between two entities:\n\n**Left Entity:**\n*   **Top Label:** NMS\n*   **Image:** A computer icon.\n*   **Bottom Label:** SNMP Manager\n\n**Right Entity:**\n*   **Top Label:** Network device\n*   **Image:** A server icon.\n*   **Bottom Labels:** MIB and SNMP Agent\n\n**Connections:**\n*   **Top Arrow (Left to Right):** Labeled with the text 'Get-request, Get-next-request, Get-bulk, Set-request'.\n*   **Bottom Arrow (Right to Left):** Labeled with the text 'Get-response, traps'.](.packetmanager-manual-en-20170818-v2/f558a71b201980ebf0cb9884d8326d799ef12f2b523af8365bb985aacb38a4fc.jpg)

Figure 25-1 SNMP Network

This example shows how to configure SNMP characteristics.

Set SNMP trap receiver address as below:

Vi /usr/share/snmp/snmpd.conf

…

\####

#notification configuration

trap2sink 172.99.1.251:162 public

informsink 172.99.1.251:162 public

# 5.3.18 Event log configuration

The event log can support remote logging via Linux syslog mechanism. The local logging can be retained when the remote logging is enabled. The remote logging debug level configuration is independent of the local debugging level, which means the user can configure different debug levels for local logging and remote logging respectively.

Log local

<table><tr><td>Description</td><td colspan="3">Local log enable or disable</td></tr><tr><td>Prerequisite</td><td colspan="3">none</td></tr><tr><td>Syntax</td><td colspan="3">log local enable</td></tr><tr><td>Option</td><td colspan="3">Enable : enable local logDisable : disable local log</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr></table>

# Example

ADLINK(fabric)# log local enable

Local log can be saved in below files:

root@aTCA-3710:/usr/local# ls -l

-rw-r----- 1 root root 532064390 Apr 23 00:33 adlink\_sx\_app.log

-rw-r--r-- 1 root root 146706717 Apr 23 00:33 adlink\_sx\_chassis.log

Log remote

<table><tr><td>Description</td><td colspan="4">remote log set</td></tr><tr><td>Prerequisite</td><td colspan="4">none</td></tr><tr><td>Syntax</td><td colspan="4">log remote</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td rowspan="3">Options</td><td>debuglevel</td><td colspan="3">Specifies the remote debug level</td></tr><tr><td>hostip</td><td colspan="3">Receiving host ip setting</td></tr><tr><td>enable/disable</td><td colspan="3">Enable /disable remote log</td></tr></table>

# Example

1. For remote log setting:

1) Login the receiving host and enter log configuration file.(e.g, syslog.conf )
2) Create a file name and file path for remote log receiving.
3) Run Linux syslog process.

For example:

The receiver machine is a Red hat Linux server 192.168.25.213

root@aTCA-receiver:/etc# vi syslog.conf

….

local7.debug

-/home/root/z0506.log

root@aTCA-receiver:/etc# syslogd -r

4) Login the log sender card and specify the hostip and debug level on which to collect event logs, and enter remote log enable mode.

ADLINK# log remote debuglevel 7

ADLINK# log remote hostip 192.168.25.213

ADLINK# log remote enable

5) View the event log successfully in the receiver machine.

root@aTCA-receiver:/etc# cat /home/root/z0506.log

May 9 18:17:53 aTCA-3710 SX\_Controller: unit=1,port=11

May 9 18:17:53 aTCA-3710 SX\_Controller: Link status : Up

May 9 18:29:03aTCA-3710 SX\_Controller: USER:127.0.0.1

COMMAND:show vlan

# 5.3.19 RPC CMM Configuration

RPC CMM (chassis manage module) is an application running on CSA-7400 switch COME, which enable user to manage the CSA-7400 chassis (Ex: reset / reading sensor / hot-plug, etc.) remotely by providing RPC APIs; It will transfer the RPC CMM APIs to IPMI message, and forward the IPMI message to CSA-7400 CMM through KCS interface.

![The diagram illustrates a system architecture flowing from left to right:\n\n**External Components:**\n*   On the far left, a **user icon** connects via a double-headed arrow to a **server icon**.\n*   The **server icon** connects via a double-headed arrow labeled '**Ethernet UDP/TCP message**' to a **router icon** (cylinder with red arrows).\n*   The **router icon** connects via a double-headed arrow labeled '**Ethernet UDP/TCP message**' to a large purple box labeled '**CSA-7400 Chassis**'.\n\n**Inside the CSA-7400 Chassis:**\n*   The router connects to a block labeled '**COME CMM RPC server**'.\n*   '**COME CMM RPC server**' connects via a double-headed arrow labeled '**KCS intf**' to a block labeled '**CMM**'.\n*   '**CMM**' connects via a double-headed arrow to a horizontal bus bar labeled '**IPMB BUS**'.\n*   The '**IPMB BUS**' connects via four separate double-headed arrows to four blocks, each labeled '**CPU board**'.](.packetmanager-manual-en-20170818-v2/6dd0a443da5f0630a1f4ad414ce9fd5f0035fc8cca66fd7ea911fee1f13887c6.jpg)

# Enable the CMM function

To enable the RPC CMM function， it needs to meet below conditions

Hardware requirement
The switch board must be MXN-3610/MXN-4100 A2;

Software requirement

COME BIOS: must be v0.92 or above;

COME OS: must be Centos 7.1;

Package manage:must be version v638 or above;

CMM FW: must be version v3.0 or above;

IPMI raw send command

<table><tr><td>Description</td><td colspan="4">Send IPMI raw command to miniBMC of CPU board or CMM of Switch board.</td></tr><tr><td>Prerequisite</td><td colspan="4">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="4">raw</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3">shelf =&gt;to CMM, board_x=&gt;to CPU board, for example, board_0 means CPU board plugged in slot 0;</td></tr><tr><td></td><td></td><td colspan="3">Standard ipmi message in hex format</td></tr></table>

# Example

Read the CMM board’s id.

<table><tr><td>ADLINK(cmm)# raw shelf 0x06 0x0120 01 03 01 02 bf 13 5f 00 10 36 dd 0b 01 00.ADLINK(cmm)#</td></tr></table>

Set RRC hotplug state

<table><tr><td>Description</td><td colspan="4">This function is used to send ipmi command to tell CMM its hotswap state by CPU board.</td></tr><tr><td>Prerequisite</td><td colspan="4">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="2">set_hotplug_state</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3">0x0 =&gt;RRC ready, 0x1=&gt;RRC is requested to hotplug, 0x3=&gt;CPU board handle hotplug request success, 0x4=&gt;CPU board handle hotplug failed;</td></tr><tr><td></td><td></td><td colspan="3">1~4 for 7400 chassis</td></tr></table>

# Example

CPU board\_1 tells it has handle the hotplug request done success.

ADLINK(cmm)# set\_hotplug\_state 0x3 0x1 Set hotswap sate: CPU node 1, msg\_type 3. ADLINK(cmm)#

Get RRC hotplug state

<table><tr><td>Description</td><td colspan="4">This function is used to send ipmi command to get CMM&#x27;s hotswap state by CPU board.</td></tr><tr><td>Prerequisite</td><td colspan="4">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="4">get_hotplug_state</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>N/A</td><td colspan="3"></td></tr><tr><td>Response</td><td>Msg_type</td><td colspan="3">0x0 =&gt;RRC ready, 0x1=&gt;RRC is requested to hotplug, 0x3=&gt;CPU board handle hotplug request success, 0x4=&gt;CPU board handle hotplug failed;</td></tr></table>

# Example

Read the hotplug state from CMM.

ADLINK(cmm)# get\_hotplug\_state Get hotswap sate: msg\_type 3. ADLINK(cmm)#

Reset payload

<table><tr><td>Description</td><td colspan="4">This function is used to send ipmit raw command to BMC of CPU board or Switch board.</td></tr><tr><td>Prerequisite</td><td colspan="4">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="4">reset</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td></td><td colspan="3">shelf =&gt;to CMM, board_x=&gt;to CPU board, for example, board_0 means CPU board plugged in slot 0</td></tr><tr><td></td><td></td><td colspan="3">0 - power down; 1 - power up; 2 - powercycle; 3 - hard reset; 5 - soft shutdown</td></tr><tr><td>Response</td><td colspan="4">N/A</td></tr></table>

# Example

Reset CPU board on slot 1.

```txt
ADLINK(cmm)# reset board_1
ADLINK(cmm)#
```

Get payload slot mask

<table><tr><td>Description</td><td colspan="3">This function is used to tell how may CPU boards are plugin in, and in which slot.</td></tr><tr><td>Prerequisite</td><td colspan="3">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="3">chassis slot</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Response</td><td colspan="3">N/A</td></tr></table>

# Example

Read the information of how many CPU boards plugged in chaiss .

<table><tr><td colspan="2">ADLINK(cmm)# chassis slot</td></tr><tr><td colspan="2">Slot 1 is empty</td></tr><tr><td colspan="2">Slot 2 is empty</td></tr><tr><td colspan="2">Slot 3 is occupied</td></tr><tr><td colspan="2">Slot 4 is empty</td></tr><tr><td colspan="2">Slot 5 is empty</td></tr><tr><td colspan="2">Slot 6 is empty</td></tr><tr><td colspan="2">Slot 7 is empty</td></tr><tr><td colspan="2">Slot 8 is empty.</td></tr><tr><td colspan="2">Chassis&#x27;Total Slots: 8</td></tr><tr><td colspan="2">CPU Board Inserted: 1</td></tr><tr><td colspan="2">Empty Slot: 7</td></tr><tr><td colspan="2">ADLINK(cmm)#</td></tr></table>

Get switch board number

<table><tr><td>Description</td><td colspan="3">This function is used to tell how may Switch board was plugin.</td></tr><tr><td>Prerequisite</td><td colspan="3">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="3">chassis switch</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Response</td><td colspan="3">N/A</td></tr></table>

# Example

Read the information of how many switch boards plugged in chaiss .

<table><tr><td>ADLINK(cmm)# chassis switchChassis&#x27; Switch Number: 2ADLINK(cmm)#</td></tr></table>

Get chassis ID

<table><tr><td>Description</td><td colspan="4">This function is used to read the chassis ID, such as the serial number of the chassis.</td></tr><tr><td>Prerequisite</td><td colspan="4">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="4">chassis id</td></tr><tr><td rowspan="2">Applies to</td><td colspan="2">aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td colspan="2">MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>N/A</td><td colspan="3"></td></tr><tr><td>Response</td><td>N/A</td><td colspan="3"></td></tr></table>

# Example

Read the CSA-7400 chassis id.

<table><tr><td>ADLINK(cmm)# chassis switchThis Chassis ID: 55 66ADLINK(cmm)#</td></tr></table>

Get CMM state and slot ID

<table><tr><td>Description</td><td colspan="3">This function is used to tell which SW slot current Switch is plugin, and whether the CMM is main or standalone.</td></tr><tr><td>Prerequisite</td><td colspan="3">See above section “Enable the CMM function”.</td></tr><tr><td>Syntax</td><td colspan="3">shelf state</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td colspan="3">N/A</td></tr><tr><td>Response</td><td colspan="3">N/A</td></tr></table>

# Example

Read the CSA-7400 chassis id.

<table><tr><td colspan="2">ADLINK(cmm)# shelf state</td></tr><tr><td colspan="2">Slot ID : Slot-1</td></tr><tr><td colspan="2">Shelf state : Main</td></tr></table>

# 5.3.20 Transceiver module configuration

The following commands are available for configuring port parameters.

Show Transceiver module

<table><tr><td>Description</td><td colspan="3">Show Transceiver module information.</td></tr><tr><td>Prerequisite</td><td colspan="3">None</td></tr><tr><td>Syntax</td><td colspan="3">show transceiver module PORT_LIST|PORT_ID</td></tr><tr><td rowspan="2">Applies to</td><td>aTCA-3710</td><td>aTCA-N700</td><td>aTCA-3430</td></tr><tr><td>MXN-3610/MXN-4100</td><td>cPCI-6S10</td><td>MXN-0410</td></tr><tr><td>Options</td><td>PORT_LIST|PORT_ID</td><td colspan="2">Port id list or port id. eg: xe1 or xe1,xe3 or xe1-xe3.</td></tr></table>

Example

<table><tr><td colspan="2">ADLINK(fabric)# show transceiver module xe1,xe2-xe3</td></tr><tr><td colspan="2">----Module xe1 Information----</td></tr><tr><td>Name</td><td>: xe1</td></tr><tr><td>Install</td><td>: YES</td></tr><tr><td>Identifier</td><td>: SFP</td></tr><tr><td>Connector Type</td><td>: LC</td></tr><tr><td>Transceiver Type</td><td>: Multiple Module</td></tr><tr><td>Vendor Name</td><td>: FINISAR CORP.</td></tr><tr><td>Vendor PN</td><td>: FTLX8571D3BCL</td></tr><tr><td>Vendor SN</td><td>: MTL1J31</td></tr><tr><td>Vendor Rev</td><td>: A</td></tr><tr><td>Vendor DateCode</td><td>: 150522</td></tr><tr><td>Vendor OUI</td><td>: 0x009065</td></tr><tr><td>Temperature</td><td>: 27.1C</td></tr><tr><td>VCC</td><td>: 3.31V</td></tr><tr><td>Tx Bias Current</td><td>: 7.60mA</td></tr><tr><td>Tx Output Power</td><td>: 575.1uW</td></tr><tr><td>Rx Power</td><td>: 485.4uW</td></tr><tr><td colspan="2">----Module xe2 Information----</td></tr><tr><td>Name</td><td>: xe2</td></tr><tr><td>Install</td><td>: NO</td></tr><tr><td>Identifier</td><td>: Unknown</td></tr><tr><td>Connector Type</td><td>: Unknown</td></tr><tr><td>Transceiver Type</td><td>: UnKnown</td></tr><tr><td>Vendor Name</td><td>:</td></tr><tr><td>Vendor PN</td><td>:</td></tr><tr><td>Vendor SN</td><td>:</td></tr><tr><td>Vendor Rev</td><td>:</td></tr><tr><td>Vendor DateCode</td><td>:</td></tr><tr><td>Vendor OUI</td><td>: 0x000000</td></tr><tr><td>Temperature</td><td>: 0.0C</td></tr><tr><td>VCC</td><td>: 0.00V</td></tr><tr><td>Tx Bias Current</td><td>: 0.00mA</td></tr><tr><td>Tx Output Power</td><td>: 0.0uW</td></tr><tr><td>Rx Power</td><td>: 0.0uW</td></tr><tr><td colspan="2">----Module xe3 Information----</td></tr><tr><td>Name</td><td>: xe3</td></tr><tr><td>Install</td><td>: YES</td></tr><tr><td>Identifier</td><td>: SFP</td></tr><tr><td>Connector Type</td><td>: LC</td></tr><tr><td>Transceiver Type</td><td>: Single Module</td></tr><tr><td>Vendor Name</td><td>: FINISAR CORP.</td></tr><tr><td>Vendor PN</td><td>: FTLF1318P2BCL</td></tr><tr><td>Vendor SN</td><td>: PRR44BT</td></tr><tr><td>Vendor Rev</td><td>: A</td></tr><tr><td>Vendor DateCode</td><td>: 140624</td></tr><tr><td>Vendor OUI</td><td>: 0x009065</td></tr><tr><td>Temperature</td><td>: 0.0C</td></tr><tr><td>VCC</td><td>: 0.00V</td></tr><tr><td>Tx Bias Current</td><td>: 0.00mA</td></tr><tr><td>Tx Output Power</td><td>: 0.0uW</td></tr><tr><td>Rx Power</td><td>: 0.0uW</td></tr><tr><td colspan="2">ADLINK(fabric)#</td></tr></table>

# 6 DHCP

This chapter describes switch blades how to configure the DHCP server /relay features using dhcpd/dhcrelay procedure and PacketManager. The switch blades have provided the dhcpd/dhcrelay service already. we can use the dhcpd/dhcrelay command directly.

# 6.1 DHCP SEVER CONFIG

# 6.1.1 Server Configuration

# Create VLAN interface

We configure the DHCP server to IP address range192.168.1.0/24 as an example.

```txt
##Fabric vlan-config
vlan add 1 cpu0 tag
##Fabric L3_intf-config
ip vlan-interface 1 address 192.168.1.110/24
##Fabric route-config (NOTE :this is for the dhcp relay example)
route add 192.168.2.1/24 192.168.1.10 1
```

# Edit the dhcpd.conf file

We need to edit the dhcpd.conf file to configure the port. The file is under the directory /etc/.

```txt
class "ge0" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge0";
}

class "ge1" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge1";
}

class "ge2" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge2";
}

class "xe0" {
    match if substring (option dhcp-client-identifier, 0, 3) = "xe0";
}

class "xe1" {
    match if substring (option dhcp-client-identifier, 0, 3) = "xe1";
}

shared-network hostname {
    subnet 192.168.1.0 netmask 255.255.255.0 {
    option domain-name "rrc.org";
    option domain-name-servers 192.168.2.22, 192.168.2.21;
    option routers 192.168.1.1;
    option subnet-mask 255.255.255.0;
    default-lease-time 21600;
    max-lease-time 43200;
    }
}
```

```txt
pool {
    allow members of "ge0";
    range 192.168.1.11 192.168.1.20;
}

pool {
    allow members of "ge1";
    range 192.168.1.21 192.168.1.30;
}

pool {
    allow members of "ge2";
    range 192.168.1.31 192.168.1.31;
}

pool {
    allow members of "xe0";
    range 192.168.1.41 192.168.1.42;
}

pool {
    allow members of "xe1";
    range 192.168.1.51 192.168.1.52;
}
```

Note : The class "ge0" is the name of the switch port ID.

# Start DHCP service

```txt
[root@cpci-6s10 home]#dhcpd
Internet Systems Consortium DHCP Server 4.2.6
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Wrote 0 class decls to leases file.
Wrote 0 leases to leases file.
Listening on LPF/f.vlan.1/00:30:64:06:a5:1b/hostname
Sending on LPF/f.vlan.1/00:30:64:06:a5:1b/hostname
...
[root@cpci-6s10 home]#
```

# 6.1.2 Client configuration

It is assumed that the port “eth0” of the CPU blade is connected to the port “ge0” of the switch blade.

```ini
[root@localhost ~]# dhclient -I ge0 eth0
[root@cpci-6s10 ~]#ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:64:2B:1B:27
inet addr:192.168.1.11 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1347 errors:0 dropped:0 overruns:0 frame:0
TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
Interrupt:234 Base address:0x2000
[root@cpci-6s10 ~]
```

The eth0 of cpu blade has got the ip 192.168.1.11.

# 6.2 DHCP RELAY CONFIG

# 6.2.1 Network topology

we can connect the switches topology as blew:

![Based on the provided image, here is the description of the flowchart:\n\n**Labeled Blocks:**\n*   **Left:** A blue cube icon with arrows pointing outward, labeled below as 'SWitch A' and further below as 'DHCP Sever'.\n*   **Center:** A blue cube icon with arrows pointing outward, labeled below as 'SWitch B' and further below as 'DHCP relay'.\n*   **Right:** An icon of a laptop computer.\n\n**Connections:**\n*   **Connection 1:** A black arrow points from 'SWitch A' to the right, towards 'SWitch B'. Above this arrow is the text: 'vlan1: 192.168.1.0/24'.\n*   **Connection 2:** A black arrow points from the laptop towards the left, connecting to 'SWitch B'. Above this arrow is the text: 'vlan2: 192.168.2.0/24'.](.packetmanager-manual-en-20170818-v2/1c5c7e4f3ab225eedf921e6ba32f3c58938805003c8e06de2aa6be7559b0ff8a.jpg)

# 6.2.2 Server Configuration

Start the DHCP server service on switch A using the commands in the above chapter(7.1.1), and modify the dhcpd.conf file :

```txt
class "ge0" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge0";
}
class "ge1" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge1";
}
class "ge2" {
    match if substring (option dhcp-client-identifier, 0, 3) = "ge2";
}
class "xe0" {
    match if substring (option dhcp-client-identifier, 0, 3) = "xe0";
}
class "xe1" {
    match if substring (option dhcp-client-identifier, 0, 3) = "xe1";
}
subnet 192.168.1.0 netmask 255.255.255.0 {
    option domain-name "rrc.org";
    option domain-name-servers 192.168.2.22, 192.168.2.21;
    option routers 192.168.1.110;
    option subnet-mask 255.255.255.0;
    default-lease-time 21600;
    max-lease-time 43200;

    pool {
    allow members of "ge0";
    range 192.168.1.11 192.168.1.20;
    }
    pool {
    allow members of "ge1";
    range 192.168.1.21 192.168.1.30;
    }
    pool {
    allow members of "ge2";
    range 192.168.1.31 192.168.1.31;
    }
    pool {
    allow members of "xe0";
    range 192.168.1.41 192.168.1.42;
    }
    pool {
    allow members of "xe1";
    range 192.168.1.51 192.168.1.52;
    }
}
```

```solidity
subnet 192.168.2.0 netmask 255.255.255.0 {
    option domain-name "rrc.org";
    option domain-name-servers 192.168.2.22, 192.168.2.21;
    option routers 192.168.2.1;
    option subnet-mask 255.255.255.0;
    default-lease-time 21600;
    max-lease-time 43200;
    pool {
    allow members of "ge0";
    range 192.168.2.11 192.168.2.20;
    }
    pool {
    allow members of "ge1";
    range 192.168.2.21 192.168.2.30;
    }
    pool {
    allow members of "ge2";
    range 192.168.2.31 192.168.2.31;
    }
    pool {
    allow members of "xe0";
    range 192.168.2.41 192.168.2.42;
    }
    pool {
    allow members of "xe1";
    range 192.168.2.51 192.168.2.52;
    }
}
```

```txt
pool {
    allow members of "ge0";
    range 192.168.2.11 192.168.2.20;
}
pool {
    allow members of "ge1";
    range 192.168.2.21 192.168.2.30;
}
pool {
    allow members of "ge2";
    range 192.168.2.31 192.168.2.31;
}
pool {
    allow members of "xe0";
    range 192.168.2.41 192.168.2.42;
}
pool {
    allow members of "xe1";
    range 192.168.2.51 192.168.2.52;
}
```

# 6.2.3 Relay Configuration

Create vlan interface
```txt
##Fabric port-config
port ge2 pvlan 2

##Fabric vlan-config
vlan 1 port cpu0 tag
vlan 2 enable
vlan 2 port ge2 untag
vlan 2 port cpu0 tag

##Fabric L3_intf-config
ip vlan-interface 1 address 192.168.1.10/24
ip vlan-interface 2 address 192.168.2.1/24
```

# Start DHCP relay service

[root@cpci-6s10 \~]#dhcrelay 192.168.1.110

Internet Systems Consortium DHCP Relay Agent 4.2.6

Copyright 2004-2014 Internet Systems Consortium.

All rights reserved.

For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/f.vlan.2/00:30:64:27:c1:1a

Sending on LPF/f.vlan.2/00:30:64:27:c1:1a

Listening on LPF/f.vlan.1/00:30:64:27:c1:1a

Sending on LPF/f.vlan.1/00:30:64:27:c1:1a

Listening on LPF/eth0/00:30:64:2b:1b:27

Sending on LPF/eth0/00:30:64:2b:1b:27

Sending on Socket/fallback

[root@cpci-6s10 \~]#

# 6.2.4 Client Configuration

It is assumed that the port “eth0” of the CPU blade is connected to the port “ge0” of the switch blade.

[root@localhost \~]# dhclient –I ge0 eth0

[root@cpci-6s10 \~]#ifconfig

eth0 Link encap:Ethernet HWaddr 00:30:64:2B:1B:27

inet addr:192.168.2.11 Bcast:0.0.0.0 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1347 errors:0 dropped:0 overruns:0 frame:0

TX packets:191 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

Interrupt:234 Base address:0x2000

The CPU blade manager port will get the IP 192.168.2.11 .

# 7 Boot Configuration File

Except the default configuration file (/etc/vtysh.conf) we saved by the CLI. We provide two configuration file at the boot folder (/usr/local/bcm/). When the PacketManager starting, it will load one of them according to the slot number of the switch blade.

Note that this feature can only work on cPCI-6S10.

# File naming rules

The boot configuration files are named as “adlink\_boot\_config\_xx”. “xx” is two bit lowercase hexadecimal digits. Such as: 08, 0c and so on. The value of the digits is the slot number got by the command “ ipmitool raw 0x30 0xF0” (Second bytes of results). When the PacketManager starting, it will execute this command and get the slot number. Then, it will load the file with the specific name.

```ini
[root@cpci-6s10 ~]#ipmitool raw 0x30 0xf0
be 09 01
[root@localhost ~]#ls /usr/local/bcm/adlink_boot_config_adlink_boot_config_08 adlink_boot_config_09
[root@localhost ~]#
```

Note: If the IPMI command reports the following error information, you need to install the IPMC FW. You can refer to the user manual of the cPCI-6S10 or ask the local FAE for help.

```txt
[root@cpci-6s10 ~]#ipmitool raw 0x30 0xF0
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
[root@localhost ~]#
```

# Configuration rules

The boot configuration files has the same format as the default configuration file. So we can refer to the configure guide of CLI to write this file.

```tcl
#Wrote on Thu Jan 1 00:39:37 1970
!
fabric
    ##Fabric port-config
    port ge0 pvlan 100
    port ge1 pvlan 200
    port ge2 pvlan 300

    ##Fabric vlan-config
    vlan 100 enable
    vlan add 100 cpu0 tag
    vlan add 100 ge0 untag

    vlan 200 enable
    vlan add 200 cpu0 tag
    vlan add 200 ge1 untag

    vlan 300 enable
    vlan add 300 cpu0 tag
    vlan add 300 ge2 untag

    ##Fabric L3_intf-config
    ip vlan-interface 100 address 10.10.1.1/24
    ip vlan-interface 200 address 10.10.2.1/24
    ip vlan-interface 300 address 10.10.3.1/24

    ##Fabric route-config
    route add 192.168.1.1/24 10.10.1.100 10
    route add 192.168.2.1/24 10.10.2.100 10
    route add 192.168.3.1/24 10.10.3.100 10

!
#End
```

Note: If the file format is incorrect, PacketManager may fail to start.

# Effective rules

When the PacketManager starts, it will load the default configuration file (/etc/vtysh.conf) firstly. The boot configuration file (/usr/local/adlink\_boot\_config\_xx) will load at the second step. So boot configuration will cover the default configuration.

# 8 Glossary

Most of the definitions found in this glossary can be found in various public and commercial websites.

# ACE

Access Control Entry. An ACE is a description of access rights associated with a user or process.

# ACL

An ACL is a list of permissions assigned to an object. The list describes which users or which processes are allowed to access and manipulate an object. An ACL is made up of ACEs.

# Bandwidth

A measurement of the information-carrying capacity of a line or a network. For digital devices, the bandwidth is usually expressed in bits per second (bps) or bytes per second. For analog devices, the bandwidth is expressed in cycles per second, or Hertz (Hz).

# bps

Bits per second. A measurement for determining transmission speed.

# Class of Service

Class of Service is a way of managing network traffic by grouping similar types of data (for example, e-mail, streaming video, voice, large document file transfer) and treating each type as a class with its own level of service priority. Class of Service technologies do not guarantee a level of service in terms of bandwidth and delivery time; they offer a “best-effort.” One can think of CoS as “coarsely-grained” traffic control and QoS (Quality of Service) as “finely-grained” traffic control.

# CoS

See Class of Service.

# CRC

Cyclic Redundancy Checking. A method of checking for errors in data that has been transmitted on a communications link. A sending device applies a 16- or 32-bit polynomial to a block of data that is to be transmitted and appends the resulting cyclic redundancy code (CRC) to the block. The receiving end applies the same polynomial to the data and compares its result with the result appended by the sender. If they agree, the data has been received successfully. If not, the sender can be notified to resend the block of data.

# Differentiated Services

Also known as DiffServ or Type of Service, is a field in the IP header that allows users to provide Quality of Service (QoS) for network traffic. See also Type of Service.

# Fast Ethernet

Fast Ethernet is a LAN transmission standard that provides a data rate of 100 megabits per second (referred to as 100BASE-T).

# ICMP

Internet Control Message Protocol. This protocol is used to transmit messages in IP networks. It also includes utilities such as ping and traceroute which are useful for diagnostic analysis of network connectivity.

# IEEE

Institute of Electrical and Electronics Engineers. The largest international non-profit, professional organization for the advancement of technology related to electricity.

# IGMP

Internet Group Management Protocol. A communications protocol that focuses on the membership of Internet Protocol multicast groups.

# IP

Internet Protocol. The computer networking protocol used on the Internet. IP may also stand for:Internet Provider (more commonly referred to as Internet Service Provider or ISP). A business or organization that offers users access to the Internet and related services.Intellectual Property. The legal term which encompasses copyrights, patents, trademarks, and trade secrets (amongst others).

# ITU

International Telecommunications Union. Created to standardize and regulate international radio and telecommunications. Originally (in 1865) formed as the International Telegraph Union, the ITU is one of the oldest active international organizations.

#

Kilobits per second

# LAN

Local Area Network. A computer network covering a local area, like a home, office or small group of buildings such as a college. When using ethernet, the computers are usually wired to a hub or to a switch. LANs can be interlinked via a router to form a Wide Area Network (WAN).

# MEF

The MEF (Metro Ethernet Forum) is a non-profit organization promoting the adoption of Carrier-class Ethernet networks and services. The Forum membership includes service providers, incumbent local exchange carriers, network equipment vendors such as Salira, test equipment vendors, and other networking companies that share an interest in metro Ethernet. (See Metro Ethernet Network.)

# MEN

Metro Ethernet Network. The Ethernet network created by service providers.

# MIB

Management Information Base. A database of network performance information (such as error counts and on/off information), stored on a Network Agent and retrieved by a Network Management Station (NMS).

# NE

Network Element, for example, a Salira 2500 Series terminal. A network element is telecommunications hardware equipment that is addressable and manageable. NEs provide support or services to the user and can be managed through an element manager (EMS). A group of interconnected network elements form a network.

# OSI

Open Systems Interconnection was a new effort in networking started in 1982 by the International Organization for Standardization (ISO), along with the ITU-T.Prior to OSI, networking was completely vendor-developed and proprietary, which lead to interoperability issues resulting from a lack of common protocols between network devices. OSI was a new industry effort, attempting to get everyone to agree to common network standards to provide multi-vendor interoperability.The OSI approach was eventually eclipsed by the Internets TCP/IP protocol suite. Its pragmatic approach to computer networking and independent implementations of simplified protocols made it a practical standard.

# RADIUS

Remote Authentication Dial-In User Service. A security service for authenticating and authorizing remote users.

# STP

Spanning Tree Protocol. A network management protocol that facilitates loop-free traffic forwarding for any bridged LAN.

# Type of Service

A system of seven traffic prioritization schemes.

# VLAN

Virtual Local Area Network. A group of devices on different physical LANs which can communicate with each other as if they were on the same physical LAN segment.

# Getting Service

Ask an Expert: http://askanexpert.adlinktech.com

# ADLINK Technology, Inc.

Address: 9F, No.166 Jian Yi Road, Zhonghe District

New Taipei City 235, Taiwan

新北市中和區建一路 166 號 9 樓

Tel: +886-2-8226-5877

Fax: +886-2-8226-5717

Email: service@adlinktech.com

# Ampro ADLINK Technology, Inc.

Address: 5215 Hellyer Avenue, #110, San Jose, CA 95138, USA

Tel: +1-408-360-0200

Toll Free: +1-800-966-5200 (USA only)

Fax: +1-408-360-0222

Email: info@adlinktech.com

# ADLINK Technology (China) Co., Ltd.

Address: 上海市浦东新区张江高科技园区芳春路 300 号 (201203)

300 Fang Chun Rd., Zhangjiang Hi-Tech Park, Pudong New Area

Shanghai, 201203 China

Tel: +86-21-5132-8988

Fax: +86-21-5132-3588

Email: market@adlinktech.com

# ADLINK Technology GmbH

Address: Hans-Thoma-Strasse 11, D-68163, Mannheim, Germany

Tel: +49-621-43214-0

Fax: +49-621 43214-30

Email: emea@adlinktech.com

Please visit the Contact page at www.adlinktech.com for information on how to contact the ADLINK regional office nearest you.
[🔗 Link to the original document](.packetmanager-manual-en-20170818-v2/packetmanager-manual-en-20170818-v2.pdf)