Cisco Systems OL-4344-01 manual Resource Pools, Access Domain Assigned

Page 5

Chapter 1 About Cisco IP Solution Center

Overview of ISC

Figure 1-3 Access Domain Assigned

Service Provider

network

IP Solution Center

Network Management

subnet

Management PE

Management VPN

Management CE

PE

 

89998

Access domain

Service provider

 

CLE-1

 

MPLS core

 

PE

PE

 

 

 

CLE-2

PE-POP 1

PE-POP 2

CE 2

New York

CE 2

Chicago

2.All the network elements have been discovered during the Autodiscovery process, as well as the network topology (connectivity between sites).

3.The service operator wants to deploy an Ethernet over MPLS service from Chicago to New York.

4.Using ISC’s GUI, the service operator needs to select the From and To ports, and the appropriate service policy that allows VLAN IDs in the Access Domain to be picked automatically.

5.ISC allocated a VLAN ID for Chicago and a VLAN ID for New York. (Both sites belong to the same customer.)

6.VLAN IDs are allocated and assigned.

Resource Pools

ISC enables multiple pools to be defined and used during deployment operations. The following resource pools are available:

VLAN ID pool: VLAN ID pools are defined with a starting value and a size of the VLAN pool. A given VLAN ID pool can be attached to an Access Domain. During the deployment an Ethernet Service (EWS, ERS for example), VLAN ID can be auto-allocated from the Access Domain’s VLAN pools. This gives the Service Provider a tighter control of VLAN ID allocation.

IP address pool: The IP address pool can be defined and assigned to regions.

Multicast pool: The Multicast pool is used for Multicast MPLS VPNs.

Route Target (RT) pool: A route target is the MPLS mechanism that informs PEs as to which routes should be inserted into the appropriate VRFs. Every VPN route is tagged with one or more route targets when it is exported from a VRF and offered to other VRFs. The route target can be considered a VPN identifier in MPLS VPN architecture. RTs are a 64-bit number.

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

 

OL-4344-01

1-5

 

 

 

Image 5
Contents About Cisco IP Solution Center ISC Network Management Subnet Overview of ISCISC Features Service Provider Network for Vlan ID Management Resource Pools Access Domain AssignedVPN Service Profile-Based Provisioning Features and Functions Provided in Provisioning with ISCRole-Based Access Control Rbac CPE Customer’s View of the Network Customer’s and Provider’s View of the NetworkAbout Multi-VRF CEs About Provider Edge Routers PEsA Multi-VRF CE Providing Layer 3 Aggregation Mapping IPsec Tunnels to Mpls VPNs Using Templates to Customize Configuration FilesUses for the Template Function Auditing Service RequestsVPNs Sharing Sites About Mpls VPNsIntranets and Extranets Characteristics of Mpls VPNsVPN Routing and Forwarding Tables VRFs Ip vrf site2 rd VRF Implementation ConsiderationsRoute Distinguishers and Route Targets Creating a VRF InstanceCE Routing Communities Route Target CommunitiesHub and Spoke Considerations Address Space and Routing Separation Security Requirements for Mpls VPNsAddress Space Separation Routing SeparationHiding the Mpls Core Structure Securing the Routing Protocol Resistance to AttacksLabel Spoofing Securing the Mpls Core Routing AuthenticationTrusted Devices PE-CE InterfaceConnectivity Between VPNs LDP AuthenticationSeparation of CE-PE Links Security Through IP Address Resolution MP-BGP Security FeaturesAPI Functionality Supported North Bound Interface NBIEnsuring VPN Isolation API Approach Distributed Load BalancingNBI Benefits 11 Simple Flat-Based Server Load Balancing Configuration Client tier Four-Tier System ArchitectureControl tier