The LANforge-ICE Cookbook provides a set of high-level examples of how to setup useful test scenarios in LANforge-ICE for WAN emulation. Each example intends to give the reader a brief introduction to the test scenario and a set of step-by-step instructions on how to use the LANforge-GUI to configure the test.
All of the following examples will work on Linux systems running the LANforge software with the LANforge kernel and a sufficient license. If you are running another Linux kernel, you will not be able to exactly duplicate some of the examples, but there are usually work-arounds available to assist you. Please contact us at support@candelatech.com if you have any questions.
If you are using the Windows version of LANforge, you will have to modify ports using the Windows utilities and you will not be able to duplicate the Routed Mode ICE examples. Everything else should work approximately the same, but the performance is limited to 10Mbps speeds.
Before attempting the examples below, ensure that you have successfully
followed these software installation guides:
It is also recommended that you back up your current running LANforge-Server database so that you may safely return to your current operating state.
1. Bridged Mode (Non-routed) WanLink
Goal: Allow LANforge-ICE to sit transparently on a network segment by using a Bridged Mode WanLink to simulate a WAN. Return to LANforge-ICE Cookbook
In this test scenario, a LANforge-ICE WanLink is created in Bridged Mode to simulate a WAN consisting of a DS1 speed (1.544Mbps) link with 20ms of delay in one direction and 30ms of delay in the other direction.
| Bridged Mode WanLinks use ports that have no IP address because the ports are transparent to the traffic flowing through them. |
| A: Go to the Port Manager |
 |
| B: Modify port eth0
• Set the IP address, IP Mask and Gateway IP to all zeroes (0.0.0.0) |
 |
| C: Modify port eth1
• Set the IP address, IP Mask and Gateway IP to all zeroes (0.0.0.0) |
 |
| D: Verify the port configuration |
 |
| A: Go to the WanLinks tab |
 |
| B: Create a WanLink
• To simulate a WAN, enter a specific amount of delay or other impairment • For this example, enter 20ms of delay for Entry Point A and 30ms of delay for Entry Point B • Be sure to set the correct ports and transfer rate for each Entry Point • Click OK when done |
 |
| C: Verify the WanLink was created |
 |
| D: Go to the Status tab and click Netsmith to view the graphical representation of the WanLink |
 |
| E: This is the general form of a Bridged Mode WanLink in Netsmith. It consists of two 0.0.0.0 IP addressed ports with a vertical bar between them. |
 |
| A: Right-click on the WanLink and select Toggle WanLink to allow traffic to flow from a transmitting device to a receiving device |
 |
| B: The transmitting/receiving devices can be just about
anything that generates and receives traffic such as a web server and client or a pair
of LANforge-FIRE ports
• Right-click the WanLink and select Display WanLink |
 |
| C: View the WanLink display |
 |
| D: View the WanLinks tab
• Selecting a WanLink automatically selects the WanLink Endpoints on the bottom panel
• Scroll to the right on the bottom panel to note the Serialization
Delay (delay injected by LANforge to account for packet size and transfer rate).
• The total delay as experienced by the transmitting/receiving device is the sum of the WanLink configured delay and the serialization delay which in this case would be about 28ms in one direction and 38ms in the other. |
 |
2. Bridged Mode WanLink with Virtual Ports/Redirect Devices
Goal: Setup a Bridged Mode WanLink using RDDs (Redirect Devices). Return to LANforge-ICE Cookbook
In this test scenario, a LANforge-ICE WanLink is created in Bridged Mode using Redirect Devices to illustrate an example of how to send LANforge-FIRE traffic to yourself through LANforge-ICE. This is useful when physical ports are in short supply and a proof-of-concept test is needed.
| A: Go to the Status tab and click Netsmith |
|
| B: Right-click inside the Netsmith window and select New Connection |
 |
| C: Accept defaults, Auto Create everything and click OK
• NOTE: The new connection consists of two pairs of Redirect Devices, Port 1A, 1B and Port 2A, 2B and a WanLink. The new connection is not created until you click the Apply button in the Netsmith window. |
 |
| D: Apply the new connection
• NOTE: The new connection is created and has a Bridged Mode WanLink between Redirect Device ports 1B and 2B which are shown as smaller, green squares (B-Ports) connected by a vertical bar (WanLink). |
 |
| A: Right-click the WanLink and select Modify WanLink |
 |
| B: Verify that the B-side ports of the Redirect Device pairs
(rddVR0b and rddVR1b) are configured
• NOTE: Be sure to set the impairment, if any, and transfer rate • Click OK when done |
 |
