card commands

configure 
   —  card number 
      —  admin-state keyword
      —  apply-groups reference
      —  apply-groups-exclude reference
      —  card-type keyword
      —  fail-on-error boolean
      —  fp number 
         —  apply-groups reference
         —  apply-groups-exclude reference
         —  egress 
         —  ingress 
            —  access 
               —  queue-group reference instance-id number 
                  —  accounting-policy reference
                  —  apply-groups reference
                  —  apply-groups-exclude reference
                  —  collect-stats boolean
                  —  description description
                  —  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
            —  network 
               —  pool named-item 
                  —  apply-groups reference
                  —  apply-groups-exclude reference
               —  queue-group reference instance-id number 
                  —  accounting-policy reference
                  —  apply-groups reference
                  —  apply-groups-exclude reference
                  —  collect-stats boolean
                  —  description description
                  —  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
         —  init-extract-prio-mode 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
         —  event keyword 
            —  action keyword
            —  apply-groups reference
            —  apply-groups-exclude reference
         —  fail-on-error boolean
         —  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
         —  sync-e keyword

card command descriptions

card [slot-number] number


	Synopsis	Enter the card list instance
	Context	configure card number
	Tree	card
	Description	Commands in this context cover attributes for specific chassis slots for physical cards. In SR OS, cards cover IOM, IMM, and XCM.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

[slot-number] number


	Synopsis	Slot number within the chassis
	Context	configure card number
	Tree	card
	Description	This command configures a unique value that identifies the card slot within a chassis in the system.
	Range	1 to 20
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

admin-state keyword


	Synopsis	Administrative state of the card
	Context	configure card number admin-state keyword
	Tree	admin-state
	Options	enable, disable
	Default	enable
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	xcm-x20, imm40-10gb-sfp, iom4-e, iom-a, imm-2pac-fp3, iom4-e-hs, imm4-100gb-cfp4, iom-e, iom-v, iom4-e-b, iom-sar-hm, xcm2-x20, iom-1, xcm-14s, imm40-10gb-sfp-ptp, iom-ixr-r6, imm36-100g-qsfp28, imm48-sfp+2-qsfp28, iom5-e, xcm-7s, imm48-sfp++6-qsfp28, xcm-1s, xcm-2s, imm24-sfp++8-sfp28+2-qsfp28, iom-sar-hmc, imm14-10g-sfp++4-1g-tx, iom-ixr-r4, imm6-qsfpdd+48-sfp56, imm32-qsfp28+4-qsfpdd, i48-800g-qsfpdd-1x, imm36-qsfpdd, imm4-1g-tx+20-1g-sfp+6-10g-sfp+, iom-ixr-r6d, xcm2-7s, i24-800g-qsfpdd-1, imm36-800g-qsfpdd, xcm2-14s, i48-400g-qsfpdd-1, i80-200g-sfpdd+12-400g-qsfpdd-1, i40-200g-sfpdd+6-800g-qsfpdd-1, i80-200g-sfpdd+12-800g-qsfpdd-1x, xcm-2se, xcm-14s-b, xcm-7s-b, imm2-qsfpdd+2-qsfp28+24-sfp28, xcmc-2se, imm12-sfp28+2-qsfp28, dms24-800g-qsfpdd-1, iom-sar
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

fp [fp-number] number


	Synopsis	Enter the fp list instance
	Context	configure card number fp number
	Tree	fp
	Description	Commands in this context configure forwarding plane (FP) specific options on the card.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

[fp-number] number


	Synopsis	Forwarding plane within the card
	Context	configure card number fp number
	Tree	fp
	Range	1 to 12
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

egress


	Synopsis	Enter the egress context
	Context	configure card number fp number egress
	Tree	egress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

ingress


	Synopsis	Enter the ingress context
	Context	configure card number fp number ingress
	Tree	ingress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

access


	Synopsis	Enter the access context
	Context	configure card number fp number ingress access
	Tree	access
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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 named-item
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

description description


	Synopsis	Text description
	Context	configure card number fp number ingress access queue-group reference instance-id number description description
	Tree	description
	String length	1 to 80
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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 named-item
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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 named-item policer number
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	no-stats, minimal, offered-profile-no-cir, offered-total-cir, offered-priority-no-cir, offered-profile-cir, offered-priority-cir, offered-limited-profile-cir, offered-profile-capped-cir, offered-limited-capped-cir
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

network


	Synopsis	Enter the network context
	Context	configure card number fp number ingress network
	Tree	network
	Description	Commands in this context configure the IOM ingress network forwarding plane settings.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

pool [name] named-item


	Synopsis	Enter the pool list instance
	Context	configure card number fp number ingress network pool named-item
	Tree	pool
	Description	Commands in this context configure the list of forwarding plane ingress network pool settings.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

[name] named-item


	Synopsis	Network ingress pool name for the FP
	Context	configure card number fp number ingress network pool named-item
	Tree	pool
	String length	1 to 32
	MD-CLI default	default
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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 named-item
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

description description


	Synopsis	Text description
	Context	configure card number fp number ingress network queue-group reference instance-id number description description
	Tree	description
	String length	1 to 80
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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 named-item
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

[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 named-item policer number
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	auto
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	max
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	no-stats, minimal, offered-profile-no-cir, offered-total-cir, offered-priority-no-cir, offered-profile-cir, offered-priority-cir, offered-limited-profile-cir, offered-profile-capped-cir, offered-limited-capped-cir
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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 named-item
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	uniform, l3-classify
	Default	uniform
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

mda [mda-slot] number


	Synopsis	Enter the mda list instance
	Context	configure card number mda number
	Tree	mda
	Description	Commands in this context cover attributes for specific MDA and XMA.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

[mda-slot] number


	Synopsis	MDA or XMA slot
	Context	configure card number mda number
	Tree	mda
	Range	1 to 6
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

access


	Synopsis	Enter the access context
	Context	configure card number mda number access
	Tree	access
	Description	Commands in this context configure egress and ingress pool policy parameters. Access egress and ingress pools are only allocated on channelized MDAs.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

egress


	Synopsis	Enter the egress context
	Context	configure card number mda number access egress
	Tree	egress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

ingress


	Synopsis	Enter the ingress context
	Context	configure card number mda number access ingress
	Tree	ingress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

admin-state keyword


	Synopsis	Administrative state of the MDA
	Context	configure card number mda number admin-state keyword
	Tree	admin-state
	Options	enable, disable
	Default	enable
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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. The log event raised for any event type (such as soft-error or memory-error) is tmnxEqHwEventDetected.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

[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. soft-error — Defines the action to take when soft errors are detected on the MDA. internal-frame-loss — Provides system detected frame loss in the traffic transiting the MDA. memory-error — Provides the user options to handle MDA memory error events on MDAs. This feature is supported on FP2- and FP3-based Ethernet MDAs and IMMs. data-link-error — Provides the user options to handle datapath link errors on an MDA.
	Options	soft-error, internal-frame-loss, memory-error, datapath-link-error
	Notes	This element is part of a list key.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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: log-only — Pass the log event to log management. No other action is taken. reset-mda — Reset the MDA. fail-mda — Set the operational state of the MDA to Failed. This Failed state persists until the clear mda command is issued (reset) or the MDA is removed and reinserted (re-seated).
	Options	none, log-only, reset, fail
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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.
	Default	false
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	x12-400g-qsfpdd, x6-200g-cfp2-dco, p10-10g-sfp, p1-100g-cfp, p6-10g-sfp, x40-10g-sfp, m40-10g-sfp, p20-1gb-sfp, s36-100gb-qsfp28-3.6t, p-isa2-ms, p-isa2-ms-e, isa2-aa, isa2-tunnel, isa2-bb, x4-100g-cfp2, maxp1-100gb-cfp, ma4-10gb-sfp+, maxp10-10gb-sfp+, me10-10gb-sfp+, ma2-10gb-sfp+12-1gb-sfp, ma44-1gb-csfp, ma20-1gb-tx, m20-10g-sfp+, me1-100gb-cfp2, m4-100g-cfp4, maxp1-100gb-cfp2, maxp1-100gb-cfp4, isa-ms-v, isa-aa-v, isa-tunnel-v, isa-bb-v, m20-v, me-isa2-ms, me-isa2-ms-e, me40-1gb-csfp, m4-1g-tx+20-1g-sfp+6-10g-sfp+, me6-10gb-sfp+, isa2-video, me2-100gb-qsfp28, i6-10/100eth-tx, i2-sdi, i2-cellular, me12-10/1gb-sfp+, me16-25gb-sfp28+2-100gb-qsfp28, me6-100gb-qsfp28, x6-400g-cfp8, me2-100gb-ms-qsfp28, s18-100gb-qsfp28, x40-10g-sfp-ptp, m40-10g-sfp-ptp, m36-100g-qsfp28, m48-sfp+2-qsfp28, m10-10g-sfp+, m20-1g-csfp, m6-10g-sfp++1-100g-qsfp28, me3-200gb-cfp2-dco, x24-100g-qsfp28, me12-100gb-qsfp28, i1-wlan, s36-400gb-qsfpdd, m24-sfp++8-sfp28+2-qsfp28, s36-100gb-qsfp28, a32-chds1v2, m48-sfp++6-qsfp28, maxp10-10/1gb-msec-sfp+, m4-10g-sfp++1-100g-cfp2, i3-10/100eth-tx, me3-400gb-qsfpdd, m18-25g-sfp28, m14-10g-sfp++4-1g-tx, m6-10g-sfp++4-25g-sfp28, me6-400gb-qsfpdd, me8-10/25gb-sfp28, m10-1g-sfp+2-10g-sfp+, m6-qsfpdd+48-sfp56, m32-qsfp28+4-qsfpdd, m36-qsfpdd, m1-400g-qsfpdd+1-100g-qsfp28, m5-100g-qsfp28, m48-800g-qsfpdd-1x, m24-800g-qsfpdd-1, ms36-800g-qsfpdd, x2-s36-800g-qsfpdd-18.0t, m48-400g-qsfpdd-1, m80-200g-sfpdd+12-800g-qsfpdd-1x, m40-200g-sfpdd+6-800g-qsfpdd-1, m80-200g-sfpdd+12-400g-qsfpdd-1, m46-10g-sfp+, m2-cfp2, m2-qsfpdd+2-qsfp28+24-sfp28, x2-s36-800g-qsfpdd-12.0t, me16-25gb-sfp28+2-100gb-qsfp-b, m10-50g-sfp56, m32-1g-csfp, m80-1g-csfp, m12-sfp28+2-qsfp28, m2-100g-qsfp28+16-10g-sfp+, d24-800g-qsfpdd-1, m10-sfp++6-sfp
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

network


	Synopsis	Enter the network context
	Context	configure card number mda number network
	Tree	network
	Description	Commands in this context configure egress and ingress pool policy parameters for the network. Network egress pools are only allocated on channelized MDAs.
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

egress


	Synopsis	Enter the egress context
	Context	configure card number mda number network egress
	Tree	egress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

ingress


	Synopsis	Enter the ingress context
	Context	configure card number mda number network ingress
	Tree	ingress
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2

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	true, false
	Introduced	25.3.R2
	Platforms	7705 SAR Gen 2