2.20. Configuration Command Reference

2.20.1. Command Hierarchies

2.20.1.1. Card Commands

config
[no] card slot-number
card-type card-type [level card-level]
— no card-type
[no] fail-on-error
[no] named-pool-mode [now]
[no] shutdown

2.20.1.2. MCM Commands

config
[no] card slot-number
[no] mcm mcm-slot
mcm-type mcm-type
— no mcm-type
[no] shutdown

2.20.1.3. MDA Commands

config
[no] card slot-number
[no] mda mda-slot
access
egress
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
clock-mode adaptive
clock-mode differential [timestamp-freq {19440 | 77760 | 103680}]
egress
threshold xpl-errors
window minutes
[no] fail-on-error
threshold threshold
window window
mda-type mda-type [level mda-level]
— no mda-type
egress
named-pool-policy policy-name
named-pool-policy policy-name
egress
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
queue-policy name
[no] shutdown
[no] sync-e
[no] shutdown

2.20.1.4. Power Commands

config
— system
— power-management
mode [none | basic | advanced]
[no] pcm pcm-slot [chassis chassis-id]
pcm-type peq-type
— no pcm-type
[no] peq peq-slot [chassis chassis-id]
input-power-mode amperage
peq-type peq-type
— no peq-type
[no] shutdown
power-safety-alert wattage
power-safety-level percent

2.20.1.5. Virtual Scheduler Commands

config
[no] card slot-number
— virtual-scheduler-adjustment
internal-scheduler-weight-mode {default | force-equal | offered-load | capped-offered-load}
rate-calc-min-int [fast-queue percent-of-default] [slow-queue percent-of-default]
sched-run-min-int percent-of-default
slow-queue-threshold kilobits-per-second
task-scheduling-int percent-of-default

2.20.1.6. Forwarding Plane (FP) Commands

config
[no] card slot-number
fp [fp-number]
egress
hs-fixed-high-thresh-delta size-in-bytes
buffer-allocation min percentage max percentage
resv-cbs min percentage max percentage
— no resv-cbs
[no] shutdown
slope-policy slope-policy-name
hi-bw-mcast-src [alarm] [group group-id] [default-paths-only]
access
queue-group queue-group-name instance instance-id [create]
— no queue-group queue-group-name instance instance-id
accounting-policy acct-policy-id
[no] collect-stats
description description-string
max-rate {rate | max}
min-thresh-separation size [bytes | kilobytes]
[no] priority level
mbs-contribution [bytes | kilobytes]
policer-control-policy policer-control-policy-name
policer policer-id [create]
— no policer policer-id
cbs {size [bytes | kilobytes] | default}
— no cbs
mbs {size [bytes | kilobytes] | default}
— no mbs
packet-byte-offset {add add-bytes | subtract sub-bytes}
rate {rate | max} [cir {max | rate}]
— no rate
stat-mode stat-mode
— no stat-mode
bandwidth-policy policy-name
[no] shutdown
— network
queue-group queue-group-name instance instance-id [create]
— no queue-group queue-group-name instance instance-id
accounting-policy acct-policy-id
[no] collect-stats
description description-string
max-rate {rate | max}
min-thresh-separation size [bytes | kilobytes]
[no] priority level
mbs-contribution size [bytes | kilobytes]
policer-control-policy policer-control-policy-name
policer policer-id [create]
— no policer policer-id
cbs {size [bytes | kilobytes] | default}
— no cbs
mbs {size [bytes | kilobytes] | default}
— no mbs
packet-byte-offset {add bytes | subtract bytes}
rate {rate | max} [cir {max | rate}]
— no rate
stat-mode stat-mode
— no stat-mode

2.20.1.7. Port Configuration Commands

config
[no] port {port-id | bundle-id | bpgrp-id | aps-id | connector-port-id}
access
egress
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
breakout breakout
— no breakout
[no] ddm-events
description long-description-string
dwdm
[no] report-alarms [ild] [tmp] [mth] [mtl] [los] [lop] [com]
channel channel
channel channel
compatibility mode
cpr-window-size window-size
dispersion dispersion
mode {automatic | manual}
[no] report-alarms [modflt] [mod] [netrx] [nettx] [hosttx]
rx-los-reaction {squelch}
rx-los-thresh threshold
sweep start dispersion-start end dispersion-end
target-power power
[no] rxdtv-adjust
tdcm
channel channel
dispersion dispersion
mode {automatic | manual}
[no] report-alarms [nrdy] [mth] [mtl] [unlck] [tlim] [einv] [com]
sweep start dispersion-start end dispersion-end
encode key1 wave-key key2 wave-key
— no encode
[no] power-control
target-power dBm
[no] report-alarm [encode-fail] [encode-degrade] [power-fail] [power-degrade] [power-high] [power-low] [missing]
egr-weight access access-weight network network-weight
— no egr-weight
ing-weight access access-weight network network-weight
— no ing-weight
egr-percentage-of-rate egr-rate-percentage
ing-percentage-of-rate ing-rate-percentage
egress
named-pool-policy policy-name
named-pool-policy policy-name
egress
[no] pool [name]
amber-alarm-threshold percentage
red-alarm-threshold percentage
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
— no resv-cbs
slope-policy name
[no] otu
[no] async-mapping
fec {g709 | enhanced}
— no fec
otu2-lan-data-rate {11.049 | 11.096}
pm-tti
expected auto-generated
expected bytes byte-string [byte-string ... (up to 64 byte-strings max, 64 bytes max)]
expected string identifier
expected use-rx
mismatch-reaction {squelch-rx}
tx auto-generated
tx bytes byte-string [byte-string ...(up to 64 byte-strings max, 64 bytes max)]]
tx string identifier
— no tx
expected byte
expected auto
mismatch-reaction {squelch-rx}
tx byte
tx auto
[no] psi-tti
expected auto-generated
expected bytes byte-string [byte-string...(up to 64 byte-strings max, 255 bytes max)]]
expected string identifier
expected use-rx
mismatch-reaction {squelch-rx}
tx auto-generated
tx bytes byte-string [byte-string...(up to 64 byte-strings max, 255 bytes max)]
tx string identifier
— no tx
[no] report-alarms [loc] [los] [lof] [lom] [otu-ais] [otu-ber-sf] [otu-ber-sd] [otu-bdi] [otu-tim] [otu-iae] [otu-biae] [fec-sf] [fec-sd] [fec-fail] [fec-uncorr] [odu-ais] [odu-oci] [odu-lck] [odu-bdi] [odu-tim] [opu-tim] [opu-plm]
sf-sd-method {bip8 | fec}
sf-threshold threshold [coefficient coefficient]
sf-threshold-clear threshold [coefficient coefficient]
sm-tti
expected auto-generated
expected bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]
expected string identifier
expected use-rx
mismatch-reaction {squelch-rx}
tx auto-generated
tx bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]
tx string identifier
— no tx
[no] shutdown

2.20.1.8. Port XC Commands

config
pxc pxc-id [create]
— no pxc pxc-id
description description-string
port port-id
— no port
[no] shutdown
[no] port

2.20.1.9. Forwarding Path Extension (FPE) Commands

config
fpe fpe-id [create]
— no fpe fpe-id
description description-string
path xc-a lag-id xc-b lag-id
path pxc pxc-id
— no path
[no] pw-port
vxlan-termination [router router-name]
vxlan-termination service-name service-name
sdp-id-range from id to id

2.20.1.10. Port APS Commands

config
[no] port {aps-id}
aps
advertise-interval advertise-interval
hold-time hold-time
— no hold-time
hold-time-aps [lsignal-failure sf-time] [lsignal-degrade sd-time]
[no] mode-annexb
neighbor ip-address
— no neighbor
protect-circuit port-id
rdi-alarms [suppress | circuit]
revert-time minutes
— no revert-time
switching-mode {bi-directional | uni-directional | uni-1plus1}
working-circuit port-id [number number]
— no working-circuit [number number]
wtr-annexb minutes

2.20.1.11. Ethernet Commands

config
[no] port {port-id}
accounting-policy policy-id
autonegotiate [limited]
[no] collect-stats
sd-threshold threshold [multiplier multiplier]
sf-threshold threshold [multiplier multiplier]
window-size seconds
half-life half-life max-suppress-time max-time
[no] shutdown
suppress-threshold suppress-penalties reuse-threshold reuse-penalties
dot1q-etype value
dot1x
[no] macsec
ca-name ca-name
— no ca-name
[no] exclude-protocol {protocol-name}
max-peer max-peer
— no max-peer
[no] shutdown
max-auth-req max-auth-request
port-control {auto | force-auth | force-unauth}
quiet-period seconds
radius-plcy name
re-auth-period seconds
server-timeout seconds
supplicant-timeout seconds
transmit-period seconds
— no tunneling
down-on-internal-error [tx-disable]
keep-alive timer
— no keep-alive
retry-timeout timer
[no] shutdown
duplex {full | half}
hold-time time-value
— no hold-time
sd-threshold errored-frames
sf-threshold errored-frames
[no] shutdown
window deciseconds
sd-threshold errored-frames
sf-threshold errored-frames
[no] shutdown
window packets
sd-threshold errored-seconds
sf-threshold errored-seconds
[no] shutdown
window deciseconds
sd-threshold errored-symbols
sf-threshold errored-symbols
[no] shutdown
window deciseconds
[no] dying-gasp
local-port-action {log-only | out-of-service}
[no] shutdown
mode {active | passive}
critical-event local-port-action {log-only | out-of-service}
dying-gasp local-port-action {log-only | out-of-service}
event-notification local-port-action {log-only | out-of-service}
link-fault local-port-action {log-only |out-of-service}
[no] shutdown
[no] transmit-interval interval [multiplier multiplier]
trigger-fault {dying-gasp | critical-event}
[no] tunneling
egress
[no] exp-secondary-shaper secondary-shaper-name [create]
high-burst-increase size [bytes | kilobytes]
low-burst-limit size [bytes | kilobytes]
class class-number rate rate [monitor-threshold size-in-kbytes] [burst-limit size] [bytes | kilobytes]
— no class class-number
rate rate [monitor-threshold size-in-bytes]
— no rate
hs-port-pool-policy policy-name
group group-id rate rate
— no group group-id
max-rate rate
— no max-rate
scheduling-class class rate rate
scheduling-class class weight weight-in-group
— no scheduling-class class
hs-scheduler-policy policy-name
hs-secondary-shaper secondary-shaper-name [create]
— no hs-secondary-shaper secondary-shaper-name
[no] aggregate
rate rate
— no rate
[no] class class-number
rate rate
— no rate
description description-string
egress-rate sub-rate
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
elmi
mode {none | uni-n}
n393 [value]
— no n393
t391 [value]
— no t391
t392 [value]
— no t392
encap-type {dot1q | null | qinq}
— no encap-type
[no] mep mep-id domain md-index association ma-index [vlan vlan-id]
[no] ais-enable
client-meg-level [level [level]]
interval {1 | 60}
— no interval
low-priority-defect {allDef | macRemErrXcon}
priority priority-value
— no priority
[no] ccm-enable
ccm-ltm-priority priority
ccm-padding-size ccm-padding
ccm-tlv-ignore [port-status] [interface-status]
[no] csf-enable
multiplier multiplier-value
— no multiplier
description description-string
eth-bn
[no] receive
rx-update-pacing seconds
bit-error-threshold bit-errors
test-pattern {all-zeros | all-ones} [crc-enable]
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
hold-time {[up hold-time-up] [down hold-time-down] [seconds | centiseconds]}
— no hold-time
group group-id rate rate
— no group group-id
max-rate rate
— no max-rate
scheduling-class class rate rate
scheduling-class class weight weight-in-group
— no scheduling-class class
ingress-rate ingress-rate
[no] lacp-tunnel
lldp
dest-mac {nearest-bridge | nearest-non-tpmr | nearest-customer}
admin-status {rx | tx | tx-rx | disabled}
[no] notification
port-id-subtype {tx-if-alias | tx-if-name | tx-local}
tx-mgmt-address [system] [system-ipv6]
tx-tlvs [port-desc] [sys-name] [sys-desc] [sys-cap]
— no tx-tlvs
mac ieee-address
— no mac
min-frame-length byte-length
mode {access | network | hybrid}
— no mode
[no] mon-port-sch
mtu mtu-bytes
— no mtu
pbb-etype [ethertype-value]
— no pbb-etype
ptp-asymmetry nanoseconds
qinq-etype qinq-etype-value
— no qinq-etype
[no] report-alarm [signal-fail] [remote] [local] [no-frame-lock] [high-ber] [no-block-lock] [no-am-lock] [duplicate-lane]
rs-fec-mode rs-fec-mode
— no rs-fec-mode
[no] sflow
[no] single-fiber
speed {10 | 100 | 1000 | 10000 | 25000 | 40000 | 50000 | 100000}
ssm
code-type {sonet | sdh}
— no code-type
[no] shutdown
[no] tx-dus
sd-threshold threshold [multiplier multiplier]
sf-threshold threshold [multiplier multiplier]
[no] shutdown
window-size seconds
xgig {lan | wan}
config
— system
— ethernet
— efm-oam

2.20.1.11.1. Ethernet Access and Network Commands

config>port>ethernet
access
bandwidth bandwidth
— no bandwidth
booking-factor factor
egress
[no] queue-group queue-group-name [create] [instance instance-id]
accounting-policy acct-policy-id
[no] agg-rate
rate kilobits-per-second
— no rate
[no] collect-stats
description description-string
host-match destination-string [create]
— no host-match destination-string
[no] hs-turbo
packet-byte-offset {add add-bytes | subtract sub-bytes}
queue queue-id [create]
— no queue
mbs {[0 to2625] kilobytes | [0 to 2688000] bytes | default}
— no mbs
rate pir-rate
— no rate
slope-policy hsmda-slope-policy-name
— no slope-policy
wrr-weight weight
— no wrr-weight
secondary-shaper secondary-shaper-name
wrr-policy wrr-policy-name
queue queue-id [create]
— no queue queue-id
adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}]
burst-limit {default | size [bytes | kilobytes]}
cbs size-in-kbytes
— no cbs
low
mbs {size [bytes | kilobytes] | default}
— no mbs
[no] monitor-depth
parent [weight weight] [cir-weight cir-weight]
— no parent
percent-rate pir-percent [cir cir-percent]
rate pir-rate [cir cir-rate]
— no rate
scheduler scheduler-name [create]
— no scheduler scheduler-name
parent {[weight weight] [cir-weight cir-weight]}
— no parent
rate pir-rate [cir cir-rate]
— no rate
scheduler-policy scheduler-policy-name
vport name [create]
— no vport name
[no] agg-rate
rate kilobits-per-second
— no rate
description description-string
host-match dest description-string [create]
— no host-match dest destination-string
[no] mon-port-sch
port-scheduler-policy port-scheduler-policy-name
scheduler-policy scheduler-policy-name
[no] queue-group queue-group-name [create]
accounting-policy acct-policy-id
[no] collect-stats
description description-string
queue queue-id [create]
— no queue queue-id
adaptation-rule [pir adaptation-rule] [cir {max | min | closest}]
cbs size-in-kbytes
— no cbs
low
mbs {size [bytes | kilobytes] | default}
— no mbs
[no] monitor-depth
rate pir-rate [cir cir-rate]
— no rate
scheduler scheduler-name [create]
— no scheduler scheduler-name
parent {[weight weight] [cir-weight cir-weight]}
— no parent
rate pir-rate [cir cir-rate]
— no rate
scheduler-policy scheduler-policy-name
accounting-policy policy-id
[no] collect-stats
egress
[no] queue-group queue-group-name [instance instance id] [create]
accounting-policy acct-policy-id
— no agg-rate
rate kilobits-per-second
— no rate
[no] collect-stats
description description-string
[no] hs-turbo
policer-control-policy policy-name
queue queue-id [create]
— no queue queue-id
adaptation-rule [pir adaptation-rule] [cir {max | min | closest}]
cbs size-in-kbytes
— no cbs
low
mbs {size [bytes | kilobytes] | default}
— no mbs
[no] monitor-depth
percent-rate pir-percent [cir cir-percent]
rate pir-rate [cir cir-rate]
— no rate
parent scheduler-policy-name
— no parent
scheduler-policy scheduler-policy-name
queue-policy name

2.20.1.12. Interface Group Handler Commands

config
[no] member port-id
[no] shutdown
threshold num-members
— no threshold

2.20.1.13. Multilink Bundle Commands

config
[no] port {bundle-id}
fragment-threshold fragment-threshold
fragment-threshold unlimited
ima
atm
cell-format {uni | nni}
min-vp-vpi value
link-delay {activate | deactivate} milli-seconds
— no link-delay {activate | deactivate}
max-bandwidth number-links
[no] shutdown
test-link port-id
— no test-link
test-pattern pattern
version IMA-version
— no version
[no] member port-id
minimum-links minimum-links
mlfr
ack-timeout timer
egress
qos-profile profile-id
— no qos-profile
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
hello-interval timer
identifier frf16-identifier
— no identifier
ingress
qos-profile profile-id
— no qos-profile
retry-limit count
mlppp
egress
qos-profile profile-id
endpoint-discriminator class {ip-address | global-mac-address |null} [discriminator-id discriminator-id]
qos-profile profile-id
[no] magic-number
multiclass count
— no multiclass
mrru mrru
— no mrru
[no] protect-bundle bundle-id
red-differential-delay red-diff-delay [down]
[no] working-bundle bundle-id
yellow-differential-delay yellow-diff-delay

2.20.1.14. SONET-SDH Commands

config
[no] port {port-id}
clock-source {loop-timed | node-timed}
framing {sonet | sdh}
group sonet-sdh-index payload {tu3 | vt2 | vt15}
hold-time {[up hold-time-up] [down hold-time-down]}
— no hold-time
loopback {line | internal}
— no loopback
[no] path [sonet-sdh-index]
— access
— egress
vport name [create]
— no vport name
[no] agg-rate
rate kilobits-per-second
— no rate
description description-string
host-match dest description-string [create]
— no host-match dest destination-string
[no] mon-port-sch
port-scheduler-policy port-scheduler-policy-name
scheduler-policy scheduler-policy-name
atm
cell-format {uni | nni}
buffer-pool value
vc-threshold buffer-threshold
ilmi [vpi/vci]
— no ilmi
egress
traffic-desc traffic-desc-profile-id
traffic-desc traffic-desc-profile-id
keep-alive [poll-frequency seconds] [poll-count value] [test-frequency seconds]
— no keep-alive
protocol protocol-type
— no protocol
[no] shutdown
min-vp-vpi value
down-count down-count
— no down-count
keepalive time-interval
— no keepalive
up-count up-count
— no up-count
crc {16 | 32}
description long-description-string
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc}
[no] frf-12
egress
qos-profile profile-id
fragment-threshold threshold
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
mac ieee-address
— no mac
mode {access | network | hybrid}
mtu mtu-bytes
— no mtu
accounting-policy policy-id
[no] collect-stats
queue-policy name
payload {sts3 | tug3 | ds3 | e3 | vt2 | vt15 | ds1 | e1}
ppp
keepalive time-interval [dropcount drop-count]
— no keepalive
[no] report-alarm [pais] [plop] [prdi] [pplm] [prei] [puneq] [plcd]
[no] scramble
[no] shutdown
signal-label value
trace-string [trace-string]
[no] report-alarm [loc] [lais] [lrdi] [ss1f] [lb2er-sd] [lb2er-sf] [slof] [slos] [lrei]
section-trace {increment-z0 | byte value | string string}
[no] single-fiber
speed {oc3 | oc12}
— no speed
threshold {ber-sd | ber-sf} rate threshold-rate
— no threshold {ber-sd | ber-sf}
[no] tx-dus

2.20.1.15. TDM Commands

config
[no] port {port-id}
tdm
buildout {long | short}
[no] ds1 ds1-id
bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration
— no bert
[no] channel-group channel-group
atm
cell-format {uni | nni}
min-vp-vpi value
down-count down-count
— no down-count
keepalive time-interval
— no keepalive
up-count up-count
— no up-count
crc {16 | 32}
description long-description-string
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc | cem}
[no] frf-12
egress
qos-profile profile-id
fragment-threshold threshold
identifier frf16-identifier
— no identifier
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
idle-cycle-flag {flags | ones}
idle-payload-fill {all-ones}
idle-payload-fill pattern pattern
idle-signal-fill {all-ones}
idle-signal-fill pattern pattern
mac ieee-address
— no mac
mode {access | network}
mtu mtu-bytes
— no mtu
accounting-policy policy-id
[no] collect-stats
queue-policy name
ppp
compress {acfc [pfc] | pfc [acfc]}
— no compress
keepalive time-period [dropcount drop count]
— no keepalive
[no] scramble
[no] shutdown
speed {56 | 64}
timeslots timeslots
— no timeslots
clock-source {loop-timed | node-timed | adaptive | differential}
framing (DS-1) {esf | sf | ds1-unframed}
[no] invert-data
loopback {line | internal | fdl-ansi | fdl-bellcore | payload-ansi | inband-ansi | inband-bellcore}
— no loopback
[no] report-alarm [ais] [los] [oof] [rai] [looped] [ber-sd] [ber-sf]
[no] shutdown
signal-mode {cas}
threshold {ber-sd | ber-sf} rate {1 | 5 | 10 | 50 | 100}
— no threshold {ber-sd | ber-sf}
hold-time {[up hold-time-up] [down hold-time-down]}
— no hold-time
lbo [0dB | -7.5dB | -15.0dB | -22.5dB]
length {133 | 266 | 399 | 533 | 655}

2.20.1.16. DS3 Commands

config
[no] port {port-id}
tdm
[no] ds3 [sonet-sdh-index]
atm
cell-format {uni | nni}
mapping mapping
min-vp-vpi value
bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration
— no bert
channelized {ds1 | e1}
down-count down-count
— no down-count
keepalive time-interval
— no keepalive
up-count up-count
— no up-count
clock-source {loop-timed | node-timed}
crc {16 | 32}
description long-description-string
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc | cem}
[no] frf-12
egress
qos-profile profile-id
fragment-threshold threshold
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
framing (DS3) {c-bit | m23 | ds3-unframed}
idle-cycle-flag {flags | ones}
loopback {line | internal | remote}
— no loopback
mac ieee-address
— no mac
mdl {eic | lic | fic | unit | pfi | port | gen} mdl-string
— no mdl [eic | lic | fic | unit | pfi | port | gen]
mdl-transmit {path | idle-signal | test-signal}
— no mdl-transmit [path | idle-signal | test-signal]
mode {access | network}
mtu mtu-bytes
— no mtu
accounting-policy policy-id
[no] collect-stats
queue-policy name
ppp
keepalive time-period [dropcount drop-count]
— no keepalive
[no] report-alarm [ais] [los] [oof] [rai] [looped]
[no] scramble
[no] shutdown
subrate {digital-link | larscom} rate-step
— no subrate

2.20.1.17. E1 Commands

config
[no] port {port-id}
tdm
[no] e1 [e1-id]
bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration
— no bert
[no] channel-group channel-group-id
atm
cell-format {uni | nni}
min-vp-vpi value
down-count down-count
— no down-count
keepalive time-interval
— no keepalive
up-count up-count
— no up-count
crc {16 | 32}
description long-description-string
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc | cem}
[no] frf-12
egress
qos-profile profile-id
fragment-threshold threshold
identifier frf16-identifier
— no identifier
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
idle-cycle-flag {flags | ones}
idle-payload-fill {all-ones}
idle-payload-fill pattern pattern
idle-signal-fill {all-ones}
idle-signal-fill pattern pattern
mac ieee-address
— no mac
[no] mode {access | network}
mtu mtu-bytes
— no mtu
accounting-policy policy-id
[no] collect-stats
queue-policy name
ppp
compress {afc [pfc] | [pfc] afc]}
— no compress
keepalive time-period [dropcount drop count]
— no keepalive
[no] scramble
[no] shutdown
speed {56 | 64}
timeslots timeslots
— no timeslots
clock-source {loop-timed | node-timed | adaptive | differential}
framing (E-1) {no-crc-g704 | g704 | e1-unframed}
[no] invert-data
loopback {line | internal}
— no loopback
national-bits sa4 sa5 sa6 sa7 sa8
[no] report-alarm [ais] [los] [oof] [rai] [looped] [ber-sd] [ber-sf]
[no] shutdown
signal-mode {cas}
— no signal-mode {cas}
threshold {ber-sd | ber-sf} rate {1 | 5 | 10 | 50 | 100}
— no threshold {ber-sd | ber-sf}

2.20.1.18. E3 Commands

config
[no] port {port-id}
tdm
[no] e3 [sonet-sdh-index]
atm
cell-format {uni | nni}
min-vp-vpi value
bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration
— no bert
down-count down-count
— no down-count
keepalive time-interval
— no keepalive
up-count up-count
— no up-count
clock-source {loop-timed | node-timed}
crc {16 | 32}
description long-description-string
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
— no level priority-level
max-rate rate
max-rate percent percent-rate
— no max-rate
egress-scheduler-policy port-scheduler-policy-name
encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc | cem}
[no] frf-12
egress
qos-profile profile-id
fragment-threshold threshold
lmi-type {ansi | itu | none | rev1}
mode {dce | dte | bidir}
n391dte intervals
— no n391dte
n392dce threshold
— no n392dce
n392dte threshold
— no n392dte
n393dce count
— no n393dce
n393dte count
— no n393dte
t391dte keepalive
— no t391dte
t392dce keepalive
— no t392dce
framing (E-3) {g751 | g832 | e3-unframed}
idle-cycle-flag {flags | ones}
loopback {line | internal}
— no loopback
mac ieee-address
— no mac
mode {access | network}
mtu mtu-bytes
— no mtu
accounting-policy policy-id
[no] collect-stats
queue-policy name
ppp
keepalive time-period [dropcount drop-count]
— no keepalive
[no] report-alarm [ais] [los] [oof] [rai] [looped]
[no] scramble
[no] shutdown

2.20.1.19. LAG Commands

config
[no] lag lag-id
access
adapt-qos {link | port-fair | distribute [include-egr-hash-cfg]}
bandwidth bandwidth
— no bandwidth
booking-factor factor
bfd
family {ipv4 | ipv6}
local-ip-address ip-address
max-admin-down-time [[down-interval] | infinite]
max-setup-time [[up-interval] | infinite]
multiplier [multiplier]
— no multiplier
receive-interval interval
remote-ip-address ip-address
[no] shutdown
transmit-interval interval
description long-description-string
[no] dynamic-cost
encap-type {dot1q | null | qinq}
— no encap-type
[no] mep mep-id domain md-index association ma-index [vlan vlan-id]
[no] ais-enable
client-meg-level [level [level]]
interval {1 | 60}
— no interval
low-priority-defect {allDef | macRemErrXcon}
priority priority-value
— no priority
[no] ccm-enable
ccm-ltm-priority priority
ccm-padding-size ccm-padding
ccm-tlv-ignore [port-status] [interface-status]
[no] csf-enable
multiplier multiplier-value
— no multiplier
description description-string
bit-error-threshold bit-errors
test-pattern {all-zeros | all-ones} [crc-enable]
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
hold-time down hold-down-time
— no hold-time
lacp [mode] [administrative-key admin-key] [system-id system-id] [system-priority priority]
lacp-mux-control {coupled | independent}
lacp-xmit-interval {slow | fast}
link-map-profile lag-link-map-profile-id [create]
— no link-map-profile lag-link-map-profile-id
description description-string
failure-mode [discard | per-link-hash]
link port-id {primary | secondary}
— no link port-id
mac ieee-address
— no mac
mode {access | network | hybrid}
— no mode
[no] per-link-hash
per-link-hash weighted [auto-rebalance]
port port-id [port-id] [priority priority] [sub-group sub-group-id]
— no port port-id [port-id]
port-threshold value [action {dynamic-cost | down}]
port-type lag-port-type
— no port-type
selection-criteria [best-port | highest-count | highest-weight] [slave-to-partner] [subgroup-hold-time hold-time]
[no] shutdown
standby-signaling {lacp | power-off}
weight-threshold value [action {dynamic-cost | down}]

2.20.1.20. MACsec Commands

config
macsec
connectivity-association ca-name [create]
cipher-suite {cipher-suite}
— no cipher-suite
clear-tag-mode clear-tag-mode
description description
— no description
encryption-offset encryption-offset
replay-window-size number-of-packets
[no] shutdown
[no] static-cak
active-psk active-pre-shared-key
— no active-psk
pre-shared-key pre-shared-key-index [encryption-type encryption-type] [create]
— no pre-shared-key pre-shared-key-index
cak hex-string [hash | hash2]
— no cak
ckn hex-string
— no ckn

2.20.1.21. Ethernet Tunnel Commands

config
[no] eth-tunnel tunnel-index
ccm-hold-time {down down-timeout | up up-timeout}
description long-description-string
encap-type {dot1q | qinq}
— no encap-type
[no] mac ieee-address
access
adapt-qos {distribute | link | port-fair}
— no adapt-qos
path-threshold num-paths
[no] path path-index
control-tag qtag[.qtag]
description description-string
[no] mep mep-id domain md-index association ma-index
[no] ccm-enable
ccm-ltm-priority priority
ccm-padding-size ccm-padding
[no] control-mep
description description-string
bit-error-threshold bit-errors
test-pattern {all zeros | all-ones} [crc-enable]
grace
eth-ed
priority priority
— no priority
[no] rx-eth-ed
[no] tx-eth-ed
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
mac-address mac-address
[no] shutdown
member port-id
— no member
precedence {primary | secondary}
— no precedence
[no] shutdown
protection-type {g8031-1to1 | loadsharing}
revert-time time
[no] shutdown

2.20.1.22. Multi-Chassis Redundancy Commands

config
boot-timer seconds
— no boot-timer
peer ip-address [create]
— no peer ip-address
authentication-key [authentication-key | hash-key] [hash | hash2]
description description-string
[no] mc-endpoint
[no] bfd-enable
boot-timer interval
— no boot-timer
keep-alive-interval interval
[no] passive-mode
[no] shutdown
system-priority value
[no] mc-lag
keep-alive-interval interval
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]
— no lag lag-id
[no] shutdown
ring sync-tag [create]
— no ring sync-tag
dst-ip ip-address
— no dst-ip
interface ip-int-name
— no interface
service-id service-id
— no service-id
service-name service-name
[no] path-b
[no] range vlan-range
[no] path-excl
[no] range vlan-range
ring-node ring-node-name [create]
— no ring-node ring-node-name
dst-ip ip-address
— no dst-ip
interval interval
— no interval
service-id service-id
— no service-id
service-name service-name
[no] shutdown
src-ip ip-address
— no src-ip
src-mac ieee-address
— no src-mac
vlan vlan-encap
— no vlan
[no] shutdown
peer-name peer-name
— no peer-name
[no] shutdown
source-address ip-address
[no] sync
[no] igmp
[no] igmp-snooping
[no] mc-ring
[no] mld
[no] mld-snooping
pim-snooping [saps] [spoke-sdps]
port port-id [sync-tag sync-tag] [create]
— no port [port-id | lag-id]
range encap-range sync-tag sync-tag
— no range encap-range
[no] shutdown
[no] srrp
[no] sub-mgmt

