COREBUILDER 6000 SOFTWARE INSTALLATION AND RELEASE NOTES ™ ¨ CoreBuilder Extended Switching Software Revision 8.2.3 October 17, 1997 Part No.
3Com Corporation ■ 5400 Bayfront Plaza ■ Santa Clara, California ■ 95052-8145 Copyright © 3Com Corporation, 1997. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without permission from 3Com Corporation.
CONTENTS COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Overview 1 Hardware Dependencies 1 Upgrading Your LMM or LMM+ 1 Extended Switching Software Requirement 2 Release Highlights for 8.2.3 2 Release Highlights for 8.2.0 2 Before You Start 3 Updating Your System Software 3 Copying System Software to a Hard Disk 4 Copying to the UNIX Platform 4 Copying to the MS-DOS Platform 5 Loading System Software on the LMM+ 6 User Documentation 8 What’s New at Revision 8.2.
Disconnecting an Active telnet or rlogin Session STP linkState Changes 20 CoreBuilder 6000 12-Slot Chassis 21 System Issues 23 Known Problems 26 SNMP MIB Files 28 Supported Versions 28 Compiler Support 29 Revision History 30 18 A IP MULTICAST ROUTING Overview A-1 Enabling and Disabling DVMRP A-2 Enabling and Disabling IGMP A-2 Administering IP Multicast Interfaces A-3 DVMRP Metric Value A-3 Time To Live (TTL) Threshold A-3 Rate Limit A-4 Displaying Multicast Interfaces A-4 Disabling Multicast Interfaces
Host Group B-7 HostTopN Group B-8 Matrix Group B-8 3Com Transcend RMON Agents B-8 Management Information Base (MIB) B-9 MIB Objects B-10 C VLANS ON THE COREBUILDER SYSTEM About VLANs C-1 Types of VLANs C-1 Port Group VLANs C-2 MAC Address Group VLANS C-2 Application-Oriented VLANS C-2 Protocol-Sensitive VLANS C-3 CoreBuilder Protocol-Sensitive VLAN Configuration C-3 Protocol Suite C-3 Layer 3 Addressing Information C-4 Default VLAN C-4 Modifying the Default VLAN C-5 How the CoreBuilder System Makes Floodi
E TECHNICAL SUPPORT Online Technical Services E-1 World Wide Web Site E-1 3Com Bulletin Board Service E-1 Access by Analog Modem E-2 Access by Digital Modem E-2 3ComFacts Automated Fax Service E-2 3ComForum on CompuServe Online Service Support from Your Network Supplier E-3 Support from 3Com E-4 Returning Products for Repair E-5 E-3 3COM CORPORATION LIMITED WARRANTY
COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Overview These installation instructions and release notes describe revision 8.2.3 of the CoreBuilder™ 6000 Extended Switching software from 3Com Corporation, dated October 9, 1997. This revision supersedes revision 8.2.1, dated May 30, 1997. Hardware Dependencies LANplex® Extended Switching software revision 8.0.0 or greater, or CoreBuilder Extended Switching software revision 8.2.
2 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 If you have an LMM+ at a revision earlier than 1.21 (for revision 1 modules) or 2.12 (for revision 2 modules), call 3Com at 1-800-876-3266 and press option 2. 3Com will replace your LMM+ with an LMM+ at the correct revision, free of charge. (Contact 3Com at the same number to upgrade an LMM to an LMM+. There is a fee for this upgrade.) Release 8.0.
Updating Your System Software ■ Filter MIB ■ FTP packet filter program transfers via SNMP ■ Disconnecting an active telnet or rlogin session ■ STP linkState changes ■ CoreBuilder 6000 12-slot Chassis 3 For more information about this release, see “What’s New at Revision 8.2.0?” on page 14. Before You Start Before you install your new software, read all of these release notes. Carefully read “System Issues” on page 23 and “Known Problems” on page 26.
4 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Copying System Software to a Hard Disk You can copy system software to a computer that runs either a UNIX or an MS-DOS operating system. Copying to the UNIX Platform The CoreBuilder software for a UNIX system is distributed on six diskettes. Diskettes #1, #2, #3, #4, and #5 contain the CoreBuilder software. Diskette #6 contains the SNMP MIBs. To copy the software to a UNIX hard disk, follow these instructions.
Updating Your System Software 5 8 Insert diskette #4 into the disk drive and extract the fourth part of the file using the following command: # tar xvf /dev/rfd0 9 Remove diskette #4 using the following command: # eject 10 Insert diskette #5 into the disk drive and extract the fifth part of the file using the following command: # tar xvf /dev/rfd0 11 Remove diskette #5 using the following command: # eject The following files are now in your /usr/lp6000R directory: ■ README1 ■ lp6000R00 ■ lp6000R0
6 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Installing on a Windows 95 or Windows NT Computer. To copy software to an MS-DOS host computer’s hard disk using Windows 95 or Windows NT, take these steps: 1 Insert diskette #1 into a disk drive. These instructions assume drive a. 2 For Windows 95, click the Windows 95 START button and choose Run. OR For Windows NT, from the File menu, select Run. The system displays the Setup screen, with the system software name, and the Setup dialog box.
Loading System Software on the LMM+ 7 Loading 8.2.3 software into flash memory takes approximately 10 to 15 minutes to complete, depending on your network load. To load the new software: 1 From the top level of the Administration Console, enter: system softwareUpdate The system prompts you for the Host IP address, Install filename, User name, and Password. Press Return or Enter to accept the default values, which are shown in brackets. The Password field does not display what you enter.
8 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 After the software is loaded, this message appears: Installation complete. If the CoreBuilder executable software image stored in flash memory is corrupted (for example, when the power fails while you are updating software), contact 3Com Technical Support. See Appendix E.
What’s New at Revision 8.2.3? ■ FDDI Switching Module (FSM) Guide ■ Fast Ethernet Switching Module (FESM) Guide 9 In addition, Filter Builder software and the Filter Builder Getting Started Guide are shipped with CoreBuilder 6000 Extended Switching software. What’s New at Revision 8.2.3? This section describes the new features, software enhancements, and corrections implemented at this release. New Features The following new features have been added at this release.
10 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 ■ Group 2: History — Stores periodic statistical samples of Group 1 data for later retrieval.
What’s New at Revision 8.2.3? 11 7 Enter the advertisement address to be used on the interface. 8 Enter the number of the VLAN whose interface you are defining. Example: Select IP stack by slot {1-3,5,7,9-12} [1]: 5 Enter IP address: 158.101.1.1 Enter subnet mask [255.255.0.0]: 255.255.255.0 Enter cost [1]: Enter advertisement address(es) [158.101.1.
12 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Top-Level Menu system display ethernet mode fddi lowLatency tokenring ipFragmentation ➧ bridge ipxSnapTranslation ip trFddiMode snmp addressThreshold analyzer agingTime script stpState logout ➧ stpFollowLinkState stpPriority stpMaxAge stpHelloTime stpForwardDelay stpGroupAddress srBridgeNumber port packetFilter vlan Enabling and Disabling STP Transitions on linkState Changes The menu item stpFollowLinkState has been added.
What’s New at Revision 8.2.
14 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 What’s New at Revision 8.2.0? This section describes the new features, software enhancements, and corrections that are implemented at this release. New Features The following features have been added at this release.
What’s New at Revision 8.2.0? 15 To verify that you have an LMM+ module and not an LMM module installed: 1 Verify that the module’s ejector tab is labeled “LMM+”. 2 Determine the revision level of your LMM+. From the top level of the Administration Console, enter: system display To upgrade your LMM or LMM+, see “Upgrading Your LMM or LMM+” on page 1.
16 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Full-duplex mode eliminates both the link’s collision domain and the need for collision detection. As a result, full-duplex point-to-point links can be much longer than half-duplex links. To configure a port for full-duplex operation: The items available on the top-level menus in this section vary depending on your level of access and on the modules installed in your CoreBuilder 6000 chassis.
What’s New at Revision 8.2.0? 17 5 Enter full to set the port to full-duplex mode or half to set the port to half-duplex mode. Default The port’s current setting is indicated in brackets. To select this default, press Return. This action leaves the port duplex mode unchanged. 6 Repeat steps 4 and 5 to configure all the selected ports in all the selected slots. Changing the mode to full-duplex disables collision detection on these ports. Intelligent Flow Management (IFM).
18 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 For each slot that you enter, the system asks for specific port numbers: Select Ethernet port(s) (1-8,all): 3 Enter the number(s) of the port(s) that you want to configure: 1,2,5-7 Default To select the default all, press Return. Enter enable or disable to select the IFM mode for each selected port: Enter new value (disabled, enabled) [disabled]: 4 Enter enabled to set the port to IFM mode or disabled to deactivate IFM for the port.
What’s New at Revision 8.2.0? 19 telnet Implementation. When you attempt to use the telnet command to enter a system that is being used by another telnet connection, the system displays: Sorry, this system is engaged by another telnet session. Host IP address: xxx.xxx.xxx.xxx Logout the other telnet session? (Y/N) y Enter Password: correctpassword The first telnet session is disconnected and the system displays: LOGGING OUT the other telnet session. You can then connect in the usual manner.
20 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 STP linkState Changes The linkState of a port is now a factor in determining the Spanning Tree port state. This change helps prevent bridge loops when making network connections to previously inactive ports.
What’s New at Revision 8.2.0? 21 Note these additional items: ■ ■ ■ The linkState up or down settings apply to Ethernet and Fast Ethernet ports, not to FDDI ports, and only when the stpState for the bridge is enabled. If the stpState on the Bridge menu is disabled, the State for the port remains in forwarding state. When the bridge port is in the Removed state, the State remains in forwarding state. If STP is disabled on an individual port, the State remains disabled.
22 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 To remove a faulty power supply and replace it with a new unit, follow these steps: 1 Turn off the power supply according to the safety and removal procedures in the Installation Guide that is shipped with the new power supply. The system control panel displays the following message (where n designates power supply 1 or power supply 2): Power Supply n: Input Failure 2 Remove the power supply.
System Issues ■ 23 +12V Restored The power supply +12-volt input is restored. ■ Power Supply Over Temp One of the power supplies has exceeded the allowable temperature of 90 °C (194 °F). SNMP Traps. When you insert and extract either of the power supplies, the system generates SNMP traps. Hot-swappable fans. You can remove and replace either of the two fans at the back of the chassis. Follow the safety precautions and removal instructions in the Installation Guide that comes with the new fan.
24 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 ■ 3Com recommends that you hot-swap one module at a time (except FESMs and FSMs, as described in the previous System Issue). After you hot-swap one module, wait until the system completes full initialization before you install another module. One indication that initialization is complete is that the Administration Console prompt appears.
System Issues 25 ■ If you attempt to run CoreBuilder 6000 system software revision 8.2.3 on an LMM+ at revision 2.11 or earlier, the system fails to reboot when you turn it on. See “Hardware Dependencies” on page 1. ■ You can configure a maximum total of 100 routing interfaces for all switching modules in a single CoreBuilder 6000 system.
26 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Known Problems The following software problems are identified at this release: ■ To compile lpv2.mib with a version 2 compiler, perform these steps: 1 In the IMPORTS section, add: RowStatus FROM SNMPv2-TC 2 A few lines below, add the following RowStatus comment: -- RowStatus ::== INTEGER (1..
Known Problems 27 ■ Roving Analysis cannot monitor outgoing routed packets. ■ FCS error statistics report inaccurate values on the TMM-FE’s port. ■ You cannot modify the port specification of an IP interface that is defined on the LMM+ module. To modify the port specification, remove the IP interface and define it again. ■ An NVDATA save procedure fails if it occurs at the same instant that a MAC address is learned or aged out of the slot’s MAC address table.
28 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 ■ Performing a manual nvdata restore restores configurations to slots even if the configurations have been specified not to restore. When you restore NV data, the system proposes a method of restoration based on restoration rules. You are prompted to load the proposal. Entering yes restores the system NV data as proposed. Entering no displays the saved configuration for you to load manually.
SNMP MIB Files ■ lp.mib — LANplex Systems MIB, version 1.3.0 ■ lpOpFddi.mib — LANplex Optional FDDI MIB, version 1.2.1 ■ mib2.mib — MIB-II, RFC 1213 ■ rmon.mib — RMON MIB, RFC 1757 ■ srbridge.mib —Source Routing MIB RFC1525 ■ vlan.mib — LANplex VLAN MIB Compiler Support 29 ASN.1 MIB files are provided for each of the MIB compilers in this list. Any warnings or exceptions related to a compiler are listed with it. ■ SMIC (version 1.0.9) ■ MOSY (version 7.1) For the MIB file lpOpFddi.
30 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Revision History Table 2 describes the previous releases of the CoreBuilder 6000 Extended Switching software. Table 2 Revision History for CoreBuilder 6000 Software Revision Number Description of Release 8.2.1/8.2.3 New features: 8.2.
Revision History 31 Table 2 Revision History for CoreBuilder 6000 Software (continued) Revision Number Description of Release 8.0.0 New features: 7.0.
32 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.3 Table 2 Revision History for CoreBuilder 6000 Software (continued) Revision Number Description of Release 6.0.0 New feature: ■ 5.0.0 4.3.0 New features: ■ Support for LMM+ management module ■ Support for IPX Routing ■ Support for AppleTalk Routing New features: ■ UDP Helper ■ IPX Snap Translation Option ■ Support for EFSM Type 1, 10BASE-2 (BNC) module ■ 4.1.
Revision History 33 Table 2 Revision History for CoreBuilder 6000 Software (continued) Revision Number Description of Release 3.1.7 Maintenance release MIB support removed: ■ ■ 3.1.5 3.1.1 3.0.1 The LANplex SNMP MIB traps, lpBridgePortAddressLearnedEvent and lpBridgePortAddressForgottenEvent, are no longer supported. New feature: ■ 3.1.4 The Ethernet MIB attributes, requestedEnabledPaths and enabledPaths, are no longer supported.
34 COREBUILDER 6000 EXTENDED SWITCHING SOFTWARE REVISION 8.2.
IP MULTICAST ROUTING A Overview This appendix describes how to set up your CoreBuilder ™ 6000 system to use IP multicast routing. Before you define any IP multicast interfaces, you should have previously defined IP interfaces and routes as described in the LANplex® 6000 Extended Switching User Guide.
A-2 APPENDIX A: IP MULTICAST ROUTING Enabling and Disabling DVMRP Top-Level Menu system ethernet interface fddi ➧ dvmrp route tokenring arp igmp bridge ➧ multicast interfaces ➧ ip udpHelper tunnel ipx routeDisplay routing appletalk icmpRouterDiscovery cacheDisplay snmp rip analyzer ping script statistics logout DVMRP is the simple Distance Vector Multicast Routing Protocol, similar to the IP Routing Information Protocol.
Administering IP Multicast Interfaces A-3 When you select the IGMP option, the interface prompts you to enable or disable IGMP snooping mode and IGMP query mode. Both are enabled by default. Under most conditions, IGMP snooping mode and IGMP query mode should remain enabled.
A-4 APPENDIX A: IP MULTICAST ROUTING Rate Limit The rate limit determines how fast multicast traffic can travel over the interface in kilobytes per second. Multicast traffic may not exceed this rate limit or the CoreBuilder system will drop packets in order to maintain the set rate. The default is set to 0, which implies no rate limit. In all other instances, the lower the rate limit, the more limited the traffic over the interface.
Administering IP Multicast Interfaces Disabling Multicast Interfaces Top-Level Menu system ethernet interface route dvmrp fddi igmp display tokenring arp bridge ➧ multicast ➧ interface enable udpHelper tunnel ➧ disable ➧ ip routing routeDisplay ipx cacheDisplay appletalk icmpRouterDiscovery rip snmp analyzer ping statistics script logout A-5 To disable multicast routing on an interface: 1 From the top level of the Administration Console, enter: ip multicast interface disable 2 Enter the slot(s) of the s
A-6 APPENDIX A: IP MULTICAST ROUTING Example: Select IP stack by slot (2,3,7,9-12|all) [12]: Enter an IP interface index [1]: 2 Enter Interface DVMRP metric [1]: 1 Enter Interface TTL threshold [1]: Enter interface rate limit in KBits/sec [0]: Administering Multicast Tunnels A multicast tunnel allows multicast packets to cross several unicast routers to a destination router that supports multicast. A tunnel has two end points.
Administering Multicast Tunnels Defining a Multicast Tunnel A-7 To define a multicast tunnel: 1 From the top level of the Administration Console, enter: Top-Level Menu system interface ethernet route dvmrp fddi arp igmp display tokenring ➧ multicast interface ➧ define bridge udpHelper ➧ tunnel remove ➧ ip routing routeDisplay ipx icmpRouterDiscovery cacheDisplay appletalk rip snmp ping analyzer statistics script logout ip multicast tunnel define 2 Enter the slot(s) of the switching module for which yo
A-8 APPENDIX A: IP MULTICAST ROUTING Removing a Multicast Tunnel Top-Level Menu system ethernet interface fddi route dvmrp tokenring arp display igmp bridge ➧ multicast interface define ➧ ip udpHelper➧ tunnel ➧ remove ipx routing routeDisplay appletalk icmpRouterDiscovery cacheDisplay snmp rip analyzer ping script statistics logout To remove an IP multicast tunnel: 1 From the top level of the Administration Console, enter: ip multicast tunnel remove 2 Enter the slot(s) of the switching module for which
Displaying Routes A-9 The following display shows all available multicast routes: Multicast Routing Table (2598 entries) Origin-Subnet From-Gateway Metric Tmr 157.88.29.1/32 137.39.229.98 18 25 137.39.2.254/32 137.39.229.98 5 25 131.215.125.236/32 137.39.229.98 14 25 130.118.106.254/32 137.39.229.98 10 25 129.127.118.12/32 137.39.229.98 10 25 129.127.110.12/32 137.39.229.98 10 25 129.127.110.11/32 137.39.229.98 13 25 129.127.110.5/32 137.39.229.98 10 25 129.95.63.12/32 137.39.229.98 13 25 129.95.63.
A-10 APPENDIX A: IP MULTICAST ROUTING Displaying the Multicast Cache The multicast cache contains the IP source address and destination address for packets observed on the system. The multicast cache shows you how information is routed over interfaces and ports in your system.
Displaying the Multicast Cache The following display shows the multicast cache configuration: Multicast Routing Cache Table (125 entries) Origin Mcast-group CTmr Age PTmr In-If >202.242.133.128/26 224.2.0.1 202.242.133.139 2 packets >128.84.247/24 224.2.0.1 128.84.247.53 43 packets 128.84.247.156 33 packets >128.138.213/24 224.2.0.1 128.138.213.1 23 packets >128.206.212/24 224.2.0.1 128.206.212.69 8 packets >131.136.234/24 224.2.0.1 131.136.234.103 12 packets >138.39.25/24 224.2.0.1 138.39.25.
A-12 APPENDIX A: IP MULTICAST ROUTING Table A-2 describes the fields in the CacheDisplay. Table A-2 Field Attributes for the CacheDisplay Field Description Origin The source of the incoming packets. Entries preceded by an angle bracket (>) indicate a multicast subnetwork. Entries without an angle bracket beneath subnetwork entries are multicast routers within that subnetwork.
REMOTE MONITORING (RMON) TECHNOLOGY B This appendix provides an overview of RMON and describes the specific CoreBuilder™ RMON implementation. What Is RMON? The Remote Monitoring (RMON) Management Information Base (MIB) provides a way to monitor and analyze a local area network LAN from a remote location. RMON is defined by the Internet Engineering Task Force (IETF) in documents RFC 1271 and RFC 1757.
B-2 APPENDIX B: REMOTE MONITORING (RMON) TECHNOLOGY Benefits of RMON Traditional network management applications poll network devices such as switches, bridges, and routers at regular intervals from a network management console. The console gathers statistics, identifies trends, and can highlight network events. The console polls network devices constantly to determine if the network is within its normal operating conditions.
RMON Groups RMON Groups B-3 The CoreBuilder system supports seven of the RMON groups defined by the Internet Engineering Task Force (IETF). Table B-1 lists these supported groups. Table B-1 RMON Groups Supported in the CoreBuilder System RMON/FDDI Groups Group Group Number Statistics 1 Maintains utilization and error statistics for the segment being monitored History 2 Gathers and stores periodic statistical samples from the statistics group.
B-4 APPENDIX B: REMOTE MONITORING (RMON) TECHNOLOGY Statistics and axFDDI Groups The Statistics group records frame statistics for Ethernet and FDDI interfaces.
RMON Groups B-5 The History group records periodic statistical samples from the network and stores them for retrieval at another time.
B-6 APPENDIX B: REMOTE MONITORING (RMON) TECHNOLOGY When you disable a port, the application might not update some of the statistics counters associated with it. An alarm calculates the difference in counter values over a set time interval and remembers the high and low values. When the value of a counter exceeds a preset threshold, the alarm reports this occurrence.
RMON Groups B-7 You can associate an alarm with the high threshold, the low threshold, or both. The actions taken because of an alarm depend on the network management application. RMON Hysteresis Mechanism The RMON hysteresis mechanism provides a way to prevent small fluctuations in counter values from causing alarms. This mechanism generates an alarm only under the following conditions: ■ The counter value exceeds the high threshold after previously falling below the low threshold.
B-8 APPENDIX B: REMOTE MONITORING (RMON) TECHNOLOGY The HostTopN group prepares reports describing hosts that top a list ordered by one of their statistics. Information from this group includes: HostTopN Group ■ Number of received packets ■ Number of transmitted packets ■ Number of received octets ■ Number of transmitted octets ■ Number of transmitted broadcast packets ■ Number of transmitted multicast packets The Matrix group records statistics on conversations between sets of addresses.
Management Information Base (MIB) B-9 The CoreBuilder system associates statistics with individual ports and then takes action based on these statistics. For example, the system can generate a log event and send an RMON trap if errors on a port exceed a user-set threshold. You must assign an IP address to the CoreBuilder system to manage RMON. See the CoreBuilder 6000 Administration Console User Guide for information on how to assign an IP address.
B-10 APPENDIX B: REMOTE MONITORING (RMON) TECHNOLOGY The data in the MIB consists of objects that represent features of the equipment that an agent can control and manage. Examples of objects in the MIB include a port that you can enable or disable and a counter that you can read. MIB Objects A counter is a common type of MIB object used by RMON. A counter object might record the number of frames transmitted onto the network.
VLANS ON THE COREBUILDER SYSTEM C This appendix contains: ■ A description of Virtual LAN (VLAN) concepts and their operational aspects in the CoreBuilder™ 6000 system ■ Examples of VLAN configurations About VLANs The VLAN concept in LAN technology helps minimize broadcast and multicast traffic. It also makes end-station moves, adds, and changes easier for the network administrator.
C-2 APPENDIX C: VLANS ON THE COREBUILDER SYSTEM Port Group VLANs Port group VLANs group together one or more switch ports. This simple implementation of VLANs requires little configuration. All frames received on a port are grouped together. For example, all frames received on a port that is part of a port group are kept within that port group, regardless of the data contained in the frames. Port groups are useful when traffic patterns are known to be directly associated with particular ports.
About VLANs C-3 Protocol-Sensitive VLANS When the CoreBuilder system receives data that has a broadcast, multicast, or unknown destination address, it forwards the data to all ports. This process is referred to as bridge flooding. Protocol-sensitive VLANs group one or more switch ports together for a specified network layer 3 protocol, such as IP or AppleTalk. These VLANs make flooding decisions based on the network layer protocol of the frame.
C-4 APPENDIX C: VLANS ON THE COREBUILDER SYSTEM Table C-1 Supported Protocols for VLAN Configuration Protocol Suite Protocol Types IP IP, ARP, RARP (Ethertype, SNAP PID) Novell IPX IPX (Ethertype, DSAP, SNAP PID) AppleTalk DDP, AARP (Ethertype, SNAP PID) Xerox XNS XNS IDP, XNS Address Translation, XNS Compatibility (Ethertype, SNAP PID) DECnet DEC MOP, DEC Phase IV, DEC LAT, DEC LAVC (Ethertype, SNAP PID) SNA SNA Services over Ethernet (Ethertype) Banyan VINES Banyan (Ethertype, DSAP, SNAP
About VLANs C-5 Modifying the Default VLAN New switch ports can dynamically appear in the CoreBuilder system if you insert a new switching module (FESM, FSM). When a new switch port that is not part of a default VLAN appears in the system at initialization, the system software adds that switch port to the first default VLAN defined in the system. CoreBuilder VLANs also allow you to modify the initial default VLAN to form two or more subsets of switch ports.
C-6 APPENDIX C: VLANS ON THE COREBUILDER SYSTEM This example shows how flooding decisions are made according to VLANs set up by protocol (assuming an 18-port switch): VLAN Exception Flooding Index VLAN Ports 1 Default 1 - 18 2 IP 1 - 12 3 IPX 11 - 16 Data received on Is flooded on Because IP - port 1 VLAN 2 IP data received matches IP VLAN on the source port. IPX - port 11 VLAN 3 IPX data received matches IPX VLAN on the source port.
About VLANs Overlapped IP VLANs C-7 The CoreBuilder system also gives you the ability to assign network layer information to IP VLANs. This capability allows network administrators to manage their VLANs by subnetwork. Flooding decisions are made by first matching the incoming frame using the protocol (IP) and then matching it with layer 3 subnetwork information. If received data is IP but does not match any defined IP subnetwork VLAN, it is flooded within all IP VLANs using the relevant switch port.
C-8 APPENDIX C: VLANS ON THE COREBUILDER SYSTEM Routing Between VLANs The only way for stations that are in two different VLANs to communicate is to route between them. The CoreBuilder system supports internal routing among IP, IPX, and AppleTalk VLANs. If VLANs are configured for other routable network layer protocols, they can communicate between them only via an external router. The CoreBuilder routing model lets you configure routing protocol interfaces based on a VLAN defined for that protocol.
ADMINISTERING VLANS D This appendix describes how to display information about VLANs and how to configure VLANs.
D-2 APPENDIX D: ADMINISTERING VLANS Example of a summary display for several VLANs: Select menu option (bridge/vlan): summary Select bridge(s) by slot (2-3,5,7,12|all): 2 Index Protocol Identifier Ports 1 default 0 1-18 Index 1 Name Layer 3 none Example of a detailed display for the VLANs: Select menu option (bridge/vlan): detail Index Protocol Identifier Ports 1 default 0 1-18 Index 1 Name none Index inPackets 1 54 Layer 3 inBytes 7654 outPackets 54 outBytes 6897
Displaying VLAN Information D-3 Table D-1describes these statistics.
D-4 APPENDIX D: ADMINISTERING VLANS Defining VLAN Information for a Traditional Bridge Top-Level Menu system ethernet fddi display tokenring mode ➧ bridge lowLatency ip ipFragmentation ipx ipxSnapTranslation appletalk trFDDIMode snmp addressThreshold analyzer agingTime summary script stpState detail logout stpPriority ➧ define stpMaxAge modify stpHelloTIme remove stpForwardDelay stpGroupAddress srBridgeNumber port packetFilter ➧ vlan Follow these steps to create a VLAN definition for a traditional bridge
Defining VLAN Information for an HSI Switch Engine D-5 9 Enter the subnetwork mask. Example: menu option (bridge/vlan): define Select bridge(s) by slot (2-3,5,7,9-12) [2]: 5 Enter Protocol Suite (IP,IPX,Apple,XNS,DECnet,SNA, Vines,X.25,NetBIOS,default): IP Enter Integer VLAN Identifier: 1 Enter VLAN Name: SD Marketing Ports 1-2=FDDI, 3-18=Ethernet Enter port(s) (1-18|all): 1,3-5 Layer 3 Address (undefined, defined): defined Enter IP Subnet Address: 158.111.122.0 Enter subnet mask [255.255.0.0] 255.255.
D-6 APPENDIX D: ADMINISTERING VLANS If you did not choose the IP protocol suite for this VLAN, you have completed the steps for defining the VLAN. 7 If you have selected the IP protocol suite and want to use the Layer 3 address information, enter defined for layer 3 addressing. Enter undefined if you do not want layer 3 addressing.
Modifying VLAN Information Modifying VLAN Information To modify VLAN information for a traditional bridge: Top-Level Menu system ethernet fddi display tokenring mode ➧ bridge lowLatency ip ipFragmentation ipx ipxSnapTranslation appletalk trFDDIMode snmp addressThreshold analyzer agingTime summary script stpState detail logout stpPriority define stpMaxAge ➧ modify stpHelloTIme stpForwardDelay remove stpGroupAddress srBridgeNumber port packetFilter ➧ vlan 1 From the top level of the Administration Console
D-8 APPENDIX D: ADMINISTERING VLANS Removing VLAN Information Top-Level Menu system ethernet fddi display tokenring mode ➧ bridge lowLatency ip ipFragmentation ipx ipxSnapTranslation appletalk trFDDIMode snmp addressThreshold analyzer agingTime summary script stpState detail logout stpPriority define stpMaxAge modify stpHelloTIme ➧ remove stpForwardDelay stpGroupAddress srBridgeNumber port packetFilter ➧ vlan Follow these steps to remove a VLAN definition: 1 From the top level of the Administration Conso
E TECHNICAL SUPPORT 3Com provides easy access to technical support information through a variety of services. This appendix describes these services. Information contained in this appendix is correct at time of publication. For the very latest, we recommend that you access 3Com Corporation’s World Wide Web site.
E-2 APPENDIX E: TECHNICAL SUPPORT Access by Analog Modem To reach the service by modem, set your modem to 8 data bits, no parity, and 1 stop bit.
Support from Your Network Supplier E-3 Local access numbers are available within the following countries: 3ComForum on CompuServe Online Service Country Telephone Number Country Telephone Number Australia 1800 123 853 Netherlands 0800 0228049 Belgium 0800 71279 Norway 800 11062 Denmark 800 17319 Portugal 0505 442 607 Finland 98 001 4444 Russia (Moscow only) 956 0815 France 0800 908158 Spain 900 964 445 Germany 0130 81 80 63 Sweden 020 792954 Italy 1678 99085 U.K.
E-4 APPENDIX E: TECHNICAL SUPPORT Support from 3Com If you are unable to receive support from your network supplier, technical support contracts are available from 3Com. Contact your local 3Com sales office to find your authorized service provider using one of these numbers: Regional Sales Office 3Com Corporation P.O. Box 58145 5400 Bayfront Plaza Santa Clara, California 95052-8145 U.S.A. 3Com Asia Limited Australia Telephone Number 800 NET 3Com Singapore Taiwan, R.O.C.
Returning Products for Repair Returning Products for Repair E-5 Before you send a product directly to 3Com for repair, you must first obtain a Return Materials Authorization (RMA) number. Products sent to 3Com without RMA numbers will be returned to the sender unopened, at the sender’s expense. To obtain an RMA number, call or fax: Country Telephone Number Fax Number U.S.A.
3Com Corporation LIMITED WARRANTY The duration of the warranty for the CoreBuilder™ 6000 Extended Switching Software, 3C96270B2, is ninety (90) days.
LIMITATION OF LIABILITY TO THE FULL EXTENT ALLOWED BY LAW, 3COM ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF INFORMATION OR DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF
