50 likes | 55 Views
RAQMON MIB Discussion. IETF 55 Atlanta, Nov. 18, 2002. Agenda (Andy’s Questions). Determine (if possible) if the MIB is complete for: Configuration Reported attributes collected from RAQMON PDU. MIB Structure. Changes In draft-02. changed OID of raqmonSessionAlarm
E N D
RAQMON MIB Discussion IETF 55 Atlanta, Nov. 18, 2002
Agenda (Andy’s Questions) • Determine (if possible) if the MIB is complete for: • Configuration • Reported attributes collected from RAQMON PDU
Changes In draft-02 • changed OID of raqmonSessionAlarm • clarifications in DESCRIPTION clauses • changed raqmonParticpantActive SYNTAX to TruthValue • change range of raqmonParticipantSrcLayer2 and raqmonParticipantDestLayer2 to (0..7) • changed raqmonParticipantSrcLayer3 and raqmonParticipantDestLayer3 to Dscp • changed counters SYNTAX to Counter32 • added raqmonConfigPDUTransport and raqmonConfigRaqmonPDUs • added raqmonPDUBasicPDU and raqmonSNMPTransportNotification • changed raqmonConformace to reflect the different conformance requirements for collectors and RAQMON devices
Fixes and Open Issues • Read-write objects in raqmonParticpantTable • CPU and memory utilization objects? • Extend raqmonQosTable to cover more than the basic attributes carried by the RAQMON PDUs? • Mechanism to add vendor specific extensions? • Keep raqmonParticipantAddrTable, or add raqmonParticipantAddr as index in the raqmonParticipantTable? • raqmonConfigPDUTransport – can / should a collector support more than one transport simultaneously?