https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-464 Instrument control development <p>This is a ticket to note the problem. Fixing ics_dnsmasq is easy, but we need to check the network topology to see what other effects this might have. Do we just add an alias on the FPS machine? Does the FPGA have a dedicated line or does it go through a switch at the PFI? <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono" class="user-hover" rel="atsushi.shimono">shimono</a>, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kyono" class="user-hover" rel="kyono">kyono</a>?</p> <p>Or do we want to recompile with a different address?</p> <p>128.149.77.1 is fixed as the gateway, btw.</p> INSTRM-464

PFI FPGA uses non-PFS fixed address of 128.149.77.24 (/24)

Task Minor Done Done Unassigned cloomis EngRun FPS PFI Thu, 30 Aug 2018 11:52:20 +0000 Thu, 14 Oct 2021 17:40:09 +0000 Mon, 9 Aug 2021 15:27:46 +0000 0 1 <p>According to Xilinx, the LWIP stack uses DHCP by default. But the FPGA code does set a static address. Odd.</p> <p>network to PFI is shared by all, so better to recompile.<br/> (not sure whether we can use vlan for PFI network switch)</p> <p>Ugh.</p> <p>But it (the controller board) is just Kintex-7 built with Vivado, so probably straightforward. The driver boards are a little more exotic, but we don't need to touch those. </p> <p>I just talked with Kiaina, and we think this will not be a problem. The switch connecting to the PFI FPGA is in fact a PFS switch. So we can simply add an IP alias on the host running <tt>ics_fpsActor</tt> (and thus the <tt>ics_cobraCharmer</tt> code). <tt>128.149.77.1</tt> or <tt>128.149.77.2</tt> would be fine. The point being that no other host would see the traffic. Note, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a></p> <p>I'll leave this Open but lower the priority just so this does not disappear.</p> <p>Well, it is wanted, if only to keep the switch/router interface configuration simple. Will add as 133.40.164.101, which is in the "PFI" section of the SSN-28 allocation. I.e. it will be fixed IP address, and not allocated by DHCP. With ASRD being unreachable, debugging that change could become difficult.</p> <p>Merged and tagged 3.0.0 with that address, and so installable at ASRD. But after chatting a bit more, we realize that we might need to be more clever at Subaru and need to talk with <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiaina" class="user-hover" rel="kiaina">Kiaina Schubert</a> about topology.</p> <p>The FPGA is plugged into the PEB Ethernet switch, so is on the same network segment as several other PFS devices: the 133.40.164.110 address in the new formware is good.</p> Development Rank 0|zzs8vb:r Sprint EngRun03