DEC-ELAN-MIB: View SNMP OID List / Download MIB

When new GIGAswitch MIBs are released to the public, they will be given new version numbers. The implementation strategy allows multiple versions to be supported simultaneously. MIB versions greater than or equal to this version are still supported.

When new GIGAswitch MIBs are released to the public, they will be given new version numbers. The implementation strategy allows multiple versions to be supported simultaneously. MIB versions less than or equal to this version are still supported. A management station may load a MIB which is not supported until the GIGAswitch software is updated.

The number of unused bytes of management memory available on the clock card. The management memory is used for storing management parameters.

This object, when read, returns a value of other(1) unless it is in the middle of rewriting the management memory. At such times, it will return rewriting(3). The state will revert to other(1) when the action is completed. Setting this variable to rewrite(2) will cause the SCP to attempt to rewrite the management Memory on the clock-card. Attempts to set this variable to all other values result in an error. Rewriting the management memory gets rid of duplicate entries, and thus may increase the available space. This action should be allowed to complete before intentionally removing power from the SCP or clock card. If the value is set to clearAndLock(4), management memory is completely erased. From this point on, SNMP operations that write management memory will fail, except for sets to the mgmtMemoryData object. In fact, the clearAndLock action must be set before management memory can be re-written using the mgmtMemoryData object. The GIGAswitch must be rebooted after the clearAndLock action (and after it has been re-written, if so desired) in order to allow future SNMP operations to be logged to management memory. Enumeration: 'rewriting': 3, 'clearAndLock': 4, 'other': 1, 'locked': 5, 'rewrite': 2.

The table for managing management memory.

A record of management memory.

Index of 80 byte binary records

SNMP object mgmtMemoryData allows the user to read management memory and, with certain restrictions, to write it as well. In particular, this object allows the user to read a management memory image and, at a later time, restore it. Management memory is accessed in uninterpreted 80-byte binary records, numbered starting from 1. As a result, doing a GET of instance number N will return bytes 80*(N-1) through 80*N-1 from management memory. If an attempt is made to read beyond the end of written flash, an error is returned; if a read of a record spans the end of written flash, only the valid data is returned. To restore a management memory image, management memory must first be cleared and locked using the clearAndLock action on the mgmtMemoryAction object. Then management memory may be written sequentially, writing 80 bytes at a time until the last write, at which point less than 80 bytes may be written. During this operation, and until the GIGAswitch is rebooted, other SNMP sets requiring writes to management memory may not be done. It is therefore recommended that the GIGAswitch be booted as soon as possible after management memory has been restored. Any attempt to write a management memory record out of sequence, for example writing record 5 followed by record 4 or record 7, results in an error.

The status of the Power System Controller (PSC). Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The firmware revision of the Power System Controller (PSC).

The hardware revision of the Power System Controller (PSC).

Indicates the position of the keyswitch. The keyswitch position determines the type of access allowed to network management and to out-of-band management. For SNMP access, secure means no SNMP access. Local means read-only SNMP access. Other values allow read-write SNMP access. All access is still subject to the community string, IP address, and privileged port restrictions. Enumeration: 'fault': 1, 'remote': 4, 'local': 3, 'secure': 2, 'worldAccess': 5.

The status of the PSC firmware image. If the value of this object is downloadRequired(2), the manager should download a new firmware image to the PSC. This can be done by using objects in the gigaUpgradeSoftware group. Enumeration: 'downloadRequired': 2, 'okay': 1.

Status of the GIGAswitch backplane. Enumeration: 'fault': 2, 'okay': 1.

The cabinet temperature. Enumeration: 'high': 2, 'excessivelyLow': 5, 'excessivelyHigh': 3, 'low': 4, 'normal': 1.

The value of this variable determines how the SCP responds to a condition of too high or too low cabinet temperature, or both both fans inoperative. If the value is heedWarning(1) the system will be shut down when the temperature goes outside the designed limits or both fans are inoperative. If the value is ignoreWarning(2), the system will continue to operate when either of these conditions occur. Setting this variable to ignoreWarning(2) allows the manager to cause a system that is too hot or too cold to continue to run. This variable will also allow both fans to be inoperative and still allow the system to continue to run. Managers should note that doing so may be detrimental to the equipment. This object has a default value of heedWarning(1). Enumeration: 'heedWarning': 1, 'ignoreWarning': 2.

The status of the right power unit. Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The input source of the right power unit. A value of ACline(1) is returned if the power supply is connected to an AC line. A value of DC48V(2) is returned if the power supply is connected to a 48 volt DC (telecommunications) line. A value of none(3) is returned if the power unit is not present or not powered on. See the batteryUsing object to see if the battery or this power source is being used. Enumeration: 'acLine': 1, 'dc48V': 2, 'none': 3.

Output power of right power unit, in watts.

The status of the left power unit. Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The input source of the left power unit. A value of ACline(1) is returned if the power supply is connected to an AC line. A value of DC48V(2) is returned if the power supply is connected to a 48 volt DC (telecommunications) line. A value of none(3) is returned if the power unit is not present or not powered on. See the batteryUsing object to see if the battery or this power source is being used. Enumeration: 'acLine': 1, 'dc48V': 2, 'none': 3.

Output power of left power unit, in watts.

The number of slots in the box.

Identifies the slot the Switch Control Processor (SCP) occupies. A value of 0 will be returned if an SCP has not been chosen.

Describes the current configuration of the box.

The description and status of the card plugged into the slot.

The slot number. Varies from 1 to slotNumber.

The status of the card. If the value is read as notPresent(1), then the entire entry should be considered invalid. Writing a value of powerDown(2) will cause the SCP to power down the card. Writing a value of powerUp(3) will cause the SCP to power up the card. Writing a value of powerDownThenUp(4) will cause the SCP to power cycle the line card. Attempts to set any other values will result in a badValue error. The clock and crossbar cards cannot be powered up or down through this object. They are fundamental to the GIGAswitch's operation. Unpopulated slots are notPresent(1), and can not be powered up or down. Enumeration: 'selfTestInProgress': 7, 'powerUp': 3, 'fault': 5, 'powerDown': 2, 'revisionMismatch': 6, 'notPresent': 1, 'powerDownThenUp': 4.

The type of the Card. Enumeration: 'gs2000-plus': 12, 'clockCard': 5, 'fgl4': 7, 'xgl4': 10, 'fgl2': 2, 'agl-2': 6, 'other': 1, 'agl-2-plus': 8, 'xgl2': 9, 'gs2000': 11, 'cbs36': 3, 'switchEngine': 4.

The Hardware revision number of the card.

The Firmware revision number of the card.

Describes the current IP address and community string of any modules which are hosted in the switch (eg GS2000).

The IP and community of the module hosted in the slot corresponding to the index.

The slot number. Varies from 1 to slotNumber.

The IP address of the hosted module.

The speed of the fans. Set this variable to maximum(1) for maximum cooling where noise does not matter. Set this variable to normal(2) to cause fan speeds to be under temperature control. Enumeration: 'maximum': 1, 'normal': 2.

The status of the right fan tray. Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The status of the left fan tray. Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The status of the backup battery. Enumeration: 'fault': 3, 'notPresent': 1, 'okay': 2.

The source of power being used for the box. The value batteryPower(2) indicates that the backup battery unit is being used to power the GIGAswitch. The external power line can be either AC or a 48 volt DC telecommunications power line. Enumeration: 'externalPower': 2, 'batteryPower': 1.

The charge-level of the backup battery. Meaningful only if the battery is present. Enumeration: 'fullyCharged': 1, 'okay': 2, 'low': 3.

Only the value test(3) can be written. Writes of other values are erroneous. This shows the result of the last battery test performed. Testing the battery is risky, since the GIGAswitch is temporarily switched to run off the battery, and if the battery-backup system is not working properly, the GIGAswitch fails and restarts. Meaningful only if the battery is present. Enumeration: 'fail': 2, 'test': 3, 'pass': 1.

A list of front panel port number to MIB-II interface number mappings.

Assigns the MIB-II interface ifIndex for a physical datalink (cable) connection to the box.

The 1-based slot number of the module.

The 1-based media connection to the module.

The assigned MIB-II ifIndex.

The assigned Bridge MIB dot1dBasePort.

A list of mPort entries.

A collection of objects containing information for a given mPort MAC entity

The value of the SMT index associated with this mPort MAC.

The value of the MAC index associated with this mPort MAC.

When true, this link will be enabled to operate in concentrator mode, i.e. mport. Enumeration: 'false': 2, 'true': 1.

A list of LED entries, one for each module.

Each entry describes the state of one module.

The module index into the table.

The number of LEDs on this module.

A list of LED entries, one for each module LED.

Each entry describes the state of one module LED.

The slot index into the table.

The led index within the slot given by slotIndex.

A textual description of the information which the LED is meant to convey. i.e.: +5 Volt Power, DC Okay ATM port activity. Diagnostic status.

The ledProgram string is a sequence of instructions for the LED state. The LED constantly repeats the program. Each LED state is represented by a two octet sequence where the value of the first octet of the pair indicates the color of the LED, and the value of the second octet of the pair indicates the duration in which that color will be present. +----------+----------+ --/ /-- +----------+----------+ | Color | Duration | | Color | Duration | +----------+----------+ --/ /-- +----------+----------+ The 'color' octet may have one of the following values: 0 - off 1 - other 2 - red 3 - yellow 4 - green 5 - blue 6 - red-blinking 7 - yellow-blinking 8 - blue-blinking 9 - green-blinking The value 'off' indicates that the LED is off. The value 'other' indicates a color not covered by any others in the list. The value of the second octet in each pair indicates the duration in which that color will be present. A value of zero indicates that the LED is off. A value of 0xff indicates that the LED is always on. Values in between 0 and 0xff indicate the duration in 10 ms ticks. A zero length string may be returned if the LED is 'not present'. This indicates that the LED is currently not visible. Activity LEDs are a special case. Activity LEDs are defined as LEDs which blink whenever data is received on the line. They are typically on solid under heavy activity. Since these LEDs can change rapidly, the following rules apply: o The initial state of activity LEDs is off. o If the line shows activity any time in a 10 second period, then the LED is shown as on. o If the line shown inactivity any time in a 10 second period, then the LED is shown as off. See the 'pcomLedProgram' object in the DECHUB900-COMMON MIB for examples.

This table allows filter matrices to be succinctly specified and named. These matrices may later be used and combined in filter specifications.

A particular named filter matrix.

This name for a filter matrix is whatever the user likes, as long as it is a unique filter matrix name.

A matrix is expressed using a shorthand that says what input ports can talk to what output ports. An examples of a specification is: 11:1; 1:3-5; 2:0,3; 4-7,9:4-7,9; 10: Semicolons separate expressions. Within each expression, the colon has a left hand side and a right hand side. Bridge ports on the left hand side can send packets to bridge ports on the right hand side. Commas separate items in a list of bridge ports. Hyphens are short-hand for specifying a range of numbers. If there is no right hand side, the bridge ports on the left cannot send packets to any bridge port (unless the matrix is combined with some some other matrix in a filter specification, or unless the filter is overridden). Bridge port numbers are specified in decimal. A matrix will read back in a form equivalent to the form written. It may not read back exactly as written. No single matrix defines whether a packet arriving on a port is forwarded to its destination. Various destination address, source address, protocol, and default filtering specifications are combined to determine whether the packet is forwarded. If the ebrNportMatrixValue is changed, all filters using it are immediately updated.

Assigning the value invalid will result in an error while the matrix is still reference by some filter. All matrices are permanent; it is their usage which may or may not be temporary. Enumeration: 'permanent': 2, 'invalid': 1.

A matrix is expressed using a shorthand that says what input ports can talk to what output ports. An examples of a specification is: 1.1,2.1-14.2:1.1-14.2; 2.2:5.3,6.4; 10.3:; Semicolons separate expressions. Within each expression, the colon has a left hand side and a right hand side. Front panel ports on the left hand side can send packets to front panel ports on the right hand side. Commas separate items in a list of front panel ports. Hyphens are short-hand for specifying a range of numbers. If there is no right hand side, the front panel ports on the left cannot send packets to any front panel port (unless the matrix is combined with some some other matrix in a filter specification, or unless the filter is overridden). Front panel port numbers are of the form (slot.connector), where slot is the slot number the module is plugged into, and connector is the connector number specified on the front of the card. A matrix will read back in a form equivalent to the form written. It may not read back exactly as written. No single matrix defines whether a packet arriving on a port is forwarded to its destination. Various destination address, source address, protocol, and default filtering specifications are combined to determine whether the packet is forwarded. If the ebrNportMatrixFppnValue is changed, all filters using it are immediately updated. Managers may not specify both ebrNportMatrixValue and ebrNportMatrixFppnValue at the same time to set an entry in this table.

The filters specified by SAP protocol.

A portion of a particular filter for a particular SAP protocol.

This name for a portion of a filter is whatever the user likes, as long as it is a unique ebrNportSapName. The combination of ebrNportSapNameSap and ebrNportSapMatrixName is unique within this table. Insertions of new names for pre-existing combinations will be denied. ebrNportSapName is present and is the index to give a mnemonic handle on the combination of SAP and matrix for purposes of discussion and of access through the network management station user interface. SAPs, for example, are often just meaningless numbers unless laborious steps are taken to interpret them.

The one-byte SAP. Changes to ebrNportSapProtoTable for this SAP are denied while filtering of the SAP is specified by reference to a named matrix using this table.

A ebrNportMatrixName. Multiple matrices for the same SAP are combined using an elementwise-OR operator.

filter(1) : The filtering for this SAP is specified by the filter matrix. alwaysFilter(2) : Frames of this SAP (protocol) are filtered regardless of any other alwaysForward dispositions based on the frame's address. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames for this SAP (protocol) are sent to ports specified in the filter matrix regardless of any address filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. Setting this object will cause a side effect on the ebrNportSapFilterCharacteristicsTable entry for this SAP. It is here to group information for window-based forms. Setting this object will also cause a side effect on other entries in this table with the same SAP value. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

This object specifies the permanence of the associated filter matrix, and also provides a means to delete a filter matrix. Writing invalid(1) to the object removes the filter. Writing permanent(2) value to the object indicates the filter is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The filters specified by Protocol ID for the SNAP SAP.

A portion of a particular filter for a particular Protocol ID.

