| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
uc:uc20250902_september_2_2025 [2025/09/02 18:43]
nchanove |
uc:uc20250902_september_2_2025 [2025/09/02 18:49] (current)
nchanove |
| There was a recent failure of the main site network's subnet switch, which took out the site phones and 1075 network. This switch handles the common communications network for all site communications, on-site computers, and non-telescope-specific instruments and computers. The switch was replaced and it took about 24 hours to get everything back up and running correctly. It was an old switch so we had no direct spare; it was replaced with another managed switch. These need to be managed switches because they handle communications that pass through some other specific configurations for wifi security and other security protocols. Because it was a managed switch it was not a simple plug-and-play quick swap; the major part of the recovery was to get the network back up and running. Although this was all accomplished by 4 pm the next day, it did unfortunately result in one night of down time. It would be cost prohibitive to reengineer the entire network so there are no plans to overhaul the site network configuration. We are trying to source a replacement for the switch that we used as a spare and will evaluate what other steps we can take to ensure that we are better prepared for this kind of situation if it arises in the future. | There was a recent failure of the main site network's subnet switch, which took out the site phones and 1075 network. This switch handles the common communications network for all site communications, on-site computers, and non-telescope-specific instruments and computers. The switch was replaced and it took about 24 hours to get everything back up and running correctly. It was an old switch so we had no direct spare; it was replaced with another managed switch. These need to be managed switches because they handle communications that pass through some other specific configurations for wifi security and other security protocols. Because it was a managed switch it was not a simple plug-and-play quick swap; the major part of the recovery was to get the network back up and running. Although this was all accomplished by 4 pm the next day, it did unfortunately result in one night of down time. It would be cost prohibitive to reengineer the entire network so there are no plans to overhaul the site network configuration. We are trying to source a replacement for the switch that we used as a spare and will evaluate what other steps we can take to ensure that we are better prepared for this kind of situation if it arises in the future. |
| |
| Regarding the open positions, we are currently conducting remote interviews. After that we hope to schedule a smaller number of on-site interviews prior to making an offer. Also, we welcome Tim McQuaid, a third-year graduate student at NMSU, who will be replacing Mark Croom as the emergency fill-in observing specialist. Tim has already begun his training so you will likely encounter him soon. | Regarding the open positions, the hiring process is moving forward. Also, we welcome Tim McQuaid, a third-year graduate student at NMSU, who will be replacing Mark Croom as the emergency fill-in observing specialist. Tim has already begun his training so you will likely encounter him soon. |
| |
| We continue to have challenges with the camera(s) on the 0.5m. It is possible that the DIS camera can be used once the decommissioning is further along. University of Virginia brought a spare Apogee camera for use on ARCSAT; it is still not known whether that can be used by the broader ARCSAT user community. | We continue to have challenges with the camera(s) on the 0.5m. It is possible that the DIS camera can be used once the decommissioning is further along. University of Virginia brought a spare Apogee camera for use on ARCSAT; it is still not known whether that can be used by the broader ARCSAT user community. |
| |
| New action items from this meeting: | New action items from this meeting: |
| * Nancy: follow up with UWy KOSMOS users to determine severity of dark current issue. | * Nancy: follow up with UWy KOSMOS user to determine severity of dark current issue. |
| * UC reps: remind your users to review the Q3 schedule and request OPEN time in September if they can make a good case for it. | * UC reps: remind your users to review the Q3 schedule and request OPEN time in September if they can make a good case for it. |
| * UC reps: poll your users about a Jan. 2026 splinter session at the AAS for APO science highlights and networking (or other ideas!). | * UC reps: poll your users about a Jan. 2026 splinter session at the AAS for APO science highlights and networking (or other ideas!). |
