Juniper Cloud Customer Certification Labs (Cloud CCL)

vMX consists of two VMs:

• vCP (orvRE)
  • 2GB RAM, 1 vCPU
• vFPC (orvPFE)
  • 8GB RAM, 3vCPU
  • It uses E1000 for the management functions (fxp0 and bridge between CP/FPC)
  • It uses VMXNET3 for traffic
  • Traffic interfaces are: ge-0/0/0 .. ge-0/0/7

Currently, these JUNOS software releases are available:

vSRX consists of one VM:

• 4GB RAM, 2 vCPU
• Network interfaces
  
  • It uses VMXNET3 for the management functions (fxp0)
  • It uses VMXNET3 for traffic
  • Traffic interfaces are: ge-0/0/0 .. ge-0/0/7

Currently, these JUNOS software releases are available:

Resource vQFX consists of one VM (vRE):

• 1GB RAM
• 1 vCPU
• 5 network interfaces for traffic
  • vNIC uses E1000
  • Names of traffic interfaces: em3 .. em7

Currently, this JUNOS software release is available:

Note: This is not officially supported by Juniper and is an experimental VM for your testing in Cloud-CCL. We'll not be able to resolve issues/provide patches in vQFX.

This resource consists of one VM with these software packages installed:

• Junos Space Network Management Platform, Release 16.1R1.7
• Junos Space Security Director and Integrated Log Collector, Release 16.1R1.1874
• Junos Space Network Director, Release 3.0R1
• Junos Space Service Now / Service Insight, Release 16.2R1.4

VM is configured with the following resources:

• RAM 40GB
• CPU 4 cores
• HDD: 250GB + 500GB
• NIC: 4x E1000, all on the same network

DMI Schema files are already installed. If you need more information around this, check this KB article.

 Known issues:

• Network Director might not be able to manage the devices that do not show correct serial number (some vQFX)
• Network Director might not be able to manage the devices that do not show correct model number (some vMX)

Junos Space has REST API (doc page is here) that can be used to automate tasks or build a demo.

You need this resource only if you want Spirent ports in your reservation. You do not need more than one resource of this type in your reservation.

This resource (SpirentGUI) will automatically find and manage the Spirent ports in this reservation, no need to connect those ports to SpirentGUI (no need to draw connections).

To use this resource, you need to connect over RDP protocol to VM running Spirent GUI:

• You can use RDP client on your computer to connect to IP address of that VM, or
• Use RDP session provided within Cloud CCL directly from your web browser

Once you have RDP connection open, you should see Spirent Session Manager application running with only one session listed, pointing to Spirent Lab Server appliance (the other VM in this resource, dedicated to your reservation). Double click on that session to start Spirent GUI Client. After Spirent GUI Client starts, you will see a list of the reserved ports and you will be able to use them.

These are the tools installed on this VM that you might find useful:

• Wireshark
• WinSCP
• Filezilla FTP server and client

This resource has one VM, capable of sending and receiving traffic. It has two interfaces:

• one management interface (IP address of the resource, shown in canvas), and
• one traffic interface for sending/receiving test traffic

For each Spirent traffic port, you want in your reservation, you need to add one of these resources. These resources are controlled by Spirent GUI Client, not by CLI - do not try to connect to them directly.

From the product web page "JSA Virtual Appliance is a virtualized security information and event management (SIEM) system that consolidates log source event data from thousands of devices, endpoints, and applications distributed throughout a network".

JSA is installed on VM with the following characteristics:

• 24GB RAM, 4 vCPU
• 100GB vHDD
• NICs
  • eth0 for management uses VMXNET3
  • eth1-eth4 for data-traffic, use E1000

Currently, these software releases are available:

Add abstract resource "JSAVM" to your topology/environment and reserve it. In the canvas of the active reservation, hover-over the JSA resource (triangle pointing down) and click "Web GUI" command. A new tab will be opened in your browser with the web interface to JSA.

Here are some useful links:

• JSA Product info
• Datasheet and Technical Docs
• JSA Release Notes for 2014.8.R7
• JSA API Guide
• JSA Solutions Brief

Two resources, typically combined together in the topology. To use these in your topology:

• add the abstract resources NS-App and NS-vRR (one of each)
• connect: NS-App interface eth1 (172.16.16.1/30) and NS-vRR interface em1 (172.16.16.2/30)

Details of NS-App:

• VM based on CentOS with NorthStar 3.1.0 application installed
• 6GB RAM, 2 vCPU, 80GB HDD
• 6 Ethernet interfaces
  • eth0 - for management (please do not change)
  • eth1 - dedicated for direct connection to NS-vRR
  • eth2-eth5 for connecting to other resources in the reservation (e.g. routers)
• Use WebGUI to manage this resource, ports 8091 (http) and 8443 (https)

Details of NS-vRR:

• VM is based on vMX (only RE, no PFE)
• 8GB RAM, 1 vCPU, 25GB HDD
• 6 Ethernet interfaces
  • em0 - for management (please do not change)
  • em1 - dedicated for direct connection to NS-App
  • em2-em5 for connecting to other resources in the reservation (e.g. routers)
• JUNOS 17.2R1.13

This is based on Ubuntu 14.04 LTS (if need be, you can upgrade to newer versions). In addition to the management interface (eth0) it has 8 Ethernet interfaces (eth1-eth8) that can be used to send/receive the traffic by connecting them to other resources in your reservation.

This is based on Ubuntu 16.04 LTS and is intended to help Cloud CCL users with junos provisioning & test automation.

It’s got Juniper’s Robot-Python based test-automation framework pre-installed, along with leading automation tools like Ansible, Juniper PyEZ & JSNAPy.

You can make use of ‘Cloud CCL Orchestrator’ (based on Jenkins) to execute automation scripts & view test-result reports, trends & analytics from the GUI. In addition, there are automation scripts that are provided to help you in day-to-day automation — backup/ restore configuration, install config, verify config etc.

If you already have python/Ansible/robot-based scripts, you can import them to this VM and run them against your virtual topology the same way you would do against physical routers and similarly, export scripts from this environment onto your production.