HP 8/20q HP StorageWorks Simple SAN Connection Manager User Guide (5697-0460, - Page 134

Linux Server Name and IP address to the Simple SAN Connection Manager

Get HP 8/20q PDF manuals and user guides View all HP 8/20q manuals
Add to My Manuals
Save this manual to your list of manuals

Page 134 highlights

Why is the Linux Server on my local SAN not discovered? Symptoms: A new Linux server has been added to the SAN, and it has the appropriate Simple SAN Connection Manager Agent running, but the Linux server is not being discovered by the Windows 2003 Simple SAN Connection Manager server. Solution: If the local SAN is not running DNS, there is no Domain Name Server to perform the name server-to-IP resolution for the newly-attached server. You must manually add the Linux Server Name and IP address to the Simple SAN Connection Manager hosts file. NOTE: Most distributions of Linux have the firewall enabled by default. The user must add the portmap and qlremote service TCP/IP ports to allow traffic to pass through. The file is located at: C:\Windows\system32\drivers\etc\hosts Example of hosts file: # Copyright (c) 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. # Each entry should be kept on an individual line. The IP address # should be placed in the first column followed by the # corresponding host name. The IP address and the host name should # be separated by at least one space. # # Additionally, comments (such as these) may be inserted on # individual lines or following the machine name denoted by a '#' # symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 10.1.6.65 10.3.8.5 10.3.8.127 10.3.8.107 10.3.8.109 localhost apsun01 DL145-1 DL380G3-2 DL320-1 ml370-1 How do I prevent losing aliases when updating Simple SAN Connection Manager to a new version? Symptoms: I updated Simple SAN Connection Manager to a newer version and when I re-launched the program, all of my aliases were lost. How do I save them before updating to a newer version? Solution: Before removing, reinstalling, or updating the Simple SAN Connection Manager application, preserve your aliases by saving the file HP_SSCM.ALI. This file is located in the same directory as the Simple SAN Connection Manager executable. After the new version has been installed, copy the file back to the directory where the new executable is installed. This also applies when you install and launch Simple SAN Connection Manager on a new server and want to preserve the aliases created when running Simple SAN Connection Manager on an older server. 134 Troubleshooting

  • 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
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
134
Troubleshooting
Why is the Linux Server on my local SAN not discovered?
How do I prevent losing aliases when updating Simple SAN Connection Manager to a new version?
Symptoms:
A new Linux server has been added to the SAN, and it has the appropriate Simple
SAN Connection Manager Agent running, but the Linux server is not being discovered
by the Windows 2003 Simple SAN Connection Manager server.
Solution:
I
f the local SAN is not running DNS, there is no Domain Name Server to perform the
name server-to-IP resolution for the newly-attached server. You must manually add the
Linux Server Name and IP address to the Simple SAN Connection Manager
hosts
file.
NOTE:
Most distributions of Linux have the firewall enabled by default. The user must
add the portmap and qlremote service TCP/IP ports to allow traffic to pass through.
The file is located at:
C:\Windows\system32\drivers\etc\hosts
Example of
hosts
file:
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names.
# Each entry should be kept on an individual line. The IP address
# should be placed in the first column followed by the
# corresponding host name. The IP address and the host name should
# be separated by at least one space.
#
# Additionally, comments (such as these) may be inserted on
# individual lines or following the machine name denoted by a '#'
# symbol.
#
# For example:
#
#
102.54.94.97
rhino.acme.com
# source server
#
38.25.63.10
x.acme.com
# x client host
127.0.0.1
localhost
10.1.6.65
apsun01
10.3.8.5
DL145-1
10.3.8.127
DL380G3-2
10.3.8.107
DL320-1
10.3.8.109
ml370-1
Symptoms:
I updated Simple SAN Connection Manager to a newer version and when I
re-launched the program, all of my aliases were lost. How do I save them before
updating to a newer version?
Solution:
Before removing, reinstalling, or updating the Simple SAN Connection Manager
application, preserve your aliases by saving the file
HP_SSCM.ALI
. This file is located
in the same directory as the Simple SAN Connection Manager executable. After the
new version has been installed, copy the file back to the directory where the new
executable is installed.
This also applies when you install and launch Simple SAN Connection Manager on a
new server and want to preserve the aliases created when running Simple SAN
Connection Manager on an older server.