Logical instability

Cst has logical instability with multi-login more than 3 Min reset and reconfiguration done and problem still the same so the right action will be.

• Inform Customer To Check With Another CPE

• Escalate to SLS

• Reset & Reconfigure again

For logical instability case (Multiple Login = 3 min) Reset and Reconfigure , still the same issue

• Escalate ticket to SLS

• Adjust Mtu

Cst has logical Instability case connected through cable CST has spywares CCA action :

• Stop Trouble Shoot and CST must has clean PC

• Continue Trouble Shoot

CST has Logical Instability case and has congested POP

• Stop Trouble shooting and inform CST script

• continue Trouble shooting

For logical instability case (No Multi-Login) , no spyware and packet loss from Google IP was 30% your action will .

• Check packet loss from CPE IP

• Reset and Reconfigure

• Escalate to SLS

Cst has Logical Instability​ TKT with update 'No problem from network side let customer check his CPE' CCA action:

• No Steps needed, Let customer check with another CPE

• Add WE DNS

• Add Google DNS

We can direct customer to our CSO to configure the locked router by another company.

• True

• False

logical instability case will escalated to :

• SLS

• IU

• Second level advanced

SLA for logical instability cases will be

• 2-5 H

• 2 H

• 2 WD

Escalate un supported logical instability cases with status

• Open

• Waiting for Research

• Waiting for response