26.09.2014 Views

ASF Specification v2.0 DSP0136 - DMTF

ASF Specification v2.0 DSP0136 - DMTF

ASF Specification v2.0 DSP0136 - DMTF

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Alert Standard Format (<strong>ASF</strong>) <strong>Specification</strong> <strong>v2.0</strong><br />

<strong>DMTF</strong> Document <strong>DSP0136</strong><br />

2. The managed client responds with an RMCP ACK, returning only an RMCP Header. Note<br />

that all values are copied from the “Request” message’s RMCP header, with the “ACK” bit set<br />

in the fourth byte.<br />

RMCP Header<br />

Vers Rsvd Seq# Class<br />

06h 00h 05h 86h<br />

3. The managed client responds with the associated <strong>ASF</strong>-RMCP “Response”. Note that the<br />

Message Tag value (08h) is copied from the “Request” message.<br />

RMCP Header<br />

<strong>ASF</strong>-RMCP Data<br />

Vers Rsvd Seq# Class IANA Enterprise Number Type Tag Rsvd Len<br />

06h 00h 09h 06h 00h 00h 11h BEh xx 08h xx xx<br />

4. The management console, having received both the ACK and “Response” sends an RMCP<br />

ACK, completing the request/response cycle. The RMCP Header is copied from the<br />

managed client’s “Response” message, with the “ACK” bit set in byte 4.<br />

RMCP Header<br />

Vers Rsvd Seq# Class<br />

06h 00h 09h 86h<br />

Interactions with some packet loss<br />

1. The description that follows illustrates the RMCP Header and RMCP Data fields in a consoleto-client<br />

communication where some of the messages are lost. The management console<br />

sends an <strong>ASF</strong>-RMCP “Request” message<br />

RMCP Header<br />

<strong>ASF</strong>-RMCP Data<br />

Vers Rsvd Seq# Class IANA Enterprise Number Type Tag Rsvd Len<br />

06h 00h 05h 06h 00h 00h 11h BEh xx 08h xx xx<br />

2. The management console waits to receive an ACK from the client, but the client never<br />

received that “Request” message; the console re-transmits the “Request” message with the<br />

same Sequence Number as the original message in step 1.<br />

RMCP Header<br />

<strong>ASF</strong>-RMCP Data<br />

Vers Rsvd Seq# Class IANA Enterprise Number Type Tag Rsvd Len<br />

06h 00h 05h 06h 00h 00h 11h BEh xx 08h xx xx<br />

3. The managed client responds with an RMCP ACK, returning only an RMCP Header. Note<br />

that all values are copied from the “Request” message’s RMCP header, with the “ACK” bit set<br />

in the fourth byte. The console never receives this ACK.<br />

RMCP Header<br />

Vers Rsvd Seq# Class<br />

06h 00h 05h 86h<br />

4. The managed client responds with the associated <strong>ASF</strong>-RMCP “Response”. Note that the<br />

Message Tag value (08h) is copied from the “Request” message.<br />

RMCP Header<br />

<strong>ASF</strong>-RMCP Data<br />

Vers Rsvd Seq# Class IANA Enterprise Number Type Tag Rsvd Len<br />

06h 00h 09h 06h 00h 00h 11h BEh xx 08h xx xx<br />

<strong>DSP0136</strong> 23 April 2003 Page 45 of 94

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!