loadbalancer ping and SFS2X
Posted: 17 May 2011, 13:47
hi
we have Fail-over Cluster configuration with one loadbalancer (www.radware.com) and two SFS2X , the loadbalancer ping SFS to see if it is alive.
this is the log of SFS :
-----------------------------------------------------------------
17 May 2011 15:00:03,183 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 5, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64510 } on Server port: 1955 <---> 64510
17 May 2011 15:00:03,188 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 5, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64510 }
17 May 2011 15:00:04,691 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 6, Type: DEFAULT, Logged: No, IP: 10.6.189.131:60213 } on Server port: 1955 <---> 60213
17 May 2011 15:00:04,691 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 6, Type: DEFAULT, Logged: No, IP: 10.6.189.131:60213 }
17 May 2011 15:00:09,183 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64476 } on Server port: 1955 <---> 64476
17 May 2011 15:00:09,184 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64476 }
--------------------------------------------------------------------
are the message logs correct ?
can the ping process disturb SFS2X activity ?
if something is wrong, what is the right way ?
thanks
we have Fail-over Cluster configuration with one loadbalancer (www.radware.com) and two SFS2X , the loadbalancer ping SFS to see if it is alive.
this is the log of SFS :
-----------------------------------------------------------------
17 May 2011 15:00:03,183 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 5, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64510 } on Server port: 1955 <---> 64510
17 May 2011 15:00:03,188 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 5, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64510 }
17 May 2011 15:00:04,691 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 6, Type: DEFAULT, Logged: No, IP: 10.6.189.131:60213 } on Server port: 1955 <---> 60213
17 May 2011 15:00:04,691 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 6, Type: DEFAULT, Logged: No, IP: 10.6.189.131:60213 }
17 May 2011 15:00:09,183 INFO [SocketReader] bitswarm.core.SocketAcceptor - Session created: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64476 } on Server port: 1955 <---> 64476
17 May 2011 15:00:09,184 INFO [SocketReader] bitswarm.sessions.DefaultSessionManager - Session removed: { Id: 7, Type: DEFAULT, Logged: No, IP: 10.6.189.130:64476 }
--------------------------------------------------------------------
are the message logs correct ?
can the ping process disturb SFS2X activity ?
if something is wrong, what is the right way ?
thanks