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: Spanning Tree Graph (Kristof Van Doorsselaere)
----------------------------------------------------------------------
Message: 1
Date: Wed, 19 Mar 2014 07:59:29 +0000
From: Kristof Van Doorsselaere <[email protected]>
Subject: Re: [Netdot-users] Spanning Tree Graph
To: Carlos Vicente <[email protected]>
Cc: Netdot-users <[email protected]>
Message-ID: <cf4f0b0c.1c3eb%[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Carlos,
I think this might have changed, in the hp 2600 datasheet the RFC 1493
Bridge MIB is listed
(http://www.andovercg.com/datasheets/hp-procurve-2600-series.pdf), I think
this is the one used to get STP info, isn?t it?
I can do some test if you would like? Just to see if they now provide
enough STP info, do you still remember what info was missing?
I tested the dot1dStpPortState , and this seems to be correct:
[root@syslog netdot]# snmpwalk -v2c -c public xxxxxxx.hogent.be
.1.3.6.1.2.1.17.2.15.1.3
SNMPv2-SMI::mib-2.17.2.15.1.3.1 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.2 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.3 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.4 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.5 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.6 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.7 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.8 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.9 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.10 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.11 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.12 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.13 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.14 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.15 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.16 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.17 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.18 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.19 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.20 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.21 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.22 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.23 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.24 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.25 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.26 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.27 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.28 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.29 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.30 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.31 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.32 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.33 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.34 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.35 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.36 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.37 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.38 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.39 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.40 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.41 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.42 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.43 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.44 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.45 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.46 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.47 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.48 = INTEGER: 5
SNMPv2-SMI::mib-2.17.2.15.1.3.49 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.50 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.51 = INTEGER: 1
SNMPv2-SMI::mib-2.17.2.15.1.3.52 = INTEGER: 1
1 = disabled (nothing connected)
5 = forwarding
traffic)
2 = blocking
mvg,
Kristof Van Doorsselaere
Hoofdmedewerker server- en netwerkbeheer
----------------------------------
Hogeschool Gent
Cel Netwerk- en Serverbeheer
Valentin Vaerwyckweg 1 - Schoonmeersstraat 52
9000 Gent
Belgium
Tel : 09/243.35.20
mailto:[email protected]
On 19/03/14 01:03, "Carlos Vicente" <[email protected]> wrote:
>Hi Kristof,
>
>Last time I checked (years ago), HP switches did not provide enough STP
>information in the MIBs.
>
>cv
>
>On Mar 13, 2014, at 6:35 AM, Kristof Van Doorsselaere
><[email protected]> wrote:
>
>> Hello
>>
>> I?m trying to figure out why the generated spanning tree graph is
>>missing links, but let me first give you some info about our network,
>>and what I have done so far
>>
>> Our campus network was successfully discovered by netdot, we now have
>>325 switches (cisco & HP) 2 firewalls, 2 routers and some extra devices
>>in netdot
>>
>> The switches are a combination of:
>>
>> cisco catalyst 6509, 3750 & 2960 for core and distribution layer
>> hp procurve 2800, 2600, 2500 for access layer
>>
>> We are running MST spanning tree with a single instance
>>
>> I noticed that in the web GUI that for cisco the STP type was set to
>>mst , while for our HP switches it was set to: mstpOperation
>>
>> Since no HP switches were seen in the Spanning Tree graph, so I Tried
>>to find out why. I discovered in Device.pm there were a few places in
>>the code were actions were done if stp_type was equal to mst, so I made
>>some modifications:
>>
>> [root@syslog Netdot]# diff /usr/local/netdot/lib/Netdot/Model/Device.pm
>>/usr/local/src/netdot-1.0.4/lib/Netdot/Model/Device.pm
>> 810c810
>> <
>> if ( $dev{stp_type} eq 'ieee8021d' || $dev{stp_type} eq 'mst' ||
>>$dev{stp_type} eq 'mstpOperation' ){
>> ---
>> >
>> if ( $dev{stp_type} eq 'ieee8021d' || $dev{stp_type} eq 'mst' ){
>> 819c819
>> <
>> if ( $dev{stp_type} eq 'mst' || $dev{stp_type} eq 'mstpOperation' ){
>> ---
>> >
>> if ( $dev{stp_type} eq 'mst' ){
>> 1071c1071
>> <
>> if ( $dev{stp_type} eq 'mst' || $dev{stp_type} eq 'mstpOperation' ){
>> ---
>> >
>> if ( $dev{stp_type} eq 'mst' ){
>> [root@syslog Netdot]#
>>
>> And now the HP devices do show up in the Spanning Tree Graph
>>
>> But Now I?m still facing another issue I don?t understand, while the
>>Topology maps do look fine, the Spanning Tree Graph is missing lots of
>>links, there are devices on the map without a single link, while the
>>trunk ports (uplink to the above switch) are properly shown in the
>>device icon on the map. Looking at the device interfaces tab all
>>neighbor are shown, so I don?t understand why these links are missing.
>>So now I?m trying to debug this but so far I did not succeed (my perl
>>knowledge is very basic)
>>
>> Can anyone give me some hints on how to debug this?
>>
>> Any comment is welcome
>>
>>
>> Thanks in advance,
>>
>> Kristof Van Doorsselaere
>> Hoofdmedewerker server- en netwerkbeheer
>> ----------------------------------
>>
>> Hogeschool Gent
>> Cel Netwerk- en Serverbeheer
>>
>> Valentin Vaerwyckweg 1 - Schoonmeersstraat 52
>> 9000 Gent
>> Belgium
>> mailto:[email protected]
>> _______________________________________________
>> Netdot-users mailing list
>> [email protected]
>> https://osl.uoregon.edu/mailman/listinfo/netdot-users
>
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 64, Issue 10
********************************************
