WO2010094216A1 - 主从网络设备配置方法、装置和系统 - Google Patents

主从网络设备配置方法、装置和系统 Download PDF

Info

Publication number
WO2010094216A1
WO2010094216A1 PCT/CN2010/070280 CN2010070280W WO2010094216A1 WO 2010094216 A1 WO2010094216 A1 WO 2010094216A1 CN 2010070280 W CN2010070280 W CN 2010070280W WO 2010094216 A1 WO2010094216 A1 WO 2010094216A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
master
configuration information
state configuration
slave state
Prior art date
Application number
PCT/CN2010/070280
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 EP10743397.1A priority Critical patent/EP2391061B1/en
Publication of WO2010094216A1 publication Critical patent/WO2010094216A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • 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/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • 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/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • 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/0866—Checking the 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/0883—Semiautomatic configuration, e.g. proposals from system

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a master-slave network device configuration method, a master-slave network device configuration apparatus, and a system.
  • the Master network device uses a local clock to transmit data
  • the Slave network device uses a recovery clock to transmit data
  • the existing master-slave network device configuration method is: setting the master-slave state configuration information of the network devices at both ends according to the network clock state (such as the Ethernet synchronization state information ESSM level), and then the network devices at both ends perform PHY (physical) layer auto-negotiation. If the master-slave configuration information of the network devices at both ends is set to manual-master (manual configuration-master) or manual-slave (manual configuration-slave), the auto-negotiation fails. The ports of the network devices at both ends are in the down state.
  • the network clock state such as the Ethernet synchronization state information ESSM level
  • the network device is the primary network device.
  • the network device with the manual-Slave is the slave network device.
  • the ports of the network devices at both ends are in the UP state. The network devices at both ends can perform normal communication.
  • the inventor finds that, in the above configuration method, when the auto-negotiation fails, the network devices at both ends need to be re-configured; if the configuration is to be avoided, the upper-layer information needs to be exchanged.
  • the device knows the master-slave configuration information that should be set, which increases the complexity and overhead of the master-slave network device configuration.
  • the above configuration method may cause the master-slave network device to fail to switch; for example, for network device A and network device B, the current state of network device A The master-slave configuration information is manual-Master, and the current master-slave configuration information of network device B is manual-Slave.
  • the current master-slave state configuration information of network device B changes from manual-Slave to manual-Master
  • network device A The current master-slave configuration information is still manual-Master. Therefore, the physical layer auto-negotiation fails.
  • the ports of the network devices at both ends are in the down state, and the master-slave network device fails to switch. It can be seen that the above-mentioned master-slave network device configuration method affects the maintainability of the network device.
  • An embodiment of the present invention provides a method, an apparatus, and a system for configuring a master-slave network device, which can prevent a network device at both ends from re-configuring the master-slave state configuration information, an upper-layer information interaction process, and a master when the physical layer auto-negotiation fails. Switching failures from network devices improves the maintainability of network devices.
  • the network device receives the master-slave state configuration information
  • the network device performs physical layer auto-negotiation according to the received master-slave state configuration information
  • the network device sets the master-slave state configuration mode of the network device to the automatic mode, and does not perform physical layer auto-negotiation for the setting of the current automatic mode.
  • a receiving unit configured to receive master-slave state configuration information
  • a configuration unit configured to perform physical layer auto-negotiation according to the master-slave state configuration information received by the receiving unit, and set a master-slave state configuration mode of the network device to an automatic mode, and the setting for the current automatic mode is not Perform physical layer auto-negotiation.
  • the master-slave network device configuration system provided by the embodiment of the present invention includes multiple network devices;
  • a first network device configured to perform physical layer auto-negotiation according to the received master-slave state configuration information after receiving the master-slave state configuration information, and set the master-slave state configuration mode of the network device A to an automatic mode, and Physical layer auto-negotiation is not performed for the setting of this automatic mode;
  • the second network device is configured to perform physical layer auto-negotiation with the first network device after the first network device initiates physical layer auto-negotiation.
  • the master-slave state configuration mode of the network device is set to the automatic mode, and the setting for the current automatic mode is not the same with the peer network device.
  • the physical layer auto-negotiation is performed so that the physical layer auto-negotiation of the network devices at both ends can be negotiated successfully without the interaction of the upper-layer information.
  • the physical layer auto-negotiation negotiation for the received master-slave state configuration information In the case of a failure, only one network device configures the master-slave configuration information to enable the physical layer auto-negotiation of the network devices at both ends to be successfully implemented.
  • the configuration process of the state configuration information, the interaction process of the upper layer information, and the failure of the master-slave network device switchover improve the maintainability of the network device.
  • FIG. 1 is a flowchart of a method for configuring a master-slave network device according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for configuring a master-slave network device according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a method for configuring a master-slave network device according to Embodiment 3 of the present invention
  • FIG. 4 is a schematic diagram of a master-slave network device configuration apparatus according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic diagram of a network device according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic diagram of a master-slave network device configuration system according to Embodiment 6 of the present invention.
  • Embodiment 1 A method for configuring a master-slave network device. The flow of the method is shown in Figure 1.
  • the network device receives the master-slave state configuration information.
  • the network device here may be a network device supporting synchronous Ethernet, for example, the network device may be a network device including a PHY chip of 1000BASE-T.
  • the master-slave state configuration information may indicate that the network device is set to manual-Master or manual-Slave.
  • the network device performs physical layer auto-negotiation with the peer network device according to the received master-slave state configuration information, and sets a master-slave state configuration mode of the network device to an automatic mode.
  • the network devices at both ends perform physical layer auto-negotiation for the setting of the current automatic mode, but in this embodiment, the network devices at both ends are not targeted.
  • the setting of this automatic mode performs physical layer auto-negotiation.
  • the network device may not directly perform operations such as physical layer auto-negotiation and automatic mode setting, but first the current port state of the network device and/or the received master-slave state.
  • the configuration information is judged whether the current master-slave state configuration information is the same.
  • the network device determines whether the physical layer auto-negotiation and automatic mode setting operations need to be performed according to the determination result.
  • the network device may directly perform the foregoing physical layer without determining whether the current port state and/or the received master-slave state configuration information is the same as the current master-slave state configuration information. Auto-negotiation and automatic mode settings.
  • the network device determines whether the current port status is down or up. If the current port status is determined to be down, the network device performs physical layer auto-negotiation with the peer network device according to the received master-slave state configuration information, and the main device of the network device The status configuration mode is set to automatic mode, and the network devices at both ends do not perform physical layer auto-negotiation for the settings of this automatic mode.
  • the network device may continue to determine whether the received master-slave state configuration information is the same as the current master-slave state configuration information. If not, the network device according to the received master-slave state configuration information. Physical layer auto-negotiation with the peer network device, and the master-slave state configuration mode of the network device is set to the automatic mode, and the network devices at both ends do not perform physical layer auto-negotiation for the setting of the automatic mode; It is determined that the received master-slave state configuration information is the same as the current master-slave state configuration information, and the network device does not perform operations such as the physical layer auto-negotiation and automatic mode setting.
  • the network device determines whether the received master-slave state configuration information is the same as the current master-slave state configuration information. If not, the network device performs physical layer auto-negotiation with the peer network device according to the received master-slave state configuration information, and the The master-slave configuration mode of the network device is set to the automatic mode. Moreover, the network devices at both ends do not perform physical layer auto-negotiation for the settings of this automatic mode.
  • the network device determines that the received master-slave state configuration information is the same as the current master-slave state configuration information, the network device continues to determine the current port state. If the current port state is determined to be down, the network device according to the received master-slave state. The configuration information is automatically negotiated with the peer network device, and the master-slave configuration mode of the network device is set to the automatic mode. The network devices at both ends do not perform physical layer auto-negotiation for the automatic mode setting. When the network device determines that the current port status is up, the network device does not perform operations such as the physical layer auto-negotiation and automatic mode setting.
  • the network device According to the received master-slave state configuration information, the physical layer auto-negotiation is performed with the peer network device, and the master-slave state configuration mode of the network device is set to the automatic mode, and the network devices at both ends are not targeted to the automatic mode.
  • the settings are made by physical layer auto-negotiation.
  • the network device may also determine whether the current port status and the received master-slave state configuration information are the same as the current master-slave state configuration information.
  • the current master-slave state configuration information of the network device may be stored in the network device in the form of text, database, table or flag.
  • the current master-slave state configuration information stored by the network device may indicate manual-Master or manual-Slave or be empty.
  • the master-slave state configuration information received by the network device may be different from the current master-slave state configuration information.
  • the received master-slave state configuration information is manual-Master, and the current master-slave state configuration information of the network device is manual- Slave is either empty (such as null); or: the received master-slave configuration information is manual-Slave, and the current master-slave configuration information of the network device is manual-Master or empty (such as null).
  • the network device may receive the master-slave state configuration information during normal communication with the peer network device, or may receive the master-slave state configuration information before it communicates normally with the peer network device. . That is, the operation described in the first embodiment may be performed during normal communication between the network device and the peer network device, or may be performed before the network device performs normal communication with the peer network device.
  • the master-slave state configuration information received by the network device may be in the form of an input parameter of the interface function.
  • the interface function performs the foregoing determining operation, and the interface function instructs the network device to perform physical layer auto-negotiation with the peer network device; and, by the interface function, the master-slave state configuration mode of the network device is set to the automatic mode, and the network is prohibited.
  • the device performs operations such as the automatic layer mode setting and the physical layer auto-negotiation operation of the peer network device.
  • a specific example of implementing a master-slave network device configuration method by using an interface function is: the network device receives the master-slave state configuration information, the interface function performs a judgment operation, determines that the current port state is down, or receives the master-slave state configuration information and the network device.
  • the current master-slave state configuration information is different, and the interface function indicates that the network device where the interface function is located performs physical layer auto-negotiation with the peer network device according to the received master-slave state configuration information, that is, the interface function allows the network device where the interface function is located and The peer network device performs physical layer auto-negotiation; the interface function sets the master-slave state configuration mode of the network device where the interface function is located to the automatic mode.
  • the interface function prohibits the network device where the interface function is located from performing physical layer auto-negotiation with the peer network device, that is, the interface function does not perform the operation indicating the physical layer auto-negotiation.
  • the interface function prohibits the physical layer from being self-negotiated.
  • the interface function does not output the indication information of the physical layer auto-negotiation with the peer network device. In this case, the network device does not receive the indication information. Perform physical layer auto-negotiation on the peer network device.
  • the manner in which the interface function prohibits the auto-negotiation of the physical layer may also be: the interface function outputs the indication information that the network device where the network device is located does not perform physical layer auto-negotiation with the peer network device, and at this time, the network device receives the indication information. In this case, physical layer auto-negotiation is not performed with the peer network device.
  • the interface function can also output information about negotiation success or negotiation failure according to the physical layer auto-negotiation result.
  • the interface function may not perform the foregoing determining operation, and the foregoing determining operation may be performed by other units or modules in the network device.
  • the unit or module that performs the judging operation determines whether to provide the interface function with the master-slave state configuration information received by the network device according to the judgment result; the interface function instructs the network device and the peer network device to perform the physical layer according to the received master-slave state configuration information.
  • the auto-negotiation is used to set the master-slave state configuration mode of the network device to the automatic mode.
  • the interface function prohibits the network device from performing physical layer auto-negotiation operations on the peer network device for the setting of the automatic mode.
  • the master-slave state configuration mode of the network device is set to the automatic mode, and the setting for the current automatic mode is not related to the peer network.
  • the device performs the physical layer auto-negotiation, so that the physical layer auto-negotiation of the network devices at both ends can be negotiated successfully without the interaction of the upper-layer information.
  • only one end of the network device reconfigures the master-slave state configuration information.
  • the physical layer auto-negotiation of the network devices at both ends is successfully implemented. This prevents the network devices at both ends from re-configuring the master-slave configuration information, the upper-layer information exchange process, and the master-slave network device failover. Phenomenon improves the maintainability of network devices.
  • Embodiment 2 A method for configuring a master-slave network device. The flow of the method is shown in Figure 2.
  • the network device receives the master-slave state configuration information.
  • the master-slave state configuration information may be manual-Master or manual-Slave.
  • the network device can be a network device supporting synchronous Ethernet.
  • the network device determines whether the current port status and/or the received master-slave state configuration information is the same as the current master-slave state configuration information. If the network device determines that the current port status is up and determines that the received master-slave state configuration information is the same as the current master-slave state configuration information, then go to S230; if the network device determines that the current port state is down and/or determines the received The master-slave state configuration information is different from the current master-slave state configuration information, and then to S220.
  • the network device performs physical layer auto-negotiation with the peer network device according to the received master-slave state configuration information, and sets the master-slave state configuration mode to the automatic mode, and the setting for the current automatic mode is not related to the peer network.
  • the device performs physical layer auto-negotiation.
  • the network device does not perform physical layer auto-negotiation with the peer network device, and does not set the master-slave state configuration mode to the automatic mode.
  • the master-slave network device configuration method ends.
  • the network device sets the master-slave state configuration mode of the network device to the automatic mode, and does not perform physical layer auto-negotiation with the peer network device for the current automatic mode setting.
  • the physical layer auto-negotiation of the network device can be negotiated successfully without the interaction of the upper-layer information. This prevents the network devices at both ends from re-configuring the configuration process of the master-slave state and the interaction process of the upper-layer information. And the failure of the master-slave network device to switch, improving the maintainability of the network device.
  • Embodiment 3 A method for configuring a master-slave network device. The flow of the method is shown in Figure 3.
  • both the network device 1 and the network device 2 perform the master-slave state configuration, and both the network device 1 and the network device 2 receive the master-slave state configuration information. It can be understood that, at this time, the network device 1 and the network device 2 are powered on, and the current port states of the network device 1 and the network device 2 are both down. Go to S310.
  • the network device 1 and the network device 2 after receiving the master-slave state configuration information, both detect that the current port state is down, and the first physical layer auto-negotiation is performed between the network device 1 and the network device 2, and the network device Both the network device 2 and the network device 2 will set the master-slave state configuration mode to the automatic mode; the first physical layer auto-negotiation is not the physical layer auto-negotiation for the setting of the automatic mode, but the above-mentioned received Physical layer auto-negotiation performed by master-slave status configuration information. Go to S320.
  • the network device 1 and the network device 2 both determine whether the physical layer auto-negotiation is successful. If the negotiation succeeds, the current port status of the network devices at both ends is up, to S330; if the negotiation fails, the current port of the network devices at both ends The status is down, to S340.
  • the master-slave state configuration information received by the network device 1 is a manual-Slave
  • the master-slave state configuration information received by the network device 2 is a manual-Master
  • the first physical layer auto-negotiation succeeded. If the master-slave state configuration information received by the network devices at both ends is manual-Master or manual-Slave, the first physical layer auto-negotiation between the network device 1 and the network device 2 fails.
  • the network device 1 is a slave network device
  • the network device 2 is a master network device, and the network device 1 and the network device 2 can perform normal communication to S340.
  • the network device 1 and the network device 2 wait for the next configuration, that is, the network device 1 and the network device 2 wait to receive the master-slave state configuration information again. Any of the network device 1 and the network device 2 can be reconfigured. When any of the network devices is reconfigured (ie, any of the network devices receives the master-slave state configuration information again), the process goes to S350. In the third embodiment, the configuration of the network device 1 is re-configured, and the master-slave state configuration information received by the network device 1 is manual-master.
  • the re-configuring operation of the network device 1 may cause a handover of the master-slave network device (ie, switching of the master-slave state of the network device).
  • the reconfiguration operation of the network device 1 causes the network device 1 to try to communicate with the network device 2 again.
  • the following S350 and S320 are described by taking the reconfiguration of the network device 1 as an example, and the network device 2 is reconfigured similarly, and therefore will not be described again.
  • the network device 1 After reconfiguring, if the network device 1 detects that its current port status is down, or detects that the received master-slave state configuration information is different from the current master-slave state configuration information of the network device 1, the network device 1 The master-slave state configuration mode is set to the automatic mode, and the network device 1 performs the second physical layer auto-negotiation with the network device 2 for the re-configured configuration, instead of the re-configured automatic mode setting and the network device 2 Perform physical layer auto-negotiation. Go to S320.
  • the network device 2 sets the network according to the master-slave state configuration information configured by the network device 1.
  • the master-slave configuration information of device 2 is set to manual-Slave. Therefore, the second physical layer auto-negotiation can be negotiated successfully.
  • Network device 1 is the master network device
  • network device 2 is the slave network device. The current ports of the network devices at both ends. The status is up, and normal communication can be performed between the network device 1 and the network device 2.
  • the network device 1 and the network device 2 configure the master-slave state of the network device after receiving the master-slave state configuration information.
  • the physical layer auto-negotiation is not performed with the peer network device for the setting of the automatic mode.
  • the physical layer between the network device 1 and the network device 2 is independent of whether the first physical layer auto-negotiation succeeds or fails.
  • Negotiation can be successfully negotiated without the interaction of the upper-layer information.
  • only one network device can reconfigure the master-slave configuration information to enable the physical layer auto-negotiation of the network devices at both ends to be successfully implemented.
  • both the network device 1 and the network device 2 need to re-configure the master-slave configuration information, the upper-layer information exchange process, and the master-slave network device switch failure, which improves the maintainability of the network device. .
  • Embodiment 4 A master-slave network device configuration device.
  • the device may be a stand-alone network device, such as a network device supporting synchronous Ethernet; or a component disposed in the network device, such as a chip in a network device, a printed circuit board Wait.
  • the device is taken as an example of a component disposed in the network device.
  • the device comprises a structure as shown in Figure 4.
  • the apparatus in FIG. 4 includes a receiving unit 400 and a configuration unit 410. among them,
  • the receiving unit 400 is configured to receive the master-slave state configuration information.
  • the master-slave state configuration information received by the receiving unit 400 may represent a manual-Master or a manual-Slave.
  • the receiving unit 400 may receive the master-slave state configuration information during normal communication of the network device, or may receive the master-slave state configuration information before the network device performs normal communication.
  • the configuration unit 410 is configured to perform physical layer auto-negotiation with the peer network device according to the master-slave state configuration information received by the receiving unit 400, and set the master-slave state configuration mode of the network device to the automatic mode. In this embodiment, the configuration unit 410 does not perform physical layer auto-negotiation with the peer network device for the setting of the current automatic mode.
  • the receiving unit 410 may not directly perform the operations of the physical layer auto-negotiation and the automatic mode setting, but first the current port state of the network device where the network device is located. Whether the received master-slave state configuration information is the same as the current master-slave state configuration information is determined, and the configuration unit 410 further determines whether to perform the operations such as the physical layer auto-negotiation and the automatic mode setting according to the determination result. Certainly, the configuration unit 410 may directly perform the determination of whether the current port state and the received master-slave state configuration information are the same as the current master-slave state configuration information after the receiving unit 400 receives the master-slave state configuration information. The above physical layer auto-negotiation and automatic mode setting operations.
  • the configuration unit 410 may also output information that the negotiation succeeds or the negotiation fails according to the negotiation result with the peer network device.
  • the configuration unit 410 may further include: a determining module 411 and a configuration module 412. among them,
  • the determining module 411 is configured to determine, after the receiving unit 400 receives the master-slave state configuration information, whether the current port state of the network device where the determining module 411 is located is down or up, and/or the received master-slave state configuration information and the network Whether the current master-slave configuration information of the device is different.
  • the determining module 411 may first determine the current port status of the network device, and then determine whether the master-slave state configuration information received by the receiving unit 400 is the same as the current master-slave state configuration information.
  • the configuration module 412 is configured to perform physical layer auto-negotiation with the peer network device according to the master-slave state configuration information received by the receiving unit 400, and configure the module 412 to be located in the network.
  • the master-slave state configuration mode of the device is set to automatic mode.
  • the network device where the device is located is prohibited from performing physical layer auto-negotiation with the peer network device for the setting of the automatic mode.
  • the determining module 411 is configured to determine whether the master-slave state configuration information received by the receiving unit 400 is the same as the current master-slave state configuration information of the network device.
  • the configuration module 412 is further configured to perform, according to the master-slave state configuration information received by the receiving unit 400, with the peer network device.
  • the physical layer is auto-negotiated, and the master-slave state configuration mode of the network device is set to the automatic mode.
  • the network device is not allowed to perform physical layer auto-negotiation with the peer network device for the automatic mode setting.
  • the configuration module 412 does not perform the operations such as the physical layer auto-negotiation and the automatic mode setting.
  • the determining module 411 may first determine whether the master-slave state configuration information received by the receiving unit 400 is the same as the current master-slave state configuration information, and then determine the current port state of the network device. Alternatively, the determining module 411 can also determine whether the current port state and the two information are the same at the same time. Specifically, as described in the foregoing method embodiments, the description is not repeated here.
  • the configuration module 412 receives according to the receiving.
  • the master-slave state configuration information received by the unit 400 performs physical layer auto-negotiation, and sets the master-slave state configuration mode of the network device to the automatic mode, and does not perform physical layer auto-negotiation for the setting of the current automatic mode.
  • the current master-slave state configuration information of the network device may be stored in the network device in the form of text, database, table or flag, etc., such as in the configuration unit 410, or in other modules or units other than the configuration unit 410. .
  • the current master-slave state configuration information stored by the network device may indicate that the manual-Master or manual-Slave is empty or the like.
  • An interface function may be included in the configuration unit 410.
  • the description of the interface function is as described in the foregoing method embodiment, and the description is not repeated here.
  • the configuration unit 410 sets the master-slave state configuration mode of the network device to the automatic mode after receiving the master-slave state configuration information, and the setting for the current automatic mode is not
  • the physical layer auto-negotiation of the peer network device enables the physical layer auto-negotiation of the network devices at both ends to negotiate successfully without the interaction of the upper-layer information.
  • only one network device needs to reconfigure the master-slave state configuration information.
  • the physical layer auto-negotiation of the network devices at both ends can be successfully implemented. This prevents the network devices at both ends from re-configuring the master-slave configuration information, the upper-layer information exchange process, and the master-slave network. Device switching failures improve the maintainability of network devices.
  • Embodiment 5 Network equipment.
  • the master-slave network device configuration device is taken as an example of a network device.
  • the network device may be a network device supporting synchronous Ethernet, for example, the network device is a network device including a PHY chip of 1000BASE-T.
  • the network device includes a structure as shown in FIG.
  • the network device in FIG. 5 includes a receiving unit 500 and a configuration unit 510.
  • the configuration unit 510 can include a determination module 511 and a configuration module 512.
  • the receiving unit 500 receives the master-slave state configuration information that is externally input.
  • the master-slave state configuration information received by the receiving unit 500 may indicate a manual-Master or a manual-Slave.
  • the receiving unit 500 may receive the master-slave state configuration information during the normal communication process between the network device where the network device is located and the peer network device, or may receive the master-slave state configuration before the network device where the network device is in communication with the peer network device. information.
  • the configuration unit 510 performs physical layer auto-negotiation with the peer network device according to the master-slave state configuration information received by the receiving unit 500, and sets its master-slave state configuration mode to the automatic mode.
  • the master-slave state configuration mode is set to the automatic mode, the network devices at both ends perform physical layer auto-negotiation for the setting of the current automatic mode, but in this embodiment, the configuration unit 510 does not target This automatic mode is set to perform physical layer auto-negotiation with the peer network device.
  • the configuration unit 510 may not directly perform the operations such as the physical layer auto-negotiation and the automatic mode setting after the receiving unit 500 receives the master-slave state configuration information, but firstly the current port state and/or the received host of the network device where the network device is located.
  • the state configuration information is determined to be the same as the current master-slave state configuration information.
  • the configuration unit 510 performs the operations such as the physical layer auto-negotiation and the automatic mode setting.
  • the configuration unit 510 may not directly determine whether the current port state and/or the received master-slave state configuration information is the same as the current master-slave state configuration information, but directly Perform the above physical layer auto-negotiation and automatic mode setting operations.
  • the configuration unit 510 may output information that the negotiation succeeds or the negotiation fails according to the negotiation result with the peer network device.
  • Embodiment 6 A master-slave network device configuration system. The system is shown in Figure 6.
  • the system in FIG. 6 includes a first network device 600 and a second network device 610. Although the system in FIG. 6 shows only two network devices, the system may include more than two network devices.
  • the first network device 600 and the second network device 610 may be network devices supporting synchronous Ethernet.
  • the first network device 600 and the second network device 610 may both be network devices including a PHY chip of 1000BASE-T.
  • the first network device 600 After receiving the master-slave state configuration information, the first network device 600 performs physical layer auto-negotiation with the second network device 610 of the peer end according to the received master-slave state configuration information, and configures the master-slave state of the first network device 600.
  • the mode is set to the automatic mode, and for the setting of the current automatic mode, the first network device 600 does not perform physical layer auto-negotiation with the second network device 610 of the opposite end.
  • the second network device 610 is a peer network device of the first network device 600. After the first network device 600 initiates physical layer auto-negotiation, the second network device 610 performs physical layer auto-negotiation with the first network device 600.
  • the specific structure of the first network device 600 and the second network device 610 may be as described in Embodiment 5, and the description thereof will not be repeated here.
  • the network device A and the network device B are taken as an example to introduce several specific scenarios of master-slave network device configuration.
  • the ports of network device A and network device B are all in the down state.
  • both network device A and network device B are configured as manual-Master or manual-Slave.
  • network device A and network are configured as manual-Master or manual-Slave.
  • network device A and network are configured as manual-Master or manual-Slave.
  • network device A and network are configured as manual-Master or manual-Slave.
  • network device A and network are configured as manual-Master or manual-Slave.
  • the physical layer auto-negotiation between devices B fails, causing the ports of network device A and network device B to be in the down state.
  • the ports of network device A and network device B are in the down state, for example, the device just powers on, and before network device A and network device B communicate, the network device The ports of A and network device B are also in the down state.
  • network device B receives the master-slave state configuration information.
  • the network device B in this scenario does not determine whether the current port state and the received master-slave state configuration information are the same as the current master-slave state configuration information.
  • the network device B performs physical layer negotiation with the peer network device according to the received master-slave state configuration information (ie, the network device B performs physical layer auto-negotiation with the network device A), and configures the master-slave state of the network device B.
  • the network device B and the network device A do not perform physical layer auto-negotiation for the setting of the current automatic mode.
  • the network device B Since the master-slave state configuration mode of the network device B is the automatic mode, the network device B performs the physical layer auto-negotiation operation with the network device A according to the master-slave state configuration requirement of the network device A.
  • the physical layer can negotiate through the negotiation. Success, so that the ports of network device B and network device A are both in the up state.
  • the master-slave state configuration mode of the network devices at both ends is still in the automatic mode.
  • the network device A receives the master-slave state configuration information different from the current master-slave state configuration information, that is, the current master-slave state configuration information of the network device A changes, the network device A according to the received master-slave The status configuration information is in physical layer auto-negotiation with network device B.
  • the network device B performs the physical layer auto-negotiation operation with the network device A according to the master-slave state configuration requirement of the network device A. If the negotiation is successful, the master/slave status of the network devices at both ends is switched. The ports of the network devices at both ends are up. The network devices at both ends can continue to communicate normally.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Small-Scale Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

