We receive an Admin case to inspect the serial numbers to pass or fail before the contract for the device is renewed. This articles provides step by step procedure for RIS cases raised for switching products.

Step-1: Once we receive the admin cases, we send email looping the customer and the C-CARE / Sales who open the case on behalf of the customer with the below commands that is required for inspection:

root> show chassis alarms | no-more
root> show chassis environment no-forwarding | no-more
root> show chassis environment pem | no-more
root> show chassis power | no-more
root> show system alarms | no-more
root> show version detail | no-more
root> show chassis hardware detail | no-more
root> show system core-dumps no-forwarding | no-more
root> show system storage no-forwarding | no-more
root> show chassis routing-engine | no-more
root> show chassis fabric summary  | no-more
root> show chassis fabric fpcs | no-more
root> show chassis fabric plane | no-more
root> show chassis craft-interface | no-more
root> show version invoke-on other-routing-engine | no-more
root> show chassis hardware extensive | no-more
root> show chassis fpc pic-status | no-more
root> show system boot-messages | no-more

Step-2: Additionally we request for below details along with the above commands:

• Front and rear pictures of the device to check for any physical damages. 
• The USB port and Console port are working fine physically or not?
• If the switches are in production?
• Ask to reboot the device and check if the customer agrees for it (Reboot is optional since the device may be in production and customer might not agree).

Step-3: Once the above information is collected then proceed with further checks:

• Perform Physical Checks of the device,

1. Chassis Front Image
2. Chassis Back Image
3. Power supplies
4. Routing Engines
5. Air filter
6. Fan tray
7. Line cards:
8. Flexible PIC Concentrators (FPCs)
9. Physical Interface Cards (PICs)
10. Confirm if the below are healthy,
11. PEM if are healthy,
12. Fan tray is in what condition.
13. RE if in good condition.

• Perform software version check,

Check if the software used is in active support or if an EOS.

• Check for chassis environment,

root> show chassis environment no-forwarding | no-more

• Check for PEM status,

root> show chassis environment pem |no-more

• Check for any active chassis alarms,

root> show chassis alarms | no-more  

• Check for any active system alarms,

root> show system alarms | no-more  

• Check for any recent core-dumps,

root> show system core-dumps no-forwarding | no-more  

• Check for routing engine status,

root> show chassis routing-engine | no-more 

• Check for available storage file system,

root> show system storage no-forwarding | no-more 

Step-4: Create a technical case in SFDC with the serial number of the device for which inspection case was raised. Below are the details to be added while creating technical case:

• Case must be opened with "Employee"
• Account name to be selected "JUNIPER NETWORKS-RIS"
• Summary should be “RIS Technical Log Analysis”
• Description should be “RIS Technical Log Analysis for - <serial number>”
• Case priority must always be "P4"
• Update the resolution notes with inspection status.
• Under category select "REMOTE INSPECTION SERVICES --> FAILED / PASSED RIS CERTIFICATION"
• Under cause select "Undetermined" and "Not reproducible/Single Occurrence"
• Attach the word file with the filename "Remote-Inspection-Checklist-ABCDE1234.docx" and excel sheet with filename "Remote-Inspection-Checklist-ABCDE1234.xlsl" where you have documented the outputs from step-3 and attach it to the admin and technical case.
• Document the technical case number, serial number of the device and inspection status in the admin case internally.
• Proceed with closing the technical case.

Step-5: Once, all the SN’s have been verified. Convey the result in a consolidated email on the admin case as an external note.