This command enables and disables the ability of the router to ignore D-PATH domain segment length during best-path selection. At the base router level (or vprn>bgp level for PE-CE routers), this command allows BGP to ignore the D-PATH domain segment length for best-path selection purposes. The D-PATH length is ignored when comparing two VPN routes or two IFL routes within the same RD. However, these VPN/IFL routes are processed in Main-BGP instance.

At the VPRN router level, this command allows the VPRN RTM to ignore the D-PATH domain segment length for best path selection purposes (for routes in VPRN). The user can control whether the D-PATH length is considered when two VPN routes with different RDs are compared.

Best-path selection for EVPN-IFF routes against other owners (for example, EVPN-IFL or IPVPN) still relies on RTM preference. When EVPN-IFF RTM preference matches the RTM preference of another BGP owner, the existing RTM selection applies and D-PATH is not considered, irrespective of the d-path-length-ignore configuration.

The no form of this command disables the ability to ignore the D-PATH domain segment length.

This command configures a delayed ACK (DACK) timeout for the TCP optimizer. By entering this command a default of 200 ms timeout is enabled for delayed acknowledgment. This value is not configurable.

The no form of this command disables the delayed acknowledgment timeout.

This command disables duplicate address detection (DAD) on a per-interface basis. This prevents the router from performing a DAD check on the interface. All IPv6 addresses of an interface with DAD disabled, immediately enter a preferred state, without checking for uniqueness on the interface. This is useful for interfaces which enter a looped state during troubleshooting and operationally disable themselves when the loop is detected, requiring manual intervention to clear the DAD violation.

The no form of this command turns off dad-disable on the interface.

This command allows the router to populate the neighbor discovery table through snooping subscribers’ duplicate address detection messages.

The no form of this command reverts to the default.

This command controls how long a BGP peer session remains in the idle-state after some type of error causes the session to reset. In the idle state, BGP does not initiate or respond to attempts to establish a new session. Repeated errors that occur a short while after each session reset cause longer and longer hold times in the idle state. This command supports the DampPeerOscillations FSM behavior described in section 8.1 of RFC 4271, A Border Gateway Protocol 4 (BGP-4).

The default behavior, which applies when no damp-peer-oscillations is configured, is to immediately transition out of the idle-state after every reset.

This command controls how long a BGP peer session remains in the idle-state after some type of error causes the session to reset. In the idle state, BGP does not initiate or respond to attempts to establish a new session. Repeated errors that occur a short while after each session reset cause longer and longer hold times in the idle state. This command supports the DampPeerOscillations FSM behavior described in section 8.1 of RFC 4271, A Border Gateway Protocol 4 (BGP-4).

The default behavior, which applies when no damp-peer-oscillations is configured, is to immediately transition out of the idle-state after every reset.

Commands in this context configure exponential port dampening for an Ethernet port.

Exponential Port Dampening (EPD) reduces the number of physical link transitions reported to upper layer protocols, potentially reducing upper layer protocol churn caused by a faulty link. Penalties are added against a port whenever the port’s physical link state transitions from a link up state to a link down state. When the penalties exceed a configurable threshold, port-up and port-down transitions are no longer advertised to upper layers and the port’s operational state will remain down until the penalty amount drops below a configurable reuse threshold. Each transition of link up state to link down state increments the accumulated penalty value by 1000. The accumulated penalties for a port are reduced at an exponential decay rate according to a configurable half-life parameter.

This command enables BGP route damping for learned routes which are defined within the route policy. Use damping to reduce the number of update messages sent between BGP peers and reduce the load on peers without affecting the route convergence time for stable routes. Damping parameters are set via route the policy definition.

The no form of this command used at the global level disables route damping.

When damping is enabled and the route policy does not specify a damping profile, the default damping profile is used. This profile is always present and consists of the following parameters:

This command enables BGP route damping for learned routes which are defined within the route policy. Use damping to reduce the number of update messages sent between BGP peers and reduce the load on peers without affecting the route convergence time for stable routes. Damping parameters are set via route policy definition.

The no form of this command used at the global level disables route damping.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

When damping is enabled and the route policy does not specify a damping profile, the default damping profile is used. This profile is always present and consists of the following parameters:

Half-life: 15 minutes

Max-suppress: 60 minutes

Suppress-threshold: 3000

Reuse-threshold: 750

This command enables BGP route damping for learned routes which are defined within the route policy. Use damping to reduce the number of update messages sent between BGP peers and reduce the load on peers without affecting the route convergence time for stable routes. Damping parameters are set via route policy definition.

The no form of this command used at the global level reverts route damping.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

When damping is enabled and the route policy does not specify a damping profile, the default damping profile is used. This profile is always present and consists of the following parameters:

This command creates a context to configure a route damping profile to use in route policy entries.

The no form of this command deletes the named route damping profile.

This command configures a damping profile used for routes matching the route policy statement entry.

If no damping criteria is specified, the default damping profile is used.

The no form of this command removes the damping profile associated with the route policy entry.

This command enables debugging for PIM data exception.

The no form of this command disables PIM data exception debugging.

This command creates a data bearer assigned to a TE Link. Only one data bearer may be configured within a given TE Link.

This command configures the I-PMSI data delay timer.

This delay timer is intended to allow time for the RSVP control plane to signal and bring up the S2L sub-LSP to each destination PE participating in the VPLS/B-VPLS service. The delay timer is started as soon as the P2MP LSP instance becomes operationally up after the user performed a ‘no shutdown’ under the inclusive node, i.e., as soon as the first S2L sub-LSP is up. In general, it is started when the P2MP LSP instance transitions from the operationally down state to the up state.

For a mLDP P2MP LSP, the delay timer is started as soon as the P2MP FEC corresponding to the I-PMSI is resolved and installed at the root node. The user must factor in the value configured in the data-delay-interval at the root node any delay configured in IGP-LDP sync timer (config>router>if>ldp-sync-timer) on interfaces over the network. This is because the mLDP P2MP LSP may move to a different interface at the expiry of this timer since the routing upstream of the LDP Label Mapping message may change when this timer expires and the interface metric is restored.

At the expiry of this timer, the VPLS/B-VPLS will begin forwarding of BUM packets over the P2MP LSP instance even if not all the S2L paths are up.

The no version of this command re-instates the default value for this delay timer.

This command specifies the interval, in seconds, before a PE router connected to the source switches traffic from the inclusive provider tunnel to the selective provider tunnel.

