config>port>tdm>ds1>channel-group
config>port>tdm>e1>channel-group
The no form of this command removes any description string from the context.
The no form of this command administratively enables an entity.
This mandatory command enables access to the chassis card Input/Output
Control Forwarding Module (IOM), slot,
MCM and MDA CLI context.
The no form of this command removes the card from the configuration. All associated ports, services, and MDAs must be shutdown.
SR-7: slot-number = 1 — 5
SR-12: slot-number = 1 — 10
This mandatory command adds an IOM 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.
Because the IOM-3 integrated card does 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, etc., remain in the MDA configuration context.
The no form of this command removes the card from the configuration.
The type of card to be configured and installed in that slot.
|
Values
|
iom-20g, iom2-20g, iom-20g-b, iom3-20g, iom3-40g, iom3-xp, imm48-1gb-sfp, imm48-1gb-tx, imm4-10gb-xfp, imm5-10gb-xfp, imm8-10gb-xfp, imm12-10gb-SF+, imm1-40gb-tun, imm3-40gb-qsfp, imm1-oc768-tun, imm1-100g-cfp, iom3-xp, iom4-eiom3-xp, imm-2pac-fp3
|
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 Alcatel-Lucent 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).
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, it is recommended to enable the reporting of the specific events/errors (configure log event-control) when
fail-on-error is enabled.
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).
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.
The named-pool-mode CLI context is used 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.
The no rate-calc-min-interval command is used to restore the default fast queue and slow queue minimum rate calculation interval.
The no sched-run-min-int command is used to restore the default minimum scheduler run interval for all virtual schedulers on the card.
The no scheduling-int command is used to restore the default task scheduling interval of the card’s hierarchical virtual scheduler task.
The no slow-queue-thresh command is used to restore the default slow queue and fast queue rate thresholds.
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.
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.
A maximum of two MDAs can be provisioned on an IOM
. 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.
Note: CMAs 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.
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.
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.
7750: m60-10/100eth-tx, m10-1gb-sfp, m16-oc12/3-sfp, m8-oc12/3-sfp, m16-oc3-sfp, m8-oc3-sfp, m4-oc48-sfp, m1-oc192, m5-1gb-sfp, m12-chds3, m1-choc12-sfp, m1-10gb, m4-choc3-sfp, m2-oc192-xp-xfp, m2-oc48-sfp, m20-100eth-sfp, m20-1gb-tx, m2-10gb-xfp, m2-oc192-xfp, m12-1gb-sfp, m12-1gb+2-10gb-xp, m4-atmoc12/3-sfp, m16-atmoc3-sfp, m20-1gb-sfp, m4-chds3, m1-10gb-xfp, vsm-cca, m5-1gb-sfp-b, m10-1gb-sfp-b, m4-choc3-as-sfp, m10-1gb+1-10gb, isa-ipsec, m1-choc12-as-sfp, m12-chds3-as, m4-chds3-as, isa-aa, isa-tms, m12-1gb-xp-sfp, m12-1gb+2-10gb-xp, m10-1gb-hs-sfp, m1-10gb-hs-xfp, m4-choc3-ces-sfp, m1-choc3-ces-sfp, m4-10gb-xp-xfp, m2-10gb-xp-xfp, m1-10gb-xp-xfp, m10-1gb-xp-sfp, m20-1gb-xp-sfp, m20-1gb-xp-tx, m1-choc12-ces-sfp, p1-100g-cfp, p10-10g-sfp,p3-40g-qsfp, p6-10g-sfp, imm24-1gb-xp-sfp, imm24-1gb-xp-tx, imm5-10gb-xp-xfp, imm4-10gb-xp-xfp, imm3-40gb-qsfp, imm1-40gb-qsfp, imm1-40gb-xp-tun, imm-1pac-fp3/p1-100g-tun
, imm2-10gb-xp-xfp, imm12-10gb-xp-SF+, imm1-oc768-xp-tun, imm1-100gb-xp-cfp, isa-video, m1-10gb-dwdm-tun, iom3-xp-b, m4-atmoc12/3-sf-b, m16-atmoc3-sfp-b, m16-oc12/3-sfp-b, m4-oc48-sfp-b, me10-10gb-sfp+, me1-100gb-cfp2
7750 SR-c12/4: m60-10/100eth-tx, m8-oc3-sfp, m5-1gb-sfp, m2-oc48-sfp, m20-100eth-sfp, m20-1gb-tx, m4-atmoc12/3-sfp, m20-1gb-sfp, m5-1gb-sfp-b, m4-choc3-as-sfp, c8-10/100eth-tx, c1-1gb-sfp,c2-oc12/3-sfp-b, c8-chds1, c4-ds3, c2-oc12/3-sfp, c1-choc3-ces-sfp, m1-choc12-as-sfp, m12-chds3-as, m4-chds3-as, m4-choc3-ces-sfp, m10-1gb-xp-sfp, m20-1gb-xp-sfp, m20-1gb-xp-tx
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.
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.
The named-pool-policy command is used to associate 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.
The defined policy-name must be an existing named pool policy on the system. If policy-name does not exist, the named-pool-policy command will fail. If another named pool policy is currently associated, it will continue 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.
This command enables the context to configure egress-xpl settings used by the
fail-on-error feature.
threshold cannot be changed while fail-on-error is enabled for this MDA.
window cannot be changed while fail-on-error is enabled for this MDA.
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.
This command designates the MDA 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 MDA. If a group is specified, all MDAs 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 MDA, the MDAs will be brought online and generate an event (SYSTEM: 2052 - mdaHiBwMulticastAlarm). 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 MDA.
The no form of the command removes the path limit override from an ingress multicast path and restores the path limit defined in the bandwidth policy associated with the MDA.
The no form of the command restores default HSMDA scheduler policy control over the ingress scheduler on the HSMDA. The
no scheduler-policy command cannot be executed when scheduler overrides exist on the ingress HSMDA. The overrides must be removed prior to executing the no scheduler-policy command.
Specifies an existing policy created in the config>qos>hsmda-scheduler-policy context. The “default” policy name cannot be specified. Instead, the
no scheduler-policy command should be executed resulting in the default scheduler policy being used by the ingress MDA.
The no form of the command disables synchronous Ethernet on the MDA.
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.
threshold cannot be changed while fail-on-error is enabled for this MDA.
window cannot be changed while fail-on-error is enabled for this MDA.
resv-cbs percent-or-default amber-alarm-action step
percent max
[1..100]
The no form of this command restores the default value.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
port {port-id | bundle-id | bpgrp-id | aps-id}
no port {bundle-id | bpgrp-id | aps-id}
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. (See
card and
mda commands.)
Syntax: 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.)
bundle: keyword
slot: IOM/MDA slot numbers
bundle-num: 1 — 336
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.
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,
Syntax: port aps-
group-id aps: keyword
group-id: 1 — 64
Syntax: 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.
bpg-num: 1 — 1600
Syntax: bundle-
type-
slot/mda.bundle-num
bundle-
ppp-
slot/mda.bundle-num (Creates a multilink PPP bundle.)
bundle: keyword
slot: card/mda slot numbers
bundle-num: 1 — 256
The no form of the command disables DDM events.
[no
] report-alarms
[ild
] [tmp
] [mth
] [mtl
] [los
] [lop
] [com
]
The no form of the command removes the alarm parameters.
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 the table below:
mode {automatic | manual}
mode {automatic | manual}
[no
] report-alarms
[nrdy
] [mth
] [mtl
] [unlck
] [tlim
] [einv
] [com
]
[no
] report-alarms
[modflt
] [mod
] [netrx
] [nettx
] [hosttx
]
sweep start
dispersion-start end
dispersion-end
sweep start
dispersion-start end
dispersion-end
The no version of this command deletes the queue-group instance from the network egress context of the port.
Note: 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.
Note: FEC cannot be disabled on OTU3 encapsulated OC768 or 40-Gigabit Ethernetby 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.
expected {string
string | bytes
byte-sequence | auto-generated
| use-rx
}
tx bytes bytes [bytes...(up to 64 max)]
The no form of the command reverts to the default TTI.
bytes byte1 [byte2...(up to 64 bytes)]
tx {auto-generated
| string
identifier | bytes
byte1 [byte2...(up to 64 bytes)]}
The no form of the command reverts to the default TTI.
bytesbyte1 [byte2...(up to 64 bytes)]
The no form of the command reverts to the default.
tx {string
identifier | bytes
byte-sequence | auto-generated
}
bytes byte1 [byte2...(up to 64 bytes)]
expected {string
string | bytes
byte-sequence | auto-generated
| use-rx
}
The no form of this command configures the port to receive synchronously mapped data.
[no
] 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
]
The no form of the command disables OTU alarm reporting.
loc, los, lof, lom, otu-ais, otu-bdi, fec-sf, fec-sd, odu-ais, odu-oci, odu-lck, odu-bdi, opu-plm
The no form of this command restores the default values for the ingress access and network weights.
The no form of this command restores the default values for the egress access and network weights.
The no ing-percentage-of-rate command is used to remove 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%.
The no egr-percentage-of-rate command is used to remove 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%.
[no
] egress-scheduler-override
|
•
|
The max-rate allowed for the scheduler.
|
See the 7750 SR OS 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.
level priority-level rate
pir-rate [cir
cir-rate]
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.
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.
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 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.
mode {access
| network
| hybrid}
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.
The user configures a network IP interface under config>router>interface>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.
The user configures a network IP interface under config>router>interface>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 * is used to create 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.
network — Configures the Ethernet port, TDM channel or SONET path for transport network use.
access — Default channel/port mode for channelized, ASAP, and ATM MDAs.
The no form of this command disables per-link-hash on a LAG.
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 BPDU’s are sent with the new MAC address.
The no form of this command returns the MAC address to the default value.
This command configures the maximum payload MTU size for an Ethernet port or 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 received larger than the MTU will be discarded. Packets that cannot be fragmented at egress and exceed the MTU are discarded.
The no form of this command restores the default values.
|
Values
|
512 — 9212config>port>sonet-sdh>path 512 — 9208 config>port>tdm>ds3 512 — 9208 config>port>tdm>ds1>channel-group 512 — 9208 config>port>tdm>e3 512 — 9208 config>port>tdm>e1>channel-group 512 — 9208
|
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.
The no form of the command disables the header compression.
The no form of the command reverts to normal operation where the link remains in-service when ber-sf is encountered.
[no
] report-alarm
[ais
] [los
] [oof
] [rai
] [looped
]
The no form of this command disables logging of the specified alarms.
|
Default
|
oof alarms are not issued.
|
|
Default
|
rai alarms are not issued.
|
The no form of this command disables scrambling.
keepalive time-interval [dropcount
drop-count]
The no form of this command returns the interval to the default value.
The aps command is only available for APS groups and not physical ports.
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.
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.
hold-time-aps [lsignal-failure
sf-time] [lsignal-degrade
sd-time]
The no version of this command resets hol a specified string expression from an app-filter definition.
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:
The no form of this command removes the protect-circuit.
Syntax:
port-id:
slot/mda/port
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).
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.
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.
Syntax:
port-id:
slot/mda/port
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 suggested to increase the default timer on the working line accordingly with the transmission delay present on the protect line. See
hold-time on .
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#
This context can only be used when configuring Fast Ethernet, gigabit, or 10Gig Ethernet LAN ports on an appropriate MDA.
mode {access
| network
| hybrid
}
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.
The user configures a network IP interface under config>router>interface>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.
The user configures a network IP interface under config>router>interface>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 * is used to create 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.
queue-group queue-group-name [instance
instance-id] [create
]
queue-group queue-group-name [instance
instance-id] [create
]
no queue-group
queue-group-name
[no
] limit-unused-bandwidth
[no
] queue-frame-based-accounting
queue queue-id [queue-type] [create
]
The no form of the command removes the queue-id from the configuration.
parent [[weight
weight] [cir-weight
cir-weight]]
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.
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.
|
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.
The queue burst-limit command is used to define an explicit 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 burst-limit command is supported under the sap-ingress and sap-egress QoS policy queues. The command is also supported under the ingress and egress queue-group-templates queues.
The no form of this command
is used to restore the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates. When specified within a queue-override queue context, any current burst limit override for the queue will be removed and the queue’s burst limit will be controlled by its defining policy or template.
The bytes qualifier is used to specify that the value given for size must be interpreted as the burst limit in bytes. The byte qualifier is optional and mutually exclusive with the kilobytes qualifier.
The kilobyte qualifier is used to specify that the value given for size must be interpreted as the burst limit in Kilobytes. The kilobyte qualifier is optional and mutually exclusive with the bytes qualifier. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.
The no form of this command restores the default CBS size to the template queue.
The high-prio-only command specifies the percentage of buffer space for the queue, used exclusively by high priority packets. The specified value overrides the default value for the context.
The no form of this command restores the default high priority reserved size.
The queue-group or network egress QoS context for mbs provides a mechanism for overriding the default maximum size for the queue.
The no form of this command
returns the MBS size assigned to the queue to the value.
The no form of the command removes queue depth monitoring for the specified queue.
rate pir-rate [cir
cir-rate]
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).
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.
The cir parameter overrides the default administrative CIR used by the queue. 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.
scheduler-policy scheduler-policy-name
The no form of this command removes the configured ingress or egress scheduler policy from the queue-group.
The scheduler-policy-name parameter applies an existing scheduler policy that was created in the
config>qos>scheduler-policy scheduler-policy-name context to create the hierarchy of ingress or egress virtual schedulers.
rate {max
| kilobits-per-second}
The no form of this command is used to restore the default metering and profiling rate to a policer.
{max |
kilobits-per-second}
Specifying the keyword max or an explicit
kilobits-per-second parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the shaper 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.
class class-number rate
{kilobits-per-second | max
} [monitor-threshold
size-in-kilobytes]
The no form of the command returns the class id for the Ethernet egress expanded secondary shaper to the default value.
Specifies the class identifier of the low burst max class for the shaper.
rate {kilobits-per-second |
max}
Specifies the rate limit for the secondary shaper.
Specifies the monitor threshold for the secondary shaper.
The no form of the command returns the class number value for the Ethernet egress expanded secondary shaper to the default value.
Specifies the class number of the class for the secondary shaper.
|
•
|
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.
|
The channel bandwidth definition policy is defined in the mcac policy in the configure>router>mcac>policy context. The policy is applied under the group-interface or in case of redirection under the redirected-interface.
qos scheduler-hierarchy port
port-id vport
vport-name
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.
This command enables congestion monitoring on an Egress Port Scheduler (EPS) that is applied to a physical port or to a Vport.
The no form of the command disables congestion monitoring.
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.
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.
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 gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.
If the autonegotiate limited keyword option is specified the port will autonegotate 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 multispeed gigabit ports to force gigabit operation while keeping autonegotiation enabled for compliance with IEEE 801.3.
SR OS 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.
The no form of this command reverts the dot1q-etype value to the default.
[no
] accept-remote-loopback
The no form of this command disables reactions to loopback control OAM PDUs.
The no version of this command suppresses the advertisement of this capability
When the ignore-efm-state command is configured, ANY failure in the protocol state machine (discovery, configuration, timeout, loops, etc.) does not impact the state of the port. There is only be a protocol warning message on the port. If this optional command is not configured, the port state is affected by any existing EFM-OAM protocol fault condition.
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.
Allows the frame error sf-threshold crossing events to transmit the Event Notification OAMPDU with the specific Link Event TLV information. The Event Notification OAM PDU will only be generated when the initial
sf-threshold is reached. No subsequent notification will be sent until the event that triggered until the event is manually cleared. The burst parameter under the
local-sf-action will determine the number of Event Notification OAMPDUs to generate when the event occurs. The reception of the event notification will be processed regardless of this parameter.
The no version of this command will disable the transmission of the Event Notification OAMPDU for this event type.
The no value of this option disables the sd-threshold.
This command defines the size of the window using a 100ms base deciseconds. Errors are accumulated until the end of the window. At the end of the window the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
The no value of this option disables the sd-threshold
The no value of this option disables the sd-threshold
This command defines the size of the window using a 100ms base deciseconds. Errored seconds are accumulated until the end of the window. At the end of the window, the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
The no version of this command will disable the transmission of the Event Notification OAMPDU for this event type.
The no value of this option means there is there is no automatic return to service.
Defines the size of the window using a 100ms base deciseconds. The time value is converted to a number of symbols for the underlying medium. Errors are accumulated until the end of the window. At the end of the window, the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
The no form of the command activates the link monitoring function.
The no form of the command activates the local monitoring function and actions for the event.
Interactions: The sf-thresh threshold will trigger these actions.
[no
] transmit-interval
interval [multiplier
multiplier]
The no form of the command disables tunneling.
The no form of this command returns the value to the default.
The no form of this command restores the default.
hold-time {[up hold-time up] [down
hold-time down] [seconds | centiseconds]}
The no form of this command reverts to the default values.
down 0 seconds — No port link down dampening is enabled; link down transitions are immediately reported to upper layer protocols.
up 0 seconds — No port link up dampening is enabled; link up transitions are immediately reported to upper layer protocols.
[no
] hsmda-scheduler-overrides
|
Values
|
Command Configuration
description no description max-rate no max-rate group group 1 rate max group 2 rate max scheduling-class scheduling-class 1 rate max scheduling-class 2 rate max scheduling-class 3 rate max scheduling-class 4 rate max scheduling-class 5 rate max scheduling-class 6 rate max scheduling-class 7 rate max scheduling-class 8 rate max
|
The no form of the command removes the overridden parameters from the HSMDA egress port or ingress MDA scheduler. Once existing overrides are removed, the scheduler reverts all scheduling parameters back to the parameters defined on the hsmda-scheduler-policy associated with the egress port or ingress MDA.
The no form of the command removes the local overrides for the weighted scheduling group. Once removed, the defined behavior within the HSMDA scheduling policy for the weighted scheduling group is used.
The megabits-per-second parameter specifies a local limit on the total bandwidth for the weighted scheduling group and overrides any rate defined in the HSMDA scheduler policy for the weighted scheduling group. The parameter is specified in Megabits per second in a base 10 context. A value of 1 equals a rate of 1000000 bits per second.
The max keyword removes any existing rate limit imposed by the HSMDA scheduler policy for the weighted scheduling group allowing it to use as much total bandwidth as possible.
This command overrides the max-rate parameters configured in the hsmda-scheduler-policy associated with the egress port or ingress MDA. When a
max-rate is defined at the override level, the HSMDA scheduler policy’s
max-rate parameter is ignored.
The hsmda-scheduler-override max-rate command supports a
max 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 HSMDA scheduler policy has an explicit maximum rate defined and it is desirable to remove this limit at the port instance.
The no form of the command removes the maximum rate override from the egress port or the ingress MDA scheduler context. Once removed, the max-rate parameter from the HSMDA scheduler policy associated with the port or MDA will be used by the local scheduler context.
The rate parameter is mutually exclusive to specifying the
max keyword. When executing the max-rate override command either the keyword
max or a rate in megabits-per-second must be specified.
The max keyword is mutually exclusive to specifying a
rate in megabits-per-second. When executing the
max-rate override command either the keyword
max or a rate in megabits-per-second must be specified. The max keyword removes an existing rate limit from the HSMDA scheduler context.
The no form of the command removes the local overrides for the scheduling class. Once removed, the defined behavior for the scheduling class within the HSMDA scheduling policy will used.
The max keyword removes any existing rate limit imposed by the HSMDA scheduler policy for the scheduling class allowing it to use as much total bandwidth as possible.
The no form of this command returns the value to the default.
The no form of the command disables LACP packet tunneling for the Ethernet port.
In the default mode, no load-balancing-algorithm, the port inherits the global settings. The value is not applicable for ports that do not pass any traffic.
|
•
|
include-l4 — Enables inherits system-wide settings including Layer 4 source and destination port value in hashing algorithm.
|
|
•
|
exclude-l4 — Layer 4 source and destination port value will not be included in hashing.
|
|
Values
|
include-l4 — Specifies that the source and destination ports are used in the hashing algorithm. exclude-l4 — Specifies that the source and destination ports are not used in the hashing algorithm.
|
|
Values
|
0x0600.. 0xffff: 1536 — 65535 (accepted in decimal or hex)
|
The no form of this command reverts the qinq-etype value to the default.
[no
] report-alarm
[signal-fail
] [remote
] [local
] [no-frame-lock
] [lcd
]
The no form of this of this command disables sFlow.
[no
] down-on-internal-error
This command configures the maximum number of times that the 7750 SR will send an access request RADIUS message to the RADIUS server. If a reply is not received from the RADIUS server after the specified
number attempts, the 802.1x authentication procedure is considered to have failed.
The no form of this command returns the value to the default.
The no form of this command returns the value to the default.
The no form of this command returns the value to the default.
The no form of this command removes the RADIUS policy association.
The no form of this command returns the value to the default.
When re-authentication is enabled, the 7750 SR will re-authenticate clients on the port every re-auth-period seconds.
The no form of the command returns the value to the default.
This command configures the period during which the 7750 SR waits for the RADIUS server to responds to its access request message. When this timer expires, the 7750 SR will re-send the access request message, up to the specified number times.
The no form of this command returns the value to the default.
This command configures the period during which the 7750 SR waits for a client to respond to its EAPOL messages. When the supplicant-timeout expires, the 802.1x authentication session is considered to have failed.
The no form of this command returns the value to the default.
The no form of this command returns the value to the default.
The no form of this command disables tunneling of untagged 802.1x frames.
[no
] use-broadcast-address
|
Values
|
nearest-bridge — Specifies to use the nearest bridge. nearest-non-tpmr — Specifies to use the nearest non-Two-Port MAC Relay (TPMR) . nearest-customer — Specifies to use the nearest customer.
|
The no form of the command disables LLDP notifications.
[no
] tunnel-nearest-bridge
tx-tlvs [port-desc
] [sys-name
] [sys-desc
] [sys-cap
]
The no form of the command resets the value to the default.
The no form of this command removes the accounting policy association from the network interface, and the acccounting policy reverts to the default.
The accounting policy-id of an existing policy. Accounting policies record either service (access) or network information. A network accounting policy can only be associated with the network port configurations. Accounting policies are configured in the
config>log>accounting-policy context.
When the no collect-stats command is issued, the statistics are still accumulated by the IOM cards, 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.
This command specifies the existing 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.
[no
] interface-group-handler
group-id
The no form of this command deletes the interface group handler. All members must be removed before the IGH can be deleted.
This command binds the specified port with the associate Interface Group Handler. Up to eight member commands can be issued to add multiple ports to the associated IGH. The
member must be a port or channel on a SONET or POS MDA. It must be a physical port or channel in network mode, and not bound to any router interfaces. A port or channel cannot be a member of more than one IGH at the same time. MLPPP bundles and their members cannot be IGH members.
The no form of this command removes the specified port ID from the associated IGH.
The no form of this command resets the threshold to 1. Note: For APS configurations, if the ber-sd or ber-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 resets the fragment threshold back to the default value.
[no
] interleave-fragments
The no form of this command disables Link Fragmentation and Interleaving on the multilink bundle.
The no form of this command removes the specified channel group from the multilink bundle.
The no form of this command removes the minimum link limit.
[no
] identifier
bundle-id-string
[no
] identifier
frf16-link-id-string
Specify the expected interval in seconds between status inquiries issued by the DTE equipment.
The no form of this command resets the fragment threshold back to the default value.
The no form of the command removes the parameters from the configuration.
The no form of the command removes the parameters from the configuration.
The no form of the command disables the loopback detection.
This command enables multi-class MLPPP as defined by RFC 2686, The Multi-Class Extension to Multi-Link PPP, on a MLPPP bundle (including MLPPP bundle protection groups) with 2, 3 or 4 classes. For multiclass MLPPP bundles with a non-zero count, the class index takes valid values from 0 to one less than the maximum number of classes inclusive. For example a 4-class MLPPP bundle has 4 classes with indices 0, 1, 2, and 3. A bundle must be shutdown with no links for this value to be changed.
The no form of the command disables multi-class MLPPP.
[no
] stateless-aps-switchover
The no form of the command disables stateless APS switchover.
The no form of this command resets the MRRU to the default.
[no
] protect-bundle
bundle-id
Syntax: bundle-
type-
slot/mda.bundle-num
bundle-
PPP or IMA-
slot/mda.bundle-num (Creates an MLPPP or IMA bundle.)
bundle: keyword
slot: IOM/MDA slot numbers
bundle-num: 1 — 256
The no form of this command restores the red-differential-delay defaults.
The no form of this command disables the short-sequence feature.
[no
] working-bundle
bundle-id
Syntax: bundle-
type-
slot/mda.bundle-num
bundle-
PPP or IMA-
slot/mda.bundle-num (Creates an MLPPP or IMA bundle.)
bundle: keyword
slot: IOM/MDA slot numbers
bundle-num: 1 — 256
The no form of this command removes the yellow-differential-delay.
The no form of the command resets the max-bandwidth to its default value
The no form of this command deletes the link from test-pattern procedure. The test-pattern procedure must be shutdown first.
The no form of this command restores the test-pattern to the default.
The no form of this command disables the IMA test pattern procedure.
This command enables access to the context to configure SONET/SDH ports. This context can only be used when configuring an OC-3, OC-12, OC-48, OC-192, and OC-768 SONET/SDH ports on an appropriate MDA.
group sonet-sdh-index payload
{tu3
| vt2
| vt15
}
hold-time hold-time {[up
hold-time up] [down
hold-time down]}
Note: For APS configurations, the hold-time down and
up default values are 100 ms and 500 ms respectively. But, if there is a large communication delay (time to exchange K1/K2 bytes) between the APS Controllers of the two endpoints of an APS link, it is highly suggested to increase the default hold-time down timer on the APS group port accordingly with the communication delay.
See
aps on .
[no
] report-alarm
[loc] [lais
] [lrdi
] [ss1f
] [lb2er-sd
] [lb2er-sf
] [slof
] [slos
] [lrei
]
The no form of this command disables logging of the specified alarms
|
Default
|
lais alarms are not issued.
|
|
Default
|
ss1f alarms are not issued.
|
|
Default
|
lrei traps are not issued.
|
[no
] reset-port-on-path-down
The no form of this command reverts back to default.
This command enables the suppression of lower order alarms on SONET/SDH port such as MLPPP bundle alarms, DS1/E1 links alarms and 336 APS channel groups alarms.
The no form of the command disables the suppression of lower order alarms on SONET/SDH port.
threshold {ber-sd
| ber-sf
} rate
threshold-rate
Note: For APS configurations, if the
ber-sd or
ber-sf threshold rates must be modified, the changes must be performed at the line level on both the working and protect APS port member. See port
aps-id .
The no form of this command reverts to the default value.
threshold ber-sf 6 — Signal degrade BER threshold of 10
-6
threshold ber-sf 3 — Signal failure BER threshold of 10
-3
[no
] path
[sonet-sdh-index]
The no form of this command removes the specified SONET/SDH path.
Configures STS3/STM1 payload as clear channel.
Configures the port or channel as DS1.vt15 or vt2 payload as DS-1
[no
] report-alarms
[pais
] [plop
] [prdi
] [pplm
] [prei
] [puneq
] [plcd
]
The no form of this command disables logging of the specified alarms.
|
Default
|
pais alarms are not issued
|
|
Default
|
prdi alarms are not issued
|
|
Default
|
prei traps are not issued
|
|
Default
|
plcd traps are not issued
|
encap-type {atm
| bcp-null
| bcp-dot1q
| ipcp
| ppp-auto
| frame-relay
| wan-mirror
| cisco-hdlc
}
When the encap-type is set to ATM the CRC default cannot be changed.
When the encap-type is ATM, ATM sub-layer verification (GR-1248-CORE,
Generic Requirements for Operations of ATM Network Elements (NEs)) is automatically enabled. The result of the verification includes:
|
•
|
Loss of Cell Delineation defect/alarm. The LCD defect/alarm is defined in RFC 2515, Definitions of Managed Objects for ATM Management. When a path is in an LCD defect state, the path’s operational status will be down. When a path exits the LCD state, the path’s operational status will change to up (assuming nothing else causes the path to stay down). A trap is raised to indicate the LCD status change. Also a P-RDI is sent to indicate the defect to the remote end.
|
The encap-type is only required when configuring a SONET/SDH path for access mode.
The no form of this command restores the default.
config>port>sonet-sdh>path
The no form of this command disables the sending of echo requests.
[no
] report-alarm
{pais
| plop
| prdi
| pplm
| prei
}
The no form of this command disables logging of the specified alarms.
The no form of this command disables scrambling.
The no form of this command resets the string to its default.
The default J1 value is Alcatel-Lucent XXX YYY (for example, Alcatel 7750 SR) where XXX is the platform name, such as "7750", and YYY is the product name, such as "SR" or "ESS". The value does not change when the encap-type changes. The J1 string contains all zeros for a non-provisioned path.
|
Values
|
direct — Specifies direct cell mapping. plcp — Specifies PLCP cell maping.
|
keep-alive [poll-frequency
seconds] [poll-count
value] [test-frequency
seconds]
The no form of this command resets the devault values on an ILMI link.
The protocol-type is an enumerated integer whose value indicates the ILMI version of either 3.1 or 4.0 that is advertised by IME and also indicates the ILMI IME type of either user-side or network-side.
The port’s mode must be set to
access in
config>port>sonet-sdh>path>mode access context.
The port’s encapsulation type must be set to frame-relay in the
config>port>sonet-sdh>path>encap-type frame-relay context.
The no form of this command removes the Frame Relay LMI operational parameters.
[no
] identifier
frf16-link-id-string
The no form of this command changes the LMI type back to the default value.
The no form of this command returns the
n391dte counter to the default value.
The no form of this command returns the
n392dce counter to the default value.
The no form of this command returns the
n392dte counter to the default value.
The no form of this command returns the
n393dce counter to the default value.
The no form of this command returns the
n393dte counter to the default value.
The no form of this command returns the
t391dte keepalive timer to the default value.
The no form of this command returns the
t392dce keepalive timer to the default value.
Specify the expected interval in seconds between status inquiries issued by the DTE equipment.
The no form of this command disables DS-1 capabilities.
[no
] ds3
[sonet-sdh-index]
The no form of this command disables DS-3 capabilities.
The no form of this command disables E-1 capabilities.
The no form of this command disables E-3 capabilities.
bert {2e3
|2e9
|2e11
|2e15
|2e20
|2e20q
|2e23
|ones
|zeros
|alternating
} duration
duration
The no form of the command terminates the BERT test if it has not yet completed.
NOTE: This command is not saved in the router configuration between boots.
lbo [0dB
| -7.5dB
| -15.0dB
| -22.5dB
]
This command applies only to a DS-1 port configured with a 'long' buildout (see the buildout command). Specify the number of decibels the transmission signal decreases over the line.
length {133
| 266
| 399
| 533
| 655
}
This command applies only to a DS-1 port configured with a 'short' buildout. The length command configures the length of the line (in feet). For line lengths longer than 655 feet, configure the DS-1 port buildout as 'long'.
[no
] channel-group
channel-group-id
The no form of this command deletes the specified DS1 or E1 channel.
clock-source {loop-timed
| node-timed
| adaptive
| differential
}
encap-type {atm
| bcp-null
| bcp-dot1q
| ipcp
| ppp-auto
| frame-relay
| wan-mirror |cisco-hdlc
}
When the encap-type is set to ATM the CRC, timeslots, scrambling (if applicable), and idle-cycle-flags are set to ATM defaults respectively. When the encap-type is changed from ATM, those parameters are set to their non-ATM defaults.
When the encap-type is ATM, ATM sub-layer verification (GR-1248-CORE,
Generic Requirements for Operations of ATM Network Elements (NEs)) is automatically enabled. When ATM PLCP cell mapping is used, the results of this verification include:
|
•
|
Loss of Cell Delineation defect/alarm. The LCD defect/alarm is defined in RFC 2515, Definitions of Managed Objects for ATM Management. When a path is in an LCD defect state, the path’s operational status will be down. When a path exits the LCD state, the path’s operational status will change to up (assuming nothing else causes the path to stay down). A trap is raised to indicate the LCD status change. Also, a P-RDI is sent to indicate the defect to the remote end.
|
The no form of this command restores the default.
On circuit emulation CMAs and MDAs, only the cem encap-type is supported. All other values are blocked with an appropriate warning. The
cem encap-type is not supported on other CMAs and MDAs and are blocked with an appropriate warning.
The no form of this command prevents the associated DS-3/E-3 interface from responding to remote loop signals.
framing {no-crc-g704
| g704
| e1-unframed
}
framing {c-bit | m23 | unframed-ds3
}
framing {g751
| g832 | unframed-e3
}
The no form of this command reverts the idle cycle flag to the default value.
loopback {line
| internal
| fdl-ansi
| fdl-bellcore
| payload-ansi
| inband-ansi
| inband-bellcore
}
NOTE: This command is not saved in the router configuration between boots.
The no form of this command disables the specified type of loopback.
NOTE: This command is not saved in the router configuration between boots.
The no form of this command disables the specified type of loopback.
mdl {eic
| lic
| fic
| unit
| pfi
| port
| gen
} mdl-string
The no form of this command removes the MDL string association and stops the transmission of any IDs.
The no form of this command disables transmission of the specified message or all messages.
[no
] report-alarm
[ais
] [los
] [oof
] [rai
] [looped
] [ber-sd
] [ber-sf
]
The no form of this command disables logging of the specified alarms.
|
Default
|
oof alarms are not issued.
|
|
Default
|
rai alarms are not issued
|
looped alarms are not issuedlof
The no form of the command reverts to the default value.
subrate {digital-link
| larscom
} rate-step
The no form of this command remove the subrate functionality.
threshold {ber-sd
| ber-sf
} rate
{1
| 5
| 10
| 50
| 100
}
The no form of this command reverts to the default value.
The no form of this command removes DS-0 timeslots from a channel group.
NOTE: All ports in a LAG group must have autonegotiation set to Limited or Disabled.
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 gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.
If the autonegotiate limited keyword option is specified the port will autonegotiate 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 multispeed gigabit ports to force gigabit operation while keeping autonegotiation is enabled for compliance with IEEE 801.3.
The no form of this command deletes the LAG from the configuration. Deleting a LAG can only be performed while the LAG is administratively shut down. Any dependencies such as IP-Interfaces configurations must be removed from the configuration before issuing the
no lag command.
adapt-qos {link
| port-fair
| distribute
[include-egr-hash-cfg
]}
|
Values
|
link — Specifies that the LAG will create the SAP queues and virtual schedulers with the actual parameters on each LAG member port. port-fair — Places the LAG instance into a mode that enforces QoS bandwidth constraints in the following manner: —all egress QoS objects associated with the LAG intance are created on a per port basis —bandwidth is distributed over these per port objects based on the proportion of the port's bandwidth relative to the total of all active ports bandwidth within the LAG —the include-egr-hash-cfg behavior is automatically enabled allowing the system to detect objects that hash to a single egress link in the lag and enabling full bandwidth for that object on the appropriate port distribute — Creates an additional internal virtual scheduler per IOMXCM as parent of the configured SAP queues and vitual schedulers per LAG member port on that IOMXCM. This internal virtual scheduler limits the total amount of egress bandwidth for all member ports on the IOMXCM to the bandwidth specified in the egress qos policy. include-egr-hash-cfg — Specifies whether explicitly configured hashing should factor into the egress buffering and rate distribution. When this parameter is configured, all SAPs on this LAG which have explicit hashing configured, the egress HQos and HPol (including queues, policers, schedulers and arbiters) will receive 100% of the configured bandwidth (essentially operating in adapt-qos link mode). For any Multi-Service-Sites assigned to such a LAG, bandwidth will continue to be divided according to adapt-qos distribute mode A LAG instance that is currently in adapt-qos link mode may be placed at any time in port-fair mode. Similarly, a LAG instance that is currently in adapt-qos port-fair mode may be placed at any time in link mode. However, a LAG instance in adapt-qos distribute mode may not be placed into port-fair (or link) mode while QoS objects are associated with the LAG instance. To move from distribute to port-fair mode it is necessary to remove all QoS objects from the LAG instance.
|
[no
] disable-soft-rest-extension
The no form of this command disables optimized SAP instance allocation.
The no form of the command disables the method of queue allocation for LAG SAPs.
The no form of the command disables the method of queue allocation for LAG SAPs.
The no form of the command disables restricting micro-BFD sessions
The no form of the command removes this address from the configuration.
The no form of the command removes the time interval from the configuration.
The no form of the command returns the timer value to the default (0) which indicates that forwarding will not start until the BFD session is established.
The no form of the command removes multiplier from the configuration.
The no form of the command removes the receive timer from the configuration.
The no form of the command removes this address from the configuration.
The no form of the command removes the transmit timer from the configuration.
The no form of the command re-enables micro BFD sessions for this address family.
This command enables OSPF/ISIS costing of a Link Aggregation Group (LAG) based on the available aggregated, operational bandwidth.
Assume a physical link in OSPF has a cost associated with it of 100, and the LAG consists of four physical links. The cost associated with the logical link is 25. If one link fails then the cost would automatically be adjusted to 33.
The no form of this command removes dynamic costing from the LAG.
The no form of this command restores the default.
null — All traffic on the port belongs to a single service or VLAN.
lacp [mode] [administrative-key
admin-key] [system-id
system-id][system
-priority
priority]
|
Values
|
passive — Starts transmitting LACP packets only after receiving packets. active — Initiates the transmission of LACP packets.
|
The no form of the command disables multiplexing machine control.
The no form of this command disables LACP message transmission. This command should be disabled for compatibility when using active/standby groups. This forces a timeout of the standby links by the peer. Use the
no form if the peer does not implement the correct behavior regarding the lacp sync bit.
The no form of this command, deletes the specified link map profile.
link port-id {primary
|secondary
}
The no form of this command deletes the link from this LAG link mapping profile. A port must be deleted from all lag link profiles if it is to be deleted from the LAG.
|
•
|
discard – egress traffic for SAPs/network interfaces using this link-map-profile is discarded to protect SAP/network interface traffic on other LAG links from impact of re-hashing the affected SAPs/network interfaces
|
|
•
|
per-link-hash – egress traffic for SAPs/network interfaces using this link-map-profile is rehashed on remaining, available LAG links using per-link-hash algorithm. SAP/network interface QoS configurations dictate what traffic is discarded on any link that may become oversubscribed as result of the re-hash.
|
The no form of this command restores the default failure-mode value.
port port-id [port-id … ] [priority priority] [subgroup sub-group-id]
The no form of this command removes ports from the LAG.
|
Values
|
1 — 8 identifies a LAG subgroup. The auto-iom subgroup is defined based on the IOM (all ports of the same IOM are assigned to the same subgroup). The auto-mda subgroup is defined based on the MDA. (all ports of the same MDA are assigned to the same subgroup).
|
The no form of this command reverts to the default values.
When the dynamic-cost action is specified, then dynamic costing will be activated. As a result the LAG will remain operationally up with a cost relative to the number of operational links. The link will only be regarded as operationally down when all links in the LAG are down.
When the down action is specified, then the LAG will be brought operationally down if the number of operational links is equal to or less than the configured threshold value. The LAG will only be regarded as up once the number of operational links exceeds the configured threshold value.
no port-weight-speed – all LAG links must be of the same speed. Each link weight is 1.
port-weight-speed 1 – LAG supports any mix of 1GE, 10GE ports up to a total weight of 64 (for 64 link LAGs) or 32 (for 32 link LAGs). Each 1 GE port has a weight of 1; each 10GE port has a weight of 10.
port-weight-speed 10 – LAG supports any mix of 10GE, 40GE, 100GE ports up to a total weight of 64 (for 64 link LAGs) or 32 (for 32 link LAGs). Each 10 GE port has a weight of 1; each 40GE port has a weight of 4; each 100GE port has a weight of 10.
no port-weight-speed can be changed to
port-weight-speed 1 or
port-weight-speed 10 in service, when all links of the LAG are 1GE or 10GE respectively.
port-weight-speed 1 or
port-weight-speed 10 can be changed to
no port-weight-speed in service, when all links of the LAG are 1GE or 10GE respectively.
selection-criteria {highest-count
| highest-weight | best-port
} [slave-to-partner
] [subgroup-hold-time
hold-time]
The slave-to-partner keyword specifies that it, together with the selection criteria, should be used to select the active sub-group. An eligible member is a lag-member link which can potentially become active. This means it is operationally up (not disabled) for use by the remote side. The
slave-to-partner parameter can be used to control whether or not this latter condition is taken into account.
|
Values
|
not specified – Equivalent to specifying a value of 0. Specifies no delay and to switchover immediately to a new candidate active sub-group.
|
|
Values
|
infinite – Do not switchover from existing active sub-group if the subgroup remains UP. Manual switchover possible using tools perform lag force command.
|
The no form of this command disabled weight-threshold operation in LAG.
The no form of this command deletes the Ethernet tunnel specified by the tunnel-id.
The no form of this command removes the text description.
The no form of this command returns the MAC address to the default value.
The no form of this command sets the hold-time to the default value.
The no form of the command reverts the default.
The no form of the command reverts the default.
The no form of the command reverts the default.
The no form of this command sets the revert-time to the default value.
The no form of this command removes the path from under the Ethernet tunnel. If this is the last path, the associated SAP need to be un-configured before the path can be deleted.
The no form of this command removes the text description.
eth-tunnel 1
path 1
member 1/1/1
path 2
member 1/1/4
eth-tunnel 2
path 1
member 1/1/1
path 2
member 1/1/5
The no form of this command is used just to indicate that a member is not configured. The procedure described above, based on the
no path command must be used to un-configure/change the member port assigned to the path.
The no form of this command is used just to indicate that a control-tag is not configured. The procedure described above, based on ‘no path’ command must be used to un-configure/change the control-tag assigned to the path.
The no form of this command sets the precedence to the default value.
[no
] mep
mep-id domain
md-index association
ma-index
The no form of the command reverts to the default values.
The no form of this command disables Ethernet ring control.
The no form of the command disables the generation of CCM messages.
The no form of the command removes the priority value from the configuration.
oam eth-cfm eth-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [data-length
data-length]
The no form of the command removes the values from the configuration.
The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke SDP).
The no form of this command disables the use of the CC state by the Ethernet tunnel manager\.
The no form of this command enables the MEP.
The no form of this command enables the path.
mep mep-id domain
md-index association
ma-index [vlan
vlan-id]
no mep mep-id domain
md-index association
ma-index [vlan
vlan-id]
The no form of the command reverts to the default values.
The no form of the command reverts to the default values.
The no form of the command reverts to the default values.
The no form of the command reverts to the default values.
The no form of the command reverts to the default values.
The no form of the command disables the generation of CCM messages.
The no form of the command reverts to the default values.
The no form of the command reverts to the default.
The no form of the command causes the receiving MEP will process all recognized TLVs in the CCM PDU.
The no form of the command disables and deletes the counters for this SAP, Binding or facility.
oam eth-cfm eth-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [data-length
data-length]
The no form of the command disables eth-test capabilities.
The no form of the command reverts to the default values.
The no form of the command reverts to the MAC address of the MEP back to the default, that of the port, since this is SAP based.
accept (SAP Level for Epipe and VPLS)
NOTE: Switching to the standby displays the following message.
WARNING: Configuration and/or Boot options may have changed since the last save.
Are you sure you want to switchover (y/n)?
Refer to the 7750 SR OS Basic System Configuration Guide.
This command performs a synchronization of the standby CPM/CFM’s images and/or config files to the active CPM/CFM. Either the
boot-env or
config parameter must be specified.
In the config>redundancy context, this command performs an automatically triggered standby CPM/CFM synchronization.
When the standby CPM/CFM takes over operation following a failure or reset of the active CPM/CFM, it is important to ensure that the active and standby CPM/CFMs have identical operational parameters. This includes the saved configuration, CPM and IOM images.This includes the saved configuration, CPM and IOM images.This includes the saved configuration and CFM images.
The active CPM/CFM ensures that the active configuration is maintained on the standby CPM/CFM. However, to ensure smooth operation under all circumstances, runtime images and system initialization configurations must also be automatically synchronized between the active and standby CPM/CFM.
The no form of this command sets the value to 2.
|
•
|
If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.
|
The no form of the command reverts to default value.
[no
] peer
ip-address create
|
Values
|
ipv4-address: a.b.c.dipv6-address: x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x: [0 — FFFF]H d: [0 — 255]D
|
The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.
The no form of this command disables BFD.
The no form of this command sets the interval to default.
The no form of this command sets the multiplier to default value
The no form of this command sets the interval to default value
The no form of this command will disable the passive mode behavior.
The no form of this command sets the system priority to default
The no form of this command administratively disables multi-chassis LAG. MC-LAG can be issued only when mc-lag is shutdown.
The no form of this command sets this parameter to default value.
The no form of this command sets the interval to default value
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority source-bmac-lsb
use-lacp-key
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority source-bmac-lsb
MAC-Lsb
lag lag-id lacp-key
admin-key system-id
system-id [remote-lag
remote-lag-id] system-priority
system-priority
lag lag-id [remote-lag
remote-lag-id]
The partner system (the system connected to all links forming MC-LAG) will consider all ports using the same lacp-key,
system-id,
system-priority as the part of the same LAG. In order to achieve this in MC operation, both redundant-pair nodes have to be configured with the same values. In case of the mismatch, MC-LAG is kept in oper-down status.
Note that the correct CLI command to enable MC LAG for a LAG in standby-signaling power-off mode is
lag lag-id [
remote-lag remote-lag-id]. In the CLI help output, the first three forms are used to enable MC LAG for a LAG in LACP mode. MC LAG is disabled (regardless of the mode) for a given LAG with
no lag lag-id.
The LAG identifier, expressed as a decimal integer. Specifying the lag-id allows the mismatch between lag-id on redundant-pair. If no
lag-id is specified it is assumed that neighbor system uses the same
lag-id as a part of the given MC-LAG. If no matching MC-LAG group can be found between neighbor systems, the individual LAGs will operate as usual (no MC-LAG operation is established.).
port [port-id | lag-id] [sync-tag
sync-tag]
range encap-range sync-tag
sync-tag
|
Values
|
Dot1Q start-vlan- end-vlan
QinQ Q1. start-vlan-Q1. end-vlan
|
The no form of the command removes the service-id from the IBC configuration.
This command enables the egress fp node that contains the multicast path management configuration commands for IOM-3 ingress multicast management.
The buffer-allocation command defines the amount of IOM3-XP 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 IOM3-XP 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 and the size if further fine-tuned by the forwarding class oversubscription factors.
Each WRED queue in a SAP egress QoS policy is created on an egress IOM3-XP when the policy is applied to an egress SAP on the IOM and at least one forwarding class is mapped to the queue. For WRED queue buffer management purposes, each forwarding class is configured with an MBS oversubscription factor (OSF) on the IOM using the
osf command. The MBS oversubscription factor is used by the system as a provisioning parameter that defines the acceptable level of oversubscription between the sum of the maximum buffer sizes (mbs) of the WRED queues for a given class and the number of buffers for that class in the WRED mega-pool. Since multiple forwarding classes may be mapped to the same queue, the oversubscription factor associated with the highest forwarding class mapped is used for dynamically sizing the WRED mega-pool.
And the forwarding plane on the IOM3-XP is configured with the following WRED limits:
The no form of the command immediately restores the default min and max percentage values for sizing the WRED mega-pool.
This required keyword defines the minimum percentage of total IOM3-XP queue buffers that will be applied to the WRED mega-pool. The value given for percent-of-total must be less than or equal to the value given for the
max percent-of-total. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
This required keyword defines the maximum percentage of total IOM3-XP queue buffers that may be applied to the WRED mega-pool. The value given for percent-of-total must be greater than or equal to the value given for the
min percent-of-total. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
This command defines the amount of IOM3-XP 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 IOM3-XP 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. Further control over shared congestion is defined later in this document under the slope-policy command.
Each WRED queue in a SAP egress QoS policy is created on an egress IOM3-XP when the policy is applied to an egress SAP on the IOM and at least one forwarding class is mapped to the queue. For WRED queue CBS buffer management purposes, each forwarding class is configured with a CBS oversubscription factor (OSF) on the IOM using the
osf command. The CBS oversubscription factor is used by the system as a provisioning parameter that defines the acceptable level of oversubscription between the sum of the committed buffer sizes (CBS) of the WRED queues for a given class and the number of buffers for that class that should be placed in the WRED mega-pool CBS reserve. Since multiple forwarding classes may be mapped to the same queue, the oversubscription factor associated with the highest forwarding class mapped is used for dynamically sizing the WRED mega-pool CBS reserve.
And the forwarding plane on theIOM3-XP is configured with the following WRED limits:
The no form of the command immediately restores the default min and max percentage values for sizing the WRED mega-pool CBS reserve.
This required keyword defines the minimum percentage of the IOM3-XP WRED mega-pool buffers that will be applied to the CBS reserve. The value given for percent-of-wred must be less than or equal to the value given for the max percent-of-wred. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
This 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 percent-of-wred must be greater than or equal to the value given for the min percent-of-wred. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).
The no form of the command restores the default slope policy to the WRED mega-pool.
The no form of the command removes the high-bandwidth IP multicast source designation from the forwarding plane.
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 IOM3-XP.
The ingress CLI node within the fp node contains the multicast path management configuration commands for IOM-3 ingress multicast management. The
bandwidth-policy command is supported within the ingress node.
The no stable-pool-sizing command is used to disable stable pool sizing on a forwarding plane. Existing buffer pools will be resized according to normal pool sizing behavior.
queue-group queue-group-name instance
instance-id [create
]
The no form of the command deletes a specific instance of a queue group.
specifies the instance of the named queue group to be created on the IOM/IMM ingress forwarding plane.
The no version of this command deletes the queue-group instance from the network ingress context of the forwarding plane.
The no form of this command removes the accounting policy association from the queue-group.
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.
The no form of this command removes the policer-control policy association from the queue-group.
NOTE: This feature is supported on all 50G FP2-based line cards and 100G/200G FP3-based line cards.
The no form of this command returns the ingress buffer allocation to the default value.
The policer-control-policy root max-rate setting may be overridden on each SAP or sub-profile where the policy is applied.
The max parameter 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.
The no max-rate command returns the policer-control-policy’s parent policer maximum rate to max.
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.
The second function the system uses the min-thresh-separation value for is determining the value per priority level for the fair-portion:
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:
|
•
|
If the mbs-contribution value is not set to zero:
|
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.
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.
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.
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.
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.
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.
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.
The mbs-contribution command is used to configure 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.
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.
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.
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.
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.
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.
The optional fixed keyword is used to force the inclusion of the defined mbs-contribution value (or an override value defined on the SAP or sla-profile) in the parent policer’s discard threshold calculations. If the
mbs-contribution command is executed without the
fixed keyword, the fixed calculation behavior for the priority level is removed.
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.
The no form of the command is used to remove any existing policer overrides.
The no form of this command is used to delete 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.
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.
stat-mode {no-stats
| minimal
| offered-profile-no-cir
| offered-priority-no-cir
| offered-limited-profile-cir
| offered-profile-cir
| offered-priority-cir
| offered-total-cir
}
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.
When collect-stats is enabled, the lack of counters causes the system to generate the following statistics:
The default stat-mode for a policer is
minimal. The
minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types (profile or priority) and do not count green or yellow output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With minimal enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-profile-no-cir mode is most useful when the policer is receiving only in-profile and out-of-profile pre-marked (and trusted) packets. It is expected that in this instance a CIR rate will not be defined since all packet are already pre-marked. This mode does not prevent the policer from receiving un-trusted (color undefined) nor does it prevent the policer from being configured with a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-profile-no-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-priority-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-priority-no-cir mode is most useful when the policer is receiving only un-trusted packets and the ingress priority high and priority low classification options are being used without a CIR profiling rate defined. This mode does not prevent the policer from receiving trusted packets that are pre-marked in-profile or out-of-profile nor does it prevent the policer from being configured with a CIR rate.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-priority-no-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-limitied-profile-cir mode allocates three forwarding plane offered counters and three traffic manager discard counters.
The offered-limited-profile-cir mode is most useful when the policer is receiving trusted out-of-profile (profile out but no profile in) traffic and un-trusted packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile packets.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-limited-profile-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.
The offered-profile-cir mode is most useful when the policer is receiving trusted out-of-profile and in-profile traffic and is also receiving un-trusted packets that are being applied to a defined CIR profiling rate. This mode differs from
offered-limited-profile-cir mode in that it expects both trusted in-profile and out-of-profile packets while still performing CIR profiling on packets with un-trusted markings. It is expected that in most cases where both trusted and un-trusted packets are received, the predominate case will not include trusted in-profile packets making the offered-limited-profile-cir accounting mode acceptable.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-profile-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-priority-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.
The offered-priority-cir mode is most useful when the policer is receiving only un-trusted packets that are being classified as high priority or low priority and are being applied to a defined CIR profiling rate. This mode differs from
offered-profile-cir mode in that it does not expect trusted in-profile and out-of-profile packets but does not exclude the ability of the policer to receive them.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-priority-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-total-cir mode is most useful when the policer is not receiving trusted in-profile or out-of-profile traffic and both high and low priority classifications are not being used on the un-trusted packets and the offered packets are being applied to a defined CIR profiling rate. This mode does not prevent the policer from receiving trusted in-profile or out-of-profile packets and does not prevent the use of priority high or low classifications on the un-trusted packets.
When collect-stats is enabled, the counters are used by the system to generate the following statistics:
With offered-total-cir enabled as the policer
stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values:
rate {max
| kilobits-per-second
} [cir
{max
| kilobits-per-second
}]
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 Kbps (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 is used to restore the default metering and profiling rate to a policer.
{max |
kilobits-per-second}
Specifying the keyword max or an explicit
kilobits-per-second 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.
cir {max | kilobits-per-second
}
The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit
kilobits-per-second 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 Kbps. 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 CPIR used is equivalent to max.
cbs {size [bytes
| kilobytes
] | default
}
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.
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
byte and
kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
mbs {size [bytes
| kilobytes
] | default
}
This command is used to configure 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 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.
When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes.
When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
This command is used to modify 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.
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 is used to remove per packet size modifications from the policer.
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.
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.
The no form of the command removes an explicit bandwidth policy from a forwarding plane or MDA and restores the default bandwidth policy.
*A:Dut-C# tools dump mcast-path-mgr cpm
McPathMgr[10][0]: 0x763a52c0 blkHoleEval 0
pPath swPlaneID pathType availBw pathLimit
inUseBw maxUsedBw numSGs
0x763a54c8 2 secondary 1800000
1800000 0 0 0
0x763a56c0 1 primary 1039959 2000000
960041 960041 6
0x763a58b8 15 primary 879910 2000000
1120090 1120090 7
0x763a5ab0 14 primary 879908 2000000
1120092 1120092 7
0x763a5ca8 13 primary 880007 2000000
1119993 1119993 7
0x763a5ea0 12 primary 880172 2000000
...
0x763a7448 0 none 0
0 0 0 0
0x763a7640 0 blackhole 0
0 0 0 0
McPathMgr[8][0]: 0x7639a9d8 blkHoleEval 0
pPath swPlaneID pathType availBw pathLimit
inUseBw maxUsedBw numSGs
0x7639abe0 1 secondary 1800000
1800000 0 0 0
0x7639add8 15 primary 2000000
2000000 0 0 0
0x7639afd0 14 primary 2000000
...0x7639cd58 0 blackhole 0
0 0 0 0
McPathMgr[9][0]: 0x76398420 blkHoleEval 0
pPath swPlaneID pathType availBw pathLimit
inUseBw maxUsedBw numSGs
0x76398628 15 secondary 1800000
1800000 0 0 0
0x76398820 14 primary 2000000
2000000 0 0 0
0x76398a18 13 primary 2000000
2000000 0 0 0
...
0x7639a7a0 0 blackhole 0
0 0 0 0
SwPlane[0]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98ba320 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[1]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98ba390 2000000 2000000 960041 1039959
1800000 0 1039959
###################################
stype inst src grp currBw pathBw pref repl path exp
0 1 10.10.6.33 227.0.0.23 159891 159891 0 0 P N
0 1 10.10.4.10 225.0.0.0 159990 159990 0 0 P N
0 1 10.10.4.27 225.0.0.17 159990 159990 0 0 P N
0 1 10.10.4.43 225.0.0.33 159993 159993 0 0 P N
0 1 10.10.6.47 227.0.0.37 160049 160049 0 0 P N
0 1 10.10.4.59 225.0.0.49 160128 160128 0 0 P N
SwPlane[2]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98ba400 2000000 2000000 1119789 880211
1800000 0 880211
###################################
...
###################################
stype inst src grp currBw pathBw pref repl path exp
0 1 10.10.6.29 227.0.0.19 159891 159891 0 0 P N
0 1 10.10.4.28 225.0.0.18 159989 159989 0 0 P N
0 1 10.10.4.11 225.0.0.1 159990 159990 0 0 P N
0 1 10.10.4.41 225.0.0.31 159992 159992 0 0 P N
0 1 10.10.6.43 227.0.0.33 160049 160049 0 0 P N
0 1 10.10.6.58 227.0.0.48 160052 160052 0 0 P N
0 1 10.10.4.55 225.0.0.45 160127 160127 0 0 P N
SwPlane[16]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98baa20 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[17]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98baa90 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[18]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98bab00 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[19]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98bab70 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[20]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
0x98babe0 2000000 2000000 0 2000000
1800000 0 1800000
SwPlane[21]
pSwPlane totalBw priBw priInUseBw priAvailBw
secBw secInUseBw secAvailBw
