Part No. 060306-10, Rev. C May 2012 OmniSwitch 6250/6450 Switch Management Guide www.alcatel-lucent.
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. Alcatel-Lucent® and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent.
Contents About This Guide .......................................................................................................... xi Supported Platforms .......................................................................................................... xi Who Should Read this Manual? ....................................................................................... xii When Should I Read this Manual? ...................................................................................
Contents Utility Commands ..................................................................................................1-18 Displaying Free Memory Space ......................................................................1-18 Performing a File System Check .....................................................................1-18 Deleting the Entire File System .......................................................................1-19 Loading Software onto the Switch ................................
Contents Using FTP .....................................................................................................................2-10 Using FTP to Log Into the Switch .........................................................................2-10 Using Secure Shell ........................................................................................................2-12 Secure Shell Components .......................................................................................
Contents Setting SNMP Security ...................................................................................3-12 Working with SNMP Traps ..........................................................................................3-13 Trap Filtering ..........................................................................................................3-13 Filtering by Trap Families ...............................................................................3-13 Filtering By Individual Trap .......
Contents Managing the Directory Structure (Non-Redundant) ...................................................5-13 Rebooting the Switch .............................................................................................5-13 Copying the Running Configuration to the Working Directory ............................5-16 Rebooting from the Working Directory .................................................................5-18 Copying the Working Directory to the Certified Directory ......................
Contents Enabling Command Logging ..........................................................................6-17 Disabling Command Logging .........................................................................6-17 Viewing the Current Command Logging Status .............................................6-18 Viewing Logged CLI Commands and Command Entry Results ....................6-18 Customizing the Screen Display ...................................................................................
Contents Automatic Remote Configuration Defaults ...................................................................8-3 Quick Steps for Automatic Remote Configuration .........................................................8-4 Overview .........................................................................................................................8-5 Basic Operation ........................................................................................................8-5 Network Components ......
Contents Quick Steps for Creating Customer Login User Accounts ......................................9-8 Default User Settings ...............................................................................................9-9 Account and Password Policy Settings ..................................................................9-10 How User Settings Are Saved ................................................................................9-11 Creating a User ................................................
Contents Quick Steps for Setting Up ASA ..................................................................................10-7 Setting Up Management Interfaces for ASA ................................................................10-9 Enabling Switch Access .......................................................................................10-10 Configuring the Default Setting ...........................................................................10-10 Using Secure Shell ..........................
Contents R. U-Boot ............................................................................................................. A-14 S. Solaris .............................................................................................................. A-14 T. Internet Protocol Version 6 .............................................................................. A-14 U. CURSES .......................................................................................................... A-15 V. ZModem ...
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.
Who Should Read this Manual? About This Guide Who Should Read this Manual? The audience for this user guide are network administrators and IT support personnel who need to configure, 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.
About This Guide What is Not in this Manual? What is Not in this Manual? The configuration procedures in this manual primarily use Command Line Interface (CLI) commands in examples. CLI commands are text-based commands used to manage the switch through serial (console port) connections or through Telnet sessions. This guide does include introductory chapters for alternative methods of managing the switch, such as web-based (WebView) and SNMP management.
Documentation Roadmap About This Guide Documentation Roadmap The OmniSwitch user documentation suite was designed to supply you with information at several critical junctures of the configuration process. The following section outlines a roadmap of the manuals that will help you at each stage of the configuration process. Under each stage, we point you to the manual or manuals that will be most helpful to you.
About This Guide Documentation Roadmap Anytime The CLI Reference Guide contains comprehensive information on all CLI commands supported by the switch. This guide includes syntax, default, usage, example, related CLI command, and CLI-to-MIB variable mapping information for all 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.
Related Documentation About This Guide 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. Also provides information on fundamental aspects of OmniSwitch software and stacking architecture.
About This Guide Related Documentation • 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.
User Manual CD About This Guide User Manual CD Some products are shipped with documentation included on a User Manual CD that accompanies the switch. This CD also includes documentation for other Alcatel-Lucent data enterprise products. All products are shipped with a Product Documentation Card that provides details for downloading documentation for all OmniSwitch and other Alcatel-Lucent data enterprise products.
1 Managing System Files This chapter describes the several methods of transferring software files onto the OmniSwitch and how to register those files for use by the switch. This chapter also describes several basic switch management procedures and discusses the Command Line Interface (CLI) commands used.
File Management Specifications Managing System Files File Management Specifications The functionality described in this chapter is supported unless otherwise stated in the following Specifications table or specifically noted within any section of this chapter. File Transfer Methods FTP, TFTP, Zmodem. Switch Software Utility OmniSwitch as an FTP Client, FTP server or TFTP Client.
Managing System Files Switch Administration Overview Switch Administration Overview The OmniSwitch has a variety of software features designed for different networking environments and applications. 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.
Switch Administration Overview Managing System Files Switch Directories You can create your own directories in the switch flash directory. This allows you to organize your configuration and text files on the switch. You can also use the vi command to create files. This chapter tells you how to make, copy, move, and delete both files and directories. Listing Directory: /flash Directory: /flash/certified Directory: /flash/network (Files) (Files) Directory: /flash/working (Files) (Files) boot.
Managing System Files File and Directory Management File and Directory Management A number of CLI commands allow you to manage files on your switch by grouping them into subdirectories within the switch flash directory. These commands perform the same functions as file management software applications (such as Microsoft Explorer) perform on a workstation. For documentation purposes, we have categorized the commands into the following three groups.
File and Directory Management Managing System Files To list all the files and directories in your current directory, use the ls command. Here is a sample display of the flash directory. -> ls Listing Directory /flash: -rw drw drw -rw drw -rw -rw -rw drw 315 2048 2048 12 2048 64000 64000 256 2048 Jan Jan Jan Dec Dec Jan Dec Dec Dec 5 5 5 18 27 5 27 27 18 09:38 09:22 09:22 2030 2030 09:37 2030 2030 2030 boot.params certified/ working/ boot.slot.cfg switch/ swlog1.log swlog2.
Managing System Files File and Directory Management Using Wildcards Wildcards allow you to substitute symbols (* or ?) for text patterns while using file and directory commands. The asterisk (*) takes the place of multiple characters and the question mark character (?) takes the place of single characters. More than one wildcard can be used within a single text string. Multiple Characters An asterisk (*) is used as a wildcard for multiple characters in a text pattern.
File and Directory Management Managing System Files Directory Commands The directory commands are applied to the switch file system and to files contained within the file system. When you first enter the flash directory, your login is located at the top of the directory tree. You may navigate within this directory by using the pwd and cd commands (discussed below). The location of your login within the directory structure is called your current directory.
Managing System Files File and Directory Management Changing Directories Use the cd command to navigate within the file directory structure. The cd command allows you to move “up” or “down” the directory tree. To go down, you must specify a directory located in your current directory. The following command example presumes your current directory is the /flash file directory as shown in the directory on page 1-8 and that you want to move down the directory tree to the certified directory.
File and Directory Management Managing System Files Displaying Directory Contents The ls and dir commands have the same function. These two commands display the contents of the current directory.
Managing System Files File and Directory Management If you specify a path as part of the ls or dir command, your screen will list the contents of the directory at the specified path. -> ls /flash/ Listing Directory /flash: drw -rw -rw -rw -rw drw drw drw -rw -rw -rw -rw -rw -rw 1024 276 4890749 256 64000 1024 1024 1024 222 524288 834497 64000 719 199567 Nov 8 08:30 WORKING/ Nov 8 09:59 boot.params Oct 21 21:43 cs_system.pmd Nov 8 09:57 random-seed Nov 8 09:59 swlog1.
File and Directory Management Managing System Files Displaying Directory Contents Including Subdirectories The ls -r command displays the contents of your current directory in addition to recursively displaying all subdirectories. The following example shows the result of the ls -r command where the /flash/working directory contains a directory named newdir1. Be sure to include a space between ls and -r.
Managing System Files File and Directory Management To verify the creation of the new directory, use the ls -r command to produce a list of the contents of the certified directory. This list will include the files that were originally in the certified directory plus the newly created copy of the working directory and all its contents.
File and Directory Management Managing System Files File Commands The file commands apply to files located in the /flash file directory and its sub-directories. Note. Each file in any directory must have a unique name. If you attempt to create or copy a file into a directory where a file of the same name already exists, you will overwrite or destroy one of the files. Creating or Modifying Files The switch has an editor for creating or modifying files.
Managing System Files File and Directory Management Secure Copy an Existing File Use the scp command to copy an existing file in a secure manner. You can specify the path and filename for the original file being copied as well as the path and filename for a new copy being created. If no path is specified, the command assumes the current directory. If SCP is not enabled on the switch, use the scp-sftp command to enable it.
File and Directory Management Managing System Files In this first example, the user current directory is the flash directory. The following command syntax moves the testfile2 file from the user created testfiles directory into the working directory as shown in the illustration above. The screen displays a warning that the file is being renamed (or in this case, redirected).
Managing System Files File and Directory Management Managing Files on Switches On OmniSwitch stackable switches, you can copy a file from a non-primary switch to the primary switch in a stack using the rcp command. To use this command, enter rcp followed by the slot number of the non-primary switch, the path and file name of the source file on the non-primary switch, and the destination file name on the primary switch. For example, to copy the boot.
File and Directory Management Managing System Files Utility Commands The utility commands include freespace, fsck, and newfs. These commands are used to check memory and delete groups of files. Displaying Free Memory Space The freespace command displays the amount of free memory space available for use in the switch file system. You may issue this command from any location in the switch directory tree.
Managing System Files File and Directory Management Deleting the Entire File System The newfs command deletes the flash file system and all the files and directories contained in it. This command is used when you want to reload all files in the 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.
Loading Software onto the Switch Managing System Files Loading Software onto the Switch There are three common methods for loading software to and from your switch. The method you use depends on your workstation software, your hardware configuration, and the location and condition of your switch. These methods are discussed here. • FTP Server—You can use the switch as an FTP server. If you have FTP client software on your work- station, you can transfer a file to the switch via FTP.
Managing System Files Loading Software onto the Switch Note. If you are using Authenticated Switch Access (ASA), the port interface must be authenticated for FTP use and the username profile must have permission to use FTP. Otherwise the switch will not accept an FTP login. For information about ASA, refer to Chapter 10, “Managing Switch Security.” 2 Specify the transfer mode. If you are transferring a switch image file, you must specify the binary transfer mode on your FTP client.
Loading Software onto the Switch Managing System Files 1 Establish a connection to the switch as explained in your appropriate Getting Started Guide. 2 Log on to the switch and enter the ftp command to start the FTP client. Next, enter a valid host name or IP address. (For information about enabling the DNS resolver for host names, please refer to Chapter 2, “Logging Into the Switch.”) A screen similar to the following is displayed: -> ftp 198.23.9.101 Connecting to [198.23.9.101]...
Managing System Files Loading Software onto the Switch delete Delete a file on the remote machine. dir Obtain a long listing on the remote machine. get Retrieve a file from the remote machine. hash Print the hash symbol (#) for every block of data transferred. (This command toggles hash enabling and disabling.) help Displays a list of FTP commands and their definitions. ls Display summary listing of the current directory on the remote host. put Send a file to the remote machine.
Loading Software onto the Switch Managing System Files -> 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. 2 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.
Managing System Files Loading Software onto the Switch Using TFTP to Transfer Files Trivial File Transfer Protocol (TFTP), a client-server protocol, can be used to transfer files between the TFTP server and client. TFTP client functionality on the OmniSwitch is used to download files from or upload files to the TFTP server within a LAN using the tftp command. The following is an example of how to start a TFTP session to download a file from a TFTP server: -> tftp 10.211.17.1 get source-file boot.
Loading Software onto the Switch Managing System Files Note. If a file you are transferring already exists in the switch flash memory, you must remove the file before transferring the new file via Zmodem. Workstation Zmodem OmniSwitch Zmodem is used to transfer a file from a workstation to the OmniSwitch Zmodem File Transfer To transfer a file via Zmodem, complete the following steps: 1 Connect your terminal emulation device containing the Zmodem protocol to the switch console port.
Managing System Files Registering Software Image Files Registering Software Image Files New software transferred to the switch must go through a registration process before it can be used by the switch. The registration process includes two tasks: • Transfer the new software file(s) to the switch /flash/working directory via remote connection. • Restart the switch to register the software. Directories on the Switch When you log into the switch, your current directory is the flash directory.
Registering Software Image Files Managing System Files Available Image Files The following table lists the image files for the OmniSwitch 6450 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. Archive File Name Base or Optional Software Description KFbase.img Base Software CMM Base KFeni.img Base Software NI image for all Ethernet-type NIs KFos.
Managing System Files Application Examples for File Management Application Examples for File Management The following sections provide detailed examples of managing files and directories on the switch. 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.
Application Examples for File Management Managing System Files Creating a File Directory on the Switch In this example, the user wants to store several test files on the switch for use at a later date. The user has loaded the files into the switch /flash/working directory by using FTP. Rather than leaving the files in the working directory, the user may want to create a new directory.
Managing System Files Application Examples for File Management 5 Use the ls command to verify that the files are now located in the /flash/resources directory. -> ls /flash/resources Listing Directory /flash/resources: drw drw -rw -rw -rw 2048 2048 6 6 6 Jul Jul Jul Jul Jul 5 5 5 5 5 17:20 16:25 17:03 17:03 17:03 ./ ../ test1.txt test2.txt test3.txt 17995776 bytes free FTP Client Application Example The following example shows how to transfer a file named rrtext.
Application Examples for File Management Managing System Files 3 Enter the FTP mode by using the ftp command followed by the IP address or the name of the host you are connecting to. (If you enter a host name, please refer to “Using Zmodem” on page 1-25.) ->ftp 10.255.11.101 220 Connecting to [10.255.11.101]...connected. Cosmo Windows FTP server ready Name: Myhost1 Note. You can only use a host name instead of an IP address if the DNS resolver has been configured and enabled.
Managing System Files Application Examples for File Management Creating a File Directory Using Secure Shell FTP The following example describes the steps necessary to create a directory on a remote OmniSwitch and to transfer a file into the new directory by using Secure Shell FTP. 1 Log on to the switch and issue the sftp CLI command with the IP address for the device you are connecting to.
Application Examples for File Management 287 2048 2048 64000 64000 2048 206093 2048 2048 256 Managing System Files boot.params certified working swlog1.log swlog2.log30 policy.cfg network cs_system.pmd LPS newssdir random-seed Transfer a File Using Secure Shell FTP To demonstrate how to transfer a file by using the Secure Shell FTP, this application example continues from the previous example where a new directory named “newssdir” was created on a remote OmniSwitch.
Managing System Files Verifying Directory Contents Verifying Directory Contents To display a list of files, the following CLI commands may be used. ls Displays the contents of a specified directory or the current working directory. dir Displays the contents of a specified directory or the current working directory. rls 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.
Installing Software Licenses Managing System Files 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. To install the license file on the switch and to activate the licensed features, perform the following steps: 1 Log on to https://service.esd.
Managing System Files Installing Software Licenses Licensed Features License Features Installation Notes Metro Ethernet-service OAM (802.1ag, Y-1731, 802.3ah) CPE test head G.8032 IPMC VLAN Dying Gasp SAA MVR Mac Forced Forwarding PPPoE Switch/Stack must rebooted after installing licenses. Allows SMB models to run Metro features. Metro licenses are installed on the units in a stack only if the keys for all the units are available; all units must have a metro license.
Installing Software Licenses Managing System Files License Features Installation Notes 10GIG Enables 10-Gigabit non-combo SFP+ ports. No reboot required. Non-combo SFP+ ports will be upgraded to provide 10G capacity. Individual units can be upgraded. Temporary Unlocks any licensed feature for 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.
Managing System Files Setting the System Clock Setting the System Clock The switch clock displays time by using a 24-hour clock format. It can also be set for use in any time zone. Daylight Savings Time (DST) is supported for a number of standard time zones. DST parameters can be programmed to support non-standard time zones and time off-set applications. All switch files and directories listed in the flash directory bear a time stamp. This feature is useful for file management purposes.
Setting the System Clock Managing System Files You may set the switch system clock to a time that is offset from standard UTC time. For example, you can set a time that is offset from UTC by increments of 15, 30, or 45 minutes. You must indicate by a plus (+) or minus (-) character whether the time should be added to or subtracted from the system time.
Managing System Files Setting the System Clock Daylight Savings Time Configuration The switch can be set to change the system clock automatically to adjust for Daylight Savings Time (DST). There are two situations that apply depending on the time zone selected for your switch.
Setting the System Clock Managing System Files Enabling DST When Daylight Savings Time (DST) is enabled, the switch clock will automatically set the default DST parameters for the time zone specified on the switch or for the custom parameters you can specify with the system daylight savings time command. In this case, it is not necessary to change the time setting on the switch when your time zone changes to and from DST.
Managing System Files Setting the System Clock Time Zone and DST Information Table (continued) Abbreviation Name Hours from UTC cet Central Europe met DST Start DST End DST Change +01:00 Last Sunday in Mar. at 2:00 a.m. Last Sunday in Oct. at 3:00 a.m. 1:00 Middle Europe +01:00 Last Sunday in Mar. at 2:00 a.m. Last Sunday in Oct. at 3:00 a.m. 1:00 bst British Standard Time +00:00 Last Sunday in Mar. at 1:00 a.m. Last Sunday in Oct. at 3:00 a.m.
Setting the System Clock page 1-44 Managing System Files OmniSwitch 6250/6450 Switch Management Guide May 2012
2 Logging Into the Switch Logging into the switch may be done locally or remotely. Management tools include: the Command Line Interface (CLI), which may be accessed locally through the console port, or remotely through Telnet; WebView, which requires an HTTP client (browser) on a remote workstation; and SNMP, which requires an SNMP manager (such as Alcatel-Lucent OmniVista or HP OpenView) on the remote workstation.
In This Chapter Logging Into the Switch Management access is disabled (except through the console port) unless specifically enabled by a network administrator. For more information about management access and methods, use the table here as a guide: For more information about... See...
Logging Into the Switch Login Specifications Login Specifications Platforms Supported OmniSwitch 6250, 6450 Telnet clients supported Any standard Telnet client FTP clients supported Any standard FTP client HTTP (WebView) clients supported – Internet Explorer for Windows NT, Windows XP, and Windows 2000, version 6.0 – Netscape for Windows NT, Windows XP, and Windows 2000, version 7.1 – Netscape for Sun OS 2.8, version 4.79 – Netscape for HP-UX 11.0, version 4.
Login Defaults Logging Into the Switch The following table describes the maximum number of sessions allowed on an OmniSwitch: Session OmniSwitch 6250/ OmniSwitch 6450 Telnet (v4 or v6) 4 FTP (v4 or v6) 4 SSH + SFTP (v4 or v6 secure sessions) 8 HTTP 4 Total Sessions 20 SNMP 50 page 2-4 OmniSwitch 6250/6450 Switch Management Guide May 2012
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: • Connecting to the switch through the console port. • Setting up the Ethernet Management Port (EMP) through the switch’s boot prompt.
Overview of Switch Login Components Logging Into the Switch Overview of Switch Login Components Switch access components include access methods (or interfaces) and user accounts stored on the local user database in the switch and/or on external authentication servers. Each access method, except the console port, must be enabled or “unlocked” on the switch before users can access the switch through that interface.
Logging Into the Switch Overview of Switch Login Components Using the WebView Management Tool • HTTP—The switch has a Web browser management interface for users logging in through HTTP. This management tool is called WebView. For more information about using WebView, see Chapter 11, “Using WebView.” Using SNMP to Manage the Switch • SNMP—Any standard SNMP browser may be used for logging into the switch. See Chapter 3, “Using SNMP.
Using Telnet Logging Into the Switch Using Telnet Telnet may be used to log into the switch from a remote station. All of the standard Telnet commands are supported by software in the switch. When Telnet is used to log in, the switch acts as a Telnet server. If a Telnet session is initiated from the switch itself during a login session, then the switch acts as a Telnet client.
Logging Into the Switch Using Telnet Here, you must enter a valid username and password. Once login is complete, the OmniSwitch welcome banner is displayed as follows: login : admin password : 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.
Using FTP Logging Into the Switch Using FTP The OmniSwitch can function as an FTP server. Any standard FTP client may be used. Note. An FTP connection is not secure. Secure Shell is recommended instead of FTP or Telnet as a secure method of accessing the switch. Using FTP to Log Into the Switch You can access the OmniSwitch with a standard FTP application. To log in to the switch, start your FTP client. Where the FTP client asks for “Name”, enter the IP address of your switch.
Logging Into the Switch Using FTP You have to enter a valid user name and password for the host you specified with the ftp6 command, after which you will get a screen similar to the following display: Name:Jsmith 331 Password required for Jsmith Password: ***** 230 User Jsmith logged in. Note. It is mandatory to specify the name of the particular IPv6 interface, if the target has been specified using the link-local address.
Using Secure Shell Logging Into the Switch Using Secure Shell The OmniSwitch Secure Shell feature provides a secure mechanism that allows you to log in to a remote switch, to execute commands on a remote device, and to move files from one device to another. Secure Shell provides secure, encrypted communications even when your transmission is between two untrusted hosts or over an unsecure network.
Logging Into the Switch Using Secure Shell Secure Shell Interface The Secure Shell interface is invoked when you enter the ssh command, and the Secure Shellv6 interface is invoked by using the ssh6 command in an IPv6 environment. After the authentication process between the client and the server is complete, the remote Secure Shell interface runs in the same way as Telnet. Refer to “Starting a Secure Shell Session” on page 2-17 to for detailed information.
Using Secure Shell Logging Into the Switch Secure Shell Application Overview Secure Shell is an access protocol used to establish secured access to your OmniSwitch. The Secure Shell protocol can be used to manage an OmniSwitch directly or it can provide a secure mechanism for managing network servers through the OmniSwitch. The drawing below illustrates the Secure Shell being used as an access protocol replacing Telnet to manage the OmniSwitch.
Logging Into the Switch Using Secure Shell Secure Shell Authentication Secure Shell authentication is accomplished in several phases using industry standard algorithms and exchange mechanisms. The authentication phase is identical for Secure Shell and Secure Shell FTP. The following sections describe the process in detail.
Using Secure Shell Logging Into the Switch Connection Phase After successful authentication, both the client and the server process the Secure Shell connection protocol. The OmniSwitch supports one channel for each Secure Shell connection. This channel can be used for a Secure Shell session or a Secure Shell FTP session.
Logging Into the Switch Using Secure Shell Starting a Secure Shell Session To start a Secure Shell session, issue the ssh command and identify the IP address or hostname for the device you are connecting to. You can use the ssh6 command to start an SSHv6 session followed by the relevant IPv6 address or the hostname, over an IPv6 environment. Note. You can only use a host name instead of an IP address if the DNS resolver has been configured and enabled. If not, you must specify an IP address.
Using Secure Shell Logging Into the Switch The following drawing shows an OmniSwitch, using IP address 11.233.10.145, establishing a Secure Shell session across a network to another OmniSwitch, using IP address 11.133.30.135. To establish this session from the console in the figure below, you would use the CLI commands shown in the examples above. Once you issue the correct password, you are logged into the OmniSwitch at IP address 11.133.30.135. Console OmniSwitch 11.233.10.145 OmniSwitch 11.133.30.
Logging Into the Switch Using Secure Shell Closing a Secure Shell Session To terminate the Secure Shell session, issue the exit command. The following is displayed: -> exit Connection to 11.133.30.135 closed. Using the example shown above, this display indicates the Secure Shell session between the two switches is closed. At this point, the user is logged into the local OmniSwitch at IP address 11.233.10.145. Note.
Using Secure Shell Logging Into the Switch sftp>? Available commands: cd path lcd path chmod mode path help get remote-path [local-path] lls [path]] ln oldpath newpath lmkdir path lpwd ls [path] mkdir path put local-path [remote-path] pwd exit quit rename oldpath newpath rmdir path rm path symlink oldpath newpath version ? Change remote directory to 'path' Change local directory to 'path' Change permissions of file 'path' to 'mode' Display this help text Download file Display local directory listing Syml
Logging Into the Switch Modifying the Login Banner Modifying the Login Banner The Login Banner feature allows you to change the banner that displays whenever someone logs into the switch. This feature can be used to display messages about user authorization and security. You can display the same banner for all login sessions or you can implement different banners for different login sessions.
Modifying the Login Banner Logging Into the Switch If you want the login banner in the text file to apply to HTTP switch sessions, execute the following CLI command where the text filename is thirdbanner.txt. -> session banner http /flash/thirdbanner.txt The banner files must contain only ASCII characters and should bear the .txt extension. The switch does not reproduce graphics or formatting contained in the file.
Logging Into the Switch Configuring Login Parameters Configuring Login Parameters You can set the number of times a user may attempt unsuccessfully to log in to the switch’s CLI by using the session login-attempt command as follows: -> session login-attempt 5 In this example, the user may attempt to log in to the CLI five (5) times unsuccessfully. If the user attempts to log in the sixth time, the switch will break the TCP connection.
Enabling the DNS Resolver Logging Into the Switch Enabling the DNS Resolver A Domain Name System (DNS) resolver is an optional internet service that translates host names into IP addresses. Every time you enter a host name when logging into the switch, a DNS service must look up the name on a server and resolve the name to an IP address. You can configure up to three IPv4 domain name servers and three IPv6 domain name servers that is queried in turn to resolve the host name.
Logging Into the Switch Verifying Login Settings Verifying Login Settings To display information about login sessions, use the following CLI commands: who Displays all active login sessions (for example, console, Telnet, FTP, HTTP, Secure Shell, Secure Shell FTP). whoami Displays the current user session. show session config Displays session configuration information (for example, default prompt, banner file name, inactivity timer, login timer, login attempts).
Verifying Login Settings page 2-26 Logging Into the Switch OmniSwitch 6250/6450 Switch Management Guide May 2012
3 Using SNMP The Simple Network Management Protocol (SNMP) is an application-layer protocol that allows communication between 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).
SNMP Specifications Using SNMP SNMP Specifications The following table lists specifications for the SNMP protocol.
Using SNMP SNMP Defaults Parameter Description Command Default Value/Comments Enables the forwarding of traps to WebView. snmp trap to webview Enabled Enables or disables SNMP snmp authentication trap authentication failure trap forwarding.
Quick Steps for Setting Up An SNMP Management Station Using SNMP Quick Steps for Setting Up An SNMP Management Station An SNMP Network Management Station (NMS) is a workstation configured to receive SNMP traps from the switch. To set up an SNMP NMS by using the switch’s CLI, proceed as follows: 1 Specify the user account name and the authentication type for that user.
Using SNMP Quick Steps for Setting Up Trap Filters Quick Steps for Setting Up Trap Filters You can filter traps by limiting user access to trap command families. You can also filter according to individual traps. Filtering by Trap Families The following example creates a new user account. This account is granted read-only privileges to three CLI command families (snmp, chassis, and interface). Read-only privileges is withheld from all other command families.
Quick Steps for Setting Up Trap Filters Using SNMP Filtering by Individual Traps The following example enables trap filtering for the coldstart, warmstart, linkup, and linkdown traps. The identification numbers for these traps are 0, 1, 2, and 3. When trap filtering is enabled, these traps are filtered. This means that the switch does not pass them through to the SNMP management station. All other traps are passed through.
Using SNMP SNMP Overview SNMP Overview SNMP provides an industry standard communications model used by network administrators to manage and monitor their network devices. The SNMP model defines two components, the SNMP Manager and the SNMP Agent. Network Management Station OmniSwitch OmniSwitch 6648 SNMP Agent SNMP Manager SNMP Network Model • The SNMP Manager resides on a workstation hosting the management application. It can query agents by using SNMP operations.
SNMP Overview Using SNMP Using SNMP for Switch Management The Alcatel-Lucent switch can be configured using the Command Line Interface (CLI), SNMP, or the WebView device management tool. When configuring the switch by using SNMP, an NMS application (such as Alcatel-Lucent’s OmniVista or HP OpenView) is used. Although MIB browsers vary depending on which software package is used, they all have a few things in common.
Using SNMP SNMP Overview The community string security standard offers minimal security and is generally insufficient for networks where the need for security is high. Although SNMPv1 lacks bulk message retrieval capabilities and security features, it is widely used and is a de facto standard in the Internet environment. SNMPv2 SNMPv2 is a later version of the SNMP protocol. It uses the same Get, Set, GetNext, and Trap operations as SNMPv1 and supports the same community-based security standard.
Using SNMP For Switch Security Using SNMP Using SNMP For Switch Security Community Strings (SNMPv1 and SNMPv2) The switch supports the SNMPv1 and SNMPv2c community strings security standard. When a community string is carried over an incoming SNMP request, the community string must match up with a user account name as listed in the community string database on the switch. Otherwise, the SNMP request is not processed by the SNMP agent in the switch.
Using SNMP Using SNMP For Switch Security Encryption and Authentication (SNMPv3) Two important processes are used to verify that the message contents have not been altered and that the source of the message is authentic. These processes are encryption and authentication. A typical data encryption process requires an encryption algorithm on both ends of the transmission and a secret key (like a code or a password).
Using SNMP For Switch Security Using SNMP Setting SNMP Security By default, the switch is set to “privacy all”, which means the switch accepts only authenticated and encrypted v3 Sets, Gets, and Get-Nexts. You can configure different levels of SNMP security by entering snmp security followed by the command parameter for the desired security level.
Using SNMP Working with SNMP Traps Working with SNMP Traps The SNMP agent in the switch has the ability to send traps to the management station. It is not required that the management station request them. Traps are messages alerting the SNMP manager to a condition on the network. A trap message is sent via a PDU issued from the switch’s network management agent. It is sent to alert the management station to some event or condition on the switch.
Working with SNMP Traps Using SNMP Authentication Trap The authentication trap is sent when an SNMP authentication failure is detected. This trap is a signal to the management station that the switch received a message from an unauthorized protocol entity. This normally means that a network entity attempted an operation on the switch for which it had insufficient authorization. When the SNMP authentication trap is enabled, the switch forwards a trap to the management station.
Using SNMP SNMP MIB Information SNMP MIB Information MIB Tables You can display MIB tables and their corresponding command families by using the show snmp mib family command. The MIB table identifies the MIP identification number, the MIB table name and the command family. If a command family is not valid for the entire MIB table, the command family is displayed on a per-object basis.
SNMP MIB Information Using SNMP Industry Standard MIBs The following table lists the supported industry standard MIBs. MIB Name Description Dependencies BRIDGE-MIB, RFC 1493 The Bridge MIB for managing MAC bridges based on SNMPv2-SMI, the IEEE 802.1D standard between Local Area NetRFC1215-MIB work (LAN) segments. EE8023-LAG-MIB, IEEE 802.3ad Link Aggregation module for managing IEEE Standard 802.3ad.
Using SNMP SNMP MIB Information MIB Name Description Dependencies IGMP-STD-MIB, RFC 2933 Internet Group Management Protocol MIB. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF, IF-MIB INET-ADDRESS-MIB, RFC 2851 Textual Conventions for Internet Network Addresses. SNMPv2-SMI, SNMPv2-TC IP-BRIDGE-MIB, RFC 2674 The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D.
SNMP MIB Information Using SNMP MIB Name Description Dependencies RIPv2-MIB, RFC 1724 Routing Information Protocol (RIP) Version 2 MIB Extension. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF RMON-MIB, RFC 2819 Remote Network Monitoring (RMON) Management Information Base. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF RS-232-MIB, RFC 1659 Definitions of Managed Objects for RS-232-like Hardware Devices by using SMIv2.
Using SNMP SNMP MIB Information MIB Name Description SNMP-USER-BASEDSM-MIB, RFC 2574 User-based Security Model (USM) for version 3 of the SNMPv2-SMI, Simple Network Management Protocol (SNMPv3). SNMPv2-TC, SNMPv2-CONF, SNMPFRAMEWORKMIB SNMPv2-MIB, RFC 1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2).
SNMP MIB Information Using SNMP Enterprise (Proprietary) MIBs The following table lists the supported enterprise proprietary MIBs. Note. The ALCATEL-IND1-BASE* MIB is required for all MIBs listed in this table. MIB Name Description Dependencies* ALCATEL-IND1AAA-MIB Definitions of managed objects for the Authentication, SNMPv2-SMI, Authorization, and Accounting (AAA) subsystem.
Using SNMP SNMP MIB Information MIB Name Description Dependencies* ALCATEL-IND1INTERSWITCHPROTOCOL-MIB Definitions of managed objects for the Interswitch Protocol (that is, GMAP, XMAP) subsystem. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF IF-MIB ALCATEL-IND1IP-MIB Definitions of managed objects for the IP Stack subsystem.
SNMP MIB Information Using SNMP MIB Name Description ALCATEL-IND1MAC-SERVER-MIB Definitions of managed objects for the Chassis Super- SNMPv2-SMI, vision MAC Server subsystem. SNMPv2-TC, SNMPv2-CONF, ENTITY-MIB, ALCATEL-IND1CHASSIS-MIB ALCATEL-IND1MLD-MIB Definitions of the Multicast Listener Discovery (MLD) subsystem. ALCATEL-IND1NTP-MIB Definitions of the Network Time Protocol (NTP) sub- SNMPv2-SMI, system.
Using SNMP SNMP MIB Information MIB Name Description Dependencies* ALCATEL-IND1RIP-MIB Definitions of managed objects for the Routing Information Protocol (RIP) subsystem. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF ALCATEL-IND1RIPNG-MIB Definitions of managed objects for the Routing Information Protocol (RIPng) subsystem. SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF IPv6-TC ALCATEL-IND1SESSION-MGR-MIB Definitions of managed objects for the User Session Manager subsystem.
Verifying the SNMP Configuration Using SNMP Verifying the SNMP Configuration To display information about SNMP management stations, trap management, community strings, and security, use the show commands listed in the following table. show snmp station Displays current SNMP station information including IP address, UDP Port number, Enabled/Disabled status, SNMP version, and user account names.
4 Configuring Network Time Protocol (NTP) Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver. It provides client time accuracies within a millisecond on LANs, and up to a few tens of milliseconds on WANs relative to a primary server synchronized to Universal Coordinated Time (UTC) (via a Global Positioning Service receiver, for example).
NTP Specifications Configuring Network Time Protocol (NTP) NTP Specifications RFCs supported 1305–Network Time Protocol Platforms Supported OmniSwitch 6250, 6450 Maximum number of NTP servers per client 3 NTP Defaults Table The following table shows the default settings of the configurable NTP parameters: NTP Defaults Parameter Description Command Default Value/Comments Specifies an NTP server from which ntp server this switch receives updates version: 4 minpoll: 6 prefer: no key: 0 Used to acti
Configuring Network Time Protocol (NTP) NTP Quick Steps NTP Quick Steps The following steps are designed to show the user the necessary commands to set up NTP on an OmniSwitch: 1 Designate an NTP server for the switch using the ntp server command. The NTP server provides the switch with its NTP time information. For example: -> ntp server 1.2.5.6 2 Activate the client side of NTP on the switch using the ntp client command.
NTP Quick Steps Configuring Network Time Protocol (NTP) 5 You can check the client configuration using the show ntp client command, as shown: -> show ntp client Current time: Last NTP update: Client mode: Broadcast client mode: Broadcast delay (microseconds): page 4-4 THU SEP 15 2005 17:44:54 (UTC) THU SEP 15 2005 17:30:54 enabled disabled 4000 OmniSwitch 6250/6450 Switch Management Guide May 2012
Configuring Network Time Protocol (NTP) NTP Overview NTP Overview Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver. It provides client time accuracies within a millisecond on LANs, and up to a few tens of milliseconds on WANs relative to a primary server synchronized to Universal Coordinated Time (UTC) (via a Global Positioning Service receiver, for example).
NTP Overview Configuring Network Time Protocol (NTP) Stratum Stratum is the term used to define the relative proximity of a node in a network to a time source (such as a radio clock). Stratum 1 is the server connected to the time source itself. (In most cases the time source and the stratum 1 server are in the same physical location.) An NTP client or server connected to a stratum 1 source would be stratum 2.
Configuring Network Time Protocol (NTP) NTP Overview Examples of these are shown in the simple network diagram below: UTC Time Source Stratum 1 NTP Servers 1a 1b Stratum 2 NTP Server/Clients 2a 2b Stratum 3 NTP Clients 3a 3b Servers 1a and 1b receive time information from, or synchronize with, a UTC time source such as a radio clock. (In most cases, these servers would not be connected to the same UTC source, though it is shown this way for simplicity.
NTP Overview Configuring Network Time Protocol (NTP) When planning your network, it is helpful to use the following general rules: • It is usually not a good idea to synchronize a local time server with a peer (in other words, a server at the same stratum), unless the latter is receiving time updates from a source that has a lower stratum than from where the former is receiving time updates. This minimizes common points of failure.
Configuring Network Time Protocol (NTP) Configuring NTP Configuring NTP The following sections detail the various commands used to configure and view the NTP client software in an OmniSwitch. Configuring the OmniSwitch as a Client The NTP software is disabled on the switch by default.
Configuring NTP Configuring Network Time Protocol (NTP) NTP Servers An NTP client needs to receive NTP updates from an NTP server. Each client must have at least one server with which it synchronizes (unless it is operating in broadcast mode). There are also adjustable server options. Designating an NTP Server To configure an NTP client to receive updates from an NTP server, enter the ntp server command with the server IP address or domain name, as shown: -> ntp server 1.1.1.
Configuring Network Time Protocol (NTP) Configuring NTP Setting the Version Number There are currently four versions of NTP available (numbered one through four). The version that the NTP server uses must be specified on the client side. To specify the NTP version on the server from which the switch receives updates, use the ntp server command with the server IP address (or domain name), version keyword, and version number, as shown: -> ntp server 1.1.1.1 version 3 The default setting is version 4.
Configuring NTP Configuring Network Time Protocol (NTP) Using Authentication Authentication is used to encrypt the NTP messages sent between the client and server. The NTP server and the NTP client must both have a text file containing the public and secret keys. (This file should be obtained from the server administrator. For more information on the authentication file, see “Authentication” on page 4-8.
Configuring Network Time Protocol (NTP) Verifying NTP Configuration Verifying NTP Configuration To display information about the NTP client, use the show commands listed in the following table: show ntp client Displays information about the current client NTP configuration. show ntp server status Displays the basic server information for a specific NTP server or a list of NTP servers. show ntp client server-list Displays a list of the servers with which the NTP client synchronizes.
Verifying NTP Configuration page 4-14 Configuring Network Time Protocol (NTP) OmniSwitch 6250/6450 Switch Management Guide May 2012
5 Managing CMM Directory Content The CMM (Chassis Management Module) software runs the switches. The directory structure of the CMM software is designed to prevent corrupting or losing switch files. It also allows you to retrieve a previous version of the switch software. In addition to working as standalone switches, OmniSwitches can be linked together as a stack. A stack can provide CMM redundancy; one switch is designated as the primary CMM, and one is designated as the secondary CMM.
CMM Specifications Managing CMM Directory Content CMM Specifications Size of Flash Memory 128 Megabytes Size of RAM Memory 256 Megabytes Maximum Length of File Names 32 Characters Maximum Length of Directory Names 32 Characters Default Boot Directory Certified USB Flash Drive Specifications Platforms Supported OmniSwitch 6250, 6450 USB Flash Drive Support Alcatel-Lucent Certified USB Flash Drive Automatic Software Upgrade Supported Disaster Recovery Supported Note: The format of the Alca
Managing CMM Directory Content CMM Files 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. • A configuration file, named boot.
CMM Files Managing CMM Directory Content Where is the Switch Running From? When a switch has booted and is running, the software used comes either from the certified directory or the working directory. In most instances, the switch boots from the certified directory. (A switch can be booted from the working directory by using the reload working command described in “Rebooting from the Working Directory” on page 5-18.
Managing CMM Directory Content CMM Files Software Rollback Configuration Scenarios for a Single Switch The following examples illustrate a few likely scenarios and explain how the running configuration, working directory, and certified directory interoperate to facilitate the software rollback on a single switch. Note. This information applies to a switch stack; however, the manner in which CMM software is propagated to all switches in a stack is explained in “Redundancy Scenarios” on page 5-9.
CMM Files Managing CMM Directory Content Scenario 2: Running Configuration Saved to Working Directory The network administrator recreates the running configuration of Switch X and immediately saves the running configuration to the working directory. In another mishap, the power to the switch is again interrupted. The switch reboots from certified directory, overwrites all of the changes in the running configuration, and rolls back to the certified directory (which in this case is the factory settings).
Managing CMM Directory Content CMM Files Scenario 3: Saving the Working Directory to the Certified Directory After running the modified configuration settings and checking that there are no problems, the network administrator decides that the modified configuration settings (stored in the working directory) are reliable. The administrator then decides to save the contents of the working directory to the certified directory.
CMM Files Managing CMM Directory Content 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. Since the switch is booted from the working directory, the switch is running from the working directory.
Managing CMM Directory Content CMM Files Redundancy CMM software redundancy is one of the switch’s most important fail over features. For CMM software redundancy, at least two fully-operational switches must be linked together as a stack. In addition, the CMM software must be synchronized. (Refer to “Synchronizing the Primary and Secondary CMMs” on page 5-27 for more information.
CMM Files Managing CMM Directory Content This process occurs automatically when the switch boots. The working and certified directory relationship described in the preceding figure in “Software Rollback Feature” on page 5-4 continues to apply to the primary CMM switch. Generally speaking, the switch assigned the lowest stack number is the primary CMM switch; the switch with the next lowest stack number is the secondary CMM switch, and all other switches are idle.
Managing CMM Directory Content CMM Files Scenario 3: Synchronizing Switches in a Stack When changes have been made to the primary CMM switch certified directory, these changes have to be propagated to the other switches in the stack. This could be done by rebooting the stack. However, a loss of switch functionality is to be avoided, a copy flash-synchro command can be issued. The following diagram illustrates the process that occurs when using a copy flash-synchro command.
CMM Files Managing CMM Directory Content Scenario 4: Adding a New Switch to a Stack Since the OmniSwitch is designed to be expandable, it is likely that new switches are added to stacks. The stack automatically detects new switches added to the stack, and new switches can pass traffic without a complete reboot of the stack. However, a new switch added to the stack may not have the same software as the rest of the stack. In this case, the new switch must be synchronized with the stack software.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) Managing the Directory Structure (Non-Redundant) The following sections define commands that allow the user to manipulate the files in the directory structure of a single CMM. Note. All of the commands described in the following sections work on switches in a stack with redundancy enabled.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content To reboot the switch from the certified directory, enter the reload command at the prompt: -> reload This command loads the image and configuration files in the certified directory into the RAM memory. These files control the operation of the switch. Note. When the switch reboots using the reload command, it boots up from the certified directory.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) Checking the Status of a Scheduled Reboot You can check the status of a reboot set for a later time by entering the following command: -> show reload or -> show reload status The reload command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content Copying the Running Configuration to the Working Directory Once the switch has booted and is running, a user can modify various parameters of switch functionality. These changes are stored temporarily in the running configuration in the RAM of the switch.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) To save the running configuration to the working directory, enter the copy running-config working or write memory command at the prompt, as shown: -> copy running-config working or -> write memory The preceeding commands perform the same function. When these commands are issued the running configuration with all modifications made is saved to a file called boot.cfg in the working directory. Note.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content Rebooting from the Working Directory Besides a regular boot of the switch (from the certified directory), you can also force the switch to boot from the working directory. This is useful for checking whether a new configuration or image file boots up the switch correctly, before committing it to the certified directory.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) Note. If the switch is rebooted before using the copy certified working command, the switch runs from the certified directory as the working and certified directories are not the same. This behavior is described in “Where is the Switch Running From?” on page 5-4.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content Cancelling a Rollback Timeout To cancel a rollback time-out, enter the reload cancel command as shown: -> reload primary cancel or -> reload cancel The reload working command is described in detail in the OmniSwitch 6250/6450 CLI Reference Guide.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) Copying the Working Directory to the Certified Directory When the running configuration is saved to the working directory, the working and certified directories of the switch are now different. This difference, if the CMM reboots, causes the switch to boot and run from the certified directory.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content When the software on the working directory of a switch has proven to be effective and reliable, eventually the contents of the working directory should be copied into the certified directory.
Managing CMM Directory Content Managing the Directory Structure (Non-Redundant) Show Currently Used Configuration When a switch is booted, the certified and working directories are compared. If they are the same, the switch runs from the working directory. If they are different, the switch runs from the certified directory. A switch running from the certified directory cannot modify directory contents. (This topic is covered in “Where is the Switch Running From?” on page 5-4.
Managing the Directory Structure (Non-Redundant) Managing CMM Directory Content Show Switch Files The files currently installed on a switch can be viewed using the show microcode command. This command displays the files currently in the specified directory. To display files on a switch, enter the show microcode command with a directory, as shown: -> show microcode certified Package Release Size Description -----------------+---------------+--------+----------------------------------KFbase.img 6.6.3.311.
Managing CMM Directory Content Managing Redundancy in a Stack and CMM Managing Redundancy in a Stack and CMM The following section describe circumstances that the user should be aware of when managing the CMM directory structure on a stack with redundant CMMs. It also includes descriptions of the CLI commands designed to synchronize software between the primary and secondary CMMs. Rebooting the Switch When you reload the primary switch CMM in a stack, the secondary switch takes over the primary function.
Managing Redundancy in a Stack and CMM Managing CMM Directory Content Note. If a switch fails over to the secondary CMM, it is necessary to have a management interface connection to the secondary CMM (such as an Ethernet port or a console port). Copying the Working Directory to the Certified Directory Synchronizing the Primary and Secondary CMMs At the same time that you copy the working directory to the certified directory, you can synchronize the secondary CMM with the primary CMM.
Managing CMM Directory Content Managing Redundancy in a Stack and CMM Synchronizing the Primary and Secondary CMMs If you have a secondary CMM in your switch, it is necessary to synchronize the software between the primary and secondary CMMs. If the primary CMM goes down (for example, during a reboot), then the switch fails over to the secondary CMM.
Managing Redundancy in a Stack and CMM Managing CMM Directory Content To synchronize the secondary CMM to the primary CMM, enter the following command at the prompt: -> copy flash-synchro The 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.
Managing CMM Directory Content Managing Redundancy in a Stack and CMM Swapping the Primary CMM for the Secondary CMM If the primary CMM is having problems, or if it needs to be shut down, then the secondary CMM can be instructed to “take over” the switch operation as the primary CMM is shut down. Note. It is important that the software for the secondary CMM has been synchronized with the primary CMM before you initiate a secondary CMM takeover.
Managing Redundancy in a Stack and CMM Managing CMM Directory Content Show Currently Used Configuration In a chassis with a redundant CMM, the display for the currently running configuration tells the user if the primary and secondary CMMs are synchronized.
Managing CMM Directory Content Managing Redundancy in a Stack and CMM NI Module Behavior During Takeover If there are no unsaved configuration changes and the flash directories on both the primary and secondary management modules have been synchronized through the copy flash-synchro command, no NIs is reloaded if a management module takeover occurs. As a result, data flow is not interrupted on the NIs during the takeover.
Using the USB Flash Drive Managing CMM Directory Content 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. Additionally, automatic code upgrades as well as the capability to boot from the USB flash drive for disaster recovery purposes are also supported.
Managing CMM Directory Content Using the USB Flash Drive Disaster Recovery Using USB The switch can be configured to boot from the USB flash drive. This can be used if the image files on the 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: 1 It is recommended to prepare the USB flash drive prior to needing it for disaster recovery.
Emergency Restore of the boot.cfg File Managing CMM Directory Content Emergency Restore of the boot.cfg File If all copies of the boot.cfg file have been deleted and a system boot has occurred, network configuration information is permanently lost. However, if the files have been deleted and no boot has occurred you can issue a write memory command to regenerate the boot.cfg file. Can I Restore the boot.file While Running from Certified? Yes.
Managing CMM Directory Content Displaying CMM Conditions Displaying CMM Conditions To show various CMM conditions, such as where the switch is running from and which files are installed, use the following CLI show commands: show running-directory Shows the directory from where the switch was booted. show reload Shows the status of any time delayed reboot(s) that are pending on the switch. show microcode Displays microcode versions installed on the switch.
Displaying CMM Conditions page 5-36 Managing CMM Directory Content OmniSwitch 6250/6450 Switch Management Guide May 2012
6 Using the CLI Command Line Interface (CLI) is a text-based configuration interface that allows you to configure switch applications and to view switch statistics. 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.
Using the CLI CLI Specifications CLI Specifications The following table lists specifications for the Command Line Interface. Platforms Supported OmniSwitch 6250, 6450 Configuration Methods • • Online configuration through real-time sessions using CLI commands. Offline configuration using text file holding CLI commands. Command Capture Feature Snapshot feature captures switch configurations in a text file.
CLI Overview Using the CLI CLI Overview The CLI uses single-line text commands that are similar to other industry standard switch interfaces. However, the Alcatel-Lucent CLI is different from industry standard interfaces in that the Alcatel-Lucent uses a single level command hierarchy. Unlike other switch interfaces, the Alcatel-Lucent CLI has no concept of command modes. Other CLIs require you to step your way down a tree-type hierarchy to access commands.
Using the CLI Command Entry Rules and Syntax Command Entry Rules and Syntax When you start a session on the switch, you can execute CLI commands as soon as you are logged in. The following rules apply: • Enter only one command per line. • No command can be extended across multiple lines. • Passwords are case sensitive. • Commands are not case sensitive. The switch accepts commands entered in upper case, lower case, or a combination of both. • Press Enter to complete each command line entry.
Command Entry Rules and Syntax Using the CLI Using “Show” Commands The CLI contains show commands that allow you to view configuration and switch status on your console screen. The show syntax is used with other command keywords to display information pertaining to those keywords. For example, the show vlan command displays a table of all VLANs currently configured, along with pertinent information about each VLAN.
Using the CLI Command Entry Rules and Syntax Partial Keyword Completion The CLI has a partial keyword recognition feature that allows the switch to recognize partial keywords to CLI command syntax. Instead of typing the entire keyword, type only as many characters as is necessary to identify the keyword uniquely, then press the Tab key. The CLI completes the keyword and place the cursor at the end of the keyword.
Command Help Using the CLI Command Help The CLI has an internal help feature you can invoke by using the question mark (?) character as a command. The CLI help feature provides progressive information on how to build your command syntax, one keyword at a time. If you do not know the first keyword of the command you need, you can use a question mark character at the CLI system prompt. The CLI responds by listing command keywords divided into command sets.
Using the CLI Command Help Command Set Name Commands IP Routing & Multicast DEBUG, TRACEROUTE6, SHOW, PING6, NO, IPV6, IP, CLEAR QoS SHOW, QOS, POLICY, NO, DEBUG Debug UPDATE, SHOW, NO, DEBUG OmniSwitch 6250/6450 Switch Management Guide May 2012 page 6-8
Command Help Using the CLI Tutorial for Building a Command Using Help The Help feature allows you to figure out syntax for a CLI command by using a series of command line inquiries together with some educated guesses. If you do not know the correct CLI command you can use the Help feature to determine the syntax. This tutorial shows you how to use help to find the CLI syntax to create a VLAN. This VLAN will be given the ID number 33 and will be named “test vlan 2.
Using the CLI Command Help 3 At the command prompt, enter name followed by a space and a question mark. This step either gives you more choices or an error message. -> vlan 33 name ? ^ <"string"> (Vlan Manager Command Set) There is a smaller set of keywords available for use with the vlan 33 name syntax. This is because the command becomes more specialized as more keywords are added.
CLI Services Using the CLI CLI Services There are several services built into the CLI that help you use the interface. The Command Line Editing service makes it easy for you to enter and edit repetitive commands. Other CLI services, such as syntax checking, command help, prefix prompt, and history assist you in selecting and using the correct command syntax for the task you are performing. Command Line Editing CLI commands are entered from your keyboard and are executed when you press Enter.
Using the CLI CLI Services Recalling the Previous Command Line To recall the last command executed by the switch, press either the Up Arrow key or the !! (bang, bang) command at the prompt and the previous command is displayed on your screen. You can execute the command again by pressing Enter or you can edit it first by deleting or inserting characters. In the following example, the ls command is used to list the contents of the /flash/switch directory of the switch.
CLI Services Using the CLI Syntax Checking If you make a mistake while entering command syntax, the CLI gives you clues about how to correct your error. Whenever you enter an invalid command, two indicators are displayed. • The Error message tells you what the error is. • The caret (^) character tells you where the error is in your syntax. The following example of the syntax checking feature shows an attempt to set IP routing.
Using the CLI CLI Services Example for Using Prefix Recognition This example shows how the Prefix Recognition feature is used for entering multiple commands that have the same prefix. This table lists the tasks to be accomplished in this example and the CLI syntax required for each task. Task CLI Syntax 1. Create a VLAN with an identification number of 501. vlan 501 enable 2. Enable the spanning tree protocol for VLAN 501. vlan 501 stp enable 3. Enable authentication for VLAN 501.
CLI Services Using the CLI Prefix Prompt You can set the CLI so that your screen prompt displays the stored prefix. To display the stored prefix as part of the screen prompt for the VLAN example above, enter the prompt prefix CLI command as follows: -> prompt prefix The following is displayed: -> vlan 501 Your screen prompt includes your stored prefix until a new prompt is specified.
Using the CLI CLI Services You can recall commands shown in the history list by using the exclamation point character (!) also called “bang”. To recall the command shown in the history list at number 4, enter !4 (bang, 4). The CLI responds by printing the number four command at the prompt. Using the history list of commands above, the following would display: -> !4 -> show temp You can recall the last command in the history list by issuing the !! (bang bang) syntax.
Logging CLI Commands and Entry Results Using the CLI Logging CLI Commands and Entry Results The switch provides command logging through the command-log command. This feature allows users to record up to 100 of the most recent commands entered through Telnet, Secure Shell, and console sessions. In addition to a list of commands entered, the results of each command entry are recorded.
Using the CLI Logging CLI Commands and Entry Results Viewing the Current Command Logging Status As mentioned above, the command logging feature is disabled by default. To view whether the feature is currently enabled or disabled on the switch, use the show command-log status command. For example: -> show command-log status CLI command logging: Enable In this case, the feature has been enabled by the user through the command-log command.
Customizing the Screen Display Using the CLI Customizing the Screen Display The CLI has several commands that allow you to customize the way switch information is displayed to your screen. You can make the screen display smaller or larger. You can also adjust the size of the table displays and the number of lines shown on the screen. Note. Screen display examples in this chapter assume the use of a VT-100/ASCII emulator.
Using the CLI Customizing the Screen Display Setting Session Prompt as System Name CLI prompt can be configured as the current system name of the switch. By default, the system name is set to ‘VxTarget’. This can be configured using the command session prompt default system-name. Every time the system name is modified, the prompt also gets modified. The new prompt takes effect after relogging to a new session. Note. System name is configured for the switch using the CLI command system name.
Customizing the Screen Display Using the CLI To exit the more mode, use the no more CLI command. Note. The value set with the more size command applies to the screen display when the CLI is in the more mode or when you are using the Vi text editor of the switch. Filtering Table Information The CLI allows you to define filters for displaying table information. This is useful in cases where a vast amount of display data exists but you are interested in only a small subset of that data.
Using the CLI Multiple User Sessions Multiple User Sessions Several CLI commands give you information about user sessions that are currently operating on the OmniSwitch, including your own session. These commands allow you to list the number and types of sessions that are currently running on the switch. You can also terminate another session, provided you have administrative privileges. Listing Other User Sessions The who command displays all users currently logged into the OmniSwitch.
Multiple User Sessions Using the CLI Listing Your Current Login Session To list information about your current login session, use the who command and identify your login by your IP address or enter the whoami command. The following is displayed: -> whoami Session number = 4 User name = admin, Access type = telnet, Access port = NI, IP address = 148.211.11.
Using the CLI Multiple User Sessions Possible values for command domains and families are listed here: domain families domain-admin file telnet debug domain-system system aip snmp rmon webmgt config domain-physical chassis module interface pmm health domain-network ip rip ip-routing ipmr ipms rdp ipv6 domain-layer2 vlan bridge stp 802.
Using the CLI Application Example Application Example Using a Wildcard to Filter Table Information The wildcard character allows you to substitute the asterisk (*) character for text patterns while using the filter mode. Note. Type the wildcard character in front of and after the filter text pattern unless the text pattern appears alone on a table row. In this example, the show snmp mib family command is used because it displays a long table of MIB information.
Using the CLI Application Example 4 Press the spacebar key to execute the filter option. The following is displayed.
Using the CLI Verifying CLI Usage Verifying CLI Usage To display information about CLI commands and the configuration status of your switch, use the show commands listed here: show session config Displays session manager configuration information (for example, default prompt, banner file name, and inactivity timer). show alias Lists all current commands defined by the use of the alias CLI command. show prefix Shows the command prefix (if any) currently stored by the CLI.
Verifying CLI Usage page 6-28 Using the CLI OmniSwitch 6250/6450 Switch Management Guide May 2012
7 Working With Configuration Files Commands and settings needed for the OmniSwitch can be contained in an ASCII-based configuration text file. Configuration files can be created in several ways and are useful in network environments where multiple switches must be managed and monitored. This chapter describes how configuration files are created, how they are applied to the switch, and how they can be used to enhance OmniSwitch usability.
Configuration File Specifications Working With Configuration Files Configuration File Specifications The following table lists specifications applicable to Configuration Files. Creation Methods for Configuration Files • • • Timer Functions Files can be applied immediately or by setting a timer on the switch. Command Capture Feature Snapshot feature captures switch configurations in a text file. Error Reporting Snapshot feature includes error reporting in the text file.
Working With Configuration Files Tutorial for Creating a Configuration File 4 Use the show configuration status command to verify that the dhcp_relay.txt configuration file was applied to the switch. The display is similar to the one shown here: -> show configuration status File configuration : completed with no errors File configuration: none scheduled Running configuration and saved configuration are different Note.
Quick Steps for Applying Configuration Files Working With Configuration Files Quick Steps for Applying Configuration Files Setting a File for Immediate Application In this example, the configuration file configfile_1 exists on the switch in the /flash directory. When these steps are followed, the file will be immediately applied to the switch. 1 Verify that there are no timer sessions pending on the switch.
Working With Configuration Files Quick Steps for Applying Configuration Files Note. Optional. To verify that the switch received this configuration apply request, enter the show configuration status command. The display is similar to the one shown here. -> show configuration status File configuration : scheduled at 07/04/02 09:00 For more information about this display see “Configuration File Manager Commands” in the OmniSwitch 6250/6450 CLI Reference Guide.
Configuration Files Overview Working With Configuration Files Configuration Files Overview Instead of using CLI commands entered at a workstation, you can configure the switch using an ASCIIbased text file. You may type CLI commands directly into a text document to create a configuration file that will reside in your switch’s /flash directory.
Working With Configuration Files Configuration Files Overview Cancelling a Timed Session You may cancel a pending timed session by using the configuration cancel command. To confirm that your timer session has been cancelled, use the show configuration status command. The following will display.
Configuration Files Overview Working With Configuration Files Setting the Error File Limit The number of files ending with the .err extension present in the switch’s /flash directory is set with the configuration error-file limit command. You can set the switch to allow up to 25 error files in the /flash directory. Once the error file limit has been reached, the next error file generated will cause the error file with the oldest time stamp to be deleted.
Working With Configuration Files Configuration Files Overview Verbose Mode Syntax Checking When verbose is specified in the command line, all syntax contained in the configuration file is printed to the console, even if no error is detected. (When verbose is not specified in the command line, cursory information—number of errors and error log file name—will be printed to the console only if a syntax or configuration error is detected.
Creating Snapshot Configuration Files Working With Configuration Files Creating Snapshot Configuration Files You can generate a list of configurations currently running on the switch by using the configuration snapshot command. A snapshot is a text file that lists commands issued to the switch during the current login session. Note. A user must have read and write permission for the configuration family of commands to generate a snapshot file for those commands.
Working With Configuration Files Creating Snapshot Configuration Files User-Defined Naming Options When the snapshot syntax does not include a file name, the snapshot file is created using the default file name asc.n.snap. Here, the n character holds the place of a number indicating the order in which the snapshot file name is generated. For example, the following syntax may generate a file named asc.1.snap.
Creating Snapshot Configuration Files Working With Configuration Files Example Snapshot File Text The following is the text of a sample snapshot file created with the configuration snapshot all command. !========================================! ! File: asc.1.snap ! !========================================! ! Chassis : system name FujiCmm mac alloc 91 0 1 00:d0:95:6b:09:41 ! Configuration: ! VLAN : ! VLAN SL: ! IP : ip service all icmp unreachable net-unreachable disable ip interface "vlan-1" address 10.
Working With Configuration Files Creating Snapshot Configuration Files 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.
Verifying File Configuration Working With Configuration Files Verifying File Configuration You can verify the content and the status of the switch’s configuration files with commands listed in the following table. show configuration status Displays whether there is a pending timer session scheduled for a configuration file and indicates whether the running configuration and the saved configuration files are identical or different.
8 Managing Automatic Remote Configuration Download The Automatic Remote Configuration feature enables: • the automatic upgrade of firmware and/or configuration of an OmniSwitch without user intervention. • the automated configuration of the switch on bootup, when the switch is connected to the network for the first time. • the automatic download and installation of the critical configuration bootup and image files. In This Chapter This chapter describes the Automatic Remote Configuration on OmniSwitch.
Automatic Remote Configuration Specifications Managing Automatic Remote Configuration Download Automatic Remote Configuration Specifications Platforms Supported OmniSwitch 6250, 6450 DHCP Specifications DHCP Server required Temporary DHCP Client on VLAN 1 or VLAN 127 (DHCP client on VLAN 127 only works on combo and uplink ports) File Servers TFTP FTP/SFTP Clients supported TFTP FTP/SFTP Instruction file Maximum length of: • Pathname: 255 characters • Filename: 63 characters Maximum length of use
Managing Automatic Remote Configuration Download Automatic Remote Configuration Defaults Automatic Remote Configuration Defaults Description Default Management VLAN Untagged Management VLAN VLAN 1 DHCP broadcast VLAN 802.1q tagged VLAN VLAN 127 Default Auto Link Aggregate Creation Between VLAN 1 and VLAN 127 Instruction file Location: TFTP Server File name: *.alu (* represents any instruction filename) Download location: /flash directory Downloaded as a temporary file.
Quick Steps for Automatic Remote Configuration Managing Automatic Remote Configuration Download Quick Steps for Automatic Remote Configuration 1 Configure the DHCP server in the network to provide IP address, gateway, and TFTP server addresses to the OmniSwitch DHCP client. 2 Store the instruction file on the TFTP server. 3 Store the configuration, image, and script files on the primary and/or secondary FTP/SFTP servers. 4 When the OmniSwitch is integrated in to the network as a new device with no boot.
Managing Automatic Remote Configuration Download Overview Overview The Automatic Remote Configuration feature provides the advantage of automatic download and installation of critical configuration and image files at initial bootup or when firmware upgrade is required for the OmniSwitch. Automatic Remote Configuration download occurs when: • There is no bootup configuration file (boot.cfg) in the working directory of the switch. • During a takeover or reboot on the new Primary unit or CMM.
Overview Managing Automatic Remote Configuration Download Network Components The network components required for the Automatic Remote Configuration download process are: • DHCP server (mandatory) • TFTP file server (mandatory) • Primary FTP/SFTP server (mandatory) • Secondary FTP/SFTP server (optional) • Management Switch (only required for Nearest-Edge Mode) Information Provided by DHCP Server When the network interfaces or ports on the switch are ready, a DHCP client is automatically configured on any
Managing Automatic Remote Configuration Download Overview File Servers and Download Process The download process from the file servers is as follows: 1 The username required to connect to the FTP/SFTP enabled servers is provided in the instruction file. The password required to connect to the servers is same as the username. 2 The required files mentioned in the instruction file are downloaded from the primary FTP/SFTP file server.
Interaction With Other Features Managing Automatic Remote Configuration Download Interaction With Other Features This section contains important information about how other OmniSwitch features interact with Automatic Remote Configuration. Refer to the specific sections if required, to get detailed information about the feature interaction process.
Managing Automatic Remote Configuration Download Automatic Remote Configuration Download Process Automatic Remote Configuration Download Process The automatic remote configuration process is initialized when an OmniSwitch is integrated in to the network as a new device or when a firmware and configuration upgrade is required. If the automatic configuration download process is not performed completely on the switch, manual intervention is required.
Automatic Remote Configuration Download Process Managing Automatic Remote Configuration Download Process Illustration The following flowchart represents the automatic remote configuration download process in detail. . Power ON Yes Is boot.
Managing Automatic Remote Configuration Download Automatic Remote Configuration Download Process Additional Process Notes 1 Once the switch obtains an IP interface from the DHCP server, remote access through SSH is automatically configured to allow remote access in case of any download errors during the Auto Configuration process. Note. It is not recommended to have the write memory command in the script file if a configuration file is downloaded. This causes the boot.
Download Component Files Managing Automatic Remote Configuration Download Download Component Files This section provides the details of the files downloaded and how they are utilized during the automatic configuration process. The main component files are: • Instruction file -The instruction file is the initial file required for the automatic remote configuration process to occur. The instruction file is stored in the TFTP server with the .alu extension.
Managing Automatic Remote Configuration Download Download Component Files Instruction File Syntax The instruction file is a text file containing the following information: Header Contains user information such as switch ID, file version, and so on. Header text is a type of comment. Comments Comments provide additional information for better user readability. These lines are ignored during the remote configuration download process.
Download Component Files Managing Automatic Remote Configuration Download Instruction File Usage Guidelines • The instruction file is case sensitive and can contain only the keywords provided in the instruction file output example. • The keywords can be placed in any order. • If the Keyword:Value format is incorrect, the information on that line is discarded. • Firmware version must be provided in the format as specified in the example.
Managing Automatic Remote Configuration Download Download Component Files Debug Configuration File The debug configuration file is used for setting specific OmniSwitch settings and must only be used as directed by Service and Support. During the automatic remote configuration process, the debug configuration file is downloaded with the filename AlcatelDebug.cfg. Script File The script file is downloaded and stored with the same name in the /flash/working directory.
LACP Auto Detection and Automatic Link Aggregate Association Managing Automatic Remote Configuration Download LACP Auto Detection and Automatic Link Aggregate Association DHCP Server Association and DHCP Client creation works on fixed ports. When an OmniSwitch is newly introduced to a network, an assigned peer network device detects this device as new. If the peer device has a link aggregate configuration on the detecting port, then it sends LACP PDU to the newly connected OmniSwitch.
Managing Automatic Remote Configuration Download DHCP Client Auto-Configuration Process LACP auto detection is enabled by default and operates only on the combo ports and uplink ports on OmniSwitch during the Automatic Remote Configuration stage. 1 When an OmniSwitch detects LACP PDUs from a remote peer connected through a combo or an uplink port, it configures that port as a LACP port and starts LACP handshake with the peer device.
DHCP Client Auto-Configuration Process Managing Automatic Remote Configuration Download 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.
Managing Automatic Remote Configuration Download DHCP Client Auto-Configuration Process The detailed process of DHCP client auto-configuration on OmniSwitch is as follows: 1 At boot-up, the initial DHCP client starts with untagged VLAN 1.The DHCP client waits for 30 seconds for a DHCP lease. 2 If the lease is not obtained even after 30 seconds, the DHCP client is stopped on the untagged VLAN 1 and DHCP client is started on tagged VLAN 127.
Nearest-Edge Mode Operation Managing Automatic Remote Configuration Download Nearest-Edge Mode Operation In order for the network to propagate Nearest-Edge mode LLDP PDUs a Management Switch must be configured to send the LLDP PDUs with the Management VLAN information. Additionally, the peer switches are automatically configured to process the Nearest-Edge Mode LLDP PDU frames by the Automatic Configuration Download feature.
Managing Automatic Remote Configuration Download Nearest-Edge Mode Operation Access Switch When used in conjunction with the Automatic Remote Configuraton feature no configuration is necessary on the Access OmniSwitches. Newly connected switches without a boot.cfg file receive the Nearest-Edge LLDP PDUs, discover the Management VLAN, tag the port with that VLAN ID, and create a DHCP client interface on the Managment VLAN.
Zero Touch License Upgrade Managing Automatic Remote Configuration Download 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.
Managing Automatic Remote Configuration Download Troubleshooting Troubleshooting Due to errors during download, the automatic configuration process can halt, or the file download process can be incomplete. The errors that occur during the automatic remote configuration download process are displayed on the switch command prompt and also stored in switch log or the swlog.log file.
Troubleshooting Managing Automatic Remote Configuration Download Error Description Table The following table provides information on the common server connection failures and file download errors that can occur during Automatic Remote Configuration: Error Type Error Description User Login Auto-Config Abort User logged in via console, Automatic Remote configuration is aborted. DHCP client is automatically stopped only if a user logs in to the switch through console port before getting the DHCP lease.
Managing Automatic Remote Configuration Download Troubleshooting Error Description Table The following error description table provides information about some of the common script file errors that occur during Automatic Remote Configuration: Error Type Error Description Script File Download Download of Script file from Primary Server Failed Script file cannot be downloaded from the primary server.
Troubleshooting page 8-26 Managing Automatic Remote Configuration Download OmniSwitch 6250/6450 Switch Management Guide May 2012
9 Managing Switch User Accounts Switch user accounts can be set up locally on the switch for users to log into and manage the switch. The accounts specify login information (combinations of usernames and passwords) and privilege or profile information depending on the type of user. The switch has several interfaces (console, Telnet, HTTP, FTP, Secure Shell, and SNMP) through which users can access the switch. The switch can be set up to allow or deny access through any of these interfaces.
User Database Specifications Managing Switch User Accounts User Database Specifications Platforms Supported OmniSwitch 6250, 6450 Maximum number of alphanumeric characters in a username 31 Maximum number of alphanumeric characters in a user password 31 Maximum number of alphanumeric characters in an end-user profile name 32 Maximum number of user accounts 64 Maximum number of end-user profiles 128 User Account Defaults • Two user accounts are available on the switch by default: admin and defa
Managing Switch User Accounts • User Account Defaults Global user account lockout defaults are as follows: Parameter Description Command Default Length of time during which failed login attempts are counted. user lockout-window 0—all attempts are counted Length of time a user account remains locked out of the switch before the account is automatically unlocked.
Overview of User Accounts Managing Switch User Accounts Overview of User Accounts A user account includes a login name, password, and user privileges. The account also includes privilege or profile information, depending on the type of user account. There are two types of accounts: network administrator accounts and end-user or customer login accounts. Network administrator accounts are configured with user (sometimes called functional) privileges.
Managing Switch User Accounts Overview of User Accounts 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.
Overview of User Accounts Managing Switch User Accounts Startup Defaults By default, a single user management account is available at the first bootup of the switch. This account has the following user name and password: • user name—admin • password—switch Initially, the admin user can only be authorized on the switch through the console port. Management access through any other interface is disabled.
Managing Switch User Accounts Overview of User Accounts Quick Steps for Network Administrator User Accounts 1 Configure the user with the relevant username and password. For example, to create a user called thomas with a password of techpubs, enter the following: -> user thomas password techpubs For information about creating a user and setting up a password, see “Creating a User” on page 9-12.
Overview of User Accounts Managing Switch User Accounts Quick Steps for Creating Customer Login User Accounts 1 Set up a user profile through the aaa admin-logout command. For example, configure a profile called Profile1 that specifies read-write access to the physical and basic-ip-routing command areas: -> end-user profile Profile1 read-write physical basic-ip-routing 2 Specify ports to which the profile will allow access.
Managing Switch User Accounts Overview of User Accounts Default User Settings The default user account on the switch is used for storing new user defaults for privileges and profile information. This account does not include a password and cannot be used to log into the switch. At the first switch startup, the default user account is configured for: • No read or write access. • No SNMP access. • No end-user profile.
Overview of User Accounts Managing Switch User Accounts Account and Password Policy Settings The switch includes global password settings that are used to implement and enforce password complexity when a password is created, modified, and used. These user-configurable settings apply the following password requirements to all user accounts configured for the switch: • Minimum password size. • Whether or not a password can contain the account username. • Minimum password character requirements.
Managing Switch User Accounts Overview of User Accounts How User Settings Are Saved Unlike other settings on the switch, user settings configured through the password command are saved to the switch configuration automatically. These settings are saved in real time in the local user database. At bootup, the switch reads the database file for user information (rather than the boot.cfg file).
Creating a User Managing Switch User Accounts Creating a User To create a new user, enter the user command with the desired username and password. Use the password keyword. For example: -> user thomas password techpubs In this example, a user account with a user name of thomas and a password of techpubs is stored in the local user database. The password must be a string of non-repeating characters. The CLI uses the first occurrence of the character series to uniquely identify the password.
Managing Switch User Accounts Creating a User 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.
Creating a User Managing Switch User Accounts User-Configured Password Users can change their own passwords by using the password command. In this example, the current user wants to change her password to my_passwd. Follow these steps to change the password: 1 Enter the password command. The system displays a prompt for the new password: -> password enter old password: 2 Enter the old password. (The password is concealed with asterisks.) A prompt displays for the new password.
Managing Switch User Accounts Creating a User 3 Enter the desired password. The system then displays a prompt to verify the password. -> password enter old password:******** enter new password: ********* reenter new password: 4 Enter the password again. -> password enter old password:******** enter new password: ********* reenter new password: ********* -> The password is now reset for the current user. At the next switch login, the user must enter the new password. Note.
Configuring Password Policy Settings Managing Switch User Accounts Configuring Password Policy Settings The global password policy settings for the switch define the following requirements that are applied to all user accounts: • Minimum password size. • Whether or not the password can contain the username. • The minimum number of uppercase characters required in a password. • The minimum number of uppercase characters required in a password.
Managing Switch User Accounts Configuring Password Policy Settings Setting a Minimum Password Size The default minimum password length (or size) is 8 characters. To configure a minimum password size, enter the user password-size min command. 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.
Configuring Password Policy Settings Managing Switch User Accounts Configuring the Username Password Exception By default, specifying the username as all or part of a password is allowed. Use the user password-policy cannot-contain-username command to block the ability to configure a password that contains the username.
Managing Switch User Accounts Configuring Password Policy Settings Configuring Password Character Requirements The character requirements specified in the global password policy determine the minimum number of uppercase, lowercase, non-alphanumeric, and 10-base digit characters required in all passwords. These requirements are configured using the following user password-policy commands: Command Configures ...
Configuring Password Policy Settings Managing Switch User Accounts Configuring Password Expiration By default, password expiration is disabled on the switch. A global default password expiration can be specified for all users or password expiration can be set for an individual user. Note. When the current user’s password has less than one week before expiration, the switch will display an expiration warning after login.
Managing Switch User Accounts Configuring Password Policy Settings Configuring the Password History The password history refers to the number of old passwords for each user account that are saved by the switch. This functionality prevents the user from using the same password each time their account password is changed.
Configuring Global User Lockout Settings Managing Switch User Accounts Configuring the Minimum Age for a Password The password minimum age setting specifies the number of days during which a user is not allowed to change their password. It is necessary to configure a password minimum age value that is less than the password expiration value. The default minimum age is set to zero, which means that there is no minimum age requirement for a password.
Managing Switch User Accounts Configuring Global User Lockout Settings Configuring the User Lockout Window The lockout window is basically a moving observation window of time in which failed login attempts are counted. If the number of failed login attempts exceeds the lockout threshold setting (see “Configuring the User Lockout Threshold Number” on page 9-24) during any given observation window period of time, the user account is locked out of the switch.
Configuring Global User Lockout Settings Managing Switch User Accounts Configuring the User Lockout Threshold Number The lockout threshold number specifies the number of failed login attempts allowed during any given lockout window period of time (see “Configuring the User Lockout Window” on page 9-23).
Managing Switch User Accounts Configuring Global User Lockout Settings Configuring the User Lockout Duration Time The user lockout duration time specifies the number of minutes a user account remains locked until it is automatically unlocked by the switch. This period of time starts when the user account is locked out of the switch. At any point during the lockout duration time, the admin user can still manually unlock the user account.
Configuring Global User Lockout Settings Managing Switch User Accounts Manually Locking and Unlocking User Accounts The user lockout unlock command is used to manually lock or unlock a user account. This command is only available to the admin user or a user who has read/write access privileges to the switch. To lock a user account, enter user lockout and the username for the account. For example, -> user lockout j_smith To unlock a user account, enter user unlock and the username for the locked account.
Managing Switch User Accounts Configuring Privileges for a User Configuring Privileges for a User To configure privileges for a user, enter the user command with the read-only or read-write option and the desired CLI command domain names or command family names. The read-only option provides access to show commands; the read-write option provides access to configuration commands and show commands. Command families are subsets of command domains.
Setting Up SNMP Access for a User Account Managing Switch User Accounts Setting Up SNMP Access for a User Account By default, users can access the switch based on the SNMP setting specified for the default user account. The user command, however, can be used to configure SNMP access for a particular user. SNMP access can be configured without authentication and encryption required (supported by SNMPv1, SNMPv2, or SNMPv3).
Managing Switch User Accounts Setting Up SNMP Access for a User Account SNMP Access Without Authentication/Encryption To give a user SNMP access without SNMP authentication required, enter the user command with the no auth option.
Setting Up SNMP Access for a User Account Managing Switch User Accounts SNMP Access With Authentication/Encryption To configure a user with SNMP access and authentication, enter the user command with the desired authentication type (sha, md5, sha+des, and md5+des). -> user thomas password techpubs sha+des When SNMP authentication is specified, an SNMP authentication key is computed from the user password based on the authentication/encryption setting.
Managing Switch User Accounts Setting Up SNMP Access for a User Account 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.
Setting Up End-User Profiles Managing Switch User Accounts Setting Up End-User Profiles End-user profiles are designed for user accounts in the carrier market. With end-user profiles, a network administrator can configure customer login accounts that restrict users to particular command areas over particular ports and/or VLANs. End-user profiles are only managed and stored on the switch; profiles are not stored on external servers. Note.
Managing Switch User Accounts Setting Up End-User Profiles Creating End-User Profiles To set up an end-user profile, use the aaa admin-logout command and enter a name for the profile. Specify read-only or read-write access to particular command areas. The profile can also specify port ranges and/or VLAN ranges. The port ranges and VLAN ranges must be configured on separate command lines and are discussed in the next sections.
Setting Up End-User Profiles Managing Switch User Accounts Setting Up Port Ranges in a Profile To set up port ranges for a profile, enter the end-user profile port-list command with the relevant profile name and the desired slots/ports. For example: -> end-user profile Profile3 port-list 2 3/1-4 In this example, the port list includes all ports in slot 2, and ports 1 through 4 on slot 3. A user with this profile will be able to manage these ports (depending on the command areas specified in the profile).
Managing Switch User Accounts Setting Up End-User Profiles Setting Up VLAN Ranges in a Profile To set up VLAN ranges for a profile, enter the end-user profile vlan-range command with the relevant profile name and the desired VLAN range. For example: -> end-user profile Profile3 vlan-range 2-4 7-8 In this example, the VLAN range includes VLANs 2, 3, 4, 7, and 8. A user with this profile will be able to manage these VLANs (depending on the command areas specified in the profile).
Setting Up End-User Profiles Managing Switch User Accounts Associating a Profile With a User To associate a profile with a user, enter the user command with the end-user profile keywords and the relevant profile name. For example: -> user Customer2 end-user profile Profile3 Profile3 is now associated with Customer2. When Customer2 logs into the switch, Customer2 will have access to command areas, port ranges, and VLAN ranges specified by Profile3.
Managing Switch User Accounts Setting Up End-User Profiles Removing a Profile From the Configuration To delete a profile from the configuration, enter the no form of the end-user profile command with the name of the profile you want to delete. For example: -> no end-user profile Profile3 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.
Verifying the User Configuration Managing Switch User Accounts Verifying the User Configuration To display information about user accounts configured locally in the user database, use the show commands listed here: show user Displays information about all users or a particular user configured in the local user database on the switch. show user password-size Displays the minimum number of characters that are required for a user password.
10 Managing Switch Security Switch security is provided on the switch for all available management interfaces (console, Telnet, HTTP, FTP, Secure Shell, and SNMP). The switch can be set up to allow or deny access through any of these interfaces. (Users attempting to access the switch must have a valid username and password.) In This Chapter This chapter describes how to set up switch management interfaces through the Command Line Interface (CLI).
Switch Security Specifications Managing Switch Security Switch Security Specifications The following table describes the maximum number of sessions allowed on an OmniSwitch: Session OmniSwitch 6250, 6450 Telnet (v4 or v6) 4 FTP (v4 or v6) 4 SSH + SFTP (v4 or v6 secure sessions) 8 HTTP 4 Total Sessions 20 SNMP 50 Note. An IPv6 client session for Telnet, FTP, SSH, SFTP, and SNMP is supported on an OmniSwitch 6250, 6450.
Managing Switch Security Switch Security Overview Switch Security Overview Switch security features increase the security of the basic switch login process by allowing management only through particular interfaces for users with particular privileges. Login information and privileges can be stored on the switch and/or an external server, depending on the type of external server you are using and how you configure switch access.
Authenticated Switch Access Managing Switch Security Authenticated Switch Access Authenticated Switch Access (ASA) is a way of authenticating users who want to manage the switch. With authenticated access, all switch login attempts using the console or modem port, Telnet, FTP, SNMP, or HTTP require authentication via the local user database or via a third-party server.
Managing Switch Security Authenticated Switch Access The following illustration shows the two different user types attempting to authenticate with an ACE/ Server: Network Administrator Customer login request login request ACE/Server ACE/Server user privileges The switch polls the server for login information; privileges are stored on the switch. The switch polls the server for login information; enduser profiles are stored on the switch.
Configuring Authenticated Switch Access Managing Switch Security Configuring Authenticated Switch Access Setting up Authenticated Switch Access involves the following general steps: 1 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. 2 Set Up the Local User Database.
Managing Switch Security Quick Steps for Setting Up ASA Quick Steps for Setting Up ASA 1 If the local user database is used for user login information, set up user accounts through the user command. User accounts includes user privileges or an end-user profile.
Quick Steps for Setting Up ASA Managing Switch Security The order of the server names is important here as well. In this example, the switch will use ldap2 for logging switch access sessions. If ldap2 becomes unavailable, the switch will use the local Switch Logging facility. For more information about Switch Logging, see the OmniSwitch 6250/6450 Network Configuration Guide. Note. To verify the switch access setup, enter the show aaa authentication command.
Managing Switch Security Setting Up Management Interfaces for ASA Setting Up Management Interfaces for ASA By default, authenticated access is available through the console port. Access through other management interfaces is disabled. Other management interfaces include Telnet, FTP, HTTP, Secure Shell, and SNMP. This chapter describes how to set up access for management interfaces. For more details about particular management interfaces and how they are used, see Chapter 2, “Logging Into the Switch.
Setting Up Management Interfaces for ASA Managing Switch Security Enabling Switch Access Enter the aaa authentication command with the relevant keyword that indicates the management interface and specify the servers to be used for authentication. In this example, Telnet access for switch management is enabled.
Managing Switch Security Setting Up Management Interfaces for ASA In this scenario, SNMP access is not enabled because only RADIUS servers have been included in the default setting. If servers of different types are configured and include LDAP or local, SNMP will be enabled through those servers. For example: -> aaa authentication default rad1 ldap2 local In this case, SNMP access is enabled, and users will be authenticated through ldap2 and the local database.
Configuring Accounting for ASA Managing Switch Security Configuring Accounting for ASA Accounting servers track network resources such as time, packets, bytes, and user activity (when a user logs in and out, how many login attempts were made, session length, and so on.). The accounting servers can be located anywhere in the network. Note the following: • Up to four servers can be configured. • The servers can be of different types. • ACE cannot be used as an accounting server.
Managing Switch Security Verifying the ASA Configuration Verifying the ASA Configuration To display information about management interfaces used for Authenticated Switch Access, use the show commands listed here: show aaa authentication Displays information about the current authenticated switch session. show aaa accounting mac Displays information about accounting servers configured for Authenticated Switch Access or Authenticated VLANs.
Verifying the ASA Configuration page 10-14 Managing Switch Security OmniSwitch 6250/6450 Switch Management Guide May 2012
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 Note. For information about setting up browser preferences and options, see “Browser Setup” on page 11-2.
WebView CLI Defaults Using WebView WebView CLI Defaults Web Management Command Line Interface (CLI) commands allow you to enable/disable WebView, enable/disable Secure Socket Layer (SSL), and view basic WebView parameters. These configuration options are also available in WebView.
Using WebView WebView CLI Commands WebView CLI Commands The following configuration options can be performed using the CLI. These configuration options are also available in WebView; but changing the web server port or secured port can only be done through the CLI (or SNMP). Enabling/Disabling WebView WebView is enabled on the switch by default. If necessary, use the http server command to enable WebView. For example: -> http server Use the no http server command to disable WebView on the switch.
WebView CLI Commands Using WebView Enabling/Disabling SSL Force SSL is disabled by default. Use the http ssl command to enable Force SSL on the switch. For example: -> http ssl Use the no http ssl command to disable Force SSL on the switch. Use the show http command to view WebView status. As an alternative you can use the https keyword instead of the http keyword to enable Force SSL.
Using WebView Quick Steps for Setting Up WebView Quick Steps for Setting Up WebView 1 Make sure you have an Ethernet connection to the switch. 2 Configure switch management for HTTP using the aaa authentication command. Enter the command, the port type that you are authenticating (http), and the name of the LDAP, RADIUS, ACE, or local server that is being used for authentication.
WebView Overview Using WebView Banner Configuration Group Feature options Toolbar View/Configuration Area Configuration Feature WebView Chassis Home Page Banner The following features are available in the WebView Banner: • Options—Brings up the User Options Page, which is used to change the user login password. • Save Config—Brings up the Save Configuration Screen. Click Apply to save the running configuration of the switch for the next startup. • Help—Brings up general WebView Help.
Using WebView WebView Overview View/Configuration Area The View/Configuration area is where switch configuration information is displayed and where configuration pages appear. 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 configure the switch.
WebView Overview page 11-8 Using WebView OmniSwitch 6250/6450 Switch Management Guide May 2012
A Software License and Copyright Statements This appendix contains Alcatel-Lucent and third-party software vendor license and copyright statements. Alcatel-Lucent License Agreement ALCATEL-LUCENT SOFTWARE LICENSE AGREEMENT IMPORTANT. Please read the terms and conditions of this license agreement carefully before opening this package. By opening this package, you accept and agree to the terms of this license agreement.
Alcatel-Lucent License Agreement Software License and Copyright Statements 3. Confidentiality. Alcatel-Lucent considers the Licensed Files to contain valuable trade secrets of Alcatel-Lucent, the unauthorized disclosure of which could cause irreparable harm to Alcatel-Lucent. Except as expressly set forth herein, Licensee agrees to use reasonable efforts not to disclose the Licensed Files to any third party and not to use the Licensed Files other than for the purpose authorized by this License Agreement.
Software License and Copyright Statements Alcatel-Lucent License Agreement Alcatel-Lucent, Licensee agrees to return to Alcatel-Lucent or destroy the Licensed Materials and all copies and portions thereof. 10. Governing Law. This License Agreement shall be construed and governed in accordance with the laws of the State of California. 11. Severability.
Third Party Licenses and Notices Software License and Copyright Statements Third Party Licenses and Notices The licenses and notices related only to such third party software are set forth below: A.
Software License and Copyright Statements Third Party Licenses and Notices C. Linux Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. D. GNU GENERAL PUBLIC LICENSE: Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
Third Party Licenses and Notices Software License and Copyright Statements verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
Software License and Copyright Statements Third Party Licenses and Notices b Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c Accompany it with the information you received as to the offer to distr
Third Party Licenses and Notices Software License and Copyright Statements consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
Software License and Copyright Statements Third Party Licenses and Notices Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program.
Third Party Licenses and Notices Software License and Copyright Statements Material copyright Linux Online Inc. Design and compilation copyright (c)1994-2002 Linux Online Inc. Linux is a registered trademark of Linus Torvalds Tux the Penguin, featured in our logo, was created by Larry Ewing Consult our privacy statement URLWatch provided by URLWatch Services. All rights reserved. E.
Software License and Copyright Statements Third Party Licenses and Notices above restrictions. (This clause is necessary due to a potential bad interaction between the GPL and the restrictions contained in a BSD-style copyright.) THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF WHICH ARE HEREBY DISCLAIMED.
Third Party Licenses and Notices Software License and Copyright Statements K. Sun Microsystems, Inc. This product contains Coronado ASIC, which includes a component derived from designs licensed from Sun Microsystems, Inc. L. Wind River Systems, Inc. Provided with this product is certain software (“Run-Time Module”) licensed from Wind River Systems, Inc.
Software License and Copyright Statements Third Party Licenses and Notices N.Remote-ni Provided with this product is a file (part of GDB), the GNU debugger and is licensed from Free Software Foundation, Inc., whose copyright notice is as follows: Copyright (C) 1989, 1991, 1992 by Free Software Foundation, Inc. Licensee can redistribute this software and modify it under the terms of General Public License as published by Free Software Foundation Inc.
Third Party Licenses and Notices Software License and Copyright Statements Q.Boost C++ Libraries Provided with this product is free peer-reviewed portable C++ source libraries. Version 1.33.1 Copyright (C) by Beman Dawes, David Abrahams, 1998-2003. All rights reserved. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT.
Software License and Copyright Statements Third Party Licenses and Notices 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
Third Party Licenses and Notices Software License and Copyright Statements This software is not subject to any license of Eindhoven University of Technology.Redistribution and use in source and binary forms are permitted only as authorized by the OpenLDAP Public License. This software is not subject to any license of Silicon Graphics Inc.or Purdue University. Redistribution and use in source and binary forms are permitted without restriction or fee of any kind as long as this notice is preserved. Y.
B SNMP Trap Information This appendix lists the supported SNMP traps along with their descriptions.
SNMP Traps Table SNMP Trap Information SNMP Traps Table The following table provides information on all SNMP traps supported by the switch. Each row includes the trap name, its ID number, any objects (if applicable), its command family, and a description of the condition the SNMP agent in the switch is reporting to the SNMP management station. No. Trap Name Objects Family Description 0 coldStart none chassis The SNMP agent in the switch is reinitiating and its configuration may have been altered.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family Description 4 authenticationFailure none snmp The SNMP agent in the switch has received a protocol message that is not properly authenticated. 5 entConfigChange none module An entConfigChange notification is generated when a conceptual row is created, modified, or deleted in one of the entity tables.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 9 chassisTrapsStr- chassis Level chassisTrapsStrAppID chassisTrapsStrSnapID chassisTrapsStrfileName chassisTrapsStrfileLineNb chassisTrapsStrErrorNb chassisTrapsStrcomments chassisTrapsStrdataInfo chassisTrapsStr Family Description A software trouble report (STR) was sent by an application encountering a problem during its execution. chassisTrapsStrLevel—An enumerated value that provides the urgency level of the STR.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 11 chassis physicalIndex chassisTrapsObjectType chassisTrapsObjectNumber chasEntPhysOperStatus chassisTrapsStateChange Family Description An NI status change was detected. physicalIndex—The physical index of the involved object. chassisTrapsObjectType—An enumerated value that provides the object type involved in the alert trap. chassisTrapsObjectNumber—A number defining the order of the object in the set (e.g.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family Description 16 healthModuleSlot healthMonRxStatus healthMonRxTxStatus healthMonMemoryStatus healthMonCpuStatus health Indicates a module-level threshold was crossed. healthMonModuleTrap healthModuleSlot—The (one-based) front slot number within the chassis. healthMonRxStatus—Rx threshold status indicating if threshold was crossed or no change.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family Description 21 pimNeighborIfIndex ipmr Signifies the loss of adjacency with a neighbor device. This trap is generated when the neighbor time expires and the switch has no other neighbors on the same interface with a lower IP address than itself. pimNeighborLoss pimNeighborIfIndex—The value of ifIndex for the interface used to reach this PIM neighbor.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 25 rmon alarmIndex alarmVariable alarmSampleType alarmValue alarmFallingThreshold fallingAlarm Family Description An Ethernet statistical variable has dipped below its falling threshold. The variable’s falling threshold and whether it will issue an SNMP trap for this condition are configured by an NMS station running RMON. alarmIndex—An index that uniquely identifies an entry in the alarm table.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 29 mirmonPrima- pmm rySlot mirmonPrimaryPort mirroringSlot mirroringPort mirMonErrorNi mirrorUnlikeNi Family Description The mirroring configuration is deleted due to the swapping of different NI board type. The Port Mirroring session which was active on a slot cannot continue with the insertion of different NI type in the same slot. mirmonPrimarySlot—Slot of mirrored or monitored interface.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 36 trapAbsorStamp none trapAbsorTrapId trapAbsorCounter trapAbsorTime trapAbsorptionTrap Family Description The absorption trap is sent when a trap has been absorbed at least once. trapAbsorStamp—The time stamp of the absorbed trap. trapAbsorTrapId—The trap identifier of the absorbed trap. trapAbsorCounter—The number of the iterations of the absorbed trap. trapAbsorTime—The time stamp of the last iteration.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 40 lpsTrapSwitch- bridge Name lpsTrapSwitchIpAddr lpsTrapSwitchSlice lpsTrapSwitchPort lpsTrapViolatingMac lpsTrapViolationType systemServicesDate systemServicesTime lpsViolationTrap Family Description A Learned Port Security (LPS) violation has occurred. lpsTrapSwitchName—The name of the switch. lpsTrapSwitchIpAddr—The IP address of switch. lpsTrapSwitchSlice— The physical slice number for the LPS port on which the violation occurred.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family Description 42 gmBindRuleType gmBindRuleVlanId gmBindRuleIPAddress gmBindRuleMacAddress gmBindRulePortIfIndex gmBindRuleProtoClass gmBindRuleEthertype gmBindRuleDsapSsap vlan Occurs whenever a binding rule which has been configured gets violated. gmBindRuleViolation gmBindRuleType—Type of binding rule for which trap sent. gmBindRuleVlanId—Binding Rule VLAN Id. gmBindRuleIPAddress—Binding Rule IP address.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 48 pethPsePortmodule PowerMaintenanceStatus pethPsePortPowerMaintenanceStatus Family Description Indicates the status of the power maintenance signature for inline power. pethPsePortPowerMaintenanceStatus—The value ok (1) indicates the Power Maintenance Signature is present and the overcurrent condition has not been detected. The value overCurrent (2) indicates an overcurrent condition has been detected.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family Description 55 alaStackMgrSlotNINumber chassis The element identified by alaStackMgrSlotNINumber will enter the pass through mode because its operational slot was cleared with immediate effect. alaStackMgrClearedSlotTrap alaStackMgrSlotNINumber—Numbers allocated for the stack NIs as follows: - 0: invalid slot number - 1..8: valid and assigned slot numbers corresponding to values from the entPhysicalTable - 1001..
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family Description 60 traplnkaggId traplnkaggPortIfIndex linkaggregation Indicates the link aggregate is active. This trap is sent when any one port of the link aggregate group goes into the attached state. linkaggregation Indicates the link aggregate is not active. This trap is sent when all ports of the link aggregate group are no longer in the attached state.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 66 mirmonPrima- pmm rySlot mirmonPrimaryPort monitorFileName monitorFileSize monitorFileWritten Family Description A File Written Trap is sent when the amount of data requested by the user has been written by the port monitoring instance. mirmonPrimarySlot—Slot of mirrored or monitored interface. mirmonPrimaryPort—Port of mirrored or monitored interface.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 94 lldptatsRemTa- aip blesInserts lldptatsRemTablesDeletes lldptatsRemTablesDrops lldptatsRemTablesAgeouts lldpRemTablesChange Family Description This trap is sent when the value ofthe LLDP Stats Rem Table Last ChangeTime changes. It can be utilized by an NMS to trigger LLDP remote systems table maintenance polls.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 97 ipmr alaPimGroupMappingPimMode alaPimInvalidRegisterAddressType alaPimInvalidRegisterOrigin alaPimInvalidRegisterGroup alaPimInvalidRegisterRp alaPimInvalidRegister Family Description This trap is sent when an invalid PIM Register message is received. The notification is generated whenever the PIM Invalid Register Message Reveived counter is incremented, subject to the rate limit specified by the Invalid Register NotificationPeriod.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects 99 ipmr alaPimGroupMappingPimMode alaPimGroupMappingPrecedence alaPimRPMappingChange Family Description This trap is sent when a change is detected to the active RP mapping on the device. The notification is generated whenever the PIM RP Mapping Change Count is incremented, subject to the rate limit specified by PIM RP Mapping Change Notification Period alaPimGroupMappingPimMode—The PIM mode used for groups in this group prefix.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family 106 healthMonIpcTrap healthhealth MonIpcPoolStatus Description This trap is sent when IPC Pools exceed usage. healthMonIpcPoolStatus—The IPC Pools usage status. 107 bcmHashCollisionTrap ? eth This trap is sent when ? bcmHashCollisionTrap—The ? 108 healthMonCpuShutPortTrap healthModule- health Slot ifIndex healthModuleCpuLatest This trap is sent when port is shut down because of a CPU spike.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family 119 dot3OamThresholdEvent dot3OamEvent dot3-oam LogTimestamp dot3OamEvent LogOui dot3OamEvent LogType dot3OamEvent LogLocation dot3OamEvent LogWindowHi dot3OamEvent LogWindowLo dot3OamEvent LogThresholdHi dot3OamEvent LogThresholdLo dot3OamEvent LogValue dot3OamEvent LogRunningTotal dot3OamEvent LogEventTotal Description This trap is sent when a local or remote threshold crossing event is detected.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family Description 120 dot3OamNonThresholdEvent dot3OamEvent LogTimestamp dot3OamEvent LogOui dot3OamEvent LogType dot3OamEvent LogLocation dot3OamEvent LogEventTotal dot3-oam This trap is sent when a local or remote non-threshold crossing event is detected.
SNMP Trap Information No. Trap Name SNMP Traps Table Objects Family Description dot3OamEventLogTimestamp—The sysUpTime at the time of the logged event. dot3OamEventLogOui—The OUI of the entity defining the object type. All IEEE 802.3 defined events (as appearing in [802.3ah] except for the Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of 0x0180C2. Organizations defining their own Event Notification TLVs include their OUI in the Event Notification TLV that is reflected here.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects Family Description 147 alaHashCollisionTrap ifIndex, ddmNotificationType ddmRxOpticalPower port This trap is sent when an SFP/ XFP/SFP+ Rx optical power has crossed any threshold or reverted from previous threshold violation for a port represented by ifIndex. It also provides the current realtime value of SFP/XFP/SFP+ Rx optical power. ifIndex—The interface index.
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family 153 alaErpRingPortStatusChanged alaErpRingId, bridge alaErpRingPortIfIndex, alaErpRingPortStatus Description This trap is sent when the ring port status is changed. alaErpRingId—The Ring identifier that is unique in the bridge. alaErpRingPortIfIndex—The interface index - either a bridge port, or an aggregated link within a bridge port, to which ring port is configured. alaErpRingPortStatus—The status of the ring port.
SNMP Traps Table No. Trap Name SNMP Trap Information Objects Family Description alaTestOamConfigTestId—A unique name to identify the entries in the table. alaTestOamConfigSourceEndpoint—The the local or transmitting switch. For bidirectional test, this also identifies the analyzer switch. alaTestOamConfigTestIdStatus—The test status (not started, running, stopped, ended).
SNMP Trap Information SNMP Traps Table No. Trap Name Objects Family 169 alaSaaEthIterationCompleteTrap alaSaaCtrlOwn- system erIndex, alaSaaCtrlTestIndex, alaSaaEthoamResultsTestRunIndex, alaSaaCtrlLastRunResult, alaSaaCtrlLastRunTime Description This trap is sent is sent when a Eth-LB or Eth-DMM SAA iteration is completed. alaSaaCtrlOwnerIndex—An owner name to identify entries in the table. This is currently not supported and its value will always be the string 'USER'.
SNMP Traps Table No. Trap Name SNMP Trap Information Objects Family Description aaaHSvrIpAddress—The HIC/Rem/WebDL server's IP address. aaaHSvrRole—The HIC Server’s role. aaaHSvrName—The HIC Server’s name. 173 alaLldpTrustViolation aip agentalreadyexistonport , agentalreadyexistonotherport, chassisidsubtypemissmatch This trap is sent when there is an LLDP Trust Violation, and gives the reason for the violation. agentalreadyexistonport (1)—There is already one trust agent exists on the port.
SNMP Trap Information No. Trap Name SNMP Traps Table Objects Family Description ifIndex—The interface that was shut down due to the violation. esmPortViolationValue—The reason the interface was shut down.
SNMP Traps Table SNMP Trap Information No. Trap Name Objects 183 alaDhcpBindingDuplicateEntry iphelperDhcpSnoopingBindingMacAddre ss, iphelperDhcpSnoopingBindingVlan, iphelperDhcpSnoopingBindingIfIndex, Family Description This trap is sent to notify the user of MAC Movement in DHCPBinding Table. iphelperDhcpSnoopingBindingMacAddress—The MAC Address subindex identifying this instance. iphelperDhcpSnoopingBindingVlan—The DHCP client VLAN.
SNMP Trap Information No. Trap Name SNMP Traps Table Objects Family Description 192 Reserved 193 Reserved 194 Reserved 195 Reserved 196 Reserved 197 Reserved 198 aluLicenseManagerLicenseExpired aluLicensedAp- license manager plication aluLicenseTimeRemaining This trap is sent when the value of aluLicenseTimeRemaining becomes 0 (zero) for a demo licensed application. This notification is applicable only for temporary licenses.
SNMP Traps Table page B-32 SNMP Trap Information OmniSwitch 6250/6450 Switch Management Guide May 2012
Index B banner login 2-21 pre-login text 2-22 boot.
configuration file application examples 7-2 specifications 7-2 configuration files 5-3, 6-3 errors 7-7 configuration snapshot all command 7-12 configuration syntax check 7-8 console port 2-6 copy certified working command 5-22 copy flash-synchro command 5-28 copy running-config working command 5-17 copy working certified flash-synchro command cp command 5-34, 5-35 customer login user accounts application examples 9-7 D date 1-39, 7-4 Daylight Savings Time see DST defaults login 2-3 NTP 4-2 SNMP 3-2 startup
login banner 2-21 login settings verify information about 2-25 ls command 1-6, 1-10, 6-10 ls-r command 1-13 P Management Information Bases see MIBs MD5 authentication 3-11 memory 1-18 MIBs enterprise 3-20 industry standard 3-16 mkdir command 1-11 more command 6-18, 7-9 mv command 1-30 partition management 3-13 password command 9-10 passwords expiration 9-13 global settings 9-8 minimum length 9-12 user-configured 9-10 pre_banner.
Secure Socket Layer WebView 11-4 security SNMP 3-10 session banner command 2-21 session login-attempt command 2-23 session login-timeout command 2-23 session prompt command 6-17 session timeout command 2-23 sftp command 1-23, 2-19 sftp6 command 1-23, 1-33 SHA authentication 3-11 show command-log command 6-16 show command-log status command 6-16 show configuration status command 7-3, 7-7 show history command 6-13 show ip helper command 7-3 show microcode command 5-24, 6-10 show ntp client command 4-4 show nt
UTC 4-1 V verbose mode 7-9 vi command 1-14 W WebView 11-1 application examples 11-5 browser setup 11-2 CLI commands 11-3 defaults 11-2 disabling 11-3 enabling 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 write memory command 5-17 5-21, 5-26 Z Zmodem Index-5 1-25 OmniSwitch 6250/6450 Switch Management Guide May 2012
Index-6 OmniSwitch 6250/6450 Switch Management Guide May 2012
