Method for realizing simple operation, maintenance and management functions based on network management software of upper computer

Abstract

The invention discloses a method for realizing a simple operation, maintenance and management function based on network management software of an upper computer, which comprises the following steps that: S1, the upper computer retrieves all equipment in an environment: the upper computer sends a broadcast message corresponding to retrieval equipment through an equipment retrieval command, and the equipment receiving the broadcast message in a network sends the broadcast message corresponding to the retrieval equipment; the equipment capable of analyzing the message replies a corresponding response message, and the message carries the basic information of the equipment; after receiving the response message, the upper computer analyzes the content in the message and presents the basic information of the equipment in software; s2, the upper computer carries out basic configuration operation on the equipment; and S3, the upper computer carries out upgrading operation on the equipment. Through the technical scheme of the invention, an administrator can retrieve all equipment in the environment through the upper computer, check whether the state of the equipment in the environment is normal or not, and perform simple operation and management on the equipment based on two-layer forwarding; the method is helpful for an administrator to quickly position and solve network faults, and reduces service interruption caused by the faults.

Description

Technical Field

[0001] The present invention relates to the technical field of data communication, and in particular to a method for realizing simple operation maintenance management functions based on upper computer network management software. The method can realize that the upper computer network management software interacts with SOAM (Simple Operation Administration and Maintenance) through various commands, and realizes functions such as searching all devices in the environment, configuring IP addresses, operating devices to restore factory configurations, restarting, delaying restarting, upgrading image files, upgrading OEM files, upgrading BIOS files, uploading configuration files, etc. Background Art

[0002] Usually, when switch equipment is upgraded and configured in actual use, it can help administrators easily monitor, identify and solve network problems, manage equipment, and improve network security and stability. The existing technology mainly interacts with SOAM through the host computer software to complete part of the configuration and upgrade operations of the equipment. SOAM has the following characteristics: 1. Scope of application and versatility: SOAM is designed for specific network environments or devices and is only applicable to specific network devices. Its functions and performance will be customized according to specific needs.

[0003] 2. Maintenance method: SOAM uses specific host computer software for management. This mode can reduce the need for personnel to operate equipment through web pages in a specific local area network, or to operate equipment through serial ports, thereby reducing the risk of errors during operation and the cost of personnel maintenance, making it more convenient and quick.

[0004] 3. Data interaction and processing state machine: SOAM uses a custom check field, and can use different keys to interact with different devices, making the message interaction process more secure. The processing state machine is simpler and easier to understand, and different types of operation methods use different processing procedures, so that the operation of the host computer response can be completed without taking up too much memory.

[0005] To sum up, private network management software may have more advantages in terms of scope of application, maintenance methods, data interaction and processing status, especially for complex network environments that require efficient and real-time data collection.

[0006] The information disclosed in this background technology section is only intended to deepen the understanding of the overall background technology of the present invention, and should not be regarded as acknowledging or suggesting in any form that the information constitutes the prior art already known to those skilled in the art. Summary of the invention

[0007] In view of the problems existing in the prior art, the object of the present invention is to provide a method for realizing simple operation, maintenance and management functions based on upper computer network management software.

