Cisco Systems OL-4344-01 manual Service Provider Network for Vlan ID Management

Page 4

Chapter 1 About Cisco IP Solution Center

Overview of ISC

VLAN ID Management: ISC allocates VLAN IDs per customer and per Ethernet Service deployed. The service provider can track per Access Domain a particular allocated VLAN ID (per service or per customer or per Access Domain).

ISC keeps track of the VLANs allocated and gives detailed usage information of the VLAN allocated per service, per customer, or per Access Domain.

Access Domain: The Layer 2 Ethernet switching domain attached to a PE defines an access domain. All the switches attached to the PE-POP belong to the access domain (as illustrated in Figure 1-3 on page 1-5). This notion enables the network operator to tie multiple VLAN pools to a single Access Domain, and also allows redundancy with dual PEs in a single Access Domain.

For illustration purpose, let’s assume that a Service Provider has a network such as the one illustrated in Figure 1-2. A customer has two sites (Chicago and New York), and would like to get an Ethernet Wire Service between the two sites.

Figure 1-2 Service Provider Network for VLAN ID Management

Service Provider

network

IP Solution Center

Network Management

subnet

Management PE

Management VPN

Management CE

PE

 

89997

 

Service provider

 

 

CLE-1

MPLS core

 

 

PE

 

 

PE

 

CLE-2

PE-POP 1

PE-POP 2

CE 2

New York

CE 2

Chicago

1.If the network operator has chosen the Auto-Pick VLAN ID option in the service policy (see the “PE Interface Information” section on page 4-11), the network operator must assign an access domain and a VLAN pool for a given PE-POP.

This automatically gives ISC the range of VLAN IDs that are attached to the access domain.

Figure 1-3shows the access domain assigned, with PE-POP 1, CLE 1, and CLE 2 defined within the access domain.

Cisco IP Solution Center, 3.0: MPLS VPN Management User Guide, 3.0

1-4

OL-4344-01

 

 

Image 4
Contents About Cisco IP Solution Center Overview of ISC ISC Network Management SubnetISC Features Service Provider Network for Vlan ID Management Access Domain Assigned Resource PoolsFeatures and Functions Provided in Provisioning with ISC VPN Service Profile-Based ProvisioningRole-Based Access Control Rbac CPE Customer’s and Provider’s View of the Network Customer’s View of the NetworkAbout Provider Edge Routers PEs About Multi-VRF CEsA Multi-VRF CE Providing Layer 3 Aggregation Using Templates to Customize Configuration Files Mapping IPsec Tunnels to Mpls VPNsAuditing Service Requests Uses for the Template FunctionAbout Mpls VPNs VPNs Sharing SitesCharacteristics of Mpls VPNs Intranets and ExtranetsVPN Routing and Forwarding Tables VRFs VRF Implementation Considerations Ip vrf site2 rdCreating a VRF Instance Route Distinguishers and Route TargetsRoute Target Communities CE Routing CommunitiesHub and Spoke Considerations Security Requirements for Mpls VPNs Address Space and Routing SeparationAddress Space Separation Routing SeparationHiding the Mpls Core Structure Resistance to Attacks Securing the Routing ProtocolLabel Spoofing Routing Authentication Securing the Mpls CoreTrusted Devices PE-CE InterfaceSeparation of CE-PE Links LDP AuthenticationConnectivity Between VPNs MP-BGP Security Features Security Through IP Address ResolutionEnsuring VPN Isolation North Bound Interface NBIAPI Functionality Supported NBI Benefits Distributed Load BalancingAPI Approach 11 Simple Flat-Based Server Load Balancing Configuration Four-Tier System Architecture Client tierControl tier