Send Netdot-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."


Today's Topics:

   1. Re: Dell 5548 PowerConnect SNMP VLAN membership not reported
      (Brian Candler)


----------------------------------------------------------------------

Message: 1
Date: Fri, 12 Jun 2015 20:19:05 +0100
From: Brian Candler <[email protected]>
Subject: Re: [Netdot-users] Dell 5548 PowerConnect SNMP VLAN
        membership not reported
To: "Boyer, Eric" <[email protected]>,      Netdot-users
        <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 12/06/2015 19:12, Boyer, Eric wrote:
> Does anyone have any experience with using Netdot to query information 
> via SNMP from Dell PowerConnect 5548 switches? I?m not sure if maybe 
> netdot just needs a copy of the Dell MIBs to be placed somewhere, but 
> when I look at the device information page for any of my Dell 5548?s 
> they don?t show which VLANs each port is on. Other devices in our 
> network do provide this information so I?m wondering if this is a 
> Netdot problem or a Dell problem.
>
It's a Dell SNMP problem - Q-BRIDGE-MIB not implemented correctly. I saw 
it with 5524, at least on trunk ports.

http://sourceforge.net/p/snmp-info/bugs/59/
https://osl.uoregon.edu/redmine/issues/1832

AFAICS there's no way to work out via SNMP which VLAN(s) are enabled on 
each port.



------------------------------

_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users


End of Netdot-users Digest, Vol 79, Issue 2
*******************************************

Reply via email to