公开了主从网络设备配置方法、装置和系统的技术方案。其中，主从网络设备配置方法包括：网络设备接收主从状态配置信息，网络设备根据接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。上述技术方案可避免物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。

Description

主从网络设备配置方法、装置和系统
本申请要求于2009年2月20日提交中国专利局、申请号为200910078406.6、发明名称为“主从网络设备配置方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络通讯技术领域，具体涉及主从网络设备配置方法、主从网络设备配置装置和系统。
发明背景
在采用了Master-Slave（主-从）机制的网络设备中，Master网络设备使用本地时钟发送数据，Slave网络设备使用恢复时钟发送数据。
现有的主从网络设备配置方法为：根据网络时钟状态（如以太同步状态信息ESSM级别）设置两端网络设备的主从状态配置信息，之后，两端网络设备进行PHY（物理）层自协商，如果两端网络设备的主从状态配置信息均被设置为manual-Master（手工配置-主）或manual-Slave（手工配置-从），则自协商失败，两端网络设备的端口处于down状态，需要重新进行配置；如果一端网络设备的主从状态配置信息设置为manual-Master、另一端网络设备的主从状态配置信息被设置为manual-Slave，则自协商成功，设置了manual-Master的网络设备为主网络设备，设置了manual-Slave的网络设备为从网络设备，两端网络设备的端口处于UP状态，两端网络设备可以进行正常通讯。
在实现本发明的过程中，发明人发现：上述配置方法在自协商失败时，两端网络设备均需要重新进行配置；如果为了避免多次配置操作，则需要进行上层信息交互，使两端网络设备均获知应设置的主从状态配置信息，从而增加主从网络设备配置的复杂度和开销。另外，在正常通讯过程中，一端网络设备的当前主从状态配置信息发生变化时，上述配置方法会导致主从网络设备切换失败；例如，针对网络设备A和网络设备B，网络设备A的当前主从状态配置信息为manual-Master，网络设备B的当前主从状态配置信息为manual-Slave，在网络设备B当前主从状态配置信息由manual-Slave变化为manual-Master时，由于网络设备A当前主从状态配置信息仍然为manual-Master，因此，物理层自协商失败，两端网络设备的端口均处于down状态，主从网络设备切换失败。由此可知，上述主从网络设备配置方法影响了网络设备的可维护性。
发明内容
本发明实施方式提供一种主从网络设备配置方法、装置和系统，可避免物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
本发明实施方式提供的主从网络设备配置方法，包括：
网络设备接收主从状态配置信息；
所述网络设备根据接收到的所述主从状态配置信息进行物理层自协商；
所述网络设备将网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
本发明实施方式提供的主从网络设备配置装置，包括：
接收单元，用于接收主从状态配置信息；
配置单元，用于根据所述接收单元接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
本发明实施方式提供的主从网络设备配置系统，包括多个网络设备；
第一网络设备，用于在接收到主从状态配置信息后，根据接收到的主从状态配置信息进行物理层自协商，将所述网络设备A的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商；
第二网络设备，用于在第一网络设备发起物理层自协商后，与第一网络设备进行物理层自协商。
通过上述技术方案的描述可知，通过在网络设备接收到主从状态配置信息后，将该网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商，使下一次两端网络设备的物理层自协商能够在不需要上层信息交互的情况下协商成功；而且，在本次针对接收的主从状态配置信息的物理层自协商协商失败时，只需一端网络设备对主从状态配置信息进行配置，即可使两端网络设备的物理层自协商成功实现；从而避免物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
附图简要说明
图1是本发明实施例一的主从网络设备配置方法流程图；
图2是本发明实施例二的主从网络设备配置方法流程图；
图3是本发明实施例三的主从网络设备配置方法流程图；
图4是本发明实施例四的主从网络设备配置装置示意图；
图5是本发明实施例五的网络设备示意图；
图6是本发明实施例六的主从网络设备配置系统示意图。
实施本发明的方式
实施例一、主从网络设备配置方法。该方法的流程如附图1所示。
图1中，S100、网络设备接收主从状态配置信息。
这里的网络设备可以为支持同步以太网的网络设备，例如，该网络设备可以为包含有1000BASE-T的PHY芯片的网络设备。该主从状态配置信息可以表示出该网络设备被设置为manual-Master或者manual-Slave。
S110、网络设备根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式。
在现有技术中，如果主从状态配置方式被设置为自动模式，则两端网络设备会针对本次自动模式的设置进行物理层自协商，而在本实施例中，两端网络设备不针对本次自动模式的设置进行物理层自协商。
在S110中，网络设备可以在接收到主从状态配置信息后，不直接执行物理层自协商以及自动模式设置等操作，而是先对该网络设备的当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断，然后，网络设备根据判断结果再确定是否需要执行上述物理层自协商及自动模式设置等操作。当然，网络设备也可以在接收到主从状态配置信息后，不进行针对当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同的判断，而直接执行上述物理层自协商及自动模式设置等操作。
在网络设备需要对当前端口状态和接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断的情况下，S110的一个具体例子为：
网络设备判断当前端口状态为down还是up，如果判断出当前端口状态为down，则网络设备根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商。
如果网络设备判断出当前端口状态为up，则网络设备可以继续判断接收的主从状态配置信息与当前主从状态配置信息是否相同，如果不相同，则网络设备根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商；如果网络设备判断出接收的主从状态配置信息与当前主从状态配置信息相同，则网络设备不再执行上述物理层自协商及自动模式设置等操作。
从上述S110的具体例子可以看出：在网络设备当前端口状态为down的情况下，无论网络设备接收到的主从状态配置信息与当前主从状态配置信息是否相同，网络设备都需要根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商。
需要说明的是，在上述S110的具体例子中，也可以先对网络设备接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断，然后，再判断当前端口状态，从而上述S110的具体例子可以变换为：
网络设备判断接收的主从状态配置信息与当前主从状态配置信息是否相同，如果不相同，则网络设备根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商。
如果网络设备判断出接收的主从状态配置信息与当前主从状态配置信息相同，则网络设备继续对当前端口状态进行判断，如果判断出当前端口状态为down，则网络设备根据接收的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商；如果网络设备判断出当前端口状态为up，则网络设备不再执行上述物理层自协商及自动模式设置等操作。
从上述S110变换的具体例子可以看出：在网络设备接收到的主从状态配置信息与当前主从状态配置信息不相同的情况下，无论网络设备的当前端口状态为down还是为up，网络设备都需要根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将该网络设备的主从状态配置方式设置为自动模式，而且，两端网络设备不针对本次自动模式的设置进行物理层自协商。
另外，网络设备也可以同时对当前端口状态、及接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断。
上述网络设备的当前主从状态配置信息可以以文本、数据库、表或者标志位等形式存储在网络设备中。网络设备存储的当前主从状态配置信息可以表示出manual-Master或者manual-Slave或者为空。
网络设备接收到的主从状态配置信息与当前主从状态配置信息不相同的情况可以为：接收到的主从状态配置信息为manual-Master，而网络设备的当前主从状态配置信息为manual-Slave或者为空（如null等）；或者为：接收到的主从状态配置信息为manual-Slave，而网络设备的当前主从状态配置信息为manual-Master或者为空（如null等）。
另外，在实施例一中，网络设备可以在其与对端网络设备进行正常通讯过程中接收到主从状态配置信息，也可以在其与对端网络设备正常通讯之前接收到主从状态配置信息。即实施例一记载的操作可以在网络设备与对端网络设备进行正常通讯过程中执行，也可以在网络设备与对端网络设备进行正常通讯之前执行。
上述网络设备接收到的主从状态配置信息可以表现为接口函数的输入参数的形式。此时，接口函数进行上述判断操作，且接口函数指示网络设备与对端网络设备进行物理层自协商；而且，由接口函数执行将网络设备的主从状态配置方式设置为自动模式、以及禁止网络设备针对本次自动模式的设置与对端网络设备进行物理层自协商的操作等操作。
采用接口函数实现主从网络设备配置方法的一个具体例子为：网络设备接收到主从状态配置信息，接口函数进行判断操作，确定当前端口的状态为down或者接收到主从状态配置信息与网络设备当前的主从状态配置信息不同，则接口函数根据接收到的主从状态配置信息指示接口函数所在的网络设备与对端网络设备进行物理层自协商，即接口函数允许接口函数所在的网络设备与对端网络设备进行物理层自协商；接口函数将接口函数所在网络设备的主从状态配置方式设置为自动模式。而且，针对本次自动模式的设置，接口函数禁止接口函数所在的网络设备与对端网络设备进行物理层自协商，即接口函数不执行指示物理层自协商的操作。
其中，接口函数禁止物理层自协商的方式可以为：接口函数不输出与对端网络设备进行物理层自协商的指示信息；此时，网络设备在没有接收到该指示信息的情况下，不与对端网络设备进行物理层自协商。当然，接口函数禁止物理层自协商的方式也可以为：接口函数输出其所在的网络设备不与对端网络设备进行物理层自协商的指示信息，此时，网络设备在接收到该指示信息的情况下，不与对端网络设备进行物理层自协商。接口函数还可以根据进行的物理层自协商结果输出协商成功或者协商失败的信息。
需要说明的是，接口函数也可以不进行上述判断操作，上述判断操作可以由网络设备中的其它单元或模块等来执行。执行判断操作的单元或模块等根据判断结果确定是否向接口函数提供网络设备接收到的主从状态配置信息；接口函数根据接收到的主从状态配置信息指示网络设备与对端网络设备进行物理层自协商，将网络设备的主从状态配置方式设置为自动模式；而且，由接口函数执行禁止网络设备针对本次自动模式的设置与对端网络设备进行物理层自协商的操作。
从上述实施例一的描述可知，通过在网络设备接收到主从状态配置信息后，将该网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商，使两端网络设备的物理层自协商能够在不需要上层信息交互的情况下协商成功；而且，只需一端网络设备对主从状态配置信息进行重新配置，即可使两端网络设备的物理层自协商成功实现；从而避免了物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
实施例二、主从网络设备配置方法。该方法的流程如附图2所示。
图2中，S200、网络设备接收主从状态配置信息。该主从状态配置信息可以为manual-Master或manual-Slave等。该网络设备可以为支持同步以太网的网络设备。
S210、网络设备对当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断。如果网络设备判断出当前端口状态为up且判断出接收的主从状态配置信息与当前主从状态配置信息相同，则到S230；如果网络设备判断出当前端口状态为down和/或者判断出接收的主从状态配置信息与当前主从状态配置信息不相同，则到S220。
S220、网络设备根据接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将其主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商。
S230、网络设备不进行与对端网络设备进行物理层自协商、以及不将其主从状态配置方式设置为自动模式等操作，本次主从网络设备配置方法结束。
从上述实施例二的描述可知，网络设备通过将该网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商，使两端网络设备的物理层自协商能够在不需要上层信息交互的情况下协商成功；从而避免了物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
实施例三、主从网络设备配置方法。该方法的流程如附图3所示。
图3中，S300、在网络设备1和网络设备2进行正常通讯之前，网络设备1和网络设备2均会进行主从状态配置，网络设备1和网络设备2均接收到主从状态配置信息。可以理解，此时网络设备1和网络设备2上电启动，网络设备1和网络设备2的当前端口状态均为down。到S310。
S310、网络设备1和网络设备2在接收到主从状态配置信息后，均检测出当前端口状态为down，则网络设备1和网络设备2之间进行第一次物理层自协商，且网络设备1和网络设备2均会将其主从状态配置方式设置为自动模式；第一次物理层自协商并不是针对本次自动模式的设置而进行的物理层自协商，而是针对上述接收到的主从状态配置信息而进行的物理层自协商。到S320。
S320、网络设备1和网络设备2均判断物理层自协商是否成功，如果协商成功，则两端网络设备的当前端口状态均为up，到S330；如果协商失败，则两端网络设备的当前端口状态均为down，到S340。
在本实施例中，如果网络设备1接收到的主从状态配置信息为manual-Slave、且网络设备2接收到的主从状态配置信息为manual-Master，则网络设备1与网络设备2之间的第一次物理层自协商成功。如果两端网络设备接收到的主从状态配置信息均为manual-Master或manual-Slave，则网络设备1与网络设备2之间的第一次物理层自协商失败。
S330、网络设备1为从网络设备，网络设备2为主网络设备，网络设备1和网络设备2可以进行正常通讯，到S340。
S340、网络设备1和网络设备2等待下一次的配置，即网络设备1和网络设备2等待再次接收主从状态配置信息。网络设备1和网络设备2中的任一网络设备均可以重新进行配置，当任一网络设备重新进行配置（即任一网络设备再次接收到主从状态配置信息），则到S350。在本实施例三中，设定网络设备1重新进行配置、且网络设备1再次接收到的主从状态配置信息为manual-Master。
需要说明的是，在第一次物理层自协商成功的情况下，网络设备1重新进行的配置操作会导致主从网络设备的切换（即网络设备主从状态的切换）。在第一次物理层自协商失败的情况下，网络设备1重新进行的配置操作会使网络设备1再次尝试与网络设备2之间进行正常通讯。另外，下面的S350和S320是以网络设备1重新进行配置为例进行描述的，而对网络设备2重新进行配置与之相类似，因此不再赘述。
S350、网络设备1在重新进行配置后，如果检测到其当前端口状态为down，或者检测到再次接收到的主从状态配置信息与网络设备1当前主从状态配置信息不同，则网络设备1会将其主从状态配置方式设置为自动模式，且网络设备1会针对重新进行的配置与网络设备2进行第二次物理层自协商，而不针对重新进行配置后的自动模式设置与网络设备2进行物理层自协商。到S320。
在上述网络设备1重新进行配置过程中，由于此时网络设备2的主从状态配置方式在S310中被设置为自动模式，则网络设备2会根据网络设备1配置的主从状态配置信息将网络设备2的主从状态配置信息设置为manual-Slave；因此，第二次物理层自协商可以协商成功，网络设备1为主网络设备，网络设备2为从网络设备，两端网络设备的当前端口状态均为up，网络设备1和网络设备2之间可以进行正常通讯。
从上述实施例三的描述可知，在网络设备1和网络设备2进行正常通讯之前，网络设备1和网络设备2通过在接收到主从状态配置信息后，均将网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商，不论第一次物理层自协商成功还是失败，网络设备1和网络设备2之间的物理层自协商能够在不需要上层信息交互的情况下协商成功；而且，只需一端网络设备对主从状态配置信息进行重新配置，即可使两端网络设备的物理层自协商成功实现；从而避免了第一次物理层自协商失败时网络设备1和网络设备2均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
实施例四、主从网络设备配置装置。
在本发明的实施例中，该装置可以是一个独立的网络设备，如支持同步以太网的网络设备；也可以是设置在网络设备中的一个部件，如网络设备中的芯片、印制电路板等。本实施例四中，以该装置为设置在网络设备中的一个部件为例，进行介绍。该装置包含的结构如附图4所示。
图4中的装置包括：接收单元400和配置单元410。其中，
接收单元400，用于接收主从状态配置信息。本实施例中，接收单元400接收到的主从状态配置信息可以表示出manual-Master或者manual-Slave。接收单元400可以在网络设备的正常通讯过程中接收到主从状态配置信息，也可以在网络设备进行正常通讯之前接收到主从状态配置信息。
配置单元410，用于根据接收单元400接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将网络设备的主从状态配置方式设置为自动模式。在本实施例中，配置单元410不会针对本次自动模式的设置与对端网络设备进行物理层自协商。
可选的，配置单元410可以在接收单元400接收到主从状态配置信息后，不直接执行上述物理层自协商以及自动模式设置等操作，而是先对其所在网络设备的当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断，配置单元410根据判断结果再确定是否执行上述物理层自协商及自动模式设置等操作。当然，配置单元410也可以在接收单元400接收到主从状态配置信息后，不进行针对当前端口状态、及接收的主从状态配置信息与当前主从状态配置信息是否相同的判断，而直接执行上述物理层自协商及自动模式设置等操作。
可选的，配置单元410还可以根据与对端网络设备的协商结果输出协商成功或者协商失败的信息。
可选的，配置单元410还可以包括：判断模块411和配置模块412。其中，
判断模块411，用于在接收单元400接收到主从状态配置信息后，判断判断模块411所在网络设备的当前端口状态为down还是up，和/或，所述接收的主从状态配置信息与网络设备的当前主从状态配置信息是否不同。
本实施例中，判断模块411可以先判断网络设备的当前端口状态，然后再对接收单元400接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断。
当判断模块411的判断结果为当前端口状态为down时，配置模块412用于根据接收单元400接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将配置模块412所在网络设备的主从状态配置方式设置为自动模式，而且，禁止其所在网络设备针对本次自动模式的设置与对端网络设备进行物理层自协商。
当判断模块411的判断结果为当前端口状态为up时，判断模块411用于判断接收单元400接收的主从状态配置信息与网络设备的当前主从状态配置信息是否相同。
当判断模块411的判断结果为接收的主从状态配置信息与当前主从状态配置信息不相同时，配置模块412还用于根据接收单元400接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将其所在网络设备的主从状态配置方式设置为自动模式，而且，禁止其所在网络设备针对本次自动模式的设置与对端网络设备进行物理层自协商。
当判断模块411的判断结果为接收的主从状态配置信息与当前主从状态配置信息相同，则配置模块412不再执行上述物理层自协商及自动模式设置等操作。
需要说明的是，判断模块411也可以先对接收单元400接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断，然后，再判断网络设备的当前端口状态。或者，判断模块411也可以同时对当前端口状态和两个信息是否相同进行判断。具体如上述方法实施例中的描述，在此不再重复说明。
从上面可知，当判断模块411的判断结果为当前端口状态为down、或者接收的主从状态配置信息与所述网络设备的当前主从状态配置信息不同时，配置模块412就会根据所述接收单元400接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
上述网络设备的当前主从状态配置信息可以以文本、数据库、表或者标志位等形式存储在网络设备中，如存储在配置单元410中，或者存储在配置单元410之外的其它模块或单元中。网络设备存储的当前主从状态配置信息可以表示出manual-Master或者manual-Slave或者为空等。
上述配置单元410中可以包含有接口函数，接口函数的描述如上述方法实施例中的记载，在此不再重复说明。
从上述实施例四的描述可知，配置单元410通过在网络设备接收到主从状态配置信息后，将该网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不与对端网络设备进行物理层自协商，使两端网络设备的物理层自协商能够在不需要上层信息交互的情况下协商成功；而且，只需一端网络设备对主从状态配置信息进行重新配置，即可使两端网络设备的物理层自协商成功实现；从而避免了物理层自协商失败时两端网络设备均需要重新进行主从状态配置信息的配置过程、上层信息交互过程、以及主从网络设备切换失败现象，提高了网络设备的可维护性。
实施例五、网络设备。
在本实施例五中，以主从网络设备配置装置为一个网络设备为例进行介绍。该网络设备可以为支持同步以太网的网络设备，例如，该网络设备为包含有1000BASE-T的PHY芯片的网络设备。该网络设备包括的结构如附图5所示。
图5中的网络设备包括：接收单元500和配置单元510。配置单元510可以包括：判断模块511和配置模块512。
接收单元500接收外部输入的主从状态配置信息。接收单元500接收到的主从状态配置信息可以表示出manual-Master或者manual-Slave。接收单元500可以在其所在的网络设备与对端网络设备进行正常通讯过程中接收到主从状态配置信息，也可以在其所在的网络设备与对端网络设备正常通讯之前接收到主从状态配置信息。
配置单元510根据接收单元500接收到的主从状态配置信息与对端网络设备进行物理层自协商，并将其主从状态配置方式设置为自动模式。在现有技术中，如果主从状态配置方式被设置为自动模式，则两端网络设备会针对本次自动模式的设置进行物理层自协商，而在本实施例中，配置单元510不会针对本次自动模式的设置与对端网络设备进行物理层自协商。
配置单元510可以在接收单元500接收到主从状态配置信息后，不直接执行上述物理层自协商以及自动模式设置等操作，而是先对其所在网络设备的当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断，在判断结果为预先设定的某种情况时，配置单元510再执行上述物理层自协商及自动模式设置等操作。当然，配置单元510也可以在接收单元500接收到主从状态配置信息后，不进行针对当前端口状态和/或接收的主从状态配置信息与当前主从状态配置信息是否相同的判断，而直接执行上述物理层自协商及自动模式设置等操作。配置单元510可以根据与对端网络设备的协商结果输出协商成功或者协商失败的信息。
配置单元510、判断模块511和配置模块512执行的具体操作如上述实施例四中的描述，在此不再重复说明。
实施例六、主从网络设备配置系统。该系统如附图6所示。
图6中的系统包括：第一网络设备600和第二网络设备610。虽然图6中的系统仅示出了两个网络设备，但是，该系统包括的网络设备的数量可以多于两个。
第一网络设备600和第二网络设备610可以为支持同步以太网的网络设备，例如，第一网络设备600和第二网络设备610可以均为包含有1000BASE-T的PHY芯片的网络设备。
第一网络设备600在接收到主从状态配置信息后，根据接收到的主从状态配置信息与对端的第二网络设备610进行物理层自协商，并将第一网络设备600的主从状态配置方式设置为自动模式，且针对本次自动模式的设置，第一网络设备600不与对端的第二网络设备610进行物理层自协商。
第二网络设备610为第一网络设备600的对端网络设备，在第一网络设备600发起物理层自协商后，第二网络设备610与第一网络设备600进行物理层自协商。
第一网络设备600和第二网络设备610的具体结构可以如实施例五中的描述，在此不再重复说明。
为了更好的对本发明的各实施例进行说明，下面以网络设备A和网络设备B为例，介绍几个具体的主从网络设备配置的场景。
场景一
在本场景中，网络设备A和网络设备B的端口均处于down的状态。导致网络设备A和网络设备B的端口均处于down状态的原因有很多，例如：将网络设备A和网络设备B均配置为manual-Master或manual-Slave，这种情况下，网络设备A和网络设备B之间进行的物理层自协商会失败，从而导致网络设备A和网络设备B的端口均处于down状态。当然，在实际的应用中还可能有其他的原因导致网络设备A和网络设备B的端口均处于down的状态，如：设备刚刚上电启动，网络设备A和网络设备B进行通讯之前，网络设备A和网络设备B的端口也是均处于down的状态。
假设本场景中，网络设备B接收到主从状态配置信息。为便于描述，本场景中网络设备B在接收到主从状态配置信息之后，并未对当前端口状态、及接收的主从状态配置信息与当前主从状态配置信息是否相同进行判断。
网络设备B根据接收到的主从状态配置信息，与对端网络设备进行物理层协商（即：网络设备B与网络设备A进行物理层自协商），并将网络设备B的主从状态配置方式设置为自动模式，根据本实施例的描述，网络设备B和网络设备A并不针对本次的自动模式的设置进行物理层自协商。
由于此时网络设备B的主从状态配置方式为自动模式，因此，网络设备B会根据网络设备A的主从状态配置要求与网络设备A进行物理层自协商操作，该物理层自协商可以协商成功，从而使得网络设备B和网络设备A的端口均处于up状态。
场景二
在网络设备A和网络设备B进行正常通讯过程中，两端网络设备的主从状态配置方式仍然为自动模式。此时，如果网络设备A接收到与当前主从状态配置信息不同的主从状态配置信息，即：网络设备A的当前主从状态配置信息发生变化，则网络设备A会根据接收到的主从状态配置信息与网络设备B进行物理层自协商。此时，由于网络设备B的主从状态配置方式为自动模式，因此，网络设备B会根据网络设备A的主从状态配置要求与网络设备A进行物理层自协商操作，该物理层自协商可以协商成功，从而两端网络设备的主从状态发生切换，两端网络设备的端口处于up状态，两端网络设备仍然可以继续进行正常通讯。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到本发明可借助软件加必需的硬件平台的方式来实现，当然也可以全部通过硬件来实施，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案对背景技术做出贡献的全部或者部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备（可以是个人计算机，服务器，或者网络设备等）执行本发明各个实施例或者实施例的某些部分所述的方法。
虽然通过实施例描绘了本发明，本领域普通技术人员知道，本发明有许多变形和变化而不脱离本发明的精神，本发明的申请文件的权利要求包括这些变形和变化。

