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. cisco cat 37xx / forwarding table for vlan        interfaces?
      (Alexander Bochmann)
   2. Re: cisco cat 37xx / forwarding table for vlan    interfaces?
      (Carlos Vicente)
   3. Re: cisco cat 37xx / forwarding table for vlan interfaces?
      (Alexander Bochmann)
   4. Re: cisco cat 37xx / forwarding table for vlan    interfaces?
      (Carlos Vicente)
   5. Re: cisco cat 37xx / forwarding table for vlan    interfaces?
      (Carlos Vicente)


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

Message: 1
Date: Thu, 31 Oct 2013 11:18:54 +0100
From: Alexander Bochmann <[email protected]>
Subject: [Netdot-users] cisco cat 37xx / forwarding table for vlan
        interfaces?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Hi,

with our 3750X switches, I just noticed that netdot only seems to get 
FWT table entries for VLAN 1, even though the systems have several IP 
interfaces (interface Vlan xxx) - and on the console, I see associated 
ARP entries for hosts in the respective subnets.

Is that an expected result, or is it more likely I'm doing something 
wrong on my side?

Alex.



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

Message: 2
Date: Thu, 31 Oct 2013 09:10:31 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] cisco cat 37xx / forwarding table for vlan
        interfaces?
To: Alexander Bochmann <[email protected]>,
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

You mention both FWT entries and ARP entries, which are different
things. In any case, Netdot should be able to pull the info out of every
VLAN.

It's hard to tell without more information. Send the output of:

updatedevices.pl -IFA -d -H <host>

cv

On 10/31/13, 6:18 AM, Alexander Bochmann wrote:
> Hi,
>
> with our 3750X switches, I just noticed that netdot only seems to get 
> FWT table entries for VLAN 1, even though the systems have several IP 
> interfaces (interface Vlan xxx) - and on the console, I see associated 
> ARP entries for hosts in the respective subnets.
>
> Is that an expected result, or is it more likely I'm doing something 
> wrong on my side?
>
> Alex.
>
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users



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

Message: 3
Date: Thu, 31 Oct 2013 15:13:59 +0100
From: Alexander Bochmann <[email protected]>
Subject: Re: [Netdot-users] cisco cat 37xx / forwarding table for vlan
        interfaces?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Hi,

...on Thu, Oct 31, 2013 at 09:10:31AM -0400, Carlos Vicente wrote:

 > You mention both FWT entries and ARP entries, which are different
 > things. In any case, Netdot should be able to pull the info out of every
 > VLAN.

Oh, ok. I naively thought that basically ARP info is what fills the 
forwarding table.

 > It's hard to tell without more information. Send the output of:
 > updatedevices.pl -IFA -d -H <host>

I can send the full output offlist, but this is where it fails:

 > [..]
 > DEBUG - Device::_walk_fwt: c37-switch.intern: 10113 (GigabitEthernet1/0/13) 
 > -> A418759F4DC0
 > DEBUG - c37-switch.intern supports Cisco community string indexing. 
 > Connecting to each VLAN
 > DEBUG - Device::get_snmp_session: Trying SNMPv3 session with 10.48.46.18
 > SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
 > SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
 > ERROR - c37-switch.intern: SNMP error for VLAN 350: 
 > Device::get_snmp_session: 10.90.20.18: SNMPv3 failed
 > DEBUG - Device::get_snmp_session: Trying SNMPv3 session with 10.48.46.18
 > SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
 > SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
 > ERROR - c37-switch.intern: SNMP error for VLAN 354: 
 > Device::get_snmp_session: 10.90.20.18: SNMPv3 failed
 > DEBUG - Device::get_snmp_session: Trying SNMPv3 session with 10.48.46.18
 > SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
 > SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
 > ERROR - c37-switch.intern: SNMP error for VLAN 355: 
 > Device::get_snmp_session: 10.90.20.18: SNMPv3 failed
 > DEBUG - Device::get_snmp_session: Trying SNMPv3 session with 10.48.46.18
 > SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
 > SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
 > ERROR - c37-switch.intern: SNMP error for VLAN 356: 
 > Device::get_snmp_session: 10.90.20.18: SNMPv3 failed
 > DEBUG - c37-switch.intern: FWT fetched. 52 entries in 1 sec
 > INFO - c37-switch.intern: FWT fetched. 52 entries in 1 sec
 > DEBUG - c37-switch.intern: Updating Forwarding Table (FWT)
 > DEBUG - c37-switch.intern: Updating Forwarding Table (FWT)
 > DEBUG - PhysAddr::fast_update: Updating MAC addresses in DB
 > DEBUG - PhysAddr::fast_update: Done Updating: 52 addresses in 0 sec
 > DEBUG - c37-switch.intern: FWT updated. 52 entries in 0 sec
 > DEBUG - c37-switch.intern: Fetching ARP cache via SNMP
 > SNMP::Info::_load_attr orig_at_paddr : IP-MIB::ipNetToMediaPhysAddress : 
 > .1.3.6.1.2.1.4.22.1.2
 > DEBUG - Device::_validate_arp: c37-switch.intern: valid: 656 -> 10.10.12.1 
 > -> 2C542DEEE1C3
 > [..]

I'll try to find out why that happens, while everything else seems to work fine.

Thanks,

Alex.



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

Message: 4
Date: Thu, 31 Oct 2013 12:13:59 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] cisco cat 37xx / forwarding table for vlan
        interfaces?
To: Alexander Bochmann <[email protected]>,
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Hi Alexander,

On 10/31/13, 10:13 AM, Alexander Bochmann wrote:
> I can send the full output offlist, but this is where it fails:
>
>  > [..]
>  > DEBUG - Device::_walk_fwt: c37-switch.intern: 10113 
> (GigabitEthernet1/0/13) -> A418759F4DC0
>  > DEBUG - c37-switch.intern supports Cisco community string indexing. 
> Connecting to each VLAN
>  > DEBUG - Device::get_snmp_session: Trying SNMPv3 session with 10.48.46.18
>  > SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
>  > SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : 
> .1.3.6.1.2.1.1.1.0
>  > ERROR - c37-switch.intern: SNMP error for VLAN 350: 
> Device::get_snmp_session: 10.90.20.18: SNMPv3 failed
>  >

I see it's probably a bug in how the SNMP parameters are passed on
inside the Device class.

I imagine that you are running the latest (1.0.4). There have been many
changes towards 1.0.5, and I wonder if the problem persists. I'd like to
know before I release it, but I don't have a SNMPv3 enabled Cisco switch
right at this moment to check.

In the meantime, if you have time to test, the latest development
snapshot is at:

https://github.com/cvicente/Netdot/archive/netdot-1.0.zip

Let me know.

cv


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

Message: 5
Date: Thu, 31 Oct 2013 14:20:13 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] cisco cat 37xx / forwarding table for vlan
        interfaces?
To: Alexander Bochmann <[email protected]>,
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

On 10/31/13, 12:13 PM, Carlos Vicente wrote:
> I imagine that you are running the latest (1.0.4). There have been many
> changes towards 1.0.5, and I wonder if the problem persists. I'd like to
> know before I release it, but I don't have a SNMPv3 enabled Cisco switch
> right at this moment to check.
I was able to test this and the bug is still there. I will try to fix
and release soon.

Thanks for the report.

cv


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

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


End of Netdot-users Digest, Vol 59, Issue 8
*******************************************

Reply via email to