6.7. Configuring System Management with CLI

This section provides information about configuring system management features with CLI.

Topics in this section include:

6.8. System Management Configuration

6.8.1. Saving Configurations

Whenever configuration changes are made, the modified configuration must be saved so that 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 options file (BOF). For more information about the BOF, see Boot Options.

Configuration files are saved by executing explicit or implicit command syntax.

  1. An explicit save writes the configuration to the location specified in the save command syntax (the file-url option).
  2. An implicit save writes the configuration to the file specified in the primary configuration location.
    If the file-url option is not specified in the save command syntax, the system attempts to save the current configuration to the current BOF primary configuration source. If the primary configuration source (path and/or filename) changed since the last boot, the new configuration source is used.

The save command includes an option to save both default and non-default configuration parameters (the detail option).

The index option specifies that the system preserves system indexes when a save command is executed, regardless of the persistent status in the BOF file. 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, LSP IDs, and path IDs. This reduces resynchronizations of the Network Management System (NMS) with the affected network element.

If the save attempt fails at the destination, an error occurs and is logged. The system does not try to save the file to the secondary or tertiary configuration sources unless the path and filename are explicitly named with the save command.

6.9. 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:

The following example displays a basic system configuration:

ALU-1>config>system# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
        name "ALU-1"
        coordinates "Unknown"
        snmp
        exit
        security
            snmp
                community "private" rwa version both
            exit
        exit
        time
            ntp
                server 192.168.15.221 
                no shutdown
            exit
            sntp
                shutdown
            exit
            zone GMT
        exit
----------------------------------------------
ALU-1>config>system#

6.10. 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.

6.10.1. System Information

This section covers the basic system information parameters to configure the physical location of the 7705 SAR, contact information, router location information such as an address, floor, and room number, global navigation satellite system (GNSS) coordinates, and system name.

Use the CLI syntax displayed below to configure the following system components:

6.10.1.1. System Information Parameters

General system parameters include:

CLI Syntax:
config>system
name system-name
contact contact-name
location location
clli-code clli-code
coordinates coordinates

6.10.1.1.1. Name

Use the system name command to configure a name for the device. The name is used in the prompt string. Only one system name can be configured. If multiple system names are configured, the last one encountered overwrites the previous entry.

Use the following CLI syntax to configure the system name:

CLI Syntax:
config>system
name system-name
Example:
config>system# name ALU-1

The following example displays the system name:

ALU-1>config>system# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
        name "ALU-1"
. . .
        exit
----------------------------------------------
ALU-1>config>system#

6.10.1.1.2. Contact

Use the contact command to specify the name of a system administrator, IT staff member, or other administrative entity.

CLI Syntax:
config>system
contact contact-name
Example:
config>system# contact “Fred Information Technology”

6.10.1.1.3. Location

Use the location command to specify the system location of the device. For example, enter the city, building address, floor, and room number where the router is located.

Use the following CLI syntax to configure the location:

CLI Syntax:
config>system
location location
Example:
config>system# location “Bldg.1-floor 2-Room 201”

6.10.1.1.4. CLLI Code

The Common Language Location Code (CLLI code) is an 11-character standardized geographic identifier that is used to uniquely identify the geographic location of a 7705 SAR.

Use the following CLI command syntax to define the CLLI code:

CLI Syntax:
config>system
clli-code clli-code
Example:
config>system# clli-code abcdefg1234

6.10.1.1.5. Coordinates

Use the optional coordinates command to specify the GNSS location of the device. If the string contains spaces, 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:
config>system# coordinates "N 45 58 23, W 34 56 12"

The following example displays the configuration output of the general system commands:

ALU-1>config>system# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
name "ALU-1"
        contact "Fred Information Technology"
        location "Bldg.1-floor 2-Room 201"
        clli-code "abcdefg1234"
        coordinates "N 45 58 23, W 34 56 12"
 
. . .
        exit
----------------------------------------------
ALU-1>config>system#

6.10.1.1.6. System Identifier

The system identifier is an IPv4 address that can be used to uniquely identify the 7705 SAR in the network in situations where the system IP address may change dynamically.

Use the following CLI command syntax to define the system identifier:

CLI Syntax:
config>system
identifier id
Example:
config>system# identifier 192.0.2.255

6.10.1.2. 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:

Use the following CLI syntax to configure system time elements. The authentication-key des keyword is not supported if the 7705 SAR node is running in FIPS-140-2 mode.

CLI Syntax:
config>system
time
dst-zone zone-name
end {end-week} {end-day} {end-month} [hours-minutes]
offset offset
start {start-week} {start-day} {start-month} [hours-minutes]
gnss
port port-id time-ref-priority priority-value
ntp
authentication-check
authentication-key key-id {key key} [hash | hash2] {type des | message-digest}
broadcastclient [router router-name] {interface ip-int-name} [authenticate]
mda-timestamp
multicastclient [authenticate]
server {ip-address | ipv6-address} [key-id key-id] [version version] [prefer]
no shutdown
ptp
clock clock-id time-ref-priority priority-value
clock csm time-ref-priority priority-value
sntp
broadcast-client
server-address ip-address [version version-number] [normal | preferred] [interval seconds]
no shutdown
tod1-pps
message-type {ct | cm | irig-b002-b122 | irig-b003-b123 | irig-b006-b126 | irig-b007-b127}
zone {std-zone-name | non-std-zone-name} [hh[:mm]]

6.10.1.2.1. Zone

The zone command sets the time zone and/or time zone offset for the router. The 7705 SAR supports system-defined and user-defined time zones. The system-defined time zones are listed in Table 36.

CLI Syntax:
config>system>time
zone {std-zone-name | non-std-zone-name}
[hh [:mm]]
Example:
config>system>time# zone GMT

The following example displays the zone output:

ALU-1>config>system>time# info
----------------------------------------------
         ntp
                server 192.168.15.221 
                no shutdown
         exit
         sntp
                shutdown
         exit
         zone UTC 
----------------------------------------------
ALU-1>config>system>time#
Table 36:  System-defined Time Zones  

Acronym

Time Zone Name

UTC Offset

Europe:

GMT

Greenwich Mean Time

UTC

WET

Western Europe Time

UTC

WEST

Western Europe Summer Time

UTC +1 hour

CET

Central Europe Time

UTC +1 hour

CEST

Central Europe Summer Time

UTC +2 hours

EET

Eastern Europe Time

UTC +2 hours

EEST

Eastern Europe Summer Time

UTC +3 hours

MSK

Moscow Time

UTC +3 hours

MSD

Moscow Summer Time

UTC +4 hours

US and Canada:

AST

Atlantic Standard Time

UTC -4 hours

ADT

Atlantic Daylight Time

UTC -3 hours

EST

Eastern Standard Time

UTC -5 hours

EDT

Eastern Daylight Saving Time

UTC -4 hours

CST

Central Standard Time

UTC -6 hours

CDT

Central Daylight Saving Time

UTC -5 hours

MST

Mountain Standard Time

UTC -7 hours

MDT

Mountain Daylight Saving Time

UTC -6 hours

PST

Pacific Standard Time

UTC -8 hours

PDT

Pacific Daylight Saving Time

UTC -7 hours

HST

Hawaiian Standard Time

UTC -10 hours

AKST

Alaska Standard Time

UTC -9 hours

AKDT

Alaska Standard Daylight Saving Time

UTC -8 hours

Australia and New Zealand:

AWST

Western Standard Time

UTC +8 hours

ACST

Central Standard Time

UTC +9.5 hours

AEST

Eastern Standard/Summer Time

UTC +10 hours

NZT

New Zealand Standard Time

UTC +12 hours

NZDT

New Zealand Daylight Saving Time

UTC +13 hours

6.10.1.2.2. Summer Time Conditions

The dst-zone 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 will be adjusted by adding the configured offset when summer time starts and subtracting the configured offset when summer time ends.

CLI Syntax:
config>system>time
dst-zone zone-name
end {end-week} {end-day} {end-month} [hours-minutes]
offset offset
start {start-week} {start-day} {start-month} [hours-minutes]
Example:
config>system>time# dst-zone pt
config>system>time>dst-zone# start second sunday april 02:00
end first sunday october 02:00
config>system>time>dst-zone# offset 0

If the time zone configured is listed in Table 36, then the starting and ending parameters and offset do not need to be configured with this command unless there is a need to override the system defaults. The command will return an error if the start and ending dates and times are not available either in Table 36 or entered as optional parameters in this command.

The following example displays the configured parameters.

A:ALU-1>config>system>time>dst-zone# info 
----------------------------------------------
                start second sunday april 02:00
                end first sunday october 02:00
                offset 0
----------------------------------------------
A:ALU-1>config>system>time>dst-zone# offset 0

6.10.1.2.3. NTP

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.

NTP time elements include:

CLI Syntax:
config>system>time
ntp
authentication-check
authentication-key key-id {key key} [hash | hash2] {type des | message-digest}
broadcastclient [router router-name] {interface ip-int-name} [authenticate]
mda-timestamp
multicastclient [authenticate]
server {ip-address | ipv6-address} [key-id key-id] [version version] [prefer]
no shutdown

6.10.1.2.3.1. Authentication-check

The authentication-check command provides for the option to skip the rejection of NTP PDUs that do not match the authentication key or authentication type requirements. The default behavior when authentication is configured is to reject all NTP protocol PDUs that have a mismatch in either the authentication key ID, type, or key.

When authentication-check is configured, NTP PDUs are authenticated on receipt. However, mismatches cause a counter to be increased, one counter for key ID, one for type, and one for key value mismatches.

CLI Syntax:
config>system>time>ntp
authentication-check
Example:
config>system>time>ntp# authentication-check
config>system>time>ntp# no shutdown

6.10.1.2.3.2. 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.

CLI Syntax:
config>system>time>ntp
authentication-key key-id {key key} [hash | hash2] type {des | message-digest}
Example:
config>system>time>ntp# authentication-key 1 key A type des
config>system>time>ntp# no shutdown

The following example shows NTP disabled with the authentication-key parameter enabled.

A:ALU-1>config>system>time>ntp# info
----------------------------------------------
                shutdown
                authentication-key 1 key "OAwgNUlbzgI" hash2 type des 
----------------------------------------------
A:ALU-1>config>system>time>ntp# 

6.10.1.2.3.3. Broadcastclient

The broadcastclient command enables listening to NTP broadcast messages on the specified interface.

CLI Syntax:
config>system>time>ntp
broadcastclient[router router-name] {interface ip-int-name} [authenticate]
Example:
config>system>time>ntp# broadcastclient interface int11
config>system>time>ntp# no shutdown

The following example shows NTP enabled with the broadcastclient parameter enabled.

ALU-1>config>system>time# info
----------------------------------------------
            ntp
                broadcastclient interface int11
                no shutdown
            exit
            dst-zone PT
                start second sunday april 02:00
                end first sunday october 02:00
                offset 0
            exit
            zone UTC
----------------------------------------------
ALU-1>config>system>time#

6.10.1.2.3.4. MDA-timestamp

The mda-timestamp command enables timestamping on an adapter card by the network processor in order to allow more accurate timestamping for in-band NTP packets. Timestamping on an adapter card is only performed on Ethernet-based adapter cards. This command can only be set if NTP is shut down and all the NTP servers are not associated with an authentication key. This command does not change the behavior of NTP over the management port. Use the no form of this command to revert to the default behavior of having NTP packets timestamped by the CSM.

CLI Syntax:
config>system>time>ntp
mda-timestamp
Example:
config>system>time>ntp# mda-timestamp
config>system>time>ntp# no shutdown

The following example shows enhanced NTP performance enabled using the mda-timestamp command.

A:ALU-1>config>system>time>ntp# info
----------------------------------------------
                shutdown
                no authentication-key 1 
                mda-timestamp
----------------------------------------------
A:ALU-1>config>system>time>ntp# 

6.10.1.2.3.5. Multicastclient

This command is used to configure an address to receive multicast NTP messages on the CSM Management port. The no form of this command removes the multicast client.

If multicastclient is not configured, all NTP multicast traffic will be ignored.

CLI Syntax:
config>system>time>ntp
multicastclient [authenticate]
Example:
config>system>time>ntp# multicastclient authenticate
config>system>time>ntp# no shutdown

The following example shows NTP enabled with the multicastclient command configured.

ALU-1>config>system>time# info
----------------------------------------------
              server 192.168.15.221 
              multicastclient
              no shutdown
----------------------------------------------
ALU-1>config>system>time##

6.10.1.2.3.6. 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.

CLI Syntax:
config>system>time>ntp
server {ip-address | ipv6-address} [key-id key-id] [version version] [prefer]
Example:
config>system>time>ntp# server 192.168.1.1 key-id 1
config>system>time>ntp# no shutdown

