Ad Widget

Collapse

cannot accurately apply filter no value received for macro {#SNMPVALUE}

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • whntk
    Junior Member
    • Feb 2018
    • 2
    #1

    cannot accurately apply filter no value received for macro {#SNMPVALUE}

    Use the built-in template on a HUAWEI router which also has virtual interfaces configured.
    Template Module EtherLike-MIB SNMPv2: EtherLike-MIB Discovery
    Discovery rule is:
    discovery[{#SNMPVALUE},1.3.6.1.2.1.10.7.2.1.19,{#IFOPERSTATU S},1.3.6.1.2.1.2.2.1.8,{#IFALIAS},1.3.6.1.2.1.31.1 .1.1.18,{#IFNAME},1.3.6.1.2.1.31.1.1.1.1,{#IFDESCR },1.3.6.1.2.1.2.2.1.2]

    snmpwalk information:
    [root@localhost]# snmpwalk ********** 1.3.6.1.2.1.10.7.2.1.19

    EtherLike-MIB::dot3StatsDuplexStatus.3 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.4 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.5 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.6 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.7 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.8 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.9 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.10 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.11 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.12 = INTEGER: unknown(1)
    EtherLike-MIB::dot3StatsDuplexStatus.13 = INTEGER: unknown(1)

    How to solve the problem described in the title？
    Last edited by whntk; 20-09-2018, 11:45.
    Tags: None
    • redpeppers
      Junior Member
      • Dec 2015
      • 8
      #2
      I am also experiencing the same error message when polling a Juniper Device. Has anyone found a solution to this issue?

      snmpwalk ************* 192.168.64.2 1.3.6.1.2.1.10.7.2.1.19

      EtherLike-MIB::dot3StatsDuplexStatus.538 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.539 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.540 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.541 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.550 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.551 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.552 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.553 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.554 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.555 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.556 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.557 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.606 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.612 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.613 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.614 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.615 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.616 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.617 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.622 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.624 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.625 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.633 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.640 = INTEGER: fullDuplex(3)
      EtherLike-MIB::dot3StatsDuplexStatus.642 = INTEGER: fullDuplex(3)

        Comment

        Previous template Next
        Working...