Grass Valley K2 (Summit 3G) 10Gv2 Storage Area Network Installation v.8.1 - Manual (Page 252)

If the following system connection or component fails to respond to network communication:
• The control connection between a K2 SAN-attached system and GigE switch “A”.
Then the following failover behavior occurs:
1. The control team on the K2 SAN-attached system fails over and communication begins on the
other control port.
2. The control communication finds a path through GigE “B” switch and across an ISL to GigE
switch “A” to reach the same control port on the same K2 Media Server.
3. Media (iSCSI) traffic keeps using the same path.
4. K2 Media Server “A” is still the media file system/metadata server. The media file system (SNFS)
and media database do not fail over.
5. The other K2 SAN-attached systems (not affected by the connection failure) keep using the same
paths for media and control, as in pre-failover behavior.
K2 client media (iSCSI) connection failover behavior
K2 RAID
K2 Media
Servers
K2 SAN-attached system
Ethernet
switches
A
A B
B
Fibre Channel
connections
Control
Media
Control
Media
Control
FTP
Media
Control
FTP
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.
If the following system connection or component fails to respond to network communication:
• Media (iSCSI) network “A” connection between a K2 SAN-attached system and the GigE switch
Then the following failover behavior occurs:
1. The K2 SAN-attached system 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/metadata server. The media file system (SNFS)
and media database do not fail over.
252 K2 SAN Installation and Service Manual 02 February 2012
Operating the K2 SAN