Alcatel-Lucent 7750 SR Manual page 998

IES Interface Commands
IES SAP Commands
sap
Syntax sap sap-id [create]
no sap sap-id
Context config>service>ies>interface
config>service>ies>sub-if>grp-if
Description This command creates a Service Access Point (SAP) within a service. A SAP is a combination of port
and encapsulation parameters which identifies the service access point on the interface and within the
router. Each SAP must be unique.
All SAPs must be explicitly created. If no SAPs are created within a service or on an IP interface, a
SAP will not exist on that object.
Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the
service in which it was created.
A SAP can only be associated with a single service. A SAP can only be defined on a port that has
been configured as an access port using the command. Channelized TDM ports are always access
ports.
If a port is shutdown, all SAPs on that port become operationally down. When a service is shutdown,
SAPs for the service are not displayed as operationally down although all traffic traversing the service
will be discarded. The operational state of a SAP is relative to the operational state of the port on
which the SAP is defined.
Note that you can configure an IES interface as a loopback interface by issuing the loopback
command instead of the sap sap-id command. The loopback flag cannot be set on an interface where
a SAP is already defined and a SAP cannot be defined on a loopback interface.
The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all
configuration parameters for the SAP will also be deleted. For Internet Enhanced Service (IES), the
IP interface must be shutdown before the SAP on that interface may be removed.
Default
No SAPs are defined.
Special Cases IES — An IES SAP can be defined with Ethernet ports, SONET/SDH or TDM channels. A SAP is
Command syntax: sap ipsec-id.private|public:tag associates an IPSec group SAP with this interface.
This is the public side for an IPSec tunnel. Tunnels referencing this IPSec group in the private side
may be created if their local IP is in the subnet of the interface subnet and the routing context
specified matches with the one of the interface.
This context will provide a SAP to the tunnel. The operator may associate an ingress and egress QoS
policies as well as filters and virtual scheduling contexts. Internally this creates an Ethernet SAP that
will be used to send and receive encrypted traffic to and from the MDA. Multiple tunnels can be
associated with this SAP. The "tag" will be a dot1q value. The operator may see it as an identifier.
The range is limited to 1 — 4095.
Page 998
defined within the context of an IP routed interface. Each IP interface is limited to a single SAP
definition. Group interfaces allow more than one SAP. Attempts to create a second SAP on an IP
interface will fail and generate an error; the original SAP will not be affected.
7750 SR OS Services Guide