Vlan 2 not able to ping gateway.

[gssagoo22]

we are able to ping and access networks from vlan1 to vlan 2 with no issues at all.

[GRANT3779]

Your subject says Vlan 2 is unable to ping GW, but PCs in Vlan 2 can reach PCs in Vlan 1? Did you mistype?

If communication is happening between the VLANs then I suspect the GW is reachable.

Are you talking about Vlan 3 PCs not being able to hit their GW?

[gssagoo22]

nope I did not mistyped anything. communication is happening between Vlan 1 and 2. the only problem is that we are not able to reach the gateway from VLan 2.

our gateway is a UTM box. is there anything need to configure at the gateway level?

[chrihussey]

Does the gateway have a route for the VLAN 2 network?

[gssagoo22]

on Gateway i have an entry with 172.17.0.0/16 to 172.16.1.1

[GRANT3779]

Where on the network and what device is 172.16.1.1?

Looking at your config you attached I see you have the following -

ip default-gateway 172.16.1.1

On a side note, I do not think you need this command as you are running the switch in Layer 3 mode. If it was Layer 2, then you would need that command.

Do you have a brief topology of the setup?

[gssagoo22]

172.16.1.1 is a UTM device acting as a Gateway..  

[GRANT3779]

Have you enabled IP Routing on the Core Switch first of all and then on your Core Switch add

ip route 0.0.0.0 0.0.0.0 172.16.1.1 as chrihussey has already advised?

[gssagoo22]

already done that..

#show ip route
Codes: C - connected, S - static, 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
i - IS-IS, su - IS-IS summary, 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 172.16.1.1 to network 0.0.0.0

C 172.17.0.0/16 is directly connected, Vlan2
C 172.16.0.0/16 is directly connected, Vlan1
S* 0.0.0.0/0 [1/0] via 172.16.1.1

[GRANT3779]

From your Core switch, can you ping the GW sourcing from the 172.16.x.x subnet?

Ping 172.16.1.1 source 172.16.1.37

?

[chrihussey]

Am I missing something here, but if the gateway is 172.16.1.1, why does it have a route saying "on Gateway i have an entry with 172.17.0.0/16 to 172.16.1.1".

Grant's earlier post said it should be:

ip route 172.17.0.0 255.255.0.0 172.16.1.37
ip route 172.18.0.0 255.255.0.0 172.16.1.37

[gssagoo22]

here are the ping result

Mcubecore2#ping
Protocol [ip]:
Target IP address: 172.16.1.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.17.1.30
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
Packet sent with a source address of 172.17.1.30
.....
Success rate is 0 percent (0/5)

[chrihussey]

As stated in my earlier post the switch needs a route pointing to your gateway. The default gateway statement is not sufficient. It also needs IP routing enabled.

[GRANT3779 · Accepted solution]

I am making some assumptions here -

Your UTM box  is the GW of last resort for your Network (address is 172.16.1.1)

The Core Switch (config you attached) is the default GW for your VLANs/Clients.

You cannot Ping VLAN 2 to UTM and Vice Versa.

If I understand what you are trying to achieve then I believe you will need routes on your UTM box.

ip route 172.17.0.0 255.255.0.0 172.16.1.37
ip route 172.18.0.0 255.255.0.0 172.16.1.37

On your L3 switch - enable IP routing.

[GRANT3779]

A topology might help. Where is the GW plugged into and what is the IP address of the GW?