This command is not applicable to multi-stream S-PMSI.

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

This command specifies the interval, in seconds, before a PBR connected to the source switches traffic from the inclusive provider tunnel to the selective provider tunnel.

This command is not applicable to multi-stream S-PMSIs.

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

This command configures a rendezvous point (RP) using Multicast Source Discovery Protocol (MSDP) to encapsulate multicast data received in MSDP register messages inside forwarded MSDP source-active messages.

This command configures a rendezvous point (RP) using Multicast Source Discovery Protocol (MSDP) to encapsulate multicast data received in MSDP register messages inside forwarded MSDP source-active messages.

This command specifies the data rate threshold that triggers the switch from the inclusive provider tunnel to the selective provider tunnel for (C-S, C-G) within the group range. Optionally, PE thresholds for creating/deleting ng-MVPN S-PMSI may also be specified. Omitting the PE thresholds, preserves the currently set value (or defaults if never set). Multiple statements (one per a unique group) are allowed in the configuration.

This command is not applicable to multi-stream S-PMSI.

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

This command specifies the data rate threshold that triggers the switch from the inclusive provider tunnel to the selective provider tunnel for (C-S, C-G) within the group range. Optionally, PBR thresholds for creating or deleting NG-MVPN S-PMSI may also be specified. Omitting the PBR thresholds preserves currently set values (or defaults if never set). Multiple statements (one per a unique group) are allowed in the configuration.

This command is not applicable to multi-stream S-PMSIs.

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

This command allows the operator to add an optional Data TLV to PDU and increase the frame on the wire by the specified amount. Note that this command only configures the size of the padding added to the PDU, and does not configure the total size of the frame on the wire.

The no form of this command removes the optional TLV.

Commands in this context configure data-triggered subscriber management entities.

This command enables learning of MAC addresses from data packets.

The no form of this command disables learning of MAC addresses from data packets.

This command enables matching on UEs currently in a data-triggered state. This query only filters UEs that are currently authenticating due to a data trigger, not UEs that were originally authenticated due to data trigger, such as those in an ESM, DSM, or portal state.

The no form of this command disables matching on UEs in a data-triggered state, unless all state matching is disabled.

This command enables data-triggered subscriber creation for WIFI subscribers. Data- triggered UE creation is currently only supported for UDP and TCP packets.

The no form of this command disables the data-triggered subscriber creation for WIFI subscribers.

Commands in this context configure dynamic services data trigger capture SAP debugging. The no form of this command removes all dynamic services data trigger capture SAP debug configurations.

This command enables or disables debugging for the PIM database.

This command enables the population of the extended TE Database (TE-DB) with the link-state information from a given IGP instance.

The extended TE-DB is used as a central point for importing all link-state information, link, node, and prefix, from IGP instances on the router or the vSROS controller of the NSP and to exporting it to BGP-LS on the router and to Java-VM proxy on the vSROS controller. This information includes the IGP, TE, and the SR information, prefix SID sub-TLV, adjacency SID sub-TLV, and router SR capability TLV.

The no form of this command disables database exportation.

This command enables the population of the extended TE Database (TE-DB) with the link-state information from a given IGP instance.

The extended TE-DB is used as a central point for importing all link-state information, link, node, and prefix, from IGP instances on the router or the vSROS controller of the NSP and to exporting it to BGP-LS on the router and to Java-VM proxy on the vSROS controller. This information includes the IGP, TE, and the SR information, prefix SID sub-TLV, adjacency SID sub-TLV, and router SR capability TLV.

The no form of this command disables database exportation.

This command allows the user to prune the IGP link-state information of a specific IS-IS level from being exported into the extended TE-DB.

The no form of this command returns to the default behavior inherited from the database-export command at the IS-IS instance level.

This command allows the user to prune the IGP link-state information of a specific OSPF level or OSPF area from being exported into the extended TE-DB. The no form of this command returns to the default behavior inherited from the database-export command at the IS-IS or OSPF instance level.

This command configures the system-wide high watermark threshold as a percentage of the per-ISA datapath core CPU utilization, where an alarm will be raised by the agent. CPU usage is the average usage across all datapath cores.

This command configures the system-wide low watermark threshold as a percentage of the per-ISA datapath core CPU utilization, where an alarm will be raised by the agent. CPU usage is the average usage across all datapath cores.

This command specifies which days of the month that the schedule will occur. Multiple days of the month can be specified. When multiple days are configured, each of them will cause the schedule to trigger. If a day-of-month is configured without configuring month, weekday, hour, and minute, the event will not execute.

Using the weekday command as well as the day-of-month command will cause the script to run twice. For example, consider that today is Monday January 1. If Tuesday January 5 is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).

The no form of this command removes the specified day-of-month from the list.

This command enables debugging for PIM database.

The no form of this command disables PIM database debugging.

This command enables dark bandwidth accounting and enters the context to configure the associated parameters. When dark bandwidth accounting is enabled, the system polls the dark bandwidth counters, performs sample and average rate computations, and generates IGP-TE updates if required. To enable dark bandwidth accounting, auxiliary MPLS statistics must first be enabled using the command config>router>mpls>aux-stats.

The no form of this command disables dark bandwidth accounting, resets all global parameters to their default values, and results in an immediate IGP-TE update for which dark bandwidth is null.

This command sets the minimum change (in percent of the latest advertised value) above which an decrease in MRLB (IS-IS TE sub-TLV 10) or MRB (OSPF TE sub-TLV 7) triggers an IGP-TE update. This configuration only applies to a change in MRLB or MRB caused by dark bandwidth. Other events affecting MRLB/MRB (such as the change of the subscription factor or the loss of link in a LAG over which the RSVP interface is defined) trigger an immediate TE update, regardless of the importance of the impact.

Optionally, the threshold can also be expressed as an absolute value. In this case, the evaluation of the change is made using the percent change and the absolute change. An IGP-TE update is sent if both thresholds are crossed. Changing this parameter in the course of dark bandwidth accounting does not affect the accounting cycle.

By default, the multiplier inherits the global value, unless it is specifically set using this command. The no form of this command sets this parameter to inherit the value of the corresponding global parameter.

This command sets the dark bandwidth multiplier to the specified value. Choosing 0% will lead to no IGP-TE updates based on dark bandwidth evolution being sent. Changing this parameter in the course of dark bandwidth accounting does not affect the accounting cycle.