This name for a portion of a filter is whatever the user likes, as long as it is a unique ebrNportSnapName. The combination of ebrNportSnapNameSnap and ebrNportSnapMatrixName is unique within this table. Insertions of new names for pre-existing combinations will be denied. ebrNportSnapName is present and is the index to give a mnemonic handle on the combination of protocol and matrix for purposes of discussion and of access through the network management station user interface. Protocol IDs, for example, are often just meaningless numbers unless laborious steps are taken to interpret them.

The five-byte PID. Changes to ebrNportSnapProtoTable for this protocol are denied while filtering of the protocol is specified by reference to a named matrix using this table.

A ebrNportMatrixName. Multiple matrices for the same PID are combined using an elementwise-OR operator.

filter(1) : The filtering for this Protocol ID is specified by the filter matrix. alwaysFilter(2) : Frames of this Protocol ID are filtered regardless of any other alwaysForward dispositions based on the frame's address. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames for this Protocol ID are sent to ports specified in the filter matrix regardless of any address filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. Setting this object will cause a side effect on the ebrNportSnapFilterCharacteristicsTable entry for this protocol. It is here to group information for window-based forms. Setting this object will also cause a side effect onother entries in this table with the same protocol value. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

This object specifies the permanence of the associated filter matrix, and also provides a means to delete a filter matrix. Writing invalid(1) to the object removes the filter. Writing permanent(2) value to the object indicates the filter is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The filters specified by destination address.

A portion of a particular filter for a particular destination address.

This name for a portion of a filter is whatever the user likes, as long as it is a unique ebrNportDAName. The combination of ebrNportDANameDA and ebrNportDAMatrixName is unique within this table. Insertions of new names for pre-existing combinations will be denied. ebrNportDAName is present and is the index to give a mnemonic handle on the combination of address and matrix for purposes of discussion and of access through the network management station user interface. Addresses, for example, are often just meaningless numbers unless laborious steps are taken to interpret them.

The six-byte destination address. Changes to ebrNportStaticDATable for this address are denied while filtering of the address is specified by reference to a named matrix using this table.

A ebrNportMatrixName. Multiple matrices for the same address are combined using an elementwise-OR operator.

filter(1) : The filtering for this address is specified by the filter matrix. alwaysFilter(2) : Frames destined to address are filtered regardless of any other alwaysForward dispositions based on the frame's source address or protocol type. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames destined to address are always forwarded to ebrNportPortNum if specified. The filter matrix is used to specify ports to which frames may be sent. In both cases, this disposition overrides filters based on the frame's source address or protocol type, unless either of those filters has an alwaysFilter disposition. Setting this object will side effect the ebrNportStaticDAFilterCharacteristicsTable entry for this address. It is here to group information for window-based forms. Setting this object will also cause a side effect on other entries in this table with the same address. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

The filters specified by source address.

A portion of a particular filter for a particular source address.

This name for a portion of a filter is whatever the user likes, as long as it is a unique ebrNportSAName. The combination of ebrNportSANameSA and ebrNportSAMatrixName is unique within this table. Insertions of new names for pre-existing combinations will be denied. ebrNportSAName is present and is the index to give a mnemonic handle on the combination of address and matrix for purposes of discussion and of access through the network management station user interface. Addresses, for example, are often just meaningless numbers unless laborious steps are taken to interpret them.

The six-byte source address. Changes to ebrNportStaticSATable for this address are denied while filtering of the address is specified by reference to a named matrix using this table.

A ebrNportMatrixName. Multiple matrices for the same address are combined using an elementwise-OR operator.

This object specifies how to interpret the ebrNportPortNum and the ebrNportSAMatrixName objects. portMask(1) : The static filtering for this address is specified by the filter matrix. alwaysFilter(2) : Frames sourced from this address are filtered regardless of any other alwaysForward dispositions based on the frame's destination address or protocol type. The static filtering information is specified by the filter matrix. alwaysForward(3) : Frames sourced from this address are sent to ports specified in the filter matrix regardless of any DA or protocol filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. lockdown (4) : Frames sourced from this address are ONLY forwarded if received on the same port as ebrNportPortNum. lockdownportmask (5) : Frames sourced from this address are ONLY forwarded if received on the same port as ebrNportPortNum AND if the frame is destined to a permitted port as specified by the filter matrix. filter(6) : The static filtering for this address is specified by the filter matrix. portMask(1) is the different name with the same effect. Setting this object will side effect the ebrNportStaticSAFilterCharacteristicsTable entry for this address. It is here to group information for window-based forms. Setting this object will also cause a side effect on other entries in this table with the same address. Enumeration: 'lockdownportmask': 5, 'alwaysFilter': 2, 'filter': 6, 'lockdown': 4, 'alwaysForward': 3, 'portMask': 1.

other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

A matrix is expressed using a shorthand that says what input ports can talk to what output ports. An examples of a specification is: 11:1; 1:3-5; 2:0,3; 4-7,9:4-7,9; 10: Semicolons separate expressions. Within each expression, the colon has a left hand side and a right hand side. Bridge ports on the left hand side can send packets to bridge ports on the right hand side. Commas separate items in a list of bridge ports. Hyphens are short-hand for specifying a range of numbers. If there is no right hand side, the bridge ports on the left cannot send packets to any bridge port (unless the matrix is combined with some some other matrix in a filter specification, or unless the filter is overridden). Bridge port numbers are specified in decimal. A matrix will read back in a form equivalent to the form written. It may not read back exactly as written. No single matrix defines whether a packet arriving on a port is forwarded to its destination. Various destination address, source address, protocol, and default filtering specifications are combined to determine whether the packet is forwarded. Unspecified rows are set to one's, which means that the corresponding input ports can communicate with every output port.

The list of bridge ports in manual mode is listed. Manual mode means that the bridge purges the learned entries for that port from its forwarding database, stops its learning process on that port, and forwards to that port only frames with destination and source addresses that have been specified via management. A comma-separated list of bridge ports, with hyphens used to abbreviate ranges, is supported. The bridge port numbers are in decimal.

This table is another view of ebrNportMatrixNameTable. Changes to this table cause changes to ebrNportMatrixNameTable. Users or programs can choose whichever matrix specification language they feel more comfortable with. This table also side-steps issues of the worst-case ascii representation length on the part of either ebrNportMatrixNameTable or the management station interface.

A particular row of a particular named filter matrix.

This name for a filter matrix is whatever the user likes, as long as it is a unique filter matrix name. Same as ebrNportMatrixName.

A bridge port number. Zero is treated as in other tables, and is short-hand for all rows not previously mentioned.

Just like all the other GoTos. The set of ports to which frames received from a specific port are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. If the ebrNportMatrixAllowedToGoTo is changed, all filters using it are immediately updated.

Assigning the value invalid will delete the row of the matrix. Attempting to delete the last ebrNportmatrixName entry for a matrix will result in an error while the matrix is still reference by some filter. All matrices are permanent; it is their usage which may or may not be temporary. Enumeration: 'permanent': 2, 'invalid': 1.

A matrix is expressed using a shorthand that says what input front panel ports can talk to what output front panel ports. An examples of a specification is: 1.1,2.1-14.2:1.1-14.2; 2.2:5.3,6.4; 10.3:; Semicolons separate expressions. Within each expression, the colon has a left hand side and a right hand side. Front panel ports on the left hand side can send packets to front panel ports on the right hand side. Commas separate items in a list of front panel ports. Hyphens are short-hand for specifying a range of numbers. If there is no right hand side, the front panel ports on the left cannot send packets to any front panel port (unless the matrix is combined with some some other matrix in a filter specification, or unless the filter is overridden). Front panel port numbers are of the form (slot.connector), where slot is the slot number the module is plugged into, and connector is the connector number specified on the front of the card. A matrix will read back in a form equivalent to the form written. It may not read back exactly as written. No single matrix defines whether a packet arriving on a port is forwarded to its destination. Various destination address, source address, protocol, and default filtering specifications are combined to determine whether the packet is forwarded. Unspecified rows are set to one's, which means that the corresponding input ports can communicate with every output port.

The list of front panel ports in manual mode is listed. Manual mode means that the bridge purges the learned entries for that port from its forwarding database, stops its learning process on that port, and forwards to that port only frames with destination and source addresses that have been specified via management. A comma-separated list of front panel ports, with hyphens used to abbreviate ranges, is supported. Front panel port numbers are of the form (slot.connector), where slot is the slot number the module is plugged into, and connector is the connector number specified on the front of the card.

This table is yet another view of ebrNportMatrixNameTable. Changes to this table cause changes to ebrNportMatrixNameTable. Users or programs can choose whichever matrix specification language they feel more comfortable with. This table also side-steps issues of the worst-case ascii representation length on the part of either ebrNportMatrixNameTable or the management station interface.

A particular row of a particular named filter matrix.

This name for a filter matrix is whatever the user likes, as long as it is a unique filter matrix name. Same as ebrNportMatrixName.

Front panel port numbers are of the form (slot.connector), where slot is the slot number the module is plugged into, and connector is the connector number specified on the front of the card. To avoid the syntactic ambiguity, the slot number must take two characters. For example, front panel port number 3.1 must be typed by 03.1. 0.0 is treated as in other tables, and is short-hand for all rows not previously mentioned.

Just like all the other GoTos. The set of ports to which frames received from a specific port are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. If the ebrNportMatrixFppnAllowedToGoTo is changed, all filters using it are immediately updated.

Assigning the value invalid will delete the row of the matrix. Attempting to delete the last ebrNportmatrixname entry for a matrix will result in an error while the matrix is still reference by some filter. All matrices are permanent; it is their usage which may or may not be temporary. Enumeration: 'permanent': 2, 'invalid': 1.

When a matrix name is written to this object, the default matrix is set to the matrix if and only if the matrix exists. Unspecified rows in the matrix are set to one's, which means that the corresponding input ports can communicate with every output port.

This table is another view of ebrNportDefaultMatrixValue.

A particular row of the default matrix.

A bridge port number.

The set of ports to which frames received from a specific port are allowed to be forwarded by default. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

A flood matrix is expressed using a shorthand that says what input ports can be flooded to what output ports. Unspecified rows are set to one's, which means that the corresponding input ports can be flooded to every output port.

A flood matrix is expressed using a shorthand that says what input front panel ports can be flooded to what output front panel ports. Unspecified rows are set to one's, which means that the corresponding input ports can be flooded to every output port.

When a matrix name is written to this object, the flood matrix is set to the matrix if and only if the matrix exists. Unspecified rows in the matrix are set to one's, which means that the corresponding input ports can be flooded to every output port.

This table is another view of ebrNportFloodMatrixValue.

A particular row of the flood matrix.

A bridge port number.

The set of ports to which frames received from a specific port are allowed to be flooded by default.

A table that contains filtering information about 802.2 SAPs in the DSAP field for N-port bridges.

A table that contains filtering information about 802.2 SAPs in the DSAP field for N-port bridges.

The 802.2 DSAP in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrNportSapAllowedToGoTo. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.

The set of ports to which frames received from a specific port and containing the DSAP in an 802 frame specified by ebrNportSapValue are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. Filter matrix rows can be initialized or overwritten, but not deleted. Only whole matrices are deleted via the characteristics table. To produce the equivalent of row deletion, set the GoTo according to the following table: Disp GoTo filter/portMask 0xFFFFFFFFF0 alwaysFilter 0xFFFFFFFFF0 alwaysForward 0

A table that contains information about how 802.2 DSAP filters are used within N-port bridges.

802.2 DSAP filter usage for N-port bridges.

The 802.2 DSAP in a frame to which this entry's information applies. The value of this object is the same as ebrNportSapValue.

This object specifies how to interpret the ebrNportSapAllowedToGoTo values for the specified SAP. filter(1) : The filtering for this SAP is specified by the filter matrix. alwaysFilter(2) : Frames of this SAP (protocol) are filtered regardless of any other alwaysForward dispositions based on the frame's address. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames for this SAP (protocol) are sent to ports specified in the filter matrix regardless of any address filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

This object specifies the permanence of the associated filter matrix, and also provides a means to delete a filter matrix. Writing invalid(1) to the object removes the filter. Writing permanent(2) value to the object indicates the filter is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

A table that contains filtering information about 5-byte SNAP Protocol IDs (PIDs) for N-port bridges.

A table that contains filtering information about 5-byte SNAP Protocol IDs (PIDs) for N-port bridges.

The SNAP Protocol ID (PID) in an 802 frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrNportSnapAllowedToGoTo. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.

The set of ports to which frames received from a specific port and containing the SNAP PID in an 802 frame specified by ebrNportSnapValue are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. Filter matrix rows can be initialized or overwritten, but not deleted. Only whole matrices are deleted via the characteristics table. To produce the equivalent of row deletion, set the GoTo according to the following table: Disp GoTo filter/portMask 0xFFFFFFFFF0 alwaysFilter 0xFFFFFFFFF0 alwaysForward 0

A table that contains information about how SNAP Protocol ID (PID) filters are used within N-port bridges.

802.2 SNAP Protocol ID (PID) filter usage for N-port bridges.

The SNAP Protocol ID (PID) in a frame to which this entry's information applies. The value of this object is the same as ebrNportSnapValue.

This object specifies how to interpret the ebrNportSnapAllowedToGoTo values for the specified SNAP PID. filter(1) : The filtering for this Protocol ID is specified by the filter matrix. alwaysFilter(2) : Frames of this Protocol ID are filtered regardless of any other alwaysForward dispositions based on the frame's address. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames for this Protocol ID are sent to ports specified in the filter matrix regardless of any address filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

This object specifies the permanence of the associated filter matrix, and also provides a means to delete a filter matrix. Writing invalid(1) to the object removes the filter. Writing permanent(2) value to the object indicates the filter is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

This table contains management-specified destination address filtering information about unicast and multicast addresses for N-port bridges. In RFC 1286 lingo, static objects are those objects which have been specified by network management.

Information about a specific MAC address for which the bridge has some management-specified forwarding and/or filtering information.

The destination MAC Address in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrNportDAAllowedToGoTo field. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.

The set of ports to which frames received from a specific port and destined to the address specified by ebrNportDAAddress are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. Filter matrix rows can be initialized or overwritten, but not deleted. Only whole matrices are deleted via the characteristics table. To produce the equivalent of row deletion, set the GoTo according to the following table: Disp GoTo filter/portMask 0xFFFFFFFFF0 alwaysFilter 0xFFFFFFFFF0 alwaysForward 0

A table that contains information about how static destination address filters (for unicast and multicast addresses) are used within N-port bridges. Static objects are those objects which have been specified by network management.

Information about a specific static MAC destination address filter's usage within N-port bridges.

The destination MAC Address in a frame to which this entry's information applies. The value of this object is the same as ebrNportDAAddress.

This object specifies how to interpret the ebrNportPortNum and ebrNportDAAllowedToGoTo objects. filter(1) : The filtering for this address is specified by the filter matrix. alwaysFilter(2) : Frames destined to address are filtered regardless of any other alwaysForward dispositions based on the frame's source address or protocol type. The filtering information is specified by the filter matrix. alwaysForward(3) : Frames destined to address are always forwarded to ebrNportPortNum if specified. The filter matrix is used to specify ports to which frames may be sent. In both cases, this disposition overrides filters based on the frame's source address or protocol type, unless either of those filters has an alwaysFilter disposition. Enumeration: 'filter': 1, 'alwaysFilter': 2, 'alwaysForward': 3.

other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

A table that contains static source address filtering information about unicast and multicast addresses for N-port bridges. Static objects are those objects which have been specified by network management.

Information about a specific MAC address for which the bridge has some static forwarding and/or filtering information.

The source MAC Address in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrNportSAAllowedToGoTo field. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.

The set of ports to which frames received from a specific port and sourced from the address specified by ebrNportSAAddress are allowed to be forwarded. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. Filter matrix rows can be initialized or overwritten, but not deleted. Only whole matrices are deleted via the characteristics table. To produce the equivalent of row deletion, set the GoTo according to the following table: Disp GoTo filter/portMask 0xFFFFFFFFF0 alwaysFilter 0xFFFFFFFFF0 alwaysForward 0

A table that contains information about how static source address filters (for unicast and multicast addresses) are used within N-port bridges.

Static source address filter usage for N-port bridges.

The source MAC Address in a frame to which this entry's information applies. The value of this object is the same as ebrNportSAAddress.

This object specifies how to interpret the ebrNportPortNum and and the ebrNportSAAllowedToGoTo objects. portMask(1) : The static filtering for this address is specified by the filter matrix. alwaysFilter(2) : Frames sourced from this address are filtered regardless of any other alwaysForward dispositions based on the frame's destination address or protocol type. The static filtering information is specified by the filter matrix. alwaysForward(3) : Frames sourced from this address are sent to ports specified in the filter matrix regardless of any DA or protocol filter with a disposition of filter. The alwaysForward disposition also overrides a forwarding disposition of filter in the default filter matrix object. Filters with a disposition of alwaysFilter are never superceded. lockdown (4) : Frames sourced from this address are ONLY forwarded if received on the same port as ebrNportPortNum. lockdownportmask (5) : Frames sourced from this address are ONLY forwarded if received on the same port as ebrNportPortNum AND if the frame is destined to a permitted port as specified by the filter matrix. filter(6) : The static filtering for this address is specified by the filter matrix. portMask(1) is the different name with the same effect. Enumeration: 'lockdownportmask': 5, 'alwaysFilter': 2, 'filter': 6, 'lockdown': 4, 'alwaysForward': 3, 'portMask': 1.

other(1) - This entry is currently in use, but the conditions under which it will remain so are different from each of the following values. Like other uses of 'other' in MIBs, this value may not be assigned to the object. invalid(2) - Writing this value to the object removes the entry permanent(3) - Writing this value to the object indicates that the entry is preserved across a bridge reset. deleteOnReset(4) - Writing this value removes the permanent entry characteristic. The entry is deleted upon the next bridge reset (SCP or GIGAswitch failure). Writing deleteOnReset is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. deleteOnTimeout(5) - Writing this value removes the permanent entry characteristic. Since the timers used for aging information within the bridge are hidden from the user, the change may in fact take place immediately. Writing deleteOnTimeout is not supported. SNMP does not currently model viewing the non-volatile and volatile data structures independently, which can lead to unexpectedly having no filter if a reset occurs while temporarily trying a change to an existing filter. Writes of this value will result in a bad value return status. It is present for consistency with the Bridge MIB (RFC 1286), which describes address filters. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

This table describes the default filter matrix.

The entry describes a row of the default filter matrix.

The bridge port on which a frame must be received to use the corresponding ebrNportSwAllowedToGoTo field. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other management-specified entry.

This object specifies the default forwarding disposition after all DA, SA, and protocol filters have been applied. For those cases where no filter applies to the frame, the forwarding disposition for the frames received on the ebrNportSwReceivePort interface and sent to one or all of the bridge's interfaces is determined by the ebrNportSwAllowedToGoTo object. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

A switch that controls address filtering. Specifying a one in a bit position says that the port is in manual mode. Each octet of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'. Manual mode means that the bridge purges the learned entries for that port from its forwarding database, stops its learning process on that port, and forwards to that port only frames with destination and source addresses that have been specified via management.

A table that contains static (i.e., configured by network management) information about the bridge port on which unicast or multicast addresses reside on N-port bridges.

Information about a specific MAC address.

The MAC Address to which this entry's information applies.

The Port Number to which this address will be translated (to which frames destined for the address will be forwarded). There are some filtering nuances for addresses with specified port numbers which are determined by the source address and destination address filter disposition characteristics. If zero, no port number is specified. This value is a giganet destination address instead of a bridge port number if it is greater than 127.

This object specifies the permanence of the specified information, and also provides a means to delete an entry. Writing invalid(1) to the object removes the entry. Writing permanent(2) value to the object indicates the entry is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The Front Panel Port Number to which this address will be translated (to which frames destined for the address will be forwarded). There are some filtering nuances for addresses with specified front panel port numbers which are determined by the source address and destination address filter disposition characteristics. Managers may not specify both ebrNportPortNum and ebrNportFppnPortNum at the same time to set an entry in this table.

A table that contains resource information (e.g., queuing) about 802.2 SAPs in the DSAP field for N-port bridges.

Resource information about an 802.2 SAP in the DSAP field for N-port bridges.

The 802.2 DSAP in a frame to which this entry's resource information applies.

The service class used to allocate resources and implement service policy within the bridge. The service class associated with a frame is a function of either the frame's destination address or the frame's protocol. The default value for this field is 0. This value is used to assign the single path service class in the absence of an overriding service class associated with the frame's destination addr. There are 16 possible service classes, 0-15. Service classes 1-11 are reserved for internal or future use.

This object specifies the permanence of the specified service class usage, and also provides a means to delete an entry. Writing invalid(1) to the object removes the entry. Writing permanent(2) value to the object indicates the entry is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The ebrNportSapSinglePath object is used to set the single path ports for a ebrNportSapSvcSapValue. The default is to not use the default (single path) service class. ebrNportSapSinglePath is expressed using a shorthand that specifies which physical ports are to be set to the default (single path) service class. An example of a specification would be : (1,6-9,21) where commas separate physical ports and hyphens are short-hand for specifying a range of numbers. This example would assign physical ports 1,6,7,8,9, and 21 to use the default (single path) service class, for the given ebrNportSapSvcSapValue. Physical port numbers are specified in decimal. A ebrNportSapSinglePath will read back in a form equivalent to the form written. It may not read back exactly as written.

A table that contains resource information (e.g., queuing) about 5-byte SNAP Protocol IDs (PIDs) for N-port bridges.

Resource information about a 5-byte SNAP Protocol ID (PID) for N-port bridges.

The SNAP Protocol ID (PID) in a frame to which this entry's resource information applies.

The service class used to allocate resources and implement service policy within the bridge. The service class associated with a frame is a function of either the frame's destination address or the frame's protocol. The default value for this field is 0. This value is used to assign the single path service class in the absence of an overriding service class associated with the frame's destination addr. There are 16 possible service classes, 0-15. Service classes 1-11 are reserved for internal or future use.

This object specifies the permanence of the specified service class usage, and also provides a means to delete an entry. Writing invalid(1) to the object removes the entry. Writing permanent(2) value to the object indicates the entry is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The ebrNportSnapSinglePath object is used to set the single path ports for a ebrNportSnapSvcSnapValue. The default is to not use the default (single path) service class. ebrNportSnapSinglePath is expressed using a shorthand that specifies which physical ports are to be set to the default (single path) service class. An example of a specification would be : (1,6-9,21) where commas separate physical ports and hyphens are short-hand for specifying a range of numbers. This example would assign physical ports 1,6,7,8,9, and 21 to use the default (single path) service class, for the given ebrNportSnapSvcSnapValue. Physical port numbers are specified in decimal. A ebrNportSnapSinglePath will read back in a form equivalent to the form written. It may not read back exactly as written.

A table that contains resource information about unicast and multicast destination addresses for N-port bridges.

Resource information about a specific MAC destination address for N-port bridges.

The destination MAC Address in a frame to which this entry's resource information applies.

The service class used to allocate resources and implement service policy within the bridge. The service class associated with a frame is a function of either the frame's destination address or the frame's protocol. The default value for this field is 0. This value is used to assign the single path service class in the absence of a service class associated with the frame's protocol. There are 16 possible service classes, 0-15. The ebrNportSvc allows 32 values to be specified. The specification of a value greater than 15 is used to connote that the service class (ebrNportSvc-16), is to be associated with the frame and that this service class has precedence over a service class associated with a frame's protocol. Service classes 1-11 are reserved for internal or future use.

This object specifies the permanence of the specified service class usage, and also provides a means to delete an entry. Writing invalid(1) to the object removes the entry. Writing permanent(2) value to the object indicates the entry is preserved across a bridge reset. Enumeration: 'permanent': 2, 'invalid': 1.

The maximum bytes-per-second bandwidth of packets multicast because the destination address was not yet learned by the bridge. The resolution of this value is 100 bytes-per-second. The 2 LS digits are rounded down to zero, i.e. 1-99 => 0.

The maximum bytes-per-second bandwidth of packets multicast because the destination address is a multicast address.The resolution of this value is 100 bytes-per-second. The 2 LS digits are rounded down to zero, i.e. 1-99 => 0.

Detailed view of the bridge flooding process.

Flooding state for a packet class and source.

The quota qualifier describes an incoming or outgoing port. It is a linear index to the port starting from 1. If n is the quota qualifier for the first port of a two port line card, the quota qualifier for the second port is n + 1. The clock card and the crossbar have zero port, so the index must be skipped over those slots. This numbering scheme may be changed as we have four port line cards.

The quota class describes the type of packet. Four packet types are classified as follows: 1 - Unknown Destination Packets, 2 - Multicast Packets, 3 - IS-IS Packets, 4 - Bursty Control Packets

This object is the count of bytes in flooded packets. It does not include filtered packets or packets discarded due to buffer limitations. Each packet is counted once, regardless of the number of outbound links to which it was flooded.

This object is the count of flooded packets. It does not include filtered packets or packets discarded due to buffer limitations. Each packet is counted once, regardless of the number of outbound links to which it was flooded.

This object is the count of packets that could not be flooded because they had remained in the SCP or in the inbound linecard too long.

This object is the count of packets discarded by the SCP flooding software (at the interrupt level) due to insufficient buffering.

This object is the count of packets for which buffer quota conversion to flooding software optimistic quotas failed. This includes packets that were discarded as well as packets that were successfully flooded.

This object is the count of packets discarded to prevent packet misordering. Certain protocol types are considered single-path and may not be delivered out of order. If the Destination Address for a packet having a single-path protocol type is learned while the packet is buffered by the flooding software, the packet must be discarded (since line cards would have been directly forwarding packets using the learned address while packets received earlier were buffered on the SCP).

This object is the count of packets discarded by the flooding software because user-configured filtering resulted in no allowed outbound transmit ports.

This object is the count of packets discarded due to the incoming link leaving FORWARDING state while they were buffered by flooding software.

This object is the byte count in packets discarded due to the incoming link leaving FORWARDING state while they were buffered by flooding software.

This object is the count of multicast packets addressed to software modules in the SCP that have been successfully delivered to those modules.

This object is the count of multicast packets addressed to software modules in the SCP that, because of buffer limitations, could not be delivered to those modules.

This table controls the enabling of some hardware performance enhancements that avoid store-and-forward delays during packet forwarding, whenever possible.

Information about the enabling of some hardware performance enhancements that avoid store-and-forward delays for a specific bridge port.

The dot1dBasePort bridge port number for this table entry.

If true, some hardware performance enhancements are enabled to avoid store-and-forward delays when packets enter the GIGAswitch. If false, the whole packet is buffered on the line card at which the packet enters the GIGAswitch before it is sent to the line card at which the packet leaves the GIGAswitch. Cut-through is normally enabled. Enumeration: 'false': 2, 'true': 1.

If true, some hardware performance enhancements are enabled to avoid store-and-forward delays when packets leave the GIGAswitch. If false, the whole packet is buffered on the line card at which the packet leaves the GIGAswitch before it is sent out of the GIGAswitch. Cut-through is normally enabled. Enumeration: 'false': 2, 'true': 1.

This table controls the enabling of some hardware performance enhancements that avoid store-and-forward delays during packet forwarding, whenever possible.

Information about the enabling of some hardware performance enhancements that avoid store-and-forward delays for a specific front panel port.

The front panel port number for this table entry. Front panel port numbers are of the form (slot.connector), where slot is the slot number the module is plugged into, and connector is the connector number specified on the front of the card.

If true, some hardware performance enhancements are enabled to avoid store-and-forward delays when packets enter the GIGAswitch. If false, the whole packet is buffered on the line card at which the packet enters the GIGAswitch before it is sent to the line card at which the packet leaves the GIGAswitch. Cut-through is normally enabled. Enumeration: 'false': 2, 'true': 1.

If true, some hardware performance enhancements are enabled to avoid store-and-forward delays when packets leave the GIGAswitch. If false, the whole packet is buffered on the line card at which the packet leaves the GIGAswitch before it is sent out of the GIGAswitch. Cut-through is normally enabled. Enumeration: 'false': 2, 'true': 1.

A list of gigaStp entries

A collection of objects containing information for a given StpPort

The value of the interface associated with this spanning tree port.

When true, this interface will be enabled to operate as part of the spanning tree. When trueNoDelay, this interface will be enabled to operate as part of the spanning tree but will have a pre-forwarding delay of zero. Enumeration: 'false': 2, 'true': 1, 'trueNoDelay': 3.

If true, then when a source address is learned, the address is only written to the Translation Table in the bridge port on which it was learned. If the address later occurs as a destination address in a packet received on some other bridge port, the packet is flooded if possible and the address is written to the Translation table of the other bridge port at that time. Thus, a bridge port that receives no packets for a certain address will not have that address in its database unless the address had been learned on that bridge port. If false, then when a source address is learned, the address is promptly written to the Translation Table of every bridge port in the GIGASwitch. This variable should be set to yes if the total number of learned addresses is expected to be greater than the number supported by the linecards and if there is sufficient locality of traffic that the behavior described above will not result in more than that number of addresses being learned on any one bridge port. It should be set to no if the total number of learned addresses is not greater than the number supported by the linecards and if it is desired to avoid flooding of packets to already-learned addresses. Enumeration: 'false': 2, 'true': 1.

The number of entries in the tables used to store learned network addresses.

This object shows the number of unknown DA unicast packets which are transmitted from linecards to the SCP for multicasting, but discarded due to the lack of buffer space in the XAC chip. Packets counted here are not included in other, per-port, discard counters because this counter is shared by all the incoming ports.

This object shows the number of multicast packets which are transmitted from linecards to the SCP for processing, but discarded due to the lack of buffer space in the XAC chip. Packets counted here are not included in other, per-port, discard counters because this counter is shared by all the incoming ports.

This object shows the number of IP packets which are transmitted from linecards to the SCP for forwarding, but discarded due to the lack of buffer space in the XAC chip. Packets counted here are not included in other, per-port, discard counters because this counter is shared by all the incoming ports.

The communityStringDelimiter object is used to delimit community string suffixes. Community string suffixes give the SNMP agent additional information to process certain objects. If the objects do not need the suffix then the suffix is ignored. If the object uses the suffix and none is supplied, then a default is used. There are two valid suffixes available for the Gigaswitch/Fddi, LDx and LBDx. LDx references learning domains, LD1-LD8. LBDx references logical bridge domains, LBD1- LBD8. Both uppercase and lowercase are valid. The default communityStringDelimiter is the ':'. ex. public:LD3, use learning domain 4 if required public:LBD4, use logical bridge domain 4 if required public, use default if required. The set of Valid communityStringDelimiter is the set of all printable characters minus all the alphas and all the digits. If a LDx suffix is used where an LBDx is required, then the LBD that contains the LDx will be used. If a LBDx suffix is used where an LDx is required, then the lowest numbered LD in that LBD is used. In both cases if there are no members in the LD/LBD then the default is used. The default LD is LD1 and the default LBD is LBD1.

This object is the IP address of the host storing the file containing the software image. The object may not be set until the last requested transfer succeeds or fails. So, before setting this object the user should verify that transferStatus does not have the value 'requested' or 'inProgress'.

This object is the 802 48-bit address of the host storing the file containing the software image. The object may not be set until the last requested transfer succeeds or fails. So, before setting this object, the user should verify that transferStatus does not have the value 'requested' or 'inProgress'. Both version 3 and version 4 of MOP are supported. If a unicast address is specified, the transfer will be from that host. If the MOP multicast address ab-00-00-01-00-00 is used, the transfer will be from the first MOP server to respond, as usual.

This object is the name of the file containing the software image. The object may not be set until the last requested transfer succeeds or fails. Before setting this object, the user should verify that transferStatus does not have the value 'requested' or 'inProgress'. Further, this object may not be set until the last requested copy succeeds or fails. Before setting this object, the user should verify that copyStatus does not have the value 'requested' or 'inProgress'.

To initiate a transfer of a file from a server to the SCP, set this object. If transferFileName is non-empty, and mopDestination is non-zero, setting this object to doMOP(2) will cause a MOP 'load' to be attempted. If transferFileName is non-empty, and tftpDestination is non-zero, setting this object to doTFTP(3) will cause a TFTP 'Get' to be attempted. This object may not be set until the last requested transfer succeeds or fails, and the last requested copy succeeds or fails. So, before setting this object the user should verify that transferStatus does not have the values 'requested' or 'inProgress', and that copyStatus does not have the values 'requested' or 'inProgress'. Enumeration: 'none': 1, 'doTFTP': 3, 'doMOP': 2.

This variable can be polled to determine when the transfer has completed. Polling for completion allows other SNMP requests to be processed while the transfer is in progress (the SNMP is single-threaded). Enumeration: 'requested': 2, 'none': 1, 'success': 5, 'failed': 4, 'failedDueToCheckSum': 6, 'inProgress': 3.

Size in bytes of the transfered file. This object can be polled along with the transferStatus object to monitor the progress of the transfer.

The slot number of the card which is to be upgraded. The object may not be set until the last requested copy succeeds or fails.

The type of the image. The object is set after a transfer succeeds or fails. Enumeration: 'none': 1, 'clock': 4, 'fgl4': 7, 'fgl2': 3, 'agl-2': 6, 'agl-2-plus': 8, 'powerSystemController': 5, 'scp': 2.

To initiate a software upgrade of a card, set this object. If copyToSlot is non-zero, and copyType has a value other than 'none', and transferStatus has the value 'success', a software upgrade of the card is attempted. The handler double-checks that the slot requires software of the expected type, and provides demultiplexing when multiple images may be sent to the same slot. The power system controller is updated by sending its image to the clock card slot. The object may not be set until the last requested transfer succeeds, and the last requested copy succeeds or fails. Reading this object always returns the value none(1). Enumeration: 'doUpgrade': 2, 'none': 1.

This variable can be polled to determine when the card upgrade has completed. Polling for completion allows other SNMP requests to be processed while the copy is in progress (the SNMP is single-threaded). Enumeration: 'requested': 2, 'none': 1, 'success': 5, 'failedDueToHwRev': 7, 'failed': 4, 'failedDueToFwRev': 8, 'failedDueToBadImage': 9, 'inProgress': 3, 'failedDueToCardType': 6.

When read, this object indicates whether the result of a file transfer is still present. The value exists indicates that the transferred file is present; the value notExist indicates that no file has been transferred or that it has been deleted. Writing the value exists is an error. Writing the value notExist deletes the transferred file. The object may not be set until the last requested transfer succeeds or fails. It may not be set while a copy is in progress, either. Enumeration: 'notExist': 2, 'exists': 1.

The maximum amount of time an IP to LAN address translation will be used if it cannot be re-verified.

The time, in seconds, between ARP requests that are used to verify or to discover an IP to LAN address translation.

The number of times ARP requests are used to verify or to discover an IP to LAN address translation.

If duplicated snmp messages arrive within this interval, all but the first one will be discarded. The unit is a hundredth of second.

When true, the GIGAswitch will service broadcast ARP requests from its ARP cache. When false, Broadcast ARP frames are flooded. Enumeration: 'false': 2, 'true': 1.

This table stores ARP counters.

Information about the ARP statistical table is stored.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

Unicast ARP requests received on this port.

Broadcast ARP requests received on this port.

ARP replies transmitted on this port.

ARP frames received on this port that required flooding while acting as an ARP agent.

ARP frames received on this port that were discarded due to protocol errors.

If true then switched IP filtering is enabled. If false switched IP filtering is disabled. Enumeration: 'false': 2, 'true': 1.

This table allows the user to assign an address range to logical bridge ports so that all traffic destined to addresses within that range will go out those ports.

An entry that stores information about a switched IP filtering range.

An index for the ipSwitchPortsTable. This is the start address of the range of addresses for which the the ipStaticPorts and ipDynamicPorts are valid.

An index for the ipSwitchPortsTable. This is the end address of the range of addresses for which the the ipStaticPorts and ipDynamicPorts are valid.

The IP address associated with the range, ipRangeStartAddr and ipRangeEndAddr.

ipStaticPorts is the set of logical ports that packets will exit the Gigaswitch when the destination address is within the range specified by ipRangeStartAddr and ipRangeEndAddr. ipStaticPorts is expressed using a shorthand that specifies which logical ports are assigned to the address range. An example of a specification would be (1,6-9,21), where commas separate logical ports and hyphens are short-hand for specifying a range of numbers. This example would assign logical ports 1,6,7,8,9, and 21 to the specified address/mask. Logical port numbers are specified in decimal. The ipStaticPorts will read back in a form equivalent to the form written. It may not read back exactly as written.

ipDynamicPorts is the set of logical ports, learned dynamically, that packets will exit the Gigaswitch when the destination address is within the range specified by ipRangeStartAddr and ipRangeEndAddr.

ipPrimaryPorts is the set of all logical ports, set by management, that packets will exit the Gigaswitch regardless of the range to which they are addressed to. The ipPrimaryPorts is expressed using a shorthand that specifies the logical ports. An example of a specification would be (1,6-9,21) where commas separate logical ports and hyphens are short-hand for specifying a range of numbers. This example would assign logical ports 1,6,7,8,9, and 21 to the specified address/mask. Logical port numbers are specified in decimal. The ipPrimaryPorts will read back in a form equivalent to the form written. It may not read back exactly as written.

ipPrimaryPorts is the set of all logical ports, learned dynamically, that packets will exit the Gigaswitch regardless of the range to which they are addressed to.

ipSwitchDynamicEnabledPorts is the set of bridge ports over which the GIGAswitch sends and receives information about configured IP address ranges. The syntax used to specify it is the same as for ipPrimaryPorts.

The table for storing the port group membership.

An entry stores information about a single port group.

The port group port number. It is unique within this table and must be between 37 and 64. Without management settings, the port group has no members in it.

This object displays the current state of the port group membership. Managers specify a new port group membership using portGroupMembershipWorkBuf. The new membership becomes effective and remains unchanged after a system crash when portGroupAction is set to doUpdate and the updating process succeeds.

Managers can update a new port group membership as many times as they want using this object. Setting this object to a new value does not change the current membership and the value will be resetted after a system crash. The new value is copied to portGroupMembership when portGroupAction is set to doUpdate and the updating process successfully changes the port member. A port group is expressed using a shorthand that says what bridge ports are members of the group. An examples of a specification is: (1,3,5) (32-36) (6,12-24,36) () A list of bridge ports between 1 and 36 are used to represent the members of the port group. A bridge port becoming a member of a port group ceases to operate as a normal bridge port, therefore filters on the port have no effect. If a port group is specified as an empty set, the members in the group will operate as normal bridge ports and take their original brige port numbers. Their original filters will also become effective. Commas separate items in a list of bridge ports. Hyphens are short-hand for specifying a range of numbers. Bridge port numbers are specified in decimal. A port group will read back in a form equivalent to the form written. It may not read back exactly as written. If the manager specifies a member that is overlapped with a member of a preexisting port group in the same object, setting portGroupAction to doUpdate will fail.

This object displays the current state of the port group port type. Managers specify a new port group port type using portGroupPortTypeWorkBuf. The new port type becomes effective and remains unchanged after a system crash when portGroupAction is set to doUpdate and the updating process succeeds. Enumeration: 'reliabilityGroup': 2, 'huntGroup': 1.

Managers can update a new port group port type as many times as they want using this object. Setting this object to a new value does not change the current port type and the value will be resetted after a system crash. The new value is copied to portGroupPortType when portGroupAction is set to doUpdate and the updating process successfully changes the port type. Two port group types are supported: 1) the hunt group and 2) the reliability group. All members in the hunt group port work like a single bridge port as far as the bridge functions are concerned and yet provides higher bandwidth due to multiple parallel FDDI links. A state of a port in a reliability group is either operational or backup. Only a single port in the group may be operational, while the other ports in the group are backup. When the operational port fails, one backup mode port will be selected, and quickly become operational. Enumeration: 'reliabilityGroup': 2, 'huntGroup': 1.

This object indicates the operational status of the port group. The status represents the aggregated effect of each member's status. uninitializedPort(1) state indicates one of the followings: 1) the port group has no member in it, 2) no port in the port group is powered on, 3) no port in the port group has successfully completed startup diagnostics. State preBridging(2) means that some ports in the port group have been initialized with the bridge functions, but no port is not yet functioning as part of a bridge port. This is always the case if the datalink is not up. A hunt group member remains in this state if the remote end of the link is not properly configured as part of the hunt group. An inactive member of a reliability group is also in this state if it is up and initialized. State bridging(3) means that at least one port in the port group is functioning as part of a bridge port. The port group must be in this state to carry user data. Enumeration: 'uninitializedPort': 1, 'bridging': 3, 'preBridging': 2.

The table for storing the port group membership specified by FPPN numbers.

An entry stores information about a single port group.

The port group port number. It is unique within this table and must be between 99.37 and 99.64. Without management settings, the port group has no members in it.

This object displays the current state of the port group membership. Managers specify a new port group membership using portGroupFppnMembershipWorkBuf. The new membership becomes effective and remains unchanged after a system crash when portGroupAction is set to doUpdate and the updating process succeeds.

Managers can update a new port group membership as many times as they want using this object. Setting this object to a new value does not change the current membership and the value will be resetted after a system crash. The new value is copied to portGroupFppnMembership when portGroupAction is set to doUpdate and the updating process successfully changes the port member. A port group is expressed using a shorthand that says what FPPN ports are members of the group. An examples of a specification is: (1.1,3.2,5.1) (13.1-14.2) (4.1,11.1-13.2,14.2) () A list of FPPN ports between 1.1 and 14.2 are used to represent the members of the port group. A port becoming a member of a port group ceases to operate as a normal bridge port, therefore filters on the port have no effect. If a port group is specified as an empty set, the members in the group will operate as normal bridge ports and take their original FPPN port numbers. Their original filters will also become effective. Commas separate items in a list of FPPN ports. Hyphens are short-hand for specifying a range of numbers. FPPN port numbers are of the form (slot.port) where slot is the slot number and port is the port number in the slot. A port group will read back in a form equivalent to the form written. It may not read back exactly as written. If the manager specifies a member that is overlapped with a member of a preexisting port group in the same object, setting portGroupAction to doUpdate will fail.

This object displays the current state of the port group port type. Managers specify a new port group port type using portGroupPortTypeWorkBuf. The new port type becomes effective and remains unchanged after a system crash when portGroupAction is set to doUpdate and the updating process succeeds. Enumeration: 'reliabilityGroup': 2, 'huntGroup': 1.

Managers can update a new port group port type as many times as they want using this object. Setting this object to a new value does not change the current port type and the value will be resetted after a system crash. The new value is copied to portGroupPortType when portGroupAction is set to doUpdate and the updating process successfully changes the port type. Two port group types are supported: 1) the hunt group and 2) the reliability group. All members in the hunt group port work like a single bridge port as far as the bridge functions are concerned and yet provides higher bandwidth due to multiple parallel FDDI links. A state of a port in a reliability group is either operational or backup. Only a single port in the group may be operational, while the other ports in the group are backup. When the operational port fails, one backup mode port will be selected, and quickly become operational. Enumeration: 'reliabilityGroup': 2, 'huntGroup': 1.

