----------------------                      WindNet SNMP FAQ # 1.1                      ----------------------                      Numbers: 1 to 29This is a FAQ for WindNet SNMPv1/v2c 1.0 FCS, and this version is supportedon Tornado 1.0 and 1.0.1. In addition to these questions you can findexample code from the SNMP user's guide in the "Techpubs" area online. Forward your comments to support@wrs.com ==========================================================================1.  TITLE: WindNet SNMP agent versions and releases, what is supported ? 2.  TITLE: Building the snmp agent gives " out of environment space " error.3.  TITLE: Missing parameter information for user hooks in snmpdInitFinish.4.  TITLE: How does WindNet SNMP agent interface with network drivers            and MIB2.5.  TITLE: getproc_got_string manpage missing how snmpdMemoryFree is used. 6.  TITLE: The trap processing is missing a reference to the hook for            releasing privately allocated memory.7.  TITLE: nextproc_next_instance() does not explain the reference point            of the instance.8.  TITLE: snmpSet() and snmpTest() in snmpSnmp.c have incorrect code. 9.  TITLE: SNMPv1/v2c 1.0 demo MIB exmaple from the user guide does            not compile.10. TITLE: snmpGroupedVbsProcess() prototype defined in snmpdLib.h is            not found.11. TITLE: Prototype for snmpdContinue() is missing in snmpdLib.h.12. TITLE: What can I do to make the -stub option generate method            routines for the SNMP trap objects.13. TITLE: When to use non-asynch functions, %n or %N option.  14. TITLE: How is the cookie variable used. 15. TITLE: Why would one want to use the -skel output format for the            mibcompiler.16. TITLE: How to add support for counters and MIB-II in custom network            drivers such as token ring, ethernet etc.17. TITLE: How does the snmpdGroupByGetprocAndInstance() function work ?18. TITLE: Missing documentation for snmpNextIndex in SNMPv1/v2c 1.0.19. TITLE: Why is snmpIoCommunityValidate() not returning a response PDU            to the SNMP manager ?20. TITLE: Compiling custom and standard MIBs gives errors.21. TITLE: mibleaf.h file is missing in the /snmpv1/agent/ directory.22. TITLE: How to use non-ip interfaces in the MIB ifTable.23. TITLE: Problem using ipAddrTable in snmpIp.c. 24. TITLE: SNMP MIB compiler fails on UInteger32 in rfc1447 MIB definition.25. TITLE: SNMP MIB compiler complains about BITS in the MIB definition. 26. TITLE: m2Init does not initialze the maxRouteTableSize value correctly. 27. TITLE: How to set the priority of the tSnmpd task at vxWorks boot time. 28. TITLE: How are the driver counters used for MIB2 interfaces ? 29. TITLE: Why the SET request from a SNMP manager does not get a            response from the SNMP agent ?==========================================================================1. TITLE: WindNet SNMP agent versions and releases, what is supported ?                          SCOPE                   DISCOVERED ON              HOST:  All                     -------------------     -------------------      ARCHITECTURE:  All                     -------------------     -------------------               BSP:  All                     -------------------     -------------------PRODUCT / REVISION:  5.2, 5.3. 5.3.1                     -------------------     -------------------DESCRIPTION OF PROBLEM: Which versions of the snmp agent can I use with Vxworks and Tornado. RESOLUTION: Check your WindNet SNMP user guide and Tornado installation guide.VxWorks 5.2   - uses WindNet SNMP 1.0  Tornado 1.0   - uses WindNet SNMPv1/v2c 1.0 Tonnado 1.0.1 - uses WindNet SNMPv1/v2c 1.0 (NOTE - The SNMP agent version                is the same as in Tornado 1.0 because agent was not modified.                 But this optional product is re-released for Tornado 1.0.1.                 If you are running the SNMP agent that was released for                 Tornado 1.0 in Tornado 1.0.1, it will ** NOT WORK **. VxWorks 5.2          - uses SNMP protocol version v1 and v2  Tornado 1.0, 1.0.1   - uses SNMP protocol version v1 and v2c VxWorks 5.2          - based on bilingual monolithic agent release 12.1.11                           from SNMP Research Tornado 1.0, 1.0.1   - based on  bilingual monolithic agent from Epilogue                           Epilogue agent version         7.0                            Epilogue mib compiler version  6.0Not yet supported    - Masteragent-subagent technology.NOTE - If you have snmp applications (method routines) running on        5.2 VxWorks using the agent based on SNMP Research, the routines       are not compatible with the Epilogue based snmp agent in Tornado 1.0       and 1.0.1. See the WindNet SNMPv1/v2c 1.0 release notes. KEYWORDS: Envoy Emissary mibcomp mib2 snmpv1v2c snmpv2  --------------------------------------------------------------------------2. TITLE: Building the snmp agent gives " out of environment space " error.                         SCOPE                   DISCOVERED ON              HOST:  Windows 95              Windows 95                     -------------------     -------------------      ARCHITECTURE:  All                     ads360                     -------------------     -------------------               BSP:  All                     ads360                     -------------------     -------------------PRODUCT / REVISION:  SNMPv1/v2c 1.0 FCS      Tornado 1.0                     -------------------     -------------------DESCRIPTION OF PROBLEM: After WindNet SNMP v1/v2c agent is installed,torVars on the msdos window gives "out of environment space" error. Andwhen the snmp agent is built using the makefile in /target/src/snmpv1/agentthe following error is displayed :...Out of environment spaceOut of environment spaceOut of environment spaceOut of environment spaceOut of environment spaceOut of environment spaceBad command or file nameFile creation errorFile creation errorRESEARCH: The dos shell is running out of environment spaceRESOLUTION: In your msdos window do the following ...1. Point to the title bar of the dos window and click the right mouse button.2. Now you should have a pop up menu with the last option as "Properties"3. Click on Properties and a "MS-DOS Prompt Properties" window will pop up.   - This window will have 5 tab buttons, click on the "Memory" button   - Now you will see 4 different boxes for memory settings   - Go to the "Conventional memory" box, and there is an "Intial Environment"     setting; change the setting from "Auto" or any other number to the highest     value (4096) by selecting from it's pull down list.4. Click on the "Apply" button.5. Restart the dos command prompt window6. Set the environment variables for Tornado executing torVars, it is located   in your Tornado's /host/x86-win32/bin/ directory.7. Rebuild the snmp agent.SPR / PATCH:KEYWORDS: compile NT windows95 make makefile fails environment variables--------------------------------------------------------------------------3. TITLE: Missing parameter information for user hooks in snmpdInitFinish.                         SCOPE                   DISCOVERED ON              HOST:  All                     -------------------     -------------------      ARCHITECTURE:  All                     -------------------     -------------------               BSP:  All                     -------------------     -------------------PRODUCT / REVISION:  snmpv1/v2c 1.0          snmpv1/v2c 1.0                     -------------------     -------------------DESCRIPTION OF PROBLEM:In WindNet SNMPv1/v2c Component Release Supplement, Section 4.8 HOOKS,pg 29.  We are allowed 5 hooks to user supplied routines to be used inthe "SET" processing sequence.  What are the parameters passed to theseroutines? The manpage for snmpdInitFinish does not describe the parametersfor the hooks.RESOLUTION: The parameter to the hook routines is a pointer to the snmp packetyou are processing.LOCAL VOIDFUNCPTR   snmpHkPrivRlseRtn;     /* user hook private release rtn */LOCAL FUNCPTR       snmpHkSetPduVldtRtn;   /* user hook set pdu validate rtn */LOCAL FUNCPTR       snmpHkPreSetRtn;       /* user hook pre set rtn */LOCAL FUNCPTR       snmpHkPostSetRtn;      /* user hook post set rtn */LOCAL FUNCPTR       snmpHkSetFailedRtn;    /* user hook set failed rtn */void snmpdInitFinish    (    VOIDFUNCPTR    pPrivRlse,     /* user's privare release routine */    FUNCPTR        pSetPduVldt,   /* user's set pdu validate routine */    FUNCPTR        pPreSet,       /* user's pre set routine */    FUNCPTR        pPostSet,      /* user's post set routine */    FUNCPTR        pSetFailed     /* user's set failed routine */    )    {    snmpHkPrivRlseRtn = pPrivRlse;    snmpHkSetPduVldtRtn = pSetPduVldt;    snmpHkPreSetRtn = pPreSet;    snmpHkPostSetRtn = pPostSet;    snmpHkSetFailedRtn = pSetFailed;    snmpIoTrapSend (COLD_START, 0);    snmpMibsInit ();    }The parameters to the routines in snmpdInitFinish for all the 5 hook routines  are pointers to the snmp packet you are processing ...* snmpHookPrivRelease - release private memory used by hooks** This routine is used by the agent to free any memory attached to the* private field of the SNMP_PKT_T structure.  This routine must be* provided by the user, if it is required.void snmpHookPrivRelease    (    SNMP_PKT_T  *pPkt    /* snmp packet */    )* snmpHookSetPduValidate - validate a `set' request PDU** This routine is called before any processing of a `set' request has* taken place.  It can be used to perform global validation of the* request, if needed.  This routine must be provided by the user, if* it is required.** RETURNS:*   0 indicates that the `set' PDU is valid, and processing should continue.*   1 indicates that the `set' PDU is valid, and that this routine has*   already completed all the required `set' operations.*   -1 indicates that the `set' PDU is invalid and should be rejected.*int snmpHookSetPduValidate    (    SNMP_PKT_T *     pPkt    )* snmpHookPreSet - perform user-specified actions before a `set' operation** This routine is called after all `testproc' operations have* completed successfully, but before any `setproc' operation is begun.* This routine must be provided by the user, if it is required.** RETURNS:*   0 indicates that the `set' PDU is valid, and processing should continue.*   1 indicates that the `set' PDU is valid, and that this routine has*   already completed all the required `set' operations.*   -1 indicates that the `set' PDU is invalid and should be rejected.*int  snmpHookPreSet    (    SNMP_PKT_T *    pPkt    )* snmpHookPostSet - perform user-specified actions after a `set' operation** This routine is called after all `setproc' have completed* successfully. This routine can be used to free resources allocated* during `set' processing.  This routine must be provided by the user,* if it is required.*int  snmpHookPostSet    (    SNMP_PKT_T *     pPkt    )* snmpHookSetFailed  - perform user-specified actions on failure of a                        `set' operation** This routine is possibly called under two sets of circumstances:* after all `testproc' operations have returned and some of them have* failed, and/or after all `undoproc' operations have returned and* some `setproc' operations have failed.  It can be used to do any* required cleanup.  This routine must be provided by the user, if it* is required.*int  snmpHookSetFailed    (    SNMP_PKT_T *     pPkt    )SPR / PATCH: 8480KEYWORDS: snmp v1v2c v1 v2 mib --------------------------------------------------------------------------4. TITLE: How does WindNet SNMP agent interface with network drivers           and MIB2.                          SCOPE                   DISCOVERED ON              HOST:  All                     -------------------     -------------------      ARCHITECTURE:  All                     -------------------     -------------------               BSP:  All                     -------------------     -------------------PRODUCT / REVISION:  snmpv1/v2c 1.0                     -------------------     -------------------DESCRIPTION OF PROBLEM:The user is setting up the system so that there are two SNMP Managersrunning on two separate nodes, though only one will be used at any onetime.  How to get our agent to switch from talking to one to start talking to the other.  Would this just work?  In other words could our agent receive SNMP requests from both managers and respond to the appropriate one? Exactly what should be added to the driver to support the FDDI MIB ? How toupdate the FDDI MIB ? We use FDDI as our physical network interface.  We wish to use SNMP tomonitor the status of the FDDI interface. Thus we need know how theFDDI driver updates the FDDI MIB statistics. The WindNet SNMP documents doesnot give more details other than this in the WindNet SNMP ReleaseNotes 1 Section 5:"Existing network drivers and drivers under development must provide MIB-II support."Since FDDI MIB is not included in the MIB-II, what ioctl commands doesWindNet SNMP or VxWorks provide for the FDDI driver to support FDDI-MIB?  Should there be more data structures defined specifically for FDDI?From these paragraphs, I assume VxWorks supports MIB-II (all MIB groups)using ioctl commands.  Are the 2 structures specified in the Release Note 1sufficient to support all other MIB-II parameters?  Are there any