Comware

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.

Anyone at all?

You don't need to add routes to the switch for direct connected networks, like your own VLAN interface.

If PC on VLANx can't ping the VLANy interface, make sure the PC has proper route:
either default route, next-hop = IP address of switch on VLANx
or static route for VLANy/24 , next-hop = IP address of switch on VLANx

Did you solve it? I have the same behavior with 8 switches new brand.

I'm having exactly the same issue. I've initialized the switch five or six times and each time I've created three additional VLANs (Default is 192.168.1.0/24) and assigned untagged and tagged ports to all of them. I have then created VLAN interfaces with manual IP addresses. (10.10.1.254/24, 10.10.2.254/24, 172.16.1.1/30

Usually, all I see in the routing table is

127.0.0.0 255.0.0.0             Direct 0 127.0.0.1    InLoopBack0

127.0.0.1  255.255.255.255  Direct 0 127.0.0.1    InLoopBack0

192.168.1.0 255.255.255.0   Direct 0 192.168.1.1 Vlan-interface1

192.168.1.1 255.255.255.255 Direct 0 127.0.0.1    InLoopBack0

However, once or twice the switch has added the routes for one of the new interfaces!

10.10.1.0      255.255.255.0    Direct 0 10.10.1.254 Vlan-interface2

10.10.1.254 255.255.255.255  Direct 0 127.0.0.1      InLoopBack0

If I remove the IP address from the interface I can then create a static route but in my case, this route does not appear in the 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. 

Can anyone shed any light on this please? It is very frustrating!

OK. I think I understand what's happening now.

The routing table only shows active routes for the switch port that you are connected to.

Tagged GE1/0/24 in all four configured VLANs and connected laptop (192.168.1.2) to it. The routing table shows all of the static routes correctly.

Configure two WAPs 10.10.1.250 10.10.2.250 and connected them to untagged ports in their respective VLANs

Connected laptop (192.168.1.2) to GE1/0/1 (untagged in VLAN1) routing table now shows routes for VLANs 2 and 3 and I can ping both WAPs

Hope this helps

Thanks John for your post. It is a couple of months old but definitely made my day.

I just want to confirm that at least one port on the switch needs to be up with that VLAN tagged/untagged to it. I was trying to untag a port to which nothing was connected, but it does not work either. Then I tagged another port that was up and the routing table automatically changed.

Thanks for the help.