Skip to content
ATIS Best Practices

Search

1098 matching practices

NumberBest Practice
13-10-0404Service Providers, Network Operators, Equipment Suppliers, and Public Safety should incorporate methodologies that continually improve network or equipment performance.
13-10-0407Network Operators and Service Providers should establish processes for NOC-to-NOC (Network Operations Center) peer communications for critical network activities (e.g., scheduled maintenance, upgrades and outages).
13-10-0409Service Providers should use virtual interfaces (i.e. a router loopback address) for routing protocols and network management to maintain connectivity to the network element in the presence of physical interface outages.
13-10-0411Network Operators, Service Providers, and Public Safety should consider developing and implementing cable labeling standards.
13-10-0418Network Operators, Service Providers and Public Safety should should where appropriate, have a documented back-out plan as part of a Method of Procedure (MOP) for scheduled and unscheduled maintenance activities.
13-10-0419Network Operators and Service Providers should design and capacity-manage EMSs (Element Management Systems) and OSSs (Operational Support Systems) to accommodate changes in network element capacity.
13-10-0420Network Operators and Service Providers should periodically measure EMS (Element Management System), NMS (Network Management System) and OSS (Operational Support System) performance using a benchmark or applicable requirements to verify that internal or vendor performance objectives are being met.
13-10-0421Equipment Suppliers should design network elements intended for critical hardware and software with recovery mechanisms to minimize restoration times.
13-10-0424Network Operators and Public Safety should whenever possible require specific applicable safety standards for network elements that they plan to purchase, procure or implement.
13-10-0427Equipment Suppliers should maintain software documentation including revision change history and associated release notes.
13-10-0429Equipment Suppliers should provide for appropriate storage and retrieval mechanisms of system operational data to support analysis after a hardware or software crash.
13-10-0430Equipment Suppliers should be able to recreate supported software from source including, where feasible, software obtained from third parties.
13-10-0431Equipment Suppliers should provide capacity and performance data for network elements.
13-10-0432Equipment Suppliers should support standardized MIBs (Management Information Bases) and maintain documentation of private and enterprise MIBs.
13-10-0435Network Operators, Service Providers, Equipment Suppliers, Property Managers, and Public Safety should assess the functions of their organization and identify those critical to ensure network reliability.
13-10-0436Network Operators, Service Providers, and Public Safety should have a process to ensure smooth handling and clear ownership of problems that transition work shifts or organizational boundaries.
13-10-0437Network Operators and Service Providers should aggregate routes where appropriate (e.g., singly-homed downstream networks) in order to minimize the size of the global routing table taking care to not disrupt engineered circuit diversity.
13-10-0438Network Operators and Service Providers should enable CIDR (Classless Inter-Domain Routing) by implementing classless route prefixes on routing elements.
13-10-0440Network Operators and Service Providers should set and periodically review situation-specific limits on numbers of routes imported from peers and customers in order to lessen the impact of misconfigurations.
13-10-0447Network Operators and Service Providers should consider establishing a customer advocacy function to take part in the development and scheduling of network change activity in order to minimize impact.

Download matching Best Practices

Next results