Cisco Systems OL-4344-01 manual Simple Flat-Based Server Load Balancing Configuration

Page 30

Chapter 1 About Cisco IP Solution Center

Security Requirements for MPLS VPNs

•The Processing server can be added dynamically. The Watchdog will discover their existence when you start up ISC.

•Each Collection server is responsible for a set of collection zones. Each zone has one Collection Server.

•Both Processing servers and Collection servers failover to the Master server automatically.

•Each device belongs to a zone, but a device can be relocated to a different zone as needed.

If the service provider has implemented one or more Processing servers or Collection servers, all the servers—Master, Processing, and Collection servers—are listed in the Administration Control Center.

The Remote server can be installed from the Control Center as well.

All Remote servers are monitored by Watchdogs. Remote Watchdogs report statistics to the Master Watchdog. You can start and stop all the servers from the Administration Control Center. Logs are available for viewing in real time.

Figure 1-11shows the topology for a simple flat-based load-balancing configuration.

Figure 1-11 Simple Flat-Based Server Load Balancing Configuration

Service Provider

network

Load Balancer 192.168.0.10 VIP: 192.168.0.200

Layer 2 switch

Web servers

 

192.168.0.100

 

192.168.0.101

93003

192.168.0.102

Figure 1-12 on page 1-31shows a flat-based route-path server load balancing configuration with redundancy built into the topology.

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

1-30

OL-4344-01

 

 

Page 29 Page 31
Image 30
Page 29 Page 31
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 Address Space Separation Security Requirements for Mpls VPNsAddress Space and Routing Separation Routing SeparationHiding the Mpls Core Structure Resistance to Attacks Securing the Routing ProtocolLabel Spoofing Trusted Devices Routing AuthenticationSecuring the Mpls Core PE-CE InterfaceLDP Authentication Separation of CE-PE LinksConnectivity Between VPNs MP-BGP Security Features Security Through IP Address ResolutionNorth Bound Interface NBI Ensuring VPN IsolationAPI Functionality Supported Distributed Load Balancing NBI BenefitsAPI Approach 11 Simple Flat-Based Server Load Balancing Configuration Four-Tier System Architecture Client tierControl tier
Top Page Image Contents