Terminal operation and maintenance management system

Abstract

The invention provides a terminal operation and maintenance management system. Along with rapid development of business of a company, an information network of the company is developed and expanded rapidly, besides an office PC, various terminals such as video monitoring, on-line monitoring, a network attendance machine, a network printer, an IP telephone, access control equipment and the like are explosively increased, and the information network of the company is developed from a traditional computer network to the Internet of Things. Therefore, great difficulty is brought to operation and maintenance management of the network. Because an intranet carries out IP + MAC + port binding, a user needs to fill in an application form during network access and migration, but the user often neglects a network quit application, so that an IP + MAC + port binding table stored by a transportation and housing department is inconsistent with configuration in an actual switch. In the prior art, a user does not submit a network quitting application or a fault of a terminal such as a monitoring device may be out of the network for a long time and cannot be found in time, so that a great difficulty is brought to distribution of IP addresses, and serious waste of the IP addresses is caused. Therefore, according to the terminal operation and maintenance management system provided by the invention, the ARP table of the core switch is scanned regularly, the online and offline states of all terminal devices are monitored in real time, whether the terminal devices are offline or have faults is found in time, and meanwhile, batch IP + MAC + port binding is realized, so that the terminal operation and maintenance efficiency is improved.

Description

Technical Field

[0001] The present invention relates to network operation and maintenance, and in particular to a terminal operation and maintenance management system. Background Art

[0002] With the rapid development of the company's business, the company's information network has also grown rapidly. In addition to office PCs, various terminals such as video surveillance, online monitoring, network attendance machines, network printers, IP phones, access control devices, etc. have grown explosively. The company's information network is developing from traditional computer networks to the Internet of Things, which has brought great difficulties to the operation and maintenance of the network.

[0003] Since the intranet implements IP+MAC+port binding, users need to fill out an application form when joining the network and migrating, and fill out a withdrawal application when leaving the network. However, users often ignore the withdrawal application, which makes it impossible to detect the user's withdrawal behavior, making the IP+MAC+port binding table saved by the operation and residence department inconsistent with the configuration in the actual switch. Over time, the error will accumulate. If the user does not submit a withdrawal application or a terminal failure such as monitoring equipment may be offline for a long time and not discovered in time, it will also bring great difficulties to the allocation of IP addresses. An IP address cannot be taken back after it is allocated, and new devices constantly need new IP addresses, resulting in serious waste of IP addresses.

[0004] At present, there is no unified software tool to manage various types of terminals. Management mainly relies on manual records and operations by operation and maintenance personnel, resulting in problems such as delayed terminal management and waste of IP addresses. Summary of the invention

[0005] In view of this, the main purpose of the present invention is to solve the problems of delayed terminal management and waste of IP addresses.

[0006] In the first aspect, the present invention provides a terminal operation and maintenance management system, characterized in that it includes: an application layer, the application layer is used for human-computer interaction, including a terminal device management module, a switch management module and a switch access module; an access layer, the access layer mainly provides support for services and accesses databases and switches; a resource layer, the resource layer is used for data reading, writing and storage, including databases and all switches in the intranet; the terminal device management module is responsible for maintaining the information of the terminal device, monitoring its network status, and providing log query to track device activities. The switch management module is used to synchronize switch data to the database and manage IP+MAC+port binding data; the switch access module is used to log in to the switch and send relevant commands to access the switch;

[0007] Furthermore, the terminal device management module includes terminal device data management function, terminal monitoring function, and monitoring log management function; the terminal device data management function uses ADO.net components to operate the terminal device table to realize the functions of adding, deleting, modifying and querying terminal device information; the terminal monitoring function uses SSH.net components to log in to the core switch to obtain the ARP table and scan the ARP table regularly, assuming that the currently scanned ARP table is stored in the object array arp_list1, and the last scanned ARP table is stored in the object array arp_list2 (initially empty), and the object array arp_list1 and the object array arp_list2 are monitored on the network and off the network, and the on-line terminal devices and off-line terminal devices are separated; the monitoring log management function uses ADO.net components to query the monitoring log table to realize terminal monitoring log query.

[0008] Furthermore, the steps of performing online monitoring in the terminal monitoring function include:

[0009] S1, read a record from the object array arp_list1 to item;

[0010] S2. If item reads a record, it determines whether item.mac exists in the object array arp_list2; if item does not read a record, the process ends;

[0011] S3. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number of item.mac record corresponding to the terminal device table, original IP = IP of item.mac record corresponding to the terminal device table, new IP = item.id, time = current time, type = online; then update the device record corresponding to item.mac in the terminal device table: last online time = current time IP = item.ip;

[0012] S4. If item.mac exists in the object array arp_list2, then update the corresponding item.mac device record in the terminal device table: the last online time = current time IP = item.ip;

