M6100 Series Switches - ネットギア【NETGEAR】 while performance and feature sets continue to improve. Devices that are capable of switching Layers 2, 3, and 4 are increasingly

350 East Plumeria DriveSan Jose, CA 95134USA

September 2014202-11457-02

M6100 Series SwitchesCLI Command Reference Manual

Sof tware Version 10.2.0

2

M6100 Series Switches

SupportThank you for selecting NETGEAR products.

After installing your device, locate the serial number on the label of your product and use it to register your product at https://my.netgear.com. You must register your product before you can use NETGEAR telephone support. NETGEAR recommends registering your product through the NETGEAR website. For product updates and web support, visit http://support.netgear.com.

Phone (US & Canada only): 1-888-NETGEAR.

Phone (Other Countries): Check the list of phone numbers at http://support.netgear.com/general/contact/default.aspx.

Contact your Internet service provider for technical support.

ComplianceFor regulatory compliance information, visit http://www.netgear.com/about/regulatory.

See the regulatory compliance document before connecting the power supply.

TrademarksNETGEAR, the NETGEAR logo, and Connect with Innovation are trademarks and/or registered trademarks of NETGEAR, Inc. and/or its subsidiaries in the United States and/or other countries. Information is subject to change without notice. NETGEAR, Inc. All rights reserved.

Revision History

Publication Part Number Publish Date Comments

202-11457-02 September 2014 Corrected the syntax of the {deny | permit} (IPv6) command. Added a note to all debug commands.

202-11457-01 August 2014 Initial publication of this manual.

https://my.netgear.comhttp://support.netgear.comhttp://support.netgear.com/general/contact/default.aspxhttp://www.netgear.com/about/regulatory/

Contents

Chapter 1 About the NETGEAR Managed Switch Software

Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Product Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Using the Command-Line Interface

Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Command Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Common Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12unit/slot/port Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Using the No Form of a Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Executing Show Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14CLI Output Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3 NETGEAR Managed Switch Software Modules

Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Command Completion and Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22CLI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22CLI Line-Editing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Using CLI Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Accessing the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 4 Chassis Commands

General Chassis Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Backplane Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Chassis Firmware Synchronization Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Nonstop Forwarding Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 5 Management Commands

Configure the Switch Management CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44CPU Queue Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Network Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Console Port Access Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Telnet Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Secure Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Management Security Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Management Access Control List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Hypertext Transfer Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3


Access Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76User Account Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Per-Command Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Exec Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107RADIUS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119TACACS+ Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Configuration Scripting Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Prelogin Banner, System Prompt, and Host Name Commands. . . . . . . . . . . . . 140

Chapter 6 Utility Commands

AutoInstall Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144CLI Output Filtering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Dual Image Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149System Information and Statistics Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 151Switch Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Logging Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Email Alerting and Mail Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189System Utility and Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Simple Network Time Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Time Zone Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213DHCP Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217DNS Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230IP Address Conflict Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Serviceability Packet Tracing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Support Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Cable Test Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Power Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273USB commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277sFlow Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Switch Database Management Template Commands . . . . . . . . . . . . . . . . . . . . 286Green Ethernet Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Remote Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Statistics Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Chapter 7 Switching Commands

Port Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Spanning Tree Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331VLAN Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Double VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Private VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Voice VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Provisioning (IEEE 802.1p) Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Asymmetric Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Protected Ports Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Private Group Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

4


GARP Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389GVRP Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391GMRP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Port-Based Network Access Control Commands . . . . . . . . . . . . . . . . . . . . . . . . 396802.1X Supplicant Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416Storm-Control Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420Link Local Protocol Filtering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427MRP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428MMRP Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429MSRP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432MVRP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Port-Channel/LAG (802.3ad) Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443VPC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462Port Mirroring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473Static MAC Filtering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476DHCP L2 Relay Agent Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480DHCP Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487DHCP Snooping Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488Dynamic ARP Inspection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498MVR Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505IGMP Snooping Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512IGMP Snooping Querier Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521MLD Snooping Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525MLD Snooping Querier Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533Port Security Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537LLDP (802.1AB) Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542LLDP-MED Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550Denial of Service Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558MAC Database Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568ISDP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570UniDirectional Link Detection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578Link Debounce Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Chapter 8 Data Center Commands

Data Center Bridging Exchange Protocol Commands . . . . . . . . . . . . . . . . . . . . 585Enhanced Transmission Selection and Traffic Class Group . . . . . . . . . . . . . . . . 592FIP Snooping Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597Priority-Based Flow Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

Chapter 9 Routing Commands

Address Resolution Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622IP Routing Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628Routing Policy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Router Discovery Protocol Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675Virtual LAN Routing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679Virtual Router Redundancy Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . 683DHCP and BootP Relay Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692

5


IP Helper Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694Open Shortest Path First Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

General OSPF Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702OSPF Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722IP Event Dampening Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

OSPF Graceful Restart Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731OSPFv2 Stub Router Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734OSPF Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

Routing Information Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756ICMP Throttling Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

Chapter 10 Captive Portal Commands

Captive Portal Global Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768Captive Portal Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Captive Portal Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782Captive Portal Client Connection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 784Captive Portal Interface Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787Captive Portal Local User Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789Captive Portal User Group Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796

Chapter 11 Border Gateway Protocol Commands

BGP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799Routing Policy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

Chapter 12 IPv6 Commands

IPv6 Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883Tunnel Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890Loopback Interface Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892IPv6 Routing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894OSPFv3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928

Global OSPFv3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928OSPFv3 Interface Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944OSPFv3 Graceful Restart Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949OSPFv3 Stub Router Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952OSPFv3 Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954

DHCPv6 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971DHCPv6 Snooping Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 983

Chapter 13 Quality of Service Commands

Class of Service Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995Differentiated Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1003DiffServ Class Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1004DiffServ Policy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1013DiffServ Service Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1020DiffServ Show Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1021

6


MAC Access Control List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1027IP Access Control List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1033IPv6 Access Control List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1047Time Range Commands for Time-Based ACLs . . . . . . . . . . . . . . . . . . . . . . . . .1054Auto-Voice over IP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1057iSCSI Optimization Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1062

Chapter 14 IP Multicast Commands

Multicast Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1070DVMRP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1076PIM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1081Internet Group Message Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . .1096IGMP Proxy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1104

Chapter 15 IPv6 Multicast Commands

IPv6 Multicast Forwarder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1111IPv6 PIM Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1115IPv6 MLD Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1129IPv6 MLD-Proxy Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1135

Chapter 16 Power over Ethernet Commands

About PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1142PoE Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1143

Chapter 17 NETGEAR Managed Switch Software Log Messages

Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1154Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1156Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1159Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1162QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1170Routing/IPv6 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1171Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1173Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1178Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1179O/S Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1181

Command List

7

1

1. About the NETGEAR Managed Switch Software

The NETGEAR Managed Switch software has two purposes:

Assist attached hardware in switching frames, based on Layer 2, 3, or 4 information contained in the frames.

Provide a complete device management portfolio to the network administrator.

This chapter contains the following sections:

Scope Product Concept

Note: For more information about the topics covered in this manual, visit the support website at support.netgear.com.

