WO2016078302A1 - 一种故障数据获取系统和远程设备控制系统及其对应方法 - Google Patents

一种故障数据获取系统和远程设备控制系统及其对应方法 Download PDF

Info

Publication number
WO2016078302A1
WO2016078302A1 PCT/CN2015/076573 CN2015076573W WO2016078302A1 WO 2016078302 A1 WO2016078302 A1 WO 2016078302A1 CN 2015076573 W CN2015076573 W CN 2015076573W WO 2016078302 A1 WO2016078302 A1 WO 2016078302A1
Authority
WO
WIPO (PCT)
Prior art keywords
board
remote device
fault data
mch
management center
Prior art date
Application number
PCT/CN2015/076573
Other languages
English (en)
French (fr)
Inventor
苗滋润
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016078302A1 publication Critical patent/WO2016078302A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34Signalling channels for network management communication

Definitions

  • the present invention relates to the field of communications, and in particular, to a fault data acquisition system, a remote device control system, and a corresponding method thereof.
  • Micro TCA Micro Telecommunication Computing Architecture
  • ATCA Advanced Telecom Computing Architecture
  • the purpose is to solve the problem that devices in the communication field cannot be compatible with each other, resulting in the inability to industrialize component manufacturing, long manufacturing cycle, and high maintenance cost. It regulates the interface between the components and elements of the device, improves the compatibility between the devices, and stipulates the reliability and performance of the device, providing a unified platform for system integration and business development.
  • the architecture thereof is as shown in FIG. 1.
  • the remote device 12 based on the uTCA architecture and the network management center 11 are connected through the first network interface 101 and the second network interface 102. And performing data transmission, the data transmission is based on the IP protocol transmission. Therefore, the channel for transmitting data between the remote device 12 and the network management center 11 is called an IP channel, and the link between the two can use the Ethernet.
  • the network twisted pair link is connected to the fiber when the distance is long; the network management center 11 can conveniently use the network cable or fiber based on the IP protocol to log in to the control board of the remote device 12 (MCH, MicroTCA Carrier Hub) On the board 103) or on the remote device based on the uTCA architecture, the IP connection channel between the MCH board 103 and the Advanced Mezzanine Card (AMC) (the third network interface 104 and the fourth network interface 105) the connection between The channel is logged onto the AMC board 106 for fault location.
  • MCH MicroTCA Carrier Hub
  • embodiments of the present invention are expected to provide a fault data acquisition system and a remote device control system and corresponding methods thereof.
  • An embodiment of the present invention provides a fault data acquiring system, where the system includes: a network management center and a remote device;
  • the network management center is configured to receive fault data sent by the remote device
  • the remote device is configured to report device fault data to the network management center through an internal intelligent platform management bus IPMB channel and an internetwork protocol IP channel between the remote device and the network management center, where the remote device and the network management center
  • An inter-IP channel refers to a channel between a second network interface in the remote device and a first network interface in the network management center.
  • the remote device includes: a bearer hub MCH board and an advanced mezzanine card AMC board;
  • the MCH board is configured to send device fault data to the network management center, where the device fault data is from the AMC board;
  • the AMC board is configured to obtain device fault data and send the data to the MCH board through the IPMB channel between the AMC board and the MCH board.
  • the MCH board includes: a first IPMI interface controller, where the AMC board includes: a second IPMI interface controller;
  • the IPMB channel inside the remote device is a channel between the first IPMI interface controller in the MCH board and the second IPMI interface controller in the AMC board.
  • the AMC board is configured to process the fault data, and send the processed fault data to the MCH board through the IPMB channel.
  • the MCH board is configured to process the received fault data and report the processed fault data to the network management center.
  • the AMC board further includes: a second CPU control unit, and is connected to the second IPMI interface controller;
  • the AMC board is configured to process fault data in the following manner:
  • the second IPMI interface controller in the AMC board decodes the fault data acquired from the second CPU control unit, and converts the decoded data into data supported by the first IPMI interface controller in the MCH board. Formatting, and transmitting the formatted fault data to the first IPMI interface controller.
  • the MCH board further includes: a first CPU control unit, which is respectively connected to the second network interface and the first IPMI interface controller;
  • the MCH board is configured to process the received fault data in the following manner:
  • the first IPMI interface controller After receiving the fault data sent by the second IPMI interface controller in the AMC board, the first IPMI interface controller decodes the fault data and converts the fault data into an MCH board. a data format required by the first CPU control unit, and transmitting the format converted data to the first CPU control unit;
  • the first CPU control unit After receiving the fault data sent by the first IPMI interface controller, the first CPU control unit first decodes the fault data according to a data format supported by the second network interface in the MCH board, and decodes the fault data. The packet is packaged, and the packaged fault data is sent to the second network interface.
  • the MCH board reports the processed fault data to the network management center, including:
  • the second network interface in the MCH board reports the processed fault data to the network management center through the first network interface of the network management center.
  • An embodiment of the present invention provides a method for acquiring fault data, where the method includes:
  • the remote device acquires fault data
  • the remote device reports the fault data to the network management center through an internal intelligent platform management bus IPMB channel and an internetwork protocol IP channel between the remote device and the network management center, and the IP between the remote device and the network management center
  • IPMB channel refers to a channel between a second network interface in the remote device and a first network interface in the network management center.
  • the IPMB channel is a channel between the first IPMI interface controller on the MCH board of the remote device internal bearer and the second IPMI interface controller on the AMC board of the advanced mezzanine card.
  • the remote device reports the fault data to the network management center through the IPMB channel, including:
  • the AMC board processes the fault data and sends the processed fault data to the MCH board through the IPMB channel between the AMC board and the MCH board. After the MCH board processes the received fault data, it processes the fault. The fault data is reported to the network management center.
  • the AMC board processes the fault data, including:
  • the second IPMI interface controller in the AMC board decodes the fault data acquired from the second CPU control unit, and converts the decoded data into data supported by the first IPMI interface controller in the MCH board. Formatting, and transmitting the format converted data to the first IPMI interface controller.
  • the MCH board processes the fault data, including:
  • the first IPMI interface controller After receiving the fault data sent by the second IPMI interface controller in the AMC board, the first IPMI interface controller decodes the fault data and converts the fault data into an MCH board. a data format required by the first CPU control unit, and the format converted data is sent to the first CPU control unit; the first CPU control unit receives the first After the fault data is sent by the IPMI interface controller, the fault data is decoded according to the data format supported by the second network interface in the MCH board, and the decoded fault data is packaged and sent to the second network interface. .
  • the MCH board reports the processed fault data to the network management center, including:
  • the second network interface in the MCH board reports the processed fault data to the network management center through the first network interface of the network management center.
  • An embodiment of the present invention provides a remote device control system, where the system includes: a network management center and a remote device;
  • the network management center is configured to send a control instruction to the remote device by using an IP channel between the remote device and an IPMB channel inside the remote device;
  • the remote device is configured to receive a control command sent by the network management center, and perform a corresponding operation according to the control instruction.
  • the remote device includes: an MCH board and an AMC board;
  • the MCH board is configured to receive a control command from the network management center, and send the control command to the AMC board through an IPMI channel between the MCH board and the AMC board;
  • the AMC board is configured to receive a control command sent by the MCH board, and perform a corresponding operation according to the control instruction.
  • the MCH board includes: a first IPMI interface controller, where the AMC board includes: a second IPMI interface controller;
  • the IPMB channel inside the remote device is a channel between the first IPMI interface controller in the MCH board and the second IPMI interface controller in the AMC board.
  • An embodiment of the present invention provides a remote device control method, where the method includes:
  • the network management center generates a control instruction
  • the network management center sends a control command to the remote device through an IP channel between itself and the remote device and an IPMB channel inside the remote device.
  • the IPMB channel refers to a data channel between the first IPMI interface controller on the MCH board of the remote device and the second IPMI interface controller on the AMC board.
  • the embodiment of the present invention further provides a computer storage medium, the storage medium comprising a set of computer executable instructions for performing the fault data acquisition method according to the embodiment of the present invention.
  • the embodiment of the invention further provides a computer storage medium, the storage medium comprising a set of computer executable instructions, the instructions being used to execute the remote device control method according to the embodiment of the invention.
  • the remote device reports the device fault data to the network management center through the internal IP data channel, which not only provides a new alternative, but also can be used as the device fault data acquisition in the prior art.
  • the fault data is reported to the network management center through the IPMB channel inside the remote device.
  • FIG. 1 is a basic structural diagram of a remote device fault data acquisition system in the prior art
  • FIG. 2 is a schematic structural diagram 1 of a remote device fault data acquiring system according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram 2 of a remote device fault data acquiring system according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for acquiring fault data of a remote device according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for controlling a remote device according to an embodiment of the present invention.
  • the remote device fault data acquiring system includes: a network management center and a remote device; wherein the network management center is configured to receive fault data sent by the remote device; and the remote device is configured to pass through the internal device.
  • Intelligent Platform Management Bus (IPMB) channel and remote device and network management center
  • IP Internet Protocol
  • the first embodiment of the present invention provides a remote device fault data acquiring system.
  • the system includes: a network management center 11 and a remote device 12;
  • the network management center 11 is configured to receive device fault data and analyze and process the received device fault data.
  • the remote device 12 is configured to report device fault data to the network management center through an internal IPMB channel and an Internet Protocol (IP) channel between the remote device and the network management center.
  • IP Internet Protocol
  • the remote device 12 includes: a MicroTCA Carrier Hub (MCH) single board 103 and an Advanced Mezzanine Card (AMC) board 106;
  • MCH MicroTCA Carrier Hub
  • AMC Advanced Mezzanine Card
  • the MCH board 103 is configured to send device fault data to the network management center 11, and the device fault data is from the AMC board 106;
  • the AMC board 106 is configured to acquire device fault data, and send it to the MCH board 103 through the IPMB channel between the MCH board 103 and the MCH board 103;
  • the first network interface 101 of the network management center 11 is connected to the second network interface 102 of the MCH board 103 in the remote device 12, thereby implementing the network management center 11 and the MCH board 103 (or implementing the network management center 11).
  • the channel between the first network interface 101 and the second network interface 102 is an IP channel between the network management center 11 and the remote device 12;
  • the MCH board 103 passes through its own first Intelligent Platform Management Interface (IPMB) controller 107 and the AMC board 106.
  • IPMB Intelligent Platform Management Interface
  • the second IPMI interface controller 108 is connected to implement communication between the MCH board 103 and the AMC board 106 in the remote device 12; wherein the first IPMI interface controller 107 in the MCH board 103 is
  • the channel between the second IPMI interface controller 108 in the AMC board 106 may be referred to as an IPMB channel between the MCH board 103 and the AMC board 106.
  • the remote device AMC board 106 reports the device fault data to the network management center 11 through the IPMB channel between the AMC board and the MCH board 103.
  • the reported fault data may report the fault data or periodically report the fault data. Or a non-periodic reporting of fault data and the like.
  • the remote device MCH board 103 further includes: a first CPU control unit 31, and the remote device AMC board 106 further includes a second CPU.
  • the control unit 32; the first CPU control unit 31 is connected to the second network interface 102 and the first IPMI interface controller 107, respectively, and the second CPU control unit 32 is connected to the second IPMI interface controller 108.
  • the second CPU control unit 32 processes the device fault information to generate fault data, and the data format of the fault data may be: a recommended identifier 232 (RS232, Recommended Standard 232), or a recommended identifier 485 (RS485, Recommended Standard 485) ), or a local bus or the like, after which the format converted data is sent to the second IPMI interface controller 108.
  • a recommended identifier 232 RS232, Recommended Standard 232
  • a recommended identifier 485 RS485, Recommended Standard 485
  • the second IPMI interface controller 108 decodes the fault data acquired from the second CPU control unit 32, and converts the decoded data into a data format required by the first IPMI interface controller 107, the required
  • the data format may be, for example, a format required by an Inter-Integrated Circuit (I2C) bus, and the format converted data is transmitted to the first IPMI interface controller 107.
  • I2C Inter-Integrated Circuit
  • the first IPMI interface controller 107 receives the second IPMI interface controller 108 to send After the fault data, the fault data is decoded, and the fault data is converted into a data format required by the first CPU control unit 31, for example, may be RS232, or RS485 or localbus format data, and then format conversion The latter data is sent to the first CPU control unit 31.
  • the first CPU control unit 31 After receiving the data sent by the first IPMI interface controller 107, the first CPU control unit 31 first decodes the data according to the data format supported by the second network interface 102, restores the real data, and restores the restored real data according to the Ethernet. The format of the packet is packaged and then transmitted to the second network interface 102.
  • the second network interface 102 transmits the received data directly to the first network interface 101.
  • the fault data is finally reported from the remote device to the network management center, and the network management center processes the fault data to realize rapid fault location and processing.
  • the second embodiment of the present invention provides a method for acquiring fault data of a remote device. As shown in FIG. 4, the method includes the following steps:
  • Step 401 The remote device acquires fault data.
  • the remote device needs to collect and organize the device failure data
  • the remote device processes the fault data, including:
  • the second CPU control unit in the AMC board of the remote device processes the device fault information to generate fault data, and the data format of the fault data may be: RS232, RS485, or localbus;
  • the second CPU control unit sends the format converted data to the second IPMI interface controller in the AMC board.
  • Step 402 The remote device reports the fault data to the network management center through an internal IPMB channel and an IP channel between the network management center, and the IP channel between the remote device and the network management center refers to the remote device. a second network interface with the network management center a channel between the first network interfaces;
  • the IPMB channel refers to a data channel between the first IPMI interface controller on the MCH board of the remote device and the second IPMI interface controller on the AMC board.
  • the remote device reports the fault data to the network management center through the IPMB channel, including:
  • the AMC board processes the fault data and sends the processed fault data to the MCH board. After processing the fault data, the MCH board reports the fault data to the network management center.
  • the processing of the fault data by the AMC board includes:
  • the second IPMI interface controller in the AMC board decodes the fault data acquired from the second CPU control unit, and converts the decoded data into data supported by the first IPMI interface controller in the MCH board.
  • the format, the supported data format for example, may be a format required by the I2C bus, and then the format converted data is sent to the first IPMI interface controller.
  • the processing of the fault data by the MCH board includes:
  • the first IPMI interface controller After receiving the fault data sent by the second IPMI interface controller in the AMC board, the first IPMI interface controller decodes the fault data and converts the fault data into an MCH board.
  • the data format required by the first CPU control unit may be RS232, or RS485 or localbus format data, and then the format converted data is sent to the first CPU control unit; the first CPU control unit receives the first After the fault data sent by the IPMI interface controller, the fault data is first decoded according to the data format supported by the second network interface in the MCH board, and the real data is restored, and the restored real data is according to the Ethernet packet.
  • the format is packaged and then transmitted to the second network interface.
  • the MCH board reports the processed fault data to the network management center, including:
  • the second network interface in the MCH board reports the processed fault data to the network management center through the first network interface of the network management center.
  • the third embodiment of the present invention provides a remote device control system.
  • the basic structure of the system is the same as that of the fault data reporting system shown in FIG. 2 . Therefore, the remote device control system is directly introduced by using FIG. 2 as an example.
  • the system includes: a network management center 11 and a remote device 12; wherein
  • the network management center 11 is configured to send a control instruction to the remote device 12 through an IP channel between the remote device 12 and an IPMB channel inside the remote device;
  • the remote device 12 is configured to receive a control command sent by the network management center 11 and perform a corresponding operation according to the control instruction.
  • the remote device 12 includes: an MCH board 103 and an AMC board 106;
  • the MCH board 103 is configured to receive the control command from the network management center 11 and send the control command to the AMC board 106 through the IPMI channel between the AMC board 106 and the AMC board 106;
  • the AMC board 106 is configured to receive a control command sent by the MCH board 103, and perform a corresponding operation according to the control instruction;
  • the first network interface 101 of the network management center 11 is connected to the second network interface 102 of the MCH board 103 in the remote device 12, thereby implementing the network management center 11 and the MCH board 103 (or implementing the network management center 11).
  • the channel between the first network interface 101 and the second network interface 102 is an IP channel between the network management center 11 and the remote device 12;
  • the MCH board 103 is connected to the second IPMI interface controller 108 on the AMC board 106 through its own IPMB controller 107, so that communication between the MCH board 103 and the AMC board 106 is implemented inside the remote device;
  • the channel between the first IPMI interface controller 107 and the second IPMI interface controller 108 in the AMC board 106 may be referred to as between the MCH board 103 and the AMC board 106. IPMB channel.
  • the remote device MCH board 103 sends a control command sent by the network management center 11 to the AMC board 106 through the IPMB channel between the remote device and the AMC board 106.
  • the remote device The MCH board 103 further includes: a first CPU control unit 31, the remote device AMC board 106 further includes a second CPU control unit 32; the first CPU control unit 31 and the second network interface 102 and the first IPMI, respectively
  • the interface controller 107 is connected, and the second CPU control unit 32 is connected to the second IPMI interface controller 108.
  • the control command is directly sent to the second network interface 102 of the remote device 12 through the first network interface 101, and the control command is Ethernet format data;
  • the control instruction After the second network interface 102 receiving the control instruction converts the control instruction into a data format supported by the first CPU control unit 31, the control instruction is sent to the first CPU control unit 31; wherein
  • the data format supported by the first CPU control unit 31 may be RS232, or RS485 or localbus;
  • the first CPU control unit 31 After receiving the format-converted control command sent by the second network interface 102, the first CPU control unit 31 performs format conversion on the control command, and converts the control command into data supported by the first IPMI interface controller unit 107. The format is then sent to the first IPMI interface control unit 107; wherein the data format supported by the first IPMI interface controller unit 107 may be an I2C bus format or the like.
  • the first IPMI interface controller 107 directly sends the received control command to the second IPMI interface controller 108; after the second IPMI interface controller 108 performs format conversion on the control command, the control command is converted into
  • the data format supported by the second CPU control unit 32 may be RS232, RS485 or localbus.
  • the second CPU control unit 32 After receiving the control command, the second CPU control unit 32 parses the control command and performs a corresponding operation according to the instruction of the control command.
  • a fourth embodiment of the present invention provides a method for acquiring fault data of a remote device. As shown in FIG. 5, the method includes the following steps:
  • Step 501 The network management center generates a control instruction.
  • the network management center In this step, the network management center generates a control command that is sent to the remote device according to actual needs.
  • Step 502 The network management center sends a control instruction to the remote device by using an IP channel between itself and the remote device and an IPMB channel inside the remote device.
  • the IP channel between the remote device and the network management center refers to a channel between the second network interface on the remote device and the first network interface on the network management center.
  • the IPMB channel refers to a data channel between the first IPMI interface controller on the MCH board of the remote device and the second IPMI interface controller on the AMC board.
  • the network management center sends a control instruction to the remote device through an IPMB channel inside the remote device, including:
  • the remote device sends a control command to the MCH board of the remote device. After the MCH board processes the control command, the control command is sent to the AMC board, and the AMC board performs the control command. Processing, and performing corresponding operations according to the control instruction;
  • the MCH board processes the control command, including:
  • the second network interface in the MCH board converts the received control command into a data format supported by the first CPU control unit, and then sends the control command to the first CPU control unit; wherein the first CPU
  • the data format supported by the control unit can be RS232, or RS485, or localbus;
  • the first CPU control unit After receiving the control instruction, the first CPU control unit converts the control instruction into a data format supported by the first IPMI interface controller, and sends the data format to the first IPMI interface controller; wherein the first IPMI interface
  • the data format supported by the controller is the I2C bus format and the like.
  • the AMC board processes the control command, including:
  • the second IPMI interface controller in the AMC board After receiving the control instruction, the second IPMI interface controller in the AMC board converts the control command into a data format supported by the second CPU control unit, and sends the data format to the second CPU control unit;
  • the data format supported by the CPU control unit is RS232, RS485 or localbus.
  • the embodiment of the present invention further provides a computer storage medium, the storage medium comprising a set of computer executable instructions, and the instructions are used to execute the fault data acquisition method according to the second embodiment of the present invention.
  • the embodiment of the present invention further provides a computer storage medium, the storage medium comprising a set of computer executable instructions for performing the remote device control method according to Embodiment 4 of the present invention.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the device is implemented in a flow chart A function specified in a block or blocks of a process or multiple processes and/or block diagrams.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本发明公开了一种故障数据获取系统,包括:网络管理中心和远程设备;其中,所述网络管理中心,用于接收远程设备发送的故障数据;所述远程设备,用于通过内部的智能平台管理总线IPMB通道、以及远程设备与网络管理中心之间的网际互联协议IP通道向网络管理中心上报设备故障数据,所述远程设备与网络管理中心之间的IP通道是指所述远程设备中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。本发明同时还公开了一种故障数据获取方法、远程设备控制系统及方法。

