Alcatel-Lucent OmniSwitch 6250 Management Manual
  1. Manuals
  2. Brands
  3. Alcatel-Lucent Manuals
  4. Switch
  5. OmniSwitch 6250
  6. Management manual

Alcatel-Lucent OmniSwitch 6250 Management Manual

Hide thumbs Also See for OmniSwitch 6250:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Owner's Manual, User Manual
Part No. 060306-10, Rev. C
May 2012
OmniSwitch 6250/6450
Switch Management Guide
www.alcatel-lucent.com

Advertisement

Table of Contents
loading

Related Manuals for Alcatel-Lucent OmniSwitch 6250

Summary of Contents for Alcatel-Lucent OmniSwitch 6250

  • Page 1 Part No. 060306-10, Rev. C May 2012 OmniSwitch 6250/6450 Switch Management Guide www.alcatel-lucent.com...
  • Page 2 This user guide documents release 6.6.3 of the OmniSwitch 6250, 6450. The functionality described in this guide is subject to change without notice. Copyright © 2012 by Alcatel-Lucent. All rights reserved. This document may not be reproduced in whole or in part without the express written permission of Alcatel-Lucent.

  • Page 3: Table Of Contents

    Copy an Existing File ..................1-14 Secure Copy an Existing File .................1-15 Move an Existing File or Directory ..............1-15 Change File Attribute and Permissions ............1-16 Delete an Existing File ..................1-16 Managing Files on Switches ................1-17 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 4 Using the WebView Management Tool ............2-7 Using SNMP to Manage the Switch ..............2-7 User Accounts ......................2-7 Using Telnet ........................2-8 Logging Into the Switch Through Telnet ..............2-8 Starting a Telnet Session from the Switch ...............2-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 5 SNMP Versions ......................3-8 SNMPv1 ......................3-8 SNMPv2 ......................3-9 SNMPv3 ......................3-9 Using SNMP For Switch Security ................3-10 Community Strings (SNMPv1 and SNMPv2) ............3-10 Configuring Community Strings ..............3-10 Encryption and Authentication (SNMPv3) ............3-11 Configuring Encryption and Authentication ...........3-11 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 6 CMM Files ........................5-3 CMM Software Directory Structure .................5-3 Where is the Switch Running From? ..............5-4 Software Rollback Feature ..................5-4 Software Rollback Configuration Scenarios for a Single Switch .....5-5 Redundancy ......................5-9 Redundancy Scenarios ..................5-9 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 7 Recalling the Previous Command Line ............6-12 Inserting Characters ..................6-12 Syntax Checking ....................6-13 Prefix Recognition ....................6-13 Example for Using Prefix Recognition ............6-14 Prefix Prompt ....................6-15 Command History ....................6-15 Logging CLI Commands and Entry Results ..............6-17 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 8 Snapshot Feature List .....................7-10 User-Defined Naming Options ................7-11 Editing Snapshot Files ..................7-11 Verifying File Configuration ..................7-14 Chapter 8 Managing Automatic Remote Configuration Download ......... 8-1 In This Chapter ........................8-1 Automatic Remote Configuration Specifications ............8-2 viii OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 9 Managing Switch User Accounts ................9-1 In This Chapter ........................9-1 User Database Specifications ..................9-2 User Account Defaults ....................9-2 Overview of User Accounts ....................9-4 Startup Defaults ......................9-6 Quick Steps for Network Administrator User Accounts ..........9-7 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 10 Switch Security Defaults ....................10-2 Switch Security Overview .....................10-3 Authenticated Switch Access ..................10-4 AAA Servers—RADIUS or LDAP ................10-4 Authentication-only—ACE/Server ................10-4 Interaction With the User Database ...............10-5 ASA and Authenticated VLANs ................10-5 Configuring Authenticated Switch Access ..............10-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 11 Software License and Copyright Statements ............. A-1 Alcatel-Lucent License Agreement ................A-1 ALCATEL-LUCENT SOFTWARE LICENSE AGREEMENT ......A-1 Third Party Licenses and Notices .................. A-4 A. Booting and Debugging Non-Proprietary Software .......... A-4 B. The OpenLDAP Public License: Version 2.8, 17 August 2003 ......A-4 C.
  • Page 12 W. Boost Software License ................... A-15 X. OpenLDAP ...................... A-15 Y. BITMAP.C ....................... A-16 Z. University of Toronto ..................A-16 AA.Free/OpenBSD ....................A-16 Appendix B SNMP Trap Information ..................B-1 SNMP Traps Table ......................B-2 Index ........................Index-1 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 13: About This Guide

    This OmniSwitch 6250/6450 Switch Management Guide describes basic attributes of your switch and basic switch administration tasks. The software features described in this manual are shipped standard with your OmniSwitch 6250, 6450 switches. These features are used when readying a switch for integration into a live network environment.

  • Page 14: Who Should Read This Manual

    The audience for this user guide are network administrators and IT support personnel who need to config- ure, maintain, and monitor switches and routers in a live network. However, anyone wishing to gain knowledge on how fundamental software features are implemented in the OmniSwitch 6250, 6450 switches benefits from the material in this configuration guide.

  • Page 15: What Is Not In This Manual

    OmniSwitch. However, it is not intended as a comprehensive refer- ence to all CLI commands available in the OmniSwitch. For such a reference to all CLI commands, consult the OmniSwitch 6250/6450 CLI Reference Guide. How is the Information Organized? Each chapter in this guide includes sections that will satisfy the information requirements of casual read- ers, rushed readers, serious detail-oriented readers, advanced users, and beginning users.

  • Page 16: Documentation Roadmap

    802.1Q, VLANs, Spanning Tree, and network routing proto- cols. The Network Configuration Guide contains overview information, procedures, and examples on how standard networking technologies are configured in the OmniSwitch. page xiv OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 17 CLI commands supported by the switch. This guide can be consulted anytime during the configuration process to find detailed and specific information on each CLI command. OmniSwitch 6250/6450 Switch Management Guide May 2012 page xv...

  • Page 18: Related Documentation

    Related Documentation User manuals can be downloaded at: http://enterprise.alcatel-lucent.com/?dept=UserGuides&page=Portal The following are the titles and descriptions of all the related OmniSwitch 6250, 6450 user manuals: • OmniSwitch 6250 Getting Started Guide Describes the hardware and software procedures for getting an OmniSwitch 6250 switch up and running.
  • Page 19 • AOS Release 6.6.3 Release Notes Includes critical Open Problem Reports, feature exceptions, and other important information on the features supported in the current release and any limitations to their support. OmniSwitch 6250/6450 Switch Management Guide May 2012 page xvii...

  • Page 20: User Manual Cd

    Service and Support web page, you’ll be able to view and update any case (open or closed) that you have reported to Alcatel-Lucent’s technical support, open a new case or access helpful release notes, technical bulletins, and manuals. For more information on Alcatel-Lucent’s Service Programs, see our web page at service.esd.alcatel-lucent.com, call us at 1-800-995-2696, or email us at esd.support@alcatel-lucent.com.

  • Page 21: Chapter 1 Managing System Files

    System Date and Time (set system clock) CLI commands are used in the configuration examples; for more details about the syntax of commands, see the OmniSwitch 6250/6450 CLI Reference Guide. In This Chapter Configuration procedures described in this chapter include: •...

  • Page 22: File Management Specifications

    System Clock Set local date, time and time zone, Universal Time Coordinate (UTC), Daylight Savings (DST or summertime). System Date Default Value THU JAN 01 1970 (Thursday, January 1, 1970) page 1-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 23: Switch Administration Overview

    Over the life of the switch, it is very likely that your configuration and feature set will change because the needs of your network are likely to expand. Also, software updates become available from Alcatel-Lucent. If you change your configuration to upgrade your network, you must understand how to install switch files and to manage switch directories.

  • Page 24: Switch Directories

    Listing Directory: /flash Directory: /flash/certified Directory: /flash/network (Files) boot.params (Files) (Files) cs_system.pmd Directory: /flash/working boot.slot.cfg boot.cfg.1.err swlog1.log (Files) swlog2.log Switch Flash Directory page 1-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 25: File And Directory Management

    Sample Flash Directory boot.params cs_system.pmd Network Directory Flash Files boot.slot.cfg policy.cfg boot.cfg.1.err swlog1.log swlog2.log Working Directory Certified Directory Kadvrout.img Ksecu.img Krelease.img Ksecu.img Kos.img Kbase.img Kbase.img Kos.img boot.cfg boot.cfg boot.params boot.params OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-5...
  • Page 26 Here, the first entry shows a directory named WORKING, the second entry shows a file named boot.params. • The value shown at the bottom of the display indicates the amount of flash memory remaining for use in this directory (9.47 megabytes in the above example). page 1-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 27: Using Wildcards

    The single and multiple character wildcards can be used in combination. The following command lists all entries containing the letter i followed by any two single characters. -> ls *i?? Listing Directory /flash: 2048 Aug 12 18:51 working/ OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-7...

  • Page 28: Directory Commands

    The display shows the name of the current directory and its path. If your current directory is the certified directory and you enter the command, the following will be displayed: -> pwd /flash/certified -> The display shows the path to your current directory. page 1-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 29: Changing Directories

    In other words, if you use while your current directory is /flash, your current directory will remain /flash after you execute the command. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-9...

  • Page 30: Displaying Directory Contents

    8 09:59 boot.cfg.1.err 524288 Oct 31 10:51 u-boot.bin 834497 Oct 31 10:50 miniboot.uboot 64000 Nov 8 10:56 swlog2.log 719 Nov 6 12:07 test020 199567 Nov 5 11:16 rule930.txt 63308800 bytes free page 1-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 31: Making A New Directory

    The following command makes a new directory in the working directory on an OmniSwitch: -> mkdir /flash/working/newdir1 Flash Directory Working Directory (Files) newdir1 Directory Ksecu.img Kbase.img boot.cfg This drawing represents the content of the /flash/working directory after the new directory is added. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-11...

  • Page 32: Displaying Directory Contents Including Subdirectories

    -r command will work. ->cp -r /flash/working flash/certified/working Flash Directory Certified Directory Working Directory (Files) (Files) Working Directory newdir1 Directory boot.cfg boot.cfg Kos.img Kbase.img Krelease.img Ksecu.img Ksecu.img (Files) newdir1 Directory boot.cfg Kbase.img Ksecu.img page 1-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 33: Removing A Directory And Its Contents

    1-8, the working directory would be removed from the certified directory. ->rm -r /flash/certified/working Note. Your login account must have write privileges to execute the rmdir command. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-13...

  • Page 34: File Commands

    In each case, the file being copied will remain in its original location. Note. You must have write privileges in order to execute the command. page 1-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 35: Secure Copy An Existing File

    Note. Your login account must have write privileges to use the move command. Flash Directory Certified Directory Testfiles Directory (Files) (File) testfile2 Working Directory Network Directory (Files) (File) policy.cfg OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-15...

  • Page 36: Change File Attribute And Permissions

    If you are in another directory, you must specify the path and name for the file being deleted. The user of this command must have write privileges for any file being deleted. -> delete /flash/config.txt page 1-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 37: Managing Files On Switches

    Sep 13 16:45 working/ 64000 Sep 13 16:46 swlog1.log 64000 8 21:24 swlog2.log 1024 Sep 13 16:45 switch/ 1024 Sep 10 17:34 network/ Sep 13 16:41 random-seed 1024 Jun 22 1986 tk.dir/ OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-17...

  • Page 38: Utility Commands

    While performing the repair operation, the switch will display the errors found and specify those errors that have been repaired. If there are no errors found, then just the file system information is displayed. page 1-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 39: Deleting The Entire File System

    Caution. This command will delete all of the switch system files. All configurations programmed into the switch will be lost. Do not use this command unless you are prepared to reload all files. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 40: Loading Software Onto The Switch

    “Using the Switch as an FTP Server” on page 1-20. • TFTP Client—You can use the TFTP client functionality on an OmniSwitch 6250 to transfer software to/from a TFTP server. For details see “Using TFTP to Transfer Files” on page 1-25 •...

  • Page 41: Using The Switch As An Ftp Client

    OmniSwitch to retrieve File Server a file from a file server OmniSwitch FTP Client FTP Server OmniSwitch FTP Client Use the switch command to start its FTP client. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-21...
  • Page 42 220 cosmo FTP server (UNIX(r) System V Release 4.1) ready Name : Note. FTPv6 sessions are supported only on the OmniSwitch 6250. It is mandatory to specify the name of the particular IPv6 interface, if the FTPv6 server has been specified using its link-local address.

  • Page 43: Using Secure Shell Ftp

    You can use the sftp6 command followed by the IPv6 address or hostname of the SFTPv6 server to start an SFTPv6 session over an IPv6 environment. For example: OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-23...

  • Page 44: Closing A Secure Shell Ftp Session

    -> sftp6 fe80::a00:20ff:fea8:8961 int1 login as: Note. SFTPv6 sessions are supported only on the OmniSwitch 6250. It is mandatory to specify the name of the particular IPv6 interface, if the SFTPv6 server has been specified using its link-local address. You must have a login and password that is recognized by the IP address you specify. When you enter your login, the device you are logging in to, will request your password as shown here.

  • Page 45: Using Tftp To Transfer Files

    To use Zmodem, you must have a terminal emulator that supports the Zmodem protocol. There are many Zmodem products available that operate differently. You should consult the user manual that came with your terminal emulation software for details. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-25...
  • Page 46 Note. Files transferred via Zmodem are loaded into the flash directory. Before the new files can be used by the switch, you must transfer them to the switch /flash/working directory and reboot the switch. page 1-26 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 47: Registering Software Image Files

    Other files can be put into this directory if desired. The path to this directory is /flash/network. For more information on switch directories refer to the “Managing CMM Directory Content” chapter of this manual. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-27...

  • Page 48: Available Image Files

    Base Software CMM Security The following table lists the image files for the OmniSwitch 6250 Series switches. Most of the files listed here are part of the base switch configuration. Files that support an optional switch feature are noted in the table.

  • Page 49: Application Examples For File Management

    Transferring a File to the Switch Using FTP In this example, the user is adding a security feature to an OmniSwitch 6250 switch. To do this, the user must load the KFsecu.img image file onto the switch and then register the file by rebooting the switch.

  • Page 50: Creating A File Directory On The Switch

    6 Aug 5 17:03 test2.txt 6 Aug 5 17:03 test3.txt Use the command to move the test files from /flash/working to /flash/resources. -> mv test1.txt /flash/resources -> mv test2.txt /flash/resources -> mv test3.txt /flash/resources page 1-30 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 51: Ftp Client Application Example

    /flash/working. Use the command to verify. -> cd working -> ls Listing Directory /flash/working: 2048 Aug 3 12:32 ./ 2048 Aug 14 10:58 ../ 450 Aug 13 10:02 rrtest1.txt OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-31...
  • Page 52 To exit the switch FTP client mode, use the “quit” FTP command. Your current directory on the switch is /flash/working, which is the location from which you initiated the FTP client session. Use the command to verify your current directory. ftp> quit 221 Bye -> pwd /flash/working page 1-32 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 53: Creating A File Directory Using Secure Shell Ftp

    /flash/newssdir Use the ls command again to list the contents of the current (flash) directory. Note that the “newssdir” directory appears toward the bottom of the following list. sftp> ls OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-33...

  • Page 54: Transfer A File Using Secure Shell Ftp

    This display indicates the Secure Shell FTP session with IP address 11.333.20.135 is closed. The user is now logged into the OmniSwitch as a local device with no active remote connection. page 1-34 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 55: Verifying Directory Contents

    Displays the contents of a specified directory or the current working directory. Displays the content of a non primary switch in a stack. For more information about these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 56: Installing Software Licenses

    Some features require a software license and are restricted only to a licensed user. To activate licensed features, a license serial number must be purchased along with an authorization code from Alcatel-Lucent. The authorization code can then be used to generate a license file.

  • Page 57: Licensed Features

    Enables gigabit interfaces on No reboot required. “lite” models. Copper ports will be upgraded to provide gigabit capacity. Individual units in a stack can be upgraded. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-37...
  • Page 58 No license file required, can be enabled a period of 15 days. with CLI. Can only be unlocked if no boot.cfg file exists. Can be re-installed after expiration as long as no boot.cfg file exists. page 1-38 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 59: Setting The System Clock

    “Enabling DST” on page 1-42 for time zone abbrevia- tions. The following command sets the system clock to run on Pacific standard time: -> system timezone pst PST: (Coordinated Universal Time) UTC-8 hours OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-39...

  • Page 60: Time

    The following command will set the switch system time to 10:45:00 a.m: -> system time 10:45:00 -> The following command will set the switch system time to 3:14:00 p.m: -> system time 15:41:00 -> page 1-40 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 61: Daylight Savings Time Configuration

    11:00 by 1 For more details on syntax for this command, please refer to the OmniSwitch 6250/6450 CLI Reference Guide. You can also use the question mark (?) character in the command syntax to invoke the CLI help feature as described in the “Using the CLI”...

  • Page 62: Enabling Dst

    Last Sunday in Mar. Last Sunday in Oct. 1:00 at 2:00 a.m. at 3:00 a.m. Eastern Europe +02:00 Last Sunday in Mar. Last Sunday in Oct. 1:00 at 2:00 a.m. at 3:00 a.m. page 1-42 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 63 1st Sunday in Apr. at Last Sunday in Oct. 1:00 2:00 a.m. at 2:00 a.m. Hawaii -10:00 No default No default No default zm11 No standard name -11:00 No default No default No default OmniSwitch 6250/6450 Switch Management Guide May 2012 page 1-43...
  • Page 64 Setting the System Clock Managing System Files page 1-44 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 65: Logging Into The Switch

    Telnet or Secure Shell session on another device. It also includes information about managing sessions and specifying a DNS resolver. For more details about the syntax of referenced commands, see the OmniSwitch 6250/6450 CLI Reference Guide.

  • Page 66: In This Chapter

    Chapter 9, “Managing Switch User Accounts” Using the CLI Chapter 6, “Using the CLI” Using WebView to manage the switch Chapter 11, “Using WebView” Using SNMP to manage the switch Chapter 3, “Using SNMP” page 2-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 67: Login Specifications

    TCP connection is closed. Inactivity time-out period. The session timeout 4 minutes length of time the switch can remain idle during a login session before the switch will close the session. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-3...
  • Page 68 The following table describes the maximum number of sessions allowed on an OmniSwitch: OmniSwitch 6250/ Session OmniSwitch 6450 Telnet (v4 or v6) FTP (v4 or v6) SSH + SFTP (v4 or v6 secure sessions) HTTP Total Sessions SNMP page 2-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 69: Quick Steps For Logging Into The Switch

    Quick Steps for Logging Into the Switch Quick Steps for Logging Into the Switch The following procedure assumes that you have set up the switch as described in your OmniSwitch 6250/ 6450 Getting Started Guide and OmniSwitch 6250/6450 Hardware Users Guide. Setup includes: •...

  • Page 70: Overview Of Switch Login Components

    Console port—A direct connection to the switch through the console port. The console port is always enabled for the default user account. For more information about connecting to the console port, see your OmniSwitch 6250/6450 Hardware Users Guide. • Telnet—Any standard Telnet client may be used for remote login to the switch. This method is not secure.

  • Page 71: Using The Webview Management Tool

    The user information includes usernames and passwords; it may also include privilege information or reference an end-user profile name. For information about setting up the switch to communicate with external authentication servers, see the OmniSwitch 6250/6450 Network Configuration Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 72: Using Telnet

    Connected to fe80::a00:20ff:fea8:8961. Escape character is '^]'. login : Note. It is mandatory to specify the name of the particular IPv6 interface, if the target has been specified using the link-local address. page 2-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 73 Welcome to the Alcatel-Lucent OmniSwitch 6450 Software Version 6.6.1.R01 Development, October 05, 2007. Copyright(c), 1994-2007 Alcatel-Lucent. All Rights reserved. OmniSwitch(TM) is a trademark of Alcatel-Lucent registered in the United States Patent and Trademark Office. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 74: Using Ftp

    The following is an example of how to start an FTPv6 session to an OmniSwitch with an IPv6 address of fe80::a00:20ff:fea8:8961 -> ftp6 fe80::a00:20ff:fea8:8961 intf1 Connecting to [fe80::a00:20ff:fea8:8961]...connected 220 cosmo FTP server (UNIX(r) System V Release 4.1) ready Name: page 2-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 75 After logging in, you see the ftp-> prompt, where you can execute the FTP commands that are supported on the switch. For further information refer to the OmniSwitch 6250/6450 CLI Reference Guide. Note. You must use the binary mode (bin) to transfer image files through FTP.

  • Page 76: Using Secure Shell

    Both Telnet and FTP are available on the OmniSwitch but they do not support encrypted passwords. Note. Secure Shell may only be used to log into the switch to manage the switch. It cannot be used for Layer 2 authentication through the switch. page 2-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 77: Secure Shell Interface

    Shell FTP subsystem runs. Secure Shell FTP connects and logs into the specified host, then enters an interactive command mode. Refer to “Starting a Secure Shell Session” on page 2-17 for detailed information. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-13...

  • Page 78: Secure Shell Application Overview

    Secure Shell is used on the switches or servers being managed. Secure Shell Access Protocol Secure Shell Network OmniSwitch Secure Secure Shell Terminal Shell Client Server OmniSwitch as a Secure Shell Client page 2-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 79: Secure Shell Authentication

    The server disconnects itself from the client if a certain number of failed authentications are attempted or if a time-out period expires. Authentication is performed independent of whether the Secure Shell interface or the SFTP file transfer protocol is implemented. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-15...

  • Page 80: Connection Phase

    , PKA is still used even if this method of authentication was disabled using the ssh enforce pubkey-auth command. Rename, move, or delete the public key file to ensure that PKA is disabled on the switch. page 2-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 81: Starting A Secure Shell Session

    Once the Secure Shell session is established, you can use the remote device specified by the IP address on a secure connection from your OmniSwitch. Note. The login parameters for Secure Shell session login parameters can be affected by the session login-attempt session login-timeout CLI commands. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-17...
  • Page 82 IPv6 address or the hostname of the SSHv6 server to start an SSHv6 session. It is mandatory to specify the name of the particular IPv6 interface, if the SSHv6 server has been specified using its link-local address. page 2-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 83: Closing A Secure Shell Session

    SFTPv6 server has been specified using its link-local address. After logging in, you see the sftp> prompt. You may enter a question mark (?) to view available Secure Shell FTP commands and their definitions as shown here. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-19...

  • Page 84: Closing A Secure Shell Ftp Session

    OmniSwitch as a local device with no active remote connection. Note. Establishing and closing the Secure Shell FTPv6 connection is similar to that of the Secure Shell FTP connection. page 2-20 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 85: Modifying The Login Banner

    Welcome to the Alcatel-Lucent OmniSwitch 6450 Software Version 6.6.1.R01 Development, October 05, 2007. Copyright(c), 1994-2007 Alcatel-Lucent. All Rights reserved. OmniSwitch(TM) is a trademark of Alcatel-Lucent registered in the United States Patent and Trademark Office. Here is an example of a banner that has been changed:...

  • Page 86: Modifying The Text Display Before Login

    The pre-banner text cannot be configured for FTP sessions. To remove a text display before the login prompt, delete the pre_banner.txt file (it is recreated at the next bootup and will be empty), or modify the pre_banner.txt file. page 2-22 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 87: Configuring Login Parameters

    In this example, any new WebView session will have a time-out of 10 minutes. Current WebView sessions are not affected. For more information about WebView sessions, see Chapter 11, “Using WebView.” OmniSwitch 6250/6450 Switch Management Guide May 2012 page 2-23...

  • Page 88: Enabling The Dns Resolver

    You can disable the IPv6 DNS resolver by using the no form of the ip domain-lookup command. For more information, refer to the OmniSwitch 6250/6450 CLI Reference Guide. Specify the IPv6 addresses of up to three servers with the ipv6 name-server CLI command.

  • Page 89: Verifying Login Settings

    Displays the current DNS resolver configuration and status. For more information about these commands, refer to the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 90 Verifying Login Settings Logging Into the Switch page 2-26 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 91: Chapter 3 Using Snmp

    SNMP managers and SNMP agents on an IPv4 as well as on an IPv6 network. Network administrators use SNMP to monitor network performance and to manage network resources. SNMP functionality over IPv6 environment can be configured only on an OmniSwitch 6250. In This Chapter This chapter describes SNMP and how to use it through the Command Line Interface (CLI).

  • Page 92: Snmp Specifications

    UDP port 162, SNMPv3, Enabled Community Strings snmp community map Enabled SNMP Security setting snmp security Privacy all (highest) security Trap filtering snmp trap filter Disabled Trap Absorption snmp trap absorption Enabled page 3-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 93 SNMP Defaults Parameter Description Command Default Value/Comments Enables the forwarding of traps to snmp trap to webview Enabled WebView. Enables or disables SNMP snmp authentication trap Disabled authentication failure trap forwarding. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-3...

  • Page 94: Quick Steps For Setting Up An Snmp Management Station

    ---------------------------------------------------+---------+--------+------ 172.21.160.32/4000 enable 172.21.160.12/5000 enable user1 0300:0000:0000:0000:0211:d8ff:fe47:470b/4001 enable user2 0300:0000:0000:0000:0211:d8ff:fe47:470c/5001 enable For more information about this display, see the “SNMP Commands” chapter in the OmniSwitch 6250/ 6450 CLI Reference Guide. page 3-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 95: Quick Steps For Setting Up Trap Filters

    -> show snmp station ipAddress/udpPort status protocol user ---------------------------+---------+--------+------------------------------- 210.1.2.1/162 enable usermark2 The usermark2 account is established on the SNMP station at IP address 210.1.2.1. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-5...

  • Page 96: Filtering By Individual Traps

    For trap numbers refer to the “Using SNMP For Switch Security” on page 3-10. For more information on the CLI commands and the displays in these examples, refer to the OmniSwitch 6250/6450 CLI Reference Guide. page 3-6 OmniSwitch 6250/6450 Switch Management Guide...

  • Page 97: Snmp Overview

    In an unsolicited notification, the SNMP agent in the switch sends a trap PDU to the SNMP manager to inform it that an event has occurred. The SNMP manager normally does not send confirmation to the agent acknowledging receipt of a trap. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-7...

  • Page 98: Using Snmp For Switch Management

    Although MIB browsers vary depending on which software package is used, they all have a few things in common. The browser must compile the Alcatel-Lucent switch MIBs before it can be used to manage the switch by issuing requests and reading statistics. Each MIB must be checked for dependencies and the MIBs must be compiled in the proper order.

  • Page 99: Snmpv2

    • Encryption—Scrambling the contents of a packet to prevent it from being learned by an unauthorized source. • Authentication—Determining that the message is from a valid source holding the correct privileges. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-9...

  • Page 100: Using Snmp For Switch Security

    The display is similar to the one shown here: ->show snmp community map Community mode : enabled status community string user name --------+--------------------------------+-------------------------------- enabled comstring2 community_user1 This display also verifies that the community map mode is enabled. page 3-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 101: Encryption And Authentication (Snmpv3)

    = snmp chassis interface , Write for domains = None , Snmp authentication = MD5, Snmp encryption = DES The user’s SNMP authentication is shown as MD5 and SNMP encryption is shown as DES. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-11...

  • Page 102: Setting Snmp Security

    Encrypted v3 Sets, Gets, and Get-Nexts privacy set Authenticated v3 Gets and Get-Nexts Encrypted v3 Sets, Gets, and Get-Nexts privacy all Encrypted v3 Sets, Gets, and Get-Nexts traps only All SNMP requests are rejected. page 3-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 103: Working With Snmp Traps

    Procedures for filtering individual traps can be found in the Quick Steps for “Filtering by Individual Traps” on page 3-6. For a list of trap names, ID numbers, and their descriptions refer to the table “Using SNMP For Switch Security” on page 3-10. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-13...

  • Page 104: Authentication Trap

    When WebView forwarding is enabled, all traps sent by switch applications are also forwarded to WebView. The following command allows a WebView session to retrieve the trap history log: -> snmp trap to webview enable page 3-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 105: Snmp Mib Information

    For MIB Id number 87042, the MIB table name is vacmContextTable. This table is found in the SNMP-VIEW-BASED-ACM MIB, which serves as the view-based access control model (VACM) for the SNMP. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-15...

  • Page 106: Industry Standard Mibs

    SNMPv2-SMI, based access control. SNMPv2-TC, SNMPv2-CONF, SNMP- FRAMEWORK- IF-MIB IF-MIB, RFC 2863 The Interfaces Group MIB. Contains generic SNMPv2-SMI, information about the physical interfaces of the entity. SNMPv2-TC, SNMPv2-CONF, SNMPv2-MIB, IANAifType-MIB page 3-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 107 SNMPv2-TC, SNMPv2-CONF, IF-MIB, IPMROUTE-STD- Q-BRIDGE-MIB, The Bridge MIB Extension module for managing Pri- SNMPv2-SMI, RFC 2674 ority and Multicast Filtering, defined by IEEE 802.1D. SNMPv2-TC, SNMPv2-CONF, SNMP- FRAMEWORK- MIB, BRIDGE-MIB, P-BRIDGE-MIB OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-17...
  • Page 108 SNMP Applications, Proxy SNMP Entity Remote SNMPv2-SMI, RFC 2573 Configuration. SNMPv2-TC, SNMPv2-CONF, SNMP- FRAMEWORK- MIB, SNMP-TARGET SNMP-TARGET-MIB, SNMP Applications, Proxy SNMP Entity Remote SNMPv2-SMI, RFC 2573 Configuration. SNMPv2-TC, SNMPv2-CONF, SNMP- FRAMEWORK- page 3-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 109 Transmission Control Protocol by using SMIv2. SNMPv2-CONF TUNNEL-MIB, IP Tunnel MIB SNMPv2-SMI, RFC 2667 SNMPv2-TC, SNMPv2-CONF, IF-MIB UDP-MIB, RFC 2013 SNMPv2 Management Information Base for the User SNMPv2-SMI, Datagram Protocol by using SMIv2. SNMPv2-CONF OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-19...

  • Page 110: Enterprise (Proprietary) Mibs

    SNMPv2-CONF ALCATEL-IND1- Definitions of managed objects for the Health Moni- SNMPv2-SMI, HEALTH-MIB toring subsystem. SNMPv2-CONF ALCATEL-IND1-IGMP- Definitions of managed objects for the IPv4 Multicast SNMPv2-TC, MIB. SNMPv2-SMI, SNMPv2-CONF, INET-ADDRESS- MIB, IF-MIB page 3-20 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 111 Definitions of the MIB module for the address learning SNMPv2-SMI, LPS-MIB MIB addresses entity. SNMPv2-TC, IF-MIB, Q-BRIDGE-MIB, ALCATEL-IND1- SYSTEM-MIB, SNMPv2-CONF ALCATEL-IND1- Definitions of managed objects for the Source Learn- SNMPv2-SMI, MAC-ADDRESS-MIB ing MAC Address subsystem. SNMPv2-TC, SNMPv2-CONF, IF-MIB, Q-Bridge-MIB OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-21...
  • Page 112 Definitions of managed objects for the Quality of Ser- SNMPv2-SMI, QOS-MIB vice (QoS) subsystem. SNMPv2-TC ALCATEL-IND1- Definitions of managed objects for the Router Discov- SNMPv2-SMI, RDP-MIB ery Protocol (RDP) subsystem. SNMPv2-TC, SNMPv2-CONF page 3-22 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 113 Definitions of managed objects for the VLAN Span- SNMPv2-SMI, VLAN-STP-MIB ning Tree Protocol (STP) subsystem. SNMPv2-CONF, BRIDGE-MIB ALCATEL-IND1-WEB- Definitions of managed objects for the Web Based SNMPv2-SMI, MGT-MIB Management subsystem. SNMPv2-TC, SNMPv2-CONF, INET-ADDRESS- OmniSwitch 6250/6450 Switch Management Guide May 2012 page 3-23...

  • Page 114: Verifying The Snmp Configuration

    This command also dis- plays the Enabled/Disabled status of SNMP absorption and the Traps to WebView service. For more information about the resulting displays from these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. page 3-24...

  • Page 115: Configuring Network Time Protocol (Ntp)

    This chapter describes the basic components of the OmniSwitch implementation of Network Time Proto- col and how to configure it through Command Line Interface (CLI). CLI commands are used in the configuration examples; for more details about the syntax of commands, see the OmniSwitch 6250/6450 CLI Reference Guide.

  • Page 116: Ntp Specifications

    0 Used to activate client ntp client disabled Used to activate NTP client ntp broadcast disabled broadcast mode Used to set the advertised broadcast ntp broadcast-delay 4000 microseconds delay, in microseconds page 4-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 117: Ntp Quick Steps

    You can check the list of servers associated with this client using the show ntp client server-list command, as shown: -> show ntp client server-list IP Address Delay Offset Disp ================+===+=======+====+==========+=================+========== 1.2.5.6 0.06 -0.673 0.017 OmniSwitch 6250/6450 Switch Management Guide May 2012 page 4-3...
  • Page 118 -> show ntp client Current time: THU SEP 15 2005 17:44:54 (UTC) Last NTP update: THU SEP 15 2005 17:30:54 Client mode: enabled Broadcast client mode: disabled Broadcast delay (microseconds): 4000 page 4-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 119: Ntp Overview

    Protocols that do this include NTP. Note. The OmniSwitch can only be an NTP client in an NTP network. It cannot act as an NTP server. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 4-5...

  • Page 120: Stratum

    A switch (regardless of its status as either a client or server) must be peered with another switch. Peer- ing allows NTP entities in the network of the same stratum to regard each other as reliable sources of time and exchange time information. page 4-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 121 Note. Alcatel-Lucent current implementation of NTP only allows the OmniSwitch to act as a passive client, not as a server. A passive client only receives NTP information and adjusts its time accordingly. In the above example, an OmniSwitch could be either Server 3a or 3b.

  • Page 122: Authentication

    MD5 key written as a 1 to 31 character ASCII string with each character standing for a key octet. The key file (with identical MD5 keys) must be located on both the local NTP client and the client’s server. page 4-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 123: Configuring Ntp

    NTP hosts. The correct time is determined from an NTP message based on a pre-config- ured latency or broadcast delay in the order of a few milliseconds. To set the broadcast delay, enter the ntp broadcast-delay command as shown: -> ntp broadcast delay 1000 OmniSwitch 6250/6450 Switch Management Guide May 2012 page 4-9...

  • Page 124: Ntp Servers

    For example, to set the minimum poll time to 128 seconds, enter the following: -> ntp server 1.1.1.1 minpoll 7 This would set the minimum poll time to 2 = 128 seconds. page 4-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 125 To specify an NTP as preferred, use the ntp server command with the server IP address (or domain name) and the prefer keyword, as shown: -> ntp server 1.1.1.1 prefer OmniSwitch 6250/6450 Switch Management Guide May 2012 page 4-11...

  • Page 126: Using Authentication

    A key can be set to untrusted status by using the ntp key command with the untrusted keyword. For example, to set key ID 5 to untrusted status, enter the following: -> ntp key 5 untrusted page 4-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 127: Verifying Ntp Configuration

    Displays information about all authentication keys. For more information about the resulting displays from these commands, see the “NTP Commands” chap- ter in the OmniSwitch 6250/6450 CLI Reference Guide. Examples of the show ntp client, show ntp server status, and show ntp client server-list command outputs are given in the section “NTP Quick Steps”...
  • Page 128 Verifying NTP Configuration Configuring Network Time Protocol (NTP) page 4-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 129: Chapter 5 Managing Cmm Directory Content

    “idle” for the purposes of CMM control. Note. Mixing OmniSwitch 6250 and OmniSwitch 6450 models in the same stack is not supported. Management of the stack is run by the stack configuration software. A detailed description of the stack configuration software and how it works is provided in the “Managing Stacks”...

  • Page 130: Cmm Specifications

    Disaster Recovery Supported Note: The format of the Alcatel-Lucent Certified USB Flash Drive must be FAT16. To avoid file corruption issues the USB Drive must be stopped before removing from a PC. Directory names are case sensitive and must be lower case.

  • Page 131: Cmm Files

    The management of a stack or single switch is controlled by three types of files: • Image files, which are proprietary code developed by Alcatel-Lucent to run the hardware. These files are not configurable by the user, but can be upgraded from one release to the next. These files are also known as archive files as they are really the repository of several smaller files grouped under a common heading.

  • Page 132: Where Is The Switch Running From

    Once the contents of the working directory are established as good files, then these files can be saved to the certified directory and used as the most reliable software to which the switch can be rolled back in an emergency situation. page 5-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 133: Software Rollback Configuration Scenarios For A Single Switch

    Running Configuration is Overwritten by the Certified Directory on Boot OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-5...
  • Page 134 The changes made and saved to the working directory are not in effect. The switch can be booted from the working directory by using the reload working command. page 5-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 135 Running Configuration is Saved to Working, then to the Certified Directory OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-7...
  • Page 136 Scenario 4: Roll back to Previous Version of Switch Software Later that year, an upgraded image file is released from Alcatel-Lucent. The network administrator loads the new file through FTP to the working directory of the switch and reboots the switch from the working directory.

  • Page 137: Redundancy

    Additional switches in a stack are set to “idle” for the purposes of redundancy. For more information on managing a stack of switches, see the “Managing Stacks” chapter found in the related OmniSwitch 6250/6450 Hardware Users Guide. When two CMMs are running in a stack, one...
  • Page 138 “Copying the Working Directory to the Certified Directory” on page 5-21, while synchronizing the switch is described in “Synchronizing the Primary and Secondary CMMs” on page 5-27. page 5-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 139 “Copying the Working Directory to the Certified Directory” on page 5-21, while synchronizing the switch is described in “Synchronizing the Primary and Secondary CMMs” on page 5-27. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-11...
  • Page 140 The working primary CMM is then copied to directory is then switch. the certified direc- copied to the certi- tory. fied directory. Synchronizing a Stack with Three More Switches page 5-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 141: Managing The Directory Structure (Non-Redundant)

    “Managing Redundancy in a Stack and CMM” on page 5-25. See the related OmniSwitch 6250/6450 Hardware Users Guide for more information on switch redundancy. Rebooting the Switch When booting the switch, the software in the certified directory is loaded into the RAM memory of the...
  • Page 142 -> reload primary cancel To cancel all scheduled reboots with a single command, enter the following: -> reload cancel page 5-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 143 You can check the status of a reboot set for a later time by entering the following command: -> show reload -> show reload status reload command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-15...

  • Page 144: Copying The Running Configuration To The Working Directory

    To save these changes, it is necessary to save the contents of the running configuration to the working directory. page 5-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 145 Switch Running From?” on page 5-4 for an explanation. copy running-config working write memory commands are described in detail in the OmniSwitch 6250/6450 CLI Reference Guide. Note. The saved boot.cfg file is overwritten if the takeover command is executed after the copy running-config working...

  • Page 146: Rebooting From The Working Directory

    “Copying the Certified Directory to the Working Directory” on page 5-22, or by using the reload command as described in “Rebooting the Switch” on page 5-13. page 5-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 147 To schedule a working directory reboot of the CMM at 8:00pm with a rollback time-out of 10 minutes, you would enter: -> reload working rollback-timeout 10 at 20:00 Note. Scheduled reboot times should be entered in military format ( a twenty-four hour clock). OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-19...
  • Page 148 To cancel a rollback time-out, enter the reload cancel command as shown: -> reload primary cancel -> reload cancel reload working command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide. page 5-20 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 149: Copying The Working Directory To The Certified Directory

    Note. Only software that has been thoroughly validated as viable and reliant software has to be copied to the certified directory. Once you copy software to the certified directory, you will not be able to recover a previous version of the image or configuration files. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-21...

  • Page 150: Copying The Certified Directory To The Working Directory

    OmniSwitch 6250/6450 CLI Reference Guide. Note. In order for this command to work, the amount of free space in flash must equal the size of the files being copied.

  • Page 151: Show Currently Used Configuration

    CMM is currently controlling the switch (primary or secondary). It also displays whether the working and certified directories are the same, and if a synchronization is needed between the primary and secondary CMM. show running-directory command is described in detail in the OmniSwitch 6250/6450 CLI Refer- ence Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 152: Show Switch Files

    2486643 Alcatel-Lucent NI Software KFos.img 6.6.3.311.R01 941331 Alcatel-Lucent OS KFsecu.img 6.6.3.311.R01 371661 Alcatel-Lucent Security Management If no directory is specified, the files that have been loaded into the running configuration are shown. page 5-24 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 153: Managing Redundancy In A Stack And Cmm

    “idle” and the next available “idle” switch becomes the secondary CMM. For more information on stacks, see the “Managing Stacks” chapter found in the OmniSwitch 6250/6450 Hardware Users Guide. You can specify a reboot of the secondary CMM by using the secondary keyword in conjunction with the reload command.

  • Page 154: Copying The Working Directory To The Certified Directory

    This command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide. Note. When synchronizing the primary and secondary CMMs, it is important to remember that the boot.params file and the switch date and time are not automatically synchronized. See the OmniSwitch 6250/6450 Getting Started Guide for information on the boot.params file, and...

  • Page 155: Synchronizing The Primary And Secondary Cmms

    This process copies the files in the certified directory of the primary CMM to the certified directory of the secondary CMM. This prevents the secondary CMM from rebooting using incorrect or out-of-date soft- ware if the primary CMM goes down. This command synchronizes all switches in a stack. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-27...
  • Page 156 To synchronize the secondary CMM to the primary CMM, enter the following command at the prompt: -> copy flash-synchro copy flash-synchro command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide. Note. When synchronizing the primary and secondary CMMs, it is important to remember that the boot.params file and the switch date and time are not automatically synchronized.

  • Page 157: Swapping The Primary Cmm For The Secondary Cmm

    In a stack with three or more switches, the secondary CMM takes over as primary and the original primary becomes “idle.” The next available idle switch becomes the new secondary CMM. For more information on stacks, see the “Managing Stacks” chapter found in the OmniSwitch 6250/6450 Hardware Users Guide.

  • Page 158: Show Currently Used Configuration

    ALL, or a list of specific modules. Refer to the following section for additional information on NI module behavior during a redundant takeover. show running-directory command is described in detail in the OmniSwitch 6250/6450 CLI Refer- ence Guide. page 5-30 OmniSwitch 6250/6450 Switch Management Guide...

  • Page 159: Ni Module Behavior During Takeover

    NIs is reloaded automatically if a management module takeover occurs. Data flow is interrupted on all NIs until the reload is complete. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 5-31...

  • Page 160: Using The Usb Flash Drive

    Using the USB Flash Drive An Alcatel-Lucent certified USB flash drive can be connected the CMM and used to transfer images to and from the flash memory on the switch. This can be used for upgrading switch code or backing up files.

  • Page 161: Disaster Recovery Using Usb

    CMM become corrupted, deleted, or the switch is unable to boot from the CMM for other reasons. The following is an example for an OmniSwitch 6250: It is recommended to prepare the USB flash drive prior to needing it for disaster recovery.

  • Page 162: Emergency Restore Of The Boot.cfg File

    Once the boot.cfg file is confirmed to be good, it has to be saved to the certified directory by using the procedure described in “Copying the Working Directory to the Certified Directory” on page 5-21. page 5-34 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 163: Displaying Cmm Conditions

    Displays microcode versions installed on the switch. For more information on the resulting displays from these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. An example of the output for the show microcode command is given in “Show Switch Files”...
  • Page 164 Displaying CMM Conditions Managing CMM Directory Content page 5-36 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 165: Using The Cli

    Each CLI command applicable to the switch is defined in the OmniSwitch 6250/6450 CLI Reference Guide. All command descriptions listed in the Reference Guide include command syntax definitions, defaults, usage guidelines, example screen output, and release history.

  • Page 166: Cli Specifications

    Command Help • Keyword Completion Command History (up to 30 commands) • Command Logging (up to 100 commands; detailed information) • Syntax Error Display • Alias Command Option • • More Command OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-2...

  • Page 167: Cli Overview

    OmniSwitch 6250/6450 Getting Started Guide. Note. If you are using an OmniSwitch 6250, 6450 switch in a stacked configuration, you must be connected to the console port of the primary switch. For detailed information on primary switch status, refer to the “Managing Stacks”...

  • Page 168: Command Entry Rules And Syntax

    To use spaces within a user-defined text string, enclose the entry in quotation marks (“ ”). If you receive a syntax error (that is, ERROR: Invalid entry:), double-check your command as written • and re-enter it exactly as described in the OmniSwitch 6250/6450 CLI Reference Guide. Be sure to include all syntax option parameters. •...

  • Page 169: Using "Show" Commands

    VLAN. Using the “No” Form The OmniSwitch 6250/6450 CLI Reference Guide defines all CLI commands and explains their syntax. Whenever a command has a “no” form, it is described on the same page as the original command.

  • Page 170: Partial Keyword Completion

    In this case, pressing Tab causes the CLI to complete the common prefix and place the cursor at the end of the prefix. In this case, no space is placed at the end of the keyword. Note. The keyword completion feature accepts wildcards. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-6...

  • Page 171: Command Help

    PING, NO, MAC-RANGE, MAC, LANPOWER, IP, IPV6, ICMP, HTTPS, HRE, HEALTH, GMAP, DEBUG, CLEAR, ARP, AMAP, 802.1X AAA & Configuration USER, SHOW, PASSWORD, NO, END-USER, DEBUG, Manager CONFIGURATION, AAA Interface TRAP, SHOW, NO, INTERFACES, FLOW, DEBUG, 10GIG page 6-7 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 172 Using the CLI Command Help Command Set Name Commands IP Routing & Multicast DEBUG, TRACEROUTE6, SHOW, PING6, NO, IPV6, IP, CLEAR SHOW, QOS, POLICY, NO, DEBUG Debug UPDATE, SHOW, NO, DEBUG OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-8...

  • Page 173: Tutorial For Building A Command Using Help

    VLAN, and want to give the VLAN a name, you can presume the proper syntax for this task is NAME as shown in the VLAN Manager Command Set. page 6-9 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 174 -----+-------+------+-------+------+----+-----+--------------------------------- VLAN 1 test vlan 2 The second entry verifies that a VLAN was created, the VLAN ID is 33, and the name is test vlan 2. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-10...

  • Page 175: Cli Services

    “m” and the “a”. -> show m acrocode Use the Delete key to remove the “a” and type “i”. -> show microcode Press Enter to execute the command. page 6-11 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 176: Recalling The Previous Command Line

    Then, use the Left Arrow key to position the cursor between the “r” and the “c” characters. To insert the missing character, type “o”. -> !! -> show microcode To execute the corrected command, press Enter. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-12...

  • Page 177: Syntax Checking

    Then, if a valid related command is entered next, the CLI assumes the stored prefix is part of the next command. In this case, you are only required to enter the suffix information for the next command. page 6-13 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 178: Example For Using Prefix Recognition

    CLI is vlan 501, the following is displayed: -> show prefix Current prefix: vlan 501 If you issue the show prefix command when there is no prefix stored by the CLI, a “no prefix” message is displayed. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-14...

  • Page 179: Prefix Prompt

    9 ip bgp pn 10 show ip bgp 11 show history In the example above, the show history command is listed last because it is the command that was executed most recently. page 6-15 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 180 Note. The Partial Keyword Completion feature described on page 6-6 works within the CLI history buffer. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-16...

  • Page 181: Logging Cli Commands And Entry Results

    6-15. Refer to the sections below for more information on configuring and using CLI command logging. For detailed information related to command logging commands, refer to the OmniSwitch 6250/6450 CLI Reference Guide. Enabling Command Logging By default, command logging is disabled. To enable command logging on the switch, enter the following command: ->...

  • Page 182: Viewing The Current Command Logging Status

    SUCCESS displays in the Result field. If a syntax or configuration error occurred at the time a command was entered, details of the error display. For example: Result : ERROR: Ip Address must not belong to IP VLAN 67 subnet OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-18...

  • Page 183: Customizing The Screen Display

    -> prompt time date string ##=> 01:31:01 04/29/02##=> For an example of using a stored prefix as part of the prompt, refer to “Prefix Prompt” on page 6-15. page 6-19 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 184: Setting Session Prompt As System Name

    (through CLI, WebView, SNMP) gets priority over the DHCP server values. For more information on the session prompt default command, refer to the OmniSwitch 6250/6450 CLI Reference Guide. Displaying Table Information The amount of information displayed on your console screen can be extensive, especially for certain show commands.

  • Page 185: Filtering Table Information

    The filter command is case sensitive. When using the slash (/) command, type the text exactly as it would appear in the CLI table. For additional information about filtering, refer to “Using a Wildcard to Filter Table Information” on page 6-25. page 6-21 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 186: Multiple User Sessions

    The other sessions are identi- fied by session number, user name, the type of access, port type, IP address, and user privileges. The output definitions are defined in the table on page 6-23. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-22...

  • Page 187: Listing Your Current Login Session

    Read-Write families The command families available with the read-write access of the user. See the table beginning on page 6-24 for a listing of valid families. page 6-23 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 188: Terminating Another Session

    The command syntax requires you to specify the number of the session you want to kill. You can use the who command for a list of all current user sessions and their numbers. The kill command takes effect immediately. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-24...

  • Page 189: Application Example

    CLI table and to type the asterisk (*) character before and after the text. The More? mode prompt automatically re-appears. Enter filter pattern: *vlan* More? [next screen <sp>*, next line <cr>*, filter pattern </>*, quit <q>] OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-25...
  • Page 190 More? [next screen <sp>*, next line <cr>*, filter pattern </>*, quit <q>] The screen displays ten table rows, each of which contain the text pattern “vlan”. Alcatel-Lucent CLI uses a single level command hierarchy. (The screen rows shown above and below the table are not counted as part of the 10 rows.) If you want to display the rows one line at a time, press Enter instead of the space bar...

  • Page 191: Verifying Cli Usage

    Shows the enable status of the more mode along with the number of lines specified for the screen display. For more information about the resulting displays from these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. Additional information can also be found in “Using “Show”...
  • Page 192 Verifying CLI Usage Using the CLI page 6-28 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 193 “Applying Configuration Files to the Switch” on page 7-6 • “Configuration File Error Reporting” on page 7-7 • “Text Editing on the Switch” on page 7-9 • • “Creating Snapshot Configuration Files” on page 7-10 OmniSwitch 6250/6450 Switch Management Guide May 2012 page 7-1...

  • Page 194: Working With Configuration Files

    Chapter 1, “Managing System Files.” Apply the configuration file to the switch by using the configuration apply command as shown here: -> configuration apply dhcp_relay.txt File configuration <dhcp_relay.txt>: completed with no errors page 7-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 195 To synchronize the running configuration and the saved configuration, use the write memory command. For more information about these displays, refer to the OmniSwitch 6250/6450 CLI Reference Guide. Use a the show ip helper command to verify that the DHCP Relay parameters defined in the configu- ration files were actually implemented on the switch.

  • Page 196: Quick Steps For Applying Configuration Files

    -> show configuration status File configuration: none scheduled Apply the file by executing the configuration apply using the at keyword with the relevant date and time. -> configuration apply bncom_cfg.txt at 09:00 04 july page 7-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 197: Setting An Application Session For A Specified Time Period

    The “scheduled at” date and time show when the file will be applied. This value is 6 hours and 15 minutes from the date and time the command was issued. For more information about this display see “Configuration File Manager Commands” in the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 7-5...

  • Page 198: Configuration Files Overview

    The following displays where the timed session was set on March 10, 2002 at 01:00 using the configuration apply group_config in 6:10 syntax. -> show configuration status File configuration <group_config>: scheduled at 03/10/02 07:10 page 7-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 199: Cancelling A Timed Session

    File configuration: none scheduled For more details about the CLI commands used to apply configuration files or to use timer sessions, refer to “Configuration File Manager Commands” in the OmniSwitch 6250/6450 CLI Reference Guide. Configuration File Error Reporting If you apply a configuration file to the switch that contains significant errors, the application may not work.

  • Page 200: Setting The Error File Limit

    For error details, you can view the contents of a generated error file. To view the contents of an error file, use the more command. For example: -> more asc.1.snap.1.err For more information, refer to “Displaying a Text File” on page 7-9. page 7-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 201: Displaying A Text File

    -> vi /flash/working switchlog.txt You can invoke the Vi editor in read-only mode by using the following syntax. -> view To exit the Vi editor, use the Cap ZZ key sequence. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 7-9...

  • Page 202: Creating Snapshot Configuration Files

    -> configuration snapshot vlan qos snmp You can verify that a new snapshot file is created by using the command to list all files in the /flash directory. page 7-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 203: User-Defined Naming Options

    Comment lines are located at the beginning of the snapshot file to form a sort of header. They also appear intermittently throughout the file to identify switch features or applications that apply to the commands that follow them. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 7-11...
  • Page 204 ! Server load balance : ! System service : ! Web : ! AMAP : ! GMAP : ! Module : ! Lan Power : ! NTP : ! RDP : page 7-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 205 This file shows configuration settings for the Chassis, IP, AAA, SNMP, IP route manager, Spanning tree, and Bridging services. Each of these services have configuration commands listed under their heading. All other switch services and applications are either not being using or are using default settings. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 7-13...

  • Page 206: Verifying File Configuration

    A snapshot is a sin- gle text file that can be viewed, edited, and reused as a configuration file. write terminal Displays the switch’s current running configuration for all features. page 7-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 207: Managing Automatic Remote Configuration Download

    “Zero Touch License Upgrade” on page 8-22 • “Troubleshooting” on page 8-23 For related information on the initial setup of the switch, see the OmniSwitch 6250/6450 Getting Started Guide. For information on switch file management, see Chapter 1, Managing System Files. OmniSwitch 6250/6450 Switch Management Guide...

  • Page 208: Automatic Remote Configuration Specifications

    Association (operates only on combo ports and uplink ports). Configuration Load Mode (no boot.cfg file present). Unsupported Features: • ISSU and IPv6 are not supported. • Upgrade of uboot, miniboot, or FPGA files is not supported. page 8-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 209: Automatic Remote Configuration Defaults

    (* represents image filename) Location: FTP/SFTP/TFTP Server Download location: /flash/working directory File download server Primary FTP/SFTP/TFTP Server Backup server for file download Secondary FTP/SFTP/TFTP Server Password for FTP/SFTP Server Same as username OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-3...

  • Page 210: Quick Steps For Automatic Remote Configuration

    • If a boot.cfg is already present in the working directory of the switch, Automatic Remote Configuration Download does not occur. page 8-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 211: Overview

    Alcatel-Lucent OmniSwitch TFTP Server Stores the instruction file. the config file and firmware. FTP/SFTP Server Stores the firmware and configuration for secure access Basic Network Components for Automatic Remote Configuration Download OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-5...

  • Page 212: Network Components

    Secondary FTP/SFTP file server address / type / username. For more details on all the component files downloaded during the automatic remote configuration download process, see - “Download Component Files” on page 8-12. page 8-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 213: File Servers And Download Process

    The LED status during different stages of the Automatic Remote Configuration download process is as follows: • DHCP phase: OK LED is flashing green • DHCP lease obtained: OK LED is solid green • DHCP phase stopped by console login: OK LED is solid green. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-7...

  • Page 214: Interaction With Other Features

    The link aggregate is associated as a tagged member of VLAN 127 and VLAN 1. • On completion of the Automatic Download and configuration process, the automatic link aggregate is disabled and all port associations are deleted. page 8-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 215: Automatic Remote Configuration Download Process

    (a reboot occurs only if no script file is downloaded). If available, commands in the script file are run and the DHCP client configuration is automatically removed on the default VLAN 1. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-9...

  • Page 216: Process Illustration

    TFTP server server address ? Get instruction file Found instruction file? Download Download firmware and/or Script boot.cfg only Reload Switch Run Script Switch is available remotely Illustration of Automatic Remote Configuration Process page 8-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 217: Additional Process Notes

    After the successful download of the script file, the DHCP IP interface is automatically deleted. However, SSH access remains enabled. Use the no aaa authentication ssh command to disable SSH connectivity if desired. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-11...

  • Page 218: Download Component Files

    SSH. • All contents of the instruction file are stored in the switch log (swlog.log) file as evidence of the last Automatic Remote Configuration download. page 8-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 219: Instruction File Syntax

    The specified protocol and username are used for the download. Example The instruction file has the Keyword:Value format as shown below: ! Alcatel-Lucent OmniSwitch OS6250 – Instruction file version 1.2.1 ! Firmware version Firmware version:OS_6_6_3_355_R01 Firmware location:/home/ftpboot/firmware ! Configuration file Config filename:boot_OS6250.cfg...

  • Page 220: Instruction File Usage Guidelines

    FTP/SFTP server and stored as boot.cfg in the /flash/working directory of the switch. If no script file is downloaded, the switch boots up normally according to the configurations specified in the boot.cfg file when the remote configuration download process is completed. page 8-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 221: Debug Configuration File

    • If the script file name mentioned in the instruction file is incorrect, then an error is logged in the switch log or swlog.log file. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-15...

  • Page 222: Lacp Auto Detection And Automatic Link Aggregate Association

    TFTP Server Stores the instruction file. optionally the config file and firmware FTP/SFTP Server Stores the firmware and configuration for secure access Network Components for LACP Auto Detection and Link Aggregate Association page 8-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 223: Dhcp Client Auto-Configuration Process

    Nearest-Edge Mode. See the “Nearest-Edge Mode Operation” on page 8-20 for additional information. Note. OmniSwitch must have at least one port with connectivity to the DHCP server through Management VLAN. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-17...
  • Page 224 If OmniSwitch receives LLDP PDUs with VLAN and port information from a Management switch in nearest edge mode, then the DHCP client interface is moved to user defined LLDP management VLAN on the network. page 8-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 225 DHCP lease. This condition applies for any type of DHCP client (untagged, tagged 127 or tagged with LLDP associated management VLAN). Once the DHCP client gets the lease, the Remote Config process does not stop even if the user logs on to the switch through console port. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-19...

  • Page 226: Nearest-Edge Mode Operation

    Nearest-edge MAC address and propagated throughout the network eventually reaching the Access Switch. For example: -> vlan 999 name “VLAN 999” -> vlan 999 port default 1/1 -> lldp destination mac-address nearest-edge -> lldp 1/1 tlv dot1 vlan-name enable page 8-20 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 227 LLDP PDUs, discover the Management VLAN, tag the port with that VLAN ID, and create a DHCP client interface on the Managment VLAN. This auto-configuration allows the DHCP client interface on the OmniSwitch to receive an IP address in the proper IP subnet. Example Nearest-Edge Configuration OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-21...

  • Page 228: Zero Touch License Upgrade

    Some features like OmniSwitch-Metro features require a software license for activation and are restricted only to a licensed user. To activate licensed features, a license serial number must be purchased along with an authorization code from Alcatel-Lucent. The authorization code can then be used to generate a license file.

  • Page 229: Troubleshooting

    TFTP server is not reachable. • Primary and secondary servers are not reachable. File download errors can occur when: • Files are corrupted. • File locations or names listed in the instruction file are incorrect. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-23...

  • Page 230: Error Description Table

    If the script file name mentioned in the instruction file is incorrect, then an error is logged in the switch log or swlog.log file. In such an instance, check the swlog.log file. The script file can be downloaded manually from the FTP/SFTP servers and implemented onto the OmniSwitch. page 8-24 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 231: Error Description Table

    Unable to remove Instruction Command file <File name and pathname> due to error in running the script file Failure commands. Error in executing the downloaded The downloaded script file cannot be run. script file OmniSwitch 6250/6450 Switch Management Guide May 2012 page 8-25...
  • Page 232 Troubleshooting Managing Automatic Remote Configuration Download page 8-26 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 233: Managing Switch User Accounts

    (except end-user profiles, which can only be configured on the switch). For information about setting up external servers that are configured with user information, see the “Managing Authentication Servers” chapter in the OmniSwitch 6250/6450 Network Configuration Guide. OmniSwitch 6250/6450 Switch Management Guide...

  • Page 234: User Database Specifications

    Maximum number of old passwords user password-history to retain in the password history. Minimum number of days user is user password-min-age 0 (disabled) blocked from changing password. page 9-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 235 Maximum number of failed login user lockout-threshold 0—no limit to the num- attempts allowed during the lockout ber of failed login window time period. attempts OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-3...

  • Page 236: Overview Of User Accounts

    Note. For information about setting up user information on an authentication (AAA) server, see the “Managing Authentication Servers” chapter of the OmniSwitch 6250/6450 Network Configuration Guide. Users typically log into the switch through one of the following methods: Console port—A direct connection to the switch through the console port.
  • Page 237 For more information about connecting to the switch through one of these methods, see Chapter 2, “Logging Into the Switch,”and the OmniSwitch 6250/6450 Getting Started Guide. For information about setting up the switch to allow user access through these interfaces, see Chapter 10, “Managing Switch Security.”...

  • Page 238: Startup Defaults

    An example of creating a user and setting access privileges for the account is given here: -> user thomas techpubs read-write domain-policy md5+des For more details about command syntax, see the OmniSwitch 6250/6450 CLI Reference Guide. page 9-6 OmniSwitch 6250/6450 Switch Management Guide...

  • Page 239: Quick Steps For Network Administrator User Accounts

    The default user is not an active user account. It constains the default user account settings, for new user accounts. For more information about the show user command, see the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide...

  • Page 240: Quick Steps For Creating Customer Login User Accounts

    Slot : 2, ports allowed : 1-8 Vlan Id : For more information about the show end-user profile command, see the OmniSwitch 6250/6450 CLI Reference Guide. Associate the profile with a user account. Enter the user command with the relevant username and password and specify Profile1.

  • Page 241: Default User Settings

    RADIUS or LDAP server on which privileges are not configured. For more information about these servers, see the “Managing Authentication Servers” chapter of the OmniSwitch 6250/6450 Network Configuration Guide. OmniSwitch 6250/6450 Switch Management Guide...

  • Page 242: Account And Password Policy Settings

    “Configuring Password Policy Settings” on page 9-16 “Configuring Global User Lockout Settings” on page 9-22 for more information. page 9-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 243: How User Settings Are Saved

    For information about using the write memory, copy running-config working, and configuration snapshot commands, see Chapter 5, “Managing CMM Directory Content,” Chapter 7, “Working With Configuration Files,” and the OmniSwitch 6250/6450 CLI Reference Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-11...

  • Page 244: Creating A User

    The password does not display in clear text in an ASCII configuration file produced by the snapshot command. Instead, it displays in encrypted form. See Chapter 7, “Working With Configuration Files,” information about using the snapshot command. page 9-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 245: Removing A User

    To remove a user from the local database, use the no form of the command: -> no user thomas The user account for thomas is removed from the local user database. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-13...

  • Page 246: User-Configured Password

    Enter the password command. The system displays a prompt for the new password: -> password enter old password: Enter the old password. (The password is concealed with asterisks.) A prompt displays for the new password. -> password enter old password:******** enter new password: page 9-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 247 (*) as one or more characters in a password is allowed as long as every character is not an asterisk. For example, password **123456** is allowed; password ******** is not allowed. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-15...

  • Page 248: Configuring Password Policy Settings

    To view the current policy configuration, use the show user password-policy command. For more infor- mation about this command and those used in the configuration examples throughout this section, see the OmniSwitch 6250/6450 CLI Reference Guide. page 9-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 249: Setting A Minimum Password Size

    For example: -> user password-size min 10 The minimum length for any passwords configured for users is now 10 characters. The maximum password length is 31 characters. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-17...

  • Page 250: Configuring The Username Password Exception

    For example, the password for the account username of public can not contain the word public in any part of the password. However, the username of another account is still allowed. page 9-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 251: Configuring Password Character Requirements

    Specifying zero with any of the these commands disables the requirement. For example, if the number of minimum uppercase characters is set to zero (the default), then there is no requirement for a password to contain any uppercase characters. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-19...

  • Page 252: Configuring Password Expiration

    For more information on the system date or time, see the OmniSwitch 6250/6450 Switch Management Guide. Note. The expiration will be reset to the global default setting (based on the user password-expiration command) if the user password is changed or the user password-expiration command is entered again.

  • Page 253: Configuring The Password History

    To disable the password history function, specify 0 as the number of old passwords to save. For example: -> user password-history 0 A password is dropped from the password history when it no longer falls within the number of passwords that are retained by the switch. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-21...

  • Page 254: Configuring The Minimum Age For A Password

    For more information about this command and those used in the configuration examples throughout this section, see the OmniSwitch 6250/6450 CLI Reference Guide. page 9-22 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 255: Configuring The User Lockout Window

    -> user lockout-window 30 Do not configure an observation window time period that is greater than the lockout duration time period (see “Configuring the User Lockout Duration Time” on page 9-25). OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-23...

  • Page 256: Configuring The User Lockout Threshold Number

    A locked user account is automatically unlocked when the lockout duration time (see “Configuring the User Lockout Duration Time” on page 9-25) is reached or the admin user manually unlocks the user account. page 9-24 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 257: Configuring The User Lockout Duration Time

    For example: -> user lockout-duration 60 Do not configure a lockout duration time that is less than the lockout window time period (see “Configur- ing the User Lockout Window” on page 9-23). OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-25...

  • Page 258: Manually Locking And Unlocking User Accounts

    “Configuring the User Lockout Duration Time” on page 9-25) is not config- ured for the switch, then it is only possible to manually unlock a user account with the user lockout command or by changing the user password. page 9-26 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 259: Configuring Privileges For A User

    Note. When modifying an existing user, the user password is not required. If you are configuring a new user with privileges, the password is required. The default user privileges can also be modified. See “Default User Settings” on page 9-9. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-27...

  • Page 260: Setting Up Snmp Access For A User Account

    When modifying a user’s SNMP access, the user password must be re-entered (or a new one config- • ured). This is required because the hash algorithm used to save the password in the switch depends on the SNMP authentication level. page 9-28 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 261: Snmp Access Without Authentication/Encryption

    SNMPv3 frames through the switch. Use the snmp security command to change the SNMP security level. For more information about configuring SNMP globally on the switch, Chapter 3, “Using SNMP.” OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-29...

  • Page 262: Snmp Access With Authentication/Encryption

    The key is indicated in the file by the syntax authkey key. See Chapter 7, “Working With Config- uration Files,” for information about using the snapshot command. The key is not displayed in the CLI. page 9-30 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 263: Removing Snmp Access From A User

    To deny SNMP access, enter the user command with the no snmp option: -> user thomas no snmp This command results in thomas no longer having SNMP access to manage the switch. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-31...

  • Page 264: Setting Up End-User Profiles

    9-32 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 265: Creating End-User Profiles

    If port ranges or VLAN ranges are not configured, a user with this profile will not be able to use any commands that require port or VLAN values or view any show outputs that contain port or VLAN values. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 266: Setting Up Port Ranges In A Profile

    For example: -> end-user profile Profile3 no port-list 3 In this example, all ports on slot 3 are removed from the profile. page 9-34 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 267: Setting Up Vlan Ranges In A Profile

    To remove a VLAN range from a profile, use the no form of the command and the VLAN ID of the start of the range to be removed. For example: -> end-user profile Profile3 no vlan-range 7 This command removes VLANs 7 and 8 from Profile3. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-35...

  • Page 268: Associating A Profile With A User

    The user information stored on an external server can include a profile name. When the user attempts to log into the switch, the switch will attempt to match the profile name to a profile stored on the switch. page 9-36 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 269: Removing A Profile From The Configuration

    Profile3 is deleted from the configuration. Note. If the profile name is associated with a user, and the profile is deleted from the configuration, the user will not have access to the switch. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 9-37...

  • Page 270: Verifying The User Configuration

    Displays hexadecimal values for command domains/families. For more information about the resulting displays from these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. An example of the output for the show user command is also given in “Quick Steps...

  • Page 271: Chapter 10 Managing Switch Security

    (CLI). CLI commands are used in the configuration examples; for more details about the syntax of commands, see the OmniSwitch 6250/6450 CLI Reference Guide. An overview of switch security is given in this chapter. In addition, configuration procedures described in this chapter include: •...

  • Page 272: Switch Security Specifications

    Switch Security Defaults Access to managing the switch is always available for the admin user through the console port, even if management access to the console port is disabled for other users. page 10-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 273: Switch Security Overview

    Logging can also be accomplished directly on the switch. For information about configuring local logging for switch access, see “Configuring Accounting for ASA” on page 10-12. For complete details about local logging, see the “Using Switch Logging” chapter in the OmniSwitch 6250/6450 Network Configuration Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 274: Authenticated Switch Access

    The authentication-only server supported by the switch is ACE/Server, which is a part of RSA Security’s SecurID product suite. RSA Security’s ACE/Agent is embedded in the switch. page 10-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 275: Interaction With The User Database

    For more information on authenticated VLANs, and authentication servers, see “Configuring Authenti- cated VLANs” and “Configuring Authentication Servers” in the OmniSwitch 6250/6450 Network Configuration Guide. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 10-5...

  • Page 276: Configuring Authenticated Switch Access

    Setting up Authenticated Switch Access involves the following general steps: Set Up the Authentication Servers. This procedure is described briefly in this chapter. See the “Managing Authentication Servers” chapter of the OmniSwitch 6250/6450 Network Configuration Guide for complete details. Set Up the Local User Database. Set up user information on the switch if user login or privilege infor- mation will be pulled from the switch.

  • Page 277: Quick Steps For Setting Up Asa

    For example: -> aaa radius-server rad1 host 10.10.1.2 timeout 3 For more information, see the “Managing Authentication Servers” chapter in the OmniSwitch 6250/6450 Network Configuration Guide. Use the aaa authentication command to specify the management interface through which switch access is permitted (such as console, telnet, ftp, http, or ssh).
  • Page 278 Service type = Ssh Authentication = Use Default, 1rst authentication server = rad1 2nd authentication server = local For more information about this command, see the OmniSwitch 6250/6450 CLI Reference Guide. page 10-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 279: Setting Up Management Interfaces For Asa

    For more information about configur- ing the switch to communicate with these servers, see the “Managing Authentication Servers” chapter of the OmniSwitch 6250/6450 Network Configuration Guide. Note. RADIUS or LDAP servers used for authenticated switch access can also be used with authenticated VLANs.

  • Page 280: Enabling Switch Access

    SNMP management access. If the default interface setting includes only RADIUS and/or ACE server, the default setting will not be used for SNMP. For example: -> no aaa authentication ftp -> aaa authentication default rad1 rad2 page 10-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 281: Using Secure Shell

    DSA key, use the Secure Shell tools available on your Unix or Windows system and copy the files to the /flash/network directory. For more information about Secure Shell, see Chapter 2, “Logging Into the Switch.” Note. Secure Shell cannot be used for Authenticated VLANs. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 10-11...

  • Page 282: Configuring Accounting For Asa

    Switch Logging feature. (For more information about Switch Logging, see the OmniSwitch 6250/6450 Network Configuration Guide.) To remove an individual server from the list of servers, enter the aaa accounting session command with the relevant server name(s), removing the desired server from the list.

  • Page 283: Verifying The Asa Configuration

    Displays information about a particular AAA server or AAA servers. address For more information about the resulting displays from these commands, see the OmniSwitch 6250/6450 CLI Reference Guide. An example of the output for the show aaa authentication command is also given “Quick Steps for Setting Up ASA”...
  • Page 284 Verifying the ASA Configuration Managing Switch Security page 10-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 285: Chapter 11 Using Webview

    11 Using WebView The switch can be monitored and configured using WebView, Alcatel-Lucent web-based device management tool. The WebView application is embedded in the switch and is accessible through the following web browsers: Internet Explorer 6 or later • Firefox2 or later •...

  • Page 286: Webview Cli Defaults

    Typically many of these settings are configured as the default. Different browsers (and different versions of the same browser) can have different dialogs for these settings. Check your browser help pages if you need help. page 11-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 287: Webview Cli Commands

    This command changes the HTTP port to 2000. To restore an HTTP port to its default value, use the default keyword as shown in the following example: -> http port default OmniSwitch 6250/6450 Switch Management Guide May 2012 page 11-3...

  • Page 288: Enabling/Disabling Ssl

    This command changes the secure HTTP port to 2500. To restore an HTTPS port to its default value, use the default keyword as shown in the following exam- ple: -> https port default page 11-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 289: Quick Steps For Setting Up Webview

    Toolbar—Used to access WebView features. • • Feature Options—Used to access specific configuration options for each feature (displayed in drop- down menus at the top of the page). • View/Configuration Area—Used to view/configure a feature. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 11-5...

  • Page 290: Banner

    Under each configuration group are switch features, identified by a name and an icon. For detailed configuration information on each feature, see other chapters in this guide, the OmniSwitch 6250/6450 Network Configuration Guide. Help pages are also available in WebView. page 11-6...

  • Page 291: View/Configuration Area

    After logging into WebView, a real-time graphical representation of the switch displays all of the switch’s current components. The feature configuration options on this page are used to config- ure the switch. OmniSwitch 6250/6450 Switch Management Guide May 2012 page 11-7...
  • Page 292 WebView Overview Using WebView page 11-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 293: Appendix A Software License And Copyright Statements

    Licensee further acknowledges and agrees that all rights, title, and interest in and to the Licensed Materials are and shall remain with Alcatel-Lucent and its licen- sors and that no such right, license, or interest shall be asserted with respect to such copyrights and trade- marks.
  • Page 294 Period, a defect in the Licensed Files appears, Licensee may return the Licensed Files to Alcatel-Lucent for either replacement or, if so elected by Alcatel-Lucent, refund of amounts paid by Licensee under this License Agreement. EXCEPT FOR THE WARRANTIES SET FORTH ABOVE, THE LICENSED MATERIALS ARE LICENSED “AS IS”...
  • Page 295 14.Third Party Materials. Licensee is notified that the Licensed Files contain third party software and materials licensed to Alcatel-Lucent by certain third party licensors. Some third party licensors (e.g., Wind River and their licensors with respect to the Run-Time Module) are third part beneficiaries to this License Agreement with full rights of enforcement.

  • Page 296: Third Party Licenses And Notices

    Alcatel-Lucent for a limited period of time. Alcatel-Lucent will provide a machine-readable copy of the applicable non-proprietary software to any requester for a cost of copying, shipping and handling.

  • Page 297: Linux

    “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 298 Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software inter- change; or, page A-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 299 Many people have made generous contributions to the wide range of software distributed through that system in reliance on OmniSwitch 6250/6450 Switch Management Guide May 2012 page A-7...
  • Page 300 SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS. page A-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 301 If this is what you want to do, use the GNU Library General Public License instead of this License. URLWatch: For notice when this page changes, fill in your email address. Maintained by: Webmaster, Linux Online Inc. Last modified: 09-Aug-2000 02:03AM. Views since 16-Aug-2000: 177203. OmniSwitch 6250/6450 Switch Management Guide May 2012 page A-9...

  • Page 302: University Of California

    ALTERNATIVELY, this product may be distributed under the terms of the GNU Public License, in which case the provisions of the GPL are required INSTEAD OF the page A-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 303: Apptitude, Inc

    Licensee, Licensee shall immediately return the EMWEB Product and any back-up copy to Alcatel- Lucent, and will certify to Alcatel-Lucent in writing that all EMWEB Product components and any copies of the software have been returned or erased by the memory of Licensee’s computer or made non-read- able.

  • Page 304: Sun Microsystems, Inc

    Time Module other than in connection with operation of the product. In addition, please be advised that: (i) the Run-Time Module is licensed, not sold and that Alcatel-Lucent and its licensors retain ownership of all copies of the Run-Time Module; (ii) WIND RIVER DISCLAIMS ALL IMPLIED WARRANTIES,...

  • Page 305: Remote-Ni

    PANYING WRITTEN MATERIALS.To the maximum extent permitted by applicable law, IN NO EVENT SHALL MOTOROLA BE LIABLE FOR ANY DAMAGES WHATSOEVER. Copyright (C) Motorola, Inc. 1989-2001 All rights reserved. Version 13.1 OmniSwitch 6250/6450 Switch Management Guide May 2012 page A-13...

  • Page 306: Boost C++ Libraries

    3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. page A-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 307: Curses

    Provided with this software is an open source implementation of the Lightweight Directory Access Proto- col (LDAP). Version 3 Copyright (C) 1990, 1998, 1999, Regents of the University of Michigan, A. Hartgers, Juan C. Gomez. All rights reserved. OmniSwitch 6250/6450 Switch Management Guide May 2012 page A-15...

  • Page 308: Bitmap.c

    Version 1.5 Copyright (C) 1986 by University of Toronto and written by Henry Spencer. AA.Free/OpenBSD Copyright (c) 1982, 1986, 1990, 1991, 1993 The Regents of University of California. All Rights Reserved. page A-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 309 B SNMP Trap Information This appendix lists the supported SNMP traps along with their descriptions. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-1...

  • Page 310: Snmp Traps Table

    (2) state if and only if there is a fault that prevents it from going to the up (1) state; it should remain in the notPresent (6) state if the interface has missing (typically, hardware) components. page B-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 311 The switch notifies the NMS ventDetail- when a significant event happens String that involves the policy manager. policyTrapE- ventCode policyTrapEventDetailString—Details about the event that took place. policyTrapEventCode—The code of the event. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-3...
  • Page 312 An instance of the appearance of the trap could be “failure on a module. Power supply 3”. chassisTrapsAlertNumber—This number that identifies the alert among all the possible chassis alert causes. chassisTrapsAlertDescr— The description of the alert matching ChassisTrapsAlertNumber. page B-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 313 CPU temperature threshold status indicating if threshold was crossed or no change. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-5...
  • Page 314 Discontinuities in the value of this counter can occur at re-ini- tialization of the management system and at other times as indicated by the value of ifCounterDiscontinuity- Time. esmDrvTrapDrops— Partitioned port (separated due to errors). page B-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 315 A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm (1) or risin- gOrFallingAlarm (3). OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-7...
  • Page 316 NI slot number. mirMonError—The Error returned by the NI which failed to configure Mirroring/Monitoring. page B-8 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 317 Name sessionUserI- pAddress sessionAuth- Failure sessionAccessType—The access type of the session. sessionUserName—The user name of the user logged-in. sessionUserIpAddress—The IP address of the user logged-in. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-9...
  • Page 318 Indicates that a new primary or mary secondary stack is elected. alaStackMgr- Secondary alaStackMgrPrimary—Holds the number of the stack, which is in Primary role. alaStackMgrSecondary—Holds the number of the stack, which is in Secondary role. page B-10 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 319 Denial of Service (DoS) attack. alaDoSType—Index field for the alaDoSTable. Integer indicating the DoS Type: 0=portscan, 1=tcpsyn, 2=pingofdeath, 3=smurf, 3=pepsi, 5=land and 6=teardropBonkBoink. alaDoSDetected—Number of attacks detected OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-11...
  • Page 320 PSE State diagram is in the state TEST_MODE. A value of denyLowPriority (8) indicates that the port was disabled by the power management system, in order to keep active higher priority ports. page B-12 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 321 - 1001..1008: switches operating in pass through mode - 255: unassigned slot number. alaStackMgrChasRole—The current role of the chassis as follows: - unassigned(0), - primary(1), - secondary(2), - idle(3), - standalone(4), - passthrough(5). OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-13...
  • Page 322 VLAN rule table. gmOverloadRuleVlanId—The overloaded VLAN ID. gmOverloadRuleMacAddress—The overloaded MAC address. gmOverloadRuleIpAddress—The overloaded IP address. gmOverloadRuleProtocol—The overloaded protocol type. page B-14 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 323 The number of packet drops (within a configured time interval) of the pktDropType that trig- gered this particular trap instance. — pktDropFrag Less than or equal to 512 bytes of the dropped packet (dsmac[12], tag[4], etype[2], pay- load[..512] (0 if DropCount only). OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-15...
  • Page 324 LPS port on which the violation occured systemServicesDate—The current System Date in the following format: MM/DD/YYYY. systemServicesTime—The current System Time in the following format: HH:MM:SS. bridge dot1agCfmFaultAlarm gmSubnetRuleTable—Overloaded HW subnet rule table. gmOverloadRuleSlice—Overloaded slot Id. unused page B-16 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 325 PIM NeighborLoss Count is incremented, subject to the rate limit specified by the PIM Neighbor Loss Notification- Period. alaPimNeighborUpTime—The time since this PIM neighbor (last) became a neighbor of the local router. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-17...
  • Page 326 IP multicast group address carried in the last unexpected Join/Prune message received alaPimInvalidJoinPruneRp—The RP address carried in the last unexpected Join/Prune message received alaPimNeighborUpTime—The time since this PIM neighbor (last) became a neighbor of the local router. page B-18 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 327 UDLD state of the port - notapplicable (0), shutdown (1), undetermined (2), bidirectional (3). alaUdldCurrentState—he current UDLD state of the port - notapplicable (0), shutdown (1), undetermined (2), bidirectional (3). OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-19...
  • Page 328 112 ripngRouteMaxLimitReached none ripng This trap is sent when the RIPng database reaches the supported maximum number of entries. When the maximum number is reached, RIPng discards any new updates. Reserved page B-20 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 329 OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-21...
  • Page 330 LogOui dot3OamEvent LogType dot3OamEvent LogLocation dot3OamEvent LogWin- dowHi dot3OamEvent LogWin- dowLo dot3OamEvent LogThreshol- dot3OamEvent LogThresh- oldLo dot3OamEvent LogValue dot3OamEvent LogRunning- Total dot3OamEvent LogEvent- Total page B-22 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 331 (local(1)), or was received from the OAM peer via Ethernet OAM (remote(2)). dot3OamEventLogEventTotal—The total number of times this event has resulted in a notification. Reserved OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-23...
  • Page 332 DDM parameters (clearViolation(1), highAlarm(2), high- Warning(3), lowWarning(4), lowAlarm(5). ddmRxOpticalPower—The current Received Optical Power of the SFP/XFP in 10s of milli-Watts (mW). Reserved page B-24 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 333 163 alaTestOamTxDoneTrap alaTestOam- bridge After a configured time interval, ConfigTestId, this trap is sent to the NMS from alaTestOam- Generator switch when the test Config- duration expires. SourceEndpoi alaTestOam- ConfigTestId- Status OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-25...
  • Page 334 SAA test iteration: 1 - Undetermined, 2 - Success, 3 - Failed, 4 - Aborted. alaSaaCtrlLastRunTime—The date and time at which the last iteration of the SAA was run. page B-26 OmniSwitch 6250/6450 Switch Management Guide May 2012...

  • Page 335: Index

    HIC/Rem/WebDL server's IP address. aaaHSvrCurrIpAddress—The current active HIC server's IP address. 172 aaaHicServerUpTrap aaaHSvrIpAd- This trap is sent when at least one dress, of the HIC servers comes UP. aaaHSvrRole, aaaHSvrName OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-27...
  • Page 336 Vlan Movement from one port to another port. 177 esmPortViolation ifIndex, interface This trap is sent when an inter- esmPortViola- face is shut down by a feature tionValue due to violation. page B-28 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 337 182 alaTestOamTestAbortTrap alaTestOam- bridge This trap is sent to the NMS from ConfigTestId the switch, if the test is aborted during takeover. alaTestOamConfigTestId—A unique name to identify the entries in the table. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-29...
  • Page 338 Number, mode because element license alaStackMgrPri- information is not same as pri- maryLicense mary element license informa- tion. alaStackMgrSlotNINumber—The number assigned for NI Stack. alaStackMgrPrimaryLicense—The stack element license type. 191 Reserved page B-30 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 339 NMS to inform user about an application license expiration. aluLicensedApplication—String displaying the application for which this license is valid. aluLicenseTimeRemaining—Number of days remaining to evaluate this demo license. OmniSwitch 6250/6450 Switch Management Guide May 2012 page B-31...
  • Page 340 SNMP Traps Table SNMP Trap Information page B-32 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 341 3-10 Troubleshooting 8-23 configuration apply command 7-2, 7-4 Automatic Remote Configuration network components for a specific timeperiod 7-5 TFTP File Server configuration cancel command 7-7 configuration error-file limit command 7-8 OmniSwitch 6250/6450 Switch Management Guide May 2012 Index-1...
  • Page 342 DES 3-11 logging into the switch end-user profile command 9-7, 9-21 application examples end-user profile port-list command 9-21 login end-user profile vlan-range command 9-21 defaults errors 7-7 specifications exit command 1-24, 2-19 Index-2 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 343 5-27 Synchronization Tests 4-10 Secure Shell 2-6, 2-12, 10-9 version number 4-11 algorithms 2-15 ntp server command 4-3, 4-10 DSA key 10-11 key exchange 2-15 managing the switch 10-11 Index-3 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 344 7-2 specifications 9-2 file management 1-2 switch management 10-5 login 2-3 user password-expiration command 9-13 NTP 4-2 user password-size min command 9-12 SNMP 3-2 users switch security 10-2 see user accounts Index-4 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 345 11-3 HTTP port 11-3 Secure Socket Layer 11-4 who command 2-18, 6-20 whoami command 6-21 wildcards 6-23 working directory 5-3 copying to certified directory 5-21, 5-26 write memory command 5-17 Zmodem 1-25 Index-5 OmniSwitch 6250/6450 Switch Management Guide May 2012...
  • Page 346 Index-6 OmniSwitch 6250/6450 Switch Management Guide May 2012...

This manual is also suitable for:

Omniswitch 6450

Table of Contents