CatPaw Rumors: Post Release Summary Part III

It is unexpected that CatPaw needs two refresh releases (5.1 and 5.2). But it shows a few bugs need to be addressed as soon as possible.

A few bugs only occur in our command line tools. So they are minor and do not harm the whole package. 

The biggest problem comes from our CF assembly. It is hard to make sure everything works for CF, as I am not using .NET CF anymore. Therefore, when 5.0 was shipped we can see the CF assembly is in fact broken. I was planning to fix that all in 5.1. Fixing the csproj file and adding Mono code files are relatively easy. However, something from .NET CF itself leads to side effect.

As Microsoft cut off too many things, even though Mono classes filled in some gaps, an issue happened when I tried to work around a missing String.Split method. This breaks 5.1 release, so we have to release 5.2 this weekend.

Hope you are not bothered much by these issues. If you are, please grab our latest release which contains the fixes.

http://sharpsnmplib.codeplex.com/releases/view/47894

CatPaw Rumors: Post Release Summary, Part II

Our agent, snmpd.exe, supports all three SNMP versions. Then how to get data from it?

SNMP v1 and v2c

The community strings for both GET and SET operations are the same, "public".

SNMP v3

Community names are obsolete, so snmpd.exe supports three users (to match three modes).

• "neither" is the user for noAuthNoPriv mode. If you use it, remember to use default authentication provider and default privacy provider.
• "auth" is the user for authNoPriv mode. It uses MD5 authentication provider whose phrase is "authentication". Its privacy provider is still the default one.
• "privacy" is the user for authPriv mode. It uses MD5 authentication provider whose phrase is "authentication", but its privacy provider is the DES privacy provider whose phrase is "privacyphrase".

Now let's see if you are going to test out snmpd.exe using our command line tools what commands should be used.

SNMPGET

For SNMP v1 and v2c, typical command is

snmpget -v=1 -c=public localhost 1.3.6.1.2.1.1.1.0

For SNMP v3, typical command is

snmpget -v=3 -l=authPriv -a=MD5 -A=authentication -x=DES -X=privacyphrase -u=privacy localhost 1.3.6.1.2.1.1.1.0

SNMPSET

For SNMP v1 and v2c, typical command is

snmpset -v=1 -c=public localhost 1.3.6.1.2.1.1.6.0 s Shanghai

For SNMP v3, typical command is

snmpset -v=3 -l=authPriv -a=MD5 -A=authentication -x=DES -X=privacyphrase -u=privacy localhost 1.3.6.1.2.1.1.1.0 s Shanghai

SNMPBULKGET

For SNMP v2c, typical command is

snmpbulkget -v=2 -c=public -Cr=10 localhost 1.3.6.1.2.1.1.1.0

For SNMP v3, typical command is

snmpbulkget  -v=3 -l=authPriv -a=MD5 -A=authentication -x=DES -X=privacyphrase -u=privacy -Cr=10 localhost 1.3.6.1.2.1.1.1.0

SNMPGETNEXT

For SNMP v1 and v2c, typical command is

snmpgetnext -v=1 -c=public localhost 1.3.6.1.2.1.1.1.0

For SNMP v3, typical command is

snmpgetnext -v=3 -l=authPriv -a=MD5 -A=authentication -x=DES -X=privacyphrase -u=privacy localhost 1.3.6.1.2.1.1.1.0

SNMPTRANSLATE
Typical command is

snmptranslate 1.3.6.1.2.1.1.1.0

SNMPWALK

For SNMP v1, typical command is

snmpwalk -v=1 -c=public -m=subtree localhost 1.3.6.1.2.1.1

For SNMP v2c, typical command is

snmpwalk -v=2 -c=public -Cr=10 -m=subtree localhost 1.3.6.1.2.1.1

For SNMP v3, typical command is

snmpwalk -v=3 -l=authPriv -a=MD5 -A=authentication -x=DES -X=privacyphrase -u=privacy -Cr=10 -m=subtree localhost 1.3.6.1.2.1.1

(Update: Two more bugs were found and fixed during the authoring of this article. So we will refresh CatPaw again, and it should be 5.2.)