WO2015096737A1 - 一种控制网络设备自动开局的方法、设备及系统 - Google Patents

一种控制网络设备自动开局的方法、设备及系统 Download PDF

Info

Publication number
WO2015096737A1
WO2015096737A1 PCT/CN2014/094810 CN2014094810W WO2015096737A1 WO 2015096737 A1 WO2015096737 A1 WO 2015096737A1 CN 2014094810 W CN2014094810 W CN 2014094810W WO 2015096737 A1 WO2015096737 A1 WO 2015096737A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
interface
topology information
address
network device
Prior art date
Application number
PCT/CN2014/094810
Other languages
English (en)
French (fr)
Inventor
张学明
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP14873759.6A priority Critical patent/EP3073676B1/en
Publication of WO2015096737A1 publication Critical patent/WO2015096737A1/zh
Priority to US15/191,822 priority patent/US10091274B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • 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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention belongs to the field of data communication technologies, and in particular, to a method, device and system for controlling automatic start of a network device.
  • a network in a data center area usually consists of multiple network devices, such as multiple core switches and hundreds of access switches.
  • network devices such as multiple core switches and hundreds of access switches.
  • Automatic deployment refers to the process of loading operating system files and/or configuration files to complete related functions and related services when the network device is powered on for the first time.
  • the automatic network device automatic deployment scheme can complete the automatic deployment of the network device according to the media access control (English: media access control, MAC address) address or serial number (English: serial number, abbreviation: SN).
  • FIG. 1 is a flowchart of an implementation of automatically starting a network device.
  • FTP File Transfer Protocol
  • the network device obtains the temporary network protocol (English: Internet Protocol, IP address) sent by the DHCP server, the gateway address of the FTP server, the IP address of the FTP server, and the minimum configuration file name;
  • the temporary network protocol English: Internet Protocol, IP address
  • the network device obtains a minimum configuration file from the FTP server.
  • the network device starts with a minimum configuration file
  • the DHCP server determines whether data transmitted through the Simple Network Management Protocol (English: Simple Network Management Protocol, abbreviation: SNMP) can reach the network device;
  • Simple Network Management Protocol English: Simple Network Management Protocol, abbreviation: SNMP
  • the server sends a request for obtaining the MAC address or the SN of the network device
  • the network device returns its MAC address or SN
  • the DHCP server sends the information about the file transfer protocol FTP to the network device, and the identifier of the operating system file and/or the identifier of the configuration file required for the deployment, so that the network device establishes an FTP connection with the FTP server. Obtain operating system files and/or configuration files in the FTP server.
  • the network device automatically starts the solution.
  • the network device is replaced, because the MAC address or SN of the network device changes, the original plan needs to be redone, and the network device cannot be plug and play. Therefore, it is not applicable.
  • the network device replaces the scenario and cannot be automatically started when the network device is replaced.
  • the object of the present invention is to provide a method and a device for controlling the automatic deployment of a network device, aiming at solving the problem that the network device automatically starts the deployment, and the problem of automatic deployment cannot be achieved when the network device is replaced.
  • a method for a server to control automatic network deployment of a network device includes:
  • Obtaining network topology information of the network device in the live network where the network topology information includes an interface and an IP address of the uplink device directly connected to the network device;
  • the network management device sends, to the network device, information that enables the Simple File Transfer Protocol (TFTP) or File Transfer Protocol (FTP), and the identifier of the operating system file and/or the identifier of the configuration file required for the deployment, so that the network
  • the device establishes a TFTP connection or an FTP connection with the TFTP server or the FTP server, and obtains operating system files and/or configuration files on the TFTP server or the FTP server.
  • the interface includes one or a combination of a physical interface and a virtual local area network VLAN interface to which the physical interface belongs.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • the acquiring network topology information of the network device in the live network includes:
  • the network management device obtains an interface table of the uplink device, and an address resolution protocol ARP table of the network device, where the interface table of the uplink device includes a correspondence between each interface of the uplink device and a media access control MAC address of each interface.
  • the ARP table of the network device includes an IP address of an interface directly connected to the network device and a MAC address of an interface directly connected to the network device by the uplink device;
  • the network topology information and the preset network topology information in the current network are detected, whether Matches, including:
  • the physical interface of the network topology information in the live network the VLAN interface and the IP address to which the physical interface belongs, and the preset physical interface, the VLAN interface to which the preset physical interface belongs, and the IP address of the uplink device match.
  • the network topology information further includes a device model And detecting whether the network topology information in the current network and the preset network topology information match, further including:
  • a device for controlling automatic deployment of a network device includes:
  • a first acquiring unit configured to acquire network topology information of a network device in an existing network, where the network topology information includes an interface and an IP address of an uplink device directly connected to the network device;
  • a first detecting unit configured to detect whether network topology information in the current network and preset network topology information are matched
  • the network management device sends, to the network device, information that enables a simple file transfer protocol TFTP or a file transfer protocol FTP, and an identifier of an operating system file and/or a configuration file identifier required for the deployment, so that Establishing a TFTP connection or an FTP connection with the TFTP server or the FTP server, and acquiring an operating system file and/or a configuration file in the TFTP server or the FTP server;
  • the interface includes one or a combination of a physical interface and a virtual local area network VLAN interface to which the physical interface belongs.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • the first acquiring unit is further configured to obtain an interface table of an uplink device, and an address resolution protocol ARP table of the network device, where the uplink device is The interface table includes the correspondence between the respective interfaces of the uplink device and the media access control MAC addresses of the respective interfaces, and the ARP table of the network device includes an IP of an interface directly connected to the network device by the uplink device. Corresponding relationship between the address and the MAC address of the interface directly connected to the network device by the uplink device;
  • the IP address of the interface directly connected to the network device is obtained in the ARP table of the network device.
  • the detecting unit is further configured to detect a physical interface and an IP address of the network topology information in the existing network, and the preset physical interface and the IP address. Whether it matches; or,
  • the detecting unit it is further used to detect whether the device model in the network topology information matches the device model in the preset network topology information.
  • a third aspect is a device for controlling automatic opening of a network device, where the device includes a processor, a memory, and a communication interface, wherein the processor, the communication interface, and the memory complete communication with each other through the bus;
  • the communication interface is configured to communicate with other communication devices
  • the processor is configured to execute a program
  • the memory is configured to store a program
  • the program is configured to obtain the network topology information of the network device in the live network, where the network topology information includes an interface and an IP address of the uplink device directly connected to the network device, where the interface includes a physical interface, and the physical interface belongs to the physical interface.
  • the network topology information includes an interface and an IP address of the uplink device directly connected to the network device, where the interface includes a physical interface, and the physical interface belongs to the physical interface.
  • the network management device sends, to the network device, information that enables a simple file transfer protocol TFTP or a file transfer protocol FTP, and an identifier of an operating system file and/or a configuration file identifier required for the deployment, so as to enable
  • the network device establishes a TFTP connection or an FTP connection with the TFTP server or the FTP server, and obtains an operating system file and/or a configuration file in the TFTP server or the FTP server.
  • a system for controlling automatic deployment of a network device includes: a device for controlling automatic opening of a network device, and at least one network device, at least one uplink device, wherein the uplink device is directly connected to the network device. .
  • the network topology information in the existing network and the preset network topology information are matched, and the scheme for automatically starting the device is solved, and the problem of automatic deployment cannot be achieved when the network device spare parts are replaced, so that the same location is Network equipment, plug and play when it is automatically opened.
  • FIG. 1 is a flowchart of an implementation of automatically starting a network device
  • FIG. 2 is a flowchart of an implementation of a method for controlling automatic deployment of a network device according to an embodiment of the present invention
  • FIG. 3 is a diagram showing a preferred connection relationship between a network device and an uplink device according to an embodiment of the present invention
  • FIG. 4 is a table including preset network topology information according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a preferred embodiment of transmitting an operating system file and/or a configuration file when the network topology information includes an interface and an IP address of an uplink device directly connected to the network device according to the embodiment of the present disclosure
  • FIG. 6 is a flowchart of a preferred embodiment of transmitting an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface, an IP address, and a device model of the uplink device directly connected to the network device;
  • FIG. 7 is a flow chart showing another preferred implementation of transmitting an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface and an IP address of an uplink device directly connected to the network device;
  • FIG. 8 is another preferred implementation flow of sending an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface, an IP address, and a device model of the uplink device directly connected to the network device.
  • FIG. 9 is a device for controlling automatic startup of a network device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an apparatus for controlling automatic opening of a network device according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of an implementation of a method for controlling automatic deployment of a network device according to an embodiment of the present invention, which is described in detail as follows:
  • step S201 the network management device acquires network topology information of the network device in the live network, where the network topology information includes an interface and an IP address of the uplink device directly connected to the network device;
  • the live network represents the network in practice.
  • the network device includes a network switch, a router, and an optical network terminal (English: optical network terminal, abbreviation: ONT).
  • the uplink device includes a network switch, a router, and an optical line terminal (English: optical line terminal, abbreviation: OLT).
  • the network device refers to a device that has not completed the deployment.
  • the uplink device refers to the device that has completed the deployment configuration.
  • the direct connection refers to the connection mode in which the network device directly connects to the uplink device without passing through other network devices.
  • Embodiment 2 The implementation flow of obtaining the network topology information of the network device in the live network is described in Embodiment 2.
  • step S202 the network management device detects whether the network topology information in the existing network and the preset network topology information match.
  • the network topology information includes an interface and an IP address of an uplink device directly connected to the network device.
  • the interface includes one of a physical interface of an uplink device directly connected to the network device, a virtual local area network (English: Virtual Local Area Network, abbreviation: VLAN) interface, or a combination thereof.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • the physical interface of the uplink device that is directly connected to the network device refers to a physical interface that is directly connected to the network device and is located in the uplink device.
  • the VLAN interface of the uplink device that is directly connected to the network device refers to the VLAN interface that the physical interface that is directly connected to the network device belongs to.
  • the VLAN interface can complete the link layer forwarding inside the VLAN. At the same time, it can participate in network layer forwarding because it has IP attributes.
  • the physical interface directly connected to the network device may be one or more.
  • FIG. 3 is a diagram showing a preferred connection relationship between a network device and an uplink device according to an embodiment of the present invention.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • the fixed IP address is also the IP address in the configuration file.
  • the network device receives the dynamic IP address assigned by the network management device in the current network, and configures the address as a dynamic IP address.
  • the network device extracts the IP address in the configuration file and uses extraction.
  • the IP address to be replaced replaces the previously configured temporary IP address.
  • the IP address of the network device is the IP address in the configuration file, which is the fixed IP address in the current network.
  • the network device that has completed the deployment configuration can be used as the uplink device to participate in the configuration process of the device that has not completed the deployment.
  • step S203 if the network device matches, the network management device sends a Trivial File Transfer Protocol (TFTP) or a file transfer protocol (English: File Transfer Protocol, abbreviation: FTP) to the network device.
  • TFTP Trivial File Transfer Protocol
  • FTP File Transfer Protocol
  • the device uses the FTP protocol to obtain an operating system file or a configuration file.
  • the essence is that the device first establishes an FTP connection with the FTP server, and then uses the command get in the FTP protocol to obtain the operating system according to the operating system file and/or the identifier of the configuration file. File and / or configuration file.
  • the operating system file is a binary file.
  • the network device loads the file when it is started. It is used to drive and schedule all the hardware resources of the network, and complete the forwarding of data packets and protocol packets to implement communication between network devices.
  • the configuration file is a file that defines the configuration parameters of the device, such as the IP address, VLAN, default route, and login parameters. After the network device starts according to the operating system file, configure the parameters according to the configuration file.
  • the operating system files and/or configuration files may exist in a TFTP or FTP server.
  • the corresponding relationship between the operating system file and/or the configuration file and the preset network topology information is pre-established in the network management device, and the operating system file and/or the configuration file stored in the FTP server may be invoked according to the corresponding relationship between the two. Identifies the identity of the operating system file and/or configuration file to the network device.
  • Operating system files and/or configuration files can also be present in the network management device.
  • the network device can load the operating system file and establish an operating system after receiving the operating system file.
  • the network device can complete the configuration of the related parameters according to the configuration command in the configuration file.
  • the network device can load the version, establish an operating system, and complete the configuration of related parameters through the configuration file. Access to the network.
  • the network topology information of the network device in the live network is consistent with the preset network topology information, that is, the same uplink device and the same uplink device interface.
  • Sending operating system files and/or configuration files to the network device saves the cost of the automatic deployment configuration, saves the time for automatic deployment, improves the efficiency of automatic deployment, and automatically starts when the network device is replaced.
  • the acquiring network topology information of a network device in an existing network includes:
  • the network management device obtains an interface table of the uplink device, and an address resolution protocol ARP table of the network device, where the interface table of the uplink device includes a correspondence between each interface of the uplink device and a media access control MAC address of each interface.
  • the ARP table of the network device includes an IP address of an interface directly connected to the network device and a MAC address of an interface directly connected to the network device by the uplink device;
  • the network management device sends an interface table acquisition request to the uplink device in the current network, so that each uplink device returns an interface table after receiving the interface table.
  • the network management device sends an ARP table acquisition request to the uplink device and the network device in the current network, so that each uplink device and the network device receive the ARP table acquisition request, and then return to the ARP table.
  • the request to obtain the interface table is as follows:
  • the protocol used is snmp, the command is get, and if Descr is the description of the interface.
  • the physical interface is active. Only the interface whose interface status is active is obtained.
  • the request for obtaining the ARP table is as follows:
  • the protocol used is snmp, the command is get, and the ipAdEntIfIndex is the device interface index.
  • the network management device receives the interface table returned by the uplink device.
  • the interface table includes the IP address of the uplink device, the MAC address of the physical interface of the uplink device, and the VLAN interface of the uplink device.
  • the network management device receives the ARP table (hereinafter referred to as the first ARP table) returned by the network device, and the first ARP table includes the MAC address (hereinafter referred to as the first MAC address) of the interface directly connected to the network device by the uplink device.
  • the ARP table hereinafter referred to as the first ARP table
  • the first ARP table includes the MAC address (hereinafter referred to as the first MAC address) of the interface directly connected to the network device by the uplink device.
  • the network management device receives the interface table returned by the uplink device, and obtains a MAC address (hereinafter referred to as a second MAC address) in the returned interface table.
  • a MAC address hereinafter referred to as a second MAC address
  • the network management device detects whether there is a common MAC address in the first MAC address of the first ARP table and the second MAC address of the interface table.
  • the network device storing the first ARP table and the uplink device indicating the interface table where the second MAC address is stored are directly connected, and the third MAC address is MAC address of the interface of the upstream device directly connected to the network device.
  • the network management device queries the physical interface corresponding to the third MAC address according to the third MAC address in the interface table returned by the uplink device, where the physical interface is a physical interface of the uplink device directly connected to the network device.
  • the network management device queries the VLAN interface corresponding to the third MAC address of the network device according to the third MAC address in the interface table returned by the uplink device, where the VLAN interface is a VLAN interface to which the physical interface of the uplink device directly connected to the network device belongs.
  • the network management device obtains the uplink device by using the third MAC address in the ARP table returned by the network device according to the mapping between the IP address of the interface directly connected to the network device and the MAC address of the interface directly connected to the network device.
  • IP address of the interface directly connected to the network device is the IP address of the interface directly connected to the network device by the upstream device.
  • the network management device When a network device is used to replace another network device, the network management device sends an interface table acquisition request to the uplink device in the current network, so that each uplink device returns an interface table after receiving the interface table.
  • the network management device sends an ARP table acquisition request to the replaced network device in the live network, so that the network device receives the request. After the ARP table obtains the request, it returns its ARP table.
  • the network management device receives the ARP table returned by the replaced network device (hereinafter referred to as the fourth ARP table), and the fourth ARP table includes the MAC address of the interface directly connected between the uplink device and the replaced network device (hereinafter referred to as the fourth MAC address).
  • the network management device receives the interface table returned by the uplink device, and obtains a MAC address (hereinafter referred to as a second MAC address) in the returned interface table.
  • a MAC address hereinafter referred to as a second MAC address
  • the network management device detects whether there is a common MAC address in the first MAC address of the first ARP table and the second MAC address of the interface table.
  • the network device storing the first ARP table and the uplink device indicating the interface table where the second MAC address is stored are directly connected, and the third MAC address is MAC address of the interface of the upstream device directly connected to the network device.
  • the ARP table returned by the replaced network device does not change, and the interface table returned by the uplink does not change. Therefore, the common MAC address of the first ARP table and the interface table does not change, that is, the third MAC address does not change. Therefore, the physical interface, the VLAN interface, and the IP address of the physical interface of the third MAC address are not changed. Therefore, the network topology information of the replaced network device in the live network is also unchanged. Therefore, in the present invention, the matching result of detecting whether the network topology information of the network device in the existing network matches the preset network topology information does not change, so that the TFTP or file for enabling the simple file transfer protocol can be subsequently sent to the network device.
  • the information of the FTP protocol of the transport protocol, and the identifier of the operating system file and/or the identifier of the configuration file required for the deployment Therefore, even if the MAC address or SN of the network device is changed, the original plan does not need to be redone, so the network can be implemented.
  • the device is plug-and-play, so it is suitable for the network device replacement scenario, and can automatically start when the network device is replaced.
  • the first MAC address, the second MAC address, the third MAC address, and the fourth MAC address all refer to the MAC address of the physical interface.
  • detecting whether the network topology information in the existing network and the preset network topology information match includes:
  • a physical interface that detects network topology information in the live network, a VLAN interface and an IP address to which the physical interface belongs. Whether it matches the preset physical interface, the VLAN interface to which the preset physical interface belongs, and the uplink device IP address.
  • the network topology information in the existing network and the preset network topology information are detected, and there are three solutions.
  • the first solution is to check whether the physical interface and IP address of the network topology information in the live network match the preset physical interface and IP address.
  • the IP address of the network topology information in the current network is matched with the preset IP address, indicating that the uplink device accessed in the current network is a preset uplink device.
  • the operating system file and/or configuration file is obtained only when the same physical interface of the same upstream device directly connected to the network device before the replacement is accessed.
  • the second solution is to check whether the VLAN interface and IP address of the physical interface of the network topology information in the live network match the VLAN interface and IP address of the preset physical interface.
  • the VLAN interface of the network topology information in the current network matches the preset VLAN interface, the port that is accessed is correct, and the VLAN interface of the uplink device that is preset is accessed.
  • the existing network devices access the multiple physical interfaces of the same VLAN interface that are directly connected to the previous network device, and the operating system files and/or configuration files are obtained.
  • the third solution is to detect the physical interface of the network topology information in the live network, the VLAN interface and IP address to which the physical interface belongs, and the preset physical interface, the VLAN interface to which the preset physical interface belongs, and the uplink device IP address. , whether it matches.
  • the physical interface to which the physical interface belongs is correct.
  • the existing network device accesses the same physical interface of the same VLAN interface that is directly connected to the previous network device, and the operating system file and/or configuration file is obtained.
  • the second solution is preferred, because in actual applications, when multiple physical interfaces correspond to one VLAN interface, one of the multiple physical interfaces can select one of the physical interfaces to access the network, so that it has flexibility. Suitable for access to network devices.
  • the detecting whether the network topology information in the current network and the preset network topology information match further includes :
  • the device model of the network device that needs to be automatically opened is stored.
  • the network management device sends a device model acquisition request to the network device in the current network, so that the network device returns the device model after receiving the device model acquisition request.
  • the device model acquisition request is as follows:
  • the protocol used is SNMP, the command is get, and the sysObjectID is the system object identifier defined by the vendor.
  • the first solution when detecting the physical interface and IP address of the network topology information in the live network, and the preset physical interface and IP address, the device model and the preset network topology of the network topology information in the live network are also detected. Whether the device models in the information match, that is, there are three matching items, namely physical interface, IP address, and device model, and all three matching items need to be matched.
  • the second solution detects the VLAN interface and IP address of the physical interface of the network topology information in the live network, and detects the network in the live network when the VLAN interface and IP address to which the preset physical interface belongs are matched. Whether the device model of the topology information matches the device model in the preset network topology information, that is, it has three matching items: VLAN interface, IP address, and device model. All three matching items need to be matched.
  • the third solution is to detect the physical interface of the network topology information in the live network, the VLAN interface and IP address to which the physical interface belongs, and the preset physical interface, the VLAN interface to which the preset physical interface belongs, and the uplink device IP address. If it matches, it also checks whether the device model of the network topology information on the live network and the device model in the preset network topology information match, that is, there are four matching items, namely VLAN interface, IP address, and device model. , physical interface, all four matches need to match.
  • the network topology information of the network device in the live network is consistent with the preset network topology information, that is, the location and device model of the network device in the network are not changed.
  • Send the operating system file and/or configuration file to the network device so that the network device can complete the automatic deployment configuration, so that the same device model network device in the same location can be plugged and used automatically when the network device is started, saving the cost of the automatic deployment configuration and saving the automatic deployment.
  • the configuration time can be automatically started when the network device spare parts are replaced, which improves the efficiency of the automatic deployment configuration.
  • FIG. 4 is a table including preset network topology information according to an embodiment of the present invention.
  • the device type of the network device is S2, and the network device is connected to the physical interfaces of the two uplink devices.
  • the physical interface of the first uplink device is GE 1/0/1 and the IP address is Agg_ip_1, VLAN interface is 1000, the physical interface of the second uplink device is GE2/0/3, the IP address is Agg_ip_2, and the VLAN interface is 1000.
  • the VLAN interface of the uplink device is 1000, and the IP addresses of the uplink device are Agg_ip_1 and Agg_ip_2, it indicates that the two match.
  • the operating system file S2.bin is sent to the network device, and the configuration file Startup_config1.cfg.
  • the automatic deployment of network devices of different models in the same location is avoided, and the automatic deployment of network devices in different locations of the same model is avoided, so that the same type of network device in the same location is automatically Plug and play at the beginning of the deployment, saving the cost of the automatic deployment configuration, saving the time for the automatic deployment configuration, and improving the efficiency of the automatic deployment configuration, and automatically starting the installation when the equipment spare parts are replaced.
  • FIG. 5 is a flowchart showing a preferred implementation process of transmitting an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface and an IP address of an uplink device directly connected to the network device. as follows:
  • the network management device Based on the network topology information, the network management device pre-establishes the correspondence between the operating system files and/or configuration files and the preset network topology information, and stores the corresponding operating system files and/or configuration files in the file transfer (File Transfer Protocol).
  • the network topology information includes an interface and an IP address of the uplink device directly connected to the network device.
  • the network device receives the dynamic IP address sent by the network management device, the gateway address and IP address of the FTP server, and the minimum configuration file name.
  • the network device obtains a minimum configuration file in the file transfer server
  • the network device starts with a minimum configuration file
  • the network management device determines whether the data transmitted by the simple network management protocol SNMP can reach the network device
  • the network management device obtains network topology information of the network device in the live network, where the network extension The information includes the interface, the IP address, and the device model of the uplink device directly connected to the network device, and detects whether the network topology information in the current network and the preset network topology information match.
  • the network management device sends the information about the file transfer protocol FTP to the network device, and the identifier of the operating system file and/or the identifier of the configuration file required for the deployment, so that the network device establishes an FTP connection with the FTP server. Obtain operating system files and/or configuration files in the FTP server.
  • FIG. 6 is a schematic diagram of transmitting an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface, an IP address, and a device model of the uplink device directly connected to the network device.
  • the implementation flow chart is detailed as follows:
  • the network topology information Based on the network topology information, pre-establish the corresponding relationship between the operating system file and/or the configuration file and the preset network topology information, and store the operating system file and/or configuration corresponding to the preset network topology information on the network management device.
  • the file is stored in a File Transfer Protocol (FTP) server.
  • FTP File Transfer Protocol
  • the network topology information includes an interface of the uplink device directly connected to the network device, an IP address, and a device model of the network device.
  • the network device receives the dynamic IP address sent by the network management device, the gateway address and IP address of the FTP server, and the minimum configuration file name.
  • the network device obtains a minimum configuration file in the file transfer server
  • the network device starts with a minimum configuration file
  • the network management device determines whether the data transmitted by the simple network management protocol SNMP can reach the network device
  • the network management device obtains network topology information of the network device in the live network, where the network topology information includes an interface, an IP address, and a device model of the uplink device directly connected to the network device, and detects the current network. Whether the network topology information matches the preset network topology information;
  • the network management device sends the information about the file transfer protocol FTP to the network device, and the identifier of the operating system file and/or the identifier of the configuration file required for the deployment, so that the network device establishes an FTP connection with the FTP server. Obtain operating system files and/or configuration files in the FTP server.
  • FIG. 7 is a flowchart of another preferred implementation of transmitting an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface and an IP address of an uplink device directly connected to the network device.
  • the operating system files and/or configuration files are stored on the network management device.
  • FIG. 8 is a schematic diagram of sending an operating system file and/or a configuration file when the network topology information provided by the embodiment of the present invention includes an interface, an IP address, and a device model of the uplink device directly connected to the network device. Good implementation flow chart.
  • the operating system files and/or configuration files are stored on the network management device.
  • FIG. 9 is a device for controlling automatic deployment of a network device according to an embodiment of the present invention.
  • FIG. 9 is a device for controlling automatic deployment of a network device according to an embodiment of the present invention.
  • parts related to the embodiment are shown, which are as follows:
  • the first obtaining unit 91 is configured to acquire network topology information of the network device in the live network, where the network topology information includes an interface and an IP address of the uplink device directly connected to the network device;
  • the first detecting unit 92 is configured to detect whether the network topology information in the existing network and the preset network topology information match.
  • the sending unit 93 is configured to: if the matching, the network management device sends, to the network device, information that enables a simple file transfer protocol TFTP or a file transfer protocol FTP, and an identifier of the operating system file and/or an identifier of the configuration file required for the deployment. So that the network device establishes a TFTP/FTP connection with the TFTP/FTP server, and obtains an operating system file and/or a configuration file in the TFTP server or the FTP server;
  • the interface includes one or a combination of a physical interface and a virtual local area network VLAN interface to which the physical interface belongs.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • the sending unit may be located in a device that stores an operating system file and/or a configuration file, including but not limited to a DHCP server and an FTP server.
  • the first acquiring unit is further configured to acquire an interface table of the uplink device, and an address resolution protocol ARP table of the network device, where the interface table of the uplink device includes each interface of the uplink device.
  • the ARP table of the network device includes an IP address of the interface directly connected to the uplink device and the network device, and the uplink device and the network device, respectively, corresponding to a media access control MAC address of each of the interfaces. The correspondence between the MAC addresses of the directly connected interfaces;
  • the IP address of the interface directly connected to the network device is obtained in the ARP table of the network device.
  • the detecting unit is further configured to detect whether a physical interface and an IP address of the network topology information in the live network match the preset physical interface and the IP address; or
  • the detecting unit is further configured to detect whether the device model in the network topology information and the device model in the preset network topology information match.
  • FIG. 10 is a schematic structural diagram of a device for controlling automatic deployment of a network device according to an embodiment of the present invention.
  • the device includes a processor (English: processor) 101, and a communication interface (English: Communications Interface 102, memory (English) :memory) 103, bus 104.
  • the processor 101, the communication interface 102, and the memory 103 complete communication with each other via the bus 104.
  • a communication interface 102 configured to communicate with other communication devices
  • the processor 101 is configured to execute a program.
  • the program can include program code, the program code including computer operating instructions.
  • the processor 103 may be a central processing unit (English: central processing unit, abbreviation: CPU.
  • the memory 103 is configured to store a program.
  • the program is configured to obtain network topology information of a network device in an existing network, where the network topology information includes an interface and an IP address of an uplink device directly connected to the network device;
  • the network management device sends, to the network device, information that enables a simple file transfer protocol TFTP or a file transfer protocol FTP, and an identifier of an operating system file and/or a configuration file identifier required for the deployment, so as to enable Establishing a TFTP connection or an FTP connection with the TFTP server or the FTP server, and obtaining an operating system file and/or a configuration file in the TFTP server or the FTP server;
  • the interface includes one or a combination of a physical interface and a virtual local area network VLAN interface to which the physical interface belongs.
  • the IP address is an IP address fixed by the uplink device in the live network.
  • a system for controlling automatic deployment of a network device including a device for controlling automatic opening of a network device, and at least A network device, at least one uplink device, wherein the uplink device is connected to the network device by using a direct connection.
  • the present invention can be implemented by means of software plus necessary general hardware.
  • the technical solution of the present invention which is essential or contributes to the prior art, can be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • a hard disk or optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本发明适用于数据通信技术领域，一种控制网络设备自动开局的方法、设备及系统，该方法包括：获取网络设备在现网中的网络拓扑信息，该网络拓扑信息包括与该网络设备直接连接的上行设备的接口和IP地址；检测该现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；若匹配，该网管设备向该网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使该网络设备获取操作系统文件和/或配置文件。本发明通过检测现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，解决了在网络设备备件替换时不能做到自动开局的问题，使得同一位置的网络设备，在自动开局时即插即用。

Description

一种控制网络设备自动开局的方法、设备及系统
本申请要求于2013年12月26日提交中国专利局、申请号为201310732900.0、发明名称为“一种控制网络设备自动开局的方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明属于数据通信技术领域，尤其涉及一种控制网络设备自动开局的方法、设备及系统。
背景技术
一个数据中心区域的网络，通常由多个网络设备组成，例如多台核心交换机，上百台接入交换机组成。当在网络里添加一个网络设备时，需要对网络设备进行自动开局(英文：provisioning)。自动开局是指在网络设备第一次上电时，加载操作系统文件和/或配置文件，完成相关功能和相关业务的配置的过程。
通常的网络设备自动开局的方案，可根据介质访问控制(英文：media access control，缩写：MAC)地址或序列号(英文：serial number，缩写：SN)完成网络设备的自动开局。
参考图1，图1是网络设备自动开局的实施流程图。
1、预先建立操作系统文件和预先采集的MAC地址的对应关系，或者预先建立配置文件和预先采集的SN的对应关系,将对应关系存放在动态主机配置协议(英文：Dynamic Host Configuration Protocol，缩写：DHCP)服务器上，并将与MAC地址或SN对应的操作系统文件和配置文件，存放在文件传输协议(File Transfer Protocol，FTP)服务器上；
2、现场安装网络设备，网络设备上电启动；
3、网络设备获取DHCP服务器发送的临时网络协议(英文：Internet Protocol，缩写：IP)地址、FTP服务器的网关地址和FTP服务器的IP地址和最小配置文件名字；
5、网络设备从FTP服务器获取最小配置文件；
6、网络设备使用最小配置文件启动；
7、DHCP服务器判断通过简单网络管理协议(英文：Simple Network Management Protocol，缩写：SNMP)传输的数据是否可以到达网络设备；
8、当通过SNMP传输的数据可以到达网络设备时，服务器发送获取网络设备的MAC地址或SN的请求；
9、网络设备返回其MAC地址或SN；
10、查找与MAC地址或SN号相对应的版本文件、配置文件，
11、DHCP服务器向网络设备发送启用文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与FTP服务器建立一个FTP连接，在所述FTP服务器中获取操作系统文件和/或配置文件。
然而，该网络设备自动开局的方案，在网络设备替换时，因为网络设备的MAC地址或SN变了，原先的规划需要重做、不能做到网络设备的即插即用，因此，不适用于网络设备替换场景，在网络设备替换时不能做到自动开局。
发明内容
本发明的目的在于提供一种控制网络设备自动开局的方法及设备，旨在解决网络设备自动开局的方案，在网络设备备件替换时不能做到自动开局的问题。
第一方面，一种服务器控制网络设备自动开局的方法，包括：
获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
结合第一方面，在第一方面的第一种可能的实现方式中，所述获取网络设备在现网中的网络拓扑信息，包括：
网管设备获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，包括：
检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
结合第一方面，以及第一方面的第一至第二种可能的实现方式中的任意一个，在第一方面的第三种可能的实现方式中，当所述网络拓扑信息还包括设备型号时，所述检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，进一步还包括：
检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
第二方面，一种控制网络设备自动开局的设备，包括：
第一获取单元，用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
第一检测单元，用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
发送单元，若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
结合第二方面，在第二方面的第一种可能的实现方式中，所述第一获取单元还用于获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
还用于根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
还用于在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
还用于在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
结合第二方面，在第二方面的第二种可能的实现方式中，所述检测单元还用于检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
还用于检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
还用于检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
结合第二方面或结合第二方面第一至第二种可能的实现方式，在第一方面的第三种可能的实现方式中，当所述网络拓扑信息还包括设备型号时，所述检测单元进一步用于检测网络拓扑信息中的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
第三方面，一种控制网络设备自动开局的设备，所述设备包括处理器、存储器、通信接口，其中处理器、通信接口、存储器通过总线完成相互间的通信；
所述通信接口，用于与其他通信设备进行通信；
所述处理器，用于执行程序；
所述存储器，用于存储程序；
其中程序用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址，所述接口包括物理接口、所述物理接口所属的虚拟局域网VLAN接口之一或其组合；
用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
用于若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件。
第四方面，一种控制网络设备自动开局的系统，包括控制网络设备自动开局的设备以及至少一个网络设备，至少一个上行设备，其中所述上行设备与所述网络设备采用直接连接的方式进行连接。
在本发明中，检测现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，解决了设备自动开局的方案，在网络设备备件替换时不能做到自动开局的问题，使得同一位置的网络设备，在自动开局时即插即用。
附图说明
图1是网络设备自动开局的实施流程图；
图2是本发明实施例提供的一种控制网络设备自动开局的方法的实现流程图；
图3示出了本发明实施例提供的网络设备与上行设备较佳的连接关系图；
图4是本发明实施例提供的包括预置的网络拓扑信息的表格；
图5是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址时，发送操作系统文件和/或配置文件较佳的实施流程图；
图6是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址以及网络设备的设备型号时，发送操作系统文件和/或配置文件较佳的实施流程图；
图7是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址时，发送操作系统文件和/或配置文件另一个较佳的实施流程图；
图8是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址以及网络设备的设备型号时，发送操作系统文件和/或配置文件另一个较佳的实施流程图；
图9是本发明实施例提供的一种控制网络设备自动开局的设备；
图10是本发明实施例提供的一种控制网络设备自动开局的设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
实施例一
参考图2，图2是本发明实施例提供的一种控制网络设备自动开局的方法的实现流程图，详述如下：
在步骤S201中，网管设备获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
其中，现网表示在实际中的网络。
在本实施例中，网络设备包括网络交换机、路由器、光网络终端(英文：optical network terminal，缩写：ONT)。
在本实施例中，上行设备包括网络交换机、路由器、光线路终端(英文：optical line terminal，缩写：OLT)。
其中，网络设备是指未完成开局的设备。上行设备是指完成了开局配置的设备。
其中，直接连接指的是该网络设备不经过其他的网络设备，直接连接到上行设备的连接方式。
关于获取网络设备在现网中的网络拓扑信息的实施流程，在实施例二进行描述。
在步骤S202中，网管设备检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
其中，网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址。
其中，在步骤S201和步骤S202，所述接口包括与所述网络设备直接连接的上行设备的物理接口、虚拟局域网(英文：Virtual Local Area Network，缩写：VLAN)接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
其中，与网络设备直接连接的上行设备的物理接口,是指位于上行设备内，与网络设备直接连接的物理接口。
其中，与网络设备直接连接的上行设备的VLAN接口，是指位于上行设备内，与网络设备直接连接的物理接口所属的VLAN接口。VLAN接口作为一种基于VLAN设置的具有IP属性的逻辑接口，即能完成VLAN内部的链路层转发，同时由于其具备IP属性，因而又可以参与网络层转发。
需要进行说明的，与网络设备直接连接的物理接口可以是一个或多个。
参考图3，图3示出了本发明实施例提供的网络设备与上行设备较佳的连接关系图。
其中，IP地址为上行设备在现网中固定的IP地址。固定的IP地址也就是配置文件中的IP地址。
例如，开局时，网络设备接收现网中网管设备分配的动态IP地址，配置其地址为动态IP地址，在开局的过程中，网络设备获取到配置文件后，提取配置文件中IP地址，采用提取到的IP地址替换之前配置的临时IP地址，替换后，网络设备的IP地址为配置文件中的IP地址，也就是现网中固定的IP地址。完成了开局配置的网络设备可以作为上行设备参与未完成开局的设备的配置过程。
关于检测现网中的网络拓扑信息与预置的网络拓扑信息的实施流程，在实施例三进行描述，在此不做描述。
在步骤S203中，若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议(英文：Trivial File Transfer Protocol，缩写：TFTP)或文件传输协议(英文：File Transfer Protocol，缩写：FTP)协议的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，获取操作系统文件和/或配置文件。
其中，设备使用FTP协议获取操作系统文件或配置文件，实质就是设备先与FTP服务器建立一个FTP连接，然后使用FTP协议中的命令get，根据操作系统文件和/或配置文件的标识，获取操作系统文件和/或配置文件。
其中，操作系统文件是一个二进制文件，网络设备启动时加载该文件，用于驱动、调度网络的所有硬件资源，完成数据报文与协议报文的转发，实现网络设备之间的彼此通信。
其中，配置文件是一个定义了设备的配置参数的文件，如IP地址、VLAN、缺省路由、登录参数等，网络设备根据操作系统文件启动之后，根据该配置文件，配置有关参数。
其中，操作系统文件和/或配置文件可存在TFTP或FTP服务器中。
其中，在网管设备中预先建立操作系统文件和/或配置文件与预置的网络拓扑信息的对应关系，可根据两者的对应关系，调用存放在FTP服务器的操作系统文件和/或配置文件的标识，向网络设备发送操作系统文件和/或配置文件的标识。
操作系统文件和/或配置文件也可以存在网管设备中。
当网络设备中没有存放操作系统文件时，向网络设备发送操作系统文件时，网络设备接收操作系统文件后，可加载操作系统文件，建立操作系统。
当网络设备中没有存放配置文件时，当向网络设备发送配置文件时，网络设备接收配置文件后，可根据配置文件中的配置指令，完成相关参数的配置。
当网络设备中没有存放操作系统文件和配置文件时，当向网络设备发送操作系统文件和配置文件时，网络设备接收后，可加载版本，建立操作系统，通过配置文件，完成相关参数的配置，接入网络。
在本实施例中，若匹配，表示网络设备在现网中的网络拓扑信息与预置的网络拓扑信息一致，也就是同样的上行设备，同样的上行设备的接口。向网络设备发送操作系统文件和/或配置文件，节省自动开局配置的成本，节省自动开局配置的时间，并提高自动开局配置的效率，且在网络设备备件替换时可做到自动开局。
实施例二
作为本发明的一个实施例，所述获取网络设备在现网中的网络拓扑信息，包括：
网管设备获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
其中，网管设备向现网中的上行设备发送接口表的获取请求，以使各个上行设备接收到接口表的获取请求后，返回其接口表。
其中，网管设备向现网中的上行设备以及网络设备发送ARP表的获取请求，以使各个上行设备和网络设备接收到ARP表的获取请求后，返回其ARP表。
为便于说明，接口表的获取请求，如下：
Snmp get if Descr，ifPhysAddress，ifOperaStatus//获取接口表
其中，采用的协议为snmp，命令为get，if Descr表示接口的描述，
ifPhysAddress的表示物理接口的MAC地址，
ifOperaStatus表示物理接口状态，只当与其他设备相连接且互通时，物理接口状态为active，在此，只获取接口状态为active的接口。
为便于说明，ARP表的获取请求，如下：
Snmp get ipAdEntAddr，ipAdEntIfIndex//获取ARP表
其中，采用的协议为snmp，命令为get，后面ipAdEntIfIndex为设备接口索引。
网管设备接收上行设备返回的接口表，接口表中包括了上行设备的IP地址、上行设备的物理接口的MAC地址、上行设备的VLAN接口。
网管设备接收网络设备返回的ARP表(以下称为第一ARP表)，第一ARP表中包括了上行设备与该网络设备直接连接的接口的MAC地址(以下称为第一MAC地址)。
网管设备接收上行设备返回的接口表，获取返回的接口表中的MAC地址(以下称为第二MAC地址)。
网管设备检测第一ARP表的第一MAC地址和接口表的第二MAC地址中，是否存在共同的MAC地址。
若存在共同的MAC地址(以下称为第三MAC地址)表示存放第一ARP表的网络设备与表示存放第二MAC地址所在接口表的上行设备之间是直接连接的，第三MAC地址为与网络设备直接连接的上行设备的接口的MAC地址。
网管设备在上行设备返回的接口表中，根据第三MAC地址，查询第三MAC地址对应的物理接口，该物理接口为与所述网络设备直接连接的上行设备的物理接口。
网管设备在上行设备返回的接口表中，根据第三MAC地址，查询网络设备的第三MAC地址对应的VLAN接口，该VLAN接口为网络设备直接连接的上行设备的物理接口属于的VLAN接口。
网管设备在网络设备返回的ARP表中，根据上行设备与网络设备直接连接的接口的IP地址和上行设备与网络设备直接连接的接口的MAC地址的对应关系，通过第三MAC地址，获取上行设备与网络设备直接连接的接口的IP地址，该IP地址为上行设备与网络设备直接连接的接口的IP地址。
当采用一个网络设备替换另一个网络设备时，网管设备向现网中的上行设备发送接口表的获取请求，以使各个上行设备接收到接口表的获取请求后，返回其接口表。
网管设备向现网中替换后的网络设备发送ARP表的获取请求，以使网络设备接收到 ARP表的获取请求后，返回其ARP表。
网管设备接收替换后的网络设备返回的ARP表(以下称为第四ARP表)，第四ARP表中包括了上行设备与替换后的网络设备直接连接的接口的MAC地址(以下称为第四MAC地址)。
网管设备接收上行设备返回的接口表，获取返回的接口表中的MAC地址(以下称为第二MAC地址)。
网管设备检测第一ARP表的第一MAC地址和接口表的第二MAC地址中，是否存在共同的MAC地址。
若存在共同的MAC地址(以下称为第三MAC地址)表示存放第一ARP表的网络设备与表示存放第二MAC地址所在接口表的上行设备之间是直接连接的，第三MAC地址为与网络设备直接连接的上行设备的接口的MAC地址。
在网络设备替换时，由于替换后的网络设备返回的ARP表不变，上行返回的接口表不变，因此第一ARP表和接口表共同的MAC地址不变，也就是第三MAC地址没有改变，因此第三MAC地址对应的物理接口、VLAN接口、以及物理接口的IP地址没有改变，因此替换后的网络设备在现网中的网络拓扑信息也没有改变。因此在本发明中，检测网络设备在现网中的网络拓扑信息与预置的网络拓扑信息是否匹配的匹配结果也没有改变，因此后续可向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，因此即使网络设备的MAC地址或SN改变了，原先的规划也不需要重做、因此能做到网络设备的即插即用，因此，适用于网络设备替换场景，在网络设备替换时能做到自动开局。
需要注意的是，第一MAC地址、第二MAC地址、第三MAC地址、第四MAC地址均指物理接口的MAC地址。
实施例三
作为本发明的一个实施例，检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，包括：
检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址， 与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
在本实施例中，检测所述现网中的网络拓扑信息与预置的网络拓扑信息，存在三种方案。
第一种方案：检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配。
其中，检测现网中的网络拓扑信息的IP地址，与预置的IP地址匹配时，表示现网中接入的上行设备是预置的上行设备。
当现网中的网络拓扑信息的物理接口与预置的物理接口匹配时，表示同一物理接口。
在当采用网络设备替换另一个网络设备时，只有接入与之替换前的网络设备直接连接的同一个上行设备的同一个物理接口，才会获取到操作系统文件和/或配置文件。
第二种方案：检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；
其中，当现网中的网络拓扑信息的VLAN接口与预置的VLAN接口匹配时，表示接入的端口是正确的，可限定接入预置的上行设备的VLAN接口。在备品备件替换时，现有的网络设备，接入与之前的网络设备直接连接的同一个上行设备的同一个VLAN接口的多个物理接口，就会获取到操作系统文件和/或配置文件。
第三种方案：检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
其中，当现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口与预置的物理接口、预置的物理接口所属的VLAN接口时，表示其接入的物理接口是正确的。
在备品备件替换时，现有的网络设备，接入与之前的网络设备直接连接的同一个上行设备的同一个VLAN接口的同一个物理接口，就会获取到操作系统文件和/或配置文件。
在本实施例中，优选第二种方案，因为在实际应用中，当多个物理接口对应一个VLAN接口时，可在多个物理接口中选择其中一个物理接口接入网络，因此其具有灵活性，适合网络设备的接入。
实施例四
作为本发明的一个实施例，可选地，当所述网络拓扑信息还包括设备型号时，所述检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，进一步还包括：
检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
在本实施例中，在预置的网络拓扑信息中，存储了需要自动开局的网络设备的设备型号。
其中，网管设备向现网中的网络设备发送设备型号的获取请求，以使该网络设备接收到设备型号的获取请求后，返回其设备型号。
为便于说明，设备型号的获取请求，如下：
Snmp get sysObjectID
其中，采用的协议为SNMP，命令为get，sysObjectID为厂商定义的系统对象标识。
在本实施例中，检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配，有三种方案，
第一种方案：在检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址时，还检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配，也就是具有三个匹配项，分别是物理接口、IP地址、设备型号，三个匹配项都需要匹配。
第二种方案：在检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配时，还检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配，也就是具有三个匹配项，分别是VLAN接口、IP地址、设备型号，三个匹配项都需要匹配。
第三种方案：检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配时，还检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配，也就是具有四个匹配项，分别是VLAN接口、IP地址、设备型号、物理接口，四个匹配项都需要匹配。
在本实施例中，若匹配，表示网络设备在现网中的网络拓扑信息与预置的网络拓扑信息一致，也就是网络设备在网络中的位置和设备型号没有改变。向网络设备发送操作系统文件和/或配置文件，以使网络设备可完成自动开局配置，使得同一位置的同一设备型号网络设备自动开局时即插即用，节省自动开局配置的成本，节省自动开局配置的时间，且在网络设备备件替换时可做到自动开局，提高了自动开局配置的效率。
参考图4，图4是本发明实施例提供的包括预置的网络拓扑信息的表格。
其中，在表格加粗的两行数据中，网络设备的设备型号为S2，网络设备与两个上行设备的物理接口相连，第一个上行设备的物理接口为GE1/0/1、IP地址为Agg_ip_1、VLAN接口为1000，第二个上行设备的物理接口为GE2/0/3，IP地址为Agg_ip_2，VLAN接口为1000。
以预置的网络拓扑信息中的三个匹配项为例，三个匹配项分别是VLAN接口、IP地址、设备型号时，三个匹配项都需要匹配。
当获取到待自动开局的网络设备的设备型号为S2、上行设备的VLAN接口为1000、上行设备的IP地址为Agg_ip_1和Agg_ip_2时，表示两者匹配。
此时，向网络设备发送操作系统文件S2.bin，配置文件Startup_config1.cfg。
在本实施例中，避免了对同一位置不同型号的网络设备进行自动开局的情况，同时避免了对同一型号不同位置的网络设备进行自动开局的情况，使得同一位置同一型号的网络设备，在自动开局时即插即用，节省自动开局配置的成本，节省自动开局配置的时间，并提高自动开局配置的效率，且在设备备件替换时可做到自动开局。
实施例五
参考图5，图5是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址时，发送操作系统文件和/或配置文件较佳的实施流程图，详述如下：
1、基于网络拓扑信息，网管设备预先建立操作系统文件和/或配置文件与预置的网络拓扑信息的对应关系并存储将对应的操作系统文件和/或配置文件存放在文件传输(File Transfer Protocol，FTP)服务器中，网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址；
2、现场手动安装网络设备，网络设备上电启动；
3、网管设备发送的动态IP地址、FTP服务器的网关地址和IP地址、最小配置文件名字；
4、网络设备接收动态主机配置网管设备发送的动态IP地址、FTP服务器的网关地址和IP地址、最小配置文件名字；
5、网络设备在文件传输服务器中获取最小配置文件；
6、网络设备使用最小配置文件启动；
7、网管设备判断通过简单网络管理协议SNMP传输的数据是否可以到达网络设备；
8、当可以到达时，网管设备获取网络设备在现网中的网络拓扑信息，所述网络拓 扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址、设备型号，检测现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
9、若匹配，网管设备向网络设备发送启用文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与FTP服务器建立一个FTP连接，在所述FTP服务器中获取操作系统文件和/或配置文件。
实施例六
参考图6，图6是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址以及网络设备的设备型号时，发送操作系统文件和/或配置文件较佳的实施流程图，详述如下：
1、基于网络拓扑信息，预先建立操作系统文件和/或配置文件与预置的网络拓扑信息的对应关系存放网管设备上，并将与预置的网络拓扑信息对应的操作系统文件和/或配置文件存放在文件传输(File Transfer Protocol，FTP)服务器中，网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址以及该网络设备的设备型号；
2、现场安装网络设备，网络设备上电启动；
3、网管设备发送的动态IP地址、FTP服务器的网关地址和IP地址、最小配置文件名字；
4、网络设备接收动态主机配置网管设备发送的动态IP地址、FTP服务器的网关地址和IP地址、最小配置文件名字；
5、网络设备在文件传输服务器中获取最小配置文件；
6、网络设备使用最小配置文件启动；
7、网管设备判断通过简单网络管理协议SNMP传输的数据是否可以到达网络设备；
8、当可以到达时，网管设备获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址、设备型号，检测现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
9、若匹配，网管设备向网络设备发送启用文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与FTP服务器建立一个FTP连接，在所述FTP服务器中获取操作系统文件和/或配置文件。
实施例七
参考图7，图7是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址时，发送操作系统文件和/或配置文件另一个较佳的实施流程图。
其中，操作系统文件和/或配置文件存放在网管设备上。
实施例八
参考图8，图8是本发明实施例提供的网络拓扑信息包括与网络设备直接连接的上行设备的接口、IP地址以及网络设备的设备型号时，发送操作系统文件和/或配置文件另一个较佳的实施流程图。
其中，操作系统文件和/或配置文件存放在网管设备上。
实施例九
参考图9，图9是本发明实施例提供的一种控制网络设备自动开局的设备，为了便于说明，仅示出了与本实施例相关的部分，详述如下：
第一获取单元91，用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
第一检测单元92，用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
发送单元93，用于若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP/FTP服务器建立/TFTP/FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
其中，发送单元可以位于存放操作系统文件和/或配置文件的设备中，包括但不限于DHCP服务器和FTP服务器。
进一步地，在该设备中，所述第一获取单元还用于获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
还用于根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
还用于在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
还用于在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
进一步地，在该设备中，所述检测单元还用于检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
还用于检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
还用于检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
进一步地，在该设备中，当所述网络拓扑信息还包括设备型号时，所述检测单元进一步用于检测网络拓扑信息中的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
参考图10，图10是本发明实施例提供的一种控制网络设备自动开局的设备的结构示意图，所述设备包括处理器(英文：processor)101，通信接口(英文：Communications Interface102，存储器(英文：memory)103，总线104。
处理器101，通信接口102，存储器103通过总线104完成相互间的通信。
通信接口102，用于与其他通信设备进行通信；
处理器101，用于执行程序。
具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。
处理器103可能是一个中央处理器(英文：central processing unit，缩写：CPU。
存储器103，用于存储程序。其中程序用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
用于若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
一种控制网络设备自动开局的系统，包括控制网络设备自动开局的设备，以及至少 一个网络设备，至少一个上行设备，其中所述上行设备与所述网络设备采用直接连接的方式进行连接。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可借助软件加必需的通用硬件的方式来实现。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (10)

  1. 一种控制网络设备自动开局的方法，其特征在于，包括：
    网管设备获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
    检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
    若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
    其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合。
  2. 根据权利要求1所述的方法，其特征在于，所述获取网络设备在现网中的网络拓扑信息，包括：
    网管设备获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
    根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
    在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
    在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
  3. 根据权利要求1或2所述的方法，其特征在于，所述检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，包括：
    检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
    检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
    检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
  4. 根据权利要求1至3任意一项所述的方法，其特征在于，当所述网络拓扑信息还包括设备型号时，所述检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配，进一步还包括：
    检测现网中的网络拓扑信息的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
  5. 一种控制网络设备自动开局的设备，其特征在于，包括：
    第一获取单元，用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址；
    第一检测单元，用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
    发送单元，用于若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件；
    其中，所述接口包括物理接口、物理接口所属的虚拟局域网VLAN接口之一或其组合，所述IP地址为所述上行设备在现网中固定的IP地址。
  6. 根据权利要求5所述的设备，其特征在于，所述第一获取单元还用于获取上行设备的接口表以及所述网络设备的地址解析协议ARP表，所述上行设备的接口表包括所述上行设备的各个接口与所述各个接口各自的介质访问控制MAC地址的对应关系，所述网络设备的ARP表包括所述上行设备与所述网络设备直接连接的接口的IP地址和所述上行设备与所述网络设备直接连接的接口的MAC地址的对应关系；
    还用于根据所述上行设备的接口表以及所述网络设备的ARP表，获取与所述网络设备直接连接的上行设备的接口的MAC地址；
    还用于在所述上行设备的接口表中，根据与所述网络设备直接连接的上行设备的接口的所述MAC地址，获取与所述网络设备直接连接的上行设备的接口；
    还用于在所述网络设备的ARP表中，获取所述上行设备与所述网络设备直接连接的接口的IP地址。
  7. 根据权利要求5所述的设备，其特征在于，所述检测单元还用于检测现网中的网络拓扑信息的物理接口和IP地址，与预置的物理接口和IP地址，是否匹配；或者，
    还用于检测现网中的网络拓扑信息的物理接口所属的VLAN接口和IP地址，与预置的物理接口所属的VLAN接口和IP地址，是否匹配；或者，
    还用于检测现网中的网络拓扑信息的物理接口、所述物理接口所属的VLAN接口和IP地址，与预置的物理接口、预置的物理接口所属的VLAN接口和上行设备IP地址，是否匹配。
  8. 根据权利要求5至7任意一项所述的设备，其特征在于，当所述网络拓扑信息还包括设备型号时，所述检测单元进一步用于检测网络拓扑信息中的设备型号与预置的网络拓扑信息中的设备型号，是否匹配。
  9. 一种控制网络设备自动开局的设备，其特征在于，所述设备包括处理器、存储器、通信接口，其中处理器、通信接口、存储器通过总线完成相互间的通信；
    所述通信接口，用于与其他通信设备进行通信；
    所述处理器，用于执行程序；
    所述存储器，用于存储程序；
    其中程序用于获取网络设备在现网中的网络拓扑信息，所述网络拓扑信息包括与所述网络设备直接连接的上行设备的接口和IP地址，所述接口包括物理接口、所述物理接口所属的虚拟局域网VLAN接口之一或其组合；
    用于检测所述现网中的网络拓扑信息与预置的网络拓扑信息，是否匹配；
    用于若匹配，所述网管设备向所述网络设备发送启用简单文件传输协议TFTP或文件传输协议FTP的信息，以及开局所需的操作系统文件的标识和/或配置文件的标识，以使所述网络设备与TFTP服务器或FTP服务器建立TFTP连接或FTP连接，在所述TFTP服务器或FTP服务器中获取操作系统文件和/或配置文件。
  10. 一种控制网络设备自动开局的系统，其特征在于，包括权利要求5至8任意一项所述的设备，以及至少一个网络设备，至少一个上行设备，其中所述上行设备与所述网络设备采用直接连接的方式进行连接。
PCT/CN2014/094810 2013-12-26 2014-12-24 一种控制网络设备自动开局的方法、设备及系统 WO2015096737A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14873759.6A EP3073676B1 (en) 2013-12-26 2014-12-24 Method, apparatus and system for controlling auto-provisioning of network device
US15/191,822 US10091274B2 (en) 2013-12-26 2016-06-24 Method, device, and system for controlling network device auto-provisioning

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310732900.0 2013-12-26
CN201310732900.0A CN104753697B (zh) 2013-12-26 2013-12-26 一种控制网络设备自动开局的方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/191,822 Continuation US10091274B2 (en) 2013-12-26 2016-06-24 Method, device, and system for controlling network device auto-provisioning

Publications (1)

Publication Number Publication Date
WO2015096737A1 true WO2015096737A1 (zh) 2015-07-02

Family

ID=53477560

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/094810 WO2015096737A1 (zh) 2013-12-26 2014-12-24 一种控制网络设备自动开局的方法、设备及系统

Country Status (4)

Country Link
US (1) US10091274B2 (zh)
EP (1) EP3073676B1 (zh)
CN (1) CN104753697B (zh)
WO (1) WO2015096737A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114244695A (zh) * 2021-12-31 2022-03-25 普联技术有限公司 隔离网络的终端上线配置方法、装置及网络管理系统

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107919973B (zh) * 2016-10-08 2020-06-26 华为技术有限公司 用于配置网络设备参数的方法和装置
US10218712B2 (en) * 2017-01-25 2019-02-26 International Business Machines Corporation Access control using information on devices and access locations
CN106921521B (zh) * 2017-02-28 2020-05-08 迈普通信技术股份有限公司 设备信息加载方法及网络设备
CN109495333B (zh) * 2017-09-12 2021-05-07 华为技术有限公司 检测处理的方法、设备及网络设备
CN109831541B (zh) * 2017-11-23 2022-02-22 中国电信股份有限公司 设备地址分配方法、系统和相关设备
CN108234203B (zh) * 2017-12-27 2021-03-26 新华三技术有限公司 配置下发方法及装置、配置方法及装置、网络系统
CN110062061B (zh) * 2019-04-29 2020-06-19 清华大学 基于ip/mac交换的地址解析映射方法
CN110661670A (zh) * 2019-10-21 2020-01-07 中国民航信息网络股份有限公司 一种网络设备配置管理方法及装置
CN113472558B (zh) * 2020-03-31 2023-11-21 北京华为数字技术有限公司 网络部署的方法及装置
CN113872783B (zh) * 2020-06-30 2023-08-22 华为技术有限公司 网络配置的方法、装置及计算机可读存储介质
CN114221950A (zh) * 2020-09-03 2022-03-22 华为技术有限公司 上传配置文件的方法、下载配置文件的方法及装置
CN112203302B (zh) * 2020-09-30 2023-06-30 中国联合网络通信集团有限公司 接入设备配置方法和网管系统
CN112543120B (zh) * 2020-12-02 2023-01-17 中盈优创资讯科技有限公司 一种olt开局自动化配置方法及装置
CN114827243B (zh) * 2022-05-18 2024-03-22 上海电气风电集团股份有限公司 配置文件下发方法、工具、电子设备和可读存储介质
CN115277401B (zh) * 2022-07-20 2024-05-14 浪潮思科网络科技有限公司 一种既定组网的设备扩容方法、装置、设备及介质
CN116827801B (zh) * 2023-08-25 2023-12-15 武汉吧哒科技股份有限公司 网络拓扑构建方法、装置、计算机设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101035016A (zh) * 2007-02-08 2007-09-12 中兴通讯股份有限公司 终端设备配置系统及方法
US20080130517A1 (en) * 2006-12-01 2008-06-05 Cameo Communications, Inc. Intelligent automatic reconfiguration method and apparatus for network system
CN102142988A (zh) * 2010-12-28 2011-08-03 华为终端有限公司 配置设备的方法、装置和系统
CN102546267A (zh) * 2012-03-26 2012-07-04 杭州华三通信技术有限公司 网络设备的自动配置方法和管理服务器

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003032277A (ja) * 2001-07-12 2003-01-31 Allied Tereshisu Kk ネットワーク機器の管理方法及びシステム
US20030227878A1 (en) * 2002-06-07 2003-12-11 Krumm-Heller Alexander Michael Apparatus and method for automatically and dynamically reconfiguring network provisioning
US7843906B1 (en) * 2004-02-13 2010-11-30 Habanero Holdings, Inc. Storage gateway initiator for fabric-backplane enterprise servers
US7843907B1 (en) * 2004-02-13 2010-11-30 Habanero Holdings, Inc. Storage gateway target for fabric-backplane enterprise servers
US7990994B1 (en) * 2004-02-13 2011-08-02 Habanero Holdings, Inc. Storage gateway provisioning and configuring
US8713295B2 (en) * 2004-07-12 2014-04-29 Oracle International Corporation Fabric-backplane enterprise servers with pluggable I/O sub-system
CN101945110B (zh) * 2010-09-20 2014-08-20 中兴通讯股份有限公司 地址解析协议表目的配置方法和装置
CN102075364B (zh) * 2011-01-31 2013-12-11 杭州华三通信技术有限公司 一种直连链路的确定方法和设备
EP2629164B1 (de) * 2012-02-14 2014-12-17 Siemens Aktiengesellschaft Verfahren und Konfigurationskomponente zur Zuweisung eines Stationsnamens zu Komponenten einer industriellen Automatisierungsanordnung
CN102624876B (zh) * 2012-02-23 2015-11-25 华为技术有限公司 一种数据配置方法和装置
CN102594944B (zh) * 2012-03-19 2015-11-25 杭州华三通信技术有限公司 一种自动配置的方法和网络设备
CN103095495B (zh) * 2013-01-06 2016-05-25 华为技术有限公司 网络开局配置方法及装置、系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080130517A1 (en) * 2006-12-01 2008-06-05 Cameo Communications, Inc. Intelligent automatic reconfiguration method and apparatus for network system
CN101035016A (zh) * 2007-02-08 2007-09-12 中兴通讯股份有限公司 终端设备配置系统及方法
CN102142988A (zh) * 2010-12-28 2011-08-03 华为终端有限公司 配置设备的方法、装置和系统
CN102546267A (zh) * 2012-03-26 2012-07-04 杭州华三通信技术有限公司 网络设备的自动配置方法和管理服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3073676A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114244695A (zh) * 2021-12-31 2022-03-25 普联技术有限公司 隔离网络的终端上线配置方法、装置及网络管理系统
CN114244695B (zh) * 2021-12-31 2024-03-19 普联技术有限公司 隔离网络的终端上线配置方法、装置及网络管理系统

Also Published As

Publication number Publication date
EP3073676A1 (en) 2016-09-28
EP3073676A4 (en) 2016-11-02
EP3073676B1 (en) 2018-09-19
CN104753697B (zh) 2019-05-24
CN104753697A (zh) 2015-07-01
US10091274B2 (en) 2018-10-02
US20170180456A1 (en) 2017-06-22

Similar Documents

Publication Publication Date Title
WO2015096737A1 (zh) 一种控制网络设备自动开局的方法、设备及系统
CN103580980B (zh) 虚拟网络自动发现和自动配置的方法及其装置
US8774054B2 (en) Network policy configuration method, management device, and network management center device
US8433779B2 (en) Computer system for allocating IP address to communication apparatus in computer subsystem newly added and method for newly adding computer subsystem to computer system
US10530643B2 (en) Automatic management network provisioning
CN107666419B (zh) 一种虚拟宽带接入方法、控制器和系统
WO2020180776A1 (en) Network access controller operation
US20160036638A1 (en) Provisioning
CN106713039B (zh) 以太网口的识别方法、装置及路由器
CN103701628A (zh) 家庭网关的配置管理方法、虚拟家庭网关和光网络终端
US20180167282A1 (en) Address Assignment by Port Enumeration in a Software-Defined Network
JP4721082B1 (ja) Ｖｐｎ接続システム
US11522754B2 (en) Systems and methods for Zero-Touch Provisioning of a switch in intermediate distribution frames and main distribution frames
US11929851B2 (en) Gateway selection method, device, and system
CN107547403B (zh) 报文转发方法、协助方法、装置、控制器及主机
JP6445408B2 (ja) 通信システムおよび設定方法
WO2012171427A1 (zh) 客户/服务器应用的处理方法及集中处理系统
CN108234203B (zh) 配置下发方法及装置、配置方法及装置、网络系统
CN107070725B (zh) 一种服务器两级管理模块间通信握手的方法
CN113923149B (zh) 网络接入方法、装置、网络系统、电子设备及存储介质
US20130282923A1 (en) Managing overlapping address domains
Cisco Configuring IBM Channel Attach
Cisco Configuring IBM Channel Attach
US20200274791A1 (en) Multi-vrf and multi-service insertion on edge gateway virtual machines
JP2020114024A (ja) ネットワークを制御する方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14873759

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014873759

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014873759

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE