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.

Values

kernel, user, mail, systemd, auth, syslogd, printer, netnews, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, cron2, local0, local1, local2, local3, local4, local5, local6, local7

Valid responses per RFC3164, The BSD syslog Protocol, are listed in Syslog Facility Codes.

Table 1. Syslog Facility Codes

Numerical Code

Facility Code

0

kernel

1

user

2

mail

3

systemd

4

auth

5

syslogd

6

printer

7

net-news

8

uucp

9

cron

10

auth-priv

11

ftp

12

ntp

13

log-audit

14

log-alert

15

cron2

16

local0

17

local1

18

local2

19

local3

20

local4

21

local5

22

local6

23

local7

Values: 0 to 23

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.

Values

kernel, user, mail, systemd, auth, syslogd, printer, netnews, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, cron2, local0, local1, local2, local3, local4, local5, local6, local7

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.

Values

kernel, user, mail, systemd, auth, syslogd, printer, netnews, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, cron2, local0, local1, local2, local3, local4, local5, local6, local7

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.

Values

kernel, user, mail, systemd, auth, syslogd, printer, netnews, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, cron2, local0, local1, local2, local3, local4, local5, local6, local7

Valid responses per RFC 3164, The BSD syslog Protocol, are listed in Syslog Protocol Valid Responses.

Table 2. Syslog Protocol Valid Responses

Numerical Code

Facility Code

0

kernel

1

user

2

mail

3

systemd

4

auth

5

syslogd

6

printer

7

net-news

8

uucp

9

cron

10

auth-priv

11

ftp

12

ntp

13

log-audit

14

log-alert

15

cron2

16

local0

17

local1

18

local2

19

local3

20

local4

21

local5

22

local6

23

local7

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.

Note:

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.

Values

drop, forward

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>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check fail-action)

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check fail-action)

Full Context

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check fail-action

configure service vprn 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.

Values

1 to 4294967295

preference-value

Specifies the route preference associated with the provisioned managed route if the CPE check fails.

Values

0 to 255

tag-value

Specifies the route tag used if the CPE check fails.

Values

1 to 4294967295

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 fail-on-error)

[Tree] (config>card>xiom fail-on-error)

Full Context

configure card fail-on-error

configure card xiom 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

All

  • configure card fail-on-error

7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s

  • configure card xiom 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.

Values

1 to 2

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>router>dhcp6>server>pool failover)

[Tree] (config>service>vprn>dhcp6>server>pool failover)

[Tree] (config>service>vprn>dhcp6>server failover)

[Tree] (config>service>vprn>dhcp>server>pool failover)

[Tree] (config>router>dhcp>server>pool failover)

[Tree] (config>router>dhcp>server failover)

[Tree] (config>service>vprn>dhcp>server failover)

[Tree] (config>router>dhcp6>server failover)

Full Context

configure router dhcp6 local-dhcp-server pool failover

configure service vprn dhcp6 local-dhcp-server pool failover

configure service vprn dhcp6 local-dhcp-server failover

configure service vprn dhcp local-dhcp-server pool failover

configure router dhcp local-dhcp-server pool failover

configure router dhcp local-dhcp-server failover

configure service vprn dhcp local-dhcp-server failover

configure router dhcp6 local-dhcp-server 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>service>vprn>l2tp failover)

[Tree] (config>router>l2tp failover)

[Tree] (config>service>vprn>l2tp>group>tunnel failover)

[Tree] (config>router>l2tp>group failover)

[Tree] (config>service>vprn>l2tp>group failover)

[Tree] (config>router>l2tp>group>tunnel failover)

Full Context

configure service vprn l2tp failover

configure router l2tp failover

configure service vprn l2tp group tunnel failover

configure router l2tp group failover

configure service vprn l2tp group failover

configure router 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>ies>interface>spoke-sdp>bfd failure-action)

[Tree] (config>service>vpls>spoke-sdp>bfd failure-action)

[Tree] (config>service>vprn>interface>spoke-sdp>bfd failure-action)

[Tree] (config>service>epipe>spoke-sdp>bfd failure-action)

Full Context

configure service ies interface spoke-sdp bfd failure-action

configure service vpls spoke-sdp bfd failure-action

configure service vprn interface spoke-sdp bfd failure-action

configure service epipe 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.

Values

2 to 10

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-template fallback-path-computation-method)

[Tree] (config>router>mpls>lsp fallback-path-computation-method)

Full Context

configure router mpls lsp-template fallback-path-computation-method

configure router mpls lsp 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.

Values

1 to 100 percent

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

Values

ipv4, ipv6

Platforms

All

family

Syntax

[no] family {ipv4 | ipv6 | label-ipv4 | flow-ipv4 | flow-ipv6}

Context

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived family)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived family)

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived family)

Full Context