2.20.2. Configuration Command Descriptions

2.20.2.1. Generic Commands

description

Syntax 
description description-string
no description
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
config>eth-tunnel>path>eth-cfm>mep
config>fwd-path-ext>fpe
config>lag>link-map-profile
config>port>ethernet>access>egr>qgrp
config>port>ethernet>access>egr>vport
config>port>ethernet>access>ing>qgrp
config>port>ethernet>eth-cfm>mep
config>port>ethernet>network>egr>qgrp
config>port>ethernet>egress>hs-secondary-shaper
config>port-xc>pxc
config>redundancy>multi-chassis>peer
Description 

This command creates a text description for a configuration context to help identify the content in the configuration file.

The no form of this command removes any description string from the context.

This command is supported on TDM satellite.

Default 

no description

Parameters 
description-string—
Specifies a description character string. Strings can be up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

description

Syntax 
description long-description-string
no description
Context 
config>port
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
config>lag
Description 

This command creates a text description for a configuration context to help identify the content in the configuration file.

The no form of this command removes any description string from the context.

Default 

no description

Parameters 
long-description-string—
Specifies the description character string. Strings can be up to 160 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

shutdown

Syntax 
[no] shutdown
Context 
config>card
config>card>fp>ingress>mcast-path-management
config>card>mcm
config>card>mda
config>interface-group-handler
config>lag
config>lag>eth-cfm>mep
config>port
config>port>ethernet
config>port>ethernet>dwl
config>port>ethernet>efm-cfm>mep
config>port>ethernet>efm-oam
config>port>ethernet>ssm
config>port>ethernet>symbol-monitor
config>port>otu
config>port>sonet-sdh>path
config>port>tdm>ds1
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1
config>port>tdm>e1>channel-group
config>port>tdm>e3
config>port>ml-bundle>ima>test-pattern-procedure
config>port>sonet-sdh>path>atm>ilmi
config>port>sonet-sdh>path>atm>ilmi
config>port>ethernet>dampening
config>port>ethernet>eth-cfm>mep
config>port>ethernet>efm-oam
config>port-xc>pxd
config>redundancy>multi-chassis>peer
config>redundancy>mc>peer>mcr
config>redundancy>mc>peer>mc-lag
config>redundancy>mc>peer>mcr>ring
config>redundancy>mc>peer>mcr>node>cv
config>redundancy>multi-chassis>peer>sync
config>redundancy>multi-chassis>peer>mc-endpoint
Description 

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within.

The no form of this command administratively enables an entity.

This command is supported on TDM satellite.

Special Cases 
card—
Specifies the default state for a card is no shutdown.
interface group handler (IGH)—
Specifies the default state for an IGH is shutdown.
mda—
Specifies the default state for a mda is no shutdown.
lag—
Specifies the default state for a Link Aggregation Group (LAG) is shutdown.
port—
Specifies the default state for a port is shutdown.
path—
Specifies the default state for a SONET/SDH path is shutdown.

2.20.2.2. Card Commands

card

Syntax 
[no] card slot-number
Context 
config
Description 

This mandatory command enables access to the chassis card Input/Output, Control Forwarding Module (IOM/CFM), slot, MCM, MDA, XCM and XMA CLI contexts.

The no form of this command removes the card from the configuration. All associated ports, services, and MDAs must be shutdown.

Default 

no card

Parameters 
slot-number—
Specifies the slot number of the card in the chassis. The maximum slot number is platform dependent. Refer to the hardware installation guides.
Values—
1 to 10

 

card-type

Syntax 
card-type card-type [level card-level]
no card-type
Context 
config>card
Description 

This mandatory command adds an IOM/XCM to the device configuration for the slot. The card type can be preprovisioned, meaning that the card does not need to be installed in the chassis.

A card must be provisioned before an MDA, MCM, connector, or port can be configured.

A card can only be provisioned in a slot that is vacant, meaning no other card can be provisioned (configured) for that particular slot. To reconfigure a slot position, use the no form of this command to remove the current information.

A card can only be provisioned in a slot if the card type is allowed in the slot. An error message is generated if an attempt is made to provision a card type that is not allowed.

If a card is inserted that does not match the configured card type for the slot, then a log event and facility alarm is raised. The alarm is cleared when the correct card type is installed or the configuration is modified.

A log event and facility alarm are is raised if an administratively enabled card is removed from the chassis. The alarm is cleared when the correct card type is installed or the configuration is modified. A log event is issued when a card is removed that is administratively disabled.

Because IMMs do not have the capability to install separate MDAs, the configuration of the MDA is automatic. This configuration only includes the default parameters such as default buffer policies. Commands to manage the MDA such as shutdown, named buffer pool, and so on, remain in the MDA configuration context.

Some card hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two card types that are the same, except for a “-ptp” suffix to indicate the second loadset; for example, imm40-10gb-sfp and imm40-10gb-sfp-ptp. A hard reset of the card occurs when switching between the two provisioned types.

An appropriate alarm is raised if a partial or complete card failure is detected. The alarm is cleared when the error condition ceases.

New generations of cards include variants controlled by hardware and software licensing. For these cards, the license level must be provisioned in addition to the card type. A card can not become operational unless the provisioned license level matches the license level of the card installed into the slot. The set of license levels varies by card type.

The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration exists that would not be permitted with the new target license level.

If the license level is not specified, the level is set to the highest license level for that card.

The no form of this command removes the card from the configuration.

Default 

no card-type

Parameters 
card-type—
Specifies the type of card to be configured and installed in that slot. Values for this attribute vary by platform and release. The release notes include a listing of all supported card-types and their CLI strings. In addition, the command can be queried to check which card-types are relevant for the active platform type. Some examples include iom4-e-b and imm-2pac-fp3.
card-level—
Specifies the license level of the card, up to 32 characters. Possible values vary by card type.

fail-on-error

Syntax 
[no] fail-on-error
Context 
config>card
Description 

This command controls the behavior of the card when any one of a specific set of card level errors is encountered in the system. When the fail-on-error command is enabled, and any one (or more) of the specific errors is detected, then the Operational State of the card is set to Failed. This Failed state will persist until the clear card command is issued (reset) or the card is removed and re-inserted (re-seat). If the condition persists after re-seating the card, then Nokia support should be contacted for further investigation.

Enabling fail-on-error is only recommended when the network is designed to be able to route traffic around a failed card (redundant cards, nodes or other paths exist).

The list of specific errors includes:

  1. CHASSIS event ID# 2063 – tmnxEqCardPChipMemoryEvent
  2. CHASSIS event ID# 2076 – tmnxEqCardPChipCamEvent
  3. CHASSIS event ID# 2059 – tmnxEqCardPChipError (for ingress Ethernet only)
  4. CHASSIS event ID# 2098 tmnxEqCardQChipBufMemoryEvent
  5. CHASSIS event ID# 2099 tmnxEqCardQChipStatsMemoryEvent
  6. CHASSIS event ID# 2101 tmnxEqCardQChipIntMemoryEvent
  7. CHASSIS event ID# 2103 tmnxEqCardChipIfCellEvent

On platforms without independent IOM/IMM and CPM cards, such as the 7750 SR c4/c12 or 7450 ESS-1, the node will be rebooted if fail-on-error is enabled and one of the card level errors is encountered.

The tmnxEqCardPChipError is only considered as a trigger for card fail-on-error for ingress FCS errors (not egress FCS errors), and only for Ethernet MDAs or IMMs.

Note that upon the detection of the event/error in the system, the reporting of the event (logs) and the fail-on-error behavior of the card are independent. Log event control configuration will determine whether the events are reported in logs (or SNMP traps, etc) and the fail-on-error configuration will determine the behavior of the card. This implies that the card can be configured to fail-on-error even if the events are suppressed (some may be suppressed in the system by default). In order to facilitate post-failure analysis, Nokia recommends that you enable the reporting of the specific events/errors (configure log event-control) when fail-on-error is enabled.

Default 

no fail-on-error

named-pool-mode

Syntax 
[no] named-pool-mode [now]
Context 
config>card
Description 

This command places an IOM in the named pool mode. When in named pool mode, the system will change the way default pools are created and allow for the creation of MDA and port level named buffer pools. When not enabled, the system will create default ingress and egress pools per port. When enabled, the system will not create per port pools, instead a default network and access pool is created for ingress and egress and is shared by queues on all ports.

The named pool mode may be enabled and disabled at anytime. Care should be taken when changing the pool mode for an IOM as the process of changing to or from named pool mode causes an IOM reset if MDAs are currently provisioned on the slot. If MDAs have not been provisioned at the time the named-pool-mode or no named-pool-mode command is executed, the IOM is not reset (for example, when the system is booting, the named pool mode command does not reset the IOM since the mode is set prior to provisioning the IOM’s MDAs).

This command is not enabled for the ISA-AA MDA.

The no form of the command converts the pool mode on the IOM card to the default mode. If MDAs are currently provisioned on the IOM, the card is reset.

Default 

no named-pool-mode

Parameters 
now—
Changes named-pool-mode without prompting.

reset-on-recoverable-error

Syntax 
[no] reset-on-recoverable-error
Context 
config>card
Description 

This command configures the behavior of the card when a fatal memory parity error is detected on a Q-chip of the card. If reset-on-recoverable-error is enabled, the card is reset, regardless of the setting of the fail-on-error parameter.

The no form of this command specifies that the recovery action is taken instead of resetting the card.

Default 

no reset-on-recoverable-error

2.20.2.3. MCM Commands

MCM commands are supported on the 7750 SR only.

mcm

Syntax 
[no] mcm mcm-slot
Context 
config>card
Description 

This mandatory command enables access to a card’s MCM CLI context to configure MCMs.

Parameters 
mcm-slot—
Specifies the MCM slot number to be configured. Even slot numbers 2 to 12 are invalid. MCM provisioning is not required to provision Compact Media Adapters (CMAs).
Values—
7750 SR-c4: 1, 3 7750 SR-c12: 1, 3, 5, 7, 9, 11

 

mcm-type

Syntax 
mcm mcm-type
no mcm mcm-type
Context 
config>card>mcm
Description 

This mandatory command provisions a specific MCM type to the device configuration for the slot. The MCM can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.

To modify an MCM slot, shut down all port associations. MCMs are required to provision MDAs. MCMs are not required to provision CMAs.

Parameters 
mcm-type—
Specifies the type of MCM to provision for that slot.
Values—
mcm-v1, mcm-v2

 

2.20.2.4. MDA (XMA) Commands

mda

Syntax 
[no] mda mda-slot
Context 
config>card
Description 

This mandatory command enables access to a card’s MDA CLI context to configure MDAs.

Parameters 
mda-slot—
Specifies the MDA slot number to be configured. Slots are numbered 1 and 2. On vertically oriented slots, the top MDA slot is number 1, and the bottom MDA slot is number 2. On horizontally oriented slots, the left MDA is number 1, and the right MDA slot is number 2. For 7750 SR-c12/4 systems, MDAs may not be provisioned before MCMs are configured for the same slot. MCMs are not required for CMA provisioning.
Values—
1, 2

 

Values—
7750 SR c-12 MDA: 1, 3, 5, 7, 9, 11 7750 SR c-12 CMA: 1-12 7750 SR c-4 MDA: 1, 3 7750 SR c-4 CMA: 1-4

 

clock-mode

Syntax 
clock-mode adaptive
clock-mode differential [timestamp-freq {19440 | 77760 | 103680}]
Context 
config>card>mda
Description 

This command defines the clocking mode on the specified CMA/MDA. This command is only supported on CES CMAs and MDAs.

Default 

clock-mode adaptive

Parameters 
adaptive—
Specifies that MDA is in the adaptive clock mode. This CMA/MDA can use adaptive clock recovery methods.
differential—
Specifies that MDA is in the differential clock mode. This CMA/MDA can use differential clock recovery methods.
timestamp-freq—
Sets the differential timestamp frequency to be 103.68 MHz (default), 77,76 MhZ or 19.44 MHz. The frequency value is entered in kHz, thus valid values are 103680, 77760 and 19440. If this parameter is omitted, the default timestamp frequency of 103.68 MHz is used.
Values—
19440, 77760, 103680

 

fail-on-error

Syntax 
[no] fail-on-error
Context 
config>card>mda
Description 

This command enables the fail-on-error feature. If an MDA is experiencing too many Egress XPL Errors, this feature causes the MDA to fail. This can force an APS switchover or traffic re-route. The purpose of this feature is to avoid situations where traffic is forced to use a physical link that suffers from errors but is still technically operational.

The feature uses values configured in the config>card>mda>egress-xpl context. When this feature is enabled on a MDA, if window consecutive minutes pass in which the MDA experiences more than threshold Egress XPL Errors per minute, then the MDA will be put in the failed state.

The no form of this command disables the feature on the MDA.

egress

Syntax 
egress
Context 
config>card>mda
Description 

This command enables the context to configure egress MDA parameters.

egress-xpl

Syntax 
egress-xpl
Context 
config>card>mda
Description 

This command enables the context to configure egress-xpl settings used by the fail-on-error feature.

threshold

Syntax 
threshold xpl-errors
Context 
config>card>mda>egress-xpl
Description 

This command configures the Egress XPL Error Threshold value used by the fail-on-error feature.

Default 

threshold 1000

Parameters 
xpl-errors—
Specifies an upper limit on the frequency of Egress XPL Errors that can occur on the MDA. When fail-on-error is enabled, if the MDA experiences more than xpl-errors errors per minute for the specified number of minutes from the window minutes command, the MDA will be put in the failed state.

The threshold value cannot be changed while fail-on-error is enabled for this MDA.

Values—
1 to 1000000

 

window

Syntax 
window minutes
Context 
config>card>mda>egress-xpl
Description 

This command configures the Error Window value used by the fail-on-error feature.

Default 

window 60

Parameters 
minutes—
Specifies the time, in minutes, that the MDA can experience frequent Egress XPL Errors. When fail-on-error is enabled, if more than xpl-errors Egress XPL errors per minute occur on the MDA for the specified number of consecutive minutes, the MDA will be put in the failed state.

The window value cannot be changed while fail-on-error is enabled for this MDA.

Values—
1 to 1440

 

mda-type

Syntax 
mda-type mda-type [level mda-level]
no mda-type
Context 
config>card>mda
Description 

This mandatory command provisions a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.

A maximum of two MDAs can be provisioned on an IOM/XCM. Only one MDA can be provisioned per IOM/MDA slot. To modify an MDA slot, shut down all port associations.

A maximum of six MDAs or eight CMAs (or a combination) can be provisioned on a 7750 SR-c12. Only one MDA/CMA can be provisioned per MDA slot. To modify an MDA slot, shut down all port associations.

CMAs do not rely on MCM configuration and are provisioned without MCMs.

CMAs/XMAs are provisioned using MDA commands. A medium severity alarm is generated if an MDA/CMA is inserted that does not match the MDA/CMA type configured for the slot. This alarm is cleared when the correct MDA/CMA is inserted or the configuration is modified. A high severity alarm is raised when an administratively enabled MDA/CMA is removed from the chassis. This alarm is cleared if the either the correct MDA/CMA type is inserted or the configuration is modified. A low severity trap is issued if an MDA/CMA is removed that is administratively disabled.

An MDA can only be provisioned in a slot if the MDA type is allowed in the MDA slot. An error message is generated when an MDA is provisioned in a slot where it is not allowed.

Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two MDA types that are the same, except for a “-ptp” suffix to indicate the second loadset; for example, x40-10gb-sfp and x40-10gb-sfp-ptp. A hard reset of the MDA occurs when switching between the two provisioned types.

A medium severity alarm is generated if an MDA is inserted that does not match the MDA type configured for the slot. This alarm is cleared when the correct MDA is inserted or the configuration is modified.

A high severity alarm is raised when an administratively enabled MDA is removed from the chassis. This alarm is cleared if the either the correct MDA type is inserted or the configuration is modified. A low severity trap is issued if an MDA is removed that is administratively disabled.

An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases.

All parameters in the MDA context remain and if non-default values are required then their configuration remains as it is on all existing MDAs.

New generations of XMAs include variants controlled through hardware and software licensing. For these XMAs, the license level must be provisioned in addition to the MDA type. An XMA can not become operational unless the provisioned license level matches the license level of the XMA installed into the slot. The set of license levels varies by MDA type.

The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration that would not be permitted with the new target license level exists.

If the license level is not specified, the level is set to the highest license level for that XMA.

The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.

Parameters 
mda-type—
Specifies the type of MDA selected for the slot position. Values for this attribute vary by platform and release. The release notes include a listing of all supported mda-types and their CLI strings. In addition, the command can be queried to check which mda-types are relevant for the active platform type. Some examples include me6-10gb-spf+ and x4-100g-cfp2.
mda-level—
Specifies the MDA level. Possible values vary by MDA type.

named-pool-mode

Syntax 
named-pool-mode
Context 
config>card>mda
config>port
Description 

This command enables the context to configure egress and ingress named pool parameters to store the MDA and port level named pool mode configuration commands. Currently, only the ingress and egress named-pool-policy commands are supported. Any future named pool mode configuration commands or overrides will be placed in the named-pool-mode CLI context. Within the context is an ingress and egress context.

Enter the named-pool-mode to define the ingress and egress named pool policy associations for either an MDA or port. The node may be entered regardless of the current named-pool-mode state of the IOM.

egress

Syntax 
egress
Context 
config>card>mda>named-pool-mode
config>port>named-pool-mode
Description 

The egress node within the named-pool-mode context is used to contain the egress named-pool-policy configuration. Enter the egress node when defining or removing the MDA or port level egress named pool policy.

ingress

Syntax 
ingress
Context 
config>card>mda>named-pool-mode
config>port>named-pool-mode
Description 

The ingress node within the named-pool-mode context is used to contain the ingress named-pool-policy configuration. Enter the ingress node when defining or removing the MDA or port level ingress named pool policy.

named-pool-policy

Syntax 
named-pool-policy policy-name
no named-pool-policy
Context 
config>card>mda>named-pool-mode>ingress
config>card>mda>named-pool-mode>egress
config>port>named-pool-mode>ingress
config>port>named-pool-mode>egress
Description 

This command associates a named pool policy with an MDA or port ingress or egress context. The policy governs the way that named pools are created at the MDA or port level. The policy may be applied regardless of whether the IOM is in named pool mode; however, a named pool policy to an MDA or port to a card that is not on named pool mode will be ignored. Pools may not be created due to insufficient resources or pool name collisions. Pool name collisions are allowed. The name check is performed independently between ingress and egress. A port on ingress may have a named pool defined that is also on the egress side at the MDA level. Multiple ports on the same MDA may have the same policy or the same named pools defined. Ports on the same MDA may also have different named pool policies defined.

The no named-pool-policy command removes any existing policy associated with the MDA or port.

Default 

no named-pool-policy

Parameters 
policy-name—
Specifies an existing named pool policy on the system, up to 32 characters. If policy-name does not exist, the named-pool-policy command fails. If another named pool policy is currently associated, it continues to be associated on the MDA or port. If the policy-name does exist, the pools within the current policy (if a policy is currently associated) will be removed and the pools defined within the new policy will be created. Queues on the port or MDA will be moved to the new pools. If a pool being used by a queue existed on the previous policy, but not in the new policy, the queue is moved to the appropriate default pool and marked as ‘pool-orphaned’. The policy-name may be changed at any time.

power-priority-level

Syntax 
power-priority-level priority
no power-priority-level
Context 
config>card>mda
Description 

This command sets the power priority value for the 7950 XRS.

Default 

power-priority-level 150

Parameters 
priority —
Specifies the power priority level. An operator must assign a priority value to each XMA using a range of number from 1 to 200. The lowest number has the highest priority. The priority number range from 1 to 100 should be used for modules considered essential for system operation. Lower priority values of 101 to 200 should be used for non-essential modules.

reset-on-recoverable-error

Syntax 
[no] reset-on-recoverable-error
Context 
config>card>mda
Description 

This command configures the behavior of the MDA when a fatal memory parity error is detected on a Q-chip of the MDA. If reset-on-recoverable-error is enabled, the MDA is reset, regardless of the setting of the fail-on-error parameter.

The no form of this command specifies that the recovery action is taken instead of resetting the MDA.

Default 

no reset-on-recoverable-error

sync-e

Syntax 
[no] sync-e
Context 
config>card>mda
Description 

This command enables synchronous Ethernet on the MDA. Then any port on the MDA can be used as a source port in the sync-if-timing configuration.

The no form of the command disables synchronous Ethernet on the MDA.

2.20.2.5. MDA/Port QoS Commands

access

Syntax 
access
Context 
config>card>mda
config>port
Description 

This command enables the access context to configure egress and ingress pool policy parameters.

On the MDA level, access egress and ingress pools are only allocated on channelized MDAs/CMAs.

egress

Syntax 
egress
Context 
config>card>mda>access
config>card>mda>network
config>port>access
config>port>network
Description 

This command enables the context to configure egress buffer pool parameters which define the percentage of the pool buffers that are used for CBS calculations and specify the slope policy that is configured in the config>qos>slope-policy context.

On the MDA level, network and access egress pools are only allocated on channelized MDAs/CMAs.

pool

Syntax 
[no] pool [name]
Context 
config>card>mda>access>egress
config>card>mda>access>ingress
config>card>mda>network>egress
config>port>access>egress
config>port>access>ingress
config>port>access>uplink>egress
config>port>network>egress
config>port>network>ingress
Description 

This command configures pool policies.

On the MDA level, access and network egress and access ingress pools are only allocated on channelized MDAs. On the MDA level, access and network egress and access ingress pools are only allocated on channelized MDAs. Network ingress pools are allocated on the MDA level for non-channelized MDAs.

Default 

pool default

Parameters 
name—
Specifies the pool name, a string up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

amber-alarm-threshold

Syntax 
amber-alarm-threshold percentage
no amber-alarm-threshold
Context 
config>card>mda>access>egress>pool
config>card>mda>access>ingress>pool
config>card>mda>network>egress>pool
config>card>mda>network>ingress>pool
config>port>access>egress>pool
config>port>access>ingress>pool
config>port>network>egress>pool
Description 

This command configures the threshold for the amber alarm on the over-subscription allowed.

Users can selectively enable amber or red alarm thresholds. But if both are enabled (non-zero) then the red alarm threshold must be greater than the amber alarm threshold.

The no form of the command reverts to the default value.

Default 

no amber-alarm-threshold

Parameters 
percentage—
Specifies the amber alarm threshold.
Values—
1 to 1000

 

red-alarm-threshold

Syntax 
red-alarm-threshold percentage
no red-alarm-threshold
Context 
config>card>mda>access>egress>pool
config>card>mda>access>ingress>pool
config>card>mda>network>egress>pool
config>card>mda>network>ingress>pool
config>port>access>egress>pool
config>port>access>ingress>pool
config>port>network>egress>pool
Description 

This command configures the threshold for the red alarm on the over-subscription allowed.

Users can selectively enable amber or red alarm thresholds. But if both are enabled (non-zero) then the red alarm threshold must be greater than the amber alarm threshold.

The no form of the command reverts to the default value.

Default 

no red-alarm-threshold

Parameters 
percentage—
Specifies the amber alarm threshold.
Values—
1 to 1000

 

resv-cbs

Syntax 
resv-cbs percent-or-default amber-alarm-action step percent max percent
resv-cbs percent-or-default
no resv-cbs
Context 
config>card>mda>access>egress>pool
config>card>mda>access>ingress>pool
config>card>mda>network>egress>pool
config>card>mda>network>ingress>pool
config>port>access>egress>channel>pool
config>port>access>egress>pool
config>port>access>ingress>pool
config>port>ethernet>network
config>port>network>egress>pool
Description 

This command defines the percentage or specifies the sum of the pool buffers that are used as a guideline for CBS calculations for access and network ingress and egress queues. Two actions are accomplished by this command:

  1. A reference point is established to compare the currently assigned (provisioned) total CBS with the amount the buffer pool considers to be reserved. Based on the percentage of the pool reserved that has been provisioned, the over provisioning factor can be calculated.
  2. The size of the shared portion of the buffer pool is indirectly established. The shared size is important to the calculation of the instantaneous-shared-buffer-utilization and the average-shared-buffer-utilization variables used in Random Early Detection (RED) per packet slope plotting.

It is important to note that this command does not actually set aside buffers within the buffer pool for CBS reservation. The CBS value per queue only determines the point at which enqueuing packets are subject to a RED slope. Oversubscription of CBS could result in a queue operating within its CBS size and still not able to enqueue a packet due to unavailable buffers. The resv-cbs parameter can be changed at any time.

If the total pool size is 10 MB and the resv-cbs set to 5, the ‘reserved size’ is 500 KB.

The no form of this command restores the default value.

The no resv-cbs command will clear all the adaptive configurations. There cannot be any adaptive sizing enabled for default resv-cbs.

Default 

resv-cbs 30

Parameters 
percent-or-default—
Specifies the pool buffer size percentage.
Values—
0 to 100, or default

 

amber-alarm-action step percent
Specifies the percentage step-size for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, step percent must be set to non-default value along with the max parameter. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS (Committed Burst Size) defines the amount of buffer space within the pool that is not considered shared.
Values—
1 to 100

 

Default—
0
max percent
Specifies the maximum percentage for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, max value must be set to non-default value along with the step percent. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS (Committed Burst Size) defines the amount of buffer space within the pool that is not considered shared. Max reserved CBS must not be more than the reserved CBS.
Values—
1 to 100

 

Default—
0

slope-policy

Syntax 
slope-policy name
no slope-policy
Context 
config>card>mda>access>egress>pool
config>card>mda>access>ingress>pool
config>card>mda>network>egress>pool
config>card>mda>network>ingress>pool
config>port>access>egress>channel>pool
config>port>access>egress>pool
config>port>access>ingress>pool
config>port>network>egress>pool
Description 

This command specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The policy is defined in the config>qos>slope-policy context.

Default 

slope-policy default

Parameters 
name—
Specifies the policy name, a string up to 32 characters.

ingress

Syntax 
ingress
Context 
config>card>mda>access
config>card>mda>network
config>port>access
Description 

This command enables the context to configure ingress buffer pool parameters which define the percentage of the pool buffers that are used for CBS calculations and specify the slope policy that is configured in the config>qos>slope-policy context.

On the MDA level, access ingress pools are only allocated on channelized MDAs/CMAs.

ingress-xpl

Syntax 
ingress-xpl
Context 
config>card>mda
Description 

This command enables the context to configure ingress MDA XPL interface error parameters.

threshold

Syntax 
threshold xpl-errors
Context 
config>card>mda>ingress-xpl
Description 

This command configures the Ingress XPL Error Threshold value used by the fail-on-error feature.

Default 

threshold 1000

Parameters 
xpl-errors—
Specifies an upper limit on the frequency of Ingress XPL Errors that can occur on the MDA. When fail-on-error is enabled, if the MDA experiences more than xpl-errors errors per minute for the specified number of minutes from the window minutes command, the MDA will be put in the failed state.

The threshold value cannot be changed while fail-on-error is enabled for this MDA.

Values—
1 to 1000000

 

window

Syntax 
window minutes
Context 
config>card>mda>ingress-xpl
Description 

This command configures the Error Window value used by the fail-on-error feature.

Default 

window 60

Parameters 
minutes—
Specifies the time, in minutes, that the MDA can experience frequent Ingress XPL Errors. When fail-on-error is enabled, if more than xpl-errors Ingress XPL errors per minute occur on the MDA for the specified number of consecutive minutes, the MDA will be put in the failed state.

The window value cannot be changed while fail-on-error is enabled for this MDA.

Values—
1 to 1440

 

network

Syntax 
network
Context 
config>card>mda
config>port
Description 

This command enables the network context to configure egress and ingress pool policy parameters.

On the MDA level, network egress pools are only allocated on channelized MDAs/CMAs.

2.20.2.6. Power Commands

The following power commands are supported the 7950 XRS only.

mode

Syntax 
mode {none | basic | advanced}
Context 
config>system>power-management
Description 

This command sets the power mode.

Default 

mode basic

Parameters 
none—
Specifies that there is no management of power to modules. In this mode, no gradual shutdown of active XCMs and XMAs is enforced. No spare capacity is reserved and any APEQ failure may result in brownouts or card failures.
basic—
Specifies that the node will bring up as many provisioned modules (in order of priority) as possible using the N+1 algorithm. In basic mode the system shuts down IO cards when power capacity drops below the Power Safety Level.
advanced—
Specifies that the operator can maintain a spare APEQ as long as possible to make it immune to the possibility of power brown-outs. In advanced mode, the system starts shutting down IO cards when the power capacity drops below the Power Safety Level + Max rated APEQ.

pcm

Syntax 
[no] pcm pcm-slot [chassis chassis-id]
Context 
config>system>power-management
Description 

This command sets the PCM slot number.

Parameters 
pcm-slot—
Identifies the PCM slot.
Values—
1 to 12

 

chassis-id—
Specifies chassis ID for the router chassis.
Values—
1, 2

 

Default—
1

pcm-type

Syntax 
pcm-type pcm-type
no pcm-type
Context 
config>system>pwr-mgmt>pcm
Description 

This command sets the type of PCM for the designated PCM slot. This is not a mandatory configuration; however, by configuring a PCM type of quad-pcm, this ensures the system will always monitor for the presence of PCM fan trays and will provide an indication if no PCM fan trays are detected.

The no form of this command moves the PCM to an unprovisioned state.

Default 

no pcm-type

Parameters 
pcm-type—
Identifies the PCM type installed in the PCM slot.
Values—
dual-pcm, quad-pcm

 

peq

Syntax 
[no] peq peq-slot [chassis chassis-id]
Context 
config>system>power-management
Description 

This command sets the APEQ slot number.

Parameters 
peq-slot—
Identifies the APEQ slot.
Values—
1 to 12

 

chassis-id—
Specifies chassis ID for the router chassis.
Values—
1, 2

 

Default—
1

peq-type

Syntax 
peq-type peq-type
no peq-type
Context 
config>system>pwr-mgmt>peq
Description 

This command sets the type of APEQ for the designated APEQ slot.

The no form of this command moves the APEQ to an unprovisioned state.

Default 

no peq-type

Parameters 
peq-type—
Identifies the APEQ type.
Values—
apec-ac-3000, apeq-dc-2000, apeq-dc-2200-2800, apec-dc-4275, apeq-hvdc-3000

 

input-power-mode

Syntax 
input-power-mode amperage
Context 
config>system>pwr-mgmt>peq
Description 

This command sets the input-power-mode of the APEQ for the designated APEQ slot.

Parameters 
amperage—
Sets the APEQ input power mode.
Values—
60, 80

 

Default—
60

shutdown

Syntax 
[no] shutdown
Context 
config>system>pwr-mgmt>peq
Description 

This command administratively enables/disables the APEQ.

power-safety-alert

Syntax 
power-safety-alert wattage
Context 
config>system>pwr-mgmt
Description 

This command sets a value in watts for the Power Safety Alert. The Power Safety Alert minor alarm is generated when the system power capacity drops below the Power Safety Level (in watts) + the Power Safety Alert. This is a critical level, which when breached the system starts shutting down IO cards based on card priority.

Parameters 
wattage—
Specifies the number of Watts for the power safety alert level.
Values—
0 to 102600

 

Default—
0

power-safety-level

Syntax 
power-safety-level percent
Context 
config>system>pwr-mgmt
Description 

This command sets the Power Safety Level, which is a percentage of the calculated worst case power draw value. Once a Power Safety Level is configured by the operator, both the Basic and Advanced modes use the Power Safety Level as a reference for calculating the power redundancy using N+1 algorithm during start up and recovery from power depression.

Default 

power-safety-level 100

Parameters 
percent—
Specifies the Power Safety Level as a percentage of the calculated worst case power draw value.
Values—
0 to 100

 

2.20.2.7. Virtual Scheduler Commands

internal-scheduler-weight-mode

Syntax 
internal-scheduler-weight-mode {default | force-equal | offered-load | capped-offeredload}
no internal-scheduler-weight-mode
Context 
config>card>virt-sched-adj
Description 

This command specifies the internal scheduler weight mode.

Default 

default

Parameters 
default—
Specifies that queues are equally weighted, except at ingress for mixed-speed LAGs without per-fp-inq-queuing enabled and at egress for all mixed-speed LAGs, in which cases the queues are weighted based on port speed.
force-equal—
Specifies that the queues are always equally weighted.
offered-load—
Specifies that the queues are weighted based on observed offered load.
capped-offered-load—
Specifies that the queues are weighted based on observed offered load capped. by PIR

rate-calc-min-int

Syntax 
rate-calc-min-int [fast-queue percent-of-default] [slow-queue percent-of-default]
no rate-calc-min-int
Context 
config>card>virt-sched-adj
Description 

This command overrides the default minimum time that must elapse before a policer or queue’s offered rate may be recalculated. A minimum time between offered rate calculations is enforced to both prevent inaccurate estimation of the offered rate and excessive input to the virtual scheduler process.

In order to smooth out rapidly fluctuating offered rates, the system averages the measured offered rate with a window of previously measured offered traffic statistics and knowledge of the time between the samples.

The window size is defined by the “rate calculation minimum interval” with offered traffic statistics being read at most four times within the window. Any previous measured offered statistics within the window are used in the averaging function. Note that if there are large numbers of samples required, for example when a large number of queues are running HQoS, then it may be that a time greater than the “rate calculation minimum interval” passes before another sample of the offered statistics can be taken for a queue. In this case, in order to calculate an offered rate, HQoS will always use two samples, the current and the previous. In this case, using a smaller rate-calc-min-int will have no effect on the responsiveness of HQoS to queue rate changes.

The system separates policers and queues into fast and slow categories and maintains a separate “rate calculation minimum interval” for each type. The default for each type are as follows:

Slow Queue: 1.0 seconds

Fast Queue: 0.25 seconds

The actual minimum rate calculation interval may be increased or decreased by using the fast-queue and/or slow-queue keywords (which are also applicable for policers managed by HQoS) followed by a percent value which is applied to the default interval. The default slow-queue threshold rate is 1 Mb/s. Once a policer or queue is categorized as slow, its rate must rise to 1.5 Mb/s before being categorized as a fast policer or queue. The categorization threshold may be modified by using the slow-queue-threshold command.

The no rate-calc-min-interval command restores the default fast queue and slow queue minimum rate calculation interval.

Default 

no rate-calc-min-int

Parameters 
percent-of-default
Specifies that the fast-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for “fast” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the fast queue minimum rate calculation time.
Values—
0.01% to 1000.00%

 

Default—
100.00%
percent-of-default
Specifies that the slow-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for “slow” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the slow queue minimum rate calculation time.
Values—
0.01% to 1000.00%

 

Default—
100.00%

sched-run-min-int

Syntax 
sched-run-min-int percent-of-default
no sched-run-min-int
Context 
config>card>virt-sched-adj
Description 

This command overrides the default minimum time that must elapse before a virtual scheduler may redistribute bandwidth based on changes to the offered rates of member policers or queues. A minimum run interval is enforced to allow a minimum amount of “batching” queue changes before reacting to the changed rates. This minimum interval is beneficial since the periodic function of determining policer or queue offered rates is performed sequentially and the interval allows a number policer and queue rates to be determined prior to determining the distribution of bandwidth to the policers and queues.

The default minimum scheduler run interval is 0.5 seconds. The sched-run-min-int command uses a percent value to modify the default interval.

The no sched-run-min-int command restores the default minimum scheduler run interval for all virtual schedulers on the card.

Default 

no sched-run-min-int

Parameters 
percent-of-default—
Specifies that the percent-of-default parameter is required and is used to modify the default minimum scheduler run interval for all virtual schedulers on the card. Defining 100.00 percent is equivalent to removing the override (restoring the default) for the minimum scheduler run interval.
Values—
0.01% to 1000.00%

 

Default—
100.00%

slow-queue-threshold

Syntax 
slow-queue-threshold kilobits-per-second
no slow-queue-threshold
Context 
config>card>virt-sched-adj
Description 

This command overrides the system default rate threshold where policers and queues are placed in the “slow” queue category. Slow rate policers and queues use a different minimum rate calculation interval time than fast rate queues. The rate is determined based on the previous calculated offered rate for the policer or queue.

The default slow policer or queue rate is 1 Mb/s. The fast rate is derived by multiplying the slow rate by a factor of 1.5 resulting in a default fast rate of 1.5 Mb/s. The slow-queue-threshold command uses a “Kilobit-Per-Second” value to modify the default slow queue rate threshold and indirectly changes the fast queue rate threshold.

The no version of this command restores the default slow queue and fast rate thresholds.

Default 

no slow-queue-threshold

Parameters 
kilobits-per-second—
Specifies that the kilobit-per-second parameter is required and is used to modify the default slow rate threshold. Defining a value of 0 forces all policers and queues to be treated as fast rate. Defining a value of 1000 (1 Mb/s) returns the threshold to the default value and is equivalent to executing no slow-queue-threshold.

The fast rate threshold is derived by multiplying the new slow rate threshold by a factor of 1.5.

Values—
0 to 1000000 kb/s

 

Default—
1000 kb/s

task-scheduling-int

Syntax 
task-scheduling-int percent-of-default
no task-scheduling-int
Context 
config>card>virt-sched-adj
Description 

This command overrides the system default time between scheduling the hierarchical virtual scheduling task. By default, the system “wakes” the virtual scheduler task every 50ms; this is equivalent to five 10ms timer ticks. The task-scheduling-int command uses a percent value parameter to modify the number of timer ticks.

While the system accepts a wide range of percent values, the result is rounded to the nearest 10ms tick value. The fastest wake interval is 10ms (1 timer tick).

The no scheduling-int command restores the default task scheduling interval of the card’s hierarchical virtual scheduler task.

Parameters 
percent-of-default:—
Specifies that the percent-of-default parameter is required and is used to modify the default task scheduling interval for the hierarchical virtual scheduling task on the card. Defining 100.00 percent is equivalent to removing the override.
Values—
0.01% to 1000.00%

 

Default—
100.00%

2.20.2.8. Forwarding Plane Configuration Commands

fp

Syntax 
fp [fp-number]
Context 
config>card
Description 

This command enables access to the configuration of the forwarding planes on a card.

The default forwarding plane is 1. When entering the fp node, if the forwarding plane number is omitted, the system will assume forwarding plane number 1.

Commands can only be configured under card>fp if the hardware that the FP resides on (either a card or an XMA) is provisioned. Conversely, all commands under card>fp of the corresponding FPs are automatically removed when that hardware is unprovisioned.

Parameters 
fp-number—
Specifies that the fp-number parameter is optional following the fp command.
Values—
1 to 6

 

Default—
fp 1

egress

Syntax 
egress
Context 
config>card>fp
Description 

This command enables access to the egress fp CLI context.

hs-fixed-high-thresh-delta

Syntax 
hs-fixed-high-thresh-delta size-in-bytes
no hs-fixed-high-thresh-delta
Context 
config>card>fp>egress
Description 

This command specifies the egress QoS high threshold delta for this port.

Parameters 
size-in-bytes—
Specifies high threshold data in bytes.
Values—
0 to 65536

 

hs-pool-policy

Syntax 
hs-pool-policy name
no hs-pool-policy
Context 
config>card>fp>egress
Description 

This command specifies the egress QoS HS scheduler policy for this port.

When this forwarding plane is on non-High Scale card type, the value is ignored. If this forwarding plane is on High Scale card type, the default for this object will be the string 'default'.

Parameters 
name—
Specifies the HS pool policy name up to 32 characters in length.

wred-queue-control

Syntax 
wred-queue-control
Context 
config>card>fp>egress
Description 

This command enables the context to configure the aggregate WRED queue parameters for all WRED queues on an egress forwarding plane.

buffer-allocation

Syntax 
buffer-allocation min percentage max percentage
no buffer-allocation
Context 
config>card>fp>egress>wred-queue-control
Description 

The buffer-allocation command defines the amount of buffers that will be set aside for WRED queue buffer pools. Note that the min percentage and max percentage parameters must be set to the same value. The forwarding plane protects against cross application buffer starvation by implementing a hierarchy of buffer pools. At the top of the hierarchy are mega-pools. Mega-pools are used to manage buffers at a system application level. Two mega-pools are currently used by the system. The first (default) mega-pool services all non-WRED type queues and when WRED queues are not enabled will contain all available forwarding plane queue buffers. When WRED queuing is enabled, the second mega-pool (the WRED mega-pool) is given buffers from the default mega-pool based on the buffer-allocation command.

The mega-pools provide buffers to the second tier buffer pools. The default mega-pool services all default pools and explicitly created named pools. As the name implies, the WRED mega-pool services all the WRED buffer pools created for the WRED queues. The WRED mega-pool allows each WRED queue pool to be configured to an appropriate size while allowing the sum of the WRED queue pool sizes to oversubscribe the total amount set aside for WRED queue buffering without affecting the queues using the default or named pools.

No buffers are allocated to the WRED mega-pool until the wred-queue-control shutdown command is set to no shutdown. When the shutdown command is executed, all buffers allocated to the WRED mega-pool are returned to the default mega-pool and all WRED queues are returned either to their default buffer pool or their specified named buffer pool.

The no form of the command immediately restores the default min and max percentage values for sizing the WRED mega-pool.

Default 

buffer-allocation min 25.00 max 25.00

Parameters 
min percentage
Specifies that the required keyword defines the minimum percentage of total egress forwarding plane queue buffers that will be applied to the WRED mega-pool. The value given for percentage must be less than or equal to the value given for the max percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
Values—
0.00 to 99.99

 

Default—
25.00
max percentage
Specifies that the required keyword defines the maximum percentage of total egress forwarding plane queue buffers that may be applied to the WRED mega-pool. The value given for percentage must be equal to or greater than the value given for the min percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
Values—
0.01 to 99.99

 

Default—
25.00

resv-cbs

Syntax 
resv-cbs min percentage max percentage
no resv-cbs
Context 
config>card>fp>egress>wred-queue-control
Description 

This command defines the amount of buffers within the WRED mega-pool that will be set aside for WRED queues operating within their configured CBS thresholds. Note that the min percentage and max percentage parameters must be set to the same value. The forwarding plane protects against WRED queue buffer starvation by setting aside a portion of the buffers within the WRED mega-pool. The WRED queue CBS threshold defines when a WRED queue requests buffers from reserved portion of the WRED mega-pool and when it starts requesting buffers from the shared portion of the mega-pool. With proper oversubscription provisioning, this prevents a seldom active queue from being denied a buffer from the mega-pool when the shared portion of the mega-pool is congested.

The WRED mega-slope reserve CBS size is controlled in the same manner as the overall sizing of the WRED mega-pool. A min and max parameter is provided to scope the range that the reserved portion based on percentages of the WRED mega-pool current size.

The no form of the command immediately restores the default min and max percentage values for sizing the WRED mega-pool CBS reserve.

Default 

resv-cbs min 25.00 max 25.00

Parameters 
min percentage
Specifies that the required keyword defines the minimum percentage of the WRED mega-pool buffers that will be applied to the CBS reserve. The value given for percentage must be less than or equal to the value given for the max percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
Values—
0.00 to 99.99

 

Default—
25.00
max percentage
Specifies that the required keyword defines the maximum percentage of the IOM3-XP WRED mega-pool buffers that may be applied to the CBS reserve. The value given for percentage must be greater than or equal to the value given for the min percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
Values—
0.01 to 99.99

 

Default—
25.00

slope-policy

Syntax 
slope-policy slope-policy-name
no slope-policy
Context 
config>card>fp>egress>wred-queue-control
Description 

This command configures WRED slopes within the WRED mega-pool. The WRED slopes in the WRED mega-pool are used when WRED queues are requesting buffers from the mega-pool while they are over their CBS threshold. Once over the CBS threshold, the WRED queue stops receiving buffers from the CBS reserve in the mega-pool and starts competing for buffers in the shared portion of the mega-pool. If the packet resulting in the buffer request is inplus-profile, the packet will be associated with the highplus-slope. In-profile packets are associated with the high slope. Out-of-profile packets are associated with the low slope. Exceed-profile packets are associated with the exceed slope. While the queue is within its CBS threshold, the slopes are ignored.

Within the defined slope-policy, each slope is enabled or disabled (no shutdown or shutdown) and each slope’s geometry is defined as percentages of shared portion depth. If a slope is shutdown, the related traffic uses the minimum of the queue MBS and egress WRED megapool size as a drop tail.

The slope-policy also defines the time average factor (TAF) value that is used to determine how the pool’s weighted average depth is calculated. The higher the factor, the slower the average depth tracks the actual pool depth.

The no form of the command restores the default slope policy to the WRED mega-pool.

Default 

slope-policy default

Parameters 
slope-policy-name—
Specifies which slope policy the system should apply to the WRED mega-pool. When slope-policy is not executed, the WRED mega-pool will use the default slope policy. The defined slope policy must already exist or the command will fail. 32 characters maximum.

shutdown

Syntax 
[no] shutdown
Context 
config>card>fp>egress>wred-queue-control
Description 

This command enables or disables egress WRED queue support on the forwarding plane. By default, WRED queue support is disabled (shutdown). While disabled, the various wred-queue-control commands may be executed on the forwarding plane and SAP egress QoS policies and egress queue group templates with wred-queue enabled may be applied to egress SAPs and port, respectively. The forwarding plane will allocate WRED pools to the WRED queues and the appropriate WRED mega-pool size and CBS reserve size will be calculated, but the WRED mega-pool will be empty and all buffers will be allocated to the default mega-pool. Each WRED queue will be mapped to either its appropriate default pool or an explicitly defined named pool.

Once the no shutdown command is executed, the calculated WRED mega-pool buffers will be moved from the default mega-pool to the WRED mega-pool. The WRED mega-pool CBS reserve size will be applied and each egress WRED queue will be moved from its default mega-pool buffer pool to its WRED pool within the WRED mega-pool hierarchy.

The no form of the command enables WRED queuing on an egress forwarding plane.

Default 

shutdown

hi-bw-mcast-src

Syntax 
hi-bw-mcast-src [alarm] [group group-id] [default-paths-only]
no hi-bw-mcast-src
Context 
config>card>fp
Description 

This command designates the forwarding plane as a high-bandwidth IP multicast source, expecting the ingress traffic to include high-bandwidth IP multicast traffic. When configured, the system attempts to allocate a dedicated multicast switch fabric plane (MSFP) to the forwarding plane. If a group is specified, all FPs in the group will share the same MSFP. If the alarm parameter is specified and the system cannot allocate a dedicated MSFP to the new group or FP, the FPs will be brought online and generate an event (SYSTEM: 2052 - tmnxChassisHiBwMulticastAlarm). Similarly, if during normal operation there is a failure or removal of resources, an event will be generated if the system cannot maintain separation of MSFPs for the MDAs.

The no form of the command removes the high-bandwidth IP multicast source designation from the forwarding plane.

Default 

no hi-bw-mcast-src

Parameters 
alarm—
Enables event generation if the MDA is required to share an MSFP with another MDA that is in a different group. MDAs within the same group sharing an MSFP will not cause this alarm.
group-id
Specifies the logical MSFP group for the MDA. MDAs configured with the same group-id will be placed on the same MSFP.
Values—
0 to 32 (A value of 0 removes the MDA from the group.)

 

Default—
By default, “none” is used, and the system will attempt to assign a unique MSFP to the MDA.
default-paths-only—
When this parameter is specified the system will only attempt to allocate the two default paths (one high priority and one low priority) to dedicated MSFPs.

ingress

Syntax 
ingress
Context 
config>card>fp
Description 

This command enables access to the ingress fp CLI context.

access

Syntax 
access
Context 
config>card>fp>ingress
Description 

This CLI node contains the access forwarding-plane parameters.

queue-group

Syntax 
queue-group queue-group-name instance instance-id [create]
no queue-group queue-group-name instance instance-id
Context 
config>card>fp>ingress>access
Description 

This command creates an instance of a named queue group template on the ingress forwarding plane of a given IOM/IMM. The queue-group-name and instance instance-id are mandatory parameters when executing the command.

The named queue group template can contain only policers. If it contains queues, then the command will fail.

The no form of the command deletes a specific instance of a queue group.

Parameters 
queue-group-name—
Specifies the name of the queue group template to be instantiated on the forwarding plane of the IOM/IMM, up to 32 characters in length. The queue-group-name must correspond to a valid ingress queue group template name, configured under config>qos>queue-group-templates.
instance-id—
Specifies the instance of the named queue group to be created on the IOM/IMM ingress forwarding plane.
Values—
1 to 65535

 

create—
Keyword used to associate the queue group. The create keyword requirement can be enabled/disabled in the environment>create context.

accounting-policy

Syntax 
accounting-policy acct-policy-id
no accounting-policy
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description 

This command configures an accounting policy that can apply to a queue-group on the forwarding plane.

An accounting policy must be configured before it can be associated to an interface. If the accounting policy-id does not exist, an error is returned.

Accounting policies associated with service billing can only be applied to SAPs. The accounting policy can be associated with an interface at a time.

The no form of this command removes the accounting policy association from the queue-group.

Default 

No accounting policies are specified by default. You must explicitly specify a policy. If configured, the accounting policy configured as the default is used.

Parameters 
acct-policy-id—
Specifies the name of the accounting policy to use for the queue-group.
Values—
1 to 99

 

collect-stats

Syntax 
[no] collect-stats
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description 

This command enables the collection of accounting and statistical data for the queue group on the forwarding plane. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued, the statistics are still accumulated, however, the CPU does not obtain the results and write them to the billing file. If the collect-stats command is issued again (enabled), then the counters written to the billing file will include the traffic collected while the no collect-stats command was in effect.

Default 

no collect-stats

policer-control-override

Syntax 
policer-control-override [create]
no policer-control-override
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description 

This command configures policer control overrides.

Parameters 
create—
Keyword required to create a new policer control override instance.

max-rate

Syntax 
max-rate {rate | max}
no max-rate
Context 
config>card>fp>ingress>acc>qgrp>policer-ctrl-over
config>card>fp>ingress>network>qgrp>policer-ctrl-over
Description 

This command defines the parent policer’s PIR leaky bucket’s decrement rate. A parent policer is created for each time the policer-control-policy is applied to either a SAP or subscriber instance. Packets that are not discarded by the child policers associated with the SAP or subscriber instance are evaluated against the parent policer’s PIR leaky bucket.

For each packet, the bucket is first decremented by the correct amount based on the decrement rate to derive the current bucket depth. The current depth is then compared to one of two discard thresholds associated with the packet. The first discard threshold (discard-unfair) is applied if the FIR (Fair Information Rate) leaky bucket in the packet’s child policer is in the confirming state. The second discard threshold (discard-all) is applied if the child policer's FIR leaky bucket is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet.

If the result is “conform,” the bucket depth is increased by the size of the packet (plus or minus the per-packet-offset setting in the child policer) and the packet is not discarded by the parent policer. If the result is “violate,” the bucket depth is not increased and the packet is discarded by the parent policer. When the parent policer discards a packet, any bucket depth increases (PIR, CIR and FIR) in the parent policer caused by the packet are canceled. This prevents packets that are discarded by the parent policer from consuming the child policers PIR, CIR and FIR bandwidth.

The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.

The no version of the command returns the policer-control-policy’s parent policer maximum rate to max.

Default 

max-rate max

Parameters 
rate
Specifies that a kilobits-per-second value is mutually exclusive with the max keyword. The kilobits-per-second value must be defined as an integer that represents the number of kilobytes that the parent policer will be decremented per second. The actual decrement is performed per packet based on the time that has elapsed since the last packet associated with the parent policer.
Values—
0 to 2000000000

 

max—
The max keyword is mutually exclusive with defining a kilobits-per-second value. When max is specified, the parent policer does not enforce a maximum rate on the aggregate throughput of the child policers. This is the default setting when the policer-control-policy is first created and is the value that the parent policer returns to when no max-rate is executed. In order for the parent policer to be effective, a kilobits-per-second value should be specified.

priority-mbs-thresholds

Syntax 
priority-mbs-thresholds
Context 
config>card>fp>ingress>access>queue-group>policer-control-override
config>card>fp>ingress>network>queue-group>policer-control-override
Description 

This command contains the root arbiter parent policer’s min-thresh-separation command and each priority level’s mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority sensitive rate-based discards within the root arbiter’s parent policer.

The priority-mbs-thresholds CLI node always exists and does not need to be created.

min-thresh-separation

Syntax 
min-thresh-separation size [bytes | kilobytes]
no min-thresh-separation
Context 
config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds
config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds
Description 

This command defines the minimum required separation between each in-use discard threshold maintained for each parent policer context associated with the policer-control-policy. The min-thresh-separation value may be overridden on each SAP or sub-profile to which the policy is applied.

The system uses the default or specified min-thresh-separation value in order to determine the minimum separation required between each of the of the parent policer discard thresholds. The system enforces the minimum separation based on the following behavior in two ways. The first is determining the size of the shared-portion for each priority level (when the mbs-contribution command’s optional fixed keyword is not specified):

  1. When a parent policer instance’s priority level has less than two child policers associated, the shared-portion for the level will be zero.
  2. When a parent policer instance’s priority level has two or more child policers associated, the shared-portion for the level will be equal to the current value of min-thresh-separation.

The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:

  1. When a parent policer instance’s priority level has no child policers associated, the fair-portion for the level will be zero.
  2. When a parent policer instance’s priority level has one child policer associated, the fair-portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value.
  3. When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following:
    1. min-thresh-separation value
    2. The priority level’s mbs-contribution value less min-thresh-separation value

When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS. While the system will continue to track child policer associations with the parent policer priority levels, the association counters will have no effect. Instead the following rules will be used to determine a fixed priority level’s shared-portion and fair-portion:

  1. If a fixed priority level’s mbs-contribution value is set to zero, both the shared-portion and fair-portion will be set to zero
  2. If the mbs-contribution value is not set to zero:
    1. The shared-portion will be set to the current min-thresh-separation value
    2. The fair-portion will be set to the maximum of the following:
      1. min-thresh-separation value
      2. mbs-contribution value less min-thresh-separation value

Each time the min-thresh-separation value is modified, the thresholds for all instances of the parent policer created through association with this policer-control-policy are reevaluated except for parent policer instances that currently have a min-thresh-separation override.

Determining the Correct Value for the Minimum Threshold Separation Value

The minimum value for min-thresh-separation should be set equal to the maximum size packet that will be handled by the parent policer. This ensures that when a lower priority packet is incrementing the bucket, the size of the increment will not cause the bucket's depth to equal or exceed a higher priority threshold. It also ensures that an unfair packet within a priority level cannot cause the PIR bucket to increment to the discard-all threshold within the priority.

When evaluating maximum packet size, each child policer’s per-packet-offset setting should be taken into consideration. If the maximum size packet is 1518 bytes and a per-packet-offset parameter is configured to add 20 bytes per packet, min-thresh-separation should be set to 1538 due to the fact that the parent policer will increment its PIR bucket using the extra 20 bytes.

In most circumstances, a value larger than the maximum packet size is not necessary. Management of priority level aggregate burst tolerance is intended to be implemented using the priority level mbs-contribution command. Setting a value larger than the maximum packet size will not adversely affect the policer performance, but it may increase the aggregate burst tolerance for each priority level.

One thing to note is that a priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state. The fair burst amount for a priority level is defined using the mbs-contribution command.

The no form of this command returns the policy’s min-thresh-separation value to the default value. This has no effect on instances of the parent policer where min-thresh-separation is overridden unless the override is removed.

Default 

no min-thresh-separation

Parameters 
size
Specifies that the size parameter is required when executing the min-thresh-separation command. It is expressed as an integer and specifies the shared portion in bytes or kilobytes that is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is the assumed value. Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.
Values—
0 to 16777216

 

bytes | kilobytes—
Specifies that the bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.

The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.

Values—
bytes or kilobytes

 

Default—
kilobytes

priority

Syntax 
[no] priority level
Context 
config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds
config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds
Description 

The priority level command contains the mbs-contribution configuration command for a given strict priority level. Eight levels are supported numbered 1 through 8 with 8 being the highest strict priority.

Each of the eight priority CLI nodes always exists and do not need to be created. While parameters exist for each priority level, the parameters are only applied when the priority level within a parent policer instance is currently supporting child policers.

Parameters 
level—
Specifies the priority level.
Values—
1 to 8

 

mbs-contribution

Syntax 
mbs-contribution size [bytes | kilobytes]
no mbs-contribution
Context 
config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds>priority
config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds>priority
Description 

This command configures the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs-contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level. The shared-portion and fair-portions for each priority level are then used by the system to calculate each priority level’s discard-unfair threshold and discard-all threshold.

The value for a priority level’s mbs-contribution within the policer-control-policy may be overridden on the SAP or subscriber sub-profile where the policy is applied in order to allow fine tuning of the discard-unfair and discard-all thresholds relevant to the needs of the local child policers on the object.

Accumulative Nature of Burst Tolerance for a Parent Policer Priority Level

When defining mbs-contribution, the specified size may only be a portion of the burst tolerance associated with the priority level. The packets associated with the priority level share the burst tolerance of lower within the parent policer. As the parent policer PIR bucket depth increases during congestion, the lower priority packets eventually experience discard based on each priority’s discard-unfair and discard-all thresholds. Assuming congestion continues once all the lower priority packets have been prevented from consuming bucket depth, the burst tolerance for the priority level will be consumed by its own packets and any packets associated with higher priorities.

The Effect of Fair and Unfair Child Policer Traffic at a Parent Policer Priority Level

The system continually monitors the offered rate of each child policer on each parent policer priority level and detects when the policer is in a congested state (the aggregate offered load is greater than the decrement rate defined on the parent policer). As previously stated, the result of congestion is that the parent policer's bucket depth will increase until it eventually hovers around either a discard-unfair or discard-all threshold belonging to one of the priority levels. This threshold is the point where enough packets are being discarded that the increment rate and decrement rate begin to even out. If only a single child policer is associated to the priority level, the discard-unfair threshold is not used since fairness is only applicable when multiple child policers are competing at the same priority level.

When multiple child policers are sharing the congested priority level, the system uses the offered rates and the parenting parameters of each child to determine the fair rate per child when the parent policer is unable to meet the bandwidth needs of each child. The fair rate represents the amount of bandwidth that each child at the priority level should receive relative to the other children at the same level according to the policer control policy instance managing the child policers. This fair rate is applied as the decrement rate for each child’s FIR bucket. Changing a child’s FIR rate does not modify the amount of packets forwarded by the parent policer for the child’s priority level. It simply modifies the forwarded ratio between the children on that priority level. Since each child FIR bucket has some level of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard-all threshold.

This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels. In essence, the system ensures that for each iteration of the child FIR rate calculation, the sum of the child FIR decrement rates plus the sum of the higher priority traffic increment rates equals the parent policers decrement rate. This means that dynamic amounts of higher priority traffic can be ignored when sizing a lower priority’s fair aggregate burst tolerance. Consider the following:

  1. The parent policer decrement rate is set to 20 Mb/s (max-rate 20,000).
  2. A priority level’s fair burst size is set to 30 kbytes (mbs-contribution 30 kilobytes).
  3. Higher priority traffic is currently taking 12 Mb/s.
  4. The priority level has three child policers attached.
  5. Each child’s PIR MBS is set to 10 kbytes, which makes each child’s FIR MBS 10 kbytes.
  6. The children want 10 Mb/s, but only 8 Mb/s is available,
  7. Based on weights, the children's FIR rates are set as follows:

    FIR Rate

    FIR MBS

    Child 1

    4 Mb/s

    10 kbytes

    Child 2

    3 Mb/s

    10 kbytes

    Child 3

    1 Mb/s

    10 kbytes

The 12 Mb/s of the higher priority traffic and the 8 Mb/s of fair traffic equal the 20 Mb/s decrement rate of the parent policer.

It is clear that the higher priority traffic is consuming 12 Mb/s of the parent policer’s decrement rate, leaving 8 Mb/s of decrement rate for the lower priority’s fair traffic.

  1. The burst tolerance of child 1 is based on 10 kbytes above 4 Mb/s,
  2. The burst tolerance of child 2 is based on 10 kbytes above 3 Mb/s,
  3. The burst tolerance of child 3 is based on 10 kbytes above 1 Mb/s.

If all three children burst simultaneously (unlikely), they will consume 30 kbytes above 8 Mb/s. This is the same as the remaining decrement rate after the higher priority traffic.

Parent Policer Total Burst Tolerance and Downstream Buffering

The highest in-use priority level’s discard-all threshold is the total burst tolerance of the parent policer. In some cases the parent policer represents downstream bandwidth capacity and the max-rate of the parent policer is set to prevent overrunning the downstream bandwidth. The burst tolerance of the parent policer defines how much more traffic may be sent beyond the downstream scheduling capacity. In the worst case scenario, when the downstream buffering is insufficient to handle the total possible burst from the parent policer, downstream discards based on lack of buffering may occur. However, in all likelihood, this is not the case.

In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present.

Configuring a Priority Level's MBS Contribution Value

In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer. This ensures that even in the absolute worst case where all the lower priority levels are simultaneously bursting to the maximum capacity of each child, enough burst tolerance for the priority’s children will exist if they also burst to their maximum capacity.

Since simply adding up all the child policer’s PIR MBS values may result in large overall burst tolerances that are not ever likely to be needed, you should consider some level of burst oversubscription when configuring the mbs-contribution value for each priority level. The amount of oversubscription should be determined based on the needs of each priority level.

Using the Fixed Keyword to Create Deterministic Parent Policer Discard Thresholds

In the default behavior, the system ignores the mbs-contribution values for a priority level on a subscriber or SAP parent policer when a child policer is not currently associated with the level. This prevents additional burst tolerance from being added to higher priority traffic within the parent policer.

This does cause fluctuations in the defined threshold values when child policers are added or removed from a parent policer instance. If this behavior is undesirable, the fixed keyword may be used which causes the mbs-contribution value to always be included in the calculation of parent policer’s discard thresholds. The defined mbs-contribution value may be overridden on a subscriber sla-profile or on a SAP instance, but the fixed nature of the contribution cannot be overridden.

If the defined mbs-contribution value for the priority level is zero, the priority level will have no effect on the parent policer’s defined discard thresholds. A packet associated with the priority level will use the next lower priority level’s discard-unfair and discard-all thresholds.

Default 

no mbs-contribution

The no mbs-contribution command returns the policy’s priority level’s MBS contribution to the default value. When changed, the thresholds for the priority level and all higher priority levels for all instances of the parent policer will be recalculated.

Parameters 
size
Specifies that the size parameter is required when executing the mbs-contribution command. It is expressed as an integer and specifies the priority’s specific portion amount of accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed. Setting this value has no effect on parent policer instances where the priority level’s mbs-contribution value has been overridden. Clearing an override on parent policer instance causes this value to be enforced.
Values—
0 to 16777216

 

bytes, kilobytes—
Specifies that the bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in bytes.

The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.

Default—
kilobytes

policer-control-policy

Syntax 
policer-control-policy policer-control-policy-name
no policer-control-policy
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description 

This command configures an policer-control policy that can apply to a queue-group on the forwarding plane.

The no form of this command removes the policer-control policy association from the queue-group.

Default 

no policer-control-policy

Parameters 
policer-control-policy-name—
Specifies the name of the policer-control policy to use for the queue-group. The name can be up to 32 characters long.

policer-override

Syntax 
[no] policer-override
Context 
config>card>fp>ingress>access>queue-group
config>card>fp>ingress>network>queue-group
Description 

This command, within the SAP ingress or egress contexts, is used to create a CLI node for specific overrides to one or more policers created on the SAP through the sap-ingress or sap-egress QoS policies.

The no form of the command removes any existing policer overrides.

Default 

no policer-override

policer

Syntax 
policer policer-id [create]
no policer policer-id
Context 
config>card>fp>ingress>access>qgrp>policer-over
config>card>fp>ingress>network>qgrp>policer-over
Description 

This command creates, modifies or deletes a policer. Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue ID space, allowing both a queue and a policer to share the same ID. The sap-ingress policy may have up to 32 policers (numbered 1 through 32) may be defined while the sap-egress QoS policy supports a maximum of 8 (numbered 1 through 8). While a policer may be defined within a QoS policy, it is not actually created on SAPs or subscribers associated with the policy until a forwarding class is mapped to the policer’s ID.

All policers must be created within the QoS policies. A default policer is not created when a sap-ingress or sap-egress QoS policy is created.

Once a policer is created, the policer's metering rate and profiling rates may be defined as well as the policer's maximum and committed burst sizes (MBS and CBS respectively). Unlike queues which have dedicated counters, policers allow various stat-mode settings that define the counters that will be associated with the policer. Another supported feature—packet-byte-offset—provides a policer with the ability to modify the size of each packet based on a defined number of bytes.

Once a policer is created, it cannot be deleted from the QoS policy unless any forwarding classes that are mapped to the policer are first moved to other policers or queues.

The system will allow a policer to be created on a SAP QoS policy regardless of the ability to support policers on objects where the policy is currently applied. The system only scans the current objects for policer support and sufficient resources to create the policer when a forwarding class is first mapped to the policer ID. If the policer cannot be created due to one or more instances of the policy not supporting policing or having insufficient resources to create the policer, the forwarding class mapping fails.

The no form of this command deletes a policer from a sap-ingress or sap-egress QoS policy. The specified policer cannot currently have any forwarding class mappings for the removal of the policer to succeed. It is not necessary to actually delete the policer ID for the policer instances to be removed from SAPs or subscribers associated with the QoS policy once all forwarding classes have been moved away from the policer. It is automatically deleted from each policing instance although it still appears in the QoS policy.

Parameters 
policer-id
Specifies that the policer-id must be specified when executing the policer command. If the specified ID already exists, the system enters that policer's context to allow the policer’s parameters to be modified. If the ID does not exist and is within the allowed range for the QoS policy type, a context for the policer ID will be created (depending on the system's current create keyword requirements which may require the create keyword to actually add the new policer ID to the QoS policy) and the system will enter that new policer’s context for possible parameter modification.
Values—
1 to 32

 

cbs

Syntax 
cbs {size [bytes | kilobytes] | default}
no cbs
Context 
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description 

This command configures the policer’s CIR leaky bucket’s exceed threshold. The CIR bucket’s exceed threshold represents the committed burst tolerance allowed by the policer. If the policer’s forwarding rate is equal to or less than the policer’s defined CIR, the CIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the forwarding rate increases beyond the profiling rate, the amount of data allowed to be in-profile above the rate is capped by the threshold.

The policer’s cbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command returns the policer to its default CBS size.

Parameters 
size
Specifies that the size parameter is required when specifying cbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
bytes—
When bytes is defined, the value given for size is interpreted as the queue’s CBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue’s CBS value given in kilobytes.
Values—
0 to 16777216

 

Default—
kilobyte
default—
Specifying the keyword default sets the CBS to its default value.

mbs

Syntax 
mbs {size [bytes | kilobyte] | default}
no mbs
Context 
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description 

This command configures the policer’s PIR leaky bucket’s high priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold. For ingress, trusted in-profile packets and un-trusted high priority packets use the policer’s high priority violate threshold while trusted out-of-profile and un-trusted low priority packets use the policer’s low priority violate threshold. At egress, in-profile packets use the policer’s high priority violate threshold and out-of-profile packets use the policer’s low priority violate threshold.

The PIR bucket’s violate threshold represent the maximum burst tolerance allowed by the policer. If the policer’s offered rate is equal to or less than the policer’s defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance defined by high-prio-only is available for the higher priority traffic.

The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command returns the policer to its default MBS size.

Parameters 
size
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional bytes and kilobytes keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
bytes—
When bytes is defined, the value given for size is interpreted as the policer’s MBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the policer’s MBS value given in kilobytes.
Values—
0 to 16777216

 

default—
Specifying the keyword default sets the MBS to its default value.

packet-byte-offset

Syntax 
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context 
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description 

This command modifies the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism the can be used to either add downstream frame encapsulation or remove portions of packet headers. Both the policing metering and profiling throughput is affected by the offset as well as the stats associated with the policer.

When child policers are adding to or subtracting from the size of each packet, the parent policer’s min-thresh-separation value should also need to be modified by the same amount.

The policer’s packet-byte-offset defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no version of this command removes per packet size modifications from the policer.

Parameters 
add-bytes—
The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is increased by the amount being added to the size of each packet.
Values—
1 to 31

 

sub-bytes—
The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When b is defined the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling and accounting purposes. From the policer’s perspective, the maximum packet size is reduced by the amount being subtracted from the size of each packet. Note that the minimum resulting packet size used by the system is 1 byte.
Values—
0 to 32

 

rate

Syntax 
rate {rate | max} [cir {max | rate}]
no rate
Context 
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description 

This command configures the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on the each packets size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches it's exceed (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are used to configure the policer’s PIR and CIR thresholds.

If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket, the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR bucket rate. If the packet is violating the PIR, the packet is marked red and will be discarded. If the packet is not red, it may be green or yellow based on the conforming or exceeding state from the CIR bucket.

When a packet is red neither the PIR or CIR bucket depths are incremented by the packets size. When the packet is yellow the PIR bucket is incremented by the packet size, but the CIR bucket is not. When the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that conforming packets impact the bucket depth while exceeding or violating packets do not.

The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.

By default, the policer’s metering rate is max and the profiling rate is 0 kb/s (all packets out-of-profile).

The rate settings defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command restores the default metering and profiling rate to a policer.

Parameters 
{rate | max}
Specifying the keyword max or an explicit rate parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The kilobits-per-second value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.
Values—
max or 1 to 2000000000

 

cir {max | rate}
The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit rate parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 kb/s. The kilobits-per-second value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.
Values—
max or 0 to 2000000000

 

stat-mode

Syntax 
stat-mode stat-mode
no stat mode
Context 
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description 

This command configures the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, high priority or low priority) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the large number of policers, it is not economical to allocate counters in the forwarding plane for all possible offered packet types and output conditions. Many policers will not be configured with a CIR profiling rate and not all policers will receive explicitly profiled offered packets. The stat-mode command allows provisioning of the number of counters each policer requires and how the offered packet types and output conditions should be mapped to the counters.

While a no-stats mode is supported which prevents any packet accounting, the use of the policer’s parent command requires at the policer's stat-mode to be set at least to the minimal setting so that offered stats are available for the policer's Fair Information Rate (FIR) to be calculated. Once a policer has been made a child to a parent policer, the stat-mode cannot be changed to no-stats unless the policer parenting is first removed.

Each time the policer’s stat-mode is changed, any previous counter values are lost and any new counters are set to zero.

Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. You can view the total/allocated/free stats by using the tools dump system-resources command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.

The default stat-mode when a policer is created within the policy is minimal.

The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.

The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.

Parameters 
See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for details on the policer stat-mode parameters.

mcast-path-management

Syntax 
mcast-path-management
Context 
config>card>fp>ingress
Description 

This CLI node contains the forwarding plane settings for ingress multicast path management. Enter the node to configure the bandwidth-policy and the administrative state of ingress multicast path management.

bandwidth-policy

Syntax 
bandwidth-policy policy-name
no bandwidth-policy
Context 
config>card>fp>ingress>mcast-path-management
Description 

This command explicitly associates a bandwidth policy to a forwarding plane or MDA. The bandwidth policy defines the dynamic rate table and the multicast paths bandwidth and queuing parameters.

If a bandwidth policy is not explicitly associated with a forwarding plane or MDA, the default bandwidth policy is used when ingress multicast path management is enabled.

The no form of the command removes an explicit bandwidth policy from a forwarding plane or MDA and restores the default bandwidth policy.

Parameters 
policy-name—
The policy-name parameter is required and defines the bandwidth policy that should be associated with the MDA or forwarding plane for ingress multicast path management. If the policy name does not exist, the bandwidth-policy command will fail. The name can be up to 32 characters long.
Values—
Any existing bandwidth policy name.

 

Default—
default

queue-group

Syntax 
queue-group queue-group-name instance instance-id [create]
no queue-group queue-group-name instance instance-id
Context 
config>card>fp>ingress>network
Description 

This command creates a queue-group instance in the network ingress context of a forwarding plane.

Only a queue-group containing policers can be instantiated. If the queue-group template contains policers and queues, the queues are not instantiated. If the queue-group contains queues only, the instantiation in the data path is failed.

One or more instances of the same policer queue-group name and/or a different policer queue-group name can be created on the network ingress context of a forwarding plane.

The queue-group-name must be unique within all network ingress and access ingress queue groups in the system. The queue-group instance-id must be unique within the context of the forwarding plane.

The no version of this command deletes the queue-group instance from the network ingress context of the forwarding plane.

Parameters 
queue-group-name—
Specifies the name of the queue group template up to 32 characters.
instance-id
Specifies the identification of a specific instance of the queue-group.
Values—
1 to 65535

 

create—
Keyword used to create the queue-group instance.

ingress-buffer-allocation

Syntax 
ingress-buffer-allocation percentage
no ingress-buffer-allocation
Context 
config>card>fp
Description 

This command allows the user to configure an ingress buffer allocation percentage per forwarding plane from 20.00% to 80.00%. Ingress buffer allocation applies to user-accessible buffers (total buffers less those reserved for system use).

The ingress buffer allocation percentage determines how much of the user-accessible buffers will be available for ingress purposes. The remaining buffers will be available for egress purposes.

This command is supported on all 50G FP2-based and 100G/200G FP3-based hardware. It is not supported on other FP2 or FP3-based hardware, nor on FP4-based hardware.

The no form of this command returns the ingress buffer allocation to the default value.

Default 

ingress-buffer-allocation 50.00

Parameters 
percentage—
Specifies the buffer allocation percentage.
Values—
20.00 to 80.00

 

policy-accounting

Syntax 
policy-accounting limit
no policy-accounting
Context 
config>card>fp
Description 

This command allows the user to configure the number of stats resources for policy accounting for the forwarding plane.

Default 

no policy-accounting

Parameters 
limit—
Specifies the number of stats resources.
Values—
1000 to 128000

 

stable-pool-sizing

Syntax 
[no] stable-pool-sizing
Context 
config>card>fp
Description 

This command provides a stable buffer pool allocation environment for all default port buffer pools on a forwarding plane. This stable environment is provided at the expense of optimal buffer allocation between the various port buffer pools. Normally, port pools are sized according to a ports relative bandwidth with other ports and the ability of a port to use pool buffers. As an example, on a forwarding plane with two potential MDAs and only one equipped, the normal behavior is to provide all available default pool buffers to the ports on the currently equipped MDA. If a second MDA is equipped in the future, buffers are freed from the existing MDA and provided to the ports on the new MDA. Stable pool sizing alters this behavior by reserving buffers for both MDAs whether they are equipped or not thus preventing a resizing event when an MDA is equipped. In addition, existing ports on a module always receive their maximum bandwidth share of buffers independent on any sub-rate condition that may currently exist. This provides a stable amount of buffers to other ports on the module independent of link or configuration events that may occur on the port.

Stable pool sizing preserves the ability to modify the effective bandwidth used to determine a port’s relative share of the available buffers through the use of the ing-percentage-of-rate and egr-percentage-of-rate commands under the port configuration. Changing the values associated with these commands will cause a reevaluation of buffer distribution and thus a possible resizing of pools on each port within the module. These commands have no effect on ports associated with other modules on the forwarding plane.

Stable pool sizing is mutually exclusive with card level named-pool-mode. Named pool mode must be disabled and not operational before stable pool sizing can be enabled. Once stable pool sizing is enabled on any forwarding plane on a card, named-pool-mode cannot be enabled for that card.

Stable pool sizing may be enabled (while named pool mode is disabled) or disabled at any time on a forwarding plane. The system will dynamically change the pool sizes according to the stable pool sizing state.

When a port connector breakout is configured, its ports will be included in the stable pool sizing calculation. Consequently, adding or removing a port connector breakout to or from the configuration will cause the buffer pool allocation to be recalculated even when stable pool sizing is enabled.

The no stable-pool-sizing command disables stable pool sizing on a forwarding plane. Existing buffer pools will be resized according to normal pool sizing behavior.

2.20.2.9. MACsec Commands

macsec

Syntax 
macsec
Context 
config
Description 

This command enables the context for MACsec configuration. The MACsec MKA profile can be configured under this command.

connectivity-association

Syntax 
connectivity-association ca-name [create]
no connectivity-association ca-name
Context 
config>macsec
Description 

This command configures a connectivity association. MACsec connectivity associations are applied to a port dot1x configuration to enable MACsec on that port.

The no form of this command removes the connectivity association.

Parameters 
ca-name—
The name of the connectivity association, a string up to 32 characters long.
create—
Mandatory while creating an entry.

cipher-suite

Syntax 
cipher-suite cipher-suite
no cipher-suite
Context 
config>macsec>connectivity-association
Description 

This command configures encryption of datapath PDUs. When all parties in the Connectivity Association (CA) have the SAK, they use the above algorithm in conjunction with the SAK to encrypt the datapath PDUs.

The XPN 64 bit (extended packet number) can be used for higher rate ports like 10 gige to minimize the window rollover and renegotiation of the SAK.

The no form of this command disables encryption of datapath PDUs.

Default 

cipher-suite gcm-aes-128

Parameters 
cypher-suite—
Specifies the algorithm.
Values—
gcm-aes-128 — algorithm is used for control plain encryption
gcm-aes-256 — algorithm is used for control plain encryption
gcm-aes-xpn-128 — algorithm with extended packet number is used for control plain encryption
gcm-aes-xpn-256 — algorithm with extended packet number is used for control plain encryption

 

clear-tag-mode

Syntax 
clear-tag-mode clear-tag-mode
no clear-tag-mode
Context 
config>macsec>connectivity-association
Description 

This command puts 802.1Q tags in clear "before sectag". There are two modes: single tag and dual-tag.

Table 40 explains the encrypted dot1q and QinQ packet format when clear-tag-mode single-tag or dual-tag is configured.

The no form of this command will put all dot1q tags after sectag and encrypt the tags.

Table 40:  Encrypted Dot1q and QinQ Packet Format 

Unencrypted format

Clear-tag-mode

Pre-encryption (Tx)

Pre-decryption (Rx)

Single tag (dot1q)

single-tag

DA, SA, TPID, VID, Etype

DA, SA, TPID, VID, SecTag

Single tag (dot1q)

dual-tag

DA, SA, TPID, VID, Etype

DA, SA, TPID, VID, SecTag

Double tag (q-in-q)

single-tag

DA, SA, TPID1, VID1, IPID2, VID2, Etype

DA, SA, TPID1, VID1, SecTag

Double tag (QinQ)

dual-tag

DA, SA, TPID1, VID1, IPID2, VID2, Etype

DA, SA, TPID1, VID1, IPID2, VID2, SecTag

Default 

no clear-tag-mode

Parameters 
clear-tag-mode —
Specifies the clear tag mode.
Values—
single-tag, dual-tag

 

description

Syntax 
description description
no description
Context 
config>macsec>connectivity-association
Description 

This command enters a description for connectivity association.

The no form of this command removes the connectivity association description.

Parameters 
description—
The brief explanation of the connectivity association, a string up to 80 characters long.

encryption-offset

Syntax 
encryption-offset encryption-offset
no encryption-offset
Context 
config>macsec>connectivity-association
Description 

This command specifies the offset of the encryption in MACsec packet.

The encryption-offset is distributed by MKA (Key-server) to all parties.

It is signaled via MACsec capabilities. There are four basic settings for this. Table 41 breaks down the settings.

Table 41:  MACsec Basic Settings 

Setting

Description

0

MACsec is not implemented

1

Integrity without confidentiality

2

The following are supported:

  1. Integrity without confidentiality
  2. Integrity and confidentiality with a confidentiality offset of 0

3  1

The following are supported:

  1. Integrity without confidentiality
  2. Integrity and confidentiality with a confidentiality offset of 0, 30, or 50

    Note:

  1. SR OS supports (3) Integrity without confidentiality and Integrity and confidentiality with a confidentiality offset of 0, 30, or 50.

The no form of this command rejects all arriving traffic whether MACsec is secured or not.

Default 

encryption-offset 0

Parameters 
encryption-offset—
Specifies the encryption.
Values—
0 — encrypt the entire payload
30 — leave the IPv4 header in clear
50 — leave the IPv6 header in clear

 

macsec-encrypt

Syntax 
[no] macsec-encrypt
Context 
config>macsec>connectivity-association
Description 

This command specifies all PDUs will be encrypted and authenticated (ICV payload).

The no form of this command specifies all PDUs are transmitted with clear text, but still authenticated and have the trailing ICV.

Default 

macsec-encrypt

replay-protection

Syntax 
[no] replay-protection
Context 
config>macsec>connectivity-association
Description 

Specifies the size of the replay protection window.

This command must be configured to force packet discard when it has detected a packet that is not within the replay-window-size.

When replay protection is enabled, the sequence of the ID number of the received packets are checked. If the packet arrives out of sequence and the difference between the packet numbers exceeds the replay window size, the packet is counted by the receiving port and then discarded. For example, if the replay protection window size is set to five and a packet assigned the ID of 1006 arrives on the receiving link immediately after the packet assigned the ID of 1000, the packet that is assigned the ID of 1006 is counted and discarded because it falls outside the parameters of the replay window size.

Replay protection is especially useful for fighting man-in-the-middle attacks. A packet that is replayed by a man-in-the-middle attacker on the Ethernet link will arrive on the receiving link out of sequence, so replay protection helps ensure the replayed packet is dropped instead of forwarded through the network.

Replay protection should not be enabled in cases where packets are expected to arrive out of order.

Default 

replay-protection

replay-window-size

Syntax 
replay-window-size number-of-packets
no replay-window-size
Context 
config>macsec>connectivity-association
Description 

This command specifies the size of the replay protection window.

This command must be configured to enable replay protection. When replay protection is enabled, the sequence of the ID number of received packets are checked. If the packet arrives out of sequence and the difference between the packet numbers exceeds the replay protection window size, the packet is dropped by the receiving port. For example, if the replay protection window size is set to five and a packet assigned the ID of 1006 arrives on the receiving link immediately after the packet assigned the ID of 1000, the packet that is assigned the ID of 1006 is dropped because it falls outside the parameters of the replay protection window.

Replay protection is especially useful for fighting man-in-the-middle attacks. A packet that is replayed by a man-in-the-middle attacker on the Ethernet link will arrive on the receiving link out of sequence, so replay protection helps ensure the replayed packet is dropped instead of forwarded through the network.

Replay protection should not be enabled in cases where packets are expected to arrive out of order.

When the number-of-packets variable is set to 0, all packets that arrive out-of-order are dropped.

The no form of this command reverts to the default.

Default 

replay-window-size 0

Parameters 
number-of-packets—
Specifies the window that the packets can arrive out of order.
Values—
0 to 4294967294

 

shutdown

Syntax 
[no] shutdown
Context 
config>macsec>connectivity-association
Description 

This command shuts down the CA profile. All ports using this profile will not transmit PDUs as this command shuts down the MACsec for this profile.

Default 

shutdown

static-cak

Syntax 
[no] static-cak
Context 
config>macsec>connectivity-association
Description 

This command allows the configuration of a Connectivity Association Key (CAK). A CAK is responsible for managing the MKA.

active-psk

Syntax 
active-psk active-pre-shared-key
no active-psk
Context 
config>macsec>conn-assoc>static-cak
Description 

This command specifies which pre-shared-key is the active transmitting pre-shared-key. If there are two pre-shared-keys configured, the arriving MACsec MKA can be decrypted via CAKs of both pre-shared keys; however, only the active-psk will be used for TX encryption of MKA PDUs.

Default 

active-psk 1

Parameters 
active-pre-shared-key—
Specifies the value of the pre-shared-key.
Values—
1 or 2

 

mka-key-server-priority

Syntax 
mka-key-server-priority priority
no mka-key-server-priority
Context 
config>macsec>conn-associ>static-cak
Description 

This command specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key server when MACsec is enabled using static connectivity association key (CAK) security mode.

The no form of this command disables the mka-key-server-priority.

Default 

mka-key-server-priority 16

Parameters 
priority—
Specifies the priority of the server.
Values—
0 to 255

 

pre-shared-key

Syntax 
pre-shared-key pre-shared-key-index [encryption-type encryption-type] [create]
no pre-shared-key pre-shared-key-index
Context 
config>macsec>conn-assoc>static-cak
Description 

This command specifies the pre-shared key used to enable MACsec using static connectivity association key (CAK) security mode. This command also specifies the encryption algorithm used for encrypting the SAK.

A pre-shared key includes a connectivity association key name (CKN) and a connectivity association key (CAK). The pre-shared key-the CKN and CAK-must match on both ends of a link.

A pre-shared key is configured on both devices at each end of point-to-point link to enable MACsec using static CAK security mode. The MACsec Key Agreement (MKA) protocol is enabled after the successful MKA liveliness negotiation.

The encryption-type is used for encrypting SAK and authentication of the MKA packet. The symmetric encryption key SAK (Security Association Key) needs to be encrypted (wrapped) via the above protocols. The AES key is derived via pre-shared-key.

The no form of this command removes the index.

Parameters 
pre-shared-key-index—
Specifies the index of this pre-shared-key.
Values—
1, 2

 

encryption-type—
Specifies the type of encryption.
Values—
aes-128-cmac, aes-256-cmac

 

create—
Mandatory while creating an entry.

cak

Syntax 
cak hex-string [hash | hash2]
no cak
Context 
config>macsec>conn-assoc>static-cak>pre-shared-key
Description 

Specifies the connectivity association key (CAK) for a pre-shared key. Two values are derived from CAK.

  1. KEK (Key Encryption Key), this is used to encrypt the MKA and SAK (symmetric key used for datapath PDUs) to be distributed between all members.
  2. ICK (Integrity Check Value), this is used to authenticate the MKA and SAK PDUs to be distributed between all members.

The no form of this command removes the value.

Parameters 
hex-string—
Specifies the value of the CAK.
Values—
up to 64 hexadecimal characters, 32 hexadecimal characters for 128-bit key and 64 hexadecimal characters for 256-bit key

 

hash
Keyword, specifying the hash scheme.
hash2
Keyword, specifying the hash scheme.

ckn

Syntax 
ckn hex-string
no ckn
Context 
config>macsec>conn-assoc>static-cak>pre-shared-key
Description 

Specifies the connectivity association key name (CKN) for a pre-shared key.

CKN is appended to the MKA for identification of the appropriate CAK by the peer.

The no form of this command.

Parameters 
hex-string—
Specifies the value of the CKN.
Values—
32 octets char (64 hex)

 

2.20.2.10. General Port Commands

port

Syntax 
[no] port {port-id | bundle-id | bpgrp-id | aps-id | connector-port-id}
Context 
config
Description 

This command enables access to the context to configure ports, multilink bundles, and bundle protection groups (BPGs). Before a port can be configured, the chassis slot must be provisioned with a valid card type and the MDA parameter must be provisioned with a valid MDA type.

Default 

No ports are configured. All ports must be explicitly configured and enabled.

Parameters 
port-id—
Specifies the physical port ID in the following format:
Values—
slot/mda/port [.channel]

 

eth-sat-id—
Specifies the Ethernet satellite ID to be associated with this IP interface. This parameter applies to the 7950 XRS only.
Values—

eth-sat-id

esat-id/slot/port

esat

keyword

id

1 to 20

 

pxc-id—
Specifies the PXC ID to be associated with this IP interface. This parameter applies to the 7950 XRS only.
Values—

pxc-id

pxc-id.sub-port

pxc

keyword

id

1 to 64

sub-port

a, b

 

bundle-id—
Specifies the multilink bundle to be associated with this IP interface. The command syntax must be configured as follows:
Values—
bundle-type-slot/mda.bundle-num

bundle-ppp-slot/mda.bundle-num

Creates a multilink PPP bundle.

bundle-ima-slot/mda.bundle-num

Creates an IMA bundle.

bundle-fr-slot/mda.bundle-num

Creates an MLFR bundle.

where:

bundle: keyword

slot: IOM/MDA slot numbers

bundle-num: 1 to 336

For example:
router1>config# port bundle-ppp-5/1.1 (multilink PPP bundle)
router1>config# port bundle-ima-5/1.2 (IMA bundle)

 

aps-id—
This option configures APS on unbundled SONET/SDH ports. All SONET-SDH port parameters, with certain exceptions, for the working and protection circuit ports must be configured in the config>port>aps-group-id context. The working and protection circuit ports inherit all those parameters configured. The exception parameters for the working and protect circuits can be configured in the config>port>sonet-sdh context. Exception list commands include:
  1. clock-source
  2. [no] loopback
  3. [no] report-alarm
  4. section-trace
  5. [no] threshold

When an aps-group-id is created all applicable parameters under the port CLI tree (including parameters under any submenus) assume aps-group-id defaults, or when those are not explicitly specified, default to SONET/SDH port defaults for any SONET port.

All but a few exception SONET/SDH parameters for the working channel port must be configured in the config>port>aps>sonet-sdh context. The protection channel inherits all the configured parameters. The exception parameters for the protection channel can be configured in the config>port>aps>sonet-sdh context.

Signal failure (SF) and signal degrade (SD) alarms are not enabled by default on POS interfaces. It is recommended to change the default alarm notification configuration for POS ports that belong to APS groups in order to be notified of SF/SD occurrences to be able to interpret the cause for an APS group to switch the active line.

For path alarms, modify the logical line aps-id in the config>port aps-id <sonet-sdh>path report-alarm context. For example:

configure port aps-1 sonet-sdh path report-alarm p-ais

For line alarms, separately, modify the 2 physical ports that are members of the logical aps-id port (the working and protect lines). APS reacts only to line alarms, not path alarms. For example:

configure port 1/2/3 sonet-sdh report-alarm lb2er-sd

configure port 4/5/6 sonet-sdh report-alarm lb2er-sd

If the SD and SF threshold rates must be modified, the changes must be performed at the line level on both the working and protect APS port member.

The no form of this command deletes an aps-group-id or bundle-aps-group-id. In order for an aps-group-id to be deleted,

The same rules apply for physical ports, bundles deletions apply to APS ports/bundles deletions (for example an aps-group-id must be shutdown, have no service configuration on it, and no path configuration on it). In addition working and protection circuits must be removed before an aps-group-id may be removed.

Values—
port aps-group-id aps: keyword where group-id: 1 to 64
 
Example: port aps-64

 

bpgrp-id—
Creates a bundle protection group (BPG). The BPGrp consists of a working and protection bundles that provide APS protection to each other using bi-directional APS as supported on the 7750 SR family of products. All members of a working/protection bundle must be on the same working/protection circuit respectively of the same, already provisioned APS group. The working bundle must have already been created in the config>port context before services can be created on a BPGrp.
Values—
bpgrp-type-bpgrp-num

