Hi All, I am a new entrant to this mailing list and appreciate the time and effort you spend on it. I am in a slight quandary. I am writing three agents (with separate functionalities) for a network element that is an H323 gatekeeper. Two of these agents are based on the mandatory MIBs for an H.323 Gatekeeper (the RAS-MIB and the H323-GATEKEEPER-MIB, B.2 and B.4 respectively,as given in Annex B of the ITU-T H.341 Recommendation *Multimedia Management Information Base*) These MIBs use ifIndex from Interfaces MIB (RFC 1573, 2233).
I have queried regarding the problem with Mr.Keith McCloghrie of Cisco Systems who is one of the authors of the RFCs on this (RFC1573,2233) and he appears to be of the opinion that the definitions are probably broken.
I'll describe the problem below.
The description of the following notifications seems to be broken.They use ifIndex as an object of the notification, while it is specified in the RFCs mentioned above that the semantics of an ifIndex value is to identify a network interface, not a network element such as the Gatekeeper, as the Description of these notifications shows. I wish to ascertain the purpose of using ifIndex in these MIBs and what it stands for from among the following ** Multiple Gatekeepers within managed system ? ** Multiple physical network interfaces of s single gatekeeper ? Further, RFC 2578 specifies that a single value of a MIB "Counter has (in general) no information content" (see section 7.1.6). Therefore, it is contrary to the SMI to specifythat "All MIB counters have gone to zero".
Please clarify regarding the same. Any and all comments will be appreciated. Best Regards, --Shshank
The notifications are given as follows: #1 **************************************************************************** ***** Name: h323GatekeeperStart Type: NOTIFICATION-TYPE OID: 0.0.8.341.1.1.6.6.0.1 Full path: oid_ccitt(0).oid_recommendation(0).oid_h(8).oid_h341(341).mmRoot(1).mmH323Ro ot(1).h323Gatekeeper(6).oid_ 0_0_8_341_1_1_6_6(6).h323GatekeeperNotifications(0).h323GatekeeperStart(1) Module: H323-GATEKEEPER-MIB
Parent: h323GatekeeperNotifications Next sibling: h323GatekeeperGoingDown
Status: current Objects: 1: ifIndex
Description: Signifies that the gatekeeper has started. All MIB counters have gone to zero. **************************************************************************** ***** #2 **************************************************************************** ***** Name: h323GatekeeperGoingDown Type: NOTIFICATION-TYPE OID: 0.0.8.341.1.1.6.6.0.2 Full path: oid_ccitt(0).oid_recommendation(0).oid_h(8).oid_h341(341).mmRoot(1).mmH323Ro ot(1).h323Gatekeeper(6).oid_ 0_0_8_341_1_1_6_6(6).h323GatekeeperNotifications(0).h323GatekeeperGoingDown( 2) Module: H323-GATEKEEPER-MIB
Parent: h323GatekeeperNotifications Prev sibling: h323GatekeeperStart Next sibling: h323GatekeeperError
Status: current Objects: 1: ifIndex
Description: Signifies that the gatekeeper is about to go down **************************************************************************** ***** #3 **************************************************************************** ***** Name: h323GatekeeperError Type: NOTIFICATION-TYPE OID: 0.0.8.341.1.1.6.6.0.3 Full path: oid_ccitt(0).oid_recommendation(0).oid_h(8).oid_h341(341).mmRoot(1).mmH323Ro ot(1).h323Gatekeeper(6).oid_ 0_0_8_341_1_1_6_6(6).h323GatekeeperNotifications(0).h323GatekeeperError(3) Module: H323-GATEKEEPER-MIB
Parent: h323GatekeeperNotifications Prev sibling: h323GatekeeperGoingDown
Status: current Objects: 1: ifIndex 2: h323GatekeeperStatisticsLastErrorEventTime 3: h323GatekeeperStatisticsLastErrorSeverity 4: h323GatekeeperStatisticsLastErrorProbableCause
Description: Signifies that an error has occurred in the Gatekeeper. **************************************************************************** *****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com