Can't ping Native (default) Vlan from created Vlan

[Carlos Trevino]

Erased.

[John Blakley]

Interface f0/6, according to your output above, is in vlan 4. Can you do a "show run int fa0/6" and "show int fa0/6 trunk" and post the results?
 

[Carlos Trevino]

erased

[John Blakley]

I'm still confused. You said that you want the native vlan (1) to be able to ping everything else? Is vlan 1 addressed at 172.10.6.x? The interface that you posted, f0/2, is configured as an access port to vlan 2. If the host is addressed at 172.10.4.x, then that should work. Then you said that you didn't know what to put for a gateway because there's no router and the native vlan has no address. If that's the case, the hosts in vlan 1 will not be able to ping anything outside of its own subnet. You must put an address on the vlan 1 svi on the switch for them to be able to route outside of its own network.

HTH,

John

[Carlos Trevino]

I'm sorry for all the confusion I was rushing yesterday. Ok this is what I have:

Switch

vlan 1: 172.10.6.1

vlan 10: 172.10.2.1

vlan 20: 172.10.4.1

ip route 0.0.0.0 0.0.0.0 172.10.6.2

Hosts

host 1: 172.10.6.10 255.255.255.0 Gateway 172.10.6.1 vlan 1

host 2: 172.10.2.10 255.255.255.0 Gateway 172.10.2.1 vlan 10

host 3: 172.10.4.10 255.255.255.0 Gateway 172.10.4.1 vlan 20

Router

172.10.6.2 255.255.255.0 connect to switch f0/1 vlan 1

Switch#show vlan

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/2, Fa0/3, Fa0/4
10   Sales                            active    Fa0/10
20   Marketing                        active    Fa0/20

Switch#show int f0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administrative Mode: dynamic auto
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)

Switch#show ip route

Gateway of last resort is 172.10.6.2 to network 0.0.0.0

     172.10.0.0/24 is subnetted, 3 subnets
C       172.10.2.0 is directly connected, Vlan10
C       172.10.4.0 is directly connected, Vlan20
C       172.10.6.0 is directly connected, Vlan1
S*   0.0.0.0/0 [1/0] via 172.10.6.2

Router#show ip route

Gateway of last resort is not set

     172.10.0.0/24 is subnetted, 1 subnets
C       172.10.6.0 is directly connected, FastEthernet0/0

Ping Tests

hosts on vlan1, vlan10,and vlan20 can all ping each other (fixed by adding address to vlan1 as you said...Thank you!)

host on vlan1 can ping router

New Problem: vlan10 and vlan20 can not ping router.... thereby can not access network beyond router

Thanks for all the help.

[John Blakley · Accepted solution]

Glad to hear vlan 1 is working now :) You're at the finish line. The reason that vlan 10 and 20 cannot ping the router is because the router doesn't know about those routes. On your router, you could add static routes pointing back to vlan 1's ip address:

ip route 172.10.2.0 255.255.255.0 172.10.6.1

ip route 172.10.4.0 255.255.255.0 172.10.6.1

That should work. For default routes, you'll need to add (on the switch):

ip route 0.0.0.0 0.0.0.0 172.10.6.2

Then your router will route for everything else...

HTH,

John

[John Blakley]

Just curious....are you erasing these posts or is something going on in the forum?

[Carlos Trevino]

I erased them. I made too many mistakes writing the question and thought it be too confusing for others. 

About the static route do I have to use it or can I use RIP or OSPF. I know RIP and OSPF work between routers how could I go about setting either one up in this situation. I tired 

Router(config)#router ospf 1
Router(config-router)#network 172.10.0.0 0.0.255.255 area 0
 

but it didn't work.

[John Blakley · Accepted solution]

Yes, you can use ospf or rip. OSPF would be better since it doesn't have the hop limitation.You would do the configuration that you have on the router also on the switch. You should see a neighbor come up:

sh ip ospf neighbor

You can then remove your static routes. If you're using the switch as the default gateway for all of your lan users, you still need a default route. You can do that with the static on the switch, or you can advertise a static from ospf on the router with:

ospf default-information originate

You need a static default route configured on the router for the above command to work, or you can do:

ospf default-information originate always

This will set the router as the default route for the switch.

HTH,

John

[Carlos Trevino]

Thanks everything works now!! Now off to the next challenge.

[Carlos Trevino]

erased