Note: Firmware updates with new features and bug fixes are made available from time to time at downloadcenter.netgear.com. Some products can regularly check the site and download new firmware, or you can check for and download new firmware manually. If the features or behavior of your product does not match what is described in this guide, you might need to update your firmware.

8

http://downloadcenter.netgear.comhttp://support.netgear.com


Scope

NETGEAR Managed Switch software encompasses both hardware and software support. The software is partitioned to run in the following processors:

CPU. This code runs the networking device management portfolio and controls the overall networking device hardware. It also assists in frame forwarding, as needed and specified. This code is designed to run on multiple platforms with minimal changes from platform to platform.

Networking device processor. This code does the majority of the packet switching, usually at wire speed. This code is platform dependent, and substantial changes might exist across products.

Product Concept

Fast Ethernet and Gigabit Ethernet switching continues to evolve from high-end backbone applications to desktop switching applications. The price of the technology continues to decline, while performance and feature sets continue to improve. Devices that are capable of switching Layers 2, 3, and 4 are increasingly in demand. NETGEAR Managed Switch software provides a flexible solution to these ever-increasing needs.

The exact functionality provided by each networking device on which the NETGEAR Managed Switch software base runs varies depending upon the platform and requirements of the NETGEAR Managed Switch software.

NETGEAR Managed Switch software includes a set of comprehensive management functions for managing both NETGEAR Managed Switch software and the network. You can manage the NETGEAR Managed Switch software by using one of the following three methods:

Command-line interface (CLI) Simple Network Management Protocol (SNMP) Web-based

About the NETGEAR Managed Switch Software

9

2

2. Using the Command-Line Interface

The command-line interface (CLI) is a text-based way to manage and monitor the system. You can access the CLI by using a direct serial connection or by using a remote logical connection with telnet or SSH.

This chapter describes the CLI syntax, conventions, and modes. It contains the following sections:

Command Syntax Command Conventions Common Parameter Values unit/slot/port Naming Convention Using the No Form of a Command Executing Show Commands CLI Output Filtering

10


Command Syntax

A command is one or more words that might be followed by one or more parameters. Parameters can be required or optional values.

Some commands, such as show network or clear vlan, do not require parameters. Other commands, such as network parms, require that you supply a value after the command. You must type the parameter values in a specific order, and optional parameters follow required parameters. The following example describes the network parms command syntax:

network parms ipaddr netmask [gateway]

network parms is the command name. ipaddr and netmask are parameters and represent required values that you must enter after you type the command keywords.

[gateway] is an optional parameter, so you are not required to enter a value in place of the parameter.

The CLI Command Reference Manual M6100 Series Switches lists each command by the command name and provides a brief description of the command. Each command reference also contains the following information:

Format shows the command keywords and the required and optional parameters. Mode identifies the command mode you must be in to access the command. Default shows the default value, if any, of a configurable setting on the device.

The show commands also contain a description of the information that the command shows.

Command Conventions

The parameters for a command might include mandatory values, optional values, or keyword choices. Parameters are order-dependent. The following table describes the conventions this document uses to distinguish between value types.

Table 1. Parameter Conventions

Symbol Example Description

[ ] square brackets [value] Indicates an optional parameter.

italic font in a parameter.

value or [value] Indicates a variable value. You must replace the italicized text, angle brackets, or square brackets with an appropriate value, which might be a name or number.

{ } curly braces {choice1 | choice2} Indicates that you must select a parameter from the list of choices.

| Vertical bars choice1 | choice2 Separates the mutually exclusive choices.

[{ }] Braces within square brackets

[{choice1 | choice2}] Indicates a choice within an optional element.

Using the Command-Line Interface

11


Common Parameter Values

Parameter values might be names (strings) or numbers. To use spaces as part of a name parameter, enclose the name value in double quotes. For example, the expression System Name with Spaces forces the system to accept the spaces. Empty strings () are not valid user-defined strings. The following table describes common parameter values and value formatting.

Table 2. Parameter Descriptions

Parameter Description

ipaddr This parameter is a valid IPv4 address. You can enter the IP address in the following formats: a (32 bits) a.b (8.24 bits) a.b.c (8.8.16 bits) a.b.c.d (8.8.8.8)In addition to these formats, the CLI accepts decimal, hexadecimal and octal formats through the following input formats (where n is any valid hexadecimal, octal or decimal number): 0xn (CLI assumes hexadecimal format.) 0n (CLI assumes octal format with leading zeros.) n (CLI assumes decimal format.)

ipv6-addr This parameter is a valid IPv6 address. You can enter the IP address in the following formats: FE80:0000:0000:0000:020F:24FF:FEBF:DBCB FE80:0:0:0:20F:24FF:FEBF:DBCB FE80::20F24FF:FEBF:DBCB FE80:0:0:0:20F:24FF:128:141:49:32For additional information, refer to RFC 3513.

Interface or unit/slot/port

Valid slot and port number separated by a forward slash. For example, 0/1 represents slot number 0 and port number 1.

Logical Interface Represents a logical slot and port number. This is applicable in the case of a port-channel (LAG). You can use the logical unit/slot/port to configure the port-channel.

Character strings Use double quotation marks to identify character strings, for example, System Name with Spaces. An empty string () is not valid.


12


unit/slot/port Naming Convention

NETGEAR Managed Switch software references physical entities such as cards and ports by using a unit/slot/port naming convention. The NETGEAR Managed Switch software also uses this convention to identify certain logical entities, such as Port-Channel interfaces.

The slot number has two uses. In the case of physical ports, it identifies the card containing the ports. In the case of logical and CPU ports it also identifies the type of interface or port.

The port identifies the specific physical port or logical interface being managed on a given slot.

Note: In the CLI, loopback and tunnel interfaces do not use the unit/slot/port format. To specify a loopback interface, you use the loopback ID. To specify a tunnel interface, you use the tunnel ID.

Table 3. Type of Slots

Slot Type Description

Physical slot numbers Physical slot numbers begin with zero, and are allocated up to the maximum number of physical slots.

Logical slot numbers Logical slots immediately follow physical slots and identify port-channel (LAG) or router interfaces. The value of logical slot numbers depend on the type of logical interface and can vary from platform to platform.

CPU slot numbers The CPU slots immediately follow the logical slots.

Table 4. Type of Ports

Port Type Description

Physical Ports The physical ports for each slot are numbered sequentially starting from one. For example, port 1 on slot 0 (an internal port) for a switch is 1/0/1, port 2 is 1/0/2, port 3 is 1/0/3, and so on.

Logical Interfaces Port-channel or Link Aggregation Group (LAG) interfaces are logical interfaces that are only used for bridging functions. VLAN routing interfaces are only used for routing functions.Loopback interfaces are logical interfaces that are always up.Tunnel interfaces are logical point-to-point links that carry encapsulated packets.