| C: Right-click on the WanLink and select Toggle WanLink to Running (green) |
 |
| A: Right-click port rddVR0 and select Modify Port |
 |
| B: Assign an IP address and Network Mask to rddVR0 |
 |
| C: Right-click port rddVR1 and select Modify Port |
 |
| D: Assign an IP address and Network Mask to rddVR1
• NOTE: As an alternate method to set Network Mask, enter a / followed by the number of mask bits after the IP address. In this case, /24 is equivalent to 255.255.255.0 |
 |
| E: Select the 'IPv4s' checkbox at the bottom of the Netsmith window to verify port configuration |
 |
| F: Go to the Port Mgr tab to verify port configuration
• NOTE: The Bridged Mode WanLink is connected between rddVR0b and rddVR1b which both have 0.0.0.0 IP addresses |
 |
| A: Go to the Layer-3 tab and click Create |
 |
| B: The RDD-FIRE connection will use the A-side ports of
the Redirect Device pairs
• NOTE: These are the ports rddVR0 and rddVR1 that were assigned IP addresses in step 2 |
 |
| C: Verify the Layer-3 connection was created |
 |
| A: Select the Layer-3 Cross Connect and click Start |
 |
| B: Click Display to show the Layer-3 Cross Connect details |
 |
| C: Go to the Status tab and click Netsmith to view the graphical representation of the setup |
 |
| D: Right-click on the WanLink and select Display WanLink to display the WanLink details |
 |
3. Routed Mode WanLinks with Virtual Routers
Goal: Setup a Routed Mode WanLink between two Virtual Routers. Return to LANforge-ICE Cookbook
In this test scenario, LANforge-ICE is used to simulate a routed network where incoming traffic on one port is sent through one Virtual Router then through a WanLink, then through a second Virtual Router and then finally out to a port on a different network.
| A: Go to the Status tab and click Netsmith |
|
| B: Right-click in the Netsmith window and select New Connection |
|
| C: Accept defaults, Auto Create everything then click OK |
|
| D: Click Apply in the Netsmith window to create the connection |
|
| A: Right-click in the Netsmith window and select New Router |
 |
| B: Accept defaults, or change the name, graphical size and
notes about the Virtual Router.
• Click OK when done |
 |
| C: Click the Apply button and repeat for the
second Virtual Router
• NOTE: After making any changes to the Netsmith window, you must click Apply or your changes will NOT be implemented and could be lost. |
 |
| D: Click the Apply button followed by the Sync
button
• NOTE: Clicking Sync makes sure any changes are synchronized with the current database. • Also, note the Netsmith Apply Progress bar displayed at the bottom of the Netsmith window. |
 |
| A: Right-click port rddVR0 and select Modify Port |
 |
| B: Assign an IP address and Network Mask.
This example uses 10.1.1.100 and 255.255.255.0. |
|
| C: Right-click port rddVR1 and select Modify Port |
 |
| D: Assign an IP address and Network Mask.
This example uses 10.1.1.101 and 255.255.255.0. |
|
| A: Left-click and drag rddVR0 into Router R0(1) |
 |
| B: Left-click and drag rddVR1 into Router R1(2) |
 |
| C: Click the Apply button at the bottom of the Netsmith window |
 |
| A: Right-click the WanLink and select Modify Wanlink |
 |
| B: Verify that the B-side ports, rddVR0b and rddVR1b are
filled in.
• NOTE: Be sure to set the impairment, if any, and transfer rate. • Click OK when done |
|
| C: Right-click the WanLink and select Toggle Wanlink to set its status to Running (green). |
 |
| A: Right-click port eth0 and select Modify Port |
 |
| B: Assign port eth0 an IP address and Network Mask
• NOTE: This example uses 172.1.1.1 and 255.255.255.0 |
 |
| C: Drag port eth0 into Router R0(1) |
 |
| D: Right-click port eth1 and select Modify Port |
 |
| E: Assign port eth1 an IP address and Network Mask.
• NOTE: This example uses 172.2.2.1 and 255.255.255.0 |
 |
| F: If either physical port connects to a larger routed
network, right-click the port and select Modify and enter values for Next Hop
and Subnets as follows:
• NOTE: Next Hop is the default gateway of your next network hop • Up to 8 different subnets can be configured or 0.0.0.0/0 for any subnet • Click OK when done, then click Apply in Netsmith to apply your changes |
 |
| G: Drag port eth1 into Router R1(0) |
 |
| H: Click the Apply button at the bottom of the Netsmith window |
 |
| A: Verify that the traffic on eth0 is being sent to
Default Gateway 172.1.1.1 and that traffic on eth1 is being sent to Default Gateway
172.2.2.1
• NOTE: In this example, traffic to eth0 is from a port configured with IP address 172.1.1.105 Network Mask 255.255.255.0 and Default Gateway 172.1.1.1 • Traffic to eth1 is from a port configured with IP address 172.2.2.106 Network Mask 255.255.255.0 and Default Gateway 172.2.2.1 • To generate routed network traffic refer to the LANforge FIRE Cookbook Routed Network Testing section. • If your physical configuration is complete, Netsmith should appear as shown here |
 |
| B: Right-click one of the Virtual Routers and select Show Routing Table to view the internal routing table for the Virtual Router |
 |
| C: LANforge Virtual Routers by default use simple subnet routing, but can also use OSPF or BGP routing protocols. LANforge can also perform IPv4 multicast routing. |
 |
4. Routed Mode WanLinks with a Single Physical Port
Goal: Setup a Routed Mode WanLink between two Virtual Routers that only use one physical port. Return to LANforge-ICE Cookbook
In this test scenario, LANforge-ICE is used to simulate a routed network where a single physical port is used for incoming and outgoing traffic. The traffic will enter the physical port and will then be sent through two Virtual Routers connected by a WanLink and then back out the same physical port.
| A: Go to the Status tab and click Netsmith |
|
| B: Right-click in the Netsmith window and select New Connection |
|
| C: Accept defaults, Auto Create everything and click OK |
|
| D: Click Apply in the Netsmith window to create the connection |
|
| A: Right-click in the Netsmith window and select New Router |
|
| B: Accept defaults, or change the name, graphical size and
notes about the Virtual Router
• Click OK when done |
|
| C: Click the Apply button and repeat for the
second Virtual Router
• NOTE: After making any changes to the Netsmith window, you must click Apply or your changes will NOT be implemented and could be lost |
|
| D: Click the Apply button followed by the Sync
button
• NOTE: Clicking Sync makes sure any changes are synchronized with the current database • Also, note the Netsmith Apply Progress bar displayed at the bottom of the Netsmith window |
|
| A: Right-click port rddVR0 and select Modify Port |
|
| B: Assign an IP address and Network Mask
• This example uses 10.1.1.100 and 255.255.255.0 |
|
| C: Right-click port rddVR1 and select Modify Port |
|
| D: Assign an IP address and Network Mask
• This example uses 10.1.1.101 and 255.255.255.0 |
|
| A: Left-click and drag rddVR0 into Router R0(1) |
|
| B: Left-click and drag rddVR1 into Router R1(2) |
|
| C: Click the Apply button at the bottom of the Netsmith window |
|
| A: Right-click the WanLink and select Modify Wanlink |
|
| B: Verify that the B-side ports, rddVR0b and rddVR1b, are
filled in
• NOTE: Be sure to set the impairment, if any, and transfer rate • Click OK when done |
|
| C: Right-click the WanLink and select Toggle Wanlink to set its status to Running (green) |
|
| A: Go to the Port Mgr tab, select eth0 and click Create |
 |
| B: Select the MAC-VLAN button
• Set a MAC address that begins with 00 (Ex: 00:11:33:55:77:01) • Set the Quantity to 2 • Set the IP Address to 172.1.1.1 and IP Mask to 255.255.255.0 • Leave the Gateway IP field blank • Click OK when done |
 |
| C: Select the MAC VLAN eth0#1 and click Modify |  |
| D: Set eth0#1 IP address to 172.2.2.1 and IP Mask to 255.255.255.0 |
 |
| E: Select eth1 and click Create |
 |
| F: Select the MAC-VLAN button
• Set a MAC address that begins with 00 (Ex: 00:22:44:66:88:01) • Set the Quantity to 2 • Set the IP Address to 172.1.1.100 and IP Mask to 255.255.255.0 • Set the Gateway IP to 172.1.1.1 • Click OK when done |
 |
| G: Select the MAC VLAN eth1#1 and click Modify |
 |
| H: Set eth1#1 IP address to 172.2.2.100, IP Mask to 255.255.255.0 and Gateway IP to 172.2.2.1 |
 |
| A: Move the ports on the Netsmith window to be
more clearly visible
• NOTE: Be sure to click Apply after moving objects so that their new positions are saved to the database |
 |
| B: Drag eth0#0 into Router R0(1) |
 |
| C: Drag eth0#1 into Router R1(2) |
 |
