This attribute when set to 'true' triggers the change-over
operation for Externally-Directed Load Balancing.
Setting this attribute to 'true' is known as a commit
operation. A commit operation is considered successful
if the CMTS considers that the entered information
is valid and the transaction can be initiated. It
does not imply that the channel-change operation itself
(i.e. UCC, DCC, DBC transaction) reports success
or completion. A commit operation is considered unsuccessful
if the CMTS determines that there are invalid
attributes values in the ChangeOver object such
that the change-over operation cannot be initiated.
After system initialization all ChangeOver object
parameters are set to default values.
After a successful commit operation all ChangeOver
object parameters are set to default values with the
exception of this attribute (commit) that is set to 'true'.
An unsuccessful commit operation is rejected
and this attribute reports false in subsequent value
queries.
With regard to error checking on a commit operation,
the following aspects are defined:
- The CMTS rejects the commit operation when the MAC address
in MacAddr attribute is not from an existing and
operational cable modem in the CMTS.
- The CMTS rejects the commit operation when there is
already a change-over operation in progress for the
CM, i.e. the corresponding attribute value in the -ChangeOverStatus
object is one of 'messageSent', 'modemDeparting'
or 'waitToSendMessage'.
- The CMTS rejects the commit operation when neither
of the upstream or downstream attribute parameters
of the change-over operation are set.
When the CM is in MRC disabled mode, only UCC/DCC commands
are valid, therefore:
- The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo
in the commit operation.
- The CMTS rejects the commit operation if neither of
DownFrequency or UsChSet were set to non-default values.
- The CMTS rejects the commit operation when the UsChSet
indicates more than one upstream channel.
- A single-upstream-channel change-over operation
(no downstream information) is rejected if the upstream
channel information corresponds to a non-existent
channel or a channel with operational status down.
- The CMTS rejects the commit operation for a downstream
frequency that the CMTS can determine to be invalid.
For example, the downstream frequency corresponds
to a channel that is part of the MD-DS-SG in which the
target CM is currently registered, and this Downstream
Channel is known to be operationally down, in a
test mode, mute state, etc.
- To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC
Domain, the operator needs to reinitialize the CM via
a DCC operation by including the appropriate DownFrequency
and an InitTech allowing only the 'reinitialize
MAC' initialization technique.
When the CM is in MRC enabled mode, DCC and DBC commands
are valid, therefore:
- The CMTS rejects the commit operation if both the Downstream
Frequency (via the DownFrequency attribute)
and the RCC (via the RcpId and RccId) are set to non-default
values.
- The CMTS rejects the commit operation if the MdIfIndex
attribute value is invalid, or if the triplet MdIfIndex,
RcpId, RccId does not resolve in a valid RCC,
or at least one of the indicated downstream channels
is know to be operationally down, in a test mode, mute
state, etc.
- The CMTS rejects the commit operation if it can detect
the UsChSet includes one or more channels that are
not part of the US-SG of the CM, or any of those channels
are in operational status down.
- The CMTS rejects the commit operation if a service flow
entry in the ServiceFlowInfo attribute includes
channels that are not part of the CMs target RCS or TCS.
After processing the commit operation the CMTS creates
or overwrites (if it already exists) an instance
of the ChgOverStatus object for the associated CM.
After a successful commit operation, the CMTS initiates
the change-over transaction using the most appropriate
technique. The potential techniques are:
- UCC - For upstream-channel-only changes on CMs not
operating in MRC mode.
- DCC - For upstream and/or downstream channel changes
on CMs not operating in MRC mode.
- DCC followed by channel assignment in REG-RSP-MP -
For MAC Domain re-assignment on CMs operating in MRC
mode. In this case, the change-over command might only
include a downstream frequency, or might include
an RCC defined in the target MAC domain. The upstream
channel set may or may not be provided. The only applicable
Initialization Technique for this operation
is 'reinitializeMAC'.
- DBC - For upstream and/or downstream channel set changes
on CMs operating in MRC mode.
Parsed from file DOCS-LOADBAL3-MIB.mib
Module: DOCS-LOADBAL3-MIB
This attribute when set to 'true' triggers the change-over
operation for Externally-Directed Load Balancing.
Setting this attribute to 'true' is known as a commit
operation. A commit operation is considered successful
if the CMTS considers that the entered information
is valid and the transaction can be initiated. It
does not imply that the channel-change operation itself
(i.e. UCC, DCC, DBC transaction) reports success
or completion. A commit operation is considered unsuccessful
if the CMTS determines that there are invalid
attributes values in the ChangeOver object such
that the change-over operation cannot be initiated.
After system initialization all ChangeOver object
parameters are set to default values.
After a successful commit operation all ChangeOver
object parameters are set to default values with the
exception of this attribute (commit) that is set to 'true'.
An unsuccessful commit operation is rejected
and this attribute reports false in subsequent value
queries.
With regard to error checking on a commit operation,
the following aspects are defined:
- The CMTS rejects the commit operation when the MAC address
in MacAddr attribute is not from an existing and
operational cable modem in the CMTS.
- The CMTS rejects the commit operation when there is
already a change-over operation in progress for the
CM, i.e. the corresponding attribute value in the -ChangeOverStatus
object is one of 'messageSent', 'modemDeparting'
or 'waitToSendMessage'.
- The CMTS rejects the commit operation when neither
of the upstream or downstream attribute parameters
of the change-over operation are set.
When the CM is in MRC disabled mode, only UCC/DCC commands
are valid, therefore:
- The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo
in the commit operation.
- The CMTS rejects the commit operation if neither of
DownFrequency or UsChSet were set to non-default values.
- The CMTS rejects the commit operation when the UsChSet
indicates more than one upstream channel.
- A single-upstream-channel change-over operation
(no downstream information) is rejected if the upstream
channel information corresponds to a non-existent
channel or a channel with operational status down.
- The CMTS rejects the commit operation for a downstream
frequency that the CMTS can determine to be invalid.
For example, the downstream frequency corresponds
to a channel that is part of the MD-DS-SG in which the
target CM is currently registered, and this Downstream
Channel is known to be operationally down, in a
test mode, mute state, etc.
- To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC
Domain, the operator needs to reinitialize the CM via
a DCC operation by including the appropriate DownFrequency
and an InitTech allowing only the 'reinitialize
MAC' initialization technique.
When the CM is in MRC enabled mode, DCC and DBC commands
are valid, therefore:
- The CMTS rejects the commit operation if both the Downstream
Frequency (via the DownFrequency attribute)
and the RCC (via the RcpId and RccId) are set to non-default
values.
- The CMTS rejects the commit operation if the MdIfIndex
attribute value is invalid, or if the triplet MdIfIndex,
RcpId, RccId does not resolve in a valid RCC,
or at least one of the indicated downstream channels
is know to be operationally down, in a test mode, mute
state, etc.
- The CMTS rejects the commit operation if it can detect
the UsChSet includes one or more channels that are
not part of the US-SG of the CM, or any of those channels
are in operational status down.
- The CMTS rejects the commit operation if a service flow
entry in the ServiceFlowInfo attribute includes
channels that are not part of the CMs target RCS or TCS.
After processing the commit operation the CMTS creates
or overwrites (if it already exists) an instance
of the ChgOverStatus object for the associated CM.
After a successful commit operation, the CMTS initiates
the change-over transaction using the most appropriate
technique. The potential techniques are:
- UCC - For upstream-channel-only changes on CMs not
operating in MRC mode.
- DCC - For upstream and/or downstream channel changes
on CMs not operating in MRC mode.
- DCC followed by channel assignment in REG-RSP-MP -
For MAC Domain re-assignment on CMs operating in MRC
mode. In this case, the change-over command might only
include a downstream frequency, or might include
an RCC defined in the target MAC domain. The upstream
channel set may or may not be provided. The only applicable
Initialization Technique for this operation
is 'reinitializeMAC'.
- DBC - For upstream and/or downstream channel set changes
on CMs operating in MRC mode.
This attribute when set to 'true' triggers the change-over
operation for Externally-Directed Load Balancing.
Setting this attribute to 'true' is known as a commit
operation. A commit operation is considered successful
if the CMTS considers that the entered information
is valid and the transaction can be initiated. It
does not imply that the channel-change operation itself
(i.e. UCC, DCC, DBC transaction) reports success
or completion. A commit operation is considered unsuccessful
if the CMTS determines that there are invalid
attributes values in the ChangeOver object such
that the change-over operation cannot be initiated.
After system initialization all ChangeOver object
parameters are set to default values.
After a successful commit operation all ChangeOver
object parameters are set to default values with the
exception of this attribute (commit) that is set to 'true'.
An unsuccessful commit operation is rejected
and this attribute reports false in subsequent value
queries.
With regard to error checking on a commit operation,
the following aspects are defined:
- The CMTS rejects the commit operation when the MAC address
in MacAddr attribute is not from an existing and
operational cable modem in the CMTS.
- The CMTS rejects the commit operation when there is
already a change-over operation in progress for the
CM, i.e. the corresponding attribute value in the -ChangeOverStatus
object is one of 'messageSent', 'modemDeparting'
or 'waitToSendMessage'.
- The CMTS rejects the commit operation when neither
of the upstream or downstream attribute parameters
of the change-over operation are set.
When the CM is in MRC disabled mode, only UCC/DCC commands
are valid, therefore:
- The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo
in the commit operation.
- The CMTS rejects the commit operation if neither of
DownFrequency or UsChSet were set to non-default values.
- The CMTS rejects the commit operation when the UsChSet
indicates more than one upstream channel.
- A single-upstream-channel change-over operation
(no downstream information) is rejected if the upstream
channel information corresponds to a non-existent
channel or a channel with operational status down.
- The CMTS rejects the commit operation for a downstream
frequency that the CMTS can determine to be invalid.
For example, the downstream frequency corresponds
to a channel that is part of the MD-DS-SG in which the
target CM is currently registered, and this Downstream
Channel is known to be operationally down, in a
test mode, mute state, etc.
- To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC
Domain, the operator needs to reinitialize the CM via
a DCC operation by including the appropriate DownFrequency
and an InitTech allowing only the 'reinitialize
MAC' initialization technique.
When the CM is in MRC enabled mode, DCC and DBC commands
are valid, therefore:
- The CMTS rejects the commit operation if both the Downstream
Frequency (via the DownFrequency attribute)
and the RCC (via the RcpId and RccId) are set to non-default
values.
- The CMTS rejects the commit operation if the MdIfIndex
attribute value is invalid, or if the triplet MdIfIndex,
RcpId, RccId does not resolve in a valid RCC,
or at least one of the indicated downstream channels
is know to be operationally down, in a test mode, mute
state, etc.
- The CMTS rejects the commit operation if it can detect
the UsChSet includes one or more channels that are
not part of the US-SG of the CM, or any of those channels
are in operational status down.
- The CMTS rejects the commit operation if a service flow
entry in the ServiceFlowInfo attribute includes
channels that are not part of the CMs target RCS or TCS.
After processing the commit operation the CMTS creates
or overwrites (if it already exists) an instance
of the ChgOverStatus object for the associated CM.
After a successful commit operation, the CMTS initiates
the change-over transaction using the most appropriate
technique. The potential techniques are:
- UCC - For upstream-channel-only changes on CMs not
operating in MRC mode.
- DCC - For upstream and/or downstream channel changes
on CMs not operating in MRC mode.
- DCC followed by channel assignment in REG-RSP-MP -
For MAC Domain re-assignment on CMs operating in MRC
mode. In this case, the change-over command might only
include a downstream frequency, or might include
an RCC defined in the target MAC domain. The upstream
channel set may or may not be provided. The only applicable
Initialization Technique for this operation
is 'reinitializeMAC'.
- DBC - For upstream and/or downstream channel set changes
on CMs operating in MRC mode.
Parsed from file DOCS-LOADBAL3-MIB.my.txt
Company: None
Module: DOCS-LOADBAL3-MIB
This attribute when set to 'true' triggers the change-over
operation for Externally-Directed Load Balancing.
Setting this attribute to 'true' is known as a commit
operation. A commit operation is considered successful
if the CMTS considers that the entered information
is valid and the transaction can be initiated. It
does not imply that the channel-change operation itself
(i.e. UCC, DCC, DBC transaction) reports success
or completion. A commit operation is considered unsuccessful
if the CMTS determines that there are invalid
attributes values in the ChangeOver object such
that the change-over operation cannot be initiated.
After system initialization all ChangeOver object
parameters are set to default values.
After a successful commit operation all ChangeOver
object parameters are set to default values with the
exception of this attribute (commit) that is set to 'true'.
An unsuccessful commit operation is rejected
and this attribute reports false in subsequent value
queries.
With regard to error checking on a commit operation,
the following aspects are defined:
- The CMTS rejects the commit operation when the MAC address
in MacAddr attribute is not from an existing and
operational cable modem in the CMTS.
- The CMTS rejects the commit operation when there is
already a change-over operation in progress for the
CM, i.e. the corresponding attribute value in the -ChangeOverStatus
object is one of 'messageSent', 'modemDeparting'
or 'waitToSendMessage'.
- The CMTS rejects the commit operation when neither
of the upstream or downstream attribute parameters
of the change-over operation are set.
When the CM is in MRC disabled mode, only UCC/DCC commands
are valid, therefore:
- The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo
in the commit operation.
- The CMTS rejects the commit operation if neither of
DownFrequency or UsChSet were set to non-default values.
- The CMTS rejects the commit operation when the UsChSet
indicates more than one upstream channel.
- A single-upstream-channel change-over operation
(no downstream information) is rejected if the upstream
channel information corresponds to a non-existent
channel or a channel with operational status down.
- The CMTS rejects the commit operation for a downstream
frequency that the CMTS can determine to be invalid.
For example, the downstream frequency corresponds
to a channel that is part of the MD-DS-SG in which the
target CM is currently registered, and this Downstream
Channel is known to be operationally down, in a
test mode, mute state, etc.
- To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC
Domain, the operator needs to reinitialize the CM via
a DCC operation by including the appropriate DownFrequency
and an InitTech allowing only the 'reinitialize
MAC' initialization technique.
When the CM is in MRC enabled mode, DCC and DBC commands
are valid, therefore:
- The CMTS rejects the commit operation if both the Downstream
Frequency (via the DownFrequency attribute)
and the RCC (via the RcpId and RccId) are set to non-default
values.
- The CMTS rejects the commit operation if the MdIfIndex
attribute value is invalid, or if the triplet MdIfIndex,
RcpId, RccId does not resolve in a valid RCC,
or at least one of the indicated downstream channels
is know to be operationally down, in a test mode, mute
state, etc.
- The CMTS rejects the commit operation if it can detect
the UsChSet includes one or more channels that are
not part of the US-SG of the CM, or any of those channels
are in operational status down.
- The CMTS rejects the commit operation if a service flow
entry in the ServiceFlowInfo attribute includes
channels that are not part of the CMs target RCS or TCS.
After processing the commit operation the CMTS creates
or overwrites (if it already exists) an instance
of the ChgOverStatus object for the associated CM.
After a successful commit operation, the CMTS initiates
the change-over transaction using the most appropriate
technique. The potential techniques are:
- UCC - For upstream-channel-only changes on CMs not
operating in MRC mode.
- DCC - For upstream and/or downstream channel changes
on CMs not operating in MRC mode.
- DCC followed by channel assignment in REG-RSP-MP -
For MAC Domain re-assignment on CMs operating in MRC
mode. In this case, the change-over command might only
include a downstream frequency, or might include
an RCC defined in the target MAC domain. The upstream
channel set may or may not be provided. The only applicable
Initialization Technique for this operation
is 'reinitializeMAC'.
- DBC - For upstream and/or downstream channel set changes
on CMs operating in MRC mode.
docsLoadbal3ChgOverGroupCommit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute when set to 'true' triggers the change-over operation for Externally-Directed Load Balancing. Setting this attribute to 'true' is known as a commit operation. A commit operation is considered successful if the CMTS considers that the entered information is valid and the transaction can be initiated. It does not imply that the channel-change operation itself (i.e. UCC, DCC, DBC transaction) reports success or completion. A commit operation is considered unsuccessful if the CMTS determines that there are invalid attributes values in the ChangeOver object such that the change-over operation cannot be initiated. After system initialization all ChangeOver object parameters are set to default values. After a successful commit operation all ChangeOver object parameters are set to default values with the exception of this attribute (commit) that is set to 'true'. An unsuccessful commit operation is rejected and this attribute reports false in subsequent value queries. With regard to error checking on a commit operation, the following aspects are defined: - The CMTS rejects the commit operation when the MAC address in MacAddr attribute is not from an existing and operational cable modem in the CMTS. - The CMTS rejects the commit operation when there is already a change-over operation in progress for the CM, i.e. the corresponding attribute value in the -ChangeOverStatus object is one of 'messageSent', 'modemDeparting' or 'waitToSendMessage'. - The CMTS rejects the commit operation when neither of the upstream or downstream attribute parameters of the change-over operation are set. When the CM is in MRC disabled mode, only UCC/DCC commands are valid, therefore: - The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo in the commit operation. - The CMTS rejects the commit operation if neither of DownFrequency or UsChSet were set to non-default values. - The CMTS rejects the commit operation when the UsChSet indicates more than one upstream channel. - A single-upstream-channel change-over operation (no downstream information) is rejected if the upstream channel information corresponds to a non-existent channel or a channel with operational status down. - The CMTS rejects the commit operation for a downstream frequency that the CMTS can determine to be invalid. For example, the downstream frequency corresponds to a channel that is part of the MD-DS-SG in which the target CM is currently registered, and this Downstream Channel is known to be operationally down, in a test mode, mute state, etc. - To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC Domain, the operator needs to reinitialize the CM via a DCC operation by including the appropriate DownFrequency and an InitTech allowing only the 'reinitialize MAC' initialization technique. When the CM is in MRC enabled mode, DCC and DBC commands are valid, therefore: - The CMTS rejects the commit operation if both the Downstream Frequency (via the DownFrequency attribute) and the RCC (via the RcpId and RccId) are set to non-default values. - The CMTS rejects the commit operation if the MdIfIndex attribute value is invalid, or if the triplet MdIfIndex, RcpId, RccId does not resolve in a valid RCC, or at least one of the indicated downstream channels is know to be operationally down, in a test mode, mute state, etc. - The CMTS rejects the commit operation if it can detect the UsChSet includes one or more channels that are not part of the US-SG of the CM, or any of those channels are in operational status down. - The CMTS rejects the commit operation if a service flow entry in the ServiceFlowInfo attribute includes channels that are not part of the CMs target RCS or TCS. After processing the commit operation the CMTS creates or overwrites (if it already exists) an instance of the ChgOverStatus object for the associated CM. After a successful commit operation, the CMTS initiates the change-over transaction using the most appropriate technique. The potential techniques are: - UCC - For upstream-channel-only changes on CMs not operating in MRC mode. - DCC - For upstream and/or downstream channel changes on CMs not operating in MRC mode. - DCC followed by channel assignment in REG-RSP-MP - For MAC Domain re-assignment on CMs operating in MRC mode. In this case, the change-over command might only include a downstream frequency, or might include an RCC defined in the target MAC domain. The upstream channel set may or may not be provided. The only applicable Initialization Technique for this operation is 'reinitializeMAC'. - DBC - For upstream and/or downstream channel set changes on CMs operating in MRC mode." DEFVAL { false } ::= { docsLoadbal3ChgOverGroup 11 }
docsLoadbal3ChgOverGroupCommit OBJECT-TYPE SYNTAX TruthValue ACCESS read-write STATUS mandatory DESCRIPTION "This attribute when set to 'true' triggers the change-over operation for Externally-Directed Load Balancing. Setting this attribute to 'true' is known as a commit operation. A commit operation is considered successful if the CMTS considers that the entered information is valid and the transaction can be initiated. It does not imply that the channel-change operation itself (i.e. UCC, DCC, DBC transaction) reports success or completion. A commit operation is considered unsuccessful if the CMTS determines that there are invalid attributes values in the ChangeOver object such that the change-over operation cannot be initiated. After system initialization all ChangeOver object parameters are set to default values. After a successful commit operation all ChangeOver object parameters are set to default values with the exception of this attribute (commit) that is set to 'true'. An unsuccessful commit operation is rejected and this attribute reports false in subsequent value queries. With regard to error checking on a commit operation, the following aspects are defined: - The CMTS rejects the commit operation when the MAC address in MacAddr attribute is not from an existing and operational cable modem in the CMTS. - The CMTS rejects the commit operation when there is already a change-over operation in progress for the CM, i.e. the corresponding attribute value in the -ChangeOverStatus object is one of 'messageSent', 'modemDeparting' or 'waitToSendMessage'. - The CMTS rejects the commit operation when neither of the upstream or downstream attribute parameters of the change-over operation are set. When the CM is in MRC disabled mode, only UCC/DCC commands are valid, therefore: - The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo in the commit operation. - The CMTS rejects the commit operation if neither of DownFrequency or UsChSet were set to non-default values. - The CMTS rejects the commit operation when the UsChSet indicates more than one upstream channel. - A single-upstream-channel change-over operation (no downstream information) is rejected if the upstream channel information corresponds to a non-existent channel or a channel with operational status down. - The CMTS rejects the commit operation for a downstream frequency that the CMTS can determine to be invalid. For example, the downstream frequency corresponds to a channel that is part of the MD-DS-SG in which the target CM is currently registered, and this Downstream Channel is known to be operationally down, in a test mode, mute state, etc. - To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC Domain, the operator needs to reinitialize the CM via a DCC operation by including the appropriate DownFrequency and an InitTech allowing only the 'reinitialize MAC' initialization technique. When the CM is in MRC enabled mode, DCC and DBC commands are valid, therefore: - The CMTS rejects the commit operation if both the Downstream Frequency (via the DownFrequency attribute) and the RCC (via the RcpId and RccId) are set to non-default values. - The CMTS rejects the commit operation if the MdIfIndex attribute value is invalid, or if the triplet MdIfIndex, RcpId, RccId does not resolve in a valid RCC, or at least one of the indicated downstream channels is know to be operationally down, in a test mode, mute state, etc. - The CMTS rejects the commit operation if it can detect the UsChSet includes one or more channels that are not part of the US-SG of the CM, or any of those channels are in operational status down. - The CMTS rejects the commit operation if a service flow entry in the ServiceFlowInfo attribute includes channels that are not part of the CMs target RCS or TCS. After processing the commit operation the CMTS creates or overwrites (if it already exists) an instance of the ChgOverStatus object for the associated CM. After a successful commit operation, the CMTS initiates the change-over transaction using the most appropriate technique. The potential techniques are: - UCC - For upstream-channel-only changes on CMs not operating in MRC mode. - DCC - For upstream and/or downstream channel changes on CMs not operating in MRC mode. - DCC followed by channel assignment in REG-RSP-MP - For MAC Domain re-assignment on CMs operating in MRC mode. In this case, the change-over command might only include a downstream frequency, or might include an RCC defined in the target MAC domain. The upstream channel set may or may not be provided. The only applicable Initialization Technique for this operation is 'reinitializeMAC'. - DBC - For upstream and/or downstream channel set changes on CMs operating in MRC mode." DEFVAL { false } ::= { docsLoadbal3ChgOverGroup 11 }
Vendor: Cable Television Laboratories, Inc.
Module: DOCS-LOADBAL3-MIB
[Automatically extracted from oidview.com]
docsLoadbal3ChgOverGroupCommit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute when set to 'true' triggers the change-over operation for Externally-Directed Load Balancing. Setting this attribute to 'true' is known as a commit operation. A commit operation is considered successful if the CMTS considers that the entered information is valid and the transaction can be initiated. It does not imply that the channel-change operation itself (i.e. UCC, DCC, DBC transaction) reports success or completion. A commit operation is considered unsuccessful if the CMTS determines that there are invalid attributes values in the ChangeOver object such that the change-over operation cannot be initiated. After system initialization all ChangeOver object parameters are set to default values. After a successful commit operation all ChangeOver object parameters are set to default values with the exception of this attribute (commit) that is set to 'true'. An unsuccessful commit operation is rejected and this attribute reports false in subsequent value queries. With regard to error checking on a commit operation, the following aspects are defined: - The CMTS rejects the commit operation when the MAC address in MacAddr attribute is not from an existing and operational cable modem in the CMTS. - The CMTS rejects the commit operation when there is already a change-over operation in progress for the CM, i.e. the corresponding attribute value in the -ChangeOverStatus object is one of 'messageSent', 'modemDeparting' or 'waitToSendMessage'. - The CMTS rejects the commit operation when neither of the upstream or downstream attribute parameters of the change-over operation are set. When the CM is in MRC disabled mode, only UCC/DCC commands are valid, therefore: - The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo in the commit operation. - The CMTS rejects the commit operation if neither of DownFrequency or UsChSet were set to non-default values. - The CMTS rejects the commit operation when the UsChSet indicates more than one upstream channel. - A single-upstream-channel change-over operation (no downstream information) is rejected if the upstream channel information corresponds to a non-existent channel or a channel with operational status down. - The CMTS rejects the commit operation for a downstream frequency that the CMTS can determine to be invalid. For example, the downstream frequency corresponds to a channel that is part of the MD-DS-SG in which the target CM is currently registered, and this Downstream Channel is known to be operationally down, in a test mode, mute state, etc. - To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC Domain, the operator needs to reinitialize the CM via a DCC operation by including the appropriate DownFrequency and an InitTech allowing only the 'reinitialize MAC' initialization technique. When the CM is in MRC enabled mode, DCC and DBC commands are valid, therefore: - The CMTS rejects the commit operation if both the Downstream Frequency (via the DownFrequency attribute) and the RCC (via the RcpId and RccId) are set to non-default values. - The CMTS rejects the commit operation if the MdIfIndex attribute value is invalid, or if the triplet MdIfIndex, RcpId, RccId does not resolve in a valid RCC, or at least one of the indicated downstream channels is know to be operationally down, in a test mode, mute state, etc. - The CMTS rejects the commit operation if it can detect the UsChSet includes one or more channels that are not part of the US-SG of the CM, or any of those channels are in operational status down. - The CMTS rejects the commit operation if a service flow entry in the ServiceFlowInfo attribute includes channels that are not part of the CMs target RCS or TCS. After processing the commit operation the CMTS creates or overwrites (if it already exists) an instance of the ChgOverStatus object for the associated CM. After a successful commit operation, the CMTS initiates the change-over transaction using the most appropriate technique. The potential techniques are: - UCC - For upstream-channel-only changes on CMs not operating in MRC mode. - DCC - For upstream and/or downstream channel changes on CMs not operating in MRC mode. - DCC followed by channel assignment in REG-RSP-MP - For MAC Domain re-assignment on CMs operating in MRC mode. In this case, the change-over command might only include a downstream frequency, or might include an RCC defined in the target MAC domain. The upstream channel set may or may not be provided. The only applicable Initialization Technique for this operation is 'reinitializeMAC'. - DBC - For upstream and/or downstream channel set changes on CMs operating in MRC mode." DEFVAL { false } ::= { docsLoadbal3ChgOverGroup 11 }
docsLoadbal3ChgOverGroupCommit OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This attribute when set to 'true' triggers the change-over operation for Externally-Directed Load Balancing. Setting this attribute to 'true' is known as a commit operation. A commit operation is considered successful if the CMTS considers that the entered information is valid and the transaction can be initiated. It does not imply that the channel-change operation itself (i.e. UCC, DCC, DBC transaction) reports success or completion. A commit operation is considered unsuccessful if the CMTS determines that there are invalid attributes values in the ChangeOver object such that the change-over operation cannot be initiated. After system initialization all ChangeOver object parameters are set to default values. After a successful commit operation all ChangeOver object parameters are set to default values with the exception of this attribute (commit) that is set to 'true'. An unsuccessful commit operation is rejected and this attribute reports false in subsequent value queries. With regard to error checking on a commit operation, the following aspects are defined: - The CMTS rejects the commit operation when the MAC address in MacAddr attribute is not from an existing and operational cable modem in the CMTS. - The CMTS rejects the commit operation when there is already a change-over operation in progress for the CM, i.e. the corresponding attribute value in the -ChangeOverStatus object is one of 'messageSent', 'modemDeparting' or 'waitToSendMessage'. - The CMTS rejects the commit operation when neither of the upstream or downstream attribute parameters of the change-over operation are set. When the CM is in MRC disabled mode, only UCC/DCC commands are valid, therefore: - The CMTS ignores the values of RcpId, RccId, and ServiceFlowInfo in the commit operation. - The CMTS rejects the commit operation if neither of DownFrequency or UsChSet were set to non-default values. - The CMTS rejects the commit operation when the UsChSet indicates more than one upstream channel. - A single-upstream-channel change-over operation (no downstream information) is rejected if the upstream channel information corresponds to a non-existent channel or a channel with operational status down. - The CMTS rejects the commit operation for a downstream frequency that the CMTS can determine to be invalid. For example, the downstream frequency corresponds to a channel that is part of the MD-DS-SG in which the target CM is currently registered, and this Downstream Channel is known to be operationally down, in a test mode, mute state, etc. - To move a MRC/MTC-capable CM to a MRC/MTC enabled MAC Domain, the operator needs to reinitialize the CM via a DCC operation by including the appropriate DownFrequency and an InitTech allowing only the 'reinitialize MAC' initialization technique. When the CM is in MRC enabled mode, DCC and DBC commands are valid, therefore: - The CMTS rejects the commit operation if both the Downstream Frequency (via the DownFrequency attribute) and the RCC (via the RcpId and RccId) are set to non-default values. - The CMTS rejects the commit operation if the MdIfIndex attribute value is invalid, or if the triplet MdIfIndex, RcpId, RccId does not resolve in a valid RCC, or at least one of the indicated downstream channels is know to be operationally down, in a test mode, mute state, etc. - The CMTS rejects the commit operation if it can detect the UsChSet includes one or more channels that are not part of the US-SG of the CM, or any of those channels are in operational status down. - The CMTS rejects the commit operation if a service flow entry in the ServiceFlowInfo attribute includes channels that are not part of the CMs target RCS or TCS. After processing the commit operation the CMTS creates or overwrites (if it already exists) an instance of the ChgOverStatus object for the associated CM. After a successful commit operation, the CMTS initiates the change-over transaction using the most appropriate technique. The potential techniques are: - UCC - For upstream-channel-only changes on CMs not operating in MRC mode. - DCC - For upstream and/or downstream channel changes on CMs not operating in MRC mode. - DCC followed by channel assignment in REG-RSP-MP - For MAC Domain re-assignment on CMs operating in MRC mode. In this case, the change-over command might only include a downstream frequency, or might include an RCC defined in the target MAC domain. The upstream channel set may or may not be provided. The only applicable Initialization Technique for this operation is 'reinitializeMAC'. - DBC - For upstream and/or downstream channel set changes on CMs operating in MRC mode." DEFVAL { false } ::= { docsLoadbal3ChgOverGroup 11 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4491.2.1.22.1.2.11.0 | docsLoadbal3ChgOverGroupCommit | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4491.2.1.22.1.2.1 | docsLoadbal3ChgOverGroupMacAddress | 1 | 1 | This attribute represents the MAC address of the cable modem that the CMTS instructs to move to a new downstream and/or upstream … |
| 1.3.6.1.4.1.4491.2.1.22.1.2.2 | docsLoadbal3ChgOverGroupInitTech | 1 | 1 | This attribute represents the initialization technique that the cable modem is instructed to use when performing multiple-channel… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.3 | docsLoadbal3ChgOverGroupForceUCC | 1 | 1 | This attribute when set to 'true' indicates that the CMTS forces UCC messages instead of DCC messages. In some cases the CMTS may… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.4 | docsLoadbal3ChgOverGroupdownFrequency | 1 | 1 | This attribute represents a single-downstream frequency to which the cable modem is instructed to move using a DCC request. The v… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.5 | docsLoadbal3ChgOverGroupMdIfIndex | 1 | 1 | This attribute describes the MAC Domain Interface index of the triplet: Mac Domain, RCP-ID and RCC Status Index of the RccStatus … |
| 1.3.6.1.4.1.4491.2.1.22.1.2.6 | docsLoadbal3ChgOverGroupRcpId | 1 | 1 | This attribute describes the RCP-ID of the triplet: Mac Domain, RCP-ID and RCC Status Index of the RccStatus object that represen… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.7 | docsLoadbal3ChgOverGroupRccId | 1 | 1 | This attribute describes the RCC Status Index of the triplet: Mac Domain, RCP-ID and RCC Status Index of the RccStatus object tha… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.8 | docsLoadbal3ChgOverGroupUsChSet | 1 | 1 | This attribute describes the Channel list (within the context of the MAC domain identified by MdIfIndex) that represents the fina… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.9 | docsLoadbal3ChgOverGroupServiceFlowInfo | 1 | 1 | This attribute provides a list of Service Flow ID-Channel Set ID pairs used to control Service Flow assignment in the change-over… |
| 1.3.6.1.4.1.4491.2.1.22.1.2.10 | docsLoadbal3ChgOverGroupTransactionId | 1 | 1 | This attribute represents an operator identifier for the change-over operation to be used to correlate logged information in the … |
| 1.3.6.1.4.1.4491.2.1.22.1.2.12 | docsLoadbal3ChgOverGroupLastCommit | 1 | 1 | The value of sysUpTime when the attribute Commit was last set to true. Zero if never set. |