JP5246812B2 - COMMUNICATION SYSTEM, CLIENT DEVICE, SERVER DEVICE, AND COMMUNICATION SETTING METHOD - Google Patents

Description

  The present invention relates to a communication system, a client device, a server device, and a communication setting method.

  In general, when a plurality of types of network devices are managed and set, the network configuration and status are displayed and the user performs a setting operation (for example, Patent Document 1 or Patent Document 2). When setting an Ether OAM-compatible device, it is necessary to set a wide variety of Ether OAM settings, and the maintenance person sets the setting according to the installation location. However, since the burden on the maintenance person increases, as a technique for facilitating the setting of Ether OAM, the server transmits setting information to the client in response to a request from the network device (client), and based on the setting information. Technology set by the client.

  A technique in which a server transmits setting information to a client will be described with reference to FIG.

  The communication system shown in FIG. 1 is constructed by Ethernet (registered trademark), and includes user network devices 11 and 15, bridges 12 and 13 of a carrier 2 that operates as a client, a bridge 14 of a carrier 1 that operates as a client, and a carrier. It is constructed by a management server 16 installed in one network.

  When the carrier 2 bridge 12 sets the maintenance domain of the carrier 1 and the carrier 2, a setting request is transmitted by the Ethernet frame to the management server 16 holding the maintenance domain setting information of the two carriers of the carrier 1 and the carrier 2. . The setting of the Ether OAM of the maintenance domain of the two carriers is executed by the Ethernet frame in response to the setting request. Further, in order to reach the management server 16 with the Ethernet frame transmitted by the carrier 2 bridge 12, the frame destination address is set to broadcast and transmitted. The transmitted Ethernet frame passes through the carrier 2 bridge 13 and the carrier 1 bridge 14 and reaches the management server 16 and the user network device 15.

JP 2004-102558 A Special table 2007-525105 gazette

  However, the above technique is not sufficient for setting Ether OAM. In Ether OAM, there is a case where information of a plurality of carriers is set for one port, and each piece of information is not managed by one management server, but should be managed by each carrier. It is. When managing by one management server, the management server must also hold information on a plurality of carriers and a plurality of users, and it is necessary to pass network information of the own carrier to other carriers. Therefore, there is a problem that it is not desirable from the viewpoint of security.

  Therefore, the problem to be solved by the present invention is to provide a technique capable of performing desirable management settings from the viewpoint of security.

A first invention for solving the above-mentioned problem is a communication system, and transmits a setting request in which a maintenance domain level of a carrier for setting Ether OAM (Operations, Administration, Maintenance) and a MAC address of the own device is transmitted. In addition, a client device that sets the Ether OAM of its own device based on setting information transmitted in response to the setting request and a maintenance domain level of the transmitted setting request are provided for each maintenance domain of each carrier. If it is the same as the Maintenance Domain Level of the own device, the setting information corresponding to the device is obtained based on the MAC address of the transmitted setting request. And having a server device that transmitted to dress.

  A second invention for solving the above problem is a client device, which transmits a setting request in which a maintenance domain level of a carrier that sets Ether OAM (Operations, Administration, Maintenance) and a MAC address of the own device are described. Then, the Ether OAM of the own apparatus is set based on the setting information transmitted in response to the setting request.

  A third invention for solving the above-described problem is a server device, which is provided for each maintenance domain of each carrier, and sets a carrier OAM (Operations, Administration, Maintenance) transmitted from a client device. When the Maintenance Domain Level of the setting request that describes the Maintenance Domain Level and the MAC address of the client device is the same as the Maintenance Domain Level of the own device, it corresponds to the device based on the MAC address of the transmitted setting request The setting information is transmitted to the MAC address.

  A fourth invention for solving the above-mentioned problem is a communication setting method, and a setting request in which a maintenance domain level of a carrier that sets Ether OAM (Operations, Administration, Maintenance) and a MAC address of the own device is described. When the setting request transmission step transmitted by the client device and the server device provided for each maintenance domain of each carrier, the maintenance domain level of the transmitted setting request is the same as the maintenance domain level of the own device. A setting information transmission step for transmitting setting information corresponding to the apparatus to the MAC address based on the MAC address of the transmitted setting request, and the transmission And having a setting step of setting the Ether OAM client device based on the setting information.

  According to the present invention, it is not necessary to pass network information to another carrier, which is desirable from the viewpoint of security.

FIG. 1 is a diagram for explaining a technique related to the present application. FIG. 2 is a schematic diagram of the communication system according to the first embodiment. FIG. 3 is a block diagram of the client device. FIG. 4 is a block diagram of the server device. FIG. 5 is a flow for explaining the operation. FIG. 6 is an example of a setting request Ether OAM frame format. FIG. 7 shows an example of a response Ether OAM frame format. FIG. 8 is an example of a management table. FIG. 9 is a schematic diagram of a communication system according to the second embodiment.

  In the present invention, a client device and a server device are configured to face each other via a network. Thereby, it is possible to easily execute the Ether OAM setting of the client device. The maintenance person sets all the MD levels of the carriers to which the Ether OAM is to be set for the client device by using the DIP switch.

  The DIP switch can be set to ON / OFF of 8 levels from 0 to 7 of MD Level. Then, a push button that gives an opportunity to start the setting is set. When the push button is turned on, the client device reads the setting of the dip switch, generates an MD Level setting request Ether OAM frame in which the dip switch is turned on, and sequentially transmits it to the server.

  On the other hand, when the server apparatus 4 receives the MD Level setting request Ether OAM frame of its own apparatus, the server apparatus 4 reads the setting information of the requested client from the client setting information storage unit held by the own apparatus. Then, the read Ether OAM setting information of the client is written in the response Ether OAM frame and transmitted to the client device.

  Here, the client apparatus holds the response Ether OAM frame from the server apparatus as the setting information of the own apparatus.

  The response Ether OAM frame is returned from all servers for each transmitted setting request Ether OAM. The client device operates according to IEEE Std 802.1ag-2007 or ITU-TY.1731 based on the held Ether OAM setting information.

  In order to specifically describe the features of the present invention, the following description is made with reference to the drawings.

  A first embodiment for carrying out the present invention will be described in detail with reference to the drawings.

  FIG. 2 shows a configuration example of the communication system of the present invention. The communication system of the present invention has a carrier 2 bridge (client device) 22, a carrier 2 bridge (server device) 23, and a carrier 1 bridge (server) 24, and operates as a maintenance association end point (hereinafter referred to as MEP). Show. It should be noted that the present invention relates to IEEE Std 802.1ag and ITU-T Y. 1731 is applicable.

  The communication system has a maintenance domain of a user maintenance domain, a carrier 1 maintenance domain, and a carrier 2 maintenance domain. The user maintenance domain is a maintenance domain between the user network devices 21 and 25. The carrier 1 maintenance domain is a maintenance domain between the carrier 2 bridge (client) 22 and the carrier 1 bridge (server) 24. The carrier 2 maintenance domain is a maintenance domain between the carrier 2 bridge (server) 23 and the carrier 1 bridge (server) 24. MD Level decreases in the order of User Maintenance Domain (MD Level = 7), Carrier 1 Maintenance Domain (MD Level = 4), and Carrier 2 Maintenance Domain (MD Level = 2).

  FIG. 3 is an example of a block diagram of the client, and FIG. 4 is an example of a block diagram of the server.

  First, the client device 3 will be described.

  The client apparatus 3 includes a Passive SAP unit 301, an Ether OAM multiplexing unit 302, an Active SAP 303, a provisioning control unit 304, an Ether OAM setting storage unit 305, an Ether OAM control unit 306, and an Ether OAM demultiplexing unit 307. , A dip switch 308 and a push button 309.

  The Passive SAP unit 301 receives a data frame and an Ether OAM frame (an unprocessed Ether OAM frame) that is not a management target of the own device. Also, a frame transmitted from the Ether OAM demultiplexing unit 307 whose Ether type is not Ether OAM is transmitted.

  The Ether OAM multiplexing unit 302 multiplexes the Ether OAM frame generated by the own apparatus on the frame received by the Passive SAP 301.

  The Active SAP 303 receives the data frame and the management target and unmanaged Ether OAM frames of the own device. Also, the Ether OAM frame multiplexed by the Ether OAM multiplexing unit 302 is transmitted.

  The provisioning control unit 304 sends a setting request Ether OAM frame to the Ether OAM multiplexing unit 302 when the push button 309 is pressed based on the MD Level set by the DIP switch 308. In addition, the provisioning control unit 304 stores the Ether OAM setting in the Ether OAM setting storage unit 305 based on the response Ether OAM frame containing the setting information from the Ether OAM control unit 306.

  Here, the Ether OAM frame generated by the provisioning control unit 304 will be described. FIG. 6 is an example of the format of the setting request Ether OAM frame. Here, an example using a VSM PDU defined in ITU-T Y.1731 is shown. Note that elements other than those shown below conform to ITU-T Y.1731.

  VSM PDUs are Destination address 601, Source address 602, Ether type 603, MD Level 604, Version 605, OpCode 606, Flag 607, TLV Offset 608, 6T, 609

  In Destination address 601, Multicast DA Class 1 is set. The setting of the dip switch 308 is read into “x” of 01-C2-00-00-3x of Multicast DA Class 1 and the value of MD Level is set.

  In the source address 602, the MAC address of the client device 3 is set.

  In MD Level 604, the MD Level value is set based on the setting of the DIP switch 308.

  OpCode 606 sets “51” for specifying the VSM.

  Version 605 is not used in the present invention. Further, since Flag 607, OUI 609, and SubOpCode 610 are not used in the present invention, '0' is set. The PDU 611 is not used in the present invention, but can be used as an identifier when a different Ether OAM is set for each port in an apparatus having a plurality of ports.

  The Ether OAM setting storage unit 305 stores the Ether OAM setting by the provisioning control unit 304.

  The Ether OAM control unit 306 reads the setting information (operation parameter) from the Ether OAM setting storage unit 305, and performs IEEE Std 802.1ag-2007 or ITU-T Y on the Ether OAM frame from the Ether OAM demultiplexing unit 307. The process based on .1731 is executed. The Ether OAM control unit 306 generates an Ether OAM frame and sends it to the Ether OAM multiplexing unit 302. Further, the received response Ether OAM frame is sent to the provisioning control unit 304.

  The Ether OAM demultiplexing / multiplexing unit 307 confirms the Ether type of the Ethernet frame from the Active SAP 303, sends a frame whose Ether type is the Ether OAM to the Ether OAM control unit 306, and sends other frames to the Passive SAP 301.

  The dip switch 308 is used when setting the MD Level where the own apparatus is installed.

  The push button 309 gives an opportunity to transmit the setting request Ether OAM frame.

  Next, the server device 4 will be described.

  The server device 4 includes a Passive SAP unit 401, an Ether OAM multiplexing unit 402, an Active SAP 403, a provisioning control unit 404, a client setting storage unit 405, an Ether OAM control unit 406, an EtherOAM demultiplexing unit 407, a management A user interface 408 and an Ether OAM setting storage unit 409.

  The Passive SAP unit 401 receives a data frame and an Ether OAM frame that is not managed by the own device, that is, is not processed by the own device.

  The Ether OAM multiplexing unit 402 multiplexes the Ether OAM frame generated by the own apparatus on the frame transmitted from the Passive SAP 401.

  The Active SAP 403 receives a data frame and an Ether OAM frame that is a management target and a non-management target in the self apparatus.

  The provisioning control unit 404 reads setting information from the client setting storage unit 405 based on the MAC Address information of the setting request Ether OAM frame from the Ether OAM control unit 406. Then, the response Ether OAM frame containing the setting information is sent to the Ether OAM multiplexing unit 402.

  FIG. 7 shows an example of a response Ether OAM frame format. Here, an example using a VSR PDU defined in ITU-TY.1731 is shown. The elements other than the following shall comply with ITU-T Y.1731.

  VSR PDU consists of Destination address 701, Source address 702, Ether type 703, MD Level 704, Version 705, OpCode 706, Flag 707, TLV Offset 708, UL 709, TLV Offset 708, UL 709

  In the destination address 701, the source address of the setting request Ether OAM is set.

  In the source address 702, the MAC address of the server device 4 is set.

  In MD Level 704, the value of MD Level is set based on the setting read from Ether OAM setting storage unit 409.

  In OpCode 706, “50” for specifying the VSR is set.

  Since FLAG 707, OUI 709, and SubOpCode 710 are not used in the present invention, '0' is set. Further, the TLV Offset 708, the End TLV 712, and the FCS 713 are not used in the present invention, and thus the description thereof is omitted.

  Setting information read from the client setting storage unit 405 is set in the PDU 711. The client device 3 sets its own Ether OAM using this information.

  The client setting storage unit 405 stores Ether OAM information set in the client via the administrator interface unit 408.

  FIG. 8 shows a management table format example of the client setting storage unit 405. This management table is set by the administrator via the administrator interface 408. The management table manages the MAC address of the client device and the Ether OAM setting in association with each other. The Ether OAM setting item manages items that can be set in IEEE Std 802.1ag-2007 and ITU-T Y.1731, such as Maintenance Domain name and CCM Interval.

  The Ether OAM control unit 406 reads out parameters that the device itself should operate from the Ether OAM setting storage unit 409. Then, based on IEEE Std 802.1ag-2007, the Ether OAM frame received from the Ether OAM demultiplexing unit 407 is processed. The Ether OAM control unit 406 also has a function of generating an Ether OAM frame and transmitting it to the Ether OAM multiplexing unit 402, and transmitting a setting request Ether OAM frame to the provisioning control unit 404.

  The Ether OAM demultiplexing unit 407 confirms the Ether type of the Ethernet frame received from the Active SAP 403, transmits a frame whose Ether type is the Ether OAM to the Ether OAM control unit 406, and transmits other frames to the Passive SAP 401.

  The Ether OAM setting storage unit 409 stores the Ether OAM setting of its own device.

  The administrator interface 408 writes settings to the client setting storage unit 405 and the EtherOAM setting storage unit 409.

  Next, a frame flow will be described with reference to FIG. In the following description, it is assumed that the dip switch 308 has already been set by the maintenance person.

  When the push button 309 is pressed, the carrier 2 bridge (client) 22 transmits a setting request Ether OAM (MD Level = 14). Since the MD level of this Ether OAM frame is '4' and the carrier 2 maintenance domain is MD Level 2, the carrier 2 bridge (server) 23 follows the operation of IEEE Std 802.1ag-2007 or ITU-T Y.1731. The Ether OAM frame is transferred and transmitted without terminating itself.

  The carrier 1 bridge (server) 24 that has received the setting request Ether OAM (MD Level = 4) terminates in its own device without transmitting to the user network device 25 because this frame is the same as its own MD Level. Then, referring to the client setting storage unit 405, a response Ether OAM (MD Level = 4) in which the setting of the carrier 2 bridge (client) 22 is entered is transmitted to the carrier 2 bridge (client) 22.

  The carrier 2 bridge (client) 22 transmits a setting request Ether OAM (MD Level = 2) following transmission of the setting request Ether OAM (MD Level = 4).

  The carrier 2 bridge (server) 23 that has received the setting request Ether OAM (MD Level = 2) has the same frame as its own MD Level, and therefore does not transmit the frame to the carrier 1 bridge (server) 24. Terminate. Then, referring to the client setting storage unit 405, a response Ether OAM (MD Level = 2) containing setting information of the carrier 2 bridge (client) 22 is transmitted to the carrier 2 bridge (client) 22.

  The carrier 2 bridge client 22 that has received the response Ether OAM (MD Level = 4) and the response Ether OAM (MD Level = 2) determines whether IEEE Std 802.1ag-2007 or ITU-TY. Set according to 1731 and operate.

  Next, the operation of the present invention will be described. Hereinafter, an operation example when the client device 3 and the server device 4 are installed in a network configuration as shown in FIG. 2 will be described. FIG. 5 is a flowchart showing an operation in which the server apparatus 4 responds to a request from the client apparatus 3 and the client apparatus 3 executes Ether OAM setting. A carrier 2 bridge (client) 22 shown in FIG. 5 shows the client device 3 shown in FIG. 3, and a carrier 2 bridge (server) 23 and a carrier 1 bridge (server) 24 show the server device 4 shown in FIG. In the following description, it is assumed that the dip switch 308 has already been set as MD Level = 4, 2 by the maintenance person.

  First, the carrier 2 bridge (client) 22 confirms the push of the push button 309 by the maintenance person (step 501).

  When the push button 309 is pressed, the setting of the dip switch 308 is confirmed. If none of the dip switches are set, a transition is made to the start state. If the DIP switch 308 is set (step 502), a setting request Ether OAM is generated. Here, since the setting of the dip switch 308 is MD Level = 4, 2, a setting request Ether OAM of MD Level = 4 is first transmitted (step 503). Subsequently, a setting request Ether OAM with MD Level = 2 is transmitted (step 504). After transmitting the setting request Ether OAM, a response Ether OAM waiting timer is started (step 505).