configure service vprn bgp group graceful-restart long-lived family

configure service vprn bgp group neighbor graceful-restart long-lived family

configure service vprn bgp 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 family)

[Tree] (config>service>vprn>bgp>group family)

[Tree] (config>service>vprn>bgp>group>neighbor family)

Full Context

configure service vprn bgp family

configure service vprn bgp group family

configure service vprn bgp group neighbor 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.

Values

ipv4, ipv6, vpn-ipv4, vpn-ipv6, label-ipv4, label-ipv6

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 family)

[Tree] (config>router>bgp family)

[Tree] (config>router>bgp>group>neighbor family)

Full Context

configure router bgp group family

configure router bgp family

configure router bgp group neighbor 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>graceful-restart>long-lived family)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived family)

[Tree] (config>router>bgp>group>graceful-restart>long-lived family)

Full Context

configure router bgp graceful-restart long-lived family

configure router bgp group neighbor graceful-restart long-lived family

configure router bgp group 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>neighbor>srv6>route family)

[Tree] (config>router>bgp>group>srv6>route family)

Full Context

configure router bgp group neighbor segment-routing-v6 route-advertisement family

configure router bgp group 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.

Caution:

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.

Values

1.0.0.1 to 223.255.255.254

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.

Values

2048 to 18431

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>mld-snooping fast-leave)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping fast-leave)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping fast-leave)

[Tree] (config>service>vpls>sap>igmp-snooping fast-leave)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping fast-leave)

[Tree] (config>service>vpls>sap>mld-snooping fast-leave)

Full Context

configure service vpls mesh-sdp mld-snooping fast-leave

configure service vpls spoke-sdp mld-snooping fast-leave

configure service vpls mesh-sdp igmp-snooping fast-leave

configure service vpls sap igmp-snooping fast-leave

configure service vpls spoke-sdp 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-template fast-reroute)

[Tree] (config>router>mpls>lsp fast-reroute)

Full Context

configure router mpls lsp-template fast-reroute

configure router mpls lsp 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.

Note:

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.

Values

one-to-one — In the one-to-one technique, a label switched path is established which intersects the original LSP somewhere downstream of the point of link or node failure. For each LSP which is backed up, a separate backup LSP is established.

Values

facility — This option, sometimes called many-to-one, takes advantage of the MPLS label stack. Instead of creating a separate LSP for every backed-up LSP, a single LSP is created which serves to backup up a set of LSPs. This LSP tunnel is called a bypass tunnel.

The bypass tunnel must intersect the path of the original LSP(s) somewhere downstream of the point of local repair (PLR). Naturally, this constrains the set of LSPs being backed-up through that bypass tunnel to those that pass through a common downstream node. All LSPs which pass through the PLR and through this common node which do not also use the facilities involved in the bypass tunnel are candidates for this set of LSPs.

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>sap fault-propagation-bmac)

[Tree] (config>service>vpls>spoke-sdp fault-propagation-bmac)

[Tree] (config>service>vpls>mesh-sdp fault-propagation-bmac)

Full Context

configure service vpls sap fault-propagation-bmac

configure service vpls spoke-sdp fault-propagation-bmac

configure service vpls mesh-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>epipe>spoke-sdp>eth-cfm>mep fault-propagation-enable)

[Tree] (config>service>ipipe>sap>eth-cfm>mep fault-propagation-enable)

[Tree] (config>service>epipe>sap>eth-cfm>mep fault-propagation-enable)

Full Context

configure service epipe spoke-sdp eth-cfm mep fault-propagation-enable

configure service ipipe sap eth-cfm mep fault-propagation-enable

configure service epipe sap 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>mesh-sdp>eth-cfm>mep fault-propagation-enable)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep fault-propagation-enable)

[Tree] (config>service>vpls>sap>eth-cfm>mep fault-propagation-enable)

Full Context

configure service vpls mesh-sdp eth-cfm mep fault-propagation-enable

configure service vpls spoke-sdp eth-cfm mep fault-propagation-enable

configure service vpls sap 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>spoke-sdp>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>sap>eth-cfm>mep fault-propagation-enable)

Full Context

configure service vprn interface spoke-sdp eth-cfm mep fault-propagation-enable

configure service vprn subscriber-interface group-interface sap eth-cfm fault-propagation-enable

configure service vprn interface sap 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 sap eth-cfm mep fault-propagation-enable
  • configure service vprn interface spoke-sdp 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.

Values

nc, h1, ef, h2, l1, af, l2, be

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.

Values

nc, h1, ef, h2, l1, af, l2, be

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>if>sap>eth-cfm>collect-lmm-fc-stats fc)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>collect-lmm-fc-stats fc)

Full Context

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

configure service ies subscriber-interface group-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.

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.

Values

nc, h1, ef, h2, l1, af, l2, be

Platforms

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

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

fc

Syntax

fc fc-name [fc-name]

no fc

Context

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>collect-lmm-fc-stats fc)

[Tree] (config>service>vprn>sub-if>grp-if>sap>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 interface spoke-sdp eth-cfm collect-lmm-fc-stats fc

configure service vprn subscriber-interface group-interface sap 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.

Values

nc, h1, ef, h2, l1, af, l2, be

Platforms

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

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

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.

Values

1 to 4 (in system profile None/A)

1 to 6 (in system profile B)

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.

Table 3. 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.

Values

0 to 7

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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>up-nat-policy>priority-sessions fc)

[Tree] (config>service>nat>firewall-policy>priority-sessions fc)

Full Context

configure service nat nat-policy priority-sessions fc

configure service nat up-nat-policy priority-sessions fc

configure service nat firewall-policy priority-sessions fc

Description

This command configures the forwarding classes that have their sessions prioritized.

Parameters

fc-name

Specifies the forwarding class.

Values

be, l2, af, l1, h2, ef, h1, nc

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

  • configure service nat up-nat-policy priority-sessions fc
  • configure service nat 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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Table 4. fc Request Packet and Behavior

CPM (sender node)

Echo request packet:

  • packet {tos=1, fc1, profile1}

  • fc1 and profile1 are as entered by user in OAM command or default values

  • tos1 as per mapping of {fc1, profile1} to IP precedence in network egress QoS policy of outgoing interface

Outgoing interface (sender node)

Echo request packet:

  • pkt queued as {fc1, profile1}

  • ToS field=tos1 not remarked

  • EXP=exp1, as per mapping of {fc1, profile1} to EXP in network egress QoS policy of outgoing interface

Incoming interface (responder node)

Echo request packet:

  • packet {tos1, exp1}

  • exp1 mapped to {fc2, profile2} as per classification in network QoS policy of incoming interface

CPM (responder node)

Echo reply packet:

  • packet {tos=1, fc2, profile2}

Outgoing interface (responder node)

Echo reply packet:

  • pkt queued as {fc2, profile2}

  • ToS filed= tos1 not remarked (reply inband or out-of-band)

  • EXP=exp2, if reply is inband, remarked as per mapping of {fc2, profile2} to EXP in network egress QoS policy of outgoing interface

Incoming interface (sender node)

Echo reply packet:

  • packet {tos1, exp2}

  • exp2 mapped to {fc1, profile1} as per classification in network QoS policy of incoming interface

Default

no fc

Parameters

fc-name

Specifies the forwarding class of the MPLS echo request packets.

Values

be, l2, af, l1, h2, ef, h1, nc

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-trace>sr-policy fc)

[Tree] (config>saa>test>type-multi-line>lsp-ping>sr-policy fc)

[Tree] (config>saa>test>type-multi-line>lsp-ping fc)

Full Context

configure saa test type-multi-line lsp-trace sr-policy fc

configure saa test type-multi-line lsp-ping 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.

Values

be, l2, af, l1, h2, ef, h1, nc

Default

be

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.

Values

be, l2, af, l1, h2, ef, h1, nc

Default

be

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.

Values

be — Specifies best effort

l2 — Specifies low-2

af — Specifies assured

l1 — Specifies low-1

h2 — Specifies high-2

ef — Specifies expedited

h1 — Specifies high-1

nc — Specifies network control

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.

Values

be, l2, af, l1, h2, ef, h1, nc

profile

Specifies one of the egress packet profile states.

Values

exceed, in, inplus, out

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.

Values

fc:

class[.subclass]

class: be, l2, af, l1, h2, ef, h1, nc

subclass: 29 characters max

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

be, l1, af, l2, h1, ef, h2, nc

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.

Values

be, l2, af, l1, h2, ef, h1, nc

Platforms

All

fc

Syntax

fc fc-name

no fc

Context

[Tree] (config>filter>ipv6-filter>entry>action fc)

[Tree] (config>filter>ip-filter>entry>action fc)

Full Context

configure filter ipv6-filter entry action fc

configure filter ip-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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

nc, h1, ef, h2, l1, af, l2, be

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.

Values

be, l2, af, 1, h2, ef, h1, nc

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.

Values

be, l2, af, l1, h2, ef, h1, nc

Default

none (no QoS information is associated with matched routes)

priority {low | high}

This parameter associates an enqueuing priority with routes matched by the policy entry. Specifying a priority is optional.

Values

high — Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. After the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.

low — Setting the enqueuing parameter to low for a packet decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. After the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.

Default

low

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.

Values

be, l2, af, l1, h2, ef, h1, nc

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.

Values

nc, h1, ef, h2, l1, af, l2, be

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 spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)

[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)

Full Context

configure service vpls spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile

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

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.

Values

nc, h1, ef, h2, l1, af, l2, be

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 if spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile)

[Tree] (config service ies sub-if grp-if sap 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 interface spoke-sdp eth-cfm collect-lmm-fc-stats fc-in-profile

configure service ies subscriber-interface group-interface sap 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.

Values

nc, h1, ef, h2, l1, af, l2, be

Platforms

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

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

fc-in-profile

Syntax

fc-in-profile fc-name [fc-name]

no fc-in-profile

Context

[Tree] (config service vprn if sap eth-cfm collect-lmm-fc-stats fc-in-profile)

[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)

Full Context

configure service vprn interface sap eth-cfm collect-lmm-fc-stats fc-in-profile

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

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.

Values

nc, h1, ef, h2, l1, af, l2, be

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

  • configure service vprn 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

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

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.

Values

nc, h1, ef, h2, l1, af, l2, be

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>session fcc)

[Tree] (config>isa>video-group>watermark>bandwidth fcc)

Full Context

configure isa video-group watermark session fcc

configure isa video-group watermark bandwidth 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.

Values

1 to 99

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 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>hd fcc-burst)

[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)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface hd fcc-burst

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

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.

Values

HD:

0 to 100

SD and PIP:

0 to 600

Default

25

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 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-1, 7750 SR-7/12/12e, 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>channel>video fcc-min-duration)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video fcc-min-duration)

Full Context

configure mcast-management multicast-info-policy bundle channel video fcc-min-duration

configure mcast-management multicast-info-policy bundle 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.

Values

300 to 8000

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 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-1, 7750 SR-7/12/12e, 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-1, 7750 SR-7/12/12e, 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-1, 7750 SR-7/12/12e, 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-1, 7750 SR-7/12/12e, 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.

Values

5 to 300

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 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.

Note:

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>vpls fdb-table-high-wmark)

[Tree] (config>service>template>vpls-template fdb-table-high-wmark)

Full Context

configure service vpls fdb-table-high-wmark

configure service template vpls-template 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.

Values

0 to 100

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.

Values

0 to 100

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.

Values

7450 ESS, 7950 XRS, or 7750 SR-7, SR-12, SR-12e: 1 to 511999

7750 SR-e, SR-a: 1 to 250000

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.

Values

255999 to 2047999

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.

Values

local-forward

Values

transparent-clock-eth

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:

  1. Generates a trap and a syslog message.

  2. 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.

  3. 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.

Values

ipv4-prefix - a.b.c.d

ipv4-prefix-le - [0..32]

ipv6-prefix

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x - [0..FFFF]H

d - [0..255]D

ipv6-prefix-le - [0..128]

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.

Values

16 to 1048575

in-label

Specifies the number of labels to send to the peer associated with this FEC.

Values

32 to 1023

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.

Values

IPv4 prefix:

a.b.c.d

a, b, c, d - 0 to 255; decimal

IPv6 prefix:

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x - 0 to FFFF; hexadecimal

x:x:x:x:x:x:d.d.d.d

mask

Specifies the mask of the IP address.

Values

IPv4: 0 to 32

IPv6: 0 to 128

Platforms

All

fec-type-capability

fec-type-capability

Syntax

fec-type-capability

Context

[Tree] (config>router>ldp>session-params>peer fec-type-capability)

[Tree] (config>router>ldp>if-params>if>ipv4 fec-type-capability)

[Tree] (config>router>ldp>if-params>if>ipv6 fec-type-capability)

Full Context

configure router ldp session-parameters peer fec-type-capability

configure router ldp interface-parameters interface ipv4 fec-type-capability

configure router ldp interface-parameters interface ipv6 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>rtp-perf>video-template>dynamic-fields field)

[Tree] (config>app-assure>group>cflowd>rtp-perf>audio-template>dynamic-fields field)

[Tree] (config>app-assure>group>cflowd>rtp-perf>voice-template>dynamic-fields field)

[Tree] (config>app-assure>group>cflowd>tcp-perf>template>dynamic-fields field)

[Tree] (config>app-assure>group>cflowd>volume>template>dynamic-fields field)

[Tree] (config>app-assure>group>cflowd>comp>template>dynamic-fields field)

Full Context

configure application-assurance group cflowd rtp-performance video-template dynamic-fields field

configure application-assurance group cflowd rtp-performance audio-template dynamic-fields field

configure application-assurance group cflowd rtp-performance voice-template dynamic-fields field

configure application-assurance group cflowd tcp-performance template dynamic-fields field

configure application-assurance group cflowd volume template dynamic-fields field

configure application-assurance group cflowd comprehensive 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.

Values

Common to all templates