Description

一种故障数据获取系统和远程设备控制系统及其对应方法 技术领域
本发明涉及通信领域,具体涉及一种故障数据获取系统和远程设备控制系统及其对应方法。
背景技术
uTCA作为微型通讯计算架构(Micro TCA,Micro Telecommunications Computing Architecture)的第一个版本,是为了满足小型设备的制造和维护要求,从高级通讯计算机架构(ATCA,Advanced Telecom Computing Architecture)中演化而来,其目的是为了解决通信领域各厂商间的设备无法相互兼容,导致组件制造无法产业化、制造周期长且维护成本高的问题。其规范了设备的组成元素和元素之间的接口,提高了设备之间的兼容性,并且对设备的可靠性和性能给出了规定,为系统集成和业务开发提供统一的平台。
目前,为了实现网络管理中心与远程设备之间的通信,其架构如图1所示,基于uTCA架构的远程设备12与网络管理中心11通过第一网络接口101和第二网络接口102相连接,并进行数据传输,所述数据传输是基于IP协议传输,因此,将所述远程设备12和网络管理中心11之间进行数据传输的通道称为IP通道,两者之间的链路可以使用以太网双绞线链接或者距离较远时使用光纤相连;在网络管理中心11可以很方便的使用基于IP协议的网线或光纤登陆到远程设备12的控制板(承载集线器(MCH,MicroTCA Carrier Hub)单板103)上或者在基于uTCA架构的远程设备上,通过MCH单板103和高级夹层卡(AMC,Advanced Mezzanine Card)单板之间的IP连接通道(第三网络接口104和第四网络接口105之间的连接 通道)登陆到AMC单板106上进行故障定位。但是,如果AMC单板106和MCH单板103之间的IP通道无法正常连接时,由于现有技术中并没有一种替代方案能够实现网络管理中心对远程设备故障数据的获取及对远程设备的控制,也就无法对AMC单板进行远程定位及故障排查。
如果由工程维护人员到达远程设备处进行故障数据获取,从而进行故障排查、处理,则费时、费力且成本较高。
发明内容
为了解决现有存在的技术问题,本发明实施例期望提供一种故障数据获取系统和远程设备控制系统及其对应方法。
本发明实施例提供了一种故障数据获取系统,所述系统包括:网络管理中心和远程设备;其中,
所述网络管理中心,配置为接收远程设备发送的故障数据;
所述远程设备,配置为通过内部的智能平台管理总线IPMB通道、以及远程设备与网络管理中心之间的网际互联协议IP通道向网络管理中心上报设备故障数据,所述远程设备与网络管理中心之间的IP通道是指所述远程设备中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。
上述方案中,所述远程设备包括:承载集线器MCH单板及高级夹层卡AMC单板;其中,
所述MCH单板,配置为向网络管理中心发送设备故障数据,所述设备故障数据来自于AMC单板;
所述AMC单板,配置为获取设备故障数据,并通过与MCH单板之间的IPMB通道发送给MCH单板。
上述方案中,所述MCH单板包括:第一IPMI接口控制器,所述AMC单板包括:第二IPMI接口控制器;
所述远程设备内部的IPMB通道为所述MCH单板中第一IPMI接口控制器与所述AMC单板中第二IPMI接口控制器之间的通道。
上述方案中,所述AMC单板配置为对故障数据进行处理,并将处理后的故障数据通过IPMB通道发送给MCH单板;
所述MCH单板配置为对接收到的故障数据进行处理后,将处理后的故障数据上报网络管理中心。
上述方案中,所述AMC单板还包括:第二CPU控制单元,与所述第二IPMI接口控制器相连;
所述AMC单板配置为通过以下方式对故障数据进行处理:
所述AMC单板中的第二IPMI接口控制器对从第二CPU控制单元获取的故障数据进行译码,并将译码后的数据转换成MCH单板中第一IPMI接口控制器支持的数据格式,并将格式转换后的故障数据发送给所述第一IPMI接口控制器。
上述方案中,所述MCH单板还包括:第一CPU控制单元,分别与第二网络接口和第一IPMI接口控制器相连;
所述MCH单板配置为通过以下方式对接收到的故障数据进行处理:
所述MCH单板中的第一IPMI接口控制器接收到AMC单板中第二IPMI接口控制器发送的故障数据后,对所述故障数据进行译码,将所述故障数据转换成MCH单板中第一CPU控制单元要求的数据格式,并将格式转换后的数据发送给所述第一CPU控制单元;
第一CPU控制单元接收到第一IPMI接口控制器发送的故障数据后先将所述故障数据按照MCH单板中的第二网络接口支持的数据格式进行译码,并对译码后的故障数据进行打包,将打包后的故障数据发送给第二网络接口。
上述方案中,所述MCH单板将处理后的故障数据上报网络管理中心,包括:
MCH单板中的第二网络接口通过网络管理中心的第一网络接口将处理后的故障数据上报网络管理中心。
本发明实施例提供了一种故障数据获取方法,所述方法包括:
远程设备获取故障数据;
所述远程设备通过内部智能平台管理总线IPMB通道、以及远程设备与网络管理中心之间的网际互联协议IP通道将所述故障数据上报网络管理中心,所述远程设备与网络管理中心之间的IP通道是指所述远程设备中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。
上述方案中,所述IPMB通道为远程设备内部承载集线器MCH单板上的第一IPMI接口控制器与高级夹层卡AMC单板上的第二IPMI接口控制器之间的通道。
上述方案中,所述远程设备通过所述IPMB通道将故障数据上报网络管理中心,包括:
AMC单板对故障数据进行处理,并将处理后的故障数据通过AMC单板与MCH单板之间的IPMB通道发送给MCH单板,MCH单板对接收到的故障数据进行处理后,将处理后的故障数据上报网络管理中心。
上述方案中,所述AMC单板对故障数据进行处理,包括:
所述AMC单板中的第二IPMI接口控制器对从第二CPU控制单元获取的故障数据进行译码,并将译码后的数据转换成MCH单板中第一IPMI接口控制器支持的数据格式,并将格式转换后的数据发送给所述第一IPMI接口控制器。
上述方案中,所述MCH单板对故障数据进行处理,包括:
所述MCH单板中的第一IPMI接口控制器接收到AMC单板中第二IPMI接口控制器发送的故障数据后,对所述故障数据进行译码,将所述故障数据转换成MCH单板中第一CPU控制单元要求的数据格式,将格式转换后的数据发送给所述第一CPU控制单元;第一CPU控制单元接收到第一 IPMI接口控制器发送的故障数据后,将所述故障数据按照MCH单板中的第二网络接口支持的数据格式进行译码,对译码后的故障数据进行打包,并发送给第二网络接口。
上述方案中,所述MCH单板将处理后的故障数据上报网络管理中心,包括:
MCH单板中的第二网络接口通过网络管理中心的第一网络接口将处理后的故障数据上报网络管理中心。
本发明实施例提供了一种远程设备控制系统,所述系统包括:网络管理中心和远程设备;其中,
所述网络管理中心,配置为通过与远程设备之间的IP通道和远程设备内部的IPMB通道向远程设备发送控制指令;
所述远程设备,配置为接收网络管理中心发送的控制指令,并根据所述控制指令执行相应操作。
上述方案中,所述远程设备包括:MCH单板及AMC单板;其中,
所述MCH单板,配置为接收来自网络管理中心的控制指令,并通过自身与AMC单板之间的IPMI通道将所述控制指令发送至AMC单板;
所述AMC单板,配置为接收MCH单板发送的控制指令,并根据所述控制指令执行相应操作。
上述方案中,所述MCH单板包括:第一IPMI接口控制器,所述AMC单板包括:第二IPMI接口控制器;
所述远程设备内部的IPMB通道为所述MCH单板中第一IPMI接口控制器与所述AMC单板中第二IPMI接口控制器之间的通道。
本发明实施例提供了一种远程设备控制方法,所述方法包括:
网络管理中心生成控制指令;
所述网络管理中心通过自身与远程设备之间的IP通道和远程设备内部的IPMB通道向远程设备发送控制指令。
上述方案中,所述IPMB通道是指远程设备内部MCH单板上的第一IPMI接口控制器与AMC单板上的第二IPMI接口控制器之间的数据通道。
本发明实施例还提供了一种计算机存储介质,所述存储介质包括一组计算机可执行指令,所述指令用于执行本发明实施例所述的故障数据获取方法。
本发明实施例还提供了一种计算机存储介质,所述存储介质包括一组计算机可执行指令,所述指令用于执行本发明实施例所述的远程设备控制方法。
本发明实施例相较于现有技术中远程设备通过内部IP数据通道向网络管理中心上报设备故障数据的方案,不仅提供了一种新的替代方案,也能够作为现有技术中设备故障数据获取方案的备用方案,在现有技术的远程设备中用于故障数据获取的IP数据通道发生故障时,使得故障数据通过远程设备内部的IPMB通道向网络管理中心进行故障数据的上报。
附图说明
图1为现有技术中远程设备故障数据获取系统基本结构图;
图2为本发明实施例提供的远程设备故障数据获取系统基本结构图一;
图3为本发明实施例提供的远程设备故障数据获取系统基本结构图二;
图4为本发明实施例提供的远程设备故障数据获取方法流程图;
图5为本发明实施例提供的远程设备控制方法流程图。
具体实施方式
本发明实施例中,远程设备故障数据获取系统,包括:网络管理中心和远程设备;其中,所述网络管理中心,配置为接收远程设备发送的故障数据;所述远程设备,配置为通过内部的智能平台管理总线(IPMB,Intelligent Platform Management Bus)通道、以及远程设备与网络管理中心 之间的网际互联协议(IP)通道向网络管理中心上报设备故障数据,所述远程设备与网络管理中心之间的IP通道是指所述远程设备中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。
下面通过附图及具体实施例对本发明做进一步的详细说明。
实施例一
本发明实施例一提供了一种远程设备故障数据获取系统,如图2所示,该系统包括:网络管理中心11和远程设备12;其中,
所述网络管理中心11,配置为接收设备故障数据并对接收到的设备故障数据进行分析、处理;
所述远程设备12,配置为通过内部的IPMB通道、以及远程设备与网络管理中心之间的网际互联协议(IP,Internet Protocol)通道向网络管理中心上报设备故障数据。
所述远程设备12包括:MicroTCA架构下的承载集线器(MCH,MicroTCA Carrier Hub)单板103及高级夹层卡(AMC,Advanced Mezzanine Card)单板106;其中,
所述MCH单板103,配置为向网络管理中心11发送设备故障数据,所述设备故障数据来自于AMC单板106;
所述AMC单板106,配置为获取设备故障数据,并通过与MCH单板103之间的IPMB通道发送给MCH单板103;
所述网络管理中心11的第一网络接口101与远程设备12中MCH单板103的第二网络接口102相连接,从而实现网络管理中心11与MCH单板103(或者说是实现网络管理中心11与远程设备12)之间的通信,该第一网络接口101与第二网络接口102之间的通道即为网络管理中心11与远程设备12之间的IP通道;
所述MCH单板103通过自身的第一智能平台管理接口(IPMB,Intelligent Platform Management Interface)控制器107与AMC单板106上 的第二IPMI接口控制器108相连接,从而在远程设备12内部实现MCH单板103与AMC单板106之间的通信;其中,所述MCH单板103中第一IPMI接口控制器107与所述AMC单板106中第二IPMI接口控制器108之间的通道可以被称为MCH单板103和AMC单板106间的IPMB通道。
所述远程设备AMC单板106通过其与MCH单板103之间的IPMB通道向网络管理中心11上报设备故障数据;所述上报故障数据可以为应请求上报故障数据、或者周期性上报故障数据、或者非周期性上报故障数据等等方式。
如图3所示,在图2所示远程故障定位系统的基础上,所述远程设备MCH单板103还包括:第一CPU控制单元31,所述远程设备AMC单板106还包括第二CPU控制单元32;所述第一CPU控制单元31分别与第二网络接口102和第一IPMI接口控制器107相连,所述第二CPU控制单元32与第二IPMI接口控制器108相连。
下面基于图3,对本发明实施例一提供的远程故障定位系统中的实现原理做以下详细介绍:
所述第二CPU控制单元32对设备故障信息进行处理,生成故障数据,所述故障数据的数据格式可以为:推荐标识232(RS232,Recommended Standard 232)、或者推荐标识485(RS485,Recommended Standard 485)、或者局域总线(localbus)等,之后,将格式转换后的数据发送给第二IPMI接口控制器108。
所述第二IPMI接口控制器108对从第二CPU控制单元32获取的故障数据进行译码,并将译码后的数据转换成第一IPMI接口控制器107要求的数据格式,所述要求的数据格式例如可以是互联集成电路(I2C,Inter-Integrated Circuit)总线要求的格式,将格式转换后的数据发送给第一IPMI接口控制器107。
所述第一IPMI接口控制器107接收到第二IPMI接口控制器108发送 的故障数据后,对所述故障数据进行译码,将所述故障数据转换成第一CPU控制单元31要求的数据格式,例如,可以是RS232、或者RS485或者localbus等格式数据,之后将格式转换后的数据发送给第一CPU控制单元31。
第一CPU控制单元31接收到第一IPMI接口控制器107发送的数据后先将数据按照第二网络接口102支持的数据格式进行译码,还原真实数据,并将还原后的真实数据按照以太网包的格式进行打包,然后传送给第二网络接口102。
第二网络接口102将接收到的数据直接发送到第一网络接口101。
经过以上一系列处理后,最终完成故障数据从远程设备向网络管理中心的上报,网络管理中心通过对故障数据进行处理,从而实现故障的快速定位和处理。
实施例二
本发明实施例二提供了一种远程设备故障数据获取方法,如图4所示,所述方法包括以下步骤:
步骤401:远程设备获取故障数据;
这一步骤中,远程设备需要收集并整理设备故障数据;
所述远程设备对故障数据进行处理,包括:
所述远程设备中AMC单板中的第二CPU控制单元对设备故障信息进行处理,生成故障数据,所述故障数据的数据格式可以为:RS232、或者RS485、或者localbus等;
之后,所述第二CPU控制单元将格式转换后的数据发送给所述AMC单板中的第二IPMI接口控制器。
步骤402:远程设备通过内部IPMB通道、及与网络管理中心之间的IP通道将所述故障数据上报网络管理中心,所述远程设备与网络管理中心之间的IP通道是指所述远程设备上的第二网络接口与所述网络管理中心上的 第一网络接口之间的通道;
所述IPMB通道是指远程设备内部MCH单板上的第一IPMI接口控制器与AMC单板上的第二IPMI接口控制器之间的数据通道。
远程设备通过所述IPMB通道将故障数据上报网络管理中心,包括:
AMC单板对故障数据进行处理,并将处理后的故障数据发送给MCH单板,MCH单板对所述故障数据进行处理后,将处理后的故障数据上报网络管理中心。
所述AMC单板对故障数据进行处理包括:
所述AMC单板中的第二IPMI接口控制器对从第二CPU控制单元获取的故障数据进行译码,并将译码后的数据转换成MCH单板中第一IPMI接口控制器支持的数据格式,所述支持的数据格式,例如可以是I2C总线要求的格式,之后将格式转换后的数据发送给所述第一IPMI接口控制器。
所述MCH单板对故障数据进行处理包括:
所述MCH单板中的第一IPMI接口控制器接收到AMC单板中第二IPMI接口控制器发送的故障数据后,对所述故障数据进行译码,将所述故障数据转换成MCH单板中第一CPU控制单元要求的数据格式,例如,可以是RS232、或者RS485或者localbus等格式数据,之后将格式转换后的数据发送给所述第一CPU控制单元;第一CPU控制单元接收到第一IPMI接口控制器发送的故障数据后先将所述故障数据按照MCH单板中的第二网络接口支持的数据格式进行译码,还原真实数据,并将还原后的真实数据按照以太网包的格式进行打包,然后传送给第二网络接口。
MCH单板将处理后的故障数据上报网络管理中心,包括:
MCH单板中的第二网络接口通过网络管理中心的第一网络接口将处理后的故障数据上报网络管理中心。
实施例三
本发明实施例三提供了一种远程设备控制系统,该系统的基本结构与图2示出的故障数据上报系统相同,因此,直接以图2为例,对该远程设备控制系统进行介绍,该系统包括:网络管理中心11和远程设备12;其中,
所述网络管理中心11,配置为通过与远程设备12之间的IP通道和远程设备内部的IPMB通道向远程设备12发送控制指令;
所述远程设备12,配置为接收网络管理中心11发送的控制指令,并根据所述控制指令执行相应操作。
所述远程设备12包括:MCH单板103及AMC单板106;其中,
所述MCH单板103,配置为接收来自网络管理中心11的控制指令,并通过自身与AMC单板106之间的IPMI通道将所述控制指令发送至AMC单板106;
所述AMC单板106,配置为接收MCH单板103发送的控制指令,并根据所述控制指令执行相应操作;
所述网络管理中心11的第一网络接口101与远程设备12中MCH单板103的第二网络接口102相连接,从而实现网络管理中心11与MCH单板103(或者说是实现网络管理中心11与远程设备12)之间的通信,该第一网络接口101与第二网络接口102之间的通道即为网络管理中心11与远程设备12之间的IP通道;
所述MCH单板103通过自身的IPMB控制器107与AMC单板106上的第二IPMI接口控制器108相连接,从而在远程设备内部实现MCH单板103与AMC单板106之间的通信;其中,所述MCH单板103中第一IPMI接口控制器107与所述AMC单板106中第二IPMI接口控制器108之间的通道可以被称为MCH单板103和AMC单板106间的IPMB通道。
所述远程设备MCH单板103通过其与AMC单板106之间的IPMB通道将网络管理中心11发送的控制指令发送给AMC单板106。
如图3所示,在图2所示远程设备控制系统的基础上,所述远程设备 MCH单板103还包括:第一CPU控制单元31,所述远程设备AMC单板106还包括第二CPU控制单元32;所述第一CPU控制单元31分别与第二网络接口102和第一IPMI接口控制器107相连,所述第二CPU控制单元32与第二IPMI接口控制器108相连。
下面基于图3,对本发明实施例三提供的远程设备控制系统的实现原理做以下详细介绍:
网关管理中心11生成控制指令后,直接将所述控制指令通过第一网络接口101发送至远程设备12的第二网络接口102,所述控制指令为以太网格式数据;
接收到所述控制指令的第二网络接口102将所述控制指令转换成第一CPU控制单元31所支持的数据格式之后,将所述控制指令发送至第一CPU控制单元31;其中,所述第一CPU控制单元31所支持的数据格式可以是RS232、或者RS485或者localbus等;
第一CPU控制单元31接收到第二网络接口102发送的格式转换后的控制指令后,对所述控制指令进行格式转换,将所述控制指令转换成第一IPMI接口控制器单元107支持的数据格式,之后,发送给所述第一IPMI接口控制单元107;其中,所述第一IPMI接口控制器单元107支持的数据格式可以为I2C总线格式等。
第一IPMI接口控制器107直接将所述接收到的控制指令发送个第二IPMI接口控制器108;第二IPMI接口控制器108对所述控制指令进行格式转换后,将所述控制指令转换成第二CPU控制单元32支持的数据格式之后,发送给第二CPU控制单元32;所述第二CPU控制单元32支持的数据格式为可以是RS232、或者RS485或者localbus等。
接收到所述控制指令后,第二CPU控制单元32对所述控制指令进行解析,并根据所述控制指令的指示执行相应操作。
实施例四
本发明实施例四提供了一种远程设备故障数据获取方法,如图5所示,所述方法包括以下步骤:
步骤501:网络管理中心生成控制指令;
这一步骤中,网络管理中心根据实际需要生成向远程设备下发的控制指令。
步骤502:所述网络管理中心通过自身与远程设备之间的IP通道和远程设备内部的IPMB通道向远程设备发送控制指令;
所述远程设备与网络管理中心之间的IP通道是指所述远程设备上的第二网络接口与所述网络管理中心上的第一网络接口之间的通道。
所述IPMB通道是指远程设备内部MCH单板上的第一IPMI接口控制器与AMC单板上的第二IPMI接口控制器之间的数据通道。
所述网络管理中心通过远程设备内部的IPMB通道向远程设备发送控制指令,包括:
远程设备将控制指令发送至远程设备的MCH单板,所述MCH单板对所述控制指令进行处理后,将所述控制指令发送给AMC单板,所述AMC单板对所述控制指令进行处理,并根据所述控制指令执行相应操作;
所述MCH单板对所述控制指令进行处理,包括:
MCH单板中的第二网络接口将接收到的控制指令转换成第一CPU控制单元所支持的数据格式,之后,将所述控制指令发送至第一CPU控制单元;其中,所述第一CPU控制单元所支持的数据格式可以是RS232、或者RS485、或者localbus等;
第一CPU控制单元接收到所述控制指令后,将所述控制指令转换为第一IPMI接口控制器所支持的数据格式,并发送给第一IPMI接口控制器;其中,所述第一IPMI接口控制器所支持的数据格式为I2C总线格式等。
所述AMC单板对所述控制指令进行处理,包括:
AMC单板中的第二IPMI接口控制器接收到所述控制指令后,将所述控制指令转换为第二CPU控制单元所支持的数据格式,并发送给第二CPU控制单元;所述第二CPU控制单元支持的数据格式为RS232、或者RS485或者localbus等。
本发明实施例还提供了一种计算机存储介质,所述存储介质包括一组计算机可执行指令,所述指令用于执行本发明实施例二所述的故障数据获取方法。
本发明实施例还提供了一种计算机存储介质,所述存储介质包括一组计算机可执行指令,所述指令用于执行本发明实施例四所述的远程设备控制方法。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、或计算机程序产品。因此,本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个 流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述,仅为本发明的较佳实施例而已,并非用于限定本发明的保护范围。

Claims (20)

  1. 一种故障数据获取系统,所述系统包括:网络管理中心和远程设备;其中,
    所述网络管理中心,配置为接收远程设备发送的故障数据;
    所述远程设备,配置为通过内部的智能平台管理总线IPMB通道、以及远程设备与网络管理中心之间的网际互联协议IP通道向网络管理中心上报设备故障数据,所述远程设备与网络管理中心之间的IP通道是指所述远程设备中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。
  2. 根据权利要求1所述的系统,其中,所述远程设备包括:承载集线器MCH单板及高级夹层卡AMC单板;其中,
    所述MCH单板,配置为向网络管理中心发送设备故障数据,所述设备故障数据来自于AMC单板;
    所述AMC单板,配置为获取设备故障数据,并通过与MCH单板之间的IPMB通道发送给MCH单板。
  3. 根据权利要求2所述的系统,其中,所述MCH单板包括:第一IPMI接口控制器,所述AMC单板包括:第二IPMI接口控制器;
    所述远程设备内部的IPMB通道为所述MCH单板中第一IPMI接口控制器与所述AMC单板中第二IPMI接口控制器之间的通道。
  4. 根据权利要求3所述的系统,其中,所述AMC单板配置为对故障数据进行处理,并将处理后的故障数据通过IPMB通道发送给MCH单板;
    所述MCH单板配置为对接收到的故障数据进行处理后,将处理后的故障数据上报网络管理中心。
  5. 根据权利要求4所述的系统,其中,所述AMC单板还包括:第 二CPU控制单元,与所述第二IPMI接口控制器相连;
    所述AMC单板配置为通过以下方式对故障数据进行处理:
    所述AMC单板中的第二IPMI接口控制器对从第二CPU控制单元获取的故障数据进行译码,并将译码后的数据转换成MCH单板中第一IPMI接口控制器支持的数据格式,并将格式转换后的故障数据发送给所述第一IPMI接口控制器。
  6. 根据权利要求4或5所述的系统,其中,所述MCH单板还包括:第一CPU控制单元,分别与第二网络接口和第一IPMI接口控制器相连;
    所述MCH单板配置为通过以下方式对接收到的故障数据进行处理:
    所述MCH单板中的第一IPMI接口控制器接收到AMC单板中第二IPMI接口控制器发送的故障数据后,对所述故障数据进行译码,将所述故障数据转换成MCH单板中第一CPU控制单元要求的数据格式,并将格式转换后的数据发送给所述第一CPU控制单元;
    第一CPU控制单元接收到第一IPMI接口控制器发送的故障数据后先将所述故障数据按照MCH单板中的第二网络接口支持的数据格式进行译码,并对译码后的故障数据进行打包,将打包后的故障数据发送给第二网络接口。
  7. 根据权利要求4所述的系统,其中,所述MCH单板将处理后的故障数据上报网络管理中心,包括:
    MCH单板中的第二网络接口通过网络管理中心的第一网络接口将处理后的故障数据上报网络管理中心。
  8. 一种故障数据获取方法,所述方法包括:
    远程设备获取故障数据;
    所述远程设备通过内部智能平台管理总线IPMB通道、以及远程设备与网络管理中心之间的网际互联协议IP通道将所述故障数据上报网络管理中心,所述远程设备与网络管理中心之间的IP通道是指所述远程设备 中的第二网络接口与所述网络管理中心中的第一网络接口之间的通道。
  9. 根据权利要求8所述的方法,其中,所述IPMB通道为远程设备内部承载集线器MCH单板上的第一IPMI接口控制器与高级夹层卡AMC单板上的第二IPMI接口控制器之间的通道。
  10. 根据权利要求9所述的方法,其中,所述远程设备通过所述IPMB通道将故障数据上报网络管理中心,包括:
    AMC单板对故障数据进行处理,并将处理后的故障数据通过AMC单板与MCH单板之间的IPMB通道发送给MCH单板,MCH单板对接收到的故障数据进行处理后,将处理后的故障数据上报网络管理中心。
  11. 根据权利要求10所述的方法,其中,所述AMC单板对故障数据进行处理,包括:
    所述AMC单板中的第二IPMI接口控制器对从第二CPU控制单元获取的故障数据进行译码,并将译码后的数据转换成MCH单板中第一IPMI接口控制器支持的数据格式,并将格式转换后的数据发送给所述第一IPMI接口控制器。
  12. 根据权利要求10或11所述的方法,其中,所述MCH单板对故障数据进行处理,包括:
    所述MCH单板中的第一IPMI接口控制器接收到AMC单板中第二IPMI接口控制器发送的故障数据后,对所述故障数据进行译码,将所述故障数据转换成MCH单板中第一CPU控制单元要求的数据格式,将格式转换后的数据发送给所述第一CPU控制单元;第一CPU控制单元接收到第一IPMI接口控制器发送的故障数据后,将所述故障数据按照MCH单板中的第二网络接口支持的数据格式进行译码,对译码后的故障数据进行打包,并发送给第二网络接口。
  13. 根据权利要求10所述的方法,其中,所述MCH单板将处理后的故障数据上报网络管理中心,包括:
    MCH单板中的第二网络接口通过网络管理中心的第一网络接口将处理后的故障数据上报网络管理中心。
  14. 一种远程设备控制系统,所述系统包括:网络管理中心和远程设备;其中,
    所述网络管理中心,配置为通过与远程设备之间的IP通道和远程设备内部的IPMB通道向远程设备发送控制指令;
    所述远程设备,配置为接收网络管理中心发送的控制指令,并根据所述控制指令执行相应操作。
  15. 根据权利要求14所述的远程控制系统,其中,所述远程设备包括:MCH单板及AMC单板;其中,
    所述MCH单板,配置为接收来自网络管理中心的控制指令,并通过自身与AMC单板之间的IPMI通道将所述控制指令发送至AMC单板;
    所述AMC单板,配置为接收MCH单板发送的控制指令,并根据所述控制指令执行相应操作。
  16. 根据权利要求15所述的系统,其中,所述MCH单板包括:第一IPMI接口控制器,所述AMC单板包括:第二IPMI接口控制器;
    所述远程设备内部的IPMB通道为所述MCH单板中第一IPMI接口控制器与所述AMC单板中第二IPMI接口控制器之间的通道。
  17. 一种远程设备控制方法,所述方法包括:
    网络管理中心生成控制指令;
    所述网络管理中心通过自身与远程设备之间的IP通道和远程设备内部的IPMB通道向远程设备发送控制指令。
  18. 根据权利要求17所述的方法,其中,所述IPMB通道是指远程设备内部MCH单板上的第一IPMI接口控制器与AMC单板上的第二IPMI接口控制器之间的数据通道。
  19. 一种计算机存储介质,所述存储介质包括一组计算机可执行指 令,所述指令用于执行权利要求8-13任一项所述的故障数据获取方法。
  20. 一种计算机存储介质,所述存储介质包括一组计算机可执行指令,所述指令用于执行权利要求17-18任一项所述的远程设备控制方法。