The carrier 2 bridge (server) 23 and the carrier 1 bridge (server) 24 confirm the MD Level of the setting request Ether OAM and the MD Level of the own device, and send the same MD Level setting request Ether OAM as the MD Level of the own device. Receive. Here, the carrier 2 bridge (server) 23 receives the setting request Ether OAM of MD Level = 2 (step 510). On the other hand, the carrier 1 bridge (server) 24 receives the setting request Ether OAM of MD Level = 4 (step 514).

  Using the MAC address described in the Source MAC address of the received setting request Ether OAM frame, the MAC address is searched from the client setting storage unit 405 (steps 511 and 515). If the MAC address cannot be searched, the process proceeds to start.

  On the other hand, if the MAC address can be retrieved, the Ether OAM setting information associated with the MAC address is read, and a response frame describing the read setting information is generated (steps 512 and 516).

  The destination of the generated response frame is set to the MAC address described in the source MAC address of the setting request Ether OAM frame, and transmitted to the carrier 2 bridge (client) 22 that is the transmission source of the setting request Ether OAM (step) 513, 517).

  The carrier 2 bridge (client) 22 that has received the response Ether OAM from the carrier 2 bridge (server 23) stores the setting information described in the received frame in the Ether OAM setting storage unit 305 (step 506). Similarly, the carrier 2 bridge (client) 22 that has received the response Ether OAM from the carrier 1 bridge (server) 24 stores the setting information described in the received frame in the Ether OAM setting storage unit 305 (step 506). ).

  It is confirmed whether or not all the response Ether OAM to the setting request Ether OAM has been received (step 508). If the response Ether OAM to the setting request Ether OAM cannot be received, that is, if the timer set in step 505 has expired, the process proceeds to start.

  On the other hand, when all of the responses Ether OAM to the setting request Ether OAM have been received, the operation of Ether OAM is started with the value stored in the Ether OAM setting storage unit 305 (step 509).

  According to the present invention, since the management server is configured for each carrier, it is not necessary to pass network information to other carriers, which is desirable from the viewpoint of security.

  Further, in the installation work at the site, the maintenance person can easily set by operating the dip switch, the push button, etc. without operating the command interface or the graphic interface and inputting the settings one by one. In addition, setting errors caused by maintenance personnel can be reduced thereby, so that occurrence of network failures due to setting errors can be reduced.

  In addition, since it is not necessary to set the setting request frame transmitted from the client device to the management server as a broadcast frame, it does not reach a device installed in a user network that does not require the broadcast frame.

