CN115278743A - SPN connection fault detection method, system and device for 5G transmission equipment - Google Patents
SPN connection fault detection method, system and device for 5G transmission equipment Download PDFInfo
- Publication number
- CN115278743A CN115278743A CN202210892888.9A CN202210892888A CN115278743A CN 115278743 A CN115278743 A CN 115278743A CN 202210892888 A CN202210892888 A CN 202210892888A CN 115278743 A CN115278743 A CN 115278743A
- Authority
- CN
- China
- Prior art keywords
- checking
- spn
- equipment
- configuration
- monitoring
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Abstract
The invention relates to the technical field of 5G network transmission connection fault detection, in particular to a method, a system and a device for detecting SPN connection fault of 5G transmission equipment, wherein the method comprises the following steps: checking the hardware version and SN number of the device with problems and correspondingly modifying according to the checking result; checking the electronic tag burning of the equipment with the problem and correspondingly modifying according to the checking result; checking the network configuration, router configuration, network management configuration and server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result; checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent with the IP set by the monitoring port and correspondingly modifying according to the checking result; checking whether IP of UNI port of client trace UPE node at core network side can ping and making corresponding modification according to checking result; and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to the checking result. The invention can quickly find the problems, solve the problems and improve the working efficiency.
Description
Technical Field
The invention relates to the technical field of detection of transmission connection faults of 5G networks, in particular to a method, a system and a device for detecting SPN (shortest Path network) connection faults of 5G transmission equipment.
Background
With the large-scale construction of transmission 4G and 5G networks, the trend of development of lower delay and higher bandwidth required in service quality is a greater challenge for transmission networks, and particularly under the condition of ultrahigh network flow, congestion affecting the networks is easily generated. When Network traffic occupies a high-bandwidth full-load operation of a transmission SPN (Slicing Packet Network) Network, network congestion is a common fault phenomenon of transmission operation and maintenance, once the SPN Network congestion occurs, network paralysis can be caused, the working efficiency is influenced, and economic loss of a company is caused.
In view of this, how to overcome the technical problems existing in the prior art is a problem to be solved in the technical field.
Disclosure of Invention
One of the objectives of the present invention is to overcome the technical problems in the prior art, and provide a method, a system, and an apparatus for detecting an SPN connection fault of a 5G transmission device, so as to improve the accuracy of detecting the SPN device network connection fault and improve the working efficiency of workers for a sudden network connection fault.
The invention is realized in the following way:
in a first aspect, the present invention provides a method for detecting an SPN connection failure of a 5G transmission device, including:
checking the hardware version and SN number of the device with problems and correspondingly modifying according to the checking result;
checking the electronic tag burning of the equipment with problems and correspondingly modifying according to the checking result;
checking the network configuration, router configuration, network management configuration and server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result;
checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent with the IP set by the monitoring port and correspondingly modifying according to the checking result;
checking whether IP of UNI port of client trace UPE node at core network side can ping and making corresponding modification according to checking result;
and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to the checking result.
Further, the checking the hardware version and the SN number of the device having a problem and correspondingly modifying according to the checking result specifically includes:
checking the single disk information of the equipment in a network management command line, checking the hardware version number of the bottom layer through the diameter-a, checking whether the version number is consistent with other equipment, and replacing the version number with the same hardware version number if the version number is inconsistent;
logging in two equipment addresses, checking a local SN number, logging in an operating system through the ostelnet, checking whether the electronic tags are consistent or not, and modifying and distinguishing the electronic tags according to the field tags if the electronic tags are consistent.
Further, the burning of the electronic tag of the device with the problem and the corresponding modification according to the checking result specifically include:
checking the arp of the two devices, checking whether the mac addresses are consistent, if so, checking whether the SN numbers are in conflict, if not, logging in an operating system to check the factory mac addresses of the two devices, and if so, modifying the mac addresses of the devices according to the labels above the devices.
Further, the checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the device with the problem and correspondingly modifying according to the checking result specifically comprises:
if the SPN equipment can normally ping the server, but a certain service is abnormal and a certain port monitored by the server is normally connected without abnormality, closing a server firewall or adding the port into a white list in an access rule;
if the network management port is checked, the UPE is found to have no optional port, but the port is checked in the network element manager, and then the network management server service is restarted;
if the corresponding configuration of the corresponding network management is checked, and no problem is found in the configuration, the routing table of the original node is checked, whether the routing exists among the routing tables is checked, and if not, the router setting is reconfigured.
Further, when the corresponding configuration of the corresponding network manager is checked, if a configuration problem is found, the configuration is modified to be the correct configuration.
Further, the checking whether the monitoring IPs of the SPN device network management server and the client are consistent with the IP set by the monitoring port and correspondingly modifying according to the checking result specifically includes:
firstly, logging in an SPN network management server, and if the monitoring IP of the SPN equipment network management server and the monitoring IP of the client and the IP set by the monitoring port are not consistent, resetting the monitoring IP and the monitoring IP to be consistent; then logging in the network management of the client, selecting parameter setting in a system interface, finding out a Telnet/SSH proxy server, filling the content in the proxy into the setting in a consistent manner, and restarting the network management service to take effect.
Further, the checking whether the IP of the UNI port of the client trace UPE node on the core network side can ping and correspondingly modifying according to the checking result specifically includes:
if the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected but the route cannot be routed to the base station, the IP of the UNI port on the UPE can be ping-connected to the core network address, whether the base station is configured with a designated route or not is checked, and the base station is checked to be a default route as a result.
Further, the checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE and correspondingly modifying according to the checking result specifically includes:
and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the customer UPE, and modifying the service and the management gateway address of the base station side when the gateway IP configured by the base station is different from the UNI gateway IP of the customer UPE so that the wireless OMC network manager can discover the SN of the base station.
In a second aspect, the present invention provides a system for detecting a SPN connection failure of a 5G transmission device, which is used to implement the method for detecting a SPN connection failure of a 5G transmission device according to the first aspect, and the system includes a hardware version and SN number detection module, an electronic tag burning detection module, a network and network management detection module, a monitoring IP and monitoring port setting IP detection module, a UNI port IP detection module, and a UNI gateway IP detection module, where:
the hardware version and SN number detection module is used for detecting the hardware version and SN number of the device with problems and correspondingly modifying according to the detection result;
the electronic tag burning detection module is used for checking electronic tag burning of the equipment with problems and modifying the electronic tag burning according to the checking result;
the network and network management detection module is used for checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result;
the monitoring IP and monitoring port setting IP detection module is used for checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent or not and carrying out corresponding modification according to the checking result;
the UNI port IP detection module is used for checking whether the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected or not and correspondingly modifying according to the checking result;
and the UNI gateway IP detection module is used for checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to a check result.
In a third aspect, the present invention provides a device for detecting an SPN connection failure of 5G transmission equipment, where the device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being arranged by the processor to perform the method of detection of a connection failure of a 5G transport device, SPN, as described in the first aspect.
In conclusion, the beneficial effects of the invention are as follows: through the previous steps of the invention, the general network connection problem can be rapidly solved, the working efficiency is improved, the economic loss caused by the network connection fault can be saved in time, and the connection fault caused by the hardware equipment fault can be rapidly solved; through the subsequent steps of the invention, the problem of network connection failure caused by the address gateway can be effectively solved, the problem can be quickly found and solved, the working efficiency is improved, and the method has strong effectiveness and feasibility.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a method for detecting an SPN connection fault of 5G transmission equipment according to embodiment 1 of the present invention;
FIG. 2 is an expanded flowchart of step 100 provided in embodiment 1 of the present invention;
fig. 3 is an expanded flowchart of step 200 provided in embodiment 1 of the present invention;
FIG. 4 is an expanded flowchart of step 300 provided in embodiment 1 of the present invention;
FIG. 5 is an expanded flowchart of step 400 provided in embodiment 1 of the present invention;
FIG. 6 is an expanded flowchart of step 500 provided in embodiment 2 of the present invention;
fig. 7 is an expanded flowchart of step 600 provided in embodiment 2 of the present invention;
fig. 8 is a block diagram of a system for detecting an SPN connection failure of 5G transmission equipment according to embodiment 2 of the present invention;
fig. 9 is a schematic structural diagram of a device for detecting an SPN connection failure of 5G transmission equipment according to embodiment 3 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
The present invention is an architecture of a system with specific functions, and therefore, in the specific embodiment, the functional logic relationship of each structural module is mainly described, and the specific software and hardware implementation is not limited.
In addition, the technical features related to the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other, and the order of the steps may be changed if they are logical and do not conflict with each other.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1:
as shown in fig. 1, embodiment 1 of the present invention provides a method for detecting an SPN connection failure of a 5G transmission device, where the method includes the following steps.
Step 100: the hardware version, SN Number (Serial Number) of the device in question are checked and modified accordingly according to the checking result.
Step 200: and checking the electronic tag burning of the equipment with the problems and correspondingly modifying according to the checking result.
Step 300: and checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result.
Step 400: and checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent with the IP set by the monitoring port and correspondingly modifying according to the checking result.
Step 500: checking whether the IP of a UNI port (user network interface) of a client trace UPE (user plane entry, user port function) node on the core network side can be ping-connected or not and correspondingly modifying according to the checking result.
Step 600: and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to the checking result.
In the above steps, steps 100-400 are independent detection means, and steps 500-600 have support. For step 500, if the IP of the UNI port of the client trace UPE node on the core network side can be ping-passed but the route cannot be routed to the base station, checking whether the base station is configured with a designated route or not at the address of the core network that the IP of the UNI port on the UPE can be ping-passed, and checking that the base station is the default route to the transmission network. The default route has no influence on the method, and the gateway and the IP address on both sides are continuously checked to be consistent. If the route is the designated route, checking whether the configured designated route is the routing address required by the core network, or restoring the default route, and retesting whether ping access is available, for example, if the default route from the base station to the transmission network is the system, the next step of checking whether the network management and the address at the two ends are consistent, if not, modifying the gateway and the IP address at the two ends to be consistent, and retesting whether ping access is available, so that the problem can be solved. For step 600, after the default route from the base station to the transmission network is obtained in step 500, checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the customer UPE, and modifying the service and the management gateway address of the base station side when the gateway IP configured by the base station is different from the UNI gateway IP of the customer UPE, so that the wireless OMC network manager can discover the SN of the base station. That is, step 600 is based on step 500.
As shown in fig. 2, in a specific implementation of the preferred embodiment, step 100 (checking the hardware version of the device with problem, SN number and making corresponding modifications according to the checking result) can be specifically extended to the following steps.
Step 101: and checking the single disk information of the equipment in a network management command line, checking the hardware version number of the bottom layer through the diameter-a, checking whether the version number is consistent with other equipment, and replacing the version number with the same hardware version number if the version number is inconsistent. In this step, if the check result shows that the hardware version number of the device with the failure matches that of another device, it indicates that the failure is not due to the hardware version number of the device, and therefore the hardware version does not need to be replaced.
Step 102: logging in two equipment addresses, checking a local SN number, logging in an operating system through the ostelnet, checking whether the electronic tags are consistent or not, and modifying and distinguishing the electronic tags according to the field tags if the electronic tags are consistent. In this step, if the check result shows that the SN numbers of the electronic tags of the two devices are not consistent, it indicates that the occurrence of the fault is not due to the SN number of the device, and therefore, the electronic tags of the SN numbers do not need to be modified.
As shown in fig. 3, in a specific implementation manner of the preferred embodiment, step 200 (checking the burning of the electronic tag of the device with the problem and making corresponding modification according to the checking result) can be specifically extended to the following steps.
Step 201: check whether the mac addresses are consistent by looking at the arp (Address Resolution Protocol) of the two devices.
Step 202: and if the SN numbers are consistent, checking whether the SN numbers conflict or not, and if no conflict is found, logging in an operating system to check the factory mac addresses of the two devices. In the step, if inconsistency is found when mac addresses are checked, SN numbers are also checked, and the two links are not carried out after one is missed. When checking SN number, if finding conflict, it proves mac address is consistent, and it needs to modify mac address and SN number.
Step 203: and if the conflict is caused by the consistency of the mac addresses burnt from the factory, modifying the mac address of the equipment according to the label above the equipment. In this step, if the result of the check shows that the mac addresses burned from the factory are not consistent, there is no conflict, which indicates that the problem is not present here, and the mac addresses do not need to be modified.
As shown in fig. 4, in a specific implementation manner of the preferred embodiment, step 300 (checking the network configuration, router configuration, network management configuration, and server firewall configuration of the device with problem and making corresponding modifications according to the checking result) is specifically extended to the following steps.
Step 301: if the SPN device can normally ping the server, but a certain service is abnormal and a certain port monitored by the server is normally connected without abnormality, the firewall of the server is closed or the port is added into a white list in the access rule. In this step, if the SPN device cannot ping the server, it checks whether the IP address configuration is correct.
Step 302: if the network management port is checked, the UPE is found to have no optional port, but the network management server service is restarted if the port is checked in the network element manager.
Step 303: if the corresponding configuration of the corresponding network management is checked, and no problem is found in the configuration, the routing table of the original node is checked, whether the routing exists among the routing tables is checked, and if not, the router setting is reconfigured. When checking the corresponding configuration of the corresponding network manager, if finding the configuration problem, modifying the configuration to correct configuration
As shown in fig. 5, in a specific implementation manner of the preferred embodiment, the step 400 (checking whether the monitoring IPs and the monitoring IPs set on the monitoring ports of the SPN device network management server and the client are consistent and modifying the monitoring IPs accordingly according to the checking result) can be specifically extended to the following steps.
Step 401: firstly, logging in an SPN network management server, and if the monitoring IP of the SPN equipment network management server and the monitoring IP of the client and the IP set by the monitoring port are not consistent, resetting the monitoring IP and the monitoring IP to be consistent. In this step, if the two are found to be consistent by checking results, the problem is not solved here, and no modification is required.
Step 402: then logging in the network management of the client, selecting parameter setting in a system interface, finding out a Telnet/SSH proxy server, filling the content in the proxy into the setting in a consistent manner, and restarting the network management service to take effect. This step is for the case where the previous step was modified.
As shown in fig. 6, in a specific implementation manner of the preferred embodiment, the step 500 (checking whether the IP of the UNI port of the core network side client trace UPE node can ping and modifying accordingly according to the checking result) is specifically extended as follows.
Step 501: if the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected but the route can not be routed to the base station, the IP of the UNI port of the UPE can be ping-connected to the core network address, and whether the base station is configured with the appointed route or not is checked. In the step, if Ping fails to prove that the IP address is not correct, the IP address is reset.
Step 502: and if the specified route is not configured, setting the default route from the base station to the transmission network. In this step, if the base station configures a specific designated route, it may also check whether the configured designated route is a routing address required by the core network, and if not, set the base station to the transmission network as a default route.
As shown in fig. 7, in a specific implementation manner of the preferred embodiment, the step 600 (checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE and modifying accordingly according to the checking result) can be specifically extended as follows.
Step 601: and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE.
Step 602: and when the gateway IP configured by the base station is different from the UNI gateway IP of the client UPE, modifying the service and the management gateway address of the base station side so that the wireless OMC network manager can discover the SN of the base station. In this step, if the checking result shows that the gateway IP configured by the base station is the same as the UNI gateway IP of the client UPE, the explanation is not given here and no modification is required.
In summary, the foregoing steps 100 to 300 of the embodiment of the present invention can rapidly solve the general network connection problem, improve the working efficiency, save the economic loss caused by the network connection failure in time, and rapidly solve the connection failure caused by the hardware device failure; through the subsequent steps 400-600 of the invention, the problem of network connection failure caused by the address gateway can be effectively solved, the problem can be quickly found and solved, the working efficiency is improved, and the invention has strong effectiveness and feasibility.
Example 2:
embodiment 2 of the present invention provides a system for detecting a SPN connection fault of a 5G transmission device, so as to implement the method for detecting a SPN connection fault of a 5G transmission device provided in embodiment 1, as shown in fig. 8, the system of this embodiment includes a hardware version and SN number detection module, an electronic tag burning detection module, a network and network management detection module, a monitoring IP and monitoring port setting IP detection module, a UNI port IP detection module, and a UNI gateway IP detection module, where: the hardware version and SN number detection module is used for detecting the hardware version and SN number of the device with problems and correspondingly modifying according to the detection result; the electronic tag burning detection module is used for checking electronic tag burning of the equipment with problems and modifying the electronic tag burning according to the checking result; the network and network management detection module is used for checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result; the monitoring IP and monitoring port setting IP detection module is used for checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent or not and carrying out corresponding modification according to the checking result; the UNI port IP detection module is used for checking whether the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected or not and correspondingly modifying according to the checking result; and the UNI gateway IP detection module is used for checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to a check result.
Specifically, when the hardware version and SN number detection module detects, the single-disk information of the device is checked in a network management command line, the bottom layer checks the hardware version number through the name-a, whether the hardware version number is consistent with other devices or not is checked, and if the hardware version number is inconsistent, the hardware version number is replaced by the same hardware version number. And then logging in two equipment addresses, checking the local SN number, logging in the electronic tag through an ostelnet operating system, checking whether the electronic tag is consistent, and modifying and distinguishing the electronic tag according to the field tag if the electronic tag is consistent. In this module, if the hardware version number of the device having a problem is found to match with that of another device as a result of the check, it is described that the occurrence of the failure is not due to the hardware version number of the device, and therefore, the hardware version does not need to be replaced. In this module, if the check result shows that the SN numbers of the electronic tags of the two devices are not consistent, it indicates that the occurrence of the fault is not due to the SN number of the device, and therefore, the electronic tags of the SN numbers do not need to be modified.
When the electronic tag burning detection module detects, the arp of the two devices is checked at first, and whether the mac addresses are consistent or not is checked. And if the SN numbers are consistent, checking whether the SN numbers conflict or not, and if no conflict is found, logging in an operating system to check the factory mac addresses of the two devices. And if the conflict is caused by the consistency of the mac addresses burnt from the factory, modifying the mac address of the equipment according to the label above the equipment. In this module, if the result of the check shows that the mac addresses burned from the factory are inconsistent, there is no conflict, which indicates that the problem is not present, and the mac addresses do not need to be modified.
When the network and network management detection module detects, if the SPN device can normally ping the server, but a certain service is abnormal and a certain port monitored by the server is normally connected without abnormality, the server firewall is closed or the port is added to the white list in the access rule. If the network management port is checked, the UPE is found to have no optional port, but the port is checked in the network element manager, and then the network management server service is restarted. If the corresponding configuration of the corresponding network management is checked, and no problem is found in the configuration, the routing table of the original node is checked, whether the routing exists among the routing tables is checked, and if not, the router setting is reconfigured.
When the monitoring IP and monitoring port setting IP detection module detects, firstly, the SPN network management server is logged in, and if the monitoring IP and monitoring port setting IP of the SPN equipment network management server and the client are not consistent, the monitoring IP and monitoring port setting IP are reset to be consistent. Then logging in the network management of the client, selecting parameter setting in a system interface, finding out a Telnet/SSH proxy server, filling the content in the proxy into the setting in a consistent manner, and restarting the network management service to take effect. In this module, if the two are found to be consistent by checking results, the explanation problem is not presented here, and no modification is required.
When the UNI port IP detection module detects that the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected but the route cannot be routed to the base station, the UNI port IP detection module detects whether the base station is not provided with the designated route or not by checking the core network address which can be ping-connected with the IP of the UNI port on the UPE. If the designated route is not configured, setting the route from the base station to the transmission network as a default route.
And when detecting, the UNI gateway IP detection module checks whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE. And when the gateway IP configured by the base station is different from the UNI gateway IP of the client UPE, modifying the service and the management gateway address of the base station side so that the wireless OMC network manager can discover the SN of the base station. In this module, if the checking result shows that the gateway IP configured by the base station is the same as the UNI gateway IP of the client UPE, the explanation is not given here and no modification is required.
In summary, the first modules of the embodiment of the present invention can rapidly solve the general network connection problem, improve the working efficiency, save the economic loss caused by the network connection failure in time, and rapidly solve the connection failure caused by the hardware device failure; the latter modules of the embodiment of the invention can effectively solve the problem of network connection failure caused by the address gateway, can quickly find the problem, solve the problem, improve the working efficiency and have extremely strong effectiveness and feasibility.
Example 3:
on the basis of the method for detecting the SPN connection failure of the 5G transmission device provided in embodiment 1, the present invention further provides a device for detecting the SPN connection failure of the 5G transmission device, which is capable of implementing the method described above, and as shown in fig. 9, the device is a schematic diagram of an architecture of the device according to the embodiment of the present invention. The apparatus for detecting a connection failure of the 5G transmission device SPN of the present embodiment includes one or more processors 21 and a memory 22. In fig. 9, one processor 21 is taken as an example.
The processor 21 and the memory 22 may be connected by a bus or other means, and fig. 9 illustrates the connection by a bus as an example.
The memory 22, which is a nonvolatile computer-readable storage medium, may be used to store nonvolatile software programs, nonvolatile computer-executable programs, and modules, such as the 5G transmission device SPN connection failure detection method in embodiment 1. The processor 21 executes various functional applications and data processing of the 5G transmission device SPN connection failure detection apparatus by running the nonvolatile software program, instructions, and modules stored in the memory 22, that is, implements the 5G transmission device SPN connection failure detection method of embodiment 1.
The memory 22 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 22 may optionally include memory located remotely from the processor 21, and these remote memories may be connected to the processor 21 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The program instructions/modules are stored in the memory 22, and when executed by the one or more processors 21, perform the 5G transmission device SPN connection failure detection method in embodiment 1 described above, for example, perform the respective steps shown in fig. 1 to 7 described above.
Those of ordinary skill in the art will appreciate that all or part of the steps of the various methods of the embodiments may be performed by associated hardware as instructed by a program, which may be stored on a computer-readable storage medium, which may include: a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A method for detecting SPN connection fault of 5G transmission equipment is characterized by comprising the following steps:
checking the hardware version and SN number of the device with problems and correspondingly modifying according to the checking result;
checking the electronic tag burning of the equipment with the problem and correspondingly modifying according to the checking result;
checking the network configuration, router configuration, network management configuration and server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result;
checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent with the IP set by the monitoring port and correspondingly modifying according to the checking result;
checking whether IP of UNI port of client trace UPE node at core network side can ping and making corresponding modification according to checking result;
and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to the checking result.
2. The method for detecting SPN connection failure of 5G transmission equipment according to claim 1, wherein the checking the hardware version and SN number of the equipment with problems and making corresponding modification according to the checking result specifically comprises:
checking the single disk information of the equipment in a network management command line, checking the hardware version number of the bottom layer through the diameter-a, checking whether the version number is consistent with other equipment, and replacing the version number with the same hardware version number if the version number is inconsistent;
logging in two equipment addresses, checking local SN numbers, logging in an operating system through ostelnet, checking whether electronic tags are consistent or not, and modifying and distinguishing the electronic tags according to field tags if the electronic tags are consistent.
3. The method for detecting SPN connection failure of 5G transmission equipment according to claim 1, wherein the step of checking the electronic tag burn of the equipment with problems and correspondingly modifying the electronic tag burn according to the checking result specifically comprises the following steps:
checking the arp of the two devices, checking whether the mac addresses are consistent, if so, checking whether the SN numbers are in conflict, if not, logging in an operating system to check the factory mac addresses of the two devices, and if so, modifying the mac addresses of the devices according to the labels above the devices.
4. The SPN connection fault detection method of the 5G transmission equipment according to claim 1, wherein the step of checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result specifically comprises the steps of:
if the SPN equipment can normally ping the server, but a certain service is abnormal and a certain port monitored by the server is normally connected without abnormality, closing a server firewall or adding the port into a white list in an access rule;
if the network management port is checked, the UPE is found to have no optional port, but the port is checked in the network element manager, and then the network management server service is restarted;
if the corresponding configuration of the corresponding network management is checked, and no problem is found in the configuration, the routing table of the original node is checked, whether the routing exists among the routing tables is checked, and if not, the router setting is reconfigured.
5. The SPN connection failure detection method for 5G transmission equipment according to claim 1, wherein when checking the corresponding configuration of the corresponding network manager, if a configuration problem is found, the configuration is modified to be a correct configuration.
6. The method for detecting SPN connection failure of 5G transmission equipment according to claim 1, wherein the checking whether the monitoring IPs of the SPN equipment network management server and the client are consistent with the IP set by the monitoring port and making corresponding modification according to the checking result specifically comprises:
firstly, logging in an SPN network management server, and if the monitoring IP of the SPN equipment network management server and the monitoring IP of the client and the IP set by the monitoring port are not consistent, resetting the monitoring IP and the monitoring IP to be consistent; then logging in the network management of the client, selecting parameter setting in a system interface, finding out a Telnet/SSH proxy server, filling the content in the proxy into the setting in a consistent manner, and restarting the network management service to take effect.
7. The method for detecting SPN connection failure of 5G transmission equipment according to claim 1, wherein the checking whether the IP of the UNI port of the client trace UPE node on the core network side can ping and making corresponding modification according to the checking result specifically comprises:
if the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected but the route cannot be routed to the base station, checking whether the base station is configured with the appointed route or not at the address of the core network which can be ping-connected with the IP of the UNI port on the UPE, and if the appointed route is not configured, setting the route from the base station to the transmission network as the default route.
8. The method for detecting SPN connection failure of 5G transmission equipment according to claim 1, wherein the checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE and the corresponding modification according to the checking result specifically comprises:
and checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the customer UPE, and modifying the service and the management gateway address of the base station side when the gateway IP configured by the base station is different from the UNI gateway IP of the customer UPE so that the wireless OMC network manager can discover the SN of the base station.
9. A SPN connection failure detection system for 5G transmission devices, for implementing the SPN connection failure detection method for 5G transmission devices according to any one of claims 1 to 8, comprising a hardware version and SN number detection module, an electronic tag burning detection module, a network and network management detection module, a monitoring IP and monitoring port setting IP detection module, a UNI port IP detection module, and a UNI gateway IP detection module, wherein:
the hardware version and SN number detection module is used for detecting the hardware version and SN number of the device with problems and correspondingly modifying according to the detection result;
the electronic tag burning detection module is used for checking electronic tag burning of the equipment with problems and modifying the electronic tag burning according to the checking result;
the network and network management detection module is used for checking the network configuration, the router configuration, the network management configuration and the server firewall configuration of the equipment with problems and correspondingly modifying according to the checking result;
the monitoring IP and monitoring port setting IP detection module is used for checking whether the monitoring IP of the SPN equipment network management server and the monitoring IP of the client are consistent or not and carrying out corresponding modification according to the checking result;
the UNI port IP detection module is used for checking whether the IP of the UNI port of the client trace UPE node on the core network side can be ping-connected or not and correspondingly modifying according to the checking result;
and the UNI gateway IP detection module is used for checking whether the gateway IP configured by the base station is consistent with the UNI gateway IP of the client UPE or not and correspondingly modifying according to a check result.
10. The utility model provides a 5G transmission equipment SPN connection fault detection device which characterized in that, the device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being arranged by the processor to perform the method of detection of a connection failure of a 5G transport device, SPN, according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210892888.9A CN115278743A (en) | 2022-07-27 | 2022-07-27 | SPN connection fault detection method, system and device for 5G transmission equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210892888.9A CN115278743A (en) | 2022-07-27 | 2022-07-27 | SPN connection fault detection method, system and device for 5G transmission equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115278743A true CN115278743A (en) | 2022-11-01 |
Family
ID=83771539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210892888.9A Pending CN115278743A (en) | 2022-07-27 | 2022-07-27 | SPN connection fault detection method, system and device for 5G transmission equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115278743A (en) |
-
2022
- 2022-07-27 CN CN202210892888.9A patent/CN115278743A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111886833B (en) | Method for redirecting control channel messages and device for implementing the method | |
| US11729059B2 (en) | Dynamic service device integration | |
| JP7108674B2 (en) | Failure root cause determination method and device, and computer storage medium | |
| JP5846221B2 (en) | Network system and topology management method | |
| Sidki et al. | Fault tolerant mechanisms for SDN controllers | |
| Azzouni et al. | sOFTDP: Secure and efficient topology discovery protocol for SDN | |
| US10778505B2 (en) | System and method of evaluating network asserts | |
| JP7416919B2 (en) | Data processing methods and devices and computer storage media | |
| US11153185B2 (en) | Network device snapshots | |
| CN105791126B (en) | Ternary Content Addressable Memory (TCAM) table look-up method and device | |
| WO2015184739A1 (en) | Fault detection method and device | |
| Azzouni et al. | sOFTDP: Secure and efficient OpenFlow topology discovery protocol | |
| Canini et al. | Renaissance: A self-stabilizing distributed SDN control plane | |
| CN112291116A (en) | Link fault detection method and device and network equipment | |
| Lopez-Pajares et al. | Amaru: Plug&play resilient in-band control for SDN | |
| CN110380966B (en) | Method for discovering forwarding path and related equipment thereof | |
| CN116566752B (en) | Safety drainage system, cloud host and safety drainage method | |
| US20230254244A1 (en) | Path determining method and apparatus, and computer storage medium | |
| CN115278743A (en) | SPN connection fault detection method, system and device for 5G transmission equipment | |
| CN112637054B (en) | Networking optimization method and device for IP bearing network, computing equipment and storage medium | |
| Cisco | Release Notes for Catalyst 4000 Family Software Release 4.x | |
| Sharma et al. | Enabling fast failure recovery in openflow networks using routeflow | |
| US10904123B2 (en) | Trace routing in virtual networks | |
| Cisco | Release Notes for Catalyst 5000 Family Software Release 4.x | |
| Han et al. | Computer network failure and solution |
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 |