The third principle is to facilitate NOC to NOC communication. Know the direct NOC contacts for your customer network operators, your peer network operators and your upstream network operators. And this is not about calling the customer support line. If you have a network down situation, waiting in a queue to speak to customer support who is going to check if things are powered off or powered on or plugged in or otherwise is not what you want. When you have a major network outage make sure that your NOC contact info is part of any service contract. Keep up-to-date information in Route Objects and AS Objects in the Internet Routing Registry and keep up-to-date AS info in the PeeringDB. So our advice: make sure that NOC contact info for all your connected autonomous networks is known to your network operation center staff.

© Produced by Philip Smith and the Network Startup Resource Center, through the University of Oregon.

Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
This is a human-readable summary of (and not a substitute for) the license. Disclaimer. You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. NonCommercial — You may not use the material for commercial purposes. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.