|Network Testing and Emulation Solutions|
|Every port, radio, virtual port, endpoint and connection in LANforge has an ID known as an EID. These are an internal notation that expresses the heirarchy of the physical and virtual objects managed by LANforge realm.|
Entity IDs (EIDs) are a dotted-decimal phrase. It expresses the Shelf, Resource Number, Port or Connection number, and if it is an endpoint, it gains an fourth decimal. An Example:
188.8.131.52 : EID 1 : shelf 2 : resource 8 : port 4 : endpoint
You can assume the shelf number will always be 1 for now. The Resource number will refer to the LANforge machine ID as reported on the Status tab. The port id is only unique within a LANforge machine. The port ID also refers to hardware in a machine: radios get a third decimal. The fourth decimal refers to either endpoints or connections.
While some items with port numbers, notably radios and ports, do not generate traffic. Endpoints generate traffic, and typically endpoints are transmitting to an opposite endpoint. The exception to this are multicast endpoints.
From the dotted-decimal perspective:
The formatting of the decimals might or might not be zero-padded. The picture below should convey how a connection (Layer 3) relates to two endpoints, and two ports:
The exception is connections. Connections are numbered outside of this heirarchy.
Usually not, for these reasons:
In scripts, it is legal to reference port numbers, but not advised to store them between sessions. If you reference an EID, it should be from within your present LANforge session. If your resources tend to disappear off the network and return (you had a machine reboot) those EIDs are not guaranteed to return.
If you look into the saved scenarios (in /home/lanforge/DB/DFLT) you will notice that ports, endpoints, and connections are refered to by name. Event though in the CLI Users's guide, where it states port number, use names in your scripts:
CMD | SHELF | | RESOURCE | | | PORT | | | | set_port 1 1 eth1 10.26.1.2 255.255.255.0 10.26.1.1 ....