PowerConnect 5424 basic questions about IP config, subnet, router IP etc.

Hello, I have a PowerConnect 5424, which was previously in use at a data center I was co-located at.  It has been well over a year since I logged into it and messed with anything, and even then, I spent all of 10 minutes setting it up and never looked at it again. It just worked.

I have moved from that data center and want to use this elsewhere now.  I have reset it to factory, and as soon as I find a serial to USB adapter that works with Macs, or borrow a friends computer, I will need to set it up.

I would access this deice over ssh or telnet, but mostly used the https browser based configuration tool.  I now have limited IP addresses and do not know if it is possible to use this switch without a static IP address to assign to it.  If I just plug it in now, as it stands from the factory, will it work as a switch with no changes in the initial setting at all?  Or do I need to login to the device, set the passwords up, and then set a static IP for the device... etc

If I have to give it an IP address, can I give it an address from my DHCP pool of local addresses from the router?  I seem to remember in the past I set each port on the switch to a specific IP address.  However, that may not be a requirement, and I may have just named the ports by the IP address that was on the machine plugged into it.  I just can not remember.

Ideally I do not want to waste any of my IP addresses, so any suggestions on how to set this up where my router will have 13 static IP addresses, but an entire pool of non routable internal addresses as well.  I am hoping to give the 5424 an IP address of 192.168.x.x which will be the address I contact it at to configure it.  However, things plugged into it will get IP addresses that are in the normal anyone in the world can access them address space.

Thanks for any help or suggestions.

Tags (2)
0 Kudos
1 Reply

Re: PowerConnect 5424 basic questions about IP config, subnet, router IP etc.

Set to factory defaults, the switch will switch untagged traffic.  Tagged traffic will be dropped.

You can assign an IP address to vlan 1 to manage the switch.  You can do this statically or via DHCP.

interface vlan 1
ip address /24


interface vlan 1
ip address dhcp

You can assign an IP address to a port also.

interface ethernet g1
ip address /24

Assigning an IP address to a port allows you to manage the switch via that port, but the port is no longer a switching port.   The port is actually just put in its own vlan.   This can be seen by the following command:

console# show vlan internal usage

Usage   VLAN   Reserved   IP address
------ ------ ---------- ------------
  g1    4094      No        Active


0 Kudos