Skip to main content
NetApp Knowledge Base

SANnav lost connection to switch after Fabric OS update

Views:
158
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

  • SANnav v2.3.0
  • Fabric OS (FOS) v9.2.1

Issue

  • SANnav loses connection to switch that was updated from FOS v9.2.0 to FOS v9.2.1
  • Attempts to rediscover the switch's fabric fail with Discovery Failed. Seed switch IP address is either not reachable or having problem in connecting via HTTPS:
AddFabric_DiscoveryFailed.png
  • Server to Switch Communication preference is "First HTTPS and then HTTP" as per <SANnav installation directory>/conf/server.properties:
# Server to Switch Communication preference
# 0 --> HTTP Only
# 1 --> HTTPS Only
# 2 --> First HTTPS and then HTTP
dcm.server.switch.comm.preference=2
  • Switch permits traffic over HTTP/HTTPS ports 80/443:
switch:admin> ipfilter --show
 
Name: default_ipv4, Type: ipv4, State: active
Rule  Source IP      Protocol   Dest Port    Action
[...]
3     any            tcp         80          permit
4     any            tcp        443          permit
[...]
  • Switch Web Tools is reachable from the same subnet as the SANnav Management Portal
  • SANnav can reach the switch over HTTP from the CLI:
# curl http://<switch IP address>/secinfo.html -u admin:<password>
<HTML>
<HEAD>
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
[...]

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.