Download Print this page

Alcatel-Lucent 7210 SAS M Configuration Manual

Alcatel-Lucent 7210 SAS M Configuration Manual

Service access switch

Hide thumbs Also See for Alcatel-Lucent 7210 SAS M:

Service manual (952 pages)

,

Configuration manual (516 pages)

,

Quality of service manual (404 pages)

Table Of Contents

page of 558

/ 558
Contents
Table of Contents
Bookmarks

Table of Contents

Advertisement

Quick Links

See also: Service Manual , User Manual

Alcatel-Lucent

Service Access Switch| Release 7.0 Rev.07

7 2 1 0 S A S M , T , X , R 6 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 09 52 1A AAFT QZ Z A

3HE09521AAAFTQZZA

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

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the Alcatel-Lucent 7210 SAS M and is the answer not in the manual?

Questions and answers

Summary of Contents for Alcatel-Lucent Alcatel-Lucent 7210 SAS M

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
Getting Started Alcatel-Lucent 7210 SAS-Series System Configuration Process ....... .17 CLI Usage CLI Structure.
Page 4 Table of Contents Moving Files ..............100 Removing Files and Deleting Directories .
Page 5 Table of Contents System Time ..............202 Time Zones .
Page 6 Table of Contents Configuration Guidelines for System Resource Profile ....... . .258 System Configuration Process Overview .
Page 7 IST OF ABLES Getting Started Table 1: Configuration Process ............17 CLI Usage Table 2: Console Control Commands .
Page 8 List of Tables Table 38: Show System Time Output Fields..........507 Table 39: Show VWM-shelf Output Fields .
Page 9 IST OF IGURES CLI Usage Figure 1: Rollback Operation............45 Figure 2: Configuration Rollback .
Page 10 List of Figures Page 10 7210 SAS M, T, X, R6 Basic System Configu-...
Page 11: Preface
Preface About This Guide This guide describes system concepts and provides configuration explanations and examples to configure 7210 SAS-M, T, X and R6 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 Preface This document is organized into functional chapters and provides concepts and descriptions of the implementation flow, as well as Command Line Interface (CLI) syntax and command usage. Page 12 7210 SAS M, T, X, R6 Basic System Configura- tion Guide...
Page 13 Preface Audience This manual is intended for network administrators who are responsible for configuring the 7210 SAS-Series routers. It is assumed that the network administrators have an understanding of networking principles and configurations. Protocols, standards, and processes described in this manual include the following: •...
Page 14: List Of Technical Publications
Preface List of Technical Publications The 7210 SAS-M, T, X, R6 OS documentation set is composed of the following books: • 7210 SAS-M, T, X, R6 OS Basic System Configuration Guide This guide describes basic system configurations and operations. • 7210 SAS-M, T, X, R6 OS System Management Guide This guide describes system security and access configurations as well as event logging and accounting logs.
Page 15: 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 re-seller for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center: Web: http://www.alcatel-lucent.com/wps/portal/support...
Page 16 Preface Page 16 7210 SAS M, T, X, R6 Basic System Configura- tion Guide...
Page 17: 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 18: Getting Started
Getting Started Table 1: Configuration Process Area Task Chapter (Continued) Boot options Configure boot option files Boot Options on page 119 (BOF) System configuration Configure system functions, System Management on page 197 including host name, address, domain name, and time parameters.
Page 19: 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 20 • Navigating in the CLI on page 21 • Basic CLI Commands on page 23 •...
Page 20: 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 21: Navigating In The Cli
Entering Numerical Ranges on page 38 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 22 Navigating in the CLI 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# Page 22 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 23: Basic Cli Commands
CLI Usage 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 24 Navigating in the CLI 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 25: Table 3: Command Syntax Symbols
CLI Usage 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 26: Cli Environment Commands
Navigating in the CLI 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 27: Cli Monitor Commands
CLI Usage 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 28: Getting Help In The Cli
Getting Help in the CLI 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 29 CLI Usage 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> | | +---shutdown | | +---access | +---shutdown...
Page 30: The Cli Command Prompt
The CLI Command Prompt 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 31: Displaying Configuration Contexts
CLI Usage 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 32: Exec Files
EXEC Files 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 33: Entering Cli Commands
CLI Usage 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 34: Editing Keystrokes
Entering CLI Commands 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 35: Absolute Paths
CLI Usage 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 36 Entering CLI Commands 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> Page 36 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 37: 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-M 7210 Copyright (c) 2000-2008 Alcatel-Lu cent.
Page 38: Entering Numerical Ranges
Entering CLI Commands Entering Numerical Ranges The 7210-SAS M 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 39 CLI Usage 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 40: Pipe/Match
Entering CLI Commands Pipe/Match The 7210-SAS M OS 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 41: Table 9: Regular Expression Symbols
CLI Usage 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 42: Table 10: Special Characters
Entering CLI Commands 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 43: Redirection
CLI Usage 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 44: Configuration Rollback
Configuration Rollback Configuration Rollback Note: This feature is supported only on 7210 SAS-R6 devices. The Configuration Rollback feature provides the ability to “undo” configuration and reverts back to previous router configuration states while minimizing impacts to services. This feature gives the operator better control and visibility over the router configurations and reduces operational risk while increasing flexibility and providing powerful recovery options.
Page 45: Feature Behavior
CLI Usage Figure 1: Rollback Operation SNMP commands (SAM) (config) Active Config rollback revert rollback save Commit / Commit / Rollback Rollback File Rollback File Checkpoint Files Feature Behavior The following list describes detailed behavior and CLI usage of the rollback feature: •...
Page 46 Configuration Rollback • When a rollback save [no “-”] is executed, the system shifts the file suffix of all the previous checkpoints by 1 (new id = old id + 1). If there are already as many checkpoint files as the maximum number supported then the last checkpoint file is deleted. •...
Page 47 CLI Usage • As shown in Figure 2, support for rolling back to a previous configuration (a saved rollback checkpoint) with minimal impact on services. The previous configuration will be loaded and take operational effect: admin>rollback# revert [latest-rb|<checkpoint-id>] 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 47...
Page 48: Figure 2: Configuration Rollback
Configuration Rollback Figure 2: Configuration Rollback SNMP set SNMP set CLI config CLI config rollback save rollback save rollback rollback checkpoint checkpoint rollback save rollback save rollback rollback checkpoint checkpoint rollback revert 2 rollback revert 2 rollback save rollback save rollback rollback checkpoint...
Page 49 CLI Usage • Impacts to the running services are minimized during a rollback: − No impact in areas of configuration that did not change − Configuration parameters that changed (or items that changed config have dependencies on) are first removed (revert to default) and the previous values are then restored (can be briefly service impacting in changed areas).
Page 50 Configuration Rollback • The following list captures some side effects and specific behaviors of a Rollback revert. Some of these side effects are not related purely to configuration (that is, in the CLI config branch) and may have interactions with tools commands, RADIUS, etc. −...
Page 51 CLI Usage dependant on admin state), then the rollback revert will automatically remove the force-switchover and the node will revert to whatever is the best spoke-sdp in the redundant set. − Rollback impacts the configuration state of the router, and as with normal operator CLI or SNMP configuration changes, additional actions or steps may need to occur before certain configuration changes take operational effect.
Page 52: Rescue Configuration
Configuration Rollback • Although the use of the Control-C key combination is not recommended during a rollback revert, it is supported (through CLI or SNMP). Interrupting a rollback revert may leave the router in a state that is not necessarily something between the old active config and the rollback checkpoint since the rollback processing may have been in the middle of tearing things down or rebuilding configurations.
Page 53 CLI Usage • “rollback-save” to create a rollback checkpoint. − used for intermediate checkpoints that can be recovered with minimal impacts to services. − should be done each time that a moderate amount configuration changes have been made. − should be done after any hardware changes. −...
Page 54: Limitations Of Cli Rollback
Configuration Rollback occurs during a rollback (or within a few seconds of a rollback completing), the operator is advised to repeat the rollback revert operation to the same checkpoint. • A rollback checkpoint stores the rollback-location and the local/remote-max-checkpoint values, and as such a rollback revert operation can change those values. If an operator changes the local/remote-max-checkpoint values it is recommended to delete all the existing checkpoints (otherwise a subsequent rollback revert could change the max back to a previous value).
Page 55: Basic Command Reference
Basic Command Reference Basic Command Reference Command Hierarchies • Monitor Commands • Environment Commands Basic CLI Commands — back — clear — echo [text-to-echo] [extra-text-to-echo] [more-text] — enable-admin — exec [-echo] [-syntax] filename | eof-marker-string — exit [all] — help —...
Page 56: Monitor Commands
Monitor Commands monitor — filter — ip-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 57: 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 58 Page 58 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 59 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 60 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 61 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 62 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 63 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 64 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 65 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 66 Global Commands {interface interface-name} | bypass-routing] [count requests] [do-not-fragment] [router router-instance|service-name service-name][timeout timeout] Context <GLOBAL> Description This command is the TCP/IP utility to verify IP reachability. Parameters ip-address | dns-name — The remote host to ping. The IP address or the DNS name (if DNS name resolution is configured) can be specified.
Page 67 Root Commands pattern pattern — A 16-bit pattern string to include in the ping packet, expressed as a decimal integer. Values 0 — 16384 source ip-address — The source IP address to use in the ping requests in dotted decimal notation. Default The IP address of the egress IP interface.
Page 68 Global Commands service-name service-name — Specifies a unique service name to identify the service. Values [64 chars max] Syntax pwc [previous] Context <GLOBAL> Description This command displays the present or previous working context of the CLI session. The pwc com- mand provides a user who is in the process of dynamically configuring a chassis a way to display the current or previous working context of the CLI session.
Page 69 Root Commands Syntax ssh [ip-addr | dns-name |username@ip-addr] [-l username] [-v SSH-version] [router router- instance| service-name service-name] Context <GLOBAL> Description This command initiates a client SSH session with the remote host and is independent from the admin- istrative or operational state of the SSH server. However, to be the target of an SSH session, the SSH server must be operational.
Page 70 Global Commands router router-instance — Specify the router name or service ID. Values router-name: Base, management service-id: 1 — 2147483647 Default Base traceroute Syntax traceroute {ip-address | dns-name} [ttl ttl] [wait milliseconds] [no-dns] [source ip-address] [tos type-of-service] [router router-instance] Context <GLOBAL>...
Page 71 Root Commands Values router-name: Base, management service-id: 1 — 2147483647 Default Base tree Syntax tree [detail] Context <GLOBAL> Description This command displays the command hierarchy structure from the present working context. Parameters detail — Includes parameter information for each command displayed in the tree output. write Syntax write {user | broadcast} message-string...
Page 72 CLI Environment 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 73 Root 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 74 CLI Environment 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 75 Root 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 Description This command enables IP filter monitoring.
Page 76 Monitor CLI 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) -------------------------------------------------------------------------------...
Page 77 Root Commands The first screen displays the current statistics related to the specified IPv6 filter. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the "rate per second" for each statistic is displayed instead of the delta.
Page 78 Monitor CLI Commands ------------------------------------------------------------------------------- At time t = 9 sec (Mode: Absolute) ------------------------------------------------------------------------------- Ing. Matches : 0 pkts Egr. Matches : 0 pkts =============================================================================== *A:7210SAS>monitor>filter# Syntax mac mac-filter-id entry entry-id [interval seconds] [repeat repeat] [absolute | rate] Context monitor>filter Description This command enables MAC filter monitoring.
Page 79 Root Commands Monitor statistics for Mac filter 50 entry 10 =============================================================================== At time t = 0 sec (Base Statistics) ------------------------------------------------------------------------------- Ing. Matches: 0 Egr. Matches ------------------------------------------------------------------------------ At time t = 3 sec (Mode: Absolute) ------------------------------------------------------------------------------- Ing. Matches: 0 Egr. Matches ------------------------------------------------------------------------------- At time t = 6 sec (Mode: Absolute) -------------------------------------------------------------------------------...
Page 80 Monitor CLI Commands Parameters lag-id — The number of the LAG. Default none — The LAG ID value must be specified. Values 1 — 12 interval seconds — Configures the interval for each display in seconds. Default 5 seconds Values 3 —...
Page 81 Root Commands management-access-filter Syntax management-access-filter Context monitor Description This command enables the context to monitor management-access filters. These filters are configured in the config>system>security>mgmt-access-filter context. port Syntax port port-id [port-id...(up to 5 max)] [interval seconds] [repeat repeat] [absolute | rate] Context monitor Description...
Page 82 Monitor CLI Commands At time t = 0 sec (Base Statistics) ------------------------------------------------------------------------------- Octets Packets Errors ------------------------------------------------------------------------------- At time t = 3 sec (Mode: Absolute) ------------------------------------------------------------------------------- Octets Packets Errors ------------------------------------------------------------------------------- At time t = 6 sec (Mode: Absolute) ------------------------------------------------------------------------------- Octets Packets Errors ------------------------------------------------------------------------------- At time t = 9 sec (Mode: Absolute)
Page 83 Root Commands router Syntax router router-instance Context monitor Description This command enables the context to configure criteria to monitor statistical information for BGP, LDP, MPLS, OSPF and RSVP protocols. Parameters router-instance — Specify the router name or service ID. Values router-name: Base, management service-id:...
Page 84 Monitor CLI Commands 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. The first screen displays the current statistics related to the SAP. The subsequent statistical informa- tion listed for each interval is displayed as a delta to the previous display.
Page 85 Root Commands repeat repeat — Configures how many times the command is repeated. Default Values 1 — 999 absolute — When the absolute keyword is specified, the absolute rate-per-second value for each statistic is displayed. rate — When the rate keyword is specified, the rate-per-second for each statistic is displayed instead of the delta.
Page 86 Monitor CLI Commands I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0 E. Fwd. Pkts. : 0 E. Fwd. Octets : 0 ------------------------------------------------------------------------------- At time t = 22 sec (Mode: Delta) ------------------------------------------------------------------------------- I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0 E.
Page 87: Table 11: Show Alias Output Fields
Root 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 88 Show Commands Page 88 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 89: 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 90 → Compact Flash Devices on page 90 → USB Storage Device on page 91 →...
Page 90: The File System
The File System The File System The 7210 SAS file system is used to store files used and generated by the system, for example, image files, configuration files, logging files and accounting files. The file commands allow you to copy, create, move, and delete files and directories, navigate to a different directory, display file or directory contents and the image version.
Page 91: Usb Storage Device
File System Management Volume in drive cf1 on slot A is formatted as FAT32. Directory of cf1:\ 10/12/2011 10:37p 4248394 boot.tim 10/17/2011 07:28a 524 sasm.sdx 10/26/2011 10:06p 828 bof.cfg 10/27/2011 09:04p <DIR> act-collect 10/27/2011 09:06p <DIR> 10/17/2011 07:30a 0 test1.txt 10/26/2011 10:43p 5360 sasm.cfg...
Page 92: R6 Devices
The File System • The list of USB devices and the capacities that is supported for use with 7210 SAS are listed in the 7210 SAS OS Software Release Notes. • When an USB device is unplugged or removed from the system a major alarm is raised. The alarm can be cleared using the shutdown command.
Page 93 File System Management are located at the same location as the default configuration file. The default configuration file is created at the same place as the Timos image with which the system booted up. For example - If the no configuration file location was specified in the BOF and the Timos image (both.tim) located in uf1:\ was used to boot the system, then the default configuration file, the index file, the sdx file and nvsys.info file will be created on uf1:\ and used subsequently.
Page 94: Configuration Guidelines For Storing The Timos, Boot.tim, Bof.cfg, Ndx, Sdx And Nvsys.info File
The File System Configuration Guidelines for storing the Timos, boot.tim, BOF.cfg, ndx, sdx and nvsys.info file. • Store the boot.tim and BOF.cfg on cf1:\. Create a backup of the boot.tim and BOF.cfg on cf2:\ or uf1:\ • Store the both.tim, configuration file (and as a result the ndx, sdx, and nvsys.info) on cf2:\. Create a backup of these files on cf2:\ or uf1:\ or create a backup on SAM (Service Access Manager) or the network management station regularly.
Page 95: Urls
File System Management URLs The arguments for the 7210 SAS OS file commands are modeled after standard universal resource locator (URL). A URL refers to a file (a file-url) or a directory (a directory-url). 7210 SAS OS supports operations on both the local file system and on remote files. For the purposes of categorizing the applicability of commands to local and remote file operations, URLs are divided into three types of URLs: local, ftp and tftp.
Page 96: 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 97: 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 98: Creating Directories
File Management Tasks The following displays the file configuration: A:ALA-1>file cf1:\ # attrib cf1:\bootlog.txt cf1:\bof.cfg cf1:\boot.ldr cf1:\bootlog_prev.txt cf1:\BOF.SAV A:ALA-1>file cf1:\ # attrib +r BOF.SAV A:ALA-1>file cf1:\ # attrib cf1:\bootlog.txt cf1:\bof.cfg cf1:\boot.ldr cf1:\bootlog_prev.txt cf1:\BOF.SAV Creating Directories Use the command to create a new directory in the local file system, one level at a time. Enter the command to navigate to different directories.
Page 99: 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 100: 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 101: 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 102 File Management Tasks Page 102 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 103: 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 7210SAS-T and 7210 SAS-R6) —...
Page 104 File Command Reference Page 104 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 105 Configuration Commands Configuration Commands File System Commands shutdown Syntax [no] shutdown [cflash-id] Context file Description This command is available for use only with removable storage drives. The removable storage drives differ among the 7210 SAS platforms. It cannot be used with the internal non-removable compact flash.
Page 106: File Commands
File Commands File Commands attrib Syntax attrib [+r | -r] file-url attrib Context file Description This command sets or clears/resets the read-only attribute for a file in the local file system. To list all files and their current attributes enter attrib or attrib x where x is either the filename or a wildcard (*).
Page 107 Configuration Commands cf1:|uf1: - 7210 SAS-X +r — Sets the read-only attribute on the specified file. -r — Clears/resets the read-only attribute on the specified file. Syntax cd [file-url] Context file Description This command displays or changes the current working directory in the local file system. Parameters file-url —...
Page 108 File Commands copy Syntax copy source-file-url dest-file-url [force] Context file Description This command copies a file or all files in a directory from a source URL to a destination URL. At least one of the specified URLs should be a local URL. The optional wildcard (*) can be used to copy multiple files that share a common (partial) prefix and/or (partial) suffix.
Page 109 Configuration Commands <file-url> : <local-url>|<remote-url> - [255 chars max] local-url - [<cflash-id>/][<file-path>] remote-url - [{ftp://|tftp://}<login>:<pswd>@ <remote-locn>/][<file-path>] remote-locn - [ <hostname> | <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, for link local addresses cflash-id or usb-flash-id - cf1:|uf1: - 7210 SAS-M...
Page 110 File Commands d - [0..255]D interface - 32 chars max, for link local addresses cflash-id or usb-flash-id - cf1:|uf1: - 7210 SAS-M cf1:|cf2:|uf1: - 7210 SAS-T cf1:|cf1-A:|cf1-B:|cf2:|cf2-A:|cf2-B:|uf1:|uf1-A:| uf1-B: - 7210 SAS-R6 cf1:|uf1: - 7210 SAS-X Values force Forces an immediate deletion of the specified file(s). file delete * force deletes all the wildcard matching files without displaying a user prompt mes- sage.
Page 111 Configuration Commands cf1:|uf1: - 7210 SAS-X Values Use the file-url with the optional wildcard (*) to reduce the number of files to list. sort-order { d | n | s } — Specifies the sort order. Values d — date n —...
Page 112 File Commands Syntax md file-url Context file Description This command creates a new directory in a file system. Directories can only be created one level at a time. Parameters file-url — The directory name to be created. <local-url>|<remote-url> - [255 chars max] local-url - [<cflash-id>/ |<usb-flash-id>/][<file-path>] remote-url...
Page 113 Configuration Commands <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> | "["<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, for link local addresses cflash-id or usb-flash-id - cf1:|uf1: - 7210 SAS-M...
Page 114 File Commands file move force executes the command without displaying a user prompt message. Syntax rd file-url rf [force] Context file Description The rd command is used to delete a directory. If a directory has files and no sub-directories, the force option must be used to force delete the direc- tory and files it contains.
Page 115 Configuration Commands Parameters cflash-id — Specify the compact flash slot ID to be shut down or enabled. When a specific cflash-id is specified, then that drive is shutdown. If no cflash-id is specified, the drive referred to by the cur- rent working directory is assumed.
Page 116 File Commands 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 117 Configuration Commands cf1:|uf1: - 7210 SAS-M cf1:|cf2:|uf1: - 7210 SAS-T cf1:|cf1-A:|cf1-B:|cf2:|cf2-A:|cf2-B:|uf1:|uf1-A:| uf1-B: - 7210 SAS-R6 cf1:|uf1: - 7210 SAS-X version Syntax version file-url [check] Context file Description file This command displays the version of a TiMOS Parameters file-url — The file name of the target file. <local-url>|<remote-url>...
Page 118 File Commands Syntax vi local-url Context file Description Edit files using the vi editor. Parameters local-url — Specifies the local source file or directory. Values cflash-id -cf1: - 7210 SAS-M cflash-id -cf1:|uf: - 7210 SAS-X cflash-id -cf1:| -uf1: - 7210 SAS-T [<cflash-id>|<uflash-id>]<file-path>...
Page 119: 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 120 → Manual Mode on page 127 → Auto Init on page 128 → Ping Check in auto-init mode on page 135 −...
Page 120: System Intialization
System Intialization System Intialization Note: Some 7210 SAS platforms (For example: 7210 SAS-R6 ) 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 121 Boot Option Files • Boot by manually creating a BOF file (manual boot). • Boot by retrieving the BOF file from the network, using DHCP to get the network location of the BOF file (auto init). Auto-init is the default boot procedure if there is no manual-intervention during the first-time boot of the node.
Page 122: Figure 3: Bootstrap Load Process - System Initialisation - Part I
The following is an example of console display output when the file is located on cf1 and boot.tim the system boots successfully. 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 123: 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-M 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 124 System Intialization n — Minor release number Y: A — Alpha release B — Beta release M — Maintenance release R — Released software z — Version number both.tim — CPM and IOM image file Page 124 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 125: System Boot Options On 7210 Sas-M And 7210 Sas-X Devices
Boot Option Files System Boot Options on 7210 SAS-M and 7210 SAS-X devices The 7210 SAS-M and 7210 SAS-X supports booting the system using any of the following options: • Internal flash (cf1:\) • Network (with auto-init) • Network (without auto-init) NOTE: The 7210 SAS-M and 7210 SAS-X can use a both.tim (that is, Timos image) present on the USB storage stick for booting up.
Page 126 System Intialization • cf2:\ (external flash) • uf1:\ (external USB) If the bootrom does not find the boot.tim in any of the locations, the boot procedure fails. If the boot.tim is found in one of the locations, the system searches for BOF.cfg on the same storage device under the root directory (For example, if it finds boot.tim on cf2:\, then it looks for bof.cfg in cf2:\bof.cfg).
Page 127: Manual Mode
Boot Option Files Manual Mode If the user opts for the manual-mode boot procedure for the first time boot, the required parameters must be specified for a successful system boot. Manual mode configurations require authentication. The default password is password. BOF parameters that should be configured include: •...
Page 128: Auto Init
System Intialization Auto Init Note: Auto-init is not supported on 7210 SAS-R6. 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 129: Configuration And Image Loading
Boot Option Files cf1:\*TIMOS*\both.tim) . After successful bootup using the Timos 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 130: Figure 5: Bootstrap Process - System Initialization - Part Ii-A
Configuration and Image Loading Figure 5: Bootstrap Process - System Initialization - Part II-A Page 130 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 131: Figure 6: Automode With Partial Bof
Boot Option Files Figure 6: Automode with partial BOF 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 131...
Page 132: Figure 7: Bootstrap Process - System Initialization - Part Ii-B
Configuration and Image Loading Figure 7: Bootstrap Process - System Initialization - Part II-B Page 132 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 133: Figure 8: Bootstrap Process - System Initialization - Part Ii-C
Boot Option Files 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 134: Figure 9: Timos Boot - System Initialization - Part Iii
Configuration and Image Loading Figure 9: Timos Boot - System Initialization - Part III Page 134 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 135: Ping Check In Auto-Init Mode
Boot Option Files 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 136: Persistence
Configuration and Image Loading • For 7210 SAS-M 24F 2XFP (10GigE) (both standard and ETR variants) and 7210 SAS-X devices, the DHCP requests are sent out of port 1/1/25 and 1/1/26 as part of auto-init. The system attempts to obtain the system parameters and the BOF file location by sending out DHCP requests on the following ports in the order that appears as 1/1/1, 1/1/2, 1/1/25 and 1/1/26.
Page 137: Out-Of-Band (Oob) Ethernet Management Port
Boot Option Files Out-of-band (OOB) Ethernet Management Port The 7210 platforms support out-of-band ethernet management port for management of the node. An Out-of-band Ethernet port can be used to download the TIMOS image file and the configuration file by creating a BOF file manually. The out-of-band management port allows for use of both IPv4 and IPv6.
Page 138: Reset The Node To Factory Default Setting
Configuration and Image Loading Reset the node to factory default setting From release 4.0 and onwards, the default BOF password can be modified by the user. To edit the BOF parameters, user needs to provide the correct password. If the user forgets the password and fails to provide a correct password after three attempts, the system prompts the user to reset the BOF password to factory default.
Page 139 Boot Option Files eth-mgmt-speed #uplinkA Port Settings: uplinkA-port 1/1/1 uplinkA-address uplinkA-vlan #uplinkB Port Settings: uplinkB-port 1/1/2 uplinkB-address uplinkB-vlan #System Settings: wait persist console-speed 115200 uplink-mode network acl-mode IPv6-None use-expansion-card-type m4-ds1-ces console-disabled Hit a key within 3 seconds to change boot parameters... Enter password to edit the Boot Options File Or CTRL-D to exit the prompt Password:...
Page 140 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 141 Boot Option Files console-disabled Hit a key within 1 second to change boot parameters... Enter password to edit the Boot Options File Or CTRL-D to exit the prompt Password: Note: At this prompt, the default password “password” must be used. 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 141...
Page 142: Initial System Startup Process Flow
Initial System Startup Process Flow 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)
Page 143: Configuration Notes
Boot Option Files 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. 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 143...
Page 144 Configuration Notes Page 144 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 145: 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 145 • BOF Configuration Overview on page 146 •...
Page 146: Bof Configuration Overview
BOF Configuration Overview BOF Configuration Overview Alcatel-Lucent routers do not contain a boot EEPROM. The boostrap 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 147: Basic Bof Configuration
Boot Option Files Basic BOF Configuration The parameters which specify location of the image filename that the router will try to boot from and the configuration file are in the BOF. The most basic BOF configuration should have the following: •...
Page 148 Basic BOF Configuration console-speed 115200 console-disabled =============================================================================== A:dut-a>show# Page 148 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 149: 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 150 → Accessing the CLI on page 156 − Console Connection on page 156 • Configuring BOF Parameters on page 159 For details about hardware installation and initial router connections, refer to the specific hardware installation guide.
Page 150: 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 151 Boot Option Files Here are some examples cf1:/config.cfg ftp://user:passwd@192.168.1.150/./config.cfg ftp://user:passwd@[3FFE::1]/./config.cfg tftp://192.168.1.150/./config.cfg tftp://3FFE::1/./config.cfg 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 152: Sample Output For Bof Configuration On Bootup For 7210 Sas-R6
Common Configuration Tasks uplinkB port is configured for Boot Interface Management, Press ENTER to proceed with existing port settings Or "disable" to disable the port for Boot Interface Management Or "edit" to change the port settings: New Settings ------------ primary-image ftp://*:*@135.254.170.22//home/****/images/both.tim secondary-config tftp://10.135.25.100/STU/config.cfg...
Page 153 Boot Option Files a USB flash drive, or on the network. Here are some examples cf1:/timos1.0R1 uf1:/timos1.0R1 ftp://user:passwd@192.168.1.150/./timos1.0R1 ftp://user:passwd@[3FFE::1]/./timos1.0R1 tftp://192.168.1.150/./timos1.0R1 tftp://[3FFE::1]/./timos1.0R1 The existing Image URL is 'ftp://*:*@135.250.26.204/tmp/sasr/b/' Press ENTER to keep it. Software Image URL: Using: 'ftp://*:*@135.250.26.204/tmp/sasr/b/' Configuration File Location --------------------------- You must enter the location of configuration file to be used by TiMOS.
Page 154 Common Configuration Tasks eth-mgmt port is configured for Boot Interface Management, Press ENTER to proceed with existing port settings Or "disable" to disable the port for Boot Interface Management Or "edit" to change the port settings: edit You need to assign an IP address for this port. The IP address should be entered in standard dotted decimal form with a network length.
Page 155 Boot Option Files tertiary-config cf2:\SASR2553.cfg #eth-mgmt Port Settings: eth-mgmt-disabled eth-mgmt-address 10.135.25.53/24 active eth-mgmt-address 10.135.25.54/24 standby eth-mgmt-route 2.2.2.0/24 next-hop 10.135.25.1 eth-mgmt-route 3.3.3.0/24 next-hop 10.135.25.1 eth-mgmt-route 10.135.0.0/16 next-hop 10.135.25.1 eth-mgmt-route 135.0.0.0/8 next-hop 10.135.25.1 eth-mgmt-autoneg eth-mgmt-duplex full eth-mgmt-speed #System Settings: wait persist console-speed 115200 console-disabled Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no): y...
Page 156: Accessing The Cli
Common Configuration Tasks 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 157: Figure 11: 7210 Sas-M Front Panel Console Port
Boot Option Files Figure 11 displays an example of the Console port on a 7210 SAS-M front panel. Console Port 7210 SAS-M Service Access Switch 24 SFP Crit Figure 11: 7210 SAS-M Front Panel Console Port Figure 12 displays an example of the Console port on a 7210 SAS-T front panel. –A 10 11 14 15...
Page 158: Figure 13: 7210 Sas-X Front Panel Console Port
Common Configuration Tasks Figure 13 displays an example of the Console port on a 7210 SAS X front panel. Console Port SR72033A Figure 13: 7210 SAS-X Front Panel Console Port Figure 14: 7210 SAS-R6 Front Panel Console Port To establish a console connection: Connect the terminal to the Console port on the front panel using the serial cable.
Page 159: Configuring Bof Parameters
Boot Option Files Configuring BOF Parameters The following output displays a BOF configuration7210 SAS-M/X/T: A:7210>show# bof =============================================================================== BOF (Memory) =============================================================================== primary-image ftp://*:*@135.254.170.29//import/panos_builds/nightly/2.0 /S80/MTU-sultan/ primary-config tftp://10.135.25.100/MTU/mtu3DGP.cfg #eth-mgmt Port Settings: eth-mgmt-disabled #uplinkA Port Settings: uplinkA-port 1/1/24 uplinkA-address uplinkA-vlan #uplinkB Port Settings: uplinkB-port 1/1/2 uplinkB-address uplinkB-vlan...
Page 160: Service Management Tasks
Service Management Tasks Service Management Tasks This section discusses the following service management tasks: • System Administration Commands on page 160 → Viewing the Current Configuration on page 160 → Modifying and Saving a Configuration on page 162 → Deleting BOF Parameters on page 163 →...
Page 161 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 162: 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 163: 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 164 Service Management Tasks wait Page 164 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 165: Saving A Configuration To A Different Filename
Boot Option Files Saving a Configuration to a Different Filename Save the current configuration with a unique filename to have additional backup copies and to edit parameters with a text editor. You can save your current configuration to an ASCII file. Use either of the following CLI syntax to save a configuration to a different location: CLI Syntax: bof# save [cflash-id] Example...
Page 166 Service Management Tasks 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 When an admin reboot auto-init command is issued, the system resets the existing BOF file and reboots.
Page 167: 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 168 BOF Command Reference — [no] uplinkA-route ip-address/mask next-hop ip-address — uplinkA-vlan 0..4094 — 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 —...
Page 169: 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 170 File Management Commands Default Saves must be explicitly executed. BOF is saved at the same location as the location of boot.tim used for booting the system. Parameters flash-id — The compact flash ID where the bof.cfg is to be saved. Values cf1, cf2 (only on 7210 SAS-T and 7210 SAS-R6) Default...
Page 171 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 172: 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 173 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 174 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 175 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 176 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 177 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 178 File Management Commands uplink-mode Syntax uplink-mode {access-uplink| network} Context Description This BOF parameter allows the user to configure the system in either access- uplink mode or network mode. In access-uplink mode, the device allows for configuration of port in access-uplink mode and allow for use of access-uplink SAPs for service configuration.
Page 179 Boot Option Files ________________________________________________________________________________ Default none Parameters ip-address — Specifies an IPv4 ip-address in the form a.b.c.d, for example, 10.1.2.10. uplinkA-address Syntax uplinkA-address ip-address/mask no uplinkA-address Context Description This command configures the uplink-A address. The no form of the command sets the uplinkA to use DHCP to get the IP and the show bof value reflects 0 for this parameter.
Page 180 File Management Commands NOTES: • This command is not supported on 7210 SAS-R6 platforms. • 7210 SAS-T does not support use of IPv6 addresses. ________________________________________________________________________________ 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 181 Boot Option Files ________________________________________________________________________________ Parameters port-id — Specifies the secondary port to be used for boot up in the slot/mda/port format. uplinkA-route Syntax [no] uplinkA-route ip-address/mask next-hop ip-address Context Description This command configures an uplink-A static route. ________________________________________________________________________________ NOTE: This command is not supported on 7210 SAS-R6 platforms. ________________________________________________________________________________ Parameters ip-address —...
Page 182 File Management Commands of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Values 0 — 32 next-hop ip-address — The next hop IP address used to reach the destination. uplinkA-vlan Syntax uplinkA-vlan 0..4094...
Page 183 Boot Option Files Default eth-mgmt-autoneg — Auto-negotiation is enabled on the management Ethernet port. eth-mgmt-disabled Syntax [no] eth-mgmt-disabled Context Description This command allows the user to enable or disable the out-of-band management Ethernet port for use during boot up. The no form of the command enables the port. Default eth-mgmt-disabled eth-mgmt-duplex...
Page 184 File Management Commands Default No default routes are configured. Parameters ip-prefix\ip-prefix-length — The destination address of the static route in dotted decimal notation. 100 — The destination address of the static route in dotted decimal notation. Values ip-prefix|ip-prefix-length: ipv4-prefix a.b.c.d (host bits must be zero) ipv4-prefix-le 0 —...
Page 185 Boot Option Files currently specified in the BOF. A log message is displayed if a MDA type mismatch is detected. The system has to be re-booted if this parameter is changed. For 7210 SAS-M devices in access-uplink mode, only the 2x10G MDA is supported. Hence, the value of this parameter must be set to m2-xfp.
Page 186: Dns Configuration Commands
File Management Commands 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 187 Boot Option Files 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 188 File Management Commands x - [0..FFFF]H d - [0..255]D Page 188 7210 SAS M, T, X, R6 Basic System Configuration...
Page 189: 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 190 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 191 Boot Option Files 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# *A:ALA# show bof booted =============================================================================== System booted with BOF =============================================================================== 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...
Page 192 Show Commands uplinkA-vlan null uplinkA-route 10.135.0.0/16 next-hop 10.135.25.1 uplinkA-route 135.254.0.0/16 next-hop 10.135.25.1 #uplinkB Port Settings: uplinkB-port 1/1/24 uplinkB-address uplinkB-vlan #System Settings: wait persist console-speed 115200 uplink-mode access-uplink no-service-ports 1/1/24 1/1/2 use-expansion-card-type m2-xfp no console-disabled =============================================================================== A:7210-SAS>show# Sample output for 7210 SAS-M configured in Access uplink mode: *A:7210-SAS-M>bof# show bof =============================================================================== BOF (Memory)
Page 193 Boot Option Files speed wait persist console-speed 115200 console-disabled =============================================================================== A:dut-a>show# 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 193...
Page 194 Total Memory: 512MB Chassis Type: sas Card Type: badami_7210 TiMOS-L-0.0.I312 boot/mpc ALCATEL SAS-M 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 195 To enable SNMP, execute the command 'config>system>snmp no shutdown'. TiMOS-B-1.0.B1-12 both/mpc ALCATEL SAS-M 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 196 Show Commands Page 196 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 197: 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 199 → System Information on page 199 − System Name on page 199 − System Contact on page 199 −...
Page 198 System Basics Introduction • IEEE 1588v2 PTP on page 229 → PTP Clock Synchronization on page 233 → PTP Capabilities on page 237 → PTP Ordinary Slave Clock For Frequency on page 238 → PTP Ordinary Master Clock For Frequency on page 191 →...
Page 199: System Management Parameters
System Management 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 200: 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 201: 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 202: System Time
System Basics Introduction 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 203 System Management Table 16: 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 Eastern Time...
Page 204: Network Time Protocol (Ntp)
System Basics Introduction 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 205: Sntp Time Synchronization
System Management • In order to avoid the generation of too many events/trap the NTP module will rate limit the generation of events/traps to three per second. At that point a single trap will be generated that indicates that event/trap squashing is taking place. SNTP Time Synchronization For synchronizing the system clock with outside time sources, the 7210 SAS MOS software includes a Simple Network Time Protocol (SNTP) client.
Page 206: Cron
System Basics Introduction 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 207: High Availability
System Management High Availability NOTE: High availability with control plane redundancy is an option available for use only on 7210 SAS-R6. Control plane redundancy option is not available on 7210 SAS-X, 7210 SAS-M and 7210 SAS-T. These platforms support only component redundancy as described below. 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.
Page 208: Redundancy
System Basics Introduction Redundancy The redundancy features enable the duplication of data elements to maintain service continuation in case of outages or component failure. Software Redundancy on 7210 SAS-R6 Software outages are challenging even when baseline hardware redundancy is in place. There should be a balance to provide high availability routing otherwise router problems typically propagate not only throughout the service provider network, but also externally to other connected networks possibly belonging to other service providers.
Page 209 System Management • Hot standby — The router image, configuration, and network state is already loaded on the standby and it receives continual updates from the active route processor and the swapover is immediate. However, hot standby affects conventional router performance as more frequent synchronization increases consumption of system resources.
Page 210: Nonstop Forwarding On 7210 Sas-R6
System Basics Introduction Nonstop Forwarding on 7210 SAS-R6 In a control plane failure or a forced switchover event, the router continues to forward packets using the existing stale forwarding information. Nonstop forwarding requires clean control plane and data plane separation. Usually the forwarding information is distributed to the IMMs. Nonstop forwarding is used to notify peer routers to continue forwarding and receiving packets, even if the route processor (control plane) is not working or is in a switch-over state.
Page 211: Cpm Switchover On 7210 Sas-R6
System Management CPM Switchover on 7210 SAS-R6 During a switchover, system control and routing protocol execution are transferred from the active to the standby CPM. An automatic switchover may occur under the following conditions: • A fault condition that causes the active CPM to crash or reboot. •...
Page 212: Temperature Threshold Alarm And Fan Speed
System Basics Introduction Temperature Threshold Alarm and Fan Speed Temperature Threshold Alarm and Fan Speed for 7210 SAS-M, 7210 SAS-T and 7210 SAS-X and 7210 SAS-R6 devices Table 17 Table 18 show the over-temperature threshold and fan speed values for 7210 SAS devices: Table 17: Over-Temperature Threshold for 7210 SAS devices Device Variants...
Page 213: Synchronization
System Management Synchronization Synchronization between the CPMs includes the following: • Configuration and boot-env Synchronization on page 213 • State Database Synchronization on page 213 Configuration and boot-env Synchronization Configuration and boot-env synchronization are supported in admin>redundancy> synchronize and config>redundancy>synchronize contexts. State Database Synchronization If a new standby CPM/CFM is inserted into the system, it synchronizes with the active CPM/CFM upon a successful boot process.
Page 214: Synchronization And Redundancy
System Basics Introduction Synchronization and Redundancy 7210 SAS-R6 routers supporting redundancy use a 1:1 redundancy scheme. Redundancy methods facilitate system synchronization between the active and standby Control Processor Modules (CPMs) so they maintain identical operational parameters to prevent inconsistencies in the event of a CPM failure.
Page 215: Active And Standby Designations
System Management Active and Standby Designations Typically, the first Switch Fabric (SF)/CPM card installed in a redundant 7210 SAS-R6 chassis assumes the role as active, regardless of being inserted in Slot A or B. The next CPM installed in the same chassis then assumes the role as the standby CPM. If two CPM are inserted simultaneously (or almost simultaneously) and are booting at the same time, then preference is given to the CPM installed in Slot A.
Page 216: When The Active Cpm Goes Offline
System Basics Introduction When the Active CPM Goes Offline When an active CPM goes offline (due to reboot, removal, or failure), the standby CPM takes control without rebooting or initializing itself. It is assumed that the CPMs are synchronized, therefore, there is no delay in operability. When the CPM that went offline boots and then comes back online, it becomes the standby CPM.
Page 217: Network Synchronization
System Management Network Synchronization This section describes network synchronization capabilities available on 7210 SAS platforms. These capabilities involve multiple approaches to network timing; namely Synchronous Ethernet, PTP/1588v2, adaptive timing, and others. These features address barriers to entry by: • Providing synchronization quality required by the mobile space; such as radio operations and circuit emulation services (CES) transport.
Page 218: Central Synchronization Sub-System
System Basics Introduction Figure 15: Conventional Network Timing Architecture (North American Nomenclature) The architecture shown in Figure 17 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. •...
Page 219: Figure 16: Synchronisation Reference Selection On 7210 Sas-M, 7210 Sas-X
System Management platform. See Figure 16 below for a description of synchronization reference selection for the 7210 platforms. 7210 SAS-M (includes all variants), 7210 SAS-T (includes all variants), and 7210 SAS-X and 7210 SAS-R6, the recovered clock is able to derive the timing from any of the following references (also shown in the Figure 16 below):...
Page 220: Table 19: Revertive, Non-Revertive Timing Reference Switching Operation
System Basics Introduction Table 19 shows the selection followed for two references in both revertive and non-revertive modes: Table 19: Revertive, non-Revertive Timing Reference Switching Operation Status of Status of Active Reference Active Reference Reference A Reference B Non-revertive Case Revertive Case Failed Failed...
Page 221: Synchronizations Option Available On 7210 Sas Platforms
System Management Synchronizations Option available on 7210 SAS platforms The following table lists the synchronization options on various 7210 SAS platforms: Table 21: Synchronizations Option available on 7210 SAS-M, X, T, and R6 platforms Platform 7210 SAS-M 7210 SAS-T 7210 SAS-X 7210 SAS-R6 SyncE with SSM Supported...
Page 222: Synchronization Status Messages (Ssm)
System Basics Introduction Table 21: Synchronizations Option available on 7210 SAS-M, X, T, and R6 platforms Platform 7210 SAS-M 7210 SAS-T 7210 SAS-X 7210 SAS-R6 1588v2/PTP with Supported. PTP Supported (only Supported Not Supported Port-based hybrid mode on 10G ports) timestamps (time recommended for only with SyncE...
Page 223: E1 Signals
System Management DS1 signals can carry an indication of the quality level of the source generating the timing information using the SSM transported within the 1544 Kbit/s signal's Extended Super Frame (ESF) Data Link (DL) as specified in Recommendation G.704. No such provision is extended to SF formatted DS1 signals.
Page 224: Using Synchronous Ethernet Timing For T1/E1 Mda
System Basics Introduction delay variation). Therefore, the frequency accuracy and stability may be expected to exceed those of networks with un-synchronized physical layers. Synchronous Ethernet allows operators to gracefully integrate existing systems and future deployments into conventional industry-standard synchronization hierarchy. The concept behind synchronous Ethernet is analogous to SONET/SDH system timing capabilities.
Page 225: Clock Source Quality Level Definitions
System Management Clock Source Quality Level Definitions The following clock source quality levels have been identified for the purpose of tracking network timing flow. These levels make up all of the defined network deployment options given in Recommendation G.803 and G.781. The Option I network is a network developed on the original European SDH model;...
Page 226: Table 23: Synchronization Message Coding And Source Priorities
System Basics Introduction 1011 (sec/eec1) 1011 (sec) 8. Lowest quality qualified in QL- enabled mode 1100 (smc) 00100010 11111111 (smc) 00101000 11111111 (st4) 1110 (pno) 01000000 11111111 (pno) 1111 (dnu) 1111 (dus) 1111 (dnu) 00110000 11111111 (dus) Any other Any other Any other 13.
Page 227 System Management 1111 (dnu) 1111 (dus) 1111 dnu 00101000 11111111 (st4) 1111 (dnu) 1110 (pno) 1111 (dnu) 01000000 11111111 (pno) 1111 (dnu) 1111 (dus) 1111 (dnu) 00110000 11111111 (dus) 13. QL_INVALID 1111 (dnu) 1111 (dus) 1111 (dnu) 00110000 11111111 (dus) 14.
Page 228: Adaptive Clock Recovery
System Basics Introduction Adaptive Clock Recovery NOTE: ACR is supported only with CES MDA on 7210 SAS-M network mode. Adaptive Clock Recovery (ACR) is a timing-over-packet technology that transports timing information via periodic packet delivery over a pseudowire. ACR is used when there is no other Stratum 1 traceable clock available.
Page 229: Ieee 1588V2 Ptp
System Management IEEE 1588v2 PTP The Precision Time Protocol (PTP) is a timing-over-packet protocol defined in the IEEE 1588v2 standard 1588 PTP 2008. PTP may be deployed as an alternative timing-over-packet option to ACR. PTP provides the capability to synchronize network elements to a Stratum-1 clock or primary reference clock (PRC) traceable source over a network that may or may not be PTP-aware.
Page 230: Figure 17: Peer Clocks
System Basics Introduction Figure 17: 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 231: Table 24: Local Clock Parameters When Profile Is Set To Ieee1588-2008
System Management 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 232: Table 25: Local Clock Parameters When Profile Is Set To: Itu-Telecom-Freq
System Basics Introduction The 7210 SAS sets its local parameters as follows: Table 25: 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 233: Ptp Clock Synchronization
System Management Figure 18: 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 234 System Basics Introduction two-step synchronization operation can be used, with the two-step operation requiring a follow-up message after each synchronization message. NOTE: The 7210 SAS-M and 7210 SAS-X supports only two-step master port operation. 7210 SAS-T and 7210 SAS-R6 supports only one-step master port operation. All node types can operate slave ports that receive from a one-step or two-step master port.
Page 235: Figure 19: Ptp Slave Clock And Master Clock Synchronization
System Management Master Slave O = Offset = Slave - Master Sync D = Delay Follow_up (t1) t1, t2, t3, t4 are measured values t2 - t1 = Delay + Offset = 51 - 44 = 7 t4 - t3 = Delay - Offset = 57 - 56 = 1 Delay = ((t2-t1) + (t4 - t3))/2 = 4 Offset = ((t2 - t1) - (t4 - t3))/2 = 3 Delay_req...
Page 236: Figure 20: Using Ieee 1588V2 For Time Distribution For 7210 Sas-M And 7210 Sas-X
System Basics Introduction Figure 20: Using IEEE 1588v2 For Time Distribution for 7210 SAS-M and 7210 SAS-X Page 236 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 237: 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 238: 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 239: 1Pps And 10Mhz Interface
System Management IEEE 1588v2 can function across a packet network that is not PTP-aware; however, the performance may be unsatisfactory and unpredictable. PDV across the packet network varies with the number of hops, link speeds, utilization rates, and the inherent behavior of the routers. By using routers with boundary clock functionality in the path between the grand master clock and the slave clock, one long path over many hops is split into multiple shorter segments, allowing better PDV control and improved slave performance, see...
Page 240 System Basics Introduction • The PTP slave capability is available on all the ports on 7210 SAS-M, 7210 SAS-X, and 7210 SAS-T. • On 7210 SAS-M and 7210 SAS-X, 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 241: Configuration To Change Reference From Synce To Ptp On 7210 Sas-M And 7210 Sas-X
System Management Configuration to change reference from SyncE to PTP on 7210 SAS-M and 7210 SAS-X On 7210 SAS-M and 7210 SAS-X, use of PTP and SyncE as a reference simultaneously is not allowed. The user can configure either SyncE as a reference or PTP as a reference, but not both together.
Page 242: Example Configuration On Use Of Ptp And Synce References On 7210 Sas-T And 7210 Sas-R6
System Basics Introduction ql-selection -------------------> Optional , if we need Quality to be consisdered . 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]. This is called PTP Hybrid mode. 3.
Page 243 System Management *A:SAS-T-B>config>system>sync-if-timing# info detail ---------------------------------------------- ql-selection ref-order ptp ref1 ref2 --> All three reference can be configured simultaneously ref1 source-port 1/1/1 no shutdown no ql-override exit ref2 source-port 1/1/7 no shutdown no ql-override exit no ql-override no shutdown exit revert ---------------------------------------------- 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 244: Management Of 1830 Vwm
System Basics Introduction Management of 1830 VWM The 7210 SAS supports use and management of the 1830 VWM CWDM and 1830 VWM DWDM clip-on device. 1830 VWM is a family of cost-optimized managed WDM passive device, which is add-on shelf/NE and provides CWDM/DWDM extension to devices that do not have an in-built CWDM/DWDM capabilities.
Page 245: Feature Description
System Management optically terminates all the channels using either the 4-channel or the 8-channel termination module. The second channel is the intermediate OADM sites with 7210 SAS-M, and 7210 SAS- X. These sites use the CWDM passive units to add or drop channel in both the directions (east and west), for traffic to be processed by the node.
Page 246: 1830 Cwdm Shelf Layout And Description
System Basics Introduction unsupported devices results in an error log being printed. A shelf created by the user will be operationally down when an unrecognized device is plugged into the USB port. The user can interchange the device connected to the USB port without requiring a reboot. For example, when the 7210 SAS is operating with a clip-on device, the user can pull out the clip-on device, instead plug-in a USB mass-storage device to copy over image files or other files, and then plug back a clip-on device.
Page 247: 1830 Dwdm Shelf Layout And Description
System Management 1830 DWDM shelf layout and description The following describes the 1830 DWDM shelf and the entities that can be managed by 7210 SAS: Figure 25: 1830 DWDM Shelf layout • The slot #1 and slot #2 are capable of hosting DWDM Power and Controller modules (either EC-DW or EC-DWA).
Page 248 System Basics Introduction → The 7210 supports Fan Module. → The 7210 does not support BPM (Bulk Power Management) module (which allows for aggregation of 44 DWDM channels using the SFD44 unit). • The following events is tracked by the 7210 host related to these modules in slot#3 and slot#4: →...
Page 249: 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 250: Led Functionality
System Basics Introduction information on the number of units supported. • In a stacked/cascaded configuration, all 1830 units connected to the 7210 is of a similar type either ‘ec-cw’ or ‘ec-dw/ec-dwa’. It cannot be a mix of CWDM and DWDM types. NOTE: 1830 allows for a mix of passive DWDM and active DWDM devices in a stacked configuration and is supported on 7210.
Page 251: Table 29: Led Functionality For 7210 And 1830 Vwm (Dwdm)
System Management Table 29: 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 252: 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 253 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 254: System Resource Allocation
System Basics Introduction 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.
Page 255: Allocation Of Egress Internal Tcam Resources
System Management encounters a command to which resources cannot be allocated. The available resources can be allocated to different features. Please refer to the scaling guide for amount of resources available per platform and per feature. For ACL and QoS resources, the user has the option to allocate resources to limit usage per feature, irrespective of the match criteria used (that is, sum of all resources used for different SAP ingress classification match-criteria is limited by the amount allocated for SAP ingress classification) and can further allocate resources for use by specific match criteria.
Page 256: System Resource Allocation Examples
System Basics Introduction typically want to use different features. Therefore, ingress internal TCAM resource allocation capabilities has been extended to the egress internal TCAM resources. For more details about individual commands and features that use System Resource Allocation. Please see the CLI descriptions and the feature description in the respective user guides. NOTE: Boot-time commands under the config>...
Page 257 System Management config> system> resource-profile> acl-sap-ingress mac-match-enable max ipv4-match-enable 1 no ipv6_128-ipv4-match-enable ipv6_64-only-match-enable max exit In the above example CLI, the system will take the following actions: • 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.
Page 258: Configuration Guidelines For System Resource Profile
System Basics Introduction ipv6-64-bit criteria or the entire chunk is allocated to ipv6-64-bit criteria, if the first SAP that needs resources requests for ipv6-64-bit criteria and there are no entries in the chunk already allocated to ipv6-64-bit criteria, leaving no resources for use by mac-criteria. Configuration Guidelines for System Resource Profile The following configuration guidelines are applicable to 7210 SAS-R6: •...
Page 259: System Configuration Process Overview
System Management System Configuration Process Overview Figure 26 displays the process to provision basic system parameters. START CONFIGURE SYSTEM INFORMATION CONFIGURE TIME PARAMETERS Figure 26: System Configuration and Implementation Flow 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 259...
Page 260: 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 260 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 261: 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 263 • Common Configuration Tasks on page 264 • System Information on page 265 →...
Page 262: 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 263: 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 266 • System Time Elements on page 269 The following example displays a basic system configuration: A:ALA-12>config>system# info #------------------------------------------...
Page 264: 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 265 → Name on page 266 → Contact on page 266 →...
Page 265: 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 266: 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 267 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 268: 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 269: 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 270: Table 30: System-Defined Time Zones
Common Configuration Tasks Table 30: 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 271 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 272 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 273 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 274 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 275 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 276 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 277 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 278 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 279 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 280 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 281 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 282: 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 283 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 284 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 285 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 286 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 287 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 288 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 and QoS policies. Multiple policies may be included and each must be assigned a different priority;...
Page 289 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 M, T, X, R6 Basic System Configuration Guide Page 289...
Page 290: 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 291: 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 291 • Updating the Golden Bootstrap Image on page 292 • Disconnect on page 292 •...
Page 292: Updating The Golden Bootstrap Image
System Administration Parameters Updating the Golden Bootstrap Image The admin>update-golden-bootstrap command validates the input file, which must be a 7210 SAS M bootstrap image, and updates the golden bootstrap image with the contents of this file. CLI Syntax: admin update-golden-bootstrap [<file-url>] Example admin# update-golden-bootstrap boot.tim The following is an example of the output.
Page 293: 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 294 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 295: 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 296: 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 296...
Page 297: 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 298 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 299 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 300: System Timing
System Timing 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-M/X: *A:MTU>config>system>sync-if-timing# info detail ----------------------------------------------...
Page 301 System Management shutdown exit output shutdown line-length 110 exit exit shutdown no ql-override exit no revert ---------------------------------------------- *A:sasr_dutb>config>system>sync-if-timing# CLI Syntax for 7210 SAS-T: *A:SAS>config>system>sync-if-timing# info detail ---------------------------------------------- no ql-selection ref-order ref1 ref2 ptp bits1 bits2 ref1 shutdown no source-port no ql-override exit ref2 shutdown...
Page 302: Edit Mode
System Timing Edit Mode To enter the mode to edit timing references, you must enter the begin keyword at the config>system>sync-if-timing# prompt. Use the following CLI syntax to enter the edit mode: CLI Syntax: config>system>sync-if-timing begin The following error message displays when the you try to modify sync-if-timing parameters without entering the keyword begin.
Page 303: Configuring Timing References
System Management Configuring Timing References Listed below is an example to configure timing reference parameters. Example: config>system# sync-if-timing config>system>sync-if-timing# begin config>system>sync-if-timing# ref1 config>system>sync-if-timing>ref1# source-port 1/1/1 config>system>sync-if-timing>ref1# no shutdown config>system>sync-if-timing>ref1# exit config>system>sync-if-timing# ref2 config>system>sync-if-timing>ref2# source-port 1/1/2 config>system>sync-if-timing>ref2# no shutdown config>system>sync-if-timing>ref2# exit config>system>sync-if-timing>commit The following displays the timing reference parameters: *7210-SAS>config>system>sync-if-timing#info detail...
Page 304: Using The Revert Command
System Timing 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 305: Other Editing Commands
System Management Other Editing Commands The other editing commands are listed below: • commit : saves changes made to the timing references during a session. Modifications are not persistent across system boots unless this command is entered. • abort : discards changes that have been made to the timing references during a session. CLI Syntax: config>system>sync-if-timing abort...
Page 306: Forcing A Specific Reference
System Timing Forcing a Specific Reference The system synchronous timing output can be forced to use a specific reference. Note: The debug sync-if-timing force-reference command should be used only to test and debug problems. Once the system timing reference input has been forced, the system does not revert back to another reference unless explicitly re-configured or The system reverts to another reference if forced ref fails or QL received is dus/dnu and ql selection is enabled.
Page 307: Configuring System Monitoring Thresholds
System Management 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 308 Configuring System Monitoring Thresholds 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 309: System Alarm Contact Inputs
System Management System Alarm Contact Inputs The 7210 SAS platform hardware supports alarm contact inputs that allow an operator to monitor and report changes in the external environmental conditions. In a remote or outdoor deployment, alarm contact inputs allow an operator to detect conditions, for example, air conditioner fault, open door.
Page 310: Configuring 1830 Vwm
Configuring 1830 VWM 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 311 System Management =========================================================================== 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 312 Configuring 1830 VWM =========================================================================== *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 313: Configuring Lldp
System Management Configuring LLDP 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 tx-tlvs port-desc sys-cap tx-mgmt-address system exit...
Page 314 Configuring LLDP Page 314 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 315 System Management System Command Reference Command Hierarchies Configuration Commands NOTE: Not all CLI commands are supported on all the 7210 SAS platforms. Some commands are available only on some platforms. The support for a particular command for a given platform is either stated explicitly in the command reference OR in the CLI command description, as applicable.
Page 316 Command Hierarchies — no boot-bad-exec — boot-good-exec file-url — no boot-good-exec — chassis — allow-imm-family imm-family — no allow-imm-family — clli-code clli-code — no clli-code — config-backup count — no config-backup — contact contact-name — no contact — coordinates coordinates —...
Page 317: System Management
System Management — [no] shutdown — [no] shutdown 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 317...
Page 318 Command Hierarchies System Alarm Commands config — system — thresholds — 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 — 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 319: System Management
System Management PTP Commands 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 — network-type {sonet|sdh} — [no] peer ip-address [create] —...
Page 320 Command Hierarchies PTP Commands for 7210 SAS-R6 config — system — ptp — clock-type boundary — clock-type ordinary {slave} — [no] domain domain — [no] log-sync-interval value — network-type {sonet|sdh} — [no] peer ip-address [create] — [no] priority local-priority — [no] shutdown —...
Page 321 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 322 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 323 System Management — policy-id [time-range time-range-name] [priority priority] — no policy-id [time-range time-range-name] 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 323...
Page 324 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 325 System Management High Availability (Redundancy) Commands root — admin — display-config [detail |index] — redundancy — force-switchover [now] — rollback-sync — synchronize {boot-env | config} Configuration Rollback Commands for 7210 SAS-R6 root — admin — rollback — compare [to checkpoint2] —...
Page 326 Command Hierarchies — no source-address — [no] sync — [no] igmp — [no] igmp-snooping — port [port-id | lag-id] [sync-tag sync-tag] [create] — no port [port-id | lag-id] — range encap-range [sync-tag sync-tag] — no range encap-range — [no] shutdown —...
Page 327 System Management System Alarm Contact Commands config — system — alarm-contact-in-power {on|off} — 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 —...
Page 328 Command Hierarchies System Synchronization Commands for 7210 SAS-M and 7210 SAS-X config — system — sync-if-timing — abort — begin — commit — ref-order first second — no ref-order — — ql-override {prs | stu | st2 | tnc | st3e | st3 | prc | ssua | ssub | sec} —...
Page 329 System Management — no shutdown — shutdown — output — no shutdown — shutdown — commit — ref-order first second [third] [fourth] [fifth] — no ref-order — — ql-override {prs | stu | st2 | tnc | st3e | st3 | prc | ssua | ssub | sec} —...
Page 330 Command Hierarchies — ql-override {prs | stu | st2 | tnc | st3e | st3 | prc | ssua | ssub | sec} — no ql-override — [no] shutdown — ref1 — ql-override {prs | stu | st2 | tnc | st3e | st3 | prc | ssua | ssub | sec | eec1 | eec2} —...
Page 331 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 332 Command Hierarchies System Resource-Profile Commands for 7210 SAS-M, X, and T configure — system — resource-profile — g8032-fast-flood-enable (applicable only on 7210 SAS-M devices) — no g8032-fast-flood-enable — decommission — entry entry-id port port-range to port-range — no entry entry-id —...
Page 333 System Management — no mbs-pool 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 333...
Page 334 Command Hierarchies System Resource-Profile Router Commands for 7210 SAS-M, 7210 SAS-T, and 7210 SAS-X configure — system — resource-profile — router — ecmp max-routes-dest — no ecmp — ldp-ecmp percent-value — no ldp-ecmp — max-ip-subnets number — no max-ip-subnets Page 334 7210 SAS M, T, X, R6 Basic System Configuration...
Page 335 System Management System Resource-Profile Commands for 7210 SAS-R6 configure — system — resource-profile policy-id [create] — no resource-profile policy-id — description description-string — no description — 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 —...
Page 336 Command Hierarchies Global System Resource Profile Commands for 7210 SAS-R6 configure — system — global-res-profile — — no port-scheduler-mode — port-scheduler-mode — router — no ecmp — ecmp — ldp-ecmp percent-value — no ldp-ecmp — no max-ipv6-routes — max-ipv6-routes number —...
Page 337 System Management Show Commands show — alarm-contact-input alarm-contact-input-id [detail] — alarm-contact-input — chassis [environment] [power-supply] — cron — action action-name [owner owner-name] — schedule action-name [owner owner-name] — script script-name [owner owner-name] — tod-suite tod-suite-name [detail] associations failed-associations — time-range name associations [detail] —...
Page 338 Command Hierarchies — uptime Page 338 7210 SAS M, T, X, R6 Basic System Configuration...
Page 339 System Management Clear Commands clear — cron — action — completed [action-name] [owner action-owner] — screen action-name [owner owner-name] — system — inactive-peers — peer ip-address statistics — statistics — sync-if-timing {ref1 | ref2} — sync-if-timing {ref1 | ref2 | bits1 | bits2} 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 339...
Page 340 Command Hierarchies Debug Commands debug — sync-if-timing — force-reference {ref1 | ref2 | ptp} — force-reference {ref1|ref2|bits1|bits2|ptp} (Supported only on 7210 SAS-R6 and T) — no force-reference — [no] force-reference — [router router-name] [interface ip-int-name] Page 340 7210 SAS M, T, X, R6 Basic System Configuration...
Page 341 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>sync-if-timing>ref1 config>system>sync-if-timing>ref2 config>system>sync-if-timing>bits1>input config>system>sync-if-timing>bits1>output config>system>sync-if-timing>bits2>input config>system>sync-if-timing>bits2>output config>redundancy>multi-chassis>peer config>redundancy>multi-chassis>peer>mc-lag Description This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
Page 342 Generic Commands Default No description associated with the configuration context. Parameters string — The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
Page 343 System Management 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 344 System Information Commands 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:, cf2 (only on 7210 SAS-T) usb-flash-id uf1: Related exec command on page 61 — This command executes the contents of a text file as if they were CLI Commands commands entered at the console.
Page 345 System Management • A change in the current value of IMM family requires a reboot of the node to take effect. there- fore, the user configured value for IMM family type takes effect only after the next reboot. Default no allow-imm-family Parameters imm-family —...
Page 346 System Information Commands xyz.cfg.3 xyz.cfg.4 xyz.cfg.5 xyz.ndx Each persistent index file is updated at the same time as the associated configuration file. When the index file is updated, then the save is performed to xyz.cfg and the index file is created as xyz.ndx. Synchronization between the active and standby is performed for all configurations and their associated persistent index files.
Page 347 System Management The no form of the command reverts to the default value. 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 348 System Information Commands Syntax login-control Context config>system Description This command enables the context to configure login control. name Syntax name system-name no name Context config>system Description This command creates a system name string for the device. For example, system-name parameter ALA-1 for the name command configures the device name as ALA-1.
Page 349 System Management Parameters name — Specifies the operational group identifier up to 32 characters in length. Values [32 chars max] create — This keyword is required when first creating the configuration context. Once the context is created, it is possible to navigate into the context without the create keyword. Values Keyword hold-time...
Page 350 System Information Commands Page 350 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 351 System Management vwm-shelf Syntax [no] vwm-shelf vwm-shelf-id [create] Context config>system Description Platforms Supported: 7210 SAS-R6. 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 352 System Information Commands vwm-shelf Syntax [no] vwm-shelf vwm-shelf-id [vwm-type vwm-type] [create] Context config>system Description Platforms Supported: 7210 SAS-M, 7210 SAS-X, and 7210 SAS-T. 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 353 System Management • 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 Context config>system>vwm-shelf Description This command provides the context to provision the information for the modules that can be plugged into the slots on the 1830 VWM clip-on device.
Page 354 System Information Commands Syntax [no] card-type card-type Context config>system>vwm-shelf>card Description 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. The modules are identified using the acronyms listed below.
Page 355: Table 31: Card Type Acronyms For 1830 Cwdm Devices
System Management 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. Table 31: Card Type acronyms for 1830 CWDM devices Module Description Acronym...
Page 356 System Information Commands Module Description Acronym 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 1830VWM Remote Filter 4CH (AF Var) SFD4B_R...
Page 357 System Management Module Description Acronym 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 1830VWM Manual Filter 8CH (AC Var) SFD8C...
Page 358 System Information Commands Module Description Acronym 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 Amplifier Modules...
Page 359 System Management 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 360 System Alarm Commands 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 361 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’...
Page 362 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 363 System Management cflash-cap-alarm cf1-A: rising-threshold 50000000 falling-threshold 49999900 interval 120 rmon-event-type both start-alarm rising. cflash-cap-warn Syntax 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 Context config>system>thresholds Description This command enables capacity monitoring of the compact flash specified in this command. The severity level is warning.
Page 364 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 365 System Management The TiMOS logger message includes a rising or falling threshold crossing event indicator, the sample type (absolute or delta), the sampled value, the threshold value, the RMON-alarm-id, the associated RMON-event-id and the sampled SNMP object identifier. Use the no form of this command to remove an rmon-event-id from the configuration. Parameters rmon-event-type —...
Page 366 System Alarm Commands memory-use-alarm Syntax memory-use-alarm rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type] no memory-use-alarm Context config>system>thresholds Description The memory thresholds are based on monitoring the TIMETRA-SYSTEM-MIB sgiMemoryUsed object. This object contains the amount of memory currently used by the system. The severity level is The absolute sample type method is used.
Page 367 System Management destinations which may be CONSOLE, telnet session , memory log, cflash file, syslog, or SNMP trap destinations logs. both — In the case of both, both a entry in the RMON-MIB logTable and a TiMOS logger event are generated. none —...
Page 368 System Alarm Commands falling-threshold threshold — The falling-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.
Page 369 System Management rmon Syntax rmon Context config>system>thresholds Description This command creates the context to configure generic RMON alarms and events. Generic RMON alarms can be created on any SNMP object-ID that is valid for RMON monitoring (for example, an integer-based datatype). The configuration of an event controls the generation and notification of threshold crossing events configured with the alarm command.
Page 370 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 371 System Management 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'. This mode of operation where the PTP is used only for time recovery and syncE or BITS used for frequency recovery is also known as PTP Hybrid mode.
Page 372: Table 33: Values And The Corresponding Pps Rate
PTP Commands domain Syntax [no] domain domain Context config>system>ptp Description This command configures the PTP domain. The no form of the command reverts to the default configuration. Note some profiles may require a domain number in a restricted range. It is up to the operator to ensure the value aligns with what is expected within the profile.
Page 373 System Management 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. This value is used by the Best Master Clock Algorithm to determine which clock should provide timing for the network.
Page 374 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 375 System Management Default Parameters sdh — Specifies the values used on a G.781 Option 1 compliant network. sonet — Specifies the values used on a G.781 Option 2 compliant network. peer Syntax peer ip-address Context config>system>ptp This command configures a remote PTP peer. It provides the context to configure parameters for the remote PTP peer.
Page 376 PTP Commands 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 377: 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 378: 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 379 System Management Default none Parameters key-id — Configure the authentication key-id that will be used by the node when transmitting or receiving Network Time Protocol packets. Entering the authentication-key command with a key-id value that matches an existing configuration key will result in overriding the existing entry. Recipients of the NTP packets must have the same authentication key-id, type, and key value in order to use the data transmitted by this node.
Page 380 Date and Time Commands Values Base, management Default Base ip-int-name — Specifies the local interface on which to transmit NTP broadcast packets. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
Page 381 System Management authenticate — Specifies whether or not to require authentication of NTP PDUs. When enabled, NTP PDUs are authenticated upon receipt. ntp-server Syntax ntp-server [transmit key-id] no ntp-server Context config>system>time>ntp Description 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.
Page 382 Date and Time Commands version version — Specify the NTP version number that is generated by this node. This parameter does not need to be configured when in client mode in which case all three nodes are accepted. Default Values 2 —...
Page 383: Sntp Commands
System Management 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 384 Date and Time Commands server-address 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 —...
Page 385 System Management 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 386 Date and Time Commands 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 387 System Management 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 388 Date and Time Commands Parameters number — The number of times the schedule is run. Values 1 — 65535 Default 65535 day-of-month Syntax [no] day-of-month {day-number [..day-number] all} Context config>cron>sched Description This command specifies which days of the month that the schedule will occur. Multiple days of the month can be specified.
Page 389 System Management time — Specifies the time of day to schedule a command. Values hh:mm in hour:minute format hour Syntax [no] hour {..hour-number [..hour-number]| all} Context config>cron>sched Description This command specifies which hour to schedule a command. Multiple hours of the day can be specified.
Page 390 Date and Time Commands Values 0 — 59 (maximum 60 minute-numbers) all — Specifies all minutes. month Syntax [no] month {month-number [..month-number]|month-name [..month-name]| all} Context config>cron>sched Description This command specifies the month when the event should be executed. Multiple months can be specified.
Page 391 System Management weekday Syntax [no] weekday {weekday-number [..weekday-number]|day-name [..day-name]| all} Context config>cron>sched Description This command specifies which days of the week that the schedule will fire on. Multiple days of the week can be specified. When multiple days are configured, each of them will cause the schedule to occur.
Page 392 Date and Time Commands ipv4-address a.b.c.d cflash-id: cf1:, cf2 (only on 7210 SAS-T) usb-flash-id uf1: Page 392 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 393: Time Range Commands
System Management 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 394 Date and Time Commands 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 395 System Management 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 396 Date and Time Commands 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 397 System Management 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 Context...
Page 398 Date and Time Commands 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 399 System Management scheduler-policy Syntax [no] scheduler-policy scheduler-policy-name [time-range time-range-name] [priority priority] Context config>cron>tod-suite>egress config>cron>tod-suite>ingress Description This command creates time-range based associations of previously created scheduler policies. Multiple policies may be included and each must be assigned a different priority; in case time-ranges overlap, the priority will be used to determine the prevailing policy.
Page 400 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 401 System Management Values first, second, third, fourth, last Default first end-day — Specifies the starting day of the week when the summer time will end. Values sunday, monday, tuesday, wednesday, thursday, friday, saturday Default sunday end-month — The starting month of the year when the summer time will take effect. Values january, february, march, april, may, june, july, august, september, october, novem- ber, december...
Page 402 Date and Time Commands Parameters start-week — Specifies the starting week of the month when the summer time will take effect. Values first, second, third, fourth, last Default first start-day — Specifies the starting day of the week when the summer time will take effect. Default sunday Values...
Page 403 System Management defined time zones have implicit summer time settings which causes the switchover to summer time to occur automatically; configuring the dst-zone parameter is not required. A user-defined time zone name is case-sensitive and can be up to 5 characters in length. Values A user-defined value can be up to 4 characters or one of the following values: MT,WET,CET,EET,MSK,MSD,AST,NST,EST,CST,MST,PST,HST,AKST,AWST,...
Page 404 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 405 System Management • 7210 SAS-R6 supports configuration of only the BITS1 interface for use as an input or output reference. • 7210 SAS-T allows for configuration of both BITS1 and BITS2 interface as an input and output reference. • On 7210 SAS-T, the BITS1 configuration parameters such as bits-interface-type, line-length, source-reference, etc.
Page 406 System Synchronization Commands • 7210 SAS-R6 supports configuration of only the BITS1 interface for use as an input or output reference. • 7210 SAS-T allows for configuration of both BITS1 and BITS2 interface as an input and output reference. • On 7210 SAS-T, the BITS1 configuration parameters such as bits-interface-type, line-length, source-reference, etc.
Page 407 System Management NOTE: On 7210 SAS-T, BITS2 inherits the values configured for BITS1. The no form of the command reverts to the default configuration. Default ds1 esf Parameters ds1 esf — Specifies Extended Super Frame (ESF). This is a framing type used on DS1 circuits that consists of 24 192-bit frames, The 193rd bit provides timing and other functions.
Page 408 System Synchronization Commands Syntax ssm-bit sa-bit Context config>system>sync-if-timing>bits1 Description This command configures which sa-bit to use for conveying SSM information when the BITS interface-type is E1. SSM is not available when the BITS interface-type is either T1/DS1 SF synchronization interface. NOTE: On 7210 SAS-T, BITS2 inherits the value configured for BITS1.
Page 409 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 config>system>sync-if-timing>bits1 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 410 System Synchronization Commands ref-order Syntax ref-order first second [third] [fourth] [fifth] ref-order ptp no ref-order Context config>system>sync-if-timing Description The synchronous equipment timing subsystem can lock to different timing reference inputs, those specified in the ref1, ref2 and ptp command configuration. This command organizes the priority order of the timing references.
Page 411 System Management Values ref1, ref2, ptp ref1 Syntax ref1 Context config>system>sync-if-timing Description This command enables the context to configure parameters for the first timing reference. 7210 SAS M, T, X, R6 Basic System Configuration Guide Page 411...
Page 412 System Synchronization Commands ref2 Syntax ref2 Context config>system>sync-if-timing Description This command enables the context to configure parameters for the second timing reference. Page 412 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 413 System Management 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 414 Generic Commands Generic Commands shutdown Syntax [no] shutdown Context config>system>time>sntp config>system>lldpconfig>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 415 System Management System Administration Commands admin Syntax admin Context <ROOT> Description The context to configure administrative system commands. Only authorized users can execute the commands in the admin context. Default none check-golden-bootstrap Syntax check-golden-bootstrap Context admin Description This command validates the current golden bootstrap image, and displays its version, if found to be valid.
Page 416 System Administration Commands 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...
Page 417 System Management 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 418 System Administration Commands 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 419 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 420 System Administration Commands file-url — The file URL location to save the binary file. 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 remote-url: [{ftp://} login:pswd@remote-locn/][file-path] remote-locn [ hostname | ipv4-address] ipv4-address a.b.c.d...
Page 421 System Management System Alarm Contact Commands alarm-contact-in-power Syntax alarm-contact-in-power {on|off} Context config>system Description This command allows user to enable supply of +24V power to the alarm input. With this feature, users can use the power supplied through the alarm input pin to supply power to the external sensor devices, and Equipment cabinet door sensors, and so on connected to the alarm input, instead of using an external power source for the external sensor devices.
Page 422 System Alarm Contact Commands Syntax [no] alarm-output-severity {critical | major | none} (for 7210 SAS-M) [no] alarm-output-severity {critical | major | minor | none} (for 7210 SAS-X and 7210 SAS- T only) Context config>system>alarm-contact-input Description This command allows the user to relay alarms from the alarm-contact input to the alarm-contact output by associating an appropriate alarm-contact output with the alarm-contact input.
Page 423 System Management Syntax description description-string Context config>system>alarm-contact-input alarm-contact-input-id description Description This command describes an alarm contact input pin. The description provides an indication of the usage or attribute of the pin. It is stored in the CLI configuration file and helps the user in identifying the purpose of the pin.
Page 424 System Alarm Contact Commands Syntax [no] trigger-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 generates an alarm. The system generates a default message if the message is not configured.
Page 425 System Management Redundancy Commands redundancy Syntax redundancy Context admin config Description This command enters the context to allow the user to perform redundancy operations. rollback-sync Syntax no rollback-sync Context admin>redundancy Description This command copies the entire set of rollback checkpoint files from the active CPM CF to the inactive CPM CF.
Page 426 Redundancy Commands The no form of the command removes the parameter from the configuration. Default none Parameters boot-env — Synchronizes all files required for the boot process (loader, BOF, images, and config). config — Synchronizes only the primary, secondary, and tertiary configuration files. display-config Syntax display-config [detail | index]...
Page 427 System Management When the file-url parameter is not specified, no CLI script file is executed. Default none Parameters file-url — Specifies the location and name of the CLI script file. Values file url: local-url | remote-url: 255 chars max local-url: [cflash-id/][file-path] remote-url: [{ftp://|tftp://} login:pswd@remote-locn/][file-path]...
Page 428 Redundancy Commands This includes the saved configuration and CFM images. CPM/CFM CPM/ The active ensures that the active configuration is maintained on the standby . However, to ensure smooth operation under all circumstances, runtime images and system initialization configurations must also be automatically synchronized between the active and standby CPM/CFM If synchronization fails, alarms and log messages that indicate the type of error that caused the failure of the synchronization operation are generated.
Page 429 System Management peer-name Syntax peer-name name no peer-name Context config>redundancy>multi-chassis>peer Description This command specifies a peer name. Parameters name — The string may be up to 32 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 430 Redundancy Commands igmp-snooping Syntax [no] igmp-snooping Context config>redundancy>multi-chassis>peer>sync Description This command specifies whether IGMP snooping information should be synchronized with the multi- chassis peer. Default no igmp-snooping port Syntax port [port-id | lag-id] [sync-tag sync-tag] no port [port-id | lag-id] Context config>redundancy>multi-chassis>peer>sync Description...
Page 431 System Management Rollback Commands compare Syntax compare [to checkpoint2] compare checkpoint1 to checkpoint2 Context admin>rollback Description Platforms Supported: 7210 SAS-R6. This command displays the differences between rollback checkpoints and the active operational configuration, with source1 as the base/first file to which source2 is compared. Parameters checkpoint1 to checkpoint2 —...
Page 432 Rollback Commands rescue — Deletes the rescue checkpoint. No checkpoint suffix numbers are changed. rollback-location Syntax no rollback-location file-url Context config>system>rollback Description Platforms Supported: 7210 SAS-R6. The location and name of the rollback checkpoint files is configurable to be local (on compact flash) or remote.
Page 433 System Management remote-max-checkpoints Syntax remote-max-checkpoints <1..200> Context config>system>rollback Description Platforms Supported: 7210 SAS-R6. Configures the maximum number of rollback checkpoint files when the rollback-location is remote (For example: ftp). Default local-max-checkpoints Syntax local-max-checkpoints <1..50> Context config>system>rollback Description Platforms Supported: 7210 SAS-R6. Configures the maximum number of rollback checkpoint files when the rollback-location is on local compact flash.
Page 434 Rollback Commands revert Syntax revert checkpoint | rescue [now] Context admin>rollback Description Platforms Supported: 7210 SAS-R6. This command initiates a configuration rollback revert operation that will return the configuration state of the node to a previously saved checkpoint. The rollback revert minimizes impacts to running services.
Page 435 System Management Peer Commands peer Syntax [no] peer ip-address Context config>redundancy>multi-chassis Description Platforms Supported: 7210 SAS-R6. This command configures a multi-chassis redundancy peer. Parameters ip-address — Specifies a peer IP address. Multicast address are not allowed. authentication-key Syntax authentication-key [authentication-key | hash-key] [hash | hash2] no authentication-key config>redundancy>multi-chassis>peer Context...
Page 436 Rollback Commands Page 436 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 437 System Management MC-LAG Commands mc-lag Syntax [no] mc-lag Context config>redundancy>multi-chassis>peer>mc-lag Description This command enables the context to configure multi-chassis LAG operations and related parameters. The no form of this command administratively disables multi-chassis LAG. MC-LAG can only be issued only when mc-lag is shutdown. hold-on-neighbor-failure Syntax hold-on-neighbor-failure multiplier...
Page 438 Rollback Commands Parameters interval — The time interval expressed in deci-seconds Values 5 — 500 Syntax lag lag-id lacp-key admin-key system-id system-id [remote-lag lag-id] system-priority system-priority no lag lag-id Context config>redundancy>multi-chassis>peer>mc-lag Description This command defines a LAG which is forming a redundant-pair for MC-LAG with a LAG configured on the given peer.
Page 439 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 440 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 441 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 442 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 443 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 444 System Resource-Profile Commands System Resource-Profile Commands resource-profile Syntax resource-profile policy-id [create] no resource-profile policy-id Context configure>system Description This command enables the context to configure resource-profile parameters on the system. Default no default Parameters policy-id — Specifies a resource profile policy. Values 1 —...
Page 445 System Management | Total | Allocated | Free -------------------------------+-----------+-----------+------------ Ingress Shared CAM Entries | 0 | 0 | 512 If the configuration file contains a no form of this command, then the system does not allocate any resources for use by G.8032.The entire resource pool is available for use by ACLs. The no form of the command takes affect only on reboot.
Page 446 System Resource-Profile Commands The administrative state or the operational state of the port is not affected by configuring the port in a decommission entry. NOTE: • Any changes to the command, example - modifying the list of ports in existing entries or execu- tion of ‘no entry’...
Page 447 System Management Values port or port range. Example 1/1/1-1/1/3 or 1/1/1,1/1/4 Examples The following examples show the list of ports, range of ports, and a combination of list of ports and range of ports that can be specified. List of ports can be specified as: –...
Page 448 System Resource-Profile Commands With the no form of the command, software does not allocate any resources for use by egress filter policies. If no resources are allocated for use, then the software fails all attempts to associate a service entity (For example: SAP, IP interface) with a filter policy using any of the match criteria. Parameters num-resources —...
Page 449 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 450 System Resource-Profile Commands Syntax [no] Context configure>system>resource-profile>egress-internal-tcam>acl-sap-egress Description Syntax [no] Context configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress Description mac-ipv4-match-enable Syntax [no] mac-ipv4-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 IPv4 criteria or MAC criteria. The resources allocated are allocated on a first-cum-first-serve basis among service entities (For example: SAP, IP interface, etc) using IPv4 and MAC criteria egress filter policies.
Page 451 System Management Syntax [no] mac-ipv6-64bit-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 MAC criteria or IPv6 criteria using only the upper 64-bits of the IPv6 addresses. The resources allocated are allocated on a first-cum-first-serve basis among service entities (For example: SAP, IP interface, and more) using IPv6 64-bit and MAC criteria egress filter policies.
Page 452 System Resource-Profile Commands g8032-control-sap-tags Syntax [no] g8032-control-sap-tags vlan-range Context configure>system>resource-profile Platforms supported: 7210 SAS-R6 Description Allows user to configure the range of VLANs per IMM to be used internally with G8032 MEPs which support hardware CCM message processing. NOTE: User must ensure that the VLANs configured for use with G8032 MEPs is not configured for any of the SAPs configured on the IMM.
Page 453 System Management Values Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-M (per node) 7210 SAS-X (per node) 7210 SAS-T Access-Uplink mode (per node) 7210 SAS-T Network Mode (per node) 7210 SAS-R6 (per IMM) IMM-SAS-R: def (2) IMM-SAS-R-b: def (3) NOTE: On 7210 SAS-X, the limit applies to the total number of slices that can be used by ACLs across all match criteria supported on the node.
Page 454 System Resource-Profile Commands Values Platforms Min value Max value Default (per node) (per node) Values 7210 SAS-M (per node) 7210 SAS-X (per node) 7210 SAS-T Access-Uplink mode (per node) 7210 SAS-T Network Mode (per node) 7210 SAS-R6 (per IMM) 0 (per IMM) max —...
Page 455 System Management max — It is a special keyword. If user specifies max, then the software allocates one chunk when the first SAP is associated with a ingress filter policy using this match criteria. It continues to allocate resources to SAPs associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the command config>...
Page 456 System Resource-Profile Commands The resource cannot be shared with ingress filter or SAP ingress QoS filter policies using mac criteria or ipv6 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 ingress filter policies or SAP ingress QoS policies using ipv4 criteria.
Page 457 System Management 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. Please see the 7210 SAS Router Configuration guide for more information on resource allocation details and fields available for use. The resources cannot be shared with IPv4 filter policies or IPv6 filter policies specifying 128-bit addresses.
Page 458 System Resource-Profile Commands Syntax [no] mac-match-enable Context configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress configure>system>resource-profile>ingress-internal-tcam> qos-sap-ingress-resource Description This command allows the user to allocate maximum resources for use by ingress filter policies using mac criteria. Or when used under the qos-sap-ingress-resource context, its used to allocates resources for use by SAP ingress QoS policies using MAC criteria (any).
Page 459 System Management eth-cfm Syntax [no] eth-cfm Context configure>system>resource-profile>ingress-internal-tcam Description On 7210 SAS-M, 7210 SAS-T and 7210 SAS-X, the behavior is as follows: This command provides the context to allocate resources for CFM UP MEPs. With the no form of the command, software does not allocate any resources for use by CFM UP MEPs.
Page 460 System Resource-Profile Commands Syntax [no] down-mep Context configure>system>resource-profile>ingress-internal-tcam>eth-cfm Description This command is supported only on 7210 SAS-R6 platform. On 7210 SAS-R6, the functionality is as follows: This command provides the context to allocate resources for CFM Down MEPs. Resources from this pool is allocated towards the following: –...
Page 461 System Management Parameters num-resources — Specifies the maximum amount of resources for use by up-mep. Values [0..2] (For 7210 SAS-X and R6) [0..1] (For 7210 SAS-M and T) ipv6-ipv4-match-enable Syntax ipv6-ipv4-match-enable no ipv6-ipv4-match-enable Context configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource Description User needs to allocate resources from the SAP ingress QoS resource pool for ipv6-criteria by using the command "configure>...
Page 462 System Resource-Profile Commands Values Platforms Min value Max value Default (per node) (per node) Values 7210 SAS-M (per node) 7210 SAS-X (per node) 7210 SAS-T Access-Uplink mode (per node) 7210 SAS-T Network Mode (per node) 7210 SAS-R6 (per IMM) qos-sap-ingress-resource Syntax qos-sap-ingress-resource no qos-sap-ingress-resource...
Page 463 System Management The following are the min, max and default values: Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-M (per node) 7210 SAS-X (per node) 7210 SAS-T Access-uplink mode (per node) 7210 SAS-T Network Mode (per node) 7210 SAS-R6 IMM-SAS-R: def (3)
Page 464 System Resource-Profile Commands If user allocates resources for ingress ACLs (or for G8032-fast-flood feature in 7210-M network mode only) and then configures resources for SAP aggregate meter using this command, then the software does the following: • It does not allocate any additional chunks/resources from the available global ingress CAM resource pool to SAP aggregate meter, if it can allocate the required number of meters from the chunks/resources allocated to ingress ACLs (or from resources allocated to G8032-fast-flood in 7210-M network mode only).
Page 465 System Management allocated also varies based on the IMM plugged into the slot. The table below provides the values used for keyword ‘def’ on different 7210 platforms and on different IMM types. Platforms Min value Max value Default Values (per node) (per node) 7210 SAS-M (per node) 7210 SAS-X (per node)
Page 466 System Resource-Profile Commands this command and the amount of entries reserved for IP subnets using the command config> sys- tem> resource-profile> router> max-ip-subnets. Please read the description of the CLI com- mand “max-ip-subnets”. With the no form of the command, the software does not allocate any resources for use by IPv6 routes.
Page 467 System Management over-subscription of the ingress queued traffic must be prevented. The software does not implement any mechanism to detect the overload condition, hence proper care must be exercised by the user to prevent it. When the no form of the command is executed, on the next reboot, the mode of the device does not allow for use of unicast queues and shaping for SAP ingress traffic.
Page 468 System Resource-Profile Commands port — Use per port MBS pool, along with an option to relocate buffers to ports that need better burst handling capability using the decommissioning commands. Page 468 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 469 System Management router Syntax router Context configure>system>resource-profile - Supported on 7210-M,T, and X config>system>glob-res-profile - Supported on 7210-R6 Description This command enables the context to configure router parameters that is applicable to the entire chassis (in other words it applies to all IMMs). ecmp Syntax ecmp max-routes-dest...
Page 470 System Resource-Profile Commands Syntax ldp-ecmp percent-value no ldp-ecmp Context configure>system>resource-profile>router - Supported on 7210-M,T, and X config>system>glob-res-profile>router - Supported on 7210-R6 Description This command enables LDP ECMP and allows users to configure the percentage of the total amount of hardware ECMP resources to be allocated for use by LDP ECMP FECs. The remaining amount of resources are allocated for use by IP ECMP.
Page 471 System Management NOTES: • Each IPv4 subnet configured on the node requires 1 entry and each IPv6 subnet configured on the node requires 2 entries. In other words, each IPv6 /64-bit address prefixes requires twice the amount of space needed for IPv4 address prefix. Additionally, user must also account for resources required for IPv6 primary and secondary addresses assigned to an IPv6 interface.
Page 472 System Resource-Profile Commands • A separate route table is used for IPv6 /128-bit prefix route lookup. A limited amount of IPv6 / 128 prefixes route lookup entries is supported. The software enables lookups in this table by default (in other words, no user configuration is required to enable IPv6 /128-bit route lookup). •...
Page 473 System Management Global System Resource Profile Commands for 7210 SAS- global-res-profile Syntax global-res-profile Context config>system Description Platforms Supported: 7210 SAS-R6 This command provides the context to configure the CAM resources. Syntax Context config>system>glob-res-profile Description Platforms Supported: 7210 SAS-R6. This command provides port-scheduler-mode Syntax no port-scheduler-mode...
Page 474 Global System Resource Profile Commands for 7210 SAS-R6 When port-scheduler-mode is disabled, per SAP egress queues are available for use. Please see the QoS user guide for more details on the two modes. Enabling or Disabling port-scheduler-mode requires a reboot of the node. Default no port-scheduler-mode qos-sap-egress-resource...
Page 475 System Management Syntax eth-cfm-upmeps max_slices no eth-cfm-upmeps Context config>system>glob-res-profile>sf-ingress-internal-tcam Description Platforms Supported: 7210 SAS-R6. This command allocates resources towards UP MEP from the sf-ingress-internal-tcam pool. The value specified here allocates a fixed number of entries for use with this feature. Entries are allocated by software from this pool whenever UP MEP is configured in a VPLS service (either on a SAP or a SDP).
Page 476 Global System Resource Profile Commands for 7210 SAS-R6 Page 476 7210 SAS M, T, X, R6 Basic System Configuration Guide...
Page 477 System Management Show Commands YSTEM OMMANDS chassis imm-family Syntax chassis imm-family [imm-family] chassis imm-family {active|configured} Context show>system Description Platforms Supported: 7210 SAS-R6. With 'imm-family' option, this command lists the IMM types allowed to be provisioned (and equipped) in the chassis for the specified type of imm-family. The description for show chassis imm-family active | configured is as follows: With the 'active' option, this command displays the current active configuration of the IMM family.
Page 478 System Commands *A:sasr_dutb>show>system# chassis imm-family active =============================================================================== IMM FAMILY INFORMATION =============================================================================== IMM-TYPE IMM-FAMILY SUPPORTED ------------------------------------------------------------------------------- imm-sas-10sfp+1xfp imm-sas-r Supported (Default) imm-sas-10sfp imm-sas-r Supported (Default) imm-sas-2xfp imm-sas-r Supported (Default) =============================================================================== *A:sasr_dutb>show>system# =============================================================================== *A:sasr_dutb>show>system# chassis imm-family configured =============================================================================== IMM FAMILY INFORMATION =============================================================================== IMM-TYPE IMM-FAMILY SUPPORTED -------------------------------------------------------------------------------...
Page 479 System Management Output Standard Connection Output — The following table describes the system connections output fields. Label Description Proto Displays the socket protocol, either TCP or UDP. RecvQ Displays the number of input packets received by the protocol. TxmtQ Displays number of output packets sent by the application.
Page 480 System Commands Sample Detailed Output A:ALA-12# show system connections detail ------------------------------------------------------------------------------- TCP Statistics ------------------------------------------------------------------------------- packets sent : 659635 data packets : 338982 (7435146 bytes) data packet retransmitted : 73 (1368 bytes) ack-only packets : 320548 (140960 delayed) URG only packet window probe packet window update packet control packets...
Page 481: Table 34: Show System Cpu Output Fields
System Management Parameters sample-period seconds — The number of seconds over which to sample CPU task utilization. Default Values 1 — 5 Output System CPU Output — The following table describes the system CPU output fields. Table 34: Show System CPU Output Fields Label Description The total amount of CPU time.
Page 482 System Commands OSPF ~0.00% ~0.00% 5,600 0.27% 0.27% 0.00% 0.00% RTM/Policies 0.00% 0.00% Redundancy 3,635 0.18% 0.13% 1,462 0.07% 0.04% SNMP Daemon 0.00% 0.00% Services 2,241 0.11% 0.05% Stats 0.00% 0.00% Subscriber Mgmt 2,129 0.10% 0.04% System 8,802 0.43% 0.17% Traffic Eng 0.00% 0.00%...
Page 483 System Management Label Description Action Displays the name of the action. Action owner The name of the action owner. Administrative Enabled — Administrative status is enabled status Disabled — Administrative status is disabled Script The name of the script Script owner The name of the script owner.
Page 484 System Commands Error time : never Results file : ftp://*:*@192.168.15.18/home/testlab_bgp/cron/_20061106-203008. Run exit : Success ------------------------------------------------------------------------------- Script Run #18 ------------------------------------------------------------------------------- Start time : 2006/11/06 20:35:24 End time : 2006/11/06 20:40:40 Elapsed time : 0d 00:05:16 Lifetime : 0d 00:00:00 State : terminated Run exit code : noError Result time : 2006/11/06 20:40:40...
Page 485 System Management State : initializing Run exit code : noError Result time : never Keep history : 0d 01:00:00 Error time : never Results file : none ------------------------------------------------------------------------------- Script Run #23 ------------------------------------------------------------------------------- Start time : never End time : never Elapsed time : 0d 00:00:00 Lifetime...
Page 486 System Commands Label Description (Continued) Script owner Displays the name of the script. Script owner Displays the name of the of script owner. Script source Displays the location of scheduled script. location Script results Displays the location where the script results have been sent. location Schedule type Periodic —...
Page 487 System Management /cron/test1.cfg Script results location : ftp://*****:******@192.168.15.1/home/testlab_bgp /cron/res Schedule type : periodic Interval : 0d 00:01:00 (60 seconds) Next scheduled run : 0d 00:00:42 Weekday : tuesday Month : none Day of month : none Hour : none Minute : none Number of schedule runs : 10...
Page 488 System Commands Sample Output A:sim1>show>cron# script =============================================================================== CRON Script Information =============================================================================== Script : test Owner name : TiMOS CLI Description : asd Administrative status : enabled Operational status : enabled Script source location : ftp://*****:******@192.168.15.1/home/testlab_bgp /cron/test1.cfg Last script error : none Last change : 2006/11/07 17:10:03 ===============================================================================...
Page 489 System Management =============================================================================== System Global Resource Profile =============================================================================== ------------------------------------------------------------------------------- G8032 Fast Flood Eth-Cfm Vpls Upmeps Max-ipv6-routes : 1000 System-max-ecmp L3-max-ecmp-groups : 1024 Ldp-max-ecmp-groups : disable Ldp-ecmp-percent-value : disable Max-ip-subnets : 2000 port-scheduler-mode : disable ------------------------------------------------------------------------------- A:Dut-A>show>system# information Syntax information Context show>system Description This command displays general system information including basic system, SNMP server, last boot...
Page 490 System Commands Label Description (Continued) SNMP Oper State Enabled — SNMP is operationally enabled. Disabled — SNMP is operationally disabled. SNMP Index Boot Persistent — System indexes are saved between reboots. Status Not Persistent — System indexes are not saved between reboots.
Page 491: Table 35: Show Memory Pool Output Fields
System Management Label Description (Continued) Time Last Modified The date and time of the last modification. Max Cfg/BOF Backup The maximum number of backup revisions maintained for a configura- tion file. This value also applies to the number of revisions maintained for the BOF file.
Page 492 System Commands Table 35: Show Memory Pool Output Fields (Continued) Label Description No Limit — No size limit. Current Size The current size of the memory pool. The largest amount of memory pool used. Max So Far The current amount of the memory pool currently in use. In Use The sum of the Current Size column.
Page 493 System Management Context show>system Description This command displays NTP protocol configuration and state. Output Show NTP Output — The following table describes NTP output fields. Label Description Enabled — NTP is enabled. — NTP is disabled. Admin Status — Administrative state is enabled. —...
Page 494 System Commands Label Description (Continued) Chosen The peer is chosen as the source of synchronization. ChosenPPS The peer is chosen as the source of synchronization, but the actual syn- chronization is occurring from a pulse-per-second (PPS) signal. Remote The IP address of the remote NTP server or peer with which this local host is exchanging NTP packets.
Page 495 System Management Label Description (Continued) Auth yes — Authentication is enabled. no — Authentication is disabled. Poll Polling interval in seconds. Yes — The NTP peer or server has been reached at least once in the last 8 polls. No — The NTP peer or server has not been reached at least once in the last 8 polls.
Page 496 System Commands Syntax oper-group [group-name] oper-group group-name [detail] oper-group group-name [monitoring] Context show>system Description This command displays the oper-group information, member count, monitor-client count, and status in a single line for each of the configured oper-groups. Output Show oper-group Output — The following table describes oper-group output fields. Label Description Name...
Page 497 System Management rollback Syntax rollback [rescue] Context show>system Description This command displays rollback configuration and state. rescue — Revert to the rescue checkpoint. Sample Output A:7210SAS>show>system# rollback =============================================================================== Rollback Information =============================================================================== Rollback Location : None Max Local Rollback Files : 10 Max Remote Rollback Files : 10 Save...
Page 498: Table 36: Show System Resource-Profile Output Fields
System Commands Parameters active|configure — keyword - Displays active or configured values. Active values are those in use by the system currently. Configured values are those that have been changed by the user and has not taken effect. For the system resource-profile parameters that need a reboot to take effect, the active and configured values can be different.
Page 499 System Management Table 36: Show system resource-profile output fields. Label Description The total amount of egress internal CAM chunks configured for Mac and IPv4 Resource use by MAC and IPv4 egress ACL match criteria policies. Mac-only Resource The total amount of egress internal CAM chunks configured for use only by MAC egress ACL match criteria policies.
Page 500 System Commands ------------------------------------------------------------------------------- Router ------------------------------------------------------------------------------- max-ip-subnets : 384 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Router ------------------------------------------------------------------------------- system-max-ecmp ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Ingress Internal CAM ------------------------------------------------------------------------------- Sap Ingress Qos resource Aggregate Meter ------------------------------------------------------------------------------- IPv4 Resource : max Resource : max IPv4-IPv6 Resource : disable ------------------------------------------------------------------------------- Sap Ingress ACL resource ------------------------------------------------------------------------------- IPv4 Resource : max...
Page 501 System Management =============================================================================== Active System Resource Profile Information =============================================================================== Ingress Queue Mode : none ------------------------------------------------------------------------------- IPv6 FIB ------------------------------------------------------------------------------- max-ipv6-routes : disable ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Router ------------------------------------------------------------------------------- max-ip-subnets : 384 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Router ------------------------------------------------------------------------------- system-max-ecmp ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Ingress Internal CAM ------------------------------------------------------------------------------- Sap Ingress Qos resource Aggregate Meter ------------------------------------------------------------------------------- IPv4 Resource...
Page 502 System Commands Sample Output for 7210 SAS-T A:SAST>show>system# resource-profile =============================================================================== Active System Resource Profile Information =============================================================================== ------------------------------------------------------------------------------- IPv6 FIB ------------------------------------------------------------------------------- max-ipv6-routes : disable ------------------------------------------------------------------------------- Router ------------------------------------------------------------------------------- max-ip-subnets : 384 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Ingress Internal CAM ------------------------------------------------------------------------------- Sap Ingress Qos resource Aggregate Meter ------------------------------------------------------------------------------- IPv4 Resource...
Page 503 System Management Sample output for 7210 SAS-R6 devices *A:7210SAS>show>system# resource-profile ====================================================================== System Resource Profile ====================================================================== Policy-Id Description ---------------------------------------------------------------------- Default System Resource Profile Policy ====================================================================== *A:7210SAS>show>system# The show command for system resource profile commands with ‘def’ will display as follows. *A:7210SAS>show>system# resource-profile 1 =============================================================================== System Resource Profile Policy : 1 ===============================================================================...
Page 504 System Commands Syntax ptp [ peer <ip-address> [detail] | peers [detail] | unicast | statistics | standby] Context show>system Description This command displays the parameters for IEEE 1588-2008/ Precision Time Protocol Clock Informa- tion. Sample Output: A:7210SAS>show>system# ptp =============================================================================== IEEE 1588/PTP Clock Information =============================================================================== ------------------------------------------------------------------------------- Local Clock...
Page 505: Table 37: Show System Sntp Output Fields
System Management Description This command displays SNTP protocol configuration and state. Output Show SNTP Output — The following table describes SNTP output fields. Table 37: Show System SNTP Output Fields Label Description The SNTP server address for SNTP unicast client mode. SNTP Server The SNTP version number, expressed as an integer.
Page 506 System Commands Label Description (Continued) Startup Alarm Displays the alarm that may be sent when this alarm is first created. Owner Displays the owner of this alarm. Description Displays the event cause. Event Id Displays the identifier of the threshold event. Last Sent Displays the date and time the alarm was sent.
Page 507: Table 38: Show System Time Output Fields
System Management Description: TiMOS CLI - cflash capacity alarm rising event Event Id Last Sent : 10/31/2006 08:47:59 Action Type : both Owner : TiMOS CLI Description: TiMOS CLI - cflash capacity alarm falling event Event Id Last Sent : 10/31/2006 08:48:00 Action Type : both Owner...
Page 508 System Commands Table 38: Show System Time Output Fields (Continued) Label Description Non-standard — The zone is user-defined. Zone type Standard — The zone is system defined. The number of hours and minutes added to universal time for the zone, Offset from UTC including the DST offset for a DST zone The number of hours (always 0) and minutes (0—60) added to the time...
Page 509: Table 39: Show Vwm-Shelf Output Fields
System Management vwm-shelf Syntax vwm-shelf vwm-shelf-id [detail] Context show>system Description Lists all the shelves connected to the 7210 SAS node and display the administrative and operational state of the connected shelves. VWM-Shelf output — The following table describes the VWM-shelf output fields. Table 39: Show VWM-shelf Output Fields Label Description...
Page 510 System Commands Table 39: Show VWM-shelf Output Fields (Continued) Label Description The operational state of the 1830 device. It is set to UP if the 7210 SAS Operational state device is able to communicate and retrieve information from the 1830 device connected to it.
Page 511 System Management SFC2A&B SFC2A&B CWDM CWDM =========================================================================== 1830 VWM Shelf Controller-A Hardware Data =========================================================================== No of Slots Part Number : 3KC19297AAAB01 CLEI code : WOCUAZNUTA Unit Mnemonic : EC-CW Serial Number : EZ444555666 Manufacturing Date : 12112000 Administrative state : UP Operational state : UP Firmware version...
Page 512 System Commands Type State State Equipped slots --------------------------------------------------------------------------- DWDM =========================================================================== Slot Summary =========================================================================== Slot-ID Provisioned Equipped Admin Oper Type Type State State --------------------------------------------------------------------------- SFD4F_R SFD4F_R SFD8D_R SFD8D_R DWDM DWDM UP/Active DWDM DWDM UP/Stanby =========================================================================== *A:Dut-C# A:Dut-C# show system vwm-shelf 4 detail =========================================================================== Shelf Summary ===========================================================================...
Page 513 System Management CLEI code : ---------- Unit Mnemonic : EC-DW Serial Number : RT135100009 Manufacturing Date : 13122000 Administrative state : UP Operational state : UP/Stanby Firmware version : -------------- Current Alarm state : Cleared =========================================================================== 1830 VWM Slot/Module Hardware Data =========================================================================== Slot Number Provisioned type...
Page 514 System Commands =========================================================================== Shelf Summary =========================================================================== 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 =========================================================================== *A:7210SAS# show system vwm-shelf 7 detail ===========================================================================...
Page 515 System Management =========================================================================== Slot Number Provisioned type : SFC1D Equipped type : Equipped (SFC1D) Part Number : 3KC19289AEAA01 CLEI code : ---------- Unit Mnemonic : SFC1D Serial Number : EZ121130171 Manufacturing Date : 03192012 Operational state : UP Firmware version : -------------- Current Alarm state : Cleared...
Page 516: Table 40: Show System Tod-Suite Output Fields
System Commands 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 40: Show System tod-suite Output Fields Label Description Associations Shows which SAPs this tod-suite is associated with. Shows the SAPs or Multiservice sites where the TOD Suite could not failed-associa- tions...
Page 517 System Management 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. A:kerckhot_4# show cron tod-suite suite_sixteen failed-associations =============================================================================== Cron tod-suite associations failed =============================================================================== tod-suite suite_sixteen : failed association for SAP -------------------------------------------------------------------------------...
Page 518 System Commands Mac Learning : Enabled Discard Unkwn Srce: Disabled Mac Aging : Enabled Mac Pinning : Disabled L2PT Termination : Disabled BPDU Translation : Disabled Multi Svc Site : None I. Sched Pol : SchedPolCust1 Intend I Sched Pol : SchedPolCust1_Night E.
Page 519: Table 41: Show System Time-Range Output Fields
System Management A:kerckhot_4# show filter ip 160 associations =============================================================================== IP Filter =============================================================================== Filter Id : 160 Applied : No Scope : Template Def. Action : Drop Entries ------------------------------------------------------------------------------- Filter Association : IP ------------------------------------------------------------------------------- Tod-suite "english_suite" - ingress, time-range "day" (priority 5) =============================================================================== A:kerckhot_4# time-range...
Page 520 System Commands ------------------------------------------------------------------------------- IP Filter associations ------------------------------------------------------------------------------- IP filter Id : 10, entry 1010 ------------------------------------------------------------------------------- MAC Filter associations ------------------------------------------------------------------------------- None ------------------------------------------------------------------------------- Tod-suite associations ------------------------------------------------------------------------------- Tod-suite : suite_sixteen, for Ingress Qos Policy "1160" Tod-suite : suite_sixteen, for Ingress Scheduler Policy "SchedPolCust1_Day" Tod-suite : suite_sixteen, for Egress Qos Policy "1160"...
Page 521 System Management Label Description Displays the multi-chassis redundancy peer. Peer IP Address The text string describing the peer. Description If configured, displays the authentication key used between this node Authentication and the MC peer. Source IP Address Displays the source address used to communicate with the MC peer. Displays the administrative state of the peer.
Page 522 System Commands MC Peer Address : 10.10.10.2 MC Peer Lag-id MC System Id : 00:00:00:33:33:33 MC System Priority : 32888 MC Admin Key : 32666 MC Active/Standby : active MC Lacp ID in use : true MC extended timeout : false MC Selection Logic : peer decided MC Config Mismatch...
Page 523 System Management Packets Rx Peer Config Packets Rx State Packets Dropped Keep-Alive Task Packets Dropped Too Short Packets Dropped Verify Failed Packets Dropped Tlv Invalid Size Packets Dropped Out Of Seq Packets Dropped Unknown Tlv Packets Dropped Tlv Invalid MC-Endpoint Id Packets Dropped MD5 Packets Dropped Unknown Peer Packets Dropped MC Endpoint No Peer...
Page 524 System Commands =============================================================================== Number of Entries 1 =============================================================================== mc-lag Syntax mc-lag [lag lag-id] mc-lag peer ip-address lag lag-id statistics Context show>redundancy>multi-chassis Description This command displays multi-chassis LAG information. Parameters lag lag-id — Shows information for the specified LAG identifier. Values 1 —...
Page 525 System Management Label Description broken — The inband control connection with the peer has timed out. conflict — The inband control connection with the peer has timed out but the physical connection is still OK; the failure of the inband signaling con- nection is caused by a misconfiguration.
Page 526 System Commands VLAN Map B Path Provisioned ------------------------------------------------------------------------------ range 13-13 range 17-17 ------------------------------------------------------------------------------ VLAN Map Excluded Path Provisioned ------------------------------------------------------------------------------ range 18-18 ------------------------------------------------------------------------------ VLAN Map B Path Operational ------------------------------------------------------------------------------ range 13-13 range 17-17 ------------------------------------------------------------------------------ VLAN Map Excluded Path Operational ------------------------------------------------------------------------------ range 18-18 ============================================================================== *A:ALA-48>show>redundancy>multi-chassis# *A:ALA-48>show>redundancy>multi-chassis# mc-ring peer 192.251.10.104...
Page 527 System Management Failure Reason : None ------------------------------------------------------------------------------ Ring Node Connectivity Verification ------------------------------------------------------------------------------ Admin State : inService Service ID : 11 VLAN Tag : 11 Dest IP : 10.11.3.1 : None Interval : 1 minutes Src MAC : None ============================================================================== *A:ALA-48>show>redundancy>multi-chassis# *A:ALA-48>show>redundancy>multi-chassis# mc-ring peer 10.0.0.2 ring ring11 ring-node ============================================================================== MC Ring Node entries...
Page 528 System Commands Label Description Displays the number of valid MC-ring control packets of type 'kee- Keepalive palive' were received from the peer. *A:ALA-48>show>redundancy>multi-chassis# mc-ring peer 192.251.10.104 statistics ============================================================================== MC Ring statistics for peer 192.251.10.104 ============================================================================== Message Received Transmitted ------------------------------------------------------------------------------ MCS ID Request MCS ID Response Ring Exists Request Ring Exists Response...
Page 529 System Management Show mc-ring ring-node Command Output Label Description Displays the state of the connection verification (both local and Oper State remote). notProvisioned — Connection verification is not provisioned. configErr — Connection verification is provisioned but a configu- ration error prevents it from operating properly. notTested —...
Page 530 System Commands Label Description Displays the number of MC-ring signalling packets were received by Rx Unknown Ring Node this system that were related to an unknown ring node. Displays the number of MC-ring signalling packets were transmitted by this system. Displays the number of MC-ring signalling packets could not be trans- Tx No Buffer mitted by this system due to a lack of packet buffers.
Page 531 System Management Description This command displays synchronization information. Parameters port port-id — Shows the specified port ID of the multi-chassis peer. lag lag-id — Shows information for the specified LAG identifier. Values 1 — 20020064 Output Show Redundancy Multi-chassis Sync Output — The following table describes show redun- dancy multi-chassis sync output fields: Label Description...
Page 532 System Commands ------------------------------------------------------------------------------- Peer IP Address : 10.10.10.20 Description : Mc-Lag peer 10.10.10.20 Authentication : Disabled Source IP Address : 0.0.0.0 Admin State : Enabled ------------------------------------------------------------------------------- Sync-status ------------------------------------------------------------------------------- Client Applications : SUBMGMT Sync Admin State : Up Sync Oper State : Up DB Sync State : inSync...
Page 533: Table 42: System Timing Output Fields
System Management Context show Description This command displays the time since the system started. Output Uptime Output — The following table describes uptime output fields. Table 42: System Timing Output Fields Label Description Displays the length of time the system has been up in days, System Up Time hr:min:sec format.
Page 534 System Commands Label Description (Continued) Selected For Use Indicates if reference input 1 is selected for use Source Port Displays the source port information Reference Input 2 Displays information about reference input 2 Admin Status Indicates the Admin status of reference input 2. down —...
Page 535 System Management Label Description (Continued) Rx Quality Level Indicates the QL value received on the interface. • inv - SSM received on the interface indicates an invalid code for the interface type. • unknown - No QL value was received on the interface. The following example is for a node locked to the active BITS input and directing the signal on ref1 to the BITS output: Sample Output for 7210 SAS-M/X:...
Page 536 System Commands *A:MTU>show>system# Sample Output for 7210 SAS-R6: *A:sasr_dutb>show>system# sync-if-timing =============================================================================== System Interface Timing Operational Info =============================================================================== System Status CPM A : Master Free Run Reference Input Mode : Non-revertive Quality Level Selection : Disabled Reference Selected : none System Quality Level : st3 Reference Order : bits1 ref1 ref2 ptp...
Page 537 System Management Output Reference Selected : none Tx Quality Level : N/A Reference PTP Admin Status : down Rx Quality Level : unknown Quality Level Override : none Qualified For Use : No Not Qualified Due To disabled Selected For Use : No Not Selected Due To disabled...
Page 538 System Commands Interface Type : DS1 Framing : ESF Line Coding : B8ZS Line Length : 0-110ft Output Admin Status : down Output Source : internal clock Output Reference Selected : none Tx Quality Level : N/A Reference BITS 2 Input Admin Status : down Rx Quality Level...
Page 539 System Management Chassis Output — The following table describes chassis output fields. Label Description Name The system name for the router. Type The router series model number. Location The system location for the device. A user-configurable string that indicates the Global Positioning System Coordinates (GPS) coordinates for the location of the chassis.
Page 540 System Commands Label Description (Continued) Operational sta- Current status of the fan tray. Fan speed Half speed — The fans are operating at half speed. Full speed — The fans are operating at full speed. Number of power The number of power supplies installed in the chassis. supplies Power supply The ID for each power supply installed in the chassis.
Page 541 System Management CLEI code : IPMNX10GRA Serial number : NS1035F0181 Manufacture date : 08242010 Manufacturing string Manufacturing deviations : D01669 D01696 Time of last boot : 2010/11/10 14:38:43 Current alarm state : alarm cleared ------------------------------------------------------------------------------- Environment Information Number of fan trays Number of fans Fan tray number Status...
Page 542 System Commands Power supply number Configured power supply type : dc (+24V) Status : not equipped =============================================================================== A:7210-SAS-M# A:7210-SAS-M# show chassis power-supply =============================================================================== Chassis Information =============================================================================== Power Supply Information Number of power supplies Power supply number Configured power supply type : dc (+24V) Status : up...
Page 543 System Management Manufacturing assembly number Temperature : 39C Time of last boot : 2000/05/31 23:24:58 Current alarm state : alarm active ------------------------------------------------------------------------------- Environment Information Number of fan trays Number of fans Fan tray number Speed : unknown Status : failed ------------------------------------------------------------------------------- Power Supply Information Number of power supplies...
Page 544 System Commands Sample Output *A:7210-2# show alarm-contact-input 1 =============================================================================== Alarm Contact Input =============================================================================== Alarm Input Pin Number Alarm Input Pin Current State : Disabled Alarm Output Pin Used : Major =============================================================================== *A:7210-2# *A:7210-2# show alarm-contact-input 1 detail =============================================================================== Alarm Contact Input =============================================================================== Alarm Input Pin Number Alarm Input Pin Description...
Page 545 System Management Syntax pools Context show Description This command displays information on the buffer allocation and buffer usage per port. Output pools — The following table describes pools output fields Label Description Port Displays the Port ID of the port Application Indicates whether its access, network or access-uplink buffer pool.
Page 546 System Commands Label Description O.CIR/PIR Operational value of CIR/PIR after applying the adap- tation rule. A:7210SAS# show pools 1/1/2 access-egress =============================================================================== Pool Information =============================================================================== Port : 1/1/2 Application : Acc-Egr Slope Policy : default Resv CBS : Sum MMU Pool Total In Use: 1256 KB MMU Pool Shared In*: 1236 KB Pool Total : 910 KB...
Page 547 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 Platforms Supported: 7210 SAS-M and 7210 SAS-X. This command allows an operator to force the system synchronous timing output to use a specific ref- erence.
Page 548 System Commands This command allows an operator to force the system synchronous timing output to use a specific ref- erence. Note: This command should be used for testing and debugging purposes only. Once the system tim- ing reference input has been forced, it will not revert back to another reference at anytime. The state of this command is not persistent between system boots.
Page 549 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 550 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 551: Standards And Protocol Support
Standards and Protocol Support NOTE: The capabilities available when operating in access-uplink mode/L2 mode and network mode/MPLS mode are different. Correspondingly, not all the standards and protocols listed below are applicable to access-uplink mode and network mode. Standards Compliance RFC 2439 BGP Route Flap Dampening RFC 3046 DHCP Relay Agent Information Option (Option 82) RFC 2547bis BGP/MPLS VPNs...
Page 552 Standards and Protocols RFC 4552 Authentication/Confidentiality RFC 3478 Graceful Restart Mechanism Protocol, Version 3 (Snooping) [Only in for OSPFv3 for LDP — GR helper 7210 SAS-M and 7210 SAS-T access-uplink mode and supported RFC 4659 BGP-MPLS IP Virtual Private RFC 5283 LDP extension for Inter-Area with IPv4 Multicast in network Network (VPN) Extension for IPv6 mode]...
Page 553 Standards and Protocols RFC 2864 INVERTED-STACK-MIB RFC 4448 Encapsulation Methods for RFC 1350 The TFTP Protocol Transport of Ethernet over MPLS RFC 3014 NOTIFICATION-LOGMIB RFC 791 IP Networks (draft-ietf-pwe3-ethernet- RFC 3164 Syslog RFC 792 ICMP encap-11.txt) RFC 3273 HCRMON-MI RFC 793 TCP RFC 4446 IANA Allocations for PWE3 RFC 3411 An Architecture for RFC 826 ARP...
Page 554 Standards and Protocols Networked Measurement and TIMETRA-SAS-SERV-MIB.mib Control Systems. (Not Supported on TIMETRA-SAS-VRTR-MIB.mib 7210 SAS-R6) TIMETRA-SCHEDULER-MIB.mib TIMETRA-SECURITY-MIB.mib VPLS TIMETRA-SERV-MIB.mib RFC 4762 Virtual Private LAN Services TIMETRA-SYSTEM-MIB.mib Using LDP (previously draft-ietf- TIMETRA-TC-MIB.mib l2vpn-vpls-ldp-08.txt) TIMETRA-ISIS-MIB.mib TIMETRA-ROUTE-POLICY-MIB.mib VRRP TIMETRA-MPLS-MIB.mib RFC 2787 Definitions of Managed TIMETRA-RSVP-MIB.mib Objects for the Virtual Router TIMETRA-LDP-MIB.mib...
Page 555 Standards and Protocols Standards and Protocols Page 555...
Page 556 Standards and Protocols Page 556 Standards and Protocols...
Page 557: Index
NDEX compact flash devices URLs auto mode configuring command reference copying files creating directories displaying information overview modifying compact flash moving files synchronization removing/deleting image loading persistence saving a configuration configuring image loading accessing the CLI console connection basic lldp BOF parameters command reference management tasks...
Page 558 Index revert system administration parameters system parameters system time elements timing Page 558 7210 SAS M, T, and X Basic System Configuration...

This manual is also suitable for:

Alcatel-lucent 7210 sas tAlcatel-lucent 7210 sas r6 osAlcatel-lucent 7210 sas x