Which port connects your 5324 to the 6024?  Is it port 24 on 5324 connects to port 24 on 6024?  Port 1 on 6024 is not a member of any VLAN at this point based on your configuration.  Is that the port (g1) that connects to the rest of your production network?  Is it connecting to another switch?  Do you want the 10,20,30 VLANs to get trunk out that port (g1)?  If so, perhaps you need to configure port 1 as a trunk port similarly to how you configured the port 24?

Cuong.

We just tried your setup - seems to work for us.  Let's check some things:

• Are you using Windows for your workstation?  If so be aware that Windows allows you to configure a default gateway per interface and it is know that it gets confused sometime and pickup the wrong default gateway.
• You mentioned that from the 6024 you can ping into the hosts on the internal VLAN and also out to the production network correct?  If so, let's try this:
• • From the host on the VLAN, can you ping the interface on the 6024?  For example, from the host 192.168.79.1 can you ping your default gateway 192.168.79.253?
  • Then from your 192.168.79.1 interface can you ping the other interfaces on the 6024 such as the 192.168.11.253?

By systematically pinging the different segments, perhaps we can try to isolate the problem to the segment.  If you fail to get to the gateway then perhaps the problem is on the host.  If you can get to the gateway (192.168.79.253) but not to the external interface (192.168.11.253) then perhaps the problem is on the router.  If you can get through both but then cannot ping external addresses then perhaps the problem is at the next hop?  Try pinging the address of the router at the next hop (I'm assuming that's 192.168.11.244 or 192.168.11.20).  Perhaps it is the next hop that's not configured correctly?

Cuong.

The configuration we use is the exact same configuration you sent us.  We just loaded your configuration into our switch and test with it.  Note that in our setup the next hop from the 6024 is just the workstation we are pinging to.  We think the problem is at the next hop beyond the 6024 given that you can ping from the host on the VLAN all the way to the interface leaving the 6024 to the production network.  So you know that your packet is being routed to the appropriate interface so the question is why the next hop (the gateway beyond the 6024) doesn't response to the ping.  Do you have control over the router at the next hop?  Is it a router managed by your service provider or is it one of your own?  If its a service provider router perhaps it is blocking ping or it is incorrectly configured?

You might try isolating your test setup with your own router beyond the 6024 to simulate the service provider router then see if you can ping to it first.  If you can, then your setup is good and its just a question of what's happening on the next hop in the service provider network.

Cuong.