CN107070676A - The virtualized management method of the network equipment - Google Patents
The virtualized management method of the network equipment Download PDFInfo
- Publication number
- CN107070676A CN107070676A CN201611032732.4A CN201611032732A CN107070676A CN 107070676 A CN107070676 A CN 107070676A CN 201611032732 A CN201611032732 A CN 201611032732A CN 107070676 A CN107070676 A CN 107070676A
- Authority
- CN
- China
- Prior art keywords
- subsystem
- actual
- main system
- actual subsystem
- message
- 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
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/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Abstract
The invention discloses a kind of virtualized management method of the network equipment, it comprises the following steps：Step one, main system collects the actual subsystem information of the second line of a couplet, and actual subsystem is virtualized on the master system, actual subsystem is turned into the Virtualization Subsystems of main system；Step 2, after the virtualization of actual subsystem is completed, main system carries out webmaster management, monitoring and fault warning to Virtualization Subsystems.The present invention can realize that access device carries out equipment control, fault detect and alarming mechanism in the case of without ip.
Description
Technical field
The present invention relates to a kind of virtualized management method, more particularly to a kind of virtualized management method of the network equipment.
Background technology
Current network conditions are made up of access device, convergence device and nucleus equipment.Access device major responsibility is to provide
The cut-in operation of the network of terminal user, the major responsibility of convergence device is to carry out network convergence work, core to access device
Equipment major responsibility is data is correctly arrived at the destination data distribution and transmission.The wherein quantity phase of access device
It is again very huger than convergence device and nucleus equipment.
With the fast development of internet, the increasing network equipment, which is put into, to be used so that the ipv4 network address
Rapidly consumption, and ipv6 development in relatively slow can not fully substitute the use of ipv4 networks.And access device because
It is very huge for its quantity, become consumption ipv4 main force.
In order to save the use of ipv4 addresses in real network arrangement, many network providers are all abandoned to entering equipment
The distribution of ipv4 addresses is carried out, so as to abandon direct network pipeline access device, so resulting in that many access devices are in can not
The state of webmaster.Thus bring terminal device and break down and can not perceive in time, it is impossible to solve failure in time.So certainly will
The network of end user can be influenceed to experience.
The content of the invention
The technical problems to be solved by the invention are to provide a kind of virtualized management method of the network equipment, and it can be realized
Access device carries out equipment control, fault detect and alarming mechanism in the case of without ip.
The present invention is to solve above-mentioned technical problem by following technical proposals：A kind of virtual management of the network equipment
Method, it is characterised in that it comprises the following steps：
Step one, main system collects the actual subsystem information of the second line of a couplet, actual subsystem is carried out on the master system virtual
Change, actual subsystem is turned into the Virtualization Subsystems of main system；
Step 2, after the virtualization of actual subsystem is completed, main system carries out webmaster management, prison to Virtualization Subsystems
Control and fault warning.
Preferably, the step 2 is after the virtualization of actual subsystem is completed, and main system and actual subsystem are into one
Individual total system gives a network management system, and network management system is directly managed and monitored to actual subsystem.
Preferably, the Virtualization Subsystems be mainly responsible for the actual corresponding configuration information of subsystem of storage, fault message with
And warning information.
Preferably, the network management system management and the actual subsystem of monitoring use following steps：
Step 11：Network management system needs to access actual subsystem, solicited message can be sent to main system, and inform master
System network management system request is actual subsystem；
Step 12：Equipment index during main system is asked according to webmaster determines that request is local or actual subsystem,
Handled if solicited message can be sent on the actual subsystem of native virtualization by actual subsystem；
Step 13：The actual subsystem of virtualization in main system can be to real actual subsystem after receiving processing request
System initiates information request, and acquisition corresponding information returns to main system from real actual subsystem；
Step 14：Actual subsystem detects this earth fault later, it is necessary to be noticed to main system, actual subsystem
Fault message is sent on the Virtualization Subsystems of main system first；
Step 15：Virtualization Subsystems are received after the fault message from true actual subsystem, can pass through main system
Fault message is sent to network management system；
Step 10 six：Fault message with actual subsystem information is sent to network management system by main system.
Preferably, the main system can distribute a globally unique actual Sub-System Number to Virtualization Subsystems.
Preferably, the actual Sub-System Number is the physics in the main system being connected according to actual subsystem with main system
Port numbers are configured, advantage of this is that easily knowing that port hung under the actual subsystem on the master system
On.
Preferably, the main system listens to the hello packet that actual subsystem is sent, by hello packet come really
The annexation that fixed actual subsystem exists and sets up main system between actual subsystem.
Preferably, the annexation set up between main system and actual subsystem uses following steps：
Step 2 11：Actual subsystem periodically sends hello packet, notices the presence of oneself；
Step 2 12：Main system can notice oneself after receiving actual subsystem hello requests to actual subsystem
Through receiving opposite end request, and back message is provided, allow actual subsystem to carry out next step operation；
Step 2 13：Actual subsystem will stop hello packet after the hello packet for receiving main system is responded
, and the request message of the actual subsystem of loading is initiated main system to main system；
Step 2 14：Main system detects main system and actual subsystem after the load request of actual subsystem is received
Between data channel whether normal table；
Step 2 15：Actual subsystem after the configuration message of main system is received can according to configuration message it is corresponding in
Appearance is configured, and shaking hands between actual subsystem and main system just completes after success；Now need to inform to main system
Oneself configuration successful, and local overtime timer is opened, the purpose of the timer is not receive any master within a certain period of time
Timeout treatment is carried out after the message of system, and oneself will be placed in original state, and restarts to send hello packet；
Step 2 16：Main system just completes all behaviour that shake hands receiving actual subsystem configuration successful message later
Make；Now main system needs to enter actual subsystem native virtualization operation according to actual subsystem corresponding information, by all realities
Border subsystem information is virtual on local software.
Preferably, data interaction is carried out using reliable transport mechanism between the Virtualization Subsystems and actual subsystem.
Preferably, the step of data interaction is carried out between the Virtualization Subsystems and actual subsystem is as follows：
Step 3 11：Main system can access this first after the order of the actual subsystem of network management system acquisition is received
Ground whether with the presence of corresponding actual subsystem Virtualization Subsystems, if there is acquisition order just is transferred into correspondingly virtual subsystem
System processing；
Step 3 12：Virtualization Subsystems obtain communication ID from communication adaptation layer, and the ID is an interim ID, for identifying
Current operation；The ID can be encapsulated in data message and be sent out together by transmitting with order after success acquisition communication ID
It is sent to actual subsystem；
Step 3 13：Virtualization Subsystems pass through the Information encapsulations such as provisional communication ID, command word, index into data message
Reliable transport protocol is sent to actual subsystem；
Step 3 14：Actual subsystem is received after Virtualization Subsystems send over request of data, first to its data
Command word in message is parsed, and then obtains data from local according to the command word and index information parsed；Obtaining
Take after data, the data return value of acquisition, data and communication ID can be packaged into data message and are sent to by actual subsystem
Virtualization Subsystems；
Step 3 15：Virtualization Subsystems are received after the back message that actual subsystem is received, and first message is solved
Analysis, parses communication ID therein；Then search whether that thread is waiting communication ID echo message, if then will
The return value and data that are received from actual subsystem give the thread process of wait, if waiting communication ID without thread, that
Directly neglect the back message；
Step 3 16：Virtualization Subsystems enter after wait state when obtaining data from actual subsystem, if in rule
Receive actual subsystem in the fixed stand-by period to respond, then the response received from actual subsystem is returned into upper layer software (applications),
Time-out failure is thought if not receiving and responding within the regulation stand-by period, failure result is returned into upper layer software (applications).
Preferably, the command word used between the Virtualization Subsystems and actual subsystem must keep one with data structure
Cause.
The positive effect of the present invention is：The present invention can realize that access device carries out equipment in the case of without ip
Management, fault detect and alarming mechanism.The application can be good at realizing the centralized management of convergence device and access device.
Brief description of the drawings
Fig. 1 is that the application implements that the flow chart of actual subsystem is managed and monitored by network management system.
Fig. 2 is that the application implements how main system realizes the flow chart that actual subsystem is linked and virtualized with main system.
Fig. 3 is that the application implements the flow chart how Virtualization Subsystems obtain data from actual subsystem.
Embodiment
To make the object, technical solution and advantage of the application definitely, below with reference to the explanation respective streams of accompanying drawing in detail
Journey and detail section.
The virtualized management method of inventive network equipment comprises the following steps：
Step one, main system collects the actual subsystem information of the second line of a couplet, actual subsystem is carried out on the master system virtual
Change, actual subsystem is turned into the Virtualization Subsystems of main system；
Step 2, after the virtualization of actual subsystem is completed, main system carries out webmaster management, prison to Virtualization Subsystems
Control and fault warning etc..
After the virtualization of actual subsystem is completed, main system and actual subsystem give a net into a total system
Guard system, network management system directly can be managed and monitor to actual subsystem, easy to use.
Virtualization Subsystems are mainly responsible for the actual corresponding configuration information of subsystem of storage, fault message and warning information
Deng.
First actual subsystem is held consultation after completion with main system, and main system can be obtained according in negotiations process
Corresponding information carries out virtualization operations to actual subsystem, and sets up one virtual first actually in the software systems of oneself
Subsystem.The software information and the first actual subsystem of the first now virtual actual subsystem storage are completely the same, wherein wrapping
Include information and configuration, global cpu and internal memory service condition, fault detect situation of all of the port etc..
First actual subsystem is virtualized into after a Virtualization Subsystems on the master system, and main system can give virtual subsystem
System one globally unique actual Sub-System Number of distribution, the actual Sub-System Number is for the actual subsystem of unique mark, just
It can be distinguished in network management system.The numbering of actual Sub-System Number is in the main system being connected according to actual subsystem with main system
The index of physical port is determined.Physical port in main system is divided into port type, slot number, actual subsystem
Number, port numbers, wherein actual Sub-System Number is 0, for being expressed as main system port.Virtualization Subsystems pass through the thing in main system
Reason stomochord, which attracts to calculate Virtualization Subsystems and index, is advantageous in that network management system can clearly know the actual son accessed
System is suspended under being under main system that physical port, and when can clearly know access actual subsystem data message from
Physical interface in that main system is sent.
Network management system can obtain its Virtualization Subsystems information stored after main system is logined from main system, and
Now network management system can just see the information of main system and all actual subsystems in its management system, and being capable of basis
Demand makes corresponding configuration and monitoring demand.
It is real for the uniformity of the software-related information that ensures the actual subsystem of virtual first and the first actual subsystem
Any configuration information of border subsystem must all be configured by main system.Actual subsystem relevant information is configured by main system
Corresponding modification information can be preserved by the Virtualization Subsystems software in main system, virtual software.If directly configured actual
Subsystem is without Virtualization Subsystems, then Virtualization Subsystems software can not just know corresponding configuration information, cause by principal series
System can not correctly check actual subsystem information.
As shown in figure 1, the process that the application implements to manage and monitor by network management system actual subsystem is as follows：
Step 101：Network management system needs to access actual subsystem, solicited message can be sent to main system, and inform master
System network management system request is actual subsystem；
Step 102：Equipment index during main system is asked according to webmaster determines that request is local or actual subsystem, such as
Fruit is that solicited message can be sent to processing on the actual subsystem of native virtualization by actual subsystem；
Step 103：The actual subsystem of virtualization in main system can be to real actual subsystem after receiving processing request
System initiates information request, and acquisition corresponding information returns to main system from real actual subsystem；
Step 104：Actual subsystem detects this earth fault later, it is necessary to be noticed to main system, actual subsystem
Fault message is sent on the Virtualization Subsystems of main system first；
Step 105：Virtualization Subsystems are received after the fault message from true actual subsystem, can be incited somebody to action by main system
Fault message is sent to network management system；
Step 106：Fault message with actual subsystem information is sent to network management system by main system.
When network management system needs to carry out data acquisition to the second actual subsystem, comprise the following steps that：
Network management system initiates access request firstly the need of to main system, informs that main system network management system needs the purpose accessed
What is.Main system judges that network management system needs to access the second actual subsystem after the access request of network management system is received
Data message in system.
Main system can be transmitted the request to local after the access request for the second actual subsystem for receiving network management system
The virtual second actual subsystem, handled by the virtual second actual subsystem.If webmaster access be configuration information or
The non real-time access request for needing to obtain hardware information, just returns to webmaster by the software information stored on local virtual subsystem
System.If what network management system was accessed is the information for needing to obtain from the second actual subsystem in real time, then virtual second is real
Border subsystem will be by replying network management system after accessing the second actual subsystem.
Virtual second actual subsystem stored the second actual subsystem all in information, and timing synchronizes
Operation.Network management system can so be reduced frequently to obtain actual subsystem information or once obtain multiple actual subsystem letters
The traffic between the system of a large amount of main systems and actual subsystem is caused during breath.And can be quickly response data give webmaster system
System.And then need directly to obtain from actual subsystem for the higher operation of requirement of real-time, it is ensured that network management system can and
When see the real time execution situation of actual subsystem.
There are multiple threads in the virtual second actual subsystem can be to some requirement of real-time in the second actual subsystem
The synchronization that not high information is timed.Including the CPU, internal memory, the optical module of port of the second actual subsystem DDM numbers
According to etc..And to the traffic statistics of the second actual subsystem port, the higher operation of requirement of real-time such as physics link states is then
By directly being obtained in real time from the second actual subsystem.
Virtual second actual subsystem timing or acquisition in real time from the second actual subsystem by reliable transport protocol
Corresponding data.Second actual subsystem access information of virtual second actual subsystem on main system is received provides corresponding sound
Should and it reply.Need to enter the index informations such as port when the virtual second actual subsystem conducts interviews to the second actual subsystem
Row conversion, in order to uniquely distinguishing the port index on all actual subsystems, all actual subsystem ports in main system
Index has taken actual Sub-System Number.And needed when the virtual second actual subsystem conducts interviews to actual subsystem by rope
Fuse breath is converted into general index, removes actual Sub-System Number relevant information, and so actual subsystem could correctly obtain correspondence
Information.
First actual subsystem needs to be noticed to network management system in real time after detecting local emergency failure.
First actual subsystem needs timely to send alarm letter to network management system after local emergency failure is detected
Breath, and can not go to obtain when network management system poll.For example after physical port link down need in time to main system and net
Guard system is noticed.Detected in the first actual subsystem and catastrophe failure locally occur with rear virtual first reality to main system
Border subsystem carries out fault warning notice.Virtual first actual subsystem receives record first after the first actual subsystem alarm
Actual subsystem is in malfunction, and is sent a warning message by main system to network management system, reminds user serious event occur
Barrier, it is necessary to be handled in time.
As shown in Fig. 2 the process how established the link for actual subsystem and main system.
In order to reduce main system burden, main system will not active the whether online message of the actual subsystem of transmission detection.
But hello packet is periodically sent by actual subsystem, notice the presence of oneself.Set up in actual subsystem and main system
After connection physically, the request that main system will receive actual subsystem is reached the standard grade information.Main system is entered with actual subsystem
Main system can then load into actual subsystem local Virtualization Subsystems to handshake operation of having gone later, comprise the following steps that：
Step 201：Hello packet is periodically sent for actual subsystem, the presence of oneself is noticed.In actual subsystem
Set up with main system after stable physical connection, main system will receive the hello packet sent of actual subsystem, and
Message is responded to hello packet.
Step 202：Main system can notice oneself after actual subsystem hello requests are received to actual subsystem
Opposite end request is received, and provides back message, allows actual subsystem to carry out next step operation.
Step 203：Actual subsystem will stop hello packet after the hello for receiving main system is responded, and right
Main system initiates the request message of the actual subsystem of loading to main system.
Step 204：Main system detected after the load request of actual subsystem is received main system and actual subsystem it
Between data channel whether normal table, now main system can be by transmitting message to actual subsystem send configuration message
(configuration message can be clock setting or sky).The main purpose of this message is whether just to detect data transmission channel
Often.
Step 205：Actual subsystem can be according to the corresponding contents for configuring message after the configuration message of main system is received
Configured, shaking hands between actual subsystem and main system just completes after success.Now need to inform certainly to main system
Own configuration successful, and the overtime timer on format ground is played, the purpose of the timer is not receive any principal series within a certain period of time
Timeout treatment is carried out after the message of system, and oneself will be placed in original state, and restarts to send hello packet.
Step 206：Main system just completes all handshake operations receiving actual subsystem configuration successful message later.This
When main system need according to actual subsystem corresponding information actual subsystem is entered native virtualization operation, by all actual subsystems
Information of uniting is virtual on local software.Actual subsystem corresponding information can be frequently obtained in virtualization process, until all
Information is got.
As shown in figure 3, Virtualization Subsystems are the flow charts that data how are obtained from actual subsystem, specific steps are such as
Under：
Shown in step 301, main system can access this first after the order of the actual subsystem of network management system acquisition is received
Ground whether with the presence of corresponding actual subsystem Virtualization Subsystems, if there is acquisition order just is transferred into correspondingly virtual subsystem
System processing.In addition to receiving the corresponding order for obtaining actual subsystem information from network management system, Virtualization Subsystems are also periodic
The synchronous corresponding software information of the actual subsystem of poll, is easy to network management system directly to obtain information from Virtualization Subsystems.
Shown in step 302, Virtualization Subsystems obtain communication ID from communication adaptation layer, and the ID is an interim ID, for marking
Know current operation.The ID can be encapsulated in data message and with order together by transmitting by success after obtaining communication ID
It is sent to actual subsystem.
Shown in step 303, Virtualization Subsystems lead to the Information encapsulations such as provisional communication ID, command word, index into data message
Cross reliable transport protocol be sent to actual subsystem (described transmitting principle here is similar with tcp agreements, using based on
Two layers of reliable transport protocol is carried out), wherein index information can not be the index information stored on Virtualization Subsystems, it is necessary to change
The general index information that can be recognized into the corresponding actual subsystem of actual subsystem.This is operated into after data are sent
Actual subsystem is waited to respond state.
Shown in step 304, actual subsystem is received after Virtualization Subsystems send over request of data, first to its data
Command word in message is parsed, and then obtains data from local according to the command word and index information parsed.If
Return value and data are then returned to Virtualization Subsystems by data acquisition success, and return value is returned into virtual subnet if unsuccessful
System.After data have been obtained, actual subsystem can send the data return value of acquisition, data and Virtualization Subsystems
Communication ID be packaged into data message and be sent to Virtualization Subsystems.
Shown in step 305, Virtualization Subsystems are received after the back message that actual subsystem is received, and first message is solved
Analysis, parses communication ID therein.Then search whether that thread is waiting communication ID echo message, if then will
The return value and data that are received from actual subsystem give the thread process of wait, if waiting communication ID without thread, that
Directly neglect the back message.
Shown in step 306, Virtualization Subsystems enter after wait state when obtaining data from actual subsystem, if in rule
Receive actual subsystem in the fixed stand-by period to respond, then the response received from actual subsystem is returned into upper layer software (applications),
Time-out failure is thought if not receiving and responding within the regulation stand-by period, failure result is returned into upper layer software (applications).
Above-mentioned steps describe the process how upper layer software (applications) obtains data from actual subsystem.And Notable
Some is：One, command word when being interacted between Virtualization Subsystems and actual subsystem needs complete unity, it is proposed that actual subsystem
Using same command word header file when being compiled with main system, transmitting the structure size and content of data will also be consistent.Two,
Virtualization Subsystems are with representing that the index value of port has differences on actual subsystem, the port index value on Virtualization Subsystems is to add
Virtualization Subsystems ID information has been gone up, has so been for unique mark all of the port on the master system.And actual subsystem subordination
In a single system, so the port index ID of all actual subsystems is general, that is, going out for repetition is had
It is existing.When Virtualization Subsystems are with actual subsystem communication, it is necessary to which index information be converted into that opposite end can recognize is correct
Index value.
Particular embodiments described above, technical problem, technical scheme and beneficial effect to the solution of the present invention are carried out
It is further described, should be understood that the specific embodiment that the foregoing is only of the invention, be not limited to
The present invention, within the spirit and principles of the invention, any modification, equivalent substitution and improvements done etc. should be included in this
Within the protection domain of invention.
Claims (11)
1. a kind of virtualized management method of the network equipment, it is characterised in that it comprises the following steps：
Step one, main system collects the actual subsystem information of the second line of a couplet, and actual subsystem is virtualized on the master system, made
Actual subsystem turns into the Virtualization Subsystems of main system；
Step 2, after the virtualization of actual subsystem is completed, main system carries out webmaster management to Virtualization Subsystems, monitor and
Fault warning.
2. the virtualized management method of the network equipment as claimed in claim 1, it is characterised in that the step 2 completes real
After the virtualization of border subsystem, main system and actual subsystem give a network management system, network management system into a total system
Directly actual subsystem is managed and monitored.
3. the virtualized management method of the network equipment as claimed in claim 2, it is characterised in that the Virtualization Subsystems are main
It is responsible for the actual corresponding configuration information of subsystem of storage, fault message and warning information.
4. the virtualized management method of the network equipment as claimed in claim 2, it is characterised in that the network management system management and
The actual subsystem of monitoring uses following steps：
Step 11：Network management system needs to access actual subsystem, solicited message can be sent to main system, and inform main system
Network management system request is actual subsystem；
Step 12：Equipment index during main system is asked according to webmaster determines that request is local or actual subsystem, if
It is that solicited message can be sent to processing on the actual subsystem of native virtualization by actual subsystem；
Step 13：The actual subsystem of virtualization in main system can be sent out after receiving processing request to real actual subsystem
Information request is played, and corresponding information is obtained from real actual subsystem and returns to main system；
Step 14：Actual subsystem detects this earth fault later, it is necessary to be noticed to main system, and actual subsystem is first
Fault message is sent on the Virtualization Subsystems of main system；
Step 15：Virtualization Subsystems are received after the fault message from true actual subsystem, can by main system will therefore
Barrier information is sent to network management system；
Step 10 six：Fault message with actual subsystem information is sent to network management system by main system.
5. the virtualized management method of the network equipment as claimed in claim 1, it is characterised in that the main system can be to virtual
Subsystem distributes a globally unique actual Sub-System Number.
6. the virtualized management method of the network equipment as claimed in claim 5, it is characterised in that the actual Sub-System Number is
The physical port number in main system being connected according to actual subsystem with main system is configured, advantage of this is that convenient
Know on that port hung under the actual subsystem on the master system.
7. the virtualized management method of the network equipment as claimed in claim 1, it is characterised in that the main system listens to reality
The hello packet that border subsystem is sent, determines that actual subsystem exists and sets up main system and reality by hello packet
Annexation between subsystem.
8. the virtualized management method of the network equipment as claimed in claim 7, it is characterised in that described to set up main system and reality
Annexation between the subsystem of border uses following steps：
Step 2 11：Actual subsystem periodically sends hello packet, notices the presence of oneself；
Step 2 12：Main system receives and can notice oneself to actual subsystem after actual subsystem hello request and received
Asked to opposite end, and provide back message, allow actual subsystem to carry out next step operation；
Step 2 13：Actual subsystem will stop hello packet after the hello packet for receiving main system is responded, and
The request message of the actual subsystem of loading is initiated main system to main system；
Step 2 14：Main system is being detected between main system and actual subsystem after receiving the load request of actual subsystem
Data channel whether normal table；
Step 2 15：Actual subsystem can enter after the configuration message of main system is received according to the corresponding contents of configuration message
Row configuration, shaking hands between actual subsystem and main system just completes after success；Now need to inform oneself to main system
Configuration successful, and local overtime timer is opened, the purpose of the timer is not receive any main system within a certain period of time
Message after carry out timeout treatment, and oneself will be placed in original state, and restart to send hello packet；
Step 2 16：Main system just completes all handshake operations receiving actual subsystem configuration successful message later；This
When main system need according to actual subsystem corresponding information actual subsystem is entered native virtualization operation, by all actual subsystems
Information of uniting is virtual on local software.
9. the virtualized management method of the network equipment as claimed in claim 1, it is characterised in that the Virtualization Subsystems and reality
Data interaction is carried out using reliable transport mechanism between the subsystem of border.
10. the virtualized management method of the network equipment as claimed in claim 9, it is characterised in that the Virtualization Subsystems with
The step of data interaction is carried out between actual subsystem is as follows：
Step 3 11：Main system is after the order of the actual subsystem of network management system acquisition is received, and can access first is locally
The no Virtualization Subsystems with the presence of corresponding actual subsystem, are transferred at correspondence Virtualization Subsystems if there is will just obtain order
Reason；
Step 3 12：Virtualization Subsystems obtain communication ID from communication adaptation layer, and the ID is an interim ID, current for identifying
Operation；The ID can be encapsulated in data message and be sent to together by transmitting with order after success acquisition communication ID
Actual subsystem；
Step 3 13：Virtualization Subsystems pass through the Information encapsulations such as provisional communication ID, command word, index into data message reliable
Host-host protocol is sent to actual subsystem；
Step 3 14：Actual subsystem is received after Virtualization Subsystems send over request of data, first to its data message
In command word parsed, data are then obtained from local according to the command word that parses and index information；Obtaining
After data, the data return value of acquisition, data and communication ID can be packaged into data message and are sent to virtually by actual subsystem
Subsystem；
Step 3 15：Virtualization Subsystems are received after the back message that actual subsystem is received, and first message is parsed, solution
Separate out communication ID therein；Then search whether that thread is waiting communication ID echo message, if then will be from reality
Return value and data that border subsystem is received give the thread process of wait, if waiting communication ID without thread, then straight
Connect and neglect the back message；
Step 3 16：Virtualization Subsystems enter after wait state when obtaining data from actual subsystem, if defined
Receive actual subsystem in stand-by period to respond, then the response received from actual subsystem is returned into upper layer software (applications), if
Do not receive response within the regulation stand-by period and then think time-out failure, failure result is returned into upper layer software (applications).
11. the virtualized management method of the network equipment as claimed in claim 10, it is characterised in that the Virtualization Subsystems with
The command word used between actual subsystem must be consistent with data structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611032732.4A CN107070676A (en) | 2016-11-16 | 2016-11-16 | The virtualized management method of the network equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611032732.4A CN107070676A (en) | 2016-11-16 | 2016-11-16 | The virtualized management method of the network equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107070676A true CN107070676A (en) | 2017-08-18 |
Family
ID=59618867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611032732.4A Pending CN107070676A (en) | 2016-11-16 | 2016-11-16 | The virtualized management method of the network equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107070676A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110995585A (en) * | 2019-12-10 | 2020-04-10 | 武汉瑞盈通网络技术有限公司 | Link non-load sharing protection method |
| CN111130934A (en) * | 2019-12-20 | 2020-05-08 | 国铁吉讯科技有限公司 | Monitoring method, device and system of communication system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101765225A (en) * | 2008-12-24 | 2010-06-30 | 华为技术有限公司 | Virtual cluster management system and cluster node |
| CN101986655A (en) * | 2010-10-21 | 2011-03-16 | 浪潮(北京)电子信息产业有限公司 | Storage network and data reading and writing method thereof |
| US20150089505A1 (en) * | 2013-09-26 | 2015-03-26 | Infosys Limited | Systems and methods for fault tolerant batch processing in a virtual environment |
| CN104639413A (en) * | 2013-11-13 | 2015-05-20 | 华为技术有限公司 | Access network virtualization method and agent node |
| CN105391741A (en) * | 2015-12-17 | 2016-03-09 | 迈普通信技术股份有限公司 | Access device safety control method, device and system |
-
2016
- 2016-11-16 CN CN201611032732.4A patent/CN107070676A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101765225A (en) * | 2008-12-24 | 2010-06-30 | 华为技术有限公司 | Virtual cluster management system and cluster node |
| CN101986655A (en) * | 2010-10-21 | 2011-03-16 | 浪潮(北京)电子信息产业有限公司 | Storage network and data reading and writing method thereof |
| US20150089505A1 (en) * | 2013-09-26 | 2015-03-26 | Infosys Limited | Systems and methods for fault tolerant batch processing in a virtual environment |
| CN104639413A (en) * | 2013-11-13 | 2015-05-20 | 华为技术有限公司 | Access network virtualization method and agent node |
| CN105391741A (en) * | 2015-12-17 | 2016-03-09 | 迈普通信技术股份有限公司 | Access device safety control method, device and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110995585A (en) * | 2019-12-10 | 2020-04-10 | 武汉瑞盈通网络技术有限公司 | Link non-load sharing protection method |
| CN111130934A (en) * | 2019-12-20 | 2020-05-08 | 国铁吉讯科技有限公司 | Monitoring method, device and system of communication system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102880475B (en) | Based on the real-time event disposal system of cloud computing and method in computer software | |
| CN103581276B (en) | Cluster management device, system, service customer end and correlation method | |
| CN103199972B (en) | The two-node cluster hot backup changing method realized based on SOA, RS485 bus and hot backup system | |
| CN105407180B (en) | The information push method and device of server | |
| CN109831318A (en) | A kind of system, method and server obtaining network topology | |
| CN102246489A (en) | Systems and methods for connection management for asynchronous messaging over http | |
| CN104077199B (en) | Based on partition method and the system of the high-availability cluster of shared disk | |
| CN103207841A (en) | Method and device for data reading and writing on basis of key-value buffer | |
| CN104270291A (en) | Content delivery network (CDN) quality monitoring method | |
| CN101567861B (en) | Data synchronization method and application system between heterogeneous application systems | |
| CN102523118A (en) | Redundancy control system consisting of multiple control computers in local area network and method for redundancy control system | |
| CN102130759A (en) | Data collection method, data collection device cluster and data collection devices | |
| EP3568322B1 (en) | Central data store in vehicle electrical system | |
| CN109495530A (en) | A kind of real time traffic data transmission method, transmitting device and Transmission system | |
| CN102412990A (en) | Remote sensing satellite raw data recording system with centralized management and real-time transmission functions | |
| CN108063832B (en) | Cloud storage system and storage method thereof | |
| CN108304296A (en) | A kind of server monitoring method, system, equipment and computer readable storage medium | |
| CN103731290A (en) | Server failure switching method | |
| CN109194744A (en) | A kind of data transmission method, device, storage medium and monitoring device | |
| CN107070676A (en) | The virtualized management method of the network equipment | |
| US10225358B2 (en) | Page push method, device, server and system | |
| CN110392123A (en) | The methods, devices and systems of detection outlet IP address | |
| CN107332813A (en) | A kind of ACL collocation methods, ACL configuration equipment and server | |
| CN107145304A (en) | Server, storage system and correlation technique | |
| CN107071189A (en) | A kind of connection method of communication apparatus physical interface |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170818 |
|
| RJ01 | Rejection of invention patent application after publication |