Logical instability

CST has 5 logs exist in NST and when asked him about this logs informed me that he restart his CPE 5 times this consider Multiple - Login

• True

• False

Cst has logical Instability​ TKT with update 'Announcement has been sent' and no Outage exist

• A- Escalate to SLS

• B- Refer to your Team Leader to check Outage with him

- Cst has logical Instability​ TKT with update' Session is up and stable since 11 PM' , there are 2 logs after mentioned time and customer didn’t restart CPE your action :

• A- Re-escalate to SLS

• B- Reset & Re-configure the CPE

• C- Add DNS

While Trouble shooting Logical instability if CST has PC connected via wireless your action

• A- Check spyware

• B- Check Multiple Login

• C - Re-configure Wireless

CST has Logical Instability case and has congested POP

• A- Stop Trouble shooting and inform CST script

• B- continue Trouble sooting

Customer complain from instability ,Line supported by Assia, you found Last fix within 24 hours from now, Clear View output : No DSL Physical Layer Issue Is Detected , your action :

• A- Handle as Logical Instability

• B- Handle as physical instability

• C- Handle BLQ

While Trouble shooting Logical Instability CST must connect his CPE via Cable

• True

• False

Spyware command :

• A- Ping

• B- Ipconfig/flushdns

• C- Netstat -n -o

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

• A- Check with another CPE

• B- Reset and Reconfigure

• C- Escalate to SLS

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

• A- Ceck packet loss from CPE IP

• B- Reset and Reconfigure

• C- Escalate to SLS