Grass Valley K2 Storage System Instruction Manual v.3.2 Sep.24 2007 - Manual (Page 599)

September 7, 2007 K2 Storage System Instruction Manual 599
Failover behaviors
K2 Media Client media (iSCSI) connection failover behavior
If the following system connection fails to respond to network communication:
• Media (iSCSI) network “A” connection between a K2 Media Client and the GigE
switch.
Then the following failover behavior occurs:
1. The K2 Media Client drops communication on its “A” media port and begins using
its “B” media port and the “B” media (iSCSI) network. The iSCSI adapter (TOE)
on the “B” K2 Media Server provides access to the Fibre Channel connected RAID
storage.
2. Control traffic keeps using the same path to K2 Media Server “A”.
3. K2 Media Server “A” is still the media file system/database server. The media file
system (SNFS) and media database (SQL) do not fail over.
4. The other K2 Media Clients (not affected by the component failure) keep using the
same paths for media and control, as in the previous diagram “Pre-failover
behavior” . This means the K2 Media Clients unaffected by the failover are using
the iSCSI adapter (TOE) on the “A” K2 Media Server to provide access to the Fibre
Channel connected RAID storage, while at the same time the affected K2 Media
Clients are using the iSCSI adapter (TOE) on the “B” K2 Media Server to provide
access to the Fibre Channel connected RAID storage. In this case both RAID
controller are simultaneously providing disk access.
K2 RAID
K2 Media
Servers
K2 Media
Client
Gigabit
Ethernet
switches
A
A B
B
Fibre Channel
connections
Control
Media
Control
Media
Control
FTP
Media
Media
POWER SERVICE K2 RAID STORAGE !
!
Control
FTP
Media
Media
ISLs
X
Connection
Failure
Control traffic goes
to server A, which is
still the media file
system/database
server.
iSCSI traffic uses
the iSCSI adapter
on server B.