Router Platform(s): 7200, 3600
IOS Version: 12.4(11)T1, 12.4(18)
IOS Feature Set: Service Provider, Enterprise
IOS File Name: c7200-spservicesk9-mz.124-11.T1.bin, c3640-js-mz.124-18.uncompressed.bin
idlepc: 0x61280c1c, 0x60428c4c
IOS Image Uncompressed before use: Yes , Yes
IOS Memory Requirements: 256Mb, 128Mb
Average Dynamips.exe CPU Utilization: 30%

Comments:

The configuration in this article contains two devices, one 7200 serving as the router and one 3600 used as a network switch.  The point of this lab is to demonstrate the use of Etherchannel and also Vlan Trunking in an Etherchannel configuration (2 separate scenarios).  There are two .net configuration files included.  One file contains the 7200 setup with etherchannel and the 3640 acting as the switch has the etherchannel interfaces in access mode (assigned to vlan 10).  The other .net file is basically the same scenario, with Vlan Trunking added.

Other Notes:

You will need to create vlan 10 on the 3640 after it boots.  You can do this by getting to an enable prompt and typing:

vlan database
vlan 10
exit

Failure to do this will prevent you from pinging the layer3 interface configured on the 3640 from the 7200 router.

Link to configuration files:

Dynagen GNS3 configuration files

The TACACS+ Windows executable can be downloaded from here.

First step is to extract TACACS+ zip file into a directory of your choice (in this example, I used c:\tacacs). Next, edit the configuration file as needed to define server characteristics and users. Be sure to edit the configuration file in an editor that supports UNIX file types. You will be fine if you open the existing file in an editor that doesn’t add <CRLF> characters at the end of each line (so don’t use Windows notepad, although Wordpad will be fine).

Start the TACACS server with the following command:

tac_plus -C tac.cfg

The warning regarding not running tac_plus as root can safely be ignored. To verify the tacacs+ server is running, open task manager and go to the processes tab – you should see tac_plus.exe running:

If you need to stop the tacacs server, just select it in the task manager list and click on End Process.

Dynagen configuration with one 3640 router instance

]]> http://www.xpresslearn.com/tools/dynamips/using-tacacs-with-dynagen-dynamips/feed 1 http://www.xpresslearn.com/tools/dynamips/dynagen-configuration-using-five-3640-routers http://www.xpresslearn.com/tools/dynamips/dynagen-configuration-using-five-3640-routers#comments Wed, 02 Apr 2008 14:44:07 +0000 Scott Pilkinton http://www.xpresslearn.com/?p=89 Network Drawing:

Router Platform: 3640
IOS Version: 12.3.24
IOS Feature Set: IP PLUS IPSEC 3DES
IOS File Name: c3640-ik9s-mz.123-24.bin
idlepc: 0x6050aae0
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MM
Average Dynamips.exe CPU Utilization: 65%

Comments:

Five 3640 Routers running the IP Plus Crypto feature set. R1 is running OSPF and EIGRP and has two ethernet links, one connected to R2 and the other connected to R3. R2 is connected to R4 over a single serial connection and is running OSPF. R3 is connected to R4 over a single serial connection and is running EIGRP. R4 is running both OSPF and EIGRP and has a static route to R5, which is being redistributed into both routing protocols.

Link to file:

Dynagen configuration configured for five 3640 routers

Router Platform: 7200
IOS Version: 12.4(11)T1
IOS Feature Set: Service Provider
IOS File Name: c7200-spservicesk9-mz.124-11.T1.bin
idlepc: 0x61280bd8
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips.exe CPU Utilization: 40%

Comments:

The configuration in this article contains four 7206 Routers running the Service Provider feature set. This particular configuration will be used as the basis of a series of MPLS articles. The four routers in this configuration will serve as the Provider (P) devices performing label switching.

Link to File:

Dynagen Configuration using Four 7206 Routers

Router Platform: 3640
IOS Version: 12.4(18)
IOS Feature Set: Enterprise
IOS File Name: c3640-js-mz.124-18.bin
idlepc: 0x60428c4c
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips.exe CPU Utilization: 55%

Comments:

Four 1640 Routers running the Enterprise feature set with 16 port Ethernet switch network modules. Two switches (SW1&SW2) serve as the small office/datacenter core/distribution switches. SW3&SW4 serves as a desktop access switch typically installed in a wiring closet and has dual uplinks back to each distribution switch.

Examples demonstrated in the included switch configurations:

• 802.1q trunking
• Spanning tree root bridge configurations
• Load balancing vlans across multiple uplinks
• VTP client/server operation
• Etherchannel
• Native vlan configuration
• Switch management vlan configuration

Link to file:

Dynagen Lab and Configuration files using 3640 Routers and NM-16ESW modules

Router Platform: 1721
IOS Version: 12.4.18
IOS Feature Set: Service Provider
IOS File Name: c1700-spservicesk9-mz.124-18.bin
idlepc: 0x80c422a4
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 96MB
Average Dynamips.exe CPU Utilization: 72%

Comments:

Three 1721 Routers running the Service Provider feature set. The Lan and Wan routers is in the same office connected via local lan. The Branch router is connected to the Wan router via point to point T1.

Link to file:

Dynagen Configuration using Three 1721 Routers

Router Platform: 2621XM
Number of Ethernet Interfaces: 2
Number of Serial Interfaces: 0
IOS Version: 12.4.15T3
IOS Feature Set: IP Base
IOS File Name: c2600-ipbasek9-mz.124-15.T3.bin
IOS Image Uncompressed before use: Yes
IOS Memory Requirements: 128MB
Average Dynamips CPU Utilization: 52%

Comments:

Routers are connected back to back via FastEthernet0/1.

Link to file:

Dynagen Network Configuration File with Cisco 2621XM Routers

One of the main purposes of the hypervisor is to provide a communication channel for distributing labs across multiple machines. The hypervisor can be thought of as the server side of a client/server operation. The hypervisor provides a ‘supervisor’ like function for telling the dynamips instances what to do. A hypervisor can talk to other hypervisor’s for communicating across distributed hardware.

The popular Dynagen project provides a configuration front end for Dynamips. It allows you to use text based configuration files that defines Dynamips networks. Dynagen works by taking a properly written configuration file and translates that into the appropriate Dynamips commands, that are much harder to understand. Dynagen then talks to a hypervisor instance to send the translated commands to Dynamips. This article will explain how to manually send commands to a Dynamips hypervisor instance, just like what Dynagen would do.

The first thing needed is to start a Dynamips hypervisor instance. This is done by opening a command prompt and switching to the Dynamips directory. Start the hypervisor by typing the following command:

C:\dynamips>start /belownormal /B /wait dynamips-wxp.exe -H 7200

The command does the following:

• Starts dynamips-wxp.exe (Dynamips) in the current command window using the belownormal priority class
• The -H option tells it to operate as a hypervisor instance
• The hypervisor will receive commands on port 7200

Once the hypervisor is started, you can telnet to localhost on port 7200. Open a separate window and issue the command: telnet localhost 7200 . If preferred, any telnet program can be used to make the connection to the hypervisor. Once connected to the hypervisor instance, there won’t initially be anything echoed to the terminal screen. In order to test the connection, issue the following command inside the telnet window (your typing won’t echo back to the screen on this initial command).

hypervisor version (press enter)

If operating properly, you will receive a response containing the version of Dynamips that is running

100-0.2.8-RC1-x86

The 100 in the response is a (successful) return code, with the command results following immediately after the dash following the return code. In this case, the version is 0.2.8 Release Candidate 1, compiled for the x86 platform.

If an invalid command is sent to the hypervisor, a different response code will be returned along with an explanation:

200-At least a module and a command must be specified

To get started, clear the hypervisor to make sure you are starting with a clean slate.

hypervisor reset
100-OK

Next, set the working directory that will contain the router virtual disk images and other files that are created to hold things like the contents of NVRAM, etc.

hypervisor working_dir “C:/Documents and Settings/Administrator/My Documents/dynamips/workdir”
100-OK

Create a 7200 virtual router instance and call it R1

vm create R1 0 c7200
100-VM ‘R1′ created

Make the console port of R1 available on TCP port 2000:

vm set_con_tcp_port R1 2000
100-OK

Set the amount of RAM for R1 to 160Mb:

vm set_ram R1 160
100-OK

The Network Processing Engine (NPE) for the 7200 router called R1 will be a model npe-400:

c7200 set_npe R1 npe-400
100-OK

Set the IOS image for the 7200 virtual router called R1 to boot:

vm set_ios R1 “C:\Documents and Settings\Administrator\My Documents\dynamips\ios\c7200-spservicesk9-mz.124-11.T1.image”
100-IOS image set for ‘R1′

Don’t use the sparse memory option for R1:

vm set_sparse_mem R1 0
100-OK

vm set_blk_direct_jump R1 0
100-OK

Create a virtual switch (called S1) to allow communication between the router Ethernet interface and the a pc interface just as if they both were connected to a real switch:

ethsw create S1
100-ETHSW ‘S1′ created

Add a PA-2FE-TX Port Adapter in slot1 of R1:

vm slot_add_binding R1 1 0 PA-2FE-TX
100-OK

Create a communication channel called nio_udp0 that listens for traffic on port 10000 and connects to the remote port 10001 on localhost to send traffic:

nio create_udp nio_udp0 10000 127.0.0.1 10001
100-NIO ‘nio_udp0′ created

Create a communication channel called nio_udp1 that listens for traffic on port 10001 and connects to the remote port 10000 on locahost to send traffic:

nio create_udp nio_udp1 10001 127.0.0.1 10000
100-NIO ‘nio_udp1′ created

Bind the interface in Slot 1 Port 0 (Interface Fa1/0) on R1 to the nio_udp0 communication channel:

vm slot_add_nio_binding R1 1 0 nio_udp0
100-OK

Connect the virtual switch S1 with the nio_udp1 communication channel:

ethsw add_nio S1 nio_udp1
100-NIO ‘nio_udp1′ bound.

Set the nio_udp1 interface on virtual switch S1 to vlan 1:

ethsw set_access_port S1 nio_udp1 1
100-Port settings OK

Create an interface called nio_gen_eth0 and associate it with a Windows interface on the host machine:

nio create_gen_eth nio_gen_eth0 \Device\NPF_{6BEED806-4E3F-41F9-A5E6-9E558ECFB2E3}
100-NIO ‘nio_gen_eth0′ created

Connect the Windows network interface to S1

ethsw add_nio S1 nio_gen_eth0
100-NIO ‘nio_gen_eth0′ bound.

Set the port connected to nio_gen_eth0 in virtual switch S1 to vlan 1

ethsw set_access_port S1 nio_gen_eth0 1
100-Port settings OK

Set the idle pc value for the image R1 is running to prevent 100% cpu usage

vm set_idle_pc R1 0×60791304
100-OK

Boot the virtual router instance named R1

vm start R1
100-VM ‘R1′ started

Once the instance has been started, telnet to the console port of the router R1 by telneting to localhost on port 2000.

Connected to Dynamips VM “R1″ (ID 0, type c7200) – Console port

R1#sh ip int brief
Interface            IP-Address      OK? Method Status                Protocol
FastEthernet0/0      unassigned      YES NVRAM  administratively down down

FastEthernet1/0      10.1.100.1      YES NVRAM  up                    up

FastEthernet1/1      unassigned      YES NVRAM  administratively down down

R1#sh hardware
Cisco IOS Software, 7200 Software (C7200-SPSERVICESK9-M), Version 12.4(11)T1, RE
LEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Thu 25-Jan-07 19:57 by prod_rel_team

ROM: ROMMON Emulation Microcode
BOOTLDR: 7200 Software (C7200-SPSERVICESK9-M), Version 12.4(11)T1, RELEASE SOFTW
ARE (fc5)

R1 uptime is 0 minutes
System returned to ROM by unknown reload cause - suspect boot_data[BOOT_COUNT] 0
x0, BOOT_COUNT 0, BOOTDATA 19
System image file is "tftp://255.255.255.255/unknown"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco 7206VXR (NPE400) processor (revision A) with 147456K/16384K bytes of memor
y.
Processor board ID 4294967295
R7000 CPU at 150MHz, Implementation 39, Rev 2.1, 256KB L2 Cache
6 slot VXR midplane, Version 2.1

Last reset from power-on

PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb0_mb1 has a total of 600 bandwidth points.
This configuration is within the PCI bus capacity and is supported.

PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 0 bandwidth points
This configuration is within the PCI bus capacity and is supported.

Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.

3 FastEthernet interfaces
125K bytes of NVRAM.

65536K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2102

R1#

In this initial explanation, we will run a single virtual 7200 router instance that will have an Ethernet interface bridged with a network adapter on the host PC. By doing this, the host PC will be able to communicate to the virtual router just like it was a real router on a real network.

The first thing needed is to determine the PCAP string that represents the network adapter to be bridged with the virtual router interface. To do this run the dynamips executable with just a ‘-e’ option.

C:\Program Files\Dynamips>dynamips -e
Cisco Router Simulation Platform (version 0.2.8-RC1-x86)
Copyright (c) 2005-2007 Christophe Fillot.
Build date: Sep 7 2007 17:17:20

Network device list:

rpcap://\Device\NPF_{3A61C8A2-3B20-4C04-880D-C24930E29609} : Network adapter ‘Intel(R) PRO/1000 MT Mobile Connection – Deterministic Network Enhancer Miniport’ on local host
rpcap://\Device\NPF_{6BEED806-4E3F-41F9-A5E6-9E558ECFB2E3} : Network adapter ‘MS LoopBack Driver’ on local host
rpcap://\Device\NPF_{FCE28766-936D-4D4B-A534-CC9D50B477C5} : Network adapter ‘Intel(R) PRO/Wireless 2200BG Network Connectio’ on local host

The Windows interface we want to use for communication with the virtual router interface is the MS Loopback Driver. So the next step is to create a switch.cfg file, this will define the properties of the virtual switch.

IF:E0:udp:10001:127.0.0.1:10000
IF:E1:gen_eth:\Device\NPF_{6BEED806-4E3F-41F9-A5E6-9E558ECFB2E3}

ACCESS:E0:4
ACCESS:E1:4

The contents of this file will define the makeup of the virtual switch. In this particular virtual switch, there are two interfaces: E0 and E1. The virtual switch interface E0 will be sourced locally using udp port 10001 and will connect to port 10000, also residing on the localhost. The virtual switch interface E1 will be mapped to the Windows loopback adapter. Both ports are put in the same vlan, which is vlan 4 in this particular example. Once the file is created, you can run Dynamips like so:

dynamips-wxp.exe -X -i 996 -t npe-400 -r 256 -p 0:C7200-IO-FE -s 0:0:udp:10000:127.0.0.1:10001 c7200-spservicesk9-mz.124-11.T1.image -E switch.cfg

The above command string starts a single Dynamips 7200 instance with a C7200-IO card containing a single FastEthernet adapter, which will be FastEthernet0/0 inside the IOS. The -s option says take the adapter in slot0:port0 and map it’s input locally to udp port 10000 and direct it’s output traffic to udp port 10001 on the localhost. You will notice this is just the opposite of what is defined in the switch configuration file. Below is what you will see after running the command string above:

Cisco Router Simulation Platform (version 0.2.8-RC2-x86)
Copyright (c) 2005-2007 Christophe Fillot.
Build date: Oct 14 2007 10:54:51

Instance ID set to 996.
Virtual RAM size set to 256 MB.
IOS image file: ..\ios\c7200-spservicesk9-mz.124-11.T1.image

ILT: loaded table "mips64j" from cache.
ILT: loaded table "mips64e" from cache.
ILT: loaded table "ppc32j" from cache.
ILT: loaded table "ppc32e" from cache.
CPU0: carved JIT exec zone of 16 Mb into 512 pages of 32 Kb.
C7200 instance 'default' (id 996):
  VM Status  : 0
  RAM size   : 256 Mb
  IOMEM size : 0 Mb
  NVRAM size : 128 Kb
  NPE model  : npe-400
  Midplane   : vxr
  IOS image  : ..\ios\c7200-spservicesk9-mz.124-11.T1.image

Loading ELF file '..\ios\c7200-spservicesk9-mz.124-11.T1.image'...
ELF entry point: 0x80008000

C7200 'default': starting simulation (CPU0 PC=0xffffffffbfc00000), JIT enabled.
ROMMON emulation microcode.

Launching IOS image at 0x80008000...
Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS Software, 7200 Software (C7200-SPSERVICESK9-M), Version 12.4(11)T1, RE
LEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Thu 25-Jan-07 19:57 by prod_rel_team
Image text-base: 0x60009084, data-base: 0x62B1A000

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco 7206VXR (NPE400) processor (revision A) with 245760K/16384K bytes of memory.
Processor board ID 4294967295
R7000 CPU at 150MHz, Implementation 39, Rev 2.1, 256KB L2, 512KB L3 Cache
6 slot VXR midplane, Version 2.1

Last reset from power-on

PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb0_mb1 has a total of 200 bandwidth points.
This configuration is within the PCI bus capacity and is supported.

PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 0 bandwidth points
This configuration is within the PCI bus capacity and is supported.

Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.

1 FastEthernet interface
125K bytes of NVRAM.

65536K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
% Crashinfo may not be recovered at bootflash:crashinfo
% This file system device reports an error

Press RETURN to get started!

