Changes between Version 5 and Version 6 of Workshops/Sig Comm2022/Mininet Optical
- Timestamp:
- Aug 18, 2022, 3:54:09 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Workshops/Sig Comm2022/Mininet Optical
v5 v6 367 367 368 368 (Note: if you want to use the X11 features of Mininet, such as the `xterm` or `plot` commands, you may need to use `sudo HOME=~` rather than just `sudo`.) 369 <Should we add instructions to setup x11?> 370 371 If you don't have one open already, open up another terminal window with the below instructions: 372 373 == [WIP] Opening another terminal window in Orbit == 374 375 1. SSH into 369 370 If you don't have one open already, open up another terminal window with the below instructions. For ease of use, we will call this terminal-2 hereafter: 371 372 == Opening another terminal window in Orbit == 373 374 1. Open another terminal window in your computer/laptop (Linux:CTRL+ALT+T, Mac: CMD+T, Windows: CTRL+Shift+T) 375 2. SSH to Orbit console with your username. This is the same step used to login to Orbit console in hardware tutorial [wiki:/Workshops/SigComm2022/SignupInstructions] according to your assigned group. 376 376 377 377 {{{ 378 378 #!shell-session 379 user@ console:~$ cd ~/mininet-optical380 }}} 381 382 2. Connect to the VM where Mininet-Optical is installed 379 user@local-computer:~$ ssh user@<console-name> 380 }}} 381 382 3. Connect to the node where Mininet-Optical is installed. This <node> is the same where you are logged in the previous terminal window. 383 383 384 384 {{{ 385 385 #!shell-session 386 user@console:~$ cd ~/mininet-optical 387 }}} 388 389 3. Enter source directory 390 391 {{{#!shell-session 392 user@console:~$ cd ~/mininet-optical 386 user@console:~$ ssh root@<node> 387 }}} 388 389 4. Enter source directory 390 391 {{{#!shell-session 392 root@<node>:# cd ~/mininet-optical 393 root@<node>:~/mininet-optical# 393 394 }}} 394 395 395 396 Unless specified otherwise, all of the configuration commands below should 396 be entered in t his second windowat the shell prompt.397 be entered in terminal-2 at the shell prompt. 397 398 All of these configurations can be performed by Python scripts developed to work with the COSMOS test-bed. The Python commands send NETCONF commands to the ROADM. 398 399 399 400 == Running the configuration script == 400 401 401 Run the script with the following command 402 Run the script with the following command in terminal-2 402 403 {{{#!shell-session 403 404 root@node:~/mininet-optical# bash -x ./examples/config-sigcommtutorial.py … … 474 475 475 476 As expected, none of the servers are able to ping each other because lightpath connections have not been established as of yet. 477 476 478 477 479 == Configuring ROADMs … … 588 590 ''Note that the Mininet-Optical ROADM dataplane is currently modeled using OvS switching in the Linux kernel, so each hop will add some delay that would not be seen on hardware. Process scheduling, OS and VM overhead, etc. can create additional delays in a software emulator.'' 589 591 592 As before 593 590 594 == Network Interfaces Configuration for Experiment-2 (long-hop) 591 595