What Events Are Logged?
Field | Description |
|
|
Tx | • Session Disconnect Event: The number of bytes of successfully |
| transmitted user data on this session at the time of session |
| termination. This field will always be zero for MOP remote console |
| connections. |
| • Logout Event: The number of bytes output to the port during the |
| life of the associated login. |
Rx | • Session Disconnect Event: The number of bytes of successfully |
| received user data on this session at the time of session termination. |
| This field will always be zero for MOP remote console |
| connections. |
| • Logout Event: The number of bytes input to the port during the |
| life of the associated login. |
| Subtracting the sum of all the session disconnect Tx/Rx fields during |
| the life of a login from the Tx/Rx values in the logout event will yield |
| the Tx/Rx count of bytes sent and received while the user was in local |
| mode. |
User | This field is a variable length string as follows: |
| • Login Events: When authentication is enabled on the port, this |
| field will contain the entire Kerberos user name string (for example, |
| jones@finance.acme.com). |
| • All Other Events: This field will contain the user name string |
| associated with the port (the string in the first field of the SHOW |
| PORT display). |
| The SET PORT USERNAME command may change a port’s user |
| name from the string stored at login. This can cause entries associated |
| with a particular login to have different user name fields. The login |
| entry, when Kerberos is enabled, is the only trusted source for the |
| user name. |
|
|