Unsolved
This post is more than 5 years old
3 Posts
0
7350
October 5th, 2017 12:00
PowerConnect 3524 Can't Access Web GUI
Hello,
We have an older 3524 switch that we recently reset and need to configure from scratch. I am able to telnet into the switch with putty and I deleted the startup config and reset the switch. I followed the setup wizard and set an ip address for vlan 1 along with an snmp community string. The switch is currently not on network, it is directly connected to an off-network laptop for configuration. The laptop is plugged into port 1. From what I understand, all ports are in vlan 1 by default. My problem is, after configuring the initial settings I still cannot access the GUI. I made sure the laptop nic was set to the same subnet as the switch. Any suggestions? Any help is greatly appreciated.
0 events found
vt1012
212 Posts
0
October 5th, 2017 12:00
Hello,
If you are able to ping it then you are 90% there. Be sure you have setup a user ID and password, and set Level 7 or 15 (whichever is the highest it will take) authentication. The command is something like "user USERNAME password PASSWORD level 15". Then use the ip address URL to connect. You will be prompted for the user ID and password.
Hope this helps!
-B
ncarpenter1992
3 Posts
0
October 5th, 2017 13:00
Thanks for your reply. I am actually not able to ping the switch either. It says destination unreachable. Which I don't understand because both the laptop and the switch are in the same subnet. The ip I have set on the switch is 172.16.9.250 /23 and the ip I have set on the laptop's nic is 172.16.9.20 /23.
vt1012
212 Posts
0
October 5th, 2017 15:00
Do you get a link light on port 1? The IP addresses should work I think. A few other things to try, make sure your Cat cable is good, or see if another cable works. Use a different switch port, possibly port 1 has become bad. If you can, try a simple IP subnet of something like 10.10.10.x/24, just to make sure the IP is working properly. You may also want to paste your new running configuration into this forum, and hopefully that will help someone to troubleshoot the issue. So I guess you can no longer telnet into the switch and must use the serial connection?
ncarpenter1992
3 Posts
0
October 6th, 2017 06:00
I have tried several different ports and I'm getting the same result. Here is my current running config. I also updated the firmware to the latest version overnight last night using the xmodem feature in SecureCRT. So maybe that had something to do with it, I'll try getting the GUI to come up again.
console# show run
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
interface vlan 1
ip address 172.16.9.250 255.255.254.0
exit
ip default-gateway 172.16.9.253
username admin password 5f4dcc3b5aa765d61d8327deb882cf99 level 15 encrypted
snmp-server community password rw 172.16.9.250 view DefaultSuper
snmp-server community private rw view Default
Default settings:
Service tag: 1M36VS1
SW version 2.0.0.66 (date 09-Mar-2017 time 13:23:09)
Fast Ethernet Ports
==========================
no shutdown
speed 100
duplex full
negotiation
flow-control off
mdix auto
no back-pressure
Gigabit Ethernet Ports
=============================
no shutdown
speed 1000
duplex full
negotiation
flow-control off
mdix auto
no back-pressure
interface vlan 1
interface port-channel 1 - 15
spanning-tree
spanning-tree mode STP
qos basic
qos trust cos
Talso235
5 Posts
0
September 4th, 2019 13:00