Difference between revisions of "HallD Online IP Name And Address Conventions"

From GlueXWiki
Jump to: navigation, search
(Crate Names)
Line 67: Line 67:
  
 
* Continue notation "halld<b><i>device</i></b>", where <i>device</i> is the name that describes the device type and the number of that device. For instance, <b>hallden2t2.jlab.org</b> or <b>halldbrooks1.jlab.org</b>. Or for High Voltage and Low Voltage devices <b>halldcaen1</b>, <b>halldmpod1</b>, <b>halldcan1</b>. For the main  file server we can use <b>halldfs1</b>, and for fast the RAID file servers we can use <b>halldraid1</b>, <b>halldraid2</b>.
 
* Continue notation "halld<b><i>device</i></b>", where <i>device</i> is the name that describes the device type and the number of that device. For instance, <b>hallden2t2.jlab.org</b> or <b>halldbrooks1.jlab.org</b>. Or for High Voltage and Low Voltage devices <b>halldcaen1</b>, <b>halldmpod1</b>, <b>halldcan1</b>. For the main  file server we can use <b>halldfs1</b>, and for fast the RAID file servers we can use <b>halldraid1</b>, <b>halldraid2</b>.
 
 
== Crate Names ==
 
 
* Each major detector component will have a number of crates named based on its GlueX name, followed by one or two digits specifying the number of the crate.
 
* If more than one detector component is a part of one crate only one name is assigned, preferably of the larger one or a name that can characterize both detectors, e.g. use "tag<i>x</i>" for TAGM&TAGH crates.
 
* Numbering assignment with respect to the geographical location (the map) will need to be created out before requesting IP names. The map should define one-to-one corresponds between this detector-based scheme and one based on the geographical location ordering of the crates in the racks and the Hall. 
 
* The VME crates with the JLab discriminators are separated from the other VXS crates, they are considered as a separate "detector" for the naming purposes.
 
 
{| border="1" cellpadding="2" align="left" valign="top"
 
!width="120"  | Detector
 
!width="150"  | Crate Names
 
!width="150"  | Possible modules
 
|-
 
| TAGM/TAGH      ||  tag1 - tag3    || fADC250/F1TDC
 
|-
 
| PS/PSC        ||  ps1  - ps2      || fADC250/F1TDC
 
|-
 
| ST            ||  st1  - st2      || fADC250/F1TDC
 
|-
 
| TRIG          ||  trig1 - trig2  || GTP/TS/TD
 
|-
 
| BCAL          ||  bcal1 - bcal12  || fADC250/F1TDC 
 
|-
 
| CDC            ||  cdc1 - cdc4    || fADC125
 
|-
 
| FDC            ||  fdc1 - fdc14    || fADC125/F1TDC
 
|-
 
| TOF            ||  tof1 - tof2    || fADC250/CAEN TDC
 
|-
 
| FCAL          ||  fcal1 -fcal12  || fADC250
 
|-
 
| DISC          ||  dscr1 -dscr8    || JLab Discriminators
 
|-}
 
 
  
 
== Crate IP Addresses==  
 
== Crate IP Addresses==  
  
{| border="1" cellpadding="2" align="left" valign="top"
+
{| class="wikitable"
!width="200"  | Crate
+
! Crate Name
!width="200"  | IP Address
+
! IP Address
 
|-
 
|-
 
| rocfcal1 || 129.57.135.11  
 
| rocfcal1 || 129.57.135.11  
Line 232: Line 197:
 
|-
 
|-
 
| rocdisc1 || 129.57.135.97
 
| rocdisc1 || 129.57.135.97
|- }
+
|}
 +
 
 +
== Crate Names ==
 +
 
 +
* Each major detector component will have a number of crates named based on its GlueX name, followed by one or two digits specifying the number of the crate.
 +
* If more than one detector component is a part of one crate only one name is assigned, preferably of the larger one or a name that can characterize both detectors, e.g. use "tag<i>x</i>" for TAGM&TAGH crates.
 +
