Contents
Nomad status messages
- 0x0000000001 – SNO_EVT_START
- 0x0000000002 – SNO_EVT_STOP
- 0x0000000004 – SNO_EVT_ERROR
- 0x0000000008 – SNO_EVT_PAUSED
- 0x0000000010 – SNO_EVT_RESUMED
- 0x0000000020 – SNO_EVT_REQUEST_STARTED
- 0x0000000040 – SNO_EVT_REQUEST_COMPLETED
- 0x0000000080 – SNO_EVT_SERVICE_RESET
- 0x0000000100 – SNO_EVT_STARTED_CACHE_MANAGEMENT
- 0x0000000200 – SNO_EVT_FINISHED_CACHE_MANAGEMENT
- 0x0000000400 – SNO_EVT_STARTED_HASHCHECK
- 0x0000000800 – SNO_EVT_FINISHED_HASHCHECK
- 0x0000001000 – SNO_EVT_ELECTION_REQUEST
- 0x0000002000 – SNO_EVT_MASTER_CHANGED
- 0x0000004000 – SNO_EVT_FILLIN_MASTER_CHANGED
- 0x0000008000 – SNO_EVT_MCAST_CENTRALSCHED
- 0x0000010000 – SNO_EVT_MCAST_ERROR
- 0x0000020000 – SNO_EVT_MCAST_COMPLETE
- 0x0000040000 – SNO_EVT_SCHEDULER
- 0x0000080000 – SNO_EVT_STARTED_TX_CENTRALMCAST
- 0x0000100000 – SNO_EVT_STOPPED_TX_CENTRALMCAST
- 0x0000200000 – SNO_EVT_STARTED_TX_ACTIVEMCAST
- 0x0000400000 – SNO_EVT_STOPPED_TX_ACTIVEMCAST
- 0x0000800000 – SNO_EVT_STARTED_TX_FILLINMCAST
- 0x0001000000 – SNO_EVT_STOPPED_TX_FILLINMCAST
- 0x0002000000 – SNO_EVT_STARTED_RX_CENTRALMCAST
- 0x0004000000 – SNO_EVT_STOPPED_RX_CENTRALMCAST
- 0x0008000000 – SNO_EVT_STARTED_RX_ACTIVEMCAST
- 0x0010000000 – SNO_EVT_STOPPED_RX_ACTIVEMCAST
- 0x0020000000 – SNO_EVT_STARTED_RX_FILLINMCAST
- 0x0040000000 – SNO_EVT_STOPPED_RX_FILLINMCAST
- 0x0080000000 – SNO_EVT_STARTED_COPY
- 0x0100000000 – SNO_EVT_STOPPED_COPY
- 0x0200000000 – SNO_EVT_WORKRATE_CHANGED
- 0x0400000000 – SNO_EVT_WRONG_PKG_VERSION
- 0x0800000000 – SNO_EVT_INFORMATIONAL
- 0x1000000000 – SNO_EVT_FINALSTATS (see notes below)
- 0x2000000000 – SNO_EVT_WAIT
- 0x4000000000 – SNO_EVT_MAX_EVENTID
SNO_EVT_FINALSTATS notes
For success reporting, this message provides feedback on the status of the download. For example, it can show how much data was received using multicast as opposed to peer-to-peer copying. Turning this message on creates an extra status message per machine for each deployment. The format of the status message is:
Evt_FinalStats MD100067 1 170 59195038 170 59195038 0 59195038 0 0
Configuration Manager status messages are made up of insertion strings. The strings for the final stats event are:
InstrStr0 | Nomad event string (internal reference) | N/A |
InstrStr1 | Package Id and Package version | MD100067 1 |
InstrStr2 | Total number of files in package | 170 |
InstrStr3 | Total number of package bytes | 59195038 |
InstrStr4 | Number of files which are cached | 170 |
InstrStr5 | Bytes which are cached | 59195038 |
InstrStr6 | Bytes coped from a peer agent (P2P) | 0 |
InstrStr7 | Bytes copied from the DP | 59195038 |
InstrStr8 | Bytes received via local multicast | 0 |
InstrStr9 | Bytes received from a central multicast | 0 |
If the package is already cached and is re-deployed with an unchanged package version, the final stats message will not be re-sent.
Status messages for the Nomad Dashboard
Nomad clients must be configured to return the following status messages into the Configuration Manager site database in order to populate the Nomad dashboard's Latest Operations tiles. Because the Nomad client does not return any status messages by default, you must configure the Nomad client registry StatusMsgEvents value, either during installation of 1E Client or using The Nomad Baseline Wizard.
SNO_EVT_ERROR (0x0000000004)
SNO_EVT_REQUEST_STARTED (0x0000000020)
SNO_EVT_REQUEST_COMPLETED (0x0000000040)
SNO_EVT_FINALSTATS (0x1000000000)
These combine to the following value: 0x1000000064