| D: Click Apply in the Netsmith window
• LANforge is now ready to accept incoming traffic on eth0, the single physical port that is connected to a Routed Mode WanLink • Ports eth0 and eth1 are physically connected via a loopback cable in this example. MAC VLANs on eth1 are configured to generate test traffic to the Routed Mode WanLink |
 |
| A: Go to the Layer-3 tab and click Create |
|
| B: Set Endpoint A to be eth1#0 and Endpoint B to be eth1#1
• Enter the CX name then set the CX Type to LANforge UDP and the Report Timer to 1000 • Set the Min/Max Tx Rate to 1024000 and the Min/Max Pkt Size to 1472 |
 |
| C: Select the new connection and click Start |
 |
| D: LANforge will issue a pop-up warning, but it can be ignore since the two MAC-VLAN interfaces are on different subnets and connected by the Routed Mode WanLink |
 |
| E: Netsmith now shows the new connection and traffic flowing through the Routed Mode WanLink |
 |
5. Routed Mode WanLink with WanPaths
Goal: Setup a Routed Mode WanLink with WanPaths. Return to LANforge-ICE Cookbook
In this test scenario, LANforge-ICE is used to filter traffic by IP address on a WanLink with the use of WanPaths.
| A: Go to the Status tab and click Netsmith |
|
| B: Right-click in the Netsmith window and select New Connection |
|
| C: Accept defaults, Auto Create everything and click OK |
|
| D: Click Apply in the Netsmith window to create the connection |
 |
| E: The Netsmith window after applying changes |
|
| A: Right-click the WanLink and select Modify WanLink |
|
| B: Setup the WanLink with values larger than what each of the
WanPaths will use
• WanPaths are subordinate to WanLinks. WanLinks, therefore, should be configured with sufficient bandwidth and buffering required by all of its WanPaths • Click Apply and leave the Create/Modify WanLink window open |
 |
| A: Click Create-WP on Entry Point A to create a new
WanPath on this WanLink
• NOTE: In order to filter by specific IP address, use a Source and Dest Mask of 32 to exactly match the IP coming in on the Entry Point • Click OK to create the WanPath |
 |
| B: Click Create-WP on Entry Point B to create a new
WanPath on this WanLink
• NOTE: The Source and Destination IPs for this WanPath are the reverse of those for Entry Point A • Click OK to create the WanPath |
 |
| C: Create a second WanPath for this WanLink using the next set of IP addresses |
 |
| D: Reverse the Source and Destination IPs for this corresponding WanPath |
 |
| E: Verify that the WanPaths on this WanLink are setup correctly, then click OK on the Create/Modify WanLink window shown here |
 |
| A: Right-click on the WanLink and select Toggle Wanlink |
|
| B: Right-click port rddVR0 and select Modify Port |
|
| C: Setup an IP address that is on a different network than the WanPath entry points |
 |
| D: Setup an IP address on port rddVR1 that is on the same network as rddVR0 |
 |
| A: Right-click in the Netsmith window and select New Router |
 |
| B: Accept the defaults or change the Virtual Router name and graphical size |
|
| C: Click the Apply button and repeat for the
second Virtual Router
• NOTE: After making any changes to the Netsmith window, you must click Apply or your changes will NOT be implemented and could be lost • NOTE: Clicking Sync makes sure any changes are synchronized with the current database |
 |
| D: Left-click rddVR0 and drag it inside Router R0(1) |
 |
| E: Left-click rddVR1 and drag it inside Router R1(2) |
 |
| F: Apply your changes in Netsmith |
 |
| A: Right-click port eth0 and select Modify Port |
 |
| B: Setup eth0 with a valid IP address and IP mask that is on the same network as the WanPath entry points ep-1 and ep-3 |
|
| C: Left-click port eth0 and drag it inside Router R0(1) |
 |
| D: Setup eth1 with a valid IP address and IP mask that is on the same network as the WanPath entry points ep-2 and ep-4 |
|
| E: Drag eth1 inside Router R1(2) and Apply changes in Netsmith |
 |
| A: Right-click the WanLink and select Display Wanlink |
 |
| B: The lower half of the WanLink display shows traffic passing on WanPath entry points ep-3 and ep-4 and other IP address are excluded from passing on the WanLink |
 |
| C: Select a WanPath and click Display Selected Paths in the lower left corner of the WanLink display window |
 |
