Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-27124

Support the Summit Activity in Phase 1

    XMLWordPrintable

    Details

    • Story Points:
      3
    • Sprint:
      TSSW Sprint - Oct 12 - Oct 26
    • Team:
      Telescope and Site
    • Urgent?:
      No

      Description

      Support the summit activity of rebooting the M2 and hexapod/rotator servers. The action of M2 server will be at 10/14 (SUMMIT-4314) and the action of hexpod/rotator server will be at 10/15 (SUMMIT-4315).

      This task is in the phase 1.

        Attachments

          Issue Links

            Activity

            Hide
            ttsai Te-Wei Tsai added a comment - - edited

            M2 can be put into the closed-loop already. Franco and Roberto will do the following check. Andrew will focus on the rot/hex/ccw now. He and I created a diagram to show IT the network we need. IT should support this in tomorrow.

            Show
            ttsai Te-Wei Tsai added a comment - - edited M2 can be put into the closed-loop already. Franco and Roberto will do the following check. Andrew will focus on the rot/hex/ccw now. He and I created a diagram to show IT the network we need. IT should support this in tomorrow.
            Hide
            ttsai Te-Wei Tsai added a comment - - edited

            The ThinkPad and hex/rot server can ping each other already. Andrew powered on the rotator PXI controller by netbooter and I could ping the rotator PXI controller from the management PC. Based on the Andrew's feedback, it looks like there is the problem of tcp/ip connection of port 5580 (5581 looks good). The 5580 is the telemetry and 5581 is the command.

            Show
            ttsai Te-Wei Tsai added a comment - - edited The ThinkPad and hex/rot server can ping  each other already. Andrew powered on the rotator PXI controller by netbooter and I could ping  the rotator PXI controller from the management PC. Based on the Andrew's feedback, it looks like there is the problem of tcp/ip connection of port 5580 (5581 looks good). The 5580 is the telemetry and 5581 is the command.
            Hide
            ttsai Te-Wei Tsai added a comment - - edited

            Summary of today's test:

            1. We cleaned the tigervnc temporary files (X5 - X9) and made sure 5 vncserver services are runnung in the management PC.

            2. We made sure only the rotator 2 and camera hexapod can be powered on. The M2 hexapod controller is in the base office.

            3. We used the netstat in the management PC to make sure the connections of 5580 (tmosms0), 5581 (tmosms1), 5590, and 5591 are established.

            4. We made sure they are the same in the controller.

            5. We used the tcpdump command in the management PC to make sure we had the packet from controller (5580 and 5590 are the telemetry ports from the low-level controler to the management PC).

            6. If we use the ThinkPad rotator/hexapod GUI, we have the error from telemetry ports.

            Show
            ttsai Te-Wei Tsai added a comment - - edited Summary of today's test: 1. We cleaned the tigervnc temporary files (X5 - X9) and made sure 5 vncserver services are runnung in the management PC. 2. We made sure only the rotator 2 and camera hexapod can be powered on. The M2 hexapod controller is in the base office. 3. We used the netstat in the management PC to make sure the connections of 5580 (tmosms0), 5581 (tmosms1), 5590, and 5591 are established. 4. We made sure they are the same in the controller. 5. We used the tcpdump command in the management PC to make sure we had the packet from controller (5580 and 5590 are the telemetry ports from the low-level controler to the management PC). 6. If we use the ThinkPad rotator/hexapod GUI, we have the error from telemetry ports.
            Hide
            ttsai Te-Wei Tsai added a comment -

            Please help to review this ticket. Thanks!

            Show
            ttsai Te-Wei Tsai added a comment - Please help to review this ticket. Thanks!
            Hide
            aheyer Andrew Heyer [X] (Inactive) added a comment -

            Te-Wei and I did work on the network over this past week. We made good progress, still have a few issues to resolve. I will be creating a ticket for this soon. 

            Show
            aheyer Andrew Heyer [X] (Inactive) added a comment - Te-Wei and I did work on the network over this past week. We made good progress, still have a few issues to resolve. I will be creating a ticket for this soon. 

              People

              Assignee:
              ttsai Te-Wei Tsai
              Reporter:
              ttsai Te-Wei Tsai
              Reviewers:
              Andrew Heyer [X] (Inactive)
              Watchers:
              Andrew Heyer [X] (Inactive), Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Start date:
                End date:

                  Jenkins Builds

                  No builds found.