Welcome, Guest. Please login or register.

Author Topic: tik  (Read 2771 times)

redpineapple

  • Jr. Member
  • **
  • Posts: 53
    • View Profile
tik
« on: February 03, 2012, 04:48:34 AM »
This is the stuff for a tik.  One little quirk is that you need to add +ct to the username in nedi.conf as well!!!

# Definition for 1.3.6.1.4.1.14988.1 created by Defgen 1.8 on 3.Feb 2012 (rbartels)

# General
SNMPv   2
Type   Mikrotik
Typoid   
Sysdes   
OS   ROS
Icon   c3od
Bridge   normal
Dispro   CDP
Serial   1.3.6.1.4.1.14988.1.1.4.1.0
Bimage   

# Vlan Specific
VLnams   
VLnamx   
VTPdom   
VTPmod   

# Interfaces
IFname   1.3.6.1.2.1.31.1.1.1.1
IFalia   1.3.6.1.2.1.31.1.1.1.18
IFalix   
InBcast   1.3.6.1.2.1.31.1.1.1.9
InDisc   1.3.6.1.2.1.2.2.1.13
OutDisc   1.3.6.1.2.1.2.2.1.19
IFvlan   1.3.6.1.2.1.17.7.1.4.5.1.1
IFvlix   
IFpowr   
IFpwix   
IFdupl   1.3.6.1.2.1.10.7.2.1.19
IFduix   1.3.6.1.2.1.10.7.2.1.1
Halfdp   2
Fulldp   3

# Modules
Modesc   
Moclas   
Movalu   
Moslot   
Modhw   
Modsw   
Modfw   
Modser   
Momodl   

# RRD Graphing
CPUutl   1.3.6.1.2.1.25.3.3.1.2.1
Temp   1.3.6.1.4.1.14988.1.1.3.10.0   0.1
MemCPU      
Custom      

lib cli code (Is it not possible to put this in the .def?)

# MIKROTIK

$cmd{'ROS'}{'ropr'} = '(.+?)>\s?$';
$cmd{'ROS'}{'enpr'} = '(.+?)>\s?$';
$cmd{'ROS'}{'conf'} = 'export';
$cmd{'ROS'}{'strt'} = '.';
$cmd{'ROS'}{'page'} = '';

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2786
    • View Profile
    • NeDi
Re: tik
« Reply #1 on: February 04, 2012, 12:40:13 PM »
Thanks for the contribution. I thought about this, but then it has do be done in every .def. an alternative would be to create a dictionary to separate it from the lib...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo