User manual TP-LINK TL-SG5426 INSTALLATION GUIDE

[. . . ] TL-SG5426 26-Port Gigabit Managed Switch Rev: 1. 0. 0 1910010105 COPYRIGHT & TRADEMARKS ® is a registered Specifications are subject to change without notice. trademark of TP-LINK TECHNOLOGIES CO. , LTD. Other brands and product names are trademarks or registered trademarks of their respective holders. No part of the specifications may be reproduced in any form or by any means or used to make any derivative such as translation, transformation, or adaptation without permission from TP-LINK TECHNOLOGIES CO. , LTD. [. . . ] Web ­ Click IP Source Guard, Port Configuration. Figure 3-119 IP Source Guard Port Configuration CLI ­ This example shows how to enable IP source guard on port 5. Console(config)#interface ethernet 1/5 Console(config-if)#ip source-guard sip Console(config-if)#end Console#show ip source-guard Interface Filter-type ------------------Eth 1/1 DISABLED Eth 1/2 DISABLED Eth 1/3 DISABLED Eth 1/4 DISABLED Eth 1/5 SIP Eth 1/6 DISABLED . 4-227 4-230 Static IP Source Guard Binding Configuration Adds a static addresses to the source-guard binding table. Table entries include a MAC address, IP address, lease time, entry type (Static, Dynamic), VLAN identifier, and port identifier. All static entries are configured with an infinite lease time, which is indicated with a value of zero in the table. 3-192 IP Source Guard Command Attributes · · · · · Static Binding Table Counts ­ The total number of static entries in the table. (Range: 1-26) VLAN ID ­ ID of a configured VLAN (Range: 1-4094) MAC Address ­ A valid unicast MAC address. IP Address ­ A valid unicast IP address, including classful types A, B or C. 3 Web ­ Click IP Source Guard, Static Configuration. Figure 3-120 Static IP Source Guard Binding Configuration CLI ­ This example shows how to configure a static source-guard binding on port 5. Console(config)#ip source-guard binding 11-22-33-44-55-66 vlan 1 192. 168. 0. 99 interface ethernet 1/5 Console(config)# 4-229 Dynamic IP Source Guard Binding Information Displays the source-guard binding table for a selected interface. Command Attributes · Query by ­ Select an interface to display the source-guard binding. (Options: Port, VLAN, MAC Address, or IP Address) · Dynamic Binding Table Counts ­ Displays the number of IP addresses in the source-guard binding table. · Current Dynamic Binding Table ­ Displays the IP addresses in the source-guard binding table. 3-193 3 Configuring the Switch Web ­ Click IP Source Guard, Dynamic Information. Figure 3-121 Dynamic IP Source Guard Binding Information CLI ­ This example shows how to configure a static source-guard binding on port 5. Console#show ip source-guard binding 4-230 MacAddress IpAddress Lease(sec) Type VLAN Interface ----------------- --------------- ---------- -------------------- -------11-22-33-44-55-66 192. 168. 0. 99 0 Static 1 Eth 1/5 Console# Switch Clustering Switch Clustering is a method of grouping switches together to enable centralized management through a single unit. Switches that support clustering can be grouped together regardless of physical location or switch type, as long as they are connected to the same local network. A switch cluster has a "Commander" unit that is used to manage all other "Member" switches in the cluster. The management station can use both the web interface and Telnet to communicate directly while the Commander throught its IP address, and the Commander manages Member switches using cluster "internal" IP addresses. There can be up to 16 Member switches in one cluster. Cluster switches are limited to within a single IP subnet. 3-194 Switch Clustering Once a switch has been configured to be a cluster Commander, it automatically discovers other cluster-enabled switches in the network. These "Candidate" switches only become cluster Members when manually selected by the administrator through the management station. 3 After the Commander and Members have been configured, any switch in the cluster can be managed from the web interface by choosing the Member ID from the Cluster drop-down menu. From the Commander CLI prompt, use the "rcommand" command (see 4-240) to connect to the Member switch. Figure 3-122 Cluster Member Choice Cluster Configuration To create a switch cluster, first be sure that clustering is enabled on the switch (the default is enabled), then set the switch as a Cluster Commander. Set a Cluster IP Pool that does not conflict with the network IP subnet. Cluster IP addresses are assigned to switches when they become Members and are used for communication between Member switches and the Commander. Command Attributes · Cluster Status ­ Enables or disables clustering on the switch. · Cluster Commander ­ Enables or disables the switch as a cluster Commander. · Role ­ Indicates the current role of the switch in the cluster; either Commander, Member, or Candidate. · Cluster IP Pool ­ An "internal" IP address pool that is used to assign IP addresses to Member switches in the cluster. [. . . ] This is related directly to the hardware interface for network devices and passes on traffic based on MAC addresses. Link Aggregation See Port Trunk. Link Aggregation Control Protocol (LACP) Allows ports to automatically negotiate a trunked link with LACP-configured ports on another device. Management Information Base (MIB) An acronym for Management Information Base. It is a set of database objects that contains information about a specific device. MD5 Message-Digest Algorithm An algorithm that is used to create digital signatures. It is intended for use with 32 bit machines and is safer than the MD4 algorithm, which has been broken. MD5 is a one-way hash function, meaning that it takes a message and converts it into a fixed string of digits, also called a message digest. Glossary-3 Glossary Multicast Switching A process whereby the switch filters incoming multicast frames for services for which no attached host has registered, or forwards them to all ports contained within the designated multicast VLAN group. Network Time Protocol (NTP) NTP provides the mechanisms to synchronize time across the network. [. . . ]