CN102946326B - A kind of implementation method of exchanger management system - Google Patents

A kind of implementation method of exchanger management system Download PDF

Info

Publication number
CN102946326B
CN102946326B CN201210502792.3A CN201210502792A CN102946326B CN 102946326 B CN102946326 B CN 102946326B CN 201210502792 A CN201210502792 A CN 201210502792A CN 102946326 B CN102946326 B CN 102946326B
Authority
CN
China
Prior art keywords
switch
message
master
slave
upgrade
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.)
Active
Application number
CN201210502792.3A
Other languages
Chinese (zh)
Other versions
CN102946326A (en
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.)
Wangshi Technology Co ltd
Original Assignee
SHENZHEN NETCORE INDUSTRIAL 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 SHENZHEN NETCORE INDUSTRIAL Co Ltd filed Critical SHENZHEN NETCORE INDUSTRIAL Co Ltd
Priority to CN201210502792.3A priority Critical patent/CN102946326B/en
Publication of CN102946326A publication Critical patent/CN102946326A/en
Application granted granted Critical
Publication of CN102946326B publication Critical patent/CN102946326B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Small-Scale Networks (AREA)

Abstract

The invention discloses a kind of exchanger management system and implementation method.It is provided with in this management system and realizes the Topology g eneration module of respective function, designated equipment configuration module, parameter consistency maintenance module and upgrade maintenance module successively.Described Topology g eneration module, it is achieved show network topology structure figure the most intuitively;Described designated equipment configuration module, it is achieved designated switch is configured by single IP;Described upgrade maintenance functional module, it is achieved batch upgrade switch.Instant invention overcomes existing centralized exchanger management system by above-mentioned configuration to need switch device is upgraded one by one, operation is repeated several times and occupies the defect of substantial amounts of management time, by switch is managed collectively, substantially increase efficiency, reduce the probability made mistakes and save public network address simultaneously, overcome the problem that management complexity is high, be suitable for promoting the use of.

Description

