Cisco Cisco Packet Data Gateway (PDG)
Engineering Rules
VPC Interface and Port Rules ▀
VPC-VSM System Administration Guide, StarOS Release 19 ▄
297
VPC Interface and Port Rules
The rules discussed in this section pertain to the vNIC Ethernet ports designated via the hypervisor for subscriber traffic.
vNIC Ethernet Ports
Give all hypervisor-assigned logical interfaces a unique name to differentiate the interface from others in the
same context.
A single virtual port can support multiple hypervisor-assigned logical interfaces when you configure VLAN tags
for that port. You can use VLAN tagging to bind a single port to multiple logical interfaces that reside in
different contexts.
different contexts.
Each vNIC port for subscriber traffic may contain up to a maximum of 1,024 VLAN tags (maximum of 4,000
VLANs per VPC chassis).
All hypervisor-assigned logical interfaces must have a valid IP address and subnet.
If multi-homing is supported on the network, you can assign all logical interfaces a single primary IP
address and up to 16 secondary IP addresses.
You configure a single StarOS logical (named) interface per context. That named interface can have up to 512
ethernet+ppp+tunnel interfaces.
Different StarOS contexts can can share the same logical (named) interface.
You can apply a maximum of 256 access control list (ACL) rules to a StarOS logical interface.
In StarOS all ports are identified by their <slot#>/<port#>.
Packet Data Network (PDN) Interface Rules
The following engineering rules apply to the interface to the packet data network (PDN):
Configure the logical interfaces used to facilitate the PDN interface within the egress context.
The default is to use a single interface within the egress context to facilitate the PDN interface.
You can configure multiple interfaces in the egress context by using static routes or dynamic routing protocols.
You may also configure next-hop default gateways.