6. Virtual Router with DHCP Service
Goal: Setup a Virtual Router with one interface serving DHCP. Return to LANforge-ICE Cookbook
In this test scenario, a LANforge Virtual Router is created with one interface setup to serve DHCP to two remote redirect interfaces that are setup to be DHCP clients.
| A: Go to the Status tab and click the Netsmith button |
|
| B: Right-click in the Netsmith window and select
New Router
• Follow steps discussed above for configuring the router |
 |
| C: Right-click in the Netsmith window and select New Connection |
 |
| D: Accept defaults, Auto Create everything and click OK |
|
| E: Repeat and create a second connection. |
 |
| F: Click the Apply button to commit the changes in
Netsmith to the LANforge Server.
• NOTE: Modifications in Netsmith are only sent to the LANforge-Server after Applying them |
 |
| A: Right-click the first WanLink and select Modify WanLink |
 |
| B: Enter values specific to your test and click OK
• NOTE: Kernel-Mode allows for much higher emulation speeds and supports all features of the normal WAN emulation mode • Kernel-Mode is available for the WAN emulation if you are using a pre-compiled Linux kernel from the Candela downloads page |
 |
| C: Right-click to toggle the WanLink status to Running (green). |
 |
| D: Repeat for the second WanLink and set it to Running (green). |
 |
| A: Right-click port rddVR0 and select Create Ports |
 |
| B: Select the Bridge button from the available connection types, name it, and click OK |
 |
| C: Right-click the bridge port and select Modify Port
• NOTE: You will have to click the Sync button for your newly created bridge port to appear in the Netsmith window. |
 |
| D: Assign an IP address and IP mask, then click Apply |
 |
| E: Enter interface names rddVR0 and rddVR2 in the whitespace located below the Add Ports button so that you can add them as bridge members |
 |
| F: Click Add Ports to add the interfaces as bridge members, then click OK |
 |
| G: The Netsmith window now shows a bridge port with two bridge members |
 |
| A: Drag the bridge port into the virtual router. |
 |
| B: Right-click the bridge port and select Modify |
 |
| C: Select the 'DHCP' checkbox at the bottom of the window and
enter in your desired DHCP Server configuration, then click OK |
 |
| D: Right-click interface rddVR1 and select Modify Port |
 |
| E: Select the 'DHCP' checkbox to make this interface a DHCP client, then click OK |
 |
| F: Repeat for interface rddVR3, then click Netsmith Apply |
 |
| G: After the Netsmith apply, DHCP clients will acquire
IP addresses from the DHCP server
• Select the 'IPv4s' checkbox at the bottom of the Netsmith window to see the IP addresses of the DHCP clients |
 |
| A: Go to the Layer-3 tab and click Create |
|
| B: The RDD-FIRE connection for this example will use interfaces rddVR1 and rddVR3. |
 |
| C: Verify the Layer-3 connection was created |
 |
| A: Select the Layer-3 Cross Connect and click Start |
 |
| B: Go to the Status tab and click Netsmith to view the graphical representation of the setup |
 |
7. Virtual Router with NAT
Goal: Setup a Virtual Router with one interface performing NAT on outgoing traffic. Return to LANforge-ICE Cookbook
In this test scenario, a pair of Virtual Routers are connected with a Redirected Interface connection with one side of the connection performing NAT on outgoing traffic. Two additional Redirected Interface connections are configured to pass traffic and demonstrate NAT.
| A: Right-click inside the Netsmith window and select New Router |
 |
| B: Repeat to create another virtual router |
 |
| C: Right-click inside the Netsmith window and select New Connection |
 |
| D: Select the 'Skip' option on Port 1-B, WanLink and Port 2-B, then click OK |
 |
| E: Repeat and create two more connections |
 |
| F: Click the Apply button followed by the
Sync button
• NOTE: Modifications in Netsmith are only sent to the LANforge-Server after Applying them • Clicking Sync makes sure any changes are synchronized with the current database |
 |
| A: Right-click the rdd ports and select Modify Port
• Assign each pair of rdd ports a unique subnet and IP address |
 |
| B: Select the 'IPv4s' checkbox to view the IP addresses of the rdd ports |
 |
| C: Configure rddVR3 and rddVR5 with a Gateway IP that
corresponds to their peer rdd interface
• NOTE: In this example, rddVR3 has a Gateway IP of 20.20.20.1 and rddVR5 has a Gateway IP of 30.30.30.1 |
 |
| A: Drag rddVR0 into Router R0(1) and rddVR1 into Router R1(2) |
 |
| B: Drag rddVR2 into Router R0(1) and rddVR4 into Router R1(2) |
 |
| C: Click Netsmith Apply to commit the changes |
 |
