WO2009052741A1 - Système de microarchitecture informatique pour les télécommunications et procédé pour sa gestion de fiabilité - Google Patents

Système de microarchitecture informatique pour les télécommunications et procédé pour sa gestion de fiabilité Download PDF

Info

Publication number
WO2009052741A1
WO2009052741A1 PCT/CN2008/072689 CN2008072689W WO2009052741A1 WO 2009052741 A1 WO2009052741 A1 WO 2009052741A1 CN 2008072689 W CN2008072689 W CN 2008072689W WO 2009052741 A1 WO2009052741 A1 WO 2009052741A1
Authority
WO
WIPO (PCT)
Prior art keywords
fru
information device
data
fru information
carrier board
Prior art date
Application number
PCT/CN2008/072689
Other languages
English (en)
Chinese (zh)
Inventor
Qingyin Fang
Qiangzhi Xia
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009052741A1 publication Critical patent/WO2009052741A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure

Definitions

  • the present invention relates to the field of communication technologies, and in particular to a small telecommunications and computing hardware platform architecture (Micro Teacommunica t ions Computing Archi tecture, MicroTCA) system and a reliability management method.
  • a small telecommunications and computing hardware platform architecture Micro Teacommunica t ions Computing Archi tecture, MicroTCA
  • MicroTCA is a small telecom and computing common hardware platform architecture developed by the PCI Indus tr ia l Computer Manufacturers Group (PICMG). MicroTCA uses the Advanced Mezzanine Card (AMC) to build the system. The hot-swappable AMC can be plugged directly into the MicroTCA's backplane. MicroTCA is primarily targeted at low-end, cost-sensitive, telecommunications or computing applications that require small physical size. The main applications include wireless base stations, routers, media gateways, and more.
  • the MicroTCA base specification name is MicroTCA. 0, in which the frame structure, management, power supply, heat dissipation, interconnection, etc. of the Mi croTCA are defined.
  • AMC is a universal mezzanine card defined by the PICMG organization that supports hot swapping.
  • the specific types include digital signal processing (DSP) AMC, central processing unit (CPU) AMC, network processor (NP) AMC, interface AMC, storage AMC, etc. .
  • DSP digital signal processing
  • CPU central processing unit
  • NP network processor
  • interface AMC storage AMC
  • storage AMC storage AMC
  • the AMC module can be directly plugged into the backplane of the MicroTCA for application to form the MicroTCA system.
  • the AMC specification includes the AMC. X-series standard specification, which defines the AMC's architecture, management, power, cooling, interconnection, and switching network recommendations.
  • IPMI Inte ll igent Platform Management Interface
  • IPMB Intelligent Platform Management Bus
  • MMC MicroTCA bearer management controller
  • EMMC enhanced management controller
  • MCH MicroTCA switch control module
  • a basic MicroTCA system supports a maximum of 12 AMCs and a maximum of 2 MCHs.
  • the two supported MCHs can be redundant backup relationships.
  • FIG. 1 is a schematic diagram of the connection of the FRU information device of the MicroTCA.0 specification carrier board.
  • each MCMC accesses a bearer FRU information device through an independent I 2 C, and configures the system device by using the FRU data of the FRU information device of the bearer.
  • the system device may include an MCH, an AMC, a power supply unit, and a fan unit.
  • the bearer FRU information device can be implemented as a separate physical entity by a non-volatile memory fixed to the MicroTCA backplane.
  • MCMC1 accesses its corresponding carrier FRU information device 1 through its dedicated channel I 2 C1
  • MCMC 2 accesses its corresponding 7-carrier FRU information device 2 through its dedicated channel 1 2 C 2 .
  • the FRU storage information describes the capacity of each port in the AMC slot, and the information stored in the FRU information device of the bearer board describes the capability of each port on the backplane.
  • the MCH slot is described in the FRU storage information of the MCMC. Bit per port capability. By comparing the port capabilities of these resource information, the carrier board manager determines whether the AMC or MCH star port is enabled. The bearer manager and the MMC on the AMC or the MCMC on the MCH pass the corresponding port capability information to ensure that only compatible ports can be enabled.
  • the FRU data stored by the carrier board FRU information device includes Mi croTCA carrier board attributes, such as the backplane connection, AMC power-on sequence, and the storage information reflects the ability of the MicroTCA carrier board to manage the AMC board.
  • the carrier FRU information device is external to the MCMC and is connected to the MCMC through a dedicated bus.
  • the Mi croTCA chassis takes into account that each FMC information device with the MCMC and the carrier board is connected through the I 2 C bus.
  • FIG. 1 is a schematic diagram of the failure of the FRU information device of the MCH access carrier board of the MicroTCA. 0 specification.
  • the MCH 1 cannot manage the bearer FRU information device 1 .
  • the system will face two problems: First, the system turnover is frequently risky. If the MicroTCA system needs to work normally, MCH2 must start the active/standby switchover action, activate MCH2, and MCH2 to take over the work of MCH1. MCH2 accesses the FRU information device 2 through the dedicated I 2 C bus to take over the management work, and control the AMC board to be normal. Powering on and off and performing E-Keying management. This switching trigger increases the frequency and risk of active/standby switching.
  • the system has long-term faulty operation risks.
  • the MCH1 cannot use the valid data of the FRU information device 2 corresponding to the MCH2 in time to synchronize the content of the FRU information device 1 corresponding to the MCH1, and the FRU information device FRU.
  • the information device 1 failure cannot be repaired in time, and the system is at risk of running with a fault.
  • the failure occurs between the carrier FRU information device 2 and the MCMC 2, the above problem also exists.
  • the MCH and the FRU information device of the bearer board are connected through only one dedicated I 2 C interface. Therefore, the FRU management bus architecture defined by the MicroTCA specification may be inconsistent with the information of the FRU information device of the bearer board.
  • the problem of over-loading is too heavy.
  • the information synchronization failure will cause the MCH to lose control of the AMC management, and the system cannot properly configure and manage the AMC.
  • the switching of the MCH depends on the corresponding FRU information equipment of the carrier board, which reduces the reliability of the system.
  • the embodiments of the present invention provide a small-scale telecommunications and computing general hardware platform architecture system and a reliability management method to ensure normal configuration and management of system equipment due to information synchronization failure.
  • a method for reliability management of a MiTC system is provided in the embodiment of the present invention, where the MiTC system includes a MiTCTC bearer management controller, a main bearer FRU information device, and a backup carrier FRU information device, where the method includes :
  • the FRU information device of the primary carrier board Determining that the FRU information device of the primary carrier board is not in a position or is faulty, the FRU information device of the standby carrier board is in place, and the FRU data of the FRU information device of the standby carrier board is successfully verified, and the standby carrier board FRU is utilized.
  • the FRU data of the information device is configured and processed.
  • the system of the present invention provides a MicroTCA system, which includes: an MCMC, a main carrier FRU information device, and a backup carrier FRU information device, where the MCMC is connected to the FRU information device of the primary carrier board and the FRU information device of the backup carrier board, respectively.
  • the primary carrier FRU information device is configured to provide FRU data to the MCMC when the primary carrier FRU information device is operating normally;
  • the standby carrier FRU information device is configured to provide FRU data to the MCMC when the primary carrier board FRU information device is not in place or fails;
  • the MCMC is configured to acquire FRU data, and perform configuration processing by using the acquired FRU data.
  • a Mi croTCA bearer management controller includes:
  • a data acquisition unit configured to acquire FRU data from the primary carrier FRU information device when the primary carrier FRU information device is running normally; when the primary carrier FRU information device is absent or fails, the data acquisition unit is configured to: The FRU information device of the carrier board acquires FRU data;
  • a configuration unit is configured to perform configuration processing by using the acquired FRU data.
  • the MCH corresponding to the FRU information device of the primary carrier board fails, the MCH does not need to start a complex active/standby switching process, but only needs to access the FRU information device of the standby carrier board to obtain the correct FRU data, and then Realize the normal configuration and management of system equipment.
  • FIG. 1 is a schematic diagram of a FRU information device connection of a Mi croTCA. 0 specification bearer board in the prior art
  • FIG. 2 is a schematic diagram of a FRU information device fault of the MCH access bearer board for the MicroTCA. 0 specification shown in FIG. 1;
  • FIG. 3 is a schematic structural diagram of a Mi croTCA. 0 system according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of an MCMC according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for implementing reliability according to an embodiment of the present invention.
  • the system equipment when it is determined that the primary carrier FRU information device is not in place or fails, the system equipment is configured by using the FRU data of the standby carrier FRU information device.
  • the system device may include an MCH, an AMC, a power supply unit, and a fan unit.
  • determining whether the primary carrier FRU information device is faulty may be implemented as follows: when the primary carrier FRU information device is in place, but the FRU data of the primary carrier FRU information device cannot be read, or the primary carrier FRU is When the information saved by the information device is unsuccessful, it is determined that the FRU information device of the primary carrier board is faulty.
  • the FRU data saved by the primary carrier FRU information device is updated by using the data of the standby carrier FRU information device, it may be further determined whether the standby FRU storage device is in place. . When the standby FRU storage device is in place, and the read data is successful and the read data is successfully verified, the FRU data saved by the standby carrier FRU information device is obtained. Thereafter, the FRU data saved by the primary bearer FRU information device is updated by using the data of the standby carrier FRU information device.
  • the system device can be directly configured by using the FRU data of the primary carrier FRU information device.
  • the user system may be prompted to fail.
  • the FRU data saved by the primary bearer FRU information device may be updated by using FRU data of the standby carrier FRU information device.
  • the system of the embodiment of the present invention includes: an MCMC, a main carrier FRU information device, and a backup carrier FRU information device, such as a FRU information device 1 as a primary carrier FRU information device, and a carrier FRU information device.
  • a FRU information device 1 as a primary carrier FRU information device
  • a carrier FRU information device such as a carrier FRU information device 1 as a primary carrier FRU information device, and a carrier FRU information device.
  • 2 is a FRU information device of the standby carrier board
  • the MCMC is respectively connected to the FRU information device of the primary carrier board and the FRU information device of the backup carrier board.
  • the primary carrier FRU information device is configured to store FRU data, and provide FRU data to the MCMC during normal operation;
  • the backup carrier FRU information device is configured to store FRU data, where the primary carrier board FRU data is provided to the MCMC when the FRU information device is not in place or fails;
  • the MCMC is configured to acquire FRU data, and perform configuration processing by using the acquired FRU data.
  • I 2 C1 is MCMC1 FRU information to the carrier plate apparatus 1 dedicated I 2 C-channel
  • I 2 C4 is MCMC2 FRU information to the carrier plate 2 apparatus dedicated I 2 C-channel.
  • the MC2 is added to the I 2 C channel I 2 C2 of the FRU information device 2 of the bearer board, and the I 2 C2 shown by the dashed line in FIG. 3 is used as an access channel for the MCMC1 to access the FRU information device 2 of the bearer.
  • the MCMC2 is added to the I 2 C channel I 2 C3 of the FRU information device 1 of the bearer board, and the I 2 C3 shown by the dashed line in FIG. 3 serves as an access channel for the MCMC 2 to access the FRU information device 1 of the bearer board.
  • the MCMC1 accesses its corresponding FRU device carrier FRU information device 1 through the dedicated channel I 2 C1, and accesses its corresponding carrier FRU device carrier FRU information device 2 through the dedicated channel I 2 C2; likewise, the MCMC 2 passes the dedicated channel.
  • I 2 C3 access its corresponding carrier plate FRU device carrier plate FRU information equipment 1
  • I 2 C4 access its corresponding carrier plate carrier plate apparatus FRU FRU information device 2 through a dedicated channel.
  • the MCMC1 on the left side of Figure 3 is the main board, and the FRU information equipment 1 corresponding to the dedicated I 2 C channel I 2 C1 is the main FRU storage device.
  • the side MCMC2 is a standby board, and the carrier board FRU information device 2 corresponding to the dedicated I 2 C channel I 2 C4 is a standby FRU storage device.
  • the MCMC shown in FIG. 3 is connected to the FRU information device of the carrier board through the I 2 C bus, and can also be connected.
  • the MCMC may include: a data acquisition unit 42 and a configuration unit 43.
  • the data obtaining unit 42 is configured to acquire FRU data from the primary carrier FRU information device when the primary carrier FRU information device is running normally; when the primary carrier FRU information device is not in place or fails,
  • the FRU information device of the standby carrier board acquires FRU data;
  • the configuration unit 43 is configured to perform configuration processing by using the acquired FRU data.
  • the MCMC may include: a first detecting unit 41, configured to detect whether the FRU information device of the primary carrier board is operating normally.
  • the MCMC may further include: a second detecting unit 44, configured to detect, when the primary carrier FRU information device is absent or fails, detecting whether the standby carrier FRU information device is in place or fails, When the standby carrier FRU information device is in or out of failure, the data acquiring unit 42 is instructed to acquire FRU data from the standby carrier FRU information device. Therefore, the data acquisition unit 42 acquires FRU data from the standby carrier FRU information device when the standby carrier FRU information device is in place or has not failed.
  • the MCMC may further include: a synchronization update unit 45, configured to: when the primary carrier FRU information device is not in place or fails, use the FRU data of the standby carrier FRU information device to update the primary carrier FRU information device to save FRU data.
  • a synchronization update unit 45 configured to: when the primary carrier FRU information device is not in place or fails, use the FRU data of the standby carrier FRU information device to update the primary carrier FRU information device to save FRU data.
  • the MCMC may further include: an alarm unit, configured to prompt the user system to malfunction when the FRU information device of the standby carrier board is not in place or fails.
  • the MCMC can separately take different measures according to different states of the FRU information equipment of the active and standby carrier boards:
  • the MCMC1 When the primary FRU storage device is in place, the MCMC1 reads the primary FRU data successfully through the primary FRU dedicated channel I 2 C1. When the data verification is correct, the MCMC1 accepts the storage data of the primary FRU storage device, and configures the MicroTCA system by using the configuration file. Configure ports on the AMC board in the system to implement power-on and power-off management.
  • the MCMC1 fails to read the primary FRU storage device data through the primary FRU dedicated channel I 2 C1.
  • the MCMC1 passes the standby FRU storage device.
  • the dedicated channel I 2 C2 reads data from the alternate FRU storage device and verifies the stored information. If the verification is successful, the alternate FRU storage device data is used. If the backup data fails to be obtained, the MCMC board gives a severe alarm indication, and the self-test fails. The error message is output: "The carrier board FRU data is invalid.”
  • the MCMC1 When the primary FRU storage device is in place, the MCMC1 reads the data successfully through the primary FRU dedicated channel I 2 C1, but the parity data does not pass. When the standby FRU storage device is in place, the MCMC1 reads the data from the standby FRU storage device through the I 2 C2. And check it out. If the MCMC1 is successful, the MCMC1 accepts the storage data of the standby FRU storage device.
  • the configuration file is used to configure the MicroTCA system to configure the ports on the AMC board in the system to implement power-on and power-off management.
  • the primary FRU data is overwritten by the primary FRU dedicated channel I 2 C1 using the alternate data. If the backup data fails to be obtained, the MCMC board gives a severe alarm indication, and the self-test fails.
  • the error message is output: "The carrier board FRU data is invalid.”
  • MCMC1 When the primary FRU storage device is in place, MCMC1 fails to read data through the primary FRU dedicated channel I 2 C1. When the standby FRU storage device is in place, MCMC1 reads data from the standby FRU storage device through I 2 C2 and performs verification. If the MCMC1 is successful, the MCMC1 accepts the storage data of the standby FRU storage device.
  • the configuration file is used to configure the MicroTCA system to configure the ports on the AMC board in the system to implement power-on and power-off management. If the backup data fails to be obtained, the MCMC board gives a severe alarm indication, and the self-test fails. The error message is output: "The carrier board FRU data is invalid.”
  • the MCMC1 When the primary FRU storage device is not in place and the standby FRU storage device is in place, the MCMC1 reads data from the alternate FRU storage device through I 2 C2 and performs verification. If successful, use alternate FRU storage device data. If the backup data fails to be obtained, the MCMC board gives a severe alarm indication, and the self-test fails. The error message is output: "The carrier board FRU data is invalid.”
  • the MCMC board gives a severe alarm indication, and the self-test fails.
  • the error message is output: "The carrier board FRU data is invalid.”
  • Step 501 Determine whether the primary carrier FRU information device is in place. If it is in place, execute step 502. Otherwise, go to step 504.
  • Step 502 MCMC1 reads the primary carrier FRU information device through the primary FRU dedicated channel I 2 C 1 If the reading is successful, step 503 is performed; otherwise, step 504 is performed.
  • Step 503 The MCMC1 checks the read FRU data. If the verification is correct, the MCMC1 accepts the FRU data, and performs step 509. Otherwise, step 504 is performed.
  • Step 504 Determine whether the FRU information device is in place on the standby carrier board. If yes, execute step 505. Otherwise, go to step 508.
  • Step 505 The MCMC1 reads the FRU data of the FRU information device of the bearer board through the standby FRU dedicated channel I 2 C. If the reading is successful, step 506 is performed; otherwise, step 508 is performed.
  • Step 506 The MCMC1 checks the FRU data of the read FRU information device of the standby carrier board. If the verification is correct, the MCMC1 accepts the FRU data of the FRU information device of the standby carrier board, and performs step 509. Otherwise, step 508 is performed.
  • Step 507 Determine whether the FRU data of the FRU information device of the read carrier board is successful. If successful, the MCMC1 accepts the FRU data of the FRU information device of the standby carrier board, and performs step 509. If not, the MCMC1 accepts the FRU information device of the primary bearer board. The FRU data of the FRU information device of the primary carrier board is synchronized with the FRU information device of the standby carrier board, and step 509 is performed.
  • the carrier board FRU information device data synchronization is realized by IPMB_L, CAN, serial port and other buses.
  • Step 508 Determine that the FRU information device of the standby carrier board is not in place or fails, and return to step 501.
  • the MCH does not need to start a complex active/standby switchover process, which increases the system switching load, but only needs to be added to the dedicated I 2 C channel of the board to access the board carrier board FRU information device. It reduces the risk of system switching load and switching, and improves the reliability of the MicroTCA system.
  • the MCMC After the FMC data stored in the FRU information device of the bearer board is verified by the MCMC, the MCMC first analyzes the FRU record of the bearer board in the FRU information device of the bearer board. From the composite record (Mul ti Record) The "Activity Activation and Power Management Record" is extracted, and according to the configuration parameter of "FRU Act ivat ion and Power Descriptor", whether to activate the bearer is determined. Board FRU information device. If the configuration parameter is to allow activation, the MCMC sends a Set FRU Activation (Activate FRU) command to activate the bearer FRU information device by using the IPMB command, and the bearer FRU information device enters an active state.
  • Activate FRU Set FRU Activation
  • the MCMC compares the capabilities of each port in the FRU resource information in the MCH and AMC boards, and determines whether the AMC or MCH star port is enabled.
  • the bearer board manager communicates the corresponding port capability information with the MMC module on the AMC or the MCMC module on the MCH. Ensure that only compatible ports are enabled to open.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Hardware Redundancy (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention porte sur un procédé de gestion de fiabilité d'un système de microarchitecture informatique pour les télécommunications (MicroTCA). Le système MicroTCA comprend au moins le contrôleur de gestionnaire de porteuse MicroTCA, le dispositif d'informations FRU de carte porteuse active et le dispositif d'informations FRU de carte porteuse au repos. Le procédé consiste à : déterminer si le dispositif d'informations FRU de carte porteuse active n'est pas à sa place ou, en cas de défaillance, si le dispositif d'informations FRU de carte porteuse au repos est à sa place, vérifier les données FRU du dispositif d'informations FRU de carte porteuse au repos avec succès, et utiliser les données FRU du dispositif d'informations FRU de carte porteuse au repos pour réaliser l'opération de configuration. L'invention porte également sur un système MicroTCA et un contrôleur de gestionnaire de porteuse MicroTCA. Dans les modes de réalisation de l'invention, en cas d'une défaillance du dispositif d'informations FRU de carte porteuse, il n'est pas nécessaire de lancer une opération de commutation complexe entre carte active et carte au repos, il suffit d'obtenir les données FRU correctes par accès au dispositif d'informations FRU de carte porteuse au repos, et en outre la configuration normale et la gestion du dispositif de système peuvent être réalisées.
PCT/CN2008/072689 2007-10-16 2008-10-15 Système de microarchitecture informatique pour les télécommunications et procédé pour sa gestion de fiabilité WO2009052741A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101631951A CN101415127B (zh) 2007-10-16 2007-10-16 小型电信和计算通用硬件平台架构系统及可靠性管理方法
CN200710163195.1 2007-10-16

Publications (1)

Publication Number Publication Date
WO2009052741A1 true WO2009052741A1 (fr) 2009-04-30

Family

ID=40579083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072689 WO2009052741A1 (fr) 2007-10-16 2008-10-15 Système de microarchitecture informatique pour les télécommunications et procédé pour sa gestion de fiabilité

Country Status (2)

Country Link
CN (1) CN101415127B (fr)
WO (1) WO2009052741A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108462529A (zh) * 2018-04-27 2018-08-28 上海欣诺通信技术股份有限公司 主备板卡切换方法、光传送网络设备及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102385566B (zh) * 2010-09-01 2016-05-04 研祥智能科技股份有限公司 一种基于mtca平台的热插拔方法及mtca平台
CN101958806A (zh) * 2010-10-12 2011-01-26 艾诺通信系统（苏州）有限责任公司 一种实现MicroTCA系统MCH网口备份的模块及其方法
CN102325040A (zh) * 2011-06-27 2012-01-18 艾诺通信系统（苏州）有限责任公司 一种基于MicroTCA系统的电源管理方法
CN103838639B (zh) * 2012-11-23 2018-04-27 华为技术有限公司 一种恢复虚拟磁盘元数据的方法、装置及系统
CN105511921A (zh) * 2015-12-09 2016-04-20 浪潮电子信息产业股份有限公司 一种保障fru中写入资产编码为大写的方法
CN111177043B (zh) * 2019-12-26 2021-07-06 苏州浪潮智能科技有限公司 加快读取现场可更换单元信息的方法、系统、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1393748A (zh) * 2001-06-22 2003-01-29 华为技术有限公司 主备电路倒换设备及其方法
CN1756107A (zh) * 2004-09-28 2006-04-05 华为技术有限公司 一种实现单板倒换的方法
WO2007089993A2 (fr) * 2006-01-31 2007-08-09 Emerson Network Power - Embedded Computing, Inc. Procédé de vérification de panne latente dans un réseau de gestion

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1393748A (zh) * 2001-06-22 2003-01-29 华为技术有限公司 主备电路倒换设备及其方法
CN1756107A (zh) * 2004-09-28 2006-04-05 华为技术有限公司 一种实现单板倒换的方法
WO2007089993A2 (fr) * 2006-01-31 2007-08-09 Emerson Network Power - Embedded Computing, Inc. Procédé de vérification de panne latente dans un réseau de gestion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PICMG@ MTCA.0 R1.0 MICRO TELECOMMUNICATIONS COMPUTING ARCHITECTURE SHORT FORM SPECIFICATION, 21 September 2006 (2006-09-21), pages 8 - 10, 21-2 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108462529A (zh) * 2018-04-27 2018-08-28 上海欣诺通信技术股份有限公司 主备板卡切换方法、光传送网络设备及存储介质
CN108462529B (zh) * 2018-04-27 2023-12-19 上海欣诺通信技术股份有限公司 主备板卡切换方法、光传送网络设备及存储介质

Also Published As

Publication number Publication date
CN101415127B (zh) 2011-07-27
CN101415127A (zh) 2009-04-22

Similar Documents

Publication Publication Date Title
US9734093B2 (en) Management of secured storage devices in an information handling system
WO2009052741A1 (fr) Système de microarchitecture informatique pour les télécommunications et procédé pour sa gestion de fiabilité
US8707290B2 (en) Firmware update in an information handling system employing redundant management modules
US9189349B2 (en) Distributed blade server system, management server and switching method
TW202041061A (zh) 用於組態漂移偵測及補救之系統及方法
US20070220301A1 (en) Remote access control management module
CN104598329A (zh) 一种基于rmc管理的自动bmc故障解决方法
CN101483540A (zh) 一种高端数据通信设备中的主备倒换方法
US10862900B2 (en) System and method for detecting rogue devices on a device management bus
JP5515766B2 (ja) 情報処理装置、情報処理装置のハードウェア設定方法及びそのプログラム
CN106936616A (zh) 备份通信方法和装置
CN114116280B (zh) 交互式bmc自恢复方法、系统、终端及存储介质
CN111585835B (zh) 一种带外管理系统的控制方法、装置和存储介质
CN105549696B (zh) 具有机箱管理功能的机架式服务器系统
CN117992270B (zh) 一种内存资源管理系统、方法、装置、设备及存储介质
CN112868013B (zh) 经由边带接口恢复场域可程序门阵列固件的系统及方法
TW200301418A (en) Computer system with dedicated system management buses
CN116483613B (zh) 故障内存条的处理方法及装置、电子设备及存储介质
US8522075B2 (en) Storage system having storage devices for storing data and control devices for controlling the storage devices
CN113076210A (zh) 服务器故障诊断结果通知方法、系统、终端及存储介质
CN111352662A (zh) 一种服务器启动顺序控制方法、系统、终端及存储介质
WO2021238579A1 (fr) Procédé de gestion de disque dur sata au moyen d'un système de stockage, et système de stockage
CN114124803B (zh) 设备管理方法、装置、电子设备及存储介质
CN100375961C (zh) 应用于刀锋伺服系统的错误检测方法与装置
CN115309577A (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: 08843276

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: 08843276

Country of ref document: EP

Kind code of ref document: A1