TTY spitting out IOD365 error and pointing to IP asddress of TM

[cynlaw1]

% IOD365 Data send failed, retry timeout,
% addr=10.120.100.234, sCount=3, rCount=0.
%
% IOD370 10.120.100.234
%
% IOD365 Data send failed, retry timeout,
% addr=10.120.100.234, sCount=3, rCount=0.
Receiving this error continuouly on my TTY terminal. Checked TM for DBA and call collection and costing and no errors. How do I troubleshoot this to resolve?

 

[bdmcdonald99]

IOD365 Network connection lost. Buffering data to memory and storage device
IOD370 Network connection re-established

Looks like a data connectivity issue to me. Check your patch cords, switch ports etc.

It's a phone system, NOT a clock!

 

[Firebird Scrambler]

Here are a few answers below

Symptoms:
Error 'Connection to XXX.XXX.XXX.XXX. failed. Retry?'

Cannot connect via DBA.
Station retrieval through ethernet works.
Can login into switch through ethernet.
Can access switch over ethernet using Overlay Passthru.
DBA application can connect to another PBX.
IOD370 Buffer has resumed normal operation. This message is output after DBA has recovered from the error conditions described by IOD0365.
IOD365 Network connection lost. Buffering data to memory and storage device.

Fix:
To resolve try the following: 1) Verify that within PBX BDI = YES, CDR BUF = YES, TRF BUF = YES 2) Verify that 2 PTYs programmed and USER = MTC SCH BUG 3) Verify that the PTYs are not being used, LD 32 STAT (the programmed PTYs should say DSBL if they are not in use) 4) Try to resolve any possible corruption with the current PTY programming. OUT each PTY and rebuild them within LD 17. 5) Schedule an INI of the PBX. 6) Ensure correct DBA patch is installed in the Option11.

####################################################

mplr16561 rls 25.40, 25.40B

Symptoms:
DBA Buffer exceeding limits.
DBA buffer is 100% full.
Buffer is not cleared even when the DBA session is re-established.
DBA collection stopped.
DBA session connection goes up and down.
Error: DBA00003 Data session failed.
Error: IOD365 - Network connection lost. Buffering data to memory and storage device.
Error: IOD370 - Network connection re-established.

Cause:
In fact, the system stops writing DBA data to HDD when the limit is reached. The global variable nFreeSpace is assigned to represent an available disk space for DBA buffer. The root cause of the problem is that the system incorrectly calculates the value of the variable nFreeSpace. After the system wrote DBA data to HDD, it decrements the variable nFreeSpace to the amount of written bytes. Such calculation is carried out without any correspondence to the real free disk space. The system continues writing DBA data to HDD while the variable nFreeSpace is larger than zero. But if there is not enough disk space, the system will attempt to write data to HDD but the function write will always fail. In this case the INI is possible as a result.

Fix:

Install patch MPLR16561. Refer to Product Advisory PAA-2003-0360.

If the buffered data is still not being cleared, terminate the actual DBA session in OTM as well as the DBA application. Launch DBA and create a new session. If this does not resolve the problem, the old files in the DBA directory may have to be removed manually.

NOTE: some sites are still experiencing the IOD365 and IOD370 messages even with the patch installed. CR Q00711471 was raised to investigate this issue, and it was found that an OTM patch is required as well. A fix has been integrated into OTM 2.10. If you are running OTM 2.00.50 or OTM 2.01.37, patches are available from Nortel Networks Customer Support as 20050p28 and 20137p08 (these are controlled patches that will be integrated into a Service Update (delivery date not known at the time of writing this solution).


###############################################

Patch mplr20359 for 04.50W

Problem Description
----------------------------------
DBA has been configured on OTM to collect CDR info. If we use the STAT BUF command in LD 117 the CDR buffer never shows less than 96.5% full.

When STAT BUF is entered we are seeing the following response:
ld 117
OAM000

=> stat buf

CDR ENL
TRF DIS
STN DIS
Storage space is 96.5% full
Connected to 172.18.18.200

We are also seeing IOD365 alarm listed in history file which may indicate LAN failure although there is no indication that this is the case. The Field engineer has also observed IOD366-IOD370 alarms indicating buffer overflow and reset.

IOD365 Data send failed, retry timeout,
addr=172.18.18.139, sCount=3, rCount=0.

IOD370 172.18.18.139

IOD365 Data send failed, retry timeout,
addr=172.18.18.139, sCount=3, rCount=0.
and
31/10/2006 16:10:26 BUG2587 DR: Can't take drBlockSem [0x4a4c9e0], errno [0x3d00
04].
31/10/2006 16:10:36 BUG2587 DR: Can't take drBlockSem [0x4a4c9e0], errno [0x3d00
04].