*Jan  6 23:23:01.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0
, changed state to up
*Jan  6 23:23:01.931: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Jan  6 23:23:03.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0/0, changed state to up
*Jan  6 23:23:03.531: %SYS-5-CONFIG_I: Configured from memory by console
*Jan  6 23:23:03.855: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 7200 Software (C7200-SPSERVICESK9-M), Version 12.4(11)T1, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Thu 25-Jan-07 19:57 by prod_rel_team
*Jan  6 23:23:04.183: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoing a cold start
Router>

Our loopback IP address is statically defined on the Windows PC as 10.1.100.20, so we will ping it from the IOS command prompt:

Router>en

Router#sh ip int brief

Interface           IP-Address    OK?    Method    Status    Protocol

FastEthernet0/0     10.1.100.1    YES    NVRAM     up        up

Router#ping 10.1.100.20

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.100.20, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 28/68/92 ms
Router#

As you can see, we have successfully setup an single virtual router instance using Dynamips and have configured it to successfully communicate to an interface on the host Windows PC.

- MIPS64 and PowerPC CPU processors. The instruction sets are not completely emulated now (MIPS FPU support is lacking, TLB support is not finished and other minor things), but it is sufficient for IOS
- DRAM and Packet SRAM memory
- Non-Volatile Memory (NVRAM)
- Signetics SCN 2681 DUART (C7200 Console and AUX ports)
- National Semiconductors NS16552 DUART (C3600/C3700/C2600 Console/AUX ports)
- Dallas DS1620 Temperature Sensors and Voltage Sensors, allowing the C7200 Environmental Monitor to work properly
- NMC93C46 Serial EEPROM
- Bootflash of 8 Mb (Intel 28F016SA)
- Galileo GT64010/GT64120/GT96100 PCI controllers, DEC 21×50 PCI bridges and so
- PCMCIA ATA disk emulation (C7200 only at this time)

Cisco 7200 (7206) Platform

The following Port Adapters (PA) is currently supported:
- FastEthernet cards C7200-IO-FE and PA-FE-TX based on DEC21140 chip
- Ethernet cards PA-4E, and PA-8E based on AMD Am79c97x chips
- ATM card PA-A1 based on Texas Instruments Tneta1570 chip
- Serial cards PA-4T+ and PA-8T
- POS (Packet over Sonet) card PA-POS-OC3

Chassis Types:
- STD,VXR

NPE Models:
- NPE-100, NPE-150, NPE-175, NPE-200, NPE-225, NPE-300, NPE-400

Cisco 3600 (3620, 3640, and 3660) Platform

The following Network Modules (NM) is currently supported:
- Ethernet cards: NM-1E, NM-4E and NM-1FE-TX, all based on AMD Am79c97x chips
- Ethernet switching module: NM-16ESW
- Serial cards: NM-4T, WIC-1T, WIC-2T
- Services cards: NM-NAM, NM-CIDS

Cisco 3700 (2691, 3725, and 3745) Platform

The following Network Modules (NM) is currently supported:
- FastEthernet cards: NM-1FE-TX
- Ethernet switching module: NM-16ESW
- Serial card NM-4T, WIC-1T, WIC-2T
- Services cards: NM-NAM, NM-CIDS

Cisco 2600 (2610, 2611, 2620, 2621, 2610XM, 2611XM, 2620XM, 2621XM, 2650XM and 2651XM) Platform

The following Network Modules (NM) is currently supported:
- Ethernet cards: NM-1E, NM-4E and NM-1FE-TX
- Ethernet switching module: NM-16ESW
- Serial cards: WIC-1T, WIC-2T
- Services cards: NM-NAM, NM-CIDS

Cisco 1700 (1710,1720,1721,1750,1751, and 1760) Platform

The following WIC Modules are currently supported:
- Ethernet cards: WIC-1ENET
- Serial cards: WIC-1T, WIC-2T

Non router hardware specific features:

- Ability to bridge Ethernet adapters on the emulated hardware with a NIC on the host PC. This allows you to connect the emulated router directly to the network the host computer is plugged into. For example, you might want an emulated router to interact somehow with an existing real network for some testing purposes. This is possible by using the PC network adapter to transparently bridge an emulated router interface. Another useful combination is using a network interface on the host pc (such as a loopback) to communicate with router interfaces in the virtual network.

- Capture packets on virtual Ethernet or Serial interfaces and write the output to a capture file for use with applications like tcpdump, Wireshark, or any other application that can read the libpcap capture file format.