The following example shows NTP enabled with the server command configured.

A:sim1>config>system>time>ntp# info
----------------------------------------------
            no shutdown
            server 192.168.1.1 key 1 
----------------------------------------------
A:sim1>config>system>time>ntp# 

6.10.1.2.4. 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:

CLI Syntax:
config>system>time
sntp
broadcast-client
server-address ip-address [version version-number] [normal | preferred] [interval seconds]
no shutdown

6.10.1.2.4.1. Broadcast-client

The broadcast-client command enables listening at the global device level to SNTP broadcast messages on interfaces with broadcast client enabled.

CLI Syntax:
config>system>time>sntp
broadcast-client
Example:
config>system>time>sntp# broadcast-client
config>system>time>sntp# no shutdown

The following example shows SNTP enabled with the broadcast-client parameter enabled.

ALU-1>config>system>time# info
----------------------------------------------
            sntp
                broadcast-client
                no shutdown
            exit
            dst-zone PT
                start second sunday april 02:00
                end first sunday october 02:00
                offset 0
            exit
            zone GMT
----------------------------------------------
ALU-1>config>system>time#

6.10.1.2.4.2. Server-address

The server-address command configures an SNTP server for SNTP unicast client mode.

CLI Syntax:
config>system>time>sntp
server-address ip-address version version-number] [normal | preferred] [interval seconds]
Example:
config>system>time>sntp# server-address 10.10.0.94 version 1 preferred interval 100

The following example shows SNTP enabled with the server-address parameter configured.

ALU-1>config>system>time# info
----------------------------------------------
            sntp
                server-address 10.10.0.94 version 1 preferred interval 100
                no shutdown
            exit
            dst-zone PT start-date 2018/04/04 12:00 end-date 2018/10/25 12:00
            zone GMT
----------------------------------------------
ALU-1>config>system>time#

6.10.1.2.5. PTP

Precision Time Protocol (PTP) is a timing-over-packet protocol defined in the IEEE 1588v2 standard 1588 2008. 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.

The ptp command specifies the PTP source as an option for recovered time. The specific PTP clock is identified by clock-id (from 1 to 16 for PTP clocks that use IPv4 or IPv6 encapsulation, and csm for PTP clocks that use Ethernet encapsulation) and has an assigned priority-value (from 1 to 16).

CLI Syntax:
config>system>time
ptp
clock clock-id time-ref-priority priority-value
clock csm time-ref-priority priority-value
Example:
config>system>time# ptp
config>system>time>ptp# clock 1 time-ref-priority 1

6.10.1.2.6. Time-of-Day Measurement (ToD-1pps)

The 7705 SAR can receive and extract time of day/phase recovery from a 1588 grand master clock or boundary clock and transmit the recovered time of day/phase signal to an external device such as a base station through an external time of day port, where available. Transmission is through the ToD or ToD/PPS Out port with a 1 pulse/s output signal. The port interface communicates the exact time of day by the rising edge of the 1 pulse/s signal.

The tod-1pps command specifies the format for the time of day (ToD) message that is transmitted out the ToD or ToD/PPS Out port and specifies whether the 1pps output is enabled.

CLI Syntax:
config>system>time
tod-1pps
message-type {ct | cm | irig-b002-b122 | irig-b003-b123 | irig-b006-b126 | irig-b007-b127}
output
Example:
config>system>time# tod-1pps
config>system>time>tod-1pps# message-type ct
config>system>time>tod-1pps# output

6.10.1.2.7. GNSS

For a 7705 SAR chassis that is equipped with a GNSS receiver and an attached GNSS antenna, the GNSS receiver can be used as a synchronous timing source. GNSS data is used to provide network-independent frequency and ToD synchronization.

The gnss command specifies a GNSS receiver port as a synchronous timing source. The specific GNSS receiver port is identified by port-id and has an assigned priority-value (from 1 to 16).

CLI Syntax:
config>system>time
gnss
port port-id time-ref-priority priority-value
Example:
config>system>time# gnss
config>system>time>gnss# port 1/2/1 time-ref-priority 1

6.10.1.2.8. CRON

The cron command is used for periodic and date- and time-based scheduling.

The schedule function configures the type of schedule to run, including one-time-only (one-shot), periodic, or calendar-based runs. All runs are scheduled by month, day, hour, minute, and interval (seconds). If end-time and interval are both configured, whichever condition is reached first is applied.

CLI Syntax:
config>system>cron
schedule schedule-name [owner schedule-owner]
count number
day-of-month {day-number [..day-number] | all}
description description-string
end-time [date | day-name] time
hour {hour-number [..hour-number] | all}
interval seconds
minute {minute-number [..minute-number] | all}
month {month-number [..month-number] | month-name [..month-name] | all}
script-policy policy-name [owner policy-owner]
type schedule-type
weekday {weekday-number [..weekday-number] | day-name [..day-name] | all}
no shutdown

The following example creates a schedule named “test2” to run a script policy named “test_policy” every 15 minutes on the 17th of each month and every Friday until noon on December 17, 2018:

Example:
config>system>cron# schedule test2
config>system>cron>sched# day-of-month 17
config>system>cron>sched# end-time 2018/12/17 12:00
config>system>cron>sched# minute 0 15 30 45
config>system>cron>sched# weekday friday
config>system>cron>sched# script-policy “test_policy”
config>system>cron>sched# no shutdown

6.10.2. Configuring Script Parameters

The 7705 SAR provides centralized script management for CLI scripts that are used by CRON and the Event Handling System (EHS). Scripts contain a set of CLI commands that are executed at a scheduled time or when an event is triggered.

The script and script-policy commands within the config>system>script-control context configure the script parameters.

The script command assigns a name to the script and references its location. When the script has been defined, a script-policy is configured that calls the previously configured script. The script-policy also specifies a location and filename that stores the results of the script run.

CLI Syntax:
config>system
script-control
script script-name [owner script-owner]
description description-string
location file-url
no shutdown
script-policy policy-name [owner policy-owner]
expire-time {seconds | forever}
lifetime {seconds | forever}
max-completed unsigned
results file-url
script script-name [owner script-owner]
no shutdown
Example:
config>system# script-control
config>system>script-control# script “test_script”
config>system>script-control>script# location "cf3:/test.txt"
config>system>script-control>script# no shutdown
config>system>script-control>script# exit
config>system>script-control# script-policy “test_policy”
config>system>script-control>script-policy# results "cf3:/script-results.txt"
config>system>script-control>script-policy# max-completed 4
config>system>script-control>script-policy# expire-time 7200
config>system>script-control>script-policy# no shutdown
config>system>script-control>script-policy# exit
config>system>script-control># exit

