:
Programming flash memory block 1...
Programming flash memory block 2...
Programming flash memory block 3...
.
.
.
Programming flash memory block 31...
Installation complete.
The system menu reappears.
If the LANplex executable software image stored in FLASH is corrupted (for example, when a power failure occurs while you are updating software), contact 3Com Technical Support.
6 Unlock the Administration Console to allow users to log in remotely via telnet.
From the top level of the Administration Console, enter:
system consoleLock
You are asked for a value:
Enter new value (off, on) [off]:
7 Enter off
8 To reboot the system to use the newly loaded software, enter:
system reboot
You are prompted with the following message:
Are you sure you want to reboot the system (n,y) [y]:
9 At the prompt, enter y (yes).
You are now ready to configure management access for your system. For information on configuring management access for the LANplex system, see the LANplex 2500 Getting Started guide.
User Documentation
This version of software is compatible with the documentation revisions listed here. These release notes describe only the changes and additions to this documentation.
These documents comprise the LANplex 2500 documentation set, which ships with each system (3C92000A). These release notes describe the changes and additions to this documentation.
o LANplex 2500 Getting Started (Rev. 03, Part No. 801-00335-000)
o LANplex 2500 Operation Guide (Rev. 03, Part No. 801-00344-000)
o LANplex 2500 Administration Console User Guide (Rev. 03, Part No. 801-00322-000)
o LANplex 2500 Extended Switching User Guide (Rev. 02, Part No. 801-00345-000)
o LANplex 2500 Command Quick Reference (Rev. 02, Part No. 801-00319-000)
The appropriate module installation guide is shipped with each module:
o Ethernet RJ-21 Module Installation Guide, 2500/2016
(Rev. 02, Part No. 801-00118-000)
o Ethernet RJ-45 Module Installation Guide, 2500/2016
(Rev. 02, Part No. 801-00094-000)
o Ethernet 10BASE-FL Module Installation Guide, 2500/2016
(Rev. 03, Part No. 801-00325-000)
o Ethernet 10BASE-2 (BNC) Module Installation Guide, 2500/2016
(Rev. 01, Part No. 801-00217-000)
o Ethernet 10BASE-5 (AUI) Module Installation Guide, 2500/2016
(Rev. 01, Part No. 801-00218-000)
o FDDI DAS MIC (MMF) Module Installation Guide, 2500
(Rev. 01, Part No. 801-00096-000)
o FDDI DAS MIC (SMF) Module Installation Guide, 2500
(Rev. 01, Part No. 801-00153-000)
o TP-DDI DAS Module Installation Guide, 2500
(Rev. 01, Part No. 801-00265-000)
o 100BASE-TX Fast Ethernet Module Installation Guide (Rev. 01, Part No. 801-00294-000)
o 100BASE-FX Fast Ethernet Module Installation Guide (Rev. 01, Part No. 801-00304-000)
o ATM Module Installation Guide (Rev. 01, Part No. 801-00324-000)
Whats New at Revision 8.1.1?
This section describes the new features, software enhancements, or corrections that were implemented at this release of revision 8.1.1.
New Features
The following features have been added at this release of revision 8.1.1:
Support for the Asynchronous Transfer Mode (ATM) Switching Module
Revision 8.1.1 of LANplex software supports the new LANplex 2500 ATM switching module, which provides a single OC-3 155Mbps interface (multimode fiber) into a high-speed slot. In the LANplex 2500 system, you can mix and match two high-speed modules in the following configurations: ATM and FDDI, ATM and 100BASE-T, 100BASE-T and 100BASE-T, FDDI and 100BASE-T, and FDDI and FDDI.
The LANplex 2500 ATM switching module is designed to be fully interoperable with 3Com's ATM switches (CELLplexTM 7000) as well as other switches that comply with industry standards (UNI 3.0; LANE 1.0; Classical IP RFC 1577).
The LANplex 2500 ATM module supports these features:
o UNI 3.0 signaling
o LAN Emulation 1.0 (including LES/BUS services) 14
Emulated LANs (ELANs)
o Configuring a LANplex via a LAN Emulation Configuration Server (LECS)
o Classical IP over ATM (RFC 1577)
o ATMARP Server implementation (up to 8)
o Dynamic configuration of Emulated LANs (ELANs)
o A maximum of 1024 Virtual Circuits (VCs) per system
o Management:
-- UME Address registration
-- MIBs: ILMI, AToM, LEC, SONET
o Virtual LANs
o LANplex High-Function Switching (including IP, IPX, and AppleTalk routing)
For more information about administering ATM on the LANplex system, see Appendix A.
Support for Enhanced Layer 3 Virtual LANs
Revision 8.1.1 of LANplex software offers enhanced Layer 3 Virtual LAN (VLAN) support, allowing you to define Layer 3 VLANs based on the network protocol, including IP, IPX, AppleTalk®, DECnetTM, DECLATTM, SNA®, Banyan Vines®, and NetBIOS protocols. This release also allows for overlapping of VLANs by supporting multiple protocols per port and multiple IP subnets per port, as well as the spanning of layer 3 networks across multiple ports. An external router can also be used to allow communication between VLANs. For more information about Virtual LANs, see Appendix B: Administering VLANs.
Support for RMON
Revision 8.1.1 of LANplex Extended Switching software offers Full-Time Embedded RMON support for Ethernet ports through SNMP for four RMON groups. When combined with the Roving Analysis Port (RAP) function, RMON support for these four groups provides a comprehensive, powerful mechanism for managing your network. Revision 8.1.1 supports these RMON groups:
o Statistics Group (group 1) Maintains utilization and error statistics for the segment being monitored.
o History Group (group 2) Holds periodic, statistical samples from the statistics group and stores them for later retrieval.
o Alarm Group (group 3) Allows you to define thresholds for any MIB variable and trigger an alarm.
o Events Group (group 9) Allows you to define actions based on group 3 alarms, such as generate traps, log alarms, or both.
The RMON MIB contains standard MIB variables defined to collect comprehensive network statistics to alert a network administrator to significant network events. If the Embedded RMON agent operates full time, it collects data on the correct port at the time the relevant network event occurs.
You must assign an IP address to the LANplex system to manage RMON. See the Administration Console User Guide for information on how to assign an IP address.
Configuring the RMON state of etherStatsStatus, historyControlStatus, alarmStatus, and eventStatus from non-existent state to underCreation can now be performed by setting "valid".
RMON MIB Support added
RMON MIB support has been added for:
o Statistics
o History
o Alarm
o Events
IP Interface Configuration Change
The way you define an IP interface has changed. Instructions for defining a logical IP subnet (LIS) interface (using Classical IP over ATM) and an IP VLAN interface are shown below. The method of viewing an IP interface display and summary has also changed. For information on viewing the IP interface display and summary, see "Displaying Interfaces".
Defining a Logical IP Subnet Interface
When you define an IP LIS interface, you specify several general IP interface characteristics and IP LIS characteristics.
Before you define an IP LIS interface with switched virtual circuits (SVCs), be sure you have defined an ATM ARP server as described in the section Administering Classical IP and ARP over ATM in Appendix A: Administering ATM. If the LIS interface has only permanent virtual circuits (PVCs), you do not need to define an ATM ARP server.
To define an IP interface:
1 From the top level of the Administration Console, enter:
ip interface define
The Console prompts you for the interfaces parameters. To use the value in brackets, press [Return] at the prompt.
2 Enter the IP address of the interface.
3 Enter the subnet mask of the network to which the interface is to be connected.
4 Enter the cost value of the interface.
5 Enter the type of IP interface: LIS
6 Enter the advertisement addresses for this interface. You can enter up to 32 advertisement addresses for each interface. (The maximum number on the LANplex system is 64.)
You may enter one or more addresses, and the router will send advertisements to each of these addresses. They may be broadcast addresses, individual addresses, or any combination. In most cases, you will configure VLAN interfaces with a single broadcast address and LIS interfaces with a list of individual addresses of other routers in the ATM network. Addresses must be separated by commas (,). The default address is a broadcast address.
7 Enter the LIS information:
-- For a LIS interface with SVCs, enter the ATM ARP server address, the maximum SVC count, the inactivity timer, the minimum holding time, and the ATM port associated with the interface. (You can also accept the defaults for these values.)
The maximum number of SVCs is the maximum number of SVCs you want to be configurable on the LIS. The inactivity time is the maximum time a circuit is open with no activity before being released. The holding time is the minimum time the connection remains open after the connection has been established.
-- For a LIS interface with only PVCs, enter the ATM port and the PVCs associated with the interface. You can enter up to 51 PVCs for each interface. (The maximum number on the LANplex system is 64.)
LIS interface example with both PVCs and SVCs:
Enter IP address: 158.101.1.1
Enter subnet mask [255.255.0.0]: 255.255.255.0
Enter cost [1]:
Enter interface type (vlan,lis) [lis]:
Enter advertisement address(es) []: 158.101.1.255
Enter ATM arp server address
[00-0000-00-000000-0000-0000-0000-000000000000-00]:47-0000-00-000000-000-0-0000-00cc-000000000001-ff
Accept completed ATM address (yes,no) [yes]:
Enter max. SVC count (0=no max.) [0]:
Enter inactivity time (0=infinite, 10-10000) seconds [1200]:
Enter min. holding time (0-10000) seconds [60]:
Select ATM port [1]:
Enter PVC(s) (VPI/VCI)[]: 1/32,1/200,1/3330
Defining an IP VLAN Interface
When you define an IP VLAN interface, you specify several interface characteristics, as well as the index of the VLAN associated with the interface.
You must first define a VLAN, as described in Appendix B: Administering VLANs, before you define an associated IP VLAN interface.
To define an IP VLAN interface:
1 From the top level of the Administration Console, enter:
ip interface define
The Console prompts you for the interfaces parameters. To use the value in brackets, press [Return] at the prompt.
2 Enter the IP address of the interface.
3 Enter the subnet mask of the network to which the interface is to be connected.
4 Enter the cost value of the interface.
5 Enter the type of IP interface: VLAN.
6 Enter the advertisement address for this interface.
The parameter broadcast address in IP interface define has been changed to advertisement address(es) primarily to support non-broadcast networks, such as ATM.
You may enter one or more addresses, and the router will send advertisements to each of these addresses. They may be broadcast addresses, individual addresses, or any combination. In most cases, you will configure VLAN interfaces with a single broadcast address and LIS interfaces with a list of individual addresses of other routers in the ATM network. Addresses must be separated by commas (,). The default address is a broadcast address. A total of 32 advertisement addresses may be added, and a maximum of 64 advertisement addresses may be defined on the system.
7 Enter the index of the VLAN associated with the interface.
Example:
Enter IP address: 158.101.1.1
Enter subnet mask [255.255.0.0]: 255.255.255.0
Enter cost [1]:
Enter interface type (vlan, lis) [vlan]:
Enter advertisement address(es) [158.101.1.255]:
IP VLANs:
Index Ports
3 1-8
4 9-12
Select VLAN index: 3
If you physically change the configuration of your system after defining IP interfaces, the ports designated for those interfaces might no longer be valid and you may need to reconfigure your interfaces.
Displaying Interfaces
You can display both summary and detailed information about all IP interfaces configured for each switching module in the system. The detail display contains all the summary information as well as information about the advertisement address, PVCs, and VLANs.
To display IP interface summary information:
1 From the Administration Console top-level menu, enter:
ip interface summary
OR
ip interface detail
2 Select the interface index(es) all.
Enabling and Disabling ICMP Router Discovery
The Internet Control Message Protocol (ICMP) Router Discovery protocol (RFC 1256) allows an appropriately configured end-station to locate one or more routers on the LAN to which it is attached. The end-station then automatically installs a default route to each of the routers running ICMP Router Discovery protocol. You do not need to manually configure a default route. While IP traffic may initially be directed to any of the routers on the LAN, ICMP redirect messages will subsequently channel the IP traffic to the correct router.
Only certain end-stations, such as SolarisTM workstations, can be configured to work with the ICMP Router Discovery protocol. Refer to the documentation for your workstation to determine whether you can configure it to work with this protocol.
To enable ICMP Router Discovery, from the top level of the Administration Console, enter
ip icmpRouterDiscovery
Enter the ICMP Router Discovery mode (enabled or disabled). This protocol is disabled by default.
State Field Added to the Interface Display
A new field, state, has been added to the interface display table, allowing you to view the state of all interfaces configured for each switching module in the system.
The interface state is determined based on the state of all ports within the VLAN associated with the interface. For IP or IPX, the state displayed will be either up or down.
The interface state is displayed as down if:
-- No port in the defined VLAN interface, including those in overlapping subnets, has established link status. Link status is not established for FDDI DAS ports when neither the A nor the B port has established link status.
The interface state is displayed as up if:
-- One or more ports in the defined VLAN interface, including those in overlapping subnets, have established link status
-- Address Registration has successfully completed for all ATM ports using Classical IP over ATM or LAN Emulation.
-- The LAN Emulation Client (LEC) is in the operational state when using LAN Emulation.
As the interface state changes, transitions are reflected in the corresponding tables for all directly connected and associated routes as shown in Table 2.
Table 2 Interface Display Table Updates
|
IP |
IPX |
AppleTalk |
|
Routing Table
Static Route Table |
Routing Table
Server Table |
Routing Table |
IPX transitions time out immediately. For IP and AppleTalk transitions, all routes associated with the interface time out in the same manner as do learned routes that are not updated.
If link status is transitioned, previously defined configurations, such as static routes, do not have to be redefined.
Parameter Change: Broadcast Address Changed to Advertisement Address(es)
The parameter broadcast address in IP interface define has been changed to advertisement address(es) primarily to support non broadcast networks, such as ATM.
Previously, a broadcast address was configured for each IP interface. The router used this IP address as the destination address for advertisements, such as RIP updates. You may now enter one or more addresses, and the router will send advertisements to each of these addresses. There is no restriction on the addresses. They may be broadcast addresses, individual addresses, or any combination. In most cases, you will configure VLAN interfaces with a single broadcast address and Classical IP LIS interfaces with a list of individual addresses of other routers in the ATM network. Addresses must be separated by commas (,). A total of 32 advertisement addresses may be added, and a maximum of 64 advertisement addresses may be defined on the system.
System upTime Menu Added
You can display the time in minutes, hours, and days since the last system reboot.
To display system upTime:
1 From the top level of the Administration Console, enter:
system upTime
System upTime is displayed.
LANplex MIB Support Updates Added
LANplex MIB support has been added for:
o File transfer of Flash and NVRAM images
o Enhanced FDDI MAC and port configuration
o SNMP community string configuration
o Control panel access lock
o Remote console session lock
o Console password configuration
o Date and time configuration
o FDDI backplane station mode configuration
IF.MIB Added
The if.mib has been added at this release. This MIB supports:
o ifStackTable
o ifXTable
-- ifName
-- ifLinkUpDownTrapEnable
ATM.MIB Added
-- The atm.mib has been added at this release.
VLAN.MIB Added
-- A 3Com vlan.mib has been added at this release.
Removing Spanning Tree Protocol (STP) on a Per Port Basis
You may now remove ports from the Spanning Tree operation on a per port basis. Ports removed from STP will not participate in the STP operation but will continue to forward data. Previously, ports could be enabled or disabled. For more information on administering STP bridge port parameters, see the LANplex 2500 Administration Console User Guide.
New System Software Installation Procedure for MS-DOS®
The system software installation procedure for MS-DOS® at revision 8.1.1 requires the Windows 95 or Windows NT operating software. See "Copying to the MS-DOS® Platform" for the new installation procedure.
Software Changes and Corrections
This section describes software changes and corrections implemented at this release:
o Configurations with multiple IPX interfaces now properly forward IPX NetBIOS frames.
o The telnet timeout interval can now be configured to a number between 1 and 60 minutes. Previously this could be configured to a number between 30 and 60 minutes.
System Issues
The following system issues are identified at this release:
o An ATM LEC cannot be configured as the backbone port in Express Switching mode.
o The configuration of two ATM modules in a single chassis is not supported at this release.
o At this release, when a ping is initiated from a LANplex 2500 system and is destined to an ATM device with a specific ATM adapter card, multiple pings are required for communication to be initiated. This is due to the amount of time required for the adapter card to resolve ATM ARP.
o At this release, when the ILMI autoconfig option is enabled on a 3Com CELLplex switch, it could take approximately 6 minutes for a LEC to join an emulated LAN.
o At this release, when a VLAN is created with the Transcend® Network Management application, all VLAN statistics and the VLAN ID remain at zero until a system reboot is performed.
o Not enough storage space exists for you to define VLANs for all 10 protocol types. If you use DECnet, XNS VLANS or both, you can define between 6 and 9 protocol types.
o A maximum of 32 routing interfaces (IP VLAN or Classical IP LIS interfaces) can be configured in a single LANplex 2500 system.
o When connected to the MBONE, the Internets multicast backbone, a combined maximum of 32 IP multicast tunnels and IP interfaces can be configured on a revision 8.x motherboard.
o Roving analysis frames over a remote Fast Ethernet connection are truncated if greater than 1495 bytes.
o Packet filters can access packet data through byte 64 in the packet.
o Packet filtering is not available on frames that will be routed by the LANplex software.
o When configuring multiple permanent virtual circuits (PVCs) for a logical IP subnet (LIS) interface, do not add spaces after the comma to separate the list of PVCs. Any PVCs added after the space will be ignored.
o The ipDefaultTTL MIB variable cannot be set.
o You may not install LANplex system software earlier than version 7.0.0 on a revision 8.0 motherboard after software revision 7.0.0 or later has been installed. To see if you have a revision 8.0 motherboard in your system:
-- At the top level of the Administration Console, enter: system display. The first line of the display shows the product name and, in parentheses, the motherboards revision number.
Known Problems
The following software problems are identified at this release:
o The LANplex will not route FDDI multicast frames larger than 1500 bytes (that is, frames that require fragmentation).
o The FCS error statistics report inaccurate values on the Fast Ethernet port.
o After setting a system baseline, ATM LEC bridge statistics will be incorrect.
o Before enabling Express Switching mode, you must disable the backbone port. Then, after enabling Express Switching mode, re-enable the backbone port.
o After modifying an existing IP multicast configuration, you must reboot the LANplex system.
o The roving analyzer port (RAP) bridge-transmit frame statistic is incorrect.
o Roving Analysis is not supported on the LANplex 2500 when an ATM card is present in the chassis.
o Remote Roving Analysis is not supported over a Fast Ethernet connection with Spanning Tree enabled.
o Roving Analysis is not supported on the LANplex 2500 when an ATM card is present in the chassis.
o Remote Roving Analysis is not supported over a Fast Ethernet connection with Spanning Tree Protocol (STP) enabled.
o When adding a permanent virtual connection (PVC), modifying an IP interface, or defining an IP interface, the following response is always displayed The PVC has been added. To view PVC information, enter ip interface detail from the top level of the Administration Console.
o Attempting to enter 33 VLANs, exceeding the maximum of 32 VLANs allowed, causes a system reset.
SNMP MIB Files
SNMP MIB files are shipped with the LANplex system software as ASN.1 files. Copies of ASN.1 files are provided for each of the supported compilers described at the end of this section.
Supported Versions
The SNMP MIB file names and the currently supported version of each MIB are listed here:
o atm.mib -- ATM MIB, RFC 1695
o bridge.mib -- Bridge MIB, RFC 1493
o ethernet.mib - Ethernet MIB, RFC 1398
o if.mib -- If MIB, RFC 1573
o fddiSmt7.mib -- FDDI SMT 7.3 MIB, RFC 1512
o lec.mib -- LEC MIB, af-lane-0044.00
o les.mib -- ATM MIB, af-lane-1129.001
o lp.mib -- LANplex Systems MIB, version 1.3.0
o lpOpFddi.mib -- LANplex Optional FDDI MIB, version 1.2.1
o mib2.mib -- MIB-II, RFC 1213
o rmon.mib -- RMON MIB, RFC 1757
o vlan.mib -- 3Com VLAN MIB
Compiler Support
ASN.1 MIB files are provided for each of the MIB compilers listed in this section. Any warnings or exceptions related to a compiler are listed with it.
o SMIC (version 1.0.9)
o MOSY (version 7.1)
For the MIB file lpOpFddi.mib, the MOSY compiler reports warnings for counter names that do not end in s. This report has no effect on the output produced by the MOSY compiler.
o HP Openview (version 3.1)
o mib2schema (with SunNet ManagerTM version 2.0)
The MIB file fddiSmt7.mib produces the following warning messages when compiled using mib2schema:
Translating....
Warning: The following INDEX entries in
fddimibMACCountersTable not resolved:
fddimibMACSMTIndex
fddimibMACIndex
Translation Complete.
Schema file in fddiSmt7.mib.schema
Oid file in fddiSmt7.mib.oid
These warning messages have no effect on the ability of SNM to use the schema file generated with SNM version 2.0 or later.
Revision History
Table 3 provides a brief description of the previous releases of the LANplex 2500 software.
Table 3 Revision History for LANplex 2500 Software
|
Revision Number |
Description of Release |
|
7.0.1 |
Maintenance release:
o Modification to LANplex operating software to eliminate operational issue with the third-party management processor |
|
7.0.0 |
New features:
o Support for the Fast Ethernet Module
o Support for the unterminated BNC module
o Support for IP Multicast
o Telnet and rlogin sessions will terminate after a user-specified time interval
o Configurable Spanning Tree Protocol (STP) group address
o Menu item change (ip forwarding now ip routing)
o Support for 64 IP static routes
o Menu item change: IPX frame types
o Ethernet Ports configurable as Express Switching Ports |
|
5.1.0 |
Maintenance release
Several bug fixes implemented |
|
5.0.0 |
New features:
o IPX Routing
o AppleTalk Routing |
|
4.3.0 |
New features:
o UDP Helper
o IPX Snap Translation |
|
4.2.0 |
New features:
o IP Routing implemented
o Support for the AUI and BNC Option Modules |
|
4.0.1 |
Maintenance release
Several bug fixes implemented |
|
4.0.0 |
First release of LANplex 2500 system software |
Technical Support
This section describes technical support information for 3Com products.
Support from Your Network Supplier
Many suppliers are authorized 3Com service partners who are qualified to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services.
When you contact your network supplier for assistance, have the following information ready:
o Diagnostic error messages
o A list of system hardware and software, including revision levels
o Details about recent configuration changes, if applicable
If you are unable to contact your network supplier, see the following section on how to contact 3Com.
Support from 3Com
If you are unable to receive support from your network supplier, technical support contracts are available from 3Com.
In the U.S. and Canada, call (800) 876-3266 for customer service.
If you are outside the U.S. and Canada, contact your local 3Com sales office to find your authorized service provider:
|
Country |
Telephone Number |
|
Country |
Telephone Number |
|
Australia* |
1800 678 515 |
|
Japan |
(81) (3) 3345 7251 |
|
Belgium** These numbers are toll-free. |
0800 71429 |
|
Mexico |
(525) 531 0591 |
|
Brazil |
(55) (11) 546 0869 |
|
Netherlands* |
06 0227788 |
|
Canada |
(905) 882 9964 |
|
Norway* |
800 11376 |
|
Denmark* |
800 17309 |
|
Singapore |
(65) 538 9368 |
|
Finland* |
0800 113153 |
|
South Africa |
(27) (11) 803 7404 |
|
France* |
05 917959 |
|
Spain* |
900 983125 |
|
Germany* |
0130 821502 |
|
Sweden* |
020 795482 |
|
Hong Kong |
(852) 868 9111 |
|
Taiwan |
(886) (2) 577 4352 |
|
Ireland* |
1 800 553117 |
|
United Arab Emirates |
(971) (4) 349049 |
|
Italy* |
1678 79489 |
|
U.K.* |
0800 966197 |
|
|
|
|
U.S. |
(1) (408) 492 1790 |
* These numbers are toll-free.
Returning Products for Repair
Before you send a product sent directly to 3Com for repair, you must first obtain a Return Materials Authorization (RMA) number. A product sent to 3Com without an RMA number will be returned to the sender unopened, at the senders expense.
To obtain an RMA number, call or fax:
|
Country |
Telephone Number |
Fax Number |
|
U.S. and Canada |
(800) 876 3266, option 2 |
(408) 764 7120 |
|
Europe |
31 30 60 29900, option 5 |
(44) (1442) 275822 |
|
Outside Europe, U.S., and Canada |
(1) (408) 492 1790 |
(1) (408) 764 7290 |
Appendix A
Administering ATM
This appendix describes how to administer asynchronous transfer mode (ATM) on the LANplex® 2500 system. It includes information about:
o LAN Emulation (LANE)
o Classical IP over ATM
o UNI Management Entity (UME)
o ATM ports
ATM in Your Network
ATM architecture differs fundamentally from IEEE 802.x technology. IEEE 802.x LANs, which are limited to FDDI, Ethernet, and token ring, are connectionless and use the Media Access Control (MAC) addresses in each packet to communicate to end-stations. ATM is connection-oriented and uses an circuit identifier, called a virtual channel identifier, to exchange data between two ATM stations over previously established virtual channel connection (VCC).
LAN Emulation and Classical IP
To forward data over an ATM interface in an existing network, two methods are provided to adapt existing network layer protocols to the connection-oriented paradigm of ATM. These methods are LAN Emulation (LANE) and Classical IP over ATM.
o LAN Emulation supports transparent translation of higher level protocols, such as IP, IPX, and AppleTalk. LANE also supports broadcast and multicast addressing.
o Classical IP over ATM supports transparent translation of IP only over ATM, and does not support broadcast or multicast addressing.
Before You Configure ATM
Before configuring ATM, you should:
o Check the ATM link status.
o Verify LANplex address registration is operational.
o Verify that signalling is operational.
Checking Link Status
To check the link status:
1 From the top level of the Administration Console, enter:
atm ume display
You are prompted for the number(s) of the UME you want to display.
2 Enter the number(s) of the UME(s) or all.
The state shown should be connected. If the state shown is disconnected, there is a problem with the link. If this happens, check the cabling to ensure that the system is correctly connected to the ATM switch.
Verifying Address Registration
After ensuring that the link is connected, verify that the LANplex is able to register addresses at both the network and user sides of the UME Network Interface (UNI). Two addresses --- one for LAN Emulation and one for Classical IP over ATM --- are registered at the network side.
To verify registered addresses:
1 From the top level of the Administration Console, enter:
atm ume list
You are prompted for the number(s) of the ATM port you want to list.
2 Enter the number(s) of the ports(s) or all.
Verifying Signaling
The ATM signaling protocol allows end-stations to establish, maintain, and clear ATM connections between endpoints via virtual connections (VCCs). Multiple virtual connections can exist on a physical link. There are two types of virtual connections: a virtual path and a virtual channel.
You can verify that signaling is operational by viewing the virtual connections --- virtual path identifiers (VPIs) and virtual channel identifiers (VCIs) that the LANplex has established.
To verify that UNI signaling is operational:
1 From the top level of the Administration Console, enter:
atm ports vcc list
In addition to newly defined VCCs, two additional VCCs are listed. These are reserved VPIs and VCIs which are used for signaling (VPI 0/VCI 5) and for the UME ILMI (VPI 0/VCI 16).
LAN Emulation
LAN Emulation (LANE) provides unicast, multicast, and broadcast network behavior over connection-oriented ATM. An emulated LAN (ELAN) can consist of many LAN emulation clients (LECs). An ELAN consists of the following components:
o A Broadcast and Unknown Server (BUS)
The BUS is responsible for handling broadcast, multicast, and initial unicast frames sent from a LAN Emulation Client. Each ELAN contains only one BUS.
o A LAN Emulation Server (LES)
The LES is responsible for registering and resolving MAC addresses to ATM addresses for LECs. Each ELAN contains only one LES.
o LAN Emulation Clients (LECs)
The LEC is the end node from the perspective of the ATM network. It performs data forwarding, address resolution, and other control functions. Additionally, it maintains the LAN emulation software.
A LES and a BUS must be defined as part of an ELAN before a LEC may be defined.
o A LAN Emulation Configuration Server (LECS)
The LECS provides configuration information about the ATM and LAN networks. It also provides the address of the LES to the LEC.
The LES and the BUS can be configured on the same LEC or on different LECs.
Eliminating Bridge Loops in ELAN Configurations
When configuring more than one LEC in a LANplex system, a bridge loop may be created. This possibility exists because the LANplex can bridge between all ports, including logical bridge ports (LECs).
Consider the following example:
o Two LANplex 2500 systems configured in the same ATM network with 2 LECs defined on each system.
o Two ELANs, called Marketing and Engineering, are configured in the ATM network and both LANplex 2500 systems have connections to each of these ELANs.
In this scenario, two bridge ports connect to the same location, causing a bridge loop. The result is the same as connecting two LANplex systems together via two Ethernet segments.
With Spanning Tree Protocol (STP) enabled, one of these ELANs would be blocked. In most cases this is not desired behavior because you might want to have multiple ELANs between switches. STP is off by default, we recommend the following procedure when you create multiple LECs with LANplex Extended Software:
1 Define the LECs, but leave them in the disabled state.
2 Reboot the system.
Once all the LECs are created, reboot the LANplex system to add the LECs to the bridge table.
3 Modify the default VLAN.
Remove all LECs from the default VLAN. Removing LECs from the default VLAN removes the possibility of a bridge loop. You may choose to allow one LEC to remain in the default VLAN. Leaving more than one LEC in the same default VLAN is not recommended unless Spanning Tree Protocol is enabled.
4 Enable the lecState of each LEC port from the atm lane lec modify menu.
Now that LECs are enabled and removed from the default VLAN, they will not flood any traffic.
5 Define new VLANs.
You may now create protocol-based VLANs which may or may not include LECs.
Creating an Emulated LAN
You can create an 802.3 emulated LAN on ATM by defining the LAN's servers (the BUS and the LES) and then configuring each LAN Emulation Client (LEC). See the section Virtual LANs for important information regarding LEC configuration.
To create an emulated LAN, follow these steps:
1 Determine the location of the BUS and LES.
You can define the BUS and LES in any LEC on the network, or on an ATM switch, such as 3Com's CELLplexTM 7000 system.
2 Define the Broadcast and Unknown Server (BUS).
3 Define the LAN Emulation Server (LES).
4 Define the LAN Emulation Clients (LEC).
The LANplex system supports Unspecified Bit Rate (UBR) only.
Virtual LANs
As LECs are created for the first time, they create a bridge port which becomes part of the LANplex default Virtual LAN (VLAN). Depending on the configuration of your network (that is, if multiple connections exist between a group of ports for a VLAN), the potential exists for bridge loops which may result in broadcast storms. To avoid this problem, either enable the Spanning Tree functionality of the bridge, or insure that duplicate connections between bridge ports are on different VLANs. This can be accomplished by creating multiple default VLANs per bridge. For information on how to configure protocol-sensitive VLANs, see Appendix B: Administering VLANs. Note that enabling Spanning Tree Protocol for the bridge may disable bridge ports that have duplicate connections between them.
Defining a Broadcast and Unknown Server (BUS)
When you define a Broadcast and Unknown Server, you provide information necessary to create an emulated LAN.
1 From the top level of the Administration Console, enter:
atm lane bus define
2 Enter the number of the ATM port to which the Broadcast and Unknown Server is connected.
3 Enter the BUS requested state for the next reboot.
After defining a BUS, make sure that the LANplex 2500 system is turned on and the ATM connection is working before attempting to define the LES and any clients.
Displaying a Broadcast and Unknown Server (BUS)
If the LANplex 2500 system is turned on and the ATM connection is up, the BUS is assigned an ATM address, which you need when you configure the LAN Emulation Server. To display this address, enter the following command from the top level of the Administration Console:
atm lane bus display
Defining a LAN Emulation Server (LES)
When you define a LAN Emulation Server, you provide information necessary to create an emulated LAN. A Broadcast and Unknown Server) must already be defined for the emulated LAN before you can define a LAN Emulation Server. See "Defining a Broadcast and Unknown Server (BUS)".
To define a LAN Emulation Server, take these steps:
1 From the top level of the Administration Console, enter:
atm lane les define
2 Enter the number of the ATM port to which the server is attached.
3 Enter the emulated LAN name.
Use the same emulated LAN name you entered when you defined the Broadcast and Unknown Server.
4 Enter the maximum frame size (1516 or 4544).
5 Enter the LES requested state for next reboot (disable or enable). The default is disable.
6 Enter the ATM address of the Broadcast and Unknown Server. Press [Return} to accept the default or existing choice in brackets.
If you do not know the ATM address of the Broadcast and Unknown Server, display the BUS information; use the value assigned to the busAddress attribute.
Example:
Select menu option (atm/lane/les): define
Select ATM port [1]:
Enter Elan Name []: Elan_1
Enter Elan Mtu (1516,4544) [4544]:
Enter LES requested state for next reboot (disable, enable) [disable]: enable
Enter BUS ATM Address:
Accept completed ATM address (yes, no) [yes]:
If you enter no, the system requests the BUS ATM address until you enter it. To exit this function and return to the previous menu item, type q.
Displaying a LAN Emulation Server (LES)
If the LANplex 2500 system is turned on and the ATM connection is up, the LES is assigned an ATM address, which you need when you manually configure each LAN Emulation Client. To display this address, enter the following command from the top level of the Administration Console:
atm lane les display
You do not need the LES address if using LECS services.
Configuring Clients to Join an Existing Emulated LAN
You can configure a LAN Emulation Client (LEC) to join an existing 802.3 emulated LAN by providing information about the LAN Emulation Server (LES) and the Broadcast and Unknown Server (BUS).
Defining LAN Emulation Clients
When you define a LAN Emulation Client, you give information necessary for a client to be included in the emulated LAN. A BUS and a LES must already be defined as part of the emulated LAN before you can define a client.
When the client attempts to join the emulated LAN, some of the configured information is carried along with the join request sent to the LES. The LES can alter this information. The client then has the option of accepting or rejecting any changes made by the LES. If the changes are accepted or if there are no changes, the client successfully joins the emulated LAN. Otherwise, the join fails.
To define a client:
1 From the top level of the Administration Console, enter:
atm lane lec define
2 Enter the number of the ATM port to which the client is attached.
You can attach only one LEC per port to the same emulated LAN.
3 Enter the LECS access type (lecs, manual) [LECS].
If you choose LECS as your means of joining an ELAN, and another LANplex provides LES and BUS services, you must update the directly attached ATM switch LECS with the ELAN name and the corresponding LES address.
4 Enter the name of the emulated LAN to which you are adding the client, or press [Return] to choose the default ELAN. The ELAN name may contain a maximum of 32 characters.
If you do not know the name of the emulated LAN, display the LES information (as described on "Displaying Information about a LAN Emulation Server" on the next page) and use the name assigned to the oprElanName attribute. You can only do this if the LES is configured on the same LANplex 2500 system. Otherwise, you must obtain the address for the device on which the LES is configured.
5 Enter the maximum transmission unit (MTU), also known as maximum frame size (Unspecified, 1516, or 4544).
All LECs within the same emulated LAN must have the same MTU size. Enter 1516 for Ethernet ports, for FDDI passing Ethernet traffic, or for FDDI using IP fragmentation. Enter 4544 for FDDI-to-FDDI traffic. Enter Unspecified to allow the LES to select an appropriate MTU size.
6 Enter enable for the enable state for the next reboot.
7 Repeat steps 1 through 6 to define other LECs.
8 Reboot to enable all newly defined LECs.
Example:
Select menu option (atm/lane/lec): define
Select ATM port [1]:
Enter LEC access type (lecs, manual) [lecs]:
Enter Elan Name []: Elan_1
Enter Elan MTU Size (Unspecified,1516,4544) [Unspecified]:
Enter Enable State for next reboot (disable, enable) [disable].
You must REBOOT to be able to modify the state of a newly created LEC.
When more than one LEC is defined in a LANplex system, a bridge loop can exist. For more information, see the section "Eliminating Bridge Loops in ELAN Configurations".
Administering LAN Emulation Clients
From the Administration Console you can:
o Display summary or detailed information about emulated LAN clients
o Modify information for emulated LAN clients
o Define a client for inclusion in an emulated LAN
o Remove a client from the network
Displaying Information About LAN Emulation Clients
You can display a summary report or a detailed report of information about LAN Emulation Clients. The summary displays information about the location and state and the most important statistics about the client's general activity. The detailed includes the summary information plus additional statistics.
To display information about a LAN Emulation Client:
1 From the top level of the Administration Console, enter:
atm lane lec summary
or
atm lane lec detail
You are prompted for the number of a LEC.
2 Specify the number of the LAN Emulation Client about which you want information.
The information is displayed in the format you specified.
Table A-1 describes the attributes of the LAN Emulation Client. References to
the ATM Forum Specification for LAN Emulation are listed in parentheses
following the parameter description.
Table A-1 LAN Emulation Client Attributes
|
Parameter |
Description |
|
arpAfterCt |
Number of unknown frames after which the client will send an
LE_ARP request |
|
busAddress |
ATM address of Broadcast and Unknown Server |
|
cfgAgeTime |
Requested maximum time that the client will maintain an entry
in its LE_ARP cache (C17) |
|
cfgArpRespTime |
Requested maximum time (in seconds) that the client expects
between an LE_ARP request and an LE_ARP response (C20) |
|
cfgConnCompTime |
Requested time during which data or a READY_IND message is
expected from a calling party (C28) |
|
cfgCtrlTimer |
Requested timeout period for request/response control frame
interactions (C7) |
|
cfgElanType |
Requested type of LAN to emulate (802.3) |
|
cfgElanMtu |
Requested maximum frame size |
|
cfgElanName |
Requested emulated LAN name |
|
cfgflushRspTime |
Requested time limit for receiving an LE_FLUSH_RESPONSE after
sending an LE_FLUSH_REQUEST (C21) |
|
cfgFwdDlyTime |
Requested maximum time the client will maintain an entry for a
non-local MAC address in its LE_ARP cache as long as the
topologyChgFlag is true (C18)q |
|
cfgLesAccessType |
Requested method for determining how to access the LAN
Emulation Server |
|
cfgLesAddr |
ATM address of requested LAN Emulation Server |
|
cfgMaxArpRtryCt |
Requested maximum number of LE_ARP attempts |
|
cfgMaxUnkFrmCt |
Requested maximum unknown frame count (C10) |
|
cfgPathSwDlyTime |
Requested time since sending a frame to the BUS after which
the client assumes that the frame has been discarded or
delivered (C22) |
|
cfgVccTime |
Requested time after which the client should release any data
direct VCC that did not transmit or receive data frames (C12) |
|
LesAccessType |
Current type of access to the LAN Emulation Server |
|
lecState |
Current client machine state |
|
location |
ATM port to which the client is connected |
|
ElanMtu |
Current maximum frame size |
|
ElanName |
Current emulated LAN name |
|
ElanType |
Type of LAN currently emulated (802.3) |
|
enabled |
Current management state of the client (disabled or enabled) |
|
inArpReqs |
Number of LE_ARP requests received |
|
inArpRsps |
Number of LE_ARP responses received |
|
inBus |
Number of frames transmitted to the Broadcast and Unknown Server |
|
inCtrls |
Number of control frames received |
|
inDds |
Number of frames received on data direct circuits |
|
lecAddress |
ATM address of client |
|
LesAddr |
ATM address of current LAN Emulation Server |
|
maxUnkFrmTime |
Requested time period during which the client will send no
more than the maximum number of unknown frames to the
Broadcast Unknown Server (BUS) for a given destination (C11) |
|
outCtrls |
Number of control frames transmitted |
|
outDds |
Number of frames transmitted on data direct circuits |
|
outArpReqs |
Number of LE_ARP requests transmitted |
|
outArpRsps |
Number of LE_ARP responses transmitted |
|
outBus |
Number of frames received from the Broadcast and Unknown Server |
|
outBusUcDscrds |
Number of unknown unicast frames thrown away by the
Broadcast and Unknown Server |
|
requestedState |
Requested management state of the client (disabled or enabled) |
|
topologyChgFlag |
Boolean value indicating that the client is using Forward Delay
Time rather than Aging Time to age non local entries in its LE_ARP
cache (C19) |
Modifying Information About LAN Emulation Clients
You may modify LAN Emulation Client parameters. T-notify:configuringTo modify these parameters, take these steps:
1 From the top level of the Administration Console, enter:
atm lane lec modify
You are prompted for the parameter you want to modify.
2 Enter the parameter.
You are prompted for the number(s) of the LEC(s) you want to modify.
3 Select the number(s) of the LEC(s) or all.
You are prompted for the new value of the option you selected.
4 Enter the new value.
If you modify the ELAN name in the LEC configuration, you must disable, and then enable, the LEC for the change to take effect.
Removing a LAN Emulation Client
To remove a client from the emulated LAN:
1 From the top level of the Administration Console, enter:
atm lane lec remove
You are prompted for the number of the LEC to remove.
2 Specify the number of the LEC to remove.
You are prompted to confirm the deletion.
3 Enter y to confirm or n to cancel. If you enter y, the system reboots and deletes the specified LEC.
Example:
Select menu option (atm/lane/lec): remove
Select ATM LEC(s) (1-3|all) [1]: 1
Delete LEC(s) resulting in system reboot?" (n,y) [y]: y
Administering a LAN Emulation Server
Each emulated LAN has one LAN Emulation Server (LES). This server coordinates the joining of clients to the emulated LAN.
Displaying Information about a LAN Emulation Server
When you display information about a LAN Emulation Server, you display values for the server's location, enabled state, ATM address, and other attributes.
To display information about a LES:
1 From the top level of the Administration Console, enter:
atm lane les display
2 Enter the number of the LAN Emulation Server (LES) about which you want information.
Table A-2 describes the parameters of the LAN Emulation Server.
Table A-2 LAN Emulation Server Attributes
|
Attribute |
Description |
|
BusAddress |
ATM address of current Broadcast and Unknown Server |
|
cfgBusAddress |
ATM address of requested Broadcast and Unknown Server |
|
cfgCtrlTime |
Requested timeout period for request/response control frame
interactions (C7) |
|
cfgElanName |
Requested emulated LAN name |
|
cfgElanMtu |
Requested maximum frame size |
|
cfgElanType |
Requested type of LAN to emulate (802.3) |
|
CtrlTime |
Current timeout period for request/response control frame
interactions (C7) |
|
ElanName |
Current emulated LAN name |
|
ElanMtu |
Current maximum frame size |
|
ElanType |
Type of LAN currently emulated (802.3) |
|
enabled |
Management state of the client (disabled or enabled) |
|
lesAddress |
ATM address of LAN Emulation Server |
|
location |
Port to which the LAN Emulation Server is connected |
Modifying Information About the LAN Emulation Server
You can modify LAN Emulation Server information, such as the emulated LAN name or the ATM address of the Broadcast and Unknown Server.
To modify information about the LAN Emulation Server, follow these steps:
1 From the top level of the Administration Console, enter:
atm lane les modify
You are prompted for an attribute.
2 Enter the attribute.
You are prompted for a LES to modify.
3 Enter the number of the LAN Emulation Server.
You are prompted for the new value of the option you selected.
4 Enter the new value for the selected attribute.
Example:
Select menu option (atm/lane/les/modify): elanMtu
Select LES (1-3|all) [1]: all
Enter new value (1516,4544) [4544]: 1516
Removing a LAN Emulation Server
To remove a LAN Emulation Server from the network, take these steps:
1 From the top level of the Administration Console, enter:
atm lane les remove
You are prompted for the number of an LES.
2 Enter the number of the LAN Emulation Server to remove.
Administering a Broadcast and Unknown Server
Each emulated LAN has one Broadcast and Unknown Server (BUS), which distributes frames destined for multiple end-stations.
Displaying Information About a Broadcast and Unknown Server
You can display values for a Broadcast and Unknown Server's location, management state, and ATM address. To display this information, take these steps:
1 From the top level of the Administration Console, enter:
atm lane bus display
If more than one BUS is defined, you are prompted to select one to display.
2 If prompted, select a Broadcast and Unknown Server to display.
The information is displayed.
Table A-3 describes the type of information provided about the ATM BUS.
Table A-3 Broadcast and Unknown Server Attributes
|
Attribute |
Description |
|
busAddress |
ATM address of the Broadcast and Unknown Server |
|
location |
Port to which the Broadcast and Unknown Server is connected |
|
requestedState |
Management state of the Broadcast and Unknown Server |
Enabling and Disabling BUS Management
To enable or disable management of the Broadcast and Unknown Server:
1 From the top level of the Administration Console, enter:
atm lane bus busState
If more than one BUS is defined, you are prompted to select one to display.
2 If prompted, select a Broadcast and Unknown Server to display.
3 Enter the new value for the management state (enabled or disabled).
Removing a Broadcast and Unknown Server
To remove a Broadcast and Unknown Server:
1 From the top level of the Administration Console, enter:
atm lane bus remove
You are prompted for the number of a BUS.
2 Enter the number of the Broadcast and Unknown Server to remove.
Administering Classical IP and ARP over ATM
The second method of adapting IP to the connection-oriented ATM paradigm is by means of Classical IP over ATM. This section describes the configuration of Classical IP over ATM Address Resolution Protocol (ATM ARP) in an Asynchronous Transfer Mode (ATM) network configured into several logical IP subnetworks (LISs).
About Classical IP
In a network environment where data is forwarded among Ethernet, FDDI, or token ring nodes, a router that receives a packet across a LAN interface forwards it using the Address Resolution Protocol (ARP). The ARP locates the destination Media Access Control (MAC) address corresponding to the destination IP address. Classical IP does not support broadcast or multicast traffic.
To forward data using Classical IP over an ATM interface, the node must first learn the ATM address for the corresponding IP address. The node can learn this address using a protocol known as Classical IP over ATM (RFC 1577).
Forwarding Over ATM
Classical IP over ATM uses a logical IP subnet (LIS) --- a group of IP nodes directly connected to a single ATM network and belonging to the same IP subnet --- to forward packets within the network environment. A LIS learns addresses via the ATM ARP server table.
Establishing an ATM ARP Server
Each ATM ARP server supports a single LIS. While multiple LISs can be connected to the same ATM network, each LIS operates independently of other LISs on the network. When you add a node to an LIS, you must define its IP address, its subnet mask, and the address of the ATM ARP server that supports it.
A maximum of 8 ATM ARP servers and a maximum of 32 LISs can be configured on a single LANplex 2500 system.
ATM ARP servers can be configured on a LANplex 2500 system even if that system is not part of the LIS it serves. ATM ARP servers do not respond to pings.
The ATM ARP server function can be provided on a workstation in the network, on any LANplex system with revision 8.1.0 or later extended software, or on an ATM switch.
The following sequence describes how the node IP and ATM addresses are learned and stored in the ATM ARP server table:
1 First, a node establishes a connection to the ATM ARP server.
2 The ATM ARP server then sends an inverse ATM ARP request to the node, requesting its IP and ATM addresses.
3 When this information is returned, it is stored --- or cached --- in the ATM ARP server table.
Forwarding to Nodes Within an LIS
Packets can be forwarded directly between nodes on the same LIS.
To forward a packet within the same LIS, the sending node requests a translation from the destination IP address to the corresponding ATM address from the ATM ARP server table with an ATM ARP request.
o If the destination address is known to the server, the server returns a message with this address.
o If the address is not known to the server, the server returns a message to advise the sending node and the packet is discarded.
When the server returns a destination address, the sending node uses this learned address to create a virtual circuit (VC) and to forward this and all subsequent packets to the destination address. The VC is added to the ARP cache of the sending node.
To display the ARP cache of the host, from the top level of the Administration Console, enter:
atm arp display
Forwarding to Nodes on Another LIS
Communication to nodes on a separate LIS is done via an IP router. This router can be configured as a member of one or more LISs.
Using Classical IP
Here are the steps to follow to begin using Classical IP over ATM:
o Determine the location of the ATM ARP server you want to use.
You can define the ATM ARP server on your local LANplex system. You can also define the ATM ARP server externally on another LANplex system or on an ATM switch, such as 3Com's CELLplex (TM) 7000 system.
o Define the ATM ARP server. See "Defining an ATM ARP Server", next
o Define the IP interface for the LIS. See "Defining an IP LIS Interface".
Defining an ATM ARP Server
You can define the ATM ARP server for each LIS if you are defining permanent virtual circuits (PVCs). Each LIS must connect to a single ATM network and must belong to the same IP subnet.
To define an ATM ARP server:
1 From the top level of the Administration Console, enter:
ip atmArpServer define
2 Enter the number for the ATM port where you wish to define the ATM ARP server.
3 Enter the IP address of the ATM port you wish to define.
4 Enter the subnet mask. To use the value in brackets, press [Return] at the prompt.
Defining an IP LIS Interface
When you define an IP LIS interface, you specify several general IP interface characteristics and IP LIS characteristics.
Before you define an IP LIS interface with switched virtual circuits (SVCs), be sure you have defined an ATM ARP serve, as shown in the previous section. If the LIS interface has only PVCs, you do not need to define an ATM ARP server.
To define an IP interface:
1 From the top level of the Administration Console, enter:
ip interface define
The Console prompts you for the interface's parameters. To use the value in brackets, press [Return] at the prompt.
2 Enter the IP address of the interface.
3 Enter the subnet mask of the network to which the interface is to be connected.
4 Enter the cost value of the interface.
5 Enter the type of IP interface: LIS.
6 Enter the advertisement addresses for this interface. You can enter up to 32 advertisement addresses for each interface. (The maximum number on the LANplex system is 64.)
You may enter one or more addresses, and the router will send advertisements to each of these addresses. They may be broadcast addresses, individual addresses, or any combination. In most cases, you will configure VLAN interfaces with a single broadcast address and LIS interfaces with a list of individual addresses of other routers in the ATM network. Addresses must be separated by commas (,). The default address is a broadcast address. A total of 32 advertisement addresses may be added, and a maximum of 64 advertisement addresses may be defined on the system.
7 Enter the LIS information:
-- For a LIS interface with SVCs, enter the ATM ARP server address, the maximum SVC count, the inactivity timer, the minimum holding time, and the ATM port associated with the interface. (You can also accept the defaults for these values.)
The maximum number of SVCs is the maximum number of SVCs you want to be configurable on the LIS. The inactivity time is the maximum time a circuit is open with no activity before being released. The holding time is the minimum time the connection remains open after the connection has been established.
-- For a LIS interface with only PVCs, enter the ATM port and the PVCs associated with the interface. You can enter up to 51 PVCs for each interface. (The maximum number on the LANplex system is 64.)
This LIS interface example has both PVCs and SVCs:
Enter IP address: 158.101.1.1
Enter subnet mask [255.255.0.0]: 255.255.255.0
Enter cost [1]:
Enter interface type (vlan,lis) [lis]:
Enter advertisement address(es) []: 158.101.112.1
Enter ATM arp server address
[00-0000-00-000000-0000-0000-0000-000000000000-00]:47-0000-00-000000-00000000-00cc -000000000001-ff
Accept completed ATM address (yes, no) [yes]:
Enter max. SVC count (0=no max.0) [0]:
Enter inactivity time (0=infinite, 10-10000) seconds [1200]:
Enter min. holding time (0-10000) seconds [60]:
Select ATM port [1]:
Enter PVC(s) (VPI/VCI)[]: 1/32,1/200,1/3330
Defining an IP VLAN Interface
When you define an IP VLAN interface, you specify several interface characteristics, as well as the index of the VLAN associated with the interface.
You must first define a VLAN, as described in Appendix B: Administering VLANs, before you define an associated IP VLAN interface.
To define an IP VLAN interface:
1 From the top level of the Administration Console, enter:
ip interface define
The Console prompts you for the interface's parameters. To use the value in brackets, press [Return] at the prompt.
2 Enter the IP address of the interface.
3 Enter the subnet mask of the network to which the interface is to be connected.
4 Enter the cost value of the interface.
5 Enter the type of IP interface: VLAN.
6 Enter the advertisement address for this interface.
You may enter one or more addresses, and the router will send advertisements to each of these addresses. They may be broadcast addresses, individual addresses, or any combination. In most cases, you will configure VLAN interfaces with a single broadcast address and LIS interfaces with a list of individual addresses of other routers in the ATM network. Addresses must be separated by commas (,). The default address is a broadcast address. A total of 32 advertisement addresses may be added, and a maximum of 64 advertisement addresses may be defined on the system.
7 Enter the index of the VLAN associated with the interface.
Example:
Enter IP address: 158.101.1.1
Enter subnet mask [255.255.0.0]: 255.255.255.0
Enter cost [1]:
Enter interface type (vlan, lis) [vlan]:
Enter advertisement address(es) [158.101.1.255]:
IP VLANs:
Index Ports
3 1-8
4 9-12
Select VLAN index: 3
To modify a PVC, you must first remove it from the LIS, then add it back using the new VPI and VCI.
Displaying Interfaces
You can display both summary and detailed information about all IP interfaces configured for each switching module in the system. The detail display contains all the summary information as well as information about the advertisement address, PVCs, and VLANs.
To display IP interface summary and detail information:
1 From the Administration Console top-level menu, enter:
ip interface summary
OR
ip interface detail
2 Enter the slot(s) of the switching module(s) for which you want to display the interface information. Separate non consecutive ports with commas (,). Enter a consecutive series of slots using a dash (-).
Removing an IP Interface for a LIS
To remove the IP interface for a LIS:
1 From the top level of the Administration Console, enter:
ip interface remove
2 Enter the IP address of the interface.
The interface is removed.
Defining an Advertisement Address for a LIS
To define an advertisement address:
1 From the top level of the Administration Console, enter:
ip interface defineAdvertisement
2 Enter the IP address of the interface.
3 Enter the advertisement address.
The address is added.
Removing an Advertisement Address for a LIS
To remove an advertisement address in a LIS:
1 From the top level of the Administration Console, enter:
ip interface removeAdvertisement
2 Enter the IP interface index.
3 Enter the advertisement address.
The address is removed.
Defining a PVC for a LIS
To define a PVC for a LIS:
1 From the top level of the Administration Console, enter:
ip interface definePVC
2 Enter the IP interface index.
3 Enter the PVC (vpi/vci).
The PVC is added.
Removing a PVC for a LIS
To remove a PVC for a LIS:
1 From the top level of the Administration Console, enter:
ip interface removePVC
2 Enter the IP interface index.
3 Enter the PVC (vpi/vci).
The PVC is removed.
Displaying ATM ARP Server Information
You can display a summary of ATM ARP server information for each LIS. The summary includes the index, the IP address, the subnet mask, and the ATM address. An index number is assigned to each ATM ARP server when the server is defined.
To display information about the ATM ARP server:
1 From the top level of the Administration Console, enter:
ip atmArpServer display
The information is displayed.
Removing an ATM ARP Server
You can remove the ATM ARP server for each LIS based on the index number associated with the ATM ARP server. An index number is assigned to each ATM ARP server when the server is defined.
To remove the ATM ARP server:
1 From the top level of the Administration Console, enter:
ip atmArpServer remove
You are prompted for the ATM ARP server index(es).
2 Enter the ATM ARP server index(es).
The index(es) are removed.
Displaying the ATM ARP Cache
You can display the ATM ARP cache to determine which IP addresses are known to the ATM ARP server.
To display the ATM ARP cache:
1 From the top level of the Administration Console, enter:
ip atmArpServer arp display
The ATM ARP cache is displayed.
An entry in the ATM ARP cache may be displayed as pending if:
o The client did not respond to an inverse ATM ARP request, or
o A duplicate IP address has been entered for existing clients.
Removing ATM ARP Cache Entries
To remove an ATM ARP cache entry:
1 From the top level of the Administration Console, enter:
ip atmArpServer arp remove
2 Enter the IP address of the entry you want to remove at the prompt.
The entry is removed.
Flushing All ATM ARP Cache Entries
To flush all ATM ARP cache entries:
1 From the top level of the Administration Console, enter:
ip atmArpServer arp flush
Administering UNI Management Entities
A User-to-Network Interface (UNI) Management Entity (UME) implements the management interface to the ATM network. Each ATM port has one UME, which manages the network prefix and address tables and provides access to the Interim Local Management Interface (ILMI) MIB.
Each LANplex UME registers one address for LAN Emulation and one address for Classical IP over ATM with the switch port to which it is attached.
You can display information about each UME and configure its attributes.
Displaying UME Information
When you display UME information for an ATM port, you display values for the connection state, the VPI (virtual path identifier), the VCI (virtual channel identifier), and other attributes.
To display UME information:
1 From the top level of the Administration Console, enter:
atm ume display
You are prompted to select an ATM port.
2 Enter the ATM port for which you want to display the UME information.
The UME information is displayed.
Table A-4 describes the types of information provided about the UNI Management Entity.
Table A-4 UNI Management Entity Attributes
|
Attribute |
Description |
|
connCount |
Number of times port has successfully connected since last reboot |
|
discCount |
Number of times port has disconnected since last reboot |
|
dropRxPdus |
Number of protocol data units (frames) received but not processed |
|
reqState |
Requested connection state for management access and address registration (connected or disconnected) |
|
reqVci |
Requested virtual channel identifier. This value takes effect after you disable and then enable the port. |
|
reqVpi |
Requested Virtual Path Identifier. This value takes effect after you disable and then enable the port. |
|
rxPdus |
Number of protocol data units (frames) received |
|
txPdus |
Number of Protocol Data Units (frames) transmitted. |
|
state |
Current connection state for management access and address registration. Possible values:
o Connected: address registration has been successfully completed
o Connecting: the circuit is up, but the port has not successfully completed address registration
o Disconnected: either the reqState has been set to disconnected or the circuit is down
o Disconnecting: address registration has been terminated but the circuit is still up |
|
vci |
Current virtual channel identifier |
|
vpi |
Current virtual path identifier |
Listing Network Prefixes and Addresses
You can list the registered network prefixes and addresses of any ATM port.
To list prefixes and addresses:
1 From the top level of the Administration Console, enter:
atm ume list
You are prompted for an ATM port.
2 Select an ATM port.
The registered network prefixes and addresses are listed for the port you requested.
Setting the UME Connect State
For each ATM port, you can set the connect state for management access and address registration.
To set the connect state:
1 From the top level of the Administration Console, enter:
atm ume state
You are prompted for an ATM port.
2 Enter the ATM port for which to set the state.
3 Enter the new value (connected or disconnected). The default is connected.
Setting the Virtual Path Identifier
For each ATM port, you can set the virtual path identifier (VPI) used by UME for the Interim Local Management Interface (ILMI). To set the VPI:
1 From the top level of the Administration Console, enter:
atm ume vpi
You are prompted for an ATM port.
2 Enter the ATM port for which you want to set the virtual path identifier.
3 Enter the new value for the VPI.
The new VPI takes effect after the port has been disabled and then enabled.
Setting the Virtual Channel Identifier
You can set the virtual channel identifier (VCI) used by UME for the Interim Local Management Interface (ILMI). To set the VCI:
1 From the top level of the Administration Console, enter:
atm ume vci
You are prompted for an ATM port.
2 Enter the ATM port for which you want to set the virtual channel identifier.
3 Enter the new value for the VCI.
The new VCI takes effect after the port has been disabled and then enabled.
Administering ATM Ports
You can display summary or detailed reports, create labels, and list virtual channel connection (VCC) information for ATM ports.
Displaying Port Information
You can display a summary of ATM port information or a detailed report. When you display a summary, you receive information about the port, including its label, status, and the most important statistics about general port activity and port errors. The detailed report includes the information in the summary plus additional port statistics, such as cells discarded.
To display information about ATM ports:
1 From the top level of the Administration Console, enter:
atm ports summary
or
atm ports detail
The port information is displayed in the format you specified.
Table A-5 describes these statistics.
Table A-5 Description of Fields for ATM Ports
|
Field |
Description |
|
bandwidth |
Total bandwidth available for port (in bits per second) |
|
cfgVPCx |
Current number of virtual path connections |
|
cfgVCCs |
Current number of virtual channel connections |
|
hecErrors |
Header Error Checksum count |
|
lastChange |
Last time the link state of the port changed since the last reboot |
|
linkStatus |
State of link |
|
maxVCCs |
Maximum number of possible virtual channel connections |
|
maxVPCs |
Maximum number of possible virtual path connections |
|
maxVCIbits |
Maximum number of bits available to represent a Virtual Channel Identifier |
|
maxVPIbits |
Maximum number of bits available to represent a Virtual Path Identifier |
|
mediaType |
Type of physical connection media |
|
ocdEvents |
Number of times an out-of-cell delineation was detected |
|
operStatus |
Current state of port |
|
portLabel |
Label for the physical port |
|
reqStatus |
Requested state of port |
|
rxCells |
Number of cells received |
|
rxCellsDropped |
Number of cells received but thrown away |
|
tcAlarm |
Transmission convergence alarm |
|
transType |
Type of transmission sublayer |
|
txCellDiscards |
Number of cells thrown out after attempting to transmit |
|
txCells |
Number of cells transmitted |
|
uniType |
Type of User-Network Interface (public or private) |
|
uniVersion |
UNI specification implemented |
Labeling a Port
Port labels serve as a useful reference point and as an accurate way to identify your ports for management. You might want to label your ATM ports so that you can easily identify the device specifically attached to each port (for example, LAN, workstation, or server).
To label an ATM port:
1 From the top level of the Administration Console, enter:
atm ports label
2 Enter the port(s) you want to label
3 Enter the label of each ATM port.
Ports labels can be a maximum of 32 characters in length. The new port label appears next time you display information for that port.
Listing Virtual Channel Connection Information
You can list general virtual channel connection information as well as specific transmit and receive information.
Listing General Virtual Channel Connection Information
To list general virtual channel connection information, enter the following command from the top level of the Administration Console:
atm ports vcc list
Table A-6 describes VCC general information.
Table A-6 Description of Fields for Virtual Channel Connection Information
|
Field |
Description |
|
aalType |
Type of ATM Adaptation Layer (aal5) |
|
lastChange |
Last time the circuit changed state |
|
status |
Current status for the circuit |
|
VPI/VCI |
The VPI and VCI for the circuit listed in the present entry |
Listing Virtual Channel Connection Transmit Information
To list virtual channel connection transmit information, enter the following command from the top level of the Administration Console:
atm ports vcc listxmt
Table A-7 describes VCC transmit information.
Table A-7 Description of Fields for Virtual Channel Connection Transmit Information
|
Field |
Description |
|
parameter 1
parameter 2
parameter 3 |
Values associated with the transmit trafficDescriptor |
|
transmit trafficDescriptor |
Transmit characteristics of the circuit |
|
VPI/VCI |
The VPI and VCI for the circuit listed in the present entry |
Listing Virtual Channel Connection Receive Information
To list virtual channel connection receive information, enter the following command from the top level of the Administration Console:
atm ports vcc listrcv
Table A-8 describes VCC receive information.
Table A-8 Description of Fields for Virtual Channel Connection Receive Information
|
Field |
Description |
|
vpi/vci |
The VPI and VCI for the circuit listed in the present entry |
|
receive trafficDescriptor |
Receive characteristics of the circuit |
|
parameter 1
parameter 2
parameter 3 |
Values associated with the receive trafficDescriptor |
References
RFC 1577, January 1994.
ATM LAN Emulation: An Inside Look at Version 1.0 of the LANE Specification, 3Com Corporation, February 1996.
Appendix B
Administering VLANs
This appendix contains:
o A description of Virtual LAN (VLAN) concepts and operational aspects for the LANplex 2500 system
o Examples of VLAN configurations
o Information on how to configure VLANS and display VLAN information using the Administration Console
About VLANs
The VLAN concept in LAN technology helps minimize broadcast and multicast traffic and makes end-station moves, adds, and changes easier for the network administrator.
In the LANplex system, VLANs allow you to:
o Create independent broadcast domains to optimize network performance and create firewalls
o Form flexible user groups independent of the users physical network location
Types of VLANs
Several different types of VLANs, described next, can be used for grouping users:
o Port group VLANs
o MAC address group VLANs
o Application-oriented VLANs
o Protocol-sensitive VLANs
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 are 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. They can benefit the user by restricting traffic based on a set of simple rules.
MAC Address Group VLANs
MAC-address-grouped VLANs allow a switch to make filtering decisions based on grouping MAC addresses together. These MAC address groups can be configured so that stations in the group can only communicate with each other or with specific network resources. This solution is good for security. It allows the VLAN association to move with the station. However, MAC-address-grouped VLANs may require complex configuration in comparison to other types of VLANs. Also, every time an end-station is added, the network administrator must modify the VLAN definition.
Port group and MAC address group VLANs are supported using the packet filtering capabilities in the LANplex system. For information on port group and MAC address group filtering, refer to your LANplex 2500 Operation Guide and LANplex Administration Console User Guide.
Application-Oriented VLANs
Using the LANplex filtering capability, application-specific traffic such as telnet traffic or ftp traffic can be filtered based on higher-layer information. You create this application-oriented VLAN by configuring packet filters that specify data and offsets of the data within received packets. For example, if you want a filter on a particular port for all telnet traffic, you could create a a filter that discards all TCP traffic received on the telnet port.
IP Multicast routing and AutoCast VLANs are additional VLAN features in the LANplex system that can be used to group IP Multicast traffic for specific applications. For more information on how the LANplex system manages IP Multicast traffic, refer to the LANplex 2500 Extended Switching User Guide.
Protocol-Sensitive VLANs
Data that is received by the LANplex that has a broadcast, multicast, or unknown destination address is forwarded to all switch ports. This process is referred to as bridge flooding. Protocol-sensitive VLANs group one or more switch ports together as the flooding domain for a specified layer 3 protocol, such as IP or AppleTalk. protocol
These VLANs make flooding decisions based on the network layer protocol of the frame. In addition, for IP VLANs, you can also make flooding decisions based on layer 3 subnet address information. Protocol-sensitive VLANs allow the restriction of flood traffic for both routable and nonroutable protocols. They have a relatively simple configuration comprising one or more protocols and groups of switch ports. These protocol-sensitive VLANs operate independent of each other and are simple to configure.
Additionally, the same switch port can belong to multiple VLANs. For example, you can have port 1 on a LANplex assigned to several IP subnet VLANs, plus one IPX VLAN, one AppleTalk VLAN, and one NetBIOS VLAN. In a multiprotocol environment, protocol-sensitive VLANs can be very effective for controlling broadcast and multicast flooding.
Multiple types of VLANs can coexist in the LANplex system. When associating received data with a particular VLAN configuration in a multiple VLAN configuration, port group, MAC address group, and application-oriented VLANs always take precedence over protocol-sensitive VLANs.
LANplex Protocol-Sensitive VLAN Configuration
LANplex 2500 revision 8.1.1 software introduces protocol-sensitive VLAN configuration through the Administrator Console. The LANplex protocol-sensitive VLAN configuration elements, discussed next, include:
o Protocol suite
o Switch ports
o Layer 3 addressing information for IP VLANs
Protocol Suite
The protocol suite describes which protocol entities can comprise a protocol-sensitive VLAN. For example, LANplex VLANs support the IP protocol suite, which is made up of the IP, ARP, and RARP protocols. Table B-1 lists the protocol suites that the LANplex supports, and the protocol types included in each protocol suite.
Table B-1 LANplex 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) |
|
DECnetTM |
DEC MOP, DEC Phase IV, DEC LAT, DEC LAVC (Ethertype, SNAP PID) |
|
SNA |
SNA Services over Ethernet (Ethertype) |
|
Banyan VINES® |
Banyan (Ethertype, DSAP, SNAP PID) |
|
X25 |
X.25 Layer 3 (Ethertype) |
|
NetBIOSTM |
NetBIOS (DSAP) |
|
Default |
Default (all protocol types) |
Switch Ports
A group of switch ports is any combination of switch ports on the LANplex system. Included are switch ports created as ATM LAN Emulation Clients (ATM LECs). VLANs do not support media implementations that do not run over switch (bridge) ports, for example, ATM Logical IP Subnets (ATM LISs).
Layer 3 Addressing Information
For IP VLANs only, the LANplex system optionally supports configuring of individual IP VLANs with network layer subnet addresses. With this additional layer 3 information, you can create independent IP VLANs that share the same switch ports for multiple IP VLANs. Data is flooded according to both the protocol (IP) and the layer 3 information in the IP header to distinguish among multiple IP VLANs on the same switch port. This configuration is discussed later in the section Overlapped IP VLANs.
The Default VLAN
At system startup, the LANplex automatically creates a VLAN Interface called the Default VLAN. Initially, the Default VLAN includes all of the switch ports in the system. In the LANplex system, the Default VLAN serves two purposes:
o Defining the flood domain for protocols not supported by any VLAN in the system.
o Defining the flood domain for protocols supported by a VLAN in the system but received on nonmember ports.
Both cases represent exception flooding conditions that are described in the following sections.
Modifying the Default VLAN
New switch ports can dynamically appear in the LANplex system if you insert a daughter LAN card or create an ATM LEC. 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.
LANplex VLANs also allow you to modify the initial Default VLAN to form two or more subsets of switch ports. If you remove the Default VLAN and no other VLANs are defined for the system, no flooding of traffic can occur.
How the LANplex System Makes Flooding Decisions
Protocol-sensitive VLANs directly affect how the LANplex system performs flooding. Without protocol-sensitive VLANs, the flooding process is to forward data to all switch ports in the system. With protocol-sensitive VLANs, the flooding process follows this model:
o As a frame is received that needs to be flooded, it is decoded to determine its protocol type.
o If a VLAN exists for that protocol in the LANplex system and the frames source port is a member of the VLAN, the frame is flooded according to the group of ports assigned to that VLAN.
o If a VLAN exists for that protocol in the LANplex system, but the frames source port is not a member of the VLAN definition, then the frame is flooded according to the Default VLAN assigned to that port.
o If the protocol type of the received frame has no VLAN defined for it in the system, the frame is flooded to the Default VLAN for the receive port.
This example shows how flooding decisions are made according to VLANs set up by protocol (assuming an 18-port switch):
|
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. |
|
XNS - port 1 |
VLAN 1 |
XNS data received matches no protocol VLAN, so the Default VLAN is used. |
VLAN Exception Flooding
If data arrives on a switch port for a certain protocol, and VLANs for that protocol are defined in the system but not on that switch port, the Default VLAN defines the flooding domain for that data. This case is called VLAN Exception Flooding.
This example shows how the VLAN Exception Flooding decision is made (assuming an 18-port switch):
|
Index |
VLAN |
Ports |
|
1 |
Default |
1 - 18 |
|
2 |
IP |
1- 10 |
|
Data received on... |
Is flooded on... |
Because... |
|
XNS - port 1 |
VLAN 1 |
XNS data does not match any defined VLAN in the system. |
|
IP - port 2 |
VLAN 2 |
IP data received matches IP VLAN 2 for source ports 1 - 10. |
|
IP - port 12 |
VLAN 1 |
IP data received on source port 12 does not match any defined source port for IP VLAN, so the Default VLAN is used. |
Overlapped IP VLANs
The LANplex also gives you the ability to assign network layer information to IP VLANs. This capability allows network administrators to manage their VLANs by subnet. Flooding decisions are made by first matching the incoming frame using the protocol (IP) and then matching it with layer 3 subnet information. If received data is IP but does not match any defined IP subnet VLAN, it is flooded within all IP VLANs using the relevant switch port.
For example, two IP VLANs can be configured for ports 1-10 as follows:
IP VLAN 1 - Subnet 158.101.112.0, ports 1-10
IP VLAN 2 - Subnet 158.101.113.0, ports 1-10
This example shows how flooding decisions are made using overlapping IP VLANs (assuming a 12-port switch):
|
Index |
VLAN |
Network Address/Mask |
Ports |
|
1 |
Default |
none |
1 - 12 |
|
2 |
IP |
158.103.122.0/
255.255.255.0 |
1 - 6 |
|
3 |
IP |
158.103.123.0/
255.255.255.0 |
6 - 12 |
|
Data received on... |
Is flooded on... |
Because... |
|
IP subnet 158.103.122.2
on port 6 |
VLAN 2 |
IP network layer matches layer 3 address for VLAN 2. |
|
IP subnet 158.103.123.2
on port 6 |
VLAN 3 |
IP network layer matches layer 3 address for VLAN 3. |
|
IP subnet 158.103.124.2
on port 6 |
VLAN 2 and
VLAN 3 |
IP network layer does not match any layer 3 address for IP VLANs. |
|
IPX on port 6 |
VLAN 1 |
IPX frame does not match any defined VLAN. |
In this example, when the subnet address of an IP packet does not match any subnet address of any defined IP VLAN in the system, it is flooded to all of the IP VLANs that share the source switch port., in this case, port 6.
Routing Between VLANs
The only way for stations that are in two different VLANs to communicate is to route between them. The LANplex 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 through an external router.
The LANplex routing model lets you configure routing protocol interfaces based on a VLAN defined for that protocol. To assign a routing interface, you must first create a VLAN for that protocol and then associate it with that interface.
For example, to create an IP interface that can route through a VLAN:
1 Create an IP VLAN for a group of switch ports.
This IP VLAN does not need to contain layer 3 information unless you want to further restrict flooding according to the layer 3 subnet address.
2 Configure an IP interface with a network address, subnet mask, broadcast address, cost, and type (VLAN). Select an IP VLAN to bind to that IP interface.
If layer 3 information is provided in the IP VLAN for which you are configuring an IP Interface, the subnet portion of both addresses must be compatible.
For example:
IP VLAN Subnet 157.103.54.0 with subnet mask of 255.255.255.0
IP host interface address 157.103.54.254 with subnet mask of 255.255.255.0
Layer 2 (bridging) communication is still possible within an IP VLAN (or router interface) for the group of ports within that IP interfaces IP VLAN. IP data destined for a different IP subnet will use the IP routing interface to get to that different subnet, even if the destination subnet is on a shared port.
VLAN Examples
Figure B-1 is a simple configuration containing three protocol-sensitive VLANs (two IP and one IPX) that share a high-speed FDDI link. The end-stations and servers are on 10Mbps ports with traffic segregated by protocol. They are only aggregated over the high-speed FDDI link.
Figure B-1 Protocol Sensitive VLANs over FDDI
Figure B-2 is a configuration that contains two different protocol-sensitive VLANs (IP and IPX) with servers on separate high-speed 100BaseT ports. The end-station clients share the same switch ports, yet the IP and IPX traffic stays separate.
Figure B-2 Protocol Sensitive VLANs over 100BASE-T
Administering VLANs
This section describes how to display information about VLANs and how to configure VLANs.
Through the Administrator Console, you can:
o Display summary or detailed information on VLANs
o Define or modify a VLAN definition
o Delete a VLAN definition
Displaying VLAN Information
You can display a summary of VLAN information or a detailed report. When you display a summary, you receive information about the protocols and ports assigned to each VLAN plus the layer 3 addresses used to manage flood domains for overlapping IP subnets. The detailed VLAN report includes the summary information plus additional utilization statistics.
1 From the top level of the Administration Console, enter:
bridge vlan summary
or
bridge vlan detail
The VLAN information is displayed in the format you specified.
Example of a summary display for several VLANs:
Select menu option (bridge/vlan): summary
Index Protocol Identifier Ports
1 default 0 1-17
2 IP 2 1, 5-7
3 IPX 3 8-10
4 IP 4 7, 12-15
Index Name Layer 3
1 none
2 eastgroup 158.101.111.16 255.255.255.0
3 westgroup none
4 northgroup 158.101.112.14 255.255.255.0
Example of a detailed display for the VLANs:
Select menu option (bridge/vlan): detail
Index Protocol Identifier Ports
1 default 0 1-17
2 IP 2 1, 5-7
3 IPX 3 8-10
4 IP 4 7, 12-15
Index Name Layer 3
1 none
2 eastgroup 158.101.111.16 255.255.255.0
3 westgroup none
4 northgroup 158.101.112.14 255.255.255.0
index inPackets inBytes outPackets outBytes
1 342 3676 322 2987
2 125 7654 118 6897
3 345 554 289 7431
4 876 8651 765 7969
Table B-2 describes these statistics.
Table B-2 VLAN Parameters
|
Field |
Description |
|
Index |
A system-assigned index used for identifying a particular VLAN |
|
Protocol |
The protocol suite of the VLAN |
|
Identifier |
A unique, user-defined (4-byte) integer for use by global management operations |
|
Ports |
The numbers of the ports assigned to the VLAN |
|
Name |
A 16-byte character string intended for use in identifying the members of the VLAN |
|
Layer 3 |
Optional parameters consisting of IP subnet and mask used to set up flood domains for overlapping IP VLAN subnets |
|
inPackets |
Number of flooded broadcast and multicast packets that were received on the VLAN |
|
inBytes |
Number of flooded broadcast and multicast bytes that were received on the VLAN |
|
outPackets |
Number of flooded broadcast and multicast packets transmitted over the VLAN |
|
outBytes |
Number of flooded broadcast and multicast bytes transmitted over the VLAN |
Defining VLAN Information
To create a VLAN definition:
1 From the top level of the Administration Console, enter:
bridge vlan define
2 Enter the appropriate protocol suite (IP, IPX, AppleTalk, XNS, DECnet, SNA, Banyan, X.25, NetBIOS, NetBEUI, default).
3 Enter the VLAN Identifier.
This is a unique number in your VLAN network used to represent a particular VLAN interface.
4 Enter the VLAN Name.
This is a short descriptive name for the VLAN.
5 Enter the number(s) of the port(s) or all to assign all ports to the VLAN.
You are prompted to enter the number(s) of the port(s) that can be assigned to the VLAN.
6 If you did not choose the IP protocol suite for this VLAN, you have completed the steps for defining the VLAN.
If you selected the IP protocol suite:
-- Enter defined to use layer 3 subnet addressing and continue with steps 7 and 8.
-- Enter undefined to not use layer 3 addressing.
7 Enter the IP subnet address.
8 Enter the subnet mask.
Example of VLAN configuration:
Select menu option (bridge/vlan): define
Enter Protocol Suite (IP,IPX,AppleTalk,XNS,DECnet,SNA,Banyan,X.25,NetBIOS,NeBEUI,
default): IP
Enter VLAN Identifier: 1
Enter VLAN Name: SD Marketing
Ports 1=FDDI, 2-17=Ethernet
Enter port(s) (1-17|all): 1-5
Layer 3 Address (undefined, defined): defined
Enter IP Subnet Address: 158.111.122.0
Enter subnet mask [255.255.0.0] 255.255.255.0
The maximum number of VLANs you can define on a single bridge is 32.
Modifying VLAN Information
To modify VLAN information:
1 From the top level of the Administration Console, enter:
bridge vlan modify
You are prompted to reenter the information that defines the VLAN. Press the Return or Enter key to accept any value that appears in brackets [ ].
2 Enter the number of the VLAN interface index.
3 Enter the protocol suite for that VLAN (IP, IPX, AppleTalk, XNS, DECnet, SNA, Banyan, X.25, NetBIOS, NetBEUI, default).
4 Enter the VLAN Identifier.
5 Enter the VLAN Name.
6 Enter the number(s) of the port(s) or all.
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.
Example of modified VLAN information:
Select menu option (bridge/vlan): modify
Select VLAN interface [1-2]: 2
Protocol Suite (IP,IPX,AppleTalk,XNS,DECnet,SNA,
Banyan,X.25,NetBIOS,NetBEUI,default) [AppleTalk]: IP
VLAN Identifier [1]: 2
VLAN Name [Sales]:
Ports 1=FDDI, 2-17=Ethernet
Enter port(s) (1-17|all) [1-5]:
Layer 3 Address (undefined,defined) [undefined]:
Removing VLAN Information
To remove a VLAN definition:
1 From the top level of the Administration Console, enter:
bridge vlan remove
2 Enter the indexes for the VLANs you want to remove.
Example:
Select menu option (bridge/vlan): remove
Select VLAN index(es) (1-2|all): 1