This object encapsulates the data corresponding to the umc1ResponseTransNbr
and umc1ResponseSeqNbr. The first byte of this umc1ResponseData is a version
byte. The second byte is a number of records encapsulated in the
umc1ResponseData. A length field precedes all records (Variable as well as
fixed length records). The length field specifies the length of record in
Octets.
General Response Data Format is shown below:
Version Number Of Length of Record 1 Length of Record 2 ...
(Byte) Records Record 1 Record 2
(Byte) (Byte) (Byte)
The record format depends on the type of data that is being dumped.
Record Data Format.
For the _ReadTable_ command.
1. Record format for Terminal Info Table (umc1TerminalInfoTable)
Fields Terminal Terminal Serial Baud New
Id Name Device Rate Terminal
Type Id
Num Bytes 1 1-21 1 1 1
2. Record Format for Terminal Status Table (umcTerminalStatusTable)
Fields Terminal Terminal
Id Status
Num Bytes 1 1
3. Record Format for Inventory Shelf Table (umcInventoryShelfTable)
Fields Terminal Shelf Shelf
Id Id Type
Num Bytes 1 1 2
4. Record Format for Inventory Plug-in Table (umcInventoryPluginTable)
Fields Terminal Shelf Slot Plugin
Id Id Id Type
Num Bytes 1 1 1 2
5. Record Format for Topology Link Table and ACO Snap Topology Link Table
(umc1TopologyLinkTable and umc1AcoSnapTopologyLinkTable)
Fields TerminalA TerminaB
Id Id
Num Bytes 1 1
6. Record Format for cross connect Table( umc1XCTable)
Fields XC Index XC Data
Num Bytes 1-255 0-255
7. Record Format for GR-303 Group Provisioning Table
(umc1GR303Table)
Fields GR-303 GR-303
Index Data
Num Bytes 1-255 0-255
8. Record Format for TR-08 Group Provisioning Table
(umc1TR8Table)
Fields TR-08 TR-08
Index Data
Num Bytes 1-255 0-255
9. Record Format for ATM Protection Group Provisioning Table
(umc1AtmProtGrpTable)
Fields ATM ATM
Protection Protection
Index Data
Num Bytes 1-255 0-255
10. Record Format for Port Profile Provisioning Table
(umc1PortProfTable)
Fields Port Port
Profile Profile
Index Data
Num Bytes 1-255 0-255
11. Record Format for Terminal Span Table (umc1TerminalSpanTable)
Fields Near Near Near Near Far Far Far
End End End End End End End
Term Shelf Slot Plugin Term Shelf Slot
Id Id Id type Id Id Id
Num Bytes 1 1 1 2 1 1 1
12. Record Format for Shelf Span Table (umc1ShelfSpanTable)
Fields Near Near Near Near Far Far Far
End End End End End End End
Term Shelf Slot Plugin Shelf Slot Plugin
Id Id Id type Id Id type
Num Bytes 1 1 1 2 1 1 2
For the _GetAllSeqNum_ command.
When the umc1CommandId is _GetAllSeqNum_, refer to the object description of
umc1SystemAllSeqNbr for the record format.
For the _GetActiveTermName_ command.
When the umc1CommandId is _GetActiveTermName_, the record format is:
Fields Terminal Terminal Terminal Baud New Serial
Id Status Name Rate Terminal Device
Id Type
Num Bytes 1 1 1-21 1 1 1
For the _GetCpuDbDumpPort_ command.
When the umc1CommandId is _GetCpuDbDumpPort_, the record format is:
Fields Port Number
Num Bytes 4
For the _SetOrDelete_ command.
When the umc1CommandId is _SetOrDelete_, the record format is:
Fields No. of Record Created/Deleted
Num Bytes 1
For the _ClearCache_ command.
When the umc1CommandId is _ClearCache_, the record format is:
Fields Is Cache Cleared
Num Bytes 1
Is Cache Cleared value Meaning
1 Cache Successfully cleared
If error occured while clearing cache, Agent shall issue _gerErr_ to
Management Station.
For the _ActivateAco_ command.
When the umc1CommandId is _ActivateAco_, the record format is:
Fields Result Byte
Num Bytes 1
Result Byte value Meaning
1 ACO Activated Successfully
If error occured while activating ACO, Agent shall issue _gerErr_ to
Management Station.
For the _AotRollover_ command.
When the umc1CommandId is _AotRollover_, the record format is:
Fields Result Byte
Num Bytes 1
Result Byte value Meaning
1 AoT to End-To-End ATM Rollover was Successful
If error occured while rolling over Aot, Agent shall issue _gerErr_ to
Management Station.
For the _CurTrafficStats_ command.
When the umc1CommandId is _CurTrafficStats_, the record format is:
Fields Terminal Total Blocked Used Available Non-Available Current
Id Calls Calls Channels Channels Channels Hour Load
Num Bytes 1 2 2 2 2 2 2
For the command ID equal to _GetLineCardStatus_, the response data will
follow the 'General Response Data Format' as defined above. The definition
of the response record will vary depending upon the version of the UMC system.
In all cases, the response data will contain a single record.
Original Response data format for command ID _GetLineCardStatus_.
The version octet = 1. The number of records octet = 1. The length of
record #1 and the record format are determined by the octet string returned
by the UMC system CPU card. In general, the record represents an array of six
elements where each element contains the following attributes for a single
circuit/port: port status, downstream rate, downstream SNR margin, upstream
rate, and upstream SNR margin.
Enhanced Response data format for command ID _GetLineCardStatus_.
The version octet = 1. The number of records octet = 1. The record will
contain an array of equivalent data elements. The size of the array
will depend on the number of circuits/ports supported by the card. The length
of each element and the element format are determined by the octet string
returned by the UMC system CPU card. In general, each record contains the
following attributes for a single circuit/port: port status, downstream rate,
downstream SNR margin, upstream rate, and upstream SNR margin, downstream signal
attenuation, downstream current channel bit rate, downstream transmitted signal
power, downstream relative capacity operation, upstream signal attenuation,
upstream current channel bit rate, upstream transmitted signal power, and
upstream relative capacity operation.
For the command ID equal to _GetAtmStatistics_, the response data will
follow the 'General Response Data Format' as defined above. The version
octet = 1. The number of records octet = 2. The response data will contain
a two records. The first record represents the 'receive' ATM
statistics and the second record represents the 'transmit'
ATM statistics. The length of each record and the record format
are determined by the octet string returned by the UMC system CPU card.
For the command ID equal to _GetAdslPmAttribute_, the response data will
follow the 'General Response Data Format' as defined above. The response
data will contain a single record or multiple equivalent records depending
on the 'Data Operation' octet specified in the corresponding command table
record. The length of each record and the record format are determined by
the octet string returned by the UMC system CPU card.
For the command ID equal to _GetPmDataBin_, the response data
will follow the 'General Response Data Format' as defined above. The
version octet = 1. The number of records octet depends on the 'Data
Operation' specified in the request. For a 'GET EXACT' request, the
response data will contain
- a single record for a single port and bin request.
- multiple records for an all port and/or all bin request
For a Write request, the response data will contain a single record.
The format and length of each record is determined by the octet string
returned by the UMC system CPU card.
For the command ID equal to _GetNBLinkStats_, the response data will
follow the 'General Response Data Format' as defined above. The version
octet = 1. The number of records octet = 1 for a Get Exact operation and
1 - 8 (maximum number of GR303/transport link CCS data before overflowing
the 255 byte limit) for a Get Progressive operation. The response data
can be one of two record types (transport link record or GR303 Group record).
The length of each record and the record format are determined by the octet
string returned by the UMC system CPU card (IB response payload).
For the command ID equal to _ManualProtectionSwitch_, the response data
will always contain two records. The first record has a length of one
octet and represents the response field from the internal system interface.
The possible values are: _RvOk_, _RvInvalidData_, & _RvFailure_. The length
and format of the second record are determined by the octet string returned
by the internal system interface
For each of the following commands ID, the response data will follow the
'General Response Data Format' as defined above. The record format will
consist of an octet string as returned by the CPU:
_GetVcStatusInfo_
_GetBlockedVccInfo_
_GetAtmBandwidth_
_GetAdslBitsPerTone_
_GetDropTestResults_
For the command ID equal to _GenericIB_, the response data will be formatted
as follows:
- First octet = version number = 1.
- Second octet = number of records octet = 1.
- Third octet = size of record in bytes.
- Forth octet = first byte of record will contain the CPU error code.
- Fifth octet = second byte of record will contain the first byte of the IB
payload.
- Sixth octet = third byte of record will contain the second byte of the IB
payload.
- xth octet = last byte of the record will contain the last byte of the IB
payload.
Note: The third octet will be set to 1 if the CPU returns an error code
(not equal to _RvOk_) back to the IPMI via the IB response message. The
third octet will be set to a value of greater than 1 if the CPU returns
valid data back to the IPMI via the IB response message. The forth octet
will contain a value of 0 (RvOk) when valid data is returned in the IB
payload. The forth octet will contain a value greater than 0 (error type)
when the CPU identifies an error condition.
For the command ID equal to _GetAtmStatsPerVcc_, the response data will
follow the 'General Response Data Format' as defined above. The response
can contain anywhere from zero (0) response records up to six (6) response
records. The record format will consist of an octet string as returned by
the CPU:
Parsed from file umc1000.mib.txt
Company: None
Module: UMC1000-MIB
This object encapsulates the data corresponding to the umc1ResponseTransNbr
and umc1ResponseSeqNbr. The first byte of this umc1ResponseData is a version
byte. The second byte is a number of records encapsulated in the
umc1ResponseData. A length field precedes all records (Variable as well as
fixed length records). The length field specifies the length of record in
Octets.
General Response Data Format is shown below:
Version Number Of Length of Record 1 Length of Record 2 ...
(Byte) Records Record 1 Record 2
(Byte) (Byte) (Byte)
The record format depends on the type of data that is being dumped.
Record Data Format.
For the _ReadTable_ command.
1. Record format for Terminal Info Table (umc1TerminalInfoTable)
Fields Terminal Terminal Serial Baud New
Id Name Device Rate Terminal
Type Id
Num Bytes 1 1-21 1 1 1
2. Record Format for Terminal Status Table (umcTerminalStatusTable)
Fields Terminal Terminal
Id Status
Num Bytes 1 1
3. Record Format for Inventory Shelf Table (umcInventoryShelfTable)
Fields Terminal Shelf Shelf
Id Id Type
Num Bytes 1 1 2
4. Record Format for Inventory Plug-in Table (umcInventoryPluginTable)
Fields Terminal Shelf Slot Plugin
Id Id Id Type
Num Bytes 1 1 1 2
5. Record Format for Topology Link Table and ACO Snap Topology Link Table
(umc1TopologyLinkTable and umc1AcoSnapTopologyLinkTable)
Fields TerminalA TerminaB
Id Id
Num Bytes 1 1
6. Record Format for cross connect Table( umc1XCTable)
Fields XC Index XC Data
Num Bytes 1-255 0-255
7. Record Format for GR-303 Group Provisioning Table
(umc1GR303Table)
Fields GR-303 GR-303
Index Data
Num Bytes 1-255 0-255
8. Record Format for TR-08 Group Provisioning Table
(umc1TR8Table)
Fields TR-08 TR-08
Index Data
Num Bytes 1-255 0-255
9. Record Format for ATM Protection Group Provisioning Table
(umc1AtmProtGrpTable)
Fields ATM ATM
Protection Protection
Index Data
Num Bytes 1-255 0-255
10. Record Format for Port Profile Provisioning Table
(umc1PortProfTable)
Fields Port Port
Profile Profile
Index Data
Num Bytes 1-255 0-255
11. Record Format for Terminal Span Table (umc1TerminalSpanTable)
Fields Near Near Near Near Far Far Far
End End End End End End End
Term Shelf Slot Plugin Term Shelf Slot
Id Id Id type Id Id Id
Num Bytes 1 1 1 2 1 1 1
12. Record Format for Shelf Span Table (umc1ShelfSpanTable)
Fields Near Near Near Near Far Far Far
End End End End End End End
Term Shelf Slot Plugin Shelf Slot Plugin
Id Id Id type Id Id type
Num Bytes 1 1 1 2 1 1 2
For the _GetAllSeqNum_ command.
When the umc1CommandId is _GetAllSeqNum_, refer to the object description of
umc1SystemAllSeqNbr for the record format.
For the _GetActiveTermName_ command.
When the umc1CommandId is _GetActiveTermName_, the record format is:
Fields Terminal Terminal Terminal Baud New Serial
Id Status Name Rate Terminal Device
Id Type
Num Bytes 1 1 1-21 1 1 1
For the _GetCpuDbDumpPort_ command.
When the umc1CommandId is _GetCpuDbDumpPort_, the record format is:
Fields Port Number
Num Bytes 4
For the _SetOrDelete_ command.
When the umc1CommandId is _SetOrDelete_, the record format is:
Fields No. of Record Created/Deleted
Num Bytes 1
For the _ClearCache_ command.
When the umc1CommandId is _ClearCache_, the record format is:
Fields Is Cache Cleared
Num Bytes 1
Is Cache Cleared value Meaning
1 Cache Successfully cleared
If error occured while clearing cache, Agent shall issue _gerErr_ to
Management Station.
For the _ActivateAco_ command.
When the umc1CommandId is _ActivateAco_, the record format is:
Fields Result Byte
Num Bytes 1
Result Byte value Meaning
1 ACO Activated Successfully
If error occured while activating ACO, Agent shall issue _gerErr_ to
Management Station.
For the _AotRollover_ command.
When the umc1CommandId is _AotRollover_, the record format is:
Fields Result Byte
Num Bytes 1
Result Byte value Meaning
1 AoT to End-To-End ATM Rollover was Successful
If error occured while rolling over Aot, Agent shall issue _gerErr_ to
Management Station.
For the _CurTrafficStats_ command.
When the umc1CommandId is _CurTrafficStats_, the record format is:
Fields Terminal Total Blocked Used Available Non-Available Current
Id Calls Calls Channels Channels Channels Hour Load
Num Bytes 1 2 2 2 2 2 2
For the command ID equal to _GetLineCardStatus_, the response data will
follow the 'General Response Data Format' as defined above. The definition
of the response record will vary depending upon the version of the UMC system.
In all cases, the response data will contain a single record.
Original Response data format for command ID _GetLineCardStatus_.
The version octet = 1. The number of records octet = 1. The length of
record #1 and the record format are determined by the octet string returned
by the UMC system CPU card. In general, the record represents an array of six
elements where each element contains the following attributes for a single
circuit/port: port status, downstream rate, downstream SNR margin, upstream
rate, and upstream SNR margin.
Enhanced Response data format for command ID _GetLineCardStatus_.
The version octet = 1. The number of records octet = 1. The record will
contain an array of equivalent data elements. The size of the array
will depend on the number of circuits/ports supported by the card. The length
of each element and the element format are determined by the octet string
returned by the UMC system CPU card. In general, each record contains the
following attributes for a single circuit/port: port status, downstream rate,
downstream SNR margin, upstream rate, and upstream SNR margin, downstream signal
attenuation, downstream current channel bit rate, downstream transmitted signal
power, downstream relative capacity operation, upstream signal attenuation,
upstream current channel bit rate, upstream transmitted signal power, and
upstream relative capacity operation.
For the command ID equal to _GetAtmStatistics_, the response data will
follow the 'General Response Data Format' as defined above. The version
octet = 1. The number of records octet = 2. The response data will contain
a two records. The first record represents the 'receive' ATM
statistics and the second record represents the 'transmit'
ATM statistics. The length of each record and the record format
are determined by the octet string returned by the UMC system CPU card.
For the command ID equal to _GetAdslPmAttribute_, the response data will
follow the 'General Response Data Format' as defined above. The response
data will contain a single record or multiple equivalent records depending
on the 'Data Operation' octet specified in the corresponding command table
record. The length of each record and the record format are determined by
the octet string returned by the UMC system CPU card.
For the command ID equal to _GetPmDataBin_, the response data
will follow the 'General Response Data Format' as defined above. The
version octet = 1. The number of records octet depends on the 'Data
Operation' specified in the request. For a 'GET EXACT' request, the
response data will contain
- a single record for a single port and bin request.
- multiple records for an all port and/or all bin request
For a Write request, the response data will contain a single record.
The format and length of each record is determined by the octet string
returned by the UMC system CPU card.
For the command ID equal to _GetNBLinkStats_, the response data will
follow the 'General Response Data Format' as defined above. The version
octet = 1. The number of records octet = 1 for a Get Exact operation and
1 - 8 (maximum number of GR303/transport link CCS data before overflowing
the 255 byte limit) for a Get Progressive operation. The response data
can be one of two record types (transport link record or GR303 Group record).
The length of each record and the record format are determined by the octet
string returned by the UMC system CPU card (IB response payload).
For the command ID equal to _ManualProtectionSwitch_, the response data
will always contain two records. The first record has a length of one
octet and represents the response field from the internal system interface.
The possible values are: _RvOk_, _RvInvalidData_, & _RvFailure_. The length
and format of the second record are determined by the octet string returned
by the internal system interface
For each of the following commands ID, the response data will follow the
'General Response Data Format' as defined above. The record format will
consist of an octet string as returned by the CPU:
_GetVcStatusInfo_
_GetBlockedVccInfo_
_GetAtmBandwidth_
_GetAdslBitsPerTone_
_GetDropTestResults_
For the command ID equal to _GenericIB_, the response data will be formatted
as follows:
- First octet = version number = 1.
- Second octet = number of records octet = 1.
- Third octet = size of record in bytes.
- Forth octet = first byte of record will contain the CPU error code.
- Fifth octet = second byte of record will contain the first byte of the IB
payload.
- Sixth octet = third byte of record will contain the second byte of the IB
payload.
- xth octet = last byte of the record will contain the last byte of the IB
payload.
Note: The third octet will be set to 1 if the CPU returns an error code
(not equal to _RvOk_) back to the IPMI via the IB response message. The
third octet will be set to a value of greater than 1 if the CPU returns
valid data back to the IPMI via the IB response message. The forth octet
will contain a value of 0 (RvOk) when valid data is returned in the IB
payload. The forth octet will contain a value greater than 0 (error type)
when the CPU identifies an error condition.
For the command ID equal to _GetAtmStatsPerVcc_, the response data will
follow the 'General Response Data Format' as defined above. The response
can contain anywhere from zero (0) response records up to six (6) response
records. The record format will consist of an octet string as returned by
the CPU:
Parsed from file UMC1000-MIB.mib
Module: UMC1000-MIB
Vendor: Advanced Fibre Communications
Module: AFC-OIDS (umc.mib)
Type: TABULAR
Access: read-only
Syntax: OCTET STRING
( SIZE (
1..255 ) )
Automatically extracted from www.mibdepot.com
umc1ResponseData OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "This object encapsulates the data corresponding to the umc1ResponseTransNbr and umc1ResponseSeqNbr. The first byte of this umc1ResponseData is a version byte. The second byte is a number of records encapsulated in the umc1ResponseData. A length field precedes all records (Variable as well as fixed length records). The length field specifies the length of record in Octets. General Response Data Format is shown below: Version Number Of Length of Record 1 Length of Record 2 ... (Byte) Records Record 1 Record 2 (Byte) (Byte) (Byte) The record format depends on the type of data that is being dumped. Record Data Format. For the _ReadTable_ command. 1. Record format for Terminal Info Table (umc1TerminalInfoTable) Fields Terminal Terminal Serial Baud New Id Name Device Rate Terminal Type Id Num Bytes 1 1-21 1 1 1 2. Record Format for Terminal Status Table (umcTerminalStatusTable) Fields Terminal Terminal Id Status Num Bytes 1 1 3. Record Format for Inventory Shelf Table (umcInventoryShelfTable) Fields Terminal Shelf Shelf Id Id Type Num Bytes 1 1 2 4. Record Format for Inventory Plug-in Table (umcInventoryPluginTable) Fields Terminal Shelf Slot Plugin Id Id Id Type Num Bytes 1 1 1 2 5. Record Format for Topology Link Table and ACO Snap Topology Link Table (umc1TopologyLinkTable and umc1AcoSnapTopologyLinkTable) Fields TerminalA TerminaB Id Id Num Bytes 1 1 6. Record Format for cross connect Table( umc1XCTable) Fields XC Index XC Data Num Bytes 1-255 0-255 7. Record Format for GR-303 Group Provisioning Table (umc1GR303Table) Fields GR-303 GR-303 Index Data Num Bytes 1-255 0-255 8. Record Format for TR-08 Group Provisioning Table (umc1TR8Table) Fields TR-08 TR-08 Index Data Num Bytes 1-255 0-255 9. Record Format for ATM Protection Group Provisioning Table (umc1AtmProtGrpTable) Fields ATM ATM Protection Protection Index Data Num Bytes 1-255 0-255 10. Record Format for Port Profile Provisioning Table (umc1PortProfTable) Fields Port Port Profile Profile Index Data Num Bytes 1-255 0-255 11. Record Format for Terminal Span Table (umc1TerminalSpanTable) Fields Near Near Near Near Far Far Far End End End End End End End Term Shelf Slot Plugin Term Shelf Slot Id Id Id type Id Id Id Num Bytes 1 1 1 2 1 1 1 12. Record Format for Shelf Span Table (umc1ShelfSpanTable) Fields Near Near Near Near Far Far Far End End End End End End End Term Shelf Slot Plugin Shelf Slot Plugin Id Id Id type Id Id type Num Bytes 1 1 1 2 1 1 2 For the _GetAllSeqNum_ command. When the umc1CommandId is _GetAllSeqNum_, refer to the object description of umc1SystemAllSeqNbr for the record format. For the _GetActiveTermName_ command. When the umc1CommandId is _GetActiveTermName_, the record format is: Fields Terminal Terminal Terminal Baud New Serial Id Status Name Rate Terminal Device Id Type Num Bytes 1 1 1-21 1 1 1 For the _GetCpuDbDumpPort_ command. When the umc1CommandId is _GetCpuDbDumpPort_, the record format is: Fields Port Number Num Bytes 4 For the _SetOrDelete_ command. When the umc1CommandId is _SetOrDelete_, the record format is: Fields No. of Record Created/Deleted Num Bytes 1 For the _ClearCache_ command. When the umc1CommandId is _ClearCache_, the record format is: Fields Is Cache Cleared Num Bytes 1 Is Cache Cleared value Meaning 1 Cache Successfully cleared If error occured while clearing cache, Agent shall issue _gerErr_ to Management Station. For the _ActivateAco_ command. When the umc1CommandId is _ActivateAco_, the record format is: Fields Result Byte Num Bytes 1 Result Byte value Meaning 1 ACO Activated Successfully If error occured while activating ACO, Agent shall issue _gerErr_ to Management Station. For the _AotRollover_ command. When the umc1CommandId is _AotRollover_, the record format is: Fields Result Byte Num Bytes 1 Result Byte value Meaning 1 AoT to End-To-End ATM Rollover was Successful If error occured while rolling over Aot, Agent shall issue _gerErr_ to Management Station. For the _CurTrafficStats_ command. When the umc1CommandId is _CurTrafficStats_, the record format is: Fields Terminal Total Blocked Used Available Non-Available Current Id Calls Calls Channels Channels Channels Hour Load Num Bytes 1 2 2 2 2 2 2 For the command ID equal to _GetLineCardStatus_, the response data will follow the 'General Response Data Format' as defined above. The definition of the response record will vary depending upon the version of the UMC system. In all cases, the response data will contain a single record. Original Response data format for command ID _GetLineCardStatus_. The version octet = 1. The number of records octet = 1. The length of record #1 and the record format are determined by the octet string returned by the UMC system CPU card. In general, the record represents an array of six elements where each element contains the following attributes for a single circuit/port: port status, downstream rate, downstream SNR margin, upstream rate, and upstream SNR margin. Enhanced Response data format for command ID _GetLineCardStatus_. The version octet = 1. The number of records octet = 1. The record will contain an array of equivalent data elements. The size of the array will depend on the number of circuits/ports supported by the card. The length of each element and the element format are determined by the octet string returned by the UMC system CPU card. In general, each record contains the following attributes for a single circuit/port: port status, downstream rate, downstream SNR margin, upstream rate, and upstream SNR margin, downstream signal attenuation, downstream current channel bit rate, downstream transmitted signal power, downstream relative capacity operation, upstream signal attenuation, upstream current channel bit rate, upstream transmitted signal power, and upstream relative capacity operation. For the command ID equal to _GetAtmStatistics_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet = 2. The response data will contain a two records. The first record represents the 'receive' ATM statistics and the second record represents the 'transmit' ATM statistics. The length of each record and the record format are determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetAdslPmAttribute_, the response data will follow the 'General Response Data Format' as defined above. The response data will contain a single record or multiple equivalent records depending on the 'Data Operation' octet specified in the corresponding command table record. The length of each record and the record format are determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetPmDataBin_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet depends on the 'Data Operation' specified in the request. For a 'GET EXACT' request, the response data will contain - a single record for a single port and bin request. - multiple records for an all port and/or all bin request For a Write request, the response data will contain a single record. The format and length of each record is determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetNBLinkStats_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet = 1 for a Get Exact operation and 1 - 8 (maximum number of GR303/transport link CCS data before overflowing the 255 byte limit) for a Get Progressive operation. The response data can be one of two record types (transport link record or GR303 Group record). The length of each record and the record format are determined by the octet string returned by the UMC system CPU card (IB response payload). For the command ID equal to _ManualProtectionSwitch_, the response data will always contain two records. The first record has a length of one octet and represents the response field from the internal system interface. The possible values are: _RvOk_, _RvInvalidData_, & _RvFailure_. The length and format of the second record are determined by the octet string returned by the internal system interface For each of the following commands ID, the response data will follow the 'General Response Data Format' as defined above. The record format will consist of an octet string as returned by the CPU: _GetVcStatusInfo_ _GetBlockedVccInfo_ _GetAtmBandwidth_ _GetAdslBitsPerTone_ _GetDropTestResults_ For the command ID equal to _GenericIB_, the response data will be formatted as follows: - First octet = version number = 1. - Second octet = number of records octet = 1. - Third octet = size of record in bytes. - Forth octet = first byte of record will contain the CPU error code. - Fifth octet = second byte of record will contain the first byte of the IB payload. - Sixth octet = third byte of record will contain the second byte of the IB payload. - xth octet = last byte of the record will contain the last byte of the IB payload. Note: The third octet will be set to 1 if the CPU returns an error code (not equal to _RvOk_) back to the IPMI via the IB response message. The third octet will be set to a value of greater than 1 if the CPU returns valid data back to the IPMI via the IB response message. The forth octet will contain a value of 0 (RvOk) when valid data is returned in the IB payload. The forth octet will contain a value greater than 0 (error type) when the CPU identifies an error condition. For the command ID equal to _GetAtmStatsPerVcc_, the response data will follow the 'General Response Data Format' as defined above. The response can contain anywhere from zero (0) response records up to six (6) response records. The record format will consist of an octet string as returned by the CPU: " ::= { umc1ResponseTableEntry 3 }
umc1ResponseData OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "This object encapsulates the data corresponding to the umc1ResponseTransNbr and umc1ResponseSeqNbr. The first byte of this umc1ResponseData is a version byte. The second byte is a number of records encapsulated in the umc1ResponseData. A length field precedes all records (Variable as well as fixed length records). The length field specifies the length of record in Octets. General Response Data Format is shown below: Version Number Of Length of Record 1 Length of Record 2 ... (Byte) Records Record 1 Record 2 (Byte) (Byte) (Byte) The record format depends on the type of data that is being dumped. Record Data Format. For the _ReadTable_ command. 1. Record format for Terminal Info Table (umc1TerminalInfoTable) Fields Terminal Terminal Serial Baud New Id Name Device Rate Terminal Type Id Num Bytes 1 1-21 1 1 1 2. Record Format for Terminal Status Table (umcTerminalStatusTable) Fields Terminal Terminal Id Status Num Bytes 1 1 3. Record Format for Inventory Shelf Table (umcInventoryShelfTable) Fields Terminal Shelf Shelf Id Id Type Num Bytes 1 1 2 4. Record Format for Inventory Plug-in Table (umcInventoryPluginTable) Fields Terminal Shelf Slot Plugin Id Id Id Type Num Bytes 1 1 1 2 5. Record Format for Topology Link Table and ACO Snap Topology Link Table (umc1TopologyLinkTable and umc1AcoSnapTopologyLinkTable) Fields TerminalA TerminaB Id Id Num Bytes 1 1 6. Record Format for cross connect Table( umc1XCTable) Fields XC Index XC Data Num Bytes 1-255 0-255 7. Record Format for GR-303 Group Provisioning Table (umc1GR303Table) Fields GR-303 GR-303 Index Data Num Bytes 1-255 0-255 8. Record Format for TR-08 Group Provisioning Table (umc1TR8Table) Fields TR-08 TR-08 Index Data Num Bytes 1-255 0-255 9. Record Format for ATM Protection Group Provisioning Table (umc1AtmProtGrpTable) Fields ATM ATM Protection Protection Index Data Num Bytes 1-255 0-255 10. Record Format for Port Profile Provisioning Table (umc1PortProfTable) Fields Port Port Profile Profile Index Data Num Bytes 1-255 0-255 11. Record Format for Terminal Span Table (umc1TerminalSpanTable) Fields Near Near Near Near Far Far Far End End End End End End End Term Shelf Slot Plugin Term Shelf Slot Id Id Id type Id Id Id Num Bytes 1 1 1 2 1 1 1 12. Record Format for Shelf Span Table (umc1ShelfSpanTable) Fields Near Near Near Near Far Far Far End End End End End End End Term Shelf Slot Plugin Shelf Slot Plugin Id Id Id type Id Id type Num Bytes 1 1 1 2 1 1 2 For the _GetAllSeqNum_ command. When the umc1CommandId is _GetAllSeqNum_, refer to the object description of umc1SystemAllSeqNbr for the record format. For the _GetActiveTermName_ command. When the umc1CommandId is _GetActiveTermName_, the record format is: Fields Terminal Terminal Terminal Baud New Serial Id Status Name Rate Terminal Device Id Type Num Bytes 1 1 1-21 1 1 1 For the _GetCpuDbDumpPort_ command. When the umc1CommandId is _GetCpuDbDumpPort_, the record format is: Fields Port Number Num Bytes 4 For the _SetOrDelete_ command. When the umc1CommandId is _SetOrDelete_, the record format is: Fields No. of Record Created/Deleted Num Bytes 1 For the _ClearCache_ command. When the umc1CommandId is _ClearCache_, the record format is: Fields Is Cache Cleared Num Bytes 1 Is Cache Cleared value Meaning 1 Cache Successfully cleared If error occured while clearing cache, Agent shall issue _gerErr_ to Management Station. For the _ActivateAco_ command. When the umc1CommandId is _ActivateAco_, the record format is: Fields Result Byte Num Bytes 1 Result Byte value Meaning 1 ACO Activated Successfully If error occured while activating ACO, Agent shall issue _gerErr_ to Management Station. For the _AotRollover_ command. When the umc1CommandId is _AotRollover_, the record format is: Fields Result Byte Num Bytes 1 Result Byte value Meaning 1 AoT to End-To-End ATM Rollover was Successful If error occured while rolling over Aot, Agent shall issue _gerErr_ to Management Station. For the _CurTrafficStats_ command. When the umc1CommandId is _CurTrafficStats_, the record format is: Fields Terminal Total Blocked Used Available Non-Available Current Id Calls Calls Channels Channels Channels Hour Load Num Bytes 1 2 2 2 2 2 2 For the command ID equal to _GetLineCardStatus_, the response data will follow the 'General Response Data Format' as defined above. The definition of the response record will vary depending upon the version of the UMC system. In all cases, the response data will contain a single record. Original Response data format for command ID _GetLineCardStatus_. The version octet = 1. The number of records octet = 1. The length of record #1 and the record format are determined by the octet string returned by the UMC system CPU card. In general, the record represents an array of six elements where each element contains the following attributes for a single circuit/port: port status, downstream rate, downstream SNR margin, upstream rate, and upstream SNR margin. Enhanced Response data format for command ID _GetLineCardStatus_. The version octet = 1. The number of records octet = 1. The record will contain an array of equivalent data elements. The size of the array will depend on the number of circuits/ports supported by the card. The length of each element and the element format are determined by the octet string returned by the UMC system CPU card. In general, each record contains the following attributes for a single circuit/port: port status, downstream rate, downstream SNR margin, upstream rate, and upstream SNR margin, downstream signal attenuation, downstream current channel bit rate, downstream transmitted signal power, downstream relative capacity operation, upstream signal attenuation, upstream current channel bit rate, upstream transmitted signal power, and upstream relative capacity operation. For the command ID equal to _GetAtmStatistics_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet = 2. The response data will contain a two records. The first record represents the 'receive' ATM statistics and the second record represents the 'transmit' ATM statistics. The length of each record and the record format are determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetAdslPmAttribute_, the response data will follow the 'General Response Data Format' as defined above. The response data will contain a single record or multiple equivalent records depending on the 'Data Operation' octet specified in the corresponding command table record. The length of each record and the record format are determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetPmDataBin_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet depends on the 'Data Operation' specified in the request. For a 'GET EXACT' request, the response data will contain - a single record for a single port and bin request. - multiple records for an all port and/or all bin request For a Write request, the response data will contain a single record. The format and length of each record is determined by the octet string returned by the UMC system CPU card. For the command ID equal to _GetNBLinkStats_, the response data will follow the 'General Response Data Format' as defined above. The version octet = 1. The number of records octet = 1 for a Get Exact operation and 1 - 8 (maximum number of GR303/transport link CCS data before overflowing the 255 byte limit) for a Get Progressive operation. The response data can be one of two record types (transport link record or GR303 Group record). The length of each record and the record format are determined by the octet string returned by the UMC system CPU card (IB response payload). For the command ID equal to _ManualProtectionSwitch_, the response data will always contain two records. The first record has a length of one octet and represents the response field from the internal system interface. The possible values are: _RvOk_, _RvInvalidData_, & _RvFailure_. The length and format of the second record are determined by the octet string returned by the internal system interface For each of the following commands ID, the response data will follow the 'General Response Data Format' as defined above. The record format will consist of an octet string as returned by the CPU: _GetVcStatusInfo_ _GetBlockedVccInfo_ _GetAtmBandwidth_ _GetAdslBitsPerTone_ _GetDropTestResults_ For the command ID equal to _GenericIB_, the response data will be formatted as follows: - First octet = version number = 1. - Second octet = number of records octet = 1. - Third octet = size of record in bytes. - Forth octet = first byte of record will contain the CPU error code. - Fifth octet = second byte of record will contain the first byte of the IB payload. - Sixth octet = third byte of record will contain the second byte of the IB payload. - xth octet = last byte of the record will contain the last byte of the IB payload. Note: The third octet will be set to 1 if the CPU returns an error code (not equal to _RvOk_) back to the IPMI via the IB response message. The third octet will be set to a value of greater than 1 if the CPU returns valid data back to the IPMI via the IB response message. The forth octet will contain a value of 0 (RvOk) when valid data is returned in the IB payload. The forth octet will contain a value greater than 0 (error type) when the CPU identifies an error condition. For the command ID equal to _GetAtmStatsPerVcc_, the response data will follow the 'General Response Data Format' as defined above. The response can contain anywhere from zero (0) response records up to six (6) response records. The record format will consist of an octet string as returned by the CPU: " ::= { umc1ResponseTableEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2067.1.1.2.5.2.1.1 | umc1ResponseTransNbr | 0 | 0 | This object shall be used by the manager to retrieve the response of a command executed by the Agent. |
| 1.3.6.1.4.1.2067.1.1.2.5.2.1.2 | umc1ResponseSeqNbr | 0 | 0 | This object uniquely identifies the rows of umc1ResponseTable along with umc1ResponseTransNbr. It keeps track of the last fragme… |