Sun Microsystems MEDIACENTER 2.1 - Manual (Page 153)

Appendix A Setting up the SNMP Agent A-9
As an example of a the SNMP agent’s capability, the following is a Quick Dump
report for the
bitPump attribute on a machine redoubt :
A.3 Enabling Trap Handling
In addition to the six standard SNMP traps, the Sun MediaCenter server ’s SNMP
agent supports three enterprise-specific traps,
Admission_Failed ,
Missed_Deadline , and Disk_Failure . When the bit pump misses a deadline, the
server fails to admit a title, or a disk failure occurs, the agent sends enterprise-
specific trap 1, 2, or 3, respectively.
Perform the following tasks to enable trap handling in Solstice Domain Manager.
SNM uses the snmp.traps file, stored by default in /var/opt/SUNWconn/snm , to
establish mapping between trap numbers and descriptive names for those traps. To
map the enterprise-specific trap numbers (1, 2, and 3, as mentioned above) to names,
on the SNM Console machine, perform one of the following two tasks:
■
If you have not made use of the snmp.traps file to this point, save the file to a
file of a different name. Then, from the Sun MediaCenter server, copy the
snmp.traps file in /opt/SUNWsms/agents to /var/opt/SUNWconn/snm on
the SNM Console machine.
■
If you have already modified snmp.traps on the Console machine and want to
preserve its contents, append the contents of snmp.traps on the Sun
MediaCenter server to its counterpart on the Console machine.
See the Solstice Domain Manager Administration Manual for details on the
snmp.traps file.
The trap explanations are:
1 Admission_Failed
The Sun MediaCenter server was unable to admit a title that a user requested for
playing. This indicates an exhaustion of resources.
Wed May 24 15:12:15 1995 [ redoubt ] : Quick Dump: sms-vod.bitPump
bitPumpStreams=2
bitPumpBandwidth=8003840
bitPumpTimePeriod=5405:07:40.72
bitPumpMissedDeadlines=0