User manual SMC 6709GL2 INT

[. . . ] TigerSwitch 10/100 9-Port Fast Ethernet Switch 8 10BASE-T/100BASE-TX ports, 1 1000BASE-LX MMF port 1. 8 Gbps aggregate bandwidth Spanning Tree Protocol Port mirroring for non-intrusive analysis QoS support with two priority queues Full support for VLANs with GVRP IP multicasting with IGMP snooping Security filtering based on MAC addresses Manageable via console, Web, SNMP/RMON Management Guide SMC6709GL2 TigerSwitch 10/100 Management Guide From SMC's Tiger line of feature-rich workgroup LAN solutions 38 Tesla Irvine, CA 92618 Phone: (949) 679-8000 March 2004 Information furnished by SMC Networks, Inc. However, no responsibility is assumed by SMC for its use, nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of SMC. SMC reserves the right to change specifications at any time without notice. [. . . ] Port address table is cleared, and the port begins learning addresses. - Forwarding - Port forwards packets, and continues learning addresses. Web ­ Click Administrator=>Spanning Tree. 3-38 PORT MIRRORING Port Mirroring You can mirror traffic from any source port to a target port for real-time analysis. You can then attach a logic analyzer or RMON probe to the target port and study the traffic crossing the source port in a completely unobtrusive manner. Command Usage · Monitor port speed should match or exceed source port speed, otherwise traffic may be dropped from the monitor port. · When mirroring port traffic, the target port must be included in the same VLAN as the source port. Field Attributes · · · · · Roving Analysis State ­ Enables / disables port mirroring. Analysis Port ­ The port that mirrors traffic from the source port. Monitor Tx ­ Mirrors transmit traffic. Web ­ Click Administrator=>Port Sniffer. Specify the analysis port, the monitor ports and traffic types to mirror, enable the Roving Analysis State, and then click Apply. 3-39 CONFIGURING THE SWITCH Simple Network Management Protocol The switch includes an onboard agent that continuously monitors the status of its hardware, as well as the traffic passing through its ports, based on the Simple Network Management Protocol (SNMP). A network management station can access this information using software. Access rights to the onboard agent are controlled by community strings. To communicate with the switch, the management station must first submit a valid community string for authentication. The options for configuring community strings and related trap functions are described in the following sections. Configuring System Information Use the SNMP page to identify the system by providing a descriptive name, location, and contact information. Field Attributes · Name ­ Name assigned to the switch system. Specify the system name, location, and contact information for the system administrator, then click Apply. Setting Community Access Strings You may configure up to five community strings authorized for management access. For security reasons, you should consider removing the default strings. 3-40 SIMPLE NETWORK MANAGEMENT PROTOCOL Field Attributes · Community String ­ A community string acts as a password and permits access to the SNMP protocol. Authorized management stations are able to both retrieve and modify MIB objects. Enter a new string in the text box and select the access rights, then click Add. Specifying Trap Managers You can specify up to five management stations that will receive authentication failure messages and other trap messages from the switch. Field Attributes · IP Address ­ IP address of trap manager. · Community ­ A community string acts as a password and allows the trap manager to receive trap messages via the SNMP protocol. Fill in the IP address and community string for a trap manager, then click Add. 3-41 CONFIGURING THE SWITCH User Authentication The administrator has write access for parameters governing the onboard agent. [. . . ] · If you are trying to connect to the agent via a tagged VLAN group, your management station must include the appropriate tag in its transmitted frames. · Check that you have a valid network connection to the switch and that the port you are using has not been disabled. · Check network cabling between the management station and the switch. · If you cannot connect using Telnet, there may already be four active sessions. [. . . ]