• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New switch what else to setup?

Operations

n00b
Joined
Mar 11, 2019
Messages
45
I have just bought and received a D-link 1510-28x. I wanted a switch with 10Gbit ports so that i could connect my servers (with Mellanox 10Gb cards) to it.

I have setup the switch, i immediately replaced the noisy fan with a Noctua 40mm one.
I have setup my vLANs (and static IP) and created a team of the two ports which are connected to my other switch. I have also created a PRTG sensor to check if the switch is online, not really configuration on the switch i know.

My question is, what else would you normally setup / configurated on a new switch? I mean it it working fine now, but switches (so also this one) have got so many options. So i am wondering if you guys do more configuration to a new switch.
 
I have just bought and received a D-link 1510-28x. I wanted a switch with 10Gbit ports so that i could connect my servers (with Mellanox 10Gb cards) to it.

I have setup the switch, i immediately replaced the noisy fan with a Noctua 40mm one.
I have setup my vLANs (and static IP) and created a team of the two ports which are connected to my other switch. I have also created a PRTG sensor to check if the switch is online, not really configuration on the switch i know.

My question is, what else would you normally setup / configurated on a new switch? I mean it it working fine now, but switches (so also this one) have got so many options. So i am wondering if you guys do more configuration to a new switch.
I see you have VLANs. My typical case scenario is to setup ACLs along with VLANs to prevent someone on a limited VLAN from accessing other VLANs. I also handle DHCP from the switch. And, use the layer 3 routing feature on the switch, if you can.
 
So - let me just tell you from experience of what not to do - exactly what you are doing. Try to let your network serve and provide connectivity to your overall lab, and configurations and learning will come along with it. If you just take a switch and put it into a lab environment with no specific goals in mind, you're just going to be wandering aimlessly through the CLI and GUI coming up with use-cases.

Do you need to do DHCP from the switch? Maybe you have a Microsoft server for AD and also DHCP, so maybe you need DHCP relay configured on the switch. Wanna test dot1x authentication? Try configuring RADIUS on a server and do that.... etc. etc.
 
Sounds like the main reason for this switch was the 10G ports. If those are working, declare victory and stop until you have a need for one of the other functions.

Make sure you have done the basic stuff like change admin passwords, verifying the out of the box config isn't sending 'telemetry' to some out of network server, that any admin functions are only available from the local network, etc.

If you have one or more single function servers like DHCP, time server, etc., might be worth while to see if one or more could be retired and the functions moved to the switch.

Make a copy of your switch configuration to a backup device.
 
Back
Top