PCT/CN2015/076573 2014-11-19 2015-04-14 一种故障数据获取系统和远程设备控制系统及其对应方法 WO2016078302A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410665598.6 2014-11-19
CN201410665598.6A CN105610595B (zh) 2014-11-19 2014-11-19 一种故障数据获取系统和远程设备控制系统及其对应方法

Publications (1)

Publication Number Publication Date
WO2016078302A1 true WO2016078302A1 (zh) 2016-05-26

Family

ID=55990141

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/076573 WO2016078302A1 (zh) 2014-11-19 2015-04-14 一种故障数据获取系统和远程设备控制系统及其对应方法

Country Status (2)

Country Link
CN (1) CN105610595B (zh)
WO (1) WO2016078302A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116450692A (zh) * 2023-06-06 2023-07-18 山东浪潮科学研究院有限公司 一种数据库故障排查方法,装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1983975A (zh) * 2006-05-25 2007-06-20 华为技术有限公司 高级电信计算架构机框管理系统及服务器远程控制的方法
CN101001169A (zh) * 2006-01-10 2007-07-18 英业达股份有限公司 应用在具有多个服务单元的电子设备中的数据传送系统
CN101394301A (zh) * 2007-09-21 2009-03-25 华为技术有限公司 小型电信和计算通用硬件平台系统、装置及其通信方法
CN101902491A (zh) * 2009-05-26 2010-12-01 深圳市汉普电子技术开发有限公司 一种远程管理系统和控制装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642101A (zh) * 2004-01-15 2005-07-20 英业达股份有限公司 全程远程控制系统及方法
US20060106968A1 (en) * 2004-11-15 2006-05-18 Wooi Teoh Gary C Intelligent platform management bus switch system
US20070094426A1 (en) * 2005-10-24 2007-04-26 Aten International Co., Ltd. KVM switch supporting IPMI communications with computing devices
KR100788896B1 (ko) * 2005-12-08 2007-12-27 한국전자통신연구원 다중모드 통신장치 및 그의 운용정보 수집방법
CN201467145U (zh) * 2009-05-26 2010-05-12 深圳市汉普电子技术开发有限公司 一种远程管理系统和控制装置
CN101719089A (zh) * 2009-10-30 2010-06-02 曙光信息产业(北京)有限公司 分布式集群的远程管理方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001169A (zh) * 2006-01-10 2007-07-18 英业达股份有限公司 应用在具有多个服务单元的电子设备中的数据传送系统
CN1983975A (zh) * 2006-05-25 2007-06-20 华为技术有限公司 高级电信计算架构机框管理系统及服务器远程控制的方法
CN101394301A (zh) * 2007-09-21 2009-03-25 华为技术有限公司 小型电信和计算通用硬件平台系统、装置及其通信方法
CN101902491A (zh) * 2009-05-26 2010-12-01 深圳市汉普电子技术开发有限公司 一种远程管理系统和控制装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116450692A (zh) * 2023-06-06 2023-07-18 山东浪潮科学研究院有限公司 一种数据库故障排查方法,装置、设备及存储介质
CN116450692B (zh) * 2023-06-06 2023-08-29 山东浪潮科学研究院有限公司 一种数据库故障排查方法,装置、设备及存储介质

