The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "WI05 Unresponsive NGI escalation"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{Template:Op menubar}} | |||
{{Template:GO menubar}} | |||
[[Category:Grid Oversight]] | [[Category:Grid Oversight]] | ||
Revision as of 11:20, 1 November 2012
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
| EGI Infrastructure Operations Oversight menu: | Home • | EGI.eu Operations Team • | Regional Operators (ROD) |
In case of not responding NGI, COD should:
- Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from GOC DB - NGIs List or in Dashboard)
- Make a phone call to NGI manager (phone number can be found in GOC DB - look at given NGI's detailes - do not forgot about time zones ;) . If first one was unsuccesful please make a second call.
- Set the ticket assigned to NGI to unsolved and create a new ticket to COO with full report about the situation.