3com 4007 Release note

http://www.3com.com/

Switch 4007

Release Notes

Management Module, Release 3.0.5

Layer 2 Switch Fabric Modules, Release 3.0.5

Layer 2 Switching Modules, Release 3.0.5

Multilayer Switching Modules, Releases 3.0.5

Part No. 10013820

Published August 2000

3Com Corporation

5400 Bayfront Plaza

Santa Clara, California

95052-8145

in any form or by any means or used to make any derivative work (such as translation, transformation, or

adaptation) without written permission from 3Com Corporation.

3Com Corporation reserves the right to revise this documentation and to make changes in content from time

to time without obligation on the part of 3Com Corporation to provide notification of such revision or change.

3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied

or expressed, including, but not limited to, the implied warranties, terms, or conditions of merchantability,

satisfactory quality, and fitness for a particular purpose. 3Com may make improvements or changes in the

product(s) and/or the program(s) described in this documentation at any time.

If there is any software on removable media described in this documentation, it is furnished under a license

agreement included with the product as a separate document, in the hard copy documentation, or on the

removable media in a directory file named LICENSE.TXT or !LICENSE.TXT. If you are unable to locate a copy,

please contact 3Com and a copy will be provided to you.

UNITED STATES GOVERNMENT LEGEND

If you are a United States government agency, then this documentation and the software described herein are

provided to you subject to the following:

All technical data and computer software are commercial in nature and developed solely at private expense.

Software is delivered as “Commercial Computer Software” as defined in DFARS 252.227-7014 (June 1995) or

as a “commercial item” as defined in FAR 2.101(a) and as such is provided with only such rights as are

provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights

only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable.

You agree not to remove or deface any portion of any legend provided on any licensed program or

documentation contained in, or delivered to you in conjunction with, these Release Notes.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not

be registered in other countries.

3Com, CoreBuilder, SuperStack, and Transcend are registered trademarks of 3Com Corporation. The 3Com

logo is a trademark of 3Com Corporation. 3Com Facts is a service mark of 3Com Corporation.

Netscape is a registered trademark of Netscape Communications Corporation in the United States and other

countries. Java is a registered trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United

States and other countries, licensed exclusively through X/Open Company, Ltd.

All other company and product names may be trademarks of the respective companies with which they are

associated.

C

ONTENTS

1

O

VERVIEW

Scope 11

Important Notices 12

System Requirements 14

2

R

ELEASE

H

IGHLIGHTS

Accelerated Address Aging 16

Purpose 16

How It Works 16

Recommendations 17

Interaction with Transcend Enterprise VLAN Manager 17

Advanced Autonegotiation 18

Sample Problem Description 18

How Advanced Autonegotiation Works 18

Configuration Options 19

Configuring Standard Autonegotiation 19

Configuring a Fixed Port State 19

Configuring Advanced Autonegotiation or Port Monitoring 19

Sample Configurations and System Behavior 20

Configuration A 20

Configuration B 20

Configuration C 21

Configuration D 21

Configuration E 21

Information Display 22

Important Considerations 22

LX 70 GBIC Transceiver 23

Trap Filtering 24

Available Trap Filters 24

Managing Traps 24

3

R

ELEASE

I

SSUES

F

OR

M

ANAGEMENT

M

ODULES

Corrected Problems in Release 3.0.0 28

Operating Considerations for Release 3.0.5 29

Diagnostic events 29

Chassis Reset 29

Software Transfers 29

Password Access 30

System and Module Naming 30

Web Management 30

Known Problems in Release 3.0.5 30

Diagnostics 30

SLIP Interfaces 31

System Time 31

Software Downloads 31

4

R

ELEASE

I

SSUES

F

OR

S

WITCH

F

ABRIC

M

ODULES

Corrected Problems in Release 3.0.0 34

System 34

Ethernet 34

Bridging 34

VLAN 34

Corrected Problems in Release 3.0.5 35

Bridging 35

Management 35

Problems Fixed in v3.0.5 Address Table 36

Problem Overview 36

Problem Detail 36

Work Around 37

Recommendations 37

Guidelines from FR003 TRANSCEND UNIX 5.0 UPDATE 37

Important Notes 39

Operating Considerations for Release 3.0.5 41

Staging 41

System 41

Management 41

