для Cisco Cisco Tunnel Terminating Gateway (TTG)

 

▄  VPC-VSM System Administration Guide, StarOS Release 19 

This section defines important StarOS terms used throughout this guide. 

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). 

StarOS 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. 

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. 

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 StarOS is the 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. 

This interface provides the point of attachment to the management network. The interface supports remote access to the 
StarOS command line interface (CLI). It also supports event notification via the Simple Network Management Protocol 
(SNMP). 

A binding is an association between elements within StarOS. There are two types of bindings: static and dynamic. 

Static binding is accomplished through system configuration. Static bindings associate: 



 

A specific logical interface (configured within a particular context) to a physical or virtual port. Once the 

interface is bound, traffic can flow through the context as if it were any physically-defined circuit. Static 
bindings support any encapsulation method over any interface and port type. 



 

A service to an IP address assigned to a logical interface within the same context. This allows the interface to 

take on the characteristics (that is, support the protocols) required by the service. 

Dynamic binding associates a subscriber to a specific egress context based on the configuration of their profile or 
system parameters. This provides a higher degree of deployment flexibility, as it allows a wireless carrier to support 
multiple services and facilitates seamless connections to multiple networks. 

Management ports can only be bound in the local context. Traffic or subscriber ports can only be bound in a non-local 
context.