Difference: NetworkStructure (1 vs. 64)

Revision 64
Changes from r61 to r64
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 75 to 75
 
192.168.100.73 hadhvp02 CAEN power supply SY1527LC (hadhv002)
192.168.100.74 hadhvp03 CAEN power supply SY1527LC (hadhv003)
192.168.100.75 hadhvp04 CAEN power supply SY1527LC (hadhv004)
Added:
>
>
192.168.100.104 hadhvp08 CAEN power supply SY1527LC (hadhv008)
192.168.100.105 hadhvp09 not yet used (hadhv009)
192.168.100.106 hadhvp10 not yet used (hadhv010)
192.168.100.107 hadhvp11 not yet used (hadhv011)
 
192.168.100.76 hadds002 device server
192.168.100.77 kp1pcp075 Cryo PC
192.168.100.78 hadesp28 Magnet PC
Line: 84 to 88
 
192.168.100.90 hadesp30  
192.168.100.91 hadesp31  
192.168.100.92 lxgp0464 DAQ PC from Munich. Ask Rafal Lalik
Added:
>
>
192.168.100.93 lxhadgw01 HADES gateway PC
192.168.100.94 rpccam camera to monitor the RPC bubblers
 
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
192.168.100.99 hadescomp4  
Revision 61
Changes from r58 to r61
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 21 to 21
 
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04 10 Gbps
Added:
>
>
192.168.100.15 lxhadeb05 10 Gbps
 
192.168.100.18 hadsw14 Longshine switch (4 SFP )
192.168.100.19 hadsw13 Longshine switch (4 SFP )
192.168.100.20 hadsw12 Longshine switch (4 SFP )
Line: 81 to 82
 
192.168.100.80 hadesp25  
192.168.100.81-89 hadc01-9 VME CPUs
192.168.100.90 hadesp30  
Added:
>
>
192.168.100.91 hadesp31  
192.168.100.92 lxgp0464 DAQ PC from Munich. Ask Rafal Lalik
 
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
192.168.100.99 hadescomp4  
Revision 58
Changes from r55 to r58
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 6 to 6
 

Added:
>
>

INFO

  • we use passive SFP+-Direct-Attached-Copper cables for 10Gb connections between EB machines and the switch.
 

HADES private VLAN

  • VLAN1000
Changed:
<
<
  • Subnet: 192.168.100.0 /23 (subnetmask: 255.255.254.0)
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)
>
>
  • Subnet: 192.168.100.0 /22 (subnetmask: 255.255.252.0)
  • IP range: 192.168.100.11 - 192.168.103.249 (we should not use first 10 IPs and last 5 IPs)
 

IP Device Comment
192.168.100.11 lxhadeb01 10 Gbps
Line: 74 to 78
 
192.168.100.77 kp1pcp075 Cryo PC
192.168.100.78 hadesp28 Magnet PC
192.168.100.79 hades16 laptop in cave close to MU crate
Changed:
<
<
192.168.100.80 hades25  
192.168.100.81-96 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
>
>
192.168.100.80 hadesp25  
192.168.100.81-89 hadc01-9 VME CPUs
192.168.100.90 hadesp30  
 
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
192.168.100.99 hadescomp4  
Revision 55
Changes from r52 to r55
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 17 to 17
 
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04 10 Gbps
Added:
>
>
192.168.100.18 hadsw14 Longshine switch (4 SFP )
192.168.100.19 hadsw13 Longshine switch (4 SFP )
 
192.168.100.20 hadsw12 Longshine switch (4 SFP )
192.168.100.21 hadsw11 Longshine switch (4 SFP )
192.168.100.22 hadsw10 Longshine switch (4 SFP )
Line: 52 to 54
 
192.168.100.56 hadsw04 Netgear Manageable Switch
192.168.100.57 hadesdaqp01 Monitoring, SlowCtrl
192.168.100.58 hadesdaqp02 Monitoring, SlowCtrl
Added:
>
>
192.168.100.59 msix340 laptop in cave (registered in GSI VLAN as Lab Device)
 
192.168.100.60 laptop01.gsi.de laptop of Pavel
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
Revision 52
Changes from r49 to r52
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 58 to 58
 
192.168.100.63 haepcp16 remote power control
192.168.100.64 haepcp13 remote power control
192.168.100.65 lecroy01 oscilloscope
Added:
>
>
192.168.100.66 yokogawa01 oscilloscope
192.168.100.67 haepcp06 remote power control
 
192.168.100.69 hadhvp05 CAEN power supply SY1527LC (hadhv005)
192.168.100.70 hadhvp06 CAEN power supply SY1527LC (hadhv006)
192.168.100.71 hadhvp07 CAEN power supply SY1527LC (hadhv007)
Line: 69 to 71
 
192.168.100.77 kp1pcp075 Cryo PC
192.168.100.78 hadesp28 Magnet PC
192.168.100.79 hades16 laptop in cave close to MU crate
Added:
>
>
192.168.100.80 hades25  
 
192.168.100.81-96 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
Revision 49
Changes from r46 to r49
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 17 to 17
 
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04 10 Gbps
Added:
>
>
192.168.100.20 hadsw12 Longshine switch (4 SFP )
192.168.100.21 hadsw11 Longshine switch (4 SFP )
192.168.100.22 hadsw10 Longshine switch (4 SFP )
192.168.100.23 hadsw09 Longshine switch (4 SFP )
192.168.100.24 hadsw08 Longshine switch (4 SFP )
 
192.168.100.25 hadrt01 W-Lan router (D-Link DI-624)
192.168.100.26 hadsw05 Longshine switch (4 SFP )
192.168.100.27 hadsw06 Longshine switch (4 SFP )
Line: 68 to 73
 
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
192.168.100.99 hadescomp4  
Added:
>
>
192.168.100.249 hadsc1  
192.168.100.250 e7had2  
 
192.168.101.0-199 etraxp000-199 TRB with Etrax FS
192.168.101.200-250 etraxp200-250 TRB with Etrax MCM
Revision 46
Changes from r43 to r46
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 45 to 45
 
192.168.100.53 hadeb06b  
192.168.100.55 hadsw03 Netgear Manageable Switch
192.168.100.56 hadsw04 Netgear Manageable Switch
Changed:
<
<
192.168.100.57 hadesdaq01 Monitoring, SlowCtrl
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
>
>
192.168.100.57 hadesdaqp01 Monitoring, SlowCtrl
192.168.100.58 hadesdaqp02 Monitoring, SlowCtrl
 
192.168.100.60 laptop01.gsi.de laptop of Pavel
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
Line: 61 to 61
 
192.168.100.74 hadhvp03 CAEN power supply SY1527LC (hadhv003)
192.168.100.75 hadhvp04 CAEN power supply SY1527LC (hadhv004)
192.168.100.76 hadds002 device server
Changed:
<
<
192.168.100.77 kp1pc075 Cryo PC
192.168.100.78 hades28 Magnet PC
>
>
192.168.100.77 kp1pcp075 Cryo PC
192.168.100.78 hadesp28 Magnet PC
 
192.168.100.79 hades16 laptop in cave close to MU crate
Changed:
<
<
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
>
>
192.168.100.81-96 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
192.168.100.97 hadvmp08 Virtual Machine on Magnet PC
192.168.100.98 hadescomp3  
192.168.100.99 hadescomp4  
 
192.168.101.0-199 etraxp000-199 TRB with Etrax FS
192.168.101.200-250 etraxp200-250 TRB with Etrax MCM
Revision 43
Changes from r40 to r43
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 52 to 52
 
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
192.168.100.64 haepcp13 remote power control
Changed:
<
<
192.168.100.72 hadhv001 CAEN power supply
192.168.100.73 hadhv002 CAEN power supply
192.168.100.74 hadhv003 CAEN power supply
192.168.100.75 hadhv004 CAEN power supply
>
>
192.168.100.65 lecroy01 oscilloscope
192.168.100.69 hadhvp05 CAEN power supply SY1527LC (hadhv005)
192.168.100.70 hadhvp06 CAEN power supply SY1527LC (hadhv006)
192.168.100.71 hadhvp07 CAEN power supply SY1527LC (hadhv007)
192.168.100.72 hadhvp01 CAEN power supply SY1527LC (hadhv001)
192.168.100.73 hadhvp02 CAEN power supply SY1527LC (hadhv002)
192.168.100.74 hadhvp03 CAEN power supply SY1527LC (hadhv003)
192.168.100.75 hadhvp04 CAEN power supply SY1527LC (hadhv004)
 
192.168.100.76 hadds002 device server
192.168.100.77 kp1pc075 Cryo PC
192.168.100.78 hades28 Magnet PC
Line: 80 to 84
 
  • Buffer sizes: 32MB Ingress and 32MB Egress Buffers per PacketProcessor (one 32MB buffer per 12x1GbE Ports and one 32MB buffer for each 1x10GbE Port)
  • Removing buffer allocation limits: You can remove buffer allocation limits on all ports and all Traffic Classes globally. This permits all available buffers in a port region to be used in a first-come-first-serve basis by any of its ports, regardless of priority. By doing this , there is no limit on the number of buffers a port or a specific priority on a port can use. So one port could potentially use up all the available buffers of its port region and cause starvation on other ports of the port region.
Changed:
<
<

Turbo Iron Switch (10Gbit)

>
>

GIFTX04 Turbo Iron Switch (10Gbit)

 

Buffers

  • Buffer sizes: 2MB per Port
Changed:
<
<
  • TurboIron is a hybrid mode switch that can do both cut-through (sending the frame out while receiving it) and store-forward (basically, it has to - because it has ports with different speeds and also to provide QoS). This is why it needs a packet buffer. Default mode for TurboIron is cut-through, so it tries to use it as long as possible. In the case of congestion on the output port (for example, 2 ports sending traffic to 1) the switch falls back to store-and-forward and uses its buffer.
>
>
  • TurboIron is a hybrid mode switch that can do both cut-through (sending the frame out while receiving it) and store-forward (basically, it has to - because it has ports with different speeds and also to provide QoS). This is why it needs a packet buffer. Default mode for TurboIron is cut-through, so it tries to use it as long as possible. In the case of congestion on the output port (for example, 2 ports sending traffic to 1) the switch falls back to store-and-forward and uses its buffer.
 

Netgear GSM7212

Revision 40
Changes from r37 to r40
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 45 to 45
 
192.168.100.53 hadeb06b  
192.168.100.55 hadsw03 Netgear Manageable Switch
192.168.100.56 hadsw04 Netgear Manageable Switch
Added:
>
>
192.168.100.57 hadesdaq01 Monitoring, SlowCtrl
 
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
192.168.100.60 laptop01.gsi.de laptop of Pavel
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
192.168.100.64 haepcp13 remote power control
Added:
>
>
192.168.100.72 hadhv001 CAEN power supply
192.168.100.73 hadhv002 CAEN power supply
192.168.100.74 hadhv003 CAEN power supply
192.168.100.75 hadhv004 CAEN power supply
 
192.168.100.76 hadds002 device server
192.168.100.77 kp1pc075 Cryo PC
192.168.100.78 hades28 Magnet PC
Line: 79 to 84
 

Buffers

  • Buffer sizes: 2MB per Port
Changed:
<
<
  • This switch uses cut-through-technology which means there is no buffering. It sends the frame out while receiving it.
>
>
  • TurboIron is a hybrid mode switch that can do both cut-through (sending the frame out while receiving it) and store-forward (basically, it has to - because it has ports with different speeds and also to provide QoS). This is why it needs a packet buffer. Default mode for TurboIron is cut-through, so it tries to use it as long as possible. In the case of congestion on the output port (for example, 2 ports sending traffic to 1) the switch falls back to store-and-forward and uses its buffer.
 

Netgear GSM7212

Revision 37
Changes from r34 to r37
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 61 to 61
 

GIFFWSX24 Foundry Switch

Added:
>
>

Monitoring

 
Line: 70 to 71
 
      • show mac eth 17 (mac table for port 17)
      • show arp (arp table)
Changed:
<
<
Description of the Foundry switch configuration:
  • HADES VLAN: 39 ports
    • 12 ports (only 6 of which are shown in Fig.) will be taken by the data links from TRBs (or switches) according to the Fig. below
    • 16 ports will be taken by four EBs: 4x4x1Gbit (each EB will have 4x1Gbit link aggregation). All those 16 ports are tagged - they will see both GSI and HADES VLANs. All these features are being tested now.
    • 1 port for bridge machines (hadesdaq, lxhadesdaq, EPICS gateway)
    • 10 ports left for other our experimental needs
  • GSI VLAN: 7 ports
    • 1 port for bridge machines (hadesdaq, lxhadesdaq, EPICS gateway)
    • 3 downlinks to three 1Gbit netgear switches
    • 3 ports are left
  • 1 port for GSI WLAN
  • 1 port for accelerator VLAN
>
>

Buffers

  • Buffer sizes: 32MB Ingress and 32MB Egress Buffers per PacketProcessor (one 32MB buffer per 12x1GbE Ports and one 32MB buffer for each 1x10GbE Port)
  • Removing buffer allocation limits: You can remove buffer allocation limits on all ports and all Traffic Classes globally. This permits all available buffers in a port region to be used in a first-come-first-serve basis by any of its ports, regardless of priority. By doing this , there is no limit on the number of buffers a port or a specific priority on a port can use. So one port could potentially use up all the available buffers of its port region and cause starvation on other ports of the port region.

Turbo Iron Switch (10Gbit)

Buffers

  • Buffer sizes: 2MB per Port
  • This switch uses cut-through-technology which means there is no buffering. It sends the frame out while receiving it.
 

Netgear GSM7212

Revision 34
Changes from r31 to r34
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 17 to 17
 
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04 10 Gbps
Added:
>
>
192.168.100.25 hadrt01 W-Lan router (D-Link DI-624)
 
192.168.100.26 hadsw05 Longshine switch (4 SFP )
192.168.100.27 hadsw06 Longshine switch (4 SFP )
192.168.100.28 hadsw07 Longshine switch (4 SFP )
Line: 50 to 51
 
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
192.168.100.64 haepcp13 remote power control
Added:
>
>
192.168.100.76 hadds002 device server
192.168.100.77 kp1pc075 Cryo PC
192.168.100.78 hades28 Magnet PC
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
192.168.101.0-199 etraxp000-199 TRB with Etrax FS
Revision 31
Changes from r28 to r31
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"
Changed:
<
<

Network Structure

>
>

Network Structure

 

Our Foundry 10Gbit switch is "divided" into two VLANs: GSI VLAN and our private HADES VLAN. All the TRBs, switches and other network devices in the cave are in the HADES VLAN. All lxg machines are in the GSI VLAN.

Changed:
<
<

HADES private VLAN

