Issue:
If using NetBotz rest API, Pod Enclosure Number (podEncNum) may be either 0 or 1 based
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Cause:
There are 2 different numbering systems in the NetBotz code, some are 0 based while others are 1 based.
This is exposed in the podEncNum field that we expose in our REST API, mass config, SNMP, Modbus.
Resolution:
For the 150 and 155 pod’s the podEncNum values will be 0-based
For the 170 anad 175 pod’s the podEncNum values will be 1-based
For the AP9520TH the podEncNum values will be 0-based
NOTE that the numbers allocated are distinct across the three sequences based on enclosure type / pod model.
If using NetBotz rest API, Pod Enclosure Number (podEncNum) may be either 0 or 1 based
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Cause:
There are 2 different numbering systems in the NetBotz code, some are 0 based while others are 1 based.
This is exposed in the podEncNum field that we expose in our REST API, mass config, SNMP, Modbus.
Resolution:
For the 150 and 155 pod’s the podEncNum values will be 0-based
For the 170 anad 175 pod’s the podEncNum values will be 1-based
For the AP9520TH the podEncNum values will be 0-based
NOTE that the numbers allocated are distinct across the three sequences based on enclosure type / pod model.
Опубликовано для: Schneider Electric Казахстан