session/flowStartSeconds, session/flowDurationMilliseconds, postIpPrecedence, ipTTL, aaProt, aaApp, aaAppGrp, hostName, deviceId, deviceMfgId, deviceOsId, ipFamily, deviceOsVer1, deviceOsVer2, deviceOsVer3, anlType, anlTopology, anlCongestionState, timeZone, aaChargingGrp, flowAttr_video, flowAttr_abr_service, flowAttr_audio, flowAttr_encrypted, flowAttr_download, flowAttr_upload, flowAttr_realtime_communication, aaSubTetheringState

When AA is deployed in FWA SR: ApnExtended

For the TCP and comprehensive templates only

tcpSessionEstDelay, tcpRetransmittedBytes, tcpRetransmittedPackets

For the rtp-voice template only

rtpBurstCount, rtpAvgBurstLengthMs, rtpGapCount, rtpAvgGapLengthMs, MAPDV, RBurst, RGap, SSRC

For the rtp-video template only

rtpRefClockRate, MOSAV, VSTQ, estimatedPSNR, GoPType, avgGoPLength, avgInterIFrameGap, imageWidth, imageHeight, frameRate, slicesPerIFrame, SSRC, videoInterlaced, IFrameReceived, IFrameImpaired, PFrameReceived, PFrameImpaired, BFrameReceived, BFrameImpaired, SIFrameReceived, SIFrameImpaired, SPFrameReceived, SPFrameImpaired, frameInterArrivalJitter, IFrameInterArrivalJitter, avgFrameArrivalDelay

For the rtp-audio template only

frtpBurstCount, rtpAvgBurstLengthPkts, rtpGapCount, rtpAvgGapLengthPkts, PPDVM, rtpNumAudioChannels, rtpRefClockRate, rtpPeakAudioBw, SSRC, hostName

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.

Note:

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.

Values

The following parameters are supported in any deployment:

  • static-string — header name for the inserted string

  • static-string-2 — header name for the inserted string

  • subscriber-id — header name for the subscriber ID

  • subscriber-ip — header name for the subscriber IP address

The following parameters are supported in Fixed Wireless Access (FWA) deployments only:

  • apn — APN used by the UE

  • apn-ni — APN Network Identifier (APN-NI) used by the UE

  • billing-type — UE charging type (charging characteristics)

  • dynamic-acr — dynamic Anonymous Customer Record (ACR)

  • static-acr — static ACR

  • imei-sv — subscriber IMEI with format AABBBBBBCCCCCCEE

  • imei-hyphenated — subscriber IMEI with format AABBBBBB-CCCCCC-EE

  • imei-hyphenated-2 — subscriber IMEI with format AABBBBBB-CCCCCC-EE

  • imsi — subscriber IMSI

  • imsi-2 — subscriber IMSI

  • msisdn — subscriber MSISDN

  • msisdn-ts — subscriber MSISDN appended with the UNIX timestamp

  • msisdn-without-cc — subscriber MSISDN without a country code

  • pgw_ggsn-address — PGW/GGSN address serving the UE

  • plmn-id — Public Land Mobile Network (PLMN) ID of the SGSN/MME

  • rat-type — Radio Access Technology (RAT) type

  • timestamp — timestamp inserted in UNIX time format Example: 1531204313

  • user-location — UE LOCATION (ULI)

  • user-location-3gpp — ULI encoded as defined in 3GPP 29.061

  • user-location-raw — ULI in raw format <ULI-TYPE1>[+<ULI-TYPE2>]=<ULI HEX>

    Example: x-locinfo: TAI+ECGI=1300622c46130062014adf16

  • user-location-raw-2 — ULI in raw format <ULI-TYPE1>[+<ULI-TYPE2>]=<ULI HEX>

    Example: x-locinfo: TAI+ECGI=1300622c46130062014adf16

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>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)

[Tree] (config>app-assure>group>cflowd>rtp-perf>voice-template field-selection)

[Tree] (config>app-assure>group>cflowd>rtp-perf>audio-template field-selection)

[Tree] (config>app-assure>group>cflowd>volume>template field-selection)

Full Context

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

configure application-assurance group cflowd rtp-performance voice-template field-selection

configure application-assurance group cflowd rtp-performance audio-template field-selection

configure application-assurance group cflowd volume 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.

Values

[cflash-id/] file-path: [200 chars max]

cflash-id: - cf1: | cf1-A: | cf1-B: | cf2: | cf2-A: | cf2-B: | cf3: | cf3-A: | cf3-B:

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.

Table 5. 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.

Values

1 to 99

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.

Values

ftp – The file transfer FTP protocol is used between 7750 SR or 7950 XRS host and the 7210 SAS Ethernet satellite.

scp - The file transfer SCP protocol is used between the 7750 SR or 7950 XRS host and the 7210 SAS Ethernet satellite.

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.

Values

[local-url | remote-url]

