mrtg and snmp v3 setup

Ok, so I tried to get a possible answer for this, post is here:
https://www.linuxquestions.org/quest...v3-4175634900/
I know, this is a second post, but maybe this belongs here, as opposed to software.

Anyways, mrtg with snmp v2c works fine. Basically, using mrtg on a server, to track router traffic.
Network admin wants to change to snmp v3. So, supposedly the test router is set up to use snmp v3.
So, now I am trying to re-write the cfgmaker command so that it will work on on 3 instead of 2c.

Currently, my command stands as such:

snmpwalk -v3 -l authPriv -u "username" -a SHA -A "shapass" -x AES -X "password" routerip

Packets do get to the router and back, so firewall port is open.
The return error is:
no log handling enabled - turn on stderr logging.
snmpwalk: Unsupported security level.

Now, logging might help, but I haven't found how to turn it on for this.
The unsupported security level makes me thing it is something on the router config.

Prior to this, the mrtg server on had snmp libraries installed, I did install the rest of snmp 5.5
I have not made any sort of change to snmpd.conf, as there was none for snmp v2c, so I didn't think it was needed for v3. Maybe?

Anyone have an idea?

Thanks!

The router wouldn't by any chance happen to be a Cisco device?

I haven't seen it myself, but I can almost guarantee it is a cisco device.

In that case, if you follow the link you'll see there's a bug related to SNMPv3 and usernames over a certain length.

Yeah, I saw that, but the username is not long enough to be an issue. If only it were that easy!

Then you need to check the privilege level of the user on the router itself.

That's about what I thought. I've been trying to work with the network guy on this, but communication is slow. I am also having him look into the contextengineid to make sure I have the right one.

I have been able to get the snmpwalk to work now, and parses the BGP route tables. So now it is just getting the cfgmaker command to work. So, I would have to concur that it is probably a setting on the router.