This object indicates the operational status of the port group. The status represents the aggregated effect of each member's status. uninitializedPort(1) state indicates one of the followings: 1) the port group has no member in it, 2) no port in the port group is powered on, 3) no port in the port group has successfully completed startup diagnostics. State preBridging(2) means that some ports in the port group have been initialized with the bridge functions, but no port is not yet functioning as part of a bridge port. This is always the case if the datalink is not up. A hunt group member remains in this state if the remote end of the link is not properly configured as part of the hunt group. An inactive member of a reliability group is also in this state if it is up and initialized. State bridging(3) means that at least one port in the port group is functioning as part of a bridge port. The port group must be in this state to carry user data. Enumeration: 'uninitializedPort': 1, 'bridging': 3, 'preBridging': 2.

The table for storing the port status.

An entry stores the port status.

The bridge port number runs from 1 to _LASTPHYSPORT_.

If the indexed port is a member of a port group, the port group number is returned. Otherwise, the index itself is returned.

This object represents the port type. Enumeration: 'singleton': 1, 'huntGroupMember': 2, 'reliabilityGroupMember': 3.

This object indicates the operational status of the indexed port. uninitializedPort(1) state indicates one of the followings: 1) the port is nonexistent, 2) the port is in a slot that is not powered on, 3) the port has not successfully completed startup diagnostics. Ports in portInitializing(2) state are in the process of being initialized. It is a temporary state. State preBridging(3) means that the port has been initialized with the bridge functions, but is not functioning as part of a bridge port. This is always the case if the datalink is not up. A hunt group member remains in this state if the remote end of the link is not properly configured as part of the hunt group. An inactive member of a reliability group is also in this state if it is up and initialized. State bridging(4) means that the port is functioning as part of a bridge port. Ports must be in this state to carry user data. Enumeration: 'uninitializedPort': 1, 'bridging': 4, 'preBridging': 3, 'portInitializing': 2.

This table allows learning domains to be created, modified, and deleted. There can be from 1 to 8 learning domains. A learning domain is a collection of port groups (or bridge ports) which share a learning database. Every bridge port is a member of precisely one learning domain. A MAC address that is seen on one port of the learning domain will be taught to the other ports in the learning domain, but not to ports in other learning domains, unless a target learning domain has been set up. Among other things, this allows for the possbility that a single MAC address may be learned on several different ports - as long as they are in separate learning domains. There are a maximum of 8 learning domains, including the default learning domain. The default learning domain is the set of all bridge ports that do not belong to a management defined learning domain.

A group of objects, indexed by learningDomainNumber, that specify learning domain attributes.

The index for a learning domain is an integer with range, 1-8, where 1 is the default learning domain.

This object displays the current state of the learning domain membership. Managers specify a new learning domain membership using learningDomainMembershipWorkBuf. The new membership becomes effective and remains unchanged, across system reboots, when portGroupAction is set to doUpdate and the updating process succeeds.

The learningDomainMembershipWorkBuf object is used to create,modify, and delete learning domains. Managers can update a learning domain membership as many times as they want using this object. Setting this object to a new value does not change the current membership nor the values stored in non-volatile memory until the object portGroupAction is written with doUpdate. At that time the new values will be written to learningDomainMembership and non-volatile memory and the learning domain changes will take effect. The addition/removal of bridge ports to/from a learning domain is an atomic operation. Because a bridge port can only belong to one learning domain, the last assignment of a bridge port to a learning domain will determine the learning domain in which the bridge port resides. There is a default learning domain, designated by learningDomainNumber 1, which all bridge ports belong to until management changes the assignments of bridge ports to learning domains. If a bridge port is removed from a learning domain, it is placed back into the default learning domain. The default learning domain can not be modified directly. It changes when new learning domains are created or modified. Every learning domain is a member of precisely one logical bridge. The learningDomainMembership is expressed using a shorthand that specifies which bridge ports belong in the learning domain. An example of a specification would be : (1,6-9,21) where commas separate bridge ports and hyphens are short-hand for specifying a range of numbers. This example would assign bridge ports 1,6,7,8,9, and 21 to the specified learning domain. Bridge port numbers are specified in decimal. A learning domain will read back in a form equivalent to the form written. It may not read back exactly as written.

This table allows port target domains lists to be created, modified, and deleted. The port target domain list is the set of all mgmt defined learning domains to which a bridge port, as specified by the index, will learn addresses from. A MAC address that is seen in one of the learning domains in the port target domain list will be learned by the indexed bridge port. Every port target domain is a member of precisely one logical bridge.

A group of objects, indexed by portTargetDomainListIndex, that specify port target domain attributes.

A bridge port number from 1 - 64 .

The portTargetDomainListMembership specifies a set of mgmt specified learning domains. This object displays the current state of the port target domain list membership. Managers specify a new port target domain membership, or modify an existing one using portTargetDomainListMembershipWorkBuf. The new membership becomes effective and remains unchanged, across system reboots, when portGroupAction is set to doUpdate and the updating process succeeds.

The portTargetDomainListMembership object is used to create, modify, and delete port target domain lists. Managers can update a port target domain membership list as many times as they want using this object. Setting this object to a new value does not change the current membership nor the values stored in mgmt memory until the object portGroupAction is written with doUpdate. At that time the new values will be written to portTargetDomainListMembership and mgmt memory and the target domain changes will take effect. The portTargetDomainListMembership specifies the target domains that a learning domain belongs to. This set of learning domains is called the port target domain list. The portTargetDomainListMembership is expressed using a shorthand that specifies which learning domains belong in the port target domain list. An example of a specification would be : (2-4,6,8) where commas separate learning domains and hyphens are short-hand for specifying a range of numbers.. This example would map the learning domain to the port target domain list consisting of learning_domains 2, 3, 4, 6, and 8. Valid values for learning domains are 1-8. A port target domain list will read back in a form equivalent to the form written. It may not read back exactly as written.

The table for storing the logical bridge domain membership.

An entry stores information about a logical bridge domain.

The logical bridge domain number. It is unique within this table and must be between 1 and 8.

This object displays the learning domain numbers which are members of the indexed logical bridge domain in the current box configuration.

Managers can specify logical bridge domains as many times as needed without effecting the current box configuration using this object. Setting this object to a new value is stored in a local buffer and the changes are not recorded in the nonvolatile memory. The new value is copied into lBDomainMembership and becomes effective when portGroupAction is set to doUpdate and the updating process successfully upgrades the logical bridge domains. A logical bridge domain is expressed using a shorthand that says what learning domains are members of it. An examples of a specification is: (1,3,5) (2-4) Commas separate items in a list of learning domains. Hyphens are short-hand for specifying a range of numbers. Learning domain numbers are specified in decimal. A logical bridge domain will read back in a form equivalent to the form written. It may not read back exactly as written. Without a management set, the default logical bridge domain (i.e., domain number 1) contains all learning domains. The other logical bridge domains are empty sets. A logical bridge domain is created by specifying what learning domains are members of it. Specified learning domains are deleted from the old logical bridge domain and added to the new logical bridge domain. Deletion and addition of the learning domains are atomic across the SNMP messages. Learning domains left out in the specification will automatically join the default logical bridge domain. Reconfiguring logical bridge domains is an expensive operation. Therefore the manager should not change the configuration very often.

To initiate a configuration upgrade of a box, set this object. The tables updated with this set operation are: portGroupMembershipTable, learningDomainMembershipTable, portTargetDomainListMembershipTable, lBDomainMembershipTable The handler checks the consistency of the manager's configuraton of the box specified in the tables' working buffer. If no configuraton error is detected, the box starts the reconfiguration process and the working buffers are copied into their corresponding variables. The changes will survive after a system crash. Reading this object always returns the value none(1). Enumeration: 'doUpdate': 2, 'none': 1.

This object shows the result of the most recent setting of portGroupAction to doUpdate(2). Enumeration: 'success': 1, 'failedDueToPGSpec': 3, 'failedDueToLDSpec': 4, 'failedDueToLBDSpec': 6, 'failedDueToOthers': 2, 'failedDueToTLDSpec': 5.

This table allows the user to add and delete physical ports to traffic groups. There can be from 1 to 16 traffic groups. A traffic group is a collection of physical ports that is used to allow single path traffic coming in on physical ports to be transmitted out a single management assigned member port of a hunt group. This is used to restrict single path traffic from being multipathed in a hunt group. Every physical port must belong to one of 16 traffic groups. Traffic group 1 is the default traffic group. All ports that do not belong to traffic groups 2-16 belong to the default traffic group.

An entry that stores information about a traffic group.

The index for the traffic group membership is a traffic group number. Traffic group numbers are in the range 1-16. Traffic group 1 is the default traffic group.

The trafficGroupMembership object allows the user to add and delete physical ports from traffic groups. Because a physical port can only belong to one traffic group, the last assignment of a physical port to a traffic group will determine the traffic group in which the physical port is a member. There is a default traffic group which physical ports belong to until management changes the assignments of physical ports to traffic groups. If a physical port is removed from a traffic group, it is placed back into the default traffic group. The default traffic group can not be modified directly. It changes when new traffic groups are added or removed from other traffic groups. The default traffic group is traffic group 1. The trafficGroupMembership is expressed using a shorthand that specifies which physical ports belong in the traffic group. An example of a specification would be : (1,6-9,21) where commas separate physical ports and hyphens are short- hand for specifying a range of numbers. This example would assign physical ports 1,6,7,8,9, and 21 to the specified traffic group. Physical port numbers are specified in decimal. A traffic group will read back in a form equivalent to the form written. It may not read back exactly as written.

This table allows traffic group attributes to be set.

An entry that stores traffic group attributes.

One of two indexes into the trafficGroupAttributeTable. It is within the range 1-16.

Second of two indexes into the trafficGroupAttributeTable. This is the hunt group that all ports in the traffic group are assigned to and is in the range 37-64.

The trafficGroupHgMember is a number in the range 1-16 that maps to a member of the hunt group specified by trafficGroupHgNumber. trafficGroupHgMember 1 maps to the lowest numbered member of the hunt group, trafficGroupHgMember 2 maps to the second lowest numbered member of the hunt group, etc. If the trafficGroupHgMember is greater then the number of members in the hunt group, then it wraps. For example : Given that traffic groups 1,2,3,4,5 all have physical ports. hunt group 37 = {3,6,8} For hunt group 37 : traffic group 1 set to member number 1 traffic group 2 set to member number 2 traffic group 3 set to member number 3 traffic group 4 set to member number 4 traffic group 5 set to member number 5 then trafficGroupHgMember 1 maps to port 3 trafficGroupHgMember 2 maps to port 6 trafficGroupHgMember 3 maps to port 8 trafficGroupHgMember 4 maps to port 3 trafficGroupHgMember 5 maps to port 6

The trafficGroupCatagory is defined as follows : fixed ----- fixed means that traffic is to stay on the same port until the port fails. For this value, the member number is ignored completely. The first physical port that comes up in the hunt group will be assigned the traffic. If the port fails the lowest numbered remaining member of the hunt group will be assigned the traffic. If the traffic category is fixed, sequential delivery of packets is almost guaranteed. reconfig -------- reconfig means that the traffic group may be moved from one hunt group member to another whenever any port joins or leaves the hunt group. If possible, the traffic group must use the hunt group member whose trafficGroupHgMember is configured. If the traffic category is reconfig, sequential delivery of packets is guaranteed, except when members enter or leave the hunt group. Enumeration: 'reconfig': 2, 'fixed': 1.

Each logical bridge domain (LBD) has a learning quota. This table allows the setting of theses quotas.

A group of objects, indexed by learningQuotaNumber, that specify learning quotas.

The index for a learning quota is a learning domain with range, 1 - 8.

Each learning domain has a learning quota. The ports in the domain are guaranteed the ability to use approximately this number of address entries in the Translation Table, so that an excessive number of learned addresses in one domain cannot interfere significantly with learning in another domain. The GIGAswitch keeps track of the count of addresses learned in each domain and deletes addresses from the domains that have most exceeded their learning quotas to make room for addresses learned in other domains. If these quotas are configured so that they add up to less than the size of the SCP Translation Table, there are almost always SCP Translation Table entries available to accommodate new learned addresses. Further, these addresses will not be deleted to make room for others unless the domain's quota is reached or is close to being reached. If the SCP Translation Table is not full, the quotas are allowed to be exceeded. Under such circumstances, the count of learned addresses in a logical bridge may grow until it is close to the number of unused entries in the Translation Table plus the applicable learning quota. The learning quotas are not exact, and addresses may start to be deleted when this limit is within a small number of addresses (initially 100) of being reached. It should be remembered that there are factors other than the learning quotas that may restrict the number of addresses that can be learned, so that a high learning quota does not guarantee that number of addresses may be learned. In particular: 1) If the capacity of the linecard Translation Tables is exceeded, no more addresses may be learned on that linecard. 2) If the sum of the configured learning quotas is greater than the SCP Translation Table size, then no more addresses may be learned once the SCP Translation Table is full, even though no quota may have been exceeded. When either of these situations occur, an attempt is made to solve the problem by deleting addresses in the same manner as when dealing with the learning quota limits. The default value for each learning quota is 32768, the same as the capacity of the SCP Translation Table. This large value means that the quotas have no effect. To see the full benefit of learning quotas, they should be set so that the sum of the quotas over all active domains is less than 32500.

Exercise abort undo code in SNMP commit processing

This table contains miscellaneous objects for configuring Fast Ethernet interfaces.

Data for a particular Fast Ethernet interface. This table may be optionally implemented in such a way as to allow pre-configuration of hardware which has not yet been installed.

When true, packets with a data unit of size <= 1500 bytes are sent and received. When false, packets with a data unit of size <= 1535 bytes are sent and received. Enumeration: 'false': 2, 'true': 1.

When true(1), ICMP redirect message processing is disabled for the specified port. Enumeration: 'false': 2, 'true': 1.

When true(1), transmit errors are sent to the ICMP FIFO. Enumeration: 'false': 2, 'true': 1.

When true(1), receive errors are sent to the ICMP FIFO. Enumeration: 'false': 2, 'true': 1.

When true(1), enables Appletalk ARP II support. Enumeration: 'false': 2, 'true': 1.

When true(1), enables raw IPX support. Enumeration: 'false': 2, 'true': 1.

This table contains the AGL specific interface configuration parameters, one entry per ATM interface port.

This list contains ATM interface configuration parameters and state variables.

The value of this object identifies the AGL port interface for which this entry contains management information.

Indicates the type of physical interface used on the ATM port. Two physical layer types are supported: 1. STS3c/STM1 2. DS3/E3 The type is unknown if the port is not present or its physical layer type is not known. Enumeration: 'sts3cStm1': 1, 'unKnown': 3, 'ds3e3': 2.

Indicates the granularity in cell/s for assigning peak, average and minimum guaranteed rates for traffic shaped circuits on the AGL port. This value also represents the minimum rate in cells/s that can be assigned to a circuit. The rates subscribed to in the aglVCConnectionTable will be set to a multiple of this rate.

This table contains the AGL specific interface configuration parameters for the SONET/SDH physical layer.

This list contains SONET/SDH interface configuration parameters and state variables.

The value of this object identifies the AGL port interface for which this entry contains management information and is the same as aglInterfaceIndex.

Specifies whether the PHY operates in SONET STS-3c or SDH STM-1 mode. The following code points are used: 1 SONET STS-3c 2 SDH STM-1 Enumeration: 'sonetSTS3c': 1, 'sdhSTM1': 2.

Specifies whether the PHY operates in loop-timing or local-timing mode. In loop-timing, the recovered clock from the receive signal is used directly to time transmit data. Hence, the PHY is synchronized to the far-end transmitter. In local timing, transmit data is timed from a local oscillator of frequency 155.52 MHz (20ppm). The following code points are used: 1 loop-timing 2 local-timing Enumeration: 'loopTiming': 1, 'localTiming': 2.

This table contains the AGL specific interface configuration parameters for the DS3/E3 physical layer.

This list contains DS3/E3 interface configuration parameters and state variables.

The value of this object identifies the AGL port interface for which this entry contains management information and is the same as aglInterfaceIndex.

Specifies whether the DS3/E3 PHY operates in low power mode for short distances or high power mode for longer distances. The following code points are used: 1 low-power 2 high-power Enumeration: 'low-power': 1, 'high-power': 2.

Specifies whether ATM cells may be mapped into the DS3 PLCP. In the enabled mode, PLCP framing and timing is applied to each ATM cell. Enumeration: 'enable': 1, 'disable': 2.

This table contains AGL ATM VCC configuration and performance parameters and state variables. Each entry represents a bidirectional traffic flow.

A bidirectional circuit.

The value of this object identifies the AGL ATM port A of the VCC segment for FDDI-bridged and ATM-to-ATM circuit types.

The VPI value at port A for the bidirectional circuit. The maximum VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at AGL ATM port A. This value is used for both transmit and receive VPIs

The VCI value at the port A for the bidirectional circuit. The VCI values from 0 to 31 are reserved. The maximum VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits specified for the AGL ATM port A. This value is used for both transmit and receive VCIs

The value of this object identifies the AGL ATM port B of the VCC segment for ATM-to-ATM circuit types. For FDDI-bridged circuit types this value should be zero.

The VPI value at port B for the bidirectional ATM-to-ATM circuit. The maximum VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at AGL ATM port B. This value is used for both transmit and receive VPIs. For other circuit types this value should be zero.

The VCI value at the port B for the bidirectional ATM-to-ATM circuit. The VCI values from 0 to 31 are reserved. The maximum VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits specified for the AGL ATM port B. This value is used for both transmit and receive VCIs. For other circuit types this value should be zero.

The status column used for creating, and deleting bidirectional circuit entries in the agl virtual channel connection table. Enumeration: 'create': 1, 'delete': 2.

The value of this object identifies the circuit type and characteristics of a particular circuit. There are two types of connections supported: 1. FDDI-bridged 2. ATM-to-ATM An FDDI-bridged circuit carries all bridged FDDI traffic on AGL ATM port A. No information is required to be entered for Port B. Only one bridged FDDI circuit per AGL ATM port is supported. The packet format on this circuit is VC based multiplexed bridged FDDI as per RFC 1483. An ATM-to-ATM circuit carries arbitrary packet types between circuits specified on Port A and Port B of the GIGAswitch. Multiple ATM-to-ATM circuits are supported per AGL ATM port. Enumeration: 'fddi-bridged': 1, 'atm-to-atm': 2.

The value of this object identifies the AAL type that should be used on a particular circuit. Enumeration: 'aal34': 1, 'aal5': 2.

This object indicates the operational status of the VCC, i.e., whether the managed VCC segment is up or down. In the down state, no cells can get across this VCC segment. The status is unknown if the OAM is disabled. Enumeration: 'down': 2, 'unknown': 3, 'up': 1.

This object indicates the desired status of the VCC, i.e., whether the managed VCC segment is enabled or disabled. In the disabled state, no cells can be passed across this VCC segment. Enumeration: 'enable': 1, 'disable': 2.

The value of this object specifies the peak rate in cells/s that should be used on a particular circuit. The peak rate will be set to a multiple of the aglInterfaceTrafficRateGranularity close to the user specified input.

The value of this object specifies the average (sustained) rate in cells/s that should be used on a particular circuit. The average rate must be less than or equal to the peak rate and it will be set to a multiple of the aglInterfaceTrafficRate- Granularity close to the user specified input.

The value of this object specifies the minimum guaranteed rate in cells/s that should be used on a particular circuit. For VBR traffic AGL allows the possibility of overbooking link bandwidth (up to 1200%) to achive statistical multiplexing. This parameter specifies the minimum peak bandwidth that you want to guarantee to the circuit. The minimum guaranteed rate must be less than or equal to the peak rate and it will be set to a multiple of the aglInterfaceTrafficRateGranularity close to the user specified input.

The value of this object specifies the priority which should be given to this circuit in assigning opportunistic bandwidth that arises from AGL's bandwidth overbooking policy.

This table contains AGL ATM interface specific settable parameters.

The list of settable parameters.

The value of this object identifies the AGL port interface for which this entry contains management information and is the same as aglInterfaceIndex.

This object indicates the desired status of the cell scramble module. In the enabled state, outgoing cells are scrambed and input cells are descrambled. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the desired status of the OAM module in the default circuit. In the enabled state, normal OAM cells are exchanged between the peers. Enumeration: 'enable': 1, 'disable': 2.

This identifies the no ATM traffic enforcement type.

This identifies the ATM traffic enforcement type is 1. For type 1 traffic enforcement, parameter 1 specifies CLP=0+1 peak traffic. Parameters 2, 3, 4 and 5 are not used. The peak rate is measured in cells per second.

This identifies the ATM traffic enforcement type is 2. For type 2 traffic enforcement, parameter 1 specifies CLP=0 peak traffic and parameter 2 specifies CLP=0+1 peak traffic. Parameters 3, 4, and 5 are not used. The peak rate is measured in cells per second.

This identifies the ATM traffic enforcement type is 3. For type 3 traffic enforcement, parameter 1 specifies CLP=0+1 peak traffic, parameter 2 specifies CLP=0 sustained rate, and parameter 3 specifies CLP=0 maximum burst size. Parameters 4 and 5 are not used. The peak rate is measured in cells per second. The sustained rate is measured in cells per second and burst size is measured in cells.

This identifies the ATM traffic enforcement type is 4. For type 4 traffic enforcement, parameter 1 specifies CLP=0 peak traffic, parameter 2 specifies CLP=0+1 peak traffic, and parameter 3 specifies tagging (e.g., a value 1 may be used to indicate tagging). Parameters 4 and 5 are not used. The peak rate is measured in cells per second.

This identifies the ATM traffic enforcement type is 5. For type 5 traffic enforcement, parameter 1 specifies CLP=0+1 peak traffic, parameter 2 specifies CLP=0 sustained rate, parameter 3 specifies CLP=0 maximum burst size, and parameter 4 specifies tagging (e.g., a value 1 may be used to indicate tagging). Parameter 5 is not used.

This identifies the ATM traffic enforcement type is 6. For type 6 traffic enforcement, parameter 1 specifies CLP=0+1 peak traffic, parameter 2 specifies CLP=0+1 sustained rate, and parameter 3 specifies CLP=0+1 maximum burst size. Parameters 4 and 5 are not used.

This identifies the ATM traffic enforcement type is 7. For type 7 traffic enforcement, parameter 1 specifies CLP=0+1 peak traffic and parameter 2 specifies best effort traffic (e.g., a value 1 may be used to indicate best effort traffic). Parameters 3, 4 and 5 are not used.

This table contains ATM local interface configuration parameters and state variables, one entry per ATM interface port.

This list contains ATM interface configuration parameters and state variables.

The value of this object identifies the ATM port interface for which this entry contains management information.

The maximum number of VPCs supported at this ATM interface.

The maximum number of VCCs supported at the ATM interface.

The number of VPCs configured for use at this ATM interface.

The number of VCCs configured for use at the ATM interface.

The maximum number of active VPI bits configured for use at the ATM interface.

The maximum number of active VCI bits configured for use at this ATM interface.

The decimal value of the three octet VPI/VCI field that identifies the VCC supporting the ILMI at the ATM interface. If the value of this object is greater than 16777215 then the ILMI is not supported at the ATM interface. The default VPI/VCI values for ILMI are VPI=0 and VCI=16.

This object points to the additional information specific to ATM interfaces. For example, if Enterprise specific objects have been defined in addition to this MIB module, then the value of this object refers to that MIB defining these objects. If the additional information is not present, then the value should be {0 0}.

This table contains ATM interface DS3 PLCP parameters and state variables, one entry per ATM interface port.

This list contains DS3 PLCP parameters and state variables at the ATM interface.

The value of this object identifies the ATM interface port for which this entry contains management information and is the same as the atmInterfaceIndex.

A DS3 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF event.

This variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. Enumeration: 'incomingLOF': 3, 'noAlarm': 1, 'receivedFarEndAlarm': 2.

The counter associated with the number of Unavailable Seconds encountered by the PLCP.

This table contains ATM interface SONET TC Sublayer parameters and state variables, one entry per ATM interface port.

This list contains SONET TC Sublayer parameters and state variables at the ATM interface.

The value of this object identifies the ATM interface port for which this entry contains management information and is the same as the atmInterfaceIndex.

The number of times the Out of Cell Delineation (OCD) events occur. If seven consecutive ATM cells have Header Error Control (HEC) violations, an OCD event occurs. A high number of OCD events may indicate a problem with the SONET TC Sublayer.

This variable indicates if there is an alarm present for the SONET TC Sublayer. The value lcdFailure indicates that a Loss of Cell Delineation (LCD) failure state has been declared for the SONET TC Sublayer. Enumeration: 'lcdFailure': 2, 'noAlarm': 1.

The SONET/SDH Medium table.

An entry in the SONET/SDH Medium table.

An index value that uniquely identifies a SONET/SDH Medium/Section/Line Interface.

This variable identifies whether a SONET or a SDH signal is used across this interface. Enumeration: 'sonet': 1, 'sdh': 2.

The number of seconds, including partial seconds, that have elapsed since the beginning of the current error-measurement period.

The number of previous intervals for which valid data has been stored. A SONET device must support at least n intervals. The minimum value of n is 4. The default of n is 32. The maximum value of n is 96. The value of this object will be n unless the device was brought online within the last (nx15) minutes, in which case the value will be the number of complete 15 minute intervals the device has been online.

This variable describes the line coding for this interface. The B3ZS and CMI are used for electrical SONET/SDH signals (STS-1 and STS-3). The Non-Return to Zero (NRZ) and the Return to Zero are used for optical SONET/SDH signals. Enumeration: 'sonetMediumB3ZS': 2, 'sonetMediumNRZ': 4, 'sonetMediumRZ': 5, 'sonetMediumOther': 1, 'sonetMediumCMI': 3.

This variable describes the line type for this interface. The line types are Short and Long Range Single Mode fiber or Multi-Mode fiber interfaces, and coax and UTP for electrical interfaces. The value sonetOther should be used when the Line Type is not one of the listed values. Enumeration: 'sonetShortSingleMode': 2, 'sonetMultiMode': 4, 'sonetOther': 1, 'sonetCoax': 5, 'sonetUTP': 6, 'sonetLongSingleMode': 3.

This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.

The SONET/SDH Section Current table.

An entry in the SONET/SDH Section Current table.

The index value which uniquely identifies the SONET/SDH Medium/Section/Line Interface.

This variable indicates the status of the interface. The sonetSectionStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetSectionNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetSectionNoDefect 2 sonetSectionLOS 4 sonetSectionLOF

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in the current 15 minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section in the current 15 minute interval.

The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Section in the current 15 minute interval.

The SONET/SDH Line Current table.

An entry in the SONET/SDH Line Current table.

The index value which uniquely identifies the SONET/SDH Medium/Line Interface.

This variable indicates the status of the interface. The sonetLineStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetLineNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetLineNoDefect 2 sonetLineAIS 4 sonetLineRDI

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The SONET/SDH Path Current table.

An entry in the SONET/SDH Path Current table.

An index value that uniquely identifies a SONET/SDH Path Interface.

A value that indicates the type of the SONET/SDH Path. For SONET, the assigned types are the STS-Nc SPEs, where N = 1, 3, 12, 24, and 48. STS-1 is equal to 51.84 Mbps. For SDH, the assigned types are the STM-Nc VCs, where N = 1, 4, and 16. Enumeration: 'sts3cSTM1': 2, 'sts1': 1, 'sts12cSTM4': 3, 'sts48cSTM16': 5, 'sts24c': 4.

This variable indicates the status of the interface. The sonetPathStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetPathNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetPathNoDefect 2 sonetPathSTSLOP 4 sonetPathSTSAIS 8 sonetPathSTSRDI 16 sonetPathUnequipped 32 sonetPathSignalLabelMismatch

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Unavailable Seconds encountered by a Path in the current 15 minute, interval.

A list of SMT entries. The number of entries is given by smtNumber, defined in the FDDI MIB.

A collection of objects containing information for a given SMT link.

Identifies the SMT Index. The value of this object is the same as the snmpFddiSMTIndex, defined in the FDDI MIB, for this smt entity.

The Station Type Identification. Enumeration: 'sas': 1, 'sac': 3, 'das': 5, 'nac': 4, 'dac': 2.

The number of PC Traces received by this station.

A list of MAC entries. The number of entries is given by macNumber, defined in the FDDI MIB.

A collection of objects containing information for a given MAC entity.

