WO2018077124A1 - 一种业务告警处理方法、装置及系统 - Google Patents

一种业务告警处理方法、装置及系统 Download PDF

Info

Publication number
WO2018077124A1
WO2018077124A1 PCT/CN2017/107154 CN2017107154W WO2018077124A1 WO 2018077124 A1 WO2018077124 A1 WO 2018077124A1 CN 2017107154 W CN2017107154 W CN 2017107154W WO 2018077124 A1 WO2018077124 A1 WO 2018077124A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
network
node
sink
tunnel
Prior art date
Application number
PCT/CN2017/107154
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 中兴通讯股份有限公司
Publication of WO2018077124A1 publication Critical patent/WO2018077124A1/zh

Links

Images

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/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • 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
    • 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
    • H04L2012/4629—LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching

Definitions

  • the present application relates to the field of communications, for example, to a method, apparatus, and system for service alert processing.
  • LTE Long Term Evolution
  • L3VPN Layer 3 virtual private network
  • the network will be equipped with two active and standby transmission links.
  • the primary transmission link fails, the secondary transmission link will take over the primary transmission link for subsequent data transmission.
  • a primary transmission network element in the primary transmission link is connected between two different networks, and a link fault occurs on the network side of the network element, and the transmission link needs to be switched, if the network element corresponds to the network element If the connection of the backup network element on the side of the link failure network also fails at the same time, the network on the other side cannot know the fault information, and thus the switchover between the active and standby links cannot be implemented, and finally the service is affected. transmission.
  • the related art cannot achieve the above situation, and the fault information is transmitted from the network on the side where the failure occurred to the network on the other side.
  • the present disclosure provides a method, an apparatus, and a system for processing a service alarm to solve the problem that the related technology cannot transmit the fault from the faulty side network to the other side network when the network fault occurs.
  • the embodiment of the present disclosure provides a service alarm processing method, including:
  • the source object and the sink object of the multicast service of the L3VPN configured on the network element may include:
  • the source object and the sink object are set according to the node type.
  • Setting the node type of the network element according to the access port may include:
  • the access port does not include an interface of a virtual Ethernet type, setting a node type of the network element to a three-layer core landing node;
  • the node type of the network element is set as a bridge node.
  • Setting the source object and the sink object according to the node type may include:
  • the inbound interface of the static multicast configuration information of the multicast service is obtained according to the multicast VRF, and the source object is set as the ingress interface;
  • the multicast VRF obtains the outbound interface of the static multicast configuration information, and sets the sink object as the outbound interface;
  • the egress interface of the multicast routing configuration information of the multicast service is obtained according to the multicast VRF, and the source object is set as the egress interface;
  • the service port of the service and the service association relationship between the L3VPN and the Layer 2 virtual private network (L2VPN) acquire the pseudowire of the L2VPN, and set the sink object to be the pseudowire.
  • L2VPN Layer 2 virtual private network
  • the establishing the alarm mapping relationship between the source object and the sink object may include:
  • the alarm mapping relationship between the source object and the sink object is established according to the binding relationship in the case that the configuration is present.
  • Obtaining the detection session of the source object may include:
  • a Layer 3 Ethernet interface or a Layer 3 aggregation port is set according to the inbound interface; and the source is obtained according to the Layer 3 Ethernet interface or the Layer 3 aggregate port.
  • the tunnel information of the network element is obtained according to the outbound interface, and the detection session of the source object is obtained according to the tunnel information, where the detection session is a multicast tunnel type. Detection session.
  • Setting the Layer 3 Ethernet interface or the Layer 3 aggregate port according to the inbound interface may include:
  • the inbound interface includes an Ethernet interface or an aggregation port, maintaining the Ethernet interface or the aggregation port unchanged;
  • the Ethernet sub-interface or the aggregation sub-port is converted into a corresponding Ethernet interface or an aggregation port.
  • Determining whether the tunnel of the source object and the tunnel or the pseudowire of the sink object have the configuration of the MPLS-TP-OAM may include:
  • the node type is the three-layer core landing node, determining whether the tunnel of the sink object has the configuration of the MPLS-TP-OAM;
  • the node type is the bridge node, it is determined whether the tunnel of the source object and the pseudo line of the sink object have the configuration of the MPLS-TP-OAM.
  • the method may further include:
  • the node type is the bridge node, acquiring configuration information of the tunnel corresponding to the source object, and acquiring configuration information of the pseudo line according to the sink object.
  • the method may further include include:
  • the stop transmission continuity and connectivity detection packet in the MPLS-TP-OAM configured by the sink object is set to enable, according to the alarm.
  • the mapping relationship conveys a fault message.
  • the inbound interface may include an Ethernet interface, an Ethernet sub-interface, an aggregation port, an aggregation sub-port or a tunnel interface, and the egress interface may be the tunnel interface.
  • the first network may be a third-party network; when the node type is the bridge node, the outgoing interface may be the tunnel interface; and the first network may be the L2VPN network.
  • the embodiment of the present disclosure further provides a service alarm processing apparatus, which may include:
  • a setting module configured to set a source object and a sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network, The source object and the sink object are respectively connected to the first network and the L3VPN network;
  • the sending module is configured to send the alarm mapping relationship to the device corresponding to the network element.
  • the setting module can include:
  • the query sub-module is configured to set the virtual private network route forwarding VRF to be a multicast VRF, and query the access port of the multicast service according to the multicast VRF;
  • a first setting submodule configured to set a node type of the network element according to the access port
  • a second setting submodule configured to set the source object and the sink object according to the node type.
  • the first setting submodule may include:
  • a first setting unit configured to: when the access port does not include an interface of a virtual Ethernet type, set a node type of the network element to a three-layer core landing node;
  • the second setting unit is configured to set the node type of the network element to be a bridge node when the access port includes an interface of a virtual Ethernet type.
  • the first obtaining submodule may include:
  • the second setting sub-module includes:
  • a third setting unit configured to: when the node type is the three-layer core landing node, acquire an inbound interface of static multicast configuration information of the multicast service according to the multicast VRF, and set the source object
  • the inbound interface is configured to obtain the outbound interface of the static multicast configuration information according to the multicast VRF, and set the sink object to be the outbound interface
  • a fourth setting unit configured to: when the node type is the bridging node, obtain an outbound interface of the multicast routing configuration information of the multicast service according to the multicast VRF, and set the source object to be the The outbound interface obtains the pseudowire of the L2VPN according to the access port of the multicast service and the service association relationship between the L3VPN and the Layer 2 virtual private network L2VPN, and sets the sink object as the pseudowire.
  • the establishing module may include:
  • Obtaining a sub-module configured to acquire a detection session of the source object, and generate a source tracking detection group according to the detection session;
  • a binding sub-module configured to add the source object to the source tracking detection group, and bind the sink object to the source tracking detection group to generate a corresponding binding relationship
  • a judging sub-module configured to determine whether the tunnel of the source object and the tunnel and the pseudowire of the sink object have a multi-protocol label switching transmission application operation, management, and maintenance MPLS-TP-OAM configuration
  • the acquiring sub-module may be configured to: when the node type is the three-layer core landing node, set a Layer 3 Ethernet interface or a Layer 3 aggregation port according to the ingress interface; according to the Layer 3 Ethernet interface or Obtaining, by the Layer 3 aggregation port, a detection session of the source object, where the detection session is a detection session of an interface type;
  • the tunnel information of the network element is obtained according to the outbound interface; the detection session of the source object is obtained according to the tunnel information, where the detection session is a multicast tunnel. Type of detection session.
  • the determining submodule can be configured to:
  • the node type is the three-layer core landing node, determining whether the tunnel of the sink object has the configuration of the MPLS-TP-OAM;
  • the node type is the bridge node, it is determined whether the tunnel of the source object and the pseudo line of the sink object have the configuration of the MPLS-TP-OAM.
  • the device may further include:
  • An acquiring module configured to acquire configuration information of the tunnel corresponding to the sink object when the node type is the three-layer core landing node;
  • the node type is the bridge node, acquiring configuration information of the tunnel corresponding to the source object, and acquiring configuration information of the pseudo line according to the sink object.
  • the device may further include:
  • the enabling module is configured to: when the detection session of the source object is invalid, set the stop transmission continuity and connectivity detection packet of the sink object to be enabled, and transmit according to the alarm mapping relationship Fault message.
  • the above device can be disposed in the network management.
  • the embodiment of the present disclosure further provides a service alarm processing system, including a network management device and a device:
  • the network management device is configured to set a source object and a sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network.
  • the source object and the sink object are respectively connected to the first network and the L3VPN network; establishing an alarm mapping relationship between the source object and the sink object; and sending the alarm mapping relationship to the network element Corresponding device.
  • the device is configured to receive the alarm mapping relationship sent by the network management device, and establish the alarm mapping between the source object and the sink object.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • An embodiment of the present disclosure further provides an electronic device, including:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being At least one processor executes to cause the at least one processor to perform the method described above.
  • the source object and the sink object of the L3VPN multicast service configured on the network element are obtained, and the corresponding relationship between the two is established. If the network connection fails, the transmission link switching needs to be performed, and the active and standby network elements are connected. When a connection failure occurs and the other side network cannot know the fault, the fault message can be transmitted from the fault occurrence side network to the other side network through the establishment of the source-sink object mapping relationship to implement the subsequent active/standby transmission link. Switching and other operations.
  • FIG. 1 is a flowchart of a service alarm processing method according to Embodiment 1 of the present disclosure
  • FIG. 2 is a block diagram 1 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure
  • FIG. 3 is a block diagram 2 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 4 is a block diagram 3 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 5 is a block diagram 4 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 6 is a block diagram 5 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 7 is a block diagram 6 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 8 is a block diagram 7 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • FIG. 9 is a block diagram of a service alarm processing system according to Embodiment 3 of the present disclosure.
  • FIG. 10 is a flowchart of a service alarm processing method according to Embodiment 4 of the present disclosure.
  • FIG. 11 is a schematic diagram of a service alarm according to Embodiment 4 of the present disclosure.
  • FIG. 12 is a flowchart of a service alarm processing method according to Embodiment 5 of the present disclosure.
  • FIG. 13 is a schematic diagram of a service alarm according to Embodiment 5 of the present disclosure.
  • FIG. 14 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a service alarm processing method according to Embodiment 1 of the present disclosure. As shown in FIG. 1, the method includes the following steps:
  • Step S102 setting a source object and a sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network, the source object and the sink object Connecting the first network and the L3VPN network respectively;
  • Step S104 Establish an alarm mapping relationship between the source object and the sink object.
  • Step S106 Send the alarm mapping relationship to the device corresponding to the network element.
  • steps S102 and S104 are configuration operations on the network management system.
  • step S106 the device corresponding to the configuration information is sent to the device for establishing the actual mapping relationship.
  • the source object is an inbound interface on the network element, and the third-party network is connected, and the sink object is an outgoing interface on the network element, and is connected to the L3VPN network; in the case where the first network is an L2VPN network, The source object is the outgoing interface on the network element, and is connected to the L3VPN network.
  • the sink object is a pseudowire on the network element, and is connected to the L3VPN network and the L2VPN network.
  • the transmission link switching needs to be performed, and the connection failure occurs between the active and standby network elements, so that the other side network cannot know the fault, the fault can be established through the establishment of the mapping relationship between the source and sink objects.
  • the message is transmitted to the other side of the network to implement operations such as switching of the subsequent primary and secondary transmission links.
  • Setting the source object and the sink object of the L3VPN multicast service configured on the network element may include: setting a virtual private network route forwarding VRF to be a multicast VRF, and querying an access port of the multicast service according to the multicast VRF; Setting a node type of the network element according to the access port; setting the source object and the sink object according to the node type.
  • Setting the node type of the network element according to the access port may include: setting the node type of the network element to a three-layer core landing node when the access port does not include the virtual Ethernet type interface; and including, at the access port, the access port includes When a virtual Ethernet type interface is used, set the node type of the network element to a bridge node.
  • Setting the source object and the sink object according to the node type may include: the node type is the third The inbound interface of the static multicast configuration information of the multicast service is obtained according to the multicast VRF, and the source object is set as the inbound interface; and the outbound interface of the static multicast configuration information is obtained according to the multicast VRF. Setting the sink object as the outgoing interface;
  • the egress interface of the multicast routing configuration information of the multicast service is obtained according to the multicast VRF, and the source object is set as the egress interface; according to the access port of the multicast service and the The service association relationship between the L3VPN and the Layer 2 virtual private network L2VPN obtains the pseudowire of the L2VPN, and sets the sink object as the pseudowire.
  • Establishing the alarm mapping relationship between the source object and the sink object may include:
  • Obtaining a detection session of the source object generating a source tracking detection group according to the detection session; adding the source object to the source tracking detection group, and binding the sink object to the source tracking detection group to generate a corresponding binding Relationship; determining whether the tunnel of the source object and the tunnel or pseudowire of the sink object have a configuration of operation, management, and maintenance (MPLS-TP-OAM) of the multi-protocol label switching transmission application; in the case where the configuration exists, The binding relationship establishes the alarm mapping relationship between the source object and the sink object.
  • MPLS-TP-OAM configuration of operation, management, and maintenance
  • the obtaining the detection session of the source object may include: when the node type is the three-layer core landing node, setting a Layer 3 Ethernet interface or a Layer 3 aggregation port according to the inbound interface; according to the Layer 3 Ethernet interface or the Layer 3 aggregation
  • the port obtains the detection session of the source object, where the detection session is an interface type detection session; when the node type is the bridge node, the tunnel information of the network element is obtained according to the outbound interface; and the source is obtained according to the tunnel information.
  • the detection session of the object wherein the detection session is a detection session of a multicast tunnel type.
  • the detection session is a detection means. By obtaining the information of the detection session, it can be determined whether the source object can communicate normally, and whether the sink object can communicate normally.
  • the detection object of the source object carries the information of the active object, and the source object is added to the source tracking detection group.
  • the detection session of the source object is added to the source tracking detection group.
  • the sink object is bound to the source tracking detection group, which is indirectly the binding of the sink object to the source object.
  • the binding countermeasure may be that after all source objects in the source tracking detection group are invalid, the bound sink object starts working; or some of the source objects in the source tracking detection group fail, the bound sink object starts working.
  • All source objects can be added to the source tracking detection group, and all the sink objects are bound to the source tracking monitoring group. Some source objects can also be selected to join the source tracking detection group, and some of the sink objects are bound to the source tracking monitoring group.
  • the tracking detection group may be an existing detection group in the queried network element, or may be a network management device. Set the generated detection group.
  • Obtaining the detection session of the source object may include: when the node type is the three-layer core landing node, setting a Layer 3 Ethernet interface or a Layer 3 aggregation port according to the inbound interface; according to the Layer 3 Ethernet interface or the Layer 3
  • the aggregation port obtains the detection session of the source object, where the detection session is an interface type detection session; when the node type is the bridge node, the tunnel information of the network element is obtained according to the outbound interface;
  • a detection session of the source object wherein the detection session is a detection session of a multicast tunnel type.
  • Setting the Layer 3 Ethernet interface or the Layer 3 aggregate port according to the inbound interface may include:
  • the Ethernet interface or the aggregation port When the inbound interface includes an Ethernet interface or an aggregation port, the Ethernet interface or the aggregation port is maintained unchanged; when the inbound interface includes an Ethernet sub-interface or an aggregation sub-port, the Ethernet sub-interface or the aggregate is used. The port is converted to the corresponding Ethernet interface or aggregation port.
  • the same inbound interface can be filtered to prevent the same ingress interface from creating the same detection session, resulting in redundancy of the detection session.
  • Determining whether the tunnel of the source object and the tunnel or the pseudowire of the sink object have the MPLS-TP-OAM configuration may include: determining whether the tunnel of the sink object exists when the node type is the three-layer core landing node The configuration of the MPLS-TP-OAM; when the node type is the bridge node, it is determined whether the tunnel of the source object and the pseudowire of the sink object have the configuration of the MPLS-TP-OAM.
  • the node type is the three-layer core landing node
  • the source object that is, the inbound interface of the network element
  • the tunnel interface it is necessary to determine whether the tunnel corresponding to the source object has the configuration of the MPLS-TP-OAM.
  • the method may further include: when the node type is the three-layer core landing node, acquiring the sink The configuration information of the tunnel corresponding to the object; when the node type is the bridge node, obtaining configuration information of the tunnel corresponding to the source object; and acquiring configuration information of the pseudowire according to the sink object.
  • the tunnel is a point-to-multipoint P2MP tunnel.
  • the method may further include:
  • the MPLS-TP-0AM configured for the sink object
  • the stop transmission continuity and connectivity detection packet is set to enable, and the fault message is transmitted according to the alarm mapping relationship.
  • the peer network connected to the sink object knows that the network connected to the source object is faulty and needs to perform service switching.
  • the inbound interface of the network element may include an Ethernet interface, an Ethernet sub-interface, an aggregation port, or an aggregation sub-port or a P2MP tunnel interface, and the egress interface may be a P2MP tunnel interface.
  • the first network may be a third-party network.
  • the outbound interface of the network element may be the P2MP tunnel interface, and the first network may be an L2VPN network.
  • FIG. 2 is a block diagram of a service alarm processing apparatus according to Embodiment 2 of the present disclosure. As shown in FIG. 2, the apparatus includes:
  • the setting module 22 is configured to set a source object and a sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network, the source object Connecting the first network and the L3VPN network to the sink object;
  • the establishing module 24 is configured to establish an alarm mapping relationship between the source object and the sink object.
  • the sending module 26 is configured to send the alarm mapping relationship to the device corresponding to the network element.
  • the setting module 22 includes:
  • the query sub-module 32 is configured to set the virtual private network route forwarding VRF to be a multicast VRF, and query the access port of the multicast service according to the multicast VRF;
  • the first setting submodule 34 is configured to set a node type of the network element according to the access port;
  • the second setting sub-module 36 is configured to set the source object and the sink object according to the node type.
  • the first setting sub-module 34 includes:
  • the first setting unit 42 is configured to: when the access port does not include an interface of a virtual Ethernet type, set a node type of the network element to a three-layer core landing node;
  • the second setting unit 44 is configured to set the node type of the network element as a bridge node when the access port includes an interface of a virtual Ethernet type.
  • FIG. 5 is a block diagram 4 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure. As shown in FIG. 5, the second setting sub-module 36 includes:
  • the third setting unit 52 is configured to: when the node type is the three-layer core landing node, obtain an inbound interface of the static multicast configuration information of the multicast service according to the multicast VRF, and set the source object as the ingress interface. Obtaining the outbound interface of the static multicast configuration information according to the multicast VRF, and setting the sink object as the outbound interface;
  • the fourth setting unit 54 is configured to: when the node type is the bridge node, obtain an outbound interface of the multicast routing configuration information of the multicast service according to the multicast VRF, and set the source object to be the outbound interface;
  • the access port of the multicast service and the service association relationship between the L3VPN and the Layer 2 virtual private network L2VPN obtain the pseudowire of the L2VPN, and set the sink object as the pseudowire.
  • FIG. 6 is a block diagram 5 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure.
  • the establishing module 24 includes:
  • the obtaining sub-module 62 is configured to acquire a detection session of the source object, and generate a source tracking detection group according to the detection session;
  • the binding sub-module 64 is configured to add the source object to the source tracking detection group, and bind the sink object to the source tracking detection group to generate a corresponding binding relationship.
  • the determining sub-module 66 is configured to determine whether the tunnel of the source object and the tunnel and the pseudowire of the sink object have a multi-protocol label switching transmission application operation, management, and maintenance MPLS-TP-OAM configuration;
  • the establishing sub-module 68 is configured to establish the alarm mapping relationship between the source object and the sink object according to the binding relationship, if the configuration is present.
  • the acquisition sub-module 62 can be configured to:
  • a Layer 3 Ethernet interface or a Layer 3 aggregate port is set according to the inbound interface; and the detection session of the source object is obtained according to the Layer 3 Ethernet interface or the Layer 3 aggregate port, where The detection session is an interface type detection session;
  • the tunnel information of the network element is obtained according to the outbound interface; the detection session of the source object is obtained according to the tunnel information, where the detection session is a multicast tunnel type Detect session.
  • the determining sub-module 66 may include: determining, when the node type is the three-layer core landing node, whether the tunnel of the sink object exists in the MPLS-TP-OAM configuration;
  • the node type is the bridge node, it is determined whether the tunnel of the source object and the pseudowire of the sink object have the configuration of the MPLS-TP-OAM.
  • FIG. 7 is a block diagram 6 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure. As shown in FIG. 7, the apparatus further includes:
  • the obtaining module 72 is configured to: when the node type is the three-layer core landing node, acquire configuration information of the tunnel corresponding to the sink object; when the node type is the bridge node, obtain the tunnel corresponding to the source object The configuration information of the pseudowire is obtained according to the sink object.
  • the above device can be disposed in the network management.
  • FIG. 8 is a block diagram 7 of a service alarm processing apparatus according to Embodiment 2 of the present disclosure. As shown in FIG. 8, the apparatus further includes:
  • the enabling module 82 is configured to enable the stop transmission continuity and connectivity detection packet of the sink object to be enabled when the detection session of the source object fails, and transmit the fault message according to the alarm mapping relationship.
  • FIG. 9 is a block diagram of a service alarm processing system according to Embodiment 3 of the present disclosure. As shown in FIG. 9, the system includes a network management unit 92 and a device 94:
  • the network management unit 92 is configured to set a source object and a sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network, and the source object The first object is connected to the L3VPN network, and the alarm mapping relationship between the source object and the sink object is established. The alarm mapping relationship is sent to the device corresponding to the network element.
  • the device 94 is configured to receive the alarm mapping relationship sent by the network management device, and establish the alarm mapping between the source object and the sink object.
  • the node type is a three-layer L3 core landing node, and the L3 core drop location network element If the inbound interface is disconnected from the inbound interface of the third-party network device, the service alarm mapping is configured to notify the L3VPN side of the network. The protection switching of the network on the L3VPN can ensure the normal transmission of services.
  • FIG. 10 is a flowchart of a service alarm processing method according to Embodiment 4 of the present disclosure. As shown in FIG. 10, the implementation steps are as follows:
  • Step S1001 Setting Virtual Private Forwarding (VRF) to be a multicast VRF.
  • Step S1002 Analyze the calculation source object information:
  • the multicast VRF query the inbound interface of the static multicast configuration information of the multicast service configured by the network element.
  • Step 1 According to the inbound interface of the obtained static multicast configuration information, set the type of the inbound interface and perform interface conversion calculation.
  • Port types include Ethernet interfaces, Ethernet sub-interfaces, aggregation ports, aggregation sub-ports, and point-to-multipoint (P2MP) tunnel interfaces.
  • P2MP point-to-multipoint
  • For the sub-ports convert the name to the Layer 3 interface corresponding to its parent port.
  • the Ethernet sub-interface needs to be converted to the corresponding Ethernet Layer 3 interface.
  • the aggregation sub-port needs to be converted to the corresponding one.
  • Step 2 Calculate the detection session of the inbound interface.
  • the inbound interface is a Layer 3 Ethernet port/Layer 3 aggregation port
  • the detection session of the INTERFACE type is calculated according to the binding relationship between the inbound interface and the detection session.
  • Step 3 Calculate the tracking detection group information of each detection session according to the binding relationship between the detection session and the tracking detection group.
  • Step 4 If the ingress port analyzed in step 1 is a P2MP tunnel interface, the tunnel information is converted according to the tunnel interface information, and the service information of the tunnel carrying the multicast service and the tunnel is calculated.
  • the source object is an inbound interface on the network element and is connected to a third-party network.
  • Step S1003 Analyze and calculate the sink object information:
  • the outbound interface can only be a P2MP tunnel interface.
  • Step 1 Calculate the name of the P2MP tunnel based on the name of the multicast routing outbound interface (P2MP tunnel interface), and calculate the MEG information based on the association between the tunnel name and the MEG of the MPLS-TP-OAM.
  • P2MP tunnel interface the name of the multicast routing outbound interface
  • Step 2 Calculate the MPLS-TP-OAM type detection session packet according to the binding relationship between the MEG and the detection session.
  • Step 3 Perform tunnel information conversion based on the tunnel interface information, and calculate the service information of the tunnel carrying the multicast service and the tunnel.
  • the sink object is an outgoing interface on the network element and is connected to the L3VPN network.
  • Step S1004 Adding the source object to the source tracking detection group, all objects can be selected, and some objects can be selected; the sink object is bound to the source tracking detection group, and all objects can be selected, and some objects can be selected.
  • Step S1005 Check the MPLS-TP-OAM configuration of the tunnel of the source object and the tunnel of the sink object.
  • the information of the source and sink objects indicates whether the MPLS-TP-OAM is configured.
  • Step S1006 Generate an alarm mapping relationship between the source object and the sink object according to the binding relationship between the sink object and the source tracking detection group, and send the device to the device corresponding to the network element for establishing the mapping relationship.
  • FIG. 11 is a schematic diagram of a service alarm according to Embodiment 4 of the present disclosure.
  • the network connected to the L3VPN network is a third-party network. Subsequently, if the detection session managed by the source tracking detection group fails, the sink object sets the MPLS-TP-OAM "Continuity and Connectivity Check (CC) message" of the tunnel to "make” If the network connected to the source object is faulty, you need to perform service switching.
  • CC Continuousity and Connectivity Check
  • the node type is a bridge node.
  • the service alarm mapping is configured to notify the L2VPN network.
  • the L2VPN network performs protection switching to ensure normal service transmission.
  • FIG. 12 is a flowchart of a service alarm processing method according to Embodiment 5 of the present disclosure. As shown in FIG. 12, the implementation steps are as follows:
  • Step S1101 Set Virtual Private Forwarding (VRF) to be a multicast VRF.
  • VRF Virtual Private Forwarding
  • Step S1102 Analyze the calculation source object information:
  • the multicast VRF query the multicast routing configuration information of the multicast service configured by the network element.
  • Step 1 Calculate the next hop configuration information based on the multicast routing information and calculate the corresponding outgoing interface.
  • the outgoing interface here may only be a P2MP tunnel interface.
  • Step 2 Calculate the P2MP tunnel name according to the calculated P2MP tunnel interface in step 1, query the tunnel information on the NE according to the name, and set the detection session according to the binding relationship between the tunnel and the detection session.
  • the type of the detection session is MTE. - TUNNEL type.
  • Step 3 Calculate a tracking detection group that generates each detection session according to the binding relationship between the detection session and the detection group.
  • Step 4 If the P2MP tunnel interface information analyzed in step 1 is used for tunnel information conversion, the service information of the tunnel carrying the multicast service and the end-to-end tunnel is calculated.
  • the source object is an outbound interface on the network element, and is connected to the L3VPN network.
  • Step S1103 Analyze and calculate the sink object information:
  • Step 1 Calculate the pseudowire information of the L2VPN according to the virtual Ethernet port information in the multicast VRF access interface and the service association relationship between the L3VPN and the Layer 2 virtual private network L2VPN.
  • Step 2 Generate MEG information according to the pseudowire calculated in step 1 and the MEG association binding relationship of the MPLS-TP-OAM.
  • Step 3 Calculate a detection session for generating an MPLS-TP-OAM type according to the MEG information calculated in step 2 and the binding association relationship of the detection session.
  • Step 4 According to the pseudowire name calculated in step 1, analyze the pseudowire carried on the network element, and generate the end-to-end pseudowire information.
  • the source object is a pseudowire on the network element, and connects the L3VPN network and the L2VPN network.
  • Step S1104 Add the source object to the source tracking detection group, select all objects, select some objects, bind the sink object to the source tracking detection group, select all objects, and select some objects.
  • Step S1105 Check the MPLS-TP-OAM configuration of the source line's tunnel and the sink object's pseudowire. The information of the source and sink object shows whether the MPLS-TP-OAM is configured.
  • Step S1106 Generate an alarm mapping relationship between the source object and the sink object according to the binding relationship between the object and the source tracking detection group, and send the device to the device corresponding to the network element for establishing the mapping relationship.
  • FIG. 13 is a schematic diagram of a service alarm according to Embodiment 5 of the present disclosure.
  • the network connected to the L3VPN network is an L2VPN network.
  • the sink object sets the MPLS-TP-OAM "Continuity and Connectivity Check (CC) message" of the pseudowire to " Enable, the peer network connected to the sink object knows that the L2VPN network connected to the source object needs to be switched.
  • CC Continuousity and Connectivity Check
  • Embodiment 6 of the present disclosure also provides a storage medium.
  • an embodiment of the present disclosure also provides a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • the computer readable storage medium may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the source object and the sink object of the multicast service of the Layer 3 virtual private network L3VPN configured on the network element, where the network element is connected to the first network and the L3VPN network, where the source object and the sink object respectively Connecting the first network to the L3VPN network;
  • the alarm mapping relationship is sent to the device corresponding to the network element.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs the above steps S1, S2, and S3 according to the stored program code in the storage medium.
  • the embodiment of the present disclosure further provides a schematic structural diagram of an electronic device.
  • the electronic device Includes:
  • At least one processor 140 which is exemplified by a processor 140 in FIG. 14; and a memory 141, may further include a communication interface 142 and a bus 143.
  • the processor 140, the communication interface 142, and the memory 141 can complete communication with each other through the bus 143.
  • Communication interface 142 can be used for information transfer.
  • Processor 140 may invoke logic instructions in memory 141 to perform the methods of the above-described embodiments.
  • logic instructions in the memory 141 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the memory 141 is a computer readable storage medium, and can be used to store a software program, a computer executable program, a program instruction/module corresponding to the method in the embodiment of the present disclosure.
  • the processor 140 executes the function application and the data processing by executing the software program, the instruction and the module stored in the memory 141, that is, the service alarm processing method in the foregoing method embodiment.
  • the memory 141 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to use of the terminal device, and the like. Further, the memory 141 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • modules or steps of the present disclosure may be Implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, optionally, they may be implemented by program code executable by the computing device, such that They may be stored in a storage device by a computing device, and in some cases, the steps shown or described may be performed in an order different than that herein, or separately fabricated into individual integrated circuit modules, or Implementing multiple modules or steps in them as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
  • the method, device and system for processing service alarms provided by the present application solve the problem that when the network failure occurs and the service is performed, the above fault cannot be transmitted from the network on the side where the failure occurs to the network on the other side.

