Jump to content
EduGeek EdSec 2026 is Go! 27th Oct in Derby! Join us for a day of EdTech security focused talks, networking, and an evening social ×

Recommended Posts

Posted

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 -

3COm 4500 Inter Vlan routing newbie question - HP: A-Series networking solutions - Tek-Tips, 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.

 

Can anyone help?

Posted

This may seem a daft response but have you tried updating the firmware?

 

We had so many issues when we bought them originally, assigning vlans to ports meant we had to change the access rule of each port. It was only on the off chance i up graded the firmware and things changed autmatically.

 

Not the best of switches ive configured, the 2530s are possibly the best ones ive dealt with

Posted (edited)

Timbo343, Davit2005 - thank you for your replies.

 

Timbo343, hadn't thought about updating firmware - will grab the latest version.

Davit2005 - need inter VLAN routing. It's almost as if 'ip routing' hasn't been run on the switch, but after seeing a few others mention the same thing regarding this particular model of switch, I read that routing is on by default. It's just strange that the routes aren't being created automatically, along with the internal loopback interfaces.

 

Here's the current config:

display current-configuration

#

version 5.20.99, Release 1112

#

sysname CORE

#

domain default enable system

#

ipv6

#

telnet server enable

#

ssl version ssl3.0 disable

#

password-recovery enable

#

vlan 1

#

vlan 10

description Cygnets

#

domain system

access-limit disable

state active

idle-cut disable

self-service-url disable

#

user-group system

group-attribute allow-guest

#

local-user admin

password cipher $c$3$XCxJKTcIklnb9DlADGoG/R7tS4G/8BUPr2rlCmwBmwcp4Q==

authorization-attribute level 3

service-type telnet terminal

service-type web

#

stp mode rstp

stp enable

#

interface NULL0

#

interface Vlan-interface1

ip address 10.149.4.42 255.255.252.0

#

interface Vlan-interface10

ipv6 address auto link-local

ip address dhcp-alloc

#

interface GigabitEthernet1/0/1

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/2

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/3

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/4

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/5

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/6

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/7

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/8

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/9

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/10

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/11

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/12

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/13

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/14

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/15

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/16

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/17

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/18

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/19

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/20

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/21

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/22

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/23

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/24

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/25

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/26

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/27

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/28

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/29

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/30

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/31

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/32

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/33

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/34

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/35

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/36

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/37

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/38

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/39

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/40

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/41

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/42

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/43

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/44

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/45

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/46

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/48

port auto-power-down

stp edged-port enable

#

interface GigabitEthernet1/0/49

stp edged-port enable

#

interface GigabitEthernet1/0/50

stp edged-port enable

#

interface GigabitEthernet1/0/51

stp edged-port enable

#

interface GigabitEthernet1/0/52

stp edged-port enable

#

ip route-static 192.168.1.0 255.255.255.0 Vlan-interface10 192.168.1.1

#

undo info-center logfile enable

#

snmp-agent

snmp-agent local-engineid 383030303633413236353133443839343033333343303736

snmp-agent sys-info contact Hewlett Packard Enterprise Company 3000 Hanover St Palo Alto, CA 94304

snmp-agent sys-info version v3

#

load xml-configuration

#

user-interface aux 0

authentication-mode scheme

user-interface vty 0 15

authentication-mode scheme

 

 

From the commands available, I can't see a way to run an 'ip route x.x.x.x etc' or even to create a loopback interface.

 

Here's a shot from a walkthrough for the switch - the routing for the newly created VLAN can be seen. Network ID of the new VLAN points to the chosen IP for the VLAN interface, which in turn points to the internal loopback of 127.0.0.1.

 

IProutingtable.PNG

 

Thanks chaps.

Edited by MrJDH
Posted
We aren't doing any Intervlan routing on our switches, that's been done on our Smoothwall as we don't have any Layer 3 switches here. I didn't think the 1920s could do intervlan routing as they are only L2 switches, they can only be configured with ACLs. The 5300 switches are layer 3 switches so you are able to do this.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...