The value of the SMT index associated with this MAC. The value of this object is the same as the snmpFddiMACSMTIndex, defined in the FDDI MIB, for this MAC entity.

Identifies the MAC Index. The value of this object is the same as the snmpFddiMACIndex, defined in the FDDI MIB, for this MAC entity.

The SMT Resource Index.

The current state of the link. Enumeration: 'broken': 6, 'offFaultRecovery': 3, 'onRingRun': 5, 'offReady': 2, 'onRingInit': 4, 'offMaint': 1.

The current Ring Purger state. Enumeration: 'purger': 4, 'purgerOff': 1, 'candidate': 2, 'nonPurger': 3.

If true, this Link will participate in the Ring Purger Election and, if elected, perform the Ring Purger function. Enumeration: 'false': 2, 'true': 1.

The number of times the MAC PurgeError Event bit was set.

Method of frame removal used by this station. Enumeration: 'bridgeStrip': 2, 'saMatch': 1.

The number of times a Frame Content Independent Strip operation was terminated by receipt of a token.

Reason for last ring disturbance. Enumeration: 'noReason': 1, 'directedBeaconReceived': 14, 'pcTraceReceived': 16, 'daDetected': 9, 'ringInitReceived': 7, 'ringBeaconingInitiated': 8, 'ringPurgeError': 11, 'ringInitInitiated': 6, 'ringOpOscillation': 13, 'bridgeStripError': 12, 'duplicateTokenDetected': 10, 'pcTraceInitiated': 15.

Number of Ring Claim Processes initiated by this link entity.

Number of Ring Claim Processes or Ring Beaconing Processes initiated by a remote link entity and detected by this link entity.

The number of Ring Beacon Processes initiated by this link entity.

The number of times the duplicate address test failed.

The number of times this link entity detected a duplicate token.

The upstream neighbor's duplicate address status, as reported by the NIF frame. Unknown if no NIF frame has been received yet. Enumeration: 'false': 2, 'true': 1, 'unknown': 3.

The number of PC Traces initiated by this station.

The restricted token timeout, which limits how long a single restricted mode dialog may last before being terminated.

The number of frames received on the line that had the E (error detected) indicator set or a missing E indicator.

The number of frames received on the line that contained an odd number of symbols; that is, a non-integral number of octets.

The number of times an underrun occured because the device's transmit FIFO became empty due to insufficient memory. In other words, the device was trying to transmit but could not get into memory fast enough.

A list of PORT entries. The number of entries is given by portNumber, defined in the FDDI MIB.

A collection of objects containing information for a given PORT entity.

The value of the SMT index associated with this port. The value of this object is the same as the snmpFddiPORTSMTIndex, defined in the FDDI MIB, for this PORT entity.

Identifies the PORT Index. The value of this object is the same as the snmpFddiPORTIndex, defined in the FDDI MIB, for this PORT entity.

The SMT Resource index. Index of the PHY resource used to identify the PHY PORT in ANSI SMT frames.

The physical media type of the PORT. Enumeration: 'pmdTHN': 5, 'pmdUTP': 7, 'pmdSTP': 6, 'pmdNone': 1, 'pmdMM': 2, 'pmdSM': 3, 'pmdLC': 4.

The PHY state. Enumeration: 'failed': 6, 'inuse': 8, 'watch': 7, 'broken': 2, 'offready': 3, 'starting': 5, 'offmaintenance': 1, 'wait': 4.

The current reject reason. Enumeration: 'noReason': 1, 'tracesReceived': 10, 'tneExpired': 7, 'remoteReject': 8, 'topologyRules': 6, 'lctLocal': 2, 'standby': 11, 'lemFailure': 5, 'lctProtocol': 12, 'lctRemote': 3, 'tracesInProgress': 9, 'lctBoth': 4.

The number of Physical Connections established for this PHY PORT.

The number of times a physical disconnection took place because the TNE Noise Timer expired.

The number of ELM Chip EBUFF_ERROR events.

A list of FDX entries.

A collection of objects containing information for a given FDX MAC entity.

The value of the SMT index associated with this FDX MAC.

The value of the MAC index associated with this FDX MAC.

When true, this link will participate in the full duplex auto-configuration and, if this is successful, will operate in the full duplex mode. Enumeration: 'false': 2, 'true': 1.

When true, this link is operating in the full duplex mode. Enumeration: 'false': 2, 'true': 1.

The state of the full duplex Control process. Enumeration: 'fdxConfirm': 3, 'fdxRequest': 2, 'fdxOperation': 4, 'fdxIdle': 1.

The version number of the software stored in ROM.

This object allows the management action of initializing a device and forcing it to run selftest. It can also be used to reset all information added to the device's NVRAM. When read, it returns a value of other(1). Enumeration: 'reset': 2, 'resetWithDefaults': 3, 'other': 1.

This object is the state of a hardware switch which, when true, causes the device to reset its parameters to the factory defaults when initialized. Enumeration: 'false': 2, 'true': 1.

This object allows the setting of a default gateway address for this device.

A table of IP Addresses to which this device will send traps.

Each entry contains an IP Address to which all SNMP Traps will be sent by this device.

An IP Address to which all SNMP traps generated by this device will be sent.

A software switch that, when set to true, instructs the device to accept a down-line loaded firmware upgrade. If false, the device will not accept upgrades. Enumeration: 'false': 2, 'true': 1.

The physical address of the last host, if any, that responded to the device's request for a downline load of software.

The operational state of the device. Enumeration: 'broken': 3, 'init': 1, 'operate': 2.

The reason that the Device State is BROKEN. If current state is not BROKEN and the Unsolicited Resets counter is nonzero, this object show reason for last failure. Enumeration: 'none': 1, 'firmwareFail': 4, 'selftestFail': 2, 'onlineDiagFail': 3.

A flag, that, when set to True, indicates that the NVRAM failed selftest following the last initialization of the device. Enumeration: 'false': 2, 'true': 1.

The number of times this device was powered on. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.

Number of times the device was initialized with a management command using esysInitSwitch. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.

Number of times the device initialized itself after encountering a fatal error. Power Ups, Management Resets and Unsolicited Resets are all mutually exclusive.

A list of configuration table entries.

A collection of objects containing information for a given configuration entry.

This object is used for indexing the FRU configuration table.

The physical slot number in which the module resides, if applicable. If not applicable, this is reported as '0'.

A textual description of this FRU.

Integer representation for the FRU type. This is the machine-readable form of the descriptor object. Enumeration: 'singleModeMgmtCard': 15, 'singleModeAnsiPortCard4line': 11, 'upgradeApCard': 19, 'fddiCard': 7, 'thinwirePortCard6line': 12, 'controllerBackplane': 8, 'ansiMgmtCard': 2, 'stpCopperPortCard6line': 14, 'ansiPortCard6line': 29, 'dasSingleModeFddiCard': 24, 'qmCard': 9, 'dasAnsiFddiCard': 21, 'niCard': 6, 'dasAnsiASingleModeBfiCard': 22, 'opticalBypass': 26, 'empty': 1, 'apCard': 5, 'ansiPortCard4line': 3, 'dasSingleModeAAnsiBfiCard': 23, 'fan': 4, 'threeNiCard': 20, 'obmUartCard': 27, 'ansi-SingleModeMgmtCard': 16, 'sasSingleModeFddiCard': 25, 'lowPowerPortCard6line': 13, 'lowPowerPortCard4line': 10, 'singleMode-ANSIMgmtCard': 17.

This object represents the FRU revision number.

The operational state of the FRU, if present. Enumeration: 'marginal': 3, 'obrNotSupported': 5, 'working': 2, 'empty': 1, 'broken': 4.

This is a switch to enable or diable FDDI port up and port down traps. When set to true, the concentrator will send a trap when one of its ports comes up or goes down. Enumeration: 'false': 2, 'true': 1.

A list of interface entries. The number of entries is given by ifNumber, defined in MIB-II.

A collection of objects containing information for a given interface.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

Number of frames received with a bad frame check sequence.

Number of times that the device received a frame loss indication from the hardware on the interface.

Number of frames received on the interface that were larger than the maximum legal size.

Number of frames that were transmitted with an error on the line.

This hardware switch, when true, allows write access to the device. This object has meaning only when the corresponding functionality is present. Enumeration: 'false': 2, 'true': 1.

The version number of the Spanning Tree algorithm used by the bridge when in the LAN Bridge 100 Spanning Tree mode.

The version number of the Spanning Tree algorithm used by the bridge when in the 802.1d Spanning Tree mode.

The maximum number of address entries that the bridge can store in its volatile memory.

The maximum number of permanent address entries that the bridge canstore in its NVRAM.

The maximum number of protocol entries that the bridge can store in its protocol database. These entries control the handling of frames based on their Ethernet PT, IEEE 802.2 DSAP or IEEE 802 SNAP Protocol ID.

The maximum number of protocol entries that the bridge can store in its nonvolatile memory. These are retained after a power-down.

The total number of active and inactive address entries that will trigger a purge of the inactive entries.

The number of consecutive successful self-tests needed before the bridge considers a line to be operational.

The interval, in seconds, at which the bridge will run selftests on a line that is in the BROKEN state.

The number of seconds remaining, if this is the Root, for which Topology Change will be propagated in Hello messages. Otherwise this value will be reported as 0.

A switch that controls address filtering. When true, the bridge purges the learned entries from its forwarding database, stops its learning process, and forwards only frames with destination and source addresses that have been specified via management. Enumeration: 'false': 2, 'true': 1.

A switch that controls whether fragmentation is performed by the bridge when a large IP frame is received on a datalink that supports a higer frame size than the other datalink. Enumeration: 'false': 2, 'true': 1.

This object allows the action of removing all management entered addresses from the forwarding database when set to true(2). When read, it returns a value of other(1). Enumeration: 'other': 1, 'true': 2.

This object allows the action of removing all management entered protocols from the protocol database when set to true(2). When read, it returns a value of other(1). Enumeration: 'other': 1, 'true': 2.

The number of address entries in the bridge's volatile memory. These will be lost upon loss of power.

The number of address entries in the bridge's NVRAM. These will be retained after loss of power.

The number of protocol entries that are stored in the bridge's protocol database. These control the handling of frames based on their Ethernet protocol type, IEEE 802.2 DSAP, or 802 SNAP Protocol ID.

The number of protocol entries in the bridge's NVRAM. These are retained after a power loss.

The port on which this command was received.

The address of the LAN Bridge 100 mode bridge that sent this bridge into the LAN Bridge 100 Spanning Tree mode. If this bridge is the Root, this object indicates the bridge that will be polled periodically to determine if it is still necessary to stay in this Spanning Tree mode.

The number of inactive address entries in the bridge's forwarding database. The bridge marks an address entry inactive when the entry is aged out.

The number of seconds since the bridge cleared the forwarding database of inactive entries.

The number of seconds since the bridge last sent a Hello message.

The number of frames addressed to the bridge itself that the bridge discarded because it did not have sufficient receive buffers available.

The number of times that the bridge switched from the 802.1d Spanning Tree mode to the LB100 Spanning Tree mode.

The age, in hundereths of seconds, of the Hello message that established the best root.

A flag that indicates whether a Topology Change is currently in effect on the extended LAN. Enumeration: 'false': 2, 'true': 1.

A flag that indicates if the bridge is attempting to propagate a topology change towards the Root. Enumeration: 'false': 2, 'true': 1.

The number of seconds that the bridge keeps learned entries active while a topology change is in effect.

The number of hello intervals during which the bridge receives one or more bad hellos on a line, before the bridge performs a test on the link. A bad Hello message is one that contains inferior information that is received on a port on which this bridge is Designated.

The number of Hello intervals without bad Hellos that the bridge will wait before it resets its bad Hello count to zero.

The The number of seconds of inactivity on a line that will cause the bridge to run a test on that line. The bridge considers a line to be inactive if it does not receive any frames on that line.

The number of seconds that a Root bridge in LAN Bridge 100 mode waits between polling the LAN Bridge 100 that is keeping it in this mode. This polling is done to determine whether the LB100 is still present on the extended LAN.

The number of seconds that a Root in LAN Bridge 100 Spanning Tree mode will wait for a response from the LAN Bridge 100 which is keeping it in this mode, before which it will assume that the LB100 is no longer on the extended LAN.

A switch that controls the Spanning Tree mode used by the bridge. If in Auto-Select mode, the bridge will go into 802 Spanning Tree mode by default, but will switch to LB100 mode as soon as a LB100 is detected. In 802 Spanning Tree mode, the bridge will stay in 802 mode. Enumeration: 'ieee802': 2, 'autoSelect': 1.

A list of interface entries. The number of entries is given by ifNumber, defined in MIB-II.

A collection of objects containing information for a given interface.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

The reason why the link was last broken. A possible internal fault(1) indicates a problem with the bridge line itself, a possible external fault(2), indicates a problem with the transmission medium to which the line is attached. Enumeration: 'possibleInternalFault': 2, 'noFault': 1, 'possibleExternalFault': 3.

The number of times the bridge restarted the line.

The number of frames received on this line for which the bridge had no address entry in its forwarding database.

The number of frames filtered by the bridge on this port because of address entries in the forwarding database.

The number of frames with multicast destination addresses that were received on the line on the line and filtered by the bridge.

The number of frames received on this line that the bridge discarded because of entries set by management in the protocol database.

The number of frames originating from the bridge itself that were transmitted on this line.

The number of frames addressed to the bridge itself that were received on this line.

The number of bytes in the frames originating from the bridge that were transmitted on this line.

The number of bytes in the frames addressed to the bridge itself that were received on this line.

The number of frames received on the line addressed to the bridge itself discarded by the bridge because it did not have internal buffers to store them.

The number of bytes in Multicast Frames sent, as reported in ifOutNUcastPkts, defined in MIB-II.

The number of bytes in Multicast Frames received, as reported in ifInNUcastPkts, defined in MIB-II.

The number of frames with multicast destination addresses transmitted by the bridge itself on the line.

The number of frames with multicast destination addresses received by the bridge itslef on the line.

The number of bytes in ebrIfMultiDeviceFramesSent.

The number of bytes in ebrIfMultiDeviceFramesReceived.

The number of bytes in frames received that had a bad frame check sequence.

The number of times that the Bad Hellos on the line exceeded the Bad Hello limit.

A list of interface entries for an Ethernet port.

A collection of objects containing information for a given interface.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