bpgrp:

keyword

type:

ppp — Provides protection of one PPP bundle by another.

ima — Provides protection of one IMA bundle by another IMA bundle.

bpgrp-num:

1 to 1600

 

connector-port-id—
Specifies the physical port of a connector in the following format.
Values—
slot/mda/cconnector/port

 

connector

Syntax 
connector
Context 
config>port
Description 

This command enables the context to configure connector parameters.

breakout

Syntax 
breakout breakout
no breakout
Context 
config>port>connector
Description 

This command defines the port breakout of the transceiver that will be used in the connector. Specifying the type triggers the creation of the ports that will be accessible under the connector.

The no version of this command removes the ports under the connector.

Default 

no breakout

Parameters 
breakout—
Specifies the breakout type.
Values—
c1-40g, c4-10g, c1-100g

 

ddm-events

Syntax 
[no] ddm-events
Context 
config>port
Description 

This command enables Digital Diagnostic Monitoring (DDM) events for the port.

The no form of the command disables DDM events.

dwdm

Syntax 
dwdm
Context 
config>port
Description 

This command configures the Dense Wavelength Division Multiplexing (DWDM) parameters.

amplifier

Syntax 
amplifier
Context 
config>port>dwdm
Description 

This command enables you to tune the optical amplifier parameters.

report-alarms

Syntax 
[no] report-alarms [ild] [tmp] [mth] [mtl] [los] [lop] [com]
Context 
config>port>dwdm>amplifier
Description 

This command allows users to enable/disable the optical amplifier alarms for the port.

Default 

All alarms are enabled

Parameters 
ild—
Reports amplifier pump over-current faults.
tmp—
Reports pump temperature faults.
mth—
Reports module case temperature high faults.
mtl—
Reports module case temperature low faults.
los—
Reports loss of signal faults.
lop—
Reports loss of optical power faults.
com—
Reports module communication failure faults.

coherent

Syntax 
coherent
Context 
config>port>dwdm
Description 

This command configures the coherent optical module parameters.

channel

Syntax 
channel channel
Context 
config>port>dwdm
config>port>dwdm>coherent
config>port>dwdm>tdcm
Description 

This command configures the Dense Wavelength Division Multiplexing (DWDM) ITU channel at which a tunable MDA optical interface will be configured to operate. It is expressed in a form that is derived from the laser's operational frequency. For example 193.40 THz corresponds to DWDM ITU channel 34 in the 100 GHz grid and 193.45 THz corresponds to DWDM ITU channel 345 in the 50 GHz grid. Provisioning rules: The provisioned MDA type must have DWDM tunable optics (for example, p1-100g-tun).

  1. The 'dwdm channel' must set to a non-zero value before the port is set to 'no shutdown'
  2. The port must be 'shutdown' before changing the dwdm channel.
  3. The port must be a physical port to set the dwdm channel
Parameters 
channel—
Specifies the channel.
Values—
0, 17 to 61, 175 to 605

Where:

17 to 61 is used for 100 GHz channels

175, 185 to 605 is used for 50 GHz channels

0 is only valid on disabled (shutdown) ports

 

Values—
The DWDM channel number range is listed in Table 42.
Table 42:  DWDM Channel Numbers  

C-Band

100 GHz Grid

50GHz Grid

nm

THz

ITU Channel

nm

THz

ITU Channel

1528.77

196.10

61

1529.16

196.05

605

1529.55

196.00

60

1529.94

195.95

595

1530.33

195.90

59

1530.72

195.85

585

1531.12

195.80

58

1531.51

195.75

575

1531.90

195.70

57

1532.29

195.65

565

1532.68

195.60

56

1533.07

195.55

555

1533.47

195.50

55

1533.86

195.45

545

1534.25

195.40

54

1534.64

195.35

535

1535.04

195.30

53

1535.43

195.25

525

1535.82

195.20

52

1536.22

195.15

515

1536.61

195.10

51

1537.00

195.05

505

1537.40

195.00

50

1537.79

194.95

495

1538.19

194.90

49

1538.58

194.85

485

1538.98

194.80

48

1539.37

194.75

475

1539.77

194.70

47

1540.16

194.65

465

1540.56

194.60

46

1540.95

194.55

455

1541.35

194.50

45

1541.75

194.45

445

1542.14

194.40

44

1542.54

194.35

435

1542.94

194.30

43

1543.33

194.25

425

1543.73

194.20

42

1544.13

194.15

415

1544.53

194.10

41

1544.92

194.05

405

1545.32

194.00

40

1545.72

193.95

395

1546.12

193.90

39

1546.52

193.85

385

1546.92

193.80

38

1547.32

193.75

375

1547.72

193.70

37

1548.11

193.65

365

1548.51

193.60

36

1548.91

193.55

355

1549.32

193.50

35

1549.72

193.45

345

1550.12

193.40

34

1550.52

193.35

335

1550.92

193.30

33

1551.32

193.25

325

1551.72

193.20

32

1552.12

193.15

315

1552.52

193.10

31

1552.93

193.05

305

1553.33

193.00

30

1553.73

192.95

295

1554.13

192.90

29

1554.54

192.85

285

1554.94

192.80

28

1555.34

192.75

275

1555.75

192.70

27

1556.15

192.65

265

1556.55

192.60

26

1556.96

192.55

255

1557.36

192.50

25

1557.77

192.45

245

1558.17

192.40

24

1558.58

192.35

235

1558.98

192.30

23

1559.39

192.25

225

1559.79

192.20

22

1560.20

192.15

215

1560.61

192.10

21

1561.01

192.05

205

1561.42

192.00

20

1561.83

191.95

195

1562.23

191.90

19

1562.64

191.85

185

1563.05

191.80

18

1563.45

191.75

175

1563.86

191.70

17

 

compatibility

Syntax 
compatibility mode
Context 
config>port>dwdm>coherent
Description 

This command configures the optical mode and rate of operation.

Parameters 
mode—
Specifies the optical mode.
Values—
long-haul, metro, access, interop, interop2

 

Default—
long-haul

cpr-window-size

Syntax 
cpr-window-size window-size
Context 
config>port>dwdm>coherent
Description 

This command configure the window size used for carrier phase recovery.

Default 

32

Parameters 
window-size—
Indicates the number of symbols used for carrier phase recovery algorithm of the receiver. When this parameter is changed, the link will bounce because the receiver needs to be reconfigured.
Values—
2, 4, 8, 16, 32, 64

 

dispersion

Syntax 
dispersion dispersion
Context 
config>port>dwdm>coherent
Description 

This command configures the residual chromatic dispersion to be compensated when the coherent receiver is operating in manual dispersion control mode.

Default 

0

Parameters 
dispersion—
Specifies the dispersion compensation.
Values—
-50000 to 50000

 

mode

Syntax 
mode {automatic | manual}
Context 
config>port>dwdm>coherent
Description 

This command configures the mode used to compensate for chromatic dispersion.

Parameters 
automatic—
Sets to automatic mode.
manual—
Sets to manual mode.

report-alarms

Syntax 
[no] report-alarms [modflt] [mod] [netrx] [nettx] [hosttx]
Context 
config>port>dwdm>coherent
Description 

This command configures the alarms that will be reported for the coherent module.

Default 

modflt mod netrx nettx hosttx

Parameters 
modflt—
Reports module fault alarm.
mod—
Reports module alarm.
netrx —
Reports network (optical side) receive alarm.
nettx—
Reports network (optical side) transmit alarm.
hosttx—
Reports host (electrical side) transmit alarm.

rx-los-reaction

Syntax 
rx-los-reaction {squelch}
no rx-los-reaction
Context 
config>port>dwdm>coherent
Description 

This command configures the reaction to an RX LOS.

Parameters 
squelch—
Specifies to squelch (turn off) the transmit signal on RX LOS.

rx-los-thresh

Syntax 
rx-los-thresh threshold
Context 
config>port>dwdm>coherent
Description 

This command configures the average input power LOS (Loss of Signal) threshold.

Default 

-23

Parameters 
threshold—
Specifies the port’s rx los threshold.
Values—
-24.00 to -13.00

 

sweep

Syntax 
sweep start dispersion-start end dispersion-end
Context 
config>port>dwdm>coherent
Description 

This command allows users to configure the dispersion sweep ‘start’ and ‘end’ values for the automatic mode of coherent control. If the user knows the approximate or theoretical residual dispersion of the link, this command can be used to limit the range of sweeping for the automatic control mode and thus achieve faster link up.

Parameters 
dispersion-start—
Specifies the lower range limit for the dispersion compensation.
Values—
-50000 to 50000

 

Default—
-25500
dispersion-end—
Specifies the upper range limit for the dispersion compensation.
Values—
-50000 to 50000

 

Default—
2000

target-power

Syntax 
target-power power
Context 
config>port>dwdm>coherent
Description 

This command configures the target transmit optical power for the port.

Default 

target-power 1.00

Parameters 
power—
Specifies the desired average output power in dBm.
Values—
-20.00 to 3.00

 

rxdtv-adjust

Syntax 
[no] rxdtv-adjust
Context 
config>port>dwdm
Description 

This command enables you to adjust the optical receive decision threshold voltage (RxDTV).

Default 

no rxdtv-adjust

tdcm

Syntax 
tdcm
Context 
config>port>dwdm
Description 

This command configures the Tunable Dispersion Compensation Module parameters.

dispersion

Syntax 
dispersion dispersion
Context 
config>port>dwdm>tdcm
Description 

This command allows users to configure the dispersion compensation for the port when manual mode is selected.

Parameters 
dispersion—
Specifies the dispersion compensation.
Values—
-1200 to 1200

 

Default—
0

mode

Syntax 
mode {automatic | manual}
Context 
config>port>dwdm>tdcm
Description 

This command allows users to configure the dispersion algorithm mode used for the port. Manual mode is used when the user knows the residual dispersion on the link. Automatic mode is used to let the software determine the optimal dispersion compensation required. Automatic mode should be used during service commissioning and when the state if the TDCM control is converged, the user can change to manual mode and configure the dispersion compensation found by the software. Because automatic mode uses a search algorithm that will sweep the entire range of dispersion specified in the sweep command, it can take up to 10 minutes for the link to come up. In manual mode, the link can come up in 2 minutes or less.

Parameters 
automatic—
Sets to automatic mode.
manual—
Sets to manual mode.

report-alarms

Syntax 
[no] report-alarms [nrdy] [mth] [mtl] [unlck] [tlim] [einv] [com]
Context 
config>port>dwdm>tdcm
Description 

This command allows users to Enable/disable logging of tdcm alarms on the port.

Default 

All alarms are enabled

Parameters 
nrdy—
Reports Tdcm not ready faults.
mth—
Reports module case temperature high faults.
mtl—
Reports module case temperature low faults.
unlck—
Reports thermal control locked faults.
tlim—
Reports thermal control temperature limit faults.
einv—
Reports EEPROM invalid faults.
com—
Reports Tdcm module communication failure faults.

sweep

Syntax 
sweep start dispersion-start end dispersion-end
Context 
config>port>dwdm>tdcm
Description 

This command allows users to configure the dispersion sweep ‘start’ and ‘end’ values for the automatic mode of TDCM control. If the user knows the approximate or theoretical residual dispersion of the link, this command can be used to limit the range of sweeping for the automatic control mode and thus achieve faster link up.

Parameters 
dispersion-start—
Specifies the lower range limit for the dispersion compensation.
Values—
-1200 to 1200

 

Default—
-1200
dispersion-end—
Specifies the upper range limit for the dispersion compensation.
Values—
-1200 to 1200

 

Default—
1200

wavetracker

Syntax 
wavetracker
Context 
config>port>dwdm
Description 

This command validates whether or not the port supports Wavetracker.

encode

Syntax 
encode key1 wave-key key2 wave-key
no encode
Context 
config>port>dwdm>wavetracker
Description 

This command specifies whether or not Wavetracker keys should be encoded on the transmitted optical signal.

Default 

no encode

Parameters 
wave-key —
The wave-key values must be selected based on the currently configured DWDM ITU channel. Both keys must be odd or both keys must be even. One even key and one odd key cannot be configured. The ranges of values for each key are defined in Table 43:
Table 43:  Value Ranges for DWDM ITU Channel 

DWDM ITU Channel Number

Key 1 Minimum

Key 1 Maximum

Key 2 Minimum

Key 2 Maximum

17

1276

1290

1760

1774

18

1259

1273

1743

1757

19

1242

1256

1726

1740

20

1225

1239

1709

1723

21

528

542

1072

1086

22

511

525

1055

1069

23

494

508

1038

1052

24

477

491

1021

1035

25

1208

1222

1692

1706

26

460

474

1004

1018

27

443

457

987

1001

28

426

440

970

984

29

409

423

953

967

30

1191

1205

1675

1689

31

392

406

936

950

32

375

389

919

933

33

358

372

902

916

34

341

355

885

899

35

1174

1188

1658

1672

36

324

338

868

882

37

307

321

851

865

38

290

304

834

848

39

273

287

817

831

40

1157

1171

1641

1655

41

256

270

800

814

42

239

253

783

797

43

222

236

766

780

44

205

219

749

763

45

1140

1154

1624

1638

46

188

202

732

746

47

171

185

715

729

48

154

168

698

712

49

137

151

681

698

50

1123

1137

1607

1621

51

120

134

664

678

52

103

117

647

661

53

86

100

630

644

54

69

83

613

627

55

1106

1120

1590

1604

56

52

66

596

610

57

35

49

579

593

58

18

32

562

576

59

1

15

545

559

60

1089

1103

1573

1587

61

1548

1548

2032

2032

175

3553

3567

4065

4079

185

3536

3550

4048

4062

195

3519

3533

4031

4045

205

3502

3516

4014

4028

215

3840

3854

2304

2318

225

3823

3837

2287

2301

235

3806

3820

2270

2284

245

3789

3803

2253

2267

255

3485

3499

3997

4011

265

3772

3786

2236

2250

275

3755

3769

2219

2233

285

3738

3752

2202

2216

295

3721

3735

2185

2199

305

3468

3482

3980

3994

315

3704

3718

2168

2182

325

3687

3701

2151

2165

335

3670

3684

2134

2148

345

3653

3667

2117

2131

355

3451

3465

3963

3977

365

3636

3650

2100

2114

375

3619

3633

2083

2097

385

3602

3616

2066

2080

395

3585

3599

2049

2063

405

3434

3448

3946

3960

415

1548

1562

2032

2046

425

1531

1545

2015

2029

435

1514

1528

1998

2012

445

1497

1511

1981

1995

455

3908

3922

2372

2386

465

1480

1494

1964

1978

475

1463

1477

1947

1961

485

1446

1460

1930

1944

495

1429

1443

1913

1927

505

3891

3905

2355

2369

515

1412

1426

1896

1910

525

1395

1409

1879

1893

535

1378

1392

1862

1876

545

1361

1375

1845

1859

555

3874

3888

2338

2352

565

1344

1358

1828

1842

575

1327

1341

1811

1825

585

1310

1324

1794

1808

595

1293

1307

1777

1791

605

3857

3871

2321

2335

power-control

Syntax 
[no] power-control
Context 
config>port>dwdm>wavetracker>power-control
Description 

This command specifies whether the power control loop should be turned on to actively control the laser’s launch power to the specified target power. When power-control is disabled, the launch power is set to the laser’s maximum achievable power.

Default 

no power-control

target-power

Syntax 
target-power dBm
Context 
config>port>dwdm>wavetracker>power-control
Description 

This command specifies launch power in dBm for the DWDM Wavetracker-enabled interface.

Default 

target-power -20.00

Parameters 
dBm—
Specifies the desired average output power in dBm.
Values—
-22.00 to 3.00

 

report-alarm

Syntax 
[no] report-alarm [encode-fail] [encode-degrade] [power-fail] [power-degrade] [power-high] [power-low] [missing]
Context 
config>port>dwdm>wavetracker
Description 

This command specifies the alarms which are enabled or outstanding against a Wave Tracker-enabled interface.

The no form of the command removes the alarm parameters.

Parameters 
encode-fail —
Specifies the Encoder failure alarm.
encode-degrade —
Specifies the Encoder degrade alarm.
encode-fail —
Specifies the Power control failure alarm.
power-degrade—
Specifies the Power control degrade alarm.
power-high—
Specifies the Power control high limit reached alarm.
power-low —
Specifies the Power control low limit reached alarm.
missing—
Specifies the wavelength/wavetracker missing alarm.

queue-group

Syntax 
queue-group queue-group-name instance instance-id
no queue-group
Context 
config>port>ethernet>network>egress
Description 

This command configures a queue-group instance in the network egress context of a port.

Queue-groups containing queues only or policers and queues can be instantiated. When a port is a LAG, one instance of the queue-group is instantiated on each member link.

One or more instances of the same queue-group name and/or a different queue-group name can be created in the network egress context of a port.

The queue-group-name must be unique within all network egress and access egress queue groups in the system. The queue-group instance-id must be unique within the context of the port.

The no version of this command deletes the queue-group instance from the network egress context of the port.

Parameters 
queue-group-name—
Specifies the name of the queue group template up to 32 characters in length.
instance-id
Specifies the identification of a specific instance of the queue-group.
Values—
1 to 65535

 

xgig

Syntax 
xgig {lan |wan}
Context 
config>port>ethernet
Description 

This command configures a 10 Gb/s interface to be in Local or Wide Area Network (LAN or WAN) mode. When configuring the port to be in WAN mode, you can change certain SONET/SDH parameters to reflect the SONET/SDH requirements for this port. When you configure a port for LAN mode, all SONET/SDH parameters are pre-determined and not configurable.

Default 

xgig lan

Parameters 
lan—
Sets the port to operate in LAN mode.
wan—
Sets the port to operate in WAN mode.

otu

Syntax 
[no] otu
Context 
config>port
Description 

This command specifies whether or not to enable OTU encapsulation. The port must be shut down before OTU is enabled. This command is valid only for ports on assemblies that support this encapsulation mode. Refer to the appropriate Installation Guide for ports assembly to determine if OTU encapsulation is supported.

Note that OTU cannot be disabled on OTU3 encapsulated OC768 or 40-Gigabit Ethernet.by the no otu command. Therefore, the default depends on the port type. The default for OTU3 encapsulated OC768 or 40-Gigabit Ethernet is otu.

The no form of this command disables OTU (clear channel 10GE-LAN/WAN or OC192).

Default 

no otu

fec

Syntax 
fec {g709 | enhanced}
no fec
Context 
config>port>otu>fec
Description 

This command enables the Forwarding Error Correction (FEC) encoder/decoder and specifies the FEC encoder/decoder mode to use when enabled.

The following rules must be followed:

  1. The port’s OTU must be enabled to set or change the FEC mode.
  2. The port must be shut down before changing the FEC mode.
  3. The sf-sd-method must be changed to BIP8 before setting the FEC mode to disabled.

Note that FEC cannot be disabled on OTU3 encapsulated OC768 or 40-Gigabit Ethernet by the no fec command. Therefore, the default depends on the port type. The default for OTU3 encapsulated OC768 or 40-Gigabit Ethernet is fec enhanced.

The no form of the command disables FEC encoder and decoder.

Default 

no fec

Parameters 
enhanced —
Enables the FEC encoder and decoder with a proprietary enhanced FEC algorithm.
g709 —
Enables the FEC encoder and decoder with the standard G.709 FEC algorithm.

otu2-lan-data-rate

Syntax 
otu2-lan-data-rate {11.049 | 11.096}
Context 
config>port>otu
Description 

This command specifies the data rate to use when configured for an OTU encapsulated 10GE-LAN signal. The port must be shut down before changing the 10GE LAN OTU2 data rate.

Default 

otu2-lan-data-rate 11.049

Parameters 
11.049 —
Configures the port to transmit and receive an 11.049 Gb/s synchronous OTU encapsulated 10GE-LAN signal (No fixed stuffing bytes in the OTU2 frame).
11.096 —
Configures the port to transmit and receive an 11.096 Gb/s synchronous OTU encapsulated 10GE-LAN signal (with fixed stuffing bytes in the OTU2 frame).

pm-tti

Syntax 
pm-tti
Context 
config>port>otu
Description 

This command enables the context to configure path monitoring trail trace identifier parameters.

expected

Syntax 
expected auto-generated
expected bytes byte-string [byte-string (up to 64 bytes-strings max, 64 bytes max)]
expected string identifier
expected use-rx
Context 
config>port>otu>pm-tti
Description 

This command allows the user to configure the expected RX trail trace identifier (TTI) for path monitoring (PM) in the ODU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes. This trace should match the far-end port’s PM trace. When this trace does not match the received PM trace, the ODU-TIM alarm will be reported if enabled.

Default 

Blank (all zeros)

Parameters 
auto-generated—
Sets the default.
identifier—
Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. Up to 64 byte strings can be specified in a single statement.
byte-string—
[byte1 byte2 to byte64]. Sets the PM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0.
use-rx—
Copies the received pm-tti to the expected either as a string or a sequence of bytes depending on the received pm-tti data.

mismatch-reaction

Syntax 
mismatch-reaction {squelch-rx}
no mismatch-reaction
Context 
config>port>otu>pm-tti
Description 

This command allows the user to configure the consequent action to a pm-tti mismatch.

The no form of the command reverts to the default.

Default 

n/a, the received traffic is passed through.

Parameters 
squelch-rx —
Specifies that the received traffic is blocked.

tx

Syntax 
tx auto-generated
tx bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]
tx string identifier
no tx
Context 
config>port>otu>pm-tti
Description 

This command enables the user to configure the transmit (tx) trail trace identifier (TTI) for path monitoring (PM) in the ODU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes.

The no form of the command reverts to the default TTI.

Default 

Auto-generated in the format of nodename:iomnum/mdanum/portnum/dwdmchan

The auto-generated value has five sections:

  1. Nodename — The first section is the name of the node.
  2. iomnum — The second section contains the IOM slot number.
  3. mdanum — The third section contains the MDA slot number.
  4. portnum — The fourth section contains the port number.
  5. dwdmchan — The fifth section contains the DWDM channel number (see DWDM Channel Numbers).
Parameters 
auto-generated—
Specifies to use the system generated (default) TTI.
identifier
Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0.
byte-string—
Sets the PM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0. A 1 byte sequence of 0xFF will set the default strings. Up to 64 byte strings can be specified in a single statement.
Values—
0 to FF, in hexadecimal byte notation

 

psi-payload

Syntax 
psi-payload
Context 
config>port>otu
Description 

This command enables the context to configure payload structure identifier payload parameters.

expected

Syntax 
expected byte
expected auto
Context 
config>port>otu>psi-payload
Description 

This command allows the user to configure the expected received payload type value in byte 0 of the Payload structure identifier (PSI) of the OPU overhead. When this values does not match the received value, the OPU-PLM alarm will be reported if it is enabled.

Default 

3 for 10GE-LAN/WAN or OC192 with OTU encapsulation; 5 for GFP framed 10GE-LAN with OTU encapsulation.

Parameters 
auto—
Sets the expected value to the standard value in the payload type field.
byte—
Specifies the expected received payload type value in bytes.
Values—
[00 to FF] Hexadecimal notation

 

Default—
00

mismatch-reaction

Syntax 
mismatch-reaction {none | squelch-rx}
Context 
config>port>otu>psi-payload
Description 

This command allows the user to configure the consequent action to a psi-payload type mismatch.

Parameters 
none —
Specifies the received traffic is passed through.
squelch-rx —
Specifies the received traffic is blocked.

sf-sd-method

Syntax 
sf-sd-method {bip8 | fec}
Context 
config>port>otu>sf-sd-method
Description 

This command specifies the method used to determine the signal fail and signal degrade alarms. When select the bip8 method is selected, the SM-BIP8 errors are used. When the FEC method is selected, the FEC corrected bits are used.

The following rules must be followed:

  1. The port’s OTU must be enabled to set or change the sf-sd-method.
  2. The FEC mode must be enhanced or g709 before setting the sf-sd-method to fec.
  3. The SF threshold must be 5 or higher before setting the sf-sd-method to bip8.
Default 

sf-sd-method fec

Parameters 
bip8—
The SM-BIP8 errors are used to declare the presence of the Signal Fail and Signal Degrade condition.
fec—
The FEC corrected bit errors are used to declare the presence of the Signal Fail and Signal Degrade condition.

sf-threshold

Syntax 
sf-threshold threshold [coefficient coefficient]
Context 
config>port>otu
Description 

This command specifies the error rate at which to declare the signal fail condition for the signal fail (SF) threshold. The value represents an error rate of 10E-<value>.

The SF threshold must:

  1. Be less than the SD threshold
  2. Be 5 or higher before setting the sf-sd-method to bip8
Default 

4

Parameters 
threshold—
Specifies the signal fail (SF) threshold.
Values—
3 to 6

 

Default—
5
coefficient—
Specifies the coefficient of the SF threshold.
Values—
10 to 99

 

Default—
10

sf-threshold-clear

Syntax 
sf-threshold-clear threshold [coefficient coefficient]
Context 
config>port>otu
Description 

This command the signal fail (SF) threshold clear.

Parameters 
threshold—
Specifies the exponent of the error rate, thus an error rate from 10E-3 to 10E-7.
Values—
5 to 9

 

Default—
6
coefficient—
Specifies the coefficient of the SF threshold.
Values—
10 to 99

 

Default—
10

sd-threshold

Syntax 
sd-threshold threshold [coefficient coefficient]
Context 
config>port>otu>sd-threshold
Description 

This command specifies the error rate at which to declare the signal fail condition for the signal degrade (SD). The value represents an error rate of 10E-value.

The SD threshold must be:

  1. greater than the SF threshold.
  2. 5 or higher before setting the sf-sd-method to bip8.
Default 

7

Parameters 
threshold—
Specifies the exponent of the error rate, thus an error rate from 10E-3 to 10E-7.
Values—
5 to 9

 

Default—
7
coefficient—
Specifies the coefficient of the SD threshold.
Values—
10 to 99

 

Default—
10

sd-threshold-clear

Syntax 
sd-threshold-clear threshold [coefficient coefficient]
Context 
config>port>otu
Description 

This command configures the signal degrade threshold clear.

Parameters 
threshold—
Specifies the exponent of the error rate, thus an error rate from 10E-3 to 10E-7.
Values—
3 to 10

 

Default—
8
coefficient—
Specifies the coefficient of the SD threshold.
Values—
10 to 99

 

Default—
10

sm-tti

Syntax 
sm-tti
Context 
config>port>otu
Description 

This command enables the context to configure section monitoring trail trace identifier parameters.

expected

Syntax 
expected auto-generated
expected bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]
expected string identifier
expected use-rx
Context 
config>port>otu>sm-tti
Description 

This command enables the user to configure the expected RX Trail Trace Identifier (TTI) for Section Monitoring (SM) in the OTU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes. This trace should match the expected far-end port’s SM trace. When this trace does not match the received SM trace, the OTU-TIM alarm will be reported if enabled.

Default 

Blank (all zeros)

Parameters 
auto-generated—
Sets the default.
identifier—
Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. Up to 64 byte strings can be specified in a single statement.
byte-string—
[byte1 byte2 to byte64]. Sets the PM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0.
use-rx—
Copies the received pm-tti to the expected either as a string or a sequence of bytes depending on the received pm-tti data.

mismatch-reaction

Syntax 
mismatch-reaction {none | squelch-rx}
Context 
config>port>otu>sm-tti
Description 

This command allows the user to configure the consequent action to a sm-tti mismatch.

Default 

n/a

Parameters 
none —
Specifies that the received traffic is passed through.
squelch-rx —
Specifies that the received traffic is blocked.

tx

Syntax 
tx byte
tx auto
Context 
config>port>otu>psi-payload
Description 

This command allows the user to configure the transmit payload type value in byte 0 of the payload structure identifier (PSI) of the OPU overhead.

Default 

3 for 10GE-LAN/WAN or OC192 with OTU encapsulation; 5 for GFP framed 10GE-LAN with OTU encapsulation.

Parameters 
auto—
Transmits the standard value in the payload type field.
byte—
Specifies the transmit payload type value in bytes.
Values—
[00 to FF] Hexadecimal notation

 

Default—
00

tx

Syntax 
tx auto-generated
tx bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]
tx string identifier
no tx
Context 
config>port>otu>sm-tti
Description 

This command allows the user to configure the transmit (tx) trail trace identifier (TTI) for section monitoring (SM) in the OTU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes.

The no form of the command reverts to the default TTI.

Default 

Auto-generated in the format of nodename:iomnum/mdanum/portnum/dwdmchan

The auto-generated value has five sections:

  1. Nodename — The first section is the name of the node.
  2. iomnum — The second section contains the IOM slot number.
  3. mdanum — The third section contains the MDA slot number.
  4. portnum — The fourth section contains the port number.
  5. dwdmchan — The fifth section contains the DWDM channel number (see DWDM Channel Numbers).
Parameters 
auto-generated—
Specifies to use the system generated (default) TTI.
identifier
Sets the SM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. Up to 64 byte strings can be specified in a single statement.
byte-string—
Sets the SM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0. A 1 byte sequence of 0xFF will set the default strings.
Values—
0 to FF, in hexadecimal byte notation

 

psi-tti

Syntax 
psi-tti
Context 
config>port>otu
Description 

This command enables the context to configure payload structure identifier trail trace identifier parameters.

tx

Syntax 
tx {string identifier | bytes byte-sequence | auto-generated}
Context 
config>port>otu>psi-trace
Description 

This command allows the user to configure the transmit trace in bytes 1 to 255 (skipping byte 0) of the payload structure identifier (PSI) of the OPU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 255 bytes.

Default 

Blank (all zeros)

Parameters 
auto-generated—
Sets the default PSI trace.
identifier
Sets the PSI trace to the string provided by the user. If the string is less than 255 bytes, the remaining bytes will be set to 0.
byte-sequence —
[byte1 byte2 to byte64] Sets the PSI trace to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0. A 1 byte sequence of 0xFF will set the default strings.
Values—
0 to FF, in hexadecimal byte notation

 

mismatch-reaction

Syntax 
mismatch-reaction {none | squelch-rx}
Context 
config>port>otu>psi-tti
Description 

This command allows the user to configure the consequent action to a psi-tti mismatch.

Default 

n/a

Parameters 
none —
Specifies the received traffic is passed through.
squelch-rx —
Specifies the received traffic is blocked.

async-mapping

Syntax 
[no] async-mapping
Context 
config>port>otu
Description 

This command allows the user to configure the port to support asynchronous mapping of the payload inside the OTU. If the port is configured for async-mapping and the payload clock is asynchronous to the OTU clock, there will be positive or negative pointer justification that will show up in the OTU statistics and the data will be received error free. If the port is configured for synchronous mapping and the received data is asynchronously mapped, there will be errors in the received data.

async-mapping is the only mode of operation that is supported on the OTU3 encapsulated 40-Gigabit Ethernet and therefore the 'no async-mapping' is not supported on that port type and the default on the is async-mapping.

The no form of this command configures the port to receive synchronously mapped data.

Default 

no async-mapping

report-alarms

Syntax 
[no] report-alarms [loc] [los] [lof] [lom] [otu-ais] [otu-ber-sf] [otu-ber-sd] [otu-bdi] [otu-tim] [otu-iae] [otu-biae] [fec-sf] [fec-sd] [fec-fail] [fec-uncorr] [odu-ais] [odu-oci] [odu-lck] [odu-bdi] [odu-tim] [opu-tim] [opu-plm]
Context 
config>port>otu
Description 

This command enables OTU alarms. Specify specific alarms to add to the list of reported alarms.

The no form of the command disables OTU alarm reporting.

Default 

loc, los, lof, lom, otu-ber-sf, otu-bdi, fec-sf

Parameters 
alarms—
Refer to Table 44 for alarm descriptions.
Table 44:  Alarm Descriptions 

Alarm

Description  

loc

Loss of lock.

lof

Loss of OTU framing.

lom

Loss of Multi-frame.

los

Loss of signal transitions on the data.

otu-ais

OTU Alarm Indication Signal (all 1s, overwrites all OTU overhead, even framing bytes).

otu-ber-sf

SM Signal Fail (based on BPI8).

otu-ber-sd

SM Signal Degrade (based on BPI8).

otu-bdi

SM Backward defect indication.

otu-tim

SM Trace Id Mismatch.

otu-iae

SM Incoming Alignment Error.

otu-biae

SM Backward Incoming Alignment Error.

fec-sf

Signal Fail (based on FEC corrected bits).

fec-sd

Signal Degrade (based on FEC corrected bits).

fec-fail

FEC Mode mismatch (EFEC-GFEC) or High Uncorrectable rate (>10E-2).

fec-uncorr

One or More Uncorrectable FEC errors.

odu-ais

ODU Alarm Indication Signal.

odu-oci

ODU Open connection Indication.

odu-lck

ODU Locked.

odu-bdi

PM Backward Defect indication.

odu-tim

PM Trace Id Mismatch.

opu-tim

OPU PSI Trace Mismatch.

opu-plm

OPU PSI Payload Type Mismatch.

hybrid-buffer-allocation

Syntax 
hybrid-buffer-allocation
Context 
config>port
Description 

This command enables the context for configuring hybrid port buffer allocation parameters.

egr-weight

Syntax 
egr-weight access access-weight network network-weight
no egr-weight
Context 
config>port>hybrid-buffer-allocation
Description 

This command configures the sharing of the egress buffers allocated to a hybrid port among the access and network contexts. By default, it is split equally between network and access.

The no form of this command restores the default values for the egress access and network weights.

Parameters 
access-weight—
Specifies the access weight as an integer.
Values—
0 to 100

 

Default—
50
network-weight—
Specifies the network weight as an integer.
Values—
0 to 100

 

Default—
50

ing-weight

Syntax 
ing-weight access access-weight network network-weight
no ing-weight
Context 
config>port>hybrid-buffer-allocation
Description 

This command configures the sharing of the ingress buffers allocated to a hybrid port among the access and network contexts. By default, it is split equally between network and access.

The no form of this command restores the default values for the ingress access and network weights.

Parameters 
access-weight—
Specifies the access weight as an integer.
Values—
0 to 100

 

Default—
50
network-weight—
Specifies the network weight as an integer.
Values—
0 to 100

 

Default—
50

modify-buffer-allocation-rate

Syntax 
modify-buffer-allocation-rate
Context 
config>port
Description 

This command enables the context to configure ingress and egress percentage of rate parameters. This command only applies to physical ports (for example, it will not work on APS or similar logical ports). The percentage of rate commands are used to define a percentage value that affects the amount of buffers used by ingress and egress port managed buffer space. Enter the modify-buffer-allocation-rate context when editing the port’s percentage of rate commands.

egr-percentage-of-rate

Syntax 
egr-percentage-of-rate egr-rate-percentage
no egr-percentage-of-rate
Context 
config>port>modify-buffer-allocation-rate
Description 

The egr-percentage-of-rate command increases or decreases the active bandwidth associated with the egress port that affects the amount of egress buffer space managed by the port. Changing a ports active bandwidth using the egr-percentage-of-rate command is an effective means of artificially lowering the buffers managed by one egress port and giving them to other egress ports on the same MDA.

The egr-percentage-of-rate command accepts a percentage value that increases or decreases the active bandwidth based on the defined percentage. A value of 50% causes the active bandwidth to be reduced by 50%. A value of 150% causes the active bandwidth to be increased by 50%. Values from 1 to 1000 percent are supported.

A value of 100 (the default value) is equivalent to executing the no egr-percentage-of-rate command and restores the egress active rate to the normal value.

The no form of the command removes any artificial increase or decrease of the egress active bandwidth used for egress buffer space allocation to the port. The no egr-percentage-of-rate command sets rate-percentage to 100%.

Parameters 
egr-rate-percentage—
The rate-percentage parameter is required and defines the percentage value used to modify the current egress active bandwidth of the port. This does not actually change the bandwidth available on the port in any way. The defined rate-percentage is multiplied by the egress active bandwidth of the port. A value of 150 results in an increase of 50% (1.5 x Rate).
Values—
1 to 1000

 

Default—
100 (no change to active rate)

ing-percentage-of-rate

Syntax 
ing-percentage-of-rate ing-rate-percentage
no ing-percentage-of-rate
Context 
config>port>modify-buffer-allocation-rate
Description 

This command increases or decreases the active bandwidth associated with the ingress port that affects the amount of ingress buffer space managed by the port. Changing a port’s active bandwidth using the ing-percentage-of-rate command is an effective means of artificially lowering the buffers managed by one ingress port and giving them to other ingress ports on the same MDA.

The ing-percentage-of-rate command accepts a percentage value that increases or decreases the active bandwidth based on the defined percentage. A value of 50% causes the active bandwidth to be reduced by 50%. A value of 150% causes the active bandwidth to be increased by 50%. Values from 1 to 1000 percent are supported.

A value of 100 (the default value) is equivalent to executing the no ing-percentage-of-rate command and restores the ingress active rate to the normal value.

The no form command removes any artificial increase or decrease of the ingress active bandwidth used for ingress buffer space allocation to the port. The no ing-percentage-of-rate command sets rate-percentage to 100%.

Parameters 
ing-rate-percentage—
The rate-percentage parameter is required and defines the percentage value used to modify the current ingress active bandwidth of the port. This does not actually change the bandwidth available on the port in any way. The defined rate-percentage is multiplied by the ingress active bandwidth of the port. A value of 150 results in an increase of 50% (1.5 x Rate).
Values—
1 to 1000

 

Default—
100 (no change to active rate)

monitor-agg-egress-queue-stats

Syntax 
[no] monitor-agg-egress-queue-stats
Context 
config>port
Description 

This command enables the monitoring of aggregate egress queue statistics on the port. All queues on the port are monitored, including SAP egress, network egress, subscriber egress, and egress queue group queues, as well as system queues that can be used, for example, to send port-related protocol packets (LACP, EFM, and so on). The aggregate in-profile, out-of-profile, and total statistics are provided for both forwarded and dropped packets and octets.

Monitoring of aggregate statistics is supported on PXC sub-ports but not on a PXC physical port. It is also not supported on satellite ports or ports on an HSMDA.

The no form of the command disables aggregate egress queue statistics monitoring on the specified port.

egress-scheduler-override

Syntax 
egress-scheduler-override [create]
no egress-scheduler-override
Context 
config>port>sonet-sdh>path
config>port>ethernet
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command applies egress scheduler overrides. When a port scheduler is associated with an egress port, it is possible to override the following parameters:

  1. The max-rate allowed for the scheduler.
  2. The maximum rate for each priority level 8 through 1.
  3. The CIR associated with each priority level 8 through 1.

See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for command syntax and usage for the port-scheduler-policy command.

The no form of this command removes all override parameters from the egress port or channel scheduler context. Once removed, the port scheduler reverts all rate parameters back to the parameters defined on the port-scheduler-policy associated with the port.

Parameters 
create—
Mandatory while creating an entry.

level

Syntax 
level priority-level rate pir-rate [cir cir-rate]
level priority-level percent-rate pir-percent [percent-cir cir-percent]
no level priority-level
Context 
config>port>ethernet>egress-scheduler-override
config>port>sonet-sdh>path>egress-scheduler-override
config>port>tdm>ds1>channel-group>egress-scheduler-override
config>port>tdm>ds3>egress-scheduler-override
config>port>tdm>e1>egress-scheduler-override
config>port>tdm>e3>egress-scheduler-override
Description 

This command overrides the maximum and CIR rate parameters for a specific priority level on the port or channel’s port scheduler instance. When the level command is executed for a priority level, the corresponding priority level command in the port-scheduler-policy associated with the port is ignored. The override level command supports the keyword max for the rate and cir parameter. When executing the level override command, at least the rate or cir keywords and associated parameters must be specified for the command to succeed.

The no form of this command removes the local port priority level rate overrides. Once removed, the port priority level will use the port scheduler policies level command for that priority level.

Parameters 
priority-level—
Identifies which of the eight port priority levels are being overridden.
Values—
1 to 8

 

pir-rate
Overrides the port scheduler policy’s maximum level rate and requires either the max keyword or a rate defined in kilobits per second to follow.
Values—
max, 1 to 3200000000 kb/s

 

cir-rate
Overrides the port scheduler policy’s within-cir level rate and requires either the max keyword or a rate defined in kilobits per second to follow.
Values—
max, 0 to 3200000000 kb/s

 

pir-percent—
Specifies the PIR as a percentage.
Values—
0.01 to 100.00

 

cir-percent—
Specifies the CIR as a percentage.
Values—
0.00 to 100.00

 

max—
removes any existing rate limit imposed by the port scheduler policy for the priority level allowing it to use as much total bandwidth as possible.

max-rate

Syntax 
max-rate rate
max-rate percent-rate
no max-rate
Context 
config>port>ethernet>egress-scheduler-override>level>rate
config>port>ethernet>egress-scheduler-override
config>port>sonet-sdh>path>egress-scheduler-override
config>port>tdm>ds1>channel-group>egress-scheduler-override
config>port>tdm>ds3>egress-scheduler-override
config>port>tdm>e1>channel-group>egress-scheduler-override
config>port>tdm>e3>egress-scheduler-override
Description 

This command overrides the max-rate parameter found in the port-scheduler-policy associated with the port. When a max-rate is defined at the port or channel level, the port scheduler policies max-rate parameter is ignored.

The egress-scheduler-override max-rate command supports a parameter that allows the override command to restore the default of not having a rate limit on the port scheduler. This is helpful when the port scheduler policy has an explicit maximum rate defined and it is desirable to remove this limit at the port instance.

The no form of this command removes the maximum rate override from the egress port or channels port scheduler context. Once removed, the max-rate parameter from the port scheduler policy associated with the port or channel will be used by the local scheduler context.

Parameters 
rate—
Specifies the explicit maximum frame based bandwidth limit. This value overrides the QoS scheduler policy rate.
Values—
1 to 3200000000, max

 

percent-rate—
Values—
0.01 to 100.00

 

egress-scheduler-policy

Syntax 
egress-scheduler-policy port-scheduler-policy-name
no egress-scheduler-policy
Context 
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command enables the provisioning of an existing port-scheduler-policy to a port or channel.

The egress-scheduler-override node allows for the definition of the scheduler overrides for a specific port or channel.

When a port scheduler is active on a port or channel, all queues and intermediate service schedulers on the port are subject to receiving bandwidth from the scheduler. Any policers, queues, or schedulers with port-parent associations are mapped to the appropriate port priority levels based on the port-parent command parameters. Any policers, queues, or schedulers that do not have a port-parent or valid intermediate scheduler parent defined are treated as orphaned and are handled based on the port scheduler policies default or explicit orphan behavior.

The port scheduler maximum rate and priority level rate parameters may be overridden to allow unique values separate from the port-scheduler-policy-name attached to the port or channel. Use the egress-scheduler-override command to specify the port or channel specific scheduling parameters.

The command used to associate an egress scheduler policy on the port is also used for the HSMDA. HSMDA policies should be associated with HSMDA ports.

The no form of this command removes a port scheduler policy from an egress port or channel. Once the scheduler policy is removed, all orphaned policers, queues, and schedulers revert to a free running state governed only by the local queue or scheduler parameters. This includes any queues or schedulers with a port-parent association.

Parameters 
port-scheduler-policy-name—
Specifies an existing port-scheduler-policy configured in the config>qos context. The name can be up to 32 characters.

elmi

Syntax 
elmi
Context 
config>port>ethernet
Description 

This command configures Ethernet Local Management Interface (E-LMI) parameters for the Ethernet port. E-LMI is only supported on Ethernet access ports with Dot1q encapsulation type.

mode

Syntax 
mode {none | uni-n}
Context 
config>port>ethernet>elmi
Description 

This command configures the Ethernet LMI mode.

Parameters 
none—
Specifies that the E LMI mode is set to none.
uni-n—
Specifies that the E LMI mode is set to UNI-N.

n393

Syntax 
n393 [value]
no n393
Context 
config>port>ethernet>elmi
Description 

This command configures the monitored count of consecutive errors.

Parameters 
value—
Specifies the monitored count of consecutive errors.
Values—
2 to 10

 

t391

Syntax 
t391 [value]
no t391
Context 
config>port>ethernet>elmi
Description 

This command configures the polling timer for UNI-C.

Parameters 
value—
Specifies the polling timer for UNI-C.
Values—
5 to 30

 

t392

Syntax 
t392 [value]
no t392
Context 
config>port>ethernet>elmi
Description 

This command configures the polling verification timer for UNI-N.

Parameters 
value—
Specifies the polling verification timer for UNI-N.
Values—
5 to 30

 

mode

Syntax 
mode {access | network | hybrid}
no mode
Context 
config>lag
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command configures an Ethernet port, TDM channel, or SONET/SDH path (sub-port) for access, network or hybrid mode operation.

An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path. Note that ATM, Frame Relay, and cHDLC port parameters can only be configured in the access mode.

An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path. Note that ATM, Frame Relay, and cHDLC port parameters can only be configured in the access mode.

A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.

When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.

A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation.

When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* also supported.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces.

When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values. The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <port-id>:qtag1.*. An outer VLAN tag qtag2 of * creates an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.

The no form of this command restores the default.

Default 

mode network — Configures the Ethernet port, TDM channel or SONET path for transport network use.

mode access — Default channel/port mode for channelized, ASAP, and ATM MDAs.

Special Cases 
SONET/SDH Path—
When network mode is selected, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.
Parameters 
network—
Configures the Ethernet port, TDM channel or SONET path as service access.
access—
Configures the Ethernet port, TDM channel or SONET path for transport network use.
hybrid—
Configures the Ethernet port for hybrid use.

mac

Syntax 
mac ieee-address
no mac
Context 
config>eth-tunnel
config>lag
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), Ethernet tunnel, or BCP-enabled port or sub-port.

Only one MAC address can be assigned to a port. When multiple mac commands are entered, the last command overwrites the previous command. When the command is issued while the port is operational, IP will issue an ARP, if appropriate, and BPDUs are sent with the new MAC address.

The no form of this command returns the MAC address to the default value.

Default 

A default MAC address is assigned by the system from the chassis MAC address pool.

Parameters 
ieee-address—
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

mtu

Syntax 
mtu mtu-bytes
no mtu
Context 
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command configures the maximum payload MTU size for an Ethernet port, PPP-enabled port or sub-port and Frame Relay-enabled port or subport. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive. Packets that cannot be fragmented at egress and exceed the MTU are discarded.

The value specified for the MTU includes the destination MAC address, source MAC address, the Ethertype or Length field and the complete Ethernet payload. The MTU value does not include the preamble, start of frame delimiter or the trailing CRC.

PoS channels use the MTU to define the largest PPP payload a PoS frame may contain. A significant difference between SONET/SDH PoS channel and Ethernet physical MTU values the overhead considered part of the framing method and the overhead considered to be part of the application using the frame. In Ethernet, the preamble, start of frame delimiter and the CRC are considered part of the framing overhead and not part of the frame payload. For a PoS channel, the HDLC framing overhead is not included in the physical MTU; only the PPP and PPP payload are included. If the port mode or encapsulation type is changed, the MTU assumes the default values of the new mode or encapsulation type.

The no form of this command restores the default values.

Default 

The default MTU value depends on the (sub-)port type, mode and encapsulation and are listed in Table 45:

Table 45:  Default MTU Values 

Type

Mode

Encap Type

Default (Bytes)

10/100, Gig, or 10GigE

Access

null

1514

10/100, Gig, or 10GigE

Access

dot1q

1518

10/100, Gig, or 10GigE

Access

q-in-q

1522

SONET/SDH or TDM

Access

mpls

1506

SONET/SDH or TDM

Access

bcp-null

1518

SONET/SDH or TDM

Access

bcp-dot1q

1522

SONET/SDH or TDM

Access

ipcp

1502

SONET/SDH or TDM

Access

frame-relay

1578

ATM, SONET/SDH or TDM

Access

atm

1524

10/100 or 100FX Ethernet

Network

null

1514

10/100 or 100FX Ethernet

Network

dot1q

1518

SONET/SDH

Network

ppp-auto

1524

Parameters 
mtu-bytes —
Sets the maximum allowable size of the MTU, expressed as an integer.
Values—

512 to 9212

config>port>ethernet

512 to 9208

config>port>sonet-sdh>path

512 to 9208

config>port>tdm>ds1>channel-group

512 to 9208

config>port>tdm>ds3

512 to 9208

config>port>tdm>e1>channel-group

512 to 9208

config>port>tdm>e3

 

network

Syntax 
network
Context 
config>port>tdm>ds1>channel-group
config>port>tdm>e1>channel-group
Description 

This command enables the context to configure network channel group parameters.

queue-policy

Syntax 
queue-policy name
no queue-policy
Context 
config>port>tdm>ds1>channel-group>network
config>port>tdm>e1>channel-group>network
Description 

This command specifies an existing network policy to apply to the channel group.

Parameters 
name—
Specifies an existing network-queue policy name. The name can be up to 32 characters.

queue-policy

Syntax 
queue-policy name
no queue-policy
Context 
config>card>mda>network>ingress
config>port>sonet-sdh>path>network
Description 

This command specifies the network-queue policy which defines queue parameters such as CBS, high priority only burst size, MBS, CIR and PIR rates, as well as forwarding-class to queue mappings. The network-queue policy is defined in the config>qos>network-queue context.

Default 

queue-policy default

Parameters 
name—
Specifies an existing network-queue policy name. The name can be up to 32 characters long.

ppp

Syntax 
ppp
Context 
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command enables access to the context to configure the LCP operational parameters for a SONET/SDH PoS link, a DS--3/E-3 port or channel, a DS-1/E-1 channel or a DS-0 channel.

compress

Syntax 
compress {acfc [pfc] | pfc [acfc]}
no compress
Context 
config>port>tdm>ds1>channel-group>ppp
config>port>tdm>e1>channel-group>ppp
Description 

This command enables and disables Protocol Field Compression (PFC) per RFC 1661, The Point-to-Point Protocol (PPP), Section 6.5 and Address and Control Field Compression (ACFC) as per Section 6.6.

This command is only supported on DS-1 and E-1 channel groups on ASAP MDAs.

The no form of the command disables the header compression.

Default 

no compress

Parameters 
acfc—
Specifies address and control field compression.
pfc—
Specifies protocol field compression.

ber-sf-link-down

Syntax 
[no] ber-sf-link-down
Context 
config>port>tdm>ds1>channel-group>ppp
config>port>tdm>e1>channel-group>ppp
Description 

This command enables the port down on BER-SF alarm. When enabled, the link will be placed out of service once ber-sf is detected.

The no form of the command reverts to normal operation where the link remains in-service when ber-sf is encountered.

Default 

no ber-sf-link-down

report-alarm

Syntax 
[no] report-alarm [ais] [los] [oof] [rai] [looped]
Context 
config>port>tdm> ds3
config>port>tdm> e3
Description 

This command enables logging of DS-3 and E-3 alarms for a DS-3/E-3 port or channel.

The no form of this command disables logging of the specified alarms.

Parameters 
ais—
Reports alarm indication signal errors. When configured, ais alarms are not raised and cleared.
Default—
ais alarms are issued
los —
Reports loss of signal errors. When configured, los traps are not raised and cleared.
Default—
los traps are issued
oof —
Reports out-of-frame errors. When configured, oof alarms are not raised and cleared.
Default—
oof alarms are not issued
rai —
Reports resource availability indicator events. When configured, rai events are not raised and cleared.
Default—
rai alarms are not issued
looped—
Reports looped packets errors.
Default—
looped alarms are not issued

scramble

Syntax 
[no] scramble
Context 
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command enables payload scrambling on channel groups.

Scrambling randomizes the pattern of 1s and 0s carried in a SONET frame. Rearranging or scrambling the pattern prevents continuous strings of all 1s or all 0s and meets the needs of physical layer protocols that rely on sufficient transitions between 1s and 0s to maintain clocking.

For ATM, this command enables or disables ATM cell-level payload scrambling/descrambling using x43+1 polynomial as defined in ITU-T I.432.1. Scrambling is enabled by default for the ATM path/channel. Note that this scrambling is done in addition to SONET/SDH frame scrambling/descrambling, which is always enabled in the framer.

The no form of this command disables scrambling.

Default 

no scramble

keepalive

Syntax 
keepalive time-interval [dropcount drop-count]
no keepalive
Context 
config>port>sonet-sdh>path>ppp
config>port>tdm>ds1>channel-group>cisco-hdlc
config>port>tdm>ds1>channel-group>ppp
config>port>tdm>ds3>ppp
config>port>tdm>e1>channel-group>ppp
config>port>tdm>e3>ppp
Description 

This command sets the keepalive interval.

The no form of this command returns the interval to the default value.

Default 

keepalive 10

Parameters 
time-interval—
Specifies the time, in seconds, between keepalive messages, expressed as a decimal integer.
Values—
1 to 60

 

drop-count—
Specifies the number of consecutive keepalive failed request attempts or remote replies that can be missed after which the port is operationally downed.
Values—
1 to 255

 

2.20.2.11. Port XC Commands

The port xc commands are supported on the 7450 ESS only.

port-xc

Syntax 
port-xc
Context 
config
Description 

This command enables the context to configure port-cross connect functionality.

pxc

Syntax 
pxc pxc-id [create]
no pxc pxc-id
Context 
config>port-xc
Description 

This command creates a port cross-connect (PXC) object. Referencing an Ethernet port within the PXC object will automatically configure this Ethernet port as a loopback port. The node will automatically create two PXC sub-ports under this Ethernet port. The configuration of PXC sub-ports can be accessed through the CLI.

Parameters 
pxc-id—
Specifies the port cross-connect identifier.
Values—
1 to 64

 

port

Syntax 
port port-id
no port
Context 
config>port-xc>pxc
Description 

This command configures the referenced Ethernet port as a loopback or a cross-connect port (PXC). Once this command is executed, the system automatically creates two PXC sub-ports under this Ethernet port. The two PXC sub-ports are logical configurations used by the node to transmit traffic bi-directionally through a single physical port that is internally cross-connected.

The physical PXC port does not require any external connectivity or optical transceivers to function properly. Consequently, all optic-related alarms are disabled on the port.

The physical PXC port is automatically configured as a hybrid port. The MTU is preset to 9212 bytes, The encapsulation type is set to dot1q and dot1x tunneling is turned on.

Since the PXC is using a single physical port to transmit traffic in both directions, the nominal port bandwidth is asymmetrically divided between the two directions. For example, a 10Gb/s Ethernet port in PXC mode can accommodate nine Gb/s of traffic in one direction and one Gb/s in the other. Any other ratio can be achieved as long as the sum of the bandwidth of the two PXC sub-ports does not exceed the bandwidth capacity of the physical port (10 Gb/s in this case).

The following apply to PXC ports:

  1. Only unused physical ports (not associated with an interface or SAP) can be referenced inside of a PXC ID configuration.
  1. Once inside of a PXC ID configuration, the physical port cannot be removed from that PXC ID configuration if the corresponding PXC sub-ports are currently in use.
  1. Once inside of a PXC ID configuration, the physical port cannot be used outside of the PXC context. For example, a regular IP interface cannot use this physical port, or a SAP on that port cannot be associated with a service.
  1. A physical port can be associated with only one PXC ID configuration.
Parameters 
port-id—
Specifies the physical port in the slot/mda/port format.

pxc-pxc-id.sub-port-id

Syntax 
pxc-pxc-id.sub-port-id
Context 
config>port
Description 

This command enables access to PXC sub-port level parameters. The PXC sub-ports are automatically created once the external Ethernet port is configured inside of an PXC object. The PXC sub-ports are by default administratively disabled (shutdown). In order for PXC sub-ports to became operational, both, the underlying external Ethernet port and the PXC object must be operationally up.

Parameters 
pxc-id—
Specifies the unique identifier of this PXC.
Values—
1 to 64

 

sub-port-id—
When this the pxc-id is configured, two logical sub-ports are automatically created. These logical sub-ports are used to create two paths within the loop; one upstream path, and one downstream path. These sub-ports are destroyed when either this PXC row is destroyed, this object is de-provisioned.
Values—
a, b

 

2.20.2.12. Forwarding Path Extension (FPE) Commands

fwd-path-ext

Syntax 
fwd-path-ext
Context 
config
Description 

This command provides context for configuring Forwarding Path Extensions (FPE). FPE is utilized by certain applications that rely on PXC functionality. Its purpose is to simplify configuration of such applications.

fpe

Syntax 
fpe fpe-id [create]
no fpe fpe-id
Context 
config>fwd-path-ext
Description 

This command configures an FPE object which associates the application with a PXC (paired set of PXC sub-ports or a paired set of PXC based LAGs).

The no form of the command disables the FPE object association.

Parameters 
fpe-id—
Specifies the FPE ID.
Values—
1 to 64

 

create —
Keyword used to associate the queue group. The create keyword requirement can be enabled or disabled in the environment>create context.

path

Syntax 
path xc-a lag-id xc-b lag-id
path pxc pxc-id
no path
Context 
config>fwd-path-ext>fpe
Description 

This command references a PXC (pair of PXC sub-ports) and consequently create an association between the PXC and the application which is referenced under the same FPE object. Each application will utilize the PXC in the form of an internal cross-connect. The exact use and internal provisioning of this cross-connect depends on the application itself.

The no form of the command removes the reference and association from the configuration.

Default 

no path

Parameters 
xc-a lag-id
Specifies the LAG identifier associated with one side of the cross-connect. The operator has the freedom to associate xc-a with LAG ID containing either sub-ports.a or sub-ports.b. In other words, the system does not perform automatic check that will ensure a match between xc-a and the LAG ID containing sub-ports.a.
Values—
1 to 800

 

xc-b lag-id
Specifies the LAG identifier associated with one side of the cross-connect. The operator has the freedom to associate xc-a with LAG ID containing either sub-ports.a or sub-ports.b.
Values—
1 to 800

 

pxc-id
Specifies the PXC identifier, the PXC construct that contains a physical port in a loopback mode that provides the cross-connect capability. The system creates two paired sub-ports on top of this physical port and each of these two sub-ports forwards traffic in one direction over the loopback. One sub-port is associated with the transit side of the loopback, while the other sub-port is associated with the termination side (see PXC Configuration Guides for further explanation).
Values—
1 to 64

 

pw-port

Syntax 
[no] pw-port
Context 
config>fwd-path-ext>fpe
Description 

This command informs the system about the type of the cross-connect that is required in order to terminate an external tunnel to an anchored PW port. The system automatically builds the internal infrastructure required to perform the tunnel termination on a PW port.

PW ports support the following types of tunnels:

  1. GRE/MPLS PW
    with SDP of type MPLS or GRE
  2. L2oGRE
    bridged Ethernet over GRE, where GRE protocol number is 0x6558

The no form of the command removes the cross-connect type from the configuration.

Default 

no pw-port

sub-mgmt-extensions

Syntax 
[no] sub-mgmt-extensions
Context 
config>fwd-path-ext>fpe
Description 

This command configures FPE for subscriber management extensions. The FPE cannot be used for other applications but can be used for multiple subscriber management applications.

The no version of this command disables FPE for subscriber management extensions.

Default 

no sub-mgmt-extensions

vxlan-termination

Syntax 
vxlan-termination [router router-name]
vxlan-termination service-name service-name
no vxlan-termination
Context 
config>fwd-path-ext>fpe
Description 

This command informs the system about the cross-connect type that is required for non-system IPv4 and IPv6 VXLAN termination. Internally, it triggers the automatic creation of two internal IP interfaces in the PXC ports and enables those internal interfaces to process and terminate VXLAN.

If no parameters are used, the VXLAN termination occurs in the base router; however, when the FPE is used for static VXLAN termination (no BGP-EVPN services), non-system IPv4 and IPv6 VXLAN can be terminated in a VPRN service. In this case, the VPRN router instance or service name must be configured with the vxlan-termination command.

The no form of the command disables the cross-connect type from the configuration.

Default 

no vxlan-termination

Parameters 
router-name
Specifies the router instance for VXLAN termination.
Values—

router-name : router-name or vprn-svc-id

router-name

“Base”

vprn-svc-id

1 to 2147483647

 

Default—
Base
service-name
Specifies the service name that identifies the VPRN for VXLAN termination, up to 64 characters.

sdp-id-range

Syntax 
sdp-id-range from id to id
no sdp-id-range
Context 
config>fwd-path-ext
Description 

This command reserves an SDP ID range used by the FPE based PW-Port and VXLAN termination applications.

Each configured FPE based PW-Port is associated with two internal SDPs (one in each direction) whose id(s) are allocated from the configured sdp-id-range.

When the FPE is associated to VXLAN termination, an internal SDP is allocated from the configured sdp-id-range and is used for R-VPLS services that terminate VXLAN IPv6. A spoke-sdp per VXLAN IPv6 R-VPLS service is created on that SDP for egress processing of the packets. Sdp-id-range cannot be modified if any of its IDs are currently in use.