where:

  • local-url — [cflash-id/] [file-path]

    180 chars max, including cflash-id

    directory length 99 chars max each

  • remote-url — [{ftp://| tftp://} login:pswd@remote-locn/][ file-path]

    180 chars max

    directory length 99 chars max each

    where: remote-locn — [hostname | ipv4-address | ipv6-address]

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x - [0..FFFF]H

d - [0..255]D

interface - 32 chars max, for link

local addresses

cflash-id

cf1:| cf1-A:| cf1-B:| cf2:| cf2-A:| cf2-B:| cf3:| cf3-A:| cf3-B:

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.

Values

1 to 65535

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>ies>sub-if>grp-if>dhcp6 filter)

[Tree] (config>service>vprn>sub-if>grp-if>dhcp6 filter)

Full Context

configure service ies subscriber-interface group-interface dhcp6 filter

configure service vprn 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

Values

1 to 65535

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>spoke-sdp>ingress filter)

[Tree] (config>service>vprn>nw-if>egress filter)

[Tree] (config>service>vprn>red-if>spoke-sdp>ingress filter)

[Tree] (config>service>vprn>red-if>spoke-sdp>egress filter)

[Tree] (config>service>vprn>if>spoke-sdp>egress filter)

Full Context

configure service vprn interface spoke-sdp ingress filter

configure service vprn network-interface egress filter

configure service vprn redundant-interface spoke-sdp ingress filter

configure service vprn redundant-interface spoke-sdp egress filter

configure service vprn 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.

Values

1 to 65535

Platforms

All

  • configure service vprn network-interface egress filter
  • configure service vprn interface spoke-sdp egress filter
  • configure service vprn interface spoke-sdp ingress filter

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

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>ies>sub-if>grp-if>sap>egress filter)

[Tree] (config>service>ies>red-if>egress filter)

[Tree] (config>service>ies>if>sap>ingress filter)

[Tree] (config>service>ies>if>sap>egress filter)

[Tree] (config>service>vprn>sub-if>grp-if>sap>egress filter)

[Tree] (config>service>vprn>sub-if>grp-if>sap>ingress filter)

[Tree] (config>service>ies>sub-if>grp-if>sap>ingress filter)

[Tree] (config>service>ies>red-if>ingress filter)

Full Context

configure service ies subscriber-interface group-interface sap egress filter

configure service ies red-if egress filter

configure service ies interface sap ingress filter

configure service ies interface sap egress filter

configure service vprn subscriber-interface group-interface sap egress filter

configure service vprn subscriber-interface group-interface sap ingress filter

configure service ies subscriber-interface group-interface sap ingress filter

configure service ies red-if ingress 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.

Values

1 to 65535

ipv6 ipv6-filter-id

Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.

Values

1 to 65535

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.

Values

1 to 65535

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

  • configure service ies subscriber-interface group-interface sap egress filter
  • configure service vprn subscriber-interface group-interface sap ingress filter
  • configure service ies subscriber-interface group-interface sap ingress filter
  • configure service vprn subscriber-interface group-interface sap egress filter

All

  • configure service ies interface sap egress filter
  • configure service ies interface sap ingress 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>spoke-sdp>egress filter)

[Tree] (config>service>vpls>spoke-sdp>ingress filter)

[Tree] (config>service>vpls>mesh-sdp>egress filter)

[Tree] (config>service>vpls>mesh-sdp>ingress filter)

[Tree] (config>service>vpls>sap>egress filter)

[Tree] (config>service>vpls>sap>ingress filter)

Full Context

configure service vpls spoke-sdp egress filter

configure service vpls spoke-sdp ingress filter

configure service vpls mesh-sdp egress filter

configure service vpls mesh-sdp ingress filter

configure service vpls sap egress filter

configure service vpls sap 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.

Values

1 to 65535

ipv6 ipv6-filter-id

Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.

Values

1 to 65535

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.

Values

1 to 65535

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>ipipe>spoke-sdp>ingress filter)

[Tree] (config>service>cpipe>spoke-sdp>ingress filter)

[Tree] (config>service>ipipe>sap>egress filter)

[Tree] (config>service>ipipe>sap>ingress filter)

[Tree] (config>service>cpipe>spoke-sdp>egress filter)

Full Context

configure service ipipe spoke-sdp egress filter

configure service ipipe spoke-sdp ingress filter

configure service cpipe spoke-sdp ingress filter

configure service ipipe sap egress filter

configure service ipipe sap ingress filter

configure service cpipe spoke-sdp egress 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.

Values

1 to 65535

ipv6-filter-id

Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.

Values

1 to 65535

Platforms

All

  • configure service ipipe sap egress filter
  • configure service ipipe sap ingress filter
  • configure service ipipe spoke-sdp ingress 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 egress filter
  • configure service cpipe spoke-sdp ingress 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>ingress filter)

