card commands
configure
— card number
— admin-state keyword
— apply-groups reference
— apply-groups-exclude reference
— card-type keyword
— fail-on-error boolean
— filter-profile keyword
— fp number
— apply-groups reference
— apply-groups-exclude reference
— egress
— hs-fixed-high-thresh-delta number
— hs-pool-policy reference
— wred-queue-control
— admin-state keyword
— buffer-allocation decimal-number
— reserved-cbs decimal-number
— slope-policy reference
— fp-resource-policy reference
— hi-bw-mcast-src
— alarm boolean
— default-paths-only boolean
— group number
— ingress
— access
— queue-group reference instance-id number
— accounting-policy reference
— apply-groups reference
— apply-groups-exclude reference
— collect-stats boolean
— description string
— policer-control-policy
— overrides
— apply-groups reference
— apply-groups-exclude reference
— max-rate (number | keyword)
— priority-mbs-thresholds
— min-threshold-separation (number | keyword)
— priority number
— apply-groups reference
— apply-groups-exclude reference
— mbs-contribution (number | keyword)
— policy-name reference
— policer-overrides
— policer reference
— apply-groups reference
— apply-groups-exclude reference
— cbs (number | keyword)
— mbs (number | keyword)
— packet-byte-offset number
— rate
— cir (number | keyword)
— pir (number | keyword)
— stat-mode keyword
— dist-cpu-protection
— dynamic-enforcement-policer-pool number
— mcast-path-management
— admin-state keyword
— bandwidth-policy reference
— network
— pool string
— amber-alarm-threshold number
— apply-groups reference
— apply-groups-exclude reference
— red-alarm-threshold number
— resv-cbs
— amber-alarm-action
— max number
— step number
— cbs number
— slope-policy reference
— queue-group reference instance-id number
— accounting-policy reference
— apply-groups reference
— apply-groups-exclude reference
— collect-stats boolean
— description string
— policer-control-policy
— overrides
— apply-groups reference
— apply-groups-exclude reference
— max-rate (number | keyword)
— priority-mbs-thresholds
— min-threshold-separation (number | keyword)
— priority number
— apply-groups reference
— apply-groups-exclude reference
— mbs-contribution (number | keyword)
— policy-name reference
— policer-overrides
— policer reference
— apply-groups reference
— apply-groups-exclude reference
— cbs (number | keyword)
— mbs (number | keyword)
— packet-byte-offset number
— rate
— cir (number | keyword)
— pir (number | keyword)
— stat-mode keyword
— queue-policy reference
— policy-accounting
— classes number
— policers number
— ingress-buffer-allocation decimal-number
— init-extract-prio-mode keyword
— stable-pool-sizing boolean
— level keyword
— mda number
— access
— apply-groups reference
— apply-groups-exclude reference
— egress
— apply-groups reference
— apply-groups-exclude reference
— ingress
— apply-groups reference
— apply-groups-exclude reference
— admin-state keyword
— apply-groups reference
— apply-groups-exclude reference
— egress-xpl
— threshold number
— window number
— event keyword
— action keyword
— apply-groups reference
— apply-groups-exclude reference
— fail-on-error boolean
— ingress-xpl
— threshold number
— window number
— level keyword
— mda-type keyword
— network
— apply-groups reference
— apply-groups-exclude reference
— egress
— apply-groups reference
— apply-groups-exclude reference
— ingress
— apply-groups reference
— apply-groups-exclude reference
— power-priority-level number
— reset-on-recoverable-error boolean
— sync-e keyword
— upgrade number
— apply-groups reference
— apply-groups-exclude reference
— path keyword
— xconnect
— mac number
— apply-groups reference
— apply-groups-exclude reference
— description string
— loopback number
— apply-groups reference
— apply-groups-exclude reference
— bandwidth number
— description string
— power-save boolean
— reset-on-recoverable-error boolean
— upgrade number
— apply-groups reference
— apply-groups-exclude reference
— path keyword
— virtual-scheduler-adjustment
— apply-groups reference
— apply-groups-exclude reference
— internal-scheduler-weight-mode keyword
— interval
— rate-calculation-minimum
— fast-queue decimal-number
— slow-queue decimal-number
— scheduler-run-minimum decimal-number
— task-scheduling decimal-number
— slow-queue-threshold-rate number
— xiom string
— admin-state keyword
— apply-groups reference
— apply-groups-exclude reference
— fail-on-error boolean
— level keyword
— mda number
— admin-state keyword
— apply-groups reference
— apply-groups-exclude reference
— mda-type keyword
— power-priority-level number
— sync-e keyword
— xconnect
— mac number
— apply-groups reference
— apply-groups-exclude reference
— description string
— loopback number
— apply-groups reference
— apply-groups-exclude reference
— bandwidth number
— description string
— reset-on-recoverable-error boolean
— upgrade number
— apply-groups reference
— apply-groups-exclude reference
— path keyword
— xiom-type keyword
card command descriptions
card [slot-number] number
[slot-number] number
admin-state keyword
| Synopsis | Administrative state of the card | |
| Context | configure card number admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | enable | |
| Introduced | 16.0.R1 | |
Platforms | All |
card-type keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Card type | |
| Context | configure card number card-type keyword | |
| Tree | card-type | |
Description | This command adds an IOM, IMM, XCM to the device configuration for the slot. The card type can be pre-provisioned, meaning that the card does not need to be installed in the chassis. A card must be provisioned before any contained object can be configured: MDA, XIOM, XMA, MDA-s, connector, or port. A card can only be provisioned in a slot if the card type is allowed in the slot. An error message is generated if an attempt is made to provision a card type that is not allowed. If a card is inserted that does not match the configured card type for the slot, a log event and facility alarm is raised. The alarm is cleared when the correct card type is installed or the configuration is modified. A log event and facility alarm are raised if an administratively enabled card is removed from the chassis. The alarm is cleared when the correct card type is installed or the configuration is modified. A log event is issued when a card is removed that is administratively disabled. Because IMMs do not have the capability to install separate MDAs, the configuration of the MDAs is automatic. This configuration only includes the default options such as default buffer policies. Commands to manage the MDA remain in the MDA configuration context. Some card hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two card types that are the same, except for a “-ptp” suffix to indicate the second loadset. A hard reset of the card occurs when switching between the two provisioned types. An appropriate alarm is raised if a partial or complete card failure is detected. The alarm is cleared when the error condition ceases. | |
| Options | ||
| Introduced | 16.0.R1 | |
|
Platforms | All | |
fail-on-error boolean
| Synopsis | Set operational state of the card to Failed upon error | |
| Context | configure card number fail-on-error boolean | |
| Tree | fail-on-error | |
Description | When configured to true, 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 this command is set to true, and any one (or more) of the specific errors is detected, the operational state of the card is set to failed. This failed state persists until the clear card command is issued (reset) or the card is removed and reinserted (reseated). If the condition persists after reseating the card, contact Nokia support to investigate more. Nokia only recommends configuring this command to true when the network is designed to be able to route traffic around a failed card (redundant cards, nodes, or other paths exist). The list of specific errors includes the following: CHASSIS event ID# 2063 - tmnxEqCardPChipMemoryEvent CHASSIS event ID# 2076 - tmnxEqCardPChipCamEvent CHASSIS event ID# 2059 - tmnxEqCardPChipError (for ingress Ethernet only) CHASSIS event ID# 2098 - tmnxEqCardQChipBufMemoryEvent CHASSIS event ID# 2099 - tmnxEqCardQChipStatsMemoryEvent CHASSIS event ID# 2101 - tmnxEqCardQChipIntMemoryEvent CHASSIS event ID# 2103 - tmnxEqCardChipIfCellEvent On platforms with integrated CPM and IOM, IMM, or XCM, the node is rebooted if this command is set to true and one of the card level errors is encountered. The tmnxEqCardPChipError is only considered as a trigger for this command for ingress FCS errors (not egress FCS errors). Note: On the detection of the event or 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 determines whether the events are reported in logs (or SNMP traps, and so on) and the fail-on-error configuration determines 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). To facilitate post-failure analysis, Nokia recommends reporting the specific events or errors and that configure log log-events be enabled when this command is set to true. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | All |
filter-profile keyword
|
WARNING: Modifying this element toggles the admin-state of the parent element automatically for the new value to take effect. | ||
| Synopsis | Filter profile for the card | |
| Context | configure card number filter-profile keyword | |
| Tree | filter-profile | |
Description | This command controls the resources allocated to ingress and egress IPv4 and IPv6 filters on a per-line card basis on the SR-a platform. | |
| Options | ||
| Default | none | |
| Introduced | 19.10.R1 | |
Platforms | 7750 SR-a | |
fp [fp-number] number
[fp-number] number
egress
hs-fixed-high-thresh-delta number
| Synopsis | High threshold delta on the forwarding plane | |
| Context | configure card number fp number egress hs-fixed-high-thresh-delta number | |
| Tree | hs-fixed-high-thresh-delta | |
Description | This command specifies the egress aggregate shaper high burst limit threshold delta for this HSQ IOM FP. An aggregate rate can be applied to each egress HSQ queue group, HS secondary shaper, and (for subscribers configured with HS SLA expanded mode) primary shaper that manages the maximum burst limit over a specified shaping rate. Each aggregate shaper supports two thresholds that are used in conjunction with the low burst class setting. The system uses the lowest value attainable for each low threshold aggregate burst limit without causing shaper under run conditions. The high burst limit threshold is determined by adding the configured value of this command to the aggregate low burst limit threshold value. An operator must set this configured value to at least two times the maximum frame size to prevent lower threshold class forwarding from also affecting the higher threshold classes when forwarding larger packet sizes. An insufficiently high threshold delta defeats the intended purpose of mapping classes to the higher threshold. | |
| Range | 0 to 65536 | |
| Introduced | 16.0.R1 | |
|
Platforms | 7750 SR-7/12/12e |
hs-pool-policy reference
| Synopsis | HS pool policy | |
| Context | configure card number fp number egress hs-pool-policy reference | |
| Tree | hs-pool-policy | |
Description | This command specifies the HS pool policy for the FP. An HS pool policy contains the required parameters to create and size root and mid-tier buffer pools on an HSQ IOM, and applies a slope policy to each. A single HS pool policy is supported per port FP. This command is only applicable to the HSQ IOM (iom4-e-hs) and fails if configured on other card types. | |
Reference | configure qos hs-pool-policy string | |
| Introduced | 16.0.R1 | |
Platforms | 7750 SR-7/12/12e |
wred-queue-control
| Synopsis | Enter the wred-queue-control context | |
| Context | configure card number fp number egress wred-queue-control | |
| Tree | wred-queue-control | |
Description | Commands in this context configure the aggregate Weighted Random Early Detection (WRED) queue options for all WRED queues on an egress forwarding plane. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
admin-state keyword
| Synopsis | Administrative state of the WRED queue control function | |
| Context | configure card number fp number egress wred-queue-control admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | disable | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
buffer-allocation decimal-number
| Synopsis | Buffer allocation for WRED queue buffer pools | |
| Context | configure card number fp number egress wred-queue-control buffer-allocation decimal-number | |
| Tree | buffer-allocation | |
Description | This command defines the percentage of buffers to set aside for WRED queue buffer pools. | |
| Range | 0.01 to 99.99 | |
| Units | percent | |
| Default | 25.00 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
reserved-cbs decimal-number
| Synopsis | Buffers for queues operating within CBS thresholds | |
| Context | configure card number fp number egress wred-queue-control reserved-cbs decimal-number | |
| Tree | reserved-cbs | |
Description | This command specifies the percentage of buffers within the WRED mega-pool to set aside for WRED queues operating within the configured CBS thresholds. The forwarding plane protects against WRED queue buffer starvation by setting aside a portion of the buffers within the WRED mega-pool. This threshold defines when a WRED queue requests buffers from the 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, a seldom active queue is not denied a buffer from the mega-pool when the shared portion of the mega-pool is congested. | |
| Range | 0.01 to 99.99 | |
| Units | percent | |
| Default | 25.00 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
slope-policy reference
| Synopsis | Slope policy for the forwarding plane | |
| Context | configure card number fp number egress wred-queue-control slope-policy reference | |
| Tree | slope-policy | |
Reference | configure qos slope-policy string | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
fp-resource-policy reference
|
WARNING: Modifying this element resets the associated cards/XIOMs/MDAs for the new value to take effect. On the 7750 SR-1, the configuration must be saved and the router must be rebooted for the new value to take effect. | ||
| Synopsis | Resource policy to manage resources on the FP | |
| Context | configure card number fp number fp-resource-policy reference | |
| Tree | fp-resource-policy | |
Description | This command configures an FP resource policy used to manage resources on a forwarding plane that is FP4-based and later. The system creates a default policy that applies to all FP4 and later FPs. If an FP resource policy is removed from an FP, the system automatically applies the default policy to that FP. The system prevents the modification or deletion of the default policy, and the deletion of any user-created policy that is applied to an FP. | |
Reference | configure qos fp-resource-policy string | |
| Introduced | 20.2.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS | |
hi-bw-mcast-src
| Synopsis | Enable the hi-bw-mcast-src context | |
| Context | configure card number fp number hi-bw-mcast-src | |
| Tree | hi-bw-mcast-src | |
Description | Commands in this context configure the attributes to designate the FP as a high-bandwidth IP multicast source, expecting the ingress traffic to include high-bandwidth IP multicast traffic. When configured, the system attempts to allocate a dedicated multicast switch fabric plane (MSFP) to the forwarding plane. When a group is specified, all FPs in the group share the same MSFP. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS |
alarm boolean
| Synopsis | Raise an alarm when multiple traffic taps share a plane | |
| Context | configure card number fp number hi-bw-mcast-src alarm boolean | |
| Tree | alarm | |
Description | When configured to true, the router generates an event if the MDA must share an MSFP with another MDA in a different group. MDAs within the same group that share an MSFP do not generate an event. Additionally, if a failure occurs during normal operation or resources are removed, the system generates an event if it cannot maintain separation of MSFPs for the MDAs. When configured to false, the router does not generate events. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS |
default-paths-only boolean
| Synopsis | Allocate the default paths to dedicated MSFPs | |
| Context | configure card number fp number hi-bw-mcast-src default-paths-only boolean | |
| Tree | default-paths-only | |
Description | When configured to true, the system only attempts to allocate the two default paths (one high priority and one low priority) to dedicated MSFPs. When configured to false, the default path allocation is disabled. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS |
group number
| Synopsis | Logical MSFP group for the MDA | |
| Context | configure card number fp number hi-bw-mcast-src group number | |
| Tree | group | |
Description | This command specifies the logical MSFP group for the MDA. If a group is specified, all FPs in the group share the same MSFP. | |
| Range | 0 to 32 | |
| Default | 0 | |
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS |
ingress
access
queue-group [queue-group-name] reference instance-id number
| Synopsis | Enter the queue-group list instance | |
| Context | configure card number fp number ingress access queue-group reference instance-id number | |
| Tree | queue-group | |
Description | Commands in this context create a named queue group template on the ingress forwarding plane of an IOM or IMM. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[queue-group-name] reference
| Synopsis | Queue group name | |
| Context | configure card number fp number ingress access queue-group reference instance-id number | |
| Tree | queue-group | |
Reference | configure qos queue-group-templates ingress queue-group string | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
instance-id number
| Synopsis | Instance ID | |
| Context | configure card number fp number ingress access queue-group reference instance-id number | |
| Tree | queue-group | |
| Range | 1 to 65535 | |
| MD-CLI Default | 1 | |
|
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
accounting-policy reference
| Synopsis | Accounting policy for the FP ingress queue group | |
| Context | configure card number fp number ingress access queue-group reference instance-id number accounting-policy reference | |
| Tree | accounting-policy | |
Description | This command configures an accounting policy for the FP ingress queue group. You can only apply accounting policies associated with service billing to SAPs. Only associate the accounting policy with one interface at a time. | |
Reference | configure log accounting-policy number | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
collect-stats boolean
| Synopsis | Collect statistics on FP ingress queue group | |
| Context | configure card number fp number ingress access queue-group reference instance-id number collect-stats boolean | |
| Tree | collect-stats | |
Description | When configured to true, the system collects accounting and statistical data for the queue group on the FP. When configured to false, the system still accumulates the statistics; however, the CPU does not obtain the results and write them to the billing file. If this command is set to true (after it had previously been set to false), the counters written to the billing file include the traffic collected when the command was set to false. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
description string
| Synopsis | Text description | |
| Context | configure card number fp number ingress access queue-group reference instance-id number description string | |
| Tree | description | |
| String Length | 1 to 80 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer-control-policy
| Synopsis | Enter the policer-control-policy context | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy | |
| Tree | policer-control-policy | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
overrides
| Synopsis | Enable the overrides context | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides | |
| Tree | overrides | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
max-rate (number | keyword)
| Synopsis | Maximum rate override | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides max-rate (number | keyword) | |
| Tree | max-rate | |
Description | This command defines the PIR leaky bucket decrement rate of the parent policer. Each time you apply the policer control policy to a SAP or subscriber instance a parent policer is created. Packets not discarded by the child policer associated with the SAP or subscriber instance are evaluated against the leaky bucket of the parent policer. For each packet, the system first decrements the bucket by the correct amount based on the decrement rate to derive the current bucket depth. The system compares the current depth to one of two discard thresholds associated with the packet. The first discard threshold is applied if the Fair Information Rate (FIR) leaky bucket of the child policer is in the confirming state. The second discard threshold is applied if the FIR leaky bucket of the child policer is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet. If the result is conform, the bucket depth is increased by the size of the packet (plus or minus the per-packet offset setting in the child policer) and the parent policer does not discard the packet. If the result is violate, the bucket depth is not increased and the parent policer discards the packet. When the parent policer discards a packet, the bucket depth increases (PIR, CIR, and FIR) in the parent policer are canceled. This prevents packets that the parent policer discards from consuming the PIR, CIR, and FIR bandwidth of the child policers. | |
| Range | 1 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
priority-mbs-thresholds
| Synopsis | Enter the priority-mbs-thresholds context | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds | |
| Tree | priority-mbs-thresholds | |
Description | Commands in this context configure the derivative for the shared portion and fair portion for each priority level. The system uses the shared portion and fair portion values to calculate the discard-unfair and discard-all MBS thresholds that enforce priority-sensitive rate-based discards within the root arbiter parent policer. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
min-threshold-separation (number | keyword)
| Synopsis | Minimum separation between any two active thresholds | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds min-threshold-separation (number | keyword) | |
| Tree | min-threshold-separation | |
Description | This command configures the minimum separation between any two active thresholds in the parent policer. | |
| Range | 0 to 16777216 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
priority [level] number
| Synopsis | Enter the priority list instance | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number | |
| Tree | priority | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[level] number
| Synopsis | Priority level, higher number is stricter | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number | |
| Tree | priority | |
| Range | 1 to 8 | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
mbs-contribution (number | keyword)
| Synopsis | MBS contribution size override | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number mbs-contribution (number | keyword) | |
| Tree | mbs-contribution | |
Description | This command specifies the packet burst capacity required at the parent policer for a specified priority level with at least one child, and where the total capacity also includes the capacity of all lower thresholds. | |
| Range | 0 to 16777216 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policy-name reference
| Synopsis | Policer control policy name | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-control-policy policy-name reference | |
| Tree | policy-name | |
Reference | configure qos policer-control-policy string | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer-overrides
| Synopsis | Enter the policer-overrides context | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides | |
| Tree | policer-overrides | |
Description | Commands in this context configure specific overrides to one or more policers created on the SAP through SAP ingress QoS policies. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer [policer-id] reference
| Synopsis | Enter the policer list instance | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference | |
| Tree | policer | |
Description | Commands in this context create, modify, or delete a policer. Policers are created and used in a similar manner to queues. Unlike queues that have dedicated counters, policers allow various stat-mode settings that define the counters to be associated with the policer. Packet byte offset provides a policer with the ability to modify the size of each packet based on a defined number of bytes. All policers must be created within the QoS policies. After a policer is created, it cannot be deleted from the QoS policy unless all forwarding classes mapped to the policer are first moved to other policers or queues. The system allows a policer to be created on a SAP QoS policy regardless of the ability to support policers on objects where the policy is currently applied. The system only scans the current objects for policer support and sufficient resources to create the policer when a forwarding class is first mapped to the policer ID. If the policer cannot be created because one or more instances of the policy do not support policing or have insufficient resources to create the policer, the forwarding class mapping fails. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[policer-id] reference
| Synopsis | Policer ID | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference | |
| Tree | policer | |
Reference | configure qos queue-group-templates ingress queue-group string policer number | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
cbs (number | keyword)
| Synopsis | CBS tolerance allowed by the policer | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference cbs (number | keyword) | |
| Tree | cbs | |
Description | This command configures the CIR leaky bucket exceed threshold of the policer. If the forwarding rate of the policer is equal to or less than the defined CIR, the CIR bucket depth hovers around the 0 depth, with spikes up to the maximum packet size in the offered load. If the forwarding rate increases beyond the profiling rate, the threshold caps the amount of data allowed to be in-profile above the rate. | |
| Range | 0 to 268435456 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
mbs (number | keyword)
| Synopsis | Maximum burst tolerance allowed by the policer | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference mbs (number | keyword) | |
| Tree | mbs | |
Description | This command configures the PIR leaky bucket violate threshold of the policer. Ingress, trusted in-profile packets and untrusted high priority packets use the high priority violate threshold and trusted out-of-profile. Untrusted low priority packets use the low priority violate threshold. If the offered rate of the policer is equal to or less than the defined rate, the PIR bucket depth hovers around the 0 depth, with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the threshold caps the amount of data allowed above the rate. The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Because all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance is available for higher priority traffic. | |
| Range | 0 to 268435456 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
packet-byte-offset number
| Synopsis | Packet size adjustment | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference packet-byte-offset number | |
| Tree | packet-byte-offset | |
Description | This command modifies the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. Use this command to add downstream frame encapsulation or remove portions of packet headers. When child policers add to or subtract from the packet size, the minimum threshold separation value of the parent policer must be modified by the same amount. | |
| Range | -32 to 31 | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
rate
| Synopsis | Enter the rate context | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference rate | |
| Tree | rate | |
Description | Commands in this context configure the metering and optional profiling rates of the policer. The metering rate is used by the system to configure the PIR leaky bucket decrement rate and the profiling rate configures the CIR leaky bucket decrement rate. The decrement function empties the bucket; packets applied to the bucket attempt to fill it based on its packet size. If the bucket fills faster than the rate that it empties, the bucket depth eventually reaches its exceeded (CIR) or violate (PIR) threshold. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
cir (number | keyword)
| Synopsis | CIR for the policer | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference rate cir (number | keyword) | |
| Tree | cir | |
Description | This command overrides the default CIR rate of the policer. When the policer is first created, the profiling rate defaults to 0 kb/s. When max is configured, the maximum policer rate used is equal to the maximum capacity of the card that the policer is configured for. If the policer rate is set to a value larger than the maximum rate possible for the card, the CIR used is equivalent to maximum. | |
| Range | 0 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
pir (number | keyword)
| Synopsis | PIR for the policer | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference rate pir (number | keyword) | |
| Tree | pir | |
Description | This command configures the metering rate of the policer for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. When max is configured, the maximum policer rate used is equal to the maximum capacity of the card that the policer is configured for. If the policer rate is set to a value larger than the maximum rate possible for the card, the PIR used is equivalent to maximum. | |
| Range | 1 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
stat-mode keyword
| Synopsis | Stat mode for the policer | |
| Context | configure card number fp number ingress access queue-group reference instance-id number policer-overrides policer reference stat-mode keyword | |
| Tree | stat-mode | |
Description | This command specifies the forwarding plane counters that allow offered, output, and discard accounting to occur for the policer. | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
dist-cpu-protection
| Synopsis | Enter the dist-cpu-protection context | |
| Context | configure card number fp number ingress dist-cpu-protection | |
| Tree | dist-cpu-protection | |
Description | Commands in this context configure the distributed CPU protection forwarding plane settings. | |
| Introduced | 21.2.R1 | |
Platforms | All |
dynamic-enforcement-policer-pool number
| Synopsis | Number of policers reserved as enforcement policers use | |
| Context | configure card number fp number ingress dist-cpu-protection dynamic-enforcement-policer-pool number | |
| Tree | dynamic-enforcement-policer-pool | |
Description | This command reserves a set of policers for use as dynamic enforcement policers for the Distributed CPU Protection (DCP) feature. Policers are allocated from this pool and instantiated as per-object per-protocol dynamic enforcement policers after a local monitor is triggered for an object, such as a SAP or network interface. A change to this configured value automatically clears the high water mark, timestamp, and failed allocation count. If the command is configured to a value below the currently used or allocated number, all dynamic policers are returned to the free pool (and traffic returns to the local monitors). | |
| Range | 1000 to 32000 | |
| Introduced | 21.2.R1 | |
Platforms | All |
mcast-path-management
| Synopsis | Enter the mcast-path-management context | |
| Context | configure card number fp number ingress mcast-path-management | |
| Tree | mcast-path-management | |
Description | Commands in this context configure the IOM ingress multicast path management forwarding plane settings. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR |
admin-state keyword
| Synopsis | Administrative state of multicast path management | |
| Context | configure card number fp number ingress mcast-path-management admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | disable | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR |
bandwidth-policy reference
| Synopsis | Bandwidth policy for ingress multicast path management | |
| Context | configure card number fp number ingress mcast-path-management bandwidth-policy reference | |
| Tree | bandwidth-policy | |
Description | This command specifies the bandwidth policy associated with the forwarding plane. The bandwidth policy defines the dynamic rate table and the multicast paths bandwidth and queuing parameters. If a bandwidth policy is not explicitly associated with a forwarding plane, the default bandwidth policy is used with ingress multicast path management. | |
Reference | configure multicast-management bandwidth-policy string | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR |
network
pool [name] string
[name] string
amber-alarm-threshold number
| Synopsis | Amber alarm threshold allowed on oversubscription | |
| Context | configure card number fp number ingress network pool string amber-alarm-threshold number | |
| Tree | amber-alarm-threshold | |
Description | This command configures the threshold for the amber alarm on oversubscription. If both amber and red alarm thresholds are configured, the amber alarm threshold must be equal to or less than the red alarm threshold. | |
| Range | 1 to 1000 | |
| Units | percent | |
| Introduced | 19.5.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
red-alarm-threshold number
| Synopsis | Red alarm threshold allowed on oversubscription | |
| Context | configure card number fp number ingress network pool string red-alarm-threshold number | |
| Tree | red-alarm-threshold | |
Description | This command configures the threshold for the red alarm on oversubscription. If both amber and red alarm thresholds are configured, the red alarm threshold must be equal to or exceed the amber alarm threshold. | |
| Range | 1 to 1000 | |
| Units | percent | |
| Introduced | 19.5.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
resv-cbs
| Synopsis | Enter the resv-cbs context | |
| Context | configure card number fp number ingress network pool string resv-cbs | |
| Tree | resv-cbs | |
Description | Commands in this context specify the pool buffer settings. The commands do not set aside buffers within the buffer pool for CBS reservation. The CBS value per queue only determines the point at which enqueuing packets are subject to a RED slope. CBS oversubscription can result in a queue operating within its CBS configuration and still being unable to enqueue a packet due to unavailable buffers. | |
| Introduced | 19.5.R1 | |
Platforms | All |
amber-alarm-action
| Synopsis | Enter the amber-alarm-action context | |
| Context | configure card number fp number ingress network pool string resv-cbs amber-alarm-action | |
| Tree | amber-alarm-action | |
Description | Commands in this context specify settings for the reserved Committed Burst Size (CBS) and step change when the amber alert threshold is exceeded. The reserved CBS defines the amount of buffer space within the pool that is not considered shared. | |
| Introduced | 19.5.R1 | |
Platforms | All |
max number
| Synopsis | Maximum reserved CBS size of the pool | |
| Context | configure card number fp number ingress network pool string resv-cbs amber-alarm-action max number | |
| Tree | max | |
Description | This command configures the maximum reserved CBS size of the pool. To enable adaptive CBS sizing, this command and the step command must be configured. The value for this command must not be more than the configure card fp ingress network pool resv-cbs cbs command. When the configure card fp ingress network pool resv-cbs cbs command is set to a value of zero (0), adaptive CBS sizing is disabled. | |
| Range | 1 to 100 | |
| Units | percent | |
| Introduced | 19.5.R1 | |
Platforms |
All |
step number
| Synopsis | Step-size percentage for reserved CBS size of the pool | |
| Context | configure card number fp number ingress network pool string resv-cbs amber-alarm-action step number | |
| Tree | step | |
Description | This command configures the step-size percentage for the reserved CBS size of the pool. To enable adaptive CBS sizing, this command and the max command must be configured. When the configure card fp ingress network pool resv-cbs cbs command is set to a value of zero (0), adaptive CBS sizing is disabled. | |
| Range | 1 to 100 | |
| Units | percent | |
| Introduced | 19.5.R1 | |
Platforms |
All |
cbs number
| Synopsis | Pool size reserved for CBS | |
| Context | configure card number fp number ingress network pool string resv-cbs cbs number | |
| Tree | cbs | |
Description | This command configures the percentage of pool size reserved for CBS. For network, the default value is computed as the sum of the CBS request by the entities using the pool. For access, the default value is 30%. | |
| Range | 0 to 100 | |
| Units | percent | |
| Introduced | 19.5.R1 | |
Platforms |
All |
slope-policy reference
| Synopsis | Slope policy | |
| Context | configure card number fp number ingress network pool string slope-policy reference | |
| Tree | slope-policy | |
Description | This command specifies the slope policy that defines the high and low priority RED slope parameters and the time average factor. | |
Reference | configure qos slope-policy string | |
| Introduced | 19.5.R1 | |
Platforms | All |
queue-group [queue-group-name] reference instance-id number
| Synopsis | Enter the queue-group list instance | |
| Context | configure card number fp number ingress network queue-group reference instance-id number | |
| Tree | queue-group | |
Description | Commands in this context configure IOM ingress network forwarding plane queue-group settings. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[queue-group-name] reference
| Synopsis | Queue group name | |
| Context | configure card number fp number ingress network queue-group reference instance-id number | |
| Tree | queue-group | |
Reference | configure qos queue-group-templates ingress queue-group string | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
instance-id number
| Synopsis | Instance ID | |
| Context | configure card number fp number ingress network queue-group reference instance-id number | |
| Tree | queue-group | |
| Range | 1 to 65535 | |
| MD-CLI Default | 1 | |
|
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
accounting-policy reference
| Synopsis | Accounting policy for the FP ingress queue group | |
| Context | configure card number fp number ingress network queue-group reference instance-id number accounting-policy reference | |
| Tree | accounting-policy | |
Description | This command configures an accounting policy for the FP ingress queue group. You can only apply accounting policies associated with service billing to SAPs. Only associate the accounting policy with one interface at a time. | |
Reference | configure log accounting-policy number | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
collect-stats boolean
| Synopsis | Collect statistics on FP ingress queue group | |
| Context | configure card number fp number ingress network queue-group reference instance-id number collect-stats boolean | |
| Tree | collect-stats | |
Description | When configured to true, the system collects accounting and statistical data for the queue group on the FP. When configured to false, the system still accumulates the statistics; however, the CPU does not obtain the results and write them to the billing file. If this command is set to true (after it had previously been set to false), the counters written to the billing file include the traffic collected when the command was set to false. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
description string
| Synopsis | Text description | |
| Context | configure card number fp number ingress network queue-group reference instance-id number description string | |
| Tree | description | |
| String Length | 1 to 80 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer-control-policy
| Synopsis | Enter the policer-control-policy context | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy | |
| Tree | policer-control-policy | |
Description | Commands in this context configure the IOM ingress network forwarding plane queue-group policer control policy settings. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
overrides
| Synopsis | Enable the overrides context | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides | |
| Tree | overrides | |
Description | Commands in this context configure the IOM ingress network forwarding plane queue-group policer control policy override settings. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
max-rate (number | keyword)
| Synopsis | Maximum rate override | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides max-rate (number | keyword) | |
| Tree | max-rate | |
Description | This command defines the PIR leaky bucket decrement rate of the parent policer. Each time you apply the policer control policy to a SAP or subscriber instance a parent policer is created. Packets not discarded by the child policer associated with the SAP or subscriber instance are evaluated against the leaky bucket of the parent policer. For each packet, the system first decrements the bucket by the correct amount based on the decrement rate to derive the current bucket depth. The system compares the current depth to one of two discard thresholds associated with the packet. The first discard threshold is applied if the Fair Information Rate (FIR) leaky bucket of the child policer is in the confirming state. The second discard threshold is applied if the FIR leaky bucket of the child policer is in the exceed state. Only one of the two thresholds is applied per packet. If the current depth of the parent policer PIR bucket is less than the threshold value, the parent PIR bucket is in the conform state for that particular packet. If the depth is equal to or greater than the applied threshold, the bucket is in the violate state for the packet. If the result is conform, the bucket depth is increased by the size of the packet (plus or minus the per-packet offset setting in the child policer) and the parent policer does not discard the packet. If the result is violate, the bucket depth is not increased and the parent policer discards the packet. When the parent policer discards a packet, the bucket depth increases (PIR, CIR, and FIR) in the parent policer are canceled. This prevents packets that the parent policer discards from consuming the PIR, CIR, and FIR bandwidth of the child policers. | |
| Range | 1 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
priority-mbs-thresholds
| Synopsis | Enter the priority-mbs-thresholds context | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds | |
| Tree | priority-mbs-thresholds | |
Description | Commands in this context configure settings to derive the shared portion and fair portion for each priority level. The system uses the shared portion and fair portion values to calculate the discard-unfair and discard-all MBS thresholds that enforce priority-sensitive rate-based discards within the root arbiter parent policer. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
min-threshold-separation (number | keyword)
| Synopsis | Minimum separation between any two active thresholds | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds min-threshold-separation (number | keyword) | |
| Tree | min-threshold-separation | |
Description | This command configures the minimum separation between any two active thresholds in the parent policer. | |
| Range | 0 to 16777216 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
priority [level] number
| Synopsis | Enter the priority list instance | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number | |
| Tree | priority | |
Description | Commands in this context configure the list of priority MBS threshold priority settings for IOM ingress network forwarding plane queue-group policer control policy overrides. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[level] number
| Synopsis | Priority level, higher number is stricter | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number | |
| Tree | priority | |
| Range | 1 to 8 | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
mbs-contribution (number | keyword)
| Synopsis | MBS contribution size override | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy overrides priority-mbs-thresholds priority number mbs-contribution (number | keyword) | |
| Tree | mbs-contribution | |
Description | This command specifies the packet burst capacity required at the parent policer for a specified priority level with at least one child, and where the total capacity also includes the capacity of all lower thresholds. | |
| Range | 0 to 16777216 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policy-name reference
| Synopsis | Policer control policy name | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-control-policy policy-name reference | |
| Tree | policy-name | |
Reference | configure qos policer-control-policy string | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer-overrides
| Synopsis | Enter the policer-overrides context | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides | |
| Tree | policer-overrides | |
Description | Commands in this context configure the policer overrides for the IOM ingress network forwarding plane queue-groups. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
policer [policer-id] reference
| Synopsis | Enter the policer list instance | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference | |
| Tree | policer | |
Description | Commands in this context configure the list of policer override parameters for IOM ingress network forwarding plane queue-groups. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
[policer-id] reference
| Synopsis | Policer ID | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference | |
| Tree | policer | |
Reference | configure qos queue-group-templates ingress queue-group string policer number | |
Notes | This element is part of a list key. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
cbs (number | keyword)
| Synopsis | CBS tolerance allowed by the policer | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference cbs (number | keyword) | |
| Tree | cbs | |
Description | This command configures the CIR leaky bucket exceed threshold of the policer. If the forwarding rate of the policer is equal to or less than the defined CIR, the CIR bucket depth hovers around the 0 depth, with spikes up to the maximum packet size in the offered load. If the forwarding rate increases beyond the profiling rate, the threshold caps the amount of data allowed to be in-profile above the rate. | |
| Range | 0 to 268435456 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
mbs (number | keyword)
| Synopsis | Maximum burst tolerance allowed by the policer | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference mbs (number | keyword) | |
| Tree | mbs | |
Description | This command configures the PIR leaky bucket violate threshold of the policer. Ingress, trusted in-profile packets and untrusted high priority packets use the high priority violate threshold and trusted out-of-profile. Untrusted low priority packets use the low priority violate threshold. If the offered rate of the policer is equal to or less than the defined rate, the PIR bucket depth hovers around the 0 depth, with spikes up to the maximum packet size in the offered load. If the offered rate increases beyond the metering rate, the threshold caps the amount of data allowed above the rate. The low priority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer. Because all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance is available for higher priority traffic. | |
| Range | 0 to 268435456 | |
| Units | bytes | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
packet-byte-offset number
| Synopsis | Packet size adjustment | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference packet-byte-offset number | |
| Tree | packet-byte-offset | |
Description | This command modifies the size of each packet handled by the policer by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed. Use this command to add downstream frame encapsulation or remove portions of packet headers. When child policers add to or subtract from the packet size, the minimum threshold separation value of the parent policer must be modified by the same amount. | |
| Range | -32 to 31 | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
rate
| Synopsis | Enter the rate context | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference rate | |
| Tree | rate | |
Description | Commands in this context configure the metering and optional profiling rates of the policer. The metering rate is used by the system to configure the PIR leaky bucket decrement rate and the profiling rate configures the CIR leaky bucket decrement rate. The decrement function empties the bucket; packets applied to the bucket attempt to fill it based on its packet size. If the bucket fills faster than the rate that it empties, the bucket depth eventually reaches its exceeded (CIR) or violate (PIR) threshold. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
cir (number | keyword)
| Synopsis | CIR for the policer | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference rate cir (number | keyword) | |
| Tree | cir | |
Description | This command overrides the default CIR rate of the policer. When the policer is first created, the profiling rate defaults to 0 kb/s. When max is configured, the maximum policer rate used is equal to the maximum capacity of the card that the policer is configured for. If the policer rate is set to a value larger than the maximum rate possible for the card, the CIR used is equivalent to maximum. | |
| Range | 0 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
pir (number | keyword)
| Synopsis | PIR for the policer | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference rate pir (number | keyword) | |
| Tree | pir | |
Description | This command configures the metering rate of the policer for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. When max is configured, the maximum policer rate used is equal to the maximum capacity of the card that the policer is configured for. If the policer rate is set to a value larger than the maximum rate possible for the card, the PIR used is equivalent to maximum. | |
| Range | 1 to 2000000000 | |
| Units | kilobps | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
stat-mode keyword
| Synopsis | Stat mode for the policer | |
| Context | configure card number fp number ingress network queue-group reference instance-id number policer-overrides policer reference stat-mode keyword | |
| Tree | stat-mode | |
Description | This command specifies the forwarding plane counters that allow offered, output, and discard accounting to occur for the policer. | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR |
queue-policy reference
| Synopsis | Network queue policy | |
| Context | configure card number fp number ingress network queue-policy reference | |
| Tree | queue-policy | |
Reference | configure qos network-queue string | |
| Introduced | 19.5.R1 | |
Platforms | All |
policy-accounting
| Synopsis | Enter the policy-accounting context | |
| Context | configure card number fp number ingress policy-accounting | |
| Tree | policy-accounting | |
Description | Commands in this context configure policy accounting. Use policy accounting to collect statistics about the amount of traffic matching particular routes or to police traffic associated with certain routes as destinations of the traffic. | |
| Introduced | 20.10.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS |
classes number
| Synopsis | Number of accounting classes for the forwarding plane | |
| Context | configure card number fp number ingress policy-accounting classes number | |
| Tree | classes | |
Description | This command specifies the maximum number of source and destination classes that can be instantiated for accounting purposes on the interfaces of a specific card or FP. When unconfigured, resources are not reserved for source or destination classes. | |
| Range | 1000 to 128000 | |
| Introduced | 21.2.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS |
policers number
ingress-buffer-allocation decimal-number
| Synopsis | Ingress buffer pool allocation for the forwarding plane | |
| Context | configure card number fp number ingress-buffer-allocation decimal-number | |
| Tree | ingress-buffer-allocation | |
Description | This command configures an ingress buffer allocation for the FP. Ingress buffer allocation applies to user-accessible buffers (total buffers less those reserved for system use). The ingress buffer allocation determines how much of the user-accessible buffers are available for ingress purposes. The remaining buffers are available for egress purposes. | |
| Range | 20.00 to 80.00 | |
| Units | percent | |
| Default | 50.00 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e, 7950 XRS |
init-extract-prio-mode keyword
| Synopsis | Initial drop priority mode of extracted traffic | |
| Context | configure card number fp number init-extract-prio-mode keyword | |
| Tree | init-extract-prio-mode | |
Description | This command specifies the scheme to select the initial drop priority of extracted control plane traffic. The initial drop priority of extracted packets can be either low or high priority. The drop priority can be altered subsequently by mechanisms such as CPU protection. High priority traffic receives preferential treatment in control plane congestion situations over low priority traffic. | |
| Options | ||
| Default | uniform | |
| Introduced | 16.0.R1 | |
Platforms | All |
stable-pool-sizing boolean
| Synopsis | Enable stable pool sizing for the forwarding plane | |
| Context | configure card number fp number stable-pool-sizing boolean | |
| Tree | stable-pool-sizing | |
Description | When configured to true, the router provides a stable buffer pool allocation environment for all default port buffer pools on the forwarding plane. This stable environment is provided at the expense of optimal buffer allocation between the various port buffer pools. When configured to false, the router disables stable pool sizing on the forwarding plane. Existing buffer pools are resized according to normal pool sizing behavior. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
level keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | License level of the card | |
| Context | configure card number level keyword | |
| Tree | level | |
Description | This command configures the license level of the card. New generations of cards include variants controlled by hardware and software licensing. For these cards, the license level must be provisioned in addition to the card type. A card cannot become operational unless the provisioned license level matches the license level of the card installed into the slot.The set of license levels varies by card type. The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress user queues and egress policers. Changes to the provisioned license level may be blocked if configuration exists that would not be permitted with the new target license level. If the license level is not specified, the level is set to the highest license level for that card. | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-1se | |
mda [mda-slot] number
[mda-slot] number
access
egress
ingress
admin-state keyword
| Synopsis | Administrative state of the MDA | |
| Context | configure card number mda number admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | enable | |
| Introduced | 16.0.R1 | |
Platforms | All |
egress-xpl
| Synopsis | Enter the egress-xpl context | |
| Context | configure card number mda number egress-xpl | |
| Tree | egress-xpl | |
Description | Commands in this context specify settings for the fail-on-error feature. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
threshold number
| Synopsis | Threshold value for XPL errors | |
| Context | configure card number mda number egress-xpl threshold number | |
| Tree | threshold | |
Description | This command configures the threshold for XPL errors. If the number of XPL errors exceeds the threshold value defined by the window value command, the MDA is placed in the failed state. | |
| Range | 1 to 1000000 | |
| Units | xpl errors | |
| Default | 1000 | |
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
window number
| Synopsis | Time interval to measure XPL error frequency | |
| Context | configure card number mda number egress-xpl window number | |
| Tree | window | |
Description | This command configures the time interval used to measure the frequency of XPL errors for the fail-on-error feature. If the number of XPL errors exceeds the threshold value in defined by this command, the MDA is placed in the Failed state. | |
| Range | 1 to 1440 | |
| Units | minutes | |
| Default | 60 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
event [type] keyword
| Synopsis | Enter the event list instance | |
| Context | configure card number mda number event keyword | |
| Tree | event | |
Description | Commands in this context allow the user to control the action taken when a specific hardware error event is raised against the target MDA. If no event action has been created for a specific event type, the management plane of the router ignores the hardware errors related to that event type. | |
| Introduced | 19.7.R1 | |
Platforms | All |
[type] keyword
| Synopsis | MDA event type being monitored | |
| Context | configure card number mda number event keyword | |
| Tree | event | |
Description | This command configures the type of event to be acted upon.
| |
| Options | ||
Notes | This element is part of a list key. | |
| Introduced | 19.7.R1 | |
Platforms | All |
action keyword
| Synopsis | Action when a specific hardware error event is raised | |
| Context | configure card number mda number event keyword action keyword | |
| Tree | action | |
Description | This command defines the action taken when a specific hardware error event is detected on the target MDA. When no event action is specified for an event type, the hardware errors related to the event type are ignored by the management plane of the router. Actions include the following:
| |
| Options | ||
| Introduced | 19.7.R1 | |
Platforms |
All |
fail-on-error boolean
| Synopsis | Set operational state to Failed if an error is detected | |
| Context | configure card number mda number fail-on-error boolean | |
| Tree | fail-on-error | |
Description | When configured to true, the fail-on-error feature is enabled on the MDA. When a defined rate of egress or ingress XPL errors occur on an MDA within a specified time interval, the MDA is placed in the Failed state. This can force an APS switchover or traffic to be rerouted. 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 configure card mda egress-xpl and configure card mda ingress-xpl contexts. See "Fail-on-error overview" in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Troubleshooting Guide for more information. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | All |
ingress-xpl
| Synopsis | Enter the ingress-xpl context | |
| Context | configure card number mda number ingress-xpl | |
| Tree | ingress-xpl | |
Description | Commands in this context specify settings for ingress XPL error occurrences. | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
threshold number
| Synopsis | Threshold value for XPL errors | |
| Context | configure card number mda number ingress-xpl threshold number | |
| Tree | threshold | |
Description | This command configures the threshold for XPL errors. If the number of XPL errors exceeds the threshold value defined by the window value command, the MDA is placed in the failed state. | |
| Range | 1 to 1000000 | |
| Units | xpl errors | |
| Default | 1000 | |
| Introduced | 16.0.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
window number
| Synopsis | Time interval to measure XPL error frequency | |
| Context | configure card number mda number ingress-xpl window number | |
| Tree | window | |
Description | This command configures the time interval used to measure the frequency of XPL errors for the fail-on-error feature. If the number of XPL errors exceeds the threshold value in defined by this command, the MDA is placed in the Failed state. | |
| Range | 1 to 1440 | |
| Units | minutes | |
| Default | 60 | |
| Introduced | 16.0.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS |
level keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | MDA card level | |
| Context | configure card number mda number level keyword | |
| Tree | level | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS | |
mda-type keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | MDA type for the slot | |
| Context | configure card number mda number mda-type keyword | |
| Tree | mda-type | |
Description | This command provisions a specific MDA type to the device configuration for the slot. The MDA can be pre-provisioned and an MDA must be provisioned before connectors or ports can be configured. A maximum of two MDAs can be provisioned on an IOM or XCM. XMAs are provisioned using MDA commands. 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 either the correct MDA type is inserted or the configuration is modified. A low severity alarm is issued if an MDA is removed that is administratively disabled. An MDA can only be provisioned in a slot if the MDA type is allowed in the MDA slot. An error message is generated when an MDA is provisioned in a slot where it is not allowed. Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode. These are identified as two MDA types that are the same, except for a “-ptp” suffix to indicate the second loadset. A hard reset of the MDA occurs when switching between the two provisioned types. An alarm is raised if partial or complete MDA failure is detected. The alarm is cleared when the error condition ceases. New generations of XMAs include variants controlled through hardware and software licensing. For these XMAs, the license level must be provisioned in addition to the MDA type. An XMA cannot become operational unless the provisioned license level matches the license level of the XMA installed into the slot. The set of license levels varies by MDA type. The provisioned level controls aspects related to connector provisioning and the consumption of hardware egress queues and egress policers. Changes to the provisioned license level may be blocked if configuration that would not be permitted with the new target license level exists. If the license level is not specified, the level is set to the highest license level for that XMA. | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms | All | |
network
egress
ingress
power-priority-level number
| Synopsis | Power priority level for the MDA | |
| Context | configure card number mda number power-priority-level number | |
| Tree | power-priority-level | |
| Range | 1 to 200 | |
| Default | 150 | |
| Introduced | 16.0.R1 | |
Platforms |
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS |
reset-on-recoverable-error boolean
| Synopsis | Reset MDA for fatal memory parity error on a Q-chip | |
| Context | configure card number mda number reset-on-recoverable-error boolean | |
| Tree | reset-on-recoverable-error | |
Description | When configured to true, the MDA resets when a fatal memory parity error is detected on a Q-chip of the MDA, regardless of the setting of the fail-on-error configuration for the MDA. When configured to false, the recovery action is taken instead of resetting the MDA. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS |
sync-e keyword
| Synopsis | Synchronous Ethernet capability | |
| Context | configure card number mda number sync-e keyword | |
| Tree | sync-e | |
Description | This command enables synchronous Ethernet on the MDA. When enabled, any port on the MDA can be used as a source port in the central frequency clock configuration, under the configure system central-frequency-clock context. | |
| Options | ||
| Introduced | 16.0.R1 | |
Platforms |
All |
upgrade [upgrade-index] number
| Synopsis | Enter the upgrade list instance | |
| Context | configure card number mda number upgrade number | |
| Tree | upgrade | |
Description | Commands in this context configure the license level upgrade for the MDA. You can apply multiple upgrades to an MDA. The first upgrade must use index 1, then index 2, and so on. When removing upgrades, remove the largest index first, followed by the next largest, and so on. Some upgrades require a hard reset of the MDA to take effect. In general, this is required when the full duplex bandwidth changes as a result of the upgrade. | |
| Introduced | 16.0.R4 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS |
[upgrade-index] number
path keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Upgrade path of the MDA for the slot | |
| Context | configure card number mda number upgrade number path keyword | |
| Tree | path | |
Description | This command configures the upgrade path for the MDA in the slot. The path indicates the starting level and the new level that is applied due to the upgrade. | |
| Options | ||
Notes | This element is mandatory. | |
| Introduced | 16.0.R4 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS | |
xconnect
mac [mac-id] number
[mac-id] number
description string
| Synopsis | Text description | |
| Context | configure card number mda number xconnect mac number description string | |
| Tree | description | |
| String Length | 0 to 255 | |
| Introduced | 21.5.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS |
loopback [loopback-id] number
| Synopsis | Enter the loopback list instance | |
| Context | configure card number mda number xconnect mac number loopback number | |
| Tree | loopback | |
Description | Commands in this context configure the attributes of the loopback on a MAC chip. The system and services can start using the loopback only when a port is associated with it (for example, port 1/1/m1/1, where m1 represents the MAC ID). | |
| Introduced | 21.5.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS |
[loopback-id] number
bandwidth number
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Maximum bandwidth for a Layer 2 rate for MAC loopback | |
| Context | configure card number mda number xconnect mac number loopback number bandwidth number | |
| Tree | bandwidth | |
| Range | 10 | 25 | 40 | 100 | 400 | 800 | |
| Units | gigabps | |
| Default | 100 | |
| Introduced | 21.5.R1 | |
Platforms |
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS | |
description string
| Synopsis | Text description | |
| Context | configure card number mda number xconnect mac number loopback number description string | |
| Tree | description | |
| String Length | 0 to 255 | |
| Introduced | 21.5.R1 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS |
power-save boolean
| Synopsis | Place card in power-save mode when not in use | |
| Context | configure card number power-save boolean | |
| Tree | power-save | |
Description | When configured to true, this command enables the power-save mode on the card when it is not in use. The power-save mode allows the card to be installed and configured in a platform for future use, while having minimal impact on the overall power consumption. A card placed in the power-save mode is reset, forced into an idle state, and consumes minimal power. In power save mode, the download of a software image to the card is not allowed. The card must be administratively disabled before it is placed in the power-save mode. Cards in the power save mode do not count in the intelligent power management budget and they also do not pass traffic. When configured to false, this command removes the card from power-save mode. | |
| Default | false | |
| Introduced | 19.5.R1 | |
|
Platforms | 7450 ESS, 7750 SR-7/12/12e, 7750 SR-a8, 7750 SR-2e, 7750 SR-3e, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS |
reset-on-recoverable-error boolean
| Synopsis | Reset card for fatal memory parity error on a Q-chip | |
| Context | configure card number reset-on-recoverable-error boolean | |
| Tree | reset-on-recoverable-error | |
Description | When configured to true, the card is reset when a fatal memory parity error is detected on a Q-chip of the card, regardless of the setting of the fail-on-error configuration for the card. When configured to false, the recovery action is taken instead of resetting the card. | |
| Default | false | |
| Introduced | 16.0.R1 | |
|
Platforms | 7450 ESS, 7750 SR-7/12/12e |
upgrade [upgrade-index] number
| Synopsis | Enter the upgrade list instance | |
| Context | configure card number upgrade number | |
| Tree | upgrade | |
Description | Commands in this context assign a license level upgrade to the card, XIOM, or XMA. There can be multiple upgrades applied to a card, XIOM, or XMA. The first upgrade must use index 1, and then next index 2, and so on. Also, when removing upgrades, the largest index must be removed first, and then the next largest removed, and so on. The path indicates the starting level and the new level that will apply due to the upgrade. For example, "cr1200g-cr1600g" can be applied to an XMA that is currently at the cr1200g level and after application of the upgrade, the operational level of the XMA will be cr1600g. There must be an upgrade license available for the path specified. Available upgrades can be checked using the show licensing entitlements command. Some upgrades require a hard reset of the card or MDA to take effect. In general, this is required when the Full Duplex bandwidth is being changed. | |
| Introduced | 16.0.R4 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-1se |
[upgrade-index] number
path keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Upgrade path of the target module for the slot | |
| Context | configure card number upgrade number path keyword | |
| Tree | path | |
Description | This command configures the upgrade path associated with the upgrade instance for the target module in the slot. The path indicates the starting level and the new level that applies during the upgrade. | |
| Options | ||
Notes | This element is mandatory. | |
| Introduced | 16.0.R4 | |
Platforms | 7450 ESS, 7750 SR, 7750 SR-1se | |
virtual-scheduler-adjustment
| Synopsis | Enter the virtual-scheduler-adjustment context | |
| Context | configure card number virtual-scheduler-adjustment | |
| Tree | virtual-scheduler-adjustment | |
Description | Commands in this context configure virtual scheduler options. This is applicable to queues and policiers associated to a scheduler. | |
| Introduced | 16.0.R1 | |
Platforms | All |
internal-scheduler-weight-mode keyword
| Synopsis | Internal scheduler weight mode | |
| Context | configure card number virtual-scheduler-adjustment internal-scheduler-weight-mode keyword | |
| Tree | internal-scheduler-weight-mode | |
Description | This command specifies the internal scheduler (tier 0) weight mode for all ingress queues on a LAG on the card on which it is applied. | |
| Options | ||
| Default | auto | |
| Introduced | 16.0.R1 | |
Platforms |
All |
interval
| Synopsis | Enter the interval context | |
| Context | configure card number virtual-scheduler-adjustment interval | |
| Tree | interval | |
| Introduced | 16.0.R1 | |
Platforms | All |
rate-calculation-minimum
| Synopsis | Enter the rate-calculation-minimum context | |
| Context | configure card number virtual-scheduler-adjustment interval rate-calculation-minimum | |
| Tree | rate-calculation-minimum | |
Description | Commands in this context override the default minimum time that must elapse before a policer or queue’s offered rate can be recalculated. A minimum time between offered rate calculations is enforced to both prevent inaccurate estimation of the offered rate and excessive input to the virtual scheduler process. To smooth out rapidly fluctuating offered rates, the system averages the measured offered rate with a window of previously measured offered traffic statistics and knowledge of the time between the samples. | |
| Introduced | 16.0.R1 | |
Platforms | All |
fast-queue decimal-number
| Synopsis | Minimum rate calculation time for fast queues | |
| Context | configure card number virtual-scheduler-adjustment interval rate-calculation-minimum fast-queue decimal-number | |
| Tree | fast-queue | |
| Range | 0.01 to 1000.00 | |
| Units | percent | |
| Default | 100.00 | |
| Introduced | 16.0.R1 | |
Platforms | All |
slow-queue decimal-number
| Synopsis | Minimum rate calculation time for slow queues | |
| Context | configure card number virtual-scheduler-adjustment interval rate-calculation-minimum slow-queue decimal-number | |
| Tree | slow-queue | |
| Range | 0.01 to 1000.00 | |
| Units | percent | |
| Default | 100.00 | |
| Introduced | 16.0.R1 | |
Platforms | All |
scheduler-run-minimum decimal-number
| Synopsis | Minimum time of the scheduler run | |
| Context | configure card number virtual-scheduler-adjustment interval scheduler-run-minimum decimal-number | |
| Tree | scheduler-run-minimum | |
Description | This command overrides the default minimum time that must elapse before a virtual scheduler can redistribute bandwidth based on changes to the offered rates of member policers or queues. A minimum run interval is enforced to manage the number of batched queue changes before reacting to the changed rates. Because the periodic function of determining policer or queue offered rates is performed sequentially, the interval allows the policer and queue rates to be determined before the bandwidth distribution to the policers and queues. | |
| Range | 0.01 to 1000.00 | |
| Units | percent | |
| Default | 100.00 | |
| Introduced | 16.0.R1 | |
Platforms | All |
task-scheduling decimal-number
| Synopsis | Task scheduling interval | |
| Context | configure card number virtual-scheduler-adjustment interval task-scheduling decimal-number | |
| Tree | task-scheduling | |
Description | This command overrides the system default time interval for scheduling the hierarchical virtual scheduler task. By default, the system wakes the virtual scheduler task every 50 ms which is equivalent to five 10 ms timer ticks. | |
| Range | 0.01 to 1000.00 | |
| Units | percent | |
| Default | 100.00 | |
| Introduced | 16.0.R1 | |
Platforms | All |
slow-queue-threshold-rate number
| Synopsis | Slow queue threshold rate | |
| Context | configure card number virtual-scheduler-adjustment slow-queue-threshold-rate number | |
| Tree | slow-queue-threshold-rate | |
Description | This command overrides the system default threshold rate used to place policers and queues in the slow queue category. Slow rate policers and queues use a different minimum rate calculation interval time than fast rate queues. The fast rate threshold is derived by multiplying the adjusted slow rate threshold by a factor of 1.5. Configuring a value of zero (0) forces all policers and queues to be treated as fast rate queues. | |
| Range | 0 to 1000000 | |
| Units | kilobps | |
| Default | 1000 | |
| Introduced | 16.0.R1 | |
Platforms | All |
xiom [xiom-slot] string
[xiom-slot] string
admin-state keyword
| Synopsis | Administrative state of the XIOM | |
| Context | configure card number xiom string admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | enable | |
| Introduced | 20.2.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
fail-on-error boolean
| Synopsis | Set operational state of the card to failed on error | |
| Context | configure card number xiom string fail-on-error boolean | |
| Tree | fail-on-error | |
Description | When configured to true, the operational state of the card is set to failed when at least one of a specific set of card-level errors is detected. The failed state persists until the operator reseats the card or resets it using the clear command. | |
| Default | false | |
| Introduced | 20.2.R1 | |
|
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
level keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | License level of the XIOM | |
| Context | configure card number xiom string level keyword | |
| Tree | level | |
Description | This command provisions the license level of the XIOM, which controls aspects related to connector provisioning and consumption of hardware egress queues and policers. An XIOM only becomes operational if the provisioned license level matches the license level of the card installed into the slot. The set of license levels varies by XIOM type. Changes to the provisioned license level may be blocked if a configuration exists that is not permitted with the new target license level. If the license level is not specified, the level is set to the highest license level for the XIOM. | |
| Options | ||
| Introduced | 20.2.R1 | |
Platforms |
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s | |
mda [mda-slot] number
[mda-slot] number
admin-state keyword
| Synopsis | Administrative state of the MDA | |
| Context | configure card number xiom string mda number admin-state keyword | |
| Tree | admin-state | |
| Options | ||
| Default | enable | |
| Introduced | 20.2.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
mda-type keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | MDA-s type provisioned for the XIOM slot | |
| Context | configure card number xiom string mda number mda-type keyword | |
| Tree | mda-type | |
Description | This command provisions the MDA-s type for the XIOM slot. The MDA-s type can be preprovisioned, which means that the MDA-s does not have to be installed in the chassis. You can preprovision the MDA type before you install the MDA in the chassis. An MDA-s can only be provisioned in a slot that is vacant. No other MDA-s can be provisioned (configured) for that particular slot. An error message or log event is generated if the wrong MDA type is provisioned or inserted. | |
| Options | ||
| Introduced | 20.2.R1 | |
|
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s | |
power-priority-level number
| Synopsis | Power priority level for the XIOM MDA-s | |
| Context | configure card number xiom string mda number power-priority-level number | |
| Tree | power-priority-level | |
Description | This command configures the power-priority level for the XIOM MDA-s. Consider the following suggestions when configuring the power-priority level:
| |
| Range | 1 to 200 | |
| Default | 150 | |
| Introduced | 20.2.R1 | |
Platforms |
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
sync-e keyword
xconnect
mac [mac-id] number
[mac-id] number
description string
| Synopsis | Text description | |
| Context | configure card number xiom string mda number xconnect mac number description string | |
| Tree | description | |
| String Length | 0 to 255 | |
| Introduced | 21.5.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
loopback [loopback-id] number
| Synopsis | Enter the loopback list instance | |
| Context | configure card number xiom string mda number xconnect mac number loopback number | |
| Tree | loopback | |
Description | Commands in this context configure a MAC loopback on a MAC chip. The system and services only start using the loopback when a port is associated with it. For example, port 1/1/m1/1, where m1 represents the MAC ID. | |
| Introduced | 21.5.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
[loopback-id] number
bandwidth number
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Maximum bandwidth for a Layer 2 rate for MAC loopback | |
| Context | configure card number xiom string mda number xconnect mac number loopback number bandwidth number | |
| Tree | bandwidth | |
| Range | 10 | 25 | 40 | 100 | 400 | 800 | |
| Units | gigabps | |
| Default | 100 | |
| Introduced | 21.5.R1 | |
Platforms |
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s | |
description string
| Synopsis | Text description | |
| Context | configure card number xiom string mda number xconnect mac number loopback number description string | |
| Tree | description | |
| String Length | 0 to 255 | |
| Introduced | 21.5.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
reset-on-recoverable-error boolean
| Synopsis | Reset XIOM for fatal memory parity error on a Q-chip | |
| Context | configure card number xiom string reset-on-recoverable-error boolean | |
| Tree | reset-on-recoverable-error | |
Description | When configured to true, the XIOM is reset when a fatal memory parity error is detected on a Q-chip of the XIOM, regardless of the setting of the fail-on-error configuration for the XIOM. When configured to false, the recovery action is taken instead of resetting the XIOM. | |
| Default | false | |
| Introduced | 20.2.R1 | |
|
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
upgrade [upgrade-index] number
| Synopsis | Enter the upgrade list instance | |
| Context | configure card number xiom string upgrade number | |
| Tree | upgrade | |
Description | Commands in this context assign a license level upgrade to the XIOM. Multiple upgrades can be applied to an XIOM. The first upgrade must use index 1, then index 2, and so on. When removing upgrades, the largest index must be removed first, followed by the next largest, and so on. Some upgrades require a hard reset of the XIOM to take effect. In general, this is required when the Full Duplex bandwidth is changed as a result of the upgrade. | |
| Introduced | 20.2.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s |
[upgrade-index] number
path keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | Upgrade name | |
| Context | configure card number xiom string upgrade number path keyword | |
| Tree | path | |
Description | This command specifies the upgrade name. An upgrade license must be available for the specified path. Available upgrades can be checked using the show licensing entitlements command. | |
| Options | ||
Notes | This element is mandatory. | |
| Introduced | 20.2.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s | |
xiom-type keyword
|
WARNING: Modifying this element recreates the parent element automatically for the new value to take effect. | ||
| Synopsis | XIOM type | |
| Context | configure card number xiom string xiom-type keyword | |
| Tree | xiom-type | |
Description | This command associates the XIOM type with the slot. The XIOM type can be preprovisioned, which means that the XIOM does not have to be installed in the chassis. An XIOM must be provisioned before an MDA-s, a connector, or a port can be configured. An XIOM can only be provisioned in a slot that is vacant. After an XIOM is provisioned in the slot, no other XIOM can be provisioned (configured) for the slot. An XIOM can only be provisioned in a slot if the XIOM type is allowed in the slot. An error message is generated if an attempt is made to provision an XIOM type that is not allowed. If an XIOM is inserted that does not match the configured XIOM type for the slot, then a log event and a facility alarm are raised. The alarm is cleared when the correct XIOM type is installed or the configuration is modified. A log event and a facility alarm are raised if an administratively enabled XIOM is removed from the chassis. The alarm is cleared when the correct XIOM type is installed or the configuration is modified. A log event is issued when an XIOM is removed that is administratively disabled. XIOMs are controlled by hardware and software licensing. In addition to the XIOM type, the license level must be provisioned using the level command. | |
| Options | ||
| Introduced | 20.2.R1 | |
Platforms | 7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s | |