Important points:

1. How to check CPE in ZF2741 and T301

 Go to particular ZD, click on dashboard, click on client.
 Filter Rows where: Client MAC  Exactly equals bc:62:9f:01:76:d2 and query.
 Click on # client devices in active client: search items
 Copy CPE mac and paste as it is bc:62:9f:01:76:d2 from 2nd page RFTR.
2. HOW TO FIND AP IN Flex master in T301 and ZF2741 :

 Click on AP (via AP MAC)

 Device View: All Zone Directors  Report Type: All Access Points AP Type: Aps Period:
Greater 24 hours Filter Rows where: MAC Address Exactly equals f8:e7:1e:18:c8:00
(AP MAC)

 Click on AP (via AP DESCRIPTION)

 Device View: All Zone Directors  Report Type: All Access Points AP Type: Aps Period:
Greater 24 hours Filter Rows where Description Contains Sundram Tower Ram Bagh
RAP-2 (AP DESCRIPTION)
3. How to check CPE in Cambium
 Go to toolsmesh peersmesh client copy paste CPE from RFTR 2nd page.
4. HOW TO FIND AP IN Cambium,
 Search (blank) AP name or AP description.

5. Command for ping response/ success rate:

 Command for Telnet:

Username: team

Password: team

#pi (ip address) c 1000

 Command for Telnet:

Username: team

Password: team

>en

>cisco3400
# pi (ip address) r 1000

 Command for core:

Username: monitor

Password: m0n!t0R123

>ping –c 1000 –m 1 (ip address)

6. If CPE and connected clients have complete drop/ If we want to know the exact core/Telnet.
How to find/procedure:
 Click on any core. Type username & password
 Type command: sh ip route (ip address)
 It will reflect (ip address) from 192.168.2.x

 Then open kitty/telnet/core type 192.168.2.x in upper side

 Select telnet & then open.

 Use credential according and use ping command to proceed further.

 To Abort telnet /core/ Kitty/: press Cntrl+c, Cntrl+shift+6
Note: Varanasi is exception for this, for Varanasi case always ping device from
192.168.2.194 first then 2.193.
7. How to raise EV:
Create new TT

Type Area Sub-Area

Service Request Service Change Field Engineer Visit
 Click on required info:
 Notes
 Copy paste notes
 Select Field engineer visit reason
 Mention problem description and case description
 Submit & copy SR #
 Go to connectivity /Speed issue which is progressing
 Click on new, select resolution paste SR TT
 Go to required info and close SR.

8. (FOR L1) If there is AP Outage/AP Event seen at TT Creation time and AP is up more than 1
hr. As per XPERT TT is parked under RFTR_RESOLVED_QUEUE.
Create new TT by click on NEW

Type Area Sub-Area

FTR Technical AP outage

In Case description: AP MAC: & submit TT

9. (FOR L1) LDAP status:

 If LDAP status ACTIVE : Normal action
 If LDAP status is SUSPENDED: park TT under BACKEND_FINE_QUEUE mention
RFTR 1st page and send inactive message.
 If LDAP status is BLOCKED: park TT under BACKEND_FINE_QUEUE mention RFTR
1st page and send inactive message, highlight to TL

10. For RMDU INSTALLATION Type:

 RFTR 2nd page is mandatory where we can see NEAR end and FAR end.
 If NEAR end ping response/success rate having complete drop or RFTR 2 nd page is
incomplete kindly check HFODCPE in RFTR 2nd page.
 Sh arp | i 4e02
 00:19:3b:23:4e:02
 If any issue in RMDU installation or BNMDU installation. kindly contact to TL.
11. If multiple Mac seen in more data with different backend, RFTR 2 nd Page hyperlink NA,
RFTR 3rd page is no record found, 4th EV/4th NOC within 30 days highlight to TL.
12. While raising EV check Last EV closure is mandatory and should understand. If any doubt
ask TL.
13. (FOR L1) Check Case description and understand in every case.
14. While moving TT to above 3 Queue, i.e. PERFORMANCE_NETWORK_QUEUE,
FTAP_DISCONNECTED_QUEUE, AP4HRS_DISCONNECTED_QUEUE. "REF TT" & Case
description should be captured properly, these details are given In SOP under RFNOC cases
Refer TT. This is absolutely necessary or else TT will be again move to your bucket..
15. Backend details should be properly capture in Notes while moving TTs to performance
queue, eg. If AP packet drop / bandwidth issue found then, Don't just Copy AP ping, entire
AP details should be captured in note which is there in Cambium or particular ZD.
16. For HFODCPE roaming case, AP parameters should be check and captured, most of agents
not doing that. Also in REF TT : HFODCPE roaming issue & in case description " HFODCPE
MAC & Parent AP MAC" should be mentioned properly is necessary for network team for
mac binding..
17. If AP showing disconnected more than 24 hours then don't blindly move TT to
AP4HOURSdisconnected queue, usually AP doesn't gets down for that much time, here most
probably you are checking incorrect details or AP migrated to different ZD so check
properly again or with AP Name (Description) if needed take help of TL.
18. While checking connected clients.
 Connectivity issue: Top 4 clients with good signal check ping response of respective
CPE and it should >=99% (In case of HFODCPE connected client should have VLAN
99 or 1 & In case of ODCPE connected client should have VLAN102 or 103)
 Speed issue: Top 4 clients with good signal check ping response and speed flex of
respective CPE.

19. Find zf2741 AP and CPE from respective city.

 City Unify Zf2741 Flexmaster
Agra Delhi Delhi
Ahmedaba 20. FOR L1) Kindly refer SOP for RFTR
d Mumbai Ahmedabad updated for SMS ,Email & Rate plan.
Allahabad Delhi Delhi 21. Some shortcut key:
Hyderaba Cntrl+c=Copy
Bangalore d Bangalore Cntrl+v= paste
Bhopal Mumbai Indore Cntrl+f= search
Hyderaba Fn+F9= Email
Chennai d Chennai Cntrl+W= Close browser
Hyderaba Cntrl+a= Select all
Coimbatore d Chennai 22. AP flapping should be checked in
Delhi Delhi Delhi events as well as in CN-Maestro.
Hyderaba
Hyderabad d Hyderabad
Indore Mumbai Indore
Jabalpur Mumbai Indore
Jaipur Delhi Delhi
Kanpur Delhi Delhi
Kolkata Mumbai Kolkata
Lucknow Delhi Delhi
Meerut Delhi Delhi
Mumbai Mumbai Mumbai
Nagpur Mumbai Pune
Pune Mumbai Pune
Raipur Mumbai Indore
Rajkot Mumbai Ahmedabad
Surat Mumbai Surat
Vadodara Mumbai Ahmedabad
Hyderaba
Vizag d Hyderabad
Varanasi Delhi Delhi