I am currently working on a new driver that has SNMP and CLI connections. The way I am structuring the Pids is with a buffer of 1000 per page in the protocol and the CLI parameters beginning at 50000. My reasoning is that as the driver may grow and parameters may need to be added to pages or auxiliary data needed to add to columns, they may be added to that buffer, and same with the CLI, but in reverse, so they can always be separated until they potentially meet in the middle.
Is this in line with the Skyline Standard? Or is there an actual standard somewhere with example drivers and recommended spacing procedures? I feel it makes sense to me, want to make sure it makes sense to others who will pick up the driver in the future. Any other recommendations would be welcome.
Hi Gabriel, Let me please point you to: Protocol development checklists – DataMiner Dojo In the checklist you will find the applicable guidelines on the allowed ID Range, ID Gaps, ID Ordering & ID Grouping.
It's indeed applicable to leave some spare ID's between tables or different features etc.
You mentioned you reserved ID's above 50k for your communication parameters:
If you organize the protocol to have the logic & communication parameters reserved at the beginning, then you will never have to cross that gap when you have tremendous amount of parameters in the future. (In case you would still reach 50k & higher for example).
Note that there are no hard-rules on these matters.
Those are just guidelines to support common sense 😉
Hope that cleared things out!