Yes, it's not in the SNMP configuration file, but it's easy to fix. As root, add to /etc/snmp/snmpd.conf:
sysServices 4 which shows that up to and including the internet layer is supported. Then run /opt/vyatta/sbin/snmpd.init restart These are the commands for Glendale, but it'll either be the same or very similar for previous releases. I'll file a bug on it for you as well. Justin On Fri, Feb 22, 2008 at 3:11 PM, Philip McDonald <[EMAIL PROTECTED]> wrote: > My OSS app is trying to discover a Vyatta NE and is being tripped-up by the > lack of a sysServices OID (.1.3.6.1.2.1.1.7.0) in the mib. > Why does vyatta lack this OID while all other commercial NEs have this > included in their system mib? > > As a work-around I've tried using snmpset to set the sysService OID but it > tells me that the OID doesn't exist and it won't add the OID by default. > > Should I try snmpconfig? If so, how would I solve this problem. > > Thanks, > P > > > _______________________________________________ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
