Simware 5.2a usage (Experience summary)

Statement:

1. I do not provide any software mentioned in this article;

2. This Article is a summary of my personal experience and only represents my point of view;

3. If there are similarities, it is a coincidence;

4. indicate the source for reprinting.

 

There has been a period of time in contact with simware, from the beginning to gradually understanding the software temper has also taken a lot of detours, here to record the use of methods for memo.

 

Once the software is installed, you do not need to repeat it. (install winpcap3.0)and use the cracked wvrp5.2a.exe(also the cen.exe file) and you do not need to join the h3c.com domain.

 

Ii. Topology connection, the focus of this article.

I manually edit the hardcfg. TCL file of each device to create a topology. The instance description is clearer:

1. vswitch Connection Method 1:

Connect to the E0/4/X port through the L2 port of the V3 driver. The configuration file is as follows:

Hardcfg. TCL of SW1:

Setselfslot 0
Setmainslot 0
Setconsolecom 2001.
Setbrdtype 0 7
Setmemorysize 96
Setwinsockoffset 100
Setmac 00 01
Setwvrpinstancename SW1
Addlink-portnum 1-localip 127.0.0.1-localport 18141-dstip 127.0.0.1-dstport 18241

 

Hardcfg. TCL of sw2:

Setselfslot 0
Setmainslot 0
Setconsolecom 2002.
Setbrdtype 0 7
Setmemorysize 96
Setwinsockoffset 200
Setmac 00 02
Setwvrpinstancename sw2
Addlink-portnum 1-localip 127.0.0.1-localport 18241-dstip 127.0.0.1-dstport 18141

The red font in the configuration file is the connection command.

Note: When the topology created by method 1 appears in the loop, the port is constantly reversed. If you do not know if it is a bug, you can use method 2 to create a topology for STP experiment.

 

2. vswitch Connection Method 2:

You can switch the Ethernet port through the Layer 2/Layer 3 of the V5 driver to achieve the connection. The configuration file is as follows:

Hardcfg. TCL of SW1:

......

......

Addethnew-speed100 level2-canswitch-slot 0-subslot 2-local 127.0.0.1-lport 18141-Dest 127.0.0.1-dport 18241

 

Hardcfg. TCL of sw2:

......

......

Addethnew-speed100 level2-canswitch-slot 0-subslot 2-local 127.0.0.1-lport 18241-Dest 127.0.0.1-dport 18141

After the switch is started, enter the interface configuration mode. Enter the Port Link-mode Bridge command to specify the Layer 2 mode for all connected ports.

 

3. How to connect a vswitch to a vro:

Same as vswitch connection method 1. After the device is started, it only establishes a VLAN on the router (actually a layer-3 Switch), adds the interconnect interface to the VLAN, and configures the IP address for the VLAN. The command is as follows:

[H3C] VLAN 10

[H3C-vlan10] int VLAN 10
[H3C-Vlan-interface10] ip addr 10.1.1.254 24

The vlan-interface10 is equivalent to the Ethernet port of the router.

 

4. Connect the vro to the vro:

Ethernet port connection: addethernet-Index 1. The interconnection interface can be connected after the IP address of the same network segment is configured.

Serial port connection: addserial-local 127.0.0.1-lport 10121-Dest 127.0.0.1-dport 10221

 

5. The vswitch is connected to the local NIC:

Switch's hardcfg. TCL:

......

......

Bindportwithadaptor-Port 2-adaptor 2

The red command is used to connect the E0/4/1 port of the switch to the NIC with the index value of 2 of the local Nic. The local Nic can be a real Nic or a lookback Nic.

Obtain the NIC index value: run the systeminfo command in the CMD window.

 

6. The vswitch is connected to the vmwarevm:

Switch's hardcfg. TCL:

......

......

Bindportwithadaptor-Port 1-adaptor 3

In the above process, the NIC with the index value of 3 is connected to the vswitch E0/4/0, and then the NIC can be bridging with the Virtual Machine in vwmare.

 

 

3. Start the device

Create a separate directory for each device, such as E:/mylab/SW1. the TCL configuration file is stored in this directory, and then run is created in this directory. BAT, the content is as follows:

E:/simware/wvrp5.2a.exe

Run run. bat and the device starts up. Use securecrt to log on to the device and configure the experiment.

 

Current problems:

1. The host in the same VLAN across vswitches is sometimes interconnected and sometimes disconnected, which may be a bug;

2. The port aggregation experiment fails. There is no lacp enable command.

 

If you have any questions about the content described in this article, please let us know and I will try my best to reply. You are also welcome to share your experience with us!