CN108650126A - The method with interior DCN is found and configures automatically in a kind of PTN network - Google Patents
The method with interior DCN is found and configures automatically in a kind of PTN network Download PDFInfo
- Publication number
- CN108650126A CN108650126A CN201810438017.3A CN201810438017A CN108650126A CN 108650126 A CN108650126 A CN 108650126A CN 201810438017 A CN201810438017 A CN 201810438017A CN 108650126 A CN108650126 A CN 108650126A
- Authority
- CN
- China
- Prior art keywords
- ibm
- network
- network element
- managed
- management system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/026—Details of "hello" or keep-alive messages
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses finding and configuring automatically the method with interior DCN in a kind of PTN network, include based on IBM extension message discoveries wait for pipe network member, wait for establishing the channels IBM between pipe network member and managed network element, the process that network management system is managed new access network element.The in-band management channel that the present invention can have found new network element automatically in PTN network and reach the connection of the network element, and remotely establish to this new network element, to which new network element is included in network management system range of management；Whole process need to only connect GNE, without personnel to each device context, can be automatically performed the structure of DCN.Working efficiency can be improved using the present invention, the shortening construction period, save labour turnover, there is preferable practicability.
Description
Technical field
The invention belongs to the technical fields of data communication, and in particular to find and configure automatically in a kind of PTN network in band
The method of DCN.
Background technology
In PTN network deployment, network management system (NMS) manages each equipment (network element, NE) and is usually not directed through equipment
Management port, and only Gateway Network Element (GNE) is accessed by its management port, remaining network element passes through logic in service communication link
It isolates in-band management channel (IBM) and forms one with interior data communication network (DCN), and connect via Gateway Network Element and network management system
It connects, to be included in network management.The in-band management channel of PTN is a kind of logical channel, and network management data is based on specific
MPLS label (label) is separated with business datum.If having physical connection (such as optical fiber, optical fiber both ends point between two neighboring network element
Not Wei two network elements a network port (NNI)), then can establish a channel IBM, usually pass through network management system or maintenance
Terminal is configured to complete according to the network planning ports NNI corresponding to each network element.
However, at network construction initial stage, before the DCN based on the channels IBM is established, be located at the network management system of network management center without
Method remote management apparatus.The foundation in the channels IBM usually requires operating personnel, and network element is configured in device context one by one.And one
Denier configuration error cannot be managed from network management center to network element, also need to send someone to field reconfigurable.Of high cost, time-consuming.It needs
Improve.
Invention content
The purpose of the present invention is to provide finding and configuring automatically the method with interior DCN in a kind of PTN network, the present invention can
The in-band management for finding new network element automatically in PTN network and reaching the connection of the network element, and remotely establishing to this new network element
Channel, to which new network element is included in network management system range of management；Due to that can be automatically performed the structure of DCN, work can be improved in the present invention
Make efficiency, shorten the construction period, save labour turnover, while avoiding personnel and operating issuable mispairing, has preferable
Practicability.
The present invention is achieved through the following technical solutions：The side with interior DCN is found and configures automatically in a kind of PTN network
Network element is divided into managed network element according to the controlled state of network element and waits for that pipe network member, managed network element are managed by network management system by method；Packet
It includes and pipe network member is waited for based on IBM extension message discoveries, is waiting for establishing the channels IBM, network management system pair between pipe network member and managed network element
The process that new access network element is managed；The IBM extensions message is extended based on 802.1ab LLDP protocol massages, packet
Include tri- kinds of type of messages of IBM_HELLO, IBM_SETUP_REQ, IBM_SETUP_ACK.
It is further, described to be found during waiting for pipe network member based on IBM extension message in order to realize the present invention, it is managed
It network element and waits between pipe network member through IBM_HELLO interacting messages；Original state waits for that pipe network member must respond IBM_HELLO and disappear
Breath；If NE status=NE_STATUS_ in IBM_HELLO TLV contents in the IBM_HELLO message that managed network element receives
INIT and Port status=PORT_STATUS_IBM_NO can then confirm that pipe network member is waited in opposite end for original state, by pipe network
Member reports information to network management system；To report information include the candidate ports IBM of managed network element, waits for pipe network member and its corresponding port.
It is to realize the present invention, further, described to wait for during establishing the channels IBM between pipe network member and managed network element,
Network management system sends IBM channel configuration orders to managed network element, specifies the MPLS marks in the channels IBM in the order comprising network management system
Sign and wait for the IP address of pipe network member；The managed network element sends IBM_SETUP_REQ message on the ports IBM yet to be built and waits for pipe network to this
Member simultaneously requires to wait for that pipe network member does IBM configurations；This waits for that pipe network member configures IBM on the receiving port, configures its IP address and through this IBM
The default route in channel, and IBM_SETUP_ACK confirmation messages are sent to managed network element；It is described to wait for that the IBM configurations of pipe network member are completed
After can send newer IBM_HELLO message to managed network element；The managed network element is configured to the channels network management system report IBM
At so that network management system can connect this and wait for that pipe network member is managed it.The content of the IBM_SETUP_REQ message includes
The specified MPLS label of Label=network management systems, IP Address=network management systems be opposite end wait for the distribution of pipe network member IP address,
The managed network elements of GW Address=are with the IP address in interior DCN；Described its IBM_SETUP_ of IBM_SETUP_ACK confirmation messages
SN in the IBM_SETUP_REQ that Return Code=IBM_SET_OK, SN=are received in ACK TLV contents；It is described to wait for pipe network
Its Port status=PORT_ of the IBM_HELLO TLV of IBM_HELLO message is sent after the completion of first IBM configurations again
STATUS_IBM_SET。
Network element is divided into managed network element according to the controlled state of network element and waits for pipe network member by the present invention.Managed network element refers to
By the network element of network management system management, the management port direct communication of network element is may be by between managed network element and network management system
May be to be communicated via in-band management channel (IBM)；And wait for pipe network member still without the management passage to network management system.They
Different roles is undertaken during IBM Path Setups.Between a managed network element and adjacent thereto one wait for pipe network member
(adjacent refers to having physical connection therebetween) establishes during the channels IBM, which undertakes proxy role (proxy),
And this waits for that pipe network member is target to be managed (target).
The state of network element and role can change with the process of construction with interior DCN.Only GNE is managed network element under primary condition
(directly passing through the management port of GNE network elements)；And with the foundation in the channels IBM, more network elements can be by the channels IBM by webmaster system
Reason under the overall leadership.
The construction of DCN based on the present invention is related to：Based on IBM extension message discovery wait for pipe network member, wait for pipe network member with
The channels IBM are established between managed network element, the process that network management system is managed new access network element.The above process is by webmaster system
System, managed network element and it is adjacent wait for pipe network member cooperation complete.The interacting message designed by this method between adjacent network element.
This method is absorbed in the initial construction of DCN, and the network element that whole network is interconnected is included in DCN by net by this process
In guard system management.Thereafter further work can be normally carried out configuration by webmaster by redundant configuration, optimization DCN etc.,
Not in this method scope of design, so it will not be repeated.
The process and message being related to separately below to this method illustrate.
1, IBM extends message：
The message of the present invention is extended based on 802.1ab LLDP protocol massages, is encapsulated using Ethernet II formats.
The NNI communication port of PTN network elements is Ethernet interface, these IBM extend message can be in the physical connection of the sides adjacent network element NNI
It transmits.
The present invention devises following several IBM message：
-IBM_HELLO：Notice message notices network element and NNI port status；
-IBM_SETUP_REQ：Request message is arranged in IBM；
-IBM_SETUP_ACK：Confirmation message is arranged in IBM.
The general format of message is as shown in Figure 1, wherein after extension：
-DA：Destination address is fixed as ethernet multicast address 01-80-C2-00-00-0E here.
-SA：Source address, to send the NNI port macs address of message.
-EtherType：Frame type is 0x88CC.
-LLDP PDU：Message content is made of a series of TLV, including partial content as defined in LLDP and terminates to mark
Will, and the IBM designed here extend.Next IBM extensions TLVs will be described in detail.And TLV as defined in LLDP agreements here
Including：
■ Chassis ID TLV are transmitted network element MAC Address as Chassis ID here；
■ Port ID TLV are transmitted this sending port MAC Address as Port ID here；
■ TTL TLV indicate that the effective time of message, unit are the second；
■ END TLV, mark LLDP PDU terminate.
-FCS：Frame check sequence.
Here IBM extends TLV formats as shown in Fig. 2, wherein：
-Type：TLV types, it is 127 that IBM, which extends TLV types,.
-Length：The TLV message lengths.
-OUI：Organization ID, the whole world is unique, and the OUI of Hua Xinsai nurses company is used in the product of Hua Xinsai nurses.
-Sub-type：Subtype is distinguished due to having OUI, and subtype here is exactly that class is enumerated in a part in fact
Type is ensured unique in this tissue by organizing autonomous definition.Following several IBM extensions TLV subclasses are devised in this method
Type：
■IBM_HELLO
■IBM_SETUP
-Value；Message content, length must coincide with the length value (i.e. Length fields) of this TLV.
IBM_HELLO extends TLV, and message length (Length fields) is 6 bytes, and TLV subtypes (Sub-type) are
IBM_HELLO, message content (Value fields) is as shown in figure 3, wherein：
-Version：Version, for extending later, current version 0x01.
-NE status：The controlled state of network element, is an enumeration type, and current version has following several states：
■NE_STATUS_INIT：Original state, 0x00；
■NE_STATUS_MANAGED：Network element is managed；
■NE_STATUS_LOM：The de- pipe (Loss of management) of network element.
-Port status：Port status indicates that the port for sending this IBM_HELLO message participates in the state with interior DCN,
It is an enumeration type, current version has following several states：
■PORT_STATUS_IBM_NA：Don't care state, the port are not involved in interior DCN；
■PORT_STATUS_IBM_NO：There is no IBM configurations on this port；
■PORT_STATUS_IBM_PENDING：IBM configurations are being done in this port, this is transition state；
■PORT_STATUS_IBM_SET：The configured IBM in this port.
-Label：MPLS label, the channels the IBM MPLS label of this port configuration, label itself occupy 20 bits, remaining 4
Bit retains.
IBM_HELLO message includes the IBM_HELLO TLV and above-mentioned several indispensable standard LLDP TLV,
And may further include that some other TLV (do not belong to this range, as other purposes but can be put into same report with IBM_HELLO notices
Periodicity sending in text, the maintenance phase periodicity sending LLDP messages that can such as talk about below do consistency detection).Wherein END
It is last that TLV must necessarily be placed in all TLV, that is, is placed on including Chassis ID TLV, Port ID TLV, TTL TLV, IBM_HELLO
After TLV and other possible TLV.
IBM_SETUP_REQ extends TLV, and TLV subtypes (Sub-type) are IBM_SETUP, and Value fields include
Content is as shown in figure 4, wherein：
-Version：Version, for extending later, current version 0x01.
-Request Flag：Flag bit sets 1 in IBM_SETUP_REQ message.
-SN：Sequence number, for being matched with IBM_SETUP_ACK.
-Label：MPLS label, grammer is the same as the Label fields in IBM_HELLO.
-IP Address：IP address.
-GW Address：Gateway address, for the corresponding gateway address of the IBM interfaces yet to be built, if after this IBM Path Setup
IP packet is forwarded by this interface, with this gateway address.
IBM_SETUP_REQ message includes the IBM_SETUP_REQ TLV and above-mentioned several indispensable standards
LLDP TLV.Wherein END TLV must necessarily be placed in all other TLV, including Chassis ID TLV, Port ID TLV, TTL
TLV and IBM_SETUP_REQ TLV, later.
IBM_SETUP_ACK extends TLV, and TLV subtypes (Sub-type) are IBM_SETUP, and Value fields include
Content is as shown in figure 5, wherein：
-Version：Version, for extending later, current version 0x01.
-Request Flag：Flag bit is 0 in IBM_SETUP_ACK message.
-SN：Sequence numbers match in sequence number, with IBM_SETUP_REQ message.
-Return Code：Return code indicates the handling result to IBM setting requests.Current version regulation is supported following
Code：
■IBM_SET_OK：0x00 indicates that there is no problem；
■IBM_SET_ERR_LABEL：0x11, parameter error, MPLS label conflict；
■IBM_SET_ERR_INVALID：0x20, invalidation request (this port current state does not support IBM settings request)；
■IBM_SET_ERR_GEN：0x10, other mistakes.
IBM_SETUP_ACK message includes the IBM_SETUP_ACKTLV and above-mentioned several indispensable standards
LLDP TLV.Wherein END TLV must necessarily be placed in all other TLV, including Chassis ID TLV, Port ID TLV,
TTLTLV and IBM_SETUP_ACKTLV, later.
2, the discovery procedure of pipe network member is waited for：
By IBM_HELLO interacting messages between adjacent network element, managed NE Discovery waits for pipe network member and may establish the channels IBM
Physical connection, and report network management system.
Discovery procedure can be initiated by network management system active and (be found on demand), can also be sent out by periodically mutual between network element
IBM_HELLO message (period discovery)；Can configure whether network element is periodically to send IBM_HELLO on its NNI mouth to disappear
Breath.In the case where device power is not made to be arranged, as pipe network member is waited for, default configuration can be not enabled periodicity IBM_
HELLO message is sent, but must receive IBM_HELLO message.It is different from LLDP, wait for that pipe network member is receiving IBM_HELLO message
It must handle, the IBM_HELLO message of their own is sent as response in the port for receiving IBM_HELLO message.
IBM_HELLO TLV contents are as follows in the IBM_HELLO message that managed network element is sent：
- NE status (NE management state)=NE_STATUS_MANAGED (managed state)；
- Port status (port status)=PORT_STATUS_IBM_NO (are configured) without IBM.
Original state waits for that IBM_HELLO TLV contents are as follows in the IBM_HELLO message that pipe network member is sent：
- NE status (NE management state)=NE_STATUS_INIT (original state)；
- Port status (port status)=PORT_STATUS_IBM_NO (are configured) without IBM.
After managed network element receives this message, can assert the receiving port network member for one wait for pipe network member.It is described managed
Network element, which will be seen that, is reported to network management system, report information include this find wait for pipe network member and corresponding port (by receiving message
In Chassis ID TLV and Port ID TLV obtain), and the candidate ports IBM of this corresponding managed network element (receive
The ports NNI of this IBM_HELLO message).
If this discovery procedure is the on-demand discovery actively initiated by network management system, the managed network element also needs to start one
Timer, if not receiving NE status=NE_STATUS_INIT or NE in IBM_HELLO TLV before the defined time
The message of status=NE_STATUS_LOM should be reported to network management system.
Notice that described above is the method for waiting for pipe network member for judging original state.And another situation is de- pipe network member,
It can be found in IBM_HELLO interacting messages.Difference lies in the NE that de- pipe network member is noticed in IBM_HELLO TLV
Status=NE_STATUS_LOM is different from original state (i.e. the case where NE status=NE_STATUS_INIT).De- pipe
Network element such case belongs to the maintenance phase that can be mentioned below, has been managed before this network element, but since network failure is de-
Pipe.Network element determines that oneself whether de- pipe has maturation method, not in the new scope of design of the present invention.Many systems have the reality of their own
It is existing, such as pass through very much heartbeat detection simply between network management system and network element.Network element has taken off the condition adjudgement of pipe in a word
It is maturation method, not in limit of consideration of the present invention.
To support automatic discovery, network element device should be default to open all-network side ports after the power is turned on, can receive and dispatch ether
Network packet handles the IBM extension message of aforementioned definitions.To save equipment power dissipation, this point can be optimized for：After device power,
All-network side ports debit opens to detection function, and originating party sends signal to only periodically opening；If in debit Xiang Jian
Line signal is measured, then port is kept opening completely.
This is just for network-side port (NNI), and default setting is Close All to user port (UNI) after the power-up, this
It is because being also by interconnecting networking between NNI mouthfuls in normal use, between PTN device.UNI is used to access client signal,
It is meaningless before offering customers service, to open UNI mouthfuls not configure equipment.There are some equipment section ports can flexibly match
It sets, i.e., a port can be configured to NNI, and can be configured to UNI, then this type port factory default is set as NNI.Due to
The in-band management communication port of PTN exists only between NNI, such as non-specifically points out, port described in this explanatory note refers both to net
Network side ports (NNI).
3, process is established in IBM channels：
It was found that after pipe network member, network management system can send out instruction to the managed network element for reporting this to find, it is desirable that do the channels IBM
Configuration；Wherein, other than target network element and port, network management system should also specify the MPLS label in the channels IBM and wait for pipe network member
IP address.
After receiving network management system instruction, this managed network element waits for pipe network on the specified candidate ports IBM to its adjacent target
Member sends IBM_SETUP_REQ message, it is desirable that opposite end configures IBM.This IBM_SETUP_REQ message includes following content：
The specified MPLS label of-Label (label)=network management system；
- IP Address (IP address)=network management system is the IP address of opposite end (waiting for pipe) network element distribution；
- GW Address (gateway address)=sheet (managed) network element is with the IP address in interior DCN.
The target of opposite end is after pipe network member receives this IBM_SETUP_REQ request message, if there is no problem, waits for pipe network member
IBM, IP address and default gateway address through this channel IBM are configured on the receiving port according to the parameter specified in message, and
IBM_SETUP_ACK confirmation messages are sent to the managed network element for sending this IBM_SETUP_REQ request message；After the completion of configuration,
On that port IBM_HELLO message is sent to opposite end (managed network element).
Here in IBM_SETUP_ACK confirmation messages its IBM_SETUP_ACKTLV：
- Return Code=IBM_SET_OK (there is no problem)；
SN in the IBM_SETUP_REQ for-SN (sequence number)=receive.
One initial NE is by specifically with postponing, the content in the IBM_HELLO message sent here should have following change
Change：
- Port status (port status)=PORT_STATUS_IBM_SET；
Label in the IBM_SETUP_REQ for-Label (label)=receive.
After receiving IBM_SETUP_ACK message, managed network element configures the channels IBM on its corresponding ports；This IBM is configured
The same MPLS label that opposite end is issued in aforementioned IBM_SETUP_REQ request messages should be used.In addition, this managed network element is also
One routing for arriving peer IP address of configuration.
Above-mentioned configuration is completed, and receives and waits for pipe network member Port status (port status)=PORT_ from opposite end target
After the IBM_HELLO message of STATUS_IBM_SET, this managed network element is completed to network management system report IBM channel configurations.
Note that if network element cannot complete the configuration required by the IBM_SETUP_REQ request messages received, understand to requesting party
Respond the message containing corresponding error code in IBM_SETUP_ACKTLV.Described in error code such as front message one saves, explicitly
Mistake is as follows：
If this port of network element does not support that IBM is configured or network element state is controlled state, the Return Code=of return
IBM_SET_ERR_INVALID；
If IBM configurations, the Return Code=IBM_SET_ERR_INVALID of return are being in this port of network element；
If MPLS label has conflict, the Return Code=IBM_SET_ERR_LABEL of return.
And after the network element for sending out IBM_SETUP_REQ request messages receives this IBM_SETUP_ACKTLV, it should be to webmaster
System Reports mistake.Mistake described above is only the integrity of message design, so that network element has certain error handle
Mechanism.This mistake will not occur under normal circumstances.If this port of network element does not support IBM to configure, if or network element state is to have managed
Reason state then has specific state and indicates in IBM_HELLO notice messages in front, just clear in discovery phase.And
And network management system should have all net element informations managed, should not send the instruction of conflict.Network management system and adjacent managed
Network element should not make this IBM_SETUP_REQ requirements.
In the initial construction stage, automatic mode can be set as in network management system.Network management system receives managed NE Discovery and arrives
Newly after the report of pipe network member, from trend, this reports managed network element to send out management instruction, starts above-mentioned IBM Path Setups process,
This need is by certain regular determine instruction parameter.MPLS for IBM should be preset with a range, and the IP address of network element should also be planned
There is a certain range.Simple rule is：MPLS label by receive instruction managed network element within the scope of sequentially determine, i.e., from
IBM MPLS label stated range minimums start, in case of certain label on the managed network element using then skip the label value sequence pass
Increase and determines, it is unique on the network element to ensure；For wait for pipe network member distribute IP address can by discovery sequence the IP address section successively
It is incremented by.
Under this automatic mode, for network management system on new management after a network element, the automatic command network element has company all
IBM_HELLO notice messages are sent on the network port connect, are found.
In addition, in general, one is waited for that pipe network member should may only instruct one by multiple managed NE Discoveries, network management system
Managed network element establishes the channels IBM at it between the managed network element, this is waited for that pipe network member is included in range of management.The rule of simple possible
It is exactly then sequencing, instructs this managed network element to go to establish and be somebody's turn to do if receiving certain managed reported by network elements discovery at first and waiting for pipe network member
Wait for the channels IBM between pipe network member.
In this way, in automatic mode, the initial construction process of entire DCN can be automatic under the instructions coordinate of network management system
It completes, all network elements of interconnection is accessed into network management range.
Above-mentioned pattern is suitable for initial construction process, is started in network management system by operating personnel.DCN is completed once confirming
Initial construction, operating personnel can terminate initial construction process, terminate automatic mode.Follow-up optimization or maintenance work manually into
Row.It is of course also possible to select not start automatic mode, operating personnel are gradually had found and are configured by network management system, due to being remote
Journey operates, more traditional still to have larger cost and odds for effectiveness in device context configuration.
4, the effect of maintenance phase：
Although this method is absorbed in the initial construction for solving the problems, such as DCN.But it after DCN structures, designs here
IBM extends message and partial routine method also can be helpful in maintenance phase.
First, in maintenance phase, network element periodically sends IBM_HELLO message on its NNI, other side can be made to detect
Inconsistent place.This, which is often represented, mispairing or wrong the case where connecting.By reporting network management system, network management system can be helped to send out
Existing mispairing or wrong the case where connecting, to take measures.This belongs to the normal usage of LLDP, but LLDP agreements are not specified by IBM
The case where, IBM extensions are devised in this method.
Second, in maintenance phase, if due to network failure, if separate line disconnects, the part channels IBM is caused to disconnect,
Individual de- pipes of network element, network management center can take off pipe network member hair since other adjacent not de- pipe network members according to network topology to this
IBM_SETUP_REQ message simultaneously carries out IBM settings, establishes the new channels IBM, obtains new path to manage the network element.This
Operating personnel can establish the channels IBM by network management center to adjacent not de- pipe network member request in the process, need not directly arrive scene
It could handle.And after the network element is managed, operation maintenance personnel can carry out necessary diagnosis from this equipment of network management center's remote operation,
Power-assisted preferably positions and excludes network failure.O＆M cost can be preferably reduced in this way.
Beneficial effects of the present invention：
(1) present invention includes waiting for pipe network member based on IBM extension message discoveries, waiting for establishing between pipe network member and managed network element
The process that the channels IBM, network management system are managed new access network element；The IBM extensions message is to be based on 802.1ab LLDP
Protocol massages are extended, including tri- kinds of type of messages of IBM_HELLO, IBM_SETUP_REQ, IBM_SETUP_ACK.The present invention
The band inner tube that can be found new network element automatically in PTN network and reach the connection of the network element, and remotely establish to this new network element
Channel is managed, to which new network element is included in network management system range of management；Whole process need to only connect GNE, be set to each without personnel
Standby scene, can be automatically performed the structure of DCN；The present invention improves efficiency compared with conventional method, shortens the construction period, reduces into
This, has preferable practicability.
(2) it is of the present invention pipe network member is waited for based on IBM extension message discoveries during, managed network element and wait between pipe network member
Pass through IBM_HELLO interacting messages；Original state waits for that pipe network member must respond IBM_HELLO message；If managed network element receives
To IBM_HELLO message in NE status=NE_STATUS_INIT and Port status in IBM_HELLO TLV contents
=PORT_STATUS_IBM_NO can then confirm that pipe network member is waited in opposite end for original state, and managed reported by network elements information is to webmaster
System；To report information include the candidate ports IBM of managed network element, waits for pipe network member and its corresponding port.Due to being to find automatically, keep away
Exempt from personnel and operates issuable mispairing；The present invention improves efficiency compared with conventional method, reduces cost, has preferable real
The property used.
(3) of the present invention to wait for during establishing the channels IBM between pipe network member and managed network element, network management system is sent
The channels IBM configuration order gives managed network element, specifies the MPLS label in the channels IBM comprising network management system in the order and waits for pipe network member
IP address；The managed network element sends IBM_SETUP_REQ message on the ports IBM yet to be built and waits for pipe network member to this and require to wait for pipe
Network element does IBM configurations；This waits for that pipe network member configures IBM on the receiving port, and configures its IP address and through the default of this channel IBM
Routing, while this waits for that pipe network member sends IBM_SETUP_ACK confirmation messages to managed network element；It is described to wait for that pipe network member IBM is configured
Cheng Houhui sends newer IBM_HELLO message to managed network element；The managed network element is configured to the channels network management system report IBM
At so that network management system can connect this and wait for that pipe network member is managed it.By this method, personnel are not necessarily to each equipment
Scene, and the in-band management channel of new network element is remotely established, new network element is included in network management system range of management；The present invention relatively passes
System method improves efficiency, reduces cost, has preferable practicability.
(4) IBM of the invention extension message and partial routine method also can be helpful in maintenance phase：First, can help
It was found that mispairing, mistake are even caused inconsistent；Second is that lead to the specific condition of the de- pipe of individual network elements in network failure, it can be remotely from it
Its not de- pipe network member repairing DCN manages de- pipe network member again, and help reduces O＆M cost.
Description of the drawings
Fig. 1 is the schematic diagram of the general format of message；
Fig. 2 is the schematic diagram that IBM extends TLV；
Fig. 3 is the schematic diagram that IBM_HELLO extends content；
Fig. 4 is the schematic diagram that IBM_SETUP_REQ extends content；
Fig. 5 is the schematic diagram that IBM_SETUP_ACK extends content；
Fig. 6 is to be related to entity legend；
Interaction schematic diagrames of the Fig. 7 between entity.
Specific implementation mode
Embodiment 1：
Automatically the method with interior DCN is found and configured in a kind of PTN network, and the present embodiment example finds new network element and can arrive
Up to the connection of the network element, and the in-band management channel remotely established to this new network element, to which new network element is included in network management system pipe
Manage the process of range.IBM extension message be extended based on 802.1ab LLDP protocol massages, including IBM_HELLO,
Tri- kinds of type of messages of IBM_SETUP_REQ, IBM_SETUP_ACK.
As shown in fig. 6, the NE2 by network management system (NMS) manage, its (passing through its port p1) between NE1,
The channels IBM have had been established between NE1 and GNE.And NE3 is in original state, is not managed.The ports p2 of NE2 and the ends p1 of NE3
There is optical fiber connection between mouthful.The port p1, p2 of NE2 and the port p1, p2 of NE3 can be used as the ports NNI.
Fig. 7 show managed network element NE2 discoveries and waits for pipe network member NE3, and establishes a channel IBM therebetween, thus by NE3
It is included in the process of network management range.
Discovery procedure is actively initiated by network management system in example.Network management system (NMS) sends out instruction to NE2, starts to send out
Existing process.
After receiving this instruction, NE2 sends IBM_HELLO notice messages on its ports p2.
NE3 receives the IBM_HELLO message that NE2 is sent from its ports p1, and as response, it sends on this port p1
The IBM_HELLO notice messages of oneself.Since NE3 is in original state after the power is turned at this time, the IBM_HELLO that it sends is noticed
In message, NE status=NE_STATUS_INIT, Port status=PORT_STATUS_IBM_NO indicate that network element is in
Original state, port do not configure IBM.
NE2 receives the IBM_HELLO notice messages that NE3 is sent from its ports p2, it is found that NE3 waits for pipe network member.NE2 it
Give the information reporting of this discovery to network management system (NMS).
Network management system (NMS) sends out instruction to NE2, it is desirable that it establishes the channels IBM between NE3, here network management system
(NMS) it specifies the MPLS label in the channels IBM and distributes to the IP address of NE3.
NE2 sends IBM_SETUP_REQ message from its ports p2 to NE3.Wherein the instruction of filling network management system is specified
MPLS label and IP address (filling IP Address fields), and filled out the IP address of NE2 oneself as GW Address fields
Enter.
NE3 receives the IBM_SETUP_REQ request messages that NE3 is sended over from its ports p1.NE3 is in initial at this time
State, MPLS label also Lothrus apterus, it can do IBM settings as required.While doing IBM configurations, NE3 is first at its ends p1
Mouth sends IBM_SETUP_ACK confirmation messages to NE2, and Return Code fields are IBM_SET_OK.
NE3 does IBM configurations to its ports p1, the MPLS label received using this.The parameter that NE3 is received by this
The interior IP address of band of oneself is configured, and configures a default route, the routing is through the GW that gateway address is that this is received
Address is specified, i.e. the interior IP address of the band of NE2, and the interface of routing is the IBM channel interfaces just configured here.It finishes to match and postpone,
NE3 sends IBM_HELLO notice messages from its ports p1, and at this moment, NE management state NE status are constant, but the ends p1
The Port status of mouth become for PORT_STATUS_IBM_SET.
NE2 is also configured according to this IBM after the IBM_SETUP_ACK confirmation messages that its ports p2 receive that NE3 is sent
It is required that MPLS label, IBM configurations are done to its ports p2.
NE2 configurations are completed and after its port p2 receives the IBM_HELLO notice messages that NE3 is sent (by this IBM_
HELLO message can find that its Port status becomes for PORT_STATUS_IBM_SET), to the channels network management system report IBM
Configuration is completed.(channels IBM i.e. through this foundation, go directly and are assigned to NE3's for static routing of the configuration one to the addresses NE3IP
With interior IP address).
If without Routing Protocol, network management system need to configure the static routing on GNE, NE1, be added one and arrive in NE3 bands
The routing of IP address, the gateway address of GNE upper this routings are NE1 with interior IP address, and the gateway address that this upper of NE1 route is
NE2 is with interior IP address, and forwarding interface is as to the forwarding interface of NE2.
In more general terms, in automatic mode, being found with it under network management system instruction when certain managed network element (proxy)
It is adjacent to wait for establishing the channels IBM between pipe network first (target), network management system can reach the managed network elements of the proxy it is all in
Between a static routing that pipe network member is waited for the target targets is automatically configured on network element, the purpose IP address of route table items is net
Guard system is assigned to the IP address for waiting for pipe network member, on the managed network elements of the proxy on an adjacent network element route table items gateway
Address IP address in the managed network element bands of proxy thus, on other network elements the gateway address of the route table items with it is managed to the proxy
The route table items of network element IP are consistent, and forwarding interface is also consistent with the route table items to the managed network element IPs of the proxy.
The channels IBM between NE2 are passed through at this time, and a channel is had been set up between NE3 and network management system.Network management system
NE3 can be managed.After managing NE3, NE3 can further be configured by webmaster instruction, such as configures dynamic routing association
View.
The above process is expanded with interior DCN, and NE3 has been included in its range with interior DCN at this time, and NE3 is also from waiting for that pipe network member becomes
For managed network element.Next, via same process, the channels IBM between NE3 and NE4 can be established, DCN further expands
NE4 is included in its range, to which NE4 is included in management by network management system.
This process gradually in managed network element and waits for establishing the channels IBM between pipe network member, expands DCN since GNE, until
The DCN for setting up covering the whole network, range of management is included in by the whole network.
Embodiment 2：
Further, in Fig. 6 example networks, network topology cyclization, DCN processs of construction are two to the left and right since GNE
Direction promotes simultaneously, may be found from left and right in some network element depending on both sides progress.Such as if NE3 and NE5 are included in
Management, they all may find that waits for pipe network member NE4.At this moment, since the NE Discovery information that reports includes the MAC of network element
Location, network management system should be able to determine NE3 and NE5 discovery be it is same wait for pipe network member.Network management system instruction certain side (such as
NE3 after) establishing the channels IBM and managing NE4, the other side (NE5) need not establish IBM through IBM_SETUP_REQ message again.
In general, a network element should may only instruct a managed network element by multiple managed NE Discoveries, network management system
The channels IBM are established between the managed network element at it, this network element is included in range of management.Simple rule is exactly sequencing,
It is found between waiting for that pipe network member then instructs this managed network element that foundation and this is gone to wait for pipe network member with receiving certain managed reported by network elements at first
The channels IBM.
Certainly (not in the new scope of design of this method), the channels IBM between NE4 and NE5 can be also got through, as redundant channel
To enhance the robustness (noticing that routing configuration should avoid cyclization) of DCN, but this directly configures NE4 respectively simply by network management system
This redundant channel is established with NE5.In fact, after NE4 is managed, it will not receive other IBM_ again as managed network element
SET_REQ is asked, but returns to the IBM_SET_ that Return Code fields are IBM_SET_ERR_INVALID (invalidation request)
ACK message, refusal this set request.Moreover, after NE4 is managed, our DCN initial constructions have been completed；Latter acts
It can be completed by normal webmaster order, not in the new scope of design of this method, including DCN's is further perfect, such as
Establish redundant channel, further Routing Protocol and routing configuration etc..
The other parts of the present embodiment are same as Example 1, and so it will not be repeated.
Embodiment 3：
Further, in embodiment 1, after the channels IBM are established between NE2 and NE3, network management system is automatically in GNE
Be configured on NE1 reach NE3 IP address static routing list item so that NE3 is reachable.If operation state routing association
View also can safeguard routing by dynamic routing protocol, then be not necessarily to configure this static routing.It only need to be by same rule configuration routing
Agreement.Such as OSPF, it need to only ensure all related network elements IBM channel interfaces configurations at the same ospf area (Area).
The present invention can have found new network element automatically in PTN network and reach the connection of the network element, and remotely establishes and arrive this
The in-band management channel of new network element, to which new network element is included in network management system range of management.Whole process need to only connect GNE, nothing
It needs personnel to each device context, the structure of DCN can be automatically performed.Working efficiency can be improved using the present invention, shorten and build week
Phase saves labour turnover, while avoiding personnel and operating issuable mispairing, has preferable practicability.
The other parts of the present embodiment are same as Example 1, and so it will not be repeated.
The above is only presently preferred embodiments of the present invention, not does limitation in any form to the present invention, it is every according to
According to the technical spirit of the present invention to any simple modification, equivalent variations made by above example, the protection of the present invention is each fallen within
Within the scope of.
Claims (3)
1. finding and configuring automatically the method with interior DCN in a kind of PTN network, which is characterized in that extend message including being based on IBM
It was found that wait for pipe network member, wait for establishing the channels IBM between pipe network member and managed network element, network management system is managed new access network element
Process；IBM extension message is extended based on 802.1ab LLDP protocol massages, including IBM_HELLO, IBM_
Tri- kinds of type of messages of SETUP_REQ, IBM_SETUP_ACK.
2. finding and configuring automatically the method with interior DCN in a kind of PTN network according to claim 1, which is characterized in that
It is described pipe network member is waited for based on IBM extension message discoveries during, managed network element and wait between pipe network member through IBM_HELLO message
Interaction；Original state waits for that pipe network member must respond IBM_HELLO message；If the IBM_HELLO message that managed network element receives
NE status=NE_STATUS_INIT and Port status=PORT_STATUS_ in middle IBM_HELLO TLV contents
IBM_NO can then confirm that pipe network member is waited in opposite end for original state, and managed reported by network elements information is to network management system；Report packet
It includes the candidate ports IBM of managed network element, wait for pipe network member and its corresponding port.
3. finding and configuring automatically the method with interior DCN in a kind of PTN network according to claim 1, which is characterized in that
It is described to wait for during establishing the channels IBM between pipe network member and managed network element, network management system send IBM channel configuration orders to by
Pipe network member specifies the MPLS label in the channels IBM comprising network management system in the order and waits for the IP address of pipe network member；The managed network element
IBM_SETUP_REQ message is sent on the ports IBM yet to be built to wait for pipe network member to this and require to wait for that pipe network member does IBM configurations；This is waited for
Pipe network member configures IBM on the receiving port, configures its IP address and the default route through this channel IBM, and send IBM_
SETUP_ACK confirmation messages give managed network element；It is described to wait for that send newer IBM_HELLO after the completion of pipe network member IBM configuration disappears
It ceases to managed network element；The managed network element is completed to network management system report IBM channel configurations, is waited for which network management system can connect this
Pipe network member is managed it；The content of the IBM_SETUP_REQ message includes the specified MPLS of Label=network management system
Label, IP Address=network management system are that opposite end waits for that the IP address of pipe network member distribution, GW Address=managed network element exist
With the IP address in interior DCN；Return in its IBM_SETUP_ACK TLV content of the IBM_SETUP_ACK confirmation messages
SN in the IBM_SETUP_REQ for Code=IBM_SET_OK, SN=receive；It is described to wait for sending out after the completion of the IBM configurations of pipe network member
Send its Port status=PORT_STATUS_IBM_SET of the IBM_HELLO TLV of IBM_HELLO message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810438017.3A CN108650126B (en) | 2018-05-09 | 2018-05-09 | Method for automatically discovering and configuring in-band DCN in PTN network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810438017.3A CN108650126B (en) | 2018-05-09 | 2018-05-09 | Method for automatically discovering and configuring in-band DCN in PTN network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108650126A true CN108650126A (en) | 2018-10-12 |
| CN108650126B CN108650126B (en) | 2021-04-23 |
Family
ID=63753984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810438017.3A Active CN108650126B (en) | 2018-05-09 | 2018-05-09 | Method for automatically discovering and configuring in-band DCN in PTN network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108650126B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110351141A (en) * | 2019-07-12 | 2019-10-18 | Ut斯达康通讯有限公司 | FlexE interface managerial method, device and network element |
| CN111565149A (en) * | 2020-04-03 | 2020-08-21 | 烽火通信科技股份有限公司 | Method and device for keeping remote session alive under LDP RLFA FRR scene |
| CN111786888A (en) * | 2020-03-24 | 2020-10-16 | 北京京东尚科信息技术有限公司 | Interface isolation method and device |
| CN111917621A (en) * | 2019-05-10 | 2020-11-10 | 烽火通信科技股份有限公司 | Communication method and system for network management server and network element of communication equipment |
| WO2022228078A1 (en) * | 2021-04-25 | 2022-11-03 | 中国移动通信有限公司研究院 | Data transmission method and apparatus, system, and communication device |
| CN115296987A (en) * | 2022-07-25 | 2022-11-04 | 武汉烽火技术服务有限公司 | SDH device network element automatic tube loading method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102223278A (en) * | 2011-05-17 | 2011-10-19 | 中兴通讯股份有限公司 | Realization method and system for enabling LLDP function on non-Ethernet link |
| CN103259728A (en) * | 2013-05-24 | 2013-08-21 | 华为技术有限公司 | OFS in-band communication method and OFS |
| CN105591798A (en) * | 2015-07-24 | 2016-05-18 | 杭州华三通信技术有限公司 | Method and device for transmitting OAM information in DCN |
| CN105791014A (en) * | 2016-03-09 | 2016-07-20 | 浪潮通信信息系统有限公司 | Method for discovering network relationship and automatically realizing layered TOPO display by LLDP |
| WO2017000858A1 (en) * | 2015-06-30 | 2017-01-05 | 中兴通讯股份有限公司 | Network element device and method for opening data communication network |
| CN107995041A (en) * | 2017-12-12 | 2018-05-04 | 江西山水光电科技股份有限公司 | A kind of DCN management methods of PTN network |
-
2018
- 2018-05-09 CN CN201810438017.3A patent/CN108650126B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102223278A (en) * | 2011-05-17 | 2011-10-19 | 中兴通讯股份有限公司 | Realization method and system for enabling LLDP function on non-Ethernet link |
| CN103259728A (en) * | 2013-05-24 | 2013-08-21 | 华为技术有限公司 | OFS in-band communication method and OFS |
| WO2017000858A1 (en) * | 2015-06-30 | 2017-01-05 | 中兴通讯股份有限公司 | Network element device and method for opening data communication network |
| CN106330511A (en) * | 2015-06-30 | 2017-01-11 | 中兴通讯股份有限公司 | Network element device and method for opening data communication network |
| CN105591798A (en) * | 2015-07-24 | 2016-05-18 | 杭州华三通信技术有限公司 | Method and device for transmitting OAM information in DCN |
| CN105791014A (en) * | 2016-03-09 | 2016-07-20 | 浪潮通信信息系统有限公司 | Method for discovering network relationship and automatically realizing layered TOPO display by LLDP |
| CN107995041A (en) * | 2017-12-12 | 2018-05-04 | 江西山水光电科技股份有限公司 | A kind of DCN management methods of PTN network |
Non-Patent Citations (1)
| Title |
|---|
| LINGXIA LIAO: "LLDP Based Link Latency Monitoring in Software Defined Networks", 《 2016 12TH INTERNATIONAL CONFERENCE ON NETWORK AND SERVICE MANAGEMENT (CNSM)》 * |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111917621A (en) * | 2019-05-10 | 2020-11-10 | 烽火通信科技股份有限公司 | Communication method and system for network management server and network element of communication equipment |
| WO2020228130A1 (en) * | 2019-05-10 | 2020-11-19 | 烽火通信科技股份有限公司 | Communication method and system for network management server and network element of communication device |
| CN111917621B (en) * | 2019-05-10 | 2021-09-07 | 烽火通信科技股份有限公司 | Communication method and system for network management server and network element of communication equipment |
| CN110351141A (en) * | 2019-07-12 | 2019-10-18 | Ut斯达康通讯有限公司 | FlexE interface managerial method, device and network element |
| CN110351141B (en) * | 2019-07-12 | 2022-05-17 | Ut斯达康通讯有限公司 | Flexe interface management method, device and network element |
| CN111786888A (en) * | 2020-03-24 | 2020-10-16 | 北京京东尚科信息技术有限公司 | Interface isolation method and device |
| CN111786888B (en) * | 2020-03-24 | 2022-08-09 | 北京京东尚科信息技术有限公司 | Interface isolation method and device |
| CN111565149A (en) * | 2020-04-03 | 2020-08-21 | 烽火通信科技股份有限公司 | Method and device for keeping remote session alive under LDP RLFA FRR scene |
| CN111565149B (en) * | 2020-04-03 | 2022-04-08 | 烽火通信科技股份有限公司 | Method and device for keeping remote session alive under LDP RLFA FRR scene |
| WO2022228078A1 (en) * | 2021-04-25 | 2022-11-03 | 中国移动通信有限公司研究院 | Data transmission method and apparatus, system, and communication device |
| CN115296987A (en) * | 2022-07-25 | 2022-11-04 | 武汉烽火技术服务有限公司 | SDH device network element automatic tube loading method and system |
| CN115296987B (en) * | 2022-07-25 | 2023-11-10 | 烽火通信科技股份有限公司 | Automatic network element management method and system for SDH equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108650126B (en) | 2021-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108650126A (en) | The method with interior DCN is found and configures automatically in a kind of PTN network | |
| WO2016177030A1 (en) | Method, device and system for establishing link of sdn network device | |
| CN104270309B (en) | A kind of method that multi-hop BFD is realized under IP RAN equipment | |
| EP3059901A1 (en) | Network element device configuration and management method, device and network element device | |
| CN103001887A (en) | Link keeping alive method, controller and switchboard | |
| CN102638389A (en) | Redundancy backup method and system of TRILL (Transparent Interconnection over Lots of Links) network | |
| CN105577502A (en) | Service transport method and device | |
| CN105791074A (en) | Method and device for establishing PW (Pseudo Wire) links | |
| CN109428766A (en) | Software defined network system with switch automatically deployed and method thereof | |
| CN105281951B (en) | Double primary apparatus conflict detection methods and the network equipment in VSU systems | |
| WO2005006670A1 (en) | Session establishment method in label switch network and label switch node | |
| JP2013026708A (en) | Network system | |
| CN107615721A (en) | Transmitting software defines network (SDN) logical links polymerization (LAG) member's signaling | |
| CN101160862B (en) | Method and system for realizing the consistency of the virtual circuit status | |
| CN105637806B (en) | Network topology determines method and apparatus, centralized network status information storage equipment | |
| EP1524797A1 (en) | Method and system for the centralized collection of link state routing protocol data | |
| US20050089029A1 (en) | Method for operating a transmission system and transmission system in an energy supply network | |
| CN107566277B (en) | Topology determining method, message response method, controller and switch | |
| CN108601055B (en) | Method and system for deploying L3 VPN in L TE mobile backhaul network | |
| CN104270307A (en) | Establishing method and device for BGP neighborhood | |
| CN100559755C (en) | Automatically find the method and system of virtual network | |
| CN103812684B (en) | A kind of complete outdoor digital microwave transmission equipment independent and mandatory administration passage implementation method and device | |
| WO2016086721A1 (en) | Method, device and system for transmitting multicast data in trill network | |
| JP3794496B2 (en) | Network connection method, network connection system, layer 2 switch and management server constituting the same | |
| CN108809840A (en) | A method of for controlling and multicast group in management subnet |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |