Inter Vlan Configuration

super22

Guys help please

I use Routersim Network Visualizer 6. I am not sure if this config did not work because of software limitations or if I really made a mistake. Please help me. Thanks

ROUTER connected to SWITCH connected to 2 HOST


HOST A: 192.168.1.2, 255.255.255.128, DG: 192.168.1.1

HOST B: 192.168.1.130, 255.255.255.128, DG: 192.168.1.129


router#config t
router(config-if)#int fa0/0
router(config-if)#no ip address
router(config-if)#no shut
router(config-if)#int fa0/0.2
router(config-subif)#encapsulation dot1q 2
router(config-subif)#ip address 192.168.1.1 255.255.255.128
router(config-subif)#int fa0/0.3
router(config-subif)#encapsulation dot1q 3
router(config-subif)#ip address 192.168.1.129 255.255.255.128
router(config-subif)#exit

switch#conf t
switch(config)#vlan 2
switch(config-vlan)#name HOSTA
switch(config-vlan)#vlan 3
switch(config-vlan)#name HOSTB
switch(config-vlan)#int fa0/1
switch(config-if)#switchport mode trunk
switch(config-if)#int fa0/2
switch(config-if)#switchport access vlan 2
switch(config-if)#int fa0/3
switch(config-if)#switchport access vlan 3

I cannot ping between host

Did I miss something?

Also I did not use vlan1 because I read that it is a administrative vlan. Anyone care to explain about what administrative vlan is for?

Thanks in advance

Mrock4

You're using dot1q on the router's side of your link to your switch, but not on the switches side. Try adding:

switchport trunk encap dot1q

to your switches trunk interface to the router.

ColbyG

Mrock4 wrote: »

You're using dot1q on the router's side of your link to your switch, but not on the switches side. Try adding:

switchport trunk encap dot1q

to your switches trunk interface to the router.

Depends on the switch he's using, if it's a 2950 (seems likely), it will only support dot1q.

What isn't working? Can you ping the gateway? What does "sh ip int b" give you on both devices? Also "sh vlan b" on the switch.

Mrock4

ColbyG wrote: »

Depends on the switch he's using, if it's a 2950 (seems likely), it will only support dot1q.

What isn't working? Can you ping the gateway? What does "sh ip int b" give you on both devices? Also "sh vlan b" on the switch.

I thought the same thing initially, but he's using a simulator..so it's hard to tell..

super22

im using 1841 and 2960 on the sim of course hehe

super22

Mrock4 wrote: »

You're using dot1q on the router's side of your link to your switch, but not on the switches side. Try adding:

switchport trunk encap dot1q

to your switches trunk interface to the router.

I'll try adding the encapsulation on the switch side

im now using packet tracer instead of network visualizer

ColbyG

ColbyG wrote: »

What isn't working? Can you ping the gateway? What does "sh ip int b" give you on both devices? Also "sh vlan b" on the switch.

Help shed some light.

Mrock4

Yeah, think the 2960's are just like the 2950's are as encapsulation goes, only dot1q, right?

super22

ColbyG wrote: »

Help shed some light.

i cant ping from Host A to Host B

I'll try to do sh ip int b and and sh vlan b later

thanks in advance

mikej412

ColbyG wrote: »

Can you ping the gateway?

I would have just come out and asked if the hosts were configured to use the (correct) gateways -- and what IP Address they had, and which host was plugged into which port.....

super22

mikej412 wrote: »

I would have just come out and asked if the hosts were configured to use the (correct) gateways -- and what IP Address they had, and which host was plugged into which port.....

HOST A: 192.168.1.2, 255.255.255.128, DG: 192.168.1.1 --> Fa0/2 (switch)

HOST B: 192.168.1.130, 255.255.255.128, DG: 192.168.1.129 --> Fa0/3 (switch)

mikej412

super22 wrote: »

I'll try to do sh ip int b and and sh vlan b later

Might as well toss in a trace route from A to B (and B to A)

It's starting to sound like a simulator software thing. Save your config, close and then open it back up -- and see if it magically works (after allowing time for simulated STP to do it's thing).

super22

mikej412 wrote: »

Might as well toss in a trace route from A to B (and B to A)

It's starting to sound like a simulator software thing. Save your config, close and then open it back up -- and see if it magically works (after allowing time for simulated STP to do it's thing).

hmmm I will also try that but the config I posted in the first post should work right?

super22

just more info:

HOST A: 192.168.1.2, 255.255.255.128, DG: 192.168.1.1 --> Fa0/2 (switch) VLAN 2

HOST B: 192.168.1.130, 255.255.255.128, DG: 192.168.1.129 --> Fa0/3 (switch) VLAN 3

hexem

paste the following for us to see:

on the router.

'show ip route'

switch:

'show int trunk'
'show vlan brief'


Also try adding 'switchport mode access' under each int.

mella060

Make sure the port on the switch connecting to the router is a trunk port

switchport mode trunk

Make the ports connecting to the PCs access ports

switchport mode access

super22

mella060 wrote: »

Make sure the port on the switch connecting to the router is a trunk port

switchport mode trunk

Make the ports connecting to the PCs access ports

switchport mode access

I will try all your suggestions once I get home

hopefully with everyone's help I can figure this out cos its driving me nuts

dummy123

try adding:
router(config-if)#int fa0/0
router(config-if)#duplex full

switch(config-vlan)#int fa0/1
switch(config-if)#duplex full

assuming those are your trunk ports

super22

Switch#sh int trunk
Port Mode Encapsulation Status Native vlan
Fa0/1 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/1 1-1005
Port Vlans allowed and active in management domain
Fa0/1 1,2,3
Port Vlans in spanning tree forwarding state and not pruned
Fa0/1 1,2,3
Switch#sh vlan brief
VLAN Name Status Ports
----

---

---

---

1 default active Fa0/4, Fa0/5, Fa0/6, Fa0/7
Fa0/8, Fa0/9, Fa0/10, Fa0/11
Fa0/12, Fa0/13, Fa0/14, Fa0/15
Fa0/16, Fa0/17, Fa0/18, Fa0/19
Fa0/20, Fa0/21, Fa0/22, Fa0/23
Fa0/24, Gig1/1, Gig1/2
2 HOSTA active Fa0/2
3 HOSTB active Fa0/3
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active


Router#sh ip ro
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
192.168.1.0/25 is subnetted, 2 subnets
C 192.168.1.0 is directly connected, FastEthernet0/0.2
C 192.168.1.128 is directly connected, FastEthernet0/0.3

mikej412

You've got the trunk, you've got the VLANs (and they are active & have the ports assigned), routing is enabled and the connected interfaces look correct.

Unless you have your simulated hosts A and B plugged into the wrong ports, I'm leaning towards simulator issue.

Can the hosts ping themselves?
Can the Router ping the hosts?
Can the Router ping itself?

Did you do the show ip interface brief someone suggested and verified your ports are UP/UP?

Have you verified that you are using the correct simulated cables?

Does the simulator have a graphical interface and does it show you the simulated link LEDs?

Has anyone copied the configs and tried them on real hardware (or Dynamips) to rule out any typo no one has caught?

Mrock4

mikej412 wrote: »

Has anyone copied the configs and tried them on real hardware (or Dynamips) to rule out any typo no one has caught?

Got the scenario working with two 2500's as the hosts, a 3550 as the switch, and a 3640 as the router on a stick

Nothing really had to be changed, biggest problem was some duplex issues, and making sure that a route was in place on the 'hosts'.

From HostB (192.168.1.130) to Host A

ping 192.168.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/23/24 ms

mikej412

Mrock4 wrote: »

Nothing really had to be changed, biggest problem was some duplex issues, and making sure that a route was in place on the 'hosts'.

You could just disable routing on the 2500 and set a default gateway so they just like dumb hosts....

The duplex issue was mentioned -- but with 1841's & a 2960 I wouldn't expect simulated duplex issues to happen. Maybe there's a simulated cross-over cable installed, rather than a simulated straight through cable -- and maybe there's a problem with the simulated MDIX on the simulated 2960

Gotta love working with simulators

Mrock4

mikej412 wrote: »

You could just disable routing on the 2500 and set a default gateway so they just like dumb hosts....

yeah, but the 2500's are both configured already based on the INE configs..it was just as easy to throw in a static route and an ip address.

Yeah, sounds like a simulator issue to me, which I wouldn't be surprised by. I've used a simulator for about 2 hrs while working on the CCNA, and got frustrated at random bugs and such.

super22

guys one more piece of info:

I did not do anything else on the switches and routers except the one I posted on the first post - Thats it! no other configs except the one I posted on the first post.

If thats ok then its gotta be a simulator issue...

super22

has anyone tried it on Packet Tracer?

hexem

Here's my switch and router config in packet tracer 5.2 (works fine)

Switch(config)#vlan 2
Switch(config-vlan)#vlan 3
Switch(config-vlan)#vlan 2
Switch(config-vlan)#name HOSTA
Switch(config-vlan)#vlan 3
Switch(config-vlan)#name HOSTB
Switch(config-vlan)#int fa0/3
Switch(config-if)#switchport mode trunk
Switch(config-if)#int fa0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#int fa0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3


Router(config)#int fa0/0.2
Router(config-subif)#encapsulation dot1Q 2
Router(config-subif)#ip address 192.168.1.1 255.255.255.0
Router(config-subif)#int fa0/0.3
Router(config-subif)#encapsulation dot1Q 3
Router(config-subif)#ip address 192.168.2.1 255.255.255.0
Router(config-subif)#int fa0/0
Router(config-if)#no shut


Packet Tracer PC Command Line 1.0
PC>ping 192.168.2.2

Pinging 192.168.2.2 with 32 bytes of data:

Request timed out.
Reply from 192.168.2.2: bytes=32 time=15ms TTL=127
Reply from 192.168.2.2: bytes=32 time=16ms TTL=127

PC>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=14ms TTL=127
Reply from 192.168.1.2: bytes=32 time=14ms TTL=127

super22

ok I finally solved my problem...I was just using the wrong cable doh!

I have another question if you dont mind...

down below is my config:

Building configuration...
Current configuration : 1177 bytes
!
version 12.4
no service timestamps log datetime msec
no service timestamps debug datetime msec
service password-encryption
!
hostname DENRouter
!
!
!
enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
!
!
!
ip name-server 0.0.0.0
!
!
!
!
!
!
interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
duplex auto
speed auto
!
interface FastEthernet0/1/0
switchport mode access
!
interface FastEthernet0/1/1
switchport mode access
!
interface FastEthernet0/1/2
switchport mode access
!
interface FastEthernet0/1/3
switchport mode access
!
interface Vlan1
description PRIVATE NETWORK
ip address 10.1.1.1 255.255.255.0
!
ip classless
!
!
!
ip dhcp excluded-address 10.1.1.1
!
ip dhcp pool CLIENT
network 10.1.1.0 255.255.255.0
default-router 10.1.1.1
!
banner motd ^C
*****************************
WELCOME!!
*****************************
^C
!
!
!
!
line con 0
exec-timeout 30 0
password 7 0822455D0A16
logging synchronous
login
line vty 0 4
exec-timeout 30 0
password 7 0822455D0A16
logging synchronous
login
line vty 5 15
exec-timeout 30 0
password 7 0822455D0A16
logging synchronous
login
!
!
!
end


Now when I connect a PC to the switchports (fastethernet 0/1/0-3) and enable DHCP on the PC they get an IP address but when I connect it to fastethernet 0/0-1 they do not get an ip address from dhcp.

How do i get those ports to be part of VLAN1 so they can get ip address from dhcp that I configured.

notgoing2fail

Well by default they should be on VLAN 1 because that's the native VLAN for 802.1Q.

But to be sure, just issue this command in subinterface config mode.


switchport access VLAN 1

mikej412

super22 wrote: »

interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
duplex auto
speed auto

You haven't told us the hardware/simulator your using -- so I'll guess those are routed ports on a router. Since you don't have an IP address configured, those ports aren't running IP.....

super22 wrote: »

when I connect it to fastethernet 0/0-1 they do not get an ip address from dhcp.

If you have a PC plugged into FA0/0 or FA0/1 with a crossover cable, it has nothing to talk to since the ports aren't running IP.

What does a show ip int brief show? Protocol down?

super22

mikej412 wrote: »

You haven't told us the hardware/simulator your using -- so I'll guess those are routed ports on a router. Since you don't have an IP address configured, those ports aren't running IP.....


If you have a PC plugged into FA0/0 or FA0/1 with a crossover cable, it has nothing to talk to since the ports aren't running IP.

What does a show ip int brief show? Protocol down?

oh yeah sorry

well im just using packet tracer 5

and yes it does show protocol down...

so that means that i have to assign an ip address to those ports so the pc connected to it can get ip using dhcp?

so that also means that i have to assign a default-router and exclude those routers.

is there a way I can function those ports like the switchports?

thanks a lot!

mikej412

super22 wrote: »

so that means that i have to assign an ip address to those ports so the pc connected to it can get ip using dhcp?

Your routed interfaces can't overlap with an exiting network space, so you'd have to also define DHCP pools to match those new networks.

super22 wrote: »

so that also means that i have to assign a default-router and exclude those routers.

You exclude the router interfaces from the new DHCP pool and configure DHCP to support the clients out on those new networks.

super22 wrote: »

is there a way I can function those ports like the switchports?

You can configure those Fast Ethernet interfaces for bridging -- but you wind up with a router acting as a very expensive low density switch.

And bridging your router interfaces isn't a CCNA topic -- and probably isn't supported by Packet Tracer.