MS Series Layer 3 Switch Command Line Interface Guide - SnapAV

MS Series

LAYER 3 SWITCHES WITH OVRC

MS-1212, MS-2424, MS-2400, MS-2416, MS-4424

Command Line Interface Guide

Contents

1. CONSOLE AND TELNET ADMINISTRATION INTERFACE ..........................................................2

1.1.

Local Console Management ............................................................................2

1.2.

Set up Your Switch Using Console Access ........................................................3

1.3.

Set up Your Switch Using Telnet Access...........................................................4

2. COMMAND LINE INTERFACE STRUCTURE AND MODE-BASED CLI .........................................4

2.1.

CLI Command Format......................................................................................5

2.2.

CLI Mode-based Topology ...............................................................................6

3. SWITCHING COMMANDS......................................................................................................9

3.1.

System Information and Statistics Commands ................................................9

3.2.

Device Configuration Commands ..................................................................19

3.3.

Provisioning (IEEE 802.1p) Commands.........................................................102

3.4.

Management Commands ............................................................................103

3.5.

Spanning Tree Protocol Commands.............................................................143

3.6.

System Log Commands ...............................................................................161

3.7.

Script Management Commands ..................................................................171

3.8.

User Account Management Commands ......................................................176

3.9.

Port-based Network Access Control Commands..........................................186

3.10.

AAA Commands ..........................................................................................207

3.11.

RADIUS Commands .....................................................................................213

3.12.

TACACS+ Commands ...................................................................................235

3.13.

Security Commands ....................................................................................242

3.14.

SNTP (Simple Network Time Protocol) Commands......................................249

3.15.

LLDP (Link Layer Discovery Protocol) Commands ........................................258

3.16.

System Utilities ...........................................................................................270

3.17.

DHCP Snooping Commands.........................................................................292

3.18.

Dynamic ARP Inspection (DAI) Command....................................................306

3.19.

Differentiated Service Commands...............................................................312

3.20.

ACL Commands ...........................................................................................344

3.21.

IPv6 ACL Commands....................................................................................362

3.22.

CoS (Class of Service) Command..................................................................369

3.23.

Domain Name Server Relay Commands ......................................................370

3.24.

Time Zone Commands.................................................................................377

4. ROUTING COMMANDS .....................................................................................................380

4.1.

Address Resolution Protocol (ARP) Commands ...........................................380

4.2.

IP Routing Commands .................................................................................386

4.3.

VLAN Routing Commands ...........................................................................404

5. IP MULTICAST COMMANDS ..............................................................................................405

5.1.

Internet Group Management Protocol (IGMP) Commands..........................405

5.2.

IPv4 Protocol Independent Multicast (PIM) Commands ..............................415

1. Console and Telnet Administration Interface

This chapter discusses many of the features used to manage the Switch and explains many concepts and important points regarding these features. Configuring the Switch to implement these concepts is discussed in detail in later chapters. The command-line interface (CLI) provides a text-based way to manage and monitor the switch features. You can access the CLI by using a direct connection to the console port or by using a Telnet or SSH client. To access the switch by using Telnet or Secure Shell (SSH), the switch must have an IP address configured on the network interface, and the management station you use to access the device must be able to ping the switch IP address. DHCP is enabled by default on the network VLAN.

1.1. Local Console Management

Local console management involves the administration of the Switch via a direct connection to the RS-232 DCE console port. This is an Out-of-band connection, meaning that it is on a different circuit than normal network communications, and thus works even when the network is down. The local console management connection involves a terminal or PC running terminal emulation software to operate the Switch's built-in console program (see Chapter 5). Using the console program, a network administrator can manage, control, and monitor many functions of the Switch. Hardware components in the Switch allow it to be an active part of a manageable network. These components include a CPU, memory for data storage, other related hardware, and SNMP agent firmware. Activities on the Switch can be monitored with these components, while the Switch can be manipulated to carry out specific tasks.

2

1.2. Set up Your Switch Using Console Access

Out-of-band management requires connecting a terminal, such as a VT-100 or a PC running a terminalemulation program (such as HyperTerminal, which is automatically installed with Microsoft Windows) to the RS-232 DCE console port of the Switch. Switch management using the RS-232 DCE console port is called Local Console Management to differentiate it from management done via management platforms, such as DView or HP OpenView. Make sure the terminal or PC you are using to make this connection is configured to match these settings. If you are having problems making this connection on a PC, make sure the emulation is set to VT-100 or ANSI. If you still don't see anything, try pressing + r to refresh the screen.

First-time configuration must be carried out through a console, that is, either (a) a VT100-type serial data terminal, or (b) a computer running communications software set to emulate a VT100. The console must be connected to the Diagnostics port. This is an RS-232 port with a 9-socket D-shell connector and DCE-type wiring. Make the connection as follows: 1. Obtain suitable cabling for the connection. You can use a null-modem RS-232 cable or an ordinary RS-

232 cable and a null-modem adapter. One end of the cable (or cable/adapter combination) must have a 9-pin D-shell connector suitable for the Diagnostics port; the other end must have a connector suitable for the console's serial communications port. 2. Power down the devices, attach the cable (or cable/adapter combination) to the correct ports, and restore power. 3. Set the console to use the following communication parameters for your terminal: The console port is set for the following configuration: Baud rate: 115,200 Data width: 8 bits Parity: none Stop bits: 1 Flow Control: none

3

1.3. Set up Your Switch Using Telnet Access

Once you have set an IP address for your Switch, you can use a Telnet program (in a VT-100 compatible terminal mode) to access and control the Switch. The port number for Telnet is 23. Most of the screens are identical, whether accessed from the console port or from a Telnet interface.

1.3.1. Accessing the Switch CLI through the Network

Remote management of the switch is available through the network interface. To use telnet , SSH , or SNMP for switch management, the switch must be connected to the network, and you must know the IP or IPv6 address of the management interface. The switch has no IP address by default. The DHCP client on the network vlan is enabled, and the DHCP client on the network interface is disabled.

1.3.2. Using the Network Interface for Remote Management

You can manage the switch through the production network, which is known as in-band management, because in-band management traffic is mixed in with production network traffic, it is subject to all of the filtering rules usually applied on a switched/routed port such as ACLs and VLAN tagging. You can access the in-band network management interface through a connection to any front-panel port.

1.3.2.1. Configuring the In-Band Network Interface

To use a DHCP server to obtain the IP address, subnet mask, and default gateway information, use: network protocol dhcp

and Use below command to display the ip address information. Show network

2. Command Line Interface Structure and Mode-based CLI

The Command Line Interface (CLI) syntax, conventions, and terminology are described in this section. Each CLI command is illustrated using the structure outlined below.

4

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download