VLL Service Configuration Commands
Page 412 7750 SR OS Services Guide
The no form of the command removes the SAP from any multi-service customer site the SAP belongs
to. Removing the site can cause existing or future queues to enter an orphaned state.
Default None
customer-site-name — The customer-site-name must exist in the context of the customer-id defined
as the service owner. If customer-site-name exists and local scheduler policies have not been
applied to the SAP, the current and future queues defined on the SAP will look for their parent
schedulers within the scheduler hierarchies defined on customer-site-name.
Values Any valid customer-site-name created within the context of the customer-id.
tod-suite
Syntax tod-suite tod-suite-name
no tod-suite
Context config>service>cpipe>sap
Description This command applies a time-based policy (filter or QoS policy) to the service SAP. The suite name
must already exist in the config>cron context.
Default no tod-suite
Parameters tod-suite-name — Specifies collection of policies (ACLs, QoS) including time-ranges that define the
full or partial behavior of a SAP. The suite can be applied to more than one SAP.
service-mtu
Syntax service-mtu octets
no service-mtu
Context config>service>cpipe
Description This command configures the service payload (Maximum Transmission Unit – MTU), in bytes, for
the service. This MTU value overrides the service-type default MTU. The service-mtu defines the
payload capabilities of the service. It is used by the system to validate the SAP and SDP binding’s
operational state within the service.
The service MTU and a SAP’s service delineation encapsulation overhead (i.e., 4 bytes for a dot1q
tag) is used to derive the required MTU of the physical port on which the SAP was created. If the
required payload is larger than the port or channel MTU, then the SAP will be placed in an
inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP will
be able to transition to the operative state.
When binding an SDP to a service, the service MTU is compared to the path MTU associated with the
SDP. The path MTU can be administratively defined in the context of the SDP. The default or
administrative path MTU can be dynamically reduced due to the MTU capabilities discovered by the
tunneling mechanism of the SDP or the egress interface MTU capabilities based on the next hop in
the tunnel path.
To Next Page
Loading...
