How can we help you today?
This FAQ has been written for NEAL (North East Africa and Levant) region. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.

What does the “NIC No Response” alarm mean in an Easergy MiCOM P54x relay, and how can it be investigated?

Issue :
Troubleshooting guidance for the “NIC No Response” alarm in Easergy MiCOM P54x relays, including basic Ethernet checks and the information required for further investigation.

Product Family:
Easergy Micom P54x & application for all Px4x relays,P40 relays

Resolution:

The “NIC No Response” alarm is a major alarm indicating that the relay's Ethernet communication card is not responding or that there may be a communication/connection issue with the Ethernet port.

Before reporting the issue to Schneider Electric Customer Care, please perform the following basic checks:

a) Check the Ethernet port communication

Verify the health and connectivity of the Ethernet port using a ping test.
Record the results of the ping test.

Ping test Procedure :
Ping test

b) Check the physical connection

Double-check the physical connections of the rear Ethernet ports.
Check the Ethernet cables and connections.
If the issue persists, capture a short video showing the relay indication and physical connection when reporting the case.

c) Check communication through Easergy Studio

Verify whether the relay can be connected through the rear Ethernet port using Easergy Studio.
Check whether the relay settings can be successfully extracted.
Information Required for Further Investigation

If further support is required, please provide the following information to your local Schneider Electric Customer Care Center:

1. MiCOM system files

Complete .studioarch file, including the settings, PSL, MCL/ICD files, and available logs such as events, disturbance records, and fault records.
MCL/CID files extracted directly from both the affected and healthy relays, where available.
Complete network architecture/details relevant to the affected relay. Please provide the original/exported files where applicable rather than converting them to PDF.

Extraction procedure Video :https://youtu.be/aH0-VL3XYRA

Can you please arrange MCL/CID file of unhealthy & healthy relay and complete network architecture directly extracted from the affected relays( (not in PDF format)

2. Detailed description of the issue Please describe:

Nature of the problem
Conditions under which the issue appeared
Approximate date and time when the issue occurred
Approximate date and time when troubleshooting/data collection was performed
Tests already performed and their results

3. For SAS/network-related issues Please additionally provide:

Relays/devices involved in the issue
Relevant relay event records
Network traces captured during the issue
Confirmation of whether the captured frames are time-synchronized with the tested system
List of devices involved, including their IP addresses
List of files provided for investigation
Any other relevant observations

4. Point-by-point feedback Please provide the results of checks (a) to (c) and the requested information above. Videos or screenshots may also be included where they help demonstrate the issue.

These details are required to support a detailed investigation by the concerned customer care center.

Local Customer Care support contact details can be found at the following Schneider Electric link:
https://www.se.com/eg/en/work/support/customer-care/contact-schneider-electric.jsp

Schneider Electric Egypt and North East Africa

Explore more
Range:
Users group

Discuss this topic with experts

Visit our community and get advice from experts and peers on this topic and more
Explore more
Range:
  • Products Documentation
  • Software Downloads
  • Product Selector
  • Product Substitution and Replacement
  • Help and Contact Center
  • Find our Offices
  • Get a Quote
  • Where to buy
  • Schneider Electric Community
  • Careers
  • Company Profile
  • Report a misconduct
  • Accessibility
  • Newsroom
  • Investors
  • EcoStruxure
  • Job Search
  • Blog
  • Privacy Policy
  • Cookie Notice
  • Terms of use
  • Change your cookie settings