127:
330:
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:
25:
66:
401:
types of entities. It expresses key aspects of their availability at any given time. The purpose of the state model is to indicate the availability of an entity in providing its functions and, if an entity is not available, to indicate the cause of the unavailability and what kind of activity may be taken by the manager (e.g., the OS or the craft) to make the entity available.
412:
To help ensure interoperability, particularly for an OS that interfaces with multiple NEs using one of the two state models, a mapping between the models may be needed. GR-1093 provides a mapping for the two models and also defines the extension to the OSI state/status attributes that is necessary to
400:
Different types of entities (such as hardware, transport facilities, and subscriber service) have a variety of state characteristics that express the availability of their underlying resources that are specific to each entity type. However, a state model is expected to be common to a large number of
396:
The state of an entity represents the current condition of availability of the underlying resource or service in the NE from the point of view of management. In the context of the
Telcordia State Model, the term "entity" represents an entry in a TL1 administrative view (i.e., represents the resource
388:
A network element state model facilitates cross domain network management and promotes a multi-vendor environment. The standard definitions and mappings allow
Operations Systems to gather state information from NEs and integrate it into a consistent representation of the status of the entire managed
329:
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
360:
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
392:
Telcordia GR-1093 discusses the two primary state models in industry. One is the
Telcordia State Model, which consolidates the state models previously described in several Telcordia documents. By consolidating the models, changes and expansions to the models can be presented and can evolve in a
260:
refers to a facility or to equipment used in the provision of a telecommunications service. This term also refers to features, functions, and capabilities that are provided by means of such facility or equipment. This includes items such as subscriber numbers, databases, signaling systems, and
269:
With development of distributed networks, network management had become an annoyance for administration staff. It was hard to manage each device separately even if they were of the same vendor. Configuration overhead as well as misconfiguration possibility were quite high. A
404:
In a specific application, only a subset of the state model may be needed. The rationale of such restrictions is not described in GR-1093. The technology or application-specific requirements document should be consulted for this information.
408:
The standard definitions and mappings allow
Operations Systems to gather state information from NEs and integrate it into a consistent representation of the status of the entire managed network and each of the services that it supports.
393:
coordinated fashion. Also, inconsistencies and redundancy may be averted. The other model is the
International Organization for Standardization (ISO) State Model, which is defined in ITU-T Recommendation X.731.
274:
for a basic service required complex configurations of numerous devices. It was also hard to store all network devices and connections in a plain list. Network structuring approach was a natural solution.
283:
With structuring and grouping, it is very well seen that in any distributed network there are devices performing one complex function. At that, those devices can be placed in different location. A
339:
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.
261:
information that is sufficient for billing and collection. Alternatively, it's also included if it's used in the transmission, routing, or other provision of a telecommunications service.
287:
is the most typical example of such a distributed group of devices. It typically contains subscriber line units, line trunk units, switching matrix, CPU and remote hubs. A basic
249:
is a manageable logical entity uniting one or more physical devices. This allows distributed devices to be managed in a unified way using one management system.
397:
or service generally identified by the Access
Identifier parameter). In the context of the ISO State Model, the term "entity" means "managed object".
336:
Trouble
Detection – Detect trouble by continuous monitoring, periodic tests, per-call or other pre-action tests, or other automatic processes.
306:. For enterprise solutions, it is common to locate cluster nodes in different locations, even in different regions (settlements).
478:
191:
463:
428:
422:
377:
163:
348:
Trouble
Isolation – Isolate the trouble to its source, preferably to a single field-repairable element, e.g., circuit pack.
170:
354:
Repair Verification and Return to Service – Verify that the trouble has been fixed and return the element to service.
271:
228:
210:
108:
52:
144:
90:
38:
177:
253:
148:
159:
510:
444:
432:
81:
342:
Service Recovery – Minimize the degradation of service by automatic or manual protection actions.
288:
137:
184:
44:
8:
292:
284:
76:
299:
242:
504:
345:
Trouble Verification – Determine whether the reported condition still exists.
320:
Information related to the quality or health of the transmission signal, and
427:
A concept of the network element as a distributed entity is widely used in
365:
291:
leans on all those units, so it is convenient for an engineer to manage a
369:
323:
Information related todata its own internal hardware/software integrity.
303:
314:
In general, an NE can generate two types of maintenance information:
492:
373:
126:
364:
GR-474 complements recent criteria in industry standards such as
413:
meet the telecommunications needs of the service providers.
466:
Network Maintenance: Alarm and Control for Network Elements
295:
as one complex entity encompassing all those units inside.
302:. A cluster can occupy a lot of space and may not fit one
416:
481:
Generic State Requirements for Network Elements (NEs),
431:which in turn is used as a standard for developing
389:network and each of the services that it supports.
151:. Unsourced material may be challenged and removed.
86:
improve grammar, wikification, need more citations.
16:Manageable logical entity uniting physical devices
502:
298:Another good example of a network element is a
351:Repair – Fix or replace the faulty element.
53:Learn how and when to remove these messages
229:Learn how and when to remove this message
211:Learn how and when to remove this message
109:Learn how and when to remove this message
503:
423:Telecommunications Management Network
417:Telecommunications Management Network
149:adding citations to reliable sources
120:
59:
18:
13:
14:
522:
34:This article has multiple issues.
361:alarm surveillance and control.
125:
64:
23:
383:
136:needs additional citations for
42:or discuss these issues on the
486:
472:
457:
309:
254:Telecommunications Act of 1996
1:
450:
264:
7:
438:
366:ITU-T Recommendation M.3100
278:
84:. The specific problem is:
10:
527:
493:ITU-T Recommendation X.731
433:element management systems
420:
445:Unbundled network element
272:provisioning process
145:improve this article
91:improve this article
80:to meet Knowledge's
511:Network management
293:telephone exchange
285:telephone exchange
289:telephone service
258:'network element'
252:According to the
243:computer networks
239:
238:
231:
221:
220:
213:
195:
160:"Network element"
119:
118:
111:
82:quality standards
73:This article may
57:
518:
495:
490:
484:
476:
470:
461:
300:computer cluster
234:
227:
216:
209:
205:
202:
196:
194:
153:
129:
121:
114:
107:
103:
100:
94:
68:
67:
60:
49:
27:
26:
19:
526:
525:
521:
520:
519:
517:
516:
515:
501:
500:
499:
498:
491:
487:
477:
473:
462:
458:
453:
441:
425:
419:
386:
312:
281:
267:
247:network element
235:
224:
223:
222:
217:
206:
200:
197:
154:
152:
142:
130:
115:
104:
98:
95:
88:
69:
65:
28:
24:
17:
12:
11:
5:
524:
514:
513:
497:
496:
485:
471:
455:
454:
452:
449:
448:
447:
440:
437:
421:Main article:
418:
415:
385:
382:
358:
357:
356:
355:
352:
349:
346:
343:
340:
337:
327:
326:
325:
324:
321:
311:
308:
280:
277:
266:
263:
237:
236:
219:
218:
133:
131:
124:
117:
116:
72:
70:
63:
58:
32:
31:
29:
22:
15:
9:
6:
4:
3:
2:
523:
512:
509:
508:
506:
494:
489:
483:
482:
475:
468:
467:
460:
456:
446:
443:
442:
436:
434:
430:
424:
414:
410:
406:
402:
398:
394:
390:
381:
379:
375:
371:
367:
362:
353:
350:
347:
344:
341:
338:
335:
334:
333:
332:
331:
322:
319:
318:
317:
316:
315:
307:
305:
301:
296:
294:
290:
286:
276:
273:
262:
259:
255:
250:
248:
244:
233:
230:
215:
212:
204:
193:
190:
186:
183:
179:
176:
172:
169:
165:
162: –
161:
157:
156:Find sources:
150:
146:
140:
139:
134:This article
132:
128:
123:
122:
113:
110:
102:
92:
87:
83:
79:
78:
71:
62:
61:
56:
54:
47:
46:
41:
40:
35:
30:
21:
20:
488:
480:
474:
465:
459:
426:
411:
407:
403:
399:
395:
391:
387:
384:State models
363:
359:
328:
313:
297:
282:
268:
257:
251:
246:
240:
225:
207:
198:
188:
181:
174:
167:
155:
143:Please help
138:verification
135:
105:
96:
89:Please help
85:
74:
50:
43:
37:
36:Please help
33:
310:Maintenance
256:, the term
99:August 2020
93:if you can.
451:References
304:datacenter
265:Background
201:April 2023
171:newspapers
39:improve it
479:GR-1093,
469:, Issue 2
429:TMN model
45:talk page
505:Category
464:GR-474,
439:See also
279:Examples
75:require
378:ANSI T1
185:scholar
77:cleanup
376:, and
372:, and
187:
180:
173:
166:
158:
374:G.709
370:G.707
192:JSTOR
178:books
245:, a
164:news
241:In
147:by
507::
435:.
380:.
368:,
48:.
232:)
226:(
214:)
208:(
203:)
199:(
189:·
182:·
175:·
168:·
141:.
112:)
106:(
101:)
97:(
55:)
51:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