Landscapes

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

Abstract

本申请提供了一种业务告警处理方法，包括：设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；建立所述源对象与所述宿对象之间的告警映射关系；将所述告警映射关系发送给所述网元对应的设备。通过上述方法，一旦网络连接出现故障需要进行传输链路倒换，而主备网元之间又发生连接故障，导致另一侧网络无法获知该故障时，通过源宿对象映射关系的建立可以将故障消息从故障发生一侧网络传送到另一侧网络，以实现主备传输链路的倒换等操作。此外，本申请还提供了一种业务告警处理装置与系统。

Description

一种业务告警处理方法、装置及系统 技术领域
本申请涉及通信领域，例如涉及一种业务告警处理的方法、装置及系统。
背景技术
在长期演进(Long Term Evolution，LTE)组网场景中，三层虚拟专用网(L3 Virtual Private Network，L3VPN)组播业务已经逐步在现网中部署应用。
通常情况下，网络中会配备有主备两条传输链路，主传输链路发生故障时，备用传输链路就会接替主传输链路进行后续的数据传输。当主传输链路中的一个主传输网元恰好跨接于两个不同的网络之间，且该网元一侧网络发生链路故障，需要进行传输链路的倒换时，如果该网元与其对应的备用网元在该链路故障网络一侧的连接也同时出现故障的话，另一侧的网络是无法获知该故障信息的，从而无法实现主备链路之间的倒换，最后影响到业务的传输。
相关技术无法实现上述情形下，将故障信息从发生故障的一侧网络传输到另一侧网络。
发明内容
本公开提供了一种业务告警处理方法、装置及系统，以解决相关技术在网络出现故障影响业务进行时，无法将上述故障从发生故障的一侧网络传输到另一侧网络的问题。
本公开实施例的技术方案实现如下：
本公开实施例提供了一种业务告警处理方法，包括：
设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；
建立所述源对象与所述宿对象之间的告警映射关系；
将所述告警映射关系发送给所述网元对应的设备。
设置所述网元上所配置的所述L3VPN的组播业务的源对象与宿对象可以包括：
设置虚拟专用网路由转发VRF为组播VRF，依据所述组播VRF查询所述组播业务的接入端口；
根据所述接入端口设置所述网元的节点类型；
依据所述节点类型设置所述源对象与所述宿对象。
根据所述接入端口设置所述网元的节点类型可以包括：
在所述接入端口不包括虚拟以太网类型的接口时，设置所述网元的节点类型为三层核心落地节点；
在所述接入端口包括虚拟以太网类型的接口时，设置所述网元的节点类型为桥接节点。
依据所述节点类型设置所述源对象与所述宿对象可以包括：
在所述节点类型为所述三层核心落地节点时，依据所述组播VRF获取所述组播业务的静态组播配置信息的入接口，设置所述源对象为所述入接口；依据所述组播VRF获取所述静态组播配置信息的出接口，设置所述宿对象为所述出接口；
在所述节点类型为所述桥接节点时，依据所述组播VRF获取所述组播业务的组播路由配置信息的出接口，设置所述源对象为所述出接口；依据所述组播业务的接入端口以及所述L3VPN与二层虚拟专用网L2VPN的业务关联关系获取所述L2VPN的伪线，设置所述宿对象为所述伪线。
建立所述源对象与所述宿对象的所述告警映射关系可以包括：
获取所述源对象的检测会话，根据所述检测会话生成源跟踪检测组；
将所述源对象加入到所述源跟踪检测组，并将所述宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；
判断所述源对象的隧道以及所述宿对象的隧道或伪线是否存在多协议标签交换传送应用操作、管理和维护MPLS-TP-OAM的配置；
在存在所述配置的情况下，依据所述绑定关系建立所述源对象与所述宿对象之间的所述告警映射关系。
获取所述源对象的所述检测会话可以包括：
在所述节点类型为所述三层核心落地节点时，依据所述入接口设置三层以太网接口或者三层聚合端口；依据所述三层以太接口或者所述三层聚合端口获取所述源对象的检测会话，其中，该检测会话为接口类型的检测会话；
在所述节点类型为所述桥接节点时，依据所述出接口获取所述网元的隧道信息；依据所述隧道信息获取所述源对象的检测会话，其中，该检测会话为组播隧道类型的检测会话。
依据所述入接口设置所述三层以太网接口或者所述三层聚合端口可以包括：
在所述入接口包括以太网接口或者聚合端口时，维持所述以太网接口或者所述聚合端口不变；
在所述入接口包括以太网子接口或者聚合子端口时，将所述以太网子接口或者所述聚合子端口转换为对应的以太网接口或者聚合端口。
判断所述源对象的隧道与所述宿对象的隧道或伪线是否存在所述MPLS-TP-OAM的配置可以包括：
在所述节点类型为所述三层核心落地节点时，判断所述宿对象的隧道是否存在所述MPLS-TP-OAM的配置；
在所述节点类型为所述桥接节点时，判断所述源对象的隧道与所述宿对象的伪线是否存在所述MPLS-TP-OAM的配置。
在判断所述源对象的隧道与所述宿对象的隧道和伪线是否存在所述MPLS-TP-OAM的配置之前，所述方法还可以包括：
当所述节点类型为所述三层核心落地节点时，获取所述宿对象对应的所述隧道的配置信息；
当所述节点类型为所述桥接节点时，获取所述源对象对应的所述隧道的配置信息；依据所述宿对象，获取所述伪线的配置信息。
将所述告警映射关系发送给所述网元对应的设备之后，所述方法还可以包 括：
在所述源对象的所述检测会话失效的情况下，将所述宿对象配置的所述MPLS-TP-OAM中的停止发送连续性和连通性检测报文设置为使能，依据所述告警映射关系传递故障消息。
当所述节点类型为所述三层核心落地节点时，所述入接口可以包括以太网接口、以太网子接口、聚合端口、聚合子端口或隧道接口，所述出接口可以为所述隧道接口，所述第一网络可以为第三方网络；当所述节点类型为所述桥接节点时，所述出接口可以为所述隧道接口；所述第一网络可以为所述L2VPN网络。
本公开实施例还提供了一种业务告警处理装置，可以包括：
设置模块，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；
建立模块，被配置为建立所述源对象与所述宿对象的之间告警映射关系；
发送模块，被配置为将所述告警映射关系发送给所述网元对应的设备。
所述设置模块可以包括：
查询子模块，被配置为设置虚拟专用网路由转发VRF为组播VRF，依据所述组播VRF查询所述组播业务的接入端口；
第一设置子模块，被配置为根据所述接入端口设置所述网元的节点类型；
第二设置子模块，被配置为依据所述节点类型设置所述源对象与所述宿对象。
所述第一设置子模块可以包括：
第一设置单元，被配置为在所述接入端口不包括虚拟以太网类型的接口时，设置所述网元的节点类型为三层核心落地节点；
第二设置单元，被配置为在所述接入端口包括虚拟以太网类型的接口时，设置所述网元的节点类型为桥接节点。
所述第一获取子模块可以包括：
第二设置子模块包括：
第三设置单元，被配置为在所述节点类型为所述三层核心落地节点时，依据所述组播VRF获取所述组播业务的静态组播配置信息的入接口，设置所述源对象为所述入接口；依据所述组播VRF获取所述静态组播配置信息的出接口，设置所述宿对象为所述出接口；
第四设置单元，被配置为在所述节点类型为所述桥接节点时，依据所述组播VRF获取所述组播业务的组播路由配置信息的出接口，设置所述源对象为所述出接口；依据所述组播业务的接入端口以及所述L3VPN与二层虚拟专用网L2VPN的业务关联关系获取所述L2VPN的伪线，设置所述宿对象为所述伪线。
所述建立模块可以包括：
获取子模块，被配置为获取所述源对象的检测会话，根据所述检测会话生成源跟踪检测组；
绑定子模块，被配置为将所述源对象加入到所述源跟踪检测组，并将所述宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；
判断子模块，被配置为判断所述源对象的隧道以及所述宿对象的隧道和伪线是否存在多协议标签交换传送应用操作、管理和维护MPLS-TP-OAM的配置；
建立子模块，被配置为在存在所述配置的情况下，依据所述绑定关系建立所述源对象与所述宿对象之间的所述告警映射关系。
所述获取子模块可以被配置为：在所述节点类型为所述三层核心落地节点时，依据所述入接口设置三层以太网接口或者三层聚合端口；依据所述三层以太接口或者所述三层聚合端口获取所述源对象的检测会话，其中，所述检测会话为接口类型的检测会话；
在所述节点类型为所述桥接节点时，依据所述出接口获取所述网元的隧道信息；依据所述隧道信息获取所述源对象的检测会话，其中，所述检测会话为组播隧道类型的检测会话。
所述判断子模块可以被配置为：
在所述节点类型为所述三层核心落地节点时，判断所述宿对象的隧道是否存在所述MPLS-TP-OAM的配置；
在所述节点类型为所述桥接节点时，判断所述源对象的隧道与所述宿对象的伪线是否存在所述MPLS-TP-OAM的配置。
所述装置还可以包括：
获取模块，被配置为当所述节点类型为所述三层核心落地节点时，获取所述宿对象对应的所述隧道的配置信息；
当所述节点类型为所述桥接节点时，获取所述源对象对应的所述隧道的配置信息；依据所述宿对象，获取所述伪线的配置信息。
所述装置还可以包括：
使能模块，被配置为在所述源对象的所述检测会话失效的情况下，将所述宿对象的停止发送连续性和连通性检测报文设置为使能，依据所述告警映射关系传递故障消息。
上述装置可以设置于网管中。
本公开实施例还提供了一种业务告警处理系统，包括网管以及设备：
所述网管，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；建立所述源对象与所述宿对象之间的告警映射关系；将所述告警映射关系发送给所述网元对应的设备。
所述设备，被配置为接收所述网管发送的所述告警映射关系，并在所述源对象与所述宿对象之间建立所述告警映射。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
本公开实施例还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述 至少一个处理器执行，以使所述至少一个处理器执行上述的方法。
本申请中，通过获取网元上所配置的L3VPN组播业务的源对象与宿对象，并建立二者的对应关系，一旦网络连接出现故障需要进行传输链路倒换，而主备网元之间又发生连接故障，导致另一侧网络无法获知该故障时，通过源宿对象映射关系的建立可以将故障消息从故障发生一侧网络传送到另一侧网络，以实现后续主备传输链路的倒换等操作。
附图概述
图1是根据本公开实施例一的一种业务告警处理方法流程图；
图2是根据本公开实施例二的一种业务告警处理装置框图一；
图3是根据本公开实施例二的一种业务告警处理装置框图二；
图4是根据本公开实施例二的一种业务告警处理装置框图三；
图5是根据本公开实施例二的一种业务告警处理装置框图四；
图6是根据本公开实施例二的一种业务告警处理装置框图五；
图7是根据本公开实施例二的一种业务告警处理装置框图六；
图8是根据本公开实施例二的一种业务告警处理装置框图七；
图9是根据本公开实施例三的一种业务告警处理系统框图；
图10是根据本公开实施例四的一种业务告警处理方法流程图；
图11是根据本公开实施例四的一种业务告警示意图；
图12是根据本公开实施例五的一种业务告警处理方法流程图；
图13是根据本公开实施例五的一种业务告警示意图；以及
图14是根据本公开实施例的电子设备的结构示意图。
具体实施方式
以下结合附图和实施例对本公开的方案进行详细说明，应当理解，以下所说明的实施例仅用于说明和解释本公开，并不用于限定本公开。
实施例一
图1是根据本公开实施例一的一种业务告警处理方法流程图，如图1所示，该方法包括以下步骤：
步骤S102，设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，该网元跨接于第一网络与该L3VPN网络，该源对象与该宿对象分别连接该第一网络与该L3VPN网络；
步骤S104，建立该源对象与该宿对象之间的告警映射关系；
步骤S106，将该告警映射关系发送给该网元对应的设备。
上述步骤S102与S104是网管上的配置操作，步骤S106是将网管上配置好的信息下发对应的设备用于实际映射关系的建立。
在第一网络为第三方网络的情况下，源对象为网元上的入接口，连接第三方网络，宿对象为网元上的出接口，连接L3VPN网络；在第一网络为L2VPN网络的情况下，源对象为网元上的出接口，连接L3VPN网络，宿对象为网元上的伪线，连接L3VPN网络与L2VPN网络。
通过上述方法，一旦网络连接出现故障需要进行传输链路倒换，而主备网元之间又发生连接故障，导致另一侧网络无法获知该故障时，通过源宿对象映射关系的建立可以将故障消息传送到另一侧网络，以实现后续主备传输链路的倒换等操作。
设置该网元上所配置的该L3VPN的组播业务的源对象与宿对象可以包括：设置虚拟专用网路由转发VRF为组播VRF，依据该组播VRF查询该组播业务的接入端口；根据该接入端口设置该网元的节点类型；依据该节点类型设置该源对象与该宿对象。
根据该接入端口设置该网元的节点类型可以包括：在该接入端口不包括虚拟以太网类型的接口时，设置该网元的节点类型为三层核心落地节点；在该接入端口包括虚拟以太网类型的接口时，设置该网元的节点类型为桥接节点。
依据该节点类型设置该源对象与该宿对象可以包括：在该节点类型为该三 层核心落地节点时，依据该组播VRF获取该组播业务的静态组播配置信息的入接口，设置该源对象为该入接口；依据该组播VRF获取该静态组播配置信息的出接口，设置该宿对象为该出接口；
在该节点类型为该桥接节点时，依据该组播VRF获取该组播业务的组播路由配置信息的出接口，设置该源对象为该出接口；依据该组播业务的接入端口以及该L3VPN与二层虚拟专用网L2VPN的业务关联关系获取该L2VPN的伪线，设置该宿对象为该伪线。
建立该源对象与该宿对象的该告警映射关系可以包括：
获取该源对象的检测会话，根据该检测会话生成源跟踪检测组；将该源对象加入到该源跟踪检测组，并将该宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；判断该源对象的隧道以及该宿对象的隧道或伪线是否存在多协议标签交换传送应用操作、管理和维护(MPLS-TP-OAM)的配置；在存在该配置的情况下，依据该绑定关系建立该源对象与该宿对象之间的该告警映射关系。
获取该源对象的检测会话可以包括：在该节点类型为该三层核心落地节点时，依据该入接口设置三层以太网接口或者三层聚合端口；依据该三层以太接口或者该三层聚合端口获取该源对象的检测会话，其中，该检测会话为接口类型的检测会话；在该节点类型为该桥接节点时，依据该出接口获取该网元的隧道信息；依据该隧道信息获取该源对象的检测会话，其中，该检测会话为组播隧道类型的检测会话。
检测会话是一种检测手段，通过获取检测会话的信息，可以判断源对象是否可以正常通信，宿对象是否可以正常通信。
源对象的检测会话中携带有源对象的信息，将源对象加入源跟踪检测组在实际操作中表现为将源对象的检测会话加入源跟踪检测组。宿对象与源跟踪检测组进行绑定，间接地就是宿对象与源对象的绑定。绑定对策可以是源跟踪检测组中的所有源对象都失效后，绑定的宿对象启动工作；也可以是源跟踪检测组中的部分源对象失效后，绑定的宿对象启动工作。
可以设置全部源对象加入源跟踪检测组，全部宿对象与源跟踪监测组绑定；也可以选取一部分源对象加入源跟踪检测组，一部分宿对象与源跟踪监测组绑定。其中，跟踪检测组可以是查询到的网元中已有的检测组，也可以是网管设 置生成的检测组。
获取该源对象的该检测会话可以包括：在该节点类型为该三层核心落地节点时，依据该入接口设置三层以太网接口或者三层聚合端口；依据该三层以太接口或者该三层聚合端口获取该源对象的检测会话，其中，该检测会话为接口类型的检测会话；在该节点类型为该桥接节点时，依据该出接口获取该网元的隧道信息；依据该隧道信息获取该源对象的检测会话，其中，该检测会话为组播隧道类型的检测会话。
依据该入接口设置该三层以太网接口或者该三层聚合端口可以包括：
在该入接口包括以太网接口或者聚合端口时，维持该以太网接口或者该聚合端口不变；在该入接口包括以太网子接口或者聚合子端口时，将该以太网子接口或者该聚合子端口转换为对应的以太网接口或者聚合端口。
通过上述操作，可以过滤到相同的入接口，防止相同的入接口创建相同的检测会话，造成检测会话的冗余。
判断该源对象的隧道与该宿对象的隧道或伪线是否存在该MPLS-TP-OAM的配置可以包括：在该节点类型为该三层核心落地节点时，判断该宿对象的隧道是否存在该MPLS-TP-OAM的配置；在该节点类型为该桥接节点时，判断该源对象的隧道与该宿对象的伪线是否存在该MPLS-TP-OAM的配置。
在该节点类型为该三层核心落地节点时，如果源对象，即网元的入接口还包括隧道接口的情况下，需要判断源对象对应的隧道是否存在该MPLS-TP-OAM的配置。
在判断该源对象的隧道与该宿对象的隧道和伪线是否存在该MPLS-TP-OAM的配置之前，该方法还可以包括：当该节点类型为该三层核心落地节点时，获取该宿对象对应的该隧道的配置信息；当该节点类型为该桥接节点时，获取该源对象对应的该隧道的配置信息；依据该宿对象，获取该伪线的配置信息。
其中，该隧道为点到多点P2MP隧道。
将该告警映射关系发送给该网元对应的设备之后，该方法还可以包括：
在该源对象的该检测会话失效的情况下，将该宿对象配置的MPLS-TP-0AM 中的停止发送连续性和连通性检测报文设置为使能，依据该告警映射关系传递故障消息。
通过上述步骤，一旦网络发生故障，而主备网元之间又发生连接故障，通过设置宿对象，此时与宿对象相连的对端网络就知道源对象连接的网络发生故障需要进行业务倒换
当该节点类型为该三层核心落地节点时，网元的入接口可以包括以太网接口、以太网子接口、聚合端口或聚合子端口或P2MP隧道接口，该出接口可以为P2MP隧道接口，该第一网络可以为第三方网络；当该节点类型为该桥接节点时，网元的出接口可以为该P2MP隧道接口，该第一网络可以为L2VPN网络。
实施例二
本公开实施例二还提供了一种业务告警处理装置，图2是根据本公开实施例二的一种业务告警处理装置框图一，如图2所示，该装置包括：
设置模块22，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，该网元跨接于第一网络与该L3VPN网络，该源对象与该宿对象分别连接该第一网络与该L3VPN网络；
建立模块24，被配置为建立该源对象与该宿对象的之间告警映射关系；
发送模块26，被配置为将该告警映射关系发送给该网元对应的设备。
图3是根据本公开实施例二的一种业务告警处理装置框图二，如图3所示，该设置模块22包括：
查询子模块32，被配置为设置虚拟专用网路由转发VRF为组播VRF，依据该组播VRF查询该组播业务的接入端口；
第一设置子模块34，被配置为根据该接入端口设置该网元的节点类型；
第二设置子模块36，被配置为依据该节点类型设置该源对象与该宿对象。
图4是根据本公开实施例二的一种业务告警处理装置框图三，如图4所示，该第一设置子模块34包括：
第一设置单元42，被配置为在该接入端口不包括虚拟以太网类型的接口时，设置该网元的节点类型为三层核心落地节点；
第二设置单元44，被配置为在该接入端口包括虚拟以太网类型的接口时，设置该网元的节点类型为桥接节点。
图5是根据本公开实施例二的一种业务告警处理装置框图四，如图5所示，该第二设置子模块36包括：
第三设置单元52，被配置为在该节点类型为该三层核心落地节点时，依据该组播VRF获取该组播业务的静态组播配置信息的入接口，设置该源对象为该入接口；依据该组播VRF获取该静态组播配置信息的出接口，设置该宿对象为该出接口；
第四设置单元54，被配置为在该节点类型为该桥接节点时，依据该组播VRF获取该组播业务的组播路由配置信息的出接口，设置该源对象为该出接口；依据该组播业务的接入端口以及该L3VPN与二层虚拟专用网L2VPN的业务关联关系获取该L2VPN的伪线，设置该宿对象为该伪线。
图6是根据本公开实施例二的一种业务告警处理装置框图五，如图6所示，该建立模块24包括：
获取子模块62，被配置为获取该源对象的检测会话，根据该检测会话生成源跟踪检测组；
绑定子模块64，被配置为将该源对象加入到该源跟踪检测组，并将该宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；
判断子模块66，被配置为判断该源对象的隧道以及该宿对象的隧道和伪线是否存在多协议标签交换传送应用操作、管理和维护MPLS-TP-OAM的配置；
建立子模块68，被配置为在存在该配置的情况下，依据该绑定关系建立该源对象与该宿对象之间的该告警映射关系。
该获取子模块62可以被配置为：
在该节点类型为该三层核心落地节点时，依据该入接口设置三层以太网接口或者三层聚合端口；依据该三层以太接口或者该三层聚合端口获取该源对象的检测会话，其中，该检测会话为接口类型的检测会话；
在该节点类型为该桥接节点时，依据该出接口获取该网元的隧道信息；依据该隧道信息获取该源对象的检测会话，其中，该检测会话为组播隧道类型的 检测会话。
该判断子模块66可以包括：在该节点类型为该三层核心落地节点时，判断该宿对象的隧道是否存在该MPLS-TP-OAM的配置；
在该节点类型为该桥接节点时，判断该源对象的隧道与该宿对象的伪线是否存在该MPLS-TP-OAM的配置。
图7是根据本公开实施例二的一种业务告警处理装置框图六，如图7所示，该装置还包括：
获取模块72，被配置为当该节点类型为该三层核心落地节点时，获取该宿对象对应的该隧道的配置信息；当该节点类型为该桥接节点时，获取该源对象对应的该隧道的配置信息；依据该宿对象，获取该伪线的配置信息。上述装置可以设置于网管中。
图8是根据本公开实施例二的一种业务告警处理装置框图七，如图8所示，该装置还包括：
使能模块82，被配置为在该源对象的该检测会话失效的情况下，将该宿对象的停止发送连续性和连通性检测报文设置为使能，依据该告警映射关系传递故障消息。
实施例三
本公开实施例还提供了一种业务告警处理系统，图9是根据本公开实施例三的一种业务告警处理系统框图，如图9所示，该系统包括网管92以及设备94：
该网管92，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，该网元跨接于第一网络与该L3VPN网络，该源对象与该宿对象分别连接该第一网络与该L3VPN网络；建立该源对象与该宿对象之间的告警映射关系；将该告警映射关系发送给该网元对应的设备。
该设备94，被配置为接收该网管发送的该告警映射关系，并在该源对象与该宿对象之间建立该告警映射。
实施例四
本实施例四中，节点类型为三层L3核心落地节点，当L3核心落地点网元 与第三方网络设备间连接的入方向接口出现全部断纤情况下，此时配置业务告警映射，将故障通知到L3VPN侧网络，可以实现L3VPN侧网络的保护倒换，保证业务的正常传输。图10是根据本公开实施例四的一种业务告警处理方法流程图，如图10所示，其实施步骤说明如下：
步骤S1001：设置虚拟专用网路由转发(Virtual Routing Forwarding，VRF)为组播VRF。
步骤S1002：分析计算源对象信息：
根据组播VRF，查询分析网元所配置的组播业务的静态组播配置信息的入接口。
针对上述业务的基本信息进行如下步骤的计算：
步骤1：根据获取的静态组播配置信息的入接口，设置入接口的类型并进行接口转换计算。端口类型包括以太网接口、以太网子接口、聚合端口、聚合子端口、点到多点(point 2multiple point，P2MP)隧道接口。对于其中的子端口，将其名称转换为其父端口对应的三层口，如以太网子接口，需要将其转换为对应的以太网三层口；聚合子端口，需要将其转换为对应的聚合端口三层口，并过滤掉相同的对象；
步骤2：计算入接口的检测会话。当入接口为三层以太端口/三层聚合端口时，根据入接口与检测会话的绑定关系，计算输出INTERFACE类型的检测会话。
步骤3：根据检测会话与跟踪检测组的绑定关系，计算各个检测会话的跟踪检测组信息；
步骤4：如果步骤1分析的入端口为P2MP隧道接口，根据隧道接口信息进行隧道信息转换，计算出承载组播业务的隧道以及隧道的业务信息。
实施例四中，源对象为网元上的入接口，连接第三方网络。
步骤S1003：分析计算宿对象信息：
根据业务的VRF，查询分析网元所配置的组播业务的静态组播配置信息，此时，出接口只可能是P2MP隧道接口。
针对上述业务的基本信息进行如下步骤的计算：
步骤1：依据组播路由出端口(P2MP隧道接口)的名称转换计算出P2MP隧道的名称，并根据隧道名称与MPLS-TP-OAM的MEG关联绑定关系，计算出MEG信息；
步骤2：根据MEG与检测会话的绑定关联关系，计算生成MPLS-TP-OAM类型的检测会话报文；
步骤3：根据隧道接口信息进行隧道信息转换，计算出承载组播业务的隧道以及隧道的业务信息。
实施例四中，宿对象为网元上的出接口，连接L3VPN网络。
步骤S1004：将源对象加入到源跟踪检测组，可以选择所有对象、可以选择一部分对象；将宿对象与源跟踪检测组进行绑定，可以选择所有对象、可以选择一部分对象。
步骤S1005：校验源对象的隧道和宿对象的隧道的MPLS-TP-OAM配置，源宿对象的信息中会显示MPLS-TP-OAM是否已有配置。
步骤S1006：依据宿对象与源跟踪检测组的绑定关系生成源对象与宿对象之间的告警映射关系，下发至网元对应的设备用于映射关系的建立。
图11是根据本公开实施例四的一种业务告警示意图，与L3VPN网络相连的网络为第三方网络。后续，如果源跟踪检测组管理的检测会话失效，宿对象就会将隧道的MPLS-TP-OAM的“停止发送连续性和连通性检测(Continuity and Connectivity Check，CC)报文”设置为“使能”，此时与宿对象相连第三方网络就知道源对象连接的网络发生故障需要进行业务倒换。
实施例五
本实施例五中，节点类型为桥接节点。当在二三层桥接节点的入方向接口出现断纤情况下，此时配置业务告警映射，将故障通知到L2VPN侧网络，L2VPN侧网络就会进行保护倒换，保证业务的正常传输。图12是根据本公开实施例五的一种业务告警处理方法流程图，如图12所示，其实施步骤说明如下：
步骤S1101：设置虚拟专用网路由转发(Virtual Routing Forwarding，VRF)为组播VRF。
步骤S1102：分析计算源对象信息：
根据组播VRF，查询分析网元所配置的组播业务的组播路由配置信息。
步骤1：根据组播路由信息，计算出“下一跳配置”信息，计算对应的出接口。这里出接口仅可能是P2MP隧道接口。
步骤2：根据步骤1中的计算的P2MP隧道接口转换计算出P2MP隧道名称，根据名称查询该网元上的隧道信息，依据隧道与检测会话的绑定关系设置检测会话，检测会话的类型为MTE-TUNNEL类型。
步骤3：根据检测会话与检测组的绑定关系，计算生成各个检测会话的跟踪检测组。
步骤4：如果步骤1分析的P2MP隧道接口信息进行隧道信息转换，计算出承载组播业务的隧道以及所属端到端隧道的业务信息。
实施例五中，源对象为网元上的出接口，连接L3VPN网络。
步骤S1103：分析计算宿对象信息：
步骤1：根据组播VRF接入接口中的虚拟以太网端口信息以及L3VPN与二层虚拟专用网L2VPN的业务关联关系计算生成L2VPN的伪线信息。
步骤2：根据步骤1中计算出来的伪线以及MPLS-TP-OAM的MEG关联绑定关系，生成MEG信息；
步骤3：根据步骤2中计算的MEG信息以及检测会话的绑定关联关系，计算生成MPLS-TP-OAM类型的检测会话。
步骤4：根据步骤1中计算的伪线名称，分析出该网元上承载的伪线，并生成计算所属端到端伪线信息。
实施例五中，源对象为网元上的伪线，连接L3VPN网络与L2VPN网络。
步骤S1104：将源对象加入到源跟踪检测组，可以选择所有对象、可以选择一部分对象；将宿对象与源跟踪检测组进行绑定，可以选择所有对象、可以选择一部分对象。
步骤S1105：校验源对象的隧道和宿对象的伪线的MPLS-TP-OAM配置，源宿对象的信息中会显示MPLS-TP-OAM是否已有配置。
步骤S1106：依据对象与源跟踪检测组的绑定关系生成源对象与宿对象之间的告警映射关系，下发至网元对应的设备用于映射关系的建立。
图13是根据本公开实施例五的一种业务告警示意图，与L3VPN网络相连的网络为L2VPN网络。后续，如果源跟踪检测组管理的检测会话失效，宿对象就会将伪线的MPLS-TP-OAM的“停止发送连续性和连通性检测(Continuity and Connectivity Check，CC)报文”设置为“使能”，此时与宿对象相连的对端网络就知道源对象连接的L2VPN网络发生故障需要进行业务倒换。
实施例六
本公开的实施例六还提供了一种存储介质。例如，本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。所述计算机可读存储介质可以是暂态计算机可读存储介质，也可以是非暂态计算机可读存储介质。
可选地，在本实施例六中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，该网元跨接于第一网络与该L3VPN网络，该源对象与该宿对象分别连接该第一网络与该L3VPN网络；
S2，建立该源对象与该宿对象之间的告警映射关系；
S3，将该告警映射关系发送给该网元对应的设备。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述步骤S1、S2以及S3。
可选地，本实施例中的示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本公开实施例还提供了一种电子设备的结构示意图。参见图14，该电子设 备包括：
至少一个处理器(processor)140，图14中以一个处理器140为例；和存储器(memory)141，还可以包括通信接口(Communications Interface)142和总线143。其中，处理器140、通信接口142、存储器141可以通过总线143完成相互间的通信。通信接口142可以用于信息传输。处理器140可以调用存储器141中的逻辑指令，以执行上述实施例的方法。
此外，上述的存储器141中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器141作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令/模块。处理器140通过运行存储在存储器141中的软件程序、指令以及模块，从而执行功能应用以及数据处理，即实现上述方法实施例中的业务告警处理方法。
存储器141可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器141可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开实施例的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质，也可以是暂态存储介质。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以 用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
工业实用性
本申请提供的业务告警处理的方法、装置及系统，解决了在网络出现故障影响业务进行时，无法将上述故障从发生故障的一侧网络传输到另一侧网络的问题。

