|
|
1.1 root 1: Help for Cisco 7200 simulator (dynamips-0.2.3)
2: ==============================================
3: Authors: Fabien Devaux, Christophe Fillot, MtvE
4:
5: Emulated hardware
6: *****************
7:
8: By default, a NPE-200 is emulated. You can choose the NPE type with the
9: "-t" option. It is possible to select "npe-100", "npe-150", "npe-175",
10: "npe-200", "npe-225", "npe-300" and "npe-400". The "npe-g1" is not working.
11:
12: Please note that you must use the C7200-IO-FE PA driver as IO card if you
13: want a FastEthernet interface in slot 0. For other slots, you must use
14: the PA-FE-TX driver.
15:
16: The Serial driver (PA-4T+) is not working at all (the interfaces are only
17: "seen" by IOS).
18:
19:
20: Command Line Options overview
21: *****************************
22:
23: -r <ram_size> : Set the virtual RAM size (default is 256 Mb)
24: -o <rom_size> : Set the virtual ROM size (default is 4 Mb)
25: -n <nvram_size> : Set the NVRAM size (default is 128 Kb)
26: -l <log_file> : Set logging file (default is pred_log0.txt)
27: -C <cfg_file> : Import an IOS configuration file into NVRAM
28: -R <rom_file> : Load an alternate ROM (default is embedded)
29: -s <sym_file> : Load symbol file
30: -c <conf_reg> : Set the configuration register (default is 0x2102)
31: -m <mac_addr> : Set the MAC address of the chassis (IOS chooses default)
32: -k <clock_div> : Set the clock divisor (default is 2)
33: -T <port> : Console is on TCP <port> (default is on the terminal)
34: -A <port> : AUX is on TCP <port> (default is no AUX port)
35: -i : Instruction block trace, very slow
36: -j : Disable the JIT compiler, very slow
37: -t <npe_type> : Select NPE type
38: -M <midplane> : Select Midplane ("std" or "vxr")
39: -p <pa_desc> : Define a Port Adapter
40: -a <cfg_file> : Virtual ATM switch configuration file
41: -b <cfg_file> : Virtual bridge configuration file
1.1.1.2 ! root 42: -e : Show network device list
1.1 root 43:
44:
45: Command Line Options details
46: ****************************
47:
48: <clock_div> :
49:
50: Specify the clock divider (integer) based on the host clock.
51: Alter the value to match the CISCO clock with the real time.
52: The command "show clock" at the IOS' CLI will help you set this value.
53:
54: <pa_desc> :
55:
56: Format: slot:pa_driver:netio_type[:netio_parameters]
57:
58: slot : the number of the physical slot (starts from 0)
59:
60: pa_driver : the name of a port adapter driver in:
61: - C7200-IO-FE (FastEthernet, slot 0 only)
62: - PA-FE-TX (FastEthernet, slots 1 to 6)
63: - PA-4T+ (Serial, NOT WORKING)
64: - PA-A1 (ATM)
65:
66: netio_type : host interface for communication
67:
68: unix:<local_sock>:<remote_sock>
69: Use unix sockets for local communication.
70: <local_sock> is created and represents the local NIC.
71: <remote_sock> is the file used by the other interface.
72: (ex. "/tmp/local:/tmp/remote")
73:
74: tap:<tap_name>
75: Use a virtual ethernet device for communication.
76: <tap_name> is the name of the tap device (ex. "tap0")
77:
1.1.1.2 ! root 78: gen_eth:<dev_name>
! 79: Use a real ethernet device for communication, using libpcap 0.9
! 80: or WinPcap. Works on Windows and Unix systems.
! 81:
! 82: <dev_name> is the name of the Ethernet device (ex. "eth0")
! 83:
! 84: The device list can be found using the "-e" option.
! 85:
1.1 root 86: linux_eth:<dev_name>
87: Use a real ethernet device for communication (Linux specific).
88: <dev_name> is the name of the Ethernet device (ex. "eth0")
89:
90: udp:<local_port>:<remote_host>:<remote_port>
91: Use an UDP socket for connection between remote instances.
92: <local_port> is the port we listen to.
93: <remote_host> is the host listening the port you want to connect to.
94: <remote_port> is the port you want to connect to.
95: (ex. "1000:somehost:2000" and "2000:otherhost:1000" on the other
96: side)
97:
98: tcp_cli:<host>:<port>
99: Client side of a tcp connection.
100: <host> is the ip address of the server.
101: <port> is the port to connect to.
102:
103: tcp_ser:<port>
104: Server side of a tcp connection.
105: <port> is the port to listen to.
106:
107: null
108: Dummy netio (used for testing/debugging), no parameters needed.
109:
110:
111: Escape commands
112: ***************
113:
1.1.1.2 ! root 114: You can press ^] (Ctrl + ]) at any time, followed by one of these characters:
1.1 root 115:
116: d : Show the device list
117: r : Dump MIPS CPU registers
118: t : Dump MIPS TLB entries
119: m : Dump the latest memory accesses
120: s : Suspend CPU emulation
121: u : Resume CPU emulation
122: q : Quit the emulator
123: b : Dump the instruction block tree
124: c : Write IOS configuration to disk (ios_cfg.txt)
125: j : Non-JIT mode statistics
126: x : Experimentations (can crash the box!)
127: ^]: Send ^]
128:
129: If you press an unrecognized key, help will be shown.
130:
1.1.1.2 ! root 131: Note: on Windows, it may be the "Ctrl + $" sequence.
! 132:
1.1 root 133:
134: Virtual Bridge
135: **************
136:
137: The virtual bridge is used to emulate a shared network between emulator
138: instances.
139:
140: Any emulator instance can ast as a virtual bridge.
141:
142: The configuration file (specified by the "-b" option) contains a list of
143: NetIO descriptors, which the following syntax: netio_type[:netio_parameters]
144:
145: Example:
146:
147: # Connection to instance "I0"
148: udp:10000:127.0.0.1:10001
149:
150: # Connection to instance "I1"
151: udp:10002:127.0.0.1:10003
152:
153: # Connection to instance "I2"
154: udp:10004:127.0.0.1:10005
155:
156: The "I0" would be launched with the following parameters:
157:
158: dynamips ios.bin -p 1:PA-FE-TX:udp:10001:127.0.0.1:10000
159:
160:
161: Virtual ATM switch
162: ******************
163:
164: The virtual ATM switch fabric is used to emulate an ATM backbone between
165: emulator instances. The use of this virtual switch is not mandatory, you
166: can directly connect emulator instances for point-to-point ATM connections.
167: Please note that only basic VP/VC switching is supported, there is no
168: support for ILMI/QSAAL/... or other specific ATM protocols.
169:
170: Any emulator instance can act as a virtual ATM switch.
171:
172: Example of configuration file (specified by the "-a" option):
173:
174: # Virtual Interface List
175: IF:A0:udp:10001:127.0.0.1:10000
176: IF:A1:udp:10002:127.0.0.1:10003
177: IF:A2:udp:10004:127.0.0.1:10005
178:
179: # VP connection between I0 and I1
180: VP:A0:10:A1:20
181: VP:A1:20:A0:10
182:
183: # VP connection between I0 and I2
184: VP:A0:11:A2:30
185: VP:A2:30:A0:11
186:
187: # VC connection between I1 and I2
188: VC:A1:5:2:A2:7:3
189: VC:A2:7:3:A1:5:2
190:
191: In this example, we have 3 virtual interfaces, A0, A1 and A2. The syntax
192: for interface definition is similar to Port Adapters:
193:
194: IF:interface_name:netio_type[:netio_parameters]
195:
196: You can do VP switching or VC switching:
197:
198: 1) VP switching
199:
200: syntax: VP:input_if:input_vpi:output_if:output_vpi
201:
202: 2) VC switching
203:
204: syntax: VC:input_if:input_vpi:input_vci:output_if:output_vpi:output_vci
205:
206:
207: Testing the Virtual ATM switch with one dynamips instance
208: *********************************************************
209: (Contribution of Mtv Europe)
210:
211: Virtual ATM switch configuration file ("atm.cfg"):
212:
213: IF:A0:udp:10003:127.0.0.1:10001
214: IF:A1:udp:10004:127.0.0.1:10002
215: # a0/vpi=1/vci=100 connects to a1/vpi=2/vci=200
216: VC:A0:1:100:A1:2:200
217: VC:A1:2:200:A0:1:100
218:
219: Invoking dynamips:
220:
221: ./dynamips -p 1:PA-A1:udp:10001:127.0.0.1:10003 -p 2:PA-A1:udp:10002:127.0.0.1:10004 -a atm.cfg IOS.BIN
222:
223: (note input ports of IOS interfaces are output ports of ATM switch
224: interfaces, and vice versa).
225:
226: IOS configuration:
227:
228: ip cef
229: ip vrf test
230: rd 1:1
231: route-target both 1:1
232: int a1/0
233: no shut
234: int a1/0.2 p
235: ip addr 1.1.1.1 255.255.255.0
236: pvc 1/100
237: interface a2/0
238: no shut
239: interface a2/0.2 p
240: ip vrf forwarding test
241: ip addr 1.1.1.2 255.255.255.0
242: pvc 2/200
243: !
244:
245: # ping 1.1.1.2
246: !!!!!
247:
248: == EOF ==
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.