We are exploring setting IP inputs on the Proview in DataMiner Cube and noticed that the place where we'd expect the Physical Inputs (IP), GbE Socket In table, is not populated with the 4x IP input sockets.
I can see in the Logical Inputs table the choices for Primary Source has choices IP-1, IP-2, IP-3, IP-4, and I can also see in the protocol stream viewer where it gets the information for the configuration of these, such as:
<GbeSocketIn Id="23000003">
<Attr>
<AdminStatus>1</AdminStatus>
<IsUnicast>0</IsUnicast>
<MulticastIp>232.9.80.36</MulticastIp>
<UdpPort>50000</UdpPort>
<!--None(0) 1D [Columns Only](1) 2D [Rows and Columns](2)-->
<FecMode>0</FecMode>
<!--UDP(0) RTP(1)-->
<RtpReordering>0</RtpReordering>
<NullInsertion>0</NullInsertion>
<!--None(0) Low(1) Normal(2) High(3) SFN(4) T2-MI(5) Customize(255)-->
<DjMode>1</DjMode>
<DjActualDelay>100</DjActualDelay>
<!--NotDefined (-1) Disable (0) All (255)-->
<LocalOverride Internal="true">-1</LocalOverride>
<VirtualInputIndex Internal="true">65535</VirtualInputIndex>
<PhyNum Internal="true">0</PhyNum>
<!--OK(0) Failure(1) Inconsistent Rate(2) Off(3) No PCR(4) Unsupported Rate(5) Illegal PCR Skew(6) No Stream Detected(7) Inconsistent MIP(8) No MIP(9)-->
<DjStatus>0</DjStatus>
<FecColDetected>0</FecColDetected>
<FecRowDetected>0</FecRowDetected>
<NumOfRecoveredPkts>0</NumOfRecoveredPkts>
<NumOfMissingPkts>0</NumOfMissingPkts>
<NumOfOutOfOrderPkts>0</NumOfOutOfOrderPkts>
<NumOfOutOfRangePkts>0</NumOfOutOfRangePkts>
<DetNumOfCols>0</DetNumOfCols>
<DetNumOfRows>0</DetNumOfRows>
<DetTsPerIpPkt>7</DetTsPerIpPkt>
</Attr>
<Ssm Id="81000003">
<Attr>
<SourceIp>10.29.80.13</SourceIp>
</Attr>
</Ssm>
</GbeSocketIn>
Are we just looking in the wrong place or have something misconfigured?
Proview 7100 Firmware 4.3.70.301.6
DataMiner protocol versions tested 4.2.3.15 and 4.2.3.16 (11/2024)
DataMiner version 10.4.11.0-15028
Update #2: I tried going back to protocol version 4.2.3.14 (first to include SSM IP's for IP inputs), no change, and then on a whim went back to 4.2.2.2, and my GbE Socket In Table populated (no SSM info, none expected).
Bumped protocol version back up to current 4.2.3.16 and I had the SSM fields, though not populated – which is manually correctable for now.
Hi Jake,
We had a quick look into this and we would need to run further investigations in order to be able to help you further on this.
Looking at the logs you provided, we can safely assume the connector has some bugs so I would suggest you report the issue by reaching out to our TechSupport.
Here is more info on how to proceed: Contacting tech support | DataMiner Docs.
Regards,
Hi Jake,
This sounds like it might be a bug and would need further investigation. You should raise a UOSA ticket.
Not sure if this has anything to do with the issue, but in the element log at the bottom:
2025/02/11 14:59:03.162|SLElement.exe|16656|CElement::StartFunc|CRU|-1|** Start Complete
2025/02/11 14:59:03.170|SLProtocol – 42776 – NYNY-DR DEC 2_3|17480|CProtocol::StartFunc|CRU|-1|LoadProperties returnes. 0x00000000
2025/02/11 14:59:03.170|SLProtocol – 42776 – NYNY-DR DEC 2_3|17480|CProtocol::Start|CRU|-1|Initializing Port
2025/02/11 14:59:03.170|SLProtocol – 42776 – NYNY-DR DEC 2_3|17480|CProtocol::Start|CRU|-1|Starting Timers
2025/02/11 14:59:03.170|SLProtocol – 42776 – NYNY-DR DEC 2_3|17480|CProtocol::StartTimers|CRU|0|Starting protocol thread.
2025/02/11 14:59:03.171|SLProtocol – 42776 – NYNY-DR DEC 2_3|17480|CProtocol::Start|CRU|-1|Starting Protocol done
2025/02/11 14:59:03.171|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::Start|DBG|-1|Complete.
2025/02/11 14:59:03.171|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::SetState|DBG|0|** Setting state from 1 to 10 (RealState = 4)
2025/02/11 14:59:03.171|SLProtocol – 42776 – NYNY-DR DEC 2_3|18044|CProtocol::ProtocolThreadFunc|CRU|0|[Harmonic Proview PVR7000/4.2.3.16] NYNY-DR DEC 2_3 – ProtocolThread | Name: Main Protocol Thread
2025/02/11 14:59:03.171|SLProtocol – 42776 – NYNY-DR DEC 2_3|18044|CProtocol::ProtocolThreadFunc|DBG|0|– Waiting for Polling to be enabled.
2025/02/11 14:59:03.171|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::Activate|DBG|0|** Alarm template : <No monitoring>
2025/02/11 14:59:03.171|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::Activate|DBG|0|** Trend template : <No Trending>
2025/02/11 14:59:03.171|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::InitializeLock|DBG|0|** Initializing lock status
2025/02/11 14:59:03.172|SLProtocol – 42776 – NYNY-DR DEC 2_3|18044|CProtocol::ProtocolThreadFunc|DBG|0|– Polling enabled.
2025/02/11 14:59:03.188|SLElement.exe|17944|CElement::ApplyServiceSettingsChange|INF|-1|Updating list of affected services (6 services) for element NYNY-DR DEC 2_3 [All]
2025/02/11 14:59:03.208|SLElement.exe|33760|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 0.
2025/02/11 14:59:03.442|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::InitializeLock|DBG|0|** Not locked.
2025/02/11 14:59:03.442|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::NotifyRedundancy|DBG|0|** Redundancy Changes
2025/02/11 14:59:03.442|SLDataMiner.exe – NYNY-DR DEC 2_3|32016|CElement::NotifyServiceTriggers|DBG|0|** Service Triggers
2025/02/11 14:59:07.875|SLManagedScripting.exe|ManagedInterop|ERR|0|111|QA2|Set Requests with Ids|SetRequestsIds|System.IndexOutOfRangeException: Index was outside the bounds of the array.
at QAction.ProcessMainBoard(SLProtocol protocol, Platform platform)
at QAction.SetRequestsIds(SLProtocol protocol)
2025/02/11 14:59:14.930|SLManagedScripting.exe|ManagedInterop|ERR|0|94|QA11054|Empty Response:
2025/02/11 14:59:14.931|SLManagedScripting.exe|ManagedInterop|ERR|0|94|QA57432|Process Response – HadasCard|Empty response.