Claims (23)

  1. 一种业务告警处理方法，包括：
    设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；
    建立所述源对象与所述宿对象之间的告警映射关系；
    将所述告警映射关系发送给所述网元对应的设备。
  2. 如权利要求1所述的方法，其中，设置所述网元上所配置的所述L3VPN的组播业务的源对象与宿对象包括：
    设置虚拟专用网路由转发VRF为组播VRF，依据所述组播VRF查询所述组播业务的接入端口；
    根据所述接入端口设置所述网元的节点类型；
    依据所述节点类型设置所述源对象与所述宿对象。
  3. 如权利要求2所述的方法，其中，根据所述接入端口设置所述网元的节点类型包括：
    在所述接入端口不包括虚拟以太网类型的接口时，设置所述网元的节点类型为三层核心落地节点；
    在所述接入端口包括虚拟以太网类型的接口时，设置所述网元的节点类型为桥接节点。
  4. 如权利要求3所述的方法，其中，依据所述节点类型设置所述源对象与所述宿对象包括：
    在所述节点类型为所述三层核心落地节点时，依据所述组播VRF获取所述 组播业务的静态组播配置信息的入接口，设置所述源对象为所述入接口；依据所述组播VRF获取所述静态组播配置信息的出接口，设置所述宿对象为所述出接口；
    在所述节点类型为所述桥接节点时，依据所述组播VRF获取所述组播业务的组播路由配置信息的出接口，设置所述源对象为所述出接口；依据所述组播业务的接入端口以及所述L3VPN与二层虚拟专用网L2VPN的业务关联关系获取所述L2VPN的伪线，设置所述宿对象为所述伪线。
  5. 如权利要求4所述的方法，其中，建立所述源对象与所述宿对象的所述告警映射关系包括：
    获取所述源对象的检测会话，根据所述检测会话生成源跟踪检测组；
    将所述源对象加入到所述源跟踪检测组，并将所述宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；
    判断所述源对象的隧道以及所述宿对象的隧道或伪线是否存在多协议标签交换传送应用操作、管理和维护MPLS-TP-OAM的配置；
    在存在所述配置的情况下，依据所述绑定关系建立所述源对象与所述宿对象之间的所述告警映射关系。
  6. 如权利要求5所述的方法，其中，获取所述源对象的所述检测会话包括：
    在所述节点类型为所述三层核心落地节点时，依据所述入接口设置三层以太网接口或者三层聚合端口；依据所述三层以太接口或者所述三层聚合端口获取所述源对象的检测会话，其中，该检测会话为接口类型的检测会话；
    在所述节点类型为所述桥接节点时，依据所述出接口获取所述网元的隧道信息；依据所述隧道信息获取所述源对象的检测会话，其中，该检测会话为组 播隧道类型的检测会话。
  7. 如权利要求6所述的方法，其中，依据所述入接口设置所述三层以太网接口或者所述三层聚合端口包括：
    在所述入接口包括以太网接口或者聚合端口时，维持所述以太网接口或者所述聚合端口不变；
    在所述入接口包括以太网子接口或者聚合子端口时，将所述以太网子接口或者所述聚合子端口转换为对应的以太网接口或者聚合端口。
  8. 如权利要求5所述的方法，其中，判断所述源对象的隧道与所述宿对象的隧道或伪线是否存在所述MPLS-TP-OAM的配置包括：
    在所述节点类型为所述三层核心落地节点时，判断所述宿对象的隧道是否存在所述MPLS-TP-OAM的配置；
    在所述节点类型为所述桥接节点时，判断所述源对象的隧道与所述宿对象的伪线是否存在所述MPLS-TP-OAM的配置。
  9. 如权利要求5-8任一所述的方法，其中，在判断所述源对象的隧道与所述宿对象的隧道和伪线是否存在所述MPLS-TP-OAM的配置之前，所述方法还包括：
    当所述节点类型为所述三层核心落地节点时，获取所述宿对象对应的所述隧道的配置信息；
    当所述节点类型为所述桥接节点时，获取所述源对象对应的所述隧道的配置信息；依据所述宿对象，获取所述伪线的配置信息。
  10. 如权利要求5-8任一所述的方法，其中，将所述告警映射关系发送给所述网元对应的设备之后，所述方法还包括：
    在所述源对象的所述检测会话失效的情况下，将所述宿对象配置的所述MPLS-TP-OAM中的停止发送连续性和连通性检测报文设置为使能，依据所述告警映射关系传递故障消息。
  11. 如权利要求5-8任一所述的方法，其中，当所述节点类型为所述三层核心落地节点时，所述入接口包括以太网接口、以太网子接口、聚合端口、聚合子端口或隧道接口，所述出接口为所述隧道接口，所述第一网络为第三方网络；当所述节点类型为所述桥接节点时，所述出接口为所述隧道接口，所述第一网络为所述L2VPN网络。
  12. 一种业务告警处理装置，包括：
    设置模块，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；
    建立模块，被配置为建立所述源对象与所述宿对象的之间告警映射关系；
    发送模块，被配置为将所述告警映射关系发送给所述网元对应的设备。
  13. 如权利要求12所述的装置，其中，所述设置模块包括：
    查询子模块，被配置为设置虚拟专用网路由转发VRF为组播VRF，依据所述组播VRF查询所述组播业务的接入端口；
    第一设置子模块，被配置为根据所述接入端口设置所述网元的节点类型；
    第二设置子模块，被配置为依据所述节点类型设置所述源对象与所述宿对象。
  14. 如权利要求13所述的装置，其中，所述第一设置子模块包括：
    第一设置单元，被配置为在所述接入端口不包括虚拟以太网类型的接口时， 设置所述网元的节点类型为三层核心落地节点；
    第二设置单元，被配置为在所述接入端口包括虚拟以太网类型的接口时，设置所述网元的节点类型为桥接节点。
  15. 如权利要求14所述的装置，其中，所述第二设置子模块包括：
    第三设置单元，被配置为在所述节点类型为所述三层核心落地节点时，依据所述组播VRF获取所述组播业务的静态组播配置信息的入接口，设置所述源对象为所述入接口；依据所述组播VRF获取所述静态组播配置信息的出接口，设置所述宿对象为所述出接口；
    第四设置单元，被配置为在所述节点类型为所述桥接节点时，依据所述组播VRF获取所述组播业务的组播路由配置信息的出接口，设置所述源对象为所述出接口；依据所述组播业务的接入端口以及所述L3VPN与二层虚拟专用网L2VPN的业务关联关系获取所述L2VPN的伪线，设置所述宿对象为所述伪线。
  16. 如权利要求15所述的装置，其中，所述建立模块包括：
    获取子模块，被配置为获取所述源对象的检测会话，根据所述检测会话生成源跟踪检测组；
    绑定子模块，被配置为将所述源对象加入到所述源跟踪检测组，并将所述宿对象与该源跟踪检测组进行绑定，生成对应的绑定关系；
    判断子模块，被配置为判断所述源对象的隧道以及所述宿对象的隧道和伪线是否存在多协议标签交换传送应用操作、管理和维护MPLS-TP-OAM的配置；
    建立子模块，被配置为在存在所述配置的情况下，依据所述绑定关系建立所述源对象与所述宿对象之间的所述告警映射关系。
  17. 如权利要求16所述的装置，其中，所述获取子模块被配置为：在所述 节点类型为所述三层核心落地节点时，依据所述入接口设置三层以太网接口或者三层聚合端口；依据所述三层以太接口或者所述三层聚合端口获取所述源对象的检测会话，其中，所述检测会话为接口类型的检测会话；
    在所述节点类型为所述桥接节点时，依据所述出接口获取所述网元的隧道信息；依据所述隧道信息获取所述源对象的检测会话，其中，所述检测会话为组播隧道类型的检测会话。
  18. 如权利要求16所述的装置，其中，所述判断子模块被配置为：
    在所述节点类型为所述三层核心落地节点时，判断所述宿对象的隧道是否存在所述MPLS-TP-OAM的配置；
    在所述节点类型为所述桥接节点时，判断所述源对象的隧道与所述宿对象的伪线是否存在所述MPLS-TP-OAM的配置。
  19. 如权利要求16-18任一所述的装置，还包括：
    获取模块，被配置为当所述节点类型为所述三层核心落地节点时，获取所述宿对象对应的所述隧道的配置信息；
    当所述节点类型为所述桥接节点时，获取所述源对象对应的所述隧道的配置信息；依据所述宿对象，获取所述伪线的配置信息。
  20. 如权利要求16-18任一所述的装置，还包括：
    使能模块，被配置为在所述源对象的所述检测会话失效的情况下，将所述宿对象的停止发送连续性和连通性检测报文设置为使能，依据所述告警映射关系传递故障消息。
  21. 如权利要求13-18任一所述的装置，其中，所述装置设置于网管中。
  22. 一种业务告警处理系统，包括网管以及设备：
    所述网管，被配置为设置网元上所配置的三层虚拟专用网L3VPN的组播业务的源对象与宿对象，其中，所述网元跨接于第一网络与所述L3VPN网络，所述源对象与所述宿对象分别连接所述第一网络与所述L3VPN网络；建立所述源对象与所述宿对象之间的告警映射关系；将所述告警映射关系发送给所述网元对应的设备。
    所述设备，被配置为接收所述网管发送的所述告警映射关系，并在所述源对象与所述宿对象之间建立所述告警映射。
  23. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-11中任一项的方法。
