Huawei eNSP and GNS3

On this page, I will revisit one of my favorite integrations. Taking a network simulator like eNSP and connecting it to another virtual machine housing GNS3.

I’m linking this article to a previous one I wrote in the GNS3 community here:

What I found out since posting the article above is that you have to have a VERY specific build.

The prerequisites are the following:

  1. Virtualbox environment.
    1. You would effectively be creating 2 vitual machines and using the virtualbox interfaces inside GNS3 and eNSP (Huawei) for that connection.
  2. eNSP
    1. the Huawei simulator is limited to certain builds. As my previous article points out, there is a build that allows the use of a ‘cloud interface’ in eNSP. If you don’t see that cloud interface, you don’t have the correct version.
  3. Windows 7 virtual machine.
    1. the eNSP simulator works well in a Windows 7 virtual machine. If you try to run it inside an 8/8.1/or 10 it crashes. I’ve already tried running it in an older environment. My guess is it has to do with how eNSP was written and the type of libraries it uses in a Windows 7 machine.

The point of this article is to sort of preface that older article posted in GNS3. I noticed I still get the occasional question about Huawei (or more importantly the Huawei simulator eNSP and I recommend performing the following tasks.

Stage 1: Gather your items (Huawei simulator, Windows 7 vm and a second vm running gns3 (with GNS3’s vm, you can run it on windows or linux).

Stage 2: Configure your virtualbox network environment. Use HOST ONLY networks to ensure your using the same interfaces handled by that virtual box server. (see for more information.)

Stage 3: Follow the article or ‘script’ found at here:

Once you have passed all three stages, you will be able to ping between the two environments and you can then create a cool sandbox where Huawei is a branch located in ‘China’ (the huawei eNSP topology in the Windows 7 machine) and then create a typical Cisco US branch in the GNS3 topology in the second vm.