Web-based Management 41

Ethernet 42

Transmit and Receive Ports on GBIC Modules 42

Bridging 42

Trunking 42

Resilient Links 43

VLANs 43

Known Problems for Release 3.0.5 44

System 44

Management 44

Ethernet 45

Trunking 45

VLANs 46

5

R

ELEASE

I

SSUES

FOR

L

AYER

2 S

WITCHING

M

ODULES

Corrected Problems in Release 3.0.0 48

System 48

Management 48

Ethernet 48

Bridging 48

VLANs 49

Corrected Problems in Release 3.0.5 49

Bridging 49

Management 50

NVRAM 51

Problems Fixed in v3.0.5 Address Table 51

Problem Overview 51

Problem Detail 52

Work Around 52

Recommendations 53

Guidelines from FR003 TRANSCEND UNIX 5.0 UPDATE 53

Important Notes 54

Operating Considerations for Release 3.0.5 57

System 57

Web-based Management 57

SNMP 57

57

Ethernet 57

Bridging 58

Trunking 59

VLANs 59

Known Problems in Release 3.0.5 60

System 60

Management 60

Ethernet 61

Bridging 61

Trunking 62

6

R

ELEASE

I

SSUES

FOR

M

ULTILAYER

S

WITCHING

M

ODULES

Corrected Problems in Release 3.0.0 66

System 66

Bridging 66

Virtual LANs (VLANs) 66

IP 66

QoS 66

Roving Analysis 66

Web Console 66

Ethernet 66

4-port Gigabit Ethernet Layer 3 Switching Module (GBIC) 67

Corrected Problems in Release 3.0.5 67

QoS 67

RMON 67

RMON-2 Network Management Applications 67

IP Policies 67

OSPF 68

VRRP 68

Problems Fixed in v3.0.5 Address Table 68

Problem Overview 68

Problem Detail 69

Work Around 69

Recommendations 70

Guidelines from FR003 TRANSCEND UNIX 5.0 UPDATE 70

Important Notes 71

Operating Considerations in Release 3.0.5 74

System 74

SNMP 74

RMON 75

Ethernet 75

Bridging 75

Backplane Port Trunking 76

Trunking 76

Packet Filtering 77

Virtual Router Redundancy Protocol (VRRP) 77

IP 77

IP Multicast 77

AppleTalk 77

QoS 78

Roving Analysis 79

Filter Builder 79

Transmit and Receive Ports on GBIC Modules 79

Web-based Management 79

VLANs 79

4-port GBIC Multilayer Switching Module (3CB9RG4) 80

Known Problems in Release 3.0.5 80

System 80

SNMP 80

Ethernet 81

Bridging 81

Trunking 82

VLANs 83

Internet Protocol (IP) 83

OSPF 83

Virtual Router Redundancy Protocol (VRRP) 84

IP Multicast 84

IPX 84

QoS 84

RSVP 85

RMON 85

Web-based Management 86

4-port GBIC Multilayer Switching Module (Model

Number 3CB9RG4) 86

7

D

OCUMENTATION

C

HANGES

Ter mino logy 8 8

Ethernet 88

Internet Packet Exchange (IPX) 88

Important Considerations 89

Quality of Service (QoS) 90

Web-based Management 90

Resetting Modules 91

SNMP Traps 92

EME Command Changes in Release 3.0.5 92

Old command structure in software release 3.0.0: 92

New command structure in software release 3.0.5: 92

Examples 93

Setting SNMP Trap Destinations 94

8

S

OFTWARE

I

NSTALLATION

Verifying Module Software Releases and Compatibility 96

Verifying Software Releases on an Existing System 96

Verifying Software Releases on a New System and Modules 98

How to Obtain the Latest Software 100

Where to Place the Software 100

Terminology for the EME Module 101

Clarifying Acronym Use 101

Terms for Redundant EME Modules 101

Prerequisites for Software Installation 102

Upgrading the EME Module to Release 3.0.5 104

Upgrading a Single EME Module 105

Upgrading Two EME Modules 106

Installing EMC Boot Software 108

Installing EMC Operational Software 108

Installing EME Boot Software 109

Installing EME Operational Software 109

Upgrading Layer 2 Switching Modules to Release 3.0.5 110

Upgrading Multilayer Switching Modules From 2.1 to 3.0.5 111

