Hello there. Trying to setup a VLAN on the above switch.
VLAN has been created, along with an IP for the VLAN interface.
The issue I have is that I cannot ping the VLAN gateway IP. I need to know whether it's because nothing has been untagged for that VLAN, or whether something is awry with static routes.
Now. When viewing the procedure for creating a new VLAN for this switch, I can see from screenshots that the appropriate static routes are automatically created for the new VLAN and it's respective interface IP in the 'IPv4 Routing' section. After creating my VLAN and the associated interface IP, the only entries in the routing section are for my default VLAN, and for the the 127.0.0.1 InLoopback0 interface.
As the routes weren't being created automatically, I set about creating the routes manually. This too, resulted in failure, as when specifying 192.168.0.1 as the next hop for the 192.168.0.0 network, the switch informed me of an error: bad/invalid next hop address.
I then found this -
http://www.tek-tips.com/viewthread.cfm?qid=1281900, after reading that this particular series of switch are based on older 3com devices. I switched the VLAN interface over to DHCP assignment and created the static route accordingly as follows:
Dest IP: 192.168.1.0
Mask: 255.255.255.0
Next Hop: 192.168.1.1
Interface: Vlan-Interface10
Doing it this way allowed me to create the route, as mentioned in the link. However, I still need another static entry to route 192.168.1.1 (this will be the IP for the VLAN gateway), to 127.0.0.1. Attempting to do so presents me with another 'Error: Invalid next-hop address'. I should also mention that the initial static route is created successfully, but appears in the 'Summary' section of the 'IPv4 Routing' section, along with the default VLAN details, but instead remains in the 'Configured Static Route Information' section of the 'Create' tab.
I all want to do is create a VLAN, assign it's GW IP, and be able to ping that gateway address from a PC in another VLAN. Do I have to ensure that a machine is first within the new VLAN before the ping will work? I ask as I have several VLANs configured on an HP Procurve 5300 series, and am able to ping the VLAN gateway regardless of assigning ports over to that new VLAN.
What I thought would be a simple task, seems mightily difficult to achieve with this switch.
James.
