Multiple IES services are created to separate customer owned IP interfaces. Attempting to edit a service with the incorrect customer-id specified results in an error. Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. The service must be deleted and recreated with a new customer association.
Once a service has been created with a customer association, it is not possible to edit the customer association. The customer-id must already exist having been created using the customer command in the service context. When a service is created, the customer keyword and customer-id must be specified and associates the service with a customer. This allows a combination of bridging and IP routing for redundancy purposes. IP interfaces defined within the context of an IES service ID must have a SAP created as the access point to the subscriber network. This feature is defined using the config router service-prefix command. This allows a portion of the service provider address space to be set aside for service IP provisioning, becoming administered by a separate but subordinate address authority. While IES is part of the routing domain, the usable IP address space may be limited. IES services require that the IP addressing scheme used by the subscriber must be unique between it and other addressing schemes used by the provider and potentially the entire Internet.
IES services allow the creation of customer facing IP interfaces in the same routing instance used for service network core routing connectivity. If the service-id exists, the context for editing the service is entered. If the service-id does not exist, a context for the service is created.
The ies command creates or maintains an Internet Ethernet Service (IES). This command creates or edits an IES service instance.
0 kommentar(er)
