ALLIEDTELESYN-MIB: View SNMP OID List / Download MIB

The status of the Redundant Power Supply (RPS) connection, ie, whether an RPS is actually connected or not, regardless of whether the RPS is on or not. not-supported means that an RPS is not supported in this hardware platform, connected means that the RPS is connected, not-connected means that the RPS is not connected, and not-monitoring means that the status of the RPS is not being monitored presently. RPS monitoring can be turned on via the variable fanAndPsRpsMonitoringStatus, or by the command SET SYSTEM RPSMONITOR=ON. Enumeration: 'not-monitoring': 3, 'not-connected': 2, 'connected': 1, 'non-supported': 0.

The status of the main Power Supply. on means that the power supply is present and fully operational. off means that the power supply is totally off (and obviously only applies to systems with a redundant power supply). faulty means that the main power supply is delivering power but that a component of the power supply is faulty. This applies to systems like SwitchBlade which have 3 power supplies but do not provide individual power supply monitoring. Also, in the case of SwitchBlade, power supply status includes the status of the fans in the power supply. Enumeration: 'on': 1, 'faulty': 3, 'off': 2.

The status of the redundant Power Supply. non-supported means this device does not support redundant power supplies, on means that the redundant power supply is connected and able to supply system power if required, off means that the redundant power supply is either not connected or is connected and is not able to supply system power if required, and not-monitoring means that the status of the RPS is not being monitored presently. RPS monitoring can be turned on via the variable fanAndPsRpsMonitoringStatus, or by the command SET SYSTEM RPSMONITOR=ON. Enumeration: 'not-monitoring': 3, 'on': 1, 'off': 2, 'non-supported': 0.

The current status of redundant power supply monitoring. The monitoring of the redundant power supply and its fan must be enabled by command or by setting this variable to on. The value non-supported means that this device does not support redundant power supplies. Only the values on or off may be written to this variable. If this variables reads as non-supported, an attempt to write to this variable will result in a bad value error. Enumeration: 'on': 1, 'off': 2, 'non-supported': 0.

The status of the main Power Supply fan. non-supported means that this device does not support monitoring on the main power supply fan, or that there is no main power supply fan. The warning means the fan's speed is outside 30% of the expected speed. Enumeration: 'not-ok': 2, 'warning': 3, 'ok': 1, 'non-supported': 0.

The status of the redundant Power Supply Fan. non-supported means this device does not support redundant power supplies, ok means that the redundant power supply fan is running, not-ok means that the redundant power supply fan is not running, and not-monitoring means that the status of the RPS is not being monitored presently. RPS monitoring can be turned on via the variable fanAndPsRpsMonitoringStatus, or by the command SET SYSTEM RPSMONITOR=ON. Enumeration: 'not-monitoring': 3, 'not-ok': 2, 'ok': 1, 'non-supported': 0.

The status of temperature in this device. ok means that the device is not capable of monitoring temperature or that the temperature is OK, not-ok means that the temperature is being monitored and is currently out of the range 0C - 45C. Enumeration: 'not-ok': 2, 'ok': 1.

The status of the presence of the fan tray in this system. Systems which do not support a fan tray return the value non-supported. Upon removal of the fan tray there is a short period (20s) before the value of this variable is changed to not-present. This is to allow for scheduled replacement and/or cleaning of the fan tray. Enumeration: 'not-present': 2, 'non-supported': 0, 'present': 1.

The status of the fan tray in this system. Systems which do not support a fan tray return the value non-supported. The value ok is returned if all fans in the fan tray are running at full speed. The value not-ok is returned if one of more of the fan tray fans is running slow or has stalled. Enumeration: 'not-ok': 2, 'ok': 1, 'non-supported': 0.

The current status of main power supply monitoring. The monitoring of the main power supply and its fan is always enabled by those systems that support it. Systems which do not support main power supply or fan monitoring report a value of not-supported. The value ok is returned for those systems that do support main power supply and fan monitoring, and where the monitoring operation is reporting valid information (refer to fanAndPsMainFanStatus for the current status of the system). When main power supply and fan monitoring is failing, the value not-ok is returned. Enumeration: 'not-ok': 2, 'ok': 1, 'non-supported': 0.

The table of AT8948 fanAndPsPsuStatusTable. Each entry in the table represents the status of one of the power supplies in AT8948 system. Each power supply has its own board ID.

A single entry of AT8948 fanAndPsPsuStatusTable, indexed by fanAndPsPsuNumber field.

The PSU board identity for which this entry holds. If the system consists only of a single PSU board, only one entry will appear in the table, whose index is 1.

The PSU present state, displayed as 'yes' if present, or 'no' if absent. Enumeration: 'yes': 0, 'no': 1.

The PSU type, displayed as AC, or DC, or FAN, or NOT PRESENT. Enumeration: 'ac': 0, 'not-supported': 4, 'fan': 2, 'dc': 1, 'not-present': 3.

The PSU fan status, displayed as OK, or FAIL, or NOT PRESENT. Enumeration: 'fail': 1, 'not-supported': 3, 'ok': 0, 'not-present': 2.

The PSU temperature, displayed as GOOD, or HIGH, or NOT PRESENT, or NOT SUPPORTED. Enumeration: 'high': 1, 'good': 0, 'not-supported': 3, 'not-present': 2.

The PSU power status, displayed as GOOD, or BAD, or NOT PRESENT or NOT SUPPORTED. Enumeration: 'bad': 1, 'good': 0, 'not-supported': 3, 'not-present': 2.

The status of the accelerator card fans. Non-supported means this device does not support monitoring of the accelerator card fans. Enumeration: 'not-ok': 2, 'ok': 1, 'non-supported': 0.

A router/switch restart request. A management station can remotely instruct an ATI router/switch to action a warm or cold restart. Once all the appropriate internal checks have been made, the router/switch will acknowledge the request via normal SNMP channels. The restart instruction will be actioned after waiting for a period of 5 seconds, this is because the SNMP acknowledgement packet needs time to reach the management station. Once the request has been actioned, it can not be cancelled and communication with the router/switch will be lost during system initialisation. Enumeration: 'restart-cold': 2, 'restart-warm': 1, 'restart-none': 0.

Maximum CPU utilisation since the router was last restarted. Expressed as a percentage.

Average CPU utilisation since the router was last restarted. Expressed as a percentage.

Average CPU utilisation over the past minute. Expressed as a percentage.

Average CPU utilisation over the past ten seconds. Expressed as a percentage.

Average CPU utilisation over the past second. Expressed as a percentage.

Maximum CPU utilisation over the last 5 minutes. Expressed as a percentage.

Average CPU utilisation over the past 5 minutes. Expressed as a percentage.

The value supported indicates general temperature is displayed by the device. The value not-supported indicates the device displays specific temperature information or none at all. Enumeration: 'supported': 1, 'not-supported': 0.

The current temperature of product's base board, in degrees Celsius. A device which doesn't support this group will return the value 0 for this variable.

The status of temperature in this device. ok indicates the temperature is below the threshold temperature or the device is not capable of monitoring temperature. not-ok indicates the temperature is being monitored and is currently above the threshold temperature (displayed in generalTemperatureThreshold). Enumeration: 'not-ok': 2, 'ok': 1.

The temperature threshold for the device. If the temperature of the device rises above this threshold generalTemeratureStatus will indicate a not-ok status.

The table of SwitchBlade sysTemperature. Each entry in the table represents temperature monitoring from one of the CPU cards which may be present in the SwitchBlade system.

A single entry of SwitchBlade sysTemperature

The board for which this temperature entry holds. If the system consists only of a single CPU board, only one entry will appear in the table, whose index is master(1). Enumeration: 'slave': 2, 'master': 1.

The actual SwitchBlade temperature. This temperature is measured within the SwitchBlade CPU, and is sampled at 1 second intervals.

The temperature status with regard to the fixed temperature threshold. The value of the fixed temperature threshold is set at 90 degrees C. This variable represents whether the actual temperature is above the threshold (value is crossover(2)) or below the threshold (value is normal(1)). If the temperature is exactly the same as the fixed temperature threshold, the value of this variable reads as normal(1). Enumeration: 'crossover': 2, 'normal': 1.

The temperature status with regard to the settable temperature threshold. The value of the settable temperature threshold is set by management intervention. This variable represents whether the actual temperature is above the threshold (value is crossover(2)) or below the threshold (value is normal(1)). When the value of this variable is undefined(3), no settable threshold has been specified and the value of sbTempSettableThreshold is not used. Enumeration: 'crossover': 2, 'undefined': 3, 'normal': 1.

The value of the settable temperature threshold. This can be set independently for each temperature entry. The value of this threshold is only valid when sbTempSettableThresholdStatus is not set to undefined(3).

The value of the fixed temperature threshold. This value is fixed for both CPU cards, and cannot be set.

The value supported indicates whether accelerator card temperature is displayed by the device. The value not-supported indicates the device does not display specific accelerator card temperature information. Enumeration: 'supported': 1, 'not-supported': 0.

The current temperature of product's base board, in degrees Celsius. A device which doesn't support this group will return the value 0 for this variable.

The status of temperature in this device. ok indicates the temperature is below the threshold temperature or the device is not capable of monitoring temperature. not-ok indicates the temperature is being monitored and is currently above the threshold temperature (displayed in generalTemperatureThreshold). Enumeration: 'not-ok': 2, 'ok': 1.

The temperature threshold for the device. If the temperature of the device rises above this threshold generalTemeratureStatus will indicate a not-ok status.

Generated when the temperature status of the device changes.

Trap occurs when fixed threshold status changes. The actual temperature and the fixed threshold are also given.

Trap occurs when settable threshold status changes. The actual temperature and the settable threshold are also given.

Generated when the temperature status of the device changes.

The contact details for Allied Telesyn inc.

Percentage of free memory still available on device

Total number of buffers available on device

Shows the status of the real time clock Enumeration: 'invalid': 0, 'normal': 1.

Host Identifier of this device

Generated when the RPS connection status changes.

Generated when the main power supply status changes.

Generated when the RPS status changes.

Generated when the main fan changes status.

Generated when the redundant fan changes status.

Generated when the temperature changes status.

Generated when the fan tray presence status changes.

Generated when the fan tray status changes.

Generated when the main power supply monitoring status changes.

Generated when the accelerator fans' status changes.

Generated at boot when the device detects that the BBR has been corrupted and reinitialised. This can happen if the device's BBR battery has run down, and the device has been powered off, then on.

The table of Ethernet interfaces.

A single entry in the Ethernet interfaces table.

The ifIndex of the Ethernet interface.

The index in the arBoardTable of the board on which this Ethernet interface resides. If this Ethernet interface is not found, the value of this object is 0.

The position on this Ethernet interface's board of this Ethernet interface. If this Ethernet interface is not found, the value of this object is 0.

The duplex mode of this Ethernet interface. The value unknown is returned when the interface cannot or has not yet made a determination of its duplex mode, or when the interface cannot be found. Enumeration: 'half-duplex': 2, 'full-duplex': 1, 'unknown': 3.

The number of flash get operations that have failed.

The number of flash open operations that have failed.

The number of flash read operations that have failed.

The number of flash close operations that have failed.

The number of flash complete operations that have failed.

The number of flash write operations that have failed.

The number of flash create operations that have failed.

The number of flash put operations that have failed.

The number of flash delete operations that have failed.

The number of flash check operations that have failed.

The number of flash erase operations that have failed.

The number of flash compaction operations that have failed.

The number of flash verify operations that have failed.

The table of call details parameters.

A single entry of ISDN call details. This contains the parameters of a single ISDN call details.

The index of the call details entry in the call details table. When an entry is created in this table, the index does not have to be written. However, to reference the values that are written, an unused index must be found by reading the index values of the table until a no such object error is returned. Attempting to create a row by using an already used index will result in simply changing the parameters of an existing call details entry.

The name of the ISDN call details. This must be unique for all ISDN call details, when comparisons are done ignoring the case of letters. Valid characters in the ISDN call name include 0-9, a-z, A-Z and '_'. A name consisting of all digits is not valid. Setting this object is mandatory on row creation. However, this object cannot be set for an existing call. This is because for the command line interface calls are identified by name. There is one exception. Setting ccDetailsName to an empty string will cause the call details to be deleted.

The remote ISDN call name. This name can be referenced by certain other call details parameters related with setting up the Q.931 SETUP message for outgoing calls, or searching for calls for incoming calls. Valid characters in the ISDN remote call name include 0-9, a-z, A-Z and '_'. A remote name consisting of all digits is valid.

The number called when this call details is activated. The number should include all telephone network access codes, country codes and area codes required to make a call from the particular ISDN interface. Setting this object is mandatory on row creation.

The number used as the calling number when this call is activated. The calling number can optionally be placed in the outgoing SETUP message.

The number called when all retries with the main called number have failed. In this event, the router tries once with the alternate number, then checks the ccDetailsKeepup object to determine whether to try again with the main number.

Whether this ISDN call is enabled or disabled for incoming and outgoing calls. If the call details entry is disabled, all existing active calls based on this call details entry are left active. Enumeration: 'disabled': 1, 'enabled': 2.

The direction for which calls may be made or received using this call details entry. Enumeration: 'both': 3, 'out-only': 2, 'in-only': 1.

The precedence of this call details entry in the event of call collision. Call collision occurs when an incoming call for a given details entry is detected while an outgoing call is waiting to complete. This object configures whether the router treats the incoming or outgoing call as having precedence. Since the device at the other end will also probably be experiencing a call collision, the precedence should be configured to the opposite value at the other end. Setting this object is mandatory on row creation. Enumeration: 'out': 2, 'in': 1.

The time, in seconds, that active calls created from this call details should be held up after initial activation. The call will be held up for at least this time, unless cleared from the network. Thus, for example, PPP idle timeouts will not bring the call down.

The ifIndex of an ISDN interface on this router which is the preferred ISDN interface on which to make an outgoing call using this call details entry. The ifIndex, if not 0, should reference the ifEntry which contains information about the entire ISDN interface, at the lowest layer. If a channel is not available on this interface, the call can try other interfaces in order to make the call. This object is not used on incoming calls. If the value of this object is set to 0, no interface will be preferred over any other. If the value of this object does not reference the ifEntry for the entire ISDN interface, no interface will be preferred.