The following displays the configuration:

Dut-B>config>system>script-control# info
----------------------------------------------
            script "test_script"
                location "cf3:/test.txt"
                no shutdown
            exit
            script-policy "test_policy"
                results "cf3:/script-results.txt"
                script "test_script"
                max-completed 4
                expire-time 7200
                no shutdown
            exit
----------------------------------------------
Dut-B>config>system>script-control#

6.10.3. Configuring Synchronization and Redundancy

Use the CLI syntax displayed below to configure various synchronization and redundancy parameters:

6.10.3.1. Configuring Synchronization

The switchover-exec command specifies the location and name of the CLI script file executed following a redundancy switchover from the previously active CSM card.

CLI Syntax:
config>system
switchover-exec file-url

6.10.3.2. Configuring Manual Synchronization

Automatic synchronization can be configured in the config>system> synchronization context.

Manual synchronization can be configured with the following command:

CLI Syntax:
admin
redundancy
synchronize {boot-env | config}
Example:
admin>redundancy# synchronize config

The following shows the output that displays during a manual synchronization:

ALU-1>admin>redundancy# synchronize config 
 
Syncing configuration......
 
Syncing configuration.....Completed.
ALU-1# 

6.10.3.3. Forcing a Switchover

The force-switchover now command forces an immediate switchover to the standby CSM card.

CLI Syntax:
admin
redundancy
force-switchover [now]
Example:
admin>redundancy# force-switchover now
ALU-1# admin redundancy force-switchover now
ALU-1y#
Resetting...
?

If the active and standby CSMs are not synchronized for some reason, users can manually synchronize the standby CSM by rebooting the standby by issuing the admin reboot standby command on the active or the standby CSM.

6.10.3.4. Configuring Synchronization Options

Network operators can specify the type of synchronization operation to perform between the primary and secondary CSMs after a change has been made to the configuration files or the boot environment information contained in the BOF.

Use the following CLI command to configure the boot-env option:

CLI Syntax:
config
redundancy
synchronize {boot-env | config}
Example:
config>redundancy# synchronize boot-env

The following displays the configuration:

*ALU-1>config>redundancy# synchronize boot-env
*ALU-1>config>redundancy# show redundancy synchronization
===============================================================================
Synchronization Information
===============================================================================
Standby Status               : disabled
Last Standby Failure         : N/A
Standby Up Time              : N/A
Failover Time                : N/A
Failover Reason              : N/A
Boot/Config Sync Mode        : Boot Environment
Boot/Config Sync Status      : No synchronization
Last Config File Sync Time   : Never
Last Boot Env Sync Time      : Never
===============================================================================

Use the following CLI command to configure the config option:

CLI Syntax:
config
redundancy
synchronize {boot-env | config}
Example:
config>redundancy# synchronize config

The following example displays the configuration.

ALU-1>config>redundancy# synchronize config
ALU-1>config>redundancy# show redundancy synchronization
===================================================
Synchronization Information
===================================================
Synchronize Mode        : Configuration
Synchronize Status      : No synchronization
Last Config Sync Time   : 2006/06/27 09:17:15
Last Boot Env Sync Time : 2006/06/24 07:16:37
===================================================

6.10.3.5. Configuring Multi-Chassis Redundancy

When configuring multi-chassis redundancy, configuration must be performed on the two nodes that will form redundant-pair peer nodes. Each node will point to its peer using the peer command.

When creating a multi-chassis LAG, the LAG must first be created under the config>lag lag-id context. Additionally, the LAG must be in access mode and LACP must be enabled (active or passive). Under the multi-chassis>peer>mc-lag context, the lag-id is the ID of the previously created LAG.

Use the following CLI syntax to configure multi-chassis redundancy features:

CLI Syntax:
config>redundancy
multi-chassis
peer ip-address
authentication-key [authentication-key | hash-key] [hash | hash2]
description description-string
mc-lag
hold-on-neighbor-failure multiplier
keep-alive-interval interval
lag lag-id lacp-key admin-key system-id system-id [remote-lag lag-id] system-priority system-priority
no shutdown
source-address ip-address
Example:
config>redundancy#
config>redundancy# multi-chassis
config>redundancy>multi-chassis# peer 10.10.10.2 create
config>redundancy>multi-chassis>peer# description “Mc-Lag peer 10.10.10.2”
config>redundancy>multi-chassis>peer# mc-lag
config>redundancy>mc>peer>mc-lag# lag 1 lacp-key 32666 system-id 00:00:00:33:33:33 system-priority 32888
config>redundancy>mc>peer>mc-lag# no shutdown
config>redundancy>mc>peer>mc-lag# exit
config>redundancy>multi-chassis>peer# no shutdown
config>redundancy>multi-chassis>peer# exit
config>redundancy>multi-chassis# exit
config>redundancy#

The following displays the configuration:

A:7705:Dut-A>config>redundancy# info
----------------------------------------------
            multi-chassis
                peer 10.10.10.2 create
                   description "Mc-Lag peer 10.10.10.2"
                    mc-lag
                       lag 1 lacp-key 32666 system-id 00:00:00:33:33:33 system
priority 32888
                       no shutdown
                    exit
                    no shutdown
                exit
            exit
----------------------------------------------
A:7705:Dut-A>config>redundancy#

6.10.4. Configuring ATM Parameters

The ATM context configures system-wide ATM parameters.

CLI Syntax:
config>system
atm
atm-location-id location-id
Example:
config>system# atm
config>system>atm# atm-location-id 03:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

The following example shows the ATM configuration.

ALU-1>config>system>atm# info
----------------------------------------------
            atm-location-id 03:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
exit
----------------------------------------------
ALU-1>config>system>atm#

6.10.5. Configuring Backup Copies

The config-backup command allows you to specify the maximum number of backup versions of configuration and index files kept in the primary location.

For example, if the config-backup count is set to 5 and the configuration file is called xyz.cfg, the file xyz.cfg is saved with a .1 extension when the save command is executed. Each subsequent config-backup command increments the numeric extension until the maximum count is reached. The oldest file (5) is deleted as more recent files are saved.

  1. xyz.cfg
  2. xyz.cfg.1
  3. xyz.cfg.2
  4. xyz.cfg.3
  5. xyz.cfg.4
  6. xyz.cfg.5
  7. 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 CSMs is performed for all configurations and their associated persistent index files.