[0008] In order to achieve the above object, the present invention adopts the following technical solutions: A method for realizing simple operation, maintenance and management functions based on upper computer network management software, the method comprising the following steps: S1. The host computer searches for all devices in the environment: The host computer sends a broadcast message corresponding to the searched device through the device search command. The device in the network that receives the broadcast packet and can parse the message will reply with a corresponding response message, which contains the basic information of the device. After receiving the response message, the host computer parses the content in the message and presents the basic information of the device in the software. S2. The host computer performs basic configuration operations on the device, including: S21. First, the host computer sends a connection request message to the device with the destination MAC of (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The subsequent message interactions will match this field to ensure that the message is the message data of the same connection, and will respond with a connection response message. After the host computer receives the response message of successful connection, it will send a request message for control information. After receiving the request message for control information, the device parses the control content in the message and modifies the IP address and mask address of the switch accordingly. After the operation is completed, it returns a successful response control request message to the host computer. If it fails, it will return a failed response control message. S22, the host computer performs a factory reset operation on the device through a factory reset command; the execution process is the same as step S21; S23, the host computer performs a delayed restart operation on the device through a device restart command. The delay parameter determines the delay time in milliseconds. The execution process is the same as step S21; S3. The host computer performs upgrade operations on the device, including: S31. The host computer upgrades the OS file of the device through the image upgrade command. First, the host computer sends a connection request message to the device with the destination MAC of (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The message interaction of subsequent operations will match this field to ensure that the message is the message data of the same connection, and respond to a response message of a connection at the same time; after the host computer receives the response message of successful connection, it starts to send data messages; during the data transmission process, each data message needs to respond to a successful reception response message from the corresponding device, otherwise the host computer will keep sending until it receives a successful response; when the data is sent, the host computer will send a data transmission completion request to the device. After receiving the request message, the device will reply with a successful response message and release the memory of this connection. After receiving the response message, the host computer ends the connection. If the host computer does not receive a successful or failed response message, the connection will be terminated after a certain period of time. S32, the host computer performs a BIOS file upgrade operation on the device through a BIOS upgrade command, and the execution process is the same as step S31; S33, the host computer performs an OEM file upgrade operation on the device through an OEM upgrade command, and the execution process is the same as step S31; S34, the host computer performs a configuration file upgrade operation on the device through a configuration file upgrade command, and the execution process is the same as step S31.

[0009] Furthermore, the request message for retrieving the device in step S1 uses the frame format of the extended protocol, and the following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_REQUEST; Option in the protocol header: TSC_DCP_OPT_ALL; subOption in the protocol header: TSC_DCP_SUB_ALL; The length field in the protocol header is 0, indicating that there is no additional block information.

[0010] Furthermore, in step S1, the message of the device responding to the retrieval request uses the frame format of the extended protocol, and the following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_RSPSUCCESS; Option in the protocol header: TSC_DCP_OPT_MANU_CUS.

[0011] Furthermore, in step S1, the request message for establishing a connection between the host computer and the device uses a custom frame format, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: randomly generated UUID; seqNum in the frame header: sequence number value; Status in the frame header: 0; The option field in the block information header is: TSC_SOAM_OPTION_CON_AR; The randomXid field in the block information header is: a random number used to identify this connection request operation; The seqNum field in the block information header is: sequence number value; The block information must contain at least one signature information for security authentication of the connection: The message type is: TSC_SOAM_BLK_CON_T_SIGN; The message length is: 4; The information value is: According to the following rules, calculate the CRC32 value of the generated data; The calculation rules for signature information are as follows: First, construct the content to be signed, an array constructed by the frame destination MAC + frame source MAC + frame header uuid + frame header + seqNum + block information header randomXid + block information header seqNum + Keyword, and then calculate the CRC32 value of this array as the final signature information; the Keyword is a specially customized SOAM authentication key, and a key value is set by default for verification; if this value is inconsistent with the value used on the device side, the signature information verification will fail and the connection will fail.

[0012] Furthermore, in step S1, the message that the device responds to the connection establishment request uses a custom frame format, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the connection is established successfully, and other values ​​indicate failure.

[0013] Furthermore, the request message for releasing the device connection in step S1 uses a custom frame format, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: the UUID of the established connection, or a randomly generated UUID; The option field in the block information header is: TSC_SOAM_OPTION_REL_FORCE.

[0014] Furthermore, in step S1, the device uses a custom frame format in response to the release connection request. The following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the release is successful, and other values ​​indicate failure.

[0015] By adopting the above technical solution, the present invention has the following beneficial effects: 1: The administrator can search all devices in the environment through the host computer to check whether the devices are in normal state in the environment, and perform simple operations and management on the devices based on Layer 2 forwarding. This improves the simplicity and security of operations.

[0016] 2: Fault diagnosis When a network fault occurs, the network management system can quickly identify the source of the fault and provide a detailed fault diagnosis report. This helps administrators quickly locate and resolve network faults and reduce business interruptions caused by faults.

[0017] 3: The simple operation, maintenance and management function of the equipment can manage the company's switch equipment in the enterprise network. The administrator can uniformly configure and manage these devices through the host computer, simplify the equipment management process and improve management efficiency.

[0018] The advantages of simple operation, maintenance and management functions also include security management, performance optimization and other aspects, which can greatly improve the company's network management level and efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 It is the migration diagram of SOAM session state; Figure 2 A structural diagram of establishing a connection between the host computer and the device of the present invention; Figure 3 This is a flow chart of the write operation performed by the host computer of the present invention; Figure 4 The figure is a flow chart of the upgrade operation of the host computer of the present invention. DETAILED DESCRIPTION

[0021] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] The specific implementation of the present invention is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described here is only used to illustrate and explain the present invention, and is not used to limit the present invention.

[0023] Combination Figure 1-4 As shown in the figure, to achieve interaction between the host computer software and SOAM and complete partial configuration and upgrade operations on the device, it is necessary to enable the device to identify the corresponding message type and correctly parse the message content, so as to achieve simple operation and maintenance of the device. When the device's IP address is not clear to access the device webpage, and it is impossible to connect the device through the serial port on site, this method can be used to directly set the device's IP, upgrade, restart and other functions. Compared with the snmp management method, this method is safer, simpler and more stable.

[0024] In order to ensure that the Ethernet packets of SOAM can be sent to the CPU correctly, two methods are designed: ①: For broadcast packets, the ACL rule is used to match the destination MAC address of ff:ff:ff:ff:ff:ff, and the Ethernet protocol type is 0xf1f1.

[0025] ②: The unicast message configures the device's own MAC address through the destination MAC address of the message and is sent to the CPU by the switch.

[0026] 1. Packet Encapsulation Format One is based on other protocols and extended with private custom options; the other is a private custom format.

[0027] 1.1 Other formats of extensions: The message format of the relevant protocol is borrowed and private custom options are extended. The message format is shown in Table 1, and the information content in the message format is shown in Tables 2 to 4.

[0028]

[0029] 1.2 TSC custom frame, see Table 5 for the specific message format, and see Tables 6 to 8 for the information content in the message format.

[0030]

[0031]

[0032] The content of the block information is optional and depends on the option field in the block information header. The content of the block information is encoded in the TLV format. There can be multiple TLVs in a block information to tell the device what operations need to be performed.

[0033] 2. Specific key values ​​of message types: 2.1 Request message for retrieving device The frame format of the extended protocol is used. The following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_REQUEST; Option in the protocol header: TSC_DCP_OPT_ALL; subOption in the protocol header: TSC_DCP_SUB_ALL; The length field in the protocol header is 0, indicating that there is no additional block information.

[0034] 2.2 Device response to retrieval request message The frame format of the extended protocol is used. The following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_RSPSUCCESS; Option in the protocol header: TSC_DCP_OPT_MANU_CUS; The subOption options in the protocol header are as follows:

[0035] 2.3 Request message to establish connection with the device A custom frame format is used, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: randomly generated UUID; seqNum in the frame header: sequence number value; Status in the frame header: 0; The option field in the block information header is: TSC_SOAM_OPTION_CON_AR; The randomXid field in the block information header is: a random number used to identify this connection request operation; The seqNum field in the block information header is: sequence number value; The block information must contain at least one signature information for security authentication of the connection: The message type is: TSC_SOAM_BLK_CON_T_SIGN; The message length is: 4; The information value is: According to the following rules, calculate the CRC32 value of the generated data.

[0036] Calculation rules for signature information: First, construct the content to be signed, an array constructed by the frame destination MAC + frame source MAC + frame header uuid + frame header + seqNum + block information header randomXid + block information header seqNum + Keyword, and then calculate the CRC32 value of this array as the final signature information. Among them, the Keyword is a custom SOAM authentication key, and a key value will be set by default for verification. If this value is inconsistent with the one used on the device side, the signature information verification will fail and the connection will fail.

[0037] 2.4 Device responds to the connection request message A custom frame format is used, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the connection is established successfully, and other values ​​indicate failure.

[0038] 2.5 Request message for releasing device connection A custom frame format is used, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: the UUID of the established connection, or a randomly generated UUID; The option field in the block information header is: TSC_SOAM_OPTION_REL_FORCE.

[0039] 2.6 Device responds to the message of releasing the connection request A custom frame format is used, and the following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the release is successful, and other values ​​indicate failure.

[0040] 3. SOAM state machine: SOAM has been added to the device authentication process, and the operations it supports have administrator privileges. In order to make SOAM more controllable, secure, and extensible, most of the operations of SOAM need to establish a session before they can be performed. Security can be increased by controlling the process of establishing a session. Currently, only one session is allowed between the device and the host computer. If a request to establish a session connection is made after the device has established a session with the host computer, the device will return an error. Only when this session is released can the device establish a session with the host computer again. This can be changed to establish multiple sessions with the host computer according to specific needs, and manage multiple devices at the same time.

[0041] In addition to some Read-related operations, the host computer needs to establish a session connection before operating the device. After the session is established, the device is operated through the session connection. The following is a flowchart for establishing a session connection. Figure 2 shown.

[0042] After a session is established between the host computer and the device, the host computer can write files or data to the device. The flowchart of the Write operation is as follows: Figure 3 shown.

[0043] If the upgrade file has been successfully uploaded to the device through the write operation, you can send the upgrade command to the device. Figure 4 shown.

[0044] The host computer operates the device through various commands. For specific parameter descriptions, please see the table below:

[0045]

[0046] The method of realizing simple operation, maintenance and management functions based on the host computer network management software is as follows: 1. All devices in the host computer search environment: Step 1: The host computer sends a broadcast message for the corresponding search device through the device search command. The device in the network that receives the broadcast packet and can parse the message will reply with a corresponding response message, which contains some basic information about the device. After receiving the response message, the host computer will parse the content of the message and present the basic information of the device in the software.

[0047] 2. The host computer performs basic configuration operations on the device: Step 1: The host computer sends the relevant configuration commands. First, the host computer sends a connection request message to the device with the destination MAC (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The subsequent message interactions will match this field to ensure that the message is the message data of the same connection, and will respond to a connection response message. After the host computer receives the response message of successful connection, it sends a request message for control information. After receiving the request message for control information, the device parses the control content in the message and modifies the IP address and mask address of the switch accordingly. After the operation is completed, it will return a successful response control request message to the host computer. If it fails, it will return a failed response control message.

[0048] Step 2: The host computer performs factory reset on the device through the factory reset command. The execution process is the same as step 1 in point 2.

[0049] Step 3: The host computer delays the restart of the device through the device restart command. The delay parameter determines the delay time in milliseconds. The execution process is the same as step 1 in point 2.

[0050] 3. The host computer upgrades the device: Step 1: The host computer upgrades the OS file of the device through the image upgrade command. First, the host computer sends a connection request message to the device with the destination MAC (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The message interaction of subsequent operations will match this field to ensure that the message is the message data of the same connection, and a connection response message will be responded at the same time. When the host computer receives the response message of successful connection, it starts to send data messages. When the data is not being sent, each data message needs to respond to a successful response message from the corresponding device, otherwise the host computer will keep sending until a successful response is received. When the data is sent, the host computer will send a request to the device to complete the data transmission. After receiving the request message, the device will reply with a successful response message and release the memory of this connection. After receiving the response message, the host computer will end the connection. If the host computer does not receive a successful or failed response message, the connection will time out after a certain period of time.

[0051] Step 2: The host computer uses the BIOS upgrade command to upgrade the BIOS file of the device. The execution process is the same as step 1 in point 3.

[0052] Step 3: The host computer uses the OEM upgrade command to upgrade the OEM file of the device. The execution process is the same as step 1 in point 3.

[0053] Step 4: The host computer upgrades the configuration file of the device through the configuration file upgrade command. The execution process is the same as step 1 in point 3.

[0054] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for realizing simple operation, maintenance and management functions based on upper computer network management software, characterized in that: The method comprises the following steps: S1. The host computer searches for all devices in the environment: The host computer sends a broadcast message corresponding to the searched device through the device search command. The device in the network that receives the broadcast packet and can parse the message will reply with a corresponding response message, which contains the basic information of the device. After receiving the response message, the host computer parses the content in the message and presents the basic information of the device in the software; S2. The host computer performs basic configuration operations on the device, including: S21. First, the host computer sends a connection request message to the device with the destination MAC of (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The subsequent message interactions will match this field to ensure that the message is the message data of the same connection, and will respond with a connection response message. After the host computer receives the response message of successful connection, it will send a request message for control information. After receiving the request message for control information, the device parses the control content in the message and modifies the IP address and mask address of the switch accordingly. After the operation is completed, it returns a successful response control request message to the host computer. If it fails, it will return a failed response control message. S22, the host computer performs a factory reset operation on the device through a factory reset command; the execution process is the same as step S21; S23, the host computer performs a delayed restart operation on the device through a device restart command. The delay parameter determines the delay time in milliseconds. The execution process is the same as step S21; S3. The host computer performs upgrade operations on the device, including: S31. The host computer upgrades the OS file of the device through the image upgrade command. First, the host computer sends a connection request message to the device with the destination MAC of (60:63:fd:00:00:03). After receiving the message, the device will check the CRC32 field in the message. After the check is successful, the uuid and seqNmu field information in the message will be retained. The message interaction of subsequent operations will match this field to ensure that the message is the message data of the same connection, and respond to a response message of a connection at the same time; after the host computer receives the response message of successful connection, it starts to send data messages; during the data transmission process, each data message needs to respond to a successful reception response message from the corresponding device, otherwise the host computer will keep sending until a successful response is received; when the data is sent, the host computer will send a data transmission completion request to the device. After receiving the request message, the device will reply with a successful response message and release the memory of this connection. After receiving the response message, the host computer ends the connection. If the host computer does not receive a successful or failed response message, the connection will be terminated after a certain period of time. S32, the host computer performs a BIOS file upgrade operation on the device through a BIOS upgrade command, and the execution process is the same as step S31; S33, the host computer performs an OEM file upgrade operation on the device through an OEM upgrade command, and the execution process is the same as step S31; S34, the host computer performs a configuration file upgrade operation on the device through a configuration file upgrade command, and the execution process is the same as step S31.

2. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: The request message for retrieving the device in step S1 uses the frame format of the extended protocol. The following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_REQUEST; Option in the protocol header: TSC_DCP_OPT_ALL; subOption in the protocol header: TSC_DCP_SUB_ALL; The length field in the protocol header is 0, indicating that there is no additional block information.

3. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: The message that the device responds to the retrieval request in step S1 uses the frame format of the extended protocol. The following are the parameter values ​​it uses: sId in the protocol header: TSCSOAM_DCP_SERVICE_IDENTIFY; sType in the protocol header: TSCSOAM_DCP_SERVICE_TYPE_RSPSUCCESS; Option in the protocol header: TSC_DCP_OPT_MANU_CUS.

4. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: In step S1, the request message for establishing a connection between the host computer and the device uses a custom frame format. The following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: randomly generated UUID; seqNum in the frame header: sequence number value; Status in the frame header: 0; The option field in the block information header is: TSC_SOAM_OPTION_CON_AR; The randomXid field in the block information header is: a random number used to identify this connection request operation; The seqNum field in the block information header is: sequence number value; The block information must contain at least one signature information for security authentication of the connection: The message type is: TSC_SOAM_BLK_CON_T_SIGN; The message length is: 4; The information value is: According to the following rules, calculate the CRC32 value of the generated data; The calculation rules for signature information are as follows: First, construct the content to be signed, an array constructed by the frame destination MAC + frame source MAC + frame header uuid + frame header + seqNum + block information header randomXid + block information header seqNum + Keyword, and then calculate the CRC32 value of this array as the final signature information; the Keyword is a specially customized SOAM authentication key, and a key value is set by default for verification; if this value is inconsistent with the one used on the device side, the signature information verification will fail and the connection will fail.

5. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: In step S1, the device responds to the connection establishment request using a custom frame format. The following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_CONNECT; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the connection is established successfully, and other values ​​indicate failure.

6. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: The request message for releasing the device connection in step S1 uses a custom frame format. The following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_REQ; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: the UUID of the established connection, or a randomly generated UUID; The option field in the block information header is: TSC_SOAM_OPTION_REL_FORCE.

7. The method for realizing simple operation, maintenance and management functions based on host computer network management software according to claim 1, characterized in that: In step S1, the device responds to the release connection request using a custom frame format. The following are the parameter values ​​it uses: rpcType in the frame header: TSC_SOAM_GEN_RSP; opType in the frame header: TSC_SOAM_RELEASE; rpcUuid in the frame header: UUID carried in the request message; seqNum in the frame header: seqNum carried in the request message; Status in the frame header: returns information based on the processing result of the device. If it is TSC_SOAM_OK, it means the release is successful, and other values ​​indicate failure.

Images