Not been left Switch IPs

[Shadow_Walker]

Long story cut short. Started a new job a couple of months back and have not been left any of the switch ip addresses. Also each cab has not been labelled properly so not sure where they go back to or what is attached to each one. We could also know what is attached to each one as we want to re do the setup at some point!

 

Most of the switches are HP Pro Curve 2524

[pete]

I forsee a console cable in your future.

 

Fire up nmap or similar and start port scanning? I assume if the previous incumbent wasn't diligent enough to write documentation they also weren't diligent enough to configure a management VLAN, so you should find likely candidates. Look for devices listening on port 22/80/443 that aren't things you recognise and go from there.

 

nmap --open -p 22,80,443 10.0.0.1-255 > results.txt

 

That would scan the IP range and report if ports 22, 80 or 443 were open. From there you can whittle the list of candidates down.

 

Once you have some candidates, use (nmap -A 10.0.0.1) to provide a bit more detail about what the host could be, based on service info.

 

CDP or LLDP (show lldp info remote-device e2) might give you some clues too, if you have a login to at least one switch (that supports lldp/cdp).

Edited August 10, 2017 by pete

[ricki]

Put spiceworks on a server it will show you all sorts

[Shadow_Walker]

I forsee a console cable in your future.

 

Fire up nmap or similar and start port scanning? I assume if the previous incumbent wasn't diligent enough to write documentation they also weren't diligent enough to configure a management VLAN, so you should find likely candidates. Look for devices listening on port 22/80/443 that aren't things you recognise and go from there.

 

nmap --open -p 22,80,443 10.0.0.1-255 > results.txt

 

That would scan the IP range and report if ports 22, 80 or 443 were open. From there you can whittle the list of candidates down.

 

Once you have some candidates, use (nmap -A 10.0.0.1) to provide a bit more detail about what the host could be, based on service info.

 

CDP or LLDP (show lldp info remote-device e2) might give you some clues too, if you have a login to at least one switch (that supports lldp/cdp).

 

Thanks

 

I have never used that tool before. When i downloaded it and ran your command i got

 

Starting Nmap 7.60 ( https://nmap.org ) at 2017-08-10 13:15 GMT Summer TimeNmap done: 255 IP addresses (0 hosts up) scanned in 49.44 secondsFailed to resolve ">".Failed to resolve "results.txt".

 

Any ideas.

[pete]

Thanks

 

I have never used that tool before. When i downloaded it and ran your command i got

 

Starting Nmap 7.60 ( https://nmap.org ) at 2017-08-10 13:15 GMT Summer TimeNmap done: 255 IP addresses (0 hosts up) scanned in 49.44 secondsFailed to resolve ">".Failed to resolve "results.txt".

 

Any ideas.

 

I'm doing it on Linux, but adding "> results.txt" on the end of a command should redirect the output to a text file called "results.txt". That works on Windows for other applications, so I don't see why Nmap would be different. Lose the "> results.txt" part for now.

 

You adjusted the IP range (10.0.0.1-255) for one appropriate to your network/VLAN, right? When you ran nmap it checked 255 hosts but didn't find anything with ports 22,80 or 443 open, then whined because it decided ">" and "results.txt" were also hosts.

 

If you're really finding nothing on the IP ranges at your school, maybe check to see if the previous person was using telnet (port 23)?

Edited August 10, 2017 by pete

[Shadow_Walker]

I'm doing it on Linux, but adding "> results.txt" on the end of a command should redirect the output to a text file called "results.txt". That works on Windows for other applications, so I don't see why Nmap would be different. Lose the "> results.txt" part for now.

 

You adjusted the IP range (10.0.0.1-255) for one appropriate to your network/VLAN, right? When you ran nmap it checked 255 hosts but didn't find anything with ports 22,80 or 443 open, then whined because it decided ">" and "results.txt" were also hosts.

 

If you're really finding nothing on the IP ranges at your school, maybe check to see if the previous person was using telnet (port 23)?

 

Ok changed the range to 10.165.x.0 and got some machines and 2 switches but that was it. I already had those 2 as they were new ones but still need the rest of them. This network is a bit of a mess to say the least.

[snagrat]

Do you actually know they have been assigned an IP address?

 

Are they currently managed in any way?

[Shadow_Walker]

From what i can see we have some VLANS set up so i take it as a yes. However i could be wrong, any way to check?

[Shadow_Walker]

I just found a console cable in one of the store rooms. It looks like it is console (serial) to ethernet. Issue is that when i plugged it in and loaded up putty it could not get a connection!!! Also the laptop supplied does not have an ethernet port so using a usb converter so could this be an issue as well?

[steveg]

That sounds like it may be the wrong console cable for that switch - I believe the hp 2524 switches have a serial port on the front of the switch? In which case you want a serial to serial cable, and a serial to usb converter if you don't have a serial port on the laptop.

 

The cable you have, you would connect the serial port end to a laptop, and the rj45 plug would go into the console port on a switch (not one of the network ports).

 

Steve

[Ric_]

I just found a console cable in one of the store rooms. It looks like it is console (serial) to ethernet. Issue is that when i plugged it in and loaded up putty it could not get a connection!!! Also the laptop supplied does not have an ethernet port so using a usb converter so could this be an issue as well?

 

I believe that the 2524 has a 9-pin serial port on the front. You'll likely need a 9-pin to 9-pin cable. The 'plugging in a serial cable' section of the instructions can be found at ftp://ftp.hp.com/pub/networking/software/59692353.pdf page 2-15.

[Davit2005]

Long story cut short. Started a new job a couple of months back and have not been left any of the switch ip addresses. Also each cab has not been labelled properly so not sure where they go back to or what is attached to each one. We could also know what is attached to each one as we want to re do the setup at some point!

 

Most of the switches are HP Pro Curve 2524

 

To find out where they go back to run:

 

show lldp information remote (or sh ll i r for short) on each switch.

 

Once you get IP addresses for the switches set them up a A host record in DNS using their name etc. makes management so much easier.

[Shadow_Walker]

I found a serial to usb cable but still get nothing from putty all i get is an error saying unable to open serial port. Clutching at straws with this now

[Davit2005]

I found a serial to usb cable but still get nothing from putty all i get is an error saying unable to open serial port. Clutching at straws with this now

 

Check in Device Manager to make sure you have right com port for the Serial adapter set in Putty. Often have to do this myself :-).

[Shadow_Walker]

Check in Device Manager to make sure you have right com port for the Serial adapter set in Putty. Often have to do this myself :-).

