The no form of this command places the entity into an administratively enabled state.
The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
Refer to the 7750 SR Services Guide for information about ATM QoS policies and ATM-related service parameters.
The retry values are configured on a system wide basis and are affective on the next period cycle of any ATM VC SAP using periodic-loopback, if changed. The timeout for receiving a loopback response from the remote peer and declaring the loopack failed is 1 second and is not configurable.
|
Values
|
file url: local-url | remote-url: 255 chars max
local-url: [cflash-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 addressescflash-id: cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:
|
|
Values
|
file url: local-url | remote-url: 255 chars max
local-url: [cflash-id/][ file-path] remote-url: [{ftp://} login:pswd@remote-locn/][file-path] remote-locn [ hostname | ipv4-address | [ ipv6- address] 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: cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:
|
Note that, if you are in chassis-mode d and configure an IOM type as iom2-20g and then downgrade to chassis-mode
a or
b (must specify
force keyword), a warning appears about the IOM downgrade. In this case, the IOM`s provisioned type will downgrade to iom-20g-b. Once this is done, the ASAP MDA cannot be configured.
If this is the desired behavior, for example, chassis-mode d is configured and IPv6 is running, you can then downgrade to chassis-mode
a or
b if you want to disable IPv6.
For chassis mode d, the default must be changed from the default mode
a which assumes the least available features. Mode
d enables the new feature sets available with newer generations of IOMs. Chassis mode
d supports the P2/Q2/T2-based IOMs products and the extensive queuing/policing/bandwidth. Mode
d assumes that the
iom3-xp is installed.
Note:
force command is not available for chassis-mode d.
a: This mode corresponds to scaling and feature set associated with iom-20g.
b: This mode corresponds to scaling and feature set associated with iom-20g-b.
c: This mode corresponds to scaling and feature set associated with iom2-20g.
d: This mode corresponds to scaling and feature set associated with iom3-xp.
This command creates a Common Language Location Identifier (CLLI) code string for the 7750 SR router. A CLLI code is an 11-character standardized geographic identifier that uniquely identifies geographic locations and certain functional categories of equipment unique to the telecommunications industry.
The no form of the command removes the CLLI code.
For example, assume the config-backup count is set to 5 and the configuration file is called
xyz.cfg. When a
save command is executed, the file
xyz.cfg is saved with a .1 extension. Each subsequent
config-backup command increments the numeric extension until the maximum count is reached.
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
CPM is performed for all configurations and their associated persistent index files.
The no form of the command returns the configuration to the default value.
The no form of the command reverts to default.
The no form of the command reverts to the default value.
This algorithm will be used in all cases where IP information in per-packet hashing is included (see LAG and ECMP Hashing in the Interfaces Guide). However, the Layer 4 information (TCP/UDP ports) will not be used in the following cases:
[no
] mc-enh-load-balancing
The no form of the command preserves the default behavior for per flow hashing of multicast traffic.
The no form of the command preserves the default behavior of VLL LAG service ID hashing.
This command is set at a system wide basis, however if certain IOMs do not support the new load-balancing algorithm, they will continue to use the default algorithm. By default, the IPv4 system IP address is used in the hash algorithm. When no IPv4 system IP address is configured, the IPv6 system IP address, when configured, is used in the hash algorithm.
The no form of the command resets the system wide algorithm to default.
The no form of the command reverts to the default value.
none — No system location is configured.
For example, system-name parameter ALA-1 for the name command configures the device name as ALA-1.
ABC>config>system# name "ALA-1"
ALA-1>config>system#
The no form of the command reverts to the default value.
When the file-url parameter is not specified, no CLI script file is executed.
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]
Use the no form of this command to remove an rmon-alarm-id from the configuration.
|
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 — Specifies that the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds.
|
The identifier of the the rmon>event that specifies the action to be taken when a rising threshold crossing event occurs.
If there is no corresponding ’event’ configured for the specified rmon-event-id, then no association exists and no action is taken.
If the ’rising-event rmon-event-id’ has a value of zero (0), no associated event exists.
The identifier of the rmon>event that specifies the action to be taken when a falling threshold crossing event occurs. If there is no corresponding event configured for the specified rmon-event-id, then no association exists and no action is taken. If the falling-event has a value of zero (0), no associated event exists.
alarm 3 variable-oid ifInOctets.184582144 interval 20 sample-type delta start-alarm either
rising-event 5 rising-threshold 10000 falling-event 5 falling-threshold 9000 owner "TiMOS
CLI"
cflash-cap-alarm cflash-id rising-threshold
threshold [falling-threshold
threshold] interval
seconds [rmon-event-type] [startup-alarm
alarm-type]
The no form of this command removes the configured compact flash threshold alarm.
cflash-cap-warn cflash-id rising-threshold
threshold [falling-threshold
threshold] interval
seconds [rmon-event-type] [startup-alarm
alarm-type]
The no form of the command removes the parameters from the configuration.
event rmon-event-id [event-type] [description
description-string] [owner
owner-string]
The event command configures an entry in the RMON-MIB event table. The event command controls the generation and notification of threshold crossing events configured with the alarm command. When a threshold crossing event is triggered, the rmon>event configuration optionally specifies if an entry in the RMON-MIB log table should be created to record the occurrence of the event. It may also specify that an SNMP notification (trap) should be generated for the event. The RMON-MIB defines two notifications for threshold crossing events: Rising Alarm and Falling Alarm.
Creating an event entry in the RMON-MIB log table does not create a corresponding entry in the TiMOS event logs. However, when the event-type is set to trap, the generation of a Rising Alarm or Falling Alarm notification creates an entry in the TiMOS event logs and that is distributed to whatever TiMOS log destinations are configured: CONSOLE, session, memory, file, syslog, or SNMP trap destination.
Use the no form of this command to remove an rmon-event-id from the configuration.
This does not create a TiMOS logger entry. The RMON-MIB log table entries can be viewed using the
show>system>thresholds CLI command.
The no form of this command removes the configured memory threshold warning.
The no form of this command removes the configured compact flash threshold warning.
memory-use-warn rising-threshold 500000 falling-threshold 400000 interval 800 rmon-event-type log start-alarm falling
|
Values
|
YYYY is the four-digit year MM is the two-digit month DD is the two-digit date
|
|
Values
|
hh is the two-digit hour in 24 hour format (00=midnight, 12=noon) mm is the two-digit minute
|
[no
] authentication-check
When authentication-check is enabled, NTP PDUs are authenticated on receipt. However, mismatches cause a counter to be increased, one counter for type and one for key-id, one for type, value mismatches. These counters are visible in a show command.
The no form of this command allows authentication mismatches to be accepted; the counters however are maintained.
The no form of the command removes the authentication key.
broadcast [router
router-name] {interface
ip-int-name} [key-id
key-id] [version
version] [ttl
ttl]
The no form of this command removes the address from the configuration.
routerSpecifies the router name used to transmit NTP packets. Base is the default. Select management to use the management port (Ethernet port on the
CPM).
broadcastclient [router
router-name] {interface
ip-int-name} [authenticate
]
The no form of this command removes the address from the configuration.
This command configures NTP the node to transmit multicast packets on the CPMCCM MGMT port. Broadcast and multicast messages can easily be spoofed; authentication is strongly recommended.
The no form of this command removes the multicast address from the configuration.
This command configures the node to receive multicast NTP messages on the CPM MGMT port. If multicastclient is not configured, received NTP multicast traffic will be ignored. Use the
show command to view the state of the configuration.
The no construct of this message removes the multicast client for the specified interface from the configuration.
peer {ip-address | ipv6-address} [key-id
key-id] [version
version] [prefer
]
The no form of the command removes the configured peer.
Specify the key-id that identifies the configured authentication key and authentication type used by this node to transmit NTP packets to an NTP peer. If an NTP packet is received by this node, the authentication key-id, type, and key value must be valid otherwise the packet will be rejected and an event/trap generated.
server {ip address | ipv6-address | ptp
}[key-id
key-id] [version
version] [prefer
]
The no form of the command removes the SNTP instance and configuration. SNTP does not need to be administratively disabled when removing the SNTP instance and configuration.
When this global parameter is configured then the ntp-broadcast parameter must be configured on selected interfaces on which NTP broadcasts are transmitted.
The no form of the command disables broadcast client mode.
server-address ip-address [version
version-number] [normal
| preferred
]
[no
] schedule
schedule-name [owner
owner-name]
The no form of the command removes the context from the configuration.
Using the weekday command as well as the
day-of-month command will cause the script to run twice. For example, consider that “today” is Monday January 1. If “Tuesday January 5” is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).
The no form of this command removes the specified day-of-month from the list.
This command is used concurrently with type periodic or
calendar. Using the type of
periodic, end-time determines at which interval the schedule will end. Using the type of
calendar, end-time determines on which date the schedule will end.
When no end-time is specified, the schedule runs forever.
hour {..hour-number [..hour-number]| all
}
The no form of this command removes the specified hour from the configuration.
minute {minute-number [..minute-number]| all
}
The no form of this command removes the specified minute from the configuration.
month {month-number [..month-number]|month-name [..month-name]| all
}
The no form of this command removes the specified month from the configuration.
|
Values
|
january, february, march, april, may, june, july, august, september, october, november, december (maximum 12 month names).
|
|
Values
|
periodic — Specifies a schedule which runs at a given interval. interval must be specified for this feature to run successfully. calendar — Specifies a schedule which runs based on a calendar. weekday, month, day-of-month, hour and minute must be specified for this feature to run successfully. oneshot — Specifies a schedule which runs one time only. As soon as the first event specified in these parameters takes place and the associated event occurs, the schedule enters a shutdown state. month, weekday, day-of-month, hour and minute must be specified for this feature to run successfully.
|
weekday {weekday-number [..weekday-number]|day-name [..day-name]| all
}
Using the weekday command as well as the
day-of month command will cause the script to run twice. For example, consider that “today” is Monday January 1. If “Tuesday January 5” is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).
The no form of this command removes the specified weekday from the configuration.
The no form of the command removes the
name from the configuration.
absolute start
start-absolute-time end
end-absolute-time
The no form of the command removes the absolute time range from the configuration.
The no form of the command removes the daily time parameters from the configuration.
The no form of the command removes the weekday parameters from the configuration.
The no form of the command removes the weekend parameters from the configuration.
The no form of the command removes the weekly parameters from the configuration.
day sun, mon, tue, wed, thu, fri, sat
sunday, monday, tuesday, wednesday, thursday, friday,
saturday
hh 0 — 23
mm 0 — 59
|
Values
|
day sun, mon, tue, wed, thu, fri, sat
sunday, monday, tuesday, wednesday, thursday, friday,
saturday
hh 0 — 24
mm 0 — 59
|
[no
] tod-suite
tod-suite name create
filter ip ip-filter-id [time-range
time-range-name] [priority
priority]
filter ipv6 ipv6-filter-id [time-range
time-range-name] [priority
priority]
filter mac mac-filter-id [time-range
time-range-name] [priority
priority]
no ip ip-filter-id [time-range
time-range-name]
qos policy-id [time-range
time-range-name] [priority
priority]
no qos
policy-id [time-range
time-range-name] [
[no
] scheduler-policy
scheduler-policy-name [time-range
time-range-name] [priority
priority]
The no form of the command removes the file location from the configuration. Scripts will not execute if there is no result location defined.
Specifies the location to send CLI output from script runs. The file-url is a location, directory, and filename prefix to which a data and timestamp suffix is added when the results files are created during a script run, as follows:
file-url_YYYYMMDD-hhmmss.uuuuuu.out
where: YYYYMMDD — date
hhmmss — hours, minutes, and seconds
uuuuuu — microseconds (padded to 6 characters with leading zeros)
local-url — [
cflash-id/] [
file-path]
200 chars max, including
cflash-id
directory length 99 characters max each
remote url — [{ftp:// | tftp://}
login:
password@
remote-location/][
file-path]
255 characters max
directory length 99 characters max each
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 characters max, for link local addresses
cflash-id — cf1: | cf1-A: | cf1-B: | cf2: | cf2-A: | cf2-B: | cf3: | cf3-A: | cf3-B:
script script-name [owner
script-owner]
The no form of the command removes the script.
The no form of the command removes the location.
local-url — [
cflash-id/] [
file-path]
200 chars max, including
cflash-id
directory length 99 characters max each
remote url — [{ftp:// | tftp://}
login:
password@
remote-location/][
file-path]
255 characters max
directory length 99 characters max each
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 characters max, for link local addresses
cflash-id — cf1: | cf1-A: | cf1-B: | cf2: | cf2-A: | cf2-B: | cf3: | cf3-A: | cf3-B:
[no
] dst-zone
[std-zone-name | non-std-zone-name]
If the time zone configured is listed in Table 22, “System-defined Time Zones,” , then the starting and ending parameters and offset do not need to be configured with this command unless it is necessary to override the system defaults. The command returns an error if the start and ending dates and times are not available either in
Table 22 on or entered as optional parameters in this command.
The no form of the command removes a configured summer (daylight savings) time entry.
end {end-week} {end-day} {end-month} [hours-minutes]
|
Values
|
january, february, march, april, may, june, july, august, september, october, november, december}
|
start {start-week} {start-day} {start-month} [hours-minutes]
|
Values
|
january, february, march, april, may, june, july, august, september, october, november, december
|
zone [std-zone-name | non-std-zone-name] [hh [:mm]]
SR OS supports system-defined and user-defined time zones. The system-defined time zones are listed in
Table 22, “System-defined Time Zones,” .
The no form of the command reverts to the default of Coordinated Universal Time (UTC). If the time zone in use was a user-defined time zone, the time zone will be deleted. If a
dst-zone command has been configured that references the zone, the summer commands must be deleted before the zone can be reset to UTC.
zone utc - The time zone is set for Coordinated Universal Time (UTC).
|
Values
|
A user-defined value can be up to 4 characters or one of the following values:
GMT, BST, IST, WET, WEST, CET, CEST, EET, EEST, MSK, MSD, AST, ADT, EST, EDT, ET, CST, CDT, CT, MST, MDT, MT, PST, PDT, PT, HST, AKST, AKDT, WAST, CAST, EAST
|
The bits command subtree is only available on the7750 SR-7, 7750 SR-12, 7750 Sr-12e, and 7750 SR-c4.
interface-type {ds1
[{esf
| sf
}] | e1
[{pcm30crc
| pcm31crc
}] | 2048khz-g703
}
The no form of the command reverts to the default configuration.
The no form of the command reverts to the default configuration
This command provides a context to enable or disable the external BITS timing reference inputs to the SR/ESS router. In redundant systems with BITS ports, there are two possible BITS-in interfaces, one for each CPM. In the 7750 SR-c4 system, there are two bits ports on the CFM. They are configured together, but they are displayed separately in the show command.
This command provides a context to configure and enable or disable the external BITS timing reference output to the SR/ESS router. On redundant systems, there are two possible BITS-out interfaces, one for each CPM. On the 7750 SR-c4 system, there are two possible BITS-out interfaces on the chassis front panel. They are configured together, but they are displayed separately in the show command.
source {line-ref
| internal-clock
}
This command configures the values used to identity the source of the BITS (Building Integrated Timing Supply) output. This is either the signal recovered directly from ref1, ref2 or ptp, or it is the output of the node’s central clock. The directly recovered signal would be used when the BITS output signal is feeding into an external stand alone timing distribution device (BITS/SASE). The specific directly recovered signal used is the best of the available signals based of the QL and/or the ref-order. The central clock output would be used when no BITS/SASE device is present and the BITS output signal is used to monitor the quality of the recovered clock within the system.
ql-override {prs
|stu
|st2
|tnc
|st3e
|st3
|eec1
|sec
|prc
|ssu-a
|ssu
-b
|eec2
}
The synchronous equipment timing subsystem can lock to different timing reference inputs, those specified in the ref1, ref2, bits and
ptp command configuration. This command organizes the priority order of the timing references.
If a reference source is disabled, then the clock from the next reference source as defined by ref-order is used. If all reference sources are disabled, then clocking is derived from a local oscillator.
Note that if a sync-if-timing reference is linked to a source port that is operationally down, the port is no longer qualified as a valid reference.
The no form of the command resets the reference order to the default values.
The bits option is not supported on the 7750 SR-c12 chassis.
The timing reference for
ref1 must be specified for the following chassis slots:
The timing reference for ref2 must be specified for the following chassis slots.
This command configures the source port for timing reference ref1 or
ref2. If the port is unavailable or the link is down, then the reference sources are re-evaluated according to the reference order configured in the
ref-order command.
The timing reference for ref1 and
ref2 must be specified for ports in the following chassis slots:
|
Values
|
file url: local-url | remote-url: 255 chars max
local-url: [cflash-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 | [ 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 255 chars max, directory length 99 chars max each cflash-id: cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:
|
disconnect [address
ip-address | username
user-name | console
| telnet
| ftp
| ssh
| netconf
]
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]Dusername
user-name
Specifying the detail option displays all default and non-default configuration parameters.
reboot [active
| standby
| upgrade] [hold] [now
]
This command reboots the router or one CPM and can also be used to force an upgrade of the system boot ROMs.
ALA-1>admin# reboot
Are you sure you want to reboot (y/n)?
When the upgrade keyword is specified, a chassis flag is set for the BOOT Loader (boot.ldr) and on the subsequent boot of the SR OS on the chassis, firmware images on
CPMs or IOMs will be upgraded automatically.
Any CPMs that are installed in the chassis will be upgraded automatically. For example, if a card is inserted with down revision firmware as a result of a card hot swap with the latest OS version running, the firmware on the card will be automatically upgraded before the card is brought online.
save [file-url] [detail
] [index]
A:ALA-1>admin# save ftp://test:test@192.168.x.xx/./100.cfg
Saving configuration .........Completed.
An admin save operation initiated by a user is aborted if another user initiates another
admin save from another session.
|
Values
|
file url: local-url | remote-url: 255 chars max
local-url: [cflash-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 | [ 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 255 chars max, directory length 99 chars max each cflash-id: cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:
|
NOTE: This command should only be used with authorized direction from the Alcatel-Lucent Technical Assistance Center (TAC).
NOTE: This command should only be used with authorized direction from the Alcatel-Lucent Technical Assistance Center (TAC).
|
Values
|
file url: local-url | remote-url: 255 chars max
local-url: [cflash-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 | [ 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 255 chars max, directory length 99 chars max each cflash-id: cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:
|
The ts-location command is used (along with an automatic system generated file name) when no
file-url parameter is provided for the
admin tech-support command. If
no ts-location is defined then the operator must provide a file-url with the
admin tech-support command itself.
view {bootup-cfg|active-cfg|candidate-cfg|latest-rb|
checkpoint-id|rescue
}
This command configures NAT port forwarding persistence parameters.
In the subscriber management context, the location specifies the flash device on a CPM card where the data for handling subscriber management persistency is stored.
The no form of this command returns the system to the default. If there is a change in file location while persistence is running, a new file will be written on the new flash, and then the old file will be removed.
The no form of the command reverts to the default configuration. The default value is dependent upon the configured profile, as detailed below.
Note: In order to minimize BMCA driven reconfigurations, the IEEE recommends that the announce-interval should be consistent across the entire 1588 network.
The no form of the command reverts to the default configuration.
The no form of the command reverts to the default configuration.
profile {g8265dot1-2010
| ieee1588-2008 | g8275dot1-2014
}
When you change the profile, the domain changes to the default value for the new profile. The clock-type is restricted based on the profile. If the profile is ieee1588-2008 then the clock-type is not restricted. If the profile is g8265dot1-2010 then the clock type may only be ordinary slave or ordinary master; boundary clock is not allowed. If the profile is g8275dot1-2014 then the clock type may only be boundary clock; ordinary slave and ordinary master is not allowed.
|
•
|
log-anno-interval set for the clock
|
The no form of the command deletes the specified peer.
address {01:1b:19:00:00:00
|01:80:c2:00:00:0e
}
The no form of this command sets the address to the default address.
The log-sync-interval cannot be changed unless the peer is shutdown.
For g8275dot1-2014, this parameter sets the value of the localPriority associated with the Announce messages received from the external clocks (
ptp>peer or
ptp>port), or the local clock (
PTP). See G.8275.1 for detailed information.
The revert option allows the administrator to control when to revert back to the management Ethernet port of the primary CPM once it comes up again.
The no form of the command disables redundancy, so that connectivity to the active CPM is lost if its Ethernet port goes down.
In the admin>redundancy context, this command performs a manually triggered standby CPM synchronization. When the standby CPM takes over operation following a failure or reset of the active CPM, it is important to ensure that the active and standby CPM have identical operational parameters. This includes the saved configuration, CPM and IOM images.
The no form of the command removes the parameter from the configuration.
This command forces a switchover to the standby CPM card. The primary
CPM reloads its software image and becomes the secondary
CPM.
The no form of the command reverts the default.
config>redundancy>bgp-multi-homing
|
•
|
If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.
|
The no form of the command reverts to default value.
This command performs a synrchonization of the standby CPMs images and/or config files to the active
CPM. Either the
boot-env or
config parameter must be specified.
In the
config>redundancy context, this command performs an automatically triggered standby
CPM synchronization. When the standby
CPM takes over operation following a failure or reset of the active
CPM, it is important to ensure that the active and standby
CPMs have identical operational parameters. This includes the saved configuration,
CPM and IOM images.
The active CPM ensures that the active configuration is maintained on the standby
CPM. 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.
This command performs a synrchonization of the standby CPM’s images and/or config files to the active
CPM. Either the
boot-env or
config parameter must be specified.
In the admin>redundancy context, this command performs a manually triggered standby
CPM synchronization. When the standby
CPM takes over operation following a failure or reset of the active
CPM, it is important to ensure that the active and standby
CPM have identical operational parameters. This includes the saved configuration,
CPM and IOM images.
The active CPM ensures that the active configuration is maintained on the standby
CPM. 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.
port [port-id | lag-id] [sync-tag
sync-tag]
Use the mcs-peer command in the python-policy to enable syncing for a specific python-policy.
range encap-range sync-tag
sync-tag
|
Values
|
Dot1Q start-vlan- end-vlan
QinQ Q1. start-vlan-Q1. end-vlan
|
The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.
The no form of this command disables BFD.
The no form of this command sets the interval to default.
The no form of this command sets the multiplier to default value
The no form of this command sets the interval to default value
The no form of this command will disable the passive mode behavior.
The no form of this command sets the system priority to default
The no form of this command administratively disables multi-chassis LAG. MC-LAG can only be issued only when mc-lag is shutdown.
The no form of this command sets this parameter to default value.
The no form of this command sets the interval to default value
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority source-bmac-lsb
use-lacp-key
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority source-bmac-lsb
MAC-Lsb
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority
lag lag-id [remote-lag
remote-lag-id]
This command defines a LAG which is forming a redundant-pair for MC-LAG with a LAG configured on the given peer. The same LAG group can be defined only in the scope of 1 peer.
The same lacp-key,
system-id, and
system-priority must be configured on both nodes of the redundant pair in order to MC-LAG to become operational. In order MC-LAG to become operational, all parameters (
lacp-key,
system-id,
system-priority) must be configured the same on both nodes of the same redundant pair.
The partner system (the system connected to all links forming MC-LAG) will consider all ports using the same lacp-key,
system-id,
system-priority as the part of the same LAG. In order to achieve this in MC operation, both redundant-pair nodes have to be configured with the same values. In case of the mismatch, MC-LAG is kept operationally down.
The LAG identifier, expressed as a decimal integer. Specifying the lag-id allows the mismatch between lag-id on redundant-pair. If no
lag-id is specified it is assumed that neighbor system uses the same
lag-id as a part of the given MC-LAG. If no matching MC-LAG group can be found between neighbor systems, the individual LAGs will operate as usual (no MC-LAG operation is established.).
bfd-enable [service
service-id] interface
interface-name
The no form of the command removes the service-id from the IBC configuration.
|
Values
|
nearest-bridge — Specifies to use the nearest bridge. nearest-non-tpmr — Specifies to use the nearest non-Two-Port MAC Relay (TPMR) . nearest-customer — Specifies to use the nearest customer.
|
The no form of the command disables LLDP notifications.
tx-tlvs [port-desc
] [sys-name
] [sys-desc
] [sys-cap
]
The no form of the command resets the value to the default.
