Packet Tracer 4.11 Help

suarve · 22 Feb 2008 at 14:13

Hi,

I'm just testing a network I made using packet tracer 4.11. I have several VLANs configured with trunks and want to test them. Howe would i do this exactly in packet tracer? I'm tempted to add a pc and configure it with and ip from the VLAN and then try to get pings to ping (or not ping) eachother. I'm sure there must be a better way to this via packet tracer?

Also, how can i add a connection going to an ISP (E.g. s 0/0 from a router goes to the ISP) and how would i add another network (e.g. i want to represent that a network - 180.150.1.0 for example - is connected to a router via f 0/0).

Thanks

Curiosityx · 22 Feb 2008 at 15:36

I think this would be of use to you. That is if it's the product i think your referring too.

http://www.wvup.edu/dweaver/Cisco/P...racer_module/packet_tracer_module/default.htm

suarve · 22 Feb 2008 at 17:28

Curiosityx said:
I think this would be of use to you. That is if it's the product i think your referring too.

http://www.wvup.edu/dweaver/Cisco/P...racer_module/packet_tracer_module/default.htm

Yes thats the one. I'm familiar with all the basic adding, pinging etc of devices . Just wanted some advice on exactly how to implement my OP in packet tracer.

Thanks

Laser402 · 22 Feb 2008 at 19:05

Pinging is best bet, put pc on each VLAN and try to ping between them, should all fail of course (without a router). If you want to see the packets route just use simulation mode and play.

For ISP you could either add a loopback interface on the router with an ip address and a 255.255.255.255 mask then use a default route to point unknown traffic to it.

To add another network just make another network, or simply connect a pc to the router and advertise the route using your routing protocol.

suarve · 23 Feb 2008 at 20:39

Thanks for the replies.

I have another question now

When viewing the running and startup configs for the switches the commands to actually create my vlans (VLAN DATABASE > VLAN xx name fhsdjkfjksd) isn't there. However, all the commands for trunking are there. Do i need to include this in my config file???

Laser402 · 23 Feb 2008 at 21:04

Use 'switch#show vlan' to verify the VLANs you have created and the ports assigned, I don’t believe it is shown in the running/startup config as the switch saves the VLANs to 'flash:vlan.dat' file.

And VLAN database method is obsolete now as packet tracer will tell you when you use it. instead use:

Switch#config t
Switch(config)#vlan (put number here)
Switch(config-vlan)#name (put name here)

Enjoy.

bigredshark · 23 Feb 2008 at 22:03

Laser402 said:
Use 'switch#show vlan' to verify the VLANs you have created and the ports assigned, I don’t believe it is shown in the running/startup config as the switch saves the VLANs to 'flash:vlan.dat' file.

And VLAN database method is obsolete now as packet tracer will tell you when you use it. instead use:

Switch#config t
Switch(config)#vlan (put number here)
Switch(config-vlan)#name (put name here)

Enjoy.

All vlan config is in the running/startup config on modern cisco's

Laser402 · 23 Feb 2008 at 23:42

The actual VLANs arnt stored in the running/startup config, or have I missed something big?

Using IOS ver:12.1 here. The ports commands like 'switchport access vlan 10' and stuff is in the run/start config but not the actual VLAN's and their names.

VLAN 1 information is stored in the configs with IP address etc.

Whats the 'modern' cisco's you talk of?

suarve · 24 Feb 2008 at 10:13

Laser402 said:
The actual VLANs arnt stored in the running/startup config, or have I missed something big?

Using IOS ver:12.1 here. The ports commands like 'switchport access vlan 10' and stuff is in the run/start config but not the actual VLAN's and their names.

VLAN 1 information is stored in the configs with IP address etc.

Whats the 'modern' cisco's you talk of?

Yer can see the vlan 1 info - ip etc in the config file. All the other commands relating to trunking are there too it just the bit where the vlans are created. I only ask as for a case study i have to include config files for switches/routers etc. I also noticed this too when i searhing about.

bigredshark · 24 Feb 2008 at 14:04

Laser402 said:
The actual VLANs arnt stored in the running/startup config, or have I missed something big?

Using IOS ver:12.1 here. The ports commands like 'switchport access vlan 10' and stuff is in the run/start config but not the actual VLAN's and their names.

VLAN 1 information is stored in the configs with IP address etc.

Whats the 'modern' cisco's you talk of?

Only if you use the vlan database (which is on it's way out and not recommended)

Best practice is to define all vlans in the running config, I'd use something like...

conf t
vlan 150
name demo_vlan_name
do wr me

Thats any modern cisco I've worked with. Just my opinion of course

Laser402 · 24 Feb 2008 at 19:39

^ Still stores info in flash:vlan.dat

Source

hense the procedure to get a switch back to default is:

erase start
delete flash:vlan.dat
reload