This command sets the dark bandwidth multiplier to the specified value. Choosing 0% will lead to no IGP-TE updates based on dark bandwidth evolution being sent. Changing this parameter in the course of dark bandwidth accounting does not affect the accounting cycle.

By default, the multiplier inherits the global value, unless it is specifically set using this command. The no form of this command sets this parameter to inherit the value of the corresponding global parameter.

This command sets the minimum change (in percent of the latest advertised value) above which an increase in MRLB (IS-IS TE sub-TLV 10) or MRB (OSPF TE sub-TLV 7) triggers an IGP-TE update. This configuration only applies to a change in MRLB or MRB caused by dark bandwidth. Other events affecting MRLB/MRB (such as the change of the subscription factor or the loss of link in a LAG over which the RSVP interface is defined) trigger an immediate TE update, regardless of the importance of the impact.

Optionally, the threshold can also be expressed as an absolute value. In this case, the evaluation of the change uses the percent change and the absolute change. An IGP-TE update is sent if both thresholds are crossed. Changing this parameter in the course of dark bandwidth accounting does not affect the accounting cycle.

By default, the multiplier inherits the global value, unless it is specifically set using this command. The no form of this command sets this parameter to inherit the value of the corresponding global parameter.

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

The no form of this command disables DDM events.

This command, when enabled on a parent forwarding class, applies a color profile mode to the packets stored in the queue associated with this forwarding class. The queue associated with the parent forwarding class must be of type profile-mode.

When this QoS policy is applied to the ingress of a Frame Relay VLL SAP, the system will treat the received FR frames with DE bit set as out-of-profile, regardless of their previous marking as the result of the default classification or on a match with an IP filter. It also adjusts the CIR of the ingress SAP queue to consider out-of-profile frames that were sent while the SAP queue was in the “< CIR” state of the bucket. This makes sure that the CIR of the SAP is achieved.

All received DE = 0 frames that are classified into this parent forwarding class or any of its subclasses have their profile unchanged by enabling this option. That is, the DE = 0 frame profile could be undetermined (default), in-profile, or out-of-profile as per previous classification. The DE = 0 frames that have a profile of undetermined will be evaluated by the system CIR marking algorithm and will be marked appropriately.

The priority option, if used, has no effect. All FR VLL DE = 1 frames have their priority automatically set to low while DE = 0 frames have their priority set to high. Furthermore, DE = 1 frames have the drop-preference bit set in the internal header. The internal settings of the priority bit and of the drop-preference bit of the frame is independent of the use of the profile mode.

All other capabilities of the Fpipe service are maintained. This includes remarking of the DE bit on egress SAP, and FR PW control word on egress network port for the packets that were classified into “out-of-profile” at ingress SAP.

This de-1-out-profile keyword has an effect when applied to the ingress of a SAP that is part of an Fpipe service. It can also be used on the ingress of an Epipe or VPLS SAP.

The no form of this command disables the color profile mode of operation on all SAPs to which this ingress QoS policy is applied.

This command is used to explicitly define the marking of the DE bit for fc fc-name according to the inplus-profile/in-profile or out-of-profile/exceed-profile status of the packet (fc-name may be used to identify the dot1p-value).

If no DE value is present, the default values are used for the marking of the DE bit; for example, 0 for inplus-profile or in-profile packets, 1 for out-of-profile or exceed-profile packets. For more information, refer to the IEEE 802.1ad-2005 standard.

In the PBB case, for a Backbone SAP (B-SAP) and for packets originated from a local I-VPLS/PBB-Epipe, the command dictates the marking of the DE bit for both the BVID and ITAG.

If this command is not used, the DE bit should be preserved if an ingress TAG exist; otherwise, set to zero.

If the DE value is included in the command line, this value is to be used for all the packets of this forwarding class regardless of their profile status.

The commands de-mark-inner and de-mark-outer take precedence over the de-mark command if both are specified in the same policy.

This command is used to explicitly define the marking of the DE bit for fc fc-name according to the inplus-profile or in-profile and out-of-profile or exceed-profile status of the packet (fc-name may be used to identify the dot1p value).

This command is used to explicitly define the marking of the DE bit in the inner VLAN tag for fc fc-name on a QinQ SAP, according to the in- and out-of-profile status of the packet.

If no DE value is present, the default values are used for the marking of the DE bit; for example, 0 for inplus-profile or in-profile packets, 1 for out-of-profile or exceed-profile packets. For more information, refer to the IEEE 802.1ad-2005 standard.

If the DE value is included in the command line, this value is used for all the inner tags of packets of this forwarding class, regardless of their profile status.

This command takes precedence over the de-mark command if both are specified in the same policy and over the default action.

The configuration of qinq-mark-top-only under the SAP egress takes precedence over the use of the de-mark-inner in the policy. That is, the inner VLAN tag is not remarked when qinq-mark-top-only is configured (the marking used for the inner VLAN tag is based on the current default, which is governed by the marking of the packet received at the ingress to the system).

If no de-mark commands are used, the DE bit is preserved if an ingress inner tag exists; otherwise, set to 0.

Remarking the inner DE bit is not supported based on the profile result of egress policing.

This command is used to explicitly define the marking of the DE bit in the outer or single VLAN tag on a qinq or dot1q SAP, respectively, according to the in, out, or exceed-profile status of the packet.

If no DE value is present, the default values are used for the marking of the DE bit; for example, 0 for inplus-profile/in-profile packets, 1 for out-of-profile/exceed-profile packets. For more information, refer to the IEEE 802.1ad-2005 standard.

If the DE value is included in the command line, this value is used for all the outer or single tags of packets of this forwarding class, regardless of their profile status.

In the PBB case, for a Backbone SAP (B-SAP) and for packets originated from a local I-VPLS/PBB-Epipe, the command dictates the marking of the DE bit for both the BVID and ITAG.

This command takes precedence over the de-mark command if both are specified in the same policy and over the default action.

If no de-mark commands are used, the DE bit is preserved if an ingress outer or single tag exists; otherwise, set to 0.

This command configures the time, in seconds, that OSPF waits before declaring a neighbor router down. If no Hello packets are received from a neighbor for the duration of the dead interval, the router is assumed to be down. The minimum interval must be two times the Hello interval.

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

This command configures the time, in seconds, that OSPF waits before declaring a neighbor router down. If no hello packets are received from a neighbor for the duration of the dead interval, the router is assumed to be down. The minimum interval must be two times the hello interval.

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

This command configures the PCEP session dead timer value, which is the amount of time a PCEP speaker (PCC or PCE) will wait after the receipt of the last PCEP message before declaring its peer down.

The keep-alive mechanism is asymmetric, meaning that each PCEP speaker can propose a different dead timer value to its peer to use to detect session timeout.

The no form of the command returns the dead timer to the default value.

This command enables the inband control path debouncing. The no form of this command disables inband control path debouncing.

The no form of this command reverts to the default.

This command configures when to trigger, for example after one or more event occurrences. The number of occurrences of an event can be bounded by a time window or left open.

The no form of this command removes the debounce configuration.

Commands in this context specify debugging options.

This command enables output to the debug log. Traced messages are decoded as text and sent to debug logging. This allows for real-time debugging but is not recommended on live systems because of the decode overhead.

This command disables logging to the compact flash. The debug-output and live-output commands are mutually exclusive.

The no form of this command disables output to the debug log.

This command saves existing debug configuration (configuration done under the debug branch of CLI). Debug configurations are not saved by the admin save command and not preserved across a node reboot or CPM switchover. The debug-save command makes the debug configuration available for the operator to execute after a reboot by using the exec command or after a CPM switchover by using the switchover-exec command, if desired.

In case the file is encrypted this command is used to configure the decryption key used to read the file.

The no form of this command removes the url-list object.

This command specifies the default application profile to be used by a subscriber host.

The no form of this command removes the application profile name from the configuration.

This command configures the default application profile.

This command configures a default application profile.

This command configures the default SPI sharing method for IPoE or PPPoE sessions from the same subscriber, having the same SLA profile associated, that are active on the same SAP. SPI sharing can be per-SAP or a dedicated SPI per-session.

This command specifies a default destination string for all subscribers associated with the SAP. The command also accepts the use-top-q flag that automatically derives the string based on the top most delineating Dot1Q tag from the SAP’s encapsulation.

The no form of this command removes the default subscriber identification string from the configuration.

This command specifies a default destination string for all subscribers associated with the SAP. The command also accepts the use-top-q flag that automatically derives the string based on the top most delineating Dot1Q tag from the SAP’s encapsulation.

The no form of this command removes the default subscriber identification string from the configuration.

no def-sub-id

This command defines how the BGP will treat a received EVPN route without RC5512 BGP encapsulation extended community. If no encapsulation is received, BGP will validate the route as MPLS or VXLAN depending on how this command is configured.

This command specifies a default SLA profile for this SAP. The SLA profile must be defined prior to associating the profile with a SAP in the config>subscr-mgmt>sla-profile context.

If a subscriber is not explicitly associated with an SLA profile during the authentication phase, a default profile will be assigned to it.

The no form of this command removes the default SLA profile from the SAP configuration.

This command specifies the explicit default sub-id for dynamic subscriber hosts (including ARP hosts) in case that the sub-id string is not supplied through RADIUS or LUDB.

The sub-id is assigned to a new subscriber host in the following order of priority:

This command does not apply to static subscribers.

The no form of this command reverts to the default.

This command configures the default subscriber ID. The default is used if no other source (like RADIUS) provides a subscriber identification string.

This command specifies a default subscriber profile for an MSAP.

A subscriber profile defines the aggregate QoS for all hosts within a subscriber context. This is done through the definition of the egress and ingress scheduler policies that govern the aggregate SLA for subscriber using the subscriber profile.

The no form of this command removes the default SLA profile from the SAP configuration.

This command specifies a default subscriber profile for this SAP. The subscriber profile must be defined prior to associating the profile with a SAP in the config>subscr-mgmt>sub-profile context.

A subscriber profile defines the aggregate QoS for all hosts within a subscriber context. This is done through the definition of the egress and ingress scheduler policies that govern the aggregate SLA for subscriber using the subscriber profile. Subscriber profiles also allow for specific SLA profile definitions when the default definitions from the subscriber identification policy must be overridden.

The no form of this command removes the default SLA profile from the SAP configuration.

This command specifies a default subscriber profile for this SAP. The subscriber profile must be defined prior to associating the profile with a SAP in the config>subscr-mgmt>sub-profile context.

A subscriber profile defines the aggregate QoS for all hosts within a subscriber context. This is done through the definition of the egress and ingress scheduler policies that govern the aggregate SLA for subscriber using the subscriber profile. Subscriber profiles also allow for specific SLA profile definitions when the default definitions from the subscriber identification policy must be overridden.

The no form of this command removes the default SLA profile from the SAP configuration.

This command configures the default accounting policy to be used with all SAPs that do not have an accounting policy.

If no access accounting policy is defined on a SAP, accounting records are produced in accordance with the default access policy. If no default access policy is created, then no accounting records will be collected other than the records for the accounting policies that are explicitly configured.

If no network accounting policy is defined on a network port, accounting records will be produced in accordance with the default network policy. If no network default policy is created, then no accounting records will be collected other than the records for the accounting policies explicitly configured.

Only one access accounting policy ID can be designated as the default access policy. Likewise, only one network accounting policy ID can be designated as the default network accounting policy.

The record name must be specified prior to assigning an accounting policy as default.

If a policy is configured as the default policy, then a no default command must be issued before a new default policy can be configured.

The no form of this command removes the default policy designation from the policy ID. The accounting policy will be removed from all SAPs or network ports that do not have this policy explicitly defined.

This command specifies the default radius-server-policy for RADIUS accounting. This policy is used when there is no specific match based on username.

The no form of this command removes the policy name from the configuration.

This command specifies the default action for DHCP filters when no entries match.

The no form of this command reverts to the default.

This command specifies the default action for DHCP6 filters when no entries match.

The no form of this command reverts to the default.

This command specifies what should happen to packets that do not match any of the configured entries.

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

This command specifies the action to be applied to the MMRP attributes (Group B-MACs) whose ISIDs do not match the specified criteria in all of the entries of the mrp-policy.

When multiple default-action commands are entered, the last command will overwrite the previous command.

The default action specifies the action that is applied to events when no action is specified in the event filter entries or when an event does not match the specified criteria.

When multiple default-action commands are entered, the last command overwrites the previous command.

The no form of this command reverts the default action to the default value (forward).

This command specifies the default action to take for packets that do not match any filter entries.

The no form of this command reverts the default action to the default value (forward).

This command configures a TCA for the counter capturing hits for the specified GTP filter default action. A default action TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

This command configures a TCA for the counter capturing hits due to the default action specified for the GTPv2 message type filter. A default action TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

This command configures a TCA for the counter capturing hits for the specified GTP IMSI-APN filter default action. A default action TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

This command configures a TCA for the counter capturing hits for the specified SCTP filter default PPID. A default action TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

This command configures a TCA for the counter capturing hits for the specified session filter default action. A default action TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

This command configures the default action for the IMSI-APN filter.

This command configures the default action for all GTP message types.

This command configures the default action for all SCTP PPIDs.

This command configures the default action to take when the ICAP server is unreachable.

This command specifies the default action to take for packets in this nat-classifier. The default-action will apply to packet that do not match any configured criteria within nat-classifier. The no form of this command equals action forward.

This command specifies the action to be applied to multicast streams (channels) when the streams do not match any of the multicast addresses defined in the MCAC policy.

When multiple default-action commands are entered, the last command will overwrite the previous command.

This command defines or edits the default action to be taken for packets that have an undefined DSCP or MPLS EXP bit set. The default-action command specifies the forwarding class to which such packets are assigned.

Multiple default-action commands will overwrite each previous default-action command.

This command defines the default action to be applied to packets not matching any entry in this ACL filter policy or to packets for that match a PBF/PBR filter entry for which the PBF/PBR target is down and pbr-down-action-override per-entry is set to filter-default-action.

The default action specifies the action that is applied to events when no action is specified in the event filter entries or when an event does not match the specified criteria.

When multiple default-action commands are entered, the last command overwrites the previous command.

The no form of this command reverts the default action to the default value (forward).

This command creates the default action for management access in the absence of a specific management access filter match.

The default-action is applied to a packet that does not satisfy any match criteria in any of the management access filters. Whenever management access filters are configured, the default-action must be defined.

This command specifies the action to take on the traffic when there are no filter entry matches. If there are no filter entries defined, the packets received are either dropped or forwarded based on that default action.

This command specifies the default action to be applied when no match conditions are met.

Commands in this context configure actions to apply to routes that do not match any entries of a route policy statement.

The no form of this command deletes the default-action context for the policy statement.

This command configures a default action for the URL filter. The default action takes effect when the URL filter cannot be used. This may happen in the following scenarios.

The no form of this command removes the default-action for the URL filter.

This command specifies the default radius-server-policy for RADIUS authentication. This policy is used when there is no specific match based on username.

The no form of this command removes the policy name from the configuration.

This command indicates that the default BRG profile must be used for new BRGs. This profile can be overridden by RADIUS.

This command configures the default category map.

The no form of this command reverts to the default.

This command associates a charging group to any applications or app-groups that are not explicitly assigned to a charging group, for an application assurance policy.

The no form of this command deletes the default charging group from the configuration.

This command configures the default credit values for RADIUS credit control and Diameter Gy application credit control.

For RADIUS credit control, this command configures the default time or volume credit for this category. The default credit is used during initial setup when no quota is received from the RADIUS server.

For Diameter Gy credit control, this command specifies the interim credit assigned to this category (rating group) when Extended Failure Handling (EFH) is enabled. This command is ignored when EFH is disabled.

The no form of this command reverts to the default.

This command configures the IP address to substitute for the destination IP address of the packets

This command configures last resort IP DNS addresses that can be used for name resolution by IPoE hosts (IA_NA, IA_PD and SLAAC) and PPPoE hosts (IA_NA, IA_PD and SLAAC).

The no form of this command reverts to the default.

This command configures last resort IPv6 DNS addresses that can be used for name resolution by IPoEv6 hosts (IA_NA, IA_PD and SLAAC) and PPPoEv6 hosts (IA_NA, IA_PD and SLAAC).

The no form of this command reverts to the default.

This command configures the DNS domain name to be added in DNS retries when a DNS query is not replied or an empty DNS reply is received.

The no form of this command prevents DNS retries when the DNS query is not replied or an empty DNS reply is received.

Commands in this context configure MIP creation parameters per index (bridge-identifier bridge-id vlan vlan-id) if the MIP creation statement exists as part of the service connection. The mip creation statement must be present on the connection before any configuration can occur for a MIP under this context. The determining factor for MIP creation is based on the authoritative properties of the eth-cfm domain association configuration. The individual indexes in this table are used for MIP creation only when the association context is not authoritative; this includes the lack of association for a matching index.

This command configures the default forwarding class for the policy. In the event that an ingress packet does not match a higher priority (more explicit) classification command, the default forwarding class or subclass will be associated with the packet. Unless overridden by an explicit forwarding class classification rule, all packets received on an ingress SAP using this ingress QoS policy will be classified to the default forwarding class. Optionally, the default ingress enqueuing priority for the traffic can be overridden as well.

The default forwarding class is best effort (be). The default-fc settings are displayed in the show configuration and save output regardless of inclusion of the detail keyword.

This command configures the recorder filter default action to either record or no-record. This parameter applies to http-host values not matching any expressions defined in the filter context.

This command configures the group interface where the PPP sessions are established when the authentication server does not specify the group interface.

The no form of this command removes the interface name or service ID from the configuration.

This command configures a TCA for the counter capturing drops due to the GTP endpoint limits create requests exceeding the configured allowed limit (set by the default-tunnel-endpoint-limit command). A default-gtp-tunnel-endpoint-limit drop TCA can be created for traffic generated from the subscriber side of AA (from-sub). The create keyword is mandatory when creating a TCA.

This command configures the default-host. More than one default host can be configured per SAP.

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

This command enables a non-MI capable router to establish an adjacency and operate with an SR OS in a non-zero instance. If the router does not receive IID-TLVs, it will establish an adjacency in a single instance. Instead of establishing an adjacency in the standard instance 0, the router will establish an adjacency in the configured non-zero instance. The router will then operate in the configured non-zero instance so that it appears to be in the standard instance 0 to its neighbor. This feature is supported on point-to-point interfaces, broadcast interfaces are not supported.

The no form of this command disables the functionality so that the router can only establish adjacencies in the standard instance 0.

