[Vyatta-users] MIssing the sysServices.0 OID from the MIB

2008-02-22 Thread Philip McDonald
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

Re: [Vyatta-users] MIssing the sysServices.0 OID from the MIB

2008-02-22 Thread Justin Fletcher
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

Re: [Vyatta-users] MIssing the sysServices.0 OID from the MIB

2008-02-22 Thread Christopher Johnson
I'm not sure that is the correct sysServices value. I've always used snmpconf to calculate the sysServices value. I believe a better value is 76 1 = physical (e.g. repeater) 2 = datalink/subnetwork (e.g. bridges) 3 = internet (e.g., supports IP) 4 = end-to-end (e.g., supports TCP) 7 =