pktcEnNcsEndPntLVMgmtPolicy

This MIB Object allows the Service Provider to choose
a suitable policy for Loop Voltage behavior on MTAs.  
              
Unless overridden by the operator, the MTA MUST use the
default value specified in the definition of this MIB
Object.
              
The MTA MUST adhere to PacketCable signaling 
requirements, such as the NCS open loop voltage requirement, 
irrespective of any chosen policy. 
              
For MTAs that need to remove loop voltage during the MTA 
initialization phase, in contradiction to a chosen policy,
such a loop voltage removal period MUST NOT exceed 1000ms.
              
              
The MTA MUST  retain the value of this MIB Object across 
hard reboots or soft resets (for a definition of the terms,
please refer to [1]).
              
This MIB object specifies four policies. An informative
illustration of the E-MTA behavior with different policies
is presented in Appendix A. 
              
              
Provisioned line is an MTA Endpoint that has been provided 
with valid per-line configuration data either via the 
configuration file (during provisioning) or the SNMP 
management interface.
              
When the MIB Object is set to a value of 
voltage_at_all_times(1),  - indicating Policy 1 -
the MTA MUST maintain the loop idle voltage on all 
lines, irrespective of the line status.
              
              
When this MIB Object is set to a value of 
voltage_unless_RF_QAM_absent(2)- indicating Policy 2 
- the MTA MUST apply loop idle voltage at all 
times except when it confirms the absence of any 
RF QAM carrier, following a complete scan of the 
spectrum (i.e., loop voltage is maintained during
the scan). When the MTA detects the presence of any 
RF QAM carrier, it MUST apply the loop idle voltage. 
Additionally, the following conditions apply:
  - during a hard reboot, this policy applies at all 
    lines until the MTA is successfully provisioned (
    i.e., pktcMtaDevProvisioningState has a value 
    other than 'inProgress')
  - once the MTA is successfully provisioned (
    (i.e., pktcMtaDevProvisioningState has a value 
    of 'pass(1)', 'passWithWarnings(4)' or 
    'passWithIncompleteParsing(5)') then the policy
    applies to all provisioned lines 
  - upon the onset of a re-initialization due to a 
    soft reset (via SNMP or Rf conditions) the MTA MUST 
    continue to maintain the existing policy and state 
    on previously provisioned lines, unless overridden 
    by a policy or the provisioning process specifies
    otherwise
              
This policy is similar to Policy 1, except for the 
ability to recognize events like cable cuts (due to 
malicious activities, or otherwise).
              
              
The following requirements apply to policies 3 and 4:
- upon the onset of a re-initialization due to a soft reset 
  the MTA MUST continue to maintain the existing policy and 
  state on provisioned lines, unless overridden by a policy 
  or the provisioning process specifies otherwise
- once the provisioning process is completed with the value 
  of the MIB Object pktcMtaDevProvisioningState set to a 
  value of 'pass(1)', 'passWithWarnings(4)' or 
  'passWithIncompleteParsing(5)', the MTA MUST apply the
  chosen policy to all the provisioned lines
              
When this MIB Object is set to a value of 
voltage_based_on_service_or_timers(3)- indicating Policy 3 - 
the MTA MUST adhere to the requirements that follow 
at any given point in time: 
              
     -  when the timer defined by 
       pktcEnNcsEndPntLVMgmtResetTimer has 
        a non-zero value, the MTA MUST apply loop idle voltage 
        under all circumstances (similar to policy 1).
        Refer to the definition of the MIB Object for the
        persistence and timer requirements.
              
     -  when the timer defined by 
        pktcEnNcsEndPntLVMgmtMaintTimer has 
        a non-zero value, the MTA MUST maintain a line's loop 
        idle voltage state that was in effect prior to the timer 
        being set to a non-zero value. Refer to the definition 
        of the MIB Object defining the timer for the persistence 
        and timer requirements.
              
     - When the timers defined by 
       pktcEnNcsEndPntLVMgmtMaintTimer and 
       pktcEnNcsEndPntLVMgmtResetTimer have 
       expired (both have a value of zero), then:
        = the MTA MUST apply loop voltage if the provisioning 
          process is completed with the value of 
          pktcMtaDevProvisioningState set to a value of 
          than 'pass(1)', 'passWithWarnings(4)' or 
          'passWithIncompleteParsing(5)' 
        = During a T4 timeout (note: the timers have expired), 
          the E-MTA MUST remove loop idle voltage on all lines
              
     -  When both the timers are active (i.e., they both have 
        non-zero values), then the timer defined by the MIB 
        Object pktcEnNcsEndPntLVMgmtMaintTimer takes precedence
              
     -  if none of the above cases apply, the MTA MUST remove 
        loop idle voltage on all lines
                              
When the MIB Object is set to a value of 
voltage_based_on_service(4) - indicating Policy 4 - the 
following conditions apply at any given point in time:
              
    - the MTA MUST apply loop idle voltage to all 
    the provisioned lines if the value of the MIB Object 
    'pktcMtaDevProvisioningState' is set to a 
    value of 'pass(1)', 'passWithWarnings(4)' 
    or 'passWithIncompleteParsing(5)' 
              
    - in all other cases, the MTA 
    MUST remove loop idle voltage on all lines.

MIB

PKTC-EN-SIG-MIB

OID

.1.3.6.1.4.1.4491.2.2.6.2.1.2.3.1.1

Type

column

Access

readwrite

Status

current

Parent

pktcEnNcsEndPntLVMgmtTableEntry

Table

pktcEnNcsEndPntLVMgmtTable

Siblings

2