Bad P_Key : how to run down this issue

[gmckee]

Hi ,

I have these log messages in UFM log.

What do they mean ? And how can I fix this issue ?

Jul 21 15:24:46 334009 [FF6CC700] 0x01 → log_trap_info: Bad P_Key:0xcc2f on SL:0 from LID1:80 (GUID 0x946dae030057f07a) QP1:0x104c to LID2:83 (GUID 0x946dae030093e282) QP2:0x1
Jul 21 15:24:46 334024 [FF6CC700] 0x02 → log_notice: Reporting Generic Notice type:2 num:259 (Bad P_Key (switch external port)) from LID:110 GID:fe80::900a:8403:7b:91c0
Jul 21 15:24:47 437691 [AEE3700] 0x01 → log_trap_info: Received Generic Notice type:2 num:259 (Bad P_Key (switch external port)) Producer:2 (Switch) from LID:110 TID:0x00006dc600000103
Jul 21 15:24:47 437706 [AEE3700] 0x01 → log_trap_info: Bad P_Key:0xcc2f on SL:0 from LID1:125 (GUID 0x946dae030070dee2) QP1:0x104c to LID2:83 (GUID 0x946dae030093e282) QP2:0x1
Jul 21 15:24:47 437721 [AEE3700] 0x02 → log_notice: Reporting Generic Notice type:2 num:259 (Bad P_Key (switch external port)) from LID:110 GID:fe80::900a:8403:7b:91c0
Jul 21 15:24:48 370384 [FCEC7700] 0x01 → mcmr_rcv_join_mgrp: ERR 1B11: method = SubnAdmSet, scope_state = 0x1, component mask = 0x0000000000010083, expected comp mask = 0x00000000000130c7, MGID: ff12:401b:e394::ffff:ffff from port 0x946dae030070ed4a (gmckee-vm1 HCA-1)
Jul 21 15:24:48 541407 [24F17700] 0x01 → log_trap_info: Received Generic Notice type:2 num:259 (Bad P_Key (switch external port)) Producer:2 (Switch) from LID:110 TID:0x00006dd200000103
Jul 21 15:24:48 541428 [24F17700] 0x01 → log_trap_info: Bad P_Key:0xcc2f on SL:0 from LID1:10 (GUID 0x946dae030070dd0a) QP1:0x1 to LID2:83 (GUID 0x946dae030093e282) QP2:0x1

[ipavis]

Hello,

Thanks for contacting us.
The error you are seeing in UFM indicates that there is some configuration issue your partitioning settings on the fabric.
Partition Key (P_Key): Enforces membership. Administered through the subnet manager by the partition manager.
P_Key configuration can be found under /opt/ufm/files/conf/opensm/partitions.conf

Incase you would like us to debug the issue. I would suggest to open a case on the Enterprise Support website so this could be fixed.

Thanks,
Ilan.