a Commands – Part III
app-profile-map
app-profile-map
Syntax
app-profile-map
Context
[Tree] (config>subscr-mgmt>sub-ident-pol app-profile-map)
Full Context
configure subscriber-mgmt sub-ident-policy app-profile-map
Description
Commands in this context configure an application profile mapping.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
app-profile-string
app-profile-string
Syntax
app-profile-string app-profile-string
no app-profile-string
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ident-strings app-profile-string)
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ident-strings app-profile-string)
Full Context
configure subscriber-mgmt local-user-db ppp host identification-strings app-profile-string
configure subscriber-mgmt local-user-db ipoe host identification-strings app-profile-string
Description
This command specifies the application profile string which is encoded in the identification strings.
The no form of this command returns to the default.
Parameters
- app-profile-string
-
Specifies the application profile string, up to 16 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
app-qos-policy
app-qos-policy
Syntax
app-qos-policy
Context
[Tree] (config>app-assure>group>policy app-qos-policy)
Full Context
configure application-assurance group policy app-qos-policy
Description
Commands in this context configure an application QoS policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
app-route-notifications
app-route-notifications
Syntax
app-route-notifications
Context
[Tree] (config>log app-route-notifications)
Full Context
configure log app-route-notifications
Description
Specific system applications in SR OS can take action based on a route to certain IP destinations being available. This CLI branch contains configuration related to these route availability notifications. A delay can be configured between the time that a route is determined as available in the CPM, and the time that the application is notified of the available route. For example, this delay may be used to increase the chances that other system modules (such as IOMs/XCMs/MDAs/XMAs) are fully programmed with the new route before the application takes action. Currently, the only application that acts upon these route available or route changed notifications with their configurable delays is the SNMP replay feature, which receives notifications of route availability to the SNMP trap receiver destination IP address.
Platforms
All
app-service-options
app-service-options
Syntax
app-service-options
Context
[Tree] (config>app-assure>group>policy app-service-options)
Full Context
configure application-assurance group policy app-service-options
Description
Commands in this context configure application service option characteristics.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
app-service-options
Syntax
[no] app-service-options
Context
[Tree] (config>log>acct-policy>cr>aa>aa-sub-attributes app-service-options)
Full Context
configure log accounting-policy custom-record aa-specific aa-sub-attributes app-service-options
Description
This command enables the subscriber application service option attributes to be exported in the AA subscriber's custom record.
The no form of this command excludes the subscriber application service option attributes from the AA subscriber's custom record.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
applicant-sm
applicant-sm
Syntax
[no] applicant-sm
Context
[Tree] (debug>service>id>mrp applicant-sm)
Full Context
debug service id mrp applicant-sm
Description
This command enables debugging of the applicant state machine.
The no form of this command disables debugging of the applicant state machine.
Platforms
All
application
application
Syntax
application {gx | gy | nasreq}
no application
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy application)
Full Context
configure subscriber-mgmt diameter-application-policy application
Description
This command specifies the Diameter application for which this policy contains the configuration details, such as AVPs to include and their format.
Applications are mutually exclusive.
The no form of this command reverts to the default.
Parameters
- gx
-
Specifies that Gx is the supported application of this DIAMETER policy.
- gy
-
Specifies that Gy is the supported application of this DIAMETER policy.
- nasreq
-
Specifies that NASREQ is the supported application of this DIAMETER policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application
Context
[Tree] (debug>diam application)
Full Context
debug diameter application
Description
This command debugs application processing for the Diameter node. This level is session aware (the session state is maintained at this level). Connection level messages are not reported on this level.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application dscp-app-name dscp {dscp-value | dscp-name}
application dot1p-app-name dot1p dot1p-priority
no application {dscp-app-name | dot1p-app-name}
Context
[Tree] (config>router>sgt-qos application)
[Tree] (config>service>vprn>sgt-qos application)
Full Context
configure router sgt-qos application
configure service vprn sgt-qos application
Description
This command configures DSCP/dot1p remarking for self-generated application traffic. When an application is configured using this command, the specified DSCP name is used for all packets generated by this application within the router instance it is configured. The instances can be base router, vprn, or management.
Using the value configured in this command:
-
sets the DSCP bits in the IP packet
-
maps to the FC. This value will be signaled from the CPM to the egress forwarding complex.
-
based on this signaled FC, the egress forwarding complex QoS policy sets the Ethernet 802.1p and MPLS EXP bits. This includes ARP, PPPoE, and IS-IS packets that do not carry DSCP bits.
-
configure the DSCP value in the egress IP header. The egress QoS policy does not overwrite this value.
Only one DSCP name can be configured per application, if multiple entries are configured, the subsequent entry overrides the previous configured entry.
The no form of this command reverts back to the default value.
Parameters
- dscp-app-name
-
Specifies the DSCP application name.
- dscp-value
-
Specifies a value when this packet egresses; the respective egress policy should provide the mapping for the DSCP value to either LSP-EXP bits or IEEE 802.1p (dot1p) bits as appropriate. Otherwise, the default mapping applies.
- dscp-name
-
Specifies the DSCP name.
- dot1p-priority
-
Specifies the dot1p priority.
- dot1p-app-name
-
Specifies the dot1p application name.
Platforms
All
application
Syntax
application app [ip-int-name | ip-address]
no application app
Context
[Tree] (config>service>vprn>source-address application)
Full Context
configure service vprn source-address application
Description
This command specifies the source address and application name.
The no form of this command removes the interface name or IP address from the command.
Parameters
- app
-
Specifies the application name.
- ip-int-name
-
Specifies the name of the IP interface, up to 32 characters. If the string contains special characters (#, ?, space), the entire string must be enclosed between double quotes.
- ip-address
-
Specifies the source IP address.
Platforms
All
application
Syntax
application {eq | neq} application-id
no application
Context
[Tree] (config>service>vprn>log>filter>entry>match application)
Full Context
configure service vprn log filter entry match application
Description
This command adds an OS application as an event filter match criterion.
An OS application is the software entity that reports the event. Applications include IP, MPLS, OSPF, CLI, SERVICES and so on Only one application can be specified. The latest application command overwrites the previous command.
The no form of this command removes the application as a match criterion.
Default
no application — no application match criterion is specified
Parameters
- eq | neq
-
The operator specifying the type of match.
- application-id
-
The application name string.
Platforms
All
application
Syntax
application application-name [rate]
no application application-name
Context
[Tree] (config>app-assure>group>cflowd>tcp-perf application)
[Tree] (config>app-assure>group>cflowd>comp application)
Full Context
configure application-assurance group cflowd tcp-performance application
configure application-assurance group cflowd comprehensive application
Description
This command configures applications to export performance records with cflowd.
The no form of this command removes the parameters from the configuration.
Parameters
- application-name
-
Specifies the name defined for the application.
- rate
-
Specifies which sampling flow rate to use; flow-rate or flow-rate2.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application application-name [create]
no application application-name
Context
[Tree] (config>app-assure>group>policy application)
Full Context
configure application-assurance group policy application
Description
This command creates an application of an application assurance policy.
The no form of this command deletes the application. To delete an application, all associations to the application must be removed.
Parameters
- application-name
-
Specifies a string of up to 32 characters uniquely identifying this application in the system.
- create
-
Mandatory keyword used when creating an application. The create keyword requirement can be enabled/disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application application-name
Context
[Tree] (config>app-assure>group>policy>app-filter>entry application)
Full Context
configure application-assurance group policy app-filter entry application
Description
This command assigns this application filter entry to an existing application. Assigning the entry to Unknown application restores the default configuration.
Parameters
- application-name
-
Specifies an existing application name.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application {eq | neq} application-name
no application
Context
[Tree] (config>app-assure>group>policy>charging-filter>entry>match application)
[Tree] (config>app-assure>group>policy>aqp>entry>match application)
Full Context
configure application-assurance group policy charging-filter entry match application
configure application-assurance group policy app-qos-policy entry match application
Description
This command adds an application to match criteria used by this entry.
The no form of this command removes the application from match criteria for this entry.
Default
no application
Parameters
- eq
-
Specifies that the value configured and the value in the flow must be equal.
- neq
-
Specifies that the value configured and the value in the flow must differ.
- application-name
-
Specifies the name of name existing application name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application application-name export-using export-method [export-method...(up to 2 max)]
application application-name no-export
no application application-name
Context
[Tree] (config>app-assure>group>statistics>aa-sub application)
Full Context
configure application-assurance group statistics aa-sub application
Description
This command configures aa-sub accounting statistics for export of applications of a given AA ISA group/partition.
The no form of this command removes the application name.
Parameters
- application-name
-
Specifies an existing application name, up to 32 characters.
- export-method
-
Specifies the method of statistics export to be used.
- no-export
-
Allows the operator to enable the referred application group to be selected (via Diameter) for Gx-usage monitoring. Gx usage monitoring is enabled automatically (and this command is not shown) if the export-using parameter is selected for the respective application group.
Usage monitoring must be enabled at the group:partition level (config>app-assure>group>statistics>aa-sub>usage-monitoring) as well in order to allow any application/application group/charging group usage monitoring.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application {eq | neq} application-name
no application
Context
[Tree] (debug>app-assure>group>traffic-capture>match application)
Full Context
debug application-assurance group traffic-capture match application
Description
This command configures debugging on an application.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
[no] application application-name
Context
[Tree] (debug>app-assure>group>port-recorder application)
Full Context
debug application-assurance group port-recorder application
Description
This commands specifies the applications used as input by the port-recorder. Applications responsible for unknown or unidentified traffic are meant to be used by this tool.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
Output
The following output is an example of configuration records TCP and UDP port numbers for the application "Unidentified TCP”.
Output Example7750# show debug
debug
application-assurance
group 1:1
port-recorder
application "Unidentified TCP"
rate 100
no shutdown
exit
exit
exit
exit
application
Syntax
application {eq | neq} application-id
no application
Context
[Tree] (config>log>filter>entry>match application)
Full Context
configure log filter entry match application
Description
This command adds an OS application as an event filter match criterion.
An OS application is the software entity that reports the event. Applications include IP, MPLS, OSPF, CLI, SERVICES and so on. Only one application can be specified. The latest application command overwrites the previous command.
The no form of this command removes the application as a match criterion.
Parameters
- eq | neq
-
Specifies the operator match type. Valid operators are listed in Valid Operators.
Table 1. Valid Operators Operator
Notes
eq
equal to
neq
not equal to
- application-id
-
The application name string.
Platforms
All
application
Syntax
application app [ip-int-name | ip-address]
no application app
Context
[Tree] (config>system>security>source-address application)
Full Context
configure system security source-address application
Description
This command configures the source IP address specified by the source-address command.
The no form of this command removes the interface name or IP address from the command.
Parameters
- app
-
Specifies the application name.
- ip-int-name
-
Specifies the name of the IP interface, up to 32 characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
- ip-address
-
Specifies the source IP address.
Platforms
All
application
Syntax
application application [keychain keychain-name]
no application application
Context
[Tree] (config>redundancy>multi-chassis>peer>sync>transport-encryption application)
Full Context
configure redundancy multi-chassis peer sync transport-encryption application
Description
This command configures transport encryption.
The no form of this command removes the specified application.
Parameters
- application
-
Specifies a Multi-Chassis Synchronization (MCS) client application
- keychain-name
-
Specifies a keychain name, up to 32 characters
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application
Syntax
application {eq | neq} app-group-name
no application
Context
[Tree] (config>app-assure>group>policy>chrg-fltr>entry>match application)
Full Context
configure application-assurance group policy charging-filter entry match application
Description
This command configures the addition of an application to the match criteria used by this charging filter entry.
The no form of this command removes the application match criteria.
Default
no application
Parameters
- eq
-
Specifies that the value configured and the value in the flow must be equal.
- neq
-
Specifies that the value configured and the value in the flow must differ.
- app-group-name
-
Specifies the name of the application group, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-assurance
application-assurance
Syntax
application-assurance
Context
[Tree] (admin application-assurance)
Full Context
admin application-assurance
Description
Commands in this context perform Application Assurance (AA) configuration operations.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-assurance
Syntax
application-assurance
Context
[Tree] (config application-assurance)
Full Context
configure application-assurance
Description
Commands in this context perform Application Assurance (AA) configuration operations.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-assurance
Syntax
application-assurance
Context
[Tree] (config>system>persistence application-assurance)
Full Context
configure system persistence application-assurance
Description
Commands in this context configure application assurance persistence parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-assurance
Syntax
application-assurance app-profile-name
Context
[Tree] (config>subscr-mgmt>http-rdr-plcy application-assurance)
Full Context
configure subscriber-mgmt http-redirect-policy application-assurance
Description
This command specifies the AA application profile used for HTTP redirect portal authentication. This forwards all UDP/TCP traffic to AA for packet filtering. Any forwarding entries under the HTTP redirect policy are not taken into account because only UDP/TCP can be configured. Outbound ICMP and ICMPv6 traffic is always dropped.
Parameters
- app-profile-name
-
Specifies an AA application profile name, up to 32 characters, that is configured in the config>app-assur>group>policy>app-prof context.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-assurance-group
application-assurance-group
Syntax
application-assurance-group application-assurance-group-index [create] [aa-sub-scale sub-scale]
no application-assurance-group application-assurance-group-index
Context
[Tree] (config>isa application-assurance-group)
Full Context
configure isa application-assurance-group
Description
Commands in this context create an application assurance group with the specified system-unique index and configure that group’s parameters.
The no form of this command deletes the specified application assurance group from the system. The group must be shutdown first.
Parameters
- application-assurance-group-index
-
Specifies an integer to identify the AA group
- create
-
Mandatory keyword used when creating an application assurance group in the ISA context. The create keyword requirement can be enabled or disabled in the environment>create context.
- sub-scale
-
Specifies the set of scaling limits that are supported with regards to the maximum number of AA subscribers per ISA, the max flow scale, and the corresponding policy scale that can be specified.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application-link-attributes
application-link-attributes
Syntax
[no] application-link-attributes
Context
[Tree] (config>router>isis>traffic-engineering-options application-link-attributes)
Full Context
configure router isis traffic-engineering-options application-link-attributes
Description
Commands in this context configure the advertisement of the TE attributes of each link on a per-application basis. Two applications are supported in SR OS: RSVP-TE and SR-TE.
The legacy mode of advertising TE attributes that is used in RSVP-TE is still supported but it can be disabled by using the no legacy command, which also enables per-application TE attribute advertisement for RSVP-TE.
The no form of this command deletes the context.
Default
no application-link-attributes
Platforms
All
application-policy
application-policy
Syntax
[no] application-policy name
Context
[Tree] (config>app-assure>group>transit-ip>diameter application-policy)
Full Context
configure application-assurance group transit-ip-policy diameter application-policy
Description
This command specifies the Diameter application to be used by seen IP transit subs. The application policy is defined using the config>subscr-mgmt>diameter-application-policy command.
The no form of this command removes the policy.
Default
no application-policy
Parameters
- name
-
Specifies the name of the application policy configured using the diameter-application-policy command up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
application6
application6
Syntax
application6 app ipv6-address
no application6 app
Context
[Tree] (config>service>vprn>source-address application6)
Full Context
configure service vprn source-address application6
Description
This command specifies the IPv6 source address and application.
The no form of this command removes the application and IPv6 address from the configuration.
Parameters
- app
-
Specifies the application name.
- ipv6-address
-
Specifies the IPv6 address.
Platforms
All
application6
Syntax
application6 app ipv6-address
no application6
Context
[Tree] (config>system>security>source-address application6)
Full Context
configure system security source-address application6
Description
This command configures the application to use the source IPv6 address specified by the source-address command.
The no form of this command removes the application and IPv6 address from the configuration.
Parameters
- app
-
Specifies the application name.
- ipv6-address
-
Specifies the IPv6 address.
Platforms
All
applications
applications
Syntax
applications all
applications [connectivity-management] [gx] [gy] [nasreq] [radius-auth] [radius-acct] [python] [ludb] [msap] [pfcp] [ppp-event]
no applications
Context
[Tree] (config>call-trace>trace-profile applications)
Full Context
configure call-trace trace-profile applications
Description
This command enables tracing of messages and events for the specified applications.
Default
applications all
Parameters
- all
-
Enables tracing of all packets and events, with the exception of PPP events.
- connectivity-management
-
Enables tracing for connectivity protocols, such as DHCP, ARP, and DHCPv6, and events related to connectivity management; for example, migrant or data-triggered host creation, idling, or session timeout. In the CUPS context, this command traces uplink IBCP messages.
- gx
-
Enables tracing of Diameter Gx messages.
- gy
-
Enables tracing of Diameter Gy messages.
- nasreq
-
Enables tracing of Diameter NASREQ messages.
- radius-auth
-
Enables tracing of messages and events related to RADIUS authentication, including CoA and Disconnect.
- radius-acct
-
Enables tracing of messages and events related to RADIUS-based accounting.
- python
-
Enables tracing of python script execution.
- ludb
-
Enables tracing of local user database lookups.
- msap
-
Enables tracing of MSAP creation events.
- pfcp
-
Enables tracing of PFCP messages.
- ppp-event
-
Enables tracing of all events related to the PPP state machine. This can result in a large amount of event messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
apply-bgp-nh-override
apply-bgp-nh-override
Syntax
[no] apply-bgp-nh-override
Context
[Tree] (config>service>vprn>pim apply-bgp-nh-override)
Full Context
configure service vprn pim apply-bgp-nh-override
Description
This command forces the RPF check to be performed via IPv4 VPN AF next-hop and not via IPv4 VPN AF VRF import extended community.
Default
no apply-bgp-nh-override
Platforms
All
apply-function-specific-behavior
apply-function-specific-behavior
Syntax
[no] apply-function-specific-behavior
Context
[Tree] (config>app-assure>group>url-filter apply-function-specific-behavior)
Full Context
configure application-assurance group url-filter apply-function-specific-behavior
Description
If this command is enabled, the default-action, default-http-redirect, and http-redirect commands at the url-filter function level (ICAP, local filtering and web service) will apply.
The no form of this command indicates that the configuration at the url-filter level will apply to all of the configured url-filter functions.
Default
no apply-function-specific-behavior
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
apply-path
apply-path
Syntax
[no] apply-path
Context
[Tree] (config>filter>match-list>ip-prefix-list apply-path)
[Tree] (config>filter>match-list>ipv6-prefix-list apply-path)
Full Context
configure filter match-list ip-prefix-list apply-path
configure filter match-list ipv6-prefix-list apply-path
Description
Commands in this context configure the auto-generation of address prefixes for IPv4 or IPv6 address prefix match lists. The context in which the command is executed governs whether IPv4 or IPv6 prefixes will be auto-generated.
The no form of this command removes all auto-generation configuration under the apply-path context.
Default
no apply path
Platforms
All
apply-to
apply-to
Syntax
apply-to {all | none}
Context
[Tree] (config>service>vprn>pim apply-to)
Full Context
configure service vprn pim apply-to
Description
This command creates a PIM interface with default parameters.
If a manually created interface or modified interface is deleted, the interface will be recreated when the apply-to command is executed. If PIM is not required on a specific interface, then execute a shutdown command.
The apply-to command is saved first in the PIM configuration structure, all subsequent commands either create new structures or modify the defaults as created by the apply-to command.
Default
apply-to none
Parameters
- all
-
Specifies that all VPRN and non-VPRN interfaces are automatically applied in PIM.
- none
-
No interfaces are automatically applied in PIM. PIM interfaces must be manually configured.
Platforms
All
apply-to
Syntax
apply-to {ies | non-ies | all | none}
Context
[Tree] (config>router>pim apply-to)
Full Context
configure router pim apply-to
Description
This command creates a PIM interface with default parameters.
If a manually created or a modified interface is deleted, the interface is recreated when (re)processing the apply-to command and if PIM is not required on a specific interface a shutdown should be executed.
The apply-to command is first saved in the PIM configuration structure. Then, all subsequent commands either create new structures or modify the defaults as created by the apply-to command.
Default
apply-to none
Parameters
- ies
-
Specifies to apply all IES interfaces in PIM.
- non-ies
-
Specifies to apply non-IES interfaces created in PIM.
- all
-
Specifies to apply all IES and non-IES interfaces created in PIM.
- none
-
Removes all interfaces that are not manually created or modified. It also removes explicit no interface commands if present.
Platforms
All
aps
aps
Syntax
aps
Context
[Tree] (config>port aps)
Full Context
configure port aps
Description
This command configures APS (Automatic Protection Switching). APS is used by SONET/SDH add/drop multiplexers (ADMs) or other SONET/SDH-capable equipment to protect against circuit or equipment failure.
An APS group contains a working and a protect circuit and can span a single node (SC-APS) or two nodes (MC-APS).
The working and protection configurations on the 7750 SRs must match the circuit configurations on the peer. This means that the working circuit on the 7750 SR must be connected to the peer’s working circuit and the protect circuit must be connected to the peer’s protection circuit.
The aps command is only available for APS groups and not physical ports.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
aqp-initial-lookup
aqp-initial-lookup
Syntax
aqp-initial-lookup
no aqp-initial-lookup
Context
[Tree] (config>app-assure>group aqp-initial-lookup)
Full Context
configure application-assurance group aqp-initial-lookup
Description
This command allows AA to perform AQP lookups on flows prior to complete application identification. As usual, AQP will be looked up again on identification complete. Without this, AA executes AQPs that are part of what so called "sub-default policy”. Sub-default policy is formed by regular AQPs that contain ASOs, subID and/or flow direction as matching conditions.
This behavior is required, for example, in order to be able apply GTP and SCTP filtering on the first packet of a new GTP/SCTP flow (AQP matching conditions in this case contains protocol id).
The no form of this command forces complete AQP look up on identification finish stage only.
Default
no aqp-initial-lookup
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
arbiter
arbiter
Syntax
arbiter arbiter-name [create]
no arbiter arbiter-name
Context
[Tree] (config>qos>plcr-ctrl-plcy>tier arbiter)
Full Context
configure qos policer-control-policy tier arbiter
Description
This command is used to create an arbiter within the context of tier 1 or tier 2. An arbiter is a child policer bandwidth control object that manages the throughput of a set of child policers. An arbiter allows child policers or other arbiters to parent to one of eight strict levels. Each arbiter is itself parented to either another tiered arbiter or to the root arbiter.
The root arbiter starts with its defined maximum rate and distributes the bandwidth to its directly attached child policers and arbiters beginning with priority 8. As the children at each priority level are distributed bandwidth according to their needs and limits, the root proceeds to the next lower priority until either all children’s needs are met or it runs out of bandwidth. The bandwidth given to a tiered arbiter is then divided between that arbiter’s children (child policers or a tier 2 arbiter) in the same fashion. A tiered arbiter may also have a rate limit defined that limits the amount of bandwidth it may receive from its parent.
An arbiter that is currently parented by another arbiter cannot be deleted.
Each time the policer-control-policy is applied to either a SAP, or a subscriber (through association with a sub-profile that has the policy applied), or a multiservice site, an instance of the parent policer and the arbiters is created.
Any child policer that uses the arbiter’s name in its parenting command will be associated with the arbiter instance. The child policer will also become associated with any arbiter to which its parent arbiter is parented (grandparent). Having child policers parented to an arbiter does not prevent that arbiter from being removed from the policer-control-policy. When removed, the child policers become orphaned.
You can create up to 31 tiered arbiters within the policer-control-policy on either tier 1 or tier 2 (in addition to the arbiter).
The no form of this command is used to remove an arbiter from tier 1 or tier 2. If the specified arbiter does not exist, the command returns without an error. If the specified arbiter is currently specified as the parent for another arbiter, the command will fail. When an arbiter is removed from a policer-control-policy, all instances of the arbiter will also be removed. Any child policers currently parented to the arbiter instance will become orphans and will not be bandwidth managed by the policer control policy instances parent policer.
Parameters
- arbiter-name
-
Any unique name within the policy. Up to 31 arbiters may be created.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
area
area
Syntax
[no] area area-id
Context
[Tree] (config>service>vprn>ospf3 area)
[Tree] (config>service>vprn>ospf area)
Full Context
configure service vprn ospf3 area
configure service vprn ospf area
Description
This command creates the context to configure an OSPF area. An area is a collection of network segments within an AS that have been administratively grouped together. The area ID can be specified in dotted decimal notation or as a 32-bit decimal integer.
The no form of this command deletes the specified area from the configuration. Deleting the area also removes the OSPF configuration of all the interfaces, virtual-links, sham-links, address-ranges and so on, that are currently assigned to this area.
Default
no area — No OSPF areas are defined.
Parameters
- area-id
-
The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Platforms
All
area
Syntax
[no] area area-id
Context
[Tree] (config>router>ospf area)
[Tree] (config>router>ospf3 area)
Full Context
configure router ospf area
configure router ospf3 area
Description
This command creates the context to configure an OSPF or OSPF3 area. An area is a collection of network segments within an AS that have been administratively grouped together. The area ID can be specified in dotted decimal notation or as a 32-bit decimal integer.
The no form of this command deletes the specified area from the configuration. Deleting the area also removes the OSPF configuration of all the interfaces, virtual-links, and address-ranges and so on, that are currently assigned to this area.
Default
no area
Parameters
- area-id
-
The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Platforms
All
area
Syntax
area [area-id]
no area
Context
[Tree] (debug>router>ospf area)
[Tree] (debug>router>ospf3 area)
Full Context
debug router ospf area
debug router ospf3 area
Description
This command enables debugging for an OSPF area.
Parameters
- area-id
-
Specifies the OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Platforms
All
area
Syntax
area area-id
no area
Context
[Tree] (config>router>policy-options>policy-statement>entry>from area)
Full Context
configure router policy-options policy-statement entry from area
Description
This command configures an OSPF area as a route policy match criterion.
This match criterion is only used in export policies.
All OSPF routes (internal and external) are matched using this criterion if the best path for the route is by the specified area.
The no form of this command removes the OSPF area match criterion.
Default
no area
Parameters
- area-id
-
Specifies the OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Platforms
All
area-id
area-id
Syntax
[no] area-id area-address
Context
[Tree] (config>service>vprn>isis area-id)
Full Context
configure service vprn isis area-id
Description
This command configures the area ID portion of NSAP addresses for the VPRN instance. This identifies a point of connection to the network, such as a router interface, and is called a Network Service Access Point (NSAP). Addresses in the IS-IS protocol are based on the ISO NSAP addresses and Network Entity Titles (NETs), not IP addresses.
A maximum of 3 area addresses can be configured for the VPRN instance.
NSAP addresses are divided into three parts.
-
Area ID — A variable length field between 1 and 13 bytes long. This includes the Authority and Format Identifier (AFI) as the most significant byte and the area ID.
-
System ID — A six-byte system identification. When not configured, the system ID is derived from the configurations for configure router isis router-id, configure router router-id, or system address ipv4 address. If the previous commands are not configured, the system ID defaults to the last four octets of the chassis MAC address.
-
Selector ID — A one-byte selector identification that must contain zeros when configuring a NET. This value is not configurable. The selector ID is always 00.
The NET is constructed like an NSAP but the selector byte contains a 00 value. NET addresses are exchanged in hello and LSP PDUs. All net addresses configured on the node are advertised to its neighbors.
For Level 1 interfaces, neighbors can have different area IDs, but, they must have at least one area ID (AFI + area) in common. Sharing a common area ID, they become neighbors and area merging between the potentially different areas can occur.
For Level 2 (only) interfaces, neighbors can have different area IDs. However, if they have no area IDs in common, they become only Level 2 neighbors and Level 2 LSPs are exchanged.
For Level 1 and Level 2 interfaces, neighbors can have different area IDs. If they have at least one area ID (AFI + area) in common, they become neighbors. In addition to exchanging Level 2 LSPs, area merging between potentially different areas can occur.
If multiple area-id commands are entered, the system ID of all subsequent entries must match the first area address.
The no form of this command removes the area address.
Platforms
All
area-id
Syntax
[no] area-id area-address
Context
[Tree] (config>router>isis area-id)
Full Context
configure router isis area-id
Description
This command was previously named the net network-entity-title command. The area-id command allows you to configure the area ID portion of NSAP addresses which identifies a point of connection to the network, such as a router interface, and is called a Network Service Access Point (NSAP). Addresses in the IS-IS protocol are based on the ISO NSAP addresses and Network Entity Titles (NETs), not IP addresses.
A maximum of three area addresses can be configured.
NSAP addresses are divided into three parts.
-
Area ID — A variable length field between 1 and 13 bytes long. This includes the Authority and Format Identifier (AFI) as the most significant byte and the area ID.
-
System ID — A six-byte system identification. When not configured, the system ID is derived from the configurations for configure router isis router-id, configure router router-id, or system address ipv4 address. If the previous commands are not configured, the system ID defaults to the last four octets of the chassis MAC address.
-
Selector ID — A one-byte selector identification that must contain zeros when configuring a NET. This value is not configurable. The selector ID is always 00.
The NET is constructed like an NSAP but the selector byte contains a 00 value. NET addresses are exchanged in hello and LSP PDUs. All net addresses configured on the node are advertised to its neighbors.
For Level 1 interfaces, neighbors can have different area IDs, but, they must have at least one area ID (AFI + area) in common. Sharing a common area ID, they become neighbors and area merging between the potentially different areas can occur.
For Level 2 (only) interfaces, neighbors can have different area IDs. However, if they have no area IDs in common, they become only Level 2 neighbors and Level 2 LSPs are exchanged.
For Level 1 and Level 2 interfaces, neighbors can have different area IDs. If they have at least one area ID (AFI + area) in common, they become neighbors. In addition to exchanging Level 2 LSPs, area merging between potentially different areas can occur.
If multiple area-id commands are entered, the system ID of all subsequent entries must match the first area address.
The no form of this command removes the area address.
Parameters
- area-address
-
Specifies a 1 — 13-byte address. Of the total 20 bytes comprising the NET, only the first 13 bytes can be manually configured. As few as one byte can be entered or, at most, 13 bytes. If less than 13 bytes are entered, the rest is padded with zeros.
Platforms
All
area-range
area-range
Syntax
area-range ip-prefix/prefix-length [advertise | not-advertise]
no area-range ip-prefix/mask
area-range ipv6-prefix/prefix-length [advertise | not-advertise]
no area-range ipv6-prefix/prefix-length
Context
[Tree] (config>service>vprn>ospf>area>nssa area-range)
[Tree] (config>service>vprn>ospf>area area-range)
[Tree] (config>service>vprn>ospf3>area area-range)
[Tree] (config>service>vprn>ospf3>area>nssa area-range)
Full Context
configure service vprn ospf area nssa area-range
configure service vprn ospf area area-range
configure service vprn ospf3 area area-range
configure service vprn ospf3 area nssa area-range
Description
This command creates ranges of addresses on an Area Border Router (ABR) for the purpose of route summarization or suppression. When a range is created, it is configured to be advertised or not advertised into other areas. Multiple range commands are used to summarize or hide different ranges. In the case of overlapping ranges, the most specific range command applies.
ABRs send summary link advertisements to describe routes to other areas. To minimize the number of advertisements that are flooded, you can summarize a range of IP addresses and send reachability information about these addresses in an LSA.
The no form of this command deletes the range (non) advertisement.
Default
no area-range
Parameters
- ipv6-prefix/prefix-length
-
The IP prefix in dotted decimal notation for the range used by the ABR to advertise that summarizes the area into another area.
- mask
-
The subnet mask for the range expressed as a decimal integer mask length or in dotted decimal notation.
- advertise | not-advertise
-
Specifies whether or not to advertise the summarized range of addresses into other areas. The advertise keyword indicates the range will be advertised, and the keyword not-advertise indicates the range will not be advertised.
The default is advertise.
Platforms
All
area-range
Syntax
area-range ip-prefix/mask [ advertise | not-advertise]
no area-range ip-prefix/mask
Context
[Tree] (config>router>ospf>area area-range)
[Tree] (config>router>ospf>area>nssa area-range)
Full Context
configure router ospf area area-range
configure router ospf area nssa area-range
Description
This command creates ranges of addresses on an Area Border Router (ABR) for the purpose of route summarization or suppression. When a range is created, the range is configured to be advertised or not advertised into other areas. Multiple range commands may be used to summarize or hide different ranges. In the case of overlapping ranges, the most specific range command applies.
ABRs send summary link advertisements to describe routes to other areas. To minimize the number of advertisements that are flooded, you can summarize a range of IP addresses and send reachability information about these addresses in an LSA.
The no form of this command deletes the range (non) advertisement.
Default
no area-range
Parameters
- ip-prefix
-
Specifies the IP prefix in dotted decimal notation for the range used by the ABR to advertise that summarizes the area into another area.
- mask
-
Specifies the subnet mask for the range expressed as a decimal integer mask length or in dotted decimal notation.
- advertise | not-advertise
-
Specifies whether to advertise the summarized range of addresses into other areas. The advertise keyword indicates the range will be advertised, and the keyword not-advertise indicates the range will not be advertised.
Platforms
All
area-range
Syntax
area-range ipv4-prefix/mask | ipv6-prefix/prefix-length [advertise | not-advertise]
no area-range ipv4-prefix/mask | ipv6-prefix/prefix-length
Context
[Tree] (config>router>ospf3>area>nssa area-range)
[Tree] (config>router>ospf3>area area-range)
Full Context
configure router ospf3 area nssa area-range
configure router ospf3 area area-range
Description
This command creates ranges of addresses on an Area Border Router (ABR) for the purpose of route summarization or suppression. When a range is created, the range is configured to be advertised or not advertised into other areas. Multiple range commands may be used to summarize or hide different ranges. In the case of overlapping ranges, the most specific range command applies.
ABRs send summary link advertisements to describe routes to other areas. To minimize the number of advertisements that are flooded, you can summarize a range of IP addresses and send reachability information about these addresses in an LSA.
The no form of this command deletes the range (non) advertisement.
Default
no area-range
Parameters
- ip-prefix/prefix-length
-
Specifies the IP prefix in dotted decimal notation for the range used by the ABR to advertise that summarizes the area into another area.
- advertise | not-advertise
-
Specifies whether or not to advertise the summarized range of addresses into other areas. The advertise keyword indicates the range will be advertised, and the keyword not-advertise indicates the range will not be advertised.
Platforms
All
area-range
Syntax
area-range [ip-address]
no area-range
Context
[Tree] (debug>router>ospf3 area-range)
[Tree] (debug>router>ospf area-range)
Full Context
debug router ospf3 area-range
debug router ospf area-range
Description
This command enables debugging for an OSPF area range.
Parameters
- ip-address
-
Specifies the IPv4 or IPv6 address for the range used by the ABR to advertise the area into another area.
Platforms
All
argument-length
argument-length
Syntax
argument-length length
Context
[Tree] (config>router>segment-routing>srv6>locator argument-length)
[Tree] (conf>router>sr>srv6>micro-segment argument-length)
Full Context
configure router segment-routing segment-routing-v6 locator argument-length
configure router segment-routing segment-routing-v6 micro-segment argument-length
Description
This command configures the argument length for an SRv6 or micro-segment locator.
The sum of the function length, argument length, and the locator prefix length must not exceed 128 bits. This is enforced in CLI validation.
The following commands are used to configure the function length and locator prefix length:
- configure router segment-routing segment-routing-v6 locator function-length
- configure router segment-routing segment-routing-v6 locator prefix ip-prefix
Default
argument-length 0
Parameters
- length
-
Specifies the argument length.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
arp
arp
Syntax
arp arp-value
no arp
Context
[Tree] (config>subscr-mgmt>gtp>peer-profile>mme>qos arp)
[Tree] (config>subscr-mgmt>gtp>peer-profile>ggsn>qos arp)
[Tree] (config>subscr-mgmt>gtp>peer-profile>pgw>qos arp)
Full Context
configure subscriber-mgmt gtp peer-profile mme qos arp
configure subscriber-mgmt gtp peer-profile ggsn qos arp
configure subscriber-mgmt gtp peer-profile pgw qos arp
Description
The command configures the allocation and retention priority to be used in the GTP messages as QoS IE (for a Gn interface) or Bearer QoS (for GTPv2).
The no form of this command reverts to the default.
Default
arp 1
Parameters
- arp-value
-
Specifies the Allocation/Retention Priority (ARP).
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
arp
Syntax
arp
Context
[Tree] (config>service>vprn>if>vpls>evpn arp)
[Tree] (config>service>ies>if>vpls>evpn arp)
Full Context
configure service vprn interface vpls evpn arp
configure service ies interface vpls evpn arp
Description
Commands in this context configure ARP host route parameters.
Platforms
All
arp
Syntax
arp
Context
[Tree] (debug>router>ip arp)
Full Context
debug router ip arp
Description
This command configures route table debugging.
Platforms
All
arp-host
arp-host
Syntax
arp-host
Context
[Tree] (config>service>ies>sub-if>grp-if arp-host)
[Tree] (config>service>vprn>sub-if>grp-if arp-host)
[Tree] (config>subscr-mgmt>msap-policy>vpls-only arp-host)
[Tree] (config>service>vpls>sap arp-host)
Full Context
configure service ies subscriber-interface group-interface arp-host
configure service vprn subscriber-interface group-interface arp-host
configure subscriber-mgmt msap-policy vpls-only-sap-parameters arp-host
configure service vpls sap arp-host
Description
Commands in this context configure ARP host parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
arp-host
Syntax
[no] arp-host
Context
[Tree] (debug>service>id arp-host)
Full Context
debug service id arp-host
Description
This command enables and configures ARP host debugging.
The no form of this command disables ARP host debugging.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
arp-host-route
arp-host-route
Syntax
arp-host-route
Context
[Tree] (config>service>vprn>if arp-host-route)
[Tree] (config>service>ies>if arp-host-route)
Full Context
configure service vprn interface arp-host-route
configure service ies interface arp-host-route
Description
Commands in this context configure ARP host routes to populate.
Platforms
All
arp-learn-unsolicited
arp-learn-unsolicited
Syntax
[no] arp-learn-unsolicited
Context
[Tree] (config>router>if arp-learn-unsolicited)
[Tree] (config>service>ies>if arp-learn-unsolicited)
[Tree] (config>service>vprn>if arp-learn-unsolicited)
Full Context
configure router interface arp-learn-unsolicited
configure service ies interface arp-learn-unsolicited
configure service vprn interface arp-learn-unsolicited
Description
This command allows the ARP application to learn new entries based on any received ARP message (GARP, ARP-Request, or ARP-Reply, such as any frame with ethertype 0x0806).
The no form of this command disables the above behavior and causes ARP entries to only be learned when needed, that is, when the router receives an ARP-reply after an ARP-request triggered by received traffic.
Platforms
All
arp-limit
arp-limit
Syntax
arp-limit limit [log-only] [threshold percent]
no arp-limit
Context
[Tree] (config>service>ies>interface arp-limit)
Full Context
configure service ies interface arp-limit
Description
This command configures the maximum amount of dynamic IPv4 ARP entries that can be learned on an IP interface.
When the number of dynamic ARP entries reaches the configured percentage of this limit, a log event is raised. When the limit is exceeded, no new entries are learned until an entry expires and traffic to these destinations will be dropped. Entries that have already been learned will be refreshed.
The no form of this command removes the arp-limit.
Default
no arp-limit
Parameters
- log-only
-
Enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, entries above the limit will be learned.
- percent
-
The threshold value (as a percentage) that triggers a warning message to be sent.
- limit
-
The number of entries that can be learned on an IP interface expressed as a decimal integer. If the limit is set to 0, dynamic ARP learning is disabled and no dynamic ARP entries are learned.
Platforms
All
arp-limit
Syntax
arp-limit limit [log-only] [threshold percent]
no arp-limit
Context
[Tree] (config>service>vprn>if arp-limit)
Full Context
configure service vprn interface arp-limit
Description
This command configures the maximum amount of dynamic IPv4 ARP entries that can be learned on an IP interface.
When the number of dynamic ARP entries reaches the configured percentage of this limit, an SNMP trap is sent. When the limit is exceeded, no new entries are learned until an entry expires and traffic to these destinations will be dropped. Entries that have already been learned will be refreshed.
The no form of this command removes the arp-limit.
Default
90 percent
Parameters
- log-only
-
Enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, entries above the limit will be learned.
- percent
-
The threshold value (as a percentage) that triggers a warning message to be sent.
- limit
-
The number of entries that can be learned on an IP interface expressed as a decimal integer. If the limit is set to 0, dynamic ARP learning is disabled and no dynamic ARP entries are learned.
Platforms
All
arp-limit
Syntax
arp-limit limit [log-only] [threshold percent]
no arp-limit
Context
[Tree] (config>router>if arp-limit)
Full Context
configure router interface arp-limit
Description
This command configures the maximum amount of dynamic IPv4 ARP entries that can be learned on an IP interface.
When the number of dynamic ARP entries reaches the configured percentage of this limit, an SNMP trap is sent. When the limit is exceeded, no new entries are learned until an entry expires and traffic to these destinations will be dropped. Entries that have already been learned will be refreshed.
The no form of this command removes the arp-limit.
Default
no arp-limit
Parameters
- limit
-
The number of entries that can be learned on an IP interface expressed as a decimal integer. If the limit is set to 0, dynamic ARP learning is disabled and no dynamic ARP entries are learned.
- log-only
-
Enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, entries above the limit will be learned.
- percent
-
The threshold value (as a percentage) that triggers a warning message to be sent.
Platforms
All
arp-nd-extended-community-advertisement
arp-nd-extended-community-advertisement
Syntax
[no] arp-nd-extended-community-advertisement
Context
[Tree] (config>service>vpls>bgp-evpn arp-nd-extended-community-advertisement)
Full Context
configure service vpls bgp-evpn arp-nd-extended-community-advertisement
Description
This command enables the advertisement of the RFC 9047 ARP/ND extended community along with the MAC/IP routes that are advertised for local static and dynamic proxy ARP or ND entries. This command also controls the processing of the ARP/ND extended community and the selection of ARP or ND entries based on the inmutable flag.
The no form of this command disables the advertisement of the RFC 9047 ARP/ND extended community.
Default
no arp-nd-extended-community-advertisement
Platforms
All
arp-nd-only-with-fdb-advertisement
arp-nd-only-with-fdb-advertisement
Syntax
[no] arp-nd-only-with-fdb-advertisement
Context
[Tree] (config>service>vpls>bgp-evpn arp-nd-only-with-fdb-advertisement)
Full Context
configure service vpls bgp-evpn arp-nd-only-with-fdb-advertisement
Description
This command enables the router to advertise local ARP/ND entries of VPRN interfaces using this VPLS BGP-EVPN service when the corresponding local MAC is programmed in the FDB.
The no form of this command disables the advertisement of the ARP/ND entries.
Default
no arp-nd-only-with-fdb-advertisement
Platforms
All
arp-populate
arp-populate
Syntax
[no] arp-populate
Context
[Tree] (config>service>vprn>sub-if>grp-if arp-populate)
[Tree] (config>service>vprn>if arp-populate)
[Tree] (config>service>ies>if arp-populate)
[Tree] (config>service>ies>sub-if>grp-if arp-populate)
Full Context
configure service vprn subscriber-interface group-interface arp-populate
configure service vprn interface arp-populate
configure service ies interface arp-populate
configure service ies subscriber-interface group-interface arp-populate
Description
This command, when enabled, disables dynamic learning of ARP entries. Instead, the ARP table is populated with static and dynamic entries from the DHCP Lease State Table (enabled with lease-populate), and optionally with static entries entered with the static-host command.
The host’s IP address and MAC address are placed in the system ARP cache as a managed entry. Static hosts must be defined on the interface using the static-host command. Dynamic hosts are enabled on the system through enabling lease-populate in the IP interface DHCP context.
In the event that both a static host and a dynamic host share the same IP and MAC address, the system’s ARP cache retains the host information until both the static and dynamic information are removed.
Both static and dynamic hosts override static ARP entries. Static ARP entries are marked as inactive when they conflict with static or dynamic hosts and will be repopulated once all static and dynamic host information for the IP address are removed. Since static ARP entries are not possible when static subscriber hosts are defined or when DHCP lease state table population is enabled, conflict between static ARP entries and the arp-populate function is not an issue.
Enabling the arp-populate command removes any dynamic ARP entries learned on this interface from the ARP cache.
The arp-populate command fails if an existing static ARP entry exists for this interface.
When arp-populate is enabled, the system does not send out ARP requests for hosts that are not in the ARP cache. Only statically configured and DHCP learned hosts are reachable through an IP interface with arp-populate enabled. The arp-populate command can only be enabled on IES and VPRN interfaces supporting Ethernet encapsulation.
The no form of this command disables ARP cache population functions for static and dynamic hosts on the interface. All static and dynamic host information for this interface is removed from the system’s ARP cache. Any existing static ARP entries previously inactive due to static or dynamic hosts will be populated in the system ARP cache.
Default
no arp-populate
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface arp-populate
- configure service vprn subscriber-interface group-interface arp-populate
All
- configure service ies interface arp-populate
- configure service vprn interface arp-populate
arp-populate-host-route
arp-populate-host-route
Syntax
[no] arp-populate-host-route
Context
[Tree] (config>service>ies>if arp-populate-host-route)
Full Context
configure service ies interface arp-populate-host-route
Description
This command enables the addition or deletion of host routes in the route table derived from ARP entries in the ARP cache. To enable this command, the interface must be shut down. The command triggers the population of host routes in the route table out of their corresponding static, dynamic, or EVPN types in the ARP table. ARP entries installed by subscriber management, local interfaces, and others, do not create host routes.
The no form of this command disables the creation of host routes from the ARP cache.
Platforms
All
arp-proactive-refresh
arp-proactive-refresh
Syntax
[no] arp-proactive-refresh
Context
[Tree] (config>service>ies>if arp-proactive-refresh)
Full Context
configure service ies interface arp-proactive-refresh
Description
This command enables the router to always send out a single refresh message with no entries 30 seconds prior to the timeout of the entry.
The no form of this command sets the default behavior, in which an entry is marked as stale 30 seconds prior to age-out, and the router only sends an ARP request to refresh the entry if the IOM receives traffic that uses it. If so, the IOM asks the ARP application to send a refresh message. With arp-proactive-refresh enabled, the ARP module sends a refresh message regardless of whether the IOM receives traffic.
Platforms
All
arp-proactive-refresh
Syntax
[no] arp-proactive-refresh
Context
[Tree] (config>service>vprn>if arp-proactive-refresh)
Full Context
configure service vprn interface arp-proactive-refresh
Description
This command enables the router to always send out a refresh message 30 seconds prior to the timeout of the entry (a single refresh message with no retries).
The no form of this command sets the default behavior, in which an entry is marked as stale 30 seconds prior to age-out, and the router only sends an ARP request to refresh the entry if the IOM receives traffic that uses it. If so, the IOM asks the ARP application to send a refresh message. With arp-proactive-refresh enabled, the ARP module sends a refresh message regardless of the IOM receiving traffic.
Platforms
All
arp-proactive-refresh
Syntax
[no] arp-proactive-refresh
Context
[Tree] (config>router>if arp-proactive-refresh)
Full Context
configure router interface arp-proactive-refresh
Description
This command enables the router to always send out a refresh message 30 seconds prior to the timeout of the entry (a single refresh message with no retries).
The no form of this command sets the default behavior, in which an entry is marked as stale 30 seconds prior to age-out, and the router only sends an ARP request to refresh the entry if the IOM receives traffic that uses it. If so, the IOM asks the ARP application to send a refresh message. With arp-proactive-refresh enabled, the ARP module sends a refresh message regardless of the IOM receiving traffic.
Platforms
All
arp-reply-agent
arp-reply-agent
Syntax
arp-reply-agent [sub-ident]
no arp-reply-agent
Context
[Tree] (config>service>vpls>sap arp-reply-agent)
Full Context
configure service vpls sap arp-reply-agent
Description
This command enables a special ARP response mechanism in the system for ARP requests destined to static or dynamic hosts associated with the SAP. The system responds to each ARP request using the host’s MAC address as the both the source MAC address in the Ethernet header and the target hardware address in the ARP header.
ARP replies and requests received on a SAP with arp-reply-agent enabled is evaluated by the system against the anti-spoof filter entries associated with the ingress SAP (if the SAP has anti-spoof filtering enabled). ARPs from unknown hosts on the SAP is discarded when anti-spoof filtering is enabled.
The ARP reply agent only responds if the ARP request enters an interface (SAP, spoke SDP or mesh SDP) associated with the VPLS instance of the SAP.
A received ARP request that is not in the ARP reply agent table is flooded to all forwarding interfaces of the VPLS capable of broadcast except the ingress interface while honoring split-horizon constraints.
Static hosts can be defined on the SAP using the host command. Dynamic hosts are enabled on the system by enabling the lease-populate command in the SAP’s dhcp context. If both a static host and a dynamic host share the same IP and MAC address, the VPLS ARP reply agent will retain the host information until both the static and dynamic information are removed. If both a static and dynamic host share the same IP address, but different MAC addresses, the VPLS ARP reply agent is populated with the static host information.
The arp-reply-agent command fails if an existing static host on the SAP does not have both MAC and IP addresses specified. Once the ARP reply agent is enabled, creating a static host on the SAP without both an IP address and MAC address will fail.
The apr-reply-agent can only be enabled on SAPs supporting Ethernet encapsulation.
The no form of the command disables arp-reply-agent functions for static and dynamic hosts on the SAP.
Default
no arp-reply-agent
Parameters
- sub-ident
-
Configures the arp-reply-agent to discard ARP requests received on the SAP that are targeted for a known host on the same SAP with the same subscriber identification.
Hosts are identified by their subscriber information. For DHCP subscriber hosts, the subscriber hosts, the subscriber information is configured using the optional subscriber parameter string.
When arp-reply-agent is enabled with sub-ident:
-
If the subscriber information for the destination host exactly matches the subscriber information for the originating host and the destination host is known on the same SAP as the source, the ARP request is silently discarded.
-
If the subscriber information for the destination host or originating host is unknown or undefined, the source and destination hosts are not considered to be the same subscriber. The ARP request is forwarded outside the SAP’s Split Horizon Group.
-
When sub-ident is not configured, the arp-reply-agent does not attempt to identify the subscriber information for the destination or originating host and will not discard an ARP request based on subscriber information.
-
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
arp-reply-agent
Syntax
arp-reply-agent [sub-ident]
no arp-reply-agent
Context
[Tree] (config>subscr-mgmt>msap-policy>vpls-only arp-reply-agent)
Full Context
configure subscriber-mgmt msap-policy vpls-only-sap-parameters arp-reply-agent
Description
This command enables a special ARP response mechanism in the system for ARP requests destined to static or dynamic hosts associated with the SAP. The system responds to each ARP request using the hosts MAC address as the both the source MAC address in the Ethernet header and the target hardware address in the ARP header.
ARP replies and requests received on an MSAP with arp-reply-agent enabled is evaluated by the system against the anti-spoof filter entries associated with the ingress SAP (if the SAP has anti-spoof filtering enabled). ARPs from unknown hosts on the SAP is discarded when anti-spoof filtering is enabled.
The ARP reply agent only responds if the ARP request enters an interface (SAP, spoke-SDP or mesh-SDP) associated with the VPLS instance of the MSAP.
A received ARP request that is not in the ARP reply agent table is flooded to all forwarding interfaces of the VPLS capable of broadcast except the ingress interface while honoring split-horizon constraints.
Static hosts can be defined using the host command. Dynamic hosts are enabled on the system by enabling the lease-populate command in the dhcp context. In the event that both a static host and a dynamic host share the same IP and MAC address, the VPLS ARP reply agent will retain the host information until both the static and dynamic information are removed. In the event that both a static and dynamic host share the same IP address, but different MAC addresses, the VPLS ARP reply agent is populated with the static host information.
The arp-reply-agent command will fail if an existing static host does not have both MAC and IP addresses specified. Once the ARP reply agent is enabled, creating a static host on the MSAP without both an IP address and MAC address will fail.
The ARP-reply-agent may only be enabled on SAPs supporting Ethernet encapsulation.
The no form of this command disables ARP-reply-agent functions for static and dynamic hosts on the MSAP.
Parameters
- sub-ident
-
Configures the arp-reply-agent to discard ARP requests received on the MSAP that are targeted for a known host on the same MSAP with the same subscriber identification.
Hosts are identified by their subscriber information. For DHCP subscriber hosts, the subscriber hosts, the subscriber information is configured using the optional subscriber parameter string.
When arp-reply-agent is enabled with sub-ident:
-
If the subscriber information for the destination host exactly matches the subscriber information for the originating host and the destination host is known on the same MSAP as the source, the ARP request is silently discarded.
-
If the subscriber information for the destination host or originating host is unknown or undefined, the source and destination hosts are not considered to be the same subscriber. The ARP request is forwarded outside the MSAP’s Split Horizon Group.
-
When sub-ident is not configured, the arp-reply-agent does not attempt to identify the subscriber information for the destination or originating host and will not discard an ARP request based on subscriber information.
-
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
arp-retry-timer
arp-retry-timer
Syntax
arp-retry-timer timer-multiple
no arp-retry-timer
Context
[Tree] (config>service>ies>if arp-retry-timer)
Full Context
configure service ies interface arp-retry-timer
Description
This command allows the arp retry timer to be configured to a specific value.
The timer value is entered as a multiple of 100 ms. So a timer value of 1, means the ARP timer will be set to 100 ms.
The no form of this command removes the command from the active configuration and returns the ARP retry timer to its default value of 5 seconds.
Default
arp-retry-timer 50
Parameters
- timer-multiple
-
Specifies the multiple of 100 ms that the ARP retry timer will be configured as.
Platforms
All
arp-retry-timer
Syntax
arp-retry-timer timer-multiple
no arp-retry-timer
Context
[Tree] (config>service>vprn>if arp-retry-timer)
[Tree] (config>service>vprn>network-interface arp-retry-timer)
Full Context
configure service vprn interface arp-retry-timer
configure service vprn network-interface arp-retry-timer
Description
This command allows the arp retry timer to be configured to a specific value.
The timer value is entered as a multiple of 100 ms. So a timer value of 1, means the ARP timer will be set to 100 ms.
The no form of this command removes the command from the active configuration and returns the ARP retry timer to its default value of 5 s.
Default
arp-retry-timer 50
Parameters
- timer-multiple
-
Specifies the multiple of 100 ms that the ARP retry timer will be configured as.
Platforms
All
arp-retry-timer
Syntax
arp-retry-timer timer-multiple
no arp-retry-timer
Context
[Tree] (config>router>if arp-retry-timer)
Full Context
configure router interface arp-retry-timer
Description
This command allows the arp retry timer to be configured to a specific value.
The timer value is entered as a multiple of 100 ms. So a timer value of 1, means the ARP timer will be set to 100 ms.
The no form of this command removes the command from the active configuration and returns the ARP retry timer to its default value of 5 seconds.
Default
arp-retry-timer 50
Parameters
- timer-multiple
-
Specifies the multiple of 100 ms that the ARP retry timer will be configured as.
Platforms
All
arp-timeout
arp-timeout
Syntax
arp-timeout seconds
no arp-timeout
Context
[Tree] (config>service>vprn>if arp-timeout)
[Tree] (config>service>ies>if arp-timeout)
[Tree] (config>service>vprn>sub-if>grp-if arp-timeout)
[Tree] (config>service>ies>sub-if>grp-if arp-timeout)
Full Context
configure service vprn interface arp-timeout
configure service ies interface arp-timeout
configure service vprn subscriber-interface group-interface arp-timeout
configure service ies subscriber-interface group-interface arp-timeout
Description
This command configures the minimum time in seconds an ARP entry learned on the IP interface is stored in the ARP table. ARP entries are automatically refreshed when an ARP request or gratuitous ARP is seen from an IP host, otherwise, the ARP entry is aged from the ARP table. If arp-timeout is set to a value of zero seconds, ARP aging is disabled.
When the arp-populate and lease-populate commands are enabled on an interface, the ARP table entries will no longer be dynamically learned, but instead by snooping DHCP ACK message from a DHCP server. In this case the configured arp-timeout value has no effect.
The default value for arp-timeout is 14400 seconds (4 hours).
The no form of this command reverts to the default value.
Default
arp-timeout 14400
Parameters
- seconds
-
Specifies the minimum number of seconds a learned ARP entry is stored in the ARP table, expressed as a decimal integer. A value of zero specifies that the timer is inoperative and learned ARP entries will not be aged.
Platforms
All
- configure service vprn interface arp-timeout
- configure service ies interface arp-timeout
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface arp-timeout
- configure service vprn subscriber-interface group-interface arp-timeout
arp-timeout
Syntax
arp-timeout seconds
no arp-timeout
Context
[Tree] (config>service>vpls>interface arp-timeout)
Full Context
configure service vpls interface arp-timeout
Description
This command configures the minimum time in seconds an ARP entry learned on the IP interface will be stored in the ARP table. ARP entries are automatically refreshed when an ARP request or gratuitous ARP is seen from an IP host, otherwise, the ARP entry is aged from the ARP table. If arp-timeout is set to a value of zero seconds, ARP aging is disabled.
The default value for arp-timeout is 14400 seconds (4 hours).
The no form of this command restores arp-timeout to the default value.
Default
arp-timeout 14400
Parameters
- seconds
-
The minimum number of seconds a learned ARP entry will be stored in the ARP table, expressed as a decimal integer. A value of zero specifies that the timer is inoperative and learned ARP entries will not be aged.
Platforms
All
arp-timeout
Syntax
arp-timeout seconds
no arp-timeout
Context
[Tree] (config>router>if arp-timeout)
Full Context
configure router interface arp-timeout
Description
This command configures the minimum time, in seconds, an ARP entry learned on the IP interface is stored in the ARP table. ARP entries are automatically refreshed when an ARP request or gratuitous ARP is seen from an IP host. Otherwise, the ARP entry is aged from the ARP table. If the arp-timeout value is set to 0 seconds, ARP aging is disabled.
The no form of this command reverts to the default value.
Default
no arp-timeout
Parameters
- seconds
-
The minimum number of seconds a learned ARP entry is stored in the ARP table, expressed as a decimal integer. A value of 0 specifies that the timer is inoperative and learned ARP entries will not be aged.
Platforms
All
as-matrix
as-matrix
Syntax
[no] as-matrix
Context
[Tree] (config>cflowd>collector>aggregation as-matrix)
Full Context
configure cflowd collector aggregation as-matrix
Description
This command specifies that the aggregation data should be based on autonomous system (AS) information. An AS matrix contains packet and byte counters for traffic from either source-destination autonomous systems or last-peer to next-peer autonomous systems.
The no form of this command removes this type of aggregation from the collector configuration.
Default
no as-matrix
Platforms
All
as-override
as-override
Syntax
[no] as-override
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy as-override)
Full Context
configure subscriber-mgmt bgp-peering-policy as-override
Description
This command replaces all instances of the peer's AS number with the local AS number in a BGP route's AS_PATH.
This command breaks BGP's loop detection mechanism. It should be used carefully.
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
as-override
Syntax
[no] as-override
Context
[Tree] (config>service>vprn>bgp>group>neighbor as-override)
[Tree] (config>service>vprn>bgp>group as-override)
Full Context
configure service vprn bgp group neighbor as-override
configure service vprn bgp group as-override
Description
This command replaces all instances of the peer's AS number with the local AS number in a BGP route's AS_PATH.
This command breaks BGP's loop detection mechanism. It should be used carefully.
Default
no as-override
Platforms
All
as-override
Syntax
[no] as-override
Context
[Tree] (config>router>bgp>group>neighbor as-override)
[Tree] (config>router>bgp>group as-override)
Full Context
configure router bgp group neighbor as-override
configure router bgp group as-override
Description
This command enables BGP to monitor the outbound routes toward the peer and whenever there is a route with the peer’s autonomous system number (ASN) in the AS_PATH, all occurrences are removed and replaced with the advertising router’s local ASN (or its confederation ID if the peer is outside the confederation).
In the group context, the no form of this command disables the functionality. In the neighbor context, the no form of this command causes the setting to be inherited from the group level.
Default
no as-override
Platforms
All
as-path
as-path
Syntax
[no] as-path name
Context
[Tree] (config>router>policy-options as-path)
Full Context
configure router policy-options as-path
Description
This command creates a route policy AS path to use in route policy entries.
The no form of this command deletes the AS path.
Default
no as-path
Parameters
- name
-
The AS path regular expression name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
Platforms
All
as-path
Syntax
as-path name
no as-path
Context
[Tree] (config>router>policy-options>policy-statement>entry>from as-path)
Full Context
configure router policy-options policy-statement entry from as-path
Description
This command configures an AS path regular expression statement as a match criterion for the route policy entry.
If no AS path criterion is specified, any AS path is considered to match.
AS path regular expression statements are configured at the global route policy level (config>router>policy-options>as-path name).
The no form of this command removes the AS path regular expression statement as a match criterion.
Default
no as-path
Parameters
- name
-
Specifies the AS path regular expression name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must be enclosed by at-signs (@) and may be midstring; for example, "@variable@," "start@variable@end", " @variable@end", or "start@variable@".
Platforms
All
as-path
Syntax
as-path {add | replace} name
no as-path
Context
[Tree] (config>router>policy-options>policy-statement>entry>action as-path)
[Tree] (config>router>policy-options>policy-statement>default-action as-path)
Full Context
configure router policy-options policy-statement entry action as-path
configure router policy-options policy-statement default-action as-path
Description
This command assigns a BGP AS path list to routes matching the route policy statement entry.
If no AS path list is specified, the AS path attribute is not changed.
The no form of this command disables the AS path list editing action from the route policy entry.
Default
no as-path
Parameters
- add
-
Specifies that the AS path list is to be prepended to an existing AS list.
- replace
-
Specifies AS path list replaces any existing as path attribute.
- name
-
Specifies the AS path list name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must be enclosed by at-signs (@) and may be midstring; for example, "@variable@," "start@variable@end"," @variable@end", or "start@variable@".
The name specified must already be defined.
Platforms
All
as-path-group
as-path-group
Syntax
[no] as-path-group name
Context
[Tree] (config>router>policy-options as-path-group)
Full Context
configure router policy-options as-path-group
Description
This command creates a route policy AS path regular expression statement to use in route policy entries.
The no form of this command deletes the AS path regular expression statement.
Default
no as-path-group
Parameters
- name
-
Specifies the AS path regular expression name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.
Platforms
All
as-path-group
Syntax
as-path-group name
no as-path-group name
Context
[Tree] (config>router>policy-options>policy-statement>entry>from as-path-group)
Full Context
configure router policy-options policy-statement entry from as-path-group
Description
This command creates a route policy AS path regular expression statement to use in route policy entries.
The no form of this command deletes the AS path regular expression statement.
Default
no as-path-group
Parameters
- name
-
Specifies the AS path regular expression name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must be enclosed by at-signs (@) and may be midstring; for example, "@variable@," "start@variable@end", " @variable@end", or "start@variable@".
Platforms
All
as-path-ignore
as-path-ignore
Syntax
as-path-ignore [ipv4] [ipv6] [ label-ipv4] [label-ipv6]
no as-path-ignore
Context
[Tree] (config>service>vprn>bgp>path-selection as-path-ignore)
Full Context
configure service vprn bgp best-path-selection as-path-ignore
Description
This command configures whether AS path length is considered in the selection of the best BGP route for a prefix.
If an address family is listed in this command, the length of AS paths is not a factor in the route selection process for routes of that address family.
The no form of this command removes the parameter from the configuration.
Default
no as-path-ignore
Parameters
- ipv4
-
Specifies that the AS path length is ignored for all unlabeled unicast IPv4 routes.
- ipv6
-
Specifies that the AS path length is ignored for all unlabeled unicast IPv6 routes.
- label-ipv4
-
Specifies that the AS path length is ignored for all labeled unicast IPv4 routes.
- label-ipv6
-
Specifies that the AS path length is ignored for all labeled unicast IPv6 routes.
Platforms
All
as-path-ignore
Syntax
as-path-ignore [ipv4] [label-ipv4] [ vpn-ipv4] [ipv6] [ label-ipv6] [vpn-ipv6] [mcast-ipv4] [mcast-ipv6] [ mvpn-ipv4] [mvpn-ipv6] [l2-vpn]
no as-path-ignore
Context
[Tree] (config>router>bgp>best-path-selection as-path-ignore)
Full Context
configure router bgp best-path-selection as-path-ignore
Description
This command configures whether AS path length is considered in the selection of the best BGP route for a prefix.
If an address family is listed in this command, then the length of AS paths is not a factor in the route selection process for routes of that address family.
The no form of this command removes the parameter from the configuration.
Default
no as-path-ignore
Parameters
- ipv4
-
Specifies that the AS-path length will be ignored for all unlabeled unicast IPv4 routes.
- label-ipv4
-
Specifies that the AS-path length will be ignored for all labeled-unicast IPv4 routes.
- vpn-ipv4
-
Specifies that the length AS-path will be ignored for all VPN IPv4 (SAFI 128) routes.
- ipv6
-
Specifies that the AS-path length will be ignored for all unlabeled unicast IPv6 routes.
- label-ipv6
-
Specifies that the AS-path length will be ignored for all labeled-unicast IPv6 routes.
- vpn-ipv6
-
Specifies that the AS-path length will be ignored for all VPN IPv6 (SAFI 128) routes.
- mcast-ipv4
-
Specifies that the AS-path length will be ignored for all IPv4 multicast routes.
- mcast-ipv6
-
Specifies that the AS-path length will be ignored for all IPv6 multicast routes.
- mvpn-ipv4
-
Specifies that the AS-path length will be ignored for all IPv4 MVPN routes.
- mvpn-ipv6
-
Specifies that the AS-path length will be ignored for all IPv6 MVPN routes.
- l2-vpn
-
Specifies that the AS-path length will be ignored for all L2-VPN NLRIs.
Platforms
All
as-path-length
as-path-length
Syntax
as-path-length length [equal | or-higher | or-lower] [unique]
no as-path-length
Context
[Tree] (config>router>policy-options>policy-statement>entry>from as-path-length)
Full Context
configure router policy-options policy-statement entry from as-path-length
Description
This command matches BGP routes based on their AS path length (the number of AS numbers in the AS_PATH).
If no comparison qualifiers are present (equal, or-higher, or-lower), then equal is the implied default.
Confederation member AS numbers in the AS_PATH do not count towards the total. An AS_SET element is considered to have a length of 1.
The unique option counts.
A non-BGP route does not match a policy entry if it contains the as-path-length command.
Default
no as-path-length
Parameters
- length
-
Specifies the length of the AS path.
- equal
-
Specifies that matched routes should have the same number of AS path elements as the value specified.
- or-higher
-
Specifies that matched routes should have the same or a greater number of AS path elements as the value specified.
- or-lower
-
Specifies that matched routes should have the same or a lower number of AS path elements as the value specified.
- unique
-
Specifies that only the unique AS numbers should be counted (that is, multiple occurrences of the same AS number in the sequence count as one).
Platforms
All
as-path-prepend
as-path-prepend
Syntax
as-path-prepend as-path [repeat]
as-path-prepend most-recent [repeat]
no as-path-prepend
Context
[Tree] (config>router>policy-options>policy-statement>entry>action as-path-prepend)
[Tree] (config>router>policy-options>policy-statement>default-action as-path-prepend)
Full Context
configure router policy-options policy-statement entry action as-path-prepend
configure router policy-options policy-statement default-action as-path-prepend
Description
The command prepends a BGP AS number once or numerous times to the AS path attribute of routes matching the route policy statement entry.
If an AS number is not configured, the AS path is not changed.
If the optional number is specified, then the AS number is prepended as many times as indicated by the number.
The no form of this command disables the AS path prepend action from the route policy entry.
Default
no as-path-prepend
Parameters
- as-path
-
Specifies the AS number to prepend expressed as a decimal integer.
- repeat
-
Specifies the number of times to prepend the specified AS number expressed as a decimal integer.
- most-recent
-
Specifies that the most recent AS number must be prepended to the AS-Path attribute of the route.
Platforms
All
asbr
asbr
Syntax
[no] asbr [trace-path domain-id]
no asbr
[no] asbr
Context
[Tree] (config>router>ospf asbr)
[Tree] (config>router>ospf3 asbr)
Full Context
configure router ospf asbr
configure router ospf3 asbr
Description
This command configures the router as an Autonomous System Boundary Router (ASBR) if the router is to be used to export routes from the Routing Table Manager (RTM) into this instance of OSPF. After a router is configured as an ASBR, the export policies into this OSPF domain take effect. If no policies are configured, no external routes are redistributed into the OSPF domain.
The no form of this command removes the ASBR status and withdraws the routes redistributed from the Routing Table Manager into this instance of OSPF from the link state database.
When configuring multiple instances of OSPF, there is a risk of loops because networks are advertised by multiple domains configured with multiple interconnections to one another. To prevent this from happening, all routers in a domain should be configured with the same domain ID. Each domain (OSPF-instance) should be assigned a specific bit value in the 32-bit tag mask.
When an external route is originated by an ASBR using an internal OSPF route in a given domain, the corresponding bit is set in the AS-external LSA. As the route gets redistributed from one domain to another, more bits are set in the tag mask, each corresponding to the OSPF domain the route visited. Route redistribution looping is prevented by checking the corresponding bit as part of the export policy; if the bit corresponding to the announcing OSPF process is already set, the route is not exported there.
Domain IDs are incompatible with any other use of normal tags. The domain ID should be configured with a value between 1 and 31 by each router in a given OSPF domain (OSPF Instance).
When an external route is originated by an ASBR using an internal OSPF route in a given domain, the corresponding (1-31) bit is set in the AS-external LSA.
As the route gets redistributed from one domain to another, more bits are set in the tag mask, each corresponding to the OSPF domain the route visited. Route redistribution looping is prevented by checking the corresponding bit as part of the export policy; if the bit corresponding to the announcing OSPF process is already set, the route is not exported there.
Default
no asbr
Parameters
- domain-id
-
Specifies the domain ID.
Platforms
All
assert
assert
Syntax
assert [group grp-ip-address] [source ip-address] [detail]
no assert
Context
[Tree] (debug>router>pim assert)
Full Context
debug router pim assert
Description
This command enables debugging for PIM assert mechanism.
The no form of this command disables PIM assert debugging.
Parameters
- grp-ip-address
-
Debugs information associated with the PIM assert mechanism.
- ip-address
-
Debugs information associated with the PIM assert mechanism.
- detail
-
Debugs detailed information on the PIM assert mechanism.
Platforms
All
assert-period
assert-period
Syntax
assert-period assert-period
no assert-period
Context
[Tree] (config>service>vprn>pim>if assert-period)
Full Context
configure service vprn pim interface assert-period
Description
This command configures the period in seconds for periodic refreshes of PIM Assert messages on an interface.
The no form of this command reverts to the default.
Default
assert-period 60
Parameters
- assert-period
-
Specifies the period, in seconds, for periodic refreshes of PIM Assert messages on an interface.
Platforms
All
assert-period
Syntax
assert-period assert-period
no assert-period
Context
[Tree] (config>router>pim>interface assert-period)
Full Context
configure router pim interface assert-period
Description
This command configures the period for periodic refreshes of PIM Assert messages on an interface.
The no form of this command removes the assert-period from the configuration.
Default
no assert-period
Parameters
- assert-period
-
Specifies the period, in seconds, for periodic refreshes of PIM Assert messages on an interface.
Platforms
All
assignment
assignment
Syntax
assignment {port port-id | card slot-number}
no assignment
Context
[Tree] (config>service>cust>multi-service-site assignment)
Full Context
configure service customer multi-service-site assignment
Description
This command assigns a multi-service customer site to a specific chassis slot, port, or channel. This allows the system to allocate the resources necessary to create the virtual schedulers defined in the ingress and egress scheduler policies as they are specified. This also verifies that each SAP assigned to the site exists within the context of the proper customer ID and that the SAP was configured on the proper slot, port, or channel. The assignment must be given prior to any SAP associations with the site.
The no form of this command removes the port, channel, or slot assignment. If the customer site has not yet been assigned, the command has no effect and returns without any warnings or messages.
Default
no assignment
Parameters
- port-id
-
Assigns the multi-service customer site to the port-id or port-id.channel-id given. When the multi-service customer site is assigned to a specific port or channel, all SAPs associated with this customer site must be on a service owned by the customer and created on the defined port or channel. The defined port or channel must already have been pre-provisioned on the system but need not be installed when the customer site assignment is made.
Syntax: port-id[:encap-val]
- slot-number
-
Assigns the multi-service customer site to the slot-number given. When the multi-service customer site is assigned to a specific slot in the chassis, all SAPs associated with this customer site must be on a service owned by the customer and created on the defined chassis slot. The defined slot must already be pre-provisioned on the system but need not be installed when the customer site assignment is made.
- fpe-id
-
Specifies the multi-service-site (MSS) assignment to an FPE object for the purpose of controlling aggregated bandwidth across a set of PW SAPs.
Platforms
All
assignment-id
assignment-id
Syntax
assignment-id assignment-id
Context
[Tree] (debug>router>l2tp assignment-id)
Full Context
debug router l2tp assignment-id
Description
This command enables and configures debugging for the L2TP tunnel with a given assignment ID.
Parameters
- assignment-id
-
Specifies a string that distinguishes this L2TP tunnel, up to 63 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
assisted-replication
assisted-replication
Syntax
assisted-replication {replicator | leaf} [replicator-activation-time seconds]
no assisted-replication
Context
[Tree] (config>service>vpls>vxlan assisted-replication)
Full Context
configure service vpls vxlan assisted-replication
Description
This command enables the Assisted Replication (AR) function for VXLAN tunnels in the service. The execution of this command triggers the BGP EVPN to send an update containing the inclusive multicast route for the service and the AR type=AR Replicator (AR-R) or AR Leaf (AR-L).
The Replicators switch the VXLAN traffic back to VXLAN destinations when the IP destination address matches their own AR-IP address. Leaf nodes select a Replicator node and send all the Broadcast or Multicast frames to it so that the Replicator can replicate the traffic on their behalf.
Enabling or disabling the AR function, or changing the role between the replicator and leaf requires the BGP EVPN MPLS to be shutdown.
If the leaf parameter is configured, the system creates a Broadcast or Multicast (BM) destination to the selected AR-R and Unknown Unicast (U) destinations to the rest of the VTEPs. If no replicator exists, the leaf creates BUM bindings to all the VTEPs.
If the replicator parameter is configured, the system will create BUM destinations to the remote leafs, Regular Network Virtualization Edge routers (RNVE), and other AR-Rs. The system will perform assisted replication for traffic from known VTEPs only (that is, where the routes have been received and programmed toward a VTEP).
The no version of this command removes the AR function from the service.
Default
no assisted-replication
Parameters
- replicator-activation-time seconds
-
Optional parameter that can be added to the leaf parameter. It specifies the wait time before the leaf can begin sending traffic to a new replicator and is used to allow some time for the replicator to learn about the leaf.
- replicator | leaf
-
Selects the AR role of the router for the service.
Platforms
All
assisted-replication-ip
assisted-replication-ip
Syntax
assisted-replication-ip ip-address
no assisted-replication-ip
Context
[Tree] (config>service>system>vxlan assisted-replication-ip)
Full Context
configure service system vxlan assisted-replication-ip
Description
The assisted-replication-ip (AR-IP) command defines the IP address that supports the AR-R function in the router. The AR-IP address must also be defined as a loopback address in the base router and advertised in the IGP/BGP so that it is accessible to the remote NVE/PEs in the Overlay network.
If the AR-R function is enabled in a service, the Broadcast and Multicast frames encapsulated in VXLAN packets arriving at the router are replicated to the other VXLAN destinations within the service (except the destination pointing at the originator of the packet).
The no version of this command removes the AR IP address.
Default
no assisted-replication-ip
Parameters
- ip-address
-
Specifies the assisted replication IP address.
Platforms
All
assistive-address-resolution
assistive-address-resolution
Syntax
[no] assistive-address-resolution
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext assistive-address-resolution)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw>lanext assistive-address-resolution)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext assistive-address-resolution
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext assistive-address-resolution
Description
This command enables assistive address resolution (AAR) for HLE services.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
association
association
Syntax
association name
no association
Context
[Tree] (config>service>vpls>sap>pfcp association)
Full Context
configure service vpls sap pfcp association
Description
This command links this capture SAP to a PFCP association. This command enables CUPS for this capture SAP and makes any trigger packets eligible for forwarding to the BNG CUPS CPF.
The no form of this command disables CUPS for this capture SAP.
Parameters
- name
-
Specifies the name of the association, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
association
Syntax
association ma-index [format ma-name-format] name ma-name [admin-name admin-name]
association ma-index
no association ma-index
Context
[Tree] (config>eth-cfm>domain association)
Full Context
configure eth-cfm domain association
Description
This command configures the Maintenance Association (MA) for the domain.
Parameters
- ma-index
-
Specifies the MA index value.
- ma-name-format
-
Specifies a value that represents the type (format).
- ma-name
-
Specifies the part of the MA identifier that is unique within the maintenance domain name, up to 45 characters.
- admin-name
-
Specifies a creation time required parameter that allows the operator to assign a name value to the domain container. This is used for information and migration purposes. This value cannot be modified without destroying the domain. If no admin-name exists, the configured md-index value is converted into a character string to become the admin-name reference. When upgrading from a release that does not include the admin-name configuration option, the md-index is converted into a character string. After an admin-name value is assigned, it cannot be modified.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
association-id
association-id
Syntax
association-id association-id
no association-id
Context
[Tree] (config>router>pcep>pcc>pce-assoc>div association-id)
Full Context
configure router pcep pcc pce-associations diversity association-id
Description
This command configures the diversity association ID. The user must specify an association ID.
The no form of the command removes the association ID from the diversity association.
Default
no association-id
Parameters
- association-id
-
Specifies the diversity association ID.
Platforms
All
association-id
Syntax
association-id association-id
no association-id
Context
[Tree] (config>router>pcep>pcc>pce-assoc>plcy association-id)
Full Context
configure router pcep pcc pce-associations policy association-id
Description
This command configures the policy association ID. The user must specify an association ID.
The no form of the command removes the association ID from the policy association.
Default
no association-id
Parameters
- association-id
-
Specifies the policy association ID.
Platforms
All
association-source
association-source
Syntax
association-source ip-address
no association-source
Context
[Tree] (config>router>pcep>pcc>pce-assoc>div association-source)
Full Context
configure router pcep pcc pce-associations diversity association-source
Description
This command configures the source IP address of the diversity association.
The no form of the command removes the IP address from the diversity association.
Default
no association-source
Parameters
- ip-address
-
Specifies the source IP address.
Platforms
All
association-source
Syntax
association-source ip-address
no association-source
Context
[Tree] (config>router>pcep>pcc>pce-assoc>plcy association-source)
Full Context
configure router pcep pcc pce-associations policy association-source
Description
This command configures the source IP address of the policy association.
The no form of the command removes IP address from the policy association.
Default
no association-source
Parameters
- ip-address
-
Specifies the source IP address.
Platforms
All
async-mapping
async-mapping
Syntax
[no] async-mapping
Context
[Tree] (config>port>otu async-mapping)
Full Context
configure port otu async-mapping
Description
This command allows the user to configure the port to support asynchronous mapping of the payload inside the OTU. If the port is configured for async-mapping and the payload clock is asynchronous to the OTU clock, there will be positive or negative pointer justification that will show up in the OTU statistics and the data will be received error free. If the port is configured for synchronous mapping and the received data is asynchronously mapped, there will be errors in the received data.
async-mapping is the only mode of operation that is supported on the OTU3 encapsulated 40-Gigabit Ethernet and therefore the 'no async-mapping' is not supported on that port type and the default on the is async-mapping.
The no form of this command configures the port to receive synchronously mapped data.
Default
no async-mapping
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
asynchronous-execution
asynchronous-execution
Syntax
asynchronous-execution seconds
asynchronous-execution never
Context
[Tree] (config>system>management-interface>ops>global-timeout asynchronous-execution)
Full Context
configure system management-interface operations global-timeouts asynchronous-execution
Description
This command configures the period of time that operations launched as "asynchronous” are allowed to execute before being automatically stopped by the SR OS.
An asynchronous operation is not deleted from the system when it is stopped. See the asynchronous-retention command.
If a specific execution timeout is not included in the request for a particular asynchronous operation, this system-level timeout applies.
This execution timeout is part of the general global operations infrastructure and is separate and independent from any operation-specific timeouts (for example, the ping operation also has its own timeout parameter).
Default
asynchronous-execution 3600
Parameters
- seconds
-
Specifies the period of time, in seconds, that asynchronous operations are allowed to execute.
- never
-
Keyword to specify that an execution timeout is not applied to asynchronous operations.
Platforms
All
asynchronous-retention
asynchronous-retention
Syntax
asynchronous-retention seconds
asynchronous-retention never
Context
[Tree] (config>system>management-interface>ops>global-timeout asynchronous-retention)
Full Context
configure system management-interface operations global-timeouts asynchronous-retention
Description
This command configures the period of time that data related to operations launched as "asynchronous” is retained in the system. After the retention timeout expires, all information related to the operation is deleted, including any status information and result data.
If a specific retention timeout is not included in the request for a particular asynchronous operation, this system-level timeout applies.
Default
asynchronous-retention 86400
Parameters
- seconds
-
Specifies the period of time, in seconds, that data related to asynchronous operations is retained in the system.
- never
-
Keyword to specify that data related to asynchronous operations will persist in memory until explicitly deleted.
Platforms
All
attempts
attempts
Syntax
attempts count [time minutes1 [lockout minutes2]
no attempts
Context
[Tree] (config>system>security>password attempts)
Full Context
configure system security password attempts
Description
This command configures a threshold value of unsuccessful login attempts allowed in a specified time frame.
If the threshold is exceeded, the user is locked out for a specified time period.
If multiple attempts commands are entered, each command overwrites the previously entered command.
The no attempts command resets all values to default.
This command applies to a local user, in addition to users on RADIUS, TACACS, and LDAP.
Default
attempts 3 time 5 lockout 10
Parameters
- count
-
Specifies the number of unsuccessful login attempts allowed for the specified time. This is a mandatory value that must be explicitly entered.
- minutes
-
Specifies the period of time, in minutes, that a specified number of unsuccessful attempts can be made before the user is locked out.
- minutes
-
Specifies the lockout period, in minutes, during which the user is not allowed to login.
Platforms
All
attempts
Syntax
attempts [count] [time minutes1] [lockout minutes2]
no attempts
Context
[Tree] (config>system>security>snmp attempts)
Full Context
configure system security snmp attempts
Description
This command configures a threshold value of unsuccessful SNMPv2 or SNMPv3 connection attempts allowed in a specified time frame. The command parameters are used to counter denial of service (DoS) attacks through SNMP.
If the threshold is exceeded, the host is locked out for the lockout time period.
The no form of the command restores the default values.
Default
attempts 20 time 5 lockout 10
Parameters
- count
-
Specifies the number unsuccessful SNMP attempts allowed for the specified time.
- minutes1
-
Specifies period of time, in minutes, that a specified number of unsuccessful attempts can be made before the host is locked out.
- minutes2
-
Specifies the lockout period in minutes where the host is not allowed to login. When the host exceeds the attempted count times in the specified time, then that host is locked out from any further login attempts for the configured time period.
Platforms
All
attrib
attrib
Syntax
attrib [+r | -r] file-url
attrib
Context
[Tree] (file attrib)
Full Context
file attrib
Description
This command sets or clears/resets the read-only attribute for a file in the local file system. To list all files and their current attributes enter attrib or attrib x where x is either the filename or a wildcard (*).
When an attrib command is entered to list a specific file or all files in a directory, the file’s attributes are displayed with or without an "R” preceding the filename. The "R” implies that the +r is set and that the file is read-only. Files without the "R” designation implies that the -r is set and that the file is read-write-all. For example:
ALA-1>file cf3:\ # attrib
cf3:\bootlog.txt
cf3:\bof.cfg
cf3:\boot.ldr
cf3:\sr1.cfg
cf3:\test
cf3:\bootlog_prev.txt
cf3:\BOF.SAV
Parameters
- file-url
-
Specifies the URL for the local file.
- +r
-
Sets the read-only attribute on the specified file.
- -r
-
Clears/resets the read-only attribute on the specified file.
Platforms
All
attribute
attribute
Syntax
attribute [vendor vendor-id] attribute-type attribute-type
no attribute
Context
[Tree] (config>service>vprn>nat>inside>subscriber-identification attribute)
[Tree] (config>router>nat>inside>subscriber-identification attribute)
Full Context
configure service vprn nat inside subscriber-identification attribute
configure router nat inside subscriber-identification attribute
Description
This command defines the attribute that will in addition to framed-ip-address (inside IP address) and service-id be used for correlating BNG subscriber with the NAT subscriber.
Only a single attribute at the time can be configured. The attribute will be extracted from the BNG accounting start and/or interim-update messages via RADIUS accounting proxy server. This attribute can be then optionally passed to the Large Scale NAT44 accounting server. User-name attribute (if included) in Large Scale NAT44 accounting messages will be automatically set to the subscriber-id string.
The attribute parameter can be changed at any given time and the change will be reflected automatically when the next interim-update message from the BNG host is received by the RADIUS accounting proxy.
In case that the BNG accounting message in RADIUS accounting proxy does not contain this attribute, subscriber aware Large Scale NAT44 functionality for this particular subscriber will be disabled.
Default
attribute vendor "nokia" attribute-type "alc-sub-string"
Parameters
- vendor vendor-id
-
specifies the RADIUS vendor ID.
- attribute-type attribute-type
-
Specifies the RADIUS attribute to be used as subscriber. identifier
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
attribute-matching
attribute-matching
Syntax
attribute-matching
Context
[Tree] (config>router>radius-proxy>server attribute-matching)
[Tree] (config>service>vprn>radius-proxy>server attribute-matching)
Full Context
configure router radius-proxy server attribute-matching
configure service vprn radius-proxy server attribute-matching
Description
Commands in this context select the RADIUS policy for authentication and accounting based on the RADIUS attribute. This feature is supported for both the ESM RADIUS proxy and the ISA RADIUS proxy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
attribute-propagation
attribute-propagation
Syntax
[no] attribute-propagation
Context
[Tree] (config>service>system>bgp-evpn>ad-per-evi-routes attribute-propagation)
Full Context
configure service system bgp-evpn ad-per-evi-routes attribute-propagation
Description
This command enables attribute propagation in multi-instance Epipe services.
The no form of this command disables the propagation of attributes, including D-PATH, even if the domain-id is configured in the service.
Default
no attribute-propagation
Platforms
All
attribute-set
attribute-set
Syntax
attribute-set
Context
[Tree] (config>service>vprn>bgp attribute-set)
Full Context
configure service vprn bgp attribute-set
Description
Commands in this context configure the handling of attribute set (ATTR_SET) attributes in BGP routes received from PE-CE peers of the VPRN.
ATTR_SET is an optional transitive BGP path attribute standardized by RFC 6368 that is added to BGP Layer 3 VPN routes to provide logical separation between the BGP domain of a customer and the BGP domain of a service provider.
Platforms
All
attribute-set
Syntax
attribute-set
Context
[Tree] (config>service>vprn>bgp-ipvpn attribute-set)
Full Context
configure service vprn bgp-ipvpn attribute-set
Description
Commands in this context configure the handling of attribute set (ATTR_SET) attributes attached to VPN-IP routes imported into or exported from the VPRN.
ATTR_SET is an optional transitive BGP path attribute standardized by RFC 6368 that is added to BGP Layer 3 VPN routes to provide logical separation between the BGP domain of a customer and the BGP domain of a service provider.
Platforms
All
attribute-table-high-wmark
attribute-table-high-wmark
Syntax
no attribute-table-high-wmark high-water-mark
no attribute-table-high-wmark
Context
[Tree] (config>service>vpls>mrp>mmrp attribute-table-high-wmark)
[Tree] (config>service>vpls>mrp>mvrp attribute-table-high-wmark)
Full Context
configure service vpls mrp mmrp attribute-table-high-wmark
configure service vpls mrp mvrp attribute-table-high-wmark
Description
This command specifies the percentage filling level of the MMRP attribute table where logs and traps are sent.
Default
attribute-table-high-wmark 95
Parameters
- high-water-mark
-
Specifies the utilization of the MRP attribute table of this service at which a table full alarm will be raised by the agent, as a percentage.
Platforms
All
attribute-table-low-wmark
attribute-table-low-wmark
Syntax
attribute-table-low-wmark low-water-mark
no attribute-table-low-wmark
Context
[Tree] (config>service>vpls>mrp>mmrp attribute-table-low-wmark)
[Tree] (config>service>vpls>mrp>mvrp attribute-table-low-wmark)
Full Context
configure service vpls mrp mmrp attribute-table-low-wmark
configure service vpls mrp mvrp attribute-table-low-wmark
Description
This command specifies the MMRP attribute table low watermark as a percentage. When the percentage filling level of the MMRP attribute table drops below the configured value, the corresponding trap is cleared and/or a log entry is added.
Default
attribute-table-low-wmark 90
Parameters
- low-water-mark
-
Specifies utilization of the MRP attribute table of this service at which a table full alarm will be cleared by the agent, as a percentage.
Platforms
All
attribute-table-size
attribute-table-size
Syntax
attribute-table-size max-attributes
no attribute-table-size
Context
[Tree] (config>service>vpls>mrp>mmrp attribute-table-size)
Full Context
configure service vpls mrp mmrp attribute-table-size
Description
This command controls the number of attributes accepted on a per B-VPLS basis. When the limit is reached, no new attributes will be registered.
If a new lower limit (smaller than the current number of attributes) from a local or dynamic I-VPLS is being provisioned, a CLI warning will be issued stating that the system is currently beyond the new limit. The value will be accepted, but any creation of new attributes will be blocked under the attribute count drops below the new limit; the software will then start enforcing the new limit.
Default
maximum number of attributes
Parameters
- value
-
The maximum number of attributes accepted per B-VPLS.
Platforms
All
attribute-table-size
Syntax
[no] attribute-table-size value
Context
[Tree] (config>service>vpls>mrp>mvrp attribute-table-size)
Full Context
configure service vpls mrp mvrp attribute-table-size
Description
This command controls the number of attributes accepted on a per M-VPLS basis. When the limit is reached, no new attributes will be registered.
If a new lower limit (smaller than the current number of attributes) is being provisioned, a CLI warning will be issued stating that the system is currently beyond the new limit. The value will be accepted, but any creation of new attributes will be blocked under the attribute count drops below the new limit; the software will then start enforcing the new limit.
Default
maximum number of attributes
Parameters
- value
-
Specifies the number of attributes accepted on a per M-VPLS basis
Platforms
All
attribute-uniform-propagation
attribute-uniform-propagation
Syntax
[no] attribute-uniform-propagation
Context
[Tree] (config>service>system>bgp-evpn>ip-prefix-routes>iff attribute-uniform-propagation)
Full Context
configure service system bgp-evpn ip-prefix-routes interface-ful attribute-uniform-propagation
Description
This command enables the uniform propagation of BGP attributes for EVPN Interface-ful (EVPN-IFF) routes. EVPN-IFF is used in R-VPLS services with bgp-evpn>ip-route-advertisement. When enabled, the received EVPN-IFF routes for the R-VPLS can be propagated with the original BGP path attributes into EVPN-IFL, IPVPN, EVPN-IFF (in other R-VPLS services), or BGP IP routes advertised for the attached VPRN. This command also enables the attribute propagation in the opposite direction; for example, from EVPN-IFL, IPVPN, IP, or EVPN-IFF routes into EVPN-IFF routes.
The propagation is in accordance with the uniform mode defined in draft-ietf-bess-evpn-ipvpn-interworking.
The no form of this command re-originates the BGP path attributes when propagating EVPN-IFF routes into other inter-subnet forwarding families.
Default
no attribute-uniform-propagation
Platforms
All
augment-route-table
augment-route-table
Syntax
[no] augment-route-table
Context
[Tree] (config>router>isis>loopfree-alternates augment-route-table)
Full Context
configure router isis loopfree-alternates augment-route-table
Description
This command enables IS-IS to attach Remote LFA specific information to RTM entries for use by other protocols. This command requires configure router isis lfa remote-lfa to be enabled. Currently only LDP makes use of this additional information.
The no form of this command disables IS-IS to attach Remote LFA specific information to RTM entries for use by other protocols.
Platforms
All
augment-route-table
Syntax
[no] augment-route-table
Context
[Tree] (config>router>ospf>loopfree-alternates augment-route-table)
Full Context
configure router ospf loopfree-alternates augment-route-table
Description
This command enables OSPF to attach Remote LFA (rLFA) information to RTM entries for use by other protocols. Before this command is configured, the configure router ospf lfa remote-lfa command, must be enabled on the system. Currently, only LDP makes use of this additional information.
The no form of this command disables the attachment of rLFA-specific information to RTM entries for use by other protocols.
Default
no augment-route-table
Platforms
All
auth
auth
Syntax
[no] auth
Context
[Tree] (debug>router>rsvp>event auth)
Full Context
debug router rsvp event auth
Description
This command debugs auth events.
The no form of the command disables the debugging.
Platforms
All
auth
Syntax
[no] auth [neighbor ip-int-name | ip-address]
Context
[Tree] (debug>router>rip auth)
Full Context
debug router rip auth
Description
This command enables debugging for RIP authentication.
Parameters
- ip-int-name | ip-address
-
Debugs the RIP authentication for the neighbor IP address or interface.
Platforms
All
auth-domain-name
auth-domain-name
Syntax
auth-domain-name domain-name
no auth-domain-name
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host auth-domain-name)
Full Context
configure subscriber-mgmt local-user-db ipoe host auth-domain-name
Description
This command sets the domain name which can be appended to user-name in RADIUS-authentication-request message for the given host.
The no form of this command removes the domain name from the host configuration.
Parameters
- domain-name
-
Specifies the domain name, up to 32 characters, to be appended to user-name in RADIUS-authentication-request message for the given host.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auth-include-attributes
auth-include-attributes
Syntax
[no] auth-include-attributes
Context
[Tree] (config>aaa>isa-radius-plcy auth-include-attributes)
Full Context
configure aaa isa-radius-policy auth-include-attributes
Description
This command configures attributes to be included in RADIUS authentication messages.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
auth-keychain
auth-keychain
Syntax
auth-keychain name
no auth-keychain
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy auth-keychain)
Full Context
configure subscriber-mgmt bgp-peering-policy auth-keychain
Description
This command configures the BGP authentication key for all peers.
The keychain allows the rollover of authentication keys during the lifetime of a session.
The no form of this command reverts to the default.
Parameters
- name
-
Specifies the name of an existing keychain, up to 32 characters, to use for the specified TCP session or sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>service>vprn>bgp>group auth-keychain)
[Tree] (config>service>vprn>bgp auth-keychain)
[Tree] (config>service>vprn>bgp>group>neighbor auth-keychain)
Full Context
configure service vprn bgp group auth-keychain
configure service vprn bgp auth-keychain
configure service vprn bgp group neighbor auth-keychain
Description
This command configures the BGP authentication key for all peers.
The keychain allows the rollover of authentication keys during the lifetime of a session.
Default
no auth-keychain
Parameters
- name
-
Specifies the name of an existing keychain, up to 32 characters, to use for the specified TCP session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>service>vprn>isis>level auth-keychain)
[Tree] (config>service>vprn>isis auth-keychain)
Full Context
configure service vprn isis level auth-keychain
configure service vprn isis auth-keychain
Description
This command configures an authentication keychain to use for the protocol interface for the VPRN instance. The keychain allows the rollover of authentication keys during the lifetime of a session.
Default
no auth-keychain
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters, to use for the specified protocol session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>router>isis auth-keychain)
[Tree] (config>router>isis>level auth-keychain)
Full Context
configure router isis auth-keychain
configure router isis level auth-keychain
Description
This command configures an authentication keychain to use for the protocol interface. The keychain allows the rollover of authentication keys during the lifetime of a session.
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters, to use for the specified protocol session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>service>vprn>ospf>area>if auth-keychain)
[Tree] (config>service>vprn>ospf>area>sham-link auth-keychain)
[Tree] (config>service>vprn>ospf>area>virtual-link auth-keychain)
Full Context
configure service vprn ospf area interface auth-keychain
configure service vprn ospf area sham-link auth-keychain
configure service vprn ospf area virtual-link auth-keychain
Description
This command enables the authentication keychain.
Parameters
- name
-
Specifies the name of the authentication keychain, up to 32 characters.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>router>ldp>tcp-session-params auth-keychain)
[Tree] (config>router>ldp>tcp-session-params>peer-transport auth-keychain)
Full Context
configure router ldp tcp-session-parameters auth-keychain
configure router ldp tcp-session-parameters peer-transport auth-keychain
Description
This command configures the TCP authentication keychain to use for the TCP session. The per-peer authentication configuration takes precedence over the global authentication configuration.
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters. This keychain is used for the specified TCP session or sessions, and allows the rollover of authentication keys during the lifetime of a session. The peer address used must be the TCP session transport address.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>router>rsvp>interface auth-keychain)
Full Context
configure router rsvp interface auth-keychain
Description
This command configures an authentication keychain to use for authentication of protocol messages sent and received over the associated interface. The keychain must include a valid entry to properly authenticate protocol messages, including a key, specification of a supported authentication algorithm, and beginning time. Each entry may also include additional options to control the overall lifetime of each entry to allow for the seamless rollover of without affecting the protocol adjacencies.
The no form of the auth-keychain command removes the association between the routing protocol and any keychain currently used.
Default
no auth-keychain
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters, to use for the specified protocol session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>router>bgp>group>neighbor auth-keychain)
[Tree] (config>router>bgp>group auth-keychain)
[Tree] (config>router>bgp auth-keychain)
Full Context
configure router bgp group neighbor auth-keychain
configure router bgp group auth-keychain
configure router bgp auth-keychain
Description
This command configures a TCP authentication keychain to use for the session. The keychain allows the rollover of authentication keys during the lifetime of a session.
Default
no auth-keychain
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters, to use for the specified TCP session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain
Context
[Tree] (config>router>ospf>area>virtual-link auth-keychain)
[Tree] (config>router>ospf>area>interface auth-keychain)
Full Context
configure router ospf area virtual-link auth-keychain
configure router ospf area interface auth-keychain
Description
This command configures an authentication keychain to use for the protocol interface. The keychain allows the rollover of authentication keys during the lifetime of a session.
The no form of this command removes the association to a previously specified keychain.
Default
no auth-keychain
Parameters
- name
-
Specifies the name of the keychain, up to 32 characters, to use for the specified protocol session or sessions.
Platforms
All
auth-keychain
Syntax
auth-keychain name
Context
[Tree] (config>router>pcep>pcc>peer auth-keychain)
[Tree] (config>router>pcep>pce auth-keychain)
Full Context
configure router pcep pcc peer auth-keychain
configure router pcep pce auth-keychain
Description
This command specifies a keychain to be used for TCP-AO authentication between the PCC and the PCE. The keychain must first be configured in the configure system security keychain context.
Default
no auth-keychain
Parameters
- name
- Specifies the name of the keychain, up to 32 characters.
Platforms
All
- configure router pcep pcc peer auth-keychain
VSR-NRC
- configure router pcep pce auth-keychain
auth-method
auth-method
Syntax
auth-method {psk | plain-psk-xauth | cert-auth | psk-radius | cert-radius | eap | auto-eap-radius | auto-eap}
no auth-method
Context
[Tree] (config>ipsec>ike-policy auth-method)
Full Context
configure ipsec ike-policy auth-method
Description
This command specifies the authentication method used with this IKE policy.
The no form of this command removes the parameter from the configuration.
Default
no auth-method
Parameters
- psk
-
Both client and gateway authenticate each other by a hash derived from a pre-shared secret. Both client and gateway must have the PSK. This work with both IKEv1 and IKEv2
- plain-psk-xauth
-
Both client and gateway authenticate each other by pre-shared key and RADIUS. This work with IKEv1 only.
- psk-radius
-
Use the pre-shared-key and RADIUS to authenticate. IKEv2 remote-access tunnel only.
- cert-radius
-
Use the certificate, public/private key and RADIUS to authenticate. IKEv2 remote-access tunnel only.
- eap
-
Use the EAP to authenticate peer. IKEv2 remote-access tunnel only
- auto-eap-radius
-
Use EAP or potentially other method to authenticate the peer. IKEv2 remote-access tunnel only. Also see config>ipsec>ike-policy auto-eap-method and config>ipsec>ike-policy auto-eap-own-method.
- auto-eap
-
Use the EAP or potentially other RADIUS-related method to authenticate the peer. IKEv2 remote-access tunnel only. Also see config>ipsec>ike-policy auto-eap-method and config>ipsec>ike-policy auto-eap-own-method.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
auth-policy
auth-policy
Syntax
auth-policy policy-name
no auth-policy
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host auth-policy)
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host auth-policy)
Full Context
configure subscriber-mgmt local-user-db ipoe host auth-policy
configure subscriber-mgmt local-user-db ppp host auth-policy
Description
This command configures the authentication policy of this host and PPPoE hosts. This authentication policy is only used if no authentication policy is defined at the interface level. For DHCP hosts, the host entry should not contain any other information needed for setup of the host (IP address, ESM strings, and so on.). For PPPoE hosts, the authentication policy configured here must have its PPPoE authentication method set to pap-chap, otherwise the request is dropped.
The no form of this command reverts to the default.
Parameters
- policy-name
-
Specifies the authentication policy name, up to 32 characters
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auth-port
auth-port
Syntax
auth-port port
no auth-port
Context
[Tree] (config>router>radius-server>server auth-port)
[Tree] (config>service>vprn>radius-server>server auth-port)
Full Context
configure router radius-server server auth-port
configure service vprn radius-server server auth-port
Description
This command specifies the UDP listening port for RADIUS authentication requests.
The no form of this commands resets the UDP port to its default value (1812)
Default
auth-port 1812
Parameters
- port
-
Specifies the UDP listening port for accounting requests of the external RADIUS server.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auth-request-script-policy
auth-request-script-policy
Syntax
auth-request-script-policy policy-name
no auth-request-script-policy
Context
[Tree] (config>aaa>radius-srv-plcy auth-request-script-policy)
Full Context
configure aaa radius-server-policy auth-request-script-policy
Description
This command specifies the name of the RADIUS script policy used to change the RADIUS attributes of the Access-Request messages.
Parameters
- policy-name
-
Specifies the name of the Python script to modify Access-Request messages, up to 32 characters
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authenticate
authenticate
Syntax
[no] authenticate
Context
[Tree] (config>service>vprn>ntp authenticate)
Full Context
configure service vprn ntp authenticate
Description
This command enables authentication for the NTP server.
Platforms
All
authenticate-client
authenticate-client
Syntax
authenticate-client
Context
[Tree] (config>system>security>tls>server-tls-profile authenticate-client)
Full Context
configure system security tls server-tls-profile authenticate-client
Description
Commands in this context configure client authentication parameters.
Platforms
All
authenticate-on-dhcp
authenticate-on-dhcp
Syntax
[no] authenticate-on-dhcp
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range authenticate-on-dhcp)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range authenticate-on-dhcp)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range authenticate-on-dhcp
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range authenticate-on-dhcp
Description
This command enables initial authentication (when there is no state for the UE on the ISA), to be triggered by DHCP DISCOVER or REQUEST. The default behavior is authentication based on first Layer 3 packet.
The no form of this command reverts to the default.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
authenticated-brg-only
authenticated-brg-only
Syntax
[no] authenticated-brg-only
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>vlan-ranges>range>vrgw>brg authenticated-brg-only)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>brg authenticated-brg-only)
[Tree] (config>service>vprn>sub-if>grp-if>brg authenticated-brg-only)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>vlan-ranges>range>vrgw>brg authenticated-brg-only)
[Tree] (config>service>ies>sub-if>grp-if>brg authenticated-brg-only)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>brg authenticated-brg-only)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-ranges range vrgw brg authenticated-brg-only
configure service vprn subscriber-interface group-interface wlan-gw ranges range brg authenticated-brg-only
configure service vprn subscriber-interface group-interface brg authenticated-brg-only
configure service vprn subscriber-interface group-interface wlan-gw vlan-ranges range vrgw brg authenticated-brg-only
configure service ies subscriber-interface group-interface brg authenticated-brg-only
configure service ies subscriber-interface group-interface wlan-gw ranges range brg authenticated-brg-only
Description
This command indicates that only BRGs that are pre-authenticated using the RADIUS proxy are allowed in this context.
The no form of this command removes the restriction.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication
authentication
Syntax
authentication {chap | pap | pref-chap | prep-pap}
Context
[Tree] (config>router>l2tp>group>ppp authentication)
[Tree] (config>service>vprn>l2tp>group>tunnel>ppp authentication)
[Tree] (config>service>vprn>l2tp>group>ppp authentication)
[Tree] (config>router>l2tp>group>tunnel>ppp authentication)
Full Context
configure router l2tp group ppp authentication
configure service vprn l2tp group tunnel ppp authentication
configure service vprn l2tp group ppp authentication
configure router l2tp group tunnel ppp authentication
Description
This command configures the PPP authentication protocol to negotiate authentication.
Default
authentication pref-chap
Parameters
- chap
-
Specifies to always use CHAP for authentication.
- pap
-
Specifies to always use PAP for authentication.
- pref-chap
-
Specifies to use CHAP as the preferred authentication method, and to use PAP if that attempt fails.
- pref-pap
-
Specifies to use PAP as the preferred authentication method, and to use CHAP if that attempt fails.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication
Syntax
authentication
Context
[Tree] (config>service>dynsvc>policy authentication)
Full Context
configure service dynamic-services dynamic-services-policy authentication
Description
Commands in this context configure authentication parameters for data-triggered dynamic services.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication
Syntax
authentication [policy policy-name] [mac-addr ieee-address] [circuit-id circuit-id]
Context
[Tree] (debug>subscr-mgmt authentication)
Full Context
debug subscriber-mgmt authentication
Description
This command debugs subscriber authentication.
Parameters
- policy-name
-
Specifies an existing subscriber management authentication policy name.
- ieee-address
-
Specifies the 48-bit MAC address xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx.
- circuit-id
-
Specify the circuit-id, up to 256 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication
Syntax
authentication
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range authentication)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range authentication)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range authentication
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range authentication
Description
Commands in this context create configuration for authenticating a user from the WLAN-GW ISA.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
authentication
Syntax
authentication bidirectional sa-name
authentication inbound sa-name outbound sa-name
no authentication
Context
[Tree] (config>service>vprn>ospf3>area>if authentication)
[Tree] (config>service>vprn>ospf3>area>virtual-link authentication)
Full Context
configure service vprn ospf3 area interface authentication
configure service vprn ospf3 area virtual-link authentication
Description
This command configures OPSFv3 confidentiality authentication.
The no form of this command removes the SA name from the configuration.
Parameters
- bidirectional sa-name
-
Specifies the IPsec security association name in case the OSPFv3 traffic on the interface has to be authenticated.
- inbound sa-name
-
Specifies the IPsec security association name in case the OSPFv3 traffic on the interface has to be authenticated.
- outbound sa-name
-
Specifies the IPsec security association name in case the OSPFv3 traffic on the interface has to be authenticated.
Platforms
All
authentication
Syntax
authentication ascii-algorithm ascii-key ascii-string [hash | hash2 | custom]
authentication auth-algorithm hex-key hex-string [hash | hash2 | custom]
no authentication
Context
[Tree] (config>ipsec>static-sa authentication)
Full Context
configure ipsec static-sa authentication
Description
This command configures the authentication algorithm to use for an IPsec manual SA.
Default
no authentication
Parameters
- auth-algorithm
-
Specifies the authentication algorithm to be used.
- ascii-string
-
Specifies an ASCII key; 16 characters for md5 and 20 characters for sha1.
- hex-string
-
Specifies a HEX key; 32 hex nibbles for md5 and 40 hex nibbles for sha1.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication
Syntax
authentication [port udp-port]
no authentication
Context
[Tree] (config>aaa>isa-radius-plcy>servers>server authentication)
Full Context
configure aaa isa-radius-policy servers server authentication
Description
This command configures authentication for this server.
Default
no authentication
Parameters
- udp-port
-
Specifies the UDP port number on which to contact the RADIUS server for authentication.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
authentication
Syntax
[no] authentication
Context
[Tree] (config>li>x-interfaces>lics>lic authentication)
Full Context
configure li x-interfaces lics lic authentication
Description
This command configures the parameters for authentication of INE and LIC on the X1 and X2 interfaces.
The no form of this command removes the configured parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
authentication
Syntax
authentication none
authentication authentication-protocol authentication-key [privacy-none] [hash | hash2 | custom]
authentication authentication-protocol authentication-key privacy privacy-protocol privacy-key [hash | hash2 | custom]
no authentication
Context
[Tree] (config>system>security>user>snmp authentication)
Full Context
configure system security user snmp authentication
Description
This command configures the SNMPv3 authentication and privacy protocols for the user to communicate with the router. The keys are stored in an encrypted format in the configuration.
The keys configured with these commands must be localized keys, which are a hash of the SNMP engine ID and a password. The password is not entered directly in this command. Use the tools perform system management-interface snmp generate-key command to generate localized authentication and privacy keys.
Default
authentication none
Parameters
- none
-
Keyword to specify that no authentication protocol is used. If none is specified, privacy cannot be configured.
- authentication-protocol
-
Specifies the SNMPv3 authentication protocol.
- authentication-key
-
Specifies the localized authentication key, which is entered as a hexadecimal string; the character length depends on the specified authentication protocol. The following table lists the authentication protocol key lengths.
Table 2. Authentication protocol key lengths Authentication protocol
Character lengths
HMAC-MD5-96
32
HMAC-SHA-96
40
HMAC-SHA-224
56
HMAC-SHA-256 64
HMAC-SHA-384
96
HMAC-SHA-512
128
- privacy-none
-
Keyword to specify that a privacy protocol is not used in the communication.
- privacy-protocol
-
Specifies the SNMPv3 privacy protocol.
- privacy-key
-
Specifies the localized privacy key, which is entered as a hexadecimal string; the character length depends on the specified privacy protocol. The following table lists the privacy protocol key lengths.
Table 3. Privacy protocol key lengths Privacy protocol Character length
CBC-DES
32
CFB128-AES-128
32
CFB128-AES-192
48
CFB128-AES-256
64
- hash
-
Keyword that specifies the key is entered in an encrypted form. If the hash or hash2 keyword is not specified, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Keyword that specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone; that is, the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 keyword is not specified, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Keyword that specifies the custom encryption to the management interface.
Platforms
All
authentication
Syntax
authentication bidirectional sa-name
authentication [inbound sa-name outbound sa-name]
no authentication
Context
[Tree] (config>router>ospf3>area>interface authentication)
[Tree] (config>router>ospf3>area>virtual-link authentication)
Full Context
configure router ospf3 area interface authentication
configure router ospf3 area virtual-link authentication
Description
This command configures the password used by the OSPF3 interface or virtual-link to send and receive OSPF3 protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for proper protocol communication.
By default, no authentication key is configured.
The no form of this command removes the authentication.
Default
no authentication
Parameters
- bidirectional sa-name
-
Specifies bidirectional OSPF3 authentication.
- inbound sa-name
-
Specifies the inbound security association (SA) name for OSPF3 authentication.
- outbound sa-name
-
Specifies the outbound SA name for OSPF3 authentication.
Platforms
All
authentication-check
authentication-check
Syntax
[no] authentication-check
Context
[Tree] (config>service>vprn>isis authentication-check)
Full Context
configure service vprn isis authentication-check
Description
This command sets an authentication check to reject PDUs that do not match the type or key requirements for the VPRN instance.
The default behavior when authentication is configured is to reject all IS-IS protocol PDUs that have a mismatch in either the authentication type or authentication key.
When no authentication-check is configured, authentication PDUs are generated and IS-IS PDUs are authenticated on receipt. However, mismatches cause an event to be generated and will not be rejected.
The no form of this command allows authentication mismatches to be accepted and generates a log event.
Default
authentication-check — Rejects authentication mismatches.
Platforms
All
authentication-check
Syntax
[no] authentication-check
Context
[Tree] (config>service>vprn>ntp authentication-check)
Full Context
configure service vprn ntp authentication-check
Description
This command provides the option to skip the rejection of NTP PDUs that do not match the authentication key-id, type or key requirements. The default behavior when authentication is configured is to reject all NTP protocol PDUs that have a mismatch in either the authentication key-id, type or key.
When authentication-check is enabled, NTP PDUs are authenticated on receipt. However, mismatches cause a counter to be increased, one counter for type and one for key-id, one for type, value mismatches. These counters are visible in a show command.
The no form of this command allows authentication mismatches to be accepted; the counters however are maintained.
Default
authentication-check — Rejects authentication mismatches.
Platforms
All
authentication-check
Syntax
[no] authentication-check
Context
[Tree] (config>system>time>ntp authentication-check)
Full Context
configure system time ntp authentication-check
Description
This command provides the option to skip the rejection of NTP PDUs that do not match the authentication key-id, type or key requirements. The default behavior when authentication is configured is to reject all NTP protocol PDUs that have a mismatch in either the authentication key-id, type or key.
When authentication-check is enabled, NTP PDUs are authenticated on receipt. However, mismatches cause a counter to be increased, one counter for type and one for key-id, one for type, value mismatches. These counters are visible in a show command.
The no form of this command allows authentication mismatches to be accepted; the counters however are maintained.
Default
authentication-check
Platforms
All
authentication-check
Syntax
[no] authentication-check
Context
[Tree] (config>router>isis authentication-check)
Full Context
configure router isis authentication-check
Description
This command sets an authentication check to reject PDUs that do not match the type or key requirements.
The default behavior when authentication is configured is to reject all IS-IS protocol PDUs that have a mismatch in either the authentication type or authentication key.
When no authentication-check is configured, authentication PDUs are generated and IS-IS PDUs are authenticated on receipt. However, mismatches cause an event to be generated and will not be rejected.
The no form of this command allows authentication mismatches to be accepted and generates a log event.
Default
authentication-check
Platforms
All
authentication-key
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy authentication-key)
Full Context
configure subscriber-mgmt bgp-peering-policy authentication-key
Description
This command configures the BGP authentication key.
The MD5 message-based digest is used to perform authentication between neighboring routers before setting up the BGP session by verifying the password. The authentication key can be any combination of letters or numbers from 1 to 16.
The no form of this command removes the authentication password from the configuration and effectively disables authentication.
Parameters
- authentication-key
-
Specifies an authentication key. The key can be up to 255 characters (unencrypted).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 342 characters (encrypted).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to the management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>redundancy>multi-chassis>peer authentication-key)
Full Context
configure redundancy multi-chassis peer authentication-key
Description
This command configures the authentication key used between this node and the multi-chassis peer. The authentication key can be any combination of letters or numbers. The no form of the command removes the authentication key.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies the authentication key. Allowed values are any string up to 20 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 33 (hash1-key) or 55 (hash2-key) characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>subscr-mgmt>rip-policy authentication-key)
Full Context
configure subscriber-mgmt rip-policy authentication-key
Description
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD5 message-based digest. The authentication key can be any combination of letters or numbers from 1 to 16.
The no form of this command removes the authentication password from the configuration and effectively disables authentication.
Default
Authentication is disabled and the authentication password is empty.
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of ASCII characters up to 255 characters (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 342 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2| custom]
no authentication-key
Context
[Tree] (config>service>ies>if>vrrp authentication-key)
Full Context
configure service ies interface vrrp authentication-key
Description
The authentication-key command, within the vrrp virtual-router-id context, is used to assign a simple text password authentication key to generate master VRRP advertisement messages and validating received VRRP advertisement messages.
The authentication-key command is one of the few commands not affected by the presence of the owner keyword. If simple text password authentication is not required, the authentication-key command is not required. If the command is re-executed with a different password key defined, the new key will be used immediately. If a no authentication-key command is executed, the password authentication key is restored to the default value. The authentication-key command may be executed at any time.
To change the current in-use password key on multiple virtual router instances:
-
Identify the current master
-
Shutdown the virtual router instance on all backups
-
Execute the authentication-key command on the master to change the password key
-
Execute the authentication-key command and no shutdown command on each backup key
The no form of the command removes the authentication key.
Default
No default. The authentication data field contains the value 0 in all 16 octets.
Parameters
- authentication-key
-
The key parameter identifies the simple text password used when VRRP Authentication Type 1 is enabled on the virtual router instance. Type 1 uses a string eight octets long that is inserted into all transmitted VRRP advertisement messages and compared against all received VRRP advertisement messages. The authentication data fields are used to transmit the key.
The key parameter is expressed as a string consisting up to eight alpha-numeric characters. Spaces must be contained in quotation marks (" ”). The quotation marks are not considered part of the string.
The string is case sensitive and is left-justified in the VRRP advertisement message authentication data fields. The first field contains the first four characters with the first octet (starting with IETF RFC bit position 0) containing the first character. The second field holds the fifth through eighth characters. Any unspecified portion of the authentication data field is padded with the value 0 in the corresponding octet.
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 22 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>bgp>group authentication-key)
[Tree] (config>service>vprn>bgp>group>neighbor authentication-key)
[Tree] (config>service>vprn>bgp authentication-key)
Full Context
configure service vprn bgp group authentication-key
configure service vprn bgp group neighbor authentication-key
configure service vprn bgp authentication-key
Description
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD5 message-based digest. The authentication key can be any combination of letters or numbers from 1 to 16.
The no form of this command removes the authentication password from the configuration and effectively disables authentication.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies an authentication key. The key can be up to 255 characters (unencrypted).
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>if>vrrp authentication-key)
Full Context
configure service vprn interface vrrp authentication-key
Description
The authentication-key command, within the vrrp virtual-router-id context, is used to assign a simple text password authentication key to generate master VRRP advertisement messages and validate received VRRP advertisement messages.
The authentication-key command is one of the few commands not affected by the presence of the owner keyword. If simple text password authentication is not required, this command is not required. If the command is re-executed with a different password key defined, the new key will be used immediately. If a no authentication-key command is executed, the password authentication key is restored to the default value. The authentication-key command may be executed at any time.
To change the current in-use password key on multiple virtual router instances:
-
Identify the current master
-
Shut down the virtual router instance on all backups
-
Execute the authentication-key command on the master to change the password key
-
Execute the authentication-key command and the no shutdown command on each backup key
The no form of this command restores the default null string to the value of key.
Parameters
- authentication-key
-
The key parameter identifies the simple text password used when VRRP Authentication Type 1 is enabled on the virtual router instance. Type 1 uses a string eight octets long that is inserted into all transmitted VRRP advertisement messages and compared against all received VRRP advertisement messages. The authentication data fields are used to transmit the key.
The key parameter is expressed as a string consisting of up to eight alpha-numeric characters. Spaces must be contained in quotation marks ( " ” ). The quotation marks are not considered part of the string.
The string is case sensitive and is left-justified in the VRRP advertisement message authentication data fields. The first field contains the first four characters with the first octet (starting with IETF RFC bit position 0) containing the first character. The second field holds the fifth through eighth characters. Any unspecified portion of the authentication data field is padded with the value 0 in the corresponding octet.
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 22 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”)
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>isis>level authentication-key)
[Tree] (config>service>vprn>isis authentication-key)
Full Context
configure service vprn isis level authentication-key
configure service vprn isis authentication-key
Description
This command sets the authentication key used to verify PDUs sent by neighboring routers on the interface for the VPRN instance.
Neighboring routers use passwords to authenticate PDUs sent from an interface. For authentication to work, both the authentication key and the authentication type on a segment must match. The OSPF Commands statement must also be included.
To configure authentication on the global level, configure this command in the config>router>isis context. When this parameter is configured on the global level, all PDUs are authenticated including the Hello PDU.
To override the global setting for a specific level, configure the authentication-key command in the config>router>isis>level context. When configured within the specific level, hello PDUs are not authenticated.
The no form of this command removes the authentication key.
Default
no authentication-key — No authentication key is configured.
Parameters
- authentication-key
-
The authentication key. The key can be any combination of ASCII characters up to 255 characters in length (un-encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>msdp>peer authentication-key)
[Tree] (config>service>vprn>msdp>group>peer authentication-key)
Full Context
configure service vprn msdp peer authentication-key
configure service vprn msdp group peer authentication-key
Description
This command configures a Message Digest 5 (MD5) authentication key to be used with a specific Multicast Source Discovery Protocol (MSDP) peering session. The authentication key must be configured per peer as such no global or group configuration is possible.
The no form of this command removes the authentication key.
Default
no authentication-key (All MSDP messages are accepted and the MD5 signature option authentication key is disabled.)
Parameters
- authentication-key
-
Specifies the authentication key. Allowed values are any string up to 256 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 451 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key key-id key key [hash | hash2 | custom] type {des | message-digest}
no authentication-key key-id
Context
[Tree] (config>service>vprn>ntp authentication-key)
Full Context
configure service vprn ntp authentication-key
Description
This command sets the authentication key-id, type and key used to authenticate NTP PDUs sent by the broadcast server function toward external clients or to authenticate NTP PDUs received from external unicast clients within the VPRN routing instance. For authentication to work, the authentication key-id, type, and key value must match.
The no form of this command removes the authentication key.
Parameters
- key-id
-
Configure the authentication key-id that will be used by the node when transmitting or receiving Network Time Protocol packets.
Entering the authentication-key command with a key-id value that matches an existing configuration key will result in overriding the existing entry.
Recipients of the NTP packets must have the same authentication key-id, type, and key value in order to use the data transmitted by this node. This is an optional parameter.
- key
-
The authentication key associated with the configured key-id, the value configured in this parameter is the actual value used by other network elements to authenticate the NTP packet.
The key can be any combination of ASCII characters up to 8 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (".”).
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
- type
-
This parameter determines if DES or message-digest authentication is used.
This is a required parameter; either DES or message-digest must be configured.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>ospf>area>if authentication-key)
[Tree] (config>service>vprn>ospf>area>virtual-link authentication-key)
[Tree] (config>service>vprn>ospf>area>sham-link authentication-key)
Full Context
configure service vprn ospf area interface authentication-key
configure service vprn ospf area virtual-link authentication-key
configure service vprn ospf area sham-link authentication-key
Description
This command configures the password used by the OSPF interface or virtual-link to send and receive OSPF protocol packets on the interface when simple password authentication is configured.
This command is not valid in the OSPF3 context.
All neighboring routers must use the same type of authentication and password for proper protocol communication. If the authentication-type is configured as password, then this key must be configured.
By default, no authentication key is configured.
This command is not supported in the OSPF context.
The no form of this command removes the authentication key.
Default
no authentication-key — No authentication key is defined.
Parameters
- authentication-key
-
The authentication key. The key can be any combination of ASCII characters up to 8 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 22 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>service>vprn>rip>group>neighbor authentication-key)
[Tree] (config>service>vprn>rip authentication-key)
[Tree] (config>service>vprn>rip>group authentication-key)
Full Context
configure service vprn rip group neighbor authentication-key
configure service vprn rip authentication-key
configure service vprn rip group authentication-key
Description
This command sets the authentication password to be passed between RIP neighbors.
The authentication type and authentication key must match exactly to authenticate and then process the RIP message.
The no form of this command removes the authentication password from the configuration and disables authentication.
Default
no authentication-key
Parameters
- authentication-key
-
The authentication key. The key can be any combination of ASCII characters up to 16 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 33 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>ldp>tcp-session-params>peer-transport authentication-key)
[Tree] (config>router>ldp>tcp-session-params authentication-key)
Full Context
configure router ldp tcp-session-parameters peer-transport authentication-key
configure router ldp tcp-session-parameters authentication-key
Description
This command specifies the authentication key used to establish a session between LDP peers. Authentication uses the MD5 message-based digest. The peer address used in authentication must be the TCP session transport address. If one or more transport addresses used in the Hello adjacencies to the same peer LSR are different from the LSR-ID value, the user must add each transport address to the authentication-key configuration as a separate peer. As a result, when the TCP connection is bootstrapped by a specific Hello adjacency, the authentication can operate over that TCP connection by using its specific transport address. The per peer authentication configuration takes precedence over global authentication configuration, and authentication keychain configuration takes precedence over authentication key configuration.
The no form of this command disables authentication.
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of ASCII characters, up to 255 characters (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies the hash key. The key can be any combination of up to 33 alphanumeric characters. If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex, encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to the management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>rsvp>interface authentication-key)
Full Context
configure router rsvp interface authentication-key
Description
This command specifies the authentication key for use between RSVP neighbors to authenticate RSVP messages. Authentication uses the MD5 message-based digest.
When enabled on an RSVP interface, authentication of RSVP messages operates in both directions of the interface. A router maintains a security association using one authentication key for each interface to an RSVP neighbor.
An RSVP neighbor transmits an authenticating digest of the RSVP message that is computed using the shared authentication key and a keyed-hash algorithm. The message digest is included in an INTEGRITY object, which also contains a flags field, a key identifier field, and a sequence number field. An RSVP neighbor uses the key together with the authentication algorithm to process received RSVP messages. The RSVP MD5 authentication complies to the procedures for RSVP message generation in RFC 2747, RSVP Cryptographic Authentication.
The MD5 implementation does not support the authentication challenge procedures in RFC 2747.
The no form of this command disables authentication.
Default
no authentication-key - The authentication key value is the null string.
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of ASCII characters up to 16 characters in length (unencrypted). If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
- hash-key
-
Specifies the hash key. The key can be any combination of up 33 alphanumeric characters. If spaces are used in the string, enclose the entire string in quotation marks (" ”)
This is useful when a user must configure the parameter, but for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>msdp>group>peer authentication-key)
[Tree] (config>router>msdp>peer authentication-key)
Full Context
configure router msdp group peer authentication-key
configure router msdp peer authentication-key
Description
This command configures an MD5 authentication key used with a specific MSDP peering session. The authentication key is not inherited from the global or group level and must be configured per peer.
The no form of this command configures acceptance of all MSDP messages and disables the MD5 signature option authentication key.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of printable, 7-bit ASCII characters, up to 255 characters. If the string contains special characters (#, ?, space), enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies a hash key. The key can be any combination of ASCII characters up to 451 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, although, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Keyword that specifies the hash key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Keyword that specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone; that is, the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Keyword that specifies the custom encryption to the management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [{hash | hash2 | custom}]
no authentication-key
Context
[Tree] (config>router>if>vrrp authentication-key)
Full Context
configure router interface vrrp authentication-key
Description
This command sets the simple text authentication key used to generate master VRRP advertisement messages and validates VRRP advertisements.
If simple text password authentication is not required, the authentication-key command is not required.
The command is configurable in both non-owner and owner vrrp nodal contexts.
The key parameter identifies the simple text password to be used when VRRP Authentication Type 1 is enabled on the virtual router instance. Type 1 uses an eight octet long string that is inserted into all transmitted VRRP advertisement messages and is compared against all received VRRP advertisement messages. The authentication data fields are used to transmit the key.
The key string is case sensitive and is left justified in the VRRP advertisement message authentication data fields. The first field contains the first four characters with the first octet (starting with IETF RFC bit position 0) containing the first character. The second field similarly holds the fifth through eighth characters. Any unspecified portion of the authentication data field is padded with a 0 value in the corresponding octet.
If the command is re-executed with a different password key defined, the new key is used immediately.
The authentication-key command can be executed at anytime.
To change the current in-use password key on multiple virtual router instances:
Identify the current master.
-
Shutdown the virtual router instance on all backups.
-
Execute the authentication-key command on the master to change the password key.
-
Execute the authentication-key command and no shutdown command on each backup.
The no form of the command reverts to the default value.
Default
no authentication-key — The authentication key value is the null string.
Parameters
- authentication-key
-
The authentication key. Allowed values are any string up to 8 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
- hash-key
-
The hash key. The key can be any combination of ASCII characters up to 22 (hash-key1) or 121 (hash-key2) characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key key-id key key [hash | hash2 | custom] type {des | message-digest}
no authentication-key key-id
Context
[Tree] (config>system>time>ntp authentication-key)
Full Context
configure system time ntp authentication-key
Description
This command sets the authentication key-id, type and key used to authenticate NTP PDUs sent to or received by other network elements participating in the NTP protocol. For authentication to work, the authentication key-id, type and key value must match.
The no form of the command removes the authentication key.
Parameters
- key-id
-
Configures the authentication key-id that will be used by the node when transmitting or receiving Network Time Protocol packets
Entering the authentication-key command with a key-id value that matches an existing configuration key will result in overriding the existing entry.
Recipients of the NTP packets must have the same authentication key-id, type, and key value in order to use the data transmitted by this node. This is an optional parameter.
- key
-
Specifies the authentication key associated with the configured key-id, the value configured in this parameter is the actual value used by other network elements to authenticate the NTP packet.
The key can be any combination of ASCII characters up to 32 characters for message-digest (md5) or 8 characters for des (length limits are unencrypted lengths). If spaces are used in the string, enclose the entire string in quotation marks (".”).
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
- type
-
Determines if DES or message-digest authentication is used.
This is a required parameter; either DES or message-digest must be configured.
- des
-
Specifies that DES authentication is used for this key.
- message-digest
-
Specifies that MD5 authentication in accordance with RFC 2104 is used for this key.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>bgp>group>neighbor authentication-key)
[Tree] (config>router>bgp authentication-key)
[Tree] (config>router>bgp>group authentication-key)
Full Context
configure router bgp group neighbor authentication-key
configure router bgp authentication-key
configure router bgp group authentication-key
Description
This command configures the BGP authentication key.
Authentication is performed between neighboring routers before setting up the BGP session by verifying the password. Authentication is performed using the MD5 message based digest.
The no form of this command reverts to the default value.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies an authentication key. The key can be up to 255 characters (unencrypted).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>isis>level authentication-key)
[Tree] (config>router>isis authentication-key)
Full Context
configure router isis level authentication-key
configure router isis authentication-key
Description
This command sets the authentication key used to verify PDUs sent by neighboring routers on the interface.
Neighboring routers use passwords to authenticate PDUs sent from an interface. For authentication to work, both the authentication key and the authentication type on a segment must match. The authentication-type command must also be included.
To configure authentication on the global level, configure this command in the config>router>isis context. When this parameter is configured on the global level, all PDUs are authenticated, including the hello PDU.
To override the global setting for a specific level, configure the authentication-key command in the config>router>isis>level context. When configured within the specific level, hello PDUs are not authenticated.
The no form of this command removes the authentication key.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of ASCII characters up to 255 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key [authentication-key | hash-key] [hash | hash2 | custom]
no authentication-key
Context
[Tree] (config>router>ospf>area>virtual-link authentication-key)
[Tree] (config>router>ospf>area>interface authentication-key)
Full Context
configure router ospf area virtual-link authentication-key
configure router ospf area interface authentication-key
Description
This command configures the password used by the OSPF interface or virtual link to send and receive OSPF protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for proper protocol communication. If authentication-type password is configured, this key must be configured.
By default, no authentication key is configured.
The no form of this command removes the authentication key.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies the authentication key. The key can be any combination of ASCII characters up to 8 characters in length (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 22 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-key
Syntax
authentication-key {authentication-key | hash-key} [{hash | hash2 | custom}]
no authentication-key
Context
[Tree] (config>router>rip>group authentication-key)
[Tree] (config>router>rip authentication-key)
[Tree] (config>router>rip>group>neighbor authentication-key)
Full Context
configure router rip group authentication-key
configure router rip authentication-key
configure router rip group neighbor authentication-key
Description
This command sets the authentication password to be passed between RIP neighbors.
The authentication type and authentication key must match exactly for the RIP message to be considered authentic and processed.
The no form of the command removes the authentication password from the configuration and disables authentication.
Default
no authentication-key
Parameters
- authentication-key
-
Specifies the authentication key. Allowed values are any string up to 16 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.
- hash-key
-
Specifies the hash key. The key can be any combination of ASCII characters up to 33 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
- hash
-
Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- hash2
-
Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the custom encryption to management interface.
Platforms
All
authentication-keychain
authentication-keychain
Syntax
authentication-keychain keychain-name
no authentication-keychain
Context
[Tree] (config>system>time>ntp authentication-keychain)
Full Context
configure system time ntp authentication-keychain
Description
This command configures the authentication keychain used to handle unsolicited NTP requests.
If the system receives a request with a key ID that matches both the configured key and the keychain, the system checks the MAC ID using the key information first. If the key authentication fails, the system then checks the MAC ID using the information from the keychain.
The no form of the command removes the authentication keychain.
Parameters
- keychain-name
-
Specifies the keychain name, up to 32 characters.
Platforms
All
authentication-keychain
Syntax
authentication-keychain keychain-name
no authentication-keychain
Context
[Tree] (config>service>vprn>ntp authentication-keychain)
Full Context
configure service vprn ntp authentication-keychain
Description
This command configures the authentication keychain used to handle unsolicited NTP requests.
If the system receives a request with a key ID that matches both the configured key and the keychain, the system checks the MAC ID using the key information first. If the key authentication fails, the system then checks the MAC ID using the information from the keychain.
The no form of the command removes the authentication keychain.
Parameters
- keychain-name
-
Specifies the keychain name, up to 32 characters.
Platforms
All
authentication-method
authentication-method
Syntax
authentication-method
Context
[Tree] (config>system>security>ssh authentication-method)
Full Context
configure system security ssh authentication-method
Description
Commands in this context configure at the system level the SSH authentication method.
Platforms
All
authentication-order
authentication-order
Syntax
authentication-order [method-1] [method-2] [method-3] [method-4] [exit-on-reject]
no authentication-order
Context
[Tree] (config>system>security>password authentication-order)
Full Context
configure system security password authentication-order
Description
This command configures the sequence in which the system attempts authentication and authorization among the local user database, RADIUS servers, TACACS+ servers, and LDAP servers.
Configure the order from the most preferred method to the least preferred. The presence of all methods in the command line does not guarantee they are all operational. Specifying options that are not available delays user authentication.
If all operational methods are attempted and no authentication for a particular login has been granted, an entry in the security log records the failed attempt. Both the attempted login identification and originating IP address are logged with a timestamp.
The no form of this command reverts to the default order.
The order is not applicable to SNMPv3. SNMPv3 messages ignore the configured order and are authorized using the locally configured users only. TACACS+, RADIUS, and LDAP are not supported for SNMPv3 authentication.
This command applies to a local user, in addition to users on RADIUS, TACACS+, and LDAP.
Default
authentication-order radius tacplus ldap local
Parameters
- method-1
-
Specifies the first password authentication method to attempt.
- method-2
-
Specifies the second password authentication method to attempt.
- method-3
-
Specifies the third password authentication method to attempt.
- method-4
-
Specifies the fourth password authentication method to attempt.
- local
-
Specifies the password authentication based on the local password database.
- radius
-
Specifies RADIUS authentication.
- tacplus
-
Specifies TACACS+ authentication.
- ldap
-
Specifies LDAP authentication.
- exit-on-reject
-
When this parameter is configured, the router stops authentication and authorization if one of the AAA methods configured in the order sends a rejection.
When this parameter is not configured, the router attempts the next AAA method if a AAA method sends a rejection. If all AAA methods are exhausted, authentication and authorization are rejected.
If the order specifies local as the first method, the following actions apply:
- If this parameter is configured and the user does not exist, the user is not authenticated.
- If the user can be authenticated locally, other methods, if configured, are used for authorization and accounting.
- If the user is configured locally but without console access, login is denied.
Platforms
All
authentication-origin
authentication-origin
Syntax
authentication-origin
Context
[Tree] (config>subscr-mgmt authentication-origin)
Full Context
configure subscriber-mgmt authentication-origin
Description
Commands in this context configure a subscriber’s authentication origin.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-over-bypass
authentication-over-bypass
Syntax
authentication-over-bypass [enable | disable]
Context
[Tree] (config>router>rsvp authentication-over-bypass)
Full Context
configure router rsvp authentication-over-bypass
Description
This command configures the MD5 authentication over the bypass LSP of all Point of Local Repairs (PLRs) and Merge Points (MPs) on the router. Only enable this command when the TE interfaces in the RSVP-TE network use the same MD5 authentication parameters.
When a Point of Local Repair (PLR) activates a bypass LSP towards a Merge Point (MP), by default, the INTEGRITY object corresponding to the bypass LSP interface is not added to a transmitted RSVP message except for packets of routed RSVP messages (Resv, Srefresh, and ACK), and only when the packet is intended for a bypass LSP endpoint (PLR or MP) that is a directly connected neighbor.
When this command is enabled, the INTEGRITY object of the interface corresponding to the bypass LSP is added to a transmitted RSVP message regardless of whether the bypass LSP endpoint (PLR or MP) is a directly connected RSVP neighbor. The INTEGRITY object is included with the following RSVP messages: Path, PathTear, PathErr, Resv, ResvTear, ResvErr, Srefresh, and ACK.
In all cases, an RSVP message received from a PLR or a MP (sender address in the SenderTemplate/FilterSpec is different from an Extended Tunnel Id in a Session Object), and which includes the INTEGRITY object is authenticated against the bypass LSP interface. An RSVP message received from a PLR or MP without the INTEGRITY object is also accepted.
Default
authentication-over-bypass disable
Parameters
- enable
-
Enables the MD5 authentication over the bypass LSP of all PLRs on the node.
- disable
-
Disables the MD5 authentication over the bypass LSP of all PLRs on the node.
Platforms
All
authentication-policy
authentication-policy
Syntax
authentication-policy auth-policy-name
no authentication-policy
Context
[Tree] (config>router>l2tp>group>ppp authentication-policy)
[Tree] (config>router>l2tp>group>tunnel>ppp authentication-policy)
[Tree] (config>service>vprn>l2tp>group>tunnel>ppp authentication-policy)
[Tree] (config>service>vprn>l2tp>group>ppp authentication-policy)
Full Context
configure router l2tp group ppp authentication-policy
configure router l2tp group tunnel ppp authentication-policy
configure service vprn l2tp group tunnel ppp authentication-policy
configure service vprn l2tp group ppp authentication-policy
Description
This command configures the RADIUS authentication policy that will be used to authenticate PPP sessions on the LNS.
The no form of this command reverts to the default value.
Default
no authentication-policy
Parameters
- auth-policy-name
-
Specifies the authentication policy name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-policy
Syntax
authentication-policy name [create]
no authentication-policy
Context
[Tree] (config>subscr-mgmt authentication-policy)
Full Context
configure subscriber-mgmt authentication-policy
Description
This command creates a RADIUS authentication policy containing parameters to authenticate subscriber sessions. The policies can be applies to an IES or VPRN interface or group interface, or a VPLS SAP.
The no form of this command removes the policy from the configuration.
Parameters
- name
-
Specifies the name of the authentication profile. The string is case sensitive and limited to 32 ASCII 7-bit printable characters.
- create
-
Keyword used to create the authentication policy. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-policy
Syntax
authentication-policy name
no authentication-policy
Context
[Tree] (config>service>vprn>sub-if>grp-if authentication-policy)
[Tree] (config>service>ies>if authentication-policy)
[Tree] (config>service>vprn>if authentication-policy)
[Tree] (config>service>ies>sub-if>grp-if authentication-policy)
Full Context
configure service vprn subscriber-interface group-interface authentication-policy
configure service ies interface authentication-policy
configure service vprn interface authentication-policy
configure service ies subscriber-interface group-interface authentication-policy
Description
This command assigns a RADIUS authentication policy to the interface.
The no form of this command removes the policy from the interface configuration.
Parameters
- name
-
Specifies the authentication policy name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface group-interface authentication-policy
- configure service ies subscriber-interface group-interface authentication-policy
All
- configure service vprn interface authentication-policy
- configure service ies interface authentication-policy
authentication-policy
Syntax
authentication-policy name
no authentication-policy
Context
[Tree] (config>service>vpls>sap authentication-policy)
Full Context
configure service vpls sap authentication-policy
Description
For a regular SAP (bridged CO model), this command defines which subscriber authentication policy must be applied when a DHCP message is received on the interface. The authentication policies must already be defined. The policy is only applied when DHCP snooping is enabled on the SAP.
For a capture SAP, this command specifies the RADIUS authentication policy to use for subscriber session authentication when a valid trigger packet is received. The same authentication policy must be assigned on the group-interface where the MSAP for the subscriber session is created.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-policy
Syntax
authentication-policy policy-name
no authentication-policy
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>authentication authentication-policy)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>authentication authentication-policy)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range authentication authentication-policy
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range authentication authentication-policy
Description
This command assigns a RADIUS authentication policy configured under the aaa context for authenticating users on WLAN-GW ISA.
The no form of this command removes the policy from the configuration.
Parameters
- policy-name
-
Specifies the name of the authentication policy up to 32 characters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
authentication-policy
Syntax
authentication-policy name
no authentication-policy
Context
[Tree] (config>app-assure>group>transit-ip>radius authentication-policy)
Full Context
configure application-assurance group transit-ip-policy radius authentication-policy
Description
This command configures the RADIUS authentication-policy for the IP transit policy.
Default
no authentication-policy
Parameters
- name
-
Specifies the authentication policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
authentication-type
authentication-type
Syntax
authentication-type {none | password | message-digest | message-digest-20}
no authentication-type
Context
[Tree] (config>subscr-mgmt>rip-plcy authentication-type)
Full Context
configure subscriber-mgmt rip-policy authentication-type
Description
This command sets the type of authentication to be used between RIP neighbors. The type and password must match exactly for the RIP message to be considered authentic and processed.
The no form of this command removes the authentication type from the configuration and effectively disables authentication.
Parameters
- none
-
Disables authentication at a given level (global, group, neighbor). If the command does not exist in the configuration, the parameter is inherited.
- password
-
Specifies enable simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
- message-digest
-
Configures 16 byte message digest for MD5 authentication. If this option is configured, then at least one message-digest-key must be configured.
- message-digest-20
-
Configures 20 byte message digest for MD5 authentication in accordance with RFC 2082, RIP-2 MD5 Authentication. If this option is configured, then at least one message-digest-key must be configured.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
authentication-type
Syntax
authentication-type {password | message-digest}
no authentication
Context
[Tree] (config>service>vprn>isis>level authentication-type)
[Tree] (config>service>vprn>isis authentication-type)
Full Context
configure service vprn isis level authentication-type
configure service vprn isis authentication-type
Description
This command enables either simple password or message digest authentication or must go in either the global IS-IS or IS-IS level context.
Both the authentication key and the authentication type on a segment must match. The authentication-key statement must also be included.
Configure the authentication type on the global level in the config>router>isis context.
Configure or override the global setting by configuring the authentication type in the config>router>isis>level context.
The no form of this command disables authentication.
Default
no authentication-type — No authentication type is configured and authentication is disabled.
Parameters
- password
-
Specifies that simple password (plain text) authentication is required.
- message-digest
-
Specifies that MD5 authentication in accordance with RFC 2104 is required.
Platforms
All
authentication-type
Syntax
authentication-type {password | message-digest}
no authentication-type
Context
[Tree] (config>service>vprn>ospf>area>sham-link authentication-type)
[Tree] (config>service>vprn>ospf>area>if authentication-type)
[Tree] (config>service>vprn>ospf>area>virtual-link authentication-type)
Full Context
configure service vprn ospf area sham-link authentication-type
configure service vprn ospf area interface authentication-type
configure service vprn ospf area virtual-link authentication-type
Description
This command enables authentication and specifies the type of authentication to be used on the OSPF interface, virtual-link, and sham-link.
This command is not valid in the OSPF3 context.
Both simple password and message-digest authentication are supported.
The no form of this command disables authentication on the interface.
Default
no authentication-type — No authentication is enabled on an interface.
Parameters
- password
-
This keyword enables simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
- message-digest
-
This keyword enables message digest MD5 authentication in accordance with RFC 1321. If this option is configured, then at least one message-digest-key must be configured.
Platforms
All
authentication-type
Syntax
authentication-type {none | password | message-digest | message-digest-20}
no authentication-type
Context
[Tree] (config>service>vprn>rip>group>neighbor authentication-type)
[Tree] (config>service>vprn>rip>group authentication-type)
[Tree] (config>service>vprn>rip authentication-type)
Full Context
configure service vprn rip group neighbor authentication-type
configure service vprn rip group authentication-type
configure service vprn rip authentication-type
Description
This command defines the type of authentication used between RIP neighbors. The type and password must match exactly to authenticate and then process the RIP message.
The no form of this command removes the authentication type from the configuration and effectively disables authentication.
Default
no authentication-type
Parameters
- none
-
No authentication is used.
- password
-
A simple cleartext password is sent.
- message-digest
-
MD5 authentication is used.
- message-digest-20
-
MD20 authentication is used.
Platforms
All
authentication-type
Syntax
authentication-type {password | message-digest}
no authentication
Context
[Tree] (config>router>isis>level authentication-type)
[Tree] (config>router>isis authentication-type)
Full Context
configure router isis level authentication-type
configure router isis authentication-type
Description
This command enables either simple password or message digest authentication or must go in either the global IS-IS or IS-IS level context.
Both the authentication key and the authentication type on a segment must match. The authentication-key statement must also be included.
Configure the authentication type on the global level in the config>router>isis context.
Configure or override the global setting by configuring the authentication type in the config>router>isis>level context.
The no form of this command disables authentication.
Parameters
- password
-
Specifies that simple password (plain text) authentication is required.
- message-digest
-
Specifies that MD5 authentication in accordance with RFC 2104 is required.
Platforms
All
authentication-type
Syntax
authentication-type {password | message-digest}
no authentication-type
Context
[Tree] (config>router>ospf>area>interface authentication-type)
[Tree] (config>router>ospf>area>virtual-link authentication-type)
Full Context
configure router ospf area interface authentication-type
configure router ospf area virtual-link authentication-type
Description
This command enables authentication and specifies the type of authentication to be used on the OSPF interface.
Both simple password and message-digest authentication are supported.
By default, authentication is not enabled on an interface.
The no form of this command disables authentication on the interface.
Default
no authentication-type
Parameters
- password
-
Enables the simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
- message-digest
-
Enables message digest MD5 authentication in accordance with RFC 1321. If this option is configured, then at least one message-digest-key must be configured.
Platforms
All
authentication-type
Syntax
authentication-type {none | password | message-digest | message-digest-20}
no authentication-type
Context
[Tree] (config>router>rip>group authentication-type)
[Tree] (config>router>rip authentication-type)
[Tree] (config>router>rip>group>neighbor authentication-type)
Full Context
configure router rip group authentication-type
configure router rip authentication-type
configure router rip group neighbor authentication-type
Description
This command sets the type of authentication to be used between RIP neighbors.
The type and password must match exactly for the RIP message to be considered authentic and processed.
The no form of the command removes the authentication type from the configuration and effectively disables authentication.
Default
no authentication-type
Parameters
- none
-
The none parameter explicitly disables authentication at a given level (global, group, neighbor). If the command does not exist in the configuration, the parameter is inherited.
- password
-
Specifies that the password enables simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
- message-digest
-
Configures 16 byte message digest for MD5 authentication. If this option is configured, then at least one message-digest-key must be configured.
- message-digest-20
-
Configures 20 byte message digest for MD5 authentication in accordance with RFC 2082, RIP-2 MD5 Authentication. If this option is configured, then at least one message-digest-key must be configured.
Platforms
All
authenticator-init
authenticator-init
Syntax
[no] authenticator-init
Context
[Tree] (config>port>ethernet>dot1x>per-host-authentication authenticator-init)
Full Context
configure port ethernet dot1x per-host-authentication authenticator-init
Description
This command configures the authenticator-initiated mode of the host.
The no form of this command disables the authenticator-initiated mode of the host.
Default
authenticator-init
Platforms
All
authorization
authorization
Syntax
authorization
Context
[Tree] (config>system>security>cli-script authorization)
Full Context
configure system security cli-script authorization
Description
Commands in this context authorize CLI script execution.
Platforms
All
authorization
Syntax
[no] authorization
Context
[Tree] (config>service>vprn>aaa>rmt-srv>radius authorization)
[Tree] (config>system>security>radius authorization)
Full Context
configure service vprn aaa remote-servers radius authorization
configure system security radius authorization
Description
This command configures RADIUS authorization parameters.
The no form of this command removes RADIUS authorization parameters from the configuration.
Default
no authorization
Platforms
All
authorization
Syntax
authorization [use-priv-lvl]
no authorization
Context
[Tree] (config>service>vprn>aaa>rmt-srv>tacplus authorization)
[Tree] (config>system>security>tacplus authorization)
Full Context
configure service vprn aaa remote-servers tacplus authorization
configure system security tacplus authorization
Description
This command configures TACACS+ command authorization parameters.
If this command is enabled without the use-priv-lvl option, each command is sent to the TACACS+ server for authorization (this is true whether the tacplus use-default-template setting is enabled or not).
If the tacplus authorization command is disabled, and the tacplus use-default-template setting is enabled, the local profile in the user-template tacplus_default is used for command authorization.
The no form of this command removes authorization parameters from the configuration.
Default
no authorization
Parameters
- use-priv-lvl
-
Specifies to automatically perform a single authorization request to the TACACS+ server for cmd* (all commands) immediately after login, and then use the local profile associated (via the priv-lvl-map command) with the privilege level returned by the TACACS+ server for all subsequent authorization (except enable-admin). After the initial authorization for cmd*, no further authorization requests are sent to the TACACS+ server (except enable-admin). If the TACACS+ server does not return a privilege level for a user, the profile from the user-template tacplus_default is used for command authorization (as long as tacplus use-default-template is enabled, otherwise all commands are rejected).
Platforms
All
authorized-only
authorized-only
Syntax
[no] authorized-only
Context
[Tree] (config>subscr-mgmt>wlan-gw>ue-query>state authorized-only)
Full Context
configure subscriber-mgmt wlan-gw ue-query state authorized-only
Description
This command enables matching on UEs in an authorized state.
The no form of this command disables matching on UEs in an authorized state, unless all state matching is disabled.
Default
no authorized-only
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
auto-bandwidth
auto-bandwidth
Syntax
[no] auto-bandwidth
Context
[Tree] (config>router>mpls>lsp auto-bandwidth)
[Tree] (config>router>mpls>lsp-template auto-bandwidth)
Full Context
configure router mpls lsp auto-bandwidth
configure router mpls lsp-template auto-bandwidth
Description
This command enables (and the no form disables) automatic adjustments of LSP bandwidth.
Auto-bandwidth at the LSP level cannot be executed unless adaptive is configured in the config>router>mpls>lsp context.
Default
no auto-bandwidth
Platforms
All
auto-bandwidth-multipliers
auto-bandwidth-multipliers
Syntax
auto-bandwidth-multipliers sample-multiplier number1 adjust-multiplier number2
no auto-bandwidth-multipliers
Context
[Tree] (config>router>mpls auto-bandwidth-multipliers)
Full Context
configure router mpls auto-bandwidth-multipliers
Description
This command specifies the number of collection intervals in the adjust interval.
Default
auto-bandwidth-multipliers sample-multiplier 1 adjust-multiplier 288
Parameters
- sample-multiplier number1
-
Specifies the multiplier for collection intervals in a sample interval.
- adjust-multiplier number2
-
Specifies the number of collection intervals in the adjust interval.
Platforms
All
auto-bind-tunnel
auto-bind-tunnel
Syntax
auto-bind-tunnel
Context
[Tree] (config>service>vpls>bgp-evpn>mpls auto-bind-tunnel)
[Tree] (config>service>epipe>bgp-evpn>mpls auto-bind-tunnel)
[Tree] (config>service>vprn>bgp-ipvpn>mpls auto-bind-tunnel)
[Tree] (config>service>vprn>bgp-evpn>mpls auto-bind-tunnel)
Full Context
configure service vpls bgp-evpn mpls auto-bind-tunnel
configure service epipe bgp-evpn mpls auto-bind-tunnel
configure service vprn bgp-ipvpn mpls auto-bind-tunnel
configure service vprn bgp-evpn mpls auto-bind-tunnel
Description
Commands in this context configure automatic binding of a VPRN service using tunnels to MP-BGP peers.
The auto-bind-tunnel node is simply a context to configure the binding of BGP IPVPN or EVPN routes to tunnels. The user must configure the resolution option to enable auto-bind resolution to tunnels in TTM. If the resolution option is explicitly set to disabled, the auto-binding to tunnel is removed.
If resolution is set to any, any supported tunnel type in the Epipe/VPRN/VPLS context is selected following TTM preference. If one or more explicit tunnel types are specified using the resolution-filter option, then only these tunnel types are selected again following the TTM preference.
The user must set resolution to filter in order to activate the list of tunnel-types configured under resolution-filter.
In VPRN services and for BGP-IPVPN, when an explicit SDP to a BGP next hop is configured (config>service>vprn>spoke-sdp), it overrides the auto-bind-tunnel selection for that BGP next hop only. There is no support for reverting automatically to the auto-bind-tunnel selection if the explicit SDP goes down. The user must delete the explicit spoke-sdp in the VPRN service context to resume using the auto-bind-tunnel selection for the BGP next hop.
Platforms
All
auto-bind-tunnel
Syntax
auto-bind-tunnel
Context
[Tree] (config>service>vprn auto-bind-tunnel)
Full Context
configure service vprn auto-bind-tunnel
Description
Platforms
All
auto-boot
auto-boot
Syntax
auto-boot [management-port] [inband [ vlan vlan-id | vlan-discovery]] [ipv4] [ipv6] [client-identifier {string ascii-string | hex hex-string | chassis-mac}] [include-user-class] [timeout minutes]
auto-boot ospf [neid neid-hex-string] [vendor-id vendor-id] [neip-ipv4 ip-address] [neip-ipv6 ipv6-address] [port-mtu mtu-bytes] [ospf-mtu ip-mtu-bytes] [vlan vlan-id] [timeout minutes]
no auto-boot
Context
[Tree] (bof auto-boot)
Full Context
bof auto-boot
Description
This command enables the auto-boot flag in the BOF and configures the auto-boot options for ZTP. When modifying auto-boot options using CLI, all required options must be explicitly configured, as the default cases will no longer be used.
The no form of this command disables the auto-boot flag.
Default
no auto-boot
Parameters
- management-port
-
Specifies that the out-of-band management port (Mgmt port) should be used for ZTP.
- inband
-
Specifies that in-band management through an Ethernet port should be used for ZTP. Unless the vlan-discovery flag is used, the inband option disables VLAN discovery.
- vlan-id
-
Specifies an in-band VLAN to use for the auto-boot process.
- vlan-discovery
-
Floods all VLANs (1 to 4094) with DHCP discovery messages and is supported only on inband ports. The first offer received on a specific VLAN is processed.
- ipv4
-
Enables IPv4 DHCP discovery. This parameter is mandatory if the ipv6 parameter is not specified.
- ipv6
-
Enables IPv6 DHCP solicitation. This parameter is mandatory if the ipv4 parameter is not specified.
- ascii-string
-
Specifies a DHCP client identification string, up to 58 ASCII characters, to be used for Option 61 (IPv4) or Option 1 (IPv6).
- hex-string
-
Specifies a DHCP client identification string, up to 116 hexadecimal nibbles, to be used for Option 61 (IPv4) or Option 1 (IPv6).
- chassis-mac
-
Specifies that the chassis MAC address should be used as the DHCP client identification string for Option 61 (IPv4) or Option 1 (IPv6).
- include-user-class
-
Specifies that Option 77 should be included in DHCP messages.
- client-identifier
-
Specifies that a custom client ID should be used in network discovery requests.
- minutes
-
Specifies the time interval after which, if the auto-boot process is unsuccessful (in the case of auto-boot using OSPF, if no OSPF adjacency is found), the node is rebooted and the auto-boot process is retried.
- ospf
-
Specifies that OSPF auto-discovery should be used.
- neid-hex-string
-
Specifies a hexadecimal network element identification string.
- ip-address
-
Specifies the IPv4 address for the network element.
- ipv6-address
-
Specifies the IPv6 address for the network element.
- vendor-id
-
Specifies the vendor identification number. The number 140 corresponds to "Nokia”.
- ip-mtu-bytes
-
Specifies the OSPF MTU in bytes.
- mtu-bytes
-
Specifies the port MTU in bytes.
Platforms
7450 ESS-7, 7750 SR-1, 7750 SR-7, 7750 SR-1e, 7750 SR-2e, 7750 SR-s
auto-config
auto-config
Syntax
[no] auto-config
Context
[Tree] (config>service>epipe>spoke-sdp-fec auto-config)
Full Context
configure service epipe spoke-sdp-fec auto-config
Description
This command enables single sided automatic endpoint configuration of the spoke SDP. The router acts as the passive T-PE for signaling this MS-PW.
Automatic Endpoint Configuration allows the configuration of a spoke SDP endpoint without specifying the TAII associated with that spoke SDP. It allows a single-sided provisioning model where an incoming label mapping message with a TAII that matches the SAII of that spoke SDP to be automatically bound to that endpoint. In this mode, the far end T-PE actively initiates MS-PW signaling and will send the initial label mapping message using T-LDP, while the router T-PE for which auto-config is specified will act as the passive T-PE.
The auto-config command is blocked in CLI if signaling active has been enabled for this spoke SDP. It is only applicable to spoke SDPs configured under the Epipe, IES and VPRN interface context.
The no form of this command means that the router T-PE either acts as the active T-PE (if signaling active is configured) or automatically determines which router will initiate MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke SDP. If the SAII has the greater prefix value, then the router will initiate MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, then the router will assume that the far end T-PE will initiate MS-PW signaling and will wait for that label mapping message before responding with a T-LDP label mapping message for the MS-PW in the reverse direction.
Default
no auto-config
Platforms
All
auto-config-save
auto-config-save
Syntax
[no] auto-config-save
Context
[Tree] (config>system>management-interface>cli>md-cli auto-config-save)
Full Context
configure system management-interface cli md-cli auto-config-save
Description
This command enables the functionality to automatically write the running configuration to the saved configuration file as part of a successful MD-CLI commit operation.
The no form of this command disables this functionality.
Default
auto-config-save
Platforms
All
auto-config-save
Syntax
[no] auto-config-save
Context
[Tree] (config>system>netconf auto-config-save)
Full Context
configure system netconf auto-config-save
Description
This command enables the functionality to automatically write the running configuration to the saved configuration file as part of a successful NETCONF or pySROS commit operation.
The no form of this command disables this functionality.
Default
auto-config-save
Platforms
All
auto-config-save
Syntax
[no] auto-config-save
Context
[Tree] (config>system>grpc>gnmi auto-config-save)
Full Context
configure system grpc gnmi auto-config-save
Description
This command enables the functionality to automatically write the running configuration to the saved configuration file as part of a successful gNMI commit operation.
The no form of this command disables this functionality.
Default
auto-config-save
Platforms
All
auto-creation
auto-creation
Syntax
[no] auto-creation
Context
[Tree] (config>qos>fp-resource-policy>aggregate-shapers auto-creation)
Full Context
configure qos fp-resource-policy aggregate-shapers auto-creation
Description
This command enables the auto-creation of hardware aggregate shapers on the specified FP. After enabling, the corresponding FP is rebooted.
The no version of this command disables auto-creation of hardware aggregate shapers.
Default
no auto-creation
Platforms
7750 SR-1, 7750 SR-s
auto-crl-update
auto-crl-update
Syntax
auto-crl-update [create]
no auto-crl-update
Context
[Tree] (config>system>security>pki>ca-prof auto-crl-update)
Full Context
configure system security pki ca-profile auto-crl-update
Description
This command creates an auto CRL update configuration context with the create parameter, or enters the auto-crl-update configuration context without the create parameter.
This mechanism auto downloads a CRL file from a list of configured HTTP URLs either periodically or before existing CRL expires. If the downloaded CRL is more recent than the existing one, then the existing one will be replaced.
The configured URL must point to a DER encoded CRL file.
Parameters
- create
-
Creates an auto CRL update for the ca-profile.
Platforms
All
auto-crl-update
Syntax
[no] auto-crl-update
Context
[Tree] (debug>certificate auto-crl-update)
Full Context
debug certificate auto-crl-update
Description
This command enables trace for automated and manual CRL updates.
Platforms
All
auto-disc-route-advertisement
auto-disc-route-advertisement
Syntax
[no] auto-disc-route-advertisement
Context
[Tree] (config>service>vpls>bgp-evpn>vxlan auto-disc-route-advertisement)
Full Context
configure service vpls bgp-evpn vxlan auto-disc-route-advertisement
Description
This command enables sending route advertisements on auto-discovery.
The no form of this command disables sending route advertisements on auto-discovery.
Default
no auto-disc-route-advertisement
Platforms
All
auto-discovery
auto-discovery
Syntax
auto-discovery [default | mdt-safi] [source-address ip-address]
Context
[Tree] (config>service>vprn>mvpn auto-discovery)
Full Context
configure service vprn mvpn auto-discovery
Description
This command enables MVPN membership auto-discovery through BGP. When auto-discovery is enabled, PIM peering on the inclusive provider tunnel is disabled. Changing auto-discovery configuration requires shutdown of this VPRN instance.
The no form of this command disables MVPN membership auto-discovery through BGP.
Default
auto-discovery default
Parameters
- default
-
Enables AD route exchange based on format defined in NG-MVPN (RFC 6514).
- mdt-safi
-
Keyword to enable AD route exchange based on the MDT-SAFI format, as described in draft-rosen-vpn-mcast.
This command optionally specifies a source IP address to be used by Rosen MVPN or NG-MVPN for core diversity, non-default IGP instances (not using system IP). Two unique IP addresses for PIM or GRE MVPNs are supported. The two unique IP address restriction does not apply to MVPNs with MPLS tunnels (for example, RSVP and MLDP). For instances using default System IP, source address configuration should not be specified to avoid consuming one of the addresses.
Explicitly defining a source address allows GRE-encapsulated Rosen MVPN or NG-MVPN multicast traffic (Default and Data MDT) to originate from a configured IP address, so the source IP address of the GRE packets is not the default system IP address.
- ip-address
-
Specifies an IPv4 address. To achieve the desired functionality, the address should be a pre-configured, non-default IS-IS or OSPF loopback address for an IGP instance using a loopback address different from the system IP loopback.
Platforms
All
auto-discovery
Syntax
auto-discovery [default]
no auto-discovery
Context
[Tree] (config>router>pim>gtm auto-discovery)
Full Context
configure router pim gtm auto-discovery
Description
This command enables multicast auto-discovery over BGP for GTM.
The no form of this command disables auto-discovery.
Default
no auto-discovery
Parameters
- default
-
Enables the default auto-discovery mode.
Platforms
All
auto-discovery-disable
auto-discovery-disable
Syntax
[no] auto-discovery-disable
Context
[Tree] (config>service>vprn>mvpn>pt>selective auto-discovery-disable)
Full Context
configure service vprn mvpn provider-tunnel selective auto-discovery-disable
Description
This command disables C-trees to P-tunnel binding auto-discovery through BGP so it is signaled using PIM join TLVs.
This command requires the c-mcast-signaling parameter to be set to PIM.
For multi-stream S-PMSI, this command must be enabled for BGP auto-discovery to function.
The no form of this command enables multicast VPN membership auto-discovery through BGP.
Default
auto-discovery-disable
Platforms
All
auto-eap-method
auto-eap-method
Syntax
auto-eap-method {psk | cert | psk-or-cert}
Context
[Tree] (config>ipsec>ike-policy auto-eap-method)
Full Context
configure ipsec ike-policy auto-eap-method
Description
This command enables following behavior for IKEv2 remote-access tunnel when auth-method is configured as auto-eap-radius:
-
If there is no AUTH payload in IKE_AUTH request, then system use EAP to authenticate client and also will own-auth-method to generate AUTH payload.
-
If there is AUTH payload in IKE_AUTH request:
-
if auto-eap-method is psk, then system proceed as auth-method:psk-radius
-
if auto-eap-method is cert, then system proceed as auth-method:cert-radius
-
if auto-eap-method is psk-or-cert, then:
-
if the "Auth Method" field of AUTH payload is PSK, then system proceed as auth-method:psk-radius
-
if the "Auth Method" field of AUTH payload is RSA or DSS, then system proceed as auth-method:cert-radius
-
-
The system will use auto-eap-own-method to generate AUTH payload.
-
This command only applies when auth-method is configured as auto-eap-radius.
Default
auto-eap-method cert
Parameters
- psk
-
Uses the pre-shared-key as the authentication method.
- cert
-
Uses the certificate as the authentication method.
- psk-or-cert
-
Uses either the pre-shared-key or certificate based on the "Auth Method” field of the received AUTH payload.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
auto-eap-own-method
auto-eap-own-method
Syntax
auto-eap-own-method {psk | cert}
Context
[Tree] (config>ipsec>ike-policy auto-eap-own-method)
Full Context
configure ipsec ike-policy auto-eap-own-method
Description
This command enables following behavior for IKEv2 remote-access tunnel when auth-method is configured as auto-eap-radius:
-
If there is no AUTH payload in IKE_AUTH request, then system use EAP to authenticate client and also will own-auth-method to generate AUTH payload.
-
If there is AUTH payload in IKE_AUTH request:
-
if auto-eap-method is psk, then system proceed as auth-method:psk-radius.
-
if auto-eap-method is cert, then system proceed as auth-method:cert-radius.
-
if auto-eap-method is psk-or-cert, then:
-
if the "Auth Method" field of AUTH payload is PSK, then system proceed as auth-method:psk-radius.
-
if the "Auth Method" field of AUTH payload is RSA or DSS, then system proceed as auth-method:cert-radius.
-
-
The system will use auto-eap-own-method to generate AUTH payload.
-
This command only applies when auth-method is configured as auto-eap-radius.
Default
auto-eap-own-method cert
Parameters
- psk
-
Uses a pre-shared-key to generate AUTH payload.
- cert
-
Uses a public/private key to generate AUTH payload.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
auto-edge
auto-edge
Syntax
[no] auto-edge
Context
[Tree] (config>service>vpls>spoke-sdp>stp auto-edge)
[Tree] (config>service>template>vpls-sap-template>stp auto-edge)
[Tree] (config>service>vpls>sap>stp auto-edge)
Full Context
configure service vpls spoke-sdp stp auto-edge
configure service template vpls-sap-template stp auto-edge
configure service vpls sap stp auto-edge
Description
This command configures automatic detection of the edge port characteristics of the SAP or spoke SDP.
If auto-edge is enabled, and STP concludes there is no bridge behind the spoke SDP, the OPER_EDGE variable is dynamically set to true. If auto-edge is enabled, and a BPDU is received, the OPER_EDGE variable is dynamically set to false.
The no form of this command disables automatic detection.
Default
auto-edge
Platforms
All
auto-edge
Syntax
[no] auto-edge
Context
[Tree] (config>service>pw-template>stp auto-edge)
Full Context
configure service pw-template stp auto-edge
Description
This command configures automatic detection of the edge port characteristics of the SAP or spoke SDP.
If auto-edge is enabled, and STP concludes there is no bridge behind the spoke SDP, the OPER_EDGE variable is dynamically set to true. If auto-edge is enabled, and a BPDU is received, the OPER_EDGE variable is dynamically set to false.
The no form of this command disables automatic detection.
Default
auto-edge
Platforms
All
auto-esi
auto-esi
Syntax
auto-esi {none | type-1}
Context
[Tree] (config>service>system>bgp-evpn>eth-seg auto-esi)
Full Context
configure service system bgp-evpn ethernet-segment auto-esi
Description
This command configures the auto-ESI type to use in the Ethernet segment (ES).
The default mode is none and forces the user to configure a manual ESI. When type-1 is configured, a manual ESI cannot be configured and the ESI is auto-derived in accordance with the RFC 7432 ESI type 1 definition.
An ESI type 1 encodes 0x01 in the ESI type octet (T=0x01) and indicates that IEEE 802.1AX LACP is used between the PEs and CEs.
The ESI is auto-derived from the LACP PDUs by concatenating the following parameters:
-
CE LACP system MAC address (6 octets)
The CE LACP system MAC address is encoded in the high-order 6 octets of the ESI value field.
-
CE LACP port Key (2 octets)
The CE LACP port key is encoded in the 2 octets next to the system MAC address.
-
the remaining octet is set to 0x00.
Parameters
- type-1
-
Specifies an auto-generated ESI value.
- none
-
Specifies the configuration of a manual ESI.
Platforms
All
auto-establish
auto-establish
Syntax
[no] auto-establish
Context
[Tree] (config>router>l2tp>group>tunnel auto-establish)
Full Context
configure router l2tp group tunnel auto-establish
Description
This command specifies if this tunnel is to be automatically set up by the system.
Default
no auto-establish
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auto-establish
Syntax
[no] auto-establish
Context
[Tree] (config>service>vprn>l2tp>group>tunnel auto-establish)
Full Context
configure service vprn l2tp group tunnel auto-establish
Description
This command specifies if this tunnel is to be automatically set up by the system.
Default
no auto-establish
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auto-establish
Syntax
[no] auto-establish
Context
[Tree] (config>ipsec>trans-mode-prof>dyn auto-establish)
[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn auto-establish)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn auto-establish)
[Tree] (config>service>vprn>if>sap>ipsec-tun>dyn auto-establish)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn auto-establish)
Full Context
configure ipsec ipsec-transport-mode-profile dynamic-keying auto-establish
configure router interface ipsec ipsec-tunnel dynamic-keying auto-establish
configure service ies interface ipsec ipsec-tunnel dynamic-keying auto-establish
configure service vprn interface sap ipsec-tunnel dynamic-keying auto-establish
configure service vprn interface ipsec ipsec-tunnel dynamic-keying auto-establish
Description
This command enables automatic attempts to establish a phase 1 exchange.
The system automatically establishes a phase 1 SA as soon as the tunnel is provisioned and enabled (no shutdown). This option should only be configured on one side of the tunnel.
Any associated static routes remains up as long as the tunnel is up, even though it may actually be operationally down according to the CLI.
The no form of this command disables the automatic attempts to establish a phase 1 exchange.
Default
no auto-establish
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure ipsec ipsec-transport-mode-profile dynamic-keying auto-establish
- configure service vprn interface sap ipsec-tunnel dynamic-keying auto-establish
VSR
- configure service vprn interface ipsec ipsec-tunnel dynamic-keying auto-establish
- configure service ies interface ipsec ipsec-tunnel dynamic-keying auto-establish
- configure router interface ipsec ipsec-tunnel dynamic-keying auto-establish
auto-learn-mac-protect
auto-learn-mac-protect
Syntax
[no] auto-learn-mac-protect
Context
[Tree] (config>service>vpls>endpoint auto-learn-mac-protect)
[Tree] (config>service>pw-template>split-horizon-group auto-learn-mac-protect)
Full Context
configure service vpls endpoint auto-learn-mac-protect
configure service pw-template split-horizon-group auto-learn-mac-protect
Description
This command enables the automatic protection of source MAC addresses learned on the associated object. MAC protection is used in conjunction with the restrict-protected-src, restrict-unprotected-dst, and mac-protect commands. When auto-learn-mac-protect command is applied or removed, the MAC addresses are cleared from the related object.
When the auto-learn-mac-protect is enabled on an SHG the action only applies to the associated SAPs (no action is taken by default for spoke SDPs in the SHG). To enable this function for spoke SDPs within a SHG, the auto-learn-mac-protect command must be enabled explicitly under the spoke SDP. If required, the auto-learn-mac-protect command can also be enabled explicitly under specific SAPs within the SHG.
The no form of the command reverts to the default.
Default
no auto-learn-mac-protect
Platforms
All
auto-learn-mac-protect
Syntax
auto-learn-mac-protect [exclude-list name]
no auto-learn-mac-protect
Context
[Tree] (config>service>vpls>sap auto-learn-mac-protect)
[Tree] (config>service>vpls>spoke-sdp auto-learn-mac-protect)
[Tree] (config>service>vpls>split-horizon-group auto-learn-mac-protect)
[Tree] (config>service>vpls>mesh-sdp auto-learn-mac-protect)
[Tree] (config>service>pw-template auto-learn-mac-protect)
Full Context
configure service vpls sap auto-learn-mac-protect
configure service vpls spoke-sdp auto-learn-mac-protect
configure service vpls split-horizon-group auto-learn-mac-protect
configure service vpls mesh-sdp auto-learn-mac-protect
configure service pw-template auto-learn-mac-protect
Description
This command specifies whether to enable automatic population of the MAC protect list with source MAC addresses learned on the associated object under which the command is configured.
When configured, dynamically learned MAC Source Addresses (SA) are protected only if they are learned on an object with ALMP configured and there is no exclude list associated to the same object or if there is an exclude list but the MAC does not match any entry.
The same list can be used in multiple objects of the same or different service. If the list is empty, ALMP does not exclude any learned MAC from protection on the object.
The no form of the command disables the automatic population of the MAC protect list.
Default
auto-learn-mac-protect
Parameters
- name
-
Specifies the name of the exclude list, up to 32 characters.
Platforms
All
auto-lifetimes
auto-lifetimes
Syntax
[no] auto-lifetimes
Context
[Tree] (config>subscr-mgmt>rtr-adv-plcy>pfx-opt>stateful auto-lifetimes)
Full Context
configure subscriber-mgmt router-advertisement-policy prefix-options stateful auto-lifetimes
Description
This command adjusts the valid and preferred lifetime values of the router advertisement from the DHCP lease of the subscriber. Every router advertisement sent to the subscriber is derived from the DHCP lease in real time. The route advertisement is always sent on a DHCP Renew.
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
auto-lsp
auto-lsp
Syntax
auto-lsp lsp-template template-name {policy peer-prefix-policy [peer-prefix-policy] | one-hop}
no auto-lsp lsp-template template-name
Context
[Tree] (config>router>mpls auto-lsp)
Full Context
configure router mpls auto-lsp
Description
This command enables the automatic creation of an RSVP point-to-point LSP to a destination node whose router ID matches a prefix in the specified peer prefix policy. This LSP type is referred to as auto-LSP of type mesh.
The user can associate multiple templates with same or different peer prefix policies. Each application of an LSP template with a given prefix in the prefix list results in the instantiation of a single CSPF computed LSP primary path using the LSP template parameters as long as the prefix corresponds to a router ID for a node in the TE database. This command does not support the automatic signaling of a secondary path for an LSP. If the signaling of multiple LSPs to the same destination node is required, the user must apply a separate LSP template to the same or different prefix list that contains the same destination node. Each instantiated LSP will have a unique LSP ID and a unique tunnel ID. This command also does not support the signaling of a non-CSPF LSP. The selection of the no cspf option in the LSP template is blocked.
Up to five peer prefix policies can be associated with a given LSP template at all times. Each time the user runs the auto-lsp command with the same or different prefix policy associations, or the user changes a prefix policy associated with an LSP template, the system re-evaluates the prefix policy. The outcome of the re-evaluation tells MPLS if an existing LSP needs to be torn down or if a new LSP needs to be signaled to a destination address that is already in the TE database.
If a /32 prefix is added to (removed from) or if a prefix range is expanded (shrunk) in a prefix list associated with an LSP template, the preceding prefix policy re-evaluation is performed.
The user must perform a no shutdown of the template before the template takes effect. After a template is in use, the user must shut down the template before effecting any changes to the parameters, except for those LSP parameters for which the change can be handled with the Make-Before-Break (MBB) procedures. These parameters are bandwidth and enabling fast-reroute with or without the hop-limit or node-protect options. For all other parameters, the user must shut down the template, makes the change, and perform a no shutdown. This results in the existing instances of the LSP using this template to be torn down and re-signaled.
When a router with a router ID that matches a prefix in the prefix list appears in the TE database, it is a trigger to signal the LSP. The signaled LSP is installed in the Tunnel Table Manager (TTM) and is available to applications such as LDP-over-RSVP, resolution of BGP label routes, resolution of BGP, IGP, and static routes. It is, however, not available for use as a provisioned SDP for explicit binding or auto-binding by services.
Except for the MBB limitations to the configuration parameter change in the LSP template, MBB procedures for manual and timer based re-signaling of the LSP, for TE Graceful Shutdown and for soft preemption are supported.
The one-to-one option under fast-reroute, the LSP Diff-Serv class-type and backup-class-type parameters are not supported. If diffserv-te is enabled under RSVP, the auto-created LSP is still signaled but with the default LSP class type.
If the one-hop option is specified instead of a prefix list, this command enables the automatic signaling of one-hop point-to-point LSPs using the specified template to all directly connected neighbors. This LSP type is referred to as auto-LSP of type one-hop. Although the provisioning model and CLI syntax differ from that of a mesh LSP only by the absence of a prefix list, the actual behavior is quite different. When this command is executed, the TE database keeps track of each TE link that comes up to a directly connected IGP neighbor whose router ID is discovered. It then instructs MPLS to signals an LSP with a destination address matching the router ID of the neighbor and with a strict hop consisting of the address of the interface used by the TE link. Thus, the auto-lsp command with the one-hop option results in one or more LSPs signaled to the neighboring router.
An auto-created mesh or one-hop LSP can collect egress statistics at the ingress LER by adding the egress-statistics node configuration into the LSP template. The user can also collect ingress statistics at the egress LER by using the same ingress-statistics node configuration. The user must specify the full LSP name as signaled by the ingress LER in the RSVP session name field of the Session Attribute object in the received Path message.
This feature also provides for the auto-creation of an SR-TE mesh LSP and for an SR-TE one-hop LSP.
The SR-TE mesh LSP feature specifically binds a mesh-p2p-srte LSP template with one or more prefix lists. When the TE database discovers a router that has a router ID matching an entry in the prefix list, it triggers MPLS to instantiate an SR-TE LSP to that router using the LSP parameters in the LSP template.
The SR-TE one-hop LSP feature specifically activates a one-hop-p2p-srte LSP template. In this case, the TE database keeps track of each TE link that comes up to a directly connected IGP neighbor. It then instructs MPLS to instantiate a SR-TE LSP with the following parameters:
-
the source address of the local router
-
an outgoing interface matching the interface index of the TE-link
-
a destination address matching the router ID of the neighbor on the TE link
In both types of SR-TE auto-LSP, the router’s hop-to-label translation computes the label stack required to instantiate the LSP.
An SR-TE auto-LSP can be reported to a PCE but cannot be delegated or have its paths computed by PCE.
The no form of this command deletes all LSPs signaled using the specified template and prefix policy. When the one-hop option is used, it deletes all one-hop LSPs signaled using the specified template to all directly-connected neighbors.
Parameters
- lsp-template template-name
-
Specifies an LSP template name, up to 32 characters in length.
- policy peer-prefix-policy
-
Specifies an peer prefix policy name, up to 32 characters in length.
- one-hop
-
Enables the automatic signaling of one-hop point-to-point LSPs.
Platforms
All
auto-mep-discovery
auto-mep-discovery
Syntax
[no] auto-mep-discovery
Context
[Tree] (config>eth-cfm>domain>assoc auto-mep-discovery)
Full Context
configure eth-cfm domain association auto-mep-discovery
Description
This command enables the ability to auto-discover remote MEPs from a peer MEP sending ETH-CC.
The no form of this command disables the ability to auto-discover remote MEPs from a peer MEP sending ETH-CC.
Default
no auto-mep-discovery
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
auto-reply
auto-reply
Syntax
[no] auto-reply
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6 auto-reply)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 auto-reply)
Full Context
configure service ies subscriber-interface group-interface ipv6 auto-reply
configure service vprn subscriber-interface group-interface ipv6 auto-reply
Description
This command assists IP-only static hosts to resolve their default gateway and MAC. By default, the BNG anti-spoof filter drops packets from unknown hosts. The auto-reply features first allow hosts to resolve their default gateway and afterwards allow them to forward traffic. Using the data traffic, the BNG can utilize the data-trigger mechanism to learn the host’s MAC and populate the full IP+MAC static host entry.
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
auto-rp
auto-rp
Syntax
auto-rp [detail]
no auto-rp
Context
[Tree] (debug>router>pim auto-rp)
Full Context
debug router pim auto-rp
Description
This command enables debugging for PIM auto-RP.
The no form of this command disables PIM auto-RP debugging.
Parameters
- detail
-
Debugs detailed information on the PIM auto-RP mechanism.
Platforms
All
auto-rp-discovery
auto-rp-discovery
Syntax
auto-rp-discovery [candidate] [mapping-agent]
no auto-rp-discovery
Context
[Tree] (config>service>vprn>pim>rp auto-rp-discovery)
Full Context
configure service vprn pim rp auto-rp-discovery
Description
This command enables the auto-RP protocol in discovery mode. In discovery mode, RP-mapping and RP-candidate messages are received and forwarded to downstream nodes. RP-mapping messages are received locally to learn the availability of RP nodes present in the network. In a VPRN configuration, Nokia recommends that a local loopback interface should be created with the same IP address as the system IP address.
The following configuration guidelines apply.
-
Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together.
-
bsr-candidate for IPv6 and auto-rp-discovery for IPv4 can be enabled together.
-
auto-rp-discovery cannot be enabled together with mdt-type sender-only or mdt-type receiver-only, or wildcard-spmsi configurations.
This command also enables the auto-RP listener functionality. The auto-RP listener forwards the candidate 224.0.1.39 and mapping 224.0.1.40 messages over the PIM interfaces.
The no form of this command disables auto-RP discovery, auto-RP listener, candidate, and mapping-agent.
Default
no auto-rp-discovery
Parameters
- candidate
-
Specifies that the RP is a candidate RP. The auto-RP C-RP announces the candidate RP messages on the 224.0.1.39 multicast address. This functionality is in addition to the listener functionality enabled by the auto RP discovery.
The default value is no candidate.
- mapping agent
-
Specifies the mapping agent on the node. The auto-RP MA observes the auto-rp-announcement messages, selects the RP, and generates the RP discovery 224.0.1.40 messages. This functionality is in addition to the auto RP discovery functionality.
The default value is no mapping-agent.
Platforms
All
auto-rp-discovery
Syntax
auto-rp-discovery [candidate] [mapping-agent]
no auto-rp-discovery
Context
[Tree] (config>router>pim>rp auto-rp-discovery)
Full Context
configure router pim rp auto-rp-discovery
Description
This command enables the auto-RP protocol in discovery mode. In discovery mode, RP-mapping and RP candidate messages are received and forwarded to downstream nodes. RP-mapping messages are received locally to learn the availability of RP nodes present in the network.
The following configuration guidelines apply.
-
Either bsr-candidate for IPv4 or auto-rp-discovery can be configured; the two mechanisms cannot be enabled together.
-
bsr-candidate for IPv6 and auto-rp-discovery for IPv4 can be enabled together.
This command also enables the auto-RP listener functionality. The auto-RP listener forwards the candidate 224.0.1.39 and mapping 224.0.1.40 messages over the PIM interfaces.
The no form of this command disables auto-RP discovery, auto-RP listener, candidate, and mapping-agent.
Default
no auto-rp-discovery
Parameters
- candidate
-
Specifies that the RP is a candidate RP. The auto-RP C-RP announces the candidate RP messages on the 224.0.1.39 multicast address. This functionality is in addition to the listener functionality enabled by the auto RP discovery.
The default value is no candidate.
- mapping agent
-
Specifies the mapping agent on the node. The auto-RP MA observes the auto-rp-announcement messages, selects the RP, and generates the RP discovery 224.0.1.40 messages. This functionality is in addition to the auto RP discovery functionality.
The default value is no mapping-agent.
Platforms
All
auto-rx
auto-rx
Syntax
auto-rx
Context
[Tree] (config>router>ldp>targeted-session auto-rx)
Full Context
configure router ldp targeted-session auto-rx
Description
Commands in this context configure an automatic targeted LDP session and accept targeted Hello messages from any peer.
Platforms
All
auto-srrp-id-range
auto-srrp-id-range
Syntax
auto-srrp-id-range start start-id end end-id
no auto-srrp-id-range
Context
[Tree] (config>redundancy>srrp auto-srrp-id-range)
Full Context
configure redundancy srrp auto-srrp-id-range
Description
This command reserves IDs for internal SRRP objects created for inter-BNG-UP resiliency. Manually provisioned SRRP instances cannot use these reserved IDs.
The no form of this command removes the reservation of IDs.
Parameters
- start-id
-
Specifies the lower bound of the ID range.
- end-id
-
Specifies the upper bound of the ID range.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auto-sub-id-key
auto-sub-id-key
Syntax
auto-sub-id-key
Context
[Tree] (config>subscr-mgmt auto-sub-id-key)
Full Context
configure subscriber-mgmt auto-sub-id-key
Description
Commands in this context configure auto-generated subscriber identification key parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
auto-tx
auto-tx
Syntax
auto-tx
Context
[Tree] (config>router>ldp>targeted-session auto-tx)
Full Context
configure router ldp targeted-session auto-tx
Description
Commands in this context configure an automatic targeted LDP session and send targeted Hello messages towards PQ nodes determined by the rLFA algorithm.
Platforms
All
autoconfigure
autoconfigure
Syntax
autoconfigure
Context
[Tree] (bof autoconfigure)
Full Context
bof autoconfigure
Description
Commands in this context autoconfigure the IP address for the BOF. The IPv4 DHCP client, IPv6 DHCP client, and NDP/RA can be configured on the management interface.
Default
no autoconfigure
Platforms
7450 ESS-7, 7750 SR-1, 7750 SR-7, 7750 SR-1e, 7750 SR-2e, 7750 SR-s
autonegotiate
autonegotiate
Syntax
autonegotiate [limited]
no autonegotiate
Context
[Tree] (config>port>ethernet autonegotiate)
Full Context
configure port ethernet autonegotiate
Description
This command enables speed and duplex autonegotiation on Fast Ethernet ports and enables far-end fault indicator support on Gb ports.
There are three possible settings for autonegotiation:
-
"on” or enabled with full port capabilities advertised
-
"off” or disabled where there are no autonegotiation advertisements
-
"limited” where a single speed/duplex is advertised.
When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored.
When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port. Note that disabling autonegotiation on Gb ports is not allowed as the IEEE 802.3 specification for Gb Ethernet requires autonegotiation be enabled for far end fault indication.
If the autonegotiate limited keyword option is specified the port will auto-negotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multi-speed Gb ports to force Gb operation while keeping autonegotiation enabled for compliance with IEEE 802.3.
Router requires that autonegotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed.
The no form of this command disables autonegotiation on this port.
Default
autonegotiate
Parameters
- limited
-
The Ethernet interface will automatically negotiate link parameters with the far end, but will only advertise the speed and duplex mode specified by the Ethernet config>port>ethernet speed and config>port>ethernet duplex commands.
Platforms
All
autonegotiate
Syntax
[no] autonegotiate
Context
[Tree] (bof autonegotiate)
Full Context
bof autonegotiate
Description
This command enables speed and duplex autonegotiation on the management Ethernet port in the running configuration and the Boot Option File (BOF).
When autonegotiation is enabled, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, then the configured duplex and speed parameters are ignored.
The no form of this command disables the autonegotiate feature on this port.
Platforms
All
autonomous
autonomous
Syntax
[no] autonomous
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv>pfx-opt autonomous)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv>pfx-opt autonomous)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv>pfx-opt autonomous)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv>pfx-opt autonomous)
Full Context
configure service ies subscriber-interface group-interface ipv6 router-advertisements prefix-options autonomous
configure service vprn subscriber-interface ipv6 router-advertisements prefix-options autonomous
configure service ies subscriber-interface ipv6 router-advertisements prefix-options autonomous
configure service vprn subscriber-interface group-interface ipv6 router-advertisements prefix-options autonomous
Description
This command enables the option that determines whether or not the prefix can be used for stateless address autoconfiguration.
The no form of this command disables the option.
Default
no autonomous
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
autonomous
Syntax
[no] autonomous
Context
[Tree] (config>service>vprn>router-advert>if>prefix autonomous)
Full Context
configure service vprn router-advertisement interface prefix autonomous
Description
This command specifies whether the prefix can be used for stateless address autoconfiguration.
Default
autonomous
Platforms
All
autonomous
Syntax
[no] autonomous
Context
[Tree] (config>router>router-advert>if>prefix autonomous)
Full Context
configure router router-advertisement interface prefix autonomous
Description
This command specifies whether the prefix can be used for stateless address autoconfiguration.
Default
autonomous
Platforms
All
autonomous-system
autonomous-system
Syntax
autonomous-system as-number
no autonomous-system
Context
[Tree] (config>service>vprn autonomous-system)
Full Context
configure service vprn autonomous-system
Description
This command defines the autonomous system (AS) to be used by this VPN routing/forwarding (VRF). This command defines the autonomous system to be used by this VPN routing
The no form of this command removes the defined AS from this VPRN context.
Default
no autonomous-system
Parameters
- as-number
-
Specifies the AS number for the VPRN service.
Platforms
All
autonomous-system
Syntax
autonomous-system autonomous-system
no autonomous-system
Context
[Tree] (config>router autonomous-system)
Full Context
configure router autonomous-system
Description
This command configures the autonomous system (AS) number for the router. A router can only belong to one AS. An AS number is a globally unique number with an AS. This number is used to exchange exterior routing information with neighboring ASs and as an identifier of the AS itself.
If the AS number is changed on a router with an active BGP instance, the new AS number is not used until the BGP instance is restarted either by administratively disabling/enabling (shutdown/no shutdown) the BGP instance or rebooting the system with the new configuration.
Default
no autonomous-system
Parameters
- autonomous-system
-
Specifies the autonomous system number expressed as a decimal integer.
Platforms
All
autonomous-system-type
autonomous-system-type
Syntax
autonomous-system-type {origin | peer}
Context
[Tree] (config>cflowd>collector autonomous-system-type)
Full Context
configure cflowd collector autonomous-system-type
Description
This command defines whether the autonomous system (AS) information included in the flow data is based on the originating AS or external peer AS of the routes.
This option is only allowed if the collector is configured as Version 5 or Version 8.
Default
autonomous-system-type origin
Parameters
- origin
-
Specifies that the AS information included in the flow data is based on the originating AS.
- peer
-
Specifies that the AS information included in the flow data is based on the peer AS.
Platforms
All
aux-channel-enable
aux-channel-enable
Syntax
[no] aux-channel-enable
Context
[Tree] (config>open-flow>of-switch aux-channel-enable)
Full Context
configure open-flow of-switch aux-channel-enable
Description
This command enables auxiliary connections for the given H-OFS instance. If enabled, the H-OFS switch sets up a statistics auxiliary channel (Auxiliary ID 1) and a packet-in auxiliary channel (Auxiliary ID 2) for the main connection to every configured OpenFlow controller.
The no form of this command disables auxiliary connections.
Default
no aux-channel-enable
Platforms
VSR
aux-stats
aux-stats
Syntax
[no] aux-stats sr
Context
[Tree] (config>router>mpls aux-stats)
Full Context
configure router mpls aux-stats
Description
This command enables and configures counters for the specified labeled traffic type in an auxiliary MPLS statistics table. The sr keyword indicates to the system to increment packet and octet counters of that table for any type of Segment Routing traffic (SR-OSPF, SR-ISIS, SR-TE, and so on). This command cannot be used in specific system configurations. This command does not impact the overall counting of MPLS packets and octets shown, for example, by the show router mpls interface [ip-int-name | ip-address] statistics command.
The no form of this command disables the counters of the auxiliary MPLS statistics table. The no form of this command cannot be used if dark bandwidth accounting is enabled (config>router>rsvp>dbw-accounting).
Default
aux-stats sr
Parameters
- sr
-
Specifies the type of traffic to count in the auxiliary MPLS statistics table. Refers to any type of Segment Routing traffic (SR-OSPF, SR-ISIS, SR-TE, and so on).
Platforms
7750 SR, 7750 SR-s, 7950 XRS, VSR
availability
availability
Syntax
availability
Context
[Tree] (config>oam-pm>session>ethernet>lmm availability)
Full Context
configure oam-pm session ethernet lmm availability
Description
Commands in this context activate, collect, and record availability statistics for LMM tests. These computations are not enabled by default. In order to modify parameters within a session, including these availability parameters, the LMM test must be shut down.
Platforms
All
avg-flr-event
avg-flr-event
Syntax
avg-flr-event {forward | backward} threshold raise-threshold-percentage [clear clear-threshold-percentage]
no avg-flr-event {forward | backward}
Context
[Tree] (config>oam-pm>session>ethernet>slm>loss-events avg-flr-event)
[Tree] (config>oam-pm>session>ethernet>lmm>loss-events avg-flr-event)
[Tree] (config>oam-pm>session>ip>twamp-light>loss-events avg-flr-event)
Full Context
configure oam-pm session ethernet slm loss-events avg-flr-event
configure oam-pm session ethernet lmm loss-events avg-flr-event
configure oam-pm session ip twamp-light loss-events avg-flr-event
Description
This command sets the frame loss ratio threshold configuration to be applied and checked at the end of the measurement interval for the specified direction. This is a percentage based on average frame loss ratio over the entire measurement interval. If the clear-threshold-percent value is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear-threshold-percent value is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no form of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no avg-flr-event forward
no avg-flr-event backward
Parameters
- forward
-
Specifies the threshold is applied to the forward direction value.
- backward
-
Specifies the threshold is applied to the backward direction value.
- raise-threshold-percentage
-
Specifies the rising percentage that determines when the event is to be generated.
- clear-threshold-percentage
-
Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated.
Platforms
All
- configure oam-pm session ethernet slm loss-events avg-flr-event
- configure oam-pm session ethernet lmm loss-events avg-flr-event
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure oam-pm session ip twamp-light loss-events avg-flr-event
avg-frame-overhead
avg-frame-overhead
Syntax
avg-frame-overhead percent
no avg-frame-overhead
Context
[Tree] (config>qos>sap-egress>queue avg-frame-overhead)
[Tree] (config>qos>network-queue>queue avg-frame-overhead)
Full Context
configure qos sap-egress queue avg-frame-overhead
configure qos network-queue queue avg-frame-overhead
Description
This command configures the average frame overhead, expressed as a percentage, at which the offered load expands on the physical medium (wire) at egress. This is important for accurate "on-the-wire" rate calculations at various levels of H-QoS that do not inherently account for the physical medium characteristics. For example, without considering this overhead, a port scheduler in H-QoS might inaccurately estimate the available bandwidth on the wire, potentially leading to congestion issues and unexpected packet loss.
The rates impacted by the average frame overhead encompass the rates set on port schedulers and aggregate rate limits for subscribers and Vports. This impact is evident in the configured values, which represent on-the-wire (OTW) rates. Queue-configured rates, however, remain unaffected by this adjustment and continue to reflect Layer 2 rates.
This average frame overhead should be configured in networks with physical mediums that have constant sizes of transmission units (packets or cells) or in scenarios where the average packet size is known.
For Ethernet ports, the effect of this command depends on the setting of the avg-frame-overhead-mode command in advanced QoS configuration policy associated with the queue. If the avg-frame-overhead-mode is set to auto, the packet encapsulation overhead calculation is based on a fixed 20 bytes (7 bytes for preamble, 1 byte for start of frame delimiter, and 12 bytes for Inter-Frame Gap (IFG)) that the Ethernet medium adds to every packet during transmission. In other words, the configured rates for port-scheduler and aggregate rate limits for subscribers and Vports represent OTW rates.
The average frame overhead only affects rate and weight calculations and does not impact collected statistics for accounting purposes.
The no form of this command disables the average frame overhead.
Default
no avg-frame-overhead
Parameters
- percent
-
Specifies the average amount of packet-to-frame encapsulation overhead expected for the queue. This value is not used by the system for egress Ethernet queues. This parameter only applies to the 7450 ESS and 7750 SR.
Platforms
All
avg-frame-overhead
Syntax
avg-frame-overhead percent
no avg-frame-overhead
Context
[Tree] (config>service>cpipe>sap>egress>queue-override>queue avg-frame-overhead)
[Tree] (config>service>vprn>if>sap>egress>queue-override>queue avg-frame-overhead)
[Tree] (config>service>ies>if>sap>egress>queue-override>queue avg-frame-overhead)
[Tree] (config>service>epipe>sap>egress>queue-override>queue avg-frame-overhead)
[Tree] (config>service>vpls>sap>egress>queue-override>queue avg-frame-overhead)
[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue avg-frame-overhead)
[Tree] (config>service>ipipe>sap>egress>queue-override>queue avg-frame-overhead)
Full Context
configure service cpipe sap egress queue-override queue avg-frame-overhead
configure service vprn interface sap egress queue-override queue avg-frame-overhead
configure service ies interface sap egress queue-override queue avg-frame-overhead
configure service epipe sap egress queue-override queue avg-frame-overhead
configure service vpls sap egress queue-override queue avg-frame-overhead
configure subscriber-mgmt sla-profile egress qos queue avg-frame-overhead
configure service ipipe sap egress queue-override queue avg-frame-overhead
Description
This command configures overrides that supersede the average frame overhead configuration under the queue.
For a full description of this command, see the command description under the following contexts:
configure qos network-queue queue avg-frame-overhead
configure qos sap-egress queue avg-frame-overhead
The no form of this command disables overrides for the queue.
Default
no avg-frame-overhead
Parameters
- percent
-
Specifies the average amount of packet-to-frame encapsulation overhead expected for the queue. This value is not used by the system for egress Ethernet queues.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress queue-override queue avg-frame-overhead
All
- configure service ies interface sap egress queue-override queue avg-frame-overhead
- configure service ipipe sap egress queue-override queue avg-frame-overhead
- configure service vprn interface sap egress queue-override queue avg-frame-overhead
- configure service vpls sap egress queue-override queue avg-frame-overhead
- configure service epipe sap egress queue-override queue avg-frame-overhead
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure subscriber-mgmt sla-profile egress qos queue avg-frame-overhead
avg-frame-overhead-mode
avg-frame-overhead-mode
Syntax
avg-frame-overhead-mode {auto | from-queue}
no avg-frame-overhead-mode
Context
[Tree] (config>qos>adv-config-policy>child-control>offered-measurement avg-frame-overhead-mode)
Full Context
configure qos adv-config-policy child-control offered-measurement avg-frame-overhead-mode
Description
This command configures the average frame overhead mode; that is, whether the average frame overhead is calculated automatically or configured manually. The average frame overhead, which represents the additional bytes associated with the physical medium (wire), facilitates more precise rate calculations based on the actual characteristics of the medium.
This command is exclusively applicable to Ethernet ports. On Ethernet, the wire overhead typically amounts to 20 bytes. These 20 bytes are comprised of 7 bytes for the preamble, 1 byte for the Start of Frame Delimiter (SFD), and 12 bytes for the Inter-Packet Gap (IPG).
When used in conjunction with the avg-frame-overhead command that is configured directly under a queue, this command allows you to enable, disable, or customize average frame overhead. To activate this command, you must apply the associated advanced configuration policy to a specific queue.
The no form of this command removes the configuration.
Default
avg-frame-overhead-mode auto
Parameters
- auto
-
Keyword used to specify that the average frame overhead is automatically calculated and 20 bytes are added to each packet in the queue. This setting impacts rate calculations on port schedulers (whether on a port or within a Vport) and aggregate rate limits for subscribers and Vports where rate calculations are based on wire rates.
- from-queue
-
Keyword used to specify that the average frame overhead is manually configured under the queue level using the avg-frame-overhead command where the overhead value is specified in percentages of an average frame size. The default value for the avg-frame-overhead command (overhead is 0), the rate calculations throughout the H-QoS hierarchy are based on Layer 2 packets (Layer 2 rates).
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
avp-hiding
avp-hiding
Syntax
avp-hiding {sensitive | always}
no avp-hiding
Context
[Tree] (config>service>vprn>l2tp avp-hiding)
[Tree] (config>router>l2tp avp-hiding)
Full Context
configure service vprn l2tp avp-hiding
configure router l2tp avp-hiding
Description
This command configures Attribute Value Pair (AVP) hiding. This capability can be used to avoid the passing of sensitive data, such as user passwords, as cleartext in an AVP.
The no form of this command reverts to the default value.
Default
no avp-hiding
Parameters
- sensitive
-
AVP hiding is used only for sensitive information (such as username/password).
- always
-
AVP hiding is always used.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
avp-hiding
Syntax
avp-hiding {sensitive | always}
no avp-hiding
Context
[Tree] (config>service>vprn>l2tp>group avp-hiding)
Full Context
configure service vprn l2tp group avp-hiding
Description
This command configures Attribute Value Pair (AVP) hiding. This capability can be used to avoid the passing of sensitive data, such as user passwords, as cleartext in an AVP.
The no form of this command returns the value to never allow AVP hiding.
Default
no avp-hiding
Parameters
- avp-hiding
-
Specifies the method to be used for the authentication of the tunnels in this L2TP group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
avp-hiding
Syntax
avp-hiding {never | sensitive | always}
no avp-hiding
Context
[Tree] (config>service>vprn>l2tp>group>tunnel avp-hiding)
Full Context
configure service vprn l2tp group tunnel avp-hiding
Description
This command configures Attribute Value Pair (AVP) hiding. This capability can be used to avoid the passing of sensitive data, such as user passwords, as cleartext in an AVP.
Nokia recommends that sensitive information not be sent in cleartext.
The no form of this command removes the parameter of the configuration and indicates that the value on group level will be taken.
Default
no avp-hiding
Parameters
- avp-hiding
-
Specifies the method to be used for the authentication of the tunnel.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR