thewolfman
Technical User
Has anybody seen these logs in the 3300 recently. Seem to be appearing every 5 minutes or so:
APPSL-SBAVSS getNextMobileDnToBeLoaded>Dn does not exist.
APPSL-SBAVSS getNextMobileDnToBeLoaded>Dn does not exist.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Logs in the 3300
- Thread starter thewolfman
- Start date
- Status
IrwinMFletcher
Programmer
Are there any devices in your system that do not have an associated DN?
My guess is that both of these systems are upgrades?
My guess is that both of these systems are upgrades?
Irwin - I'm Curious. Can you describe a device that does not have an associated DN at any software level?
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
IrwinMFletcher
Programmer
kwb, no, not by conventional means. My guess is that there was a problem with an upgrade/restore.
IrwinMFletcher
Programmer
...or perhaps a device didn't get deleted properly.
Thanks Irwin, I thought for a minute there that I was going crazy. Your explaination is sufficient.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
IrwinMFletcher
Programmer
It may be tedious, but you could go try the LOCATE PLID maintenance command and see if any have a MAC but an invalid Extension.
It was indeed tedious! Not exactly sure what specifically i was looking at, never knew IP devices had PLIDs!
Didnt seem to have any with an Invalid extention. They either had Hotdesk DN and a Mac, Logged in DN and a Mac, or just a standard DN with no Mac.
By invalid, do you mean a number not programmed on our system? as i didnt check that i imagine that would take a while!
Jon
Didnt seem to have any with an Invalid extention. They either had Hotdesk DN and a Mac, Logged in DN and a Mac, or just a standard DN with no Mac.
By invalid, do you mean a number not programmed on our system? as i didnt check that i imagine that would take a while!
Jon
IrwinMFletcher
Programmer
Everything has a plid. IP phones appear as plids off of 'virtual' PERS, just like a DNIC phone would.
By invalid, I was thinking something out of range, so either blank or maybe -1 or 65535.
Is there anything in the logs prior to these logs starting?
By invalid, I was thinking something out of range, so either blank or maybe -1 or 65535.
Is there anything in the logs prior to these logs starting?
Ah okay, thanks for explaining that =]
Nothing invalid like you described, as for the logs, is there somewhere else you can view the logs, other than on the web interface, as the web one seems to only go to 500 pages, and its filled up since the 4th of July (that can't be right?)
It seems to be a mixture of (amoungst others);
The "getNextMobileDnToBeLoaded", "Heartbeat Server - ICP has lost contact with <Various IP Addresses>" or "SAC - SacDevCommsServer> DEV Socket Accept FAILED".
I thought i was reasonably knowledgable with the 3300 but these logs are proving that to be wrong!
Nothing invalid like you described, as for the logs, is there somewhere else you can view the logs, other than on the web interface, as the web one seems to only go to 500 pages, and its filled up since the 4th of July (that can't be right?)
It seems to be a mixture of (amoungst others);
The "getNextMobileDnToBeLoaded", "Heartbeat Server - ICP has lost contact with <Various IP Addresses>" or "SAC - SacDevCommsServer> DEV Socket Accept FAILED".
I thought i was reasonably knowledgable with the 3300 but these logs are proving that to be wrong!
IrwinMFletcher
Programmer
At every 5 mins, just that one log would have been spit out 2304 times in 8 days, so yes, I could see it filling up quickly. Backup software logs are generated at certain instances, and are stored in the /db partition, however they require a special app to read them outside of the MCD. You can try to open them with any text editor, however the formatting will be off, you can however read the text portions, so you may be able to find some info.
The current log file is:
/db/database/files/pstswlog.db2
The backups are at:
/db/database/files/sw_log_backup
You *could* technically find these files and rename them to the original and then use ESM, however that's a last resort kinda thing. If you end up could to support, and the files are out of whack, I'm not sure what they would say/do, so make sure you have a snapshot of the logs.
I'd go back to those backup files and find the first instance of the log, then look at the logs prior to it.
The current log file is:
/db/database/files/pstswlog.db2
The backups are at:
/db/database/files/sw_log_backup
You *could* technically find these files and rename them to the original and then use ESM, however that's a last resort kinda thing. If you end up could to support, and the files are out of whack, I'm not sure what they would say/do, so make sure you have a snapshot of the logs.
I'd go back to those backup files and find the first instance of the log, then look at the logs prior to it.
- Status