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.

INFO

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

HADES private VLAN

  • VLAN1000
  • 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
192.168.100.12 lxhadeb02 10 Gbps
192.168.100.13 lxhadeb03 10 Gbps
192.168.100.14 lxhadeb04 10 Gbps
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 )
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 )
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"
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.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  
192.168.100.55 hadsw03 Netgear Manageable Switch
192.168.100.56 hadsw04 Netgear Manageable Switch
192.168.100.57 hadesdaqp01 Monitoring, SlowCtrl
192.168.100.58 hadesdaqp02 Monitoring, SlowCtrl
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
192.168.100.63 haepcp16 remote power control
192.168.100.64 haepcp13 remote power control
192.168.100.65 lecroy01 oscilloscope
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)
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.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
192.168.100.79 hades16 laptop in cave close to MU crate
192.168.100.80 hadesp25  
192.168.100.81-89 hadc01-9 VME CPUs
192.168.100.90 hadesp30  
192.168.100.91 hadesp31  
192.168.100.92 lxgp0464 DAQ PC from Munich. Ask Rafal Lalik
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  
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

GIFFWSX24 Foundry Switch

Monitoring

  • 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")
  • Statistics of errors/collisions on giffwsx24
  • 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)

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.

GIFTX04 Turbo Iron Switch (10Gbit)

Buffers

  • Buffer sizes: 2MB per Port
  • 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

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
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

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

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 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

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

Topic revision: r64 - 2012-02-13, PeterZumbruch
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki Send feedback | Imprint | Privacy Policy (in German)