Nicolás Victorero

Hello Dennis, Not sure if this will be your problem, but just in case. From time to time I have problems rebuilding IP tree because some device reports an IP...

Got the interface names with this (from validate arp): my %devints; %devints = $self->interfaces; foreach my $int ( $self->interfaces ){ $devints{$int->number} = $int->name; } Now i need to see how...

Got this sorted out with: ``` #Create a hash with vlan=>interface mapping my %vlanints; foreach my $if ( $self->interfaces ){ if ( my @ifv = $if->vlans ){ foreach my $ifv...

Another approach would be to get information about vlans and IPs the F5 has on that vlan in the CLI/F5.pm I'm working on, and populate from there the vlan interfaces...

Still wondering why my production netdot get different information about f5 interfaces. I'm having errors about interface sort. Because of interface number being like "4.48.46.49.48". Using a test script to...

I was checking things, when I run an update on my production machine it sees the same information as the dev one. At least that is consistent with relevant code...

Could not find a tarball with 3.01 version, but with 3.31 the behaviour is the same. Also with 3.35 which contains bugfixes for F5 module. SNMP::Info 3.31 SNMP::Info::device_type() layers:01001110 id:3375...

Figured out what changed, the vlan interfaces are still there at 1.3.6.1.2.1.2.2.1 (ifEntry) and with nice numeric numbering. It is the addition of F5 support to snmp-info what makes it...

Got it working. However it needs you to don't be using SNMP::Info::Layer3::F5.pm. So either you can use an SNMP::Info version prior to 3.01, or (this is what I did), use...

I'm quite sure vink78's solution is better, but just for the record what I did when faced with that problem was installing the .deb from debian jessie and seems to...