Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Network element
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Maintenance== In general, an NE can generate two types of maintenance information: :#Information related to the quality or health of the transmission signal, and :#Information related todata its own internal hardware/software integrity. The functional components of surveillance are performance monitoring and alarm/status monitoring, also known as alarm surveillance. In the national and international standards area for telecommunications operations, performance monitoring and alarm surveillance are classified as subcategories of the more general system management functional categories of performance management and fault management, respectively. Maintenance consists of both preventive and corrective procedures that are designed to (a) prevent troubles and identify potential troubles before they affect service, and (b) detect a network failure that impacts performance and make the appropriate repairs. A typical seven-step maintenance process consists of: :#Trouble Detection β Detect trouble by continuous monitoring, periodic tests, per-call or other pre-action tests, or other automatic processes. :#Trouble Notification β Send notification of a specific event or condition to a local display or Operations System (OS). Trouble notifications include output messages and visual and audible alarms. :#Service Recovery β Minimize the degradation of service by automatic or manual protection actions. :#Trouble Verification β Determine whether the reported condition still exists. :#Trouble Isolation β Isolate the trouble to its source, preferably to a single field-repairable element, e.g., circuit pack. :#Repair β Fix or replace the faulty element. :#Repair Verification and Return to Service β Verify that the trouble has been fixed and return the element to service. Telcordia GR-474 establishes trouble-detecting and reporting criteria for signal transmission failures and internal hardware or software anomalies. GR-474 provides proposed generic requirements that pertain to the Fault and Performance Management functions in transport and switching NEs used for alarm surveillance and control.<ref>[http://telecom-info.telcordia.com/site-cgi/ido/docs.cgi?ID=SEARCH&DOCUMENT=GR-474& GR-474, ''Network Maintenance: Alarm and Control for Network Elements''], Issue 2</ref> GR-474 complements recent criteria in industry standards such as [http://www.itu.int/rec/T-REC-M.3100/en/ ITU-T Recommendation M.3100], [http://www.itu.int/rec/T-REC-G.707/en/ G.707], and [http://www.itu.int/rec/T-REC-G.709 G.709], and [[American National Standards Institute | ANSI T1]].
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)