HP switch in Cisco network not pingable

[nLinked]

Having some trouble pinging our new HP J9540A switch. From factory defaults, it has been setup as follows:

 

Main setup

IP of switch: 172.16.254.20/24, gateway 172.16.254.254

Spanning tree enabled

 

VLANs

VLAN ID: 113

Name: vlan 113

Ports: untagged A1-D24

Set as primary VLAN

 

We have a fibre connected to port B21 which is a fibre port. Link light is on, port status is UP.

 

I can't ping the switch (172.16.254.20) from my workstation from over the network. I'd like to manage it remotely so I know it's communicating.

I've tried disabling spanning tree, same issue. I've tried having port B21 as tagged and untagged, no difference.

 

The rest of the network are Cisco switches and routers. Any ideas most appreciated.

[localzuk]

If B21 is a 'trunk' port, then it should be tagged at the HP end. How have you got the other end set up on the Cisco switch?

 

There's some clues here which explain what's what between the 2 makes - http://2and2is5.wordpress.com/2011/02/05/trunking-between-cisco-and-hp-switches/

[nLinked]

The Cisco side of the fibre is not trunked, so I've set B21 on the HP (where the fibre goes into) as untagged. Saved and rebooted, double-checked the config, it is untagged on VLAN 113. Port light is still on, link status up. Still can't ping it

 

If I plug a laptop into any port, it won't get a DHCP IP either, although the link light comes on.

[localzuk]

So the other side has the port set to whatever the equivalent of 'untagged' on VLAN 113 too?

[nLinked]

That's correct, not trunked on the Cisco side.

 

I may have found the problem. Reading a HP user guide for the switch, it says:

 

"In the factory-default configuration, the switch has one, permanent default VLAN (named

DEFAULT_VLAN) that includes all ports on the switch. Thus, when only the default VLAN exists in

the switch, if you assign an IP address and subnet mask to the switch, you are actually assigning

the IP addressing to the DEFAULT_VLAN.

 

If multiple VLANs are configured, then each VLAN can have its own IP address.

"

 

The only place I set the IP was the setup screen, which means it's applied it to the default VLAN only. I'm going to try show vlan command, and it should say:

 

DEFAULT_VLAN | Manual

VLAN113 | Disabled

 

I'll then set the global IP to DHCP again like factory defaults, and manually set the IP for the VLAN using:

vlan

ip address

 

Hopefully that will work, will try and update here soon.

 

Thanks

Edited April 18, 2013 by nLinked

[nLinked]

Unfortunately putting the IP on the VLAN didn't work either. Either way I can't ping the gateway 172.16.254.254 from the HP switch itself, times out. I can ping it from any workstation though which are connected to other Cisco switches (no machines connected to the HP yet as they won't pick up IPs from it).

 

EDIT: "can"

Edited April 18, 2013 by nLinked

[localzuk]

Thing is - it shouldn't matter if the switch has an IP or not for machines plugged in to the switch - this is handled at lower layers than level 3.

 

So, you have an issue with the connectivity between the HP and Cisco switch - which is why I'm talking about the trunk.

[cpjitservices]

you need to trunk the ports between the Cisco and the HP, and make sure you add the VLANS to the trunk. Also check the encapsulation on the switch for the trunk ports, cisco has a proprietary protocol , make sure it is 802.1q not ISL. Trunk the ports which connect both switches together.

[twin--turbo]

what is the configuration of the port on the cisco

 

it should be mode "access"

and have the access vlan that is on the 172.16.254.20/24 network.

 

Rob

[TronXP]

Unless I have missed something have we confimed that a computer plugged into the HP switch can ping something on the cisco switch, because all that has been said so far is about talking to the "switch" and by this I assume he means the management part of the switch.

[nLinked]

you need to trunk the ports between the Cisco and the HP, and make sure you add the VLANS to the trunk. Also check the encapsulation on the switch for the trunk ports, cisco has a proprietary protocol , make sure it is 802.1q not ISL. Trunk the ports which connect both switches together.

 

Can confirm everything is 802.1q. I think trunking the ports is where I'm unclear. I've tried the following on the HP:

 

The fibre from the Cisco switch, is going into fibre port B21 on the HP switch.

 

So I did this on the HP:

vlan 1 | untagged a1-d24 (so default vlan is all untagged, I think it's like this by default anyway)

vlan 113 | tagged b21

 

I'm not sure how else to add B21 to a trunk. I also tried:

 

Menu > Switch Configuration > Port/Trunk Settings > Mode=Auto; FlowCTRL=Disable; Group=Trk1; Type=LACP for port b21

 

No joy.

 

I've only set the switch's IP and and subnet mask on the default setup screen. So when I view the IP config in the menu interface, I see:

 

Default VLAN: IP: 172.16.254.20/24

VLAN 113: IP: DISABLED

 

Although I did try removing the IP from the default VLAN and placing it on VLAN 113, no joy.

 

what is the configuration of the port on the cisco

 

it should be mode "access"

and have the access vlan that is on the 172.16.254.20/24 network.

 

Rob

 

The port connected to the same fibre on the Cisco side gives me this:

 

#show interfaces switchport

Name: Gi10/6

Switchport: Enabled

Administrative Mode: trunk

Operational Mode: trunk (member of bundle Po1)

Administrative Trunking Encapsulation: dot1q

Operational Trunking Encapsulation: dot1q

Negotiation of Trunking: On

Access Mode VLAN: 1 (default)

Trunking Native Mode VLAN: 1 (default)

Voice VLAN: none

Administrative private-vlan host-association: none

Administrative private-vlan mapping: none

Administrative private-vlan trunk native VLAN: none

Administrative private-vlan trunk encapsulation: dot1q

Administrative private-vlan trunk normal VLANs: none

Administrative private-vlan trunk private VLANs: none

Operational private-vlan: none

Trunking VLANs Enabled: ALL

Pruning VLANs Enabled: 2-1001

Capture Mode Disabled

Capture VLANs Allowed: ALL

 

Unless I have missed something have we confimed that a computer plugged into the HP switch can ping something on the cisco switch, because all that has been said so far is about talking to the "switch" and by this I assume he means the management part of the switch.

 

No, if I plug a laptop into any port on the HP switch, the laptop won't get an IP via DHCP, so I can't ping anything from the laptop. The HP switch can't even ping its gateway (172.16.254.254). Error is: The destination address is unreachable

[TronXP]

Have a look at this document, It may be able to point you in the right direction:

 

http://networktest.com/hpiop/hpiopcookbook.pdf

[twin--turbo]

"Pruning VLANs Enabled: 2-1001 ??"

 

Please do , on the cisco

 

#sh run int g0/6

 

Cheers

 

Rob

[nLinked]

"Pruning VLANs Enabled: 2-1001 ??"

 

Please do , on the cisco

 

#sh run int g0/6

 

Cheers

 

Rob

 

Ah ha, you might be onto something.

 

#show run interface gi 10/6

Building configuration...

 

Current configuration : 197 bytes

!

interface GigabitEthernet10/6

description CRITICAL PORT***BLOCK A UPLINK***

switchport

switchport trunk encapsulation dot1q

switchport mode trunk

no ip address

channel-group 1 mode on

end

[Destinova]

Untagged in the HP world means "native" or access in the Cisco world.

 

So, on the Cisco side your port is access vlan 1 and native vlan 1, while on the HP side you are using vlan 113. This is why they aren't talking.

 

You either need to make both sides access ports for the same vlan or trunk both sides and ensure they are using the same native vlan (recommended for interswitch links).

 

(although it is best practice from a security perspective to use a native vlan that does not exist on any access port)

 

Example:

 

(Cisco)

interface GigabitEthernet10/6

switchport

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk native vlan 113

spanning-tree mode point-to-point

end

 

(HP)

vlan 113

untagged b21

(any other vlans that need to be carried across this trunk should be "tagged")

vlan xxx

tagged b21

vlan yyy

tagged b21

 

Also, you need to ensure the Cisco switch is aware of the layer 2 vlan (113). 'Show vlan' will confirm this.

 

The longer explanation here is that in the Cisco world creating a trunk port automatically carries all tagged (802.1Q) vlan traffic and will forward any untagged traffic to ports on the native vlan (1 by default).

 

In the HP world you have to assign the native vlan (untagged, also 1 by default) and specify which vlans are to be carried across the trunk by "tagging" each.

Edited April 21, 2013 by Destinova