Page 1
K2 SAN
10Gv2 Storage Area Network
Installation and Service Manual
Software Version 9.2
071-8779- 04
2014 01 27
Page 2
Page 3
K2 SAN
10Gv2 Storage Area Network
Installation and Service Manual
Software Version 9.2
071-8779- 04
2014 01 27
Page 4
Page 5
Contents
Safety Summaries......................................................................................................................................11
Preface.......................................................................................................................................................23
About this document...............................................................................................................................23
About documentation for previous K2 SANs...........................................................................................23
For more information...............................................................................................................................23
For the installer of a standalone K2 product with internal storage......................................................23
For the installer of a K2 product with direct connect storage..............................................................24
For the installer of K2 Summit systems with K2 SAN shared storage.................................................24
K2 Release Notes...............................................................................................................................25
Quick Start Guides..............................................................................................................................25
K2 Storage Cabling Guide..................................................................................................................25
K2 Documentation Set........................................................................................................................25
On-line Help Systems.........................................................................................................................26
K2 FCP Connect documentation.........................................................................................................26
Grass Valley Website...........................................................................................................................26
Dell Server Documentation.................................................................................................................27
Product description.....................................................................................................................................29
K2 SAN overview description.................................................................................................................29
K2 SAN key features...............................................................................................................................30
What's new in the K2 10Gv2 SAN..........................................................................................................30
K2 Storage types and terms...................................................................................................................30
K2 SAN descriptions...............................................................................................................................31
Basic K2 SAN description...................................................................................................................32
Redundant K2 SAN description..........................................................................................................33
Basic Nearline K2 SAN description.....................................................................................................34
Redundant Nearline K2 SAN description............................................................................................35
Preparing for installation.............................................................................................................................37
K2 SAN installation checklists................................................................................................................37
Pre-installation planning checklist.......................................................................................................37
Infrastructure checklist........................................................................................................................37
Network setup and implementation checklist......................................................................................37
Software update checklist...................................................................................................................38
SAN configuration checklist.................................................................................................................39
Understanding system concepts.............................................................................................................39
Control network description.................................................................................................................39
Streaming/FTP network description....................................................................................................40
Media (iSCSI) network description......................................................................................................41
Networking tips....................................................................................................................................41
Network considerations and constraints.............................................................................................41
About host files....................................................................................................................................42
Host Table tips.....................................................................................................................................42
Dell R620 Rack specifications................................................................................................................43
K2 RAID Rack specifications..................................................................................................................44
Cabling K2 SAN devices............................................................................................................................45
Rack-mount devices...............................................................................................................................45
HP ProCurve Switch Rack specifications............................................................................................45
Dell R620 Rack specifications.............................................................................................................46
K2 Summit 3G Rack specifications.....................................................................................................47
K2 RAID Rack specifications..............................................................................................................47
FT Server Rack specifications............................................................................................................48
2014 01 27 K2 SAN Installation and Service Manual 5
Page 6
Contents
Securing a server to a rack.................................................................................................................48
Basic K2 SAN - Online or Production.....................................................................................................49
Redundant K2 SAN - Online or Production............................................................................................50
Basic Nearline K2 SAN...........................................................................................................................51
Redundant Nearline K2 SAN..................................................................................................................52
Cable K2 Summit system.......................................................................................................................52
K2-XDP basic......................................................................................................................................52
K2-XDP redundant..............................................................................................................................53
Cable Ethernet switch.............................................................................................................................53
K2-SWE basic online/production.........................................................................................................53
K2-SWE redundant online/production.................................................................................................54
K2-SWE basic nearline.......................................................................................................................55
K2-SWE redundant nearline...............................................................................................................56
Cable K2 Media Server...........................................................................................................................56
K2-SVR basic Dell R620.....................................................................................................................56
K2-SVR redundant Dell R620.............................................................................................................57
Cable NH10GE K2 Media Server...........................................................................................................58
K2-SVR-NH10GE online/production Dell R620..................................................................................58
K2-SVR-NH10GE basic nearline Dell R620........................................................................................58
K2-SVR-NH10GE redundant nearline Dell R620................................................................................58
Cable K2 RAID.......................................................................................................................................59
K2 RAID basic online/production........................................................................................................59
K2 RAID redundant online/production.................................................................................................60
K2 RAID basic nearline.......................................................................................................................61
K2 RAID redundant nearline...............................................................................................................61
Setting up the K2 SAN infrastructure.........................................................................................................63
Setting up the Ethernet switch................................................................................................................63
K2 SAN Ethernet switch requirements................................................................................................63
Default Ethernet switch design............................................................................................................63
Design considerations for Ethernet switches......................................................................................64
Configuring a switch through the K2Config application ......................................................................64
Configuring QOS on the GigE switch..................................................................................................65
Upgrading firmware on HP switch.......................................................................................................66
Setting up the control point PC...............................................................................................................67
Install SiteConfig on control point PC..................................................................................................67
Planning and implementing a K2 SAN with SiteConfig..............................................................................71
About developing a system description..................................................................................................71
Importing a system description...............................................................................................................71
About device and host names................................................................................................................72
Modifying a device name........................................................................................................................72
Modifying the control network.................................................................................................................72
Modifying the FTP/streaming network....................................................................................................74
Modifying a media (iSCSI) network........................................................................................................76
About IP configuration of network interfaces on devices........................................................................78
Placeholder device IP configuration....................................................................................................79
Discovered device IP configuration.....................................................................................................79
Modifying K2 client unassigned (unmanaged) interface.........................................................................80
Modifying K2 Media Server unassigned (unmanaged) interface............................................................82
About SiteConfig support on K2 devices................................................................................................85
Discovering devices with SiteConfig.......................................................................................................85
Assigning discovered devices.................................................................................................................86
Modifying K2 client managed network interfaces...................................................................................87
Modifying K2 Media Server managed network interfaces......................................................................91
Making the host name the same as the device name.............................................................................96
Pinging devices from the PC that hosts SiteConfig................................................................................97
About hosts files and SiteConfig.............................................................................................................97
6 K2 SAN Installation and Service Manual 2014 01 27
Page 7
Contents
Generating host tables using SiteConfig.................................................................................................98
Managing K2 Software.............................................................................................................................101
Configuring K2 software deployment....................................................................................................101
Configuring deployment groups........................................................................................................101
Adding a software package to a deployment group..........................................................................102
Checking all currently installed software on devices.........................................................................103
About deploying software for the K2 SAN.........................................................................................103
Backup and Recovery Strategies..........................................................................................................103
About the recovery disk image process............................................................................................103
Recommended recovery process.....................................................................................................104
Creating a recovery disk image for storing on E: Dell R610..............................................................105
Restoring from a system-specific recovery disk image on E: Dell R610...........................................106
Restoring from the generic recovery disk image on E: Dell R610.....................................................108
Creating a recovery disk image for storing on E: Dell R620..............................................................110
Restoring from the system-specific recovery disk image on E: Dell R620........................................111
Restoring from a generic recovery disk image Dell R620.................................................................112
Installing the Discovery Agent on a K2 Media Server.......................................................................114
Setting up Windows...........................................................................................................................115
Activating the Windows operating system.........................................................................................116
Embedded Security modes and policies...............................................................................................116
Manage Embedded Security Update mode......................................................................................118
Configuring and licensing the K2 SAN.....................................................................................................119
About K2 SAN licensing........................................................................................................................119
About QOS on the K2 SAN...................................................................................................................119
Importing a SiteConfig system description into K2Config.....................................................................120
Configuring the basic K2 SAN - Online and Production.......................................................................120
Prerequisites for initial configuration - Basic K2 SAN........................................................................121
Defining a new K2 SAN.....................................................................................................................122
Configuring the server - Part 1..........................................................................................................125
Configuring RAID..............................................................................................................................129
Configuring the server - Part 2..........................................................................................................135
Configuring optional NH servers.......................................................................................................140
Configuring the redundant K2 SAN - Online and Production................................................................144
Prerequisites for initial configuration - Redundant K2 SAN...............................................................145
Defining a new K2 SAN.....................................................................................................................146
Configuring server A - Part 1.............................................................................................................149
Configuring RAID..............................................................................................................................153
Configuring server A - Part 2.............................................................................................................161
Configuring server B.........................................................................................................................166
Configuring optional NH servers.......................................................................................................173
Configuring the basic nearline K2 SAN................................................................................................179
Prerequisites for initial configuration - Basic nearline K2 SAN..........................................................179
Defining a new K2 SAN.....................................................................................................................180
Configuring NH server - Part 1..........................................................................................................184
Configuring RAID..............................................................................................................................188
Configuring NH server - Part 2..........................................................................................................195
Configuring the redundant nearline K2 SAN........................................................................................197
Prerequisites for initial configuration - Nearline K2 SAN...................................................................197
Defining a new K2 SAN.....................................................................................................................198
Configuring NH server A - Part 1......................................................................................................202
Configuring RAID..............................................................................................................................206
Configuring NH server A - Part 2......................................................................................................213
Configuring NH server B...................................................................................................................215
Configuring clients on the K2 SAN...........................................................................................................221
About iSCSI bandwidth.........................................................................................................................221
Determining K2 client bandwidth requirements....................................................................................221
2014 01 27 K2 SAN Installation and Service Manual 7
Page 8
Contents
K2 SAN prerequisites for adding clients...............................................................................................222
Verify license on K2 Media Server....................................................................................................222
Preparing K2 clients..........................................................................................................................222
Installing Multi-Path I/O Software......................................................................................................223
Configuring a K2 client for the K2 Storage System..............................................................................224
Configure page 1 - K2 client..............................................................................................................225
Configure Software Configuration page - K2 client...........................................................................226
Configure Network Configuration page - K2 client............................................................................227
Configure Database Client Configuration page - K2 client................................................................228
Configure iSCSI Initiator Configuration page - K2 client...................................................................229
Configure File System Client Configuration page.............................................................................231
Adding a generic client device..............................................................................................................231
Assigning a SAN client to different FTP server.....................................................................................232
Powering on/off a SAN client................................................................................................................232
Taking a SAN client offline....................................................................................................................232
Operating the K2 SAN..............................................................................................................................235
Powering off the K2 SAN......................................................................................................................235
Power off K2 Media Servers..............................................................................................................235
Powering off K2 G10v2 RAID............................................................................................................236
Power off remaining K2 SAN devices................................................................................................236
Powering on the K2 SAN......................................................................................................................236
Basic K2 SAN power on procedure...................................................................................................237
Redundant K2 SAN power on procedure..........................................................................................238
Nearline K2 SAN power on procedure..............................................................................................240
Powering on K2 G10v2 RAID............................................................................................................241
Powering on the HP ProCurve switch...............................................................................................241
Powering on the control point PC......................................................................................................241
Failover behaviors.................................................................................................................................242
Pre-failover behavior.........................................................................................................................242
Control Team failover behavior..........................................................................................................243
K2 client media (iSCSI) connection failover behavior........................................................................244
K2 Media Server failover behavior....................................................................................................246
K2 Media Server failover with Control team failover behavior...........................................................247
Description of K2 SAN Devices................................................................................................................249
Device terminology...............................................................................................................................249
Control point PC description.................................................................................................................249
K2 Ethernet switch description.............................................................................................................250
K2 Ethernet switch specifications......................................................................................................250
K2 Media Server description.................................................................................................................251
K2 Media Server specifications.........................................................................................................251
NH K2 Media Server.............................................................................................................................252
NH K2 Media Server specifications...................................................................................................252
K2 RAID storage description................................................................................................................253
Overview of K2 Storage Tools..................................................................................................................255
About SiteConfig...................................................................................................................................255
Opening SiteConfig...........................................................................................................................255
SiteConfig main window....................................................................................................................255
K2Config...............................................................................................................................................256
Opening the K2Config application.....................................................................................................257
Server Control Panel.............................................................................................................................258
Storage Utility for K2 SAN.....................................................................................................................259
About RANKs and LUNs in Storage Utility........................................................................................260
Windows Remote Desktop Connection................................................................................................261
Accessing Remote Desktop Connection...........................................................................................261
Grass Valley Recommended Deployment and Monitoring Solutions....................................................261
8 K2 SAN Installation and Service Manual 2014 01 27
Page 9
Contents
Administering and maintaining the K2 SAN.............................................................................................263
Passwords and security on Grass Valley systems................................................................................263
About application security on the K2 SAN........................................................................................264
About credentials in SiteConfig.........................................................................................................264
Modifying K2 SAN settings...................................................................................................................265
Accessing K2 SAN features..............................................................................................................265
About SiteConfig and K2Config settings...........................................................................................265
About Control Panel, SiteConfig, and K2Config settings..................................................................267
Synchronizing K2Config information to GV STRATUS Control Panel...............................................267
Renaming a K2 SAN.........................................................................................................................269
Adding devices to a K2 SAN.............................................................................................................269
Removing a K2 SAN.........................................................................................................................270
Accessing a K2 SAN from multiple PCs............................................................................................271
Taking a K2 SAN offline....................................................................................................................271
Bringing a K2 SAN online..................................................................................................................272
Viewing iSCSI assignments..............................................................................................................272
Using reference files..........................................................................................................................272
Managing redundancy on a K2 SAN....................................................................................................273
Identifying current primary/backup K2 Media Servers......................................................................274
Triggering an intentional failover........................................................................................................275
Recovering from a failover.................................................................................................................276
Working with K2 Media Servers............................................................................................................277
Accessing K2 Media Server features in the K2Config application ...................................................277
Taking a K2 Media Server out of service...........................................................................................277
Using the Stop button in Server Control Panel..................................................................................278
Placing a K2 Media Server in service ..............................................................................................279
Shutting down or restarting a K2 Media Server................................................................................279
Identifying K2 Media Server software versions.................................................................................279
Modifying K2 Media Server network settings....................................................................................279
Configuring Server 2008 for domain.................................................................................................280
Restoring network configuration........................................................................................................282
Removing a K2 Media Server...........................................................................................................285
Replacing a K2 Media Server...........................................................................................................285
Replacing an iSCSI interface adapter (TOE card)............................................................................287
Installing the Fibre Channel card driver............................................................................................288
Recovering from a failed K2 Media Server system battery...............................................................288
Checking K2 Media Server services.................................................................................................289
Licensing a K2 Media Server............................................................................................................291
Working with K2 clients.........................................................................................................................293
Accessing K2 client features in the K2Config application ................................................................293
Shutting down or restarting a K2 client.............................................................................................294
Taking a K2 client offline...................................................................................................................294
Bringing a K2 client online ................................................................................................................294
Adding a K2 client.............................................................................................................................294
Removing a K2 client........................................................................................................................295
Identifying K2 client software versions..............................................................................................295
Modifying K2 client control network settings.....................................................................................295
Modifying K2 client media (iSCSI) network settings..........................................................................296
Using Storage Utility.............................................................................................................................296
Accessing Storage Utility..................................................................................................................297
Overview of Storage Utility................................................................................................................297
Working on the media file system and database..................................................................................298
Checking the media file system........................................................................................................298
Cleaning unreferenced files and movies...........................................................................................299
Making a new media file system.......................................................................................................300
Expanding the media file system by capacity...................................................................................302
Expanding the media file system by bandwidth................................................................................303
2014 01 27 K2 SAN Installation and Service Manual 9
Page 10
Contents
Recovering the media database.......................................................................................................308
Working with RAID storage...................................................................................................................309
Checking RAID storage subsystem status........................................................................................309
Checking controller microcode..........................................................................................................310
Identifying disks.................................................................................................................................310
Get K2 10Gv2 RAID controller logs..................................................................................................312
Unbind RANK....................................................................................................................................313
About full/background bind................................................................................................................314
Bind RANK........................................................................................................................................314
Binding Hot Spare drives..................................................................................................................316
Loading K2 10Gv2 RAID controller and expansion chassis microcode............................................316
Downloading disk drive firmware......................................................................................................318
Replacing a disk module...................................................................................................................319
Replacing a K2 10Gv2 RAID controller.............................................................................................320
Configuring RAID chassis network and SNMP settings....................................................................321
Custom K2 SAN systems.........................................................................................................................325
About custom K2 SAN systems............................................................................................................325
About custom K2 SAN information.......................................................................................................325
System diagrams..................................................................................................................................325
iSCSI extended (redundant FSMs)...................................................................................................326
Fibre Channel connected clients (redundant FSMs).........................................................................327
Explanations and procedures...............................................................................................................328
General guidelines............................................................................................................................328
K2 RAID Fibre Channel port redundant configuration......................................................................328
Installing SANsurfer Switch Manager software.................................................................................329
Uninstalling SANsurfer Switch Manager software.............................................................................330
Fibre Channel switch domains..........................................................................................................330
Fibre Channel switch zoning.............................................................................................................330
Fibre Channel fabric cabling..............................................................................................................335
10 K2 SAN Installation and Service Manual 2014 01 27
Page 11
Safety Summaries
Safety Summary
Read andfollow the important safety information below, noting especially those instructions related
to risk of re, electric shock or injury to persons. Additional specic warnings not listed here may
be found throughout the manual.
WARNING: Any instructions in this manual that require opening the equipment cover
or enclosure are for use by qualied service personnel only. To reduce the risk of electric
shock, do not perform any servicing other than that contained in the operating instructions
unless you are qualied to do so.
Safety terms and symbols
Terms in this manual
Safety-related statements may appear in this manual in the following form:
WARNING: Warning statements identify conditions or practices that may result in
personal injury or loss of life.
CAUTION: Caution statements identify conditions or practices that may result in damage
to equipment or other property, or which may cause equipment crucial to your business
environment to become temporarily non-operational.
Terms on the product
These terms may appear on the product:
DANGER — A personal injury hazard is immediately accessible as you read the marking.
WARNING — A personal injury hazard exists but is not immediately accessible as you read the
marking.
CAUTION — A hazard to property, product, and other equipment is present.
Symbols on the product
The following symbols may appear on the product:
Indicates that dangerous high voltage is present within the equipment enclosure that may
be of sufcient magnitude to constitute a risk of electric shock.
Indicates that user, operator or service technician should refer to product manual(s) for
important operating, maintenance, or service instructions.
This is a prompt to note fuse rating when replacing fuse(s). The fuse referenced in the text
must be replaced with one having the ratings indicated.
2014 01 27 K2 SAN Installation and Service Manual 11
Page 12
Safety Summaries
Warnings
Identies a protective grounding terminal which must be connected to earth ground prior
to making any other equipment connections.
Identies anexternal protective groundingterminal which may be connected to earth ground
as a supplement to an internal grounding terminal.
Indicates thatstatic sensitive componentsare present whichmay be damagedby electrostatic
discharge. Use anti-static procedures, equipment and surfaces during servicing.
The following warning statements identify conditions or practices that can result in personal injury
or loss of life.
Dangerous voltage or current may be present — Disconnect power and remove battery (if applicable)
before removing protective panels, soldering, or replacing components.
Do not service alone — Do not internally service this product unless another person capable of
rendering rst aid and resuscitation is present.
Remove jewelry — Prior to servicing, remove jewelry such as rings, watches, and other metallic
objects.
Avoid exposed circuitry — Do not touch exposed connections, components or circuitry when power
is present.
Use proper power cord — Use only the power cord supplied or specied for this product.
Ground product — Connect the grounding conductor of the power cord to earth ground.
Operate only with covers and enclosure panels in place — Do not operate this product when covers
or enclosure panels are removed.
Use correct fuse — Use only the fuse type and rating specied for this product.
Use only in dry environment — Do not operate in wet or damp conditions.
Use only in non-explosive environment — Do not operate this product in an explosive atmosphere.
High leakage current may be present — Earth connection of product is essential before connecting
power.
Dual power supplies may be present — Be certain to plug each power supply cord into a separate
branch circuit employing a separate service ground. Disconnect both power supply cords prior to
servicing.
Double pole neutral fusing — Disconnect mains power prior to servicing.
Use proper lift points — Do not use door latches to lift or move equipment.
Avoid mechanical hazards — Allow all rotating devices to come to a stop before servicing.
Cautions
The following caution statements identify conditions or practices that can result in damage to
equipment or other property
Use correct power source — Do not operate this product from a power source that applies more than
the voltage specied for the product.
12 K2 SAN Installation and Service Manual 2014 01 27
Page 13
Safety Summaries
Use correct voltage setting — If this product lacks auto-ranging power supplies, before applying
power ensure that the each power supply is set to match the power source.
Provide proper ventilation — To prevent product overheating, provide equipment ventilation in
accordance with installation instructions.
Use anti-static procedures — Static sensitive components are present which may be damaged by
electrostatic discharge. Use anti-static procedures, equipment and surfaces during servicing.
Do not operate with suspected equipment failure — If you suspect product damage or equipment
failure, have the equipment inspected by qualied service personnel.
Ensure mains disconnect — If mains switch is not provided, the power cord(s) of this equipment
provide the means of disconnection. The socket outlet must be installed near the equipment and
must be easily accessible. Verify that all mains power is disconnected before installing or removing
power supplies and/or options.
Route cable properly — Route power cords and other cables so that they ar not likely to be damaged.
Properly support heavy cable bundles to avoid connector damage.
Use correct power supply cords — Power cords for this equipment, if provided, meet all North
American electrical codes. Operation of this equipment at voltages exceeding 130 VAC requires
power supplycords which complywith NEMA congurations. International power cords,if provided,
have the approval of the country of use.
Use correct replacement battery — This product may contain batteries. To reduce the risk of explosion,
check polarity and replace only with the same or equivalent type recommended by manufacturer.
Dispose of used batteries according to the manufacturer’s instructions.
Troubleshoot only to board level — Circuit boards in this product are densely populated with surface
mount technology (SMT) components and application specic integrated circuits (ASICS). As a
result, circuit board repair at the component level is very difcult in the eld, if not impossible. For
warranty compliance, do not troubleshoot systems beyond the board level.
Sicherheit – Überblick
Lesen und befolgen Sie die wichtigen Sicherheitsinformationen dieses Abschnitts. Beachten Sie
insbesondere die Anweisungen bezüglich
Brand-, Stromschlag- und Verletzungsgefahren. Weitere spezische, hier nicht aufgeführte
Warnungen nden Sie im gesamten Handbuch.
WARNUNG: Alle Anweisungen in diesem Handbuch, die das Abnehmen der
Geräteabdeckung oder des Gerätegehäuses erfordern, dürfen nur von qualiziertem
Servicepersonal ausgeführt werden. Um die Stromschlaggefahr zu verringern, führen
Sie keine Wartungsarbeiten außer den in den Bedienungsanleitungen genannten Arbeiten
aus, es sei denn, Sie besitzen die entsprechende Qualikationen für diese Arbeiten.
Sicherheit – Begriffe und Symbole
In diesem Handbuch verwendete Begriffe
Sicherheitsrelevante Hinweise können in diesem Handbuch in der folgenden Form auftauchen:
2014 01 27 K2 SAN Installation and Service Manual 13
Page 14
Safety Summaries
WARNUNG: Warnungen weisen auf Situationen oder Vorgehensweisen hin, die
Verletzungs- oder Lebensgefahr bergen.
VORSICHT: Vorsichtshinweise weisen auf Situationen oder Vorgehensweisen hin, die
zu Schäden an Ausrüstungskomponenten oder anderen Gegenständen oder zum zeitweisen
Ausfall wichtiger Komponenten in der Arbeitsumgebung führen können.
Hinweise am Produkt
Die folgenden Hinweise können sich am Produkt benden:
GEFAHR – Wenn Sie diesen Begriff lesen, besteht ein unmittelbares Verletzungsrisiko.
WARNUNG – Wenn Sie diesen Begriff lesen, besteht ein mittelbares Verletzungsrisiko.
VORSICHT – Es besteht ein Risiko für Objekte in der Umgebung, den Mixer selbst oder andere
Ausrüstungskomponenten.
Symbole am Produkt
Die folgenden Symbole können sich am Produkt benden:
Warnungen
Die folgenden Warnungen weisen auf Bedingungen oder Vorgehensweisen hin, die Verletzungsoder Lebensgefahr bergen:
Gefährliche Spannungen oder Ströme – Schalten Sie den Strom ab, und entfernen Sie ggf. die Batterie,
bevor sie Schutzabdeckungen abnehmen, löten oder Komponenten austauschen.
Weist auf eine gefährliche Hochspannung im Gerätegehäuse hin, die stark genug sein kann,
um eine Stromschlaggefahr darzustellen.
Weist darauf hin, dass der Benutzer, Bediener oder Servicetechniker wichtige Bedienungs-,
Wartungs- oder Serviceanweisungen in den Produkthandbüchern lesen sollte.
Dies ist eine Aufforderung, beim Wechsel von Sicherungen auf deren Nennwert zu achten.
Die im Text angegebene Sicherung muss durch eine Sicherung ersetzt werden, die die
angegebenen Nennwerte besitzt.
Weist auf eine Schutzerdungsklemme hin, die mit dem Erdungskontakt verbunden werden
muss, bevor weitere Ausrüstungskomponenten angeschlossen werden.
Weist auf eine externe Schutzerdungsklemme hin, die als Ergänzung zu einem internen
Erdungskontakt an die Erde angeschlossen werden kann.
Weist darauf hin, dass es statisch empndliche Komponenten gibt, die durch eine
elektrostatische Entladung beschädigt werden können. Verwenden Sie antistatische
Prozeduren, Ausrüstung und Oberächen während der Wartung.
Servicearbeiten nicht alleine ausführen – Führen Sie interne Servicearbeiten nur aus, wenn eine
weitere Person anwesend ist, die erste Hilfe leistenund Wiederbelebungsmaßnahmen einleiten kann.
Schmuck abnehmen – Legen Sie vor Servicearbeiten Schmuck wie Ringe, Uhren und andere
metallische Objekte ab.
14 K2 SAN Installation and Service Manual 2014 01 27
Page 15
Safety Summaries
Keine offen liegenden Leiter berühren – Berühren Sie bei eingeschalteter Stromzufuhr keine offen
liegenden Leitungen, Komponenten oder Schaltungen.
Richtiges Netzkabel verwenden – Verwenden Sie nur das mitgelieferteNetzkabel oder ein Netzkabel,
das den Spezikationen für dieses Produkt entspricht.
Gerät erden – Schließen Sie den Erdleiter des Netzkabels an den Erdungskontakt an.
Gerät nur mit angebrachten Abdeckungen und Gehäuseseiten betreiben – Schalten Sie dieses Gerät
nicht ein, wenn die Abdeckungen oder Gehäuseseiten entfernt wurden.
Richtige Sicherung verwenden – Verwenden Sie nur Sicherungen, deren Typ und Nennwert den
Spezikationen für dieses Produkt entsprechen.
Gerät nur in trockener Umgebung verwenden – Betreiben Sie das Gerät nicht in nassen oder feuchten
Umgebungen.
Gerät nur verwenden, wenn keine Explosionsgefahr besteht – Verwenden Sie dieses Produkt nur in
Umgebungen, in denen keinerlei Explosionsgefahr besteht.
Hohe Kriechströme – Das Gerät muss vor dem Einschalten unbedingt geerdet werden.
Doppelte Spannungsversorgung kann vorhanden sein – Schließen Sie die beiden Anschlußkabel an
getrennte Stromkreise an. Vor Servicearbeiten sind beide Anschlußkabel vom Netz zu trennen.
Vorsicht
Zweipolige, neutrale Sicherung – Schalten Sie den Netzstrom ab, bevor Sie mit den Servicearbeiten
beginnen.
Fassen Sie das Gerät beim Transport richtig an – Halten Sie das Gerät beim Transport nicht an Türen
oder anderen beweglichen Teilen fest.
Gefahr durch mechanische Teile – Warten Sie, bis der Lüfter vollständig zum Halt gekommen ist,
bevor Sie mit den Servicearbeiten beginnen.
Die folgendenVorsichtshinweise weisen auf Bedingungen oder Vorgehensweisen hin, die zu Schäden
an Ausrüstungskomponenten oder anderen Gegenständen führen können:
Gerät nicht öffnen – Durch das unbefugte Öffnen wird die Garantie ungültig.
Richtige Spannungsquelle verwenden – Betreiben Sie das Gerät nicht an einer Spannungsquelle, die
eine höhere Spannung liefert als in den Spezikationen für dieses Produkt angegeben.
Gerät ausreichend belüften – Um eine Überhitzung des Geräts zu vermeiden, müssen die
Ausrüstungskomponenten entsprechend den Installationsanweisungen belüftet werden. Legen Sie
kein Papier unter das Gerät. Es könnte die Belüftung behindern. Platzieren Sie das Gerät auf einer
ebenen Oberäche.
Antistatische Vorkehrungen treffen – Es gibt statisch empndliche Komponenten, die durch eine
elektrostatische Entladung beschädigt werden können. Verwenden Sie antistatische Prozeduren,
Ausrüstung und Oberächen während der Wartung.
CF-Karte nicht mit einem PC verwenden – Die CF-Karte ist speziell formatiert. Die auf der CF-Karte
gespeicherte Software könnte gelöscht werden.
Gerät nicht bei eventuellem Ausrüstungsfehler betreiben – Wenn Sie einen Produktschaden oder
Ausrüstungsfehler vermuten, lassen Sie die Komponente von einem qualizierten Servicetechniker
untersuchen.
2014 01 27 K2 SAN Installation and Service Manual 15
Page 16
Safety Summaries
Consignes desécurité
Kabel richtig verlegen – Verlegen Sie Netzkabel und andere Kabel so, dass Sie nicht beschädigt
werden. StützenSie schwere Kabelbündel ordnungsgemäß ab, damit die Anschlüsse nicht beschädigt
werden.
Richtige Netzkabel verwenden – Wenn Netzkabel mitgeliefert wurden, erfüllen diese alle nationalen
elektrischen Normen.Der Betrieb dieses Geräts mit Spannungen über 130 V AC erfordert Netzkabel,
die NEMA-Kongurationen entsprechen. Wenn internationale Netzkabel mitgeliefert wurden, sind
diese für das Verwendungsland zugelassen.
Richtige Ersatzbatterie verwenden – Dieses Gerät enthält eine Batterie. Um die Explosionsgefahr zu
verringern, prüfen Sie die Polarität und tauschen die Batterie nur gegeneine Batterie desselben Typs
oder eines gleichwertigen, vom Herstellerempfohlenen Typs aus. Entsorgen Sie gebrauchte Batterien
entsprechend den Anweisungen des Batterieherstellers.
Das Gerät enthält keine Teile, die vom Benutzer gewartet werden können. Wenden Sie sich bei
Problemen bitte an den nächsten Händler.
Il est recommandé de lire, de bien comprendre et surtout de respecter les informations relatives à la
sécurité qui sont exposées ci-après, notamment les consignes destinées à prévenir les risques
d’incendie, les décharges électriques et les blessures aux personnes. Les avertissements
complémentaires, qui ne sont pas nécessairement repris ci-dessous, mais présents dans toutes les
sections du manuel, sont également à prendre en considération.
AVERTISSEMENT: Toutes les instructions présentes dans ce manuel qui concernent
l’ouverture des capots ou des logements de cet équipement sont destinées exclusivement
à des membres qualiés du personnel de maintenance. An de diminuer les risques de
décharges électriques, ne procédez à aucune intervention d’entretien autre que celles
contenues dans le manuel de l’utilisateur, à moins que vous ne soyez habilité pour le
faire.
Consignes et symboles de sécurité
Termes utilisés dans ce manuel
Les consignes de sécurité présentées dans ce manuel peuvent apparaître sous les formes suivantes
:
AVERTISSEMENT: Les avertissements signalent des conditions ou des pratiques
susceptibles d’occasionner des blessures graves, voire même fatales.
MISE EN GARDE: Les mises en garde signalent des conditions ou des pratiques
susceptibles d’occasionner un endommagement à l’équipement ou aux installations, ou
de rendre l’équipement temporairement non opérationnel, ce qui peut porter préjudice
à vos activités.
Signalétique apposée sur le produit
La signalétique suivante peut être apposée sur le produit :
DANGER — risque de danger imminent pour l’utilisateur.
16 K2 SAN Installation and Service Manual 2014 01 27
Page 17
Safety Summaries
AVERTISSEMENT — Risque de danger non imminent pour l’utilisateur.
MISE EN GARDE — Risque d’endommagement duproduit, des installations ou des autreséquipements.
Symboles apposés sur le produit
Les symboles suivants peut être apposés sur le produit :
Signale la présence d’une tension élevée et dangereuse dans le boîtier de l’équipement ;
cette tension peut être sufsante pour constituer un risque de décharge électrique.
Signale que l’utilisateur, l’opérateur ou le technicien de maintenance doit faire référence
au(x) manuel(s) pour prendre connaissance des instructions d’utilisation, de maintenance
ou d’entretien.
Il s’agit d’une invite à prendre note du calibre du fusible lors du remplacement de ce dernier.
Le fusible auquel il est fait référence dans le texte doit être remplacé par un fusible du
même calibre.
Identie une borne de protection de mise à la masse qui doit être raccordée correctement
avant de procéder au raccordement des autres équipements.
I dentie une borne de protection de mise à la masse qui peut être connectée en tant que
borne de mise à la masse supplémentaire.
Avertissements
Les avertissements suivants signalent des conditions ou des pratiques susceptibles d’occasionner
des blessures graves, voire même fatales :
Présence possible de tensions ou de courants dangereux — Mettez hors tension, débranchez et
retirez la pile (le cas échéant) avant de déposer les couvercles de protection, de défaire une soudure
ou de remplacer des composants.
Ne procédez pas seul à une intervention d’entretien — Ne réalisez pas une intervention d’entretien
interne sur ce produit si une personne n’est pas présente pour fournir les premiers soins en cas
d’accident.
Retirez tous vos bijoux — Avant de procéder à une intervention d’entretien, retirez tous vos bijoux,
notamment les bagues, la montre ou tout autre objet métallique.
Évitez tout contact avec les circuits exposés — Évitez tout contact avec les connexions, les composants
ou les circuits exposés s’ils sont sous tension.
Utilisez le cordon d’alimentation approprié — Utilisez exclusivement le cordon d’alimentation fourni
avec ce produit ou spécié pour ce produit.
Signale la présence de composants sensibles à l’électricité statique et qui sont susceptibles
d’être endommagés par une décharge électrostatique. Utilisez des procédures, des
équipements et des surfaces antistatiques durant les interventions d’entretien.
Raccordez le produit à la masse — Raccordez le conducteur de masse du cordon d’alimentation à
la borne de masse de la prise secteur.
Utilisez le produit lorsque les couvercles et les capots sont en place — N’utilisez pas ce produit si
les couvercles et les capots sont déposés.
2014 01 27 K2 SAN Installation and Service Manual 17
Page 18
Safety Summaries
Utilisez le bon fusible — Utilisez exclusivement un fusible du type et du calibre spéciés pour ce
produit.
Utilisez ce produit exclusivement dans un environnement sec — N’utilisez pas ce produit dans un
environnement humide.
Utilisez ce produit exclusivement dans un environnement non explosible — N’utilisez pas ce produit
dans un environnement dont l’atmosphère est explosible.
Présence possible de courants de fuite — Un raccordement à la masse est indispensable avant la
mise sous tension.
Deux alimentations peuvent être présentes dans l’équipement — Assurez vous que chaque cordon
d’alimentation estraccordé à descircuits de terreséparés. Débranchez lesdeux cordons d’alimentation
avant toute intervention.
Fusion neutre bipolaire — Débranchez l’alimentation principale avant de procéder à une intervention
d’entretien.
Utilisez les points de levage appropriés — Ne pas utiliser les verrous de la porte pour lever ou déplacer
l’équipement.
Évitez les dangers mécaniques — Laissez le ventilateur s’arrêter avant de procéder à une intervention
d’entretien.
Mises en garde
Les mises en garde suivantes signalent les conditions et les pratiques susceptibles d’occasionner
des endommagements à l’équipement et aux installations :
N’ouvrez pas l’appareil — Toute ouverture prohibée de l’appareil aura pour effet d’annuler la garantie.
Utilisez la source d’alimentation adéquate — Ne branchez pas ce produit à une source d’alimentation
qui utilise une tension supérieure à la tension nominale spéciée pour ce produit.
Assurez une ventilation adéquate — Pour éviter toute surchauffe du produit, assurez une ventilation
de l’équipement conformément aux instructions d’installation. Ne déposez aucun document sous
l’appareil – ils peuvent gêner la ventilation. Placez l’appareil sur une surface plane.
Utilisez des procédures antistatiques - Les composants sensibles à l’électricité statique présentsdans
l’équipement sont susceptibles d’être endommagés par une décharge électrostatique. Utilisez des
procédures, des équipements et des surfaces antistatiques durant les interventions d’entretien.
N’utilisez pas la carte CF avec un PC — La carte CF a été spécialement formatée. Le logiciel enregistré
sur la carte CF risque d’être effacé.
N’utilisez pas l’équipement si un dysfonctionnement est suspecté — Si vous suspectez un
dysfonctionnement du produit, faites inspecter celui-ci par un membre qualié du personnel
d’entretien.
Acheminez les câbles correctement — Acheminez les câbles d’alimentation et les autres câbles de
manière à ce qu’ils ne risquent pas d’être endommagés. Supportez correctement les enroulements
de câbles an de ne pas endommager les connecteurs.
Utilisez les cordons d’alimentation adéquats — Les cordons d’alimentation de cet équipement, s’ils
sont fournis, satisfont aux exigences de toutes les réglementations régionales. L’utilisation de cet
équipement à des tensions dépassant les 130 V en c.a. requiert des cordons d’alimentation qui
satisfont aux exigences des congurations NEMA. Les cordons internationaux, s’ils sont fournis,
ont reçu l’approbation du pays dans lequel l’équipement est utilisé.
18 K2 SAN Installation and Service Manual 2014 01 27
Page 19
Utilisez une pile de remplacement adéquate — Ce produit renferme une pile. Pour réduire le risque
d’explosion, vériez la polarité et ne remplacez la pile que par une pile du même type, recommandée
par le fabricant. Mettez les piles usagées au rebut conformément aux instructions du fabricant des
piles.
Cette unité ne contient aucune partie qui peut faire l’objet d’un entretien par l’utilisateur. Si un
problème survient, veuillez contacter votre distributeur local.
Certifications and compliances
Canadian certified power cords
Canadian approval includes the products and power cords appropriate for use in the North America
power network. All other power cords supplied are approved for the country of use.
FCC emission control
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which
case the user will be required to correct the interference at his own expense. Changes or modications
not expressly approved by Grass Valley can affect emission compliance and could void the user’s
authority to operate this equipment.
Safety Summaries
Canadian EMC Notice of Compliance
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital
apparatus set out in the Radio Interference Regulations of the Canadian Department of
Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables
aux appareils numériques de la classe A préscrites dans le Règlement sur le brouillage radioélectrique
édicté par le ministère des Communications du Canada.
EN55103 1/2 Class A warning
This producthas been evaluatedfor Electromagnetic Compatibility under the EN 55103-1/2 standards
for Emissions and Immunity and meets the requirements for E4 environment.
This product complies with Class A (E4 environment). In a domestic environment this product may
cause radio interference in which case the user may be required to take adequate measures.
FCC emission limits
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) This device may not cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause undesirable operation.
2014 01 27 K2 SAN Installation and Service Manual 19
Page 20
Safety Summaries
Laser compliance
Laser safety requirements
This product may contain a Class 1 certied laser device. Operating this product outside specications
or altering its original design may result in hazardous radiation exposure, and may be considered
an act of modifying or new manufacturing of a laser product under U.S. regulations contained in
21CFR Chapter 1, subchapter J or CENELEC regulations in HD 482 S1. People performing such
an act are required by law to recertify and reidentify this product in accordance with provisions of
21CFR subchapter J for distribution within the U.S.A., and in accordance with CENELEC HD 482
S1 for distribution within countries using the IEC 825 standard.
Laser safety
Laser safety in the United States is regulated by the Center for Devices and Radiological Health
(CDRH). The laser safety regulations are published in the “Laser Product Performance Standard,”
Code of Federal Regulation (CFR), Title 21, Subchapter J.
The International Electrotechnical Commission (IEC) Standard 825, “Radiation of Laser Products,
Equipment Classication, Requirements and User’s Guide,” governs laser products outside the
United States. Europe and member nations of the European Free Trade Association fall under the
jurisdiction of the Comité Européen de Normalization Electrotechnique (CENELEC).
Safety certification
This product has been evaluated and meets the following Safety Certication Standards:
ANSI/UL 60950-1
IEC 60950-1 with CB cert.
CAN/CSA C22.2 No. 60950-1
BS EN 60950-1
ESD Protection
Electronics todayare more susceptibleto electrostatic discharge (ESD) damage thanolder equipment.
Damage to equipment can occur by ESD elds that are smaller than you can feel. Implementing the
information in this section will help you protect the investment that you have made in purchasing
Grass Valley equipment. This section contains Grass Valley’s recommended ESD guidelines that
should be followed when handling electrostatic discharge sensitive (ESDS) items. These minimal
recommendations are based on the information in the Sources of ESD and Risks on page 21 area.
The information in Grounding Requirements for Personnel on page 22 is provided to assist you in
selecting an appropriate grounding method.
Designed/tested for compliance with:Standard
Safety of Information Technology Equipment, including
Electrical Business Equipment (Second edition 2007).
Safety of Information Technology Equipment, including
Electrical Business Equipment (Second edition, 2005).
Safety of Information Technology Equipment, including
Electrical Business Equipment (Second edition 2007).
Safety of Information Technology Equipment, including
Electrical Business Equipment 2006.
20 K2 SAN Installation and Service Manual 2014 01 27
Page 21
Recommended ESD Guidelines
Follow these guidelines when handling Grass Valley equipment:
• Only trained personnel that are connected to a grounding system should handle ESDS items.
• Do not open any protective bag, box, or special shippingpackaging until you have been grounded.
NOTE: When a Personal Grounding strap is unavailable, as an absolute minimum, touch a
metal object that is touching the oor (for example, a table, frame, or rack) to discharge any
static energy before touching an ESDS item.
• Open the anti-static packaging by slitting any existing adhesive tapes. Do not tear the tapes off.
• Remove the ESDS item by holding it by its edges or by a metal panel.
• Do not touch the components of an ESDS item unless it is absolutely necessary to congure or
repair the item.
• Keep the ESDS work area clear of all nonessential items such as coffee cups, pens, wrappers
and personal items as these items can discharge static. If you need to set an ESDS item down,
place it on an anti-static mat or on the anti-static packaging.
Sources of ESD and Risks
Safety Summaries
The following information identies possible sources of electrostatic discharge and can be used to
help establish an ESD policy.
Personnel
One of the largest sources of static is personnel. The static can be released from a person’s clothing
and shoes.
Environment
The environment includes the humidity and oors in a work area. The humidity level must be
controlled and should not be allowed to uctuate over a broad range. Relative humidity (RH) is a
major part in determining the level of static that is being generated. For example, at 10% - 20% RH
a person walking across a carpeted oor can develop 35kV; yet when the relative humidity is
increased to 70% - 80%, the person can only generate 1.5kV.
Static is generated as personnel move (or as equipment is moved) across a oor’s surface. Carpeted
and waxed vinyl oors contribute to static build up.
Work Surfaces
Painted or vinyl-covered tables, chairs, conveyor belts, racks, carts, anodized surfaces, plexiglass
covers, and shelving are all static generators.
Equipment
Any equipment commonly found in an ESD work area, such as solder guns, heat guns, blowers,
etc., should be grounded.
Materials
Plastic work holders, foam, plastic tote boxes, pens, packaging containers and other itemscommonly
found at workstations can generate static electricity.
2014 01 27 K2 SAN Installation and Service Manual 21
Page 22
Safety Summaries
Grounding Requirements for Personnel
The information in this section is provided to assist you in selecting a grounding method. This
information is taken from ANSI/ESD S20.20-2007 (Revision of ANSI/ESD S20.20-1999).
Product Qualification
Required LimitsTest MethodPersonnel Grounding Technical
Requirement
< 3.5 x 107ohmANSI/ESD S1.1 (Section 5.11)Wrist Strap System*
< 3.5 x 107ohmANSI/ESD STM97.1Flooring / Footwear System –
Method 1
Flooring / Footwear System –
Method 2 (both required)
1ANSI/ESD STM97.2
< 109ohmANSI/ESD STM97.
< 100 VANSI/ESD STM97.2
Product qualication is normally conducted during the initial selection of ESD control products and
materials. Any of the following methods can be used: product specication review, independent
laboratory evaluation, or internal laboratory evaluation.
Compliance Verification
Required LimitsTest MethodPersonnel Grounding Technical
Requirement
< 3.5 x 107ohmESD TR53 Wrist Strap SectionWrist Strap System*
Flooring / Footwear System –
Method 1
Flooring / Footwear System –
Method 2 (both required)
ESD TR53 Footwear Section
ESD TR53 Footwear Section
< 3.5 x 107ohmESD TR53Flooring Section and
< 1.0 x 109ohmESD TR53Flooring Section and
* For situations where an ESD garment is used as part of the wrist strap grounding path, the total
system resistance, including the person, garment, and grounding cord, must be less than 3.5 x 10
ohm.
7
22 K2 SAN Installation and Service Manual 2014 01 27
Page 23
Preface
About this document
This is a K2™product manual.It describes the K2 10Gv2 Storage Area Network (SAN) and provides
instructions for installing and using the product in a variety of applications. The manual contains
information for K2 storage in both basic (non-redundant) and redundant congurations. Refer to
the sections that apply your K2 SAN's conguration. For custom K2 SANs that do not t one of
these pre-dened levels, you must work with your Grass Valley representative for installation and
operation.
The K2 10Gv2 SAN, andits K2 10Gv2 RAID storage, is documented in this manual. The K2 10Gv2
SAN is dened as follows: The K2 SAN with 8 Gig Fibre Channel and 10 Gig iSCSI connections.
Includes support for 2.5 inch drives and large capacity drives. Introduced in late 2012. The K2
10Gv2 SAN requires K2 software version 9.0 and higher. Some devices and/or systems used with
older K2 SANs are not compatible with the K2 10Gv2 SAN. Consult "K2 Release Notes" for
compatibility information.
For information on products that are compatible as clients to the K2 SAN, refer to those product’s
manuals, such as the "GV STRATUS Installation and Service Manual" and the "K2 FCP Connect
Installation Manual".
About documentation for previous K2 SANs
If you are looking for information about previous versions and models of K2 SAN devices, refer to
latest version of the manual published when those devices were shipped from Grass Valley, as
follows:
Manual part numberDates shippedStorage product name
071-8779-012010-2012G10
071-8724-012007 - 2010L10, L20, L30, L35
071-8461-022005 - 2007L2, L3
For more information
The following sections help you nd the information you need in product manuals and elsewhere.
For the installer of a standalone K2 product with internal storage
If you are installing a K2 system, such as a K2 Summit/Solo system, with standalone internal storage,
refer to documentation in the following sequence:
2014 01 27 K2 SAN Installation and Service Manual 23
Page 24
Preface
In these formats:In these locations…Find this document…
PDF leGrass Valley WebsiteK2 Release Notes1
PrintedK2 product shipping boxQuick Start Guide for the K2 product2
PDF leK2 Documentation Set
PDF leGrass Valley Website
PDF leK2 Documentation SetK2 System Guide3
PDF leGrass Valley Website
For the installer of a K2 product with direct connect storage
If you are installing a standalone K2 system, such as a K2 Summit system, with direct connect
external RAID storage, refer to documentation in the following sequence:
In these formats:In these locations…Find this document…
PDF leGrass Valley WebsiteK2 Release Notes1
For the installer of K2 Summit systems with K2 SAN shared storage
If you are installing a K2 SAN with connected K2 Summit systems, refer to documentation in the
following sequence:
PrintedK2 RAID shipping boxK2 Storage Cabling Guide2
PDF leK2 Documentation Set
PDF leGrass Valley Website
PrintedK2 product shipping boxQuick Start Guide for the K2 product3
PDF leK2 Documentation Set
PDF leGrass Valley Website
PDF leK2 Documentation SetK2 System Guide4
PDF leGrass Valley Website
In these formats:In these locations…Find this document…
PDF leGrass Valley WebsiteK2 Release Notes1
PrintedK2 RAID shipping boxK2 Storage Cabling Guide2
PDF leK2 Documentation Set
PDF leGrass Valley Website
PrintedK2 product shipping boxQuick Start Guide for the K2 product3
PDF leK2 Documentation Set
PDF leGrass Valley Website
24 K2 SAN Installation and Service Manual 2014 01 27
Page 25
K2 Release Notes
Contains the latest information about the software shipped on your system, including software
upgrade instructions, software specications and requirements, feature changes from the previous
releases, and any known problems. You should always check the Grass Valley Website to determine
if there is an updated version of release notes available.
Quick Start Guides
The Quick Start Guide isa printed document,shipped in theproduct packaging with K2 Summit/Solo
systems and K2 Dyno Replay Controllers. The Quick Start Guide provides step-by-step installation
instructions for basic installation and operation of the product.
Preface
In these formats:In these locations…Find this document…
PDF leK2 Documentation SetK2 SAN Installation and Service Manual4
PDF leGrass Valley Website
PDF leK2 Documentation SetK2 System Guide5
PDF leGrass Valley Website
K2 Storage Cabling Guide
The K2 Storage Cabling Guide is a printed document, shipped in the product packaging with the
primary RAID storage chassis. The cabling guide provides instructions for K2 Storage Area Network
(SAN) cabling and external conguration. The cabling guide provides instructions for each level
of K2 SAN and covers both redundant and basic (non-redundant) systems. It also provides instructions
for connecting direct-connect external RAID storage to K2 Summit systems.
K2 Documentation Set
Except for the release notes, the full set of support documentation, including this manual, is available
in the K2 or K2/STRATUS Documentation Set. You can nd the Documentation Set on the Grass
Valley website. The following URL allows you to browse by K2 software version:
http://www.grassvalley.com/dl/k2_summit
You can also nd the Documentation Set on the USB Recovery Flash drive that ships with your K2
Summit/Solo system.
The Documentation Set includes the following K2 product documents:
K2 AppCenter User
Manual
Quick Start Guides
Provides instructions for conguring and operating the media channels
of product.
The Quick Start Guide provides step-by-step installation instructions
for basic installation and operation of the product.
K2 System Guide
2014 01 27 K2 SAN Installation and Service Manual 25
Contains the product specications and instructions for modifying
system settings.
Contains information on servicing and maintaining the K2 product.K2 Service Manuals
Page 26
Preface
K2 SAN Installation and
Service Manual
K2 Storage Cabling Guide
Fibre Channel Switch
Installation Manual
On-line Help Systems
You can nd documentation online with products as follows:
K2 AppCenter Help
SiteCong Help
Contains installation, conguration, and maintenance procedures for
shared storage options.
The cabling guide provides instructions for K2 Storage Area Network
(SAN) cablingand external conguration. The cabling guide provides
instructions for each level of K2 SAN and covers both redundant and
basic (non-redundant) systems. It also provides instructions for
connecting direct-connect external RAID storage to K2 Summit
systems.
Contains information on conguring and servicing the Fibre Channel
switch.
Contains information on using K2 AppCenter. In the AppCenter user
interface menu bar select Help, then choose AppCenter Help Topics
from the drop-down menu.
Contains information on using SiteCong. In the SiteCong user
interface menu bar select Help, then choose SiteConfig Help Topics
from the drop-down menu.
K2 FCP Connect documentation
The K2 FCP Connect product has its own documentation set, described as follows:
GV Connect User Manual
K2 FCP Connect
Installation Manual
K2 FCP Connect Release
Notes
Provides instructions for using GV Connect, which is a Final Cut Pro
plugin, to access and work with K2 assets. GV Connect is part of the
K2 FCP Connect product.
Provides detailed instructions to install and congure the K2 FCP
Connect product.
Contains the latest information about the K2 FCP Connect product,
including software upgrade instructions, software specications and
requirements, feature changes from the previous releases, and any
known problems. You should always check the Grass Valley Website
to determine if there is an updated version of release notes available.
Grass Valley Website
This public Web site contains all the latest manuals and documentation, and additional support
information. Use the following URL.
http://www.grassvalley.com
26 K2 SAN Installation and Service Manual 2014 01 27
Page 27
Dell Server Documentation
If your system includes a Grass Valley product on a Dell server platform, refer to the applicable
Grass Valley product manual for installation and conguration information. However, a full set of
Dell server documentation has been provided on the Dell Product Documentation CD-ROM. Refer
to the documents on this CD-ROM only as required by procedures in Grass Valley product manual.
Preface
Information referenced on the Dell Product Documentation CD-ROM includes, but is not limited
to:
• Unpacking and rack-mounting
• Important safety and regulatory information
• Status indicators, messages, and error codes
• Troubleshooting help
CAUTION: Do not use the Dell Quick Installation Guide provided with the Dell CD-ROM
package. This guide includes instructions for using the OpenManage software CD-ROM to
install an operating system, which is not necessary on the Grass Valley product.
2014 01 27 K2 SAN Installation and Service Manual 27
Page 28
Preface
28 K2 SAN Installation and Service Manual 2014 01 27
Page 29
Product description
K2 SAN overview description
The K2 Storage Area Network (SAN) is Grass Valley’s shared storage solution that gives multiple
clients access to a common pool ofmedia. In the iSCSISAN, clients access the shared media storage
via a Gigabit Ethernet network and a Fibre Channel connection. Data is communicated using the
Small Computer System Interface (SCSI) data transfer interface and the Internet SCSI (iSCSI)
protocol.
A custom-designed Fibre Channel SAN is also available in which clients access RAID storage via
a Fibre Channel network, and the K2 Media Server connects via Ethernet for control functions only.
Refer torelated topics in "K2 System Guide" for diagrams and explanations of the media le system
and the media database.
2014 01 27 K2 SAN Installation and Service Manual 29
Page 30
Product description
K2 SAN key features
The key features of the iSCSI K2 SAN are as follows:
• iSCSI storage access protocol
• Gigabit Ethernet connectivity
• RAID 5 and RAID 6 storage
• FTP transfers
• Enhanced IT networked storage congurations to t a wide variety of size and performance
• Scaling from 100 to < 5000 MB/s
• Redundancy and fault recovery with no single point of failure
• Tuned and optimized le system for reliable and robust transaction of media les
• Best in class storage management for high throughput, deterministic performance with load
• Best in class support for 3rd party editors
requirements.
balancing, priority of service, and quality of service
What's new in the K2 10Gv2 SAN
The primary differences between K2 10Gv2 SAN and previous K2 SANs are as follows:
• 2.5 inch drives — A chassis is available that holds 2.5 inch drives with a capacity of 24 drives.
A chassis is also available that holds 3.5 inch drives, similar to previous K2 SANs.
• Larger capacity drives — Both 2.5 inch and 3.5 inch drives have increased capacity.
If you are familiar with previous K2 SANs, keep these differences in mind as you read about the
K2 10Gv2 SAN in this manual. If you need information about previous K2 SANs, refer to previous
versions of this manual.
Related Topics
About documentation for previous K2 SANs on page 23
K2 Storage types and terms
Grass Valley congures K2 storage to meet their customer’s workow needs. This topic describes
some typical congurations and terminology.
Online – Online storage is considered “Tier 1” K2 storage in that it is suitable for both record and
play. The purpose of an online SAN is to record and play media for broadcast or other on-air
applications. Performance requirements are critical for online applications, so this type of SAN
features high performance, low latency storage. Online storage can be iSCSI or Fibre Channel.
Production – Production storage is considered “Tier 2” K2 storage in that it is suitable for record
(ingest) but not recommended for on-air playout. The purpose of production storage is to provide
cost effective storage for production and editing applications. These applications require high
performance but internal buffering in editing software puts less stress on the storage system, so
performance requirements are lower than for online storage. Therefore, production storage can use
30 K2 SAN Installation and Service Manual 2014 01 27
Page 31
Product description
low cost, high capacity drives, such as 7.2K SAS drives. In a typical workow, production is nished
on the production storage and then the content is pushed to an online K2 system for playout.
Production storage is congured similar to Online storage, but with the 7.2K SAS RAID devices
and drives. Production storage can be iSCSI or Fibre Channel.
Nearline – Nearline storage is considered “Tier 3” K2 storage in that it is suitable for media le
transfer but does not support either record or play. The purpose of a nearline SAN is to provide a
large pool of storage to which les can be saved. The nearline system is considered an “ofine”
system, which means the system stores les only, such GXF les or MXF les, with no ability to
record or play those les directly on the system. The les on a nearline system can be readily
available to an online K2 system via FTP or CIFS connections over Ethernet. Nearline storage has
Fibre Channel connections between the K2 Media Server and the RAID storage devices.
Workgroup – Workgroup storage is a Fibre-Channel-only type of production storage intended for
small workgroups. This type of storage is no longer recommended, as technology advances provide
better value with standard iSCSI Production storage.
Live Production – In K2Cong you can create a Live Production K2 SAN. This mode can be
applied toonline and production SANs. A K2 SAN with LiveProduction mode has a shorter minimum
delay between start record andstart playout and is ideal for use with K2 Dyno. To support this mode,
Grass Valley must design your K2 SAN for increased bandwidth.
Stand-alone – This is not shared storage. It is the local storage for a K2 Media Client, K2 Summit
Production Client, or K2 Solo Media Server. Stand-alone storage can be internal media drives or
direct-connect K2 RAID devices. Refer to the K2 System Guide.
K2 SAN descriptions
The followingsections describe the standard, pre-dened structures of the K2 SAN. Referto related
topics in this document for more information on custom K2 SAN systems.
Related Topics
About custom K2 SAN systems on page 325
2014 01 27 K2 SAN Installation and Service Manual 31
Page 32
Product description
Basic K2 SAN description
The basic (non-redundant) K2 SAN can be an online SAN or a production SAN. The SAN has one
Ethernet switch, one K2 Media Server, and one basic K2 RAID chassis. RAID Expansion chassis
are optional for increased storage capacity.
K2 clients and other iSCSI clients, such as high resolution GV STRATUS clients, are connected to
the Ethernet switch. Each K2 client has one GigE connection for media and one GigE connection
for control. The GigE switch is congured with V-LANs to keep the control/FTP trafc and the
media (iSCSI) trafc separate.
The K2 Media Server has one 10 Gig connection for media (iSCSI), one GigE connection for control,
one GigE connection for FTP, and one Fibre Channel connection to the RAID storage. The server
hosts an iSCSI interface card for the 10 Gig media connection and a Fibre Channel card for the
RAID storage connection. The iSCSI interface card provides a bridge between iSCSI and Fibre
Channel SCSI. The server also hosts software components that allow it to function in various roles,
including media le system manager, media database server, and FTP server.
The basic K2 RAID chassis is connected via a single Fibre Channel connection to the K2 Media
Server. It also must be connected to the GigE control network. An online SAN has 2.5 inch 10K
drives, with 24 drives per chassis. A production SAN has 3.5 inch 7.2K drives with 12 drives per
chassis.
Optional 10 Gig NH K2 Media Servers are available to provide additional FTP bandwidth. If the
optional NH server is used, all FTP trafc goes to this server, so the K2 Media Server is not cabled
or congured for FTP.
The K2Cong control point PCis connected to the GigE control network. The K2Cong application
runs on this PC for conguring the SAN. The SiteCong application also runs on this PC.
32 K2 SAN Installation and Service Manual 2014 01 27
Page 33
FTP/streaming trafc accesses the K2 SAN via the FTP GigE port on K2 Media Servers.
FTP/streaming trafc does not go to K2 clients.
Related Topics
Device terminology on page 249
Setting up the Ethernet switch on page 63
Redundant K2 SAN description
Product description
The redundant K2 SAN can be an online SAN or a production SAN. The SAN has two Ethernet
switches connected by Inter-Switch Links (ISLs) to support a redundant Ethernet fabric. The SAN
also has redundant K2 Media Servers. The servers are congured to have identical roles. This
provides redundancyfor database, le system, iSCSI bridge, and FTProles. One K2 RAID supports
redundant Fibre Channel connections. Expansion chassis are optional for increased storage capacity.
K2 clients have a pair of redundant (teamed) Gigabit Ethernet ports for control and two Gigabit
Ethernet ports (A and B) for media (iSCSI). Each port of the control team is connected to a different
switch. The A media port goes to the A switch and the B media port goes to the B switch. The
switches are congured with V-LANs to keep the control/FTP and media (iSCSI) trafc separate.
Each K2 Media Server has one 10 Gig connection for media (iSCSI), one GigE connection for
control, one GigE connection for FTP, and one Fibre Channel connection to the RAID storage. All
GigE connections and the 10 Gig connection on a server go to the same GigE switch. The server
hosts a 10 Gig iSCSI interface card for the 10 Gig media connections and a Fibre Channel card for
the RAID storage connection. The iSCSI interface card provides a bridge between iSCSI and Fibre
Channel SCSI. The server also hosts software components that allow it to function in its roles,
including media le system manager, media database server, and FTP server. Redundant K2 Media
2014 01 27 K2 SAN Installation and Service Manual 33
Page 34
Product description
Servers are connected by a serial cable which supports the heartbeat signal required for automatic
system recovery (failover) features.
The redundant K2 RAID chassis has redundant RAID controllers to support the Fibre Channel
connections from the K2 Media Servers. The redundant K2 RAID chassis is also connected to the
GigE control network. It also must be connected to the GigE control network.
On the redundant K2 RAID chassis there is one RAID 1 RANK (also know as LUN) for media le
system metadata le and journal le that comes with one hot spare drive. The rst set of drives
consists of 3 blank slots. The remainder of the RAID storage is RAID 5 or RAID 6 for media. An
online SAN has 2.5 inch 10K drives, with 24 drives per chassis. A production SAN has 3.5 inch
7.2K drives with 12 drives per chassis.
Optional 10 Gig NH K2 Media Servers are available to provide additional FTP bandwidth. If the
optional NH server is used, all FTP trafc goes to this server, so neither K2 Media Server is cabled
or congured for FTP.
The K2Cong control point PCis connected to the GigE control network. The K2Cong application
runs on this PC for conguring the SAN. The SiteCong application also runs on this PC.
FTP/streaming trafc accesses the K2 SAN via the FTP GigE port on K2 Media Servers.
FTP/streaming trafc does not go to K2 clients.
Related Topics
Device terminology on page 249
Setting up the Ethernet switch on page 63
Basic Nearline K2 SAN description
The purpose of a Nearline SAN is to provide a large pool of storage to which les can be saved.
The Nearline system is considered an “ofine” system, which means the system stores les only,
such GXF les or MXF les, with no ability to record or play those les directly on the system.
This is because the Nearline system has no media database to support “movies” or “clips”, such as
there is on an “online” K2 SAN. However, the les on a Nearline system can be readily available
to an online K2 system via FTP transfer.
34 K2 SAN Installation and Service Manual 2014 01 27
Page 35
Product description
The basic Nearline SAN has one Ethernet switch.
The SAN also has one 10 Gig NH K2 Media Server. The NH server for a Nearline system has two
ports for Fibre Channel connections. NH servers do not have media (iSCSI) ports.
A NH server on a Nearline system is congured with roles of FTP server and Media le system
server.
In the Nearline system no K2 Media Servers take the role of iSCSI bridge or media database server.
No K2 clients or any other generic client are part of the Nearline system.
7.2K SAS drives provide the media le storage on a Nearline system. While these drives do not
provide the high bandwidth of the drives required by an online K2 SAN, they offer larger capacity
and lower cost. This makes these drives ideal for the Nearline SAN.
The primary RAID chassis has one controller. The primary RAID chassis is connected via Fibre
Channel to the NH server. The controller in the RAID chassis also must be connected to the GigE
control network.
There must be one primary RAID chassis and there may be optional Expansion chassis. Primary
chassis and Expansion chassis containtwelve 3.5 inch drives. All disks in both primary and optional
Expansion chassis are bound as RAID 6.
The K2Cong control point PCis connected to the GigE control network. The K2Cong application
runs on this PC for conguring the SAN. The SiteCong application also runs on this PC.
Related Topics
Device terminology on page 249
Setting up the Ethernet switch on page 63
Redundant Nearline K2 SAN description
The purpose of a Nearline SAN is to provide a large pool of storage to which les can be saved.
The Nearline system is considered an “ofine” system, which means the system stores les only,
such GXF les or MXF les, with no ability to record or play those les directly on the system.
2014 01 27 K2 SAN Installation and Service Manual 35
Page 36
Product description
This is because the Nearline system has no media database to support “movies” or “clips”, such as
there is on an “online” K2 SAN. However, the les on a Nearline system can be readily available
to an online K2 system via FTP transfer.
The redundant Nearline SAN has two Ethernet switches, connected by Inter-Switch Links (ISLs)
to support a redundant Ethernet fabric.
The SAN also has two 10 Gig NH K2 Media Servers. The NH server for a Nearline system has two
ports for Fibre Channel connections. NH servers do not have media (iSCSI) ports.
A NH server on a Nearline system is congured with roles of FTP server and Media le system
server. On a redundant system these roles are identical on both servers and provide redundancy as
follows:
• FTP server — Both servers are active in this role simultaneously. To provide FTP redundancy
• Media le system server — Only one server is active at any one time in this role, and the media
in the event of a server failure, your facility’s FTP system must be able to access alternate FTP
servers.
le system provides redundancy. If a fault occurs on the active server, one of the other servers
automatically takes over as the active media le system server.
In the Nearline system no K2 Media Servers take the role of iSCSI bridge or media database server.
No K2 clients or any other generic client are part of the Nearline system.
7.2K SAS drives provide the media le storage on a Nearline system. While these drives do not
provide the high bandwidth of the drives required by an online K2 SAN, they offer larger capacity
and lower cost. This makes these drives ideal for the Nearline SAN.
The primary RAID chassis has two controllers. The primary RAID chassis is connected via Fibre
Channel to the NH server. These Fibre Channel connections access the disks simultaneously for
redundancy and increased bandwidth. Each controller in the RAID chassis must also be connected
to the GigE control network.
There must be one primary RAID chassis and there may be optional Expansion chassis. Primary
chassis and Expansion chassis containtwelve 3.5 inch drives. All disks in both primary and optional
Expansion chassis are bound as RAID 6.
The K2Cong control point PCis connected to the GigE control network. The K2Cong application
runs on this PC for conguring the SAN. The SiteCong application also runs on this PC.
Related Topics
Device terminology on page 249
Setting up the Ethernet switch on page 63
36 K2 SAN Installation and Service Manual 2014 01 27
Page 37
Preparing for installation
K2 SAN installation checklists
Use the following sequence of checklists to guide the overall task ow of installing and
commissioning a K2 SAN.
Pre-installation planning checklist
CommentInstructionsTask
Procure existing or create new
SiteCong systemdescription
Next: Infrastructure checklist
About developing a system
description on page 71
Infrastructure checklist
Rack and cable
Congure Ethernetswitch(es)
Install/update SiteCong on
control point PC
Next: Network setup and implementation checklist
To follow cabling instructions
Setting up the Ethernet switch
on page 63
Install SiteCong on control
point PC on page 67
Network setup and implementation checklist
You can do this before
arriving at the customer site.
CommentInstructionsTask
—
—
—
CommentInstructionsTask
Import or create the
SiteCong systemdescription
on the control point PC
Modify names and networks
in the SiteCong system
description.
2014 01 27 K2 SAN Installation and Service Manual 37
Importing a system description
on page 71
Modifying a device name on
page 72, Modifying the
control network on page 72,
Modifying the FTP/streaming
network on page 74,
Modifying a media (iSCSI)
network on page 76
Select IP address range for
each network and each device
type.
Set subnet mask and other
settings.
Page 38
Preparing for installation
CommentInstructionsTask
Verify/modify device
interfaces
Discover devices
Assign placeholder devices to
discovered devices
Congure IP settings of
network interfaces on
discovered devices
Congure names
Validate networks
Modifying K2 client
unassigned (unmanaged)
interface on page 80,
Modifying K2 Media Server
unassigned (unmanaged)
interface on page 82
Discovering devices with
SiteCong on page 85
Assigning discovered devices
on page 86
Modifying K2 client managed
network interfaces on page
87, Modifying K2 Media
Server managed network
interfaces on page 91
Making the host name the
same as the device name on
page 96
Pinging devices from the PC
that hosts SiteCong on page
97
Do not proceed until the
system description accurately
represents all aspects of the
actual system. Refer to
SiteCong Help Topics . Use
procedures as appropriate for
your site.
—
—
—
—
—
Distribute host table
information
Next: Software update checklist
Software update checklist
Create deployment groups
Place software on control
point PC
Check software on devices
Upgrade/install software to
devices from control point PC
Next: SAN conguration checklist
Generating host tables using
SiteCong on page 98
Conguring deployment
groups on page 101
Adding a software package to
a deployment group on page
102
Checking all currently
installed software on devices
on page 103
the K2 SAN on page 103
—
CommentInstructionsTask
—
—
—
Refer to K2 Release Notes.About deploying software for
38 K2 SAN Installation and Service Manual 2014 01 27
Page 39
SAN configuration checklist
Preparing for installation
CommentInstructionsTask
Import SiteCong system
description into K2Cong
Congure SAN in K2Cong
Verify SAN license
Add K2 clients to SAN
K2 SAN installation complete
Understanding system concepts
Make sure you understand the following system concepts before planning or implementing a K2
SAN.
Importing a SiteCong system
description into K2Cong on
page 120
K2 SAN
Use the appropriate
instructions for your K2 SAN.
Verify license on K2 Media
Server on page 222
Conguring a K2 client for the
K2 Storage System on page224
—
—Conguring and licensing the
The K2 Media Server with
role of le system server must
be licensed for your SAN's
design and bandwidth
requirements.
—
Control network description
The control network is for communication between devices and components. It does not have
real-time mediatrafc or streaming/FTPmedia trafc. The control network trafc must be separated
from the streaming/FTP network trafc and the media (iSCSI) network trafc. This separation may
be provided by different subnets, VLANs, or physical switch fabrics. The control network and the
streaming/FTP network, if on different subnets, may be on the same VLAN. The control network
and the media (iSCSI) network must not be on the same VLAN. Static IP addresses with name
resolution via host les are recommended for the control network.
The control network applies to both online, production, and nearline K2 SANs.
All the devices of the K2 SAN are on the control network. Stand-alone K2 clients can also be on
the same control network.
Redundant K2 SANs have one control network with hardware separated into an A side and a B side.
There is an A Ethernet switch and a B Ethernet switch.Switches are connected by InterSwitch Links
2014 01 27 K2 SAN Installation and Service Manual 39
Page 40
Preparing for installation
(ISLs or trunks) to provide redundant paths for control network trafc. On a redundant K2 SAN,
devices are on the control network as follows:
• Shared Storage K2 client - The two control GigE ports are congured as a team. The control
team shares a single IP address. One port of the team is on the A side and the other port of the
team is on the B side.
• K2 Media Server - Redundant K2 Media Servers with role of media le system/metadata server
are balanced between the A and B sides. One server is on the A side and the other server is on
the B side. K2 MediaServers with other roles, such as FTP server, are likewise balancedbetween
A and B sides.
• K2 RAID - When a K2 RAID device has redundant controllers, controller 0 is on the A side and
controller 1 is on the B side.
• Ethernet switch - For control and conguration, the A switch is on the A side and the B switch
is on the B side
Streaming/FTP network description
The streaming/FTP network is for media transfers and FTP trafc. The streaming/FTP network
network trafc must be separated from the control network trafc and the media (iSCSI) network
trafc. This separation may be provided by different subnets, VLANs, or physical switch fabrics.
The control network and the streaming/FTP network, if on different subnets, may be on the same
VLAN. The control network and the media (iSCSI) network must not be on the same VLAN. Static
IP addresses with name resolution via host les are recommended for the streaming/FTP network.
Hostnames of network adapters that are dedicated to the streaming/FTP network must be aliased in
the hosts le with the _he0 sufx. This directs the streaming trafc to the correct port.
The streaming/FTP network applies to both online and nearline K2 SANs. For nearline systems,
this is the primary network for moving media to and from the storage system.
Redundant K2 SANs have one streaming/FTP network with hardware separated into an A side and
a B side. There is an A Ethernet switch and a B Ethernet switch. Switches are connected by
InterSwitch Links (ISLs) to provide redundant paths for streaming/FTP trafc.
Only those K2 devices that host a K2 FTP interface are on the streaming/FTP network, as follows:
• K2 Media Servers - Those with the role of FTP server are connected via their dedicated FTP
port. On a redundant K2 SAN, if you have multiple K2 Media Servers with role of FTP server,
balance servers between the A and B sides.
• Stand-alone K2 clients - While not a part of a K2 SAN, stand-alone K2 clients can also be on
the streaming/FTP network. Connect to the dedicated FTP port.
NOTE: Shared storage K2 clients are not on the streaming/FTP network. They do not have a
FTP interface and they do not send or receive streaming/FTP trafc.
Automatic FTP server failover is not provided by the K2 SAN. If you require automatic failover to
a redundant FTP server for your streaming/FTP trafc, you must provide it through your FTP
application.
40 K2 SAN Installation and Service Manual 2014 01 27
Page 41
Media (iSCSI) network description
The media network is exclusively for real-time iSCSI trafc on a K2 SAN. It must be on a different
subnet than the control network and the streaming/FTP network. Furthermore, its trafc is kept
physically separate from that of other networks. This separation is provided by dedicated ports,
cables, and by a dedicated VLAN on theEthernet switch or by separate switches.Static IP addresses
are required for the media network. Name resolution is not necessary, so media network IP addresses
are not required in host les.
The media network applies to online K2 SANs. Nearline K2 SANs do not have a media network.
Redundant K2 SANs have redundant media networks: an A media network and a B media network.
The two networks are on separate subnets and are also physically separated onto the A Ethernet
switch and the B Ethernet switch. InterSwitch Links (ISLs) between switches do not carry media
(iSCSI) trafc. ISLs provide redundant paths for control network trafc and streaming/FTP network
trafc only.
Devices are on the media network as follows:
• Shared Storage K2 client - On a non-redundant K2 SAN, the A media port connects to the media
network. On a redundant K2 SAN, the A media port connects to the A media network and the
B media port connects to the B media network.
• K2 Media Server - A server has one port available for connection to a media network. This is a
10 Gig iSCSI interface adapter, which supports the functionality of a TCP/IP Ofoad Engine
(TOE). On a redundant K2 SAN, one server is on the A media network and one server is on the
B media network.
Preparing for installation
Networking tips
• Before conguringany devices for networks, determine thefull scope of IP addresses and names
needed for the all the machines in your system. Work with the network administrator at your
facility to have IP addresses and names available for your use.
• It is recommended that you use the patterns offered in SiteCong by default to establish a
consistent convention for machine names and IP addresses. You can plan, organize, and enter
this information in SiteCong as you develop a system description. You can do this even before
you have devices installed and/or cabled.
• On 64-bit devices, congure IPv4 addresses. Disable the IPv6 interface of the Control and FTP
interfaces. SiteCong always congures IPv4 addresses for 64-bit devices.
Network considerations and constraints
• If your GV STRATUS system is on a domain, all servers and client PCs on that system that have
any interaction with Grass Valley components must be logged on to Windows with a domain
user account. Do not use a local user account.
• Do not use any 10.1.0.n or 10.2.0.n IP addresses. These are used by the K2 RAID maintenance
port and must be reserved for that purpose. If these addresses are otherwise used, maintenance
port communication errors occur.
2014 01 27 K2 SAN Installation and Service Manual 41
Page 42
Preparing for installation
About host files
The hosts le is used by the control network and the streaming/FTP network for name resolution,
which determines the IP address of a device on the network when only the device name (hostname)
is given. The hosts le is located at C:\Windows\system32\drivers\etc\hosts on Windows XP
and later operating systems. The hosts le must be the same on all network devices. It includes the
names and addresses of all the devices on the network.
For FTP transfers on a K2 SAN, transfers go to/from K2 Media Servers that have the role of FTP
server. No transfers go directly to/from the shared storage K2 clients that are on the K2 SAN. To
support FTP transfers, in thehosts le the K2Media Server hostname musthave the _he0 extension
added at the end of the name and that hostname must be associated with the K2 Media Server's
FTP/streaming network IP address.
Here is an example of IP addresses and names associated in a hosts le:
192.168.100.11 root_server_1
192.168.101.11 root_server_1_he0
192.168.100.21 root_server_2
192.168.101.21 root_server_2_he0
192.168.100.31 root_server_3
192.168.101.31 root_server_3_he0
192.168.100.41 root_server_4
192.168.101.41 root_server_4_he0
192.168.100.51 root_raid_1
192.168.100.61 root_gige_1
In this example 192.168.100.xx is the control network and 192.168.101.xx is the streaming/FTP
network. Each K2 Media Server has its hostname associated with its control network IP address. In
addition, each K2 Media Server (that has the role of FTP server) has its _he0 hostname associated
with its streaming/FTP network address.
Use SiteCong to dene yournetworks and devices. When you do so, SiteCong createsthe correct
hosts le and copies the hosts le to each network device.This enforces consistent hosts les across
networks and reduces errors introduced by editing and copying hosts les on individual devices.
You can also view hosts les from SiteCong for troubleshooting purposes.
Host Table tips
• If transferring to or from a Prole XP or Open SAN system via UIM, the hosts le must also
follow UIM naming conventions for those systems. Refer to the UIM Instruction Manual.
• Do not enable name resolutions for media (iSCSI) network IP addresses in the hosts le, as
hostname resolutionis not required for the media network. If desired, you can enter media network
information in the hosts le as commented text as an aid to managing your networks.
42 K2 SAN Installation and Service Manual 2014 01 27
Page 43
• Use the following tip with care. While it can solve a problem, it also introduces a nameresolution
"anomaly" that might be confusing if not considered in future troubleshooting activities.
For each SAN (shared storage) K2 client, add the "_he0" sufx to the hostname but then associate
that hostname with the K2 Media Server's FTP/streaming network IP address, not the K2 client's
IP address. Aliasing K2 client hostnames in this way would not be required if the transfer
source/destination was always correctly specied as the K2 Media Server. However, a common
mistake is to attempt a transfer in which the source/destination is incorrectly specied as the K2
client. The host le aliasing corrects this mistake and redirects to the K2 Media Server, which
is the correct transfer source/destination.
An example of a hosts le entry with this type of aliasing is as follows:
192.168.101.11 server_1_he0 client_1_he0 client_2_he0
Dell R620 Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks.
Preparing for installation
Table 1: Mechanical specifications
SpecificationCharacteristic
Rack-mountCabinet Type
1Rack units
482.4 (w) x 42.8 (h) x 683.7 (d) mmExternal Dimensions
Maximum 18.6kg , 40.96 lbsWeight
Table 2: Power specifications
consumption
(BTU/hr max)
current
495W AC750W AC1100W AC1100W DCSpecification
6.5A-3A10A-5A12A-6.5A32ACurrent
100-240VAC100-240VAC100-240VAC-48V to -60V DCSupply voltage
50/60Hz50/60Hz50/60HzN/AFrequency
1908284341004416Heat dissipation
55A55A55A55AMaximum inrush
Related Topics
K2 Media Server specications on page 251
NH K2 Media Server specications on page 252
2014 01 27 K2 SAN Installation and Service Manual 43
Page 44
Preparing for installation
K2 RAID Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks. These specications apply to K2 10Gv2 RAID (M100) chassis.
Table 3: Mechanical specifications
Expansion chassisPrimary chassisCharacteristic
Rack-mountRack-mountCabinet Type
22Rack units
External Dimensions
482 x 513.2 x 87.8 mm (no front
bezel)
Table 4: Power specifications
Power conditions
100 to 240 VAC, single-phase
50/60 Hz
(when operating in a 25° C
environment)
Related Topics
K2 RAID storage description on page 253
482 x 513.2 x 87.8 mm (no front
bezel)
29 kg maximum31 kg maximumWeight
Primary chassisPrimary chassisCharacteristic
100 to 240 VAC, single-phase
50/60 Hz
290 W400 WMaximum power consumption
44 K2 SAN Installation and Service Manual 2014 01 27
Page 45
Cabling K2 SAN devices
Rack-mount devices
All systems require this process.
Follow the instructions you received with the rack-mount hardware to install each component of
the system. One rack-unit spacing is recommended between components for ventilation. The
recommended arrangement of devices is as follows:
HP ProCurve Switch Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks.
Table 5: Mechanical specifications
SpecificationCharacteristic
Rack-mountCabinet Type
1Rack units
443 (w) x 44 (h) x 392 (d) mmExternal Dimensions
2014 01 27 K2 SAN Installation and Service Manual 45
Page 46
Cabling K2 SAN devices
Table 6: Power specifications
Dell R620 Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks.
Table 7: Mechanical specifications
SpecificationCharacteristic
Maximum 7 kgWeight
SpecificationCharacteristic
100-127 VAC/200-240 VAC; 50/60 HzType
4.0/2.0 A, 200WPower Consumption
SpecificationCharacteristic
Rack-mountCabinet Type
1Rack units
482.4 (w) x 42.8 (h) x 683.7 (d) mmExternal Dimensions
Maximum 18.6kg , 40.96 lbsWeight
Table 8: Power specifications
consumption
(BTU/hr max)
current
Related Topics
K2 Media Server specications on page 251
NH K2 Media Server specications on page 252
495W AC750W AC1100W AC1100W DCSpecification
6.5A-3A10A-5A12A-6.5A32ACurrent
100-240VAC100-240VAC100-240VAC-48V to -60V DCSupply voltage
50/60Hz50/60Hz50/60HzN/AFrequency
1908284341004416Heat dissipation
55A55A55A55AMaximum inrush
46 K2 SAN Installation and Service Manual 2014 01 27
Page 47
K2 Summit 3G Rack specifications
Use the following specications to determine load, spacing, power, and other factors when planning
system racks. These specications apply to K2 Summit 3G chassis.
Table 9: Mechanical specifications
Table 10: Power specifications
Cabling K2 SAN devices
SpecificationCharacteristic
Rack-mountCabinet Type
2Rack units
447 x 617 x 89 mmExternal Dimensions
25.0 kg maximumWeight
SpecificationCharacteristic
Maximum power consumption (when operating
in a 25° C environment)
K2 RAID Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks. These specications apply to K2 10Gv2 RAID (M100) chassis.
Table 11: Mechanical specifications
External Dimensions
Dual, redundantPower conditions
90 to 260V auto-range, 47-63HzMains Input Voltage
450W typical (standalone)
390W typical (SAN client)
Maximum AC current 8A @ 115VAC, 4A @
230VAC
482 x 513.2 x 87.8 mm (no front
bezel)
Expansion chassisPrimary chassisCharacteristic
Rack-mountRack-mountCabinet Type
22Rack units
482 x 513.2 x 87.8 mm (no front
bezel)
29 kg maximum31 kg maximumWeight
2014 01 27 K2 SAN Installation and Service Manual 47
Page 48
Cabling K2 SAN devices
Table 12: Power specifications
Primary chassisPrimary chassisCharacteristic
Power conditions
(when operating in a 25° C
environment)
Related Topics
K2 RAID storage description on page 253
FT Server Rack specifications
Use thefollowing specications to determine load, spacing, power, and other factorswhen planning
system racks.
Table 13: Mechanical specifications
Type I and Type II SpecificationCharacteristic
Rack-mountCabinet Type
4Rack units
483 (w) x 178 (h) x 736 (d) mm, 19.0 in. (w) x 7.0 in. (h) x 28.9 in. (d)External Dimensions
100 to 240 VAC, single-phase
50/60 Hz
100 to 240 VAC, single-phase
50/60 Hz
290 W400 WMaximum power consumption
Rack clearance
Table 14: Power specifications
Type
AC 100V-240V +/- 10%, 50/60Hz +/3Hz
Consumption
Securing a server to a rack
If the server is a Dell server, follow the instructions provided in the shipping box to install the rack
rails and position the server in the rack. For the Dell 1RU PowerEdge Server, follow the illustration
below to secure the system to the rack.
40 cm or more on top, 1 m or more on the front and rear, 60 cm or more
on the right and left.
Maximum 51.5kg , 113.3 lbsWeight
Type II SpecificationsType I SpecificationsPower Supply
AC 100V-240V +/- 10%, 50/60Hz +/3Hz
1300VA, 1290W1400VA, 1390WPower
48 K2 SAN Installation and Service Manual 2014 01 27
Page 49
Cabling K2 SAN devices
Install a screw in the bottom hole of the bracket on each side. Do not attempt to install a screw in
the top hole of the bracket.
Basic K2 SAN - Online or Production
2014 01 27 K2 SAN Installation and Service Manual 49
Page 50
Cabling K2 SAN devices
To cable this K2 SAN device…
K2 Summit system
platform…
K2 Summit 3G
Turn to these instructions:Of this model or
K2-XDP basic on page 52
system or rst
generation K2
Summit system
HP 2910Gigabit Ethernet Switch
Dell R620K2 Media Server
Dell R620NH10GE K2 Media Server
K2-SWE basic online/production on page 53
K2-SVR basic Dell R620 on page 56
K2-SVR-NH10GE online/production Dell R620 on page 58
(optional)
K2 RAIDK2 RAID
K2 RAID basic online/production on page 59
This manual documents the default GigE switch conguration. Other congurations are available,
depending on your port count and FTP bandwidth requirements.
Redundant K2 SAN - Online or Production
To cable this K2 SAN device…
K2 Summit system
platform…
K2 Summit 3G
Turn to these instructions:Of this model or
K2-XDP redundant on page 53
system or rst
generation K2
Summit system
50 K2 SAN Installation and Service Manual 2014 01 27
Page 51
Cabling K2 SAN devices
To cable this K2 SAN device…
(optional)
This manual documents the default GigE switch conguration. Other congurations are available,
depending on your port count and FTP bandwidth requirements.
Basic Nearline K2 SAN
platform…
HP 2910Gigabit Ethernet Switch
Dell R620K2 Media Server
Dell R620NH10GE K2 Media Server
K2 RAIDK2 RAID
Turn to these instructions:Of this model or
K2-SWE redundant online/production on page 54
K2-SVR redundant Dell R620 on page 57
K2-SVR-NH10GE online/production Dell R620 on page 58
K2 RAID redundant online/production on page 60
To cable this K2 SAN device…
platform…
HP 2910Gigabit Ethernet Switch
Dell R620NH10GE K2 Media Server
K2 RAIDK2 RAID
2014 01 27 K2 SAN Installation and Service Manual 51
Turn to these instructions:Of this model or
K2-SWE basic nearline on page 55
K2-SVR-NH10GE basic nearline Dell R620 on page 58
K2 RAID basic nearline on page 61
Page 52
!
OK
~AC
C1 C2 C3 C4
USB/1394
100BT/1000BT
GPI
VGA
REF.LOOP THROUGH
!
OK
~AC
To control por t
on GigE switch
To media (iSCSI) por t
on GigE switch
Cabling K2 SAN devices
Redundant Nearline K2 SAN
To cable this K2 SAN device…
platform…
HP 2910Gigabit Ethernet Switch
Dell R620NH10GE K2 Media Server
K2 RAIDK2 RAID
Cable K2 Summit system
As directed by the system diagram for your K2 storage, cable the K2 Summit system using the
instructions in this section.
K2-XDP basic
These cabling instructions apply to the following:
• K2 Summit 3G system or rst generation K2 Summit system on a basic (non-redundant) online
or production K2 SAN
Refer to "K2 Summit Production Client Quick Start Guide" for additional cabling details.
Turn to these instructions:Of this model or
K2-SWE redundant nearline on page 56
K2-SVR-NH10GE redundant nearline Dell R620 on page 58
K2 RAID redundant nearline on page 61
52 K2 SAN Installation and Service Manual 2014 01 27
Page 53
K2-XDP redundant
!
OK
~AC
C1 C2 C3 C4
USB/1394
100BT/1000BT
GPI
VGA
REF.LOOP THROUGH
!
OK
~AC
To control por t
on GigE switch A
To control por t
on GigE switch B
To media (iSCSI) por t
on GigE switch A
To media (iSCSI) por t
on GigE switch B
These cabling instructions apply to the following:
• K2 Summit 3G system or rst generation K2 Summit system on aredundant online or production
K2 SAN
Refer to "K2 Summit Production Client Quick Start Guide" for additional cabling details.
Cabling K2 SAN devices
Cable Ethernet switch
As directed by the system diagram for your storage system, cable the switch or switches for your
system using the instructions in this section.
These instructions are for the HP ProCurve switch 2900 and 2910 series.
If a different brand of switch, such as a Cisco Catalyst switch, is required by your site, apply the
information in the following procedures accordingly. Refer to the documentation you received with
the switch as necessary.
Install the switch in its permanent location. When installing in a video equipment rack, use 10-32
screws. Do not use HP’s 12-24 screws, as they can cause thread damage.
Provide power to the switch.
K2-SWE basic online/production
These cabling instructions apply to the following:
• HP 29xx series Gigabit Ethernet switch on a basic (non-redundant) online or production K2
SAN.
Front view
2014 01 27 K2 SAN Installation and Service Manual 53
Page 54
Cabling K2 SAN devices
Rear view
K2-SWE redundant online/production
These cabling instructions apply to the following:
• HP 29xx series Gigabit Ethernet switch on a redundant online or production K2 SAN.
Front view
Rear view
54 K2 SAN Installation and Service Manual 2014 01 27
Page 55
To server
10 Gig
Use SFP+ cable
with integrated
GBIC
Cabling K2 SAN devices
If you have other iSCSI clients, such as GV STRATUS high-resolution clients, that have just one
iSCSI connectionand one control connection, approximately half of the clients should be connected
to switch A and half of the clients should be connected to switch B. In a failover event, only the
clients connected to one of the switches will remain operational, so make connections accordingly.
Connect the client’s iSCSI connection to one of the media ports on a switch and the client’s control
connection to one of the control ports on the same switch.
If you have more than one optional NH10GE K2 Media Servers, balance servers between switch A
and switch B.
K2-SWE basic nearline
These cabling instructions apply to the following:
• HP 29xx series Gigabit Ethernet switch on a nearline K2 SAN with one NH K2 Media Server.
Front view
Rear view
2014 01 27 K2 SAN Installation and Service Manual 55
Page 56
Cabling K2 SAN devices
K2-SWE redundant nearline
These cabling instructions apply to the following:
• HP 29xx series Gigabit Ethernet switch on a nearline K2 SAN.
Front view
Rear view
Cable K2 Media Server
As directed by the system diagram for your K2 SAN, cable the K2 Media Server or Servers for your
K2 SAN using the instructions in this section.
K2-SVR basic Dell R620
These cabling instructions apply to the following:
• Dell R620 PowerEdge Server on a basic (non-redundant) online or production K2 SAN.
56 K2 SAN Installation and Service Manual 2014 01 27
Page 57
K2-SVR redundant Dell R620
These cabling instructions apply to the following:
• Dell R620 PowerEdge Server on a redundant online or production K2 SAN.
Cabling K2 SAN devices
Redundant server heartbeat serial cable
Take care to use the proper serial cable to interconnect redundant K2 Media Servers that take the
role of le system/database servers. This cable supports the heartbeat mechanism whereby the
servers monitor each other’s health. It is a 9 pin serial cable, but it is not a standard RS-232 null
modem cable. The heartbeat cable is supplied with your system (Grass Valley part number
174-8137-00) and has a pin conguration as follows:
1 – 4
2 – 3
3 – 2
4 – 1&6
5 – 5
6 – 4
7 – 8
8 – 7
9 – No Connect
2014 01 27 K2 SAN Installation and Service Manual 57
Page 58
Cabling K2 SAN devices
Cable NH10GE K2 Media Server
As directedby the systemdiagram for your K2 SAN, cable the NH10GE K2 Media Serveror Servers
for your K2 SAN using the instructions in this section
K2-SVR-NH10GE online/production Dell R620
These cabling instructions apply to the following:
• Dell R620 PowerEdge Server NH10GE on an online or production K2 SAN.
If you have more than one NH1 server, balance servers between controller 0 and controller 1.
K2-SVR-NH10GE basic nearline Dell R620
These cabling instructions apply to the following:
• Dell R620 PowerEdge Server NH10GE on a basic nearline K2 SAN.
K2-SVR-NH10GE redundant nearline Dell R620
These cabling instructions apply to the following:
• Dell R620 PowerEdge Server NH10GE on a nearline K2 SAN.
58 K2 SAN Installation and Service Manual 2014 01 27
Page 59
Cable K2 RAID
Cabling K2 SAN devices
Before cabling, install the K2 RAID chassis in its permanent location. After mounting the chassis
in the rack, you must secure brackets to the front rail to support the Grass Valley bezel. Refer to
related topics in this document for rack mount instructions.
You do not need to manually set a Fibre Channel address ID on controllers or a chassis address on
Expansion chassis.
As directed by the system diagram for your storage system, cable the K2 RAID devices using the
instructions in this section.
Once the RAID storage is connected and congured, do not swap Expansion chassis or otherwise
recongure storage. If you connect an Expansion chassis in a different order or to the wrong
controller, the controller will see a conguration mismatch and fault.
K2 RAID basic online/production
These cabling instructions apply to the following:
• K2 10Gv2 RAID on a basic (non-redundant) online or production K2 SAN.
2014 01 27 K2 SAN Installation and Service Manual 59
Page 60
AC DCAC
1
0
DC
ENCID
ENCID/DIAG
ID
1
0
ENCID
ENCID/DIAG
ID
Cabling K2 SAN devices
Continue this cable pattern for additional Expansion Chassis.
K2 RAID redundant online/production
These cabling instructions apply to the following:
• K2 10Gv2 RAID on a redundant online or production K2 SAN.
Continue this cable pattern for additional Expansion Chassis.
60 K2 SAN Installation and Service Manual 2014 01 27
Page 61
K2 RAID basic nearline
These cabling instructions apply to the following:
• K2 10Gv2 RAID on a basic nearline K2 SAN.
Cabling K2 SAN devices
Continue this cable pattern for additional Expansion Chassis.
K2 RAID redundant nearline
These cabling instructions apply to the following:
• K2 10Gv2 RAID on a Nearline K2 SAN.
2014 01 27 K2 SAN Installation and Service Manual 61
Page 62
Cabling K2 SAN devices
Continue this cable pattern for additional Expansion Chassis.
62 K2 SAN Installation and Service Manual 2014 01 27
Page 63
Setting up the K2 SAN infrastructure
Setting up the Ethernet switch
Consult with Grass Valley and use the following topics to determine the network and switch
conguration required for your site.
K2 SAN Ethernet switch requirements
K2 SAN Ethernet switch requirements are as follows:
• Redundancy — Aredundant K2 SAN must have an “A”media network and a “B” media network
and requires at least two switches, so that the A network and the B network never share the same
switch. Media trafc does not cross between an “A” switch and a “B” switch.
• Separation of iSCSI trafc — Media (iSCSI) trafc must be kept separate from control trafc,
FTP/streaming trafc, and any other type of trafc. This separation may be provided by VLANs
or by using separate switches/fabrics.
• Inter Switch Links — Only control trafc and FTP trafc use ISLs. Media (iSCSI) trafc does
not use ISLs.
• VLAN — When building VLANs on connected switches, common VLANs must have the same
VLAN number. Never use VLAN 1 for anything other than the native VLAN.
• Trunks — Trunks must use LACP and must be tagged.
• Protocols — When integrating multiple switches, the spanning tree protocol must be MSTP. The
routing protocol must be RIP.
• Port security — Do not use port security.
• IGMP — Enable IGMP snooping on the control network and on the corporate LAN, to support
the low-resolution live streaming trafc generated by K2 Summit systems.
Default Ethernet switch design
A K2 SAN system that ships from Grass Valley with self-contained networks is described as follows.
This network and switch conguration meets the K2 SAN Ethernet switch requirements:
• Switches are HP ProCurve.
• A non-redundant K2 SAN has a single switch. Redundant K2 SANs have at least two switches
to support an “A” media network and a “B” media network.
• There are three 1 Gig Inter-Switch Links (ISLs) between redundant switches. This is the default
conguration for all K2 SANs and provides sufcient bandwidth for most FTP trafc loads.
• The ISLs are congured as a trunk using LACP. Trunk ports are labeled Trk1.
• Each switch has two VLANs, with half the switch’s ports on each VLAN. The media (iSCSI)
trafc uses one VLAN and all other trafc uses the other VLAN. This “other” trafc can include
both FTP and control trafc, as it is allowed that they be on the same VLAN.
• The control/FTP VLAN ID is 10. The media VLAN IS is 60.
• IGMP Snooping is enabled on the control/FTP VLAN, to support low-resolution live streaming.
• Even numbered ports are control/FTP VLAN. Odd numbered ports are media VLAN.
2014 01 27 K2 SAN Installation and Service Manual 63
Page 64
Setting up the K2 SAN infrastructure
• The SNMP community name is public and RW permissions are unrestricted. SNMP trap
authentication is enabled.
• Spanning Tree is enabled.
• If a 10 Gig SFP+ port on the back of the switch connects to a K2 Media Server (FSM) for media
(iSCSI) trafc, the port is in the media VLAN. If a 10 Gig SFP+ port connects to a NH10GE K2
Media Server for FTP trafc, the port is in the control/FTP VLAN.
• If enough “control” ports (non-iSCSI ports) are available on a switch or switches congured for
an online K2 SAN, the Nearline system can be connected to those control ports. It is not required
that a GigE switch be dedicated to the Nearline system.
Design considerations for Ethernet switches
Extended network and switch congurations are available upon consultation with Grass Valley.
Guidelines are as follows:
• Port count— The numberof client connections, FTP/streaming connections, andother connections
determine how many ports are required. As the port count increases, you must use switches with
more ports and/or multiple switches. When multiple switches are used, the port count assigned
to each VLAN and the ports used for ISLs must be considered.
• Switch/fabric design — On large multiple switch systems, designers with sufcient knowledge
have options for the separation of iSCSI trafc. For example, you can use one switch/fabric for
media trafc, one switch/fabric for control trafc, and one switch/fabric for FTP trafc.
• You can trunk up to ten Cisco ports and four HP ports together, as necessary for your switch
design.
• FTP bandwidth — This is a consideration if using multiple switches that share the FTP trafc.
In this case you must use sufcient ISLs to provide the bandwidth needed to support your FTP
trafc load between switches. FTP trafc is variableand has potentially higherbandwidth needs,
it is the primary consideration when designing ISLs. When using 1 Gig connections for ISLs,
connect and congure as follows, taking your FTP bandwidth into consideration:
Trunk/ISLs requiredMaximum FTP bandwidth
A trunk with three 1 Gb/s ISLsLess than 100 MB/sec
A trunk with ve 1 Gb/s ISLs100 - 300 MB/sec
A trunk with two 10 Gb/s ISLsMore than 300 MB/sec
NOTE: One Gig ISLs must be an odd number (3 or 5).
If a switch's 10 Gig connections are not used for other purposes, such as connection to a K2
Media Server, you can use the 10 Gig connections for ISLs.
Configuring a switch through the K2Config application
In the K2 System Conguration (K2Cong) application , features for working on a Ethernet switch
are as follows:
64 K2 SAN Installation and Service Manual 2014 01 27
Page 65
From the K2Cong application, you can click the Configure Switch button to open the switch’s web
conguration application. Refer to the installation procedures elsewherein this document for switch
conguration information.
Configuring QOS on the GigE switch
Prerequisites for this procedure are as follows:
• The switch is HP ProCurve switch 29xx series.
• Trunks, VLANs and all other conguration is complete.
• The switch has an IP address
• You have network access to the switch
Setting up the K2 SAN infrastructure
Use this procedure to make the Quality of Service (QOS) setting on the HP ProCurve switch 29xx
series.
1. If you have not already done so, from a network connected PC open the MS-DOS command
prompt and login to the switch as administrator, as follows:
a) Telnet to the switch. For example, if the switch’s IP address is 192.168.40.12, you type the
following, then press Enter.
telnet 192.168.40.12
b) Press Enter one or more times until the switch’s username prompt appears.
c) Type the switch’s administrator username and press Enter, then type the switch’s administrator
password and press Enter. The switch console command (CLI) prompt appears.
2. Type the following, then press Enter:
config
You are now in conguration mode.
3. Type the following, then press Enter:
qos queue-cong 2-queues
This limits the number of active queues within the switch giving the most buffering to VLANs
1 and 60
2014 01 27 K2 SAN Installation and Service Manual 65
Page 66
Setting up the K2 SAN infrastructure
4. Type the following, then press Enter:
show qos vlan
The screen displays VLAN information. Note the ID number of the Media (iSCSI) VLAN. It
should be 60, as follows:
VLAN priorities
VLAN ID Apply rule | DSCP Priority
------- ----------- + ------ ---------- 1 No-override | No-override
60 No-override | No-override
5. a) Assign the Media VLAN the QOS priority of 3. For example, if the VLAN ID is 60, you type
the following, then press Enter.
vlan 60 qos priority 3
b) Type the following, then press Enter:
show qos vlan
The screen displays VLAN information. Make sure that the Priority column reports that the
Media VLAN has a value of 3.
Next, verify ow control settings.
Upgrading firmware on HP switch
1. If you have not already done so, install a TFTP Server.
For example, to install tftpd32.exe, go to http://tftpd32.jounin.net/.
2. Open the TFTP Server.
3. Make sure your current working directory includes the *.swi le that you are using for the
upgrade.
4. Execute the copy command with the following syntax:
copy tftp flash <ip-address> <remote-os-file> [ < primary | secondary
> ]
Note that if you do not specify the ash destination, the TFTP download defaults to the primary
ash.
For example, to download a software le named T_13_23.swi from a TFTP server with the IP
address of 10.16.34.3 1, use the following:
ProCurve # copy tftp flash 10.16.34.3 T_13_23.swi
5. When prompted The primary OS image will be deleted. continue [y/n]?, press
Y.
When the switch nishes downloading the software le from the server, it displays the progress
message Validating and Writing System Software to FLASH...
6. Wait until the CLI prompt re-appears, then continue with the next step in this procedure.
66 K2 SAN Installation and Service Manual 2014 01 27
Page 67
7. Check the version of rmware on the switch. To do this, type the following, then press Enter:
show flash
Information is displayed similar to the following example:
HP_iSCSI_switch1# show flash
Image Size(Bytes) Date Version
----- ---------- -------- ------Primary Image : 6737518 07/25/08 T.13.23
Secondary Image : 5886358 10/26/06 T.11.12
Boot Rom Version: K.12.12
Current Boot : Primary
8. Verify that the new software version is in the expected ash area (primary or secondary).
9. Restart the switch from the ash area that holds the new software (primary or secondary).
Setting up the control point PC
To set up the Control Point PC, you have the following options:
• Use the Grass Valley Control Point PC that comes from the factory with software pre-installed.
• Use a PC that you own and install the required software.
Setting up the K2 SAN infrastructure
1. For either option, you must do the following for the Control Point PC that runs the K2 System
Conguration application:
a) Assign a control network IP address to the PC.
b) Connect the PC to the GigE control network.
2. To use your own PC, you must additionally do the following:
a) Verify that the PC meets system requirements.
b) Install the K2 Control Point software.
c) Install SiteCong software.
d) Install other supporting software.
e) Install and license SNMP Manager software. This can be on the K2 SAN control point PC
or on a separate SNMP Manager PC that monitors the K2 SAN.
Refer to related topics aboutGrass Valley recommendeddeployment and monitoringsolutions
in "K2 Release Notes".
Install SiteConfig on control point PC
Work through the following topics to install the SiteCong application on the control point PC.
About installing SiteConfig
SiteCong uses a protocol that involves sending Ethernet broadcast messages to discover and
congure devices. To enable this protocol to work correctly, there must be unrestricted network
access between the PC that hosts SiteCong and the devices to be discovered.
This is achieved if control network interfaces are all connected to the same switch or to multiple
switches interconnected with ISLs/trunks. If your site requires that other switches and/or routers be
2014 01 27 K2 SAN Installation and Service Manual 67
Page 68
Setting up the K2 SAN infrastructure
in the network path, you must make sure that no restrictions are in place that block SiteCong
protocols.
Also, do not install SiteCong on a PC on which a drive from a managed device is mapped as an
administrative share (C$). For example, if you have a PC set up to run anti-virus software and for
this purpose you have network drives set up on the PC mapped to C$ shares on devices, then do not
use that PC to host SiteCong and manage those devices.
For a given system, there should be just one instance of SiteCong managing the system.
System requirements for SiteConfig host PC
The PC on which SiteCong is installed must meet the following requirements:
CommentsRequirements
Operating system
Java JRE
Installing/upgrading SiteConfig
Microsoft Windows (Must be a U.S. version):
• XP Professional Service Pack 3
• Server 2003
• Vista Enterprise Service Pack 1
• Windows 7
• Server 2008 R2
Minimum 512 MB, 1 GB recommendedRAM
Must have at least 128 MB memoryGraphics acceleration
Pentium 4 or higher class, 2 GHz or greaterProcessor
400 MBHard disk space
Version 4.0Microsoft .NET Framework
1.3.1_12 and 1.4.2_05 or higher. Required for
the HP Ethernet Switch conguration interface,
which is used for K2 SANs.
Microsoft XML 4 Service Pack 2 is required.XML
Prerequisites:
• The PC on which you are installing SiteConfg meets system requirements.
• The PC is connected to the LAN on which all the devices to be managed are connected.
• There are no routed paths to the devices to be managed.
1. Procure SiteCong installation les from the Grass Valley website or via other distribution
mechanisms.
The following directory and les are required to install SiteCong:
• DotNetFx directory
• ProductFrameUISetup.msi
• setup.exe
68 K2 SAN Installation and Service Manual 2014 01 27
Page 69
Setting up the K2 SAN infrastructure
2. If you already have a version of SiteCong installed, go to Windows Add/Remove Programs and
uninstall it.
3. Double-click setup.exe.
The installation wizard opens.
4. Work through the wizard pages, clicking Next and Finish.
If the PC does not have the appropriate version of Microsoft .NET, the SiteCong installation
programs installs it.
5. Open the Windows operating system Services control panel on the PC and look for an entry
called " ProductFrame Discovery Agent".
The Discovery Agent must be installed on the SiteCong PC so that the PC can be discovered
by SiteCong and added to the system description as a managed device. This is necessary to
ensure name resolution in SiteCong's hosts le.
The Discovery Agent is also known as the Network Conguration Connect Kit. For example,
in Windows Add/Remove Programs, itcan be displayedas either Network Conguration Connect
Kit or SiteCong Discovery Agent.
6. Proceed as follows:
• If the Discovery Agent is not installed, navigate to the SiteCong install location's Discovery
Agent Setupsubdirectory and double-click the DiscoveryAgentServiceSetup.msi le. This
launches the setup program and installs the Discovery Agent. Follow the setup wizard to
complete installation. A restart is required after installation. Then continue with the next step
in this procedure.
• If the Discovery Agent is already installed, continue with the next step in this procedure.
2014 01 27 K2 SAN Installation and Service Manual 69
Page 70
Setting up the K2 SAN infrastructure
7. If not already congured, congure the SiteCong PC with a valid Ethernet IP address for the
LAN using Windows Network Connections.
8. If you are not going to be using SiteCong to manage system hosts les, put the system hosts
le on the SiteCong PC.
70 K2 SAN Installation and Service Manual 2014 01 27
Page 71
Planning and implementing a K2 SAN with SiteConfig
About developing a system description
You use SiteCong to create or modify a system description for the K2 SAN. You can do this in
your planning phase, even before you have devices installed or cabled. Your goal is to have the
SiteCong system description accurately represent all aspects of your devices and networks before
you begin actually implementing any networking or other conguration tasks.
There are several task ows you can take to develop a system description, as follows:
• Obtain the sales tool system description. This is the system description that was developed for
your specic K2 SAN as part of the sales process. It should be a very accurate representation of
the K2 SAN that is to be installed at the customer site. Import the system description into
SiteCong and then make nal modications.
• Obtain a similar K2 SAN's system description, import it into SiteCong, and then modify it until
it matches your K2 SAN.
• In SiteCong, use the New Site Wizard to create a new system description. The wizard has
models based on the pre-dened K2 SAN levels. You can enter much of your site-specic
information as you work through the wizard, and then do nal modications using other
SiteCong features.
The topics in this manual follow the task ow for the sales tool system description. If you are using
a different taskow, use the topics in this manual as appropriate and refer to the SiteCong User
Manual or SiteCong Help Topics for additional information.
Importing a system description
Prerequisites for this task are as follows:
• The SiteCong PC has access to the system description le you are importing.
• Windows Explorer Folder Options must be set to Show hidden les and folders in order to see
all the folders containing SiteCong les.
1. Open SiteCong and proceed as follows:
• If a dialog box opens that gives you the choice of creating or importing a system description,
it means SiteCong does not have access to a system description le. Click Import.
• If the SiteCong main window opens, click File | Import.
The Import System Description dialog box opens.
2. Browse to and select a system description le (*.scsd) and click Open.
2014 01 27 K2 SAN Installation and Service Manual 71
Page 72
Planning and implementing a K2 SAN with SiteCong
The current system description is closed and the system description you are importing is displayed
in SiteCong.
About device and host names
In SiteCong, a device can have different names, as follows:
• Device name — This is a name for display in SiteCong only. It is stored in the SiteCong
system description, but not written to the actual device. It is displayed in the device tree view
and in the device list view. It can be a different name than the device’s host name.
• Host name — This is the network nameof the device.SiteCong has a default naming convention
for host names which you can use or override with your own host names.
In most cases it is recommended that the Device name and Host name be the same. This avoids
confusion and aids troubleshooting.
The Device name can serve as a placeholder as a system is planned and implemented. During the
install/commission process, when you reconcile a device's current and planned network interface
settings, the Host name as congured in the system description can be overwritten by the host name
on the actual device. However, the Device name congured in the system description is notaffected.
Therefore it is recommended that in the early planned stages, you congure the Device name to be
the desired name for the device, but do not yet congure the Host name. Then, after you have applied
network interface settings, you can change the Host name to be the same as the Device name. This
changes the host name on the actual device so that then all names are in sync.
SiteCong does not allow duplicate device names or host names.
Items in the tree view are automatically sorted alphabetically, so if you change a name the item
might sort to a different position.
Modifying a device name
1. In the Network Configuration | Devices tree view, right-click a device and select Rename.
2. Type in the new name.
Note that this does not change the hostname on the physical device. If you want the hostname
to match the device name, you must also modify the hostname.
Modifying the control network
1. In the Network Configuration | Networks tree view, select the K2 SAN's Site node.
The networks under that node are displayed in the list view.
72 K2 SAN Installation and Service Manual 2014 01 27
Page 73
Planning and implementing a K2 SAN with SiteCong
2. Proceed as follows:
• In the list view, right-click the Control network and select Details.
The Network Settings dialog box opens.
2014 01 27 K2 SAN Installation and Service Manual 73
Page 74
Planning and implementing a K2 SAN with SiteCong
3. Congure the settings for the network as follows:
For control networkSetting...
Type
Usage
Redundancy
Name
Exclude from Host
Files
Managed
Base IP Address
Number of Addresses
Unmanaged
Ethernet is required
Control is required
None is required. This is true even on a redundant K2 SAN. (Only the
iSCSI network is redundant on a redundant K2 SAN.)
Control is recommended
Unselected is required
Selected is required
The rst (lowest) IP address in the range of IP addresses managed by
SiteCong. Required.
The number of IP addresses in the range managed by SiteCong.
Required.
The network's subnet mask. Required.Subnet Mask
Additional network settings managed by SiteCong. Allowed.Gateway IP Address
Unselected is required. Related settings are disabled.
Servers providing DNS for name resolution. Allowed.DNS Servers
Not allowedDefault Interface
Name Sufx
4. Click OK to save settings and close.
Modifying the FTP/streaming network
1. In the Network Configuration | Networks tree view, select the K2 SAN's Site node.
The networks under that node are displayed in the list view.
74 K2 SAN Installation and Service Manual 2014 01 27
Page 75
Planning and implementing a K2 SAN with SiteCong
2. Proceed as follows:
• In the list view, right-click the Streaming network and select Details.
The Network Settings dialog box opens.
2014 01 27 K2 SAN Installation and Service Manual 75
Page 76
Planning and implementing a K2 SAN with SiteCong
3. Congure the settings for the network as follows:
For FTP/streaming networkSetting...
Type
Usage
Redundancy
Name
Exclude from Host
Files
Managed
Base IP Address
Number of Addresses
Unmanaged
Ethernet is required
FileTransfer is required
None is required. This is true even on a redundant K2 SAN. (Only the
iSCSI network is redundant on a redundant K2 SAN.)
Streaming is recommended
Unselected is required
Selected is required
The rst (lowest) IP address in the range of IP addresses managed by
SiteCong. Required.
The number of IP addresses in the range managed by SiteCong.
Required.
The network's subnet mask. Required.Subnet Mask
Additional network settings managed by SiteCong. Allowed.Gateway IP Address
Unselected is required. Related settings are disabled.
Servers providing DNS for name resolution. Allowed.DNS Servers
Default Interface
Name Sufx
4. Click OK to save settings and close.
_he0 is required
Modifying a media (iSCSI) network
1. In the Network Configuration | Networks tree view, select the K2 SAN's Site node.
The networks under that node are displayed in the list view.
76 K2 SAN Installation and Service Manual 2014 01 27
Page 77
Planning and implementing a K2 SAN with SiteCong
2. Proceed as follows:
• If the K2 SAN is basic (non-redundant), in the list view, right-click the iSCSI network and
select Details.
• If the K2 SAN is redundant, in the list view, rst right-click the primary iSCSI network and
select Details. Then proceed to modify the primary iSCSI network. After the primary iSCSI
network is modied, repeat these steps and modify the secondary iSCSI network.
The Network Settings dialog box opens.
2014 01 27 K2 SAN Installation and Service Manual 77
Page 78
Planning and implementing a K2 SAN with SiteCong
3. Congure the settings for the network as follows:
For media (iSCSI) networkSetting...
Type
Usage
Redundancy
Name
Exclude from Host
Files
Managed
Base IP Address
Number of Addresses
Ethernet is required
StorageNetworking is required
None is required for a basic (non-redundant) K2 SAN
Primary is required for a redundant K2 SAN media network A
Secondary is required for a redundant K2 SAN media network B
iSCSI (non-Redundant) is recommended for a basic (non-redundant) K2
SAN
iSCSI (Primary Redundant) is recommended for a redundant K2 SAN
media network A
iSCSI (Secondary Redundant) is recommended for a redundant K2 SAN
media network B
Selected is required
Selected is required
The rst (lowest) IP address in the range of IP addresses managed by
SiteCong. Required.
The number of IP addresses in the range managed by SiteCong.
Required.
The network's subnet mask. Required.Subnet Mask
Not allowedGateway IP Address
Unmanaged
Name Sufx
4. Click OK to save settings and close.
Unselected is required. Related settings are disabled.
Not allowedDNS Servers
Not allowedDefault Interface
About IP configuration of network interfaces on devices
You can perform IP conguration of network interfaces when working with a placeholder device
prior to discovery. When you add a device and choose a particular model, the model denes the
number, type and usage characteristics of network interfaces to expect on such a device.
You can view and edit each network interface and set up IP conguration selecting an appropriate
IP from the network to which each interface connects. The process for editing IP conguration
varies, depending on the device's phase.
78 K2 SAN Installation and Service Manual 2014 01 27
Page 79
Placeholder device IP configuration
On a placeholder device, you edit network interfaces using the Unmanaged Network Interfaces
dialog box.
Planning and implementing a K2 SAN with SiteCong
The Unmanaged Network Interfaces dialog box allows you only to save changes to the system
description.
Discovered device IP configuration
On a discovered device, you edit network interfaces using the Managed Network Interfaces dialog
box.
2014 01 27 K2 SAN Installation and Service Manual 79
Page 80
Planning and implementing a K2 SAN with SiteCong
The Managed Network Interfaces dialog box allows you to edit and save changes to the device.
Modifying K2 client unassigned (unmanaged) interface
Prerequisites for this task are as follows:
• The system description has a SAN K2 client that is a placeholder device.
• The placeholder device has a one or more unmanaged network interfaces.
Use this task to modify unmanaged network interfaces on a K2 SAN device as follows:
• K2 Summit Production Client
1. In the Network Configuration | Devices tree view, select a SAN K2 client placeholder device.
The interfaces for that device are displayed in the interfaces list view.
80 K2 SAN Installation and Service Manual 2014 01 27
Page 81
Planning and implementing a K2 SAN with SiteCong
2. In the interfaces list view, right-click an interface and select Edit.
The Unmanaged Network Interface Details dialog box opens.
2014 01 27 K2 SAN Installation and Service Manual 81
Page 82
Planning and implementing a K2 SAN with SiteCong
3. Congure the settings for the interface as follows:
For control network interfaceSetting...
Network
Set to Default
...use Interface
Name/Aliases in
Host Files...
DNS Sufx
Network
Control is required
The IP address for this interface on the network. Required.IP Address
The device host name. Required.Interface Name
Not recommended.Sets the interfacename to SiteCong default convention,
based on the root Site name and device-type.
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts le.
Not allowedAliases
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
For media (iSCSI) network interfaceSetting...
iSCSI (non-Redundant) is required for one iSCSI interface on a K2 client
on a basic K2 SAN. The other iSCSI interface is unused.
iSCSI (Primary Redundant) is required forone iSCSI interfaceon a K2 client
on a redundant K2 SAN.
iSCSI (Secondary Redundant) is required for the other iSCSI interface on a
K2 client on a redundant K2 SAN
The IP address for this interface on the network. Required.IP Address
Disabled, since names are excluded from the hosts le. Disregard.Interface Name
Disabled, since names are excluded from the hosts le. Disregard.Set to Default
Disabled, since names are excluded from the hosts le. Disregard....use Interface
Name/Aliases in
Host Files...
Disabled, since names are excluded from the hosts le. Disregard.Aliases
Disabled, since names are excluded from the hosts le. Disregard.DNS Sufx
NOTE: There is no FTP/streaming network for a SAN K2 client. On the K2 SAN,
FTP/streaming goes to the K2 Media Server.
4. Click OK to save settings and close.
Modifying K2 Media Server unassigned (unmanaged) interface
Prerequisites for this task are as follows:
• The system description has a K2 Media Server that is a placeholder device.
82 K2 SAN Installation and Service Manual 2014 01 27
Page 83
Planning and implementing a K2 SAN with SiteCong
• The placeholder device has a one or more unmanaged network interfaces.
Use this task to modify managed network interfaces on a K2 SAN device as follows:
• K2 Media Server
• NH K2 Media Server
For the K2 Media Server, do not congure the Fibre Channel interface. SiteCong does not manage
this interface. It is represented in SiteCong only to complete the description of the K2 Media
Server.
1. In the Network Configuration | Devices tree view, select a K2 Media Server placeholder device.
The interfaces for that device are displayed in the interfaces list view.
2. In the interfaces list view, right-click an interface and select Edit.
The Unmanaged Network Interface Details dialog box opens.
2014 01 27 K2 SAN Installation and Service Manual 83
Page 84
Planning and implementing a K2 SAN with SiteCong
3. Congure the settings for the interface as follows:
For control network interfaceSetting...
Network
Set to Default
...use Interface
Name/Aliases in
Host Files...
DNS Sufx
Network
Interface Name
Control is required
The IP address for this interface on the network. Required.IP Address
The device host name. Required.Interface Name
Not recommended.Sets the interfacename to SiteCong default convention,
based on the root Site name and device-type.
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts le.
Not allowedAliases
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
For FTP/streaming network interfaceSetting...
Streaming is required
The IP address for this interface on the network. Required.IP Address
The device host name with the " _he0" sufx added is required. For example,
if the host name is K2prod01, then K2prod01_he0 is required here.
Set to Default
...use Interface
Name/Aliases in
Host Files...
DNS Sufx
Network
Not recommended.Sets the interfacename to SiteCong default convention,
based on the root Site name and device-type.
Selected is required
Not allowedAliases
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
For media (iSCSI) network interfaceSetting...
iSCSI (non-Redundant) is required on K2 Media Server for all interfaces of
type iSCSI on basic K2 SAN.
iSCSI (Primary Redundant) is required on K2 Media Server A for all
interfaces of type iSCSI on redundant K2 SAN
iSCSI (Secondary Redundant) is required on K2 Media Server B for interfaces
of type iSCSI on redundant K2 SAN
The IP address for this interface on the network. Required.IP Address
Disabled, since names are excluded from the hosts le. Disregard.Interface Name
84 K2 SAN Installation and Service Manual 2014 01 27
Page 85
Planning and implementing a K2 SAN with SiteCong
For media (iSCSI) network interfaceSetting...
Disabled, since names are excluded from the hosts le. Disregard.Set to Default
Disabled, since names are excluded from the hosts le. Disregard....use Interface
Name/Aliases in
Host Files...
Disabled, since names are excluded from the hosts le. Disregard.Aliases
Disabled, since names are excluded from the hosts le. Disregard.DNS Sufx
4. Click OK to save settings and close.
About SiteConfig support on K2 devices
Before SiteCong can be used to discover or manage a device, the device must meet the following
requirements:
• The device must be a Microsoft Windows operating system device.
• The device must have Microsoft .NET version 3.5 installed, as reported in the Windows
Add/Remove Programs control panel.
• The SiteCong Discovery Agent service must be running on the device, as reported in the
Windows Services control panel.
For K2 clients and K2 Media Servers shipped new from Grass Valley with K2 software version 7.0
or higher, these requirements are pre-installed. These requirements are pre-installed on recovery
images for these K2 systems as well. Therefore, if you suspect a problem with these requirements,
do not attempt to install SiteCong support requirements. If you must restore SiteCong support
requirements, re-image the K2 system.
Discovering devices with SiteConfig
Prerequisites for this task are as follows:
• The Ethernet switch or switches that support the control network are congured and operational.
If multiple switches, ISLs are connected and trunks congured.
• The PC that hosts SiteCong is communicating on the control network.
• There are no routers between the PC that hosts SiteCong and the devices to be discovered.
• Devices to be discovered are Windows operating system devices, with SiteCong support
installed.
• Devices are cabled for control network connections.
• If discovering a device with Microsoft Windows Server 2008 operating system, the device must
have an IP address, either static or DHCP supplied.
1. Open SiteCong.
2014 01 27 K2 SAN Installation and Service Manual 85
Page 86
Planning and implementing a K2 SAN with SiteCong
2. In the toolbar, click the discover devices button.
The Discover Devices dialog box opens.
A list of discovered devices is displayed.
3. Click Rescan to re-run the discovery mechanism. You can do this if a device that you want to
discover hasits network connection restored or otherwise becomes available.Additional devices
discovered are added to the list.
Assigning discovered devices
Prerequisites for this task are as follows:
• Devices have been discovered by SiteCong
• Discovered devices are not yet assigned to a device in the system description
• The system description has placeholder devices to which to assign the discovered devices.
1. If the Discovered Devices Dialog box is not already open, click the discover devices button .
The Discover Devices dialog box opens.
2. Identify discovered devices.
• If a single device is discovered in multiple rows, it means the device has multiple network
interfaces. Choose the interface that represents the device's currently connected control
connection. This is typically Ethernet ... 0.
• If necessary, select a device in the list and click ID Device. This triggers an action on the
device, such as ashing an LED or ejecting a CD drive, to identify the device.
86 K2 SAN Installation and Service Manual 2014 01 27
Page 87
Planning and implementing a K2 SAN with SiteCong
3. To also view previously discovered devices that have already been assigned to a device in the
system description, select Show … currently assigned devices.
The currently assigned devices are added to the list. Viewing both assigned and unassigned
devices in this way can be helpful to verify the match between discovered devices and placeholder
devices.
4. In the row for each discovered device, view items on the Device Id drop-down list to determine
the match with placeholder devices, as follows:
• If SiteCong nds a match between the device-type discovered and the device-type of one
or more placeholder devices, it displays those placeholder devices in the list.
• If SiteCong does not nd a match between the device-type discovered and the device-type
of a placeholder device, no placeholder device is displayed in the list.
5. In the row for a discovered device, click the Device Id drop-down list and select the placeholder
device that corresponds to the discovered device.
If there is no corresponding placeholder device currently in the system description, you can select
Add to create a new placeholder device and then assign the discovered device to it.
6. When discovered devices have been assigned, click OK to save settings and close.
7. In the Network Configuration | Devices tree view, select each of the devices to which you assigned
a discovered device.
Modifying K2 client managed network interfaces
Prerequisites for this task are as follows:
• The physical device you are conguring has been discovered and is assigned to a device in the
SiteCong system description.
• SiteCong has communication with the device.
• The device is dened in the system description with an appropriate network interface.
Use this task to modify managed network interfaces on a K2 SAN device as follows:
• K2 Summit Production Client
1. In the tree view select a K2 client, then in the Interfaces list view, identify interfaces as follows:
• The SAN K2 client's control interface is a team. Modify the control team interface rst. The
control team is comprised of two individual interfaces, one for Control Connection #1 and
one for Control Connection # 2. Do not modify these two individual interfaces.
• For a SAN K2 client on a basic (non-redundant) K2 SAN, identify the iSCSI (non-Redundant)
interface. After the control team, modify this interface as instructed in this procedure. Do not
congure any other iSCSI interface, as only one iSCSI interface is used for a basic K2 SAN.
• For a SAN K2 clienton a redundantK2 SAN, identifythe iSCSI (Primary Redundant) interface
and the iSCSI (Primary Secondary) interface. After the control team, modify these interfaces
as instructed in this procedure.
• The SAN K2 client has no interface for FTP/streaming. All FTP/streaming goes to the K2
Media Server.
2014 01 27 K2 SAN Installation and Service Manual 87
Page 88
Planning and implementing a K2 SAN with SiteCong
2. In the Interfaces list view determine the interface to congure, as follows:
• Identify the interface with which SiteCong is currently communicating, indicated by the
green star overlay icon. This should be the control network interface.
• Verify that the interface over which SiteCong is currently communicating is in fact the
interface dened for the control network in the system description. If this is not the case, you
might have the control network cable connected to the wrong interface port. The control
connection should always be the rst port on the motherboard, except when you have a
loopback connection.
• Congure the control network interface rst before conguring any of the other interfaces.
• After you have successfully congured the control network interface, return to this step to
congure each remaining interface.
3. In the Interfaces list view, check the icon for the interface you are conguring.
If the icon has a red stop sign overlay, it indicates that current settings and planned settings do
not match or that there is some other problem. Hover over the icon to read a tooltip with
information about the problem.
4. In the Interfaces list view, right-click the interface you are conguring and select Edit.
The Managed Network Interface Details dialog box opens.
88 K2 SAN Installation and Service Manual 2014 01 27
Page 89
Planning and implementing a K2 SAN with SiteCong
5. Identify the interface on the discovered device that you are conguring.
• Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection
name. SiteCong reads this name from the device and displays it at the top of this dialog box.
This is the most accurate way to identify the network adapter on the discovered device that
you are conguring.
6. Congure naming settings as follows:
For network interface Control TeamSetting...
The device host name. Required.Interface Name
Not recommendedSet To Default
DNS Sufx
Use Interface
Name/Aliases in
Host Files
Interface Name
Use Interface
Name/Aliases in
Host Files
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
Not allowedAliases
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts le.
For any network interface of type iSCSISetting...
"Unused" is recommended. Displaying this text here serves as an aid in
understanding SAN networks.The iSCSI network has no name resolution
via the hosts le or otherwise, so the text you enter here is not actually use
for name resolution.
Not recommendedSet To Default
Not allowedDNS Sufx
Not allowedAliases
Selected is recommended. Since this interface’s network has its names
excluded from the hosts le, this setting has no affect. The interface name
is excluded from the hosts le, regardless of settings here.
NOTE: There is no FTP/streaming network for a SAN K2 client. On the K2 SAN,
FTP/streaming goes to the K2 Media Server.
7. Evaluate settings on the Planned tab and change if necessary.
• Compare settings on the Planned tab with settings on the Current tab.
• If you want to keep the current settings as reported in the Current tab, click Remove to remove
the planned settings.
• Do not specify multiple IP addresses for the same interface. Do not use the Add button.
2014 01 27 K2 SAN Installation and Service Manual 89
Page 90
Planning and implementing a K2 SAN with SiteCong
8. To modify planned settings, do the following:
a) Select the network settings and click Edit.
The Edit IP Address dialog box opens.
b) Edit IP address settings as follows:
For network interface Control TeamSetting...
Network
Address Allocation
Control is required
Static is recommended.
The IP address for this interface on the network. Required.IP Address
For basic SAN network interface Media Connection #1Setting...
Network
Address Allocation
iSCSI (non-Redundant) is required
Static is required.
The IP address for this interface on the network. Required.IP Address
For redundant SAN network interface Media Connection #1Setting...
Network
Address Allocation
iSCSI (Primary Redundant) is required
Static is required.
The IP address for this interface on the network. Required.IP Address
For redundant SAN network interface Media Connection #2Setting...
Network
Address Allocation
iSCSI (Secondary Redundant) is required
Static is required.
The IP address for this interface on the network. Required.IP Address
90 K2 SAN Installation and Service Manual 2014 01 27
Page 91
Planning and implementing a K2 SAN with SiteCong
The networks listed in the Edit IP Address dialog box are those currently dened in the system
description, with available settings restricted according to the network denition. If you
require settings that are not available, you can close dialog boxes and go to the Network
Configuration | Networks tab to modify network settings, then return to the Edit IP Address
dialog box to continue.
9. When you have veried that the planned settings are correct, click OK, then Yes to apply settings
to the device and close.
A Contacting Device message box reports progress.
10. After conguring control network settings, do the following
a) If a message informs you of a possible loss of communication, click OK.
This message is normal, since this is the network over which you are currently communicating.
b) In the Device list view, observe the device icon and wait until the icon displays the green star
overlay before proceeding.
The icon might not display the green star overlay for several seconds as settings are
recongured and communication is re-established.
c) In the Interface list view, right-click the interface and select Ping.
The Ping Host dialog box opens.
If ping status reports success, the interface is communicating on the control network.
Modifying K2 Media Server managed network interfaces
Prerequisites for this task are as follows:
• The physical device you are conguring has been discovered and is assigned to a device in the
SiteCong system description.
• SiteCong has communication with the device.
• The device is dened in the system description with an appropriate network interface.
Use this task to modify managed network interfaces on a K2 SAN device as follows:
• K2 Media Server
2014 01 27 K2 SAN Installation and Service Manual 91
Page 92
Planning and implementing a K2 SAN with SiteCong
• NH K2 Media Server
1. In the Interfaces list view determine the interface to congure, as follows:
• Identify the interface with which SiteCong is currently communicating, indicated by the
green star overlay icon. This should be the control network interface.
• Verify that the interface over which SiteCong is currently communicating is in fact the
interface dened for the control network in the system description. If this is not the case, you
might have the control network cable connected to the wrong interface port. The control
connection should always be the rst port on the motherboard, except when you have a
loopback connection.
• Congure the control network interface rst before conguring any of the other interfaces.
• After you have successfully congured the control network interface, return to this step to
congure each remaining interface.
• For the K2 Media Server, do not congure the Fibre Channel interface, which is a non-IP
interface. SiteCong does not manage this interface. It is represented in SiteCong only to
complete the description of the K2 Media Server.
2. In the Interfaces list view, check the icon for the interface you are conguring.
If the icon has a red stop sign overlay, it indicates that current settings and planned settings do
not match or that there is some other problem. Hover over the icon to read a tooltip with
information about the problem.
92 K2 SAN Installation and Service Manual 2014 01 27
Page 93
Planning and implementing a K2 SAN with SiteCong
3. In the Interfaces list view, right-click the interface you are conguring and select Edit.
The Managed Network Interface Details dialog box opens.
4. Identify the interface on the discovered device that you are conguring.
• Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection
name. SiteCong reads this name from the device and displays it at the top of this dialog box.
This is the most accurate way to identify the network adapter on the discovered device that
you are conguring.
• Identify iSCSI adapters by their "Type".
2014 01 27 K2 SAN Installation and Service Manual 93
Page 94
Planning and implementing a K2 SAN with SiteCong
5. Congure naming settings as follows:
For network interface Control ConnectionSetting...
The device host name. Required.Interface Name
Not recommendedSet To Default
DNS Sufx
Use Interface
Name/Aliases in
Host Files
DNS Sufx
Use Interface
Name/Aliases in
Host Files
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
Not allowedAliases
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts le.
For network interface FTP ConnectionSetting...
The device host name with the "_he0" sufx added is required.Interface Name
Not recommendedSet To Default
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
Not allowedAliases
Selected is required
For any network interface of type iSCSISetting...
Interface Name
The text "Unused" is recommended. Displaying this text here serves as an
aid in understanding SAN networks.The iSCSI network has no name
resolution via the hosts le or otherwise, so the text you enter here is not
actually use for name resolution.
Not allowedSet To Default
Not allowedDNS Sufx
Not allowedAliases
Use Interface
Name/Aliases in
Host Files
Selected is recommended. Since this interface’s network has its names
excluded from the hosts le, this setting has no affect. The interface name
is excluded from the hosts le, regardless of settings here.
6. Evaluate settings on the Planned tab and change if necessary.
• Compare settings on the Planned tab with settings on the Current tab.
• If you want to keep the current settings as reported in the Current tab, click Remove to remove
the planned settings.
• Do not specify multiple IP addresses for the same interface. Do not use the Add button.
94 K2 SAN Installation and Service Manual 2014 01 27
Page 95
Planning and implementing a K2 SAN with SiteCong
7. To modify planned settings, do the following:
a) Select the network settings and click Edit.
The Edit IP Address dialog box opens.
b) Edit IP address settings as follows:
For network interface Control ConnectionSetting...
Network
Address Allocation
Control is required
Static is recommended.
The IP address for this interface on the network. Required.IP Address
For network interface FTP ConnectionSetting...
Network
Address Allocation
Streaming is required
Static is required.
The IP address for this interface on the network. Required.IP Address
For basic SAN K2 Media Server any network interface of type iSCSISetting...
Network
Address Allocation
iSCSI (non-Redundant) is required
Static is required.
The IP address for this interface on the network. Required.IP Address
Setting...
For redundant SAN K2 Media Server A any network interface of type
iSCSI
Network
Address Allocation
2014 01 27 K2 SAN Installation and Service Manual 95
iSCSI (Primary Redundant) is required
Static is required.
Page 96
Planning and implementing a K2 SAN with SiteCong
Setting...
For redundant SAN K2 Media Server A any network interface of type
iSCSI
The IP address for this interface on the network. Required.IP Address
Setting...
Network
Address Allocation
For redundant SAN K2 Media Server B any network interface of type
iSCSI
iSCSI (Secondary Redundant) is required
Static is required.
The IP address for this interface on the network. Required.IP Address
The networks listed in the Edit IP Address dialog box are those currently dened in the system
description, with available settings restricted according to the network denition. If you
require settings that are not available, you can close dialog boxes and go to the Network
Configuration | Networks tab to modify network settings, then return to the Edit IP Address
dialog box to continue.
8. When you have veried that the planned settings are correct, click OK, then Yes to apply settings
to the device and close.
A Contacting Device message box reports progress.
9. After conguring control network settings, do the following
a) If a message informs you of a possible loss of communication, click OK.
This message is normal, since this is the network over which you are currently communicating.
b) In the Device list view, observe the device icon and wait until the icon displays the green star
overlay before proceeding.
The icon might not display the green star overlay for several seconds as settings are
recongured and communication is re-established.
c) In the Interface list view, right-click the interface and select Ping.
The Ping Host dialog box opens.
If ping status reports success, the interface is communicating on the control network.
Making the host name the same as the device name
1. Verify that the current device name, as displayed in the SiteCong tree view, is the same as your
desired host name.
2. In the Network Configuration | Devices | Device list view, right-click the device and select Edit.
The Edit Device dialog box opens.
3. Identify the state of buttons as follows:
• If the host name is different than the device name, the Set to Device Name button is enabled.
• If the host name is the same as the device name, the Set to Device Name button is disabled.
96 K2 SAN Installation and Service Manual 2014 01 27
Page 97
Planning and implementing a K2 SAN with SiteCong
4. If enabled, click Set to Device Name.
This changes the host name to be the same as the device name.
5. Click OK.
6. When prompted, restart the device.
Pinging devices from the PC that hosts SiteConfig
Prerequisites:
• The devices you are pinging are in the SiteCong system description.
You can send the ping command to one or more devices in the system description over the network
to which the SiteCong host PC is connected. Typically this is the control network.
1. In the Network Configuration | Networks tree view, select a network, site, or system node.
2. In the Devices list view, select one or more devices. Use Ctrl + Click or Shift + Click to select
multiple devices.
3. Right-click the selected device or devices and select Ping.
The Ping Devices dialog box opens and lists the selected device or devices.
The Ping Devices dialog box reports the progress and results of the ping command per device.
About hosts files and SiteConfig
SiteCong uses the network information in the system description to dene a hosts le and allows
you to view the hosts le. SiteCong can manage this hosts le on Windows operating system
devices that are in the system description and that are part of a SiteCong managed network.
When you have successfully assigned devices and applied planned network settings to interfaces,
it isan indication that host table information, as currently captured in the system description, is valid
and that you are ready to have SiteCong assemble the host table information into a hosts le. Your
options for placing this host table information on devices are as follows:
• If you do not want SiteCong to manage your hosttable information, you can manage it yourself.
This is typically the case if your facility has an existing hosts le that contains host table
information for devices that are not in the SiteCong system description. In this case, you can
have SiteCong generate a single hosts le that contains the host table information for the devices
in the system description. You can then copy the desired host table information out of the
SiteCong hosts le and copy it into your facility hosts le. You must then distribute your facility
hosts le to devices using your own mechanisms.
• If you want SiteCong to manage all information in hosts les on devices, you can have
SiteCong copy its hosts le to devices. In so doing, SiteCong overwrites the existing hosts
les on devices. Therefore, this requires that all devices that have name resolution through the
hosts le be congured accordingly in the SiteCong system description.
If you choose to have SiteCong write hosts les to devices, the process consumes system resource
and network bandwidth. Therefore you should wait until you have veried the information for all
devices/interfaces inthe host le, rather than updating hosts les incrementally as you discover/assign
devices.
2014 01 27 K2 SAN Installation and Service Manual 97
Page 98
Planning and implementing a K2 SAN with SiteCong
SiteCong does not automatically deploy hosts les to managed devices as you add or remove
devices. Ifyou add or remove devices from the system description, you must re-deploy the modied
hosts le to all devices.
Generating host tables using SiteConfig
Prerequisites for this task are as follows:
• Planned control network settings are applied to control network interfaces and devices are
communicating on the control network as dened in the system description.
• Interfaces for networks that require name resolution via the hosts le, such as the FTP/streaming
network, have settings applied and are communicating.
• You have viewed host names, as currently dened in the system description, and determined
that they are correct.
• The SiteCong PC is added to the system description so that it is included in the host tables
generated by SiteCong.
When you add or modify devices or their IP addresses in the SiteCong system description, you
should update host tables on all devices that use them.
1. In the Network Configuration | Networks tree view, select a network, site, or system node.
2. Click View Hosts file.
A Hosts File Contents window opens that displays the contents of the hosts le as currently
dened in the system description.
3. Verify the information in the hosts le.
98 K2 SAN Installation and Service Manual 2014 01 27
Page 99
Planning and implementing a K2 SAN with SiteCong
4. Do one of the following:
• If you are managing host table information yourself, click Save As and save a copy of the
hosts le to a location on the control point PC. Then open the copy of the hosts le, copy the
desired host table information from it, and paste it into your facility hosts leas desired. Then
you can use your own process to distribute the facility hosts le to devices. Remember to
distribute to the control point PC so that SiteCong and other management applications such
as K2Cong can resolve network host names.
• If SiteCong is managing hosts les, do the following:
NOTE: Writing hosts les to multiple devices consumes system resource and network
bandwidth. Therefore it is recommended that you wait and do this after the system is complete
and fully implemented, rather than updating hosts les incrementally as you discover/assign
devices.
a) In the Network Configuration | Devices | Devices list view, right-click a device to which you
intend to write the hosts le and select View Current Host File.
A Host File Contents window opens that displays the contents of the hosts le that is currently
on that actual device.
b) Verify that there is no information that you want to retain in the device’s current hosts le
that is not also in the hosts le as currently dened in the system description. If you need to
save the device's current hosts le, click Save As and save to a different location.
c) In the Network Configuration | Devices | Devices list view, right-click a device or use Ctrl +
Click to select multiple devices, and select Update Host File.
The current hosts le is overwritten with the hosts le as dened in the system description.
2014 01 27 K2 SAN Installation and Service Manual 99
Page 100
Planning and implementing a K2 SAN with SiteCong
100 K2 SAN Installation and Service Manual 2014 01 27
Loading...