Local area network state monitoring management system

Abstract

The invention discloses a local area network state monitoring management system, and relates to the technical field of local area network monitoring, the local area network state monitoring management system comprises a server case and a management system, a network card, a central processor and a response module are installed in the server case, a base assembly is arranged at the bottom of the server case, and the base assembly comprises a base body arranged at the bottom of the server case; positioning seats are fixedly installed on the edges of the two sides of the base body, sliding grooves are formed in the positioning seats, sliding rails are installed on the sliding grooves in a sliding mode, the sliding rails are fixedly installed on a server case, a lead mechanism is installed on the base body, and a driving mechanism is connected to the lead mechanism. The base assembly further comprises rack sliding grooves formed in the edges of the two sides of the base body and mounting holes formed in the edge of the tail end of the base body. According to the local area network state monitoring and management system, the risk that a network cable and a power line fall off in the moving process is effectively avoided, DoS attacks can be monitored, and an alarm is triggered.

Description

Technical Field

[0001] This invention relates to the field of local area network (LAN) monitoring technology, specifically a LAN status monitoring and management system. Background Technology

[0002] A local area network (LAN) is a network that connects computers, servers, printers, and other devices within a small area using network devices such as switches and routers to achieve data sharing and communication. LAN servers are typically installed in server racks.

[0003] In the prior art, patent announcement number CN222914138U discloses a server. It includes a chassis, and a power supply module, a motherboard, and a power supply board located within the chassis; the motherboard and the power supply board are separately configured; the power supply module is connected to the motherboard via a first power supply cable to supply power to the motherboard; the power supply board includes a board body, a first connector, and a second connector; the first connector and the second connector are disposed on the power supply board; the first connector includes a graphics card interface for inserting a graphics card; the second connector includes a power supply interface for connecting one end of a second power supply cable, the other end of which is used to connect to the power supply module; the first connector and the second connector are electrically connected so that the power supply module supplies power to the graphics card inserted into the second connector via the second power supply cable connected to the second connector.

[0004] Server chassis are typically installed in server racks and can be pulled out to allow users to inspect the components inside. However, network cables and power cables are connected to the rear of the server chassis via plugs. During the process of pulling out the server chassis, the cables are subject to external force, which can easily cause the network cables or power cables to come loose. Furthermore, the server is vulnerable to DoS attacks, which can cause losses to users. Summary of the Invention

[0005] The purpose of this invention is to provide a local area network status monitoring and management system to solve the problems in the prior art.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a local area network (LAN) status monitoring and management system, comprising a server chassis and a management system, wherein a network card, a central processing unit, and a response module are installed inside the server chassis, and a base assembly is provided at the bottom of the server chassis, the base assembly comprising a base body disposed at the bottom of the server chassis, positioning seats being fixedly installed at both sides of the base body, the positioning seats having sliding grooves, and slide rails being slidably installed on the sliding grooves and fixedly installed on the server chassis, and a lead wire mechanism being installed on the base body, the lead wire mechanism being connected to a drive mechanism.

[0007] Preferably, the base assembly further includes rack grooves formed on both sides of the base body and mounting holes formed on the end edge of the base body.

[0008] Preferably, the slide rail is slidably mounted on the positioning seat via a slide groove, and the server chassis is movably mounted above the base body via the slide rail.

[0009] Preferably, the lead wire mechanism includes two mounting brackets fixedly installed on the base body. Each mounting bracket is rotatably mounted with a reversing wheel. A drive wheel is rotatably mounted above the reversing wheel. A linkage shaft is fixedly installed between the drive wheels. A first limit wheel is rotatably mounted on one side of the reversing wheel. A second limit wheel is rotatably mounted below the reversing wheel. A network cable and a power cable are respectively provided between the drive wheel and the reversing wheel.

[0010] Preferably, the drive mechanism includes a drive shaft rotatably mounted between the positioning seats and a driven sprocket fixedly mounted on one side of the drive wheel. A connecting shaft is fixedly mounted at the middle position of the driven sprocket, and the end of the connecting shaft is fixedly mounted at the middle position of the drive wheel. A gear and a drive sprocket are fixedly mounted on the drive shaft. A transmission chain connects the drive sprocket and the driven sprocket. A sprocket frame is fixedly mounted on the base body. A guide sprocket is rotatably mounted on the sprocket frame. A drive rack is fixedly mounted at the bottom of the server chassis.

[0011] Preferably, one end of the network cable is plugged into the network port on the server chassis, and the other end of the network cable is fixedly installed in the mounting hole; one end of the power cord is plugged into the power socket on the server chassis, and the other end of the power cord is fixedly installed in the mounting hole.

[0012] Preferably, the gear and the drive sprocket are both rotatably mounted on the base body via a drive shaft, the gear meshes with the drive rack, and the drive rack is slidably mounted on the base body via a rack groove.

[0013] Preferably, the management system includes a data capture module, a data analysis module, and an intrusion response module. The network card only transmits data packets sent to the local machine to the upper-layer program, and discards all other packets. It will only receive all data streams passing through when the network card is set to promiscuous mode, regardless of whether the destination address is the local machine.

[0014] Preferably, after the data packet captured by the data capture module is passed to the data analysis module for further analysis, the data analysis needs to go through two steps. First, the captured data packet is parsed according to the protocol, and the key values ​​of each field are recorded. The second step is to compare these values ​​with the objects in the intrusion feature database to determine whether an intrusion has occurred.

[0015] Preferably, the intrusion response module is used to notify the administrator of the existence of a wireless DoS attack, and its alarm method is to issue an audible warning or flashing light.

[0016] Compared with the prior art, the beneficial effects of the present invention are:

[0017] In this application, when the server chassis is pulled outward, the drive rack moves outward accordingly. This movement causes the gear to rotate, which in turn drives the drive shaft to rotate. Subsequently, the drive sprocket rotates due to the rotation of the gear, and the transmission chain drives the driven sprocket to rotate. Finally, the drive wheel rotates due to the movement of the transmission chain. The rotation of the drive wheel causes one end of the network cable and power cable to move forward with the server chassis, thereby maintaining a loose connection between the network cable and power cable and the server chassis, effectively avoiding the risk of the network cable and power cable coming loose during movement.

[0018] In this application, data packets are divided into data frames, control frames, and management frames, and decoded to extract key information, including frame subtype, SSID, MAC address, and signal strength. An intrusion detection signature database stores attack characteristic parameters, which are dynamically adjusted based on statistical information to adapt to changes in network conditions. If a data packet does not match the database parameters, it is considered normal; if it matches, it may be under a wireless denial-of-service (DoS) attack and requires further detection. Only when the characteristics of suspicious data packets cumulatively exceed a set threshold is it identified as an attack and an alarm is triggered, minimizing user losses. Attached Figure Description

[0019] Figure 1 This is a schematic diagram of the overall structure of the present invention;

[0020] Figure 2 This is a partial structural diagram of the present invention;

[0021] Figure 3 This is a schematic diagram of the base assembly of the present invention;

[0022] Figure 4 This is a schematic diagram of the assembly of the lead wire mechanism and the drive mechanism of the present invention;

[0023] Figure 5 This is a schematic diagram of the lead wire mechanism of the present invention.

[0024] Figure 6 This is a schematic diagram of the drive mechanism of the present invention.

[0025] Figure 7 This is a partial schematic diagram of the lead wire mechanism and drive mechanism of the present invention.

[0026] Figure 8 This is a system flowchart of the present invention.

[0027] The diagram shows the following components: 1. Server chassis; 2. Network interface card (NIC); 3. Central processing unit (CPU); 4. Response module; 5. Base assembly; 501. Base body; 502. Rack and pinion slide; 503. Positioning seat; 504. Slide; 505. Slide rail; 506. Mounting hole; 6. Lead wire mechanism; 601. Mounting bracket; 602. Drive wheel; 603. Linkage shaft; 604. First limit wheel; 605. Second limit wheel; 606. Network cable; 607. Power cord; 608. Directional wheel; 7. Drive mechanism; 701. Driven sprocket; 702. Guide sprocket; 703. Sprocket frame; 704. Transmission chain; 705. Drive rack; 706. Gear; 707. Drive sprocket; 708. Drive shaft. Detailed Implementation

[0028] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0029] like Figure 1 and Figure 2 As shown, the present invention provides a technical solution for a local area network (LAN) status monitoring and management system, including a server chassis 1 and a management system. The server chassis 1 houses a network card 2, a central processing unit 3, and a response module 4. A base assembly 5 is located at the bottom of the server chassis 1, and a lead wire mechanism 6 is mounted on the base body 501. A drive mechanism 7 is connected to the lead wire mechanism 6.

[0030] like Figure 2 and Figure 3 As shown, the base assembly 5 includes a base body 501 disposed at the bottom of the server chassis 1. Positioning seats 503 are fixedly installed on both sides of the base body 501. The positioning seats 503 are provided with sliding grooves 504. Slide rails 505 are slidably installed on the sliding grooves 504 and are fixedly installed on the server chassis 1. The base assembly 5 also includes rack and pinion grooves 502 provided on both sides of the base body 501 and mounting holes 506 provided on the end edge of the base body 501. The slide rails 505 are slidably installed on the positioning seats 503 through the sliding grooves 504. The server chassis 1 is movably installed on the top of the base body 501 through the slide rails 505.

[0031] Specifically, when a user needs to maintain or repair the server chassis 1, they can pull the chassis outwards. At this time, the slide rail 505 will move accordingly towards the outside of the slide groove 504. This action allows the server chassis 1 to be smoothly moved out of the rack, providing the user with a convenient maintenance space and allowing them to easily access the various components inside the chassis. Conversely, when the user has completed the maintenance work, they can push the chassis inwards. At this time, the slide rail 505 will move towards the inside of the slide groove 504, thus allowing the server chassis 1 to smoothly return to its designated position in the rack, ensuring the cleanliness of the rack interior and the safety of the equipment.

[0032] like Figure 4 and Figure 5 As shown, the lead wire mechanism 6 includes two mounting brackets 601 fixedly mounted on the base body 501. Each mounting bracket 601 is rotatably mounted with a reversing wheel 608. A drive wheel 602 is rotatably mounted above the reversing wheel 608. A linkage shaft 603 is fixedly mounted between the drive wheels 602. A first limit wheel 604 is rotatably mounted on one side of the reversing wheel 608, and a second limit wheel 605 is rotatably mounted below the reversing wheel 608. A network cable 606 and a power cable 607 are respectively provided between the drive wheel 602 and the reversing wheel 608. One end of the network cable 606 is plugged into the network port on the server chassis 1, and the other end of the network cable 606 is fixedly installed in the mounting hole 506. One end of the power cable 607 is plugged into the power socket on the server chassis 1, and the other end of the power cable 607 is fixedly installed in the mounting hole 506.

[0033] Specifically, the rotation of the drive wheel 602 effectively moves one end of the network cable 606 and the power cable 607 forward, following the server chassis 1. This design ensures that the network cable 606 and the power cable 607 maintain a loose connection with the server chassis 1, thus preventing the network cable 606 and the power cable 607 from accidentally coming off during movement due to cable loosening.

[0034] like Figure 6 and Figure 7As shown, the drive mechanism 7 includes a drive shaft 708 rotatably mounted between the positioning seats 503 and a driven sprocket 701 fixedly mounted on one side of the drive wheel 602. A connecting shaft is fixedly mounted in the middle of the driven sprocket 701, and the end of the connecting shaft is fixedly mounted in the middle of the drive wheel 602. A gear 706 and a drive sprocket 707 are fixedly mounted on the drive shaft 708. A transmission chain 704 connects the drive sprocket 707 and the driven sprocket 701. A sprocket frame 703 is fixedly mounted on the base body 501. A guide sprocket 702 is rotatably mounted on the sprocket frame 703. A drive rack 705 is fixedly mounted at the bottom of the server chassis 1. The gear 706 and the drive sprocket 707 are both rotatably mounted above the base body 501 via the drive shaft 708. The gear 706 meshes with the drive rack 705. The drive rack 705 is slidably mounted on the base body 501 via the rack groove 502.