The ifIndex of an ISDN interface on this router which is the required ISDN interface on which to make an outgoing call using this call details entry. The ifIndex, if not 0, must reference the ifEntry which contains information about the entire ISDN interface, at the lowest layer. If a channel is not available on this interface, the call fails. This object is not used on incoming calls. If the value of this object is set to 0, no interface will be required. If the value of this object does not reference the ifEntry for the entire ISDN interface, no interface will be required.

The priority of calls generated from this call details entry. The priority determines whether calls can be bumped for higher priority calls. The value of priority falls into ranges: 0-19 - call bumped by incoming or outgoing, voice or data calls 20-39 - call bumped by outgoing voice and incoming or outgoing data calls 40-59 - call bumped by emergency voice calls or incoming or outgoing data calls 60-99 - call bumped by emergency voice calls or outgoing data calls. Note that when the call is bumped by a data call, the data call must have higher priority than the call being bumped.

The time in seconds between retries of calls generated from this call details entry.

The number of retries in a retry group for calls generated from this call details entry. Note that the default value means that by default the call will not be retried.

The time in seconds between retry groups for retries of calls generated from this call details entry.

The number of retry groups for calls generated from this call details entry. Note that the default value means that by default no retry groups will be attempted.

A flag indicating whether calls generated from this call details entry should be kept up always. Inspection of this flag takes place when a call is cleared from an external source. If set to 'yes', the call will be retried. Enumeration: 'yes': 2, 'no': 1.

The CLI information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no CLI information in placed in the SETUP message. The value 'calling' means that the calling number from the call details entry is placed in the SETUP message. The value 'interface' means that the Q.931 interface number for the interface and DLC on which the call is made is placed in the SETUP message. The value 'nonumber' means that the CLI information element is placed in the SETUP message with no number information. The network will fill the number in. Enumeration: 'interface': 3, 'nonumber': 4, 'off': 1, 'calling': 2.

The user-user information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no user-user information in placed in the SETUP message. The value 'local' means that the call name from the call details entry is placed in the SETUP message. The value 'remote' means that the remote call name from the call details entry is placed in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

The called subaddress information placed into outgoing SETUP messages when this call details is used to generate an outgoing call. The value 'off' means that no called subaddress information in placed in the SETUP message. The value 'local' means that the call name from the call details entry is placed in the SETUP message. The value 'remote' means that the remote call name from the call details entry is placed in the SETUP message. Note that the action of this object is overridden by the value of the object ccDetailsOutSubaddress. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

This object gives a way to override the called subaddress information placed into outgoing SETUP messages when this call details is used to generate an outgoing call, as given by the ccDetailsOutSetupCalledSub object. The object is an arbitrary string of ASCII characters, from 0 to 31 characters long.

A flag indicating whether or not to call back the caller when an incoming call is generated from this call details entry. If set to 'yes', the incoming call will be cleared, and after a short delay, an outgoing call will be activated for this call details entry. Enumeration: 'yes': 2, 'no': 1.

The time, in tenths of a second, which the router will wait after clearing an incoming call whose call details entry specified that the caller should be called back before making the return call. The purpose of this object is to allow the user to specify a delay in callback which will allow the network to properly clear the call at both this end and the remote end.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the called subaddress information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'local' means that the call details entry is used in the search and the called subaddress information is compared with the call details entry name. The value 'remote' means that the call details entry is used in the search and the called subaddress information is compared with the call details entry remote name. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the user-user information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'local' means that the call details entry is used in the search and the user-user information is compared with the call details entry name. The value 'remote' means that the call details entry is used in the search and the user-user information is compared with the call details entry remote name. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether this call details entry is used in a search of call details for an incoming call based on the contents of the calling number information in the incoming SETUP message. The value 'off' means that this call details entry is not used in the search. The value 'on' means that the call details entry is used in the search and the calling number information is compared with the call details entry called number. The value 'list' means that the call details entry is used in the search and the calling number information is compared with the numbers on the CLI list reference by the object ccDetailsInSetupCliSearchList. The value 'list' cannot be set by an SNMP management entity. Rather the ccDetailsInSetupCliSearchList object should be set to a non-zero value, which will automatically set this object to 'list'. A number of searches are carried out until a matching call is found. First a search against the called subaddress in the SETUP message, then a search against the user-user information in the SETUP message, then a search against the calling number information in the SETUP message, then a search for any call that is configured to respond to any incoming call. Enumeration: 'on': 2, 'list': 3, 'off': 1.

If the ccDetailsInSetupCliSearch object is set to 'list', this object gives the index of the CLI list to search. The value of CLI list indices is 1..100. The value 0 is returned when the ccDetailsInSetupCliSearch object is not set to 'list'. If the value of this object is set to 0 via SNMP, then the ccDetailsInSetupCliSearch object will be internally set to 'off'. Subsequently setting the value of this object to a non-zero value will set the ccDetailsInSetupCliSearch object to 'list'. Note that when using the command line interface, CLI list indices range from 0 to 99, but when using SNMP they range from 1 to 100. This is because SNMP will not allow a table index to have the value 0, and the command line usage of indices from 0 to 99 is too well established to change.

Determines whether this call details entry will match any incoming call. After all searched for incoming calls have been carried out based on called subaddress, user-user information and calling number, a search is carried out for the first call found with this flag set to 'yes'. Enumeration: 'yes': 2, 'no': 1.

Determines whether to perform a check when an incoming call matches this call details entry based on the contents of the called subaddress information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'local' means that the check is carried out and the called subaddress information is compared with the call details entry name. The value 'remote' means that the check is carried out and the called subaddress information is compared with the call details entry remote name. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether to perform a check when an incoming call matches this call details entry based on the contents of the user-user information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'local' means that the check is carried out and the user-user information is compared with the call details entry name. The value 'remote' means that the check is carried out and the user-user information is compared with the call details entry remote name. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'local': 2, 'off': 1, 'remote': 3.

Determines whether to perform a check and which check to perform when an incoming call matches this call details entry based on the contents of the calling number information in the incoming SETUP message. The value 'off' means that the check is not carried out. The value 'present' means that the check is carried out only if calling number information is present. The value 'required' means that the calling number must be present for the check to pass. When the check is carried out, the calling number information is compared with the numbers in the CLI list referenced by the object ccDetailsInSetupCliCheckList. A number of checks are optionally carried out once a matching call is found. The first check is against the called subaddress in the SETUP message, then against the user-user information in the SETUP message, then against the calling number information in the SETUP message. Enumeration: 'required': 3, 'off': 1, 'present': 2.

If the ccDetailsInSetupCliCheck object is set to 'present' or 'required', this object gives the index of the CLI list to check against. The value of CLI list indices is 1..100. The value 0 means that no list to check against is defined and the check immediately fails. Note that when using the command line interface, CLI list indices range from 0 to 99, but when using SNMP they range from 1 to 100. This is because SNMP will not allow a table index to have the value 0, and the command line usage of indices from 0 to 99 is too well established to change.

The type of user of this call. The value 'attach' means that users have to attach to this call before the call can be used for outgoing or incoming calls. The value 'ppp' means that for incoming calls only dynamic PPP interfaces will be created whenever this call details entry is matched. Enumeration: 'attach': 1, 'ppp': 2.