The type of physical medium to which this line is attached. Enumeration: 'twistedPairInterface': 11, 'stdAUIInterface': 1, 'ieeeFiberInterRepeaterLink': 6, 'fiberOpticLink850nmDualIdle': 8, 'fiberOpticLink850nmNoIdle': 7, 'dConnAuiIf': 9, 'thinwireInterfaceNoLoop': 10, 'fullDuplexFiberOptic1300nm': 24, 'thinwireInterface': 2.

A switch that informs the bridge whether the transceiver on this line is using the Collision Presence Test (CPT), commonly known as heartbeat. It must be enabled if the line's transceiver has CPT. Enumeration: 'false': 2, 'true': 1.

The number of times that a Collision Presence Test (CPT) signal was not detected within 4 microseconds after a transmission on the line. This counter is valid only if ebrIfEthCollisionPresenceTestSwitch is set to true for this line.

The number of times that a frame received on the line contained both a noninteger multiple of 8 bits and a CRC error.

The number of 802.3 frames received that contained a Length field inconsistent with the actual number of data bytes in the packet.

The number of times that the bridge had to retry transmission of a frame on the line. This was because of collisions during transmission due to congestion on the physical medium.

The number of times that the bridge detected a loss of the carrier signal while transmitting a frame on the line.

The number of times that the bridge failed to transmit a frame on this line after 16 attempts, the collision limit.

A list of interface entries for an FDDI port.

A collection of objects containing information for a given interface.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

The number of times that an error frame was received on thisline but the bridge did not have time to decipher it.

The number or large IP Datagrams that were fragmented into smaller frames because they did not fit into legal size packets on the smaller datalink after translation.

The number of large IP datagrams that could not be fragmented because the DONT-FRAGMENT bit was set in the IP header.

The number of large IP datagrams that were discarded instead of being fragmented because the IP header was of illegal length.

The number of large IP datagrams that were discarded instead of being fragmented because the IP header indicated a length greater than the number of actual bytes in the received datagram.

A list of interface entries for an FDDI port.

A collection of objects containing information for a given interface.

Identifies the Interface. The value of this object is the same as the ifIndex, defined in MIB-II, for this interface.

The age, in hundreths of seconds, of the last Hello message received from the designated bridge on the line.

The time remaining, in hundreths of seconds, before the bridge will leave the Preforwarding state (listening or learning), and enter the Forwarding State. If not in preforwarding, this value will be reported as 0.

The number of Hello intervals during which at least one Bad Hello was received.

A flag that indicates whether the bridge detected a loop condition on this line. Enumeration: 'false': 2, 'true': 1.

A flag that indicates whether a topology change notification received on a link that we are designated on needs to be acknowledged. Enumeration: 'false': 2, 'true': 1.

A table that contains static destination and source address filtering information about unicast and multicast addresses for 2-port bridges.

Information about a specific MAC address for which the bridge has some static forwarding and/or filtering information.

The destination/source MAC Address in a frame to which this entry's filtering information applies.

The Port Number to which this address will be locked-down, if the status is lockDown. Otherwise, this field has a value of 0.

The status of this entry. The meanings of the values are: lockDown(1) : This address is 'locked-down' to the port specified by the ebrTwoPortPortNum field. This address will be allowed to source frames only from the specified port, and frames destined to this address will be sent out only on the specified port. hello(2) : This is the address used by the bridge in the destination field of Spanning Tree Hellos. It is not a writeable value. invalid(3) : Writing this value to the object removes the corresponding entry. filter(4) : Frames with this address in the source or destination field will be filtered by the bridge. forward(5) : Frames with this address in the destination field will be forwarded by the bridge. rateLimit(6) : Frames with this address in the destination field will be rate-limited by the bridge, if it supports rate limiting. Applicable only to multicast addresses. For more detail, please see the ebrRateLimiting group. Enumeration: 'lockDown': 1, 'invalid': 3, 'filter': 4, 'rateLimit': 6, 'forward': 5, 'hello': 2.

A table that contains static destination and source address filtering information about unicast and multicast addresses for multi-port bridges.

Information about a specific MAC address for which the bridge has some static forwarding and/or filtering information.

The destination/source MAC Address in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrMultiPortAllowedToGoTo field. A value of zero indicates that this entry applies on all ports of the bridge.

The set of ports to which frames received from a specific port and sourced from or destined to the address specified by ebrMultiPortAddress are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

The Port Number to which this address will be locked-down, if the status is lockDown. Otherwise, this field has a value of zero.

The status of this entry. The meanings of the values are: portMask(1) : The static filtering for this address is specified by the MultiPortAllowedToGoTo field. lockDown(2) : The static filtering for this address is specified as 'locked-down' to the port specified by the ebrMultiPortPortNum field. This address will be allowed to source frames only from the specified port, and frames destined to this address will be sent out only on the specified port. maskAndLock(3) : The static filtering for this address is specified by both the ebrMultiPortAllowedToGoTo as well as 'locked-down' as explained above for 'lockDown(2)'. hello(4) : This is the address used by the bridge in the destination field of Spanning Tree Hellos. It is not a writeable value. filter(5) : This address will be filtered on all ports. invalid(6) : Writing this value to the object removes the corresponding entry. rateLimit(7) : Frames with this address in the destination field will be rate-limited by the bridge, if it supports rate limiting. Applicable only to multicast addresses. For more detail, please see the ebrRateLimiting group. Enumeration: 'lockDown': 2, 'invalid': 6, 'portMask': 1, 'filter': 5, 'maskAndLock': 3, 'rateLimit': 7, 'hello': 4.

Action taken by the bridge on Ethernet protocol types other than those specified in the ebrTwoEnetProtoTable. Enumeration: 'forward': 1, 'filter': 2.

Action taken by the bridge on 802.2 DSAPs other than those specified in the ebrTwoSapProtoTable. Enumeration: 'forward': 1, 'filter': 2.

Action taken by the bridge on the 5-byte SNAP PIDs other than those specified in the ebrTwoSnapProtoTable. Enumeration: 'forward': 1, 'filter': 2.

A table that contains filtering information about Ethernet protocol types for 2-port bridges.

A table that contains filtering information about Ethernet protocol types for 2-port bridges.

The protocol type in a frame to which this entry's filtering information applies.

Action taken by bridge when it sees this ethernet protocol type in a received frame. The meanings of the values are: forward(1) : Frames received with this protocol type are allowed to be forwarded. filter(2) : Frames received with this protocol type should be filtered. invalid(3) : Writing this value to the object removes the corresponding entry. rateLimit(4) : Frames received with this protocol type will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'forward': 1, 'filter': 2, 'rateLimit': 4, 'invalid': 3.

A table that contains filtering information about 802.2 SAPs in the DSAP field for 2-port bridges.

A table that contains filtering information about 802.2 SAPs in the DSAP field for 2-port bridges.

Index of the SAP table.

The 802.2 DSAP in a frame to which this entry's filtering information applies.

Action taken by bridge when it sees this 802.2 SAP in the DSAP field of a received frame. The meanings of the values are: forward(1) : Frames received with this sap are allowed to be forwarded. filter(2) : Frames received with this sap should be filtered. invalid(3) : Writing this value to the object removes the corresponding entry. rateLimit(4) : Frames received with this sap will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'forward': 1, 'filter': 2, 'rateLimit': 4, 'invalid': 3.

A table that contains filtering information about 5-byte SNAP PIDs for 2-port bridges.

A table that contains filtering information about 5-byte SNAP PIDs for 2-port bridges.

The index into the SNAP table.

The SNAP PID in an 802 frame to which this entry's filtering information applies.

Action taken by bridge when it sees this SNAP PID in a received 802 frame. The meanings of the values are: forward(1) : Frames received with this snap pid are allowed to be forwarded. filter(2) : Frames received with this snap pid should be filtered. invalid(3) : Writing this value to the object removes the corresponding entry. rateLimit(4) : Frames received with this snap pid will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'forward': 1, 'filter': 2, 'rateLimit': 4, 'invalid': 3.

A table that contains filtering information about Ethernet protocol types for multi-port bridges.

A table that contains filtering information about Ethernet protocol types for multi-port bridges.

The protocol type in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrMultiPortEnetProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.

The set of ports to which frames received from a specific port and containing the protocol type specified by ebrMultiEnetProtoType are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

Action taken by bridge when it sees this ethernet protocol type in a received frame. The meanings of the values are: portMask(1) : The static filtering for this address is specified by the MultiEnetAllowedToGoTo field. invalid(2) : Writing this value to the object removes the corresponding entry. filter(3) : Frames received with this protocol type should be filtered. forward(4) : Frames received with this protocol type are allowed to be forwarded. rateLimit(5) : Frames received with this protocol type will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'filter': 3, 'forward': 4, 'rateLimit': 5, 'portMask': 1, 'invalid': 2.

A table that contains filtering information about 802.2 SAPs in the DSAP field for multi-port bridges.

A table that contains filtering information about 802.2 SAPs in the DSAP field for multi-port bridges.

The 802.2 DSAP in a frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrMultiPortSapProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.

The set of ports to which frames received from a specific port and containing the DSAP in an 802 frame specified by ebrMultiSapValue are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

Action taken by bridge when it sees this 802.2 SAP in the DSAP field of a received frame. The meanings of the values are: portMask(1) : The static filtering for this address is specified by the MultiSapAllowedToGoTo field. invalid(2) : Writing this value to the object removes the corresponding entry. filter(3) : Frames received with this protocol type should be filtered. forward(4) : Frames received with this protocol type are allowed to be forwarded. rateLimit(5) : Frames received with this protocol type will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'filter': 3, 'forward': 4, 'rateLimit': 5, 'portMask': 1, 'invalid': 2.

A table that contains filtering information about 5-byte SNAP PIDs for multi-port bridges.

A table that contains filtering information about 5-byte SNAP PIDs for multi-port bridges.

The SNAP PID in an 802 frame to which this entry's filtering information applies.

The port from which a frame must be received to use the corresponding ebrMultiPortSnapProtoType field. A value of zero indicates that this entry applies on all ports of the bridge.

The set of ports to which frames received from a specific port and containing the SNAP PID in an 802 frame specified by ebrMultiSnapValue are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying port 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. If a bit has a value of '1', then the corresponding port is included in the set of ports; the port is not included if its bit has a value of '0'.

Action taken by bridge when it sees this SNAP PID in a received 802 frame. The meanings of the values are: portMask(1) : The static filtering for this address is specified by the MultiSnapAllowedToGoTo field. invalid(2) : Writing this value to the object removes the corresponding entry. filter(3) : Frames received with this protocol type should be filtered. forward(4) : Frames received with this protocol type are allowed to be forwarded. rateLimit(5) : Frames received with this protocol type will be rate-limited by the bridge, if it supports rate limiting. For more detail, please see the ebrRateLimiting group. Enumeration: 'filter': 3, 'forward': 4, 'rateLimit': 5, 'portMask': 1, 'invalid': 2.

A list of interface entries. The number of entries is given by ifNumber, defined in MIB-II.

A collection of objects containing information for a given interface.

Identifies the Interface to which this entry applies.

A switch that controls address filtering. When true, the bridge purges the learned entries from its forwarding database, stops its learning process, and forwards only frames with destination and source addresses that have been specified via management. Enumeration: 'false': 2, 'true': 1.

Action taken by the bridge on Ethernet protocol types other than those specified in the ebrMultiEnetProtoTable. Enumeration: 'forward': 1, 'filter': 2.

Action taken by the bridge on 802.2 DSAPs other than those specified in the ebrMultiSapProtoTable. Enumeration: 'forward': 1, 'filter': 2.

Action taken by the bridge on the 5-byte SNAP PIDs other than those specified in the ebrMultiSnapProtoTable. Enumeration: 'forward': 1, 'filter': 2.

A table of Ethernet protocol types which will selectively be translated in such a way as to guarantee that the form in which a packet was received - Ethernet PT or 802.3 with 1042 format and this PT - will be retained across a pair of these bridges.

A list of NTP protocol type entries.

A protocol type in the NTP table.

Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1). Enumeration: 'other': 1, 'invalid': 2.

A software switch that, when set to true, causes the bridge to translate IPX 'raw 802.3' packets into SNAP encapsulated packets on the FDDI. Note that this works only in environments where all IPX stations use only this particular format. It is recommended that the Ethernet v2 format be used on IPX stations for full connectivity of IPX stations across Ethernet as well as FDDI bridged and routed networks. Enumeration: 'false': 2, 'true': 1.

By default, rate limiting will be disabled. It can be enabled by setting this object to 'true(1)'. Enumeration: 'false': 2, 'true': 1.

This is the maximum number of rate-limited frames per second that the bridge will forward per second.

A table of the count of frames that were dropped by the bridge due to rate limiting on each port.

A list of rate limited frame counter entries.

The port for which this entry contains rate limit counters information.

This is the number of frames per second that were filtered due to address rate limiting.

This is the number of frames per second that were filtered due to protocol rate limiting.

The community string used in SNMP Trap PDUs.

A list of addresses to which traps will be sent and associated information.

Objects containing information for a given trap address.

An IP Address to which all SNMP Trap messages will be sent.

Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1). Enumeration: 'other': 1, 'invalid': 2.

The community string used to identify an SNMP community with access rights of Read-only.

A list of Read-only users and associated information.

Objects containing information for a given Read-only user.

An IP Address, or a set of IP addresses, which has Read-only SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadOnlyUserMask are treated as don't-care.

A 32-bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to eauthReadOnlyUserAddr, the message is considered to have come from a user who has Read-only access. This allows wildcarding, for example, for all NMS's on a given subnet. For fully specified IP addresses required to be in this community, this mask may be set to all 1's.

Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1). Enumeration: 'other': 1, 'invalid': 2.

The community string used to identify an SNMP community with access rights of Read-Write.

A list of Read-Write users and associated information.

Objects containing information for a given Read-Write user.

An IP Address, or a set of IP addresses, which has Read-Write SNMP access to this agent. If this object is used as a wildcard, bits corresponding to the zero bits in the corresponding euthReadWriteUserMask are treated as don't-care.

A 32-bit mask which is applied to (ANDed with) the source IP address of an incoming SNMP message. If the result of the mask is equal to eauthReadWriteUserAddr, the message is considered to have come from a user who has Read-Write access. This allows wildcarding, for example, for all NMS's on a given subnet. For fully specified IP addresses required to be in this community, this mask may be set to all 1's.

Writing invalid(2) to this object removes the corresponding entry. When read, this object always returns a value of other(1). Enumeration: 'other': 1, 'invalid': 2.