CN111338701A - Network equipment starting method and network equipment - Google Patents

Network equipment starting method and network equipment Download PDF

Info

Publication number
CN111338701A
CN111338701A CN202010116639.1A CN202010116639A CN111338701A CN 111338701 A CN111338701 A CN 111338701A CN 202010116639 A CN202010116639 A CN 202010116639A CN 111338701 A CN111338701 A CN 111338701A
Authority
CN
China
Prior art keywords
microsystem
backup
primary
software
area
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202010116639.1A
Other languages
Chinese (zh)
Inventor
祝国胜
王艳波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bangyan Technology Co ltd
Original Assignee
Bangyan Technology 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 Bangyan Technology Co ltd filed Critical Bangyan Technology Co ltd
Priority to CN202010116639.1A priority Critical patent/CN111338701A/en
Publication of CN111338701A publication Critical patent/CN111338701A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4416Network booting; Remote initial program loading [RIPL]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a network equipment starting method and network equipment, wherein the method comprises the following steps: starting a primary microsystem; the primary micro system loads a secondary micro system, and the secondary micro system is used for loading an operating system, service software and system software backup. The network equipment is started by matching the primary microsystem and the secondary microsystem, the primary microsystem is not changed, modified and upgraded and only used for driving necessary hardware equipment, the secondary microsystem can start the network equipment under the guidance of the primary microsystem, and the primary microsystem can guide the secondary microsystem to upgrade or load a backup system on line under the condition that the secondary microsystem fails, so that the software failure probability of the network equipment is reduced.

Description

Network equipment starting method and network equipment
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a network device starting method and a network device.
Background
The network device is a special or embedded device with high reliability requirement, and relates to a network such as an enterprise private network or a large-scale operator. With the rapid development of networks, network equipment operators have higher and higher requirements on equipment, and the continuous updating of the requirements for application causes the upgrading of network equipment software to become more and more frequent, so that higher requirements are provided for the upgrading starting of the equipment.
The network device usually uses bootloader (e.g. uboot) software to load and boot the startup operation of the device, and at the same time, when the device leaves a factory, a software package such as bootloader is programmed onto a storage device such as a FLASH memory (FLASH) through special tools such as JTAG. The probability of software errors is higher and higher along with the frequency of software updating; meanwhile, because the memory devices such as FLASH have unavoidable potential risks such as read-write errors, the probability that the solidified software such as bootloader is damaged is higher and higher. At present, most embedded devices exist in the form of bootloaders, kernel (linux) and service software packages, and therefore once the bootloaders of the software are abnormal, the whole device cannot be started to run. The consequence is that the device cannot be recovered for a long time, and at the same time, high software maintenance cost is brought.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art. Therefore, the invention provides a network equipment starting method which can reduce the failure rate of system software operation in the starting process of network equipment and reduce the maintenance cost.
The invention also provides network equipment.
The invention also provides a computer readable storage medium.
In a first aspect, an embodiment of the present invention provides a network device starting method: the method comprises the following steps:
starting a primary microsystem;
the primary microsystem loads a secondary microsystem, and the secondary microsystem loads an operating system and service software.
According to another embodiment of the present invention, a network device starting method includes that a secondary microsystem includes a starting area and a secure backup area, and if the primary microsystem detects that the secondary microsystem is operating normally and the secure backup area of the secondary microsystem has no backup or has a low backup system version, software stored in the starting area is copied to the secure backup area or the secondary microsystem is upgraded remotely.
Further, the method also comprises a backup reloading step: if the primary microsystem cannot load the secondary microsystem, whether backup software exists in the safety backup area or not is detected, if yes, the backup software is copied to the starting area, the primary microsystem is executed again to load the secondary microsystem, and the secondary microsystem loads an operating system and service software.
Further, recording the current system running state by adopting the head zone bit, wherein the system running state comprises the normal starting or the starting failure times of the system.
Further, the method also comprises the step of entering a backup overloading step if the number of failed starting times exceeds a preset value.
In a second aspect, an embodiment of the present invention provides a network device: the method comprises the following steps:
a primary microsystem including a preset device driver, the primary microsystem being configured to load the second microsystem,
and the secondary microsystem is used for starting a preset program of the network equipment so that the network can normally run.
Further, the secondary microsystem comprises a starting area and a safe backup area, and if the primary microsystem detects that the secondary microsystem operates normally and the safe backup area of the secondary microsystem has no backup or has a low backup system version, software stored in the starting area is copied to the safe backup area.
Further, if the primary microsystem cannot load the secondary microsystem, detecting whether backup software exists in the safety backup area, if so, copying the backup software to the starting area, re-executing the primary microsystem to load the secondary microsystem, and loading an operating system and service software by the secondary microsystem.
In a third aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions for causing a computer to execute the network device boot method.
The network equipment starting method of the embodiment of the invention at least has the following beneficial effects: the network equipment is started by matching the primary microsystem and the secondary microsystem, the primary microsystem is not changed, modified and upgraded and only used for driving necessary hardware equipment, the secondary microsystem can start the network equipment under the guidance of the primary microsystem, and the primary microsystem can guide the secondary microsystem to upgrade or load a backup system on line under the condition that the secondary microsystem fails, so that the software failure probability of the network equipment is reduced.
Drawings
Fig. 1 is a flowchart illustrating an embodiment of a network device booting method according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a backup step in an embodiment of a method for starting a network device according to the present invention;
FIG. 3 is a flowchart illustrating a backup reload step in an embodiment of a method for starting a network device according to the present invention;
fig. 4 is a block diagram of a network device according to an embodiment of the present invention.
Detailed Description
The concept and technical effects of the present invention will be clearly and completely described below in conjunction with the embodiments to fully understand the objects, features and effects of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments, and those skilled in the art can obtain other embodiments without inventive effort based on the embodiments of the present invention, and all embodiments are within the protection scope of the present invention.
In the description of the present invention, if an orientation description is referred to, for example, the orientations or positional relationships indicated by "upper", "lower", "front", "rear", "left", "right", etc. are based on the orientations or positional relationships shown in the drawings, only for convenience of describing the present invention and simplifying the description, but not for indicating or implying that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as limiting the present invention. If a feature is referred to as being "disposed," "secured," "connected," or "mounted" to another feature, it can be directly disposed, secured, or connected to the other feature or indirectly disposed, secured, connected, or mounted to the other feature.
In the description of the embodiments of the present invention, if "a number" is referred to, it means one or more, if "a plurality" is referred to, it means two or more, if "greater than", "less than" or "more than" is referred to, it is understood that the number is not included, and if "greater than", "lower" or "inner" is referred to, it is understood that the number is included. If reference is made to "first" or "second", this should be understood to distinguish between features and not to indicate or imply relative importance or to implicitly indicate the number of indicated features or to implicitly indicate the precedence of the indicated features.
Referring to fig. 1, a flowchart of a network device starting method in an embodiment of the present invention is shown. The method specifically comprises the following steps:
s100, starting a primary micro system;
and S200, loading a secondary micro system by the primary micro system, wherein the secondary micro system is used for loading an operating system, service software and system software backup.
The network equipment starting method provided by the embodiment of the invention starts the network equipment through the cooperation of the primary microsystem and the secondary microsystem, the primary microsystem is not changed, modified and upgraded and is only used for driving necessary hardware equipment, the secondary microsystem can start the network equipment under the guidance of the primary microsystem, and the primary microsystem can guide the secondary microsystem to upgrade or load a backup system on line under the condition that the secondary microsystem fails, so that the software failure probability of the network equipment is reduced.
In a specific embodiment, the first-level microsystem is burned on a storage device such as FLASH by a tool such as JTAG at the time of factory shipment, and only supports the required device driver support, such as FLASH and network interface driver. Under normal conditions, the primary microsystem is not changed, modified and upgraded any more (unless major hardware change occurs), so that the fault risk probability caused by upgrading is greatly reduced; the secondary micro-system still bears the function of the general boot software, but the secondary micro-system is not solidified on a device through special tools such as JTAG (joint test action group) and the like any more, on one hand, the secondary micro-system can be upgraded on line through the primary system, and on the other hand, the secondary micro-system can be self-repaired by loading a safe backup through the primary system, so that the problem that the general boot software is burnt or returned to a factory for processing by using special tools such as JTAG and the like when the general boot software.
In one embodiment, the secondary microsystem includes a boot area, a secure backup area, an operating system kernel storage area (kernel) or a software package storage area, and the number and size of the developed storage areas are determined according to actual conditions such as software requirements. If the primary microsystem detects that a secondary microsystem operates normally and a safe backup area of the secondary microsystem does not have backup or a backup system version is low, copying software stored in the boot area to the safe backup area or remotely upgrading the secondary microsystem, and referring to fig. 2, the method specifically comprises the following steps:
s201, starting a primary micro system;
s202, judging whether a secondary system normal mark exists in the safety backup area, recording the current system running state and the current system version number by setting a head zone bit, and if so, entering the step S203;
s203, when judging that the backup software does not exist in the safe backup area or the backup software is too low, entering the step S204, otherwise ending;
s204, backing up the current secondary microsystem to a safe backup area or remotely upgrading the secondary microsystem, and modifying the head zone bit.
In another embodiment, the method further includes a backup reloading step, where if the primary microsystem cannot load the secondary microsystem, it is detected whether backup software exists in the secure backup area, if so, the backup software is copied to the boot area, and the primary microsystem is re-executed to load the secondary microsystem, where the secondary microsystem loads an operating system and service software, specifically referring to fig. 3, the method includes the steps of:
s301, starting a primary micro system;
s302, judging whether the failure restart times of the secondary microsystem exceed a preset value or not, if so, entering the step S303;
s303, judging whether a secondary microsystem backup exists in the safety backup area, if so, entering a step S304, and if not, entering a step S306;
s304, copying the software in the safe backup area to the starting area;
s305, loading a secondary microsystem;
and S306, prompting the loading failure and needing manual intervention and manual upgrading.
The safe backup of the secondary microsystem is only started when the secondary microsystem fails due to various reasons, so that the system can be self-repaired and recovered to normally operate without human intervention.
Referring to fig. 4, the present invention also discloses a network device, including:
a primary microsystem including a preset device driver, the primary microsystem being configured to load the second microsystem,
and the secondary microsystem is used for starting a preset program of the network equipment so that the network can normally run.
In one embodiment, the secondary microsystem includes a boot area and a secure backup area, and if the primary microsystem detects that the secondary microsystem operates normally and the secure backup area of the secondary microsystem has no backup or has a low backup system version, the software stored in the boot area is copied to the secure backup area.
In one embodiment, if the primary microsystem cannot load the secondary microsystem, detecting whether backup software exists in the safe backup area, if so, copying the backup software to the boot area, and re-executing the primary microsystem to load the secondary microsystem, wherein the secondary microsystem loads an operating system and service software.
The invention also discloses a computer-readable storage medium, which stores computer-executable instructions for causing a computer to execute the network equipment starting method.
The embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the present invention is not limited to the above embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present invention. Furthermore, the embodiments of the present invention and the features of the embodiments may be combined with each other without conflict.