Claims (11)

  1. 一种主从网络设备配置方法，其特征在于，包括：
    网络设备接收主从状态配置信息；
    所述网络设备根据接收到的所述主从状态配置信息进行物理层自协商；
    所述网络设备将网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收到主从状态配置信息后，判断所述网络设备的当前端口状态为down还是up，和/或，判断所述接收的主从状态配置信息与网络设备的当前主从状态配置信息是否相同。
  3. 如权利要求2所述的方法，其特征在于，所述方法具体包括：
    网络设备接收主从状态配置信息；
    在当前端口状态为down时，所述网络设备根据接收到的所述主从状态配置信息进行物理层自协商，将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
  4. 如权利要求2所述的方法，其特征在于，所述方法具体包括：
    网络设备接收主从状态配置信息；
    当所述接收到的主从状态配置信息与网络设备的当前主从状态配置信息不同时，所述网络设备根据接收到的主从状态配置信息进行物理层自协商，将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述方法还包括：
    当对端网络设备根据配置的主从状态配置信息发起物理层自协商时，处于所述自动模式的网络设备与所述对端网络设备进行物理层自协商。
  6. 一种主从网络设备配置装置，其特征在于，包括：
    接收单元，用于接收主从状态配置信息；
    配置单元，用于根据所述接收单元接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
  7. 如权利要求6所述的装置，其特征在于，所述配置单元包括：
    判断模块，用于在接收单元接收到主从状态配置信息后，判断所述网络设备的当前端口状态为down还是up，和/或，判断所述接收的主从状态配置信息与网络设备的当前主从状态配置信息是否相同；
    配置模块，用于当所述判断模块的判断结果为当前端口状态为down、或者所述接收的主从状态配置信息与所述网络设备的当前主从状态配置信息不同时，根据所述接收单元接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
  8. 如权利要求6所述的装置，其特征在于，当对端网络设备根据配置的主从状态配置信息发起物理层自协商时，处于所述自动模式的网络设备中的配置单元与所述对端网络设备进行物理层自协商。
  9. 如权利要求6-8中任一项所述的装置，其特征在于，所述装置为支持同步以太网的网络设备，或者设置于支持同步以太网的网络设备中。
  10. 一种主从网络设备配置系统，包括多个网络设备，其特征在于：
    第一网络设备，用于在接收到主从状态配置信息后，根据接收到的主从状态配置信息进行物理层自协商，将所述网络设备A的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商；
    第二网络设备，用于在第一网络设备发起物理层自协商后，与第一网络设备进行物理层自协商。
  11. 如权利要求10所述的系统，其特征在于，所述第一网络设备还用于在接收到主从状态配置信息后，判断所述网络设备的当前端口状态为down还是up，和/或，判断所述接收的主从状态配置信息与网络设备的当前主从状态配置信息是否相同，当判断结果为所述当前端口状态为down、或者所述接收的主从状态配置信息与所述网络设备的当前主从状态配置信息不同时，根据所述接收到的主从状态配置信息进行物理层自协商，并将所述网络设备的主从状态配置方式设置为自动模式，且针对本次自动模式的设置不进行物理层自协商。
