:
Programming flash memory block 1 of 1.
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 to the system.
From the top level of the Administration Console, enter:
system consoleLock
You are prompted with:
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 for (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 were added at this release of revision 8.1.1:
Support for the 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. The LANplex 2500 ATM module allows you to 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 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).
The LANplex 2500 ATM module supports these features:
o UNI 3.0 signaling
o LAN Emulation 1.0 (LEC support) 2 Emulated LANs
o Dynamic configuration of Emulated LANs (ELANs)
o A maximum of 128 Virtual Connections (VCs) per system
o Management:
-- UME Address registration
-- MIBs: ILMI, AToM, LEC, SONET
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. Addresses must be separated by commas (,).
Defining an IP Interface
When you define an IP interface, you specify several IP interface characteristics.
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: management.
IP interface example:
Enter IP address: 158.101.1.1
Enter subnet mask [255.255.0.0]: 255.255.255.0
Enter cost [1]: 1
Enter interface type (management) [management]: management
Enter advertisement address(es) [158.101.1.255]: 158.101.1.255
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 want to reconfigure your interfaces.
Displaying Interfaces
You can display both summary and detailed information about all IP interfaces configured for the system. The detail display contains all the summary information as well as information about the advertisement address, PVCs, and VLANs.
ip interface summary
OR
ip interface detail
6 Enter the interface index(es) or all.
State Field Added to the Interface Display
The 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 associated with the interface. For IP, the state displayed will be either up or down.
The interface state is displayed as down if:
-- No port in the defined 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 interface, including those in overlapping subnets, have established link status
As the interface state changes, transitions are reflected in the corresponding tables for all directly connected and associated routes as shown in Table 1.
Table 1 Interface Display Table Updates
|
IP |
|
Routing Table
Static Route Table |
For IP 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.
System upTime Menu Added
You can display the time in minutes, hours, and days since the last system reboot.
To display system upTime, from the top level of the Administration Console, enter:
system upTime
System upTime is be 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/time configuration
o FDDI backplane station mode configuration
New IF MIB Added
The new 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.
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 an MS-DOS® Platform" for the new installation procedure.
Software Changes and Corrections
This section describes software changes and corrections implemented at this release:
o The telnet timeout interval can now be configured to a number between 1 and 60 minutes. Previously, this interval could be configured to a number between 30 and 60 minutes.
System Issues
The following system issues are identified at this release:
o 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 An ATM LEC cannot be configured as the backbone port in Express Switching mode.
o The ipDefaultTTL MIB variable cannot be set at this release.
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 Packet filters can access packet data through byte 64 in the packet.
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.
o Roving Analysis frames over a remote Fast Ethernet connection are truncated if greater than 1495 bytes.
o Before enabling Express Switching mode, you must disable the backbone port. Then, after enabling Express Switching mode, re-enable the backbone port.
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 Roving Analysis is not supported on a LANplex 2500 system that has an ATM card in the chassis.
o Remote Roving Analysis is not supported over a Fast Ethernet connection with Spanning Tree Protocol enabled.
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
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 SunNet Manager to use the schema file generated with SunNet Manager software version 2.0 or later.
Revision History
Table 2 provides a brief description of the previous releases of the LANplex 2500 software.
Table 2 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 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 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 chapter describes how to administer asynchronous transfer mode (ATM) on the LANplex® 2500 system. It includes information about:
o LAN Emulation (LANE)
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 The LANE method of adapting networks to ATM supports transparent translation of higher level protocols, such as IP, IPX, and AppleTalk protocols. LANE also supports broadcast and multicast addressing. For more information on LANE on the LANplex 2500 system, see "LAN Emulation".
o The Classical IP method supports transparent translation of IP only over ATM, and does not support broadcast or multicast addressing. Classical IP is supported only in LANplex 2500 8.1.0 Extended Switching software.
Before You Configure ATM
Before configuring ATM, you should:
o Check the ATM link status.
o Verify that LANplex address registration is operational.
o Verify that signaling is operational.
Checking ATM 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 User-to-Network Interface (UNI) Management Entity (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. 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 address --- 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 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 end-points through 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 system 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 LECs. An ELAN consists of the following components:
o One 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 One 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 BUS must be defined as part of an ELAN before a LEC can be defined.
o One 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.
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 Emulated Client (LEC). See the section "Eliminating Bridge Loops in ELAN Configurations", next, for important information regarding LEC configuration.
To create an emulated LAN, follow these steps:
1 Determine the location of the LES and BUS.
You can define the LES and BUS in any LEC on the network, or on an ATM switch, such as 3Com's CELLplex TM 7000 system.
2 Define the Broadcast and Unknown Server.
3 Define the LAN Emulation Server.
4 Define the LAN Emulation Clients.
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 system can bridge between all ports, including logical bridge ports (LECs). Since Spanning Tree Protocol (STP) is off by default, we recommend following this procedure when creating multiple LECs with LANplex Intelligent Switching software:
1 After defining LECs, enter the value enabled at the prompt:
Enter Enable State for next reboot (disable, enable)
2 Enable STP.
From the top level of the Administration Console, enter:
bridge stpState enabled
3 Reboot the system.
Once all the LECs are created, reboot the system to add the LECs to the bridge table.
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 the 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 define
2 Enter the number of the ATM port to which the client is attached.
You can attach only one client 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 is provided LES and BUS services, the ATM switch must have its LECS updated 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.
5 Enter the maximum frame size (MTU) (Unspecified, 1516, or 4544).
The LANplex system supports Unspecified Bit Rate (UBR) only.
All LECs within the same emulated LAN must have the same MTU size. 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 Enable STP to eliminate potential bridge loops. See "Eliminating Bridge Loops in ELAN Configurations" for more information.
From the top level of the Administration Console, enter:
bridge stpState enabled
9 Reboot to enable all newly defined LECs.
Example:
Select menu option (atm/lane): 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]: enable
You must REBOOT to be able to enable a newly created LEC.
Reboot after all newly created LECs have been added.
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 summary
or
atm lane detail
You are prompted for the number of an 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 nonlocal 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 nonlocal entries in its LE_ARP cache (C19) |
Modifying Information About LAN Emulation Clients
You may configure LAN Emulation Client parameters. To modify these parameters, take these steps:
1 From the top level of the Administration Console, enter:
atm lane 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 Enter the number(s) of the LEC(s) or all.
You are prompted for the new value of the option you entered.
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 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): remove
Select LEC (1-3|all) [1]: 1
Delete lec/s resulting in system reboot? (n,y) [y]: y
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-2 describes the types of information provided about the UNI Management Entity.
Table A-2 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-3 describes these statistics.
Table A-3 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 VCC 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-4 describes VCC general information.
Table A-4 Description of Fields for Virtual Channel Connection Information
|
Field |
Description |
|
aalType |
Type of ATM Adaptation Layer (aal5) |
|
lastChange |
Last time the circuit changed state |
|
operStatus |
Current status for the circuit |
|
reqStatus |
Requested status for the circuit |
|
vpi/vci |
The VPI and VCI for the circuit listed in the present entry |
Listing VCC 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-5 describes VCC transmit information.
Table A-5 Description of Fields for Virtual Channel Connection Transmit Information
|
Field |
Description |
|
transmit trafficDescriptor |
Transmit characteristics of the circuit |
|
parameter 1
parameter 2
parameter 3 |
Values associated with the transmit trafficDescriptor |
|
vpi/vci |
The VPI and VCI for the circuit listed in the present entry |
Listing VCC 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-6 describes VCC receive information.
Table A-6 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.