[Tree] (config>service>epipe>spoke-sdp>ingress filter)

[Tree] (config>service>epipe>spoke-sdp>egress filter)

[Tree] (config>service>epipe>sap>egress filter)

Full Context

configure service epipe sap ingress filter

configure service epipe spoke-sdp ingress filter

configure service epipe spoke-sdp egress filter

configure service epipe sap egress 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.

Values

1 to 65535

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.

Values

1 to 65535

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.

Values

1 to 65535

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>egress filter)

[Tree] (config>service>ies>aarp-interface>spoke-sdp>ingress filter)

Full Context

configure service ies aarp-interface spoke-sdp egress filter

configure service ies 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.

Values

1 to 65535 or a string up to 64 characters

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.

Values

1 to 65535 or a string up to 64 characters

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.

Values

ip-filter-id: 1 to 65535

name: up to 64 characters

ipv6 ipv6-filter-id

Specifies IPv6 filter policy. The filter ID must already exist within the created IP filters.

Values

ip-filter-id: 1 to 65535

name: up to 64 characters

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.

Values

1 to 1500

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.

Values

1 to 65535, name

name: 64 characters maximum

Platforms

All

filter

Syntax

filter ip ip-filter-id

no filter [ip ip-filter-id]

Context

[Tree] (config>service>ies>aa-if>sap>egress filter)

[Tree] (config>service>vprn>aa-if>sap>egress filter)

Full Context

configure service ies aa-interface sap egress filter

configure service vprn 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.

Values

1 to 65535, or name up to 64 characters maximum

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>ies>video-interface>video-sap>egress filter)

[Tree] (config>service>vprn>video-interface>video-sap>ingress filter)

[Tree] (config>service>vprn>video-interface>video-sap>egress filter)

[Tree] (config>service>ies>video-interface>video-sap>ingress filter)

Full Context

configure service ies video-interface video-sap egress filter

configure service vprn video-interface video-sap ingress filter

configure service vprn video-interface video-sap egress filter

configure service ies 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.

Values

1 to 65535

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 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.

Values

1 to 65525 or a name, up to 64 characters.

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.

Values

1 to 1000

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.

Values

1 to 16384

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.

Values

1 to 65535

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.

Values

1 to 65535

ipv6-filter-id

Specifies the IPv6 filter policy.

Values

1 to 65535

mac-filter-id

Specifies the MAC filter policy.

Values

1 to 65535

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.

Values

1 to 1500

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.

Values

1 to 1000

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.

Values

1 to 2147483647

end filter-id

Specifies the upper value of the ID range. The value must be greater than or equal to the start value.

Values

1 to 2147483647

Platforms

All

filter-name

filter-name

Syntax

[no] filter-name

Context

[Tree] (config>service>template>epipe-sap-template>egress filter-name)

[Tree] (config>service>template>epipe-sap-template>ingress filter-name)

Full Context

configure service template epipe-sap-template egress filter-name

configure service template epipe-sap-template ingress 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>ingress filter-name)

[Tree] (config>service>template>vpls-sap-template>egress filter-name)

Full Context

configure service template vpls-sap-template ingress filter-name

configure service template vpls-sap-template egress 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>ip-filter>entry filter-sample)

[Tree] (config>filter>ipv6-filter>entry filter-sample)

Full Context

configure filter ip-filter entry filter-sample

configure filter ipv6-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>up-nat-policy filtering)

[Tree] (config>service>nat>nat-policy filtering)

[Tree] (config>service>nat>firewall-policy filtering)

Full Context

configure service nat up-nat-policy filtering

configure service nat 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.

Values

address-and-port-dependent, endpoint-independent

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.

Values

1 to 65535

physical-port-id

Specifies the physical port ID that is injected into the specified build-packet.

Values

slot/mda/port

esat-<sat-id>/slot/port

esat

keyword

id

1 to 20

slot

always 1

port

Ethernet satellite client port number

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

fips-140-2

fips-140-2

Syntax

[no] fips-140-2

Context

[Tree] (bof fips-140-2)

Full Context

bof fips-140-2

Description

This command is used to configure the node in FIPS-140-2 mode. Before using this command, the operator must ensure that no current configuration exists in the config file that is not supported in FIPS-140-2 mode. Failing to remove unsupported configuration will result in the node being unable to boot up. The node must be rebooted after executing this command in order for the node to begin operating in FIPS-140-2 mode.

Platforms

All

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.

Values

1 to 102400, default

Platforms

7750 SR-1, 7750 SR-s

firewall

firewall

Syntax

firewall

Context

[Tree] (config>router firewall)

[Tree] (config>service>vprn firewall)

Full Context

configure router firewall

configure service vprn firewall

Description

