HP 2910al-24 - Link Aggregation problem

[greatbaybud]

JAN-31-2013

LACP - VLANS TRUNKED TOGETHER
VLAN2 - cifs (192.168.2.0/24) (192.168.2.10 gateway) 192.168.2.132
VLAN15 - iscsi (10.10.15.0/24) no gateway (non-routable) 10.10.15.132
VLAN16 - nfs (10.10.16.0/24) no gateway (non-routable) 10.10.16.132

HP2910al106# sh trunk
 Load Balancing
  Port | Name                             Type      | Group Type
  ---- + -------------------------------- --------- + ----- --------
  7    |                                  100/1000T | Trk1  LACP
  8    |                                  100/1000T | Trk1  LACP
  9    |                                  100/1000T | Trk1  LACP
  10   |                                  100/1000T | Trk1  LACP


HP2910al106# sh lacp
                           LACP
   PORT   LACP      TRUNK     PORT      LACP      LACP
   NUMB   ENABLED   GROUP     STATUS    PARTNER   STATUS
   ----   -------   -------   -------   -------   -------
   7      Active    Trk1      Up        Yes       Success
   8      Active    Trk1      Up        Yes       Success
   9      Active    Trk1      Up        Yes       Success
   10     Active    Trk1      Up        Yes       Success


HP2910al106# show vlan port trk1 detail
 Status and Counters - VLAN Information - for ports Trk1
  VLAN ID Name                 | Status     Voice Jumbo Mode
  ------- -------------------- + ---------- ----- ----- --------
  1       DEFAULT_VLAN         | Port-based No    No    Untagged
  2       vlan2-Subnet2        | Port-based No    No    Tagged
  15      vlan15-iSCSI         | Port-based No    No    Tagged
  16      vlan16-nfs           | Port-based No    No    Tagged


Ok, I seem to have lost my connection to one device in the lacp trunk group. I can't ping 192.168.2.132. It was working yestrday. I can ping everything else.

HP2910al106# ping 192.168.2.132
Request timed out.
HP2910al106# ping 10.10.15.132
10.10.15.132 is alive, time = 5 ms
HP2910al106# ping 10.10.15.133
10.10.15.133 is alive, time = 4 ms
HP2910al106# ping 10.10.16.132
10.10.16.132 is alive, time = 4 ms
HP2910al106# ping 10.10.16.133
10.10.16.133 is alive, time = 5 ms
HP2910al106#
HP2910al106# sh run

Running configuration:

; J9145A Configuration Editor; Created on release #W.14.38

hostname "HP2910al106"
time timezone -300
module 1 type J9145A
module 2 type J9165A
module 3 type J9165A
trunk 7-10 Trk1 LACP
ip default-gateway 192.168.1.9
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-6,11-24,A1,B1,Trk1
   ip address 192.168.1.106 255.255.255.0
   exit
vlan 15
   name "vlan15-iSCSI"
   ip address 10.10.15.10 255.255.255.0
   tagged A1,B1,Trk1
   exit
vlan 16
   name "vlan16-nfs"
   ip address 10.10.16.10 255.255.255.0
   tagged A1,B1,Trk1
   exit
vlan 2
   name "vlan2-Subnet2"
   tagged 24-A1,B1,Trk1
   no ip address
   exit
vlan 17
   name "vlan17-VMotion"
   ip address 10.10.17.10 255.255.255.0
   exit
timesync sntp
sntp unicast
sntp server priority 1 192.168.1.10 3
snmp-server community "public" unrestricted
snmp-server contact "Phil Vassall" location "Computer Room"
spanning-tree Trk1 priority 4
password manager

HP2910al106#

Any help would be appreciated.

Phil V.

[greatbaybud · Accepted solution]

It turns out that someone rebooted our cisco core switch without my knowledge. The port the HP switch was plugged into was not setup for trunking.

OUR CISCO C3750X-24

OLD CONFIG

VLAN2

config t

int range g1/0/11-12

description VLAN 2 (subnet 2)

switchport mode access

switchport access vlan 2

exit

NEW CONFIG

config t
 int range g1/0/11-12
 description VLAN TRUNKs
 switchport trunk encapsulation dot1q
 switchport mode trunk
 end

As soon as I did ran the command am able to ping 192.168.2.132 within the LACP trunk.

HP2910al106# ping 192.168.2.132 r 4
192.168.2.132 is alive, iteration 1, time = 2 ms
192.168.2.132 is alive, iteration 2, time = 3 ms
192.168.2.132 is alive, iteration 3, time = 3 ms
192.168.2.132 is alive, iteration 4, time = 2 ms
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 2/2/3
HP2910al106#

Appears everythings OK.