A text string containing general system information,
including the package identifier and the system's
software release number.    

A text string describing the physical platform
or chassis on which the system is running.    

A text string defined by the user. This
string can be used by a system running PPP
as a unique identification of itself to
its peer when communicating over a PPP link.     

Possible values are:


other, stdReboot
                

This object can be used to reboot the system.
If this object is set to stdReboot(2), the
system's action is determined by the value of
a3sysStartUpAction.  If that object has the value
monitor(1), the system will go into monitor
mode.  If that object has the value userListOnce(2)
or userListForever(3), the system will attempt to
reboot from the sources identified by the User Boot List.

If this object is read, the value, other (1),
will be returned.    

This table specifies where each IIO card
obtains its boot image.    

Each entry in this table corresponds to a
specific slot in the NetBuilder chassis.  If
an IIO board is in that slot, that entry
determines where that IIO board obtains its
boot image.    

This object specifies the slot into which
the IIO board corresponding to this entry
is placed.    

This object specifies the path and name of the
IIO board's boot image.  If the value of
this object specifies a drive, the path is assumed
to start from root.  If the value of this object does
not specify a drive number, this object specifies the
path starting from the config file directory specified by
a3sysUblConfigFilePath.  In this case, the value of this
object must not begin with a slash '/'.    

Possible values are:


empty, up, booting, recovering, dumping, 
halted, selfTestFail, error

This object provides the current state of the IIO
card installed in this slot.  If there is no IIO
card in the slot, this object will have the value
empty(1).  If the card is up and running, this object
will have the value up(2).  If the card is booting,
this object will have the value booting(3).  If the
boot has failed, and the card is in the process of
recovering from the failed boot, this object will have
the value recovering(4).  If in the process of
recovering, the IIO dumps its image, this object will
have the value dumping(5).  Note that this is simply
a sub-state within the more general recovering state.
If after recovering, the IIO card goes into a halted
state, this object will have the value halted(6).  If
the IIO card gets into an unrecoverable state, this
object will have the value error(8).    

The value of sysUpTime when the IIO board last
went into the UP state.    

The OID assigned to this version of Iio Software.    

The Test Boot Time indicates the number of seconds
after a test reboot the system will automatically
reboot.  Upon reboot, the system will start up a timer
initialized to the value of this object.  The object
a3sysTestRecoveryTimer contains the real time value of
this timer.  The timer will automatically start counting
down after the system comes up.  If this timer expires,
the system will automatically reboot using the Primary Boot
Source.

To cancel the timer, the object a3sysTestRecoveryTimer must
be set to zero.  This provides a recovery mechanism for a
system under test that loses management connectivity.    

Possible values are:


monitor, userListOnce, userListForever, 
local
                

This parameter determines the boot source
when the system is powered on or reset.  If
monitor (1) is chosen, the system enters
monitor mode immediately.  If userListOnce (2)
is chosen, the system attempts to boot from
primary and secondary sources defined by the
User Boot List.  (Specifics about the use of the
secondary boot source are provided by a3sysBootSources.)
This list may identify network boot sources or local
floppy sources, or both.
If userListForever (3) is chosen, the system
will keep trying the sources listed in the
User Boot List until one of them is successful.
If local(4) is chosen, the system will boot from
the local floppy.  The name of the file used is
identified by the value of a3sysUblFileName for the
Primary Boot Source.    

This object contains the real time value of the
Test Recovery Timer.  When the system is performing
a 'test boot' (ie, a boot when a3sysBootSources equals
testWithPrimaryBackup (3)), the system will start a
countdown timer initialized to the value of a3sysBootTime.
If this timer is allowed to count down to zero, the
system will reboot, this time using the primary boot source
instead of the test boot source.  If the timer is disabled, however,
before it counts down (the timer is disabled by setting
the value of this object to zero), the system won't reboot
and will continue to run the test boot source's software.

This timer is part of a comprehensive software update
strategy.  See the relevant 3Com manuals for more
details.    

This is a counter that tracks the number of times the
system has completed successfully a boot, no matter
how the boot was initiated (power-on, front-panel-button
reset, command line, or exception).    

This is a counter that tracks the number of times
the system has crashed and a reboot sequence is begun
by the exception handler.  Note, some type of crashes
are not able to update this counter due to various
hardware lockups.  Also note, this counter will be
incremented when a user resets the system from the
command line (RS).  This will not be incremented,
however, when the user reboots the system from the
command line (RB).    

Possible values are:


noDump, monitor, localDevice, userList, 
network

This determines whether or not a memory dump
is performed if the system fails due to a
software problem.  If noDump (1) is selected,
the system will not attempt to perform a memory
dump.  If monitor (2) is selected, the system
goes directly into monitor mode and waits for
further commands.  If localDevice (3) is selected,
the system dumps its memory to the local storage
device.  Since the memory dump will require several
floppy disks, the system will prompt the user via the
User Interface to change disks.  If userList (4) is
selected, the system will upload its memory to the
source specified in the User Boot List.

Only the NetBuilder Remote Office and NetBuilder II support
the network(5) option.  If this is set, the parameters in entry
four (dump) of a3sysUserBootListTable identify the destination.    

Possible values are:


primary, primaryAndSecondary, 
testWithPrimaryBackup, secondary

This parameter is used to specify how the entries
in this table are used.

If this object is set to primary(1), the system
will use only the primary boot source when
rebooting.  (note, this is the entry where
a3sysUblSource = primary(1)).

If this object is set to primaryAndSecondary(2),
the system will attempt to boot first from the
primary boot source, and, if that fails (after
a3sysUblMaxRetries attemps), the system will
try the secondary boot source.

If this object has the value testWithPrimaryBackup(3),
the system, when rebooting, will perform a test boot
using the 'test' boot source.  Note, the NetBuilder Remote
Office and NetBuilder II use entry 3 in a3sysUserBootListTable
as the 'test' boot source (a3sysUblSource = test(3)),
while other 3Com routers (NetBuilder Remote, NetBuilder
Remote Control, NetBuilder Local, and NetBuilder Remote
Access) don't support all 4 rows in a3sysUserBootListTable,
and simply use the secondary boot source (a3sysUblSource = secondary(2))
to identify the 'test' boot source.

After booting from the 'test' boot source, if the
Test Recovery Timer (a3sysTestRecoveryTimer) is
allowed to count down to zero, the system will
reboot using the primary boot source.  (see the
reference guide for details about test booting).
When in this mode, to prevent the system from rebooting
using the primary boot source, the Test Recovery Timer
(a3sysTestRecoveryTimer) must be set to zero.

Note, this object cannot be set to testWithPrimaryBackup(3)
explicitly.  Instead, by setting a3sysTestBootTimer to a
non-zero value, the system will automatically go into
'Test Boot' mode and this object will be given the
value testWithPrimaryBackup(3).

If this object has the value secondary(4), the system will
use only the secondary boot source when rebooting.    

This table defines a list of boot sources (and for the
NetBuilder Remote Office -- memory dump destinations).

There are two other parameters that dictate how the
contents of this table are used.  These parameters
are represented by a3sysStartUpAction and a3sysBootSources.

a3sysStartUpAction specifies what this system does when it
first comes up. If a3sysStartUpAction is set to userListOnce (2),
the system will make a single attempt to use the entries in
this table to identify how it should boot.  If a3sysStartUpAction
is set to userListForever (3), the system will make repeated
attempts at using the entries in this table.

If a3sysStartUpAction indicates that the system is to use this
table, the order in which the entries are used is dictated by
a3sysBootSources.  If a3sysBootSources has the value primary (1),
the system will attempt to boot only from the source identified by
entry 1 in this table.  If a3sysBootSources has the value
primaryAndSecondary(2), the system will attempt to boot first
from the source identified by entry 1, and, if that source fails,
the system will try the source identified by entry 2 (the secondary
source).  If a3sysBootSources has the value testWithPrimaryBackup(3),
the system will perform a test boot using the test boot source.  Note,
for the NetBuilder Remote Office, this is the third entry (test) in this
table.  For the NetBuilder II and the NetBuilder I family( NetBuilder Local,
NetBuilder Remote, NetBuilder RemoteAccess, and NetBuilder RemoteControl),
the test boot source is identified by entry 2 (secondary) in this table.
If the test boot source fails (see the Reference Guide for more details
on test booting), the system will revert back to the source identified
by entry 1 (primary) in this table.

