Table of Contents
Advertisement
User Manual
Alternatively a multi-machine approach can be used in which multiple BSD‟s are loaded
in the same process space. This architecture allows the simulator sessions to pass packets
back and forth without the need for a mediator. Running without a mediator isolates the
simulator sessions from the real network. For more information on running multiple
simulator instances in the same process, see Section 5.3, Multi-Machine Support, on page
41.
Figure 7-33 illustrates multi-machine communication of simulator sessions without a
mediator.
BSD #1 (Machine 1)
02:02:02:02:02:02
10.0.0.1
Figure 7-33: Multi-Machine Communication without a Mediator
7.24.1 Simulated Link Negotiation
A link will appear connected in the guest system when one of the following occurs:
A mediator connection has been established.
There is at least one other NIC BSD running in the same process, and are aware
of each other.
When a new mediator connection string has been specified, a one-shot link negotiation
will take place within the simulator. Depending on whether a connection was made with
the mediator, the link will appear to be connected or disconnected on the guest. If the
mediator was killed and has since been restarted, then the user will need to perform a
"linkConnect auto", to restart link negotiation.
Similarly, in a multi-machine setup, the first simulator session will also need to perform a
"linkConnect auto" to ensure that the initial guest sees that other simulator peers have
been connected.
When neither of the above conditions is met, the link appears disconnected in the guest.
It may be necessary to re-start link negotiation via "linkConnect auto". This will cause
Chapter 7: Device Configuration
AMD Confidential
Simulator Process
BSD #2 (Machine 2)
04:00:00:00:0:04
10.0.0.2
September 12
BSD #3 (Machine 3)
06:00:00:00:00:06
10.0.0.3
th
, 2008
121
Advertisement
Table of Contents