<Second Embodiment>
The configuration of the second embodiment of the present invention is shown in FIG. In addition, the same number is attached | subjected about the structure similar to the said embodiment, The detailed description is abbreviate | omitted.

  The configuration of this embodiment includes user network devices 21 and 25, carrier 2 bridges (clients) 22 and 93, carrier 2 bridge (server) 23, and carrier 1 bridge (server) 24. In the present embodiment, the carrier 2 bridge (client) 93 operates as a maintenance domain intermediate point (hereinafter referred to as MIP). Therefore, this is an embodiment in which the carrier 2 bridge (client) 93 performs the Ether OAM setting. Further, in the present embodiment, the client device 3 needs to select whether to output the setting request Ether OAM frame to the Active SAP side or to the Passive SAP side. This is to determine which interface side the server apparatus 4 is connected to, and is set by a maintenance person using the DIP switch 308 or the like.

  The frame flow of the present embodiment will be described with reference to FIG. In the following description, it is assumed that the dip switch has already been set by the maintenance person.

  When the push button is pressed, the carrier 2 bridge (client) 93 transmits a setting request Ether OAM (MD Level = 4). Since the Ether OAM frame is MD Level 4 and the Carrier 2 Maintenance Domain is MD Level 2, the carrier 2 bridge (server) 23 transmits the Ether OAM frame without terminating itself.

  The carrier 1 bridge (server) 24 that has received the setting request Ether OAM (MD Level 4) terminates itself without being transmitted to the user network device 25 because this frame is the same as its own MD Level. Then, referring to the client setting storage unit 405, a response Ether OAM (MD Level = 4) in which the setting of the carrier 2 bridge (client) 93 is entered is transmitted to the carrier 2 bridge (client) 93.

  The carrier 2 bridge (client) 93 transmits a setting request Ether OAM (MD Level = 2) following transmission of the setting request Ether OAM (MD Level = 4).

  The carrier 2 bridge (server) 23 that has received the setting request Ether OAM (MD Level = 2) terminates itself without being transmitted to the carrier 1 bridge (server) 24 because this frame is the same as its own MD Level. . Then, referring to the client setting storage unit 405, a response Ether OAM (MD Level = 2) in which the setting of the carrier 2 bridge (client) 93 is entered is transmitted to the carrier 2 bridge (client) 93.

  The carrier 2 bridge client 93 that has received the response Ether OAM (MD Level = 4) and the response Ether OAM (MD Level = 2) determines whether IEEE Std 802.1ag-2007 or ITU-T.Y. 1731.

  Since the operation of each component of the client device 3 and the server device 4 of the present embodiment is the same as that of the first embodiment, detailed description thereof is omitted.

  It should be noted that the device of the present invention described above can be configured by hardware, as is apparent from the above description, but can also be realized by a computer program. In this case, functions and operations similar to those of the above-described embodiment are realized by a processor that operates according to a program stored in the program memory. Note that only a part of the functions of the above-described embodiment can be realized by a computer program.

  Although the present invention has been described with reference to the embodiments and examples, the present invention is not necessarily limited to the above-described embodiments and examples, and various modifications can be made within the scope of the technical idea. I can do it.

301 Passive SAP unit 302 Ether OAM multiplexing unit 303 Active SAP
304 Provisioning control unit 305 Ether OAM setting storage unit 306 Ether OAM control unit 307 Ether OAM demultiplexing unit 308 Dip switch 309 Push button 401 Passive SAP
402 Ether OAM Multiplexer 403 Active SAP
404 Provisioning control unit 405 Client setting storage unit 406 Ether OAM control unit 407 Ether OAM demultiplexing unit 408 Administrator interface 409 Ether OAM setting storage unit

Claims (7)

A communication system,
A setting request in which the maintenance domain level of the carrier for setting Ether OAM (Operations, Administration, Maintenance) and the MAC address of the own device are transmitted, and the own device is based on the setting information transmitted in response to the setting request. A client device for setting the Ether OAM of
Provided for each maintenance domain of each carrier, and corresponding to the device based on the MAC address of the transmitted configuration request when the maintenance domain level of the transmitted configuration request is the same as the maintenance domain level of the own device And a server device that transmits the set information to the MAC address.   2. The communication system according to claim 1, wherein the server device transfers the received setting request when a maintenance domain level of the transmitted setting request is not the same as the maintenance domain level of the own device. A client device,
A setting request in which the maintenance domain level of the carrier for setting Ether OAM (Operations, Administration, Maintenance) and the MAC address of the own device are transmitted, and the own device is based on the setting information transmitted in response to the setting request. A client apparatus characterized by setting an Ether OAM. A server device,
Provided for each maintenance domain of each carrier, and sent from the client device, the maintenance request's MainLevene level that describes the maintenance domain level of the carrier that sets Ether OAM (Operations, Administration, Maintenance) and the MAC address of the client device Is the same as the Maintenance Domain Level of its own device, the setting information corresponding to the device is transmitted to the MAC address based on the MAC address of the transmitted setting request.   The server apparatus according to claim 4, wherein the received setting request is transferred when a maintenance domain level of the transmitted setting request is not the same as a maintenance domain level of the own apparatus. A communication setting method,
A setting request transmission step in which the client apparatus transmits a setting request in which the maintenance domain level of the carrier for setting Ether OAM (Operations, Administration, Maintenance) and the MAC address of the own apparatus are transmitted;
The server device provided for each maintenance domain of each carrier is based on the MAC address of the transmitted configuration request when the maintenance domain level of the transmitted configuration request is the same as its own maintenance domain level. A setting information transmitting step for transmitting setting information corresponding to the device to the MAC address; a setting step for setting the Ether OAM of the client device based on the transmitted setting information;
A communication setting method characterized by comprising:   The communication according to claim 6, wherein the received setting request is transferred when the maintenance domain level of the transmitted setting request is not the same as the maintenance domain level of the server apparatus that has received the setting request. Setting method.

Images