Error code.
Error codes are produced at certain stages in the CAC application.
The interpretation of the error codes is:
Terms: 'ebXXXXX.bin' : binary file in flash
data structure: EBT_file_template based structure
* no-error: no error encountered.
* nonexistent-file: the 'ebXXXXX.bin' file not found in the flash,
during APEX boot or MIB EBT load request.
* bad-file-length: mismatch in file length specified within
'ebXXXXX.bin' and the pre-specified file length. Occurs while
loading file into data structures.
* copy-corrupted: copying of data from 'ebXXXXX.bin' into the data
structure, EBT_file_template did not proceed smoothly and the data
structure is now corrupted.
* nunused-cbtdwoEBTid: command EBT id not used and current EBT id
is 0. The CAC booted without valid EBT values in the data structure.
Occurs during boot while loading file into data structures.
* nunused-cinvalid: command EBT id not used. The file eb'current EBT
id'.bin contains invalid data. Occurs just after the EBT file got
loaded into the data structure, when the verification of values
in the data structure takes place.
* nEBTid-uninit-cstays: command EBT id is 0 and the data structures
remain unchanged. Occurs when mib item cacTableload is switched to yes.
* ninvalid-cstays: eb'command EBT id'.bin contains invalid data and
the data structures remain unchanged. Occurs when mib item cacTableload
is switched to yes.
* ninvalid-cEBTid-uninit: eb'command EBT id'.bin contains invalid data
and the current EBT id is zero. This means that data structure is
corrupted. Occurs when mib item cacTableload is switched to yes.
* ninvalid-cinvalid: both eb'command EBT id'.bin and eb'current EBT
id'.bin contains invalid data. The data structure is corrupted.
Occurs when mib item cacTableload is switched to yes.
* ninvalid-cnoerror: eb'command EBT id'.bin contains invalid data
and the eb'current EBT id'.bin is loaded successfully. Occurs
when mib item cacTableload is switched to yes.
* link-not-ready: it is a runtime error which states that link is
not ready for configuration.
* link-not-configuring: it is a runtime error which states that link
is not in configuring mode and therefore the recalculation of EBT
or scr-pcr sums is not possible.
* EBT-not-loaded: it is a runtime error which states that the data
structure does not contain valid data. This occurs when the EBT
enable mib switch is turned to 'yes' or the cac version mib item
is switched to EBT.
* class-not-found: this runtime error indicates that during the
processing of allocate, deallocate or change functions, a class
corresponding to SCR, PCR or MBS was not found. The effective
bandwidth used in this situation is the same as a CBR allocation
using the attempted connection's PCR.
* dump-fs-error: this error indicates that a file system error
(e.g. the file system became full) during the EBT file dump function.
The dump file was deleted after the file system error was detected.
Parsed from file gdc-apex.mib
Company: None
Module: DV2-MIB
Error code.
Error codes are produced at certain stages in the CAC application.
The interpretation of the error codes is:
Terms: 'ebXXXXX.bin' : binary file in flash
data structure: EBT_file_template based structure
* no-error: no error encountered.
* nonexistent-file: the 'ebXXXXX.bin' file not found in the flash,
during APEX boot or MIB EBT load request.
* bad-file-length: mismatch in file length specified within
'ebXXXXX.bin' and the pre-specified file length. Occurs while
loading file into data structures.
* copy-corrupted: copying of data from 'ebXXXXX.bin' into the data
structure, EBT_file_template did not proceed smoothly and the data
structure is now corrupted.
* nunused-cbtdwoEBTid: command EBT id not used and current EBT id
is 0. The CAC booted without valid EBT values in the data structure.
Occurs during boot while loading file into data structures.
* nunused-cinvalid: command EBT id not used. The file eb'current EBT
id'.bin contains invalid data. Occurs just after the EBT file got
loaded into the data structure, when the verification of values
in the data structure takes place.
* nEBTid-uninit-cstays: command EBT id is 0 and the data structures
remain unchanged. Occurs when mib item cacTableload is switched to yes.
* ninvalid-cstays: eb'command EBT id'.bin contains invalid data and
the data structures remain unchanged. Occurs when mib item cacTableload
is switched to yes.
* ninvalid-cEBTid-uninit: eb'command EBT id'.bin contains invalid data
and the current EBT id is zero. This means that data structure is
corrupted. Occurs when mib item cacTableload is switched to yes.
* ninvalid-cinvalid: both eb'command EBT id'.bin and eb'current EBT
id'.bin contains invalid data. The data structure is corrupted.
Occurs when mib item cacTableload is switched to yes.
* ninvalid-cnoerror: eb'command EBT id'.bin contains invalid data
and the eb'current EBT id'.bin is loaded successfully. Occurs
when mib item cacTableload is switched to yes.
* link-not-ready: it is a runtime error which states that link is
not ready for configuration.
* link-not-configuring: it is a runtime error which states that link
is not in configuring mode and therefore the recalculation of EBT
or scr-pcr sums is not possible.
* EBT-not-loaded: it is a runtime error which states that the data
structure does not contain valid data. This occurs when the EBT
enable mib switch is turned to 'yes' or the cac version mib item
is switched to EBT.
* class-not-found: this runtime error indicates that during the
processing of allocate, deallocate or change functions, a class
corresponding to SCR, PCR or MBS was not found. The effective
bandwidth used in this situation is the same as a CBR allocation
using the attempted connection's PCR.
* dump-fs-error: this error indicates that a file system error
(e.g. the file system became full) during the EBT file dump function.
The dump file was deleted after the file system error was detected.
Parsed from file DV2-MIB.mib
Module: DV2-MIB
Vendor: Netcomm, Ltd.
Module: DV2-MIB
[Automatically extracted from oidview.com]
cacErrorCode OBJECT-TYPE SYNTAX INTEGER { no-error(1), nonexistent-file(2), bad-file-length(3), copy-corrupted(4), nunused-cbtdwoebtid(5), nunused-cinvalid(6), nebtid-uninit-cstays(7), ninvalid-cstays(8), ninvalid-cebtid-uninit(9), ninvalid-cinvalid(10), ninvalid-cnoerror(11), link-not-ready(12), link-not-configuring(13), ebt-not-loaded(14), class-not-found(15), dump-fs-error(16), bad-ebt-command(17), delete-fs-error(18), ebt-id-invalid(19) } ACCESS read-only STATUS mandatory DESCRIPTION "Error code.
Error codes are produced at certain stages in the CAC application. The interpretation of the error codes is: Terms: 'ebXXXXX.bin' : binary file in flash data structure: EBT_file_template based structure * no-error: no error encountered. * nonexistent-file: the 'ebXXXXX.bin' file not found in the flash, during APEX boot or MIB EBT load request. * bad-file-length: mismatch in file length specified within 'ebXXXXX.bin' and the pre-specified file length. Occurs while loading file into data structures. * copy-corrupted: copying of data from 'ebXXXXX.bin' into the data structure, EBT_file_template did not proceed smoothly and the data structure is now corrupted. * nunused-cbtdwoEBTid: command EBT id not used and current EBT id is 0. The CAC booted without valid EBT values in the data structure. Occurs during boot while loading file into data structures. * nunused-cinvalid: command EBT id not used. The file eb'current EBT id'.bin contains invalid data. Occurs just after the EBT file got loaded into the data structure, when the verification of values in the data structure takes place. * nEBTid-uninit-cstays: command EBT id is 0 and the data structures remain unchanged. Occurs when mib item cacTableload is switched to yes. * ninvalid-cstays: eb'command EBT id'.bin contains invalid data and the data structures remain unchanged. Occurs when mib item cacTableload is switched to yes. * ninvalid-cEBTid-uninit: eb'command EBT id'.bin contains invalid data and the current EBT id is zero. This means that data structure is corrupted. Occurs when mib item cacTableload is switched to yes. * ninvalid-cinvalid: both eb'command EBT id'.bin and eb'current EBT id'.bin contains invalid data. The data structure is corrupted. Occurs when mib item cacTableload is switched to yes. * ninvalid-cnoerror: eb'command EBT id'.bin contains invalid data and the eb'current EBT id'.bin is loaded successfully. Occurs when mib item cacTableload is switched to yes. * link-not-ready: it is a runtime error which states that link is not ready for configuration. * link-not-configuring: it is a runtime error which states that link is not in configuring mode and therefore the recalculation of EBT or scr-pcr sums is not possible. * EBT-not-loaded: it is a runtime error which states that the data structure does not contain valid data. This occurs when the EBT enable mib switch is turned to 'yes' or the cac version mib item is switched to EBT. * class-not-found: this runtime error indicates that during the processing of allocate, deallocate or change functions, a class corresponding to SCR, PCR or MBS was not found. The effective bandwidth used in this situation is the same as a CBR allocation using the attempted connection's PCR. * dump-fs-error: this error indicates that a file system error (e.g. the file system became full) during the EBT file dump function. The dump file was deleted after the file system error was detected." DEFVAL { no-error } ::= { dv2Cac 5 }
cacErrorCode OBJECT-TYPE SYNTAX INTEGER { no-error(1), nonexistent-file(2), bad-file-length(3), copy-corrupted(4), nunused-cbtdwoebtid(5), nunused-cinvalid(6), nebtid-uninit-cstays(7), ninvalid-cstays(8), ninvalid-cebtid-uninit(9), ninvalid-cinvalid(10), ninvalid-cnoerror(11), link-not-ready(12), link-not-configuring(13), ebt-not-loaded(14), class-not-found(15), dump-fs-error(16), bad-ebt-command(17), delete-fs-error(18), ebt-id-invalid(19) } ACCESS read-only STATUS mandatory DESCRIPTION "Error code.
Error codes are produced at certain stages in the CAC application. The interpretation of the error codes is: Terms: 'ebXXXXX.bin' : binary file in flash data structure: EBT_file_template based structure * no-error: no error encountered. * nonexistent-file: the 'ebXXXXX.bin' file not found in the flash, during APEX boot or MIB EBT load request. * bad-file-length: mismatch in file length specified within 'ebXXXXX.bin' and the pre-specified file length. Occurs while loading file into data structures. * copy-corrupted: copying of data from 'ebXXXXX.bin' into the data structure, EBT_file_template did not proceed smoothly and the data structure is now corrupted. * nunused-cbtdwoEBTid: command EBT id not used and current EBT id is 0. The CAC booted without valid EBT values in the data structure. Occurs during boot while loading file into data structures. * nunused-cinvalid: command EBT id not used. The file eb'current EBT id'.bin contains invalid data. Occurs just after the EBT file got loaded into the data structure, when the verification of values in the data structure takes place. * nEBTid-uninit-cstays: command EBT id is 0 and the data structures remain unchanged. Occurs when mib item cacTableload is switched to yes. * ninvalid-cstays: eb'command EBT id'.bin contains invalid data and the data structures remain unchanged. Occurs when mib item cacTableload is switched to yes. * ninvalid-cEBTid-uninit: eb'command EBT id'.bin contains invalid data and the current EBT id is zero. This means that data structure is corrupted. Occurs when mib item cacTableload is switched to yes. * ninvalid-cinvalid: both eb'command EBT id'.bin and eb'current EBT id'.bin contains invalid data. The data structure is corrupted. Occurs when mib item cacTableload is switched to yes. * ninvalid-cnoerror: eb'command EBT id'.bin contains invalid data and the eb'current EBT id'.bin is loaded successfully. Occurs when mib item cacTableload is switched to yes. * link-not-ready: it is a runtime error which states that link is not ready for configuration. * link-not-configuring: it is a runtime error which states that link is not in configuring mode and therefore the recalculation of EBT or scr-pcr sums is not possible. * EBT-not-loaded: it is a runtime error which states that the data structure does not contain valid data. This occurs when the EBT enable mib switch is turned to 'yes' or the cac version mib item is switched to EBT. * class-not-found: this runtime error indicates that during the processing of allocate, deallocate or change functions, a class corresponding to SCR, PCR or MBS was not found. The effective bandwidth used in this situation is the same as a CBR allocation using the attempted connection's PCR. * dump-fs-error: this error indicates that a file system error (e.g. the file system became full) during the EBT file dump function. The dump file was deleted after the file system error was detected." DEFVAL { no-error } ::= { dv2Cac 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.251.1.1.39.5.0 | cacErrorCode | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.251.1.1.39.1 | cacCurrentEbtId | 1 | 1 | Current EBT file ID code. cacCurrentEbtId holds the EBT file ID code of the EBT file currently in memory in a verified state. Th… |
| 1.3.6.1.4.1.251.1.1.39.2 | cacEbtCommand | 1 | 1 | EBT file command. This field, normally with the value none, may be set by the manager to: * load-ebt to initiate the loading of a… |
| 1.3.6.1.4.1.251.1.1.39.3 | cacCommandEbtId | 1 | 1 | Command EBT file ID code. cacCommandEbtId is written to by the manager to identify the EBT file in the flash that should be loade… |
| 1.3.6.1.4.1.251.1.1.39.4 | cacEbtState | 1 | 1 | State of the CAC. The state: * uninitialized is an initial MIB value which is never returned to without starting from a new MIB. *… |
| 1.3.6.1.4.1.251.1.1.39.6 | cacPerLinkTable | 1 | 18 | This table containing per link data. Contains per link specific data |
| 1.3.6.1.4.1.251.1.1.39.7 | cacPerSapTable | 1 | 8 | This table containing per Sap data. The virtual SAP table in the MIB has 12 entries indexed by cacSapNo in the range (20..31). Fo… |