- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2021 01:58 AM
Hi all,
I have issue with customer that said the module was faulty. Below is the error log that i received.
2021 Jan 3 09:01:49 SPMY-N7K-B-CORE %PLATFORM-2-MOD_DETECT: Module 10 detected (Serial number JAF1424CAHJ) Module-Type 10 Gbps Ethernet Module Model N7K-M132XP -12 2021 Jan 3 09:01:49 SPMY-N7K-B-CORE %PLATFORM-2-MOD_PWRUP: Module 10 powered up (Serial number JAF1424CAHJ) 2021 Jan 3 09:01:49 SPMY-N7K-B-CORE %PLATFORM-5-MOD_STATUS: Module 10 current-s tatus is MOD_STATUS_POWERED_UP 2021 Jan 3 09:02:11 SPMY-N7K-B-CORE %PLATFORM-2-MOD_PWRFAIL: Module 10 failed t o power up (Serial number JAF1424CAHJ)
The module status is powered-dn
N7K-B-CORE# show module Mod Ports Module-Type Model Status --- ----- ----------------------------------- ------------------ ---------- 2 48 10/100/1000 Mbps Ethernet Module N7K-M148GT-11 ok 5 0 Supervisor Module-1X N7K-SUP1 active * 6 0 Supervisor Module-1X N7K-SUP1 ha-standby 10 0 10 Gbps Ethernet Module powered-dn Mod Power-Status Reason --- ------------ --------------------------- 10 powered-dn Unable to power up card (Power_OK not set) Mod Sw Hw --- -------------- ------ 2 6.2(24) 1.9 5 6.2(24) 1.6 6 6.2(24) 1.6 Mod MAC-Address(es) Serial-Num --- -------------------------------------- ---------- 2 54-75-d0-c3-69-a8 to 54-75-d0-c3-69-db JAF1419BMDH 5 00-26-98-22-ca-58 to 00-26-98-22-ca-5f JAF1417DKJA 6 00-26-98-22-4b-e8 to 00-26-98-22-4b-ef JAF1417DBEM Mod Online Diag Status --- ------------------ 2 Pass 5 Pass 6 Pass Xbar Ports Module-Type Model Status --- ----- ----------------------------------- ------------------ ---------- 1 0 Fabric Module 1 N7K-C7010-FAB-1 ok 2 0 Fabric Module 1 N7K-C7010-FAB-1 ok 3 0 Fabric Module 1 N7K-C7010-FAB-1 ok
Please advise. thanks
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2021 02:33 AM
There may be some reasons,
1. Power capacity
2. Software bug.
3. Try to reseat the module and enable diagnosis before enable and capture all logs to understand the issue.
also, look FN
https://www.cisco.com/c/en/us/support/docs/field-notices/637/fn63751.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2021 02:33 AM
There may be some reasons,
1. Power capacity
2. Software bug.
3. Try to reseat the module and enable diagnosis before enable and capture all logs to understand the issue.
also, look FN
https://www.cisco.com/c/en/us/support/docs/field-notices/637/fn63751.html
