Deploying the V2PC - Cisco · Deploying the V2PC Deploying the V2PC System 11. Specify Launcher...

Deploying the V2PCThis sections contains information on how to deploy the V2P Controller. The following topics are included:

V2PC Deployment Requirements, page 25

V2PC Deployment Sizing, page 25

Deployment Testing Requirements, page 26

Deploying the V2PC System, page 27

Sample .jSON File, page 39

V2PC Deployment Requirements Hardware: UCS B200-M3/M4

Note: All the ESX Host (UCS blade servers should have the same hardware specifications)

Provider: VMware- For VMware Draft Label-Cisco Confidential Draft Label-Cisco Confidential Draft Label-Cisco Confidential setup, refer to:

VMware:

— Hypervisor: Esxi 5.5 (U3a)/Esxi6.0

— VCenter: VCenter 5.5(U3a)/VCenter6.0

V2PC master controller, Repo node should be deployed as 2x large (8 CPU, 32GB RAM, 40GB Disk storage)

ELK node should be deployed as 2x large with 500 GB disks space (8 CPU, 32GB RAM, 500GB Disk storage)

V2PC Deployment SizingThe following tables provides V2P sizing requirements.

Table 1 Sizing Requirements

Type Flavor Number of VMs Comments

V2PC Repo 2xlarge 1

V2PC Master 2xlarge 3 3 V2PC Master nodes required for HA setup

V2PC Launcher 2xlarge 1 Used to bring up/Upgrade V2PC

ELK (Log Server) 2xlarge 1 Configure with min of 500 GB storage

Cisco VSM Medium 1

25

Cisco Systems, Inc. www.cisco.com

Deploying the V2PC

Deployment Testing Requirements

Deployment Testing RequirementsThe minimal functionality testing lab deployments require the following: See also V2PC Test Topology Diagram below.