[0035] Specifically, when you pull the server chassis 1 outward, the drive rack 705 moves outward accordingly. As the drive rack 705 moves outward, it further causes the gear 706 to start rotating. Once the gear 706 starts rotating, it meshes with the drive shaft 708, causing the drive shaft 708 to also start rotating. As the drive shaft 708 rotates, the drive sprocket 707 also rotates. The rotation of the drive sprocket 707 transmits power to the driven sprocket 701 through the transmission chain 704, causing the driven sprocket 701 to also start rotating.

[0036] like Figure 8 As shown, the management system includes a data capture module, a data analysis module, and an intrusion response module 4. Network interface card 2 only transmits data packets destined for the local machine to the upper-layer program, discarding all other packets. Only when network interface card 2 is set to promiscuous mode will it receive all passing data streams, regardless of whether their destination address is the local machine. After the data packets captured by the data capture module are passed to the data analysis module for further analysis, the data analysis requires two steps. First, the captured data packets are parsed according to the protocol, and the key values ​​of each field are recorded. The second step is to compare these values ​​with objects in the intrusion signature database to determine whether an intrusion has occurred.

[0037] Specifically, captured data packets are categorized into data frames, control frames, and management frames, and then decoded according to the IEEE 802.11 network protocol to obtain a wealth of useful information. This includes frame subtypes, network SSID, source and destination MAC addresses, and signal strength. This information can be used for further analysis of the wireless LAN. Intrusion detection signature databases are pre-stored with characteristic parameters indicating an attack, such as the number of users connected to the access point (AP), the frequency of user-sent verification frames, and channel occupancy time. These parameters are dynamically adjusted based on statistical information, ensuring reasonable detection results even with changes in the LAN's state. If the information in a received data packet does not match the parameters in the intrusion signature database, the packet is considered normal; if it matches, it may be under a wireless DoS attack. The packet needs to be forwarded to the next stage for further detection. Suspicious data packets received during detection are saved, and subsequent packets are closely monitored for similar characteristics. Anomalies in only a few packets do not necessarily indicate a wireless DoS attack. Only when packets with similar characteristics accumulate to a certain level, exceeding a threshold, can an attack be confirmed and an alarm triggered.

[0038] Working Principle: In use, the base body 501 is first fixedly installed inside the server rack. When the user pulls the server chassis 1 outwards, the slide rail 505 moves outwards into the slide groove 504, allowing the server chassis 1 to be moved out of the rack for easy access to the components inside. When the user pushes the server chassis 1, the slide rail 505 moves inwards into the slide groove 504, allowing the server chassis 1 to re-enter the rack. Furthermore, when the server chassis 1 is pulled outwards, the drive rack 705 moves outwards with it, driving the gear 706 to rotate. The rotation of the gear 706 then drives the drive shaft 708 to rotate, which in turn drives the drive sprocket 707 to rotate. The rotation of the drive sprocket 707, in turn, drives the driven sprocket 701 to rotate via the transmission chain 704, which in turn drives the drive wheel 602 to rotate. The rotation of drive wheel 602 causes one end of network cable 606 and power cable 607 to move forward with server chassis 1, maintaining a loose connection between network cable 606 and power cable 607 and server chassis 1, preventing them from falling off during the loosening process. During monitoring, data packets are classified into data frames, control frames, and management frames, and decoded to obtain key information such as frame subtype, SSID, MAC address, and signal strength. This information helps in analyzing the wireless LAN. The intrusion detection signature database stores attack characteristic parameters, such as the number of users, verification frame frequency, and channel occupancy time. These parameters are dynamically adjusted based on statistical information to adapt to changes in network status. If a data packet does not match the signature database parameters, it is considered normal; if it matches, it may be under a wireless DoS attack and requires further detection. If suspicious data packets have the same characteristics, an attack is only identified and an alarm is triggered when these characteristics accumulate to exceed a threshold.

[0039] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered in all respects as exemplary and non-limiting, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

Claims

