First managed switch

[sol1109]

I purchased a D-Link DGS-1100-08P POE managed switch that I am planning on using for my NAS and security cameras. I wanted to test it out but the default IP is 10.90.90.90 with a subnet of 255.0.0.0. I have been able to access its web page with a direct connection and my laptop set to a static IP and I have been able to access it over my wired system using the D-Link SmartConsole utility. My question is what changes should I make to integrate it into a standard home network. Is it as simple as changing the IP and Subnet or are there other things to consider? Also, If I change it to say 192.168.1.2 should I change the range on the router DHCP server to start at 192.168.1.3?

 

[abailey]

Yes you just need to change its IP to subnet mask to match your network. You would need to assign it an IP that is not in your DHCP range. I usually reserve the first 20 or so numbers for things that need a static IP. Maybe start your DHCP at 192.168.1.20.

 

[mervincm]

My question is what changes should I make to integrate it into a standard home network. Is it as simple as changing the IP and Subnet or are there other things to consider? Also, If I change it to say 192.168.1.2 should I change the range on the router DHCP server to start at 192.168.1.3?

You got it.
your options are (in order of ease IMO)

1) -just configure the switch for DHCP. Easiest, but if you have a lot of devices, it MAY change it's ip address over time.

2) -configure a reservation in your DHCP server for the switch (just need its MAC address) and then configure the switch for DHCP mode. One more step, but you can rely on the switch having a fixed IP, plus you have a single place documenting it's ip address (DHCP reservations)

3) -configure a reservation in your DHCP server for the switch (just need its MAC address) and then manually configure the ip address on the switch. Slightly harder, but you can rely on the switch having a fixed IP, you have a single place documenting it's ip address (DHCP reservations), you have an ip in your switch even if you boot it without a DHCP server around. Plus if you are working on the switch, and need to hardware reset it, you just need to put it into DHCP mode to get it the proper IP address again.

4) -reconfigure your DHCP server to exclude an address for the switch and then manually configure that ip address on the switch. Slightly harder usually, and less useful than option 3

I suggest option 1 or option 3.

 

[sol1109]

Thanks for your suggestions. I was able to use the management software to find it outside my IP range and reconfigure it so I can now use a standard browser URL to reach it. I had used what you listed as option 4 mervincm and that matches what you recommended as well abailey. I did find that IE-11 has an intermittent login problem unless you add the switch URL to its compatibility list. Found this listed elsewhere as a JAVA issue. I may play around with some of the other choices you mention mervincm.

 

[mervincm]

works great, just get a label maker and put the ip on it somewhere. a switch in this context is something you might setup then not touch for a really long time. If you forget and use that same IP somewhere else, you will have some fun troubleshooting!

 

[fistv]

works great, just get a label maker and put the ip on it somewhere. a switch in this context is something you might setup then not touch for a really long time. If you forget and use that same IP somewhere else, you will have some fun troubleshooting!

Plus 1 for the label maker.

 

[azazel1024]

Not a bad idea at all. I've been wanting/needing to get a lable maker and slap some lables on masking tape on my network wires so I remember what runs where. I haven't really needed that info, but it would be nice to have handy just by looking at the wire on the switch end.

I'd have labled my network gear by now, but I keep a bookmark to each piece of network gear on my desktop, laptop, tablet and phone. 2 switches, a pair of access points, network printer and router.

 

[fistv]

Not a bad idea at all. I've been wanting/needing to get a lable maker and slap some lables on masking tape on my network wires so I remember what runs where. I haven't really needed that info, but it would be nice to have handy just by looking at the wire on the switch end.

I'd have labled my network gear by now, but I keep a bookmark to each piece of network gear on my desktop, laptop, tablet and phone. 2 switches, a pair of access points, network printer and router.

All totally useless when you are on your knees behind equipment, in poor light with a pen light between your teeth looking at the back end of a 6 ethernet port server. Every static assigned machine has it's own label on it. I've also learned to dhcp a static devices interfaces just before I pull it off the network to retire it.

 

[sol1109]

I've also learned to dhcp a static devices interfaces just before I pull it off the network to retire it.

I usually factory default it.

 

[fistv]

I usually factory default it.

That too, but I usually didn't think about printers till after they were plugged in an start spewing print jobs before I can re ip them one or two reams later LOL.