This post is more than 5 years old
3 Posts
0
88695
October 20th, 2015 12:00
Enabling SSH on N2000
Hello,
I'm attempting to enable SSH/telnet management for my Dell PowerConnect N2048. Currently I am receiving timeouts when connecting to either. I've followed instructions on multiple forum posts, and this guide:
http://ciscoskills.net/2011/10/26/how-to-configure-ssh-on-dell-power-connect/
However, at this point I am fully stumped. I've generated both RSA and DSA keys, and the SSH server was enabled succesfully. I've bound the VLAN 1 to a static IP, which I assume worked properly(can see IP in show run) I also created a user with level 15 privilege. Currently I am only able to access the console via serial cable. Connecting to SSH does not ask for a username, and instead times out. Here is the output of show ip ssh:
SSH Server enabled. Port: 22
Protocol Levels: Versions 1 and 2.
SSH Connections Currently in Use: ............. 0
Maximum number of SSH Sessions Allowed: ....... 5
SSH Session Timeout: .......................... 600
RSA key was generated.
DSA key was generated.
SSH Public Key Authentication is disabled.
Active Incoming Sessions.
Ip Address User Name Idle Time Session Time
--------------- --------------- ------------ ------------
Am I missing something?
0 events found
dellis
3 Posts
0
October 21st, 2015 09:00
I believe it connects directly. I did no configuration with the port, so it should still be on the default settings of 22. I was getting ping replies when it was set to 172.16.0.99 (still timed out SSH/telnet), and I began to wonder if it was an IP address conflict. I set it to .97 instead, and now receive no replies to my pings. So it is definitely network configuration. The workstation I am running putty in is within the same subnet (.254.0) so I assume that it would not be the issue. I shut off the firewall on my workstation just in case that was the issue, but it made no difference.
Since I am not receiving ping replies, it must be something with my network config. The default gateway was not set when it was on .99, but I have just set it after switching to .97, however this made no difference.
dellis
3 Posts
0
October 21st, 2015 10:00
The IP, subnet, and gateway for the client are as follows:
172.16.0.190, 255.255.254.0, 172.16.0.1
The client is able to ping all other devices on the network. It appears as though VLAN 1 is indeed set to access mode. Below is the log for that command, in case it helps you in any way. (omitted potential mac address). I will research the changing of the interface number, and post any changes
console(config)#show interfaces detail gi1/0/1
Port Description Duplex Speed Neg MTU Admin Link
State State
--------- --------------------------- ------ ------- ---- ----- ----- -----
Gi1/0/1 N/A Unknown Auto 1518 Up Down
Port Description
--------- ----------------------------------------------------------------------
Gi1/0/1
Flow Control: Enabled
Port: Gi1/0/1
VLAN Membership mode: Access Mode
Operating parameters:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Default Priority: 0
GVRP status: Disabled
Protected: Disabled
Port Gi1/0/1 is member in:
VLAN Name Egress rule Type
---- --------------------------------- ----------- --------
1 default Untagged Default
Static configuration:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Port Gi1/0/1 is statically configured to:
VLAN Name Egress rule
---- --------------------------------- -----------
Forbidden VLANS:
VLAN Name
---- ---------------------------------
Port Gi1/0/1 Enabled
State: Disabled Role: Disabled
Port id: 128.1 Port Cost: 0
Port Fast: No (Configured: no ) Root Protection: No
Designated bridge Priority: 32768 Address: XXXX.XXXX.XXXX
Designated port id: 0.0 Designated path cost: 0
CST Regional Root: XX:XX:XX:XX:XX:XX:XX:XX CST Port Cost: 0
BPDUs: Sent: 0, Received: 0