This command enables a non-MI capable router to establish an adjacency and operate with a router in a non-zero instance. If the router does not receive IID-TLVs, it will establish an adjacency in a single instance. Instead of establishing an adjacency in the standard instance 0, the router will establish an adjacency in the configured non-zero instance. The router will then operate in the configured non-zero instance so that it appears to be in the standard instance 0 to its neighbor. This feature is supported on point-to-point interfaces, broadcast interfaces are not supported.

This feature must be configured on the router connected to non-MI capable routers and on all other SR OS routers in the area, so that they receive non-MI LSPs in the correct instance and not in the base instance.

The no form of this command disables the functionality so that the router can only establish adjacencies in the standard instance 0.

This command configures the default metric to be used for the IS-IS interface in the IPv4 multicast topology (MT3).

The no form of this command deletes the specified default metric and reverts to using the system default of 10.

This command configures the default metric to be used for the IS-IS interface in the IPv4 multicast topology (MT3).

The no form of this command deletes the specified default metric and reverts to using the system default of 10.

This command configures the default metric to be used for the IS-IS interface in the IPv6 multicast topology (MT4).

The no form of this command deletes the specified default metric and reverts to using the system default of 10.

This command configures the default metric to be used for the IS-IS interface in the IPv6 multicast topology (MT4).

The no form of this command deletes the specified default metric and reverts to using the system default of 10.

This command specifies the default metric for IPv6 unicast.

This command specifies the default metric for IPv6 unicast.

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

This command specifies a route-table preference value to use for EBGP or IBGP routes carrying labeled-unicast prefixes and received from peers covered by the context of the command. Route-table preference comes into play when the route-table has multiple routes for the same IP prefix. In this case the route with the numerically lowest preference value is usually the route that is activated and installed into the IP FIB. By default all BGP routes have a route-table preference value of 170.

This command overrides the preference value assigned by the label-preference command; that other command does not distinguish between EBGP and IBGP routes. Overriding happens even when the default-label-preference value is inherited from a higher level of configuration and competes with an explicitly configured label-preference value at a lower level of configuration in the BGP hierarchy.

Note: The preference value assigned by the default-label-preference command can always be overwritten by a route policy entry that accepts the route with a preference command in the action.

The no form of the command lets BGP route-table preference for labeled-unicast routes to be controlled by other means.

This command sets the default metric that routes imported by the RTM will acquire.

The no form of this command removes the metric.

This command specifies the configurable default metric used for all IS-IS interfaces on this level. This value is not used if a metric is configured for an interface.

This command configures the metric used by the area border router (ABR) for the default route into a stub area. The default metric should only be configured on an ABR of a stub area. An ABR generates a default route if the area is a stub area.

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

This command specifies the configurable default metric used for all IS-IS interfaces on this level. This value is not used if a metric is configured for an interface.

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

This command configures the metric used by the area border router (ABR) for the default route into a stub area.

The default metric should only be configured on an ABR of a stub area.

An ABR generates a default route if the area is a stub area.

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

This command specifies the default managed SAP policy to use to create MSAPs when the response from the RADIUS server does not specify a managed SAP policy.

The policy-name parameter is only valid for a SAP with the keywords capture-sap specified in the SAP’s configuration. The capture-sap keyword in the SAP configuration captures the SAP where triggering packets is sent to the CPM. Non-triggering packets captured by the capture SAP is dropped.

The managed SAP policy must already be defined in the config>subscr-mgmt>msap-policy context.

The no form of this command removes the policy-name from the configuration.

This command configures the default PAP password for RADIUS authentication when the Password-Length=0 in the PAP Authenticate-Request.

RADIUS authentication cannot be initiated when the Password-Length=0 in the PAP Authenticate-Request and no default-pap-password is configured. The PPP session terminates in this case.

A default path binding must be provided before the LSP template can be used for signaling LSP. The LSP template must be shutdown to modify default-path binding.

This command designates a peer as a default peer. Traffic that is destined to realms that are not associated with locally configured peers, is sent to the default-peer. In effect, the default peer becomes a default route for Diameter realms.

This command is mandatory in multi-chassis redundancy where the inter-chassis peer is designated as default peer. Then, the SR with no open connections towards agents or servers, forwards all traffic to the inter-peer which maintains, as part of MCS, open connections with agents and servers.

The no form of this command reverts to the default.

Using the default peer mechanism, a peer can be selected as the default Multicast Source Discovery Protocol (MSDP) peer. As a result, all source-active messages from the peer will be accepted without the usual peer-reverse-path-forwarding (RPF) check.

The MSDP peer-RPF check is different from the normal multicast RPF checks. The peer-RPF check is used to stop source-active messages from looping. A router validates source-active messages originated from other routers in a deterministic fashion.

A set of rules is applied in order to validate received source-active messages, and the first rule that applies determines the peer-RPF neighbor. All source-active messages from other routers are rejected. The rules applied to source-active messages originating at Router S received at Router R from Router N are as follows:

Using the default peer mechanism, a peer can be selected as the default Multicast Source Discovery Protocol (MSDP) peer. As a result, all source-active messages from the peer will be accepted without the usual peer-reverse-path-forwarding (RPF) check.

The MSDP peer-RPF check is different from the normal multicast RPF checks. The peer-RPF check is used to stop source-active messages from looping. A router validates source-active messages originated from other routers in a deterministic fashion.

A set of rules is applied in order to validate received source-active messages, and the first rule that applies determines the peer-RPF neighbor. All source-active messages from other routers are rejected. The rules applied to source-active messages originating at Router S received at Router R from Router N are as follows:

This command references a default DHCP address pool for local PPPoX pool management in case that the pool-name is not returned via Radius or LUDB.

This command specifies a route-table preference value to use for EBGP or IBGP routes carrying unlabeled prefixes and received from peers covered by the context of the command. Route-table preference comes into play when the route-table has multiple routes for the same IP prefix. In this case, the route with the numerically lowest preference value is usually the route that is activated and installed into the IP FIB. By default all BGP routes have a route-table preference value of 170.

This command overrides the preference value assigned by the preference command; that other command does not distinguish between EBGP and IBGP routes. Overriding happens even when the default-preference value is inherited from a higher level of configuration and competes with an explicitly configured preference value at a lower level of configuration in the BGP hierarchy.

Note: The preference value assigned by the default-preference command can always be overwritten by a route policy entry that accepts the route with a preference command in the action.

The no form of the command lets BGP route-table preference to be controlled by other means.

This command configures the default enqueuing priority for all packets received on an ingress SAP using this policy. To change the default priority for the policy, the fc-name must be defined whether it is being changed or not.