PCT/CN2017/107154 2016-10-27 2017-10-20 一种业务告警处理方法、装置及系统 WO2018077124A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610957783.1A CN107995008B (zh) 2016-10-27 2016-10-27 一种业务告警处理方法、装置及系统
CN201610957783.1 2016-10-27

Publications (1)

Publication Number Publication Date
WO2018077124A1 true WO2018077124A1 (zh) 2018-05-03

Family

ID=62024336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107154 WO2018077124A1 (zh) 2016-10-27 2017-10-20 一种业务告警处理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN107995008B (zh)
WO (1) WO2018077124A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887108A (zh) * 2019-11-29 2021-06-01 中兴通讯股份有限公司 故障定位方法、装置、设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111124840B (zh) * 2019-12-02 2022-02-08 北京天元创新科技有限公司 业务运维中告警的预测方法、装置与电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102571492A (zh) * 2012-01-06 2012-07-11 华为技术有限公司 检测路由设备故障的方法和装置
CN102820990A (zh) * 2012-02-29 2012-12-12 中兴通讯股份有限公司 业务保护的切换方法及装置
US20130290791A1 (en) * 2012-04-27 2013-10-31 General Instrument Corporation Mapping a Network Fault
CN104468237A (zh) * 2014-12-25 2015-03-25 瑞斯康达科技发展股份有限公司 一种sdh和ptn网络告警联动的方法及应用该方法的系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100397826C (zh) * 2004-09-30 2008-06-25 华为技术有限公司 多协议标签交换系统中的保护倒换方法
CN1327673C (zh) * 2005-01-29 2007-07-18 华为技术有限公司 一种多协议标签交换网络的数据传输方法及系统
US9118502B2 (en) * 2009-06-16 2015-08-25 Alcatel Lucent Auto VPN troubleshooting
CN101789879B (zh) * 2009-12-30 2013-01-16 中兴通讯股份有限公司 一种关联链路的动态维护方法及装置
CN102035681B (zh) * 2010-12-17 2015-07-22 中兴通讯股份有限公司 虚拟专用网络的链路保护方法和系统
CN102611618B (zh) * 2012-02-23 2015-06-03 中兴通讯股份有限公司 路由保护切换方法及装置
CN105871613A (zh) * 2016-03-31 2016-08-17 国网山西省电力公司信息通信分公司 一种e1业务保护方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102571492A (zh) * 2012-01-06 2012-07-11 华为技术有限公司 检测路由设备故障的方法和装置
CN102820990A (zh) * 2012-02-29 2012-12-12 中兴通讯股份有限公司 业务保护的切换方法及装置
US20130290791A1 (en) * 2012-04-27 2013-10-31 General Instrument Corporation Mapping a Network Fault
CN104468237A (zh) * 2014-12-25 2015-03-25 瑞斯康达科技发展股份有限公司 一种sdh和ptn网络告警联动的方法及应用该方法的系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887108A (zh) * 2019-11-29 2021-06-01 中兴通讯股份有限公司 故障定位方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107995008A (zh) 2018-05-04
CN107995008B (zh) 2021-07-06