The type of login for calls generated using this call details entry, for incoming calls only. Incoming calls can be configured to go through a logging in phase before the call is brought up. This object defines which login types are used. The value 'none' means don't do a login phase. The value 'userdb' means use the user database on the router to check login parameters. The value 'radius' means use the router's configured RADIUS servers to check the login parameters. The values 'pap-tacacs', 'chap' and 'pap-radius' apply only when the user is 'ppp' and determine how the dynamic PPP interface are configured for authentication. The value 'pap-tacacs' means use PAP to authenticate and use the TACACS server to check the login parameters. The value 'pap-radius' means use PAP to authenticate and use the RADIUS server to check the login parameters. The value 'chap' means use CHAP to authenticate. The value 'tacacs' means use the TACACS server to check login parameters. The value 'all' means use the user database, TACACS and RADIUS to check the login parameters. The login parameters for values 'userdb', 'radius', 'tacacs' and 'all' are determined by the ccDetailsUsername and ccDetailsPassword objects. Enumeration: 'userdb': 2, 'none': 1, 'tacacs': 7, 'all': 8, 'pap-tacacs': 4, 'chap': 5, 'radius': 3, 'pap-radius': 6.

The source of the username when the ccDetailsLoginType object has a value of 'userdb', 'radius', 'tacacs' or 'all'. The value 'none' means no username is defined. The value 'cli' means take the username from the calling number information in the SETUP message. The value 'calledsub' means take the username from the called subaddress information in the SETUP message. The value 'useruser' means take the username from the user-user information in the SETUP message. The value 'callname' means take the username from the call details entry name. Enumeration: 'useruser': 4, 'callname': 5, 'none': 1, 'calledsub': 3, 'cli': 2.

The source of the password when the ccDetailsLoginType object has a value of 'userdb', 'radius', 'tacacs' or 'all'. The value 'none' means no password is defined. The value 'cli' means take the password from the calling number information in the SETUP message. The value 'calledsub' means take the password from the called subaddress information in the SETUP message. The value 'useruser' means take the password from the user-user information in the SETUP message. The value 'callname' means take the password from the call details entry name. Enumeration: 'useruser': 4, 'callname': 5, 'none': 1, 'calledsub': 3, 'cli': 2.

The time, in tenths of a second, which the router will wait after clearing an existing call which has been bumped to make way for a call based on this call details entry.

The data rate to use for active calls based on this call details entry. The actual data rate for outgoing calls is determined by both this object and the data rate parameter for the Q.931 interface chosen for the call. If either this object or the interface object specify a rate of 56k, then 56k will be the rate for the call. Otherwise, the default rate of 64k will be used. This allows interoperability between ISDNs which only allow 56k of data on a B channel. Enumeration: 'rate-56k': 2, 'rate-64k': 1.

The PPP template to use when creating dynamic PPP interfaces for calls generated from this call details entry. The value 33 represents a default PPP template, the values 1 to 32 represent PPP templates that are currently defined in the router. Note that when using the command line interface, PPP template indices range from 0 to 31, but when using SNMP they range from 1 to 32. This is because SNMP will not allow a table index to have the value 0. While there is no PPP template table accessible via SNMP, if there was, the indices of the table would have to range from 1 to 32.

The module ID of the user module currently attached to this ISDN call details entry.

The number of attachments from the user module currently attached to this call details entry. The ccAttachmentsTable gives the actual attachments for each call details entry.

The table of CLI list entries.

A single entry in the CLI list table. This contains a single number, as well as index information.

The index of the CLI list. CLI lists from 1 to 100 are defined in the router.

The index of the CLI list entry within the CLI list. The minimum CLI list entry is 1. CLI lists are unlimited in length, although internal memory requirements could result in failure to create a given entry. When creating a row in this table, the entry index should be set to index the first empty row. Only one CLI list row in a given list should be created in any one SNMP message. Attempting to create more than one row will result in failure.

The number for this CLI list entry. Setting the number to a zero length string removes the entry from the CLI list, with consequent reshuffling of CLI entry indices. Thus the easiest way to delete an entire CLI list is to repeatedly set the first element in the list to a zero length string. A failure to SET will occur when this is attempted on an empty list.

The table of ISDN active calls.

A single entry in the active call table.

The index of the active call. There are 128 possible active calls in the router simultaneously.

The index of the call details entry which generated this active call. Thus the index into the ccDetailsTable for this call.

The interface index of the interface on which this active call is being made or received. A value of zero indicates that the active has not yet had an interface assigned to it. The ifEntry indexed by this object is the ifEntry for the entire ISDN interface, not the ifEntry for the active call's B channel.

The data rate in use for this active call. This is determined by the call details setting of data rate, the ISDN interface setting for data rate, and the contents of the bearer capability information in the incoming SETUP message. Enumeration: 'rate-56k': 2, 'rate-64k': 1.

The state of this active call. The value 'null' indicates that this active call does not actually exist, in other words it is in the process of being created or destroyed. The value 'off' means that the active call is just being activated. The value 'try' means that the active call is attempting to establish. The value 'on' means that the active call is established. The value 'wait' means that the active call is waiting to retry. The value 'await1' means that the active call is waiting for authentication to succeed before becoming established. Enumeration: 'on': 4, 'off': 2, 'try': 3, 'null': 1, 'await1': 6, 'wait': 5.

The direction of this active call. The value 'in' indicates that this active call is an incoming call, the value 'out' indicates that the active call is an outgoing call. The value 'undefined' indicates that the active call has just been created and a direction has not been assigned to it yet. Enumeration: 'out': 2, 'undefined': 3, 'in': 1.

The module ID of the user module attached to this ISDN active call.

The instance of the user module attached to this ISDN active call.

The B channel number for this active entry. BRI interfaces have B channels in the range 1..2, PRI interfaces have B channels in the range 1..31, excluding a channel which is the D channel. A value of 0 for this entry means that either a B channel is not currently allocated for this call, or that more than one B channel is allocated. In the second case, the management client will have to walk the B channel allocation table looking for channels with the same active call index as this call's.

The table of ISDN call log entries.

A single entry in the ISDN call log table.

The index of the call log entry. Since the call log table is dynamic, there is no guarantee that this index will continue to refer to the same log entry over time.

The name of the call details entry which generated the active call for which this is the log entry.

The state of the log entry. The value 'initial' means that the call is being established. The value 'active' means that the call is currently established. The value 'disconnected' means that the call was disconnected after being established for some time. The value 'cleared' means that the call was cleared abormally while in the establishment phase. Enumeration: 'active': 2, 'initial': 1, 'disconnected': 3, 'cleared': 4.

A string in the format 'dd-mmm-yyyy hh:mm:ss' which gives the start time of the call for which this is the log entry. If the call never reached or has not yet reached the active state, this object will be a zero-length string.

The direction of the call for which this is the log entry. Enumeration: 'out': 2, 'in': 1.

The duration in seconds, of the call for which this is the log entry. A value of 0 in this field means either that the call has just started, that the call was cleared before becoming established, or that the call is still active. In other words, a non-zero value is present in this object only for calls which reach establishment and have since been cleared.

For incoming calls, the calling number, if this was made available in the SETUP message. For outgoing calls, the number dialed. If the number was not available, this object is a zero length string.

