At 8:00 PM this evening, we will attempt to complete the PROD environment for the ADOA AWS Oregon Path using Palo Alto Next Generation Firewalls.
The next post will occur at 8:00 PM to signify the start of this change event.
At 8:00 PM this evening, we will attempt to complete the PROD environment for the ADOA AWS Oregon Path using Palo Alto Next Generation Firewalls.
The next post will occur at 8:00 PM to signify the start of this change event.
At 9:30 PM, the Roll-Back of the change event for the Palo Alto Next Generation Firewalls within the AWS transit path was completed successfully.
All testers on the Testers Bridge Line report renewed connectivity to all servers.
The Security Team is now working with the vendor to determine the root cause of the routing issues that caused the lack of connectivity.
Tomorrow, a determination will be made as to whether we will re-attempt this change event for NON-PROD on Thursday, April 25th, or whether we will reschedule the entire change event (for both NON-PROD and PROD) at an entirely different time.
Testers will be provided with the scheduling information as soon as a decision has been reached.
THIS WILL BE THE FINAL POSTING FOR THIS CHANGE EVENT
It is 9:10 PM, and we have experienced a number of connectivity issues which have forced us to roll back the event.
We have our testers waiting on the Testers Bridge Line for the GO to commence testing once the roll back procedures have completed, in about 15 more minutes.
The next update will be posted at 9:30 PM.
At 9:00 PM, the Security Team is working with the vendor to determine the root cause of a routing issue that is causing serveral IP addresses to be unreachable at the present time.
We will continue to try to fix connectivity issues within our change window.
The next update will be posted at 9:30 PM.
Good evening.
The time is now 8:30 PM on Tuesday, April 23, 2019.
Route tables were completed 5 minutes early, with no issues.
At this time, all testers have been given the GO to begin testing.
Next update will be posted at 9:00 PM.
The time is now 8:00 PM.
This update is to confirm the start of our change event. Our change window will last until 10:00 PM.
The next AZCOOP update will be posted at 8:30 PM.
As of 8:00 PM this evening, Tuesday, April 23, 2019, we will be implementing the first of two (2) Palo Alto VM-300 Next Generation Firewalls into the AWS transit path.
This evening, we will implementing NON-PROD, while PROD will be implemented on Thursday evening, April 25, 2019, with the same change window as tonight's implementation.
The Testers Bridge Line number is 1-716-427-6516 with PIN number 406 818#. This bridge will be activated as of 7:45 PM this evening, but testers should be on this line by no later than 8:15 PM in order to listen for the GO order to begin implementing test plans previously submitted.
This AZCOOP update will be refreshed every half hour during our 8:00 PM to 10:00 PM change window.
Next update will appear at 8:00 PM to notify all of the beginning of this evening's implementation.
Today on April 1st, we started receiving reports of issues accessing the ETE menu for state employees. We have notified the appropriate groups and are looking to provide a resolution as soon as possible.
We are tracking this through ticket Cherwell 136751.
Starting around 9:30 AM, users started reporting issues with Finesse and not being able to sign in or being logged out.
We have informed the appropriate groups and are looking to provide a solution as soon as possible.
Ticket 204815
Update 10:30 AM:
Users appear to be able to login. Still no official resolution on the issue from the vendor yet.
Starting at 7:00am we started receiving reports of general network issues. We have notified the appropriate group and are working to provide a resolution as soon as possible.
We are tracking this issue through Remedy ticket 202894, Cherwell ticket 119211.
---
Update: We have restored services and will continue monitoring the issues.
General phone issues are affecting multiple agencies. AZNET is currently looking into provide a resolution as soon as possible.
The issue is being tracked with AZNET ticket number 202112.
We are currently unable to receive calls on 602-364-4444(Service Desk) or 602-542-4700(HRIS). We have informed AZNET and are currently looking to provide a resolution as soon as possible.
The issue is being tracked with AZNET ticket number 200092.
UPDATE (3:30 PM) - AZNet II has moved the internet traffic to other internet circuits to restore internet service.
UPDATE - CenturyLink is currently experiencing a nationwide network intermittent outage. The issue has been escalated to the Leadership team and are working to restore services as quickly as possible.
You can also get real time updates by calling into our AZNet II Customer Bridge below:
Toll number 240 454 0879
Meeting number 809 485 928
AZNet Remedy number: 200092
Today December 27th at around 1:15 PM we started receiving reports of network connectivity issues affecting multiple agencies. We have notified the appropriate groups and are looking to provide a solution as soon as possible. We apologize for the inconvenience.
We are tracking the issue through Remedy ticket 200092
At 6:30 AM we started receiving reports that DHS users are experiencing general network issues.
The appropriate groups have been informed and we are looking to provide a resolution as soon as possible.
This can be tracked through Cherwell Ticket 101024.
[Update]
This has been resolved. Users should be able to use the network as expected.
Good morning,
The ADOA-ASET Firewall Migration from the State Data Center at 1510 West Adams Street, in addition to a Layer 3 change performed by AZNet immediately after the Layer 2 Firewall Migration change, were both completed succesfully this morning by 2:42 AM.
This will be the final notification regarding this change.
Thank you, and have a pleasant Sunday.
Good morning,
This morning, starting at 1:00 AM, we will commence with the second attempt at a Next Generation Firewall Migration.
The IBM Operations Team is being contacted to confirm the quiescing of the Mainframe.
We will provide additional updates through the morning until this activity is completed.
Thanks,
Ken Roundtree
Good morning,
As reported previously, a routing issue experienced with one of the new Palo Alto firewalls at the Iron Mountain Data Center caused a NO GO decision to be received, and a successful implementation of the Roll Back Plan for this effort was done.
The Firewall Migration will be rescheduled after the root cause of the above mentioned issue has been determined and resolved.
As of 5:35 AM, the November IPL of the mainframe was completed successfully.
The Technical and Tester Bridge lines have both been terminated at this time.
This will be the final notification for this event.
Good moring,
Due to an OSPF routing issue experienced on one of our new Palo Alto firewalls, we received a NO GO decision on moving forward with the Firewall Migration event, and have successfully rolled back to our old firewalls at the State Data Center.
In the meantime, the IBM Operations team is continuing to move forward with the monthly IPL of the mainframe for November.
The next update will be published at 6:00 AM.