Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Questions about SNMP on QNX6.4.0 io-pkt: (3 Items)
   
Questions about SNMP on QNX6.4.0 io-pkt  
A few questions about SNMP and it's configuration when using io-pkt on Neutrino 6.4.0.  The below has been tried and 
tested on a 6.4.0 x86 VMWare installation.

***** Q1 *****
Is there a way to configure the SNMP Agent to use a different UDP port than 161 and to specifically not use port 161?
Configuring a different port number (55561 for example) in /etc/party.conf was tried, however when snmpd is started it 
seems to be opening and monitoring both the explicitly configured port as well as the default 161 port.  The message on 
startup is:
-----
# snmpd
Opening port(s): 192.168.255.128/161 192.168.255.128/55561
-----
netstat confirms this.
Can you offer instruction on how to configure the snmpd agent to not use the default port 161?

Changing the port definitions in /etc/services for snmp was also tried with no effect.

***** Q2 *****
As above, is there a way to confire SNMP TRAP to send out trap messages on a different port besides the default UPD port
 162?

Will changing the port definitions in /etc/services for snmp-trap affect this?

***** Q3 *****
The utility snmptrap can be used to send event messages for such things as "Power On" or "Link Up".  It's also 
understood that the underlying API of libsnmp can be used to send such event messages.
Is there a setting or way to configure the system or network stack in QNX to automatically enable such events to be sent
?


I don't have a lot of experience using or configuring SNMP so any assistance with the above would be greatly appreciated
.

Regards,

Eric
Re: Questions about SNMP on QNX6.4.0 io-pkt  
On Wed, Nov 11, 2009 at 01:41:31AM -0500, Eric Fausett wrote:
> A few questions about SNMP and it's configuration when using io-pkt on Neutrino 6.4.0.  The below has been tried and 
tested on a 6.4.0 x86 VMWare installation.
> 
> ***** Q1 *****
> Is there a way to configure the SNMP Agent to use a different UDP port than 161 and to specifically not use port 161?
> Configuring a different port number (55561 for example) in /etc/party.conf was tried, however when snmpd is started it
 seems to be opening and monitoring both the explicitly configured port as well as the default 161 port.  The message on
 startup is:
> -----
> # snmpd
> Opening port(s): 192.168.255.128/161 192.168.255.128/55561
> -----
> netstat confirms this.
> Can you offer instruction on how to configure the snmpd agent to not use the default port 161?
> 
> Changing the port definitions in /etc/services for snmp was also tried with no effect.
> 
> ***** Q2 *****
> As above, is there a way to confire SNMP TRAP to send out trap messages on a different port besides the default UPD 
port 162?
> 
> Will changing the port definitions in /etc/services for snmp-trap affect this?
> 
> ***** Q3 *****
> The utility snmptrap can be used to send event messages for such things as "Power On" or "Link Up".  It's also 
understood that the underlying API of libsnmp can be used to send such event messages.
> Is there a setting or way to configure the system or network stack in QNX to automatically enable such events to be 
sent?
> 
> 
> I don't have a lot of experience using or configuring SNMP so any assistance with the above would be greatly 
appreciated.

WRT 1 there doesn't appear to be a way to exclude port 161.
It looks to be hard coded in the agent.

Can you add this customer's info to PR 70375.

Thanks,

-seanb
Re: Questions about SNMP on QNX6.4.0 io-pkt  
Hello David,

Now a days I am struggling to configure the SNMP agent on the QNX 6.5.

QNX SNMP daemon is not exposing the Host Resource group data. The configuration (/etc/mib.txt) file contains all the 
required information.
The snmpget utility says – There is no such variable name in the MIB. But MIB contains this information.
 

Do you have any experience in SNMP implementation on QNX 6.5?

Regards,
Naresh