HP StorageWorks 2/16V HP StorageWorks Fabric OS V3.1.3A Release Notes (AA-RUQY - Page 67

SEC-PIDCHGERR, PID Change failed: Switch is busy

Page 67 highlights

New Diagnostic and System Error Messages Severity Error SEC-PIDCHGERR, PID Change failed: Switch is busy Message Switch: , Error SEC-PIDCHGERR, 2, PID Change failed: Switch is busy. Probable Cause The switch security daemon is busy updating something else. The value can be defined or active, or both policy sets were failed by the daemon. A negative value means that a policy set was failed by the daemon. Recommended Action Wait a few minutes and then resend the transaction. Fabric-wide commands might take a few minutes to propagate throughout the fabric. Make sure to leave enough time so your commands do not overlap in the fabric. If the problem persists, reboot or power cycle the switch. Severity Error SEC-PIDCHGINFO Message Switch: , Info SEC-PIDCHGINFO, 4, PID Change: Success Probable Cause The PID format of the switch was changed either to or from extended-edge PID. If DCC policies exist, all area ID values either increase or decrease by 16. The values wrap around after a port value of 128. If a DCC policy contains an area of 127 before changing to displaced PID, then the new area is 15 because of the wraparound. Fabric OS 3.1.3a Release Notes 67

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73

New Diagnostic and System Error Messages
67
Fabric OS 3.1.3a Release Notes
Severity
Error
Message
Switch: <number>, Error SEC-PIDCHGERR, 2, PID Change failed:
Switch is busy. <reason>
Probable Cause
The switch security daemon is busy updating something else. The <reason> value
can be defined or active, or both policy sets were failed by the daemon. A negative
value means that a policy set was failed by the daemon.
Recommended Action
Wait a few minutes and then resend the transaction. Fabric-wide commands might
take a few minutes to propagate throughout the fabric. Make sure to leave enough
time so your commands do not overlap in the fabric.
If the problem persists, reboot or power cycle the switch.
Severity
Error
Message
Switch: <number>, Info SEC-PIDCHGINFO, 4, PID Change: Success
Probable Cause
The PID format of the switch was changed either to or from extended-edge PID. If
DCC policies exist, all area ID values either increase or decrease by 16. The
values wrap around after a port value of 128. If a DCC policy contains an area of
127 before changing to displaced PID, then the new area is 15 because of the
wraparound.
SEC-PIDCHGERR, PID Change failed: Switch is busy
SEC-PIDCHGINFO