|
|
VPNSC: MPLS Solution focuses on provisioning, auditing, and monitoring the links between the customer's routers through the providers's network. This product deals only with the provider's edge routers and the customer's edge routers. A customer edge router (CE) is connected to a provider edge router (PE) in such a way that the customer's traffic is encapsulated and transparently sent to other CEs, thus creating a virtual private network. The VPNSC: MPLS Solution provisioning engine accesses the configuration files on both the CE and PE to compute the necessary changes to those files that are required to support the service on the PE-CE link.
As illustrated in Figure 1-1, Cisco requires that the VPNSC: MPLS Solution software is installed on its own dedicated system and Cisco IP Manager is installed on its own system, with the two workstations connected on a LAN. Note that Oracle 8.0.5 is installed on the Cisco IP Manager workstation. This arrangement comprises the network management subnet.
This chapter describes the system recommendations for the Cisco VPNSC: MPLS Solution workstation, as well as the Cisco IP Manager and NetFlow Collector systems. This chapter also tells you how to mount a locally attached or remotely attached CD-ROM drive.
The system recommendations are organized in the following categories:
The system recommendations for the VPNSC: MPLS Solution workstation are as follows:
| Number of CEs | Workstation | RAM | Disk Space |
Up to 500 | Minimum: Sun Ultra 60 (1 CPU) Production: Sun Enterprise 250 (2 CPUs) | 1 GB | 20+ GB |
500 to 1,500 | Minimum: Sun Ultra 60 (2 CPUs) Production: Sun Enterprise 250 (2 CPUs) | 1 GB | 20+ GB |
1,500 3,000 | Sun Enterprise 450 (4 CPUs) | 1 GB | 20+ GB |
Over 3,000 | Sun Enterprise 450 (4 CPUs) | 1 GB | 20+ GB |
Currently, the VPNSC: MPLS Solution software can run only under Solaris 2.6. The installation terminates if the operating system is not Solaris 2.6.
 |
Caution When you install Solaris 2.6, be sure to choose either the Developer System Support or the Entire Distribution software groups. Do not choose the End User System software group. The Developer System Support and Entire Distribution software groups contain the software required for a correct operating system installation (such as the SUNWbtool and SUNWsprot packages). |
If you encounter difficulty in the Solaris 2.6 installation, see the "Troubleshooting the Solaris Installation" section.
 |
Note You must install CIPM on a separate machine. The CIPM workstation must be connected on a LAN to the MPLS VPN Solution workstation. |
For information on how to install CIPM, refer to the Cisco IP Manager (Lite) User's Guide: Version 2.0 distributed with the product. This guide also contains CIPM 2.0 installation information: refer to "Installing and Starting Cisco IP Manager 2.0."
The system recommendations for the CIPM workstation are as follows:
FlowCollector generates output files containing aggregated data. These files require additional disk space; the exact amount of disk space required depends on the flow arrival rate, collection interval, number of aggregation schemes specified, binary versus ASCII data file types, use of compression, and data file retention policies.
|
Note Cisco recommends that each PE in the service provider network have a LAN connection to a NetFlow Collector device. |
The entire installation process is explained in detail in the NetFlow FlowCollector Installation and User Guide in Chapter 2, "Installing and Configuring FlowCollector." Installation troubleshooting information is located in the NetFlow FlowCollector Installation and User Guide in Appendix A, "Troubleshooting FlowCollector."
For details on setting up NetFlow accounting in VPNSC: MPLS Solution software, refer to "MPLS VPN NetFlow Accounting" in Chapter 6 of the Cisco VPN Solutions Center: MPLS Solution Provisioning and Operations Guide.
For Provider Edge Routers (PEs) and Customer Edge Routers (CEs) in the service provider network, Cisco recommends the following:
host# mkdir /cdrom
|
Note When the CD-ROM drive is already mounted or you are running the volume manager with Solaris on a Sun SPARC system, this mounting step is not necessary. |
Step 2 Mount the CD-ROM drive on the mount point.
Step 3 For Solaris (when not running Volume Management), issue the following command:
host# /usr/sbin/mount -rF hsfs device_name /cdrom
where device is the name of the locally attached CD-ROM drive. For example, to mount the CD-ROM from the local drive named /dev/dsk/c0t6d0s0, specify:
host# /usr/sbin/mount -rF hsfs /dev/dsk/c0t6d0s0 /cdrom
Prior to mounting the CD-ROM drive from the remote host, the device must be made accessible. The following procedures are performed on the remote system where the CD-ROM drive is attached.
To export the CD-ROM drive from a remote Solaris host, follow these steps:
host# /usr/lib/nfs/nfsd 8host# /usr/lib/nfs/mountd
Step 2 Issue the following command to share the mount point from the remote system:
host# /usr/sbin/share -F nfs -o ro /cdrom/vpnsc_dir
Step 3 Verify the remote host is exporting the mount point. The listing produced by this command should include the /cdrom mount point.
host# /usr/sbin/share
Step 4 On the client machine, verify the mount point on the remote host:
host# /usr/sbin/showmount -e remote_server | grep cdrom
where remote_server is the name of the remote host where the CD-ROM drive is mounted.
Step 5 On the client machine, mount the remotely installed CD-ROM device:
host# /usr/sbin/mount remote_server:/cdrom local_mount_point
where local_mount_point is the mount point on the client machine for the remotely mounted CD-ROM drive.
Posted: Tue Sep 12 15:42:41 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.