| A: Go to the Layer-3 tab and click Create |
|
| B: Create a Layer-3 TCP connection between endpoints
rddVR3 and rddVR5 then click OK |
 |
| C: In Netsmith, right-click the TCP connection and click Start |
 |
| D: Right-click port rddVR1 and click Sniff Port
• NOTE: You must have Wireshark properly installed as described here:
|
 |
| E: After Wireshark begins, notice that the source and destination IP addresses are from 20.20.20.20 (rddVR3) and 30.30.30.30 (rddVR5) as expected without NAT enabled |
 |
| A: Right-click on the TCP connection and select Stop |
 |
| B: Right-click rddVR0 and select Modify |
 |
| C: Select the 'NAT' checkbox and click OK, then click the Netsmith Apply button |
 |
| D: Right-click on the TCP connection and select Start |
 |
| E: Right-click port rddVR1 and select Sniff Port |
 |
| F: After Wireshark begins, notice that any source or destination
IP address from or to 20.20.20.20 (rddVR3) has been NAT'd to be 10.10.10.10 because rddVR0 is now performing NAT on all outgoing traffic |
 |
8. Multiple Layer-2 Switches
Goal: Emulate the behavior of five Layer-2 Switches connected together for traffic fail-over testing. Return to LANforge-ICE Cookbook
In this test scenario, the function of several layer-2 switches will be emulated using multiple LANforge Bridge devices with Spanning Tree Protocol (STP) so that each bridge can be connected to at least two others and fail-over tests can be demonstrated.
| A: Right-click inside the Netsmith window and select New Connection |
|
| B: Accept defaults, Auto Create everything then click OK |
|
| C: Repeat and create a total of seven (7) connections |
 |
| D: Click the Apply button to commit the changes in
Netsmith to the LANforge-Server
• NOTE: Modifications in Netsmith are only sent to the LANforge-Server after Applying them |
 |
| A: Right-click inside the Netsmith window and select New Bridge |
 |
| B: Select the Bridge button, enter a name,
click Apply then repeat to create four more bridges.
• NOTE: The 5 bridges here are sw-0, sw-1, sw-2, sw-3, and sw-4 |
 |
| C: In Netsmith, position the bridge devices into separate areas so they can be grouped with WanLink entry points |
 |
| A: Position the WanLink entry points in groups near the
bridges as follows:
• 2 entry points near sw-0, sw-1, and sw-2 (one to sw-3 and one to sw-4) • 3 entry points near sw-3 and sw-4 (one to sw-0, sw-1, and sw-2) • Bridges sw-3 and sw-4 should also have a WanLink between them |
 |
| B: Click Netsmith Apply to commit the changes |
 |
| A: Right-click bridge sw-0 and select Modify Port |
 |
| B: Select the 'Set Bridge Info' and 'Spanning Tree' checkboxes,
then add bridge members rddVR1 and rddVR3
• NOTE: Selecting the 'Spanning Tree' checkbox enables Spanning Tree Protocol (STP) for that port • Click the Apply or OK button to commit the changes in bridge configuration to the LANforge-Server |
 |
| C: Right-click bridge sw-1 and select Modify Port
• Enable STP and add members rddVR5 and rddVR7 |
 |
| D: Right-click bridge sw-2 and select Modify Port
• Enable STP and add members rddVR11 and rddVR13 |
 |
| E: Right-click bridge sw-3 and select Modify Port
• Enable STP and add members rddVR0, rddVR4, rddVR8 and rddVR10 |
 |
| F: Right-click bridge sw-4 and select Modify Port
• Enable STP and add members rddVR2, rddVR6, rddVR9 and rddVR12 |
 |
| G: Right-click all WanLinks and select Toggle WanLink
so that they are running
• NOTE: Set each WanLink to at least 4Mbps to work with the traffic speeds used below |
 |
| A: Right-click sw-0 and select Create Ports and
choose Redirect
• This step will create two Redirect Devices, rddA and rddB |
 |
| B: Add rddA to bridge sw-0
• Click the Apply or OK button to commit the changes in bridge configuration to the LANforge-Server |
 |
| C: Right-click rddB and select Create Ports,
then select the MAC-VLAN button
• Enter a starting MAC address, quantity 5, and starting IP address |
 |
| D: Repeat for bridge sw-1
• NOTE: The Netsmith display has been 'zoomed-out' by clicking the '-' magnifying glass icon located at the top left of the Netsmith display |
 |
| E: Repeat for bridge sw-2 |
 |
| A: On the Layer-3 tab, create a Layer-3 UDP
connection between rddB#0 and rddD#0 |
 |
| B: Create 4 more connections between the remaining rddB and rddD ports |
 |
| C: Create 5 connections between the rddD and rddF ports
• Repeat this step for the rddF and rddB ports for a total of 15 connections |
 |
| A: On the Layer-3 tab, select all 15 connections and click Start |
 |
| B: In Netsmith, verify traffic is flowing through
sw-3 or sw-4 via 3 separate WanLinks
• In this case, VRWL1.1.001, VRWL-1.1.003 and VRWL-1.1.006 all show traffic flowing |
 |
| C: Right-click WanLink VRWL-1.1.001 and select Toggle WanLink |
 |
| D: After approximately 1 minute, the traffic will find an alternate path |
 |
| E: Right-click WanLink VRWL-1.1.001 and select Toggle WanLink |
 |
| F: After approximately 1 minute, traffic resumes on its original path |
 |
| G: Traffic flow after simulating multiple path failures
• A sample LANforge HTML report of this fail-over test can be found here:
|
 |
9. Emulating a Multiple Hop Network
Goal: Use virtual routers to emulate a multi-hop network.
In this example, LANforge is used to emulate a live routed network by using multiple virtual routers to form a working multi-hop network. Each virtual router has its own routing table and can be configured to use one of many different routing protocols. OSPF will be used in this example and traceroute will be used to demonstrate the traversal of each hop.
| A: From the Status tab, select the Netsmith button. |
 |
| B: Right-click in the Netsmith window and select New Router. |
 |
| C: Select the Use OSPF checkbox. |
 |
| D: Select OK, then create four more OSPF virtual routers. |
 |
| E: After creating five OSPF virtual routers, select Apply. |
 |
| A: Right-click in the Netsmith window and select New Connection. |
 |
| B: Leave all the default settings and select OK. |
 |
| C: Create three more Netsmith connections. |
 |
| D: After creating four Netsmith connections, select Apply. |
 |
| A: Right-click on rddVR0 and select Modify Port. |
 |
| B: Set rddVR0 to 10.0.0.1/30 and select OK. |
 |
| C: Right-click on rddVR1 and select Modify Port. |
 |
| D: Set rddVR1 to 10.0.0.2/30 and select OK. |
 |
| E: Repeat the steps above to complete the following:
rddVR2 is 11.0.0.1/30 and rddVR3 is 11.0.0.2/30 rddVR4 is 12.0.0.1/30 and rddVR5 is 12.0.0.2/30 rddVR6 is 13.0.0.1/30 and rddVR7 is 13.0.0.2/30 |
 |
| A: Setup the following by dragging
the interfaces into the specified virtual routers:
rddVR0 in R0 and rddVR1 in R1 rddVR2 in R1 and rddVR3 in R2 rddVR4 in R2 and rddVR5 in R3 rddVR6 in R3 and rddVR7 in R4 |
 |
| B: Right-click on each Wanlink (red bar)
and select Toggle Wanlink (change to green bar).
Note: If you wanted to emulate an impaired multi-hop network, you could modify each Wanlink to have any LANforge impairment such as latency, jitter, dropped packets, etc... |
 |
| C: After all interfaces are moved and Wanlinks started, select Apply in the Netsmith window. |
 |
| A: Right-click on each interface and select Modify Port. |
 |
B: Setup the following IP addresses and Default Gateways:
eth1 IP address is 172.16.0.101/24 and Default GW is 172.16.0.1 eth2 IP address is 172.16.0.1/24 and Default GW is 172.16.0.1 eth3 IP address is 192.168.0.1/24 and Default GW is 192.168.0.1 eth4 IP address is 192.168.0.104/24 and Default GW is 192.168.0.1 |
 |
| C: Drag eth2 into R0 and eth3 into R4, then Apply changes.
Note: In this example, four physical interfaces are used. eth1 and eth2 are physically connected with a cable, as are eth3 and eth4. This allows us to use eth1 and eth4 to generate traffic to each other through the network interfaced by eth2 and eth3. |
 |
| A: After applying all Netsmith changes, right-click
on a virtual router and select Show Routing Table.
Before OSPF converges, only the directly connected networks are shown. |
 |
B: After OSPF converges, each virtual router has
a complete routing table for the entire network.
Note: If you select Netsmith Apply again, this will restart all virtual routers and OSPF will need time to converge again. |
 |
| A: With OSPF virtual routers, you can right-click on a virtual router and select Virtual Router Console to bring up the underlying xorp shell for the virtual router. |
 |
| B: Once at the xorp shell prompt, type the following
to display the routing table information:
show route table ipv4 unicast final |
 |
| A: Open a terminal window in the LANforge system. |
 |
B: Type the following command at the prompt:
traceroute -i eth1 13.0.0.2 Note: -i eth1 forces the traceroute program to use eth1 as its outgoing interface. |
 |
| C: Observe the results of each hop in the network. |
 |
| D: Traceroute from eth4.
traceroute -i eth4 10.0.0.1 |
 |
| A: Go to the Layer-3 tab and select Create. |
 |
B: Set Endpoint-A to use eth1 and Endpoint-B to use eth4. |
 |
| C: Start the Layer-3 connection. |
 |
| D: Traffic flowing through the multi-hop network. |
 |
10. Multiple Physical Port Testing - CT970-48 Example
Goal: Use LANforge and a managed ethernet switch to create 48 unique WAN emulations.
In this example, LANforge is paired with a managed ethernet switch to create 48 unique WAN emulations. Each of the 48 ports on the ethernet switch can be connected to an end-user device such as a PC or networked gaming console to provide 48 independent emulated links each with their own set of network impairments. Please see the CT970-48 product description for more details.
NOTE: If you are attempting to run this test scenario, you will need a LANforge license key that enables the correct number of WanLinks. Please contact us at support@candelatech.com for assistance.
You can download all of the CT970-48 configuration files to your /home/lanforge/DB/CT970-48 directory.
NOTE: This LANforge database uses eth0 as the Management port and eth2 as the VLAN trunk port. If you need to modify these, please contact us at support@candelatech.com for assistance.
NOTE: The managed switch referenced in this example is a Netgear FSM7352SNA ProSafe 48-port 10/100 L3 Managed Switch.
| A: On the Status tab, under the Test Configuration Database Name field, type in a name for your existing configuration, then select the Save button. |
 |
| B: Select CT970-48 from the Test Configuration Database List box. |
 |
| C: Select Load Behavior Overwrite. |
 |
| D: Select the Load button and acknowledge the confirmation pop-up message. |
 |
| A: On the Status tab, under Resource 1, select the Netsmith button. |
 |
| B: If any changes are made to Netsmith, then select the Apply button to commit the changes to the LANforge server. |
 |
Each switch port and VLAN correspond to a WanLink in LANforge. Here, incoming traffic on switch port 1 is tagged for VLAN 101 and sent out switch port 52 to LANforge eth2 then on to WanLink VRWL-1.1.0 via endpoints eth2.101 and rdd1.101.
| A: Connect LANforge port eth2 to the FSM7352SNA switch, port 52 which is trunking vlans 101 - 148 to the LANforge system. |
 |
| B: Here, each WanLink can be modified to have its own unique impairment profile so that each end-device has a different upstream connection. |
 |
| C: If any changes are made to Netsmith, then select the Apply button to commit the changes to the LANforge server. |
 |
| D: Alternatively, a group of WanLinks can be modified together using the Batch Modify on the WanLinks tab in the main LANforge GUI. Highlight the group of WanLinks that you want to modify, then select Batch Modify to modify the highlighted set of WanLinks. |
 |
| E: The Batch Modifier will apply changes to the group of highlighted WanLinks. |
 |
PC1 - switch port 1 - vlan 101 - switch port 52 - LANforge port eth2 - WanLink VRWL-1.1.0 - Virtual Router R0 - vlan 102 - WanLink VRWL-1.1.1 - LANforge port eth2 - switch port 52 - switch port 2 - PC2.
The end-devices used here are LANforge-FIRE interfaces on a separate system. Each interface has its own MAC and IP address and will generate traffic to and receive traffic from the switch port it is connected to.
| A: On the Port Mgr tab, assign an IP address on the 10.1.1.0/24 network and a default gateway 10.1.1.1 |
 |
B: On the Port Mgr tab, assign an IP address on the 10.1.1.0/24 network and a default gateway 10.1.1.1 |
 |
| A: The total latency of WanLinks VRWL-1.1.0 and VRWL-1.1.1 is 100ms. |
 |
B: Each end of the connection experiences 100ms of delay which gives a total round-trip delay of 200ms. |
 |
Email Candela Technologies at: support@candelatech.com if you have any questions or suggestions.
www.candelatech.com | sales@candelatech.com | +1 360 380 1618
Candela Technologies, 2026 Main Street, Suite A, P.O. Box 3285, Ferndale, WA 98248, USA
www.candelatech.com |
sales@candelatech.com | +1 360 380 1618
Last modified: Wed Apr 15 11:00:00 PDT 2009