CLI Syntax:
config>system
config-backup count
Example:
config>system#
config>system# config-backup 7

The following example shows the config-backup configuration.

ALU-1>config>system> info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
        name "ALU-1"
        contact "Fred Information Technology"
        location "Bldg.1-floor 2-Room 201"
        clli-code "abcdefg1234"
        coordinates "N 45 58 23, W 34 56 12"
        config-backup 7
...
----------------------------------------------
ALU-1>config>system>

6.10.6. Configuring System Administration Parameters

Use the CLI syntax displayed below to configure various system administration parameters.

Administrative parameters include:

CLI Syntax:
admin
disconnect [address ip-address | username user-name | {console | telnet | ftp | ssh | mct}]
display-config [detail | index]
reboot [active | standby][upgrade][now]
set-time date time
save [file-url] [detail] [index]

6.10.6.1. Disconnect

The disconnect command immediately disconnects a user from a console, Telnet, FTP, SSH, SFTP, or MPT craft terminal (MCT) session.

The ssh keyword disconnects users connected to the node via SSH or SFTP.

Note:

Configuration modifications are saved to the primary image file.

CLI Syntax:
admin
disconnect [address ip-address | username user-name | {console | telnet | ftp | ssh | mct}]
Example:
admin# disconnect

The following example displays the disconnect command results.

     ALU-1>admin# disconnect
     ALU-1>admin# Logged out by the administrator
     Connection to host lost.

6.10.6.2. 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 (no shutdown), this command cannot be used. The set-time command does not take into account any daylight saving offset if defined.

CLI Syntax:
admin
set-time date time
Example:
admin# set-time 2010/09/24 14:10:00

The following example displays the set-time command results.

     ALU-1# admin set-time 2010/09/24 14:10:00
     ALU-1# show time
     Fri Sept 24 14:10:25 UTC 2010
     ALU-1#

6.10.6.3. Display-config

The display-config command displays the system’s running configuration.

CLI Syntax:
admin
display-config [detail] [index]
Example:
admin# display-config detail

The following example displays a portion of the display-config detail command results.

ALU-1>admin# display-config detail
# TiMOS-B-0.0.current both/i386 NOKIA SAR 7705 
# Copyright (c) 2016 Nokia.
# All rights reserved. All use subject to applicable license agreements.
# Built on Fri Sept 24 01:32:43 EDT 2016 by csabuild in /rel0.0/I270/panos/main
 
# Generated FRI SEPT 24 14:48:31 2016 UTC
 
exit all
configure
#------------------------------------------
echo "System Configuration"
#------------------------------------------
    system
        name "ALU-1"
        contact "Fred Information Technology"
        location "Bldg.1-floor 2-Room 201"
        clli-code "abcdefg1234"
        coordinates "N 45 58 23, W 34 56 12"
        config-backup 7
        boot-good-exec "ftp://*:*@xxx.xxx.xxx.xx/home/csahwreg17/images/env.cfg”
        no boot-bad-exec
        no switchover-exec
        snmp
            engineID "0000197f00006883ff000000"
            packet-size 1500
            general-port 161
            no shutdown
        exit
        login-control
            ftp
                inbound-max-sessions 3
            exit
            ssh
                no disable-graceful-shutdown
                inbound-max-sessions 5
                outbound-max-sessions 5
                ttl-security 100
            exit
            telnet
                no enable-graceful-shutdown
                inbound-max-sessions 5
                outbound-max-sessions 5
                ttl-security 50
            exit
            idle-timeout 1440
            pre-login-message "Property of Service Routing Inc.Unauthorized access
prohibited."
            motd text “Notice to all users: Software upgrade scheduled 3/2 1:00 AM"
            login-banner
            no exponential-backoff
        exit
        atm
            no atm-location-id
        exit
        security
            management-access-filter
                default-action permit
                entry 1
                    no description
...
ALU-1>admin#

6.10.6.4. Tech-support

The tech-support command creates a system core dump.

Note:

This command should only be used with explicit authorization and direction from the Nokia Technical Assistance Center (TAC).

6.10.6.5. Save

The save command saves the running configuration to a configuration file. When the debug-save parameter is specified, debug configurations are saved in the config file. If this parameter is not specified, debug configurations are not saved between reboots.

CLI Syntax:
admin
save [file-url] [detail] [index]
debug-save [file-url]
Example:
admin# save ftp://test:test@192.168.x.xx/./1.cfg
admin# debug-save debugsave.txt

The following example displays the save command results.

ALU-1>admin# save ftp://test:test@192.168.x.xx/./1x.cfg
Writing file to ftp://test:test@192.168.x.xx/./1x.cfg
Saving configuration ...Completed.
ALU-1>admin# debug-save ftp://test:test@192.168.x.xx/./debugsave.txt
Writing file to ftp://julie:julie@192.168.x.xx/./debugsave.txt
Saving debug configuration .....Completed.

6.10.6.6. Reboot

The reboot command reboots the router, including redundant CSMs in redundant systems. If the now option is not specified, you are prompted to confirm the reboot operation. The reboot upgrade command forces an upgrade of the boot ROM and a reboot.

CLI Syntax:
admin
reboot [active | standby] | [upgrade] [now]
Example:
admin# reboot now

If synchronization fails, the standby does not reboot automatically. The show redundancy synchronization command displays synchronization output information.

6.10.6.7. 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. The commands are persistent between router (re)boots and are included in the configuration saves (admin>save).

CLI Syntax:
config>system
boot-bad-exec file-url
boot-good-exec file-url
Example:
config>system# boot-bad-exec ftp://t:t@192.168.xx.xxx/./
fail.cfg
config>system# boot-good-exec
ftp://test:test@192.168.xx.xxx/./
ok.cfg

The following example displays the command output:

ALU-1>config>system# info
#------------------------------------------
echo "System Configuration"
#------------------------------------------
        name "ALU-1"
        contact "Fred Information Technology"
        location "Bldg.1-floor 2-Room 201"
        clli-code "abcdefg1234"
        coordinates "N 45 58 23, W 34 56 12"
        config-backup 7
        boot-good-exec "ftp://test:test@192.168.xx.xxx/./ok.cfg"
        boot-bad-exec "ftp://test:test@192.168.xx.xxx/./fail.cfg"
        sync-if-timing
            begin
            ref-order ref1 ref2 bits
