Integrating the HP Network Simulator With GNS3 v.0.5

Integration of HP Network Simulator with GNS3

Integrating the HP Network Simulator with GNS3

A guide for installation and operation of multivendor virtual labs with VirtualBox and GNS3Prepared by: Nick ChanningCain Rd, Amen CornerBracknell, Berkshire, RG12 1HN

Document Id: XXXDocument Version: v0.5Date Prepared:6th June 2014

Contents1INTRODUction31.1purpose31.2How it works41.3Aplicability52Install VirtualBox62.1obtain software62.2Installation63Install HP Network simulator83.1OBTAIN SOFTWARE83.2Installation84Install GNS3104.1Obtain software104.2installation105Integration with HP Network simulator165.1Generate comware switch instances165.1.1Launch HNS165.1.2Make the Comware simulator config file175.1.3Save the project175.1.4Create the Simware 7 switch instances185.2Configure GNS3205.2.1Start GNS3205.2.2Configure VirtualBox Integration205.2.3Configure new HP icons for GNS3235.3Testing Comware switch integration with GNS3245.4Device control265.4.1Starting / stopping device265.4.2Displaying the device console275.4.3Using Wireshark to capture network traffic276Adding 3rd party Vendor Devices286.1VirtualBox Linked Clones286.1.1Create a Linked Clone286.1.2Add device to GNS3306.2Cisco CSR1000v316.2.1Obtain Software316.2.2Create the Cisco CSR1000v VM316.2.3Add the CSR1000v instances to GNS3346.3Microsoft Windows 2008 R2 Server356.3.1Obtain Software356.3.2Create Virtual Machine356.3.3Add Windows instance to GNS3367Appendix37HP Network Simulator Instructions378Document control information388.1Distribution List388.2Terms and Acronymous388.3related documentation38Integration of HP Network Simulator with GNS3

HP TS ConsultingHP ConfidentialPage 22 of 38

Copyright 2015 Hewlett-Packard Development Company, L.P.All rights reserved.

INTRODUctionThe HP Network Simulator enables the generation and design of virtual Comware 7 based labs for testing and training purposes. The latest iteration of the Simware 7 platform has now been modified to operate on the VirtualBox hypervisor rather than QEMU which has brought substantial improvements to the speed and operation on Windows based machines.However a key feature lacking is visual representation and control of the topologies that the new version of Simware can produce. GNS3 is a popular GUI and simulation package for Cisco based topologies that can be extended to work with HP and other vendor simulation packages filling this gap in functionality.

purposeThe purpose of this document is to detail the installation steps to enable GNS3 integration with HP Comware 7 simulation software and thus quickly produce your own network topologies using multivendor virtual machines with the aid of the Oracle VirtualBox hypervisor.In addition, this guide details the basic build and operation of a Windows based host that can be used in the simulated environment.As an example of use, figure 1 shows a topology using multiple network technologies from HP, Microsoft and Checkpoint simulating a typical computer network system. The result permits testing and analysis of potential network designs as well as a learning aid for many network based technologies.

Figure1: Sample HP Lab Environment showing Simware 7 integration with Checkpoint Firewall and multiple Windows 2008 servers

How it works The simulation environment uses multiple applications to operate virtual network topologies. Figure 2 indicates how these applications interact to create multiple virtual devices on a single hardware platform.

Figure2: An overview of system operation

To create and control simulated environments using HP Comware 7 based virtual devices, the following components are needed; Windows 8 Host Operating SystemThe Windows platform provided on HP COE computers. The operating system provides the platform for the execution of the other components of the simulation. Oracle VirtualBox HypervisorVirtualBox is installed on an existing host operating system as an application; this host application allows additional guest operating systems, each known as a Guest OS, to be loaded and run, each with its own virtual environment. VirtualBox forms the basis of the virtual environment in which the simulated environment is operated. The Guest OS can be any combination of HP Comware, Cisco IOS XE, Checkpoint Firewalls, Windows or Linux OS, plus many others. Communication between Virtual Devices uses host based UDP tunnels to transport traffic between virtual network interface cards. HP Network SimulatorThe HP Network Simulator is a tool that creates HP Comware 7network topologies for both switched and routed devices in VirtualBox through the use of configuration text file.Included in this document is a typical configuration of a Comware 7 switch device that uses 1Gig ports, however there are many virtual Comware devices that can be configured. A full list of configurable devices and instructions for use can be found in HP Network Simulator for Comware Devices in Appendix A. GNS3GNS3 is open source software that simulates complex networks while being as close as possible to the way real networks perform, all of this without having dedicated network hardware such as routers and switches.GNS3 provides an intuitive graphical user interface to design and configure virtual networks, it runs on traditional PC hardware and may be used on multiple operating systems, including Windows, Linux, and Mac OS X.While GNS3 has been used by network engineers in the past as a Dynamips emulator for older Cisco platforms, in this environment the GUI will be used to control network topologies based on the VirtualBox hypervisor. WiresharkWireshark is a network packet analyser. A network packet analyser will try to capture network packets and tries to display that packet data in as detailed a way as possible.You could think of a network packet analyser as a measuring device used to examine what's going on inside a network cable, just like a voltmeter is used by an electrician to examine what's going on inside an electric cable (but at a higher level, of course).The operation and configuration of Wireshark other than basic connectivity is outside the scope of this guide.

AplicabilityThe following instructions have been validated with the following software versions. Microsoft Windows 8 Oracle VirtualBox version 4.3.10 HP Network Simulator version 7.1.50 GNS3 version 0.8.6

Other software versions may operate as described in this guide but this cannot be guaranteed by the author.

Install VirtualBoxThe following subsections detail the installation of the Oracle VirtualBox hypervisor on the Windows 8 platform.obtain softwareFor the HP Network Simulator to work correctly, use VirtualBox version 4.3.10-93012. Newer versions of this software exist, but they do not integrate with the HP Network Simulator causing an error message to be generated informing the user that VirtualBox is not installed.VirtualBox software can be downloaded from the following location;http://download.VirtualBox.org/VirtualBox/4.3.10/VirtualBox-4.3.10-93012-Win.exeInstallation Once downloaded, install VirtualBox by double-clicking the application Select the default installation settings as detailed below and then select the directory in which to install VirtualBox; Next, select the file associations and the launch icon locations; Proceed with the installation of the VirtualBox network adaptors, this will cause the host machine network connection to drop out while the new adaptors are installed.

Click through a couple of Yes/ Next buttons to install the software. Once installed, the following dialog box should appear; Congratulations, VirtualBox is now installed and when launched the following GUI is displayed; At this point reboot the Windows PC.

Install HP Network simulatorThis section details the installation of the HP Network Simulator version 7.1.50OBTAIN SOFTWAREDownload the HP Network Simulator from the following URL;http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?swItem=nw_130365_1&ac.admitted=1402101741820.876444892.492883150

Installation Launch the downloaded file from item 3.1

Accept the licence agreement and choose the install location

Click finish, the installation is complete.

Install GNS3Install GNS3 to manage network topology creation.Obtain softwareDownload GNS3 v0.8.6 all-in-one with VirtualBox support and wireshark integration from the following location; http://downloads.sourceforge.net/project/gns-3/GNS3/0.8.6/GNS3-0.8.6-all-in-one.exe?r=http%3A%2F%2Fwww.gns3.net%2Fdownload%2F&ts=1402103599&use_mirror=optimate

installation Launch the downloaded file from step 4.1

Accept the licence agreement Choose the start menu folder in which the GNS3 program shortcut should reside

Select the following software features that should be installed. Note that GNS3 will install WinPCAP version 4.1.3 which could interfere with other programs that require this software. Additionally Wireshark will be installed so that connected interfaces in your virtual topologies can be monitored. Choose the file path where the GNS3 software should be installed. Install WinPCAP if not already installed on your PC. This library of functions is required when using packet capture for Wireshark or bridging network interfaces within GNS3.

Accept the license agreement for WinPCAP Choose where WinPCAP should be installed on your PC and then allow the WinPCAP driver to start when the host machine boots Press finish when the installation of WinPCAP has successfully completed.

Wireshark is a standard packet capture and analysis tool that has been integrated into GNS3 and is installed by default with GNS3.

Accept the license agreement

Select the components as shown below;

Select the start menu items and the file associations that Wireshark should be used with.

Choose the install location for Wireshark

The dialog below will be shown if WinPCAP is already installed the host machine. Wireshark and GNS3 require version 4.1.2 or above for correct operation.

Press next and then Finish when the installation of Wireshark has completed. Complete the installation of GNS3 and then press next and finishIntegration with HP Network simulatorThis section details the configuration of the HP Network Simulator version 7.1.50Generate comware switch instancesTo successfully use simulated Comware 7 devices with VirtualBox and GNS3, it is necessary to have a pool of virtual hardware that can be referenced by the GNS3 GUI. The subsections below detail the steps required to create a series of 20x 64bit 8 port 1Gbit Comware 7 switches that can be used in GNS3 topologies.

Launch HNS If the software has been successfully installed, the HP Network Simulator should launch as shown below;

Note:

A common error message occurs indicating that VirtualBox has not been installed if;

1. VirtualBox is not present on the system2. The latest version of VirtualBox has been installed.

To remedy this situation, please install VirtualBox version 4.3.10.

Make the Comware simulator config fileDuring testing it has been discovered that unless all of the interfaces are bound to a VirtualBox interface (either bridged or virtual), then GNS3 has problems referencing them, or there are issues with connectivity using the UDP tunnel general interfaces.

When creating many virtual Comware 7devices, using the Clone feature of VirtualBox either as a full or linked clone does not work correctly with Simware 7, as the resulting cloned machines do not have interfaces that are recognised by the Simware OS. Generating Simware devices using the config file ensures that the instances do not share identity information such as interface and base MAC addresses.

The following configuration embedded in the file below can be cut and pasted into the HNS window. It will create 20 x 8 Port switches using 64bit architecture with 512Mb of RAM. Please modify the file if more memory is required for feature such as MP BGP etc.

Save the projectSave the configuration as a Project using the Save As icon. This name is used in VirtualBox to create the name of the virtual machine group in which the Simware 7 instances will reside.

Create the Simware 7 switch instances Click the icon to start the creation of the Comware 7 switch instances;

Once all of the switches have been created, the message shown below will appear indicating that running all 20 switches will consume 10 GB of RAM and substation CPU usage. Ensure that you have the PC specified with enough RAM if you plan to test large topologies.

Open VirtualBox and see that 20 Comware devices have been created and grouped using the following convention;

ProjectName-deviceX

Configure GNS3The next step is to configure GNS3 to support VirtualBox hosts. This guide does not explain how Dynamips is configured as it is not directly relevant to this simulation environment and requires the use of software from Cisco that does not comply with the usage definition within the licencing agreement.

Start GNS3Start GNS 3 using the icon indicated below, do not follow the configuration steps listed in the start page a just press the OK button.

Configure VirtualBox IntegrationNavigate to the preferences section;Edit > Preferences

Select VirtualBox and ensure that the General Settings match the values indicated below. Press the Test Settings button and ensure that VirtualBox API is started. If you have problems here, make sure that you have the correct path to vboxwrapper.exe

To ensure that the UDP tunnels created between Virtualbox machines do not conflict with installed programs such as Microsoft Lync, it is necessary to change the base UDP port from 20900 to 36000. If this setting has not been modified then connectivity problems will occur between virtual devices. These faults manifest as a unidirectional connection or problems with protocols such as LLDP, LACP and STP.

The next step is to add the Simware devices from VirtualBox to GNS3. Select the tab VirtualBox Guest;

Select a Comware 7 device from the VM List, if this tab is empty, refresh the list. Set the number of NICs to 8 Check the box Show Advanced Options Select the NIC model to e1000 Check the box Enable Console Support. Without this, the Simware device will not correctly boot. Set an Identifier name, this is used to name the devices in your topology Press Save, the VirtualBox Virtual Machines list will now be updated

Repeat the above procedure to add more Simware devices to use in GNS3 projects, the results should look similar to this;

Configure new HP icons for GNS3

To make GNS topologies look more HP inspired, use the icon repository embedded below that matches the Visio icons devised by HPN. Extract the embedded file below into your GNS working directory.

Navigate to the Symbol Manager section;Edit > Symbol Manager

Browse to and select the hp.rcc file that you have just placed in your CNG3 working directory and press the add button. At the bottom of the left hand pan, expand the hp.rcc icon to find the new icons available for use in GNS3.NOTE: Creating new icons for GNS3 requires extra tooling and is outside the scope of this document.

To use the new device shapes, move the icons to the right pane using the arrow button in the centre of the menu. While selecting the icon in the right pane, select the Type as VirtualBox Guest. The icon can be renamed at this point as well. Repeat the above process to add more icons for use in GNS3, the result should match the example below;

Press OK when you have finished adding icons.

Testing Comware switch integration with GNS3Create a two switch topology to test the integration; Open the All Device window by pressing the button >

Drag and drop a HP L3 switch onto the central working pane. As you release the icon, a dialog box opens asking you to detect which VirtualBox guest to open. Select SW1.

Repeat the process for SW2, the result should match the figure below

Select the connect button , right click on the devices, select the interfaces that you want to connect

Start the topology, by pressing the button. Both of the switch devices will now boot to the console and will be ready for configuration. The result should look like the figure below.

NOTE: By default, the first interface is assigned to management, this will always be connected to the VirtualBox host only adaptor and will not be configured by GNS3, handy if the interface is set up for remote management.

Device controlStarting / stopping deviceRight click on a device to display in the device control menu. Device operation can be operated from the menu as displayed below;

Displaying the device consoleMost virtual hosts including Comware 7 devices display through the VirtualBox console which can be brought into focus by clicking;

Devices that redirect their display to the serial console, such as Cisco XRv, vNexus can be used with the console server built into GNS3. To display the serial console click;

Using Wireshark to capture network trafficWireshark can capture traffic from any port in the GNS3 topology by; Right clicking a link to obtain the context menu and pressing capture

Select the interface on which to capture network traffic

Restarting the network node to which the packet capture applies

Starting wireshark on the link

Adding 3rd party Vendor DevicesOne of the advantages of using VirtualBox is that devices from many manufacturers can be configured together using GNS3 to build and control the network topology. The following subsections define the settings required to install 3rd party vendor equipment.VirtualBox Linked ClonesOne of the useful features of VirtualBox is the ability to use Linked Clones, this allows for the install of a master machine image which can then spawn multiple child appliances using a common storage snapshot. This feature can create new devices very quickly while using a small amount of storage on the host PC.Create a Linked Clone Open Oracle VM VirtualBox Select a VM that you wish to clone and click the clone button

Clone machine with a new name and reinitialise the MAC addresses of the NICs. Then Choose Linked Clone and press the Clone button

The clone has been created and is ready to use

Add device to GNS3

A new clone is created that can be added in GNS3 in the same way that the Simware devices were added. Navigate to the VirtualBox Guest settings Press Refresh VM List Select the cloned VM name Select the number of network cards attached Un check Reserve first NIC for VirtualBox NAT to host OS Press save

Cisco CSR1000vThe Cisco CSR1000v can be used when testing integration with Cisco devices with newer IOS XE 12.5 S feature sets supported. By default, the image contains all software features under the Premium licence which can be enabled for trial purposes from the command line.Obtain SoftwareExperimentation shows that the latest version that work correctly on VirtualBox is;csr1000v-universalk9.03.11.01.S.154-1.S1-std.iso

Which can be downloaded from;http://software.cisco.com/download/release.html?mdfid=284364978&softwareid=282046477&release=3.11.1S&flowid=39582

Create the Cisco CSR1000v VM

Create a new virtual machine from the VirtualBox Manager and ensure that the VM device type and memory (2560Mb) settings match the following;

Create a 8Gb thin provisioned storage device with the settings indicated belowNext modify the settings on your newly created CSR1000v VM;

Disable the audio

Enable the serial port in the disconnected state

Configure 4 NICs, binding them to the Host Only adaptor. Ensure your network settings mirror those indicated below;

From the Storage tab, select the install disk .iso that was downloaded in step 6.1.1

The final settings for the VM should match those below.

The final step is to provision a linked clone of the machine using the instructions detailed in 6.1 of this guide.

Add the CSR1000v instances to GNS3Add the CSR1000v instances to GNS3 by navigating to the Preferences / VirtualBox / VirtualBox Guest section and; Choose a name for the instance Select the CSR instance from the VM List Set the number of NICs to 4 Set the NIC model to e1000 Uncheck the Reserve first NIC for VirtualBox NAT to host OS Enable console support and server Press save

The device can now be added to topologies using the VirtualBox icon and can also be customised in Symbol Manager in the same way as the HP Comware devices. When the device boots, the console will be display in the VirtualBox console window;Microsoft Windows 2008 R2 ServerA sample Windows2008 R2 deployment for simple network servicesObtain SoftwareThe Windows 2008R2 .iso can be downloaded directly from MSDN if you have an MSDN licence provided by HP. Alternatively, the following link can provide the .iso and licence key if required;http://swmedia.cv.hp.com/Vendors/Microsoft/NowShowing.aspCreate Virtual MachineCreate a standard Windows 2008 virtual machine with the following settings; 1 Gb RAM 1 vCPU 80% execution cap 2 NICs 100Gb storage (thin provisioned) DVD with the downloaded Windows Server image.

Once the master device is created, run the SYSPREP utility to package the image and then use linked clones when deploying the multiple virtual machines.

Add Windows instance to GNS3

A new clone can be added in GNS3 in the same way that the Simware devices were added.

Navigate to the VirtualBox Guest settings Press Refresh VM List Select the cloned VM name Select the number of network cards attached Un check Reserve first NIC for VirtualBox NAT to host OS Press save

Appendix HP Network Simulator Instructions

Document control informationThe latest version of this document is stored electronically. Any printed copy has to be considered an uncontrolled copy. This document should be compliant with the document control process

Document Owner:Nick ChanningTemplate Version No:1.0

Template Version Date07 Aug 2013

Document Version No:Ver 0.5

Document Sponsor:Peter HockinDocument Version Date30/06/2014

Title:Integration of HP Network Simulator with GNS3Document Acronym:

Document Revision HistoryVer. No.Ver. DatePrepared ByApproved ByAffected Section & Summary of Change

0.108/06/14Nick ChanningDraft Release

0.421/0/614Nick ChanningChanges following review by John Adams

0.530/06/14Nick ChanningChanges following team review

Distribution List

Terms and AcronymousTermDefinition

related documentationDocumentDescriptionurl

HP Network Simulator for Comware Devices

A Comware OS Learning Tool

User Guide

Version: 2.0 March 2014

LEGAL NOTICE

READ BEFORE DOWNLOADING OR OTHERWISE USING THIS HP NETWORK SIMULATOR SOFTWARE PRODUCT

This license Agreement is a legal agreement between (a) you (either an individual or a single entity) (User) and (b) Hewlett-Packard Company or in-country legal entity ("HP") that governs your use of the Software Product (as defined below), which is either i) installed on or made available by HP for use with your HP Networking Product, ii) downloaded and installed by User on any other computing hardware, or iii) made available by HP for use on a standalone basis.

BY CHECKING I ACCEPT, OR BY INSTALLING, COPYING, DOWNLOADING OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO ALL TERMS AND CONDITIONS OF THIS LICENSE AND TO BE BOUND BY THE TERMS OF THIS LICENSE.

License Agreement

1. Software Products. HP has provided or will provide the object code version of HP Simware software and any associated media, printed materials and online or electronic documentation (collectively the Software Product), for the sole purpose of enabling User to use the Software Product for demonstrations and for research purposes (the Purpose).

2. License. HP hereby grants to User a royalty-free, non-assignable license, without the right to grant sublicenses, to use the Software Product only for the Purpose described in Section 1 above. User may make one backup or archival copy of the Software Product.

3. Restrictions on Use. No intellectual property license, and no other license of any kind is granted except for the limited right to use the Software Product only for the Purpose. User shall not reverse engineer, disassemble, or decompile the software portion of the Software Product. User shall not transfer the Software Product to, nor share the Products with, any third party.

4. Intellectual Property Rights. All right, title, and interest to all intellectual property in the Products, including that which may be or become protectable by patent, copyright, trademark, trade secret, or similar laws, shall remain exclusively with HP or its suppliers. No license or other right of any kind is granted by HPs furnishing the Products to User, except for the Purpose as expressly provided in this Agreement.

5. Modifications. HP may alter features, specifications, capabilities, functions, release dates, general availability, or other characteristics of the Products without notice to User. HP maintains all Intellectual Property Rights to modifications made to the Products as a result of any suggested improvements, collaboration with or enhancement request made by the User

6. Term. This Agreement shall remain in effect in perpetuity unless terminated as provided for in Section 12 herein.

1

7. Support. No support will be provided for the Products.

8. Disclaimer of Warranties. User accepts the Products AS IS, with any errors or defects. CUSTOMER ACKNOWLEDGES THAT THE PRODUCTS MAY HAVE ERRORS OR DEFECTS. HP MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND WITH RESPECT TO THE PRODUCTS, AND SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

9. Limitation of Liability. HP shall not be responsible for any loss or damage to User, its customers, or any third parties caused by the Products or by HPs performance under the Agreement. HP SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT, OR ANY OTHER LEGAL THEORY, ARISING OUT OF THIS AGREEMENT.

10. Alterations by User. User shall not alter the Products except with the prior written consent of HP.

11. Assignment. This Agreement is personal to User. User shall not assign or otherwise transfer any rights or obligations under this Agreement.

12. Termination. In the event that User breaches this Agreement, HP may terminate this Agreement immediately upon written notice to User. Further, either party may terminate this Agreement without cause on five days prior written notice. The rights and responsibilities of the parties pursuant to Sections 3, 4, 7, 8, 9, 10, 11and 14 shall survive the expiration or termination of this Agreement.

13. Freeware. Notwithstanding the terms and conditions of this Agreement, all or any portion of the software portion of the Software Product which constitutes non-proprietary HP software or software provided under public license by third parties ("Freeware") is licensed to you subject to the terms and conditions of the software license agreement accompanying such Freeware whether in the form of a discrete agreement, shrink wrap license or electronic license terms accepted at time of download. Use of the Freeware by you shall be governed entirely by the terms and conditions of such license.

14. Governing Law; Entire Agreement. This Agreement shall be governed by New York law, excluding its choice of law provisions. This Agreement contains the entire agreement of the parties relating to the subject matter hereof. Any representation, promise, or condition not explicitly set forth in this Agreement shall not be binding on either party. Any amendments to this Agreement shall be in writing and signed by the authorized representatives of each party.

2

Table of Contents LEGAL NOTICE ..................................................................................................................................................... 1

Introduction ......................................................................................................................................................... 1

Installing HP Network Simulator ....................................................................................................................... 4

Host PC requirements ................................................................................................................................. 4

Installation procedure ................................................................................................................................. 4

Graphical User Interface Introduction (GUI) ................................................................................................. 6

Creating a simulated network project .......................................................................................................... 7

Creating a project from scratch ................................................................................................................. 7

Creating a project based on the default project ................................................................................... 11

Saving a simulated network project ....................................................................................................... 12

Viewing and changing the project storage path ................................................................................... 12

Starting a simulated network ..................................................................................................................... 14

Logging in to a simulated device ................................................................................................................ 15

Logging in through the console port ...................................................................................................... 15

Logging in through Telnet/SSH ............................................................................................................... 16

Physical Network Connection.................................................................................................................. 16

Exporting and importing a simulated network project ........................................................................... 16

Exporting a simulated network project ................................................................................................. 17

Importing a simulated network project ................................................................................................. 17

Closing a simulated network project ......................................................................................................... 17

Deleting a simulated network project ....................................................................................................... 18

Exiting HP Network Simulator .................................................................................................................... 18

Uninstalling HP Network Simulator ........................................................................................................... 18

HP Network Simulator Configuration Examples .......................................................................................... 20

Configuring a simulated network by using a single PC ........................................................................... 20

Network requirements ............................................................................................................................. 20

Configuration procedure .......................................................................................................................... 20

Verifying the configuration ...................................................................................................................... 21

Configuring a simulated network by using multiple PCs ........................................................................ 22




Configuring a simulated network by using a PC and a physical device ................................................. 23



3


Appendix ........................................................................................................................................................... 25

Error Messages ............................................................................................................................................. 25

Troubleshooting HP Network Simulator ................................................................................................... 26

The host PC operates slowly ................................................................................................................... 26

HP Network Simulator cannot start up .................................................................................................. 26

64 Bit devices do not run on 64 Bit Windows........................................................................................ 26

No sufficient memory for MDCs .............................................................................................................. 26

Communication between a virtual machine and its host PC or between virtual machines on different PCs failed .............................................................................................................................. 27

Connection between a virtual machine and its host PC failed ............................................................ 27

Telnet and SSH Utility cannot connect to the device ........................................................................... 27

Connection to the Physical Network Does not Work............................................................................ 27

The virtual machine cannot start up ...................................................................................................... 28

The system time of the virtual machine is not synchronized with that of the host PC ................... 28

The progress bar keeps progressing ..................................................................................................... 28

The virtual disk for the previous HP Network Simulator process remains ........................................ 28

A simulated network project cannot be run .......................................................................................... 28

The virtual machines run slowly ............................................................................................................. 28

The console terminal stops responding to key pressing ..................................................................... 29

Some virtual machines cannot be stopped ........................................................................................... 29

Learn more at ................................................................................................................................................... 30

hp.com/networking ..................................................................................................................................... 30

4

HP Network Simulator User Guide v2.0

Introduction

Comware v7 is HPs high-end network operating system. It provides control and management to switches, routers, unified wired/WLAN controllers and security appliances. HP Network Simulator allows users to learn the Comware v7 interface and features. Using HP Network Simulator, networking professional can create, configure and connect simulated HP fixed-port and modular switches and routers. For example, simulated switches can be aggregated to form an IRF-fabric. HP Network Simulator runs virtual machines on Oracle VM VirtualBox. The performance of the virtual machines is determined by the VirtualBox environment, the Windows OS and the hardware platform.

Note Switching features based on ASICs cannot be tested on the HP Network Simulator.

Table 1: HP Network Simulator cards and devices

Card model Device type Ports

SIM1101 32-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: Serial ports.

SIM1201 64-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: Serial ports.

SIM1102 32-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: POS ports.

SIM1202 64-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: POS ports.

SIM1103 32-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: E1 ports.

SIM1203 64-bit centralized router Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: E1 ports.

SIM1104 32-bit centralized router Port 1: Network management port. Ports 2 to 3: 25-Mbps ATM ports. Port 4: 155-Mbps ATM port. Port 5: 622-Mbps ATM port. Port 6: ADSL ATM port. Port 7: G.SHDSL ATM port. Port 8: E1 ATM port.

1


SIM1204 64-bit centralized router Port 1: Network management port. Ports 2 to 3: 25-Mbps ATM ports. Port 4: 155-Mbps ATM port. Port 5: 622-Mbps ATM port. Port 6: ADSL ATM port. Port 7: G.SHDSL ATM port. Port 8: E1 ATM port.

SIM1105 32-bit centralized router Port 1: Network management port. Port 2: E3 ATM port. Port 3: T1 ATM port. Port 4: T3 ATM port. Port 5: ADSL 2+ port. Port 6: SHDSL_4WIRE ATM port. Port 7: SHDSL_4WIRE_BIS ATM port. Port 8: SHDSL_8WIRE_BIS ATM port.

SIM1205 64-bit centralized router Port 1: Network management port. Port 2: E3 ATM port. Port 3: T1-ATM port. Port 4: T3 ATM port. Port 5: ADSL 2+ port. Port 6: SHDSL_4WIRE ATM port. Port 7: SHDSL_4WIRE_BIS ATM port. Port 8: SHDSL_8WIRE_BIS ATM port.

SIM2101 32-bit centralized switch Port 1: Network management port. Ports 2 to 8: GE ports.

SIM2201 64-bit centralized switch Port 1: Network management port. Ports 2 to 8: GE ports.

SIM2102 32-bit centralized switch Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: 10-GE ports that can operate as FC interfaces.

SIM2202 64-bit centralized switch Port 1: Network management port. Ports 2 to 4: GE ports. Ports 5 to 8: 10-GE ports that can operate as FC interfaces.

SIM3101 (MPU)

32-bit distributed switch or router

Port 1: Network management port. In the Comware system, the number of this port is 0.

SIM3201 (MPU)


Port 1: Network management port. In the Comware system, the number of this port is 0.

SIM3111 (interface card)


Ports 1 to 7: GE ports.



Ports 1 to 3: GE ports. Ports 4 to 7: Serial ports.



Ports 1 to 3: GE ports. Ports 4 to 7: POS ports.



Ports 1 to 3: GE ports. Ports 4 to 7: E1 ports.

2




Ports 1 to 2: 25-Mbps ATM ports. Port 3: 155-Mbps ATM port. Port 4: 622-Mbps ATM port. Port 5: ADSL ATM port. Port 6: G.SHDSL ATM port. Port 7: E1 ATM port.



Port 1: E3 ATM port. Port 2: T1 ATM port. Port 3: T3 ATM port. Port 4: ADSL 2+ port. Port 5: SHDSL_4WIRE ATM port. Port 6: SHDSL_4WIRE_BIS ATM port. Port 7: SHDSL_8WIRE_BIS ATM port.



Ports 1 to 7: GE ports.



Ports 1 to 3: GE ports. Ports 4 to 7: Serial ports.



Ports 1 to 3: GE ports. Ports 4 to 7: POS ports.



Ports 1 to 3: GE ports. Ports 4 to 7: E1 ports.



Ports 1 to 2: 25-Mbps ATM ports. Port 3: 155-Mbps ATM port. Port 4: 622-Mbps ATM port. Port 5: ADSL port. Port 6: G.SHDSL port. Port 7: E1 ATM port.



Port 1: E3 ATM port. Port 2: T1 ATM port. Port 3: T3 ATM port. Port 4: ADSL 2+ port. Port 5: SHDSL_4WIRE ATM port. Port 6: SHDSL_4WIRE_BIS ATM port. Port 7: SHDSL_8WIRE_BIS ATM port.

3


Installing HP Network Simulator

Host PC requirements

For performance purposes, the PC running HP Network Simulator must meet the requirements listed in Table 2.

Table 2: Host PC requirements

Item Specifications

CPU CPU frequency: 3.0 GHz

SDRAM 4 GB

Hardware 80 GB

Operating system Windows 7 or later

Installation procedure

Note Windows administrator rights are required to install and uninstall HP Network Simulator.

Important To reinstall HP Network Simulator, the current HP Network Simulator software must be installed first.

1. Obtain and install Oracle VM VirtualBox Release 4.2.18 or later.

VM VirtualBox can be downloaded from: www.VirtualBox.org.

2. Obtain the installation package HNS_7.1.50-Setup.exe.

3. Double-click the installation package to start the installation.

4. The welcome page appears.

Figure 1: Welcome Page

5. Click Next.

The license agreement page appears.

4


Figure 2: License Agreement

6. Select I accept the terms of the License Agreement and click Next.

Figure 3: Specifying the installation path

7. Enter or navigate to the destination folder and click Install. To use the default folder C:\Program Files, click Install directly.

The destination folder path and name can contain up to 128 characters. Percent signs (%) and pound signs (#) are not allowed.

After clicking Install, the installation progress page appears.

5


Figure 4: Installation progress page

After the installation is completed, the completion page appears.

Figure 5: Completion page

8. Click Finish

A desktop shortcut and a start menu shortcut are created. Either of them can be clicked to start HP Network Simulator.

Graphical User Interface Introduction (GUI) The HP Network Simulator GUI is divided in four sections.

Title bar:

If no project has been opened or the current project is not saved yet, the title bar displays HP Network Simulator

If a project has been opened or the current project has been saved, the title bar displays Project name-HP Network Simulator

Menu bar:

File - Project operations menu Edit - Edit functions menu

6


Simulate - Simulation functions menu Setting - Configuration menu Help - Help document and version information menu

Quick launch bar:

New button - Creates a project Open button - Opens a project Delete button - Deletes a project Save button - Saves a project Save as button - Saves the project as another project Import button - Imports a project Export button - Exports a project Run button - Runs a project Stop button - Stops a project

Configuration item editing area:

Displays the configuration items in the white area and the configuration item numbers in the gray area. The configuration items can be edited

Figure 6: HP Network Simulator GUI

(1) Title bar (2) Menu bar

(3) Quick launch bar (4) Configuration item editing area

Creating a simulated network project

Creating a project from scratch

A simulated network project consists of two parts:

Device parameter configuration items

7


Connection parameter configuration items

The device parameter configuration items must be placed before the connection parameter configuration items.

Project syntax

A simulated network project must follow these syntax rules:

Each configuration item defines one parameter and occupies one line A device parameter configuration item must be in the format Parameter = value. A correct keyword

is displayed in blue A connection parameter configuration item must be in the format Parameter Parameter.

Multiple hyphens can be entered between the angle brackets Some parameters consist of sub-parameters. Sub-parameters are separated by colons (:). Enter a

tab or space after a sub-parameter to configure a value for it A line beginning with a pound sign (#) is a comment line, which is displayed in green Blank lines, tabs, and spaces can be inserted for information grouping purposes

Device parameters

The following device parameters are used to create the simulated devices in the project.

Table 3: Device Parameters

Parameter Description Remarks

device_id Configures a device ID in the range of 1 to 120.

Required. Configuration for a device must start with this parameter. A device ID uniquely identifies a device in the network. A simulated network project supports up to 30 devices. Example: device_id = 1

device_model Configures the device model in the format SIMxxxx, where each x indicates a digit. The first two digits are configurable. The last two digits are fixed at zero.

Required. Configure this parameter before configuring the board parameter. Configuration for a device can contain only one device_model configuration item. For information about supported devices, see Table 1. Example: device_model = SIM1100

board Configures a card in the device in the following format: board = [slot x : ] SIMxxxx [: memory_size x ] slot x: Configures the slot number of a card on a distributed device. Slots 0 to 1 are for MPUs. Slots 2 to 7 for interface cards. This part is required for a distributed device. SIMxxxx: Configures the card model. The first two digits must be the same

Required. Only one board configuration item can be configured for a card. A simulated network project supports up to 120 cards. Example: board = slot 0 : SIM1101 : memory_size 500

8


as the two configurable digits in the device model. For information about supported cards, see Table 1. memory_size: Configures the size of the card's memory. This part is optional. The memory size varies with device types: 32-bit centralized router300 MB to

3072 MB, 512 MB by default. 32-bit centralized switch400 MB to

3072 MB, 512 MB by default. 64-bit centralized device500 MB to

3072 MB, 768 MB by default. 32-bit MPU (for a distributed device)

400 MB to 3072 MB, 512 MB by default. 64-bit MPU (for a distributed device)

500 MB to 3072 MB, 768 MB by default. 32-bit interface card (for a distributed

device)200 MB to 3072 MB, 384 MB by default.

64-bit interface card (for a distributed device)300 MB to 3072 MB, 512 MB by default.

host_ip Configures the IP address of the host PC in the format host_ip = x.x.x.x.

Optional. This parameter is required only when the simulated devices reside on different host PCs. The host PCs must be able to reach each other. Example: host_ip = 192.168.0.1

Important The default memory size may not be enough for the Telnet/SSH server to run. To connect to a device using Telnet or SSH declare a larger device memory_size in the project configuration file. Example:

board = slot 0 : SIM3101 : memory_size 1024

Connection parameters

Connection parameters configure connections of the following types:

Device-to-device connectionConnection between two simulated devices Device-to-host connectionConnection between a simulated device and its host PC

Up to 200 connection parameters can be configured after all simulated devices' parameters have been entered.

9


Table 4: Connection parameters

Type Syntax Remarks

Device-to-device connection parameter

device_id x : [ slot x : ] interface x device_id x : [ slot x : ] interface x device_id x: Specifies the device ID. slot x: Specifies the slot number of the interface card. interface x: Specifies the number of the interface.

Optional. The two device IDs must be different. The value range of the interface number depends on the card model.

Device-to-host connection parameter

device_id x : [ slot x : ] interface x host : NIC name device_id x: Specifies the device ID. slot x: Specifies the slot number of the interface card. interface x: Specifies the number of the interface. NIC name: Specifies the name of the host PC's NIC. If the name contains spaces, double-quote the name.

Optional. The device information must be on the left side of the angle brackets. To obtain the NIC name, right-click the NIC and view its name under Connect using, as shown in Figure 7.

Figure 7: Obtaining the NIC name

10


NOTE HP recommends choosing the VirtualBox Host-Only virtual NIC for connecting the simulated device and its host PC.

Choose the physical NIC for connecting a simulated device and a physical router or switch. HP recommends using the physical NIC for only one simulated device.

To manage a simulated device through Telnet or SSH one of its ports needs to be mapped to one of the hosts network interfaces. The interface to map will depend on if the Telnet/SSH utility is running on the same or a different host than the simulated device.

Table 5: Telnet/SSH Interface mapping requirements

Telnet/SSH Utility Link Configuration IP Address to be used

On the same PC Device x : interface 1 host: VirtualBox NIC name Management Ethernet port

On another PC Device x : interface y host: Physical NIC name (with y: 2-8) VLAN 1 Interface

Creating a project based on the default project

HP Network Simulator provides a default simulated network project. This project contains one distributed device and one centralized device connected to each other. You can modify the default simulated network project to create a new project.

To create a simulated network project based on the default project:

1. Select File > New, or click the New button on the quick launch bar.

2. The default simulated network project is imported and displayed in the configuration item editing area, as shown in Figure 8.

3. Modify the default simulated network project.

4. Save the project.

11


Figure 8: Default simulated network project

Saving a simulated network project

1. Choose the configuration saving mode:

To save the configuration to the current project, select File > Save or click the Save button on the quick launch bar

To save the configuration to a new project, select File > Save As or click the Save as button on the quick launch bar

2. Enter the project name in the popup dialog box, as shown in Figure 9

The project name can be a case-insensitive string of up to 20 characters. Valid characters include letters, numbers, and underscores (_)

If the name of an existing project is entered, the existing project will be overwritten 3. Click OK

Figure 9: Entering the project name

Viewing and changing the project storage path

Projects are saved to the path C:\Users\\HNS VNs by default. The storage path can be changed.

After changing the storage path:

12


All projects created after the change will be saved in the new path If an existing project is edited, the project is still saved in the old path If a new project is created with the name of an existing project, the new project is saved in the new

path. The existing project is deleted

To view and change the storage path:

1. Select Setting > Project Directory. The current path is displayed, as shown in Figure 10

2. To change the path, enter the new path.

The path must be an existing absolute path. The entire path information can have up to 128 characters and cannot contain the percent sign (%)

Figure 10: Setting the storage path

3. Click OK

13


Starting a simulated network

1. Select File > Open or click the Open button on the quick launch bar to open the project for the simulated network

2. Select Simulate > Run, or click the Run button on the quick launch bar

A progress bar appears and HP Network Simulator begins to resolve the configuration items in the project. During this period, no operation is allowed

Figure 11: Progress bar during the Run operation

If the configuration of the simulated network project has syntax errors, an error message is displayed. The configuration must be revised and the simulated network project rerun. For more information about the error messages, see Error messages. If the amount of the memory space required by the virtual machines is greater than 3 GB, HP Network Simulator displays a notification and continues to resolve the project. After HP Network Simulator finishes resolving the configuration items, Oracle VM VirtualBox Manager is displayed together with the virtual machines. See Figure 12. In the Manager, the name of a virtual machine is in one of the following formats:

Centralized device - project name-device ID Distributed device - project name-device ID-card slot number

14


Figure 12: VirtualBox Manager

3. Select the virtual machines to be started and click the Start button :

To start a centralized device, select the virtual machine To start an IRF fabric or a distributed device in standalone mode, select all virtual machines for

the fabric or device

To start multiple virtual machines, make sure the memory space of the host PC can satisfy the memory requirements of the virtual machines. Rerunning the current simulated network project does not restart the running virtual machines.

Important If a simulated network project is modified after running the project, the project must be rerun to make HP Network Simulator resolve the new configuration. Otherwise, the configuration changes do not take effect when the virtual machines are started.

For successful communication between two devices on different PCs, the two devices must use the same software version and the same simulated network project.

Logging in to a simulated device

Logging in through the console port

For a centralized device, the console CLI is displayed automatically after the virtual machine is started. The virtual machine can be managed at the CLI as with the CLI of a physical centralized device.

For a distributed device, the console CLI of the active MPU is displayed automatically after the virtual machines are started. The entire distributed device can be managed at the CLI of the active MPU.

15


Logging in through Telnet/SSH

1. The simulated network project must has a connection configured between the simulated device and the virtual NIC of the host PC. HP recommends that you use the simulated device's network management port for the connection.

2. The simulated network project must be compiled before starting the virtual machines.

3. At the console CLI of the simulated device, do the following:

Assign an IP address to the interface connected to the host PC's NIC. Make sure this IP address is in the same subnet as the NIC's IP address

Configure Telnet or SSH login. For more information about Telnet and SSH configuration commands, see Fundamentals Command Reference and Security Command Reference

4. Run the Telnet or SSH client on a PC. Use the IP address of the simulated device's virtual interface as the destination address.

Device memory requirements for Telnet and SSH

The default memory size may not be enough for the telnet server to run. Declare a larger device memory_size in the board configuration statement. Example:

# Device B device_id = 2 # Device type: 32-bit distributed device device_model = SIM3100 # Card models and slot numbers board = slot 0 : SIM3101 : memory_size 1024

Telnet/SSH Interface mapping requirements

To manage a simulated device through Telnet or SSH one of its ports needs to be mapped to one of the hosts network interfaces. The interface to map will vary if the Telnet/SSH utility is running on the same or a different host than the simulated device.


Telnet/SSH Connection Link Configuration IP Interface on Device

From the same PC Device x : interface 1 host: VirtualBox NIC name Management Ethernet port

From another PC Device x : interface y host: Physical NIC name (y: 2-8) VLAN 1

Physical Network Connection

To connect the simulated network to a physical network device one of the devices ports must be linked to the PCs physical NIC.

Table 7: Physical Network Connection Requirements

Link Configuration IP Interface on Device

Device x : interface y host: Physical NIC name (y: 2-8) VLAN 1

Exporting and importing a simulated network project A simulated network project can be deployed on multiple PCs. To do so, export the simulated network project from HP Network Simulator and import the project on the destination PCs.

The exported or imported project has the same configuration as the source project, which includes the following:

16


Simulated network project configuration. Configuration made on the virtual machines while the virtual machines were running.

Exporting a simulated network project

1. Select File > Export, or click the Export button on the quick launch bar.

2. A dialog box appears.

3. Enter the directory for saving the exported project, or navigate to the directory.

4. The directory information can have up to 128 characters.

5. Click OK.

The exported project is saved to a file named in the format project name.hns.

Figure 13: Exporting a simulated network project

Importing a simulated network project

1. Select File > Import, or click the Import button on the quick launch bar.

2. A dialog box appears, as shown in Figure 14.

3. Select the .hns project file to be imported in the Select File box.

4. Specify a name for the imported project in the Import As box. To use the original project name, skip this step.

5. Click OK.

If the project name is identical to the name of an existing project, the imported project overwrites the existing project.

Figure 14: Importing a simulated network project

Closing a simulated network project To close a virtual machine:

1. Click the Close button at the upper right corner of the virtual machine window.

2. The Close Virtual Machine window appears.

3. To save the operation information of the virtual machine for the next startup, select Save the machine state. To quit without saving operation information, select Power off the machine.

4. Click OK.

17


Figure 15: Closing a virtual machine

To close the entire simulated network project without saving the operation information:

1. Select Simulator > Stop or click the Stop button on the quick launch bar.

2. Create or open another simulated network project.

Deleting a simulated network project 1. Select File > Remove, or click the Delete button on the quick launch bar.

Figure 16: Selecting the simulated network project to be deleted

2. Select the simulated network project to be deleted and click OK.

The confirmation dialog box appears.

Figure 17: Confirming the operation

3. Click Yes.

Exiting HP Network Simulator 1. Select File > Exit, or click the Close button at the upper right corner of HP Network Simulator.

Exiting HP Network Simulator stops the running simulated network.

Uninstalling HP Network Simulator

Important Before uninstalling HP Network Simulator, delete all simulated network projects created by other users. When installing HP Network Simulator again, such simulated network projects left on the PC cannot be used. To ensure complete removal of virtual machines, HP Network Simulator must be uninstalled before uninstalling VirtualBox.

18


1. Close the VirtualBox manager and all virtual machines.

2. On the Windows operating system, select Start > Control Panel > Programs and Features, select HP Network Simulator, and then click Uninstall.

3. The Uninstall window appears.

Figure 18: Uninstalling HP Network Simulator

4. Click Uninstall.

Figure 19: Completing the HP Network Simulator uninstall process

5. To remove all simulated network projects that you created, select the Remove the projects check box. To keep the simulated network projects for future use, clear the check box.

If you install HP Network Simulator again, the simulated network projects kept when you uninstall the simulator can be used.

6. Click Finish

19


HP Network Simulator Configuration Examples

Configuring a simulated network by using a single PC

Network requirements

As shown in Figure 20, use a single PC to simulate the following devices:

Centralized device Device A Distributed device Device B:

Active MPU in slot 0 Standby MPU in slot 1 Interface cards in slots 2 and 3

Configure the following connections to use the two simulated devices to form a network:

Connection between M-Ethernet 1/0/1 on Device A and the virtual NIC of the PC Connection between GigabitEthernet 0/0/2 on Device A and GigabitEthernet 2/0/2 on Device B Connection between GigabitEthernet 0/0/3 on Device A and GigabitEthernet 3/0/2 on Device B

Figure 20: Network Diagram

Configuration procedure

1. Configure simulated network project topo1. #********************************************************************* # Device A device_id = 1 # Device type: 32-bit centralized device device_model = SIM1100 # Card model: SIM1101 board = SIM1101 #********************************************************************* # Device B device_id = 2 # Device type: 32-bit distributed device device_model = SIM3100 # Card models and slot numbers board = slot 0 : SIM3101 : memory_size 1024 board = slot 1 : SIM3101 board = slot 2 : SIM3111 board = slot 3 : SIM3112

20


#********************************************************************* # Connections between Device A and Device B # Connection between interface 1 on Device A and the virtual NIC of the PC. device 1 : interface 1 host : "VirtualBox Host-Only Ethernet Adapter" # Connection between interface 2 on Device A and # interface 2 on the card in slot 2 of Device B. device 1 : interface 2 device 2 : slot 2 : interface 2 # Connection between interface 3 on Device A and # interface 2 on the card in slot 3 of Device B. device 1 : interface 3 device 2 : slot 3 : interface 2 #***********************************************************************

Note The VirtualBox Host-Only NIC might have different names on different types of operating systems and different numbers on different versions of operating systems.

2. Start the virtual machines:

Select Simulate > Run, or click the Run button on the quick launch bar of the HP Network Simulator to start the VirtualBox manager

Select topo1-device1 and click the Start button on the VirtualBox manager to start Device A. Select topo1-device2-slot0, topo1-device2-slot1, topo1-device2-slot2, and topo1-device2-

slot3, and click the Start button to start Device B

3. On the PC operating system, configure an IP address and mask for the virtual NIC. (Details not shown)

4. At the console CLI of the simulated device, assign IP addresses to interfaces:

Assign interface M-Ethernet1/0/1 an IP address that is in the same subnet as the IP address of the PC NIC

system-view [Sysname] interface m-ethernet 1/0/1 [Sysname-M-Ethernet 1/0/1] ip address 20.0.0.1 24 Assign IP addresses to interfaces GigabitEthernet0/0/2, GigabitEthernet0/0/3,

GigabitEthernet2/0/2, and GigabitEthernet3/0/2. (Details not shown.)

Verifying the configuration

1. Verify that you can log in to Device A through Telnet:

At the console CLI of the simulated device, configure Telnet login. [Sysname] line vty 0 4 [Sysname-line-vty0-4] authentication-mode none [Sysname-line-vty0-4] user-role network-admin [Sysname-line-vty0-4] quit [Sysname] telnet server enable On the PC operating system, run the Telnet or SSH client. Use the IP address 20.0.0.1 and the

port number 23. You should be able to log in to Device A

2. Verify that the interfaces for the configured three connections can ping each other. (Details not shown)

Important Simulated devices have all their interfaces shutdown by default (administratively down) except for the Ethernet management port. During the configuration process bridged and routed ports, VLAN interfaces, bridge aggregation interfaces, etc. must be enabled using the undo shutdown command.

21


Configuring a simulated network by using multiple PCs


As shown in Figure 21, use two PCs to simulate the following devices:

Centralized device Device A on PC 1 Distributed device Device B on PC 2:

Active MPU in slot 0 Interface cards in slots 2, 3, and 4

Configure the following connections to use the two simulated devices to form a network:

Connection between GigabitEthernet 0/0/2 on Device A and GigabitEthernet 2/0/2 on Device B Connection between Serial 0/0/5 on Device A and Serial 2/0/4 on Device B



1. Configure simulated network project topo2. #********************************************************************** # Device A device_id = 1 # Device type: 32-bit centralized device device_model = SIM1100 # Host IP: IP address of PC 1 host_ip = 192.168.20.63 # Card model SIM1101 board = SIM1101 #********************************************************************** # Device B device_id = 2 # Device type: 32-bit distributed device device_model = SIM3100 # Host IP: IP address of PC 2 #(This address and the IP address of PC1 must be able to reach each other) host_ip = 192.168.20.53 # Card models and slot numbers board = slot 0 : SIM3101 board = slot 2 : SIM3112 board = slot 3 : SIM3113 board = slot 4 : SIM3114 #********************************************************************** # Connections between Device A and Device B

22


device 1 : interface 2 device 2 : slot 2 : interface 2 device 1 : interface 5 device 2 : slot 2 : interface 4 #**********************************************************************

Note To ensure successful communication between devices on different PCs, make sure the two devices use the same software version and simulated network project.

2. Start the simulated network:

# On each host PC, select Simulate > Run, or click the Run button on the quick launch bar of HP Network Simulator to start the VirtualBox manager

# On PC 1, select topo2-device1 and click the Start button on the VirtualBox manager to start Device A

# On PC 2, select topo2-device2-slot0, topo2-device2-slot2, topo2-device2-slot3 and topo2-device2-slot4, and click the Start button on the VirtualBox manager to start Device B

3. At the console CLI of the simulated device, assign IP addresses to interfaces GigabitEthernet0/0/2, GigabitEthernet2/0/2, Serial0/0/5, and Serial2/0/4. (Details not shown)


1. Verify that the console CLI of each simulated device appears after the virtual machines are started.

2. Verify that the interfaces for the network connections can ping each other. (Details not shown.)


Configuring a simulated network by using a PC and a physical device


As shown in Figure 22, use the PC to simulate a centralized device.

Configure the following connections to use the simulated device and the physical device to form a network:

Connection between GigabitEthernet 1/0/2 on Device A and the physical NIC of the PC Connection between the physical NIC of the PC and GigabitEthernet 4/7/0/1 on Device B

Note On the virtual machine, only the Ethernet port is available for communicating with the physical device.

23




1. On HP Network simulator, configure simulated network project topo3. #********************************************************************* # Device A device_id = 1 # Device type: 32-bit centralized device device_model = SIM2100 # Card model SIM2101 board = SIM2101 #********************************************************************* # Connection between interface 2 on Device A and the physical NIC of the PC. device 1 : interface 2 host : "Intel(R) 82579LM Gigabit Network Connection" #*********************************************************************

2. Connect GigabitEthernet 4/7/0/1 on Device B to the physical NIC of the PC.

3. Power on Device B.

4. On HP Network simulator, select Simulate > Run, or click the Run button on the quick launch bar to start the VirtualBox manager.

5. Select topo2-device1 and click the Start button on the VirtualBox manager to start Device A.

6. At the console CLI of the simulated device, assign IP addresses to interfaces GigabitEthernet1/0/2 and GigabitEthernet4/7/0/1. (Details not shown.)


1. Verify that the console CLI of each simulated device appears after the virtual machines are started.

2. Verify that the interfaces for the network connection can ping each other. (Details not shown)


24


Appendix

Error Messages Table 8: Error Message Description

Error message Description

Line number: Invalid parameter. The parameter is invalid.

Line number: Configuration for a device must start with device_id.

Other parameter have been configured before the device_id parameter for the device has been entered.

Line number: The parameter can't be configured more than once on the same device.

The parameter for the device has already been configured.

Line number: Configuration of the previous device is incomplete.

Some parameters required for the previous device are missing.

Line number: System configuration must precede link configuration.

Device parameter configuration must be configured before entering connection parameters.

Line number: Invalid value. The value is invalid, not in the value range, or in incorrect format.

Line number: One interface can have only one connection.

There is already a connection that uses the interface.

Line number: The device model is not configured yet or doesn't support the card.

The device model has not been configured, or the device model does not support the card model.

Line number: Number of connections exceeded the limit.

The number of connections has reached the limit.

Line number: Number of devices exceeded the limit.

The number of devices has reached the limit.

Line number: Number of boards exceeded the limit.

The number of boards has reached the limit.

Line number: The card is installed in an incorrect slot.

The slot number for an MPU or interface card is incorrect. This message might be displayed only for a distributed device.

Line number: Version file required for the previous device doesn't exist.

The system does not find the version file of the previous device.

Line number: Invalid interface number. The specified interface does not exist.

Line number: The network adapter doesnt exist.

The specified NIC does not exist.

Line number: Unknown error. The system cannot identify the error.

The project is being used. The simulated network project is being used.

Failed to run the project. The simulated network project has been resolved successfully, but it failed to operate.

Run the project successfully. The simulated network project is now operating correctly.

25


No valid configuration found. No configuration has been made for the project.

Starting all virtual machines of the project requires a lot of memory space and will slow the system down. Please start only the virtual machines that you need to use.

The memory space required for the virtual machines exceeds 3 GB. To ensure smooth system operation, start only necessary virtual machines.

Troubleshooting HP Network Simulator

The host PC operates slowly

Analysis

The virtual machines consumed more than 3 GB memory space.

Solution

Start only necessary virtual machines to reduce the memory space usage.

HP Network Simulator cannot start up

Analysis

Some files in the installation folder have been deleted, moved, or modified.

Solution

Uninstall HP Network Simulator and reinstall it. HP recommends that not deleting, changing, or moving files in the installation folder.

64 Bit devices do not run on 64 Bit Windows

Analysis

VT-x/AMD-V hardware acceleration / virtualization support must be enabled in the PCs BIOS.

Solution

If VT-x or AMD-V cannot be enabled, implement the 32 bit version of the simulated devices.

No sufficient memory for MDCs

Analysis

The memory space configured for the virtual machine is not sufficient for creating MDCs.

Solution

Configure a memory space greater than 1024 MB for each MPU. Configure a memory space greater than 768 MB for each interface card.

26


Communication between a virtual machine and its host PC or between virtual machines on different PCs failed

Analysis

Packets might have been blocked by the firewall or the anti-virus software.

Solution

Disable the packet blocking function of the firewall or anti-virus software.

Connection between a virtual machine and its host PC failed

Analysis

The connection configuration was changed while the virtual machine was running.

Solution

Rerun the project to make HP Network Simulator resolve the new configuration. Otherwise, the configuration changes do not take effect when you start virtual machines. HP recommends not changing the configuration for a virtual machine while the virtual machine is running.

Telnet and SSH Utility cannot connect to the device

Analysis: Option 1

The default memory size may not be enough for the telnet server to run.

Solution

Declare a larger device memory_size in the network configuration file. Example:

#********************************************************************* # Device B device_id = 2 # Device type: 32-bit distributed device device_model = SIM3100 # Card models and slot numbers board = slot 0 : SIM3101 : memory_size 1024

Analysis: Option 2

To manage a simulated device through Telnet or SSH one of its ports needs to be mapped to one of the hosts network interfaces.

Solution

The interface to map will vary if the Telnet/SSH utility is running on the same or a different host than the simulated device.


Telnet/SSH Connection Link Configuration IP Interface on Device

From the same PC Device x : interface 1 host: VirtualBox NIC name Management Ethernet port

From another PC Device x : interface y host: Physical NIC name (y: 2-8) VLAN 1

Connection to the Physical Network Does not Work

To connect the simulated network to a physical network device, one port of the simulated device need to be mapped to the physical NIC of the PC.

27


Table 10: Physical Network Connection Requirements

Link Configuration IP Interface on Device

Device x : interface y host: Physical NIC name (y: 2-8) VLAN 1

The virtual machine cannot start up

Analysis

The Windows system is configured with a high notification level that prohibits the virtual machine from running.

Solution

Go to User Account Control Settings in Control Panel, and drag the slider down to Never notify.

The system time of the virtual machine is not synchronized with that of the host PC

Analysis

It is normal that the system time of the virtual machine is later than that of its host PC.

The progress bar keeps progressing

Analysis

Operations have been performed on HP Network Simulator before the progress bar disappears.

Solution

Stop performing operations on HP Network Simulator. The progress bar will show the progress correctly.

The virtual disk for the previous HP Network Simulator process remains

Analysis

HP Network Simulator was closed while it was resolving a project.

Solution

Manually delete the remaining virtual disk. To avoid this problem, do not stop HP Network Simulator before the startup progress bar disappears.

A simulated network project cannot be run

Analysis

The simulated network project might have been damaged.

Solution

Run the simulated network project again. If the run operation still fails, delete the simulated network project and configure a new one.

The virtual machines run slowly

Analysis

The VT-X or AMD-V function was disabled or was not supported on the host PC. If the VT-X or AMD-V function is disabled, the icon in the red square is gray, as shown in Figure 23.

Solution

Enable the VT-X or AMD-V function on the PC if the PC supports the function.

28


Figure 23: Verifying the status of the VT-X or AMD-V function

The console terminal stops responding to key pressing

Analysis

If too many keys are pressed while a virtual machine is starting up, the console CLI might stop responding.

Solution

Do not press keys while the virtual machine is starting up.

Some virtual machines cannot be stopped

Analysis

VirtualBox bug. When a stop operation Is performed, some virtual machines might not be stopped if the virtual machines are using large amounts of memory.

Solution

Use the operating system's task manager to terminate the VirtualBox manager.

Figure 24: Remaining in the [Stopping] state

29

Learn more at

hp.com/networking

Sign up for updates

hp.com/go/getupdated Share with colleagues

Rate this document

Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Created March 2014

LEGAL NOTICEIntroductionInstalling HP Network SimulatorHost PC requirementsInstallation procedureGraphical User Interface Introduction (GUI)Creating a simulated network projectCreating a project from scratchProject syntaxDevice parametersConnection parameters

Creating a project based on the default projectSaving a simulated network projectViewing and changing the project storage path

Starting a simulated networkLogging in to a simulated deviceLogging in through the console portLogging in through Telnet/SSHDevice memory requirements for Telnet and SSHTelnet/SSH Interface mapping requirements

Physical Network Connection

Exporting and importing a simulated network projectExporting a simulated network projectImporting a simulated network project

Closing a simulated network projectDeleting a simulated network projectExiting HP Network SimulatorUninstalling HP Network Simulator

HP Network Simulator Configuration ExamplesConfiguring a simulated network by using a single PCNetwork requirementsConfiguration procedureVerifying the configuration

Configuring a simulated network by using multiple PCsNetwork requirementsConfiguration procedureVerifying the configuration

Configuring a simulated network by using a PC and a physical deviceNetwork requirementsConfiguration procedureVerifying the configuration

AppendixError MessagesTroubleshooting HP Network SimulatorThe host PC operates slowlyAnalysisSolution

HP Network Simulator cannot start upAnalysisSolution

64 Bit devices do not run on 64 Bit WindowsAnalysisSolution

No sufficient memory for MDCsAnalysisSolution

Communication between a virtual machine and its host PC or between virtual machines on different PCs failedAnalysisSolution

Connection between a virtual machine and its host PC failedAnalysisSolution

Telnet and SSH Utility cannot connect to the deviceAnalysis: Option 1SolutionAnalysis: Option 2Solution

Connection to the Physical Network Does not WorkThe virtual machine cannot start upAnalysisSolution

The system time of the virtual machine is not synchronized with that of the host PCAnalysis

The progress bar keeps progressingAnalysisSolution

The virtual disk for the previous HP Network Simulator process remainsAnalysisSolution

A simulated network project cannot be runAnalysisSolution

The virtual machines run slowlyAnalysisSolution

The console terminal stops responding to key pressingAnalysisSolution

Some virtual machines cannot be stoppedAnalysisSolution

Learn more athp.com/networking

Simware7 instances (3).txt#*********************************************************************#device 1device_id = 1

#device type is boxdevice_model = SIM2200

#board type board = SIM2201 : memory_size 512

#*********************************************************************#device 2device_id = 2



#*********************************************************************#device 3device_id = 3



#*********************************************************************#device 4device_id = 4



#*********************************************************************#device 5device_id = 5



#*********************************************************************#device 6device_id = 6



#*********************************************************************#device 7device_id = 7



#*********************************************************************#device 8device_id = 8



#*********************************************************************#device 9device_id = 9



#*********************************************************************#device 10device_id = 10



#*********************************************************************#device 11device_id = 11



#*********************************************************************#device 12device_id = 12



#*********************************************************************#device 13device_id = 13



#*********************************************************************#device 14device_id = 14



#*********************************************************************#device 15device_id = 15



#*********************************************************************#device 16device_id = 16



#*********************************************************************#device 17device_id = 17

Integrating the HP Network Simulator With GNS3 v.0.5

Documents

hp network simulator165

hp comware

network topologies

network traffic276adding

network based technologies

multiple network technologies

new hp icons

gns3 integration