TpFdbTable entry format - SNMP

This is a discussion on TpFdbTable entry format - SNMP ; I'm sure this has worked for me before and I don't know what may have changed to cause this problem. Today when I try to walk the TpFdbTable (.1.3.6.1.2.1.17.4.3), I get gibberish: $ snmpwalk -v 2c -c public 10.93.0.15 .1.3.6.1.2.1.17.4.3 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: TpFdbTable entry format

  1. TpFdbTable entry format

    I'm sure this has worked for me before and I don't know what may have
    changed to cause this problem. Today when I try to walk the TpFdbTable
    (.1.3.6.1.2.1.17.4.3), I get gibberish:

    $ snmpwalk -v 2c -c public 10.93.0.15 .1.3.6.1.2.1.17.4.3 | more
    BRIDGE-MIB::dot1dTpFdbAddress.'......' = STRING: ""
    BRIDGE-MIB::dot1dTpFdbPort.'......' = INTEGER: 8
    BRIDGE-MIB::dot1dTpFdbStatus.'......' = INTEGER: learned(3)

    This seems to me to be a presentation issue (in snmpwalk) not an agent
    issue (in my sub-agent code) but my NetSNMP installation hasn't
    changed. Any insight appreciated...


  2. Re: TpFdbTable entry format

    Christopher Nelson wrote:
    > I'm sure this has worked for me before and I don't know what may have
    > changed to cause this problem. Today when I try to walk the

    TpFdbTable
    > (.1.3.6.1.2.1.17.4.3), I get gibberish:
    >
    > $ snmpwalk -v 2c -c public 10.93.0.15 .1.3.6.1.2.1.17.4.3 | more
    > BRIDGE-MIB::dot1dTpFdbAddress.'......' = STRING: ""
    > BRIDGE-MIB::dot1dTpFdbPort.'......' = INTEGER: 8
    > BRIDGE-MIB::dot1dTpFdbStatus.'......' = INTEGER: learned(3)
    >
    > This seems to me to be a presentation issue (in snmpwalk) not an

    agent
    > issue (in my sub-agent code) but my NetSNMP installation hasn't
    > changed. Any insight appreciated...


    Never mind. It was a change in the agent that I'd missed.


+ Reply to Thread