Solved

HP Procurve 5406zl Cant access via Management IP

Posted on 2014-01-10
5
1,466 Views
Last Modified: 2014-01-10
Hi,

I have just started to build up a new 5406zl as a core switch but I'm having issues with the management ip.

I have setup VLAN99 as a VLAN for the switch, but I cannot ping it from any of my VLANS.

I can how ever access the switches via ip by telnet through the console cable connected to the 5406zl.
I can also connect from the uplink switches via console cable and telnet back to the 5406zl.

All my other VLANS appear to functioning as expect. e.g. DHCP is coming from 10.1.10.10 to 10.1.20.x range. I can ping 10.1.10.x from 10.1.20.x and vice versa.

What have I missed?

Running configuration:

; J8697A Configuration Editor; Created on release #K.15.12.0012
; Ver #05:08.41.xx.xx.xx:xx
hostname "5406-Core"
module 1 type j9538a
module 2 type j9538a
module 3 type j9546a
module 4 type j9546a
module 5 type j9550a
ip routing
interface A1
   name "Uplink to Admin1"
   exit
interface A2
   name "Uplink to Admin2"
   exit
interface A3
   name "Uplink to Admin3"
   exit
interface B7
   name "Uplink to Admin4"
   exit
interface B8
   name "Uplink to Admin5"
   exit
interface E1
   name "Uplink to Firewall"
   exit
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   no untagged A1-A3,B7-B8,E1-E13
   untagged A4-A8,B1-B6,C1-C8,D1-D8,E14-E24
   ip address dhcp-bootp
   exit
vlan 10
   name "Servers"
   untagged E2-E13
   ip address 10.1.10.1 255.255.255.0
   exit
vlan 15
   name "iSCSI_A"
   ip address 10.1.15.1 255.255.255.0
   exit
vlan 16
   name "iSCSI_B"
   ip address 10.1.16.1 255.255.255.0
   exit
vlan 17
   name "vMotion"
   ip address 10.1.17.1 255.255.255.0
   exit
vlan 18
   name "vHA"
   ip address 10.1.18.1 255.255.255.0
   exit
vlan 20
   name "Workstations"
   tagged A1-A3,B7-B8
   ip address 10.1.20.1 255.255.255.0
   ip helper-address 10.1.10.10
   ip helper-address 10.1.10.11
   exit
vlan 30
   name "Printers"
   tagged A1-A3,B7-B8
   ip address 10.1.30.1 255.255.255.0
   ip helper-address 10.1.10.10
   ip helper-address 10.1.10.11
   exit
vlan 40
   name "Private_WiFi"
   tagged A1-A3,B7-B8
   ip address 10.1.40.1 255.255.255.0
   ip helper-address 10.1.10.10
   ip helper-address 10.1.10.11
   exit
vlan 41
   name "Warehouse_WiFi"
   tagged A1-A3,B7-B8
   ip address 10.1.41.1 255.255.255.0
   ip helper-address 10.1.10.10
   ip helper-address 10.1.10.11
   exit
vlan 42
   name "Public_WiFi"
   tagged A1-A3,B7-B8
   ip address 10.1.42.1 255.255.255.0
   ip helper-address 10.1.10.10
   ip helper-address 10.1.10.11
   exit
vlan 99
   name "Switch_Management"
   tagged A1-A3,B7-B8
   ip address 10.1.99.1 255.255.255.0
   exit
vlan 100
   name "Firewall_In"
   untagged E1
   ip address 10.1.100.1 255.255.255.0
   exit
management-vlan 99
spanning-tree
spanning-tree priority 0 force-version rstp-operation
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager

Open in new window

0
Comment
Question by:Tech Man
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 50

Expert Comment

by:Don Johnston
ID: 39771071
I have setup VLAN99 as a VLAN for the switch, but I cannot ping it from any of my VLANS.
That's how it's supposed to work. There is no inter-VLAN routing for the management VLAN.
0
 
LVL 1

Author Comment

by:Tech Man
ID: 39771091
That's how it's supposed to work. There is no inter-VLAN routing for the management VLAN.

So how to I manage this switch via ip from my desktop?
0
 
LVL 27

Assisted Solution

by:Steve
Steve earned 250 total points
ID: 39771098
yep. your config looks right to me. Management access is limited to VLAN 99 so the other VLANs canont see it by design.
0
 
LVL 50

Accepted Solution

by:
Don Johnston earned 250 total points
ID: 39771111
You can't have your cake and eat it too. :-)  

If you want to manage the switch from other VLANs, you can't use the management-VLAN feature.  So remove the "management-VLAN 99" command and you'll be able to manage your switch from any VLAN.
0
 
LVL 1

Author Closing Comment

by:Tech Man
ID: 39771315
Thanks, that was it, removed management-vlan 99
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question