Loading...
Loading...
Error message from the switch logs 2024/07/16-10:50:28 (GMT), [SS-1015], 112894, CHASSIS, INFO, DS_6610B, supportSave started. 2024/07/16-10:50:29 (GMT), [SS-1001], 112895, CHASSIS, WARNING, DS_6610B, supportSave's upload operation to remote host has been aborted (Remote Host:Could not connect to remote host). 2024/07/16-10:54:00 (GMT), [SEC-1193], 112896, FID 128, INFO, dekher3sfc-Q-01, Security violation: Login failure attempt via HTTPS. IP Addr: 1xx.xxx.xxx.xxx. Error message from the SANnav server: mw-consolidated-1 - [ERROR] 2024-07-23 07:07:24.562 [defaultThreadPool (Thread-163)] com.brocade.dcm.switchsupportsave.util.SwitchSupportAsynchWork - 141.xx.xxx.xx :Not able to connect to the CAL connector : mw-consolidated-1 - [ERROR] 2024-07-23 07:07:24.566 [defaultThreadPool (Thread-163)] com.brocade.dcm.switchsupportsave.util.SwitchSupportAsynchWork - The exception occured while generating supportsave for chassis: DS_6610B[141.73.200.21] com.brocade.dcm.switchsupportsave.interfaces. SwitchSupportException: Unauthorized access to switch at com.brocade.dcm.switchsupportsave.util.SwitchSupportAsynchWork.establishCalConnection(SwitchSupportAsynchWork.java:603) at com.brocade.dcm.switchsupportsave.util.SwitchSupportAsynchWork.run(SwitchSupportAsynchWork.java:286) at com.brocade.dcm.framework.jobexecutor.impl.CallableJob.call(CallableJob.java:287) at com.brocade.dcm.framework.concurrent.contract.runnable.CallableEnclosure.call(CallableEnclosure.java:194) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) mw-consolidated-1 - [INFO ] 2024-07-23 07:07:24.567 [defaultThreadPool (Thread-163)] com.brocade.dcm.switchsupportsave.util.SwitchSupportAsynchWork - Sucessfully sent status msg to client with status class WebSocketMessage { status: Failed switchIp: 141.xx.xxx.xx } mw-consolidated-1 - [INFO ] 2024-07-23 07:07:24.605 [defaultThreadPool (Thread-163)] com.brocade.dcm.switchsupportsave.util.SwitchSupportSaveUtil - Sent an App event - ApplicationEventDetails [eventCategory=USER_ACTION_EVENT, description= Generating Supportsave for chassis DS_6610B (141.73.xxx.xx) failed. Unauthorized access to switch. , messageId=SSMP-SWSS-1005, severity=Major, eventOccurenceTime=1721732844574, module=TECH_SUPPORT, applicationEventSubType=USER_ACTION, sourceType=CORE_SWITCH, sourceGuid=c19f1a87-e865-4daa-b144-3f3b9c7fa1ee, userID=1, sourceAddress=null, sourceName=null, productAddress=null, productName=null, isNotification=true, notificationTitle=Generating switch Supportsave failed, isNotificationAlways=true, BulkActionEventDetails=null]
Try the following from the SANnav CLI. curl -k https://<switch IP address>/secinfo.html -u admin:<password> The primary means of SANnav to Switch communication is https. If SANnav cannot reach the switches using https, the switches are marked Not Reachable in the Fabric Discovery page. A proper response would show some html text from the switch as below: [root@sannav-portal-v222 ~]# curl -k https://10.xx.xx.xx.xx/secinfo.html -u admin:password <HTML> <HEAD> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <TITLE>SecureSAN Info</TITLE> </HEAD> <BODY> <PRE> --BEGIN SECINFO SECURITY = OFF DefaultPasswdBitmap = 0 primaryFCS = no switchType =181 resource = 1x.xx.xx.xx REALM = FC Switch Administration AUTHMETHOD = Custom_Basic hasUpfrontLogin=yes AUTHVERSION = 3 vfEnabled=true vfSupported=true --END SECINFO </PRE> </BODY> </HTML> A timeout or authentication failure means SANnav is not able to reach the switch.
Curl command output highlighted ' Connection timed out " as below indicating the firewall team had mistakenly replaced the IP for the switch with the SANnav IP.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.