The NetBuilder Remote Office supports a fourth entry in this table,
which identifies where over the network memory is to be dumped in the
case of a system crash.  Note, the destination device (a3sysUblDevice)
must be set to network (3), in this case.  Also note that many
of the columns in this row will be irrelevant and won't affect
where the memory gets dumped.

Note, all entries in this table apply only to future
boots.  They don't necessarily provide information
about previous boots.    

Each entry in this table contains a single boot source.    

Possible values are:


primary, secondary, test, dump
                

This identifies the entry number in this table.
Currently, the table is limited to two entries.
The first entry is labelled primary(1), the next
has the label secondary(2).

The NetBuilder RemoteOffice and NetBuilder II (as of
sw version 8.0) supports two additional entries.
Entry three (test) identifies a separate
boot block which is used when doing a test boot.
Entry four (dump) identifies where memory is to
be dumped.  Note, only a subset of the columns in
this entry are relevant.  Specifically, a3sysUblDevice
must have the value network(3) (ie, memory dumps are
preformed only over the network by the NBRO).    

Possible values are:


fap, ftp, other
                

This object specifies the protocol to use
to get the configuration files if they
are stored across the network.  Note, this
applies only if the value of
a3sysUblConfigFileDevice is network(3) or
bootDevice(1).  If a3sysUblConfigFileDevice
has the value bootDevice(1), then the
corresponding instance of a3sysUblDevice
must be network(2) for this object to have relevance.

This object has been changed to read-only in
9.0.  The only valid value for this object is
ftp(2).    

This object indicates the Username to be
used by the file service protocol identified
the corresponding instance of a3sysUblConfigProt.    

This specifies the Password to be used
by the file service protocol identified by
the corresponding instance of a3sysUblConfigProt.
Note, for reasons of security, the value of this
object will be hidden.  A string of 4 stars (*)
will be returned in response to any GET or GETNEXT
request.    

This specifies the Account Name used
by the file service protocol.
Note, for reasons of security, the value of this
object will be hidden.  A string of 4 stars (*)
will be returned in response to any GET or GETNEXT
request.    

Possible values are:


cpu-module, io-module, other
                

The MAC address to be used for booting over the
network.  This can be configured to use either the
MAC address assigned to the CPU module or the MAC
address assigned to the I/O module over which the boot
is being performed.    

Possible values are:


other, canonical, nonCanonical
                

This controls the format of addresses within
ARP packets sent by this system.    

Possible values are:


notApplicable, ppp, frameRelay, auto
                

This object specifies which serial link
protocol to use if a3sysUblSlot identifies
a slot with a High Speed Serial board.
If this is set to auto (4), the system
will try all supported protocols until
the serial line is active.

If there is a different kind of board in that
slot, the value of this object is ignored.    

Possible values are:


unknown, bps9600, kbps19, kbps38, 
kbps56, kbps64, kbps128, kbps256, 
kbps448, kbps1536, kbps2048, mbps4, 
mbps16

This object specifies the serial line or
Token Ring baud rate.  For all other types
of ports, this object will be ignored.    

Possible values are:


internal, external, unknown
                

This specifies whether to use an internal
or external clock source.  This applies only
to High Speed Serial ports.    

Possible values are:


unknown, rs232, v35
                

This object specifies the serial line
connector type.    

Possible values are:


localMediaA, localMediaB, network, 
monitor, other, auto

This object identifies the source from which the
system attempts to boot.  If this object is set to
localMediaA(1), the system will attempt to boot from
drive A of the local storage media (A is the flash drive
for those systems with both flash and floppy drives),
using the filename identified by a3sysUblFileName.
If this is set to localMediaB(2), the system will
boot from drive B.

If this object is set to network (3), the system will
attempt to boot from a BOOTP/TFTP server attached to
the network.  The network interface that is used in the
booting is identified by both a3sysUblSlot and
a3sysUblInterface.

The name of the boot file on the remote system is
identified by a3sysUblFileName.

monitor(4) is no longer supported.

If this object has the value other(5), nothing has
been specified.    

This specifies a string to initiate a
WAN connection.  The specified string required
is interface and protocol specific.  The maximum
string length is 80 bytes.  Note, this applies
only to High Speed Serial ports.    

The IP Address of this system used in packets
when booting over the network.    

The IP address of the gateway that will forward
packets to the Boot Server.    

The IP address of the configuration files Server,
if needed.    

