FSCSERIAL-TRAP-MIB: View SNMP OID List / Download MIB

This object is sent in a trap to identify the name of the user for which the trap condition occurred.

This object is sent in a trap to identify the name of the target user for which a trap condition occurred.

This object is sent in a trap to identify the type of software image for which the trap condition occurred. Enumeration: 'app': 2, 'boot': 1.

This object is sent in a trap to identify the version of the new software image the appliance is being upgraded to.

This object is sent in a trap to identify the version of the software image that the appliance is currently running.

This object contains the results of a software image upgrade.

This object is sent in a trap to identify a cry for help string that was detected on a serial port.

This object is sent in a trap to identify the serial port number associated with a serial session for which the trap condition occurred.

This object is sent in a trap to identify the serial port number for which the trap condition occurred.

This object is sent in a trap to identify the name of a file for which the trap condition occurred.

This object is sent in a trap to identify the SPC Location Name for which the trap condition occurred.

This object is sent in a trap to identify the appliance port that the SPC is attached to for which the trap condition occurred.

This object is sent in a trap to identify the Login Name for which the trap condition occurred.

This object is sent in a trap to identify the SPC socket number for which the trap condition occurred.

This object is sent in a trap to explain the reason for which a user account has been locked. Enumeration: 'consecutiveAuthenticationFailures': 1, 'administrative': 2.

This object is sent in a trap to explain the reason for which a user account has been unlocked. Enumeration: 'administrative': 2, 'lockoutExpired': 1, 'reboot': 3.

This object is sent in a trap to indicate the IP address of a user session that has caused the trap.

This object is sent in a trap to report server session status changes and power status changes. This object will report the status for all connection paths known to the appliance in an aggregated encoding format as indicated below. The information for each connection path is packed into four bytes as follows: Byte 1 = The serial port number associated with this path. Byte 2 = The enumerated socket number of the SPC cascade device associated with this connection path. The value will be 0 if an SPC socket is not associated with this connection path. The socket number enumeration will use this convention: A1 = 1 C1 = 9 A2 = 2 C2 = 10 A3 = 3 C3 = 11 A4 = 4 C4 = 12 B1 = 5 D1 = 13 B2 = 6 D2 = 14 B3 = 7 D3 = 15 B4 = 8 D4 = 16 No SPC attached = 0 Byte 3 = The power status of a connected server or the power status of an SPC socket. One of the following values can be reported: 1 = unknown - unable to determine the power status. 2 = on - the server or the SPC socket is powered on. 3 = off - the server or the SPC socket is powered off. Byte 4 = The serial session status. One of the following values can be reported: 1 = N/A - not applicable when an SPC is attached. 2 = Idle - there is no active viewer session on this path. 3 = Active - there is an active viewer session currently on this path. Each connection path will be packed into this object in four byte increments one after the other. The connection paths do not have to be packed in any specific order. Note that the size of this object could conceivably be as large as shown in the following calculation assuming a 16 socket SPC were connected to each serial port of the appliance: 48 ports X 16 sockets X 4 bytes = 3072 bytes.

This object is sent in a trap to identify the name of the server for which the trap condition occurred. The value of this object comes from an instance of the Port Table Name object. If this object is reported in a trap that is specific to a serial port on the appliance then the value of this object will be the same as the serial port's Port Table Name.

This object is sent in a trap to identify the reason for the error encountered. In case of no error being reported, this object will have a value of 9999 (no error). If an error is being reported (the value is non-zero), then, depending on the error, the fscSerialTrapObjectNFSSecErrorReason may also have a non-zero value (and thereby provide additional information about the error), or the fscSerialTrapObjectNFSPriErrorReason may have a value of 0 (if no more detail is available for the error).

This object is sent in a trap to identify the reason for the error encountered. In case of no error being reported, this object will have a value of 9999 (no error). If an error is being reported (i.e the value of fscSerialTrapObjectNFSPriErrorReason is non-zero), then depending on the error the fscSerialTrapObjectNFSSecErrorReason may also have a non-zero value (and thereby provide additional information about the error), or the fscSerialTrapObjectNFSPriErrorReason may have a value of 0 (if no more detail is available for the error).

This object is sent in a trap to identify the error status on the specified port.

The appliance is in the process of rebooting. The name of the user who initiated the reboot is contained in fscSerialTrapObjectUserName.

A user logged into the appliance. This trap is sent when a user logs into the CLI port or when a user exits a serial session. The name of the user who logged in is contained in fscSerialTrapObjectUserName.

