BSR2K reload issue | docsis.org

You are here

BSR2K reload issue

3 posts / 0 new
Last post
cabo81
BSR2K reload issue

Hi group

Happy Holidays in case I don't write you anymore :-)

We had an issue yesterday with the BSR2K. The device rebooted without any aparently reason. I post an extract of the log. I would like if you guys help me to "translate" this log.

[01/01-00:00:06.40:telnet02]-N-connection made from 190.97.201.105 on session 02

[01/01-00:00:05.20:MemChk]-N-MemChk.1 Task tRDNts000004 (taskId
0x125f92c0) is dead and possibly leaked memory

[01/01-00:00:05.20:tRDNts000004]-N-Shell forced to exit

[01/01-00:00:05.15:LOG]-N-telnet: 912 (0x3c)

[01/01-00:00:07.92:LOG]-N-telnet: 912 (0xd0003)

[01/01-00:00:07.84:tRDNts000002]-N-session 02 disconnected

[01/01-00:00:02.45:telnet03]-N-user enabled-user authenticated

[02/06-06:28:15.39:telnet03]-N-connection made from 190.97.201.105 on session 03

[01/01-00:00:04.09:LOG]-N-telnet: 912 (0xd0003)

[01/01-00:00:04.09:tRDNts000003]-N-session 03 disconnected

[01/01-00:00:00.00:telnet03]-N-user enabled-user authenticated

[01/01-00:00:07.44:telnet03]-N-connection made from 190.97.201.105 on session 03

[01/01-00:00:07.54:telnet02]-N-user enabled-user authenticated

[01/01-00:00:03.84:telnet02]-N-connection made from 190.97.201.4 on session 02

[01/01-00:00:03.85:telnet01]-N-user enabled-user authenticated

[02/06-06:28:15.60:telnet01]-N-connection made from 190.97.201.29 on session 01

[02/06-06:28:15.75:SPECMGR]-N-Set to new frequency 36000000 for
channel ifIndex=0x00cd0084, slot=0, usPort=1

[02/06-01:28:39.08:console]-N-reload reason: power reset

[02/06-01:28:39.08:console]-N-configuration change by [console]:
enable rdn-process

[02/06-01:28:39.08:console]-N-configuration change by [console]:
logging facility local7

I have two things which worry me.

[01/01-00:00:05.20:MemChk]-N-MemChk.1 Task tRDNts000004 (taskId
0x125f92c0) is dead and possibly leaked memory
[01/01-00:00:05.20:tRDNts000004]-N-Shell forced to exit

[02/06-06:28:15.75:SPECMGR]-N-Set to new frequency 36000000 for
channel ifIndex=0x00cd0084, slot=0, usPort=1
[02/06-01:28:39.08:console]-N-reload reason: power reset

This could be an hardware issue? The power output it seems fine and also temperature (24 celsius degrees). What could be the possible cause for this unsual reboot?

Thanks in advanced

cmcaldas
re reboot

could be due to a few things. first, noticed your time is not set. if your running modems with bpi+, you should configure an sntp server.
do you run telnet scripts? see sessions and forced to exit, too many will cause a memory leak that could be part of the problem. last thing would be to test the unit with a ups. slight changes in voltage can cause it to reset. had a unit connected to a ups and when the power went out, the ups was a little slow and caused a reset. replaced the ups and has been fine since.

~Carl

cabo81
SYSLOG server for BSR2K

Hi group

Thanks again for your post cmcaldas. Well I have many suspects and one you're telling me is UPS. Despite of we have a super UPS, (I'm not an electrician, but when the power is down, the UPS jump on inmediatly) I think there's something about electric installations on the head-end, I don't know why, I don't know how, but I think is possible what you're telling me about the UPS or something related to.

I don't run telnet scripts. I only use telnet for access to cmts. I don't know why those forced exit. I will look up more about this.

I'm in the process of configuring the sntp server despite of I don't have BPI+ on my cable modems on and on the process of more detail SYSLOG server. One question.... Is cmts capable to give me all detail information such as cablemodem ranging, frequency variations, all detail to a SYSLOG server? I have the following configuration but I can't get more detail information like every time a modem makes ranging process.

logging buffered 51200
no logging control docsis
logging admin-status unconstrained
logging rate-limit 100 1
logging reporting warning local-syslog
logging reporting notice local-syslog
logging buffered notifications
logging console errors

!
logging on
logging trap notifications
logging snmp-trap notifications
logging facility local7
logging 190.97.201.29
logging 10.1.46.239
!

I'm using syslog on Ubuntu and Kiwi on windows.

I really appreciate your posts again.

Thanks

Log in or register to post comments