New ProCurve switch not visible

[Borvik]

Hello,

A couple of things first, I am not a networking person by default (but have picked up a few things here and there), and I'm sorry if this is an "E-Series" forum thread - I'm not sure which forum I should be using.

That said, here is the setup: we have an 5406zl as our core switch, this is connected to a 2650, and a 2626 that handle our servers. We just bought a 2530-48G to replace both the 2650 and the 2626. The 5406zl is using port A2 to connect to the 2650 on port 49, and A4 to 2626 on port 25.

During setup (so as not to disrupt our current connections), I decided to connect the new switch on port 1 to port 50 on the 2650 - eventually it should be going to port A2 on the 5406zl.

I'm having trouble making the new 2530 visible on the network. There are multiple VLANs, and there are trunks configured, and routing tables, but I'm not certain what in the configs are relevant to post.

I'm looking for some guidance to help me at least get it on the network. Once it is visible on the network and I can use the GUI or telnet into it I should be able to figure out the rest.

Thanks.

 

[Borvik]

Here are some of the settings that may be pertinent. Please let me know if anything else is required.

5406zl

...
trunk A2-A3 Trk2 LACP
trunk A4-A5 Trk3 LACP
ip routing
...
vlan 1
   name "Management"
   untagged A1,B3,B22,Trk2-Trk3
   qos priority 7
   ip address 192.168.101.2 255.255.255.0
   no untagged A6-A24,B1-B2,B4-B21,B23-B24,C1-C24,D1-D24
   exit
...
gvrp
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4

2650

...
interface 49
   no lacp
exit
interface 50
   no lacp
exit
trunk 49-50 Trk2 LACP
ip default-gateway 192.168.101.2
...
vlan 1
   name "DEFAULT_VLAN"
   forbid 33-39,41-48
   untagged Trk2
   ip address 192.168.101.3 255.255.255.0
   ip helper-address 192.168.104.2
   tagged 40
   no untagged 1-39,41-48
   exit
...
gvrp
spanning-tree
spanning-tree Trk2 priority 4

The new 2530

...
trunk 1 trk2 lacp
gvrp
ip default-gateway 192.168.101.2
...
vlan 1
   name "DEFAULT_VLAN"
   no untagged 2-52
   untagged Trk2
   ip address 192.168.101.5 255.255.255.0
   exit
...
spanning-tree
spanning-tree Trk2 priority 4

 

[VinceWhirlwind]

So, you have the 2530 which has a single port, port 1, member of a LACP trunk, Trk2, which is untagged in VLAN 1, with VLAN1 having an interface with 192.168.101.5
That port is connected to the 2650:
on port 50, which is a member of a LACP trunk, Trk2, which is untagged on VLAN1, with VLAN1 having an interface with 192.168.101.3

If both these ports are up? Do you have link lights?, then each switch should be able to ping the other.

If you can't ping, it isn't obvious what could be wrong, so what I would do is remove all the LACP trunking config from this link to reduce the amount of config you are looking at.

Check the log when you connect the switches and see if there are any events to give you clues.

 

[Borvik]

Sorry, I've managed to muddle through the setup so far, but I'm not networking person.

What is this log I should check, and how do I do that?

 

[VinceWhirlwind]

On the switches, "show log" or "Show log -r".

As you connect things up, you should get spanning tree events, LACP events, etc... that give you good clues.

MC

 

[Borvik]

I'm seeing something that looks like it could be something:

port 1 is Blocked by LACP
trunk Trk2 is now active
port 1 is Blocked by STP
port 1 in Trk2 is now on-line

 

[VinceWhirlwind]

So now do a show spanning-tree 1 and a show spanning-tree Trk2

Can the switches ping each other or not?

 

[Borvik]

They cannot ping each other.

#show spanning-tree 1
Module not present for port or invalid port: 1

#show spanning-tree Trk2

 Multiple Spanning Tree (MST) Information

  STP Enabled   : Yes
  Force Version : MSTP-operation
  IST Mapped VLANs : 1-4094
  Switch MAC Address : 6c3be5-ded680
  Switch Priority    : 32768
  Max Age  : 20
  Max Hops : 20
  Forward Delay : 15

  Topology Change Count  : 0
  Time Since Last Change : 6 days

  CST Root MAC Address : 6c3be5-ded680
  CST Root Priority    : 32768
  CST Root Path Cost   : 0
  CST Root Port        : This switch is root

  IST Regional Root MAC Address : 6c3be5-ded680
  IST Regional Root Priority    : 32768
  IST Regional Root Path Cost   : 0
  CST Root MAC Address : 6c3be5-ded680
  CST Root Priority    : 32768
  CST Root Path Cost   : 0
  CST Root Port        : This switch is root

  IST Regional Root MAC Address : 6c3be5-ded680
  IST Regional Root Priority    : 32768
  IST Regional Root Path Cost   : 0
  IST Remaining Hops            : 20

  Root Guard Ports     :
  Loop Guard Ports     :
  TCN Guard Ports      :
  BPDU Protected Ports :
  BPDU Filtered Ports  :
  PVST Protected Ports :
  PVST Filtered Ports  :

                  |           Prio              | Designated    Hello
  Port  Type      | Cost      rity State        | Bridge        Time PtP Edge
  ----- --------- + --------- ---- ------------ + ------------- ---- --- ----
  Trk2            | Auto      64   Disabled     |

 

[Borvik]

I queried a colleague of mine, and he found the problem. The trunk group on the old switch (the 2650) spanned two ports, and I was unaware that for a trunk group, each port must connect to the same switch. I had on going to our core switch (the 5406zl) and the other going to our new switch. He reconfigured an unused port on the 2650 as a different trunk group and I plugged the new one into that and it is now working.