Revision as of 03:44, 13 July 2019 by Benrwong (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

switch-5-1 is a Netgear 10Gbe managed switch. The model is ProSafe XS716T. This switch is unlike many of the other switches in that you cannot ssh/telnet into it. You must tunnel into the private network and access it via it's IP address:

Currently, the switch only has a single gigabit link between it and switch-4-1. I hope to purchase some GBICs/SFPs and then link it with RACK0.

Quick Starting a Fresh NetGear Switch Model XS716T

By default, the XS716T will have a starting IP address of and a subnet mask of I connected to this switch by changing my local Windows 10 laptop's network adapter IP Address to and my subnet to This allows my laptop to be in the same LAN as the network switch. Then I downloaded Netgear's Smart Control Center: https://www.netgear.com/support/product/Smart%20Control%20Center%20(SCC).aspx#download

Once I connected to any port on the switch via ethernet cable to my laptop, I was able to access the switch's configuration page with a web browser by putting the switch's default IP address into the URL entry. From here, I was able to assign the proper static configurations.

Note: the 'Apply' button on the top right of the switch configuration screen saves the configuration. Be really careful not to save a bad configuration! The 'Apply' button doesn't really give a good indication the settings have been applied so only click it if you're really sure you have a configuration you want. If you're not sure, then press cancel.

The default network configuration is:

IP Address:
Subnet Mask:

I want this switch to change to the IP address that's within the cluster network:

IP Address:
Subnet Mask:

1) Create VLANs for BKS private network and UCSF Public network. Private network is VLAN 200. Public is VLAN 100.
2) IP connection can only be made through a port that is part of the management VLAN.
By default, all ports are VLAN 1 and PVID 1 (Port VLAN ID). Since our cluster's private network VLAN ID is 200, we have to change all ports to VLAN 200 EXCEPT for the port you are currently using to connect with your computer. Keep that port set to the default of VLAN 1.
3) Change the Management VLAN from VLAN 1 to VLAN 200 and change the switch's IP address from the default of to the BKS Private Network IP Address of your choosing.
4) Change your computer's IP address to a BKS private network IP address so it is within the same subnet as the switch. The interacting computer should have a private network address like 10.20.*.*/16. Use this to connect to the switch's new, non-default, IP Address.
5) Change your ethernet cable's connection to a different port. Your ethernet cable is probably still connected to the port that is in VLAN 1. Switch to a port that is VLAN 200. Since in the previous step, we changed every port to VLAN 200, you can basically switch to any other port.
5) As you login to the switch via the new IP address, use this moment to change the one lonely port that is VLAN 1 and make it VLAN 200 like all the other ports. You now basically have a dumb switch that can be a part of the cluster!

Further configuration will involve making LACP/trunks between this switch and other switches.

I have accidentally broken this configuration many times. Here's some of the actions I did: - Changing all the port PVIDs (Port VLAN ID) from 1 to 200 without having the necessary VLANs setup.