Claims (9)

1. A network device boot method, comprising:
starting a primary microsystem;
the primary micro system loads a secondary micro system, and the secondary micro system is used for loading an operating system, service software and system software backup.
2. The method according to claim 1, further comprising a backup step, wherein the secondary microsystem includes a boot area and a secure backup area, and if the primary microsystem detects that the secondary microsystem is operating normally and the secure backup area of the secondary microsystem has no backup or has a low backup system version, software stored in the boot area is copied to the secure backup area or the secondary microsystem is upgraded remotely.
3. The network device booting method of claim 2 further comprising the step of backing up the reload: if the primary microsystem cannot load the secondary microsystem, whether backup software exists in the safety backup area or not is detected, if yes, the backup software is copied to the starting area, the primary microsystem is executed again to load the secondary microsystem, and the secondary microsystem loads an operating system and service software.
4. The network equipment starting method according to claim 2 or 3, characterized in that a header flag is used to record the current system running state, wherein the system running state comprises normal starting or failure times of starting of the system.
5. The method of claim 3, further comprising the step of entering a backup reload step if the number of failed start-ups exceeds a predetermined value.
6. A network device, comprising:
a primary microsystem including a preset device driver, the primary microsystem being configured to load the second microsystem,
and the secondary microsystem is used for starting a preset program of the network equipment so that the network can normally run.
7. The network device of claim 6,
the secondary microsystem comprises a starting area and a safe backup area, and if the primary microsystem detects that the secondary microsystem operates normally and the safe backup area of the secondary microsystem has no backup or the version of the backup system is low, software stored in the starting area is copied to the safe backup area.
8. The network device according to claim 6, wherein if the primary microsystem cannot load the secondary microsystem, detecting whether backup software exists in the secure backup area, if so, copying the backup software to the boot area, and re-executing the primary microsystem to load the secondary microsystem, wherein the secondary microsystem loads an operating system and service software.
9. A computer-readable storage medium having stored thereon computer-executable instructions for causing a computer to perform the network device boot method of any of claims 1 to 5.
CN202010116639.1A 2020-02-25 2020-02-25 Network equipment starting method and network equipment Pending CN111338701A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010116639.1A CN111338701A (en) 2020-02-25 2020-02-25 Network equipment starting method and network equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010116639.1A CN111338701A (en) 2020-02-25 2020-02-25 Network equipment starting method and network equipment

Publications (1)

Publication Number Publication Date
CN111338701A true CN111338701A (en) 2020-06-26

Family

ID=71183675

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010116639.1A Pending CN111338701A (en) 2020-02-25 2020-02-25 Network equipment starting method and network equipment

Country Status (1)

Country Link
CN (1) CN111338701A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897583A (en) * 2020-07-06 2020-11-06 上海中船船舶设计技术国家工程研究中心有限公司 Equipment starting method and embedded equipment

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080263349A1 (en) * 2007-04-20 2008-10-23 Takeaki Ota Booting system, boot program, and method therefor
CN102902556A (en) * 2012-09-06 2013-01-30 深圳市共进电子股份有限公司 Multistage boot load method of embedded equipment
US8752039B1 (en) * 2009-08-19 2014-06-10 Juniper Networks, Inc. Dynamic upgrade of operating system in a network device
CN104915226A (en) * 2015-05-21 2015-09-16 北京星网锐捷网络技术有限公司 Network device software starting method, device and network device
EP3037967A1 (en) * 2014-11-28 2016-06-29 Huawei Technologies Co., Ltd. Fault-tolerant startup method and apparatus and computer system
CN106569842A (en) * 2015-10-09 2017-04-19 中兴通讯股份有限公司 Startup method and device for operating system
CN109976940A (en) * 2017-12-28 2019-07-05 天津创奇业网络技术有限公司 A kind of soft start network equipment
CN110659052A (en) * 2019-09-30 2020-01-07 深圳市九洲电器有限公司 Method and system for updating system software in network equipment and readable storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080263349A1 (en) * 2007-04-20 2008-10-23 Takeaki Ota Booting system, boot program, and method therefor
US8752039B1 (en) * 2009-08-19 2014-06-10 Juniper Networks, Inc. Dynamic upgrade of operating system in a network device
CN102902556A (en) * 2012-09-06 2013-01-30 深圳市共进电子股份有限公司 Multistage boot load method of embedded equipment
EP3037967A1 (en) * 2014-11-28 2016-06-29 Huawei Technologies Co., Ltd. Fault-tolerant startup method and apparatus and computer system
CN104915226A (en) * 2015-05-21 2015-09-16 北京星网锐捷网络技术有限公司 Network device software starting method, device and network device
CN106569842A (en) * 2015-10-09 2017-04-19 中兴通讯股份有限公司 Startup method and device for operating system
CN109976940A (en) * 2017-12-28 2019-07-05 天津创奇业网络技术有限公司 A kind of soft start network equipment
CN110659052A (en) * 2019-09-30 2020-01-07 深圳市九洲电器有限公司 Method and system for updating system software in network equipment and readable storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111897583A (en) * 2020-07-06 2020-11-06 上海中船船舶设计技术国家工程研究中心有限公司 Equipment starting method and embedded equipment

Similar Documents

Publication Publication Date Title
US20080028386A1 (en) Transmission apparatus and method of automatically updating software
US20030051235A1 (en) Method and apparatus for verifying and analyzing computer software installation
KR100952585B1 (en) Method and system for automatic recovery of an embedded operating system
US20080072030A1 (en) Computer System and Method for Updating Program Code
CN111182033B (en) Method and equipment for restoring switch
CN103970564A (en) Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions
CN110780942A (en) System starting method and device, node equipment and computer readable storage medium
CN109032636A (en) A method of UEFI firmware is updated based on encryption certification BMC
US20180322020A1 (en) Backup and recovery of configuration files in management device
CN111338701A (en) Network equipment starting method and network equipment
CN112394965B (en) Battery management system upgrade and operation method, controller, battery management system and storage medium
CN111273928B (en) Bootloader design method for self-upgrading
JP2005284902A (en) Terminal device, control method and control program thereof, host device, control method and control program thereof, and method, system, and program for remote updating
CN112685068A (en) Method for remotely upgrading BOOT image file and computer readable medium
US20100031243A1 (en) Method for updating software of an electronic device, in particular of the release of low-voltage circuit breakers
CN112395130A (en) System backup method and device
CN111897583A (en) Equipment starting method and embedded equipment
EP2354932A1 (en) Computer system, method for booting a computer system, and method for replacing a component
CN116028084A (en) Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform
CN112394656B (en) Method, external device and system for checking program execution of microcontroller
CN114995854A (en) Application program online upgrading method and device, terminal and operation machine
CA2299850C (en) System and method for the management of computer software maintenance
CN110647343A (en) OpenPower server and system deployment method thereof
CN112148531A (en) Dual-core chip and program backup and recovery method thereof
CN111443951A (en) System starting method and system starting device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 518000 2101, No. 100, Zhihe Road, Dakang community, Yuanshan street, Longgang District, Shenzhen, Guangdong

Applicant after: BANGYAN TECHNOLOGY Co.,Ltd.

Address before: 518000 room 901, block B, building 5, Shenzhen software industry base, Nanshan District, Shenzhen City, Guangdong Province

Applicant before: BANGYAN TECHNOLOGY Co.,Ltd.

CB02 Change of applicant information
RJ01 Rejection of invention patent application after publication

Application publication date: 20200626

RJ01 Rejection of invention patent application after publication