Hi,

we are using a mixed SAN environment.
3 Netware servers and 2 windows servers are connected to the SAN.
We have a MSL6030 with 1 drive.

The Netware SAN ring is working fine. (NSERVER3 = Primary)
The Windows SAN ring is working fine. (TMS = Primary)

No problem?? Yes Problem !!
To make the two SAN rings know that there are more SAN rings I have to
make the Windows Primary server a distributed server from the Primary
Netware server.
This is done with the SAN configutation tool.
There is a EDF.ini file in all system directories on all netware servers
showing the right config. So far so good.

But when I look in the CAPEER.LOG file is says that there is no
communication with the windows server??

Needless to say that all servers can ping all servers.
Protocol used is IP only.

Any ideas? Is there someone working with this solution anyway?


Willem Jan
CNE 6


Have a look at the CAPEER.log ...

*****************************************

(12/11 14:42:17) serverName [TMS] running on platform [NT] found in config
file

(12/11 14:42:17) Attempt made to get server address in unknown protocol

(12/11 14:42:17) Failed to obtain IPX address for [TMS] from NetWare.

(12/11 14:42:17) Total number of server(s) found in config file = [4]

(12/11 14:42:17) Total number of server(s) found with same platform as
host (including host) = [3]

(12/11 14:42:17) Total number of server(s) found with different platform
as host = [1]

(12/11 14:42:17) Static behavior has been directed by the EDF for load
time semaphore location.

(12/11 14:42:17) The enterprise semaphore control is in fault tolerant
mode.

(12/11 14:42:17) Protocol "tcp" has been specified in the EDF

(12/11 14:42:17) CAPEER: Peer services have been established, beginning
network discovery

(12/11 14:42:17) Beginning initial enterprise state discovery.--**--**--**-
-

(12/11 14:42:17) Attempting to contact the peer on [NSERVER3]

(12/11 14:42:17) The peer on [NSERVER3] is now active.

(12/11 14:42:17) Attempting to contact the peer on [NSERVER2]

(12/11 14:42:20) (*Ping Failure*): RPC service unavailable or server is
down on [NSERVER2]

(12/11 14:42:20) RPC services are not available on [NSERVER2] or the
server is down.

(12/11 14:42:20) Attempting to contact the peer on [NSERVER1]

(12/11 14:42:23) (*Ping Failure*): RPC service unavailable or server is
down on [NSERVER1]

(12/11 14:42:23) RPC services are not available on [NSERVER1] or the
server is down.

(12/11 14:42:23) Attempting to contact the peer on [TMS]

(12/11 14:42:26) (*Ping Failure*): RPC service unavailable or server is
down on [TMS]

(12/11 14:42:26) RPC services are not available on [TMS] or the server is
down.

(12/11 14:42:26) Enterprise initial discovery is complete.--**--**--**--