SNMP Problems

Discussions for BiPAC 7700 series: 7700N
Post Reply
l2kphil
Posts: 3
Joined: Sat Oct 06, 2012 6:38 pm

SNMP Problems

Post by l2kphil » Sat Oct 06, 2012 6:52 pm

Hi All:

Just bought myself a 7700N, the firmware version is reported as B038_N28_GH_UK-00-2426. I'm having a problem with querying it using SNMP. I've set the community read/write strings to something other than the default in the web gui and enabled SNMP monitoring from the WAN side, since the server that I run Cacti on is in a datacentre in Docklands.

When I run 'snmpwalk -v 2c -c XXX ip.of.my.router', it displays the SNMPV2-MIB values instantly, then gets really slow as it tries to display the IF-MIB parameters:

SNMPv2-MIB::sysDescr.0 = STRING: BiPAC 7700N
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.4413
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1130085) 3:08:20.85
SNMPv2-MIB::sysContact.0 = STRING: unknown
SNMPv2-MIB::sysName.0 = STRING: My Router
SNMPv2-MIB::sysLocation.0 = STRING: unknown
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1130100) 3:08:21.00
SNMPv2-MIB::sysORID.1 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (0) 0:00:00.00 <-- 1 second pause here
IF-MIB::ifNumber.0 = INTEGER: 8
IF-MIB::ifIndex.1 = INTEGER: 1 <-- 1 second pause here too
IF-MIB::ifIndex.2 = INTEGER: 2 <-- 2 second pause here
IF-MIB::ifIndex.3 = INTEGER: 3 <-- 2 second pause here
IF-MIB::ifIndex.4 = INTEGER: 4 <-- 5 second pause here
Timeout: No Response from 194.164.144.196

Just in case there was some sort of problem with my DSL connection, I installed an SNMP client on my Win7 laptop. This had the same problem running an snmpwalk against the router from my local LAN.

Looking at the logs while this is happening, I appear to be getting a kernel panic:

Code: Select all

