CN110971455A - Method for realizing FC node automatic configuration - Google Patents

Method for realizing FC node automatic configuration Download PDF

Info

Publication number
CN110971455A
CN110971455A CN201911134462.1A CN201911134462A CN110971455A CN 110971455 A CN110971455 A CN 110971455A CN 201911134462 A CN201911134462 A CN 201911134462A CN 110971455 A CN110971455 A CN 110971455A
Authority
CN
China
Prior art keywords
message
port
node
messages
multicast
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201911134462.1A
Other languages
Chinese (zh)
Other versions
CN110971455B (en
Inventor
杜建华
李键
杨明伟
胡靖宇
史亭文
赵琳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xian Aeronautics Computing Technique Research Institute of AVIC
Original Assignee
Xian Aeronautics Computing Technique Research Institute of AVIC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Xian Aeronautics Computing Technique Research Institute of AVIC filed Critical Xian Aeronautics Computing Technique Research Institute of AVIC
Priority to CN201911134462.1A priority Critical patent/CN110971455B/en
Publication of CN110971455A publication Critical patent/CN110971455A/en
Application granted granted Critical
Publication of CN110971455B publication Critical patent/CN110971455B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Abstract

The invention belongs to the field of avionics system airborne networks, and discloses a method for automatically generating and configuring FC (fiber Channel, FC for short) node configuration data. The invention provides an FC node port configuration table automatic configuration mechanism, an FC node sending communication table automatic configuration mechanism and an FC node receiving communication table automatic configuration mechanism. Aiming at the FC network, a method for automatically generating and configuring FC node configuration data is provided. According to the invention, the FC node automatically generates the configuration data, so that a large amount of upgrade and maintenance of the configuration data of the external FC node are avoided, a special configuration tool and a loading tool are not needed for upgrade and maintenance, the labor cost and the research and development cost are saved, the research and development efficiency is improved, and the management and maintenance of the external technical state of the product are reduced.

Description

Method for realizing FC node automatic configuration
Technical Field
The invention belongs to the field of avionics system airborne networks, and relates to a method for automatically generating and configuring FC (fiber Channel, FC for short) node configuration data.
Background
The avionics system onboard communication network of an existing aircraft model employs an FC switched network. In an on-board network communication system, FC configuration data is the basis for mutual communication between FC node devices. The FC node configuration data includes a port configuration table, a send communication table, and a receive communication table for the existing aircraft model. The FC configuration data is generated by the FC configuration tool on the FC nodes loaded by the FC loading tool. As the user demands, the network size or the FC network topology change, the FC node configuration data also changes. In the existing airplane model, FC configuration data is generated through an FC configuration tool and is loaded on an FC node through an FC loading tool. The existing FC node configuration data generation method and the use mode have the following defects:
(1) the FC node configuration data is frequently upgraded and the workload is large, so that upgrading and maintenance of an external field are not facilitated. Since the user requirement or the FC network topology changes frequently, the FC node configuration data needs to be regenerated and upgraded, and the scale of the existing model network is about 60 nodes, the upgrade and maintenance workload is relatively large, corresponding test verification needs to be performed after upgrade, and the maintenance cost is relatively high.
(2) The domain of influence is large and the alteration is relatively difficult. The FC node configuration data requirement change (such as adding a configuration table, modifying the attribute of an entry, etc.) affects all nodes of the FC network, the FC configuration tool, the FC node software and application, etc., so the FC node configuration data requirement change is relatively difficult.
(3) The development cost is relatively high. Besides the great upgrade and maintenance of the FC node configuration data external field, the development and maintenance of the FC configuration tool and the loading tool also increase the research and development cost, and meanwhile, the maintenance and management of the full network FC configuration data state is also needed.
Disclosure of Invention
Aiming at the defects of the FC node configuration data research, development, use and maintenance modes, the invention provides an implementation method for automatic FC node configuration.
The technical scheme of the invention is as follows: the FC node port configuration table automatic generation mechanism is based on FC node sending communication tables and FC node receiving communication tables automatic generation, and after the FC node port configuration tables are generated, the FC node sending communication tables and the FC node receiving communication tables generate information such as port IDs based on the FC node port configuration tables. The FC node sending communication table generation strategy and the FC node receiving communication table generation strategy need to be kept consistent with each other, namely the multicast message generation strategy, the broadcast message generation strategy, the unicast message generation strategy and the multicast message generation strategy, the broadcast message generation strategy and the unicast message generation strategy of the sending communication table are consistent.
The FC node port configuration table automatic configuration mechanism comprises the following specific steps:
step 1, establishing a port configuration table generation strategy;
step 2, making a local port generation strategy;
step 3, if the network management information is needed, a network management information generation strategy is formulated;
step 4, if the clock management information is needed, a clock management information generation strategy is formulated;
and 5, automatically generating a port configuration table according to the port configuration table generation strategy.
In step 1, the port configuration table generation policy refers to port configuration table composition information. The composition information includes local port information, network management information, clock management information, and the like. The local port information is indispensable information of a port configuration table, and at least comprises a port ID, a port name and a network scale. The network management information at least comprises a network role, a WDT loading period and a WDT detection period. The clock management information includes at least a clock role and a clock synchronization period. The network scale refers to the number of nodes supported by the network, and the value range of N is [0x1,0xFF ]. The network specification number can be determined by setting the network scale node, and the sizes of an FC node port configuration table, an FC node sending communication table and an FC node receiving communication table are further determined.
In step 2, the local port generation policy refers to a method for generating port information.
The strategy generating method comprises a default mode, an interface mode and an automatic mode, wherein the automatic mode has priority. The default mode refers to that according to a certain convention, the use condition is generated, and default values are specified, such as protocol regulation, model experience, requirement regulation and the like. The interface mode is provided for the application in an API interface mode, and related information is set through the application. The dynamic mode means that the FC node first acquires a default port ID in a mode, and then sends a dynamic acquisition port request message to the network switch. And after the port corresponding to the switch receives the dynamic port acquiring request message, acquiring the switch domain ID and the port number. And distributing the port ID according to the switch domain ID and the port number, carrying the distributed port ID in a dynamic acquisition port response message, and sending the dynamic acquisition port response message to the FC node. And after receiving the dynamic port acquisition response message, the FC node acquires the allocated port ID and uses the port ID as the port ID in the FC node port information. The design ensures that the process does not need manual participation and is automatically generated.
When the local port generation policy is in a default mode, the method is applicable to point-to-point and self-loop structures, and the default of the port ID is 0x 010000.
In the step 3, the network management information generation policy refers to an automatic network management information generation method. The automatic generation method of the network management information combines an API interface mode with a default mode. The network role in the network management information adopts an API interface mode, and the application can set the network role of the FC node according to the requirement, and the mode is the same as the realization mode of the existing model. And a WDT loading period and a WDT detection period in the network management information adopt a default mode.
In the step 4, the clock management information generation policy refers to an automatic clock management information generation method. The automatic generation method of the clock management information combines an API interface mode with a default mode. The clock role in the clock management information adopts an API interface mode, and the application can set the clock role of the FC node according to the requirement, and the mode is the same as the realization mode of the existing model. The clock synchronization period in the clock management information adopts a default mode.
The step 5 of automatically generating the port configuration table according to the port configuration table generation policy means that the port configuration table of the FC node is generated according to the steps 1, 2, 3, and 4.
The FC node sends an automatic configuration mechanism of the communication table, and the specific steps are as follows:
step one, establishing a sending communication table generating strategy;
step two, if multicast messages are needed, a multicast message generation strategy is formulated;
step three, if the broadcast message is needed, a broadcast message generation strategy is formulated;
step four, if the unicast message is needed, a unicast message generation strategy is formulated;
and step five, automatically generating a sending communication table according to the sending communication table generating strategy.
In the first step, the sending communication table generating strategy refers to a sending communication table composition structure. The composition structure includes unicast messages, multicast messages and broadcast messages. The sending communication table at least comprises a message ID, a message name, a message length, a source port ID, a destination port ID and a message type.
The message ID is composed of the switch ID and port number of the source port ID, the switch ID and port number of the destination port ID, the message type, and the message number. The message type value includes unicast message, multicast message and broadcast message. The unicast message numbering rules are 3N +1, 3N +2 and 3N +3, which respectively represent unicast emergency messages, unicast event messages and unicast stream messages, wherein N is a numeric area of [0, N-1], and N network nodes are numbered and are a numeric area of [1, 0xFF ]. The broadcast message numbering rules are 3N +1, 3N +2, and 3N +3, which respectively represent broadcast emergency messages, broadcast event messages, and broadcast stream messages. The number of the broadcast messages is 3P, and P > is 0. The multicast message numbering rule is 3(N + i) +1, 3(N + i) +2, 3(N + i) +3, which respectively represents multicast emergency message, multicast event message, multicast stream message. The number of multicast messages is supported to be 3M, M > is 0, and the value range of i is [1, M ].
In the second step, the multicast message generation strategy refers to a method for generating multicast messages. The method for generating the multicast message is a default mode. The default mode is used for generating the number of multicast messages, the ID of the multicast messages, the ID of a source port, the ID of a destination port and the like by default. The number of the FC nodes multicast messages is 3M. The multicast destination port ID address assignment is consistent with the protocol specification.
In the third step, the broadcast message generation strategy refers to a method for generating broadcast messages. The broadcast message method is the default. The default mode is used for generating the number of broadcast messages, broadcast message ID, source port ID, destination port ID and the like by default. The number of pieces of the broadcast message of the FC node is 3P pieces, and P > is 0. The port ID address assignment for the broadcast destination is consistent with the protocol specification.
In the fourth step, the unicast message generation strategy refers to a method for generating unicast messages. The method of generating the unicast message is a default mode. The default mode is used for generating unicast message scale, unicast message number, unicast message ID, source port ID, destination port ID and the like by default. The unicast message scale defaults to full connectivity, i.e., communication can be performed between any two FC nodes. The number of unicast emergency messages between any two FC nodes is t, the number of unicast event messages is t, the number of unicast stream messages is t, and t > is 0.
And the step five of generating the sending communication table means that the sending communication table is automatically generated according to the step one, the step two, the step three and the step four.
The FC node receiving communication table automatic configuration mechanism comprises the following specific steps:
step A, formulating a receiving communication table generating strategy;
step B, if multicast information is needed, a multicast information generation strategy is formulated;
step C, if the broadcast message is needed, a broadcast message generation strategy is formulated;
step D, if the unicast message is needed, a unicast message generation strategy is formulated;
and E, automatically generating a receiving communication table according to the receiving communication table generation strategy.
In the step a, the receiving communication table generation policy refers to a receiving communication table composition structure. The composition structure includes unicast messages, multicast messages and broadcast messages. The receiving communication table at least comprises a message ID, a message name, a message length, a source port ID, a destination port ID and a message type. The message ID is composed of the switch ID and port number of the source port ID, the switch ID and port number of the destination port ID, and the message number. The unicast message numbering rules are 3N +1, 3N +2 and 3N +3, which respectively represent unicast emergency messages, unicast event messages and unicast stream messages, wherein N is a numeric area of [0, N-1], and N is a network port number with a numeric area of [0x1,0xFF ]. The broadcast message numbering rules are 3N +1, 3N +2, and 3N +3, which respectively represent broadcast emergency messages, broadcast event messages, and broadcast stream messages. The number of broadcast messages between any two nodes is 3P, and P > is 0. The multicast message numbering rule is 3(N + i) +1, 3(N + i) +2, 3(N + i) +3, which respectively represents multicast emergency message, multicast event message, multicast stream message. The number of multicast messages between any two nodes is 3M, M > is 0, and i < ═ M.
In step B, the multicast message generation strategy refers to a method for generating a multicast message. The method for generating the multicast message is a default mode. The default mode is used for generating the number of multicast messages, the ID of the multicast messages, the ID of a source port, the ID of a destination port and the like by default. The number of multicast messages between any two FC nodes is 3M. The multicast destination port ID address assignment is consistent with the protocol specification.
In the step C, the broadcast message generation policy refers to a method for generating a broadcast message. The broadcast message method is the default. The default mode is used for generating the number of broadcast messages, broadcast message ID, source port ID, destination port ID and the like by default. The number of broadcast messages between any two FC nodes is 3P, where P > is 0. The port ID address assignment for the broadcast destination is consistent with the protocol specification.
In the step D, the unicast message generation policy refers to a method for generating a unicast message. The method of generating the unicast message is a default mode. The default mode is used for generating unicast message scale, unicast message number, unicast message ID, source port ID, destination port ID and the like by default. The unicast message scale defaults to full connectivity, i.e., communication can be performed between any two FC nodes. The number of unicast entries between any two FC nodes is 3t, and t > is 0.
And E, automatically generating a receiving communication table means generating the receiving communication table according to the step A, the step B, the step C and the step D.
According to the invention, the FC node automatically generates the configuration data, so that a large amount of upgrade and maintenance of the configuration data of the external FC node are avoided, a special configuration tool and a loading tool are not needed for upgrade and maintenance, the labor cost and the research and development cost are saved, the research and development efficiency is improved, and the management and maintenance of the external technical state of the product are reduced.
Drawings
Fig. 1 is a flow chart of an automatic configuration mechanism of a port configuration table of an FC node.
Fig. 2 is a flow chart of an FC node sending communication table auto-configuration mechanism.
Fig. 3 is a flow chart of an FC node receive communication table auto-configuration mechanism.
Detailed Description
For a better understanding of the present invention, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
As shown in fig. 1, the automatic configuration mechanism of the FC node port configuration table of the present invention is as follows:
step 100, establishing a port configuration table generation strategy;
step 101, making a local port generation strategy;
step 102, if network management information is needed, a network management information generation strategy is formulated;
103, if the clock management information is needed, making a clock management information generation strategy;
and 104, automatically generating a port configuration table according to the port configuration table generation strategy.
In step 100, the port configuration table generation policy refers to the port configuration table composition information, as shown in table 1. The composition information includes local port information, network management information, clock management information, and the like. The local port information is indispensable information of a port configuration table, and at least comprises a port ID, a port name and a network scale. The network management information at least comprises a network role, a WDT loading period and a WDT detection period. The clock management information includes at least a clock role and a clock synchronization period. The network scale refers to the number of nodes supported by the network, and the value range of N is [0x1,0xFF ].
Table 1 port configuration table generation policy
Name of composition information Attribute configuration Recommending attributes Default attributes
Local port information Is configured with Is absolutely necessary Is configured with
Network management information Is configured with Optionally Is not configured
Clock management information Is configured with Optionally Is not configured
Other management information Is not configured Optionally Is not configured
In step 101, the local port generation policy refers to a method for generating port information.
The policy generation method includes a default mode, an interface mode and an automatic mode, and the automatic mode is prioritized as shown in table 2. The default mode refers to that according to a certain convention, the use condition is generated, and default values are specified, such as protocol regulation, model experience, requirement regulation and the like. The interface mode is provided for the application in an API interface mode, and related information is set through the application. The dynamic mode means that the FC node first acquires a default port ID in a mode, and then sends a dynamic acquisition port request message to the network switch. And after the port corresponding to the switch receives the dynamic port acquiring request message, acquiring the switch domain ID and the port number. And distributing the port ID according to the switch domain ID and the port number, carrying the distributed port ID in a dynamic acquisition port response message, and sending the dynamic acquisition port response message to the FC node. And after receiving the dynamic port acquisition response message, the FC node acquires the allocated port ID and uses the port ID as the port ID in the FC node port information. When the local port generation policy is in a default mode, the method is applicable to point-to-point and self-loop structures, and the default of the port ID is 0x 010000. The local port generates a policy as shown in table 3.
TABLE 2 Generation policy Table
Policy method Description of the invention Priority level Method Attribute
By default And setting attribute values according to convention to meet general requirements. Is low in Compatible with other modes
Interface mode And calling an API (application program interface) to set an attribute value to meet special requirements. In Compatible with other modes
Dynamic mode And obtaining the attribute value through a network to meet the requirements of the whole machine. Height of Compatible with other modes
TABLE 3 local Port information Generation policy
Figure BDA0002279212070000061
Figure BDA0002279212070000071
In the step 3, the network management information generation policy refers to an automatic network management information generation method, as shown in table 4. The automatic generation method of the network management information combines an API interface mode with a default mode. The network role in the network management information adopts an API interface mode, and the application can set the network role of the FC node according to the requirement, and the mode is the same as the realization mode of the existing model. And a WDT loading period and a WDT detection period in the network management information adopt a default mode.
Table 4 network management information generation policy
Policy method Network management information Application conditions
By default Generating network management information Self-looping joint test
Interface mode Setting network roles All scenes
In step 4, the clock management information generation policy refers to an automatic clock management information generation method, as shown in table 5. The automatic generation method of the clock management information combines an API interface mode with a default mode. The clock role in the clock management information adopts an API interface mode, and the application can set the clock role of the FC node according to the requirement, and the mode is the same as the realization mode of the existing model. The clock synchronization period in the clock management information adopts a default mode.
TABLE 5 clock management information Generation strategy
Policy method Network management information Application conditions
By default Generating clock management information Self-looping joint test
Interface mode Setting clock roles All scenes
As shown in fig. 2, the method of the present invention includes the following specific steps:
step 200, establishing a sending communication table generation strategy;
step 201, if multicast message is needed, a multicast message generation strategy is formulated;
step 202, if a broadcast message is needed, a broadcast message generation strategy is formulated;
step 203, if a unicast message is needed, a unicast message generation strategy is formulated;
and step 204, automatically generating a sending communication table according to the sending communication table generating strategy.
In step 200, the transmission communication table generation policy is a transmission communication table composition structure, as shown in table 6. The composition structure includes unicast messages, multicast messages and broadcast messages. The sending communication table at least comprises a message ID, a message name, a message length, a source port ID, a destination port ID and a message type.
Table 6 transmit communication table generation strategy
Composite structure Attribute configuration Recommending attributes Default attributes
Unicast messages Is configured with Is absolutely necessary Is configured with
Multicast messages Is configured with Optionally Is not configured
Broadcast messages Is configured with Optionally Is not configured
The message ID is composed of the switch ID and port number of the source port ID, the switch ID and port number of the destination port ID, the message type, and the message number. The message type value includes unicast message, multicast message and broadcast message. The unicast message numbering rules are 3N +1, 3N +2 and 3N +3, which respectively represent unicast emergency messages, unicast event messages and unicast stream messages, wherein N is a numeric area of [0, N-1], and N network nodes are numbered and are a numeric area of [1, 0xFF ]. The broadcast message numbering rules are 3N +1, 3N +2, and 3N +3, which respectively represent broadcast emergency messages, broadcast event messages, and broadcast stream messages. The number of the broadcast messages is 3P, and P > is 0. The multicast message numbering rule is 3(N + i) +1, 3(N + i) +2, 3(N + i) +3, which respectively represents multicast emergency message, multicast event message, multicast stream message. The number of multicast messages is supported to be 3M, M > is 0, and the value range of i is [1, M ]. Specific examples of N ═ 48, N ═ 1, P ═ 1, and M ═ 1, and port numbers of 0x010000 are shown in table 7. Specific examples of N ═ 48, N ═ 1, P ═ 1, and M ═ 1, and port numbers 0x01002F are shown in table 8.
Table 7 transmit traffic table for local port 0x010000
Figure BDA0002279212070000081
Figure BDA0002279212070000091
Table 8 transmit traffic table for local port 0x01002F
Figure BDA0002279212070000092
Figure BDA0002279212070000101
In step 201, the multicast message generation policy refers to a method for generating a multicast message. The method for generating multicast messages is a default mode, the number M of multicast messages defaults to 1, and specific embodiments are shown in table 7 and table 8. The default mode is used for generating the number of multicast messages, the ID of the multicast messages, the ID of a source port, the ID of a destination port and the like by default. The number of the FC nodes multicast messages is 3M. The multicast destination port ID address assignment is consistent with the protocol specification.
In step 202, the broadcast message generation policy refers to a method for generating a broadcast message. The broadcast message method is a default mode, the number P of broadcast messages defaults to 1, and specific embodiments are shown in table 7 and table 8. The default mode is used for generating the number of broadcast messages, broadcast message ID, source port ID, destination port ID and the like by default. The number of pieces of the broadcast message of the FC node is 3P pieces, and P > is 0. The port ID address assignment for the broadcast destination is consistent with the protocol specification.
In step 203, the unicast message generation policy refers to a method for generating a unicast message. The method of generating the unicast message is a default mode. The default mode is used for generating unicast message scale, unicast message number, unicast message ID, source port ID, destination port ID and the like by default. The unicast message scale defaults to full connectivity, i.e., communication can be performed between any two FC nodes. The number of unicast emergency messages between any two FC nodes is t, the number of unicast event messages is t, the number of unicast stream messages is t, and t > is 0. The unicast message scale defaults to full connectivity, the unicast message number t defaults to 1, and specific embodiments are shown in table 7 and table 8.
The step 204 of generating the transmission communication table means that the transmission communication table is automatically generated according to the steps 200, 201, 202 and 203.
The invention comprises an FC node receiving communication table automatic configuration mechanism, which comprises the following specific steps:
step 300, formulating a receiving communication table generating strategy;
step 301, if multicast message is needed, a multicast message generation strategy is formulated;
step 302, if a broadcast message is needed, a broadcast message generation strategy is formulated;
step 303, if a unicast message is needed, a unicast message generation strategy is formulated;
and step 304, automatically generating a receiving communication table according to the receiving communication table generating strategy.
In step 300, the receiving communication table generation policy refers to a receiving communication table composition structure. The composition structure includes unicast messages, multicast messages and broadcast messages. The receiving communication table at least comprises a message ID, a message name, a message length, a source port ID, a destination port ID and a message type. The message ID is composed of the switch ID and port number of the source port ID, the switch ID and port number of the destination port ID, and the message number. The unicast message numbering rules are 3N +1, 3N +2 and 3N +3, which respectively represent unicast emergency messages, unicast event messages and unicast stream messages, wherein N is a numeric area of [0, N-1], and N is a network port number with a numeric area of [0x1,0xFF ]. The broadcast message numbering rules are 3N +1, 3N +2, and 3N +3, which respectively represent broadcast emergency messages, broadcast event messages, and broadcast stream messages. The number of broadcast messages between any two nodes is 3P, and P > is 0. The multicast message numbering rule is 3(N + i) +1, 3(N + i) +2, 3(N + i) +3, which respectively represents multicast emergency message, multicast event message, multicast stream message. The number of multicast messages between any two nodes is 3M, M > is 0, and i < ═ M. Specific examples of N ═ 48, N ═ 0, P ═ 1, and M ═ 1, and port numbers of 0x010000 are shown in table 9. Specific examples of N ═ 48, N ═ 1, P ═ 1, and M ═ 1, and port numbers 0x01002F are shown in table 10.
Table 9 receive traffic table for local port 0x010000
Figure BDA0002279212070000111
Figure BDA0002279212070000121
Figure BDA0002279212070000131
Table 10 receive traffic table for local port 0x01002F
Figure BDA0002279212070000132
Figure BDA0002279212070000141
In step 301, the multicast message generation policy refers to a method for generating a multicast message. The method for generating the multicast message is a default mode. The default mode is used for generating the number of multicast messages, the ID of the multicast messages, the ID of a source port, the ID of a destination port and the like by default. The number of multicast messages between any two FC nodes is 3M. The multicast destination port ID address assignment is consistent with the protocol specification. The number of multicast messages between any two nodes is 3M, and M is a default value of 1, and specific embodiments are shown in table 9 and table 10.
In step 302, the broadcast message generation policy refers to a method for generating a broadcast message. The broadcast message method is the default. The default mode is used for generating the number of broadcast messages, broadcast message ID, source port ID, destination port ID and the like by default. The number of broadcast messages between any two FC nodes is 3P, where P > is 0. The port ID address assignment for the broadcast destination is consistent with the protocol specification. The number of broadcast messages between any two nodes is 3P, where P is default to 1, and the specific embodiment is shown in table 9 and table 10.
In step 303, the unicast message generation policy refers to a method for generating a unicast message. The method of generating the unicast message is a default mode. The default mode is used for generating unicast message scale, unicast message number, unicast message ID, source port ID, destination port ID and the like by default. The unicast message scale defaults to full connectivity, i.e., communication can be performed between any two FC nodes. The number of unicast entries between any two FC nodes is 3t, and t > is 0. The number of unicast messages between any two nodes is 3t, and the default value of t is 1, and specific embodiments are shown in table 9 and table 10.
The step 304 of automatically generating the received communication table means that the received communication table is generated according to the steps 300, 301, 302 and 303.
The FC node port configuration table automatic generation mechanism is based on FC node sending communication tables and FC node receiving communication tables automatic generation, and after the FC node port configuration tables are generated, the FC node sending communication tables and the FC node receiving communication tables generate information such as port IDs based on the FC node port configuration tables. The FC node sending communication table generation strategy and the FC node receiving communication table generation strategy need to be kept consistent with each other, namely the multicast message generation strategy, the broadcast message generation strategy, the unicast message generation strategy and the multicast message generation strategy, the broadcast message generation strategy and the unicast message generation strategy of the sending communication table are consistent.
According to the invention, the FC node automatically generates the configuration data, so that a large amount of upgrade and maintenance of the configuration data of the external FC node are avoided, a special configuration tool and a loading tool are not needed for upgrade and maintenance, the labor cost and the research and development cost are saved, the research and development efficiency is improved, and the management and maintenance of the external technical state of the product are reduced.

Claims (8)

1. A method for implementing FC node automatic configuration is characterized by comprising the following steps:
(1) an FC node port configuration table automatic configuration mechanism;
(2) the FC node sends an automatic configuration mechanism of a communication table;
(3) the FC node receives an automatic configuration mechanism of a communication table;
the FC node port configuration table automatic generation mechanism is based on FC node sending communication tables and FC node receiving communication tables automatic generation, and after the FC node port configuration tables are generated, the FC node sending communication tables and the FC node receiving communication tables generate information such as port IDs (identity) based on the FC node port configuration tables; the FC node sending communication table generation policy and the FC node receiving communication table generation policy need to be mutually consistent.
2. The method for implementing FC node auto-configuration according to claim 1, wherein the (1) FC node port configuration table auto-configuration mechanism specifically comprises the following steps:
step 1, establishing a port configuration table generation strategy;
step 2, making a local port generation strategy;
step 3, if the network management information is needed, a network management information generation strategy is formulated;
step 4, if the clock management information is needed, a clock management information generation strategy is formulated;
and 5, automatically generating a port configuration table according to the port configuration table generation strategy.
3. The method according to claim 1, wherein the FC node (2) sends an automatic configuration mechanism for the communication table, and the specific steps are as follows:
step one, establishing a sending communication table generating strategy;
step two, if multicast messages are needed, a multicast message generation strategy is formulated;
step three, if the broadcast message is needed, a broadcast message generation strategy is formulated;
step four, if the unicast message is needed, a unicast message generation strategy is formulated;
and step five, automatically generating a sending communication table according to the sending communication table generating strategy.
4. The method according to claim 1, wherein the FC node (3) receives a communication table auto-configuration mechanism, and comprises the following steps:
step A, formulating a receiving communication table generating strategy;
step B, if multicast information is needed, a multicast information generation strategy is formulated;
step C, if the broadcast message is needed, a broadcast message generation strategy is formulated;
step D, if the unicast message is needed, a unicast message generation strategy is formulated;
and E, automatically generating a receiving communication table according to the receiving communication table generation strategy.
5. A method as claimed in claim 2, wherein the method comprises: in step 1, the port configuration table generation policy refers to port configuration table composition information, where the composition information includes local port information, network management information, and clock management information, where the local port information is essential information of the port configuration table, and includes at least a port ID, a port name, and a network scale.
6. A method as claimed in claim 2, wherein the method comprises: the strategy generating method comprises a default mode, an interface mode and an automatic mode, wherein the automatic mode is prior; the network management information generation strategy refers to a network management information automatic generation method which combines an API (application programming interface) mode with a default mode; the clock management information generation strategy refers to an automatic clock management information generation method, and the automatic clock management information generation method adopts an API (application programming interface) mode and a default mode to be combined.
7. A method for implementing FC node auto-configuration as claimed in claim 3 or 4 wherein: the sending communication table generating strategy and the receiving communication table generating strategy refer to corresponding communication table composition structures, and the composition structures comprise unicast messages, multicast messages and broadcast messages; the communication table at least comprises a message ID, a message name, a message length, a source port ID, a destination port ID and a message type; the message ID is composed of the switch ID and the port number of the source port ID, the switch ID and the port number of the destination port ID, the message type and the message number; the message type value comprises a unicast message, a multicast message and a broadcast message; the unicast message numbering rules are 3N +1, 3N +2 and 3N +3, and respectively represent unicast emergency messages, unicast event messages and unicast stream messages, wherein the value range of N is [0, N-1], the number of the N network nodes is the value range of [1, 0xFF ]; the multicast message numbering rule is 3(N + i) +1, 3(N + i) +2, 3(N + i) +3, which respectively represents multicast emergency messages, multicast event messages and multicast stream messages, the number of multicast message pieces is supported to be 3M, M > is 0, and the value range of i is [1, M ]; the broadcast message numbering rules are 3N +1, 3N +2 and 3N +3, which respectively indicate broadcast emergency messages, broadcast event messages and broadcast stream messages, wherein the number of the broadcast messages is 3P, and P > is 0.
8. A method for implementing FC node auto-configuration as claimed in claim 3 or 4 wherein: in the FC node sending communication table automatic configuration mechanism and the FC node receiving communication table automatic configuration mechanism, a unicast message generation strategy refers to a unicast message generation method, the unicast message generation method is a default mode, the default mode is used for default generation of unicast message scale, the number of unicast message pieces, unicast message IDs, source port IDs and destination port IDs, the unicast message scale is default to be fully communicated, namely communication can be carried out between any two FC nodes, the number of unicast emergency messages between any two FC nodes is t, the number of unicast event messages is t, the number of unicast stream messages is t, and t > is 0; the multicast message generation strategy refers to a method for generating multicast messages, the method for generating multicast messages is a default mode, the default mode is used for generating the number of multicast messages in a default mode, the number of multicast messages is 3M, the source port ID, the destination port ID and the FC node multicast message number, and the address allocation of the multicast destination port ID is consistent with the protocol specification; the broadcast message generation strategy is a broadcast message generation method, the broadcast message generation method is a default mode, the default mode is used for generating the number of broadcast messages in a default mode, the number of the broadcast messages is 3P, the number of source port IDs, the number of destination port IDs and the number of FC node broadcast messages is 0, and the address allocation of the broadcast destination port IDs is consistent with the protocol specification.
CN201911134462.1A 2019-11-19 2019-11-19 Method for realizing FC node automatic configuration Active CN110971455B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911134462.1A CN110971455B (en) 2019-11-19 2019-11-19 Method for realizing FC node automatic configuration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911134462.1A CN110971455B (en) 2019-11-19 2019-11-19 Method for realizing FC node automatic configuration

Publications (2)

Publication Number Publication Date
CN110971455A true CN110971455A (en) 2020-04-07
CN110971455B CN110971455B (en) 2022-03-08

Family

ID=70030804

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911134462.1A Active CN110971455B (en) 2019-11-19 2019-11-19 Method for realizing FC node automatic configuration

Country Status (1)

Country Link
CN (1) CN110971455B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7184421B1 (en) * 2001-12-21 2007-02-27 Itt Manufacturing Enterprises, Inc. Method and apparatus for on demand multicast and unicast using controlled flood multicast communications
US7343622B1 (en) * 2000-04-27 2008-03-11 Raytheon Company Multi-level secure multi-processor computer architecture
CN105471654A (en) * 2015-12-09 2016-04-06 中国航空工业集团公司西安航空计算技术研究所 FC network based configuration data automatic uploading method
CN106452918A (en) * 2016-11-23 2017-02-22 北京润科通用技术有限公司 Communication method and system for avionics network system
CN106685733A (en) * 2017-01-24 2017-05-17 北京国科天迅科技有限公司 FC-AE-1553 network rapid configuration and automatic testing method
CN106850371A (en) * 2017-01-24 2017-06-13 北京国科天迅科技有限公司 A kind of network systems of bus-type FC AE 1553 and data is activation and acquisition method
CN109672632A (en) * 2018-12-25 2019-04-23 上海赛治信息技术有限公司 FC-AE-ASM Data Communication in Computer Networks method and system
CN110166857A (en) * 2019-05-09 2019-08-23 中国航空工业集团公司西安航空计算技术研究所 A kind of implementation method of fibre channel media dynamic configuration
CN110943856A (en) * 2019-11-19 2020-03-31 中国航空工业集团公司西安航空计算技术研究所 Large-queue message transmission independence realization method based on fiber channel

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7343622B1 (en) * 2000-04-27 2008-03-11 Raytheon Company Multi-level secure multi-processor computer architecture
US7184421B1 (en) * 2001-12-21 2007-02-27 Itt Manufacturing Enterprises, Inc. Method and apparatus for on demand multicast and unicast using controlled flood multicast communications
CN105471654A (en) * 2015-12-09 2016-04-06 中国航空工业集团公司西安航空计算技术研究所 FC network based configuration data automatic uploading method
CN106452918A (en) * 2016-11-23 2017-02-22 北京润科通用技术有限公司 Communication method and system for avionics network system
CN106685733A (en) * 2017-01-24 2017-05-17 北京国科天迅科技有限公司 FC-AE-1553 network rapid configuration and automatic testing method
CN106850371A (en) * 2017-01-24 2017-06-13 北京国科天迅科技有限公司 A kind of network systems of bus-type FC AE 1553 and data is activation and acquisition method
CN109672632A (en) * 2018-12-25 2019-04-23 上海赛治信息技术有限公司 FC-AE-ASM Data Communication in Computer Networks method and system
CN110166857A (en) * 2019-05-09 2019-08-23 中国航空工业集团公司西安航空计算技术研究所 A kind of implementation method of fibre channel media dynamic configuration
CN110943856A (en) * 2019-11-19 2020-03-31 中国航空工业集团公司西安航空计算技术研究所 Large-queue message transmission independence realization method based on fiber channel

Also Published As

Publication number Publication date
CN110971455B (en) 2022-03-08

Similar Documents

Publication Publication Date Title
US8738802B2 (en) Forwarding traffic flow in intelligent resilient framework system
CN105871641B (en) A kind of data capture method based on cloud
CN103379184B (en) The method and system of Network access
CN110166857B (en) Method for realizing dynamic configuration of fiber channel switch
US20040213230A1 (en) Data matrix method and system for distribution of data
CN109756559A (en) The building and application method of Embedded airborne system distributed data distribution service
CN111106988B (en) Bus message time-sharing scheduling method and system
WO2020108160A1 (en) Rtps acceleration method, node and system of dds network
CN106713010B (en) A kind of communication means and system of avionics network system
CN110971455B (en) Method for realizing FC node automatic configuration
CN102256211A (en) Group-based method and system for application realization of M2M terminal
CN111010353A (en) Self-adaptive carefree network implementation method based on optical fiber channel
CN101115001B (en) Host computer of ADSL router and PVC dynamic binding method
CN102448120A (en) Multipath load sharing method and device
CN111447126B (en) Ethernet bus communication method, device, robot, equipment and computer readable storage medium
CN110830295B (en) Equipment management method and system
CN104244230B (en) The cast communication implementation method of next generation wireless network
CN112583676B (en) Information transmission method
CN109918742B (en) Data distribution and management method based on simulation system
CN109412868B (en) Flight simulator network communication method based on dynamic interface
CN102882799B (en) The controllable clustered deploy(ment) configuration System and method for of flow
CN112654091A (en) Cluster docking resource allocation method and system
CN111080228A (en) Intelligent business information management system for airline company
CN110943856A (en) Large-queue message transmission independence realization method based on fiber channel
CN100379206C (en) Method for realizing distributed collocation in communication device management group

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant