CN1505323A - Network administration method for no-IP address device - Google Patents
Network administration method for no-IP address device Download PDFInfo
- Publication number
- CN1505323A CN1505323A CNA021511233A CN02151123A CN1505323A CN 1505323 A CN1505323 A CN 1505323A CN A021511233 A CNA021511233 A CN A021511233A CN 02151123 A CN02151123 A CN 02151123A CN 1505323 A CN1505323 A CN 1505323A
- Authority
- CN
- China
- Prior art keywords
- address
- loop
- equipment
- agency
- physical address
- 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.)
- Granted
Links
Images
Landscapes
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a managing method for network device without IP address in communication network, it includes following steps: uses the device with IP address as the proxy of deices without IP address, configures physical address to devices without physical address; the communication between managing station and proxy can be realized by IP network, by the hop-by-hop switch of IP layer; the proxy and the mentioned managed device without IP address realizes the switch through the physical address switch. The method saves the network IP resources.
Description
Affiliated technical field
The present invention relates to a kind of method that the network equipment of no IP address in the communication network is managed.
Background technology
The main path that at present network equipment is managed for configuration has SNMP, Telnet, Web etc.These methods all are based upon on the IP, promptly will be to the managed devices configuration of IP address.Yet some equipment itself does not need the IP address in running, as equipment such as Ethernet switches.For these equipment, just to being managed, it goes to be its application IP address, be uneconomic, because the IP address is a kind of Limited resources.
Summary of the invention
The present invention proposes a kind of no IP address device network management method, only realize also managing other network equipments of not joining the IP address under the situation of only a few equipment disposition IP address.
No IP address device network management method of the present invention comprises following performing step:
The agency of the equipment of IP address as no IP address device disposed in utilization, and giving does not have physical address equipment disposition physical address;
Communicating by letter and can pass through IP network between turnkey console and the agency is by the forwarded hop-by-hop realization of IP layer;
Between agency and the described no IP address device of being managed, by being transmitted by the physical address of the no IP address device of pipe.
Adopt no IP address device network management method of the present invention, can save the IP address resource that the network equipment uses, and can control an agent equipment flexibly and act on behalf of a plurality of managed devices or a managed device by a plurality of agent equipments acquisition management information.
Description of drawings
The flow chart of request message and response message when Fig. 1 is a turnkey console by the equipment of the no IP of agent equipment management address;
Fig. 2 is for to manage the network structure of many no IP address device by an agent equipment;
Process chart when Fig. 3 wraps for a side in agent equipment and the managed device communication process receives.
Embodiment
Below in conjunction with accompanying drawing and by specific embodiment specific implementation process of the present invention is described:
Basic thought of the present invention is: utilize an equipment that has disposed the IP address as the agency, allowing this agency that the management information of turnkey console (PC) is pass on that want to manage to the user does not have the equipment of IP address.Be request message flow process via agent equipment to managed device from turnkey console as shown in Figure 1, application layer (the SNMP of agent equipment, Telnet or HTTP etc.) when receiving configuration order as server, find that this order finally is an equipment of wanting to dispose certain no IP address, just send configuration order to final purpose equipment (no IP address) as client; Is response message flow process via agent equipment to turnkey console from managed device, three layers of forwarding unit can not be arranged between agent equipment and the managed device, otherwise they can not intercommunication.
Communication between from the turnkey console to the agent equipment is by IP network, by the forwarded hop-by-hop of IP layer; To final managed devices, because managed device does not have the IP address, can not lean on the addressing of IP to transmit from agent equipment, the present invention uses the physical address of managed device to realize transmitting.Itself do not have the managed device of physical address for those, need physical address of configuration, this physical address needs not repeat on the path between three layers of adjacent forwarding unit.After the managed device that physical address conforms to is received bag, give protocol stack.What the expectation of protocol stack inlet was received usually is an IP bag, so in order to allow protocol stack can correctly resolve the bag of receiving, transmit leg (being agent equipment) will break into it IP form before sending message, but because the recipient does not have the IP address, can use loop-back address, i.e. 127.x.x.x.Because different protocol stack, the message that uses loop-back address had two kinds of processing, once being to give upper-layer protocol (this protocol stack thinks that the final destination of loop-back address expression bag is oneself) with it, the 2nd, it is thrown away (this protocol stack think the Bao Buying use loop-back address that transmits from network).For a kind of protocol stack in back, need transform, making it can be that the bag of loop-back address is sent to upper-layer protocol and handled with destination address.Source IP address then can be selected a loop-back address arbitrarily for use, when receiving packet source IP address is not conducted a survey.In brief, when communicating by letter between agent equipment and the managed device, the recipient does not conduct a survey to the occurrence of loop-back address, after its finds that target physical address is own and purpose IP is loop-back address, it just knows this bag to own upper strata, and determines fully by source physical address whom transmit leg is.
The agency who is an agent equipment as a managed device shown in Figure 1, in fact, an agent equipment can be used as agency's (this or even most applications) of a plurality of managed devices, and a managed device also may obtain management information by a plurality of agent equipments.Fig. 2 is exactly the situation of managing the equipment of many no IP addresses by an agent equipment, and the principle of its realization is identical.
Specify again below and how to select loop-back address for use and how to revise problems such as protocol stack IP layer.Because IP stack always comes marking equipment with the IP address, so, in agent equipment, be for the different loop-back address of each managed device distribution, as 127.1.1.1,127.2.3.2, or the like (so long as taking the lead) with 127.Since 127.x.x.x is loop-back address, so loop-back address almost is exhaustless.In managed device, also identify agent equipment (although agent equipment has the IP address, that is towards IP network) with loop-back address.Therefore, need set up a special ARP (address resolution protocol) table in device software, the difference of this table and common ARP table is: the IP address in the list item is a loop-back address.Whenever protocol stack is received when the IP address that network is sent is the bag of loop-back address, check loop-back address ARP table earlier according to the source physical address (the IP loop-back address in the bag is not shown interest in) of bag, if this physical address does not exist, then one of physical address assignments is seen Fig. 3 not by the used loop-back address of other ARP list items for this reason.Distributed the loop-back address of a correspondence for source physical address after, again bag is sent to the upper strata behind the loop-back address that protocol stack should distribute the source IP in the bag of receiving instead, the upper strata thinks that Correspondent Node is this new loop-back address like this.When will give out a contract for a project toward the opposite end in the upper strata later on, will tell IP layer " I will give this loop-back address " to give out a contract for a project.The IP layer is looked into above-mentioned special ARP table again according to this loop-back address, just can obtain correct target physical address, opposite end, and bag is sent out.Because each equipment is independently to carry out for the physical address assignments loop-back address, so the table of the loop-back address ARP in each equipment is mutually different.Though it is different that the loop-back address ARP of each equipment shows, can not make the mistake and confusion, because protocol stack when receiving the IP bag, finds that destination address is that loop-back address is just past and has given upper layer software (applications), specifically be which loop-back address and do not go inspection.From top discussion and Fig. 1, Fig. 2 as can be seen, the present invention does not do any hypothesis to physical link, below is that example illustrates implementation again with the Ethernet switch.
Ethernet switch itself is (do not need the supposing to three layers of routing function of its extra interpolation) that does not need the IP address when working as two layers of forwarding unit.In order to be managed for configuration it by IP network, existing processing mode be need to it dispose three layers of virtual port (here " virtual " be meant this port not with certain physical port of reality to corresponding, but be provided with in the device software), mix IP address and MAC Address for simultaneously this port.If the scheme that the present invention introduced then only needs to select an Ethernet switch as agent equipment, mix three layers of port for it, mix IP address and MAC Address simultaneously, this port is used for communicating by letter with turnkey console.And when communicating by letter between this proxy switch and the switch that does not have configuration of IP address, the bridge address that can use equipment is as physical address, and loop-back address is just used in the IP address.Here need equipment is configured, it is received when target MAC (Media Access Control) address is the bridge address of oneself, can give software with message, thereby can give protocol stack.
Introduce the agency's of application layer specific implementation process again:
● Telnet:Telnet is the agreement that is based upon on the TCP, so need to connect before the communication.After turnkey console and agent equipment have been set up Telnet and have been connected, the telnet data of being sent out (being the configuration order content) do not need all should think agent equipment to transmit, (the noticing that agent equipment oneself also need be managed) that just is used for Configuration Agent equipment oneself.When the user keys in an implication for the order of " I think that the managing physical address is the equipment of XX ", the telnet on the agent equipment will begin really to want to the user with the identity of client that the equipment of that no IP address of managing sends and set up the telnet connection requests.From then on, safeguarding on the agent equipment that two telnet connect.After, the telnet content that all users send, the agency should be forwarded to final managed device from another telnet connection with it, unless user's order implication is " I want to manage another equipment " or " I think administration agent equipment itself ".If the user wants to manage another equipment, then the telnetclient on the agency should disconnect old connection, is established to the telnet connection of another no IP address device again with the client identity.If the user is the beginning administration agent equipment self of looking on the bright side of things, then behind the old telnet client connection closed on the agency, need not build new connection again.
● the HTTP:HTTP agency has special consensus standard (seeing RFC 2068).It is to specify final purpose Web server to realize by the url field in the HTTP request message.Be similar to Telnet, the agency needs a pair of (two) HTTP to connect when work.
● SNMP:SNMP is different with above-mentioned two agreements, and it is based upon on the connectionless UDP.The user can specify final managed device in the OID of SNMP message.When agent equipment is received the SNMP request, the IP address of turnkey console and UDP source port number need be write down and (write down the necessary information that can indicate this request simultaneously, comprise OID and command type, because might act on behalf of and receive a plurality of requests that will transmit at short notice), only in this way, when the equipment of agency is received the SNMP response that managed device beams back, could successfully response message be given to turnkey console.In addition, on agent equipment, wait timeout mechanism should be set,, just overtime record (being above-mentioned OID, command type, this group information of the IP address of webmaster platform and port numbers) be deleted if confiscate the SNMP response message of managed device to certain hour.If in time receive response, just find above-mentioned record, with its deletion.
When finding after agency's application layer the request analysis that the webmaster platform is sent that the webmaster platform is when wanting to manage other equipment of certain physical address, just will begin to communicate by letter with this equipment.Before the communication, at first it will look into above-mentioned special ARP table, and the physical address of seeing this managed device if do not exist, just distributes a still unappropriated loop-back address (and add ARP show) for it whether in this table.Then, just with the IP of this loop-back address as that managed device, like this, the purpose IP that application layer passes to the bag of lower floor is exactly this loop-back address to the application layer on the agent equipment.In ARP, find physical address corresponding with this loop-back address then, beat as the target physical address and mailing in the bag of managed device.
Generally speaking, if use this invention, make following modification to protocol stack and application layer:
1 sets up a special ARP table;
The bag that the 2 couples of purpose IP that receive are loop-back address will be given the upper strata, and before submitting source physical address is distributed a loop-back address, adds the ARP table, and revises source IP address in wrapping with this loop-back address;
The Telnet of 3 agent equipments, HTTP and snmp protocol will add agent functionality.
Claims (5)
1. a no IP address device network management method is characterized in that, comprises following performing step:
1) agency of the equipment of IP address as no IP address device disposed in utilization, and giving does not have physical address equipment disposition physical address;
2) communicating by letter and can pass through IP network between turnkey console and the agency is by the forwarded hop-by-hop realization of IP layer;
3) between agency and the described no IP address device of being managed, by being transmitted by the physical address of the no IP address device of pipe.
2. no IP address device network management method according to claim 1, it is characterized in that, described equipment that has disposed the IP address can be used as the agency of a plurality of no IP address device in the step 1), and perhaps a plurality of described equipment that disposed the IP address can be used as the agency of a no IP address device.
3. no IP address device network management method according to claim 1 is characterized in that, and is when managed device itself does not have physical address, further comprising the steps of before the described step 3):
To physical address that on the path between three layers of adjacent forwarding unit, does not have repetition of managed device configuration.
4. according to claim 1 or 2 or 3 described no IP address device network management methods, it is characterized in that, comprise following processing procedure in the step 3):
A) agency distributes different loop-back addresses for each managed device, and managed device also identifies agent equipment with loop-back address;
B) the transmit leg message that will need to send breaks into the IP bag, and destination address uses the loop-back address that distributes to managed device;
C) set up an address analysis protocol table, the IP address in the list item replaces with loop-back address;
D) when reciever receives that the IP address is the bag of loop-back address, check address analysis protocol table according to the source physical address of bag;
E) if this physical address does not exist, then for this reason one of physical address assignments not by the used loop-back address of other list items; Otherwise commentaries on classics step f);
F) will wrap handing-over debit upper strata behind the loop-back address that the source IP in the bag that will receive distributes instead again and handle, finish forwarding.
5. no IP address device network management method according to claim 1 is characterized in that, uses the bridge address of equipment as its physical address when managed device is Ethernet switch.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB021511233A CN100393039C (en) | 2002-12-02 | 2002-12-02 | Network administration method for no-IP address device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB021511233A CN100393039C (en) | 2002-12-02 | 2002-12-02 | Network administration method for no-IP address device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1505323A true CN1505323A (en) | 2004-06-16 |
| CN100393039C CN100393039C (en) | 2008-06-04 |
Family
ID=34234271
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB021511233A Expired - Lifetime CN100393039C (en) | 2002-12-02 | 2002-12-02 | Network administration method for no-IP address device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100393039C (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100518087C (en) * | 2006-03-03 | 2009-07-22 | 鸿富锦精密工业（深圳）有限公司 | Apparatus and method for managing user terminal equipment |
| CN101917751A (en) * | 2010-09-10 | 2010-12-15 | 重庆金美通信有限责任公司 | IP-free routing method applicable to wireless broadcast channel |
| CN102984175A (en) * | 2012-12-21 | 2013-03-20 | 浙江宇视科技有限公司 | Front-end monitoring equipment without IP and agent device |
| CN102984006A (en) * | 2012-12-06 | 2013-03-20 | 武汉烽火网络有限责任公司 | Network management implementation method based on simple network management protocol |
| CN104247349A (en) * | 2013-03-12 | 2014-12-24 | 华为技术有限公司 | Communication method, device and system |
| WO2015100558A1 (en) * | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Method and apparatus for managing physical address of network device |
| CN111683073A (en) * | 2020-05-29 | 2020-09-18 | 烽火通信科技股份有限公司 | Communication method and system for three-layer application based on MAC |
| CN112929345A (en) * | 2021-01-22 | 2021-06-08 | 英赛克科技（北京）有限公司 | Data transmission method, management server and industrial control firewall |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002335271A (en) * | 2001-05-08 | 2002-11-22 | Yoshihiro Maruyama | Method for disclosing internet server located on private address (ip address) to the internet and system for utilizing the method |
-
2002
- 2002-12-02 CN CNB021511233A patent/CN100393039C/en not_active Expired - Lifetime
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100518087C (en) * | 2006-03-03 | 2009-07-22 | 鸿富锦精密工业（深圳）有限公司 | Apparatus and method for managing user terminal equipment |
| CN101917751A (en) * | 2010-09-10 | 2010-12-15 | 重庆金美通信有限责任公司 | IP-free routing method applicable to wireless broadcast channel |
| CN101917751B (en) * | 2010-09-10 | 2012-09-26 | 重庆金美通信有限责任公司 | IP-free routing method applicable to wireless broadcast channel |
| CN102984006A (en) * | 2012-12-06 | 2013-03-20 | 武汉烽火网络有限责任公司 | Network management implementation method based on simple network management protocol |
| CN102984175B (en) * | 2012-12-21 | 2015-12-09 | 浙江宇视科技有限公司 | A kind of without IP monitoring frontend and a kind of agent apparatus |
| CN102984175A (en) * | 2012-12-21 | 2013-03-20 | 浙江宇视科技有限公司 | Front-end monitoring equipment without IP and agent device |
| CN104247349B (en) * | 2013-03-12 | 2017-09-19 | 华为技术有限公司 | A kind of communication means, apparatus and system |
| CN104247349A (en) * | 2013-03-12 | 2014-12-24 | 华为技术有限公司 | Communication method, device and system |
| WO2015100558A1 (en) * | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Method and apparatus for managing physical address of network device |
| CN105247814A (en) * | 2013-12-30 | 2016-01-13 | 华为技术有限公司 | Method and apparatus for managing physical address of network device |
| CN105247814B (en) * | 2013-12-30 | 2018-09-21 | 华为技术有限公司 | The method and apparatus for managing the physical location of the network equipment |
| US10594590B2 (en) | 2013-12-30 | 2020-03-17 | Huawei Technologies Co., Ltd. | Method and apparatus for managing physical location of network device |
| CN111683073A (en) * | 2020-05-29 | 2020-09-18 | 烽火通信科技股份有限公司 | Communication method and system for three-layer application based on MAC |
| CN112929345A (en) * | 2021-01-22 | 2021-06-08 | 英赛克科技（北京）有限公司 | Data transmission method, management server and industrial control firewall |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100393039C (en) | 2008-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7379458B2 (en) | Server load sharing system | |
| JP3372455B2 (en) | Packet relay control method, packet relay device, and program storage medium | |
| US20040153858A1 (en) | Direct peer-to-peer transmission protocol between two virtual networks | |
| US8898265B2 (en) | Determining data flows in a network | |
| WO2002071720A1 (en) | Addressing method and system for using an anycast address | |
| US20040003099A1 (en) | Bi-directional affinity within a load-balancing multi-node network interface | |
| EP2451125A1 (en) | Method and system for realizing network topology discovery | |
| CN1917512B (en) | Method for establishing direct connected peer-to-peer channel | |
| US6760336B1 (en) | Flow detection scheme to support QoS flows between source and destination nodes | |
| EP1602034A2 (en) | Communications interchange system | |
| US20080205376A1 (en) | Redundant router having load sharing functionality | |
| CN100393039C (en) | Network administration method for no-IP address device | |
| US20050271047A1 (en) | Method and system for managing multiple overlapping address domains | |
| KR100231705B1 (en) | Structure and method of the hybrid gateway to support public and private IP address | |
| US6826623B1 (en) | Detecting a dead gateway for subsequent non-TCP transmission by sending a first TCP packet and deleting an ARP entry associated with the gateway | |
| Panwar | TCP/IP Essentials: A Lab-Based Approach | |
| Cisco | Migration Scenarios | |
| Cisco | Apple Talk | |
| Cisco | AppleTalk Routing Commands | |
| CN101170502B (en) | A method and system for realizing mutual access between stacking members | |
| Cisco | CiscoWorks Blue Features | |
| Cisco | AppleTalk Routing Commands | |
| Cisco | CiscoWorks Blue Maps and SNA View Features | |
| Cisco | AppleTalk Routing Commands | |
| Britton et al. | TCP/IP: The next generation |
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 | ||
| CX01 | Expiry of patent term |
Granted publication date: 20080604 |
|
| CX01 | Expiry of patent term |