I have checked smp_db in pdt and there multiple files dating back to February, so it looks like these are not being deleted, these are listed in the attachment.

This patch will delete all DBA files that are greater than 3 days old.
The patch will do this one of two different ways:
- Automatically every hour after task tDbaFile was initiated, in other words, automatically in 60 minute intervals.
- Manually by loading overlay 117 and using the command 'stat buf'.

########################################################

OTM 2.20.78 SU5

When this Service Update (SU5) is installed, it will clear out the patch history in the OTM Patch Utility and inserts itself into the patch history. Therefore once this Service Update is installed, only two items will be listed in the patch history of this service update (22078su5a and 22078su5b).
22078su5a is required to address issues with the patch utility.
22078su5b is the content fixes for OTM.
• This SU assumes that OTM 2.2 GA (2.20.78) has been installed.
• This SU should be installed on both the OTM Server and Clients.

Recommended Action
• Do not uninstall any other OTM 2.2 patches you have currently installed.
• Download and install SU5 for OTM 2.2 from the Patching Toolkit page:-

http://patchingtoolkit.nat.bt.com/core-support/OTM_2/index.html

This Service Update is installed by following these steps: (in the order presented)
1) Terminate OTM
2) Stop OTMWatchdog service
3) Launch the Patch Utility
4) Install 22078SU5a
5) Reboot the PC
6) Install 22078SU5b
7) Reboot the PC

Instructions for uninstalling the Service Update: (in the order presented)
1) Terminate OTM
2) Stop OTMWatchdog Service
3) Launch the Patch Utility
4) Rollback 22078SU5b
5) Reboot the PC


Important Notes about Specific CRs contained in this Service Update 1
------------------------------------------------------------------------------------
Q00965039 CUR records are remaining in the database after synchronize
Refer to separate file UsingCURRecordCleanUpTool_v1.doc for usage information.
UsingCURRecordCleanUpTool_v1.doc is included in the 22078su4.exe zipped file.
The tool cleans up the database from
a) CUR Records that do not map to CHG / RPL / SWP Records.
b) Extra CUR records in Station Administration that do not point to any other record.

Q00970709 Publish flag on multiple appearance DN's causes LDAP synch error
Rule 1: Only extension assets marked 'Prime' can be marked 'Publish'
Rule 2: Only ONE extension asset per entity may be marked 'Publish'.

Q01059050 Help for alarm message QoS0028 should be displayed in Alarm Notification Window
In order to display the help messages correctly, Java Plug-In cache needs to be cleared.
Steps for clearing Java Plug-In cache are listed below.
1) Launch Java Plug-in from Windows Control Panel
2) In the Java Control panel click on the Cache tab.
3) Click on Clear button to clear the cache.
4) Close Java Plug-in Control Panel and restart internet explorer.

Q00986675 Corporate Directory unable to add leading zeros
Feature has been incorporated to give the user the option to open the file in Excel or WordPad. If user wants to preserve leading zeros the file should be opened\saved in WordPad. A Dialog Bar with two Radio Buttons has been added in the Corporate Directory main window. The user can select any one to open file or generate reports in either Excel or WordPad.
Known Issue: Do not use quotes ('') while editing 'Include DNs' and 'Exclude DNs' csv files under M1 Corporate Directory Option tab using WordPad.
Workaround:
Use Last Name, First Name, PrimeDN, LDN, CNUM, Department, Site\System
Instead of 'Last Name', 'First Name', 'PrimeDN', 'LDN', 'CNUM', 'Department', 'Site\System'

Change Requests (CRs) Fixed by Service Update SU5:
------------------------------------------------------------------
1. Q00895704 Scheduler stops
2. Q00946387 User cannot edit or add sets with loop value higher than 156
3. Q00946387-01 Global Update lsc to lsc not permitted
4. Q00951869 Proper update to link to directory after location change
5. Q00955938 Incomplete ITG SNMP traps being sent to OTM
6. Q00965039 CUR records are remaining in the database after synchronize
7. Q00970709 Publish flag on multiple appearance DN's causes LDAP synch error
8. Q00975971-01 FTR Hot D Key is not retrieved on digital sets
9. Q00980387 Global Update fails on keys 27/28 for CLT and RLT on 3904 Sets
10. Q00983837 Issues with User Account creation
11. Q00985507 Pollcat III Buffer Box does not clear memory after collection
12. Q00986675 Corporate Directory unable to add leading zeros
13. Q00989446-02 Multi User - get server busy error
14. Q00998364 Unable to set CLS LMPX for 390x sets
15. Q00999922 Web clients appear to freeze when Web TBS report is requested
16. Q01001899 For no apparent reason we see a DBA error - Operation time out.
17. Q01006454 Station retrieve does not work for all CLS
18. Q01009644 Scheduler can not launch task with leading space in name
19. Q01010667 Can not delete Corp Report with an Apostrophe in name
20. Q01013748 CRS Rollup Reports are blank
21. Q01024833 List Manager retrieval issues
22. Q01029461 Files are incorrectly installed on the Client
23. Q01036760 Mail Server Configuration cannot be removed
24. Q01038377 CH D and Hot D Key not retrieve correctly
25. Q01039839 Can not program SCC on key 23 of 3900 set in templates without a number
26. Q01048607 Mail Server Configuration Issues in TBS
27. Q01055321 Unable to retrieve ESN Datablock
28. Q01055749 Unable to retrieve HOT D key assignment info
29. Q01056895 Extension Detail report does not show internal calls
30. Q01059050 Help for alarm message QoS0028 should be displayed in Alarm Notification Window.
31. Q01059692 Traffic not reporting ISA Peg Counts
32. Q01064607 Auto sync dialog doesn’t pop up in maintenance mode for CPND name changes
33. Q01074675 Replace functionality under TBS--GCAS doesn't operate as intended
34. Q01084524 SWAP function in 2.2 does not have any status change in CPND module
35. Q01107338 SBC Datacomm/OTM2.20.78/Unable to transmit ESN
36. Q01137023 Can not configure Ringing instead of Buzzing on i2004 set
37. Q01134823 Cannot add HFA to CLS for a i2033 set in OTM
38. Q00990935 Unable to retrieve AUTH code when SPWD configured
39. Q01133477 OTM default CLS VOUA incorrect for CS1K 04.00t
40. Q01079631 After Swap, Employee Editor continues to show the original TN as asset
41. Q01106298 OBV key cannot be added in Station or Global Update
42. Q00645071 Unable to 'Select All' in the OTM Directories
43. Q01105521 Concurrency, FTP standard compliant on Release 4.5
44. Q01090836 OTM Call Tracking: Alarms-Detail File Response contains error.
45. Q01100952 Set with AUTH does not get parsed properly
46. Q01085977 OTM DNIS IDC names appears twice in CPND block.
47. Q01092765 CRS reports are not correct
48. Q01049546 Password Complexity for TM. All characters,upper case, lower case and special characters will be supported for OVL username and password.
49. Q01131791 System terminal login always fail if invalid password was previously entered.
50. Q01094261 IPL4.5 needs concurrency support on OTM 2.2
51. Q01153481 OTM 2.2 support for SIP CTI and Converged Office feature (Alliance feature).
52. Q01192155 Primus: NORT217668 : Error: You have exceeded the maximum license for this product
53. Q01109992 Changing SCR DN to MCR DN of same number generates errors
54. Q01166733 Loss of CPND name in case of phone set TN change
55. Q01149154 Can not download speed call list from succession 3 PBX via modem.
56. Q01153381 OM report - report contains no information from ITG Card
57. Q01274394 User cannot perform EDD for the system
58. Q00839332 Modem is not disconnected when the parse begins
59. Q00958283 Cannot add value to Additional Info after upgrade from OTM2.20.60 to OTM2.20.66
60. Q01272549 Retrieving IPL 3.1 configuration with OTM 2.20.78 SU3 failed
61. Q01192090-01 Need send bye at the end of the FTP session with the CS
62. Q01245726 OTM CONNECTION TO ODBC CAN NOT BE SETUP
63. Q01235644 No info displayed in the reports of IP Telephony
64. Q01218631 Cannot Access DBA application with Release OTM 2.2 SU3 and CS1000 R4.5
65. Q01031047 TBS ERROR WARNING! Type mismatch on ''
66. Q01425967 OTM 2.2 doesn't do a real PBX database disaster backup recovery
67. Q01212380 After IOD365 and IOD370, OTM can fail to collect buffered DBA files.
68. Q01376014 Traffic report are wrong
69. Q01406803 Report is incorrect, value returned is N, it should be Y
70. Q01438294 Changing TDD to ADD in station is not reflected in the PBX
71. Q01462050-01 OTM 2.20.78 and TM 3.00.888 DBA RULEFILES ARE NOT LOADED AUTOMATICALLY
72. Q01414538 Unexpected date format change in TBS export result
73. Q01415872 Primus: NORT253015 : Fails to add all entries during report generation
74. Q01437920 Optivity - Warning table header is incorrect - VoIP Pty Ltd / Unknown

#############################################################




All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.