IP/MPLSView Integration Module for Junosphere Lab Technical Documentation

The Integration Module for Junosphere is comprised of two files: a script file and a jar file. Both files are installed on the WANDL IP/MPLSView server machine. You execute the script file from the command line prompt.

Before beginning the conversion process, you should have already completed modeling and simulating the network model in IP/MPLSView and are ready to create the associated Junosphere VMM topology file. A more detailed description of the modeling and simulation process in IP/MPLSView is beyond the scope of this document. See the relevant WANDL documentation for assistance.

You should have the following input data:

At the command line, enter the following command to display the usage description:

$ ./[Usage] ./ spec-dir runcode original-config-file-dir output-dir

spec-dir is the directory where the existing WANDL data files are located (spec, muxloc, bblink, and others).

runcode is the file runcode of the data set to be converted. For example, the runcode for data files after importing configuration files is auto.

original-config-file-dir is the directory where the corresponding router configuration files are located.

output-dir is the directory where the topology.vmm, intfmapping.vmm, and new config files are saved.

For example:

wandl@opteron:~/junosphere$ ./ sep23 auto configs outputdir

When you run the command line above, the conversion process will import the WANDL data files in the directory sep23 with the runcode auto. It will also import the router configurations stored in the directory configs.

Successful completion of the conversion process creates a Junosphere VMM topology file (topology.vmm) and an interface renaming mapping file (intfmapping.vmm) under the outputdir directory. The modified configuration files are saved to the same outputdir directory as well as to the folder configset.

Additionally, a Junosphere-ready file (WANDL.tar.gz) is created in the directory outputdir. The file can be uploaded to Junosphere. The file consists of the following:

Sample topology.vmm file:

config "config" {display "NULL";vm "E_CE11" {hostname "E_CE11" ;VJX1000_LATESTinterface "em0" { EXTERNAL; };interface "em1" { bridge "private14"; };install "ENV(HOME)/active/configset/E_CE11.conf" "/root/junos.conf";};vm "E_CE12" {hostname "E_CE12" ;VJX1000_LATESTinterface "em0" { EXTERNAL; };interface "em1" { bridge "private11"; };install "ENV(HOME)/active/configset/E_CE12.conf" "/root/junos.conf";};vm "E_P5" {hostname "E_P5" ;VJX1000_LATESTinterface "em0" { EXTERNAL; };interface "em1" { bridge "private1"; };interface "em2" { bridge "private4"; };interface "em3" { bridge "private12"; };install "ENV(HOME)/active/configset/E_P5.conf" "/root/junos.conf";};vm "E_P6" {hostname "E_P6" ;VJX1000_LATESTinterface "em0" { EXTERNAL; };interface "em1" { bridge "private1"; };interface "em2" { bridge "private2"; };interface "em3" { bridge "private10"; };install "ENV(HOME)/active/configset/E_P6.conf" "/root/junos.conf";};

Sample intfmapping.vmm file:

E_CE11 {ge-6/0/0=ge-0/0/1}E_CE12 {ge-6/0/0=ge-0/0/1}E_P5 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}E_P6 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}E_PE7 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}E_PE8 {fe-1/2/3=ge-0/0/1, xe-2/2/2=ge-0/0/3, ge-1/1/1=ge-0/0/2}W_CE10 {ge-6/0/0=ge-0/0/1}W_CE9 {ge-6/0/0=ge-0/0/1}W_P3 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}W_P4 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}W_PE1 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}W_PE2 {ge-6/0/0=ge-0/0/2, fe-2/1/2=ge-0/0/1, xe-1/2/3=ge-0/0/3}