A kind of implementation method of exchanger management system
Technical field
The invention belongs to networking technology area, concretely, belong to the implementation method of a kind of exchanger management system.
Background technology
Along with developing rapidly of network technology, increasing switch is applied in network.According to traditional network Way to manage, it would be desirable to these switches are carried out Decentralization and configures one by one.Along with the increase of network switch quantity, Its management difficulty will sharply increase, and once switch breaks down, location difficulty the most further.Present stage, adopt in the urgent need to us With centralized exchanger management system, switch is managed collectively.
Existing centralized exchanger management system uses the snmp protocol of standard mostly, although this solves to a certain extent The problem that management complexity of having determined is high, but in terms of designated switch configuration, switch maintenance, yet suffer from following defect:
For designated equipment configures, on the one hand existing centralized exchanger management system needs to divide for every switch Join the IP address of a management, effectively cause public network IP address waste;Still further aspect, is joining every switch When putting, owing to needing to input the IP address of this switch, thus artificial error probability is significantly greatly increased;
For plant maintenance, generally include device parameter consistency maintenance and upgrade maintenance.Safeguard at parameter consistency Aspect, some specific function option of switch device needs to configure identical parameter to keep concordance, existing the most centralized Exchanger management system needs to repeat the identical information of typing, greatly have impact on allocative efficiency, too increases simultaneously and makes mistakes Probability;In terms of device upgrade maintenance, existing centralized exchanger management system needs to carry out switch device one by one Upgrading, is repeated several times operation and occupies the substantial amounts of management time;
In sum, existing centralized exchanger management system is inefficient and easily make mistakes.
Summary of the invention
It is an object of the invention to overcome existing centralized switch management system to need to be manually entered IP address, increase Artificially error probability, and existing centralized exchanger management system needs to upgrade switch device one by one, repeatedly Repetitive operation can take a large amount of defect managing the time, it is provided that the implementation method of a kind of exchanger management system, improves network pipe Reason efficiency and reduction network configuration complexity.
To achieve these goals, the technical solution used in the present invention is as follows:
A kind of exchanger management system, including at least two switch, this management system is provided with and realizes each successively The Topology g eneration module of function, designated equipment configuration module, parameter consistency maintenance module and upgrade maintenance module;Topology is raw Module is become to be used for generating network topology;Designated equipment configuration module is used for realizing single IP and configures designated switch;Ginseng Number consistency maintenance module is for specifying parameter to carry out concordance distribution processor;Upgrade maintenance module is for after distribution parameters By upgrade maintenance module batch upgrade switch.
Based on this exchanger management system, present invention also offers its implementation, comprise the following steps:
(1) network topology is generated by Topology g eneration module;
(2) realize single IP by designated equipment configuration module designated switch is configured;
(3) parameter consistency maintenance module is to specifying parameter to carry out concordance distribution processor;
(4) by upgrade maintenance module batch upgrade switch after distribution parameters.
Further, the implementation method of described step (2) including:
P1. designated switch;
P2. switch management role includes Master and Slave, carries out role by step P201~step P214 and cuts Change:
P201. switch management role is Master, performs step P202~step P205, if switch management role is Slave, performs step P206~step P212;
For step P201, following steps P202~step P205, judge that switch role is as performed during Master:
P202.Master transmission handover request Switch to message is to purpose Slave, and the machine sets up NAT table, and state is Etc. to be received;
P203. the Slave of mesh receives Switch to message, and judges legitimacy: if legal, then enter next step, instead Then return " mistake " and terminate switching;
P204. the Slave of mesh sets up NAT table, transmission reception Accept message to Master;
After P205.Master receives Accept message, change nat entry is reception state, terminates switching;
For step P201, following steps P206~step P212, judge that switch role is as performed during Slave:
The most former Slave sends handover request Switch to message to Master;
P207.Master switch judges legitimacy, if legal, enters step P208;Otherwise, return mistake, terminate Switching;
P208.Master judges whether to switch to this switch, is, then perform step P213 and step P214, otherwise, then Perform step P209~step P212;
Following steps P209~step P212, held when being judged as not switching to this switch by step P208Master OK, now carry out is the switching of Slave to Slave:
P209.Master transmission Accept message, to former Slave, is deleted original NAT table, is re-established sensing purpose The NAT table of Slave, state is etc. to be received, and sends handover request Switch to message to purpose Slave;
P210. the Slave of mesh receives Switch to message, and judges legitimacy: if legal, then perform next step;Instead It, return mistake, terminates switching;
P211. the Slave of mesh adds nat entry, transmission reception Accept message to Master;
After P212.Master receives Accept message, change nat entry, for accepting state, terminates switching;
Following steps P213 and step P214, when being judged as being switched to this switch for step P207Master, performed, Now carry out is the switching of Slave to Master:
P213.Master deletes nat entry and sends Accept message;
The most former Slave deletes NAT table after receiving response, is accomplished to the switching of Master;
P3. realize switch configuration message by following steps to process:
P301. by PC main frame transmission http message to Master;
P302.Master searches NAT table: if it is found, then enter next step;Otherwise data message transfers to Master upper strata Process;
P303. according to NAT table content, replace message source IP, purpose IP and source MAC, target MAC (Media Access Control) address, change message Type is IPstack type, is forwarded to purpose Slave;
P304. changing type of message according to NAT table item content after the Slave of mesh receives message is http type of message, and Upper strata is transferred to process;
P305. after upper strata has processed message, can send back message to bottom, bottom change type of message is IPstack Type;
After P306.Master receives message, further according to NAT table item, it is forwarded to PC main frame;
P307. configuration terminates.
In order to preferably judge its legitimacy, legitimacy described in described step P203 and step P210 satisfied include with Lower two conditions:
(4a) in the Switch to message received the MAC Address of sender and private IP address with in local equipment table The MAC Address that managerial roles is Master equipment consistent with private ip;
(4b) local equipment is not set up nat entry.
Further, the satisfied three below condition that includes of legitimacy in described step P207:
(5a) MAC in recipient MAC, private ip, the tcp port of link and the machine nat entry, private ip, link Tcp port is consistent;
(5b) the machine has built up this nat entry;
(5c) " MAC Address " in the Switch to message received is present in the equipment list of the machine.
Further, described step (3) parameter consistency maintenance module is to specifying parameter to carry out concordance distribution processor Implementation method includes:
P4. determine, according to switch type information, the switch that Local Parameters can be distributed, i.e. select switch type;
P5. the switch to be distributed according to selected switch type selection and parameter to be distributed;
P6. data transmission start timer, a length of manager's designated value or acquiescence 5 seconds during timer, in messages Encapsulation parameter and exchanger information, be sent to purpose switch;
P7. the switch of mesh receives message, it is determined that message is the most processed: if untreated, perform next Step;Otherwise, abandon this message;
P8. the switch of mesh carries out validity judgement to message: if legal, automatically configures switch parameter, returns and ring Answer message;Otherwise, abandon this message;
P9. distribution switches receives response message, it is determined that timer is the most overtime: if before the timer expires, receives To all distribution switches response messages, then distribute successfully, cancel timer, return " successfully " result, go to step P11;If Timer expired, then enter next step;
P10. Retransmission timeout number of times is judged: if it exceeds number of retransmissions, stop retransmitting, return " unsuccessfully " result, under entrance One step;Otherwise, reset timer, retransmission parameter distribution message, go to step P7, wherein Retransmission timeout number of times is referred to by manager Determine or be defaulted as 3 times;
P11. result is shown.
For the legitimacy in preferably determination step P8, the judgement of legitimacy described in described step P8 includes following three Individual standard:
(6a) switch of parameter distribution message transmitting party exists in the machine;
(6b) switch type specified in parameter distribution message is consistent with the type of the machine;
(6c) parameter specified in parameter distribution message, the machine allows configuration;
The judgement of described legitimacy meets above-mentioned standard simultaneously.
Further, the concrete methods of realizing of described step (4) is as follows:
P12. the switch type to be upgraded is selected;
P13. upgrading is initiated switch and is listed scalable switch in network according to the switch type information that can be upgraded;
P14. setting up upgrade server and run, upgrade server is to initiate a journey of operation on switch in upgrading Sequence, starts " upgrade request " intervalometer, and timer duration is manager's designated value or 5 second time of acquiescence, waits upgrade file Transmission, upgrading initiate switch to scalable switch send upgrade request message, encapsulate the most scalable in messages Switch mac address;
The most scalable switch receives upgrade request message, starts updating client, start waiting for after checking legitimacy Receive upgrade file, and send upgrading response message to upgrading initiation switch;
P16. upgrading initiation switch judges whether to receive the upgrading response message of all scalable switches: if received To upgrading response message, go to step P17;If timer expired, it is determined that Retransmission timeout number of times, if it exceeds number of retransmissions, just Stop retransmitting, return " unsuccessfully " result;Otherwise, reset " upgrade request " intervalometer, retransmit upgrade request message, go to step P15;
P17. upgrade server starts to transmit upgrade file to scalable switch, starts " upgrade file transmission " calmly simultaneously Time device, such as loading error occurring or time-out, it is determined that number of retransmissions, if it exceeds three times, just stop retransmitting, return " unsuccessfully " result;Instead It, reset " upgrade file transmission " intervalometer, retransmits upgrade file;
The most scalable switch receives upgrade file, starts upgrading;
P19., after having upgraded, send upgrading and complete message to upgrading initiation switch;
P20. display upgrades successfully.
In order to preferably judge the legitimacy in step P15, the judgement of legitimacy described in described step P15 includes following 2 standards:
(9a) upgrade request message transmitting party equipment exists in local equipment table;
(9b) switch type specified in upgrade request message is consistent with the type of the machine;
The judgement of described legitimacy meets above-mentioned standard simultaneously.
Compared with prior art, the method have the advantages that
(1) the whole flow process that realizes of the present invention ensure that exchanger management system location is simple, it is possible to is managed collectively, Reducing management complexity, along with the increase of network switch quantity, the present invention also is able to realize all friendships according to its flow process The unified management changed planes, it is to avoid present stage switch quantity in whole management system is the most, and management difficulty sharply increases Problem.
(2) first the present invention selectes switch in designated switch configuration, and switch carries out Counterchange roles again, the most right Switch configuration message processes;Use a public network address that each switch is entered when switch is carried out Message processing Row configuration, this implementation need not all distribute every switch the IP address of one management, do not results in public network IP Address is wasted, and still further aspect, when configuring every switch, it is not necessary to input the address of this switch, many institute's weeks Knowing, IP address is a string long numeral, often has the phenomenon artificially made mistakes to occur in a large amount of inputs, and therefore the present invention only needs public affairs Net IP address, greatly reduces the probability artificially made mistakes.
(3) present invention need not safeguard all switches during parameter consistency safeguards this, existing Centralized exchange management system needs to repeat to employ identical information, and strong influence allocative efficiency also can increase simultaneously Wrong probability, first the present invention selects switch type, equipment that reselection to be distributed and parameter, finally transmits data and opens Dynamic Retransmission timeout timer, the most just need not all safeguard all switches, simultaneously can also be to certain of multiple devices A little parameters carry out conforming maintenance, greatly improve allocative efficiency, it is possible to reduce the generation even avoiding mistake.
(4) present invention overcomes in upgrade maintenance module needs in prior art to upgrade switch one by one, because of And operation is repeated several times and occupies the defect of substantial amounts of management time, first the present invention selects upgradeable switch in the machine, Set up upgrade server in the machine again, send message to upgradeable switch, after having upgraded, feed back to upgrade server again, This process by unifying upgrading to the switch needing upgrading, it is not necessary to upgrades switch one by one, significantly again Shorten the time and efforts spent by escalation process.
(5) present invention Slave in designated switch configures sends handover request Switch to message to switch management After the Master switch of system, Master to judge its legitimacy, and compared with prior art the present invention is prevented from being hacked, Avoid being occurred paralysing by switch system whole during outside world, simultaneously occur illegal in the case of can also automatically carry out Maintain order at a public gathering and correct in time.
(6) sum it up, the process that realizes of the present invention embodies completely and switch is carried out unified management can improve pipe This spirit of reason efficiency, prior art is all to use to control one by one to the management of switch, and this control method heals at switch Time many, difficulty is bigger, and when breaking down, location is difficult to.And switch is managed collectively by the present invention, each process is Satisfactory switch is screened, then is uniformly processed, this method overcome completely in prior art manage concentratedly, by One processes the defect causing workload appearance loaded down with trivial details, easy mistake, has prominent substantive distinguishing features with the most progressive.
Accompanying drawing explanation
Fig. 1 is embodiment of the present invention schematic flow sheet.
Fig. 2 is Slave switch S4 Counterchange roles mode flow chart in the embodiment of the present invention.
Fig. 3 is Slave switch S4 configuration message handling process schematic diagram in the embodiment of the present invention.
Fig. 4 is parameter consistency attended operation schematic flow sheet in the embodiment of the present invention.
Fig. 5 is to manage system in the embodiment of the present invention to carry out device upgrade attended operation schematic flow sheet.
Detailed description of the invention
The invention will be further described with embodiment below in conjunction with the accompanying drawings, and embodiments of the present invention include but not limited to The following example.
Embodiment
In the present embodiment, this exchanger management system has 6 switch devices, respectively S1, S2, S3, S4, S5 and S6, and this network only has public ip address 109.223.223.12, manager by this public network address to each exchange Machine equipment configures.As it is shown in figure 1, the present embodiment to realize flow process as follows:
(1), after exchanger management system starts, carry out Topology g eneration, in Topology g eneration, the management of S5 and S6 packet with S1, S2, S3 are different with S4, therefore abandon the hello packet of S5, S6, S3 and S4 is Slave;S1 Yu S2 competes unsuccessfully simultaneously, S1 It is set to Slave, S2 and becomes Master.
Wherein this Topology g eneration is prior art, therefore is described in detail the most in an embodiment.
(2) next configuring switch S1, S2, S3, S4, the process wherein configured is as follows:
First switch is selected
S2, S3, S4, S2 are configured by management system successively, and wherein the second time to S2 configures is due in this scene Under, S2 needs again to revise configuration information.
Judge that switch Counterchange roles mode configuration message process again
P1. the configuration process configuring S2, S2 is:
P101. manager inputs public network address 109.223.223.12 at the web page of PC main frame, logs on Master and hands over Change planes S2.According to the system topological figure of display, manager clicks on Master switch, configures S2, manager place PC main frame is realized by http message with the information transmission of inter-exchange;
P102.Master switch S2 processes data message, then web interface display configuration result, Master switch S2 configuration is complete;
P2. it is reconfigured at S3, it is determined that S3 is Slave, and current switch management role is Master, clicks on Topology g eneration S3 on figure, enters S3 administration interface, and now the module on management system designated switch performs to have operated as follows to join S3 Put:
P201.S2 judges that oneself is as Master;
P202.S2 transmission handover request Switch to message is to purpose Slave switch S3, and sets up NAT in the machine Table, state is etc. to be received, and wherein Switch to message is as follows:
NAT table content is as follows:
P203. the Slave switch S3 of mesh receives Switch to message, carries out validity judgement, due to 1) receive In Switch to message, the MAC Address of sender sets for Master with the managerial roles in local equipment table with private IP address Standby MAC Address is consistent with private ip;And 2) local equipment do not sets up this nat entry, it is judged that legal;
P204. transmission reception Accept message is to Master switch S2, receives Accept message content as follows:
After P205.Master switch S2 receives Accept message, changing NAT table, state is set to reception state, completes to cut Change.
P3. S3 being carried out parameter setting, system needs the flow process carrying out Message processing as follows:
P301. each option of Administrator S3, clicks on " determination ", and configuration information sends http message to handing over by PC main frame Changing the Master switch S2 of machine management system, the designated equipment configuration module now managing system performs to operate as follows:
After P302.Master switch S2 receives http message, search IP address corresponding for S3 and MAC Address in NAT table;
P303.Master switch S2, according to nat entry content, replaces message source IP, purpose IP and source MAC and purpose MAC Address, change http message Ether the type field value is 0x22e0, finally sends to purpose Slave switch S3;
P304. after the Slave switch S3 of mesh receives message according to NAT table item content change Ether the type field value it is 0x0800, and be submitted to upper strata and process, and safeguard TCP link-state information
After P305.S3 upper strata has processed message, can send back message to bottom, bottom change Ether Type is 0x22e0, is given to S2;
After P306.S2 receives message, further according to NAT table, replace the source IP of message, purpose IP and former MAC and purpose MAC Address, and to change message Ether the type field value be 0x0800, and http back message is forwarded to PC main frame;
P307.Web interface display configuration result, S3 configuration is complete, and current SWITCH now is S3.
P4. manager continues to click on Topology g eneration figure Slave switch S4, enters S4 administration interface, now manages system Designated switch configuration module operate, as shown in Figure 2:
P401.S3 judges that oneself is as Slave role;
P402.S3 sends the Switch to message S2 to exchanger management system, and content includes IP address and the MAC of S4 Address;
P403.S2 judges, if:
1) the machine has been set up nat entry;
2) MAC in the MAC of sender S3, private ip, the tcp port of link and the machine nat entry, private ip, link Tcp port consistent;
3) " the purpose equipment S4MAC " in the Switch to message received and the contrast of all entries, equipment in equipment list Table exists the entry of this MAC;
Therefore evaluate legal and enter next step;If being unsatisfactory for above three condition, then judging illegal, returning " mistake ";
P404.S2 judges that purpose switch, as S4, is not oneself;
P405.S2 sends Accept message to S3, S3 after receiving Accept message, deletion NAT table;
P406.S2 deletes the option in original NAT table about S3, re-establishes the NAT table pointing to S4, and state is etc. waiting Receiving, and send Switch to message to S4, content includes IP address and the MAC Address of S4;
P407.S4 receives after Switch to message and carries out validity decision, if 1) in the Switch to message that receives The MAC Address of sender and private IP address and the MAC Address that managerial roles is Master equipment in local equipment table and private There is IP consistent;2) local equipment does not sets up nat entry, it is determined that legal and enter next step;Otherwise then return " mistake ";
P408. judge legal after, S4 adds NAT table, sends Accept message to S2;
After P409.S2 receives Accept message, change nat entry, for accepting state, completes switching.
The most then starting to configure the parameter of S4, system needs to carry out Message processing, as it is shown on figure 3, its flow process is such as Under:
P501. each option of Administrator S4, clicks on " determination ", because S2 has public network IP address, configuration information is passed through PC main frame sends the http message S2 to exchanger management system, and the designated equipment configuration module now managing system performs as follows Operation:
After P502.Master equipment S2 node receives http message, search IP address corresponding for S4 and MAC ground in NAT table Location;
P503.S2, according to nat entry content, replaces message source IP, purpose IP, source MAC and target MAC (Media Access Control) address, change report Literary composition Ether the type field value is 0x22e0 (IPstack type of message), finally sends to purpose Slave switch S4;
After P504.S4 receives message, according to NAT table item content, change message Ether the type field value 0x0800, pass Give upper strata to process;
After P505.S4 has processed message, send http back message, and change message Ether the type field and be 0x22e0;
After P506.S2 receives message, further according to NAT table, replace the source IP address in message, purpose IP address, source MAC ground Location and target MAC (Media Access Control) address, and to change message Ether the type field value be 0x0800, and http back message is forwarded to PC master Machine;
P507.Web interface display configuration result, Slave equipment S4 configuration is complete, and current SWITCH now is S4.
P6. Master switch S2 is configured by system again, and manager again taps on S2 in Topology g eneration figure, enters S2 Administration interface, the designated equipment configuration module now managing system performs to operate as follows:
P601. judge that the role of current SWITCH S4 is as Slave;
P602.S4 sends the Switch to message Master switch S2 to exchanger management system, and content includes The IP address of Slave switch S2 and MAC Address;
P603.S2 carries out validity judgement, due to:
1) the machine has been set up nat entry;
2) MAC in the MAC of sender S4, private ip, the tcp port of link and the machine nat entry, private ip, link Tcp port consistent;
3) " the purpose equipment S2 " in the Switch to message received and all entries contrast in equipment list, see equipment Table exists the entry of this MAC;
Therefore judge legal;
P604.S2 deletes NAT table, S2 transmission Accept message to S4;
After P605.S4 receives Accept message, delete NAT table.
The most then configuring the parameter of S2, system needs to carry out Message processing, and idiographic flow is as follows:
P701. manager resets each option of S2, clicks on " determination ", and configuration information sends http message by PC main frame Master switch S2 to exchanger management system;
P702.S2 processes data message, i.e. S2 searches NAT table and do not finds corresponding performance, therefore is submitted at upper strata by message Reason;
P703.Web interface display configuration result, Master switch S2 configuration is complete.
(3) exchanger management system carries out parameter consistency distribution processor
Except designated switch being carried out parameter configuration, network manager can also be to multiple stage when switch is safeguarded Some special parameter of equipment carries out consistency maintenance.When the present embodiment starts, S1 is being configured by network manager, the most right Type is that the port 7 and 8 of the switch of 1824CF is polymerized.As shown in Figure 4, exchanger management system performs to operate as follows:
P8. select switch type, judge which switch Local Parameters can be distributed to according to device type information, this In embodiment, it is possible to achieve the switch of parameter distribution includes that S2 and S3, S4 switch type is undesirable, not may select;
P9. it is intended to distribution switches and parameter select: network manager selects, in web interface, the parameter needing to issue and is intended to point The switch sent out, the switch wherein to be distributed is S2 and S3;
P10. transmit data, start intervalometer, be set to 5 seconds, the most in messages encapsulation be intended to distribution switches MAC Address and Parameter information, is sent to purpose switch, and it is as follows that it implements step:
(3a) parameter distribution message content is as follows:
P11. the switch of mesh receives message, it is judged that this parameter distribution message is the most processed, if untreated, holds Go next step;Otherwise, abandon this message;
P12. message validity is judged by the switch of mesh, including: 1) parameter distribution message transmitting party equipment this Whether machine equipment table exists;2) device type specified in parameter distribution message is consistent with the type of the machine;3) parameter distribution The parameter specified in message, this function allocation;If legal, automatically configure switch parameter, return response message;Otherwise, lose Abandon this message.
As a example by S2, it is judged that sender S1 in local equipment table, designated switch type consistent with the machine and specify Parameter can configure, and by validity checking, S2 automatic configuration parameter to the machine, and returns the response message of configuration successful;Its In, parameter distribution response message content is as follows:
Type Field Value
1 PARAMETER_RESPONSE 02:10:18:63:3D:22
P13. distribution switches receives response message, it is judged that timer is the most overtime;If before the timer expires, received To all distribution switches response messages, then distribute successfully, cancel timer, return " successfully " result, simultaneously display port 7 He 8 successful polymerization;If timer expired, then enter next step;
P14. Retransmission timeout number of times is judged, if overtime three times, stop retransmitting, return " unsuccessfully " result, otherwise, reset Intervalometer, retransmission parameter distribution message, go to step P11.
(4) exchanger management system carries out upgrade maintenance operation to equipment
In the present embodiment, network manager needs to carry out switch device batch upgrade, and now network management logs on Master switch S2, as it is shown in figure 5, the concrete methods of realizing carrying out batch upgrade is as follows:
P15. the switch type to be upgraded is selected: selecting 1824CF is switch model to be upgraded;
P16. current SWITCH S2 lists scalable switch according to the switch type to be upgraded, S1 in current network, S3 is belonging to the switch of this model;
P17. set up upgrade server at S2, wait the transmission of upgrade file, send upgrading to purpose switch S1 and S3 Request message, and encapsulate the MAC Address of switch of need to upgrading in messages;Start " upgrade request " intervalometer simultaneously;Wherein, rise Level request message content is as follows:
P18. the switch of mesh receives upgrade request message, checks legitimacy, and the legitimacy content wherein checked includes: 1) Upgrade request message transmitting party equipment exists in local equipment table;2) device type specified in upgrade request message and the machine Type consistent;Judge legal after start updating client, start waiting for receiving upgrade file, and send upgrading response message To S2;Wherein, S1 upgrading response message content is as follows:
Type Field Value
1 UPGRADE_RESPONSE 22:22:22:22:18:24 1
P19.S2 judges whether to receive the upgrading response message of all purpose equipment S1 and S3: if receiving upgrading response Message, then enter next step;If timer expiry, it is determined that Retransmission timeout number of times, if it exceeds three times, just stop retransmitting, return Return " unsuccessfully " result;Otherwise, resetting " upgrade request " intervalometer, repeat requests message is also back to step P18;
P20. upgrade server starts to transmit upgrade file;
P21. the switch of mesh receives upgrade file, starts upgrading;
P22., after having upgraded, send upgrading and complete message to S2;
P23. display upgrades successfully.
According to above-described embodiment, just can well realize the present invention.