CPU ports CPU ports are handled by the driver as one or more physical entities located on physical slots.


13


Using the No Form of a Command

The no keyword is a specific form of an existing command and does not represent a new or distinct command. Almost every configuration command has a no form. In general, use the no form to reverse the action of a command or reset a value back to the default. For example, the no shutdown configuration command reverses the shutdown of an interface. Use the command without the keyword no to reenable a disabled feature or to enable a feature that is disabled by default. Only the configuration commands are available in the no form.

Executing Show Commands

All show commands can be issued from any configuration mode (Global Configuration, Interface Configuration, VLAN Configuration, etc.). The show commands provide information about system and feature-specific configuration, status, and statistics. Previously, show commands could be issued only in User EXEC or Privileged EXEC modes.

CLI Output Filtering

Many CLI show commands include considerable content to display to the user. This can make output confusing and cumbersome to parse through to find the information of desired importance. The CLI Output Filtering feature allows the user, when executing CLI show display commands, to optionally specify arguments to filter the CLI output to display only desired information. The result is to simplify the display and make it easier for the user to find the information the user is interested in.

The main functions of the CLI Output Filtering feature are:

Pagination Control- Supports enabling/disabling paginated output for all show CLI commands. When

disabled, output is displayed in its entirety. When enabled, output is displayed page-by-page such that content does not scroll off the terminal screen until the user presses a key to continue. --More-- or (q)uit is displayed at the end of each page.

- When pagination is enabled, press the return key to advance a single line, press q or Q to stop pagination, or press any other key to advance a whole page. These keys are not configurable.

Note: Although some NETGEAR Managed Switch show commands already support pagination, the implementation is unique per command and not generic to all commands.

Output Filtering- Grep-like control for modifying the displayed output to only show the user-desired

content.- Filter displayed output to only include lines containing a specified string match.


14


- Filter displayed output to exclude lines containing a specified string match.- Filter displayed output to only include lines including and following a specified

string match.- Filter displayed output to only include a specified section of the content (for

example, interface 0/1) with a configurable end-of-section delimiter.- String matching should be case insensitive.- Pagination, when enabled, also applies to filtered output.

The following shows an example of the extensions made to the CLI show commands for the Output Filtering feature.

(NETGEAR Switch) #show running-config ? Press enter to execute the command.| Output filter options. Script file name for writing active configuration.all Show all the running configuration on the switch.interface Display the running configuration for specificed interface on the switch.

(NETGEAR Switch) #show running-config | ?begin Begin with the line that matchesexclude Exclude lines that matchesinclude Include lines that matchessection Display portion of lines

For new commands for the feature, see CLI Output Filtering Commands on page 147.


15

3

3. NETGEAR Managed Switch Software Modules

NETGEAR Managed Switch software consists of flexible modules that can be applied in various combinations to develop advanced Layer 2/3/4+ products. The commands and command modes available on your switch depend on the installed modules. Additionally, for some show commands, the output fields might change based on the modules included in the NETGEAR Managed Switch software.

The NETGEAR Managed Switch software suite includes the following modules:

Switching (Layer 2) Routing (Layer 3) IPv6 routing Multicast BGP-4 Quality of Service Management (CLI, Web UI, and SNMP) IPv6 ManagementAllows management of the NETGEAR Managed Switch device

through an IPv6 through an IPv6 address without requiring the IPv6 Routing package in the system. The management address can be associated with the network port (front-panel switch ports), a routine interface (port or VLAN) and the Service port.

Metro Chassis management Data Center Secure Management

16


Command Modes

The CLI groups commands into modes according to the command function. Each of the command modes supports specific NETGEAR Managed Switch software commands. The commands in one mode are not available until you switch to that particular mode, with the exception of the User EXEC mode commands. You can execute the User EXEC mode commands in the Privileged EXEC mode.

The command prompt changes in each command mode to help you identify the current mode. The following table describes the command modes and the prompts visible in that mode.

Note: The command modes available on your switch depend on the software modules that are installed. For example, a switch that does not support BGPv4 does not have the BGPv4 Router Command Mode.

Table 5. CLI Command Modes

Command Mode Prompt Mode Description

User EXEC Switch> Contains a limited set of commands to view basic system information.

Privileged EXEC Switch# Allows you to issue any EXEC command, enter the VLAN mode, or enter the Global Configuration mode.

Global Config Switch (Config)# Groups general setup commands and permits you to make modifications to the running configuration.

VLAN Config Switch (Vlan)# Groups all the VLAN commands.

Interface Config Switch (Interface unit/slot/port)#

Manages the operation of an interface and provides access to the router interface configuration commands.Use this mode to set up a physical port for a specific logical connection operation.

Switch (Interface Loopback id)#

Switch (Interface Tunnel id)#

