基于脚本操作的网络管理系统SPLICE/NM设计与实现

需积分: 8 155 浏览量更新于2024-08-07 收藏 195KB PDF 举报

本文档探讨了"Design and Implementation of Network Management System SPLICE/NM Based on Scripted Operations"，由Kiyohiko Okayama和Suguru Yamaguchi（来自日本奈良科学技術大學信息科學研究生院，Ikoma）以及Hideo Miyahara（大阪大学工程科学学院，Toyonaka）合作完成。该研究的背景是随着互联网服务的可靠性和需求的增长，传统的网络管理方式在面临快速变化的网络环境和技术复杂性提升时，其问题检测与恢复服务显得效率不高且准确性不足，这给网络管理者带来了沉重的压力。 SPLICE/NM系统的设计目标是通过自动化来增强网络管理人员的工作效率。它的核心理念是让管理员能够利用编程语言来编写操作脚本，描述他们在终端上执行的任务。这些脚本记录了管理员的意图，然后系统通过自动化执行，实现了对网络设备的管理和维护工作。这种方法旨在简化繁琐的手动操作流程，提高响应速度和问题解决的准确性，从而减轻网络管理员的工作负担。具体而言，系统设计的关键在于将网络管理过程转化为可编程的形式，使得管理人员无需直接干预硬件层面，而是通过编写易于理解的代码来指示系统如何处理网络故障或进行必要的配置更改。通过这种方式，即使遇到复杂的网络问题，SPLICE/NM也能通过预定义的恢复策略自动执行解决方案，减少人工介入的时间和出错可能性。此外，文章可能还涵盖了SPLICE/NM系统的架构、技术细节、实现方法，包括如何集成到现有的网络管理环境中，以及它如何通过安全性和易用性方面的改进，提升整个网络管理系统的效能。可能还讨论了测试和评估的结果，证明了SPLICE/NM在实际应用中的性能优势，以及与其他同类网络管理系统的比较分析。这篇论文为网络管理领域提供了一种创新的方法论，通过引入基于脚本的操作，简化了网络维护流程，提升了问题解决的效率和准确性，具有重要的理论价值和实践意义，对于优化网络运营和维护具有显著的推动作用。

control reflecting policies of all participating organizations,

distribution of servers with consideration of network

scalability, and so on.

In the current study, after defining the faults handled

by SPLICE/NM, the authors will discuss the issues of

cooperative management between the distributed servers,

and then make evaluations and identify problems regarding

a real prototype based on the SPLICE/NM design.

2. Fault Definition in SPLICE/NM

Network management covers a wide field, from the

network equipment structure to user account generation and

billing. Considering various existing technologies and ap-

proaches, it is not feasible to discuss network management

as a whole.

Therefore, in OSI the entire network management is

subdivided into five classes: structure management, per-

formance management, fault management, security

management, and account management. SPLICE/NM

concentrates on the fault management and is intended for

automation of fault recovery tasks as they are convention-

ally performed by managers, but since there are all kinds of

faults that can occur on the network, they are perceived

differently by different people.

For example, although network performance deterio-

ration might be considered a fault, it could be difficult to

subdivide network deterioration cases into those regarded

as a temporary condition and those that at a certain stage

can be viewed as a fault. Solving this problem would require

technology for performance management such as that for

monitoring network traffic on a permanent basis. In addi-

tion, in a large-scale network such as the Internet, for

various reasons, such as the presence of communication bot-

tleneck sections outside of the current organization, prob-

lems cannot be solved without spending time and money.

Therefore, in SPLICE/NM, we have limited the fault

types and concentrated on network connectivity. In other

words, we consider a fault as a condition when it is impos-

sible to reach a specific host or network, or a condition when

a specific service cannot be used.

In addition, the network equipment targeted by

SPLICE/NM is a gateway functioning as a connecting point

between networks, or a server offering network services.

The term management object will refer to such types of

equipment.

3. Fault Management Model in

SPLICE/NM

Fault management in a network discussed in the time

flow aspect can be broken down into the following phases:

1. Fault discovery

2. Fault diagnosis (identification of cause and devel-

opment of countermeasures)

3. Recovery operations

4. Recording of operations results

In a conventional accident management system, each

phase is managed by a manager or a user using this network.

Among these, the fault discovery phase has long been a

target of attempts at automation, with the resulting network

monitoring system using SNMP. In addition, there is the

trouble ticket system, which involves creating a cooperative

operation environment between multiple managers. This

system can be used for recording the recovery operations

results.

The SPLICE/NM system proposed in the current

study concentrates on the phases of fault diagnosis and

recovery operations, aiming at automating the operations

required at these phases. Figure 1 illustrates a fault manage-

ment model for the case of a SPLICE/NM system combined

with a network monitoring system and a trouble ticket

system.

In the fault management model shown in Fig. 1, the

management object is usually monitored by the network

monitoring system. If a fault occurs in a management

object, then it is detected by the network monitoring system

and reported to SPLICE/NM. SPLICE/NM performs diag-

nostics of the fault in the indicated management object, and

conducts recovery operations, with the results reported to

the trouble ticket system. During this process, if it is impos-

sible to fully recover from the fault, the trouble ticket

system contacts the manager, and the recovery operations

are delegated to the manager. Finally, on recovering from

the fault, the operations results are recorded by the manager.

For implementing the fault management model using

SPLICE/NM, it is important to know how the information

Fig. 1. Management model of SPLICE/NM.

剩余10页未读，继续阅读

weixin_38621082

粉丝: 9
资源: 948

基于脚本操作的网络管理系统SPLICE/NM设计与实现

基于脚本化操作的网管系统SPLICE/NM的设计与实现

splice性能测试

To optimize splice joint between different PCF-based devices and SMF transmission medium

自动化脚本驱动的网络管理系统SPLICE/NM设计与高效恢复

自动化脚本驱动的网络管理系统SPLICE/NM：高效运维解决方案

splice

//处理 ¥ 符号 function handleRMBStr(str){ var arr=str.split('') console.log(arr); // arr.splice() // return Str } module.exports={ handleRMBStr:handleRMBStr }帮我解决上述代码的问题

Cannot read properties of undefined (reading 'splice')

TypeError: Cannot read properties of undefined (reading 'splice')

ypeError: Cannot read properties of undefined (reading 'splice')

最新资源