The mask to be applied to the addresses specified
above.    

Possible values are:


other, bootp, configAddr, bootpRarp, 
rarp, rarpBootp

This specifies the address discovery protocol
to use for booting from the network.  If configAddr(3)
is specified, then the configured addresses are
used.  If nothing has been specified, other(1) is
returned.    

This is needed when booting over a port that
uses a protocol that requires a password, e.g,
PPP.    

This specifies the path and name of the boot
file.  For example, to specify the file boot.29k in
the root directory, this object should
have the value 'boot.29k    

DEPRECATED
This object has been deprecated. (use a3sysUblFileName
regardless of whether it's local or remote).    

This specifies the physical slot where the IO module
from which the system will be booting is installed.
This only applies when a3sysUblDevice is set to
network(2)    

Possible values are:


unknown, interfaceA, interfaceB
                

This specifies the physical port on the IO
module (installed in the slot identified by a3sysUblSlot)
that the system will be booting from.  This only applies
when a3sysUblDevice is set to network(2).  If there
is only one connector in the module, this object should
have the value: interfaceA(2).    

This object determines the number of times the
system will try to boot from the source identified
by this table entry before going to the next entry.    

Possible values are:


bootDevice, local, network, other
                

This specifies the device used to access the
configuration files needed by this system.  If
this object has the value bootDevice(1), the
system will look for its configuration files on
the same device as its boot files.  This device is
specified by a3sysUblDevice.  If this object has
the value network(3), the system will look for
its configuration files on the device specified
by a3sysUblConfigIpAddr.  If this object has the
value local(2), the system will look for its
configuration files on the local storage media.
If this object has the value other(4), nothing
has been specified.

In all the cases listed above, the path for the
configuration files is specified by
a3sysUblConfigFilePath.    

This object specifies the path to the configuration
files needed by this system.    

Possible values are:


primary, secondary, monitor, test
                

This object identifies the source from which the
system last booted.

The specifics of the boot source can be found
from the corresponding User Boot List entry.    

Possible values are:


none, unknownLocalAddress, 
unknownServerAddress, noServerResponse, 
fileTransferFailed, imageNotFound, 
imageInvalid

This object identifies the reason for the
most recent boot failure.    

The date and time as reflected by the system
clock at the time the system last rebooted.
The date has the format yy/mm/dd hh:mm[:ss].    

The IP address of the configuration file server
used during the most recent boot.  Note, even
if the configuration files were obtained locally,
an address may have been configured.  This is the
address used when performing all ftp PUT and GET
operations.    

The IP address of the gateway that was used to
forward packets to the boot server or configuration file
server during the last boot.    

The IP subnet mask configured during the last boot.    

Possible values are:


bootDevice, local, network, other
                

The config file device used during the last boot.    

The config file path used during the last boot.    

If the config files were obtained from a file server
during the last boot, this object contains the user
name used during the ftp transfer of those files.    

Possible values are:


other, copy, do, delete, rename, 
directory, format, copySystem, checksum, 
abortCopy, makeDir, rmDir, getFileInfo, 
ftpGet, ftpPut, cleanFlash

This object is used to initiate a file
management operation.  When set to copy(2), the
system will get the file from the Source device
(identified by a3sysFmSourceIpAddr and
a3sysFmSourceFile) and copy it to the
Target device (identified by a3sysFmTargetIpAddr
and a3sysFmTargetFile).  Note, both the
Source and Target devices cannot be
remote systems.  At least one must be
the local system.

All information about the file
and the server is taken from the values
of the other objects in this group.  To
avoid unnecessary errors, the relevant objects
in this group should be examined and
their values validated before setting this object
to copy(2).

Currently, the do(3) enumeration is not supported.

If this object is set to delete(4), the system
will delete a single file on the local storage
device.  The file is identified by a3sysFmTargetFile.

For software release 6.2, the rename(5) enumeration
is not supported.  This is supported, however, by
release 7.0.

If this object is directory(6), the system will list
the file in the directory identified by a3sysFmTargetFile.
The resulting list can be obtained by examining
a3sysDfTable.

For software release 6.2, enumerations 7 through 9
are not supported.  Enumeration 7 and 9 are supported
by release 7.0.

If this object is set to abortCopy(10), the
system will abort any file copy process in
progress.

If this object is set to makeDir(11), the system
will create a directory off the root directory. The
name of this directory is specified by a3sysFmTargetFile.

If this object is set to rmDir(12), the system will
remove the directory identified by a3sysFmTargetFile.

If this object is set to getFileInfo(13), the system
will retrieve information about the file identified
by a3sysFmTargetFile and return that information via
the a3ComFileInfo group.  (ie, examine the contents
of that group after this object is set to getFileInfo(13)).

If this object is set to ftpGet(14), the system
will retrieve the file identified by a3sysFmSourceFile.
It will retrieve the file from the device from
which the configuration files were originally obtained.
That device can be identified by
a3sysLbConfigFileIpAddr.  Note, even if the config
files were obtained locally, a valid IP address may
have been configured.  That is the device used for
future ftp operations.

If a path is not specified, the file will be taken
from the configuration file directory.  The config
file directory cay be identified by
a3sysLbConfigFilePath.  If a relative
path is specified, and the configuration files were
originally obtained (ie, at last boot) from the
network, the path is interpreted relative to the
configuration file directory.  If a relative path
is specified and the configuration files were originally
obtained locally, the path is interpreted relative
to the login directory.  Absolute paths are allowed.
Once obtained, the file will be placed in the location
identified by a3sysFmTargetFile.  Note, this must be
on one of the local storage devices.

If this object is set to ftpPut(15), the system
will place the file identified by a3sysFmSourceFile
and place it on the device from which the config
files were obtained originally.  The path and
filename of the placed file is identified by
a3sysFmTargetFile.  As with ftpGet(14), if a relative
path is specified, and the configuration files were
originally obtained from the network, the path is
interpreted relative to the configuration file
directory.  If a relative path is specified and the
configuration files were originally obtained locally,
the path is interpreted relative to the login
directory.  Absolut paths are allowed.  Note, the
source file must be on one of the local storage devices.

If this object is read, other(1) will be
returned.    

This object specifies the results of a ccitt crc16
cyclic redundancy check performed on the file specified
by a3sysTargetFile.  The value of a3sysTargetFile at
the time this crc was performed is provided by a3sysFmCksumFile.    

This object specifies the file upon which the last ccitt crc16
cyclic redundancy check was performed.  The results of this operation
are specified by a3sysFmCksum.    

This object specifies the value of sysUpTime when the last ccitt crc16
cyclic redundancy check was performed.  The results of this operation
are specified by a3sysFmCksum.    

This object specifies the name of the file to which
the rest of this group refers.    

This object specifies the date when the file (specified by
a3sysFiName was last updated.  The format of the date is
yy/mm/dd hh:min:sec.    

This object specifies the value of sysUpTime when this group of
objects was last updated.  To update this group, set a3sysFmTargetFile
to the desired file, and set a3sysFmOperation to getFileInfo(13).    

This object specifies the size of the file (specified by a3sysFiName)
in bytes.    

This object specifies the IP address of
the Source device from which files are
obtained.

If this is set to zero's, the local storage
device is assumed.    

This specifies the path and name of
a source file.  For example, if the
action specified by a3sysFmOperation is
copy(2) or rename(5), this identifies the
path and name of the file to be copied or
renamed.

If there is no leading path string, the
source file will be accessed from the root
directory.  For devices with multiple disk
drives, the drive will be identified by appending
a prefix to the path.  For example, a:/path/name    

This object specifies the IP address of
the target device to which files are
copied, renamed, etc.    

This specifies the path and name of
the target file on the target system.
(The filename may contain the string '@M'
which will be expanded to the system MAC address.
Alternatively, the filename may contain
the string '@m'  which will be expanded to
the last six characters of the system MAC address.
This provides a mechanism for a remote system to
generate system specific filenames automatically.)
If there is no leading path string, the
file will be accessed from the root directory.
For devices with multiple disk drives, the drive
will be identified by appending a prefix to the path.
For example, a:/path/name.

If the action specified by a3sysFmOperation is copy(2),
this identifies where, on the target system (identified
by a3sysFmTargetIpAddr) the file is to be placed and the
name to give it.

If the action specified by a3sysFmOperation is
delete(4), this identifies the path and
name of the local file which is to be
deleted.

If the action specified by a3sysFmOperation is
directory(6), this identifies the full path
of the directory that is to be listed.    

Possible values are:


inactive, inProgress
                

This identifies the current status
of the file management operation.  This applies
to the following operations: copy(2),
and directory(6).  If there
is an operation in progress, this object
will have the value inProgress(2).  Otherwise
inactive(1) will be returned.    

This specifies the value of sysUpTime when
the most recent file management operation was
initiated.    

Possible values are:


none, successful, inProgress, 
badSourceAddr, badSourceFile, 
badTargetAddr, badTargetFile, 
noResponse, noFile, noSpace, 
noPermission, writeError, timeout, 
badChecksum, badOperation, aborted, 
other, badDefaultDrv, badTargetPort

This object identifies the results of the
most recent attempt at a file operation.  If no
file operations have been attempted since the
system was initialized, this object will have the
value none(1).

If the last operation was successful, this object
will have the value successful(2).

If the last operation could not be initiated
because there was another operation in progress,
this object will have the value inProgress (3).

If the source IP Address is invalid, this object
will have the value badSourceAddr(4).

If the source file name contains a syntax error,
this object will have the value badSourceFile(5).

If the target IP Address is invalid, this object
will have the value badTargetAddr(6).

If there was a syntax error in the identification
of the target file (a3sysFmTargetFile), this
object will have the value badTargetFile(7).

If the remote server does not respond, this
object will have the value noResponse(8).

If either the source file or target file could
not be found, this object will have the value
noFile(9).

If there is no space on the destination system
this object will have the value noSpace(10).

If the destination file location is write protected,
this object will have the value noPermission(11).

If there is an error encountered while
writing the file to its destination, this object
will have the value writeError(12).

If the transfer took too much time and exceeded
its limits, this object will have the value timeout(13).

If the verify operation failed, this object will have
the value badChecksum(14).

If the operation requested is not supported by this
platform or software version, this object will have
the value badOperation(15).

If the opereration was aborted by a user, this object
will have the value aborted(16).

If no drive is indicated in either the source or target
files, and the default drive is not local (this will be
the case when the system obtained its config files over
the network the last time it booted), this object will
have the value badDefaultDrv(18).

This object will have the value other(17) if an error
occured that is not listed here.    

This object specifies the value of sysUpTime when
the list of files on the system disk was last updated.
This list is updated by setting a3sysFmOperation to
directory(6).    

This object identifies the directory path under which
the files listed in a3sysDfTable were obtained.  Where
necessary, this object also identifies the disk drive
where the files are stored.    

This table contains a listing of all the files in a
specific directory on one of the systems disks.  The
directory and disk are identified by a3sysDfPath.
Each entry in this table contains information about
a single file.    

Each entry in this table describes a single disk file.    

This contains the name of a single file on the disk.    

Possible values are:


file, directory
                

This specifies whether the file identified by the
corresponding instance of a3sysDfName is a regular
file or a directory.    

The total size (in bytes) of the drive identified by
a3sysDfPath    

The available space (in bytes) of the drive identified
by a3sysDfPath.    

This table specifies the recovery procedure
for each Intelligent IO board in the system.
This also specifies the recovery procedure
for the CEC card.  Note, the eeprom version
must be 5 or greater for this table to operate
properly.    

Each entry in this table corresponds to a
specific slot in the NetBuilder chassis.  If
an IIO board is in that slot, that entry
determines the action taken by that IIO
board in the event it crashes.  There is also
an entry in this table for the CEC board.    

This object specifies the slot into which
the IIO (or CEC) board corresponding to this
entry is placed.    

Possible values are:


halt, haltSystem, reboot, rebootSystem, 
dumpAndReboot, selectiveDumpAndReboot

The value of this object determines the
action taken if the IIO (or CEC) crashes.
If the value of this object is
selectiveDumpAndReboot (5), the value of
a3sysIioRecoverySelect determines which
IIO (or CEC) boards will dump and reboot
in the event that this IIO board crashes.    

This object specifies the IIO or CEC
boards that will dump and reboot in the event
this IIO or CEC board crashes.  This
object is relevant only if the value of
a3sysIioRecoveryProcedure is
selectiveDumpAndReboot (6).

The boards are specified by their slot.  Each
slot is represented by a single bit in the
value of this object.  If that bit is set (to
1), then that board will dump and reboot.

Slot 0 is used to identify the CEC board, and
corresponds to the least significant bit in
this object.

Slot 1 is used to identify the IIO board in
that slot and corresponds to the next
significant bit in this object.  The identification
of all other boards follows this convention.    

This table contains information about the
chips that are used in the CPU board of the
system.    

Each entry in this table contains information
about one of the chips installed in the CPU
module.    

This identifies a specific slot (and
hence, a specific board).  All the Chips
described with this index are located
on a single board.    

This identifies a specific chip on the board
identified by a3sysChipSlotIndex.    

This provides general information about
the chip, including its part number and
revision number.    

This table contains information about the
system's memory configurations.    

Each entry in this table contains information
about a specific memory component.  The
information includes the memory type, its
starting address and its size.    

This identifies the slot (and hence the board)
that supports the memory elements identified
by this entry in the table.    

The index into this table.  Each memory component
is identified by a unique value of this object.
This is specific to the board identified by
a3sysMemSlotIndex.    

Possible values are:


other, ram-instruction, ram-data, 
ram-shared, rom-fprom, rom-eeprom, 
ram-total

This object identifies the type of the memory
component.    

The starting address of the memory component.    

The number of slots (empty or not) in the system    

A table that contains information about the IO boards
in this system.    

A list of information for each IO board in the
system.    

This contains general information about the
Board, including the model type, the serial
number, and manufacturing information.    

The number of physical ports supported by
this board.    

The Object Identifier assigned to this
Board.    

Possible values are:


other, reset
                

When this object is set to reset(2), the IO
board in the slot specified by this instance
identifier of this object is reset.  If a GET
request is sent for the value of this object,
other(1) is returned.    

This object returns the version of the firmware
that is running on this network interface board.
A list of all the OIDs assigned to 3Com router
firmware can be ftp'd from ftp.3com.com.    

Possible values are:


local, universal
                

This object allows the user to determine the format
of the time/date stamp that is included with each
audit trail message the system generates.  This
only applies if there is a Network Control Server
for the IBM PC/AT (NCS/AT) or Remote Boot and
Configuration Services (RBCS) server on the attached
network.  Audit trail messages are generated by
various network events and are displayed on the
NCS or RBCS console.    

DEPRECATED
The address of the NCS or the RBCS that serves
as the log server for the system.  The log server
receives all of the system's audit trail messages.    

The current date and time as reflected by the
system clock.  The date is displayed via the User
interface and Audit Trail Messages as
yy/mm/dd hh:mm[:ss].  This same format must be
used when setting the Date.    

This parameter specifies the displacement, in
minutes, from non-daylight savings time.  The
a3sysDSTime object, along with the a3sysTimeZone
object, allows the system to support Universal
time for network communications spanning different
time zones.    

This object specifies the number of minutes
displacement west of Greenwich the system's site
is located.  A negative number for this parameter
indicates how many minutes displacement east of
Greenwich the site is located.  A positive number
indicates the number of minutes west of Greenwich.    

Possible values are:


enabled, disabled
                

This object determines whether another device
can access this system via REMOTE    

Possible values are:


enabled, disabled
                

This object determines whether another device
can access this system via TELNET    

Possible values are:


enabled, disabled
                

This object determines whether another device
can access this system via the Console    

Possible values are:


enabledTraps, enabledNoTraps, 
disabledTraps, disabledNoTraps

This object determines whether another device
can access this system via SNMP.  Note, once
SNMP access is disabled, the NMS will no longer
be able to access this system via SNMP.

If this is set to enabledTraps(1), the system
allows SNMP access and will send traps when
appropriate.

If this is set to enabledNoTraps(2), the system
allows SNMP access, but no traps will be sent.

If this is set to disabledTraps, the system
does not allow SNMP access, but will send
traps when appropriate.

If this is set to disabledNoTraps(4), the system
does not allow SNMP access and does not
send any traps.    

This table contains all the community strings
known to the SNMP agent.    

Each entry in the table contains information
about a single community string.     

Possible values are:


readOnly, readWrite
                

This identifies the level of access allowed
for this community string.    

Possible values are:


genericOnly, authenOnly, allTraps, 
noTraps
                

This specifies which traps get sent to the
managers specified by this community string.    

This object is used to add and delete
entries in this table.  See the notes
describing RowStatus at the beginning
of this MIB.    

This table contains the Managers that
are allowed to use the community strings
identified in a3sysSNMPCommTable.  Each
Manager is identified by its IP address.    

Each entry identifies a single Manager,
community string pair.    

This identifies a single Management station
that is allowed to use the community string
associated with this entry.  The set of all
entries with same value of a3sysSNMPMgrCommString
identifies all the Managers that are allowed
to use that community string.    

This object can be used to mask part of the
IP address specified by a3sysSNMPMgrAddress.
The use of this mask can then be used to identify
a range of addresses that are allowed to use
this community string.    

This object is used to add and delete entries
in this table.  See the notes describing
RowStatus at the beginning of this MIB for
specific instructions on how to do this.    

This table contains the IP addresses that
are allowed to use Telnet to access to
the NetBuilder in the TelnetManager table.    

Each entry identifies a single Manager,
community string pair.    

This identifies a single Management station
that is allowed to use the Telnet to manage
the NetBuilder.  Maximally, six (6)
IP addresses can be configured in each NB.    

This object is used to add and delete entries
in this table.  See the notes describing
RowStatus at the beginning of this MIB for
specific instructions on how to do this.    

Each entry identifies a single system password.    

Possible values are:


valid, invalid
                

User Status.  `invalid' is used to indicate this user
is no longer allowed to access this device, and the
table entry may subsequently be re-used. Note that
the Status of default Users cannot be set to invalid.    

An ASCII string for the User Name.  Empty strings are
not allowed.  The index column for the User Table.  There
are two default users defined, 'root' and 'user'.    

Possible values are:


monitor, secureMonitor, manager, 
specialist, security

User Access Level defining the scope of management allowed
for this user.  Note that the access level of default Users
cannot be changed.    

Possible values are:


enabled, disabled
                

This object indicates whether this system's passwords
can be changed via snmp.    

The number of seconds between broadcasts of the
system's address on the attached network.  This
only applies to 3Com's NETMap protocol.  If this
object is set to 0, the broadcasting of the system's
address is disabled.    

Possible values are:


noDrives, driveA, driveB, driveAB
                

This object identifies which disk drives are supported
by this system.  noDrives(1) means no disk drives are
supported.  driveA means only drive A is supported.
driveB means only drive B is supported, while driveAB(4)
means both drives A and B are supported.    

This object has the IP address of the last seen
bogus DHCP or BOOTP server.    

This object returns the version number of the EEPROM
on a NetBuilderII.  Various features are dependent on
having the correct version of EEPROM resident on the
NetBuilderII.    

This object returns the number of active X25 connections
currently maintained by the NetBuilder.    

Possible values are:


on, off
                

If on, the system is allowed to negotiate for
binary transmission when a Telnet connection is
made.    

This object contains the value of sysUpTime
when the most recent change was made to this
system, either via the Console, TELNET, or
through SNMP.    

This object provides a measure of the
current utilization of the CPU on this
system.    

The system's MAC address.  For those devices
whose CPU boards contain a MAC address, this
object provides the value of that address (NB2's).
For those devices whose CPU boards don't contain a
MAC address (NB1's), this provides the MAC address
of the first interface.    

This identifies the MAC address to which the @m
symbol is expanded when doing file copies.    

This specifies the value of sysUpTime when the last
virtual port was added or deleted.  This object should
be used to determine if and when the set of virtual ports
supported by this system has changed.    

Possible values are:


driveA, driveB
                

This object identifies the current default drive
for this system.    

Possible values are:


floppy, flash, unknown, noDrive
                

This object identifies the current default
drive type for this system.    

Possible values are:


unknown, bps110, bps300, bps600, 
bps1200, bps2400, bps4800, bps9600, 
bps19200, bps38400, bps57600

This object sets the baud rate for the
console port, which is located on the CEC
module's connector/LEDC panel.    

Possible values are:


unknown, bps110, bps300, bps600, 
bps1200, bps2400, bps4800, bps9600, 
bps19200

This object sets the baud rate for the
auxiliary port, which is located on the CEC
module's connector/LEDC panel.    

Possible values are:


skip, testOnce, other, loop
                

This parameter determines how the system handles
self tests when the system is powered on or
reset.  The system can be configured to skip its
self tests, run self tests once, or run self
tests continuously (loop).