[Completed] Upcoming Network Maintenance at Monash on 22nd April 2020, 5:30pm to 9:00pm
Posted
over 4 years ago
by Swe Win Aung
Topic is Locked
Swe Win Aung
What
As part of the network maintenance activity to apply performance fixes and security patches at MeRN routers, a scheduled maintenance window has been scheduled for Wednesday 22nd April.
When
Wednesday 22nd April within an overall window of 5:30pm - 9pm
The change number of this activity is CRQ000000118505.
Interruption
The firmware upgrade will be performed on one router at a time. There should be no noticeable interruption due to the resiliency built into the network.
0 Votes
1 Comments
Swe Win Aungposted
over 4 years ago
Monash eResearch network router firmware upgrade has been completed at 7:45pm. There was no disruption at - RDS front end services - Research Cloud Classic provider networks at monash-01, monash-02 and monash-03 - HPC front end servicesDue to BGP was not established while mern-dc1-gw2 was rebooted, there was a short 10-15mins disruption at Research Cloud’s advanced networking layer aka floating IP network.
Due to BGP was not established while mern-dc1-gw2 was rebooted, there was a short 10-15mins disruption at Research Cloud's advanced networking layer.
The disruption was detected at 7:21pm from our external monitoring system and resolved at 7:45pm.
0 Votes
People who like this
Delete Comment
This post will be deleted permanently. Are you sure?
0 Votes
1 Comments
Swe Win Aung posted over 4 years ago
Monash eResearch network router firmware upgrade has been completed at 7:45pm.
There was no disruption at
- RDS front end services
- Research Cloud Classic provider networks at monash-01, monash-02 and monash-03
- HPC front end servicesDue to BGP was not established while mern-dc1-gw2 was rebooted, there was a short 10-15mins disruption at Research Cloud’s advanced networking layer aka floating IP network.
Due to BGP was not established while mern-dc1-gw2 was rebooted, there was a short 10-15mins disruption at Research Cloud's advanced networking layer.
The disruption was detected at 7:21pm from our external monitoring system and resolved at 7:45pm.
0 Votes