Upgrading Multilayer Switching Modules From 3.0 or 3.0.1 to 3.0.5 114

Transition Issues from Release 2.1 to 3.0 114

Upgrade Procedure 116

Updating Emergency Download Parameters 117

Downgrading Modules From 3.0.5 to 3.0.0 or 3.0.1 119

9

R

EFERENCE

MIB Files 121

Entering Commands 122

Year 2000 Compliance 122

10

T

ECHNICAL

S

UPPORT

Online Technical Services 123

World Wide Web Site 123

3Com Knowledgebase Web Services 123

3Com FTP Site 124

3Com Bulletin Board Service 124

Access by Analog Modem 124

Access by Digital Modem 125

3Com Facts Automated Fax Service 125

Support from Your Network Supplier 125

Support from 3Com 125

Returning Products for Repair 127

1

O

VERVIEW

Scope

These release notes summarize operational requirements and issues for

the following Switch 4007 modules and software releases:

Table 1

Software Release Numbers Addressed in These Release Notes

Description Model Number Software Release Filenames

Management Module (EME) 3CB9EME Management software —

Boot code 3.0.0

Operational code 3.0.5

Controller software —

Boot code 2.1.0

Operational code 3.0.0

eme30000.bt

eme30005.op

emcv20100.bt

emc30000.op

9-port Gigabit Ethernet Layer 2

Switching Fabric

3CB9FG9 3.0.5 fg930005.all

24-port Gigabit Ethernet Layer 2

Switching Fabric

3CB9FG24T 3.0.5 fga24t30005.all

4-port Gigabit Ethernet Interface

Module

3CB9LG4 3.0.5 Not applicable; module

passes traffic directly to

switch fabric.

20-port 100BASE-FX Layer 2

Switching Module

3CB9LF20MM 3.0.5 lf20mm3005.all

36-port 10/100BASE-TX Layer 2

Switching Module

3CB9LF36R

3.0.5 lf36r30005.all

9-port Gigabit Ethernet Layer 2

Switching Module

3CB9LG9MC 3.0.5 lg9mc30005.all

12-port 10/100BASE-TX

Multilayer Switching Module

3CB9RF12R 3.0.5 rf12r30005.all

10-port 100BASE-FX

Multilayer Switching Module

3CB9RF10MC 3.0.5 rf10mc30005.all

4-port Gigabit Ethernet

Multilayer Switching Module

3CB9RG4 3.0.5 rg430005.all

12

C

HAPTER

1: O

VERVIEW

Important Notices

Read these important notices before you begin.

The Switch 4007 management interfaces refer to the Switch 4007

Management Module as the Enterprise Management Engine (EME). In

these release notes, the Switch 4007 Management Module is referred to

as the EME for brevity.

The term

Administration Console

refers to the menu-driven, command

line interface on switching modules; each switching module has its own

Administration Console. The terms

EME prompt

,

EME console

, or

system

prompt

refer to the command line interface that you first encounter

when you connect to the system. It is from this interface that you connect

to a switching module’s Administration Console, modify system settings

such as power and temperature, modify settings on the EME module, or

arrange software downloads.

The 10-port 100BASE-FX Multilayer Switching Module (3CB9RF10MC)

that is listed in Table 1 is new to the Switch 4007 product line at this

release.

Although the heritage of the Switch 4007 product line is the

CoreBuilder 9000 product line, these Switch 4007 release notes do not

cover all aspects that apply to the CoreBuilder 9000. These release notes

include only information about the subset of modules that are officially

supported under the Switch 4007 brand and about configurations that

apply to the Switch 4007 (for example, issues that deal with dual switch

fabrics are not included because the Switch 4007 chassis only has one

fabric slot). For a list of modules that are officially supported in a

Switch 4007 system, see Table 1. If you have a CoreBuilder 9000 system

or if you are operating unsupported modules in a Switch 4007 system,

we recommend that you download from the 3Com Web site the suite of

CoreBuilder 9000 Release Notes for Software Release 3.0.5.

To obtain later software maintenance releases or upgrades and

associated release notes for the Switch 4007, visit the 3Com Web site:

http://support.3com.com/

For comprehensive, up-to-date information about the Switch 4007 and

other 3Com products, see the online user guides on the 3Com Web site:

