Cisco Cisco Packet Data Gateway (PDG)
System Operation and Configuration
▀ Terminology
▄ ASR 5500 System Administration Guide, StarOS Release 18
22
Terminology
This section defines important terms used throughout this guide.
Contexts
A context is a logical grouping or mapping of configuration parameters that pertain to various physical ports, logical IP
interfaces, and services. A context can be thought of as a virtual private network (VPN).
interfaces, and services. A context can be thought of as a virtual private network (VPN).
The system supports the configuration of multiple contexts. Each context is configured and operates independently of
the others. Once a context has been created, administrative users can configure services, logical IP interfaces, and
subscribers for that context and then bind the logical interfaces to physical ports.
the others. Once a context has been created, administrative users can configure services, logical IP interfaces, and
subscribers for that context and then bind the logical interfaces to physical ports.
You can also assign a domain alias to a context; if a subscriber’s domain name matches one of the configured alias
names for a context, that context is used.
names for a context, that context is used.
Ports
Ports are the physical connectors on line cards that support remote access and subscriber traffic. Port configuration
includes traffic profiles, data encapsulation methods, media type, and other information for physical connectivity
between the system and the rest of the network.
includes traffic profiles, data encapsulation methods, media type, and other information for physical connectivity
between the system and the rest of the network.
Ports are identified by the chassis slot number for the Management Input/Output (MIO/UMIO) card, followed by the
physical connector number. For example, Port 5/10 identifies connector number 10 on the MIO/UMIO card in slot 5.
physical connector number. For example, Port 5/10 identifies connector number 10 on the MIO/UMIO card in slot 5.
Associate ports with contexts through bindings. For additional information on bindings, refer to the Bindings section
below. You can configure each physical port to support multiple logical IP interfaces, each with up to 17 IP addresses
(one primary and up to 16 secondaries).
below. You can configure each physical port to support multiple logical IP interfaces, each with up to 17 IP addresses
(one primary and up to 16 secondaries).
For complete information on line cards and port assignments, refer to the ASR 5500 Installation Guide.
Important:
UMIO cards and UDPC/UDPC2s are direct replacements for MIO cards and DPC/DPC2s. However,
a special Universal PID license must be purchased and installed on the chassis for each installed UMIO and
UDPC/UDPC2. Contact your Cisco account representative for additional licensing information.
UDPC/UDPC2. Contact your Cisco account representative for additional licensing information.
Important:
Throughout this guide, any reference to an MIO card or DPC is assumed to also refer to the UMIO
and UDPC/UDPC2 respectively.
Logical Interfaces
You must associate a port with a StarOS virtual circuit or tunnel called a logical interface before the port can allow the
flow of user data.Within StarOS, a logical interface is a named interface associated with a virtual router instance that
provides higher-layer protocol transport, such as Layer 3 IP addressing. Interfaces are configured as part of VPN
contexts and are independent from the physical ports that will be used to bridge the virtual interfaces to the network.
flow of user data.Within StarOS, a logical interface is a named interface associated with a virtual router instance that
provides higher-layer protocol transport, such as Layer 3 IP addressing. Interfaces are configured as part of VPN
contexts and are independent from the physical ports that will be used to bridge the virtual interfaces to the network.
Logical interfaces are associated with ethernet+ppp+tunnel addresses and are bound to a specific port during the
configuration process. Logical interfaces are also associated with services through bindings. Services are bound to an IP
configuration process. Logical interfaces are also associated with services through bindings. Services are bound to an IP