All communication between the Emulab software and the switches is done
via SNMP. This task is performed by snmpit, which can be found in the
tbsetup/ directory of the Emulab source. It's been designed with the
idea of supporting multiple vendors, and currently supports Cisco, HP,
Nortel, and Foundry switches. See the modules in that directory called
snmpit_*.pm for vendor-specific support. The main operations that matter
to snmpit are creating VLANs, placing ports in those VLANs to realize
the experimenter's requested topology, and setting the speed and duplex
on those ports.
Thus spake Mohammed Azad on Mon, Apr 13, 2009 at 10:49:47PM -0500:
> _______________________________________________> Hello all,
>
> I am trying to figure out
> 1) what are the messages that the emulab software communicates with switches
> and
> 2) what are the specific operations it does with switches or
> 3) what environment that emulab establishes in switches.
>
> Basically, I was thinking these because I am trying to find out what are the
> vendor/model specific commands of emulab to handle switch or to what degree
> of generalization have been made in this? These information would be very
> helpful to those who may want to use some new vendor/model of switches and
> try to make their testbed to do some newer type of experiments.
>
> If anyone can kindly share his/her ideas and thoughts in this regard, it
> would be great. Looking forward to have your kind response.
>
> With regards
> Mohammed ABul Monzur Azad
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins
--
/-----------------------------------------------------------
| Robert P Ricci <ricci@cs.utah.edu> | <ricci@flux.utah.edu>
| Research Associate, University of Utah Flux Group
| www.flux.utah.edu | www.emulab.net
\-----------------------------------------------------------