http://support.3com.com/nav/switches.htm

Important Notices

13

The Switch 4007 software and management interfaces are built from

CoreBuilder

®

9000 switch technology. In Switch 4007 software, the

interface prompts and displays indicate this heritage. The examples,

tables, and figures in the Switch 4007 documentation may also indicate

this heritage.

CAUTION:

Except for the EME which operates four different files on

mixed release numbers (see Table 1), all modules in the Switch 4007

chassis must run software release 3.0.5 for functional reasons. The

software for CoreBuilder 9000 modules and Switch 4007 modules is

identical. Upgrade the EME first, followed by the switching modules. For

software download and installation instructions, see the chapter

“Software Installation” later in these release notes.

CAUTION:

The Switch 4007 Setup Wizard, supplied on the Software

CD-ROM, is designed to simplify installation of the switch. Release 1.0 of

the Setup Wizard enables you to enter an invalid IP address or subnet

mask, which prevents Telnet access to the EME management module.

3Com recommends that you do not use the Setup Wizard until an

updated version is available from the 3Com Web site.

CAUTION:

To run the Transcend® Network Supervisor application (for

managing and monitoring Switch 4007 activity), the Microsoft® Virtual

Machine and Microsoft WinSock2 applications may be required on your

PC. During installation, Transcend Network Supervisor will check your

PC's configuration and prompt you if these files are needed. If required,

you should exit from the Transcend Network Supervisor installation utility

and proceed to download (from the Microsoft web site) and install each

of these applications separately. After they are installed, you can restart

the installation utility for Transcend Network Supervisor.

CAUTION:

This release requires that the EME have 20 MB of CPU RAM.

To determine the current CPU RAM size, enter

show eme

from the EME

command line interface. The

CPU Ram Size (MB)

field on the left side of

the screen indicates the amount of CPU RAM:

8

or

20

. If your EME has

8 MB of CPU RAM, you must replace one of the two 4 MB DRAM cards

with a 16 MB DRAM card (order number 3CB9EE). After you install it, you

will have the required 20 MB of CPU RAM. To order a 16 MB DRAM card,

contact your network supplier or 3Com representative.

14

C

HAPTER

1: O

VERVIEW

CAUTION:

Before you attempt to download any module software, save

the configuration file for the modules that you are upgrading to an

external device using the

upload

command from the EME prompt. Name

the files so that they uniquely identify the versions of the module code

that were in use at the time they were uploaded, as well as the chassis

and slot where the module is located. See the

Switch 4007

Implementation Guide

for an explanation about how to use this

command. You must save the configuration files because they are not

guaranteed to work with revisions of code other than the ones with

which they were created. If at some point you want to downgrade the

modules to preexisting code, you must use the configuration file that

corresponds to that version of code.

System

Requirements

Each Switch 4007 chassis has these minimum system requirements:

■

One power supply.

To increase device and network availability, you can optionally install a

second power supply.

■

One fan assembly.

■

One switch fabric module with software that is compatible with other

modules in the chassis.

Depending on the other modules that are installed in the chassis and

their associated throughput requirements, choose either the 24-port

Gigabit Ethernet Switch Fabric Module (Model Number 3CB9FG24T)

or the 9-port Gigabit Ethernet Switch Fabric Module (Model

Number 3CB9FG9).

■

One Management Module (Model Number 3CB9EME) with 20 MB of

CPU RAM and software that is compatible with other modules in the

chassis.

To increase device availability and network availability, you can

optionally install a second Management Module (EME).

■

An appropriate number of Interface Modules, Layer 2 Switching

Modules, or Multilayer Switching Modules with software that is

compatible with other modules in the chassis.

2

R

ELEASE

H

IGHLIGHTS

Software Release 3.0.5 is a maintenance release, however it also includes

a few new features. The applicability of new features to the Switch 4007

module types is outlined in Table 2.

The remaining sections in this chapter provide descriptions of the

features.

Table 2

New Features on Switch 4007 Modules

Layer 2

Switching

Modules

Layer 2

Switch Fabric

Modules

Multilayer

Switching

Modules

Management

Modules

(EME)

Accelerated

Address Aging

YES YES NO NO

Advanced

Autonegotiation

YES NO YES NO

Support for LX 70

GBIC Transceiver

