Unsolved
This post is more than 5 years old
10 Posts
0
43223
December 16th, 2014 02:00
Can't get CLI response on Powerconnect 7048p
I just got a 7048p put in my lap to setup for a project. I don't know the entire previous history of the unit - so I powered it on - plugged a few cables into it to see if it would pass traffic (it does) - and hooked it up to my network to see if the OOB port would pull a DHCP address (it does).
I have it hooked up to a Digi terminal server on the administrative port, I can get to the Openmanage login page thru the DHCP addressed OOB port - and I can telnet to the switch at the DHCP address.
But I can't get into the thing. The major problem I think is that I get no response out of the admin port when I connect to it. The manual says that the initial username/password info must be set thru the Cli - so I'm guessing that without that happening first - there's no way I'm logging in thru the Openmanage web GUI - or thru a telnet session - is that correct?
Is there some default Openmanage user/pass I can use?
I believe I have the Digi port settings correct:
Port Profile: Console Management
Baud Rate: 9600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
I am using a regular CAT5 cable to go from the Digi port to the 7048 admin port. I do get a response indicating I am connecting with the client I'm using (SecureCRT)
I'm looking for any suggestions on how to get a response out of the CLI on this unit. - Thanks!
jwil44
10 Posts
0
December 16th, 2014 06:00
The emulation mode is set to VT100 - I checked that too. I don't have the DB9-RJ45 cable that came with the switch. I'm going thru a Digi terminal server - which usually has no problem connecting to just about any serial device as long as it's set correctly. The Digi has RJ45 ports - so I'm just using a regular CAT5 cable to go from the Digi RJ45 down to the RJ45 on the 7048.
I've seen some weird things before trying to connect to serial console ports - which is why I asked this question. I'm wondering if there is any known good combination that will work to connect to one of these switches: like using the original cable - and Hyperterm or something like that.
jwil44
10 Posts
0
December 16th, 2014 06:00
I'm definitely hooked up to the correct port - I've got the Digi terminal server going to the " |0|0| " port - and I've got the out of band management network port hooked up too. The out-of-band mgmt. port is correctly pulling a DHCP address - and I can actually get to the OpenManage web GUI login screen - but I can't get in there either. I can also telnet to the switch using the DHCP assigned address it has grabbed.
My problem is that I'm not getting a prompt - or any sort of response * at all * from the CLI.
I'll check out the manual link to see if it has anything that might help.
jwil44
10 Posts
0
December 16th, 2014 07:00
I think I figured it out.
The Digi server uses RJ45 ports to connect devices up to it.
Rummaging around in one of the lab guy's toolboxes - I found some cables labled "Digi cables" - with RJ45 connectors on both ends. Comparing the wiring on the connectors on both ends of the cables - I can see that there is some remapping of the individual wires within the cable. It may be wired as a crossover - I'm not sure, I can't remember the CAT5/6 crossover wiring from memory - and I'm not that familiar with serial cable wiring.
In any case - I tried it out on the 7048 switch at my workstation - and going from the Digi to the 7048's management port with a standard CAT5 cable - does not work. I get what appears to be a connection - but no response from the console. Using the "Digi" cable - I can get a response (the switch name prompt returns).
The switch I'm trying to get working is in my home lab - so I'll try out the cable tonite and see if it works - but based on this quick test - it should.
Thanks for the help - it at least got me thinking......
jwil44
10 Posts
0
December 16th, 2014 18:00
Confirmed - using the Digi cable (it's a blue CAT5 cable with a Digi part number) - does work to access the 7048. I believe what is going on is that a "regular" CAT5 cable has the twisted pairs going straight thru - whereas the Digi cable has at least one pair - reversed so the send and receive can talk to each other. But I am not an expert on serial cable pin outs.