* Numbering assignment with respect to the geographical location (the map) will need to be created out before requesting IP names. The map should define one-to-one corresponds between this detector-based scheme and one based on the geographical location ordering of the crates in the racks and the Hall. 
 +
* The VME crates with the JLab discriminators are separated from the other VXS crates, they are considered as a separate "detector" for the naming purposes.
 +
 
 +
{| border="1" cellpadding="2" align="left" valign="top"
 +
!width="120"  | Detector
 +
!width="150"  | Crate Names
 +
!width="150"  | Possible modules
 +
|-
 +
| TAGM/TAGH      ||  tag1 - tag3    || fADC250/F1TDC
 +
|-
 +
| PS/PSC        ||  ps1  - ps2      || fADC250/F1TDC
 +
|-
 +
| ST            ||  st1  - st2      || fADC250/F1TDC
 +
|-
 +
| TRIG          ||  trig1 - trig2  || GTP/TS/TD
 +
|-
 +
| BCAL          ||  bcal1 - bcal12  || fADC250/F1TDC 
 +
|-
 +
| CDC            ||  cdc1 - cdc4    || fADC125
 +
|-
 +
| FDC            ||  fdc1 - fdc14    || fADC125/F1TDC
 +
|-
 +
| TOF            ||  tof1 - tof2    || fADC250/CAEN TDC
 +
|-
 +
| FCAL          ||  fcal1 -fcal12  || fADC250
 +
|-
 +
| DISC          ||  dscr1 -dscr8    || JLab Discriminators
 +
|}

Revision as of 15:24, 18 March 2014

This page provides the information on conventions on IP name and address on the devices routed off the Hall D main Cisco router.

Hall D Internal Networks

Purpose Network VLAN Number of Addresses Broadcast Address
DAQ 129.57.135.0/24 VLAN 635 256 129.57.135.255
Controls 129.57.26.0/23 VLAN 526 512 129.57.27.255
General 129.57.172.0/22 VLAN 672 1024 129.57.175.255
Development 129.57.194.0/24 VLAN 694 256 129.57.194.255
Infiniband 172.19.5.0/24 Local 256 172.19.5.255


IP Name Conventions

Desktop Computers and Servers

  • Use gluonxx.jlab.org for the online servers main IP addresses. The name comes from GLUex ONline abbreviation. Here xx is a number.
    If we want to keep the same name for Lelvel 3 farm servers, then we will need to use gluonxxx.jlab.org.
  • The additional Ethernet ports will be labeled gluonxx_y.jlab.org for servers with multiple interfaces.
  • We can divide the numbers into ranges for different types of servers, see the table below.
    Note that Level3 is the only one with three digits after "gluon"
  • Use gluonnon-numeric-string.jlab.org for aliases. The character that follows gluon should not be a digit character which would identify this as an alias rather than the main IP address.
Type Name Range
Desktops gluon00 - gluon19
General Purpose Servers gluon20 - gluon39
DAQ EMUs gluon40 - gluon59
Level3 gluon100 - gluon999
Online Aliases gluonnon-numeric-string


Controllers and fan trays for VXS/VME crates

  • Use "rocname" for interface 0 which will be used by the fast DAQ. For instance rocfdc1
  • For the fan trays we can use "vmename". For instance, vmefdc1 .
  • For controls and monitoring we can use interface 1 on the controller called "iocname". For instance, iocfdc1 .

Crate numbering

  • The the fan tray and ROC for any crate will have matching names (e.g. rocfdc1 and vmefdc1 refer to the same crate)
  • The numbering scheme for any detector system will go in order of precedence from North to South then left to right and then from top to bottom. In other words, the first crate in a detector system is the North-most, leftmost, topmost crate for that detector system. The numbers then increase down, then to the right and then to the South. (Left is while facing the front of the crate.)

Embedded devices

  • Continue notation "hallddevice", where device is the name that describes the device type and the number of that device. For instance, hallden2t2.jlab.org or halldbrooks1.jlab.org. Or for High Voltage and Low Voltage devices halldcaen1, halldmpod1, halldcan1. For the main file server we can use halldfs1, and for fast the RAID file servers we can use halldraid1, halldraid2.

Crate IP Addresses

Crate Name IP Address
rocfcal1 129.57.135.11
rocfcal2 129.57.135.12
rocfcal3 129.57.135.13
rocfcal4 129.57.135.14
rocfcal5 129.57.135.15
rocfcal6 129.57.135.16
rocfcal7 129.57.135.17
rocfcal8 129.57.135.18
rocfcal9 129.57.135.19
rocfcal10 129.57.135.20
rocfcal11 129.57.135.21
rocfcal12 129.57.135.22
roccdc1 129.57.135.25
roccdc2 129.57.135.26
roccdc3 129.57.135.27
roccdc4 129.57.135.28
rocbcal1 129.57.135.31
rocbcal2 129.57.135.32
rocbcal3 129.57.135.33
rocbcal4 129.57.135.34
rocbcal5 129.57.135.35
rocbcal6 129.57.135.36
rocbcal7 129.57.135.37
rocbcal8 129.57.135.38
rocbcal9 129.57.135.39
rocbcal10 129.57.135.40
rocbcal11 129.57.135.41
rocbcal12 129.57.135.42
rocbcal13 129.57.135.43
rocbcal14 129.57.135.44
rocbcal15 129.57.135.45
rocbcal16 129.57.135.46
rocfdc1 129.57.135.51
rocfdc2 129.57.135.52
rocfdc3 129.57.135.53
rocfdc4 129.57.135.54
rocfdc5 129.57.135.55
rocfdc6 129.57.135.56
rocfdc7 129.57.135.57
rocfdc8 129.57.135.58
rocfdc9 129.57.135.59
rocfdc10 129.57.135.60
rocfdc11 129.57.135.61
rocfdc12 129.57.135.62
rocfdc13 129.57.135.63
rocfdc14 129.57.135.64
joebesser 129.57.135.65
roctag1 129.57.135.81
roctag2 129.57.135.82
roctag3 129.57.135.83
roctag4 129.57.135.84
roctag5 129.57.135.85
roctof1 129.57.135.87
roctof2 129.57.135.88
roctof3 129.57.135.89
roctrig1 129.57.135.91
roctrig2 129.57.135.92
rocps1 129.57.135.93
rocps2 129.57.135.94
rocst1 129.57.135.95
rocst2 129.57.135.96
rocdisc1 129.57.135.97

Crate Names

  • Each major detector component will have a number of crates named based on its GlueX name, followed by one or two digits specifying the number of the crate.
  • If more than one detector component is a part of one crate only one name is assigned, preferably of the larger one or a name that can characterize both detectors, e.g. use "tagx" for TAGM&TAGH crates.
  • Numbering assignment with respect to the geographical location (the map) will need to be created out before requesting IP names. The map should define one-to-one corresponds between this detector-based scheme and one based on the geographical location ordering of the crates in the racks and the Hall.
  • The VME crates with the JLab discriminators are separated from the other VXS crates, they are considered as a separate "detector" for the naming purposes.
Detector Crate Names Possible modules
TAGM/TAGH tag1 - tag3 fADC250/F1TDC
PS/PSC ps1 - ps2 fADC250/F1TDC
ST st1 - st2 fADC250/F1TDC
TRIG trig1 - trig2 GTP/TS/TD
BCAL bcal1 - bcal12 fADC250/F1TDC
CDC cdc1 - cdc4 fADC125
FDC fdc1 - fdc14 fADC125/F1TDC
TOF tof1 - tof2 fADC250/CAEN TDC
FCAL fcal1 -fcal12 fADC250
DISC dscr1 -dscr8 JLab Discriminators