Alcatel-Lucent OmniSwitch AOS Release 7 Manual
Alcatel-Lucent OmniSwitch AOS Release 7 Manual

Alcatel-Lucent OmniSwitch AOS Release 7 Manual

Switch management guide
Hide thumbs Also See for OmniSwitch AOS Release 7:
Table of Contents

Advertisement

Quick Links

Part No. 060318-10, Rev. B
March 2011
OmniSwitch AOS Release 7
Switch Management Guide
www.alcatel-lucent.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the OmniSwitch AOS Release 7 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Alcatel-Lucent OmniSwitch AOS Release 7

  • Page 1 Part No. 060318-10, Rev. B March 2011 OmniSwitch AOS Release 7 Switch Management Guide www.alcatel-lucent.com...
  • Page 2 The functionality described in this guide is subject to change without notice. Copyright © 2011 by Alcatel Internetworking, Inc.. All rights reserved. This document may not be repro- duced in whole or in part without the express written permission of Alcatel Internetworking, Inc..
  • Page 3: Table Of Contents

    Starting a Telnet Session from the Switch ...............1-8 Using Secure Shell ......................1-9 Secure Shell Components ..................1-9 Secure Shell Interface ..................1-9 Secure Shell File Transfer Protocol ..............1-9 Secure Shell Application Overview ...............1-10 Secure Shell Authentication ...................1-11 Protocol Identification ..................1-11 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 4 Using the Switch as an FTP Client .................2-15 Using Secure Shell FTP ..................2-15 Closing a Secure Shell FTP Session ..............2-16 Using TFTP to Transfer Files .................2-16 Setting the System Clock ....................2-17 Setting Date and Time ....................2-17 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 5 Performing an ISSU Upgrade ................3-25 Displaying CMM Conditions ..................3-26 Chapter 4 Using the CLI ....................... 4-1 CLI Specifications ......................4-2 CLI Overview ........................4-2 Online Configuration ....................4-2 Offline Configuration Using Configuration Files ............4-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 6 Snapshot Feature List ....................5-9 User-Defined Naming Options ................5-10 Editing Snapshot Files ..................5-10 Verifying File Configuration ..................5-12 Chapter 6 Managing Switch User Accounts ................6-1 In This Chapter ........................6-1 User Database Specifications ..................6-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 7 Switch Security Overview ....................7-3 Authenticated Switch Access ..................7-4 AAA Servers—RADIUS or LDAP ................7-4 Interaction With the User Database .................7-4 Configuring Authenticated Switch Access ..............7-6 Quick Steps for Setting Up ASA ..................7-7 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 8 Setting Up an SNMP Management Station ............9-8 SNMP Versions ......................9-8 SNMPv1 ......................9-8 SNMPv2 ......................9-9 SNMPv3 ......................9-9 Using SNMP For Switch Security ................9-10 Community Strings (SNMPv1 and SNMPv2) ............9-10 Configuring Community Strings ..............9-10 viii OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 9 Alcatel-Lucent License Agreement ................A-1 ALCATEL-LUCENT SOFTWARE LICENSE AGREEMENT ......A-1 Third Party Licenses and Notices .................. A-4 Appendix B SNMP Trap Information ..................B-1 SNMP Traps Table ......................B-2 Index ........................Index-1 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 10 Contents OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 11: About This Guide

    About This Guide This OmniSwitch AOS Release 7 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 switches. These features are used when readying a switch for integration into a live network environ- ment.
  • Page 12: Who Should Read This Manual

    The CLI, including on-line configuration, command-building help, syntax error checking, and line edit- ing. • Basic security features, such as switch access control and customized user accounts. • SNMP • Web-based management (WebView) page xii OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 13: What Is Not In This Manual

    Many chapters include tutorials or application examples that help convey how CLI commands can be used together to set up a particular feature. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page xiii...
  • Page 14: Documentation Roadmap

    Stage 3: Integrating the Switch Into a Network Pertinent Documentation: OmniSwitch AOS Release 7 Network Configuration Guide OmniSwitch AOS Release 7 Advanced Routing Configuration Guide When you are ready to connect your switch to the network, you will need to learn how the OmniSwitch implements fundamental software features, such as 802.1Q, VLANs, Spanning Tree, and network routing...
  • Page 15 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. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page xv...
  • Page 16: Related Documentation

    (authenticated VLANs), Quality of Service (QoS), link aggregation, and server load balancing. • OmniSwitch AOS Release 7 Advanced Routing Configuration Guide Includes network configuration procedures and descriptive information on all the software features and protocols included in the advanced routing software package. Chapters cover multicast routing (DVMRP and PIM-SM), Open Shortest Path First (OSPF), and Border Gateway Protocol (BGP).
  • Page 17: Technical Support

    With 24-hour access to Alcatel-Lucent’s Service and Support web page, you’ll be able to view and update any case (open or closed) that you have reported to Alcatel-Lucent’s technical support, open a new case or access helpful release notes, technical bulletins, and manuals.
  • Page 18 Technical Support About This Guide page xviii OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 19: In This Chapter

    Interface (CLI), which may be accessed locally via the console port, or remotely via Telnet; WebView, which requires an HTTP client (browser) on a remote workstation; and SNMP, which requires an SNMP manager (such as Alcatel-Lucent’s OmniVista or HP OpenView) on the remote workstation. Secure sessions are available using the Secure Shell interface.
  • Page 20: Chapter 1 Logging Into The Switch

    Inactivity time-out period. The session timeout 4 minutes length of time the switch can remain idle during a login session before the switch will close the session. page 1-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 21: Quick Steps For Logging Into The Switch

    For information about changing the login prompt, see Chapter 4, “Using the CLI.” For information about setting up additional user accounts locally on the switch, see Chapter 6, “Managing Switch User Accounts.” OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-3...
  • Page 22: Overview Of Switch Login Components

    For more information about using Telnet to access the switch, see “Using Telnet” on page 1-8. • Secure Shell—Any standard Secure Shell client may be used for remote login to the switch. See “Using Secure Shell” on page 1-9. page 1-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 23: Using The Webview Management Tool

    The user information includes usernames and passwords; it may also include privilege information or reference an end-user profile name. For information about setting up the switch to communicate with external authentication servers, see the OmniSwitch AOS Release 7 Network Configuration Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 24: Configuring The Console Port

    • If you use the commit system command only, changes will not be saved to the switch's non-volatile memory and will be lost if the switch is rebooted. page 1-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 25: Setting The Emp Port's Ip Address

    Boot > exit • If you use the commit system command only, changes will not be saved to the switch's non-volatile memory and will be lost if the switch is rebooted. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-7...
  • Page 26: Using Telnet

    Welcome to the Alcatel-Lucent OS10K Software Version 7.1.1.733.R01 Development, August 05, 2010. Copyright(c), 1994-2010 Alcatel-Lucent. All Rights reserved. OmniSwitch(TM) is a trademark of Alcatel-Lucent registered in the United States Patent and Trademark Office. page 1-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 27: Using Secure Shell

    Secure Shell FTP subsystem runs. Secure Shell FTP connects and logs into the specified host, then enters an interactive command mode. Refer to “Starting a Secure Shell Session from the OmniSwitch” on page 1-13 for detailed information. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-9...
  • Page 28: Secure Shell Application Overview

    Secure Shell software is used on the connecting switch and the server portion of Secure Shell is used on the switches or servers being managed. Secure Shell Access Protocol Secure Shell Network OmniSwitch Secure Secure Shell Terminal Shell Client Server OmniSwitch as a Secure Shell Client page 1-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 29: Secure Shell Authentication

    To generate a different key, use the Secure Shell tools available on your Unix or Windows system and copy the files to the OmniSwitch. The new keys will take effect after the OmniSwitch is rebooted. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-11...
  • Page 30: Authentication Phase

    Install the public key on the OmniSwitch for the specified user. -> installsshkey new_ssh_user /flash/system/new_ssh_user_rsa.pub page 1-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 31: Revoking A Key

    Copyright (c) 1994-2010 Alcatel-Lucent. All Rights Reserved. OmniSwitch(tm) is a trademark of Alcatel-Lucent, registered in the United States Patent and Trademark Office. Once the Secure Shell session is established, you can use the remote device specified by the IP address on a secure connection from your OmniSwitch.
  • Page 32: Modifying The Login Banner

    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 http banner/flash/switch/thirdbanner.txt page 1-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 33: Modifying The Text Display Before Login

    To remove a text display before the login prompt, delete the pre_banner.txt file (it will be recreated at the next bootup and will be empty), or modify the pre_banner.txt file. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-15...
  • Page 34: Configuring Login Parameters

    For example: -> session cli timeout 8 -> session ftp timeout 5 -> session http timeout 10 page 1-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 35: Enabling The Dns Resolver

    Displays the current DNS resolver configuration and status. For more information about these commands, refer to the OmniSwitch CLI Reference Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 1-17...
  • Page 36 Verifying Login Settings Logging Into the Switch page 1-18 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 37: Chapter 2 Managing System Files

    “Setting the System Clock” on page 2-17 For related information about connecting a terminal to the switch, see your Getting Started Guide. For information about switch command privileges, see Chapter 7, “Managing Switch Security.” OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-1...
  • Page 38: File Management Specifications

    Additional user-defined directories created in the /flash directory. Text Editing Standard Vi standard editor. System Clock Set local date, time and time zone, Universal Time Coordinate (UTC), Daylight Savings (DST or summertime). page 2-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 39: Switch Administration Overview

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

    Listing Directory: /flash Directory: /flash/certified Directory: /flash/network (Files) swlog.0 (Files) (Files) swlog.1 Directory: /flash/working (Files) Switch Flash Directory page 2-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 41: File And Directory Management

    To list all the files and directories in your current directory, use the command. Here is a sample display of the flash directory. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-5...
  • Page 42 1024 Aug 30 18:28 switch -rw-r--r-- 1 root 51569 Aug 30 22:52 swlog drwxr-xr-x 2 root 1024 Aug 30 18:28 system drwxrwxrwx 2 root 1024 Aug 30 18:28 dir1 page 2-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 43: Directory Commands

    The display shows the name of the current directory and its path. If your current directory is the certified directory and you enter the command, the following will be displayed: -> pwd /flash/certified -> The display shows the path to your current directory. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-7...
  • Page 44: Changing Directories

    In this example, a copy of the dir1 directory and all its contents will be created in the /flash directory. ->cp -r /flash/dir1 /flash/dir2 page 2-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 45: Removing A Directory And Its Contents

    A copy of all the image files will appear in the /flash/working direc- tory of the remote switch, once the following command is executed. -> scp /flash/working/*.img admin@198.51.100.1:/flash/working admin's password for keyboard-interactive method: OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-9...
  • Page 46: Move An Existing File Or Directory

    If you are in another directory, you must specify the path and name for the file being deleted. For example: -> rm /flash/config.txt page 2-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 47: Managing Files On Redundant Cmms

    64000 Sep 13 16:46 swlog.0 64000 8 21:24 swlog.1 1024 Sep 13 16:45 switch/ 1024 Sep 10 17:34 network/ Sep 13 16:41 random-seed 1024 Jun 22 1986 tk.dir/ OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-11...
  • Page 48: Utility Commands

    While performing the repair operation, the switch will display the errors found and specify those errors that have been repaired. If there are no errors found, then just the file system information is displayed. page 2-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 49: Deleting The Entire File System

    Caution. This command will delete all of the switch’s system files. All configurations programmed into the switch will be lost. Do not use this command unless you are prepared to reload all files. OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 50: Loading Software Onto The Switch

    IP address of your switch. Where the FTP client asks for “User ID”, enter the username of your login account on the switch. Where the FTP client asks for “Password”, enter your switch password. page 2-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 51: Using The Switch As An Ftp Client

    CLI command. The command syntax requires you to identify the IP address for the device you are connecting to. The following command establishes a Secure Shell FTP interface from the local OmniSwitch to IP address 198.51.100.125. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-15...
  • Page 52: Closing A Secure Shell Ftp Session

    A TFTP server does not prompt for a user to login and only one active TFTP session is allowed at any point of time. Note. When downloading a file to the switch, the file size must not exceed the available flash space. page 2-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 53: Setting The System Clock

    To modify the switch’s current system time, enter the system time command. When you specify the time you must use the hh:mm:ss syntax where hh is the hour based on a 24 hour clock. The mm syntax repre- OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 54: Daylight Savings Time Configuration

    2-19 to determine daylight savings time settings. Enable DST on your switch by using the following command: -> system daylight-savings-time Note. By default, Daylight Savings Time is disabled. page 2-18 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 55: Enabling Dst

    West Africa -01:00 No default No default No default No standard name -02:00 No default No default No default No standard name -03:00 No default No default No default OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 2-19...
  • Page 56 Last Sunday in Oct. 1:00 2:00 a.m. at 2:00 a.m. Hawaii -10:00 No default No default No default zm11 No standard name -11:00 No default No default No default page 2-20 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 57: Managing Cmm Directory Content

    Managing, upgrading and restoring files using a USB flash drive described in “Using the USB Flash Drive” on page 3-22. • Upgrading switch code using ISSU described in “In-Service Software Upgrade” on page 3-24. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-1...
  • Page 58: Cmm Specifications

    Disaster Recovery Supported (rescue.img file required) Note. The format of the Alcatel-Lucent certfied USB Flash Drive must be FAT32. To avoid file corrup- tion issues the USB Drive should be stopped before removing from a PC. Directory names are case sensi- tive and must be lower case.
  • Page 59: Cmm Files

    The management of a switch is controlled by three types of files: • Image files, which are proprietary code developed by Alcatel-Lucent. These files are not configurable by the user, but may 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 together under a common head- ing.
  • Page 60: Where Is The Switch Running From

    Should the configuration or images files prove to be less reliable than their older counterparts in the certi- fied directory, then the switch can be rebooted from the certified directory, and “rolled back” to an earlier version. page 3-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 61: Software Rollback Configuration Scenarios

    Running Configuration is Overwritten by the Certified Directory on Reboot OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-5...
  • Page 62 Running Configuration Saved to Working Directory page 3-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 63 Running Configuration is Saved to Working Directory, then to the Certified Directory OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-7...
  • Page 64 Switch Rolls Back to Previous Software Version page 3-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 65: Redundancy

    After changes to the configuration and image files are saved to the working directory, sometimes it is necessary to boot from the working directory to check the validity of the new files. The following diagram illustrates the synchronization process of a working directory reboot. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-9...
  • Page 66 RUNNING-DIRECTORY is described in “Copying the RUNNING DIRECTORY to the Certified Direc- tory” on page 3-16, while synchronizing the switch is described in “Synchronizing the Primary and Secondary CMMs” on page 3-19. page 3-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 67 Note. It is important to certify the CMMs as soon as the validity of the software is established. Unsynchro- nized CMMs are at risk of mismanaging data traffic due to incompatibilities in different versions of switch software. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-11...
  • Page 68: Managing Switch Configurations - Single Cmm

    This command loads the image and configuration files in the certified directory into the RAM memory. Note. When the switch reboots it will boot from the certified directory. Any information in the RUNNING CONFIGURATION that has not been saved will be lost. page 3-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 69 -> reload all cancel 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 OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-13...
  • Page 70: Saving The Running Configuration

    To change the running directory to a directory other than the certified use the modify running-directory command as shown and then save the configuration with the write memory command: -> modify running-directory user-config1 -> write memory page 3-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 71: Rebooting From A Directory

    -> reload from working rollback-timeout 10 at 20:00 Cancelling a Rollback Timeout To cancel a rollback time-out, enter the reload cancel command as shown: -> reload cancel OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-15...
  • Page 72: Copying The Running Directory To The Certified Directory

    “Where is the Switch Running From?” on page 3-4. for additional information. To check the directory from where the switch is currently running, enter the following command: -> show running-directory page 3-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 73: Show Switch Files

    Description -----------------+---------------+--------+----------------------------------- Ros.img 7.1.1.311.R01 2486643 Alcatel-Lucent OS Reni.img 7.1.1.311.R01 941331 Alcatel-Lucent NI If no directory is specified, the files that have been loaded into the running configuration are shown. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-17...
  • Page 74: Managing Cmm Redundancy

    CMM takes the place of the primary CMM. This prevents the switch from ceasing functionality during the boot process. Synchronizing the primary and secondary CMMs is done using the copy flash-synchro command described in “Synchronizing the Primary and Secondary CMMs” on page 3-19. page 3-18 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 75: Synchronizing The Primary And Secondary Cmms

    To just synchronize the secondary CMM to the primary CMM, enter the following command at the prompt: -> copy flash-synchro copy flash-synchro command is described in detail in the OmniSwitch CLI Reference Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-19...
  • Page 76: Swapping The Primary Cmm For The Secondary Cmm

    OmniSwitch CLI Reference Guide. Note. The saved boot.cfg file will be overwritten if the takeover command is executed after the copy flash-synchro command on a switch set up with redundant CMMs. page 3-20 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 77: Show Currently Used Configuration

    Certify/Restore Status : CERTIFY NEEDED SYNCHRONIZATION STATUS Flash Between CMMs : SYNCHRONIZED, Running Configuration : NOT AVAILABLE, show running-directory command is described in detail in the OmniSwitch CLI Reference Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-21...
  • Page 78: Using The Usb Flash Drive

    Using the USB Flash Drive An Alcatel-Lucent certified USB flash drive can be connected to the CMM and used to transfer images to and from the flash memory on the switch. This can be used for upgrading switch code, backing up files or recovering a failed CMM.
  • Page 79: Disaster Recovery Using A Usb Flash Drive

    Connect the USB flash drive to the CMM and reboot. The switch will automatically stop and display the option to perform a disaster recovery. Enter the ‘run rescue’ command and follow the recovery prompts. Once complete, the CMM will reboot and be operational again. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-23...
  • Page 80: In-Service Software Upgrade

    NIs can be manually reset one right after the other. However, it’s recommended to wait until the previous NI is operational before resetting the next NI. • No configuration is allowed until the entire ISSU upgrade process is complete, including NI reset. page 3-24 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 81: Performing An Issu Upgrade

    Reset the individual NIs using the issu slot command. Enter ‘copy running certified flash-synchro’ to certify the configuration. Verify the status of the ISSU upgrade using the show issu status command. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 3-25...
  • Page 82: Displaying Cmm Conditions

    Displays microcode versions installed on the switch. Enables access to the device connected to the USB port. For more information on the resulting displays from these commands, see the OmniSwitch CLI Reference Guide. page 3-26 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 83: Chapter 4 Using The Cli

    4 Using the CLI Alcatel-Lucent’s 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 CLI Reference Guide. All command descriptions listed in the Reference Guide include command syntax definitions, defaults, usage guidelines, example screen output, and release history.
  • Page 84: Cli Specifications

    CLI configuration commands can be typed into a generic text file. When the text file is placed on the switch its commands are applied to the switch when the configuration apply command is issued. Files used in this manner are called configuration files. page 4-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 85: Command Entry Rules And Syntax

    Indicates basic command and keyword syntax. Example: show snmp station “ ” (Quotation Marks) Used to enclose text strings that contain spaces Example: vlan 2 name “new test vlan” OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 4-3...
  • Page 86: Using "Show" Commands

    In this case, pressing Tab will cause the CLI to complete the common prefix and place the cursor at the end of the prefix. Note that in this case, no space is placed at the end of the keyword. page 4-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 87: Command Help

    To issue the command, press Enter. -> ls The !! (bang, bang) command will display the last command line entered and automatically run the command. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 4-5...
  • Page 88: Inserting Characters

    “bang”. To recall the command shown in the history list at number 4, enter !4 (bang, 4). The CLI will respond by printing the number four command at the prompt. Using the history list of commands above, the following would display: -> !4 -> show ip interface page 4-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 89: Logging Cli Commands And Entry Results

    All commands logged before the command-log disable syntax was entered remains available for viewing. For information on viewing logged commands, along with the command entry results, refer to “Viewing Logged CLI Commands and Command Entry Results” on page 4-8. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 4-7...
  • Page 90: Viewing The Current Command Logging Status

    SUCCESS displays in the Result field. If a syntax or configuration error occurred at the time a command was entered, details of the error display. For example: Result : ERROR: Ip Address must not belong to IP VLAN 67 subnet page 4-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 91: Customizing The Screen Display

    -> to ##=> use the session prompt command as follows: -> -> session prompt default ##=> ##=> The switch displays the new prompt string after the command is entered. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 4-9...
  • Page 92: Verifying Cli Usage

    For more information about the resulting displays from these commands, see the OmniSwitch CLI Refer- ence Guide. Additional information can also be found in “Using “Show” Commands” on page 4-4. page 4-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 93: Chapter 5 Working With Configuration Files

    “Applying Configuration Files to the Switch” on page 5-6 • “Configuration File Error Reporting” on page 5-7 • “Text Editing on the Switch” on page 5-8 • “Creating Snapshot Configuration Files” on page 5-9 OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-1...
  • Page 94: Working With Configuration Files

    The display is similar to the one shown here: -> show configuration status File syntax check <text.txt>: completed with no errors Error file limit: 1 Running configuration and saved configuration are different page 5-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 95 Bootup Option = Disable Forwarding address list (Standard mode): 192.168.10.10 These results confirm that the commands specified in the file dhcp_relay.txt configuration file were successfully applied to the switch. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-3...
  • Page 96: Quick Steps For Applying Configuration Files

    Error file limit: 1 Apply the file by executing the configuration apply using the at keyword with the relevant date and time. -> configuration apply bncom_cfg.txt at 09:00 july 4 page 5-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 97: Setting An Application Session For A Specified Time Period

    The “scheduled at” date and time show when the file will be applied. This value is 6 hours and 15 minutes from the date and time the command was issued. For more information about this display see “Configuration File Manager Commands” in the OmniSwitch CLI Reference Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-5...
  • Page 98: Configuration Files Overview

    The following displays where the timed session was set on March 10, 2002 at 01:00 using the configuration apply group_config in 6:10 syntax. -> show configuration status File configuration <group_config>: scheduled at 03/10/02 07:10 page 5-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 99: Cancelling A Timed Session

    To run a syntax check on a configuration file, use the configuration syntax-check command. For example: -> configuration syntax asc.1.snap Errors: 3 Log file name: check asc.1.snap.1.err OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-7...
  • Page 100: Text Editing On The Switch

    Invoke the “Vi” Editor You can invoke the Vi editor from the command line. Use the following syntax to view the switchlog.txt file located in the /flash/working directory: -> vi /flash/working switchlog.txt page 5-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 101: Creating Snapshot Configuration Files

    You may enter more than one network feature in the command line. Separate each feature with a space (and no comma). The following command will generate a snapshot file listing current configurations for the vlan, qos, and snmp command families. -> configuration snapshot vlan qos snmp OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-9...
  • Page 102: User-Defined Naming Options

    ! SNMP : snmp security no security snmp community map mode off ! IP route manager : ip static-route 0.0.0.0 mask 0.0.0.0 gateway 10.255.211.65 metric 1 ! RIP : page 5-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 103 Bridging services. Each of these services have configuration commands listed under their heading. All other switch services and applications are either not being using or are using default settings. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 5-11...
  • Page 104: Verifying File Configuration

    A snapshot is a sin- gle text file that can be viewed, edited, and reused as a configuration file. write terminal Displays the switch’s current running configuration for all features. page 5-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 105: Managing Switch User Accounts

    User information may also be configured on external servers in addition to, or instead of, user accounts configured locally on the switch. For information about setting up external servers that are configured with user information, see the “Managing Authentication Servers” chapter in the OmniSwitch AOS Release 7 Network Configuration Guide.
  • Page 106: User Database Specifications

    Maximum number of old passwords user password-history to retain in the password history. Minimum number of days user is user password-min-age 0 (disabled) blocked from changing password. page 6-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 107 Maximum number of failed login user lockout-threshold 0—no limit to the num- attempts allowed during the lockout ber of failed login window time period. attempts OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-3...
  • Page 108: Overview Of User Accounts

    Note. For information about setting up user information on an authentication (AAA) server, see the “Managing Authentication Servers” chapter of the OmniSwitch AOS Release 7 Network Configuration Guide. Users typically log into the switch through one of the following methods: •...
  • Page 109 Typically, options for the user are configured at the same time the user is created. An example of creating a user and setting access privileges for the account is given here: -> user thomas password techpubs read-write domain-policy OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-5...
  • Page 110: Quick Steps For Network Administrator User Accounts

    = None, Read/Write for domains = Network , Snmp allowed = NO Console-Only = Disabled For more information about the show user command, see the OmniSwitch CLI Reference Guide. page 6-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 111: Default User Settings

    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). OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-7...
  • Page 112 Overview of User Accounts Managing Switch User Accounts Note. Password settings configured through the user password-policy commands are not automatically saved to the switch configuration. page 6-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 113: Creating A User

    -> password enter old password: Enter the old password. (The password is concealed with asterisks.) A prompt displays for the new password. -> password enter old password:******** enter new password: OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-9...
  • Page 114 ********* reenter new password: ********* -> The password is now reset for the current user. At the next switch login, the user must enter the new pass- word. page 6-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 115: Configuring Password Policy Settings

    For example, the password for the account username of public can not contain the word public in any part of the password. However, the username of another account is still allowed. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-11...
  • Page 116: Configuring Password Character Requirements

    20 days, that user’s password will expire in 10 days. To disable the default password expiration, use the user password-expiration command with the disable option: -> user password-expiration disable page 6-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 117: Specific User Password Expiration

    -> user password-min-age 7 This command specifies that the user is prevented from changing their password for seven days from the time the password was created or modified. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-13...
  • Page 118: Configuring Global User Lockout Settings

    30 minutes and the threshold number is set for 3 failed login attempts, then the user is locked out when 3 failed login attempts occur within a 30 minute time frame. page 6-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 119: Configuring The User Lockout Duration Time

    6-15) is not configured for the switch, then it is only possible to manually unlock a user account with the user lockout command or by changing the user password. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-15...
  • Page 120: Configuring Privileges For A User

    Note. When modifying an existing user, the user password is not required. If you are configuring a new user with privileges, the password is required. The default user privileges may also be modified. See “Default User Settings” on page 6-7. page 6-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 121: Setting Up Snmp Access For A User Account

    To give a user SNMP access without SNMP authentication required, enter the user command with the no auth option. For example, to give existing user thomas SNMP access without SNMP authentication, enter the following: -> user thomas password techpubs no auth OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-17...
  • Page 122: Snmp Access With Authentication/Encryption

    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. page 6-18 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 123: Multiple User Sessions

    The other sessions are identi- fied by session number, user name, the type of access, port type, IP address, and user privileges. OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 124: Listing Your Current Login Session

    The command syntax requires you to specify the number of the session you want to kill. You can use the who command for a list of all current user sessions and their numbers. The kill command takes effect immediately. page 6-20 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 125: Verifying The User Configuration

    For more information about the resulting displays from these commands, see the OmniSwitch CLI Refer- ence Guide. An example of the output for the show user command is also given in “Quick Steps for Network Administrator User Accounts” on page 6-6. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 6-21...
  • Page 126 Verifying the User Configuration Managing Switch User Accounts page 6-22 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 127: Chapter 7 Managing Switch Security

    “Managing Authentication Servers” chapter in the Network Configuration Guide. This chapter describes how to enable/disable access for management interfaces. For information about basic login on the switch, see Chapter 1, “Logging Into the Switch.” OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-1...
  • Page 128: Switch Security Defaults

    Access to managing the switch is always available for the admin user through the console port, even if management access to the console port is disabled for other users. Description Command Default Console Access aaa authentication Enabled Remote Access aaa authentication Disabled page 7-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 129: Switch Security Overview

    “Configuring Accounting for ASA” on page 7-11. For complete details about local logging, see the “Using Switch Logging” chapter in the Network Configuration Guide. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-3...
  • Page 130: Authenticated Switch Access

    The admin user is always authorized through the console port via the local database (provided the correct password is supplied), even if access to the console port is disabled. page 7-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 131 The database may be set up by the admin user or any user with write privileges to the AAA commands. Chapter 6, “Managing Switch User Accounts,” for more information about setting up the user data- base. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-5...
  • Page 132: Configuring Authenticated Switch Access

    Configuring the management interface and specifying the servers and/or local user database to be used for the interface. aaa accounting session Optional. Specifies servers to be used for accounting. page 7-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 133: Quick Steps For Setting Up Asa

    Specify an accounting server if a RADIUS or LDAP server will be used for accounting. Specify local if accounting may be done on the switch through the Switch Logging feature. Multiple servers may be specified as backups. -> aaa accounting session ldap2 local OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-7...
  • Page 134 Service type = Ssh Authentication = Use Default, 1rst authentication server = rad1 2nd authentication server = local For more information about this command, see the OmniSwitch CLI Reference Guide. page 7-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 135: Setting Up Management Interfaces For Asa

    To disable authenticated access for a management interface use the no form of the command with the keyword for the interface. For example: -> no aaa authentication ftp OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-9...
  • Page 136: Configuring The Default Setting

    The default keyword may also be used to reset a specified interface to the default interface setting. For example: -> aaa authentication ftp default In this example, FTP users will now be authenticated through the servers that are specified for the default interface. page 7-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 137: Configuring Accounting For Asa

    To disable accounting for Authenticated Switch Access, use the no form of the aaa accounting session command: -> no aaa accounting session Accounting will not be performed for Authenticated Switch Access sessions. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 7-11...
  • Page 138: Verifying The Asa Configuration

    For more information about the resulting displays from these commands, see the OmniSwitch CLI Refer- ence Guide. An example of the output for the show aaa authentication command is also given in “Quick Steps for Setting Up ASA” on page 7-7. page 7-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 139: Chapter 8 Using Webview

    8 Using WebView The switch can be monitored and configured using WebView, Alcatel-Lucent’s web-based device management tool. The WebView application is embedded in the switch and is accessible via the following web browsers: In This Chapter This chapter provides an overview of WebView and WebView functionality, and includes information about the following procedures: •...
  • Page 140: Webview Cli Defaults

    Typically many of these settings are configured as the default. Different browsers (and different versions of the same browser) may have different dialogs for these settings. Check your browser help pages if you need help. page 8-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 141: Webview Cli Commands

    Note. All WebView sessions must be terminated before the switch accepts the command. For example: -> webview https-port 20000 To restore an HTTPS port to its default value, use the default keyword as shown below: -> webview https-port default OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 8-3...
  • Page 142: Quick Steps For Setting Up Webview

    • Feature Options—Used to access specific configuration options for each feature (displayed in drop- down menus at the top of the page). • View/Configuration Area—Used to view/configure a feature. page 8-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 143: Banner

    After logging into WebView, a real-time graphical representation of the switch displays all of the switch’s current components. The feature configuration options on this page are used to config- ure the switch. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 8-5...
  • Page 144 WebView Overview Using WebView page 8-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 145: Chapter 9 Using Snmp

    “Using SNMP For Switch Security” on page 9-10 • “Working with SNMP Traps” on page 9-13 This chapter also includes lists of Industry Standard and Enterprise (Proprietary) MIBs used to manage the OmniSwitch. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-1...
  • Page 146: Snmp Specifications

    SNMP Security setting snmp security Privacy all (highest) security Trap filtering snmp-trap filter-ip Disabled Trap Absorption snmp-trap absorption Enabled Enables the forwarding of traps to snmp-trap to-webview Enabled WebView. page 9-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 147 Using SNMP SNMP Defaults Parameter Description Command Default Value/Comments Enables or disables SNMP snmp authentication-trap Disabled authentication failure trap forwarding. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-3...
  • Page 148: Quick Steps For Setting Up An Snmp Management Station

    ---------------------------------------------------+---------+--------+------ 172.21.160.32/4000 enable 172.21.160.12/5000 enable user1 0300:0000:0000:0000:0211:d8ff:fe47:470b/4001 enable user2 0300:0000:0000:0000:0211:d8ff:fe47:470c/5001 enable For more information about this display, see the “SNMP Commands” chapter in the OmniSwitch CLI Reference Guide. page 9-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 149: Quick Steps For Setting Up Trap Filters

    -> show snmp station ipAddress/udpPort status protocol user ---------------------------+---------+--------+------------------------------- 210.1.2.1/162 enable usermark2 The usermark2 account is established on the SNMP station at IP address 210.1.2.1. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-5...
  • Page 150: Filtering By Individual Traps

    For trap numbers refer to the “Using SNMP For Switch Security” on page 9-10. For more information on the CLI commands and the displays in these examples, refer to the OmniSwitch CLI Reference Guide. page 9-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 151: Snmp Overview

    In an unsolicited notification, the SNMP agent in the switch sends a trap PDU to the SNMP manager to inform it that an event has occurred. The SNMP manager normally does not send confirmation to the agent acknowledging receipt of a trap. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-7...
  • Page 152: Using Snmp For Switch Management

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

    Encryption—Scrambling the contents of a packet to prevent it from being learned by an unauthorized source. • Authentication—Determining that the message is from a valid source holding the correct privileges. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-9...
  • Page 154: Using Snmp For Switch Security

    The display is similar to the one shown here: ->show snmp community map Community mode : enabled status community string user name --------+--------------------------------+-------------------------------- enabled comstring2 community_user1 This display also verifies that the community map mode is enabled. page 9-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 155: Encryption And Authentication (Snmpv3)

    Write for domains = None , Snmp authentication = MD5, Snmp encryption = DES The user’s SNMP authentication is shown as MD5 and SNMP encryption is shown as DES. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-11...
  • Page 156: Setting Snmp Security

    Encrypted v3 Sets, Gets, and Get-Nexts privacy set Authenticated v3 Gets and Get-Nexts Encrypted v3 Sets, Gets, and Get-Nexts privacy all Encrypted v3 Sets, Gets, and Get-Nexts traps only All SNMP requests are rejected. page 9-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 157: Working With Snmp Traps

    “Filtering by Individual Traps” on page 9-6. For a list of trap names, ID numbers, and their descriptions refer to the table “Using SNMP For Switch Security” on page 9-10. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-13...
  • Page 158: Authentication Trap

    When WebView forwarding is enabled, all traps sent by switch applications are also forwarded to WebView. The following command allows a WebView session to retrieve the trap history log: -> snmp trap to webview enable page 9-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 159: Snmp Mib Information

    For MIB Id number 87042, the MIB table name is vacmContextTable. This table is found in the SNMP-VIEW-BASED-ACM MIB, which serves as the view-based access control model (VACM) for the SNMP. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 9-15...
  • Page 160: Verifying The Snmp Configuration

    Enabled/Disabled status of SNMP absorption and the Traps to WebView service. For more information about the resulting displays from these commands, see the OmniSwitch CLI Refer- ence Guide. page 9-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 161: Configuring Network Time Protocol (Ntp)

    Selecting an NTP server for the NTP client and modifying settings for communicating with the server. “NTP Servers” on page 10-10. • Enabling authentication in NTP negotiations. See “Using Authentication” on page 10-12. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 10-1...
  • Page 162: Chapter 10 Configuring Network Time Protocol (Ntp)

    Used to activate client ntp client disabled Used to activate NTP client ntp src-ip preferred disabled broadcast mode Used to set the advertised broadcast ntp broadcast-delay 4000 microseconds delay, in microseconds page 10-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 163: Ntp Quick Steps

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

    Protocols that do this include NTP. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 10-5...
  • Page 166: Stratum

    Omniswitch to establish an active peering relationship with another server, enable broadcast server functionality, disable a given IP for NTP and employ MD5 authentication for clients and active peers. page 10-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 167 This minimizes common points of failure. OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 168: Authentication

    MD5 key written as a 1 to 31 character ASCII string with each character standing for a key octet. The key file (with identical MD5 keys) must be located on both the local NTP client and the client’s server. page 10-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 169: Configuring Ntp

    NTP hosts. The correct time is determined from an NTP message based on a pre-config- ured latency or broadcast delay in the order of a few milliseconds. To set the broadcast delay, enter the ntp broadcast-delay command as shown: -> ntp broadcast-delay 1000 OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 10-9...
  • Page 170: Ntp Servers

    For example, to set the minimum poll time to 128 seconds, enter the following: -> ntp server 1.1.1.1 minpoll 7 This would set the minimum poll time to 2 = 128 seconds. page 10-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 171 To specify an NTP as preferred, use the ntp server command with the server IP address (or domain name) and the prefer keyword, as shown: -> ntp server 1.1.1.1 prefer OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 10-11...
  • Page 172: Using Authentication

    A key can be set to untrusted status by using the ntp key command with the untrusted keyword. For example, to set key ID 5 to untrusted status, enter the following: -> ntp key 5 untrusted page 10-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 173: Verifying Ntp Configuration

    OmniSwitch CLI Reference Guide. Examples of the show ntp client, show ntp server status, and show ntp client server-list command outputs are given in the section “NTP Quick Steps” on page 10-3. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page 10-13...
  • Page 174 Verifying NTP Configuration Configuring Network Time Protocol (NTP) page 10-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 175: Appendix A Software License And Copyright Statements

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

    /flash/foss. Also, if needed, we provide all FOSS (Free and Open Source Software) source code used into this release at the following URL: https://service.esd.alcatel-lucent.com/portal/page/portal/EService/release page A-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 179 B SNMP Trap Information This appendix lists the supported SNMP traps along with their descriptions. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-1...
  • Page 180: Snmp Traps Table

    (1) state; it should remain in the notPresent (6) state if the interface has missing (typically, hardware) components. authenticationFailure none snmp The SNMP agent in the switch has received a protocol message that is not properly authenticated. page B-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 181 The contained and the significant portion are varying in accordance with chassisTrapsStrErrorNb. The length of this field is expressed in bytes. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-3...
  • Page 182 A packet was received from the etSrc network whose authentication vrrpTrapAuth- key conflicts with the switch’s ErrorType authentication key or type. vrrpTrapPacketSrc—The IP address of an inbound VRRP packet. vrrpTrapAuthErrorType—Potential types of configuration conflicts. page B-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 183 Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. bgpPeerState—The BGP peer connection state. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-5...
  • Page 184 IP address this system will use as a source address on this interface. On unnumbered interfaces, it must be the same value as dvmrpInterfaceLocalAddress for some interfaces on the system. dvmrpNeighborState—State of the neighbor adjacency. page B-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 185 A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm (1) or risin- gOrFallingAlarm (3). OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-7...
  • Page 186 NI slot number. mirMonError—The Error returned by the NI which failed to configure Mirroring/Monitoring. page B-8 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 187 OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-9...
  • Page 188 Indicates the link aggregate is not traplnkaggPor- gation active. This trap is sent when all tIfIndex ports of the link aggregate group are no longer in the attached state. page B-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 189 (primary for vrrp over IPv4) IP address. This is the Ip address listed as the source in the advertisement last received by this virtual switch. For IPv6, a link local address. alaVrrp3TrapNewMasterReason—This indicates the reason for NewMaster trap. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-11...
  • Page 190 Count is incremented, subject to the rate limit specified by the PIM Neighbor Loss Notification- Period. pimNeighborUpTime—The time since this PIM neighbor (last) became a neighbor of the local router. page B-12 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 191 IP multicast group address carried in the last unexpected Join/Prune mes- sage received pimInvalidJoinPruneRp—The RP address carried in the last unexpected Join/Prune message received pimNeighborUpTime—The time since this PIM neighbor (last) became a neighbor of the local router. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-13...
  • Page 192 This trap is sent when a C-BSR pimBsrCandidateBSRWinElection wins a BSR Election. dateBSRElect- edBSR pimBsrCandidateBSR ElectedBSR—Indicates whether the local router is the elected BSR for this zone. page B-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 193 MAC addresses that can be learned before a trap is sent. gvrpVlanLimitReachedEvent alaGvrpMaxV- bridge This trap is sent when the num- lanLimit of dynamically-learned VLANs has reached the config- ured limit. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-15...
  • Page 194 This trap is sent when the ERP alaErpRingState Ring State has changed from “Idle” to “Protection”. alaErpRingId—The unique Ring identifier. alaErpRingState—The current state of the Ring (0=Idle, 1=Protection). page B-16 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 195 DDM parameters (clearViolation(1), highAlarm(2), high- Warning(3), lowWarning(4), lowAlarm(5). ddmTxBiasCurrent—The current Transmit Bias Current of the SFP/XFP in 10s of milli-Amperes (mA). OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-17...
  • Page 196 ID or IPC VLAN). multiChassisTrapFailure—Indicates multi-chassis failure. multiChassisHelloIntervalConsisFail- multiChassisTra multi-chas- This trap is sent when there is an pFailure MCM Hello Interval consistency falure. multiChassisTrapFailure—Indicates multi-chassis failure. page B-18 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 197 VFLMemberPort—The multi-chassis VFL member port number. multiChassisTrapDiagnistic—The reason a port configured as virtual-fabric member is unable to join the vir- tual-fabric link - 1. Duplex Mode, 2. Speed. OmniSwitch AOS Release 7 Switch Management Guide March 2011 page B-19...
  • Page 198 SNMP Traps Table page B-20 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 199 3-19 cd command certified directory date 2-17, 5-4 copying to working directory 3-19 Daylight Savings Time Chassis Management Module see DST see CMM chmod command 2-10 OmniSwitch AOS Release 7 Switch Management Guide March 2011 Index-1...
  • Page 200 2-15 overview 10-5 FTP server 2-14 specifications 10-2 stratum 10-6 using in a network 10-6 help ntp broadcast command 10-9 HTTP ntp broadcast-delay command 10-9 web browser http port command Index-2 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 201 3-15 reload command 3-12, 3-13, 3-18 reload secondary command 3-18 reload working command 3-15 rls command 2-11 rmdir command rrm command 2-11 running configuration copying to working directory 3-14 OmniSwitch AOS Release 7 Switch Management Guide March 2011 Index-3...
  • Page 202 6-17, 9-12 user configuration snmp trap filter command verify information about 6-19 software rollback user database configuration scenarios specifications specifications switch management user password-expiration command 6-12 Index-4 OmniSwitch AOS Release 7 Switch Management Guide March 2011...
  • Page 203 10-1 verbose mode vi command WebView application examples browser setup CLI commands defaults disabling enabling Secure Socket Layer who command 6-19 whoami command 6-20 working directory OmniSwitch AOS Release 7 Switch Management Guide March 2011 Index-5...
  • Page 204: Index

    Index Index-6 OmniSwitch AOS Release 7 Switch Management Guide March 2011...

This manual is also suitable for:

Omniswitch aos 7

Table of Contents