ASF Specification v2.0 DSP0136 - DMTF

Alert Standard Format (ASF) Specification v2.0
DMTF Document DSP0136
2) The management console issues an RMCP Capabilities Request message to the managed
client; the client …
a) … acknowledges receipt of the RMCP message, so long as the RMCP version in the
message’s header is a version supported by the client.
b) … responds with a RMCP Capabilities Response message, returning the system
capabilities previously configured into the alert-sending device’s non-volatile storage.
At this point, the management console knows that the managed client is RMCP-aware and which
of the optional RMCP ‘Set’ messages are supported by the client — the client will acknowledge
receipt of any unsupported message, but will disregard the message contents.
3.2.1 RMCP UDP Port Numbers
There are two UDP ports reserved for RMCP. — The port numbers are 026Fh (623 decimal) and
0298h (644 decimal) described as:
Port Usage
026Fh The compatibility port is used for all communications for ASF version 1.0. It is defined as
the compatibility port beginning with ASF version 2.0.
0298h The secure port is used for all communications using the RMCP security extensions.
Refer to section 3.2.3 RMCP Security-Extensions Protocol (RSP) for the definition of the
protocol used on for this port.
3.2.2 For network frames sent to the managed client, each of these ports is a
destination port. For network frames sent by the managed client, each of
these ports is a source port. The source port in the frames sent to the
managed client becomes the destination port in the frames sent by the
managed client. RMCP Message Format
The following table describes the complete network frame — as sent to the managed client —
that includes RMCP, using an 802.3/Ethernet frame as defined by [IEEE 802] as the example.
RMCP is media independent and, depending on the medium, the associated header fields will be
different. All the data fields specified for RMCP messages are in network byte order. This
specification defines the format of the shaded fields in the frame described below.
Within the table that follows, a Contents field that has non-blank Value field defines the method
through which the following frame contents are determined. For example, if the MAC Header’s
Frame Type is set to 0800h then the frame element that follows the MAC Header is an IP Header.
The RMCP message (the shaded area in the table) is divided into two basic components: its
header and its associated data. Interpretation of the RMCP Data format depends on the value
present in the RMCP header’s Class of Message field. While the RMCP header is extensible to
incorporate any OEM-defined variations, this specification defines only the RMCP Data formats
for messages with Class of Message set to ASF (6).
An RMCP message's Data block is also extensible: the IANA Enterprise Number defines the
interpretation of the remaining fields within that block. This specification defines messages and
data formats when the RMCP Data block’s IANA Enterprise Number is set to 4542 (the IANAassigned
value for ASF). Any other value in that field identifies an OEM-specific RMCP message
extension; the Data block’s IANA Enterprise Number is set to the OEM’s IANA-assigned value.
DSP0136 23 April 2003 Page 19 of 94