SMP Source and Destination
Table 27-1 on page 774 defines who originates various types of SMPs and who acts as the destination. Upon receipt of an SMP packet, the combination of the method and the attribute defines to whom the packet should be delivered for processing.
| Method/Attribute | Sourced by | Method Value | Destination | Comments |
|---|---|---|---|---|
| SubnGet(attribute) | SM | 01h | SMA | The SM has issued an attribute read (of an attribute other than SMInfo) to the destination device's SMA. |
| SubnGet(SMInfo) | SM | 01h | SM | A SM has issued a request to read another SM's SMInfo attribute. |
| SubnSet(attribute) | SM | 02h | SMA | The SM has issued an attribute write (to an attribute other than SMInfo) to the destination device's SMA. |
| SubnSet(SMInfo) | SM | 02h | SM | A SM has issued a request to write to another SM's SMInfo attribute. |
| SubnGetResp(attribute) | SMA | 81h | SM | A device's SMA has issued a response packet to a SM's Get() or Set() request packet. |
| SubnGetResp(SMInfo) | SM | 81h | SM | A SM has issued a response to another SM's Get(SMInfo) or Set(SMInfo) request packet. |
| SubnTrap(Notice) | SMA | 05h | SM | A device's SMA has issued a Trap() to inform the SM of an internal event. |
| SubnTrapRepress(Notice) | SM | 07h | SMA | In response to the receipt of repetitive identical SubnTrap(Notice) packets from a device, the SM has issued a TrapRepress(Notice) packet to that device's SMA. |
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.