<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Not my intention to spam everyone, but I thought this might be of wide enough interest for the group.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
If the preferred method going forward is to refer to networked devices by host name rather than IP address in software, maybe we should consider some CED changes? As far as I can tell, the only type in CED that has a 'HostName' property is VMECrate, whereas
a lot have IPAddress (only three roots though: NetElem, RacksAndCrates, Meter).<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Should we replace IPAddress with HostName? Or maybe just rename it - IPAddress is a string, although it's domain is a regex that expects something that looks like an IP address - that would have to be relaxed. That would break some things, but it would just
be a case of replacing the property name. Presumably whatever the address itself is being used for would still work until the value is actually replaced with a host name.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Any other ideas or thoughts?<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size: 11pt; color: rgb(0, 0, 0);" face="Calibri, sans-serif"><b>From:</b> Brad Cumbia <cumbia@jlab.org><br>
<b>Sent:</b> Thursday, May 18, 2023 2:07 PM<br>
<b>To:</b> Gary Croke <gcroke@jlab.org><br>
<b>Cc:</b> Anthony Cuffe <cuffe@jlab.org><br>
<b>Subject:</b> Re: Soft ioc startup scripts</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Gary<br>
The following have been updated to use DHCP, default services configuration applied, and rebooted. You may want to restart your soft ioc again.<br>
<br>
bsydigips1<br>
nadigips1<br>
nl07digips1<br>
nl27digips1<br>
sl07digips1<br>
sl27digips1<br>
w2digimagtmp<br>
wa1digips1<br>
<br>
______________<br>
Brad Cumbia<br>
<br>
Network Engineer<br>
Accelerator Computing Group (ACG)<br>
Accelerator Computing Enviroment (ACE)<br>
<br>
Thomas Jefferson National Accelerator Facility<br>
12000 Jefferson Avenue<br>
Newport News, Virginia 23606<br>
Phone (757)269-5839<br>
<br>
________________________________________<br>
From: Gary Croke <gcroke@jlab.org><br>
Sent: Thursday, May 18, 2023 12:33 PM<br>
To: Brad Cumbia<br>
Cc: Anthony Cuffe<br>
Subject: Re: Soft ioc startup scripts<br>
<br>
iocsoftmag rebooted and connected to w2digimagtmp without issue.<br>
<br>
________________________________<br>
From: Gary Croke <gcroke@jlab.org><br>
Sent: Wednesday, May 17, 2023 12:21 PM<br>
To: Anthony Cuffe <cuffe@jlab.org><br>
Cc: Brad Cumbia <cumbia@jlab.org><br>
Subject: Re: Soft ioc startup scripts<br>
<br>
Actually, the third one (power meters) doesn't involve port servers, sorry, you can ignore that.<br>
________________________________<br>
From: Gary Croke<br>
Sent: Wednesday, May 17, 2023 12:20 PM<br>
To: Anthony Cuffe <cuffe@jlab.org>; Brad Cumbia <cumbia@jlab.org><br>
Cc: acs@jlab.org <acs@jlab.org><br>
Subject: Soft ioc startup scripts<br>
<br>
Anthony,<br>
<br>
Here are a few examples of soft iocs connecting to port servers:<br>
<br>
/cs/op/iocs/iocsoftagileturbo/startup.ipconfig<br>
/cs/op/iocs/iocsoftinj3/port_setup.cmd<br>
/cs/op/iocs/iocsoftfac/powerMetersV/stcmd/startup.shark50b.ipconfig<br>
/cs/op/iocs/iocsoftw3spce/startup.iocsoftw3spceApps.munch<br>
<br>
One of the slight complications is that there isn't a standard location or naming convention for the files that make the connections. I think mostly they are in local (not linked) files in the ioc boot directory. startup.ipconfig is a common file name. Sometimes
they are in the linked application startup files. Maybe we should try agree on a more standard approach going forward.<br>
<br>
Gary<br>
</div>
</span></font></div>
</body>
</html>