The table of call detail attachment entries.

A single entry in the attachment table.

The index of the call details entry to which this attachment entry belongs.

The index of the attachment entry within the attachment list.

The index of the active call for this attachment. A value of 0 indicates that there is currently no active call for this attachment. A value of 1 to 128 references the active call currently in place for this attachment.

The instance of the user module attached to the ISDN active call for this attachment. This object should return the same value as the object ccActiveCallUserInstance for the active call indexed by ccAttachmentActiveCallIndex, if this is not 0.

The table of B channel attachment entries.

A single entry in the B channel attachment table.

The interface index of the interface which this B channel entry is on. The ifEntry indexed by this object is the ifEntry for the entire ISDN interface, not the ifEntry for the active call's B channel.

The B channel number for this B channel entry. BRI interfaces have B channels in the range 1..2, PRI interfaces have B channels in the range 1..31, excluding a channel which is the D channel.

A flag indicating whether this B channel is actually allocated to a call or not. Enumeration: 'yes': 2, 'no': 1.

The type of call on this B channel. If the B channel is not allocated, the call type will be undefined. Enumeration: 'x25': 4, 'voice': 3, 'data': 2, 'undefined': 1.

The index of the active call which is currently attached to this B channel. If the value of this object is 0 the channel is either not allocated, or is not allocated to a data call.

The priority of the call which has this B channel allocated to it. This is in the range 0..99 for data calls, 150 for voice calls and 200 for emergency voice calls. A B channel which is not allocated will have a priority of 0.

The direction of the call which has this B channel allocated to it. If this B channel is not allocated the value will be 'unallocated'. Enumeration: 'out': 2, 'unallocated': 3, 'in': 1.

The table of BRI interfaces.

A single entry in the BRI interfaces table.

The ifIndex of the BRI interface.

The index in the arBoardTable of the board on which this BRI interface resides.

The position on this BRI interface's board of this BRI interface.

The mode of operation of this BRI interface. The value isdn means that the entire interface is operating as an ISDN interface, the value tdm means that the entire interface is operating as TDM groups and the value mixed means that some channels in the interface are dedicated to ISDN and some to TDM groups. Enumeration: 'mixed': 3, 'tdm': 2, 'isdn': 1.

A bit map of the channels in the BRI interface which are dedicated to TDM. Channel B1 has channel map value of 1, channel B2 has a channel map value of 2.

A bit map of the channels in the BRI interface which are dedicated to ISDN. Channel B1 has channel map value of 1, channel B2 has a channel map value of 2.

The table of channels on BRI interfaces.

A single entry in the BRI channels table.

The ifIndex of the BRI interface.

The channel index of the BRI channel. Channel B1 has index 1, channel B2 has index 2 and the D channel has index 3.

The mode of this BRI channel. The value isdn means that the channel is reserved for use in ISDN calls. The value tdm means that the channel is reserved for use by TDM. For the D channel, this object will always have the value isdn. Enumeration: 'none': 3, 'tdm': 2, 'isdn': 1.

The state of this BRI channel. The value inactive means that the channel does not currently have an active user, either an ISDN call or an active TDM group. The value active means that the channel is in use, either by an ISDN call or an active TDM group. For the D channel, this object will have the value active if LAPD is using the D channel (either for call control or X.25), or the value inactive otherwise. Enumeration: 'active': 2, 'inactive': 1.

The table of PRI interfaces.

A single entry in the PRI interfaces table.

The ifIndex of the PRI interface.

The index in the arBoardTable of the board on which this PRI interface resides.

The position on this PRI interface's board of this PRI interface.

The mode of operation of this PRI interface. The value isdn means that the entire interface is operating as an ISDN interface, the value tdm means that the entire interface is operating as TDM groups and the value mixed means that some channels in the interface are dedicated to ISDN and some to TDM groups. Enumeration: 'mixed': 3, 'tdm': 2, 'isdn': 1.

A bit map of the channels in the PRI interface which are dedicated to TDM. PRI channels are numbered from 0 to 31, 0 is unused, 16 (E1) or 24 (T1) is the D channel. The map values are 2 to the power of the channel number.

A bit map of the channels in the PRI interface which are dedicated to ISDN. PRI channels are numbered from 0 to 31, 0 is unused, 16 (E1) or 24 (T1) is the D channel. The map values are 2 to the power of the channel number.

The type of primary rate interface. E1 has 30 B + D channel, T1 has 23 B + D channel. If the value unknown is returned for this object, the exact PRI type has not yet been determined. Enumeration: 'unknown': 3, 'e1': 1, 't1': 2.

The table of channels on PRI interfaces.

A single entry in the PRI channels table.

The ifIndex of the PRI interface.

The channel index of the PRI channel. Valid channels have indices from 1 to 31. The D channel on an E1 interface has index 16, the D channel on a T1 interface has index 24.

The mode of this PRI channel. The value isdn means that the channel is reserved for use in ISDN calls. The value tdm means that the channel is reserved for use by TDM. For the D channel, this object will usually have the value isdn. An exception is if the interface is running common D channel mode and the D channel is reserved for TDM. Enumeration: 'neither': 3, 'tdm': 2, 'isdn': 1.

The state of this PRI channel. The value inactive means that the channel does not currently have an active user, either an ISDN call or an active TDM group. The value active means that the channel is in use, either by an ISDN call or an active TDM group. Enumeration: 'active': 2, 'inactive': 1.

The table of load parameters, dynamic and static.

A single entry of load parameters. This contains the parameters required to perform a load from the router.

There are two sets of load information, dynamic and static. The dynamic information is used once, then cleared. The static information is used whenever the dynamic information is not available. The dynamic information is also used to indicate the current load parameters when a load is in progress. Enumeration: 'dynamic': 2, 'static': 1.

The IP address from which load will load.

The destination of the file loaded, either flash or nvs memory, or undefined. Enumeration: 'flash': 3, 'nvs': 2, 'undefined': 1.

The file name of the file being loaded.

A delay in seconds between the initiation of the load and the start of the load. This allows for time to set up TFTP servers in cases where the terminal and TFTP server are using the same piece of equipment but will not work simultaneously.

Status and action object for the load module. The values 1 to 5 are read-only values and reflect the state of the load module. Values 4 and 5 (complete and reset) are 'read-once', that is, if their values are read, either by SNMP or by manager console command, then they will be changed back to idle(1). The action values (6 and 7) cause a start and stop of the load process respectively. Starting the load can only occur if this field has the values 1, 4, or 5. Stopping the load can only occur is this field has the values 2 or 3. Reading the value of the loadStatus after one of actionstart or actionstop has been set will give one of the values 1 to 5. Note: A single exception to the above rules is that if the value of loadStatus is idle(1), then a write of 1 to this variable will succeed without generating an error. This exception is to allow certain SNMP test suites to test this variable without throwing up errors. Enumeration: 'reset': 5, 'loading': 3, 'complete': 4, 'idle': 1, 'actionstop': 7, 'actionstart': 6, 'wait': 2.

The list of install configurations for the router.

An entry in the list of install configurations.

The index for the install table. There are four install configurations defined in the router, default, preferred, temporary and current. The router will attempt to use these in the order temporary, preferred, default when it boots. An install that is undefined will be skipped, an install which points to a file which is not present will be skipped. When the temporary install is used, the information is deleted. The current configuration shows what the router currently has installed. Enumeration: 'default': 3, 'current': 4, 'temporary': 1, 'preferred': 2.

The device for the release in the install. If the device is flash the file for the release is given in instRelName. Devices none(1) or flash(3) are invalid for the default(3) release. Enumeration: 'none': 1, 'flash': 3, 'eprom': 2.

The file name for the release in the install, if the instRelDevice is flash(3). If the instRelDevice is none(1) or eprom(2), this object should be a null string.

The major release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is a.

The minor release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is b.

The device for the patch in the install. The file for the patch is given in instPatName unless the device is none(1). Enumeration: 'none': 1, 'flash': 3, 'nvs': 4.

The file name for the patch in the install.

The interim release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is c. If the release number is a.b, the interim release number is 0.

Indicates if the release file exists or not. true(1) means it exists, false(2) means it doesn't. Enumeration: 'false': 2, 'true': 1.

Indicates if the patch file exists or not. true(1) means it exists, false(2) means it doesn't Enumeration: 'false': 2, 'true': 1.

The table of descriptions of events in the install history of the router.

A single line describing part of the install history of the router.

The index of this event in the install history. Indices run from 1 to the maximum number. The maximum number is not available as a managed object so this table will have to be traversed in order to find out how large it is.

A line of text describing a single event in the install history of the router.

The name of the file that the router will configure from at boot. The format of the name is the same as that for fileName described above. If the configuration file name is a zero length string, then there is no configuration file defined in the router.

The list of release licences in the router.

An entry in the list of release licences.

A unique licence index. Licence indices are recalculated every time the router reboots to reflect the current licences on the router. As licences are added, new indices are allocated to the new licences.

The status of the file. When read, this object will always return a value of ok(1), since the object will not exist if the value is deleting(2). Write the value deleting(2) to this object to delete the file. Enumeration: 'deleting': 2, 'ok': 1.

The file name for the release whose licence this is.

The major release number for the release whose licence this is.

The minor release number for the release whose licence this is.

The password for this release. The password is a string of hex digits.

A human-readable string that gives the expiry date of this licence.

The interim release number for the release whose licence this is.

The name of a file to create containing the current router configuration. A read from this variable will return the same as the variable configFile. Thus to save the current configuration in the current configuration file, read createConfigFile first, then write the result back to createConfigFile. If this variable is written with the name of an existing file, the file will be replaced with the current configuration.

Indicates if the boot configuration file exists or not. true(1) means it exists, false(2) means it doesn't Enumeration: 'false': 2, 'true': 1.

The name of the file that the router is currently configured with. The format of the name is the same as that for fileName described above. If the current configuration file name is a zero length string, then there is no current configuration file defined in the router.

The trigger number of the most recent trigger activated on this router. This is also the variable sent in the trigger trap below. If no triggers have been activated yet since the last restart of this router, this variable will read as 0.

A list of all the files in the router's non-volatile storage.

An entry in the list of files containing information about a single file in the router.

A unique file index. File indices are recalculated every time the router reboots to reflect the current files on the router. As files are added, new indices are allocated to the new files.

The name of the file, in the form . The name is up to eight characters long, the type is up to three characters long.

The device on which the file resides. Enumeration: 'flash': 1, 'nvs': 2.

The creation date and time for the file, in the format .

The status of the file. When read, this object will always return a value of ok(1), since the object will not exist if the value is deleting(2). Write the value deleting(2) to this object to delete the file. Enumeration: 'deleting': 2, 'ok': 1.

The size, in bytes, of the file.

The total number of files in FLASH and NVS.

The table of ping parameters, dynamic and static.

A single entry of ping parameters. This contains the parameters required to perform a ping from the router. The ping specified by the dynamic parameters, can be initiated or stopped at any time by altering the pingStatus accordingly.

There are two sets of ping information, dynamic and static. The dynamic information is used only once, for the next ping, then automatically replaced with the static information. The static information is used whenever specific dynamic information is not specified. The dynamic information indicates the current ping parameters when a ping is in progress. If static information is not specified, defaults are used. Static information can be changed at any time, but dynamic information cannot be changed while a ping is in progress. A change to the static information when a ping is not currently active, also updates the dynamic information. Enumeration: 'dynamic': 2, 'static': 1.

The protocol that the ping will use. The protocol must match the destination address. Ping supports both IP, IPX, Appletalk, and OSI addresses. The protocol must be specified before the address is set, because when the protocol is changed, address is reset to undefined. The default value for this variable is undefined(0). Enumeration: 'osi': 4, 'ip': 2, 'ipx': 3, 'undefined': 0, 'apple': 1.

The address specifies the destination address for ping packets for Appletalk, IP, IPX and OSI networks, respectively. The address format must match the protocol being used. The protocol must be specified before the address is set, because changing the protocol resets the address to undefined. The default value for this variable is an undefined address which is coded as a zero length octet string.

The number of ping packets to transmit.

The packet size parameter specifies the length in bytes, of data to include in the data portion of the ping packet. The protocol packet header size and the size of headers for the particular link protocol in use have to be added to the packet size to get the total size of the ping packet. The maximum pingPacketSize can be set to is 1500.

Timeout specifies the amount of time to wait for a response to a ping packet. Timeout must be greater than zero.

The delay parameter specifies the time interval, in seconds, between ping packets.

Specifies whether a trap should be issued on completion of the sequence of pings. Enumeration: 'false': 2, 'true': 1.

The Type Of Service (TOS) parameter is only valid for IP addresses, and specifies the TOS field in the IP header of the ping packet, as a decimal in the range 0 to 255.

The pattern parameter specifies the data pattern to use in the data portion of the ping packet.

Status and action object for the ping module. A status of '1' indicates that the ping is currently running, the status can be set to '2' to stop the ping. A status of '2' indicates that the ping is currently stopped, the pingStatus can be set to '1' to start the ping. The parameters for the ping can be altered in the pingTable. The destination ping address and protocol have defaults of undefined and must be specified before a ping can be started. The ping statistics are reset to defaults when a ping is started, and updated when the ping stops. Dynamic pingTable information is used only once, for the next ping. Static pingTable information is used for all pings by default, whenever the respective dynamic settings are not specified. Enumeration: 'stop-stopped': 2, 'start-running': 1.

The number of ping packets sent to the target in the last ping. The default before the completion of a ping is zero.

The number of packets received from the target in the last ping. The default before the completion of a ping is zero.

The quickest round trip time taken by any of the ping packets in milliseconds in the last ping. The default before the completion of a ping is negative one.

The average round trip time taken by the ping packets in milliseconds in the last ping. The default before the completion of a ping is zero.

The slowest round trip time taken by any of the ping packets in milliseconds in the last ping. The default before the completion of a ping is zero.

The table of DHCP ranges.

A single entry of the DHCP range table. This contains information about a single DHCP range configured on this device.

The index of this DHCP range. DHCP ranges are stored in a list which is ordered by range name. The index gives the place in the list. Note that if ranges are added or deleted, the index for a given range will change. Since this table is read-only, this will not have an undue effect, but if in future this table is made read-write, a mechanism will have to be created to lock the indices of the range table while SET operations are proceeding.