>
>

HADES private VLAN

 

  • VLAN1000
  • Subnet: 192.168.100.0 /23 (subnetmask: 255.255.254.0)
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
Changed:
<
<
192.168.100.11 lxhadeb01 4 NICs
>
>
192.168.100.11 lxhadeb01 10 Gbps
 
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
Changed:
<
<
192.168.100.14 lxhadeb04  
>
>
192.168.100.14 lxhadeb04 10 Gbps
192.168.100.26 hadsw05 Longshine switch (4 SFP )
192.168.100.27 hadsw06 Longshine switch (4 SFP )
192.168.100.28 hadsw07 Longshine switch (4 SFP )
 
192.168.100.29 hadsw01 Longshine switch (4 SFP )
192.168.100.30 hadsw02 Longshine switch (4 SFP )
192.168.100.31 hadps001 "0-8V, 0-165A", "Agilent"
Line: 34 to 37
 
192.168.100.43 hadps013 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.44 hadps014 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.45 hadps015 "0-8V, 0-180A", "TDK-Lambda"
Changed:
<
<
192.168.100.50 lxhadesdaq  
>
>
192.168.100.46 hadps016 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.50 lxhadesdaqp 'p' stands for private network
 
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
192.168.100.53 hadeb06b  
Line: 45 to 49
 
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
Added:
>
>
192.168.100.64 haepcp13 remote power control
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
Changed:
<
<
192.168.101.00-99 etraxp000-099 TRB with Etrax FS
>
>
192.168.101.0-199 etraxp000-199 TRB with Etrax FS
192.168.101.200-250 etraxp200-250 TRB with Etrax MCM
 
Changed:
<
<

GIFFWSX24 Foundry Switch

>
>

GIFFWSX24 Foundry Switch

 

Line: 73 to 79
 
  • 1 port for GSI WLAN
  • 1 port for accelerator VLAN
Changed:
<
<

Netgear GSM7212

>
>

Netgear GSM7212

 
Changed:
<
<
Command Line Interface Mode Access:
>
>

Command Line Interface Mode Access:

 
Command Mode Access Method Exit
User EXEC This is the first level of access logout
Privileged EXEC From the User EXEC mode, enter enable exit
Line: 94 to 100
 
Stack Global Config Mode From the Global Config mode, enter the stack command.
Changed:
<
<
Network Interface commands
>
>

Network Interface commands

 
Mode Command Comment
Privileged EXEC network parms {ipaddr} {netmask} [{gateway}]  
Privileged EXEC network protocol {none / bootp / dhcp}  
User EXEC show network  
Changed:
<
<
User Account commands
>
>

User Account commands

 
Mode Command Comment
Global Config users name {username} add new user account
Global Config no users name {username} delete user account
Global Config users passwd {username} set password
Privileged EXEC show users  
Changed:
<
<
SSH and Telnet
>
>

SSH and Telnet

 
Mode Command Comment
Privileged EXEC ip ssh enable SSH
Privileged EXEC no ip ssh disable SSH
Line: 115 to 121
 
Privileged EXEC sshcon timeout {1-160} timeout of SSH session in minutes
Line Config no transport input telnet disable telnet
Changed:
<
<
Manipulations with config
>
>

Manipulations with config

 
Mode Command Comment
Privileged EXEC copy system:running-config nvram:startup-config save the running config to nvram
Changed:
<
<
How to update the firmware
>
>

How to update the firmware

  (The TFTP server is already installed on hadesdaq02, you can skip next step and go to 'Get firmware')
  • Install TFTP Server on a PC
    • mkdir /tftpboot
Line: 144 to 150
 
  • chown nobody:nobody /tftpboot/gsm7212-6.3.3.7.opr
  • chmod 777 /tftpboot/gsm7212-6.3.3.7.opr
  • On the switch run the following commands:
Changed:
<
<
    • save startup-config (in 192.168.100.58:/tftpboot/):
>
>
    • save the current startup-config of the switch (in 192.168.100.58:/tftpboot/):
 
      • copy nvram:startup-config tftp://192.168.100.58//netgearGSM7212-startup-config
    • update firmware:
      • copy tftp://192.168.100.58//gsm7212-6.3.3.7.opr system:image
Deleted:
<
<
An approximate number of the 1Gbit links (used for the data transport) connected to 10Gbit switch is given in the figure below. The light blue rectangles define intermediate layer which can be optical hubs or switches.
 
Changed:
<
<
Fig. Network structure:
network structure
>
>

Longshine GS9429

LongShine-GS9420-manual.pdf: LongShine GS9420 manual

Command Line Interface Mode Access:

Command Mode Access Method
System Enter "System", press {enter}
Console -
Port -
VLAN -
Aggr -
QoS -
Mirror -
IP -
SNMP -
Ratelimit -
Exit -

Command Line Interface

All settings via Command Line Interface or Web Interface are automatically stored in memory (will survive the reboot)

Mode Command Comment
System Configuration Show system settings
UserName {name} Set new user name
Systemname {name} Set new system name
Password {name} Set new password
Reboot Reboot the switch
IP Configuration Show ip settings
Setup {IP} {netmask} Set IP address and netmask
Web management {Enable/disable} Default: enabled

-- SergeyYurevich - 15 Apr 2010
 
Deleted:
<
<
-- SergeyYurevich - 05 Mar 2010
 

META FILEATTACHMENT attr="" comment="network structure" date="1233053771" name="net_cut.jpg" path="net_cut.jpg" size="130051" user="SergeyYurevich" version="1.1"
Added:
>
>
META FILEATTACHMENT attr="" comment="LongShine GS9420 manual" date="1271338802" name="LongShine-GS9420-manual.pdf" path="LongShine-GS9420-manual.pdf" size="1389745" user="SergeyYurevich" version="1.1"
Revision 28
Changes from r25 to r28
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 13 to 13
 
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
Changed:
<
<
192.168.100.11-14 lxhadeb01 4 NICs
>
>
192.168.100.11 lxhadeb01 4 NICs
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04  
 
192.168.100.29 hadsw01 Longshine switch (4 SFP )
192.168.100.30 hadsw02 Longshine switch (4 SFP )
192.168.100.31 hadps001 "0-8V, 0-165A", "Agilent"
Line: 74 to 77
 

Command Line Interface Mode Access:
Command Mode Access Method Exit
Changed:
<
<
User EXEC This is the first level of access To exit, enter logout
Privileged EXEC From the User EXEC mode, enter enable To exit to the User EXEC mode, enter exit
Global Config From the Privileged EXEC mode, enter configure To exit to the Privileged EXEC mode, enter exit
VLAN Config From the Privileged EXEC mode, enter vlan database To exit to the Privileged EXEC mode, enter exit
Interface Config From the Global Config mode, enter interface {slot/port} To exit to the Global Config mode, enter exit
Line Config From the Global Config mode, enter lineconfig To exit to the Global Config mode, enter exit
Policy-Map Config From the Global Config mode, enter policy-map To exit to the Global Config mode, enter exit
Policy-Class-Map Config From the Policy Map mode enter class To exit to the Policy Map mode, enter exit
Class-Map Config From the Global Config mode, enter class-map To exit to the Global Config mode, enter exit
Router OSPF Config From the Global Config mode, enter router ospf To exit to the Global Config mode, enter exit
Router RIP Config From the Global Config mode, enter router rip To exit to the Global Config mode, enter exit
Router BGP Config From the Global Config mode, enter router bgp {asnumber} To exit to the Global Config mode, enter exit
MAC Access-list Config From the Global Config mode enter mac access-list extended {name} To exit to the Global Config mode, enter exit
DHCP Pool Config From the Global Config mode, enter ip dhcp pool {name} To exit to the Global Config mode, enter exit
Stack Global Config Mode From the Global Config mode, enter the stack command. To exit to the Global Config mode, enter exit
>
>
User EXEC This is the first level of access logout
Privileged EXEC From the User EXEC mode, enter enable exit
Global Config From the Privileged EXEC mode, enter configure
VLAN Config From the Privileged EXEC mode, enter vlan database
Interface Config From the Global Config mode, enter interface {slot/port}
Line Config From the Global Config mode, enter lineconfig
Policy-Map Config From the Global Config mode, enter policy-map
Policy-Class-Map Config From the Policy Map mode enter class
Class-Map Config From the Global Config mode, enter class-map
Router OSPF Config From the Global Config mode, enter router ospf
Router RIP Config From the Global Config mode, enter router rip
Router BGP Config From the Global Config mode, enter router bgp {asnumber}
MAC Access-list Config From the Global Config mode enter mac access-list extended {name}
DHCP Pool Config From the Global Config mode, enter ip dhcp pool {name}
Stack Global Config Mode From the Global Config mode, enter the stack command.
 

Network Interface commands
Line: 112 to 115
 
Privileged EXEC sshcon timeout {1-160} timeout of SSH session in minutes
Line Config no transport input telnet disable telnet
Added:
>
>
Manipulations with config
Mode Command Comment
Privileged EXEC copy system:running-config nvram:startup-config save the running config to nvram

