The most basic service configuration must have the following:
a customer ID
a service type
a service ID; an optional service name can also be configured in addition to the service ID. Service names are optional. All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used to identify and reference a specific service when it is initially created.
a SAP identifying a port and encapsulation value
an interface (where required) identifying an IP address, IP subnet, and broadcast address
for distributed services, an associated SDP
The following example provides an Epipe service configuration displaying the SDP and Epipe service entities. SDP ID 2 was created with the far-end node 10.10.10.104. Epipe ID 6000 was created for customer ID 6 which uses the SDP ID 2.
A:ALA-B>config>service# info detail
#------------------------------------------
...
sdp 2 gre create
description "GRE-10.10.10.104"
far-end 10.10.10.104
signaling tldp
no vlan-vc-etype
keep-alive
path-mtu 4462
keep-alive
shutdown
hello-time 10
hold-down-time 10
max-drop-count 3
timeout 5
no message-length
exit
no shutdown
exit
...
epipe 6000 name "customer-ABC-NW" customer 6 create
service-mtu 1514
sap 1/1/2:0 create
no multi-service-site
ingress
no scheduler-policy
qos 1
exit
egress
no scheduler-policy
qos 1
exit
no collect-stats
no accounting-policy
no shutdown
exit
spoke-sdp 2:6111 create
ingress
no vc-label
no filter
exit
egress
no vc-label
no filter
exit
no shutdown
exit
no shutdown
exit
...
#------------------------------------------
A:ALA-B>config>service#