Switch (Interface unit/slot/port (startrange)-unit/slot/port (endrange)#

Use this mode to manage the operation of a range of interfaces. For example the prompt may display as follows:Switch (Interface 1/0/1-1/0/4) #

Switch (Interface lag lag-intf-num)#

Enters LAG Interface configuration mode for the specified LAG.

Switch (Interface vlan vlan-id)# Enters VLAN routing interface configuration mode for the specified VLAN ID.

NETGEAR Managed Switch Software Modules

17


Line Console Switch (config-line)# Contains commands to configure outbound telnet settings and console interface settings, as well as to configure console login/enable authentication.

Line SSH Switch (config-ssh)# Contains commands to configure SSH login/enable authentication.

Line Telnet Switch (config-telnet)# Contains commands to configure telnet login/enable authentication.

AAA IAS User Config

Switch (Config-IAS-User)# Allows password configuration for a user in the IAS database.

Mail Server Config Switch (Mail-Server)# Allows configuration of the email server.

Policy Map Config Switch (Config-policy-map)# Contains the QoS Policy-Map configuration commands.

Policy Class Config Switch(Config-policy-class-map)# Consists of class creation, deletion, and matching commands. The class match commands specify Layer 2, Layer 3, and general match criteria.

Class Map Config Switch (Config-class-map)# Contains the QoS class map configuration commands for IPv4.

Ipv6_Class-Map Config

Switch (Config-class-map)# Contains the QoS class map configuration commands for IPv6.

Router OSPF Config

Switch (Config-router)# Contains the OSPF configuration commands.

Router OSPFv3 Config

Switch (Config rtr)# Contains the OSPFv3 configuration commands.

Router RIP Config Switch (Config-router)# Contains the RIP configuration commands.

BGP Router Config Switch (Config-router)# Contains the BGP4 configuration commands.

Route Map Config Switch (config-route-map)# Contains the route map configuration commands.

IPv6 Address Family Config

Switch (Config-router-af)# Contains the IPv6 address family configuration commands.

Peer Template Config

(Config-rtr-tmplt)# Contains the BGP peer template configuration commands.

MAC Access-list Config

Switch (Config-mac-access-list)# Allows you to create a MAC Access-List and to enter the mode containing MAC Access-List configuration commands.

Table 5. CLI Command Modes (continued)



18


The following table explains how to enter or exit each mode.

TACACS Config Switch (Tacacs)# Contains commands to configure properties for the TACACS servers.

DHCP Pool Config

Switch (Config dhcp-pool)# Contains the DHCP server IP address pool configuration commands.

DHCPv6 Pool Config

Switch (Config dhcp6-pool)# Contains the DHCPv6 server IPv6 address pool configuration commands.

Chassis Global Config Mode

Switch (Config chassis)# Allows you to access the Chassis Global Config Mode.

ARP Access-List Config Mode

Switch (Config-arp-access-list)# Contains commands to add ARP ACL rules in an ARP Access List.

Support Mode Switch (Support)# Allows access to the support commands, which should only be used by the manufacturer's technical support personnel as improper use could cause unexpected system behavior and/or invalidate product warranty.

Table 6. CLI Mode Access and Exit

Command Mode Access Method Exit or Access Previous Mode

User EXEC This is the first level of access. To exit, enter logout.

Privileged EXEC From the User EXEC mode, enter enable.

To exit to the User EXEC mode, enter exit or press Ctrl-Z.

Global Config From the Privileged EXEC mode, enter configure.

To exit to the Privileged EXEC mode, enter exit, or press Ctrl-Z.

VLAN Config From the Privileged EXEC mode, enter vlan database.


Table 5. CLI Command Modes (continued)



19


Interface Config From the Global Config mode, enter:interface unit/slot/port

To exit to the Global Config mode, enter exit. To return to the Privileged EXEC mode, enter Ctrl-Z.

From the Global Config mode, enter:interface loopback id

From the Global Config mode, enter:interface tunnel id

From the Global Config mode, enter:interface unit/slot/port(startrange)- unit/slot/port(endrange)

From the Global Config mode, enter:interface lag lag-intf-num

From the Global Config mode, enter:interface vlan vlan-id

Line Console From the Global Config mode, enter line console.


Line SSH From the Global Config mode, enter line ssh.


Line Telnet From the Global Config mode, enter line telnet.


AAA IAS User Config

From the Global Config mode, enter aaa ias-user username name.


Mail Server Config From the Global Config mode, enter mail-server address.


Policy-Map Config

From the Global Config mode, enter policy-map.


Policy-Class-Map Config

From the Policy Map mode enter class. To exit to the Policy Map mode, enter exit. To return to the Privileged EXEC mode, enter Ctrl-Z.

Class-Map Config

From the Global Config mode, enter class-map, and specify the optional keyword ipv4 to specify the Layer 3 protocol for this class. See class-map on page 1005 for more information.


Table 6. CLI Mode Access and Exit (continued)



20


VPC From Global Config mode, enter vpc. To exit to the Global Config mode, enter exit. To return to the Privileged EXEC mode, enter Ctrl-Z.

Ipv6-Class-Map Config

From the Global Config mode, enter class-map and specify the optional keyword ipv6 to specify the Layer 3 protocol for this class. See class-map on page 1005 for more information.


Router OSPF Config

From the Global Config mode, enter router ospf.


Router OSPFv3 Config

From the Global Config mode, enter ipv6 router ospf.


Router RIP Config

From the Global Config mode, enter router rip.


BGP Router Config

From the Global Config mode, enter router bgp asnumber.


Route Map Config From the Global Config mode, enter route-map map-tag.


IPv6 Address Family Config

From the BGP Router Config mode, enter address-family ipv6.


Peer Template Config

From the BGP Router Config mode, enter template peer name to create a BGP peer template and enter Peer Template Configuration mode.

o exit to the Global Config mode, enter exit. To return to the Privileged EXEC mode, enter Ctrl-Z.

MAC Access-list Config

From the Global Config mode, enter mac access-list extended name.


TACACS Config From the Global Config mode, enter tacacs-server host ip-addr, where ip-addr is the IP address of the TACACS server on your network.


DHCP Pool Config

From the Global Config mode, enter ip dhcp pool pool-name.


DHCPv6 Pool Config

From the Global Config mode, enter ip dhcpv6 pool pool-name.





21


Command Completion and Abbreviation

Command completion finishes spelling the command when you type enough letters of a command to uniquely identify the command keyword. Once you have entered enough letters, press the SPACEBAR or TAB key to complete the word.

Command abbreviation allows you to execute a command when you have entered there are enough letters to uniquely identify the command. You must enter all of the required keywords and parameters before you enter the command.

CLI Error Messages

If you enter a command and the system is unable to execute it, an error message appears. The following table describes the most common CLI error messages.

Chassis Global Config Mode

From the Global Config mode, enter chassis.

To exit to the Global Config mode, enter the exit command. To return to the Privileged EXEC mode, enter Ctrl-Z.

ARP Access-List Config Mode

From the Global Config mode, enter arp access-list.

To exit to the Global Config mode, enter the exit command. To return to the Privileged EXEC mode, enter Ctrl-Z.

Support Mode From the Privileged EXEC mode, enter support.

Note: The support command is available only if the techsupport enable command has been issued.


Table 7. CLI Error Messages

Message Text Description

% Invalid input detected at '^' marker.

Indicates that you entered an incorrect or unavailable command. The carat (^) shows where the invalid text is detected. This message also appears if any of the parameters or values are not recognized.

Command not found / Incomplete command. Use ? to list commands.

Indicates that you did not enter the required keywords or values.

Ambiguous command Indicates that you did not enter enough letters to uniquely identify the command.




22


CLI Line-Editing Conventions

The following table describes the key combinations you can use to edit commands or increase the speed of command entry. You can access this list from the CLI by entering help from the User or Privileged EXEC modes.

Table 8. CLI Editing Conventions

Key Sequence Description

DEL or Backspace Delete previous character.

Ctrl-A Go to beginning of line.

Ctrl-E Go to end of line.

Ctrl-F Go forward one character.

Ctrl-B Go backward one character.

Ctrl-D Delete current character.

Ctrl-U, X Delete to beginning of line.

Ctrl-K Delete to end of line.

Ctrl-W Delete previous word.

Ctrl-T Transpose previous character.

Ctrl-P Go to previous line in history buffer.

Ctrl-R Rewrites or pastes the line.

Ctrl-N Go to next line in history buffer.

Ctrl-Y Prints last deleted character.

Ctrl-Q Enables serial flow.

Ctrl-S Disables serial flow.

Ctrl-Z Return to root command prompt.

Tab, Command-line completion.

Exit Go to next lower command prompt.

? List available commands, keywords, or parameters.


23


Using CLI HelpEnter a question mark (?) at the command prompt to display the commands available in the current mode.

(NETGEAR Switch) >?

enable Enter into user privilege mode.help Display help for various special keys.logout Exit this session. Any unsaved changes are lost.password Change an existing users password.ping Send ICMP echo packets to a specified IP address.quit Exit this session. Any unsaved changes are lost.show Display Switch Options and Settings.telnet Telnet to a remote host.

Enter a question mark (?) after each word you enter to display available command keywords or parameters.

(NETGEAR Switch) #network ?

ipv6 Configure IPv6 parameters for system network.javamode Enable/Disable.mac-address Configure MAC Address.mac-type Select the locally administered or burnedin MAC address.mgmt_vlan Configure the Management VLAN ID of the switch.parms Configure Network Parameters of the device.protocol Select DHCP, BootP, or None as the network config protocol.

If the help output shows a parameter in angle brackets, you must replace the parameter with a value.

(NETGEAR Switch) #network parms ?

Enter the IP Address.none Reset IP address and gateway on management interface

If there are no additional command keywords or parameters, or if additional parameters are optional, the following message appears in the output:

Press Enter to execute the command

You can also enter a question mark (?) after typing one or more characters of a word to list the available command or parameters that begin with the letters, as shown in the following example:

(NETGEAR Switch) #show m?

mac mac-addr-table mac-address-tablemail-server mbuf monitor


24


Accessing the CLI

You can access the CLI by using a direct console connection or by using a telnet or SSH connection from a remote management host.

For the initial connection, you must use a direct connection to the console port. You cannot access the system remotely until the system has an IP address, subnet mask, and default gateway. You can set the network configuration information manually, or you can configure the system to accept these settings from a BootP or DHCP server on your network. For more information, see Network Interface Commands on page 47.


25

4

4. Chassis Commands

This chapter describes the chassis commands available in the NETGEAR Managed Switch CLI.

The Chassis Commands chapter includes the following sections:

General Chassis Commands Backplane Port Commands Chassis Firmware Synchronization Commands Nonstop Forwarding Commands

The commands in this chapter are in one of two functional groups:

Show commands. Display switch settings, statistics, and other information. Configuration commands. Configure features and options of the switch. For every

configuration command, there is a show command that displays the configuration setting.

26


General Chassis Commands

This section describes the commands you use to configure the chassis.

chassisThis command sets the mode to Chassis Global Config.

chassis-status sample-modeThis command set the global status management mode.

memberThis command configures a blade. The unit is the identifier of the blade that you want to add or remove from the chassis. The switchindex is the index into the database of the supported blade types, indicating the type of the blade that is being preconfigured. The blade index is a 32-bit integer. You execute this command on the management blade.

Note: You can obtain the switch index by executing the show supported switchtype command in user EXEC mode.

Format chassis

Mode Chassis Global Config

Format chassis-status sample-mode [cumulative | history [max-samples ]]



cumulative Tracks the sum of received time stamp offsets cumulatively.

history Tracks the history of received timestamps.

max-samples As an option for the history parameter, the maximum number of samples to keep. The valid range is from 100 to 500.

Format member unit switchindex


Chassis Commands

27


no member

This command removes a blade from the chassis. The unit is the identifier of the blade to be removed from the chassis. You execute this command on the primary management blade.

movemanagementThis command moves the management functionality from one blade to the other. The fromunit is the identifier of the current management blade. The tounit is the identifier of the new management blade. Upon execution, the entire chassis (including all interfaces in the chassis) is unconfigured and reconfigured with the configuration on the new management blade. After the reload is complete, you must perform all chassis management capabilities on the new management blade. To preserve the current configuration across a management blade move, execute the copy system:running-config nvram:startup-config privileged EXEC command or save privileged EXEC command before you perform the management blade move. A management blade move causes all routes and layer 2 addresses to be lost. You execute this command is executed on the management blade. The system prompts you to confirm the management blade move.

Note: You can only configure the blade in slot 1 or slot 2 as a management blade.

slotThis command configures a slot in the system. The unit/slot is the slot identifier of the slot. The cardindex is the index into the database of the supported card types, indicating the type of the card being preconfigured in the specified slot. The card index is a 32-bit integer. If a card is currently present in the slot that is unconfigured, the configured information will be deleted and the slot will be reconfigured with default information for the card.

Note: Card index can be obtained by executing show supported cardtype command in User EXEC mode.

Format no member unit


Format movemanagement fromunit tounit


Format slot unit/slot cardindex

Mode Global Config

Chassis Commands

28


no slot

This command removes configured information from an existing slot in the system.

Note: Card index can be obtained by executing show supported cardtype command in User EXEC mode.

set slot disableThis command configures the administrative mode of the slot(s). If you specify all, the command is applied to all slots, otherwise the command is applied to the slot identified by unit/slot.

If a card or other module is present in the slot, this administrative mode will effectively be applied to the contents of the slot. If the slot is empty, this administrative mode will be applied to any module that is inserted into the slot. If a card is disabled, all the ports on the device are operationally disabled and shown as unplugged on management screens.

no set slot disable

This command unconfigures the administrative mode of the slot or slots. If you specify all, the command removes the configuration from all slots, otherwise the configuration is removed from the slot identified by unit/slot.

If a card or other module is present in the slot, this administrative mode removes the configuration from the contents of the slot. If the slot is empty, this administrative mode removes the configuration from any module inserted into the slot. If a card is disabled, all the ports on the device are operationally disabled and shown as unplugged on management screens.

set slot powerThis command configures the power mode of the slot(s) and allows power to be supplied to a card located in the slot. If you specify all, the command is applied to all slots, otherwise the command is applied to the slot identified by unit/slot.

Format no slot unit/slot cardindex

Mode Global Config

Format set slot disable [unit/slot] | all]

Mode Global Config

Format no set slot disable [unit/slot] | all]

Mode Global Config

Chassis Commands

29


Use this command when installing or removing cards. If a card or other module is present in this slot, the power mode is applied to the contents of the slot. If the slot is empty, the power mode is applied to any card inserted into the slot.

no set slot power

This command unconfigures the power mode of the slot or slots and prohibits power from being supplied to a card located in the slot. If you specify all, the command prohibits power to all slots, otherwise the command prohibits power to the slot identified by unit/slot.

Use this command when installing or removing cards. If a card or other module is present in this slot, power is prohibited to the contents of the slot. If the slot is empty, power is prohibited to any card inserted into the slot.

reload (Chassis)This command resets the entire chassis or the identified blade. The blade is the blade identifier. The system prompts you to confirm that you want to reset the chassis or blade.

show supported cardtypeThis commands displays information about all card types or specific card types supported in the system.

If you do not supply a value for cardindex, the following output appears:

Format set slot power [unit/slot] | all]

Mode Global Config

Format no set slot power [unit/slot] | all]

Mode Global Config

Format reload [blade]

Mode Global Config

Format show supported cardtype [cardindex]

Mode User EXEC

Term Definition

Card Index (CID) The index into the database of the supported card types. This index is used when preconfiguring a slot.

