This command configures a description for the interface.
The no form of the command removes the description from the interface configuration.
This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command.
The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
This mandatory command enables access to the chassis card Input/Output Control Forwarding Module (IOM/CFM), slot, MCM and MDA CLI context.
The no form of this command removes the card from the configuration. All associated ports, services, and MDAs must be shutdown.
No cards are configured.
This mandatory command enables access to a card’s MDA CLI context to configure MDAs.
No MDA slots are configured by default.
This mandatory command provisions a specific MDA type to the device configuration for the slot. The MDA can be preprovisioned but an MDA must be provisioned before ports can be configured. Ports can be configured once the MDA is properly provisioned.
The no form of this command deletes the MDA from the configuration. The MDA must be administratively shut down before it can be deleted from the configuration.
No MDA/CMA types are configured for any slots by default.
This command creates or edits an IES service instance.
The ies command is used to create or maintain an Internet Enhanced Service (IES). If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.
IES services allow the creation of customer facing IP interfaces in the same routing instance used for service network core routing connectivity. 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.
While IES is part of the routing domain, the usable IP address space may be limited. 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. This feature is defined using the config router service-prefix command.
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 allows a combination of bridging and IP routing for redundancy purposes.
When a service is created, the customer keyword and customer-id must be specified and associates the service with a customer. The customer-id must already exist having been created using the customer command in the service context. Once a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer-id specified will result in an error.
Multiple IES services are created to separate customer owned IP interfaces. More than one IES service may be created for a single customer ID. More than one IP interface may be created within a single IES service ID. All IP interfaces created within an IES service ID belongs to the same customer.
By default, no IES service instances exist until they are explicitly created.
The no form of this command deletes the IES service instance with the specified service-id. The service cannot be deleted until all the IP interfaces defined within the service ID have been shutdown and deleted.
service-id: | 1 — 2147483648 |
svc-name: | 64 characters maximum |
This command configure a Threat Managment Service interface.
The no form of the command removes the interface name from the configuration.
This command assigns an IP address/IP subnet/broadcast address to the TMS instance for communications between Arbor CP collectors/managers and the TMS instance operating within the Service Router.
The no form of the command removes the IP address information from the interface configuration.
<ip-address[/mask]> | ip-address a.b.c.d |
mask | 32 |
<netmask> | a.b.c.d (all 1 bits) |
This command configures IPv6 for a threat-management service interface.
The no form of the command removes the IP address information from the interface configuration.
This command configures a password for the user.
The no form of the command removes the password.
This command specifies a chassis slot and MDA to bind the interface to a physical port.
The no form of the command removes the MDA ID from the interface configuration.
<slot>/<mda> | slot | [1..10] |
mda | [1..2] |
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.
If no protocol criterion is specified, any protocol is considered a match.
The no form of the command removes the protocol match criterion.
no protocol — Matches any protocol.