This read-only enumeration categorizes an event trap into one of three broad classes -- configuration, hardware, or software -- indicating what kind of underlying condition triggered it. Admins use this to route or prioritize incoming traps, for example escalating hardware-class traps to on-site technicians while routing configuration-class traps to network engineers. For example, a trap reporting hardware(1) would be treated very differently by an operations team than a trap reporting configuration(0), since one implies a possible field-service dispatch and the other doesn't.