Similar Documents

Publication Publication Date Title
US11323307B2 (en) Method and system of a dynamic high-availability mode based on current wide area network connectivity
KR101706439B1 (ko) 리던던트 네트워크 접속
US8982710B2 (en) Ethernet operation and maintenance (OAM) with flexible forwarding
EP2996287B1 (en) Method for notifying information of pe device and pe device
CN101924654B (zh) 一种基于点到多点业务的路径切换方法及系统
WO2020186803A1 (zh) 一种故障保护方法、节点及存储介质
CN104270309A (zh) 一种ip ran设备下实现多跳bfd的方法
CN103200100A (zh) 一种报文转发方法和设备
CN102868569A (zh) 三层虚拟专用网的性能检测方法、节点和系统
WO2016124117A1 (zh) 一种sdn中的链路保护方法、交换设备及网络控制器
US9716639B2 (en) Protection switching method and system
US8670299B1 (en) Enhanced service status detection and fault isolation within layer two networks
WO2018077124A1 (zh) 一种业务告警处理方法、装置及系统
WO2015154423A1 (zh) 跨域业务处理方法、装置及系统
CN103200107B (zh) 一种报文的传输方法和设备
EP2858302A1 (en) Connectivity check method of service stream link, related apparatus and system
CN110661643B (zh) 用于网络管理的方法、网络设备和介质
WO2012079405A2 (zh) 链路的跟踪处理方法及系统
WO2011011934A1 (zh) 一种以太网隧道分段保护方法和装置
CN104219073A (zh) Spbm网络中的报文转发方法及装置
US20160065450A1 (en) Network connectivity
EP3264693B1 (en) Protection method and system for multi-domain network, and node
WO2021098806A1 (zh) 报文传输路径的切换方法、设备和系统
WO2015180277A1 (zh) Pw双归保护倒换方法及系统
WO2018205728A1 (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: 17866339

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17866339

Country of ref document: EP

Kind code of ref document: A1