YES YES YES NO

Trap Filtering NO NO NO YES

16

C

HAPTER

2: R

ELEASE

H

IGHLIGHTS

Accelerated

Address Aging

For all Layer 2 Switching Modules in Release 3.0.5, a third option has

been added to the

bridge spanningTree stpState

menu called

agingOnly

(other options are

enable

and

disable

).

Purpose

If you select the

agingOnly

option, the Spanning Tree Protocol (STP) is

disabled on the module but the address table’s aging interval will change

(becomes shorter) whenever the module detects that one of its links has

gone down. The objective is to flush addresses as quickly as possible.

Although STP is not operating on the module, this temporary, alternate

aging process draws upon a couple of the STP parameter values. These

can be system defaults or customized values.

How It Works

Under normal operating conditions, the Layer 2 module uses the aging

interval value that you set in the

bridge agingTime

command. However,

with the

agingOnly

option selected, whenever a module detects that one

of its links has gone down, the aging interval temporarily changes to the

value that you set in the

bridge spanningTree stpForwardDelay

option. Usually, this interval is much shorter than the

bridge agingTime

and thus addresses age more quickly. After a period of time equal to

bridge spanningTree stpForwardDelay

+

bridge spanningTree

stpMaxAge

seconds has transpired, a module then reverts to using the

value in

bridge agingTime

as the aging interval.

Essentially, the

agingOnly

option mimics the action that STP takes when

ports go down, but does so without having STP enabled on the module.

The accelerated aging process affects all addresses in the Layer 2

module’s address table; it is not limited to the addresses that are

associated with the down port.

This feature was not implemented on Layer 3 modules because it was not

needed. Whether STP is enabled or disabled, whenever a port has gone

down or is disabled, Layer 3 modules immediately flush all addresses that

are associated with that specific port.

Accelerated Address Aging

17

Recommendations

If you select the

agingOnly

option, 3Com recommends that you also set

the

stpForwardDelay

value to the lowest number in the allowed range.

This will ensure that addresses flush as quickly as possible.

If you are using Transcend Enterprise VLAN Manager on your network but

are not running STP on your module, 3Com recommends that you select

the

agingOnly

option.

Interaction with

Transcend Enterprise

VLAN Manager

The

agingOnly

option in Release 3.0.5 is especially helpful if you use

3Com Transcend Enterprise VLAN Manager software because it helps to

prevent incorrect MAC address-based VLAN assignments.

Prior to Release 3.0.5, if you did not have STP enabled, a Layer 2 module

would not flush MAC addresses upon a link down event. It would only

age addresses according to the value set in

bridge agingTime

. This

situation can cause VLAN-assignment problems when endstations are

frequently plugged and unplugged into ports on the module and the

Transcend Enterprise VLAN Manager (EVM) application is used on the

network. That is, if a new endstation (with a new MAC address) is

plugged into a port prior to the aging out of the old MAC address on that

port, EVM may assign the endstation to the VLAN to which the old MAC

address belonged, which could be an incorrect VLAN for the new

endstation.

In summary, prior to Release 3.0.5, if you wanted addresses to age more

quickly after a link down event, you would have to enable STP. Now, with

the

agingOnly

option, you do not have to do that.

18

C

HAPTER

2: R

ELEASE

H

IGHLIGHTS

Advanced

Autonegotiation

Advanced Autonegotiation is an enhancement to the standard

autonegotiation feature that is defined in the IEEE 802.3u specification,

which addresses how two ends of a 10/100-TX Ethernet connection

become synchronized in speed and duplex mode. Due to limitations of

the specification, certain configurations produce duplex mismatches that

generate errors, reduce network performance, and may even “lock up”

an entire 802.3u-compliant switch. 3Com developed Advanced

Autonegotiation to overcome these limitations and correct duplex

mismatches on 10/100 links. In addition, although the 802.3u

specification does not apply to 100FX ports, Advanced Autonegotiation

also helps correct duplex mismatches on these links.

Sample Problem

Description

To illustrate the problem with the 802.3u specification:

Imagine a switch-to-switch connection (or switch-to-PC NIC connection)

where port A has standard autonegotiation enabled but port B does not

and instead is fixed at 100 Mbps and full duplex mode. The

auto-detection process in standard autonegotiation allows port A to

detect and match the speed of port B but port A cannot detect port B's

duplex mode and therefore port A defaults to half duplex mode per the

specification. Thus, a duplex mismatch exists and causes problems for the

link, switch, and network.

This problem affects any vendor’s switch that complies with the

IEEE 802.3u specification. It is not unique to 3Com.

In this example, if port B had been fixed in half duplex mode, then a

duplex mismatch would not have occurred.

How Advanced

Autonegotiation

Works

New to Software Release 3.0.5, Advanced Autonegotiation is related in

functionality to the Ethernet Port Monitoring feature that was introduced

in Software Release 3.0.

Port Monitoring monitors the error counters on specified ports and

provides notification via traps and messages on the management

interfaces. Port monitoring can also partition (temporarily disable) ports

that exceed a system error threshold.

Advanced Autonegotiation

19

As with Port Monitoring, Advanced Autonegotiation also monitors port

error levels and provides notification, but goes further by changing a

port’s mode into full duplex mode. However, if errors continue to exceed

the system threshold, Advanced Autonegotiation partitions the port.

Configuration

Options

To provide flexibility, the Advanced Autonegotiation and Port Monitoring

features are enabled and disabled separately from standard

autonegotiation. The benefits of this arrangement include:

„ T

he Advanced Autonegotiation and Port Monitoring features can also

work for 100FX ports, which do not have an autonegotiation process.

„

Port Monitoring can be enabled for ports that have been set to

operate a fixed speed and duplex mode (autonegotiation is disabled).

Configuring Standard Autonegotiation

To enable or disable standard autonegotiation, at the CLI prompt, enter:

ethernet autoNegotiation

Then select a port or range of ports and enter either

enable

or

disable

.

Configuring a Fixed Port State

To set a fixed port state (standard autonegotiation is disabled), at the CLI

prompt, enter:

ethernet portMode

Then select a port or range of ports and enter the appropriate speed and

duplex mode.

Configuring Advanced Autonegotiation or Port Monitoring

To enable or disable either Advanced Autonegotiation or Port Monitoring,

at the CLI prompt, enter:

ethernet monitoring mode

Then select a port or range of ports, and enter one of these options:

„ disabled

— neither Port Monitoring nor Advanced Autonegotiation

is enabled.

„ enabled

— Port Monitoring is enabled

„ advanced

— Advanced Autonegotiation is enabled (includes the Port

Monitoring function)

20

C

HAPTER

2: R

ELEASE

H

IGHLIGHTS

Sample

Configurations and

System Behavior

This section describes how the system behaves in certain feature

configurations. Refer to Table 3 when reading the corresponding

paragraphs below.

Configuration A

Ports autonegotiate connections according to the IEEE 802.3u

specification. Error conditions are not monitored. No alerts are sent and

preventive actions are not taken. If the remote port (the port to which the

switch is connected) is fixed in full duplex mode or uses a non-compliant

version of autonegotiation, duplex mismatches are likely to occur, causing

problems for the link, switch, and portions of the network that rely on

that switch. However, if standard autonegotiation is enabled on the

switch and the remote port, the speed and duplex modes will be set

correctly.

Configuration B

Ports autonegotiate connections according to the IEEE 802.3u

specification. The system monitors specified ports for errors and sends

alerts through traps and console messages. If the remote port is fixed in

full duplex mode or uses a non-compliant version of autonegotiation,

duplex mismatches are possible. However, the Port Monitoring feature

can partition ports with high error rates (which, incidentally, may also be

caused by factors other than duplex mismatches such as damaged

cabling).

The error threshold is fixed in system software; it is not user-configurable.

The initial time period in which a port is partitioned (disabled) is 30

seconds. When the system reenables the port, it also immediately

monitors the error conditions. If the error threshold is reached again, the

port is partitioned again. The time that the port is partitioned increases

with each incidence, up to a maximum of 5 minutes.

Table 3

Sample Configurations

Standard

Autonegotiation

Enabled

Port

Monitoring

Enabled

Advanced

Autonegotiation

Enabled

Configuration A Yes No No

Configuration B Yes Yes No

Configuration C Yes No Yes

Configuration D No Yes No

Configuration E No No Yes

Page is loading ...

3com 4007 Release note

3com 4007 Release note

Related papers

Other documents