Enterprise Switch Setup ?

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
is there a db9 on the switch right? I recall having that same cable, but I'll be darned if I can remember if thats how i got in :)
The serial connector on the switch is RJ45. I did order the DB9 to USB adapter, so if all goes well they both arrive tomorrow.
 

Mike A.

Known around here
Joined
May 6, 2017
Messages
3,825
Reaction score
6,377
Then you have the fun of figuring out the CLI to make the changes. Oh boy... ; )

One of the regulars here I remember seeing has a Supermicro switch in their rack that I just saw in a post the other day. Can't recall who it was though. Maybe change your title to include Supermicro in it and they might see it.
 

tigerwillow1

Known around here
Joined
Jul 18, 2016
Messages
3,815
Reaction score
8,424
Location
USA, Oregon
I didn't see where you gave the model # of the switch. In one supermico manual I glanced at it says the default management IP address is 192.168.100.102, and depending on the model, the management interface might not be available on all of the ports.
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
Its model SSE-G2252P, and I made progress. I now have accessed the Command Line Interface of the switch. To get here I needed:

  • Console cable USB to RJ45, conforming to Cisco standard for Console Cables --- alternatively I could have used a combination of DB9 to RJ45 Console Cable with a USB to DB9 Adapter.
  • Since I used a USB to RJ45 Console Cable, I needed to download a driver set for the cable.
  • Following Flintstone61 advice, I downloaded PUTTY, a terminal emulator for Windows.

Once installed, I connected to the Console Port on the switch and initiated a telnet session on Putty - got right into the Command Line Interface. Now I need to configure the basic settings, including DHCP and I should be good to go through the web interface from now on.

Hearty THANKS to all who helped!
 

user8963

Known around here
Joined
Nov 26, 2018
Messages
1,465
Reaction score
2,315
Location
Christmas Island
Hmm.. you dont need a serial cable...

You just have to reset it to default, do not connect it with any router/dhcp server

then just plug your computer in

change your ipv4 to

192.168.100.xxx
255.255.255.0

no gateway required

open your browser and go to 192.168.100.102 (should be the default ip for any factory resetted supermicro switch)
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
Hmm.. you dont need a serial cable...

You just have to reset it to default, do not connect it with any router/dhcp server

then just plug your computer in

change your ipv4 to

192.168.100.xxx
255.255.255.0


no gateway required

open your browser and go to 192.168.100.102 (should be the default ip for any factory resetted supermicro switch)
Where do I make those ipv4 settings?
 

user8963

Known around here
Joined
Nov 26, 2018
Messages
1,465
Reaction score
2,315
Location
Christmas Island
Where do I make those ipv4 settings?

you just have to use another ip NOT the 102 at the end but in the same subnet...

and NEVER give a switch a dhcp ip, some of them dont even have the option for that.

also if you have no idea of these enterprise switches, the vlan config on most of them is a little bit complicated and different to other vendors.
also you have to set your management vlan (default is 1) and the ports have to be in the same vlan (default all vlan 1) ... if you are on another vlan port, then you dont have access to it and then you need serial
 
Last edited:

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394

you just have to use another ip NOT the 102 at the end but in the same subnet...
I vaguely remember doing this with a command line .... ipconfig ... some time ago. I'll find it.

Good information. Thanks.
 

user8963

Known around here
Joined
Nov 26, 2018
Messages
1,465
Reaction score
2,315
Location
Christmas Island
I vaguely remember doing this with a command line .... ipconfig ... some time ago. I'll find it.

Good information. Thanks.
if you have already access via cli, you can just use "show ip interfaces" to get the ip

on some switches you have to first "enable" then "conf t"

as i remember from these supermicro switches, you can give dhcp by "ip address dhcp", but just read the manual
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394

you just have to use another ip NOT the 102 at the end but in the same subnet...

and NEVER give a switch a dhcp ip, most of them dont even have the option for that.

also if you have no idea of these enterprise switches, the vlan config on most of them is a little bit complicated and different to other vendors.
also you have to set your management vlan (default is 1) and the ports have to be in the same vlan (default all vlan 1) ... if you are on another vlan port, then you dont have access to it and then you need serial
I'm confused by your comment in the emboldened text.

In CLI, I was able to set the startup configuration for vlan 1 to look for DHCP assignment. As I understand it, now when I plug it into the router the switch will poll for an IP assignment. Once assigned, I can get into the web page for administration. BUT ... I have not gotten that far yet to see exactly what it does.

ETA: You are correct, the CLI command I used is ... ip address dhcp.
 

tigerwillow1

Known around here
Joined
Jul 18, 2016
Messages
3,815
Reaction score
8,424
Location
USA, Oregon
open your browser and go to 192.168.100.102 (should be the default ip for any factory resetted supermicro switch)
I read the same thing. But in the SSE-G2252P manual it says "An IPv4 address for this switch is obtained via DHCP by default". It then talks about changing the IP address using a command line interface. I do find this a bit confusing. With my cisco switch I just let it use DHCP, and typing its IP address gets me to the web interface.
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
Well, I am still unable to get into the web admin page on the switch.

My router assigns IPs in the 192.168.1.XXX range. Even after the configuration mentioned above, when I plug the switch into the router, it does not appear among the wired connections.

Correction ... I went back into the CLI on the switch and I think I found the IP address. Odd that the router does not show it.

Yep, I am in. FINALLY!
 

user8963

Known around here
Joined
Nov 26, 2018
Messages
1,465
Reaction score
2,315
Location
Christmas Island
I read the same thing. But in the SSE-G2252P manual it says "An IPv4 address for this switch is obtained via DHCP by default". It then talks about changing the IP address using a command line interface. I do find this a bit confusing. With my cisco switch I just let it use DHCP, and typing its IP address gets me to the web interface.
maybe they already made it for the stupid. those who dont use dhcp for switches can use static ip to configure it and those who use dhcp, can also get access..
i think most use these switches with uplink trunk ports, so they dont need dhcp... also dhcp would be on vlan 1 ... i am not sure if someone is using vlan1 ;)

i dont see any problems look up the default ip in the manual/internet, change computer ip to the subnet and get access..
but maybe this is too much in the todays world
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
maybe they already made it for the stupid. those who dont use dhcp for switches can use static ip to configure it and those who use dhcp, can also get access..
i think most use these switches with uplink trunk ports, so they dont need dhcp... also dhcp would be on vlan 1 ... i am not sure if someone is using vlan1 ;)

i dont see any problems look up the default ip in the manual/internet, change computer ip to the subnet and get access..
but maybe this is too much in the todays world
Well, I certainly feel like I qualify in the 'stupid' category after this experience. BUT ... I did manage to get into the switch via CLI and now via the web admin page. And I now know enough to be dangerous .... :)

Thanks once again to all who helped. I sincerely appreciate it.
 

SpacemanSpiff

Known around here
Joined
Apr 15, 2021
Messages
1,456
Reaction score
2,431
Location
USA
Depending on the age of the switch firmware, there was a phase were managed switches were advertised as having a web GUI, but it was not available until a certain amount of initial configuration was performed and written to NVRAM (saved). This often often included enabling the GUI, as it was disabled by default for security purposes. Based on what you shared, it seems like you set the config to DHCP. Maybe the changes at that point were never saved?
Congrats on getting it running!
 

icpilot

Getting comfortable
Joined
Feb 1, 2018
Messages
293
Reaction score
394
Depending on the age of the switch firmware, there was a phase were managed switches were advertised as having a web GUI, but it was not available until a certain amount of initial configuration was performed and written to NVRAM (saved). This often often included enabling the GUI, as it was disabled by default for security purposes. Based on what you shared, it seems like you set the config to DHCP. Maybe the changes at that point were never saved?
Congrats on getting it running!
I did, indeed, have to do several basic configuration steps using CLI and then save to the switch's flash memory. As best I can tell, the only way I could have access to the web GUI was to enable DHCP to have an IP assigned. Now that I'm in the GUI it seems I have many more controls, but that initial setup was all brand new to me. An experienced network guy would probably have been able to get it running in 30 seconds....LOL

Next challenge is to update the firmware to the latest ....
 

SpacemanSpiff

Known around here
Joined
Apr 15, 2021
Messages
1,456
Reaction score
2,431
Location
USA
Don't sell yourself short.. you got it running in less than 24 hours!!
 
Top