Just checked device manager but it is coming up as an unknown device rather than a port

[Davit2005]

You'd need to install drivers for the USB / Serial and then Plug and Pray :-) .

[Shadow_Walker]

You'd need to install drivers for the USB / Serial and then Plug and Pray :-) .

Still not showing up. Could it be the cable could be a bad one?

[Davit2005]

I've normally used the Plugable USB/Serial and they do seem pretty good.

 

Pretty sure this is the one Plugable USB to RS-232 DB9 Serial Adapter (Prolific PL2303HX Chipset) | Plugable

 

Not all are the same however, some crash the OS :-( .

 

Have you tried the default IP for the switch? I had the same at on place and found all the switches were still using the default settings. I had to disconnect the switch from the uplink (all 20 of them) one at a time change the IP and then plug in the uplinks again. Of course you will not be able to do that if you still have end users plugged into the switch.

Edited August 11, 2017 by Davit2005

[Shadow_Walker]

I found another set of cables and have got into one!!!

 

Just got to work out how to use these HP switches now!

[Shadow_Walker]

New issue is that it seems to be stuck on the password box when i use Putty. I type in the password but i don't seem to get any response

[Steve21]

New issue is that it seems to be stuck on the password box when i use Putty. I type in the password but i don't seem to get any response

 

Sometimes with HP you need to hit enter a few times to get a screen might be worth a shot (assuming it's not etrored and just blank?)

 

Steve

[Shadow_Walker]

Sometimes with HP you need to hit enter a few times to get a screen might be worth a shot (assuming it's not etrored and just blank?)

 

Steve

 

I hit enter a couple of times and it bought up the hp writing and asked for the password but when i type it in i get no feedback if it is right or not

[dapaulio]

Couple things

Increase the baud rate on the serial port. Some of the more modern switches work at 15600. Read the manual for the switch to confirm baud rate

 

Try cycling the power on the switch. I have a couple hp switches that didn't connected until a restarted them.

 

Get a different serial cable

 

If all that fails and you don't know the password then it is likely that you will need to skip all steps above and factory reset and configure again.

Maybe the quickest solution

[Ric_]

If you're being prompted for a password, then a password was sensibly configured by your predecessor - your serial settings are correct or you wouldn't see anything. Your only option is to reset the switch to factory defaults (two cocktail sticks needed for these I think).

 

Even if you knew the IP at this point, you'd still need to know that password.

 

Edit - also... I think these switches had a bug in some firmwares where auth caused a memory leak which slowly brought down your whole switch. It could be you just hit this so the power cycle suggestion may also help.

Edited August 11, 2017 by Ric_

[dapaulio]

If you're being prompted for a password, then a password was sensibly configured by your predecessor - your serial settings are correct or you wouldn't see anything. Your only option is to reset the switch to factory defaults (two cocktail sticks needed for these I think).

 

Quite right I didn't read the whole thread where the OP managed to get to a password prompt.

 

Your options are limited to configuring the switch again I'm afraid.

 

I assume your predecessor has no config backups of the switches on site? This is something I would strongly advise on all your switches. Would make this situation easier in the future to remedy in case something went wrong.

 

Have you no other HP switches you can log on to? You may be able to backup and tweeK the config slightly to suit your problematic switch. Would save loads of time configuring all the vlans

 

If you can...

Type

sh run

and copy paste into a notepad

TweeK

On factory reset switch

Login

conf t

paste in to destination

wr mem