Alcatel-Lucent 7210 SAS-D Configuration Manual

Alcatel-Lucent 7210 SAS-D Configuration Manual

Service access switch
Hide thumbs Also See for 7210 SAS-D:
Table of Contents

Advertisement

Alcatel-Lucent
Service Access Switch| Release 8.0 Rev.01
7 2 1 0 S A S D , E , K O S
B a s i c S y s t e m C o n f i g u r a t i o n G u i d e
3H E 10 38 4A AAATQ Z Z A
3HE10384AAAATQZZA
Alcatel-Lucent – Proprietary & Confidential
Contains proprietary/trade secret information which is the property of Alcatel-Lucent. Not to be made available
to, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid nondisclosure
agreement in place which covers such information and contains appropriate non-disclosure and
limited use obligations.
Copyright 2015 © Alcatel-Lucent. All rights reserved.All specifications, procedures, and information in this document are subject to change and revision at any time
without notice. The information contained herein is believed to be accurate as of the date of publication. AlcatelLucent

Advertisement

Table of Contents
loading

Summary of Contents for Alcatel-Lucent 7210 SAS-D

  • Page 1 Copyright 2015 © Alcatel-Lucent. All rights reserved.All specifications, procedures, and information in this document are subject to change and revision at any time without notice. The information contained herein is believed to be accurate as of the date of publication. AlcatelLucent...
  • Page 2 This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation.
  • Page 3: Table Of Contents

    Flash Contents of the node shipped from factory ........112 System Boot Options on 7210 SAS-D and 7210 SAS-E devices ......114...
  • Page 4 Persistence..............125 Configuration guidelines for use of software images with the 128MB 7210 SAS-D platform ..126 Out-of-band (OOB) Ethernet Management Port.
  • Page 5 Configuration guidelines and restrictions for PTP on 7210 SAS-D ETR and 7210 SAS-K ..209 Configuration to change reference from SyncE to PTP on 7210 SAS-D ETR ....210 Management of 1830 VWM .
  • Page 6 System Alarm Contact Inputs ............274 Configuring an Alarm Input in 7210 SAS-D and 7210 SAS-K devices ..... .274 Configuring 1830 VWM.
  • Page 7 Table 34: Values and the corresponding pps rate for 7210 SAS-D ......330 Table 35: Values and the corresponding pps rate for 7210 SAS-K .
  • Page 8 List of Tables Table 40: Show System Time Output Fields..........430 Table 41: Show VWM-shelf Output Fields .
  • Page 9 Conventional Network Timing Architecture (North American Nomenclature) ... . .191 Figure 19: Synchronisation Reference selection on 7210 SAS-D ETR......193 Figure 20: Peer Clocks .
  • Page 10 List of Figures Page 10 7210 SAS D, E, K OS Basic System Configu-...
  • Page 11: Preface

    About This Guide This guide describes system concepts and provides configuration explanations and examples to configure 7210 SAS-D, E, K platforms boot option file (BOF), file system and system management functions. On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the modes.
  • Page 12: List Of Technical Publications

    Preface List of Technical Publications The 7210-SAS D, E, K OS documentation set is composed of the following books: • 7210-SAS D, E, K OS Basic System Configuration Guide This guide describes basic system configurations and operations. • 7210-SAS D, E, K OS System Management Guide This guide describes system security and access configurations as well as event logging and accounting logs.
  • Page 13: Technical Support

    If you purchased a service agreement for your 7210 SAS-Series router and related products from a distributor or authorized re-seller, contact the technical support staff for that distributor or reseller for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center: Web: http://www.alcatel-lucent.com/wps/portal/support...
  • Page 14 Preface Page 14 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 15: Getting Started

    In This Chapter This chapter provides process flow information to configure basic router and system parameters, perform operational functions with directory and file management, and boot option tasks. Alcatel-Lucent 7210 SAS-Series System Configuration Pro- cess Table 1 lists the tasks necessary to configure boot option files (BOF) and system and file management functions.
  • Page 16: Getting Started

    Getting Started Table 1: Configuration Process Area Task Chapter (Continued) Boot options Configure boot option files Boot Options on page 109 (BOF) System configuration Configure system functions, System Management on page 179 including host name, address, domain name, and time parameters.
  • Page 17: Cli Usage

    CLI Usage In This Chapter This chapter provides information about using the command-line interface (CLI). Topics in this chapter include: • CLI Structure on page 18 • Navigating in the CLI on page 20 • Basic CLI Commands on page 22 •...
  • Page 18: Cli Structure

    CLI Structure CLI Structure Alcatel-Lucent’s Operating System (OS) CLI is a command-driven interface accessible through the console, Telnet and secure shell (SSH). The CLI can be used for configuration and management of routers. The CLI command tree is a hierarchical inverted tree. At the highest level is the ROOT level.
  • Page 19: Figure 2: Operational Root Commands

    CLI Usage ROOT SHOW alias boot-messages CLEAR card card chassis cron filter cron debug DEBUG dot1ag port filter mirror-source radius radius router TOOLS router dump service mirror perform snmp screen pools system service port trace tacplus port-tree trace router service snmp split-horizon-group system...
  • Page 20: Navigating In The Cli

    Entering Numerical Ranges on page 39 CLI Contexts Use the CLI to access, configure, and manage Alcatel-Lucent’s 7210 SAS devices. CLI commands are entered at the command line prompt. Access to specific CLI commands is controlled by the permissions set by your system administrator. Entering a CLI command makes navigation possible from one command context (or level) to another.
  • Page 21 CLI Usage The CLI returns an error message when the syntax is incorrect. A:ALU-7210>config>service>epipe# sapp Error: Bad command. A:ALU-7210>config>service>epipe# 7210 SAS D, E, K OS Basic System Configuration Guide Page 21...
  • Page 22: Basic Cli Commands

    Navigating in the CLI Basic CLI Commands The console control commands are the commands that are used for navigating within the CLI and displaying information about the console session. Most of these commands are implemented as global commands. They can be entered at any level in the CLI hierarchy with the exception of the command which must be entered at the ROOT level.
  • Page 23 CLI Usage Table 2: Console Control Commands (Continued) Command Description Page Causes the console session to pause operation (sleep) for one second sleep or for the specified number of seconds. Primary use is to introduce a pause within the execution of an file.
  • Page 24: Table 3: Command Syntax Symbols

    Navigating in the CLI Table 3 lists describes command syntax symbols. Table 3: Command Syntax Symbols Symbol Description A vertical line indicates that one of the parameters within the brackets or braces is required. tcp-ack {true|false} Brackets indicate optional parameters. redirects [number seconds] Angle brackets indicate that you must enter text based on the parameter inside the <...
  • Page 25: Cli Environment Commands

    CLI Usage CLI Environment Commands The CLI environment commands are found in the root>environment context of the CLI tree and controls session preferences for a single CLI session. The CLI environment commands are listed Table Table 4: CLI Environment Commands Command Description Page...
  • Page 26: Cli Monitor Commands

    Navigating in the CLI CLI Monitor Commands Monitor commands display specified statistical information related to the monitor subject (such as filter, port, QoS, router, service) at a configurable interval until a count is reached. The CLI monitor commands are found in the root>monitor context of the CLI tree. The monitor command output displays a snapshot of the current statistics.
  • Page 27: Getting Help In The Cli

    CLI Usage Getting Help in the CLI The help system commands and the key display different types of help in the CLI. Table 6 lists the different help commands. Table 6: Online Help Commands Command Description List all commands in the current context. help ? List all commands available in the current context that start with string.
  • Page 28 Getting Help in the CLI A:ALU-7210>config# tree *A:ALA-12>config# tree detail configure configure +---card +---card <slot-number> | +---card-type | no card <slot-number> | +---mda | +---card-type <card-type> | | +---access | | no card-type | | +---mda-type | +---mda <mda-slot> | | +---network | | no mda <mda-slot>...
  • Page 29: The Cli Command Prompt

    CLI Usage The CLI Command Prompt By default, the CLI command prompt indicates the device being accessed and the current CLI context. For example, the prompt: A:ALA-1>config>router>if# indicates the active context, the user is on the device with hostname ALA-1 in the configure>router>interface context. In the prompt, the separator used between contexts is the “...
  • Page 30: Displaying Configuration Contexts

    Displaying Configuration Contexts Displaying Configuration Contexts The info and info detail commands display configuration for the current level. The info command displays non-default configurations. The info detail command displays the entire configuration for the current level, including defaults. The following example shows the output that displays using the command and the output that displays using the info detail info...
  • Page 31 CLI Usage link-type pt-pt no root-guard no shutdown exit dot1ag exit no authentication-policy no l2pt-termination no bpdu-translation ingress qos 1 no match-qinq-dot1p no filter exit egress no qinq-mark-top-only no filter no agg-rate-limit exit no collect-stats no accounting-policy no shutdown exit sap 1/1/15:100 create no description no tod-suite...
  • Page 32 Displaying Configuration Contexts no shutdown ---------------------------------------------- *A:ALA>config>service>vpls# Page 32 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 33: Exec Files

    CLI Usage EXEC Files command allows you to execute a text file of CLI commands as if it were typed at a exec console device. The exec command and the associated exec files can be used to conveniently execute a number of commands that are always executed together in the same order.
  • Page 34: Entering Cli Commands

    Entering CLI Commands Entering CLI Commands Command Completion The CLI supports both command abbreviation and command completion. If the keystrokes entered are enough to match a valid command, the CLI displays the remainder of the command syntax when the <Tab> key or space bar is pressed. When typing a command, the <Tab> key or space bar invokes auto-completion.
  • Page 35: Editing Keystrokes

    CLI Usage Editing Keystrokes When entering a command, special keystrokes allow for editing of the command. Table 7 lists the command editing keystrokes. Table 7: Command Editing Keystrokes Editing Action Keystrokes Delete current character <Ctrl-d> Delete text up to cursor <Ctrl-u>...
  • Page 36: Absolute Paths

    Entering CLI Commands Absolute Paths CLI commands can be executed in any context by specifying the full path from the CLI root. To execute an out-of-context command enter a forward slash “/” or backward slash “\” at the beginning of the command line. The forward slash “/” or backward slash “\” cannot be used with the environment alias command.The commands are interpreted as absolute path.
  • Page 37 CLI Usage If the command takes you to a different context, the following occurs: CLI Syntax: config>service>ies>/configure service ies 5 create becomes Example config>service>ies>exit all configure service vpls 5 create config>service>vpls> 7210 SAS D, E, K OS Basic System Configuration Guide Page 37...
  • Page 38: History

    16 history *A:ALA-1# !3 A:cses-E11# show version TiMOS-B-0.0.I2838 both/i386 ALCATEL SR 7750 Copyright (c) 2000-2011 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Mon Jan 10 18:33:16 PST 2011 by builder in /rel0.0/I2838/panos/main A:cses-E11# TiMOS-B-0.0.I232 both/i386 ALCATEL SAS-E 7210 Copyright (c) 2000-2008 Alcatel-Lu cent.
  • Page 39: Entering Numerical Ranges

    CLI Usage Entering Numerical Ranges The 7210-SAS OS CLI allows the use of a single numerical range as an argument in the command line. A range in a CLI command is limited to positive integers and is denoted with two numbers enclosed in square brackets with two periods (“..”) between the numbers: x..y where x and y are positive integers and y-x is less than 1000.
  • Page 40 Entering CLI Commands Table 8: CLI Range Use Limitations (Continued) Limitation Description The range cannot cause a change in Commands should be formed in such a way that there is no context contexts. change upon command completion. For example, configure port 1/1/[1..10] will attempt to change ten different contexts.
  • Page 41: Pipe/Match

    CLI Usage Pipe/Match The 7210 SAS devices supports the pipe feature to search one or more files for a given character string or pattern. Note: When using the pipe/match command the variables and attributes must be spelled correctly. The attributes following the command and must come before the expression/pattern. The following displays examples of the pipe/match command to complete different tasks: •...
  • Page 42: Table 9: Regular Expression Symbols

    Entering CLI Commands For example: *A:Dut-G# show log log-id 99 | match ignore-case sap "Processing of an access port state change event is finished and the status of all affected SAPs on port 1/1/21 has been updated." "Service Id 4001, SAP Id 1/1/21:0.* configuration modified" A:Dut-C# show log log-id 98 | match max-count 1 "service 1001"...
  • Page 43: Table 10: Special Characters

    CLI Usage Table 9: Regular Expression Symbols (Continued) String Description {m,n} Matches least m and at most n repetitions of the term Matches exactly m repetitions of the term {m,} Matches m or more repetitions of the term The preceding item is optional and matched at most once. The preceding item is matched one or more times.
  • Page 44: Redirection

    Entering CLI Commands Redirection The 7210-SAS OS supports redirection (“>”) which allows the operator to store the output of a CLI command as a local or remote file. Redirection of output can be used to automatically store results of commands in files (both local and remote). ‘ping <customer_ip>...
  • Page 45: Basic Command Reference

    Basic Command Reference Basic Command Reference Command Hierarchies • Monitor Commands • Environment Commands Global CLI Commands — back — clear — echo [text-to-echo] [extra-text-to-echo] [more-text] — enable-admin — exec [-echo] [-syntax] filename — exit [all] — help — history —...
  • Page 46: Monitor Commands

    Monitor Commands monitor — filter — ip-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute | rate] — ipv6 ipv6-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute|rate] — mac-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute | rate] — lag-id [lag-id...(up to 5 max)] [interval seconds] [repeat repeat] [absolute | rate] —...
  • Page 47: Environment Commands

    Basic Command Reference Environment Commands root — environment — alias alias-name alias-command-name — no alias alias-name — [no] create — [no] more — reduced-prompt [no. of nodes in prompt] — no reduced-prompt — [no] saved-ind-prompt — terminal — length lines —...
  • Page 48 Page 48 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 49 Root Commands Basic CLI Commands Global Commands enable-admin Syntax enable-admin Context <global> Description NOTE: See the description for the admin-password command. If the admin-password is config- ured in the config>system>security>password context, then any user can enter a special administra- tive mode by entering the enable-admin command. enable-admin is in the default profile.
  • Page 50 Global Commands 'A' indicates user is in admin mode =============================================================================== A:ALA-1# A:ALA-1# enable-admin MINOR: CLI Already in admin mode. A:ALA-1# back Syntax back Context <GLOBAL> Description This command moves the context back one level of the command hierarchy. For example, if the cur- rent level is the config router ospfconfig router interface interface-id context, the back command moves the cursor to the config router context level.
  • Page 51 Root Commands echo Syntax echo [text-to-echo] [extra-text-to-echo] [more-text] Context <GLOBAL> Description This command echoes arguments on the command line. The primary use of this command is to allow messages to be displayed to the screen in files executed with the exec command. Parameters text-to-echo —...
  • Page 52 Global Commands exit Syntax exit [all] Context <GLOBAL> Description This command returns to the context from which the current level was entered. For example, if you navigated to the current level on a context by context basis, then the exit command only moves the cursor back one level.
  • Page 53 Root Commands Delete current character.....Ctrl-d Delete text up to cursor.....Ctrl-u Delete text after cursor.....Ctrl-k Move to beginning of line....Ctrl-a Move to end of line......Ctrl-e Get prior command from history....Ctrl-p Get next command from history....Ctrl-n Move cursor left......Ctrl-b Move cursor right......Ctrl-f Move back one word......Esc-b Move forward one word......Esc-f Convert rest of word to uppercase....Esc-c...
  • Page 54 Global Commands history Syntax history Context <GLOBAL> Description This command lists the last 30 commands entered in this session. Re-execute a command in the history with the !n command, where n is the line number associated with the command in the history output. For example: A:ALA-1# history 68 info...
  • Page 55 Root Commands The output of this command is similar to the output of a show config command. This command, how- ever, lists the configuration of the context where it is entered and all branches below that context level. By default, the command only enters the configuration parameters that vary from the default values. The detail keyword causes all configuration parameters to be displayed.
  • Page 56 Global Commands exit mac-move move-frequency 2 retry-timeout 10 shutdown exit sap 1/1/14:100 create no description no tod-suite limit-mac-move blockable no disable-aging no max-nbr-mac-addr no discard-unknown-source no mac-pinning path-cost 10 priority 128 no edge-port auto-edge link-type pt-pt no root-guard no shutdown exit dot1ag exit...
  • Page 57 Root Commands no authentication-policy no l2pt-termination no bpdu-translation ingress qos 1 no match-qinq-dot1p no filter exit egress no qinq-mark-top-only no filter no agg-rate-limit exit no collect-stats no accounting-policy no shutdown exit no shutdown exit ies 4001 customer 1 create no description interface "inband"...
  • Page 58 Global Commands egress no qinq-mark-top-only no filter exit no shutdown exit no shutdown exit no shutdown exit ---------------------------------------------- *A:STU-1>config>service# Parameters detail — Displays all configuration parameters including parameters at their default values. logout Syntax logout Context <GLOBAL> Description This command logs out of the router session. When the logout command is issued from the console, the login prompt is displayed, and any log IDs directed to the console are discarded.
  • Page 59 Root Commands password Syntax password Context <ROOT> Description This command changes a user CLI login password. When a user logs in after the administrator forces a new-password-at-login, or the password has expired (aging), then this command is automatically invoked. When invoked, the user is prompted to enter the old password, the new password, and then the new password again to verify the correct input.
  • Page 60 Global Commands 64 bytes from 192.xxx.xxx.xxx: icmp_seq=4 ttl=64 time<10ms. 64 bytes from 192.xxx.xxx.xxx: icmp_seq=5 ttl=64 time<10ms. ---- 192.xxx.xxx.xxx PING Statistics ---- 5 packets transmitted, 5 packets received, 0.00% packet loss round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms *A:ALU-7210# ttl time-to-live —...
  • Page 61 Root Commands bypass-routing — Send the ping request to a host on a directly attached network bypassing the routing table. The host must be on a directly attached network or an error is returned. count requests — The number of ping requests to send to the remote host, expressed as a decimal integer.
  • Page 62 Global Commands sleep Syntax sleep [seconds] Context <GLOBAL> Description This command causes the console session to pause operation (sleep) for 1 second (default) or for the specified number of seconds. Parameters seconds — The number of seconds for the console session to sleep, expressed as a decimal integer. Default Values 1 —...
  • Page 63 Root Commands Parameters ip-address — The IP address or the DNS name (providing DNS name resolution is configured) can be specified. Values ipv4-address a.b.c.d ipv6-address x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x: [0 .. FFFF]H d: [0 .. 255]D dns-name — Specify the DNS name (if DNS name resolution is configured). Values 128 characters maximum port —...
  • Page 64 Global Commands wait milliseconds — The time in milliseconds to wait for a response to a probe, expressed as a decimal integer. Default 5000 Values 1 — 60000 no-dns — When the no-dns keyword is specified, a DNS lookup for the specified host name will not be performed.
  • Page 65 Root Commands CLI Environment Commands alias Syntax alias alias-name alias-command-line no alias alias-name Context environment Description This command enables the substitution of a command line by an alias. Use the alias command to cre- ate alternative or easier to remember/understand names for an entity or command string. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
  • Page 66 CLI Environment Commands Default more — CLI output pauses at the end of each screen waiting for the user input to continue. reduced-prompt Syntax reduced-prompt [number of nodes in prompt] no reduced-prompt Context environment Description This command configures the maximum number of higher CLI context levels to display in the CLI prompt for the current CLI session.
  • Page 67 Root Commands terminal Syntax terminal no terminal Context environment Description This command enables the context to configure the terminal screen length for the current CLI session. length Syntax length lines Context environment>terminal Default 24 — Terminal dimensions are set to 24 lines long by 80 characters wide. Parameters lines —...
  • Page 68 Monitor CLI Commands Monitor CLI Commands filter Syntax filter Context monitor Description This command enables the context to configure criteria to monitor IP and MAC filter statistics. Syntax ip ip-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute | rate] Context monitor>filter monitor>management-access-filter Description...
  • Page 69 Root Commands Sample Output A:ALA-1>monitor# filter ip 10 entry 1 interval 3 repeat 3 absolute =============================================================================== Monitor statistics for IP filter 10 entry 1 =============================================================================== At time t = 0 sec (Base Statistics) ------------------------------------------------------------------------------- Ing. Matches: 0 Egr. Matches ------------------------------------------------------------------------------- At time t = 3 sec (Mode: Absolute) ------------------------------------------------------------------------------- Ing.
  • Page 70 Monitor CLI Commands ipv6 Syntax ipv6 ipv6-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute | rate] Context monitor>filter monitor>management-access-filter Description This command enables IPv6 filter monitoring. The statistical information for the specified IPv6 filter entry displays at the configured interval until the configured count is reached. The first screen displays the current statistics related to the specified IPv6 filter.
  • Page 71 Root Commands ------------------------------------------------------------------------------- At time t = 3 sec (Mode: Absolute) ------------------------------------------------------------------------------- Ing. Matches : 0 pkts Egr. Matches : 0 pkts ------------------------------------------------------------------------------- At time t = 6 sec (Mode: Absolute) ------------------------------------------------------------------------------- Ing. Matches : 0 pkts Egr. Matches : 0 pkts ------------------------------------------------------------------------------- At time t = 9 sec (Mode: Absolute) -------------------------------------------------------------------------------...
  • Page 72 Monitor CLI Commands absolute — When the absolute keyword is specified, the raw statistics are displayed, without pro- cessing. No calculations are performed on the delta or rate statistics. rate — When the rate keyword is specified, the rate-per-second for each statistic is displayed instead of the delta.
  • Page 73 Context monitor Description Platforms Supported: 7210 SAS-D and 7210 SAS-E.This command monitors traffic statistics for Link Aggregation Group (LAG) ports. Statistical information for the specified LAG ID(s) displays at the configured interval until the configured count is reached. The first screen displays the current statistics related to the specified LAG ID. The subsequent statis- tical information listed for each interval is displayed as a delta to the previous display.
  • Page 74 [interval seconds] [repeat repeat] [absolute | rate] Context monitor>management-access-filter Description Platforms Supported: 7210 SAS-D and 7210 SAS-E. This command nonitors statistics for the MAF IP filter entry. Parameters entry entry-id — Specifies an existing IP MAF entry ID.
  • Page 75 [interval seconds] [repeat repeat] [absolute | rate] Context monitor>management-access-filter Description Platforms Supported: 7210 SAS-D and 7210 SAS-E. This command nonitors statistics for the MAF IPv6 filter entry. Parameters entry entry-id — Specifies an existing IP MAF entry ID.
  • Page 76 Monitor CLI Commands repeat repeat — Configures how many times the command is repeated. Default Values 1 — 999 absolute — When the absolute keyword is specified, the raw statistics are displayed, without processing. No calculations are performed on the delta or rate statistics. rate —...
  • Page 77 Root Commands ------------------------------------------------------------------------------- Octets Packets Errors ------------------------------------------------------------------------------- At time t = 6 sec (Mode: Rate) ------------------------------------------------------------------------------- Octets Packets Errors ------------------------------------------------------------------------------- At time t = 9 sec (Mode: Rate) ------------------------------------------------------------------------------- Octets Packets Errors =============================================================================== A:ALA-12>monitor# service Syntax service Context monitor Description This command enables the context to configure criteria to monitor specific service SAP criteria.
  • Page 78 Monitor CLI Commands Syntax sap sap-id [interval seconds] [repeat repeat] [absolute | rate] Context monitor>service>id service-id Description This command monitors statistics for a SAP associated with this service. This command displays statistics for a specific SAP, identified by the port-id and encapsulation value, at the configured interval until the configured count is reached.
  • Page 79 Root Commands Ethernet Null The SAP is identified by the port. Ethernet Dot1q 0 — 4094 The SAP is identified by the 802.1Q tag on the port. Note that a 0 qtag1 value also accepts untagged packets on the dot1q port. Ethernet QinQ qtag1: 0 —...
  • Page 80 Monitor CLI Commands ------------------------------------------------------------------------------- Packets Octets Ingress Meter 1 (Unicast) For. InProf : 0 For. OutProf : 210645 0 Ingress Meter 11 (Multipoint) For. InProf : For. OutProf : 87238 0 =============================================================================== A:7210SAS-E>monitor>service>id# Syntax sdp {sdp-id | far-end ip-address} [interval seconds] [repeat repeat] [absolute | rate] Context monitor>service>id service-id Description...
  • Page 81 Root Commands E. Fwd. Pkts. : 0 E. Fwd. Octets : 0 ------------------------------------------------------------------------------- At time t = 22 sec (Mode: Delta) ------------------------------------------------------------------------------- I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0 E. Fwd. Pkts. : 0 E. Fwd. Octets : 0 ------------------------------------------------------------------------------- At time t = 33 sec (Mode: Delta) -------------------------------------------------------------------------------...
  • Page 82: Table 11: Show Alias Output Fields

    Show Commands Show Commands alias Syntax alias Context <root> Description This command displays a list of existing aliases. Output Show Alias Fields — The following table describes alias output fields. Table 11: Show Alias Output Fields Label Description Displays the name of the alias. Alias-Name The command and parameter syntax that define the alias.
  • Page 83: File System Management

    File System Management In This Chapter This chapter provides information about file system management. Topics in this chapter include: • The File System on page 84 → Compact Flash Devices on page 84 → USB Storage Device on page 85 →...
  • Page 84: The File System

    7210 SAS-E supports an internal flash (named cf1:\) and a USB port (named uf1:\) for USB based storage device • 7210 SAS-D supports only an internal flash (named cf1:\) • 7210 SAS-K supports two USB ports. The one on the rear panel is called cf1:\ with an option to secure access to the USB port.
  • Page 85: Usb Storage Device

    In the above example, the total of files and directories is 14 files + 2 directories = 16. USB Storage Device Note: USB devices are not supported on 7210 SAS-D devices. 7210 SAS platform support USB interface which provides storage functionality. It allows the use of USB sticks providing them an alternate storage location with larger capacity than the internal flash.
  • Page 86: Urls

    The File System • 7210 SAS also autodetects the device type when any of the supported devices are connected to the USB interface. Only approved USB mass storage device and optical clip- on devices can be plugged in to the USB port and are recognized as valid devices. All other unsupported devices will result in an error log being printed.
  • Page 87 File System Management files to the SCP server. If the external system treats the backslash like an escape character, the backslash delimiter will get stripped by the parser and will not be transmitted to the SCP server. For example, a destination directory specified as “cf1:\dir1\file1” will be transmitted to the SCP server as “cf1:dir1file1”...
  • Page 88: Wildcards

    The File System Wildcards 7210 SAS OS supports the standard DOS wildcard characters. The asterisk (*) can represent zero or more characters in a string of characters, and the question mark (?) can represent any one character. Example A:ALA-1>file cf1:\ # copy test*.cfg siliconvalley cf1:\testfile.cfg 1 file(s) copied.
  • Page 89: File Management Tasks

    File System Management File Management Tasks The following sections are basic system tasks that can be performed. Note that when a file system operation is performed with the copy, delete, move, rd, or scp commands that can potentially delete or overwrite a file system entry, a prompt appears to confirm the action.
  • Page 90 File Management Tasks file-url The following displays an example of the command syntax: Example file cf1:\ # md test1 file cf1:\ # cd test1 file cf1:\test1\ # md test2 file cf1:\test1\ # cd test2 file cf1:\test1\test2\ # md test3 file cf1:\test1\test2\ # cd test3 file cf1:\test1\test2\test3 # Page 90 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 91: Copying Files

    File System Management Copying Files Use the copy command to upload or download an image file, configuration file, or other file types to or from a flash card or a TFTP server. The scp command copies files between hosts on a network. It uses SSH for data transfer, and uses the same authentication and provides the same security as SSH.
  • Page 92: Moving Files

    File Management Tasks Moving Files Use the command to move a file or directory from one location to another. move Use the CLI syntax displayed below to move files: CLI Syntax: file> move old-file-url new-file-url [force] The following displays an example of the command syntax: Example A:ALA-1>file cf1:\test1\test2\test3\ # move test.cfg cf1:\test1 cf1:\test1\test2\test3\test.cfg...
  • Page 93: Displaying Directory And File Information

    File System Management Displaying Directory and File Information Use the dir command to display a list of files on a file system. The type command displays the contents of a file. The version command displays the version of a cpm.tim or iom.tim file. Use the CLI syntax displayed below to display directory and file information: CLI Syntax: file>...
  • Page 94 File Management Tasks Page 94 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 95: File Command Reference

    File Commands File Command Reference Command Hierarchy Configuration Commands file — attrib [+r | -r] file-url — attrib — [file-url] — copy source-file-url dest-file-url [force] — delete file-url [force] — [file-url] [sort-order {d | n | s}] [reverse] — format cflash cflash-id [reliable] (Only supported on 7210 SAS-K) —...
  • Page 96 File Command Reference Page 96 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 97 None cf1:|cf2:|uf1: Values uf1: - 7210 SAS-E None - 7210 SAS-D (In other words, this command is not supported on 7210 SAS- cf1: | uf1: - 7210 SAS-K 7210 SAS D, E, K OS Basic System Configuration Guide Page 97...
  • Page 98 - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K +r — Sets the read-only attribute on the specified file.
  • Page 99 - [0..FFFF]H d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K <none> — Displays the current working directory.
  • Page 100 - [0..FFFF]H d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K Values force Forces an immediate copy of the specified file(s).
  • Page 101 - [0..FFFF]H d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K Values force Forces an immediate deletion of the specified file(s).
  • Page 102 - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K Values Use the file-url with the optional wildcard (*) to reduce the number of files to list.
  • Page 103 - [0..FFFF]H d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E 7210 SAS D, E, K OS Basic System Configuration Guide Page 103...
  • Page 104 - [0..FFFF]H d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K Values new-file-url The new destination to place the old-file-url.
  • Page 105 Configuration Commands interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K Values force Forces an immediate move of the specified file(s).
  • Page 106 If no cflash-id is specified, the drive referred to by the cur- rent working directory is assumed. Default The current compact flash device. Values cf1:|uf1: - 7210 SAS-E cf1: - 7210 SAS-D cf1:|uf1: - 7210 SAS-K Syntax scp local-file-url destination-file-url [router router-instance] [force] Context file Description This command copies a local file to a remote host file system.
  • Page 107 Configuration Commands hostname - [ <dns-name> | <ipv4-address> | "["<ipv6-address>"]" ] ipv4-address - a.b.c.d ipv6-address - x:x:x:x:x:x:x:x[-interface] x:x:x:x:x:x:d.d.d.d[-interface] x - [0..FFFF]H d - [0..255]D interface - 32 chars max, mandatory for link local addresses dns-name - [128 chars max] file-path - [200 chars max] directory length 99 chars max each <router-instance>...
  • Page 108 File Commands local addresses cflash-id or usb-flash-id - cf1: - 7210 SAS-D cf1: | uf1: - 7210 SAS-E cf1: | uf1: - 7210 SAS-K version Syntax version file-url [check] Context file Description file This command displays the version of a TiMOS Parameters file-url —...
  • Page 109: Boot Options

    Boot Options In This Chapter This chapter provides information about configuring boot option parameters. Topics in this chapter include: • System Intialization on page 110 → Manual Mode on page 115 → Auto Init on page 117 → Ping Check in auto-init mode on page 124 −...
  • Page 110: System Intialization

    System Intialization System Intialization Note: Some 7210 SAS platforms (For example: 7210 SAS-K) do not ship with an image. It is expected that the user will use the external flash or the USB device with bootloader image (boot.tim) to boot the system. The user will need to insert the device (either the compact flash into the external compact flash slot or the USB storage device into the USB port) before powering on the system.
  • Page 111: Figure 3: Bootstrap Load Process - System Initialisation - Part I

    Managing a node through an external physical network secures the management network by restricting access to service customers and service data. The 7210 SAS-E node can be managed through the Out-of-band (OOB) Ethernet management port. The 7210 SAS-D and 7210 SAS-K devices do not support Out-of-band Ethernet management port.
  • Page 112: Flash Contents Of The Node Shipped From Factory

    Total Memory: 512MB Chassis Type: sas Card Type: badami_7210 TiMOS-L-0.0.I312 boot/mpc ALCATEL SAS-E 7210 Copyright (c) 2000-2009 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Fri Jan 2 04:26:32 IST 2009 by panosbld in /panosbld/ws/panos/main...
  • Page 113: Figure 4: Files On The Flash

    Boot Option Files Figure 4: Files on the Flash Files on the compact flash are: • bof.cfg — Boot option file • boot.tim — Bootstrap image • config.cfg — Default configuration file • TIMOS-m.n.Yz: m — Major release number n — Minor release number Y: A —...
  • Page 114: System Boot Options On 7210 Sas-D And 7210 Sas-E Devices

    • Network (without auto-init) NOTE: The 7210 SAS-D and 7210 SAS-E can use a both.tim (that is, Timos image) present on the USB storage stick for booting up. It cannot use boot.tim present on the USB storage stick for booting up, though.
  • Page 115: Storage Locations For Index Files (Ndx, Sdx) And Images For 7210 Sas-K

    Create a backup of these files on uf1:\ or create a backup on the SAM/network management station regularly. Manual Mode Note: Out-of-Band Ethernet management port is not supported on 7210 SAS-D and 7210 SAS-K devices. 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 116 For 7210 SAS-E devices, eth-mgmt-disable parameter indicates if the out-of-band Ethernet management port is enabled during the boot-up procedure. The 7210 SAS-D devices do not support Out-of-band Ethernet management port. For a 7210 node which has a previous BOF, the boot process uses the existing parameters for uplink A and uplink B ports to boot the TIMOS image.
  • Page 117: Auto Init

    Boot Option Files Auto Init During the first boot or a reboot after the execution of CLI command admin reboot auto-init, if the user does not intervene to create the BOF file in the manual mode, the system, by default, goes to auto-init procedure after a “wait”...
  • Page 118: Configuration And Image Loading

    Configuration and Image Loading image found on the local flash, user has the option to either continue using the same image by entering the command 'admin auto init stop" within a fixed amount of time as prompted on the screen. If the user executes this command, then a BOF is created and saved on the local flash with the image location pointing to the image on the flash.
  • Page 119: Figure 5: Bootstrap Process - System Initialization - Part Ii-A

    Boot Option Files Figure 5: Bootstrap Process - System Initialization - Part II-A 7210 SAS D, E, K OS Basic System Configuration Guide Page 119...
  • Page 120: Figure 6: Automode With Partial Bof

    Configuration and Image Loading Figure 6: Automode with partial BOF Page 120 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 121: Figure 7: Bootstrap Process - System Initialization - Part Ii-B

    Boot Option Files Figure 7: Bootstrap Process - System Initialization - Part II-B 7210 SAS D, E, K OS Basic System Configuration Guide Page 121...
  • Page 122: Figure 8: Bootstrap Process - System Initialization - Part Ii-C

    Configuration and Image Loading Figure 8: Bootstrap Process - System Initialization - Part II-C When the runtime image is successfully downloaded, control is passed from the bootstrap image. The runtime image attempts to load the configurations from the downloaded configuration file. If no configuration file location is present in the BOF file, then the system is loaded with default configuration.
  • Page 123: Figure 9: Timos Boot - System Initialization - Part Iii

    Boot Option Files Figure 9: Timos Boot - System Initialization - Part III 7210 SAS D, E, K OS Basic System Configuration Guide Page 123...
  • Page 124: Ping Check In Auto-Init Mode

    Configuration and Image Loading Ping Check in auto-init mode If the system is booted up using the auto-init procedure, the runtime image performs a ping check to make sure that the system has IP connectivity. The runtime image, after loading the configurations from the configuration file, tries three times to ping the IP address specified as the ping-address parameter in the BOF file, at a 2, 8 and 16 minutes interval minute interval.
  • Page 125: Persistence

    Boot Option Files fails, the uplink A and uplink B parameters are used to retrieve the TIMOS image and configuration files. • When using auto-init, with partial BOF configuration, the user now has an option to login to the node using the console and stop auto-init (using the command admin>auto-init stop) or let auto-init continue.
  • Page 126: Configuration Guidelines For Use Of Software Images With The 128Mb 7210 Sas-D Platform

    The new 7210 SAS-D platforms with 128MB flash can boot entirely new software releases. The older images cannot be used with the new devices. The older 7210 SAS-D platforms with 64MB flash can use any image. All new devices are shipped with the latest bootrom. The system...
  • Page 127: Configuration Guidelines For Use Of Ipv6 For Out-Of-Band Management Of The Node

    Boot Option Files Configuration Guidelines for use of IPv6 for out-of-band management of the node • The management port on the management router instance only supports host functionality. • It is necessary to have an IPv4 address configured in the bof file. A bof file that contains only IPv6 addresses is not supported.
  • Page 128 Configuration and Image Loading Note 1: The BOF password can be changed from default value to any other user defined value only at the Timos level. Note 2: It is highly recommended that user does not rename cf1:\boot.tim and cf1:\both.tim, if the system needs to retain them during the password recovery procedure.
  • Page 129 At this point the password has been reset and the node is rebooted to boot up with factory default settings. Resetting...OK ø Alcatel-Lucent 7210 Boot ROM. Copyright 2009-2011 Alcatel-Lucent. All rights reserved. All use is subject to applicable license agreements. Running POST tests from ROM Testing ROM load area...done Relocating code...Jumping to RAM...
  • Page 130 Total Memory: 1GB Chassis Type: sas Card Type: badami_7210 TiMOS-L-4.0.beta-private boot/mpc ALCATEL SAS 7210 Copyright (c) 2000-2011 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Sat Aug 20 12:59:26 IST 2011 by abc in /abc/ws-40b/panos/main TiMOS BOOT LOADER CPLD Version: 2.1...
  • Page 131: Initial System Startup Process Flow

    Boot Option Files Initial System Startup Process Flow Figure 10 displays the process start your system. Note that this example assumes that the boot loader and BOF image and configuration files are successfully located. START POWER CYCLE ROUTER BOOT.TIM FILES FOUND BOF FILES FOUND ESTABLISH ROUTER CONNECTION (CONSOLE PORT) PRIMARY IMAGE...
  • Page 132: Configuration Notes

    Configuration Notes Configuration Notes This section describes BOF configuration caveats. • The loading sequence is based on the order in which it is placed in the configuration file. It is loaded as it is read in at boot time. Page 132 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 133: Configuring Boot File Options With Cli

    Boot Option Files Configuring Boot File Options with CLI This section provides information to configure BOF parameters with CLI. Topics in this section include: • Configuring Boot File Options with CLI on page 133 • BOF Configuration Overview on page 134 •...
  • Page 134: Bof Configuration Overview

    BOF Configuration Overview BOF Configuration Overview Alcatel-Lucent routers do not contain a boot EEPROM. The bootstrap image is loaded from the boot.tim file. The BOF file performs the following tasks: 1. Sets up the uplink ports or the ethernet management port (speed, duplex, auto).
  • Page 135: Basic Bof Configuration

    #System Settings: wait persist console-speed 115200 no console-disabled =============================================================================== *A:7210>show# The following displays an example of BOF output for 7210 SAS-D device: *A:SAS-D>show# bof =============================================================================== BOF (Memory) 7210 SAS D, E, K OS Basic System Configuration Guide Page 135...
  • Page 136 Basic BOF Configuration =============================================================================== primary-image ftp://*:*@135.254.170.22//home/***/images/SASD-both.tim primary-config cf1:\****.cfg #uplinkA Port Settings: uplinkA-port 1/1/10 uplinkA-address 10.135.20.152/24 uplinkA-vlan uplinkA-route 10.135.0.0/16 next-hop 10.135.20.1 uplinkA-route 135.250.0.0/16 next-hop 10.135.20.1 uplinkA-route 135.254.0.0/16 next-hop 10.135.20.1 #System Settings: wait persist console-speed 115200 no console-disabled =============================================================================== *A:SAS-D>show# Page 136 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 137: Common Configuration Tasks

    Boot Option Files Common Configuration Tasks The following sections are basic system tasks that must be performed. • Searching for the BOF on page 138 → Accessing the CLI on page 141 − Console Connection on page 141 • Configuring BOF Parameters on page 145 For details about hardware installation and initial router connections, refer to the specific hardware installation guide.
  • Page 138: Searching For The Bof

    Common Configuration Tasks Searching for the BOF The BOF should be on the same drive as the bootstrap image file. If the system cannot load or cannot find the , then the system checks whether the boot sequence was manually interrupted else continues with the auto-init mode.
  • Page 139 Boot Option Files The existing Config URL is 'ftp://*:*@10.135.25.100/tftpboot/STU/config.cfg Press ENTER to keep it, or the word 'none' for no Config URL. Config File URL: none Network Configuration --------------------- Boot Interface Management ------------------------- You specified a network location for either the software or the configuration file.
  • Page 140 Common Configuration Tasks ------------ primary-image ftp://*:*@135.254.170.22//home/****/images/both.tim secondary-config tftp://10.135.25.100/STU/config.cfg #eth-mgmt Port Settings: eth-mgmt-disabled eth-mgmt-address 10.135.25.97/24 eth-mgmt-route 10.135.0.0/16 next-hop 10.135.25.1 eth-mgmt-route 135.254.0.0/16 next-hop 10.135.25.1 eth-mgmt-autoneg eth-mgmt-duplex full eth-mgmt-speed #uplinkA Port Settings: uplinkA-port 1/1/24 uplinkA-address uplinkA-vlan #uplinkB Port Settings: uplinkB-port 1/1/2 uplinkB-address uplinkB-vlan #System Settings: wait persist...
  • Page 141: Accessing The Cli

    Boot Option Files Accessing the CLI To access the CLI to configure the software for the first time, follow these steps: • When the power to the chassis is turned on, the 7210 SAS software automatically begins the boot sequence. •...
  • Page 142: Figure 11: 7210 Sas-E Front Panel Console Port

    Common Configuration Tasks Console Port Figure 11: 7210 SAS-E Front Panel Console Port Figure 12 Displays an example of the Console port on a 7210 SAS-D front panels. Console Port AC Power Console Port DC Power Figure 12: 7210 SAS-D Front Panel Console Port...
  • Page 143: Figure 14: 7210 Sas-K Rear Panel (Non-Etr)

    Boot Option Files Figure 14: 7210 SAS-K Rear Panel (non-ETR) Figure 15: 7210 SAS-K ETR Front Panel Figure 16: 7210 SAS-K ETR Rear Panel To establish a console connection: Connect the terminal to the Console port on the front panel using the serial cable. Step 1 7210 SAS D, E, K OS Basic System Configuration Guide Page 143...
  • Page 144: Figure 17: 7210 Sas-Mxp Front Panel Console Port

    Common Configuration Tasks Step 2 Power on the terminal. Establish the connection by pressing the <Enter> key a few times on your terminal Step 3 keyboard. At the router prompt, enter the login and password. Step 4 The default login is admin The default password is admin...
  • Page 145: Configuring Bof Parameters

    Boot Option Files Configuring BOF Parameters The following output displays a BOF configuration for 7210 SAS-E: *A:7210>show# bof =============================================================================== BOF (Memory) =============================================================================== primary-image ftp://*:*@135.254.170.22//import/panos_builds/nightly/0.0 /I783/STU-sultan primary-config ftp://*:*@10.135.25.100/tftpboot/STU/2597-ver2.cfg secondary-config tftp://10.135.25.100/STU/2597-ver2.cfg #eth-mgmt Port Settings: eth-mgmt-disabled eth-mgmt-address 10.135.25.91/24 eth-mgmt-route 10.135.0.0/16 next-hop 10.135.25.1 eth-mgmt-route 135.250.0.0/16 next-hop 10.135.25.1 eth-mgmt-route 135.254.0.0/16 next-hop 10.135.25.1...
  • Page 146: Service Management Tasks

    Service Management Tasks Service Management Tasks This section discusses the following service management tasks: • System Administration Commands on page 146 → Viewing the Current Configuration on page 146 → Modifying and Saving a Configuration on page 148 → Deleting BOF Parameters on page 149 →...
  • Page 147 Boot Option Files # Built on Fri Sep 26 20:46:58 IST 2008 by panosbld in /panosbld/ws/panos/main # Generated THU JUN 23 19:19:22 2005 UTC exit all configure #-------------------------------------------------- echo "System Configuration" #-------------------------------------------------- system name "7210-3" contact "Fred Information Technology" location "Bldg.1-floor 2-Room 201" clli-code "abcdefg1234"...
  • Page 148: Modifying And Saving A Configuration

    Service Management Tasks Modifying and Saving a Configuration If you modify a configuration file, the changes remain in effect only during the current power cycle unless a command is executed. Changes are lost if the system is powered down or the save router is rebooted without saving.
  • Page 149: Deleting Bof Parameters

    Boot Option Files Deleting BOF Parameters You can delete specific BOF parameters. The no form of these commands removes the parameter from configuration. The changes remain in effect only during the current power cycle unless a command is executed. Changes are lost if the system is powered down or the router is save rebooted without saving.
  • Page 150 Service Management Tasks uplinkB-route uplinkB-vlan wait The following is the CLI Syntax for 7210 SAS-D: CLI Syntax: *A:7210>bof# no console-speed no dns-domain persist no ping-address no primary-config no primary-dns no primary-image save no secondary-config no secondary-dns no secondary-image no tertiary-config...
  • Page 151: Saving A Configuration To A Different Filename

    A:ALA-1>admin# reboot A:DutA>admin# reboot Are you sure you want to reboot (y/n)? y Resetting...OK Alcatel-Lucent 7210 Boot ROM. Copyright 2000-2009 Alcatel-Lucent. All rights reserved. All use is subject to applicable license agreements. Running POST tests from ROM Testing ROM load area...done Relocating code...Jumping to RAM...
  • Page 152 WARNING: Configuration and/or Boot options may have changed since the last save. Are you sure you want to reset the bof and reboot (y/n)? Y Resetting...OK Alcatel-Lucent 7210 Boot ROM. Copyright 2000-2008 Alcatel-Lucent. All rights reserved. All use is subject to applicable license agreements. Page 152...
  • Page 153: Bof Command Reference

    Boot Option Files BOF Command Reference Command Hierarchies Configuration Commands NOTE: Not all the commands are supported on all the 7210 platforms. Please read the CLI description to know which platforms support these commands. — bof-password — [no] console-disabled — console-speed baud-rate —...
  • Page 154 BOF Command Reference — no uplinkA-vlan — uplinkB-address ip-address/mask — no uplinkB-address — uplinkB-port port-id — no uplinkB-port — [no] uplinkB-route ip-address/mask next-hop ip-address — uplinkB-vlan 0..4094 — no uplinkB-vlan — wait seconds Show Commands show — [cflash-id | booted] —...
  • Page 155: File Management Commands

    Boot Option Files Configuration Commands File Management Commands Syntax Context <ROOT> Description This command creates or edits the boot option file (BOF) for the specified local storage device. A BOF file specifies where the system searches for runtime images, configuration files, and other operational parameters during system initialization.
  • Page 156 File Management Commands Parameters cflash-id — The compact flash ID where the bof.cfg is to be saved. Page 156 7210 SAS D, E, K OS Basic System Configuration...
  • Page 157 Boot Option Files BOF Processing Control wait Syntax wait seconds Context Description This command configures a pause, in seconds, at the start of the boot process which allows system initialization to be interrupted at the console. When system initialization is interrupted the operator is allowed to manually override the parameters defined in the boot option file (BOF).
  • Page 158: Console Port Configuration

    File Management Commands Console Port Configuration bof-password Syntax bof-password password Context Description This command allows the user to configure a BOF password. The user will have to provide this password to edit the BOF parameters in the boot loader. It also implements a mechanism for password recovery, if the user forgets the password. If the user forgets the password, it can be reset to factory default.
  • Page 159 Boot Option Files console-speed Syntax console-speed baud-rate no console-speed Context Description This command configures the console port baud rate. When this command is issued while editing the BOF file used for the most recent boot, both the BOF file and the active configuration are changed immediately. The no form of the command reverts to the default value.
  • Page 160 File Management Commands Image and Configuration Management persist Syntax persist {on | off} Context Description This command specifies whether the system will preserve system indexes when a save command is executed. During a subsequent boot, the index file is read along with the configuration file. As a result, a number of system indexes are preserved between reboots, including the interface index, etc.
  • Page 161 Boot Option Files primary-config Syntax primary-config file-url no primary-config Context Description This command specifies the name and location of the primary configuration file. The system attempts to use the configuration specified in primary-config. If the specified file cannot be located, the system automatically attempts to obtain the configuration from the location specified in secondary-config and then the tertiary-config.
  • Page 162 File Management Commands secondary-config Syntax secondary-config file-url no secondary-config Context Description This command specifies the name and location of the secondary configuration file. The system attempts to use the configuration as specified in secondary-config if the primary config cannot be located. If the secondary-config file cannot be located, the system attempts to obtain the configuration from the location specified in the tertiary-config.
  • Page 163 Boot Option Files tertiary-config Syntax tertiary-config file-url no tertiary-config Context Description This command specifies the name and location of the tertiary configuration file. The system attempts to use the configuration specified in tertiary-config if both the primary and secondary config files cannot be located. If this file cannot be located, the system boots with the factory default configuration.
  • Page 164 File Management Commands ping-address Syntax ping-address ip-address no ping-address Context Description This command specifies the IP address which would be used for ping-test after the system boots. The no form of the command removes the ping-address configuration. Setting a value of 0 also removes the ping-address configuration.
  • Page 165 Boot Option Files The no form of the command sets the uplinkB to use DHCP to get the IP and the show bof value reflects 0 for this parameter. Parameters ip-address — The IP address of the Boot Option File (BOF). This address must be unique within the subnet and specified in dotted decimal notation.
  • Page 166 File Management Commands uplinkA-route Syntax [no] uplinkA-route ip-address/mask next-hop ip-address Context Description This command configures an uplink-A static route. Parameters ip-address — The IP address of the Boot Option File (BOF). This address must be unique within the subnet and specified in dotted decimal notation. Values a.b.c.d mask —...
  • Page 167 This command specifies a VLAN ID to be used on uplink-B. The no form of the command is used to send untagged packets on uplink-B. eth-mgmt-address Note: This command is not supported on 7210 SAS-D and 7210 SAS-K devices. Syntax [no] eth-mgmt-address ip-prefix\ip-prefix-length...
  • Page 168 - [0..255]D Values ipv4-prefix-length 0 — 32 Values ipv6-prefix-length 0 — 128 eth-mgmt-autoneg Note: This command is not supported on 7210 SAS-D and 7210 SAS-K devices. Syntax [no] eth-mgmt-autoneg Context Description Platforms Supported: 7210 SAS-E. This command enables speed and duplex Auto-negotiation on the management Ethernet port in the running configuration and the Boot Option File (BOF).
  • Page 169 Parameters full — Sets the link to full duplex mode. half — Sets the link to half duplex mode. eth-mgmt-route Note: This command is not supported on 7210 SAS-D and 7210 SAS-K devices. Syntax [no] eth-mgmt-route ip-prefix/ip-prefix-length next-hop ip-address Context Description Platforms Supported: 7210 SAS-E.
  • Page 170 File Management Commands The destination address of the static route in dotted decimal notation. eth-mgmt-speed Note: This command is not supported on 7210 SAS-D and 7210 SAS-K devices. Syntax eth-mgmt-speed speed Context Description Platforms Supported: 7210 SAS-E. This command configures the speed for the management Ethernet port when Auto-negotiation is disabled in the running configuration and the Boot Option File (BOF).
  • Page 171: Dns Configuration Commands

    Boot Option Files DNS Configuration Commands dns-domain Syntax dns-domain dns-name no dns-domain Context Description This command configures the domain name used when performing DNS address resolution. This is a required parameter if DNS address resolution is required. Only a single domain name can be configured.
  • Page 172 File Management Commands secondary-dns [no] secondary-dns ip-address Context Description This command configures the secondary DNS server for DNS name resolution. The secondary DNS server is used only if the primary DNS server does not respond. DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs.
  • Page 173: Table 15: Show Bof Output Fields

    Boot Option Files Show Commands Syntax bof [cflash-id | booted] Context show Description This command displays the Boot Option File (BOF) executed on last system boot or on the specified device. If no device is specified, the BOF used in the last system boot displays. If the BOF has been modified since the system boot, a message displays.
  • Page 174: Table 16: Show Bof Output Fields (Supported Only On 7210 Sas-E)

    Show Commands Table 15: Show BOF Output Fields (Continued) Label Description No autonegotiate — Autonegotiate not enabled. autonegotiate autonegotiate — Autonegotiate is enabled. The console port baud rate. console speed The IPv4 IP address to be used for ping-test after auto-init. ping-address The domain name used when performing DNS address resolution.
  • Page 175 Boot Option Files primary-image ftp://*:*@10.135.16.90/./images/auto-boot/solution/bothx.tim secondary-image ftp://*:*@10.135.16.90/./images/auto-boot/solution/bothx.tim tertiary-image ftp://*:*@10.135.16.90/./images/auto-boot/solution/both.tim primary-dns 135.254.244.204 dns-domain in.lucent.com ping 10.135.16.90 #uplinkA Port Settings: uplinkA-port 1/1/1 uplinkA-address 192.168.1.11/24 uplinkA-vlan uplinkA-route 10.135.0.0/16 next-hop 192.168.1.1 #uplinkB Port Settings: uplinkB-port 1/1/2 uplinkB-address uplinkB-vlan #System Settings: wait persist console-speed 115200 no console-disabled =============================================================================== *A:ALA#...
  • Page 176 Total Memory: 512MB Chassis Type: sas Card Type: badami_7210 TiMOS-L-0.0.I312 boot/mpc ALCATEL SAS-E 7210 Copyright (c) 2000-2009 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Fri Jan 2 04:26:32 IST 2009 by panosbld in /panosbld/ws/panos/main...
  • Page 177 To enable SNMP, execute the command 'config>system>snmp no shutdown'. TiMOS-B-1.0.B1-12 both/mpc ALCATEL SAS-E 7210 Copyright (c) 2000-2008 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Wed Jan 7 00:58:35 IST 2009 by builder in /builder/ws/panos/main...
  • Page 178 Show Commands Page 178 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 179: System Management

    System Management In This Chapter This chapter provides information about configuring basic system management parameters. Topics in this chapter include: • System Management Parameters on page 180 → System Information on page 180 − System Name on page 180 − System Contact on page 180 −...
  • Page 180: System Management Parameters

    System Basics Introduction System Management Parameters System management commands allow you to configure basic system management functions such as the system name, the router’s location and coordinates, and CLLI code as well as time zones, Network Time Protocol (NTP), Simple Network Time Protocol (SNTP) properties, CRON and synchronization properties.
  • Page 181: System Location

    ASCII printable text string of up to 80 characters. System Coordinates The system coordinates is the Alcatel-Lucent Chassis MIB tmnxChassisCoordinates object. This text string indicates the Global Positioning System (GPS) coordinates of the location of the chassis.
  • Page 182: Common Language Location Identifier

    The CLLI code is stored in the Alcatel-Lucent Chassis MIB tmnxChassisCLLICode object. The CLLI code can be any ASCII printable text string of up to 11 characters.
  • Page 183: System Time

    System Management System Time Routers are equipped with a real-time system clock for time keeping purposes. When set, the system clock always operates on Coordinated Universal Time (UTC), but the software has options for local time translation as well as system clock synchronization. System time parameters include: •...
  • Page 184 System Basics Introduction Table 17: System-defined Time Zones (Continued) Acronym Time Zone Name UTC Offset Moscow Time UTC +3 Moscow Summer Time UTC +4 US and Canada Atlantic Standard Time UTC -4 Atlantic Daylight Time UTC -3 Eastern Standard Time UTC -5 Eastern Daylight Saving Time UTC -4...
  • Page 185: Network Time Protocol (Ntp)

    System Management Network Time Protocol (NTP) NTP is the Network Time Protocol defined in RFC 1305, Network Time Protocol (Version 3) Specification, Implementation and Analysis. It allows for the participating network nodes to keep time more accurately and more importantly they can maintain time in a more synchronized fashion between all participating network nodes.
  • Page 186: Sntp Time Synchronization

    System Basics Introduction • NTP and SNTP — If both NTP and SNTP are enabled on the node, then SNTP transitions to an operationally down state. If NTP is removed from the configuration or shut down, then SNTP resumes an operationally up state. •...
  • Page 187: Cron

    System Management CRON The CRON feature supports the Service Assurance Agent (SAA) functions as well as the ability to schedule turning on and off policies to meet “Time of Day” requirements. CRON functionality includes the ability to specify the commands that need to be run, when they will be scheduled, including one-time only functionality (oneshot), interval and calendar functions, as well as where to store the output of the results.
  • Page 188: High Availability

    System Basics Introduction High Availability This section discusses the high availability (HA) routing options and features available to service providers that help diminish vulnerability at the network or service provider edge and alleviate the effect of a lengthy outage on IP networks. High availability is an important feature in service provider routing systems.
  • Page 189 • Fan module — 7210 SAS-D 128 MB devices support passive cooling. It has a fan to allow air circulation (and not cooling). By default the fan mode is set to 'auto'. In "auto" mode, by default, the software determines when to turn the fan 'on' and when to switch it 'off'.
  • Page 190: Temperature Threshold Alarm And Fan Speed

    NOTE: 7210 SAS-D and 7210 SAS-D ETR supports operation without the use of fan. It has a fan for air circulation (and not for cooling). By default, the fan is operated in auto mode. The operator has an option to turn it off. The 7210 SAS-D 128MB devices has a fan to provide air circulation. Page 190...
  • Page 191: Network Synchronization

    Note: Network synchronization options are available on 7210 SAS-D and 7210 SAS-E platforms. The available options on different 7210 platforms differ. Please read the section below and the release notes to know what options are supported on different 7210 platforms.
  • Page 192: Central Synchronization Sub-System

    System Basics Introduction The architecture shown in Figure 16 provides the following benefits: • Limits the need for high quality clocks at each network element and only requires that they reliably replicate input to remain traceable to its reference. • Uses reliable physical media to provide transport of the timing signal.
  • Page 193: Table 20: Revertive, Non-Revertive Timing Reference Switching Operation

    System Management On 7210 SAS-D ETR and 7210 SAS-K, , the recovered clock is able to derive the timing from any of the following references (also shown in the Figure 19 below): • Synchronous Ethernet ports • 1588v2/PTP slave port...
  • Page 194 System Basics Introduction Page 194 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 195: Synchronizations Option Available On 7210 Sas Platforms

    Synchronization Status Messages (SSM) Note: Synchronous status messages are supported only on 7210 SAS-D and 7210 SAS-K devices. The SSM provides a mechanism to allow the synchronization distribution network to both determine the quality level of the clock sourcing a given synchronization trail and to allow a network element to select the best of multiple input synchronization trails.
  • Page 196: Synchronous Ethernet

    Note: Please ensure that the SFP or XFP or SFP+ parts used with the SFP, XFP, and SFP+ ports support Synchronous Ethernet. Synchronous Ethernet using fixed copper ports is supported only on 7210 SAS-D ETR, and 7210 SAS-K platforms. The fixed copper ports can be used as a candidate reference (Master) or for distribution of recovered reference (Slave).
  • Page 197: Clock Source Quality Level Definitions

    System Management Synchronous Ethernet functionality (refer to ITU-T G.8262). The 802.3 standard link Master- Slave timing states must align with the desired direction of Synchronous Ethernet timing flow. When a fixed copper Ethernet port is specified as an input reference for the node or when it is removed as an input reference for the node, an 802.3 link auto-negotiation is triggered to ensure the link timing aligns properly.
  • Page 198: Table 24: Synchronization Message Coding And Source Priorities

    System Basics Introduction 0100 (ssua) 0100 (tnc) 0100 (ssua) 01111000 11111111 (TNC) 1101 (st3e) 01111100 11111111 (ST3E) 1000 (ssub) 1000 (ssub) 1010 (st3/eec2) 00010000 11111111 (ST3) 1011 (sec/eec1) 1011 (sec) 8. Lowest quality qualified in QL- enabled mode 1100 (smc) 00100010 11111111 (smc) 00101000 11111111...
  • Page 199 System Management 1000 (ssub) 1010 (st3/eec2) 1000 (ssub) 00010000 11111111 (st3) 1011 (sec/eec1) 1010 (st3/eec2) 1011 (sec) 00010000 11111111 (st3) 8. Lowest quality 1011 (sec/ eec1) 1100 (smc) 1011 (sec) 00100010 11111111 qualified in QL- (smc) enabled mode 1111 (dnu) 1100 (smc) 1111 (dnu) 00100010 11111111...
  • Page 200: Ieee 1588V2 Ptp

    System Basics Introduction IEEE 1588v2 PTP NOTE: This feature is applicable only to the 7210 SAS-D ETR device and 7210 SAS-K (both ETR and non-ETR). The Precision Time Protocol (PTP) is a timing-over-packet protocol defined in the IEEE 1588v2 standard 1588 PTP 2008.
  • Page 201: Figure 20: Peer Clocks

    System Management Figure 20: Peer Clocks The IEEE 1588v2 standard includes the concept of PTP profiles. These profiles are defined by industry groups or standards bodies that define how IEEE 1588v2 is to be used for a particular application. 7210 SAS currently supports two profiles: •...
  • Page 202: Table 25: Local Clock Parameters When Profile Is Set To Ieee1588-2008

    System Basics Introduction If the profile setting for the clock is ieee1588-2008, the precedence order for the best master selection algorithm is as follows: • priority1 • clock class • clock accuracy • PTP variance (offsetScaledLogVariance) • priority2 • clock identity •...
  • Page 203: Table 26: Local Clock Parameters When Profile Is Set To: Itu-Telecom-Freq

    System Management The 7210 SAS sets its local parameters as follows: Table 26: Local Clock Parameters When Profile is set to: itu-telecom-freq Parameter Value clockClass 80-110 – value corresponding to the QL out of the central clock of the 7210 SR as per Table 1/ G.8265.1 255 –...
  • Page 204: Ptp Clock Synchronization

    System Basics Introduction Figure 21: Messaging Sequence Between the PTP Slave Clock and PTP Master Clocks PTP Clock Synchronization The IEEE 1588v2 standard synchronizes the frequency and time from a master clock to one or more slave clocks over a packet stream. This packet-based synchronization can be over UDP/IP or Ethernet and can be multicast or unicast.
  • Page 205: Figure 22: Ptp Slave Clock And Master Clock Synchronization

    NOTE: The 7210 SAS-D ETR supports only two-step master port operation. All node types can operate slave ports that receive from a one-step or two-step master port.
  • Page 206: Figure 23: Using Ieee 1588V2 For Time Distribution For 7210 Sas-D Etr And 7210 Sas-K

    IEEE 1588v2 communications fail. When using IEEE 1588v2 for time distribution, the central clock should at a minimum have the PTP input reference enabled. Figure 23: Using IEEE 1588v2 For Time Distribution for 7210 SAS-D ETR and 7210 SAS-K Page 206...
  • Page 207: Performance Considerations

    System Management Performance Considerations Although IEEE 1588v2 can be used on a network that is not PTP-aware, the use of PTP-aware network elements (boundary clocks) within the packet switched network improves synchronization performance by reducing the impact of PDV between the grand master clock and the slave clock.
  • Page 208: Ptp Ordinary Slave Clock For Frequency

    System Basics Introduction State and statistics data for each master clock are available to assist in the detection of failures or unusual situations. PTP Ordinary Slave Clock For Frequency Traditionally, only clock frequency is required to ensure smooth transmission in a synchronous network.
  • Page 209: Configuration Guidelines And Restrictions For Ptp On 7210 Sas-Detr And 7210 Sas-K

    Configuration guidelines and restrictions for PTP on 7210 SAS-D ETR and 7210 SAS-K • On 7210 SAS-D ETR, use of PTP and syncE as a reference simultaneously is not allowed. User can configure either syncE as a reference or PTP as a reference, but not both together.
  • Page 210: Configuration To Change Reference From Synce To Ptp On 7210 Sas-D Etr

    • • On 7210 SAS-D ETR it is highly recommended to use PTP only in hybrid mode. It allows users to use reduced PTP packet rates on these platforms and scale better. Configuration to change reference from SyncE to PTP on 7210 SAS-D ETR The following are the configuration steps to change reference from SyncE to PTP.
  • Page 211 System Management ref-order ref1 ref2 --------> Or, the ref-order you want [But Must be configured] revert ---------------------> If you want ref-order you have setup to take effect ql-selection -------------------> Optional, if we need Quality to be considered. config> system> sync-if-timing> commit Note : Now the frequency is provided by SyncE and TOD is provided by PTP [configure >system >ptp >no shutdown].
  • Page 212: Management Of 1830 Vwm

    System Basics Introduction Management of 1830 VWM Note: This feature is supported only on 7210 SAS-E. It is not supported on 7210 SAS-D and 7210 SAS-K devices. The 7210 SAS supports use and management of the 1830 VWM CWDM and 1830 VWM DWDM clip-on device.
  • Page 213: Feature Description

    System Management Figure 26: Optical Ring with 7210 SAS and 1830 VWM Passive Optical unit In the above Figure 26, there are 5 CWDM channels that are multiplexed over a single fiber. There are two types of ring locations. One is a channel termination location, with the 1830 PSS-32 that optically terminates all the channels using either the 4-channel or the 8-channel termination module.
  • Page 214: 1830 Cwdm Shelf Layout And Description

    System Basics Introduction supports provisioning of cards inserted into the slots available on the 1830 devices. The user must provision the card and card-type (also known as, module type) before the card can be managed by the 7210 SAS. The 7210 SAS detects and reports mismatch in provisioning of the card. It also detects and reports insertion and removal of the card/module from the slot on the 1830 device.
  • Page 215: 1830 Dwdm Shelf Layout And Description

    System Management Figure 27: 1830 CWDM shelf layout The Slot#1 in the figure accepts only the controller card and is named using the acronym EC-CW for 1830 CWDM device. The 7210 does not require provisioning of this card. This card type is implicitly specified when user configures the 1830 VWM shelf type.
  • Page 216 System Basics Introduction controllers can be used in the other chassis connected to the first device in a stacked configuration. In other words, the first 1830 DWDM device that is connected to the OMC port or the USB port of the 7210 node cannot be a passive 1830 DWDM device, while subsequent chassis in the stacked configuration can be equipped with passive DWDM controllers.
  • Page 217: Configuration Guidelines And Restrictions

    System Management Configuration Guidelines and Restrictions The 7210 SAS supports management of the 1830 VWM CWDM/DWDM clip-on device, inventory management and displays the clip-on device details such as part numbers, clip-on type, manufacturing dates, firmware revision, status of alarms It also supports provisioning of the modules that can be inserted into the slot available on the 1830 device.
  • Page 218: Led Functionality

    System Basics Introduction configuration and is supported on 7210. LED functionality Table 29 shows the LED functionality of the device: Table 29: LED functionality for 7210 and 1830 VWM (CWDM) Events 7210 Major Alarm Optical shelf Con- Optical Shelf Line troller LED card LED Shelf Admin Up and...
  • Page 219: Table 30: Led Functionality For 7210 And 1830 Vwm (Dwdm)

    System Management Table 30: LED functionality for 7210 and 1830 VWM (DWDM) Events 7210 Major Alarm Optical shelf Con- Optical Shelf Line troller LED card LED Shelf Admin Up and No Color Green Amber/ Green based on shelf is physically whether line card connected to 7210.
  • Page 220: Link Layer Discovery Protocol (Lldp)

    System Basics Introduction Link Layer Discovery Protocol (LLDP) The IEEE 802.1ab Link Layer Discovery Protocol (LLDP) is a uni-directional protocol that uses the MAC layer to transmit specific information related to the capabilities and status of the local device. The LLDP can send as well as receive information from a remote device stored in the related MIB(s).
  • Page 221: Figure 29: Lldp Internal Architecture For A Network Node

    System Management information. The receiving LLDP agent discards all information related to the sending LLDP agent after the time interval indicated in the TTL field is complete. Note: A TTL value of zero can be used to signal that the sending LLDP port has initiated a port shutdown procedure.
  • Page 222: Figure 30: Customer Use Example For Lldp

    System Basics Introduction In order to detect and address network problems and inconsistencies in the configuration, the network operators can discover the topology information using LLDP. The Standard-based tools address the complex network scenarios where multiple devices from different vendors are interconnected using Ethernet interfaces.
  • Page 223: System Resource Allocation

    System Management System Resource Allocation Allocation of Ingress Internal TCAM resources In current releases, the system statically allocates ingress TCAM resources for use by SAP ingress QoS classification, SAP ingress access control list (ACLs), Identifying and sending CFM OAM packets to CPU for local processing, and so on. The resource allocation is not user configurable. With introduction of new capabilities such as IPv6 classification, UP MEP support, and G8032- fast-flood, the static allocation of resources by software does not meet requirements of different customers, who typically want to use different features.
  • Page 224: Allocation Of Egress Internal Tcam Resources

    Please see the CLI descriptions and the feature description in the respective user guides. Allocation of Egress Internal TCAM resources Note: This feature is supported only on 7210 SAS-E. It is not supported on 7210 SAS-D and 7210 SAS-K devices.
  • Page 225: System Resource Allocation Examples

    System Management System Resource Allocation Examples NOTE: On 7210 SAS-K, user needs to allocate resources among SAP ingerss QoS and ingress ACLS. They do not need to further allocate resources individually for MAC and IPv4 criteria. Example one: config> system> resource-profile acl-sap-ingress mac-match-enable max ipv4-match-enable 1...
  • Page 226 System Basics Introduction • System allocates 3 chunks for use by the SAP ingress ACL entries. These resources are available for use with mac-criteria, ipv4-criteria and ipv6-64-bit match criteria. • System allocates 1 chunk for use by SAP ingress ACL entries using ipv4-criteria. The system fails the configuration when the number of ACL entries using ipv4-criteria exceeds the configured limit (that is, the system does not allocate in excess of the configured limit of 1 chunk).
  • Page 227: System Configuration Process Overview

    System Management System Configuration Process Overview Figure 31 displays the process to provision basic system parameters. START CONFIGURE SYSTEM INFORMATION CONFIGURE TIME PARAMETERS Figure 31: System Configuration and Implementation Flow 7210 SAS D, E, K OS Basic System Configuration Guide Page 227...
  • Page 228: Configuration Notes

    System Basics Introduction Configuration Notes This section describes system configuration caveats. General • The 7210 SAS device must be properly initialized and the boot loader and BOF files successfully executed in order to access the CLI. Page 228 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 229: Configuring System Management With Cli

    System Management Configuring System Management with CLI This section provides information about configuring system management features with CLI. Topics in this chapter include: • Basic System Configuration on page 231 • Common Configuration Tasks on page 232 • System Information on page 233 →...
  • Page 230: System Management

    System Management System Management Saving Configurations Whenever configuration changes are made, the modified configuration must be saved so the changes will not be lost when the system is rebooted. The system uses the configuration and image files, as well as other operational parameters necessary for system initialization, according to the locations specified in the boot option file (BOF) parameters.
  • Page 231: Basic System Configuration

    System Management Basic System Configuration This section provides information to configure system parameters and provides configuration examples of common configuration tasks. The minimal system parameters that should be configured are: • System Information Parameters on page 234 • System Time Elements on page 237 The following example displays a basic system configuration: A:ALA-12>config>system# info #------------------------------------------...
  • Page 232: Common Configuration Tasks

    Common Configuration Tasks Common Configuration Tasks This section provides a brief overview of the tasks that must be performed to configure system parameters and provides the CLI commands. • System Information on page 233 → Name on page 234 → Contact on page 234 →...
  • Page 233: System Information

    System Management System Information This section covers the basic system information parameters to configure the physical location of the router, contact information, location information such as the place the router is located such as an address, floor, room number, etc., global positioning system (GPS) coordinates, and system name.
  • Page 234: System Information Parameters

    Common Configuration Tasks System Information Parameters Name Use the em command to configure a name for the device. The name is used in the prompt syst string. Only one system name can be configured, if multiple system names are configured the last one encountered overwrites the previous entry.
  • Page 235 System Management Location Use the command to specify the system location of the device. For example, enter the location city, building address, floor, room number, etc., where the router is located. Use the following CLI syntax to configure the location: CLI Syntax: config>system location location Example...
  • Page 236: Coordinates

    Common Configuration Tasks Coordinates Use the optional command to specify the GPS location of the device. If the string coordinates contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Use the following CLI syntax to configure the location: CLI Syntax: config>system coordinates coordinates Example...
  • Page 237: System Time Elements

    System Management System Time Elements The system clock maintains time according to Coordinated Universal Time (UTC). Configure information time zone and summer time (daylight savings time) parameters to correctly display time according to the local time zone. Time elements include: •...
  • Page 238: Table 31: System-Defined Time Zones

    Common Configuration Tasks Table 31: System-defined Time Zones Acronym Time Zone Name UTC Offset Europe: Greenwich Mean Time Western Europe Time Western Europe Summer Time UTC +1 hour WEST Central Europe Time UTC +1 hour Central Europe Summer Time UTC +2 hours CEST Eastern Europe Time UTC +2 hours...
  • Page 239 System Management Summer Time Conditions The config>system>time>dst-zone context configures the start and end dates and offset for summer time or daylight savings time to override system defaults or for user defined time zones. When configured, the time will be adjusted by adding the configured offset when summer time starts and subtracting the configured offset when summer time ends.
  • Page 240 Common Configuration Tasks Network Time Protocol (NTP) is defined in RFC 1305, Network Time Protocol (Version 3) Specification, Implementation and Analysis. It allows for participating network nodes to keep time more accurately and maintain time in a synchronized manner between all participating network nodes.
  • Page 241 System Management Authentication-key This command configures an authentication key-id, key type, and key used to authenticate NTP PDUs sent to and received from other network elements participating in the NTP protocol. For authentication to work, the authentication key-id, authentication type and authentication key value must match.
  • Page 242 Common Configuration Tasks exit A:sim1>config>system>time# The following example in the config context shows NTP enabled with the broadcast command configured. At this level, the NTP broadcast commands are displayed at the end of the output after the router interfaces are shown. A:sim1>config info ..
  • Page 243 System Management NTP-Server This command configures the node to assume the role of an NTP server. Unless the server command is used this node will function as an NTP client only and will not distribute the time to downstream network elements. If an authentication key-id is specified in this command, the NTP server requires client packets to be authenticated.
  • Page 244 Common Configuration Tasks Server The Server command is used when the node should operate in client mode with the NTP server specified in the address field. Use the no form of this command to remove the server with the specified address from the configuration. Up to five NTP servers can be configured.
  • Page 245 System Management SNTP SNTP is a compact, client-only version of the NTP. SNTP can only receive the time from SNTP/ NTP servers; it cannot be used to provide time services to other systems. SNTP can be configured in either broadcast or unicast client mode. SNTP time elements include: •...
  • Page 246 Common Configuration Tasks Server-address The server-address command configures an SNTP server for SNTP unicast client mode. CLI Syntax: config>system>time>sntp# config>system>time>sntp# server-address ip-address version version- number] [normal|preferred] [interval seconds] Example config>system>time>sntp# config>system>time# server-address 10.10.0.94 version 1 preferred interval 100 The following example shows SNTP enabled with the server-address command configured. A:ALA-12>config>system>time# info ---------------------------------------------- sntp...
  • Page 247 System Management CRON The CRON command supports the Service Assurance Agent (SAA) functions as well as the ability to schedule turning on and off policies to meet “Time of Day” requirements. CRON functionality includes the ability to specify the commands that need to be run, when they will be scheduled, including one-time only functionality (oneshot), interval and calendar functions, as well as where to store the output of the results.
  • Page 248 Common Configuration Tasks no shutdown exit action "test" results "ftp://172.22.184.249/./sim1/test-results" no shutdown exit ---------------------------------------------- A:sim1>config>cron# script Schedule The schedule function configures the type of schedule to run, including one-time only (oneshot), periodic or calendar-based runs. All runs are determined by month, day of month or weekday, hour, minute and interval (seconds).
  • Page 249 System Management end-time 2007/07/17 12:00 exit ---------------------------------------------- *A:SR-3>config>cron# Script The script command opens a new nodal context which contains information on a script. CLI Syntax: config>cron script script-name [owner script-owner] description description-string location file-url shutdown Example config>cron# script test config>cron>script# The following example names a script “test”: A:sim1>config>cron# info ----------------------------------------------...
  • Page 250: Time Range

    Common Configuration Tasks Time Range ACLs and QoS policy configurations may be enhanced to support time based matching. CRON configuration includes time matching with the 'schedule' sub-command. Schedules are based on events; time-range defines an end-time and will be used as a match criteria. Time range elements include: •...
  • Page 251 System Management The following example shows an absolute time range beginning on May 5, 2006 at 11:00 and ending May 6, 2006 at 11:01: A:sim1>config>cron>time-range# show cron time-range detail =============================================================================== Cron time-range details =============================================================================== Name : test1 Triggers Status : Inactive Absolute : start 2006/05/05,11:00 end 2006/05/06,11:01 ===============================================================================...
  • Page 252 Common Configuration Tasks Weekdays The weekdays command configures the start and end of a periodic schedule for weekdays (Monday through Friday). CLI Syntax: config>cron>time-range$ weekdays start time-of-day end time-of-day Example config>cron>time-range$ weekdays start 11:00 end 12:00 config>cron>time-range$ The following command shows a time range beginning at 11:00 and ending at 12:00. This schedule runs all weekdays during this time period.
  • Page 253 System Management Status : Inactive Periodic : weekend Start 11:00 End 12:00 Weekly The weekly command configures the start and end of a periodic schedule for the same day every week, for example, every Friday. The start and end dates must be the same. The resolution must be at least one minute apart, for example, start at 11:00 and end at 11:01.
  • Page 254 Common Configuration Tasks Time of Day Time of Day (TOD) suites are useful when configuring many types of time-based policies or when a large number of subscribers or SAPs require the same type of TOD changes. The TOD suite may be configured while using specific ingress or egress ACLs or QoS policies, and is an enhancement of the ingress and egress CLI trees.
  • Page 255 System Management Filters In a TOD suite, filters that have entries with time-ranges may not be selected. Similarly, filter entries with a time-range may not be created while a TOD suite refers to that filter. QoS policies and filters referred to by a TOD suite must have scope “template” (default). The following syntax is used to configure TOD-suite egress parameters.
  • Page 256 Common Configuration Tasks Ingress This command is an enhancement for specific ingress policies including filter lists and QoS policies. Use this command to create time-range based associations of previously created filter lists QoS policies. Multiple policies may be included and each must be assigned a different priority;...
  • Page 257 System Management Example config>cron>tod-suite$ ingress qos 101 config>cron>tod-suite$ The following command shows an association with ingress QoS-SAP policy 101. A:sim1>config>qos# sap-egress 101 create A:sim1>config>cron>tod-suite# ingress qos 101 A:sim1>config>cron>tod-suite# info detail ---------------------------------------------- no description ingress qos 101 exit ---------------------------------------------- A:sim1>config>cron>tod-suite# 7210 SAS D, E, K OS Basic System Configuration Guide Page 257...
  • Page 258: Configuring Backup Copies

    Common Configuration Tasks Configuring Backup Copies command allows you to specify the maximum number of backup versions config-backup of configuration and index files kept in the primary location. For example, assume the config-backup count is set to 5 and the configuration file is called xyz.cfg.
  • Page 259: System Administration Parameters

    System Management System Administration Parameters Use the CLI syntax displayed below to configure various system administration parameters. Administrative parameters include: • Validating the Golden Bootstrap Image on page 259 • Updating the Golden Bootstrap Image on page 260 • Disconnect on page 260 •...
  • Page 260: Updating The Golden Bootstrap Image

    SAS E bootstrap image, and updates the golden bootstrap image with the contents of this file. Note: Only on 7210 SAS-D newer platforms, the admin>update-golden-bootstrap CLI command does not update the golden-bootstrap image with the boot.tim specified in the parameter value, if the boot.tim is not a new image.
  • Page 261: Set-Time

    System Management Set-time Use the set-time command to set the system date and time. The time entered should be accurate for the time zone configured for the system. The system will convert the local time to UTC before saving to the system clock which is always set to UTC. If SNTP or NTP is enabled ( ) then this command cannot be used.
  • Page 262 System Administration Parameters packet-size 1500 general-port 161 exit login-control inbound-max-sessions 3 exit telnet inbound-max-sessions 5 outbound-max-sessions 2 exit idle-timeout 1440 pre-login-message "Property of Service Routing Inc.Unauthorized access prohib- ited." motd text “Notice to all users: Software upgrade scheduled 3/2 1:00 AM" exit security management-access-filter...
  • Page 263: Tech-Support

    System Management Tech-support command creates a system core dump. NOTE: This command should only tech-support be used with explicit authorization and direction from Alcatel-Lucent’s Technical Assistance Center (TAC). Save command saves the running configuration to a configuration file. When the...
  • Page 264: Reboot

    WARNING: Configuration and/or Boot options may have changed since the last save. Are you sure you want to reset the bof and reboot (y/n)? Y Resetting...OK Alcatel-Lucent 7210 Boot ROM. Copyright 2000-2008 Alcatel-Lucent. All rights reserved. All use is subject to applicable license agreements. Page 264...
  • Page 265: Post-Boot Configuration Extension Files

    System Management Post-Boot Configuration Extension Files Two post-boot configuration extension files are supported and are triggered when either a successful or failed boot configuration file is processed. The commands specify URLs for the CLI scripts to be run following the completion of the boot-up configuration. A URL must be specified or no action is taken.
  • Page 266 System Administration Parameters #-------------------------------------------------- echo "System Security Configuration" #-------------------------------------------------- security hash-control read-version all write-version 1 telnet-server ftp-server snmp community "private" rwa version both community "public" r version both exit source-address application ftp 10.135.16.97 application snmptrap 10.135.16.97 application ping 10.135.16.97 application dns 10.135.16.97 exit exit ----------------------------------------------...
  • Page 267 MAJOR: CLI #1009 An error occurred while processing a CLI command - File ftp://test:test@192.168.xx.xxx/./fail.cfg, Line 5: Command "abc log" failed. TiMOS-B-x.0.Rx both/hops ALCATEL Copyright (c) 2000-20011 Alcatel-Lucent. All rights reserved. All use subject to applicable license agreements. Built on Thu Nov 207 19:19:11 PST 2008 by builder in /rel5x.0/b1/Rx/panos/main...
  • Page 268: System Timing

    When synchronous Ethernet is enabled, the operator can select an Ethernet port as a candidate for timing reference. The timing information recovered from this port is used to time the system. Note: In the current release the derived time is distributed only through other Ethernet ports. CLI Syntax for 7210 SAS-D: *A:sas-d>config>system>sync-if-timing# info detail ----------------------------------------------...
  • Page 269 System Management ort 2/1/1 MINOR: CLI The sync-if-timing must be in edit mode by calling begin before any changes can be made. MINOR: CLI Unable to set source port for ref1 to 2/1/1. A:ALA-12>config>system>sync-if-timing>ref1# 7210 SAS D, E, K OS Basic System Configuration Guide Page 269...
  • Page 270: Configuring Timing References

    System Timing Configuring Timing References Configuration Guidelines Ref1 has to be configured to use one of the ports from 1/1/1 up to 1/1/4 and ref2 should be configured to use either 1/1/5 or 1/1/6. The software enforces this check. The ports 1/1/7 up to 1/1/ 10 can be configured as either ref1 or ref2.
  • Page 271: Using The Revert Command

    System Management Using the Revert Command If the current reference goes offline or becomes unstable the revert command allows the clock to revert to a higher-priority reference. When revert is ‘switching enabled’ a valid timing reference of the highest priority is used. If a reference with a higher priority becomes valid, a reference switch over to that reference is initiated.
  • Page 272: Configuring System Monitoring Thresholds

    Configuring System Monitoring Thresholds Configuring System Monitoring Thresholds Creating Events The event command controls the generation and notification of threshold crossing events configured with the alarm command. When a threshold crossing event is triggered, the rmon event configuration optionally specifies whether an entry in the RMON-MIB log table be created to record the occurrence of the event.
  • Page 273 System Management To create events, use the following CLI: Example config>system>thresholds# cflash-cap-warn cf1-B: rising- threshold 2000000 falling-threshold 1999900 interval 240 trap startup- alarm either Example config>system>thresholds# memory-use-alarm rising-threshold 50000000 falling-threshold 45999999 interval 500 both startup-alarm either Example config>system>thresh# rmon Example config>system>thresh>rmon# event 5 both description "alarm testing"...
  • Page 274: System Alarm Contact Inputs

    Configuring an Alarm Input in 7210 SAS-D and 7210 SAS-K devices Unlike the 7210 SAS-E, the 7210 SAS-D and 7210 SAS-K does not support alarm contact inputs, instead, it provides an option to configure the console port as an alarm input pin. A single alarm input pin can be enabled for use with the console port, allowing operators to monitor external events and alert the operator.
  • Page 275: Configuring 1830 Vwm

    System Management Configuring 1830 VWM The following output displays creation of vwm-shelf: NOTE: The card 1 correspond to slot #1 and card 2 corresponds to slot #2 on the 1830 CWDM device. The optical modules or line cards are inserted into these slots. *A:NS1333C2676# configure system vwm-shelf 3 vwm-type ec-cw create *A:NS1333C2676>configure>system>vwm-shelf$ info ----------------------------------------------...
  • Page 276 Configuring 1830 VWM Shelf-ID USB/ Shelf Admin Oper Number of Type State State Equipped slots --------------------------------------------------------------------------- CWDM =========================================================================== Slot Summary =========================================================================== Slot-ID Provisioned Equipped Admin Oper Type Type State State --------------------------------------------------------------------------- SFC1D SFC1D SFC2A&B SFC2A&B CWDM CWDM =========================================================================== 1830 VWM Shelf Controller-A Hardware Data =========================================================================== No of Slots Part Number...
  • Page 277 System Management *7210SAS# The following output displays deletion of vwm-shelf: *7210SAS>configure>system>vwm-shelf$ info ---------------------------------------------- card 2 card-type SF ---------------------------------------------- 7210SAS>configure>system>vwm-shelf$ *7210SAS>configure>system>vwm-shelf$ info ---------------------------------------------- card 2 card-type SFC1D no shutdown exit no shutdown ---------------------------------------------- *A AS-M>configure>system>vwm-shelf$ card 2 no card-type *A AS-M>configure>system>vwm-shelf$ info ---------------------------------------------- no shutdown ----------------------------------------------...
  • Page 278: Configuring Lldp

    Configuring LLDP Configuring LLDP The following output displays LLDP defaults: A:7210-SAS>config>system>lldp# info detail ---------------------------------------------- no tx-interval no tx-hold-multiplier no reinit-delay no notification-interval no tx-credit-max no message-fast-tx no message-fast-tx-init no shutdown ---------------------------------------------- The following example displays an LLDP port configuration: *A:7210-SAS>config>port>ethernet>lldp# info ---------------------------------------------- dest-mac nearest-bridge admin-status tx-rx...
  • Page 279 System Resource-Profile Commands for 7210 SAS-E on page 292 • System Resource-Profile Commands for 7210 SAS-K on page 291 • Fan Controller Commands for 7210 SAS-D and 7210 SAS-D ETR variant with 128MB flash on page • Show Commands on page 294 •...
  • Page 280 Command Hierarchies — boot-good-exec — chassis — clli-code clli-code — no clli-code — config-backup count — no config-backup — contact contact-name — no contact — coordinates coordinates — no coordinates — lacp-system-priority lacp-system-priority — no lacp-system-priority — lldp — location location —...
  • Page 281 System Management System Alarm Commands config — system — thresholds — kb-memory-use-alarm cflash-id rising-threshold threshold [falling-threshold thresh- old] interval seconds [rmon-event-type] [startup-alarm alarm-type] — no kb-memory-use-alarm cflash-id — cflash-cap-warn cflash-id rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type] — no cflash-cap-warn cflash-id —...
  • Page 282 Command Hierarchies PTP Commands (applicable only to 7210 SAS-D ETR and 7210 SAS-K) config — system — ptp — clock — freq-source freq-source — no freq-source — clock-type boundary — clock-type ordinary {slave} — [no] domain domain — [no] log-sync-interval value —...
  • Page 283: System Management

    System Management System Time Commands root — admin — set-time [date] [time] config — system — time — [no] — [no] authentication-check — authentication-key key-id key key [hash | hash2] type {des | message-digest} — no authentication-keykey-id — [no] broadcast [router router-name] {interface ip-int-name} [key-id key-id] [version version] [ttl ttl] —...
  • Page 284 Command Hierarchies Cron Commands config — [no] cron — [no] action action-name [owner owner-name] — expire-time {seconds | forever} — lifetime {seconds | forever} — max-completed unsigned — [no] results file-url — [no] script script-name [owner owner-name] — [no]shutdown — [no] schedule schedule-name [owner owner-name] —...
  • Page 285 System Management — policy-id [time-range time-range-name] [priority priority] — no policy-id [time-range time-range-name] 7210 SAS D, E, K OS Basic System Configuration Guide Page 285...
  • Page 286 Command Hierarchies System Administration (Admin) Commands root — admin — auto-init stop — check-golden-bootstrap — debug-save file-url — disconnect {address ip-address | username user-name | console | telnet | ftp | ssh} — display-config [detail | index] — [no] enable-tech —...
  • Page 287 System Management System Alarm Contact Commands config — system — alarm-contact-input alarm-contact-input-id — [no] alarm-output-severity [critical | major | minor | none] — [no] clear-alarm-msg {alarm-msg-txt} — description description-string — normal-state [open | closed] — [no] shutdown — [no] trigger-alarm-msg {alarm-msg-txt} System Console commands config...
  • Page 288 Command Hierarchies System Synchronization Commands config — system — sync-if-timing — abort — begin — commit — ref-order first second third — no ref-order — — ql-override {prs | stu | st2 | tnc | st3e | st3 | prc | ssua | ssub | sec} —...
  • Page 289 System Management LLDP System Commands configure — system — lldp — message-fast-tx time — no message-fast-tx — message-fast-tx-init count — no message-fast-tx-init — notification-interval time — no notification-interval — reinit-delay time — no reinit-delay — [no] shutdown — tx-credit-max count —...
  • Page 290 Command Hierarchies System Resource-Profile Commands for 7210 SAS-D configure — system — resource-profile — egress-internal-tcam — acl-sap-egress [num-resources] — no acl-sap-egress — [no] ipv6-128bit-match-enable num-resources — mac-ipv4-match-enable num-resources — no mac-ipv4-match-enable — mac-ipv6-64bit-match-enable num-resources — no mac-ipv6-64bit-match-enable — mac-match-enable num-resources —...
  • Page 291 System Management System Resource-Profile Commands for 7210 SAS-K configure — system — resource-profile — egress-internal-tcam — acl-sap-egress [num-resources] — no acl-sap-egress — mac-ipv4-ipv6-128-match-enable num-resources — no mac-ipv4-ipv6-128-match-enable — ingress-internal-tcam — acl-sap-ingress [num-resources] — no acl-sap-ingress — mac-ipv4-ipv6-128-match-enable num-resources — no mac-ipv4-ipv6-128-match-enable —...
  • Page 292 Command Hierarchies System Resource-Profile Commands for 7210 SAS-E configure — system — resource-profile — ingress-internal-tcam — acl-sap-ingress [num-resources] — no acl-sap-ingress — ipv4-ipv6-128-match-enable num-resources — no ipv4-ipv6-128-match-enable — ipv4-match-enable num-resources — no ipv4-match-enable — ipv6-64-only-match-enable num-resources — no ipv6-64-only-match-enable — mac-match-enable num-resources —...
  • Page 293 System Management Fan Controller Commands for 7210 SAS-D and 7210 SAS-D ETR variant with 128MB flash configure — system — {on | off | auto} 7210 SAS D, E, K OS Basic System Configuration Guide Page 293...
  • Page 294 [detail] — alarm-contact-input — chassis [environment] [power-supply] (The ‘environment’ option is supported only on 7210 SAS-E and 7210 SAS-D. The ‘power-supply’ option is applicable only to 7210 SAS-D ETR) — cron — action action-name [owner owner-name] — action run-history [run-state] —...
  • Page 295 — no force-reference — [no] system — [router router-name] [interface ip-int-name] Fan controller debug command (applicable only to 7210 SAS-D and 7210 SAS-D ETR variant with 128MB flash) tools — dump — fan-stats 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 296 Command Hierarchies Page 296 7210 SAS D, E, K OS Basic System Configuration...
  • Page 297 System Management System Command Reference Descriptions Generic Commands shutdown Syntax [no] shutdown Context config>system>time>ntp config>system>time>sntp config>cron>action config>cron>sched config>cron>script config>system>alarms Description This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. The operational state of the entity is disabled as well as the operational state of any entities contained within.
  • Page 298 System Information Commands System Information Commands boot-bad-exec Syntax boot-bad-exec file-url no boot-bad-exec Context config>system Description Use this command to configure a URL for a CLI script to exec following a failure of a boot-up configuration. The command specifies a URL for the CLI scripts to be run following the completion of the boot-up configuration.
  • Page 299 System Management Values file url: local-url | remote-url: 255 chars max local-url: [<cflash-id/> | <usb-flash-id>][file-path] remote-url: [{ftp://} login:pswd@remote-locn/][file-path] remote-locn [ hostname | ipv4-address ] ipv4-address a.b.c.d cflash-id: cf1: usb-flash-id uf1: Related exec command on page 51 — This command executes the contents of a text file as if they were CLI Commands commands entered at the console.
  • Page 300 Platforms Supported: 7210 SAS-D and 7210 SAS-K. This command provides an option to the user to use the console port on the 7210 SAS-D/K as an alarm-input pin. When this command is executed, the console port can be used as an alarm input pin.
  • Page 301 System Management A single alarm-input pin can be enabled for use with the console port, allowing operators to monitor external events and alert the operator. For this command to take effect, the console must be enabled in the BOF. The RXD and TXD pins of the console input is used to provide a single alarm input pin functionality and is used by the software to detect external events.
  • Page 302 System Information Commands Default none — No coordinates are configured. Parameters coordinates — The coordinates describing the device location character string. The string may be up to 80 characters long. Any printable, seven-bit ASCII characters can be used within the string. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
  • Page 303 Description Platforms Supported: 7210 SAS-D and 7210 SAS-K. This command creates a system-wide group name which can be used to associate a number of service objects (for example, ports). The status of the group is derived from the status of its members. The status of the group can then be used to influence the status of non-member objects.
  • Page 304 Values Keyword hold-time Syntax hold-time Context config>system>oper-group Description Platforms Supported: 7210 SAS-D and 7210 SAS-K. This command enables the context to configure hold time information. group-down Syntax [no] group-down time in seconds Context config>system>oper-group>hold-time Description Platforms Supported: 7210 SAS-D and 7210 SAS-K.
  • Page 305 This command enables the context to configure a power-supply. On 7210 SAS-D ETR, by default, the software does not generate any traps or alarms for PS2, when the external power- supply failure has been detected. The user is provided with an option to configure the external backup power-supply type.
  • Page 306 System Information Commands type — Identifies the type of power-supply. Values keywords - dc|ac|none power-supply Syntax power-supply [power-supply-id] type Context config>system Description Platforms Supported: 7210 SAS-K ETR. This command enables the context to configure the external power-supply type and also provide an option to the user to enable or disable notifications related to power supply.
  • Page 307 System Management vwm-shelf Syntax [no] vwm-shelf vwm-shelf-id [vwm-type vwm-type] [create] Context config>system Description Platforms Supported: 7210 SAS-E. Provides the context to configure the shelf information for 1830 VWM clip-on device. The user must create the VWM clip-on device and provision the shelf ID to allow the 7210 software to communicate with the shelf and retrieve information.
  • Page 308 System Information Commands connected through OMC interface shelf-id can be 1-7 and if connected through USB interface shelf-id should be 0. • If the main shelf has any other shelf-id (that is 1-7), the shelf will not become operational. create — Keyword used to create the vwm-shelf-id. card Syntax card card-id...
  • Page 309 System Management card-type Syntax [no] card-type card-type Context config>system>vwm-shelf>card Description Platforms Supported: 7210 SAS-E. This command provides the user a better control over the modules plugged into the 1830 CWDM device slots. The user can pre-provision acceptable modules by configuring the card-type parameter with the appropriate card-type vwm-acronym.
  • Page 310: Table 32: Card Type Acronyms For 1830 Cwdm Devices

    System Information Commands ascii-string - can use ASCII alphabets or numbers. Valid card-type acronyms is listed in the table below. The following table lists the acronyms defined by the optical group. For more information, see the Product overview guide for 1830 VWM. This is used to pre-provision the acceptable modules that can be equipped in the slots of the clip-on device.
  • Page 311 System Management Module Description Acronym 1830VWM EC-DW Active (AA variant) EC-DWA Remote Filer Modules 1830VWM Remote Filter 8CH (AA VAR) SFD8A_R 1830VWM Remote Filter 8CH (AB Var) SFD8B_R 1830VWM Remote Filter 8CH (AC Var) SFD8C_R 1830VWM Remote Filter 8CH (AD Var) SFD8D_R 1830VWM Remote Filter 4CH (AE Var) SFD4A_R...
  • Page 312 System Information Commands Module Description Acronym 1830VWM Remote Filter 2CH (BD Var) SFD2P_R 1830 VWM SSY SFD Automatic SFD2Q_R 2CH (BC Var) 1830 VWM SSY SFD Automatic SFD2R_R 2CH (BD Var) DWDM Filters with manual control 1830VWM Manual Filter 8CH (AAVar) SFD8A 1830VWM Manual Filter 8CH (AB Var) SFD8B...
  • Page 313 System Management Module Description Acronym 1830VWM Manual Filter 2CH (AX Var) SFD2L 1830VWM Manual Filter 2CH (AY Var) SFD2M 1830VWM Manual Filter 2CH (AZ Var) SFD2N 1830VWM Manual Filter 2CH (BAVar) SFD2O 1830VWM Manual Filter 2CH (BB Var) SFD2P 1830VWM Manual Filter 2CH (BC Var) SFD2Q 1830VWM Manual Filter 2CH (BD Var) SFD2R...
  • Page 314 System Alarm Commands System Alarm Commands alarm Syntax alarm rmon-alarm-id variable-oid oid-string interval seconds [sample-type] [startup-alarm alarm-type] [rising-event rmon-event-id rising-threshold threshold] [falling-event rmon- event-id falling threshold threshold] [owner owner-string] no alarm rmon-alarm-id Context config>system>thresholds>rmon Description The alarm command configures an entry in the RMON-MIB alarm Table. The alarm command controls the monitoring and triggering of threshold crossing events.
  • Page 315 System Management sample-type — Specifies the method of sampling the selected variable and calculating the value to be compared against the thresholds. Default Absolute Values absolute — Specifies that the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval. delta —...
  • Page 316 System Alarm Commands falling-threshold threshold — Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated ’startup-alarm’...
  • Page 317 System Management falling-threshold threshold — Specifies a threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single threshold crossing event will be generated. A single threshold crossing event will also be generated if the first sample taken is less than or equal to this threshold and the associated startup-alarm is equal to falling or either.
  • Page 318 System Alarm Commands Description This command configures memory usage, in kilobytes, for warning thresholds Default none Parameters rising-threshold threshold — Specifies a threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single threshold crossing event will be generated.
  • Page 319 System Management less than or equal to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold crossing event is generated. Values rising, falling, either Default either cflash-cap-alarm Syntax cflash-cap-alarm cflash-id rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type] no cflash-cap-alarm cflash-id Context...
  • Page 320 System Alarm Commands rmon-event-type — Specifies the type of notification action to be taken when this event occurs. Values log — An entry is made in the RMON-MIB log table for each event occurrence. This does not create a TiMOS logger entry. The RMON-MIB log table entries can be viewed using the show>system>thresholds CLI command.
  • Page 321 System Management threshold crossing event will also be generated if the first sample taken is greater than or equal to this threshold and the associated startup-alarm is equal to rising or either. After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling- threshold value.
  • Page 322 System Alarm Commands Configuration example: cflash-cap-warn cf1-B: rising-threshold 2000000 falling-threshold 1999900 interval 240 rmon- event-type trap start-alarm either event Syntax event rmon-event-id [event-type] [description description-string] [owner owner-string] no event rmon-event-id Context config>system>thresholds>rmon Description The event command configures an entry in the RMON-MIB event table. The event command controls the generation and notification of threshold crossing events configured with the alarm command.
  • Page 323 System Management description — The description is a user configurable string that can be used to identify the purpose of this event. This is an optional parameter and can be 80 characters long. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Default An empty string.
  • Page 324 System Alarm Commands After a rising threshold crossing event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches less than or equal the falling- threshold value. Default Values -2147483648 — 2147483647 falling-threshold threshold —...
  • Page 325 System Management memory-use-alarm rising-threshold 50000000 falling-threshold 45999999 interval 500 rmon- event-type both start-alarm either memory-use-warn Syntax memory-use-warn rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type] no memory-use-warn Context config>system>thresholds Description The memory thresholds are based on monitoring MemoryUsed object. This object contains the amount of memory currently used by the system.
  • Page 326 System Alarm Commands Values log — In the case of log, an entry is made in the RMON-MIB log table for each event occurrence. This does not create a TiMOS logger entry. The RMON-MIB log table entries can be viewed using the show>system>thresholds CLI command. trap —...
  • Page 327 System Management Syntax thresholds Context config>system Description This command enables the context to configure monitoring thresholds. 7210 SAS D, E, K OS Basic System Configuration Guide Page 327...
  • Page 328 PTP Commands PTP Commands Syntax [no] ptp Context config>system Description This command enables the context to configure parameters for IEEE 1588-2008, Precision Time Protocol. This command is only available on the control assemblies that support 1588. shutdown Syntax [no] shutdown Context config>system>ptp Description...
  • Page 329 System Management Syntax [no] freq-source freq-source Context config>system>ptp>clock Description Platforms Supported: 7210 SAS-K only. This command allows user to provide a stable frequency reference obtained through one of the line references (for example: syncE, BITS) for PTP time recovery in PTP Hybrid mode. This is achieved by the specifying the frequency source for PTP to be 'ssu'.
  • Page 330: Table 34: Values And The Corresponding Pps Rate For 7210 Sas-D

    PTP for only time. The no form of the command sets it to a default value of 64pps. It is recommended that the user set a lower packet and not use the default value on 7210 SAS-D ETR. Default 64pps Parameters value —...
  • Page 331: Table 35: Values And The Corresponding Pps Rate For 7210 Sas-K

    System Management Values [-6, -5, -4, -3] - for 7210 SAS-K. Table 35: Values and the corresponding pps rate for 7210 SAS-K Value pps Rate 64pps 32pps 16pps 8pps priority1 Syntax [no] priority1 priority Context config>system>ptp This command configures the priority1 value of the local clock. This parameter is only used when the profile is set to ieee1588-2008.
  • Page 332 PTP Commands priority2 Syntax [no] priority2 priority Context config>system>ptp This command configures the priority2 value of the local clock. This parameter is only used when the profile is set to ieee1588-2008. This value is used by the Best Master Clock algorithm to determine which clock should provide timing for the network.
  • Page 333 System Management This setting only applies to the range of values observed in the clockClass values transmitted out of the node in Announce messages. The 7210 will support the reception of any valid value in Table 1/ G.8265.1 Default Parameters sdh —...
  • Page 334 PTP Commands Values 1-255 shutdown Syntax [no] shutdown Context configure>system>ptp>peer This command disables or enables a specific PTP peer. Shutting down a peer sends cancel unicast negotiation messages on any established unicast sessions. When shutdown, all received packets from the peer are ignored. If the clock-type is ordinary slave or boundary, and PTP is no shutdown, the last enabled peer cannot be shutdown.
  • Page 335: Date And Time Commands

    System Management Date and Time Commands set-time Syntax set-time [date] [time] Context admin Description This command sets the local system time. The time entered should be accurate for the time zone configured for the system. The system will convert the local time to UTC before saving to the system clock which is always set to UTC. This command does not take into account any daylight saving offset if defined.
  • Page 336: Network Time Protocol Commands

    Date and Time Commands Network Time Protocol Commands Syntax [no] ntp Context config>system>time Description This command enables the context to configure Network Time Protocol (NTP) and its operation. This protocol defines a method to accurately distribute and maintain time for network elements. Furthermore this capability allows for the synchronization of clocks between the various network elements.
  • Page 337 System Management authentication-key Syntax authentication-key key-id {key key} [hash | hash2] type {des | message-digest} no authentication-key key-id Context config>system>time>ntp Description This command sets the authentication key-id, type and key used to authenticate NTP PDUs sent to or received by other network elements participating in the NTP protocol. For authentication to work, the authentication key-id, type and key value must match.
  • Page 338 Context config>system>time>ntp Description Platforms Supported: 7210 SAS-D and 7210 SAS-E. This command configures the node to transmit NTP packets on a given interface. Broadcast and multicast messages can easily be spoofed, thus, authentication is strongly recommended. The no form of this command removes the address from the configuration.
  • Page 339 Context config>system>time>ntp Description Platforms Supported: 7210 SAS-D and 7210 SAS-E. When configuring NTP, the node can be configured to receive broadcast packets on a given subnet. Broadcast and multicast messages can easily be spoofed, thus, authentication is strongly recommended. If broadcast is not configured then received NTP broadcast traffic will be ignored. Use the show command to view the state of the configuration.
  • Page 340 Date and Time Commands Syntax peer ip-address [key-id key-id] [version version] [prefer] no peer ip-address Context config>system>time>ntp Description Configuration of an NTP peer configures symmetric active mode for the configured peer. Although any system can be configured to peer with any other NTP node it is recommended to configure authentication and to configure known time servers as their peers.
  • Page 341 System Management server Syntax server {ip address | ptp} [key-id key-id] [version version] [prefer] no server ip address Context config>system>time>ntp Description This command is used when the node should operate in client mode with the ntp server specified in the address field of this command. The no construct of this command removes the server with the specified address from the configuration.
  • Page 342: Sntp Commands

    Date and Time Commands SNTP Commands sntp Syntax [no] sntp Context config>system>time Description This command creates the context to edit the Simple Network Time Protocol (SNTP). SNTP can be configured in either broadcast or unicast client mode. SNTP is a compact, client-only version of the NTP.
  • Page 343 System Management Syntax server-address ip-address [version version-number] [normal | preferred] [interval seconds] no server-address Context config>system>time>sntp Description This command creates an SNTP server for unicast client mode. Parameters ip-address — Specifies the IP address of the SNTP server. version version-number — Specifies the SNTP version supported by this server. Values 1 —...
  • Page 344 Date and Time Commands CRON Commands cron Syntax cron Context config Description This command creates the context to create scripts, script parameters and schedules which support the Service Assurance Agent (SAA) functions. CRON features are saved to the configuration file on both primary and backup control modules. If a control module switchover occurs, CRON events are restored when the new configuration is loaded.
  • Page 345 System Management lifetime Syntax lifetime {seconds | forever} Context config>cron>action Description This command configures the maximum amount of time the script may run. Parameters seconds — Specifies the maximum amount of time to keep the results from a script run. Values 1 —...
  • Page 346 Date and Time Commands cflash-id: cf1: usb-flash-id uf1: script Syntax [no] script script-name [owner owner-name] Context config>cron>action Description This command creates action parameters for a script including the maximum amount of time to keep the results from a script run, the maximum amount of time a script may run, the maximum number of script runs to store and the location to store the results.
  • Page 347 System Management Syntax count number Context config>cron>sched Description This command configures the total number of times a CRON “interval” schedule is run. For example, if the interval is set to 600 and the count is set to 4, the schedule runs 4 times at 600 second intervals. Parameters number —...
  • Page 348 Date and Time Commands Parameters date — Specifies the date to schedule a command. Values YYYY:MM:DD in year:month:day number format day-name — Specifies the day of the week to schedule a command. Values sunday|monday|tuesday|wednesday|thursday|friday|saturday time — Specifies the time of day to schedule a command. Values hh:mm in hour:minute format hour...
  • Page 349 System Management minute is configured, but no hour or day is configured, the event will not execute. If a minute is configured without configuring month, weekday, day-of-month, and hour, the event will not execute. The no form of this command removes the specified minute from the configuration. Parameters minute-number —...
  • Page 350 Date and Time Commands event specified in these parameters takes place and the associated event occurs, the schedule enters a shutdown state. month, weekday, day-of-month, hour minute must be specified for this feature to run successfully. Default periodic weekday Syntax [no] weekday {weekday-number [..weekday-number]|day-name [..day-name]| all} Context config>cron>sched...
  • Page 351 System Management Parameters file-url — Specifies the location where the system writes the output of an event script’s execution. Values file url: local-url | remote-url: 255 chars max local-url: [<cflash-id>/ |<usb-flash-id>/][<file-path>] remote-url: [{ftp://} login:pswd@remote-locn/][file-path] remote-locn [ hostname | ipv4-address] ipv4-address a.b.c.d cflash-id: cf1:...
  • Page 352: Time Range Commands

    Date and Time Commands Time Range Commands time-range Syntax [no] time-range name [create] Context config>cron Description This command configures a time range. The no form of the command removes the name from the configuration. Default none Parameters name — Configures a name for the time range up to 32 characters in length. absolute Syntax absolute start start-absolute-time end end-absolute-time...
  • Page 353 System Management daily Syntax daily start start-time-of-day end end-time-of-day no daily start start-time-of-day Context config>cron>time-range Description This command configures the start and end of a schedule for every day of the week. To configure a daily time-range across midnight, use a combination of two entries. An entry that starts at hour zero will take over from an entry that ends at hour 24.
  • Page 354 Date and Time Commands weekend Syntax weekend start start-time-of-day end end-time-of-day no weekend start start-time-of-day Context config>cron>time-range Description This command configures a time interval for every weekend day in the time range. The resolution must be at least one minute apart, for example, start at 11:00 and end at 11:01. An 11:00 start and end time is invalid.
  • Page 355 System Management 0 — 24 0 — 59 weekly start time-in-week end time-in-week — This parameter configures the start and end of a schedule for the same day every week, for example, every Friday. The start and end dates must be the same.
  • Page 356 Date and Time Commands Time of Day Commands tod-suite Syntax [no] tod-suite tod-suite name create Context config>cron Description This command creates the tod-suite context. Default no tod-suite egress Syntax egress Context config>cron>tod-suite Description This command enables the TOD suite egress parameters. ingress Syntax ingress...
  • Page 357 System Management Parameters ip-filter ip-filter-id — Specifies an IP filter for this tod-suite. Values 1 — 65535 ipv6-filter ip-filter-id — Specifies an IPv6 filter for this tod-suite. Values 1 — 65535 time-range time-range-name — Name for the specified time-range. If the time-range is not populated the system will assume the assignment to mean “all times”.
  • Page 358 Date and Time Commands System Time Commands dst-zone Syntax [no] dst-zone [std-zone-name | non-std-zone-name] Context config>system>time Description This command configures the start and end dates and offset for summer time or daylight savings time to override system defaults or for user defined time zones. When configured, the time is adjusted by adding the configured offset when summer time starts and subtracting the configured offset when summer time ends.
  • Page 359 System Management Syntax end {end-week} {end-day} {end-month} [hours-minutes] Context config>system>time>dst-zone Description This command configures start of summer time settings. Parameters end-week — Specifies the starting week of the month when the summer time will end. Values first, second, third, fourth, last Default first end-day —...
  • Page 360 Date and Time Commands Values 0 — 60 start Syntax start {start-week} {start-day} {start-month} [hours-minutes] Context config>system>time>dst-zone Description This command configures start of summer time settings. Parameters start-week — Specifies the starting week of the month when the summer time will take effect. Values first, second, third, fourth, last Default...
  • Page 361 System Management been configured that references the zone, the summer commands must be deleted before the zone can be reset to UTC. Default zone utc - The time zone is set for Coordinated Universal Time (UTC). Parameters std-zone-name — The standard time zone name. The standard name must be a system-defined zone in Table 17.
  • Page 362 System Synchronization Commands System Synchronization Commands sync-if-timing Syntax sync-if-timing Context config>system Description This command creates or edits the context to create or modify timing reference parameters. Default Disabled (The ref-order must be specified in order for this command to be enabled.) abort Syntax abort...
  • Page 363 System Management ql-override Syntax ql-override {prs|stu|st2|tnc|st3e|st3|sec|prc|ssu-a|ssu-b} no ql-override Context config>system>sync-if-timing>ptp config>system>sync-if-timing>ref1 config>system>sync-if-timing>ref2 Description This command configures the QL value to be used for the reference for SETS input selection and BITS output. This value overrides any value received by that reference's SSM process. Default no ql-overide Parameters...
  • Page 364 4 and ref2 should be configured to use either 1/1/5 or 1/1/6. The software enforces this check. The ports 1/1/7 up to 1/1/10 can be configured as either ref1 or ref2. Default 7210 SAS-D, E, K-ref1 ref2 ptp Parameters first — Specifies the first timing reference to use in the reference order sequence.
  • Page 365 System Management ref2 Syntax ref2 Context config>system>sync-if-timing Description This command enables the context to configure parameters for the second timing reference. 7210 SAS D, E, K OS Basic System Configuration Guide Page 365...
  • Page 366 System Synchronization Commands revert Syntax [no] revert Context config>system>sync-if-timing Description This command allows the clock to revert to a higher priority reference if the current reference goes offline or becomes unstable. If revertive switching is enabled, the highest-priority valid timing reference will be used. If a reference with a higher priority becomes valid, a reference switch over to that reference will be initiated.
  • Page 367 System Management Generic Commands shutdown Syntax [no] shutdown Context config>system>time>sntp config>system>sync-if-timing>ptp Description This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. The operational state of the entity is disabled as well as the operational state of any entities contained within.
  • Page 368 Description Platforms Supported: 7210 SAS-D and 7210 SAS-E. This command validates the current golden bootstrap image, and displays its version, if found to be valid. If the golden bootstrap image is not found to be a valid, an error message is displayed to that effect.
  • Page 369 System Management Syntax debug-save file-url Context admin Description This command saves existing debug configuration. Debug configurations are not preserved in configuration saves. Default none Parameters file-url — The file URL location to save the debug configuration. Values file url: local-url | remote-url: 255 chars max local-url: [<cflash-id>/ | <usb-flash-id>][file-path], 200 chars max, including the cflash-id directory length, 99 chars max each...
  • Page 370 System Administration Commands ftp — Disconnects the FTP session. ssh — Disconnects the SSH session. display-config Syntax display-config [detail | index] Context admin Description This command displays the system’s running configuration. By default, only non-default settings are displayed. Specifying the detail option displays all default and non-default configuration parameters. Parameters detail —...
  • Page 371 System Management reboot Syntax reboot [upgrade][auto-init] [now] Context admin Description This command is used only to reboot the system or initiate an upgrade of the firmware along with a reboot of the node or initiate an auto-init boot procedure along with a reboot of the node. If no options are specified, the user is prompted to confirm the reboot operation.
  • Page 372 Syntax [no] enable-tech Context admin Description This command enables the shell and kernel commands. NOTE: This command should only be used with authorized direction from the Alcatel-Lucent Technical Assistance Center (TAC). tech-support Syntax tech-support file-url Context admin Description This command creates a system core dump.
  • Page 373 This command updates the golden bootstrap image with the file-url, after validating it as a bootstrap image for the 7210 SAS platforms.Only on 7210 SAS-D newer platforms, the admin>update- golden-bootstrap CLI command does not update the golden-bootstrap image with the boot.tim specified in the parameter value, if the boot.tim is not a newer image.
  • Page 374 — Identifies the alarm contact input pin. Values 1 — 4 (only for 7210 SAS-E) Values console-1 (only for 7210 SAS-D and 7210 SAS-K, when using console as alarm input pin) alarm-output-severity Syntax [[no] alarm-output-severity {critical | major | minor | none}, Context config>system>alarm-contact-input...
  • Page 375 System Management clear-alarm-msg Syntax [no] clear-alarm-msg {alarm-msg-text} Context config>system>alarm-contact-input alarm-contact-input-id Description This command allows the user to configure a text message for use along with SNMP trap and Log message that are sent when the system clears an alarm. The system generates a default message if the message is not configured.
  • Page 376 System Alarm Contact Commands shutdown Syntax [no] shutdown Context config>system>alarm-contact-input Description This command stops tracking the state changes associated with the alarm contact input .The system does not generate or clear the alarms for the alarm-contact input, but if an alarm is generated for the alarm-contact-input, the system clears the alarm when the shutdown command is executed.
  • Page 377 System Management LLDP System Commands lldp Syntax lldp Context config>system Description This command enables the context to configure system-wide Link Layer Discovery Protocol parameters. message-fast-tx Syntax message-fast-tx time no message-fast-tx Context config>system>lldp Description This command configures the duration of the fast transmission period. Parameters time —...
  • Page 378 LLDP System Commands notification-interval Syntax notification-interval time no notification-interval Context config>system>lldp Description This command configures the minimum time between change notifications. Parameters time — Specifies the minimum time, in seconds, between change notifications. Values 5 — 3600 Default reinit-delay Syntax reinit-delay time no reinit-delay Context...
  • Page 379 System Management tx-hold-multiplier Syntax tx-hold-multiplier multiplier no tx-hold-multiplier Context config>system>lldp Description This command configures the multiplier of the tx-interval. Parameters multiplier — Specifies the multiplier of the tx-interval. Values 2 — 10 Default tx-interval Syntax tx-interval interval no tx-interval Context config>system>lldp Description This command configures the LLDP transmit interval time.
  • Page 380 LLDP Ethernet Port Commands LLDP Ethernet Port Commands lldp Syntax lldp Context config>port>ethernet Description This command enables the context to configure Link Layer Discovery Protocol (LLDP) parameters on the specified port. dest-mac Syntax dest-mac {bridge-mac} Context config>port>ethernet>lldp Description This command configures destination MAC address parameters. Parameters bridge-mac —...
  • Page 381 System Management notification Syntax [no] notification Context config>port>ethernet>lldp>dstmac Description This command enables LLDP notifications. The no form of the command disables LLDP notifications. tx-mgmt-address Syntax tx-mgmt-address [system] no tx-mgmt-address Context config>port>ethernet>lldp>dstmac Description This command specifies which management address to transmit. The no form of the command resets value to the default.
  • Page 382 System Resource-Profile Commands System Resource-Profile Commands resource-profile Syntax resource-profile no resource-profile Context configure>system Description This command enables the context to configure resource-profile parameters on the system. Default no default egress-internal-tcam Syntax egress-internal-tcam Context configure>system>resource-profile Description This command provides the context to allocate resources from the egress internal TCAM pool. acl-sap-egress Syntax [no] acl-sap-egress...
  • Page 383 — Specifies the amount of resources that can be allocated for use by ACL policies. Values Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-D (per node) 7210 SAS-E (per node) 7210 SAS-K (per node) 7210 SAS D, E, K OS Basic System Configuration Guide Page 383...
  • Page 384 Context configure>system>resource-profile>egress-internal-tcam Description Platforms Supported: 7210 SAS-D This command allows the user to allocate maximum resources for use by SAP egress aggregate policer from the egress-internal-tcam resource pool. This command limits the total amount of chunks allocated for use by SAP egress aggregate meter to the value specified by num-resources.
  • Page 385 System Management ipv6-128bit-match-enable Syntax [no] ipv6-128bit-match-enable num-resources Context configure>system>resource-profile>egress-internal-tcam>acl-sap-egress Description This command allows the user to allocate maximum resources for use by egress filter policies using ipv6 criteria with 128-bit IPv6 addresses. The resources cannot be shared with any other egress filter policies that specify other match crtieria. Please see the 7210 SAS Router Configuration guide for more information on resource allocation details and fields available for use.
  • Page 386 System Resource-Profile Commands mac-ipv4-ipv6-128-match-enable Syntax [no] mac-ipv4-ipv6-128-match-enable num-resources Context configure>system>resource-profile>egress-internal-tcam>acl-sap-egress Description Platforms Supported: 7210 SAS-K. On 7210 SAS-K, when resources are allocated to Egress ACLs from the egress internal tcam pool using the command configure>system>resource-profile>egress-internal-tcam>acl-sap-egress, these resources can be used by either MAC criteria entries or IPv4 entries. In order to enable IPv6 128-bit address match, user need to allocate resources using this command (that is, configure>system>resource-profile>egress-internal-tcam>acl-sap-egress>mac-ipv4-ipv6-128- match-enable.
  • Page 387 System Management Parameters num-resources — Specifies the maximum amount of resources for use by this filter match criteria. Values [0...5] mac-ipv4-ipv6-128-match-enable Syntax [no] mac-ipv4-ipv6-128-match-enable num-resources Context configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource> Description Platforms Supported: 7210 SAS-K This command allows the user to allocate maximum resources for use by SAP ingress QoS classification policies using IPv6 criteria with 128-bit IPv6 (source and destination IPv6) addresses.
  • Page 388 System Resource-Profile Commands The resources cannot be shared with any other egress filter policies that specify other match criteria. Please see the 7210 SAS Router Configuration guide for more information on resource allocation details and fields available for use. With the no form of the command, the software does not allocate any resources for use by egress filter policies using MAC or IPv4 criteria.
  • Page 389 System Management provides for use of all available resources exclusively by MAC criteria egress filter policies and provide larger number of policies to be used. The resources cannot be shared with any other egress filter policies that specify other match criteria. Please see the 7210 SAS Router Configuration guide for more information on resource allocation details and fields available for use.
  • Page 390 System Resource-Profile Commands Values Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-D (per node) 7210 SAS-E (per node) 7210 SAS-K (per node) ipv4-ipv6-128-match-enable Syntax [no] ipv4-ipv6-128-match-enable Context configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress Description This command allows the user to allocate maximum resources for use by ingress filter policies using ipv6 criteria with 128-bit IPv6 addresses.
  • Page 391 Values Platforms Min value Max value Default (per node) (per node) Values 7210 SAS-D (per node) 7210 SAS-E (per node) ipv4-match-enable 7210 SAS D, E, K OS Basic System Configuration Guide Page 391...
  • Page 392 Values Platforms Min value Max value Default (per node) (per node) Values 7210 SAS-D (per node) 7210 SAS-E (per node) ipv6-64-only-match-enable Syntax [no] ipv6-64-only-match-enable Context configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress Description This command allows the user to allocate maximum resources for use by ingress filter policies using ipv6 criteria with 64-bit IPv6 addresses.
  • Page 393 7210 SAS-D/E Router Configuration user guide. For more details about the resource allocation for SAP ingress QoS policy please refer to 7210 SAS-DE QoS user guide.
  • Page 394 NOTE: In 7210 SAS-D, mac-criteria SAP ingress QoS policies get to use an additional 128 classification entries with 64 meters. These entries are allocated to mac-criteria SAP ingress QoS resource pool by default and cannot be reassigned to any another feature or any other match criteria.
  • Page 395 System Management Default no dhcp-snooping-enable No resources are allocated to the DHCP snooping feature and it cannot be used. eth-cfm Syntax [no] eth-cfm Context configure>system>resource-profile>ingress-internal-tcam Description This command provides the context to allocate resources for CFM UP MEPs. With the no form of the command, the software does not allocate any resources for use by CFM UP MEPs.
  • Page 396 System Resource-Profile Commands Syntax [no] up-mep Context configure>system>resource-profile>ingress-internal-tcam>eth-cfm Description This command provides the context to allocate resources for CFM UP MEPs. Resources for UP MEPs created on SAP and SDP Bindings are allocated from this pool. With the no form of the command, the software does not allocate any resources for use by CFM UP MEPs.
  • Page 397 System Management Values Platforms Min value Max value Default (per node) (per node) Values 7210 SAS-D (per node) 7210 SAS-E (per node) qos-sap-ingress-resource Syntax qos-sap-ingress-resource no qos-sap-ingress-resource Context configure>system>resource-profile>ing-internal-tcam Description This command allows the user to allocate maximum resources for use by SAP ingress QoS policies using any of the supported match criteria.
  • Page 398 System Resource-Profile Commands The following are the min, max and default values: Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-D (per node) 7210 SAS-E (per node) 7210 SAS-K (per node) sap-aggregate-meter Syntax [no] sap-aggregate-meter num-resource Context configure>system>resource-profile>ingress-internal-tcam>...
  • Page 399 — Specifies the maximum amount of resources for use by this filter match criteria. Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-D (per node) 7210 SAS D, E, K OS Basic System Configuration Guide Page 399...
  • Page 400 Description NOTE: This command is supported only on 7210 SAS-D. This command allows the user to allocate IPv6 route entries in the L3 forwarding table. L3 forwarding table entries is shared among IPv4 and IPv6 route entries. Before adding routes for IPv6 destinations, route entries in the routed lookup table needs to be allocated for IPv6 addresses using this command.
  • Page 401 Description 7210 SAS-D chassis with 128MB flash has a fan to help in circulating the air inside the chassis. It does not provide for cooling. This command allows the operator to control the operation of the fan. Operators can choose to either switch 'on' or 'off' the fan permanently or let the system control the operation of the fan by setting the value to 'auto'.
  • Page 402 Fan Controller Commands Page 402 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 403 System Management Show Commands YSTEM OMMANDS connections Syntax connections [address ip-address [interface interface-name]] [port port-number] [detail] Context show>system Description This command displays UDP and TCP connection information. If no command line options are specified, a summary of the TCP and UDP connections displays. Parameters ip-address —...
  • Page 404 System Commands Label Description (Continued) Sample Output A:ALA-12# show system connections =============================================================================== Connections : =============================================================================== Proto RecvQ TxmtQ Local Address Remote Address State ------------------------------------------------------------------------------- 0 0.0.0.0.21 0.0.0.0.0 LISTEN 0 0.0.0.0.23 0.0.0.0.0 LISTEN 0 0.0.0.0.179 0.0.0.0.0 LISTEN 0 10.0.0.xxx.51138 10.0.0.104.179 SYN_SENT 0 10.0.0.xxx.51139 10.0.0.91.179 SYN_SENT...
  • Page 405: Table 36: Show System Cpu Output Fields

    System Management window probe window update packet packets received after close discarded for bad checksum discarded for bad header offset field discarded because packet too short connection request connection accept : 24 connections established (including accepts) : 27 connections closed : 26 (including 2 drops) embryonic connections dropped segments updated rtt...
  • Page 406 System Commands Table 36: Show System CPU Output Fields (Continued) Label Description The sum of CPU usage of all the processes and protocols. CPU Usage Capacity Usage Displays the level the specified service is being utilized. When this number hits 100%, this part of the system is busied out. There may be extra CPU cycles still left for other processes, but this service is run- ning at capacity.
  • Page 407 System Management Syntax cron Context show>cron Description This command enters the show CRON context. action Syntax action [action-name] [owner action-owner] run-history run-state Context show>cron# Description This command displays cron action parameters. Parameters action action-name — Specifies the action name. Values maximum 32 characters owner action-owner —...
  • Page 408 System Commands Label Description (Continued) Completed run Displays the number of completed sessions. histories Executing run Displays the number of sessions in the process of executing. histories Initializing run Displays the number of sessions ready to run/queued but not exe- histories cuted.
  • Page 409 System Management Script Run #20 ------------------------------------------------------------------------------- Start time : 2006/11/06 20:46:00 End time : never Elapsed time : 0d 00:00:56 Lifetime : 0d 00:59:04 State : executing Run exit code : noError Result time : never Keep history : 0d 01:00:00 Error time : never Results file...
  • Page 410 System Commands Parameters schedule-name — Displays information for the specified scheduler name. owner schedule-owner — Displays information for the specified scheduler owner. Output The following table describes the show cron schedule output fields. A:sim1>show>cron schedule test Label Description Schedule name Displays the schedule name.
  • Page 411 System Management Label Description (Continued) Hour Displays the configured hour. Minute Displays the configured minute. Number of sched- Displays the number of scheduled sessions. uled runs Last scheduled run Displays the last scheduled session. Number of sched- Displays the number of scheduled sessions that failed to execute. uled failures Last scheduled Displays the last scheduled session that failed to execute.
  • Page 412 System Commands Context show>cron# Description This command displays cron script parameters. Parameters schedule-name — Displays information for the specified script. owner schedule-owner — Displays information for the specified script owner. Output The following table describes the show cron script output fields. Label Description Script...
  • Page 413 System Management Syntax information Context show>system Description This command displays general system information including basic system, SNMP server, last boot and DNS client information. Output System Information Output — The following table describes the system information output fields. Label Description System Name The configured system name.
  • Page 414 System Commands Label Description (Continued) Config Source Primary — Indicates that the directory location for configuration file was loaded from the primary source. Secondary — Indicates that the directory location for configuration file was loaded from the secondary source. Tertiary — Indicates that the directory location for configuration file was loaded from the tertiary source.
  • Page 415: Table 37: Show Memory Pool Output Fields

    System Management Label Description (Continued) DNS Server The IP address of the DNS server. DNS Domain The DNS domain name of the node. BOF Static Routes To — The static route destination. Next Hop — The next hop IP address used to reach the destination. Metric —...
  • Page 416 System Commands ------------------------------------------------------------------------------- System No limit 24,117,248 24,117,248 16,974,832 8,388,608 1,048,576 1,048,576 85,200 RTM/Policies No limit 5,242,912 5,242,912 3,944,104 OSPF No limit 3,145,728 3,145,728 2,617,384 MPLS/RSVP No limit 9,769,480 9,769,480 8,173,760 No limit IS-IS No limit No limit VRRP No limit 1,048,576 1,048,576 Services...
  • Page 417 System Management Label Description (Continued) System Ref. ID IP address of this node or a 4-character ASCII code showing the state. Auth Error Displays the number of authentication errors. Auth Errors Displays the number of authentication errors ignored. Ignored Auth key ID Errors Displays the number of key identification errors .
  • Page 418 System Commands Label Description (Continued) Peer Codes: ACST — The association belongs to any cast server. AUTH — Server authentication failed. Please wait while the associa- tion is restarted. AUTO — Autokey sequence failed. Please wait while the association is restarted. BCST —...
  • Page 419 System Management Sample Output A:7210>config>system>time>ntp# show system ntp =============================================================================== NTP Status =============================================================================== Enabled : Yes Stratum : 3 Admin Status : up Oper Status : up Server enabled : No Server keyId : none System Ref Id : 192.168.15.221 Auth Check : Yes =============================================================================== A:7210 A:7210# show system ntp all...
  • Page 420 System Commands A:7210>config>system>time>ntp# A:7210>config>system>time>ntp# show system ntp detail all =============================================================================== NTP Status =============================================================================== Enabled : Yes Stratum : 3 Admin Status : up Oper Status : up Server enabled : No Server keyId : none System Ref Id : 192.168.15.221 Auth Check : Yes Auth Errors : 0 Auth Errors Ignored : 0 Auth Key Id Errors : 0 Auth Key Type Errors : 0 ===============================================================================...
  • Page 421 System Management Label Description (Continued) Hold Dn Time The configured HOLD down time. Members Displays the number of members of the oper-group. Monitor Displays the number of monitoring clients. Show Output *A:7210SAS>show>system# oper-group =============================================================================== System Oper Group Information =============================================================================== Name Oper Creation Hold Hold...
  • Page 422: Table 38: Show System Resource-Profile Output Fields

    System Commands Output Show resource-profile Output — The following table describes resource-profile output fields. Table 38: Show system resource-profile output fields. Label Description Displays the applications sharing ingress CAM resource. Ingress Internal Displays the resources configured for use by SAP Ingress ACL Sap Ingress ACL resource policies.
  • Page 423 Displays the resource allocation configured for the egress inter- Egress Internal nal CAM. Displays the amount of IPv6 FIB size configured for use by IPv6 IPv6 FIB routing. Sample Output for 7210 SAS-D *A:7210SAS>show>system# resource-profile =============================================================================== Active System Resource Profile Information =============================================================================== -------------------------------------------------------------------------------...
  • Page 424 System Commands ------------------------------------------------------------------------------- Sap Egress ACL resource ------------------------------------------------------------------------------- Mac and IPv4 Resource Mac-only Resource : disable IPv6 128 bit Resource : disable Mac and IPv6 64 bit Resour*: disable ------------------------------------------------------------------------------- =============================================================================== * indicates that the corresponding row element may have been truncated. *A:7210SAS>show>system# Sample Output for 7210 SAS-E A:7210SAS>show>system# resource-profile...
  • Page 425 System Management ------------------------------------------------------------------------------- Mac-IPv4-IPv6 Resource : disable ------------------------------------------------------------------------------- Sap Ingress ACL resource ------------------------------------------------------------------------------- Mac-IPv4-IPv6 Resource : disable ------------------------------------------------------------------------------- Egress Internal CAM ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Sap Egress ACL resource : disable ------------------------------------------------------------------------------- Mac-IPv4-IPv6 Resource : disable =============================================================================== # indicates that the value will take effect only after reboot or clear card. *A:7210SAS>show>system# Syntax ptp [ peer <ip-address>...
  • Page 426: Table 39: Show System Sntp Output Fields

    System Commands =============================================================================== ------------------------------------------------------------------------------- Time Information ------------------------------------------------------------------------------- Timescale : PTP Current Time : 2012/12/13 11:05:43 (UTC) Frequency Traceable : yes Time Traceable : yes Time Source : GPS =============================================================================== =============================================================================== A:7210SAS>show>system# sntp Syntax sntp Context show>system Description This command displays SNTP protocol configuration and state. Output Show SNTP Output —...
  • Page 427 System Management SNTP Server Version Preference Interval ------------------------------------------------------------------------------- 10.135.16.90 Preferred ------------------------------------------------------------------------------- No. of SNTP Servers: 1 =============================================================================== *A:pc-4.0# thresholds Syntax thresholds Context show>system Description This command display system monitoring thresholds. Output Thresholds Output — following table describes system threshold output fields. Label Description Variable...
  • Page 428 System Commands Label Description (Continued) Action Type log — An entry is made in the RMON-MIB log table for each event occurrence. This does not create a TiMOS logger entry. The RMON- MIB log table entries can be viewed using the show>system>thresh- olds CLI command.
  • Page 429 System Management Event Id Last Sent : 10/31/2006 08:47:59 Action Type : both Owner : TiMOS CLI Description: TiMOS CLI - memory usage alarm rising event Event Id Last Sent : 10/31/2006 08:48:00 Action Type : both Owner : TiMOS CLI Description: TiMOS CLI - memory usage alarm falling event Event Id Last Sent...
  • Page 430: Table 40: Show System Time Output Fields

    System Commands time Syntax time Context show>system Description This command displays the system time and zone configuration parameters. Output System Time Output — The following table describes system time output fields. Table 40: Show System Time Output Fields Label Description The system date and time using the current time zone.
  • Page 431: Table 41: Show Vwm-Shelf Output Fields

    System Management ------------------------------------------------------------------------------- DST Zone : PDT Offset from Non-DST : 0:60 Starts : first sunday in april 02:00 Ends : last sunday in october 02:00 ============================================================================ A:ALA-1# A:ALA-1# show system time (with no DST zone configured) =============================================================================== Date & Time =============================================================================== Current Date &...
  • Page 432 System Commands Table 41: Show VWM-shelf Output Fields (Continued) Label Description User provisioned card-type to identify the module inserted into the Provisioned Type 1830 device. The card-type currently inserted into the slot on the 1830 device. Equipped Type The number of slots available on the 1830 device. No of Slots The 1830 VWM CWDM device part number.
  • Page 433 System Management Not Provisioned SFC2A&B DOWN DOWN CWDM CWDM =========================================================================== *A:7210SAS>show>system# show system vwm-shelf 7 detail =========================================================================== Shelf Summary =========================================================================== Shelf-ID USB/ Shelf Admin Oper Number of Type State State Equipped slots --------------------------------------------------------------------------- CWDM =========================================================================== Slot Summary =========================================================================== Slot-ID Provisioned Equipped Admin Oper...
  • Page 434 System Commands Equipped type : Equipped (SFC2A&B) Part Number : 3KC19289AKAA CLEI code : WOCUAZNUTA Unit Mnemonic : SFC2A&B Serial Number : EZ120630634 Manufacturing Date : 12122000 Operational state : UP Firmware version : -------------- Current Alarm state : Cleared =========================================================================== Sample output for 7210 SAS-E, devices for DWDM: *A:Dut-C# show system vwm-shelf 4...
  • Page 435 System Management DWDM DWDM UP/Active DWDM DWDM UP/Stanby =========================================================================== 1830 VWM Shelf Controller-A Hardware Data =========================================================================== No of Slots Part Number : 3KC19319AAAA01 CLEI code : WOCUA1LUTA Unit Mnemonic : EC-DW Serial Number : EZ1242A9967 Manufacturing Date : 13022000 Administrative state : UP Operational state : UP/Active...
  • Page 436 System Commands Current Alarm state : Cleared =========================================================================== 1830 VWM Fan Hardware Data =========================================================================== Slot Number Part Number CLEI code Unit Mnemonic Serial Number Manufacturing Date Operational state : DOWN Firmware version =========================================================================== *A:Dut-C# time Syntax time Context show Description This command displays the current day, date, time and time zone.
  • Page 437: Table 42: Show System Tod-Suite Output Fields

    System Management tod-suite Syntax tod-suite [detail] tod-suite associations tod-suite failed-associations Context show>cron Description This command displays information on the configured time-of-day suite. Output CRON TOD Suite Output — The following table describes TOD suite output fields: Table 42: Show System tod-suite Output Fields Label Description Shows which SAPs this tod-suite is associated with.
  • Page 438 System Commands ------------------------------------------------------------------------------- Service Id Type : VPLS SAP 1/1/1:1 SAP 1/1/1:2 SAP 1/1/1:3 SAP 1/1/1:4 SAP 1/1/1:5 SAP 1/1/1:6 SAP 1/1/1:20 ------------------------------------------------------------------------------- Number of SAP's : 7 Customer Multi-Service Site associations ------------------------------------------------------------------------------- Multi Service Site: mss_1_1 ------------------------------------------------------------------------------- Number of MSS's: 1 =============================================================================== A:kerckhot_4# The following example shows output for TOD suite failed-associations.
  • Page 439 System Management Learned MAC Addr Static MAC Addr Admin MTU : 1518 Oper MTU : 1518 Ingress qos-policy : 1130 Egress qos-policy : 1130 Intend Ing qos-pol*: 1190 Intend Egr qos-po*: 1190 Shared Q plcy : n/a Multipoint shared : Disabled Ingr IP Fltr-Id : n/a Egr IP Fltr-Id...
  • Page 440: Table 43: Show System Time-Range Output Fields

    System Commands IP-Option : 0/0 Multiple Option: Off TCP-syn : Off TCP-ack : Off Match action : Forward Next Hop : 172.22.184.101 Ing. Matches : 0 Egr. Matches =============================================================================== A:kerckhot_4# If a filter is referred to in a TOD Suite assignment, use the show filter associations command to view the output: A:kerckhot_4# show filter ip 160 associations ===============================================================================...
  • Page 441: Table 44: System Timing Output Fields

    System Management Absolute : Start * * * * End * * * * The following example shows output for time-range associations with previously created IP and MAC filters. A:ala# show cron time-range day associations =============================================================================== Cron time-range associations =============================================================================== Name : day State...
  • Page 442 Displays information about reference input 2. Not Selected Due to Indicates the reason if reference input 2 is not selected. Note: SSM is supported only on 7210 SAS-D devices. Quality Level Selec- Indicates whether the ql-selection command has been enabled or dis- tion abled.
  • Page 443 : No Not Selected Due To on standby Source Port : 1/1/6 =============================================================================== *A:7210-SAS># Sample output for 7210 SAS-D: *7210-SASD># show system sync-if-timing =============================================================================== System Interface Timing Operational Info =============================================================================== System Status CPM A : Master Locked Reference Input Mode...
  • Page 444 System Commands Admin Status : up Rx Quality Level : prc Quality Level Override : none Qualified For Use : Yes Selected For Use : No Not Selected Due To on standby Source Port : 1/1/5 =============================================================================== Sample output for 7210 SAS-K: *A:SAH01-051>show>system# sync-if-timing =============================================================================== System Interface Timing Operational Info...
  • Page 445 Description This command displays general chassis status information. NOTE: The 'environment' option is supported only on 7210 SAS-E and 7210 SAS-D. The ‘power- supply’ option is supported only on 7210 SAS-D ETR. Parameters environment — Displays chassis environmental status information.
  • Page 446 System Commands Label Description (Continued) Manufacture date The chassis manufacture date. Not user modifiable. Manufacturing Factory-inputted manufacturing text string. Not user modifiable. string Time of last The date and time the most recent boot occurred. boot Current alarm Displays the alarm conditions for the specific board. state Number of fan The total number of fan trays installed in this chassis.
  • Page 447 System Management =============================================================================== Name : STU2597 Type : 7210 SAS-E-1 Location Coordinates CLLI code Number of slots Number of ports : 24 Critical LED state : Red Major LED state : Off Minor LED state : Off Over Temperature state : OK Base MAC address : 00:25:ba:04:b9:bc...
  • Page 448 System Commands Chassis Information =============================================================================== Name : 128sasdAc48v2573 Type : 7210 SAS-D 6F4T ETR-1 Location Coordinates CLLI code Number of slots Number of ports : 10 Critical LED state : Off Major LED state : Off Minor LED state : Off...
  • Page 449 System Management *A:SAH01-051>show# chassis =============================================================================== Chassis Information =============================================================================== Name : SAH01-051 Type : 7210 SAS-K-1 Location Coordinates CLLI code Number of slots Number of ports System LED state : Amber Over Temperature state : OK Base MAC address : 00:03:fa:27:15:4e Number of MAC addresses : 12 Hardware Data...
  • Page 450 System Commands *A:SASE>show# Output for older 7210 SAS-E devices without input-fail-detection) *A:7210-SAS-E# show chassis power-supply =============================================================================== Chassis Information =============================================================================== Power Supply Information Number of power supplies Power supply number Defaulted power supply type : none Status : not equipped Power supply number Configured power supply type : dc (+24V) Status...
  • Page 451 System Management alarm-contact-input Syntax alarm- contact-input all Context show>alarm-contact-input Description This command displays information of all the alarm contact input pins. Output alarm-contact-input Output — The following table describes alarm-contact-input output fields. Label Description Alarm input pin Number Indicates the pin alarm input pin number. Alarm input pin Descrip- Describes the alarm indicating its usage or attribute.
  • Page 452 System Commands *A:7210SAS>show# alarm-contact-input console-1 =============================================================================== Alarm Contact Input =============================================================================== Alarm Input Pin Number : console-1 Alarm Input Pin Current State : alarm Alarm Output Pin Used : Major *A:7210SAS>show# *A:7210-2# show alarm-contact-input all =============================================================================== Alarm Contact Input =============================================================================== Alarm Input Pin Number Alarm Input Pin Description Alarm Input Pin Current State : Disabled Alarm Output Pin Used...
  • Page 453 System Management Debug Commands sync-if-timing Syntax sync-if-timing Context debug Description The context to debug synchronous interface timing references. force-reference Syntax force-reference {ref1 | ref2 | ptp} no force-reference Context debug>sync-if-timing Description This command allows an operator to force the system synchronous timing output to use a specific ref- erence.
  • Page 454 System Commands Syntax [no] router router-name interface ip-int-name Context debug>system Description This command enables and configures debugging for NTP. The no form of the command disables debugging for NTP. Parameters router-name — Base Default Base ip-int-name — maximum 32 characters; must begin with a letter. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
  • Page 455 System Management Clear Commands completed Syntax completed [action-name] [owner action-owner] Context clear>cron>action Description This command clears completed CRON action run history entries. Parameters action-name — Specifies the action name. Values maximum 32 characters owner action-owner — Specifies the owner name. Default TiMOS CLI screen...
  • Page 456 System Commands Context clear>system Description This command allows an operator to individually clear (re-enable) a previously failed reference. As long as the reference is one of the valid options, this command is always executed. An inherent behavior enables the revertive mode which causes a re-evaluation of all available references. Parameters ref1 —...
  • Page 457 System Management ONTROLLER DEBUG COMMANDS fan-stats Syntax fan-stats Context tools>dump Description This command provides details of the fan operation. Sample Output The following table describes fan-stats output fields. Label Description Fan Configuration Mode Displays the user configured mode for fan operation. It can be On/Off/Auto.
  • Page 458 Fan Controller debug commands Page 458 7210 SAS D, E, K OS Basic System Configuration Guide...
  • Page 459: Standards And Protocol Support

    Standards and Protocol Support Standards Compliance Efficient Handling of in-Profile RFC 1907 SNMPv2-MIB Traffic [Only for 7210 SAS-D] RFC 2011 IP-MIB IEEE 802.1ab-REV/D3 Station and RFC 2012 TCP-MIB Media Access Control Connectivity IPv6 (only 7210 SAS-D,E) RFC 2013 UDP-MIB Discovery...
  • Page 460 SAS-D,E) RFC 2328 TFTP Blocksize Option TIMETRA-LOG-MIB.mib RFC 2349 TFTP Timeout Interval and TIMETRA-MIRROR-MIB.mib Transfer Size option TIMETRA-NTP-MIB.mib TIMETRA-OAM-TEST-MIB.mib Timing (Only on 7210 SAS-D ETR and TIMETRA-PORT-MIB.mib SAS-K) TIMETRA-QOS-MIB.mib ITU-T G.781 Telecommunication TIMETRA-SAS-ALARM-INPUT- Standardization Section of ITU, MIB.mib Synchronization layer functions, TIMETRA-SAS-FILTER-MIB.mib...
  • Page 461: Index

    NDEX configuring command reference auto mode copying files creating directories displaying information moving files removing/deleting overview image loading persistence saving a configuration image loading configuring accessing the CLI console connection lldp basic BOF parameters command reference manual mode management tasks overview rebooting searching for BOF file...
  • Page 462 Index Page 462 7210 SAS D, E, K OS Basic System Configuration Guide...

This manual is also suitable for:

7210 sas-e7210 sas-k

Table of Contents