A user logged out of the appliance. This trap is sent when a user logs out of the CLI port or when a user exits a serial session. The name of the user who logged out is contained in fscSerialTrapObjectUserName.

A serial session has started. The name of the user who is connected to the session is contained in fscSerialTrapObjectUserName. The port number on the appliance that the session is using is contained in fscSerialTrapObjectSessionIdentifier. The port name on the appliance that the session is using is contained in fscSerialTrapObjectServerName.

A serial session has stoppped. The name of the user who was connected to the session is contained in fscSerialTrapObjectUserName. The port number on the appliance that the session was using is contained in fscSerialTrapObjectSessionIdentifier. The name of the server the user was connected to is contained in fscSerialTrapObjectServerName.

A serial session has been terminated or preempted by another user. The name of the user who terminated or preempted the session is contained in fscSerialTrapObjectUserName. The name of the user who was terminated or preempted from the session is contained in fscSerialTrapObjectTargetUserName. The port number on the appliance that the session was using is contained in fscSerialTrapObjectSessionIdentifier. The name of the server the user was connected to is contained in fscSerialTrapObjectServerName.

The appliance has started an upgrade of a software image. The name of the user who initiated the image upgrade is contained in fscSerialTrapObjectUserName. The type of image that is being upgraded is contained in fscSerialTrapObjectImageType. The version of the image that the appliance is upgrading to is contained in fscSerialTrapObjectImageNewVersion. The version of the image that the appliance is currently running is contained in fscSerialTrapObjectImageCurrentVersion.

This object contains the results of the upgrade of a software image. The result is contained in fscSerialTrapObjectImageUpgradeResults. The type of software image the upgrade result is for is contained in fscSerialTrapObjectImageType.

A new user has been added to the local user database. The name of the user who added the new user is contained in fscSerialTrapObjectUserName. The name of the new user is contained in fscSerialTrapObjectTargetUserName.

A user has been deleted from the local user database. The name of the user who deleted the user is contained in fscSerialTrapObjectUserName. The name of the user who was deleted is contained in fscSerialTrapObjectTargetUserName.

A user was modified. The the name of the user who modified the user is contain in fscSerialTrapObjectUserName. The name of the user who was modified is contained in fscSerialTrapObjectTargetUserName.

A user failed to authenticate with the appliance. The name of the user who failed to authenticate is contained in fscSerialTrapObjectUserName.

The appliance has been commanded to set itself to factory defaults. The appliance sends this trap after being commanded to set itself to factory defaults but prior to actually reverting to factory defaults.

The appliance detected a cry for help string on a serial port. The serial port number the cry for help string was detected on is contained in fscSerialTrapObjectPortNumber. The cry for help string that was detected is contained in fscSerialTrapObjectPortAlertString. The serial port name the cry for help string was detected on is contained in fscSerialTrapObjectServerName.

The appliance has loaded a configuration file. The name of the user who commanded the appliance to load the configuration file is contained in fscSerialTrapObjectUserName. The name of the file that was loaded is contained in fscSerialTrapObjectFileName.

The appliance has loaded a user database file. The name of the user who commanded the appliance to load the user database file is contained in fscSerialTrapObjectUserName. The name of the file that was loaded is contained in fscSerialTrapObjectFileName.

The appliance monitor has detected that the power on/off control signal is high on a serial port indicating that the server attached to the port is powered on. This trap is sent on initialization if the condition is detected. Subsequent traps occur only if there is a transition of this signal from low to high. The affected port number is contained in fscSerialTrapObjectPortNumber. The name of the server connected to the serial port is contained in fscSerialTrapObjectServerName.

The appliance monitor has detected that the power on/off control signal is low on a serial port indicating that server attached to the port is powered off. This trap is sent on initialization if the condition is detected. Subsequent traps occur only if there is a transition of this signal from high to low. The affected port number is contained in fscSerialTrapObjectPortNumber. The name of the server connected to the serial port is contained in fscSerialTrapObjectServerName.

A user account has been locked. The IP address of the client from which the last connection was attempted is contained in fscSerialTrapObjectIPAddress. If 0.0.0.0, then the user was locked attempting to authentication from the local Serial CLI. The name of the user who was locked is contained in fscSerialTrapObjectTargetUserName. The reason for which the user account has been locked is contained in fscSerialTrapObjectLockReason.

