p Commands – Part II
pool
pool
Syntax
pool pool-name [create]
no pool pool-name
Context
[Tree] (config>service>vprn>dhcp>server pool)
[Tree] (config>router>dhcp>server pool)
[Tree] (config>service>vprn>dhcp6>server pool)
[Tree] (config>router>dhcp6>server pool)
Full Context
configure service vprn dhcp local-dhcp-server pool
configure router dhcp local-dhcp-server pool
configure service vprn dhcp6 local-dhcp-server pool
configure router dhcp6 local-dhcp-server pool
Description
This command configures a DHCP address pool on the router.
The no form of this command removes the pool name from the configuration.
Parameters
- pool name
-
Specifies the name of this IP address pool. Allowed values are any string, up to 32 characters.
- create
-
Keyword used to create the pool. 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
pool
Syntax
pool pool-name router router-instance [create]
no pool pool-name router router-instance
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>evpn>export>ip-advertise-routes pool)
Full Context
configure subscriber-mgmt isa-service-chaining evpn export ip-advertise-routes pool
Description
This command configures NAT pools that are advertised in EVPN type 5 routes to the peer participating in service chaining.
The no form of this command removes the parameters from the configuration.
Parameters
- pool-name
-
Specifies the name of the NAT pool up, to 32 characters.
- router-instance
-
Specifies the router instance belonging to the pool.
- create
-
Keyword used to create a pool instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool
Syntax
pool [name]
Context
[Tree] (config>port>access>egress pool)
[Tree] (config>port>network>egress pool)
[Tree] (config>port>access>ingress pool)
Full Context
configure port access egress pool
configure port network egress pool
configure port access ingress pool
Description
This command configures pool policies.
On the MDA level, access and network egress and access ingress pools are only allocated on channelized MDAs. Network ingress pools are allocated on the FP level for non-channelized MDAs.
Default
pool default
Parameters
- name
-
If specified, the name must be default.
Platforms
All
pool
Syntax
pool [name]
Context
[Tree] (config>card>fp>ingress>network pool)
Full Context
configure card fp ingress network pool
Description
This command configures the per-FP network ingress pool.
Default
pool default
Parameters
- name
-
If specified, the name must be default.
Platforms
All
pool
Syntax
pool nat-pool-name [nat-group nat-group-id type pool-type [ applications applications] [create]
no pool nat-pool-name
Context
[Tree] (config>service>vprn>nat>outside pool)
Full Context
configure service vprn nat outside pool
Description
This command configures a NAT pool.
Parameters
- nat-pool-name
-
Specifies the NAT pool name.
- nat-group-id
-
Specifies the NAT group ID.
- create
-
This parameter must be specified to create the instance.
- pool-type
-
Specifies the pool type.
- applications
-
Specifies the application.
- create
-
Keyword used to create the pool.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool
Syntax
pool nat-pool-name nat-group nat-group-id type pool-type [applications applications] [create]
no pool nat-pool-name
Context
[Tree] (config>router>nat>outside pool)
Full Context
configure router nat outside pool
Description
This command creates a NAT pool in the outside routing context. The NAT pool defines the parameters that will be used for IP address and port translation within the pool.
Parameters
- nat-pool-name
-
Specifies the NAT pool name, up to 32 characters.
- nat-group-id
-
Specifies the NAT group ID.
- create
-
Creates the instance.
- pool-type
-
Species the pool type.
- applications
-
This creation-time parameter configures the NAT pool for protocol agnostic operation. The IP addresses are translated in 1:1 fashion regardless of the protocol. No ports are translated for TCP or UDP traffic. Traffic through the pool can be initiated from inside or outside. When nat-pool is configured in agnostic mode, certain parameters in the pool are pre-set and cannot be changed:
-
mode one-to-one
-
port-forwarding-range 0
-
port-reservation blocks 1
-
subscriber-limit 1
-
deterministic port-reservation 65536.
This pool is used to configure static 1:1 NAT, where the operator have the control of the mapping between the inside and outside IP addresses. The static IP address mapping is using CLI constructs used in deterministic NAT (prefix and map deterministic NAT commands in the inside routing context).
ALG for TCP/UDP is supported in the protocol agnostic pool.
-
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool
Syntax
pool [name]
no pool
Context
[Tree] (config>isa>aa-grp>qos>egress>to-subscriber pool)
[Tree] (config>isa>aa-grp>qos>egress>from-subscriber pool)
Full Context
configure isa application-assurance-group qos egress to-subscriber pool
configure isa application-assurance-group qos egress from-subscriber pool
Description
Commands in this context configure an IOM pool as applicable to the specific application assurance group traffic. The user can configure resv-cbs (as percentage) values and slope-policy similarly to other IOM pool commands.
Default
pool default
Parameters
- name
-
If specified, the name must be default.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool
Syntax
pool nat-pool-name service-name service-name
pool nat-pool-name router router-instance
no pool
Context
[Tree] (config>service>nat>nat-policy pool)
Full Context
configure service nat nat-policy pool
Description
This command configures the NAT pool of this policy.
Parameters
- nat-pool-name
-
Specifies the name of the NAT pool, up to 32 characters.
- router-instance
-
Specifies the router instance the pool belongs to, either by router name or service ID.
- service-name
-
Specifies the name of the service, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool-manager
pool-manager
Syntax
pool-manager
Context
[Tree] (config>service>vprn>sub-if>wlan-gw pool-manager)
[Tree] (config>service>ies>sub-if>wlan-gw pool-manager)
Full Context
configure service vprn subscriber-interface wlan-gw pool-manager
configure service ies subscriber-interface wlan-gw pool-manager
Description
Commands in this context configure pool manager data for a WLAN GW subscriber interface.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool-name
pool-name
Syntax
[no] pool-name
Context
[Tree] (config>service>vprn>sub-if>grp-if>dhcp>option>vendor pool-name)
[Tree] (config>service>ies>if>dhcp>option>vendor pool-name)
[Tree] (config>service>vprn>if>dhcp>option>vendor pool-name)
[Tree] (config>service>ies>sub-if>grp-if>dhcp>option>vendor pool-name)
Full Context
configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option pool-name
configure service ies interface dhcp option vendor-specific-option pool-name
configure service vprn interface dhcp option vendor-specific-option pool-name
configure service ies subscriber-interface group-interface dhcp option vendor-specific-option pool-name
Description
This command sends the pool name in the Nokia vendor specific sub-option of the DHCP relay packet.
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
- configure service vprn subscriber-interface group-interface dhcp option vendor-specific-option pool-name
- configure service ies subscriber-interface group-interface dhcp option vendor-specific-option pool-name
All
- configure service vprn interface dhcp option vendor-specific-option pool-name
- configure service ies interface dhcp option vendor-specific-option pool-name
pool-name
Syntax
pool-name name
no pool-name
Context
[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client>dhcpv4-nat pool-name)
[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client>slaac pool-name)
[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client>dhcpv4-nat pool-name)
[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client>slaac pool-name)
[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client>ia-na pool-name)
[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client>ia-na pool-name)
Full Context
configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client dhcpv4-nat pool-name
configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client slaac pool-name
configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client dhcpv4-nat pool-name
configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client slaac pool-name
configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client ia-na pool-name
configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client ia-na pool-name
Description
This command specifies the pool name that should be sent in the DHCPv6 messages. This is reflected in the Nokia vendor specific pool option (vendor-id 6527, option-id 0x02).
The no form of this command removes pool-name and the option will not be sent in DHCPv6.
Parameters
- name
-
Specifies the pool name up with 32 characters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
pool-name
Syntax
[no] pool-name
Context
[Tree] (config>router>if>dhcp>option>vendor-specific-option pool-name)
Full Context
configure router interface dhcp option vendor-specific-option pool-name
Description
This command enables the sending of the pool name in the Nokia vendor-specific suboption of the DHCP relay packet.
The no form of this command disables the feature.
Default
no pool-name
Platforms
All
pool-type
pool-type
Syntax
pool-type pool-type
Context
[Tree] (config>test-oam>twamp>twl>src-udp-pools>port pool-type)
Full Context
configure test-oam twamp twamp-light source-udp-port-pools port pool-type
Description
This command maps the specified source UDP port to the TWAMP Light application allowed to configure the source UDP port. The OAM-PM IP family of tests can only configure the source UDP port when the port pool UDP source port is configured with a pool-type oam-pm. The test-oam link-measurement measurement-template can only configure the src-udp-port when the port pool UDP source port is configured with pool-type link-measurement.A pool type cannot be changed if its current application (either an oam-pm session or link-measurement template) is configured to use the specified port, regardless of the administrative or operational state. The configuration reference linking to the source UDP prevents the change.
Default
pool-type oam-pm
Parameters
- pool-type
-
Specifies the port to an application pool.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pop
pop
Syntax
[no] pop
Context
[Tree] (config>router>mpls>if>label-map pop)
Full Context
configure router mpls interface label-map pop
Description
This command specifies that the incoming label must be popped (removed). No label stacking is supported for a static LSP. The service header follows the top label. Once the label is popped, the packet is forwarded based on the service header.
The no form of this command removes the pop action for the in-label.
Platforms
All
populate
populate
Syntax
populate {static | dynamic | evpn} [ route-tag [1..255]]
no populate {static | dynamic | evpn}
Context
[Tree] (config>service>vprn>if>arp-host-route populate)
[Tree] (config>service>vprn>if>ipv6>nd-host-route populate)
[Tree] (config>service>ies>if>arp-host-route populate)
Full Context
configure service vprn interface arp-host-route populate
configure service vprn interface ipv6 nd-host-route populate
configure service ies interface arp-host-route populate
Description
This command enables the creation of ARP/ND host-route entries in the route-table out of a certain ARP/ND entry type.
The no form of this command reverts to the default.
Default
no populate
Parameters
- evpn
-
Enables the creation of ARP-ND host routes in the route table out of EVPN ARP/ND entries (entries learned from EVPN MAC/IP routes).
- dynamic
-
Enables the creation of ARP-ND host routes in the route table out of dynamic ARP/ND entries (learned from received ARP/ND messages from the hosts).
- static
-
Enables the creation of ARP-ND host routes in the route table out of configured static ARP/ND entries.
- route-tag [1..255]
-
Specifies the route tag that is added in the route table for ARP-ND host routes of type evpn, dynamic, or static. This tag can be matched on BGP VRF export and BGP peer export policies.
Platforms
All
port
port
Syntax
port port-id [sync-tag sync-tag] [create]
no port port-id]
Context
[Tree] (config>redundancy>multi-chassis>peer>sync port)
Full Context
configure redundancy multi-chassis peer sync port
Description
This command specifies the port to be synchronized with the multi-chassis peer and a synchronization tag to be used while synchronizing this port with the multi-chassis peer.
Parameters
- port-id
-
Specifies the port to be synchronized with the multi-chassis peer.
- sync-tag
-
Specifies a synchronization tag, up to 32 characters in length, to be used while synchronizing this port with the multi-chassis peer.
- create
-
Creates an entry; mandatory while creating an entry.
Platforms
All
port
Syntax
[no] port {port-id | aps-id | connector-port-id}
Context
[Tree] (config port)
Full Context
configure port
Description
This command enables access to the context to configure ports, multilink bundles, and bundle protection groups (BPGs). Before a port can be configured, the chassis slot must be provisioned with a valid card type and the MDA parameter must be provisioned with a valid MDA type.
Default
No ports are configured. All ports must be explicitly configured and enabled.
Parameters
- port-id
-
Specifies the physical port ID in the following format:
- eth-sat-id
-
Specifies the Ethernet satellite ID to be associated with this IP interface. This parameter applies to the 7950 XRS only.
- pxc-id
-
Specifies the PXC ID to be associated with this IP interface. This parameter applies to the 7950 XRS only.
- aps-id
-
This option configures APS on unbundled SONET/SDH ports. All SONET-SDH port parameters, with certain exceptions, for the working and protection circuit ports must be configured in the config>port>aps-id context. The working and protection circuit ports inherit all those parameters configured. The exception parameters for the working and protect circuits can be configured in the config>port>sonet-sdh context. Exception list commands include:
-
clock-source
-
[no] loopback
-
[no] report-alarm
-
section-trace
-
[no] threshold
When an configure port aps-id is created all applicable parameters under the port CLI tree (including parameters under any submenus) assume aps-id defaults, or when those are not explicitly specified, default to SONET/SDH port defaults for any SONET port.
All but a few exception SONET/SDH parameters for the working channel port must be configured in the configure port sonet-sdh context. The protection channel inherits all the configured parameters. The exception parameters for the protection channel can be configured in the configure port sonet-sdh context.
Signal failure (SF) and signal degrade (SD) alarms are not enabled by default on POS interfaces. It is recommended to change the default alarm notification configuration for POS ports that belong to APS groups in order to be notified of SF/SD occurrences to be able to interpret the cause for an APS group to switch the active line.
For path alarms, modify the logical line aps-id in the configure port aps-id <sonet-sdh>path report-alarm context. For example:
configure port aps-1 sonet-sdh path report-alarm p-ais
For line alarms, separately, modify the 2 physical ports that are members of the logical aps-id port (the working and protect lines). APS reacts only to line alarms, not path alarms. For example:
configure port 1/2/3 sonet-sdh report-alarm lb2er-sd
configure port 4/5/6 sonet-sdh report-alarm lb2er-sd
If the SD and SF threshold rates must be modified, the changes must be performed at the line level on both the working and protect APS port member.
The no form of this command deletes an aps-group-id or bundle-aps-group-id. In order for an aps- group-id to be deleted,
The same rules apply for physical ports, bundles deletions apply to APS ports/bundles deletions (for example an aps-group-id must be shutdown, have no service configuration on it, and no path configuration on it). In addition working and protection circuits must be removed before an aps-group-id may be removed.
-
- connector-port-id
-
Specifies the physical port of a connector in the following format.
Platforms
All
port
Syntax
port port-id
no port
Context
[Tree] (config>port-xc>pxc port)
Full Context
configure port-xc pxc port
Description
This command configures the referenced Ethernet port as a loopback or a cross-connect port (PXC). When this command is executed, the system automatically creates two PXC subports under this Ethernet port.
The physical PXC port does not require any external connectivity or optical transceivers to function properly. Consequently, all optic-related alarms are disabled on the port.
The physical PXC port is automatically configured as a hybrid port. The MTU is preset to 9212 bytes, the encapsulation type is set to dot1q, and dot1x tunneling is turned on.
A single physical port can be associated with more than one PXC. In other words, multiple PXCs are supported per physical port. Because PXC subports use a single physical port to transmit traffic in both directions, the nominal port bandwidth is asymmetrically divided between the two directions. For example, a 10 Gb/s Ethernet port in PXC mode can accommodate 9 Gb/s of traffic in one direction and 1 Gb/s in the other. Any other ratio can be achieved as long as the sum of the bandwidth of the two PXC subports does not exceed the bandwidth capacity of the physical port (10 Gb/s in this case).
Since the PXC uses a single physical port to transmit traffic in both directions, the nominal port bandwidth is asymmetrically divided between the two directions. For example, a 10 Gb/s Ethernet port in PXC mode can accommodate 9 Gb/s of traffic in one direction and 1 Gb/s in the other. Any other ratio can be achieved as long as the sum of the bandwidth of the two PXC subports does not exceed the bandwidth capacity of the physical port (10 Gb/s in this case).
The following rules apply to PXC port configurations:
-
Only unused physical ports (not associated with an interface or SAP) can be referenced inside of a PXC ID configuration.
-
The physical port cannot be removed from a PXC ID configuration if the corresponding PXC subports are currently in use.
-
A physical port cannot be used outside the configured PXC context. For example, a regular IP interface cannot use this physical port, or a SAP on that port cannot be associated with a service.
The no form of this command removes the port ID from the configuration.
Parameters
- port-id
-
Specifies the physical port in the slot/mda/port format.
Platforms
All
port
Syntax
port port-id [port-id] [priority priority] [sub-group sub-group-id] [hash-weight weight]
no port port-id [port-id]
Context
[Tree] (config>lag port)
Full Context
configure lag port
Description
This command adds ports to a Link Aggregation Group (LAG).
The port configuration of the first port added to the LAG is used as a basis to compare to subsequently added ports. If a discrepancy is found with a newly added port, that port will not be added to the LAG.
Multiple (space separated) ports can be added or removed from the LAG link assuming the maximum of number of ports is not exceeded.
Ports that are part of a LAG must be configured with auto-negotiate limited or disabled.
The no form of this command removes ports from the LAG.
Default
No ports are defined as members of a LAG.
Parameters
- port-id
-
Specifies the port ID.
The maximum number of ports in a LAG depends on the platform type, the hardware deployment, and the SR OS software release. Adding a port over the maximum allowed per given router or switch is blocked. Some platforms support double port scale for specific port types on LAGs with LAG ID in the range of 1 to 64 inclusive. Up to 16 ports can be specified in a single statement, up to 64 ports total.
- priority
-
Specifies the port priority used by LACP. The port priority is also used to determine the primary port. The port with the lowest priority is the primary port. In the event of a tie, the smallest port ID becomes the primary port.
- sub-group-id
-
Identifies a LAG subgroup. When using subgroups in a LAG, they should only be configured on one side of the LAG, not both. Only having one side perform the active/standby selection guarantees a consistent selection and fast convergence. The active or standby selection is signaled through LACP to the other side. The hold time should be configured when using subgroups to prevent the LAG going down when switching between active and standby subgroup since momentarily all ports are down in a LAG (break-before-make).
- weight
-
Specifies the flow hashing distribution between LAG ports.
Platforms
All
port
Syntax
port port-id
no port
Context
[Tree] (config>service>system>bgp-evpn>eth-seg port)
Full Context
configure service system bgp-evpn ethernet-segment port
Description
This command configures a port-id associated with the Ethernet-Segment. If the Ethernet-Segment is configured as all-active, then only a lag or a PW port can be associated to the Ethernet-Segment. If the Ethernet-Segment is configured as single-active, then a lag, port or sdp can be associated to the Ethernet-Segment. In any case, only one of the four objects can be configured in the Ethernet-Segment. A specified port can be part of only one Ethernet-Segment. Only Ethernet ports can be added to an Ethernet-Segment.
Default
no port
Parameters
- port-id
-
Specifies the port ID associated to the Ethernet-Segment.
port-id
slot/mda/port [.channel]
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
Platforms
All
port
Syntax
port [port-id | lag-id]
no port
Context
[Tree] (config>service>sdp>binding port)
Full Context
configure service sdp binding port
Description
This command specifies the port or lag identifier, to which the pseudowire ports associated with the underlying SDP are bound. If the underlying SDP is re-routed to a port or lag other than the specified one, the pseudowire ports on the SDP are operationally brought down.
The no form of the command removes the value from the configuration.
Default
no port
Parameters
- port-id
-
Specifies the identifier of the port in the slot/mda/port format.
port-id
slot/mda/port[.channel]
pxc-id
psc-id.sub-port
pxc psc-id.sub-port
pxc: keyword
id: 1 to 64
sub-port: a, b
aps-id
aps-group-id[.channel]
aps keyword
group-id
1 to 64
group-id
1 to 16
ccag-id - ccag-<id>.<path-id>[cc-type]
ccag
keyword
id
1 to 8
path-id
a, b
cc-type[.sap-net | .net-sap]
lag-id
lag-id
lag
keyword
id
1 to 800
- lag-id
-
Specifies the LAG identifier.
Platforms
All
port
Syntax
port [evpn-mpls | sap sap-id | sdp sdp-id:vc-id | vxlan vtep ip-address vni vni-id] [detail]
no port
Context
[Tree] (debug>service>id>pim-snooping port)
Full Context
debug service id pim-snooping port
Description
This command enables or disables debugging for PIM ports.
Parameters
- sap-id
-
Only debugs packets associated with the specified SAP
- sdp-id:vc-id
-
Only debugs packets associated with the specified SDP
- detail
-
Provides detailed debugging information
- evpn-mpls
-
Debugs PIM snooping statistics for EVPN-MPLS destinations
Platforms
All
port
Syntax
[no] port port-id
Context
[Tree] (config>service>system>pw-port-list port)
Full Context
configure service system pw-port-list port
Description
This command is only applicable for VSR configurations. This command is used to select ports eligible for use with Flex PW port. Physical ports used by Flex PW port can be shared with any other Layer 2 or Layer 3 service. In other words, a Layer 3 interface using a regular SAP can be associated with a VPRN service, while the port is used by a Flex PW port. Another regular SAP from the same port can be associated with a VPLS or Epipe service at the same time.
The following rules should be followed when populating a pw-port-list:
-
A port must be in hybrid mode before it is added to a pw-port-list.
-
Before a port is removed from or added to a pw-port-list, all PW ports must be dissociated from the corresponding Epipe services (PW ports must be unconfigured). This implies that all PW SAPs must be deleted.
-
Network interfaces (configured in the Base routing context) can be configured only on ports that are in the pw-port-list.
-
A port mode (access, network, or hybrid) cannot be changed while the port is in the pw-port-list.
From this, the operator can consider adding all ports that are in hybrid mode to a pw-port-list at the beginning of the system configuration. This ensures that those ports can be used by a Flex PW port at any later time, independently of their current use.
The no form of this command removes the port ID from the configuration.
Parameters
- port-id
-
Specifies the IP of the port.
Platforms
VSR
port
Syntax
port port
no port
Context
[Tree] (config>service>vprn>aaa>rmt-srv>radius port)
Full Context
configure service vprn aaa remote-servers radius port
Description
This command configures the UDP port number to contact the RADIUS server.
The no form of this command reverts to the default value.
Default
port 1812 (as specified in RFC 2865, Remote Authentication Dial In User Service (RADIUS))
Parameters
- port
-
Specifies the UDP port number to contact the RADIUS server.
Platforms
All
port
Syntax
port value
no port
Context
[Tree] (config>service>vprn>log>syslog port)
Full Context
configure service vprn log syslog port
Description
This command configures the UDP port that will be used to send syslog messages to the syslog target host.
The port configuration is needed if the syslog target host uses a port other than the standard UDP syslog port 514.
Only one port can be configured. If multiple port commands are entered, the last entered port overwrites the previously entered ports.
The no form of this command reverts to default value.
Default
no port
Parameters
- value
-
The value is the configured UDP port number used when sending syslog messages.
Platforms
All
port
Syntax
port port
Context
[Tree] (config>app-assure>group>event-log>syslog port)
Full Context
configure application-assurance group event-log syslog port
Description
This command specifies the UDP port used by application assurance to inject the syslog events inband.
Default
port 514
Parameters
- port
-
Specifies the UDP port number.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port
Syntax
[no] port port-number
[no] port range start-port-num end-port-num
Context
[Tree] (config>app-assure>group>port-list port)
Full Context
configure application-assurance group port-list port
Description
This command specifies the server TCP or UDP port number to use in the port list definition.
The no form of this command restores the default by removing port number from the port list.
Default
no port
Parameters
- port-number
-
Specifies the port number.
- start-port-number
-
Specifies the start port number.
- end-port-number
-
Specifies the end port number.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port
Syntax
port {port-id | lag lag-id} [egress] [ingress]
no port {port-id | lag lag-id} {[egress] [ ingress]}
Context
[Tree] (config>mirror>mirror-source port)
Full Context
configure mirror mirror-source port
Description
This command enables mirroring of traffic ingressing or egressing a port (Ethernet port, SONET/SDH channel, TDM channel, or Link Aggregation Group (LAG)).
The port command associates a port or LAG to a mirror source. The port is identified by the port-id. The defined port may be Ethernet, Access or network, SONET/SDH, or TDM channel access. A network port may be a single port or a Link Aggregation Group (LAG) ID. When a LAG ID is given as the port-id, mirroring is enabled on all ports making up the LAG. If the port is a SONET/SDH interface, the channel-id must be specified to identify which channel is being mirrored (applies to the 7450 ESS and 7750 SR). Either a LAG port member or the LAG port can be mirrored.
The port is only referenced in the mirror source for mirroring purposes. The mirror source association does not need to be removed before deleting the card to which the port belongs. If the port is removed from the system, the mirroring association will be removed from the mirror source.
The same port may not be associated with multiple mirror source definitions with the ingress parameter defined. The same port may not be associated with multiple mirror source definitions with the egress parameter defined.
If a SAP is mirrored on an access port, the SAP mirroring will have precedence over the access port mirroring when a packet matches the SAP mirroring criteria. Filter and label mirroring destinations will also precedence over a port-mirroring destination.
If the port is not associated with a mirror-source, packets on that port will not be mirrored. Mirroring may still be defined for a SAP, label or filter entry, which will mirror based on a more specific criteria.
The encapsulation type on an access port or channel cannot be changed to Frame Relay if it is being mirrored (applies to the 7750 SR and 7450 ESS).
The no port command disables port mirroring for the specified port. Mirroring of packets on the port may continue due to more specific mirror criteria. If the egress or ingress parameter keywords are specified in the no command, only the ingress or egress mirroring condition will be removed.
Parameters
- port-id
-
Specifies the port ID of the 7750 SR or 7950 XRS.
The following syntax applies to the 7750 SR:
port-id
slot/mda/port [.channel]
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
bgrp-id
bpgrp-type-bpgrp-num
bgrp
keyword
type
ima, ppp
bgrp-num
1 to 2000
ccag-id
ccag-id.path-id cc-type:cc-id
ccag
keyword
id
1 to 8
path-id
a, b
cc-type
sap-net, .net-sap
cc-id
0 to 4094
The following syntax applies to the 7950 XRS:
port-id
slot/mda/port [.channel]
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
- lag-id
-
The LAG identifier, expressed as a decimal integer.
Note:On the 7950 XRS, the XMA ID takes the place of the MDA.
- egress
-
Specifies that packets egressing the port should be mirrored. Egress packets are mirrored to the mirror destination after egress packet modification.
- ingress
-
Specifies that packets ingressing the port should be mirrored. Ingress packets are mirrored to the mirror destination prior to ingress packet modification.
Platforms
All
port
Syntax
port {port-id | lag lag-id} {[ egress] [ingress]}
no port {port-id | lag lag-id} [ egress] [ingress]
Context
[Tree] (config>li>li-source port)
Full Context
configure li li-source port
Description
This command specifies the port to perform lawful intercept. It is recommended when configuring li-source>port criteria, the li-source should only contain ports. All other criteria such as SAPs and subscribers should use a different li-source.
The no form of this command reverts to the default.
Parameters
- port-id
-
Specifies the port ID to perform lawful intercept.
port-id
slot/mda/port [.channel]
aps-id
aps-<group-id>[.channel]
aps
keyword
group-id
1 to 128
eth-sat-id
esat-<id>/<slot>/[u]<port>
esat
keyword
id
1 to 20
u
keyword for up-link port
tdm-sat-id
tsat-<id>/<slot>/[<u>]<port>.<channel>
tsat
keyword
id
1 to 20
u
keyword for up-link port
pxc-id
pxc-<id>.<sub-port>
pxc
keyword
id
1 to 64
sub-port
a, b
- lag-id
-
The LAG identifier, expressed as a decimal integer.
Note:On the 7950 XRS, the XMA ID takes the place of the MDA.
- egress
-
Performs lawful intercept on egress traffic.
- ingress
-
Performs lawful intercept on ingress traffic.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port tcp-port
no port
Context
[Tree] (config>li>x-interfaces>lics>lic port)
Full Context
configure li x-interfaces lics lic port
Description
This command configures the TCP port associated with this LIC.
The no form of this command reverts to the default.
Parameters
- tcp-port
-
Specifies the TCP source port of the LIC.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port tcp-port
no port
Context
[Tree] (config>li>x-interfaces>x1 port)
Full Context
configure li x-interfaces x1 port
Description
This command configures the TCP port for the X1 interface. The system listens to this port and uses it as the source TCP port.
The no form of this command reverts to the default.
Parameters
- tcp-port
-
Specifies the TCP port.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port {port-id | lag lag-id} {[egress] [ingress]}
no port {port-id | lag lag-id} [egress] [ ingress]
Context
[Tree] (debug>mirror-source port)
Full Context
debug mirror-source port
Description
This command enables mirroring of traffic ingressing or egressing a port (Ethernet port, SONET/SDH channel, TDM channel, or Link Aggregation Group (LAG)).
The port command associates a port or LAG to a mirror source. The port is identified by the port-id. The defined port may be Ethernet, Access or network, SONET/SDH, or TDM channel access. A network port may be a single port or a Link Aggregation Group (LAG) ID. When a LAG ID is given as the port-id, mirroring is enabled on all ports making up the LAG. If the port is a SONET/SDH interface, the channel-id must be specified to identify which channel is being mirrored (applies to the 7450 ESS and 7750 SR). Either a LAG port member or the LAG port can be mirrored.
The port is only referenced in the mirror source for mirroring purposes. The mirror source association does not need to be removed before deleting the card to which the port belongs. If the port is removed from the system, the mirroring association will be removed from the mirror source.
The same port may not be associated with multiple mirror source definitions with the ingress parameter defined. The same port may not be associated with multiple mirror source definitions with the egress parameter defined.
If a SAP is mirrored on an access port, the SAP mirroring will have precedence over the access port mirroring when a packet matches the SAP mirroring criteria. Filter and label mirroring destinations will also precedence over a port-mirroring destination.
If the port is not associated with a mirror-source, packets on that port will not be mirrored. Mirroring may still be defined for a SAP, label or filter entry, which will mirror based on a more specific criteria.
The encapsulation type on an access port or channel cannot be changed to Frame Relay if it is being mirrored (applies to the 7750 SR and 7450 ESS).
The no port command disables port mirroring for the specified port. Mirroring of packets on the port may continue due to more specific mirror criteria. If the egress or ingress parameter keywords are specified in the no command, only the ingress or egress mirroring condition will be removed.
Parameters
- port-id
-
Specifies the port ID of the 7750 SR or 7950 XRS.
The following syntax applies to the 7750 SR:
port-id
slot/mda/port [.channel]
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
ccag-id
ccag-id.path-id cc-type:cc-id
ccag
keyword
id
1 to 8
path-id
a,b
cc-type
sap-net, net-sap
cc-id
0 to 4094
The following syntax applies to the 7950 XRS:
port-id
slot/mda/port [.channel]
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
- lag-id
-
Specifies the LAG identifier, expressed as a decimal integer.
Note:On the 7950 XRS, the XMA ID takes the place of the MDA.
- egress
-
Specifies that packets egressing the port should be mirrored. Egress packets are mirrored to the mirror destination after egress packet modification.
- ingress
-
Specifies that packets ingressing the port should be mirrored. Ingress packets are mirrored to the mirror destination prior to ingress packet modification.
Platforms
All
port
Syntax
port {lt | gt | eq} port-number
port port-list port-list-name
port range port-number port-number
no port
Context
[Tree] (config>filter>ipv6-exception>entry>match port)
[Tree] (config>filter>ipv6-filter>entry>match port)
[Tree] (config>filter>ip-filter>entry>match port)
Full Context
configure filter ipv6-exception entry match port
configure filter ipv6-filter entry match port
configure filter ip-filter entry match port
Description
This command configures a TCP/UDP/SCTP source or destination port match criterion in IPv4 and IPv6 CPM (SCTP not supported) and/or ACL filter policies. A packet matches this criterion if the packet TCP/UDP/SCTP (as configured by protocol/next-header match) source OR destination port matches either the specified port value or a port in the specified port range or port-list.
Operational Note: This command is mutually exclusive with src-port and dst-port commands. Configuring "port eq 0", may match non-initial fragments where the source/destination port values are not present in a packet fragment if other match criteria are also met.
The no form of this command deletes the specified port match criterion.
Default
no port
Parameters
- lt | gt | eq
-
Specifies the operator to use relative to port-number for specifying the port number match criteria.
- lt
-
Specifies that all port numbers less than port-number match.
- gt
-
Specifies that all port numbers greater than port-number match.
- eq
-
Specifies that the port-number must be an exact match.
- port-number
-
Specifies a source or destination port to be used as a match criterion. The port number can be expressed as a decimal integer, as well as in hexadecimal or binary format. The following value shows a decimal integer only.
- port-list port-list-name
-
Specifies an inclusive range of source or destination port values to be used as match criteria.
- range port-number port-number
-
Specifies an inclusive range of source or destination port values to be used as match criteria.
Platforms
VSR
- configure filter ipv6-exception entry match port
All
- configure filter ip-filter entry match port
- configure filter ipv6-filter entry match port
port
Syntax
[no] port port-number
[no] port range start end
Context
[Tree] (config>filter>match-list>port-list port)
Full Context
configure filter match-list port-list port
Description
This command adds a port or a range of ports to an existing port match list. The no form of this command deletes the specified port or range of ports form the list.
Parameters
- port-number
-
Specifies the port number to add to the list. The port number can be expressed as a decimal integer, as well as in hexadecimal or binary format. Below shows decimal integer only.
- start end
-
Specifies an inclusive port range between two port numbers values. The start of the range and end of the range can be expressed as decimal integers, as well as in hexadecimal or binary format. The following value shows decimal integer only.
Platforms
All
port
Syntax
port port-id
no port
Context
[Tree] (config>router>origin-validation>rpki-session port)
Full Context
configure router origin-validation rpki-session port
Description
This command configures the destination port number to use when contacting the cache server. The default port number is 323. The port cannot be changed without first shutting down the session.
Default
no port
Parameters
- port-id
-
Specifies a port ID.
Platforms
All
port
Syntax
port port-name
no port
Context
[Tree] (config>router>if port)
Full Context
configure router interface port
Description
This command creates an association with a logical IP interface and a physical port.
An interface can also be associated with the system (loopback address).
The command returns an error if the interface is already associated with another port or the system. In this case, the association must be deleted before the command is re-attempted. The port-id or port-id for Ethernet ports can be in one of the following forms:
Ethernet interfaces
If the card in the slot has MDAs/XMAs, port-id is in the slot_number/MDA or XMA _number/port_number format; for example, 1/1/3 specifies port 3 of the MDA/XMA installed in MDA/XMA slot 1 on the card installed in chassis slot 1.
SONET/SDH interfaces
When the port-id represents a POS interface, the port-id must include the channel-id. The POS interface must be configured as a network port.
The no form of this command deletes the association with the port. The no form of this command can only be performed when the interface is administratively down.
Default
no port
Parameters
- port-name
-
The physical port identifier to associate with the IP interface.
Platforms
All
port
Syntax
port port-id to port-id [create]
no port port-id
Context
[Tree] (config>system>port-topology port)
Full Context
configure system port-topology port
Description
This command is used for satellites. It identifies to the SR OS that there is an internal connection between two ports.
Permitted pairings of the two ports are:
|
First port |
Second port |
|
Router port |
Satellite uplink port |
|
Satellite uplink port |
Router port |
For satellites, this command configures the binding between a host port ID and the satellite uplink from the satellite chassis. The port topology can be configured with the host connected to a satellite uplink or the satellite uplink port connected to the specified host port. Both configurations are supported, as shown in the following examples:
*A:Dut-A# configure system port-topology port esat-1/1/u4 to 1/2/2 create
*A:Dut-A# configure system port-topology no port esat-1/1/u4
*A:Dut-A# configure system port-topology port 1/2/2 to esat-1/1/u4 create
*A:Dut-A# configure system port-topology no port 1/2/2
The no form of the command removes the internal connection.
Default
no port port-id
Parameters
- port-id
-
Specifies one port of an internal port connection. These ports can be router ports or Ethernet satellite uplink ports. Acceptable pairings are defined in the command description.
- create
-
Specifies the keyword required to create the binding between the two ports.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port port-id
Context
[Tree] (config>system>satellite>port-template port)
Full Context
configure system satellite port-template port
Description
This command specifies the satellite port to be reconfigured.
The no form of this command deletes the specified port configuration.
Parameters
- port-id
-
Specifies the satellite physical port ID. This must use the format slot/mda/port. Currently, all satellites have a single slot and a single MDA, so these values will always be 1. For example, port 10 would be specified as 1/1/10.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port port-id [create]
no port port-id
Context
[Tree] (config>system>ptp port)
Full Context
configure system ptp port
Description
This command configures PTP over Ethernet on the physical port. The PTP process shall transmit and receive PTP messages through the port using Ethernet encapsulation (as opposed to UDP/IPv4 encapsulation).
The frames are transmitted with no VLAN tags even if the port is configured for dot1q or qinq modes for encap-type. In addition, the received frames from the external PTP clock must also be untagged.
There are two reserved multicast addresses allocated for PTP messages (see Annex F IEEE Std 1588™-2008). Either address can be configured for the PTP messages sent through this port.
A PTP port may not be created if the PTP profile is set g8265dot1-2010.
If the port specified in the port-id supports 1588 port based timestamping, then a side effect of enabling PTP over Ethernet on the port shall be the enabling of Synchronous Ethernet on that port.
De-provisioning of the card or MDA containing the specified port is not permitted while the port is configured within PTP.
Changing the encapsulation or the port type of the Ethernet port is not permitted when PTP Ethernet Multicast operation is configured on the port.
To allocate an ethernet satellite client port as a PTP port, the ethernet satellite must first be enabled for the transparent clock function. For more information, see the config>system>satellite>eth-sat ptp-tc command.
The SyncE/1588 ports of the CPM and CCMs can be specified as a PTP port. These use the 'A/3’ and 'B/3’ designation and they both must be specified as two PTP ports if both are to be used. The active CPM sends and receives messages on both ports if they are specified and enabled.
Parameters
- port-id
-
Specifies a specific physical port.
- create
-
Creates the PTP port. This keyword is required when first creating the PTP port, if the system is configured to require it (enabled in the environment create command). Once the PTP port is created, it is possible to navigate into the context without the create keyword.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port value
no port
Context
[Tree] (config>log>syslog port)
Full Context
configure log syslog port
Description
This command configures the UDP port that will be used to send syslog messages to the syslog target host.
The port configuration is needed if the syslog target host uses a port other than the standard UDP syslog port 514.
Only one port can be configured. If multiple port commands are entered, the last entered port overwrites the previously entered ports.
The no form of this command removes the value from the configuration.
Parameters
- value
-
Specifies the value that is the configured UDP port number used when sending syslog messages.
Platforms
All
port
Syntax
port port
no port
Context
[Tree] (config>system>netconf>listen port)
Full Context
configure system netconf listen port
Description
This command specifies the port on which the SR OS NETCONF server listens for new connections. Only one port can be configured for NETCONF management.
The configured port applies to both non-VPRN and VPRN management. New NETCONF connections are able to use the configured port. The SR OS NETCONF server errors if a port, different from the configured port, is used to SSH to the SR OS NETCONF server. For NETCONF connections not using VPRN management, active NETCONF connections are not disconnected if the port used to establish the connections is changed. For NETCONF connections using VPRN management, active NETCONF connections are disconnected if the port used to establish the connections is changed.
The no form of this command resets the port on which the SR OS NETCONF server listens to the default port of 830.
Parameters
- port
-
Specifies the port on which NETCONF listens for new connections.
Platforms
All
port
Syntax
port tcp/udp port-number [mask]
port port-list port-list-name
port range tcp/udp port-number tcp/udp port-number
no port
Context
[Tree] (config>system>security>cpm-filter>ipv6-filter>entry>match port)
[Tree] (config>system>security>cpm-filter>ip-filter>entry>match port)
Full Context
configure system security cpm-filter ipv6-filter entry match port
configure system security cpm-filter ip-filter entry match port
Description
This command configures a TCP/UDP source or destination port match criterion in IPv4 and IPv6 CPM filter policies. A packet matches this criterion if packet’s TCP/UDP (as configured by protocol/next-header match) source OR destination port matches either the specified port value or a port in the specified port range or port list.
This command is mutually exclusive with src-port and dst-port commands.
The no form of this command deletes the specified port match criterion.
Default
no port
Parameters
- tcp/udp port-number
-
Specifies the source or destination port to be used as a match criterion specified as a decimal integer.
- mask
-
Specifies the 16 bit mask to be applied when matching the port.
- range tcp/udp port-number
-
Specifies an inclusive range of source or destination port values to be used as match criteria. start of the range and end of the range are expressed as decimal integers.
- port-list port-list-name
-
Specifies a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port port
no port
Context
[Tree] (config>system>security>radius port)
Full Context
configure system security radius port
Description
This command configures the TCP port number to contact the RADIUS server.
The no form of this command reverts to the default value.
Default
port 1812 (as specified in RFC 2865, Remote Authentication Dial In User Service (RADIUS))
Parameters
- port
-
Specifies the TCP port number to contact the RADIUS server.
Platforms
All
port
Syntax
[no] port port-number
[no] port range start end
Context
[Tree] (config>qos>match-list>port-list port)
Full Context
configure qos match-list port-list port
Description
This command adds a port or a range of ports to an existing port match list.
The no form of this command deletes the specified port or range of ports form the list.
Parameters
- port-number
-
Specifies the port number to add to the list. The port number can be expressed as a decimal integer, as well as in hexadecimal or binary format. Below shows decimal integer only.
- range
-
Keyword specifying a range of port values.
- start
-
Specifies the start of the port range, expressed as decimal integers, as well as in hexadecimal or binary format. The following value shows decimal integer only.
- end
-
Specifies the end of the port range, expressed as decimal integers, as well as in hexadecimal or binary format. The following value shows decimal integer only.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port
Syntax
port port
no port
Context
[Tree] (config>system>grpc-tunnel>tunnel>handler port)
Full Context
configure system grpc-tunnel tunnel handler port
Description
This command assigns the TCP port number that the handler listens to internally.
The no form of this command disables the handler from listening to a TCP port.
Default
no port
Parameters
- port
-
Specifies the TCP port number.
Platforms
All
port
Syntax
port port-number
Context
[Tree] (config>test-oam>twamp>twl>src-udp-pools port)
Full Context
configure test-oam twamp twamp-light source-udp-port-pools port
Description
This command configures the TWAMP Light reserved source UDP ports to be mapped to a specific TWAMP Light or STAMP application.
Parameters
- port-number
-
Specifies the TWAMP Light reserved source UDP port number.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port-block-extensions
port-block-extensions
Syntax
port-block-extensions ports num-ports subscriber-limit number
port-block-extension no ports
Context
[Tree] (config>router>nat>outside>pool port-block-extensions)
[Tree] (config>service>vprn>nat>outside>pool port-block-extensions)
Full Context
configure router nat outside pool port-block-extensions
configure service vprn nat outside pool port-block-extensions
Description
This command configures a port block reserved for a dynamic NAT traffic flow for each subscriber with a port forwarding entry.
The no form of this command removes the values from the configuration.
Parameters
- num-ports
-
Specifies the size of extended port-block for L2-aware subscribers
- number
-
Specifies the limit of L2-aware NAT subscribers per an outside IP address
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-block-extensions
Syntax
port-block-extensions
Context
[Tree] (config>service>nat>up-nat-policy port-block-extensions)
Full Context
configure service nat up-nat-policy port-block-extensions
Description
Commands in this context configure the attributes for dynamic allocation of NAT port blocks beyond the initial port blocks.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-bw-oversub-factor
port-bw-oversub-factor
Syntax
port-bw-oversub-factor oversubscription-factor
no port-bw-oversub-factor
Context
[Tree] (config>qos>hs-pool-policy>mid-tier>mid-pool port-bw-oversub-factor)
Full Context
configure qos hs-pool-policy mid-tier mid-pool port-bw-oversub-factor
Description
This command modifies the size of the mid-pool when calculating the port-class pool sizes based on port bandwidth ratios. The command does not actually change the size of the mid-pool, only the size reported to the port-class pool sizing function.
Port-class pools can be sized in one of two ways: dynamically (proportionate to the bandwidth of each port) or explicitly (based on a percentage of the parent mid-pool). Explicit percentages require careful determination of the amount to give each pool. The dynamic sizing function attempts to automatically size each pool based on the relative amount of bandwidth each port-class pool is supporting compared to other port’s port-class pools. This is accomplished by determining a dynamic weight for each port with port-class pools mapped to a given mid-pool. As true with any weighted behavior, the mid-pool buffer allocation resource is distributed in a non-oversubscribed manner to its child port-class pools. The port-bw-oversub-factor oversubscription-factor allows this distribution mechanism to become proportionally oversubscribed based on the defined factor. An oversubscription-factor of 1.5 causes the port-class pool dynamic sizes to be 1.5 times bigger, allowing for a potentially more efficient utilization of the buffers represented by mid-pool.
The port-bw-oversub-factor oversubscription-factor for a mid-pool can be modified at any time, causing the corresponding port-class pool dynamic sizes to be recalculated.
A similar behavior can be obtained by increasing the mid-pool’s allocation-percent of its parent root-pool. However, the major difference in using port-bw-oversub-factor is that it provides larger port-class pools without allowing the mid-pool to use a higher number of buffers in the root pool.
The no form of the command reverts to the default.
Default
port-bw-oversub-factor 1
Parameters
- oversubscription-factor
-
Specifies the factor by which the dynamically-sized port-class pools associated with the mid-pool may oversubscribe the mid-pool. This parameter is required when the port-bw-oversub-factor command is executed.
Platforms
7750 SR-7/12/12e
port-control
port-control
Syntax
port-control [auto | force-auth | force-unauth]
Context
[Tree] (config>port>ethernet>dot1x port-control)
Full Context
configure port ethernet dot1x port-control
Description
This command configures the 802.1x authentication mode.
The no form of this command returns the value to the default.
Default
port-control force-auth
Parameters
- force-auth
-
Disables 802.1x authentication and causes the port to transition to the authorized state without requiring any authentication exchange. The port transmits and receives normal traffic without requiring 802.1x-based host authentication.
- force-unauth
-
Causes the port to remain in the unauthorized state, ignoring all attempts by the hosts to authenticate. The switch cannot provide authentication services to the host through the interface.
- auto
-
Enables 802.1x authentication. The port starts in the unauthorized state, allowing only EAPoL frames to be sent and received through the port. Both the router and the host can initiate an authentication procedure. The port will remain in unauthorized state (no traffic except EAPoL frames is allowed) until the first client is authenticated successfully. After this, traffic is allowed on the port for all connected hosts.
Platforms
All
port-down
port-down
Syntax
[no] port-down
Context
[Tree] (config>subscr-mgmt>ancp>ancp-policy port-down)
Full Context
configure subscriber-mgmt ancp ancp-policy port-down
Description
Commands in this context configure the actions taken on port-down.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
port-down
Syntax
[no] port-down port-id
Context
[Tree] (config>vrrp>policy>priority-event port-down)
Full Context
configure vrrp policy priority-event port-down
Description
This command configures a port down priority control event that monitors the operational state of a port or SONET/SDH channel. When the port or channel enters the operational down state, the event is considered set. When the port or channel enters the operational up state, the event is considered cleared.
Multiple unique port-down event nodes can be configured within the priority-event context up to the overall limit of 32 events. Up to 32 events can be defined in any combination of types.
The port-down command can reference an arbitrary port or channel. The port or channel does not need to be preprovisioned or populated within the system. The operational state of the port-down event is set as follows:
-
Set – non-provisioned
-
Set – not populated
-
Set – down
-
Cleared – up
When the port or channel is provisioned, populated, or enters the operationally up or down state, the event operational state is updated appropriately.
When the event enters the operationally down, non-provisioned, or non-populated state, the event is considered to be set. When an event transitions from clear to set, the set is processed immediately and must be reflected in the associated virtual router instances in-use priority value. As the event transitions from cleared to set, a hold-set timer is loaded with the value configured by the events hold-set command. This timer prevents the event from clearing until it expires, damping the effect of event flapping. If the event clears and becomes set again before the hold-set timer expires, the timer is reset to the hold-set value, extending the time before another clear can take effect.
When the event enters the operationally up state, the event is considered to be cleared. Once the events hold-set expires, the effects of the events priority value are immediately removed from the in-use priority of all associated virtual router instances.
The actual effect on the virtual router instance in-use priority value depends on the defined event priority and its delta or explicit nature.
The no form of the command deletes the specific port or channel monitoring event. The event may be removed at anytime. When the event is removed, the in-use priority of all associated virtual router instances will be re-evaluated. The events hold-set timer has no effect on the removal procedure.
Default
no port-down — No port down priority control events are defined.
Parameters
- port-id
-
The port ID of the port monitored by the VRRP priority control event.
The port-id can only be monitored by a single event in this policy. The port can be monitored by multiple VRRP priority control policies. A port and a specific channel on the port are considered to be separate entities. A port and a channel on the port can be monitored by separate events in the same policy.
Platforms
All
port-format
port-format
Syntax
port-format formatting
no port-format
Context
[Tree] (config>router>wpp>portals>portal port-format)
[Tree] (config>service>vprn>wpp>portals>portal port-format)
Full Context
configure router wpp portals portal port-format
configure service vprn wpp portals portal port-format
Description
This command specifies the encoding format of WPP port attribute.
The standard format is as follows:
<0 to 20 character system-name><1 character separator><2-digit slot><1-digit mda><2-digit port><4-digit top><5-digit bottom>
As a general rule, if a value is not present or is too large to fit in the field, is the field set to all zeros. The following rules apply to standard formats.
-
With a standard port, when the separator is a "-” character, the slot is the slot-id, mda is the mda-id, and the port is the port-id.
-
With an ESAT port, when the separator is a ":” character, the slot is the satellite-id, MDA is satellite slot-id, and the port is satellite port-id.
-
With a PXC port, when separator is a "#” character, the MDA is the PXC subport-id, and the port is the PXC port-id.
-
With a LAG port, the port is the lag-id.
-
With a connector port, the slot is the slot-id, the MDA is the mda-id, and the port is the connector-id.
The vendor-specific format is as follows:
With dot1q, append "%u” with the top vlan-id.
With qinq, append "%u.%u” with the top vlan-id and the bottom vlan-id.
As a general rule, there can be no trailing zeros. The string truncates if it becomes too long. 0 to 16 characters are allowed for the system name. The following rules apply to vendor-specific formats.
-
With a standard port, append "%s-%u/%u/%” with the system-name, slot-id, mda-id, and port-id.
-
With an ESAT port, append "%s-S%u/%u/%u” with the system-name, satellite-id, satellite-slot-id, and satellite-port-id.
-
With a PXC port, append "%s-P%u%c” with the system-name, PXC port-id, and PXC subport-id ? 'a' : 'b'.
-
With a LAG port, append "%s-L%u” with the system-name and lag-id.
-
With a connector port append "%s-%u%uc%u/%u” with the system-name, slot-id, mda-id, connector-id, and connector-port-id.
The no form of this command reverts to the default.
Default
port-format standard
Parameters
- formatting
-
Specifies the encoding format of the WPP port attribute.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
port-forward-logging
port-forward-logging
Syntax
[no] port-forward-logging
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes port-forward-logging)
Full Context
configure aaa isa-radius-policy acct-include-attributes port-forward-logging
Description
This command enables static or PCP port-forward logging via RADIUS. Port-forward logging is supported only in conjunction with the logging of port blocks.
The no form of the command disables static or PCP port-forward logging.
Default
no port-forward-logging
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-forwarding
port-forwarding
Syntax
port-forwarding
Context
[Tree] (config>service>nat port-forwarding)
Full Context
configure service nat port-forwarding
Description
Commands in this context configure NAT port forwarding parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-forwarding-dyn-block-reservation
port-forwarding-dyn-block-reservation
Syntax
[no] port-forwarding-dyn-block-reservation
Context
[Tree] (config>router>nat>outside>pool port-forwarding-dyn-block-reservation)
[Tree] (config>service>vprn>nat>outside>pool port-forwarding-dyn-block-reservation)
Full Context
configure router nat outside pool port-forwarding-dyn-block-reservation
configure service vprn nat outside pool port-forwarding-dyn-block-reservation
Description
This command will enable the reservation of the dynamic port blocks when the first port forward for the subscriber is created. The dynamic port bloc allocation is logged only if the block is being utilized (mapping are created). In other words, dynamic port block reservation due to the port forward creation but without any dynamic mapping, will not be logged.
The reserved port block will be released only when the last mapping in the block expires and there is not port forward associated with the subscriber. The de-allocation log (syslog or Radius) will be generated when the dynamic port block is completely released.
Dynamic port block reservation can be enabled only if the configured maximum number of subscriber per outside IP address is less or equal then the maximum number of configured port blocks per outside IP address.
Default
no port-forwarding-dyn-block-reservation
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-forwarding-range
port-forwarding-range
Syntax
port-forwarding-range [range-start] range-end
no port-forwarding-range
Context
[Tree] (config>service>vprn>nat>outside>pool port-forwarding-range)
[Tree] (config>router>nat>outside>pool port-forwarding-range)
Full Context
configure service vprn nat outside pool port-forwarding-range
configure router nat outside pool port-forwarding-range
Description
This command configures the lower and upper limit for port forwards in the ephemeral port space (wildcard port space) of all IP addresses in a NAT pool. A well-known port range (ports 1 to 1023) is always enabled for port forwards, and it cannot be disabled for pools in NAPT mode.
Pools in 1:1 mode do not support configured port forwards. These pools do not perform port translation and they automatically forward traffic initiated on the outside toward the inside.
Port 0 is always excluded from the port forwarding range.
The upper bound of the wildcard port range is reserved for port forwards. If the value for the range-start is not provided, the wildcard port range implicitly starts at 1024.
range-start 0 cannot be configured by an operator because it is reserved for 1:1 pools that do not support configured port forwards.
If you configure port-forwarding-range 3000, configures ports 1 to 3000 as port forwards. This implies that the well-known ports and wildcard ports are contiguous. If you configure port-forwarding-range 2000 3000, the router implicitly includes ports 1 to 1023, plus enables the wildcard port range 2000 to 3000, which is now disjoined from the well-known ports.
The range-start parameter has additional values that are configurable in the CLI. 0 is reserved for pools that do not support configured port forwards (those are 1:1 pools).
range-start 1 means that well-known ports and wildcard port forwards are contiguous. This is configured by omitting the range-start parameter and only configuring the range-end parameter.
The no form of this command disables the port forwards capability in the wildcard port range of all IP addresses in a NAT pool.
Default ranges in the range-start and range-end parameters in the MIB for the NAT pools that support port forwarding ranges are set to include only well-known ports, range-start 1 and range-end 1023.
Parameters
- range-start
-
Specifies the lower boundary of the wildcard port range reserved for port forwards. When configured, the value must be less than the range-end value.
- range-end
-
Specifies the upper boundary of the wildcard port range reserved for port forwards.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-forwarding-range
Syntax
port-forwarding-range range-end
no port-forwarding-range
Context
[Tree] (config>service>nat>nat-policy port-forwarding-range)
[Tree] (config>service>nat>firewall-policy port-forwarding-range)
Full Context
configure service nat nat-policy port-forwarding-range
configure service nat firewall-policy port-forwarding-range
Description
This command configures the end of the port range available for port forwarding. The start of the range is always equal to one.
The number of ports that can be configured is half of the available block => 64512 : 2 = 32256
In combination with port-forwarding-range the formulas are:
"max port-reservation blocks" = 65535 - "port-forwarding-range"
"max port-reservation ports" = (65535 - "port-forwarding-range") / 2
with:
the default min value for "port-forwarding-range" = 1023
Also, the same applies for max port-forwarding-range if the port-reservation is already configured:
"max port-forwarding-range" = 65535 - "port-reservation blocks"
"max port-forwarding-range" = 65535 - ("port-reservation ports" * 2)
The no form of the command reverts to the default.
Default
port-forwarding-range 1023
Parameters
- range-end
-
Specifies the end of the port range available for port forwarding.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy port-forwarding-range
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy port-forwarding-range
port-id
port-id
Syntax
[no] port-id
Context
[Tree] (config>router>if>dhcp>option>vendor-specific-option port-id)
Full Context
configure router interface dhcp option vendor-specific-option port-id
Description
This command enables sending of the port-id in the Nokia vendor specific suboption of the DHCP relay packet
The no form of this command disables the sending.
Default
no port-id
Platforms
All
port-id-subtype
port-id-subtype
Syntax
port-id-subtype {tx-if-alias | tx-if-name | tx-local}
Context
[Tree] (config>port>ethernet>lldp>dstmac port-id-subtype)
Full Context
configure port ethernet lldp dest-mac port-id-subtype
Description
This command specifies how to encode the PortID TLV transmit to the peer. The default setting tx-local (ifindex value) is required by some versions of the NSP NSM-P to properly build the Layer 2 topology map using LLDP. Changing this value to transmit the ifname ( tx-if-name) or ifAlias (tx-if-alias) in place of the ifindex (tx-local) may affect the ability of the NSP NFM-P to build the Layer 2 topology map using LLDP.
Default
port-id-subtype tx-local
Parameters
- tx-if-alias
-
Transmits the ifAlias String (subtype 1) that describes the port as stored in the IF-MIB, either user configured or the default entry (i.e. 10/100/Gig Ethernet SFP).
- tx-if-name
-
Transmits the ifName string (subtype 5) that describes the port as stored in the IF-MIB ifName info.
- tx-local
-
The interface ifIndex value (subtype 7) as the PortID.
Platforms
All
port-id-subtype
Syntax
port-id-subtype {tx-if-alias | tx-if-name | tx-local}
Context
[Tree] (config>lag>lldp-member-template>dstmac port-id-subtype)
Full Context
configure lag lldp-member-template dest-mac port-id-subtype
Description
This command configures the encoding of the PortID TLV that is transmitted to the peer. Some versions of the NSP NFM-P require the default setting tx-local (ifIndex value) to properly build the Layer 2 topology map using LLDP. Changing this value to transmit the ifName (tx-if-name) or ifAlias (tx-if-alias) in place of the ifIndex (tx-local) may affect the ability of the NSP NFM-P to build the Layer 2 topology map using LLDP.
Default
port-id-subtype tx-local
Parameters
- tx-if-alias
-
Keyword to transmit the ifAlias String (subtype 1), which describes the port as stored in the IF-MIB, either user configured or the default entry (for example, 10/100/Gig Ethernet SFP).
- tx-if-name
-
Keyword to transmit the ifName string (subtype 5), which describes the port as stored in the IF-MIB ifName information.
- tx-local
-
Keyword to transmit the interface ifIndex value (subtype 7) as the port ID.
Platforms
All
port-limits
port-limits
Syntax
port-limits
Context
[Tree] (config>service>nat>up-nat-policy port-limits)
[Tree] (config>service>nat>nat-policy port-limits)
[Tree] (config>service>nat>firewall-policy port-limits)
Full Context
configure service nat up-nat-policy port-limits
configure service nat nat-policy port-limits
configure service nat firewall-policy port-limits
Description
This command configures the port limits of this policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy port-limits
- configure service nat up-nat-policy port-limits
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy port-limits
port-list
port-list
Syntax
port-list port-list-name [create]
no port-list port-list-name
Context
[Tree] (config>app-assure>group port-list)
Full Context
configure application-assurance group port-list
Description
This command defines an AA group or partition named port-list, which contains a list of port numbers or port ranges. The port list is then referenced in AA policy app-filters, allowing increased flexibility in the use of server ports or HTTP proxy ports for application definition.
The no form of this command removes the list.
Parameters
- port-list-name
-
Specifies the name of the port list.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-list
Syntax
port-list port-list-name [create]
no port-list port-list-name
Context
[Tree] (config>filter>match-list port-list)
Full Context
configure filter match-list port-list
Description
This command creates a list of TCP/UDP/SCTP port values or ranges for match criteria in IPv4 and IPv6 ACL and CPM filter policies.
The no form of this command deletes the specified list.
Operational notes:
SCTP port match is supported in ACL filter policies only.
A port-list must contain only TCP/UDP/SCTP port values or ranges.
A TCP/UDP/SCTP port match list cannot be deleted if it is referenced by a filter policy.
See general description related to match-list usage in filter policies.
Parameters
- port-list-name
-
Specifies a string of up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.
Platforms
All
port-list
Syntax
port-list port-list-name [create]
no port-list port-list-name
Context
[Tree] (config>qos>match-list port-list)
Full Context
configure qos match-list port-list
Description
This command creates a list of port values or ranges for match criteria in QoS policies.
The no form of this command deletes the specified list.
Parameters
- port-list-name
-
Specifies a port list name, up to 32 characters of printable ASCII characters. If special characters are used, the string must be enclosed within double quotes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port-map
port-map
Syntax
port-map client-port-id primary primary-uplink-port-id [secondary secondary-uplink-port-id]
port-map client-port-id system-default
Context
[Tree] (config>system>satellite>eth-sat port-map)
Full Context
configure system satellite eth-sat port-map
Description
This command configures the mapping between a satellite client port and its associated uplink. This command allows both a primary and an optional secondary uplink to be configured.
If a secondary uplink is configured, it is used to forward traffic if the primary uplink is down for any reason.
Before an uplink can be used as either a primary or secondary uplink, it must be configured using the port-topology configuration command.
To return the uplink association to its default the port-map client-port-id system-default command should be used.
Parameters
- client-port-id
-
Specifies the satellite client port associated with the port mapping, in the format esat- id/slot/port.
- primary-uplink-port-id
-
Specifies the primary satellite uplink to be associated with the associate client port, in the format esat-id/slot/uport where id is 1 to 20.
- secondary-uplink-port-id
-
Specifies the secondary satellite uplink to be associated with the associate client port, in the format esat-id/slot/uport where id is 1 to 20.
- system-default
-
Specifies to set the port map to the system default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port-num
port-num
Syntax
port-num virtual-port-number
no port-num [virtual-port-number]
Context
[Tree] (config>service>vpls>spoke-sdp>stp port-num)
[Tree] (config>service>vpls>sap>stp port-num)
Full Context
configure service vpls spoke-sdp stp port-num
configure service vpls sap stp port-num
Description
This command configures the virtual port number which uniquely identifies a SAP within configuration bridge protocol data units (BPDUs). The internal representation of a SAP is unique to a system and has a reference space much bigger than the 12 bits definable in a configuration BPDU. STP takes the internal representation value of a SAP and identifies it with its own virtual port number that is unique to every other SAP defined on the TLS. The virtual port number is assigned at the time that the SAP is added to the TLS. Since the order that the SAP was added to the TLS is not preserved between reboots of the system, the virtual port number may change between restarts of the STP instance.
The virtual port number cannot be administratively modified.
Platforms
All
port-overall-rate
port-overall-rate
Syntax
port-overall-rate packet-rate-limit [low-action-priority]
no port-overall-rate
Context
[Tree] (config>sys>security>cpu-protection port-overall-rate)
Full Context
configure system security cpu-protection port-overall-rate
Description
This command configures a per-port overall rate limit for CPU protection.
Default
port-overall-rate max
Parameters
- packet-rate-limit
-
Specifies an overall per-port packet arrival rate limit in packets per second.
- action-low-priority
-
Marks packets that exceed the rate as low-priority (for preferential discard later if there is congestion in the control plane) instead of discarding them immediately.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-7s, 7750 SR-14s, 7950 XRS
port-parent
port-parent
Syntax
parent [weight weight] [level level] [ cir-weight cir-weight] [cir-level cir-level]
no parent
Context
[Tree] (config>qos>sap-egress>dynamic-queue port-parent)
Full Context
configure qos sap-egress dynamic-queue port-parent
Description
This command configures the queue treatment by the port parent that governs the available bandwidth for the queue. When multiple queues share a child status with the parent port, the weight and level options define how this queue contends with the other children for the above-CIR parent bandwidth. The cir-weight and cir-level options specify the weight the queue uses for the within-CIR port priority.
Parameters
- weight
-
Specifies the relative weight of this queue in comparison to other child queues while vying for above-CIR priority level bandwidth on the parent scheduler. Any queues defined as weighted receive no parental bandwidth, until all strict queues and schedulers on the parent have reached their maximum bandwidth or are idle. In this manner, weighted children are considered to be the lowest priority.
- level
-
Specifies the priority level of the queue (as compared to other competing schedulers and queues) used to feed to the parent, for above-CIR offered load bandwidth passes.
- cir-weight
-
Specifies the weight the queue uses at the within-CIR port priority level. This applies to any charging statistics also. The weight is specified as an integer value from 0 to 100, with 100 being the highest weight. When the cir-weight option is set to 0 (the default), the queue does not receive bandwidth during the port scheduler's within-CIR passes and the cir-level option is ignored. If the cir-weight is 1 or greater, the cir-level option comes into play.
- cir-level
-
Specifies the priority level of the queue (as compared to other competing schedulers and queues) used to fed to the port parent, for within-CIR offered load bandwidth passes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
port-parent
Syntax
port-parent [weight weight] [ level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context
[Tree] (config>qos>sap-egress>policer port-parent)
Full Context
configure qos sap-egress policer port-parent
Description
This command specifies whether this SAP egress policer feeds off a port-level scheduler. When configured, the policer is parented by a port-level scheduler. This requires that policers-hqos-manageable be configured in the SAP egress QoS policy. This command and the SAP egress policer scheduler-parent and the parent commands are mutually exclusive.
The port-parent command defines a child/parent association between an egress policer and a port-based scheduler or between an intermediate service scheduler and a port-based scheduler. The port-parent command allows for a set of within-CIR and above-CIR parameters that define the port priority levels and weights for the policer. If the port-parent command is executed without any parameters, the default parameters are used.
In this context, the port-parent command and the scheduler-parent command (used to create a parent/child association between a queue and an intermediate scheduler) are mutually exclusive. Executing a port-parent command when a scheduler-parent definition exists causes the current intermediate scheduler association to be removed and replaced by the defined port-parent association. Executing a scheduler-parent command when a port-parent definition exists causes the port scheduler association to be removed and replaced by the defined intermediate scheduler association.
Changing the parent context on a SAP egress policy policer may cause a SAP or subscriber or a multiservice site context of the policer (policy associated with a SAP or subscriber profile or a multiservice site) to enter an orphaned state. If an instance of a policer is created on a port or channel that does not have a port scheduler enabled, and the SAP egress policy creating the policer has a port parent association, the policer will be allowed to run according to its own rate parameters and will not be controlled by a virtual scheduling context. If an instance of a policer is on a port or channel that has a port scheduler configured and the SAP egress policy defines the policer as having a non-existent intermediate scheduler parent, the policer will be treated as an orphan and will be handled according to the current orphan behavior on the port scheduler.
The no form of this command removes a port scheduler parent association for the policer. When removed, if a port scheduler is defined on the port on which the policer instance exists, the policer will be treated as orphaned to the port scheduler.
Default
no port-parent
Parameters
- weight weight
-
Specifies the weight that the policer will use at the above-CIR port priority level (defined by the level parameter).
All weight values from all weighted active policers, queues, and schedulers with a common port parent are added together. Then, each individual active weight is divided by the total to determine the percentage of remaining bandwidth provided to the policer, queue, or scheduler after the higher priority level children have been serviced. A weight is considered to be active when the applicable policer, queue, or scheduler has not reached its maximum rate and still has packets to transmit.
The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the weight parameter is set to a value of 0, the policer receives bandwidth only after other children with a non-zero weight at this level.
- level level
-
Specifies the port priority that the policer uses to receive bandwidth for its above-CIR offered load.
- cir-weight cir-weight
-
Specifies the weight that the policer uses at the within-CIR port priority level (defined by the cir-level parameter).
All cir-weight values from all weighted active policers, queues, and schedulers with a common port parent are added together. Then, each individual active weight is divided by the total to determine the percentage of remaining bandwidth provided to the policer, queue, or scheduler after the higher priority level children have been serviced. A weight is considered to be active when the applicable policer, queue, or scheduler has not reached its maximum rate and still has packets to transmit.
The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0, the policer receives bandwidth only after the other children with a non-zero weight at this level.
- cir-level cir-level
-
Specifies the port priority that the policer will use to receive bandwidth for its within-CIR offered load. If the cir-level parameter is set to a value of 0 (the default value), the policer does not receive bandwidth during the port schedulers within-CIR pass and the cir-weight parameter is ignored. If the cir-level parameter is 1 or greater, the cir- weight parameter is used.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-1s, 7750 SR-1se, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, VSR
port-parent
Syntax
port-parent [weight weight] [ level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context
[Tree] (config>qos>sap-egress>queue port-parent)
Full Context
configure qos sap-egress queue port-parent
Description
This command specifies whether this queue feeds off a port-level scheduler. When configured, this SAP egress queue is parented by a port-level scheduler. This object is mutually exclusive with SAP egress queue parent. Only one kind of parent is allowed.
The port-parent command defines a child/parent association between an egress queue and a port-based scheduler or between an intermediate service scheduler and a port-based scheduler. The port-parent command allows for a set of within-CIR and above-CIR parameters that define the port priority levels and weights for the queue or scheduler. If the port-parent command is executed without any parameters, the default parameters are assumed.
In this context, the port-parent command is mutually exclusive to the parent command (used to create a parent/child association between a queue and an intermediate scheduler). Executing a port-parent command when a parent definition is in place causes the current intermediate scheduler association to be removed and replaced by the defined port-parent association. Executing a parent command when a port-parent definition exists causes the port scheduler association to be removed and replaced by the defined intermediate scheduler name.
Changing the parent context on a SAP egress policy queue may cause a SAP or subscriber or multiservice site context of the queue (policy associated with a SAP or subscriber profile or multiservice site) to enter an orphaned state. If an instance of a queue is created on a port or channel that does not have a port scheduler enabled and the sap-egress policy creating the queue has a port-parent association, the queue will be allowed to run according to its own rate parameters and will not be controlled by a virtual scheduling context. If an instance of a queue is on a port or channel that has a port scheduler configured and the sap-egress policy defines the queue as having a non-existent intermediate scheduler parent, the queue will be treated as an orphan and will be handled according to the current orphan behavior on the port scheduler.
The no form of this command removes a port scheduler parent association for the queue or scheduler. If a port scheduler is defined on the port on which the queue or scheduler instance exists, the queue or scheduler will become orphaned if an port scheduler is configured on the egress port of the queue or scheduler.
Default
no port-parent
Parameters
- weight weight
-
Specifies the weight the queue or scheduler will use at the above-CIR port priority level (defined by the level parameter).
- level level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its above-CIR offered-load.
- cir-weight cir-weight
-
Specifies the weight the queue or scheduler will use at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
- cir-level cir-level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
port-parent
Syntax
port-parent [weight weight] [ level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context
[Tree] (config>qos>network-queue>queue port-parent)
Full Context
configure qos network-queue queue port-parent
Description
This command specifies whether this queue feeds off a port-level scheduler. For the network-queue policy context, only the port-parent command is supported. When a port scheduler exists on the port, network queues without a port-parent association will be treated as an orphan queue on the port scheduler and treated according to the current orphan behavior on the port scheduler. If the port-parent command is defined for a network queue on a port without a port scheduler defined, the network queue will operate as if a parent association does not exist. When a port scheduler policy is associated with the egress port, the port-parent command will come into effect.
When a network-queue policy is associated with an FP for ingress queue definition, the port-parent association of the queues is ignored.
The no form of this command removes a port scheduler parent association for the queue or scheduler. If a port scheduler is defined on the port then the queue or scheduler instance exists, the queue or scheduler will become orphaned.
Default
no port-parent
Parameters
- weight weight
-
Specifies the weight the queue or scheduler will use at the above-CIR port priority level (defined by the level parameter).
- level level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its above-CIR offered-load.
- cir-weight cir-weight
-
Specifies the weight the queue or scheduler will use at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0, the queue or scheduler does not receive bandwidth during the port scheduler’s within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter is used.
- cir-level cir-level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port scheduler’s within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
port-parent
Syntax
port-parent [weight weight] [ level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context
[Tree] (config>qos>qgrps>egr>qgrp>queue port-parent)
Full Context
configure qos queue-group-templates egress queue-group queue port-parent
Description
This command defines the port scheduling parameters used to control the queue’s behavior when a virtual egress port scheduling is enabled where the egress queue group template is applied. The port-parent command follows the same behavior and provisioning characteristics as the parent command in the SAP egress QoS policy. The port-parent command and the parent command are mutually exclusive.
The no form of this command removes the values from the configuration.
Parameters
- weight weight
-
Specifies the weight the queue or scheduler will use at the above-CIR port priority level (defined by the level parameter).
- level level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its above-CIR offered-load.
- cir-weight cir-weight
-
Specifies the weight the queue or scheduler will use at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter is used.
- cir-level cir-level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter is used.
Platforms
All
port-parent
Syntax
port-parent [weight weight] [ level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context
[Tree] (config>qos>scheduler-policy>tier>scheduler port-parent)
Full Context
configure qos scheduler-policy tier scheduler port-parent
Description
The port-parent command defines a child/parent association between an egress scheduler and a port-based scheduler, or between an intermediate service scheduler and a port-based scheduler. The port-parent command allows for a set of within-CIR and above-CIR parameters that define the port priority levels and weights for the scheduler. If the port-parent command is executed without any parameters, the default parameters are assumed.
In this context, the port-parent command and the parent command (used to create a parent/child association to an intermediate scheduler) are mutually exclusive. Executing a port-parent command when a parent definition is in place causes the current intermediate scheduler association to be removed and replaced by the defined port-parent association. Executing a parent command when a port-parent definition exists causes the port scheduler association to be removed and replaced by the defined intermediate scheduler name.
Changing the parent context on a SAP egress policy policer or queue may cause a SAP or subscriber context of the policer or queue (policy associated with a SAP or subscriber profile) to enter an orphaned state. If an instance of a policer or queue is created on a port or channel that does not have a port scheduler enabled and the sap-egress policy creating the policer queue has a port-parent association, the policer or queue will be allowed to run according to its own rate parameters and will not be controlled by a virtual scheduling context. If an instance of a policer or queue is on a port or channel that has a port scheduler configured and the sap-egress policy defines the policer or queue as having a non-existent intermediate scheduler parent, the policer or queue will be treated as an orphan and will be handled according to the current orphan behavior on the port scheduler.
The no form of this command removes a port scheduler parent association for the scheduler. If a port scheduler is defined on the port that the scheduler instance exists, the scheduler will become orphaned if an port scheduler is configured on the egress port of the queue or scheduler.
Default
no port-parent
Parameters
- weight weight
-
Specifies the weight the queue or scheduler will use at the above-CIR port priority level (defined by the level parameter).
- level level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its above-CIR offered-load.
- cir-weight cir-weight
-
Specifies the weight the queue or scheduler will use at the within-CIR port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a value of 0, the queue or scheduler does not receive bandwidth during the port scheduler’s within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
- cir-level cir-level
-
Specifies the port priority the queue or scheduler will use to receive bandwidth for its within-CIR offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port scheduler’s within-CIR pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or greater, the cir-level parameter comes into play.
Platforms
All
port-policy
port-policy
Syntax
port-policy [port-policy]
no port-policy
Context
[Tree] (config>isa>wlan-gw-group port-policy)
Full Context
configure isa wlan-gw-group port-policy
Description
This command configures the port policy of this WLAN Gateway ISA group. If a port policy is associated with a WLAN Gateway ISA group, ports created for this group can take applicable configuration from that port policy. This port policy is applicable to those ports that take part in the per-tunnel QoS processing.
The no form of the command removes the port-policy name from the configuration.
Default
no port-policy
Parameters
- port-policy
-
Specifies the port policy of this WLAN Gateway ISA group, up to 32 characters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-policy
Syntax
port-policy port-policy-name [create]
no port-policy port-policy-name
Context
[Tree] (config port-policy)
Full Context
configure port-policy
Description
This command either creates a new port-policy with create parameter or enters the configuration context of an existing port-policy.
The no form of this command removes the port policy name from the configuration.
Parameters
- port-policy-name
-
Specifies the name of port-policy up to 32 characters.
- create
-
Creates the port-policy instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-policy
Syntax
port-policy policy-name
no port-policy
Context
[Tree] (config>isa>lns-group port-policy)
Full Context
configure isa lns-group port-policy
Description
This command enables policies referenced in the config>port-policy context to be created under ports. These are the ports that link the carrier IOM to the ISA, and are hidden within the system (they cannot be created through the CLI). They are created automatically. Use the show port command to view information.
Currently only the port scheduler policy is supported. Each lns-esm port in the lns-group receives an independent port scheduler instance. The port schedulers are instantiated in the carrier IOM on the lns-esm ports that carry PPPoE traffic in the downstream direction towards the ISA before the PPPoE traffic is L2TP encapsulated.
The no form of the command removes the policy name from the configuration.
Default
no port-policy
Parameters
- policy-name
-
Specifies the port policy of this LNS group, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-range-block
port-range-block
Syntax
[no] port-range-block
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes port-range-block)
Full Context
configure aaa isa-radius-policy acct-include-attributes port-range-block
Description
This command enables the inclusion of the NAT port range block attributes.
The no form of the command excludes NAT port range block attributes.
Default
no port-range-block
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-recorder
port-recorder
Syntax
[no] port-recorder
Context
[Tree] (debug>app-assure>group port-recorder)
Full Context
debug application-assurance group port-recorder
Description
This commands allows to stop or start the http-host-recorder. To reset the recorded values execute shutdown followed by no shutdown.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-redirect-group
port-redirect-group
Syntax
port-redirect-group {queue queue-id | policer policer-id [queue queue-id]}
no port-redirect-group
Context
[Tree] (config>qos>network>egress>fc port-redirect-group)
Full Context
configure qos network egress fc port-redirect-group
Description
This command is used to redirect the FC of a packet of a pseudowire (PW) or network IP interface to an egress port queue group.
It defines the mapping of an FC to a queue ID or a policer ID and a queue ID and redirects the lookup of the queue or policer of the same ID in some egress port queue-group instance. However, the queue-group name and instance are explicitly provided only at the time the network QoS policy is applied to egress context of a spoke-sdp or a network IP interface.
The no version of this command removes the redirection of the FC.
Parameters
- queue-id
-
This parameter must be specified when executing the port-redirect-group command. The specified queue-id must exist within the egress port queue group on each IP interface where the network QoS policy is applied.
- policer id
-
The specified policer-id must exist within the queue-group template applied to the ingress context of the forwarding plane.
Platforms
All
port-reservation
port-reservation
Syntax
port-reservation blocks num-blocks
port-reservation ports num-ports
no port-reservation
Context
[Tree] (config>router>nat>outside>pool port-reservation)
[Tree] (config>service>vprn>nat>outside>pool port-reservation)
Full Context
configure router nat outside pool port-reservation
configure service vprn nat outside pool port-reservation
Description
This command configures the size of the port block that will be assigned to a host that is served by this pool. The number of ports configured are available to UDP, TCP, and ICMP (as identifiers).
Parameters
- num-blocks
-
Specifies the number of port blocks per IP address. Setting this parameter to one (1) for large scale NAT enables 1:1 NAT for IP addresses in this pool.
- num-ports
-
Specifies the number of ports per block.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-reservation
Syntax
port-reservation num-ports
no port-reservation
Context
[Tree] (config>router>nat>outside>pool>deterministic port-reservation)
[Tree] (config>service>vprn>nat>outside>pool>deterministic port-reservation)
Full Context
configure router nat outside pool deterministic port-reservation
configure service vprn nat outside pool deterministic port-reservation
Description
This command is applicable only to deterministic NAT. It configures the number of deterministic ports per subscriber (for example a subscriber is an inside IP address in LSN44 or IPv6 address or prefix in DS-Lite). Once this command is enabled, the pool will transition into deterministic mode of operation. This means that the subscribers can use dynamic port-blocks in the pool only as a mean to expand the range of originally assigned deterministic ports. A pool with such property is referred to as deterministic pool. However, deterministic NAT and non-deterministic NAT cannot use the same pool simultaneously.
All subscribers in deterministic pool are pre-mapped during the configuration phase to outside IP addresses and deterministic port-blocks. Because of this, the deterministic pool cannot be oversubscribed with subscribers (first-come, first-served).
Once the deterministic pool becomes operational (no shutdown) a log is created. The same applies if the pool is disabled (shutdown). As a result of this one-time logging, there will be no additional logging when a subscriber starts using ports from the pre-assigned deterministic port block. This drastically reduces the logging overhead. However, when a deterministic port block is expanded by a dynamic port block, a log will be created on any allocation/de-allocation of the dynamic port block. The logs are also created for static port forwards (including PCP).
The number of subscribers per outside IP address (subscriber-limit) multiplied by the number of deterministic ports per subscriber (port-reservation) will determine the port range of an outside IP address that will be dedicated to deterministic mappings. The number of subscribers per outside IP address in deterministic NAT must be power of 2 (2^n). Once the deterministic ports are allocated, the dynamic ports are carved out of the remaining port space of the same outside IP address according to the existing port-reservation command under the same hierarchy,
Parameters
- num-ports
-
Specifies the number of ports in a deterministic port block that is allocated and dedicated to a single subscribers during the configuration phase.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-reservation
Syntax
[no] port-reservation
Context
[Tree] (config>service>nat>pcp-server-policy>option port-reservation)
Full Context
configure service nat pcp-server-policy option port-reservation
Description
This command enables/disables support for the port-reservation option.
Default
no port-reservation
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-role
port-role
Syntax
[no] port-role
Context
[Tree] (debug>service>id>stp port-role)
Full Context
debug service id stp port-role
Description
This command enables STP debugging for changes in port roles.
Platforms
All
port-scheduler-policy
port-scheduler-policy
Syntax
port-scheduler-policy port-scheduler-policy-name
no port-scheduler-policy
Context
[Tree] (config>port>ethernet>access>egress>vport port-scheduler-policy)
Full Context
configure port ethernet access egress vport port-scheduler-policy
Description
This command specifies the destination and organization strings to be used for matching subscriber hosts with this Vport.
The parent Vport of a subscriber host queue, which has the port-parent option enabled, is determined by matching the destination string dest string associated with the subscriber and the organization string org string associated with the subscriber host with the strings defined under a Vport on the port associated with the subscriber.
If a given subscriber host policers or queue does not have the port-parent option enabled, it is foster-parented to the Vport used by this subscriber and which is based on matching the dest string and org string. If the subscriber could not be matched with a Vport on the egress port, the host policer or queue will not be bandwidth controlled and competes for bandwidth directly based on its own PIR and CIR parameters.
By default, a subscriber host policer or queue with the port-parent option enabled is scheduled within the context of the port’s port scheduler policy.
The agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate or port-scheduler-policy involves removing the existing command and applying the new command. Applying a scheduler policy to a Vport is only applicable to Ethernet interfaces.
The no form of this command removes the port-scheduler-policy-name from the configuration.
The agg-rate rate, port-scheduler-policy and scheduler-policy commands are mutually exclusive. Changing between the use of a scheduler policy and the use of an agg-rate/port-scheduler-policy involves removing the existing command and applying the new command.
The no form of this command reverts to the default.
Parameters
- port-scheduler-policy-name
-
Specifies an existing port-scheduler-policy configured in the config>qos context.
Platforms
All
port-scheduler-policy
Syntax
port-scheduler-policy port-scheduler-policy-name
no port-scheduler-policy
Context
[Tree] (config>isa>aa-grp>qos>egress>from-subscriber port-scheduler-policy)
[Tree] (config>isa>aa-grp>qos>egress>to-subscriber port-scheduler-policy)
Full Context
configure isa application-assurance-group qos egress from-subscriber port-scheduler-policy
configure isa application-assurance-group qos egress to-subscriber port-scheduler-policy
Description
This command assigns an existing port scheduler policy as applicable to the specific application assurance group traffic.
Default
no port-scheduler-policy
Parameters
- port-scheduler-policy-name
-
Specifies the name of an existing port scheduler policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-scheduler-policy
Syntax
port-scheduler-policy port-scheduler-name [ create]
no port-scheduler-policy port-scheduler-name
Context
[Tree] (config>qos port-scheduler-policy)
Full Context
configure qos port-scheduler-policy
Description
When a port scheduler has been associated with an egress port, it is possible to override the following parameters:
-
The max-rate allowed for the scheduler
-
The maximum rate for each priority level (1 to 8)
-
The cir associated with each priority level (1 to 8)
The orphan priority level (level 0) has no configuration parameters and cannot be overridden.
The no form of this command removes a port scheduler policy from the system. If the port scheduler policy is associated with an egress port or channel, the command will fail.
Parameters
- port-scheduler-name
-
Specifies an existing port scheduler name. Each port scheduler must be uniquely named within the system and can be up to 32 ASCII characters.
Platforms
All
port-scheduler-policy
Syntax
port-scheduler-policy src-name dst-name [overwrite]
Context
[Tree] (config>qos>copy port-scheduler-policy)
Full Context
configure qos copy port-scheduler-policy
Description
This command copies existing QoS policy entries for a QoS policy to another QoS policy.
The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.
If overwrite is not specified, an error will occur if the destination policy exists.
Parameters
- src-name dst-name
-
Indicates that the source policy and the destination policy are port scheduler policy IDs. Specify the source policy that the copy command will attempt to copy from and specify the destination policy name to which the command will copy a duplicate of the policy.
- overwrite
-
Forces the destination policy name to be copied as specified. When forced, everything in the existing destination policy will be completely overwritten with the contents of the source policy.
Platforms
All
port-set
port-set
Syntax
[no] port-set
Context
[Tree] (config>service>nat>pcp-server-policy>option port-set)
Full Context
configure service nat pcp-server-policy option port-set
Description
This command enables PORT_SET option support. When this command is disabled, the PCP uses a plain MAP option to allocate a single port at a time. This is default behavior. Instead of asking for each individual port in multiple requests through the MAP option, this port-set option allows individual ports to ask the SR OS for a set of ports at once in a single request.
The no form of this command disables PORT_SET option support.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-state
port-state
Syntax
[no] port-state
Context
[Tree] (debug>service>id>stp port-state)
Full Context
debug service id stp port-state
Description
This command enables STP debugging for port states.
The no form of the command disables debugging.
Platforms
All
port-template
port-template
Syntax
port-template template-name sat-type sat-type [create]
no port-template template-name
Context
[Tree] (config>system>satellite port-template)
Full Context
configure system satellite port-template
Description
This command creates a new port template context to define the port usage for a specific satellite type. A port template is specific to the specified satellite type. Port templates must be configured separately using different template names for each different satellite chassis type.
The no form of this command deletes the specified port template.
Parameters
- template-name
-
Specifies the name for the associated port template. This value must be unique in the network.
- sat-type
-
Specifies the type of satellite chassis associated with the port-template.
- create
-
Creates a new port template.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port-threshold
port-threshold
Syntax
port-threshold value [action { dynamic-cost | static-cost | down}] [ cost static-cost]
no port-threshold
Context
[Tree] (config>lag port-threshold)
Full Context
configure lag port-threshold
Description
This command configures the behavior for the Link Aggregation Group (LAG) if the number of operational links is equal to or below a threshold level.
Nokia recommends that operators use the weight-threshold or hash-weight-threshold command instead of the port-threshold command to control LAG operational status. For example, when 10GE and 100GE ports are mixed in a LAG, each 10GE port will have a weight of 1, while each 100GE port will have a weight of 10.
The weight-threshold or hash-weight-threshold command can also be used for LAGs with all ports of equal speed to allow a common operational model. For example, each port has a weight of 1 to mimic port-threshold and its related configuration.
The no form of this command reverts to the default values.
Default
port-threshold 0 action down
Parameters
- value
-
Specifies the decimal integer threshold number of operational links for the LAG at or below which the configured action is invoked. If the number of operational links exceeds the port-threshold value, any action taken for being below the threshold value will cease.
- action
-
Specifies the action to take if the number of active links in the LAG is at or below the threshold value.
- dynamic-cost
-
Specifies that dynamic costing is activated. As a result, the LAG remains operationally up with a cost relative to the number of operational links. The link is only regarded as operationally down when all links in the LAG are down.
- static-cost
-
Specifies that static costing is activated. As a result, the LAG remains operationally up with the configured cost, regardless of the number of operational links. The link is only regarded as operationally down when all links in the LAG are down.
- down
-
Specifies that LAG is brought operationally down if the number of operational links is equal to or less than the configured threshold value. The LAG is only regarded as up once the number of operational links exceeds the configured threshold value.
- static-cost
-
Specifies decimal integer static cost of the LAG.
Platforms
All
port-time
port-time
Syntax
[no] port-time
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes port-time)
Full Context
configure aaa isa-radius-policy acct-include-attributes port-time
Description
This command enables the Alc-Nat-Port-Time RADIUS attribute, which is used to record the duration of a port-block or port-forward allocated for a NAT subscriber.
The no form of this command disables the Alc-Nat-Port-Time RADIUS attribute.
Default
no port-time
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port-topology
port-topology
Syntax
port-topology
Context
[Tree] (config>system port-topology)
Full Context
configure system port-topology
Description
This parameter creates or edits the context to configure intra-node port connections.
Default
disabled
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
port-type
port-type
Syntax
port-type lag-port-type
no port-type
Context
[Tree] (config>lag port-type)
Full Context
configure lag port-type
Description
This command configures the port type for the link aggregation group.
The no form of this command reverts to the default.
Default
port-type standard
Parameters
- lag-port-type
-
Specifies the type of ports allowed in this LAG.
Platforms
7750 SR-7/12/12e
port-xc
port-xc
Syntax
port-xc
Context
[Tree] (config port-xc)
Full Context
configure port-xc
Description
Commands in this context configure port-cross connect functionality.
Platforms
All
port1
port1
Syntax
port1 {eq | neq} port-num
no port1
Context
[Tree] (debug>app-assure>group>traffic-capture>match port1)
Full Context
debug application-assurance group traffic-capture match port1
Description
This command configures debugging on port 1.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
port2
port2
Syntax
port2 {eq | neq} port-num
no port2
Context
[Tree] (debug>app-assure>group>traffic-capture>match port2)
Full Context
debug application-assurance group traffic-capture match port2
Description
This command configures debugging on port 2.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
portal
portal
Syntax
portal router router-instance name wpp-portal-name
no portal
Context
[Tree] (config>service>ies>sub-if>grp-if>wpp portal)
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>wpp portal)
[Tree] (config>service>vprn>sub-if>grp-if>wpp portal)
Full Context
configure service ies subscriber-interface group-interface wpp portal
configure subscriber-mgmt local-user-db ipoe host wpp portal
configure service vprn subscriber-interface group-interface wpp portal
Description
This command specifies the web portal server that system talks to for the hosts on the group-interface. This command is mutually exclusive with the portal-group command.
The no form of this command removes the router instance or portal name from the configuration.
Parameters
- router-instance
-
Specifies the virtual router instance.
- wpp-portal-name
-
Specifies the name of the web portal server up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal
Syntax
[no] portal router router-instance name wpp-portal-name
Context
[Tree] (config>aaa>wpp>portal-groups>portal-group portal)
Full Context
configure aaa wpp portal-groups portal-group portal
Description
This command configures the portal for this portal group.
Parameters
- router-instance
-
Specifies the virtual router instance.
- wpp-portal-name
-
Specifies the name of the web portal server up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal
Syntax
[no] portal wpp-portal-name
Context
[Tree] (debug>router>wpp portal)
Full Context
debug router wpp portal
Description
This command enables WPP debugging for the specified WPP portal.
Parameters
- wpp-portal-name
-
Specifies the WPP portal name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal
Syntax
[no] portal
Context
[Tree] (config>subscr-mgmt>wlan-gw>ue-query>state portal)
Full Context
configure subscriber-mgmt wlan-gw ue-query state portal
Description
This command enables matching on UEs in a portal state.
The no form of this command disables matching on UEs in a portal state, unless all state matching is disabled.
Default
no portal
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
portal-group
portal-group
Syntax
portal-group portal-group-name
no portal-group
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>wpp portal-group)
Full Context
configure subscriber-mgmt local-user-db ipoe host wpp portal-group
Description
This command configures the WPP portal group name. This command is mutually exclusive with the portal command.
Parameters
- portal-group-name
-
Specifies the WPP portal group name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal-group
Syntax
portal-group portal-group-name [create]
no portal-group portal-group-name
Context
[Tree] (config>aaa>wpp>portal-groups portal-group)
Full Context
configure aaa wpp portal-groups portal-group
Description
This command creates a new portal group or enters the configuration context of an existing port group.
Parameters
- portal-group-name
-
Specifies the portal group name up to 32 characters.
- create
-
Keyword required to create the configuration context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal-group
Syntax
portal-group portal-group-name
no portal-group
Context
[Tree] (config>service>vprn>sub-if>grp-if>wpp portal-group)
[Tree] (config>service>ies>sub-if>grp-if>wpp portal-group)
Full Context
configure service vprn subscriber-interface group-interface wpp portal-group
configure service ies subscriber-interface group-interface wpp portal-group
Description
This command specifies the WPP portal group for the subscriber interface. This command is mutually exclusive with the portal command.
The no form of this command removes the name from the service configuration.
Parameters
- portal-group-name
-
Specifies the portal group name up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal-groups
portal-groups
Syntax
portal-groups
Context
[Tree] (config>aaa>wpp portal-groups)
Full Context
configure aaa wpp portal-groups
Description
Commands in this context configure portal group parameters for WPP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
portal-hold-time
portal-hold-time
Syntax
portal-hold-time seconds
no portal-hold-time
Context
[Tree] (config>subscr-mgmt>http-rdr-plcy portal-hold-time)
Full Context
configure subscriber-mgmt http-redirect-policy portal-hold-time
Description
This command configures the time for which the forwarding state applicable during redirect phase is held in the system, after the user has been authenticated on the portal. This allows the HTTP response from the portal to be forwarded back on the existing connection.
Parameters
- seconds
-
Specifies how long the system holds on to re-direct forwarding resources of a subscriber, after it has left the re-direct portal.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
portals
portals
Syntax
portals
Context
[Tree] (config>service>vprn>wpp portals)
[Tree] (config>router>wpp portals)
Full Context
configure service vprn wpp portals
configure router wpp portals
Description
Commands in this context configure WPP portal server parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ports
ports
Syntax
ports
Context
[Tree] (config>qos>fp-resource-policy ports)
Full Context
configure qos fp-resource-policy ports
Description
This command enters the ports context.
Platforms
7750 SR-1, 7750 SR-s
ports
Syntax
ports num-ports
no ports
Context
[Tree] (config>service>nat>up-nat-policy>port-block-extensions ports)
Full Context
configure service nat up-nat-policy port-block-extensions ports
Description
This command configures the number of ports in extended port blocks for the NAT subscriber.
Parameters
- num-ports
-
Specifies the number of ports per extended port block.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
positive-app-id
positive-app-id
Syntax
positive-app-id
Context
[Tree] (config>app-assure>group>ip-id-asst positive-app-id)
Full Context
configure application-assurance group ip-identification-assist positive-app-id
Description
Commands in this context implement the positive application identification mechanism, which monitors the correlations between IP addresses and applications identified with a high degree of confidence independently of any IP identification assist mechanism.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
post-policer-mapping
post-policer-mapping
Syntax
post-policer-mapping mapping-policy-name [ create]
no post-policer-mapping mapping-policy-name
Context
[Tree] (config>qos post-policer-mapping)
Full Context
configure qos post-policer-mapping
Description
This command configures a post-policer mapping policy which is used to remap a packet's forwarding class and profile state to another forwarding class and profile state for post-policer traffic.
A post-policer mapping policy is created without any forwarding class or profile remapping statements. If an empty policy is applied to a SAP-egress QoS policy, no remapping occurs.
The no form of this command deletes the post-policer mapping policy. A post-policer mapping policy can only be deleted if there are no references to it.
Parameters
- mapping-policy-name
-
Specifies the name of the post-policer mapping policy, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
post-policer-mapping
Syntax
post-policer-mapping src-name dst-name [ overwrite]
Context
[Tree] (config>qos>copy post-policer-mapping)
Full Context
configure qos copy post-policer-mapping
Description
This command copies an existing post-policer mapping policy to another policy name.
The copy command is used to create new policies using existing policies and also allows bulk modifications to an existing policy with the use of the overwrite keyword.
Parameters
- src-name
-
Specifies the source policy name that the copy command attempts to copy from.
- dst-name
-
Specifies the destination policy name to which the command copies a duplicate of the policy.
- overwrite
-
Specifies that the existing destination policy is to be replaced. Everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy name exists.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
post-policer-mapping
Syntax
post-policer-mapping mapping-policy-name
no post-policer-mapping
Context
[Tree] (config>qos>sap-egress post-policer-mapping)
Full Context
configure qos sap-egress post-policer-mapping
Description
This command applies a post-policer mapping policy in a SAP egress QoS policy. The policy contains forwarding class and profile remapping statements, which remap the forwarding class and profile state of an egress policed packet (the profile being the resulting profile after the packet has been processed by the egress policer) to another forwarding class and profile.
The remapping applies to all policers within the SAP egress QoS policy, including regular child policers and policers configured in an IP/IPv6 criteria action statement, except for dynamic policers.
Post-policer mapping is supported on FP3- and higher-based hardware, with the exception of the 7750 SR-a4/a8, which does not support egress policers resulting in the policy being ignored.
The no form of this command deletes the post-policer mapping policy from the SAP egress QoS policy.
Parameters
- mapping-policy-name
-
Specifies the name of the post-policer mapping policy, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
power
power
Syntax
power power-state
Context
[Tree] (config>system>bluetooth power)
Full Context
configure system bluetooth power
Description
This command sets the operating mode of the Bluetooth module. This can be powered off or powered on but requires the pairing button to initiate the pairing operation, or powered on and continuously pairing.
The pairing-button setting also impacts how pairing operations work.
Default
power off
Parameters
- power-state
-
Specifies the power state.
Platforms
7750 SR-1, 7750 SR-s, 7950 XRS-20e
power-priority-level
power-priority-level
Syntax
power-priority-level priority
no power-priority-level
Context
[Tree] (config>card>xiom>mda power-priority-level)
[Tree] (config>card>mda power-priority-level)
Full Context
configure card xiom mda power-priority-level
configure card mda power-priority-level
Description
This command sets the power priority value for an XMA or MDA-s on platforms that support intelligent power management.
Default
power-priority-level 150
Parameters
- priority
-
Specifies the power priority level. An operator must assign a priority value to each XMA or MDA-s using a range of number from 1 to 200. The lowest number has the highest priority. The priority number range from 1 to 100 should be used for modules considered essential for system operation. Lower priority values of 101 to 200 should be used for non-essential modules.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s
- configure card xiom mda power-priority-level
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS
- configure card mda power-priority-level
power-safety-alert
power-safety-alert
Syntax
power-safety-alert wattage
Context
[Tree] (config>system>pwr-mgmt power-safety-alert)
Full Context
configure system power-management power-safety-alert
Description
This command sets a value in watts for the Power Safety Alert. The Power Safety Alert minor alarm is generated when the system power capacity drops below the Power Safety Level (in watts) plus the Power Safety Alert. This is a critical level, which when breached the system starts shutting down IO cards based on card priority.
Parameters
- wattage
-
Specifies the number of watts for the power safety alert level.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS
power-safety-level
power-safety-level
Syntax
power-safety-level percent
Context
[Tree] (config>system>pwr-mgmt power-safety-level)
Full Context
configure system power-management power-safety-level
Description
This command sets the Power Safety Level, which is a percentage of the calculated worst case power draw value. Once a Power Safety Level is configured by the operator, both the Basic and Advanced modes use the Power Safety Level as a reference for calculating the power redundancy using N+1 algorithm during startup and recovery from power depression.
Default
power-safety-level 100
Parameters
- percent
-
Specifies the Power Safety Level as a percentage of the calculated worst case power draw value.
Platforms
7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS
power-save
power-save
Syntax
[no] power-save
Context
[Tree] (config>card power-save)
Full Context
configure card power-save
Description
This command enables power-save mode on a specific card when it is not in use. Power-save mode allows a card to be installed and configured in a platform for future use, while having minimal impact on the overall power consumption. The card placed in power-save mode is forced into an idle state to consume minimal power. This command resets the card and then disallows the download of a software image when the card comes back up. To enable power-save mode, the desired card must first be shut down, then placed into power-save mode. In this mode, the card is not counted in the intelligent power management budget. Cards set to power-save mode do not pass traffic.
The no form of this command removes the card from power-save mode.
Default
no power-save
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a8, 7750 SR-2e, 7750 SR-3e, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS
power-supply
power-supply
Syntax
power-supply power-supply-id type
Context
[Tree] (config>system power-supply)
Full Context
configure system power-supply
Description
This command configures information about the type of power supply used for each power feed connection on the router chassis. The information is used to populate queries made using the show>chassis detail and show>chassis power-supply commands.
Parameters
- power-supply-id
-
Specifies the power feed connection.
- type
-
Specifies the type of power source that is connected to the power feed connection.
Platforms
7450 ESS, 7750 SR-7/12
ppid
ppid
Syntax
ppid
Context
[Tree] (config>app-assure>group>statistics>tca>sctp-filter ppid)
Full Context
configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid
Description
This command configures a TCA for the counter capturing PPID hits for the specified SCTP filter.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
ppid
Syntax
ppid
Context
[Tree] (config>app-assure>group>sctp-filter ppid)
Full Context
configure application-assurance group sctp-filter ppid
Description
Commands in this context configure actions for specific or default Payload Protocol Identifiers (PPIDs).
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
ppid-range
ppid-range
Syntax
ppid-range direction direction [create]
no ppid-range direction direction
Context
[Tree] (config>app-assure>group>statistics>tca>sctp-filter ppid-range)
Full Context
configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid-range
Description
This command configures a TCA for the counter capturing hits for the specified SCTP filter PPID range command. An PPIPD range TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a TCA.
Parameters
- direction
-
Specifies the traffic direction.
- create
-
Keyword used to create the TCA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
ppid-range
Syntax
ppid-range min min-ppid max max-ppid
no ppid-range
Context
[Tree] (config>app-assure>group>sctp-filter ppid-range)
Full Context
configure application-assurance group sctp-filter ppid-range
Description
This command specifies the range of PPID values that are allowed by AA SCTP filter firewall.
The no form of this command removes this PPID range.
Default
no ppid-range
Parameters
- min-ppid
-
Specifies the minimum SCTP Payload Protocol Identifier (PPID) to be permitted by the SCTP filter. The value must be less than or equal to the max max-ppid value.
- max-ppid
-
Specifies the minimum SCTP Payload Protocol Identifier (PPID) to be permitted by the SCTP filter. The value must be greater or equal to the min min-ppid value.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
ppp
ppp
Syntax
ppp
Context
[Tree] (config>subscr-mgmt>loc-user-db ppp)
Full Context
configure subscriber-mgmt local-user-db ppp
Description
Commands in this context configure PPP host parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
ppp
Context
[Tree] (config>service>vprn>l2tp>group ppp)
[Tree] (config>router>l2tp>group>tunnel ppp)
[Tree] (config>router>l2tp>group ppp)
[Tree] (config>service>vprn>l2tp>group>tunnel ppp)
Full Context
configure service vprn l2tp group ppp
configure router l2tp group tunnel ppp
configure router l2tp group ppp
configure service vprn l2tp group tunnel ppp
Description
This command configures PPP for the L2TP tunnel group.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
[no] ppp [lcp] [pap] [ chap] [ipcp] [ ipv6cp] [other]
Context
[Tree] (debug>router>l2tp>group>packet ppp)
[Tree] (debug>router>l2tp>packet ppp)
[Tree] (debug>router>l2tp>assignment-id>packet ppp)
[Tree] (debug>router>l2tp>peer>packet ppp)
Full Context
debug router l2tp group packet ppp
debug router l2tp packet ppp
debug router l2tp assignment-id packet ppp
debug router l2tp peer packet ppp
Description
This command selects protocol for PPP packet debugging.
The no form of this command disables the protocols selection for PPP packet debugging.
Parameters
- lcp
-
Specifies the LCP protocol.
- pap
-
Specifies the PAP protocol.
- chap
-
Specifies the CHAP protocol.
- ipcp
-
Specifies the IPCP protocol.
- ipv6cp
-
Specifies the IPv6CP protocol.
- other
-
Specifies any other protocol.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
[no] ppp
Context
[Tree] (debug>service>id ppp)
Full Context
debug service id ppp
Description
This command enables and configures PPP debugging.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
ppp [terminate-only]
no ppp
Context
[Tree] (debug>service>id>ppp>event ppp)
Full Context
debug service id ppp event ppp
Description
This command enables debugging for PPP events.
Parameters
- terminate-only
-
Enables debugging for terminate-only PPP events.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
ppp [lcp] [pap] [chap] [ ipcp]
no ppp
Context
[Tree] (debug>service>id>ppp>packet ppp)
Full Context
debug service id ppp packet ppp
Description
This command enables debugging for specific PPP packets
Parameters
- lcp
-
Enables debugging for LCP packets.
- pap
-
Enables debugging for PAP packets.
- chap
-
Enables debugging for CHAP packets.
- ipcp
-
Enables debugging for IPCP packets.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
ppp
Context
[Tree] (debug>call-trace ppp)
Full Context
debug call-trace ppp
Description
Commands in this context set up call trace debugging for Point-to-Point Protocol sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp
Syntax
ppp [lcp] [pap] [ chap] [ipcp] [ipv6cp] [ipv6]
Context
[Tree] (debug>subscr-mgmt>vrgw>brg>pppoe-client>brg-id ppp)
Full Context
debug subscriber-mgmt vrgw brg pppoe-client brg-id ppp
Description
This command specifies which messages in PPP setup are tracked by debugging. If no messages are specified, they are all tracked. LCP Echo Request and Echo Response are never shown during debugging.
Parameters
- lcp
-
Tracks lcp messages during debugging.
- pap
-
Tracks pap messages during debugging.
- chap
-
Tracks chap messages during debugging.
- ipcp
-
Tracks ipcp messages during debugging.
- ipv6cp
-
Tracks ipv6cp messages during debugging.
- ipv6
-
Tracks ipv6 messages during debugging.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-authentication
ppp-authentication
Syntax
ppp-authentication {pap | chap | pref-chap | pref-pap}
no ppp-authentication
Context
[Tree] (config>subscr-mgmt>ppp-policy ppp-authentication)
Full Context
configure subscriber-mgmt ppp-policy ppp-authentication
Description
This command configures the PPP protocol used to authenticate the PPP session.
Default
ppp-authentication pref-chap
Parameters
- pap
-
Specifies to always use PAP to authenticate the sessions.
- chap
-
Specifies to always use CHAP to authenticate the sessions.
- pref-chap
-
Specifies to attempt to use CHAP and if it fails, use PAP.
- pref-pap
-
Specifies to attempt to use PAP and if it fails, use CHAP.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-chap-challenge-length
ppp-chap-challenge-length
Syntax
ppp-chap-challenge-length min minimum-length max maximum-length
no ppp-chap-challenge-length
Context
[Tree] (config>subscr-mgmt>ppp-policy ppp-chap-challenge-length)
Full Context
configure subscriber-mgmt ppp-policy ppp-chap-challenge-length
Description
This command configures the minimum and maximum length of a PPP Chap Challenge.
When the Chap Challenge is exactly 16 bytes, it is send in the [60] CHAP-Challenge RADIUS attribute and copied in the RADIUS Authenticator field from the RADIUS Access Request.
Default
ppp-chap-challenge-length min 32 max 64
Parameters
- min minimum-length
-
Specifies the minimum PPP CHAP challenge length.
- max maximum-length
-
Specifies the maximum PPP CHAP challenge length.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-initial-delay
ppp-initial-delay
Syntax
[no] ppp-initial-delay
Context
[Tree] (config>subscr-mgmt>ppp-policy ppp-initial-delay)
Full Context
configure subscriber-mgmt ppp-policy ppp-initial-delay
Description
This command delays the sending of an LCP-configure request after the discovery phase by 40 – 60 milliseconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-mtu
ppp-mtu
Syntax
ppp-mtu mtu-bytes
no ppp-mtu
Context
[Tree] (config>subscr-mgmt>ppp-policy ppp-mtu)
Full Context
configure subscriber-mgmt ppp-policy ppp-mtu
Description
This command configures the maximum PPP MTU size.
Parameters
- mtu-bytes
-
Specifies the maximum PPP MTU size.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-options
ppp-options
Syntax
ppp-options
Context
[Tree] (config>subscr-mgmt>ppp-policy ppp-options)
Full Context
configure subscriber-mgmt ppp-policy ppp-options
Description
Commands in this context configure PPP options.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-policy
ppp-policy
Syntax
ppp-policy ppp-policy-name [create]
no ppp-policy ppp-policy-name
Context
[Tree] (config>subscr-mgmt ppp-policy)
Full Context
configure subscriber-mgmt ppp-policy
Description
This command configures a PPP policy. These policies are referenced from interfaces configured for PPP. Multiple PPP policies may be configured.
The default policy cannot be modified or deleted.
Default
ppp-policy default
Parameters
- ppp-policy-name
-
Specifies the PPP policy name, up to 32 characters.
- create
-
Keyword used to create the entity. The create keyword requirement can be enabled/disabled in the environment>create context.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-policy-parameters
ppp-policy-parameters
Syntax
ppp-policy-parameters
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host ppp-policy-parameters)
Full Context
configure subscriber-mgmt local-user-db ppp host ppp-policy-parameters
Description
This command enables the context to configure PPP policy parameters to override the values from the host associated with the PPP policy.
The PPP host uses the values configured in the PPP policy under the group interface. It is possible to use this command to override the values from the host associated with the PPP policy. Matching a pattern on the subscriber MAC address to limit the number of sessions per MAC address is possible.
When a value is configured, the system overrides that particular PPP policy parameter. The absence of specific parameters means no overriding is performed.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-sub-id-key
ppp-sub-id-key
Syntax
ppp-sub-id-key sub-id-key [sub-id-key]
no ppp-sub-id-key
Context
[Tree] (config>subscr-mgmt>auto-sub-id-key ppp-sub-id-key)
Full Context
configure subscriber-mgmt auto-sub-id-key ppp-sub-id-key
Description
This command enables certain fields to become the base for auto-generation of default sub-id name. The sub-id name is auto-generated if there is not a more specific method available. Examples of these specific methods would be a default sub-id name as a sap-id, a preconfigured static string or explicit mappings based on RADIUS/LUDB returned strings.
In case that a more specific sub-id name generation method is not available and the auto-id keyword is defined under the def-sub-id hierarchy, the sub-id name is generated by concatenating fields defined in this command separated by a "|” character.
The maximum length of the auto-generated sub-id name is 64 characters while the concatenation of subscriber identification fields can exceed 64 characters. Subscriber host instantiation fails if the sub-id name is based on subscriber identification fields whose concatenated length exceeds 64 characters. Failing the host creation rather than truncating the sub-id name on a 64 character boundary prevents collision of sub-ids (subscriber name duplication).
In case that a more specific sub-id name generation method is not available and the auto-id keyword is not defined under the def-sub-id hierarchy, the sub-id name is a random 10 character encoded string based on the fields defined under this command.
There is only one set of identification fields allowed per host type (IPoE or PPP) per chassis.
The no form of this command reverts to the default.
Default
ppp-sub-id-key mac sap-id session-id
Parameters
- sub-id-key
-
Specifies the auto-generated sub-id keys for PPP hosts.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ppp-user-db
ppp-user-db
Syntax
ppp-user-db local-user-db-name
no ppp-user-db
Context
[Tree] (config>service>vpls ppp-user-db)
Full Context
configure service vpls ppp-user-db
Description
This command enabled access to LUDB for PPPoE and PPPoEoA v4and v6 hosts under the capture SAP. The name of this local user database must match the name of local user database configured under the config>service>vprn/ies>sub-if>grp-if>pppoe hierarchy.
The no form of this command reverts to the default.
Parameters
- local-user-db
-
Specifies the name of the local-user-database, up to 256 characters.
Platforms
All
ppp-user-name
ppp-user-name
Syntax
ppp-user-name append domain-name
ppp-user-name default-domain domain-name
ppp-user-name replace domain-name
ppp-user-name strip
no ppp-user-name
Context
[Tree] (config>subscr-mgmt>auth-plcy ppp-user-name)
Full Context
configure subscriber-mgmt authentication-policy ppp-user-name
Description
This command specifies the domain name manipulation action to perform on the PAP/CHAP user name prior to authentication.
The no form of this command reverts to the default.
Default
The PAP/CHAP user name is not changed.
Parameters
- append domain-name
-
Appends an "@” delimiter followed by the specified domain-name to the PAP/CHAP user name, independent if a domain name is already present.
- default-domain domain-name
-
Appends an "@” delimiter followed by the specified domain-name to the PAP/CHAP user name only if a domain name is not already present.
- replace domain-name
-
Replaces the string after the "@” delimiter in the PAP/CHAP user name with the specified domain-name.
- strip
-
Removes the "@” delimiter and all subsequent characters from the PAP/CHAP user name.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe
pppoe
Syntax
[no] pppoe
Context
[Tree] (config>service>ies>sub-if>grp-if pppoe)
[Tree] (config>service>vprn>sub-if>grp-if pppoe)
Full Context
configure service ies subscriber-interface group-interface pppoe
configure service vprn subscriber-interface group-interface pppoe
Description
Commands in this context configure PPPoE parameters.
The no form of this command reverts all PPPoE parameters from the PPPoE context to their defaults.
Default
pppoe
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe
Syntax
pppoe type direction {ingress | egress} script name
no pppoe type direction {ingress | egress}
Context
[Tree] (config>python>py-policy pppoe)
Full Context
configure python python-policy pppoe
Description
This command specifies the python-script for the specified PPPoE message type in the specified direction. Multiple pppoe command configuration are allowed in the same Python policy.
The no form of this command reverts to the default.
Parameters
- type
-
Specifies the message type.
- direction {ingress | egress}
-
Specifies whether the event is incoming or outgoing. The system only invokes the configured script for the specified packet type in the specified direction.
- script
-
Specifies the name of the Python script, up to 32 characters, that is used to handle the specified message.
Platforms
All
pppoe
Syntax
pppoe service-id
no pppoe
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>fwd-wholesale pppoe)
[Tree] (config>service>vprn>if>sap>fwd-wholesale pppoe)
Full Context
configure service vprn subscriber-interface group-interface sap fwd-wholesale pppoe
configure service vprn interface sap fwd-wholesale pppoe
Description
This command specifies that PPPoE packets on ingress on Ethertypes 0x8863 and 0x8864 are redirected to the specified service. The service referred to by svc-id must be an Epipe service. Redirection to VC-switching Epipe services is not supported.
The no form of this command removes the redirect.
Parameters
- service-id
-
Specifies the service ID of the Epipe to which packets are redirected.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe
Syntax
pppoe service-id
no pppoe
Context
[Tree] (config>service>ies>if>sap>fwd-wholesale pppoe)
[Tree] (config>service>ies>sub-if>grp-if>sap>fwd-wholesale pppoe)
Full Context
configure service ies interface sap fwd-wholesale pppoe
configure service ies subscriber-interface group-interface sap fwd-wholesale pppoe
Description
This command specifies that PPPoE packets on ingress on Ethertypes 0x8863 and 0x8864 will be redirected to the specified service. The service referred to by svc-id must be an Epipe service. Redirection to VC-switching Epipe services is not supported.
The no form of this command removes the redirect.
Parameters
- service-id
-
Specifies the service ID of the Epipe to which packets are redirected.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe
Syntax
pppoe origin
Context
[Tree] (config>li>x-interfaces>correlation-id pppoe)
Full Context
configure li x-interfaces correlation-id pppoe
Description
This command specifies the type of RADIUS accounting session ID to use for PPPoE subscriber correlation.
Default
host
Parameters
- origin
-
Specifies the correlation identifiers origin for PPPoE.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pppoe
Syntax
[no] pppoe
Context
[Tree] (config>redundancy>multi-chassis>peer>sync>subscriber-mgmt pppoe)
Full Context
configure redundancy multi-chassis peer sync subscriber-mgmt pppoe
Description
This command configures the router to synchronize subscriber management PPPoE information with the multi-chassis peer.
The no form of this command disables the router from synchronizing subscriber management PPPoE information with the multi-chassis peer.
Default
no pppoe
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-access-method
pppoe-access-method
Syntax
pppoe-access-method {none | padi | pap-chap}
no pppoe-access-method
Context
[Tree] (config>subscr-mgmt>auth-plcy pppoe-access-method)
Full Context
configure subscriber-mgmt authentication-policy pppoe-access-method
Description
This command indicates the authentication method used towards the RADIUS server in case the policy is used for PPPoE.
The no form of this command reverts to the default.
Parameters
- none
-
Indicates that the client is authenticated by the local user database defined under the group interface and not through RADIUS.
- padi
-
Indicates that the client is authenticated by RADIUS as soon as the PADI packet comes in (there is no PPP authentication done in the session in this case).
- pap-chap
-
Indicates that the RADIUS authentication of the client is delayed until the authentication protocol phase in the PPP session (PAP or CHAP) and authentication is performed with the user name and PAP password / CHAP response supplied by the client.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-client
pppoe-client
Syntax
pppoe-client
Context
[Tree] (debug>subscr-mgmt>vrgw>brg pppoe-client)
Full Context
debug subscriber-mgmt vrgw brg pppoe-client
Description
Commands in this context debug pppoe-client information.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-client-policy
pppoe-client-policy
Syntax
pppoe-client-policy pppoe-client-policy-name [create]
no pppoe-client-policy pppoe-client-policy-name
Context
[Tree] (config>subscr-mgmt pppoe-client-policy)
Full Context
configure subscriber-mgmt pppoe-client-policy
Description
This command provisions a policy containing a set of parameters to be used to configure a PPPoE client.
The no form of this command removes the policy from the system. The policy can only be removed when it is not in use.
Parameters
- pppoe-client-policy-name
-
Specifies a unique name for the policy.
- create
-
Mandatory keyword when creating a new policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-lac
pppoe-lac
Syntax
pppoe-lac max-nr-of-sessions
no pppoe-lac
Context
[Tree] (config>subscr-mgmt>sla-profile>session-limits pppoe-lac)
[Tree] (config>subscr-mgmt>sub-profile>session-limits pppoe-lac)
Full Context
configure subscriber-mgmt sla-profile session-limits pppoe-lac
configure subscriber-mgmt sub-profile session-limits pppoe-lac
Description
This command configures the maximum number of PPPoE L2TP LAC sessions per SLA profile instance or per subscriber.
The no form of this command removes the maximum number of PPPoE L2TP LAC sessions limit.
Parameters
- max-nr-of-sessions
-
Specifies the maximum number of PPPoE L2TP LAC sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-local
pppoe-local
Syntax
pppoe-local max-nr-of-sessions
no pppoe-local
Context
[Tree] (config>subscr-mgmt>sub-profile>session-limits pppoe-local)
[Tree] (config>subscr-mgmt>sla-profile>session-limits pppoe-local)
Full Context
configure subscriber-mgmt sub-profile session-limits pppoe-local
configure subscriber-mgmt sla-profile session-limits pppoe-local
Description
This command configures the maximum number of PPPoE local-terminated sessions (PTA) per SLA profile instance or per subscriber.
The no form of this command removes maximum number of PPPoE local-terminated sessions (PTA) limit.
Parameters
- max-nr-of-sessions
-
Specifies the maximum number of PPPoE local-terminated sessions (PTA).
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-overall
pppoe-overall
Syntax
pppoe-overall max-nr-of-sessions
no pppoe-overall
Context
[Tree] (config>subscr-mgmt>sub-profile>session-limits pppoe-overall)
[Tree] (config>subscr-mgmt>sla-profile>session-limits pppoe-overall)
Full Context
configure subscriber-mgmt sub-profile session-limits pppoe-overall
configure subscriber-mgmt sla-profile session-limits pppoe-overall
Description
This command configures the maximum number of PPPoE sessions per SLA profile instance or per subscriber.
The no form of this command removes the maximum number of PPPoE sessions limit.
Parameters
- max-nr-of-sessions
-
Specifies the maximum number of PPPoE sessions.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-policy
pppoe-policy
Syntax
pppoe-policy pppoe-policy-name
no pppoe-policy
Context
[Tree] (config>service>vpls>sap pppoe-policy)
Full Context
configure service vpls sap pppoe-policy
Description
This command references a pppoe-policy that defines session parameters (ppp-mtu, authentication options, and so on) during the session initiation phase. Normally, the PPPoE policy is referenced under the group-interface hierarchy. But with capture SAP is it not known at the session initiation phase to which group-interface the session belongs. This is why, with the capture SAP, the ppp-policy must be referenced directly under the capture SAP. The pppoe-policy referenced under the group-interface must be the same as the pppoe-policy referenced under the capture SAP. Otherwise the session will not come up.
The no form of this command reverts to the default.
Parameters
- pppoe-policy-name
-
Specifies the pppoe-policy name up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-python-policy
pppoe-python-policy
Syntax
pppoe-python-policy policy-name
no pppoe-python-policy
Context
[Tree] (config>service>vpls>sap pppoe-python-policy)
Full Context
configure service vpls sap pppoe-python-policy
Description
This command specified the Python policy for PPPoE packets sent/received on the capture SAP.
The no form of this command removes the policy name from the configuration.
Parameters
- policy-name
-
Specifies an existing Python policy name, up to 32 characters.
Platforms
All
pppoe-service-name
pppoe-service-name
Syntax
[no] pppoe-service-name
Context
[Tree] (config>subscr-mgmt>auth-policy>include-radius-attribute pppoe-service-name)
Full Context
configure subscriber-mgmt authentication-policy include-radius-attribute pppoe-service-name
Description
This command enables the generation of the pppoe-service-name RADIUS attribute.
The no form of this command reverts to the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-trace
pppoe-trace
Syntax
pppoe-trace [sap sap-id] [ mac ieee-address] circuit-id circuit-id [remote-id remote-id] [username user-name] [profile trace-profile-name] [trace-existing-sessions] [ max-jobs num] [name trace-name]
pppoe-trace [sap sap-id] mac ieee-address [circuit-id circuit-id] [remote-id remote-id] [username user-name] [profile trace-profile-name] [ trace-existing-sessions] [max-jobs num] [name trace-name]
pppoe-trace sap sap-id [mac ieee-address] [ circuit-id circuit-id] [remote-id remote-id] [username user-name] [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]
pppoe-trace [sap sap-id] [mac ieee-address] [circuit-id circuit-id] remote-id remote-id [username user-name] [ profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]
pppoe-trace [sap sap-id] [ mac ieee-address] [circuit-id circuit-id] [remote-id remote-id] username user-name [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]
no pppoe-trace name trace-name
no pppoe-trace [sap sap-id] [ mac ieee-address] [circuit-id circuit-id] [remote-id remote-id] [username user-name]
Context
[Tree] (debug>call-trace>ppp pppoe-trace)
Full Context
debug call-trace ppp pppoe-trace
Description
This command enables tracing locally terminated or LAC PPPoE sessions specified by the configured parameters. At least one filter rule must be provisioned. This command can trace a single session or multiple sessions, and can use wildcard characters.
This command can be executed multiple times to start multiple traces. When rules overlap, such as for a wildcard SAP and a specific SAP, the rule that a specific trace is associated with cannot be guaranteed.
The no form of this command prevents new traces from being configured and terminates all trace jobs that were previously started using the trace command.
Parameters
- circuit-id
-
Specifies a circuit ID, up to 255 characters, that is used to filter sessions to trace.
- ieee-address
-
Specifies a MAC address that is used to identify a session to trace, in the format "ab:cd:ef:01:23:45”. A wildcard character can be used to match all remaining octets; for example, the format "ab:cd:ef:*” can be used to filter by OUI.
- user-name
-
Specifies a username, up to 32 characters, that is used to filter sessions to trace. A wildcard character (*) can be used at the beginning and at the end of the filter.
- num
-
Specifies the maximum number of jobs that may be started with this rule.
- remote-id
-
Specifies a remote ID, up to 255 characters, that is used to filter sessions to trace.
- sap-id
-
Specifies a SAP to trace. The following formats are accepted:
-
port/lag/pw-port:svlan.cvlan
-
port/lag/pw-port:vlan
-
port/lag/pw-port
-
port/lag/pw-port:vlan.*
-
port/lag/pw-port:* (also matches *.*)
-
- trace-existing-sessions
-
Specifies that existing PPPoE sessions are traced. If this parameter is not included, only new PPPoE sessions are traced.
- trace-name
-
Specifies the name, up to 32 characters, by which the trace is referenced.
- trace-profile-name
-
Specifies the name of the trace profile to be applied, up to 32 characters. The default parameters are used if a trace profile is not specified.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pppoe-user-db
pppoe-user-db
Syntax
pppoe-user-db local-user-db-name
no pppoe-user-db
Context
[Tree] (config>service>vpls pppoe-user-db)
Full Context
configure service vpls pppoe-user-db
Description
This command enabled access to LUDB for PPPoE and PPPoEoA v4and v6 hosts under the capture SAP. The name of this LUDB must match the name of the LUDB configured under the config>service>vprn/ies>sub-if>grp-if>pppoe hierarchy.
The no form of this command reverts to the default.
Parameters
- local-user-db
-
Specifies the name of the local user database, up to 256 characters.
Platforms
All
pppoe-user-db
Syntax
pppoe-user-db ludb-name
no pppoe-user-db
Context
[Tree] (config>service>vpls>sap pppoe-user-db)
Full Context
configure service vpls sap pppoe-user-db
Description
This command enables LUDB authentication on capture SAPs for PPPoE(oA) clients. If this command is configured along with the authentication-policy command (RADIUS authentication), then the authentication-policy command takes precedence.
The no form of this command reverts to the default.
Parameters
- ludb-name
-
Specifies the name of the local user database up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pptp
pptp
Syntax
[no] pptp
Context
[Tree] (config>service>nat>nat-policy>alg pptp)
[Tree] (config>service>nat>up-nat-policy>alg pptp)
Full Context
configure service nat nat-policy alg pptp
configure service nat up-nat-policy alg pptp
Description
This command enables PPTP ALG.
The call-id is captured in the outgoing call management messages and along with the source IP address and the source TCP, is translated by NAT. Once the PPTP call is established, the call-id in the associated GRE packet in the incoming direction (from outside to inside) is correspondingly translated so that it matches the call-id mapping established during the call establishment phase. The call IDs used in the mappings are selected randomly and they try to honor parity (odds/even).
A PPTP session can be initiated only from the inside of NAT.
GRE traffic is allowed through NAT only if the corresponding mapping exists. This mapping is created during the call negotiation phase.
There can be seven calls (GRE tunnels) per control session.
Default
no pptp
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
pre-auth-policy
pre-auth-policy
Syntax
pre-auth-policy policy-name
no pre-auth-policy
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host pre-auth-policy)
Full Context
configure subscriber-mgmt local-user-db ppp host pre-auth-policy
Description
This command configures the RADIUS pre-authentication policy to use to authenticate the PPP host.
The no form of this command reverts to the default.
Parameters
- policy-name
-
Specifies the pre-authentication policy of the host, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pre-login-message
pre-login-message
Syntax
pre-login-message login-text-string [name]
no pre-login-message
Context
[Tree] (config>system>login-control pre-login-message)
Full Context
configure system login-control pre-login-message
Description
This command configures a message to display before logging in to the router using Telnet, SSH, or the console port.
Only one message can be configured. If a new pre-login message is configured, the new message overwrites the previous message.
The no form of this command removes the pre-login message.
Default
no pre-login-message
Parameters
- login-text-string
-
Specifies the pre-login message text, up to 900 characters. Any printable, 7-bit ASCII characters can be used. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Some special characters can be used to format the message text. Use the newline (\n) character to create multiline messages. A newline (\n) character in the message moves to the beginning of the next line by sending ASCII/UTF-8 characters 0xA (LF) and 0xD (CR) to the client terminal. A carriage return (\r) character in the message sends the ASCII/UTF-8 character 0xD (CR) to the client terminal.
- name
-
Displays the configured system name before the pre-login message. To remove the system name from the pre-login message, remove the current message and configure a new message without using the name parameter.
Platforms
All
pre-shared-key
pre-shared-key
Syntax
pre-shared-key pre-shared-key-index [encryption-type encryption-type] [create]
no pre-shared-key pre-shared-key-index
Context
[Tree] (config>macsec>conn-assoc>static-cak pre-shared-key)
Full Context
configure macsec connectivity-association static-cak pre-shared-key
Description
This command specifies the pre-shared key used to enable MACsec using static connectivity association key (CAK) security mode. This command also specifies the encryption algorithm used for encrypting the SAK.
A pre-shared key includes a connectivity association key name (CKN) and a connectivity association key (CAK). The pre-shared key-the CKN and CAK-must match on both ends of a link.
A pre-shared key is configured on both devices at each end of point-to-point link to enable MACsec using static CAK security mode. The MACsec Key Agreement (MKA) protocol is enabled after the successful MKA liveliness negotiation.
The encryption-type is used for encrypting the SAK and authenticating the MKA packet. The symmetric encryption key SAK (Security Association Key) needs to be encrypted (wrapped) via the MKA protocols. The AES key is derived via pre-shared-key.
The no form of this command removes the index.
Parameters
- pre-shared-key-index
-
Specifies the index of this pre-shared-key.
- encryption-type
-
Specifies the type of encryption.
- create
-
Mandatory to create an entry.
Platforms
All
pre-shared-key
Syntax
pre-shared-key key [hash | hash2 | custom]
no pre-shared-key
Context
[Tree] (config>ipsec>client-db>client>credential pre-shared-key)
Full Context
configure ipsec client-db client credential pre-shared-key
Description
This command specifies a pre-shared key used to authenticate peers.
The no form of this command reverts to the default.
Default
no pre-shared-key
Parameters
- key
-
An ASCII string to use as the pre-shared key for dynamic keying. When the hash or hash2 parameters are not used, the key is a clear text key; otherwise, the key text is encrypted.
- 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, clear text 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, clear text 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-e, 7750 SR-s, VSR
pre-shared-key
Syntax
pre-shared-key key [hash | hash2 | custom]
no pre-shared-key
Context
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn pre-shared-key)
[Tree] (config>service>vprn>if>sap>ipsec-gw pre-shared-key)
[Tree] (config>ipsec>trans-mode-prof>dyn pre-shared-key)
[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn pre-shared-key)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel>dynamic-keying pre-shared-key)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn pre-shared-key)
[Tree] (config>service>ies>if>sap>ipsec-gw pre-shared-key)
Full Context
configure service ies interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
configure service vprn interface sap ipsec-gw pre-shared-key
configure ipsec ipsec-transport-mode-profile dynamic-keying pre-shared-key
configure router interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
configure service vprn interface sap ipsec-tunnel dynamic-keying pre-shared-key
configure service vprn interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
configure service ies interface sap ipsec-gw pre-shared-key
Description
This command configures the pre-shared key for authentication.
The no form of this command reverts to the default.
Default
no pre-shared-key
Parameters
- key
-
Specifies an ASCII string to use as the pre-shared key for dynamic keying. When the hash or hash2 parameters are not used, the key is a clear text key; otherwise, the key text is encrypted.
- 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, clear text 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, clear text 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
VSR
- configure router interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
- configure service vprn interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
- configure service ies interface ipsec ipsec-tunnel dynamic-keying pre-shared-key
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel dynamic-keying pre-shared-key
- configure service ies interface sap ipsec-gw pre-shared-key
- configure service vprn interface sap ipsec-gw pre-shared-key
- configure ipsec ipsec-transport-mode-profile dynamic-keying pre-shared-key
pre-update-time
pre-update-time
Syntax
pre-update-time [days days] [ hrs hours] [min minutes] [sec seconds]
Context
[Tree] (config>system>security>pki>ca-prof>auto-crl-update pre-update-time)
Full Context
configure system security pki ca-profile auto-crl-update pre-update-time
Description
This command specifies the pre-download time for next-update-based update.
Default
pre-update-time hrs 1
Parameters
- days
-
Specifies the time period, in days, prior to the next update time of the current CRL.
- hours
-
Specifies the time period, in hours, prior to the next update time of the current CRL.
- minutes
-
Specifies the time period, in minutes, prior to the next update time of the current CRL.
- seconds
-
Specifies the time period, in seconds, prior to the next update time of the current CRL.
Platforms
All
prec
prec
Syntax
prec ip-prec-value [fc fc-name] [priority {high | low}]
no prec ip-prec-value
Context
[Tree] (config>qos>sap-ingress prec)
Full Context
configure qos sap-ingress prec
Description
This command explicitly sets the forwarding class or enqueuing priority when a packet is marked with an IP precedence value ( ip-prec-value). Adding an IP precedence rule on the policy forces packets that match the specified ip-prec-value to override the forwarding class and enqueuing priority based on the parameters included in the IP precedence rule.
When the forwarding class is not specified in the rule, a matching packet preserves (or inherits) the existing forwarding class derived from earlier matches in the classification hierarchy.
When the enqueuing priority is not specified in the rule, a matching packet preserves (or inherits) the existing enqueuing priority derived from earlier matches in the classification hierarchy.
The ip-prec-value is derived from the most significant three bits in the IP header ToS byte field (precedence bits). The three precedence bits define eight Class-of-Service (CoS) values commonly used to map packets to per-hop Quality of Service (QoS) behavior. The precedence bits are also part of the DiffServ Code Point (DSCP) method of mapping packets to QoS behavior. The DSCP uses the most significant six bits in the IP header ToS byte and so overlaps with the precedence bits. Both IP precedence and DSCP classification rules are supported. DSCP rules have a higher match priority than IP precedence rules and where a dscp-name DSCP value overlaps an ip-prec-value, the DSCP rule takes precedence.
The no form of this command removes the explicit IP precedence classification rule from the SAP ingress policy. Removing the rule on the policy immediately removes the rule on all ingress SAPs using the policy.
Parameters
- ip-prec-value
-
The ip-prec-value is a required parameter that specifies the unique IP header ToS byte precedence bits value that will match the IP precedence rule. If the command is executed more than once with the same ip-prec-value, the previous forwarding class and enqueuing priority is completely overridden by the new parameters or defined to be inherited when a forwarding class or enqueuing priority parameter is missing.
A maximum of eight IP precedence rules are allowed on a single policy.
The precedence is evaluated from the lowest to highest value.
- fc fc-name
-
The value given for the fc-name parameter must be one of the predefined forwarding classes in the system. Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the forwarding class is not explicitly defined in the rule, the forwarding class is inherited based on previous rule matches.
The subclass-name parameter is optional and used with the fc-name parameter to define a pre-existing subclass. The fc-name and subclass-name parameters must be separated by a period (.). If subclass-name does not exist in the context of fc-name, an error will occur. If subclass-name is removed using the no fc fc-name.subclass-name force command, the default-fc command will automatically drop the subclass-name and only use fc-name (the parent forwarding class for the subclass) as the forwarding class.
- priority
-
The priority parameter overrides the default enqueuing priority for all packets received on an ingress SAP using this policy that match this rule. Specifying the priority is optional. When a packet matches the rule, the enqueuing priority is only overridden when the priority parameter is defined on the rule. If the packet matches and priority is not explicitly defined in the rule, the enqueuing priority is inherited based on previous rule matches.
- high
-
This parameter is used in conjunction with the priority parameter. Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. When the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
- low
-
This parameter is used in conjunction with the priority parameter. Setting the enqueuing parameter to low for a packet decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. When the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Platforms
All
prec
Syntax
prec {ip-prec-value | in-profile ip-prec-value out-profile ip-prec-value [ exceed-profile ip-prec-value]}
no prec
Context
[Tree] (config>qos>sap-egress>fc prec)
Full Context
configure qos sap-egress fc prec
Description
This command defines a value to be used for remarking packets for the specified FC. If the optional in/out/exceed-profile is specified, the command will remark different IP precedence values depending on whether the packet was classified to be in, exceed, or out-of-profile. All inplus-profile traffic is marked with the same value as in-profile traffic.
Parameters
- ip-prec-value
-
This parameter specifies the IP precedence to be used to remark all traffic.
- exceed-profile ip-prec-value
-
This optional parameter specifies the IP precedence to be used to remark traffic that is exceed-profile. If not specified, this defaults to the same value configured for the out-profile parameter.
- in-profile ip-prec-value
-
This parameter specifies the IP precedence to be used to remark traffic that is in-profile.
- out-profile ip-prec-value
-
This parameter specifies the IP precedence to be used to remark traffic that is out-of-profile.
Platforms
All
prec
Syntax
prec ip-prec-value [fc fc-name] [profile {in | out | exceed | inplus}]
no prec ip-prec-value
Context
[Tree] (config>qos>sap-egress prec)
Full Context
configure qos sap-egress prec
Description
This command defines a specific IP precedence value that must be matched to perform the associated reclassification actions. If an egress packet on the SAP matches the specified IP precedence value, the forwarding class, or profile behavior may be overridden. By default, the forwarding class and profile of the packet is derived from ingress classification and profiling functions.
The IP precedence bits used to match against precedence reclassification rules come from the Type of Service (ToS) field within the IPv4 header. If the packet does not have an IPv4 header, precedence-based matching is not performed.
The reclassification actions from a precedence reclassification rule may be overridden by a DSCP or IP flow matching event.
The fc keyword is optional. When specified, the egress classification rule will overwrite the forwarding class derived from ingress. The new forwarding class is used for egress remarking and queue mapping decisions. If a DSCP, ipv6-criteria, or ip-criteria match occurs after the IP precedence match, the new forwarding class may be overridden by the higher priority match actions. If the higher priority match actions do not specify a new fc, the fc from the IP precedence match will be used.
The profile keyword is optional. When specified, the egress classification rule will overwrite the profile of the packet derived from ingress. The new profile value is used for egress remarking and queue congestion behavior. If a DSCP, IPv6 criteria, or IP criteria match occurs after the IP precedence match, the new profile may be overridden by the higher priority match actions. If the higher priority match actions do not specify a new profile, the profile from the IP precedence match will be used.
The no form of this command removes the reclassification rule from the SAP egress QoS policy.
Parameters
- fc fc-name
-
This keyword is optional. When specified, packets matching the IP precedence value will be explicitly reclassified to the forwarding class specified as fc-name regardless of the ingress classification decision. The explicit forwarding class reclassification may be overwritten by a higher priority DSCP, IPv6 criteria, or IP criteria reclassification match. The FC name defined must be one of the eight forwarding classes supported by the system. To remove the forwarding class reclassification action for the specified precedence value, the prec command must be re-executed without the fc parameter defined.
- profile {in | out | exceed | inplus}
-
This keyword is optional. When specified, packets matching the IP precedence value will be explicitly reclassified to the specified profile regardless of the ingress profiling decision. The explicit profile reclassification may be overwritten by a higher priority DSCP, IPv6 criteria, or IP criteria reclassification match. To remove the profile reclassification action for the specified precedence value, the prec command must be re-executed without the profile parameter defined.
- in
-
Specifies that any packets matching the reclassification rule will be treated as in-profile by the egress forwarding plane.
- out
-
Specifies that any packets matching the reclassification rule will be treated as out-of-profile by the egress forwarding plane.
- exceed
-
Specifies that any packets matching the reclassification rule will be treated as exceed-profile by the egress forwarding plane.
- inplus
-
Specifies that any packets matching the reclassification rule will be treated as inplus-profile by the egress forwarding plane.
Platforms
All
prec
Syntax
prec ip-prec-value fc fc-name profile {in | out | exceed | inplus}
no prec ip-prec-value
Context
[Tree] (config>qos>network>egress prec)
Full Context
configure qos network egress prec
Description
This command defines a specific IP precedence value that must be matched in order to perform the associated reclassification actions. If an egress packet on an IES/VPRN interface spoke SDP, on a CSC network interface in a VPRN, or network interface that the network QoS policy is applied to, matches the specified IP precedence value, the forwarding class and profile may be overridden.
By default, the forwarding class and profile of the packet is derived from ingress classification and profiling functions.
The IP precedence bits used to match against the reclassification rules come from the Type of Service (ToS) field within the IPv4 header or the Traffic Class field from the IPv6 header. If the packet does not have an IP header, IP precedence-based matching is not performed.
The configuration of egress prec classification and the configuration of an egress IP criteria or IPv6 criteria entry statement within a network QoS policy are mutually exclusive.
The IP precedence-based and DSCP-based reclassification are supported on a network interface, on a CSC network interface in a VPRN, and on a PW used in an IES or VPRN spoke interface.
This command will block the application of a network QoS policy with the egress reclassification commands to a spoke SDP part of a Layer 2 service. Conversely, this command will not allow the user to add the egress reclassification commands to a network QoS policy if it is being used by a Layer 2 spoke SDP.
The egress reclassification commands will only take effect if the redirection of the spoke SDP or CSC interface to use an egress port queue-group succeeds. For example, the following commands will succeed:
- config>service>vprn>if>
spoke-sdp>egress>qos network-policy-id port-redirect-group
queue-group-name instance instance-id
- config>service>ies>if>spoke-sdp>
egress>qos network-policy-id port-redirect-group queue-group-name
instance instance-id
- config>service>vprn>nw-if> qos network-policy-id port-redirect-group
queue-group-name instance instance-id
When the redirection command fails in CLI, the PW will use the network QoS policy assigned to the network IP interface; however, any reclassification in the network QoS policy applied to the network interface will be ignored.
The no form of this command removes the egress reclassification rule.
Parameters
- ip-prec-value
-
0 to 7
- fc fc-name
-
be, l2, af, l1, h2, ef, h1, nc
- profile {in | out | exceed | inplus}
-
The profile reclassification action is mandatory. When specified, packets matching the IP precedence value will be explicitly reclassified to the profile specified regardless of the ingress profiling decision. To remove the profile reclassification action for the specified IP precedence value, the no prec command must be executed.
This value may be overwritten by an explicit profile action in an DSCP reclassification match.
in - Specifies that any packets matching the reclassification rule will be treated as in-profile by the egress forwarding plane.
out - Specifies that any packets matching the reclassification rule will be treated as out-of-profile by the egress forwarding plane.
exceed - Specifies that any packets matching the reclassification rule will be treated as exceed-profile by the egress forwarding plane.
inplus - Specifies that any packets matching the reclassification rule will be treated as inplus-profile by the egress forwarding plane.
Platforms
All
precedence
precedence
Syntax
precedence {primary | secondary}
no precedence
Context
[Tree] (config>eth-tunnel>path precedence)
Full Context
configure eth-tunnel path precedence
Description
This command specifies the precedence to be used for the path. Only two precedence options are supported: primary and secondary.
The no form of this command sets the precedence to the default value.
Default
precedence secondary
Parameters
- primary | secondary
-
Specifies the path precedence as either primary or secondary.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
precedence
Syntax
precedence [precedence-value | primary]
no precedence
Context
[Tree] (config>service>epipe>spoke-sdp precedence)
[Tree] (config>service>ipipe>spoke-sdp precedence)
[Tree] (config>service>cpipe>spoke-sdp precedence)
Full Context
configure service epipe spoke-sdp precedence
configure service ipipe spoke-sdp precedence
configure service cpipe spoke-sdp precedence
Description
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding will begin to forward traffic.
The no form of this command returns the precedence value to the default.
Default
precedence 4
Parameters
- precedence-value
-
Specifies the spoke SDP precedence.
- primary
-
Assigns primary precedence to the spoke SDP.
Platforms
All
- configure service epipe spoke-sdp precedence
- configure service ipipe spoke-sdp precedence
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe spoke-sdp precedence
precedence
Syntax
precedence prec-value
precedence primary
no precedence
Context
[Tree] (config>service>epipe>spoke-sdp-fec precedence)
Full Context
configure service epipe spoke-sdp-fec precedence
Description
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding will begin to forward traffic.
The no form of this command returns the precedence value to the default.
Default
precedence 42
Parameters
- prec-value
-
Specifies the spoke SDP precedence.
- primary
-
Assigns primary precedence to this spoke SDP.
Platforms
All
precedence
Syntax
precedence [precedence-value | primary]
no precedence
Context
[Tree] (config>service>vpls>spoke-sdp precedence)
Full Context
configure service vpls spoke-sdp precedence
Description
This command configures the precedence of this SDP bind when there are multiple SDP binds attached to one service endpoint. When an SDP bind goes down, the next highest precedence SDP bind begins forwarding traffic.
Parameters
- precedence-value
-
Specifies the precedence of this SDP bind
- primary
-
Assigns this as the primary spoke-SDP
Platforms
All
precedence
Syntax
precedence {precedence-value | primary}
no precedence
Context
[Tree] (config>mirror>mirror-dest>spoke-sdp precedence)
Full Context
configure mirror mirror-dest spoke-sdp precedence
Description
This command indicates that the SDP is of type secondary with a specific precedence value or of type primary.
The mirror or LI service always uses the primary type as the active pseudowire and only switches to a secondary pseudowire when the primary is down. The mirror service switches the path back to the primary pseudowire when it is back up. The user can configure a timer to delay reverting back to primary or to never revert back.
If the active pseudowire goes down, the mirror service switches the path to a secondary sdp with the lowest precedence value. That is, secondary SDPs which are operationally up are considered in the order of their precedence value, 1 being the lowest value and 4 being the highest value. If the precedence value is the same, then the SDP with the lowest SDP ID is selected.
An explicitly named endpoint can have a maximum of one SAP and one ICB. Once a SAP is added to the endpoint, only one more object of type ICB SDP is allowed. An explicitly named endpoint, which does not have a SAP object, can have a maximum of four SDPs, which can include any of the following: a single primary SDP, one or many secondary SDPs with precedence, and a single ICB SDP.
An SDP is created with type secondary and with the lowest precedence value of 4.
Parameters
- precedence-value
-
Specifies the precedence of the SDP.
- primary
-
Specified that a special value of the precedence which assigns the SDP the lowest precedence and enables the revertive behavior.
Platforms
All
preempt
preempt
Syntax
[no] preempt
Context
[Tree] (config>service>vprn>sub-if>grp-if>srrp preempt)
[Tree] (config>service>ies>sub-if>grp-if>srrp preempt)
Full Context
configure service vprn subscriber-interface group-interface srrp preempt
configure service ies subscriber-interface group-interface srrp preempt
Description
When preempt is enabled, a newly initiated SRRP instance can overrides an existing Master SRRP instance if its priority value is higher than the priority of the current Master.
If preempt is disabled, an SRRP instance only becomes Master if the master down timer expires before an SRRP advertisement message is received from the adjacent SRRP enabled node.
The no form of this command reverts to the default.
Default
preempt
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preempt
Syntax
[no] preempt
Context
[Tree] (config>service>ies>if>ipv6>vrrp preempt)
Full Context
configure service ies interface ipv6 vrrp preempt
Description
The preempt mode value controls whether a specific backup virtual router preempts a lower priority master.
When preempt is enabled, the virtual router instance overrides any non-owner master with an "in use” message priority value less than the virtual router instance in-use priority value. If preempt is disabled, the virtual router only becomes master if the master down timer expires before a VRRP advertisement message is received from another virtual router.
The IP address owner will always become master when available. Preempt mode cannot be disabled on the owner virtual router.
The no form of this command disables preempt mode.
Default
preempt
Platforms
All
preempt
Syntax
[no] preempt
Context
[Tree] (config>service>ies>if>vrrp preempt)
Full Context
configure service ies interface vrrp preempt
Description
The preempt command provides the ability of overriding an existing non-owner master to the virtual router instance. Enabling preempt mode is almost required for proper operation of the base-priority and vrrp-policy-id definitions on the virtual router instance. If the virtual router cannot preempt an existing non-owner master, the effect of the dynamic changing of the in-use priority is greatly diminished.
The preempt command is only available in the non-owner vrrp virtual-router-id nodal context. The owner may not be preempted due to the fact that the priority of non-owners can never be higher than the owner. The owner will always preempt all other virtual routers when it is available.
Non-owner virtual router instances will only preempt when preempt is set and the current master has an in-use message priority value less than the virtual router instances in-use priority.
A master non-owner virtual router will only allow itself to be preempted when the incoming VRRP Advertisement message Priority field value is one of the following:
-
Greater than the virtual router in-use priority value
-
Equal to the in-use priority value and the source IP address (primary IP address) is greater than the virtual router instance primary IP address
The no form of this command prevents a non-owner virtual router instance from preempting another, less desirable virtual router. Use the preempt command to restore the default mode.
Default
preempt
Platforms
All
preempt
Syntax
[no] preempt
Context
[Tree] (config>service>vprn>if preempt)
[Tree] (config>service>vprn>if>ipv6>vrrp preempt)
Full Context
configure service vprn interface preempt
configure service vprn interface ipv6 vrrp preempt
Description
The preempt mode value controls whether a specific backup virtual router preempts a lower priority master.
When preempt is enabled, the virtual router instance overrides any non-owner master with an "in use” message priority value less than the virtual router instance in-use priority value. If preempt is disabled, the virtual router only becomes master if the master down timer expires before a VRRP advertisement message is received from another virtual router.
The IP address owner will always become master when available. Preempt mode cannot be disabled on the owner virtual router.
The default value for preempt mode is enabled.
Default
preempt
Platforms
All
preempt
Syntax
[no] preempt
Context
[Tree] (config>router>if>vrrp preempt)
[Tree] (config>router>if>ipv6>vrrp preempt)
Full Context
configure router interface vrrp preempt
configure router interface ipv6 vrrp preempt
Description
The preempt mode value controls whether a specific backup virtual router preempts a lower priority master.
When preempt is enabled, the virtual router instance overrides any non-owner master with an "in use” message priority value less than the virtual router instance in-use priority value. If preempt is disabled, the virtual router only becomes master if the master down timer expires before a VRRP advertisement message is received from another virtual router.
The IP address owner will always become master when available. Preempt mode cannot be disabled on the owner virtual router.
The default value for preempt mode is enabled.
Default
preempt
Platforms
All
preemption-timer
preemption-timer
Syntax
preemption-timer seconds
no preemption-timer
Context
[Tree] (config>router>rsvp preemption-timer)
Full Context
configure router rsvp preemption-timer
Description
This parameter configures the time in seconds a node holds to a reservation for which it triggered the soft preemption procedure.
The preempting node starts a separate preemption timer for each preempted LSP path. While this timer is on, the node should continue to refresh the Path and Resv for the preempted LSP paths. When the preemption timer expires, the node tears down the reservation if the head-end node has not already done so.
A value of zero means the LSP should be preempted immediately; hard preempted.
The no form of this command reverts to the default value.
Default
preemption-timer 300
Parameters
- seconds
-
Specifies the time (in s), of the preemption timer.
Platforms
All
prefer-failure
prefer-failure
Syntax
[no] prefer-failure
Context
[Tree] (config>service>nat>pcp-server-policy>option prefer-failure)
Full Context
configure service nat pcp-server-policy option prefer-failure
Description
This command enables/disables support for the prefer-failure option.
Default
no prefer-failure
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefer-local-time
prefer-local-time
Syntax
[no] prefer-local-time
Context
[Tree] (config>system>time prefer-local-time)
Full Context
configure system time prefer-local-time
Description
This command sets the preference to use local or UTC time in the system. This preference is applied to objects such as log file names, created and completed times reported in log files, NETCONF and gRPC date-and-time leafs, and rollback times displayed in show routines.
The operator may force the timezone used for show outputs during a CLI session using an environment variable in the environment>time-display {utc | local} command.
The preference for CLI output is set with the environment time-display command.
The format used for the date-time strings may change when the prefer-local-time option is enabled. For example, when enabled, all date-time strings include a suffix of three to five characters that indicates the timezone used for the presentation. This suffix may not be present if the option in not enabled.
The time format for timestamps on log events is controlled on a per-log basis using the config> log>log-id>time-format {utc | local} CLI command and not via prefer-local-time.
The no form of this command indicates preference for UTC time.
Default
no prefer-local-time
Platforms
All
prefer-mcast-tunnel-in-tunnel
prefer-mcast-tunnel-in-tunnel
Syntax
[no] prefer-mcast-tunnel-in-tunnel
Context
[Tree] (config>router>ldp prefer-mcast-tunnel-in-tunnel)
Full Context
configure router ldp prefer-mcast-tunnel-in-tunnel
Description
At a downstream router, this command specifies that for upstream FEC resolution a T-LDP session to the upstream peer is preferred over an I-LDP session.
At an upstream router, this command specifies that for downstream FEC resolution a T-LDP session to the downstream peer is preferred over an I-LDP session.
The no form of this command reverts to the default value.
Default
no prefer-mcast-tunnel-in-tunnel
Platforms
All
prefer-protocol-stitching
prefer-protocol-stitching
Syntax
[no] prefer-protocol-stitching
Context
[Tree] (config>router>ldp prefer-protocol-stitching)
Full Context
configure router ldp prefer-protocol-stitching
Description
This command stitches an LDP ILM to an SR NHLFE rather than to an LDP NHLFE when both LDP and SR NHLFEs exist.
The no form of this command stitches an LDP ILM to an LDP NHLFE by preference over an SR NHLFE.
Default
no prefer-protocol-stitching
Platforms
All
prefer-tunnel-in-tunnel
prefer-tunnel-in-tunnel
Syntax
[no] prefer-tunnel-in-tunnel
Context
[Tree] (config>router>ldp prefer-tunnel-in-tunnel)
Full Context
configure router ldp prefer-tunnel-in-tunnel
Description
This command specifies to use tunnel-in-tunnel over a simple LDP tunnel. Specifically, the user packets for LDP FECs learned over this targeted LDP session can be sent inside an RSVP LSP which terminates on the same egress router as the destination of the targeted LDP session. The user can specify an explicit list of RSVP LSP tunnels under the Targeted LDP session or LDP will perform a lookup in the Tunnel Table Manager (TTM) for the best RSVP LSP. In the former case, only the specified LSPs will be considered to tunnel LDP user packets. In the latter case, all LSPs available to the TTM and which terminate on the same egress router as this target ed LDP session will be considered. In both cases, the metric specified under the LSP configuration is used to control this selection.
The lookup in the TTM will prefer a LDP tunnel over an LDP-over-RSVP tunnel if both are available. Also, the tunneling operates on the dataplane only. Control packets of this targeted LDP session are sent over the IGP path.
Platforms
All
preference
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>l2tp>group>tunnel preference)
[Tree] (config>service>vprn>l2tp>group>tunnel preference)
Full Context
configure router l2tp group tunnel preference
configure service vprn l2tp group tunnel preference
Description
This command configures a preference number that indicates the relative preference assigned to a tunnel when using a weighted session assignment.
The no form of this command removes the preference value from the tunnel configuration.
Default
no preference
Parameters
- preference
-
Specifies the tunnel preference number with its group. The value 0 corresponds to the highest preference.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference
Syntax
preference preference-level
no preference
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel preference)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override preference)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle preference)
Full Context
configure mcast-management multicast-info-policy bundle channel preference
configure mcast-management multicast-info-policy bundle channel source-override preference
configure mcast-management multicast-info-policy bundle preference
Description
This command sets the relative preference level for multicast channels. The preference of a channel specifies its relative importance over other multicast channels. Eight levels of preference are supported; 0 through 7. Preference value 7 indicates the highest preference level.
When the multicast ingress path manager is congested on one or more of the switch fabric multicast paths, it uses the preference values associated with each multicast record to determine which records are allowed on the path and which records be placed in a black-hole state.
The preference value is also compared to the bundles cong-priority-threshold setting to determine the congestion priority of the channel. The result also dictates the channels multicast CAC class level (high or low). When the channels preference value is less than the congestion priority threshold, it is considered to have a congestion priority and CAC class value equal to low. When the channels preference value is equal to or greater than the threshold, it is considered to have a congestion priority and a CAC class value equal to high.
The preference value is also compared to the bundles ecmp-opt-threshold setting to determine whether the channel is eligible for ECMP path dynamic optimization. If the preference value is equal to or less than the threshold, the channel may be optimized. If the preference value is greater than the threshold, the channel will not be dynamically optimized.
The preference command may be executed in three contexts; bundle, channel and source-override. The bundle default preference value is 0. The channel and source-override preference settings are considered overrides to the bundle setting and have a default value of null (undefined).
The no form of this command restores the default preference value (0 or null depending on the context).
Parameters
- preference-level
-
The preference-level parameter is required and defines the preference value of the channel.
Platforms
All
preference
Syntax
[no] preference preference
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy preference)
Full Context
configure subscriber-mgmt bgp-peering-policy preference
Description
This command configures the route preference for routes learned from the configured peer.
The lower the preference the higher the chance of the route being the active route. The OS assigns BGP routes highest default preference compared to routes that are direct, static or learned via MPLS or OSPF.
The no form of this command used at the global level reverts to default value.
Default
preference 170
Parameters
- preference
-
The route preference, expressed as a decimal integer.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference
Syntax
preference preference
no preference
Context
[Tree] (config>aaa>diam>node>peer preference)
Full Context
configure aaa diameter node peer preference
Description
This command configures the Diameter routing preference for a peer. All open peers are installed in the Diameter realm routing table but only the one with the lowest numerical value for preference is used as next-hop for a given destination realm. If multiple peers with the same preference are configured for the same realm, the peer index with the lowest value is used to break the tie.
The no form of this command reverts to the default.
Default
preference 50
Parameters
- preference
-
Specifies the peer preference.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference
Syntax
preference preference
no preference
Context
[Tree] (config>aaa>diam>node>peer>route preference)
Full Context
configure aaa diameter node peer route preference
Description
This command configures the preference of the static route. The lower value is preferred during route selection.
The no form of this command reverts to the default.
Default
preference 50
Parameters
- preference
-
Specifies the static route preference.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference
Syntax
preference preference
no preference
Context
[Tree] (config>subscr-mgmt>sub-prof preference)
Full Context
configure subscriber-mgmt sub-profile preference
Description
This command sets the relative preference value for a subscriber profile. When multiple subscriber hosts/sessions of the same subscriber point to a different subscriber profile, the profile with the highest preference value is used. With equal preference, the subscriber profile of the last instantiated subscriber host/session is used.
Nokia recommends not to configure a subscriber profile preference value unless explicitly required for the targeted design.
The no form of this command reverts to the default value.
Default
preference 5
Parameters
- preference
-
Specifies the preference value. A lower number means a lower preference.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference
Syntax
preference [create] [non-revertive]
no preference
Context
[Tree] (config>service>system>bgp-evpn>eth-seg>service-carving>manual preference)
Full Context
configure service system bgp-evpn ethernet-segment service-carving manual preference
Description
This command creates the preference context for the Ethernet Segment (ES) and determines whether the DF election for the ES is revertive or not. Creation of the preference context ensures that the PE will run the preference-based DF election algorithm.
Parameters
- create
-
Mandatory keyword required to create the preference context in an ES.
- non-revertive
-
Configures a non-revertive ES, which ensures that when the Ethernet Segment comes back after a failure, it does not take over an existing active DF PE.
Platforms
All
preference
Syntax
[no] preference preference
Context
[Tree] (config>service>vprn>bgp>group preference)
[Tree] (config>service>vprn>bgp preference)
Full Context
configure service vprn bgp group preference
configure service vprn bgp preference
Description
This command configures the route preference for routes learned from the configured peer(s).
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The lower the preference the higher the chance of the route being the active route. The OS assigns BGP routes highest default preference compared to routes that are direct, static or learned via MPLS or OSPF.
The no form of this command, if used at the global level, reverts to default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
preference 170
Parameters
- preference
-
Specifies the route preference, expressed as a decimal integer.
Platforms
All
preference
Syntax
preference preference-value
no preference
Context
[Tree] (config>service>vprn>static-route-entry>next-hop preference)
[Tree] (config>service>vprn>static-route-entry>indirect preference)
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel preference)
[Tree] (config>service>vprn>static-route-entry>black-hole preference)
[Tree] (config>service>vprn>static-route-entry>grt preference)
Full Context
configure service vprn static-route-entry next-hop preference
configure service vprn static-route-entry indirect preference
configure service vprn static-route-entry ipsec-tunnel preference
configure service vprn static-route-entry black-hole preference
configure service vprn static-route-entry grt preference
Description
This command specifies the route preference to be assigned to the associated static route. The lower the preference value the more preferred the route is considered.
Default Route Preference lists the default route preference based on the route source.
|
Label |
Preference |
Configurable |
|---|---|---|
|
Direct attached |
0 |
No |
|
Static route |
5 |
Yes |
|
OSPF Internal routes |
10 |
Yes |
|
IS-IS level 1 internal |
15 |
Yes |
|
IS-IS level 2 internal |
18 |
Yes |
|
RIP |
100 |
Yes |
|
Aggregate |
130 |
No |
|
OSPF external |
150 |
Yes |
|
IS-IS level 1 external |
160 |
Yes |
|
IS-IS level 2 external |
165 |
Yes |
|
BGP |
170 |
Yes |
The no form of this command returns the returns the associated static route preference to its default value.
Default
preference 5
Parameters
- preference-value
-
Specifies the route preference value.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>service>vprn>isis>level preference)
Full Context
configure service vprn isis level preference
Description
This command configures the preference level of either IS-IS Level 1 or IS-IS Level 2 internal routes. By default, the preferences are listed in the table below.
A route can be learned by the router by different protocols, in which case, the costs are not comparable. When this occurs, the preference is used to decide to which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the default preference table as defined in the table below. If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the decision what route to use is determined by the configuration of the ecmp in the config>router context.
Default
Default preferences are listed in Default Preferences.
|
Route Type |
Preference |
Configurable |
|---|---|---|
|
Direct attached |
0 |
No |
|
Static route |
5 |
Yes |
|
MPLS |
7 |
— |
|
OSPF internal routes |
10 |
No |
|
IS-IS level 1 internal |
15 |
Yes |
|
IS-IS level 2 internal |
18 |
Yes |
|
OSPF external |
150 |
Yes |
|
IS-IS level 1 external |
160 |
Yes1 |
|
IS-IS level 2 external |
165 |
Yes1 |
|
BGP |
170 |
Yes |
Parameters
- preference
-
The preference for external routes at this level expressed as a decimal integer.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>service>vprn>ospf3 preference)
[Tree] (config>service>vprn>ospf preference)
Full Context
configure service vprn ospf3 preference
configure service vprn ospf preference
Description
This command configures the preference for OSPF internal routes.
A route can be learned by the router from different protocols in which case the costs are not comparable, when this occurs the preference is used to decide to which route will be used.
Different protocols should not be configured with the same preference. If the same preference is configured, the tiebreaker is per the default preference table as defined in Default Route Preferences . If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used.
If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the decision of what route to use is determined by the configuration of the ecmp in the config>router context.
The no form of this command reverts to the default value.
|
Route Type |
Preference |
Configurable |
|---|---|---|
|
Direct attached |
0 |
No |
|
Static routes |
5 |
Yes |
|
OSPF internal |
10 |
Yes2 |
|
IS-IS level 1 internal |
15 |
Yes |
|
IS-IS level 2 internal |
18 |
Yes |
|
RIP |
100 |
Yes |
|
OSPF external |
150 |
Yes |
|
IS-IS level 1 external |
160 |
Yes |
|
IS-IS level 2 external |
165 |
Yes |
Default
preference 10 — OSPF internal routes have a preference of 10.
Parameters
- preference
-
The preference for internal routes expressed as a decimal integer. Defaults for different route types are listed in the following table.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>service>vprn>rip>group>neighbor preference)
[Tree] (config>service>vprn>rip>group preference)
[Tree] (config>service>vprn>rip preference)
[Tree] (config>service>vprn>ripng>group>neighbor preference)
[Tree] (config>service>vprn>ripng>group preference)
[Tree] (config>service>vprn>ripng preference)
Full Context
configure service vprn rip group neighbor preference
configure service vprn rip group preference
configure service vprn rip preference
configure service vprn ripng group neighbor preference
configure service vprn ripng group preference
configure service vprn ripng preference
Description
This command sets the route preference assigned to RIP routes. This value can be overridden by route policies.
The no form of this command resets the preference to the default.
Default
no preference
Parameters
- preference
-
Specifies the preference value.
Platforms
All
preference
Syntax
preference preference-value
no preference
Context
[Tree] (config>router>mpls>fwd-policies>fwd-policy preference)
Full Context
configure router mpls forwarding-policies forwarding-policy preference
Description
This command configures the preference of an MPLS forwarding policy.
The no form of this command removes the preference parameter from the MPLS forwarding policy.
Default
preference 255
Parameters
- preference-value
-
Specifies the preference value.
The preference-value parameter allows the user to configure multiple label-binding forwarding policies with the same binding label or multiple endpoint policies with the same endpoint address. This provides the capability to achieve a 1:N backup strategy for the forwarding policy. Only the most preferred, lowest numerically preference value, policy is activated in data path.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>p2mp-sr-tree>p2mp-policy>candidate-path preference)
Full Context
configure router p2mp-sr-tree p2mp-policy candidate-path preference
Description
This command sets the candidate path preference for the P2MP SR tree. The candidate path with the highest preference is the active candidate path.
The no form of this command removes the candidate path preference.
Default
no preference
Parameters
- preference
-
Specifies the preference of the candidate path.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>static-route-entry>black-hole preference)
[Tree] (config>router>static-route-entry>indirect preference)
[Tree] (config>router>static-route-entry>next-hop preference)
Full Context
configure router static-route-entry black-hole preference
configure router static-route-entry indirect preference
configure router static-route-entry next-hop preference
Description
This command specifies the route preference to be assigned to the associated static route. The lower the preference value the more preferred the route is considered.
Default Route Preference shows the default route preference based on the route source.
|
Label |
Preference |
Configurable |
|---|---|---|
|
Direct attached |
0 |
No |
|
Static route |
5 |
Yes |
|
OSPF Internal routes |
10 |
Yes |
|
IS-IS level 1 internal |
15 |
Yes |
|
IS-IS level 2 internal |
18 |
Yes |
|
RIP |
100 |
Yes |
|
Aggregate |
130 |
No |
|
OSPF external |
150 |
Yes |
|
IS-IS level 1 external |
160 |
Yes |
|
IS-IS level 2 external |
165 |
Yes |
|
BGP |
170 |
Yes |
The no form of this command returns the returns the associated static route preference to its default value.
Default
preference 5
Parameters
- preference
-
Specifies the route preference value.
Platforms
All
preference
Syntax
[no] preference preference
Context
[Tree] (config>router>bgp>group preference)
[Tree] (config>router>bgp>group>neighbor preference)
[Tree] (config>router>bgp preference)
Full Context
configure router bgp group preference
configure router bgp group neighbor preference
configure router bgp preference
Description
This command configures the route preference for routes learned from the configured peers.
This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in peer-group) or neighbor level (only applies to specified peer). The most specific value is used.
The lower the preference the higher the chance of the route being the active route. The router assigns BGP routes highest default preference compared to routes that are direct, static or learned via MPLS or OSPF.
The no form of this command used at the global level reverts to default value.
The no form of this command used at the group level reverts to the value defined at the global level.
The no form of this command used at the neighbor level reverts to the value defined at the group level.
Default
preference 170
Parameters
- preference
-
Specifies the route preference expressed as a decimal integer.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>isis>level preference)
Full Context
configure router isis level preference
Description
This command configures the preference level of either IS-IS Level 1 or IS-IS Level 2 internal routes. By default, the preferences are listed in the table below.
A route can be learned by the router by different protocols, in which case, the costs are not comparable. When this occurs, the preference is used to decide to which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the default preference table as defined in the following table. If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the decision what route to use is determined by the configuration of the ecmp in the config>router context.
Default
preference (Level 1) — 15
preference (Level 2) — 18
Parameters
- preference
-
Specifies the preference for external routes at this level expressed as a decimal integer. The default preferences are listed in Default Internal Route Preferences .
Table 7. Default Internal Route Preferences Route Type
Preference
Configurable
Direct attached
0
—
Static-route
5
Yes
OSPF internal routes
10
—
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes3 IS-IS level 2 external
165
Yes3 BGP
170
Yes
1 External preferences are changed using the external-preference command in the config>router>isis>level level-number context.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>ospf3 preference)
[Tree] (config>router>ospf preference)
Full Context
configure router ospf3 preference
configure router ospf preference
Description
This command configures the preference for OSPF internal routes.
A route can be learned by the router from different protocols, in which case, the costs are not comparable. When this occurs, the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the default preference table as defined in Route Preference Defaults by Route Type . If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used.
If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the decision of what route to use is determined by the configuration of the ecmp in the config>router context.
The no form of this command reverts to the default value.
Default
preference 10
Parameters
- preference
-
Specifies the preference for internal routes expressed as a decimal integer. Defaults for different route types are listed in Route Preference Defaults by Route Type .
Table 8. Route Preference Defaults by Route Type Route Type
Preference
Configurable
Direct attached
0
No
Static routes
5
Yes
OSPF internal
10
Yes4 IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
RIP
100
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes
IS-IS level 2 external
165
Yes
BGP
170
Yes
1 Preference for OSPF internal routes is configured with the preference command.
Platforms
All
preference
Syntax
preference {none | all}
no preference
Context
[Tree] (config>router>ospf>lfa>mhp preference)
[Tree] (config>router>isis>lfa>mhp preference)
Full Context
configure router ospf loopfree-alternates multi-homed-prefix preference
configure router isis loopfree-alternates multi-homed-prefix preference
Description
This command configures the preference for the multihomed prefix LFA backup path. This knob can be enabled at a LFA computing node to force the programming of the multihomed prefix LFA backup path which, in some topologies, can avoid transiting using the best ABR or ASBR.
The no form of this command reverts to the default value.
Default
preference none
Parameters
- none
-
Specifies the preference for an LFA, TI-LFA, or RLFA backup path over the multihomed prefix LFA backup path. The multihomed prefix LFA is only programmed in cases where the prefix is not protected by LFA, RLFA, or TI-LFA.
- all
-
Specifies the forced programming of the multihomed prefix LFA backup path regardless of the outcome of the LFA, TI-LFA, or RLFA backup path computation.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>ripng>group>neighbor preference)
[Tree] (config>router>ripng preference)
[Tree] (config>router>ripng>group preference)
[Tree] (config>router>rip preference)
[Tree] (config>router>rip>group preference)
[Tree] (config>router>rip>group>neighbor preference)
Full Context
configure router ripng group neighbor preference
configure router ripng preference
configure router ripng group preference
configure router rip preference
configure router rip group preference
configure router rip group neighbor preference
Description
This command configures the preference for RIP routes.
A route can be learned by the router from different protocols in which case the costs are not comparable. When this occurs, the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is per the default preference table as defined in Route Preference Defaults by Route Type . If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used.
If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the decision of what route to use is determined by the configuration of the ecmp in the config>router context.
The no form of the command reverts to the default value.
Default
preference 100
Parameters
- preference
-
Specifies the preference for RIP routes expressed as a decimal integer. Defaults for different route types are listed in Route Preference Defaults by Route Type .
Table 9. Route Preference Defaults by Route Type Route Type
Preference
Configurable
Direct attached
0
—
Static routes
5
Yes
OSPF internal
10
Yes
IS-IS level 1 internal
15
Yes
IS-IS level 2 internal
18
Yes
RIP
100
Yes
OSPF external
150
Yes
IS-IS level 1 external
160
Yes
IS-IS level 2 external
165
Yes
BGP
170
Yes
Platforms
All
preference
Syntax
preference preference
Context
[Tree] (conf>router>segment-routing>sr-policies>policy preference)
Full Context
configure router segment-routing sr-policies static-policy preference
Description
This command associates a preference value with a statically defined-segment routing policy. This is an optional parameter.
When there are multiple policies for the same (color, endpoint) combination that are targeted for local installation, only one is selected as the active path for the (color, endpoint). In this selection process (which considers both static local policies and BGP signaled policies), the policy with the highest preference value is preferred over all policies with a lower preference value.
The no form of this command reverts to the default value.
Default
preference 100
Parameters
- preference
-
Specifies the preference ID.
Platforms
All
preference
Syntax
preference preference
no preference
Context
[Tree] (config>router>policy-options>policy-statement>name>default-action preference)
[Tree] (config>router>policy-options>policy-statement>entry>action preference)
Full Context
configure router policy-options policy-statement name default-action preference
configure router policy-options policy-statement entry action preference
Description
This command assigns a route preference to routes matching the route policy statement entry.
If no preference is specified, the default Route Table Manager (RTM) preference for the protocol is used.
The no form of this command disables setting an RTM preference in the route policy entry.
This command is supported with the following protocols: RIP import, BGP import, VPRN VRF import ( vrf-import), and VPRN GRT lookup export (export-grt).
Default
no preference
Parameters
- preference
-
Specifies the route preference expressed as a decimal integer.
Platforms
All
preference
Syntax
preference value
Context
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry preference)
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry preference)
Full Context
configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry preference
configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry preference
Description
This command associates a preference with the provisioned managed route.
Parameters
- value
-
Specifies the preference value.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preference-option
preference-option
Syntax
[no] preference-option
Context
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>asel>clnt-mac preference-option)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>asel preference-option)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>asel>srvr preference-option)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>asel preference-option)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>asel>clnt-mac preference-option)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>relay>asel>srvr preference-option)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>asel preference-option)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>relay>asel>srvr preference-option)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>relay>asel>clnt-mac preference-option)
Full Context
configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection client-mac preference-option
configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection preference-option
configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection server preference-option
configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection preference-option
configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection client-mac preference-option
configure service ies subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection server preference-option
configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection preference-option
configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay advertise-selection server preference-option
configure service vprn subscriber-interface ipv6 dhcp6 relay advertise-selection client-mac preference-option
Description
This command enables the DHCPv6 preference option that is inserted in the DHCPv6 advertise message.
The no form of this command removes the preference option.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preferred
preferred
Syntax
[no] preferred
Context
[Tree] (config>isa>nat-group>inter-chassis-redundancy preferred)
Full Context
configure isa nat-group inter-chassis-redundancy preferred
Description
This command sets the preference for activity of a nat-group in stateful inter-chassis redundancy configuration if both nodes have equal health. An example of where this can be useful is in a load balancing environment where the activity of NAT groups can be distributed between the two redundant nodes.
A nat-group with preferred command configured on a node that freshly became part of multi-chassis redundancy, takes over activity from an existing and traffic-serving node with equal health that does not have the preferred command configured. This causes a switchover and a brief interruption in traffic flow.
By default the preferred status is not set for the node.
The no form of this command reverts to the default.
Default
no preferred
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
preferred-lifetime
preferred-lifetime
Syntax
preferred-lifetime [days days] [hrs hours] [min minutes] [sec seconds]
preferred-lifetime infinite
no preferred-lifetime
Context
[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ipv6-lease-times preferred-lifetime)
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ipv6-lease-times preferred-lifetime)
Full Context
configure subscriber-mgmt local-user-db ppp host ipv6-lease-times preferred-lifetime
configure subscriber-mgmt local-user-db ipoe host ipv6-lease-times preferred-lifetime
Description
This command specifies the preferred lifetime for the lease times. When the preferred lifetime expires, then any derived addresses are deprecated.
The no form of this command reverts to the default.
Parameters
- infinite
-
Specifies that the valid lifetime is infinite.
- preferred-lifetime
-
Specifies the preferred lifetime.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preferred-lifetime
Syntax
preferred-lifetime [days days] [ hrs hours] [min minutes] [sec seconds]
no preferred-lifetime
Context
[Tree] (config>router>dhcp6>server>defaults preferred-lifetime)
[Tree] (config>service>vprn>dhcp6>server>pool>prefix preferred-lifetime)
[Tree] (config>router>dhcp6>server>pool>prefix preferred-lifetime)
[Tree] (config>service>vprn>dhcp6>server>defaults preferred-lifetime)
Full Context
configure router dhcp6 local-dhcp-server defaults preferred-lifetime
configure service vprn dhcp6 local-dhcp-server pool prefix preferred-lifetime
configure router dhcp6 local-dhcp-server pool prefix preferred-lifetime
configure service vprn dhcp6 local-dhcp-server defaults preferred-lifetime
Description
This command configures the preferred lifetime.
The no form of this command reverts to the default value.
Default
preferred-lifetime hrs 1
Parameters
- preferred-lifetime
-
Specifies the preferred time for a prefix.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn dhcp6 local-dhcp-server defaults preferred-lifetime
- configure router dhcp6 local-dhcp-server defaults preferred-lifetime
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure router dhcp6 local-dhcp-server pool prefix preferred-lifetime
- configure service vprn dhcp6 local-dhcp-server pool prefix preferred-lifetime
preferred-lifetime
Syntax
preferred-lifetime seconds
preferred-lifetime infinite
no preferred-lifetime
Context
[Tree] (config>service>vprn>if>ipv6>dhcp6>pfx-delegate>prefix preferred-lifetime)
[Tree] (config>service>ies>if>ipv6>dhcp6>pfx-delegate>prefix preferred-lifetime)
Full Context
configure service vprn interface ipv6 dhcp6-server prefix-delegation prefix preferred-lifetime
configure service ies interface ipv6 dhcp6-server prefix-delegation prefix preferred-lifetime
Description
This command configures the IPv6 prefix/mask preferred lifetime. The preferred-lifetime value cannot be bigger than the valid-lifetime value.
The no form of this command reverts to the default value.
Default
preferred-lifetime 604800 (7 days)
Parameters
- seconds
-
Specifies the time, in seconds, that this prefix remains preferred.
- infinite
-
Specifies that this prefix remains preferred infinitely.
Platforms
All
preferred-lifetime
Syntax
preferred-lifetime seconds
preferred-lifetime infinite
no preferred-lifetime
Context
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv>pfx-opt preferred-lifetime)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv>pfx-opt preferred-lifetime)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv>pfx-opt preferred-lifetime)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv>pfx-opt preferred-lifetime)
Full Context
configure service ies subscriber-interface ipv6 router-advertisements prefix-options preferred-lifetime
configure service vprn subscriber-interface group-interface ipv6 router-advertisements prefix-options preferred-lifetime
configure service ies subscriber-interface group-interface ipv6 router-advertisements prefix-options preferred-lifetime
configure service vprn subscriber-interface ipv6 router-advertisements prefix-options preferred-lifetime
Description
This command specifies the remaining time for this prefix to be preferred, thus time until deprecation.
The no form of this command reverts to the default.
Default
preferred-lifetime 3600
Parameters
- seconds
-
Specifies the time for the prefix to remain preferred on this group-interface in seconds.
- infinite
-
Specifies that the remaining time will never expire. The value 4294967295 is interpreted as infinite.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preferred-lifetime
Syntax
preferred-lifetime seconds
preferred-lifetime infinite
no preferred-lifetime
Context
[Tree] (config>subscr-mgmt>rtr-adv>pfx-opt>stateful preferred-lifetime)
[Tree] (config>subscr-mgmt>rtr-adv>pfx-opt>stateless preferred-lifetime)
Full Context
configure subscriber-mgmt router-advertisement-policy prefix-options stateful preferred-lifetime
configure subscriber-mgmt router-advertisement-policy prefix-options stateless preferred-lifetime
Description
This command specifies the remaining time for this prefix to be preferred.
The no form of this command reverts to the default.
Default
preferred-lifetime 3600
Parameters
- seconds
-
Specifies the time, in seconds, for the prefix to remain preferred.
- infinite
-
Specifies that the remaining time never expires.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preferred-lifetime
Syntax
preferred-lifetime infinite
preferred-lifetime [days days] [hrs hours] [min minutes] [sec seconds]
no preferred-lifetime
Context
[Tree] (config>service>ies>sub-if>ipv6>dhcp6>proxy-server preferred-lifetime)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>proxy-server preferred-lifetime)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>proxy-server preferred-lifetime)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>proxy-server preferred-lifetime)
Full Context
configure service ies subscriber-interface ipv6 dhcp6 proxy-server preferred-lifetime
configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server preferred-lifetime
configure service vprn subscriber-interface ipv6 dhcp6 proxy-server preferred-lifetime
configure service ies subscriber-interface group-interface ipv6 dhcp6 proxy-server preferred-lifetime
Description
This command configures the preferred lifetime. When the preferred lifetime expires, any derived addresses are deprecated.
Default
preferred-lifetime hrs 1
Parameters
- infinite
-
Specifies that the preferred lifetime is infinite.
- days days
-
Specifies the number of days of a preferred lifetime.
- hrs hours
-
Specifies the number of hours of a preferred lifetime.
- min minutes
-
Specifies the number of minutes of a preferred lifetime.
- sec seconds
-
Specifies the number of seconds of a preferred lifetime.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
preferred-lifetime
Syntax
[no] preferred-lifetime {seconds | infinite}
Context
[Tree] (config>service>vprn>router-advert>if>prefix preferred-lifetime)
[Tree] (config>router>router-advert>if>prefix preferred-lifetime)
Full Context
configure service vprn router-advertisement interface prefix preferred-lifetime
configure router router-advertisement interface prefix preferred-lifetime
Description
This command configures the remaining length of time in seconds that this prefix will continue to be preferred, such as, time until deprecation. The address generated from a deprecated prefix should not be used as a source address in new communications, but packets received on such an interface are processed as expected.
Default
preferred-lifetime 604800
Parameters
- seconds
-
Specifies the remaining length of time in seconds that this prefix will continue to be preferred.
- infinite
-
Specifies that the prefix will always be preferred. A value of 4,294,967,295 represents infinity.
Platforms
All
prefix
prefix
Syntax
prefix ipv6-addr/prefix-length [failover {local | remote | access-driven}] [pd] [wan-host] [create]
no prefix ipv6-addr/prefix-length
Context
[Tree] (config>router>dhcp6>server>pool prefix)
[Tree] (config>service>vprn>dhcp6>server>pool prefix)
Full Context
configure router dhcp6 local-dhcp-server pool prefix
configure service vprn dhcp6 local-dhcp-server pool prefix
Description
This command allocates a prefix to a pool from which Prefix Delegation prefixes and or WAN addresses can be assigned for DHCP6.
The no form of this command removes the prefix parameters from the configuration.
Default
prefix failover local
Parameters
- prefix ipv6-addr/prefix-length
-
Specifies the prefix.
- failover {local | remote | access-driven}
-
This command designates a prefix as local, remote, or access-driven. This is used when multi-chassis synchronization is enabled.
- pd
-
Specifies that this aggregate is used by IPv6 ESM hosts for DHCPv6 prefix-delegation.
- wan-host
-
Specifies that this aggregate is used by IPv6 ESM hosts for local addressing or by a routing gateway’s WAN interface.
- create
-
Keyword used to create the prefix configuration. 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
prefix
Syntax
[no] prefix ipv6-address/prefix-length
Context
[Tree] (config>service>ies>if>ipv6>dhcp6-server>pfx-delegate prefix)
Full Context
configure service ies interface ipv6 dhcp6-server prefix-delegation prefix
Description
This command specifies the IPv6 prefix that is delegated by this system.
The no form of this command reverts to the default.
Parameters
- ipv6-address/prefix-length
-
Specifies the IPv6 address on the interface
Platforms
All
prefix
Syntax
prefix ipv6-address/prefix-length [pd] [wan-host]
no prefix ipv6-address/prefix-length
Context
[Tree] (config>service>vprn>sub-if>ipv6>sub-pfx prefix)
[Tree] (config>service>ies>sub-if>ipv6>sub-pfx prefix)
Full Context
configure service vprn subscriber-interface ipv6 subscriber-prefixes prefix
configure service ies subscriber-interface ipv6 subscriber-prefixes prefix
Description
This command allows a list of prefixes (using the prefix command multiple times) to be routed to hosts associated with this subscriber interface. Each prefix is represented in the associated FDB with a reference to the subscriber interface. Prefixes are defined as being for prefix delegation (pd) or use on a WAN interface or host (wan-host).
The no form of this command reverts to the default.
Parameters
- ipv6-address
-
Specifies the 128-bit IPv6 address.
- prefix-length
-
Specifies the length of any associated aggregate prefix.
- pd
-
Specifies that this aggregate is used by IPv6 ESM hosts for DHCPv6 prefix-delegation.
- wan-host
-
Specifies that this aggregate is used by IPv6 ESM hosts for local addressing or by a routing gateway’s WAN interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix low-order-vsi-id
no prefix
Context
[Tree] (config>service>vpls>bgp-ad>vsi-id prefix)
Full Context
configure service vpls bgp-ad vsi-id prefix
Description
This command specifies the low-order 4 bytes used to compose the Virtual Switch Instance Identifier (VSI-ID) to use for NLRI in BGP auto-discovery in this VPLS service.
If no value is set, the system IP address will be used.
Default
no prefix
Parameters
- low-order-vsi-id
-
Specifies a unique VSI ID
Platforms
All
prefix
Syntax
[no] prefix ip-prefix/prefix-length
Context
[Tree] (config>service>vprn>bgp>group>dynamic-neighbor>match prefix)
Full Context
configure service vprn bgp group dynamic-neighbor match prefix
Description
This command configures a prefix to accept dynamic BGP sessions (sessions from source IP addresses not matching any configured neighbor addresses). A dynamic session is associated with the group having the longest match prefix entry for the source IP address of the peer. The group association determines local parameters that apply to the session, including the local AS, the local IP address, the MP-BGP families, the import and export policies, and so on.
The no form of this command removes a prefix entry.
Parameters
- ip-prefix/prefix-length
-
Specifies a prefix from which to accept dynamic BGP sessions.
Platforms
All
prefix
Syntax
[no] prefix ipv6-prefix/prefix-length
Context
[Tree] (config>service>vprn>router-advert>if prefix)
Full Context
configure service vprn router-advertisement interface prefix
Description
This command configures an IPv6 prefix in the router advertisement messages. To support multiple IPv6 prefixes, use multiple prefix statements. No prefix is advertised until explicitly configured using prefix statements.
Parameters
- ipv6-prefix
-
Specifies the IP prefix for prefix list entry in dotted decimal notation.
- prefix-length
-
Specifies a route must match the most significant bits and have a prefix length.
Platforms
All
prefix
Syntax
prefix prefix-string
no prefix
Context
[Tree] (config>app-assure>group>cflowd>export-override prefix)
Full Context
configure application-assurance group cflowd export-override prefix
Description
This command specifies the prefix-string associated with the export-override.
Parameters
- prefix-string
-
Specifies a prefix string,up to eight characters. If the eight-character prefix is "ABCDEFG_" for a particular node, the cflowd export override would generate IPv4 interface names such as ABCDEFG_255.255.255.255 or IPv6 as ABCDEFG_2001:DB8:EF01:2345::/64. By default the prefix will be left blank.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix ip-prefix/ip-prefix-length [name prefix-name]
no prefix ip-prefix/ip-prefix-length
Context
[Tree] (config>app-assure>group>ip-prefix-list prefix)
Full Context
configure application-assurance group ip-prefix-list prefix
Description
This command configures an IP prefix within the list.
The no form of this command removes the IP prefix from the configuration.
Parameters
- ip-prefix/ip-prefix-length
-
The IP address in dotted decimal notation.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix ipv6-prefix/prefix-length
no prefix
Context
[Tree] (config>router>nat>inside>nat64 prefix)
[Tree] (config>service>vprn>nat>inside>nat64 prefix)
Full Context
configure router nat inside nat64 prefix
configure service vprn nat inside nat64 prefix
Description
This command configures the IPv6 prefix used to derive the IPv6 address from the IPv4 address, and is same as the prefix used by DNS64 to generate AAAA record returned for IPv4 endpoint resolution. NAT64 node announces this prefix in routing to attract traffic from IPv6 hosts. If the prefix is not configured, then a well-known prefix, 64:FF9B::/96, is used.
The no form of the command removes the prefix from the NAT64 configuration.
Parameters
- ipv6-prefix/prefix-length
-
Specifies the NAT64 destination prefix.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix ip-prefix/length [nat-policy nat-policy-name]
no prefix ip-prefix/length
Context
[Tree] (config>service>nat>nat-prefix-list prefix)
Full Context
configure service nat nat-prefix-list prefix
Description
This command creates a prefix entry in the nat-prefix-list.
This prefix can be used to identify traffic with specific destination IP that needs to be associated with corresponding nat-policy (and implicitly the NAT pool) for L2-aware subscribers. In this fashion, a single L2-aware subscriber can direct traffic to multiple NAT pools, depending on the traffic destination.
Another use for a prefix is in DNAT-only application (DNAT without SNAPT). In this case the prefix identifies the inside source IP range that will be explicitly configured to ensure proper downstream routing in dNAT-only case.
The nat-prefix-list cannot reference the default nat-policy (the one that is referenced in the subscriber-profile).
The no form of the command reverts to the default.
Parameters
- ip-prefix/length
-
Specifies the IP prefix for nat prefix list entry in dotted decimal notation.
- nat-policy nat-policy-name
-
Specifies the NAT policy name. Allowed values are any string up to 32 characters composed of printable,7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes..
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix prefix/prefix-length [ create]
no prefix prefix/prefix-length
Context
[Tree] (config>router>firewall>domain prefix)
[Tree] (config>service>vprn>firewall>domain prefix)
Full Context
configure router firewall domain prefix
configure service vprn firewall domain prefix
Description
This command specifies a prefix for which firewall functionality will apply within the domain. Prefixes cannot be shared or duplicated across multiple domains in the same routing context. A domain can contain multiple prefixes.
The no form of the command removes the prefix from the domain.
Parameters
- create
-
Mandatory keyword used when creating a prefix entry.
- prefix/prefix-length
-
Specifies the prefix.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix
Syntax
prefix ip-address
no prefix
Context
[Tree] (config>router>bier>template>sub-domain prefix)
Full Context
configure router bier template sub-domain prefix
Description
This command specifies the prefix used for BFR. The prefix should be an IPv4 /32 address. The prefix can be a loopback interface or system IP address.
The no form of this command removes the prefix.
Parameters
- ip-address
-
Specifies the IP address to be used as the BFR prefix in dotted decimal format.
Platforms
All
prefix
Syntax
prefix ip-prefix/prefix-length [create]
no prefix ip-prefix/prefix-length
Context
[Tree] (config>test-oam>twamp>server prefix)
Full Context
configure test-oam twamp server prefix
Description
This command configures an IP address prefix containing one or more TWAMP clients. For a TWAMP client to connect to the TWAMP server (and subsequently conduct tests) it must establish the control connection using an IP address that is part of a configured prefix.
Parameters
- ip-prefix/prefix-length
-
Specifies an IPv4 or IPv6 address prefix.
- prefix length
-
Specifies the prefix length.
- create
-
Creates a prefix instance. 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, 7950 XRS
prefix
Syntax
prefix ip-prefix/prefix-length [create]
no prefix ip-prefix/prefix-length
Context
[Tree] (config>service>vprn>twamp-light>reflector prefix)
[Tree] (config>router>twamp-light>reflector prefix)
Full Context
configure service vprn twamp-light reflector prefix
configure router twamp-light reflector prefix
Description
This command defines which TWAMP Light packet prefixes the reflector processes.
The no form of this command with the specific prefix removes the accepted source.
Parameters
- ip-prefix/prefix-length
-
Specifies the IPv4 or IPv6 address and length.
- create
-
Creates a prefix instance. 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, 7950 XRS
prefix
Syntax
[no] prefix ip-prefix/prefix-length
Context
[Tree] (config>qos>match-list>ip-prefix-list prefix)
Full Context
configure qos match-list ip-prefix-list prefix
Description
This command adds an IPv4 address prefix to an existing IPv4 address prefix match list.
To add a set of unique prefixes, execute the command with all unique prefixes. The prefixes are allowed to overlap IPv4 address space.
An IPv4 prefix addition will be blocked, if resource exhaustion is detected anywhere in the system because of QoS Policies that use this IPv4 address prefix list.
The no form of this command deletes the specified prefix from the list.
Parameters
- ip-prefix
-
A valid IPv4 address prefix in dotted decimal notation.
- prefix-length
-
Length of the entered IP prefix
Platforms
All
prefix
Syntax
[no] prefix ipv6-prefix/prefix-length
Context
[Tree] (config>qos>match-list>ipv6-prefix-list prefix)
Full Context
configure qos match-list ipv6-prefix-list prefix
Description
This command adds an IPv6 address prefix to an existing IPv6 address prefix match list.
To add set of unique prefixes, execute the command with all unique prefixes. The prefixes are allowed to overlap IPv6 address space.
An IPv6 prefix addition will be blocked if resource exhaustion is detected anywhere in the system because of QoS Policies that use this IPv6 address prefix list.
The no form of this command deletes the specified prefix from the list.
Parameters
- ipv6-prefix
-
Specifies the IPv6 prefix for the IP match criterion in hex digits.
- prefix-length
-
Specifies the IPv6 prefix length for the IPv6 address expressed as a decimal integer.
Platforms
All
prefix
Syntax
[no] prefix ip-prefix/prefix-length
Context
[Tree] (config>filter>match-list>ip-prefix-list prefix)
Full Context
configure filter match-list ip-prefix-list prefix
Description
This command adds an IPv4 address prefix to an existing IPv4 address prefix match list.
The no form of this command deletes the specified prefix from the list.
Operational Notes:
To add set of unique prefixes, execute the command with all unique prefixes. The prefixes are allowed to overlap IPv4 address space.
An IPv4 prefix addition will be blocked, if resource exhaustion is detected anywhere in the system because of filter policies that use this IPv4 address prefix list.
Parameters
- ip-prefix
-
Specifies a valid IPv4 address prefix in dotted decimal notation.
- prefix-length
-
Specifies the length of the entered IPv4 prefix.
Platforms
All
prefix
Syntax
[no] prefix ipv6-prefix/prefix-length
Context
[Tree] (config>filter>match-list>ipv6-prefix-list prefix)
Full Context
configure filter match-list ipv6-prefix-list prefix
Description
This command adds an IPv6 address prefix to an existing IPv6 address prefix match list.
The no form of this command deletes the specified prefix from the list.
Operational Notes:
To add set of different prefixes, execute the command with all unique prefixes. The prefixes are allowed to overlap IPv6 address space.
An IPv6 prefix addition will be blocked, if resource exhaustion is detected anywhere in the system because of filter policies that use this IPv6 address prefix list.
Parameters
- ipv6-prefix/prefix-length
-
Specifies an IPv6 address prefix written as hexadecimal numbers separated by colons with host bits set to 0. One string of zeros can be omitted, so 2001:db8::700:0:217A is equivalent to 2001:db8:0:0:0:700:0:217A.
- prefix-length
-
Specifies the length of the entered IPv6 prefix.
Platforms
All
prefix
Syntax
[no] prefix ipv6-prefix/prefix-length
Context
[Tree] (config>router>router-advert>if prefix)
Full Context
configure router router-advertisement interface prefix
Description
This command configures an IPv6 prefix in the router advertisement messages. To support multiple IPv6 prefixes, use multiple prefix statements. No prefix is advertised until explicitly configured using prefix statements.
Parameters
- ipv6-prefix
-
The IP prefix for prefix list entry in dotted decimal notation.
- prefix-length
-
Specifies a route must match the most significant bits and have a prefix length.
Platforms
All
prefix
Syntax
[no] prefix ip-prefix/ip-prefix-length
Context
[Tree] (config>router>bgp>group>dynamic-neighbor>match prefix)
Full Context
configure router bgp group dynamic-neighbor match prefix
Description
This command configures a prefix to accept dynamic BGP sessions (sessions from source IP addresses not matching any configured neighbor addresses). A dynamic session is associated with the group having the longest match prefix entry for the source IP address of the peer. The group association determines local parameters that apply to the session, including the local AS, the local IP address, the MP-BGP families, the import and export policies, and so on.
The no form of this command removes a prefix entry.
Parameters
- ip-prefix/ip-prefix-length
-
Specifies a prefix from which to accept dynamic BGP sessions.
Platforms
All
prefix
Syntax
[no] prefix ip-prefix/prefix-length [exact | longer | through length | prefix-length-range length1-length2 | to ip-prefix/prefix-length | address-mask mask-pattern]
Context
[Tree] (config>router>policy-options>prefix-list prefix)
Full Context
configure router policy-options prefix-list prefix
Description
This command creates a prefix entry in the route policy prefix list.
The no form of this command deletes the prefix entry from the prefix list.
Parameters
- ip-prefix/prefix-length
-
Specifies the IP prefix and length for the prefix list entry in dotted decimal notation.
- exact
-
Specifies the prefix list entry only matches the route with the specified ip-prefix and prefix mask (length) values.
- longer
-
Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values equal to or greater than the specified mask.
- through length
-
Specifies the prefix list entry matches any route that matches the specified ip-prefix and has a prefix length between the specified length values inclusive.
- prefix-length-range length1 - length2
-
Specifies a route must match the most significant bits and have a prefix length with the given range. The range is inclusive of start and end values.
- to ip-prefix/prefix-length
-
Specifies a second IP prefix and length used in route policy prefix lists. A route matches prefix1 to prefix2 if it matches prefix1 and prefix2 according to their respective prefix lengths and if the route’s own prefix length is between the prefix lengths of prefix1 and prefix2. It could take many individual 'exact’ match prefix entries to reproduce the same logic.
- mask-pattern
-
Specifies the address mask to use for matching entries to this prefix entry. A route matches a prefix and address mask combination if the bitwise logical AND of this prefix and the mask equals the bitwise logical AND of the route’s address and the same mask and, additionally, the prefix length of the route matches the prefix length of the prefix entry.
Platforms
All
prefix
Syntax
prefix
Context
[Tree] (config>router>segment-routing>srv6>locator prefix)
Full Context
configure router segment-routing segment-routing-v6 locator prefix
Description
Commands in this context configure IPv6 prefix parameters for an SRv6 locator.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
prefix
Syntax
prefix
Context
[Tree] (conf>router>sr>srv6>ms>block prefix)
Full Context
configure router segment-routing segment-routing-v6 micro-segment block prefix
Description
Commands in this context configure IPv6 prefix parameters for an SRv6 micro-segment locator.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
prefix
Syntax
prefix ip-prefix/prefix-length
no prefix
Context
[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-isis prefix)
[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-ospf prefix)
[Tree] (config>oam-pm>session>ip>tunnel>mpls>sr-ospf3 prefix)
Full Context
configure oam-pm session ip tunnel mpls sr-isis prefix
configure oam-pm session ip tunnel mpls sr-ospf prefix
configure oam-pm session ip tunnel mpls sr-ospf3 prefix
Description
This command configures the IP prefix used with the IGP instance to tunnel IP packets for the session tests.
The no form of this command deletes the prefix from the configuration.
Default
no prefix
Parameters
- ip-prefix/prefix-length
-
Specifies an IPv4 or IPv6 address prefix.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
prefix-attributes-tlv
prefix-attributes-tlv
Syntax
[no] prefix-attributes-tlv
Context
[Tree] (config>service>vprn>isis prefix-attributes-tlv)
Full Context
configure service vprn isis prefix-attributes-tlv
Description
This command enables IS-IS Prefix Attributes TLV support to exchange extended IPv4 and IPv6 reachability information. Extended reachability information is required for traffic engineering features using path computation element (PCE) or optimal route reflection.
The no form of this command removes the prefix-attributes-tlv configuration.
Default
no prefix-attributes-tlv
Platforms
All
prefix-attributes-tlv
Syntax
[no] prefix-attributes-tlv
Context
[Tree] (config>router>isis prefix-attributes-tlv)
Full Context
configure router isis prefix-attributes-tlv
Description
This command enables IS-IS Prefix Attributes TLV support to exchange extended IPv4 and IPv6 reachability information. Extended reachability information is required for traffic engineering features using path computation element (PCE) or optimal route reflection.
The no form of this command removes the prefix-attributes-tlv configuration.
Default
no prefix-attributes-tlv
Platforms
All
prefix-delegation
prefix-delegation
Syntax
[no] prefix-delegation
Context
[Tree] (config>service>ies>if>ipv6>dhcp6-server prefix-delegation)
Full Context
configure service ies interface ipv6 dhcp6-server prefix-delegation
Description
This command enables the prefix delegation options for delegating a long-lived prefix from a delegating router to a requesting router, where the delegating router does not require knowledge about the topology of the links in the network to which the prefixes are assigned.
The no form of this command disables prefix-delegation.
Platforms
All
prefix-exclude
prefix-exclude
Syntax
prefix-exclude policy-name [policy-name]
no prefix-exclude
Context
[Tree] (config>router>ldp>aggregate-prefix-match prefix-exclude)
Full Context
configure router ldp aggregate-prefix-match prefix-exclude
Description
This command specifies the policy name containing the prefixes to be excluded from the aggregate prefix match procedures. In this case, LDP will perform an exact match of a specific FEC element prefix as opposed to a longest match of one or more LDP FEC element prefixes, against this prefix when it receives a FEC-label binding or when a change to this prefix occurs in the routing table.
The no form of this command removes all policies from the configuration.
Default
no prefix-exclude
Parameters
- policy-name
-
Specifies the route policy name, up to five. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The specified name(s) must already be defined.
Platforms
All
prefix-exclude
Syntax
[no] prefix-exclude ip-prefix/prefix-length
Context
[Tree] (config>filter>match-list>ip-pfx-list prefix-exclude)
Full Context
configure filter match-list ip-prefix-list prefix-exclude
Description
This command excludes IPv4 prefix(es) from an ip-prefix-list. The prefix-exclude command is mutually exclusive with apply-path.
The no form of this command deletes the specified excluded prefixes from the ip-prefix-list.
Parameters
- ip-prefix
-
Specifies a valid IPv4 address prefix in dotted decimal notation.
- prefix-length
-
Specifies the length of the entered IPv4 prefix.
Platforms
All
prefix-exclude
Syntax
[no] prefix ipv6-prefix/prefix-length
Context
[Tree] (config>filter>match-list>ipv6-pfx-list prefix-exclude)
Full Context
configure filter match-list ipv6-prefix-list prefix-exclude
Description
This command excludes IPv6 prefix(es) from an ipv6-prefix-list.The prefix-exclude command is mutually exclusive with apply-path.
The no form of this command deletes the specified excluded prefixes from the ipv6-prefix-list.
Parameters
- ipv6-prefix/prefix-length
-
Specifies an IPv6 address prefix written as hexadecimal numbers separated by colons with host bits set to 0. One string of zeros can be omitted, so 2001:db8::700:0:217A is equivalent to 2001:db8:0:0:0:700:0:217A.
- prefix-length
-
Specifies the length of the entered IPv6 prefix.
Platforms
All
prefix-ipv4
prefix-ipv4
Syntax
prefix-ipv4 {enable | disable}
Context
[Tree] (config>router>ldp>if-params>if>ipv6>fec-type-capability prefix-ipv4)
[Tree] (config>router>ldp>if-params>if>ipv4>fec-type-capability prefix-ipv4)
[Tree] (config>router>ldp>session-params>peer>fec-type-capability prefix-ipv4)
Full Context
configure router ldp interface-parameters interface ipv6 fec-type-capability prefix-ipv4
configure router ldp interface-parameters interface ipv4 fec-type-capability prefix-ipv4
configure router ldp session-parameters peer fec-type-capability prefix-ipv4
Description
This command enables or disables IPv4 prefix FEC capability on the session or interface.
The config>router>ldp>if-params>if>ipv6>fec-type-capability>prefix-ipv4 command is not supported on the 7450 ESS.
Platforms
All
prefix-ipv6
prefix-ipv6
Syntax
prefix-ipv6 {enable | disable}
Context
[Tree] (config>router>ldp>if-params>if>ipv6>fec-type-capability prefix-ipv6)
[Tree] (config>router>ldp>if-params>if>ipv4>fec-type-capability prefix-ipv6)
[Tree] (config>router>ldp>session-params>peer>fec-type-capability prefix-ipv6)
Full Context
configure router ldp interface-parameters interface ipv6 fec-type-capability prefix-ipv6
configure router ldp interface-parameters interface ipv4 fec-type-capability prefix-ipv6
configure router ldp session-parameters peer fec-type-capability prefix-ipv6
Description
This command enables or disables IPv6 prefix FEC capability on the session or interface.
This command is not supported on the 7450 ESS.
Platforms
All
prefix-limit
prefix-limit
Syntax
prefix-limit family limit [threshold percentage] [idle-timeout {minutes | forever} | log-only | hold-excess percentage] [post-import]
no prefix-limit family
Context
[Tree] (config>service>vprn>bgp>group>neighbor prefix-limit)
[Tree] (config>service>vprn>bgp>group prefix-limit)
Full Context
configure service vprn bgp group neighbor prefix-limit
configure service vprn bgp group prefix-limit
Description
This command configures the maximum number of BGP routes received from a peer before administrative action is taken. The administrative action can include generating a log or taking the session down. If a session is taken down, configure the idle-timeout parameter to bring it back up automatically after a specific duration. Alternatively, it can be configured to stay down indefinitely, until the user performs a reset.
No prefix limits for any address family are configured by default.
This command allows the user to apply a separate limit to each address family. A set of address family limits can be applied to one neighbor or to all neighbors in a group.
The no form of this command removes the prefix-limit.
Parameters
- threshold percentage
-
Specifies the threshold value (as a percentage) that triggers a warning message to be sent.
- family
-
Specifies the address family to which the limit applies.
- limit
-
Specifies the number of routes that can be learned from a peer expressed as a decimal integer.
- idle-timeout minutes
-
Specifies the duration in minutes before automatically re-establishing a session.
- idle-timeout forever
-
Specifies that the session is re-established only after the clear router bgp command is executed.
- log-only
-
Enables the warning message to be sent at the specified threshold percentage, and also when the limit is reached. However, the BGP session is not taken down.
- post-import
-
Specifies that the limit should be applied only to the number of routes that are accepted by import policies.
- hold-excess percentage
- Specifies the percentage of maximum routes that are allowed to be installed in the route table. If a peer within scope of the configuration exceeds the limit, the overflow routes are held in the BGP RIB as inactive routes and are ineligible for forwarding or advertisement to other peers. If the post-import parameter is configured, only routes not rejected by import policies count toward the limit. A BGP route in the overflow state is reconsidered for activation and reinstallation when an UPDATE message is received for the route. This parameter is mutually exclusive with the idle-timeout and log-only parameters.
Platforms
All
prefix-limit
Syntax
prefix-limit limit [log-only] [threshold percent] [overload-timeout { seconds | forever}]
no prefix-limit
Context
[Tree] (config>service>vprn>isis prefix-limit)
Full Context
configure service vprn isis prefix-limit
Description
This command configures the maximum number of prefixes that IS-IS can learn, and use to protect the system from a router that has accidentally advertised a large number of prefixes. If the number of prefixes reaches the configured percentage of this limit, an SNMP trap is sent. If the limit is exceeded, IS-IS will go into overload.
The overload-timeout option controls the length of time that IS-IS is in the overload state when the prefix limit is reached. The system automatically attempts to restart IS-IS at the end of this duration. If the overload-timeout forever option is used, IS-IS is not restarted automatically and stays in overload until the condition is manually cleared by the administrator. This is also the default behavior when the overload-timeout option is not configured.
The no form of this command removes the prefix-limit.
Default
prefix-limit overload-timeout forever
Parameters
- limit
-
Specifies the number of prefixes that can be learned, expressed as a decimal integer.
- log-only
-
Enables a warning message to be sent at the specified threshold percentage and also when the limit is exceeded. However, overload is not set when this parameter is configured.
- percent
-
Specifies the threshold value (as a percentage) that triggers a warning message to be sent.
- overload-timeout
-
Keyword used to control the length of time that IS-IS is in the overload state when the prefix limit is reached.
- seconds
-
Specifies the time in minutes before IS-IS is restarted.
- forever
-
Specifies that IS-IS should be restarted only after the execution of the clear router isis overload prefix-limit command.
Platforms
All
prefix-limit
Syntax
prefix-limit family limit [threshold percentage] [idle-timeout {minutes | forever} | log-only | hold-excess percentage] [post-import]
no prefix-limit family
Context
[Tree] (config>router>bgp>group>neighbor prefix-limit)
[Tree] (config>router>bgp>group prefix-limit)
Full Context
configure router bgp group neighbor prefix-limit
configure router bgp group prefix-limit
Description
This command configures the maximum number of BGP routes received from a peer before administrative action is taken. The administrative action can include generating a log or taking the session down. If a session is taken down, configure the idle-timeout parameter to bring it back up automatically after a specific duration. Alternatively, it can be configured to stay down indefinitely, until the user performs a reset.
No prefix limits for any address family are configured by default.
This command allows the user to apply a separate limit to each address family. A set of address family limits can be applied to one neighbor or to all neighbors in a group.
The no form of this command removes the prefix-limit.
Parameters
- log-only
-
Enables the warning message to be sent at the specified threshold percentage, and also when the limit is reached. However, the BGP session is not taken down.
- threshold percentage
-
Specifies the threshold value (as a percentage) that triggers a warning message to be sent.
- family
-
Specifies the address family to which the limit applies.
- limit
-
Specifies the number of routes that can be learned from a peer expressed as a decimal integer.
- idle-timeout minutes
-
Specifies the duration in minutes before automatically re-establishing a session.
- idle-timeout forever
-
Specifies that the session is re-established only after the clear router bgp command is executed.
- post-import
-
Specifies that the limit applies only to the number of routes that are accepted by import policies.
- hold-excess percentage
- Specifies the percentage of maximum routes that are allowed to be installed in the route table. If a peer within scope of the configuration exceeds the limit, the overflow routes are held in the BGP RIB as inactive routes and are ineligible for forwarding or advertisement to other peers. If the post-import parameter is configured, only routes not rejected by import policies count toward the limit. A BGP route in the overflow state is reconsidered for activation and reinstallation when an UPDATE message is received for the route. This parameter is mutually exclusive with the idle-timeout and log-only parameters.
Platforms
All
prefix-limit
Syntax
prefix-limit limit [log-only] [threshold percent] [overload-timeout { seconds | forever}]
no prefix-limit
Context
[Tree] (config>router>isis prefix-limit)
Full Context
configure router isis prefix-limit
Description
This command configures the maximum number of prefixes that IS-IS can learn, and use to protect the system from a router that has accidentally advertised a large number of prefixes. If the number of prefixes reaches the configured percentage of this limit, an SNMP trap is sent. If the limit is exceeded, IS-IS will go into overload.
The overload-timeout option controls the length of time that IS-IS is in the overload state when the prefix-limit is reached. The system automatically attempts to restart IS-IS at the end of this duration. If the overload-timeout forever option is used, IS-IS is not restarted automatically and stays in overload until the condition is manually cleared by the administrator. This is also the default behavior when the overload-timeout option is not configured.
The no form of this command removes the prefix-limit.
Default
no prefix-limit
Parameters
- log-only
-
Enables a warning message to be sent at the specified threshold percentage and also when the limit is exceeded. However, overload is not set when this parameter is configured.
- limit
-
Specifies the number of prefixes that can be learned expressed as a decimal integer.
- percent
-
Specifies the threshold value (as a percentage) that triggers a warning message to be sent.
- seconds
-
Specifies the time in minutes before IS-IS is restarted.
- forever
-
Specifies that IS-IS should be restarted only after the execution of the clear router isis overload prefix-limit command.
Platforms
All
prefix-limits
prefix-limits
Syntax
prefix-limits family limit [threshold percentage] [idle-timeout minutes] [log-only] [post-import]
no prefix-limits family
Context
[Tree] (config>subscr-mgmt>bgp-prng-plcy prefix-limits)
Full Context
configure subscriber-mgmt bgp-peering-policy prefix-limits
Description
This command configures the maximum number of BGP routes per address family that can be received from an ESM dynamic BGP peer before an administrative action is taken. Administrative actions include the generation of a log event and taking down the session. If a session is taken down, it can be brought back up automatically after an idle-timeout period. With no idle timeout configured, the session stays down until the user performs a reset.
The no form of this command removes the prefix limits for the specified family.
Default
prefix-limits threshold 90
Parameters
- family
-
Specifies the IP address family for prefix limits.
- limit
-
Specifies the prefix limit.
- percentage
-
Specifies the percentage at which a warning log message is sent.
- minutes
-
Specifies the time, in minutes, before a BGP peer is automatically reestablished on reaching the prefix limit.
- log-only
-
Keyword used to specify if the maximum limit is reached, only a log event is generated. This parameterdoes not disable the BGP session upon reaching the prefix limit.
- post-import
-
Keyword used to specify that limits are only applied to the number of routes accepted by the import policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
prefix-list
prefix-list
Syntax
prefix-list prefix-list-name [{all | none | any}] [router-instance router-instance-name]
no prefix-list [prefix-list-name] [{all | none | any}] [router-instance router-instance-name]
Context
[Tree] (config>service>vprn>static-route-entry>indirect prefix-list)
[Tree] (config>service>vprn>static-route-entry>next-hop prefix-list)
[Tree] (config>service>vprn>static-route-entry>black-hole prefix-list)
Full Context
configure service vprn static-route-entry indirect prefix-list
configure service vprn static-route-entry next-hop prefix-list
configure service vprn static-route-entry black-hole prefix-list
Description
This command associates a constraint to the associated static route such that the static route is only active if any, none, or all of the routes in the prefix list are present and active in the route table.
If the conditional static route is configured in a VPRN and the router-instance-name is configured as “Base”, the activation of the static route is dependent on the existence of routes in the Base router; the prefix-list and flag are evaluated in this context.
No router instance is specified by default, and the conditional static route is dependent on the existence of routes in the same router instance as the static route itself, subject to the details of the prefix list and the flag setting.
Entries in a referenced prefix list that are not match type ‘exact’ are interpreted as though they are ‘exact’.
The no form of this command disables these constraints on the static route.
Default
no prefix-list
Parameters
- prefix-list-name
-
Specifies the name of a currently configured prefix list.
- all
-
Specifies that the static route condition is met if all prefixes in the prefix list are present in the active static route.
- none
-
Specifies that the static route condition is met if none of the prefixes in the named prefix-list are present in the active static route.
- any
-
Specifies that the static route condition is met if any prefixes in the prefix list are present in the active static route.
- router-instance-name
-
Specifies the name of the router instance. Must be "Base".
Platforms
All
prefix-list
Syntax
prefix-list prefix-list-name [{all | none}]
no prefix-list [prefix-list-name] [{all | none}]
Context
[Tree] (config>router>static-route-entry>black-hole prefix-list)
[Tree] (config>router>static-route-entry>next-hop prefix-list)
[Tree] (config>router>static-route-entry>indirect prefix-list)
Full Context
configure router static-route-entry black-hole prefix-list
configure router static-route-entry next-hop prefix-list
configure router static-route-entry indirect prefix-list
Description
This command associates a new constraint to the associated static route such that the static route is only active if none or all of the routes in the prefix list are present and active in the route-table.
Default
no prefix-list
Parameters
- prefix-list-name
-
Specifies the name of a currently configured prefix-list.
- all
-
Specifies that the static route condition is met if all prefixes in the prefix-list must be present in the active route-table.
- none
-
Specifies that the static route condition is met if none of the prefixes in the named prefix-list can be present in the active route-table.
Platforms
All
prefix-list
Syntax
[no] prefix-list name
Context
[Tree] (config>router>policy-options prefix-list)
Full Context
configure router policy-options prefix-list
Description
This command creates a context to configure a prefix list to use in route policy entries.
The no form of this command deletes the named prefix list.
Parameters
- name
-
Specifies the prefix list name. Allowed values are any string up to 64 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), 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@".
An empty prefix list can be configured for pre-provisioning. This empty prefix list will not find a match when referred to by a policy. When removing member prefixes from a prefix list, the prefix list will not be automatically removed when the last member is removed. If required, an empty prefix list must be explicitly removed using the no form of this command.
Platforms
All
prefix-list
Syntax
prefix-list name [name]
no prefix-list
Context
[Tree] (config>router>policy-options>policy-statement>entry>to prefix-list)
[Tree] (config>router>policy-options>policy-statement>entry>from prefix-list)
Full Context
configure router policy-options policy-statement entry to prefix-list
configure router policy-options policy-statement entry from prefix-list
Description
This command configures a prefix list as a match criterion for a route policy statement entry.
If no prefix list is specified, any network prefix is considered a match.
An empty prefix list will evaluate as if 'no match' was found.
The prefix lists specify the network prefix (this includes the prefix and length) a specific policy entry applies.
A maximum of 28 prefix names can be specified.
The no form of this command removes the prefix list match criterion.
Default
no prefix-list
Parameters
- name
-
Specifies the prefix list name. Allowed values are any string up to 64 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), 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
prefix-list-override
prefix-list-override
Syntax
no prefix-list-override
prefix-list-override name {exact | longer}
prefix-list-override name prefix-length-range length1-length2
prefix-list-override name through length
Context
[Tree] (config>router>policy-options>policy-statement>entry>from prefix-list-override)
Full Context
configure router policy-options policy-statement entry from prefix-list-override
Description
This command converts a prefix list to a specific match type. The routing policy uses the converted list as a match condition.
The prefix list to be converted can be specified by its name, as an expression containing the name of a global variable that holds the name of the prefix list, or as an expression containing the name of a subroutine variable that holds the name of the prefix list.
Parameters
- name
-
Specifies the prefix list to be converted, up to 64 characters.
- exact
-
Keyword to convert all entries in the specified prefix list to the exact match type.
- longer
-
Keyword to convert all entries in the specified prefix list to the longer match type.
- length1-length2
-
Specifies the start and end length of the prefix range.
- length
-
Specifies the through length of the prefix.
Platforms
All
prefix-map
prefix-map
Syntax
prefix-map ip-prefix/length subscriber-type nat-sub-type nat-policy nat-policy-name [create]
prefix-map ip-prefix/length subscriber-type nat-sub-type
no prefix-map ip-prefix/length subscriber-type nat-sub-type
Context
[Tree] (config>service>vprn>nat>inside>deterministic prefix-map)
[Tree] (config>router>nat>inside>deterministic prefix-map)
Full Context
configure service vprn nat inside deterministic prefix-map
configure router nat inside deterministic prefix-map
Description
This command is applicable to deterministic NAT and static 1:1 NAT. It is used to configure source IP prefixes on the inside and their association with outside deterministic NAT pools via the NAT policy. Hosts within the source IP prefix are deterministically mapped to outside IP addresses and port ranges in the associated deterministic NAT pool.
Multiple source IP prefixes within an inside routing instance can be defined and they can reference different NAT policies (and therefore, outside deterministic NAT pools and routing instances). Source IP prefixes from multiple routing instances can share the same deterministic NAT pool.
With this command, multiple NAT policies based on a destination prefix or filter criteria can be used together with deterministic NAT.
Non-deterministic NAT can be used simultaneously with deterministic NAT within the same inside routing instance. However, they cannot share the same NAT pool.
Source IP prefixes can be added or removed as long as the associated deterministic NAT pool is in a no shutdown mode.
Removing a prefix or modifying the map statement under it requires that the source IP prefix be in a shutdown mode.
Parameters
- ip-prefix/length
-
Specifies source IP prefix on the inside whose hosts is deterministically mapped to an outside IP address and port block in the corresponding deterministic NAT pool.
- nat-sub-type
-
Specifies the subscriber type.
- nat-policy-name
-
Specifies a NAT policy, up to 32 characters, that points to an outside pool and outside routing instance.
- create
-
Keyword used to create the particular prefix instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
prefix-options
prefix-options
Syntax
[no] prefix-options
Context
[Tree] (config>subscr-mgmt>rtr-adv-plcy prefix-options)
[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv prefix-options)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6 prefix-options)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv prefix-options)
[Tree] (config>service>ies>sub-if>ipv6>rtr-adv prefix-options)
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv prefix-options)
[Tree] (config>service>ies>sub-if>grp-if>ipv6 prefix-options)
Full Context
configure subscriber-mgmt router-advertisement-policy prefix-options
configure service vprn subscriber-interface ipv6 router-advertisements prefix-options
configure service vprn subscriber-interface group-interface ipv6 prefix-options
configure service ies subscriber-interface group-interface ipv6 router-advertisements prefix-options
configure service ies subscriber-interface ipv6 router-advertisements prefix-options
configure service vprn subscriber-interface group-interface ipv6 router-advertisements prefix-options
configure service ies subscriber-interface group-interface ipv6 prefix-options
Description
This command configures Router Advertisement parameters for IPv6 prefixes returned via RADIUS Framed-IPv6-Prefix. All prefixes will inherit these configuration parameters.
The no form of this command unconfigures the Router Advertisement parameters for IPv6 prefixes returned via RADIUS Framed-IPv6-Prefix.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
prefix-policy
prefix-policy
Syntax
prefix-policy prefix-policy [prefix-policy]
no prefix-policy
Context
[Tree] (config>service>vprn>isis>loopfree-alternates>exclude prefix-policy)
Full Context
configure service vprn isis loopfree-alternates exclude prefix-policy
Description
This command specifies the name of the policy for the prefixes to exclude from the LFA SPF calculation in this ISIS instance.
The no form of this command deletes the exclude prefix policy.
Default
no prefix-policy
Parameters
- prefix-policy prefix-policy
-
Specifies the name of the prefix policy, up to 32 characters. Up to five prefix policies can be specified. The specified name must have been already defined.
Platforms
All
prefix-policy
Syntax
[no] prefix-policy prefix-policy [prefix-policy]
Context
[Tree] (config>service>vprn>ospf>loopfree-alternates>exclude prefix-policy)
[Tree] (config>service>vprn>ospf3>loopfree-alternates>exclude prefix-policy)
Full Context
configure service vprn ospf loopfree-alternates exclude prefix-policy
configure service vprn ospf3 loopfree-alternates exclude prefix-policy
Description
This command specifies the name of the policy for the prefixes to exclude from the LFA SPF calculation in this OSPF or OSPF3 instance.
The no form of this command deletes the exclude prefix policy.
Default
no prefix-policy
Parameters
- prefix-policy prefix-policy
-
Specifies the name of the prefix policy, up to 32 characters. Up to five prefix policies can be specified. The specified name must have been already defined.
Platforms
All
prefix-policy
Syntax
prefix-policy prefix-policy [prefix-policy]
no prefix-policy
Context
[Tree] (config>router>isis>loopfree-alternates>exclude prefix-policy)
Full Context
configure router isis loopfree-alternates exclude prefix-policy
Description
This command excludes from LFA SPF calculation prefixes that match a prefix entry or a tag entry in a prefix policy.
The implementation already allows the user to exclude an interface in IS-IS or OSPF, an OSPF area, or an IS-IS level from the LFA SPF.
If a prefix is excluded from LFA, then it will not be included in LFA calculation regardless of its priority. The prefix tag will, however, be used in the main SPF.
This command specifies the name of the policy for the prefixes to exclude from the LFA SPF calculation in this IS-IS instance.
Prefix tags are defined for the IS-IS protocol but not for the OSPF protocol.
The default action, when not explicitly specified by the user in the prefix policy, is a "reject". Thus, regardless if the user did or did not explicitly add the statement "default-action reject" to the prefix policy, a prefix that did not match any entry in the policy will be accepted into LFA SPF.
The no form of this command deletes the exclude prefix policy.
Default
no prefix-policy
Parameters
- prefix-policy prefix-policy
-
Specifies the name of the prefix policy, up to 32 characters. Up to five prefix policies can be specified. The specified name must have been already defined.
Platforms
All
prefix-policy
Syntax
prefix-policy prefix-policy [prefix-policy]
no prefix-policy
Context
[Tree] (config>router>ospf3>loopfree-alternates>exclude prefix-policy)
[Tree] (config>router>ospf>loopfree-alternates>exclude prefix-policy)
Full Context
configure router ospf3 loopfree-alternates exclude prefix-policy
configure router ospf loopfree-alternates exclude prefix-policy
Description
This command excludes from LFA SPF calculation prefixes that match a prefix entry or a tag entry in a prefix policy.
The implementation already allows the user to exclude an interface in IS-IS or OSPF, an OSPF area, or an IS-IS level from the LFA SPF.
If a prefix is excluded from LFA, then it will not be included in LFA calculation regardless of its priority. The prefix tag will, however, be used in the main SPF.
This command specifies the name of the policy for the prefixes to exclude from the LFA SPF calculation in this OSPF or OSPF3 instance.
Prefix tags are defined for the IS-IS protocol but not for the OSPF protocol.
The default action, when not explicitly specified by the user in the prefix policy, is a "reject”. Thus, regardless if the user did or did not explicitly add the statement "default-action reject” to the prefix policy, a prefix that did not match any entry in the policy will be accepted into LFA SPF.
The no form of this command deletes the exclude prefix policy.
Default
no prefix-policy
Parameters
- prefix-policy
-
Specifies the name of the prefix policy, up to 32 characters. Up to five prefix policies can be specified. The specified name must have been already defined.
Platforms
All
prefix-sid-range
prefix-sid-range
Syntax
prefix-sid-range global
prefix-sid-range start-label start-label max-index max-index
no prefix-sid-range
Context
[Tree] (config>router>bgp>segment-routing prefix-sid-range)
Full Context
configure router bgp segment-routing prefix-sid-range
Description
This command configures the label block that BGP segment routing is allowed to use.
The start-label and max-index parameters specify that BGP should be restricted to a subrange of the SRGB, with the subrange starting at start-label and ending at max-index.
It is not possible to enable segment routing (perform a no shutdown) unless the prefix-sid-range is configured using the global keyword or using the start-label and max-index parameters.
The no form of the command allocates no labels for BGP segment-routing.
Default
no prefix-sid-range
Parameters
- global
-
Specifies that BGP is allowed to allocate labels from the entire space of the SRGB, as defined under config>router>mpls-labels>sr-labels.
- start-label
-
Specifies the first label value that is available to BGP in a contiguous range of labels.
- max-index
-
Specifies the last label value that is available to BGP in a contiguous range of labels.
Platforms
All
prefix-sid-range
Syntax
prefix-sid-range {global | start-label label-value max-index index-value}
no prefix-sid-range
Context
[Tree] (config>router>isis>segment-routing prefix-sid-range)
Full Context
configure router isis segment-routing prefix-sid-range
Description
This command configures the prefix SID index range and offset label value for a given IGP instance.
The key parameter is the configuration of the prefix SID index range and the offset label value which this IGP instance will use. Since each prefix SID represents a network global IP address, the SID index for a prefix must be network-wide unique. Thus, all routers in the network are expected to configure and advertise the same prefix SID index range for a given IGP instance. However, the label value used by each router to represent this prefix; that is, the label programmed in the ILM can be local to that router by the use of an offset label, referred to as a start label:
Local Label (Prefix SID) = start-label + {SID index}
The label operation in the network becomes thus very similar to LDP when operating in the independent label distribution mode (RFC 5036, LDP Specification) with the difference that the label value used to forward a packet to each downstream router is computed by the upstream router based on advertised prefix SID index using the above formula.
There are two mutually exclusive modes of operation for the prefix SID range on the router. In the global mode of operation, the user configures the global value and this IGP instance will assume the start label value is the lowest label value in the SRGB and the prefix SID index range size equal to the range size of the SRGB. Once one IGP instance selected the global option for the prefix SID range, all IGP instances on the system will be restricted to do the same. The user must shutdown the segment routing context and delete the prefix-sid-range command in all IGP instances in order to change the SRGB. Once the SRGB is changed, the user must re-enter the prefix-sid-range command again. The SRGB range change will be failed if an already allocated SID index/label goes out of range.
In the per-instance mode of operation, the user partitions the SRGB into non-overlapping sub-ranges among the IGP instances. The user thus configures a subset of the SRGB by specifying the start label value and the prefix SID index range size. All resulting net label values (start-label + index} must be within the SRGB or the configuration will be failed. Furthermore, the code checks for overlaps of the resulting net label value range across IGP instances and will strictly enforce that these ranges do not overlap. The user must shutdown the segment routing context of an IGP instance in order to change the SID index/label range of that IGP instance using the prefix-sid-range command. In addition, any range change will be failed if an already allocated SID index/label goes out of range. The user can however change the SRGB on the fly as long as it does not reduce the current per IGP instance SID index/label range defined with the prefix-sid-range. Otherwise, the user must shutdown the segment routing context of the IGP instance and delete and re-configure the prefix-sid-range command.
Default
no prefix-sid-range
Parameters
- label-value
-
Specifies the label offset for the SR label range of this IGP instance.
- index-value
-
Specifies the maximum value of the prefix SID index range for this IGP instance.
Platforms
All
prefix-sid-range
Syntax
prefix-sid-range global
prefix-sid-range start-label label-value max-index index-value
no prefix-sid-range
Context
[Tree] (config>router>ospf3>segm-rtng prefix-sid-range)
[Tree] (config>router>ospf>segm-rtng prefix-sid-range)
Full Context
configure router ospf3 segment-routing prefix-sid-range
configure router ospf segment-routing prefix-sid-range
Description
This command configures the prefix SID index range and offset label value for an IGP instance.
The key parameter is the configuration of the prefix SID index range and the offset label value that this IGP instance will use. Because each prefix SID represents a network global IP address, the SID index for a prefix must be unique network-wide. Therefore, all routers in the network are expected to configure and advertise the same prefix SID index range for an IGP instance. However, the label value used by each router to represent this prefix, that is, the label programmed in the ILM, can be local to that router by the use of an offset label, referred to as a start label:
Local Label (Prefix SID) = start-label + {SID index}
The label operation in the network is very similar to LDP when operating in independent label distribution mode (RFC 5036, LDP Specification), with the difference being that the label value used to forward a packet to each downstream router is computed by the upstream router based on the advertised prefix SID index using the above formula.
There are two mutually exclusive modes of operation for the prefix SID range on the router. In the global mode of operation, the user configures the global value and this IGP instance will assume the start label value is the lowest label value in the SRGB and the prefix SID index range size equal to the range size of the SRGB. After one IGP instance selected the global option for the prefix SID range, all IGP instances on the system will be restricted to do the same. The user must shutdown the segment routing context and delete the prefix-sid-range command in all IGP instances in order to change the SRGB. After the SRGB is changed, the user must re-enter the prefix-sid-range command again. The SRGB range change will be failed if an already allocated SID index/label goes out of range.
In per-instance mode, the user partitions the SRGB into non-overlapping sub-ranges among the IGP instances. The user configures a subset of the SRGB by specifying the start label value and the prefix SID index range size. All resulting net label values (start-label + index) must be within the SRGB or the configuration will fail. The 7750 SR checks for overlaps of the resulting net label value range across IGP instances and will strictly enforce no overlapping of these ranges. The user must shut down the segment routing context of an IGP instance in order to change the SID index/label range of that IGP instance using the prefix-sid-range command. A range change will fail if an already allocated SID index/label goes out of range. The user can change the SRGB without shutting down the segment routing context as long as it does not reduce the current per-IGP instance SID index/label range defined with the prefix-sid-range command. Otherwise, shut down the segment routing context of the IGP instance, and disable and re-enable the prefix-sid-range command.
Default
no prefix-sid-range
Parameters
- label-value
-
Specifies the label offset for the SR label range of this IGP instance.
- index-value
-
Specifies the maximum value of the prefix SID index range for this IGP.
Platforms
All
prefix-sids
prefix-sids
Syntax
prefix-sids ip-int-name
no prefix-sids ip-int-name
Context
[Tree] (config>router>segment-routing>sr-mpls prefix-sids)
Full Context
configure router segment-routing sr-mpls prefix-sids
Description
This command configures the prefix SIDs for an interface.
The no form of this command removes the prefix SIDs list instance.
Default
no prefix-sids
Parameters
- ip-int-name
-
Specifies the loopback or system interface name that owns the prefix to be advertised, up to 32 characters.
Platforms
All
prefix-unreachable
prefix-unreachable
Syntax
prefix-unreachable
Context
[Tree] (config>router>isis prefix-unreachable)
Full Context
configure router isis prefix-unreachable
Description
Commands in this context configure the prefix-unreachable context.
Platforms
All
preserve-key
preserve-key
Syntax
[no] preserve-key
Context
[Tree] (config>system>security>ssh preserve-key)
Full Context
configure system security ssh preserve-key
Description
After enabling this command, private keys, public keys, and host key file are saved by the server. It is restored following a system reboot or the ssh server restart.
The no form of this command specifies that the keys are held in memory by an SSH server and is not restored following a system reboot.
Default
no preserve-key
Platforms
All
primary
primary
Syntax
primary
Context
[Tree] (config>aaa>radius-scr-plcy primary)
Full Context
configure aaa radius-script-policy primary
Description
Commands in this context configure a primary script.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
primary
Syntax
primary
Context
[Tree] (config>subscr-mgmt>sub-ident-pol primary)
Full Context
configure subscriber-mgmt sub-ident-policy primary
Description
Commands in this context configure primary identification script parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
primary
Syntax
primary path-name
no primary
Context
[Tree] (config>router>mpls>lsp primary)
Full Context
configure router mpls lsp primary
Description
This command specifies a preferred path for the LSP. This command is optional only if the secondary path-name is included in the LSP definition. Only one primary path can be defined for an LSP.
Some of the attributes of the LSP such as the bandwidth, and hop-limit can be optionally specified as the attributes of the primary path. The attributes specified in the primary path path-name command, override the LSP attributes.
The no form of this command deletes the association of this path-name from the LSP lsp-name. All configurations specific to this primary path, such as record, bandwidth, and hop limit, are deleted. The primary path must be shutdown first in order to delete it. The no primary command will not result in any action except a warning message on the console indicating that the primary path is administratively up.
Parameters
- path-name
-
Specifies the case-sensitive alphanumeric name label for the LSP path up to 64 characters in length.
Platforms
All
primary
Syntax
[no] primary [mda-id | esa-vm-id]
Context
[Tree] (config>isa>aa-grp primary)
Full Context
configure isa application-assurance-group primary
Description
This command assigns an AA ISA or ESA-VM configured in the specified location to this application assurance group. Primary and backup ISAs have equal operational status and when both ISAs are coming up, the one that becomes operational first becomes the active ISA.
On an activity switch from the primary ISA, all configurations are already on the backup ISA but flow state information must be re-learned. Any statistics not yet spooled will be lost. Auto-switching from the backup to primary, once the primary becomes available again, is not supported.
Operator is notified through SNMP events when:
-
When AA service goes down (all ISAs in the group are down) or comes back up (an ISA in the group becomes active)
-
When AA redundancy fails (one of the ISAs in the group is down) or recovers (the failed MDA comes back up)
-
When an AA activity switch occurred.
The no form of this command removes the specified ISA from the application assurance group.
Parameters
- mda-id
-
Specifies the slot/mda or esa/vm, identifying a provisioned AA ISA.
- esa-vm-id
-
Specifies the ESA and VM, identifying a provisioned ESA-VM. The value of the esa-vm-id for application assurance is used as the esa-id plus 128. For example, an ESA 1 with VM2 would be referred to as esa-129/2.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
primary
Syntax
primary mda-id
no primary
Context
[Tree] (config>isa>tunnel-grp primary)
Full Context
configure isa tunnel-group primary
Description
This command assigns an ISA IPsec module configured in the specified slot to this IPsec group. The backup ISA IPsec provides the IPsec group with warm redundancy when the primary ISA IPsec in the group is configured. Primary and backup ISA IPsec have equal operational status and when both MDAs are coming up, the one that becomes operational first becomes the active ISA IPsec.
All configuration information is pushed down to the backup MDA from the CPM once the CPM gets notice that the primary module has gone down. This allows multiple IPsec groups to use the same backup module. Any statistics not yet spooled will be lost. Auto-switching from the backup to primary, once the primary becomes available again, is supported.
The operator is notified through SNMP events when:
-
When the ISA IPsec service goes down (all modules in the group are down) or comes back up (a module in the group becomes active).
-
When ISA IPsec redundancy fails (one of the modules in the group is down) or recovers (the failed module comes back up).
-
When an ISA IPsec activity switch took place.
The no form of this command removes the specified primary ID from the group’s configuration.
Default
no primary
Parameters
- mda-id
-
Specifies the card/slot identifying a provisioned IPsec ISA.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
primary
Syntax
primary primary secondary secondary
Context
[Tree] (config>service>vprn>if>sap>ipsec-tun>dyn>cert>status-verify primary)
[Tree] (config>router>if>ipsec>ipsec-tun>dyn>cert>status-verify primary)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn>cert>status-verify primary)
[Tree] (config>ipsec>trans-mode-prof>dyn>cert>status-verify primary)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn>cert>status-verify primary)
[Tree] (config>service>ies>if>sap>ipsec-gw>cert>status-verify primary)
[Tree] (config>service>vprn>if>sap>ipsec-gw>cert>status-verify primary)
Full Context
configure service vprn interface sap ipsec-tunnel dynamic-keying cert status-verify primary
configure router interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
configure ipsec ipsec-transport-mode-profile dynamic-keying cert primary
configure service ies interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
configure service ies interface sap ipsec-gw cert status-verify primary
configure service vprn interface sap ipsec-gw cert status-verify primary
Description
This command specifies the primary and secondary CVS methods used to verify the revocation status of the peer’s certificate.
OCSP or CRL uses the corresponding configuration in the CA profile of the issuer of the certificate in question.
Default
primary crl
Parameters
- primary
-
Specifies the primary CSV method used to verify the revocation status of the peer’s certificate.
- secondary
-
Specifies the secondary CSV method used to verify the revocation status of the peer’s certificate.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel dynamic-keying cert status-verify primary
- configure service ies interface sap ipsec-gw cert status-verify primary
- configure service vprn interface sap ipsec-gw cert status-verify primary
- configure ipsec ipsec-transport-mode-profile dynamic-keying cert primary
VSR
- configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
- configure router interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
- configure service ies interface ipsec ipsec-tunnel dynamic-keying cert status-verify primary
primary
Syntax
[no] primary mda-id
Context
[Tree] (config>isa>video-group primary)
Full Context
configure isa video-group primary
Description
This command configures the primary video group ISA. Only one primary can be configured per video group when ad insertion is enabled. The maximum number of primaries per video-group for FCC and RD is 4.
Parameters
- mda-id
-
Specifies the slot and MDA number for the primary video group ISA.
Platforms
7450 ESS, 7750 SR, 7750 SR-s
primary-cf
primary-cf
Syntax
primary-cf cflash-id
Context
[Tree] (config>call-trace primary-cf)
Full Context
configure call-trace primary-cf
Description
This command specifies which compact-flash is used as the primary CF for call-trace operation.
Default
primary-cf cf1
Parameters
- cflash-id
-
Specifies the compact flash card to be used as the primary local storage location to save the generated call trace log files.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
primary-config
primary-config
Syntax
primary-config file-url
no primary-config
Context
[Tree] (bof primary-config)
Full Context
bof primary-config
Description
This command specifies the name and location of the primary configuration file.
The system attempts to use the configuration specified in primary-config. If the specified file cannot be located, the system automatically attempts to obtain the configuration from the location specified in secondary-config and then the tertiary-config.
If an error in the configuration file is encountered, the boot process aborts.
The no form of this command removes the primary-config configuration.
Parameters
- file-url
-
Specifies the primary configuration file location, expressed as a file URL.
Platforms
All
primary-dns
primary-dns
Syntax
primary-dns ip-address
no primary-dns
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>dhcp primary-dns)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>dhcp primary-dns)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp primary-dns
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp primary-dns
Description
This command configures the primary DNS address to be returned via DHCP on WLAN-GW ISA.
The no form of this command reverts to the default.
Parameters
- ip-address
-
Specifies the primary DNS address.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
primary-dns
Syntax
primary-dns ip-address
no primary-dns
Context
[Tree] (config>service>vprn>dns primary-dns)
Full Context
configure service vprn dns primary-dns
Description
This command configures the primary DNS server used for DNS name resolution. DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.
The no form of this command removes the primary DNS server from the configuration.
Default
no primary-dns — No primary DNS server is configured.
Parameters
- ip-address
-
The IP or IPv6 address of the primary DNS server.
Platforms
All
primary-dns
Syntax
primary-dns ip-address
no primary-dns [ip-address]
Context
[Tree] (bof primary-dns)
Full Context
bof primary-dns
Description
This command configures the primary DNS server used for DNS name resolution. DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.
The no form of this command removes the primary DNS server from the configuration.
Default
no primary-dns
Parameters
- ip-address
-
Specifies the IP or IPv6 address of the primary DNS server.
Platforms
All
primary-image
primary-image
Syntax
primary-image file-url
no primary image
Context
[Tree] (bof primary-image)
Full Context
bof primary-image
Description
This command specifies the primary directory location for runtime image file loading.
The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.
All runtime image files (*.tim files) must be located in the same directory.
The no form of this command removes the primary-image configuration.
Parameters
- file-url
-
Specifies the file-url can be either local (this CPM) or a remote FTP server.
Platforms
All
primary-ip-address
primary-ip-address
Syntax
primary-ip-address ipv4-address
no primary-ip-address
Context
[Tree] (config>router>bgp>orr>location primary-ip-address)
Full Context
configure router bgp optimal-route-reflection location primary-ip-address
Description
This command specifies the primary IP address of a reference location used for BGP optimal route reflection. Up to three IPv4 addresses and three IPv6 addresses can be specified per location.
If the TE DB is unable find a node in its topology database that matches a primary address of the location, then it tries to find a node matching a secondary address. If this attempt also fails, the TE DB tries to find a node matching a tertiary address.
The IP addresses specified for a location should be topologically "close” to a set of clients that should all receive the same optimal path for that location.
The no form of this command removes the primary IP address information.
Default
no primary-ip-address
Parameters
- ipv4-address
-
Specifies the primary IPv4 address of a location expressed in dotted decimal notation.
Platforms
All
primary-ipv6-address
primary-ipv6-address
Syntax
primary-ipv6-address ipv6-address
no primary-ipv6-address
Context
[Tree] (config>router>bgp>orr>location primary-ipv6-address)
Full Context
configure router bgp optimal-route-reflection location primary-ipv6-address
Description
This command specifies the primary IPv6 address of a reference location used for BGP optimal route reflection. Up to three IPv4 addresses and three IPv6 addresses can be specified per location.
If the TE DB is unable find a node in its topology database that matches a primary address of the location, then it tries to find a node matching a secondary address. If this attempt also fails, the TE DB tries to find a node matching a tertiary address.
The IP addresses specified for a location should be topologically "close” to a set of clients that should all receive the same optimal path for that location.
The no form of this command removes the primary IPv6 address information.
Default
no primary-ipv6-address
Parameters
- ipv6-address
-
Specifies the primary IPv6 address of a location expressed in dotted decimal notation.
Platforms
All
primary-location
primary-location
Syntax
primary-location file-url
no primary-location
Context
[Tree] (config>system>software-repository primary-location)
Full Context
configure system software-repository primary-location
Description
This command configures the primary location for the files in the software repository. See the software-repository command description for more information.
The no form of the command removes the primary location.
Parameters
- file-url
-
Specifies the primary location to be used to access the files in the software repository.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
primary-nbns
primary-nbns
Syntax
primary-nbns ip-address
no primary-nbns
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>dhcp primary-nbns)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>dhcp primary-nbns)
Full Context
configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp primary-nbns
configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp primary-nbns
Description
This command configures the primary NBNS address to be returned via DHCP on WLAN-GW ISA.
The no form of this command reverts to the default.
Parameters
- ip-address
-
Specifies the primary NBNS address.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
primary-next-hop
primary-next-hop
Syntax
[no] primary-next-hop
Context
[Tree] (config>router>mpls>fwd-policies>fwd-policy>nh-grp primary-next-hop)
Full Context
configure router mpls forwarding-policies forwarding-policy next-hop-group primary-next-hop
Description
Commands in this context configure the primary next hop of an NHG entry in a forwarding policy.
The no form of this command removes the primary next-hop context from an NHG entry in a forwarding policy.
Platforms
All
primary-p2mp-instance
primary-p2mp-instance
Syntax
[no] primary-p2mp-instance instance-name
Context
[Tree] (config>router>mpls>lsp primary-p2mp-instance)
Full Context
configure router mpls lsp primary-p2mp-instance
Description
This command creates the primary instance of a P2MP LSP. The primary instance of a P2MP LSP is modeled as a set of root-to-leaf (S2L) sub-LSPs. The root, for example a head-end node triggers signaling using one path message per S2L path. The leaf sub-LSP paths are merged at branching points.
This command is not supported on the 7450 ESS.
Parameters
- instance-name
-
Specifies a name that identifies the P2MP LSP instance. The instance name can be up to 32 characters long and must be unique.
Platforms
All
primary-path
primary-path
Syntax
primary-path
Context
[Tree] (config>mcast-mgmt>bw-plcy>t2-paths primary-path)
Full Context
configure mcast-management bandwidth-policy t2-paths primary-path
Description
Commands in this context configure primary path parameters.
Platforms
7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR
primary-ports
primary-ports
Syntax
primary-ports
Context
[Tree] (config>service>vpls>mac-move primary-ports)
[Tree] (config>service>template>vpls-template>mac-move primary-ports)
Full Context
configure service vpls mac-move primary-ports
configure service template vpls-template mac-move primary-ports
Description
Commands in this context define primary VPLS ports. VPLS ports that were declared as secondary prior to the execution of this command will be moved from secondary port-level to primary port-level. Changing a port to the tertiary level can only be done by first removing it from the secondary port-level.
Platforms
All
primary-tunnel-interface
primary-tunnel-interface
Syntax
primary-tunnel-interface ldp-p2mp p2mp-identifier sender ip-address
primary-tunnel-interface rsvp-p2mp lsp-name sender ip-address
no primary-tunnel-interface
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override primary-tunnel-interface)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel primary-tunnel-interface)
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle primary-tunnel-interface)
Full Context
configure mcast-management multicast-info-policy bundle channel source-override primary-tunnel-interface
configure mcast-management multicast-info-policy bundle channel primary-tunnel-interface
configure mcast-management multicast-info-policy bundle primary-tunnel-interface
Description
This command allows the user to define a bundle in the multicast-info-policy and specify channels in the bundle that must be received from the primary tunnel interface associated with an RSVP P2MP LSP. The multicast info policy is applied to the base router instance.
The egress LER can accept multicast packets via two different methods. The regular RPF check on unlabeled IP multicast packets, which is based on routing table lookup. The static assignment which specifies the receiving of a multicast group <*,G> or a specific <S,G> from a primary tunnel-interface associated with an RSVP P2MP LSP.
One or more primary tunnel interfaces in the base router instance can be configured. That is, the user can specify to receive different multicast groups, <*,G> or specific <S,G>, from different P2MP LSPs. This assumes that there are static joins configured for the same multicast groups at the ingress LER to forward over a tunnel interface associated with the same P2MP LSP.
At any given time, packets of the same multicast group can be accepted from either the primary tunnel interface associated with a P2MP LSP or from a PIM interface. These are mutually exclusive options. As soon as a multicast group is configured against a primary tunnel interface in the multicast info policy, it is blocked from other PIM interfaces.
A multicast packet received on a tunnel interface associated with a P2MP LSP can be forwarded over a PIM or IGMP interface which can be an IES interface, a spoke SDP terminated IES interface, or a network interface.
The no form of this command removes the static RPF check.
Parameters
- lsp-name
-
Species a string of up to 32 characters identifying the LSP name as configured at the ingress LER.
- ip-address
-
Specifies a string of 15 characters representing the IP address of the ingress LER for the LSP.
- p2mp-id
-
Identifier used for signaling mLDP P2MP LSP (applies only to the 7750 SR).
Platforms
All
primary-url
primary-url
Syntax
primary-url url
no primary-url
Context
[Tree] (config>python>py-script primary-url)
Full Context
configure python python-script primary-url
Description
This command specifies the location of the primary Python script. The system supports three locations for each Python script. Users can store the script file on either a local CF card or an FTP server.
The no form of this command removes the URL.
Parameters
- url
-
Specifies the primary URL of the Python script up to 180 characters, either a local CF card url or a FTP server URL.
Platforms
All
prio-code-point
prio-code-point
Syntax
prio-code-point priority-code-point
no prio-code-point
Context
[Tree] (config>test-oam>build-packet>header>dot1q prio-code-point)
Full Context
configure test-oam build-packet header dot1q prio-code-point
Description
This command defines the priority code point to be used in the test Dot1Q header.
The no form of this command removes the priority code point value.
Default
prio-code-point 0 (BE)
Parameters
- priority-code-point
-
Specifies the priority code point to be used in the test Dot1Q header.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
prio-code-point
Syntax
prio-code-point priority-code-point
no prio-code-point
Context
[Tree] (debug>oam>build-packet>packet>field-override>header>dot1q prio-code-point)
Full Context
debug oam build-packet packet field-override header dot1q prio-code-point
Description
This command configures a Priority Code Point (PCP) for an IEEE 802.1Q packet header to be launched by the OAM find-egress tool.
The no form of this command removes the priority code point value.
Default
no override
Parameters
- priority-code-point
-
Specifies the priority code point to be used in the test Dot1Q header.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
priority
Syntax
priority level
Context
[Tree] (config>subscr-mgmt>sub-prof>egress>policer-control-policy>priority-mbs-thresholds priority)
[Tree] (config>subscr-mgmt>sub-prof>ingress>policer-control-policy>priority-mbs-thresholds priority)
Full Context
configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds priority
configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds priority
Description
The priority level command contains the mbs-contribution configuration command for a given strict priority level. Eight levels are supported numbered 1 through 8 with 8 being the highest strict priority.
Each of the eight priority CLI nodes always exists and do not need to be created. While parameters exist for each priority level, the parameters are only applied when the priority level within a parent policer instance is currently supporting child policers.
Parameters
- level
-
Specifies the priority level override.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority priority source {python | diameter-gx | ludb | radius | diameter-nasreq | gtp | dhcp | local-address-assignment}
no priority priority
Context
[Tree] (config>subscr-mgmt>auth-orig priority)
Full Context
configure subscriber-mgmt authentication-origin priority
Description
This command allows the relative order of authentication priorities to be swapped between RADIUS and LUDB by configuring the RADIUS source priority to value 3. By moving RADIUS to the third position, LUDB, and all the origins below LUDB, are pushed down.The active order of priorities can be displayed in the output of the show subscriber-mgmt authentication-origin command.
The no form of this command deletes the priority value. To restore defaults, the priority configuration must be deleted.
Parameters
- priority
-
Specifies the authentication origin priority override.
- source
-
Specifies the source of authentication priority. Only radius can be configured. RADIUS as the authentication origin can be assigned priority 3 which places it above LUDB.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>vprn>sub-if>grp-if>srrp priority)
[Tree] (config>service>ies>sub-if>grp-if>srrp priority)
Full Context
configure service vprn subscriber-interface group-interface srrp priority
configure service ies subscriber-interface group-interface srrp priority
Description
This command overrides the default base priority for the SRRP instance. The SRRP instance priority is advertised by the SRRP instance to its neighbor router and is compared to the priority received from the neighbor router. The router with the best (highest) priority enters the master state while the other router enters the backup state. If the priority of each router is the same, the router with the lowest source IP address in the SRRP advertisement message assumes the master state.
The base priority of an SRRP instance can be managed by VRRP policies. A VRRP policy defines a set of connectivity or verification tests which, when they fail, may lower an SRRP instances base priority (creating an in-use priority for the instance). Every time an SRRP instances in-use priority changes when in master state, it sends an SRRP advertisement message with the new priority. If the dynamic priority drops to zero or receives an SRRP Advertisement message with a better priority, the SRRP instance transitions to the becoming backup state.
When the priority command is not specified, or the no priority command is executed, the system uses a default base priority of 100. The priority command may be executed at any time.
The no form of this command restores the default base priority to the SRRP instance. If a VRRP policy is associated with the SRRP instance, it will use the default base priority as the basis for any modifications to the SRRP instances in-use priority.
Default
priority 100
Parameters
- priority
-
Specifies a base priority for the SRRP instance to override the default.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
[no] priority level
Context
[Tree] (config>card>fp>ingress>network>queue-group>policer-control-override>priority-mbs-thresholds priority)
[Tree] (config>card>fp>ingress>access>queue-group>policer-control-override>priority-mbs-thresholds priority)
Full Context
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds priority
configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds priority
Description
The priority level command contains the mbs-contribution configuration command for a given strict priority level. Eight levels are supported numbered 1 through 8 with 8 being the highest strict priority.
Each of the eight priority CLI nodes always exists and do not need to be created. While parameters exist for each priority level, the parameters are only applied when the priority level within a parent policer instance is currently supporting child policers.
Parameters
- level
-
Specifies the priority level.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority
Syntax
priority priority-value
no priority
Context
[Tree] (config>port>ethernet>eth-cfm>mep>ais-enable priority)
[Tree] (config>lag>eth-cfm>mep>ais-enable priority)
Full Context
configure port ethernet eth-cfm mep ais-enable priority
configure lag eth-cfm mep ais-enable priority
Description
This command specifies the priority of the AIS messages generated by the node.
The no form of the command reverts to the default values.
Parameters
- priority-value
-
Specifies the priority value of the AIS messages originated by the node.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>lag>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure port ethernet eth-cfm mep grace eth-ed priority
configure eth-tunnel path eth-cfm mep grace eth-ed priority
configure eth-ring path eth-cfm mep grace eth-ed priority
configure lag eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
[no] priority level
Context
[Tree] (config>service>epipe>sap>egress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>epipe>sap>ingress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>ipipe>sap>egress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>cpipe>sap>ingress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>ipipe>sap>ingress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>cpipe>sap>egress>policy-ctrl-over>mbs-thrshlds priority)
Full Context
configure service epipe sap egress policer-control-override priority-mbs-thresholds priority
configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority
configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority
configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority
configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority
configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority
Description
The priority-level level override CLI node contains the specified priority level’s mbs-contribution override value.
This node does not need to be created and will not be output in show or save configurations unless an mbs-contribution override exist for level.
Parameters
- level
-
The level parameter is required when specifying priority-level and identifies which of the parent policer instances priority level’s the mbs-contribution is overriding.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service epipe sap ingress policer-control-override priority-mbs-thresholds priority
- configure service epipe sap egress policer-control-override priority-mbs-thresholds priority
- configure service ipipe sap ingress policer-control-override priority-mbs-thresholds priority
- configure service ipipe sap egress policer-control-override priority-mbs-thresholds priority
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress policer-control-override priority-mbs-thresholds priority
- configure service cpipe sap ingress policer-control-override priority-mbs-thresholds priority
priority
Syntax
priority priority-value
no priority
Context
[Tree] (config>service>epipe>sap>eth-cfm>mep priority)
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>aid-enable priority)
Full Context
configure service epipe sap eth-cfm mep priority
configure service epipe spoke-sdp eth-cfm aid-enable priority
Description
This command specifies the priority of AIS messages originated by the node.
Parameters
- priority-value
-
Specifies the priority value of the AIS messages originated by the node.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure service epipe spoke-sdp eth-cfm mep grace eth-ed priority
configure service epipe sap eth-cfm mep grace eth-ed priority
configure service ipipe sap eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority stp-priority
no priority [stp-priority]
Context
[Tree] (config>service>template>vpls-template>stp priority)
[Tree] (config>service>template>vpls-sap-template>stp priority)
[Tree] (config>service>vpls>stp priority)
Full Context
configure service template vpls-template stp priority
configure service template vpls-sap-template stp priority
configure service vpls stp priority
Description
The bridge-priority command is used to populate the priority portion of the bridge ID field within outbound BPDUs (the most significant 4 bits of the bridge ID). It is also used as part of the decision process when determining the best BPDU between messages received and sent. All values are truncated to multiples of 4096, conforming with IEEE 802.1t and 802.1D-2004.
The no form of this command returns the bridge priority to the default value.
Default
priority 4096
Parameters
- bridge-priority
-
Specifies the bridge priority for the STP instance
Platforms
All
priority
Syntax
priority stp-priority
no priority
Context
[Tree] (config>service>vpls>sap>stp priority)
[Tree] (config>service>vpls>spoke-sdp priority)
[Tree] (config>service>vpls>spoke-sdp>stp priority)
Full Context
configure service vpls sap stp priority
configure service vpls spoke-sdp priority
configure service vpls spoke-sdp stp priority
Description
This command configures the Nokia Spanning Tree Protocol (STP) priority for the SAP or spoke SDP.
STP priority is a configurable parameter associated with a SAP or spoke SDP. When configuration BPDUs are received, the priority is used in some circumstances as a tie breaking mechanism to determine whether the SAP or spoke SDP be designated or blocked.
In traditional STP implementations (802.1D-1998), this field is called the port priority and has a value of 0 to 255. This field is coupled with the port number (0 to 255 also) to create a 16 bit value. In the latest STP standard (802.1D-2004) only the upper 4 bits of the port priority field are used to encode the SAP or spoke SDP priority. The remaining 4 bits are used to extend the port ID field into a 12 bit virtual port number field. The virtual port number uniquely references a SAP or spoke SDP within the STP instance.
STP computes the actual priority by taking the input value and masking out the lower four bits. The result is the value that is stored in the SDP priority parameter. For instance, if a value of 0 is entered, masking out the lower 4 bits results in a parameter value of 0. If a value of 255 is entered, the result is 240.
The no form of this command returns the STP priority to the default value.
Default
priority 128
Parameters
- stp-priority
-
Specifies the STP priority value for the SAP or spoke SDP. 0 is the highest priority. The actual value used for STP priority (and stored in the configuration) is the result of masking out the lower 4 bits, therefore the actual value range is 0 to 240 in increments of 16.
Platforms
All
priority
Syntax
priority priority-value
no priority
Context
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>ais-enable priority)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable priority)
Full Context
configure service vpls spoke-sdp eth-cfm mep ais-enable priority
configure service vpls mesh-sdp eth-cfm mep ais-enable priority
Description
This command specifies the priority of AIS messages originated by the node.
Parameters
- priority-value
-
Specifies the priority value of the AIS messages originated by the node
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure service vpls sap eth-cfm mep grace eth-ed priority
configure service vpls eth-cfm mep grace eth-ed priority
configure service vpls mesh-sdp eth-cfm mep grace eth-ed priority
configure service vpls spoke-sdp eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
[no] priority level
Context
[Tree] (config>service>vpls>sap>egress>policy-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>vpls>sap>ingress>policy-ctrl-over>mbs-thrshlds priority)
Full Context
configure service vpls sap egress policer-control-override priority-mbs-thresholds priority
configure service vpls sap ingress policer-control-override priority-mbs-thresholds priority
Description
The priority-level level override CLI node contains the specified priority level’s mbs-contribution override value.
This node does not need to be created and will not be output in show or save configurations unless an mbs-contribution override exist for level.
The no form of this command sets the MBS contribution for the associated priority to its default value.
Parameters
- level
-
Specifies that the level parameter is required when specifying priority-level and identifies which of the parent policer instances priority level’s the mbs-contribution is overriding
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority
Syntax
priority base-priority
no priority
Context
[Tree] (config>service>ies>if>ipv6>vrrp priority)
Full Context
configure service ies interface ipv6 vrrp priority
Description
This command provides the ability to configure a specific priority value to the virtual router instance. In conjunction with an optional policy command, the base-priority is used to derive the in-use priority of the virtual router instance.
This command is only available in the non-owner vrrp virtual-router-id nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed. For non-owner virtual router instances, if the priority command is not executed, the base-priority will be set to 100.
The no form of this command restores the default value of 100 to base-priority.
Default
priority 100
Parameters
- base-priority
-
The base-priority parameter configures the base priority used by the virtual router instance. If a VRRP Priority Control policy is not also defined, the base-priority will be the in-use priority for the virtual router instance.
Platforms
All
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed priority
configure service ies interface sap eth-cfm mep grace eth-ed priority
configure service ies interface spoke-sdp eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed priority
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service ies interface spoke-sdp eth-cfm mep grace eth-ed priority
- configure service ies interface sap eth-cfm mep grace eth-ed priority
priority
Syntax
[no] priority level
Context
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over>mbs-thrshlds priority)
Full Context
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds priority
configure service ies interface sap egress policer-control-override priority-mbs-thresholds priority
Description
The priority-level level override CLI node contains the specified priority level’s mbs-contribution override value.
This node does not need to be created and will not be output in show or save configurations unless an mbs-contribution override exist for level.
The no form of this command sets the MBS contribution for the associated priority to its default value.
Parameters
- level
-
Specifies that the level parameter is required when specifying priority-level and identifies which of the parent policer instances priority level’s the mbs-contribution is overriding.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority
Syntax
priority base-priority
no priority
Context
[Tree] (config>service>ies>if>vrrp priority)
Full Context
configure service ies interface vrrp priority
Description
The priority command provides the ability to configure a specific priority value to the virtual router instance. In conjunction with an optional policy command, the base-priority is used to derive the in-use priority of the virtual router instance.
The priority command is only available in the non-owner vrrp virtual-router-id nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed. For non-owner virtual router instances, if the priority command is not executed, the base-priority will be set to 100.
The no form of this command restores the default value of 100 to base-priority.
Parameters
- base-priority
-
The base-priority parameter configures the base priority used by the virtual router instance. If a VRRP Priority Control policy is not also defined, the base-priority will be the in-use priority for the virtual router instance.
Platforms
All
priority
Syntax
priority {low | high}
no priority [{low | high}]
Context
[Tree] (config>service>vprn>static-route-entry>indirect>forwarding-class priority)
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel>forwarding-class priority)
[Tree] (config>service>vprn>static-route-entry>next-hop>forwarding-class priority)
Full Context
configure service vprn static-route-entry indirect forwarding-class priority
configure service vprn static-route-entry ipsec-tunnel forwarding-class priority
configure service vprn static-route-entry next-hop forwarding-class priority
Description
This optional command associates an enqueuing priority with the static route. The options are either high or low, with low being the default. This parameter has the ability to affect the likelihood that a packet will be enqueued at SAP ingress in the face of ingress congestion.
Once a packet is enqueued into an ingress buffer, the significance of this parameter is lost.
Default
priority low
Parameters
- low
-
Setting the enqueuing parameter for a packet to low decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
- high
-
Setting the enqueuing parameter for a packet to high increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-ed priority)
[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed priority
configure service vprn interface sap eth-cfm mep grace eth-ed priority
configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service vprn interface sap eth-cfm mep grace eth-ed priority
- configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed priority
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed priority
priority
Syntax
[no] priority level
Context
[Tree] (config>service>vprn>if>sap>egress>policer-ctrl-over>mbs-thrshlds priority)
[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over>mbs-thrshlds priority)
Full Context
configure service vprn interface sap egress policer-control-override priority-mbs-thresholds priority
configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds priority
Description
The priority-level level override CLI node contains the specified priority level’s mbs-contribution override value.
This node does not need to be created and will not be output in show or save configurations unless an mbs-contribution override exist for level.
The no form of this command sets the MBS contribution for the associated priority to its default value.
Parameters
- level
-
Specifies that the level parameter is required when specifying priority-level and identifies which of the parent policer instances priority level’s the mbs-contribution is overriding.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>vprn>if>vrrp priority)
[Tree] (config>service>vprn>if>ipv6>vrrp priority)
Full Context
configure service vprn interface vrrp priority
configure service vprn interface ipv6 vrrp priority
Description
The priority command provides the ability to configure a specific priority value to the virtual router instance. In conjunction with an optional policy command, the base-priority is used to derive the in-use priority of the virtual router instance.
The priority command is only available in the non-owner vrrp virtual-router-id nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed. For non-owner virtual router instances, if the priority command is not executed, the base-priority will be set to 100.
The no form of this command restores the default value of 100 to base-priority.
Parameters
- base-priority
-
The base-priority parameter configures the base priority used by the virtual router instance. If a VRRP priority control policy is not also defined, the base-priority will be the in-use priority for the virtual router instance.
Platforms
All
priority
Syntax
priority number
no priority
Context
[Tree] (config>service>vprn>isis>if>level priority)
Full Context
configure service vprn isis interface level priority
Description
This command configures the priority of the IS-IS router interface for designated router election on a multi-access network.
This priority is included in hello PDUs transmitted by the interface on a multi-access network. The router with the highest priority is the preferred designated router. The designated router is responsible for sending LSPs with regard to this network and the routers that are attached to it.
The no form of this command reverts to the default value.
Default
priority 64
Parameters
- number
-
Specifies the priority for this interface at this level.
Platforms
All
priority
Syntax
priority number
no priority
Context
[Tree] (config>service>vprn>ospf>area>if priority)
[Tree] (config>service>vprn>ospf3>area>if priority)
Full Context
configure service vprn ospf area interface priority
configure service vprn ospf3 area interface priority
Description
This command configures the priority of the OSPF interface that is used to elect the designated router (DR) on the subnet.
This parameter is only used if the interface is of type broadcast. The router with the highest priority interface becomes the DR. A router with priority 0 is not eligible to be the designated router or backup designated router.
The no form of this command resets the interface priority to the default value.
Default
priority 1
Parameters
- number
-
The interface priority expressed as a decimal integer. A value of 0 indicates the router is not eligible to be the Designated Router of Backup Designated Router on the interface subnet.
Platforms
All
priority
Syntax
priority dr-priority
no priority
Context
[Tree] (config>service>vprn>pim>if priority)
Full Context
configure service vprn pim interface priority
Description
This command sets the priority value to become the rendezvous point (RP) that is included in bootstrap messages sent by the router. The RP is sometimes called the bootstrap router. The priority command indicates whether the router is eligible to be a bootstrap router.
The no form of this command disqualifies the router to participate in the bootstrap election.
Default
priority 1 (The router is the least likely to become the designated router.)
Parameters
- dr-priority
-
Specifies the priority to become the designated router. The higher the value, the higher the priority.
Platforms
All
priority
Syntax
priority bootstrap-priority
Context
[Tree] (config>service>vprn>pim>rp>ipv6>bsr-candidate priority)
[Tree] (config>service>vprn>pim>rp>bsr-candidate priority)
Full Context
configure service vprn pim rp ipv6 bsr-candidate priority
configure service vprn pim rp bsr-candidate priority
Description
This command defines the priority used to become the rendezvous point (RP). The higher the priority value the more likely that this router becomes the RP. If there is a tie, the router with the highest IP address is elected.
Parameters
- bootstrap-priority
-
The priority to become the bootstrap router.
Platforms
All
priority
Syntax
priority priority
no priority
Context
[Tree] (config>service>vprn>pim>rp>rp-candidate priority)
Full Context
configure service vprn pim rp rp-candidate priority
Description
This command defines the priority used to become the rendezvous point (RP). The higher the priority value, the more likely that this router will become the RP.
Use the no form of this command to revert to the default value.
Default
priority 192
Parameters
- priority
-
Specifies the priority to become the designated router. The higher the value the more likely the router will become the RP.
Platforms
All
priority
Syntax
priority priority-level
no priority
Context
[Tree] (config>router>ldp>lsp-bfd priority)
Full Context
configure router ldp lsp-bfd priority
Description
This command configures a priority value that is used to order prefix list processing if multiple prefix lists are configured.
The no form of this command restores the default priority value.
Default
priority 1
Parameters
- priority-level
-
Specifies the priority value of the prefix list.
Platforms
All
priority
Syntax
priority setup-priority hold-priority
no priority
Context
[Tree] (config>router>mpls>lsp>primary priority)
[Tree] (config>router>mpls>lsp>secondary priority)
[Tree] (config>router>mpls>lsp-template priority)
Full Context
configure router mpls lsp primary priority
configure router mpls lsp secondary priority
configure router mpls lsp-template priority
Description
This command enables the soft preemption procedures for this LSP path. The operator enables the soft preemption mechanism on a specific LSP name by explicitly configuring the setup and holding priorities for the primary path at the head-end node. The operator can similarly configure priority values for a secondary path for this LSP name. Different values could be used for the primary and for any of the secondary paths. In the absence of explicit user configuration, the setup priority is internally set to the default value of 7 and the holding priority is set to the default value of 0.
Valid user-entered values for these two parameters require that the holding priority be numerically lower than or equal to the setup priority, otherwise preemption loops can occur.
Preemption is effected when a router preempting node processes a new RSVP session reservation and there is not enough available bandwidth on the RSVP interface, or the Class Type (CT) when Diff-Serv is enabled, to satisfy the bandwidth in the FlowSpec object while there exist other session reservations for LSP paths with a strictly lower holding priority (numerically higher holding priority value) than the setup priority of the new LSP reservation. If enough available bandwidth is freed on the link or CT to accommodate the new reservation by preempting one or more lower priority LSP paths, the preempting node allows temporary overbooking of the RSVP interface and honors the new reservation.
The preempting node will immediately set the 'Preemption pending’ flag (0x10) in the IPv4 Sub-Object in the RRO object in the Resv refresh for each of the preempted LSP paths. The IPv4 Sub-Object corresponds to the outgoing interface being used by the preempting and preempted LSP paths; however, the bandwidth value in the FlowSpec object is not changed. The Resv flag must also be set if the preempting node is a merge point for the primary LSP path and the backup bypass LSP or detour LSP and the backup LSP is activated.
When evaluating if enough available bandwidth will be freed, the preempting node considers the reservations in order from the lowest holding priority (numerically higher holding priority value) to the holding priority just below the setup priority of the new reservation. A new reservation cannot preempt a reservation which has a value of the holding priority equal to the new reservation setup priority.
When Diff-Serv is enabled on the preempting node and the MAM bandwidth allocation model is used, a new reservation can only preempt a reservation in the same Class Type (CT).
LSP paths which were not flagged at the head-end for soft preemption will be hard preempted. LSP paths with the default holding priority of 0 cannot be preempted. LSP paths with zero bandwidth do not preempt other LSP paths regardless of the values of the path setup priority and the path holding priority. They can also not be preempted.
When evaluating if enough available bandwidth will be freed, the preempting node considers the reservations in order from the lowest holding priority (numerically higher holding priority) to the holding priority just below the setup priority of the new reservation. There is no specific order in which the reservations in the same holding priority are considered.
The preempting node starts a preemption timer for each of the preempted LSP paths. While this timer is on, the node should continue to refresh the Path and Resv for the preempted LSP paths. When the preemption timer expires, the node tears down the reservation if the head-end node has not already done so.
A head-end node upon receipt of the Resv refresh message with the 'Preemption pending’ flag must immediately perform a make-before-break on the affected adaptive CSPF LSP. Both IGP metric and TE metric based CSPF LSPs are included. If an alternative path that excludes the flagged interface is not found, then the LSP is put on a retry in a similar way to the Global Revertive procedure at a head-end node. However, the number of retries and the retry timer are governed by the values of the retry-limit and retry-timer parameters: config>router>mpls>lsp>retry-limit; config>router>mpls>lsp>retry-timer.
MPLS will keep the address list of flagged interfaces for a maximum of 60 s (not user-configurable) from the time the first Resv message with the 'Preemption pending’ flag is received. This actually means that MPLS will request CSPF to find a path that excludes the flagged interfaces in the first few retries until success or until 60 s have elapsed. Subsequent retries after the 60 s will not exclude the flagged interfaces as it is assumed IGP has converged by then and the Unreserved Bandwidth sub-TLV for that priority, or TE Class, in the TE database will show the updated value taking into account the preempting LSP path reservation or a value of zero if overbooked.
If the LSP has a configured secondary standby which is operationally UP, the router will switch the path of the LSP to it and then start the MBB. If no standby path is available and a secondary non-standby is configured, the router will start the MBB and signal the path of the secondary. The LSP path will be switched to either the secondary or the new primary, whichever comes up first.
The no form of this command reverts the LSP path priority to the default values and results in setting the setup priority to 7, in setting the hold priority to 0, and in clearing the 'soft preemption desired’ flag in the RRO in the Resv refresh message.
Default
no priority
Parameters
- setup-priority
-
Specifies the priority of the reservation for this session at setup time.
- holding-priority
-
Specifies the priority of the reservation for this session at preemption action.
Platforms
All
priority
Syntax
priority value
no priority
Context
[Tree] (config>app-assure>aarp priority)
Full Context
configure application-assurance aarp priority
Description
This command defines the priority for the AARP instance. The priority value is used to determine the master/backup upon initialization or re-balance.
The no form of this command reverts to the default value.
Default
priority 100
Parameters
- value
-
Specifies an integer that defines the priority of an AARP instance.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority priority-level
no priority
Context
[Tree] (config>app-assure>group>policy>aqp>entry>action>remark priority)
Full Context
configure application-assurance group policy app-qos-policy entry action remark priority
Description
This command configures remark discard priority action on flows matching this AQP entry. When enabled, all packets for all flows matching this AQP entry will be remarked to the configured discard priority.
Default
no priority
Parameters
- priority-level
-
Specifies the priority to apply to a packet.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority priority
no priority
Context
[Tree] (config>redundancy>multi-chassis>peer>mc-ipsec>tunnel-group priority)
Full Context
configure redundancy multi-chassis peer mc-ipsec tunnel-group priority
Description
This command specifies the local priority of the tunnel-group, this is used to elect master, higher number win. If priority are same, then the peer has more active ISA win; and priority and the number of active ISA are same, then the peer with higher IP address win.
The no form of this command removes the priority value from the configuration.
Default
priority 100
Parameters
- priority
-
Specifies the priority of this tunnel-group.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority dr-priority
no priority
Context
[Tree] (config>router>pim>interface priority)
Full Context
configure router pim interface priority
Description
This command sets the priority value to elect the designated router (DR). The DR election priority is a 32-bit unsigned number and the numerically larger priority is always preferred.
The no form of this command reverts to the default value.
Default
priority 1
Parameters
- priority
-
Specifies the priority to become the designated router. The higher the value, the higher the priority.
Platforms
All
priority
Syntax
priority priority
no priority
Context
[Tree] (config>router>pim>rp>ipv6>rp-candidate priority)
[Tree] (config>router>pim>rp>rp-candidate priority)
Full Context
configure router pim rp ipv6 rp-candidate priority
configure router pim rp rp-candidate priority
Description
This command configures the Candidate-RP priority for becoming a rendezvous point (RP). This value is used to elect RP for a group range.
The no form of this command reverts to the default value.
Default
priority 192
Parameters
- priority
-
Specifies the priority to become a rendezvous point (RP). A value of 0 is considered as the highest priority.
Platforms
All
priority
Syntax
priority priority
no priority
Context
[Tree] (config>oam-pm>session>ethernet priority)
Full Context
configure oam-pm session ethernet priority
Description
This command defines the CoS priority across all tests configured under this session. This CoS value is exposed to the various QoS policies the frame passes through and does not necessarily map directly to the CoS value on the wire.
The no form of this command removes changes the priority to the default value.
Default
priority 0
Parameters
- priority
-
Specifies the CoS value.
Platforms
All
priority
Syntax
priority level
Context
[Tree] (config>qos>plcr-ctrl-plcy>root>priority-mbs-thresholds priority)
Full Context
configure qos policer-control-policy root priority-mbs-thresholds priority
Description
The priority level command contains the mbs-contribution configuration command for a given strict priority level. Eight levels are supported numbered 1 through 8 with 8 being the highest strict priority.
Each of the eight priority CLI nodes always exists and do not need to be created. While parameters exist for each priority level, the parameters are only applied when the priority level within a parent policer instance is currently supporting child policers.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority
Syntax
priority [priority]
no priority
Context
[Tree] (config>filter>redirect-policy>dest priority)
Full Context
configure filter redirect-policy destination priority
Description
Redirect policies can contain multiple destinations. Each destination is assigned an initial or base priority which describes its relative importance within the policy.
Default
priority 100
Parameters
- priority
-
Specifies the priority, expressed as a decimal integer, used to weigh the destination’s relative importance within the policy.
Platforms
All
priority
Syntax
priority {low | high}
no priority [{low | high}]
Context
[Tree] (config>router>static-route-entry>next-hop>forwarding-class priority)
[Tree] (config>router>static-route-entry>indirect>forwarding-class priority)
Full Context
configure router static-route-entry next-hop forwarding-class priority
configure router static-route-entry indirect forwarding-class priority
Description
This optional command associates an enqueuing priority with the static route. The options are either high or low, with low being the default. This parameter has the ability to affect the likelihood that a packet will be enqueued at SAP ingress in the face of ingress congestion.
Once a packet is enqueued into an ingress buffer, the significance of this parameter is lost.
Default
priority low
Parameters
- low
-
Setting the enqueuing parameter for a packet to low decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
- high
-
Setting the enqueuing parameter for a packet to high increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>router>if>eth-cfm>mep>grace>eth-ed priority)
Full Context
configure router interface eth-cfm mep grace eth-ed priority
Description
This command sets the priority bits and determines the forwarding class based on the mapping of priority to FC.
The no form of this command disables the local priority configuration and sets the priority to the ccm-ltm-priority associated with this MEP.
Default
no priority
Parameters
- priority
-
Specifies the priority bit.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority
Syntax
priority priority
no priority
Context
[Tree] (config>router>fad>flex-algo priority)
Full Context
configure router flexible-algorithm-definitions flex-algo priority
Description
This command configures the priority of the FAD. This priority is used as a tie-breaker when the router has received multiple FADs for the same flexible algorithm.
Every router that is configured to participate in a particular flexible algorithm uses the same tie-breaker logic to select the winning FAD. This allows for consistent FAD definition selection in cases where routers advertise different definitions for a specific flexible algorithm. The following rules apply to the breaker mechanism.
-
From the advertisements of the FAD in the area (including both locally generated advertisements and received advertisements), select the one with the highest priority value.
-
If there are multiple advertisements of the FAD with the same highest priority, select the one that is originated from the router with either the highest system ID or router ID.
The no form of this command sets the priority to the default value.
Default
priority 100
Parameters
- priority
-
Configures the priority of this FAD.
Platforms
All
priority
Syntax
priority priority
no priority
Context
[Tree] (config>router>if>ipv6>vrrp priority)
[Tree] (config>router>if>vrrp priority)
Full Context
configure router interface ipv6 vrrp priority
configure router interface vrrp priority
Description
This command configures the base router priority for the virtual router instance used in the master election process.
The priority is the most important parameter set on a non-owner virtual router instance. The priority defines a virtual router’s selection order in the master election process. Together, the priority value and the preempt mode allow the virtual router with the best priority to become the master virtual router.
The base-priority is used to derive the in-use priority of the virtual router instance as modified by any optional VRRP priority control policy. VRRP priority control policies can be used to either override or adjust the base priority value depending on events or conditions within the chassis.
The priority command is only available in the non-owner vrrp nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed.
For non-owner virtual router instances, the default base priority value is 100.
The no form of the command reverts to the default value.
Default
priority 100
Parameters
- priority
-
The base priority used by the virtual router instance expressed as a decimal integer. If no VRRP priority control policy is defined, the base-priority is the in-use priority for the virtual router instance.
Platforms
All
priority
Syntax
priority priority-level [{delta | explicit}]
no priority
Context
[Tree] (config>vrrp>policy>priority-event>route-unknown priority)
[Tree] (config>vrrp>policy>priority-event>lag-port-down>number-down priority)
[Tree] (config>vrrp>policy>priority-event>port-down priority)
[Tree] (config>vrrp>policy>priority-event>lag-port-down>weight-down priority)
[Tree] (config>vrrp>policy>priority-event>host-unreachable priority)
Full Context
configure vrrp policy priority-event route-unknown priority
configure vrrp policy priority-event lag-port-down number-down priority
configure vrrp policy priority-event port-down priority
configure vrrp policy priority-event lag-port-down weight-down priority
configure vrrp policy priority-event host-unreachable priority
Description
This command controls the effect the set event has on the virtual router instance in-use priority.
When the event is set, the priority-level is either subtracted from the base priority of each virtual router instance or it defines the explicit in-use priority value of the virtual router instance depending on whether the delta or explicit keywords are specified.
Multiple set events in the same policy have interaction constraints:
-
If any set events have an explicit priority value, all the delta priority values are ignored.
-
The set event with the lowest explicit priority value defines the in-use priority that are used by all virtual router instances associated with the policy.
-
If no set events have an explicit priority value, all the set events delta priority values are added and subtracted from the base priority value defined on each virtual router instance associated with the policy.
-
If the delta priorities sum exceeds the delta-in-use-limit parameter, then the delta-in-use-limit parameter is used as the value subtracted from the base priority value defined on each virtual router instance associated with the policy.
If the priority command is not configured on the priority event, the priority-value defaults to 0 and the qualifier keyword defaults to delta, therefore, there is no impact on the in-use priority.
The no form of the command configures the set event to subtract 0 from the base priority (no effect).
Default
no priority
Parameters
- priority-level
-
The priority level adjustment value expressed as a decimal integer.
- delta
-
Configures what effect the priority-level will have on the base priority value. The default base priority value is delta.
When delta is specified, the priority-level value is subtracted from the associated virtual router instance’s base priority when the event is set and no explicit events are set. The sum of the priority event priority-level values on all set delta priority events are subtracted from the virtual router base priority to derive the virtual router instance in-use priority value. If the delta priority event is cleared, the priority-level is no longer used in the in-use priority calculation.
- explicit
-
Configures what effect the priority-level will have on the base priority value.
When explicit is specified, the priority-level value is used to override the base priority of the virtual router instance if the priority event is set and no other explicit priority event is set with a lower priority-level. The set explicit priority value with the lowest priority-level determines the actual in-use protocol value for all virtual router instances associated with the policy.
Platforms
All
priority
Syntax
priority priority-level explicit
no priority
Context
[Tree] (config>vrrp>policy>priority-event>mc-ipsec-non-forwarding priority)
Full Context
configure vrrp policy priority-event mc-ipsec-non-forwarding priority
Description
This command controls the effect the set event has on the virtual router instance in-use priority.
When the event is set, the priority-level is either subtracted from the base priority of each virtual router instance or it defines the explicit in-use priority value of the virtual router instance depending on whether the delta or explicit keywords are specified.
Multiple set events in the same policy have interaction constraints:
-
If any set events have an explicit priority value, all the delta priority values are ignored.
-
The set event with the lowest explicit priority value defines the in-use priority that are used by all virtual router instances associated with the policy.
-
If no set events have an explicit priority value, all the set events delta priority values are added and subtracted from the base priority value defined on each virtual router instance associated with the policy.
-
If the delta priorities sum exceeds the delta-in-use-limit parameter, then the delta-in-use-limit parameter is used as the value subtracted from the base priority value defined on each virtual router instance associated with the policy.
If the priority command is not configured on the priority event, the priority-value defaults to 0 and the qualifier keyword defaults to delta, therefore, there is no impact on the in-use priority.
The no form of the command configures the set event to subtract 0 from the base priority (no effect).
Default
no priority
Parameters
- priority-level
-
The priority level adjustment value expressed as a decimal integer.
- explicit
-
When explicit is specified, the priority-level value is used to override the base priority of the virtual router instance if the priority event is set and no other explicit priority event is set with a lower priority-level. The set explicit priority value with the lowest priority-level determines the actual in-use protocol value for all virtual router instances associated with the policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority
Syntax
priority bridge-priority
no priority
Context
[Tree] (config>service>pw-template>stp priority)
Full Context
configure service pw-template stp priority
Description
The bridge-priority command is used to populate the priority portion of the bridge ID field within outbound BPDUs (the most significant 4 bits of the bridge ID). It is also used as part of the decision process when determining the best BPDU between messages received and sent. All values will be truncated to multiples of 4096, conforming with IEEE 802.1t and 802.1D-2004.
The no form of this command returns the bridge priority to the default value.
Default
priority 4096
Parameters
- bridge-priority
-
Specifies the bridge priority for the STP instance.
Platforms
All
priority
Syntax
priority number
no priority
Context
[Tree] (config>router>isis>if>level priority)
Full Context
configure router isis interface level priority
Description
This command configures the priority of the IS-IS router interface for designated router election on a multi-access network.
This priority is included in hello PDUs transmitted by the interface on a multi-access network. The router with the highest priority is the preferred designated router. The designated router is responsible for sending LSPs with regard to this network and the routers that are attached to it.
The no form of this command reverts to the default value.
Default
priority 64
Parameters
- number
-
Specifies the priority for this interface at this level.
Platforms
All
priority
Syntax
priority number
no priority
Context
[Tree] (config>router>ospf>area>interface priority)
[Tree] (config>router>ospf3>area>interface priority)
Full Context
configure router ospf area interface priority
configure router ospf3 area interface priority
Description
This command configures the priority of the OSPF interface that is used in an election of the designated router on the subnet.
This parameter is only used if the interface is of type broadcast. The router with the highest priority interface becomes the designated router. A router with priority 0 is not eligible to be Designated Router or Backup Designated Router.
The no form of this command reverts the interface priority to the default value.
Default
priority 1
Parameters
- number
-
Specifies the interface priority expressed as a decimal integer. A value of 0 indicates the router is not eligible to be the Designated Router or Backup Designated Router on the interface subnet.
Platforms
All
priority
Syntax
priority [value]
no priority
Context
[Tree] (config>redundancy>multi-chassis>ipsec-domain priority)
Full Context
configure redundancy multi-chassis ipsec-domain priority
Description
This command configures the priority for the tunnel group in the IPsec domain. The node with the higher priority is more likely to be elected as active within the domain.
The no form of this command reverts to the default value.
Default
priority 100
Parameters
- value
-
Specifies the IPsec domain tunnel group priority.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority-event
priority-event
Syntax
[no] priority-event
Context
[Tree] (config>vrrp>policy priority-event)
Full Context
configure vrrp policy priority-event
Description
This command creates the context to configure VRRP priority control events used to define criteria to modify the VRRP in-use priority.
A priority control event specifies an object to monitor and the effect on the in-use priority level for an associated virtual router instance.
Up to 32 priority control events can be configured within the priority-event node.
The no form of the command clears any configured priority events.
Platforms
All
priority-marking
priority-marking
Syntax
priority-marking dscp dscp-name
priority-marking prec ip-prec-value
no priority-marking
Context
[Tree] (config>service>vprn>gsmp>group>neighbor priority-marking)
[Tree] (config>service>vpls>gsmp>group>neighbor priority-marking)
Full Context
configure service vprn gsmp group neighbor priority-marking
configure service vpls gsmp group neighbor priority-marking
Description
This command configures the type of priority marking to be used.
The no form of this command reverts to the default.
Parameters
- dscp-name
-
Specifies the DSCP code-point to be used.
- ip-prec-value
-
Specifies the precedence value to be used.
Platforms
All
priority-mbs-thresholds
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>subscr-mgmt>sub-prof>ingress>policer-control-policy priority-mbs-thresholds)
[Tree] (config>subscr-mgmt>sub-prof>egress>policer-control-policy priority-mbs-thresholds)
Full Context
configure subscriber-mgmt sub-profile ingress policer-control-policy priority-mbs-thresholds
configure subscriber-mgmt sub-profile egress policer-control-policy priority-mbs-thresholds
Description
The priority-mbs-thresholds command contains the root arbiter parent policer’s min-thresh-separation command and each priority level’s mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority sensitive rate-based discards within the root arbiter’s parent policer.
The priority-mbs-thresholds CLI node always exists and does not need to be created.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>card>fp>ingress>network>queue-group>policer-control-override priority-mbs-thresholds)
[Tree] (config>card>fp>ingress>access>queue-group>policer-control-override priority-mbs-thresholds)
Full Context
configure card fp ingress network queue-group policer-control-override priority-mbs-thresholds
configure card fp ingress access queue-group policer-control-override priority-mbs-thresholds
Description
This command contains the root arbiter parent policer’s min-thresh-separation command and each priority level’s mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority sensitive rate-based discards within the root arbiter’s parent policer.
The priority-mbs-thresholds CLI node always exists and does not need to be created.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>service>cpipe>sap>ingress>policer-control-override priority-mbs-thresholds)
[Tree] (config>service>epipe>sap>ingress>policer-control-override priority-mbs-thresholds)
[Tree] (config>service>ipipe>sap>ingress>policer-control-override priority-mbs-thresholds)
[Tree] (config>service>cpipe>sap>egress>policer-control-override priority-mbs-thresholds)
[Tree] (config>service>ipipe>sap>egress>policer-control-override priority-mbs-thresholds)
[Tree] (config>service>epipe>sap>egress>policer-control-override priority-mbs-thresholds)
Full Context
configure service cpipe sap ingress policer-control-override priority-mbs-thresholds
configure service epipe sap ingress policer-control-override priority-mbs-thresholds
configure service ipipe sap ingress policer-control-override priority-mbs-thresholds
configure service cpipe sap egress policer-control-override priority-mbs-thresholds
configure service ipipe sap egress policer-control-override priority-mbs-thresholds
configure service epipe sap egress policer-control-override priority-mbs-thresholds
Description
This command overrides the CLI node contains the configured min-thresh-separation and the various priority level mbs-contribution override commands.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service cpipe sap egress policer-control-override priority-mbs-thresholds
- configure service cpipe sap ingress policer-control-override priority-mbs-thresholds
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure service epipe sap egress policer-control-override priority-mbs-thresholds
- configure service ipipe sap ingress policer-control-override priority-mbs-thresholds
- configure service epipe sap ingress policer-control-override priority-mbs-thresholds
- configure service ipipe sap egress policer-control-override priority-mbs-thresholds
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>service>vpls>sap>egress>policer-ctrl-over priority-mbs-thresholds)
[Tree] (config>service>vpls>sap>ingress>policer-ctrl-over priority-mbs-thresholds)
Full Context
configure service vpls sap egress policer-control-override priority-mbs-thresholds
configure service vpls sap ingress policer-control-override priority-mbs-thresholds
Description
This command overrides the CLI node contains the configured min-thresh-separation and the various priority level mbs-contribution override commands.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>service>ies>if>sap>ingress>policer-ctrl-over priority-mbs-thresholds)
[Tree] (config>service>ies>if>sap>egress>policer-ctrl-over priority-mbs-thresholds)
Full Context
configure service ies interface sap ingress policer-control-override priority-mbs-thresholds
configure service ies interface sap egress policer-control-override priority-mbs-thresholds
Description
This command overrides the CLI node contains the configured min-thresh-separation and the various priority level mbs-contribution override commands.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>service>vprn>if>sap>ingress>policer-ctrl-over priority-mbs-thresholds)
[Tree] (config>service>vprn>if>sap>egress>policer-ctrl-over priority-mbs-thresholds)
Full Context
configure service vprn interface sap ingress policer-control-override priority-mbs-thresholds
configure service vprn interface sap egress policer-control-override priority-mbs-thresholds
Description
This command overrides the CLI node contains the configured min-thresh-separation and the various priority level mbs-contribution override commands.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority-mbs-thresholds
Syntax
priority-mbs-thresholds
Context
[Tree] (config>qos>plcr-ctrl-plcy>root priority-mbs-thresholds)
Full Context
configure qos policer-control-policy root priority-mbs-thresholds
Description
The priority-mbs-thresholds command contains the root arbiter parent policer’s min-thresh-separation command and each priority level’s mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority-sensitive rate-based discards within the root arbiter’s parent policer.
The priority-mbs-thresholds CLI node always exists and does not need to be created.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
priority-sessions
priority-sessions
Syntax
[no] priority-sessions
Context
[Tree] (config>service>nat>firewall-policy priority-sessions)
[Tree] (config>service>nat>up-nat-policy priority-sessions)
[Tree] (config>service>nat>nat-policy priority-sessions)
Full Context
configure service nat firewall-policy priority-sessions
configure service nat up-nat-policy priority-sessions
configure service nat nat-policy priority-sessions
Description
This command configures the prioritized sessions of this NAT or residential firewall policy.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy priority-sessions
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy priority-sessions
- configure service nat up-nat-policy priority-sessions
priority1
priority1
Syntax
priority1 priority-value
no priority1
Context
[Tree] (config>system>ptp priority1)
Full Context
configure system ptp priority1
Description
This command configures the priority1 value of the local clock. This parameter is only used when the profile is set to ieee1588-2008. This value is used by the Best Master Clock Algorithm to determine which clock should provide timing for the network.
This value is used for the value to advertise in the Announce messages and for the local clock value in data set comparisons.
The no form of the command reverts to the default configuration.
Default
priority1 128
Parameters
- priority-value
-
Specifies the value of the priority1 field.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priority2
priority2
Syntax
priority2 priority-value
no priority2
Context
[Tree] (config>system>ptp priority2)
Full Context
configure system ptp priority2
Description
This command configures the priority2 value of the local clock. This parameter is only used when the profile is set to ieee1588-2008, g8275dot1-2014, or g8275dot2-2016. The parameter is ignored when any other profile is selected.
This value is used by the Best timeTransmitter Clock algorithm to determine which clock should provide timing for the network.
This value is used for the value to advertise in the Announce messages and for local clock value in data set comparisons.
The no form of the command reverts to the default configuration.
Default
priority2 128
Parameters
- priority-value
-
Specifies the value of the priority2 field.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
priv-lvl
priv-lvl
Syntax
priv-lvl priv-lvl user-profile-name
no priv-lvl priv-lvl
Context
[Tree] (config>service>vprn>aaa>rmt-srv>tacplus>priv-lvl-map priv-lvl)
Full Context
configure service vprn aaa remote-servers tacplus priv-lvl-map priv-lvl
Description
This command maps a specific TACACS+ priv-lvl to a locally configured profile for authorization. This mapping is used when the use-priv-lvl option is specified for TACPLUS authorization.
Parameters
- priv-lvl
-
Specifies the privilege level used when sending a TACACS+ ENABLE request.
- user-profile-name
-
Specifies the user profile for this mapping.
Platforms
All
priv-lvl
Syntax
priv-lvl priv-lvl user-profile-name
no priv-lvl priv-lvl
Context
[Tree] (config>system>security>tacplus>priv-lvl-map priv-lvl)
Full Context
configure system security tacplus priv-lvl-map priv-lvl
Description
This command maps a specific TACACS+ priv-lvl to a locally configured profile for authorization. This mapping is used when the use-priv-lvl option is specified for TACPLUS authorization.
Parameters
- priv-lvl
-
Specifies the privilege level used when sending a TACACS+ ENABLE request.
- user-profile-name
-
Specifies the user profile for this mapping.
Platforms
All
priv-lvl-map
priv-lvl-map
Syntax
[no] priv-lvl-map
Context
[Tree] (config>service>vprn>aaa>rmt-srv>tacplus priv-lvl-map)
Full Context
configure service vprn aaa remote-servers tacplus priv-lvl-map
Description
Commands in this context specify a series of mappings between TACACS+ priv-lvl and locally configured profiles for authorization. These mappings are used when the use-priv-lvl option is specified for tacplus authorization.
The no form of this command reverts to the default.
Default
priv-lvl-map
Platforms
All
priv-lvl-map
Syntax
[no] priv-lvl-map
Context
[Tree] (config>system>security>tacplus priv-lvl-map)
Full Context
configure system security tacplus priv-lvl-map
Description
Commands in this context specify a series of mappings between TACACS+ priv-lvl and locally configured profiles for authorization. These mappings are used when the use-priv-lvl option is specified for tacplus authorization.
The no form of this command reverts to the default.
Default
priv-lvl-map
Platforms
All
private-interface
private-interface
Syntax
private-interface ip-int-name
no private-interface
Context
[Tree] (config>ipsec>client-db>client private-interface)
Full Context
configure ipsec client-db client private-interface
Description
This command specifies the private interface name that is used for tunnel setup.
The no form of this command reverts to the default.
Default
no private-interface
Parameters
- ip-int-name
-
Specifies the name of the private interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
private-ki
private-ki
Syntax
private-ki hex-string
no private-ki
Context
[Tree] (config>li>x-interfaces>lics>lic>authentication private-ki)
Full Context
configure li x-interfaces lics lic authentication private-ki
Description
This command configures the private key for the X1 and X2 interfaces.
The no form of this command reverts to the default.
Parameters
- hex-string
-
Specifies the password. Must contain exactly 32 hex nibbles.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
private-retail-subnets
private-retail-subnets
Syntax
[no] private-retail-subnets
Context
[Tree] (config>service>vprn>sub-if private-retail-subnets)
Full Context
configure service vprn subscriber-interface private-retail-subnets
Description
This command controls the export of retail subnets and prefixes to the wholesale forwarding service. When this attribute is configured, subnets and prefixes configured on the retail subscriber interface are no longer exported to the associated wholesale VPRN and remain private to the retail VPRN. This is useful in a IPoE or PPPoE business service context, as it allows retail services to use overlapping IP address spaces even if those services are associated with the same wholesale service. IPoE and PPPoE sessions are actually terminated in the retail service although their traffic transits on a SAP belonging to the wholesale service.
Configuring private retail subnets is not supported for IPv4 static hosts and ARP hosts. If PPPoE sessions need to coexist with IPv4 static hosts or ARP hosts, then this attribute should not be configured on the retail subscriber interface.
This command fails if the subscriber interface is not associated with a wholesale service.
If the retail VPRN is of the type hub, this attribute is mandatory. In this case, private retail subnets are enabled by default and cannot be unconfigured.
The no form of this command disables overlapping IP addresses between different retailers referring to this interface.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
private-service
private-service
Syntax
private-service service-id
private-service name service-name
no private-service
Context
[Tree] (config>ipsec>client-db>client private-service)
Full Context
configure ipsec client-db client private-service
Description
This command specifies the private service ID that is used for tunnel setup.
The no form of this command reverts to the default.
Default
no private-service
Parameters
- service-id
-
Specifies the service ID of the tunnel delivery service.
This variant of this command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The private-service name service-name variant can be used in all configuration modes.
- name service-name
-
Identifies the service, up to 64 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
private-tcp-mss-adjust
private-tcp-mss-adjust
Syntax
private-tcp-mss-adjust octets
private-tcp-mss-adjust default
no private-tcp-mss-adjust
Context
[Tree] (config>service>vprn>l2tp>l2tpv3 private-tcp-mss-adjust)
[Tree] (config>router>l2tp>group>l2tpv3 private-tcp-mss-adjust)
[Tree] (config>service>vprn>l2tp>group>l2tpv3 private-tcp-mss-adjust)
[Tree] (config>router>l2tp>group>tunnel>l2tpv3 private-tcp-mss-adjust)
[Tree] (config>service>vprn>l2tp>group>tunnel>l2tpv3 private-tcp-mss-adjust)
Full Context
configure service vprn l2tp l2tpv3 private-tcp-mss-adjust
configure router l2tp group l2tpv3 private-tcp-mss-adjust
configure service vprn l2tp group l2tpv3 private-tcp-mss-adjust
configure router l2tp group tunnel l2tpv3 private-tcp-mss-adjust
configure service vprn l2tp group tunnel l2tpv3 private-tcp-mss-adjust
Description
This command enables TCP MSS adjust for L2TPv3 tunnels on the private side of the group or tunnel level. When this command is configured, the system updates the TCP MSS option value of the received TCP SYN packet on the private side.
Note that this command can be overridden by the corresponding configuration on the group or tunnel level.
With the default parameter, the system uses the upper-level configuration. With the non-default parameter, the system uses this configuration instead of the upper level configuration.
The no form of this command disables TCP MSS adjust on the private side.
Default
no private-tcp-mss-adjust
Parameters
- octets
-
Specifies the new TCP MSS value in octets.
- default
-
Specifies to use the upper-level configuration
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
private-tcp-mss-adjust
Syntax
private-tcp-mss-adjust bytes
private-tcp-mss-adjust octets
no private-tcp-mss-adjust
Context
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel private-tcp-mss-adjust)
[Tree] (config>service>vprn>if>sap>ip-tunnel private-tcp-mss-adjust)
[Tree] (config>service>vprn>if>sap>ipsec-tun private-tcp-mss-adjust)
[Tree] (config>service>ies>if>sap>ip-tunnel private-tcp-mss-adjust)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel private-tcp-mss-adjust)
[Tree] (config>router>if>ipsec>ipsec-tunnel private-tcp-mss-adjust)
[Tree] (config>ipsec>tnl-temp private-tcp-mss-adjust)
Full Context
configure service vprn interface ipsec ipsec-tunnel private-tcp-mss-adjust
configure service vprn interface sap ip-tunnel private-tcp-mss-adjust
configure service vprn interface sap ipsec-tunnel private-tcp-mss-adjust
configure service ies interface sap ip-tunnel private-tcp-mss-adjust
configure service ies interface ipsec ipsec-tunnel private-tcp-mss-adjust
configure router interface ipsec ipsec-tunnel private-tcp-mss-adjust
configure ipsec tunnel-template private-tcp-mss-adjust
Description
This command enables TCP MSS to adjust for L2TPv3 tunnels, IPsec, or IP tunnels on the private side. When the command is configured, the system updates the TCP MSS option to the value of the received TCP SYN packet on the private side.
The no form of this command disables TCP MSS adjust on the private side.
Default
no private-tcp-mcc-adjust
Parameters
- bytes
-
Specifies the new TCP MSS value in bytes.
- octets
-
Specifies the new TCP MSS value in octets.
Platforms
VSR
- configure service vprn interface ipsec ipsec-tunnel private-tcp-mss-adjust
- configure router interface ipsec ipsec-tunnel private-tcp-mss-adjust
- configure service ies interface ipsec ipsec-tunnel private-tcp-mss-adjust
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ip-tunnel private-tcp-mss-adjust
- configure service ies interface sap ip-tunnel private-tcp-mss-adjust
- configure ipsec tunnel-template private-tcp-mss-adjust
- configure service vprn interface sap ipsec-tunnel private-tcp-mss-adjust
probe-count
probe-count
Syntax
probe-count probes-per-hop
no probe-count
Context
[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy probe-count)
Full Context
configure saa test type-multi-line lsp-trace sr-policy probe-count
Description
This command configures the number of probes per hop.
The no form of this command reverts to the default value.
Default
probe-count 1
Parameters
- probes-per-hop
-
Specifies the probes-per-hop count, expressed as number of packets.
Platforms
All
probe-fail-enable
probe-fail-enable
Syntax
[no] probe-fail-enable
Context
[Tree] (config>saa>test>trap-gen probe-fail-enable)
Full Context
configure saa test trap-gen probe-fail-enable
Description
This command enables the generation of an SNMP trap when the consecutive probe failure threshold (configured using the probe-fail-threshold command) is reached during the execution of the SAA ping test. This command is not applicable to SAA trace route tests.
The no form of this command disables the generation of an SNMP trap.
Platforms
All
probe-fail-threshold
probe-fail-threshold
Syntax
probe-fail-threshold threshold
no probe-fail-threshold
Context
[Tree] (config>saa>test>trap-gen probe-fail-threshold)
Full Context
configure saa test trap-gen probe-fail-threshold
Description
This command configures the threshold for trap generation after ping probe failure.
This command has no effect when probe-fail-enable is disabled. This command is not applicable to SAA trace route tests.
The no form of this command returns the threshold value to the default.
Default
probe-fail-threshold 1
Parameters
- threshold
-
Specifies the number of consecutive ping probe failures required to generate a trap.
Platforms
All
probe-history
probe-history
Syntax
probe-history {keep | drop | auto}
Context
[Tree] (config>saa>test probe-history)
Full Context
configure saa test probe-history
Description
Specifies history probe behavior. Defaults are associated with various configured parameters within the SAA test. Auto (keep) is used for test with probe counts of 100 or less, and intervals of 1 second and above. Auto (drop) only maintains summary information for tests marked as continuous with file functions, probe counts more than 100 and intervals of less than 1 second. SAA tests that are not continuous with a write to file defaults to Auto (keep). The operator is free to change the default behaviors for each type. Each test that maintains per probe history consumes more system memory. When per probe entries are required, the probe history is available at the completion of the test.
Default
probe-history auto
Parameters
- auto
-
An auto selector that determines the storage of the history information.
- drop
-
Stores summarized min/max/avg data not per probe information for test runs. This may be configured for all tests to conserve memory.
- keep
-
Stores per probe information for tests. This consumes significantly more memory than summary information and should only be used if necessary.
Platforms
All
process-arp-probes
process-arp-probes
Syntax
[no] process-arp-probes
Context
[Tree] (config>service>vpls>proxy-arp process-arp-probes)
Full Context
configure service vpls proxy-arp process-arp-probes
Description
This command enables router proxy ARP function replies to Duplicate Address Detection (DAD) ARP probes upon a successful proxy ARP table lookup.
The no form of this command disables the router from replying to DAD ARP probes.
Default
process-arp-probes
Platforms
All
process-cpm-traffic-on-sap-down
process-cpm-traffic-on-sap-down
Syntax
[no] process-cpm-traffic-on-sap-down
Context
[Tree] (config>service>vpls>sap process-cpm-traffic-on-sap-down)
Full Context
configure service vpls sap process-cpm-traffic-on-sap-down
Description
This command is applicable to simple SAPs configured on LAGs that are not part of any "endpoint” configurations or complicated resiliency schemes like MC-LAG with inter-chassis-backup (ICB) configurations. When configured, a simple LAG SAP is not removed from the forwarding plane and flooded traffic (unknown unicast, broadcast and multicast) is dropped on egress. This allows applicable control traffic that is extracted at the egress interface to be processed by the CPM. This command will not prevent a VPLS service from entering an operationally down state if it is the last active connection to enter a nonoperational state. By default, without this command, when a SAP on a LAG enters a nonoperational state, it is removed from the forwarding plane and no forwarding occurs to the egress.
The no form of this command removes a SAP over a LAG that is not operational from the forwarding process.
Default
no process-cpm-traffic-on-sap-down
Platforms
All
process-dad-neighbor-solicitations
process-dad-neighbor-solicitations
Syntax
[no] process-dad-neighbor-solicitations
Context
[Tree] (config>service>vpls>proxy-nd process-dad-neighbor-solicitations)
Full Context
configure service vpls proxy-nd process-dad-neighbor-solicitations
Description
This command enables the router proxy ND replies to Duplicate Address Detection (DAD) neighbor solicitations upon a successful proxy ND table lookup.
The no form of this command disables the router from replying to DAD neighbor solicitations.
Default
process-dad-neighbor-solicitations
Platforms
All
process-received-upa
process-received-upa
Syntax
[no] process-received-upa
Context
[Tree] (config>router>isis>upa process-received-upa)
Full Context
configure router isis prefix-unreachable process-received-upa
Description
This command enables processing of UPAs received from other routers. When configured, received UPAs are inserted into the unicast routing table as unreachable prefixes. When configured on an Area Boundary Router (ABR), received UPAs are inserted into the unreachable prefix table and redistributed into the other areas.
The no form of this command disables the processing of UPAs received from other routers. When disabled, received UPAs are ignored by the router.
Default
no process-received-upa
Platforms
All
profile
profile
Syntax
profile profile-name [create]
no profile profile-name
Context
[Tree] (config app-assure group url-filter web-service profile)
Full Context
configure application-assurance group url-filter web-service profile
Description
This command configures the category profiles of the web service.
The no form of this command removes the category profiles configuration.
Parameters
- profile-name
-
Specifies the name of the category profile, up to 256 characters.
- create
-
Keyword that specifies to create a category profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
profile
Syntax
[no] profile user-profile-name
Context
[Tree] (config system security profile)
Full Context
configure system security profile
Description
This command creates a context to create user profiles for command authorization and other functions associated with a user.
Profiles can be used to deny or permit user access to entire command branches or to specific commands.
Once the profiles are created, the user command assigns users to one or more profiles. You can define up to 16 user profiles but a maximum of 8 profiles can be assigned to a user.
The no form of this command deletes a user profile.
Parameters
- user-profile-name
-
Specifies the user profile name entered as a character string. The string is case sensitive and limited to 32 ASCII 7-bit printable characters with no spaces.
Platforms
All
profile
Syntax
profile {in | out}
no profile
Context
[Tree] (config saa test type-multi-line lsp-ping profile)
[Tree] (config saa test type-multi-line lsp-ping sr-policy profile)
[Tree] (config saa test type-multi-line lsp-trace sr-policy profile)
Full Context
configure saa test type-multi-line lsp-ping profile
configure saa test type-multi-line lsp-ping sr-policy profile
configure saa test type-multi-line lsp-trace sr-policy profile
Description
This command configures the profile state of the MPLS echo request packet.
The no form of this command reverts to the default value.
Default
profile out
Parameters
- in
-
Specifies "in” as the profile state of the MPLS echo request packet.
- out
-
Specifies "out” as the profile state of the MPLS echo request packet.
Platforms
All
profile
Syntax
profile {in | out}
no profile
Context
[Tree] (config>oam-pm>session>ip profile)
Full Context
configure oam-pm session ip profile
Description
This command defines whether the TWAMP Light PDU packet should be treated as in-profile or out-of-profile. The default has been selected because the forwarding class defaults to best effort.
The no form of this command restores the default value.
Default
profile out
Parameters
- in
-
Specifies that the TWAMP Light PDU packet is sent as in-profile.
- out
-
Specifies that the TWAMP Light PDU packet is sent as out-of-profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
profile
Syntax
profile {in | out}
no profile
Context
[Tree] (config>oam-pm>session>mpls profile)
Full Context
configure oam-pm session mpls profile
Description
This command defines whether the DM PDU packet should be treated as in profile or out-of-profile.
The no form of this command reverts the default value.
Default
profile out
Parameters
- in
-
Marks the PDU in profile.
- out
-
Marks the PDU out of profile.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
profile
Syntax
profile {in | out}
no profile
Context
[Tree] (config qos sap-ingress fc profile)
Full Context
configure qos sap-ingress fc profile
Description
This command places a forwarding class or subclass into a color aware profile mode. Normally, packets associated with a class are considered in-profile or out-of-profile solely based on the dynamic rate of the ingress queue relative to its CIR. Explicitly defining a class as in-profile or out-of-profile overrides this function by handling each packet with the defined profile state.
The profile command may only be executed when the forwarding class or the parent forwarding class (for a subclass) is mapped to a queue that has been enabled to support color aware profile packets. The queue may only be configured for profile-mode at the time the queue is created in the SAP ingress QoS policy.
A queue operating in profile-mode may support in-profile, out-of-profile, and non-profiled packets simultaneously. However, the high- and low-priority classification actions are ignored when the queue is in profile-mode.
The no form of this command removes an explicit in-profile or out-of-profile configuration on a forwarding class or subclass.
Default
no profile — The default profile state of a forwarding class or subclass is not to treat ingress packets as color aware. An explicit definition for in-profile or out-of-profile must be specified on the forwarding class or subclass.
Parameters
- in
-
The in keyword is mutually exclusive to the out keyword. When the profile in command is executed, all packets associated with the class will be handled as in-profile. Packets explicitly handled as in-profile or out-of-profile still flow through the ingress service queue associated with the class to preserve order within flows. In-profile packets will count against the CIR of the queue, diminishing the amount of CIR available to other classes using the queue that are not configured with an explicit profile.
- out
-
The out keyword is mutually exclusive to the in keyword. When the profile out command is executed, all packets associated with the class will be handled as out-of-profile. Packets explicitly handled as in-profile or out-of-profile still flow through the ingress service queue associated with the class to preserve order within flows. Out-of-profile packets will not count against the CIR of the queue, allowing other classes using the queue that are not configured with an explicit profile to be measured against the full CIR.
Platforms
All
profile
Syntax
profile {g8265dot1-2010 | ieee1588-2008 | g8275dot1-2014 | g8275dot2-2016}
Context
[Tree] (config system ptp profile)
Full Context
configure system ptp profile
Description
This command configures the profile for the internal PTP clock, which defines the Best timeTransmitter Clock Algorithm (BTCA) behavior.
The profile setting for the clock cannot be changed unless PTP is shutdown.
The clock-type is restricted based on the PTP profile setting.
-
If the profile is ieee1588-2008, the clock-type is not restricted.
-
If the profile is g8265dot1-2010, the clock type may only be ordinary slave or ordinary master; boundary clock is not allowed.
-
If the profile is g8275dot1-2014 or g8275dot2-2016, the clock-type may only be boundary clock or ordinary slave; ordinary master is not allowed.
When the profile is changed, the domain changes to the default value for the new profile. Any command parameters that are set to default for the original profile are changed to the default for the new profile. This applies to the following:
-
log-anno-interval set for the clock
-
log-sync-interval set for a peer or a port
-
log-delay-interval set for a port
Non-default parameter values for the original profile remain unchanged.
Default
profile g8265dot1-2010
Parameters
- g8265dot1-2010
-
Conforms to the ITU-T G.8265.1 specification.
- ieee1588-2008
-
Conforms to the 2008 version of the IEEE1588 standard.
- g8275dot1-2014
-
Conforms to the ITU-T G.8275.1 specification.
- g8275dot2-2016
-
Conforms to the ITU-T G.8275.2 specification.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
profile
Syntax
profile {g8265dot1-2010 | g8275dot1-2014 | g8275dot2-2016 | ieee1588-2008}
Context
[Tree] (config>system>ptp>alternate-profile profile)
Full Context
configure system ptp alternate-profile profile
Description
This command configures the standard profile that is used as the basis for the alternate profile.
The profile setting controls the content of PTP messages sent on ports and peers using this alternate profile.
Modification of this setting is allowed only when the alternate profile is shut down.
Default
profile g8275dot1-2014
Parameters
- g8265dot1-2010
-
Keyword to conform to the ITU-T G.8265.1 specification.
- g8275dot1-2014
-
Keyword to conform to the ITU-T G.8275.1 specification.
- g8275dot2-2016
-
Keyword to conform to the ITU-T G.8275.2 specification.
- ieee1588-2008
-
Keyword to conform to the 2008 version of the IEEE1588 standard.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
profile
Syntax
profile name [create]
no profile name
Context
[Tree] (config system network-element-discovery profile)
Full Context
configure system network-element-discovery profile
Description
This command configures a profile to be used by IGP to advertise the network element information to its neighbors.
The no form of this command deletes the specified profile.
Parameters
- name
-
Specifies the name of the profile, up to 32 characters.
Platforms
All
profile
Syntax
profile user-profile-name
no profile
Context
[Tree] (config system security user-template profile)
Full Context
configure system security user-template profile
Description
This command configures the command authorization profile to associate with a user template. See the user-template command for more details.
Parameters
- user-profile-name
-
The user profile name entered as a character string. The string is case sensitive and limited to 32 ASCII 7-bit printable characters with no spaces.
Platforms
All
profile
Syntax
profile quality-of-service-profile
Context
[Tree] (config>test-oam>link-meas>template>twl profile)
Full Context
configure test-oam link-measurement measurement-template twamp-light profile
Description
This command configures the QoS profile. The profile indicator determines if the packet is treated as in or out of profile as it moves through the local node.
Default
profile in
Parameters
- quality-of-service-profile
-
Specifies the QoS profile used when launching the link measurement test belonging to the specified template.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
profile
Syntax
profile cert-update-profile
Context
[Tree] (config system security pki cert-auto-upd cert profile)
Full Context
configure system security pki certificate-auto-update cert profile
Description
This command configures a certificate-update-profile to reference the update behavior.
Parameters
- cert-update-profile
-
Specifies the certificate profile name, up to 32 characters.
Platforms
All
profile-capped
profile-capped
Syntax
[no] profile-capped
Context
[Tree] (config>qos>sap-egress>policer profile-capped)
[Tree] (config>qos>qgrps>ingress>queue-group profile-capped)
[Tree] (config>qos>sap-ingress>policer profile-capped)
[Tree] (config>qos>qgrps>egr>queue-group profile-capped)
Full Context
configure qos sap-egress policer profile-capped
configure qos queue-group-templates ingress queue-group profile-capped
configure qos sap-ingress policer profile-capped
configure qos queue-group-templates egress queue-group profile-capped
Description
Profile-capped mode enforces an overall in-profile burst limit to the CIR bucket for ingress undefined, ingress explicit in-profile, egress soft-in-profile, and egress explicit in-profile packets. The default behavior when profile-capped mode is not enabled is to ignore the CIR output state when an explicit in-profile packet is handled by an ingress or egress policer.
The profile-capped mode makes two changes:
-
At egress, soft-in-profile packets (packets received from ingress as in-profile) are treated the same as explicit in-profile (unless explicitly reclassified as out-of-profile) and have an initial policer state of in-profile.
-
At both ingress and egress, any packet output from the policer with a non-conforming CIR state are treated as out-of-profile (out-of-profile state is ignored for initial in-profile packets when profile-capped mode is not enabled).
Default
no profile-capped
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
- configure qos sap-ingress policer profile-capped
- configure qos sap-egress policer profile-capped
All
- configure qos queue-group-templates egress queue-group profile-capped
- configure qos queue-group-templates ingress queue-group profile-capped
profile-capped
Syntax
[no] profile-capped
Context
[Tree] (config>qos>qgrps>egr>qgrp>policer profile-capped)
[Tree] (config>qos>qgrps>ing>qgrp>policer profile-capped)
Full Context
configure qos queue-group-templates egress queue-group policer profile-capped
configure qos queue-group-templates ingress queue-group policer profile-capped
Description
This command enables a limit on the profile.
Default
no profile-capped
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
profile-out-preserve
profile-out-preserve
Syntax
[no] profile-out-preserve
Context
[Tree] (config>qos>sap-egress>policer profile-out-preserve)
Full Context
configure qos sap-egress policer profile-out-preserve
Description
This command specifies whether to preserve the color of offered out-of-profile traffic at sap-egress policer (profile of the packet can change based on egress CIR state).
When enabled, traffic determined as out-of-profile at ingress policer will be treated as out-of-profile at sap-egress policer.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
profile-preferred
profile-preferred
Syntax
profile-preferred
no profile-preferred
Context
[Tree] (config>qos>plcr-ctrl-plcy>root profile-preferred)
Full Context
configure qos policer-control-policy root profile-preferred
Description
The profile-preferred command ensures that the root policer provides a preference to consume its PIR bucket tokens at a given priority level to packets that have their profile state set to in-profile by the output of the child policer CIR bucket.
Default
no profile-preferred
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, 7950 XRS, VSR
profiled-traffic-only
profiled-traffic-only
Syntax
[no] profiled-traffic-only
Context
[Tree] (config subscr-mgmt msap-policy sub-sla-mgmt single-sub profiled-traffic-only)
Full Context
configure subscriber-mgmt msap-policy sub-sla-mgmt single-sub-parameters profiled-traffic-only
Description
This command specifies whether only profiled traffic is applicable for an MSAP. When enabled, all queues are deleted.
The no form of this command reverts to the default setting.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
profiled-traffic-only
Syntax
[no] profiled-traffic-only
Context
[Tree] (config service ies if sap sub-sla-mgmt single-sub profiled-traffic-only)
[Tree] (config service ies sub-if grp-if sap sub-sla-mgmt single-sub profiled-traffic-only)
[Tree] (config service vprn if sap sub-sla-mgmt single-sub profiled-traffic-only)
[Tree] (config service vpls sap sub-sla-mgmt single-sub-parameters profiled-traffic-only)
[Tree] (config service vprn sub-if grp-if sap sub-sla-mgmt single-sub profiled-traffic-only)
Full Context
configure service ies interface sap sub-sla-mgmt single-sub profiled-traffic-only
configure service ies subscriber-interface group-interface sap sub-sla-mgmt single-sub-parameters profiled-traffic-only
configure service vprn interface sap sub-sla-mgmt single-sub profiled-traffic-only
configure service vpls sap sub-sla-mgmt single-sub-parameters profiled-traffic-only
configure service vprn subscriber-interface group-interface sap sub-sla-mgmt single-sub-parameters profiled-traffic-only
Description
This command specifies whether only profiled traffic is applicable for this SAP. The profiled traffic refers to single subscriber traffic on a dedicated SAP (in the VLAN-per-subscriber model). When enabled, subscriber queues are instantiated through the QOS policy defined in the sla-profile and the associated SAP queues are deleted. This can increase subscriber scaling by reducing the number of queues instantiated per subscriber (in the VLAN-per-subscriber model). In order for this to be achieved, any configured multi-sub-sap limit must be removed (leaving the default of 1).
The no form of this command disables the command.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
progress-indicator
progress-indicator
Syntax
progress-indicator
Context
[Tree] (config>system>management-interface>cli>md-cli>environment progress-indicator)
Full Context
configure system management-interface cli md-cli environment progress-indicator
Description
Commands in this context configure progress indicator parameters.
Platforms
All
promiscuous-mode
promiscuous-mode
Syntax
[no] promiscuous-mode
Context
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw promiscuous-mode)
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw promiscuous-mode)
Full Context
configure service vprn subscriber-interface group-interface wlan-gw promiscuous-mode
configure service ies subscriber-interface group-interface wlan-gw promiscuous-mode
Description
When promiscuous mode is enabled, the router accepts all traffic, including traffic that is not destined for a WLAN gateway group interface MAC or virtual MAC address for ESM processing.
The no form of this command causes the router to only accept traffic that is destined for a WLAN gateway group interface MAC or virtual MAC address for ESM processing.
Default
no promiscuous-mode
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
prompt
prompt
Syntax
prompt
Context
[Tree] (config>system>management-interface>cli>md-cli>environment prompt)
Full Context
configure system management-interface cli md-cli environment prompt
Description
Commands in this context configure prompt parameters.
Platforms
All
propagate-admin-group
propagate-admin-group
Syntax
[no] propagate-admin-group
Context
[Tree] (config>router>mpls>lsp>fast-reroute propagate-admin-group)
[Tree] (config>router>mpls>lsp-template>fast-reroute propagate-admin-group)
Full Context
configure router mpls lsp fast-reroute propagate-admin-group
configure router mpls lsp-template fast-reroute propagate-admin-group
Description
The command enables the signaling of the primary LSP path admin-group constraints in the FRR object at the ingress.
When this command is executed, the admin-group constraints configured in the context of the P2P LSP primary path, or the ones configured in the context of the LSP and inherited by the primary path, are copied into the FAST_REROUTE object. The admin-group constraints are copied into the 'include-any’ or 'exclude-any’ fields.
The ingress LER thus propagates these constraints to the downstream nodes during the signaling of the LSP to allow them to include the admin-group constraints in the selection of the FRR backup LSP for protecting the LSP primary path.
The ingress LER inserts the FAST_REROUTE object by default in a primary LSP path message. If the user disables the object using the following command, the admin-group constraints will not be propagated: config>router>mpls>no frr-object.
Note that the same admin-group constraints can be copied into the Session Attribute object. They are intended for the use of an LSR, typically an ABR, to expand the ERO of an inter-area LSP path. They are also used by any LSR node in the path of a CSPF or non-CSPF LSP to check the admin-group constraints against the ERO regardless if the hop is strict or loose. These are governed strictly by the command:
config>router>mpls>lsp>propagate-admin-group
In other words, the user may decide to copy the primary path admin-group constraints into the FAST_REROUTE object only, or into the Session Attribute object only, or into both. Note, however, that the PLR rules for processing the admin-group constraints can make use of either of the two object admin-group constraints.
This feature is supported with the following LSP types and in both intra-area and inter-area TE where applicable:
-
Primary path of a RSVP P2P LSP.
-
S2L path of an RSVP P2MP LSP instance
-
LSP template for an S2L path of an RSVP P2MP LSP instance.
The no form of this command disables the signaling of administrative group constraints in the FRR object.
Default
no propagate-admin-group
Platforms
All
propagate-admin-group
Syntax
[no] propagate-admin-group
Context
[Tree] (config>router>mpls>lsp-template propagate-admin-group)
[Tree] (config>router>mpls>lsp propagate-admin-group)
Full Context
configure router mpls lsp-template propagate-admin-group
configure router mpls lsp propagate-admin-group
Description
This command enables propagation of session attribute object with resource affinity (C-type 1) in PATH message. If an LSR receives a session attribute with resource affinity, then it will check the compatibility of admin-groups received in PATH message against configured admin-groups on the egress interface of LSP.
To support admin-group for inter-area LSP, the ingress node must configure propagating admin-groups within the session attribute object. If a PATH message is received by an LSR node that has the cspf-on-loose-hop option enabled and the message includes admin-groups, then the ERO expansion by CSPF to calculate the path to the next loose hop includes the admin-group constraints received from ingress node.
If this option is disabled, then the session attribute object without resource affinity (C-Type 7) is propagated in PATH message and CSPF at the LSR node does not include admin-group constraints.
This admin group propagation is supported with a P2P LSP, a P2MP LSP instance, and an LSP template.
The user can change the value of the propagate-admin-group option on the fly. A RSVP P2P LSP performs a Make-Before-Break (MBB) on changing the configuration. A S2L path of an RSVP P2MP LSP performs a Break-Before-Make on changing the configuration.
The no form of this command reverts to the default value.
Default
no propagate-admin-group
Platforms
All
propagate-hold-time
propagate-hold-time
Syntax
propagate-hold-time seconds
no propagate-hold-time
Context
[Tree] (config>eth-cfm>redundancy>mc-lag propagate-hold-time)
Full Context
configure eth-cfm redundancy mc-lag propagate-hold-time
Description
This command configures the delay, in seconds, that fault propagation is delayed because of port or MC-LAG state changes. This provides the amount of time for system stabilization during a port state changes that may be protected by MC-LAG. This command requires the standby-mep-shutdown command in order to take effect.
The no form of the command reverts to the default.
Default
propagate-hold-time 1
Parameters
- seconds
-
Specifies the amount of time in seconds. Zero means no delay.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
propagate-mac-flush
propagate-mac-flush
Syntax
[no] propagate-mac-flush
Context
[Tree] (config>service>vpls propagate-mac-flush)
Full Context
configure service vpls propagate-mac-flush
Description
This command enabled propagation of mac-flush messages received from the specified T-LDP on all spoke and mesh-SDPs within the context of the VPLS service. The propagation will follow split-horizon principles and any data-path blocking in order to avoid looping of these messages.
Default
no propagate-mac-flush
Platforms
All
propagate-mac-flush-from-bvpls
propagate-mac-flush-from-bvpls
Syntax
[no] propagate-mac-flush-from-bvpls
Context
[Tree] (config>service>vpls>pbb propagate-mac-flush-from-bvpls)
Full Context
configure service vpls pbb propagate-mac-flush-from-bvpls
Description
This command enables the propagation in the local PBB of any regular LDP MAC Flush received in the related B-VPLS. If an LDP MAC flush-all-but-mine is received in the B-VPLS context, the command controls also whether a flush is performed for all the customer MACs in the associated FDB. The command does not have any effect on a PBB MAC Flush (LDP MAC flush with PBB TLV) received in the related B-VPLS context.
The no form of this command disables the propagation of LDP MAC Flush i from the related B-VPLS.
Default
no propagate-mac-flush-from-bvpls
Platforms
All
propagate-metric
propagate-metric
Syntax
[no] propagate-metric
Context
[Tree] (config>service>vprn>rip propagate-metric)
Full Context
configure service vprn rip propagate-metric
Description
This command enables the BGP MED to be used to configure the RIP metric at the BGP to RIP transition on egress routers. BGP always configures the BGP MED to the RIP metric at the ingress router. When propagate-metric is configured, the RIP metric at egress routers is configured as the BGP MED attribute added to the optional value configured with the metric-out command.
The no version of this command sets the RIP metric to the optional value configured with the metric-out command plus 1.
Default
no propagate-metric
Platforms
All
propagate-pmtu-v4
propagate-pmtu-v4
Syntax
[no] propagate-pmtu-v4
Context
[Tree] (config>router>if>ipsec>ipsec-tunnel propagate-pmtu-v4)
[Tree] (config>service>ies>if>sap>ip-tunnel propagate-pmtu-v4)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel propagate-pmtu-v4)
[Tree] (config>service>vprn>if>sap>ip-tunnel propagate-pmtu-v4)
[Tree] (config>ipsec>tnl-temp propagate-pmtu-v4)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel propagate-pmtu-v4)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel propagate-pmtu-v4)
Full Context
configure router interface ipsec ipsec-tunnel propagate-pmtu-v4
configure service ies interface sap ip-tunnel propagate-pmtu-v4
configure service vprn interface sap ipsec-tunnel propagate-pmtu-v4
configure service vprn interface sap ip-tunnel propagate-pmtu-v4
configure ipsec tunnel-template propagate-pmtu-v4
configure service vprn interface ipsec ipsec-tunnel propagate-pmtu-v4
configure service ies interface ipsec ipsec-tunnel propagate-pmtu-v4
Description
This command enables the system to propagate the path MTU learned from public side to private side (IPv4 hosts).
The no form of this command prevents the learned path MTU propagation.
Default
propagate-pmtu-v4
Platforms
VSR
- configure router interface ipsec ipsec-tunnel propagate-pmtu-v4
- configure service vprn interface ipsec ipsec-tunnel propagate-pmtu-v4
- configure service ies interface ipsec ipsec-tunnel propagate-pmtu-v4
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure ipsec tunnel-template propagate-pmtu-v4
- configure service vprn interface sap ip-tunnel propagate-pmtu-v4
- configure service ies interface sap ip-tunnel propagate-pmtu-v4
- configure service vprn interface sap ipsec-tunnel propagate-pmtu-v4
propagate-pmtu-v6
propagate-pmtu-v6
Syntax
[no] propagate-pmtu-v6
Context
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel propagate-pmtu-v6)
[Tree] (config>ipsec>tnl-temp propagate-pmtu-v6)
[Tree] (config>service>vprn>if>sap>ip-tunnel propagate-pmtu-v6)
[Tree] (config>router>if>ipsec>ipsec-tunnel propagate-pmtu-v6)
[Tree] (config>service>ies>if>sap>ip-tunnel propagate-pmtu-v6)
[Tree] (config>service>vprn>if>sap>ipsec-tunnel propagate-pmtu-v6)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel propagate-pmtu-v6)
Full Context
configure service ies interface ipsec ipsec-tunnel propagate-pmtu-v6
configure ipsec tunnel-template propagate-pmtu-v6
configure service vprn interface sap ip-tunnel propagate-pmtu-v6
configure router interface ipsec ipsec-tunnel propagate-pmtu-v6
configure service ies interface sap ip-tunnel propagate-pmtu-v6
configure service vprn interface sap ipsec-tunnel propagate-pmtu-v6
configure service vprn interface ipsec ipsec-tunnel propagate-pmtu-v6
Description
This command enables the system to propagate the path MTU learned from public side to private side (IPv6 hosts).
The no form of this command prevents the learned path MTU propagation.
Default
propagate-pmtu-v6
Platforms
VSR
- configure service vprn interface ipsec ipsec-tunnel propagate-pmtu-v6
- configure service ies interface ipsec ipsec-tunnel propagate-pmtu-v6
- configure router interface ipsec ipsec-tunnel propagate-pmtu-v6
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ip-tunnel propagate-pmtu-v6
- configure ipsec tunnel-template propagate-pmtu-v6
- configure service vprn interface sap ipsec-tunnel propagate-pmtu-v6
- configure service ies interface sap ip-tunnel propagate-pmtu-v6
propagate-topology-change
propagate-topology-change
Syntax
[no] propagate-topology-change
Context
[Tree] (config>eth-ring>sub-ring>interconnect propagate-topology-change)
Full Context
configure eth-ring sub-ring interconnect propagate-topology-change
Description
This command configures the G.8032 sub-ring to propagate topology changes. From the sub-ring to the major ring as specified in the G.8032 interconnection flush logic. This command is only valid on the sub-ring and on the interconnection node. Since this command is only valid on a Sub-ring, a virtual link or non-virtual link must be specified to configure this command. The command is blocked on major rings (when both path a and b are specified on a ring).
The no form of this command reverts propagate to the default value.
Default
no propagate-topology-change
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
protect-circuit
protect-circuit
Syntax
protect-circuit port-id
no protect-circuit
Context
[Tree] (config>port>aps protect-circuit)
Full Context
configure port aps protect-circuit
Description
This command configures a physical port that will act as the protection circuit for this APS group. The protect circuit port must contain only the default configuration and cannot belong to another APS group. The protect circuit port must be of the same type as the working circuit for the APS group, for the port to be added to an APS group port. If that’s not the case, the command will return an error.
A protection circuit can only be added if the working circuit already exists; the protection circuit must be removed from the configuration before the working circuit is removed.
When a port is a protect-circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context is not allowed for that port unless it is part of the noted exceptions. The exception list includes these SONET/SDH commands:
-
clock-source
-
[no] loopback
-
[no] report-alarm
-
section-trace
-
[no] threshold
When is port configured as a protection circuit of an APS group, the configurations described above and all service configurations related to APS port are operationally inherited by the protect circuit. If the protect circuit cannot inherit the configurations (due to resource limitations), the configuration attempt fails and an error is returned to the user.
The protect circuit must be shutdown before it can be removed from the APS group port. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.
The no form of this command removes the protect-circuit.
Parameters
- port-id
-
Specifies the physical port that will act as the protection circuit for this APS group in the following format.
port-id
slot/mda/port
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
protect-nexthop-id
protect-nexthop-id
Syntax
protect-nexthop-id next-hop-index
no protect-nexthop-id
Context
[Tree] (config>router>p2mp-sr-tree>replication-segment>sr-mpls>downstream-nodes protect-nexthop-id)
Full Context
configure router p2mp-sr-tree replication-segment segment-routing-mpls downstream-nodes protect-nexthop-id
Description
This command provides the ID of the protection next hop used for FRR.
The protection next hop outgoing SID is pushed on top of the next hop SID list.
The no form of this command removes the protection next hop.
Default
no protect-nexthop-id
Parameters
- next-hop-index
-
Specifies the ID of the protection next hop.
Platforms
All
protect-tp-path
protect-tp-path
Syntax
[no] protect-tp-path
Context
[Tree] (config>router>mpls>lsp protect-tp-path)
Full Context
configure router mpls lsp protect-tp-path
Description
This command creates or edits the protect path for an MPLS-TP LSP. At least one working path must exist before a protect path can be created for an MPLS-TP LSP. If MPLS-TP linear protection is also configured, then this is the path that is used as the default protect path for the LSP. The protect path must be deleted before the working path. Only one protect path can be created for each MPLS-TP LSP.
The following commands are applicable to the working-tp-path: lsp-num, in-label, out-label, mep, shutdown.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
protection
protection
Syntax
protection none
protection hmac-sha256 key key [hash | hash2 | custom]
no protection
Context
[Tree] (config>python>py-script protection)
Full Context
configure python python-script protection
Description
This command specifies the format of the Python script file(s) in this python-script. Unintentional changing of Python script file could be prevented by using protected format.
The no form of this command equals to protection none.
Parameters
- none
-
Indicates the Python script is stored in plain text, without any mechanism in place to ensure the integrity nor the confidentiality of the content of the Python script.
- hmac-sha256
-
Indicates the first line of the Python script must consist of the hash value obtained by hashing the rest of the Python script using the hmac-sha256 hashing algorithm.
- key
-
The specified key along with original Python script file content are used to compute the hash. The computed hash will be compared to the hash in the Python script file. If there is no match, then system will fail to load the script.
- 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, clear text 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, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.
- custom
-
Specifies the key entered is a customized hashing scheme.
Platforms
All
protection
Syntax
protection protection
no protection
Context
[Tree] (config>router>segment-routing>srv6>inst>loc>func>end-x protection)
[Tree] (config>router>segment-routing>srv6>inst>ms-loc>func>ua protection)
Full Context
configure router segment-routing segment-routing-v6 base-routing-instance locator function end-x protection
configure router segment-routing segment-routing-v6 base-routing-instance micro-segment-locator function ua protection
Description
This command configures the protection type of the SID.
The no form of this command reverts to the default value of protected.
Default
protection protected
Parameters
- protection
-
Specifies whether the adjacency SID is protected.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
protection-template
protection-template
Syntax
protection-template name
no protection-template
Context
[Tree] (config>router>mpls>mpls-tp protection-template)
Full Context
configure router mpls mpls-tp protection-template
Description
Protection templates are used to define generally applicable protection parameters for MPLS-TP tunnels. Only linear protection is supported, and so the application of a named template to an MPLS-TP LSP implies that linear protection is used. A protection template is applied under the MEP context of the protect-path of an MPLS-TP LSP.
The protection-template command creates or edits a named protection template.
Default
no protection-template
Parameters
- name
-
Specifies the protection template name as a text string of up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
protection-template
Syntax
protection-template name
no protection-template
Context
[Tree] (config>router>mpls>lsp>protect-tp-path>mep protection-template)
Full Context
configure router mpls lsp protect-tp-path mep protection-template
Description
This command applies a protection template name to an MPLS-TP LSP that the protect path is configured under. If the template is applied, then MPLS-TP 1:1 linear protection is enabled on the LSP, using the parameters specified in the named template.
A named protection template can only be applied to the protect path context of an MPLS-TP LSP.
The no form of this command removes the template and thus disables mpls-tp linear protection on the LSP.
Default
no protection-template
Parameters
- name
-
Specifies at text string for the template up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
protection-type
protection-type
Syntax
protection-type {g8031-1to1 | loadsharing}
Context
[Tree] (config>eth-tunnel protection-type)
Full Context
configure eth-tunnel protection-type
Description
This command configures the model used for determining which members are actively receiving and transmitting data.
When the value is set to "g8031-1to1 (1)”, as per the G.8031 specification, only two members are allowed, and only one of them can be active at one point in time.
When the value is set to "loadsharing (2)”, multiple members can be active at one point in time.
Default
protection-type g8031-1to1
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
protection-type
Syntax
protection-type {link | node}
no protection-type
Context
[Tree] (config>router>route-next-hop-policy>template protection-type)
Full Context
configure router route-next-hop-policy template protection-type
Description
This command configures the protection type constraint into the route next-hop policy template.
The user can select if link protection or node protection is preferred in the selection of an LFA next-hop for all IP prefixes and LDP FEC prefixes to which a route next-hop policy template is applied. The default in SR OS implementation is node protection. The implementation will fall back to the other type if no LFA next-hop of the preferred type is found.
When the route next-hop policy template is applied to an IP interface, all prefixes using this interface as a primary next-hop will follow the protection type preference specified in the template.
The no form deletes the protection type constraint from the route next-hop policy template.
Default
protection-type node
Parameters
- {link | node}
-
Specifies the two possible values for the protection type.
Platforms
All
proto-version
proto-version
Syntax
proto-version {v070 | latest}
Context
[Tree] (config>system>grpc>gnmi proto-version)
Full Context
configure system grpc gnmi proto-version
Description
This command sets the gnmi.proto version that the GRPC server should use for all gNMI RPCs.
Default
proto-version latest
Parameters
- v070
-
Specifies to use v0.7.0 for gNMI RPCs. Only use this option for backward compatibility with legacy collectors.
- latest
-
Specifies to use the latest gnmi.proto version for gNMI RPCs. The latest version is v0.8.0.
Platforms
All
protocol
protocol
Syntax
protocol protocol profile-name profile-name
Context
[Tree] (config>system>security>pki>cert-upd-prof protocol)
Full Context
configure system security pki certificate-update-profile protocol
Description
This command configures the protocol to update the certificate.
Default
protocol cmpv2
Parameters
- protocol
-
Specifies the protocol type.
- profile-name
-
Specifies the name of the CA or EST profile to be used for the certificate update.
Platforms
All
protocol
Syntax
protocol protocol-id
no protocol
Context
[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter>entry>match protocol)
Full Context
configure subscriber-mgmt isa-service-chaining vas-filter entry match protocol
Description
This command configures the protocol ID to be matched in this entry of the VAS filter.
The no form of this command removes the protocol ID from the match criterium in the entry.
Parameters
- protocol-id
-
Specifies the protocol to match.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
protocol protocol-name
Context
[Tree] (config>app-assure protocol)
Full Context
configure application-assurance protocol
Description
This command configures the shutdown of protocols system-wide.
Parameters
- protocol-name
-
A string of up to 32 characters identifying a predefined protocol.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
protocol {eq | neq} protocol-name
no protocol
Context
[Tree] (config>app-assure>group>policy>app-filter>entry protocol)
Full Context
configure application-assurance group policy app-filter entry protocol
Description
This command configures protocol signature in the application definition.
The no form of this command restores the default (removes protocol from match application defined by this app-filter entry).
Default
no protocol
Parameters
- eq
-
Specifies that the value configured and the value in the flow are equal.
- neq
-
Specifies that the value configured differs from the value in the flow.
- protocol-name
-
A string of up to 32 characters identifying a predefined protocol.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
protocol protocol-name export-using export-method
no protocol protocol-name
Context
[Tree] (config>app-assure>group>statistics>aa-sub protocol)
Full Context
configure application-assurance group statistics aa-sub protocol
Description
This command configures aa-sub accounting statistics for export of protocols of a given AA ISA group/partition.
The no form of this command removes the protocol name.
Parameters
- protocol-name
-
Specifies an existing protocol name up to 32 characters in length.
- export-using export-method
-
Specifies that the method of stats export to be used. Accounting-policy is the only option for protocol statistics.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
protocol
Context
[Tree] (config>app-assure>group>statistics protocol)
Full Context
configure application-assurance group statistics protocol
Description
Commands in this context configure accounting and statistics collection parameters per-system for protocols of application assurance for a given AA ISA group/partition.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
protocol ipsec-protocol
no protocol
Context
[Tree] (config>ipsec>static-sa protocol)
Full Context
configure ipsec static-sa protocol
Description
This command configures the security protocol to use for an IPsec manual SA. The no statement resets to the default value.
Default
protocol esp
Parameters
- ipsec-protocol
-
Identifies the IPsec protocol used with this static SA.
Platforms
All
protocol
Syntax
protocol any
protocol protocol-id port opaque
protocol protocol-id port any
protocol protocol-id port from begin-port-id to end-port-id
no protocol
Context
[Tree] (config>ipsec>ts-list>local>entry protocol)
[Tree] (config>ipsec>ts-list>remote>entry protocol)
Full Context
configure ipsec ts-list local entry protocol
configure ipsec ts-list remote entry protocol
Description
This command specifies the protocol and port range in the IKEv2 traffic selector.
The SR OS supports OPAQUE ports and port ranges for the following protocols:
-
TCP
-
UDP
-
SCTP
-
ICMP
-
ICMPv6
-
MIPv6
For ICMP and ICMPv6, the port value takes the form icmp-type/icmp-code. For MIPv6, the port value is the mobility header type. For other protocols, only the port any configuration can be used.
Default
no protocol
Parameters
- protocol-id
-
Specifies the protocol ID. The value can be a number, a protocol name, or any.
- begin-port-id
-
Specifies the beginning of the port range.
- end-port-id
-
Specifies the end of the port range
- opaque
-
Specifies OPAQUE ports.
- any
-
Specifies any port.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
[no] protocol {number | any}
Context
[Tree] (config>service>nat>firewall-policy>unknown-protocols protocol)
Full Context
configure service nat firewall-policy unknown-protocols protocol
Description
This command configures the protocol numbers that are allowed to create unknown flows.
Protocol or IPv6 extension header values that are explicitly supported by SR OS can be configured but will not be treated as unknown protocols.
The no form of the command removes the allowance for the specified protocol to create unknown flows.
Parameters
- any
-
Specifies that unknown flows can be created by any protocol.
- number
-
Specifies the IANA number of a protocol that needs to be allowed to create unknown flows.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol
Syntax
[no] protocol protocol-id
Context
[Tree] (config>filter>match-list>protocol-list protocol)
Full Context
configure filter match-list protocol-list protocol
Description
This command adds a protocol to the match protocol list.
The no form of this command removes the protocol from the protocol-list.
Parameters
- protocol-id
-
protocol-number, protocol-name
- protocol-number
-
Specifies the protocol number value to be added or removed from the protocol list. The value can be expressed as a decimal integer, or in hexadecimal or binary format.
- protocol-name
-
Specifies the protocol name to be added or removed from the protocol list.
Platforms
All
protocol
Syntax
protocol protocol
no protocol [protocol]
Context
[Tree] (config>vrrp>policy>priority-event>route-unknown protocol)
Full Context
configure vrrp policy priority-event route-unknown protocol
Description
This command adds one or more route sources to match the route unknown IP route prefix for a route unknown priority control event.
If the route source does not match one of the defined protocols, the match is considered unsuccessful and the route-unknown event transitions to the set state.
The protocol command is optional. If the protocol command is not executed, the comparison between the RTM prefix return and the route-unknown IP route prefix will not include the source of the prefix. The protocol command cannot be executed without at least one associated route source parameter. All parameters are reset each time the protocol command is executed and only the explicitly defined protocols are allowed to match.
The no form of the command removes protocol route source as a match criteria for returned RTM route prefixes.
To remove specific existing route source match criteria, execute the protocol command and include only the specific route source criteria. Any unspecified route source criteria is removed.
Default
no protocol — No route source for the route unknown priority event is defined.
Parameters
- protocol
-
Explicitly defined protocols
Platforms
All
protocol
Syntax
protocol protocol-id
no protocol
Context
[Tree] (config>system>security>mgmt-access-filter>ip-filter>entry protocol)
Full Context
configure system security management-access-filter ip-filter entry protocol
Description
This command configures an IP protocol type to be used as a management access filter match criterion.
The protocol type, such as TCP, UDP, and OSPF, is identified by its respective protocol number. Well-known protocol numbers include ICMP (1), TCP (6), and UDP (17).
The no form the command removes the protocol from the match criteria.
Parameters
- protocol
-
Specifies the protocol number for the match criterion.
Platforms
All
protocol
Syntax
[no] protocol name [create]
Context
[Tree] (config>sys>security>dist-cpu-protection>policy protocol)
Full Context
configure system security dist-cpu-protection policy protocol
Description
This command creates the control protocol for the policy.
The no form of this command means packets of the specified protocol are not monitored or enforced (although they count in the FP protocol queue) on the objects to which this DCP policy is assigned. The packets are treated as part of the all-unspecified protocol if the protocol is created in the policy.
Parameters
- names
-
Signifies the protocol name.
- create
-
Mandatory keyword to create the protocol.
Platforms
All
protocol
Syntax
protocol protocol [all | { instance instance}]
protocol protocol2 [protocol2 (up to 5 max)]
no protocol
Context
[Tree] (config>router>policy-options>policy-statement>entry>from protocol)
Full Context
configure router policy-options policy-statement entry from protocol
Description
This command configures a routing protocol as a match criterion for a route policy statement entry. This command is used for both import and export policies depending how it is used.
The protocol direct-interface route type matches the specific direct interface host IPv4 /32 and IPv6 /128 routes. The protocol direct route type matches direct routes and does not match the specific /32 or /128 interface route itself.
The instance command cannot be used if multiple protocol names are specified for the protocol2 parameter.
The no form of this command removes the protocol match criterion.
Default
no protocol
Parameters
- protocol
-
Specifies the protocol name for the match criterion.
- instance
-
Specifies the OSPF, OSPFv3, or IS-IS protocol instance.
- protocol2
-
Specifies up to five protocol names to match on.
- all
-
Keyword that specifies to match on any OSPF, OSPFv3, or IS-IS protocol instance.
Platforms
All
protocol
Syntax
protocol protocol [all | instance instance]
protocol bgp bgp-label
no protocol
Context
[Tree] (config>router>policy-options>policy-statement>entry>to protocol)
Full Context
configure router policy-options policy-statement entry to protocol
Description
This command configures a routing protocol as a match criterion for a route policy statement entry. This command is used for both import and export policies depending how it is used.
The no form of this command removes the protocol match criterion.
Default
no protocol
Parameters
- protocol
-
Specifies the protocol name to match on.
- instance
-
Specifies the OSPF, OSPFv3, or IS-IS instance.
- all
-
Keyword that specifies to match on any OSPF, OSPFv3, or IS-IS protocol instance.
Platforms
All
protocol
Syntax
protocol protocol
Context
[Tree] (config>anysec>tnl-enc>enc-grp>peer-tnl-attrs protocol)
Full Context
configure anysec tunnel-encryption encryption-group peer-tunnel-attributes protocol
Description
This command configures a routing protocol as a match criterion for the outgoing tunnel.
Default
protocol sr-isis
Parameters
- protocol
-
Specifies the protocol name.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se
protocol
Syntax
protocol protocol
Context
[Tree] (config>anysec>tnl-enc>sec-term-pol protocol)
Full Context
configure anysec tunnel-encryption security-termination-policy protocol
Description
This command configures a routing protocol that is used to advertise the node SID of the incoming tunnel.
Default
protocol sr-isis
Parameters
- protocol
-
Specifies the protocol name to match on.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se
protocol-configuration-options
protocol-configuration-options
Syntax
protocol-configuration-options {apco | pco}
no protocol-configuration-options
Context
[Tree] (config>subscr-mgmt>gtp>peer-profile protocol-configuration-options)
Full Context
configure subscriber-mgmt gtp peer-profile protocol-configuration-options
Description
This command configures the Information Element to use for the Protocol Configuration Options.
The no form of this command reverts to the default value.
Default
protocol-configuration-options pco
Parameters
- apco
-
Specifies that the system uses the Protocol Configuration Options Information Element.
- pco
-
Specifies that the system uses the Additional Protocol Configuration Options Information Element.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
protocol-list
protocol-list
Syntax
protocol-list protocol-list-name [create]
no protocol-list protocol-list-name
Context
[Tree] (config>filter>match-list protocol-list)
Full Context
configure filter match-list protocol-list
Description
This command creates a list of IP protocols that can be used in line card IP and IPv6 filters.
The no form of this command removes the IP protocol list.
Default
no protocol-list
Parameters
- protocol-list-name
-
Specifies the name of the protocol list.
- create
-
This keyword is required to create the protocol list. After it is created, the protocol list can be enabled with or without the create keyword.
Platforms
All
protocol-port
protocol-port
Syntax
[no] protocol-port
Context
[Tree] (config>cflowd>collector>aggregation protocol-port)
Full Context
configure cflowd collector aggregation protocol-port
Description
This command specifies that flows be aggregated based on the IP protocol, source port number, and destination port number.
The no form of this command removes this type of aggregation from the collector configuration.
Platforms
All
protocol-protection
protocol-protection
Syntax
protocol-protection [allow-sham-links] [block-pim-tunneled]
no protocol-protection
Context
[Tree] (config>sys>security>cpu-protection protocol-protection)
Full Context
configure system security cpu-protection protocol-protection
Description
This command causes the network processor on the CPM to discard all packets received for protocols that are not configured on the particular interface. This helps mitigate DoS attacks by filtering invalid control traffic before it hits the CPU. For example, if an interface does not have IS-IS configured, then protocol protection will discard any IS-IS packets received on that interface.
Default
no protocol-protection
Parameters
- allow-sham-links
-
Allows sham links. As OSPF sham links form an adjacency over the MPLS-VPRN backbone network, when protocol-protection is enabled, the tunneled OSPF packets to be received over the backbone network must be explicitly allowed.
- block-pim-tunneled
-
Blocks extraction and processing of PIM packets arriving at the SR OS node inside a tunnel (for example, MPLS or GRE) on a network interface. With protocol-protection enabled and tunneled pim blocked, PIM in an mVPN on the egress DR will not switch traffic from the (*,G) to the (S,G) tree.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-7s, 7750 SR-14s, 7950 XRS
protocol-version
protocol-version
Syntax
protocol-version TLS version
no protocol-version
Context
[Tree] (config>system>security>tls>client-tls-profile protocol-version)
Full Context
configure system security tls client-tls-profile protocol-version
Description
This command configures the TLS version to be negotiated between the client and server.
When configured, the client adds the specified version as a supported version in its Hello message to the server. If tls-version-all is specified, the client adds both TLS 1.2 and TLS 1.3 as supported versions in its Hello message.
The no form of this command reverts to the default TLS version.
Default
protocol-version tls-version12
Parameters
- TLS version
-
Specifies the TLS version to include in the client Hello message.
- Values
-
tls-version12, tls-version13, tls-version-all
Platforms
All
protocol-version
Syntax
protocol-version TLS version
no protocol-version
Context
[Tree] (config>system>security>tls>server-tls-profile protocol-version)
Full Context
configure system security tls server-tls-profile protocol-version
Description
This command configures the TLS version to be negotiated between the server and client.
When configured, the server adds the specified version as a supported version in its Hello message to the client. If tls-version-all is specified, the server adds both TLS 1.2 and TLS 1.3 as supported versions in its Hello message.
The no form of this command reverts to the default TLS version.
Default
protocol-version tls-version12
Parameters
- TLS version
-
Specifies the TLS version to include in the server Hello message.
- Values
-
tls-version12, tls-version13, tls-version-all
Platforms
All
provider-tunnel
provider-tunnel
Syntax
[no] provider-tunnel
Context
[Tree] (config>service>vpls provider-tunnel)
Full Context
configure service vpls provider-tunnel
Description
Commands in this context configure the use of a P2MP LSP to forward Broadcast, Unknown unicast, and Multicast (BUM) packets of a VPLS or B-VPLS instance. The P2MP LSP is referred to as the Provider Multicast Service Interface (PMSI).
Platforms
All
provider-tunnel
Syntax
provider-tunnel
Context
[Tree] (config>service>vprn>mvpn provider-tunnel)
Full Context
configure service vprn mvpn provider-tunnel
Description
This command enables context to configure tunnel parameters for the MVPN.
Platforms
All
provider-tunnel
Syntax
provider-tunnel
Context
[Tree] (config>router>gtm provider-tunnel)
Full Context
configure router gtm provider-tunnel
Description
This command enables context to configure tunnel parameters for the GTM.
Platforms
All
proxy-arp
proxy-arp
Syntax
[no] proxy-arp
Context
[Tree] (config>service>vpls proxy-arp)
Full Context
configure service vpls proxy-arp
Description
Commands in this context configure the proxy-ARP parameters in a VPLS service.
Default
no proxy-arp
Platforms
All
proxy-arp
Syntax
[no] proxy-arp [mac [ieee-address]] [ ip [ipaddr] all]]
Context
[Tree] (debug>service>id proxy-arp)
Full Context
debug service id proxy-arp
Description
This command enables the debug of the proxy-arp function for a specified service. Alternatively, the debug can be enabled only for certain entries given by their IP or MAC addresses.
Platforms
All
proxy-arp-nd
proxy-arp-nd
Syntax
proxy-arp-nd
Context
[Tree] (config>service proxy-arp-nd)
Full Context
configure service proxy-arp-nd
Description
Commands in this context configure the service-level proxy-arp-nd commands.
Platforms
All
proxy-arp-policy
proxy-arp-policy
Syntax
[no] proxy-arp-policy policy-name [policy-name]
Context
[Tree] (config>service>ies>sub-if>grp-if proxy-arp-policy)
[Tree] (config>service>vprn>sub-if>grp-if proxy-arp-policy)
[Tree] (config>service>ies>if proxy-arp-policy)
[Tree] (config>service>vprn>if proxy-arp-policy)
Full Context
configure service ies subscriber-interface group-interface proxy-arp-policy
configure service vprn subscriber-interface group-interface proxy-arp-policy
configure service ies interface proxy-arp-policy
configure service vprn interface proxy-arp-policy
Description
This command specifies an existing policy-statement to analyze match and action criteria that controls the flow of routing information to and from a given protocol, set of protocols, or a neighbor.
The no form of this command disables the proxy ARP capability.
Parameters
- policy-name
-
Specifies the export route policy name. Allowed values are any string, up to 32 characters, composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The specified name must already be defined.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service ies subscriber-interface group-interface proxy-arp-policy
- configure service vprn subscriber-interface group-interface proxy-arp-policy
All
- configure service ies interface proxy-arp-policy
- configure service vprn interface proxy-arp-policy
proxy-arp-policy
Syntax
proxy-arp-policy policy-name [policy-name]
no proxy-arp-policy
Context
[Tree] (config>subscr-mgmt>git>ipv4 proxy-arp-policy)
Full Context
configure subscriber-mgmt group-interface-template ipv4 proxy-arp-policy
Description
This command configures a proxy ARP policy for the interface.
The no form of this command disables the proxy ARP capability.
Default
no proxy-arp-policy
Parameters
- policy-name
-
Specifies the export route policy name. Allowed values are any string, up to 32 characters, composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. A maximum of five policy names can be specified.
Note:The specified policy name must already be defined.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
proxy-arp-policy
Syntax
proxy-arp-policy policy-name [policy-name]
no proxy-arp-policy
Context
[Tree] (config>router>if proxy-arp-policy)
Full Context
configure router interface proxy-arp-policy
Description
This command enables and configure proxy ARP on the interface and specifies an existing policy-statement to analyze match and action criteria that controls the flow of routing information to and from a given protocol, set of protocols, or a specific neighbor. The policy-name is configured in the config>router>policy-options context.
Use proxy ARP so the router responds to ARP requests on behalf of another device. Static ARP is used when a router needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the router configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address.
Default
no proxy-arp-policy
Parameters
- policy-name
-
Specifies the export route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. A maximum of five policy names can be specified in a single statement. The specified policy names must already be defined.
Platforms
All
proxy-authentication
proxy-authentication
Syntax
[no] proxy-authentication
Context
[Tree] (config>router>l2tp>group>tunnel>ppp proxy-authentication)
[Tree] (config>service>vprn>l2tp>group>tunnel>ppp proxy-authentication)
[Tree] (config>router>l2tp>group>ppp proxy-authentication)
[Tree] (config>service>vprn>l2tp>group>ppp proxy-authentication)
Full Context
configure router l2tp group tunnel ppp proxy-authentication
configure service vprn l2tp group tunnel ppp proxy-authentication
configure router l2tp group ppp proxy-authentication
configure service vprn l2tp group ppp proxy-authentication
Description
This command configures the use of the authentication AVPs received from the LAC.
Default
no proxy-authentication
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
proxy-lcp
proxy-lcp
Syntax
[no] proxy-lcp
Context
[Tree] (config>service>vprn>l2tp>group>ppp proxy-lcp)
[Tree] (config>service>vprn>l2tp>group>tunnel>ppp proxy-lcp)
[Tree] (config>router>l2tp>group>ppp proxy-lcp)
[Tree] (config>router>l2tp>group>tunnel>ppp proxy-lcp)
Full Context
configure service vprn l2tp group ppp proxy-lcp
configure service vprn l2tp group tunnel ppp proxy-lcp
configure router l2tp group ppp proxy-lcp
configure router l2tp group tunnel ppp proxy-lcp
Description
This command configures the use of the proxy LCP AVPs received from the LAC.
Default
no proxy-lcp
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
proxy-nd
proxy-nd
Syntax
[no] proxy-nd
Context
[Tree] (config>service>vpls proxy-nd)
Full Context
configure service vpls proxy-nd
Description
Commands in this context configure the proxy-ND parameters in a VPLS service.
Default
no proxy-nd
Platforms
All
proxy-nd
Syntax
[no] proxy-nd [mac [ieee-address]] [ ip [ipaddr] all]]
Context
[Tree] (debug>service>id proxy-nd)
Full Context
debug service id proxy-nd
Description
This command enables the debug of the proxy-nd function for a specified service. Alternatively, the debug can be enabled only for certain entries given by their IPv6 or MAC addresses.
Platforms
All
proxy-nd-policy
proxy-nd-policy
Syntax
proxy-nd-policy policy-name [policy-name]
no proxy-nd-policy
Context
[Tree] (config>service>ies>if>ipv6 proxy-nd-policy)
Full Context
configure service ies interface ipv6 proxy-nd-policy
Description
This command configures a proxy neighbor discovery policy for the interface. This policy determines networks and sources for which proxy ND is attempted, when local proxy neighbor discovery is enabled.
The no form of this command reverts to the default value.
Parameters
- policy-name
-
Specifies up to five the export route policy names. Allowed values are any string, up to 32 characters, composed of printable, 7-bit ASCII characters excluding double quotes. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The specified name(s) must already be defined.
Up to 5 policy-names can be specified in a single statement.
Platforms
All
proxy-nd-policy
Syntax
proxy-nd-policy policy-name [policy-name]
no proxy-nd-policy
Context
[Tree] (config>service>vprn>if>ipv6 proxy-nd-policy)
Full Context
configure service vprn interface ipv6 proxy-nd-policy
Description
This command configures a proxy neighbor discovery policy for the interface.
Parameters
- policy-name
-
Specifies up to five existing policy names.
Platforms
All
proxy-nd-policy
Syntax
proxy-nd-policy policy-name [policy-name]
no proxy-nd-policy
Context
[Tree] (config>router>if>ipv6 proxy-nd-policy)
Full Context
configure router interface ipv6 proxy-nd-policy
Description
This command configure a proxy neighbor discovery policy for the interface.
Parameters
- policy-name
-
The neighbor discovery policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. A maximum of five policy names can be specified in a single statement. The specified policy names must already be defined.
Platforms
All
proxy-server
proxy-server
Syntax
proxy-server
Context
[Tree] (config>service>vpls>sap>dhcp proxy-server)
[Tree] (config>service>vprn>sub-if>grp-if>dhcp proxy-server)
[Tree] (config>service>ies>sub-if>grp-if>dhcp proxy-server)
[Tree] (config>service>ies>if>dhcp proxy-server)
[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp proxy-server)
Full Context
configure service vpls sap dhcp proxy-server
configure service vprn subscriber-interface group-interface dhcp proxy-server
configure service ies subscriber-interface group-interface dhcp proxy-server
configure service ies interface dhcp proxy-server
configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp proxy-server
Description
Commands in this context configure DHCP proxy server parameters.
Platforms
All
- configure service vpls sap dhcp proxy-server
- configure service ies interface dhcp proxy-server
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp proxy-server
- configure service ies subscriber-interface group-interface dhcp proxy-server
- configure service vprn subscriber-interface group-interface dhcp proxy-server
proxy-server
Syntax
[no] proxy-server
Context
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6 proxy-server)
Full Context
configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server
Description
This command allows access to the DHCP6 proxy server context. Within this context, DHCP6 proxy server parameters of the group interface can be configured.
Default
no proxy-server
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
proxy-server
Syntax
[no] proxy-server
Context
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6 proxy-server)
Full Context
configure service ies subscriber-interface group-interface ipv6 dhcp6 proxy-server
Description
This command allows access to the DHCP6 proxy server context. Within this context, DHCP6 proxy server parameters of the group interface can be configured
Default
no proxy-server
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
ps-information
ps-information
Syntax
[no] ps-information
Context
[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>avp ps-information)
Full Context
configure subscriber-mgmt diameter-application-policy gy include-avp ps-information
Description
This command includes the following AVPs in Diameter DCCA CCR messages encapsulated in [3GPP-873] Service-Information or [3GPP-874] PS-Information grouped AVPs:
-
[8] Framed-IP-Address
-
[30] Called-Station-Id
-
[97] Framed-IPv6-Prefix
-
[123] Delegated-IPv6-Prefix
-
[6527-99] Alc-IPv6-Address
-
[10415-1] 3GPP-IMSI
-
[10415-2] 3GPP-Charging-Id
-
[10415-5] 3GPP-GPRS-Negotiated-QoS-Profile
-
[10415-7] 3GPP-GGSN-Address
-
[10415-10] GGSN-NSAPI
-
[10415-11] 3GPP-Session-Stop-Indicator
-
[10415-12] 3GPP-Selection-Mode
-
[10415-13] 3GPP-Charging-Characteristics
-
[10415-16] 3GPP-GGSN-IPv6-Address
-
[10415-21] 3GPP-RAT-Type
-
[10415-847] GGSN-Address
-
[10415-1004] Charging-Rule-Base-Name
-
[10415-1247] PDP-Context-Type
The AVPs are included when configured in the include-avp context.
By default, these AVPs are included at the command level.
The no form of this command resets to the default setting.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
psi-payload
psi-payload
Syntax
psi-payload
Context
[Tree] (config>port>otu psi-payload)
Full Context
configure port otu psi-payload
Description
Commands in this context configure payload structure identifier payload parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
psid-offset
psid-offset
Syntax
psid-offset psid-offset-length
no psid-offset
Context
[Tree] (config>service>nat>map-domain>mapping-rule psid-offset)
Full Context
configure service nat map-domain mapping-rule psid-offset
Description
This command configures the length of the high order bits in the protocol port field whose aggregate value should always be greater than 0. This automatically excludes certain ports (such as well-known ports) from the translation.
It is a function of the CE to make sure that the psid-offset bits are always greater than 0. The VSR does not check whether those bits are 0.
Default
psid-offset 6
Parameters
- psid-offset-length
-
Specifies the length of the psid-offset bits in the protocol port field.
Platforms
VSR
psnp-authentication
psnp-authentication
Syntax
[no] psnp-authentication
Context
[Tree] (config>service>vprn>isis psnp-authentication)
[Tree] (config>service>vprn>isis>level psnp-authentication)
Full Context
configure service vprn isis psnp-authentication
configure service vprn isis level psnp-authentication
Description
This command enables authentication of individual ISIS packets of partial sequence number PDU (PSNP) type.
The no form of this command suppresses authentication of PSNP packets.
Platforms
All
psnp-authentication
Syntax
[no] psnp-authentication
Context
[Tree] (config>router>isis>level psnp-authentication)
[Tree] (config>router>isis psnp-authentication)
Full Context
configure router isis level psnp-authentication
configure router isis psnp-authentication
Description
This command enables authentication of individual IS-IS packets of partial sequence number PDU (PSNP) type.
The no form of this command suppresses authentication of PSNP packets.
Default
psnp-authentication
Platforms
All
ptp
ptp
Syntax
[no] ptp
Context
[Tree] (config>service>vprn ptp)
Full Context
configure service vprn ptp
Description
Commands in this context configure PTP parameters for the VPRN service.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp
Syntax
ptp
Context
[Tree] (config>system ptp)
Full Context
configure system ptp
Description
Commands in this context configure parameters for IEEE 1588-2008, Precision Time Protocol.
This command is only available on the control assemblies that support 1588.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp
Syntax
ptp
Context
[Tree] (config>system>sync-if-timing ptp)
Full Context
configure system sync-if-timing ptp
Description
Commands in this context configure parameters for system timing via IEEE 1588-2008, Precision Time Protocol.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-asymmetry
ptp-asymmetry
Syntax
ptp-asymmetry nanoseconds
no ptp-asymmetry
Context
[Tree] (config>port>ethernet ptp-asymmetry)
Full Context
configure port ethernet ptp-asymmetry
Description
This command configures the PTP asymmetry delay on an Ethernet port. The command is used to correct for known asymmetry as part of time of day or phase recovery using PTP packets on both local and downstream PTP clocks.
Default
no ptp-asymmetry
Parameters
- nanoseconds
-
Specifies the value, in nanoseconds, that the forward path delay varies from the mean path delay; the value can be a negative number.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-hw-assist
ptp-hw-assist
Syntax
[no] ptp-hw-assist
Context
[Tree] (config>service>ies>if ptp-hw-assist)
Full Context
configure service ies interface ptp-hw-assist
Description
This command configures the 1588 port based timestamping assist feature for the interface. This feature is supported on a specific set of hardware. The command may be blocked if not all hardware has the required level of support.
Only one interface per physical port can have ptp-hw-assist enabled.
The no form of this command disables the feature for the interface.
Default
no ptp-hw-assist
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-hw-assist
Syntax
[no] ptp-hw-assist
Context
[Tree] (config>service>vprn>if ptp-hw-assist)
Full Context
configure service vprn interface ptp-hw-assist
Description
This command configures the 1588 port based timestamping assist feature for the interface. This feature is supported on a specific set of hardware. The command may be blocked if not all hardware has the required level of support.
If the SAP configuration of the interface is removed, the ptp-hw-assist configuration will be removed.
If the IPv4 address configuration of the interface is removed, the ptp-hw-assist configuration will be removed.
Only one interface per physical port can have ptp-hw-assist enabled.
The no form of this command disables the feature for the interface.
Default
no ptp-hw-assist
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-hw-assist
Syntax
[no] ptp-hw-assist
Context
[Tree] (config>router>if ptp-hw-assist)
Full Context
configure router interface ptp-hw-assist
Description
This command configures the 1588 port based timestamping assist feature for the interface. Various checks are performed to ensure that this feature can be enabled. If a check fails:
-
The command is blocked/rejected with an appropriate error message.
-
If the SAP configuration of the interface is removed, the ptp-hw-assist configuration will be removed.
-
If the IPv4 address configuration of the interface is removed, the ptp-hw-assist configuration will be removed.
The port validates the destination IP address on received 1588 messages. If the 1588 messages are sent to a loopback address within the node rather than the address of the interface, the loopback address must be configured in the configure system security source-address application ptp context.
The no form of this command disables the feature for the interface.
Default
no ptp-hw-assist
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-tc
ptp-tc
Syntax
[no] ptp-tc
Context
[Tree] (config>system>satellite>eth-sat ptp-tc)
Full Context
configure system satellite eth-sat ptp-tc
Description
This command enables the ethernet satellite IEEE1588 transparent clock function. This function works with the SR OS host router configured as a PTP ordinary clock or boundary clock. This provides increased accuracy on the PTP event messages transiting the satellite. When a IEEE1588 event message transits the ethernet satellite, the correction field of the message is updated with the residence time of that message. This is used in PTP time calculations. All ports of the satellite are enabled for this capability with the one setting. This feature must be enabled to allow the assignment of one of the satellite’s client ports as a PTP port under config>system>ptp>port. This feature is only valid when using PTP over Ethernet encapsulation; it is not valid for PTP over IP encapsulation.
To enable this command, the satellite must have first been configured to support the feature using the config>system>satellite>eth-sat>feature transparent-clock-eth and must have been enabled for synchronous ethernet with config>system>satellite>eth-sat>sync-e.
All host ports connecting to this satellite must support 1588 port-based timestamping.
The no version of this command disables the specific satellite functionality.
Default
no ptp-tc
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
ptp-timestamping
ptp-timestamping
Syntax
[no] ptp-timestamping
Context
[Tree] (config>port>ethernet ptp-timestamping)
[Tree] (config>lag ptp-timestamping)
Full Context
configure port ethernet ptp-timestamping
configure lag ptp-timestamping
Description
Commands in this context configure the filtering for the ingress 1588 timestamping of PTP messages to match multiple PTP flows.
The no form of this command removes the filter.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS
ptsf
ptsf
Syntax
ptsf
Context
[Tree] (config>system>ptp ptsf)
Full Context
configure system ptp ptsf
Description
Commands in this context configure PTSF-unusable configuration.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
public-key-authentication
public-key-authentication
Syntax
[no] public-key-authentication
Context
[Tree] (config>system>security>ldap public-key-authentication)
Full Context
configure system security ldap public-key-authentication
Description
This command enables public key retrieval from the LDAP server. If disabled (no public-key-authentication), password authentication is attempted via LDAP.
Default
no public-key-authentication
Platforms
All
public-key-min-bits
public-key-min-bits
Syntax
public-key-min-bits bits
no public-key-min-bits
Context
[Tree] (config>service>ies>if>ipv6>secure-nd public-key-min-bits)
Full Context
configure service ies interface ipv6 secure-nd public-key-min-bits
Description
This command configures the minimum acceptable key length for public keys used in the generation of a Cryptographically Generated Address (CGA).
Parameters
- bits
-
Specifies the number of bits.
Platforms
All
public-key-min-bits
Syntax
public-key-min-bits bits
[no] public-key-min-bits
Context
[Tree] (config>service>vprn>if>send public-key-min-bits)
Full Context
configure service vprn interface ipv6 secure-nd public-key-min-bits
Description
This command configures the minimum acceptable key length for public keys used in the generation of a Cryptographically Generated Address (CGA).
Parameters
- bits
-
Specifies the number of bits.
Platforms
All
public-key-min-bits
Syntax
public-key-min-bits bits
no public-key-min-bits
Context
[Tree] (config>router>if>ipv6>secure-nd public-key-min-bits)
Full Context
configure router interface ipv6 secure-nd public-key-min-bits
Description
This command configures the minimum acceptable key length for public keys used in the generation of a Cryptographically Generated Address (CGA).
Parameters
- bits
-
Specifies the number of bits.
Platforms
All
public-key-only
public-key-only
Syntax
[no] public-key-only
Context
[Tree] (config>system>security>ssh>auth-method>server public-key-only)
Full Context
configure system security ssh authentication-method server public-key-only
Description
This command configures the SSH server to accept only the public-key authentication method.
The no form of this command configures the SSH server to accept public-key or password client authentication. If interactive-authentication is enabled in the configure system security aaa remote-servers radius or configure system security aaa remote-servers tacplus contexts, the SSH server also accepts interactive keyboard authentication.
Default
no public-key-only
Platforms
All
public-key-only
Syntax
public-key-only {false|true|system}
Context
[Tree] (config>system>security>user>ssh-auth-method>server public-key-only)
Full Context
configure system security user ssh-authentication-method server public-key-only
Description
This command configures the accepted SSH authentication method for the user connection.
Default
system
Parameters
- false
-
Specifies the use of public-key only, or public-key and password for client authentication. If interactive-authentication is enabled in the configure system security aaa remote-servers radius or configure system security aaa remote-servers tacplus contexts, the SSH server also accepts interactive keyboard authentication.
- true
-
Specifies the use of public-key authentication only.
- system
-
Specifies the use of the SSH authentication method configured at the system level.
Platforms
All
public-keys
public-keys
Syntax
public-keys
Context
[Tree] (config>system>security>user public-keys)
Full Context
configure system security user public-keys
Description
This command allows the user to enter the context to configure public keys for SSH.
Platforms
All
public-tcp-mss-adjust
public-tcp-mss-adjust
Syntax
public-tcp-mss-adjust octets
public-tcp-mss-adjust default
no public-tcp-mss-adjust
Context
[Tree] (config>service>vprn>l2tp>l2tpv3 public-tcp-mss-adjust)
[Tree] (config>service>vprn>l2tp>group>l2tpv3 public-tcp-mss-adjust)
[Tree] (config>router>l2tp>group>l2tpv3 public-tcp-mss-adjust)
[Tree] (config>service>vprn>l2tp>group>tunnel>l2tpv3 public-tcp-mss-adjust)
Full Context
configure service vprn l2tp l2tpv3 public-tcp-mss-adjust
configure service vprn l2tp group l2tpv3 public-tcp-mss-adjust
configure router l2tp group l2tpv3 public-tcp-mss-adjust
configure service vprn l2tp group tunnel l2tpv3 public-tcp-mss-adjust
Description
This command enables TCP MSS adjust for L2TPv3 tunnels on the public side on the group or tunnel level. When the command is configured, the system updates the TCP MSS option value of the received TCP SYN packet on the public side that is encapsulated in the L2TPv3 tunnel.
Note that this command can be overridden by the corresponding configuration on the group or tunnel level.
With the default parameter, the system uses the upper level configuration. With the non-default parameter, the system uses this configuration instead of the upper level configuration.
The no form of this command disables TCP MSS adjust on the public side.
Default
no public-tcp-mss-adjust
Parameters
- octets
-
Specifies the new TCP MSS value in octets
- default
-
Specifies to use the upper-level configuration
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
public-tcp-mss-adjust
Syntax
public-tcp-mss-adjust bytes
public-tcp-mss-adjust octets
public-tcp-mss-adjust auto
no public-tcp-mss-adjust
Context
[Tree] (config>service>vprn>if>sap>ipsec-tun public-tcp-mss-adjust)
[Tree] (config>service>vprn>if>ip-tunnel public-tcp-mss-adjust)
[Tree] (config>service>ies>if>sap>ip-tunnel public-tcp-mss-adjust)
[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel public-tcp-mss-adjust)
[Tree] (config>service>ies>if>ipsec>ipsec-tunnel public-tcp-mss-adjust)
[Tree] (config>router>if>ipsec>ipsec-tunnel public-tcp-mss-adjust)
[Tree] (config>ipsec>tnl-temp public-tcp-mss-adjust)
Full Context
configure service vprn interface sap ipsec-tunnel public-tcp-mss-adjust
configure service vprn interface ip-tunnel public-tcp-mss-adjust
configure service ies interface sap ip-tunnel public-tcp-mss-adjust
configure service vprn interface ipsec ipsec-tunnel public-tcp-mss-adjust
configure service ies interface ipsec ipsec-tunnel public-tcp-mss-adjust
configure router interface ipsec ipsec-tunnel public-tcp-mss-adjust
configure ipsec tunnel-template public-tcp-mss-adjust
Description
This command enables the Maximum Segment Size (MSS) for the TCP traffic in an IPsec tunnel which is sent from the public network to the private network. The system may use this value to adjust or insert the MSS option in TCP SYN packet.
If the auto parameter is specified, the system derives the new MSS value based on the public MTU and IPsec overhead.
The no form of this command disables TCP MSS adjust on the public side.
Default
no public-tcp-mss-adjust
Parameters
- auto
-
Derive the new MSS value based on the public MTU and IPsec overhead.
- bytes
-
Specifies the new TCP MSS value in bytes.
- octets
-
Specifies the new TCP MSS value in octets
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn interface sap ipsec-tunnel public-tcp-mss-adjust
- configure service ies interface sap ip-tunnel public-tcp-mss-adjust
- configure ipsec tunnel-template public-tcp-mss-adjust
VSR
- configure router interface ipsec ipsec-tunnel public-tcp-mss-adjust
- configure service ies interface ipsec ipsec-tunnel public-tcp-mss-adjust
- configure service vprn interface ipsec ipsec-tunnel public-tcp-mss-adjust
purge-timeout
purge-timeout
Syntax
purge-timeout seconds
no purge-timeout
Context
[Tree] (config>system>grpc>rib-api purge-timeout)
Full Context
configure system grpc rib-api purge-timeout
Description
This command configures the purge timeout associated with the RibApi gRPC service.
If a gRPC client used the RibApi gRPC service to program RIB entries into the router, and then the TCP connection drops for any reason, the associated RIB entries are immediately marked as stale and a timer with the purge-timeout value is started. Upon timer expiration, all of the stale entries are removed. While the timer is running, the stale entries remain valid and usable for forwarding but are less preferred than any non-stale entry. The purge-timeout gives an opportunity for the disconnected client, or some other client, to re-program the necessary RIB entries so that forwarding can continue uninterrupted.
The no form of this command resets to the default value of 0. Entries are immediately deleted when the TCP connection drops.
Default
no purge-timeout
Parameters
- seconds
-
Specifies the number of seconds until the stale entries are purged.
Platforms
All
purge-timer
purge-timer
Syntax
purge-timer minutes
no purge-timer
Context
[Tree] (config>router>bgp purge-timer)
Full Context
configure router bgp purge-timer
Description
When the system sends a VPN-IP Route-Refresh to a peer it sets all the VPN-IP routes received from that peer (in the RIB-IN) to stale and starts the purge-timer. If the routes are not updated (refreshed) before the purge-timer has expired then the routes are removed.
The BGP purge timer configures the time before stale routes are purged.
The no form of this command reverts to the default.
Default
purge-timer 10
Parameters
- minutes
-
Specifies the maximum time before stale routes are purged.
Platforms
All
push
push
Syntax
push {label | implicit-null-label} nexthop ip-address
no push {out-label | implicit-null-label}
Context
[Tree] (config>router>mpls>static-lsp push)
Full Context
configure router mpls static-lsp push
Description
This command specifies the label to be pushed on the label stack and the next hop IP address for the static LSP.
The no form of this command removes the association of the label to push for the static LSP.
Parameters
- implicit-null-label
-
Specifies the use of the implicit label value for the push operation.
- label
-
The label to push on the label stack. Label values 16 through 1,048,575 are defined as follows:
-
label values 16 through 31 are reserved
-
label values 32 through 1,023 are available for static assignment
-
label values 1,024 through 2,047 are reserved for future use
-
label values 2,048 through 18,431 are statically assigned for services
-
label values 28,672 through 131,071 are dynamically assigned for both MPLS and services
-
label values 131,072 through 1,048,575 are reserved for future use
-
- nexthop ip-address
-
Specifies the IP address of the next hop towards the LSP egress router. If an ARP entry for the next hop exists, then the static LSP is marked operational. If ARP entry does not exist, software sets the operational status of the static LSP to down and continues to ARP for the configured nexthop. Software continuously tries to ARP for the configured nexthop at a fixed interval.
Platforms
All
pushed-labels
pushed-labels
Syntax
pushed-labels label [label]
no pushed-labels
Context
[Tree] (config>router>mpls>fwd-policies>fwd-policy>nh-grp>pri pushed-labels)
[Tree] (config>router>mpls>fwd-policies>fwd-policy>nh-grp>bkup pushed-labels)
Full Context
configure router mpls forwarding-policies forwarding-policy next-hop-group primary-next-hop pushed-labels
configure router mpls forwarding-policies forwarding-policy next-hop-group backup-next-hop pushed-labels
Description
This command configures the pushed label stack for the primary or backup next hop of a next-hop group of an MPLS forwarding policy.
The no form of this command removes the pushed label stack.
Parameters
- label
-
Specifies the label value; up to a maximum of 10 labels.
Platforms
All
pw-cap-list
pw-cap-list
Syntax
pw-cap-list {ethernet | ethernet-vlan} [{ ethernet | ethernet-vlan}]
no pw-cap-list
Context
[Tree] (config>service>vprn>l2tp>group>l2tpv3 pw-cap-list)
Full Context
configure service vprn l2tp group l2tpv3 pw-cap-list
Description
This command configures the allowable pseudowire capability list that is advertised to the far end. An empty list results in both pseudowire capabilities being advertised. Up to two capabilities are allowed to be advertised.
The no form of this command removes the list and advertises both pseudowire capabilities to the far end.
Default
no pw-cap-list
Parameters
- ethernet
-
Specifies that the Ethernet pseudo-wire type is advertised.
- ethernet-vlan
-
Specifies that the Ethernet-VLAN pseudo-wire type is advertised.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
pw-path-id
pw-path-id
Syntax
[no] pw-path-id
Context
[Tree] (config>service>ies>if>spoke-sdp pw-path-id)
[Tree] (config>service>vpls>spoke-sdp pw-path-id)
[Tree] (config>service>epipe>spoke-sdp pw-path-id)
[Tree] (config>service>vprn>if>spoke-sdp pw-path-id)
[Tree] (config>service>cpipe>spoke-sdp pw-path-id)
[Tree] (config>service>vprn>red-if>spoke-sdp pw-path-id)
Full Context
configure service ies interface spoke-sdp pw-path-id
configure service vpls spoke-sdp pw-path-id
configure service epipe spoke-sdp pw-path-id
configure service vprn interface spoke-sdp pw-path-id
configure service cpipe spoke-sdp pw-path-id
configure service vprn redundant-interface spoke-sdp pw-path-id
Description
Commands in this context configure an MPLS-TP Pseudowire Path Identifier for a spoke-sdp. All elements of the PW path ID must be configured in order to enable a spoke-sdp with a PW path ID.
For an IES or VPRN spoke-sdp, the pw-path-id is only valid for ethernet spoke-sdps.
The pw-path-id is only configurable if all of the following is true:
-
SDP signaling is off
-
control-word is enabled (control-word is disabled by default)
-
the service type is Epipe, VPLS, Cpipe, or IES/VPRN interface
-
mate SDP signaling is off for vc-switched services
The no form of this command deletes the PW path ID.
Default
no pw-path-id
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure service epipe spoke-sdp pw-path-id
- configure service ies interface spoke-sdp pw-path-id
- configure service cpipe spoke-sdp pw-path-id
- configure service vprn interface spoke-sdp pw-path-id
- configure service vpls spoke-sdp pw-path-id
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s
- configure service vprn redundant-interface spoke-sdp pw-path-id
pw-path-id
Syntax
[no] pw-path-id
Context
[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp pw-path-id)
[Tree] (config>mirror>mirror-dest>spoke-sdp pw-path-id)
Full Context
configure mirror mirror-dest remote-source spoke-sdp pw-path-id
configure mirror mirror-dest spoke-sdp pw-path-id
Description
Commands in this context configure an MPLS-TP Pseudowire Path Identifier for a spoke SDP. All elements of the PW path ID must be configured in order to enable a spoke SDP with a PW path ID.
For an IES or VPRN spoke SDP, the pw-path-id is only valid for Ethernet spoke SDPs.
The pw-path-id is only configurable if all of the following is true:
-
SDP signaling is off
-
control-word is enabled (control-word is disabled by default)
-
the service type is Epipe, Cpipe, Apipe, IES, VPLS, or VPRN interface
-
mate SDP signaling is off for VC-switched services
The no form of this command deletes the PW path ID.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pw-port
pw-port
Syntax
pw-port pw-port-id [pw-headend]
no pw-port
Context
[Tree] (config>service>system>bgp-evpn>eth-seg pw-port)
Full Context
configure service system bgp-evpn ethernet-segment pw-port
Description
This command configures a PW port associated to the Ethernet Segment. When the Ethernet Segment is configured as all-active, only a LAG or a PW port can be associated to the Ethernet Segment. When the Ethernet Segment is configured as single-active, then a LAG, port or SDP can be associated to the Ethernet Segment, but not a PW port unless the pw-headend parameter is configured. In either case, only one of the four objects can be configured in the Ethernet Segment. A specified PW port can be part of only one Ethernet Segment.
The no version of this command removes the PW port from the Ethernet Segment.
Default
no pw-port
Parameters
- pw-port-id
-
Specifies the PW port identifier.
- pw-headend
-
Keyword used to specify multihoming procedures are run in the PW port stitching Epipe and the routes advertised in the context of the stitching Epipe contain the ESI of the Ethernet Segment.
Platforms
All
pw-port
Syntax
pw-port id [create]
no pw-port id
Context
[Tree] (config pw-port)
Full Context
configure pw-port
Description
This command creates a PW port that can be bound to a physical port or associated with an FPE (anchored PW port). A PW port's purpose is to provide, through a PW SAP, access level (or SAP level) capability to customer traffic that is tunneled to the SR OS node through an IP/MPLS network.
The no form of this command removes the pw-port ID.
Default
no pw-port
Parameters
- id
-
Specifies the ID of the PW port.
- create
-
Keyword required to create the configuration context.
Platforms
All
pw-port
Syntax
pw-port pw-port-id [vc-id vc-id] [ create]
no pw-port pw-port-id
Context
[Tree] (config>service>sdp>binding pw-port)
Full Context
configure service sdp binding pw-port
Description
This command creates a pseudowire port.
The no form of the command removes the pseudowire port ID from the configuration.
Parameters
- pw-port-id
-
Specifies a unique identifier of the pseudowire port.
- vc-id
-
Specifies a virtual circuit identifier signaled to the peer.
- create
-
This keyword is required when a new pseudowire is being created.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pw-port
Syntax
pw-port pw-port-id [fpe fpe-id] [ create]
no pw-port
Context
[Tree] (config>service>epipe pw-port)
Full Context
configure service epipe pw-port
Description
This command is used to associate the PW-port with the PXC ports or PXC based LAGs referenced in the FPE. That is, the PW-port becomes anchored by the PXC. This enables an external PW that is mapped to the anchored PW-port to be seamlessly rerouted between the I/O ports without interruption of service on the PW-port. This mapping between the external PW (spoke SDP) and the PXC based PXC-port is performed via an Epipe operating in vc-switching mode (creation time parameter).
Default
no pw-port
Parameters
- pw-port-id
-
Specifies the PW-port associated with this service.
- fpe fpe-id
-
Specifies the FPE object which contains the PXC-based ports or PXC-based LAGs.
Platforms
All
pw-port
Syntax
pw-port pw-port-id [fpe fpe-id] [create]
no pw-port
Context
[Tree] (config>service>epipe pw-port)
Full Context
configure service epipe pw-port
Description
This command is only applicable for VSR configurations. This command associates a Flex PW port with any of the following constructs:
-
an MPLS-based spoke SDP (PW)
-
L2oGRE tunnel using IPv4 or IPv6 transport
With this configuration, a PW that is terminated on a Flex PW port can be seamlessly rerouted between I/O ports.
The payload from the PW is extracted from the Flex PW port and processed in accordance with the configured application (a capture SAP in ESM, a PW SAP for business services, and so on). The Epipe that associates the Flex PW port with the spoke SDP or with the tunnel is a regular Epipe service (not of type vc-switching).
This command must be configured before a spoke SDP is added to the Epipe.
The no form of this command removes the pw-port-id from the configuration.
Parameters
- pw-port-id
-
Specifies the PW port associated with the PW.
- fpe-id
-
Specifies the FPE object.
- create
-
Keyword required to create the configuration context.
Platforms
All
pw-port-extension
pw-port-extension
Syntax
[no] pw-port-extension
Context
[Tree] (config>fwd-path-ext>fpe pw-port-extension)
Full Context
configure fwd-path-ext fpe pw-port-extension
Description
Commands in this context configure the type of the cross-connect required to terminate an external tunnel to an anchored PW port. The system automatically builds the internal infrastructure required to perform the tunnel termination on a PW port.
PW ports support the following types of tunnels:
-
GRE/MPLS PW with SDP of type MPLS or GRE
-
L2oGRE bridged Ethernet over GRE, where GRE protocol number is 0x6558
The no form of this command removes the cross-connect type from the configuration.
Default
no pw-port-extension
Platforms
All
pw-port-list
pw-port-list
Syntax
pw-port-list
Context
[Tree] (config>service>system pw-port-list)
Full Context
configure service system pw-port-list
Description
Commands in this context configure a port list to bind to Flex PW ports.
Platforms
VSR
pw-routing
pw-routing
Syntax
pw-routing
Context
[Tree] (config>service pw-routing)
Full Context
configure service pw-routing
Description
Commands in this context configure dynamic multi-segment pseudowire (MS-PW) routing. Pseudowire routing must be configured on each node that will be a T-PE or an S-PE.
Platforms
All
pw-sap-secondary-shaper
pw-sap-secondary-shaper
Syntax
pw-sap-secondary-shaper pw-sap-sec-shaper-name
no pw-sap-secondary-shaper
Context
[Tree] (config>service>sdp>binding>pw-port>egress>shaper pw-sap-secondary-shaper)
Full Context
configure service sdp binding pw-port egress shaper pw-sap-secondary-shaper
Description
This command configures a default secondary shaper applicable to pw-saps under normal interfaces.
The no form of the command removes the shaper name from the configuration.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
pw-status-signaling
pw-status-signaling
Syntax
[no] pw-status-signaling
Context
[Tree] (config>service>epipe>spoke-sdp pw-status-signaling)
Full Context
configure service epipe spoke-sdp pw-status-signaling
Description
This command enables pseudowire status signaling for this spoke SDP binding.
The no form of this command disables the status signaling.
Default
pw-status-signaling
Platforms
All
pw-status-signaling
Syntax
[no] pw-status-signaling
Context
[Tree] (config>service>vpls>spoke-sdp pw-status-signaling)
Full Context
configure service vpls spoke-sdp pw-status-signaling
Description
This command specifies the type of signaling used by this multi-segment pseudowire provider-edge for this service.
When no pw-status-signaling is enabled, a 7450 ESS, 7750 SR, and 7950 XRS will not include the pseudowire status TLV in the initial label mapping message of the pseudowire used for a spoke-SDP. This will force both 7450 ESS, 7750 SR, and 7950 XRS PEs to use the pseudowire label withdrawal method for signaling pseudowire status.
If pw-status-signaling is configured, the node will include the use of the pseudowire status TLV in the initial label mapping message for the pseudowire.
Platforms
All
pw-template
pw-template
Syntax
pw-template policy-id [use-provisioned-sdp | [ prefer-provisioned-sdp] [auto-gre-sdp] ][create] [ name name]
no pw-template policy-id
Context
[Tree] (config>service pw-template)
Full Context
configure service pw-template
Description
This command configures an SDP template.
Parameters
- policy-id
-
Specifies a number that uniquely identifies a template for the creation of an SDP.
- use-provisioned-sdp
-
Specifies whether to use an already provisioned SDP. When specified, the tunnel manager is consulted for an existing active SDP (with a matching far-end address), and the SDP with the lowest metric is chosen. If there are multiple SDPs with the same metric, then the highest SDP identifier that is oper-up is chosen. The choice of SDP can be configured by applying sdp-include/exclude in the PW template together with an sdp-group in the provisioned SDPs. This option, and the auto-gre-sdp option, are mutually exclusive.
- prefer-provisioned-sdp
-
Specifies that if an existing matching SDP that conforms to any restrictions defined in the pw-template is found (for example, sdp-include/exclude group), then it will be used, following the same logic as for the use-provisioned-sdp parameter. Otherwise, the command will automatically create an SDP in the same manner as if the user did not specify any option. This option and the use-provisioned-sdp option are mutually exclusive.
- auto-gre-sdp
-
Specifies that an SDP should automatically be created using a GRE tunnel. This option and the use-provisioned-sdp option are mutually exclusive. The PW template parameters hash-label, entropy-label and sdp-include/exclude are ignored when an GRE SDP is auto-created.
- auto-mpls-sdp
-
Specifies that an SDP should automatically be created using an MPLS tunnel. This is the default.
- create
-
This keyword is required when first creating the configuration context. Once the context is created, it is possible to navigate into the context without the create keyword.
- name name
-
A name of the operator’s choice, up to 64 characters. The name is saved as part of the configuration.
If a name is not specified at creation time, then SR OS assigns a string version of the policy-id as the name.
Platforms
All
pw-template-bind
pw-template-bind
Syntax
pw-template-bind policy-id
no pw-template-bind
Context
[Tree] (config>service>epipe>spoke-sdp-fec pw-template-bind)
Full Context
configure service epipe spoke-sdp-fec pw-template-bind
Description
This command binds includes the parameters included in a specific PW template to a spoke SDP.
The no form of this command removes the values from the configuration.
Parameters
- policy-id
-
Specifies the existing policy ID.
Platforms
All
pw-template-binding
pw-template-binding
Syntax
pw-template-binding policy-id [import-rt { ext-community [ext-community]}] [endpoint endpoint-name]
no pw-template-binding policy-id
Context
[Tree] (config>service>epipe>bgp pw-template-binding)
Full Context
configure service epipe bgp pw-template-binding
Description
This command binds the advertisements received with the route targets (RT) that match the configured list (either the generic or the specified import) to a specific pw-template. If the RT list is not present, or if multiple matches are found, the numerically lowest pw-template is used.
The pw-template-binding applies to BGP-VPWS when enabled in the Epipe.
For BGP VPWS, the following additional rules govern the use of pseudowire-template:
-
On transmission, the settings for the L2-Info extended community in the BGP updates are derived from the pseudowire template attributes. If multiple pseudowire template bindings (with or without import-rt) are specified for the same VPWS instance the first pw-template entry will be used for the information in the BGP update sent.
-
On reception, the values of the parameters in the L2-Info extended community of the BGP updates are compared with the settings from the corresponding pseudowire template bindings. The following steps are used to determine the local pw-template:
-
The RT values are matched to determine the pw-template. The route targets configured for each pw-template-binding are compared to the route targets within the BGP update. The PW template corresponding to pw-template-binding with the first matching route target is used to for the SDP. The matching is performed from the lowest PW template binding identifier to the highest.
-
If no pw-template-binding matches are found from the previous step, the first (numerically lowest) configured pw-template entry without any route-target configured will be used.
-
If the value used for Layer 2 MTU (unless the value zero is received), or control word does not match, the pseudowire is created but with the operationally down state.
If the value used for the S (sequenced delivery) flags is not zero the pseudowire is not created.
The tools perform commands can be used to control the application of changes in pw-template for BGP-VPWS.
The no form of this command removes the values from the configuration.
Parameters
- policy-id
-
Specifies an existing policy ID.
- import-rt ext-comm
-
Specifies the communities, up to five, allowed to be accepted from remote PE neighbors. An extended BGP community in the type:x:y format. The value x can be an integer or IP address. The type can be the target or origin.
- endpoint-name
-
Specifies the name of the endpoint the BGP PW template is associated with, up to 32 characters. When the configured endpoint is associated to the pw-template-binding of a BGP VPWS service, EVPN MPLS can also be configured and associated to the same endpoint in the same Epipe service. Modifying this element causes the parent element to be recreated automatically in order for the new value to take effect.
Platforms
All
pw-template-binding
Syntax
pw-template-binding policy-id [split-horizon-group group-name] [import-rt {ext-community}]
no pw-template-bind policy-id
Context
[Tree] (config>service>vpls>bgp-ad pw-template-binding)
[Tree] (config>service>vpls>bgp pw-template-binding)
Full Context
configure service vpls bgp-ad pw-template-binding
configure service vpls bgp pw-template-binding
Description
This command binds the advertisements received with the route target (RT) that matches the configured list (either the generic or the specified import) to a specific PW template. If the RT list is not present the pw-template is used for all of them.
The pw-template-binding applies to both BGP-AD and BGP-VPLS if these features are enabled in the VPLS.
For BGP VPLS the following additional rules govern the use of pseudowire-template.
-
On transmission, the settings for the L2-Info extended community in the BGP update are derived from the pseudowire template attributes. If multiple pseudowire template bindings (with or without import-rt) are specified, the first pw-template entry will be used for the information in the BGP update sent.
-
On reception, the values of the parameters in the L2-Info extended community of the BGP update are compared with the settings from the corresponding pw-template. The following steps are used to determine the local pw-template.
-
The RT values are matched to determine the pw-template. The route targets configured for each pw-template-binding are compared to the route targets within the BGP update. The PW template corresponding to pw-template-binding with the first matching route target is used to for the SDP. The matching is performed from the lowest PW template binding identifier to the highest
-
If no pw-templates matches are found from the previous step, the first (numerically lowest) configured pw-template entry without any route-target configured will be used.
-
If the values used for Layer 2 MTU (unless the value zero is received) or control word flag do not match, the pseudowire is created but with the operationally down state.
If the value used for the S (sequenced delivery) flags is not zero, the pseudowire is not created.
The tools perform commands can be used to control the application of changes in pw-template for both BGP-AD and BGP-VPLS.
The no form of this command removes the values from the configuration.
Parameters
- policy-id
-
Specifies an existing policy ID
- group-name
-
The specified group-name overrides the split horizon group template settings
- import-rt ext-comm
-
Specifies communities allowed to be accepted from remote PE neighbors. An extended BGP community in the type:x:y format. The value x can be an integer or IP address. The type can be the target or origin. x and y are 16-bit integers. A maximum of five import-rt ext-com can be specified.
Platforms
All
pw-template-id-range
pw-template-id-range
Syntax
pw-template-id-range start pw-template-id end pw-template-id
no pw-template-id-range
Context
[Tree] (config>service>md-auto-id pw-template-id-range)
Full Context
configure service md-auto-id pw-template-id-range
Description
This command specifies the range of IDs used by SR OS to automatically assign an ID to PW templates that are created in model-driven interfaces without an ID explicitly specified by the user or client.
A PW template created with an explicitly-specified ID cannot use an ID in this range. In the classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD-CLI interfaces, the range can be changed, which causes any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.
The no form of this command removes the range values.
See the config>service md-auto-id command for further details.
Default
no pw-template-id-range
Parameters
- start pw-template-id
-
Specifies the lower value of the ID range. The value must be less than or equal to the end value.
- end pw-template-id
-
Specifies the upper value of the ID range. The value must be greater than or equal to the start value.
Platforms
All
pw-type
pw-type
Syntax
pw-type ethernet-vlan vlan-id
pw-type ethernet
no pw-type
Context
[Tree] (config>service>vpls>sap>l2tpv3-session pw-type)
[Tree] (config>service>epipe>sap>l2tpv3-session pw-type)
Full Context
configure service vpls sap l2tpv3-session pw-type
configure service epipe sap l2tpv3-session pw-type
Description
This command specifies the PW-type for the associated L2TPv3 session.
The support types are either Ethernet or Ethernet-VLAN. If Ethernet-VLAN is configured, a VLAN value must be specified as well.
The no form of this command deletes the PW-type configuration.
Parameters
- vlan-id
-
Specifies the VLAN-ID.
Platforms
All
pwc
pwc
Syntax
pwc [previous]
Context
[Tree] (pwc)
Full Context
pwc
Description
This command displays the present or previous working context of the CLI session. The pwc command provides a user who is in the process of dynamically configuring a chassis a way to display the current or previous working context of the CLI session. The pwc command displays a list of the CLI nodes that hierarchically define the current context of the CLI instance of the user.
The following example is from a 7750 SR:
A:ALA-1>config>router>bgp>group# pwc
-----------------------------------------------
Present Working Context :
-----------------------------------------------
<root>
configure
router Base
bgp
group test
ospf
area 1
-----------------------------------------------
A:ALA-1>config>router>bgp>group#
When the previous keyword is specified, the previous context displays. This is the context entered by the CLI parser upon execution of the exit command. The current context of the CLI is not affected by the pwc command.
The following example is from a 7450 ESS:
*A:ALA-1>config>router>ospf>area>if# pwc previous
---------------------------------------------------------
Previous Working Context :
---------------------------------------------------------
<root>
configure
router "Base"
ospf
area "0.0.0.0"
---------------------------------------------------------
*A:ALA-1config>router>ospf>area>if#
Parameters
- previous
-
Displays the previous present working context.
Platforms
All
pxc
pxc
Syntax
pxc pxc-id [create]
no pxc pxc-id
Context
[Tree] (config>port-xc pxc)
Full Context
configure port-xc pxc
Description
This command creates a port cross-connect (PXC) object. Referencing an Ethernet port within the PXC object will automatically configure this Ethernet port as a loopback port. The node will automatically create two PXC sub-ports under this Ethernet port. The configuration of PXC sub-ports can be accessed through the CLI.
Parameters
- pxc-id
-
Specifies the port cross-connect identifier.
Platforms
All
pxc-pxc-id.sub-port-id
pxc-pxc-id.sub-port-id
Syntax
pxc-pxc-id.sub-port-id
Context
[Tree] (config>port pxc-pxc-id.sub-port-id)
Full Context
configure port pxc-pxc-id.sub-port-id
Description
This command enables access to PXC sub-port level parameters. The PXC sub-ports are automatically created once the external Ethernet port is configured inside of an PXC object. The PXC sub-ports are by default administratively disabled (shutdown). In order for PXC sub-ports to became operational, both, the underlying external Ethernet port and the PXC object must be operationally up.
Parameters
- pxc-id
-
Specifies the unique identifier of this PXC.
- sub-port-id
-
When this the pxc-id is configured, two logical sub-ports are automatically created. These logical sub-ports are used to create two paths within the loop; one upstream path, and one downstream path. These sub-ports are destroyed when either this PXC row is destroyed, this object is de-provisioned.
Platforms
All
python
python
Syntax
python
Context
[Tree] (config python)
Full Context
configure python
Description
Commands in this context configure Python parameters.
Platforms
All
python
Syntax
[no] python
Context
[Tree] (config>redundancy>multi-chassis>peer>sync python)
Full Context
configure redundancy multi-chassis peer sync python
Description
This command enables syncing of python-policy cached entries to the peer.
Use the mcs-peer command in the Python policy to enable syncing for a specific Python policy.
The no form of this command reverts to the default.
Default
no python
Platforms
All
python-policy
python-policy
Syntax
python-policy python-name
no python-policy
Context
[Tree] (config>service>ies>if>dhcp python-policy)
[Tree] (config>service>ies>sub-if>dhcp python-policy)
[Tree] (config>service>vprn>sub-if>ipv6>dhcp6 python-policy)
[Tree] (config>service>vprn>if>dhcp python-policy)
[Tree] (config>service>vprn>sub-if>dhcp python-policy)
[Tree] (config>service>vprn>if>ipv6>dhcp6-relay python-policy)
[Tree] (config>service>vprn>sub-if python-policy)
[Tree] (config>service>vprn>sub-if>grp-if>dhcp python-policy)
[Tree] (config>service>ies>sub-if>ipv6>dhcp6 python-policy)
[Tree] (config>service>ies>if>ipv6>dhcp6-relay python-policy)
Full Context
configure service ies interface dhcp python-policy
configure service ies subscriber-interface dhcp python-policy
configure service vprn subscriber-interface ipv6 dhcp6 python-policy
configure service vprn interface dhcp python-policy
configure service vprn subscriber-interface dhcp python-policy
configure service vprn interface ipv6 dhcp6-relay python-policy
configure service vprn subscriber-interface python-policy
configure service vprn subscriber-interface group-interface dhcp python-policy
configure service ies subscriber-interface ipv6 dhcp6 python-policy
configure service ies interface ipv6 dhcp6-relay python-policy
Description
This command specifies the Python policy to be used for DHCPv6 relay.
The no form of this command reverts to the default.
Parameters
- python-name
-
Specifies the name of an existing python script, up to 32 characters.
Platforms
All
- configure service vprn interface ipv6 dhcp6-relay python-policy
- configure service vprn interface dhcp python-policy
- configure service ies interface dhcp python-policy
- configure service ies interface ipv6 dhcp6-relay python-policy
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
- configure service vprn subscriber-interface dhcp python-policy
- configure service ies subscriber-interface ipv6 dhcp6 python-policy
- configure service vprn subscriber-interface group-interface dhcp python-policy
- configure service vprn subscriber-interface python-policy
- configure service vprn subscriber-interface ipv6 dhcp6 python-policy
- configure service ies subscriber-interface dhcp python-policy
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>service>ies>sub-if>grp-if>dhcp python-policy)
[Tree] (config>service>vprn>sub-if>grp-if>dhcp python-policy)
Full Context
configure service ies subscriber-interface group-interface dhcp python-policy
configure service vprn subscriber-interface group-interface dhcp python-policy
Description
This command specified the Python policy for DHCPv4 packets sent/received on the group interface.
The no form of this command removes the policy name from the configuration.
Parameters
- name
-
Specifies an existing Python policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy policy-name
no python-policy
Context
[Tree] (config>service>ies>sub-if>grp-if>pppoe python-policy)
[Tree] (config>service>vprn>sub-if>grp-if>pppoe python-policy)
Full Context
configure service ies subscriber-interface group-interface pppoe python-policy
configure service vprn subscriber-interface group-interface pppoe python-policy
Description
This command specifies the Python policy for PPPoE packets sent/received on the group interface.
The no form of this command removes the policy name from the configuration.
Parameters
- policy-name
-
Specifies an existing Python policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>subscr-mgmt>gtp>peer-profile python-policy)
Full Context
configure subscriber-mgmt gtp peer-profile python-policy
Description
This command specifies the Python policy for MGW profile packets sent/received on the group interface.
The no form of this command removes the policy name from the configuration.
Default
no python-policy
Parameters
- name
-
Specifies an existing Python policy name up to 32 characters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy [policy-name]
no python-policy
Context
[Tree] (config>aaa>diam>node python-policy)
Full Context
configure aaa diameter node python-policy
Description
This command specified the python-policy for Diameter messages received or transmitted.
The no form of this command reverts to the default.
Parameters
- policy-name
-
Specifies the name of the Python policy, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name [create] [wlan-gw-group wlan-gw-group-id] [nat-group nat-group-id]
no python-policy name
Context
[Tree] (config>python python-policy)
Full Context
configure python python-policy
Description
This command creates a new Python policy or enables an existing Python policy configuration context.
There are two types of Python policies: centralized and distributed. A centralized Python policy runs on a CPM, while a distributed Python policy runs on an ISA. With the distributed Python policy, a wlan-gw-group wlan-gw-group-id or a nat-group nat-group-id command must specified.
The no form of this command removes the Python policy from the configuration.
Parameters
- name
-
Specifies the Python policy name up to 32 characters.
- create
-
This keyword is required when first creating the Python policy. Once the context is created, it is possible to navigate into the context without the create keyword.
- wlan-gw-group wlan-gw-group-id
-
Specifies the ID of the WLAN GW group that the distributed python-policy installs.
- nat-group nat-group-id
-
Specifies the ID of the NAT group that the distributed python-policy installs.
Platforms
All
python-policy
Syntax
python-policy policy-name
no python-policy
Context
[Tree] (config>aaa>isa-radius-policy python-policy)
Full Context
configure aaa isa-radius-policy python-policy
Description
This command specifies the Python policy for the ISA RADIUS proxy server. This is the python policy for RADIUS packets to/from the client.
The no form of this command removes the Python policy from the configuration.
Parameters
- name
-
Specifies the Python policy name, up to 32 characters
- create
-
This keyword is required when first creating the Python policy. Once the context is created, it is possible to navigate into the context without the create keyword.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6 python-policy)
[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6 python-policy)
Full Context
configure service vprn subscriber-interface group-interface ipv6 dhcp6 python-policy
configure service ies subscriber-interface group-interface ipv6 dhcp6 python-policy
Description
This command specified the Python policy for DHCPv6 packets sent/received on the group interface.
The no form of this command removes the policy name from the configuration.
Parameters
- name
-
Specifies an existing Python policy name, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>aaa>radius-srv-plcy python-policy)
Full Context
configure aaa radius-server-policy python-policy
Description
This command specifies the Python policy for RADIUS packets to/from the RADIUS servers defined in the specified radius-server-policy.
The no form of this command removes the policy name from the configuration.
Parameters
- name
-
Specifies the name of the Python policy, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>service>vprn>radius-proxy>server python-policy)
[Tree] (config>router>radius-proxy>server python-policy)
Full Context
configure service vprn radius-proxy server python-policy
configure router radius-proxy server python-policy
Description
This command specifies the Python policy for RADIUS packets sent/received on the client side of the RADIUS proxy server.
This command supports RADIUS proxy on both CPMs and ISAs.
The no form of this command removes the policy name from the configuration.
Parameters
- name
-
Specifies the name of the Python policy, up to 32 characters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>subscr-mgmt>pppoe-client-policy python-policy)
Full Context
configure subscriber-mgmt pppoe-client-policy python-policy
Description
This command applies a Python policy to all messages sent and received by the PPPoE client.
The no form of this command removes the associated Python policy from the PPPoE client.
Parameters
- name
-
The name of a preconfigured Python policy.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
python-policy
Syntax
python-policy name
no python-policy
Context
[Tree] (config>service>vprn>if>ipv6 python-policy)
Full Context
configure service vprn interface ipv6 python-policy
Description
This command specifies a python policy. Python policies are configured in the config>python> python-policy name context.
Parameters
- name
-
Specifies the name of an existing python script, up to 32 characters in length.
Platforms
All
python-policy
Syntax
python-policy python-policy-name
no python-policy
Context
[Tree] (config>router>if>dhcp python-policy)
Full Context
configure router interface dhcp python-policy
Description
This command specifies a python policy. Python policies are configured in the config>python>python-policy name context.
Default
no python-policy
Parameters
- python-policy-name
-
Specifies the name of an existing python script, up to 32 characters in length.
Platforms
All
python-policy
Syntax
python-policy policy-name
no python-policy
Context
[Tree] (config>log>log-id python-policy)
Full Context
configure log log-id python-policy
Description
This command associates the Python script with the events sent to this log ID. The Python policy can be associated with the log only if the destination in the log ID is set to syslog.
For information about Python policy configuration, refer to the Python Script Support for ESM in the 7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide.
The no form of this command disables Python processing of the events in this log ID.
Default
no python-policy
Parameters
- policy-name
-
Specifies a Python policy name, up to 32 characters.
Platforms
All
python-policy-cache
python-policy-cache
Syntax
python-policy-cache
Context
[Tree] (config>system>persistence python-policy-cache)
Full Context
configure system persistence python-policy-cache
Description
This command configures Python policy cache persistency parameters.
Platforms
All
python-script
python-script
Syntax
python-script name [create]
no python-script name
Context
[Tree] (config>python python-script)
Full Context
configure python python-script
Description
Commands in this context configure Python scripts to modify messages of different protocols.
The no form of this command removes the Python script name from the configuration.
Parameters
- name
-
Specifies the name of this Python script policy.
- create
-
This keyword is required when first creating the Python script. Once the context is created, it is possible to navigate into the context without the create keyword.
Platforms
All
python-script
Syntax
python-script script-name
Context
[Tree] (debug>python python-script)
Full Context
debug python python-script
Description
Commands in this context debug the specified Python script.
Parameters
- policy-name
-
Specifies the Python script name, up to 32 characters.
Platforms
All