Commands in this context configure firewall parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

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.

Values

128 to 255

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.

Values

128 to 255

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.

Values

128 to 255

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.

Values

128 to 255

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.

Note:

  • 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.

Values

128 to 255

param-name

Specifies the parameter name, up to 32 characters, that starts and ends with an at-sign (@) symbol.

Platforms

All

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>vprn>if>vpls>evpn>arp flood-garp-and-unknown-req)

[Tree] (config>service>ies>if>vpls>evpn>arp flood-garp-and-unknown-req)

Full Context

configure service vprn interface vpls evpn arp flood-garp-and-unknown-req

configure service ies 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.

Values

3 to 600

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

Values

3 to 600

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.

Values

video

This attribute specifies streaming or real-time video media traffic transferred between a sender and receiver. It does not differentiate adaptive and nonadaptive video streaming. Assigned to flows based on packet payload inspection (many protocols) or behavioral mechanisms, and may be used together with the RTC attribute to identify video call traffic.

abr_service

This attribute is assigned to adaptive bit rate traffic exchanges where the traffic rate or behavior can be automatically adjusted based on changes in network conditions. Assigned by application filter configuration or by behavioral mechanisms.

audio

This attribute is assigned to streaming or real-time audio media traffic transferred between a sender and receiver. Assigned to flows based on packet payload inspection or behavioral mechanisms, and may be used together with the RTC attribute to identify voice call traffic.

encrypted

This attribute is assigned to traffic exchanges where the initial payload or the entirety of the exchange is encrypted. Assigned to sessions based on packet payload inspection or by behavioral mechanisms.

download

This attribute is assigned to traffic that has a high likelihood of exchanging data predominantly in the network to subscriber direction over the lifetime of a session. May be assigned to sessions based on behavioral mechanisms.

upload

This attribute is assigned to traffic that has a high likelihood of exchanging data predominantly in the subscriber to network direction over the lifetime of the session. The upload and download attributes are mutually exclusive. Assigned to sessions based on behavioral mechanisms.

real_time_communication

This attribute is assigned to traffic that provides a low latency or real-time exchange of information between two or more communicating endpoints. Assigned by packet payload inspection of an RTP protocol being used or by behavioral mechanisms.

esni

This attribute is assigned to traffic that uses an encrypted server name indication (eSNI), as part of the TLS layer negotiation

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.

Values

0 to 100000000, max

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.

Values

0 to 1048575

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.

Values

0 to 1048575

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.)

Values

0 to 1048575

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.)

Values

0 to 1048575

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>service>vprn>nw-if>load-balancing flow-label-load-balancing)

[Tree] (config>service>vprn>if>load-balancing flow-label-load-balancing)

[Tree] (config>service>ies>if>load-balancing flow-label-load-balancing)

[Tree] (config>router>if>load-balancing flow-label-load-balancing)

Full Context

configure service vprn network-interface load-balancing flow-label-load-balancing

configure service vprn interface load-balancing flow-label-load-balancing

configure service ies interface load-balancing flow-label-load-balancing

configure router 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>rtp-perf flow-rate)

[Tree] (config>app-assure>group>cflowd>tcp-perf flow-rate)

Full Context

configure application-assurance group cflowd comprehensive flow-rate

configure application-assurance group cflowd rtp-performance flow-rate

configure application-assurance group cflowd tcp-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.

Values

1 to 1000

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>rtp-perf flow-rate2)

[Tree] (config>app-assure>group>cflowd>comp flow-rate2)

[Tree] (config>app-assure>group>cflowd>tcp-perf flow-rate2)

Full Context

configure application-assurance group cflowd rtp-performance flow-rate2

configure application-assurance group cflowd comprehensive 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.

Values

1 to 1000

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.

Values

1 to 800000, max flows/sec (disabled)

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.

Values

1 to 799999 flows/sec

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.

Values

0 to 100

Default

95

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.

Values

0 to 100

Default

90

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.

Values

1 to 50

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-to-sub-cntr flows-active-count)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr flows-active-count)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters flows-active-count

configure log accounting-policy custom-record aa-specific from-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-to-sub-cntr flows-denied-count)

[Tree] (config>log>acct-policy>cr>aa>aa-from-sub-cntr flows-denied-count)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters flows-denied-count

configure log accounting-policy custom-record aa-specific from-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>ies>if>spoke-sdp>ingress flowspec)

[Tree] (config>service>vprn>if>sap>ingress flowspec)

[Tree] (config>service>ies>if>sap>ingress flowspec)

[Tree] (config>service>vprn>if>spoke-sdp>ingress flowspec)

Full Context

configure service ies interface spoke-sdp ingress flowspec

configure service vprn interface sap ingress flowspec

configure service ies interface sap ingress flowspec

configure service vprn interface spoke-sdp 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