This command configures the default category profile to use when no category profile is explicitly selected for the subscriber.

The no form of this command removes the selected default profile configuration.

This command specifies the default certificate revocation status that is used result when both the primary and secondary CSV methods fail to verify the status.

This command specifies the id of default retail service if there is no match found in VLAN to retail map configuration (specified by the vlan command). For DSM and migrant, this command is only applicable for non-NAT stacks.

This command configures the default retailer service for WIFI users.

This command configures a route tag that EVPN and IP-VPN use when sending a route to the BGP application (for the corresponding service and BGP instance). If the corresponding BGP EVPN instance is enabled, the command cannot be changed. Additionally, EVPN services can add tags to routes with proxy-arp/nd>evpn-route-tag or the route table tag (added using the import policy). Only one tag is passed from EVPN to the BGP for matching on export policies. In case of a conflict with other route tags pushed by EVPN, the default route tag has the least priority.

The following are examples of the conflict priority handling:

The default-route-tag configuration is only supported on EVPN and IP-VPN service routes. The route tag for ES and AD per-ES routes is always zero.

The no form of this command removes the default-route-tag (that is, it sets the route tag to zero).

This command configures the route tag for default route for the router or VPRN service.

This command configures the route tag for default route.

This command originates the default RTC route (zero prefix length) towards the selected peers.

This command configures the IP address of the default router for a DHCP client. Up to four IP addresses can be specified.

The no form of this command removes the address(es) from the configuration.

This command adds a default SAP to the managed VLAN list.

The no form of this command removes the default SAP to the managed VLAN list.

This command specifies a service ID or service name of the default security service used by this SAP IPsec gateway.

This command configures the default forwarding set.

This command sets the default tag that routes processed by the AAA route downloader will take.

Note: Any route received with a specific tag retains the specific tag. The tag value is passed to the Route Table Manager and is available as match condition on the export statement of other routing protocols.

The no form of this command reverts to the default.

This command configures the maximum number of GTP endpoints requested in GTP-C messages by using, for example, the PDP Context Create message type.

The validate-gtp-tunnels command must be enabled before using this command.

The no form of this command sets the limit to 4294967295 (the maximum number of GTP endpoints supported by AA FW minus one).

This command configures a default tunnel policy template for the gateway.

This command configures the default username for authentication when not provided in PAP/CHAP authentication (no Name field in CHAP Response message or Peer-Id-Length=0 in PAP Authenticate-Request).

The PPP session terminates when no username is provided in PAP/CHAP authentication and no default-user-name is configured.

This command assigns one of the characteristic values as default.

When a default value is specified, app-profile entries that do not explicitly include this characteristic inherit the default value and use it as part of the AQP match criteria based on that app-profile.

A default-value is required for each characteristic. This is evaluated at commit time.

The no form of this command removes the default value for the characteristic.

Commands in this context configure server default timer and option parameters. These can be overridden on a per-pool and per-prefix basis.

Commands in this context configure default parameters for the GTP connection that can be used when the parameters are not returned in authentication.

Commands in this context configure or apply delay interface attributes such as static delay.

This command sets the delay before the progress indicator is displayed in the MD-CLI.

This command configures the type of delay measurement statistic used in both the sample window and aggregate sample window.

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

This command sets the bin number, the threshold and the direction that is monitored to determine if a delay metric threshold crossing event has occurred or has cleared. It requires a bin number, a rising threshold value and a direction. If the clear-threshold value is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. When a raise threshold is reached, the log event is generated. Each unique threshold can only be raised once for the threshold within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised another is not raised until a measurement interval completes, and the clear threshold has not been exceeded. A clear event is raised under that condition. In general, alarms are generated when there is a state change. The thresholds configured are applied to the count in specified bin and all higher number bins.

The no form of this command removes thresholding for this delay metric. The complete command must be configured in order to remove the specific threshold.

This optional command allows results from probes that map to the specified bin and higher bins to be excluded from the TCA count. The TCA count is used to determine if a threshold has been reached by the event monitoring function. Individual counters are incremented in the bin, but the counts in the specified bin and higher bins are not included in the TCA threshold computation. A delay-event must be configured in the same direction, and the lowest-bin configured as part of the delay-event-exclusion command must be higher than the lowest bin specified by the corresponding delay-event command.

The bin group allows this optional command to be added, modified, or deleted while tests are actively referencing the bin group. The bin group does not need to be shut down during delay-event-exclusion configuration. If the values are modified while the active tests are executing, all configured TCAs for the specified direction within the bin group enters a pending (p) state until the start of the next measurement interval. Any existing stateful TCAs that were raised are cleared without creating a log event, and no further processing for the affected TCAs occur in the active window. Depending on timing, the pending state may continue past the adjacent measurement interval until the start of the following measurement interval.

The no form of this command does not exclude any values from the configured TCA threshold.

This enables the monitoring of all configured delay events. Adding this functionality starts the monitoring of the configured delay events at the start of the next measurement interval. If the function is removed using the no command, all monitoring of configured delay events, logging, and recording of new events for that session are suspended. Any existing events at the time of the shut down are maintained until the active measurement window in which the removal was performed has completed. The state of this monitoring function can be changed without having to shutdown all the tests in the session.

The no form of this command disables the monitoring of all configured delay events.

This command selects the delay source to be advertised by the IGP for this interface.

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

It is recommended to only use this command when session-accounting is used. By default, a dual stack subscriber generates a RADIUS accounting interim message for each new host update (IPv4, IPv6 WAN, and IPv6 PD). This command delays the trigger of a RADIUS accounting start message and allows all hosts to connect first. When the delay timer expires, a single RADIUS accounting start message containing all the host currently connected to the BNG is sent to the server. Subsequent host connections will trigger interim-updates if host-update is enabled on session-accounting. For all other accounting modes, this command will delay the trigger of an accounting start when a host connects.

The no form of this command reverts to the default.

This command specifies a reference to a config>oam-pm>streaming delay-template for the Ethernet DMM test. It is possible to include a delay template reference that is not configured under config>oam-pm>streaming. In this case, the streaming of the results is not in effect. Refer to the config>oam-pm>streaming delay-template command for session to template interaction behaviors.

The no form of this command deletes the delay template from the test.

