5/29/2023 0 Comments Linux check disk health aixStartsrc -s hostmibd startsrc -s snmpmibd Startsrc -s snmpd startsrc -s dpid2 startsrc -s aixmibd Stopsrc -s snmpd stopsrc -s dpid2 stopsrc -s aixmibd You need to run the IBM snmpd on a different port: chssys -s snmpd -a '-p 1610' VACM_ACCESS director_group - noAuthNoPriv SNMPv2c defaultView - defaultView. VACM_GROUP director_group SNMPv2c public. Logging file=/usr/tmp/snmpdv3.log enabled TARGET_PARAMETERS trapparms1 SNMPv1 SNMPv1 public noAuthNoPriv -ĬOMMUNITY public public noAuthNoPriv 0.0.0.0 0.0.0.0. TARGET_ADDRESS Target1 UDP 127.0.0.1 traptag trapparms1. VACM_ACCESS group1 - noAuthNoPriv SNMPv1 defaultView - defaultView. VACM_VIEW defaultView 1.3.6.1.2.1 - included. # include normally excluded aixmibd managed MIBs from the default view VACM_VIEW defaultView snmpModules - included. # include normally excluded snmpv3 related MIBs from the default view #VACM_VIEW defaultView internet - included. Sample /etc/nf: VACM_GROUP group1 SNMPv1 public. If you are not receiving data for CPU, memory, etc:Įnsure hostmibd, snmpmibd and aixmibd are not commented out in /etc/rc.tcpipĮnsure that snmp configuration allows connections from 127.0.0.1 with public community (or the appropriate community if you’ve changed that used by aixmibd away from the default.) (Note: the subdaemon’s actually connect to hostname “loopback” – so make sure that correctly resolves to 127.0.0.1)Įnsure aixmibd is running: lssrc -s aixmibdĬheck /var/tmp/aixmibd.log to see whether aixmibd has correctly registered with the snmpd system, and for clues as to why not. Startsrc -s snmpd startsrc -s dpid2 startsrc -s aixmibd startsrc -s hostmibd startsrc -s snmpmibd Then restart all the snmp services: stopsrc -s snmpd stopsrc -s dpid2 stopsrc -s aixmibd stopsrc -s hostmibd stopsrc -s snmpmibd Is changed to included: VACM_VIEW defaultView 1.3.6.1.4.1.2.6.191 - included.
0 Comments
Leave a Reply. |