Loading...
Loading...
Unable to discover VxFlex OS gateway from VxFlex Manager: The resource discovery failed. The gateway is reachable from the appliance. A tcpdump shows no connection being made. Both the VxFlex Manager and OS Gateway can ping each other. asmManager.log: 2019-05-21 15:29:05,549 INFO [pool-10-thread-1,tid=438] (DiscoverDeviceCallable.java:64): Device IP xxx.xxx.xx.xxx unknown. Captured discovery response: null essage: The device with the IP address xxx.xxx.xx.xxx cannot be discovered because of an unknown device type., jobId=null 2019-05-21 15:29:05,558 INFO [JobMgrQuartzScheduler_Worker-15,tid=71] (DiscoverIpRangeJob.java:289): discovery job completed for the job name:Job-8a8000dc-b32a-4214-854e-39c0ecbcf36f 2019-05-21 15:29:05,549 ERROR [JobMgrQuartzScheduler_Worker-15,tid=71] (DiscoverIpRangeJob.java:212): Discovery by IP range failed for device: serviceTag: null, ipAddress: xxx.xxx.xx.xxx, message: The device with the IP address xxx.xxx.xx.xxx cannot be discovered because of an unknown device type., jobId=null
This was caused by port 443 being blocked in between the two devices. Once customer allowed, all worked as expected. Upon running the netstat command we discovered that VxFlex Manager is not listening on tcp port 443. vxfm ~]$ curl --insecure --verbose https://xxx.xxx.xx.xxx About to connect() to xxx.xxx.xx.xxx port 443 (#0) Trying xxx.xxx.xx.xxx... Connection timed out Failed connect to xxx.xxx.xx.xxx:443; Connection timed out Closing connection 0 curl: (7) Failed connect to xxx.xxx.xx.xxx:443; Connection timed out
VxFlex Manager uses port 443 to discover the VxFlex OS gateway. Ensure that network devices can communicate with each other over 443 when discovering devices in VxFlex Manager.
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.