Claims (5)

1. the implementation method of an exchanger management system, it is characterised in that mainly realize step as follows:
(1) network topology is generated by Topology g eneration module;
(2) realize single IP by designated equipment configuration module designated switch is configured;
(3) parameter consistency maintenance module is to specifying parameter to carry out concordance distribution processor;
(4) by upgrade maintenance module batch upgrade switch after distribution parameters;
The implementation method of described step (2) including:
P1. designated switch;
P2. switch management role includes Master and Slave, carries out role switching by step P201~step P214:
P201. switch management role is Master, performs step P202~step P205, if switch management role is Slave, performs step P206~step P212;
For step P201, following steps P202~step P205, judge that switch role is as performed during Master:
P202.Master transmission handover request Switch to message is to purpose Slave, and the machine sets up NAT table, and state is for waiting Receive;
P203. the Slave of mesh receives Switch to message, and judges legitimacy: if legal, then enter next step, otherwise, Then return mistake and terminate switching;
P204. the Slave of mesh sets up NAT table, transmission reception Accept message to Master;
P205., after Master receives Accept message, change nat entry is reception state, terminates switching;
For step P201, following steps P206~step P212, judge that switch role is as performed during Slave:
The most former Slave sends handover request Switch to message to Master;
P207. Master switch judges legitimacy, if legal, enters step P208;Otherwise, return mistake, terminate to cut Change;
P208.Master judges whether to switch to this switch, is, then perform step P213 and step P214, otherwise, then perform Step P209~step P212;
Following steps P209~step P212, performed when being judged as not switching to this switch for step P208Master, this Shi Jinhang's is the switching of Slave to Slave:
P209.Master transmission Accept message, to former Slave, is deleted original NAT table, is re-established and point to purpose Slave NAT table, state is etc. to be received, and sends handover request Switch to message to purpose Slave;
P210. the Slave of mesh receives Switch to message, and judges legitimacy: if legal, then perform next step;Otherwise, Return mistake, terminate switching;
P211. the Slave of mesh adds nat entry, transmission reception Accept message to Master;
After P212.Master receives Accept message, change nat entry, for accepting state, terminates switching;
Following steps P213 and step P214, when being judged as being switched to this switch for step P207Master, performed, now Carry out is the switching of Slave to Master:
P213.Master deletes nat entry and sends Accept message;
The most former Slave deletes NAT table after receiving response, is accomplished to the switching of Master;
P3. realize switch configuration message by following steps to process:
P301. by PC main frame transmission http message to Master;
P302. Master searches NAT table: if it is found, then enter next step;Otherwise data message is transferred at Master upper strata Reason;
P303. according to NAT table content, replace message source IP, purpose IP and source MAC, target MAC (Media Access Control) address, change type of message For IPstack type, it is forwarded to purpose Slave;
P304. changing type of message according to NAT table item content after the Slave of mesh receives message is http type of message, and transfers to Upper strata processes;
P305. after upper strata has processed message, can send back message to bottom, bottom change type of message is IPstack type;
After P306.Master receives message, further according to NAT table item, it is forwarded to PC main frame;
P307. configuration terminates;
Described step (3) parameter consistency maintenance module carries out concordance distribution processor implementation method to appointment parameter and includes:
P4. determine, according to switch type information, the switch that Local Parameters can be distributed, i.e. select switch type;
P5. the switch to be distributed according to selected switch type selection and parameter to be distributed;
P6. data transmission start timer, during timer, a length of manager's designated value or acquiescence 5 seconds, encapsulate in messages Parameter and exchanger information, be sent to purpose switch;
P7. the switch of mesh receives message, it is determined that message is the most processed: if untreated, perform next step;Instead It, abandon this message;
P8. the switch of mesh carries out validity judgement to message: if legal, automatically configure switch parameter, returns response report Literary composition;Otherwise, abandon this message;
P9. distribution switches receives response message, it is determined that timer is the most overtime: if before the timer expires, receive institute There is distribution switches response message, then distribute successfully, cancel timer, return " successfully " result, go to step P11;If timing Device time-out, then enter next step;
P10. Retransmission timeout number of times is judged: if it exceeds number of retransmissions, stop retransmitting, return " unsuccessfully " result, enter next step; Otherwise, reset timer, retransmission parameter distribution message, go to step P7, wherein Retransmission timeout number of times carried out specifying by manager or Person is defaulted as 3 times;
P11. result is shown;
The concrete methods of realizing of described step (4) is as follows:
P12. the switch type to be upgraded is selected;
P13. upgrading is initiated switch and is listed scalable switch in network according to the switch type information to be upgraded;
P14. setting up upgrade server and run, upgrade server is to initiate a program of operation on switch in upgrading, opens Dynamic " upgrade request " intervalometer, timer duration is manager's designated value or 5 second time of acquiescence, waits the biography of upgrade file Defeated, upgrading is initiated switch and is sent upgrade request message to scalable switch, and encapsulates corresponding scalable friendship in messages Change planes MAC Address;
The most scalable switch receives upgrade request message, starts updating client after checking legitimacy, starts waiting for receiving Upgrade file, and send upgrading response message to upgrading initiation switch;
P16. upgrading initiation switch judges whether to receive the upgrading response message of all scalable switches: if received Upgrading response message, goes to step P17;If timer expired, it is determined that Retransmission timeout number of times, if it exceeds number of retransmissions, just stop Only retransmit, return " unsuccessfully " result;Otherwise, reset " upgrade request " intervalometer, retransmit upgrade request message, go to step P15;
P17. upgrade server start transmit upgrading data message to scalable switch, simultaneously startup " upgrade file transmission " Intervalometer, such as loading error occurring or time-out, it is determined that number of retransmissions, if it exceeds three times, just stop retransmitting, return " unsuccessfully " result; Otherwise, reset " upgrade file transmission " intervalometer, retransmit upgrade file;
The most scalable switch receives upgrade file, starts upgrading;
P19., after having upgraded, send upgrading and complete message to upgrading initiation switch;
P20. display upgrades successfully.
The implementation method of a kind of exchanger management system the most according to claim 1, it is characterised in that described step P203 The satisfied following two condition that includes with legitimacy described in step P210:
(4a) MAC Address of sender and private IP address and the pipe in local equipment table in the Switch to message received Reason role is that the MAC Address of Master equipment is consistent with private ip;
(4b) local equipment is not set up nat entry.
The implementation method of a kind of exchanger management system the most according to claim 2, it is characterised in that described step P207 The satisfied three below condition that includes of middle legitimacy:
(5a) MAC in recipient MAC, private ip, the tcp port of link and the machine nat entry, private ip, the TCP end of link Mouth is consistent;
(5b) the machine has built up this nat entry;
(5c) " MAC Address " in the Switch to message received is present in the equipment list of the machine.
The implementation method of a kind of exchanger management system the most according to claim 3, it is characterised in that in described step P8 The judgement of described legitimacy includes three below standard:
(6a) switch of parameter distribution message transmitting party exists in local equipment table;
(6b) switch type specified in parameter distribution message is consistent with the type of the machine;
(6c) parameter specified in parameter distribution message, the machine allows configuration;
The judgement of described legitimacy meets above-mentioned standard simultaneously.
The implementation method of a kind of exchanger management system the most according to claim 4, it is characterised in that described step P15 Described in the judgement of legitimacy include following two standard:
(9a) upgrade request message transmitting party equipment exists in local equipment table;
(9b) switch type specified in upgrade request message is consistent with the type of the machine;
The judgement of described legitimacy meets above-mentioned standard simultaneously.
CN201210502792.3A 2012-11-30 2012-11-30 A kind of implementation method of exchanger management system Active CN102946326B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210502792.3A CN102946326B (en) 2012-11-30 2012-11-30 A kind of implementation method of exchanger management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210502792.3A CN102946326B (en) 2012-11-30 2012-11-30 A kind of implementation method of exchanger management system

Publications (2)

Publication Number Publication Date
CN102946326A CN102946326A (en) 2013-02-27
CN102946326B true CN102946326B (en) 2016-12-21

Family

ID=47729235

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210502792.3A Active CN102946326B (en) 2012-11-30 2012-11-30 A kind of implementation method of exchanger management system

Country Status (1)

Country Link
CN (1) CN102946326B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104425001A (en) * 2013-08-22 2015-03-18 北京卓越信通电子股份有限公司 System for simultaneously burning multiple switches, method thereof and corresponding switches
CN104506368B (en) * 2014-12-30 2018-04-13 浪潮(北京)电子信息产业有限公司 A kind of method and apparatus for being managed collectively switch device
CN111200524B (en) * 2019-12-30 2023-02-21 长沙湘计海盾科技有限公司 Switch configuration method and server

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1414740A (en) * 2002-03-28 2003-04-30 华为技术有限公司 Centralized management method of local net exchange equipment
CN101909291A (en) * 2009-06-04 2010-12-08 上海共联通信信息发展有限公司 Method for controlling wireless network switch

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1414740A (en) * 2002-03-28 2003-04-30 华为技术有限公司 Centralized management method of local net exchange equipment
CN101909291A (en) * 2009-06-04 2010-12-08 上海共联通信信息发展有限公司 Method for controlling wireless network switch