Also Published As

Publication number Publication date
CN105610595A (zh) 2016-05-25
CN105610595B (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
US10863386B1 (en) State machine handling at a proxy node in an ethernet-based fronthaul network
CN104965727B (zh) 一种重启服务器的方法及装置
CN109639534B (zh) 一种测试网络传输性能的方法、装置及计算机存储介质
WO2018001326A1 (zh) 故障信息获取方法及装置
CN105052076B (zh) 一种基于云计算的网元管理系统及网元管理方法
CN108563455A (zh) 一种k-ux操作系统上中间件部署方法、系统及设备
CN102387044A (zh) 一种对通信网络进行测试方法
CN111049690B (zh) 设备故障监测处理方法、装置、设备及存储介质
CN110620685A (zh) 一种上报设备异常的方法及装置
CN102082689B (zh) 使用异步轮询方式产生设备告警信息的方法
TWI448975B (zh) 應用於影像監控平台的分散式運算系統
CN105071986B (zh) 一种监控系统运行状态的方法
WO2016082509A1 (zh) 一种检测标签交换路径连通性的方法及装置
WO2016078302A1 (zh) 一种故障数据获取系统和远程设备控制系统及其对应方法
WO2015154588A1 (zh) 一种串口信息传递方法、单板设备和公用单板
CN104348645A (zh) 服务器和服务器传送数据的方法
CN105337781A (zh) 网络管理系统、方法及网络系统
CN105959183A (zh) 一种集中配置管理多工位视觉检测方法以及系统
WO2016065752A1 (zh) 一种链路状态的检测方法、设备和存储介质
CN109981394B (zh) 基于增强型can总线协议分析仪的通信方法和装置
CN113346974A (zh) 用于时钟同步的方法、设备、通信系统和存储介质
CN106713031B (zh) 一种异常自处理的智能网管系统
CN108615326B (zh) 一种对消防设备进行联网监控的方法及系统
US20140032746A1 (en) Methods for managing network elements within a network environment and devices thereof
CN105323098B (zh) 一种告警消息处理方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15860785

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15860785

Country of ref document: EP

Kind code of ref document: A1