Card Model Identifier

The model identifier for the supported card type.

Chassis Commands

30


If you supply a value for cardindex, the following output appears:

show chassisThis command displays chassis status information about all blades in the chassis or, if you specify the unit value, about a single blade. For blades that would normally be allowed to join the chassis but do not have a matching chassis template ID, the blade status is shown as STM Mismatch.

If you do not specify a value for unit, the following information displays:

Term Definition

Card Type The 32-bit numeric card type for the supported card.

Model Identifier The model identifier for the supported card type.

Card Description The description for the supported card type.

Format show chassis [unit]

Mode Privileged EXEC

Term Definition

Unit The unit identifier assigned to the blade.

Term Definition

Management Role Indicates whether the blade is the supervisor blade, a member blade, or an operational backup blade, or whether the status is unassigned.

Preconfigured Model Identifier

The model identifier of a preconfigured blade that is ready to join the chassis. The Model Identifier is a 32-character field that is assigned by the device manufacturer to identify the device.

Plugged-In Model ID

The model identifier of the blade in the chassis. The Model Identifier is a 32-character field that is assigned by the device manufacturer to identify the device.

Switch Status The chassis status. Possible values for this state are: OK, Unsupported, Code Mismatch, SDM Mismatch, Config Mismatch, or Not Present. A mismatch indicates that a blade is running a different software version, has a different SDM template, or has a different configuration from the management blade. The SDM Mismatch status indicates that the blade joined the chassis, but has a different SDM template than the management blade. This status is temporary; the blade automatically reloads using the template of the chassis manager.If a chassis firmware synchronization operation is in progress, the status is shown as Updating Code.

Code Version The detected version of code on this blade.

Chassis Commands

31


Command example: (NETGEAR Switch) #show chassis

Management Plugged-in Serial Switch Version Admin PoEUnit Role Model ID Number Status Code State Card------ ---------- ------------ ------------- ------------- ----------- ------- --------1 Primary XCM8944-PoE+ 33J1245WF0021 OK 5.26.23.31 Enable XCM89P2 Oper Standby XCM8948-uPoE 33J1245WF0022 CodeMismatch 5.26.23.31 Enable XCM89UP

3 Chassis Mbr XCM8924X 33J1245WF0023 NoPwr 5.26.23.31 Enable N/A

If you specify a value for unit, the following information displays.

Term Definition

Unit The unit number of the blade.

Management Status

Indicates whether the blade is the supervisor blade, the backup blade, a member blade, or unassigned.

Hardware Management Preference

The hardware management preference of the blade. The hardware management preference can be disabled or unassigned.

Admin Management Preference

The administrative management preference value that is assigned to the blade. This preference value indicates how likely the blade is to be selected as the primary management blade.

Admin State Administrative state of the blade.

Power State Power state of the blade.

Switch Type The 32-bit numeric blade type.

Plugged-in Model Identifier

The model identifier of the blade in the chassis. The Model Identifier is a 32-character field that is assigned by the device manufacturer to identify the device.

Switch Status The blade status. Possible values are OK, Unsupported, Code Mismatch, Config Mismatch, SDM Mismatch, or Not Present.A mismatch indicates that the blade is running a different version of the code, SDM template, or configuration than the management blade. The SDM Mismatch status indicates that the blade is part of the chassis, but is running a different SDM template than the management blade. A mismatch status is temporary; the blade automatically reloads using the template that is running on the management blade. If a chassis firmware synchronization operation is in progress, the status is shown as Updating Code.

Switch Description The blade description.

Detected Code in Flash

The version of code that is currently stored in FLASH memory on the blade. This code executes after the blade is reset. If the blade is not present and the data is from preconfiguration, then the code version is None.

POE D-Card description

The description of the PoE daughter card that is plugged into the blade.

POE D-Card PoE firmware version

The firmware version that is running on the PoE controller of the daughter card that is plugged into the blade.

Chassis Commands

32


Command example: (NETGEAR Switch) #show chassis 1

Switch............................ 1Management Status................. Management SwitchHardware Management Preference.... UnassignedAdmin Management Preference....... 15Admin State....................... EnablePower State....................... EnableSwitch Type....................... 0x4320004Preconfigured Model Identifier.... XCM8948Plugged-in Model Identifier....... XCM8948Switch Status..................... OKSwitch Description................ XCM8948 ProSafe 48-port Gigabit bladeDetected Code in Flash............ 5.26.23.31CPLD version ............ ........ 0x01POE D-card Description............ XCM89UP ProSafe UPoE daughter cardPOE D-card PoE FW version....... 1.0SFS Last Attempt Status........... NoneSerial Number..................... 33J1245WF0021Up Time........................... 4 days 21 hrs 52 mins 51 secs


Switch............................ 2Management Status................. Standby Management unitHardware Management Preference.... UnassignedAdmin Management Preference....... 14Admin State....................... EnablePower State....................... EnableSwitch Type....................... 0x5320005Preconfigured Model Identifier.... XCM8948Plugged-in Model Identifier....... XCM8948Switch Status..................... OKSwitch Description................ XCM8948 ProSafe 48-port Gigabit bladeDetected Code in Flash............ 5.26.23.31

CPLD Version The version of CPLD firmware that is running on the blade.

SFS Last Attempt Status

The chassis firmware synchronization status in the last attempt for the blade.

Serial Number The serial number for the blade.

Up Time The system up time.

Term Definition

Chassis Commands

33


CPLD version ............ ........ 0x01POE D-card Description............ XCM89P ProSafe PoE+ daughter cardPOE D-card PoE FW version....... 1.0SFS Last Attempt Status........... NoneSerial Number..................... 33J1245WF0022Up Time........................... 4 days 21 hrs 52 mins 41 secs


Switch............................ 3Management Status................. Chassis MemberHardware Management Preference.... UnassignedAdmin Management Preference....... DisabledAdmin State....................... EnablePower State....................... EnableSwitch Type....................... 0x4320004Preconfigured Model Identifier.... XCM8948Plugged-in Model Identifier....... XCM8948Switch Status..................... OKSwitch Description................ XCM8948 ProSafe 48-port Gigabit bladeDetected Code in Flash............ 5.26.23.31CPLD version ............ ........ 0x01POE D-card Description............ Not InstalledPOE D-card PoE FW version....... NASFS Last Attempt Status........... NoneSerial Number..................... 2X61295V00008Up Time........................... 4 days 21 hrs 56 mins 25 secs

show chassis watchdogThis command shows the internal watchdog timer on the switch, which reboots the switch if the CPU becomes stuck or does not respond.

Command example: (NETGEAR Switch)# show chassis watchdog Slot Watchdog counter 1 0 2 1 3 0

Format show chassis watchdog


Chassis Commands

34


show chassis-statusEvery two seconds, a blade broadcasts heartbeat messages. A state table on the supervisor and each blade tracks every unit in the chassis. The table maintains a running history of the heartbeat messages, current observed interval, and the minimum, maximum, and average observed times between heartbeat messages. Sequence numbers in the discovery messaged determine loss.

Command example: (NETGEAR Switch) #show chassis-status 1

Chassis Unit 1 StatusUnit Current Average Min Max Dropped 1 2000 2000 2000 2000 0 2 2000 2100 2000 2500 0 3 2000 2100 2000 2200 0

show supported switchtypeThis commands displays information about all supported switch types or a specific switch type.

If you do not supply a value for switchindex, the following output appears:

Format chassis-status unit [unit | all] [clear]

Mode User EXEC

Format show supported switchtype [switchindex]

Mode User EXECPrivileged EXEC

Term Definition

Switch Index (SID) The index into the database of supported blade types. This index is used when you preconfigure a member to be added to the chassis.

Model Identifier The model identifier for the supported blade type.

Management Preference

The management preference value of the blade type.

Code Version The code load target identifier of the blade type.

Chassis Commands

35


If you supply a value for switchindex, the following output appears:

Backplane Port Commands

This section describes the commands you use to view and configure backplane port information.

show backplane-portThis command displays summary backplane-port information for all interfaces.

For each Interface:

show backplane-port countersThis command displays summary data counter information for all interfaces.

Term Definition

Switch Type The 32-bit numeric switch type for the supported blade.

Model Identifier The model identifier for the supported blade type.

Switch Description The description for the supported blade type.

Format show backplane-port


Term Definition

Unit The blade number.

Interface The blade and port numbers.

Link Status Status of the link.

Link Speed Speed (Gbps) of the blade port link.

Format show backplane-port counters


Term Definition

Unit The slot number.

Interface The slot and port numbers.

Tx Data Rate Trashing data rate in megabits per second on the backplane port.

Tx Error Rate Platform-specific number of transmit errors per second.

Chassis Commands

36


show backplane-port diagThis command shows backplane port diagnostics for each port and is only intended for Field Application Engineers (FAEs) and developers. An FAE will advise on the necessity to run this command and capture this information.

show backplane-port packet-pathThis command displays the route a packet will take to reach the destination.

show backplane This command displays the backplane model ID, FAPGA version, and serial number.

Chassis Firmware Synchronization Commands

Chassis Firmware Synchronization (CFS) provides the ability to automatically synchronize firmware for all chassis members. If a blade joins the chassis and its firmware version is different from the version running on the chassis manager, the CFS feature can either upgrade or downgrade the firmware on the mismatched chassis member. There is no attempt to synchronize the blade to the latest firmware in the chassis.

Tx Total Errors Platform-specific number of total transmit errors since power-up.

Rx Data Rate Receive data rate in megabits per second on the backplane port.

Rx Error Rate Platform-specific number of receive errors per second.

Rx Total Errors Platform-specific number of total receive errors since power-up.

Link Flaps The number of times this backplane port transitioned to the down state.

Format show backplane-port diag [ | all] [verbose]


Format show backplane-port packet-path {1-3 | all}


Format show backplane


Term Definition

Chassis Commands

37


boot auto-copy-swUse this command to enable the Chassis Firmware Synchronization feature on the chassis.

no boot auto-copy-sw

Use this command to disable the Chassis Firmware Synchronization feature on the chassis.

boot auto-copy-sw trapUse this command to enable the sending of SNMP traps that are related to the Chassis Firmware Synchronization feature.

no boot auto-copy-sw trap

Use this command to disable the sending of traps that are related to the Chassis Firmware Synchronization feature.

boot auto-copy-sw allow-downgradeUse this command to allow the chassis manager to downgrade the firmware version on the chassis member if the firmware version on the manager is older than the firmware version on the chassis member.

Default Disabled

Format boot auto-copy-sw

Mode Privileged Exec

Format no boot auto-copy-sw


Default Enabled

Format boot auto-copy-sw trap


Format no boot auto-copy-sw trap


Default Enabled

Format boot auto-copy-sw allow-downgrade


Chassis Commands

38


no boot auto-copy-sw allow-downgrade

Use this command to prevent the chassis manager from downgrading the firmware version of a chassis member.

show auto-copy-swUse this command to display chassis firmware synchronization configuration status information.

Nonstop Forwarding Commands

Note: Nonstop forwarding (NSF) is enabled by default. You cannot disable NSF.

A switch can be described in terms of three semi-independent functions called the forwarding plane, the control plane, and the management plane. The forwarding plane forwards data packets. The forwarding plane is implemented in hardware. The control plane is the set of protocols that determine how the forwarding plane should forward packets, deciding which data packets are allowed to be forwarded and where they should go. Application software on the management blade acts as the control plane. The management plane is application software running on the management blade that provides interfaces allowing a network administrator to configure and monitor the device.

NSF allows the forwarding plane of chassis blades to continue to forward packets while the control and management planes restart as a result of a power failure, hardware failure, or software fault on the management blade. A nonstop forwarding failover can also be manually initiated using the initiate failover command. Traffic flows that enter and exit the chassis through physical ports on a blade other than the management blade continue with at most subsecond interruption when the management blade fails.

Format no boot auto-copy-sw allow-downgrade


Format show auto-copy-sw


Term Definition

Synchronization Shows whether the CFS feature is enabled.

SNMP Trap Status Shows whether the chassis will send traps for CFS events.

Allow Downgrade Shows wether the manager is permitted to downgrade the firmware version of a chassis member.

Chassis Commands

39


To prepare the backup management blade in case of a failover, applications on the management blade continuously checkpoint some state information to the backup blade. Changes to the running configuration are automatically copied to the backup blade. MAC addresses stay the same across a nonstop forwarding failover so that neighbors do not have to relearn them.

When a nonstop forwarding failover occurs, the control plane on the backup blade starts from a partially-initialized state and applies the checkpointed state information. While the control plane is initializing, the chassis cannot react to external changes, such as network topology changes. Once the control plane is fully operational on the new management blade, the control plane ensures that the hardware state is updated as necessary. Control plane failover time depends on the size of the chassis, the complexity of the configuration, and the speed of the CPU.

The management plane restarts when a failover occurs. Management connections must be reestablished.

For NSF to be effective, adjacent networking devices must not reroute traffic around the restarting device. NETGEAR Managed Switch software uses three techniques to prevent traffic from being rerouted:

A protocol may distribute a part of its control plane to chassis blades so that the protocol can give the appearance that it is still functional during the restart. Spanning tree and port channels use this technique.

A protocol may enlist the cooperation of its neighbors through a technique known as graceful restart. OSPF uses graceful restart if it is enabled (see IP Event Dampening Commands on page 729).

A protocol may simply restart after the failover if neighbors react slowly enough that they will not normally detect the outage. The IP multicast routing protocols are a good example of this behavior.

