Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3831

Viptela devices - Support for routing and inventory tabs

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Major
    • None
    • None
    • OS
    • None

    Description

      Viptela devices do not have a routing tab or inventory tab. Walk and MIBs are attached.

       

      Attachments

        Activity

          [OBS-3831] Viptela devices - Support for routing and inventory tabs
          landy Mike Stupalov added a comment -

          BGP support added in r11960.

          landy Mike Stupalov added a comment - BGP support added in r11960.
          landy Mike Stupalov added a comment -

          yah, as I remember support for this devices mostly improved (except BGP).

          BGP in progress now.

          landy Mike Stupalov added a comment - yah, as I remember support for this devices mostly improved (except BGP). BGP in progress now.
          kentbjoh Kent Johannessen added a comment -

          Hey Mike,
          Possible to have a look at this?
          Can provide more dumps if needed.

          kentbjoh Kent Johannessen added a comment - Hey Mike, Possible to have a look at this? Can provide more dumps if needed.
          kentbjoh Kent Johannessen added a comment -

          This would be useful for us as well. Hoping to see it added soon

          kentbjoh Kent Johannessen added a comment - This would be useful for us as well. Hoping to see it added soon
          ckunsman Chad Kunsman added a comment - - edited

          Attached are the walks from the Viptela device - however I do get a timeout on these after a while - I don't know if that means the data got truncated or not. Would you be able to tell? I'm hoping the specific data you'd need has been included.

           

          Edit: I notice the viptela mibs were removed from the attachments. Let me know if you need them re-attached.

          ckunsman Chad Kunsman added a comment - - edited Attached are the walks from the Viptela device - however I do get a timeout on these after a while - I don't know if that means the data got truncated or not. Would you be able to tell? I'm hoping the specific data you'd need has been included.   Edit: I notice the viptela mibs were removed from the attachments. Let me know if you need them re-attached.
          landy Mike Stupalov added a comment -

          Seems as you added snmpdump from different device (Cisco ASR1001-HX).
          Try again with Viptela device.

          landy Mike Stupalov added a comment - Seems as you added snmpdump from different device (Cisco ASR1001-HX). Try again with Viptela device.
          ckunsman Chad Kunsman added a comment -

          Hello - what is pending from me? Thanks.

          ckunsman Chad Kunsman added a comment - Hello - what is pending from me? Thanks.
          bot Observium Bot added a comment -

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

          People

            landy Mike Stupalov
            ckunsman Chad Kunsman
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: