f Commands
facility
facility
Syntax
facility syslog-facility
no facility
Context
[Tree] (config>service>vprn>log>syslog facility)
Full Context
configure service vprn log syslog facility
Description
This command configures the facility code for messages sent to the syslog target host.
Multiple syslog IDs can be created with the same target host but each syslog ID can only have one facility code. If multiple facility codes are entered, the last facility-code entered overwrites the previous facility-code.
If multiple facilities need to be generated for a single syslog target host, then multiple log-id entries must be created, each with its own filter criteria to select the events to be sent to the syslog target host with a given facility code.
The no form of this command reverts to the default value.
Default
local7 — Syslog entries are sent with the local7 facility code.
Parameters
- syslog-facility
-
Specifies syslog facility name represents a specific numeric facility code. The code should be entered in accordance with the syslog RFC. However, the software does not validate if the facility code configured is appropriate for the event type being sent to the syslog target host.
Platforms
All
facility
Syntax
facility syslog-facility
Context
[Tree] (config>app-assure>group>evt-log>syslog facility)
Full Context
configure application-assurance group event-log syslog facility
Description
This command configures the syslog facility. The syslog facility is an information field associated with a syslog message. It is defined by the syslog protocol and provides an indication of which part of the system originated the message.
Default
facility local7
Parameters
- syslog-facility
-
Specifies the syslog facility keyword.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
facility
Syntax
facility syslog-facility
Context
[Tree] (config>service>nat>syslog>syslog-export-policy facility)
Full Context
configure service nat syslog syslog-export-policy facility
Description
This command configures a syslog facility. For more information, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR System Management Guide. The config>log>syslog>level hierarchy also applies to this context.
Default
facility local0
Parameters
- syslog-facility
-
Specifies a syslog facility name which represents a specific numeric facility code. The code must be entered in accordance with the syslog RFC. However, the software does not validate if the facility code configured is appropriate for the event type being sent to the syslog target host.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
facility
Syntax
facility syslog-facility
no facility
Context
[Tree] (config>log>syslog facility)
Full Context
configure log syslog facility
Description
This command configures the facility code for messages sent to the syslog target host.
Multiple syslog IDs can be created with the same target host but each syslog ID can only have one facility code. If multiple facility codes are entered, the last facility-code entered overwrites the previous facility-code.
If multiple facilities need to be generated for a single syslog target host, then multiple log-id entries must be created, each with its own filter criteria to select the events to be sent to the syslog target host with a given facility code.
The no form of this command reverts to the default value.
Default
facility local7
Parameters
- syslog-facility
-
Specifies a syslog facility name which represents a specific numeric facility code. The code must be entered in accordance with the syslog RFC. However, the software does not validate if the facility code configured is appropriate for the event type being sent to the syslog target host.
Platforms
All
facility-fault
facility-fault
Syntax
[no] facility-fault
Context
[Tree] (config>port>ethernet>eth-cfm>mep facility-fault)
[Tree] (config>lag>eth-cfm>mep facility-fault)
Full Context
configure port ethernet eth-cfm mep facility-fault
configure lag eth-cfm mep facility-fault
Description
Allows the facility MEP to move from alarming only to network actionable function. This means a facility MEP will not merely report the defect conditions but will be able to action based on the transition of the MEP state. Without this command the facility MEP will only monitor and report and conditions of the MEP do not affect related services.
Default
no facility-fault
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
facility-fault
Syntax
[no] facility-fault
Context
[Tree] (config>router>if>eth-cfm>mep facility-fault)
Full Context
configure router interface eth-cfm mep facility-fault
Description
This command allows the facility MEP to move from alarming only to network actionable function. This means that a MEP facility reports both the defect conditions and the actions that are based on the transition of the MEP state.
The no form of this command causes the facility MEP to only monitor and report conditions on the MEPs that do not affect related services.
Default
no facility-fault
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
facility-id-permission
facility-id-permission
Syntax
facility-id-permission {chassis}
no facility-id-permission
Context
[Tree] (config>eth-cfm>domain>assoc facility-id-permission)
Full Context
configure eth-cfm domain association facility-id-permission
Description
This command allows the operator to include the sender-id TLV information that was specified under the config>eth>system>sender-id context for facility base MEPs. When this option is present under the maintenance association, the specific MPs in the association included the sender-id TLV information in ETH-CFM PDUs. MEPs include the sender-id TLV for CCM (not sub second CCM enabled MEPs), LBM/LBR, and LTM/LTR. MIPs include this value in the LBR and LTR PDUs.
LBR functions reflect all TLVs received in the LBM unchanged including the SenderID TLV. This command produces an error when a bridge-identifier is configured under the association. Facility MEPs do not support the bridge-identifier. Transmission of the Management Domain and Management Address fields are not supported in this TLV.
Parameters
- chassis
-
Sends the configured chassis information defined under eth-cfm>system using the sender-id option.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fail-action
fail-action
Syntax
fail-action {continue | drop}
no fail-action
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>match-radprox-cache fail-action)
Full Context
configure subscriber-mgmt local-user-db ipoe host match-radius-proxy-cache fail-action
Description
This command specifies the action to take when no match is found in the cache.
The no form of this command reverts to the default.
Default
fail-action drop
Parameters
- continue
-
Specifies to continue when no match is found.
- drop
-
Specifies to drop when no match is found.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fail-action
Syntax
fail-action fail-action
no fail-action
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>action fail-action)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry action fail-action
Description
This command configures the fail action when a packet matches with a VAS filter entry in a specific direction, but no mapping exists for the specified SF-IP or ESI in the specified EVPN service.
The no form of this command removes the fail action from the configuration.
Parameters
- fail-action
-
Specifies the fail action.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
fail-action
Syntax
fail-action {[metric metric-value] [ preference preference-value] [tag tag-value] | withdraw}
no fail-action
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check fail-action)
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check fail-action)
Full Context
configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check fail-action
configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check fail-action
Description
This command configures the fail action based on specific criteria.
The no form of this command removes the fail action from the configuration.
Parameters
- metric-value
-
Specifies the route metric associated with the provisioned managed route if the CPE check fails.
- preference-value
-
Specifies the route preference associated with the provisioned managed route if the CPE check fails.
- tag-value
-
Specifies the route tag used if the CPE check fails.
- withdraw
-
Keyword to specify the withdrawal of the route entry if the CPE check fails.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fail-on-error
fail-on-error
Syntax
[no] fail-on-error
Context
[Tree] (config>card>xiom fail-on-error)
[Tree] (config>card fail-on-error)
Full Context
configure card xiom fail-on-error
configure card fail-on-error
Description
This command controls the behavior of the card when any one of a specific set of card level errors is encountered in the system. When the fail-on-error command is enabled, and any one (or more) of the specific errors is detected, then the Operational State of the card is set to Failed. This Failed state will persist until the clear card command is issued (reset) or the card is removed and re-inserted (re-seat). If the condition persists after re-seating the card, then Nokia support should be contacted for further investigation.
Enabling fail-on-error is only recommended when the network is designed to be able to route traffic around a failed card (redundant cards, nodes or other paths exist).
The list of specific errors includes:
-
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 without independent IOM/IMM and CPM cards, the node is rebooted if fail-on-error is enabled and one of the card level errors is encountered.
The tmnxEqCardPChipError is only considered as a trigger for card fail-on-error for ingress FCS errors (not egress FCS errors), and only for Ethernet MDAs or IMMs.
Note that upon the detection of the event/error in the system, the reporting of the event (logs) and the fail-on-error behavior of the card are independent. Log event control configuration will determine whether the events are reported in logs (or SNMP traps, and so on) and the fail-on-error configuration will determine the behavior of the card. This implies that the card can be configured to fail-on-error even if the events are suppressed (some may be suppressed in the system by default). In order to facilitate post-failure analysis, Nokia recommends that you enable the reporting of the specific events/errors ( configure log event-control) when fail-on-error is enabled.
Default
no fail-on-error
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s
- configure card xiom fail-on-error
All
- configure card fail-on-error
fail-on-error
Syntax
[no] fail-on-error
Context
[Tree] (config>card>mda fail-on-error)
Full Context
configure card mda fail-on-error
Description
This command enables the fail-on-error feature. If an MDA is experiencing too many Egress XPL Errors, this feature causes the MDA to fail. This can force an APS switchover or traffic re-route. The purpose of this feature is to avoid situations where traffic is forced to use a physical link that suffers from errors but is still technically operational.
The feature uses values configured in the config>card>mda>egress-xpl context. When this feature is enabled on a MDA, if window consecutive minutes pass in which the MDA experiences more than threshold Egress XPL Errors per minute, then the MDA will be put in the failed state.
The no form of this command disables the feature on the MDA.
Platforms
All
fail-to-open
fail-to-open
Syntax
[no] fail-to-open
Context
[Tree] (config>isa>aa-grp fail-to-open)
Full Context
configure isa application-assurance-group fail-to-open
Description
This command configures the mode of operation during an operational failure of this application assurance group when no application assurance engines are available to service traffic. When enabled, all traffic that was to be inspected will be dropped. When disabled, all traffic that was to be inspected will be forwarded without any inspection as if the group was not configured at all.
Default
no fail-to-open
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
failed-mda-limit
failed-mda-limit
Syntax
failed-mda-limit number
no failed-mda-limit
Context
[Tree] (config>isa>nat-group failed-mda-limit)
Full Context
configure isa nat-group failed-mda-limit
Description
This command configures the maximum number of supported simultaneously failures in the active-active intra-chassis NAT redundancy model. Traffic from the failed ISAs is distributed over the remaining ISA in the system. Memory resources are reserved in every ISA to accommodate new mappings from the failed ISA. However, bandwidth is not reserved and each ISA operates at max speed in all conditions (with failure or without the failure).
NAT translations are not preserved across switchovers and consequently they will have to be re-initiated by the clients.
For this command to take effect, the intra-chassis redundancy mode must be set to active-active ( config>isa>nat-group>redundancy active-active).
Default
no failed-mda-limit
Parameters
- number
-
Specifies the number of simultaneous ISA failures supported in active-active intra-chassis NAT redundancy model.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
failed-threshold
failed-threshold
Syntax
failed-threshold [1 to 1000]
failed-threshold all
Context
[Tree] (config>service>vpls>site failed-threshold)
Full Context
configure service vpls site failed-threshold
Description
This command defines the number of objects should be down for the site to be declared down. Both administrative and operational status must be evaluated and if at least one is down, the related object is declared down.
Default
failed-threshold all
Parameters
- 1 to 1000
-
Specifies the threshold for the site to be declared down.
Platforms
All
failover
failover
Syntax
failover
Context
[Tree] (config>service>vprn>dhcp>server failover)
[Tree] (config>service>vprn>dhcp6>server failover)
[Tree] (config>router>dhcp>server>pool failover)
[Tree] (config>router>dhcp6>server>pool failover)
[Tree] (config>service>vprn>dhcp>server>pool failover)
[Tree] (config>router>dhcp6>server failover)
[Tree] (config>router>dhcp>server failover)
[Tree] (config>service>vprn>dhcp6>server>pool failover)
Full Context
configure service vprn dhcp local-dhcp-server failover
configure service vprn dhcp6 local-dhcp-server failover
configure router dhcp local-dhcp-server pool failover
configure router dhcp6 local-dhcp-server pool failover
configure service vprn dhcp local-dhcp-server pool failover
configure router dhcp6 local-dhcp-server failover
configure router dhcp local-dhcp-server failover
configure service vprn dhcp6 local-dhcp-server pool failover
Description
Commands in this context configure failover parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
failover
Syntax
failover
Context
[Tree] (config>router>l2tp>group failover)
[Tree] (config>service>vprn>l2tp failover)
[Tree] (config>router>l2tp>group>tunnel failover)
[Tree] (config>router>l2tp failover)
[Tree] (config>service>vprn>l2tp>group failover)
[Tree] (config>service>vprn>l2tp>group>tunnel failover)
Full Context
configure router l2tp group failover
configure service vprn l2tp failover
configure router l2tp group tunnel failover
configure router l2tp failover
configure service vprn l2tp group failover
configure service vprn l2tp group tunnel failover
Description
Commands in this context configure LAC multi-chassis redundancy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
failure-action
failure-action
Syntax
failure-action down
no failure-action
Context
[Tree] (config>router>ldp>lsp-bfd failure-action)
Full Context
configure router ldp lsp-bfd failure-action
Description
This command configures the action to take when LSP BFD fails on an LDP LSP.
The system generates an SNMP trap if BFD goes down on an LSP, regardless of whether a failure action is configured or not.
The no form of this command removes the failure action.
Default
no failure-action
Parameters
- down
-
Specifies the LSP is marked as unusable in the TTM. If the LSP appears as a shortcut in RTM, then the route is removed.
Platforms
All
failure-action
Syntax
failure-action down
no failure-action
Context
[Tree] (config>service>epipe>spoke-sdp>bfd failure-action)
[Tree] (config>service>ies>interface>spoke-sdp>bfd failure-action)
[Tree] (config>service>vprn>interface>spoke-sdp>bfd failure-action)
[Tree] (config>service>vpls>spoke-sdp>bfd failure-action)
Full Context
configure service epipe spoke-sdp bfd failure-action
configure service ies interface spoke-sdp bfd failure-action
configure service vprn interface spoke-sdp bfd failure-action
configure service vpls spoke-sdp bfd failure-action
Description
This command configures the ability to bind the operational state of a spoke-SDP to the state of its VCCV BFD session.
If failure-action down is configured, the spoke-SDP is taken operationally down if the associated VCCV BFD session goes down. This configuration also allows BFD packets to be forwarded on an otherwise operationally down spoke-SDP in order to test the spoke-SDP connectivity.
The no form of this command removes the failure action.
Default
no failure-action
Parameters
- down
-
Specifies that the spoke-SDP is taken operationally down if the associated VCCV BFD session goes down.
Platforms
All
failure-action
Syntax
failure-action failure-action
no failure-action
Context
[Tree] (config>router>mpls>lsp>bfd failure-action)
Full Context
configure router mpls lsp bfd failure-action
Description
This command configures what action occurs when LSP BFD fails on an RSVP or SR-TE LSP.
A failure action of down means an LSP is marked as unusable in TTM. If it appears as a shortcut in RTM, the route is removed. This failure action can only be configured on RSVP LSPs.
A failure action of failover causes the active path of an RSVP LSP to switch to the secondary or next-preference available secondary path. This option is only available for RSVP LSPs. It is not applicable to one-hop-p2p and mesh-p2p auto LSPs.
A failure action of failover-or-down means that a switchover from the active path is triggered on failure of the BFD session on the active path (primary or standby). If there is no available path to switch to, then the LSP is taken operationally down. For RSVP-TE LSPs, this failure action causes the two best-preference standby paths to be programmed in the data path, in addition to the primary.
The system generates an SNMP trap if BFD goes down on an LSP, regardless of whether a failure action is configured or not.
The no form of this command removes the failure action.
Default
no failure-action
Parameters
- down
-
Specifies that the LSP will be marked as unusable in the TTM. If it appears as a shortcut in RTM, then the route will be removed.
- failover
-
Specifies that the active path of an RSVP LSP will switch to the secondary path or next-preference available secondary path. This option is only available for RSVP LSPs. It is not applicable in the LSP template.
- failover-or-down
-
Specifies that the active path of an SR-TE or RSVP-TE LSP switches to the secondary or next-preference available secondary path, or for the LSP to go operationally down if no other path is available.
Platforms
All
failure-action
Syntax
failure-action {down | failover-or-down}
no failure-action
Context
[Tree] (config>router>mpls>lsp-template>bfd failure-action)
Full Context
configure router mpls lsp-template bfd failure-action
Description
This command configures the action to take when LSP BFD fails on an RSVP LSP.
The system generates an SNMP trap if BFD goes down on an LSP, regardless of whether or not a failure action is configured.
The no form of this command removes the failure action.
Default
no failure-action
Parameters
- down
-
Specifies that the LSP is marked as unusable in the TTM. If it appears as a shortcut in RTM, then the route is removed.
- failover-or-down
-
Specifies that the active path of an SR-TE LSP switches to the secondary or next-preference available secondary path, or for the LSP to go operationally down if no other path is available. This option is only available for SR-TE LSPs.
Platforms
All
failure-mode
failure-mode
Syntax
failure-mode [discard | per-link-hash]
no failure-mode
Context
[Tree] (config>lag>link-map-profile failure-mode)
Full Context
configure lag link-map-profile failure-mode
Description
This command defines the failure mode for egress traffic of SAPs/network interfaces that use this link-map-profile when neither primary nor secondary links of this profile are available.
Default
failure-mode per-link-hash
Parameters
- discard
-
Specifies egress traffic for SAPs/network interfaces using this link-map-profile is discarded to protect SAP/network interface traffic on other LAG links from impact of re-hashing the affected SAPs/network interfaces.
- per-link-hash
-
Specifies egress traffic for SAPs/network interfaces using this link-map-profile is rehashed on remaining, available LAG links using per-link-hash algorithm. SAP/network interface QoS configurations dictate what traffic is discarded on any link that may become oversubscribed as result of the re-hash.
Platforms
All
failure-recovery
failure-recovery
Syntax
[no] failure-recovery
Context
[Tree] (config>sys>switch-fabric failure-recovery)
Full Context
configure system switch-fabric failure-recovery
Description
Commands in this context configure attributes related to the automatic switch fabric recovery process.
The automatic switch fabric recovery process is triggered when there are two resets of an IOM/XCM due to ICC failures within a small time frame. The recovery process involves the sequential resetting of SFM in case the issues are due to one of the SFM in the ICC communication path. As the final step in the recovery process, a CPM switchover is triggered to reset the active CPM.
Platforms
7450 ESS, 7750 SR-7, 7750 SR-12e, 7950 XRS
failure-threshold
failure-threshold
Syntax
failure-threshold number
no failure-threshold
Context
[Tree] (config>test-oam>icmp>ping-template failure-threshold)
Full Context
configure test-oam icmp ping-template failure-threshold
Description
This command configures the count, when reached, that causes the transition of the IPv4 interface from operationally up to operationally down because of a ping template failure.
The no form of this command reverts to the default value.
Default
failure-threshold 3
Parameters
- number
-
Specifies a count that causes the transition of the IP interface from operationally up to operationally down because of ping template failure.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fallback-action
fallback-action
Syntax
fallback-action accept [force-probing]
fallback-action user-db local-user-db-name [ force-probing]
no fallback-action
Context
[Tree] (config>subscr-mgmt>auth-plcy fallback-action)
Full Context
configure subscriber-mgmt authentication-policy fallback-action
Description
This command configures the action when no RADIUS server is available; servers are either out of service or are in a probing state.
The no form of this command removes the action from the configuration.
Parameters
- accept
-
Specifies that all authentication requests are automatically accepted.
- local-user-db-name
-
Specifies that the LUDB is used to authenticate to the server.
- force-probing
-
Specifies that a subscriber or a test user Access-Request, depending which arrives first, is used to probe a RADIUS server before continuing with the configured fallback-action. This forces an out-of-service server to transition to a probing state.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fallback-path-computation-method
fallback-path-computation-method
Syntax
fallback-path-computation-method {none | local-cspf}
no fallback-path-computation-method
Context
[Tree] (config>router>mpls>lsp fallback-path-computation-method)
[Tree] (config>router>mpls>lsp-template fallback-path-computation-method)
Full Context
configure router mpls lsp fallback-path-computation-method
configure router mpls lsp-template fallback-path-computation-method
Description
This command specifies the fallback path computation method used if all configured PCEs are down or the signaling overload and the redelegation timer has expired. This method is used regardless of whether the LSP is PCE-controlled and PCE-computed, or just PCE-computed.
The no form of this command removes the fallback path computation method used.
Default
fallback-path-computation-method none
Parameters
- none
-
Specifies to fall back to using the named path for RSVP-TE LSPs.
- local-cspf
-
Specifies to fall back to using local CSPF computation.
Platforms
All
falling-percent-reset
falling-percent-reset
Syntax
falling-percent-reset percent-of-highest
no falling-percent-reset
Context
[Tree] (config>mcast-mgmt>bw-plcy falling-percent-reset)
Full Context
configure mcast-management bandwidth-policy falling-percent-reset
Description
This command is configures the percentage of bandwidth decrease that must occur to reset the dynamic bandwidth monitoring function for a multicast channel. When a channel is configured to use the ingress dynamic bandwidth as the in-use bandwidth for ingress multicast path management, the system maintains a sliding window in time that defines how long the last highest bandwidth value associated with the channel should be used. The sliding window duration is derived from the channels bw-activity dynamic falling-delay parameter within the multicast information policy. Each time the system detects a current bandwidth for a channel that is equal to or greater than the current highest bandwidth for the channel, the sliding window is reset and the highest value is used when managing the ingress multicast paths. If the system does not detect a higher or equal bandwidth value for the channel within the window period, the system resets the sliding window and uses the next highest rate seen during the duration of the window period. In this way, the system delays relinquishing bandwidth for a dynamic bandwidth channel for a configurable period. If a momentary fluctuation (decrease) in ingress bandwidth occurs, the system ignores the bandwidth change.
While this is useful for momentary fluctuations in bandwidth, it may be desirable to react faster when the current bandwidth monitored for a channel drops significantly relative to the currently in-use bandwidth. When the bandwidth decrease is equal to or greater than the falling-percent-reset value, the system immediately stops using the highest bandwidth and starts using the current bandwidth while resetting the sliding window.
If falling-percent-reset is set to 50%, when the current ingress dynamic bandwidth is 50% of the current in-use highest bandwidth, the system immediately uses the current dynamic ingress bandwidth as the highest bandwidth for the channel.
By default, the falling-percent-reset is 50% when a new bandwidth policy is created. The default bandwidth policy also has a hard configured value of 50%. Setting falling-percent-reset to 100 is equivalent to specifying no falling-percent-reset.
The no form of this command restores the default value of 50%.
Default
falling-percent-reset 50
Parameters
- percent-of-highest
-
The percent-of-highest parameter is required and defines the percentage of decline between the current ingress dynamic bandwidth and the current in-use highest bandwidth at which the system resets the dynamic ingress bandwidth monitoring for the channel. When reset in this case, the system uses the current ingress dynamic bandwidth as the highest rate and continues monitoring. The parameter must be defined as an integer value representing a percentage.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
family
family
Syntax
family [ipv4 | ipv6]
Context
[Tree] (config>lag>bfd family)
Full Context
configure lag bfd family
Description
This command specifies the address family for the micro-BFD session over the associated LAG links.
Default
family ipv4
Parameters
- ipv4
-
Specifies that IPv4 encapsulation be used for the micro-BFD session.
- ipv6
-
Specifies that IPv6 encapsulation be used for the micro-BFD session.
Platforms
All
family
Syntax
family family
Context
[Tree] (config>service>vprn>bgp>convergence family)
Full Context
configure service vprn bgp convergence family
Description
This command specifies the convergence family used for route convergence.
Parameters
- family
-
Specifies the convergence family used for route convergence
Platforms
All
family
Syntax
[no] family {ipv4 | ipv6 | label-ipv4 | flow-ipv4 | flow-ipv6}
Context
[Tree] (config>service>vprn>bgp>graceful-restart>long-lived family)
[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived family)
[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived family)
Full Context
configure service vprn bgp graceful-restart long-lived family
configure service vprn bgp group graceful-restart long-lived family
configure service vprn bgp group neighbor graceful-restart long-lived family
Description
This command configures family-specific LLGR parameters for BGP peers.
Default
no family
Parameters
- ipv4
-
Specifies the IPv4 family.
- ipv6
-
Specifies the IPv6 family.
- label-ipv4
-
Specifies the label IPv4 family.
- flow-ipv4
-
Specifies the flow IPv4 family.
- flow-ipv6
-
Specifies the flow IPv6 family.
Platforms
All
family
Syntax
family [ipv4] [label-ipv4] [ipv6] [mcast-ipv4] [ flow-ipv4] [mcast-ipv6] [ flow-ipv6]
no family
Context
[Tree] (config>service>vprn>bgp>group>neighbor family)
[Tree] (config>service>vprn>bgp family)
[Tree] (config>service>vprn>bgp>group family)
Full Context
configure service vprn bgp group neighbor family
configure service vprn bgp family
configure service vprn bgp group family
Description
This command configures the set of BGP address families (AFI plus SAFI) to be supported by the applicable VPRN BGP sessions.
The no form of this command restores the default, which corresponds to unlabeled IPv4 unicast routes (AFI 1, SAFI 1) only.
Default
family ipv4
Parameters
- ipv4
-
Adds support for the IPv4 unicast (unlabeled) address family.
- label-ipv4
-
Adds support for the IPv4 unicast (labeled) address family.
- ipv6
-
Adds support for the IPv6 unicast (unlabeled) address family.
- mcast-ipv4
-
Adds support for the IPv4 multicast SAFI address family.
- flow-ipv4
-
Adds support for the IPv4 FlowSpec address family.
- mcast-ipv6
-
Adds support for the IPv6 multicast SAFI address family.
- flow-ipv6
-
Adds support for the IPv6 FlowSpec address family.
Platforms
All
family
Syntax
family [ipv4 | ipv6]
Context
[Tree] (config>router>mpls>lsp-template family)
Full Context
configure router mpls lsp-template family
Description
This command specifies if the lsp-template is for use in IPv4 or IPv6 SR-TE LSP.
This command is optional in a IPv4 SR-TE auto-LSP but must be set to ipv6 value in a IPv6 SR-TE auto-LSP. By default, this command is set to ipv4 value for backward compatibility.
When establishing both IPv4 and IPv6 SR-TE mesh auto-LSPs with the same parameters and constraints, a separate LSP template of type mesh-p2p-srte must be configured for each address family with the family CLI leaf set to the IPv4 or IPv6 value. SR-TE one-hop auto-LSPs can only be established for either IPv4 or IPv6 family, but not both. The family leaf in the LSP template of type one-hop-p2p-srte should be set to the desired IP family value.
The no form of this command reverts to the default value.
Default
family ipv4
Parameters
- ipv4
-
Specifies the lsp-template is for use in IPv4 SR-TE LSP.
- ipv6
-
Specifies the lsp-template is for use in IPv6 SR-TE LSP.
Platforms
All
family
Syntax
family
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy family)
Full Context
configure subscriber-mgmt bgp-peering-policy family
Description
Commands in this context specify the BGP address families supported by the ESM dynamic BGP peers.
When unconfigured, the IPv4 address family is supported on BGPv4 peers and the IPv6 address family is supported on BGPv6 peers.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
family
Syntax
[no] family
Context
[Tree] (config>cflowd>collector>export-filter family)
Full Context
configure cflowd collector export-filter family
Description
This command defines the address family for the flow types that should not be sent to the associated cflowd collector.
Multiple family types can be defined in this context to filter out multiple address families to a given collector.
The no form of this command removes the address family definition, allowing all address family types to be exported to the associated collector.
Default
no family
Platforms
All
family
Syntax
family family
Context
[Tree] (config>router>bgp>convergence family)
Full Context
configure router bgp convergence family
Description
This command configures the IP family used for route convergence.
Parameters
- family
-
Specifies the convergence family.
Platforms
All
family
Syntax
family [ipv4] [label-ipv4] [vpn-ipv4] [ipv6] [ label-ipv6] [vpn-ipv6] [ mcast-ipv4] [ l2-vpn] [mvpn-ipv4] [mvpn-ipv6] [mdt-safi] [ ms-pw] [flow-ipv4] [flow-ipv6] [route-target] [ mcast-vpn-ipv4] [evpn] [bgp-ls] [mcast-ipv6] [mcast-vpn-ipv6] [sr-policy-ipv4] [sr-policy-ipv6] [flow-vpn-ipv4] [flow-vpn-ipv6]
no family
Context
[Tree] (config>router>bgp>group>neighbor family)
[Tree] (config>router>bgp family)
[Tree] (config>router>bgp>group family)
Full Context
configure router bgp group neighbor family
configure router bgp family
configure router bgp group family
Description
This command configures the set of BGP address families (AFI/SAFI) to be supported by the base router BGP sessions.
The no form of this command restores the default, which corresponds to unlabeled IPv4 unicast routes (AFI 1, SAFI 1) only.
Default
family ipv4
Parameters
- ipv4
-
Advertises MP-BGP support for the IPv4 unicast (unlabeled) address family.
- label-ipv4
-
Advertises MP-BGP support for the IPv4 unicast (labeled) address family.
- vpn-ipv4
-
Advertises MP-BGP support for the IPv4 VPN (SAFI 128) address family.
- ipv6
-
Advertises MP-BGP support for the IPv6 unicast (unlabeled) address family.
- label-ipv6
-
Advertises MP-BGP support for the IPv6 unicast (labeled) address family.
- vpn-ipv6
-
Advertises MP-BGP support for the IPv6 VPN (SAFI 128) address family.
- mcast-ipv4
-
Advertises MP-BGP support for the IPv4 multicast SAFI address family.
- l2-vpn
-
Advertises MP-BGP support for the L2 VPN address family.
- mvpn-ipv4
-
Advertises MP-BGP support for the IPv4 multicast VPN address family.
- mvpn-ipv6
-
Advertises MP-BGP support for the IPv6 multicast VPN address family.
- mdt-safi
-
Advertises MP-BGP support for the MDT SAFI address family.
- ms-pw
-
Advertises MP-BGP support for the multi-segment pseudowire address family.
- flow-ipv4
-
Advertises MP-BGP support for the IPv4 FlowSpec address family.
- flow-ipv6
-
Advertises MP-BGP support for the IPv6 FlowSpec address family.
- route-target
-
Advertises MP-BGP support for RT constraint routes.
- mcast-vpn-ipv4
-
Advertises MP-BGP support for the IPv4 VPN multicast (SAFI 129) address family.
- evpn
-
Advertises MP-BGP support for the EVPN address family.
- bgp-ls
-
Enables the advertisement of BGP-LS address family to the associated BGP neighbors.
- mcast-ipv6
-
Advertises MP-BGP support for the IPv6 multicast SAFI address family.
- mcast-vpn-ipv6
-
Advertises MP-BGP support for the IPv6 multicast routes from a VPRN over the provider network. This family is only applicable in the base BGP routing context.
- sr-policy-ipv4
-
Advertises MP-BGP support for AFI1/SAFI73 IP address families for BGP routes that encode a segment-routing policy to an IPv4 destination.
- sr-policy-ipv6
-
Advertises MP-BGP support for AF12/SAF173 IP address families for BGP routes that encode a segment-routing policy to an IPv6 destination.
- flow-vpn-ipv4
-
Advertises support for the FlowSpec-VPN IPv4 address family (AFI 1, SAFI 134).
- flow-vpn-ipv6
-
Advertises support for the FlowSpec-VPN IPv6 address family (AFI 2, SAFI 134).
Platforms
All
family
Syntax
[no] family {ipv4 | ipv6 | label-ipv4 | label-ipv6 | vpn-ipv4 | vpn-ipv6 | l2-vpn | route-target | flow-ipv4 | flow-ipv6 | flow-vpn-ipv4 | flow-vpn-ipv6}
Context
[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived family)
[Tree] (config>router>bgp>group>graceful-restart>long-lived family)
[Tree] (config>router>bgp>graceful-restart>long-lived family)
Full Context
configure router bgp group neighbor graceful-restart long-lived family
configure router bgp group graceful-restart long-lived family
configure router bgp graceful-restart long-lived family
Description
This command configures family-specific LLGR parameters for BGP peers.
The no form of this command deletes the context.
Default
no family
Parameters
- ipv4
-
Specifies the IPv4 family.
- ipv6
-
Specifies the IPv6 family.
- label-ipv4
-
Specifies the label IPv4 family.
- label-ipv6
-
Specifies the label IPv6 family.
- vpn-ipv4
-
Specifies the VPN IPv4 family.
- vpn-ipv6
-
Specifies the VPN IPv6 family.
- l2-vpn
-
Specifies the Layer 2 VPN family.
- route-target
-
Specifies the route target family.
- flow-ipv4
-
Specifies the flow IPv4 family.
- flow-ipv6
-
Specifies the flow IPv6 family.
- flow-vpn-ipv4
-
Specifies the FlowSpec-VPN IPv4 address family.
- flow-vpn-ipv6
-
Specifies the FlowSpec-VPN IPv6 address family.
Platforms
All
family
Syntax
family {label-ipv4 | label-ipv6 | vpn}
Context
[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel family)
Full Context
configure router bgp next-hop-resolution labeled-routes transport-tunnel family
Description
This command configures the address family context for configuring next-hop resolution of BGP label routes.
Parameters
- label-ipv4
-
Enters the context for configuring next-hop-resolution options for labeled-unicast IPv4 routes.
- label-ipv6
-
Enters the context for configuring next-hop-resolution options for labeled-unicast IPv6 routes.
- vpn
-
Enters the context for configuring next-hop-resolution options for VPN-IPv4 and VPN-IPv6 routes when they are not imported into any VPRN service.
Platforms
All
family
Syntax
family {ipv4 | ipv6}
Context
[Tree] (config>router>bgp>next-hop-res>shortcut-tunnel family)
Full Context
configure router bgp next-hop-resolution shortcut-tunnel family
Description
This command creates the context to configure next-hop resolution of unlabeled IPv4 or unlabeled IPv6 routes by certain tunnel types in the tunnel table.
Parameters
- ipv4
-
Specifies that the configuration applies to unlabeled IPv4 BGP routes.
- ipv6
-
Specifies that the configuration applies to unlabeled IPv6 BGP routes.
Platforms
All
family
Syntax
family [ipv4] [ipv6] [ label-ipv4] [label-ipv6] [ mcast-ipv4] [mcast-ipv6] [vpn-ipv4] [ vpn-ipv6] [mcast-vpn-ipv4] [mcast-vpn-ipv6] [ evpn] [l2-vpn] [sr-policy-ipv4] [sr-policy-ipv6]
no family
Context
[Tree] (config>bmp>station family)
Full Context
configure bmp station family
Description
This command configures the address families that are reported to a BMP monitoring station.
The no form of this command reverts to the default value.
Default
family ipv4
Parameters
- ipv4
-
Keyword to add support for the IPv4 unicast (unlabeled) address family.
- ipv6
-
Keyword to add support for the IPv6 unicast (unlabeled) address family.
- label-ipv4
-
Keyword to add support for the IPv4 unicast (labeled) address family.
- label-ipv6
-
Keyword to add support for the IPv6 unicast (labeled) address family.
- mcast-ipv4
-
Keyword to add support for the IPv4 multicast address family.
- mcast-ipv6
-
Keyword to add support for the IPv6 multicast address family.
- vpn-ipv4
-
Keyword to add support for the IPv4 VPN (SAFI 128) address family.
- vpn-ipv6
-
Keyword to add support for the IPv6 VPN (SAFI 128) address family.
- mcast-vpn-ipv4
-
Keyword to add support for the IPv4 VPN multicast address family.
- mcast-vpn-ipv6
-
Keyword to add support for the IPv6 VPN multicast address family.
- evpn
-
Keyword to add support for the VPN address family.
- l2-vpn
-
Keyword to add support for the L2-VPN address family.
- sr-policy-ipv4
-
Keyword to add support for the SR policy IPv4 address family.
- sr-policy-ipv6
-
Keyword to add support for the SR policy IPv6 address family.
Platforms
All
family
Syntax
family {ipv4 | ipv6 | srv4 | srv6}
Context
[Tree] (config>router>isis>igp-shortcut>tunnel-next-hop family)
Full Context
configure router isis igp-shortcut tunnel-next-hop family
Description
Commands in this context configure the resolution of IGP IPv4 and IGP IPv6 prefix families, as well as SR-ISIS IPv4 and SR-ISIS IPv6 tunnel families using IGP shortcuts.
Parameters
- ipv4
-
Selects the IPv4 address family.
- ipv6
-
Selects the IPv6 address family.
- srv4
-
Selects the SR-ISIS IPv4 tunnel family.
- srv6
-
Selects the SR-ISIS IPv6 tunnel family.
Platforms
All
family
Syntax
family {ipv4 | ipv6}
no family
Context
[Tree] (config>router>isis>segment-routing>adjacency-set family)
Full Context
configure router isis segment-routing adjacency-set family
Description
This command specifies the address family of an adjacency set in IS-IS.
The no form of this command reverts to the default.
Default
family ipv4
Parameters
- ipv4
-
Specifies a family of IPv4.
- ipv6
-
Specifies a family of IPv6.
Platforms
All
family
Syntax
family {ipv4 | srv4}
Context
[Tree] (config>router>ospf>igp-shortcut>tunnel-next-hop family)
Full Context
configure router ospf igp-shortcut tunnel-next-hop family
Description
Commands in this context configure the resolution of the IGP IPv4 prefix family or SR-OSPF IPv4 tunnel using IGP shortcuts.
Parameters
- ipv4
-
Selects the IPv4 address family.
- srv4
-
Selects the SR-OSPF IPv4 tunnel family.
Platforms
All
family
Syntax
family ipv6
Context
[Tree] (config>router>ospf3>igp-shortcut>tunnel-next-hop family)
Full Context
configure router ospf3 igp-shortcut tunnel-next-hop family
Description
Commands in this context configure the resolution of the IGP IPv6 prefix family using IGP shortcuts.
Parameters
- ipv6
-
Selects the IPv6 address family.
Platforms
All
family
Syntax
family [ipv4] [label-ipv4] [vpn-ipv4] [ipv6] [ label-ipv6] [vpn-ipv6] [ mcast-ipv4] [ l2-vpn] [mvpn-ipv4] [mvpn-ipv6] [mdt-safi] [ ms-pw] [flow-ipv4] [flow-ipv6] [route-target] [ mcast-vpn-ipv4] [evpn] [bgp-ls] [mcast-ipv6] [mcast-vpn-ipv6] [sr-policy-ipv4] [sr-policy-ipv6] [ flow-vpn-ipv4] [flow-vpn-ipv6]
no family
Context
[Tree] (config>router>policy-options>policy-statement>entry>from family)
Full Context
configure router policy-options policy-statement entry from family
Description
This command specifies address families as matching conditions.
The no form of the command configures the router to use the default value.
Default
no family
Parameters
- ipv4
-
Matches routes belonging to the IPv4 unicast (unlabeled) address family.
- label-ipv4
-
Matches routes belonging to the IPv4 unicast (labeled) address family.
- vpn-ipv4
-
Matches routes belonging to the IPv4 VPN (SAFI 128) address family.
- ipv6
-
Matches routes belonging to the IPv6 unicast (unlabeled) address family.
- label-ipv6
-
Matches routes belonging to the IPv6 unicast (labeled) address family.
- vpn-ipv6
-
Matches routes belonging to the IPv6 VPN (SAFI 128) address family.
- mcast-ipv4
-
Matches routes belonging to the IPv4 multicast SAFI address family.
- l2-vpn
-
Matches routes belonging to the L2 VPN address family.
- mvpn-ipv4
-
Matches routes belonging to the IPv4 multicast VPN address family.
- mvpn-ipv6
-
Matches routes belonging to the IPv6 multicast VPN address family.
- mdt-safi
-
Matches routes belonging to the MDT SAFI address family.
- ms-pw
-
Matches routes belonging to the multi-segment pseudowire address family.
- flow-ipv4
-
Matches routes belonging to the IPv4 FlowSpec address family.
- flow-ipv6
-
Matches routes belonging to the IPv6 FlowSpec address family.
- route-target
-
Matches routes belonging to the address family for RT constrain routes.
- mcast-vpn-ipv4
-
Matches routes belonging to the IPv4 VPN multicast (SAFI 129) address family.
- evpn
-
Matches routes belonging to the EVPN address family.
- bgp-ls
-
Enables the advertisement of BGP-LS address family to the associated BGP neighbors.
- mcast-ipv6
-
Matches routes belonging to the IPv6 multicast SAFI address family.
- mcast-vpn-ipv6
-
Matches routes belonging to the IPv6 multicast routes from a VPRN over the provider network. This family is only applicable in the base BGP routing context.
- sr-policy-ipv4
-
Matches routes belonging to the segment routing policy IPv4 address family (AFI1/SAFI73).
- sr-policy-ipv6
-
Matches routes belonging to the segment routing policy IPv6 address family (AFI2/SAFI73).
- flow-vpn-ipv4
-
Matches routes belonging to the FlowSpec-VPN IPv4 address family (AFI 1, SAFI 134).
- flow-vpn-ipv6
-
Matches routes belonging to the FlowSpec-VPN IPv6 address family (AFI 2, SAFI 134).
Platforms
All
family
Syntax
[no] family {ipv6 | ipv4}
Context
[Tree] (config>router>bgp>srv6 family)
Full Context
configure router bgp segment-routing-v6 family
Description
This command adds a configuration context for family-specific behaviors that relate to processing prefix SID attributes containing SRv6 TLVs.
The no form of this command deletes the family configuration context.
Parameters
- ipv4
-
Specifies a family of IPv4.
- ipv6
-
Specifies a family of IPv6.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
family
Syntax
[no] family {ipv6 | ipv4}
Context
[Tree] (config>router>bgp>group>srv6>route family)
[Tree] (config>router>bgp>group>neighbor>srv6>route family)
Full Context
configure router bgp group segment-routing-v6 route-advertisement family
configure router bgp group neighbor segment-routing-v6 route-advertisement family
Description
This command specifies an address family to use when configuring whether to strip SRv6 TLVs from BGP routes advertised to peers.
The no form of this command deletes the context.
Default
no family
Parameters
- ipv4
-
Specifies a family of IPv4.
- ipv6
-
Specifies a family of IPv6.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
fan-control
fan-control
Syntax
fan-control
Context
[Tree] (config>system fan-control)
Full Context
configure system fan-control
Description
Commands in this context configure the speed of the router fans.
Only use commands in this context with authorized direction from Nokia technical support.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se
far-end
far-end
Syntax
far-end ip-address [vc-id vc-id] [{ing-svc-label ingress-vc-label | tldp}] [icb]
no far-end ip-address
Context
[Tree] (config>mirror>mirror-dest>remote-source far-end)
Full Context
configure mirror mirror-dest remote-source far-end
Description
This command is used on a destination router in a remote mirroring solution. See the description for the remote-source command for additional information.
When using L2TPv3, MPLS-TP or LDP IPv6 LSP SDPs in the remote mirroring solution, the destination node should be configured with remote-src>spoke-sdp entries. For all other types of SDPs, remote-source>far-end entries are used.
Up to 50 far-end entries can be specified.
The no form of this command removes the IP address from the remote source configuration.
Parameters
- ip-address
-
Specifies the service IP address (system IP address) of the remote device sending mirrored traffic to this mirror destination service. If 0.0.0.0 is specified, any remote is allowed to send to this service.
- vc-id
-
Specifies the virtual circuit identifier of the remote source. For mirror services, the vc-id defaults to the service-id. However, if the vc-id is being used by another service a unique vc-id is required to create an SDP binding. For this purpose the mirror service SDP bindings accepts vc-ids. This VC ID must match the VC ID used on the spoke SDP that is configured on the source router.
- ingress-vc-label
-
Specifies the ingress service label for mirrored service traffic on the far end device for manually configured mirror service labels.
The defined ing-svc-label is entered into the ingress service label table which causes ingress packet with that service label to be handled by this mirror destination service.
The specified ing-svc-label must not have been used for any other service ID and must match the egress service label being used on the spoke SDP that is configured on the source router. It must be within the range specified for manually configured service labels defined on this router. It may be reused for other far end addresses on this mirror-dest-service-id.
- tldp
-
Specifies that the label is obtained through signaling via the LDP.
- icb
-
Specifies that the remote source is an inter-chassis backup SDP binding.
Platforms
All
far-end
Syntax
far-end node-id node-id [global-id global-id]
far-end [ip-address | ipv6-address]
no far-end ip-address | ipv6-address
Context
[Tree] (config>service>sdp far-end)
Full Context
configure service sdp far-end
Description
This command configures the system IP address of the far-end destination router for the Service Distribution Point (SDP) that is the termination point for a service.
The far-end IP address must be explicitly configured. The destination IP address must be that of an SR OS and for a GRE SDP it must match the system IP address of the far end router.
If the SDP uses GRE for the destination encapsulation, the IP address is checked against other GRE SDPs to verify uniqueness. If the IP address is not unique within the configured GRE SDPs, an error is generated and the IP address is not associated with the SDP. The local device may not know whether the IP address is actually a system IP interface address on the far-end device.
If the SDP uses MPLS encapsulation, the far-end address is used to check LSP names when added to the SDP. If the " to IP address” defined within the LSP configuration does not exactly match the SDP far-end address, the LSP will not be added to the SDP and an error will be generated. Alternatively, an SDP that uses MPLS can have an MPLS-TP node with an MPLS-TP node-id and (optionally) a global ID. In this case, the SDP must use an MPLS-TP LSP and the SDP signaling parameter must be set to off.
An SDP cannot be administratively enabled until a far-end ip-address or MPLS-TP node-id is defined. The SDP is operational when it is administratively enabled ( no shutdown) and the far-end ip-address is contained in the IGP routing table as a host route. OSPF ABRs should not summarize host routes between areas. This can cause SDPs to become operationally down. Static host routes (direct and indirect) can be defined in the local device to alleviate this issue.
On a tunnel configured as SDP with delivery type of eth-gre-bridged, this command designates L2oGRE tunnel end points. This is the only configuration option allowed for this type of SDP.
The no form of this command removes the currently configured destination IP address for the SDP. The ip-address parameter is not specified and will generate an error if used in the no far-end command. The SDP must be administratively disabled using the config service sdp shutdown command before the no far-end command can be executed. Removing the far-end IP address will cause all lsp-name associations with the SDP to be removed.
Parameters
- far-end
-
Specifies the far-end termination point for the GRE tunnel.
- ip-address | ipv6-address
-
Specifies a IPv4 or IPv6 address of the far-end SR OS for the SDP in dotted decimal notation.
- node-id
-
Specifies the MPLS-TP Node ID of the far-end system for the SDP, either in dotted decimal notation (a.b.c.d) or an unsigned 32-bit integer (1 to 4294967295). This parameter is mandatory for an SDP using an MPLS-TP LSP.
- global-id
-
Specifies a MPLS-TP Global ID of the far-end system for the SDP, in an unsigned 32-bit integer (0 to 4294967295). This parameter is optional for an SDP using an MPLS-TP LSP. If not entered, a default value for the Global ID of '0’ is used. A global ID of '0’ indicates that the far-end node is in the same domain as the local node. The user must explicitly configure a Global ID if its value is non-zero.
Platforms
All
fast-leave
fast-leave
Syntax
[no] fast-leave
Context
[Tree] (config>service>vpls>mesh-sdp>igmp-snooping fast-leave)
[Tree] (config>service>vpls>spoke-sdp>mld-snooping fast-leave)
[Tree] (config>service>vpls>mesh-sdp>mld-snooping fast-leave)
[Tree] (config>service>vpls>spoke-sdp>igmp-snooping fast-leave)
[Tree] (config>service>vpls>sap>igmp-snooping fast-leave)
[Tree] (config>service>vpls>sap>mld-snooping fast-leave)
Full Context
configure service vpls mesh-sdp igmp-snooping fast-leave
configure service vpls spoke-sdp mld-snooping fast-leave
configure service vpls mesh-sdp mld-snooping fast-leave
configure service vpls spoke-sdp igmp-snooping fast-leave
configure service vpls sap igmp-snooping fast-leave
configure service vpls sap mld-snooping fast-leave
Description
This command enables fast leave.
When IGMP fast leave processing is enabled, the 7450 ESS or 7750 SR immediately removes a SAP or SDP from the IP multicast group when it detects an IGMP leave message on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a leave message from the forwarding table without first sending out group-specific queries to the SAP or SDP, which speeds up the process of changing channels.
Fast leave should only be enabled when there is a single receiver present on the SAP or SDP.
When fast leave is enabled, the configured last-member-query-interval value is ignored.
Default
no fast-leave
Platforms
All
fast-leave
Syntax
[no] fast-leave
Context
[Tree] (config>subscr-mgmt>igmp-policy fast-leave)
Full Context
configure subscriber-mgmt igmp-policy fast-leave
Description
This command enables IGMP fast-leave processing.
The no form of this command reverts to the default value.
Default
fast-leave
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fast-leave
Syntax
[no] fast-leave
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp fast-leave)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping fast-leave
Description
This command enables fast leave.
When IGMP fast leave processing is enabled, the 7450 ESS or 7750 SR will immediately remove a SAP or SDP from the IP multicast group when it detects an IGMP leave on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a leave from the forwarding table without first sending out group-specific queries to the SAP or SDP, and thus speeds up the process of changing channels (zapping).
Fast leave should only be enabled when there is a single receiver present on the SAP or SDP.
When fast leave is enabled, the configured last-member-query-interval value is ignored.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fast-leave
Syntax
[no] fast-leave
Context
[Tree] (config>subscr-mgmt>mld-policy fast-leave)
Full Context
configure subscriber-mgmt mld-policy fast-leave
Description
This command enables fast leave. When fast leave processing is enabled, the router immediately removes a SAP or SDP from the IP multicast group when it detects an MLD leave on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a leave from the forwarding table without first sending out group-specific queries to the SAP or SDP, and thus speeds up the process of changing channels (zapping).
Fast leave should only be enabled when there is a single receiver present on the SAP or SDP.
When fast leave is enabled, the configured last-member-query-interval value is ignored.
The no form of this command reverts to the default.
Default
fast-leave
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fast-leave
Syntax
[no] fast-leave
Context
[Tree] (config>service>pw-template>igmp-snooping fast-leave)
Full Context
configure service pw-template igmp-snooping fast-leave
Description
This command enables fast leave.
When IGMP fast leave processing is enabled, the 7750 SR will immediately remove a SAP or SDP from the IP multicast group when it detects an IGMP leave on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a leave from the forwarding table without first sending out group-specific queries to the SAP or SDP, and thus speeds up the process of changing channels (zapping).
Fast leave should only be enabled when there is a single receiver present on the SAP or SDP.
When fast leave is enabled, the configured last-member-query-interval value is ignored.
Default
no fast-leave
Platforms
All
fast-reroute
fast-reroute
Syntax
fast-reroute [backup-sr-tunnel]
no fast-reroute
Context
[Tree] (config>router>ldp fast-reroute)
Full Context
configure router ldp fast-reroute
Description
This command enables LDP Fast-Reroute (FRR) procedures. When enabled, LDP uses both the primary next-hop and LFA next-hop, when available, for resolving the next-hop of an LDP FEC against the corresponding prefix in the routing table. This will result in LDP programming a primary NHLFE and a backup NHLFE into the forwarding engine for each next-hop of a FEC prefix for the purpose of forwarding packets over the LDP FEC.
When any of the following events occurs, LDP instructs in the fast path the forwarding engines to enable the backup NHLFE for each FEC next-hop impacted by this event:
-
An LDP interface goes operationally down, or is admin shutdown.
-
An LDP session to a peer went down as the result of the Hello or Keep-Alive timer expiring.
-
The TCP connection used by a link LDP session to a peer went down, due say to next-hop tracking of the LDP transport address in RTM, which brings down the LDP session.
-
A BFD session, enabled on a T-LDP session to a peer, times-out and as a result the link LDP session to the same peer and which uses the same TCP connection as the T-LDP session goes also down.
-
A BFD session enabled on the LDP interface to a directly connected peer, times out and brings down the link LDP session to this peer.
The tunnel-down-dump-time option or the label-withdrawal-delay option, when enabled, does not cause the corresponding timer to be activated for a FEC as long as a backup NHLFE is still available.
Because LDP can detect the loss of a neighbor/next-hop independently, it is possible that it switches to the LFA next-hop while IGP is still using the primary next-hop. Also, when the interface for the previous primary next-hop is restored, IGP may re-converge before LDP completed the FEC exchange with it neighbor over that interface. This may cause LDP to de-program the LFA next-hop from the FEC and blackhole traffic. In order to avoid this situation, it is recommended to enable IGP-LDP synchronization on the LDP interface.
When the SPF computation determines there is more than one primary next-hop for a prefix, it will not program any LFA next-hop in RTM. Thus, the LDP FEC will resolve to the multiple primary next-hops that provide the required protection.
The backup-sr-tunnel option enables the use of SR tunnel, as a remote LFA or TI-LFA backup tunnel next-hop by an LDP FEC.
As a pre-requisite, the user must enable the stitching of LDP and SR in the LDP-to-SR direction. That is because the LSR must perform the stitching of the LDP ILM to SR tunnel when the primary LDP next-hop of the FEC fails. Thus LDP must listen to SR tunnels programmed by the IGP in TTM but the mapping server feature is not required.
Assuming the following:
-
the backup-sr-tunnel option is enabled in LDP
-
the {loopfree-alternates remote-lfa} and/or the {loopfree-alternates ti-lfa} option is enabled in the IGP instance
-
LDP was able to resolve the primary next-hop of the LDP FEC in RTM
IGP SPF will run both the base LFA and the TI-LFA algorithms and if it does not find a backup next-hop for a prefix of an LDP FEC, it will also run the remote LFA algorithm. If IGP finds a TI-LFA or a remote LFA tunnel next-hop, LDP programs the primary next-hop of the FEC using a LDP NHLFE and programs the LFA backup next-hop using a LDP NHLFE pointing to the SR tunnel endpoint. Note that the LDP packet is not "tunneled” over the SR tunnel. The LDP label is actually stitched to the segment routing label stack. LDP points both the LDP ILM and the LTN to the backup LDP NHLFE which itself uses the SR tunnel endpoint.
The behavior of the feature is thus similar to the LDP-to-SR stitching feature, except the behavior is augmented to allow the stitching of an LDP ILM/LTN to a SR tunnel also when the primary LDP next-hop of the FEC fails.
If the LDP FEC primary next-hop failed and LDP has pre-programmed a remote LFA or TI-LFA next-hop with a LDP backup NHLFE pointing to SR tunnel, the LDP ILM/LTN switches to it. Note that if for some reason the failure impacted only the LDP tunnel primary next-hop but not the SR tunnel primary next-hop, the LDP backup NHLFE will effectively point to the primary next-hop of the SR tunnel and traffic of the LDP ILM/LTN will follow this path instead of the TI-LFA or remote LFA next-hop of the SR tunnel until the latter is activated.
This feature is limited to IPv4 /32 prefixes in both LDP and SR.
The no form of this command disables the use of SR tunnels as backups for LDP FECs and disables LDP FRR.
Default
no fast-reroute
Platforms
All
fast-reroute
Syntax
fast-reroute frr-method
no fast-reroute
Context
[Tree] (config>router>mpls>lsp fast-reroute)
[Tree] (config>router>mpls>lsp-template fast-reroute)
Full Context
configure router mpls lsp fast-reroute
configure router mpls lsp-template fast-reroute
Description
This command creates a pre-computed detour LSP from each node in the path of the LSP. In case of failure of a link or LSP between two nodes, traffic is immediately rerouted on the pre-computed detour LSP, thus avoiding packet-loss.
When fast-reroute is enabled, each node along the path of the LSP tries to establish a detour LSP as follows:
-
Each upstream node sets up a detour LSP that avoids only the immediate downstream node, and merges back on to the actual path of the LSP as soon as possible.
If it is not possible to set up a detour LSP that avoids the immediate downstream node, a detour can be set up to the downstream node on a different interface.
-
The detour LSP may take one or more hops (see config>router>mpls>lsp hop-limit, config>router>mpls>lsp>primary-p2mp-instance hop-limit) before merging back on to the main LSP path.
-
When the upstream node detects a downstream link or node failure, the ingress router switches traffic to a standby path if one was set up for the LSP.
Fast reroute is available only for the primary path. No configuration is required on the transit hops of the LSP. The ingress router will signal all intermediate routers using RSVP to set up their detours. TE must be enabled for fast-reroute to work.
If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, then global revertive will not be available for the LSP to recover.
The no form of the fast-reroute command removes the detour LSP from each node on the primary path. This command will also remove configuration information about the hop-limit and the bandwidth for the detour routes.
The no form of fast-reroute hop-limit command reverts to the default value.
A one-to-one detour backup LSP cannot be used at the PLR for ABR node protection. As a result, a PLR node does not signal a one-to-one detour LSP for ABR protection. In addition, the ABR node rejects a Path message that it has received from a third-party implementation configured with a detour object and a loose ERO next-hop. The Path message is rejected regardless of whether the cspf-on-loose-hop command is enabled on the node. When the router transits ABR for the detour path, the router rejects the signaling of an inter-area detour backup LSP.
Default
no fast-reroute — When fast-reroute is specified, the default fast-reroute method is one-to-one.
Parameters
- frr-method
-
Configures the fast-reroute method.
Platforms
All
fast-reroute
Syntax
[no] fast-reroute
Context
[Tree] (config>router>bier fast-reroute)
Full Context
configure router bier fast-reroute
Description
This command enables BIER Fast Reroute (FRR).
The no form of this command disables BIER FRR.
Default
no fast-reroute
Platforms
All
fast-start
fast-start
Syntax
[no] fast-start
Context
[Tree] (config>qos>adv-config-policy>child-control>offered-measurement fast-start)
Full Context
configure qos adv-config-policy child-control offered-measurement fast-start
Description
This command is used to enable fast detection of initial bandwidth on a child policer or queue associated with the policy. Multiple offered rate counter reads may be performed per the sampling interval. The system accumulates these counter values and evaluates the delta at the conclusion of the sampling interval. When fast-start is enabled, the system identifies all children associated with the policy that enter the inactive state (current offered rate is zero). Any inactive 'fast start’ child that has a positive offered counter during a sampling period bypasses the normal sampling interval and does an immediate offered rate evaluation.
This option is intended for use with children that would benefit from faster than normal startup detection, typically those of a real-time nature.
When this parameter is not enabled, the system uses the normal sampling interval behavior of both newly active and currently active children.
The no form of this command is used to restore the sampling-interval-based offered rate evaluation for newly active children.
Platforms
All
fast-stop
fast-stop
Syntax
[no] fast-stop
Context
[Tree] (config>qos>adv-config-policy>child-control>offered-measurement fast-stop)
Full Context
configure qos adv-config-policy child-control offered-measurement fast-stop
Description
This command is used to enable fast detection of lack of offered rate on a child policer or queue associated with the policy. Multiple offered rate counter reads may be performed per sampling interval. The system accumulates these counter values and evaluates the delta at the conclusion of the sampling interval. When fast-stop is enabled, the system bypasses the sampling interval for any currently active 'fast stop’ child that has a zero offered counter measurement and does an immediate offered rate evaluation using the zero value.
This option is intended for use with children where other children would benefit from faster than normal inactive detection, typically those of a real-time nature.
When this parameter is not enabled, the system uses the normal sampling interval behavior of both newly inactive and currently active children.
The no form of this command is used to restore the sampling-interval-based offered rate evaluation for newly inactive children.
Platforms
All
fate-sharing-group-template
fate-sharing-group-template
Syntax
fate-sharing-group-template name [create]
no fate-sharing-group-template name
Context
[Tree] (config>subscr-mgmt>up-resiliency fate-sharing-group-template)
Full Context
configure subscriber-mgmt up-resiliency fate-sharing-group-template
Description
This command creates a template that configures resiliency parameters per FSG.
The no form of this command deletes the template.
Parameters
- name
-
Specifies the FSG template ID, up to 32 characters.
- create
-
Keyword used to create a template. The create keyword requirement can be disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fault-propagation-bmac
fault-propagation-bmac
Syntax
fault-propagation-bmac [mac-name | ieee-address] [ create]
no fault-propagation-bmac [mac-name | ieee-address]
Context
[Tree] (config>service>vpls>mesh-sdp fault-propagation-bmac)
[Tree] (config>service>vpls>sap fault-propagation-bmac)
[Tree] (config>service>vpls>spoke-sdp fault-propagation-bmac)
Full Context
configure service vpls mesh-sdp fault-propagation-bmac
configure service vpls sap fault-propagation-bmac
configure service vpls spoke-sdp fault-propagation-bmac
Description
This command configures associated B-MAC addresses for fault propagation on a B-VPLS SAP or SDP binding. The statement can appear up to four times in the configuration to support four remote B-MAC addresses in the same remote B-VPLS. The configured VPLS must be a B-VPLS.
The no form of this command removes the specified MAC name or MAC address from the list of Fault Propagation B-MAC addresses associated with the SAP (or SDP).
Parameters
- mac-name
-
Specifies a (predefined) MAC name to associate with the SAP or SDP, indirectly specifying a Fault Propagation B-MAC address. Up to 32 characters in length
- ieee-address
-
Specifies a MAC address to associate with the SAP or SDP, directly specifying a Fault Propagation B-MAC address. The value should be input in either a xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx format.
Platforms
All
fault-propagation-enable
fault-propagation-enable
Syntax
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context
[Tree] (config>service>ipipe>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>epipe>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep fault-propagation-enable)
Full Context
configure service ipipe sap eth-cfm mep fault-propagation-enable
configure service epipe sap eth-cfm mep fault-propagation-enable
configure service epipe spoke-sdp eth-cfm mep fault-propagation-enable
Description
This command configures the fault propagation for the MEP.
Parameters
- use-if-tlv
-
Specifies to use the interface TLV.
- suspend-ccm
-
Specifies to suspend continuity check messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fault-propagation-enable
Syntax
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context
[Tree] (config>service>vpls>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep fault-propagation-enable)
Full Context
configure service vpls sap eth-cfm mep fault-propagation-enable
configure service vpls spoke-sdp eth-cfm mep fault-propagation-enable
configure service vpls mesh-sdp eth-cfm mep fault-propagation-enable
Description
This command configures the fault propagation for the MEP.
Parameters
- use-if-tlv
-
Specifies to use the interface TLV.
- suspend-ccm
-
Specifies to suspend the continuity check messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fault-propagation-enable
Syntax
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>ies>if>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep fault-propagation-enable)
Full Context
configure service ies subscriber-interface group-interface sap eth-cfm mep fault-propagation-enable
configure service ies interface sap eth-cfm mep fault-propagation-enable
configure service ies interface spoke-sdp eth-cfm mep fault-propagation-enable
Description
This command configures the fault propagation for the MEP.
Parameters
- use-if-tlv
-
Specifies to use the interface TLV.
- suspend-ccm
-
Specifies to suspend the continuity check messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep fault-propagation-enable
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface sap eth-cfm mep fault-propagation-enable
- configure service ies interface spoke-sdp eth-cfm mep fault-propagation-enable
fault-propagation-enable
Syntax
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context
[Tree] (config>service>vprn>if>sap>eth-cfm>mep fault-propagation-enable)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm fault-propagation-enable)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep fault-propagation-enable)
Full Context
configure service vprn interface sap eth-cfm mep fault-propagation-enable
configure service vprn subscriber-interface group-interface sap eth-cfm fault-propagation-enable
configure service vprn interface spoke-sdp eth-cfm mep fault-propagation-enable
Description
This command configures the fault propagation for the MEP.
Parameters
- use-if-tlv
-
Specifies to use the interface TLV.
- suspend-ccm
-
Specifies to suspend the continuity check messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface spoke-sdp eth-cfm mep fault-propagation-enable
- configure service vprn interface sap eth-cfm mep fault-propagation-enable
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm fault-propagation-enable
fc
fc
Syntax
fc fc-name [fc-name]
no fc
Context
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>ipipe>sap>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>epipe>sap>eth-cfm>collect-lmm-fc-stats fc)
Full Context
configure service epipe spoke-sdp eth-cfm collect-lmm-fc-stats fc
configure service ipipe sap eth-cfm collect-lmm-fc-stats fc
configure service epipe sap eth-cfm collect-lmm-fc-stats fc
Description
This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-unaware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc fc-name [fc-name]
no fc
Context
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>vpls>sap>eth-cfm>collect-lmm-fc-stats fc)
Full Context
configure service vpls spoke-sdp eth-cfm collect-lmm-fc-stats fc
configure service vpls mesh-sdp eth-cfm collect-lmm-fc-stats fc
configure service vpls sap eth-cfm collect-lmm-fc-stats fc
Description
This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc
Parameters
- fc-name
-
Specifies up to eight names of the FC for which to create an individual profile-unaware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc fc-name [fc-name]
no fc
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>ies>if>sap>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)
Full Context
configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc
configure service ies interface sap eth-cfm collect-lmm-fc-stats fc
configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats fc
Description
This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-unaware counter. Up to eight FCs may be specified. In order for the counter to be used, the config>oam-pm>session>ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats fc
- configure service ies interface sap eth-cfm collect-lmm-fc-stats fc
fc
Syntax
fc fc-name [fc-name]
no fc
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)
[Tree] (config>service>vprn>if>sap>eth-cfm>collect-lmm-fc-stats fc)
Full Context
configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc
configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats fc
configure service vprn interface sap eth-cfm collect-lmm-fc-stats fc
Description
This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-unaware counter. Up to 8 FCs can be named in a single statement. In order for the counter to be used, the config>oam-pm>session>ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats fc
- configure service vprn interface sap eth-cfm collect-lmm-fc-stats fc
fc
Syntax
fc {be | l2 | af | l1 | h2 | ef | h1| nc} forwarding-set set-id
no {be | l2 | af | l1 | h2 | ef | h1 | nc}
Context
[Tree] (config>router>mpls>class-forwarding-policy fc)
Full Context
configure router mpls class-forwarding-policy fc
Description
This command configures the mapping of FCs to up to six forwarding sets for the class-based forwarding (CBF) of an LDP FEC or a BGP prefix over IGP shortcuts.
All FCs are mapped to set 1 as soon as the policy is created. The user can then make changes to the mapping of FCs as required. An FC that is not added to the class forwarding policy is thus always mapped to set 1. An FC can only be mapped to one forwarding set. One or more FCs can map to the same set. The user can indicate the initial default set by including the default-set option.
The default forwarding set forwards packets of an FC when all LSPs of the forwarding set that the FC maps to become operationally down. The router uses the user-configured default set as the initial default set if no default is configured; otherwise, it elects the lowest numbered set as the default forwarding set in a class forwarding policy. When the last LSP in a default forwarding set goes into an operationally down state, the router designates the next lowest numbered set as the new default forwarding set.
Parameters
- {be | l2 | af | l1 | h2 | ef | h1 | nc}
-
Specifies the name of the forwarding class.
- set-id
-
Specifies the class forwarding set.
Platforms
All
fc
Syntax
fc fc-name sampling-weight sampling-weight
no fc
Context
[Tree] (config>router>mpls>lsp-template>auto-bandwidth fc)
Full Context
configure router mpls lsp-template auto-bandwidth fc
Description
This command configures the sampling weight.
Platforms
All
fc
Syntax
fc fc-name class-type ct-number
no fc fc-name
Context
[Tree] (config>router>rsvp>diffserv-te fc)
Full Context
configure router rsvp diffserv-te fc
Description
This command maps one or more system forwarding classes to a Diff-Serv Class Type (CT). The default mapping is shown in Forwarding Classes Mapping.
FC ID |
FC Name |
FC Designation |
Class Type (CT) |
---|---|---|---|
7 |
Network Control |
NC |
7 |
6 |
High-1 |
H1 |
6 |
5 |
Expedited |
EF |
5 |
4 |
High-2 |
H2 |
4 |
3 |
Low-1 |
L1 |
3 |
2 |
Assured |
AF |
2 |
1 |
Low-2 |
L2 |
1 |
0 |
Best Effort |
BE |
0 |
The no form of this command reverts to the default mapping for the forwarding class name.
Parameters
- class-type ct-number
-
The Diff-Serv Class Type number. One or more system forwarding classes can be mapped to a CT.
Platforms
All
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action>remark fc)
Full Context
configure application-assurance group policy app-qos-policy entry action remark fc
Description
This command configures remark FC action on flows matching this AQP entry. When enabled, all packets for all flows matching this AQP entry will be remarked to the configured forwarding class.
The no form of this command stops FC remarking action on packets belonging to flows matching this AQP entry.
Default
no fc
Parameters
- fc-name
-
Configure the FC remark action for flows matching this entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
fc
Syntax
[no] fc fc-name
Context
[Tree] (config>service>nat>nat-policy>priority-sessions fc)
[Tree] (config>service>nat>firewall-policy>priority-sessions fc)
[Tree] (config>service>nat>up-nat-policy>priority-sessions fc)
Full Context
configure service nat nat-policy priority-sessions fc
configure service nat firewall-policy priority-sessions fc
configure service nat up-nat-policy priority-sessions fc
Description
This command configures the forwarding classes that have their sessions prioritized.
Parameters
- fc-name
-
Specifies the forwarding class.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy priority-sessions fc
- configure service nat up-nat-policy priority-sessions fc
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy priority-sessions fc
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>mirror>mirror-dest fc)
Full Context
configure mirror mirror-dest fc
Description
This command specifies a forwarding class for all mirrored packets transmitted to the destination SAP or SDP overriding the default (be) forwarding class. All packets are sent with the same class of service to minimize out-of-sequence issues. The mirrored packet does not inherit the forwarding class of the original packet.
When the destination is on a SAP, a single egress queue is created that pulls buffers from the buffer pool associated with the fc-name.
When the destination is on an SDP, the fc-name defines the DiffServ-based egress queue that is used to reach the destination. The fc-name also defines the encoded forwarding class of the encapsulation.
The FC configuration also affects how mirrored packets are treated at the ingress queuing point on the line cards. One ingress queue is used per mirror destination (service) and that is an expedited queue if the configured FC is expedited (one of nc, h1, ef or h2). The ingress mirror queues have no CIR, but a line-rate PIR.
The no form of this command reverts the mirror-dest service ID forwarding class to the default forwarding class.
Default
The best effort (be) forwarding class is associated with the mirror-dest service ID.
Parameters
- fc-name
-
The name of the forwarding class with which to associate mirrored service traffic. The forwarding class name must already be defined within the system. If the fc-name does not exist, an error is returned and the fc command has no effect. If the fc-name does exist, the forwarding class associated with fc-name overrides the default forwarding class.
Platforms
All
fc
Syntax
fc fc-name [profile { in | out}]
no fc
Context
[Tree] (config>test-oam>ldp-treetrace fc)
Full Context
configure test-oam ldp-treetrace fc
Description
This command indicates the forwarding class and profile of the MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified FC and profile parameter values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, The FC and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the FC and profile parameter values determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The ToS byte is not modified. fc Request Packet and Behavior summarizes this behavior.
CPM (sender node) |
Echo request packet:
|
Outgoing interface (sender node) |
Echo request packet:
|
Incoming interface (responder node) |
Echo request packet:
|
CPM (responder node) |
Echo reply packet:
|
Outgoing interface (responder node) |
Echo reply packet:
|
Incoming interface (sender node) |
Echo reply packet:
|
Default
no fc
Parameters
- fc-name
-
Specifies the forwarding class of the MPLS echo request packets.
- profile {in | out}
-
Specifies the profile value to be used with the forwarding class specified in the fc-name parameter.
Platforms
All
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>saa>test>type-multi-line>lsp-ping>sr-policy fc)
[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy fc)
[Tree] (config>saa>test>type-multi-line>lsp-ping fc)
Full Context
configure saa test type-multi-line lsp-ping sr-policy fc
configure saa test type-multi-line lsp-trace sr-policy fc
configure saa test type-multi-line lsp-ping fc
Description
This command specifies the FC and profile parameters that are used to indicate the forwarding class and profile of the MPLS echo request packet.
The no form of this command reverts to the default value.
Default
fc be
Parameters
- fc-name
-
Specifies the forwarding class name.
Platforms
All
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>oam-pm>session>ip fc)
Full Context
configure oam-pm session ip fc
Description
This command sets the forwarding class designation for TWAMP Light packets that are sent through the node and exposed to the various QoS functions on the network element.
The no form of this command restores the default value.
Default
fc be
Parameters
- fc-name
-
Specifies the forwarding class name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>oam-pm>session>mpls fc)
Full Context
configure oam-pm session mpls fc
Description
This command sets the forwarding class designation for DM packets sent through the node and exposed to the various QoS functions on the network element.
The no form of this command reverts the default value.
Default
fc be
Parameters
- fc-name
-
Specifies the forwarding class name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc fc-name profile profile [create]
no fc fc-name profile profile
Context
[Tree] (config>qos>post-policer-mapping fc)
Full Context
configure qos post-policer-mapping fc
Description
This command specifies the forwarding class and profile state of an egress policed packet that is to be mapped to another forwarding class and profile, where the profile state is that of the resulting profile after the packet has been processed by the egress policer.
The new forwarding class and profile state is configured using the maps-to command.
The traffic remarking is based on the marking configured for the forwarding class and profile of the traffic after being policed but before it is remapped.
The no form of this command deletes the forwarding class and profile remapping statement, including the maps-to command.
Parameters
- fc-name
-
Specifies one of the eight forwarding classes supported by the system.
- profile
-
Specifies one of the egress packet profile states.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
fc
Syntax
fc fc-name [create]
no fc fc-name
Context
[Tree] (config>qos>sap-ingress fc)
Full Context
configure qos sap-ingress fc
Description
The fc command creates a class or subclass instance of the forwarding class fc-name. When the fc-name is created, classification actions can be applied and the subclass can be used in match classification criteria. Attempting to use an undefined subclass in a classification command will result in an execution error and the command will fail.
The no form of this command removes all the explicit queue mappings for fc-name forwarding types. The queue mappings revert to the default queues for fc-name. To successfully remove a subclass, all associations with the subclass in the classification commands within the policy must first be removed or diverted to another forwarding class or subclass.
Parameters
- fc-name
-
The parameter subclass-name is optional and must be defined using a dot separated notation with a preceding valid system-wide forwarding class name. Creating a subclass follows normal naming conventions. Up to sixteen ASCII characters may be used. If the same sub-name is used with two or more forwarding class names, each is considered a different instance of subclass. A subclass must always be specified with its preceding forwarding class name. When a forwarding class is created or specified without the optional subclass, the parent forwarding class is assumed.
Within the SAP ingress QoS policy, up to 56 subclasses may be created. Each of the 56 subclasses may be created within any of the eight parental forwarding classes. When the limit of 56 is reached, any further subclass creations will fail and the subclass will not exist.
Successfully creating a subclass places the CLI within the context of the subclass for further subclass parameter definitions. Within the subclass context, commands may be executed that define subclass priority (within the parent forwarding class queue mapping), subclass color aware profile settings, subclass in-profile and out-of-profile precedence or DSCP markings.
The subclass-name parameter is optional and used with the fc-name parameter to define a pre-existing subclass. The fc-name and subclass-name parameters must be separated by a period (.). If subclass-name does not exist in the context of fc-name, an error will occur. If subclass-name is removed using the no fc fc-name.subclass-name force command, the default-fc command will automatically drop the subclass-name and only use fc-name (the parent forwarding class for the subclass) as the forwarding class.
- create
-
Required parameter when creating a SAP QoS ingress policy forwarding class.
Platforms
All
fc
Syntax
fc fc-name [create]
no fc fc-name
Context
[Tree] (config>qos>sap-egress fc)
Full Context
configure qos sap-egress fc
Description
The fc fc-name node within the SAP egress QoS policy is used to contain the explicitly defined queue mapping and dot1p marking commands for fc-name. When the mapping for fc-name points to the default queue and the dot1p marking is not defined, the node for fc-name is not displayed in the show configuration or save configuration output unless the detail option is specified.
The no form of this command removes the explicit queue mapping and dot1p marking commands for fc-name. The queue mapping reverts to the default queue for fc-name and the dot1p marking (if appropriate) uses the default of 0.
Default
no fc
Parameters
- fc-name
-
This parameter specifies that the forwarding class queue mapping or dot1p marking is to be edited. The value given for fc-name must be one of the predefined forwarding classes in the system.
Platforms
All
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>qos>network>ingress fc)
Full Context
configure qos network ingress fc
Description
This command is used to enter the CLI node to configure QoS parameters for the specified forwarding class. The fc command overrides the default parameters for that forwarding class from the values defined in the network default policy.
The no form of this command removes the forwarding class name configuration. The forwarding class reverts to the parameters defined in the default network policy.
Parameters
- fc-name
-
The case-sensitive, system-defined forwarding class name for which policy entries will be created.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>qos>network>egress fc)
Full Context
configure qos network egress fc
Description
This command is used to enter the CLI node to configure QoS parameters for the specified forwarding class. The FC name represents a CLI parent node that contains parameters describing the egress marking criteria of packets flowing through it. This command overrides the default parameters for that forwarding class from the values defined in the network default policy. It can also be used to redirect packets to a policer or queue in a network egress queue group instance.
The no form of this command removes the forwarding class name configuration. The forwarding class reverts to the parameters defined in the default network policy.
Parameters
- fc-name
-
The case-sensitive, system-defined forwarding class name for which policy entries will be created.
Platforms
All
fc
Syntax
fc fc-name [create]
no fc fc-name
Context
[Tree] (config>qos>network-queue fc)
Full Context
configure qos network-queue fc
Description
The fc command is used to enter the forwarding class mapping context for the given fc-name. Each forwarding class maps by default to queues 1 (unicast) and 9 (multipoint).
Parameters
- fc-name
-
A valid forwarding class must be specified as fc-name when the fc command is executed. When the fc fc-name command is successfully executed, the system will enter the specified forwarding class context where the queue queue-id command may be executed.
- create
-
Required parameter when creating an FC node.
Platforms
All
fc
Syntax
fc fc-name [create]
no fc fc-name
Context
[Tree] (cfg>qos>qgrps>egr>qgrp fc)
Full Context
configure qos queue-group-templates egress queue-group fc
Description
The fc command is used to enter the forwarding class mapping context for the given fc-name. Each forwarding class has a default mapping depending on the egress queue group template. The system-created policer-output-queue template contains queues 1 and 2 by default with queue 1 being best-effort and queue 2 expedited. Forwarding classes be, l1, af and l2 all map to queue 1 by default. Forwarding classes h1, ef, h2 and nc all map to queue 2 by default. More queues may be created within the policer-output-queues template and the default forwarding classes may be changed to any defined queue within the template.
When all other user-defined egress queue group templates are created, only queue 1 (best-effort) exists and all forwarding classes are mapped to that queue. Other queues may be created and the forwarding classes may be changed to any defined queue within the template.
Besides the default mappings within the templates, the egress queue group template forwarding class queue mappings operate the same as the forwarding class mappings in a sap-egress QoS policy.
The template forwarding class mappings are the default mechanism for mapping egress policed traffic to a queue within an egress port queue group associated with the template. If a queue-id is explicitly specified in the QoS policy forwarding class policer mapping, and that queue exists within the queue group, the template forwarding class mapping is ignored.
On the 7450 ESS and 7750 SR, egress policed subscriber traffic works in a slightly different way. The subscriber and subscriber host support destination and organization strings are used to identify the egress port queue group. In this instance, the forwarding class mappings are always used and any queue overrides in the QoS policy are ignored. If neither string exists for the subscriber host, the egress queue group queue-id can be derived from either the QoS policy policer mapping or the template forwarding class queue mappings.
The no form of this command is used to return the specified forwarding class to its default template queue mapping.
Parameters
- fc-name
-
A valid forwarding class must be specified as fc-name when the fc command is executed. When the fc fc-name command is successfully executed, the system will enter the specified forwarding class context where the queue queue-id command may be executed.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
fc
Syntax
fc fc-name [create]
no fc
Context
[Tree] (config>qos>shared-queue fc)
Full Context
configure qos shared-queue fc
Description
This command specifies the forwarding class name. The forwarding class name represents an egress queue. The fc fc-name represents a CLI parent node that contains sub-commands or parameters describing the egress characteristics of the queue and the marking criteria of packets flowing through it. The fc command overrides the default parameters for that forwarding class defined in the network default policy policy-id 1.
Default
Refer to "Default Shared Queue Policy Values” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for undefined forwarding class values.
Parameters
- fc-name
-
The case-sensitive, system-defined forwarding class name for which policy entries will be created.
Platforms
All
fc
Syntax
fc fc-name
no fc
Context
[Tree] (config>filter>ip-filter>entry>action fc)
[Tree] (config>filter>ipv6-filter>entry>action fc)
Full Context
configure filter ip-filter entry action fc
configure filter ipv6-filter entry action fc
Description
This command assigns a forwarding class to packets matching the filter entry.
The no version of this command removes the forwarding class marking action.
Parameters
- fc-name
-
Specifies the forwarding class name.
Platforms
All
fc
Syntax
fc fc-name [fc-name]
no fc
Context
[Tree] (config>router>if>eth-cfm>mep>collect-lmm-fc-stats fc)
Full Context
configure router interface eth-cfm mep collect-lmm-fc-stats fc
Description
This command creates individual counters for the specified FCs without regard for profile. All countable packets that match a configured FC, regardless of profile, will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-aware FC using the fc-in-profile command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-unaware counter. A maximum of eight fc-names can be specified in a single statement. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc {fc} lsp lsp-name
no fc {fc}
Context
[Tree] (config>service>sdp>class-forwarding fc)
Full Context
configure service sdp class-forwarding fc
Description
This command makes an explicit association between a forwarding class and an LSP. The LSP name must exist and must have been associated with this SDP using the command config>service>sdp>lsp. Multiple forwarding classes can be associated with the same LSP. However, a forwarding class can only be associated with a single LSP in a given SDP. All subclasses will be assigned to the same LSP as the parent forwarding class.
Parameters
- lsp lsp-name
-
Specifies the RSVP or static LSP to use to forward service packets which are classified into the specified forwarding class.
- fc
-
Specifies a forwarding class to LSP mapping.
Platforms
All
fc
Syntax
fc fc [priority {low | high}]
no fc
Context
[Tree] (config>router>policy-options>policy-statement>entry>action fc)
Full Context
configure router policy-options policy-statement entry action fc
Description
This command associates a forwarding-class and optionally priority with the routes matched by a route policy entry. The command takes effect when the action of the route policy entry is accept, next-entry, or next-policy. It has no effect except in route policies applied as VRF import policies, BGP import policies, or RIP import policies.
The no form of this command removes the QoS association of the routes matched by the route policy entry.
Default
no fc
Parameters
- fc
-
Specify the name of one of the predefined forwarding classes in the system.
- priority {low | high}
-
This parameter associates an enqueuing priority with routes matched by the policy entry. Specifying a priority is optional.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc
Syntax
fc fc-name
Context
[Tree] (config>test-oam>link-meas>template>twl fc)
Full Context
configure test-oam link-measurement measurement-template twamp-light fc
Description
This command configures the FC name for the TWAMP Light packet.
Default
fc h1
Parameters
- fc-name
-
Specifies the forwarding class.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc-in-profile
fc-in-profile
Syntax
fc-in-profile fc-name [fc-name ]
no fc-in-profile
Context
[Tree] (config service epipe spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service epipe sap eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service ipipe sap eth-cfm collect-lmm-fc-stats fc-in-profile)
Full Context
configure service epipe spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
configure service epipe sap eth-cfm collect-lmm-fc-stats fc-in-profile
configure service ipipe sap eth-cfm collect-lmm-fc-stats fc-in-profile
Description
This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in-profile will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc-in-profile
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-aware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc-in-profile
Syntax
fc-in-profile fc-name [fc-name]
no fc-in-profile
Context
[Tree] (config service vpls mesh-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service vpls sap eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service vpls spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)
Full Context
configure service vpls mesh-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
configure service vpls sap eth-cfm collect-lmm-fc-stats fc-in-profile
configure service vpls spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
Description
This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in-profile will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc-in-profile
Parameters
- fc-name
-
Specifies up to eight names of the FC for which to create an individual profile-aware counter. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fc-in-profile
Syntax
fc-in-profile fc-name [fc-name]
no fc-in-profile
Context
[Tree] (config service ies sub-if grp-if sap eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service ies if spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service ies if sap eth-cfm collect-lmm-fc-stats fc-in-profile)
Full Context
configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
configure service ies interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
Description
This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in profile will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc-in-profile
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-aware counter. Up to eight FCs may be specified. In order for the counter to be used, the config>oam-pm>session>ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
- configure service ies interface spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
fc-in-profile
Syntax
fc-in-profile fc-name [fc-name]
no fc-in-profile
Context
[Tree] (config service vprn sub-if grp-if sap eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service vprn if spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)
[Tree] (config service vprn if sap eth-cfm collect-lmm-fc-stats fc-in-profile)
Full Context
configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
configure service vprn interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
Description
This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in profile will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc-in-profile
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-aware counter. Up to 8 FCs can be named in a single statement. In order for the counter to be used, the config>oam-pm>session>ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile
- configure service vprn interface sap eth-cfm collect-lmm-fc-stats fc-in-profile
fc-in-profile
Syntax
fc-in-profile fc-name [fc-name]
no fc-in-profile
Context
[Tree] (config router if eth-cfm mep collect-lmm-fc-stats fc-in-profile)
Full Context
configure router interface eth-cfm mep collect-lmm-fc-stats fc-in-profile
Description
This command creates individual counters for the specified FCs with regard for profile. All countable packets that match a configured FC and are deemed to be in-profile will be included in this counter.
A differential is performed when this command is re-entered. Omitted FCs will stop counting, newly added FCs will start counting, and unchanged FCs will continue to count.
Up to eight FCs may be specified. An FC that is specified as part of this command for this specific context cannot be specified as a profile-unaware FC using the fc command under the same context.
The no form of this command removes all previously defined FCs and stops counting for those FCs.
Default
no fc-in-profile
Parameters
- fc-name
-
Specifies the name of the FC for which to create an individual profile-aware counter. A maximum of eight fc-names can be specified in a single statement. In order for the counter to be used, the config>oam-pm>session> ethernet>priority command must be configured with a numerical value representing the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE), and the config>oam-pm>session>ethernet>lmm>enable-fc-collection command must be enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fcc
fcc
Syntax
fcc percent
Context
[Tree] (config>isa>video-group>watermark>bandwidth fcc)
[Tree] (config>isa>video-group>watermark>session fcc)
Full Context
configure isa video-group watermark bandwidth fcc
configure isa video-group watermark session fcc
Description
This command sets the watermark to trigger the SNMP trap if the FCC bandwidth or session exceeds the configured percentage. The bandwidth is the available egress bandwidth of the ISA. The SNMP trap is cleared when the consumption is lowered by 10%. For example, if the system resource of the available bandwidth is 10 Gb/s and the watermark is configured to be 90%, the SNMP trap is raised as the bandwidth exceeds 9 Gb/s (90% of 10 Gb/s). The SNMP trap is cleared when the bandwidth drops below 8.1 Gb/s (10% of 9 Gb/s = 0.9 Gb/s, and 9 Gb/s - 0.9 Gb/s = 8.1 Gb/s). The default value of the watermark is set at 90% of the system resources for both bandwidth and session.
Default
fcc 90
Parameters
- percent
-
Specifies the percentage of the system resources per ISA.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-burst
fcc-burst
Syntax
fcc-burst burst-percentage
no fcc-burst
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>sd fcc-burst)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>pip fcc-burst)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>hd fcc-burst)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface sd fcc-burst
configure mcast-management multicast-info-policy video-policy video-interface pip fcc-burst
configure mcast-management multicast-info-policy video-policy video-interface hd fcc-burst
Description
This command sets the burst rate at which the Fast Channel Change (FCC) server will send unicast data to the FCC client above the received rate to allow the client to catchup to the multicast stream.
This parameter is only applicable if the FCC server mode is burst.
The no form of the command returns the parameter to the default value.
Default
fcc-burst 25
Parameters
- burst-percentage
-
Specifies the percentage of nominal bandwidth used to catch up to the multicast stream.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-channel-type
fcc-channel-type
Syntax
fcc-channel-type {hd | sd | pip}
no fcc-channel-type
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video fcc-channel-type)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video fcc-channel-type)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video fcc-channel-type)
Full Context
configure mcast-management multicast-info-policy bundle video fcc-channel-type
configure mcast-management multicast-info-policy bundle channel source-override video fcc-channel-type
configure mcast-management multicast-info-policy bundle channel video fcc-channel-type
Description
This command configures the channel type for the bundle/channel. The channel type is used in the video policy to set various Fast Channel Change (FCC) parameters including the type of FCC and various FCC rates.
The no form of this command returns the parameter to the default value.
Default
no fcc-channel-type
Parameters
- hd
-
The channel type is High-Definition (HD) (Default).
- sd
-
The channel type is Standard Definition (SD).
- pip
-
The channel type is Picture in Picture (PIP).
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-min-duration
fcc-min-duration
Syntax
fcc-min-duration time
no fcc-min-duration
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video fcc-min-duration)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video fcc-min-duration)
Full Context
configure mcast-management multicast-info-policy bundle video fcc-min-duration
configure mcast-management multicast-info-policy bundle channel video fcc-min-duration
Description
This command configures the minimum time duration, in milliseconds, of the Fast Channel Change (FCC) burst. The value of this object determines the starting point of the FCC burst. If the current Group of Pictures (GOP) has less than the minimum duration worth of data, FCC burst begins from the previous GOP.
The no form of the command reverts to the default value.
Default
fcc-min-duration 300
Parameters
- time
-
Specifies the FCC burst minimum duration, in milliseconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-server
fcc-server
Syntax
[no] fcc-server
Context
[Tree] (config>isa>video-group fcc-server)
Full Context
configure isa video-group fcc-server
Description
This command enables the FCC server capability for the ISA video group. FCC server cannot be enabled if ad insertion or the local RET server is enabled.
FCC server parameters can be configured in a multicast information policy or a service, but the parameters will have no effect if the FCC server is disabled or if the video group is administratively disabled (shutdown).
The no form of the command disables the FCC server.
Default
no fcc-server
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-server
Syntax
fcc-server [mode {burst | dent | hybrid}]
no fcc-server
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>hd fcc-server)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>pip fcc-server)
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>sd fcc-server)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface hd fcc-server
configure mcast-management multicast-info-policy video-policy video-interface pip fcc-server
configure mcast-management multicast-info-policy video-policy video-interface sd fcc-server
Description
This command enables the Fast Channel Change (FCC) server and sets the mode to send the FCC unicast stream.
The mode indicates how the FCC server will send information to the client. When burst is specified, the FCC server will send the channel at a nominally faster rate than the channel was received based on the applicable fcc-burst setting. When dent is specified, the FCC server will selectively discard frames from the original stream based on the applicable dent-threshold setting. If no mode is specified, burst is the default mode.
The no form of the command disables the FCC server at that context and subordinate contexts.
Default
no fcc-server
Parameters
- mode burst
-
Sets the mode of the FCC server to burst when sending the channel to the FCC client.
- mode dent
-
Sets the mode of the FCC server to dent when sending the channel to the FCC client.
- mode hybrid
-
Combines the burst and dent modes.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-server
Syntax
fcc-server [disable]
no fcc-server
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video fcc-server)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video fcc-server)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video fcc-server)
Full Context
configure mcast-management multicast-info-policy bundle channel video fcc-server
configure mcast-management multicast-info-policy bundle channel source-override video fcc-server
configure mcast-management multicast-info-policy bundle video fcc-server
Description
This command enables Fast Channel Change (FCC) for a multicast bundle or channel. Additional parameters such as fcc-channel-type should also be configured to match the characteristics of the bundle/channel.
The no form of the command disables removes the FCC configuration for the bundle/channel context and implies the setting is inherited from a higher context or the default policy.
Default
no fcc-server
Parameters
- disable
-
Explicitly disables the FCC server within the policy. For the default bundle within the default multicast information policy, the no form of the command and the disable keyword have the same meaning and imply that the server is disabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-server
Syntax
fcc-server [client client-ip [ source-port src-port]]
no fcc-server
Context
[Tree] (debug>service>id>video-interface fcc-server)
Full Context
debug service id video-interface fcc-server
Description
This command enables debugging the FCC server.
Parameters
- client client-ip
-
Specifies the client IP address.
- source-port src-port
-
Specifies the source port’s IP address.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fcc-session-timeout
fcc-session-timeout
Syntax
fcc-session-timeout seconds
no fcc-session-timeout
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if fcc-session-timeout)
Full Context
configure mcast-management multicast-info-policy video-policy video-interface fcc-session-timeout
Description
By default, the video ISA will wait for 5 minutes before closing the RTCP session from the subscriber. The RTCP session can be adjusted from 5 second to 5 minutes. The timeout is applicable to both RET and FCC RTCP sessions.
The no form of the command reverts to the default.
Default
fcc-session-timeout 300
Parameters
- seconds
-
Specifies the FCC session timeout in seconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
fd-avg
fd-avg
Syntax
[no] fd-avg {forward | backward | round-trip}
Context
[Tree] (config>oam-pm>streaming>delay-template fd-avg)
Full Context
configure oam-pm streaming delay-template fd-avg
Description
This command specifies the sending of average frame delay for a specified direction.
The no form of this command deletes the specified average direction.
All directions can be specified if all directions are important for reporting. However, only enable those directions that are required.
Parameters
- forward
-
Specifies the measurement in the forward direction.
- backward
-
Specifies the measurement in the backward direction.
- round-trip
-
Specifies the measurement for the round trip.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fdb-table-high-wmark
fdb-table-high-wmark
Syntax
[no] fdb-table-high-wmark high-water-mark
Context
[Tree] (config>service>template>vpls-template fdb-table-high-wmark)
[Tree] (config>service>vpls fdb-table-high-wmark)
Full Context
configure service template vpls-template fdb-table-high-wmark
configure service vpls fdb-table-high-wmark
Description
This command specifies the value to send logs and traps when the threshold is reached.
The no form of this command reverts to the default value.
Default
fdb-table-high-wmark 95
Parameters
- high-water-mark
-
Specifies the value as a percentage.
Platforms
All
fdb-table-low-wmark
fdb-table-low-wmark
Syntax
[no] fdb-table-low-wmark low-water-mark
Context
[Tree] (config>service>template>vpls-template fdb-table-low-wmark)
[Tree] (config>service>vpls fdb-table-low-wmark)
Full Context
configure service template vpls-template fdb-table-low-wmark
configure service vpls fdb-table-low-wmark
Description
This command specifies the value to send logs and traps when the threshold is reached.
The no form of this command reverts to the default value.
Default
fdb-table-low-wmark 90
Parameters
- low-water-mark
-
Specifies the value as a percentage.
Platforms
All
fdb-table-size
fdb-table-size
Syntax
fdb-table-size table-size
no fdb-table-size [table-size]
Context
[Tree] (config>service>vpls fdb-table-size)
[Tree] (config>service>template>vpls-template fdb-table-size)
Full Context
configure service vpls fdb-table-size
configure service template vpls-template fdb-table-size
Description
This command specifies the maximum number of MAC entries in the forwarding database (FDB) for the VPLS instance on this node.
The fdb-table-size specifies the maximum number of forwarding database entries for both learned and static MAC addresses for the VPLS instance.
The no form of this command returns the maximum FDB table size to default.
Default
fdb-table-size 250
Parameters
- table-size
-
Specifies the number of entries permitted in the forwarding database for this VPLS instance.
Platforms
All
fdb-table-size
Syntax
fdb-table-size table-size
no fdb-table-size
Context
[Tree] (config>service>system fdb-table-size)
Full Context
configure service system fdb-table-size
Description
This command configures the maximum system FDB table size, which is dependent on the chassis type. CPMs with at least 16 GB of memory are required when exceeding 500k MAC addresses in a system. The table size cannot be reduced below its default value, which is also chassis-dependent.
The maximum system FDB table size also limits the maximum FDB table size of any card within the system.
The no version of this command sets the table size to its default.
The command default depends on the chassis type and available memory.
Parameters
- table-size
-
Specifies the maximum system FDB table size.
Platforms
All
feac-loop-respond
feac-loop-respond
Syntax
[no] feac-loop-respond
Context
[Tree] (config>port>tdm>ds3 feac-loop-respond)
Full Context
configure port tdm ds3 feac-loop-respond
Description
This command enables the associated DS-3 interface to respond to remote loop signals.
The DS-3 far-end alarm and control (FEAC) signal is used to send alarm or status information from the far-end terminal back to the local terminal. DS-3 loopbacks at the far-end terminal from the local terminal are initiated.
The no form of this command prevents the associated DS-3 interface from responding to remote loop signals.
Default
no feac-loop-respond
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
feature
feature
Syntax
[no] feature feature-name
Context
[Tree] (config>system>satellite>eth-sat feature)
Full Context
configure system satellite eth-sat feature
Description
This command enables specific satellite functionality that may have specific satellite requirements, such as software version.
The no form of this command disables the specific satellite functionality.
Parameters
- feature-name
-
Specifies the functionality to enable.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
features
features
Syntax
features
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gx features)
Full Context
configure subscriber-mgmt diameter-application-policy gx features
Description
Commands in this context configure the Gx features.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fec
fec
Syntax
fec {g709 | enhanced}
no fec
Context
[Tree] (config>port>otu fec)
Full Context
configure port otu fec
Description
This command enables the Forwarding Error Correction (FEC) encoder/decoder and specifies the FEC encoder/decoder mode to use when enabled.
The following rules must be followed:
-
The port’s OTU must be enabled to set or change the FEC mode.
-
The port must be shut down before changing the FEC mode.
-
The sf-sd-method must be changed to BIP8 before setting the FEC mode to disabled.
Note that FEC cannot be disabled on OTU3 encapsulated OC768 or 40-Gigabit Ethernet by the no fec command. Therefore, the default depends on the port type. The default for OTU3 encapsulated OC768 or 40-Gigabit Ethernet is fec enhanced.
The no form of this command disables FEC encoder and decoder.
Default
no fec
Parameters
- enhanced
-
Enables the FEC encoder and decoder with a proprietary enhanced FEC algorithm.
- g709
-
Enables the FEC encoder and decoder with the standard G.709 FEC algorithm.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fec-limit
fec-limit
Syntax
fec-limit limit [log-only] [threshold percentage]
no fec-limit
Context
[Tree] (config>router>ldp>session-params>peer fec-limit)
Full Context
configure router ldp session-parameters peer fec-limit
Description
This command configures a limit on the number of FECs which an LSR will accept from a given peer and add into the LDP label database. The limit applies to the aggregate count of all FEC types including service FEC. Once the limit is reached, any FEC received will be released back to the peer. This behavior is different from the per-peer import policy which will still accept the FEC into the label database but will not resolve it.
When the FEC limit for a peer is reached, the LSR performs the following actions:
-
Generates a trap and a syslog message.
-
Generates a LDP notification message with the LSR overload status TLV, for each LDP FEC type including service FEC, to this peer only if this peer advertised support for the LSR overload sub-TLV via the LSR Overload Protection Capability TLV at session initialization.
-
Releases, with LDP Status Code of "No_Label_Resources", any new FEC, including service FEC, from this peer which exceeds the limit.
If a legitimate FEC is released back to a peer, while the FEC limit was exceeded, the user must have a means to replay that FEC back to the router LSR once the condition clears. This is done automatically if the peer is an SR OS-based router and supports the LDP overload status TLV ( SR OS 11.0R5 and higher). Third-party peer implementations must support the LDP overload status TLV or provide a manual command to replay the FEC.
The threshold option allows to set a threshold value when a trap and an syslog message are generated as a warning to the user in addition to when the limit is reached. The default value for the threshold when not configured is 90%.
The log-only option causes a trap and syslog message to be generated when reaching the threshold and limit. However, LDP labels are not released back to the peer.
If the user decreases the limit value such that it is lower than the current number of FECs accepted from the peer, the LDP LSR raises the trap for exceeding the limit. In addition, it will set overload for peers which signaled support for LDP overload protection capability TLV. However, no existing resolved FECs from the peer which does not support the overload protection capability TLV should be de-programmed or released.
A different trap is released when crossing the threshold in the upward direction, when reaching the FEC limit, and when crossing the threshold in the downward direction. However the same trap will not be generated more often than 2 minutes apart if the number of FECs oscillates around the threshold or the FEC limit.
Default
no fec-limit
Parameters
- limit
-
Specifies the aggregate count of FECs of all types which can be accepted from this LDP peer.
- log-only
-
Specifies that only a trap and syslog message are generated when reaching the threshold and limit. However, LDP labels are not released back to the peer.
- percentage
-
Specifies the threshold value (as a percentage) that triggers a warning syslog message and trap to be sent.
Platforms
All
fec-originate
fec-originate
Syntax
fec-originate ip-prefix/mask [advertised-label in-label] [swap-label out-label] interface interface-name
fec-originate ip-prefix/mask [advertised-label in-label] next-hop ip-address [swap-label out-label]
fec-originate ip-prefix/mask [advertised-label in-label] next-hop ip-address [swap-label out-label] interface interface-name
fec-originate ip-prefix/mask [advertised-label in-label] pop
no fec-originate ip-prefix/mask interface interface-name
no fec-originate ip-prefix/mask next-hop ip-address
no fec-originate ip-prefix/mask next-hop ip-address interface interface-name
no fec-originate ip-prefix/mask pop
Context
[Tree] (config>router>ldp fec-originate)
Full Context
configure router ldp fec-originate
Description
This command defines a way to originate a FEC (with a swap action) for which the LSR is not egress, or to originate a FEC (with a pop action) for which the LSR is egress.
Parameters
- ip-prefix/mask
-
Specifies information for the specified IP prefix and mask length.
- next-hop
-
Specifies the IP address of the next hop of the prefix.
- advertised-label
-
Specifies the label advertised to the upstream peer. If not configured, then the label advertised should be from the label pool. If the configured static label is not available then the IP prefix is not advertised.
- out-label
-
Specifies the LSR to swap the label. If configured, then the LSR should swap the label with the configured swap-label. If not configured, then the default action is pop if the next-hop parameter is not defined.
The next-hop, advertised-label, swap-label parameters are all optional. If next-hop is configured but no swap label specified, it will be a swap with label 3, such as, pop and forward to the next-hop. If the next-hop and swap-label are configured, then it is a regular swap. If no parameters are specified, a pop and route is performed.
- in-label
-
Specifies the number of labels to send to the peer associated with this FEC.
- pop
-
Specifies to pop the label and transmit without the label.
- interface interface-name
-
Specifies the name of the interface the label for the originated FEC is swapped to. For an unnumbered interface, this parameter is mandatory since there is no address for the next-hop. For a numbered interface, it is optional.
Platforms
All
fec-prefix
fec-prefix
Syntax
[no] fec-prefix ip-prefix[mask]
Context
[Tree] (config>router>ldp>egr-stats fec-prefix)
Full Context
configure router ldp egress-statistics fec-prefix
Description
This command configures statistics in the egress data path at the ingress LER or LSR for an LDP FEC. The user must execute the no shutdown command for this command to effectively enable statistics. The egress data path counters will be updated for both originating and transit packets. Originating packets may be service packets or IP user and control packets forwarded over the LDP LSP when used as an IGP shortcut. Transit packets of the FEC which are label switched on this node.
When ECMP is enabled and multiple paths exist for a FEC, the same set of counters are updated for each packet forwarded over any of the NHLFEs associated with this FEC and for as long as this FEC is active.
The statistics can be enabled on prefix FECs imported from both LDP neighbors and T-LDP neighbors (LDP over RSVP). LDP sets up egress statistics collection for the LDP tunnels whose FECs match the exact prefix specified in this command. Service FECs, that is, FEC 128 and FEC 129, are not valid. LDP FEC egress statistics are collected at the Penultimate-Popping Hop (PHP) node for a LDP FEC using an implicit null egress label.
The no form of this command disables the statistics in the egress data path and removes the accounting policy association from the LDP FEC.
Parameters
- ip-prefix
-
Specifies the IP address representing the FEC.
- mask
-
Specifies the mask of the IP address.
Platforms
All
fec-type-capability
fec-type-capability
Syntax
fec-type-capability
Context
[Tree] (config>router>ldp>if-params>if>ipv6 fec-type-capability)
[Tree] (config>router>ldp>if-params>if>ipv4 fec-type-capability)
[Tree] (config>router>ldp>session-params>peer fec-type-capability)
Full Context
configure router ldp interface-parameters interface ipv6 fec-type-capability
configure router ldp interface-parameters interface ipv4 fec-type-capability
configure router ldp session-parameters peer fec-type-capability
Description
This command enables or disables the advertisement of a FEC type on a given LDP session or Hello adjacency to a peer.
Platforms
All
fec129-cisco-interop
fec129-cisco-interop
Syntax
[no] fec129-cisco-interop
Context
[Tree] (config>router>ldp>session-params>peer fec129-cisco-interop)
Full Context
configure router ldp session-parameters peer fec129-cisco-interop
Description
This command specifies whether LDP will provide translation between non-compliant FEC 129 formats of Cisco. Peer LDP sessions must be manually configured towards the non-compliant Cisco PEs.
When enabled, Cisco non-compliant format will be used to send and interpret received label release messages that is the FEC129 SAII and TAII fields will be reversed.
When the disabled, Cisco non-compliant format will not be used or supported. Peer address has to be the peer LSR-ID address.
The no form of this command returns the default.
Default
no fec129-cisco-interop
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fib-priority
fib-priority
Syntax
fib-priority {high | standard}
Context
[Tree] (config>service>vprn fib-priority)
Full Context
configure service vprn fib-priority
Description
This command specifies the FIB priority for VPRN BGP routes.
Parameters
- high
-
Specifies high FIB priority for VPRN.
- standard
-
Specifies standard FIB priority for VPRN.
Platforms
All
fib-priority
Syntax
fib-priority {high | standard}
Context
[Tree] (config>router fib-priority)
Full Context
configure router fib-priority
Description
This command specifies the FIB priority for VPRN BGP routes.
Default
fib-priority standard
Parameters
- high
-
Specifies the high FIB priority.
- standard
-
Specifies the standard FIB priority.
Platforms
All
fib-telemetry
fib-telemetry
Syntax
[no] fib-telemetry
Context
[Tree] (config>router fib-telemetry)
Full Context
configure router fib-telemetry
Description
This command enables the collection of extra state information related to the forwarding table state of certain IP routes, TTM tunnels, and MPLS LFIB entries. This extra state can be retrieved by gNMI telemetry subscriptions targeted to the following YANG paths:
-
/state/router/route-fib
-
/state/router/tunnel-fib
-
/state/router/label-fib
If this command is not configured, no information is displayed by the following show commands:
-
show>router>fib-telemetry>route
-
show>router>fib-telemetry>tunnel
The no form of this command disables the collection of this extra state.
Default
no fib-telemetry
Platforms
All
field
field
Syntax
[no] field field-name
Context
[Tree] (config>app-assure>group>cflowd>volume>template>dynamic-fields field)
[Tree] (config>app-assure>group>cflowd>tcp-perf>template>dynamic-fields field)
[Tree] (config>app-assure>group>cflowd>rtp-perf>video-template>dynamic-fields field)
[Tree] (config>app-assure>group>cflowd>comp>template>dynamic-fields field)
[Tree] (config>app-assure>group>cflowd>rtp-perf>voice-template>dynamic-fields field)
[Tree] (config>app-assure>group>cflowd>rtp-perf>audio-template>dynamic-fields field)
Full Context
configure application-assurance group cflowd volume template dynamic-fields field
configure application-assurance group cflowd tcp-performance template dynamic-fields field
configure application-assurance group cflowd rtp-performance video-template dynamic-fields field
configure application-assurance group cflowd comprehensive template dynamic-fields field
configure application-assurance group cflowd rtp-performance voice-template dynamic-fields field
configure application-assurance group cflowd rtp-performance audio-template dynamic-fields field
Description
This command specifies which fields to include in the exported cflowd template.
Certain fields, such as source and destination IP addresses, are always included in the exported template, so they are not optional.
The no form of this command removes the specified field from the template.
Parameters
- field-name
-
Specifies the name of the field to include in the exported cflowd template, up to 256 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
field
Syntax
[no] field field-name
Context
[Tree] (config>app-assure>group>http-enrich field)
Full Context
configure application-assurance group http-enrich field
Description
This command specifies the fields to insert into the HTTP header. The command must be repeated for each field to be inserted. The same field cannot be inserted twice into the header under different header names.
AA can insert two copies of the following fields in the same HTTP header (with a different header name): imei-hyphenated, imei-hyphenated-2, imsi, imsi-2, static-string, static-string-2, user-location-raw, and user-location-raw2.
The no form of this command removes the specified field so that it is not inserted into the HTTP header.
Parameters
- field-name
-
Specifies the fields to insert into the HTTP header.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
field-override
field-override
Syntax
field-override
Context
[Tree] (debug>oam>build-packet>packet field-override)
Full Context
debug oam build-packet packet field-override
Description
Commands in this context configure an override value for a field within a header within a packet to be launched by the OAM find-egress tool.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
field-selection
field-selection
Syntax
field-selection field-selection
no field-selection
Context
[Tree] (config>app-assure>group>cflowd>volume>template field-selection)
[Tree] (config>app-assure>group>cflowd>rtp-perf>audio-template field-selection)
[Tree] (config>app-assure>group>cflowd>rtp-perf>voice-template field-selection)
[Tree] (config>app-assure>group>cflowd>rtp-perf>video-template field-selection)
[Tree] (config>app-assure>group>cflowd>comp>template field-selection)
[Tree] (config>app-assure>group>cflowd>tcp-perf>template field-selection)
Full Context
configure application-assurance group cflowd volume template field-selection
configure application-assurance group cflowd rtp-performance audio-template field-selection
configure application-assurance group cflowd rtp-performance voice-template field-selection
configure application-assurance group cflowd rtp-performance video-template field-selection
configure application-assurance group cflowd comprehensive template field-selection
configure application-assurance group cflowd tcp-performance template field-selection
Description
This command configures how fields included in the exported cflowd template are selected.
The no form of this command reverts to the legacy field selection type.
Default
field-selection legacy
Parameters
- field-selection
-
Specifies how fields are selected.
legacy
Specifies that the fields within the cflowd template are set and fixed and as per SR OS release 17 (or earlier).
dynamic
Specifies that the operator can select which fields are included in the cflowd template.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
file
file
Syntax
file file-url
no file
Context
[Tree] (config>app-assure>group>url-list file)
Full Context
configure application-assurance group url-list file
Description
This command specifies the file for the URL list.
The no form of this command removes the url-list object.
Default
no file
Parameters
- file-url
-
Specifies the flash ID or file path.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
file
Syntax
file
Context
[Tree] (file)
Full Context
file
Description
Specifies the context to enter and perform file system operations. When entering the file context, the prompt changes to reflect the present working directory. Navigating the file system with the cd .. command results in a changed prompt.
The exit all command leaves the file system/file operation context and returns to the operational root CLI context. The state of the present working directory is maintained for the CLI session. Entering the file command returns the cursor to the working directory where the exit command was issued.
Platforms
All
file-id
file-id
Syntax
[no] file-id file-id [ name file-policy-name]
Context
[Tree] (config>log file-id)
Full Context
configure log file-id
Description
This command creates the context to configure a file policy that is used as the destination for an event log or billing (accounting) file.
This command defines the file location and characteristics that are to be used as the destination for a log event message stream or accounting/billing information. The file defined in this context is subsequently specified in the to command under log-id or accounting-policy to direct specific logging or billing source streams to the file destination.
A file policy can only be assigned to either one log-id or one accounting-policy. It cannot be reused for multiple instances. A file policy and associated file definition must exist for each log and billing file that must be stored in the file system.
A file is created when the file policy defined in this command is selected as the destination type for a specific log or accounting record. Log files are collected in a "log” directory. Accounting files are collected in an "act” directory.
The file names for a log are created by the system as summarized in Log File Names.
File Type |
File Name |
---|---|
Log File |
logllff-timestamp |
Accounting File |
actaaff-timestamp |
Where:
-
ll is the log-id
-
aa is the accounting policy-id
-
ff is the file-id
-
The timestamp is the actual timestamp when the file is created. The format for the timestamp is yyyymmdd-hhmmss where:
-
yyyy is the year (for example, 2006)
-
mm is the month number (for example, 12 for December)
-
dd is the day of the month (for example, 03 for the 3rd of the month)
-
hh is the hour of the day in 24 hour format (for example, 04 for 4 a.m.)
-
mm is the minutes (for example, 30 for 30 minutes past the hour)
-
ss is the number of seconds (for example, 14 for 14 seconds)
-
-
The accounting file is compressed and has a gz extension.
When initialized, each file contains:
-
The log-id description.
-
The time the file was opened.
-
The reason the file was created.
-
If the event log file was closed properly, the sequence number of the last event stored on the log is recorded.
If the process of writing to a log file fails (for example, the compact flash card is full) and if a backup location is not specified or fails, the log file will not become operational even if the compact flash card is replaced. Enter either a clear log command or a shutdown/no shutdown command to reinitialize the file.
If the primary location fails (for example, the compact flash card fills up during the write process), a trap is sent and logging continues to the specified backup location. This can result in truncated files in different locations.
The no form of this command removes the file policy from the configuration. A file policy can only be removed from the configuration if the policy is not the designated output for a log destination. The actual log or accounting file remain on the file system when a file policy is deleted.
Parameters
- file-id
-
The file identification number for the file policy, expressed as a decimal integer.
- name file-policy-name
-
Configures an optional file policy name, up to 64 characters, that can be used to refer to the file policy after it is created. If the name begins with a numerical digit (from 1 to 9), the name is a number from 1 to 99.
Platforms
All
file-storage-control
file-storage-control
Syntax
file-storage-control
Context
[Tree] (config>log file-storage-control)
Full Context
configure log file-storage-control
Description
Commands in this context configure the total size limit of log and accounting files on each storage device on the active CPM.
Platforms
All
file-transfer
file-transfer
Syntax
file-transfer file-transfer-mode [file-transfer-mode]
no file-transfer
Context
[Tree] (config>system>satellite file-transfer)
Full Context
configure system satellite file-transfer
Description
This command specifies the file transfer protocol to use between the 7750 SR or 7950 XRS host and 7210 SAS Ethernet satellite.
The no form of this command reverts to the default value.
Default
file-transfer ftp
Parameters
- file-transfer-mode
-
Specifies up to two satellite secure file transfer protocols.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
file-transmission-profile
file-transmission-profile
Syntax
file-transmission-profile name [create]
no file-transmission-profile
Context
[Tree] (config>system file-transmission-profile)
Full Context
configure system file-transmission-profile
Description
This command creates a new file transmission profile or enters the configuration context of an existing file-transmission-profile.
The file-transmission-profile context defines transport parameters for protocol such as HTTP, include routing instance, source address, timeout value, and so on.
The no form of the command removes the profile name from the configuration.
Default
no file-transmission-profile
Parameters
- name
-
Specifies the file transmission profile name, up to 32 characters.
- create
-
Keyword used to create the transmission profile. The create keyword requirement can be enabled/disabled in the environment>create context.
Platforms
All
file-transmission-profile
Syntax
file-transmission-profile profile-name
no file-transmission-profile
Context
[Tree] (config>system>security>pki>ca-prof>auto-crl-update>crl-urls>url-entry file-transmission-profile)
Full Context
configure system security pki ca-profile auto-crl-update crl-urls url-entry file-transmission-profile
Description
This command specifies the file-transmission-profile for the url-entry. When the system downloads a CRL from the configured URL in the url-entry it will use the transportation parameter configured in the file-transmission-profile. auto-crl-update supports Base/Management/VPRN routing instance. vpls-management is not supported. In case of VPRN, the HTTP server port can only be 80 or 8080.
The no form of this command removes the specified profile name.
Default
no file-transmission-profile
Parameters
- profile-name
-
Specifies the name of the file transmission profile to be matched up to 32 characters. The profile name is configured in the config>system>file-transmission-profile context.
Platforms
All
file-url
file-url
Syntax
file-url file-url
no file-url
Context
[Tree] (config>mirror>mirror-dest>pcap file-url)
Full Context
configure mirror mirror-dest pcap file-url
Description
This command specifies a file URL for the FTP or TFTP server, including the filename for packet capture transfer. After the file URL is entered, the system attempts to establish a connection and creates a file using the filename specified. The command prompt displays an error and rejects the file URL if the session establishment fails, if write privilege to remote server fails, or if the session experiences a sudden termination. If the FTP or TFTP server is unreachable, the command prompt is halted for further input until the retires are timed out after 24 seconds (after four attempts of about six seconds each). This command overwrites any file on the FTP or TFTP server with the same filename.
The no form of this command removes the file-url instance and stops the packet capture and file transfer session.
Parameters
- file-url
-
Specifies the URL for the file to direct the search.
Platforms
All
filter
filter
Syntax
filter filter-id
no filter
Context
[Tree] (config>service>vprn>sub-if>grp-if>dhcp filter)
[Tree] (config>service>ies>sub-if>grp-if>dhcp filter)
Full Context
configure service vprn subscriber-interface group-interface dhcp filter
configure service ies subscriber-interface group-interface dhcp filter
Description
This command assigns a DHCP filter to the group-interface. This feature is used where the SR 7750 is the second DHCP relay or where DHCP messages are snooped for subscriber management. The filter can be used to bypass host creation, drop DHCP message, or perform no action.
The no form of this command reverts to the default.
Parameters
- filter-id
-
Specifies the DHCP filter ID for this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter filter-id
no filter
Context
[Tree] (config>service>vprn>sub-if>grp-if>dhcp6 filter)
[Tree] (config>service>ies>sub-if>grp-if>dhcp6 filter)
Full Context
configure service vprn subscriber-interface group-interface dhcp6 filter
configure service ies subscriber-interface group-interface dhcp6 filter
Description
This command assigns a DHCP6 filter to the group interface. This feature is used where the SR 7750 is the second DHCP6 relay or where DHCP6 messages are snooped for subscriber management. The filter can be used to bypass host creation, drop DHCP6 message, or perform no action.
The no form of this command reverts to the default.
Parameters
- filter-id
-
Specifies the DHCP6 filter ID for this interface
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-id] [ ipv6 ipv6-filter-id]
Context
[Tree] (config>service>vprn>red-if>spoke-sdp>ingress filter)
[Tree] (config>service>vprn>if>spoke-sdp>egress filter)
[Tree] (config>service>vprn>nw-if>egress filter)
[Tree] (config>service>vprn>if>spoke-sdp>ingress filter)
[Tree] (config>service>vprn>red-if>spoke-sdp>egress filter)
Full Context
configure service vprn redundant-interface spoke-sdp ingress filter
configure service vprn interface spoke-sdp egress filter
configure service vprn network-interface egress filter
configure service vprn interface spoke-sdp ingress filter
configure service vprn redundant-interface spoke-sdp egress filter
Description
This command associates an IP filter policy with an ingress or egress Service Access Point (SAP) or IP interface. An IP filter policy can be associated with spoke SDPs. Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria.
The filter command is used to associate a filter policy with a specified ip-filter-id with an ingress or egress SAP. The ip-filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip ip-filter-id
-
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn redundant-interface spoke-sdp egress filter
- configure service vprn redundant-interface spoke-sdp ingress filter
All
- configure service vprn interface spoke-sdp ingress filter
- configure service vprn interface spoke-sdp egress filter
- configure service vprn network-interface egress filter
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
no filter [ip ip-filter-id] [ipv6 ipv6-filter-id]
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>ingress filter)
[Tree] (config>service>ies>if>sap>egress filter)
[Tree] (config>service>ies>red-if>ingress filter)
[Tree] (config>service>ies>red-if>egress filter)
[Tree] (config>service>ies>sub-if>grp-if>sap>egress filter)
[Tree] (config>service>ies>if>sap>ingress filter)
[Tree] (config>service>ies>sub-if>grp-if>sap>ingress filter)
[Tree] (config>service>vprn>sub-if>grp-if>sap>egress filter)
Full Context
configure service vprn subscriber-interface group-interface sap ingress filter
configure service ies interface sap egress filter
configure service ies red-if ingress filter
configure service ies red-if egress filter
configure service ies subscriber-interface group-interface sap egress filter
configure service ies interface sap ingress filter
configure service ies subscriber-interface group-interface sap ingress filter
configure service vprn subscriber-interface group-interface sap egress filter
Description
This command associates a filter policy with an ingress or egress Service Access Point (SAP). Filter policies control the forwarding and dropping of packets based on the matching criteria. MAC filters are only allowed on Epipe and Virtual Private LAN Service (VPLS) SAPs.
The filter command is used to associate a filter policy with a specified ip-filter-id or ipv6-filter-id (7750 SR) with an ingress or egress SAP. The filter policy must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to the match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip ip-filter-id
-
Specifies the ID for the IP filter policy and corresponds to a previously created IP filter policy in the config>filter>ip-filter context.
- ipv6 ipv6-filter-id
-
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
- mac mac-filter-id
-
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface sap ingress filter
- configure service ies subscriber-interface group-interface sap egress filter
- configure service vprn subscriber-interface group-interface sap egress filter
- configure service ies subscriber-interface group-interface sap ingress filter
All
- configure service ies interface sap ingress filter
- configure service ies interface sap egress filter
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
Context
[Tree] (config>service>vpls>mesh-sdp>ingress filter)
[Tree] (config>service>vpls>sap>egress filter)
[Tree] (config>service>vpls>spoke-sdp>egress filter)
[Tree] (config>service>vpls>sap>ingress filter)
[Tree] (config>service>vpls>mesh-sdp>egress filter)
[Tree] (config>service>vpls>spoke-sdp>ingress filter)
Full Context
configure service vpls mesh-sdp ingress filter
configure service vpls sap egress filter
configure service vpls spoke-sdp egress filter
configure service vpls sap ingress filter
configure service vpls mesh-sdp egress filter
configure service vpls spoke-sdp ingress filter
Description
This command associates an IP filter policy or MAC filter policy with an ingress or egress Service Access Point (SAP) or IP interface.
Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria. There are two types of filter policies: IP and MAC. Only one type may be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified filter ID with an ingress or egress SAP. The filter ID must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip ip-filter-id
-
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
- ipv6 ipv6-filter-id
-
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
- mac mac-filter-id
-
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
Platforms
All
filter
Syntax
filter filter-name
no filter
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext filter)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw ranges range vrgw lanext filter
Description
This command applies to VPRN services only to filter for ingress home traffic.
Default
no filter
Parameters
- filter-name
-
Specifies an IP filter name, up to 32 characters.
filter
Syntax
filter filter-name
no filter
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>xconnect filter)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw ranges range vrgw lanext xconnect filter
Description
This command applies to VPRN services only to filter for cross-connect traffic.
Default
no filter
Parameters
- filter-name
-
Specifies an filter name, up to 32 characters.
filter
Syntax
filter filter-name
no filter
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext>network filter)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw ranges range vrgw lanext network filter
Description
This command applies to VPRN services only to filter for ingress data center traffic.
Default
no filter
Parameters
- filter-name
-
Specifies an IP filter name, up to 32 characters.
filter
Syntax
filter [ip ip-filter-id]
filter [ipv6 ipv6-filter-id]
no filter [ip ip-filter-id] [ipv6 ipv6-filter-id]
Context
[Tree] (config>service>ipipe>spoke-sdp>egress filter)
[Tree] (config>service>cpipe>spoke-sdp>ingress filter)
[Tree] (config>service>ipipe>sap>ingress filter)
[Tree] (config>service>ipipe>sap>egress filter)
[Tree] (config>service>cpipe>spoke-sdp>egress filter)
[Tree] (config>service>ipipe>spoke-sdp>ingress filter)
Full Context
configure service ipipe spoke-sdp egress filter
configure service cpipe spoke-sdp ingress filter
configure service ipipe sap ingress filter
configure service ipipe sap egress filter
configure service cpipe spoke-sdp egress filter
configure service ipipe spoke-sdp ingress filter
Description
This command associates a filter policy with an ingress or egress Service Access Point (SAP) or IP interface.
Filter policies control the forwarding and dropping of packets based on IP matching criteria. Only one filter can be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified ip-filter-id with an ingress or egress SAP. The ip-filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets will not be subject to the filter and will always be passed, even if the filter's default action is to drop.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip-filter-id
-
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
- ipv6-filter-id
-
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
Platforms
All
- configure service ipipe sap ingress filter
- configure service ipipe spoke-sdp ingress filter
- configure service ipipe sap egress filter
- configure service ipipe spoke-sdp egress filter
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe spoke-sdp ingress filter
- configure service cpipe spoke-sdp egress filter
filter
Syntax
filter [ip ip-filter-id]
filter [ipv6 ipv6-filter-id]
filter [mac mac-filter-id]
no filter [ip ip-filter-id]
no filter [ipv6 ipv6-filter-id]
no filter [mac mac-filter-id]
Context
[Tree] (config>service>epipe>sap>egress filter)
[Tree] (config>service>epipe>spoke-sdp>ingress filter)
[Tree] (config>service>epipe>spoke-sdp>egress filter)
[Tree] (config>service>epipe>sap>ingress filter)
Full Context
configure service epipe sap egress filter
configure service epipe spoke-sdp ingress filter
configure service epipe spoke-sdp egress filter
configure service epipe sap ingress filter
Description
This command associates an IP filter policy with an ingress or egress Service Access Point (SAP) or IP interface.
Filter policies control the forwarding and dropping of packets based on IP matching criteria. Only one filter can be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified filter-id with an ingress or egress SAP. The filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets will not be subject to the filter and will always be passed, even if the filter's default action is to drop.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
IPv6 filters are only supported by the 7450 ESS and 7750 SR but are not supported on a Layer 2 SAP that is configured with QoS MAC criteria. Also, MAC filters are not supported on a Layer 2 SAP that is configured with QoS IPv6 criteria.
Parameters
- ip-filter-id
-
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
- ipv6-filter-id
-
Specifies the IPv6 filter policy for 7450 ESS or 7750 SR. The filter ID must already exist within the created IPv6 filters.
- mac-filter-id
-
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
Platforms
All
filter
Syntax
[no] filter
Context
[Tree] (config>service>template>epipe-sap-template>ingress filter)
[Tree] (config>service>template>epipe-sap-template>egress filter)
Full Context
configure service template epipe-sap-template ingress filter
configure service template epipe-sap-template egress filter
Description
Commands in this context configure filter parameters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter ip ip-filter-id
no filter
Context
[Tree] (config>service>ies>aarp-interface>spoke-sdp>ingress filter)
[Tree] (config>service>ies>aarp-interface>spoke-sdp>egress filter)
Full Context
configure service ies aarp-interface spoke-sdp ingress filter
configure service ies aarp-interface spoke-sdp egress filter
Description
This command associates an IP filter policy with an ingress or egress IP interface. Filter policies control the forwarding and dropping of packets based on IP matching criteria.
The filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets will not be subject to the filter and will always be passed, even if the filter's default action is to drop.
The no form of this command removes any configured filter ID association with the IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local.
Parameters
- ip-filter-id
-
Specifies the filter policy. The filter ID must already exist within the created IP filters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter
Context
[Tree] (config>service>ies>if>spoke-sdp>ingress filter)
[Tree] (config>service>ies>if>spoke-sdp>egress filter)
Full Context
configure service ies interface spoke-sdp ingress filter
configure service ies interface spoke-sdp egress filter
Description
This command associates an IP filter policy filter policy with an ingress or egress spoke SDP.
Filter policies control the forwarding and dropping of packets based on matching criteria.
MAC filters are only allowed on Epipe and Virtual Private LAN Service (VPLS) SAPs.
The filter command is used to associate a filter policy with a specified ip-filter-id with an ingress or egress spoke SDP. The ip-filter-id must already be defined in the config>filter context before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
In general, filters applied to SAPs or spoke SDPs (ingress or egress) apply to all packets on the SAP or spoke SDPs. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip
-
Keyword indicating the filter policy is an IP filter.
- ip-filter-id
-
The filter name acts as the ID for the IP filter policy. Allowed values are an integer in the range of 1 and 65535 that corresponds to a previously created IP filter policy. The filter ID must already exist within the created IP filters.
Platforms
All
filter
Syntax
filter ip ip-filter-id
no filter
Context
[Tree] (config>service>vprn>aarp-interface>spoke-sdp>egress filter)
[Tree] (config>service>vprn>aarp-interface>spoke-sdp>ingress filter)
Full Context
configure service vprn aarp-interface spoke-sdp egress filter
configure service vprn aarp-interface spoke-sdp ingress filter
Description
This command associates an IP filter policy with an ingress or egress IP interface. Filter policies control the forwarding and dropping of packets based on IP matching criteria.
The filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets will not be subject to the filter and will always be passed, even if the filter's default action is to drop.
The no form of this command removes any configured filter ID association with the IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local.
Parameters
- ip-filter-id
-
Specifies the filter policy. The filter ID must already exist within the created IP filters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-id] [ ipv6 ipv6-filter-id]
Context
[Tree] (config>service>vprn>if>sap>egress filter)
[Tree] (config>service>vprn>if>sap>ingress filter)
Full Context
configure service vprn interface sap egress filter
configure service vprn interface sap ingress filter
Description
This command associates an IP filter policy with an ingress or egress Service Access Point (SAP) or IP interface. Filter policies control the forwarding and dropping of packets based on IP matching criteria.
The filter command is used to associate a filter policy with a specified filter ID with an ingress or egress SAP. The filter ID must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip ip-filter-id
-
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
- ipv6 ipv6-filter-id
-
Specifies IPv6 filter policy. The filter ID must already exist within the created IP filters.
Platforms
All
filter
Syntax
filter filter-id [name filter-name]
no filter filter-id
Context
[Tree] (config>service>vprn>log filter)
[Tree] (config>service>vprn>log>log-id filter)
Full Context
configure service vprn log filter
configure service vprn log log-id filter
Description
This command creates a context for an event filter. An event filter specifies whether to forward or drop an event or trap based on the match criteria.
Filters are configured in the filter filter-id context and then applied to a log in the log-id log-id context. Only events for the configured log source streams destined to the log ID where the filter is applied are filtered.
Changes made to an existing filter using any of the sub-commands are immediately applied to the destinations where the filter is applied.
By default, no event filters are defined. Event filters must be explicitly configured.
The no form of this command removes the filter association from log IDs, which causes those logs to forward all events.
Default
No event filters are defined.
Parameters
- filter-id
-
Specifies the unique filter ID.
- name filter-name
-
Configures an optional filter name, up to 64 characters, that can be used to refer to the filter after it is created.
Platforms
All
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-id] [ ipv6 ipv6-filter-id]
Context
[Tree] (config>service>vprn>network>ingress filter)
Full Context
configure service vprn network ingress filter
Description
This command configures a network ingress filter for IPv4 or IPv6 traffic arriving over explicitly defined spokes or auto-bind network interfaces for the VPRN service.
The no form of this command removes an IPv4, IPv6, or both filters.
Default
no filter
Parameters
- ip-filter-id/ipv6-filter-id
-
Specifies an existing IP/IPv6 filter policy of a scope template.
Platforms
All
filter
Syntax
filter ip ip-filter-id
no filter [ip ip-filter-id]
Context
[Tree] (config>service>vprn>aa-if>sap>egress filter)
[Tree] (config>service>ies>aa-if>sap>egress filter)
Full Context
configure service vprn aa-interface sap egress filter
configure service ies aa-interface sap egress filter
Description
This command applies an IP filter to the SAP.
Default
no filter
Parameters
- ip-filter-id
-
Specifies an existing IP filter ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter
Context
[Tree] (debug>app-assure>group>http-host filter)
Full Context
debug application-assurance group http-host-recorder filter
Description
This command configures recorder filter settings. This command specifies the filtering parameter for the http-host-recorder feature.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter
Syntax
filter ip ip-filter-id
no filter
Context
[Tree] (config>service>vprn>video-interface>video-sap>egress filter)
[Tree] (config>service>ies>video-interface>video-sap>egress filter)
[Tree] (config>service>ies>video-interface>video-sap>ingress filter)
[Tree] (config>service>vprn>video-interface>video-sap>ingress filter)
Full Context
configure service vprn video-interface video-sap egress filter
configure service ies video-interface video-sap egress filter
configure service ies video-interface video-sap ingress filter
configure service vprn video-interface video-sap ingress filter
Description
This command associates an existing IP filter policy with an ingress or egress video SAP. Filter policies control the forwarding and dropping of packets based on the matching criteria.
Filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to the match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP. The filter ID itself is not removed from the system.
Parameters
- ip ip-filter-id
-
Specifies the ID for the IP filter policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
filter
Syntax
filter ip ip-filter-id
no filter
Context
[Tree] (config>service>vprn>ipmirrorif>spoke-sdp filter)
Full Context
configure service vprn ipmirrorif spoke-sdp filter
Description
This command places a filter on the IP mirror interface spoke SDP. It is recommended to configure this filter with a PBR filter to redirect the mirror traffic to the proper egress interface.
The no form of this command removes the filter ID from the configuration.
Parameters
- ip-filter-id
-
Specifies the IP filter ID.
filter
Syntax
filter filter-id
no filter
Context
[Tree] (config>li>log>log-id filter)
Full Context
configure li log log-id filter
Description
This command adds an event filter policy with the log destination.
The filter command is optional. If no event filter is configured, all events, alarms and traps generated by the source stream will be forwarded to the destination.
An event filter policy defines (limits) the events that are forwarded to the destination configured in the log-id. The event filter policy can also be used to select the alarms and traps to be forwarded to a destination snmp-trap-group.
The application of filters for debug messages is limited to application and subject only.
Accounting records cannot be filtered using the filter command.
Only one filter-id can be configured per log destination.
The no form of this command removes the specified event filter from the log-id.
Parameters
- filter-id
-
Specifies the event filter policy ID used to associate the filter with the log-id configuration. The event filter policy ID must already be defined in config>log>filter filter-id.
Platforms
All
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-id] [ ipv6 ipv6-filter-id]
Context
[Tree] (config>router>if>egress filter)
[Tree] (config>router>if>ingress filter)
Full Context
configure router interface egress filter
configure router interface ingress filter
Description
This command associates an IP filter policy with an IP interface.
Filter policies control packet forwarding and dropping based on IP match criteria.
The ip-filter-id must have been preconfigured before this filter command is executed. If the filter ID does not exist, an error occurs.
Only one filter ID can be specified.
The no form of this command removes the filter policy association with the IP interface.
Default
no filter
Parameters
- ip-filter-id
-
The filter name acts as the ID for the IP filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ip context.
- ipv6-filter-id
-
The filter name acts as the ID for the IPv6 filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ipv6 context. This parameter only applies to the 7750 SR and 7950 XRS.
Platforms
All
filter
Syntax
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
filter mac mac-filter-id
no filter [ip ip-filter-id] [mac mac-filter-id] [ipv6 ipv6-filter-id]
Context
[Tree] (config>service>pw-template>ingress filter)
[Tree] (config>service>pw-template>egress filter)
Full Context
configure service pw-template ingress filter
configure service pw-template egress filter
Description
This command associates an IP filter policy or MAC filter policy on egress or ingress. Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria. There are two types of filter policies: IP and MAC. Only one type may be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified filter ID with an ingress or egress SAP. The filter ID must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
This command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The filter-name command can be used in all configuration modes.
This command is mutually exclusive with the filter-name command. Only one or the other can be configured.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip-filter-id
-
Specifies the IP filter policy.
- ipv6-filter-id
-
Specifies the IPv6 filter policy.
- mac-filter-id
-
Specifies the MAC filter policy.
Platforms
All
filter
Syntax
filter filter-id [name filter-name]
no filter filter-id
Context
[Tree] (config>log filter)
Full Context
configure log filter
Description
This command creates a context for an event filter. An event filter specifies whether to forward or drop an event or trap based on the match criteria.
Filters are configured in the filter filter-id context and then applied to a log in the log-id log-id context. Only events for the configured log source streams destined to the log ID where the filter is applied are filtered.
Changes made to an existing filter using any of the sub-commands are immediately applied to the destinations where the filter is applied.
By default, no event filters are defined. Event filters must be explicitly configured.
The no form of this command removes the filter association from log IDs, which causes those logs to forward all events.
Parameters
- filter-id
-
Specifies the unique filter ID.
- name filter-name
-
Configures an optional filter name, up to 64 characters, that can be used to refer to the filter after it is created.
Platforms
All
filter
Syntax
filter filter-id
no filter
Context
[Tree] (config>log>log-id filter)
Full Context
configure log log-id filter
Description
This command adds an event filter policy with the log destination.
The filter command is optional. If an event filter is not configured, all events, alarms and traps generated by the source stream will be forwarded to the destination.
An event filter policy defines (limits) the events that are forwarded to the destination configured in the log-id. The event filter policy can also be used to select the alarms and traps to be forwarded to a destination snmp-trap-group.
The application of filters for debug messages is limited to application and subject only.
Accounting records cannot be filtered using the filter command.
Only one filter ID can be configured per log destination.
The no form of this command removes the specified event filter from the log-id.
Parameters
- filter-id
-
Specifies the event filter policy ID is used to associate the filter with the log-id configuration. The event filter policy ID must already be defined in config>log>filter filter-id.
Platforms
All
filter-cam-type
filter-cam-type
Syntax
filter-cam-type {normal | packet-length}
Context
[Tree] (config>service>vprn>flowspec filter-cam-type)
Full Context
configure service vprn flowspec filter-cam-type
Description
This command specifies the filter type that is required to embed FlowSpec entries to this VPRN. The filter type defines the match criteria that are available in the filter policy.
Default
normal
Parameters
- normal
-
Specifies that the filter policy is of type normal.
- packet-length
-
Specifies that the filter policy is of type packet-length.
Platforms
All
filter-cam-type
Syntax
filter-cam-type {normal | packet-length}
Context
[Tree] (config>router>flowspec filter-cam-type)
Full Context
configure router flowspec filter-cam-type
Description
This command specifies the filter type that is required to embed FlowSpec entries. The filter type defines the match criteria that are available in the filter policy.
Default
normal
Parameters
- normal
-
Specifies that the filter policy is of type normal.
- packet-length
-
Specifies that the filter policy is of type packet-length.
Platforms
All
filter-id-range
filter-id-range
Syntax
filter-id-range start filter-id end filter-id
no filter-id-range
Context
[Tree] (config>filter>md-auto-id filter-id-range)
Full Context
configure filter md-auto-id filter-id-range
Description
This command specifies the range of IDs used by SR OS to automatically assign an ID to filters that are created in model-driven interfaces without an ID explicitly specified by the user or client.
A filter created with an explicitly-specified ID cannot use an ID in this range. In classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD interfaces, the range can be changed, which causes any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.
The no form of this command removes the range values.
See the config>filter md-auto-id command for further details.
Default
no filter-id-range
Parameters
- start filter-id
-
Specifies the lower value of the ID range. The value must be less than or equal to the end value.
- end filter-id
-
Specifies the upper value of the ID range. The value must be greater than or equal to the start value.
Platforms
All
filter-name
filter-name
Syntax
[no] filter-name
Context
[Tree] (config>service>template>epipe-sap-template>ingress filter-name)
[Tree] (config>service>template>epipe-sap-template>egress filter-name)
Full Context
configure service template epipe-sap-template ingress filter-name
configure service template epipe-sap-template egress filter-name
Description
Commands in this context configure filter parameters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
filter-name
Syntax
[no] filter-name
Context
[Tree] (config>service>template>vpls-sap-template>egress filter-name)
[Tree] (config>service>template>vpls-sap-template>ingress filter-name)
Full Context
configure service template vpls-sap-template egress filter-name
configure service template vpls-sap-template ingress filter-name
Description
Commands in this context configure filter parameters.
Platforms
All
filter-name
Syntax
filter-name filter-name
no filter-name
Context
[Tree] (config>filter>ip-exception filter-name)
Full Context
configure filter ip-exception filter-name
Description
This command configures filter-name attribute of a given filter. filter-name, when configured, can be used instead of filter ID to reference the given policy in the CLI.
Default
no filter-name
Parameters
- filter-name
-
Specifies a string up to 64 characters in length that uniquely identifies this filter policy.
The following restrictions apply to the filter-name:
-
Policy names may not begin with a number (0-9).
-
Policy names may not begin with the underscore "_” character (e.g. _myPolicy). Names that start with underscore are reserved for system generated names.
-
"fSpec-x” (where x is any number) cannot be used as a user defined filter name.
-
Platforms
VSR
filter-name
Syntax
filter-name ip ip-name
filter-name ipv6 ipv6-name
filter-name mac mac-name
no filter-name [ip] [ipv6] [mac]
Context
[Tree] (config>service>pw-template>egress filter-name)
[Tree] (config>service>pw-template>ingress filter-name)
Full Context
configure service pw-template egress filter-name
configure service pw-template ingress filter-name
Description
This command associates an IP filter policy or MAC filter policy on egress or ingress. Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria. There are two types of filter policies: IP and MAC. Only one type may be applied to a SAP at a time.
The filter-name command is used to associate a filter policy with a specified filter name with an ingress or egress SAP. The filter name must already be defined before the filter-name command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
This command is mutually exclusive with the filter command. Only one or the other can be configured.
The no form of this command removes any configured filter name association with the SAP or IP interface. The filter name itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter name and only break the association with the service object, use scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Parameters
- ip-name
-
Specifies the IP filter policy. The filter name must already exist within the created IP filters, up to 64 characters.
- ipv6-name
-
Specifies the IPv6 filter policy. The filter name must already exist within the created IPv6 filters, up to 64 characters.
- mac-name
-
Specifies the MAC filter policy. The specified filter name must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters, up to 64 characters.
Platforms
All
filter-profile
filter-profile
Syntax
filter-profile {none | profile-a}
Context
[Tree] (config card filter-profile)
Full Context
configure card filter-profile
Description
This command controls the resources allocated to ingress and egress IPv4 and IPv6 filters on a per-linecard basis on the SR-a platform. You must shutdown the card prior to changing the filter profile.
Default
filter-profile none
Parameters
- none
-
Sets the card filter profile to its default value.
- profile-a
-
Sets the card filter profile to profile-a.
Platforms
7750 SR-a
filter-sample
filter-sample
Syntax
[no] filter-sample
Context
[Tree] (config>filter>ipv6-filter>entry filter-sample)
[Tree] (config>filter>ip-filter>entry filter-sample)
Full Context
configure filter ipv6-filter entry filter-sample
configure filter ip-filter entry filter-sample
Description
This command enables cflowd sampling for packets matching this filter entry.
If the cflowd is either not enabled or set to cflowd interface mode, this command is ignored.
The no form disables the cflowd sampling using this filter entry.
Default
no filter-sample
Platforms
All
filtering
filtering
Syntax
filtering filtering-mode
no filtering
Context
[Tree] (config>service>nat>nat-policy filtering)
[Tree] (config>service>nat>up-nat-policy filtering)
[Tree] (config>service>nat>firewall-policy filtering)
Full Context
configure service nat nat-policy filtering
configure service nat up-nat-policy filtering
configure service nat firewall-policy filtering
Description
This command configures the filtering of the NAT or residential firewall policy.
Default
filtering endpoint-independent
Parameters
- filtering-mode
-
Specifies the method used to filter the inbound traffic.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy filtering
- configure service nat up-nat-policy filtering
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy filtering
find-egress
find-egress
Syntax
find-egress packet packet-number ingress-port physical-port-id
Context
[Tree] (oam find-egress)
Full Context
oam find-egress
Description
This command executes the OAM find-egress test, injecting the specified packet ID into the specified ingress port.
Parameters
- packet-number
-
Specifies the build-packet to be injected into the associated ingress port.
- physical-port-id
-
Specifies the physical port ID that is injected into the specified build-packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fir-burst-limit
fir-burst-limit
Syntax
fir-burst-limit size [bytes | kilobytes]
no fir-burst-limit
Context
[Tree] (config>qos>sap-egress>queue fir-burst-limit)
Full Context
configure qos sap-egress queue fir-burst-limit
Description
This command configures a burst limit for the FIR of the specified queue.
The no version of this command returns the limit to the default value.
Parameters
- size
-
Specifies the size of the FIR burst limit.
Platforms
7750 SR-1, 7750 SR-s
firewall
firewall
firewall-info
firewall-info
Syntax
[no] firewall-info
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute firewall-info)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute firewall-info
Description
This command enables inclusion of the Firewall Information VSA in AAA protocols.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
firewall-policy
firewall-policy
Syntax
firewall-policy policy-name
no firewall-policy
Context
[Tree] (config>subscr-mgmt>sub-prof firewall-policy)
Full Context
configure subscriber-mgmt sub-profile firewall-policy
Description
This command enables the IPv6 firewall for this subscriber profile using the specified firewall policy.
The no form of this command disables the IPv6 firewall for this subscriber profile.
Default
no firewall-policy
Parameters
- policy-name
-
Specifies the name of the firewall policy, up to 32 characters maximum.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
firewall-policy
Syntax
firewall-policy name [create]
no firewall-policy
Context
[Tree] (config>service>nat firewall-policy)
Full Context
configure service nat firewall-policy
Description
This command configures a firewall policy that can be used in contexts where basic protection from outside attack vectors is required.
The no form of the command removes the policy, and can only be performed when the policy is not in use.
Default
no firewall-policy
Parameters
- create
-
Mandatory keyword used when creating a firewall policy.
- name
-
Specifies the name of the firewall policy, up to 32 characters maximum.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
flags-tlv
flags-tlv
Syntax
[no] flags-tlv
Context
[Tree] (config>router>fad>flex-algo flags-tlv)
Full Context
configure router flexible-algorithm-definitions flex-algo flags-tlv
Description
This command advertises the FAD Flags TLV to provide additional context on how the router must run a constrained SPF (cSPF). The IETF definition includes only the M-flag for use in the FAD Flags TLV. When it is set, the M-flag specifies the use of a Flex-Algorithm specific prefix metric. The M-flag is important for inter-area or inter-domain routing support with Flex-Algorithms.
When a router advertises a FAD, it is optional to advertise the FAD Flags TLV. However, when a FAD that includes the FAD Flags TLV is received, then the router must decode the flags before participating in the Flex-Algorithm.
By default, the following considerations apply to the FAD Flags TLV.
-
SR OS sets the M-flag and advertises the FAD Flags TLV.
-
When a FAD Flags TLV is received, SR OS decodes the flags and modifies the cSPF computation based upon the M-flag status.
The no form of this command prevents the advertisement of the FAD Flags TLV within a FAD.
Default
flags-tlv
Platforms
All
flex-algo
flex-algo
Syntax
flex-algo flex-algo
no flex-algo
Context
[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop flex-algo)
Full Context
configure router static-route-entry indirect tunnel-next-hop flex-algo
Description
This command instructs the tunnel towards the indirect static-route next-hop to use the specified flexible algorithm.
It is assumed that the router using this command is participating in the flexible algorithm. This command instructs the router to lookup the indirect next-hop using flexible algorithm tunnels. If flexible algorithm aware tunnel to the indirect next-hop does not exist, then the static-route is not activated.
The expected outcome of this command is that when the router receives an IP payload packet, that it is steered towards the indirect next-hop using a flexible algorithm aware segment-routing tunnel if such tunnel exists. If such tunnel does not exist, then the route is not active, and the received IP packet will be dropped, if no other Longest Prefix Match (LPM) route exists.
If the flex-algo parameter is specified, the resolution filter can only use matching flexible algorithm-aware segment routing tunnels created by flexible algorithm-aware routing protocols (for example, SR IS-IS).
The no form of this command disables flexible algorithm-aware indirect next-hop resolution.
Default
no flex-algo
Parameters
- flex-algo
-
Configures or deconfigures tunnel-next-hop flexible algorithm for resolving indirect static-route-entry.
Platforms
All
flex-algo
Syntax
flex-algo fad-name [create]
no flex-algo fad-name
Context
[Tree] (config>router>fad flex-algo)
Full Context
configure router flexible-algorithm-definitions flex-algo
Description
This command configures the definition context for a Flexible Algorithm Definition (FAD). Parameters, including the FAD priority, metric type, links to construct a flexible algorithm topology graph, and a description of the algorithm. Up to 256 local FADs can be configured on a router.
The FAD configuration parameters are grouped using the fad-name as the reference anchor. When an IGP is configured to use and advertise a local configured FAD, the fad-name is used as the reference anchor.
The no form of this command deletes the configured parameters and removes the defined FAD.
Default
no flex-algo
Parameters
- fad-name
-
Specifies the name of the flexible algorithm, up to 32 characters, that is used as reference anchor for the configured parameters.
- create
-
Specifies the mandatory keyword to create a router instance.
Platforms
All
flex-algo
Syntax
[no] flex-algo flex-algo
Context
[Tree] (config>router>isis>flex-algos flex-algo)
Full Context
configure router isis flexible-algorithms flex-algo
Description
This command enters the configuration context for an IS-IS flexible algorithm.
A maximum of seven unique flexible algorithms can be configured on a router across all configured IS-IS instances. In each IS-IS flexible algorithm configuration context, the IS-IS instance participation can be either enabled or disabled, and it configures the advertising of a locally-configured flexible algorithm definition.
When flexible algorithm is enabled in an IS-IS instance, it is enabled for all levels (Level 1 and Level 2) within the IS-IS instance.
The no form of this command removes the IS-IS flexible algorithm configuration context.
Default
no flex-algo
Parameters
- flex-algo
-
Specifies the number of the IS-IS flexible algorithm.
Platforms
All
flex-algo
Syntax
[no] flex-algo flex-algo-id
Context
[Tree] (config>router>ospf>flex-algos flex-algo)
Full Context
configure router ospf flexible-algorithms flex-algo
Description
This command enters the configuration context for an OSPFv2 flexible algorithm.
A maximum of seven unique flexible algorithms can be configured on a router across all configured OSPFv2 instances. The supported flexible algorithms are in the range of 128 to 255. In each OSPF flexible algorithm configuration context, the OSPFv2 instance participation can be either enabled or disabled, and it configures the advertising of a locally-configured flexible algorithm definition.
When flexible algorithm is enabled in an OSPF instance, it is enabled for all areas within the OSPF instance.
The no form of this command removes the OSPF flexible algorithm configuration context.
Default
no flex-algo
Parameters
- flex-algo-id
-
Specifies the OSPF flexible algorithm number.
Platforms
All
flex-algo
Syntax
[no] flex-algo flex-algo-id
Context
[Tree] (config>router>ospf>area>if flex-algo)
Full Context
configure router ospf area interface flex-algo
Description
This command enters the OSPFv2 flexible algorithms configuration context on the interface.
The no form of this command removes the OSPF flexible algorithm configuration context.
Default
no flex-algo
Parameters
- flex-algo-id
-
Specifies the number of the OSPF flexible algorithm.
Platforms
All
flex-algo
Syntax
flex-algo flex-algo-id | param-name
no flex-algo
Context
[Tree] (config>router>policy-options>policy-statement>entry>action flex-algo)
[Tree] (config>router>policy-options>policy-statement>default-action flex-algo)
Full Context
configure router policy-options policy-statement entry action flex-algo
configure router policy-options policy-statement default-action flex-algo
Description
This command configures the Flex-Algorithm for use in the BGP next-hop autobind operation in a BGP import policy. A Flex-Algorithm aware autobind of the BGP next-hop is enabled when the route is matched by the policy statement entry.
-
Flex-Algorithm aware next-hop lookup is supported for unicast BGP, VPRN, and BGP-LU.
-
This command is not supported for multicast address families.
The no form of this command removes the Flex-Algorithm aware next-hop lookup.
Default
no flex-algo
Parameters
- flex-algo-id
-
Specifies the flexible algorithm forwarding path.
- param-name
-
Specifies the parameter name, up to 32 characters, that starts and ends with an at-sign (@) symbol.
Platforms
All
flex-algo-id
flex-algo-id
Syntax
flex-algo-id id
no flex-algo-id
Context
[Tree] (config>anysec>tnl-enc>enc-grp>peer-tnl-attrs flex-algo-id)
Full Context
configure anysec tunnel-encryption encryption-group peer-tunnel-attributes flex-algo-id
Description
This command configures the flexible algorithm ID for the outgoing tunnel to be encrypted. This ID must match the desired LSP that is using this flex algo in order for the LSP to be encrypted via ANYsec.
The no form of this command removes the configured ID.
Default
flex-algo-id 0
Parameters
- id
-
Specifies the flexible algorithm ID.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se
flex-algo-id
Syntax
flex-algo-id id
no flex-algo-id
Context
[Tree] (config>anysec>tnl-enc>sec-term-pol flex-algo-id)
Full Context
configure anysec tunnel-encryption security-termination-policy flex-algo-id
Description
This command configures the flexible algorithm ID. This ID must be a match for the local terminating ANYsec tunnel.
The no form of this command removes the configured ID.
Default
flex-algo-id 0
Parameters
- id
-
Specifies the flexible algorithm ID.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se
flexible-algorithm-definitions
flexible-algorithm-definitions
Syntax
flexible-algorithm-definitions
Context
[Tree] (config>router flexible-algorithm-definitions)
Full Context
configure router flexible-algorithm-definitions
Description
Commands in this context locally configure algorithm definitions.
Platforms
All
flexible-algorithms
flexible-algorithms
Syntax
flexible-algorithms
Context
[Tree] (config>router>isis flexible-algorithms)
Full Context
configure router isis flexible-algorithms
Description
Commands in this context configure the IS-IS parameters for flexible algorithm participation.
Platforms
All
flexible-algorithms
Syntax
flexible-algorithms
Context
[Tree] (config>router>ospf flexible-algorithms)
Full Context
configure router ospf flexible-algorithms
Description
Commands in this context configure the OSPFv2 parameters for flexible algorithm participation.
Platforms
All
flood-garp-and-unknown-req
flood-garp-and-unknown-req
Syntax
[no] flood-garp-and-unknown-req
Context
[Tree] (config>service>ies>if>vpls>evpn>arp flood-garp-and-unknown-req)
[Tree] (config>service>vprn>if>vpls>evpn>arp flood-garp-and-unknown-req)
Full Context
configure service ies interface vpls evpn arp flood-garp-and-unknown-req
configure service vprn interface vpls evpn arp flood-garp-and-unknown-req
Description
This command controls whether CPM-originated ARP frames are flooded in the R-VPLS service. Any frames that are data path flooded, such as the ARP messages received on a SAP, are flooded regardless of the command.
The no form of this command disables flooding GARP and unknown requests.
Default
flood-garp-and-unknown-req
Platforms
All
flood-time
flood-time
Syntax
flood-time flood-time
no flood-time
Context
[Tree] (config>service>vpls>mrp flood-time)
Full Context
configure service vpls mrp flood-time
Description
This command configures the amount of time, in seconds, after a status change in the VPLS service during which traffic is flooded. When that time expires, traffic will be delivered according to the MMRP registrations that exist in the VPLS. When "no flood-time” is executed, flooding behavior is disabled.
Default
no flood-time
Parameters
- flood-time
-
Specifies the MRP flood time, in seconds.
Platforms
All
flood-time
Syntax
flood-time flood-time
no flood-time
Context
[Tree] (config>service>vpls>mrp>mmrp flood-time)
Full Context
configure service vpls mrp mmrp flood-time
Description
This command configures the amount of time, in seconds, after a status change in the VPLS service during which traffic is flooded. Once that time expires, traffic will be delivered according to the MMRP registrations that exist in the VPLS.
Default
flood-time 3
Parameters
- flood-time
-
Specifies the MRP flood time, in seconds
Platforms
All
flow-attribute
flow-attribute
Syntax
[no] flow-attribute flow-attribute-name
Context
[Tree] (config>app-assure>group>policy>aqp>entry>match flow-attribute)
Full Context
configure application-assurance group policy app-qos-policy entry match flow-attribute
Description
This command configures a flow attribute to use as match criteria.
The no form of this command reverts to the default value.
Default
no flow-attribute
Parameters
- flow-attribute-name
-
Specifies the name of the flow attribute, up to 256 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-attribute
Syntax
[no] flow-attribute flow-attribute-name
Context
[Tree] (config>isa>aa-grp flow-attribute)
Full Context
configure isa application-assurance-group flow-attribute
Description
This command enables the specified flow attribute.
The no form of this command disables the attribute.
Parameters
- flow-attribute-name
-
Specifies the name of the flow attribute, up to 256 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-attribute
Syntax
[no] flow-attribute flow-attribute-name
Context
[Tree] (config>app-assure>group>policy>chrg-fltr>entry>match flow-attribute)
Full Context
configure application-assurance group policy charging-filter entry match flow-attribute
Description
This command configured the addition of a flow attribute to the match criteria used by this charging filter entry.
The no form of this command removes the flow attribute match criteria.
Default
no flow-attribute
Parameters
- flow-attribute-name
-
Specifies the name of the flow attribute, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-count
flow-count
Syntax
flow-count flow-count
no flow-count
Context
[Tree] (config>app-assure>group>tod-override flow-count)
[Tree] (config>app-assure>group>policer flow-count)
Full Context
configure application-assurance group policer tod-override flow-count
configure application-assurance group policer flow-count
Description
This command configures the flow count for the flow-count-limit policer. It is recommended to configure flow count subscriber-level policer for AA subscribers to ensure fair usage of flow resources between AA subscribers.
Default
no flow-count
Parameters
- flow-count
-
Specifies the flow count for the flow-count-limit policer.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-count-limit
flow-count-limit
Syntax
flow-count-limit policer-name [event-log event-log-name]
no flow-count-limit
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action flow-count-limit)
Full Context
configure application-assurance group policy app-qos-policy entry action flow-count-limit
Description
This command assigns an existing flow count limit policer as an action on flows matching this AQP entry.
The match criteria for the AQP entry must specify a uni-directional traffic direction before a policer action can be configured. If a policer is used in one direction in an AQP match entry the same policer name cannot be used by another AQP entry which uses a different traffic direction match criteria.
When multiple policers apply to a single flow, the final action on a packet is the worst case of all policer outcomes (for example, if one of the policers marks packet out of profile, the final marking will reflect that).
The no form of this command removes this flow policer from actions on flows matching this AQP entry.
Default
no flow-count-limit
Parameters
- policer-name
-
Specifies the name of the existing flow setup rate policer for this application assurance profile. The policer-name is configured in the config>app-assure>group>policer context.
- event-log-name
-
Specifies the name of the event log used when event logging is enabled, up to 32 characters, which is used when event logging is enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-label
flow-label
Syntax
flow-label flow-label [mask]
no flow-label
Context
[Tree] (config>filter>ipv6-filter>entry>match flow-label)
Full Context
configure filter ipv6-filter entry match flow-label
Description
This command configures the flow-label and optional mask match condition.
The no form of the command reverts to the default.
Default
no flow-label
Parameters
- flow-label
-
Specifies the flow label to be used as a match criterion. Value can be expressed as a decimal integer, as well as in hexadecimal or binary format. The following value shows decimal integer format only.
- mask
-
Specifies the flow label mask value for this policy IPv6 Filter entry. Value can be expressed as a decimal integer, as well as in hexadecimal or binary format. The following value shows decimal integer format only.
Platforms
All
flow-label
Syntax
flow-label value
no flow-label
Context
[Tree] (config>system>security>mgmt-access-filter>ipv6-filter>entry flow-label)
Full Context
configure system security management-access-filter ipv6-filter entry flow-label
Description
This command configures flow label match conditions. Flow labeling enables the labeling of packets belonging to particular traffic flows for which the sender requests special handling, such as non-default quality of service or real-time service. This command only applies to the 7750 SR and 7950 XRS.
Parameters
- value
-
Specifies the flow identifier in an IPv6 packet header that can be used to discriminate traffic flows (See RFC 3595, Textual Conventions for IPv6 Flow Label.)
Platforms
All
flow-label
Syntax
flow-label value
no flow-label
Context
[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match flow-label)
Full Context
configure system security cpm-filter ipv6-filter entry match flow-label
Description
This command configures flow label match conditions. Flow labeling enables the labeling of packets belonging to particular traffic flows for which the sender requests special handling, such as non-default quality of service or real-time service.
Parameters
- value
-
Specifies the flow identifier in an IPv6 packet header that can be used to discriminate traffic flows (See RFC 3595, Textual Conventions for IPv6 Flow Label.)
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
flow-label-load-balancing
flow-label-load-balancing
Syntax
[no] flow-label-load-balancing
Context
[Tree] (config>router>if>load-balancing flow-label-load-balancing)
[Tree] (config>service>ies>if>load-balancing flow-label-load-balancing)
[Tree] (config>service>vprn>nw-if>load-balancing flow-label-load-balancing)
[Tree] (config>service>vprn>if>load-balancing flow-label-load-balancing)
Full Context
configure router interface load-balancing flow-label-load-balancing
configure service ies interface load-balancing flow-label-load-balancing
configure service vprn network-interface load-balancing flow-label-load-balancing
configure service vprn interface load-balancing flow-label-load-balancing
Description
This command enables load balancing in ECMP and LAG that is based on the output of a hash performed on the triplet {SA, DA, flow label} in the header of an IPv6 packet received on a IES, VPRN, R-VPLS, CsC, or network interface.
The no form of this command disables load balancing in ECMP and LAG based on the hash of triplet fields {SA, DA, flow label} in an IPv6 packet header.
Default
no flow-label-load-balancing
Platforms
All
flow-rate
flow-rate
Syntax
flow-rate sample-rate
no flow-rate
Context
[Tree] (config>app-assure>group>cflowd>comp flow-rate)
[Tree] (config>app-assure>group>cflowd>tcp-perf flow-rate)
[Tree] (config>app-assure>group>cflowd>rtp-perf flow-rate)
Full Context
configure application-assurance group cflowd comprehensive flow-rate
configure application-assurance group cflowd tcp-performance flow-rate
configure application-assurance group cflowd rtp-performance flow-rate
Description
This command specifies the per-flow sampling rate for the cflowd export of Application Assurance performance statistics.
The no form of this command reverts to the default.
Default
no flow-rate
Parameters
- sample-rate
-
Specifies the rate at which to sample flows that are eligible for TCP performance measurement.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-rate-limit
flow-rate-limit
Syntax
flow-rate-limit policer-name [event-log event-log-name]
no flow-rate-limit
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action flow-rate-limit)
Full Context
configure application-assurance group policy app-qos-policy entry action flow-rate-limit
Description
This command assigns an existing flow setup rate limit policer as an action on flows matching this AQP entry.
The match criteria for the AQP entry must specify a uni-directional traffic direction before a policer action can be configured. If a policer is used in one direction in an AQP match entry the same policer name cannot be used by another AQP entry which uses a different traffic direction match criteria.
When multiple policers apply to a single flow, the final action on a packet is the worst case of all policer outcomes (for example, if one of the policers marks packet out of profile, the final marking will reflect that).
The no form of this command removes this flow policer from actions on flows matching this AQP entry.
Default
no flow-rate-limit
Parameters
- policer-name
-
Specifies the policer name up to 32 characters.
- event-log event-log-name
-
Specifies the event-log-name up to 32 characters, which will be used when event logging is enabled.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-rate2
flow-rate2
Syntax
flow-rate2 sample-rate
no flow-rate2
Context
[Tree] (config>app-assure>group>cflowd>comp flow-rate2)
[Tree] (config>app-assure>group>cflowd>rtp-perf flow-rate2)
[Tree] (config>app-assure>group>cflowd>tcp-perf flow-rate2)
Full Context
configure application-assurance group cflowd comprehensive flow-rate2
configure application-assurance group cflowd rtp-performance flow-rate2
configure application-assurance group cflowd tcp-performance flow-rate2
Description
This command specifies the per-flow second sampling rate for the cflowd export of Application Assurance performance statistics.
The no form of this command reverts to the default.
Default
no flow-rate2
Parameters
- sample-rate
-
Specifies the rate at which to sample flows that are eligible for TCP and/or RTP performance measurement.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-setup-direction
flow-setup-direction
Syntax
flow-setup-direction {subscriber-to-network | network-to-subscriber | both}
Context
[Tree] (config>app-assure>group>policy>app-filter>entry flow-setup-direction)
Full Context
configure application-assurance group policy app-filter entry flow-setup-direction
Description
This command configures the direction of flow setup to which the application filter entry is to be applied.
Default
flow-setup-direction both
Parameters
- subscriber-to-network
-
Specifies that the app-filter entry will be applied to flows initiated by a local subscriber.
- network-to-subscriber
-
Specifies that the app-filter entry will be applied to flows initiated from a remote destination towards a local subscriber.
- both
-
Specifies that the app filter entry will be applied for subscriber-to-network and network-to-subscriber traffic.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-setup-high-wmark
flow-setup-high-wmark
Syntax
flow-setup-high-wmark high-watermark
Context
[Tree] (config>app-assure flow-setup-high-wmark)
Full Context
configure application-assurance flow-setup-high-wmark
Description
This command configures the system wide high watermark threshold for per-ISA throughput in packets/second when an alarm will be raised by the agent. The value must be larger than or equal to the packet-rate-low-wmark parameter.
Default
flow-setup-high-wmark max
Parameters
- high-watermark
-
Specifies the high watermark for flow setup rate alarms. The value must be larger than or equal to the flow-setup-low-wmark value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-setup-low-wmark
flow-setup-low-wmark
Syntax
flow-setup-low-wmark low-watermark
no flow-setup-low-wmark
Context
[Tree] (config>app-assure flow-setup-low-wmark)
Full Context
configure application-assurance flow-setup-low-wmark
Description
This command configures the flow setup rate on the ISA-AA when a flow setup alarm will be raised by the agent.
Default
flow-setup-low-wmark 0
Parameters
- low-watermark
-
Specifies the low watermark for flow setup rate alarms. The value must be larger than or equal to the flow-setup-high-wmark value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-spec-dest
flow-spec-dest
Syntax
flow-spec-dest prefix-list-name
no flow-spec-dest
Context
[Tree] (config>router>policy-options>policy-statement>entry>from flow-spec-dest)
Full Context
configure router policy-options policy-statement entry from flow-spec-dest
Description
This command is used to match BGP FlowSpec routes on the basis of the destination IP prefix in the flow specification. An IPv4 FlowSpec route is matched by this command if its NLRI contains a type 1 subcomponent encoding a prefix and prefix-length that is covered by an entry in the referenced prefix-list. An IPv6 FlowSpec route is matched by this command if its NLRI contains a type 1 component encoding prefix-offset=0 and a prefix & prefix-length that is covered by an entry in the referenced prefix-list.
The flow-spec-dest command has no effect when the policy is not applied as a BGP import or export policy.
Default
no flow-spec-dest
Parameters
- prefix-list-name
-
Specifies the name of a prefix-list containing IPv4 and/or IPv6 prefix entries [up to 64 characters].
Platforms
All
flow-spec-source
flow-spec-source
Syntax
flow-spec-source prefix-list-name
no flow-spec-source
Context
[Tree] (config>router>policy-options>policy-statement>entry>from flow-spec-source)
Full Context
configure router policy-options policy-statement entry from flow-spec-source
Description
This command is used to match BGP FlowSpec routes on the basis of the source IP prefix in the flow specification. An IPv4 FlowSpec route is matched by this command if its NLRI contains a type 2 subcomponent encoding a prefix and prefix-length that is covered by an entry in the referenced prefix-list. An IPv6 FlowSpec route is matched by this command if its NLRI contains a type 2 component encoding prefix-offset=0 and a prefix & prefix-length that is covered by an entry in the referenced prefix-list.
The flow-spec-source command has no effect when the policy is not applied as a BGP import or export policy.
Default
no flow-spec-source
Parameters
- prefix-list-name
-
Specifies the name of a prefix-list containing IPv4 and/or IPv6 prefix entries, up to 64 characters.
Platforms
All
flow-table-high-wmark
flow-table-high-wmark
Syntax
flow-table-high-wmark high-watermark
no flow-table-high-wmark
Context
[Tree] (config>app-assure flow-table-high-wmark)
Full Context
configure application-assurance flow-table-high-wmark
Description
This command configures the system-wide high watermark threshold as a percentage of the flow table size for the per-ISA utilization of the flow records when a full alarm will be raised by the agent.
Default
flow-table-high-wmark 95
Parameters
- high-watermark
-
Specifies the high watermark for flow table full alarms, in percent.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-table-low-wmark
flow-table-low-wmark
Syntax
flow-table-low-wmark low-watermark
no flow-table-low-wmark
Context
[Tree] (config>app-assure flow-table-low-wmark)
Full Context
configure application-assurance flow-table-low-wmark
Description
This command configures the system-wide low watermark threshold as a percentage of the flow table size for per-ISA. The value must be lower than or equal to the flow-table-high-wmark high-watermark parameter.
Default
flow-table-low-wmark 90
Parameters
- low-watermark
-
Specifies the low watermark for flow table full alarms, in percent.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flow-timeout-on-switchover
flow-timeout-on-switchover
Syntax
flow-timeout-on-switchover percent
Context
[Tree] (config>isa>nat-group>inter-chassis-redundancy flow-timeout-on-switchover)
Full Context
configure isa nat-group inter-chassis-redundancy flow-timeout-on-switchover
Description
This command configures an initial flow timeout on the newly activated node for the nat-group after a switchover. This timeout stays in effect only if there is no traffic present over this flow; otherwise, the first packet over the flow after the switchover resets the flow timeout to the originally configured value (under the NAT policy configuration).
This command configuration restricts the flow timeout to a portion of the originally configured value.
Default
flow-timeout-on-switchover 50
Parameters
- percent
-
Specifies the percentage of the originally configured timeout value for the flow under the nat-policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flows-active-count
flows-active-count
Syntax
[no] flows-active-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr flows-active-count)
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr flows-active-count)
Full Context
configure log accounting-policy custom-record aa-specific from-aa-sub-counters flows-active-count
configure log accounting-policy custom-record aa-specific to-aa-sub-counters flows-active-count
Description
This command includes the active flow count and only applies to the 7750 SR.
The no form of this command excludes the active flow count in the AA subscriber's custom record.
Default
no flows-active-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flows-admitted-count
flows-admitted-count
Syntax
[no] flows-admitted-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr flows-admitted-count)
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr flows-admitted-count)
Full Context
configure log accounting-policy custom-record aa-specific to-aa-sub-counters flows-admitted-count
configure log accounting-policy custom-record aa-specific from-aa-sub-counters flows-admitted-count
Description
This command includes the admitted flow count and only applies to the 7750 SR.
The no form of this command excludes the flow’s admitted count in the AA subscriber's custom record.
Default
no flows-admitted-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flows-denied-count
flows-denied-count
Syntax
[no] flows-denied-count
Context
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr flows-denied-count)
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr flows-denied-count)
Full Context
configure log accounting-policy custom-record aa-specific from-aa-sub-counters flows-denied-count
configure log accounting-policy custom-record aa-specific to-aa-sub-counters flows-denied-count
Description
This command includes the flow’s denied count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of this command excludes the flow’s denied count.
Default
no flows-denied-count
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
flowspec
flowspec
Syntax
[no] flowspec
Context
[Tree] (config>service>vprn>if>spoke-sdp>ingress flowspec)
[Tree] (config>service>vprn>if>sap>ingress flowspec)
[Tree] (config>service>ies>if>spoke-sdp>ingress flowspec)
[Tree] (config>service>ies>if>sap>ingress flowspec)
Full Context
configure service vprn interface spoke-sdp ingress flowspec
configure service vprn interface sap ingress flowspec
configure service ies interface spoke-sdp ingress flowspec
configure service ies interface sap ingress flowspec
Description
This command enables IPv4 FlowSpec filtering on an access IP interface associated with a VPRN or IES service. Filtering is based on all of the IPv4 FlowSpec routes that have been received and accepted by the corresponding BGP instance. Ingress IPv4 traffic on an interface can be filtered by both a user-defined IPv4 filter and FlowSpec. Evaluation proceeds in this order:
-
user-defined IPv4 filter entries
-
FlowSpec derived filter entries
-
user-defined IPv4 filter default-action
The no form of this command removes IPv4 FlowSpec filtering from an IP interface.
Default
no flowspec. No access interfaces have IPv4 FlowSpec enabled.
Platforms
All
flowspec
Syntax
flowspec
Context
[Tree] (config>service>vprn flowspec)
Full Context
configure service vprn flowspec
Description
Commands in this context configure FlowSpec related parameters for the specified routing instance.
Platforms
All
flowspec
Syntax
flowspec
Context
[Tree] (config>service>vprn>bgp flowspec)
Full Context
configure service vprn bgp flowspec
Description
The context to enable and disable FlowSpec validations.
Platforms
All
flowspec
Syntax
flowspec
Context
[Tree] (config>router flowspec)
Full Context
configure router flowspec
Description
Commands in this context configure FlowSpec related parameters for the specified routing instance.
Platforms
All
flowspec
Syntax
flowspec
Context
[Tree] (config>router>bgp flowspec)
Full Context
configure router bgp flowspec
Description
Commands in this context enable and disable FlowSpec validations.
Platforms
All
flowtable
flowtable
Syntax
[no] flowtable of-table-id
Context
[Tree] (config>open-flow>of-switch flowtable)
Full Context
configure open-flow of-switch flowtable
Description
This command configures the flow table parameters for this OpenFlow switch instance.
The no form of this command restores flow table configuration default settings.
Default
no flowtable
Parameters
- of-table-id
-
Specifies an identifier of the open flow table, a string up to 256 characters.
Platforms
All
flr-threshold
flr-threshold
Syntax
flr-threshold percentage
no flr-threshold
Context
[Tree] (config>oam-pm>session>ethernet>lmm>availability flr-threshold)
[Tree] (config>oam-pm>session>ethernet>slm flr-threshold)
Full Context
configure oam-pm session ethernet lmm availability flr-threshold
configure oam-pm session ethernet slm flr-threshold
Description
This command defines the frame loss threshold used to determine whether the delta-t is available or unavailable. An individual delta-t with a frame loss threshold equal to the configured threshold is marked unavailable. An individual delta-t with a frame loss threshold lower than the configured threshold is marked as available.
The no form of this command restores the default value of 50%.
Parameters
- percentage
-
Specifies the percentage of the threshold.
Platforms
All
flr-threshold
Syntax
flr-threshold percentage
no flr-threshold
Context
[Tree] (config>oam-pm>session>ip>twamp-light>loss flr-threshold)
Full Context
configure oam-pm session ip twamp-light loss flr-threshold
Description
This command defines the frame loss threshold used to determine whether the delta-t is available or unavailable. An individual delta-t with a frame loss threshold equal to or higher than the configured threshold is marked unavailable. An individual delta-t with a frame loss threshold lower than the configured threshold is marked as available.
The no form of this command restores the default value of 50%.
Default
flr-threshold 50
Parameters
- percentage
-
Specifies the percentage of the threshold.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fng-alarm-time
fng-alarm-time
Syntax
fng-alarm-time time
Context
[Tree] (config>eth-ring>path>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>lag>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>eth-tunnel>path>eth-cfm>mep>alarm-notification fng-alarm-time)
Full Context
configure eth-ring path eth-cfm mep alarm-notification fng-alarm-time
configure lag eth-cfm mep alarm-notification fng-alarm-time
configure eth-tunnel path eth-cfm mep alarm-notification fng-alarm-time
Description
This command configures the Fault Notification Generation (FNG) alarm time.
Parameters
- time
-
The length of time, in centi-seconds, that must expire before a defect is alarmed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fng-alarm-time
Syntax
fng-alarm-time time
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vpls>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vprn>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>lag>eth-cfm>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>router>if>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>epipe>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>port>ethernet>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>ipipe>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>ies>if>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>alarm-notification fng-alarm-time)
[Tree] (config>service>vpls>eth-cfm>mep>alarm-notification fng-alarm-time)
Full Context
configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-alarm-time
configure service vpls sap eth-cfm mep alarm-notification fng-alarm-time
configure service vpls mesh-sdp eth-cfm mep alarm-notification fng-alarm-time
configure service vprn sap eth-cfm mep alarm-notification fng-alarm-time
configure service vprn interface spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
configure lag eth-cfm eth-cfm mep alarm-notification fng-alarm-time
configure service vprn interface sap eth-cfm mep alarm-notification fng-alarm-time
configure router interface eth-cfm mep alarm-notification fng-alarm-time
configure service epipe sap eth-cfm mep alarm-notification fng-alarm-time
configure service ies interface spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
configure service vpls spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
configure port ethernet eth-cfm mep alarm-notification fng-alarm-time
configure service epipe spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
configure service ipipe sap eth-cfm mep alarm-notification fng-alarm-time
configure service ies interface sap eth-cfm mep alarm-notification fng-alarm-time
configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-alarm-time
configure service vpls eth-cfm mep alarm-notification fng-alarm-time
Description
This command is used to configure the Fault Notification Generation time values for raising the alarm. This timer is used for network management processes and is not tied into delaying the notification to the fault management system on the network element. This timer does not affect fault propagation mechanisms.
Parameters
- time
-
Specifies the time, in centiseconds (10ms intervals), that a defect condition at or above the low-priority-defect must be present before raising alarm.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-alarm-time
- configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-alarm-time
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vpls mesh-sdp eth-cfm mep alarm-notification fng-alarm-time
- configure service vprn interface spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
- configure port ethernet eth-cfm mep alarm-notification fng-alarm-time
- configure service epipe sap eth-cfm mep alarm-notification fng-alarm-time
- configure service ies interface spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
- configure service vpls sap eth-cfm mep alarm-notification fng-alarm-time
- configure service vpls eth-cfm mep alarm-notification fng-alarm-time
- configure service vpls spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
- configure router interface eth-cfm mep alarm-notification fng-alarm-time
- configure service ies interface sap eth-cfm mep alarm-notification fng-alarm-time
- configure service epipe spoke-sdp eth-cfm mep alarm-notification fng-alarm-time
- configure service ipipe sap eth-cfm mep alarm-notification fng-alarm-time
- configure service vprn interface sap eth-cfm mep alarm-notification fng-alarm-time
fng-alarm-time
Syntax
fng-alarm-time time
Context
[Tree] (config>router>if>eth-cfm>mep fng-alarm-time)
Full Context
configure router interface eth-cfm mep fng-alarm-time
Description
This command configures the Fault Notification Generation (FNG) alarm time.
Parameters
- time
-
The length of time, in centi-seconds, that must pass before an alarm is raised for a defect.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fng-reset-time
fng-reset-time
Syntax
fng-reset-time time
Context
[Tree] (config>eth-ring>path>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>eth-tunnel>path>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>lag>eth-cfm>mep>alarm-notification fng-reset-time)
Full Context
configure eth-ring path eth-cfm mep alarm-notification fng-reset-time
configure eth-tunnel path eth-cfm mep alarm-notification fng-reset-time
configure lag eth-cfm mep alarm-notification fng-reset-time
Description
This command configure the Fault Notification Generation (FNG) reset time.
Parameters
- time
-
The length of time, in centiseconds, that must expire before a defect is reset.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fng-reset-time
Syntax
fng-reset-time time
Context
[Tree] (config>service>ies>if>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>router>if>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>port>ethernet>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>ipipe>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vpls>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>epipe>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vprn>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>lag>eth-cfm>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vpls>sap>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>alarm-notification fng-reset-time)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>alarm-notification fng-reset-time)
Full Context
configure service ies interface sap eth-cfm mep alarm-notification fng-reset-time
configure router interface eth-cfm mep alarm-notification fng-reset-time
configure service vpls mesh-sdp eth-cfm mep alarm-notification fng-reset-time
configure port ethernet eth-cfm mep alarm-notification fng-reset-time
configure service ipipe sap eth-cfm mep alarm-notification fng-reset-time
configure service epipe spoke-sdp eth-cfm mep alarm-notification fng-reset-time
configure service vpls eth-cfm mep alarm-notification fng-reset-time
configure service ies interface spoke-sdp eth-cfm mep alarm-notification fng-reset-time
configure service epipe sap eth-cfm mep alarm-notification fng-reset-time
configure service vprn sap eth-cfm mep alarm-notification fng-reset-time
configure lag eth-cfm eth-cfm mep alarm-notification fng-reset-time
configure service vprn interface spoke-sdp eth-cfm mep alarm-notification fng-reset-time
configure service vprn interface sap eth-cfm mep alarm-notification fng-reset-time
configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-reset-time
configure service vpls sap eth-cfm mep alarm-notification fng-reset-time
configure service vpls spoke-sdp eth-cfm mep alarm-notification fng-reset-time
configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-reset-time
Description
This command configures the Fault Notification Generation time values to reset the CCM defect alarm. This timer is used for network management processes and is not tied into delaying the notification to the fault management system on the network element. This timer does not affect fault propagation mechanisms.
Parameters
- time
-
Specifies the time, in centiseconds (10ms intervals), that a defect condition at or above the low-priority-defect must be cleared before resetting the alarm.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface sap eth-cfm mep alarm-notification fng-reset-time
- configure service ipipe sap eth-cfm mep alarm-notification fng-reset-time
- configure service vpls mesh-sdp eth-cfm mep alarm-notification fng-reset-time
- configure service epipe sap eth-cfm mep alarm-notification fng-reset-time
- configure router interface eth-cfm mep alarm-notification fng-reset-time
- configure service vprn interface spoke-sdp eth-cfm mep alarm-notification fng-reset-time
- configure service epipe spoke-sdp eth-cfm mep alarm-notification fng-reset-time
- configure service vpls eth-cfm mep alarm-notification fng-reset-time
- configure service ies interface spoke-sdp eth-cfm mep alarm-notification fng-reset-time
- configure service ies interface sap eth-cfm mep alarm-notification fng-reset-time
- configure port ethernet eth-cfm mep alarm-notification fng-reset-time
- configure service vpls sap eth-cfm mep alarm-notification fng-reset-time
- configure service vpls spoke-sdp eth-cfm mep alarm-notification fng-reset-time
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-reset-time
- configure service vprn subscriber-interface group-interface sap eth-cfm mep alarm-notification fng-reset-time
fng-reset-time
Syntax
fng-reset-time time
Context
[Tree] (config>router>if>eth-cfm>mep fng-reset-time)
Full Context
configure router interface eth-cfm mep fng-reset-time
Description
This command configures the FNG reset time.
Parameters
- time
-
The length of time, in centiseconds, that must expire before a defect is reset.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
follow
follow
Syntax
follow router router-instance pool name
no follow
Context
[Tree] (config>service>vprn>nat>outside>pool>redundancy follow)
[Tree] (config>router>nat>outside>pool>redundancy follow)
Full Context
configure service vprn nat outside pool redundancy follow
configure router nat outside pool redundancy follow
Description
This command implicitly enables Pool Fate-Sharing Group (PFSG) which is required in case of multiple NAT policies per inside routing context. A NAT pool configured with this command will not advertise or monitor any route in order to change its (activity) state but instead it will directly follow the state of the lead pool in the PFSG. Once the lead pool changes its (activity) state, all the remaining pools following the lead pool will change their state accordingly.
Default
no follow
Parameters
- router router-instance
-
Specifies the routing instance where the lead pool resides.
- pool name
-
Specifies the pool whose activity state is being shared up to 32 characters in length.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
force-auth
force-auth
Syntax
force-auth [cid-change] [rid-change]
force-auth disabled
no force-auth
Context
[Tree] (config>service>vprn>sub-if>grp-if>ipoe-session force-auth)
[Tree] (config>service>ies>sub-if>grp-if>ipoe-session force-auth)
Full Context
configure service vprn subscriber-interface group-interface ipoe-session force-auth
configure service ies subscriber-interface group-interface ipoe-session force-auth
Description
By default, if the circuit-id/interface-id or remote-id in the IPoE session re-authentication trigger packet (such as a DHCP renewal) is not empty and different from the circuit-id/interface-id or remote-id stored in the IPoE session data, a forced re-authentication is performed, ignoring the configured min-auth-interval. This default behavior can be changed with this command.
The no form of this command reverts to the default behavior.
Default
force-auth cid-change rid-change force-auth disabled on wlan-gw group interfaces
Parameters
- cid-change
-
Perform a forced re-authentication upon a circuit-id/interface-id change. An empty circuit-id/interface-id is not considered a change.
- rid-change
-
Perform a forced re-authentication upon a remote-id change. an empty remote-id is not considered a change. For DHCPv6, the enterprise number is excluded from the comparison.
- disabled
-
Specifies that the min-auth-interval never is ignored. The system does not perform a forced re-authentication upon a circuit-id or interface-id or remote-id change.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
force-ipv6cp
force-ipv6cp
Syntax
[no] force-ipv6cp
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host force-ipv6cp)
Full Context
configure subscriber-mgmt local-user-db ppp host force-ipv6cp
Description
This command specifies if the IPv6 control protocol should be negotiated after PPP reaches the Network-Layer Protocol phase.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
force-l2pt-boundary
force-l2pt-boundary
Syntax
force-l2pt-boundary [cdp] [dtp] [pagp] [ stp] [udld] [vtp]
no force-l2pt-boundary
Context
[Tree] (config>service>vpls>sap force-l2pt-boundary)
Full Context
configure service vpls sap force-l2pt-boundary
Description
Enabling force-l2pt-boundary will force all SAPs managed by the specified m-vpls instance on the corresponding port to have l2pt-termination enabled. This command is applicable only to SAPs created under m-vpls regardless of the flavor of STP currently active. It is not applicable to spoke-SDPs.
The execution of this command will fail as soon as at least one of the currently managed SAPs (all SAPs falling within the specified managed-vlan-range) does not have l2pt-termination enabled regardless of its admin/operational status.
If force-l2pt-boundary is enabled on a specified m-vpls SAP, all newly created SAPs falling into the specified managed-vlan-range will have l2pt-termination enabled per default.
Extending or adding new range into a managed-vlan-range declaration will fail as soon as there is at least one SAPs falling into the specified vlan-range does not have l2pt-termination enabled.
Disabling l2pt-termination on currently managed SAPs will fail as soon as the force-l2pt-boundary is enabled under corresponding m-vpls SAP.
Parameters
- cdp
-
Specifies the Cisco discovery protocol
- dtp
-
Specifies the dynamic trunking protocol
- pagp
-
Specifies the port aggregation protocol
- stp
-
Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default)
- udld
-
Specifies unidirectional link detection
- vtp
-
Specifies the virtual trunk protocol
Platforms
All
force-mcast
force-mcast
Syntax
force-mcast [ip] [mac]
no force-mcast
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6 force-mcast)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 force-mcast)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv force-mcast)
[Tree] (config>subscr-mgmt>rtr-adv-plcy force-mcast)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv force-mcast)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv force-mcast)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv force-mcast)
Full Context
configure service ies subscriber-interface group-interface ipv6 force-mcast
configure service vprn subscriber-interface group-interface ipv6 force-mcast
configure service vprn subscriber-interface group-interface ipv6 router-advertisements force-mcast
configure subscriber-mgmt router-advertisement-policy force-mcast
configure service ies subscriber-interface group-interface ipv6 router-advertisements force-mcast
configure service ies subscriber-interface ipv6 router-advertisements force-mcast
configure service vprn subscriber-interface ipv6 router-advertisements force-mcast
Description
This command configures the protocols with forced multicast, either IP or MAC.
The no form of this command returns the command to the default setting.
Parameters
- ip
-
Specifies that IP for multicast is forced.
- mac
-
Specifies that MAC for multicast is forced.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
force-ppp-mtu-gt-1492
force-ppp-mtu-gt-1492
Syntax
[no] force-ppp-mtu-gt-1492
Context
[Tree] (config>subscr-mgmt>ppp-policy force-ppp-mtu-gt-1492)
Full Context
configure subscriber-mgmt ppp-policy force-ppp-mtu-gt-1492
Description
This command enables PPPoE Maximum-Receive-Unit (MRU) negotiations greater than 1492 bytes without the need to receive a "PPP-Max-Payload” tag in PADI/PADR from the client as defined in RFC 4638, Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE).
The MRU send in the initial LCP Config Request is determined by the port mtu and ppp-policy ppp-mtu parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
force-qinq-vc-forwarding
force-qinq-vc-forwarding
Syntax
force-qinq-vc-forwarding [{c-tag-c-tag | s-tag-c-tag}]
no force-qinq-vc-forwarding
Context
[Tree] (config>service>epipe>bgp-evpn>mpls force-qinq-vc-forwarding)
[Tree] (config>service>pw-template force-qinq-vc-forwarding)
[Tree] (config>service>vpls>mesh-sdp force-qinq-vc-forwarding)
[Tree] (config>service>vpls>spoke-sdp force-qinq-vc-forwarding)
[Tree] (config>service>vpls>bgp-evpn>mpls force-qinq-vc-forwarding)
[Tree] (config>service>vpls>bgp-evpn>srv6 force-qinq-vc-forwarding)
[Tree] (config>service>epipe>spoke-sdp force-qinq-vc-forwarding)
Full Context
configure service epipe bgp-evpn mpls force-qinq-vc-forwarding
configure service pw-template force-qinq-vc-forwarding
configure service vpls mesh-sdp force-qinq-vc-forwarding
configure service vpls spoke-sdp force-qinq-vc-forwarding
configure service vpls bgp-evpn mpls force-qinq-vc-forwarding
configure service vpls bgp-evpn segment-routing-v6 force-qinq-vc-forwarding
configure service epipe spoke-sdp force-qinq-vc-forwarding
Description
This command forces the datapath to push two VLAN tags at network egress when sending traffic on SDP bindings or EVPN destinations. The VLAN tag values are derived from the service-delimiting tags at the ingress, depending on the configured parameter. At network ingress this command, configured on EVPN-MPLS or the SDP-binding, pops two VLAN tags at most.
The no form of this command disables the datapath from pushing any VLAN tags in SDP bindings or EVPN, or from popping two VLAN tags.
Default
no force-qinq-vc-forwarding
Parameters
- c-tag-c-tag
-
Specifies that the router pushes two tags with the same value derived from the inner service delimiting tag. At network ingress, two VLAN tags are extracted at most and the C-tag and S-tag p/de bits are propagated to the egress SAPs.
- s-tag-c-tag
-
Specifies that the router pushes two tags that are copied from the QinQ service-delimiting VLAN values and may be different. At network ingress, two VLAN tags are extracted at most and the p/de bits are propagated to the egress SAP service-delimiting S-tag and C-tag respectively.
Platforms
All
- configure service vpls spoke-sdp force-qinq-vc-forwarding
- configure service pw-template force-qinq-vc-forwarding
- configure service vpls mesh-sdp force-qinq-vc-forwarding
- configure service epipe spoke-sdp force-qinq-vc-forwarding
- configure service epipe bgp-evpn mpls force-qinq-vc-forwarding
- configure service vpls bgp-evpn mpls force-qinq-vc-forwarding
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
- configure service vpls bgp-evpn segment-routing-v6 force-qinq-vc-forwarding
force-qtag-forwarding
force-qtag-forwarding
Syntax
[no] force-qtag-forwarding
Context
[Tree] (config>service>vpls>pbb force-qtag-forwarding)
Full Context
configure service vpls pbb force-qtag-forwarding
Description
This command forces the addition of a IEEE 802.1q tag after the Customer MAC (C-MAC) addresses when the PBB header is built, as it egresses a related BVPLS.
It is used to preserve the dot1q and DE bits from the customer domain when the service delimiting qtags are stripped when the packet is ingressing a PBB Epipe or an IVPLS. The VLAN value of the service delimiting qtag if one exists is used for the corresponding inserted dot1q field. If a service delimiting qtag does not exist, then the value of zero is used for all the inserted qtag bits.
The no form of this command sets default behavior.
Default
no force-qtag-forwarding
Platforms
All
force-qtag-forwarding
Syntax
[no] force-qtag-forwarding
Context
[Tree] (config>service>epipe>pbb force-qtag-forwarding)
Full Context
configure service epipe pbb force-qtag-forwarding
Description
This command forces the addition of a IEEE 802.1q tag after the Customer MAC (C-MAC) addresses when the PBB header is built, as it egresses a related BVPLS.
It is used to preserve the dot1q and DE bits from the customer domain when the service delimiting qtags are stripped when the packet is ingressing a PBB Epipe or an IVPLS. The VLAN value of the service delimiting qtag if one exists is used for the corresponding inserted dot1q field. If a service delimiting qtag does not exist, then the value of zero is used for all the inserted qtag bits.
The no form of this command sets default behavior.
Default
no force-qtag-forwarding
Platforms
All
force-reference
force-reference
Syntax
force-reference {ref1 | ref2 | bits | bitsa | bitsb | gnss | gnssa | gnssb | ptp | synce | syncea | synceb}
no force-reference
Context
[Tree] (debug>sync-if-timing force-reference)
Full Context
debug sync-if-timing force-reference
Description
This command forces the system synchronous timing output to use a specific reference.
The list of available references may vary depending on the platform; all references are not supported on every platform.
Only use this command to test and debug problems. Network synchronization problems may appear if you leave network elements with this manual override setting. After forcing the system timing reference input, clear it using the no force-reference command.
This command also clears the Wait-to-Restore state of the reference so that the reference can be selected.
This command can also force the CPM clock to use a specific input reference.
When the command is executed, the CPM clock on the active CPM immediately switches its input reference to that specified by the command. If the specified input is not available (shutdown), or in a disqualified state, the CPM clock shall use the next qualified input reference based on the selection rules.
This command also affects the BITS output port on the active CPM. If the BITS output port selection is set to line-reference and the reference being forced is not the BITS input port, then the system uses the forced reference to generate the signal out the BITS output port. If the BITS output port selection is set to internal-clock, then the system uses the output of the CPM clock to generate the signal for the BITS output port.
On a CPM activity switch, the force command is cleared and normal reference selection is determined.
Debug configurations are not saved between reboots.
Parameters
- ref1
-
Specifies that the clock uses the first timing reference.
- ref2
-
Specifies that the clock uses the second timing reference.
- bits
-
Specifies that the clock uses the external network interface on the active CPM to be the highest priority input.
- bitsa
-
Specifies that the clock uses the bitsa timing reference, for redundant systems with a BITS port on each CPM.
- bitsb
-
Specifies that the clock uses the bitsb timing reference, for redundant systems with a BITS port on each CPM.
- gnss
-
Specifies that the clock uses the GNSS port as a timing reference. This keyword is supported only on 7750 SR single-slot platforms.
- gnssa
-
Specifies that the clock uses the GNSS port on the CPM in slot A as a timing reference. This keyword is supported only on 7750 SR-2e platforms.
- gnssb
-
Specifies that the clock uses the GNSS port on the CPM in slot B as a timing reference. This keyword is supported only on 7750 SR-2e platforms.
- ptp
-
Specifies that the clock uses the PTP timeReceiver as the timing reference. This keyword is supported on 7450 ESS and 7750 SR platforms.
- synce
-
Specifies that the clock uses the SyncE/1588 timing reference on non-redundant systems.
- syncea
-
Specifies that the clock uses the SyncE/1588 timing reference on CPM A of redundant systems.
- synceb
-
Specifies that the clock uses the SyncE/1588 timing reference on CPM B of redundant systems.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
force-renews
force-renews
Syntax
[no] force-renews
Context
[Tree] (config>router>dhcp>server force-renews)
[Tree] (config>service>vprn>server force-renews)
Full Context
configure router dhcp local-dhcp-server force-renews
configure service vprn server force-renews
Description
This command enables the sending of sending FORCERENEW messages for DHCP.
The no form of this command disables the sending of FORCERENEW messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
force-switchover
force-switchover
Syntax
force-switchover [now] [ignore-status]
Context
[Tree] (admin>redundancy force-switchover)
Full Context
admin redundancy force-switchover
Description
This command forces a switchover to the standby CPM card. The primary CPM reloads its software image and becomes the secondary CPM.
Parameters
- now
-
Forces the switchover to the redundant CPM card immediately.
- ignore-status
-
Forces a switchover despite any diagnostics or conditions on the standby. This is true even if the standby cannot reach the extension CPMs on the extension chassis of a 7950 XRS-40 via its local CPM interconnect ports.
This option is supported on 7950 XRS-20 and 7950 XRS-40 platforms only.
Platforms
All
force-unique-ip-addresses
force-unique-ip-addresses
Syntax
[no] force-unique-ip-addresses
Context
[Tree] (config>router>nat>inside>l2-aware force-unique-ip-addresses)
[Tree] (config>service>vprn>nat>inside>l2-aware force-unique-ip-addresses)
Full Context
configure router nat inside l2-aware force-unique-ip-addresses
configure service vprn nat inside l2-aware force-unique-ip-addresses
Description
This command enforces the uniqueness of IPv4 addresses of L2-aware subscribers in an inside routing context.
This functionality is required if multicast sourced from the inside routing context is enabled for L2-aware subscribers.
The no form of this command allows L2-aware subscribers to have overlapping IPv4 addresses.
Default
no force-unique-ip-addresses
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
force-vlan-vc-forwarding
force-vlan-vc-forwarding
Syntax
[no] force-vlan-vc-forwarding
Context
[Tree] (config>service>epipe>bgp-evpn>srv6 force-vlan-vc-forwarding)
[Tree] (config>service>epipe>bgp-evpn>mpls force-vlan-vc-forwarding)
[Tree] (config>service>vpls>bgp-evpn>mpls force-vlan-vc-forwarding)
[Tree] (config>service>vpls>bgp-evpn>srv6 force-vlan-vc-forwarding)
Full Context
configure service epipe bgp-evpn segment-routing-v6 force-vlan-vc-forwarding
configure service epipe bgp-evpn mpls force-vlan-vc-forwarding
configure service vpls bgp-evpn mpls force-vlan-vc-forwarding
configure service vpls bgp-evpn segment-routing-v6 force-vlan-vc-forwarding
Description
This command enables the system to preserve the VLAN ID and 802.1p bits of the service-delimiting qtag in a new tag, which is sent in the customer frame to the EVPN destinations.
If this configuration is used in conjunction with the sap ingress vlan-translation command, the configured translated VLAN ID is the VLAN ID sent to the EVPN destinations, instead of the service-delimiting tag VLAN ID. If the ingress SAP or SDP binding is null-encapsulated, the output VLAN ID and p-bits are zero.
The no form of this command does not preserve the VLAN ID and 802.1p bits of the service-delimiting qtag.
Default
no force-vlan-vc-forwarding
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
- configure service epipe bgp-evpn segment-routing-v6 force-vlan-vc-forwarding
- configure service vpls bgp-evpn segment-routing-v6 force-vlan-vc-forwarding
All
- configure service vpls bgp-evpn mpls force-vlan-vc-forwarding
- configure service epipe bgp-evpn mpls force-vlan-vc-forwarding
force-vlan-vc-forwarding
Syntax
[no] force-vlan-vc-forwarding
Context
[Tree] (config>service>epipe>spoke-sdp force-vlan-vc-forwarding)
[Tree] (config>service>vpls>mesh-sdp force-vlan-vc-forwarding)
[Tree] (config>service>vpls>spoke-sdp force-vlan-vc-forwarding)
Full Context
configure service epipe spoke-sdp force-vlan-vc-forwarding
configure service vpls mesh-sdp force-vlan-vc-forwarding
configure service vpls spoke-sdp force-vlan-vc-forwarding
Description
This command forces vc-vlan-type forwarding in the datapath for spoke and mesh SDPs which have either vc-type. This command is not allowed on vlan-vc-type SDPs.
The no version of this command sets default behavior.
Default
no force-vlan-vc-forwarding
Platforms
All
foreign-ip
foreign-ip
Syntax
foreign-ip ip-address[/mask]
no foreign-ip
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>match foreign-ip)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry match foreign-ip
Description
This command configures the foreign IP address or subnet in the match criterion for this entry. The foreign IP or subnet implies a matching destination IP for upstream traffic and a source IP for downstream traffic.
The no form of this command removes the IP address or subnet from the match criterion in the entry.
Parameters
- ip-address/mask
-
Specifies the IPv4 address and mask.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
foreign-ip
Syntax
[no] foreign-ip
Context
[Tree] (config>service>nat>syslog>syslog-export-policy>include foreign-ip)
Full Context
configure service nat syslog syslog-export-policy include foreign-ip
Description
This command includes the foreign IP address in the flow log. A foreign IP address is the original IP address toward the destination node and in DNAT it is replaced by the destination IP.
If DNAT is not used, the foreign IP address (the IP address of the destination node) is the same on both sides of NAT.
The no form of the command disables the feature.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
foreign-ip
Syntax
foreign-ip ip-address
no foreign-ip
Context
[Tree] (config>service>nat>nat-classifier>entry>match foreign-ip)
Full Context
configure service nat nat-classifier entry match foreign-ip
Description
This command specifies matching on a foreign IP, that is the destination IP address of the NAT inside service before translation.
Default
no foreign-ip
Parameters
- ip-address
-
Specifies the foreign IP address.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
foreign-port
foreign-port
Syntax
foreign-port port
no foreign-port
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>match foreign-port)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry match foreign-port
Description
This command configures the foreign TCP/UDP port to match in this entry of the VAS filter.
The no form of this command
Parameters
- port
-
Specifies the foreign IP port to match.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
foreign-port
Syntax
[no] foreign-port
Context
[Tree] (config>service>nat>syslog>syslog-export-policy>include foreign-port)
Full Context
configure service nat syslog syslog-export-policy include foreign-port
Description
This command includes the foreign port address in the flow log. A foreign port is the port towards the destination node and this port is not translated by any form of NAT.
A foreign port (the port towards the destination node) is the same on both sides of NAT.
The no form of the command disables the feature.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
format
format
Syntax
format [cflash-id] [reliable]
Context
[Tree] (file format)
Full Context
file format
Description
This command formats the compact flash. The compact flash must be shut down before starting the format.
Parameters
- cflash-id
-
Specifies the compact flash type.
- reliable
-
Enables the reliance file system and disables the default DoS file system. This option is valid only on compact flashes 1 and 2.
Platforms
All
forward
forward
Syntax
forward
forward sf-ip ip-address | ipv6-address svc service-id [esi esi]
no forward
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>action forward)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry action forward
Description
This command configures the forward action.
The no form of this command removes the parameters from the configuration.
Parameters
- ip-address
-
Specifies forwarding the SF IPv4 address for the action in a VAS filter entry.
- ipv6-address
-
Specifies forwarding the SF IPv6 address for the action in a VAS filter entry.
- service-id
-
Specifies the service ID.
- esi
-
Specifies the ESI for the action in a VAS filter entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
forward
Syntax
forward
forward bonding-connection connection-id
IPv4: forward esi esi sf-ip ip-address vas-interface interface-name router router-instance
IPv6: forward esi esi sf-ip ipv6-address vas-interface interface-name router router-instance
IPv4: forward esi esi sf-ip ip-address vas-interface interface-name router service-name service-name
IPv6: forward esi esi sf-ip ipv6-address vas-interface interface-name router service-name service-name
forward esi esi service-id vpls-service-id
forward gre-tunnel gre-tunnel-name
forward lsp lsp-name
IPv4: forward mpls-policy ip-address
IPv6: forward mpls-policy ipv6-address
IPv4: forward next-hop ip-address
IPv6: forward next-hop ipv6-address
IPv4: forward next-hop ip-address router router-instance
IPv6: forward next-hop ipv6-address router router-instance
IPv4: forward next-hop ip-address router service-name service-name
IPv6: forward next-hop ipv6-address router service-name service-name
IPv4: forward next-hop indirect ip-address
IPv6: forward next-hop indirect ipv6-address
IPv4: forward next-hop indirect ip-address router router-instance
IPv6: forward next-hop indirect ipv6-address router router-instance
IPv4: forward next-hop indirect ip-address router service-name service-name
IPv6: forward next-hop indirect ipv6-address router service-name service-name
forward next-hop interface ip-int-name
forward redirect-policy policy-name
forward router router-instance
forward router service-name service-name
forward sap sap-id
forward sdp sdp-id:vc-id
IPv4: forward srte-policy ip-address color color-id
IPv6: forward srte-policy ipv6-address color color-id
IPv4: forward srv6-policy ipv6-address color color-id service-sid ipv6-address
IPv6: forward srv6-policy ipv6-address color color-id service-sid ipv6-address
IPv4: forward vprn-target bgp-nh ip-address router router-instance [adv-prefix ip-address/mask] [ lsp lsp-name]
IPv6: forward vprn-target bgp-nh ip-address router router-instance [adv-prefix ipv6-address/prefix-length] [ lsp lsp-name]
IPv4: forward vprn-target bgp-nh ip-address router service-name service-name [adv-prefix ip-address/mask] [ lsp lsp-name]
IPv6: forward vprn-target bgp-nh ip-address router service-name service-name [adv-prefix ipv6-address/prefix-length] [ lsp lsp-name]
Context
[Tree] (config>filter>ipv6-filter>entry>action forward)
[Tree] (config>filter>ip-filter>entry>action forward)
Full Context
configure filter ipv6-filter entry action forward
configure filter ip-filter entry action forward
Description
This command sets the context for specific forward commands to be performed.
Parameters
- connection-id
-
Specifies that the packet should be forwarded over the specified connection (specified by the connection ID under the bonding group interface), if that connect is available. Outside of a bonding egress context, the behavior of this filter is undefined.
- esi service-id
-
Specifies that the packet matching the entry is forwarded to an ESI-identified first appliance in Nuage service chain using EVPN-resolved VXLAN tunnel in the specified VPLS service.
- esi sf-ip vas-interface router
-
Specifies that the packet matching the entry is forwarded to ESI/SF-IP identified first appliance in Nuage service chain using EVPN-resolved VXLAN tunnel over the configured VAS interface in the specified VPRN service.
- gre-tunnel-name
-
Specifies the GRE tunnel name up to 32 characters.
- lsp
-
Specifies that the packet matching the entry is forwarded using the specified lsp.
- mpls-policy
-
Specifies the redirection of the traffic to the programed instance of the MPLS FP specified by its endpoint IPv4 or IPv6 address. The behavior results in a simple forward if no policy exists, if no instance is programmed, and if the policy or instance is administratively down.
- next-hop
-
Specifies that the packet matching the entry is forwarded in the routing context of the incoming interface using direct or indirect IPv4 address in the routing lookup.
- next-hop router
-
Specifies that the packet matching the entry is forwarded in the configured routing context using direct or indirect IPv4 address in the routing lookup.
- next-hop interface
-
Specifies that the packet matching the entry is forwarded using the configured local interface.
- redirect-policy
-
Specifies that the packet matching the entry is forwarded using forward next-hop or forward next hop router and the IP address of destination selected by the configured redirect policy. If no destination is selected, packets are subject to action forward.
- router
-
Specifies that the packet matching the entry is routed in the configured routing instance and not in the incoming interface routing instance.
- sap
-
Specifies that the packet matching the entry is forwarded using the configured SAP.
- sdp
-
Specifies that the packet matching the entry is forwarded using the configured SDP.
- srte-policy
-
Specifies the redirection of the traffic to the programed instance of the SR-TE policy specified by its endpoint IPv4 address or IPv6 address and color. The behavior results in a simple forward if no policy exists, if no instance is programmed, and if the policy or instance is administratively down.
- color-id
-
Specifies the color identifier of the specified SR-TE policy.
- vprn-target
-
Specifies that the packet matching the entry is redirected towards a designated BGP next-hop ( bgp-nh). The user may specify an LSP (lsp lsp-name) to use towards that next-hop. If no LSP is specified, the system will automatically select one. The user must specify the routing context ( router {router-instance | service-name service-name}) in which the system will perform the lookups in order to derive the proper VPRN service label. The user may specify an advertised prefix route ( adv-prefix ip-address/prefix-length). This is needed in case label per VRF is not the label allocation method configured at the BGP peer.
- esi
-
Specifies a 10-byte Ethernet Segment Identifier.
- ip-address/mask
-
Specifies an IPv4 advertised route in the CIDR notation. The IPv4 address is in dotted decimal notation.
- ipv6-address/prefix-length
-
Specifies an IPv6 advertised route in the CIDR notation.
- bgp-nh ip-address
-
Specifies the IPv4 address (in dotted decimal notation) of the target BGP next-hop.
- ipv6-address
-
Specifies the IPv6 address of a direct or indirect next hop to forward matching packets or of the service SID to use with the SRv6 policy.
- ip-int-name
-
Specifies the name of an egress IP interface where matching packets will be forwarded from. This parameter is only valid for unnumbered point-to-point interfaces. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes.
- interface-name
-
Specifies the (maximum 32-character) name of an egress R-VPLS IP interface used to forward the packets using ESI redirect for VPRN/IES service.
- lsp-name
-
Specifies an existing RSVP-TE, MPLS-TP, or SR-TE LSP that supports LSP redirect.
- policy-name
-
Specifies an IPv4 redirect policy configured in the config>filter>redirect-policy context.
- sap-id
-
Specifies an existing VPLS Ethernet SAP.
- sdp-id:vc-id
-
Specifies an existing VPLS SDP.
- router-instance
-
Specifies "Base” or an existing VPRN service ID. For the forward vprn-target bgp-nh command, router-instance must specify an existing VPRN service ID.
- service-name
-
Specifies an existing VPRN service name.
- vpls-service-id
-
Specifies an existing VPLS service ID or service name.
Platforms
All
forward
Syntax
forward
forward esi esi service-id vpls-service-id
forward sap sap-id
forward sdp sdp-id:vc-id
Context
[Tree] (config>filter>mac-filter>entry>action forward)
Full Context
configure filter mac-filter entry action forward
Description
This command sets the context for specific forward commands to be performed.
Parameters
- esi
-
Specifies a 10-byte Ethernet Segment Identifier.
- service-id
-
Specifies that a packet matching the entry is forwarded to an ESI-identified first appliance in the Nuage service chain using an EVPN-resolved VXLAN tunnel in the specified VPLS service.
- vpls-service-id
-
Specifies an existing VPLS service ID or service name.
- sap
-
Specifies that the packet matching the entry is forwarded using the configured SAP.
- sap-id
-
Specifies an existing VPLS Ethernet SAP.
- sdp
-
Specifies that the packet matching the entry is forwarded using the configured SDP.
- sdp-id:vc-id
-
Specifies an existing VPLS SDP.
Platforms
All
forward-6in4
forward-6in4
Syntax
[no] forward-6in4
Context
[Tree] (config>system>ip forward-6in4)
Full Context
configure system ip forward-6in4
Description
This command enables forwarding of IPv6 traffic encapsulated in an IPv4 transport sent to the system IP address.
The no form of this command disables this option and returns the system to the default behavior.
Default
no forward-6in4
Platforms
All
forward-delay
forward-delay
Syntax
forward-delay forward-delay
no forward-delay [forward-delay]
Context
[Tree] (config>service>vpls>stp forward-delay)
[Tree] (config>service>template>vpls-template>stp forward-delay)
Full Context
configure service vpls stp forward-delay
configure service template vpls-template stp forward-delay
Description
RSTP, as defined in the IEEE 802.1D-2004 standards, will normally transition to the forwarding state via a handshaking mechanism (rapid transition), without any waiting times. If handshaking fails (e.g. on shared links, see below), the system falls back to the timer-based mechanism defined in the original STP (802.1D-1998) standard.
A shared link is a link with more than two nodes (for example, a shared 10/100BaseT segment). The port-type command is used to configure a link as point-to-point or shared.
For timer-based transitions, the 802.1D-2004 standard defines an internal variable forward-delay, which is used in calculating the default number of seconds that a SAP or spoke-SDP spends in the discarding and learning states when transitioning to the forwarding state.
The value of the forward-delay variable depends on the STP operating mode of the VPLS instance:
-
in rstp or mstp mode, but only when the SAP or spoke-SDP has not fallen back to legacy STP operation, the value configured by the hello-time command is used;
-
in all other situations, the value configured by the forward-delay command is used.
Default
forward-delay 15
Parameters
- seconds
-
The forward delay timer for the STP instance in seconds
Platforms
All
forward-entries
forward-entries
Syntax
forward-entries
Context
[Tree] (config>subscr-mgmt>http-rdr-plcy forward-entries)
Full Context
configure subscriber-mgmt http-redirect-policy forward-entries
Description
Enters the context to configure entries that need to be forwarded.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
forward-ip-over-gre
forward-ip-over-gre
Syntax
[no] forward-ip-over-gre
Context
[Tree] (config>system>ip forward-ip-over-gre)
Full Context
configure system ip forward-ip-over-gre
Description
This command enables forwarding of IP traffic encapsulated in a GRE over IPv4 transport sent to the system IP address.
The no form of this command disables this option and returns the system to the default behavior.
Default
no forward-ip-over-gre
Platforms
All
forward-ipv4-multicast-to-ip-int
forward-ipv4-multicast-to-ip-int
Syntax
[no] forward-ipv4-multicast-to-ip-int
Context
[Tree] (config>service>vpls>allow-ip-int-bind forward-ipv4-multicast-to-ip-int)
Full Context
configure service vpls allow-ip-int-bind forward-ipv4-multicast-to-ip-int
Description
This command enables support for forwarding IPv4 multicast traffic from sources connected to the VPLS service of a routed VPLS to the IP interface of the routed VPLS service. It can only be enabled after the routed VPLS service has been bound to an IP interface.
Default
no forward-ipv4-multicast-to-ip-int
Platforms
All
forward-ipv4-packets
forward-ipv4-packets
Syntax
[no] forward-ipv4-packets
Context
[Tree] (config>service>vprn>if>ipv6 forward-ipv4-packets)
Full Context
configure service vprn interface ipv6 forward-ipv4-packets
Description
This command allows an IPv6-only interface (with no configured IPv4 addresses) to be used for forwarding transit and locally originating and terminating IPv4 packets.
The interface will report that its IPv4 oper-state is up if its IPv6 oper-state is up. Be aware that not all protocols will observe the interface as up from an IPv4 perspective. This command is mostly intended to support BGP routing use cases. Refer to RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop, for further information.
The no form of this command restores the default behavior and prevents the interface from forwarding IPv4 packets if it has no configured IPv4 subnets.
Platforms
All
forward-ipv4-packets
Syntax
[no] forward-ipv4-packets
Context
[Tree] (config>router>if>ipv6 forward-ipv4-packets)
Full Context
configure router interface ipv6 forward-ipv4-packets
Description
This command allows an IPv6-only interface (with no configured IPv4 addresses) to be used for forwarding transit and locally originating and terminating IPv4 packets.
The interface reports that its IPv4 operational state is up if its IPv6 operational state is up. Be aware that not all protocols observe the interface as up from an IPv4 perspective. This command is mostly intended to support BGP routing use cases. Refer to RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop, for further information.
The no form of this command restores the default behavior and prevents the interface from forwarding IPv4 packets if it has no configured IPv4 subnets.
Default
no forward-ipv4-packets
Platforms
All
forward-ipv6-multicast-to-ip-int
forward-ipv6-multicast-to-ip-int
Syntax
[no] forward-ipv6-multicast-to-ip-int
Context
[Tree] (config>service>vpls>allow-ip-int-bind forward-ipv6-multicast-to-ip-int)
Full Context
configure service vpls allow-ip-int-bind forward-ipv6-multicast-to-ip-int
Description
This command enables support for forwarding IPv6 multicast traffic from sources connected to the VPLS service of a routed VPLS to the IP interface of the routed VPLS service. It can only be enabled after the routed VPLS service has been bound to an IP interface.
Default
no forward-ipv6-multicast-to-ip-int
Platforms
All
forward-path
forward-path
Syntax
[no] forward-path
Context
[Tree] (config>router>mpls>mpls-tp>transit-path forward-path)
Full Context
configure router mpls mpls-tp transit-path forward-path
Description
This command enables the forward path of an MPLS-TP transit path to be created or edited.
The forward path must be created before the reverse path.
The no form of this command removes the forward path. The forward path cannot be removed if a reverse exists.
Default
no forward-path
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
forward-when
forward-when
Syntax
forward-when pattern expression expression mask mask offset-type offset-type offset-value offset-value
Context
[Tree] (config>filter>ipv6-filter>entry>action forward-when)
[Tree] (config>filter>ip-filter>entry>action forward-when)
Full Context
configure filter ipv6-filter entry action forward-when
configure filter ip-filter entry action forward-when
Description
This command configures the forward-when action for the traffic that matches this filter entry.
Parameters
- pattern
-
Specifies the traffic that can be forwarded based on a pattern found in the packet header or data payload.
- expression
-
Specifies the hexadecimal pattern to match, up to eight bytes.
- mask
-
Specifies the mask for the pattern expression, up to eight bytes.
- offset-type
-
Specifies the starting point reference for the offset-value of this pattern.
- offset-value
-
Specifies the offset value for the pattern expression.
Platforms
All
forwarding
forwarding
Syntax
forwarding limit
no forwarding
Context
[Tree] (config>service>nat>nat-policy>port-limits forwarding)
[Tree] (config>service>nat>firewall-policy>port-limits forwarding)
Full Context
configure service nat nat-policy port-limits forwarding
configure service nat firewall-policy port-limits forwarding
Description
This command configures the maximum number of port forwarding entries.
Default
no forwarding
Parameters
- limit
-
Specifies the maximum number of port forwarding entries per subscriber.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy port-limits forwarding
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy port-limits forwarding
forwarding
Syntax
forwarding {next-hop ip-address | interface interface-name | bypass-routing}
no forwarding
Context
[Tree] (config>oam-pm>session>ip forwarding)
Full Context
configure oam-pm session ip forwarding
Description
This command influences the forwarding decision of the TWAMP Light packet. When this command is used, only one of the forwarding options can be enabled at any time.
The no form of this command removes the options and enables the default forwarding logic.
Parameters
- ip-address
-
Specifies the IP address of the next hop on the path.
- interface-name
-
Specifies the name, up to 32 characters, to refer to the interface from which the packet is sent. The name must already exist in the config>router>interface context or within the appropriate config>service context.
- bypass-routing
-
Specifies to send the packet to a host on a directly attached network, bypassing the routing table.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
forwarding-bits-set
forwarding-bits-set
Syntax
forwarding-bits-set {all | non-fwd}
no forwarding-bits-set
Context
[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived forwarding-bits-set)
[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived forwarding-bits-set)
[Tree] (config>service>vprn>bgp>graceful-restart>long-lived forwarding-bits-set)
Full Context
configure service vprn bgp group neighbor graceful-restart long-lived forwarding-bits-set
configure service vprn bgp group graceful-restart long-lived forwarding-bits-set
configure service vprn bgp graceful-restart long-lived forwarding-bits-set
Description
This command determines the setting of the F bits in the GR and LLGR capabilities advertised by the router. When the F bit is set for an AFI/SAFI, it indicates that the advertising router was able to preserve forwarding state for the routes of that AFI/SAFI across the last restart. If a router restarts and does not set F=1, then when the session with a peer is re-established, the peer immediately deletes all LLGR stale routes it was preserving on behalf of the restarting router for the corresponding AFI/SAFI.
This command allows the F bits for all advertised AFI/SAFI to be set to 1, or only the F bits for non-forwarding AFI/SAFI to be set to 1. Non-forwarding AFI/SAFI are the following configuration-related address families: L2-VPN, route-target, flow-IPv4, and flow-IPv6.
Default
no forwarding-bits-set
Parameters
- all
-
Specifies that the F bit for all AFI/SAFI should be set to 1.
- non-fwd
-
Specifies that the F bit for only non-forwarding AFI/SAFI should be set to 1. These AFI/SAFI correspond to the following families: L2-VPN, route-target, flow-IPv4, and flow-IPv6.
Platforms
All
forwarding-bits-set
Syntax
forwarding-bits-set {all | non-fwd}
no forwarding-bits-set
Context
[Tree] (config>router>bgp>graceful-restart>long-lived forwarding-bits-set)
[Tree] (config>router>bgp>group>graceful-restart>long-lived forwarding-bits-set)
[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived forwarding-bits-set)
Full Context
configure router bgp graceful-restart long-lived forwarding-bits-set
configure router bgp group graceful-restart long-lived forwarding-bits-set
configure router bgp group neighbor graceful-restart long-lived forwarding-bits-set
Description
This command determines the setting of the F bits in the GR and LLGR capabilities advertised by the router. When the F bit is set for an AFI/SAFI, it indicates that the advertising router was able to preserve forwarding state for the routes of that AFI/SAFI across the last restart. If a router restarts and does not set F=1, then when the session with a peer re-establishes the peer immediately deletes all LLGR stale routes it was preserving on behalf of the restarting router for the corresponding AFI/SAFI.
This command allows the F bits for all advertised AFI/SAFI to be set to 1, or only the F bits for non-forwarding AFI/SAFI to be set to 1. Non-forwarding AFI/SAFI are the following configuration-related address families: L2-VPN, route-target, flow-IPv4, and flow-IPv6.
Default
no forwarding-bits-set
Parameters
- all
-
Specifies that the F bit for all AFI/SAFI should be set to 1.
- non-fwd
-
Specifies that the F bit for only non-forwarding AFI/SAFI should be set to 1. These AFI/SAFI correspond to the following families: L2-VPN, route-target, flow-IPv4, and flow-IPv6.
Platforms
All
forwarding-class
forwarding-class
Syntax
forwarding-class {be | l2 | af | l1 | h2 | ef | h1 | nc}
no forwarding-class [{be | l2 | af | l1 | h2 | ef | h1 | nc}]
Context
[Tree] (config>service>vprn>static-route-entry>indirect forwarding-class)
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel forwarding-class)
[Tree] (config>service>vprn>static-route-entry>next-hop forwarding-class)
Full Context
configure service vprn static-route-entry indirect forwarding-class
configure service vprn static-route-entry ipsec-tunnel forwarding-class
configure service vprn static-route-entry next-hop forwarding-class
Description
This command specifies the enqueuing forwarding class that should be associated with traffic matching the associate static route. If this parameter is not specified, the packet will use the forwarding-class association based on default classification or other QoS Policy associations.
Default
no forwarding-class
Parameters
- Forwarding class
-
The forwarding class must be one of the pre-defined system forwarding classes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
forwarding-class
Syntax
forwarding-class {be | l2 | af | l1 | h2 | ef | h1 | nc}
no forwarding-class [{be | l2 | af | l1 | h2 | ef | h1 | nc}]
Context
[Tree] (config>router>static-route-entry>indirect forwarding-class)
[Tree] (config>router>static-route-entry>next-hop forwarding-class)
Full Context
configure router static-route-entry indirect forwarding-class
configure router static-route-entry next-hop forwarding-class
Description
This command specifies the enqueuing forwarding class that should be associated with traffic matching the associate static route. If this parameter is not specified, the packet will use the forwarding-class association based on default classification or other QoS Policy associations.
Default
no forwarding-class
Parameters
- be | l2 | af | l1 | h2 | ef | h1 | nc
-
Specifies the forwarding class.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
forwarding-class
Syntax
[no] forwarding-class
Context
[Tree] (config>log>acct-policy>cr>aa>aa-to-sub-cntr forwarding-class)
[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr forwarding-class)
Full Context
configure log accounting-policy custom-record aa-specific to-aa-sub-counters forwarding-class
configure log accounting-policy custom-record aa-specific from-aa-sub-counters forwarding-class
Description
This command enables the collection of a Forwarding Class bitmap information added to the XML aa-sub and router level accounting records, and only applies to the 7750 SR.
Default
no forwarding-class
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
forwarding-policies
forwarding-policies
Syntax
[no] forwarding-policies
Context
[Tree] (config>router>mpls forwarding-policies)
Full Context
configure router mpls forwarding-policies
Description
Commands in this context configure an MPLS forwarding policy.
The no form of this command deletes all policies from the forwarding policy database.
Platforms
All
forwarding-policy
forwarding-policy
Syntax
[no] forwarding-policy name
Context
[Tree] (config>router>mpls>fwd-policies forwarding-policy)
Full Context
configure router mpls forwarding-policies forwarding-policy
Description
This command creates an MPLS forwarding policy.
There are two types of MPLS forwarding policy:
-
endpoint policy
-
label-binding policy
The endpoint policy allows the user to forward unlabeled packets over a set of user-defined direct (with option to push a label stack) or indirect next hops. Routes are bound to an endpoint policy when their next hop matches the endpoint address of the policy.
The label-binding policy provides the same capability for labeled packets. In this case, labeled packets matching the ILM of the policy binding label are forwarded over the set of next hops of the policy.
The data model of a forwarding policy represents each pair of {primary next hop, backup next hop} as a group and models the ECMP set as the set of Next-Hop Groups (NHGs). Flows of prefixes can be switched on a per-NHG basis from the primary next hop, when it fails, to the backup next hop without disturbing the flows forwarded over the other NHGs of the policy. The same can be performed when reverting back from a backup next hop to the restored primary next hop of the same NHG.
The MPLS forwarding policy supports two types of NHGs on a per policy basis:
-
An NHG of resolution type indirect supported with the label-binding policy and in which forwarding over the primary/backup next hop is modeled as a swap operation from the binding label to an implicit-null label over multiple outgoing interfaces (multiple NHLFEs) corresponding to the resolved next hops of the indirect route.
Within a given NHG, the primary next hop is the preferred active path in the absence of any failure of the NHG of resolution type indirect.
The forwarding database tracks the primary or backup next hop in the routing table. A route delete of the primary indirect next hop causes CPM to program the backup indirect next hop in the data path.
A route modify to the indirect primary or backup next hop causes CPM to update the its resolved next hops and to update the data path if it is the active indirect next hop.
When the primary indirect next hop is restored and is added back into the routing table, CPM waits for an amount of time equal to the user-programmed revert timer before updating the data path. However, if the backup indirect next hop fails while the timer is running, CPM updates the data path immediately.
-
An NHG of resolution type direct is modeled as follows:
-
For a label-binding policy, forwarding over the primary or backup next hop is modeled as a swap operation from the binding label to the configured label stack or to an implicit-null label (if the pushed-labels command not configured) over a single outgoing interface to the next hop.
-
For an endpoint policy, forwarding over the primary or backup next hop is modeled as a push operation from the binding label to the configured label stack or to an implicit-null label (if the pushed-labels command not configured) over a single outgoing interface to the next hop.
-
The labels configured by the pushed-labels command are not validated.
Within a given NHG, the primary next hop is the preferred active path in the absence of any failure of the NHG of resolution type direct.
The NHG supports uniform failover. The forwarding policy database assigns a Protect-Group ID (PG-ID) to each of the primary next hop and the backup next hop and programs both of them in data path. A failure of the active path switches traffic to the other path following the uniform failover procedures.
The forwarding database tracks the primary or backup next hop in the routing table. A route delete of the primary/backup direct next hop causes CPM to send the corresponding PG-ID switch to the data path.
A route modify to the direct primary or backup next hop causes CPM to update the MPLS forwarding database and to update the data path since both next hops are programmed.
When the primary direct next hop is restored and is added back into the routing table, CPM waits for an amount of time equal to the user programmed revert timer before activating it and updating the data path. However, if the backup direct next hop fails while the timer is running, CPM activates it and updates the data path immediately. The latter failover to the restored primary next hop is performed using the uniform failover procedure.
-
The forwarding policy database activates the best endpoint policy among the named policies sharing the same value of the endpoint parameter by selecting the lowest preference value policy. This policy is then programmed into the TTM and into the tunnel table in data path. If this policy goes down, then the forwarding policy database performs a re-evaluation and activates the named policy with the next lowest preference value for the same endpoint value. If a more preferred policy comes back up, the forwarding policy database reverts to it and activates it.
The forwarding policy database similarly activates the best label-binding policy among the named policies sharing the same binding label by selecting the lowest preference value policy. This policy is then programmed into the label FIB table in data path. If this policy goes down, then the forwarding policy database performs a re-evaluation and activates the names policy with the next lowest preference value for the same binding label value. If a more preferred policy comes back up, the forwarding policy database reverts to it and activates it.
Ingress statistics can be enabled as is associated with binding label, that is the ILM of the forwarding policy, and provides aggregate packet and byte counters for packets matching the binding label.
The no form of the command deletes the named MPLS forwarding policy.
Parameters
- name
-
Specifies the name of the MPLS forwarding policy, up to 64 characters.
Platforms
All
forwarding-set
forwarding-set
Syntax
forwarding-set policy policy-name set set-id
no forwarding-set
Context
[Tree] (config>router>mpls>lsp-template>class-forwarding forwarding-set)
[Tree] (config>router>mpls>lsp>class-forwarding forwarding-set)
Full Context
configure router mpls lsp-template class-forwarding forwarding-set
configure router mpls lsp class-forwarding forwarding-set
Description
This command configures the mapping of a class-forwarding policy and forwarding set ID to an LSP (RSVP-TE or SR-TE) or an LSP template.
An MPLS LSP can only map to one single class forwarding policy and forwarding set. Multiple LSPs can map to the same policy and set. If the LSPs form part of an ECMP set of next-hops for an IPv4 or IPv6 prefix resolved to IGP shortcuts, the prefix packets with a matching FC are mapped to this set and are sprayed over these LSPs. This behavior is based on a modulo operation of the output of the hash routine on the packet’s headers and the number of LSPs in the set.
Parameters
- policy-name
-
Specifies the name of the class forwarding policy, to a maximum of 32 characters.
- set-id
-
Specifies the class forwarding set.
Platforms
All
forwarding-tree-topology
forwarding-tree-topology
Syntax
forwarding-tree-topology unicast [st | spf]
Context
[Tree] (config>service>vpls>spb>level forwarding-tree-topology)
Full Context
configure service vpls spb level forwarding-tree-topology
Description
This command sets the unicast forwarding to follow the shortest path tree defined by the ECT algorithm shortest path forwarding (spf) or to follow a single tree. (st). Shortest path trees make use of more link resources.
Multicast traffic is defaulted to follow the single tree topology. A single tree unicast would make Multicast and unicast follow the same path.
Default
forwarding-tree-topology unicast spf
Parameters
- spf
-
Follows the shortest path tree.
- st
-
Follows a single tree.
Platforms
All
fp
fp
Syntax
fp [fp-number]
Context
[Tree] (config>card fp)
Full Context
configure card fp
Description
This command enables access to the configuration of the forwarding planes on a card.
The default forwarding plane is 1. When entering the FP node, if the forwarding plane number is omitted, the system will assume forwarding plane number 1.
Commands can only be configured under card>fp if the hardware that the FP resides on (either a card or an XMA) is provisioned. Conversely, all commands under card>fp of the corresponding FPs are automatically removed when that hardware is unprovisioned.
Parameters
- fp-number
-
Specifies that the FP number parameter is optional following the fp command.
Platforms
All
fp-redirect-group
fp-redirect-group
Syntax
fp-redirect-group policer-type policer-id
no fp-redirect-group policer-type
Context
[Tree] (config>qos>network>ingress>fc fp-redirect-group)
Full Context
configure qos network ingress fc fp-redirect-group
Description
This command is used to redirect the FC of a broadcast packet received in a VPLS service over a PW or network IP interface to an ingress forwarding plane queue-group.
It defines the mapping of an FC to a policer-id and redirects the lookup of the policer of the same ID in some ingress forwarding plane queue-group instance. However, the queue-group name and instance are explicitly provided only at the time the network QoS policy is applied to the ingress context of a spoke or mesh SDP or a network IP interface.
The broadcast-policer statement is ignored when the network QoS policy is applied to any object other than a VPLS spoke or mesh SDP or a network IP interface.
The no form of this command removes the redirection of the FC.
Parameters
- policer-type
-
The policer type to be used. The policer-type is ignored when the network QoS policy is applied to any object other than a VPLS spoke or mesh SDP or a network IP interface.
- policer-id
-
The specified policer-id must exist within the queue-group template applied to the ingress context of the forwarding plane.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
fp-resource-policy
fp-resource-policy
Syntax
fp-resource-policy name
no fp-resource-policy
Context
[Tree] (config>card>fp fp-resource-policy)
Full Context
configure card fp fp-resource-policy
Description
This command configures the FP resource policy for the specified FP.
If the allocation configured within the FP resources policy is not achievable with the current ingress or egress queue consumption, the command fails. The configuration within the newly applied FP resource policy takes effect on the FP on which the FP resources policy is applied, and that includes removing an applied user created FP resource policy to return to the default policy, and causes the router to immediately reset the associated cards, XIOMs, and MDAs, except on the 7750 SR-1 where the configuration must be saved, and the router rebooted, immediately after committing the configuration transaction.
The no form of this command reverts to the default value by applying the default fp-resource-policy to the FP.
Default
no fp-resource-policy
Parameters
- name
-
Specifies the FP resource policy name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
fp-resource-policy
Syntax
fp-resource-policy policy-name [create]
no fp-resource-policy policy-name
Context
[Tree] (config>qos fp-resource-policy)
Full Context
configure qos fp-resource-policy
Description
This command configures an FP resource policy that is used to manage resources on an FP4 forwarding plane.
A default policy is created by the system and applied to all FP4 FPs by default. If an FP resource policy is removed from an FP, the system automatically applies the default policy to that FP. The system prevents the modification or deletion of the default policy, and the deletion of any user created policy that is applied to an FP. The system supports a maximum of 15 FP resource policies.
The no form of this command deletes the FP resources policy from the system.
Parameters
- policy-name
-
Specifies the FP resource policy, up to 64 characters.
- create
-
Creates the FP resource policy entry.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
fpe
fpe
Syntax
fpe fpe-id
no fpe
Context
[Tree] (config>service>vprn>sub-if>grp-if>bonding-parameters fpe)
[Tree] (config>service>ies>sub-if>grp-if>bonding-parameters fpe)
Full Context
configure service vprn subscriber-interface group-interface bonding-parameters fpe
configure service ies subscriber-interface group-interface bonding-parameters fpe
Description
This command specifies which FPE is used to provision bonding functionality. The FPE cannot be changed when there are active bonded subscribers.
The no form of this command disables the FPE for bonding functionality under this group interface.
fpe
Syntax
fpe fpe-id
no fpe
Context
[Tree] (config>service>ies>sub-if>grp-if>gtp-parameters fpe)
[Tree] (config>service>vprn>sub-if>grp-if>gtp-parameters fpe)
Full Context
configure service ies subscriber-interface group-interface gtp-parameters fpe
configure service vprn subscriber-interface group-interface gtp-parameters fpe
Description
This command configures the FPE to be used by a group interface for extended ESM functionality such as GTP termination or bonding.
The FPE must be configured in mode sub-mgmt-extension and must be provisioned before the extended functionality becomes active.
The no form of this command disables the FPE for GTP functionality under this group interface.
fpe
Syntax
fpe fpe-id [create]
no fpe fpe-id
Context
[Tree] (config>fwd-path-ext fpe)
Full Context
configure fwd-path-ext fpe
Description
This command configures an FPE object which associates the application with a PXC (paired set of PXC sub-ports or a paired set of PXC based LAGs).
The no form of this command disables the FPE object association.
Parameters
- fpe-id
-
Specifies the FPE ID.
- create
-
Keyword used to associate the queue group. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
All
fqdn
fqdn
Syntax
fqdn fully-qualified-domain-name
no fqdn
Context
[Tree] (config>app-assure>group>url-filter>web-service fqdn)
Full Context
configure application-assurance group url-filter web-service fqdn
Description
This command configures the host name of the web-service.
The no form of this command removes the host name configuration.
Default
no fqdn
Parameters
- fully-qualified-domain-name
-
Specifies the host name of the web service, up to 255 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
frag-required
frag-required
Syntax
[no] frag-required
Context
[Tree] (config>ipsec>tnl-temp>icmp-generation frag-required)
[Tree] (config>service>vprn>if>sap>ip-tunnel>icmp-generation frag-required)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>icmp-generation frag-required)
[Tree] (config>router>if>ipsec>ipsec-tunnel>icmp-generation frag-required)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>icmp-generation frag-required)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel>icmp-generation frag-required)
[Tree] (config>service>ies>if>sap>ip-tunnel>icmp-generation frag-required)
Full Context
configure ipsec tunnel-template icmp-generation frag-required
configure service vprn interface sap ip-tunnel icmp-generation frag-required
configure service vprn interface ipsec ipsec-tunnel icmp-generation frag-required
configure router interface ipsec ipsec-tunnel icmp-generation frag-required
configure service ies interface ipsec ipsec-tunnel icmp-generation frag-required
configure service vprn interface sap ipsec-tunnel icmp-generation frag-required
configure service ies interface sap ip-tunnel icmp-generation frag-required
Description
Commands in this context configure ICMP Fragmentation Required parameters.
The no form of this command disables sending the ICMP messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel icmp-generation frag-required
- configure ipsec tunnel-template icmp-generation frag-required
- configure service ies interface sap ip-tunnel icmp-generation frag-required
- configure service vprn interface sap ip-tunnel icmp-generation frag-required
VSR
- configure service vprn interface ipsec ipsec-tunnel icmp-generation frag-required
- configure service ies interface ipsec ipsec-tunnel icmp-generation frag-required
- configure router interface ipsec ipsec-tunnel icmp-generation frag-required
fragment
fragment
Syntax
fragment {true | false}
Context
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match fragment)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry>match fragment)
Full Context
configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match fragment
configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match fragment
Description
This command configures the fragmentation match condition.
The no form of this command reverts to the default.
Parameters
- true
-
Enables fragmentation matching.
- false
-
Disables fragmentation matching.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fragment
Syntax
fragment {true | false}
no fragment
Context
[Tree] (config>li>li-filter>li-ip-filter>entry>match fragment)
Full Context
configure li li-filter li-ip-filter entry match fragment
Description
This command specifies match criterion for fragmented packets.
The no form of this command removes the match criterion.
Default
no fragment
Parameters
- true
-
Specifies to match on all fragmented IP packets.
- false
-
Specifies to match on all non-fragmented IP packets.
Platforms
All
fragment
Syntax
fragment {true | false}
no fragment
Context
[Tree] (config>qos>sap-egress>ip-criteria>entry>match fragment)
[Tree] (config>qos>sap-ingress>ip-criteria>entry>match fragment)
Full Context
configure qos sap-egress ip-criteria entry match fragment
configure qos sap-ingress ip-criteria entry match fragment
Description
This command configures fragmented or non-fragmented IP packets as a SAP QoS policy match criterion.
The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.
Default
no fragment
Parameters
- true
-
Configures a match on all fragmented IP packets. A match will occur for all packets that have either the MF (more fragment) bit set or have the Fragment Offset field of the IP header set to a non-zero value.
- false
-
Configures a match on all non-fragmented IP packets. Non-fragmented IP packets are packets that have the MF bit set to zero and have the Fragment Offset field also set to zero.
Platforms
All
fragment
Syntax
fragment {true | false | first-only | non-first-only}
no fragment
Context
[Tree] (config>qos>sap-ingress>ipv6-criteria>entry>match fragment)
Full Context
configure qos sap-ingress ipv6-criteria entry match fragment
Description
This command configures fragmented or non-fragmented IPv6 packets as a SAP ingress QoS policy match criterion.
The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.
Default
no fragment
Parameters
- true
-
Specifies to match on all fragmented IPv6 packets. A match will occur for all packets that contain an IPv6 Fragmentation Extension Header.
- false
-
Specifies to match on all non-fragmented IP packets. Non-fragmented IPv6 packets are packets that do not contain an IPv6 Fragmentation Extension Header.
- first-only
-
Matches if a packet is an initial fragment of the fragmented IPv6 packet.
- non-first-only
-
Matches if a packet is a non-initial fragment of the fragmented IPv6 packet.
Platforms
All
fragment
Syntax
fragment {true | false}
no fragment
Context
[Tree] (config>qos>network>ingress>ip-criteria>entry>match fragment)
[Tree] (config>qos>network>egress>ip-criteria>entry>match fragment)
Full Context
configure qos network ingress ip-criteria entry match fragment
configure qos network egress ip-criteria entry match fragment
Description
This command configures fragmented or non-fragmented IP packets as a network QoS policy match criterion.
The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.
Parameters
- true
-
Configures a match on all fragmented IP packets. A match will occur for all packets that have either the MF (more fragment) bit set or have the Fragment Offset field of the IP header set to a non-zero value.
- false
-
Configures a match on all non-fragmented IP packets. Non-fragmented IP packets are packets that have the MF bit set to zero and have the Fragment Offset field also set to zero.
Platforms
All
fragment
Syntax
fragment {true | false | first-only | non-first-only}
no fragment
Context
[Tree] (config>qos>network>ingress>ipv6-criteria>entry>match fragment)
[Tree] (config>qos>network>egress>ipv6-criteria>entry>match fragment)
Full Context
configure qos network ingress ipv6-criteria entry match fragment
configure qos network egress ipv6-criteria entry match fragment
Description
This command configures fragmented or non-fragmented IPv6 packets as a network QoS policy match criterion.
The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.
Parameters
- true
-
Specifies to match on all fragmented IPv6 packets. A match will occur for all packets that contain an IPv6 Fragmentation Extension Header.
- false
-
Specifies to match on all non-fragmented IP packets. Non-fragmented IPv6 packets are packets that do not contain an IPv6 Fragmentation Extension Header.
- first-only
-
Matches if a packet is an initial fragment of the fragmented IPv6 packet.
- non-first-only
-
Matches if a packet is a non-initial fragment of the fragmented IPv6 packet.
Platforms
All
fragment
Syntax
fragment {true | false | first-only | non-first-only}
no fragment
Context
[Tree] (config>filter>ip-filter>entry>match fragment)
[Tree] (config>filter>ipv6-filter>entry>match fragment)
Full Context
configure filter ip-filter entry match fragment
configure filter ipv6-filter entry match fragment
Description
This command specifies match criterion for fragmented packets.
Matches can be based on the presence of a fragmented packet (or otherwise) on the ingress or egress interface.
Matches can also be based on the presence of the first fragment of a packet, or on the presence of a fragment that is not the first fragment on the ingress interface.
The no form of the command removes the match criterion.
Default
no fragment
Parameters
- true
-
Specifies to match on all fragmented packets.
- false
-
Specifies to match on all non-fragmented packets.
- first-only
-
Matches if a packet is an initial fragment of a fragmented packet.
- non-first-only
-
Matches if a packet is a non-initial fragment of a fragmented packet.
Platforms
All
fragment
Syntax
fragment {true | false}
no fragment
Context
[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match fragment)
[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match fragment)
Full Context
configure system security cpm-filter ip-filter entry match fragment
configure system security cpm-filter ipv6-filter entry match fragment
Description
This command specifies fragmented or non-fragmented IP packets as an IP filter match criterion.
An entry containing Layer 4 match criteria will not match non-initial (2nd, 3rd, etc) fragments of a fragmented packet since only the first fragment contains the Layer 4 information.
This command enables match on existence of IPv6 Fragmentation Extension Header in the IPv6 filter policy. To match first fragment of an IP fragmented packet, specify additional Layer 4 matching criteria in a filter policy entry. The no version of this command ignores IPv6 Fragmentation Extension Header presence/absence in a packet when evaluating match criteria of a given filter policy entry.
The no form of this command removes the match criterion.
This command enables match on existence of IPv6 Fragmentation Extension Header in the IPv6 filter policy. To match first fragment of an IP fragmented packet, specify additional Layer 4 matching criteria in a filter policy entry. The no version of this command ignores IPv6 Fragmentation Extension Header presence/absence in a packet when evaluating match criteria of a given filter policy entry.
Default
no fragment
Parameters
- true
-
Specifies to match on all fragmented IP packets. A match will occur for all packets that have either the MF (more fragment) bit set or have the Fragment Offset field of the IP header set to a non-zero value. For IPv6, packet matches if it contains IPv6 Fragmentation Extension Header.
- false
-
Specifies to match on all non-fragmented IP packets. Non-fragmented IP packets are packets that have the MF bit set to zero and have the Fragment Offset field also set to zero. For IPv6, packet matches if it does not contain IPv6 Fragmentation Extension Header.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
fragment-drop
fragment-drop
Syntax
fragment-drop {all | out-of-order} [ event-log event-log-name]
no fragment-drop
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action fragment-drop)
Full Context
configure application-assurance group policy app-qos-policy entry action fragment-drop
Description
This command specifies the action to apply to fragments.
Default
no fragment-drop
Parameters
- all
-
All the fragments will be dropped.
- out-of-order
-
All out of order fragments will be dropped.
- event-log-name
-
Specifies if the dropping of fragments should be logged to the specified event log name.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
fragment-drop-all
fragment-drop-all
Syntax
fragment-drop-all direction [create]
no fragment-drop-all direction
Context
[Tree] (config>app-assure>group>statistics>tca fragment-drop-all)
Full Context
configure application-assurance group statistics threshold-crossing-alert fragment-drop-all
Description
This command configures a TCA for the counter capturing drops due to the fragment-drop- all AQP command. A fragment-drop-all 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 fragment-drop-all TCA.
Parameters
- direction
-
Specifies the traffic direction.
- create
-
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
fragment-drop-out-of-order
fragment-drop-out-of-order
Syntax
fragment-drop-out-of-order direction [create]
no fragment-drop-out-of-order direction
Context
[Tree] (config>app-assure>group>statistics>tca fragment-drop-out-of-order)
Full Context
configure application-assurance group statistics threshold-crossing-alert fragment-drop-out-of-order
Description
This command configures a TCA for the counter capturing drops due to the fragment-drop- out-of-order AQP command. A fragment-drop-out-of-order 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 fragment-drop-out-of-order TCA.
Parameters
- direction
-
Specifies the traffic direction.
- create
-
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
frame-based-accounting
frame-based-accounting
Syntax
[no] frame-based-accounting
Context
[Tree] (config>qos>scheduler-policy frame-based-accounting)
Full Context
configure qos scheduler-policy frame-based-accounting
Description
The frame-based-accounting command is used to enable frame-based accounting for both the children queues parented to the scheduling policy and for the schedulers within the scheduler policy.
When frame-based accounting is enabled on the policy, all queues associated with the scheduler (through the parent command on each queue) will have their rate and CIR values interpreted as frame-based values. When shaping, the queues will include the 12-byte Inter-Frame Gap (IFG) and 8 byte preamble for each packet scheduled out the queue. The profiling CIR threshold will also include the 20-byte frame encapsulation overhead. Statistics associated with the queue do not include the frame encapsulation overhead.
The scheduler policy’s scheduler rate and CIR values will be interpreted as frame-based values.
The configuration of parent-location and frame-based-accounting in a scheduler policy is mutually exclusive to ensure consistency between the different scheduling levels. Packet byte offset settings are not included in the applied rate when frame-based accounting is configured; however, the offsets are applied to the statistics.
The no form of this command is used to return all schedulers within the policy and queues associated with the policy to the default packet-based accounting mode. If frame-based-accounting is not currently enabled for the scheduling policy, the no frame-based-accounting command has no effect.
Platforms
All
frame-counters
frame-counters
Syntax
[no] frame-counters
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes frame-counters)
Full Context
configure aaa isa-radius-policy acct-include-attributes frame-counters
Description
This command includes the frame-counters attribute.
The no form of the command excludes frame-counters attribute.
Default
no frame-counters
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
frame-mix
frame-mix
Syntax
frame-mix
Context
[Tree] (config>test-oam>sath>svc-test>svc-stream frame-mix)
Full Context
configure test-oam service-activation-testhead service-test service-stream frame-mix
Description
Commands in this context configure frame mixing for the specified service stream by referencing the frame-size-template.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
frame-payload
frame-payload
Syntax
frame-payload
Context
[Tree] (config>test-oam>service-activation-testhead>service-test>service-stream frame-payload)
Full Context
configure test-oam service-activation-testhead service-test service-stream frame-payload
Description
Commands in this context configure packet header information used in frames generated by the testhead function.
Only the specified header information is included in the frame. At a minimum, the user must configure the Ethernet destination MAC address and ETH-CFM information to include in the frame payload configuration.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
frame-size-template
frame-size-template
Syntax
frame-size-template frame-size-tmpl-name [create]
no frame-size-template frame-size-tmpl-name
Context
[Tree] (config>test-oam>sath frame-size-template)
Full Context
configure test-oam service-activation-testhead frame-size-template
Description
This command creates a template to configure frames of different sizes for use with a test stream configured under the config>test-oam>service-activation- testhead>service-test context. The ITU-T Y.1564 methodology designates the letters "a” to "h” for a default frame size. The default frame size can be overwritten.
The no form of this command deletes the configured frame size template.
Default
frame-size-template default
Parameters
- frame-size-tmpl-name
-
Specifies the template name, up to 64 characters, for a test flow with a specific frame mix.
- create
-
Mandatory keyword to create the frame size template.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
frame-size-template
Syntax
frame-size-template frame-size-tmpl-name
Context
[Tree] (config>test-oam>sath>svc-test>svc-stream>frm-mix frame-size-template)
Full Context
configure test-oam service-activation-testhead service-test service-stream frame-mix frame-size-template
Description
This command configures the frame size template for the specified service stream.
The user can assign the default frame-size-tmpl-name "default” to remove the existing template in a service stream.
Default
frame-size-template default
Parameters
- frame-size-tmpl-name
-
Specifies the name, up to 64 characters, for the frame size template.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
framed-interface-id
framed-interface-id
Syntax
[no] framed-interface-id
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-interface-id)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-interface-id
Description
This command enables the generation of the framed-interface-id RADIUS attribute.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framed-ip-addr
framed-ip-addr
Syntax
[no] framed-ip-addr
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-ip-addr)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-ip-addr
Description
This command enables the inclusion of the framed-ip-addr attribute.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framed-ip-addr
Syntax
[no] framed-ip-addr
Context
[Tree] (config>ipsec>rad-acct-plcy>include framed-ip-addr)
Full Context
configure ipsec radius-accounting-policy include-radius-attribute framed-ip-addr
Description
This command enables the inclusion of the framed-ip-addr attribute.
Default
no framed-ip-addr
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
framed-ip-addr
Syntax
[no] framed-ip-addr
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes framed-ip-addr)
[Tree] (config>aaa>isa-radius-plcy>auth-include-attributes framed-ip-addr)
Full Context
configure aaa isa-radius-policy acct-include-attributes framed-ip-addr
configure aaa isa-radius-policy auth-include-attributes framed-ip-addr
Description
This command enables the inclusion of the framed-ip-addr attribute.
The no form of the command excludes called framed-ip-addr attributes.
Default
no framed-ip-addr
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
framed-ip-netmask
framed-ip-netmask
Syntax
[no] framed-ip-netmask
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-ip-netmask)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-ip-netmask
Description
This command enables the inclusion of the framed-ip-netmask attribute.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framed-ip-netmask
Syntax
[no] framed-ip-netmask
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes framed-ip-netmask)
Full Context
configure aaa isa-radius-policy acct-include-attributes framed-ip-netmask
Description
This command enables the inclusion of the framed-ip-netmask attribute.
The no form of the command disables the inclusion.
Default
no framed-ip-netmask
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
framed-ipv6-prefix
framed-ipv6-prefix
Syntax
[no] framed-ipv6-prefix
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-ipv6-prefix)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-ipv6-prefix
Description
This command enables the generation of the framed-ipv6-prefix RADIUS attribute.
The no form of this command disables the generation of the framed-ipv6-prefix RADIUS attribute.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framed-ipv6-prefix
Syntax
[no] framed-ipv6-prefix
Context
[Tree] (config>ipsec>rad-acct-plcy>include framed-ipv6-prefix)
Full Context
configure ipsec radius-accounting-policy include-radius-attribute framed-ipv6-prefix
Description
This command enables the inclusion of the framed-ipv6-prefix attribute.
Default
no framed-ipv6-prefix
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
framed-ipv6-prefix
Syntax
[no] framed-ipv6-prefix
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes framed-ipv6-prefix)
Full Context
configure aaa isa-radius-policy acct-include-attributes framed-ipv6-prefix
Description
If an active SLAAC lease exists, this attribute defines if the SLAAC prefix of the UE is present in accounting.
Default
no framed-ipv6-prefix
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
framed-ipv6-route
framed-ipv6-route
Syntax
[no] framed-ipv6-route
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-ipv6-route)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-ipv6-route
Description
When enabled, all valid [99] Framed-IPv6-Route attributes as received in the RADIUS authentication phase and associated with an instantiated IPv6 wan host is included in the RADIUS accounting request messages. The state of the Framed-IPv6-Route (installed, shadowed, hostInactive, and so on) is not considered for reporting in the accounting request messages.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framed-route
framed-route
Syntax
[no] framed-route
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute framed-route)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute framed-route
Description
When enabled, all valid [22] Framed-Route attributes as received in the RADIUS authentication phase and associated with an instantiated IPv4 host is included in the RADIUS accounting request messages. The state of the Framed-Route (installed, shadowed, hostInactive, and so on) is not considered for reporting in the accounting request messages.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
framing
framing
Syntax
framing {sonet | sdh}
Context
[Tree] (config>port>sonet-sdh framing)
Full Context
configure port sonet-sdh framing
Description
This command specifies SONET/SDH framing to be either SONET or SDH.
This command is supported by TDM satellite.
Default
framing sonet
Parameters
- sonet
-
Configures the port for SONET framing.
- sdh
-
Configures the port for SDH framing.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
framing
Syntax
framing {esf | sf | unframed-ds1}
Context
[Tree] (config>port>tdm>ds1 framing)
Full Context
configure port tdm ds1 framing
Description
This command specifies the DS-1 framing to be used with the associated channel.
Default
framing esf
Parameters
- esf
-
Configures the DS-1 port for extended super frame framing.
- sf
-
Configures the DS-1 port for super frame framing.
- unframed-ds1
-
Specifies ds-1 unframed (G.703) mode for DS-1 interfaces. This parameter allows the configuration of an unstructured DS-1 channel on a CES MDA. In G.704, timeslot 0 is used to carry timing information by a service provider, thus, only 31 slots are made available to the end user. In G.703, all 32 time slots are available to the end user. Timing is provided by the end user. When an e1-unframed channel is shutdown, it sends the AIS pattern to the far-end DS-1 which does not react. The operational status remains up and no alarms are generated while the near-end (shutdown) is operationally down. This is normal behavior since the G.703 option does not have framing. G.703 framing is only applicable for FR, PPP, and cHDLC encapsulations.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
framing
Syntax
framing {no-crc-g704 | g704 | e1-unframed}
Context
[Tree] (config>port>tdm>e1 framing)
Full Context
configure port tdm e1 framing
Description
This command specifies the E-1 framing to be used with the associated channel.
Default
framing g704
Parameters
- g704
-
Configures the E-1 port for G.704 framing.
- no-crc-g70
-
Configures the E-1 for G.704 with no CRC4.
- e1-unframed
-
Specifies E-1 unframed (G.703) mode for E-1 interfaces. This parameter also allows the configuration of an unstructured E-1 channel on an ASAP or CES MDA. In G.704, timeslot 0 is used to carry timing information by a service provider, thus, only 31 slots are made available to the end user. In G.703, all 32 time slots are available to the end user. Timing is provided by the end user. When an e1-unframed channel is shutdown, it sends the AIS pattern to the far-end E-1 which does not react. The operational status remains up and no alarms are generated while the near-end (shutdown) is operationally down. This is normal behavior since the G.703 option does not have framing. G.703 framing is only applicable for FR, PPP, and cHDLC and CEM encapsulations.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
framing
Syntax
framing {c-bit | m23 | unframed-ds3}
Context
[Tree] (config>port>tdm>ds3 framing)
Full Context
configure port tdm ds3 framing
Description
This command specifies DS-3 framing for the associated DS-3 port or channel.
Default
framing c-bit
Parameters
- c-bit
-
Configures the DS-3 port/channels for C-Bit framing.
- m23
-
Configures the DS-3 port/channel for M23 framing.
- unframed-ds3
-
Specifies ds-3 unframed mode for DS-3 interfaces. This parameter allows the configuration of an unstructured DS-3 channel on a CES MDA.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
framing
Syntax
framing {g751 | g832 | unframed-e3}
Context
[Tree] (config>port>tdm>e3 framing)
Full Context
configure port tdm e3 framing
Description
This command specifies E-3 framing for the associated E-3 port or channel.
Default
for E-3 non-ATM: framing g751 and cannot be changed. for E-3 ATM: framing g832 and cannot be changed.
Parameters
- g751
-
Configures the E-3 port/channel for g751 framing.
- g832
-
Configures the E-3 port/channel for g832 framing.
- unframed-e3
-
Specifies e-3 unframed mode for E-3 interfaces. This parameter allows the configuration of an unstructured E-3 channel on a CES MDA.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
frequency
frequency
Syntax
frequency frequency
no frequency
Context
[Tree] (config>port>dwdm frequency)
Full Context
configure port dwdm frequency
Description
This command configures the center frequency to use for a tunable DWDM optical interface. It replaces the configure>port>dwdm>channel command (used prior to Release 22.2.R1). The frequency command supports any frequency in the C band, but the actual operating frequency is dependent on the installed optic module.
Provisioning rules
The provisioned MDA type must have DWDM tunable optics (for example, p1-100g-tun-b) or the MDA must support the option of tunable DWDM optic modules. The following provisioning rules apply:
-
The DWDM frequency must set to a non-zero value before the port is set to no shutdown.
-
The port must be shutdown before changing the DWDM frequency.
-
The port must be a physical port to set the DWDM frequency.
Default
frequency 0
Parameters
- frequency
-
Specifies the frequency in MHz.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
from
from
Syntax
from [main] [security] [change] [debug-trace]
no from
Context
[Tree] (config>service>vprn>log>log-id from)
Full Context
configure service vprn log log-id from
Description
This command selects the source stream to be sent to a log destination.
One or more source streams must be specified. The source of the data stream must be identified using the from command before you can configure the destination using the to command. The from command can identify multiple source streams in a single statement (for example: from main change debug-trace).
Only one from command may be entered for a single log-id. If multiple from commands are configured, then the last command entered overwrites the previous from command.
The no form of this command removes all previously configured source streams.
Default
No source stream is configured.
Parameters
- main
-
Instructs all events in the main event stream to be sent to the destination defined in the to command for this destination log-id. The main event stream contains the events that are not explicitly directed to any other event stream. To limit the events forwarded to the destination, configure filters using the filter command.
- security
-
Instructs all events in the security event stream to be sent to the destination defined in the to command for this destination log-id. The security event stream contains all events that pertain to attempts to breach system security. To limit the events forwarded to the destination, configure filters using the filter command.
- change
-
Instructs all events in the user activity stream to be sent to the destination configured in the to command for this destination log-id. The change event stream contains all events that directly affect the configuration or operation of this node. To limit the events forwarded to the change stream destination, configure filters using the filter command.
- debug-trace
-
Instructs all events in the debug-trace event stream to be sent to the destination defined in the to command for this destination log-id. The debug-trace event stream contains all events that pertain to trace or other debugging information. To limit the events forwarded to the destination, configure filters using the filter command.
Platforms
All
from
Syntax
from ip-address
Context
[Tree] (config>router>mpls>lsp-template from)
[Tree] (config>router>mpls>lsp from)
Full Context
configure router mpls lsp-template from
configure router mpls lsp from
Description
This optional command specifies the IP address of the ingress router for the LSP. When this command is not specified, the system IP address is used. IP addresses that are not defined in the system are allowed. If an invalid IP address is entered, LSP bring-up fails and an error is logged.
If an interface IP address is specified as the from address, and the egress interface of the LSP nexthop IP address is a different interface, the LSP is not signaled. As the egress interface changes due to changes in the routing topology, it is recommended to set the from IP address to the system IP address or to the address of a loopback interface to ensure the LSP recovers.
Only one from address can be configured.
Default
The system IP address
Parameters
- ip-address
-
Specifies the IP address of the ingress router. This can be either the interface, the system or a loopback interface IP address. If the IP address is local, the LSP must egress through that local interface which ensures local strictness. When the LSP type is sr-te, then an IPv6 address can be used.
Platforms
All
from
Syntax
from li
no from
Context
[Tree] (config>li>log>log-id from)
Full Context
configure li log log-id from
Description
This command configures a bit mask that specifies the log event source stream(s) to be forwarded to the destination specified in the log destination (memory, session, SNMP). Events from more than one source can be forwarded to the log destination.
Parameters
- li
-
Specifies the li event stream that contains all events configured for Lawful Intercept activities.
If the requester does not have access to the li context, the event stream will fail.
Platforms
All
from
Syntax
from ipv4-address
no from
Context
[Tree] (config>oam-pm>session>mpls>lsp>rsvp-auto from)
Full Context
configure oam-pm session mpls lsp rsvp-auto from
Description
One of three mandatory configuration statements that are required to identify automatically create RSVP LSPs, created using config>router>mpls>lsp-template. The config>router>mpls>auto-lsp lsp-template links three distinct functions. The config>router>policy-options>prefix-list, config>router>policy-options>policy-statement>entry>from and config>router>mpls> lsp-template. The from address under the test context is the same as the config>router>mpls>lsp-template>from address.
The three required identifiers are from, lsp-template and to, all under this container.
The no form of this command deletes the IP address from the configuration.
Parameters
- ipv4-address
-
Specifies the IPv4 address.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
from
Syntax
from {[main] [security] [change] [debug-trace]}
no from
Context
[Tree] (config>log>log-id from)
Full Context
configure log log-id from
Description
This command selects the source stream to be sent to a log destination.
One or more source streams must be specified. The source of the data stream must be identified using the from command before you can configure the destination using the to command. The from command can identify multiple source streams in a single statement (for example: from main change debug-trace).
Only one from command may be entered for a single log-id. If multiple from commands are configured, then the last command entered overwrites the previous from command.
The no form of this command removes all previously configured source streams.
Parameters
- main
-
Instructs all events in the main event stream to be sent to the destination defined in the to command for this destination log-id. The main event stream contains the events that are not explicitly directed to any other event stream. To limit the events forwarded to the destination, configure filters using the filter command.
- security
-
Instructs all events in the security event stream to be sent to the destination defined in the to command for this destination log-id. The security stream contains all events that affect attempts to breach system security such as failed login attempts, attempts to access MIB tables to which the user is not granted access or attempts to enter a branch of the CLI to which access has not been granted. To limit the events forwarded to the destination, configure filters using the filter command.
- change
-
Instructs all events in the user activity stream to be sent to the destination configured in the to command for this destination log-id. The change event stream contains all events that directly affect the configuration or operation of this node. To limit the events forwarded to the change stream destination, configure filters using the filter command.
- debug-trace
-
Instructs all debug-trace messages in the debug stream to be sent to the destination configured in the to command for this destination log-id. Filters applied to debug messages are limited to application and subject.
Platforms
All
from
Syntax
[no] from
Context
[Tree] (config>router>policy-options>policy-statement>entry from)
Full Context
configure router policy-options policy-statement entry from
Description
This command creates the context to configure policy match criteria based on a route’s source or the protocol from which the route is received.
If no condition is specified, all route sources are considered to match.
The no form of this command deletes the source match criteria for the route policy statement entry.
Platforms
All
from
Syntax
from ipv4-address
no from
Context
[Tree] (config>oam-pm>session>ip>tunnel>mpls>rsvp-te-auto from)
Full Context
configure oam-pm session ip tunnel mpls rsvp-te-auto from
Description
This command configures the headend of the RSVP LSP. Configure the following three commands to identify an RSVP-TE Auto LSP: from, to, and lsp-template. When all three of these values are configured, the specific RSVP LSP can be identified and the test packets can be carried across the tunnel
The no form of this command removes the IPv4 address.
Parameters
- ipv4-address
-
Specifies an IPv4 address.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
from-aa-sub-counters
from-aa-sub-counters
Syntax
[no] from-aa-sub-counters [all]
Context
[Tree] (config>log>acct-policy>cr>aa from-aa-sub-counters)
Full Context
configure log accounting-policy custom-record aa-specific from-aa-sub-counters
Description
Commands in this context configure Application Assurance "from subscriber” counter parameters. This command only applies to the 7750 SR.
The no form of this command excludes the "from subscriber” count.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
from-subscriber
from-subscriber
Syntax
from-subscriber
Context
[Tree] (config>isa>aa-grp>qos>egress from-subscriber)
Full Context
configure isa application-assurance-group qos egress from-subscriber
Description
Commands in this context configure Quality of Service for this application assurance group from-subscriber logical port, traffic entering the system from AA subscribers and entering an application assurance engine.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
from-vpls
from-vpls
Syntax
from-vpls service-id
no from-vpls
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp>mvr from-vpls)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping mvr from-vpls
Description
This command configures the VPLS from which multicast traffic is copied upon receipt of an IGMP join request.
IGMP snooping must be enabled on the MVR VPLS.
The no form of this command reverts to the default.
Parameters
- service-id
-
Specifies the MVR VPLS from which multicast channels be copied into an MSAP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
from-vpls
Syntax
from-vpls vpls-id
no from-vpls
Context
[Tree] (config>service>vpls>sap>mld-snooping>mvr from-vpls)
[Tree] (config>service>vpls>sap>igmp-snooping>mvr from-vpls)
Full Context
configure service vpls sap mld-snooping mvr from-vpls
configure service vpls sap igmp-snooping mvr from-vpls
Description
This command configures the VPLS from which multicast traffic is copied upon receipt of an IGMP join request. IGMP snooping must be enabled on the MVR VPLS.
Default
no from-vpls
Parameters
- vpls-id
-
Specifies the MVR VPLS from which multicast channels should be copied into this SAP
Platforms
All
frr
frr
Syntax
frr [detail]
no frr
Context
[Tree] (debug>router>mpls>event frr)
Full Context
debug router mpls event frr
Description
This command debugs fast re-route events.
The no form of the command disables the debugging.
Parameters
- detail
-
Displays detailed information about re-route events.
Platforms
All
frr-object
frr-object
Syntax
[no] frr-object
Context
[Tree] (config>router>mpls frr-object)
Full Context
configure router mpls frr-object
Description
This command specifies whether fast reroute for LSPs using the facility bypass method is signaled with or without the fast reroute object using the one-to-one keyword. The value is ignored if fast reroute is disabled for the LSP or if the LSP is using one-to-one Backup.
Default
frr-object — Specifies the value is by default inherited by all LSPs.
Platforms
All
fsm-state-changes
fsm-state-changes
Syntax
[no] fsm-state-changes
Context
[Tree] (debug>service>id>stp fsm-state-changes)
Full Context
debug service id stp fsm-state-changes
Description
This command enables STP debugging for FSM state changes.
The no form of the command disables debugging.
Platforms
All
fsm-timers
fsm-timers
Syntax
[no] fsm-timers
Context
[Tree] (debug>service>id>stp fsm-timers)
Full Context
debug service id stp fsm-timers
Description
This command enables STP debugging for FSM timer changes.
The no form of the command disables debugging.
Platforms
All
ftp
ftp
Syntax
[no] ftp
Context
[Tree] (config>service>nat>nat-policy>alg ftp)
[Tree] (config>service>nat>firewall-policy>alg ftp)
[Tree] (config>service>nat>up-nat-policy>alg ftp)
Full Context
configure service nat nat-policy alg ftp
configure service nat firewall-policy alg ftp
configure service nat up-nat-policy alg ftp
Description
This command enables FTP ALG.
The no form of the command disables FTP ALG.
Default
ftp
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat up-nat-policy alg ftp
- configure service nat nat-policy alg ftp
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy alg ftp
ftp
Syntax
ftp
Context
[Tree] (config>system>login-control ftp)
Full Context
configure system login-control ftp
Description
This command creates the context to configure FTP login control parameters.
Platforms
All
ftp-server
ftp-server
Syntax
[no] ftp-server
Context
[Tree] (config>system>security ftp-server)
Full Context
configure system security ftp-server
Description
This command enables FTP servers running on the system.
FTP servers are disabled by default. At system startup, only SSH servers are enabled.
The no form of this command disables FTP servers running on the system.
Platforms
All
function
function
Syntax
function
Context
[Tree] (config>service>vprn>srv6>ms-locator function)
[Tree] (config>router>segment-routing>srv6>inst>loc function)
[Tree] (config>service>vpls>srv6>ms-locator function)
[Tree] (config>service>vprn>srv6>locator function)
[Tree] (config>service>vpls>srv6>locator function)
[Tree] (config>service>epipe>srv6>locator function)
[Tree] (conf>router>segment-routing>srv6>inst>ms-locator function)
[Tree] (config>service>epipe>srv6>ms-locator function)
Full Context
configure service vprn segment-routing-v6 micro-segment-locator function
configure router segment-routing segment-routing-v6 base-routing-instance locator function
configure service vpls segment-routing-v6 micro-segment-locator function
configure service vprn segment-routing-v6 locator function
configure service vpls segment-routing-v6 locator function
configure service epipe segment-routing-v6 locator function
configure router segment-routing segment-routing-v6 base-routing-instance micro-segment-locator function
configure service epipe segment-routing-v6 micro-segment-locator function
Description
Commands in this context configure SRv6 and micro-segment SID function values and parameters for the locator.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
function-length
function-length
Syntax
function-length function-length
no function-length
Context
[Tree] (config>router>segment-routing>srv6>locator function-length)
Full Context
configure router segment-routing segment-routing-v6 locator function-length
Description
This command configures the length of the function field of an SRv6 locator.
The sum of the function length and the locator prefix length must not exceed 128 bits. This is enforced by CLI validation. Configuring a function length of 16 requires the configuration of the locator level label-block.
The no form of this command reverts to the default value.
Default
function-length 20
Parameters
- function-length
-
Specifies the function length, in bits.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
fwd-inside-router
fwd-inside-router
Syntax
fwd-inside-router router-instance
fwd-inside-router service-name service-name
no fwd-inside-router
Context
[Tree] (config>router>pcp-server>server fwd-inside-router)
Full Context
configure router pcp-server server fwd-inside-router
Description
This command configures the PCP forwarding inside virtual router instance.
The no form of this command reverts to the default value.
Default
no fwd-inside-router
Parameters
- router-instance
-
Specifies the router name or the VPRN service ID.
- service-name
-
Specifies the service name, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
fwd-path-ext
fwd-path-ext
Syntax
fwd-path-ext
Context
[Tree] (config fwd-path-ext)
Full Context
configure fwd-path-ext
Description
Commands in this context configure a Forwarding Path Extension (FPE). FPE is used by certain applications that rely on PXC functionality to simplify the configuration of those applications.
Platforms
All
fwd-wholesale
fwd-wholesale
Syntax
fwd-wholesale
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap fwd-wholesale)
[Tree] (config>service>vprn>if>sap fwd-wholesale)
Full Context
configure service vprn subscriber-interface group-interface sap fwd-wholesale
configure service vprn interface sap fwd-wholesale
Description
Commands in this context select specific protocols ingressing on the SAP to be redirected to another service. The command is applicable to static SAPs as well as PW-SAPs.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fwd-wholesale
Syntax
fwd-wholesale
Context
[Tree] (config>service>ies>if>sap fwd-wholesale)
Full Context
configure service ies interface sap fwd-wholesale
Description
Commands in this context select specific protocols ingressing on the SAP to be redirected to another service. The command is applicable to static SAPs as well as PW-SAPs.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
fwd-wholesale
Syntax
[no] fwd-wholesale
Context
[Tree] (config>service>ies>sub-if>grp-if>sap fwd-wholesale)
Full Context
configure service ies subscriber-interface group-interface sap fwd-wholesale
Description
Commands in this context select specific protocols ingressing on the SAP to be redirected to another service. The command is applicable to static SAPs as well as PW-SAPs.
The no form of this command removes the redirection.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR