Cisco Cisco Packet Data Gateway (PDG) Fehlerbehebungsanleitung
Understanding System Operation and Configuration
▀ Terminology
▄ Cisco ASR 5000 Series System Administration Guide
OL-22969-02
Terminology
This section defines some of the terms used in the following chapters.
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 is configured and operates independently from the
others. Once a context has been created, administrative users can then configure services, logical IP interfaces, and
subscribers for that context. Administrative users then bind the logical interfaces to physical ports.
others. Once a context has been created, administrative users can then configure services, logical IP interfaces, and
subscribers for that context. Administrative users then bind the logical interfaces to physical ports.
Contexts can also be assigned domain aliases; if a subscriber‘s domain name matches one of the configured alias names
for that context, then that context is used.
for that context, then that context is used.
Ports
Ports are the physical Ethernet connectors (Ethernet 10/100, Ethernet 1000 Line Cards, four-port Quad Gigabit Line
Cards (QGLC), and 10-Gigabit Ethernet Line Cards (XGLC) . Ethernet port configuration addresses 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 line card, followed by the physical connector
number.
Cards (QGLC), and 10-Gigabit Ethernet Line Cards (XGLC) . Ethernet port configuration addresses 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 line card, followed by the physical connector
number.
For example, Port 24/1 identifies connector number 1 on the card in slot 24.
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).
Logical Interfaces
You must associate a port with a virtual circuit or tunnel called a logical interface before the port can allow the flow of
user data. A logical interface within the system is defined as the logical assignment of a virtual router instance that
provides higher-layer protocol transport, such as Layer 3 IP addressing. Interfaces are configured as part of the VPN
context and are independent from the physical port that will be used to bridge the virtual interfaces to the network.
user data. A logical interface within the system is defined as the logical assignment of a virtual router instance that
provides higher-layer protocol transport, such as Layer 3 IP addressing. Interfaces are configured as part of the VPN
context and are independent from the physical port that will be used to bridge the virtual interfaces to the network.
There are several types of logical interfaces to configure to support Simple and Mobile IP data applications.
Management interface: This interface provides the point of attachment to the management network. The interface
supports remote access to the CLI It also supports Common Object Request Broker Architecture (CORBA)-based
management via the Web Element Manager application, and event notification via the Simple Network Management
Protocol (SNMP).
supports remote access to the CLI It also supports Common Object Request Broker Architecture (CORBA)-based
management via the Web Element Manager application, and event notification via the Simple Network Management
Protocol (SNMP).