To take full advantage of nonstop forwarding, layer 2 connections to neighbors should be via port channels that span two or more chassis slots, and layer 3 routes should be ECMP routes with next hops via physical ports on two or more slots. The hardware can quickly move traffic flows from port channel members or ECMP paths on a failed blade to a surviving blade.

show nsfThis command displays global and per-blade information on NSF configuration on the chassis.

Format show nsf


Chassis Commands

40


initiate failoverThis command forces the backup blade to take over as the management blade and perform a warm restart of the chassis. On a warm restart, the backup blade becomes the management blade without clearing its hardware tables. (On a cold restart, hardware tables are cleared.) Applications apply checkpointed data from the former management blade. The original management blade reboots.

If the system is not ready for a warm restart, for example, because no backup blade was elected or one or more members of the chassis do not support nonstop forwarding, the command fails with a warning message.


NSF Administrative Status

Whether nonstop forwarding is administratively enabled or disabled. Default: Enabled

NSF Operational Status Indicates whether NSF is enabled on the chassis.

Last Startup Reason The type of activation that caused the software to start the last time:Power-On means that the blade rebooted. This could have been caused by a power cycle or an administrative Reload command. Administrative Move means that the administrator issued the movemanagement command for the stand-by manager to take over. Warm-Auto-Restart means that the primary management blade restarted due to a failure, and the system executed a nonstop forwarding failover. Cold-Auto-Restart means that the system switched from the active manager to the backup manager and was unable to maintain user data traffic. This is usually caused by multiple failures occurring close together.

Time Since Last Restart Time since the current management blade became the active management blade.

Restart in progress Whether a restart is in progress.

Warm Restart Ready Whether the system is ready to perform a nonstop forwarding failover from the management blade to the backup blade.

Copy of Running Configuration to Backup Unit: Status

Whether the running configuration on the backup blade includes all changes made on the management blade.

Time Since Last Copy When the running configuration was last copied from the management blade to the backup blade.

Time Until Next Copy The number of seconds until the running configuration will be copied to the backup blade. This line only appears when the running configuration on the backup blade is Stale.

Per Unit Status Parameters

NSF Support Whether a blade supports NSF.

Chassis Commands

41


The movemanagement command (see movemanagement on page 28) also transfers control from the current management blade; however, the hardware is cleared and all blades reinitialize.

show checkpoint statisticsThis command displays general information about the checkpoint service operation.

clear checkpoint statisticsThis command clears all checkpoint statistics to their initial values.

Format initiate failover

Mode Chassis Global Config Mode

Format show checkpoint statistics



Messages Checkpointed Number of checkpoint messages transmitted to the backup blade. Range: Integer. Default: 0

Bytes Checkpointed Number of bytes transmitted to the backup blade. Range: Integer. Default: 0

Time Since Counters Cleared Number of days, hours, minutes and seconds since the counters were reset to zero. The counters are cleared when a blade becomes manager and with a support command. Range: Time Stamp. Default: 0d00:00:00

Checkpoint Message Rate Average number of checkpoint messages per second. The average is computed over the time period since the counters were cleared. Range: Integer. Default: 0

Last 10-second Message Rate Average number of checkpoint messages per second in the last 10-second interval. This average is updated once every 10 seconds. Range: Integer. Default: 0

Highest 10-second Message Rate

The highest rate recorded over a 10-second interval since the counters were cleared. Range: Integer. Default: 0

Format clear checkpoint statistics


Chassis Commands

42

5

5. Management Commands

This chapter describes the management commands available in the NETGEAR Managed Switch CLI.

The Management Commands chapter contains the following sections:

Configure the Switch Management CPU CPU Queue Commands Network Interface Commands Console Port Access Commands Telnet Commands Secure Shell Commands Management Security Commands Management Access Control List Commands Hypertext Transfer Protocol Commands Access Commands User Account Commands SNMP Commands RADIUS Commands TACACS+ Commands Configuration Scripting Commands

The commands in this chapter are in one of three functional groups:

Show commands. Display switch settings, statistics, and other information. Configuration commands. Configure features and options of the switch. For every

configuration command, there is a show command that displays the configuration setting. Clear commands. Clear some or all of the settings to factory defaults.

43


Configure the Switch Management CPU

To manage the switch over the web management interface or Telnet, you must assign an IP address to the switch management CPU. You can accomplish this task through CLI commands or you can use the ezconfig tool, which simplifies the task. The tool is applicable to all NETGEAR M6100 series managed switches and lets you configure the following settings:

The administrator user password and administrator-enable password The management CPU IP address and network mask The system name and location information

The tool is interactive and uses questions to guide you through the configuration steps. At the end of the configuration session, the tool lets you save the information. To see which information was changed by the ezconfig tool after a configuration session, issue the show running-config command.

ezconfigThis command sets the IP address, subnet mask, and gateway of the switch. The IP address and the gateway must be on the same subnet.

(NETGEAR Switch) #ezconfig

EZ Configuration Utility--------------------------------Hello and Welcome!This utility will walk you thru assigning the IP address for the switchmanagement CPU. It will allow you to save the changes at the end. Afterthe session, simply use the newly assigned IP address to access the WebGUI using any public domain Web browser.

Admin password is not defined.Do you want to assign the admin password (password length should vary in a range of 8 - 64 characters)? (Y/N/Q) y

Enter new password:********Confirm new password:********

The 'enable' password required for switch configuration via the commandline interface is currently not configured.Do you want to assign it (password length should vary in a range of 8 - 64 characters) (Y/N/Q)? y

Format ezconfig


Management Commands

44


Enter new password:********Confirm new password:********Assigning an IP address to your switch management

Current IP Address Configuration--------------------------------

Management VLAN ID: 1IP Address Assignment Mode: NoneIP Address: 0.0.0.0Subnet mask: 0.0.0.0Default Router IP: 0.0.0.0Routing Mode: Disable

IP address is not assigned. What do you want to do?C - Configure IP address manually.D - Assign IP address for the switch using DHCP mode(current IP address will belost).N - Do nothing and go to the next question.Q - Quit.? - Help.(C/D/N/Q/?)? c

IP Address: 10.10.10.1Network mask: 255.255.255.0Gateway: 10.10.10.10Do you want routing to be enabled (Y/N)?y

Assigning System Name, System Location and System Contact to your switch management

Current Configuration--------------------------------System Name:

System Location:

System Contact:

Do you want to assign switch name and location information? (Y/N/Q)y

the System Name:testchassisthe System Location:testlabthe System Contact:Bud LightyearDo you want to apply and save the changes (Y/N)? y

Could not set the Default Router IP address!

Management Commands

45


Config file 'startup-config' created successfully .

The confi

Documents

M6100 Series Switches - ネットギア【NETGEAR】 while performance and feature sets continue to improve. Devices that are capable of switching Layers 2, 3, and 4 are increasingly