Virtual Instances SAP

Virtual Instances SAP

<< Click to show table of contents >>

Virtual Instances SAP

VPN Direct SAP	Previously users could only create SAP under Physical/Standard Ports from within a VPN. These SAP were visible in the VPN and in the routing table once a user routed through a Standard port with SAP. Standard ports support multiple SAP allowing for multiple VPN use of MPLS Access Ports. This model can still be used for VLL and VPLS depending on their requirements.
VPN Direct SAP Model
Example VPN Direct SAP
Example VPN Direct SAP Routing

VI SAP	If using Virtual Instances users can now allocate SAP to Virtual Sub-Ports and Standard Ports. This allows users to more accurately model the Virtual Sub-Port structure found on MPLS routers/switches. Virtual-ports are visible across the system and allow for more comprehensive reporting and routing. SAP defined in VI have a 1:1 relationship with their Standard or Virtual Sub-Port.
Virtual-Sub Port SAP Model

Comparison

Service Access Point properties and characteristics comparison.

SAP Type	VPN SAP Standard Port	VI SAP Virtual Sub-Port
Port Visibility	Physical Only	Physical and Logical
Port Kind	MPLS Access	MPLS Access Note! Parent Standard Port cannot be MPLS Access. Recommend VLAN Trunk
Name	1/1/0:* (Encap-Type 1inQ) 1/1/0:* (Encap-Type QinQ) 1/1/0 (Undefined) 1/1/0:* (Null) s/n/p:OuterTag.InnerTag Where S = Series of the port N = Slot of the port P = auto-incremented number under the parent VPN or VI.	Derived from Port
Encap-Type	User Defined	Derived from Port
Location	Derived from Port	Derived from Port
MUX	Derived from Port	Derived from Port
Card	Derived from Port	Derived from Port
Qos	User Defined	User Defined
VLAN Ingress Inner (1inQ)
VLAN Net	User Defined	Derived from Port
TAG/VID	User Defined	Derived from Port
Translate To	User Defined	User Defined
VLAN Ingress Outer (QinQ)
VLAN Net	User Defined	Derived from Port
TAG/VID	User Defined	Derived from Port
Translate To	User Defined	User Defined

Example VI Virtual Sub-Port SAP

67A54A~1_img25