Difference between revisions of "WI05 Unresponsive NGI escalation"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
In case of not responding NGI, COD should:<br> | In case of not responding NGI, COD should:<br> | ||
#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC DB - NGIs List] or | #Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC DB - NGIs List] or from Dashboard) | ||
# | #If no answer after 3 working days, 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. | ||
# | #If that doesn't help, set the ticket assigned to NGI to unsolved and create a new ticket to COO with full report about the situation. | ||
<br> | <br> |
Revision as of 17:33, 28 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 from Dashboard)
- If no answer after 3 working days, 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.
- If that doesn't help, set the ticket assigned to NGI to unsolved and create a new ticket to COO with full report about the situation.