5 Replies Latest reply on Apr 7, 2016 7:47 PM by Charles Kelley

    Trace Log not showing snmp messages in mcxa.trace

    john pereira

      hi, i have enabled tracelevel=6 in mcxa.conf

      but when i send a snmp trap to the snmp adapter system, i dont see any snmp messages in the mcxa.trace.

       

      i see from other community documents, that people do see snmp messages in the logs after tracelevel=6

       

      why is it i cant see it in my logs. what am i be doing wrong here.

       

      John

        • 1. Re: Trace Log not showing snmp messages in mcxa.trace
          Charles Kelley

          It is case sensitive on this parameter.  It must be TraceLevel, and not tracelevel.

           

          Also, make sure it is in your [default] section.

           

          Charles

          • 2. Re: Trace Log not showing snmp messages in mcxa.trace
            john pereira

            Thanks Charles, that worked. i have another question though.

             

            i am not able to get the adapter to use the portal class, instead if continues to fall back on to the enterprise class.

             

            the oid's i am getting from the snmp traps are below.

            snmp_oids=['1.3.6.1.4.1.1031.5.1.1.0','1.3.6.1.4.1.1031.5.1.2.0','1.3.6.1.4.1.1031.5.1.3.0','1.3.6.1.4.1.1031.5.1.4.0','1.3.6.1.4.1.1031.5.1.5.0','1.3.6.1.4.1.1031.5.1.6.0','1.3.6.1.4.1.1031.5.1.7.0','1.3.6.1.4.1.1031.5.1.8.0','1.3.6.1.4.1.1031.5.1.9.0','1.3.6.1.4.1.1031.5.1.10.0','1.3.6.1.4.1.1031.5.1.13.0','1.3.6.1.4.1.1031.5.1.14.0','1.3.6.1.4.1.1031.5.1.17.0','1.3.6.1.4.1.1031.5.1.18.0','1.3.6.1.4.1.1031.5.1.19.0','1.3.6.1.4.1.1031.5.1.21.0','1.3.6.1.4.1.1031.5.1.22.0','1.3.6.1.4.1.1031.5.1.23.0'];

             

            and in the map file i have the entries like below

            CLASS SNMP_bmcPMPortalParameterStateChange

                        $TrapOID equals /^1\.3\.6\.1\.4\.1\.1031\.5\.0\.1($|\.)/

                        snmpv_bmcPMPortalAccountName = GetListElem ($var, 0)

             

            I tried to work this out, but seems like i cant get it to work.

            is the $TrapOID pattern correctly set to match the actual oid's coming into the adapter?

             

            every time it seems to use the SNMP_Enterprise instead of SNMP_bmcPMPortalParameterStateChange

            i believe its due to the pattern mismatch. can you help.

             

            thanks

            john.

            • 3. Re: Trace Log not showing snmp messages in mcxa.trace
              john pereira

              hi charles, i got this fixed. i now have portal snmp alerts coming into bppm 9.6 console.

              i think the issue was i was using 2 adapters.

              when i stopped the v3 adapter i am able to get the alerts.

               

              just want to validate on this since i am confused.

              document says to use only one adapter with one mcxa.conf file.

              but the mcxa.conf had 3 snmp adapters.

              snmp_adapter, snmp and snmpV3

               

              does the document tell to use only 1 of the above ?

              this i ask, bcoz in other documents i see people were using snmp_adapter and snmpv3 more commonly, so i was confused. but my problem is resolved by disabling v3 and allowing only snmp_adapter to run.

               

              can you clarify this.. thanks

              • 4. Re: Trace Log not showing snmp messages in mcxa.trace
                john pereira

                i had problems with this setup

                E:\BPPM\Agent\server\bin>mcxactrl.pl --list

                Adapter Status:

                       MA::ESnmpTrap         snmp_adapter              RUNNING

                       MA::Adapter::CtrlPort             CtrlPort              RUNNING

                       MA::ESnmpTrapV3               SnmpV3              RUNNING

                 

                my problems were fixed after i setup this up

                E:\BPPM\Agent\server\bin>mcxactrl.pl --list

                Adapter Status:

                       MA::Adapter::CtrlPort             CtrlPort              RUNNING

                       MA::ESnmpTrap         snmp_adapter              RUNNING

                • 5. Re: Trace Log not showing snmp messages in mcxa.trace
                  Charles Kelley

                  You can have more than one adapter enabled in the mcxa.conf, although to get peak performance with high loads of SNMP traffic, I'd recommend having just one enabled on the particular machine.

                   

                  There are just three SNMP adapter examples within the commented section.  If you were to have two SNMP Adapter instances enabled for some reason, they would need to be on different ports (perhaps one on the default port of 162, and the other on some high port, such as 1162).

                   

                  On the v3 adapter, it can receive v1, v2, and v3 traps.  For v3, you'd have to setup the authentication settings in the snmptrapd.conf.  The MA::ESnmpTrap adapter can receive just v1 & v2 traps.

                   

                  You could also have, for example, an SNMP Adapter instance enabled, as well as a logfile adapter instance.  They all have to split up the polling time though, so for best performance on an adapter, I'd lean towards having just the one enabled.

                   

                  Charles