06-26-2015 05:48 AM
a couple of days ago, an unexperienced person connected an unauthorized switch in another switch and it causes an error reported as "SW Security Violation - SCC Policy Violation, Peer WWN not in ACL list". Now, I am not able to put this port as enabled again. I select the port and the "enable" option, but after confirm the process, it remains in disable mode.
Does anybody know how to reset/remove this error and enable this port with no impact for this switch that have a plenty of ports in use?
Solved! Go to Solution.
06-26-2015 06:23 AM - edited 06-26-2015 06:23 AM
never had a chance to recover from this state, but usually, auto-disabled port needs to be manually disabled and enabled using either portdisable/portenable or portcfgpersistentdisable/portcfgpersistentenable
06-26-2015 06:51 AM
When I open the Web Tools, in the "Logical Switch" box, I have three options there: 128-SW.AB, 40-PPRC-SWAB and 11-SW.AB.Logical. Only when I chose 11-SW.AB.Logical, I can see the ports that I need to work. The enable/disable doesn't work there, then I am trying to use the TELNET option.
When I open the TELNET for the IP address, the TELNET reports that I am using the 128-SW.AB and there I do not have those ports where the error exist. As all three options above uses the same IP address, how to jump from the 128-SW.AB to 11-SW.AB.Logical and perform some commands?
06-26-2015 07:26 AM
The setcontext works fine, thanks, but unfortunately the problem with the port disable was not fixed.
Look those steps that I did
SW.AB:FID128:admin> setcontext 11
SW_AB.Logical:FID11:admin> portcfgpersistentenable 1/13
portCfgPersistent commands not allowed in fmsmode
SW_AB.Logical:FID11:admin> portenable 1/13
Warning! You are about to change FICON Director parameters. Do you want to continue? (yes, y, no, n): [no] y
SW_AB.Logical:FID11:admin> portshow 1/13
portDisableReason: SW Security Violation - SCC Policy Violation, Peer WWN not in ACL list
portFlags: 0x4021 PRESENT U_PORT DISABLED LED
portState: 2 Offline
portPhys: 4 No_Light portScn: 2 Offline
port generation number: 404
state transition count: 3
portWwn of device(s) connected:
Credit Recovery: Inactive
LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 0 Fbsy: 0
Lli: 3 Loss_of_sig: 0
Proc_rqrd: 0 Protocol_err: 0
Timed_out: 0 Invalid_word: 0
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 0
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 0
Thanks Alexey by your attention and help. Have you any other suggestion to fix this issue?
06-26-2015 07:55 AM
I've just noticed this is FICON, which is not my area at all...
but anyway, please try doing portdisable first and only then proceed to portenable (which was my initial suggestion)