User manual SMC 6624FMSC

[. . . ] TigerSwitch 10/100 Stackable Fast Ethernet Switch N N N N N N N N N N N 24 10BASE-T/100BASE-TX RJ-45 ports Auto MDI/MDI-X support on all ports Optional 100BASE-FX or 1000BASE-X modules Optional stack module for linking up to 16 units 8. 8 Gbps of aggregate switch bandwidth LACP and FEC port trunking support Port mirroring for non-intrusive analysis Port security Full support for IEEE 802. 1Q VLANs with GVRP IP Multicasting with IGMP Snooping Manageable via console, Web, SNMP/RMON Management Guide SMC6624M TigerSwitch 10/100 Management Guide From SMC's Tiger line of feature-rich workgroup LAN solutions 6 Hughes Irvine, CA 92618 Phone: (949) 707-2400 July 2001 Pub. # 150000001100A R01 Information furnished by SMC Networks, Inc. (SMC) is believed to be accurate and reliable. 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. [. . . ] If the primary VLAN is tagged, then each switch in the stack must use the same VLAN ID (VID) for the primary VLAN. (See "Which VLAN Is Primary?" on page 9-51, and "Stacking Operation with Multiple VLANs Configured" on page 9-45. ) I Configuring Advanced Features Options for Configuring a Commander and Candidates. Depending on how Commander and Candidate switches are configured, Candidates can join a stack either automatically or by a Commander manually adding ("pulling") them into the stack. In the default configuration, a Candidate joins only when manually pulled by a Commander. You can reconfigure a Commander to automatically pull in Candidates that are in the default stacking configuration. You can also reconfigure a Candidate switch to either "push" itself into a particular Commander's stack, convert the Candidate to a Commander (for a stack that does not already have a Commander), or to operate as a standalone switch without stacking. The following table shows your control options for adding Members to a stack. 9-8 Configuring Advanced Features Stack Management Table 9-3. Stacking Configuration Guide Join Method1 Commander Candidate (IP Addressing Required) (IP Addressing Optional) Auto Grab Automatically add Candidate to Stack (Causes the first 15 eligible, discovered switches in the subnet to automatically join a stack. ) Manually add Candidate to Stack (Prevent automatic joining of switches you don't want in the stack) Yes Auto Join Yes (default) Passwords No (default)* Configuring Advanced Features No (default) Yes Yes Yes (default) No Yes (default) or No Disabled Optional* Optional* Configured Optional Prevent a switch from being a Candidate N/A * The Commander's Manager and Operator passwords propagate to the candidate when it joins the stack. The easiest way to automatically create a stack is to: 1. Configure IP addressing and a stack name on the Commander. Set the Commander's Auto Grab parameter to Yes. Connect Candidate switches (in their factory default configuration) to the network. This approach automatically creates a stack of up to 16 switches (including the Commander). However this replaces manual control with an automatic process that may bring switches into the stack that you did not intend to include. With the Commander's Auto Grab parameter set to Yes, any switch conforming to all four of the following factors automatically becomes a stack Member: I Default stacking configuration (Stack State set to Candidate, and Auto Join set to Yes) Same subnet (broadcast domain) and default VLAN as the Commander (If VLANs are used in the stack environment, see "Stacking Operation with a Tagged VLAN" on page 9-45. ) No Manager password 14 or fewer stack members at the moment I I I 9-9 Configuring Advanced Features Stack Management General Steps for Creating a Stack This section describes the general stack creation process. For the detailed configuration processes, see pages 9-12 through 9-36 for the menu interface and pages 9-29 through 9-41 for the CLI. Configuring Advanced Features Determine the naming conventions for the stack. Also, to help distinguish one switch from another in the stack, you can configure a unique system name for each switch. Otherwise, the system name for a switch appearing in the Stacking Status screen appears as the stack name plus an automatically assigned switch number. For example: For status descriptions, see the table on page 9-47. Stack with unique system name for each switch. Stack named "Online" with no previously configured system names assigned to individual switches. Figure 9-4. Use of System Name to Help Identify Individual Switches 2. Doing this first helps to establish consistency in your stack configuration, which can help prevent startup problems. · A stack requires one Commander switch. [. . . ] 7-37 browsing the configuration file . . . 11-3 diagnosing unusual network activity . . . 11-13 restoring factory default configuration . . . 11-3 trunk See port trunk trunk group FEC . . . [. . . ]