Launcher (can be turned off after deployment

Repo x 1

Master x 1 (supported production environments require 3 master nodes)

ELK 1

Template x 1

MCE x Scale required for Capture

MPE x Scale required for playback/delivery to CDN/client

AM x1

AppEngines x Scale required to support 3 of MCE, MPE

— IPVS, HAProxy, Redis (2 each required for each Live, VOD, cDVR work flows)

Cisco vDCM Custom (16vCPUs/64GB RAM)

1 one OTT App

Cisco PE Redis Large 2 Required only for SCE (Encryption)

Cisco PE IPVS Large 2 Load Balancer for Cisco PE Workers

Cisco PE HAProxy Large 2 Required only for SCE (Encryption)

Cisco PE Large 2 Based on number of reqs/throughput. This count has to be adjusted

Cisco CE Redis Large 2 Required only for VOD Mediaflow

Cisco CE IPVS Large 2 Required only for VOD Mediaflow

Cisco CE HAProxy Large 2 Required only for VOD Mediaflow

Cisco CE 2xlarge 2 Based on number of channels/profiles. This count has to be adjusted

Table 2 Image Flavors

Flavor Name CPU RAM(GB) Primary Disk

Medium 2 4 40

Large 4 8 40

XLarge 8 16 40

2XLarge 8 32 40

3XLarge 8 64 40

Table 1 Sizing Requirements

Type Flavor Number of VMs Comments

26

Deploying the V2PC

Deploying the V2PC System

Deploying the V2PC SystemTo fully deploy the V2PC, perform the following tasks in order:

Configure VMware. Refer to Configure VMware, page 27

Install Launcher VM from OVA. Refer to Launcher OVA Deployment, page 29

— Copy Repo. iso, coreOS .ova, centos .ova to Launcher

— Run v2p-wizard to generate .json file

Execute launcher bootstrap script to deploy repo, master, elk servers and VM templates based on .json file. Refer to Bootstrap Install, page 34

Verification, Refer to Verification, page 36.

— Verify VM created in VMware

Configure VMwareConfiguring the VMware is required before deploying the V2PC. Follow the instructions below to configure VMware.

Before You BeginRecommended Hardware: UCS Chassis with B200-M3/B200-M4 Blades Servers

ESXi version: ESXi 5.5.0, 6.0

27

Deploying the V2PC


vCenter version: 5.5 (U3a) or 6.0

Procedure to Configure VMware1. Install VMware vCenter.

Note: The installation procedure shown here is for a Windows host. VMware vCenter Server 5.5 (U3a) or 6.0 .iso image is required for the installation.

a. Download the VMware vCenter Server 5.5 (U3a) or 6.0 .iso image.

b. The deployment of VMware vCenter is done by mounting an .iso image. Copy the .iso image into the physical server (linux box) and mount the image using the command shown in the example below:

mkdir /tmp/mntmount -o loop /downloads/VMware-VCSA-all-6.0.0-2656757.iso /tmp/mnt cd /tmp/mnt

c. Copy the extracted files on the Windows host. Alternatively, you can mount the .iso image directly in the Windows host, using a tool like WinISO.

d. Open the vcsa folder and double click VMware-ClientIntegrationPlugin-6.0.0 file to install the setup.

e. Install the vcsa-setup.

2. Configure the vCenter.

a. Login to vCenter using the web browser or vSphere client.

b. Create a Datacenter on vCenter.

Navigate to Home > Inventory > Datastores and Datastore Clusters. Right click on vCenter and select New Datacenter.

c. Create a new VM folder.

Navigate to Home > Inventory > VMs and Templates. Right click on Datacenter and select New Folder.

d. Add a Cluster to the Datacenter.

Navigate to Home > Inventory > Hosts and Clusters. Right click on Datacenter and select New Cluster. Edit the cluster to enable DRS. Go to Cluster Settings > Cluster Features and enable the Turn On vSphere DRS check-box

e. Add Host to the Cluster.

Navigate to Home > Inventory > Hosts and Clusters. Right click on created Cluster and select Add Host.

f. Add Resource Pool to the cluster.

Navigate to Home > Inventory > Hosts and Clusters. Right click on created Cluster and select New Resource Pool.

3. Configure NTP client in ESXi host

a. Login to the vCenter client and select the ESXi host.

b. Navigate to Configuration > Time Configuration > Properties to configure NTP settings and start the NTP service.

c. Enable the Start and stop with host option under Startup policy for NTP Daemon.

Note: NTP has to be in sync with all the ESXi hosts.

28

Deploying the V2PC


Launcher OVA DeploymentThe Launcher has the OVF properties to configure the networking for the VM. To download and deploy the Launcher OVA, follow the instructions below. See the Virtualized Video Processing v3.2 Release Notes for information on image downloads and retrieving the latest files.

1. Download and deploy the Launcher VM in the vCenter infrastructure. Example File Location:

http://vcn-build4/v2pc_release_builds/3.1.0/launcher-ova-2016-08-19_15-33/launcher-3.2.0-8971.ova

Note: The Launcher VM will have only one network interface. This VM should have access to the network where V2P components are deployed. User can add another network interface to this VM, however, this will require manual configuration.

2. Deploy the OVA Template

.

3. Browse to the launcher OVA file location, then click Next.

29

Deploying the V2PC


4. Confirm default OVF settings, then click Next.Cn

30

Deploying the V2PC


5. Accept EULA, then click Next.

6. Provide VM name, then click Next.

31

Deploying the V2PC


7. Select Host, then click Next.

8. Select Datastore, then click Next.

32

Deploying the V2PC


9. Choose Thin Provision, then click Next.

10. Select Network, then click Next.

33

Deploying the V2PC


11. Specify Launcher Details.

Bootstrap InstallFollow the instructions below to install the bootstrap.

1. Access Launcher via SSH.

Default credentials: root/cisco

2. Download/Transfer files to launcher via SCP or wget directly. Copy the Launcher-Dockers, CentOS07, CoreOS, and REPO ISO to the Launcher VM.

Download/Transfer Files Example:

[root@localhost]# wget http://vcn-build4.cisco.com/v2pc_release_builds/3.1.0/v2p-launcher-docker-2016-09-14_14-05/v2p-launcher-docker-b620.tar[root@localhost]# wget http://vcn-build4/v2pc_release_builds/3.1.0/base-ova-latest/centos7-2016-09-14_21-35.zip [root@localhost]# wget http://vcn-build4/v2pc_release_builds/3.1.0/base-ova/coreos_production_vmware_ova.ova[root@localhost]# wget http://vcn-build4/v2pc_release_builds/3.1.0/latest/v2p-repo-3.2.0-10239.iso

3. Unpack the Launcher.tar file

[root@localhost]# tar -xvf v2p-launcher-docker-3.2.0-b600.tar

4. Change to the v2p-launcher-docker directory

[root@localhost]# cd v2p-launcher-docker/

5. Confirm that the docker daemon is running (start if necessary)

34

Deploying the V2PC


#systemctl status docker.service

If necessary:#systemctl start docker.service

6. Run setup.sh to create the docker container.

# ./setup.sh /root/centos7-2016-09-14_21-35.zip /root/coreos_production_vmware_ova.ova /root/v2p-repo-3.2.0-10191.iso

7. Within the container /root/data is a mapped volume from the host/root/v2p-launcher-docker/data directory. V2PC image files will automatically be available in root/data/

[root@267e3834697d ~]# cd /root/data/[root@267e3834697d data]# lscentos7-2016-07-27_10-51.zip clark.json v2p-repo-3.2.0-10233.isocentos7-disk1.vmdk coreos_production_vmware_ova.mf v2p-repo-3.2.0-9063.isocentos7.mf coreos_production_vmware_ova.ovf v2p-repo-3.2.0-9080.isocentos7.ovf coreos_production_vmware_ova_image.vmdk v2pcssh1.key

Note: Files may be copied to this directory on the host to be made available via root/data in the container.

8. Execute the provisioning script from the /root/ directory

[root@267e3834697d ~]# cd /root[root@267e3834697d ~]# ./v2p-provision.sh

9. Execute the v2p-wizard to define the deployment environment.

[root@267e3834697d ~]# ./v2p-wizard====== Infra Provider for V2PC Platform ======

a. Enter Infrastructure Provider:

[choices: [(0, 'vmware'), (1, 'openstack')]]

[default: vmware]: 0

The v2p-wizard is an interactive script that allows selection of items using the corresponding # options. In this example, entering 0 will choose vmware.

This wizard dynamically modifies the v2p-cluster.json which may also be manually edited in a text editor.

10. Answer remaining questions with specifics for Vcenter.

11. Run bootstrap using the .json file created by the wizard.

[root@267e3834697d ~]# cd /opt/cisco/v2p/v2pc/python/vm_manager/bootstrap/ [root@267e3834697d ~]# python bootStrapv2pMulti.py –c /opt/cisco/v2p/v2pc/python/vm_manager/wizard/v2p-cluster.jsonopt/cisco/v2p/v2pc/python/vm_manager/wizard//v2p-cluster.json /config file /opt/cisco/v2p/v2pc/python/vm_manager/wizard//v2p-cluster.jsonLog file /var/log/opt/cisco/v2pc/v2p-bootstrap.log

This process will take 30-40 minutes depending on how many nodes must be deployed in Vmware.

Note: Vcenter will also display each node as they are provisioned.

12. To observe the progress of the cluster deployment, start another bash session with the container using the following command (s)

(host)#docker ps

35

Deploying the V2PC


13. While this is executing, perform the next steps to monitor the log file.

a. Open a separate SSH session to the Launcher VM, locate the docker container, then access the container shell and tail the install log.

[root@v2p-launcher ~]# docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES267e3834697d engci-docker.cisco.com:5007/v2p-launcher:3.2.0-b600 "/bin/bash" 26 minutes ago Up 26 minutes distracted_saha[root@v2p-launcher ~]# docker exec -it 267e3834697d /bin/bash[root@267e3834697d ~]# tail -f /var/log/opt/cisco/v2pc/v2p-bootstrap.log2016-09-22 23:17:51,864 bootStrapv2pMulti.py L155(108)[INFO]:image section for this pod {u'datastore': u'FreeNas-iScsi', u'imgTag': u'cisco-centos-7.0', u'name': u'v2p-base-template10233', u'packages': [{u'src': {u'format': u'iso', u'local_file': u'/root/data/v2p-repo-3.2.0-10233.iso', u'remote_file': u'/home/v2pc/repo-3.1.0-9999.iso'},

b. Moniotor the Vcenter resource pool as each VM is created.

14. The following output will appear when bootstrap is complete.

==== ATTENTION PLEASE SAVE THE BELOW V2PC FILES ====

SSH private key: /root/.ssh/v2pcssh.keyV2PC Service Manager(SM) token file: /etc/opt/cisco/mos/public/token.json***output omitted***SUCCESS: V2PC Cluster creation completed.Login to the V2PC GUI https://<master_ip>:8443 for further configuration.To configure a V2PC Provider using default values, execute the below command.>>>cd /opt/cisco/v2p/v2pc/python/vm_manager/bootstrap>>>python infra_generator.py create_default -m <SM leader node IP>[root@267e3834697d bootstrap]#

15. Save the files. It is recommended to save the files referenced above on a management station. The container may not be active for retrieving these later without manually starting or resuming this specific container ID on the docker/launcher host.

VerificationAfter successfully executing the bootstrap install script, the following nodes are created in VCenter:

Repo x 1

Master x 1 (x3 for HA)

Elk x 1

CentOS Template x 1

CoreOS Template x 1

To verify that you can log into the V2P Controller, perform the steps below:

1. Open a web browser and enter https://<IP_or_name_of_Master:8443

The V2P controller login screen appears.

2. Enter the default credentials: admin/default to log into the V2P Controller.

36

Deploying the V2PC


The dashboard should be displayed.

Existing Deployment LimitationsThe following list summarizes current limitations for V2PC deployment.

Not tested in deployments where the datastore is an external store, such as NFS. In this scenario, the datastore names could be the same on all of the hosts.

Not tested in deployments where networking is set up using distributed vSwitch and port groups.

Hosts in maintenance mode are not ignored.

The region name is currently hard-coded to region-0.

V2PC collects only one zone/POD information.

If an ESX host has multiple datastores, the script picks up only one datastore. To address this issue, edit the JSON file manually.

The VM folder is not verified to be of the VM and Template type.

Importing the VMP BundleWith V2PC Release 3.2.3, the following VMP applications and workflows are no longer contained within the V2PC ISO:

cisco-ce

cisco-pe

cisco-am

cisco-sce

cisco-mfc

37

Deploying the V2PC


cisco-vod-mfc

Before creating any of these applications or workflows in V2PC, you must import the VMP Bundle installation .tar file.

To do this:

1. Log in to the V2PC Repository VM via SSH as user v2pc.

2. Download the appropriate VMP Bundle from the Cisco software download page and place it in a temporary folder, as shown in the following example:

$ wget <cisco-software-download-page-URL>/v2pvmp-bundle-2.8.1-20170211.tar \-O /tmp/vmpBundle/v2p-vmp-bundle-2.8.1-20170211.tar

3. Import the VMP Bundle as follows:

$ /opt/cisco/v2p/v2pc/python/v2pPkgMgr.py --import --sourcebundle /tmp/vmpBundle/v2p-vmpbundle-2.8.1-20170211.tar

Processing application upgrade bundle /tmp/vmpBundle/v2p-vmp-bundle-2.8.1-20170211.tar ...... etc ...

Successfully processed application upgrade bundle /tmp/vmpBundle/v2p-vmp-bundle-2.8.1-20170211.tar

4) Continue with Next Steps, page 38.

Next StepsOnce deployed, further configuration is performed via the V2P Controller GUI. See the Cisco Virtualized Video Processing Controller (V2PC) User Guide for details.

38

Deploying the V2PC

Sample .jSON File

Sample .jSON File{ "regions": ["region-0"], "region-0": { "name": "region-0", "type": "primary", # for secondary region use "worker" "description": "", "address": "", "city": "", "state": "", "country": "" }, "pods": ["pod1"], # POD is equivalent to a Zone "pod1": { "provider": "openstack", # [ openstack | vmware ] "controllerIP": "172.20.x.c", # VMware: IP/hostname of vCenter server (version 5.5 u3a, > 6) Openstack: IP/hostname of the controller node "protocol": "http|https", # Openstack: Controller URL protocol "apiVersion": "v2.0", # Openstack: Controller api version "port": "5000", # Vmware: vCenter port (default 443) Openstack: Controller node port (default 5000) "tenant": "admin", # Openstack: tenant name VMware: not applicable "user": "admin", # VMware: user name for vCenter server Openstack: user name for the token authentication "password": "cisco123", # VMware: password for vCenter server Openstack: password for token authentication "datacenter": "Datacenter_SJC", # VMware: Datacenter name of vCenter Openstack: Use any name. eg: dc1 (don't leave empty) will be used in node fqdn "cluster": "campus_1", # VMware: cluster name on vCenter vCenter --> Datacenter -- > Cluster Openstack: Availability zone "resourcePool": "rp1", # VMware: resource pool name on vCenter vCenter --> Datacenter --> Cluster --> Resource Pool "templateFolder": "v2p_folder", # VMware: vCenter --> Inventory --> VMs and Template (View) Create a New Folder under your datacenter. Give the name of this new folder here. Openstack: not applicable "vmFolder": "v2p_folder", # Same as templateFolder. Don't leave it blank for VMware Openstack: not applicable "datastore_host": "", # Optional ENG use only "datastores": [{"name": "datastore01", "folder": "v2p_folder"}], # VMware: Create one entry for each host in the cluster. The name should be the datastore name on that host. The folder name is same as vmFolder above.

39

Deploying the V2PC

Sample .jSON File

# Openstack: Not used. Currently use some dummy values "domain": "v2pc.com", # Domain name "net_mgmt": "vlan-1722", # VMware: The vswitch label for management network Openstack: The openstack network name for management network "ntp": ["171.68.38.65"], # List of NTP servers "region": "region-0", # Region this zone belongs to "images": [ # List of base images/templates { "vendor": "cisco", # vendor name "name": "v2p-centos-7", # VMWare: template name Openstack: glance image name. This should be same as vmName in template_node "imgTag": "cisco-centos-7.0.0", # Unique tag name format <vendor>-<os>-<version> The image tag should be same for all nodes in this JSON file "storeName": "datastore01", # name from datastores list above The image would be uploaded to that datastore "provider": "pod1", # Zone information for this image "repoIP": "172.20.x.r", # V2P Repo IP "repoPort": "5001", # Do not change "packages": [ { "type": "system", # Do not change "version": "3.2.0", # V2P software version "src": { "format": "iso", "local_file": "/sw/v2p/images/v2p-repo-3.1.0-7815.iso", # Location of V2P software ISO file "remote_file": "/home/v2pc/v2p-repo-3.1.0-7815.iso" # use /home/v2pc/<repo name> as above repo file name should be the same } } ], "_systemRepoListComment": "Repo list will be auto populated" # Do not change } ] }, "compute_nodes": [ { "vm_type": "template", # Do not edit "deployment": "pod1", # Zone to deploy the image/template "vmName": "v2p-centos-7", # Name of template/image. Should be same as image->name "hostname": "template", # Do not edit "vmSourcePath": "/sw/v2p/images/", # Directory where V2P base image OVA=(mf, ovf, vmdk) "vmSourceName": "centos7-disk1.vmdk", # For VMware: specify the ovf file Openstack: specify the vmdk file "datastore": "datastore01", # name of store in datastores from POD section "imgTag": "cisco-centos-7.0.0", # Same as in image->imgTag "imageDFormat":"vmdk", # Do not edit "imageCFormat":"bare" # Do not edit }, { "vm_type": "master", "deployment": "pod1", "dns": [ # DNS IP List

40

Deploying the V2PC

Sample .jSON File

"127.0.0.1", The first IP should always be 127.0.0.1 "171.70.168.183" ], "firstMasterHost": "172.20.207.82", # IP of the first master node address. Used in master HA. "templateName": "v2p-centos7", # should match the node->template->vmName "imgTag": "cisco-centos-7.0.0", # should match the image->imgTag "vmName": "master01.node.datacenter.consul", # Could replace the datacenter with your datacenter name not required to change it. "hostname": "master1", # Any valid hostname. not required to change this name. "fqdnName": "172.20.x.m1", # IP of the master. In case of NAT this is an external IP "privateFqdnName": "172.22.x.m1", # IP of the master. In case of NAT this in an internal IP In NAT the internal IP is the one assigned to the VM If non NAT'ed environment these two IPs are the same "isMaster": true, # Do not edit "numOfMaster": 1, # For single node use "1", for 3 node HA use "3" "flavor":"m1.medium", # VMware: not used Openstack: root filesystem size is resized as per the flavor defination. "numCPU": 4, # CPU cores. Do not edit. Only used by Vmware "memory": 8192, # Memory in MB. Currently set to 8GB. Do not edit. Only used by Vmware. "disk": 0, # Storage in GB. # VMware: The primary disk is 40GB fixed. The second disk block device of size GB is attached to the VM. User needs to make use of this block device. (/dev/sdb or /dev/vdb) Openstack: not applicable "datastore": "datastore01", # datastore name in POD->datastores->name "mosDNS": [ # This is only used by MOS Application { This is an external DNS server which is not managed by V2PC. "ip": "192.2.0.25", # IP reachable from master node "hostname": "extdns", # not used. Keep it "domain": "mosdomain.com", # This domain name should be different from V2PC domain POD->domain "key": "EA07/q61zERW7tziZupaUw==", # edit the key as per your deployment "algo": "hmac-md5" # Do not edit. } ], "networkInterfaces": [ { "dhcpEnabled": false, # Do not edit. Openstack: We use DHCP but use fixed IP. VMware : We use static IP

41

Deploying the V2PC

Sample .jSON File

"subnet": "vlan-1722-subnet", # Openstack: openstack subnet name/UUID VMware: subnet mask eg: 255.255.0.0 "net_type": "net_mgmt", # Do not edit "ip": "172.20.x.m1", # IP address to be assigned to this node "gateway": "172.20.x.g1", # VMware: Specify the gateway IP Openstack: leave it blank "hasDefaultGW": true, "label": "vlan-1722" # VMWare: vswitch label name Openstack: openstack network name/UUID } ], "artifactoryBaseUrl": "", # Do not edit. "repositoryVersion": "" # Do not edit. },{ # V2PC Software repository node Same instructions as master node. Only highlighting repo specific things "vm_type": "repo", # V2PC Software repository node "deployment": "pod1", # node to be deployed in this zone/pod "dns": [ "127.0.0.1", "171.70.168.183" ], "firstMasterHost": "172.20.207.82", # IP of the first master node "templateName": "v2p-centos7", # same as node->template->vmName "imgTag": "cisco-centos-7.0.0", # same as image->imgTag "vmName": "v2p-repo", # VM Name in VMware and Openstack "hostname": "v2p-repo", "fqdnName": "172.20.x.r1", # IP of repo "privateFqdnName": "172.22.x.r1", "isMaster": false, # Do not edit "numOfMaster": 0, # Do not edit "flavor":"m1.medium", "numCPU": 4, # 4 cores "memory": 8196, # 8GB "datastore": "datastore01", # should match pod->datastores[]->name "networkInterfaces": [ # Same as networkInterfaces section in master node { "dhcpEnabled": false, "subnet": "vlan-1722-subnet", "net_type": "net_mgmt", "ip": "172.20.x.r1", # IP address of repo VM "gateway": "172.20.x.gr", "hasDefaultGW": true, "label": "vlan-1722" } ], "artifactoryBaseUrl": "", # Do not edit "repositoryVersion": "", # Do not edit "repo_iso": "/sw/v2p/images/v2p-repo-3.1.0-7815.iso", # location of V2P ISO file "outgoing_https_proxy": "http://proxy.esl.cisco.com:8080/" # Outgoing proxy if required from Repo VM. only required if you need to download pkgs from internet on Repo VM. },{ "vm_type": "elk", # V2P ELK (Elastic-Logstash-Kibana) node # Same instructions as above. Only highlight ELK specific configs "deployment": "pod1", "dns": [ "127.0.0.1", "171.70.168.183"

42

Deploying the V2PC

Sample .jSON File

], "firstMasterHost": "172.20.x.m1", # IP of the first master node "templateName": "v2p-centos7", "imgTag": "cisco-centos-7.0.0", "vmName": "v2p-elk", "hostname": "v2p-elk", "fqdnName": "172.20.x.e1", # IP address of ELK node. Should match the networkInterfaces IP "privateFqdnName": "172.20.x.e1", "isMaster": false, "numOfMaster": 0, "flavor":"m1.medium", "numCPU": 4, "memory": 8096, "datastore": "datastore01", "networkInterfaces": [ { "subnet": "vlan-1722-subnet", "net_type": "net_mgmt", "ip": "172.20.x.e1", "gateway": "172.20.207.65", "hasDefaultGW": true, "label": "vlan-1722" } ], "repositoryVersion": "", # Do not edit "npm_repository": "", # Do not edit "outgoing_https_proxy": "" # Do not edit } ]}

43

Deploying the V2PC

Sample .jSON File

44

Deploying the V2PC - Cisco · Deploying the V2PC Deploying the V2PC System 11. Specify Launcher...

Documents

Transcript of Deploying the V2PC - Cisco · Deploying the V2PC Deploying the V2PC System 11. Specify Launcher...