8900NET
NETWORK INTERFACE MODULE
Instruction Manual
SOFTWARE VERSION 4.0.0
071061204
NOVEMBER 2005
Contacting Grass Valley
Region Voice Fax Address Web Site
North America (800) 547-8949
Support: 530-478-4148
Pacific Operations +852-2585-6688
Support: 852-2585-6579
U.K., Asia, Middle East +44 1753 218 777 +44 1753 218 757
France +33 1 45 29 73 00
Germany, Europe +49 6150 104 782 +49 6150 104 223
Copyright © Grass Valley. All rights reserved.
Grass Valley Web Site
The www.thomsongrassvalley.com web site offers the following:
Online User Documentation — Current versions of product catalogs, brochures,
data sheets, ordering guides, planning guides, manuals, and release notes
in .pdf format can be downloaded.
FAQ Database — Solutions to problems and troubleshooting efforts can be
found by searching our Frequently Asked Questions (FAQ) database.
Sales: (530) 478-3347
Support: (530) 478-3181
+852-2802-2996
Grass Valley
P.O. Box 599000
Nevada City, CA 95959-7900
USA
www.thomsongrassvalley.com
Software Downloads — Software updates, drivers, and patches can be down-
loaded.
2 8900NET Instruction Manual
Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8900NET Network Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8900NET Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Remote Control Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Basic Network Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Module Placement in the Gecko 8900 and Gecko Flex Frame . . . . . . . . . . . . . . . 9
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Frame Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RS-232 Communication Port Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8900NET Module Indicator LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Status Monitoring and Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Frame Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8900NET Module Alarm DIP Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Status Reporting Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
External Frame Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
SNMP Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Establishing Frame Network Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
NetConfig Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Good Networking Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting Frame Network Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Network Configuration Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Web Browser Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Web Browser Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Addressing the Frame URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Default MAC (machine) Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using the 8900NET GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8900 Frame GUI Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Frame Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Older and Legacy Module Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Frame Configuration Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Frame Connections Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Frame Alarm Reporting Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SNMP Reporting Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Power Supply/Demand Web Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Frame Power Supply Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
8900NET Module Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8900NET Instruction Manual 3
Contents
8900NET Module Status Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8900NET Module Configuration Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8900NET Network Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Media Module Slot Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Upgrading Software on 8900 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Acquiring Software Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
NetConfig Method Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Troubleshooting GUI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
LogPrint Procedure From 8900 Frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Temperature Sensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ROM and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
RS-232 Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Module Health Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Frame Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Module Present Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Fan Speed Control and Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
On-board Regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Control and Monitoring Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Control and Monitoring Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8900–FLOAD–CBL Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8900NET Software Update From FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
FTP Method Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
FTP Software Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Password Protection for Software Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Unsupported Software Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4 8900NET Instruction Manual
Preface
About This Manual
This manual describes the features of a specific 8900 module in the Gecko
and Gecko Flex Signal Processing System families As part of this module
family, it is subject to Safety and Regulatory Compliance described in the
Gecko 8900 Series frame and power supply documentation (see the Gecko
8900 Frames and the Gecko Flex Frames Instruction Manuals.
8900NET Instruction Manual 5
Preface
6 8900NET Instruction Manual
8900NET Network Interface Module
Introduction
The 8900NET Network Interface module provides control and monitor
access to the 8900 Gecko and Gecko Flex frames and the audio/video
media modules in the frames through a web browser graphical user interface (GUI) and the Newton Control Panel.
Note Refer to the 8900 Gecko Frames or Gecko Flex Frames Instruction Manuals
for more specific frame information.
8900NET Features
The 8900NET module features:
• 10 Base-T Ethernet interface,
• Fan front cover power and control,
• Support for the following:
• Software update downloading
• Newton Modular Control system control panels
• Frame Alarm connector on rear of module
• Asset Tag identification
• HTML protocol
• Simple Network Management Protocol (SNMP) monitoring
• NetConfig Networking Configuration application
8900NET Instruction Manual 7
Introduction
Remote Control Panels
Basic Network Design
The 8900NET module with version 3.2.0 or later software allows the frame
to be remotely controlled by the Newton Control Panel via the Ethernet
port. Refer to the Newton Control Panel documentation for details.
The 8900NET module can be employed in either a point-to-point or local
area network (LAN) control/monitoring configuration. Figure 1 illustrates
a point-to-point configuration.
Figure 1. Point-to-point Configuration
LOCK
PS 1 PS 2
FAULT
8900TFN frame with
Network Interface Module
Figure 2 illustrates a typical LAN configuration.
Figure 2. Basic Network Configuration
LOCK
8900TFN frame with
Network Interface Module
LOCK
PS 1 PS 2
FAULT
LOCK
Ethernet cable, Category 5 Crossover
PC running:
Windows OS,
Unix, or Macintosh OS
Ethernet
0612-08
Netscape Navigator 4.x
or Internet Explorer 4.x
Ethernet cable: Category 5
PC running:
Windows OS, Unix,
or Macintosh OS
Ethernet
Netscape Navigator 4.x
or Internet Explorer 4.x
LAN Ethernet Hub
LOCK
LOCK
PS 1 PS 2
FAULT
8900TFN frame with
Network Interface Module
0612-07
8 8900NET Instruction Manual
Installation
Module Placement in the Gecko 8900 and Gecko Flex Frame
Installation
This section describes placing the module in an 8900 frame and cabling the
communications ports for all frame types. Procedures for power-up, DIP
switch settings, and network configuration of the module are described in
the following sections.
Note The Gecko Flex frame requires an 8900NET module running 4.0.0 or later
software.
There are ten cell locations in the frame to accommodate media modules.
These are the left ten locations. Refer to Figure 3.
The two cells on the right are allocated for the power supplies. For additional information concerning the Power Supply module, refer to the
Gecko 8900 Series Frames Instruction Manual and the Gecko Flex Frames
Instruction Manual.
The third cell from the right is allocated for the 8900NET Network Interface
or Frame Monitor module. For additional information concerning the
Frame Monitor module, refer to the Gecko 8900 Series Frames Instruction
Manual or the Gecko Flex Frames Instruction Manual.
Figure 3. Gecko 8900 Series Frame
Any 8900 Module
Frame Monitor
or 8900NET Network
Interface Module (only)
Power
Supplies
(only)
0612_04r1
Note The 8900NET module can be plugged in and removed from an 8900 Series
frame with power on. When power is applied to the module, LED indicators
reflect the initialization process (see Power Up on page 17).
8900NET Instruction Manual 9
Installation
To install the 8900NET module in the frame:
1. Insert the module, connector end first (see Figure 4), with the
component side of the module facing to the right side of the frame.
Instead of an ejector tab, the 8900NET module has a connector tab with
a circular finger-hole for pulling the module.
2. Verify that the module connector seats properly and securely against
the backplane.
Figure 4. Module/Frame Orientation
S1
1
2
543
6
1
7
8
432
5
76
8
Component side
Configuration DIP switches
0612 -16
10 8900NET Instruction Manual
Cabling
Installation
This section describes physical connections, the connectors and cables,
used for network communications. Setup procedures for each type of connection are described in Establishing Frame Network Identity on page 25.
An example of control and monitoring connectors on the frame rear are
illustrated in Figure 5 for the Gecko 8900 frame and Figure 6 for the
Gecko Flex frame.
Note There are several versions of frames in the Gecko and Gecko Flex 8900
Series. Refer to the manual that came with your frame if the information is
not covered here.
Figure 5. 8900NET Input/Output Connectors on 8900TFN -V/-A Frame
Frame Alarm
RS232
(Video Frame – J102 pins 8 and 9)
(Audio Frame – J7 pins 8 and 9)
J1 J2
ETHERNET
Figure 6. 8900NET Input/Output Connectors on 8900FFN Frame
RS232
J102
J1 J2
ETHERNET J103
Network configuration storage
Frame ID
(Frame MAC address storage)
Frame Alarm - J102 pins 8 and 9
0612_31r1
0612_32
8900NET Instruction Manual 11
Installation
Frame Alarm
The Frame Alarm is an external connector that reports frame status and
module health (8900-TF/TFN-V/A and 8900-FF/FFN frames) that can be
accessed through pins 8 and 9 of the RS-232 connector on the rear of the
frame. Details for connecting an external customer-supplied alarm are
given in the Gecko 8900 Series Frames Instruction Manual and the Gecko Flex
Frames Instruction Manual.
The Frame Alarm responds to conditions enabled on the 8900NET
Network Interface module with DIP switches S1 and S2 as given in Tab le 2
on page 20.
Note Earlier version 8900 frames used a BNC connector labeled SMPTE ALARM to
access the alarm connection. For information concerning the SMPTE Alarm
bus cable, refer to the Gecko 8900 Frames Instruction Manual.
RS-232 Communication Port Cable
The nine-pin RS-232 connector is used to connect the frame to a PC to initially set the frame’s network communication parameters. After network
communication is established, subsequent changes to these parameters can
be made using the network GUI.
CAUTION The RS-232 cable should be removed after completing the initial frame setup.
Leaving a long serial cable connected to the frame without a connection at the
other end may freeze the 8900NET module startup routine.
Note The cable used for this connection is a DB-9F to DB-9M, straight-through
cable available from Grass Valley as part of cable kit model 8900CAB
(10 ft./3 m length).
The communication parameters for the RS-232 connection are:
• Baud rate: 9600
• Data bits: 8
• Parity: none
• Stop bits: 1
• Flow control: none
12 8900NET Instruction Manual
8900TFN Frame
Installation
The male end connects to the RS-232 connector on the 8900 frame (see
Figure 7) and the female end connects to either Com1 or Com2 on the PC,
depending upon the configuration of the computer’s I/O ports.
Figure 7. RS-232 to Initialization PC Cable and Pinout
PC running Hyperterm Terminal Emulation
RS-232
DB-9
Male
Comm. Parameters: 9600 baud, 8 bits, parity-none, 1 stop, flow-none
Pin Pin
1
2
3
4
5
6
7
8
9
1
2
3
4
5
Pin 1
6
7
8
Pin 5
9
Pin 9
Com1 or
Com2 port
DB-9
Female
0612 -09r1
8900NET Instruction Manual 13
Installation
If the PC uses a 25-pin RS-232 connector, use a cable adapter as shown in
Figure 8.
Note The 25-pin adaptor is available from Grass Valley as part of cable kit model
8900CAB.
Figure 8. DB-9 Cable and DB-25 Cable Adaptor Pinout
DB-25
Female
25-pin 25-pin9-pin 9-pin9-pin
1
2 Tx
3 Rx
4
5
6
7
8
9
20
22
1
2
3
4
5
6
7
8
9
1
8
2
3
3
2
4
20
5
7
6
6
7
4
8
5
9
22
DB-9
Female
DB-9
Male
9-pin
1
Tx 2
Rx 3
4
5
6
7
8
9
0612 -11
14 8900NET Instruction Manual
8900TFN Frame
Installation
Ethernet Cable
The 8900NET module enables the frame’s RJ-45 Ethernet connector.
Through this port the 8900 frame can connect to:
• A single PC with a network card (point-to-point), or
• A local area network (LAN) through a network hub.
Point-to-Point Connection
Figure 9 illustrates the crossover cable connection and pinout for a
point-to-point connection to the controlling PC.
Note This Category 5, UTP Crossover Cable is available from Grass Valley as part
of cable kit model 8900CAB (10 ft./3 m length).
Figure 9. Point-to-Point RJ-45 Connection and Cable Pinout
PC with network card and net browser software
Ethernet
RJ-45
connector
Pin Pin
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Category 5, UTP Crossover Cable
PinPin
1
3
2
6
3
1
4
5
5
4
6
2
7
8
8
7
Pin 1
To PC network card
RJ-45 connector
RJ-45
connector
0612 -10r1
8900NET Instruction Manual 15
Installation
8900TFN Frame
Ethernet
Local Area Network (LAN) Connection
Figure 10 illustrates the cable connection for a LAN connection to a
network hub.
Note Because of varying length requirements and ready availability from network
equipment suppliers, this cable is not supplied by Grass Valley.
Figure 10. LAN RJ-45 Connection and Cable
Network Ethernet Hub (typical)
RJ-45
connector
Pin Pin
1
2
3
4
5
6
7
8
hp
PinPin
1
2
3
4
5
6
7
8
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
Pin 1
8 7
6 5 4 3 2 1
To network hub
RJ-45 connector
10 BaseT
RJ-45
connector
0612 -15r1
Category 5, UTP Cable
16 8900NET Instruction Manual
Power Up
The various front LED indicators and configuration switches on the
8900NET module are illustrated in Figure 11. Upon power-up, all LEDs
should light for the duration of the initialization process.
After initialization the Power LED will be on and the red Network Module
LED (labeled NM) should go off. All other LEDs report detected conditions
within the frame and the installed modules. If the NM LED does not go off,
the board needs servicing.
Note When a media module is first plugged into the 8900 frame, the 8900NET
module may report a momentary fault. This will clear once the media module
has booted up.
Figure 11. LEDs and Configuration Switches on the 8900NET Module
TEMP - Temperature (red)
PS2- Power Supply 2 (red)
PS1 - Power Supply 1 (red)
FAN (red)
MOD - Module Health Bus (red)
FB - Frame Bus (red)
NM - Network Interface Module (red)
Power Up
LED Color Key
Red = Fault
Green = OK
Yellow = Active
PWR - Power (green)
INHIB - Module Health Inhibited
(yellow)
S1
COMM - Communication (yellow)
ETHER - Ethernet communiction
(yellow)
FAULT - Frame Fault (red)
Configuration DIP switch S1
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Configuration DIP switch S2
REM OVR - Remote Override
(yellow)
Tab le 1 on pa ge 18 describes all the module’s LEDs and the conditions indi-
cated.
0612 -06r1
8900NET Instruction Manual 17
Power Up
8900NET Module Indicator LEDs
The possible LED status and conditions indicated are shown in Tab le 1.
Table 1. Indicator LEDs and Conditions Indicated
LED LED State Condition
POWER
(green)
TEMP
(red)
PS2
(red)
PS1
(red)
FAN
(red)
MOD
(red)
Long continuous flashing One or more modules is reporting a configuration error
FB
(red)
INHIB
(yellow)
FAULT
(red)
COMM
(yellow)
ETHER
(yellow)
REM OVR
(yellow)
Off Power is off or on-board regulator has failed
On continuously Module is powered
Off Frame temperature is within specified parameters
On continuously Over-temperature condition detected in frame
Off Normal operation or alarm disabled
On continuously Power supply 2 is present and reporting an alarm condition
Off Normal operation or alarm disabled
On continuously Power supply 1 is present and reporting an alarm condition
Off Normal operation or alarm disabled
On continuously One or more fans in the front cover assembly is not rotating
Off Normal operation or alarm disabled
On continuously
Off Network module is communicating with modules on the frame bus
On Internal frame bus communication failure
Off Normal operation or alarm disabled
On continuously A non-compliant module in the frame has disabled the module health bus
Off Normal operation
On continuously One of the on-board fault LEDs is illuminated or flashing
Flashing Indicates the MOD (module health LED) is flashing
On Indicates module is polling the devices on the internal frame communication bus
On Indicates active communication detected on the Ethernet bus
Off All fault reporting is controlled by onboard configuration switches
On Software overrides onboard configuration switches
Module health bus is not disabled and one or more modules is reporting an internal
fault
18 8900NET Instruction Manual
Status Monitoring and Reporting
This section provides a complete summary of frame status monitoring and
reporting in a Gecko or Gecko Flex system with an 8900NET module
installed in the frame. It summarizes what status items are reported and
how to enable/disable reporting of each item. There are a number of ways
to monitor status of frame power supplies, fans, modules in the frame, and
other status items depending on the method of monitoring being used
including Frame Alarm and SNMP reporting.
Frame Status Reporting
8900 Frame status will report the following items:
• Power supply health,
• Status of fans in the frame front cover,
• Temperature,
• Module health, and
Status Monitoring and Reporting
• Frame bus status.
Module health status will report the following items:
• Internal module state (and state of submodule or options enabled)
including configuration errors (warning), internal faults, and normal
operation (Pass).
• Signal input states including valid/present (pass), not present or
invalid (warning), not monitored, and not available (no signal inputs).
• Reference input states including locked/valid (pass), not
locked/invalid (warning), and not monitored.
• Signal output states with reporting functionality (reference output).
The Module Health bus provides a means for older (legacy) or less capable
modules (such as DAs with no microprocessor) that cannot communicate
over the Frame serial bus to report alarm conditions to the Frame Monitor
or 8900NET module. The reporting is done using a voltage level sent by the
module. When a problem exists on the module, it will pulse or provide a
continuous voltage level to the Module Health bus indicating that a
problem exists on the module but will not indicate what the problem is.
8900NET Instruction Manual 19
Status Monitoring and Reporting
8900NET Module Alarm DIP Switches
Two eight-position DIP switches (S1 and S2) enable or disable the overall
status reporting of the frame, including Frame Alarm and SNMP monitoring. The current status of these settings is reported on the Frame Alarm
Reporting (page 37) and SNMP Reporting (page 39) frame web pages.
Refer to Figure 11 on page 17 for the location of S1 and S2 on the 8900NET
module and Figure 12 and Tab le 2 for the possible settings. A settings table
is also silk-screened on the bottom of the module. Disabling (or filtering) of
fault reports can sometimes be useful in isolating problems in the frame.
Figure 12. Alarm Reporting DIP switches
Power Supply #1
Power Supply #2
Temperature
Fan
Module
Frame Bus
Fan Speed
NM Control
12345678
IP Address
Frame Control
Remote
Override
LED
Status
S2S1
12345678
S1
Segmen
t
1
2
3
4
5
6
7
8
S2
Segmen
t
1
2
3
4 – 8
8900NET
Table 2. 8900NET Module DIP Switches
Left Position (open) Right Position (closed)
PS1 Fault Reporting Enabled PS1 Fault Reporting Disabled
PS2 Fault Reporting Enabled PS2 Fault Reporting Disabled
(Not used) Over Temp reporting is always enabled locally and through SNMP
Fan Fault Reporting Enabled Fan Fault Reporting Disabled
Module Fault Reporting Enabled Module Fault Reporting Disabled
Frame Bus Error Reporting Enabled Frame Bus Error Reporting Disabled
Fan Speed Controlled by Temperature Fan Speed Fixed at Maximum
Network Module Control Enabled (remote control via GUI is
enabled)
Left Position (open) Right Position (closed)
Status Enabled (enabled alarms are reported over SNMP) SNMP Reporting is disabled except for Over Temp alarm
IP Address (not currently supported)
Frame Control Enabled (remote control via GUI is enabled) GUI for the frame and all modules within is placed in read only mode
(Currently Not Used)
Network Module GUI is placed in read only mode
0612_28
Note Disabled faults are still detected by the network GUI but LEDs will be inactive.
20 8900NET Instruction Manual
Refer to the next section, Status Reporting Methods, for an overview of how
status is reported from the 8900 frames, 8900NET and 8900 media modules
in the frame.
Status Reporting Methods
The frame status reporting methods include the following:
• LEDs on the Frame, 8900NET module, and individual frame media
modules,
• External Frame Alarm output on the rear of the 8900 frames,
• Web pages, graphics and text, and
• SNMP traps, captured by NetCentral or another SNMP Manager
Application (HyperTerminal).
Note SNMP trap information is only available when an SNMP Agent has been
installed and configured.
Status Monitoring and Reporting
LEDs
LEDs on the 8900NET module, media modules in the frame, and on the
front of the 8900TF/TFN-V/-A and 8900-FF/FFN frames indicate status of
the frame and the installed power supplies, fans in the front covers, and
modules.
When a red FAULT LED is lit on a frame front cover, the fault will also be
reported on the 8900NET module. The LEDs on the front of the 8900NET
module can then be read to determine the following frame and module
fault conditions:
• Power Supply 1 and 2 health,
• Fan rotation status,
• Frame over-temperature condition,
• Frame Bus fault (8900NET only), and
• Module health bus.
In general, LED colors used on the frame and modules indicate:
• Green – normal operation, (Pass) or signal present, module locked.
• Red – On continuously = fault condition, flashing = configuration error.
• Yellow – On continuously = active condition (configuration mode or
communication), flashing in sequence = module locator function.
8900NET Instruction Manual 21
Status Monitoring and Reporting
Status LEDs for the 8900NET module are shown in Figure 11 on page 17
and described in Table 1 on page 18. LEDs for the Frame Monitor module
that comes in the 8900TF-V/TF-A or 8900-FF frames are described in the
Gecko 8900 Frame Instruction Manual or the Gecko Flex Frames Instruction
Manual.
External Frame Alarm
An external Frame Alarm connector is available on pins 8 and 9 of the
RS-232 connector on the rear of 8900 frames (Frame Monitor or 8900NET
Network Interface module required) as described earlier in Figure 5 on
page 11.
The Frame Alarm responds directly to the settings of the 8900NET DIP
switches described in 8900NET Module Alarm DIP Switches on page 20 and
to the selections made on the Frame Alarm Reporting Web Page on page 37.
When any of the fault or warning conditions enabled with the DIP switches
or Frame Reporting web page are present, the module responds with a
pulsing or continuous voltage level to the Frame Alarm. The type of
voltage output (pulsing or continuous) is user selectable on the Frame
Reporting web page.
Connection and use of the Frame Alarm is covered in detail in the Gecko
8900 Frames and the Gecko Flex Frames Instruction Manuals.
Web Browser Interface
When the 8900NET module is installed in the frame, a web browser GUI
can indicate frame and module status on the following web pages:
• Frame Status web page – reports overall frame and module status in
graphical and text formats. Refer to Frame Status Page on page 30 for
complete details.
• Module Status web page – shows specific input and reference signal
status to the module along with enabled options and module versions.
• A Status LED icon is present on each web page to report communication status for the frame slot and acts as a link to the Status web page
where warnings and faults are displayed (8900NET version 3.0 or later).
In general, web page graphics and text colors used indicate the following:
• Green = Pass – signal or reference present, no problems detected.
• Red = Fault – fault condition.
• Yellow = Warning – signal is absent, has errors, or is mis-configured.
• Gray = Not monitored (older 8900 module).
• White = Not present.
22 8900NET Instruction Manual
Status reporting for the frame is enabled or disabled with the 8900NET
module configuration DIP switches (see 8900NET Module Alarm DIP
Switches on page 20). Some module status reporting items can also be
enabled or disabled on individual configuration web pages.
SNMP Monitoring
The Thomson Grass Valley Modular Control and Monitoring System uses
the Simple Network Monitoring Protocol (SNMP) internet standard for
reporting status information to remote monitoring stations. The SNMP
reporting from the 8900NET module provides status reports (traps) for
various frame and module faults and warnings as described in Tabl e 3 o n
page 24.
Status reports (traps) are unsolicited reports sent from the SMMP Agent to
one or more SNMP Managers such as Thomson Grass Valley’s NetCentral.
Once an SNMP agent has been installed, the 8900 frame and each module
slot can be configured to enable or disable these reports through the Frame
SNMP Reporting web page (see SNMP Reporting Web Page on page 39).
Status Monitoring and Reporting
Note Two of the DIP switches described in Table 2 must be enabled for corre-
sponding SNMP reporting of the system components
S2 segment 1)
SNMP Trap severity can be one of three degrees:
• Warning – a limitation in the module’s intended performance,
• Alarm – a failure in communication with the module, or
• Informational – a configuration change such as a switch setting.
The enabled SNMP traps will be reported to any SNMP manager that is
identified as an SNMP Report Destination in 8900NET configuration (see
8900NET Module Configuration Web Page on page 44. Trap severity is
read-only hard-coded information that is interpreted and responded to by
the SNMP Manager software configuration.
The SNMP traps available on the Gecko 8900 frame and modules are outlined in Table 3 on page 24. The SNMP trap reports available and their
severity are configured on the 8900 Frame SNMP Reporting web page for
all media modules, the 8900NET module, Power Supply 1 and 2, the Frame
Bus Status, and Module Health status (8900TFN Video frame only).
.
(S1 segment 5 and
8900NET Instruction Manual 23
Status Monitoring and Reporting
Table 3. 8900 Frame and Module SNMP Reporting Summary
1
Module Health is only reported on the 8900TFN Video frame.
SNMP Trap Report Trap Severity
8900 Frame
Frame Bus Status Alarm
Cover Status Warning
Fan Status Alarm
Module Health
Frame Power Supply 1 and 2
Power Supply Fault Alarm
Power Supply Removed Warning
Net Card Status Alarm
Hardware Switch Warning
Slot Fault Alarm
Module Removed Warning
Signal Loss Warning
Reference Loss Warning
Config Error Warning
1
8900NET Module
Media Modules
Alarm
For the latest MIB (Management Information Base) files for the modular
control system, go to the Thomson Grass Valley public ftp site at:
ftp://ftp.thomsongrassvalley.com/pub/modular/
24 8900NET Instruction Manual
Establishing Frame Network Identity
The initial configuration of the 8900NET module, using the RS-232 port
(refer to Figure 7 on page 13), establishes the frame’s network identity to
enable the operation of the Web-based GUI. A PC running a terminal emulation application is used to set the initial parameters for network communication. Once initial identity is established, the GUI can be used to make
subsequent changes to the networking parameters. Parameters established
include:
• Local IP Address,
• Gateway IP Address,
• Subnet Mask, and
•Default Route.
Note If the Gecko 8900 frame is to be connected point-to-point to a single PC
workstation, both the frame and the PC must be on the same Subnet.
Establishing Frame Network Identity
NetConfig Application
With this software release, Gecko 8900 Series frames can interface with NetConfig (Network Configuration Application). NetConfig is a PC software
tool for configuring and setting up NetConfig-enabled Grass Valley
devices. Refer to the NetConfig Manual or the 8900NET Release Notes for
current information on using this tool.
Good Networking Practices
The Local IP Address form of a URL can be used within an intranet to
address the Gecko 8900 frame’s web page. An intranet is set up and maintained within your facility and is isolated from the Internet.
Access from outside, through the Internet, may require the use of a Domain
Name and a firewall, depending upon your network architecture. Domain
Name Addressing requires a Domain Name Server located within the
intranet that maps the Domain Name to the frame’s IP Address. The 8900
frame has no knowledge of its assigned Domain Name. Network traffic
through a Domain Name Server can delay 8900NET response time.
Remote workstations are also subject to network traffic delays. Local PC
workstations should be used for real-time operation of the 8900NET.
The most direct and timely access to the frame is achieved by using a PC
workstation that is assigned to the same Subnet (see Figure 13 on page 26).
A workstation in a different Subnet, even when located on the same router,
will be subject to processing of the IP Gateway.
8900NET Instruction Manual 25
Establishing Frame Network Identity
Figure 13. Local IP and Subnet Addressing
Subnet 2
Subnet 1
LOCK
FAULT
8900TFN frame 127.1.2.3
LOCK
PS 1 PS 2
FAULT
8900TFN frame 127.1.2.4
IP Gateway
Remote PC
182.1.2.2
182.1.2.1
LOCK
PS 1 PS 2
LOCK
127.1.2.1
Router
Local PC
0612-17
127.1.2.5
FTP Server
127.1.2.6
Setting Frame Network Identity
After you have connected the PC to the RS-232 port (refer to RS-232 Com-
munication Port Cable on page 12) and established communication using the
terminal emulation application, press the enter/return key several times to
see the active prompt.
At the prompt enter:
setup
You will see:
-> setup
Here are the current parameters and their values:
Local IP Address: 192.158.211.83
Gateway IP Address: 192.158.211.1
Subnet Mask: 255.255.255.0
If a change is made, it is necessary to reboot
26 8900NET Instruction Manual
Establishing Frame Network Identity
this machine. This will occur automatically when
you have completed making changes.
Do you wish to change any of the values? y/n (n): y
For each parameter, you will be given the name of the
parameter and its current value in parenthesis. To
change it, just type in the new value. If you don't
wish to change it, just hit the Enter key.
If you make a mistake on a previous value, continue
with the remaining parameters; you will be given an
opportunity to modify the value again.
Please ensure that you change from Factory defaults
to your network parameters.
The local Ip Address is the Internet address of this
machine. It consists of four numbers separated by periods ('.'). Each number can be in the range of 0 to
255. For example: 192.167.221.45
There must an IP address.
IP Address (192.158.211.83):
The Default Route is the Internet address of the machine which routes network packets outside of the local network. It consists of four numbers separated by
periods ('.').
Each number can be in the range of 0 to 255.
For example: 192.167.221.1
If you respond with a single period (.),a default
route will not be assigned.
Default Route (192.158.211.1):
The Subnet Mask is used in the routing algorithm.
The Net Card will use the mask to determine if a address is in local net or to send the message to the
default. It consists of four numbers separated by periods ('.').
Each number can be in the range of 0 to 255.
For example: 192.167.221.1
If you respond with a single period (.),
a Subnet Mask will not be assigned.
Subnet Mask (255.255.255.0):
8900NET Instruction Manual 27
Web Browser Setup
Network Configuration Storage
8900NET software version 3.2.0 and later enables storage of the IP
addresses (network configuration) on the frame backplane on frames that
are equipped with storage capability (see Figure 5 on page 11). In earlier
versions of software and frame types with no storage capacity, the IP
addresses are stored on the 8900NET module and stay with the module
when it is moved to another frame.
There are a number of ways to determine what type of frame you have.
Ta bl e 4 lists all available frame types and how they can be identified. The
assembly number of the frame is identified on a label located inside the
frame inside the chassis.
Table 4. 8900 Frames Types IP Storage Capability
Model Number Backplane Assembly Number
8900TFN-A
8900TFN
8900TFN-A
8900TFN-V
To determine what frame model you have and where IP addresses are
stored, you may also access the Frame Status page with the web browser
(see Figure 22 on page 43). All frames with 8900NET cards with software
version 3.2.0 and later will report a
the following:
• Network configuration stored on 8900NET module, or
• Network configuration stored on frame.
Note All Gecko Flex frames store the IP address on the frame.
Web Browser Setup
Audio backplane with 1 IC
Video backplane with 1 IC
Audio backplane with 2 ICs
Video backplane with 2 ICs
Network Config
Storage
610-0960-00 8900NET module
630-0063-00 8900NET module
610-0960-01 Frame backplane
610-0984-00 Frame backplane
Network Config status message as one of
The recommended Web browser for use with the 8900NET Control and
Monitoring System is either:
• Netscape Navigator 4.x or later, or
• Internet Explorer 4.x or later.
Versions 3.x or earlier of these browsers may cause undesirable results in
the presentation of HTML frames.
28 8900NET Instruction Manual
Web Browser Notes
• If applicable, configure the browser for direct HTTP requests to the
frame rather than addressing a Proxy Web Server. The Modular Frame
Web Server will typically be installed inside the firewall.
• For older Netscape browsers, the Cache should be configured to always
refresh.
Addressing the Frame URL
To address an 8900 frame from an internet browser, enter the frame’s
default URL into the URL line of the browser (“Location” in Netscape Navigator, “Address” in Internet Explorer). The URL will be the IP Address
given to the frame during initial setup (see Setting Frame Network Identity on
page 26), or a Domain name that has been mapped to the IP Address in
your Domain Name Server tables. The URL should look like this:
http://{Frame’s IP Address}/
Web Browser Setup
Example:
http://127.123.234.2/
Or:
http://{Frame’s Domain Name}/
Example:
http://frame1.xyz.com/
The correctly entered URL will call up the 8900 frame’s default first
page—Frame Status.
Default MAC (machine) Address
Each 8900 frame has a unique ethernet physical level MAC address that is
stored in the frame ID memory chip (see Figure 5 on page 11). If this
memory is missing, the 8900NET module will substitute a default MAC
address: 08-00-11-09-CD-AB. If more than one 8900 frame in your network
is assigned the default MAC address, network conflicts will occur. To verify
the frame has a unique MAC address refer to 8900NET Network Web Page
on page 48.
8900NET Instruction Manual 29
Using the 8900NET GUI
Using the 8900NET GUI
Once the frame’s first web page—Frame Status—has been accessed (see
Figure 14 on page 31), navigation can be done using the hypertext Link List
in the left column.
The Link List is a two-tier list with the frame’s devices at the highest tier
and sub-pages for each device in a secondary tier (sub-list) below the
parent device.
To navigate from device to device, click on a device link. This will open the
device’s Status web page and open the sub-list of device web pages. You
can also click on the slot icon in the content display to access a particular
module’s Status web page.
To navigate to one of the device’s web pages click on any of the device’s
sub-list of links. This will update the content display to the right.
Note To update status, web pages must be manually refreshed by clicking on the
Refresh button (to the right of the page title and shown at left). Changes
made at the frame or from other browsers or when a module has been
removed and reinstalled, will not be displayed until the page is refreshed.
8900 Frame GUI Interface
This section describes GUI functions for the 8900 frame.
Frame Status Page
The Frame Status web page (Figure 14 on page 31) displays an overall
status for the frame.
The top section reports the following for the frame:
• Model Number,
• Description,
• Frame Location (defined in Frame Configuration),
• Temperature Status,
• Warning messages, and
• Front Cover status (Cover installed, No Cover)
The graphical content display shows:
• Module slot status,
• Power supplies installed (and empty slots),
• Presence of the 8900NET module (Net Card), and
• A clickable link to each device’s status page.
30 8900NET Instruction Manual
Figure 14. 8900NET GUI for Frame Control
The Links section lists the frame and its current modules. The selected link's Status
page is first displayed and the sub-list of links for the selection is opened. The sub-list
allows you to select a particular information page for the selected device.
Content display section displays the information page
for the selected frame or module (frame slot icons are also
active links).
Refresh button for manual
refresh of page
Using the 8900NET GUI
Module Slot Status
Module Slot Status icons report one of the following (Tab le 5):
Table 5. Module Status Indicators
Icon
Color
White None Empty No module detected in slot.
Gray No Comm No Comm Slot contains a legacy module which was not designed to support Frame Bus
Green Pass Module Slot contains a fully Frame Bus capable module.
Yellow Warning Module 8900NET has detected a warning condition in module due to lack of input sig-
Red Fault Module 8900NET has detected a fault condition in module. Fault may have been com-
Module
Status
Icon Text Indication
communications with an 8900NET module.
nal or incomplete support for remote monitoring and control. Ability of module
to perform intended operation is limited.
municated over the Frame Bus, or may indicate a failure of the module to
respond over the Frame Bus.
0612-12r2
8900NET Instruction Manual 31
Using the 8900NET GUI
During initial polling, modules that do not respond immediately may transition to a
porary status until a maximum number of sequential attempts fail and a
Fault is reported.
Note The first release of 8960DEC module code causes a Fault condition because
Note Early releases of the 8960ENC, 8950DAC, 8950ADC, 8920DAC, 8920ADC,
WARNING, MODULE NOT RESPONDING status. In this case, this is a tem-
it never responds on the Frame Bus. There is no way for the 8900NET module
to tell the difference between a fully functional early release of 8900DEC and
a module whose Frame Bus Interface has failed.
and the 8916 signal a warning condition due to limited capability over the
Frame Bus. All of these, except the 8916, can be upgraded by the user with
fully capable Frame Bus software.
Frame Properties
The Properties section on the Frame Status page reports:
•Vendor name,
• Number of media module slots,
• Software version (installed on the 8900NET module),
• Network Config (whether the network configuration is stored on the
8900NET module or on the frame backplane, depending on frame
model). Refer to Network Configuration Storage on page 28.
Older and Legacy Module Support
8900 and legacy Grass Valley modules that can reside in 8900 frames are
supported to different degrees by the 8900NET module. A compatibility
matrix describing the hardware versions, software update methods
required, and remote control features of the various modules supported by
the 8900 frames and 8900NET module is located in the Compatibility Matrix
on page 71.
Note When the 8900NET is first installed or when many modules are installed
simultaneously, it may take some time for the 8900NET to poll, update status
and build the HTML pages, especially if there are modules that do not
respond as expected, such as legacy modules. During these periods the
Frame Status Page may fall behind temporarily until the 8900NET board can
catch up and present a true current status.
32 8900NET Instruction Manual
Using the 8900NET GUI
Legacy Module Support
Installation of 8500 and 8800 modules shipped prior to November 15, 1999
will cause interruption of the 8900TFN and 8900-FFN frame communication bus. Modules shipped after this date have pins removed in the rear
connector to provide compatibility. Compatible modules can be identified
by the absence of connector pins 10 and 50 (see Figure 15). Incompatible
legacy modules can be returned to Grass Valley for upgrade to the new connector.
Note If an unmodified legacy module is installed in the frame, the frame commu-
nication bus will be interrupted and all module icons in the frame status
display will be red. This problem occurs with legacy modules only and does
not occur with Gecko 8900 Series and Gecko Flex modules.
Figure 15. Modified Legacy Module Connector
Top of Module
Pin 2
Pin 10 Pin 50
Typical
Pin 50
Removed
0612-18
8900NET Instruction Manual 33
Using the 8900NET GUI
Frame Configuration Web Page
Use
this
link
Use the Frame Configuration web page shown in Figure 16 on page 35 to:
• Activate the Locate Frame function,
• Save or recall a frame configuration to a default file,
• Assign the frame a name, index number, and location, and
• Enabling/disabling Frame Health reports and SNMP Trap Reports for
SNMP monitoring.
Locate Frame
Select the Flash radio button in the Locate Frame function to flash the front
cover FAULT Indicator LED on the 8900NET module on and off with a
50 ms duty cycle to help locate the 8900 frame.
Save/Load Frame Configuration File
You may save a frame configuration to a file by clicking on the Save To
button. A frame configuration is saved to a default file (FrameConfigData.mcm) and the name cannot currently be changed. Follow the file
download instructions for saving the file. This file can be recalled on this or
any other networked 8900 frame to create a duplicate configuration.
Use the
path and file name into the display. Select the
selected configuration to the frame.
Browse button to locate a saved frame configuration file or enter a
Load button to load the
Frame Identification
Enter any name, an index number (for SNMP reporting), and a location
name to identify a frame. You may also use the factory default frame name
or location by selecting either
Default button.
Frame Health Reports
A link is provided to the frame health reports on the Frame Alarm
Reporting web page for (see Frame Alarm Reporting Web Page on page 37).
Frame SNMP Trap Reports
A link is provided to the Frame SNMP trap reports on the SNMP Reporting
web page (see Frame SNMP Trap Reports on page 34).
34 8900NET Instruction Manual
Figure 16. 8900 Frame Configuration Web Page
Using the 8900NET GUI
8900NET Instruction Manual 35
Using the 8900NET GUI
Frame Connections Web Page
Use
this
link
Selecting the Connections link will bring up the Connections web page
shown in Figure 17. This page provides a summary of the type and IP
Address of any Newton software or hardware panel or other control panel
communicating with any module in the frame.
When no control panels are communicating with modules in the frame, the
display will report
Figure 17. Frame Connections Web Page
No Connections.
36 8900NET Instruction Manual
Use
this
link
Frame Alarm Reporting Web Page
Selecting the Frame Alarm Reporting link from the Frame link list or the
Frame Health Reports link from the Configuration web page will bring up
the web page shown in Figure 18 on page 38. This page provides a
summary of the various alarms and warning reports that can be enabled
and sent to the external RS-232 Frame Alarm connector on the rear of the
frame (see Frame Alarm on page 12).
Hardware Switch Status – the Hardware Switch Status section of this web
•
page displays the current settings of the DIP switches, S1 and S2, on the
8900NET circuit board as described in 8900NET Module Alarm DIP
Switches on page 20. These switches allow enabling and disabling of
what status reporting information is provided to the Frame Alarm and
SNMP traps.
Output Format for Warnings – set the Frame Alarm output on the RS-232
•
connector to output a pulse or a continuous voltage level when a
warning condition is detected from the Frame Health Reporting bus.
The status of Frame Health reporting is given above the Output Format
for Warnings section. Reporting from the Frame Health bus can be
enabled or disabled by selecting the Module Health
the bottom of the Frame Health Reporting list.
Using the 8900NET GUI
Report checkbox at
Frame Health Reporting – enable or disable Alarm and Warning reporting
•
for the following functions or devices in the frame:
• Media module (Slots 1-10) fault alarms, and loss of signal, loss of
reference, and configuration error warnings (as specified for each
specific module),
• 8900NET module fault reporting,
• Power supply 1 and 2 fault reporting,
• Frame Bus status fault reporting,
• Fan (in front cover) Status fault reporting,
• Module health fault reporting
8900NET Instruction Manual 37
Using the 8900NET GUI
Figure 18. Frame Alarm Reporting Web Page
38 8900NET Instruction Manual
Use
this
link
SNMP Reporting Web Page
Selecting the SNMP Reporting web page link from the Frame link list or the
Frame SNMP Reporting link from the Configuration web page will bring
up the web page shown in Figure 19 on page 40. When an SNMP Managers
such as Thomson Grass Valley’s NetCentral is installed, SNMP trap
reporting from the frame and modules can be configured using these controls.
Trap Destinations – selecting the Trap Destinations link from this web page
•
will bring up the 8900NET Configuration web page explained and
shown in Figure 25 on page 47.
Hardware Switch Status – the Hardware Switch Status section of this web
•
page displays the current settings of the DIP switches, S1 and S2, on the
8900NET circuit board as described in 8900NET Module Alarm DIP
Switches on page 20. These switches allow enabling and disabling of
what status reporting information is provided to the Frame Alarm and
SNMP traps.
SNMP Trap Reporting – enable or disable SNMP Trap Alarm and Warning
•
reporting for the following functions in the frame:
Using the 8900NET GUI
• Media module (Slots 1-10) fault alarms, and removed, loss of signal,
loss of reference, and configuration error warnings (as specified for
each specific module),
• 8900NET module fault reporting,
• Power supply 1 and 2 fault reporting,
• Frame Bus status fault reporting,
• Fan (in front cover) Status fault reporting,
• Module health fault reporting (8900TF)
8900NET Instruction Manual 39
Using the 8900NET GUI
Figure 19. SNMP Reporting Web Page
40 8900NET Instruction Manual
Use
this
link
Using the 8900NET GUI
Power Supply/Demand Web Page
The Power Supply/Demand web page (Figure 20) provides a Power table
listing each of the media modules present in the frame and their power
demand. The total amount of power demand is totaled at the bottom of the
display.
Figure 20. Power Supply/Demand Web Page
8900NET Instruction Manual 41
Using the 8900NET GUI
Frame Power Supply Web Pages
Use
this
link
The frame Power Supply 1 or Power Supply 2 status web pages provide:
• Power Slot Status – pass/fail status of the supply and fan in the power
supply sled (see Figure 21).
• A Frame Health Reports link is given to the Frame Health Reporting
web page (page 37) where a fault in the power supply can be reported
as an alarm to the SMPTE Alarm connector on the rear of the frame.
• When an SNMP manager is installed on the 8900NET module, an
SNMP Trap Reports link will be present. This will link to the SNMP
Reporting web page (page 39) where power supply fault and removal
can be configured for reporting to the SNMP manager.
Figure 21. Power Supply Slot Status Page
42 8900NET Instruction Manual
8900NET Module Interface
This section describes GUI functions for the 8900NET module.
8900NET Module Status Web Page
Using the 8900NET GUI
Use
this
link
The Status web page illustrated in Figure 22 displays 8900NET:
• Module identity, location and internal Net Card diagnostic
Pass/Fail /Warning, status,
• Hardware and software properties,
• Asset Tag identifier (set on 8900NET Configuration web page), and
• Status of on-board hardware configuration switches (set as described in
8900NET Module Alarm DIP Switches on page 20).
A Status LED icon on each module page changes color to report status of
network interface, frame bus, and internal diagnostics:
• Green indicates a Pass condition,
• Red indicates a Fail condition, and
• Yellow indicates a Warning condition.
Figure 22. 8900NET Module Network Status Page
8900NET Instruction Manual 43
Using the 8900NET GUI
8900NET Module Configuration Web Page
The 8900NET Configuration web page (Figure 23) provides the following:
Use
this
link
reboot button,
•A
• SNMP Agent installation,
• An Asset Tag identifier field, and
• A Frame Health Reports link to the Frame Alarm Reporting web page.
Reboot Module
You may reboot the 8900NET module by selecting the reboot button at the
top of the page. A reboot can also be done on the Network web page.
Install SNMP Agent
To use an SNMP Manager, an SNMP Agent software must be installed on
the 8900NET module. The Configuration web page shown in Figure 23 is
displayed if the agent software has not already been installed.
To install an SNMP Agent, refer to Install SNMP Agent on page 45. When
the SNMP Agent has been installed, an SNMP Trap Reports link will be
present on the Configuration web page ().
Asset Tag Assignment
The 8900NET module can be assigned as asset tag identifier by entering
numbers or text in the Asset Tag field. This information will appear on the
8900NET Status web page and in the module inventory when using the
NetConfig Network Configuration application.
Figure 23. 8900NET Module Configuration Web Page (No SNMP Installed)
44 8900NET Instruction Manual
Using the 8900NET GUI
Frame Health Reporting
A Frame Health Reports link to the Frame Alarm Reporting web page is
provided. A fault on the 8900NET module can be reported as an alarm to
the SMPTE Frame Health Alarm on the rear of the frame.
Install SNMP Agent
When SNMP Agent software is installed on the 8900NET module, enabled
status reports are sent to an SNMP Manager such as the Grass Valley’s NetCentral application. Refer to Status Monitoring and Reporting on page 19 for
more information.
To install an SNMP Agent, click on the Install SNMP Agent button (Figure 23
on page 44) to view the license agreement.
After reading the agreement, click on
Agent (Figure 24). Clicking the
installation and return you to the Configuration web page.
Figure 24. SNMP Agent Installation Agreement
Decline button will abort the SNMP Agent
Accept to finish installing the SNMP
8900NET Instruction Manual 45
Using the 8900NET GUI
When the SNMP Agent is successfully installed, the Configuration web
page will contain the additional items listed below and shown in Figure 25
on page 47.
SNMP Trap Reports Link – When the SNMP Agent is installed an SNMP
•
Trap Reports link will be present on the Configuration web page to link
to the SNMP Reporting web page (page 40).
The following SNMP trap reports are provided for the 8900NET
module:
• Net Card Status (Alarm)
• Hardware Switch (Informational)
SNMP Report Activation Modes – each report destination has an activation
•
control that can select one of the following modes of operation:
CREATE – GO creates a new report destination that becomes active
•
after the next module reboot.
CREATE – WAIT creates a new report destination that remains out of
•
service until the user selects active and then reboots the module.
ACTIVE changes a NOT IN SERVICE report destination to active after the
•
next module reboot.
NOT IN SERVICE changes an active report destination to inactive after
•
the next module reboot.
DELETE removes the report destination entry. If the entry was active
•
it remains active until the next module reboot.
Note Report destination status does not change until the 8900NET module is
rebooted.
The status column to the left of the activation operation pull-down
window provides one of the following status reports:
<BLANK> – No entry has been applied.
•
ACTIVE – All new status reports will be sent to this destination.
•
NOT IN SERVICE – The destination has a valid definition but the user
•
has not activated it.
ACTIVE PENDING REBOOT – This entry indicates the report destination
•
will become active upon the next module reboot.
NOT IN SERVICE PENDING REBOOT – This entry indicates the report des-
•
tination will become inactive upon the next module reboot.
NOT READY – The destination entry is invalid. The IP Address may
•
not be properly defined or there is no IP Address or Community
entry.
46 8900NET Instruction Manual
Using the 8900NET GUI
Figure 25. 8900NET Configuration Web Page (SNMP Agent Installed)
8900NET Instruction Manual 47
Using the 8900NET GUI
8900NET Network Web Page
Use
this
link
To view or change the module identity and currently assigned network
addresses for the 8900NET module access the Network web page illustrated in Figure 26.
Note Depending on the type of frame this module is installed in, this network con-
figuration is saved on either the 8900NET module or on the frame backplane.
Refer to Network Configuration Storage on page 28 for details.
Figure 26. 8900NET Module Network Identification Page
After initial frame network addressing is done using the RS-232 port, subsequent address changes may be made using the web page shown above.
Note SubNet Mask and Gateway IP Address are required.
Rebooting the NET Module
Reboot the module for changes to take effect. You can reboot the 8900NET
module from the Network page by clicking the
button can also be found on the Configuration page.
reboot button. A reboot
48 8900NET Instruction Manual
Use
this
link
Media Module Slot Configuration
The 8900NET module also provides the functions for the Slot Config web
page for each media module in the frame (Figure 27 on page 50). Media
module slots may be named to reflect specific functions for that slot or
module within the facility. The configuration for the module can also be
saved to slot memory on the 8900NET module.
Note Both frame and module names and configuration information can be saved
to file and recalled as necessary. This allows quick and easy reconfiguration
of the 8900NET module if it must be replaced or moved to another frame (see
Frame Configuration Web Page on page 34).
• Slot Identification – the module may be identified by typing a specific
name in the
module and travels with the 8900NET module if it is moved to another
frame. Select
The module may also be assigned an asset tag identifier by entering text
or numbers into the
ommended for the identifier to appear completely on the media
module Status web page.
Name field. The assigned name is stored on the 89900NET
Default to enter the factory default module name.
Asset Tag field. A maximum of 23 characters is rec-
Using the 8900NET GUI
Note Asset tag functionality is not available on all 8900 media modules.
• Locate Module – when enabled by selecting the Flash pulldown, the Locate
Module
function flashes the yellow COMM and CONF LEDs on the front
of the module to make it easy to locate in the frame.
Note This function is not available on all 8900 modules and may operate differently
on some modules (only the COMM LED will flash).
• Slot Memory – the slot configuration for each media module is automati-
cally saved periodically to the 8900NET module in that frame. You may
also select the
Learn Module Config button at any time to save the current
configuration for this slot. The configuration is saved on the 8900NET
module. If the 8900NET module is removed or powered down, the
stored configurations are not saved.
When the
Restore upon Install box has been checked, the current configu-
ration saved to this slot is saved as slot memory. When the current
module is removed and another module of the same type and software
version is installed, the configuration saved to the 8900NET module
will be downloaded to the new module. The box must be checked
before the current module with the saved configuration is removed.
Note Make sure all modules of the same type are running the same software ver-
sion. Downloading a configuration to a module with a different software
version can produce unexpected results.
8900NET Instruction Manual 49
Using the 8900NET GUI
If a different type of module is installed in this slot, a warning message
will state that the original module type has been replaced with another
module type. In this case, a
clear the stored configuration from the previous module (see
Figure 27).
Frame Health Reports link is provided to the Frame Alarm Reporting
•A
web page for setting up frame health reporting for this media module
(see the Frame Alarm Reporting Web Page on page 37).
Clear button will appear allowing you to
•An
Figure 27. 8900 Media Module Slot Configuration Page
SNMP Trap Reports link is provided to the SNMP Reporting web page
for setting up SNMP Trap Reporting for this media module (see the
SNMP Reporting Web Page on page 39).
50 8900NET Instruction Manual
Upgrading Software on 8900 Modules
There are currently three ways of updating software on 8900 series modules
depending on the type of module and its current software version.
• 8900NET (version 3.2.0 and later) and some applicable 8900 modules
should be updated using the NetConfig Networking Application
option available with modular and other Grass Valley products. Refer
to NetConfig Method Overview on page 52.
• Older version (2.1.2 and earlier) 8900NET modules must be updated
using the FTP download method described in 8900NET Software Update
From FTP Server on page 74.
• Some 8900 series media modules are not upgradeable with either of the
above methods and require a special 8900-FLOAD-Cable kit as
described in Unsupported Software Updates on page 89.
Acquiring Software Updates
Software field upgrade packages are available from the Grass Valley Customer Service FAQ site and the public ftp site.
Using the 8900NET GUI
You may connect to the Grass Valley FAQ site to access the latest module
and free NetConfig software and subscribe to software updates automatically at the following URL:
http://www.thomsongrassvalley.com/downloads
This link will direct you to the Customer Service FAQ database where all
software downloads are distributed. The information provided here is the
most up-to-date. Using this link is recommended so that when new versions of software are released, you are notified by E-mail. It also provides
information on module software updating, including a list of the modules
that do not support remote upgrades and require the cable kit.
To find the latest available 8900 software on the FAQ site, do the following:
1. Navigate to the FAQ site and click on the first FAQ in the list labeled
DOWNLOAD THE LATEST SOFTWARE?
2. Select the 8900 Series link. There will be a list of all available 8900
software that can be upgraded remotely and below that, a list of the
8900 modules that require the 8900 upgrade kit.
Note Read the README file first if provided, before proceeding with a software
download.
For software that can be upgraded remotely, in most cases two files will
be provided, one with an .fld extension and one with an .sw2 extension.
One or both of these files is required, depending on the software
upgrade method.
8900NET Instruction Manual 51
Using the 8900NET GUI
NetConfig Method Overview
To use this method, your 8900NET module must be running software
version 3.2.0 or later and you must have the NetConfig Networking Application option running on a networked PC on the same subnet as the frame
with the 8900NET module. 8900 media modules that can be updated with
NetConfig are listed on the Customer Service web site.
At least two files are required for updating software with NetConfig, the
.fld and the .sw2 for the module being updated (more than one .fld files
may be required). For acquiring software, refer to Acquiring Software
Updates on page 51.
To use NetConfig for software updating, follow the steps below:
1. Locate the directory on your PC in which the NetConfig application has
been installed. The default location is C:\Program Files\Grass Valley
Group\NetConfig.
If this is not where NetConfig was installed, right-click on the NetConfig desktop shortcut on your PC and select
Shortcut tab and note the location of the installation in the Start In field.
Properties, click on the
2. Copy the .sw2 file for the module update into the main NetConfig
directory.
3. Create a subdirectory named modular (if one does not already exist) in
the main NetConfig directory.
4. Copy the .fld file for the update into this modular subdirectory in the
NetConfig directory.
5. Open NetConfig and click on the Load SW icon on the top toolbar
(shown at left).
6. The NetConfig Update Devices window will open. Available software
updates will be listed. How they appear will depend on the version of
NetConfig you have installed. NetConfig version 2.0.6 is shown in
Figure 28 on page 53. In this version there may be two directories,
modular and Misc.
7. Open the modular directory.
Note These device types and versions represent the .sw2 and .fld files loaded in the
NetConfig main directory and the modular subdirectory. These files must be
present on the PC running NetConfig for them to appear in the Device Type
list.
52 8900NET Instruction Manual
Using the 8900NET GUI
8. Select the 8900NET (4.0.0) selection in the modular folder. If the software
does not appear, open and check the
In the example in Figure 28, the 8900NET selection has been selected
and will be highlighted. All of the modules of this type accessible on the
network will appear in the window on the right under the
heading as shown.
The current software loaded on each module will be listed as well as the
IP address and other information for the module client.
9. Check the corresponding Client Name boxes to upgrade the modules or
use the
network.
10. Press the Load button to perform the update to all the selected modules.
11. Once the loading is complete, select the Refresh button to make sure all
selected modules have updated to the correct software version which
will be reported in the window.
Select All button to update all modules of this type present on the
Misc directory.
Client Name
Figure 28. NetConfig Update Devices Window
12. For more information on using NetConfig, refer to the NetConfig
Networking Application Instruction Manual which is included with the
option, available on the Thomson Grass Valley web site, and may also
be present in the NetConfig directory during some NetConfig
installations.
8900NET Instruction Manual 53
Service
Service
The 8900NET modules make extensive use of surface-mount technology
and programmed parts to achieve compact size and adherence to
demanding technical specifications. Circuit modules should not be serviced in the field.
If your module is not operating correctly, proceed as follows:
• Check frame and module power and signal present LEDs.
• Check network connections at the frame and network routing devices.
• Verify that all ethernet devices have a unique MAC and IP Address/
Domain Name.
• Reboot the 8900NET module (see Rebooting the NET Module on page 48).
Refer to Figure 11 on page 17 for the location of PWR LED and Tab le 1 on
page 18 for proper LED indications.
If the module is still not operating correctly, replace it with a known good
spare and return the faulty module to a designated Grass Valley repair
depot. Call your Grass Valley representative for depot location.
Refer to Contacting Grass Valley at the front of this document for the Grass
Valley Customer Service Information number.
Troubleshooting GUI Operation
The following is a list of possible 8900NET GUI and network problems and
logical steps for troubleshooting them.
Cannot Open Any of the Frame’s Web Pages
1. Check power to the frame.
a. Is at least one of the power supplies operating?
b. Is the 8900NET module’s PWR LED on?
2. Check that the frame is physically connected to the network.
a. Is a cable plugged into the RJ45 connector of the frame?
b. Is that cable also connected to a 10Base-T Ethernet hub?
c. Does the 8900NET module’s ETHER LED indicate network
activity?
d. Does the Ethernet hub have any indication that a link is established
to the frame?
54 8900NET Instruction Manual
3. Is the correct IP Address/URL being used to address the frame?
If a Domain Name is being used to address the frame, try to connect
using the frame IP Address instead.
The Domain Name may not be properly assigned in the local Domain
Name Server or in the workstation’s host file.
The Domain Name Server may not be available to the workstation.
Check that the 8900NET module has been properly configured.
a. Is the correct IP Address or URL being addressed in the web
browser?
b. Was the 8900NET module configured over the serial connection
with the
c. Has the 8900NET module been assigned the correct IP Address in
SETUP (re-run setup over the serial connection)?
d. Is the workstation in the same subnet as the frame? If not:
Has the 8900NET module been assigned the correct Default
Routing Address?
SETUP command?
Service
Has the 8900NET module been assigned the correct Subnet Mask?
e. Has the 8900NET module been rebooted since new IP Address,
Default Routing, or Subnet Mask were assigned or changed?
4. Check if the frame web pages can be opened from a different
workstation on the network.
5. Is the subject workstation physically connected to the network?
6. Check that the workstation and browser have been properly
configured.
a. Can the frame be opened from a different workstation?
b. Has the workstation been assigned a proper IP Address?
c. Has the workstation been assigned a Gateway Address?
d. Is the browser configured to connect to the correct port?
Is it attempting to connect through a modem when it should be connecting through a network interface module?
Some laptop have two separate network ports, one for stand-alone
operation, and the other for operation with a docking station. Is the
correct port being used?
8900NET Instruction Manual 55
Service
7. Check that network traffic can be routed between the workstation and
the frame.
a. If the workstation supports a network ping, ping the frame. For
example, using Windows NT:
Open a command prompt (DOS window)
In the DOS window, enter:
C:\> ping frame’s ip address
The results will indicate if the ping reached the frame.
b. If the workstation does not support a network ping, ping the
workstation for the frame serial interface:
In the frame serial command window, enter:
->ping “workstation’s IP address”
The workstation’s IP address must be inside the double quotes. The
results will indicate if the ping reached the workstation.
c. If the network ping failed, there may be a network problem
between the frame and the workstation. To ensure it is not the
frame, check the frame with a point-to-point connection:
Using a crossover Ethernet cable, connect the frame directly to a
workstation. The workstation should be assigned an IP Address on
the same Subnet as the frame. Attempt to load the frame’s web page
from a Browser on this workstation.
8. If the point-to-point connection attempt fails call Customer Service. If
the point-to-point connection attempt succeeds, the problem is
somewhere in the network between the original workstation and the
frame.
a. Check the connectivity to the frame from different locations in the
network to attempt to isolate physical disconnect problems.
b. Check the connectivity to the frame from inside and outside the
frame’s subnet to isolate IP Gateway routing problems.
56 8900NET Instruction Manual
c. Check for possible Ethernet MAC Address collisions.
If the Frame ID Memory chip installed on the rear of the frame is
missing or has failed, the frame adopts the default Ethernet MAC
Address.
If more than one frame in the Network adopts the default Ethernet
MAC Address, there could be address resolution problems. Upon
power up the frame will indicate in the serial port console window,
either:
“MAC address is unique!” – The Frame has successfully
retrieved a unique Ethernet MAC Address from the Frame ID
Memory chip
or
“MAC address is default!” - The Frame is using the default
Ethernet MAC Address. The Frame ID Memory chip is missing
or has failed. Call Grass valley Group Customer Service
Cannot modify parameters on Web Page
Service
1. Check if parameters can be set for other modules.
If so, the module may be in a remote lockout state.
a. Check if the LOC/REM – LOCAL jumper on the module is set for
local control only. (Refer to that specific module’s manual for help.)
b. In version 2.0 and later of the 8900NET module software, the web
pages for a module in the remote lockout state will indicate that
module remote control is disabled and the module’s controls on the
web pages will be in read-only mode.
If other modules are not controllable, the entire frame may be in a
remote lockout state. In this state, software updates to the modules and
the 8900NET module are also locked out.
c. Check The 8900NET module’s status page if the frame remote
control is disabled.
If so, flip Switch 3 on the S2 DIP switch block (FRAME CNTRL) to
the enabled setting.
2. If it is only a specific parameter that is read-only, the module may be in
a mode assigning read-only operation to that parameter. Refer to the
module’s instruction manual.
3. If only the 8900NET module is read-only, the 8900NET module may be
in remote lockout mode.
a. Check the 8900NET module’s status page to see if the NET CARD
REMOTE CONTROL
8900NET Instruction Manual 57
status is disabled.
Service
b. If so, flip Switch 8 on the S1 DIP switch block (NM CNTRL) to the
enabled setting.
Cannot Connect to the Frame From a VTECS1 VideoFrame Control Panel
1. Check that the frame is powered and configured with a 8900NET
module on the network.
2. Check that the 8900NET module in the frame is loaded with software
version 2 or later.
Version 1 software does not support the control panel connection.
3. Check that the control panel has been properly configured with IP
Address, Gateway IP Address, and Subnet Mask. (Refer to the control
panel’s help feature or instruction manual.)
4. Check that the frame’s correct IP Address has been configured in the
control panel’s frame address.
5. Check that the control panel is physically connected to the network.
a. Check that the control panel is connected to a port on an Ethernet
hub.
b. Check if the L LED (L for link) on the back of the control panel is on.
If the LED indicates no link (off), try a different hub port connection.
If the LED still indicates no link, change the cable.
If the LED still indicates no link, contact VideoFrame.
6. Check that the frame is addressable by the control panel.
a. Check if the T LED (T for transmit) on the back of the control panel
flashes upon the attempt to connect to the frame.
If T does not flash, contact VideoFrame.
b. Check if the R LED (R for receive) on the back of the control panel
flashes upon the attempt to connect to the frame.
If R does not flash, there may be a problem in the network path
between the frame and the control panel.
7. Check that the frame is addressable on the network from a Web
browser, refer to the steps on page 54.
a. Attempt to connect to a different frame.
If successful the problem may be with the original frame or the path
between the control panel and the original frame.
b. Check from a workstation connected to the same Ethernet hub as
the control panel. If unsuccessful, there may be a problem with the
network path between the frame and this hub.
58 8900NET Instruction Manual
Service
Event Messages From the Frame Are Not Being Displayed by NetCentral or
Another SNMP Manager Application
1. Check that the frame is powered on and configured with an 8900NET
module on the Network.
2. Check that the 8900NET module in the frame is loaded with software
version 2.1 or later.
Earlier versions of software do not support SNMP.
3. Check that the SNMP Agent has been installed and configured on the
8900NET module.
View the 8900NET module
figuration parameters, the
DESTINATIONS
If these are not visible, install the SNMP Agent per the instructions in
the manual.
4. Check that the IP Address and Community Name for the SNMP
Manager has been assigned in the
Active.
• If there is no entry for the SNMP Manager in the Table, the SNMP
manager’s IP Address and Community name must be entered (see
8900NET Module Configuration Web Page on page 44).
• If the entry for the SNMP Manager is incorrect, it must be corrected,
activated, and the 8900NET module must be rebooted.
• If the entry has been entered and the Status of the entry is reported
NOT IN SERVICE, the Active operation for that entry must be selected,
applied and the 8900NET module must be rebooted.
• If the entry has been entered and the Status of the entry is
the entry must be corrected, activated and the 8900NET module
must be rebooted.
table.
CONFIGURATION page and note the event con-
NET CARD EVENT REPORTS form and REPORT
REPORT DESTINATIONS table and is
NOT READY,
• If the entry has been entered and the Status of the entry is
–PENDING REBOOT
8900NET Instruction Manual 59
, the 8900NET module must be rebooted.
ACTIVE
Service
5. Check that the particular event has been enabled in the frame.
• For all events, check that the STATUS switch (Switch 1) on the S2
DIP switch block of the 8900NET module is Enabled.
• For Module Failure-Fixed events:
Check that the MODULE switch (Switch 5) on the S1 DIP switch
block of the 8900NET module is Enabled, and
Check that the
CONFIG
page is Enabled.
SLOT STATUS REPORTING parameter on the slot’s SLOT
• For Power Supply Failure-Fixed events:
Check that the PS1 or PS2 switch (Switch 1 or 2) on the S1 DIP
switch block of the 8900NET module is Enabled, and
Check that the
power supply’s
POWER SUPPLY STATUS REPORTING parameter on the
CONFIGURATION page is Enabled.
• For 8900NET module Failure-Fixed events, check that the
STATUS REPORTING
TION
page is Enabled.
• For Hardware Switch change events, check that the
SWITCH REPORTING
TION
page is Enabled.
parameter on the 8900NET module’s CONFIGURA-
HARDWARE
parameter on the 8900NET module’s CONFIGURA-
• For Frame Bus Failure-Fixed events:
Check that the FRAME BUS switch (Switch 6) on the S1 DIP switch
block of the 8900NET module is Enabled, and
Check that the
frame’s
CONFIGURATION page is Enabled.
FRAME BUS STATUS REPORTING parameter on the
NET CARD
• For Front Cover Removed -Installed events, check that the
STATUS REPORTING
parameter on the frame’s CONFIGURATION page is
COVER
Enabled.
• For Frame Bus Failure-Fixed events:
Check that the FRAME BUS switch (Switch 6) on the S1 DIP switch
block of the 8900NET module is Enabled, and
Check that the
frame’s
CONFIGURATION page is Enabled.
FRAME BUS STATUS REPORTING parameter on the
• For Cooling Fan Failure-Fixed events:
Check that the FAN switch (Switch 4) on the S1 DIP switch block of
the 8900NET module is Enabled, and
Check that the
FIGURATION
FAN STATUS REPORTING parameter on the frame’s CON-
page is Enabled.
• For Module Health Failure-Fixed events,
Check that the MODULE switch (Switch 5) on the S1 DIP switch
60 8900NET Instruction Manual
block of the 8900NET module is Enabled, and
Service
Check that the
CONFIGURATION page is Enabled.
• Check that the SNMP Manager is properly configured to receive the
Event Messages.
Check that the SNMP Manager has been assigned the same community name as in the frame’s configuration.
6. Check the network connectivity between the SNMP Manager and the
frame as described in the steps on page 54.
MODULE HEALTH REPORTING parameter on the frame’s
8900NET Instruction Manual 61
Service
LogPrint Procedure From 8900 Frame
You may use the logging function of the 8900NET module to troubleshoot
errors from modules in the 8900 frame. The log will report the last 300 commands received by the 8900 frame. It will contain all commands from
changes made through the web interface or control panel.
To access a LogPrint from a 8900 Frame do the following:
1. Access HyperTerminal by pressing the Start button. Select
Programs/Accessories/Communications/HyperTerminal as shown in
Figure 29.
Figure 29. Find HyperTerminal
2. Click on the HyperTerminal accessory. HyperTerminal will open and
bring up the
3. Typ e telnet into the Name field and select OK.
Connection Description window shown in Figure 30.
62 8900NET Instruction Manual
Figure 30. Connection ‘Description Window
Service
This will bring up the Connect To window shown in Figure 31.
4. In the Connect To window, select TCP/IP (Winsock) selection in the
Connect Using pulldown.
Figure 31. Connect To Window
This will bring up the telnet window shown in Figure 32.
5. In the Host address field that appears, type the IP address of the frame
you wish to connect to and press
8900NET Instruction Manual 63
OK.
Service
Figure 32. Enter Host Address
This will bring up the telnet-HyperTerminal screen shown in Figure 33.
Figure 33. Telnet Screen
6. To save the log to a .txt file while it is running, select the Transfer
pulldown in HyperTerminal and select
log (Figure 34).
Capture Text before running the
64 8900NET Instruction Manual
Service
Figure 34. Capture Text Pulldown
7. In the Capture Text window, browse to a location to save the text file as
shown in Figure 35. Select the
until you indicate it to stop.
Figure 35. Capture Text
Start button. This will capture the text
8. On the HyperTerminal screen, Press the Enter key several times to verify
the connection, then enter the
Figure 36. LogPrint Prompt
9. Press the Enter key to run the log.
10. Once the log has stopped, you may also stop the text capture by
selecting
(Figure 37).
The text file will now contain a record of the last 300 commands
received by the frame.
Capture Text in the Transfer pulldown again and select Stop
LogPrint command shown in Figure 36.
8900NET Instruction Manual 65
Service
Figure 37. Stop Text Capture
The log will also appear in the HyperText window as shown in Figure 38.
Figure 38. Log Print
66 8900NET Instruction Manual
Functional Description
Refer to the block diagram in Figure 39 while reading the following functional description.
Figure 39. 8900NET Block Diagram
Functional Description
+12 V
LEDs
User
Setup
Sw.
User
Setup
Sw.
On-board
Regulator
+5 V
+3.3 V
Temperature
Sensing
Microprocessor
Boot ROM
SDRAM
NVRAM
RS-232
Driver
10BaseT Ethernet
Module Health Bus
Frame Bus
Module
Present
Detection
SMPTE
Alarm
Signal
Processing
Ethernet/MAC Address
Alarm
Bus
RS-232 (9-pin D)
Ethernet (RJ-45)
M
o
t
h
e
r
b
o
a
r
d
Power Supply
Cells
Module Cells
Fan Speed
Control and
Rotation
Sensing
SMPTE
Relay
To Fan Assembly
SMPTE Alarm
(BNC)
0612_01
Temperature Sensing
Two temperature sensors on the module report to the microprocessor when
they detect:
• External ambient temperature above 50° C, or
• Internal frame temperature above 70° C.
The microprocessor will then report a temperature fault.
8900NET Instruction Manual 67
Functional Description
ROM and RAM
Ethernet Port
RS-232 Serial Port
Software updates can be made to the 8900NET ROM through the
Web-based interface. Non-volatile RAM is provided to store key setup
values when power is cycled.
The 10Base-T Ethernet port provides configuration and monitoring access
to the frame, frame modules and the 8900NET module using a web
browser.
The RS-232 port is used to initialize the module with critical network
parameters including a static assigned IP Address. Ethernet MAC address
is stored on a serial EPROM on the frame. (The frame needs both MAC and
IP Addresses.)
Module Health Bus
The Module Health bus connects all the audio/video module cells to the
microprocessor. It is used to report module faults or data errors.
Frame Bus
The Frame Bus provides serial communication to each of the audio/video
modules for remote configuration and monitoring over a network.
Module Present Detection
Module Present lines from cells 1 through 10 and Present/Health lines
from cells 12 and 13 are monitored by the microprocessor using the Module
Present Detection circuitry. For cells 1 through 10, this circuit reports to the
processor whether a module is present and if it supports frame bus communications (control and monitoring). For cells 12 and 13, this circuit
reports if the power supply is present and if it is working properly.
68 8900NET Instruction Manual
Fan Speed Control and Monitor
The fan speed circuit controls the speed of the fans based upon the ambient
temperature in the area in which the frame is located. If the temperature is
30° C or lower, the fans are set to minimum speed. For temperatures above
30° C, the fan speed is set higher as the temperature increases. The fan
speed is set to maximum for ambient temperatures above 40° C. The control
circuit can be overridden so the fans are set to maximum speed, using a
jumper on the board.
On-board Regulator
+12 V supply voltage is regulated on-board to provide +5 V and +3.3 V to
the module
Functional Description
8900NET Instruction Manual 69
Specifications
Specifications
Table 6. 8900NET Specifications
Parameter Value
Recommended Software
Web browser Netscape 4.x or Internet Explorer 4.x or later
PC operating system Windows 95/98 or later
Terminal emulation Hyperterminal
Environmental
Frame temperature range 0 to 45° C
Operating humidity range 0 to 90% non-condensing
Non-operating temperature 0 to 45° C
Mechanical
Frame type Gecko and Gecko Flex 8900 Series
RS-232 connector DB-9 Female
Ethernet connector RJ-45
Frame alarm connector DB-9 Female or BNC (depending on frame model)
Power Requirements
Supply voltage ± 12 V
Power consumption < 6 W
70 8900NET Instruction Manual
Appendix
Compatibility Matrix
The compatibility matrix in Tab le 7 lists the modules that can reside in the
8900TFN frame, features that are supported, the module assembly
numbers and how software updates are handled. For the latest information
on any module, software available and the Release Notes and latest Instruction Manual, visit the Support link on the Grass Valley web site (refer to
Contacting Grass Valley at the beginning of this manual).
Table 7. 8900 Software Compatibility Matrix
Model # Assembly #
8931
8936
8941
8916
8920DAC
8920ADC
8920ADT
8920DMX
8920MUX
8921ADT 671-6496-00 full c&m – ftp download
8921DAC 671-6497-00 full c&m – 8900-FLOAD_CBL
160169-00 no comm – n/a
160170-00 no comm – n/a
160171-00 no comm – 8900-FLOAD-CBL
671-4853-00 basic status Id defect, faults not reported Not upgradeable
671-4853-01
671-4853-02
671-4795-00
671-4795-01
671-4795-02
671-4795-03 –
671-4796-00
671-4796-01
671-4796-02
671-4796-03 full c&m –
671-6326-00
671-6326-01
671-6291-00
671-6291-01
671-6291-02
671-6291-03
671-6290-00
671-6290-01
Control &
Monitoring
Support
full c&m – 8900-FLOAD-CBL
full c&m
basic status
full c&m – 8900-FLOAD-CBL
full c&m – 8900-FLOAD-CBL
full c&m – 8900-FLOAD_CBL
Control & Monitoring
1
Id defect, faults not reported
Id defect, faults not reported
Notes
Faults not reported
Faults not reported
2
Software
Update
8900-FLOAD-CBL
8900-FLOAD-CBL
3
3
3
3
3
3
3
3
8900NET Instruction Manual 71
Appendix
Table 7. 8900 Software Compatibility Matrix - (continued)
Model # Assembly #
Control &
Monitoring
Support
Control & Monitoring
1
Notes
2
Software
Update
8937/8937D 671-6554-00/-10 full c&m – 8900-FLOAD-CBL
8950DAC
8950ADC
671-4798-00
671-4798-01
671-4798-02
671-4798-03
671-4799-00
671-4799-01
basic status faults not reported
full c&m –
basic status faults not reported
8900-FLOAD-CBL
8900-FLOAD-CBL
671-4799-02 full c&m –
671-4664-00 no comm misleading status reported
8960DEC
671-4664-01
full c&m –671-4664-03
8900-FLOAD-CBL
671-4664-04
8960ENC
8964DEC
8964ENC 671-6477-00 full c&m Requires 8900NET v3.2.0
8964FS 671-6477-50 full c&m Requires 8900NET v3.2.2
8964MON 671-6477-20 full c&m Requires 8900NET v3.2.0
8990ARC
8981FS
671-4698-00
671-4698-01
671-6471-00 full c&m Requires 8900NET v3.2.0
full c&m – 8900-FLOAD-CBL
NetConfig or
ftp download
NetConfig or
ftp download
NetConfig or
ftp download
NetConfig or
ftp download
671-5246-00 full c&m – 8900-FLOAD-CBL
671-5023-00
671-5023-01
full c&m – 8900-FLOAD-CBL
8981NR 671-5023-10 full c&m – 8900-FLOAD-CBL
8500 Series
8800 Series
1
See Control and Monitoring Support on page 73 for definitions
2
See Control and Monitoring Notes on page 73 for definitions
3
See 8900–FLOAD–CBL Assembly on page 73 for information
For 8500 and 8800 Series module compatibility see Legacy Module Support on page 33.
3
3
3
3
3
3
3
3
72 8900NET Instruction Manual
Control and Monitoring Support
The following abbreviations are used to indicate the features supported or
not supported by the modules listed in Tab le 7:
• No comm — The module does not support any remote control or monitoring functions.
• Basic status — The module responds to only low-level probe from the
Network module and only returns model number and description.
Fault and signal presence are not reported. No control is supported.
• Full C&M — The module fully supports the control and monitoring
system. The module reports status of all settings. The module can be
configured remotely.
Control and Monitoring Notes
The following abbreviations are used in Tab le A- 7 to indicate performance
limitations for the listed legacy modules:
Compatibility Matrix
• Comm problem — The module shorts out the frame communication
bus. When the problem module is installed, the NET module cannot
communicate with any of the modules in slots 1 through 10.
• ID defects — The module is susceptible to ESD (electro-static discharge)
damage of the module ID lines. If this damage occurs, the module will
be reported as faulted on the frame status page and software download
will not work.
• Faults not reported — The module may not report an error to the NET
module even though its fault LED is on. The LED gives the correct fault
status.
• Misleading status reported — The module does not support control
and monitoring but indicates through a motherboard connection that it
does. This module will show up as red on the frame status page even if
it is working correctly.
8900–FLOAD–CBL Assembly
Some modules require a cable assembly and software loading application
for the software update process. This cable assembly and CD–ROM containing update software files can be ordered from Grass Valley. Contact
your Grass Valley sales or service representative about ordering the
8900-FLOAD–CBL assembly.
8900NET Instruction Manual 73
Appendix
8900NET Software Update From FTP Server
If you are updating an 8900NET module with a software version earlier
than version 3.2.0, you must use the following procedure.
FTP Method Overview
The Modular Remote Monitoring and Control System is an extension of the
Grass Valley Signal Management System (SMS) routing system and uses
the same File Transfer Protocol (FTP) technique to download software.
Note This procedure assumes your Local FTP Server computer is a 32-bit
Windows host running Win95, 98, NT or later.
If you do not have an FTP server, Grass Valley provides a free FTP server
package that is easy to install and operate. This procedure assumes you will
use the Xitami FTPD provided. If you already have an FTPD available, you
can skip steps 3 through 5.
The software update process consists of the following steps:
1. Acquire the software update files and, if needed, the FTP Server
package.
2. Place the module software update files into an FTPD modular directory.
3. Extract the FTP Daemon (Xitami FTPD).
4. Run the Xitami installation program.
5. Modify the FTPD configuration files to the Xitami directory.
6. Start the FTPD.
7. Use the 8900 GUI to initiate software updates.
Note When updating numerous Gecko 8900 modules, it is a good idea to dedicate
one frame for the update process to avoid interrupting communication with
active modules.
8. Verify the software update results.
74 8900NET Instruction Manual
FTP Software Update Procedure
1. Acquire the software update files from Grass Valley (refer to Acquiring
Software Updates on page 51).
a. Create a temporary download directory on your PC:
c:\temp\
b. Using the web browser, select the desired .fld zipped file.
c. Click to download the .bin (8900NET only), .fld (8900 media
modules) or zipped file. You are queried to either
SAVE AS. Select the SAVE AS option and set the path to the temporary
directory on your computer.
This process will trigger the download of the file to your computer.
Note If you have access to an existing FTP Server’s directory, the module update
files can be downloaded directly into that directory.
2. Move or extract the module update files into an FTPD modular
directory.
8900NET Software Update From FTP Server
OPEN the file or
The module software update files must reside in a directory that the
FTPD can access. The Grass Valley supplied FTPD is configured to
access a directory designated:
\modular\8900
The new software for the 8900NET module (version 3.2.0 and later) will
be a binary file (.bin extension) or a field update files (.fld extension).
a. Open Windows Explorer on the local server computer.
b. If one does not already exist, create a directory on the C drive:
c:\modular\8900
c. Double-click the module software.exe file (in the temporary
directory) and save it to the appropriate directory. The resulting file
will be a .bin or .fld:
c:\modular\8900\8900net_sw400a_fw1.bin
Note The file name shown indicates: 8900NET, software version 4.00, firmware
version 1.0.
3. Extract the FTPD (Xitami FTP Server) files.
8900NET Instruction Manual 75
Appendix
Note This section is for facilities that do not already have an FTP Daemon (FTPD),
also known as a File Transfer Protocol (FTP) Server, installed on the Gecko
8900 frame’s network. For those facilities that already have an FTPD or other
FTP Service available in their network, go to step 6.
Grass Valley provides a free FTP server for those facilities that do not
have a local FTP service. The FTP server package is the same Xitami
Web Server-FTP package that is provided with the Grass Valley SMS
router upgrade package. The version of the Xitami Web-FTP server distributed with module software upgrades is for a 32-bit Windows host.
The FTP Daemon in the temporary directory is a self-extracting file
(ftpd.exe). To extract the files:
a. Open Windows Explorer and find the ftpd.exe file.
b. Double click on the .exe file and extract the files to C:\temp.
These files will be extracted:
• xic3223c.exe – the Xitami installation file,
• defaults.cfg – an FTPD configuration file that has been modified
specifically for Grass Valley software downloads, and
• ftpusers.sms – the FTPD’s admin file specifying user names and
passwords network access to files in the ftp server directories.
4. Run the Xitami installation program.
a. Double Click on xic3223c.exe. You will see the Xitami Welcome
(Figure 40). Click on
Figure 40. Xitami Web Server Welcome
Next >.
76 8900NET Instruction Manual
8900NET Software Update From FTP Server
b. You will see the Xitami Installation Notes (not shown). Click on
Next >.
c. You will see Select Destination Directory (Figure 41). Do not change
the default settings. Click on
Figure 41. Select Destination Directory
Next >
d. You will see the Select Program Group screen (Figure 42). Do not
change the default settings. Click on
Figure 42. Select Program Group
Next >.
8900NET Instruction Manual 77
Appendix
e. You will see the Automatic Startup Query screen (Figure 43). Select
No. Click on Next >.
Figure 43. Automatic Startup Query
f. You will see the Administration Password screen (Figure 44). Do
not enter anything in these fields. Click on
Figure 44. FTPD Server Administration Password
Next >.
78 8900NET Instruction Manual
8900NET Software Update From FTP Server
g. You will see the Choose Server Profile screen (Figure 45). Select
Tiny - never block another task. Click on Next >.
Figure 45. Choose Server Profile
h. You will see the Ready To Install screen (Figure 46). Click on Next >
to begin installation.
Figure 46. Ready to Install
8900NET Instruction Manual 79
Appendix
i. An installation meter box will appear as shown in Figure 47.
Figure 47. Installation Meter Box
j. Upon completion, you will see the Installation Complete! screen
(Figure 48). Click on
Figure 48. Installation Complete
Finish.
80 8900NET Instruction Manual
8900NET Software Update From FTP Server
An Icon (see Figure 49) will have been created in the Program
Group window that was selected during installation (see Figure 42
on page 77).
Figure 49. FTPD Icon in Program Group Window
5. Move the FTP Daemon Start-up Configuration Files.
The FTP Daemon has now been installed and requires configuration files
be placed in the Xitami directory.
a. Open Windows Explorer.
b. From the Explorer window, return to the FTPD directory and move
the extracted defaults.cfg and ftpusers.sms files to the directory at:
c:\Program Files\Xitami
The defaults.cfg and the ftpusers.sms files contain default configuration instructions that the FTPD application reads at start-up.
8900NET Instruction Manual 81
Appendix
6. Start the FTPD.
If the Xitami Web Server (FTPD) is not already running, start it.
a. Click on the Start popup window on the PC.
b. Select PROGRAMS, then INTERNET TOOLS, and click on Xitami Web Server
– 32 bit console
The Xitami Console will open as a DOS window. There will be a log
of events, at least one of which will indicate it is accepting connections (see Figure 50).
Figure 50. Typical FTPD Console Screen
(Figure 49 on page 81).
The IP Address line should actually indicate the IP address of the
PC you are using for the FTP server. This is the IP Address that will
be used to initiate the software update.
The line that verifies that the FTPD is running reads:
ready for FTP connections on port 21
82 8900NET Instruction Manual
8900NET Software Update From FTP Server
Password Protection for Software Upgrades
The FTPD distributed for software downloads provides user name and
password protection for software updates. User name and password entry
is required in the Software Update web pages.
The assignment of user names and passwords for a given FTP root directory is administered by editing the ftpuser.sms file included in the FTPD
distribution (see Step 3 of this procedure). This file initially contains the
default user name and password (user name: moduser, password:
moduser) for access to the modular root directory and instructions for
setting up an account.
The contents of the file are shown in Figure 51. (The file also includes the
SMS7000 account for customers with Thomson Grass Valley SMS routers.)
Figure 51. User Name and Password File ftpuser.sms
Note The FTPD configuration files should be installed in a password protected
directory.
8900NET Instruction Manual 83
Appendix
Upgrading Software
With the FTPD running, use the 8900 GUI to initiate software updates. Use
the web-browser to:
• Access the appropriate Software Update page for a given module,
• Enter the required data into the HTML Form on that page, and
• Submit the form.
The 8900 frame uses the data in the form to contact the FTPD on the
server, download the update file, and reprogram the targeted module.
Note Prior to attempting update of software, refer to the target module’s manual
and confirm that the Remote/Local Only jumper is in the Remote position.
Note To monitor the progress of the download, you may use the serial port con-
nection (see Figure 52 on page 85) with a computer running a terminal emulation application.
84 8900NET Instruction Manual
8900TFN Frame
8900NET Software Update From FTP Server
Figure 52. Serial Port Console and PC Network Connections
PC running Hyperterm Terminal Emulation
RS-232
8900TFN Frame
Comm 1 or
Comm 2 port
Serial Connection for console interface
Comm. Parameters: 9600 baud, 8 bits,
parity-none, 1 stop, flow-none
PC running web browser GUI
Ethernet
RJ-45
connector
To PC network card
RJ-45 connector
Ethernet Hub
0612 -29r1
8900NET Instruction Manual 85
Appendix
a. Open a web browser on a PC that is connected over the network to
the Gecko 8900 frame.
b. Enter the URL of the frame where the module to be updated resides.
The frame’s main status page will appear.
c. Click on the module’s link and then click on Software Update (the
8900NET module link is shown at left).
Use
this
link
The module’s Software Update web page will appear as shown in
Figure 53. This form is the same for all 8900 modules that support a
network software update.
Figure 53. 8900NET Module Software Update Page
d. In the FTP Server Address field, enter the IP Address of the PC that
has the FTPD installed and running.
e. You can enter the Host Name of the PC that has the FTPD running
into the FTP Server Name field. This is an optional step and can be
omitted.
f. Click on Apply to set the FTP Address.
The web page will refresh and the new FTP address should be displayed as the current setting.
g. In the File Path field, enter the FTP file path of the software update
file.
The FTP file paths use forward slashes. The directory name “/modular” is not needed in the path name.
86 8900NET Instruction Manual
8900NET Software Update From FTP Server
h. Submit the form and start the update process by entering the user
name and password and clicking on
By default, the Xitami Server has been configured to accept a user
name of “moduser” and a password of “moduser” for the modular
root directory. This may be changed by modifying the ftpusers.sms
file in the C:\Program Files\Xitami directory (see Password Protec-
tion for Software Upgrades on page 83).
Apply.
After you click on
the Progress Monitor (Figure 54).
If an incorrect file name or password is entered, the Progress
Monitor will report the condition and allow you to go back to the
Software download page and re-enter the correct information.
The module software compatibility check uses compatibility information included in the Field Update File to ensure that the new software was intended for this module. In the event that there is a
mismatch, the Net Board will abort the upgrade.
Note Do not make any changes to the web page during the software download.
i. If the file entered in the file path is invalid or the file cannot be
found, a
Results line (Figure 54). Select the Software Download link or the
Refresh button to refresh the page to return to the download page
and re-enter the file name.
Figure 54. 8900NET Software Download Progress Monitor
File Not Found message will appear in the Progress Monitor
Apply, the web page will be reloaded, displaying
j. If the login password is incorrect, the Progress Monitor will report
with a
Software Download link or refresh the page to return to the
download page and re-enter the correct login.
8900NET Instruction Manual 87
Login Incorrect message as shown in Figure 55. Select the
Appendix
Figure 55. Login Incorrect
k. Once the download has started and there are no error messages,
wait for the Success screen to appear, then click on Software Update
or the
Note Do not click anywhere on the web page while the download is in progress
Once the download is successful, the Progress Monitor will report
a Success message similar to Figure 56.
Figure 56. 8900NET Software Update Failure Notice
Refresh button again to refresh the page.
unless you receive a File Not Found or Login Incorrect Results message.
l. Verify the software update results by checking the Installed
Software Version in Properties portion of the 8900NET Status web
page.
The software and firmware (if applicable) numbers should match
that indicated in the .bin or .fld file name (see Step 2 of this procedure for file names and version numbers).
88 8900NET Instruction Manual
Unsupported Software Updates
If the 8900 module does not support network software updates, the Software Update web page may indicate software updating is not supported as
shown in Figure 57.
These modules require a special cable kit (8900-FLOAD-CBL with Instruction Manual) available from Grass Valley Sales or Service to perform a software update. Details for the module will be available in the specific module
release notes that accompany the upgrade.
Note Always read the Release Notes for the specific module for the latest software
download procedure before attempting to download software.
Figure 57. Software Update Not Supported
8900NET Software Update From FTP Server
8900NET Instruction Manual 89
Appendix
90 8900NET Instruction Manual
Index
Numerics
25-pin adaptor 14
8900 frame
status reporting
19
A
agent software (SNMP) 44
asset tag, assigning 44
B
backplane 10
baud rate 12
block diagram 67
C
cable
crossover
Ethernet 15
LAN 16
RS-232 12
cable kit 12
Clear button 50
Comm 1 port 13
compatibility matrix 71
Configuration web page (8900NET module) 44
Configuration web page (Frame) 34
controller module 9
15
D
daemon 74
default MAC address 29
DIP switches
alarm control
disables 20
documentation online 2
domain name server 25
20
E
enable fault reports 20
environmental 70
Ethernet 15
F
FAQ database 2
fault condition 32
FAULT LED
troubleshooting
fault reports
filtering
faulty module 54
firewall 25
flow control 12
frame 9, 70
cell 9
Frame Alarm
cabling
overview 22
Frame Health Alarm
cabling
frame ID 29
Frame Monitor Module 12
frame name and location 34
Frame Power Supply web pages 42
Frame Status page 22
frame status page 29, 30
frame types 28
frequently asked questions 2
FTP server 74
ftp site 24
20
12
12
21
G
gateway IP address 48
Gecko Flex
8900NET installation
9
8900NET Instruction Manual 91
Index
frame connectors 11
Grass Valley web site 2
I
initial configuration 25
Internet Explorer 28
IP Address
setting
storage 28
25
L
LED indicators 17
link list 30
local area network (LAN) 8
Locate Frame function 34
locate module 49
LogPrint procedure 62
M
MAC (machine) address 29
module
installation
module compatibility 71
Module Health Bus 19
module health status 19
module slot names 49
Module Status page 22
9
N
navigation 30
NET module reboot 48
NetConfig 25
feature 7
Netscape Navigator 28
network addresses 48
network configuration storage 28
network conflicts 29
network identity 25
network parameters 25
establishing 25
network traffic delays 25
Network web page (8900NET module) 48
NIM LED 17
O
on-board configuration switches 43
online documentation 2
P
parity 12
point-to-point 8, 15
point-to-point communication 25
power 70
power supply 9
power supply slot 42
power supply, frame
web pages
42
R
reboot 48
reboot button 44, 48
repair depot 54
RJ-45 15
RS-232 12, 25
S
service information 54
Slot Config web page
media modules
slot memory 49
slot status icons 31
SMPTE Alarm BNC connector 12
SNMP monitoring
frame status reporting
overview 23
SNMP Trap Reports
2000NET module
frame 34
MIB (Management Information Base) 24
software compatibility 71
software download from web 2
software updating
49
34
46
92 8900NET Instruction Manual
acquiring software 51
modules not supported 89
NetConfig 52
overview 51
Status web page (8900NET module) 43
Status web page (Frame) 30
stop bits 12
subnet 25
subnet mask 48
supported features 71
switch status 43
T
testpoints 54
troubleshooting 54
LogPrint 62
Index
U
update status 32
updating 74
URL 29
V
voltage 70
W
Web browser 28
web site
documentation
FAQ database 2
Grass Valley 2
software download 2
2
8900NET Instruction Manual 93
Index
94 8900NET Instruction Manual
Loading...