PCT/CN2010/070280 2009-02-20 2010-01-20 主从网络设备配置方法、装置和系统 WO2010094216A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP10743397.1A EP2391061B1 (en) 2009-02-20 2010-01-20 Method, apparatus and system for configuring master-slave network devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009100784060A CN101494560B (zh) 2009-02-20 2009-02-20 主从网络设备配置方法、装置和系统
CN200910078406.0 2009-02-20

Publications (1)

Publication Number Publication Date
WO2010094216A1 true WO2010094216A1 (zh) 2010-08-26

Family

ID=40924977

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/070280 WO2010094216A1 (zh) 2009-02-20 2010-01-20 主从网络设备配置方法、装置和系统

Country Status (3)

Country Link
EP (1) EP2391061B1 (zh)
CN (1) CN101494560B (zh)
WO (1) WO2010094216A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494560B (zh) * 2009-02-20 2011-11-09 华为技术有限公司 主从网络设备配置方法、装置和系统
US9811496B2 (en) 2013-07-29 2017-11-07 Huawei Technologies Co., Ltd. Method and apparatus for detecting interface connection between devices
CN103401728B (zh) * 2013-07-29 2016-08-10 华为技术有限公司 一种用于检测设备间接口连接的方法和装置
DE102013225882A1 (de) * 2013-12-13 2015-06-18 Robert Bosch Gmbh Master-Slave-Kommunikationssystem mit Standbybetrieb
CN107517121B (zh) * 2016-06-17 2020-07-07 华为技术有限公司 设备配置方法及装置
CN106776702B (zh) * 2016-11-11 2021-03-05 北京奇虎科技有限公司 一种处理主从式数据库系统中的索引的方法和装置
CN110832805B (zh) 2017-12-18 2021-06-29 华为技术有限公司 对网络设备进行同步的方法以及网络设备
CN112865899B (zh) * 2019-11-26 2022-07-22 华为技术有限公司 一种调整物理层phy主从模式的方法及装置
CN112422313B (zh) * 2020-09-29 2023-10-17 漳州立达信光电子科技有限公司 一种基于上位机的配对方法及相关装置
CN113114501A (zh) * 2021-04-09 2021-07-13 北京国科天迅科技有限公司 一种100Base-T1车载以太网主从动端自适应的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020133631A1 (en) * 2001-01-15 2002-09-19 Samsung Electronics Co., Ltd. Auto-negotiation method for high speed link in gigabit Ethernet using 1000 Base-T standard and apparatus thereof
CN1996880A (zh) * 2006-11-24 2007-07-11 华为技术有限公司 自适应管理网络设备的方法和网络设备
CN101170418A (zh) * 2007-12-05 2008-04-30 杭州华三通信技术有限公司 以太网电接口兼容性实现方法、系统及接口设备
CN101350823A (zh) * 2008-08-21 2009-01-21 中兴通讯股份有限公司 以太网端口链路连接的协商方法及装置
CN101494560A (zh) * 2009-02-20 2009-07-29 华为技术有限公司 主从网络设备配置方法、装置和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6807184B2 (en) * 2002-02-06 2004-10-19 Thomson Licensing S.A. Method and apparatus for parameter borrowing for network address translator configuration
US7174371B2 (en) * 2002-07-08 2007-02-06 Packetfront Sweden Ab Dynamic port configuration of network equipment
JP2006050092A (ja) * 2004-08-02 2006-02-16 Pacific Ind Co Ltd 光ｌａｎ装置
US7752672B2 (en) * 2006-03-15 2010-07-06 Cisco Technology, Inc. Methods and apparatus for physical layer security of a network communications link

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020133631A1 (en) * 2001-01-15 2002-09-19 Samsung Electronics Co., Ltd. Auto-negotiation method for high speed link in gigabit Ethernet using 1000 Base-T standard and apparatus thereof
CN1996880A (zh) * 2006-11-24 2007-07-11 华为技术有限公司 自适应管理网络设备的方法和网络设备
CN101170418A (zh) * 2007-12-05 2008-04-30 杭州华三通信技术有限公司 以太网电接口兼容性实现方法、系统及接口设备
CN101350823A (zh) * 2008-08-21 2009-01-21 中兴通讯股份有限公司 以太网端口链路连接的协商方法及装置
CN101494560A (zh) * 2009-02-20 2009-07-29 华为技术有限公司 主从网络设备配置方法、装置和系统