..
----------------------------------------------
ALU-1>config>system#

6.10.6.7.1. Show Command Output and Console Messages

The show>system>information command displays the current value of the bad/good exec URLs and indicates whether a post-boot configuration extension file was executed when the system was booted. If an extension file was executed, the show>system> information command also indicates if it completed successfully or not.

7705:Dut-A# show system information 
 
===============================================================================
System Information
===============================================================================
System Name            : 7705:Dut-A
System Type            : 7705 SAR-8 v2
Chassis Topology       : Standalone 
System Version         : B-0.0.I346                                           
Crypto Module Version  : SRCM 3.0
System Contact         : Fred Information Technology
System Location        : Bldg.1-floor 2-Room 201
System Coordinates     : N 45 58 23, W 34 56 12
System Active Slot     : A                                                     
System Up Time         : 1 days, 02:03:17.62 (hr:min:sec)                      
 
SNMP Port              : 161                                                   
SNMP Engine ID         : 0000197f000000164d3c3910                              
SNMP Engine Boots      : 58                                                  
SNMP Max Message Size  : 1500                                                  
SNMP Admin State       : Enabled                                               
SNMP Oper State        : Enabled                                               
SNMP Index Boot Status : Not Persistent                                        
SNMP Sync State        : OK                                                    
 
Tel/Tel6/SSH/FTP Admin : Enabled/Disabled/Enabled/Enabled                     
Tel/Tel6/SSH/FTP Oper  : Up/Down/Up/Up                                       
 
BOF Source             : cf3:                                                  
Image Source           : primary                                               
Config Source          : primary                                               
Last Booted Config File: cf3:/config.cfg
Last Boot Cfg Version  : FRI APR 20 16:24:27 2007 UTC                          
Last Boot Config Header: # TiMOS-B-0.0.I346 both/i386 NOKIA SAR 7705
                         # Copyright (c) 2016 Nokia. # All rights
                         reserved. All use subject to applicable license
                         agreements. # Built on Tue Mar 11 01:43:47 EDT 2016 by
                         csabuild in /rel0.0/I346/panos/main # Generated TUE
                         MAR 11 20:00:37 2016 UTC
Last Boot Index Version: N/A                                                   
Last Boot Index Header : # TiMOS-B-0.0.I346 both/i386 NOKIA SAR 7705
                         # Copyright (c) 2016 Nokia. # All rights
                         reserved. All use subject to applicable license
                         agreements. # Built on Tue Mar 11 01:43:47 EDT 2016 by
                         csabuild in /rel0.0/I346/panos/main # Generated TUE
                         MAR 11 20:00:37 2016 UTC
Last Saved Config      : N/A                                                   
Time Last Saved        : N/A                                                   
Changes Since Last Save: Yes                                                   
User Last Modified     : admin
Time Last Modified     : 2016/03/25 10:03:09                                   
Max Cfg/BOF Backup Rev : 5                                                     
Cfg-OK Script          : N/A                                                   
Cfg-OK Script Status   : not used                                              
Cfg-Fail Script        : N/A                                                   
Cfg-Fail Script Status : not used                                              
 
Microwave S/W Package  : invalid
 
Management IP Addr     : 192.168.1.202/16                                    
Primary DNS Server     : 192.168.x.x
Secondary DNS Server   : N/A
Tertiary DNS Server    : N/A
DNS Domain             : domain.com
DNS Resolve Preference : ipv4-only                                         
BOF Static Routes      :                                                       
  To                   Next Hop            
  192.168.0.0/16       192.168.1.1       
ATM Location ID        : 01:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00       
ATM OAM Retry Up       : 2                                                     
ATM OAM Retry Down     : 4                                                     
ATM OAM Loopback Period: 10
   
ICMP Vendor Enhancement: Disabled
Eth QinQ untagged SAP  : False
===============================================================================
7705:Dut-A# 

When executing a post-boot configuration extension file, status messages are output to the console screen prior to the “Login” prompt.

The following is an example of a failed boot-up configuration that caused a boot-bad-exec file containing another error to be executed:

Attempting to exec configuration file:
’ftp://test:test@192.168.xx.xxx/./12.cfg’ ...
System Configuration
Log Configuration
MAJOR: CLI #1009 An error occurred while processing a CLI command -
File ftp://test:test@192.168.xx.xxx/./12.cfg, Line 195: Command "log" failed.
CRITICAL: CLI #1002 An error occurred while processing the configuration file.
The system configuration is missing or incomplete.
MAJOR: CLI #1008 The SNMP daemon is disabled.
If desired, enable SNMP with the ’config>system>snmp no shutdown’ command.
Attempting to exec configuration failure extension file:
’ftp://test:test@192.168.xx.xxx/./fail.cfg’ ...
Config fail extension
Enabling SNMP daemon
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-5.0.R3 both/hops Nokia 7705 SAR Copyright (c) 2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 18 12:45:00 EST 2018 by builder in /re8.0/b1/R3/panos/main

6.10.7. System Timing

If network timing is required for the synchronous interfaces in a 7705 SAR, a timing subsystem is used to provide a Stratum 3 quality clock to all synchronous interfaces within the system. The clock source is specified in the config>port>tdm>ds1 | e1> clock-source context.

This section describes the commands used to configure and control the timing subsystem.

CLI Syntax:
config>system>sync-if-timing
abort
begin
commit
external
input-interface
impedance {high-impedance | 50-ohm | 75-ohm}
type {2048khz-G703 | 5mhz | 10mhz}
output-interface
type {2048khz-G703 | 5mhz | 10mhz}
ref-order first second [third]
ref1
source-port port-id [adaptive]
no shutdown
ref2
source-port port-id [adaptive]
no shutdown
revert

6.10.7.1. Entering 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 you try to modify sync-if-timing parameters without entering begin first.

ALU-1>config>system>sync-if-timing>ref1# source-port 1/1/1
MINOR: CLI The sync-if-
timing must be in edit mode by calling begin before any changes can be made.
MINOR: CLI Unable to set source port for ref1 to 1/1/1.
ALU-1>config>system>sync-if-timing>ref1#

6.10.7.2. Configuring Timing References

The following example shows the command usage:

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:

ALU-1>config>system>sync-if-timing# info
----------------------------------------------
            ref-order ref2 ref1
            ref1
                source-port 1/1/1
                no shutdown
            exit
            ref2
                no shutdown
                source-port 1/1/2
            exit

6.10.7.3. Configuring IEEE 1588v2 PTP

Use the following CLI syntax to configure basic IEEE 1588v2 PTP parameters.

CLI Syntax:
config>system>ptp
clock clock-id [create]
clock-mda mda-id
clock-type {ordinary [master | slave] | boundary | transparent-e2e}
domain domain-value
dynamic-peers
priority1 priority-value
priority2 priority-value
profile ieee1588-20008
ptp-port port-id
anno-rx-timeout number-of-timeouts
log-anno-interval log-anno-interval
log-sync-interval log-sync-interval
peer peer-id ip-address {ip-address | ipv6-address}
[no] shutdown
unicast-negotiate
[no] shutdown
source-interface ip-if-name
config>system>sync-if-timing
ref1
source-ptp-clock clock-id
ref2
source-ptp-clock clock-id

The following example shows the command usage:

Example:
config>system# ptp clock 1 create
config>system>ptp>clock# clock-type ordinary slave
config>system>ptp>clock# source-interface ptp-loop
config>system>ptp>clock# clock-mda 1/2
config>system>ptp>clock# domain 0
config>system>ptp>clock# no dynamic-peers
config>system>ptp>clock# priority1 128
config>system>ptp>clock# priority2 128
config>system>ptp>clock# profile ieee1588-2008
config>system>ptp>clock# ptp-port 1
config>system>ptp>clock>ptp-port# anno-rx-timeout 3
config>system>ptp>clock>ptp-port# log-anno-interval 1
config>system>ptp>clock>ptp-port# log-sync-interval -6
config>system>ptp>clock>ptp-port# unicast-negotiate
config>system>ptp>clock>ptp-port# peer 1
config>system>ptp>clock>ptp-port>peer# description "Peer to Boundary Clock"
config>system>ptp>clock>ptp-port>peer# ip-address 10.222.222.10
config>system>ptp>clock>ptp-port>peer# exit
config>system>ptp>clock>ptp-port# peer 2
config>system>ptp>clock>ptp-port>peer# description ToGM
config>system>ptp>clock>ptp-port>peer# ip-address 192.168.2.10
config>system>ptp>clock>ptp-port>peer# exit
config>system>ptp>clock>ptp-port# no shutdown
config>system>ptp>clock>ptp-port# exit
config>system>ptp>clock# no shutdown
config>system>ptp>clock# exit
config>system>ptp# exit
config>system# sync-if-timing begin
config>system>sync-if-timing# ref1
config>system>sync-if-timing>ref1# source-ptp-clock 1
config>system>sync-if-timing>ref1# no shutdown
config>system>sync-if-timing>ref1# exit

The following display shows a basic IEEE 1588v2 PTP configuration:

ALU-1>config>system>ptp># info   
#--------------------------------------------------
echo "System IEEE 1588 PTP Configuration"
#--------------------------------------------------
    system
        ptp
            clock 1 create
                clock-type ordinary slave
                source-interface "ptp loop"
                clock-mda 1/2
                domain 0
                no dynamic-peers
                priority1 128
                priority2 128
                profile ieee1588-2008
                ptp-port 1
                    anno-rx-timeout 3
                    log-anno-interval 1
                    log-sync-interval -6
                    unicast-negotiate
                    peer 1
                        description "Peer to Boundary Clock"
                        ip-address 10.222.222.10
                    exit
                    peer 2
                        description "ToGM"
                        ip-address 192.168.2.10
                    exit
                    no shutdown
                exit
                no shutdown
            exit
        exit
    exit

6.10.7.4. Configuring QL Values for SSM

Use the following syntax to configure the quality level (QL) values for Synchronization Status Messaging (SSM).

CLI Syntax:
config>system>sync-if-timing
abort
begin
external
input-interface
impedance {high-impedance | 50-ohm | 75-ohm}
no shutdown
ql-override {prs | stu | st2 | tnc | st3e | st3 | smc | prc | ssu-a | ssu-b | sec | eec1 | eec2}
type {2048khz-G703 | 5mhz | 10mhz}
commit
bits
input
[no] shutdown
interface-type {ds1[{esf|sf}] | e1[{pcm30crc | pcm31crc}] | 2048khz-G703}
output
line-length {110|220|330|440|550|660}
[no] shutdown
ql-override {prs | stu | st2 | tnc | st3e | st3 | smc | prc | ssu-a | ssu-b | sec | eec1 | eec2}
ssm-bit sa-bit
[no] shutdown
ql-selection
ref-order first second [third]
ref1
ql-override {prs | stu | st2 | tnc | st3e | st3 | smc | prc | ssu-a | ssu-b | sec | eec1 | eec2}
source-port port-id adaptive
no shutdown
ref2
ql-override {prs | stu | st2 | tnc | st3e | st3 | smc | prc | ssu-a | ssu-b | sec | eec1 | eec2}
source-port port-id adaptive
no shutdown

The following example shows the command usage:

Example:
config>system# sync-if-timing
config>system>sync-if-timing# begin
config>system>sync-if-timing# external
config>system>sync-if-timing>external# input-interface
config>system>sync-if-timing>external>input-interface# impedance 50-Ohm
config>system>sync-if-timing>external>input-interface# no shutdown
config>system>sync-if-timing>external>input-interface# ql-override prs
config>system>sync-if-timing>external>input-interface# exit
config>system>sync-if-timing>external# exit
config>system>sync-if-timing# commit
config>system>sync-if-timing# bits
config>system>sync-if-timing>bits# interface-type 2048khz-G703
config>system>sync-if-timing>bits# ssm-bit 8
config>system>sync-if-timing>bits# output
config>system>sync-if-timing>bits>output# line-length 220
config>system>sync-if-timing>bits>output# no shutdown
config>system>sync-if-timing>bits>output# exit
config>system>sync-if-timing>bits# ql-override prs
config>system>sync-if-timing>bits# exit
config>system>sync-if-timing# ql-selection
config>system>sync-if-timing# ref1
config>system>sync-if-timing>ref1# shutdown
config>system>sync-if-timing>ref1# ql-override prs
config>system>sync-if-timing>ref1# exit
config>system>sync-if-timing# ref2
config>system>sync-if-timing>ref2# no shutdown
config>system>sync-if-timing>ref2# ql-override prs
config>system>sync-if-timing>ref2# exit
config>system>sync-if-timing# exit

The following display shows a basic SSM QL configuration for the 7705 SAR-8 Shelf V2:

ALU-1>config>system>sync-if-timing# info 
----------------------------------------------
ref-order external ref1 ref2
            ql-selection
            external
               input-interface 
                   no shutdown
                   impedance 50-Ohm
                   type 2048Khz-G703
                   ql-override prs
               exit
               output-interface
                   type 2048Khz-G703
               exit
            exit
            ref1
                no shutdown
                no source-port
                ql-override prs
            exit
            ref2
                no shutdown
                no source-port
                ql-override prs
            exit
            no revert
----------------------------------------------
*ALU-1>>config>system>sync-if-timing#

The following display shows a basic SSM QL configuration for the 7705 SAR-18:

ALU-1>config>system>sync-if-timing# info 
----------------------------------------------
ref-order external ref1 ref2
            ql-selection
            exit
            bits
               interface-type 2048Khz-G703
               ssm-bit 8
               ql-override prs
               output
                   line-length 220
                   no shutdown
               exit
            ref1
                no shutdown
                no source-port
                ql-override prs
            exit
            ref2
                no shutdown
                no source-port
                ql-override prs
            exit
            no revert
----------------------------------------------

6.10.7.5. Using the Revert Command

The revert command allows the clock to revert to a higher-priority reference if the current reference goes offline or becomes unstable. With revertive switching enabled, the highest-priority valid timing reference will be used. If a reference with a higher priority becomes valid, a reference switchover to that reference will be initiated. If a failure on the current reference occurs, the next highest reference takes over.

With non-revertive switching, the active reference will always remain selected while it is valid, even if a higher-priority reference becomes available. If this reference becomes invalid, a reference switchover to a valid reference with the highest priority will be initiated. When the failed reference becomes operational, it is eligible for selection.

CLI Syntax:
config>system>sync-if-timing
revert

6.10.7.6. Other Editing Commands

Other editing commands include:

  1. commit — saves changes made to the timing references during a session Modifications are not persistent across system boots unless this command is entered.
  2. abort — discards changes that have been made to the timing references during a session
CLI Syntax:
config>system>sync-if-timing
abort
commit

6.10.7.7. Forcing a Specific Reference

You can force the system synchronous timing output to use a specific reference.

Note:

The debug sync-if-timing force-reference command should only be used to test and debug problems. Once the system timing reference input has been forced, it will not revert to another reference unless explicitly reconfigured.

When the command is executed, the current system synchronous timing output is immediately referenced from the specified reference input. If the specified input is not available (shut down), or in a disqualified state, the timing output will enter a holdover state based on the previous input reference.

Debug configurations are not saved between reboots.

CLI Syntax:
debug>sync-if-timing
force-reference {external | ref1 | ref2}
Example:
debug>sync-if-timing# force-reference

6.11. Configuring System Monitoring Thresholds

6.11.1. 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 will be created to record the occurrence of the event. It can also specify whether an SNMP notification (trap) will be generated for the event. There are two notifications for threshold crossing events, a rising alarm and a falling alarm.

Creating an event entry in the RMON-MIB log table does not create a corresponding entry in the 7705 SAR event logs. However, when the event is set to trap, the generation of a rising alarm or falling alarm notification creates an entry in the 7705 SAR event logs and that is distributed to whatever 7705 SAR log destinations are configured: console, session, memory, file, syslog, or SNMP trap destination. The 7705 SAR 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.

The alarm command configures an entry in the RMON-MIB alarm table. The alarm command controls the monitoring and triggering of threshold crossing events. In order for notification or logging of a threshold crossing event to occur there must be at least one associated rmon event configured.

The agent periodically takes statistical sample values from the MIB variable specified for monitoring and compares them to thresholds that have been configured with the alarm command. The alarm command configures the MIB variable to be monitored, the polling period (interval), sampling type (absolute or delta value), and rising and falling threshold parameters. If a sample has crossed a threshold value, the associated ‘event’ is generated.

Preconfigured CLI threshold commands are available. Preconfigured commands hide some of the complexities of configuring RMON alarm and event commands and perform the same functions. In particular, the preconfigured commands do not require the user to know the SNMP object identifier to be sampled. The preconfigured threshold configurations include memory warnings, alarms, and compact flash usage warnings and alarms.

To create events, use the following CLI syntax:

CLI Syntax:
config>system
thresholds
cflash-cap-alarm cflash-id rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
cflash-cap-warn cflash-id rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
memory-use-alarm rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
memory-use-warn rising-threshold threshold [falling-threshold threshold] interval seconds [rmon-event-type] [startup-alarm alarm-type]
rmon
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]
event rmon-event-id [event-type] [description description-string] [owner owner-string]
Example:
config>system>thresholds# cflash-cap-warn cf3-B: rising-threshold 2000000 falling-threshold 1999900 interval 240 trap startup-alarm either
config>system>thresholds# memory-use-alarm rising-threshold 50000000 falling-threshold 45999999 interval 500 both startup-alarm either
config>system>thresholds# rmon
config>system>thresholds>rmon# event 5 both description "alarm testing" owner "Timos CLI"

The following example displays the command output:

A:ALU-49>config>system>thresholds# info
----------------------------------------------
            rmon
                event 5 description "alarm testing" owner "Timos CLI"
            exit
            cflash-cap-warn cf1-B: rising-threshold 2000000 falling-
             threshold 1999900 interval 240 trap
            memory-use-alarm rising-threshold 50000000 falling-threshold 45999999
             interval 500
----------------------------------------------
A:ALU-49>config>system>thresholds#

6.12. Configuring LLDP

Use the following syntax to configure LLDP:

CLI Syntax:
config>system>lldp
    message-fast-tx time
    message-fast-tx-init count
    notification-interval time
    reinit-delay time
    tx-credit-max count
    tx-hold-multiplier multiplier
    tx-interval interval
Example:
config>system# lldp
config>system>lldp# message-fast-tx 100
config>system>lldp# notification-interval 10
config>system>lldp# reinit-delay 5
config>system>lldp# tx-credit-max 20
config>system>lldp# tx-hold-multiplier 2
config>system>lldp# tx-interval 10

The following example shows the system LLDP configuration:

A:ALU-49>config>system>lldp# info
----------------------------------------------
tx-interval 10
tx-hold-multiplier 2
reinit-delay 5
notification-interval 10
tx-credit-max 20
message-fast-tx 100
----------------------------------------------
A:ALU-49>config>system>lldp#