This command specifies a reference to a config>oam-pm>streaming delay-template for the IP TWAMP LIGHT test. It is possible to include a delay template reference that is not configured under config>oam-pm>streaming. In this case, streaming of results are not in effect. Refer to the config>oam-pm>streaming delay-template command for session to template interaction behaviors.

The no form of this command deletes the delay template from the test.

This command specifies a reference to a config>oam-pm>streaming delay-template for the MPLS DM test. It is possible to include a delay template reference that is not configured under config>oam-pm>streaming. In this case, streaming of results are not in effect. Refer to the config>oam-pm>streaming delay-template command for session to template interaction behaviors.

The no form of this command deletes the delay template from the test.

This command specifies a template for streaming delay metrics that can be referenced under the oam-pm>session technology delay style test.

The delay-template must be configured under the technology delay test oam-pm>session to allow the delay specific test to stream results using the configured template attributes.

The no form of this command deletes the specified delay template.

This command enables the generation of the delegated-ipv6-prefix RADIUS attribute.

The no form of this command disables the generation of the delegated-ipv6-prefix RADIUS attribute.

This command configures the delegated prefix length that is used if the DHCPv6 client does not specify a prefix length hint.

The DHCPv6 client prefix length hint is limited by the range specified by the minimum and maximum parameters. If the hint is smaller than the minimum, the allocated prefix length is equal to the minimum length. If the hint is larger than the maximum, the allocated prefix length is equal to the maximum length.

The no form of this command reverts to the default.

This command configures the subscriber interface level setting for delegated prefix length. The delegated prefix length for a subscriber- interface can be either set to a fixed value that is explicitly configured under the subscriber interface CLI hierarchy or a variable value that can be obtained from various sources. This command can be changed only when no IPv6 prefixes are configured under the subscriber-interface context.

The no form of this command reverts to the default.

This command deletes the specified file.

The optional wildcard (*) can be used to delete multiple files that share a common (partial) prefix and/or (partial) suffix. When the wildcard is entered, the following prompt displays for each file that matches the wildcard:

“Delete file <filename> (y/n)?”

This command deletes the selected CLI node (which includes all sub-branches). The deleted lines are also copied into a temporary buffer that can be used for a subsequent insert.

This command deletes a rollback checkpoint and causes the suffixes to be adjusted (decremented) for all checkpoints older that the one that was deleted (to close the hole in the list of checkpoint files and create room to create another checkpoint).

If config redundancy rollback-sync is enabled, a rollback delete will also delete the equivalent checkpoint on the standby CF and shuffle the suffixes on the standby CF.

It is not advised to manually delete a rollback checkpoint (for example, using a file delete command). If a rollback checkpoint file is manually deleted without using the admin rollback delete command then the suffixes of the checkpoint files are not shuffled, nor is the equivalent checkpoint file deleted from the standby CF. This manual deletion creates a hole in the checkpoint file list until enough new checkpoints have been created to roll the hole off the end of the list.

This command enables the NETCONF delete-config operation.

The no form of this command disables the operation.

This command enables matching on UEs that are in a delete-pending state.

The no form of this command disables matching on UEs in a delete pending-state, unless all state matching is disabled.

This command sets the delivery service for GRE encapsulated packets associated with a particular GRE tunnel. This is the IES or VPRN service where the GRE encapsulated packets are injected and terminated. The delivery service may be the same service that owns the private tunnel SAP associated with the GRE tunnel. The GRE tunnel does not come up until a valid delivery service is configured.

The no form of this command deletes the delivery-service from the GRE tunnel configuration.

This command configures the percentage of the delta (from the beginning to the end of the current H-QoS below CIR or above CIR pass) of the aggregate rate consumed by its other members that can be given to a queue at the end of an H-QoS below CIR pass and above CIR pass. This command is only applicable when the port scheduler is configured to use the above-offered-allowance-control algorithm, otherwise it is ignored.

The no form of this command reverts the delta-consumed-agg-rate percent to its default value.

This command configures the percentage of the delta (from the beginning to the end of the current H-QoS below CIR or above CIR pass) of the higher tier rate consumed by its other members that can be given to a queue at the end of an H-QoS below CIR pass and above CIR pass. Higher tier refers to the Vport aggregate rate and port scheduler level, group, and maximum rates.

This command is only applicable when the port scheduler is configured to use the above-offered-allowance-control algorithm, otherwise it is ignored.

The no form of this command reverts the delta-consumed-higher-tier-rate percent to its default value.

This command sets a lower limit on the virtual router in-use priority that can be derived from the delta priority control events.

Each vrrp-priority-id places limits on the delta priority control events to define the in-use priority of the virtual router instance. Setting this limit prevents the sum of the delta priority events from lowering the in-use priority value of the associated virtual router instances below the configured value.

The limit has no effect on explicit priority control events. Explicit priority control events are controlled by setting the in-use priority to any value between 1 and 254.

Only non-owner virtual router instances can be associated with VRRP priority control policies and their priority control events.

Once the total sum of all delta events is calculated and subtracted from the base priority of the virtual router instance, the result is compared to the delta-in-use-limit value. If the result is less than the limit, the delta-in-use-limit value is used as the virtual router in-use priority value. If an explicit priority control event overrides the delta priority control events, the delta-in-use-limit has no effect.

Setting the limit to a higher value than the default of 1 limits the effect of the delta priority control events on the virtual router instance base priority value. This allows for multiple priority control events while minimizing the overall effect on the in-use priority.

Changing the in-use-priority-limit causes an immediate re-evaluation of the in-use priority values for all virtual router instances associated with this vrrp-policy-id based on the current sum of all active delta control policy events.

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

This command sets the threshold value below which the FCC server will dent/drop unicast data sent to the FCC client during a fast channel change. Within the RTP extension header, the packet priority (PRI) (2 bits) and the fine-grained priority (FPRI) (3 bits) indicate the “importance” of the frame as to how essential it is to the video stream.

This parameter is only applicable if the FCC server mode is dent.

The no form of the command returns the parameter to the default value.

This command adds a deny-list URL list to the local URL filter policy.

The no form of this command removes the URL list object.

This command enables the system to send out a warning when the prefix with a configured length is no longer available in the provisioned prefix.

For example:

With the above configuration, the system will send out a warning when there is no available /64 that can be allocated out of 2001:0:0:ffe0::/50.

The no form of this command disables the warnings.

This command enables the system to send out warnings when the prefix with the configured length is no longer available in the pool.

The no form of this command disables the warnings.