Project

General

Profile

Bug #10793

SNMP: Netgate SG-3100 shows wrong speed

Added by Grischa Zengel 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
SNMP
Target version:
Start date:
07/28/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.5-p1
Affected Architecture:
SG-3100

Description

I use check_nwc_health for monitoring network interfaces and it shows always over usage (>100%) on interface mvneta1.

The problem is iso.3.6.1.2.1.2.2.1.5.2 shows only 10MBit but should have 100MBit.

iso.3.6.1.2.1.2.2.1.2.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.2.2.1.2.3 = STRING: "e6000sw0port1" 
iso.3.6.1.2.1.2.2.1.2.4 = STRING: "e6000sw0port2" 
iso.3.6.1.2.1.2.2.1.2.5 = STRING: "e6000sw0port3" 
iso.3.6.1.2.1.2.2.1.2.6 = STRING: "e6000sw0port4" 
iso.3.6.1.2.1.2.2.1.2.7 = STRING: "e6000sw0port5" 
iso.3.6.1.2.1.2.2.1.2.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.2.2.1.2.9 = STRING: "enc0" 
iso.3.6.1.2.1.2.2.1.2.10 = STRING: "lo0" 
iso.3.6.1.2.1.2.2.1.2.11 = STRING: "pflog0" 
iso.3.6.1.2.1.2.2.1.2.12 = STRING: "pfsync0" 
iso.3.6.1.2.1.2.2.1.2.13 = STRING: "mvneta2.7" 
iso.3.6.1.2.1.2.2.1.2.14 = STRING: "pppoe0" 
iso.3.6.1.2.1.2.2.1.2.15 = STRING: "ovpns3" 
iso.3.6.1.2.1.2.2.1.2.16 = STRING: "ovpnc1" 
iso.3.6.1.2.1.2.2.1.2.17 = STRING: "ovpnc2" 
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 10000000
iso.3.6.1.2.1.2.2.1.5.3 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.4 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.5 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.6 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.7 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.8 = Gauge32: 1000000000
iso.3.6.1.2.1.2.2.1.5.9 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.10 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.11 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.12 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.13 = Gauge32: 1000000000
iso.3.6.1.2.1.2.2.1.5.14 = Gauge32: 64000
iso.3.6.1.2.1.2.2.1.5.15 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.16 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.17 = Gauge32: 0

mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE>
    media: Ethernet autoselect (none)
    status: no carrier
mvneta1: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=4bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO>
    media: Ethernet 2500Base-KX <full-duplex>
    status: active
mvneta2: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=804bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,LINKSTATE>
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active

1_LAN Interface (lan, mvneta1)
Media 100baseTX <full-duplex>
2020-07-30 21-24-04.png (36.5 KB) 2020-07-30 21-24-04.png Grischa Zengel, 07/30/2020 02:27 PM
2020-07-30 21-24-58.png (23.3 KB) 2020-07-30 21-24-58.png Grischa Zengel, 07/30/2020 02:27 PM
2020-07-30 21-23-29.png (7.55 KB) 2020-07-30 21-23-29.png Grischa Zengel, 07/30/2020 02:27 PM
2020-07-30 21-22-54.png (52.5 KB) 2020-07-30 21-22-54.png Grischa Zengel, 07/30/2020 02:27 PM

History

#1 Updated by Jim Pingle 3 months ago

  • Target version set to 2.5.0

I was able to reproduce this in both bsnmpd and net-snmp, looks like neither one likes the 2.5G uplink speed.

NET-SNMP:

$ snmpwalk -c public -v 1 198.51.100.8 iso.3.6.1.2.1.2.2.1.5
iso.3.6.1.2.1.2.2.1.2.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.2.2.1.2.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 1000000000
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 10000000
iso.3.6.1.2.1.2.2.1.5.8 = Gauge32: 1000000000

$ snmpwalk -c public -v 1 198.51.100.8 iso.3.6.1.2.1.31.1.1.1
iso.3.6.1.2.1.31.1.1.1.1.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.31.1.1.1.1.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.31.1.1.1.15.1 = Gauge32: 1000
iso.3.6.1.2.1.31.1.1.1.15.2 = Gauge32: 10
iso.3.6.1.2.1.31.1.1.1.15.8 = Gauge32: 1000

bsnmpd:
$ snmpwalk -c public -v 1 198.51.100.8 iso.3.6.1.2.1.2.2.1
iso.3.6.1.2.1.2.2.1.2.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.2.2.1.2.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 10000000
iso.3.6.1.2.1.2.2.1.5.8 = Gauge32: 1000000000

$ snmpwalk -c public -v 1 198.51.100.8 iso.3.6.1.2.1.31.1.1.1
iso.3.6.1.2.1.31.1.1.1.1.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.31.1.1.1.1.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.31.1.1.1.15.1 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.15.2 = Gauge32: 10
iso.3.6.1.2.1.31.1.1.1.15.8 = Gauge32: 1000

mvneta0: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    media: Ethernet autoselect (none)
    status: no carrier
mvneta1: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    media: Ethernet 2500Base-KX <full-duplex>
    status: active
mvneta2: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active

Though it's not clear yet what, if anything, we can do about this as it may be an upstream problem in the OS and/or one or both SNMP daemons.

#2 Updated by Grischa Zengel 3 months ago

Is this relevant?
mvneta1 supports only 2500MBit but connects with 100MBit.

mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    supported media:
        media autoselect
        media 1000baseSX mediaopt full-duplex
        media 1000baseSX
        media 1000baseT mediaopt full-duplex,master
        media 1000baseT mediaopt full-duplex
        media 1000baseT mediaopt master
        media 1000baseT
        media 100baseTX mediaopt full-duplex
        media 100baseTX
        media 10baseT/UTP mediaopt full-duplex
        media 10baseT/UTP
        media none
mvneta1: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    supported media:
        media 2500Base-KX mediaopt full-duplex
mvneta2: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
    supported media:
        media autoselect
        media 1000baseSX mediaopt full-duplex
        media 1000baseSX
        media 1000baseT mediaopt full-duplex,master
        media 1000baseT mediaopt full-duplex
        media 1000baseT mediaopt master
        media 1000baseT
        media 100baseTX mediaopt full-duplex
        media 100baseTX
        media 10baseT/UTP mediaopt full-duplex
        media 10baseT/UTP
        media none

#3 Updated by Luiz Souza 3 months ago

  • Status changed from New to Feedback
  • Assignee set to Luiz Souza
  • % Done changed from 0 to 100

Fixed.

Please test with the next snapshot.

#4 Updated by Jim Pingle 3 months ago

  • Status changed from Feedback to Resolved

Looks good now.

iso.3.6.1.2.1.31.1.1.1.1.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.31.1.1.1.1.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.31.1.1.1.15.1 = Gauge32: 0
iso.3.6.1.2.1.31.1.1.1.15.2 = Gauge32: 2500
iso.3.6.1.2.1.31.1.1.1.15.8 = Gauge32: 1000

iso.3.6.1.2.1.2.2.1.2.1 = STRING: "mvneta0" 
iso.3.6.1.2.1.2.2.1.2.2 = STRING: "mvneta1" 
iso.3.6.1.2.1.2.2.1.2.8 = STRING: "mvneta2" 
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 2500000000
iso.3.6.1.2.1.2.2.1.5.8 = Gauge32: 1000000000

#5 Updated by Jim Pingle 3 months ago

Grischa Zengel wrote:

Is this relevant?
mvneta1 supports only 2500MBit but connects with 100MBit.

I do not see anything on 2.4.5-p1 or 2.5.0 which reports 100Mbit/s for mvneta1. For me, both report 2500Base-KX <full-duplex> in the widget and Status > Interfaces, which agrees with ifconfig. I don't see anything in SNMP which reports that value either.

#6 Updated by Grischa Zengel 3 months ago

It looks like it reflects speed from 1st switch port or max link speed on switch.

!2020-07-30 21-24-58.png!
!2020-07-30 21-24-04.png!
!2020-07-30 21-23-29.png!
!2020-07-30 21-22-54.png!

#7 Updated by Jim Pingle 3 months ago

"LAN Uplink" is mvneta1. The others are the individual switch ports, not mvneta* interfaces.

With the built-in bsnmpd it has that interface under iso.3.6.1.2.1.2.2.1.2.3 ("e6000sw0port1") but bsnmpd apparently can't read the speed of the switch ports, which wouldn't be related to this issue. net-snmpd doesn't list them at all. If that's something else you'd like to see, open a new feature request. We can't guarantee it's something we'd be able to address, but we can look into it.

#8 Updated by Grischa Zengel 3 months ago

No, no problem.

But you said mvneta1 is always at 2500MBit but pfsense shows 100MBit like picture 2020-07-30 21-24-04.png shows.

Where is this code? Is this closed source for SG-3100?

#9 Updated by Jim Pingle 3 months ago

That doesn't happen by default. You probably selected "Port 1" as the switch port to monitor under Interfaces > LAN_1 which is probably also not something you want to do. That's intended for setups where you map a switch port to a single VLAN and want the up/down link status of the switch port to be reflected by the assigned interface.

It's not a bug in that case, it's expected since you directed the system to associate the status of switch port 1 with LAN.

#10 Updated by Grischa Zengel 3 months ago

I agree, it's not a bug.
I forgot that this switch config for tracking ports exists because I only used it once at first setup.
I never use internal switch ports on routers if there is a backbone switch. I like to see if the backbone switch is connected and use only LAN1.

I will open a feature request to show the fact that's there a mirror port on mvneta1 in status->interface. I think this will make it more transparent if somebody forget it like me.

Also available in: Atom PDF