Changes between Version 1 and Version 2 of Internal/Network/SBSwitches


Ignore:
Timestamp:
Feb 18, 2007, 2:23:11 AM (17 years ago)
Author:
anonymous
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/Network/SBSwitches

    v1 v2  
    11= Sanbox Switch =
    22
    3 Each two-node sanbox has a 16 port Netgear GS716T Gigabit Smart Switch with the FQDN of sw-sbXX.orbit-lab.org (where XX is sanbox number 01-09). FOr each of the switches ports 1-4 are reserved for CM subnet, ports 5-8 for sanbox control subnet while ports 9-12 are reserved for sanbox data subnet. Ports 13-15 are assigned to network managemtn while port 16 is, as in the case of other Orbit switches, us uplink trunk.
     3Each two-node sanbox has a 16 port Netgear GS716T Gigabit Smart Switch with the FQDN of sw-sbXX.orbit-lab.org (where XX is sanbox number 01-09). FOr each of the switches ports 1-4 are reserved for CM subnet, ports 5-8 for sanbox control subnet while ports 9-12 are reserved for sanbox data subnet. Ports 13-15 are assigned to network managemtn while port 16 is, as in the case of other Orbit switches, used for uplink.
    44
    55== Switch Configuration ==
    66
    7 Most important part of the confration are the two tables dealing with VLANs so that if you check the switch status it shows something like this for sanbox 1 (sw-sb01):
     7=== ===
     8=== ===
     9=== ===
     10
     11After configuration check VLANs setup by looking at the switch status and make sure that looks something like this (example is for sanbox 1 -> sw-sb01):
    812
    913=== IEEE 802.1Q PVID Table  ===
    … …  
    2226||3 || U || U || U || U ||    ||   ||   ||   ||   ||   ||   ||    ||   ||  ||  ||    T  T  T  T 
    2327||11||   ||   ||   ||   ||  U || U || U || U ||   ||   ||   ||    || T || T || T || T ||
    24 ||12||                          U  U  U  U  T  T  T  T 
     28||12||                          U || U || U || U || T || T || T || T ||
    2529
    2630Configuration is done under the VLAN entry.
    2731
    28 Note: the upstream switch has to have untagged port for SmartWizard to even see the unconfigured switch. Once new switch is configured (mainly trunk ports) the upstream switches port should be configured so that it provides propper trunking.
     32Note: New switch has to be connected to the upstream switches untagged port for SmartWizard to even see it. Once new switch is configured with VLANs the upstream switch port should be configured for propper VLAN trunkning.