[0013] S5. Execute step S1.

[0014] Furthermore, the steps of performing network disconnection monitoring in the terminal monitoring function include:

[0015] S11, read a record from the object array arp_list2 to item;

[0016] S12, if item reads a record, it determines whether item.mac has a record in the object array arp_list1; if item does not read a record, the process ends;

[0017] S13. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number corresponding to item.mac record in the terminal device table, original IP = item.ip, new IP = null, time = current time, type = exit network; then execute step S11;

[0018] S14. If item.mac exists in the object array arp_list2, execute step S11.

[0019] Further, the switch management module includes a switch data management function, a switch port synchronization function, a port binding function and a binding log management function;

[0020] The switch data management function is implemented using ADO.net components, and the implementation steps include:

[0021] S21, operate the switch table to implement the functions of adding, deleting, modifying and querying switch information, and implement the query of switch ports and port binding information;

[0022] S22, query the switch port table to query the switch port information;

[0023] S23, query the port binding table to realize IP+MAC+port binding information query;

[0024] The switch port synchronization function is implemented using the SSH.net component. Log in to the switch and execute the port query command display interface brief to query the switch port information, and store the query results in the switch port table.

[0025] The port binding function uses an EXCEL table to store the bound switch IP, port, MAC and IP, batch imports and logs in to the switch through the SSH.net component to perform the binding operation;

[0026] The binding log management function uses ADO.net components to query the binding log table to implement terminal monitoring log query.

[0027] Furthermore, the steps of implementing batch binding of the port binding function include:

[0028] S31, read a record from bind_list to item;

[0029] S32, determine whether item has successfully read the record. If no record is read, the process ends; if the record is read, use item.ip to query the switch table to obtain the login user name and login password;

[0030] S33, IP, user name and login password to log in to the switch and query the current switch binding list;

[0031] S34, determine whether the binding record already exists in the current switch binding list. If not, query the port binding table to see whether there is a binding record item1 corresponding to the MAC in other switches; if yes, execute step S31;

[0032] S35, determine whether item1 exists in other switches. If so, use item1.ip to query the switch table to obtain the login user name and login password; if not, execute step S37;

[0033] S36, operating on the switch to release the binding data corresponding to item1, and deleting the binding record of item1 in the port binding table;

[0034] S37, add a binding record corresponding to the item on the switch, add the item binding record in the port binding table, and then execute step S31.

[0035] Furthermore, the switch access module simulates manual login to the switch through the SSH terminal software and inputs switch operation related commands to access or operate the switch;

[0036] The steps to use the SSH.net component to simulate a switch include:

[0037] S41. First, use the switch IP, user name and password to create a ShellStream object to log in to the switch and establish a connection;

[0038] S42, creating a ShellStream object to send a switch command;

[0039] S43. Get the returned result text through the shellStream.Expect method;

[0040] S44, parse the text to obtain the required data.

[0041] Furthermore, the system adopts Visual Studio development tools and is a Windows form application developed in C# language.

[0042] In a second aspect, an electronic device is provided, comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the steps of the method for approving, matching, and issuing innovation vouchers of any embodiment of the present invention.

[0043] In a third aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein when the program instructions are executed by a processor, the processor executes the steps of managing terminal operation and maintenance of any embodiment of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 is a system architecture diagram of the present invention;

[0045] Figure 2 It is the module design diagram of the present invention;

[0046] Figure 3 It is the on-line monitoring flow chart of the present invention;

[0047] Figure 4 This is a flowchart of network delisting monitoring of the present invention;

[0048] Figure 5 This is a flow chart of the IP+MAC+port batch binding of the present invention.

[0049] Figure 6 The switch operation flow chart of the present invention. DETAILED DESCRIPTION

[0050] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It will be understood that the specific embodiments described herein are only used to explain the relevant inventions, rather than to limit the inventions. It should also be noted that, for ease of description, only the parts related to the relevant inventions are shown in the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.

[0051] According to an embodiment of the present invention, a terminal operation and maintenance management system is provided.

[0052] like Figure 1As shown, according to the terminal operation and maintenance management system of the embodiment of the present invention, the system includes: an application layer, the application layer is used for human-computer interaction, including a terminal device management module, a switch management module and a switch access module; an access layer, the access layer mainly provides support for the business and accesses the database and the switch; a resource layer, the resource layer is used for data reading, writing and storage, including the database and all switches in the intranet; the terminal device management module is responsible for maintaining the information of the terminal device, monitoring its network status, and providing log query to track device activities. ; The switch management module is used to synchronize the switch data to the database and manage the IP+MAC+port binding data; the switch access module is used to log in to the switch and send relevant commands to access the switch;

[0053] like Figure 2 As shown, the terminal device management module includes terminal device data management function, terminal monitoring function, and monitoring log management function; the terminal device data management function uses ADO.net components to operate the terminal device table to realize the functions of adding, deleting, modifying and querying terminal device information; the terminal monitoring function uses SSH.net components to log in to the core switch to obtain the ARP table and scan the ARP table regularly, assuming that the currently scanned ARP table is stored in the object array arp_list1, and the last scanned ARP table is stored in the object array arp_list2 (initially empty), and the object array arp_list1 and the object array arp_list2 are monitored on the network and off the network, and the on-line terminal devices and off-line terminal devices are separated; the monitoring log management function uses ADO.net components to query the monitoring log table to realize terminal monitoring log query.

[0054] like Figure 3 As shown, the steps of performing online monitoring in the terminal monitoring function include:

[0055] S1, read a record from the object array arp_list1 to item;

[0056] S2. If item reads a record, it determines whether item.mac exists in the object array arp_list2; if item does not read a record, the process ends;

[0057] S3. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number of item.mac record corresponding to the terminal device table, original IP = IP of item.mac record corresponding to the terminal device table, new IP = item.id, time = current time, type = online; then update the device record corresponding to item.mac in the terminal device table: last online time = current time IP = item.ip;

[0058] S4. If item.mac exists in the object array arp_list2, then update the corresponding item.mac device record in the terminal device table: the last online time = current time IP = item.ip;

[0059] S5. Execute step S1.

[0060] like Figure 4 As shown, the steps of performing network disconnection monitoring in the terminal monitoring function include:

[0061] S11, read a record from the object array arp_list2 to item;

[0062] S12, if item reads a record, it determines whether item.mac has a record in the object array arp_list1; if item does not read a record, the process ends;

[0063] S13. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number corresponding to item.mac record in the terminal device table, original IP = item.ip, new IP = null, time = current time, type = exit network; then execute step S11;

[0064] S14. If item.mac exists in the object array arp_list2, execute step S11.

[0065] like Figure 2 As shown, the switch management module includes a switch data management function, a switch port synchronization function, a port binding function and a binding log management function;

[0066] The switch data management function is implemented using ADO.net components, and the implementation steps include:

[0067] S21, operate the switch table to implement the functions of adding, deleting, modifying and querying switch information, and implement the query of switch ports and port binding information;

[0068] S22, query the switch port table to query the switch port information;

[0069] S23, query the port binding table to realize IP+MAC+port binding information query;

[0070] The switch port synchronization function is implemented using the SSH.net component. Log in to the switch and execute the port query command display interface brief to query the switch port information, and store the query results in the switch port table.

[0071] The port binding function uses an EXCEL table to store the bound switch IP, port, MAC and IP, batch imports and logs in to the switch through the SSH.net component to perform the binding operation;

[0072] The binding log management function uses ADO.net components to query the binding log table to implement terminal monitoring log query.

[0073] like Figure 5 As shown, the steps of implementing batch binding of the port binding function include:

[0074] S31, read a record from bind_list to item;

[0075] S32, determine whether item has successfully read the record. If no record is read, the process ends; if the record is read, use item.ip to query the switch table to obtain the login user name and login password;

[0076] S33, IP, user name and login password to log in to the switch and query the current switch binding list;

[0077] S34, determine whether the binding record already exists in the current switch binding list. If not, query the port binding table to see whether there is a binding record item1 corresponding to the MAC in other switches; if yes, execute step S31;

[0078] S35, determine whether item1 exists in other switches. If so, use item1.ip to query the switch table to obtain the login user name and login password; if not, execute step S37;

[0079] S36, operating on the switch to release the binding data corresponding to item1, and deleting the binding record of item1 in the port binding table;

[0080] S37, add a binding record corresponding to the item on the switch, add the item binding record in the port binding table, and then execute step S31.

[0081] like Figure 6 As shown, the switch access module simulates manual login to the switch through the SSH terminal software and inputs switch operation related commands to access or operate the switch;

[0082] The steps to use the SSH.net component to simulate a switch include:

[0083] S41. First, use the switch IP, user name and password to create a ShellStream object to log in to the switch and establish a connection;

[0084] S42, creating a ShellStream object to send a switch command;

[0085] S43. Get the returned result text through the shellStream.Expect method;

[0086] S44, parse the text to obtain the required data.

[0087] The above are only some embodiments of the present invention. For those skilled in the art, several modifications and improvements can be made without departing from the creative concept of the present invention, which all belong to the protection scope of the present invention.

Claims

1. A terminal operation and maintenance management system, characterized in that: include Application layer, which is used for human-computer interaction and includes a terminal device management module, a switch management module and a switch access module; Access layer, which mainly provides support for business and accesses databases and switches; Resource layer, which is used for data reading, writing and storage, including databases and all switches in the intranet; The terminal device management module is responsible for maintaining the information of the terminal device, monitoring its network status, and providing log query to track device activities. The switch management module is used to synchronize switch data to the database and manage IP+MAC+port binding data; The switch access module is used to log in to the switch and send relevant commands to access the switch.

2. A terminal operation and maintenance management system according to claim 1, characterized in that: The terminal device management module includes terminal device data management function, terminal monitoring function, and monitoring log management function; The terminal device data management function uses ADO.net components to operate the terminal device table to achieve the functions of adding, deleting, modifying and querying terminal device information; The terminal monitoring function uses the SSH.net component to log in to the core switch to obtain the ARP table and scan the ARP table regularly. The currently scanned ARP table is stored in the object array arp_list1, and the last scanned ARP table is stored in the object array arp_list2 (initial empty). The object array arp_list1 and the object array arp_list2 are monitored online and offline, and the online terminal devices and the offline terminal devices are separated. The monitoring log management function uses ADO.net components to query the monitoring log table and implement terminal monitoring log query.

3. A terminal operation and maintenance management system according to claim 2, characterized in that: The steps of performing online monitoring in the terminal monitoring function include: S1, read a record from the object array arp_list1 to item; S2. If item reads a record, it determines whether item.mac exists in the object array arp_list2; if item does not read a record, the process ends; S3. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number of item.mac record corresponding to the terminal device table, original IP = IP of item.mac record corresponding to the terminal device table, new IP = item.id, time = current time, type = online; then update the device record corresponding to item.mac in the terminal device table: last online time = current time IP = item.ip; S4. If item.mac exists in the object array arp_list2, then update the corresponding item.mac device record in the terminal device table: the last online time = current time IP = item.ip; S5. Execute step S1.

4. A terminal operation and maintenance management system according to claim 2, characterized in that: The steps of performing network disconnection monitoring in the terminal monitoring function include: S11, read a record from the object array arp_list2 to item; S12, if item reads a record, it determines whether item.mac has a record in the object array arp_list1; if item does not read a record, the process ends; S13. If item.mac does not exist in the object array arp_list2, add information to the terminal monitoring log: device number = device number corresponding to item.mac record in the terminal device table, original IP = item.ip, new IP = null, time = current time, type = exit network; then execute step S11; S14. If item.mac exists in the object array arp_list2, execute step S11.

5. A terminal operation and maintenance management system according to claim 1, characterized in that: The switch management module includes switch data management function, switch port synchronization function, port binding function and binding log management function; The switch data management function is implemented using ADO.net components, and the implementation steps include: S21, operate the switch table to implement the functions of adding, deleting, modifying and querying switch information, and implement the query of switch ports and port binding information; S22, query the switch port table to query the switch port information; S23, query the port binding table to realize IP+MAC+port binding information query; The switch port synchronization function is implemented using the SSH.net component. Log in to the switch and execute the port query command display interface brief to query the switch port information, and store the query results in the switch port table. The port binding function uses an EXCEL table to store the bound switch IP, port, MAC and IP, batch imports and logs in to the switch through the SSH.net component to perform the binding operation; The binding log management function uses ADO.net components to query the binding log table to implement terminal monitoring log query.

6. A terminal operation and maintenance management system according to claim 5, characterized in that: The steps of implementing batch binding by the port binding function include: S31, read a record from bind_list to item; S32, determine whether item has successfully read the record. If no record is read, the process ends; if the record is read, use item.ip to query the switch table to obtain the login user name and login password; S33, IP, user name and login password to log in to the switch and query the current switch binding list; S34, determine whether the binding record already exists in the current switch binding list. If not, query the port binding table to see whether there is a binding record item1 corresponding to the MAC in other switches; if yes, execute step S31; S35, determine whether item1 exists in other switches. If so, use item1.ip to query the switch table to obtain the login user name and login password; if not, execute step S37; S36, operating on the switch to release the binding data corresponding to item1, and deleting the binding record of item1 in the port binding table; S37, add a binding record corresponding to the item on the switch, add the item binding record in the port binding table, and then execute step S31.

7. A terminal operation and maintenance management system according to claim 5, characterized in that: The switch access module simulates manual login to the switch through the SSH terminal software and inputs switch operation related commands to access or operate the switch; The steps to use the SSH.net component to simulate a switch include: S41. First, use the switch IP, user name and password to create a ShellStream object to log in to the switch and establish a connection; S42, creating a ShellStream object to send a switch command; S43. Get the returned result text through the shellStream.Expect method; S44, parse the text to obtain the required data.

Images