How to update the firmware (The TFTP server is already installed on hadesdaq02, you can skip next step and go to 'Get firmware')
  • Install TFTP Server on a PC
    • mkdir /tftpboot
    • chown nobody:nobody /tftpboot
    • chmod 777 /tftpboot
    • Edit /etc/xinetd.d/tftp
 
      service tftp
      {
              socket_type             = dgram
              protocol                = udp
              wait                    = yes
              flags                   = IPv6 IPv4
              user                    = root
              server                  = /usr/sbin/in.tftpd
              server_args             = -c -s /tftpboot
              disable                 = no
      }
  • Get firmware (gsm7212-6.3.3.7.opr from http://kb.netgear.com/app/answers/detail/a_id/919)
  • cp gsm7212-6.3.3.7.opr /tftpboot/
  • chown nobody:nobody /tftpboot/gsm7212-6.3.3.7.opr
  • chmod 777 /tftpboot/gsm7212-6.3.3.7.opr
  • On the switch run the following commands:
    • save startup-config (in 192.168.100.58:/tftpboot/):
      • copy nvram:startup-config tftp://192.168.100.58//netgearGSM7212-startup-config
    • update firmware:
      • copy tftp://192.168.100.58//gsm7212-6.3.3.7.opr system:image
  An approximate number of the 1Gbit links (used for the data transport) connected to 10Gbit switch is given in the figure below. The light blue rectangles define intermediate layer which can be optical hubs or switches.

Fig. Network structure:
network structure
Changed:
<
<
-- SergeyYurevich - 23 Oct 2009
>
>
-- SergeyYurevich - 05 Mar 2010
 

META FILEATTACHMENT attr="" comment="network structure" date="1233053771" name="net_cut.jpg" path="net_cut.jpg" size="130051" user="SergeyYurevich" version="1.1"
Revision 25
Changes from r22 to r25
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Changed:
<
<
I would like to start a discussion on the structure of our private network. Our 10Gbit switch will be "divided" into two VLANs: GSI VLAN and our private HADES VLAN. All the TRBs (plus 1Gbit switches if needed) will form HADES VLAN. All lxg machines will stay in GSI VLAN.
>
>
Our Foundry 10Gbit switch is "divided" into two VLANs: GSI VLAN and our private HADES VLAN. All the TRBs, switches and other network devices in the cave are in the HADES VLAN. All lxg machines are in the GSI VLAN.
 

HADES private VLAN

Line: 12 to 14
 

IP Device Comment
192.168.100.11-14 lxhadeb01 4 NICs
Changed:
<
<
192.168.100.29 hadlsw01 Longshine switch (4 SFP )
192.168.100.30 hadlsw02 Longshine switch (4 SFP )
>
>
192.168.100.29 hadsw01 Longshine switch (4 SFP )
192.168.100.30 hadsw02 Longshine switch (4 SFP )
 
192.168.100.31 hadps001 "0-8V, 0-165A", "Agilent"
192.168.100.32 hadps002 "0-8V, 0-165A", "Agilent"
192.168.100.33 hadps003 "0-50V, 0-30A", "TDK-Lambda"
Line: 33 to 35
 
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
192.168.100.53 hadeb06b  
Changed:
<
<
192.168.100.55 hadsw01 Netgear Manageable Switch
192.168.100.56 hadsw02 Netgear Manageable Switch
>
>
192.168.100.55 hadsw03 Netgear Manageable Switch
192.168.100.56 hadsw04 Netgear Manageable Switch
 
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
Added:
>
>
192.168.100.60 laptop01.gsi.de laptop of Pavel
 
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
Line: 67 to 70
 
  • 1 port for GSI WLAN
  • 1 port for accelerator VLAN
Added:
>
>

Netgear GSM7212

Command Line Interface Mode Access:
Command Mode Access Method Exit
User EXEC This is the first level of access To exit, enter logout
Privileged EXEC From the User EXEC mode, enter enable To exit to the User EXEC mode, enter exit
Global Config From the Privileged EXEC mode, enter configure To exit to the Privileged EXEC mode, enter exit
VLAN Config From the Privileged EXEC mode, enter vlan database To exit to the Privileged EXEC mode, enter exit
Interface Config From the Global Config mode, enter interface {slot/port} To exit to the Global Config mode, enter exit
Line Config From the Global Config mode, enter lineconfig To exit to the Global Config mode, enter exit
Policy-Map Config From the Global Config mode, enter policy-map To exit to the Global Config mode, enter exit
Policy-Class-Map Config From the Policy Map mode enter class To exit to the Policy Map mode, enter exit
Class-Map Config From the Global Config mode, enter class-map To exit to the Global Config mode, enter exit
Router OSPF Config From the Global Config mode, enter router ospf To exit to the Global Config mode, enter exit
Router RIP Config From the Global Config mode, enter router rip To exit to the Global Config mode, enter exit
Router BGP Config From the Global Config mode, enter router bgp {asnumber} To exit to the Global Config mode, enter exit
MAC Access-list Config From the Global Config mode enter mac access-list extended {name} To exit to the Global Config mode, enter exit
DHCP Pool Config From the Global Config mode, enter ip dhcp pool {name} To exit to the Global Config mode, enter exit
Stack Global Config Mode From the Global Config mode, enter the stack command. To exit to the Global Config mode, enter exit

Network Interface commands
Mode Command Comment
Privileged EXEC network parms {ipaddr} {netmask} [{gateway}]  
Privileged EXEC network protocol {none / bootp / dhcp}  
User EXEC show network  

User Account commands
Mode Command Comment
Global Config users name {username} add new user account
Global Config no users name {username} delete user account
Global Config users passwd {username} set password
Privileged EXEC show users  

SSH and Telnet
Mode Command Comment
Privileged EXEC ip ssh enable SSH
Privileged EXEC no ip ssh disable SSH
Privileged EXEC ip ssh protocol [1] [2] set protocol versions for SSH (default both 1 and 2)
Privileged EXEC sshcon timeout {1-160} timeout of SSH session in minutes
Line Config no transport input telnet disable telnet
  An approximate number of the 1Gbit links (used for the data transport) connected to 10Gbit switch is given in the figure below. The light blue rectangles define intermediate layer which can be optical hubs or switches.

Fig. Network structure:
Revision 22
Changes from r19 to r22
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 12 to 12
 

IP Device Comment
192.168.100.11-14 lxhadeb01 4 NICs
Added:
>
>
192.168.100.29 hadlsw01 Longshine switch (4 SFP )
192.168.100.30 hadlsw02 Longshine switch (4 SFP )
 
192.168.100.31 hadps001 "0-8V, 0-165A", "Agilent"
192.168.100.32 hadps002 "0-8V, 0-165A", "Agilent"
192.168.100.33 hadps003 "0-50V, 0-30A", "TDK-Lambda"
Line: 33 to 35
 
192.168.100.53 hadeb06b  
192.168.100.55 hadsw01 Netgear Manageable Switch
192.168.100.56 hadsw02 Netgear Manageable Switch
Changed:
<
<
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
>
>
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
192.168.100.61 jsnb04.gsi.de new laptop of Jan
192.168.100.62 haepcp02 remote power control
192.168.100.63 haepcp16 remote power control
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
192.168.101.00-99 etraxp000-099 TRB with Etrax FS
Revision 19
Changes from r16 to r19
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 33 to 33
 
192.168.100.53 hadeb06b  
192.168.100.55 hadsw01 Netgear Manageable Switch
192.168.100.56 hadsw02 Netgear Manageable Switch
Added:
>
>
192.168.100.58 hadesdaq02 Monitoring, SlowCtrl
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
Added:
>
>
192.168.101.00-99 etraxp000-099 TRB with Etrax FS
 
Changed:
<
<

Foundry switch

>
>

GIFFWSX24 Foundry Switch

 

Changed:
<
<
>
>
  • SSH access to giffwsx24:
    • Usefull commands to run:
      • show interfaces eth 17 (status of port 17)
      • show interfaces brief (port information in brief mode)
      • show mac eth 17 (mac table for port 17)
      • show arp (arp table)
 

Description of the Foundry switch configuration:
  • HADES VLAN: 39 ports
Line: 60 to 67
  Fig. Network structure:
network structure
Changed:
<
<
-- SergeyYurevich - 02 Feb 2009
>
>
-- SergeyYurevich - 23 Oct 2009
 

META FILEATTACHMENT attr="" comment="network structure" date="1233053771" name="net_cut.jpg" path="net_cut.jpg" size="130051" user="SergeyYurevich" version="1.1"
Revision 16
Changes from r13 to r16
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 12 to 12
 

IP Device Comment
192.168.100.11-14 lxhadeb01 4 NICs
Added:
>
>
192.168.100.31 hadps001 "0-8V, 0-165A", "Agilent"
192.168.100.32 hadps002 "0-8V, 0-165A", "Agilent"
192.168.100.33 hadps003 "0-50V, 0-30A", "TDK-Lambda"
192.168.100.34 hadps004 "0-8V, 0-165A", "Agilent"
192.168.100.35 hadps005 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.36 hadps006 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.37 hadps007 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.38 hadps008 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.39 hadps009 "0-50V, 0-30A", "TDK-Lambda"
192.168.100.40 hadps010 "0-50V, 0-30A", "TDK-Lambda"
192.168.100.41 hadps011 "0-50V, 0-30A", "TDK-Lambda"
192.168.100.42 hadps012 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.43 hadps013 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.44 hadps014 "0-8V, 0-180A", "TDK-Lambda"
192.168.100.45 hadps015 "0-8V, 0-180A", "TDK-Lambda"
 
192.168.100.50 lxhadesdaq  
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
192.168.100.53 hadeb06b  
192.168.100.55 hadsw01 Netgear Manageable Switch
Added:
>
>
192.168.100.56 hadsw02 Netgear Manageable Switch
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs

Foundry switch

Changed:
<
<
  • Graphs with used bandwidth for different time periods for our 10Gbps uplink to GIFRX81-13/3. (or go to current path "/", choose "Network" -> "giffwsx24" -> "Interface_Counters" -> "10GigabitEthernet49")
>
>
  • Torrus performance monitoring framework Graphs with used bandwidth for all ports of giffwsx24 (including 10Gbps uplink to GIFRX81-13/3). (or go to current path "/", choose "Network" -> "giffwsx24" -> "Interface_Counters" -> "10GigabitEthernet49")
 
Revision 13
Changes from r10 to r13
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 11 to 11
 
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
Changed:
<
<
192.168.100.11-12 lxhadeb01 2 NICs (HADES VLAN)
>
>
192.168.100.11-14 lxhadeb01 4 NICs
 
192.168.100.50 lxhadesdaq  
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
Added:
>
>
192.168.100.53 hadeb06b  
192.168.100.55 hadsw01 Netgear Manageable Switch
 
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs

Foundry switch

Changed:
<
<
Graphs with used bandwidth for different time periods for our 10Gbps uplink to GIFRX81-13/3. (or go to current path "/", choose "Network" -> "giffwsx24" -> "Interface_Counters" -> "10GigabitEthernet49")
>
>
 

Description of the Foundry switch configuration:
  • HADES VLAN: 39 ports
Revision 10
Changes from r7 to r10
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 11 to 11
 
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
Changed:
<
<
192.168.100.11 lxhadeb01 2 NICs (HADES VLAN)
>
>
192.168.100.11-12 lxhadeb01 2 NICs (HADES VLAN)
 
192.168.100.50 lxhadesdaq  
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
Added:
>
>
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.81-99 hadc01-19 hadc18 and hadc19 are in EELab (GSI-VLAN), thus they are served with GSI IPs
 

Foundry switch

Changed:
<
<
Graphs with used bandwidth for different time periods for our 10Gbps uplink to GIFRX81-13/3.
>
>
Graphs with used bandwidth for different time periods for our 10Gbps uplink to GIFRX81-13/3. (or go to current path "/", choose "Network" -> "giffwsx24" -> "Interface_Counters" -> "10GigabitEthernet49")
 

Description of the Foundry switch configuration:
  • HADES VLAN: 39 ports
Revision 7
Changes from r4 to r7
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

Line: 11 to 11
 
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
Changed:
<
<
192.168.100.11 lxhadeb01 lxhadeb01 has 2 NICs in HADES VLAN
192.168.100.12 lxhadeb01  
>
>
192.168.100.11 lxhadeb01 2 NICs (HADES VLAN)
192.168.100.50 lxhadesdaq  
192.168.100.51 hadesdaq  
192.168.100.52 hades27  
 
Added:
>
>

Foundry switch

 
Changed:
<
<

Configuration of the Foundry switch

>
>
Graphs with used bandwidth for different time periods for our 10Gbps uplink to GIFRX81-13/3.
 
Changed:
<
<
Description of the Foundry switch configuration:
>
>
Description of the Foundry switch configuration:
 
  • HADES VLAN: 39 ports
    • 12 ports (only 6 of which are shown in Fig.) will be taken by the data links from TRBs (or switches) according to the Fig. below
    • 16 ports will be taken by four EBs: 4x4x1Gbit (each EB will have 4x1Gbit link aggregation). All those 16 ports are tagged - they will see both GSI and HADES VLANs. All these features are being tested now.
Line: 35 to 38
  Fig. Network structure:
network structure
Changed:
<
<
-- SergeyYurevich - 30 Jan 2009
>
>
-- SergeyYurevich - 02 Feb 2009
 

META FILEATTACHMENT attr="" comment="network structure" date="1233053771" name="net_cut.jpg" path="net_cut.jpg" size="130051" user="SergeyYurevich" version="1.1"
Revision 4
Changes from r1 to r4
Line: 1 to 1
 
META TOPICPARENT name="HadesNetworkCountingHouse"

Network Structure

I would like to start a discussion on the structure of our private network. Our 10Gbit switch will be "divided" into two VLANs: GSI VLAN and our private HADES VLAN. All the TRBs (plus 1Gbit switches if needed) will form HADES VLAN. All lxg machines will stay in GSI VLAN.
Changed:
<
<
The configuration of the switch now is as follows:
>
>

HADES private VLAN

  • VLAN1000
  • Subnet: 192.168.100.0 /23 (subnetmask: 255.255.254.0)
  • IP range: 192.168.100.11 - 192.168.101.249 (we should not use first 10 IPs and last 5 IPs)

IP Device Comment
192.168.100.11 lxhadeb01 lxhadeb01 has 2 NICs in HADES VLAN
192.168.100.12 lxhadeb01  

Configuration of the Foundry switch

Description of the Foundry switch configuration:
 
  • HADES VLAN: 39 ports
Changed:
<
<
    • 12 ports will be taken by the data links from TRBs (or switches) according to the Fig. below
>
>
    • 12 ports (only 6 of which are shown in Fig.) will be taken by the data links from TRBs (or switches) according to the Fig. below
 
    • 16 ports will be taken by four EBs: 4x4x1Gbit (each EB will have 4x1Gbit link aggregation). All those 16 ports are tagged - they will see both GSI and HADES VLANs. All these features are being tested now.
    • 1 port for bridge machines (hadesdaq, lxhadesdaq, EPICS gateway)
    • 10 ports left for other our experimental needs
Line: 22 to 35
  Fig. Network structure:
network structure
Changed:
<
<
-- SergeyYurevich - 26 Jan 2009
>
>
-- SergeyYurevich - 30 Jan 2009
 
Added:
>
>
META FILEATTACHMENT attr="" comment="network structure" date="1233053771" name="net_cut.jpg" path="net_cut.jpg" size="130051" user="SergeyYurevich" version="1.1"
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)