Network Response:
The John Day Heli Base is of major concern. Since 5/24 this office’s longest uptime has been 1 week from June 2nd to the 9th. Currently there are no discoverable service tickets for that site If one has not been created, it is highly recommended the customer submit a service ticket so that it can be escalated to Lumen for determining the unstableness of this circuit.
On June 10th, the entire forest went down due to a contractor performing an onsite change out of all switches and routers for the SO. Other than that, all offices had an uptime for 30+ days without issue. Uptime is in relation to pings between a server and the site that verify it is reachable, not necessarily any specific issues with various technologies used within the forest.
The Malheur NF has 6 out of 8 offices that used prior AT&T UTN services migrated to USDA.Net. The remaining two are the SO and Fall MTN Radio.
The SO connects Fall MTN via a point-to-point T1, so Fall MTN will need to be upgraded first in line. Fall Mountain is still awaiting a pending quote for USDA.Net services according to our tracker.
Regarding the complaint of no backup power for the communication infrastructure, it is known that uninterrupted power supplies, backup powers and equals are the responsibility of the local unit. USDA Network Operations may give recommendations, but ultimately the procurement and the installation falls on the local facility. For further guidance and information refer to the Federal Information and Technology Reform Act, OMB M-15-14 memorandum, and the USDAs ‘What is IT’ document.
LMR Response:
All land mobile radio backbone infrastructure (repeaters, base stations, and associated equipment) has been updated to new equipment within the last 2 years.
For ALL USDA/Forest Service IT-related issues/outages:
The most efficient means of obtaining assistance with IT difficulties is by opening a ticket with the Forest Service Customer Help Desk (CHD) at 1-866-945-1354 (TTY: 1-800-877-8339). The user/customer should request a ticket be opened, reporting as specifically as possible WHAT system(s) or capabilities were affected, the date and time WHEN they were impacted, WHERE the impact occurred, and WHO can provide additional information that may be required. Please include the ticket number in ALL correspondence related to the issue/outage, including SAFENET if one is initiated.
|
