switched out

techEDtechED Member Posts: 55 ■■□□□□□□□□
Any help here would be great.
My freind loan me a Cisco Catalyst 5000 which was on his network but doesn't remember the switche ip address. Is there a way I can recover the switch ip address? (and yes he doesn't have a supervisor cable)
His gateway was 192.168.101.5?

I have connected the switch to my network and gave one PC on the network a 192.168.101.7 address so as to ping the switch to figure out its ip address but to no avail. I have tried everything from 192.168.101.10 thru 192.168.101.150.

I was just wondering if there was another way to discover the ip address for the switch?

Comments

  • techEDtechED Member Posts: 55 ■■□□□□□□□□
    i know the password, the ip addressis what I don't know and want to recover.
  • mgodinezmgodinez Member Posts: 12 ■□□□□□□□□□
    'show ip interfaces' command?

    mgodinez
  • techEDtechED Member Posts: 55 ■■□□□□□□□□
    no can do m..nez unable to connect to the switch, need ip address.
  • mikej412mikej412 Member Posts: 10,086 ■■■■■■■■■■
    techED wrote:
    no can do m..nez unable to connect to the switch, need ip address.
    So what's a supervisor cable?
    techED wrote:
    His gateway was 192.168.101.5?

    I have connected the switch to my network and gave one PC on the network a 192.168.101.7 address so as to ping the switch to figure out its ip address but to no avail. I have tried everything from 192.168.101.10 thru 192.168.101.150.

    Well.... if he had a /30 network, that 192.168.101.7 address would be the broadcast....

    Since this is your network, why don't you give your PC the gateway address of 192.168.101.5....

    Then ping 192.168.101.6.... just incase it was a /30 subnet....

    Then ping the broadcast addresses... starting with the /24 network -- 192.168.101.255 and see if you get anything in your arp cache.

    If there are access lists (and you can't access the console port) blocking icmps... then you might want to try a port scanner and hope the tcp/udp small servers are enabled.
    :mike: Cisco Certifications -- Collect the Entire Set!
  • WebmasterWebmaster Admin Posts: 10,292 Admin
    techED wrote:
    i know the password, the ip addressis what I don't know and want to recover.
    Oh... in that case, what Mike said.

    I need to go back to sleeping.gif
  • techEDtechED Member Posts: 55 ■■□□□□□□□□
  • david_rdavid_r Member Posts: 112
    Ed,
    How exactly did you "...connected the switch to my network?" You need to be on the same broadcast domain.

    port scanner is the easiest.

    take 5 mins and write a batch file to ping the whole network, one IP at a time.
    If you have excel, this should get you there.
    first cell ping -n 1 -w 20
    second cell =concatenate(c1,d1)
    3rd cell 192.168.1.
    4th cell 1-254

    Then copy the first two columns into a batch file.

    I'm not familiar with cat 5000's but what does the default GW have to do with this?

    Why can't you come up with a way to console into that switch?
  • techEDtechED Member Posts: 55 ■■□□□□□□□□
    I don't have a console cable, I connected it to a switch on my network (192.168.100.xx). Thats why I made a PC on the network 192.168.101.x so as to try and ping the switch.
  • Danman32Danman32 Member Posts: 1,243
    I would advise getting a console cable. Should be cheap enough. You could probably make one with a network cable and a DB9.

    There are some things you can only do through the console.
  • PCHoldmannPCHoldmann Member Posts: 450
    If you have a router around, you might try reverse telnet.

    1. get or make a rollover cable (1 to 8, 2 to 7, etc)

    2 connect to the AUX port of the router and the console port on the switch

    3 on the router, run "show line"

    4 there is a line number in front of each line, find the one for AUX

    5 Telnet to the router on port 2000 + line number i.e. line 65, telnet <router IP> 2065

    after you log in, you should have a console session to the switch.
    There's no place like ^$
    Visit me at Route, Switch, Blog
  • marlon23marlon23 Member Posts: 164 ■■□□□□□□□□
    PCHoldmann:

    why reverse telnet ?

    "#show cdp neighbors detail" from router should be enought.
    LAB: 7609-S, 7606-S, 10008, 2x 7301, 7204, 7201 + bunch of ISRs & CAT switches
Sign In or Register to comment.