Date/Time 	Facility 	Severity 	Message
Oct 6 18:45:25 	user 	warn 	kernel: ------------[ cut here ]------------
Oct 6 18:45:25 	user 	warn 	kernel: WARNING: at net/core/dev.c:4024 0x801763d8()
Oct 6 18:45:25 	user 	warn 	kernel: Modules linked in:
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_tftp init_addr((null) - (null)), core_addr(c0aca000 - c0aca064)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_irc init_addr((null) - (null)), core_addr(c0ac1000 - c0ac11a8)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_rtsp init_addr((null) - (null)), core_addr(c0ab8000 - c0ab89b8)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_ftp init_addr((null) - (null)), core_addr(c0aae000 - c0aae3dc)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_tftp init_addr((null) - (null)), core_addr(c0aa4000 - c0aa421c)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_irc init_addr((null) - (null)), core_addr(c0a9a000 - c0a9a5f0)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_rtsp init_addr((null) - (null)), core_addr(c0a8f000 - c0a90148)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_ftp init_addr((null) - (null)), core_addr(c0a83000 - c0a83c04)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_pptp init_addr((null) - (null)), core_addr(c0a78000 - c0a78448)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_pptp init_addr((null) - (null)), core_addr(c0a6e000 - c0a6eb04)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat_proto_gre init_addr((null) - (null)), core_addr(c0a63000 - c0a6320c)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_proto_gre init_addr((null) - (null)), core_addr(c0a5a000 - c0a5a8ec)
Oct 6 18:45:25 	user 	warn 	kernel: nfnetlink_queue init_addr((null) - (null)), core_addr(c0a4e000 - c0a4f2c4)
Oct 6 18:45:25 	user 	warn 	kernel: ipt_LOG init_addr((null) - (null)), core_addr(c0a41000 - c0a41d84)
Oct 6 18:45:25 	user 	warn 	kernel: xt_limit init_addr((null) - (null)), core_addr(c0a36000 - c0a362a4)
Oct 6 18:45:25 	user 	warn 	kernel: xt_state init_addr((null) - (null)), core_addr(c0a2c000 - c0a2c108)
Oct 6 18:45:25 	user 	warn 	kernel: ipt_REDIRECT init_addr((null) - (null)), core_addr(c0a23000 - c0a230fc)
Oct 6 18:45:25 	user 	warn 	kernel: ipt_MASQUERADE init_addr((null) - (null)), core_addr(c0a1a000 - c0a1a6d0)
Oct 6 18:45:25 	user 	warn 	kernel: iptable_nat init_addr((null) - (null)), core_addr(c0a07000 - c0a0789c)
Oct 6 18:45:25 	user 	warn 	kernel: nf_nat init_addr((null) - (null)), core_addr(c09fa000 - c09fc514)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack_ipv4 init_addr((null) - (null)), core_addr(c09ea000 - c09eb5ec)
Oct 6 18:45:25 	user 	warn 	kernel: nf_defrag_ipv4 init_addr((null) - (null)), core_addr(c09dc000 - c09dc0ec)
Oct 6 18:45:25 	user 	warn 	kernel: nf_conntrack init_addr((null) - (null)), core_addr(c09c9000 - c09d149c)
Oct 6 18:45:25 	user 	warn 	kernel: nfnetlink init_addr((null) - (null)), core_addr(c09ac000 - c09ac514)
Oct 6 18:45:25 	user 	warn 	kernel: xt_SKIPLOG init_addr((null) - (null)), core_addr(c09a2000 - c09a203c)
Oct 6 18:45:25 	user 	warn 	kernel: xt_TCPMSS init_addr((null) - (null)), core_addr(c0999000 - c09995cc)
Oct 6 18:45:25 	user 	warn 	kernel: iptable_mangle init_addr((null) - (null)), core_addr(c073b000 - c073b204)
Oct 6 18:45:25 	user 	warn 	kernel: xt_multiport init_addr((null) - (null)), core_addr(c0731000 - c07314a8)
Oct 6 18:45:25 	user 	warn 	kernel: xt_MARK init_addr((null) - (null)), core_addr(c0727000 - c0727114)
Oct 6 18:45:25 	user 	warn 	kernel: xt_mark init_addr((null) - (null)), core_addr(c071e000 - c071e078)
Oct 6 18:45:25 	user 	warn 	kernel: xt_mac init_addr((null) - (null)), core_addr(c0715000 - c0715088)
Oct 6 18:45:25 	user 	warn 	kernel: xt_DSCP init_addr((null) - (null)), core_addr(c070c000 - c070c440)
Oct 6 18:45:25 	user 	warn 	kernel: xt_dscp init_addr((null) - (null)), core_addr(c0702000 - c0702154)
Oct 6 18:45:25 	user 	warn 	kernel: iptable_filter init_addr((null) - (null)), core_addr(c06f0000 - c06f00e4)
Oct 6 18:45:25 	user 	warn 	kernel: ip_tables init_addr((null) - (null)), core_addr(c06e4000 - c06e6058)
Oct 6 18:45:25 	user 	warn 	kernel: bcmvlan(P) init_addr((null) - (null)), core_addr(c0680000 - c0688774)
Oct 6 18:45:25 	user 	warn 	kernel: wl(P) init_addr((null) - (null)), core_addr(c0425000 - c052b52c)
Oct 6 18:45:25 	user 	warn 	kernel: bcm_enet(P) init_addr((null) - (null)), core_addr(c0128000 - c01384e0)
Oct 6 18:45:25 	user 	warn 	kernel: adsldd(P) init_addr((null) - (null)), core_addr(c00cd000 - c00ef778)
Oct 6 18:45:25 	user 	warn 	kernel: bcmxtmcfg(P) init_addr((null) - (null)), core_addr(c0068000 - c00703c0)
Oct 6 18:45:25 	user 	warn 	kernel: pktflow(P) init_addr((null) - (null)), core_addr(c0043000 - c0046950)
Oct 6 18:45:25 	user 	warn 	kernel:
Oct 6 18:45:25 	user 	warn 	kernel: Call Trace:[<80016e9c>] 0x80016e9c
Oct 6 18:45:25 	user 	warn 	kernel: [<80016e9c>] 0x80016e9c
Oct 6 18:45:25 	user 	warn 	kernel: [<80037290>] 0x80037290
Oct 6 18:45:25 	user 	warn 	kernel: [<801763d8>] 0x801763d8
Oct 6 18:45:25 	user 	warn 	kernel: [<801763d8>] 0x801763d8
Oct 6 18:45:25 	user 	warn 	kernel: [<80160660>] 0x80160660
Oct 6 18:45:25 	user 	warn 	kernel: [<80098398>] 0x80098398
Oct 6 18:45:25 	user 	warn 	kernel: [<800984a0>] 0x800984a0
Oct 6 18:45:25 	user 	warn 	kernel: [<80161994>] 0x80161994
Oct 6 18:45:25 	user 	warn 	kernel: [<8008b71c>] 0x8008b71c
Oct 6 18:45:25 	user 	warn 	kernel: [<801618ac>] 0x801618ac
Oct 6 18:45:25 	user 	warn 	kernel: [<80161a10>] 0x80161a10
Oct 6 18:45:25 	user 	warn 	kernel: [<80098aac>] 0x80098aac
Oct 6 18:45:25 	user 	warn 	kernel: [<801625c8>] 0x801625c8
Oct 6 18:45:25 	user 	warn 	kernel: [<80087aa0>] 0x80087aa0
Oct 6 18:45:25 	user 	warn 	kernel: [<800121b0>] 0x800121b0
Oct 6 18:45:25 	user 	warn 	kernel:
Oct 6 18:45:25 	user 	warn 	kernel: ---[ end trace 908fd84d474392ff ]---
Anybody got any idea what's going on? Have I been sent a duff router?

l2kphil
Posts: 3
Joined: Sat Oct 06, 2012 6:38 pm

Re: SNMP Problems

Post by l2kphil » Tue Oct 16, 2012 8:11 pm

Just an update on this in the hope that it will help someone else. I logged this with Billion support to see if they had any suggestions. After a few e-mails were exchanged between us, they came back with the following:
HI Phil

After speaking to our engineers they have stated this issue is a performance limitation.

They have forwarded the issue over to the chipset vendor (Broadcom) so see if they can enhance the function, but have not stated a time scale for the fix.
So it looks like the 7700N is not powerful enough to allow you to make us of its SNMP feature, which is a shame because it's the one thing I wanted to be able to do with it. I've decided to return it to the retailer that I bought it from for a refund and get something else instead.

Post Reply