HP Procurve 2610-48

[Jord9857]

Hi,

Whatever i do i cannot get to the portal or access through Putty using the 'default ip address'.

I was told the default ip address for this switch is 192.168.2.10

Therefore i set my ethernet ip on my desktop up as 192.168.2.20

Subnet of 255.255.0.0

Gateway of 192.168.2.10

Cannot ping or browse etc to the 192.168.2.10, got ethernet cable from Port 1 on the switch to my laptop.

Console ethernet port doesn't work & no other console port or serial port.

I've tried using this guide as well -https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c02597295

Could someone help on where i'm going wrong please? Thank you!

Jord

[parnassus]

---

@Jord9857 wrote: I was told the default ip address for this switch is 192.168.2.10
...
Could someone help on where i'm going wrong please? Thank you!

---

Hi Jord, probably what was told you is wrong or, at best, incomplete...thus the 192.168.2.10 isn't the correct IP Address through which you could contact your Switch (via SSH, Telnet or HTTP)...or it is correct but nobody told you on which port to connect in order for your host to land on the proper VLAN (the VLAN which own that IP Address).

---

@Jord9857 wrote: Console ethernet port doesn't work & no other console port or serial port.

Why it doesn't work? pay attention that you need a RJ45-to-Serial cable (don't get confused about RJ45 Connector style...that port is not Ethernet!) and eventually an additional Serial-to-USB - Serial here is DB9 - if the host you plan to use for direct managment has no Serial (DB9) port.

That's to say that your 2610-48 owns a RJ-45 Serial Console port and that port can generally be used to control your switch when you can't via usual IP (for reasons explained above)...you can use PuTTY (Serial Connection at 9600 baud) once you have proper cable(s) connected.

[Jord9857]

Hi,

Thank you for your response.

So i got a ethernet to USB cable (USB into my laptop & ethernet to console port). I use Putty & select Serial, COM5 & 9600 speed as it picks it up in Device Manager. I lierally sat there for a good few minutes and nothing happened no error messages or CLI.

Kind Regards

Jord