PHTv5 & Diag tools(IS_10/2018) Flashcards
What are the five new ICFR location indicators in v5 of PHT
Solo,Outlet,Home,Drop, and Network
When we cannot isolate the ICFR fault to specific location in the home or drop, although we have checked neighbors and eliminated a potential network issue as the cause
Solo
When an ICFR fault is isolated to a specific outlet that feeds the device in the home
outlet
When an ICFR fault is isolated to a common point in the home that feeds multiple devices but does not affect all devices in the home
home
When an ICFR fault is isolated to a common point that feeds all devices in the home. We have checked neighbors and eliminated a potential network issue as the cause
drop
When an ICFR fault is isolated to a common point in the network that feeds multiple accounts. At least one other neighbor account has an ICFR signature match
network
Upper fail for Actual upstream transmit
> 54 dBmV
Lower fail for Actual upstream transmit
< 25 dBmV
five or more spikes are at least =>10dB above the average amplitude for that given frequency area, then that condition will trigger a
MODERATE FM Ingress pass
five or more ingress spikes start to peak =>15dB above the average amplitude, then that condition will trigger
SEVERE FM Ingress failure.
Account passes but may alert tech to issues
Pass with Warnings
Account passes due to NWT event on account
Pass with Overides
(UET)
Upstream Extended Transmit
A growing number of devices in our network have Upstream Extended Transmit (UET) capabilities and can transmit___higher than the initial DOCSIS 3.0 specification allowed
3 dBmV
the level a device is transmitting at, or would need to transmit at in order to reach the CMTS at the proper input level
Actual US Tx
A registration state of 1,2,3 or 5 on any channel indicates that a device is not utilizing those channels and is in
partial bonding mode
If a Device is transmitting at maximum power and still cannot reach the CMTS at the requested input level, generally 0 dBmV, it is in a state called
compression
DOCSIS 3.0 devices have the ability to send and receive data transmissions across multiple US and DS channels, this is called
bonding
(FBC)
Full Band Capture
4 ways to access customer in PHT
MAC Address, Home Address, Account #, Phone #
PHT results fall into 4 possible results:
Pass• Pass W/ Warnings • Pass W/Overrides • FAIL
What’s an Unrecognizable device (PHT) PHT pass with warning examples
active device on an account (account at least 3 days old) that has been unresponsive for longer than 24 hours
Unrecognizable Device, Incomplete D3P Data, Service Call Failure, Missing PHY Rate are override examples for
PASS W/ WARNINGS
CMTS knows the device has been online within the prior 24 hours but device is offline
Unresponsive Device
Poll for data is missing data (could result from poor cell connectivity or disruption during test)
Incomplete DP3 Data
Failure to call data sources (cell connectivity, VPN drop, tools outage)
Service Call Failure
Call from X-Ray failed to return PHY rates for all devices
Missing PHY Rate
US Tx, Ds SNR, Ds RX, spectra suckout, spectra wave are override examples for
PHT Pass w/override
filter, outage, poe filter, snr delta, true node are what
PHT analysis types
Downstream RX upper fail
> 13 dBmV
Downstream SNR single threshold fail
<33dB
MoCA PHY Rate single threshold fail
< 200 Mbps (Xi to Xi rates excluded)
FLUX ICFR single threshold fail
> = 3 dB ICFR (non-network issue)
Downstream RX lower fail
< -13 dBmV
4 ways to access customer in PHT
MAC Address, Home Address, Account #, Phone #
EPON Us Rx upper fail
>
- 4.0 dBm
EPON Ds Rx lower fail
< -28.5dBm
EPON Us Rx lower fail
< -28.0 dBm
EPON Ds Rx upper fail
> -8.0 dBm
SpectraCM impairments single threshold fail
Any Individual Impairment <>ACP (suckout and wave only)
FM ingress poller single threshold fail
severe FM ingress
MoCA bridged network single threshold fail
device from another account on MoCA network
MoCA segmented network single threshold fail
multiple separate MoCA networks on account
This means that there is only one device with a MoCA interface assigned to the target account, so it is not of concern that it is by itself with no other nodes to talk to
singleExpected
This means that the MoCA interface of this device has been disabled, typically something that is only done by Field Operations or Customer Care personnel. The device is not part of a MoCA network by design.
mocaDisabled
This means that the device responds via DOCSIS interrogation, but either doesn’t appear on the MoCA network or is by itself on a segment separate from other devices.
possiblePhysicalImpairment
This is a serious issue as the device is powered up and on plant, indicating the customer’s intent to use it, but it is not talking to other MoCA-capable device in the home. This will usually accompany a split network indication
possiblePhysicalImpairment
This means the device is not responding via DOCSIS or MoCA and therefore there is not a way to determine its current state.
deviceNotResponding
This indicates one of a number of unusual states defined in the TR-181 spec that Xi STBs and XB wireless gateways can enter. We don’t believe that the RDK teams have implemented setting the MoCA status to one of these states, but it is for future-proofing in case they do.
mocaInterfaceFault
This indicates that MoCA is reporting what appears to be illegal states or other behaviors that don’t have a clear root cause.
mocaUnknownReason
singleExpected, mocaDisabled, possiblePhysicalImpairment, deviceNotResponding, mocaInterfaceFault, mocaUnknownReason refer to what?
MoCA Isolated Device Analysis