Also Published As

Publication number Publication date
CN101494560A (zh) 2009-07-29
EP2391061A4 (en) 2012-05-02
CN101494560B (zh) 2011-11-09
EP2391061B1 (en) 2017-11-29
EP2391061A1 (en) 2011-11-30

Similar Documents

Publication Publication Date Title
WO2010094216A1 (zh) 主从网络设备配置方法、装置和系统
US6535990B1 (en) Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system
TWI317592B (en) Method and apparatus of operation of a network interface, network interface and computer system
CN101150413B (zh) 一种atca刀片服务器多机框级联系统及方法
US20080215910A1 (en) High-Availability Networking with Intelligent Failover
WO2022108087A1 (ko) 차량용 can 통신 보안 장치 및 방법
EP2761447A2 (en) Apparatus and method for synchronizing application data
US20020021661A1 (en) Standby redundancy in IMA
WO2014082261A1 (zh) 一种以太端口自协商的方法及通信设备
WO2012019464A1 (zh) 路由器集群中板间互联的装置及方法
JPH0752886B2 (ja) ループ型ネットワークの構成方法
US20110145630A1 (en) Redundant, fault-tolerant management fabric for multipartition servers
WO2016000107A1 (zh) 动态路由设备的主备系统切换的方法及其装置
JP3492229B2 (ja) 通信制御装置
CN103119893A (zh) 一种aps业务通道切换方法、系统及自动保护倒换设备
JP3712369B2 (ja) メディアコンバータおよびそのリンク切断方法
JP4571313B2 (ja) 冗長システムの状態同期
WO2015103729A1 (zh) 一种重路由方法、系统以及网络设备
JP2002326773A (ja) エレベーターの通信制御装置
WO2020197008A1 (ko) RAPIEnet 시스템에서 통신 장애 발생 시 네트워크 복구방법
WO2011107036A2 (zh) 交换设备上的数据传输方法和装置
JP2009218727A (ja) 通信管理システム、通信管理方法及び通信装置
JP2003348128A (ja) コールサーバおよびそのポート切替え方法
WO2015042779A1 (zh) 一种终端、基站及其发送失败信息的方法
WO2017008195A1 (zh) 一种业务管理方法及其装置

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: 10743397

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2010743397

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010743397

Country of ref document: EP