Also Published As

Publication number Publication date
CN102946326A (en) 2013-02-27

Similar Documents

Publication Publication Date Title
RU2520385C2 (en) Method and system for updating network device
US9246976B2 (en) Method and apparatus for controlling HTTP sockets
US10693976B2 (en) Method and system for dynamic discovery of service functions
CN108259215B (en) Equipment management method and device
CN1816011A (en) Data transfer apparatus and multicast system and program
EP2991313B1 (en) Method and system for forwarding information in distributed network
CN103856302B (en) A kind of smart machine control method
CN104346198B (en) Information processing unit, server unit, information processing method and storage equipment
CN111866063B (en) Online updating system, method and device for AI algorithm of industrial Internet of things
CN102946326B (en) A kind of implementation method of exchanger management system
CN111629065B (en) Method and system for controlling OTA (over the air) upgrade of equipment in networking system
CN104094243A (en) Information processing apparatus, information processing method and program
CN102332989B (en) Method for sending configuration information and service boards
TW202103475A (en) Method for terminal device management, server and terminal device
CN104797004B (en) The method that automatic network-building is realized between master-slave equipment
CN103138961B (en) server control method, controlled server and central control server
CN103401954A (en) Implementation method of virtual DHCP (dynamic host configuration protocol)
CN112887416A (en) Frequency adjustment method and device for sending keep-alive packets
CN101242295A (en) A method for managing low-end switch
EP3320650B1 (en) Service layer anycast and somecast
CN101540696A (en) Complex dynamic routing analysis method for realizing telecommunication network based on intelligent routing simulation technique
CN108011825B (en) Multi-network equipment interconnection reality method and system based on software defined network
CN105721314A (en) Method and equipment for sending data packet
CN107528929A (en) The processing method and processing device of arp entry
JP2015037267A (en) Network apparatus setting system and network apparatus setting method

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20240304

Address after: 337099 First Floor, Building 6, Tongjiu Road, Pingxiang Economic and Technological Development Zone, Pingxiang City, Jiangxi Province

Patentee after: Wangshi Technology Co.,Ltd.

Country or region after: China

Address before: 518000, No. 902, 9th Floor, Building B, Tsinghua Information Port, High tech Zone, Nanshan District, Shenzhen, Guangdong Province

Patentee before: Shenzhen Leike Industrial Co.,Ltd.

Country or region before: China

TR01 Transfer of patent right