A user account has been unlocked. The IP address of the client that originated the unlock request is contained in fscSerialTrapObjectIPAddress. When the user account is unlocked by an appliance reboot or by the expiration of the lockout period (as specified in the fscSerialTrapObjectUnlockReason object), the IP address will be 0.0.0.0. The name of the user who unlocked the user is contained in fscSerialTrapObjectUserName. When the user account is unlocked by an appliance reboot or by the expiration of the lockout period (as specified in the fscSerialTrapObjectUnlockReason object), the name of the user will be blank. The name of the user who was unlocked is contained in fscSerialTrapObjectTargetUserName. The reason for which the user account has been unlocked is contained in fscSerialTrapObjectUnlockReason.

The request to disable NFS was sent. The user that requested NFS disable is contained in fscSerialTrapObjectUserName.

The appliance has completed the disable/unmount NFS. This trap is sent after an NFS Disable request is made and confirms that the unmount operation was successfully completed.

The request to enable NFS was sent. The user that requested NFS enable is contained in fscSerialTrapObjectUserName.

The appliance has completed the enable/mount NFS. This trap is sent after an NFSEnable request is made and confirms that the mount operation was successfully completed.

The appliance has verified that the NFS mount operation succedded.

The first NFS mount attempt failed. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

The final NFS mount attempt failed. No more attempts to mount a NFS will be maid. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

This trap is sent when the NFS mount is lost. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

The first NFS remount attempt failed. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

The final NFS remount attempt failed. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

A request to enable a NFS port was sent. The fscSerialTrapObjectUserName contains the name of the user that requested this operation. The fscSerialTrapObjectPortNumber returns the port number of the NFS port to be enabled.

A request to disable a NFS port was sent. The fscSerialTrapObjectUserName contains the name of the user that requested this operation. The fscSerialTrapObjectPortNumber returns the port number of the NFS port to be disabled.

This trap is sent when a port needs mount. The fscSerialTrapObjectPortNumber returns the port number of the NFS port that needs remount. The fscSerialTrapObjectNFSPortErrStatus returns the status of the port at the time that this trap was generated. The fscSerialTrapObjectNFSErrorReason returns the error codes for this operation.

The first attempt to open a file using the NFS failed. Several attempts will be made until the operation will get canceled. The fscSerialTrapObjectPortNumber returns the port number of the NFS port that failed. The fscSerialTrapObjectNFSPortErrStatus returns the status of the port at the time that this trap was generated. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

The final attempt to open a file using the NFS failed. No more attempts will be made and the operation will be canceled. The fscSerialTrapObjectPortNumber returns the port number of the NFS port that failed. The fscSerialTrapObjectNFSPortErrStatus returns the status of the port at the time that this trap was generated. The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

This trap is sent when an attempt to open a file through NFS is successful. The fscSerialTrapObjectPortNumber returns the port number of the NFS port that was successfully open.

This trap is sent when a write file operation fails. If multiple consecutive write operations fail, this trap is only sent once, upon the occurrence of the first failure. Once sent, this trap will not be sent again until a write operation has been successfully performed, and a period of 15 minutes has elapsed without any additional write operation failures and without any overrun errors. (I.e. This trap is sent only when the status of the port is 'No recent errors.) The port number of the NFS port on which the failure occurred is contained in fscSerialTrapObjectPortNumber. The status of the NFS port on which the failure occurred is contained in fscSerialTrapObjectNFSPortErrStatus. (This is the status of the port at the time that the Trap was generated.) The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

This trap is sent when an overrun occurs when writing to the file. If multiple consecutive overruns occur, this trap is only sent once, upon the occurrence of the first overrun. Once sent, this trap will not be sent again until a write operation has been successfully performed, and a period of 15 minutes has elapsed without any additional overruns or write operation failures. This trap is not sent if the most recent write operation failed or if a write operation failed within the preceding 15 minute period. (I.e. This trap is sent only when the status of the port is 'No recent errors.) The port number of the NFS port on which the failure occurred is contained in fscSerialTrapObjectPortNumber. The status of the NFS port on which the error occurred is contained in fscSerialTrapObjectNFSPortErrStatus. (This is the status of the port at the time that the Trap was generated.) The fscSerialTrapObjectNFSPriErrorReason specifies the main reason of failure and can have any value defined in NFSErrorReasonEnum. The fscSerialTrapObjectNFSSecErrorReason specifies the secondary reason of failure and can have any value defined in NFSErrorReasonEnum or if there is no detailed reason then the value will be zero.

This trap is sent if the status of a port changes to a status of 'No recent errors' from one of the current or recent write and/or overrun error status conditions. The fscSerialTrapObjectPortNumber contains the number of the port that has no errors.

The file open through a NFS port was successfully closed. The fscSerialTrapObjectPortNumber returns the NFS port number where the file was open.