Hello Support,
The Customer is facing, since DataMiner ver 10 and recently 10.1-Main, some RTE alarms that I cannot track the source and another information to investigate the reason of the alarms. They are affecting some Juniper or Cisco boxes and after a time, the Errors are cleared automatically or they are cleared when the element is restarted. These switches are also being consumed by the new Dashboards and some parameters from them might be available in services. The example below consistis in a Cisco switch C3750 Ver 15.0(2)SE2 using the protocol Cisco Manager preferred ver 3.1.1.96 but this customer is monitoring another models and versions with this or equivalend brand driver.
From alarm console it is displaying:
VM-HEPNIS-DMA01 DataMiner Agent DataMiner run-time DataMiner run-time Thread problem in SLProtocol.exe: [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread Today 9:44:18 AM Today 9:44:18 AM Error 7h 59m 29s 0 None.None.None New alarm Open System Not Assigned WatchDog 19701/17186782 19701/17186782 Today 9:44:18 AM Today 9:44:18 AM No impact 0 0 0
At Watchdog file:
2021-03-17 09:36:47 7576|- (1656) Not signaled 1 (since 2021-03-17 09:29:16): SLProtocol.exe - [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread [pid 148 - thread 13380] [element 19701/9367]
2021-03-17 09:36:47 7576|HALFOPEN RTE: - (1656) Not signaled 1 (since 2021-03-17 09:29:16): SLProtocol.exe - [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread [pid 148 - thread 13380] [element 19701/9367] in Process: SLProtocol.exe for Thread: [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread notificationID created: 5797
2021-03-17 09:44:18 7576|>>>>>>> (1656) THREAD PROBLEM : SLProtocol.exe - [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread [pid 148 - thread 13380] [element 19701/9367]
2021-03-17 09:44:18 7576|Send alarm for process SLProtocol.exe (bSignaled = FALSE, bStopped = FALSE) for iCookie = 1656 (RTE Count = 1)
2021-03-17 09:44:18 7576|** Making minidump ..
2021-03-17 09:44:40 7576|** Making minidump C:\Skyline DataMiner\Logging\MiniDump\2021_03_17 09_44_18_mini_SLProtocol.exe.zip finished.
2021-03-17 09:44:40 7576|OPEN RTE: Thread problem in SLProtocol.exe: [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread on agent VM-HEPNIS-DMA01 in Process: SLProtocol.exe for Thread: [CISCO Manager/3.1.1.96] t-br-pr-pnis-tp-smi-14 - ProtocolThread with notificationID: 5797
At Errors log:
Nothing found related to it
At Element Log
2021/03/15 09:31:13.606|SLManagedScripting.exe|ManagedInterop|ERR|-1|292|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:31:43.323|SLManagedScripting.exe|ManagedInterop|ERR|-1|175|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:32:13.620|SLManagedScripting.exe|ManagedInterop|ERR|-1|164|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:32:43.346|SLManagedScripting.exe|ManagedInterop|ERR|-1|194|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:33:13.582|SLManagedScripting.exe|ManagedInterop|ERR|-1|143|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:33:43.402|SLManagedScripting.exe|ManagedInterop|ERR|-1|283|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:34:13.627|SLManagedScripting.exe|ManagedInterop|ERR|-1|159|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:34:43.369|SLManagedScripting.exe|ManagedInterop|ERR|-1|271|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:35:13.597|SLManagedScripting.exe|ManagedInterop|ERR|-1|328|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:35:43.446|SLManagedScripting.exe|ManagedInterop|ERR|-1|292|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:36:13.648|SLManagedScripting.exe|ManagedInterop|ERR|-1|220|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:36:43.330|SLManagedScripting.exe|ManagedInterop|ERR|-1|169|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:37:13.581|SLManagedScripting.exe|ManagedInterop|ERR|-1|209|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:37:43.362|SLManagedScripting.exe|ManagedInterop|ERR|-1|292|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:38:13.602|SLManagedScripting.exe|ManagedInterop|ERR|-1|287|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:38:43.408|SLManagedScripting.exe|ManagedInterop|ERR|-1|184|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:39:13.887|SLManagedScripting.exe|ManagedInterop|ERR|-1|169|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:39:43.461|SLManagedScripting.exe|ManagedInterop|ERR|-1|175|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:40:13.978|SLManagedScripting.exe|ManagedInterop|ERR|-1|160|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:40:43.519|SLManagedScripting.exe|ManagedInterop|ERR|-1|158|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:41:13.664|SLManagedScripting.exe|ManagedInterop|ERR|-1|292|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:41:43.430|SLManagedScripting.exe|ManagedInterop|ERR|-1|169|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:42:13.786|SLManagedScripting.exe|ManagedInterop|ERR|-1|283|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:42:43.507|SLManagedScripting.exe|ManagedInterop|ERR|-1|220|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:43:13.631|SLManagedScripting.exe|ManagedInterop|ERR|-1|220|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:43:43.406|SLManagedScripting.exe|ManagedInterop|ERR|-1|164|NotifyProtocol with 220 failed. 0x80040221
2021/03/15 09:44:13.670|SLManagedScripting.exe|ManagedInterop|ERR|-1|280|NotifyProtocol with 220 failed. 0x80040221
The parameter ID 220 is:
<Param id="220">
<Name>Add/Edit VLAN Begin Title</Name>
<Description>Add/Edit VLAN</Description>
<Type>fixed</Type>
<Display>
<RTDisplay>true</RTDisplay>
<Positions>
<Position>
<Page>Modify VLAN</Page>
<Row>0</Row>
<Column>0</Column>
</Position>
</Positions>
</Display>
<Measurement>
<Type options="begin;connect">title</Type>
</Measurement>
</Param>
At the element Data Display, Polling of VLAN Data was disabled and I tried with enable too. But I think this could not be the reason, since the ERROR also occurs at Juniper Switch. At that driver, the ID 220 is "IF Frame Errors IN Count".
At StreamViewer:
No major errors, device communicates without TIMEOUT alarms.
According to this circunstance, I´d be glad if could someone help on how to fix it and avoid further ERRORs alarms on switches.
Hi Henrique,
I believe that the first step to solve this issue will be using the latest driver version available for the Cisco Manager driver. Currently the latest version (for the driver range 3.1.1.x) is 3.1.1.150. You can download the driver:
- From the Catalog (see version history link to download the version 3.1.1.150).
- Via Update Center (see DataMiner Help - Updating protocols with the Update Center)
For you information, the error:
NotifyProtocol with 220 failed. 0x80040221
is not related to the parameter with ID 220, but a NotifyType (a method that can be used in a QAction to set or update one or more table columns with provided values). More information can be found in DataMiner Development Library - NotifyType
Hi Henrique, just FYI, your comment had to go through a manual approval, probably because it contains partial URLs. Normally comments are displayed immediately, but in this case the moderator had to manually approve it before it became visible, hence a small delay…
Hi Henrique,
I made a typo in my answer. Indeed, the driver version is 3.1.1.150 (The answer has been updated). After upgrading the driver, please could you let us know if you are still able to reproduce the issue?
Regarding the issue with the Alcatel driver, similar as the Cisco Manager, please could you let us know if you are using the latest version of the driver?
Thanks Bert.
Hi Miguel, this Element is a Nokia 7750SR using the Alcatel SR Manager protocol 2.0.1.5. I can test it also in the newest version, what do you recommend for this range?
Hi Henrique,
I would recommend the latest version for this range. Currently the latest version is 2.0.1.9.
Thanks Miguel. I Will test another driver version. At catalog, the most recent is the x.150, do you recommend testing the x.50 anyway?
Today morning the other DMA presented also an error alarm on Alcatel element:
VM-HEPNIS-DMAST DataMiner Agent DataMiner run-time DataMiner run-time Thread problem in SLProtocol.exe: [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread Today 10:45:39 AM Today 10:45:39 AM Error 4m 43s 0 None.None.None New alarm Open System Not Assigned WatchDog ….
On watchdog:
2021-03-18 10:38:08 5648|HALFOPEN RTE: – (8670) Not signaled 1 (since 2021-03-18 10:30:37): SLProtocol.exe – [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread [pid 4448 – thread 10964] [element 19704/20929] in Process: SLProtocol.exe for Thread: [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread notificationID created: 8246
2021-03-18 10:45:39 5648|>>>>>>> (8670) THREAD PROBLEM : SLProtocol.exe – [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread [pid 4448 – thread 10964] [element 19704/20929]
2021-03-18 10:45:39 5648|Send alarm for process SLProtocol.exe (bSignaled = FALSE, bStopped = FALSE) for iCookie = 8670 (RTE Count = 1)
2021-03-18 10:45:39 5648|** Making minidump ..
2021-03-18 10:46:06 5648|** Making minidump C:Skyline DataMinerLoggingMiniDump2021_03_18 10_45_39_mini_SLProtocol.exe.zip finished.
2021-03-18 10:46:06 5648|OPEN RTE: Thread problem in SLProtocol.exe: [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread on agent VM-HEPNIS-DMAST in Process: SLProtocol.exe for Thread: [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread with notificationID: 8246
2021-03-18 10:50:22 5648|Send alarm for process SLProtocol.exe (bSignaled = TRUE, bStopped = FALSE) for iCookie = 8670 (RTE Count = 0)
2021-03-18 10:50:22 5648|CLEARED RTE: Runtime error cleared in process SLProtocol.exe on agent VM-HEPNIS-DMAST in Process: SLProtocol.exe for Thread: [Alcatel SR Manager/2.0.1.5m] t-br-pa-blm-ccp-rvsa-01-test – copy – ProtocolThread with NotificationID: 8246
On Element log:
2021/03/18 10:28:11.565|SLManagedScripting.exe|ManagedInterop|ERR|0|102|QA3|Exception on Parse Location Method: System.UriFormatException: Invalid URI: The format of the URI could not be determined.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at http://FTP.FtpManager.ParseLocation(SLProtocol protocol, String sLocation)
2021/03/18 10:28:11.565|SLManagedScripting.exe|ManagedInterop|ERR|0|102|QA3|13099|Run|Exception thrown:
System.NullReferenceException: Object reference not set to an instance of an object.
at QAction.GetAccountingFiles(SLProtocolExt protocol)
2021/03/18 10:28:29.174|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, leaving 1
2021/03/18 10:28:29.174|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, entering 0
2021/03/18 10:49:11.278|SLElement.exe|8752|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 7
2021/03/18 10:50:22.011|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, leaving 0
2021/03/18 10:50:22.011|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, entering 1
2021/03/18 10:50:24.470|SLElement.exe|15596|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 0
2021/03/18 10:51:40.513|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, leaving 1
2021/03/18 10:51:40.513|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, entering 0
2021/03/18 10:51:44.748|SLManagedScripting.exe|ManagedInterop|ERR|0|102|QA3|Exception on Parse Location Method: System.UriFormatException: Invalid URI: The format of the URI could not be determined.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at http://FTP.FtpManager.ParseLocation(SLProtocol protocol, String sLocation)
2021/03/18 10:51:44.749|SLManagedScripting.exe|ManagedInterop|ERR|0|102|QA3|13099|Run|Exception thrown:
System.NullReferenceException: Object reference not set to an instance of an object.
at QAction.GetAccountingFiles(SLProtocolExt protocol)
2021/03/18 10:59:43.122|SLElement.exe|8896|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 7
2021/03/18 11:00:53.722|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, leaving 0
2021/03/18 11:00:53.722|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, entering 1
2021/03/18 11:00:56.195|SLElement.exe|16120|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 0
2021/03/18 11:03:44.129|SLManagedScripting.exe|ManagedInterop|ERR|0|120|QA3|Exception on Parse Location Method: System.UriFormatException: Invalid URI: The format of the URI could not be determined.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at http://FTP.FtpManager.ParseLocation(SLProtocol protocol, String sLocation)
2021/03/18 11:03:44.130|SLManagedScripting.exe|ManagedInterop|ERR|0|120|QA3|13099|Run|Exception thrown:
System.NullReferenceException: Object reference not set to an instance of an object.
at QAction.GetAccountingFiles(SLProtocolExt protocol)
2021/03/18 11:04:07.856|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, leaving 1
2021/03/18 11:04:07.856|SLProtocol – 4448 – t-br-pa-blm-ccp-rvsa-01-test – copy|10964|CProtocol::GetRedundantConnection|DBG|-1|RedundantPolling, change connection, entering 0
This Element is a Nokia 7750SR using the Alcatel SR Manager protocol 2.0.1.5