Oracle SBC 6350 compliant with prognosis 11.9 ?

[tony2beire]

Hi to all,

Does anyone knows if the Oracle SBC 6350 supported ? The documentation shows only 6300. 

Thanks for your comments.

[SCOTT_BALDWIN · Accepted solution]

Hi @tony2beire,

Monitoring of the the Oracle SBC is done completely by SNMP. In the past, the Oracle SBCs with the same first 2 digits all used the same MIB. If the same holds true, the 6300 and 6350 will use the same MIBs and Prognosis will not know the difference between the 2 when sending the queries.

I would suggest adding the Oracle SBC 6350 to Prognosis Server. If the history with Oracle SBC model names and MIBs remains consistent, Prognosis Server will show data.
If the Oracle SBC 6350 uses different MIBs, there will be no harm to the SBC (because SNMP is so lightweight) and there will be no data in Prognosis Server.
If SNMP v3 is used instead of SNMP v2c, the irSBC.log files will show connection time outs.

Thank you,
Scott Baldwin

[tony2beire · Accepted solution]

Hi Scott,

Thanks a lot for this precision. Btw, after configuring SBC as 6350 model, status in 'SBC-WELCOME' display from Windows client shown 'INIT' instead of 'Operating'. I had to modify the WHERECLAUSE to add this model 'OR TYPE MATCHES "6350"' to get the right status. Would you recommend to do this way or just put '6300' as model type when configuring ? 

[SCOTT_BALDWIN · Accepted solution]

Hi @tony2beire,

Beautiful and perfect solution to the SBCs being stuck in an Init state!

I think the 6350 model will be returned by the SNMP queries, so adding the 6350 model to Where Clause is very likely required. Additionally, having the actual model information show is better than having to use an alias and remember what the actual model is.

In fact, this is such a good idea, I'll share it with IR Development and see if they agree it can be added to product.

Thank you for the feedback!
Scott Baldwin

[tony2beire]

Hi Scott.

This is what we did. You are right and you confirm what I was thinking about : reflecting the correct model is the best solution.

We did change all display configs for SBC with adding 6350.

May be it could be a good idea to set the WHERECLAUSE with 63** to the displays so that all variants can match, as they are using the same Mib's. 

thanks a lot for your help.

Best regards.

Tony