The name given to identify this DHCP range. This is the ultimate method for uniquely identifying this range. Names are compared without regard to case, for example >range1< will be treated as the same as >RANGE1<.

The base address of this range. This address defines the lower bound of the range of IP addresses which can be allocated to devices requesting an IP address via DHCP.

The number of IP address in this range. This number defines the upper bound of the range of IP addresses which can be allocated to devices requesting an IP address via DHCP.

The IP address of the BOOTP relay agent which will be relaying DHCP requests for this range. If this address is 0.0.0.0, then there will be no BOOTP relay agent and the range will be allocated to devices directly connected to this device.

Whenever a DHCP client attempts to lease an IP address and the DHCP server cannot provide an address, this variable is set to the gateway address of the DHCP request. The gateway address is the IP address of the gateway acting as a BOOTP relay agent for the request. If there is no gateway, the address will be 0.0.0.0. If the gateway address is non-zero, the DHCP range from which the allocation should have been made will able to be identified by lookup in the DHCP range table.

Whenever a DHCP client attempts to lease an IP address and the DHCP server cannot provide an address, this variable is set to the IP address of the interface which received the DHCP request. If the gateway address associated with the failed DHCP request is 0.0.0.0, the interface address will be able to be used to lookup the range that was exhausted and from which the allocation should have been made.

The table of defined DHCP range client addresses.

A single entry of the DHCP range client table. This contains information about a single DHCP range client address.

An IP address from the range of available addresses.

The hardware address of the client, if any, that has been assigned the IP address.

The state of the IP address; one of unused, inuse or reclaim. Enumeration: 'unused': 0, 'offered': 3, 'reclaiming': 1, 'inuse': 2.

The type of allocation mechanism applied to the IP address; one of static, auto or dyn. Enumeration: 'auto': 1, 'dyn': 2, 'static': 3.

The expiry date for dynamically allocated IP address.

The last message sent in a firewall TRAP. This variable is really just a placeholder for the object sent in the firewall TRAP, but can be read independently if required. Note however that a new TRAP will cause this variable to be overwritten.

Table of port properties.

An entry in the port information table.

This object identifies the port of the switch.

The Ingress Bandwidth Limit applied to the port. A value of zero indicates that no limit is set.

The Egress Bandwidth Limit applied to the port. A value of zero indicates that no limit is set.

Table of swi56xx port counter properties.

An entry in the port information table.

This object identifies the port of the switch.

The number of 64kB packets received and transmitted.

The number of 65kB To 127kB packets received and transmitted.

The number of 128kB To 255kB packets received and transmitted.

The number of 256kB To 511kB packets received and transmitted.

The number of 512kB To 1023kB packets received and transmitted.

The number of 1024kB To MaxPktSz packets received and transmitted.

The number of 519kB To 1522kB packets received and transmitted.

The number of octets received.

The number of packets received.

The number of frames received containing a Frame Check Sequence error.

The number of multicast packets received.

The number of broadcast packets received.

The number of valid PAUSE MAC Control frames received.

The number of oversize packets received.

The number of fragments received.

The number of jabber frames received.

The number of MAC Control frames (Pause and Unsupported) received.

The number of MAC Control frames with unsupported opcode (i.e. not Pause) received.

The number of frames with alignment errors received.

The number of packets with length out of range received.

The number of frames with invalid data symbols received.

The number of false carrier conditions between frames received.

The number of undersized packets received.

swiPortRxIpInHdrErrors

The number of octets transmitted.

The number of packets transmitted.

The number of frames containing a Frame Check Sequence error transmitted.

The number of multicast packets transmitted.

The number of broadcast packets transmitted.

The number of valid PAUSE MAC Control frames transmitted.

The number of oversize packets transmitted.

The number of fragments transmitted.

The number of jabber frames transmitted.

The number of Pause control frames transmitted.

The number of frames deferred once before successful transmission.

The number of frame aborted after too many deferrals.

The number of frames which experienced exactly one collision.

The number of frames which experienced 2 to 15 collisions (including late collisions).

The number of frames which experienced late collisions.

The number of frames aborted before transmission after 16 collisions.

The total number of collisions.

The number of packets discarded at ingress port.

The number of VLAN tagged packets transmitted.

The number of Layer 2 and 3 packets aborted during transmission.

Number of multicast TTL expired frames.

Number of multicast bridged frames

Number of multicast frames dropped at reception

NNumber of multicast frames dropped at transmission

For switches based on certain switch chips, the number of parity errors that have been detected in packet memory associated with the switch. If the device does not include the counting of memory parity errors, this variable will return 0.

General configuration and status of all of the virtual balancers configured on the router.

An entry in the global table.

The index for the global table.

The length of time in seconds that a resource can be associated to a source IP address or Cookie after the connection has been closed.

The length of time in seconds that a connection can exist without having any data traversing it, before being declared an orphan and closed by the router.

The ratio of total messages received from a resource that can be TCP RST messages represented as a percentage.

The total number of resources configured on the router.

The total number of resource pools configured on the router.

The total number of virtual balancers configured on the router.

Displays the current total number of connections to all resources in every resource pool on the router.

A list about the general information about for a given resource.

An entry in the resource table.

The index for the resource table.

The name of the resource.

The IP address that a virtual balancer uses to accesses the resource.

The port that the service that the resource offer is accessed on.

The current state of the resource, either UP, DOWN, or CLOSING.

The weight that the virtual balancer will apply to the resource when selecting resources to try a connection to from a resource pool using either the WEIGHTEDLEASTCONNECT or WEIGHTEDLOTTERY selection algorithms.

The total number of successful connections that have been made to this resource while it has been in the UP state.

The total number of connections currently made to the resource.

A list about the general information about for a given resource pool.

An entry in the resource pool table.

The index for the resource pool table.

The index for the resource table.

The name of the resource pool.

The selection algorithm that ius employed by this resource pool when a resource has been selected for a connection. The options are ROUNDROBIN, WEIGHTEDLEASTCONNECT, WEIGHTEDLOTTERY and FASTESTRESPONSE.

Indicates whether or not the resource pool will fail a resource if it is the last resource in the resource pool.

The total number of successful connections that have been made to the resources in the resource pool over the lifetime of the resource pool.

The name of the resource that is currently allocated to the resource pool.

A list about the general information about for a given virtual balancer.

An entry in the virtual balancer table.

The index for the virtual balancer table.

The name of the virtual balancer.

The IP address on which the virtual balancer will receive requests for the service provided by the resource pool associated with it.

The port on which the virtual balancer will receive requests for the service provided by the resource pool associated with it.

The current state of the virtual balancer, can either be UP, CLOSING, or DOWN.

The name of the resource pool that is associated with the virtual balancer.

The type of load balancer that this virtual balancer currently is, can be either TCP, HTTP, or ROUTE.

The total number of stateful connections currently running through this virtual balancer.

Indicates whether or not entries will be made in a virtual balancers' affinity table for each stateful connection to a resource in its' resource pool (TCP and ROUTE type) or for cookies received from clients (HTTP type).

A list of the HTTP server error status code added.

A list of affinity tables for all configured virtual balancers on the router.

An entry in the affinity table.

The index for the affinity table.

The name of the virtual balancer whose affinity table is being displayed.

The IP address that has affinity to the given resource.

The cookie that has affinity to the given resource.

The name of the resource that the Client IP/Cookie has an affinity for.

The amount of seconds left before this entry expires, and is removed from the affinity table.

A list about all of the TCP connections currently open to a given virtual balancer.

An entry in the connections table.

The index for the connections table.

The name of the virtual balancer the listed connections are to.

The IP address of that originated the connection.

The port on the originating system that represents the other end of the connection.

The name of the resource that the connection has been made to.

The ATR enterprise DS3 trap table.

An entry in the ATR enterprise DS3 trap table.

Indicates whether the threshold crossing alert traps should be generated for this interface. Enumeration: 'disabled': 2, 'enabled': 1.

This variable shows which kind of parameter or primitive caused the trap. This variable is really just a placeholder for the object sent in the DS3 TRAP, but can be read independently if required. The variable will hold the value at the latest trap. A value of ds3NoError shows no trap has occured Enumeration: 'ds3UAS': 5, 'ds3PSES': 3, 'ds3NoError': 1, 'ds3PCVs': 7, 'ds3CCVs': 9, 'ds3CESs': 10, 'ds3SEFs': 4, 'ds3PES': 2, 'ds3LESs': 8, 'ds3CSESs': 11, 'ds3LCVs': 6.

This variable shows whether the trap was caused by a problem at the local or remote end. This variable is really just a placeholder for the object sent in the DS3 TRAP, but can be read independently if required. The variable will hold the value at the latest trap. A value of ds3NoLoc shows no trap had occured. Enumeration: 'ds3NoLoc': 1, 'ds3Near': 2, 'ds3Far': 3.

This variable shows whether the counter which has crossed the threshold is a twenty four hour or fifteen minute counter. This variable is really just a placeholder for the object sent in the DS3 TRAP, but can be read independently if required. The variable will hold the value at the latest trap. A value of ds3NoInt shows no trap has occured. Enumeration: 'ds3Fifteen': 2, 'ds3Twentyfour': 3, 'ds3NoInt': 1.

A flash failure trap is generated when any of the above flash counter is incremented and the failure type is sent in the trap.

This trap is generated when the boot file is detected as missing

A trigger trap is generated a trigger is activated. The number of the trigger activated is given by the variable triggerLastTriggerActivated.

A ping trap is generated when a ping has completed. Traps are only generated if the variable pingTrapOnCompletion is set to true(1) in the dynamic ping entry. A trap is still generated if the ping is stopped prematurely by setting the variable pingStatus to stop/stopped(2).

This trap is generated when a DHCP client makes a request for an IP address and the request cannot be satisfied because all addresses in the range are already allocated to other devices.

A firewall trap is generated when the firewall detects an intrusion or attack and notifies the router manager. Firewall trap notifications are enabled with the command ENABLE FIREWALL NOTIFY=SNMP.

An intrusion detection trap is generated when a port has intrusion detection enabled, and the action taken when intrusion is detected is to generate a trap. Intrusion is detected when the number of MAC addresses learned on the port exceeds the configured learn limit. The ifIndex of the port is included in the trap.

A DS3 trap is generated when a threshold crossing alert occurs. This happens when an error count exceeds a pre determined value. The values are counted over 15 minute and 24 hour periods. Once a trap has occured in a given period it may not occur again within the same period.

The maximum index of boards in the board table. Index 1 is reserved for the main system board of the router.

The table of boards in the AR router.

A single entry in the board table. Each entry consists of information about one board in the router.

The index of the board in the board table. Index 1 is reserved for the main system board of the router. Other boards will take index numbers as they are initialised at router startup, or for routers with hot-swap capability, as boards are added to and removed from the router.

The type of board in this board entry. The values of this object are taken from the pprXxx object IDs under the boards sub-tree.

The name of the board in this board entry. This is a readable string which identifies the board to the manager.

The manufacturing revision of the board in this board entry. This string has the format Xm-n, where X is P for prototype, or M for manufacturing, m is the major revision number for this board, and n is the field upgrade revision number for this board.

The serial number of the board in this board entry. Serial numbers are strings of decimal numbers up to 10 digits in length. Each and every serial number is globally unique. It is possible for the serial number of a board to be invalid. In this case the value returned for this object will be '*** Invalid ***'

The number of slots on this board. Each slot from 1 to the value of this object may be empty or occupied by another board. By searching the arSlotTable with this board's board index and all values of slot index from 1 to the value of this object, a tree of the boards in this router can be built. The value 0 for this object means that it has no slots.

The number of positions on this board. Each position from 1 to the value of this object contains a single router interface. Note that positions are different from slots. An position contains an actual interface while a slot contains a different board which itself may contain interfaces in its positions.

The table of slots in the router, indexed by board index and slot index.

A single entry in the board slot table.

The index of the board for this slot entry. Index 1 is reserved for the main system board of the router.

The index of the slot for this slot entry. Indices start from 1 and are specific to each different board type. There are no gaps in the sequence of slot indices. The maximum value for slot index is given by the value of arBoardTotalSlots for this board.

The index of the board held in the slot for this slot entry. This is an index into the arBoardTable. A value of 0 for this object means that the slot is not populated.

A description for this slot entry. This is a textual description which gives the manager a clue as to what the slot for this entry is. For example, the slots on an AR 720 have descriptions 'Bay0', 'Bay1' and 'MAC'.

The table of physical interfaces in the AR router.

A single entry in the interface table. Each entry consists of information about one interface in the router, and is indexed by the board index and the position of the interface on the board.

The index of the board in the board table which contains this interface. Index 1 is reserved for the main system board of the router.

The position of the interface on the board. Each board type will have well-known positions which are the interfaces provided by the board. The number of positions on a given board is given by the object arBoardTotalPositions for this board.

The ifIndex for the interface represented by this entry of the interfaces table. This is the ifIndex of the ifEntry used to represent the physical interface. The value 0 is used for interfaces which don't have an ifIndex.

The name of this interface. This is the name that the manager can use to refer to this interface in entering router commands.

The fully qualified name for this interface. This identifies the path that must be followed to reach the interface. This name can be used in router commands. In routers don't support fully qualified names, this is the same as arInterfaceName.

The table of interface statistics for the AR router. This table extends the ifTable.

A single entry in the interface extension table. Each entry consists of extra interface information not covered in standard MIBs. The index for this table is ifIndex, the same as for ifTable.

The index of the ifTable.

The average number of bits received per second on all interfaces over the past 8.5 minutes. The average is calculated by an 8.5 minute (512s) decaying average, which is updated every 4 seconds using the following formula: X' = 127/128X + 1/128i where X' is the new average X is the old average i is the most recent poll result The times and multiplier factors have been chosen to give the simplest possible calculation using bit shifting operations.

The average number of packets received per second on all interfaces over the past 8.5 minutes. See the description for arIfXAverageInputBitsSecond for details of the way in which the average is calculated.

The average number of bits sent per second on all interfaces over the past 8.5 minutes. See the description for arIfXAverageInputBitsSecond for details of the way in which the average is calculated.

The average number of bits sent per second on all interfaces over the past 8.5 minutes. See the description for arIfXAverageInputBitsSecond for details of the way in which the average is calculated.