This object is sent in a trap to report server status changes. This object will report the status change of multiple servers (connection paths) in an aggregated encoding format as indicated below. Note that on bootup the appliance will send this object in the avctDsrServerStatusChangedTrap containing the status of all connection paths in the appliance. Thereafter the appliance will send this object in the avctDsrServerStatusChangedTrap containing only the connection paths whose status has changed. This object is composed of two sections, which are the header section and the connection path section. The header section provides version information and is the first 2 bytes of this object. The connection path section provides information on each of the connection paths and is defined in the bytes following the header. Header Section Byte 1 = Start indicator for the header section. The value of the start indicator is always zero. The value of the start indicator provides means for management applications to determine that this object has a header section. All previous implementations of this object have a non-zero value in the first byte. Byte 2 = Version of the aggregate object. The version provides means to identify the format/structure of this aggregate object. The format of the aggregate object, as described here, is identified with a value of 3 for the version. Connection Path Section The connection path section is composed of 1 or more connection paths. The information for each connection path is packed into 10 bytes as follows: Byte 1 = The appliance input port number associated with this connection path. The input port defined for dsrAggregateServerStatus is an ARI port that interfaces the data traffic coming from or going directly or indirectly to a target device or a power device. Note that a power device will report the port number as 100 + the power device port number (dsrSpcDeviceTablePortNumber). For the first power device port, Byte 1 will report 101 for the power device. This will avoid potential port conflicts for ARI and power device ports. In the event that additional power device ports are available, the number will reflect the power device port number (i.e. 101, 102, etc.) Byte 2 = The cascade switch channel number associated with this connection path. The value will be 0 if a switch channel is not associated with this connection path. For power devices, this Byte will represent the power device number (dsrSpcDeviceTableSpcNumber). Byte 3 will contain the socket number for this connection path. Byte 3 ~ 8 = The EID of the RIP associated with this connection path. Each byte in this field will encode two digits of the RIP's EID number. For example, if the actual EID number on the label attached to a RIP is 520255-0346DC then bytes 3 through 8 would contain the following hex values: Byte 3 = 0x52 Byte 4 = 0x02 Byte 5 = 0x55 Byte 6 = 0x03 Byte 7 = 0x46 Byte 8 = 0xDC Note that the dash character is not represented in the encoded value. For a power device, the first byte (Byte 3) will represent the socket number and the remaining 5 bytes (Byte 4-8) will be 0. Byte 9 ~ the left most 4 bits = The left most four bits of the 9th byte shall be used to encode / decode the following integer value to represent the power status of a connected server or the power status of a power device socket. One of the following values can be reported: 1 = Off - The connection path does not have power, which could be the result of the following situation: the RIP is unplugged or the RIP is plugged in but receives no power from the target device. 2 = On - The connection path has power. Byte 9 ~ the right most 4 bits = The right most four bits of the 9th byte shall be used to encode / decode the following integer value to represent the viewer session status of a connection path. For a power device or power device socket, this value is always 1 since viewer sessions are not supported. One of the following values can be reported: 1 = Idle - There is not a viewer session active on this connection path. 2 = Active - There is an active viewer session on this connection path. 3 = Blocked - The connection path is blocked meaning a viewer session cannot be established to this connection path because of another viewer session is currently using a resource required by this connection path in order to establish a connection path. A viewer session cannot be blocked by a virtual media session. Byte 10 ~ the left most 4 bits = The left most four bits of the 10th byte shall be used to encode / decode the following integer value to represent the virtual media session status of a connection path. For a power device or power device socket, this value is always 1 since virtual media sessions are not supported. One of the following values can be reported: 1 = Idle - There is not a virtual media session active on this connection path. 2 = Active - There is a virtual media session on this connection path. 3 = Blocked - The connection path is blocked meaning a virtual media session cannot be established to this connection path because of another virtual media session is currently using a resource required by this connection path in order to establish a connection path. A virtual media session cannot be blocked by a viewer session. Byte 10 ~ the right most 4 bits = The right most four bits of the 10th byte shall be used for future use and they will have a value of 0. Every connection path will be packed into this object in 10 byte increments one after the other. The connection paths do not have to be packed in any specific order. Note that the size of this object could conceivably be as large as shown in the following calculation with these assumptions. - 24 channel switch connected to each port of the appliance - 4 power devices connected to appliance, each having 32 outlets (((16 ports X 24 channels) + (4 power devices X 32 power device sockets)) X 10 bytes) + (2 byte Header) = 5122.