1. A local area network (LAN) status monitoring and management system, comprising a server chassis (1) and a management system, wherein a network interface card (NIC) (2), a central processing unit (3), and a response module (4) are installed inside the server chassis (1), characterized in that: The server chassis (1) is provided with a base assembly (5) at the bottom. The base assembly (5) includes a base body (501) located at the bottom of the server chassis (1). Positioning seats (503) are fixedly installed on both sides of the base body (501). A sliding groove (504) is provided on the positioning seat (503). A slide rail (505) is slidably installed on the sliding groove (504) and the slide rail (505) is fixedly installed on the server chassis (1). A lead wire mechanism (6) is installed on the base body (501) and a drive mechanism (7) is connected to the lead wire mechanism (6).

2. The local area network status monitoring and management system according to claim 1, characterized in that: The base assembly (5) further includes rack grooves (502) opened on both sides of the base body (501) and mounting holes (506) opened on the end edge of the base body (501).

3. The local area network status monitoring and management system according to claim 2, characterized in that: The slide rail (505) is slidably mounted on the positioning seat (503) via the slide groove (504), and the server chassis (1) is movably mounted above the base body (501) via the slide rail (505).

4. A local area network status monitoring and management system according to claim 3, characterized in that: The lead wire mechanism (6) includes two mounting brackets (601) fixedly installed on the base body (501). Each mounting bracket (601) is rotatably mounted with a reversing wheel (608). A drive wheel (602) is rotatably mounted above the reversing wheel (608). A linkage shaft (603) is fixedly installed between the drive wheels (602). A first limiting wheel (604) is rotatably mounted on one side of the reversing wheel (608). A second limiting wheel (605) is rotatably mounted below the reversing wheel (608). A network cable (606) and a power cable (607) are respectively provided between the drive wheel (602) and the reversing wheel (608).

5. A local area network status monitoring and management system according to claim 4, characterized in that: The drive mechanism (7) includes a drive shaft (708) rotatably mounted between the positioning seats (503) and a driven sprocket (701) fixedly mounted on one side of the drive wheel (602). A connecting shaft is fixedly mounted in the middle of the driven sprocket (701), and the end of the connecting shaft is fixedly mounted in the middle of the drive wheel (602). A gear (706) and a drive sprocket (707) are fixedly mounted on the drive shaft (708). A transmission chain (704) connects the drive sprocket (707) and the driven sprocket (701). A sprocket frame (703) is fixedly mounted on the base body (501). A guide sprocket (702) is rotatably mounted on the sprocket frame (703). A drive rack (705) is fixedly mounted at the bottom of the server chassis (1).

6. A local area network status monitoring and management system according to claim 5, characterized in that: One end of the network cable (606) is plugged into the network port on the server chassis (1), and the other end of the network cable (606) is fixedly installed in the mounting hole (506). One end of the power cord (607) is plugged into the power socket on the server chassis (1), and the other end of the power cord (607) is fixedly installed in the mounting hole (506).

7. A local area network status monitoring and management system according to claim 6, characterized in that: The gear (706) and the drive sprocket (707) are both rotatably mounted on the base body (501) via the drive shaft (708). The gear (706) meshes with the drive rack (705), and the drive rack (705) is slidably mounted on the base body (501) via the rack groove (502).

8. A local area network status monitoring and management system according to claim 1, characterized in that: The management system includes a data capture module, a data analysis module and an intrusion response module (4). The network card (2) only transmits the data packets sent to the local machine to the upper-layer program, and discards all other packets. It will only receive all data streams that pass through when the network card (2) is set to promiscuous mode, regardless of whether the destination address is the local machine.

9. A local area network status monitoring and management system according to claim 8, characterized in that: After the data capture module captures the data packets, it needs to be passed to the data analysis module for further analysis. The data analysis requires two steps. First, the captured data packets are parsed to record the key values ​​of each field. Second, these values ​​are compared with objects in the intrusion signature database to determine whether an intrusion has occurred.

10. A local area network status monitoring and management system according to claim 9, characterized in that: The intrusion response module (4) is used to notify the administrator of the existence of a wireless DoS attack. Its alarm method is to issue an audible warning or flash a light.

Images