{"id":6383,"date":"2026-05-04T12:10:36","date_gmt":"2026-05-04T12:10:36","guid":{"rendered":"http:\/\/docs.connexite.co.uk\/index.php\/docs\/connexite-documentation\/synapse-web-ui-documentation\/web-configuration\/"},"modified":"2026-05-04T12:19:10","modified_gmt":"2026-05-04T12:19:10","slug":"web-configuration","status":"publish","type":"docs","link":"https:\/\/docs.connexite.co.uk\/index.php\/docs\/network\/synapse-web-ui-documentation\/web-configuration\/","title":{"rendered":"Configuration"},"content":{"rendered":"

VLAN<\/h2>\n

3.1.1 Introduction Ethernet is a network technology based on the Carrier Sense Multiple Access\/Collision Detect (CSMA\/CD) mechanism. As the medium is shared, collisions and excessive broadcasts are common on an Ethernet. To address the issue, virtual LAN (VLAN) was introduced. The idea is to break a LAN down into separate VLANs, that is, Layer 2 broadcast domains whereby frames are switched between ports assigned to the same VLAN. VLANs are isolated from each other at Layer 2. A VLAN is a bridging domain, and ll broadcast traffic is contained within it, as shown in Figure 3-1.<\/p>\n

\"A
Figure 3-1: A VLAN diagram<\/figcaption><\/figure>\n

A VLAN is logically divided on an organizational basis rather than on a physical basis. For example, all workstations and servers used by a particular workgroup can be connected to the same LAN, regardless of their physical locations. VLAN technology delivers the following benefits:<\/p>\n

    \n
  • Confining broadcast traffic within individual VLANs. This reduces bandwidth waste and improves network performance.<\/li>\n
  • Improving LAN security. By assigning user groups to different VLANs, you can isolate them at Layer 2. For hosts in different VLANs to communicate, routers or Layer 3 switches are required.<\/li>\n
  • Flexible virtual workgroup creation. As users from the same workgroup can be assigned to the same VLAN regardless of their physical locations, network construction and maintenance is much easier and more flexible.<\/li>\n<\/ul>\n

    You can create VLANs based on:<\/p>\n

      \n
    • Port<\/li>\n
    • MAC address<\/li>\n
    • Protocol<\/li>\n
    • IP subnet<\/li>\n
    • Policy<\/li>\n
    • Other criteria<\/li>\n<\/ul>\n

      Because the Web interface is available only for port-based VLANs, this chapter introduces only port-based VLANs. 3.1.1.1 VLAN Mode Depending on the tag handling mode, the VLAN Mode of a port can be one of the following three:<\/p>\n

        \n
      • Access \uff1a<\/li>\n<\/ul>\n

        An access port belongs to only one VLAN and usually connects to a user device.<\/p>\n

          \n
        • Trunk \uff1a<\/li>\n<\/ul>\n

          A trunk port can join multiple VLANs to receive and send traffic for them. It usually connects to a network device.<\/p>\n

            \n
          • Hybrid \uff1a<\/li>\n<\/ul>\n

            A hybrid port can join multiple VLANs to receive and send traffic for them. It can connect either a user device or a network device.<\/p>\n

            A hybrid port is different from a trunk port in that:<\/p>\n

              \n
            • A hybrid port allows traffic of multiple VLANs to pass through untagged.<\/li>\n
            • A trunk port allows only traffic of the default VLAN to pass through untagged.<\/li>\n<\/ul>\n

              3.1.1.2 Port link type<\/p>\n

              By default, VLAN 1 is the default VLAN for all ports. However, you can change the default VLAN for a port as required. When doing that, follow these guidelines:<\/p>\n

                \n
              • Because an access port can join only one VLAN, its default VLAN is the VLAN to which it belongs and cannot be configured.<\/li>\n
              • Because a trunk or hybrid port can join multiple VLANs, you can configure a default VLAN for the port.<\/li>\n<\/ul>\n

                3.1.1.3 Frame handling methods<\/p>\n

                Table 3-1: A port configured with a default VLAN handles a frame as follows:<\/strong><\/p>\n

                \n\n\n\n\n\n\n\n\n\n\n\n\n
                Port type<\/th>\nActions (in the inbound direction)<\/th>\n<\/tr>\n
                Actions (in the outbound direction)<\/td>\n<\/tr>\n
                Untagged frame<\/td>\nTag the frame with the default VLAN tag.<\/td>\n<\/tr>\n
                \u2022 Receive the frame if its VLAN ID is the same as the default VLAN ID<\/td>\n\u2022 Drop the frame if its VLAN ID is different from the default VLAN ID.<\/td>\n<\/tr>\n
                Remove the default VLAN tag and send the frame.<\/td>\n<\/tr>\n
                Trunk<\/td>\nCheck whether the default VLAN is carried on the port\uff1a<\/td>\n<\/tr>\n
                \u2022 If yes, tag the frame with the default VLAN tag.<\/td>\n\u2022 If not, drop the frame.<\/td>\n<\/tr>\n
                \u2022 Receive the frame if its VLAN is carried on the port.<\/td>\n\u2022 Drop the frame if its VLAN is not carried on the port.<\/td>\n<\/tr>\n
                \u2022 Remove the tag and send the frame if the frame Carries the default VLAN tag.<\/td>\n\u2022 Send the frame without removing the tag if its VLAN is carried on the port but is different from the default one.<\/td>\n<\/tr>\n
                Hybrid<\/td>\nSend the frame if its VLAN is carried on the port. The frame is sent with the VLAN tag removed or intact depending on your configuration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                3.1.2 Configuring VLAN 3.1.2.1 Creating VLAN<\/p>\n

                  \n
                1. Select Configuration > VLAN in the navigation area. The system automatically enters the VLAN page as shown in Figure 3-2. Table 3-2 describes the configuration items of creating a VLAN.<\/li>\n<\/ol>\n
                  \"VLAN
                  Figure 3-2: VLAN configuration page<\/figcaption><\/figure>\n

                  Table 3-2: Vlan configuration items<\/strong><\/p>\n

                  \n\n\n\n\n\n\n\n\n\n
                  Item<\/th>\nDescription<\/th>\n<\/tr>\n
                  ID<\/td>\nThis field displays the ID of the VLAN<\/td>\n<\/tr>\n
                  name<\/td>\nBy default, the description string of a VLAN is its VLAN ID, such as VLAN 0002.<\/td>\n<\/tr>\n
                  Members<\/td>\nIndicates that the port sends the traffic of the VLAN without removing the VLAN tag.<\/td>\n<\/tr>\n
                  Edit<\/td>\nClick to enter the VLAN editing page<\/td>\n<\/tr>\n
                  Add<\/td>\nClick to enter the VLAN adding page<\/td>\n<\/tr>\n
                  Delete<\/td>\nSelect the VLAN ID, click to delete<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                    \n
                  1. Click Add button to enter the page for creating a VLAN, as shown in Figure 3-3.<\/li>\n
                  2. Type VLAN number into the ID box, select the Tagged Members in the port panel to be assigned to these VLAN.<\/li>\n<\/ol>\n
                    \"Create
                    Figure 3-3: Create VLAN<\/figcaption><\/figure>\n
                      \n
                    • Click the Save in the auxiliary area to save the configuration.<\/li>\n<\/ul>\n

                      3.1.2.2 Configuring Trunk Port<\/p>\n

                        \n
                      1. Select Configuration > VLAN in the navigation area to enter the VLAN page as shown in Figure 3-4. Table 3-3 describes the configuration items of configuring a Trunk Port.<\/li>\n<\/ol>\n
                        \"Trunk
                        Figure 3-4: Trunk Configuration page<\/figcaption><\/figure>\n
                          \n
                        1. Click Batch Edit button below \u201cTrunk Configuration\u201d to enter the trunk configuration page, as shown in Figure 3-5. Table 3-3 describes the configuration items of configuring a VLAN.<\/li>\n<\/ol>\n
                          \"Interface
                          Figure 3-5: Interface configuration page<\/figcaption><\/figure>\n

                          Table 3-3: The description of the Trunk configuration<\/strong><\/p>\n

                          \n\n\n\n\n\n\n\n
                          Item<\/th>\nDescription<\/th>\n<\/tr>\n
                          Mode<\/td>\nAccess<\/td>\n<\/tr>\n
                          Set the port\u2019s default VLAN ID, only exist in access mode.<\/td>\nThe trunk ports at the two ends of a link must have the same PVID. Otherwise, the link cannot properly transmit packets<\/td>\n<\/tr>\n
                          Native Vlan<\/td>\nVLAN\uff08Native Vlan\uff09, only exist in Trunk mode.<\/td>\n<\/tr>\n
                          Allow VLANs<\/td>\nSelect the VLANs that are allowed through the port.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                            \n
                          1. Select the Vlan Mode, type VLAN number in PVID and Allow VLANs box, click Ok button to complete the configuration.<\/li>\n
                          2. Click the Save in the auxiliary area to save the configuration.<\/li>\n<\/ol>\n

                            Port<\/h2>\n

                            3.2.1 Port Configuration<\/p>\n

                            You can use the interface management feature to view interface information, create\/remove logical interfaces, change interface status, and reset interface parameters, as shown in Figure 3-6.<\/p>\n

                            \"Port
                            Figure 3-6: Port Configuration page<\/figcaption><\/figure>\n

                            Configuring interface management<\/p>\n

                              \n
                            1. Select Configuration > Port > Port Configuration in the navigation area to enter the port configuration page as shown in Figure 3-6.<\/li>\n
                            2. Select the ports to be configured, click Edit button to enter the page for configuring an interface, as shown in Figure 3-7. Table 3-4 describes the configuration items of configuring an interface.<\/li>\n<\/ol>\n
                              \"Port
                              Figure 3-7: Port Configuration page<\/figcaption><\/figure>\n

                              Table 3-4: Configuration items of Port<\/strong><\/p>\n

                              \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
                              Item<\/th>\nDescription<\/th>\n<\/tr>\n
                              Admin State<\/td>\nShutdown\/no shutdown the port.<\/td>\n<\/tr>\n
                              Description<\/td>\nSet the description of a logical interface.<\/td>\n<\/tr>\n
                              Port Mode<\/td>\nSet the port\u2019s vlan mode, Access or Trunk<\/td>\n<\/tr>\n
                              PVID\/Native VLAN<\/td>\nSet the port\u2019s PVID or Native VLAN.<\/td>\n<\/tr>\n
                              Medium type<\/td>\nSet the medium type of the Combo ports<\/td>\n<\/tr>\n
                              \u2022 RJ45\uff1athe mode of port is 10\/100\/1000BASE-T<\/td>\n\u2022 SFP\uff1athe mode of port is 1000BASE-X<\/td>\n<\/tr>\n
                              Note: only for combo ports.<\/td>\n<\/tr>\n
                              Speed(copper)<\/td>\nSet the port\u2019s transmission rate:<\/td>\n<\/tr>\n
                              \u2022 10: indicates 10 Mbps<\/td>\n\u2022 100M\uff1aindicates 100 Mbps<\/td>\n<\/tr>\n
                              \u2022 1000M\uff1aindicates 1000 Mbps<\/td>\n\u2022 Auto: indicates auto-negotiation<\/td>\n<\/tr>\n
                              Note: only for copper ports.<\/td>\n<\/tr>\n
                              Duplex(copper)<\/td>\nSet the port\u2019s duplex mode:<\/td>\n<\/tr>\n
                              \u2022 AUTO\uff1aindicates auto-negotiation<\/td>\n<\/tr>\n
                              \u2022 FULL\uff1aindicates full duplex<\/td>\n<\/tr>\n
                              \u2022 HALF\uff1aindicates half duplex<\/td>\n<\/tr>\n
                              Set the port\u2019s mode<\/td>\n\u2022 100BASE-FX\uff1aindicates the port mode is 100BASE-FX.<\/td>\n<\/tr>\n
                              \u2022 1000BASE-X\uff1aindicates the port mode is 1000BASE-X.<\/td>\n\u2022 2500BASE-X\uff1aindicates the port mode is 2.5G BASE-X.<\/td>\n<\/tr>\n
                              \u2022 10G BASE-X: indicates the port mode is 10G BASE-X.<\/td>\nNote: only for fiber ports.<\/td>\n<\/tr>\n
                              Autoneg(fiber)<\/td>\nEnables or disables port\u2019s autoneg.<\/td>\n<\/tr>\n
                              The auto-negotiation function needs to be enabled or disabled at the same<\/td>\ntime as the peer end, otherwise a link failure will occur.<\/td>\n<\/tr>\n
                              Note: only for fiber ports.<\/td>\n<\/tr>\n
                              Flow control<\/td>\nEnables or disables port\u2019s Flow control.<\/td>\n<\/tr>\n
                              MTU<\/td>\nAllows or forbids jumbo frames to pass through the port. Default length of packets is 46-1500 bytes.<\/td>\n<\/tr>\n
                              Admin Shutdown<\/td>\nShutdown\/no shutdown the port.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                              3.2.2 Port Extension 3.2.2.1 Rate Limiting Port-based rate limiting allows you to limit the speed at which network traffic is sent or received by a device that is connected to a port on your switch. Unlike 802.1p Quality of Service (QoS), port-based rate limiting does not prioritize information based on type. Rate limiting simply means that the switch will slow down traffic on a port to keep it from exceeding the limit that you set. If you set the rate limit on a port too low, you might see degraded video stream quality, sluggish response times during online activity, and other problems.<\/p>\n

                              The best use of rate limiting is to keep low-priority devices that are connected to your switch from using too much of your bandwidth and slowing down your other connected devices. A combination of rate limiting and QoS can help you maximize your network\u2019s efficiency and prioritize devices and activities.<\/p>\n

                              Configuring Port Ratelimit<\/p>\n

                                \n
                              1. Select Configuration > Port > Port Extension > Rate Limiting in the navigation area to enter the port ratelimit page as shown in Figure 3-8.<\/li>\n
                              2. Click the Batch Edit button below \u201cRate Limiting\u201d to enter the configure rate limiting page, as shown in Figure 3-9, type the number in the box. Table 3-5 describes the configuration items of configuring an interface.<\/li>\n
                              3. Click the Ok button.<\/li>\n
                              4. Click the Save button in the auxiliary area.<\/li>\n<\/ol>\n
                                \"Port
                                Figure 3-8: Port Ratelimit page<\/figcaption><\/figure>\n
                                \"Port
                                Figure 3-9: Port Ratelimit configuration<\/figcaption><\/figure>\n
                                  \n
                                • CBS embodies a rate-limit feature for policing traffic. When policing traffic with CBS, here recommends the burst value 4 times of the limit value. If the burst values are too low, then the achieved rate is often much lower than the configured rate.<\/li>\n<\/ul>\n

                                  Table 3-5: Port Ratelimit Configuration items<\/strong><\/p>\n

                                  \n\n\n\n\n\n\n\n
                                  Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                  In CIR (kbps)<\/td>\nSpecify the rate limit in the inbound direction (KBits).<\/td>\n<\/tr>\n
                                  In CBS (KB)<\/td>\nSpecify the burst size in the inbound direction (KBits).<\/td>\n<\/tr>\n
                                  Out CIR (kbps)<\/td>\nSpecify the rate limit in the outbound direction (KBits).<\/td>\n<\/tr>\n
                                  Out CBS (KB)<\/td>\nSpecify the burst size in the outbound direction (KBits).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                  3.2.2.2 Storm Control A traffic storm occurs when a large amount of broadcast, multicast, or unicast packets congest a network.<\/p>\n

                                  You can use the storm suppression function to limit the size of a particular type of traffic (currently broadcast, multicast and unknown unicast traffic) on a per-interface basis in Ethernet port view or port group view.<\/p>\n

                                  In interface or port group view, you set the maximum broadcast, multicast or unknown unicast traffic allowed to pass through an interface or each interface in a port group. When the broadcast, multicast, or unknown unicast traffic on the interface exceeds the threshold, the system discards packets until the traffic drops below the threshold.<\/p>\n

                                  Configuring the Storm Control<\/p>\n

                                    \n
                                  1. Select Configuration > Port > Port Extension > Strom Control in the navigation area to enter the storm control page as shown in Figure 3-10.<\/li>\n<\/ol>\n
                                    \"Strom
                                    Figure 3-10: Strom Control page<\/figcaption><\/figure>\n
                                      \n
                                    1. Select the Type, type the box of the Percentage, select the ports to be configured in the port panel, as shown in Figure 3-11. Table 3-7 describes the configuration items of configuring Strom control.<\/li>\n
                                    2. Click the Ok button to complete the configuration.<\/li>\n
                                    3. Click the Save in the auxiliary area.<\/li>\n<\/ol>\n
                                      \"Strom
                                      Figure 3-11: Strom Control configuration<\/figcaption><\/figure>\n

                                      Table 3-7: Items of the storm control<\/strong><\/p>\n

                                      \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
                                      Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                      Type<\/td>\nDisabled<\/td>\n<\/tr>\n
                                      Selects the parameter used in broadcast suppression and sets its<\/td>\nvalue in the percentage box.<\/td>\n<\/tr>\n
                                      Multicast<\/td>\nSelects the parameter used in multicast suppression and sets its<\/td>\n<\/tr>\n
                                      value in the percentage box.<\/td>\n<\/tr>\n
                                      Unicast<\/td>\nSelects the parameter used in unicast suppression and sets its<\/td>\n<\/tr>\n
                                      value in the percentage box.<\/td>\n<\/tr>\n
                                      multicast-broadcast<\/td>\nSelects the parameter used in multicast and broadcast<\/td>\n<\/tr>\n
                                      suppression and sets its value in the percentage box.<\/td>\n<\/tr>\n
                                      unicast-broadcast<\/td>\nSelects the parameter used in unicast and broadcast,<\/td>\n<\/tr>\n
                                      suppression and sets its value in the percentage box.<\/td>\n<\/tr>\n
                                      All<\/td>\nSelects the parameter used in unicast and unicast,<\/td>\n<\/tr>\n
                                      broadcast, suppression and sets its value in the percentage box.<\/td>\n<\/tr>\n
                                      Percentage (%)<\/td>\nIndicates the maximum percentage of traffic to the total<\/td>\n<\/tr>\n
                                      transmission capability of an Ethernet interface.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                      3.2.2.1 Isolation Usually, Layer 2 traffic isolation is achieved by assigning ports to different VLANs. To save VLAN resources, port isolation is introduced to isolate ports within a VLAN, allowing for great flexibility and security.<\/p>\n

                                        \n
                                      1. Switch support multiple isolation groups which can be configured manually. These devices are referred to as multiple-isolation-group devices.<\/li>\n
                                      2. There is no restriction on the number of ports assigned to an isolation group.<\/li>\n
                                      3. Within the same VLAN, Layer 2 data transmission between ports within and outside the isolation group is supported.<\/li>\n<\/ol>\n

                                        Configuring an Isolation Group<\/p>\n

                                          \n
                                        1. Select Configuration > Port > Port Extension > Isolation in the navigation area to enter the Port isolate page as shown in Figure 3-12.<\/li>\n
                                        2. Select the port to be isolated, click Ok button.<\/li>\n
                                        3. Click Save in the auxiliary area.<\/li>\n<\/ol>\n
                                          \"Port
                                          Figure 3-12: Port Isolate page<\/figcaption><\/figure>\n

                                          3.2.3 Port Mirroring Port mirroring is to copy the packets passing through one or multiple ports (called source interface) to a port (called the destination interface) on the local device. The source interface is connected with a monitoring device. By analyzing on the monitoring device, the packets mirrored to the destination interface, you can monitor the network and troubleshoot possible network problems.<\/p>\n

                                          Figure3-13 A port mirroring implementation Creating a mirroring group<\/p>\n

                                            \n
                                          1. Select Configuration > Port > Port Mirror in the navigation area to enter the Port mirror page as shown in Figure 3-14.<\/li>\n<\/ol>\n
                                            \"Port
                                            Figure 3-14: Port Mirror Page<\/figcaption><\/figure>\n
                                              \n
                                            1. Click the Edit button for the corresponding ID and select the destination interface or source interface, as shown in Figure 3-15. Table 3-8 describes the configuration items of creating a mirroring group.<\/li>\n<\/ol>\n
                                              \"The
                                              Figure 3-15: The page for creating a mirroring group<\/figcaption><\/figure>\n

                                              Table 3-8: Configuration items of creating a mirroring group<\/strong><\/p>\n

                                              \n\n\n\n\n\n\n
                                              Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                              Session<\/td>\nID of the mirroring group to be created<\/td>\n<\/tr>\n
                                              Destination Interface<\/td>\nthe monitor port for the mirroring group, there can only be one<\/td>\n<\/tr>\n
                                              Source Interface<\/td>\nmirroring ports for the mirroring group, there can be more than one<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                \n
                                              1. Click the Save button for the corresponding ID.<\/li>\n
                                              2. Click Ok button.<\/li>\n
                                              3. Click Save in the auxiliary area.<\/li>\n<\/ol>\n

                                                3.2.4 Port Aggregation 3.2.4.1 Overview Link Aggregation Ethernet link aggregation, most often simply called link aggregation, aggregates multiple physical Ethernet links into one logical link to increase link bandwidth beyond the limits of any one single link. This logical link is called an aggregate link. It allows for link redundancy because the member physical links dynamically back up one another.<\/p>\n

                                                As shown in Figure 3-16, Switch A and Switch B are connected with three physical Ethernet links. These physical Ethernet links are aggregated into an aggregate link, Link aggregation 1. The bandwidth of this aggregate link can be as high as the total bandwidth of these three physical Ethernet links.<\/p>\n

                                                \"Port
                                                Figure 3-16: Port Isolate page<\/figcaption><\/figure>\n

                                                LACP<\/p>\n

                                                The IEEE 802.3ad Link Aggregation Control Protocol (LACP) enables dynamic aggregation of physical links. It uses link aggregation control protocol data units (LACPDUs) for exchanging aggregation information between LACP-enabled devices.<\/p>\n

                                                There are two link aggregation modes: dynamic and static. Dynamic link aggregation uses LACP while static link aggregation does not. A link aggregation group operating in static mode is called a static link aggregation group, while a link aggregation group operating in dynamic mode is called a dynamic link aggregation group. 3.2.4.2 Configuring an Aggregation Group<\/p>\n

                                                Configuration procedure:<\/p>\n

                                                  \n
                                                1. Select Configuration > Port > Port Aggregation in the navigation area to enter the Link Aggregation page as shown in Figure 3-17, The description of the link aggregation is described in Table 3-9.<\/li>\n<\/ol>\n
                                                  \"Global
                                                  Figure 3-17: Global Configure Page<\/figcaption><\/figure>\n

                                                  Table 3-9: description of global configure item<\/strong><\/p>\n

                                                  \n\n\n\n\n\n\n\n\n\n\n
                                                  Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                  Equalize according to the destination MAC address and source MAC address<\/td>\n<\/tr>\n
                                                  dst-ip<\/td>\nEqualize according to the destination IP address<\/td>\n<\/tr>\n
                                                  srt-ip<\/td>\nEqualize according to the source IP address<\/td>\n<\/tr>\n
                                                  src-dst-ip<\/td>\nEqualize according to the destination IP address and source IP address<\/td>\n<\/tr>\n
                                                  dst-port<\/td>\nEqualize according to the L4 TCP\/UDP destination port number<\/td>\n<\/tr>\n
                                                  src-port<\/td>\nEqualize according to the L4 TCP\/UDP source port number<\/td>\n<\/tr>\n
                                                  src-dst-port<\/td>\nEqualize according to the L4 TCP\/UDP destination port number and source port number<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                    \n
                                                  1. In the Aggregate ports Configure page, click +Add button to enter port configuration page, as shown in Figure 3-18, The description of the link aggregation is described in Table 3-10.<\/li>\n<\/ol>\n
                                                    \"Aggregation
                                                    Figure 3-18: Aggregation port configuration page<\/figcaption><\/figure>\n
                                                    \"Aggregation
                                                    Figure 3-19: Aggregation port page<\/figcaption><\/figure>\n

                                                    Table 3-10: description of Aggregation Member<\/strong><\/p>\n

                                                    \n\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                    Table 3-11: description of Aggregation port<\/strong><\/p>\n

                                                    \n
                                                    \n\n\n\n\n
                                                    Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                    Aggregation<\/td>\n<\/tr>\n
                                                    The member ports of the Aggregation Port<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                    3.2.5 Port Violation During the use of the device, active or passive violations may occur on the switch port, such as port security violations, port flapping violations, port loop detection violations, etc. The port violation module is used to configure the recovery enablement and recovery time of the violating port, and displays the port's violation behavior.<\/p>\n

                                                    Configuration procedure:<\/p>\n

                                                    Select Configuration > Port > Port Violation in the navigation bar to enter the port violation global configuration interface, check the service that needs to be violated, turn on the automatic recovery button and configure the recovery time, click the Apply button to complete the configuration, such as Figure 3-40 is shown, and the global configuration parameters are shown in Table 3-13.<\/p>\n

                                                    \"Global
                                                    Figure 3-19: Global configuration page<\/figcaption><\/figure>\n
                                                    \"Port
                                                    Figure 3-20: Port State<\/figcaption><\/figure>\n

                                                    Spanning Tree<\/h2>\n

                                                    3.3.1 Overview Spanning Tree Protocol (STP) is a Layer-2 management protocol. It cannot only selectively block redundant links to eliminate Layer-2 loops but also can back up links.<\/p>\n

                                                    Like many protocols, STP is continuously updated from Rapid Spanning Tree Protocol (RSTP) to Multiple Spanning Tree Protocol (MSTP) as the network develops.<\/p>\n

                                                    For the Layer-2 Ethernet, only one active link can exist between two local area networks (LANs). Otherwise, a broadcast storm will occur. To enhance the reliability of a LAN, it is necessary to establish a redundant link and keep some paths in backup state. If the network is faulty and a link fails, you must switch the redundant link to the active state. STP can automatically activate the redundant link without any manual operations. STP enables devices on a LAN to:<\/p>\n

                                                    Discover and start the best tree topology on the LAN.<\/p>\n

                                                    Troubleshoot a fault and automatically update the network topology so that the possible best tree topology is always selected.<\/p>\n

                                                    The LAN topology is automatically calculated based on a set of bridge parameters configured by the administrator. The best topology tree can be obtained by properly configuring these parameters.<\/p>\n

                                                    RSTP is completely compatible with 802.1D STP. Like traditional STP, RSTP provides loop-free and redundancy services. It is characterized by rapid speed. If all bridges in a LAN support RSTP and are properly configured by the administrator, it takes less than 1 second (about 50 seconds if traditional STP is used) to re-generate a topology tree after the network topology changes.<\/p>\n

                                                    STP and RSTP have the following defects:<\/p>\n

                                                    STP migration is slow. Even on point-to-point links or edge ports, it still takes two times of the forward delay for ports to switch to the forwarding state.<\/p>\n

                                                    RSTP can rapidly converge but has the same defect with STP: Since all VLANs in a LAN share the same spanning tree, packets of all VLANs are forwarded along this spanning tree. Therefore, redundant links cannot be blocked according to specific VLANs and data traffic cannot be balanced among VLANs.<\/p>\n

                                                    MSTP, defined by the IEEE in 802.1s, resolves defects of STP and RSTP. It cannot only rapidly converge but also can enable traffic of different VLANs to be forwarded along respective paths, thereby providing a better load balancing mechanism for redundant links.<\/p>\n

                                                    In general, STP\/RSTP works based on ports while MSTP works based on instances. An instance is a set of multiple VLANs. Binding multiple VLANs to one instance can reduce the communication overhead and resource utilization. 3.3.2 Spanning Tree Configuring Global Configuration of the Spanning Tree<\/p>\n

                                                    Select Configuration > Spanning Tree > Global Configuration in the navigation area to enter the Global Configuration page, as shown in Figure 3-20. Table 3-12 describes the Spanning Tree Global Configuration items.<\/p>\n

                                                    \"Spanning
                                                    Figure 3-20: Spanning Tree Global Configuration<\/figcaption><\/figure>\n
                                                    \"Spanning
                                                    Figure 3-21: Spanning Tree Instance Configuration<\/figcaption><\/figure>\n

                                                    Table 3-12: Spanning Tree Global Configuration items<\/strong><\/p>\n

                                                    \n\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                    \"Spanning
                                                    Figure 3-22: Spanning Tree port Configuration<\/figcaption><\/figure>\n

                                                    Table 3-13: Spanning Tree Instance items<\/strong><\/p>\n

                                                    \n
                                                    \n<\/tbody>\n<\/table>\n<\/figure>\n

                                                    ERPS<\/h2>\n

                                                    3.4.1 Overview<\/p>\n

                                                    The ITU-T G.8032 ERPS feature implements protection switching mechanisms for Ethernet layer ring topologies. This feature uses the G.8032 Ethernet Ring Protection (ERP) protocol, defined in ITU-T G.8032, to provide protection for Ethernet traffic in a ring topology, while ensuring that no loops are within the ring at the Ethernet layer. The loops are prevented by blocking traffic on either a predetermined link or a failed link.<\/p>\n

                                                    Initial State<\/p>\n

                                                    As the following figure, the devices on the ring have been configured, and all the link status is up.<\/p>\n

                                                    The RPL owner interface will be blocked by ERPS protocol to prevent loops. If a RPL neighbor interface is configured, it will also be blocked. Other interfaces are under the forwarding state, can forward the traffic.<\/p>\n

                                                    Link failure<\/p>\n

                                                    When there is a link failure between SwitchD and SwitchE, the two interfaces on the link will be blocked by ERPS protocol, the RPL owner interface will be forwarded.<\/p>\n

                                                    Figure 1 Link failure Link restores<\/p>\n

                                                    When the failure link is restored. When the erps ring is configured to revertive mode, the RPL owner interface will be blocked by ERPS protocol, the restored link will be configured to forwarding state to forward traffic.<\/p>\n

                                                    Single-Ring\uff1a Only one ring in a network topology needs to be protected.<\/p>\n

                                                    In Figure 3-23, the network topology has only one ring, only one ring protection link (RPL) owner node, and only one RPL. All nodes must belong to the same ring automatic protection switching (R-APS) virtual local area network (VLAN).<\/p>\n

                                                    All devices in the ring network must support ERPS.<\/p>\n

                                                    The links between devices in the ring network must be directly connected, and there must be no intermediate devices.<\/p>\n

                                                    \"ERPS
                                                    Figure 3-23: ERPS single ring<\/figcaption><\/figure>\n

                                                    Tangent Rings\uff1a<\/p>\n

                                                    The two rings in a network topology that share one device need to be protected.<\/p>\n

                                                    In Figure 3-24, the two rings in the network topology share one device. Each ring has only one PRL owner node and only one RPL. The two rings belong to different R-APS VLANs.<\/p>\n

                                                    All devices in the ring network need to support ERPS.<\/p>\n

                                                    The links between devices in the ring network must be directly connected, and there must be no intermediate devices.<\/p>\n

                                                    \"ERPS
                                                    Figure 3-24: ERPS Tangent Rings<\/figcaption><\/figure>\n

                                                    Intersecting Rings\uff1a Two or more rings in a network topology share one link. (Each link between intersecting nodes must be a direct link without any intermediate node.)<\/p>\n

                                                    In Figure 3-25, four rings exist in the network topology. Each ring has only one PRL owner node and only one RPL. The four rings belong to different R-APS VLANs.<\/p>\n

                                                    All devices in the ring network need to support ERPS.<\/p>\n

                                                    The links between devices in the ring network must be directly connected, and there must be no intermediate devices.<\/p>\n

                                                    \"ERPS
                                                    Figure 3-25: ERPS Intersecting Rings<\/figcaption><\/figure>\n

                                                    3.4.2 Configure the ERPS Ring Configuration<\/p>\n

                                                    Select Configuration > ERPS > Ring Configuration in the navigation area to enter the ERPS Ring Configuration page as shown in Figure 3-26, The description of the ERPS Ring Configuration is described in Table 3-15.<\/p>\n

                                                    \"ERPS
                                                    Figure 3-26: ERPS Ring Configuration<\/figcaption><\/figure>\n
                                                    \"ERPS
                                                    Figure 3-27: ERPS Instance Configuration<\/figcaption><\/figure>\n

                                                    Table 3-15: Ring Configuration description<\/strong><\/p>\n

                                                    \n

                                                    \n<\/tbody>\n<\/table>\n<\/figure>\n
                                                    \"ERPS
                                                    Figure 3-28: ERPS Instance Configuration<\/figcaption><\/figure>\n
                                                    \"ERPS
                                                    Figure 3-29: ERPS State<\/figcaption><\/figure>\n

                                                    Table 3-16: Description of the ERPS Instance Configuration<\/strong><\/p>\n

                                                    \n
                                                    \n<\/tbody>\n<\/table>\n<\/figure>\n

                                                    PoE Management<\/h2>\n

                                                    3.5.1 PoE Overview Power over Ethernet (PoE) means that power sourcing equipment (PSE) supplies power to powered devices (PDs) from Ethernet interfaces through twisted pair cables. 3.5.2 PoE Configuration<\/p>\n

                                                      \n
                                                    • 1. Before configure PoE, make sure that the PoE power supply and PSE are operating normally; otherwise, you cannot configure PoE or the configured PoE function does not take effect.<\/li>\n
                                                    • 2. For switches with external power supply, the input voltage range is 44-57 V. In order to obtain a more stable power supply, it is recommended that the power supply voltage of AT equipment be greater than 50V, and that of BT equipment be greater than 53V.<\/li>\n
                                                    • 1. Before configure PoE, make sure that the PoE power supply and PSE are operating normally; otherwise, you cannot configure PoE or the configured PoE function does not take effect.<\/li>\n
                                                    • 2. For switches with external power supply, the input voltage range is 44-57 V. In order to obtain a more stable power supply, it is recommended that the power supply voltage of AT equipment be greater than 50V, and that of BT equipment be greater than 53V.<\/li>\n
                                                    • Select Configuration > PoE in the navigation area to enter the PoE Management page as shown in Figure<\/li>\n<\/ul>\n

                                                      3-30, the Table 3-18 describes the items of PoE Global Configuration.<\/p>\n

                                                        \n
                                                      1. Type the \u201cPower supply\u201d and \u201cPower reserved\u201d boxes, and click Apply button.<\/li>\n<\/ol>\n
                                                        \"PoE
                                                        Figure 3-30: PoE Global Configuration<\/figcaption><\/figure>\n
                                                        \"PoE
                                                        Figure 3-31: PoE Interface Configuration<\/figcaption><\/figure>\n

                                                        Table 3-18: description of PoE Global Configuration<\/strong><\/p>\n

                                                        \n

                                                    \n\n\n\n\n\n\n\n\n\n\n\n\n
                                                    Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                    Power supply (w)<\/td>\nBy default, the default power provided by the device is 15.4W*port number, for example, the maximum power provided by an 8-port device is 123.2W<\/td>\n<\/tr>\n
                                                    \u2022 For devices with external power supply, please fill in this parameter according to the actual configured power supply<\/td>\n\u2022 For devices with built-in power supply, please refer to the description of PoE power in the product manual for this parameter<\/td>\n<\/tr>\n
                                                    Power reserved (%)<\/td>\nReserved power set against power fluctuations<\/td>\n<\/tr>\n
                                                    \u2022 For devices with external power supply, it is recommended to fill in the power consumption of the main board<\/td>\n\u2022 For devices with built-in power supply, this parameter can be set 0 by default<\/td>\n<\/tr>\n
                                                    Power<\/td>\nmanagement<\/td>\n<\/tr>\n
                                                    Display the mode of power management is energy-saving. In this mode, the power requested and allocated to the port is based on the actual port's (real time) power consumption.<\/td>\n<\/tr>\n
                                                    Disconnect mode<\/td>\nDisplay the mode of disconnection is DC disconnect<\/td>\n<\/tr>\n
                                                    Alarm state<\/td>\nTurn on\/off the log alarm when the power is insufficient<\/td>\n<\/tr>\n
                                                    Power alarm (%)<\/td>\nAlarm power limit setting, when the PoE power consumption exceeds this value, the system will automatically output a log alarm<\/td>\n<\/tr>\n
                                                    \u2022 Click Batch Edit below \u201cport configuration\u201d to enter PoE port configuration page, Select the port to be configured, as shown in Figure 3-31.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                      \n
                                                    1. Click the OK to complete the operation, and then the page will return to the PoE Interface Configuration page, as shown in Figure 3-32. the Table 3-19 describes the items of the PoE Interface Configuration.<\/li>\n<\/ol>\n
                                                      \"PoE
                                                      Figure 3-32: PoE Interface Configuration<\/figcaption><\/figure>\n
                                                        \n
                                                      1. Click the Save in the navigation area to save the configuration.<\/li>\n<\/ol>\n

                                                        Security<\/h2>\n

                                                        3.6.1 Port Security 3.6.1.1 Overview<\/p>\n

                                                        The Port Security function restricts the number of valid MAC addresses on the port to limit the access of illegal users to the port. The illegal MAC packets will be directly discarded.<\/p>\n

                                                        The legal MAC can be generated statically or dynamically. The static legal MAC is generated through user command line configuration; the dynamic legal MAC is dynamically generated through the MAC address learning function.<\/p>\n

                                                        When the number of secure addresses on the port has reached the configured value of the maximum number of secure addresses, the new MAC access port will be recognized as an illegal MAC and a violation event will be generated. The user can configure the actions to be taken when the violation event occurs, respectively restrict or shutdown the port.<\/p>\n

                                                        Restrict: Prohibit illegal MAC data from passing, and generate alarm log prompt information. Illegal MAC will prohibit access to the port within the MAC address aging time. It can be restored through shutdown and no shutdown ports.<\/p>\n

                                                        Shutdown: The port is forced to be down, and the port recovery time can be configured. The port will automatically recover when the time is up; it can also be recovered by the shutdown, no shutdown command.<\/p>\n

                                                        If you want to convert a dynamic security user to a static security user, you can enable the sticky function on the port. When the sticky function is enabled on the port, the dynamic users learned on the port will exist as static users. If the configuration is saved, the device will still exist after restarting the device.<\/p>\n

                                                          \n
                                                        • Only support L2 port configuration port security, such as ordinary physical port, aggregation port.<\/li>\n
                                                        • Only support port security configuration in access mode.<\/li>\n
                                                        • Does not support aggregation port member ports to configure port security functions.<\/li>\n
                                                        • Does not support SPAN destination port configuration port security function.<\/li>\n
                                                        • Does not support configuring port security functions on ports that have been configured with static MAC addresses.<\/li>\n
                                                        • Only support L2 port configuration port security, such as ordinary physical port, aggregation port.<\/li>\n
                                                        • Only support port security configuration in access mode.<\/li>\n
                                                        • Does not support aggregation port member ports to configure port security functions.<\/li>\n
                                                        • Does not support SPAN destination port configuration port security function.<\/li>\n
                                                        • Does not support configuring port security functions on ports that have been configured with static MAC addresses.<\/li>\n<\/ul>\n

                                                          3.6.1.2 Configuring Port Security Port Configuration<\/p>\n

                                                          Select Configuration > Security > Port security in the navigation area to enter the Port security page as shown in Figure 3-33.<\/p>\n

                                                          \"Port
                                                          Figure 3-33: Port Security statistic page<\/figcaption><\/figure>\n

                                                          Click the Batch Edit button below \u201cPort Configuration\u201d to enter the Port Configuration page, as shown in Figure 3-34. The items of the port configuration are described in Table 3-20.<\/p>\n

                                                          \"Port
                                                          Figure 3-34: Port Security configuration page<\/figcaption><\/figure>\n
                                                          \"MAC
                                                          Figure 3-35: MAC configuration summary<\/figcaption><\/figure>\n
                                                          \"MAC
                                                          Figure 3-36: MAC configuration page<\/figcaption><\/figure>\n

                                                          Table 3-20: the items of the port security configuration<\/strong><\/p>\n

                                                          \n\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                          Table 3-21: the items of the mac configuration<\/strong><\/p>\n

                                                          \n
                                                          \n\n\n\n\n\n\n\n
                                                          Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                          MAC<\/td>\nConfiguration<\/td>\n<\/tr>\n
                                                          Interface<\/td>\nSelect the interface to be configured.<\/td>\n<\/tr>\n
                                                          MAC Address<\/td>\nConfigure a static security address, the format of the security address: XXXX.XXXX.XXXX<\/td>\n<\/tr>\n
                                                          The security address cannot be a broadcast or multicast Address.<\/td>\n<\/tr>\n
                                                          Type<\/td>\nConfigure the MAC address as dynamic or static.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                          3.6.2 IP Source Guard 3.6.2.1 Overview IP Source Guard\uff1a<\/p>\n

                                                          The Ip Source Guard binding function allows IP packets conforming to the IP+MAC binding to pass through the port, and non-conforming packets are directly discarded, thereby achieving the purpose of preventing IP\/MAC spoofing attacks.<\/p>\n

                                                          The binding entries of Ip Source Guard mainly come from two sources: user static configuration and dynamic acquisition in the ip dhcp snooping environment.<\/p>\n

                                                          User static configuration: mainly for host users whose IP addresses are statically configured in the local area network.<\/p>\n

                                                          Ip dhcp snooping dynamic acquisition: mainly respond to the host users who dynamically acquire the IP address through dhcp in the local area network.<\/p>\n

                                                          IP\/MAC spoofing attack: Illegal MAC users send IP packets with legal source IP to realize the legalization of access identity.<\/p>\n

                                                          ARP Check\uff1a<\/p>\n

                                                          The Arp-check (ARP packet check) function filters all ARP packets under the port and discards all illegal ARP packets, which can effectively prevent ARP spoofing in the network and improve the stability of the network.<\/p>\n

                                                          In the device that supports the Arp-check function, the Arp-check function can generate corresponding ARP filtering information based on the legal user information (IP+MAC) generated by the security application modules such as IP Source Guard, so as to realize the illegal ARP packets filtering in the network. 3.6.2.2 Configuring IP Source Guard<\/p>\n

                                                            \n
                                                          1. Select Configuration > Security > IP Source Guard in the navigation area to enter the IP Source Guard Summary page as shown in Figure 3-37.<\/li>\n<\/ol>\n
                                                            \"IP
                                                            Figure 3-37: IP source guard Summary<\/figcaption><\/figure>\n
                                                              \n
                                                            1. Click Batch Edit button below \u201cPort Configuration\u201d in the current page, select the interface to be configured in the port panel, click Verify Source button, as shown in Figure 3-38.<\/li>\n<\/ol>\n
                                                              \"IP
                                                              Figure 3-38: IP source guard port configuration<\/figcaption><\/figure>\n

                                                              Click OK button, the rules created were displayed in summary page as shown in Figure 3-39.<\/p>\n

                                                              \"port
                                                              Figure 3-39: port configuration<\/figcaption><\/figure>\n
                                                                \n
                                                              1. Click +ADD button below \u201cUser Configuration\u201d in current page, to enter the user configuration page, Select the port in the interface box, text VID, IP Address, MAC Address, as shown in Figure 3-40.<\/li>\n<\/ol>\n
                                                                \"IP
                                                                Figure 3-40: IP source guard user configuration<\/figcaption><\/figure>\n
                                                                  \n
                                                                1. Click OK button, the rules created were displayed in summary page as shown in Figure 3-41.<\/li>\n<\/ol>\n
                                                                  \"IP
                                                                  Figure 3-41: IP source guard rules Summary<\/figcaption><\/figure>\n

                                                                  3.6.2.3 Configuring ARP Check<\/p>\n

                                                                    \n
                                                                  1. Select Configuration > Security > IP Source Guard in the navigation area to enter the IP Source Guard Summary page as shown in Figure 3-37.<\/li>\n
                                                                  2. Click Batch Edit button below \u201cPort Configuration\u201d in the current page, select the interface to be configured in the port panel, click ARP Check button, as shown in Figure 3-42.<\/li>\n<\/ol>\n
                                                                    \"IP
                                                                    Figure 3-42: IP Source Guard ARP Check<\/figcaption><\/figure>\n
                                                                      \n
                                                                    1. Click +ADD button below \u201cUser Configuration\u201d in current page, to enter the user configuration page, as shown in Figure 3-43.<\/li>\n<\/ol>\n
                                                                      \"IP
                                                                      Figure 3-43: IP Source Guard User Configuration<\/figcaption><\/figure>\n
                                                                        \n
                                                                      1. Click APPLY button, the rules created were displayed in summary page as shown in Figure 3-44.<\/li>\n<\/ol>\n
                                                                        \"ARP
                                                                        Figure 3-44: ARP Check rules<\/figcaption><\/figure>\n

                                                                        3.6.3 Dot1X 3.6.3.1 Overview<\/p>\n

                                                                        The 802.1X(Dot1X) protocol was proposed by the IEEE 802 LAN\/WAN committee for security of wireless LANs (WLAN). It has been widely used on Ethernet as a common port access control mechanism.<\/p>\n

                                                                        As a port-based access control protocol, 802.1X authenticates and controls accessing devices at the port level. A device connected to an 802.1X-enabled port of an access control device can access the resources on the LAN only after passing authentication.<\/p>\n

                                                                        Architecture of 802.1X 802.1X operates in the typical client\/server model and defines three entities: Client, Device, and Server, as shown in below.<\/p>\n

                                                                        Client is an entity seeking access to the LAN. It resides at one end of a LAN segment and is authenticated by Device at the other end of the LAN segment. Client is usually a user-end device such as a PC. 802.1X authentication is triggered when an 802.1X-capable client program is launched on Client. The client program must support Extensible Authentication Protocol over LAN (EAPOL).<\/p>\n

                                                                        Device, residing at the other end of the LAN segment, authenticates connected clients. Device is usually an 802.1X-enabled network device and provides access ports (physical or logical) for clients to access the LAN.<\/p>\n

                                                                        Server is the entity that provides authentication services to Device. Server, normally running RADIUS (Remote Authentication Dial-in User Service), serves to perform authentication, authorization, and accounting services for users.<\/p>\n

                                                                        Authentication modes of 802.1x<\/p>\n

                                                                        The 802.1X authentication system employs the Extensible Authentication Protocol (EAP) to exchange authentication information between the client, device, and authentication server. Client Device Server Between the client and the device, EAP protocol packets are encapsulated using EAPOL to be transferred on the LAN.<\/p>\n

                                                                        Between the device and the RADIUS server, EAP protocol packets can be exchanged in two modes: EAP relay and EAP termination. In EAP relay mode, EAP packets are encapsulated in EAP over RADIUS (EAPOR) packets on the device, and then relayed by device to the RADIUS server. In EAP termination mode, EAP packets are terminated at the device, converted to RADIUS packets either with the Password Authentication Protocol (PAP) or Challenge Handshake Authentication Protocol (CHAP) attribute, and then transferred to the RADIUS server.<\/p>\n

                                                                        Basic concepts of 802.1x These basic concepts are involved in 802.1X: controlled port\/uncontrolled port, authorized state\/unauthorized state, and control direction.<\/p>\n

                                                                        Controlled port and uncontrolled port A device provides ports for clients to access the LAN. Each port can be regarded as a unity of two logical ports: a controlled port and an uncontrolled port. Any packets arriving at the port are visible to both logical ports.<\/p>\n

                                                                        The uncontrolled port is always open in both the inbound and outbound directions to allow EAPOL protocol packets to pass, guaranteeing that the client can always send and receive authentication packets.<\/p>\n

                                                                        The controlled port is open to allow data traffic to pass only when it is in the authorized state.<\/p>\n

                                                                        Authorized state and unauthorized state<\/p>\n

                                                                        \"Authorized\/unauthorized
                                                                        Figure 3-45: Authorized\/unauthorized state of a controlled port<\/figcaption><\/figure>\n

                                                                        A controlled port can be in either authorized state or unauthorized state, which depends on the authentication result, as shown in Figure 3-45.<\/p>\n

                                                                        You can control the port authorization status of a port by setting port authorization mode to one of the following:<\/p>\n

                                                                        Force-Authorized: Places the port in authorized state, allowing users of the port to access the network without authentication.<\/p>\n

                                                                        Force-Unauthorized: Places the port in unauthorized state, denying any access requests from users of the port.<\/p>\n

                                                                        Auto: Places the port in the unauthorized state initially to allow only EAPOL packets to pass, and turns the port into the authorized state to allow access to the network after the users pass authentication. This is the most common choice.<\/p>\n

                                                                        Control direction<\/p>\n

                                                                        In the unauthorized state, the controlled port can be set to deny traffic to and from the client or just the traffic from the client. 802.1X authentication triggering 802.1X authentication can be initiated by either a client or the device.<\/p>\n

                                                                        Unsolicited triggering of a client A client can initiate authentication unsolicitedly by sending an EAPOL-Start packet to the device. The destination address of the packet is 01-80-C2-00-00-03, the multicast address specified by the IEEE 802.1X protocol.<\/p>\n

                                                                        Some devices in the network may not support multicast packets with the above destination address, and unable to receive authentication requests of clients as a result. To solve this problem, the device also supports EAPOL-Start packets using a broadcast MAC address as the destination address.<\/p>\n

                                                                        Unsolicited triggering of the device<\/p>\n

                                                                        The device can trigger authentication by sending EAP-Request\/Identity packets to unauthenticated clients periodically (every 30 seconds by default). This method can be used to authenticate clients that cannot send EAPOL-Start packets unsolicitedly to trigger authentication, for example, a client running the 802.1X client application provided by Windows XP.<\/p>\n

                                                                        Authentication process of 802.1x An 802.1X device communicates with a remote RADIUS server in two modes: EAP relay and EAP termination. The following describes the 802.1X authentication procedure in the two modes, which is triggered by the client in the examples.<\/p>\n

                                                                        EAP relay EAP relay is defined in IEEE 802.1X. In this mode, EAP packets are carried in an upper layer protocol, such as RADIUS, so that they can go through complex networks and reach the authentication server. Generally, relaying EAP requires that the RADIUS server support the EAP attributes of EAP-Message and Message-Authenticator, which are used to encapsulate EAP packets and protect RADIUS packets carrying the EAPMessage attribute respectively.<\/p>\n

                                                                        \"shows
                                                                        Figure 3-46: shows the message exchange procedure with EAP-MD5<\/figcaption><\/figure>\n
                                                                          \n
                                                                        1. When a user launches the 802.1X client software and enters the registered username and password, the 802.1X client software generates an EAPOL-Start frame and sends it to the device to initiate an authentication process.<\/li>\n
                                                                        2. Upon receiving the EAPOL-Start frame, the device responds with an EAPRequest\/Identity packet for the username of the client.<\/li>\n
                                                                        3. When the client receives the EAP-Request\/Identity packet, it encapsulates the username in an EAP-Response\/Identity packet and sends the packet to the device.<\/li>\n
                                                                        4. Upon receiving the EAP-Response\/Identity packet, the device relays the packet in a RADIUS Access-Request packet to the authentication server.<\/li>\n
                                                                        5. When receiving the RADIUS Access-Request packet, the RADIUS server compares the identify information against its user information table to obtain the corresponding password information. Then, it encrypts the password information using a randomly generated challenge, and sends the challenge information through a RADIUS Access-Challenge packet to the device.<\/li>\n
                                                                        6. After receiving the RADIUS Access-Challenge packet, the device relays the contained EAP-Request\/MD5 Challenge packet to the client.<\/li>\n
                                                                        7. When receiving the EAP-Request\/MD5 Challenge packet, the client uses the offered challenge to encrypt the password part (this process is not reversible), creates an EAP-Response\/MD5 Challenge packet, and then sends the packet to the device.<\/li>\n
                                                                        8. After receiving the EAP-Response\/MD5 Challenge packet, the device relays the packet through a RADIUS Access-Request packet to the authentication server.<\/li>\n
                                                                        9. When receiving the RADIUS Access-Request packet, the RADIUS server compares the password information encapsulated in the packet with that generated by itself. If the two are identical, the authentication server considers the user valid and sends to the device a RADIUS Access-Accept packet.<\/li>\n
                                                                        10. Upon receiving the RADIUS Access-Accept packet, the device opens the port to grant the access request of the client. After the client gets online, the device periodically sends handshake requests to the client to check whether the client is still online. By default, if two consecutive handshake attempts end up with failure, the device concludes that the client has gone offline and performs the necessary operations, guaranteeing that the device always knows when a client goes offline.<\/li>\n
                                                                        11. The client can also send an EAPOL-Logoff frame to the device to go offline unsolicitedly. In this case, the device changes the status of the port from authorized to unauthorized and sends an EAP-Failure packet to the client.<\/li>\n<\/ol>\n

                                                                          3.6.3.2 Configuring Dot1X<\/p>\n

                                                                          Select Security > Dot1x> Configuration from the navigation area. The system automatically displays the 802.1X Global Configuration and Port Configuration, as shown in Figure 3-47 and Figure 3-48. Table 3-22 and Table 3-23 describes the Global Configuration and Port Configuration items.<\/p>\n

                                                                          \"802.1X
                                                                          Figure 3-47: 802.1X Global Configuration<\/figcaption><\/figure>\n
                                                                          \"802.1X
                                                                          Figure 3-48: 802.1X Port Configuration<\/figcaption><\/figure>\n

                                                                          Table 3-22: The 802.1X Configuration items<\/strong><\/p>\n

                                                                          \n\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                                          Table 3-23: The 802.1X port Configuration items<\/strong><\/p>\n

                                                                          \n
                                                                          \n\n\n\n\n\n\n\n\n\n\n\n\n\n
                                                                          Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                                          Port<\/td>\nConfiguration<\/td>\n<\/tr>\n
                                                                          Name<\/td>\nPhysical interface name<\/td>\n<\/tr>\n
                                                                          Port Control<\/td>\nPort control mode<\/td>\n<\/tr>\n
                                                                          Protocol Version<\/td>\nEapol protocol version, default version 2<\/td>\n<\/tr>\n
                                                                          Quiet Period(s)<\/td>\nSets the number of seconds that the switch remains in the quiet-period following a failed authentication exchange with the client. The range is 0 to 65,535 seconds; the default is 60.<\/td>\n<\/tr>\n
                                                                          When the switch cannot authenticate the client, the switch remains idle for a set period, and then tries again. The idle time is determined by the quiet-period value.<\/td>\n<\/tr>\n
                                                                          Tx Period(s)<\/td>\nSets the number of seconds that the switch waits for a response to an EAP-request\/identity frame from the client before retransmitting the request. The range is 1 to 65,535 seconds; the default is 30.<\/td>\n<\/tr>\n
                                                                          ReAuth Enabled<\/td>\nEnables periodic reauthentication of the client<\/td>\n<\/tr>\n
                                                                          ReAuth Period(s)<\/td>\nSpecifies the number of seconds between reauthentication attempts or have the switch use a RADIUS-provided session timeout. The range is 1 to 65,535; the default is 3600 seconds. This command affects the behavior of the switch only if periodic reauthentication is enabled.<\/td>\n<\/tr>\n
                                                                          Supp Timeout(s)<\/td>\nSets the number of seconds that the switch waits for a response to an EAP-Request\/MD5 Challenge frame from the client before retransmitting the request. The range is 1 to 65,535 seconds; the default is 30.<\/td>\n<\/tr>\n
                                                                          Server Timeout(s)<\/td>\nSets the number of seconds that the switch waits for a response to a RADIUS Access-Request packet from the server. The range is 1 to 65,535 seconds; the default is 30.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                                          3.6.4 MAC Auth 3.6.4.1 Overview Authentication of MAC addresses is supported using a RADIUS server that contains a database of all valid users.<\/p>\n

                                                                          When the mac-auth option is enabled on any interface, all source MAC addresses from any incoming frame are sent for authentication. If the username and password of the source address are configured in the RADIUS server, then authentication succeeds, otherwise it fails. When authentication succeeds, the source MAC is added to the forwarding table with forwarding enabled. In the case of failure, the source MAC either is added to the forwarding table as discarded or is added to a restricted VLAN.<\/p>\n

                                                                            \n
                                                                          • If the configured static MAC is the same as the silent MAC, the MAC silent function after the MAC address authentication fails will be invalid.<\/li>\n<\/ul>\n

                                                                            3.6.4.2 Configuring MAC authentication Displaying MAC Authentication Summary<\/p>\n

                                                                            Select Configuration > Security > MAC Authentication from the navigation area. The system automatically displays the MAC Authentication summary, as shown in Figure 3-49. Table 3-24 describes the MAC Authentication Summary items.<\/p>\n

                                                                            \"The
                                                                            Figure 3-49: The MAC Authentication Summary<\/figcaption><\/figure>\n
                                                                            \"MAC
                                                                            Figure 3-50: MAC Authentication Port Configuration<\/figcaption><\/figure>\n

                                                                            Table 3-24: The MAC Authentication Summary items<\/strong><\/p>\n

                                                                            \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
                                                                            Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                                            Global<\/td>\nConfiguration<\/td>\n<\/tr>\n
                                                                            State<\/td>\nEnables the 802.1X feature on your switch.<\/td>\n<\/tr>\n
                                                                            RADIUS<\/td>\nConfiguration<\/td>\n<\/tr>\n
                                                                            Click to jump to the RADIUS configuration interface<\/td>\n<\/tr>\n
                                                                            Port<\/td>\nConfiguration<\/td>\n<\/tr>\n
                                                                            Name<\/td>\nPhysical interface name<\/td>\n<\/tr>\n
                                                                            State<\/td>\nDisplay the state of MAC Auth<\/td>\n<\/tr>\n
                                                                            MAC Address Aging<\/td>\nDisplay the state of MAC Address Aging<\/td>\n<\/tr>\n
                                                                            Action<\/td>\nClick to Edit the rule<\/td>\n<\/tr>\n
                                                                            Select Configuration > Security > MAC Authentication from the navigation area. Click Statebutton in \u201cGlobal Configuration\u201d, click Apply button to enable the MAC Auth function.<\/td>\n<\/tr>\n
                                                                            \u2022 Configuring Port<\/td>\nClick Batch Edit button below \u201cPort Configuration\u201d to enter the port configuration page, as shown in Figure<\/td>\n<\/tr>\n
                                                                            3-50. Click State button, select the port to be configured in port panel, click Ok button.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                                            3.6.5 RADIUS 3.6.5.1 Overview Remote Authentication Dial-In User Service (RADIUS) is protocol for implementing Authentication, Authorization, and Accounting (AAA).<\/p>\n

                                                                            RADIUS is a distributed information interaction protocol using the client\/server model. RADIUS can protect networks against unauthorized access and is often used in network environments where both high security and remote user access are required. RADIUS uses UDP, and its packet format and message transfer mechanism are based on UDP. It uses UDP port 1812 for authentication and 1813 for accounting.<\/p>\n

                                                                            RADIUS was originally designed for dial-in user access. With the diversification of access methods, RADIUS has been extended to support more access methods, for example, Ethernet access and ADSL access. It uses authentication and authorization in providing access services and uses accounting to collect and record usage information of network resources.<\/p>\n

                                                                            Client\/server model Client: The RADIUS client runs on the NASs located throughout the network. It passes user information to designated RADIUS servers and acts on the responses (for example, rejects or accepts user access requests).<\/p>\n

                                                                            Server: The RADIUS server runs on the computer or workstation at the network center and maintains information related to user authentication and network service access. It listens to connection requests, authenticates users, and returns the processing results (for example, rejecting or accepting the user access request) to the clients.<\/p>\n

                                                                            In general, the RADIUS server maintains three databases: Users, Clients, and Dictionary, as shown in Figure 4-39.<\/p>\n

                                                                            \"RADIUS
                                                                            Figure 4-39: RADIUS server components<\/figcaption><\/figure>\n

                                                                            Users: Stores user information such as the usernames, passwords, applied protocols, and IP addresses.<\/p>\n

                                                                            Clients: Stores information about RADIUS clients, such as the shared keys and IP addresses.<\/p>\n

                                                                            Dictionary: Stores information about the meanings of RADIUS protocol attributes and their values.<\/p>\n

                                                                            Security and authentication mechanisms Information exchanged between a RADIUS client and the RADIUS server is authenticated with a shared key, which is never transmitted over the network. This enhances the information exchange security. In addition, to prevent user passwords from being intercepted on insecure networks, RADIUS encrypts passwords before transmitting them.<\/p>\n

                                                                            A RADIUS server supports multiple user authentication methods, for example, the Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP) of the Point-to-Point Protocol (PPP). Moreover, a RADIUS server can act as the client of another AAA server to provide authentication proxy services.<\/p>\n

                                                                            Basic message exchange process of RADIUS<\/p>\n

                                                                            \"illustrates
                                                                            Figure 3-51: illustrates the interaction of the host, the RADIUS client, and the RADIUS server.<\/figcaption><\/figure>\n
                                                                            \"Basic
                                                                            Figure 3-51: Basic message exchange process of RADIUS<\/figcaption><\/figure>\n

                                                                            The following is how RADIUS operates:<\/p>\n

                                                                              \n
                                                                            1. The host initiates a connection request carrying the username and password to the RADIUS client.<\/li>\n
                                                                            2. Having received the username and password, the RADIUS client sends an authentication request (Access-Request) to the RADIUS server, with the user password encrypted by using the Message-Digest 5 (MD5) algorithm and the shared key.<\/li>\n
                                                                            3. The RADIUS server authenticates the username and password. If the authentication succeeds, it sends back an Access-Accept message containing the user \u2018s authorization information. If the authentication fails, it returns an Access-Reject message.<\/li>\n
                                                                            4. The RADIUS client permits or denies the user according to the returned authentication result. If it permits the user, it sends a start-accounting request (Accounting-Request) to the RADIUS server.<\/li>\n
                                                                            5. The RADIUS server returns a start-accounting response (Accounting-Response) and starts accounting.<\/li>\n
                                                                            6. The user accesses the network resources.<\/li>\n
                                                                            7. The host requests the RADIUS client to tear down the connection and the RADIUS client sends a stop-accounting request (Accounting-Request) to the RADIUS server.<\/li>\n
                                                                            8. The RADIUS server returns a stop-accounting response (Accounting-Response) and stops accounting for the user.<\/li>\n
                                                                            9. The user stops access to network resources<\/li>\n<\/ol>\n
                                                                                \n
                                                                              • Do not support RADIUS accounting function<\/li>\n<\/ul>\n

                                                                                3.6.5.2 Configuring RADIUS RADIUS global configuration<\/p>\n

                                                                                Select Configuration > Security > RADIUS from the navigation area. The system automatically displays the RADIUS Global Configuration, as shown in Figure 3-52. Table 4-19 describes the RADIUS Global Configuration items.<\/p>\n

                                                                                \"The
                                                                                Figure 3-52: The RADIUS Global Configuration<\/figcaption><\/figure>\n

                                                                                Table 4-19: The RADIUS Global Configuration items<\/strong><\/p>\n

                                                                                \n\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                                                \"The
                                                                                Figure 3-53: The RADIUS Server Configuration<\/figcaption><\/figure>\n

                                                                                Control<\/h2>\n

                                                                                3.7.1 Serial Servers 3.7.1.1 Overview<\/p>\n

                                                                                The serial device server is used to connect serial devices to the Ethernet. The serial device server supports bidirectional conversion and transmission of network data and serial data. Serial device server work in tcp-client mode, as shown in Figure 3-53.<\/p>\n

                                                                                \"Serial
                                                                                Figure 3-53: Serial device server work in tcp-client mode<\/figcaption><\/figure>\n

                                                                                Serial device server in tcp-client mode provides client connections for TCP network servers. it actively initiates a connection and connect to the server to realize the interaction between serial device and tcp server. The Tcp\/Ip and serial data are transparently transmitted in both directions. The serial device server supports to establish multiple TCP Clients to connect to different Tcp Server. Serial device server work in tcp-server mode, as show in Figure 3-54.<\/p>\n

                                                                                In TCP Server mode, the module monitors the local port, accepts and establishes a connection for data communication when a connection request is sent. Used for communication with TCP clients within a local area network. It is suitable for scenarios where there is no server in the LAN and there are multiple computers or mobile phones requesting data from the module.<\/p>\n

                                                                                \"Serial
                                                                                Figure 3-54: Serial device server work in tcp-server mode<\/figcaption><\/figure>\n

                                                                                3.7.1.2 Configuring Serial Server<\/p>\n

                                                                                Select Configuration > Control > Serial Server from the navigation area. The system automatically displays the Serial Server Configuration page, as shown in Figure 3-55.<\/p>\n

                                                                                \"Serial
                                                                                Figure 3-55: Serial Server Configuration Summary<\/figcaption><\/figure>\n

                                                                                Click Edit button to enter Serial Server Configuration page, as shown in Figure 3-56. Table 3-25 describes the Serial Server Configuration items.<\/p>\n

                                                                                \"Serial
                                                                                Figure 3-56: Serial Server Configuration<\/figcaption><\/figure>\n

                                                                                Table 3-25: Serial Server Configuration items<\/strong><\/p>\n

                                                                                \n

                                                                                \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
                                                                                Item<\/th>\nDescription<\/th>\n<\/tr>\n
                                                                                Serial port number<\/td>\n<\/tr>\n
                                                                                Baud Rate<\/td>\nThe baud rate of the serial port is configured, and there are five kinds of options: 9600, 19200, 38400, 57600, and 115200<\/td>\n<\/tr>\n
                                                                                Data Bits<\/td>\nThe data bits of the serial port are configured, and there are two kinds of options: 7 and 8<\/td>\n<\/tr>\n
                                                                                Parity<\/td>\nThere are five types of configuration checksum methods: none, even, odd, mark, and space<\/td>\n<\/tr>\n
                                                                                Stop Bits<\/td>\nThere are two options for configuring the stop bit, 1 and 2<\/td>\n<\/tr>\n
                                                                                Serial port data bits are transmitted at low speed, and the data is transferred from the network end to the serial port side to increase the fifo, improve the forwarding ability, the range < 0-128>, the default 64<\/td>\nThe length of the serial port data packet, beyond the LEGGTH value, the packet is forwarded to the network end, the range <0-1460>, the default is 1460<\/td>\n<\/tr>\n
                                                                                Interval<\/td>\nIf the interval between the bytes before and after the serial port data exceeds MILLISECONDS, the post-byte data is recognized as the new message header byte<\/td>\n<\/tr>\n
                                                                                Configure the serial port server to keep alive, during which there is no data interaction, then active detection is initiated<\/td>\n<\/tr>\n
                                                                                Client<\/td>\nRemote IP<\/td>\n<\/tr>\n
                                                                                Configure the port number for the remote connection, ranging from < 1-65535><\/td>\n<\/tr>\n
                                                                                Local port<\/td>\nFor optional configurations, the default system is automatically assigned<\/td>\n<\/tr>\n
                                                                                Configure the tcp-server port number, which < range from 1-65535><\/td>\n<\/tr>\n
                                                                                Max connections<\/td>\nThe maximum number of connections in tcp-server mode, ranging from 1 to 65535 ><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

                                                                                3.7.2 IO Control IO control module is divided into DI, DO two parts. In current software, DO only supports simple manual control relay (DO) ON\/OFF switching function, as shown in Figure 3-57. DI only supports input level high and low judgment, as shown in Figure 3-58.<\/p>\n

                                                                                \"DI
                                                                                Figure 3-57: DI Configuration page<\/figcaption><\/figure>\n
                                                                                \"DO
                                                                                Figure 3-58: DO Configuration page<\/figcaption><\/figure>\n

                                                                                LoopDetect<\/h2>\n

                                                                                3.8.1 Overview LOOP-DETECT is an Ethernet loop detection protocol, which is used to quickly detect loop faults on downlink interfaces. If a fault is found, LOOP-DETECT will notify the user to manually close or automatically close the relevant port according to the fault handling method configured by the user, so as to avoid affecting the normal data exchange.<\/p>\n

                                                                                Enable control: Enable control is divided into global enable control and port enable control. When the global enable control is enabled and the loop detection is enabled on the port, the port supports the loop detection function.<\/p>\n

                                                                                Loop action: When a loop fault is detected on the port, the user will be notified to manually handle the loop fault by default, and the automatic closing of the port can also be configured. When the port is automatically shut down, the port can recover from the fault by waiting for timeout, shutdown\/no shutdown port, recovery command, or restarting the device.<\/p>\n

                                                                                Specify vlan: By default, the port vlan attribute is ignored; if you need to detect whether a loop fault occurs in a specific vlan domain, you can configure the specified vlan on the port, and only detect Whether there is a loop data path in this vlan domain.<\/p>\n

                                                                                The device supports loop fault alarm and loop fault recovery message traps to the snmp server, which is disabled by default. 3.8.2 Configuring LoopDetect LoopDetect Configuration<\/p>\n

                                                                                  \n
                                                                                1. Select Configuration > LoopDetect in the navigation area to enter the loopdetect page. This page contains two parts: "Global Configuration" and "Port Configuration".<\/li>\n
                                                                                2. Turn on the loop detection switch in the global configuration page, configure the detection<\/li>\n<\/ol>\n

                                                                                  interval, turn on the Trap switch (optional), and click the Apply button to complete theconfiguration, as shown in Figure 3-59, the Table 3-26 describes the items of PoE Global Configuration.<\/p>\n

                                                                                  \"LoopDetect
                                                                                  Figure 3-59: LoopDetect Global Configuration<\/figcaption><\/figure>\n

                                                                                  Table 3-26: Loop detection global configuration items<\/strong><\/p>\n

                                                                                  \n\n\n\n\n\n\n
                                                                                  Items<\/th>\nDescription<\/th>\n<\/tr>\n
                                                                                  Loop detection<\/td>\nTurn on\/off the loop detection function. The default is to turn off globally and the port.<\/td>\n<\/tr>\n
                                                                                  Detection interval<\/td>\nConfigure loop detection interval, range 5-300 seconds, default 5 seconds<\/td>\n<\/tr>\n
                                                                                  Trap<\/td>\nEnable\/disable loop fault trap alarm<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
                                                                                    \n
                                                                                  1. Click the Batch Edit button under "Port Configuration" or the Edit button behind the port that needs to be configured to enter the loop detection port configuration interface, configure the management status, violation handling method, VLAN domain detection, and select the required. The port that enables this function is shown in Figure 3-60, and the parameter description is shown in Table 3-27.<\/li>\n<\/ol>\n
                                                                                    \"LoopDetect
                                                                                    Figure 3-60: LoopDetect Port Configuration<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

                                                                                    Networking \u203a Switching \u203a Edge \u203a Synapse<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":6380,"menu_order":3,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[115,119,117],"class_list":["post-6383","docs","type-docs","status-publish","hentry","doc_tag-connexite","doc_tag-network","doc_tag-synapse-web-ui-documentation","no-post-thumbnail"],"acf":[],"_links":{"self":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6383","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/comments?post=6383"}],"version-history":[{"count":1,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6383\/revisions"}],"predecessor-version":[{"id":6431,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6383\/revisions\/6431"}],"up":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6380"}],"wp:attachment":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/media?parent=6383"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/doc_tag?post=6383"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}