Default 

no sdp-id-range

Parameters 
from id
Specifies the start of the SDP ID range (inclusive).
Values—
1 to 17407

 

to id
Specifies the end of the SDP ID range.
Values—
1 to 17407

 

2.20.2.13. APS Commands

aps

Syntax 
aps
Context 
config>port
Description 

This command configures APS (Automatic Protection Switching). APS is used by SONET/SDH add/drop multiplexers (ADMs) or other SONET/SDH-capable equipment to protect against circuit or equipment failure.

An APS group contains a working and a protect circuit and can span a single node (SC-APS) or two nodes (MC-APS).

The working and protection configurations on the 7750 SRs must match the circuit configurations on the peer. This means that the working circuit on the 7750 SR must be connected to the peer’s working circuit and the protect circuit must be connected to the peer’s protection circuit.

The aps command is only available for APS groups and not physical ports.

advertise-interval

Syntax 
advertise-interval advertise-interval
no advertise-interval
Context 
config>port>aps
Description 

This command specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for multi-chassis APS.

The advertise-interval value is valid only for a multi-chassis APS as indicated by the value of the neighbor command value if it is not set to 0.0.0.0.

Default 

10

Parameters 
advertise-interval—
Specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for multi-chassis APS.
Values—
10 to 650

 

hold-time

Syntax 
hold-time hold-time
no hold-time
Context 
config>port>aps
Description 

This command specifies how much time can pass, in 100s of milliseconds, without receiving an advertise packet from the neighbor before the multi-chassis signaling link is considered not operational.

The hold-time is usually 3 times the value of the advertise-interval. The value of the advertise-interval is valid only for a multi-chassis APS as indicated by the value of neighbor IP address if it is not set to 0.0.0.0.

Parameters 
hold-time—
Specifies how long to wait for an APS advertisement packet before the peer in a Multi-Chassis APS group is considered operationally down.
Values—
10 to 650

 

hold-time-aps

Syntax 
hold-time-aps [lsignal-failure sf-time] [lsignal-degrade sd-time]
no hold-time-aps
Context 
config>port>aps
Description 

This command configures hold-down timers to debounce signal failure conditions (lais, b2err-sf) and signal degrade conditions (b2err-sd) for Uni 1+1 Sig+Data APS switching mode (switching mode uni-1plus1).

The no version of this command resets the hold-down timer to the default value.

Default 

0 (disabled)

Parameters 
sf-time—
Specifies an integer to define the signal failure hold-down time in milliseconds.
Values—
1 to 100

 

sd-time —
Specifies an integer to define the signal degrade hold-down time in milliseconds.
Values—
1 to 100

 

mode-annexb

Syntax 
[no] mode-annexb
Context 
config>port>aps
Description 

This command configures the APS group for 1+1 Optimized operation as described in Annex B of ITU.T G.841. Note that Annex B operates in non-revertive bi-directional switching mode only as defined in G.841.

neighbor

Syntax 
neighbor ip-address
no neighbor
Context 
config>port>aps
Description 

This command specifies the neighbor's IP address only on a multi-chassis APS where the working and protect circuits are configured on different routers. When the value the neighbor IP address is set to 0.0.0.0, this implies that the APS group is configured as a single-chassis APS group.

The route to the neighbor must not traverse the multi-chassis APS member (working or protect) circuits. It is recommended that the neighbor IP address configured is on a shared network between the routers that own the working and protect circuits.

By default no neighbor address is configured and both the working and protect circuits should be configured on the same router (i.e., single-chassis APS). APS is assumed to be configured wholly on a single chassis.

Parameters 
ip-address—
Specifies the neighbor's IP address only on a multi-chassis APS where the working and protect circuits are configured on different routers. The node should be connected with a direct interface to ensure optimum fail-over time.
Values—

ipv4-address:

a.b.c.d

ipv6-address:

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x:-[0 to FFFF]H

d: [0 to 255]D

 

protect-circuit

Syntax 
protect-circuit port-id
no protect-circuit
Context 
config>port>aps
Description 

This command configures a physical port that will act as the protection circuit for this APS group. The protect circuit port must contain only the default configuration and cannot belong to another APS group. The protect circuit port must be of the same type as the working circuit for the APS group, for the port to be added to an APS group port. If that’s not the case, the command will return an error.

A protection circuit can only be added if the working circuit already exists; the protection circuit must be removed from the configuration before the working circuit is removed.

When a port is a protect-circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context is not allowed for that port unless it is part of the noted exceptions. The exception list includes these SONET/SDH commands:

  1. clock-source
  2. [no] loopback
  3. [no] report-alarm
  4. section-trace
  5. [no] threshold

When is port configured as a protection circuit of an APS group, the configurations described above and all service configurations related to APS port are operationally inherited by the protect circuit. If the protect circuit cannot inherit the configurations (due to resource limitations), the configuration attempt fails and an error is returned to the user.

The protect circuit must be shutdown before it can be removed from the APS group port. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.

The no form of this command removes the protect-circuit.

Parameters 
port-id—
Specifies the physical port that will act as the protection circuit for this APS group in the following format.

port-id

slot/mda/port

eth-sat-id

esat-id/slot/port

esat

keyword

id

1 to 20

pxc-id

pxc-id.sub-port

pxc

keyword

id

1 to 64

sub-port

a, b

Also see Modifying Hold-Down Timer Values for information about modifying the timer defaults in the event of communication delays between the APS controllers.

rdi-alarms

Syntax 
rdi-alarms [suppress | circuit]
Context 
config>port>aps
Description 

This command configures how RDI alarms (line, path, section) are generated on physical circuits of an APS ports. The command configuration changes are supported only for switching-mode set to uni_1plus1. The configuration can be changed only when no working and protecting circuit has been added. Options:

  1. circuit–RDI alarms are H/W-generated independently on each working and protect circuit based on RX failure of that circuit regardless of APS line status.
  2. suppress–RDI H/W generation on working and protect circuits is suppressed. No alarms are generated on RX failure of that circuit.
Default 

rdi-alarms circuit

revert-time

Syntax 
revert-time minutes
no revert-time
Context 
config>port>aps
Description 

This command configures the revert-time timer to determine how long to wait before switching back to the working circuit after that circuit has been restored into service.

A change in the minutes value takes effect upon the next initiation of the wait to restore (WTR) timer. It does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.

The no form of this command restores the default (non-revertive mode).

Default 

The default is to not revert back unless the protect circuit fails or there is an operator intervention.

Parameters 
minutes—
Specifies the time, in minutes, to wait before reverting back to the original working circuit after it has been restored into service.
Values—
0 to 60 minutes

 

Default—
5

switching-mode

Syntax 
switching-mode {bi-directional | uni-directional | uni-1plus1}
Context 
config>port>aps
Description 

This command configures the switching mode for the APS group.

Parameters 
bi-directional—
Configures the group to operate in Bidirectional 1+1 Signaling APS mode.
uni-directional—
Configures the group to operate in Unidirectional 1+1 Signaling APS mode.
uni-1plus1—
Configures the group to operate in Unidirectional 1+1 Signaling and Datapath APS mode (7750 SR-c4/c12 platforms only).

working-circuit

Syntax 
working-circuit port-id [number number]
no work-circuit [number number]
Context 
config>port>aps
Description 

This command configures a physical port that will act as the working circuit for this APS group. The working circuit port must contain only the default configuration and cannot be part of another APS group. The working circuit must be created before the protection circuit.

When a port is a working circuit of an APS group, the configuration available under config>port port-id context (including submenus) is not allowed for that port unless it is a part of the noted exceptions.

When a port is being configured as a working circuit of an APS group, all common configuration as described above and all service configurations related to the APS port is operationally inherited by the working circuit from the aps-group-id. If the working circuit cannot inherit that configuration, for example, due to resource limitations, the configuration attempt fails and an error is returned to the user.

Before a working circuit can be removed from an APS group, the working circuit port must be shutdown. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.

Note that all configurations for aps-group-id under the config>port context and its submenus and all configuration for services that use this aps-group-id is preserved as a non-activated configuration since the APS group no longer has any physical circuits assigned.

The no form of this command removes the working-circuit. The working circuit can only be removed from the configuration after the protect circuit has been removed.

Parameters 
port-id—
Specifies the physical port that will act as the working circuit for this APS group in the following format:

port-id

slot/mda/port

eth-sat-id

esat-id/slot/port

esat

keyword

id

1 to 20

pxc-id

pxc-id.sub-port

pxc

keyword

id

1 to 64

sub-port

a, b

number—
Specifies the APS channel number; value is 1 or 2.

Modifying Hold-Down Timer Values

Note that for APS configurations, the hold-time down and hold-time up default values are 100 ms and 500 ms respectively. But, if there is a large difference in the transmission delay between the APS working (working-circuit) and protect line (protect-circuit), it is highly recommended that you increase the default timer on the working line accordingly with the transmission delay present on the protect line.

The following output shows an example of the timers on POS interfaces.

A:NS044050253# show port aps-1
===============================================================================
SONET/SDH Interface
===============================================================================
Description        : APS Group
Interface          : aps-1                  Speed                : oc3         
Admin Status       : up                     Oper Status          : up          
Physical Link      : Yes                    Loopback Mode        : none        
Single Fiber Mode  : No                                                        
Clock Source       : node                   Framing              : sonet       
Last State Change  : 04/11/2007 13:53:01    Port IfIndex         : 1358987264  
J0 String          : 2/1/5 7750-SR-7        Section Trace Mode   : string      
Rx S1 Byte         : 0x00 (stu)             Rx K1/K2 Byte        : 0x00/0x00
Tx S1 Byte         : 0x0f (dnu)             Tx DUS/DNU           : disabled   
Rx J0 String (Hex) : 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       
Cfg Alarm          : loc lais lrdi ss1f lb2er-sd lb2er-sf slof slos lrei   
Alarm Status       :                                                       
Hold time up       : 500 milliseconds                                      
Hold time down     : 100 milliseconds 
===============================================================================
Port Statistics
=============================================================================== 
Input                 Output
-------------------------------------------------------------------------------
Packets                                          6670498                3804661
Discards                                               0                      0
Unknown Proto Discards                                 0                       
===============================================================================
A:NS044050253# 
 
 
For unprotected port these timer are different:
A:NS044050253# show port 2/2/2
===============================================================================
SONET/SDH Interface
===============================================================================
Description        : OC-48 SONET/SDH
Interface          : 2/2/2                  Speed                : oc48        
Admin Status       : up                     Oper Status          : up          
Physical Link      : Yes                    Loopback Mode        : none        
Single Fiber Mode  : No                                                        
APS Group          : none                   APS Role             : none        
Clock Source       : loop                   Framing              : sonet       
Last State Change  : 04/11/2007 14:53:53    Port IfIndex         : 37814272    
J0 String          : 0x01                   Section Trace Mode   : byte        
Rx S1 Byte         : 0x00 (stu)             Rx K1/K2 Byte        : 0x00/0x00   
Tx S1 Byte         : 0x0f (dnu)             Tx DUS/DNU           : disabled
Rx J0 String (Hex) : af 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       
Cfg Alarm          : loc lrdi lb2er-sf slof slos                           
Alarm Status       :                                                       
Hold time up       : 500 milliseconds                                      
Hold time down     : 0 milliseconds 
Transceiver Data
 
Transceiver Type   : SFP                                             
Model Number       : SFP-OC48-SR1                                    
Transceiver Code   : OC48 SR                                         
Laser Wavelength   : 1310                   Diag Capable         : yes         
Connector Code     : LC                     Vendor OUI           : 00:01:9c    
Manufacture date   : 2004/08/20 00:00:00    Media                : SONET/SDH   
Serial Number      : 6331000705                                      
Part Number        : CT2-MS1LBTD32Z2                                 
Optical Compliance*: 00:01:00:00:00:00:00:00                         
Link Len 9u        : 2 kms                  Link Len Cu          : 0 m         
Link Len 9u        : 20 * 100m              Link Len 62.5u       : 0 * 10m     
Link Len 50u       : 0 * 10m 
===============================================================================
Port Statistics
===============================================================================
                                                   Input                 Output
-------------------------------------------------------------------------------
Packets                                          3870094                6656408
Discards                                               0                      0
Unknown Proto Discards                                 0                       
===============================================================================
A:NS044050253# 

wtr-annexb

Syntax 
wtr-annexb minutes
Context 
config>port>aps
Description 

This command waits to restore for Annex B mode operation. The delay after which the newly active section becomes the primary section after a switch-over from the primary section to the secondary section occurs and the switch request clears normally.

Parameters 
minutes—
Specifies the time, in minutes, to wait to restore for Annex B mode operation.
Values—
0 to 60

 

Default—
5

2.20.2.14. Ethernet Port Commands

ethernet

Syntax 
ethernet
Context 
config>port
Description 

This command enables access to configure Ethernet port attributes.

This context can only be used when configuring Fast Ethernet, gigabit, or 10-Gb Ethernet LAN ports on an appropriate MDA.

mode

Syntax 
mode {access | network | hybrid}
no mode
Context 
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>ds1>channel-group
config>port>tdm>ds3
config>port>tdm>e1>channel-group
config>port>tdm>e3
Description 

This command configures an Ethernet port for access, network, or hybrid mode of operation. It also configures a TDM channel or SONET/SDH path (sub-port) for access or network mode operation.

An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path. Once an Ethernet port, a TDM channel or a SONET path has been configured for access mode, multiple services can be configured on the Ethernet port, a TDM channel or SONET path. Note that ATM, Frame Relay, and cHDLC port parameters can only be configured in the access mode.

A network port or channel participates in the service provider transport or infrastructure network when a network mode is selected. When the network option is configured, the encap-type cannot be configured for the port/channel.

When network mode is selected on a SONET/SDH path, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed. The same applies for MPLS, MPLSCP, and OSICP. When configuring a SONET/SDH port, the mode command must be entered in the channel context or an error message is generated.

A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured as either dot1q or QinQ encapsulation.

When the hybrid port is configured to the dot1q encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. A SAP of format <port-id>:* also supported.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface. The 4096 VLAN tag space on the port is shared among VLAN SAPs and VLAN network IP interfaces.

When the hybrid port is configured to QinQ encapsulation, the user configures a SAP inside a service simply by providing the SAP ID which must include the port-id value of the hybrid mode port and the outer and inner VLAN tag values. The format is <port-id>:qtag1.qtag2. A SAP of format <port-id>: qtag1.* is also supported. The outer VLAN tag value must not have been used to create an IP network interface on this port. In addition, the qtag1.qtag2 value combination must not have been used by another SAP on this port.

The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and a VLAN tag value. The format is <port-id>:qtag1.*. An outer VLAN tag qtag2 of * creates an IP network interface. In addition, the qtag1.qtag2 value combination must not have been used on another SAP or IP network interface on this port.

The no form of this command restores the default.

Default 

mode network — For Ethernet ports.

mode access — For TDM channel or SONET paths.

Parameters 
access—
Configures the Ethernet port, TDM channel or SONET path as service access.
network—
Configures the Ethernet port, TDM channel or SONET path for transport network use.
hybrid—
Configures the Ethernet port for hybrid use.

access

Syntax 
access
Context 
config>port>ethernet
Description 

This command configures Ethernet access port parameters.

egress

Syntax 
egress
Context 
config>port>ethernet>access
config>port>ethernet>network
Description 

This command configures Ethernet access egress port parameters.

queue-group

Syntax 
queue-group queue-group-name [instance instance-id] [create]
no queue-group queue-group-name [instance instance-id]
Context 
config>port>ethernet>access>egress
config>port>ethernet>access>ingress
Description 

This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of queues identified by a group name. Queue groups created on access ports are used as an alternative queue destination for SAPs.

Within a SAP, a forwarding class may be redirected from the local SAP queue to a port queue group queue. The forwarding classes from multiple SAPs may be redirected to the same queue group which can be used to minimize the number of per-SAP queues.

Queue groups may be created on both access and network oriented ports. When the port is in access mode, the queue groups must be created within the port access node.

Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is supported. Multiple access egress queue groups may be created on a single port and are used by egress SAP forwarding classes. The instance-id parameter identifies different instances of the same queue group template. Creating multiple queue groups with a different instance ID but the same queue group name results in separate queue groups being created on the port. The instance-id parameter is only valid for egress queue groups on access ports.

When the queue group is created in an ingress port context, the group-name must be an existing ingress queue group template. Similarly, queue groups created in an egress port context must have a group-name of an existing egress queue group template. Two ingress queue groups with the same name cannot be created on the same port. Two egress queue groups can only be created on the same port with the same queue group template name if they have different instance-id values.

The queues defined in the template are created on the queue group. The queue parameters within the template are used as the default queue parameters for each queue in the queue group. The default queue parameters for each queue may be overridden on the queue group with specific queue parameters.

Each queue group supports the application of a scheduler-policy for the purpose of managing the queues within the group into an aggregate SLA. The queues defined within the template may be configured with parent scheduler defining the mapping of a queue to one of the schedulers within the scheduler policy. Egress queue groups also support the agg-rate parameter and the queues in the egress template support the port-parent command. Each command is used for configuring egress port virtual scheduling behavior.

Each queue group allows the application of an accounting policy and the ability to enable and disable collecting statistics. The statistics are derived from the queue counters on each queue within the queue group. The accounting policy defines which queue counters are collected and to which accounting file they will be written.

A queue group does not have an administrative shutdown or no shutdown command. A queue group is considered to be always on once created.

When creating a queue group, the system will attempt to allocate queue resources based on the queues defined in the queue group template. If the appropriate queue resources do not currently exist, the queue group will not be created. Ingress port queue groups do not support the shared-queuing or multipoint-shared queuing behavior.

When the queue group is created on a LAG (Link Aggregation Group), it must be created on the primary port member. The primary port member is the port with the lowest port ID based on the slot, MDA position and port number on the MDA. A queue group created on the primary LAG port will be automatically created on all other port members. If a new port is being added to a LAG with an existing queue group, the queue group must first be created on the port prior to adding the port to the LAG. If the LAG queue group has queue overrides, the queue overrides must also be defined on the port queue group prior to adding the port to the LAG.

A port queue group cannot be removed from the port when a forwarding class is currently redirected to the group. All forwarding class redirections must first be removed prior to removing the queue group.

Parameters 
group-name —
The group-name parameter is required when executing the port queue-group command. The specified group-name must exist as an ingress or egress queue group template depending on the ingress or egress context of the port queue group. Only a single queue group may be created on an ingress port. Multiple queue groups may be created on an egress port.
instance-id —
Specifies the identification of a specific instance of the egress queue-group. This parameter is only valid for egress access port queue groups.
Values—
1 to 65535

 

create —
Keyword used to associate the queue group. The create keyword requirement can be enabled/ disabled in the environment>create context.

egress

Syntax 
egress
Context 
config>port>ethernet
Description 

This command configures Ethernet egress port parameters.

ingress

Syntax 
ingress
Context 
config>port>ethernet>access
Description 

This command configures Ethernet access ingress port parameters.

queue-group

Syntax 
[no] queue-group queue-group-name [instance instance-id] [create]
Context 
config>port>ethernet>access>egr
config>port>ethernet>access>ing
Description 

This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of queues identified by a group name. Queue groups created on access ports are used as an alternative queue destination for SAPs.

Within a SAP, a forwarding class may be redirected from the local SAP queue to a port queue group queue. The forwarding classes from multiple SAPs may be redirected to the same queue group which can be used to minimize the number of per-SAP queues.

Queue groups may be created on both access and network oriented ports. When the port is in access mode, the queue groups must be created within the port access node.

Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is supported. Multiple access egress queue groups may be created on a single port and are used by egress SAP forwarding classes. The instance-id parameter identifies different instances of the same queue group template. Creating multiple queue groups with a different instance ID but the same queue group name results in separate queue groups being created on the port. The instance-id parameter is only valid for egress queue groups on access ports.

When the queue group is created in an ingress port context, the group-name must be an existing ingress queue group template. Similarly, queue groups created in an egress port context must have a group-name of an existing egress queue group template. Two ingress queue groups with the same name cannot be created on the same port. Two egress queue groups can only be created on the same port with the same queue group template name if they have different instance-id values.

The queues defined in the template are created on the queue group. The queue parameters within the template are used as the default queue parameters for each queue in the queue group. The default queue parameters for each queue may be overridden on the queue group with specific queue parameters.

Each queue group supports the application of a scheduler-policy for the purpose of managing the queues within the group into an aggregate SLA. The queues defined within the template may be configured with parent scheduler defining the mapping of a queue to one of the schedulers within the scheduler policy. Egress queue groups also support the agg-rate parameter and the queues in the egress template support the port-parent command. Each command is used for configuring egress port virtual scheduling behavior.

Each queue group allows the application of an accounting policy and the ability to enable and disable collecting statistics. The statistics are derived from the queue counters on each queue within the queue group. The accounting policy defines which queue counters are collected and to which accounting file they will be written.

A queue group does not have an administrative shutdown or no shutdown command. A queue group is considered to be always on once created.

When creating a queue group, the system will attempt to allocate queue resources based on the queues defined in the queue group template. If the appropriate queue resources do not currently exist, the queue group will not be created. Ingress port queue groups do not support the shared-queuing or multipoint-shared queuing behavior.

When the queue group is created on a LAG (Link Aggregation Group), it must be created on the primary port member. The primary port member is the port with the lowest port ID based on the slot, MDA position and port number on the MDA. A queue group created on the primary LAG port will be automatically created on all other port members. If a new port is being added to a LAG with an existing queue group, the queue group must first be created on the port prior to adding the port to the LAG. If the LAG queue group has queue overrides, the queue overrides must also be defined on the port queue group prior to adding the port to the LAG.

A port queue group cannot be removed from the port when a forwarding class is currently redirected to the group. All forwarding class redirections must first be removed prior to removing the queue group.

Parameters 
queue-group-name—
The group-name parameter is required when executing the port queue-group command. The specified group-name must exist as an ingress or egress queue group template depending on the ingress or egress context of the port queue group. Only a single queue group may be created on an ingress port. Multiple queue groups may be created on an egress port.
instance-id—
Specifies the identification of a specific instance of the queue-group.
Values—
1 to 65535

 

create—
Keyword used to associate the queue group. The create keyword requirement can be enabled/disabled in the environment>create context.

agg-rate

Syntax 
[no] agg-rate
Context 
config>port>ethernet>access>egr>qgrp
config>port>ethernet>access>egr>vport
config>port>ethernet>network>egr>qgrp
Description 

This command controls an HQoS aggregate rate limit. It is used in conjunction with the following parameter commands: rate, limit-unused-bandwidth, and queue-frame-based-accounting.

When specified under a VPORT, the agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate/port-scheduler-policy involves removing the existing command and applying the new command.

limit-unused-bandwidth

Syntax 
[no] limit-unused-bandwidth
Context 
config>port>ethernet>access>egr>qgrp>agg-rate
config>port>ethernet>access>egr>vport>agg-rate
config>port>ethernet>network>egr>qgrp>agg-rate
config>port>sonet-sdh>path>access>egress>vport
Description 

This command enables aggregate rate overrun protection on the agg-rate context.

The no form of the command disables aggregate rate overrun protection on the agg-rate context.

queue-frame-based-accounting

Syntax 
[no] queue-frame-based-accounting
Context 
config>port>ethernet>access>egr>qgrp>agg-rate
config>port>ethernet>access>egr>vport>agg-rate
config>port>ethernet>network>egr>qgrp>agg-rate
config>port>sonet-sdh>path>access>egress>vport
Description 

This command enables frame based accounting on all policers and queues associated with the agg-rate context. It is only supported on Ethernet ports but not on HSMDA Ethernet ports. Packet byte offset settings are not included in the applied rate when queue frame-based accounting is configured, regardless of how offsets are applied to the statistics.

The no form of the command disables frame based accounting on all policers and queues associated with the agg-rate context.

rate

Syntax 
rate kilobits-per-second
no rate
Context 
config>port>ethernet>access>egr>qgrp>agg-rate
config>port>ethernet>access>egr>vport>agg-rate
config>port>ethernet>network>egr>qgrp>agg-rate
config>port>sonet-sdh>path>access>egress>vport
Description 

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object (SAP, subscriber, VPORT and so on).

Parameters 
kilobits-per-second —
Specifies the rate limit for the VPORT, in kb/s.
Values—
1 to 3200000000 or max

 

host-match

Syntax 
host-match dest destination-string [create]
no host-match dest destination-string
Context 
config>port>ethernet>access>egr>qgrp
Description 

This command configures host matching for the Ethernet port egress queue-group.

The no form of the command removes host matching for the Ethernet port egress queue-group.

Parameters 
destination-string
Specifies a host match destination string up to 32 characters.
create—
Keyword used to create the host match. The create keyword requirement can be enabled or disabled in the environment>create context.

hs-turbo

Syntax 
[no] hs-turbo-queues
Context 
config>port>ethernet>access>egress>queue-group
config>port>ethernet>network>egress>queue-group
Description 

This command enables or disables HS turbo queues.

hsmda-queue-override

Syntax 
[no] hsmda-queue-override
Context 
config>port>ethernet>access>egress>queue-group
Description 

This command configures HSMDA egress queue overrides parameters.

packet-byte-offset

Syntax 
packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override
Description 

This command configures a packet offset for HSMDA queue accounting.

Parameters 
add-bytes
Specifies the number of bytes to add.
Values—
0 to 31

 

sub-bytes
Specifies the number of bytes to subtract.
Values—
1 to 64

 

queue

Syntax 
queue queue-id [create]
queue queue-id
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override
Description 

This command configures overrides for an HSMDA egress queue.

Parameters 
queue-id
Specifies the queue ID.
Values—
1 to 8

 

create—
Keyword used to create

mbs

Syntax 
mbs {[0 to 2625] kilobytes | [0 to 268800] bytes | default}
no mbs
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override>queue
Description 

This command configures the maximum buffer space override.

rate

Syntax 
rate pir-rate
no rate
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override>queue
Description 

This command configures the peak information rate.

Parameters 
pir-rate
Specifies the pir weight.
Values—
1 to 100000000, or max

 

slope-policy

Syntax 
slope-policy hsmda-slope-policy-name
no slope-policy
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override>queue
Description 

This command configures the slope policy.

Parameters 
hsmda-slope-policy-name
Specifies the HSMDA slope policy name, up to 32 characters.

wrr-weight

Syntax 
wrr-weight weight
no wrr-weight
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override>queue
Description 

This command configures the weighted round robin (WRR).

Parameters 
weight
Specifies the WRR weight value.
Values—
1 to 32

 

secondary-shaper

Syntax 
secondary-shaper secondary-shaper-name
no secondary-shaper
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override
Description 

This command configures the HSMDA egress secondary shaper.

Parameters 
secondary-shaper-name
Specifies the HSMDA secondary shaper name, up to 32 characters.

wrr-policy

Syntax 
wrr-policy wrr-policy-name
Context 
config>port>ethernet>access>egress>queue-group>hsmda-queue-override
Description 

This command configures the HSDMA egress wrr-policy.

Parameters 
wrr-policy-name
Specifies the HSMDA egress WRR policy name, up to 32 characters.

policer-control-policy

Syntax 
policer-control-policy policy-name
no policer-control-policy
Context 
config>port>ethernet>network>egress>queue-group>policer-control-policy
Description 

This command configures the policer control policy for the QoS egress queue-group.

Parameters 
policy-name—
Specifies the name of the policer control policy, up to 32 characters.

queue-overrides

Syntax 
queue-overrides
Context 
config>port>ethernet>access>egr>qgrp
config>port>ethernet>access>ing>qgrp
config>port>ethernet>network>egr>qgrp
Description 

This command enables the context to define optional queue parameter overrides for each queue within the queue group.

queue

Syntax 
queue queue-id [create]
no queue queue-id
Context 
config>port>ethernet>access>egr>qgrp>qover
config>port>eth>network>egr>qgrp>qover
Description 

This command associates a queue for use in a queue group template. The defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue-group object which is created with the queue group template name. Each queue is identified within the template by a queue-id number. The template ensures that all queue groups created with the template’s name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP egress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

The no form of the command removes the queue-id from the configuration.

Parameters 
queue-id—
Specifies the queue ID.
Values—
1 to 8

 

create—
Mandatory when creating an entry.

queue

Syntax 
queue queue-id [create]
no queue queue-id
Context 
config>port>ethernet>access>ing>qgrp>qover
Description 

This command associates a queue for use in a queue group template. The defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue-group object which is created with the queue group template name. Each queue is identified within the template by a queue-id number. The template ensures that all queue groups created with the template’s name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP egress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

The no form of the command removes the queue-id from the configuration.

Parameters 
queue-id—
Specifies the queue ID.
Values—
1 to 32

 

create—
Mandatory when creating an entry.

parent

Syntax 
parent [weight weight] [cir-weight cir-weight]
no parent
Context 
config>port>ethernet>access>egr>qgrp>qover>q
Description 

This command, when used in the queue-overrides context for a queue group queue, defines an optional weight and cir-weight for the queue treatment by the parent scheduler that further governs the available bandwidth given the queue aside from the queue PIR setting. When multiple schedulers and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent bandwidth.

Parameters 
weight
Weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler-name. Any queues or schedulers defined as weighted receive no parental bandwidth until all strict queues and schedulers on the parent have reached their maximum bandwidth or are idle. In this manner, weighted children are considered to be the lowest priority.
Values—
0 to 100

 

Default—
1
cir-weight
Defines the weight the queue will use at the within-cir port priority level. The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Values—
0 to 100

 

adaptation-rule

Syntax 
adaptation-rule [pir adaptation-rule] [cir {max | min | closest}]
no adaptation-rule
Context 
config>port>ethernet>access>egr>qgrp>qover>q
config>port>ethernet>access>ing>qgrp>qover>q
config>port>ethernet>network>egr>qover>q
Description 

This command specifies the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.

The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.

Default 

adaptation-rule pir closest cir closest

Parameters 
pir—
Defines the constraints enforced when adapting the PIR rate defined within the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the rate command is not specified, the default applies.
cir—
Defines the constraints enforced when adapting the CIR rate defined within the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
adaptation-rule—
Specifies the adaptation rule to be used while computing the operational CIR or PIR value.
Values—
max — The max (maximum) option is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
min — The min (minimum) option is mutually exclusive with the max and closest options. When min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command.
closest — The closest parameter is mutually exclusive with the min and max parameter. When closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the rate command.

 

burst-limit

Syntax 
burst-limit {default | size [bytes | kilobytes]}
no burst-limit
Context 
config>port>ethernet>access>egr>qgrp>qover>q
Description 

The queue burst-limit command overrides the shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.

The no form of this command removes the current burst limit override for the queue. The queue’s burst limit is controlled by its defining template.

Default 

no burst-limit

Parameters 
default—
Reverts the queue's burst limit to the system default value.
size—
When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the bytes qualifier must be added following size.
Values—
1 to 13671 kilobytes
1 to 14000000 bytes

 

Default—
No default for size; use the default keyword to specify default burst limit.
bytes—
Specifies that the value given for size must be interpreted as the burst limit in bytes.
kilobytes—
Specifies that the value given for size must be interpreted as the burst limit in kilobytes. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.

cbs

Syntax 
cbs size-in-kbytes
no cbs
Context 
config>port>ethernet>access>egr>qgrp>qover>q
config>port>ethernet>access>ing>qgrp>qover>q
config>port>ethernet>network>egr>qover>q
Description 

This command defines the default committed buffer size for the template queue. Overall, the cbs command follows the same behavior and provisioning characteristics as the cbs command in the queue-group or network QoS policy. The exception is the addition of the cbs-value qualifier keywords bytes or kilobytes.

The no form of this command restores the default CBS size to the template queue.

Default 

cbs default

Parameters 
size-in-kbytes—
The size parameter is an integer expression of the number of kilobytes reserved for the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that no reserved buffers are required by the queue (a minimal reserved size can still be applied for scheduling purposes).
Values—
0 to 1048576 or default

 

drop-tail

Syntax 
drop-tail
Context 
config>port>eth>access>ing>qgrp>qover>q
config>port>eth>access>egr>qgrp>qover>q
config>port>ethernet>network>egr>qgrp>qover>q
Description 

This command enters the context to configure queue drop tail parameters.

low

Syntax 
low
Context 
config>port>eth>access>ing>qgrp>qover>q>drop-tail
config>port>eth>access>egr>qgrp>qover>q>drop-tail
config>port>ethernet>network>egr>qgrp>qover>q>drop-tail
Description 

This command enters the context to configure the queue low drop tail parameters. The low drop tail defines the queue depth beyond which out-of-profile packets will not be accepted into the queue and will be discarded.

percent-reduction-from-mbs

Syntax 
percent-reduction-from-mbs percent
no percent-reduction-from-mbs
Context 
config>port>ethernet>access>egr>qgrp>qover>q>drop-tail>low
config>port>ethernet>access>ing>qgrp>qover>q>drop-tail>low
config>port>ethernet>network>egr>qgrp>qover>q>drop-tail>low
Description 

This command overrides the low queue drop tail as a percentage reduction from the MBS of the queue. For example, if a queue has an MBS of 600 kbytes and this percentage is configured to be 30% for the low drop tail, then the low drop tail will be at 420 kbytes and out-of-profile packets will not be accepted into the queue if its depth is greater than this value, and so will be discarded.

Parameters 
percent—
Specifies the percentage reduction from the MBS for a queue drop tail.
Values—
0 to 100, default

 

mbs

Syntax 
mbs {size [bytes | kilobytes] | default}
no mbs
Context 
config>port>ethernet>access>egr>qgrp>qover>q
config>port>ethernet>access>ing>qgrp>qover>q
config>port>ethernet>network>egr>qgrp>qover>q
Description 

The Maximum Burst Size (MBS) command specifies the default maximum buffer size for the template queue. The value is given in kilobytes.

The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue.

The queue-group or network egress QoS context for mbs provides a mechanism for overriding the default maximum size for the queue.

The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packets RED slope will not force the discard of the packet. Setting proper CBS parameters and controlling CBS oversubscription is one major safeguard to queue starvation (when a queue does not receive its fair share of buffers). Another is properly setting the RED slope parameters for the needs of services on this port or channel.

This command applies to egress queue group queues as the queue-delay is only supported on egress queues. This command the queue-delay command are mutually exclusive.

The no form of this command returns the MBS size assigned to the queue to the value.

Default 

mbs default

Parameters 
size
The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Values—
0 to 1073741824

 

bytes—
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
kilobytes—
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
default—
Specifying the keyword default sets the MBS to its default value.

monitor-depth

Syntax 
[no] monitor-depth
Context 
config>port>eth>access>ing>qgrp>qover>q
config>port>eth>access>egr>qgrp>qover>q
config>port>ethernet>network>egr>qgrp>qover>q
Description 

This command enables queue depth monitoring for the specified queue. This command and the dynamic-mbs command are mutually exclusive on the related queue group queue.

The no form of the command removes queue depth monitoring for the specified queue.

percent-rate

Syntax 
percent-rate pir-percent [cir cir-percent]
Context 
config>port>eth>access>egr>qgrp>qover>q
config>port>ethernet>network>egr>qgrp>qover>q
Description 

This command specifies percent rates (CIR and PIR).

Parameters 
pir-percent—
Specifies the PIR as a percentage.
Values—
0.01 to 100.00

 

cir-percent—
Specifies the CIR as a percentage.
Values—
0.00 to 100.00

 

rate

Syntax 
rate pir-rate [cir cir-rate]
no rate
Context 
config>port>ethernet>access>egr>qgrp>qover>q
config>port>ethernet>access>ing>qgrp>qover>q
config>port>ethernet>network>egr>qover>q
Description 

This command specifies the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default 

rate max cir 0 - The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.

Parameters 
pir-rate—
Defines the administrative PIR rate, in kilobits per second, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values—
1 to 200000000, max

 

Default—
max
cir-rate—
The cir parameter overrides the default administrative CIR used by the queue, in kilobits per second. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer.
Values—
0 to 200000000, max

 

Default—
0

scheduler-override

Syntax 
[no] scheduler-override
Context 
config>port>ethernet>access>egr>qgrp
config>port>ethernet>access>ing>qgrp
Description 

This command specifies the set of attributes whose values have been overridden by management on this virtual scheduler. Clearing a given flag will return the corresponding overridden attribute to the value defined on the ingress or egress queue group template.

The no form of the command removes all of the scheduler overrides and returns the scheduler’s parent weight and CIR weight, and its PIR and CIR to the values configured in the applied scheduler policy.

scheduler

Syntax 
scheduler scheduler-name [create]
no scheduler scheduler-name
Context 
config>port>ethernet>access>egr>qgrp>sched-override
config>port>ethernet>access>ing>qgrp>sched-override
Description 

This command can be used to override specific attributes of the specified scheduler name. A scheduler defines bandwidth controls that limit each child (other schedulers and queues) associated with the scheduler. Scheduler objects are created within the hierarchical tiers of the policy. It is assumed that each scheduler created will have queues or other schedulers defined as child associations. The scheduler can be a child which takes bandwidth from a scheduler in a higher tier. A total of 32 schedulers can be created within a single scheduler policy with no restriction on the distribution between the tiers. The scheduler-name must exist in the applied scheduler policy.

The no form of the command removes the scheduler overrides for the specified scheduler and returns the scheduler’s parent weight and CIR weight, and its PIR and CIR to the values configured in the applied scheduler policy.

Parameters 
scheduler-name—
Specifies the name of the scheduler.
Values—
Valid names consist of any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

 

create —
Creates a new scheduler for this port.

parent

Syntax 
parent [weight weight] [cir-weight cir-weight]
no parent
Context 
config>port>ethernet>access>egr>qgrp>sched-override>scheduler
config>port>ethernet>access>ing>qgrp>sched-override>scheduler
Description 

This command can be used to override the scheduler's parent weight and CIR weight. The weights apply to the associated level/cir-level configured in the applied scheduler policy. The scheduler name must exist in the applied scheduler policy.

The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy - this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the queue group overrides. If the parent scheduler does not exist, causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used; this avoids having non-default weightings for fostered schedulers.

The no form of the command returns the scheduler's parent weight and cir-weight to the value configured in the applied scheduler policy.

Default 

no parent

Parameters 
weight—
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict level defined by the level parameter in the applied scheduler policy. Within the level, all weight values from active children at that level are summed and the ratio of each active child's weight to the total distributes the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.

A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.

Values—
0 to 100

 

cir-weight—
Specifies the relative weight of this scheduler in comparison to other child schedulers and queues at the same cir-level defined by the cir-level parameter in the applied scheduler policy. Within the strict cir-level, all cir-weight values from active children at that level are summed and the ratio of each active child's cir-weight to the total distributes the available bandwidth at that level. A cir-weight is considered to be active when the policer, queue, or scheduler that the cir-weight pertains to has not reached the CIR and still has packets to transmit.

A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.

Values—
0 to 100

 

rate

Syntax 
rate pir-rate [cir cir-rate]
no rate
Context 
config>port>ethernet>access>egr>qgrp>sched-override>scheduler
config>port>ethernet>access>ing>qgrp>sched-override>scheduler
Description 

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler's 'within CIR' distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler's parent scheduler may not have the available bandwidth to meet the scheduler's needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child policers, queues, and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters 
pir-rate—
Specifies the PIR rate. Any other value will result in an error without modifying the current PIR rate.
Values—
1 to 3200000000, max

 

cir-rate—
Specifies the CIR rate. If the CIR is set to max, then the CIR rate is set to infinity. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.
Values—
0 to 3200000000, max, sum

 

scheduler-policy

Syntax 
scheduler-policy scheduler-policy-name
no scheduler-policy
Context 
config>port>ethernet>egress>queue-group
config>port>ethernet>ingress>queue-group
config>port>ethernet>network>egress>queue-group
Description 

This command configures a scheduler policy for the egress queue group.

Parameters 
scheduler-policy-name—
Specifies the scheduler policy name, up to 32 characters.

exp-secondary-shaper

Syntax 
exp-secondary-shaper secondary-shaper-name [create]
Context 
config>port>ethernet>egress
Description 

This command configures the Ethernet egress expanded secondary shaper on this port.

Parameters 
secondary-shaper-name—
Specifies the secondary shaper name to apply to this port, up to 32 characters.
create —
Creates a new secondary shaper for this port.

agg-burst

Syntax 
agg-burst
Context 
config>port>ethernet>egress>exp-secondary-shaper
Description 

This command specifies the aggregate burst limits.

high-burst-increase

Syntax 
high-burst-increase size [bytes | kilobytes]
no high-burst-increase
Context 
config>port>ethernet>egress>exp-secondary-shaper>agg-burst
Description 

This command specifies a high burst increase.

Parameters 
size—
Specifies the shaping burst size.
Values—
0 to 65528

 

bytes—
Specifies to use the size in bytes above the low burst limit to be used as the high burst threshold.
kilobytes—
Specifies to use the size kilobytes above the low burst limit to be used as the high burst threshold.

low-burst-limit

Syntax 
low-burst-limit size [bytes | kilobytes]
no low-burst-limit
Context 
config>port>ethernet>egress>exp-secondary-shaper>agg-burst
Description 

This command specifies a low burst limit.

Parameters 
size—
Specifies the low burst size.
Values—
1 to 327680

 

bytes—
Specifies to use the size in bytes.
kilobytes—
Specifies to use the size in kilobytes.

class

Syntax 
class class-number rate rate [monitor-threshold size-in-kilobytes] [burst-limit size] [bytes | kilobytes]
no class class-number
Context 
config>port>ethernet>egress>exp-secondary-shaper
Description 

This command assigns the low burst maximum class to associate with the Ethernet egress expanded secondary shaper.

The no form of the command returns the class id for the Ethernet egress expanded secondary shaper to the default value.

Parameters 
class-number—
Specifies the class identifier of the low burst max class for the shaper.
Values—
1 to 8

 

rate—
Specifies the rate limit for the secondary shaper.
Values—
max, 1 to 10000000 kb/s

 

size-in-kilobytes
Specifies the monitor threshold for the secondary shaper.
Values—
0 to 8190

 

size—
Specifies the burst limit size.
Values—
1 to 327680

 

bytes—
Specifies to use the size in bytes.
kilobytes—
Specifies to use the size in kilobytes.

low-burst-max-class

Syntax 
low-burst-max-class class
no low-burst-max-class
Context 
config>port>ethernet>egress>exp-secondary-shaper
Description 

This command specifies the class to associate with the Ethernet egress expanded secondary shaper.

The no form of the command returns the class number value for the Ethernet egress expanded secondary shaper to the default value.

Parameters 
class—
Specifies the class number of the class for the secondary shaper.
Values—
1 to 8

 

rate

Syntax 
rate rate [monitor-threshold size-in-kbytes]
no rate
Context 
config>port>ethernet>egress>exp-secondary-shaper
Description 

This command configures the shaper’s metering and optional profiling rates. The metering rate is used by the system to configure the shaper’s PIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on the each packets size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches it's violate (PIR) threshold.

The no form of this command restores the default metering and profiling rate to a policer.

Parameters 
rate—
Specifies the exp-secondary-shaper rate.
Values—
max, 1 to 10000000 kb/s

 

size-in-kbytes—
Specifies the monitor threshold size in kbytes.
Values—
0 to 8190

 

vport

Syntax 
vport name [create]
no vport name
Context 
config>port>ethernet>access>egress
config>port>sonet-sdh>path>access>egress
Description 

This command configures a scheduling node, referred to as virtual port, within the context of an egress Ethernet port. The Vport scheduler operates either like a port scheduler with the difference that multiple Vport objects can be configured on the egress context of an Ethernet port, or it can be an aggregate rate when an egress port-scheduler policy is applied to the port.

The Vport is always configured at the port level even when a port is a member of a LAG.

When a port scheduler policy is applied to a Vport the following command is used:

config>port>ethernet>access>egress>vport>port-scheduler-policy port-scheduler-policy-name

The CLI will not allow the user to apply a port scheduler policy to a Vport if one has been applied to the port. Conversely, the CLI will not allow the user to apply a port scheduler policy to the egress of an Ethernet port if one has been applied to any Vport defined on the access egress context of this port. The agg-rate, along with an egress port-scheduler, can be used to ensure that a given Vport does not oversubscribe the port’s rate.

SAP and subscriber host queues can be port-parented to a Vport scheduler in a similar way they port-parent to a port scheduler or can be port-parented directly to the egress port-scheduler if the agg-rate is used.

Parameters 
name—
Specifies the name of the Vport scheduling node and can be up to 32 ASCII characters in length. This does not need to be unique within the system but is unique within the port or a LAG.

agg-rate

Syntax 
[no] agg-rate
Context 
config>port>sonet-sdh>path>access>egress>vport
config>port>ethernet>access>egress>vport
Description 

This command configures an aggregate rate for the Vport. The agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate/port-scheduler-policy involves removing the existing command and applying the new command.

egress-rate-modify

Syntax 
[no] egress-rate-modify
Context 
config>port>ethernet>access>egress>vport
config>port>sonet-sdh>path>access>egress>vport
Description 

This command applies HQoS Adjustment to a Vport. HQoS Adjustment refers to the dynamic adjustment of the rate limit at an QoS enforcement point within a Nokia router when the multicast traffic stream is disjointed from the unicast traffic stream. This QoS enforcement point within the router represents the physical point further down in the access part of the network where the two streams join each other and potentially can cause congestion.

An example would be a PON port which is shared amongst subscriber’s multicast traffic (single copy of each channel) and subscriber’s unicast traffic. The bandwidth control point for this PON port resides in the upstream Nokia BNG node in the form of a Vport. In the case where the multicast delivery method of the BNG utilizes redirection, the multicast traffic in the BNG will flow outside of the subscriber or the Vport context and thus will bypass any bandwidth enforcement in the Nokia router. To correct this, a Vport bandwidth adjustment is necessary in the router that will account for the multicast bandwidth consumption that is bypassing Vport in the router but is present in the PON port whose bandwidth is controlled by Vport.

An estimate of the multicast bandwidth consumption on the PON port can be made at the Vport level based on the IGMP messages sourced from the subscribers behind the PON port. This process is called HQoS Adjustment.

A multicast channel bandwidth is subtracted from or added to the Vport rate limit according to the received IGMP Join/Leave messages and the channel bandwidth definition policy associated with the Vport (indirectly through a group-interface). Since the multicast traffic on the PON port is shared amongst subscribers behind this PON port, only the first IGMP Join or the last IGMP Leave per multicast channel is tracked for the purpose of the Vport bandwidth modification.

The Vport rate that will be affected by this functionality depends on the configuration:

  1. In case the agg-rate within the Vport is configured, its value will be modified based on the IGMP activity associated with the subscriber under this Vport.
  2. In case the port-scheduler-policy within the Vport is referenced, the max-rate defined in the corresponding port-scheduler-policy will be modified based on the IGMP activity associated with the subscriber under this Vport.

The channel bandwidth definition policy is defined in the mcac policy in the config>router>mcac>policy context. The policy is applied under the group-interface or in case of redirection under the redirected-interface.

The rates in effect can be displayed with the following two commands:

show port 1/1/5 vport name
qos scheduler-hierarchy port port-id vport vport-name

The configuration of a scheduler policy under a VPORT, which is only applicable to Ethernet interfaces, is mutually exclusive with the configuration of the egress-rate-modify parameter.

Context: HQoS Adjustment for Vport is disabled.

host-match

Syntax 
host-match dest description-string [create]
no host-match dest destination-string
Context 
config>port>sonet-sdh>path>access>egress>vport
config>port>ethernet>access>egress>vport
Description 

This command specifies the destination and organization strings to be used for matching subscriber hosts with this Vport.

The parent Vport of a subscriber host queue, which has the port-parent option enabled, is determined by matching the destination string dest string associated with the subscriber and the organization string org string associated with the subscriber host with the strings defined under a Vport on the port associated with the subscriber.

If a given subscriber host queue does not have the port-parent option enabled, it will be foster-parented to the Vport used by this subscriber and which is based on matching the dest string and org string. If the subscriber could not be matched with a Vport on the egress port, the host queue will not be bandwidth controlled and will compete for bandwidth directly based on its own PIR and CIR parameters.

By default, a subscriber host queue with the port-parent option enabled is scheduled within the context of the port’s port scheduler policy.

Parameters 
description-string —
The destination character string. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

mon-port-sch

Syntax 
[no] mon-port-sch
Context 
config>port>ethernet
config>port>ethernet>access>egress>vport
config>port>sonet-sdh>path>access>egress>vport
Description 

This command enables congestion monitoring on an Egress Port Scheduler (EPS) that is applied to a physical port or to a Vport.

Congestion monitoring must be further configured under the port-scheduler CLI hierarchy. Once the congestion monitoring is in effect, the offered rate (incoming traffic) is compared to the configured port-scheduler congestion threshold. The results of these measurements are stored as the number of samples representing the number of times the offered rates exceeded the configured congestion threshold since the last clearing of the stats. Therefore, the results represent the number of times that the port-scheduler that is applied to a port/Vport was congested since the last reset of the stats (via a clear command).

The no form of the command disables congestion monitoring.

Default 

no mon-port-sch

port-scheduler-policy

Syntax 
port-scheduler-policy port-scheduler-policy-name
no port-scheduler-policy
Context 
config>port>ethernet>access>egress>vport
config>port>sonet-sdh>path>access>egress>vport
Description 

This command specifies the destination and organization strings to be used for matching subscriber hosts with this Vport.

The parent Vport of a subscriber host queue, which has the port-parent option enabled, is determined by matching the destination string dest string associated with the subscriber and the organization string org string associated with the subscriber host with the strings defined under a Vport on the port associated with the subscriber.

If a given subscriber host queue does not have the port-parent option enabled, it will be foster-parented to the Vport used by this subscriber and which is based on matching the dest string and org string. If the subscriber could not be matched with a Vport on the egress port, the host queue will not be bandwidth controlled and will compete for bandwidth directly based on its own PIR and CIR parameters.

By default, a subscriber host queue with the port-parent option enabled is scheduled within the context of the port’s port scheduler policy.

The no form of the command removes the port-scheduler-policy-name from the configuration. The agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate/port-scheduler-policy involves removing the existing command and applying the new command.

Parameters 
port-scheduler-policy-name—
Specifies an existing port-scheduler-policy configured in the config>qos context. The name can be up to 32 characters long.

scheduler-policy

Syntax 
scheduler-policy scheduler-policy-name
no scheduler-policy
Context 
config>port>ethernet>access>egress>vport
config>port>sonet-sdh>path>access>egress>vport
Description 

This command configures a scheduler policy for the egress virtual port.

Parameters 
scheduler-policy-name—
Specifies the name of the scheduler policy, up to 32 characters.

autonegotiate

Syntax 
autonegotiate [limited]
no autonegotiate
Context 
config>port>ethernet
Description 

This command enables speed and duplex autonegotiation on Fast Ethernet ports and enables far-end fault indicator support on Gb ports.

There are three possible settings for autonegotiation:

  1. “on” or enabled with full port capabilities advertised
  2. “off” or disabled where there are no autonegotiation advertisements
  3. “limited” where a single speed/duplex is advertised.

When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored.

When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port. Note that disabling autonegotiation on Gb ports is not allowed as the IEEE 802.3 specification for Gb Ethernet requires autonegotiation be enabled for far end fault indication.

If the autonegotiate limited keyword option is specified the port will auto-negotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multi-speed Gb ports to force Gb operation while keeping autonegotiation enabled for compliance with IEEE 801.3.

Router requires that autonegotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed.

The no form of this command disables autonegotiation on this port.

Default 

autonegotiate

Parameters 
limited—
The Ethernet interface will automatically negotiate link parameters with the far end, but will only advertise the speed and duplex mode specified by the Ethernet speed and duplex commands.

dampening

Syntax 
dampening
Context 
config>port>ethernet
Description 

This command enters the context to configure exponential port dampening for an Ethernet port.

Exponential Port Dampening (EPD) reduces the number of physical link transitions reported to upper layer protocols, potentially reducing upper layer protocol churn caused by a faulty link. Penalties are added against a port whenever the port’s physical link state transitions from a link-up state to a link-down state. When the penalties exceed a configurable threshold, port-up and -down transitions are no longer advertised to upper layers and the port’s operational state will remain down until the penalty amount drops below a configurable reuse threshold. Each transition of link-up state to link-down state increments the accumulated penalty value by 1000. The accumulated penalties for a port are reduced at an exponential decay rate according to a configurable half-life parameter.

half-life

Syntax 
half-life half-life max-suppress-time max-time
Context 
config>port>ethernet>dampening
Description 

This command configures the half-life decay time and the maximum period of time for which the port-up state can be suppressed.

The half-life and max-time values must be set at the same time and the ratio of max-time/half-life must be less than or equal to 49 and greater than or equal to 1.

Parameters 
half-life—
Specifies the time, in seconds, that must pass before penalties decay to one-half the initial amount.
Values—
1 to 2000

 

Default—
5
max-time—
Specifies the maximum suppression time, in seconds, which is the time it can take after the physical link comes up before the worst case accumulated penalties have decayed to the reuse threshold. The maximum penalty is derived from the maximum suppression time, half-life, and reuse threshold, using the following equation:

maximum penalty = (reuse threshold) × 2 expo:(max-time/half-life)

Values—
1 to 43200

 

Default—
20

suppress-threshold

Syntax 
suppress-threshold suppress-penalties reuse-threshold reuse-penalties
Context 
config>port>ethernet>dampening
Description 

This command configures the penalties thresholds at which the port state events to the upper layer are to be dampened (suppress threshold) and then permitted (reuse threshold).

Parameters 
suppress-penalties—
Specifies the threshold at which the port-up state is suppressed until the accumulated penalties drop below the reuse threshold again.
Values—
1 to 20000

 

Default—
2000
reuse-penalties—
Specifies the threshold at which the port-up state is no longer suppressed, after the port has been in a suppressed state and the accumulated penalties decay drops below this threshold. The reuse threshold value must be less than the suppress threshold value.
Values—
1 to 20000

 

Default—
1000

dot1q-etype

Syntax 
dot1q-etype value
no dot1q-etype
Context 
config>port>ethernet
Description 

This command specifies the Ethertype expected when the port's encapsulation type is dot1q. Dot1q encapsulation is supported only on Ethernet interfaces.

The no form of this command reverts to the default value.

Parameters 
value—
Specifies the Ethertype to expect, in either decimal or hex.
Values—
1536 to 65535 (0x0600 to 0xffff)

 

Default—
If the encap-type is dot1p, then the default is 0x8100. If the encap-type is qinq, then the default is 0x8100.

duplex

Syntax 
duplex {full | half}
Context 
config>port>ethernet
Description 

This command configures the duplex of a Fast Ethernet port when autonegotiation is disabled.

This configuration command allows for the configuration of the duplex mode of a Fast Ethernet port. If the port is configured to autonegotiate this parameter is ignored.

Default 

duplex full

Parameters 
full—
Sets the link to full duplex mode.
half—
Sets the link to half duplex mode.

efm-oam

Syntax 
efm-oam
Context 
config>port>ethernet
Description 

This command configures EFM-OAM attributes.

accept-remote-loopback

Syntax 
[no] accept-remote-loopback
Context 
config>port>ethernet>efm-oam
Description 

This command enables reactions to loopback control OAM PDUs from peers.

The no form of this command disables reactions to loopback control OAM PDUs.

Default 

no accept-remote-loopback

dying-gasp-tx-on-reset

Syntax 
[no] dying-gasp-tx-on-reset
Context 
config>system>ethernet>efm-oam
config>port>ethernet>efm-oam
Description 

This command enables generation of the Information OAM PDU off-cycle when the soft reset notification is received by the EFM application. The local port state remains under the control of the Soft Reset application and does not change based on this EFM function. If the port is operationally up then the local node will continue to consider the port as available for service data and forwarding. If the upstream node requires notification to route around the local node undergoing the soft reset, notification must be sent to those nodes. This is a disruptive function.

This command is disabled by default at the system level and enabled by default at the port level. The combination of the system-level and port-level configuration determines if the dying gasp on soft reset function is active on individual ports. Both the system-level and port-level commands must be enabled in order to support generation of the Information OAM PDU for soft reset. If either is disabled, dying gasp is not active on those ports. This functionality must be enabled prior to the soft reset.

When both grace-tx-enable and dying-gasp-tx-on-reset are active on the same port, grace-tx-enable takes precedence when a soft reset is invoked if the Peer Vendor OUI being received is 00:16:4d (ALU) or the configured grace-vendor-oui value. The grace-tx-enable command should not be configured if the Nokia Vendor Specific Grace TLV is not supported on the remote peer, including Nokia 7750 SR equipment prior to release 11.0 R4.

Default 

config>system>ethernet>efm-oam>no dying-gasp-tx-on-reset

config>port>ethernet>efm-oam>dying-gasp-tx-on-reset

discovery

Syntax 
discovery
Context 
config>port>ethernet>efm-oam
Description 

This is the top level of the hierarchy containing various discovery parameters that allow the operator to control certain aspects of the negotiation process as well as what action to take when there is a mismatch in peer capabilities.

advertise-capabilities

Syntax 
advertise-capabilities
Context 
config>port>ethernet>efm-oam>discovery
Description 

This is the top level of the hierarchy which allows for the overriding of default advertising of capabilities to a remote peer.

link-monitoring

Syntax 
[no] link-monitoring
Context 
config>port>ethernet>efm-oam>discovery>advertise-capabilities
Description 

When the link monitoring function is in a no shutdown state, the Link Monitoring capability (EV) is advertised to the peer through the EFM OAM protocol. This may not be desired if the remote peer does not support the Link Monitoring functionality.

The no version of this command suppresses the advertisement of capabilities

Default 

link-monitoring

grace-tx-enable

Syntax 
[no] grace-tx-enable
Context 
config>system>ethernet>efm-oam
config>port>ethernet>efm-oam
Description 

Enables the sending of grace for all the enabled EFM-OAM sessions on the node. Disabled by default at the system level and enabled by default at the port level. The combination of the system level and port level configuration will determine if the grace function is enabled on the individual ports. Both the system level and the port level must be enabled in order to support grace on a specific port. If either level is disabled, grace is not enabled on those ports. Enabling grace during an active ISSU or soft reset does not invoke the grace function for the active event.

When both grace-tx-enable and dying-gasp-tx-on-reset are active on the same port, grace-tx-enable takes precedence when a soft reset is invoked if the Peer Vendor OUI being received is 00:16:4d (ALU) or the configured grace-vendor-oui value. The grace-tx-enable command should not be configured if the Nokia Vendor Specific Grace TLV is not supported on the remote peer, including Nokia 7750 SR equipment prior to release 11.0 R4.

The no form of the command disables the sending of the Nokia Vendor Specific Grace TLV.

Default 

config>system>ethernet>efm-oam>no grace-tx-enable

config>port>ethernet>efm-oam>grace-tx-enable

grace-vendor-oui

Syntax 
grace-vendor-oui oui
no grace-vendor-oui
Context 
config>port>ethernet>efm-oam
Description 

This optional command configures an additional peer vendor OUI which indicates support for the Vendor Specific EFM-OAM Grace functionality, allowing grace to be preferred over dying gasp when both are configured. This is in addition to the Nokia Vendor OUI 00:16:4d.

When both grace-tx-enable and dying-gasp-tx-on-reset are active on the same port, grace-tx-enable takes precedence when a soft reset is invoked if the Peer Vendor OUI being received is 00:16:4d (ALU) or the configured grace-vendor-oui value. The grace-tx-enable command should not be configured if the Nokia Vendor Specific Grace TLV is not supported on the remote peer, including Nokia 7750 SR equipment prior to release 11.0 R4.

The no form of the command removes the additional Vendor OUI but does not remove the Nokia 00:16:4d value.

Default 

no grace-vendor-oui

Parameters 
oui—
Hex value in the range 00:00:00 to FF:FF:FF.

hold-time

Syntax 
hold-time time-value
no hold-time
Context 
config>port>ethernet>efm-oam
Description 

This command configures efm-oam operational transition dampening timers which reduce the number of efm-oam state transitions reported to upper layers.

Default 

no hold-time

Parameters 
time-value—
Indicates the number of seconds that the efm-oam protocol will wait before going back to the operational state after leaving the operational state. Note that the hold-time does not apply if efm-oam moved from operational to link-fault.

A hold-time value of zero indicates that there should be no delay in transitioning to the operational state. A non-zero value will cause the efm-oam protocol to attempt to negotiate with a peer if possible, but it will remain in the send-local-remote-ok state until the hold time has expired if negotiation is successful.

If efm-oam is administratively shutdown while it was in the operational state and then re-enabled when a non-zero hold time is configured, efm-oam will attempt transition to the operational state immediately.

The no form of this command reverts the value to the default.

Values—
0 to 50