X Gig Family Hardware

Xgig Family Hardware Guide
Notice Every effort was made to ensure that the information in this document was accurate at the time of printing. However, information is subject to change without notice, and JDS Uniphase Corporation reserves the right to provide an addendum to this document with information not available at the time that this document was created. Copyright Copyright June 2010 JDS Uniphase Corporation. All rights reserved. JDSU, ACTERNA, Test and Measurement Solutions, and the JDSU and Acterna logo are trademarks of JDS Uniphase Corporation ("JDS Uniphase"). All other trademarks are the property of their respective owners. No part of this guide may be reproduced or transmitted electronically or otherwise without written permission of the publisher. Trademarks JDS Uniphase Corporation and Xgig are trademarks or registered trademarks of JDS Uniphase Corporation in the United States and/or other countries. All trademarks are registered to their respective companies. Specifications, terms, and conditions are subject to change without notice. All trademarks and registered trademarks are the property of their respective companies. Technical Support Phone- US Toll Free- 1 866.594.2557 Phone- International- 1 408.546.7096 E-mail: techsupport-snt@jdsu.com Sales and Maintenance Support Phone- US Toll Free- 1 888.746.6484 Phone- International- 1 408.546.7096 E-mail: sales-snt@jdsu.com E-mail: insidesales.snt@jdsu.com Website: www.jdsu.com/snt/
ii
Federal Communications Commission (FCC) Notice This product was tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This product generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this product in a residential area is likely to cause harmful interference, in which case you will be required to correct the interference at your own expense. The authority to operate this product is conditioned by the requirements that no modifications be made to the equipment unless the changes or modifications are expressly approved by JDS Uniphase Corporation. WEEE Directive Compliance JDSU has established processes in compliance with the Waste Electrical and Electronic Equipment (WEEE) Directive, 2002/96/EC. This product should not be disposed of as unsorted municipal waste and should be collected separately and disposed of according to your national regulations. In the European Union, all equipment purchased from JDSU after 2005-08-13 can be returned for disposal at the end of its useful life. JDSU will ensure that all waste equipment returned is reused, recycled, or disposed of in an environmentally friendly manner, and in compliance with all applicable national and international waste legislation. It is the responsibility of the equipment owner to return the equipment to JDSU for appropriate disposal. If the equipment was imported by a reseller whose name or logo is marked on the equipment, then the owner should return the equipment directly to the reseller. Instructions for returning waste equipment to JDSU can be found in the Environmental section of JDSUs web site at. If you have questions concerning disposal of your equipment, contact JDSUs WEEE Program Management team at.
iii
iv
Contents
Contents
Contents
Chapter 1 Xgig Family ..................................................................................................................1 Xgig Family of Systems ........................................................................................2 Xgig Slotted Chassis .....................................................................................2 Xgig One Slot .........................................................................................3 Xgig Two Slot .........................................................................................4 Xgig Four Slot .........................................................................................5 Xgig Fixed-Port Systems ...............................................................................6 Xgig LX ...................................................................................................6 Xgig-LXP ................................................................................................8 Cascading ......................................................................................................9 Xgig System Ports/Connections/LEDs ................................................................10 Management Port ........................................................................................10 Console Port ................................................................................................10 Tap Port .......................................................................................................10 TTL Ports ..................................................................................................... 11 Cascade Ports ............................................................................................. 11 +12VDC Output Only ................................................................................... 11 Clock Out ..................................................................................................... 11 Other Xgig Ports ..........................................................................................12 Descriptions of Xgig System LEDs ..............................................................12 Descriptions of Link LEDs for an Xgig-LX System .......................................12 Descriptions of Port LEDs for an Xgig Fixed-Port System ...........................13 Chapter 2 Xgig System Setup....................................................................................................19 Unpacking the System ........................................................................................20 Installing Xgig Blades ..........................................................................................20 Locating the System in Your Environment ..........................................................21 Rack Mounting Instructions, Four Slot .........................................................21 Rack Mounting Instructions, Two Slot ..........................................................23 Rack Mounting Instructions, One Slot .........................................................24 Xgig System Overview ........................................................................................25 Xgig System and Application Images ..........................................................27 Xgig Server Software ...................................................................................28 Xgig Client Software ....................................................................................29 Xgig Access Through a Firewall ..................................................................29 Setup Instructions ...............................................................................................30
vi
Contents PATH 1: Setting Up the Xgig Chassis in a DHCP Network ..........................30 PATH 2: Setting Up the Xgig Chassis with a Static IP Address in a non-DHCP Network ............................................................32 PATH 3: Setting Up the Xgig Chassis in a Standalone Environment ...........36 Cascading Xgig Chassis .....................................................................................40 Xgig Chassis Startup Sequence .........................................................................43 Xgig Chassis Shutdown Sequence .....................................................................44 Shutdown Using the Web Utility Interface ...................................................44 Shutdown Using the Console Interface .......................................................44 Chapter 3 Administration...........................................................................................................45 Administration of the Xgig System over the Internet ...........................................46 Xgig Web Utility ...........................................................................................46 Accessing the Xgig System for Administration ............................................47 Logging In and Logging Out .................................................................48 System Requirements for Internet Administration .......................................49 Setting Client Authentication ...............................................................................49 Licensing .............................................................................................................50 Blade Licenses .....................................................................................50 Port-Pair Licenses ................................................................................50 Portable Licenses .................................................................................51 System Upgrades ...............................................................................................52 Setting Up the FTP Site for Upgrades .........................................................52 If You Already Have an FTP Site ..........................................................52 If You Need to Create an FTP Site .......................................................53 Updating the FTP Server with Upgrade Images ..........................................54 Upgrading the Xgig System Image and Application Image Software ..........54 Chapter 4 Tips and Troubleshooting ........................................................................................61 Troubleshooting ..................................................................................................62 No LEDs Are Lit on the Chassis ..................................................................62 The Power light is lit but other system LEDs do not light up ........................62 Power Up Problems Following Chassis Shutdown ......................................62 The Management port LED is not lit ............................................................63 The Ready LED is off ...................................................................................63 The Ready LED is yellow .............................................................................63 The Temp LED is yellow ..............................................................................63 Cannot Ping the Xgig Chassis .....................................................................64
vii
Contents Cannot Connect to the Xgig Chassis Using the Web Browser ....................65 Cant find the System or Application upgrade on FTP server ......................65 The system is rebooting repeatedly .............................................................66 The Cascade Port LEDs do not blink after initiating Sync Discovery ..........66 Sync Discovery Will Not Complete ..............................................................66 Cannot Find an Xgig Chassis Using the Discover Button in the Port Selection Window .......................................................................67 Auto Link Speed Detection Problems for SAS/SATA ...................................67 Restarting the Xgig Chassis with the Backup System Image .............................68 Tips .....................................................................................................................69 Pinging the Xgig Chassis .............................................................................69 Naming the Xgig Chassis ............................................................................69 Using Wireless Connections ........................................................................69 Network Bandwidth Considerations .............................................................69 Recommended System for more than 16 ports ...........................................70 Problems with Xgig Blade Memory .....................................................................71 Running Blade Diagnostics: ........................................................................71 Memory Re-Seating Instructions .................................................................76 Validating the Xgig Blade Memory ...............................................................78
viii
Chapter 1
Xgig Family
In this chapter:
Overview of the Xgig Family of Systems Xgig Ports/Connections/LEDs Xgig System Specifications
Chapter 1, Xgig Family
Xgig Family of Systems

The JDSU Xgig Family of Distributed Systems for Monitoring, Analysis, and Testing are multi-purpose systems designed for product development, field service, and network operations personnel. Xgig platforms can be rack-mounted or placed in a bench setup at your data center or anywhere on your network. Xgig chassis can also be directly connected to a PC to create a portable instrument for test or analysis. All Xgig systems can be accessed remotely using a LAN connection and JDSU software to perform tasks. System administration and configuration can be performed over the network.
Xgig Slotted Chassis

The Xgig slotted chassis are designed to accommodate a variety of blades for different applications. Xgig provides the necessary software tools running in a PC environment to perform the application task using the blades within the chassis. Xgig systems are available in one-slot, two-slot, four-slot models to support different network needs. Blades within an Xgig slotted chassis support a variety of different functions, line rates, and protocols. Multi-Function Blades can perform analysis, traffic modification, traffic generation, bit error rate testing, or load testing for Fibre Channel (FC), Gigabit Ethernet (GE), or SAS/SATA links. Not all blades support all functions, all protocols, or all speeds. Refer to the Xgig Blade Hardware Guide for complete information on all available blades.
Xgig One Slot (Shown with One Xgig Multi-Function Blade)

Port 1 Port 2 Port 3 Port 4
1
Xgig Multi-Function Blade
O O O O O O O O O O O O O O O O
O ............. In Use ........... O O................Link............... O O............. LED x............. O O............ LED y............. O
Finisar gig
Xgig One Slot
Xgig Family Hardware Guide Figure 1: Xgig One Slot

Tap
Finisar
Console
..... ....
O O O O
Status Temp Ready Power
..... ....
Cascade Ports 10/100/1000 LAN Ethernet Connection for Software Control and Configuration
In
Cascade Out In Management Ultra2 SCSI
Trigger Out
Console Port for Local Configuration
System LEDs
The Xgig One Slot has a single slot for a JDSU blade.
Used for CLE or as Console port when using Xgig Dongle license TTL Input/Output to Other Devices
SCSI Port for Capture to Disk (Ultra2 SCSI SE/LVD Cable Required) (Reserved for Future Use)
4
Xgig Two Slot (Shown with Two Xgig Multi-Function Blades)
1
O O O O O O O O O O O O
O ............. In Use ........... O O................Link............... O O............. LED x............. O O............ LED y............. O O O O O
Finisar gig
Xgig Two Slot
Finisar
2
Tap In Cascade Out In Management Ultra2 SCSI Trigger Out
O O O O O O O O O O O O O O O O
Figure 2: Xgig Two Slot
Finisar
Console
..... ....
O O O O
..... ....
Cascade Ports 10/100/1000 LAN Ethernet Connection for Software Control and Configuration
The Xgig Two Slot has two slots for JDSU blades.
System LEDs
TTL Input/Output to Used for CLE or as Other Devices Console port when using Xgig Dongle license
Xgig Four Slot (Shown with Four Multi-Function Blades)

Port 4 Port 1 Port 3 Port 4 Port 2
Xgig Four Slot
Port 1
Port 2
Port 3

O Xgig Multi-Function Blade
Port 4 Port 1 Port 3 Port 4 Port 2
1
O O O O Xgig Multi-Function Blade O O O O O
O O O O O O O O O O O O
O............. In Use ........... O O................Link............... O O............. LED x............. O O............ LED y............. O O O O O
Finisar gig
Finisar
Finisar
Port 1
Port 2
Port 3
Figure 3: Xgig Four Slot
2
O O O O O O O O O Xgig Multi-Function Blade
Management Ultra2 SCSI
O O O O O O O O O O O O O O ............. In Use ........... O O................Link............... O O............. LED x............. O O............ LED y............. O O O O O
O............. In Use ........... O O................Link............... O O............. LED x............. O O............ LED y............. O
Finisar Finisar

Power
Console
Tap
..... ....
O O O O
..... ....
10/100/1000 LAN Ethernet Connection for Software Control and Configuration System LEDs
In
Cascade Out
In
Trigger Out
Power
The Xgig Four Slot has four slots for JDSU blades.
Cascade Ports
Used for CLE or as Console port when using Xgig Dongle license
TTL Input/Output to Other Devices
Xgig Fixed-Port Systems

An Xgig fixed-port system is a self-contained Xgig system. These systems are available as either fixed-function (Analyzer) or multi function. All ports, connectors, and controls found on an Xgig chassis containing Xgig blades are present on these systems. The multi-function system ports can support a variety of different functions depending on the license for the system ports. Possible functions include analysis, traffic modification, and traffic generation. Xgig fixed-port systems consist of four major elements: serial gigabit connection, real-time performance measurement, filter and trigger, and capture to memory. Xgig fixed-port systems ensure both accurate data collection and transparency on the link. The system has sophisticated triggering and filtering to isolate error conditions in the data. Pre-capture filtering can expand the capture time to minutes. Xgig provides the necessary software tools running in a PC environment to perform the application task using the fixed-port system. These systems are designed for bench setup. All chassis in the Xgig Family share the same type of I/O ports for device control and network management. JDSU offers the following two fixed-port systems: Xgig 6 Gigabit SAS/SATA Wide Port Analyzer (Xgig-LX) Xgig 6 Gigabit SAS/SATA Multi-Function System(LXP)
Xgig LX The Xgig-LX has eight SAS/SATA Analyzer ports (4 links) that support a maximum line rate of 6.0 Gbps. This fixed-port system does not require or accept Xgig blades. The Xgig-LX is a bench setup. It is not rack-mountable. The Xgig-LX has two female mini-SAS connectors on the front. One connector is typically used for connection to the target, and the other is used for connection to the host. Either port can be used for the host or the target. Standard mini-SAS cables are supplied with the system. The signals from a mini-SAS connector can be split into single-port outputs (or, single-port inputs can be consolidated into a mini-SAS connector) by using a hydra type cable. Using a hydra cable, the Analyzer can be configured to monitor between a single host and up to four drives.
6 Gigabit SAS/SATA Wide Port Analyzer Port LEDs Clock Out (SMA Connector) CLE Power Output
Ports 1, 3, 5, 7 Signal FrameError Trigger 2- O O O O 4- O O O O 6- O O O O 8- O O O O Clock Out +12VDC Output Only Ports 2, 4, 6, 8
Figure 4: Xgig-LX

Mini-SAS Connectors Finisar gig
In Trigger Out Management Ultra2 SCSI Power
Link LEDs
6 Gigabit SAS/SATA Wide Port Analyzer
In Use Rate 1, 2 O O 3, 4 O O 5, 6 O O 7, 8 O O
Signal FrameError Trigger 1- O O O O 3- O O O O 5- O O O O 7- O O O O
Console
Tap
In
Cascade Out
..... ....
O O O O
..... ....
10/100/1000 LAN Ethernet Connection for Software Control and Configuration System LEDs
Power
Cascade Ports
This system supports Xgig Link Extender (LE) and Configurable Link Extender (CLE).
TTL Input/Output to Other Devices
Xgig-LXP The Xgig-LXP has four multi-function SAS/SATA ports (2 links) that support a maximum line rate of 6.0 Gbps. This fixed-port system does not require or accept Xgig blades. The Xgig-LXP is a bench setup. It is not rack-mountable. The Xgig-LXP supports the following functions: Capture/Analysis (Xgig Analyzer function) Traffic Modification (Xgig Jammer function) Traffic Generation (Xgig Generator function) Traffic Emulation (Xgig Target Emulator function)
The Xgig-LXP has two female mini-SAS connectors on the front. One connector is typically used for connection to the target, and the other is used for connection to the host. Either port can be used for the host or the target. Standard mini-SAS cables are supplied with the system. The signals from a mini-SAS connector can be split into single-port outputs (or, single-port inputs can be consolidated into a mini-SAS connector) by using a hydra type cable. This system supports Xgig Link Extender (LE) and Configurable Link Extender (CLE).
Cascading
6 Gigabit SAS/SATA Analyzer Mini-SAS Connectors
Xgig Family Hardware Guide Figure 5: Xgig-LXP

Port LEDs Clock Out (SMA Connector)
Signal FrameError 1- O -- O -- O 2- O -- O -- O 3- O -- O -- O 4- O -- O -- O Ports 1, 3 Ports 2, 4 Clock Out
CLE Power Output
+12VDC Out Only
Finisar
gig
Ultra2 SCSI In In Cascade Out Trigger Out Management
Console
Tap
..... ....
Cascade Ports
..... ....
O O O O
6 Gigabit SAS/SATA Multi-Function Xgig System Xgig C012-6G-P
10/100/1000 LAN Ethernet Connection for Software Control and Configuration
System LEDs
Up to four Xgig chassis can be cascaded together to provide a sync group with up to 64 ports. Refer to Chapter 2 for information on cascading Xgig chassis.
TTL Input/Output to Other Devices SCSI Port for Capture to Disk (Ultra2 SCSI SE/LVD Cable Required) (Reserved for Future Use)
Xgig System Ports/Connections/LEDs

Management Port
The Management port provides a connection to the 10/100/1000 network or a direct connection to a PC's 10/100/1000 Ethernet adapter. The Management port is used for the following: Configuring the Xgig chassis using the Xgig Web Utility Controlling the operation of Xgig application-specific blades Retrieving data collected by Xgig application-specific blades
Console Port
The Console port is one of the 9-pin serial ports on the left. The Console port is used for the following: Configuring the Xgig chassis Selecting the Xgig boot image Minor troubleshooting
The Console port can be used for all system configuration through a command line interface. Configuration commands are passed to Xgig by connecting the Console port to a terminal or to a PC with a terminal emulation program. However, Configuration is usually performed using the Xgig Web Utility over the internet through the 10/100/1000 Ethernet management port.
Tap Port
The Tap port is one of the two 9-pin serial ports on the left. The CLE uses the Tap port to connect to the CLE software. The Tap port may also be used as a Console port when the Xgig dongle license is being used. The Dongle must be plugged into the Console port to function. In this case, the Tap port is used for the following: Configuring the Xgig chassis Selecting the Xgig boot image Minor troubleshooting
10
When acting as a Console port, the Tap port can be used for all system configuration through a command line interface. Configuration commands are passed to Xgig by connecting the Console port to a terminal or to a PC with a terminal emulation program. However, Configuration is usually performed using the Xgig Web Utility over the internet through the 10/100/ 1000 Ethernet management port.
TTL Ports
The TTL Input and TTL Output ports provide a means of sending or receiving an electrical signal between the Xgig and other instruments for triggering purposes. The trigger-out pulse is approximately 200ns wide, active-high, LVTTL (3.3V). The trigger-in can handle 3.3V or 5.0V inputs, also active-high.
Cascade Ports
The Cascade In and Cascade Out ports provide a means of time-synchronizing up to four Xgig chassis. Cascaded chassis provide a sync group resource with up to 64 ports. Cascade Ports are used to share domains and send triggers between chassis. Cascade ports use standard RJ-45 connectors and CAT5 cables to connect, but use JDSUs proprietary protocol to communicate between cascaded units.
+12VDC Output Only

This port is only available with Xgig fixed-port systems. The +12VDC port is used to supply power to an Xgig Link Extender (LE) or Configurable Link Extender (CLE). Use the +12VDC power cable included with the LE or CLE to connect to this port.
Clock Out
This port is only available with the Xgig fixed-port systems. The Clock Out port provides a means of using the clock out signal to measure the eye diagram of the output signal from the Analyzer.
11
Other Xgig Ports

The SCSI port on the chassis is not used at this time.
Descriptions of Xgig System LEDs

There are four LEDs that provide indications for the Xgig system.
Table 1: System LEDS for Xgig Systems Status Reserved for future use. Indicates any temperature problems with the unit. Solid green light means the temperature is OK. Blinking yellow light means the temperature is nearing critical. Solid yellow light means the temperature is critical. The FPGA will shutdown causing blade to stop functioning and server applications using the blade to terminate. The Xgig operating system remains up and running. Indicates if the system is ready for use. A solid green light means that the Xgig operating system is up and running and has obtained a valid IP address. A yellow light means that the system is not properly configured. Indicates if power to the Xgig system is ON or OFF. Solid green light means power is ON.
Temp
Ready
Power
Descriptions of Link LEDs for an Xgig-LX System

There are two LEDs that provide indications for each link or port pair.
Table 2: Link LEDs for a Fixed-Port Xgig System LED In Use Color Green Locked Indicates that the Analyzer port is locked for use by an Xgig application. Lower Rate 1.5 Gb/s or 3Gb/s Color Yellow N/A OFF Not Locked The Analyzer port/link is available.
Rate
Highest Rate 6.0 Gb/s or Auto
N/A
12
Descriptions of Port LEDs for an Xgig Fixed-Port System

There are four LEDs that provide indications for each port.
Table 3: Port LEDs for an Xgig Fixed-Port System LED Signal Color Green Signal present;
OOB complete and link established
Color Yellow OOB Signaling in process N/A
OFF N/A
Frame
Indicates that SOFs have been detected within the past sampling period. N/A
No SOF Detected
Error
Phy error detected: No Errors Detected indicates a disparity, CRC, primitive, framing, or code violation error has been detected on the link within the past sampling period (50-200ms) The Analyzer port is either stopped or is running but has not been triggered.
Trigger (only applicable to Xgig-LX)
Indicates that a trigger N/A event has occurred and the Analyzer port is currently completing the post-fill of its buffer.
Note: If a trigger was set in TraceControl, the Triggered LED only lights up after the trigger event while the buffer is being filled; at other times, the LED remains off.
13
Xgig System Specifications

Table 4: Physical Specifications, Xgig Two Slot Height Width Depth Weight Mount 3.4 in. / 8.7 cm. 10 in. / 25.4 cm. 15.2 in. / 38.6 cm. 11.0 lbs. / 5.0 kg (no blades) 13.2 lbs. / 6.0 kg (two blades) 19.0 in., with rack mounts
Table 5: Physical Specifications, Xgig Four Slot Height Width Depth Weight Mount 3.4 in. / 8.7 cm. 15.2 in. / 38.6 cm. 12.7 in. / 32.3 cm. 13.5 lbs. / 6.1 kg (no blades) 18.0 lbs. / 8.2 kg (four blades) 19.0 in., with rack mounts
Table 6: Physical Specifications, Xgig-LX Height Width Depth Weight Mount 3.4 in. / 8.7 cm. 15.2 in. / 38.6 cm. 12.7 in. / 32.3 cm. 17.0 lbs. / 7.7kg No rack mount
Table 7: Physical Specifications, Xgig-LXP Height Width Depth Weight Mount 2.44 in. / 6.2cm. 11.88 in. / 30.2cm. 13.44 in. / 34.1cm. 5.0 lbs. / 2.3kg No rack mount
14
Table 8: Power Specifications, Xgig Two Slot Power Consumption Fuse Protection Input Voltage Range Input Frequency Inrush Current (Peak) 200W 4.0A 250V 90-132/180-264 VAC 50/60 Hz 40A Maximum
Table 9: Power Specifications, Xgig Four Slot Power Consumption Fuse Protection Input Voltage Range Input Frequency Inrush Current (Peak) 520W 10A 250V 90-265 VAC 50/60 Hz 50A Maximum
Table 10: Power Specifications, Xgig-LX Power Consumption Fuse Protection Input Voltage Range Input Frequency Inrush Current (Peak) 520W 10A 250V 90-265 VAC 50/60 Hz 50A Maximum
Table 11: Power Specifications, Xgig -LXP Power Consumption Fuse Protection Input Voltage Range Input Frequency Inrush Current (Peak) 130W 2.5A 250V 90-132/180-264 VAC 50/60 Hz 40A Maximum
15
Table 12: Port Specifications Console Port Tap Port Management Port SCSI Port Cascade Ports TTL Input 9-pin serial port connects to PC 9-pin serial port connects to CLEs 9-pin serial port 10/100/1000 RJ-45 Ultra 2 SCSI SE/LVD (reserved for future use) RJ-45 connection to additional units (straight-through cable only) BNC Connector for Trigger IN (thin coaxial cable only) The trigger-in can handle 3.3V or 5.0V inputs, active-high. BNC Connector for Trigger OUT (thin coaxial cable only) The trigger-out pulse is approximately 200ns wide, active-high, LVTTL (3.3V). Power connector for Xgig LE or CLE Voltage is +12VDC (Xgig fixed-port systems only) SMA connector for clock out signal AC coupled, LVPECL compatible, 800mV p-p (Xgig fixed-port systems only)
TTL Output
+12VDC Power Output Only Clock Out
Table 13: Environmental Specifications Temperature Operational Non-operational Humidity Operational Non-operational
10 to +40 C (50 to +104 F) -40 to +70 C (-40 to +158 F) Up to 90% humidity (non-condensing) at +40 C Up to 95% humidity at +65 C.
16
Chapter 1, Xgig Family Table 13: Environmental Specifications Vibration Operational Non-operational
Random Vibration 5-500 Hz, 10 minutes per axis, 2.41g (rms) Random vibration 5-500 Hz, 10 minutes per axis, 0.3 g (rms) Resonant search, 5-500 Hz swept sine, 1 octave/min. sweep rate, 0.75 g, 5 minute resonant dwell at 4 resonances/axis FCC Class A, CE Compatibility UL
Electromagnetic Compliance Safety
17
18
Chapter 2
Xgig System Setup
In this chapter:
Unpacking the Xgig System System Placement, including Rack Mounting Xgig System Overview Xgig Firewall Access Setup Instructions Xgig Startup Sequence Cascading Xgig Chassis
19
Chapter 2, Xgig System Setup
Unpacking the System

Inspect Xgig system packaging and its contents for visible damage. If you notice any damage, please contact JDSU immediately. When you receive your Xgig system, the package will contain the following items: Xgig Chassis Xgig System Server Software CD-ROM Xgig Family Hardware Guide (this document) 100-120 V Power Cord RJ-45 Straight-Through Cable DB-9 Null Modem Cable Warranty Rack Mounting Brackets and Screws (if applicable)
Please check the contents of your Xgig system package to make certain you have received all the components on this list. If any items are missing, please contact JDSU immediately. Customers that do not have access to a 100-120V power supply will need to supply their own power cord.
Installing Xgig Blades

Xgig Blades are distributed in a separate package. Refer to the Hardware Guide that accompanies the blade hardware for installation information. You can install blades before or after you perform the procedures in this guide to set up the Xgig chassis. Note that the 3G Xgig Multi-Function Blade can support SAS/SATA through special adapters. Refer to the Blade Hardware Guide for information. Note also that the 3G/6G SAS/SATA Wide-Port/4x Blade requires minor modifications to the chassis to support the blade. Refer to instructions in the Xgig Chassis Modifications to Support the 3G/6G SAS/SATA Wide-Port/4x Blade for information. These instructions are shipped with the blade.
20
Locating the System in Your Environment

Place your Xgig system in a location where you have easy access to the following: Physical connection to your local area network A socket outlet supplying 110-115V power (or 200-240V for international).
The socket-outlet shall be installed near the equipment and shall be easily accessible. Surge protection should be provided between the Xgig chassis and the power supply. If you want to rack-mount your Xgig system, follow the instructions below.
Rack Mounting Instructions, Four Slot

Use a screw driver to tighten all mounting screws. Fasten securely, but do not over tighten.
1
Use four of the screws supplied with the accessory kit to attach one mounting bracket to the Xgig chassis. The bracket ear should extend out from the Xgig chassis in line with the connection side of the Xgig chassis.
21
Chapter 2, Xgig System Setup Figure 1: Attaching Mounting Brackets to the Xgig Four Slot
2 3
Use 4 screws to attach the other bracket. With the bracket ears securely attached, mount the Xgig chassis in your equipment rack. Use the remaining screws to attach the mounting bracket to the rack, 2 screws for each side.
Figure 2: Mounting Brackets, Front View of Four Slot
22
Rack Mounting Instructions, Two Slot

Use a screw driver to tighten all mounting screws . Fasten securely, but do not over tighten.
1
Use 4 of the screws supplied with the accessory kit to attach one mounting bracket to the Xgig chassis. The bracket ear should extend out from the Xgig chassis in line with the connection side of the Xgig chassis.
Figure 3: Attaching Mounting Brackets to the Xgig Two Slot
Use 4 screws to attach the other bracket. The bracket is a different size to make it fit a 19-inch rack mount. The larger bracket can be used on either side of the Xgig chassis. With the bracket ears securely attached, mount the Xgig chassis in your equipment rack. Use the remaining screws to attach the mounting bracket to the rack, 2 screws for each side.
Figure 4: Mounting Brackets, Front View of Two Slot
23
Rack Mounting Instructions, One Slot

Use a screw driver to tighten all mounting screws . Fasten securely, but do not over tighten.
1
Use 2 of the screws supplied with the accessory kit to attach the smaller mounting bracket to the left side of the Xgig chassis (see diagram below). The bracket ear should extend out from the Xgig chassis in line with the connection side of the Xgig chassis.:
Warning: The brackets must be installed on the left and right
sides of the Xgig chassis as shown in the figure below.

Figure 5: Attaching Mounting Brackets to the Xgig One Slot
Use 2 screws to attach the larger bracket to the right side of the Xgig chassis. The bracket is a different size to make it fit a 19-inch rack mount. With the bracket ears securely attached, mount the Xgig chassis in your equipment rack. Use the remaining screws to attach the mounting bracket to the rack, 2 screws for each side.
Figure 6: Mounting Brackets, Front View of One Slot
24
Xgig System Overview

The Xgig chassis is the hardware platform for installing blade hardware specific to analysis and test applications it is part of a larger system. Performing application tasks requires blade installation, PC hardware, installation of software at the PC, and making proper connections. There is a client-server relationship between the Xgig chassis (server) and the Xgig application software (client) used to perform tasks. The software on the Xgig server interacts with the blade hardware and services the requests made from the Xgig client software.
Figure 7: Xgig Client-Server Relationship
Xgig Blade for Application 1
Xgig Server Software (Xgig Image)

Xgig System Operating System Application 1 Server Software Application 2 Server Software Application n Server Software
Xgig Blade for Application 2
Xgig Chassis
Ethernet
Connection
PC with Windows
Application 2 Client Software Application 1 Client Software
There are two methods of connecting and working with the Xgig system: standalone and network. A standalone environment implies a work bench installation where the Xgig chassis is connected to a single PC for management and interface with Xgig software applications. A network environment implies an installation where the Xgig chassis is connected to an Ethernet network. The Xgig chassis can be reached on the network from many different clients running Xgig software applications. To set up the Xgig chassis, follow the instructions in the following section, depending on the environment of your Xgig system.
25
Below is diagram showing the relationships of the components to use, update, and configure an Xgig chassis in a network environment. Note that all PC-installed software does not necessarily need to reside on different PC systems.
Figure 8: Xgig Components in a Network Environment
Connections to Network Under Test or Device Under Test
O O O O
Port 1
Port 2
O ............. In Use ........... O O ................Link............... O O ............. LED x............. O O ............ LED y............. O
Port 3
Port 4
O O O O
Finisar
Console
Tap
..... ....
..... ....
In
Cascade Out
In
Trigger Out
Management
Ultra2 SCSI
O O O O
Console Port to Terminal to Set IP Address (One Time Operation, Required for Static IP Addresses Only)
PC or Terminal
Windows PC with Xgig Application Software and Browser for Xgig System Configuration
Windows PC with FTP Server for Xgig Upgrades
Ethernet Network
Windows PC with Xgig Application Software
26
Below is diagram showing the relationships of components to use, update, and configure an Xgig chassis in a standalone environment.
Figure 9: Xgig Components in a Standalone Environment
Connections to Network Under Test or Device Under Test
O O O O
Port 1
Port 2
Port 3
Port 4
O O O O
Finisar
Console
Tap
..... ....
..... ....
In
Cascade Out
In
Trigger Out
Management
Ultra2 SCSI
O O O O
Ethernet RJ-45 Cable Windows PC with: Xgig Application Client Software Browser for Xgig System Configuration FTP Server for System Upgrade
Console Port to PC COM Port
Xgig System and Application Images

Important: The Xgig chassis has two software images, one for
system software and one for applications. All software required to run the Xgig chassis comes pre-installed. All software required to run the Xgig chassis comes pre-installed. Update of Xgig chassis software is required with new releases. There are two images that reside within the Xgig chassis: System Image Application Image
27
The system image is the operating system for the Xgig chassis. The application image is software that communicates with Xgig client applications and controls the blades within the Xgig chassis. Software for all client applications is contained in a single application image.
Xgig Server Software

All server software required to run the Xgig chassis comes pre-installed. The Xgig System Server Software CD-ROM should auto run when you insert it in the CD-ROM drive. A screen will appear with a menu of options. If the CD does not autorun, select the Run option in the Start menu and type D:\autorun, where D: is the CD-ROM drive. The Xgig System Server Software CD-ROM contains: FTP Server Program An FTP server program is included for upgrades to the Xgig chassis. Installation of the FTP server program supplied on the CD-ROM is optional; you can use your own FTP server program and FTP site. An FTP server is required ONLY for system upgrades. Xgig System and Application Images (Kits Folder) Duplicate images of the pre-installed software are included on the CD-ROM. There is one image for the Xgig system software and one image for all application software. Upgrade images are also referred to as kits. Java Runtime Environment (JRE) Software The JRE is typically downloaded from a web site, and is provided on the CD for those without internet access. The correct version of the JRE software is required ONLY for system upgrades. PDF Versions of System Manuals PDF versions of system manuals are included on the CD. Acrobat Reader A version of Acrobat Reader is included for viewing system manuals in PDF format.
28
Xgig Client Software

Xgig Application client software is distributed on CD-ROM in a separate package. Applications are installed on a PC running Windows XP, Windows 2003 Server, Windows 2008 Server, Windows Vista Business (32-bit), or Windows Vista Ultimate (32-bit). Refer to the Software Installation Guide that accompanies the application client software for installation information.
Xgig Access Through a Firewall

In general, Xgig client software should be able to access an Xgig Chassis that lies behind a firewall. Ports must be open as described in the following table to permit operation across a firewall for Xgig applications:
Table 1: Requirements for Xgig Access Through a Firewall Application Administration Web Pages Administration Web Pages Xgig Analyzer Xgig Maestro Xgig Maestro Xgig Maestro TCP/UDP 80 (HTTP) 21 (FTP) 2000 2000 6000 135 (DCOM) Port Direction In Out In/Out In/Out In/Out In/Out Server Application on Port Apache Web Server None Xgig Analyzer Server Xgig Maestro Server Xgig Maestro Server Xgig Maestro Server
For sites where the Xgig Analyzer is the only application, it is suggested that the DCOM port remain closed. Network Address Translation (NAT) is not supported. An Xgig Chassis protected by a firewall that uses Network Address Translation (NAT) cannot be accessed from Xgig clients outside the firewall. For Win XP, Win 2003, and Win Vista users, ICMPv4 Allow incoming echo request (used for Ping) is disabled by default. To use the Xgig Web Utility to upgrade an Xgig chassis, this option must be enabled.
29
Access to Xgig chassis through a firewall is available with Xgig Analyzer Client software version 2.1 or greater, and Xgig Maestro software version 1.2 or greater.
Setup Instructions
To prepare the Xgig chassis for use, follow one of the three paths below depending on your environment:
Important: The Xgig chassis comes ready-to-use in a
DHCP-configured network. This is the easiest way to setup the Xgig chassis. Follow Path 1 unless you are required to setup the system differently.
Warning: Serious errors may occur if the Xgig chassis is not
shutdown properly. If you have a problem during setup and need to shutdown, follow either shutdown procedure in Xgig Chassis Shutdown Sequence on page 44 before removing power to the chassis.
PATH 1: Setting Up the Xgig Chassis in a DHCP Network

Follow the steps below to use the Xgig chassis in a DHCP-configured network. Connect the Xgig chassis to the network and verify that the chassis can be accessed from another node on the network. The default name for the Xgig chassis is XGIG followed by a eight-digit serial number; for example, XGIG78234335. The serial number is located on the bottom of the Xgig chassis.
1
Use the RJ-45 Ethernet straight-through cable to attach the Xgig to the network. The Ethernet connection is required for management of the Xgig chassis through application software and for configuration through the Xgig Web Utility.
Plug in the Xgig chassis. Attach the female end of the power cord to the Xgig chassis power receptacle and the male end into an appropriate power source.
30
Chapter 2, Xgig System Setup 3 4
Turn on the Xgig system using the power switch on the chassis. From the PC attached to the network, launch the browser. Using the default name of the Xgig chassis, access the Xgig chassis using the default name as the URL. For Example, http://XGIG78234335. If the operation is successful, you will see the screen asking for the user name and password to access the Xgig Web Utility. The default user name is Finisar and the default password is finisar.
Figure 10: Xgig System Login
If you cannot see the Xgig chassis, see Chapter 4, Tips and Troubleshooting for information on how to troubleshoot connections. The setup for the Xgig chassis is complete. Install the application blades and application software you will be using with the Xgig chassis. Refer to the Hardware Guide that comes with your blade for information on installing blade(s). Install application client software on a PC that can reach the Xgig chassis on your Ethernet network. Refer to the Software Installation Guide for your application client software for installation information. Skip to the Administration Chapter once you have completed these procedures.
31
PATH 2: Setting Up the Xgig Chassis with a Static IP Address in a non-DHCP Network
Important! The Xgig chassis comes ready-to-use in a
DHCP-configured network. You must use the serial interface to disable DHCP to set a Static IP Address. Follow the steps below to disable DHCP, set the IP address, and connect the Xgig chassis for use. In most environments, you will also need to set the subnet mask and the default gateway address for the Xgig chassis as well as the IP address. If you have a DNS name server, assign a name to the Xgig chassis so users can easily locate the system. The default name for the Xgig chassis is XGIG followed by a eight-digit serial number; for example, XGIG78256743. The serial number is located on the bottom of the Xgig chassis.
1
Use the DB-9 Null Modem Cable to connect Xgig chassis to either a VT-100 terminal or a desktop or laptop computer running VT-100 terminal emulation software such as Windows HyperTerminal. Plug one end of the cable into the Console port (9-pin port to the left), and the other into a COM port on the computer. Use the supplied RJ-45 Ethernet straight-through cable to attach the Xgig chassis to the network. The Ethernet connection is required for management of the Xgig chassis through application software and for configuration through the Xgig Web Utility.
Plug in the Xgig chassis. Attach the female end of the power cord to the Xgig system power receptacle and the male end into an appropriate power source. Turn on the Xgig system using the power switch on the chassis. If you are using a PC, start a terminal emulation software program on the PC, such as HyperTerminal. Configure the terminal or terminal emulation software to communicate with Xgig chassis. The terminal device must be connected to the Xgig console serial port with the following settings: 57600 Baud, 8 Data Bits, 1 Stop Bit, No Parity Flow control = none
4 5 6
32
Chapter 2, Xgig System Setup 7
When you launch the terminal emulation program, a screen such as the following will appear.
Figure 11: Xgig Command Line Options:
Determine if DHCP is enabled or disabled. If it is currently enabled, type D to disable DHCP. The addresses in the Static IP, Static Subnet Mask, and Static Default Gateway are not used if DHCP is enabled. Consult with your network administrator to obtain an appropriate Static IP Address, Static Subnet Mask, and Static Default Gateway for the Xgig chassis. These values will be specific to the network segment to which the Xgig chassis is attached. in IP dotted notation. Record the static IP address assigned to the Xgig chassis. You will need this address to verify the connect to the Xgig chassis and to use the Xgig Web Utility to set configuration parameters.
10 Type I and press Enter to set the IP address. Type in the Static IP address
33
Chapter 2, Xgig System Setup 11 Type M and press Enter to set the Static Subnet Mask. Type in the IP
address in IP dotted notation (for example, 255.255.255.0).

12 Type G and press Enter to set the Static Default Gateway. Type in the IP
address in IP dotted notation.

13 Type R to reboot the system. The message Do you want to reboot?
appears. Press Y to continue with the reboot. When the screen shown below appears, press Enter.
Important: You must reboot for changes to take affect. Wait
several minutes for the Xgig chassis to boot. During boot, the HyperTerminal screen below will show no activity.
Figure 12: HyperTerminal Screen During Xgig Boot
14 Check the status lights on the Xgig chassis to confirm that reboot is
complete. The Power, Ready, and Temp LEDs should be solid green. If you do not get solid green lights for the three LEDs, see Chapter 4, Tips and Troubleshooting.
15 Check the connection using either of the steps below. a
Ping the host PC from the Xgig chassis using the H command. The terminal emulation program must be running and you must be connected to the Xgig through the serial cable to use the H command. Enter the host name or the IP address of the remote host at the prompt. For example: > ping 10.10.4.2
34
Chapter 2, Xgig System Setup b
You can also ping the Xgig chassis from the PC to check the connection. From the Start menu in Windows, select Run and type in CMD. From the Command prompt, type the ping command with the new Static IP address as the argument. For example: > ping 10.10.4.34
If the ping is successful, you are ready to access the Xgig chassis from the Xgig Web Utility and from Xgig software applications. If your request times out, see Chapter 4, Tips and Troubleshooting for information on how to troubleshoot connections.
16 Close the serial port connection to the Xgig chassis from the PC. 17 Remove the DB-9 Null Modem cable between the terminal/PC and the
Xgig chassis (optional). Once the IP address is set, the use of the DB-9 Null Modem cable is no longer required. The console interface using the DB-9 Null Modem cable can be used to set other configuration values. However, all other configuration can be accomplished through a browser from the Xgig Web Utility. Refer to the section called Administration of Xgig Chassis over the Internet for information on running the Xgig Web Utility. The setup for the Xgig chassis is complete. Install the application blades and application software you will be using with the Xgig chassis. Refer to the Hardware Guide that comes with your blade for information on installing blade(s). Install application client software on a PC that can reach the Xgig chassis on your Ethernet network. Refer to the Software Installation Guide for your application client software for installation information. Skip to the Administration Chapter once you have completed these procedures.
35
PATH 3: Setting Up the Xgig Chassis in a Standalone Environment

Important: The Xgig chassis comes ready-to-use in a
DHCP-configured network. You must use the serial interface to disable DHCP and set a Static IP Address to setup the Xgig chassis for a standalone environment. Follow the steps below to disable DHCP, set the IP address, and connect the Xgig chassis for use in a standalone environment.
1
Use the DB-9 Null Modem Cable to connect Xgig chassis to either a VT-100 terminal or a desktop or laptop computer running VT-100 terminal emulation software such as Windows HyperTerminal. Plug one end of the cable into the Console port (9-pin port on the left), and the other into a COM port on the computer. This can be the same PC that will be used to connect with the Xgig chassis through the Ethernet port. Use the supplied RJ-45 Ethernet straight-through cable to attach the Xgig chassis directly to a PC with an Ethernet port. The Ethernet connection is required for management of the Xgig chassis through application software and for configuration through the Xgig Web Utility.
Plug in the Xgig chassis. Attach the female end of the power cord to the Xgig system power receptacle and the male end into an appropriate power source. Turn on the PC connected to the Xgig chassis and log in as the administrator. Set a static IP address for the PC connected to Xgig chassis. From Windows go to Start > Settings... > Network and Dial-up Connections and select the Local Area Connection. From the Status dialog, select Properties. From the Properties dialog box, highlight Internet Protocol (TCP/IP) and select Properties. Select the Use the following address: option and enter the static IP address and sub-net mask, such as 10.10.4.3 and 255.255.255.0. Write down the IP address. Start a terminal emulation software program on the PC, such as HyperTerminal.
4 5
36
Chapter 2, Xgig System Setup 7
Configure the terminal or terminal emulation software to communicate with Xgig chassis. For most systems, the terminal emulation program is accessible form Start > Accessories > Communication > Hyperterminal. The terminal device must be connected to the Xgig console serial port with the following settings: 57600 Bits/second, 8 Data Bits, 1 Stop Bit, No Parity Flow control = none
Turn on the Xgig system using the power switch on the chassis. Wait several minutes for the Xgig chassis to boot. The boot is complete when the Power, Ready, and Temp LEDs on the front of the chassis are solid green.
When you launch the terminal emulation program, a screen such as the following will appear:
Figure 13: Xgig Command Line Options
37
Chapter 2, Xgig System Setup 10 Determine if DHCP is enabled or disabled. If it is currently enabled, type D to disable DHCP. The addresses in the Static IP Address, Static
Subnet Mask, and Static Default Gateway fields are not used if DHCP is enabled.
11 Type I to set the IP address. Type in the Static IP address in IP dotted
notation. The IP address should match the IP address for the PC you set in step 6, except for changing the last portion of the address. For example, if the PC address from step 6 is 10.10.4.3, then assign an address such as 10.10.4.4.
12 Type M to set the Static Subnet Mask. For example, use 255.255.255.0
as the Subnet Mask.

13 Type R to reboot the system. The message Do you want to reboot? appears. Press Y to continue with the reboot. When the screen shown
below appears, press Enter.

Important: You must reboot for changes to take affect. Wait
several minutes for the Xgig chassis to boot. During boot, the HyperTerminal screen below will show no activity.
Figure 14: HyperTerminal Screen During Xgig Boot
14 Check the status lights on the Xgig chassis to confirm that reboot is
complete. The Power, Ready, and Temp LEDs should be solid green. If you do not get solid green lights for the three LEDs, see Chapter 4, Tips and Troubleshooting.
38
Chapter 2, Xgig System Setup 15 Check the connection using either of the steps below. a
Ping the host PC from the Xgig chassis using the H command. The terminal emulation program must be running and you must be connected to the Xgig through the serial cable to use the H command. Enter the IP address of the PC at the prompt. For example: > ping 10.10.4.3 You can also ping the Xgig chassis from the PC to check the connection. From the Start menu in Windows, select Run and type in CMD. From the Command prompt, type the ping command with the new Static IP address as the argument. For example: > ping 10.10.4.4
If the ping is successful, you are ready to access the Xgig chassis from the Xgig Web Utility and from Xgig software applications. If your request times out, see Chapter 4, Tips and Troubleshooting for information on how to troubleshoot connections.
16 Close the serial port connection to the Xgig chassis from the PC. 17 Remove the DB-9 Null Modem cable between the PC and Xgig chassis.
Once the IP address is set, the use of the DB-9 Null Modem cable is no longer required. The console interface using the DB-9 Null Modem cable can be used to set other configuration values. However, all other configuration can be accomplished through a browser from the Xgig Web Utility. Refer to the section called Administration of Xgig Chassis over the Internet for information on running the Xgig Web Utility. The setup for the Xgig chassis is complete. Install the application blades and application software you will be using with the Xgig chassis. Refer to the Hardware Guide that comes with your blade for information on installing blade(s). Install application client software on a PC that can reach the Xgig chassis on your Ethernet network. Refer to the Software Installation Guide for your application client software for installation information.
39
Cascading Xgig Chassis

Once single Xgig chassis are set up for operation, it is possible to cascade several chassis together using CAT-5 straight-through cables and the Cascade ports on the Xgig chassis. Up to four chassis can be cascaded together to form a Sync Group. Xgig chassis use standard RJ-45 connectors and CAT-5 cable to connect, as with any standard Ethernet connection; however, the chassis communicate using a proprietary JDSU protocol. You can specify the length of the sync cable(s) between chassis in Analyzers discovery control window if you are required to use sync cables other than the ones provided with a chassis. The minimum is 1ft, and the maximum is 100ft. The default is 3ft, which is the length of the cable provided with the chassis. For cascaded units, as shown in the figure below, the first chassis in the sequence is called the master. All other chassis in the cascade are slaves. The entire cascaded sequence is always addressed by the IP address or DNS name of the master unit. Connect the Cascade Out port on the master Xgig chassis to the Cascade In port on the next chassis in the chain. Continue cabling from Cascade Out to Cascade In as you move down the chain. The management ports of all chassis in the cascade must be connected to the same LAN subnet for the chassis to be in the same Sync Group.
40
Chapter 2, Xgig System Setup Figure 15: Cascade Cabling for Xgig
Cascade In Cascade Out Management Port
Master
CAT-5 (or better) Cables
Slave
Slave
LAN
Slave
Note that there is no connection to the Cascade In port of the master Xgig chassis. Do not connect the Cascade Out port on the last Xgig in the cascade to the Cascade In port of the master in a loop.
41
Chassis are numbered consecutively starting with the master. The ports are addressed in a cascaded configuration by chassis number, blade number within the chassis, and port number within the blade for example, FC Port(1,2,3) refers to port 3 on blade 2 in chassis 1. The diagram below shows how chassis are numbered for port addressing when they are cascaded together.
Figure 16: Chassis Numbering for Cascaded Xgig Chassis
Example Port Number: FC Port (1,3,1)
Master
Chassis #1
Slave
Chassis #2
Slave
Chassis #3
Slave
Chassis #4
42
Xgig Chassis Startup Sequence

The following is the start up sequence that you will observe when you power on the Xgig chassis.
1 2 3
Turn on the power switch to supply power to the Xgig chassis. The Power LED comes on. Wait several minutes. When the Management Port is connected to the network, the remainder of the start up sequence continues. If the Management Port is not connected, the Ready LED turns yellow and the sequence does not continue until the Management Port is connected. All of the following events occur at the same time. The Sync Discover operation takes the longest to complete.
a b c d
The Management Port activates; the Link LED on the right of the port blinks yellow to show link activity. The blades initialize and blade LEDs activate (not all LEDs for all ports will activate). The Temp and Ready LEDs turn solid green. The Sync Discovery operation starts and the LEDs on the Cascade Ports blink. During a Sync Discovery, the concatenated chassis go through the process of discovering how many units are cascaded together and reset ports accordingly. Sync Discovery may take several minutes.
When the Xgig chassis is finished booting and Sync Discovery is complete, the Cascade Ports stop blinking and turn solid green. The Temp, Ready, and Power LEDs are solid green, indicating that Xgig chassis is ready for use.
Note that when a reboot or a Sync Discovery is initiated, all existing data in the capture buffer of any Xgig blade with the chassis is lost. Sync Discovery can also be initiated by a command from the Xgig Web interface utility.
43
Xgig Chassis Shutdown Sequence

The following are the proper shutdown sequences for the Xgig chassis. You must follow one of these procedures before removing power from the chassis.
Warning: Serious errors may occur if the Xgig chassis is not
shutdown properly. You must follow one of the procedures below before removing power to the chassis. If you experience problems with restarting the chassis after powering down and then reapplying power to the unit, see Power Up Problems Following Chassis Shutdown on page 62 in the Troubleshooting section.
Shutdown Using the Web Utility Interface

1 2 3 4
Determine the IP address of the unit. From the Internet Explorer application, connect to the unit. From the Server drag down menu, select Shutdown. Wait until the chassis shuts down completely before removing power. The management port LEDs will go out when the unit has completely shutdown.
Shutdown Using the Console Interface

1
Ensure that the direct communication with the unit is achieved by:
a b c
Connect a null modem cable to the console port of the Xgig chassis. Open the console interface by using HyperTerminal or an equivalent interface. Press Enter and verify that the unit information refreshes.
2 3
Type in S to initiate system shutdown. Wait until the chassis shuts down completely before removing power. The management port LEDs will go out when the unit has completely shutdown.
44
Chapter 3
Administration
In this chapter:
Administration of Xgig over the Internet Licensing Multi-Function Blades System Upgrade Procedures
45
Chapter 3, Administration
Administration of the Xgig System over the Internet

Important: The Xgig comes with a web-based system
administration utility that performs upgrades and other configuration activities over the Internet.
Xgig Web Utility

You can perform administration and configuration activities over the Internet using the Xgig Web Utility. The Xgig Web Utility performs the following functions: Configure set chassis IP addresses and select/remove DHCP addressing set the system IP address/account name/password for the FTP server used to upgrade application and system images synchronize the Xgig system clock to the time on your local system assign or change licensing for a blade within the chassis
Get chassis status blade information, including location and firmware revision level chassis system information, including current system image version application image information, including revision levels of all application software at the Xgig chassis
Perform upgrades system image application image upgrade status, check for available upgrade versions
Perform chassis administration system reboot system shutdown sync reset

46
Change the web access login user name and password Enable user authentication and set the password for remote users
Set management port speed (pre-set to auto-detect the speed)
Accessing the Xgig System for Administration

Once the IP address is set or assigned for the Xgig chassis, use the IP address or the DNS name as the URL to reach the instrument over the Internet. For example, if the name of the Xgig chassis is XGIG78344987: https://XGIG78344987. Or, if the IP address of the Xgig chassis is 10.24.233.6: https://10.24.233.6. Refer to the previous sections on setting up your Xgig chassis for information on setting/obtaining the correct IP address. Connections use the Secure Sockets Layer (SSL) protocol to protect your resources. The use of a secure connection requires validation by a certificate authority. The first time you enter the URL, you may receive the following security alert.
The security alert gives you a warning that the security authority is not in your browsers list of trusted authorities. Press Yes to continue. You can use the View Certificate button to install an JDSU Xgig Certificate Authority (CA) certificate in your browser. If you do not install the certificate, you will get continue to get this security alert from your browser when you use HTTPS to access the Xgig chassis.
47
Other security messages may be posted by your browser when you leave or enter the secure connection to the Xgig chassis. These messages may vary depending on the version of JRE or the version of the browser that you have installed. When you log in using a secure connection, a lock icon appears on the status bar at the bottom of the web page. It is highly recommended that you access the Xgig using a secure connection, especially when changing the Xgig Web Utility password or when setting up Client Authentication. Note that you can also access the chassis over an unsecured connection (HTTP); for example, http://
10.24.233.6.
Logging In and Logging Out Use the default account and password to log in. Logging into the administrator web page provides you will full administration privileges. The factory defaults are shown below: User Name: Password: JDSU JDSUsnt
Once you are logged in, refer to the on-line help for information about the functions available from the Web utility. User names and passwords are case sensitive. To provide system security, you should change the default user name and password from the Security menu of the Xgig Web Utility. If you forget the user name or password for the Xgig, you must use the Web Login Reset option from the console to reset the user name and password to the factory defaults. When you log out, you must close the browser to completely break the connection with the Xgig chassis. There is no time out when you are logged into the Xgig Web Utility; always log out and then close the browser when the utility is not being used.
Important: When you are finished using the Xgig Web Utility, log out and close the browser. The browser must be closed to ensure that security is not compromised with the Xgig chassis.
48
System Requirements for Internet Administration

Web administration is performed through Java applets and HTML forms. You must use Internet Explorer version 6.0 or greater, Netscape version 6.0 or greater, or Firefox version 1.5 or greater when using the web console. The upgrade portion of the Web utility requires the Java Runtime Environment (JRE). If you do not have the correct version of JRE and you are connected to the internet, you are asked to install JRE version 6 with update 2 (the latest auto-install version) when you access the upgrade portion of the Xgig Web utility. Follow the simple steps to install a new JRE version. If you do not already have JRE installed and you are not connected to the Internet, you will need to manually install the correct version of the JRE. JRE version6 with update 3 can be installed using the Xgig System Server Software CD-ROM. Note that Windows Vista uses Internet Explorer 7.0. IE 7.0 has higher default levels of security, and pop-ups are disabled by default. Some software functions of the Xgig Web Utility use pop-ups, such as displaying the upgrade log. Pop-ups must be enabled before using the Xgig Web Utility. Also, higher levels of security in the browser may require you to re-enter the username and password for the Xgig system when you enter the applet for upgrading the Xgig chassis.
Setting Client Authentication

Use the Security > Client Authentication menu of the Xgig Web Utility to set the password for the Xgig Chassis. If authentication is not set for the Xgig, any user of Xgig Client software will be able to access and use the Xgig Chassis. The password for client access can only be assigned by the Xgig Web Utility. The password cannot be set or reset from Xgig Client software.
49
Licensing
There are three different ways to license ports blade licensing, port-pair licensing, and floating/mobile licensing via the serial port dongle. Not all methods apply to all blades types and/or all port functions. From client application software, you can change the function of the port-pair only if the port-pair has a license for multiple functions. If a blade or port-pair does not have the ability or the license to perform a function, all menus and options related to that function will not be available from applications for the those ports/blades. Note that JDSU blades originally purchased as fixed-function blades can be turned into multi-function blades with the proper upgrade and license. License keys assigned by JDSU are associated with each function of a blade/ port. Use the license configuration page to view each blades description, serial number, current license key, and licensed feature set. If a blade has an inherent, built-in feature, it will also be displayed. Check with Customer Support if you need to expand the functional capabilities of an Xgig blade or port-pair and require an additional license key. Blade Licenses Use the Web Utility to change the licensing of any Xgig Blade within a chassis. Blade licenses are assigned by the Xgig Web Utility ONLY and stored on the blade. If the blade is moved to a different chassis, its license, and therefore its ability to change functions, remains the same. In other words, the licenses follow the blade and are not associated with the chassis. Port-Pair Licenses Port-pair licenses are also assigned by the Xgig Web Utility ONLY and stored on the blade. For all Xgig blades there is a blade license key and, if required, a license key for each port-pair. The port-pair license key allows specific functions for each port-pair. The port-pair license is only assigned if port-pairs within the blade are licensed for different functions. This option alleviates the cost of purchase licenses for the entire blade when there is only a need for a port-pair(s).
50
Portable Licenses Licensing for Xgig ports is also supported through a serial-port dongle. The dongle is a small serial device that connects to the first serial port (labeled as Console) at the bottom of the Xgig chassis. When using a dongle, the console connection must be moved to the second serial port (labeled as Tap). The License web page for the chassis shows the dongle licenses and the dongle serial number when the dongle is attached. The dongle contains licenses to enable functions for port-pairs in the chassis. At this time, only the Jammer port function is supported. The dongle can be moved between Xgig chassis and provide licenses for different chassis. It is essentially a movable license the dongle is not keyed in any way to a particular chassis or port-pair. However, the dongle license can apply to specific classes of blades. For example, a license could enable Jammer for 6G blades but not 3G blades. Existing license(s) on a blade will not be overridden by the license from the dongle. The dongle provides license(s) for a number of additional port-pair(s) for a function in the chassis. The port-pairs selected for licensing are always the first applicable port-pairs within the chassis that are not already licensed for the function. If a port-pair is physically not capable of performing the function, it is skipped and the license is applied to the next available and capable port-pair. For example, assume the dongle allows 2 additional FC Jammer port-pairs and there is one port pair in slot 1 already licensed for FC Jammer. With the dongle attached, a total of 3 port pairs can function as FC Jammers. Assume the port-pair already licensed is port(1,1,1)-port(1,1,2) and the blade in slot 2 is an SATA blade and cannot perform FC Jammer functions. The 2 additional licenses are applied to port(1,1,3)-port(1,1,4) of the blade in slot 1 and port(1,3,1)-port(1,3,2) of the blade in slot 3 provided that this is a matching FC blade type. Note that if the license is for an 8G FC blade, the license will not work for the 4G or 2G FC blades. The dongle must be attached to the serial port and remain plugged in as long as the functions are needed. If the dongle is removed while the dongle-enabled port-pairs are in use, all operations on those port-pairs will stop, and traffic going through those ports may be interrupted. When the dongle is re-inserted, you must resume operation manually. A license from a dongle can only be applied to the ports within the chassis that the dongle is attached to. The maximum number of licenses for a chassis is 16 ports or 8 port-pairs. Attaching a dongle so that the number of licenses exceeds the maximum licenses allowed for the chassis will result in unused licenses.
Xgig Family Hardware Guide 51
System Upgrades
Important: Upgrades are not required when you initially install
Xgig chassis. You will receive a new version of the Xgig System Server Software CD-ROM when upgrades become available. With Xgig Analyzer Software Release 3.2 or later, an Xgig chassis or cascaded set of chassis can be upgraded from the client software. Xgig client software is distributed on CD-ROM or can be downloaded from the Internet. See the section Chassis Software Upgrade in the Xgig Analyzer Users Guide for more information.
Setting Up the FTP Site for Upgrades

The JDSU Xgig System Server Software CD-ROM contains software to set up the FTP site so you can upgrade software for the Xgig chassis over the network. It installs the directories containing upgrade files and, if needed, installs an FTP server software program. It is not required that you use the FTP server program supplied by JDSU or set up the FTP site until you need to upgrade the software on your Xgig chassis. For Win XP, Win 2003, and Win Vista users, ICMPv4 Allow incoming echo request (used for Ping) is disabled by default. To use the Xgig Web Utility to upgrade an Xgig chassis, this option must be enabled. Also, port 21 in the FTP server must be opened in the Firewall for upgrades using FTP. Refer to your Windows documentation for setting Firewall rules and opening ports. If You Already Have an FTP Site There are several things you must do to set up an FTP server for upgrades using the Xgig Web Utility: Copy the /Kits folder and all of its contents from the Xgig System Server Software CD-ROM to the FTP server root or default login folder. Set up an account with read file access to the directory containing the upgrades so they can be reached over the Internet. Leave the server up and running to access upgrades. If the FTP account is password protected, the account and password must be supplied to the Xgig administrator. The Xgig administrator will use the account name and password to log-in to the FTP site to obtain upgrades.
52
Proceed to the section Updating the FTP Server with Upgrade Images on page 54 to perform an upgrade. If You Need to Create an FTP Site If you do not have an FTP site or wish to install a separate FTP site for upgrades, JDSU supplies a free-ware FTP application. To install the FTP software application, follow these steps. For an Xgig chassis in a standalone environment, install the upgrade site on the same PC that contains your Xgig client applications.
1 2 3 4
Log on as Administrator of the system. Insert the Xgig System Server Software CD-ROM into your computer. Click on Install FTP Server from the CD-ROM menu. Follow the steps in the Install Wizard to load the image files and directories to a location of your choosing.
The FTP server can be started from the shortcut on the Start menu. You may also chose to install it as a Windows service and specify that it starts automatically upon boot of the system. To setup the FTP server as a Windows service, launch the FTP server, go to Settings > Edit Server Options > Startup Options, and place a check mark in the appropriate box. The FTP server install program automatically creates the /Kits directory required for storing Xgig system and application images. It also creates a shortcut within the JDSU folder in the Start menu to the Xgig FTP Server. When using the JDSU-supplied FTP server, you have two choices when you receive an upgrade software CD-ROM for the Xgig chassis:
1 2
Copy the contents of the /Kits directory to the same directory on your server. Reinstall your FTP server software. If you select the repair option, all older kits are saved and newer kits are added to the /Kits directory on the server. The login options are restored to their default values. If you select the remove option, the contents of the /Kits directory are replaced. The login options are restored to their default values.
53
Updating the FTP Server with Upgrade Images

Use this procedure to update Xgig chassis software when new versions become available. There is no need to run this procedure when you first install the Xgig chassis. Upgrades for the image software are distributed on the Xgig System Server Software CD-ROM.
1 2
Insert the Xgig System Server Software CD-ROM into the CD-ROM drive of the system containing your FTP server. Select the Update Existing SW option from the CD-ROM. Follow the instructions on how to retrieve the new Xgig software images from the Xgig System Server Software CD-ROM. When you log into the FTP server through the Xgig Web Utility, the upgrade page picks up the names of any kits in the /Kits directory on the FTP server and presents them as options for installation.
Write down the IP address of the system containing the FTP server. You will need this address to perform upgrades. To find the address, from the Windows Start menu of the FTP server select Run... and type in CMD. From the DOS prompt, type the IPCONFIG command. This command will return the IP address assigned to the system with the FTP server, such as 10.10.254.4.
Upgrading the Xgig System Image and Application Image Software

Once you have your FTP site set up with the latest version, use this procedure to update Xgig chassis software.
1
From your browser, access the Xgig Web Utility. Enter the DNS name or IP address of the Xgig chassis as the URL (for example, https:// xgig-3, or https://10.10.254.3). See Accessing the Xgig System for Administration on page 47 for more information about secure login. A log-in screen appears. Enter the account name and password for the Xgig chassis. The default account and password for the Xgig system are JDSU for the account name and JDSUsnt for the password.
54
Chapter 3, Administration Figure 17: Xgig System Login for Upgrade
If you are having a problem reaching the Xgig chassis through the browser, see Cannot Connect to the Xgig Chassis Using the Web Browser on page 65 in the Tips and Troubleshooting chapter.
3
Select FTP from the Configuration section of the Xgig Web Utility. The FTP Configuration page appears.
Figure 18: Xgig FTP Configuration
Set the IP address of the host running the FTP server with the software image(s). Set the correct account name and password and click Save.
55
Account name and password set up are controlled at the FTP server. The default username and password should be modified as necessary to match the FTP server's account information. The defaults are jdsu for the account name and jdsu for the password. The upgrade utility uses the IP address, account name, and password entered on the FTP configuration page to access the FTP server when you perform an upgrade.
5
Select Upgrades from the Xgig Web Utility. The upgrade portion of utility appears with four tab stops. All chassis in the same subnet will also appear. The utility performs a discovery of all Xgig chassis within your subnet.
Important: Only the Xgig chassis on the same subnet that have
client authentication disabled will appear in the System Upgrade and Application Upgrade tabs of the Upgrade Utility page. For security reasons, if authentication is enabled for a chassis, you must login directly to that chassis to upgrade the images.
56
Chapter 3, Administration Figure 19: Xgig System Upgrade
You may be asked to install the proper Java runtime version if you are connected to the Internet. Install the JRE software and continue. The correct JRE version can be installed from the Xgig System Server Software CD-ROM if you are not connected to the Internet. See System Requirements for Internet Administration on page 49 for more information.
6
Select System Upgrade or Application Upgrade. For either type of upgrade, you can upgrade multiple chassis to the latest version. Press Select all latest versions to upgrade all chassis to the latest version. All chassis shown in the tree will be upgraded. To select specific chassis and software versions, use one of the steps below.
a
For System Upgrade, all versions of the system software image available on the FTP server are displayed. Check the box for System A or System B. The system has two image copies. If one of the system images is in use, you will not be allowed to select that image. Select the version of the new image to install. For Application Upgrade, all versions of the application software image available on the FTP server are displayed. Select the version of the new image to install.
57
Chapter 3, Administration 7
For either type of upgrade, press the Upgrade button. The new image is loaded to the Xgig chassis. The time it takes to load the image will depend on the type of upgrade.
Warning: DO NOT REBOOT OR POWER OFF THE XGIG
CHASSIS DURING APPLICATION IMAGE UPGRADE. An application upgrade sometimes requires the reprogramming of the FPGA. The FPGA programming is sensitive to interruption, and must be allowed to complete. If interrupted, partial FPGA programming can make the chassis unusable without JDSU factory maintenance. If the FPGA update is not required, the following message appears during application upgrade and the upgrade takes less than a minute.
Checking for FPGA bitfile update...none required
If an FPGA update is required, the following message appears during upgrade and the upgrade takes about 4 minutes.
Checking for FPGA bitfile update...update required ######################################################## WARNING...Bitfile update in progress. This should take ~4 minutes. Chassis may become unusable if this update is interrupted. Factory or in-field maintenance would then be required. ########################################################
If the FPGA update completes and the Xgig re-initializes, the following message appears:
FPGA bitfile updated and device re-initialized
The FPGA programming may complete successfully, yet the device fails to initialize. If you receive the following message after the FPGA update, cycle the power to the Xgig chassis after the Xgig reboots but before using the chassis to perform other operations.
######################################################## WARNING...Bitfile update completed but device initialization failed. This chassis must be power cycled to complete FPGA update. Operation will be unpredictable without a power cycle. ########################################################
Once the application upgrade and FPGA update complete successfully, the following messages appear:
Application Install Completed. End of application Upgrade. Local system rebooting
58
Chapter 3, Administration 8
Do not refresh the Upgrade Utility page in the browser and wait until the Xgig chassis is finished rebooting. Wait 4 minutes for an Application Image Upgrade, and 5 minutes for a System Image Upgrade. You can also confirm that the reboot is complete by checking the status lights on the Xgig chassis. See Xgig Chassis Startup Sequence on page 43 for more information.
Important: Do not refresh the Upgrade Utility page in the
browser. This will cause the Xgig to restart its reboot routine.
9
The system automatically reboots after each upgrade. The Xgig system will reboot twice as a normal boot sequence after a system image upgrade.
Important: The Xgig chassis has two software images, one for
system software and one for applications. BOTH images may require update to bring your software to the required level. Repeat these steps after the reboot is complete to upgrade the second image.
10 After the system reboots, verify the latest software version is installed by checking the Upgrade Status page. See Figure 20 for an example.
Important: Always check the Upgrade Status tab after you complete an upgrade to verify that the upgrade was successful.
59
Chapter 3, Administration Figure 20: Verify System or Application Image Upgrade
To check on updates to the software image for versions of Xgig software, contact JDSU Customer Support.
Important: When upgrading multiple chassis with System
Images older than 2.5.6, the upgrade log of the local chassis may show timeout upgrade failure messages for the remote chassis. In most cases, these messages are erroneous and the upgrade(s) were successful. If the upgrade log shows a failure message, check the status by logging on the failed chassis and verify that the upgrade succeeded. You can avoid this issue by first upgrading only one chassis to the newer version. After this chassis is upgraded, remotely upgrade the remaining chassis using the upgraded chassis as the local system for the upgrade.
60
Chapter 4
Tips and Troubleshooting
In this chapter:
Troubleshooting Interpreting the LEDs on the Chassis Miscellaneous Tips for Using the Xgig Chassis Instructions for Re-seating Blade Memory
61
Chapter 4, Tips and Troubleshooting
Troubleshooting
No LEDs Are Lit on the Chassis
The chassis has no power. Make sure the power cord is properly connected to the chassis. Make sure the power adapter is properly connected to a functioning power outlet. If the cord is connected to a power strip, make sure the power strip is turned on. In rare occurrences, the fuse may have burned. Check the fuse at the power cord receptacle in the back of the one-slot and two-slot chassis. If the fuse needs to be replaced, use the spare fuse included in the housing. If another replacement fuse is used, be sure to use a fuse with the rating indicated on the Xgig chassis cover.
The Power light is lit but other system LEDs do not light up
The system software is not started. If the system has just been upgraded, the system is rebooting. Wait for another two to five minutes for the system to completely boot and start the software correctly. The boot system image may be corrupted. Refer to Restarting the Xgig Chassis with the Backup System Image on page 68 to bring the system back up. Once the system is booted up using the backup image, replace the systems image by going through the system upgrade process.
Power Up Problems Following Chassis Shutdown

If after removing and then reapplying power to the Xgig chassis the system does not boot properly, start the chassis using the Backup System Image. Refer to the Restarting the Xgig Chassis with the Backup System Image on page 68 to bring the system back up. Once the system is booted up using the backup image, replace the systems image by going through the system upgrade process. To prevent these problems, follow the shutdown procedures as described in Xgig Chassis Shutdown Sequence on page 44.
62
The Management port LED is not lit

This indicates an Ethernet connection problem. Make sure the Ethernet cable connectors are securely plugged in at both ends. Try a different port on the hub or switch. Verify the cable is in good working order by plugging it to two different devices. Make sure that the network speed for the management port is set correctly. Some switches require that you force the management port speed to a fixed speed and duplex-value rather than letting the Xgig auto-detect the network speed. You can configure the speed and duplex setting of the management port using the Xgig Web Utility.
The Ready LED is off

The chassis may be downloading new system image or application image. While downloading a new system image or application image, the Ready LED is turned off. Wait for two to five minutes for the system to completing the image download and reboot.
The Ready LED is yellow

There is an Ethernet connection or Ethernet setup problem. See the The Management port LED is not lit section above for tips to solve an Ethernet connection problem. If DHCP is used, verify that the chassis has a valid IP address using the Console port. If the chassis has no valid IP address, contact the network administrator. If static IP address is used, make sure all pertinent address information is entered correctly. This includes an IP address and Subnet Mask.
The Temp LED is yellow

The chassis temperature is too high. Check and make sure that the sides of the Xgig chassis are not blocked. There must be a minimum of 4 inches of space around the sides of the unit.
63
Reboot the chassis by turning the power switch off, wait for ten seconds, and turn the power switch back on. If the Temp LED remains yellow, turn the power switch off. Contact JDSU Customer Support for further instructions.
Cannot Ping the Xgig Chassis

The connection between the Xgig chassis and the PC is down as indicated by the failure of the Ping operation. Verify the Ethernet cables are securely plugged in for both the Xgig chassis and the PC you are using. Try the Ping operation with IP address instead of the Xgig chassis name. If the address is not known, use the console port to get its IP address. See the Installation chapter for instructions. If DHCP information is used to address devices: Verify that your PC has a valid IP address. Verify the Xgig chassis has a valid IP address. See the Installation chapter for instructions on using the Console port to check the Xgig chassis IP address. If either device does not have a valid IP address, contact your network administrator.
If static IP addresses are used, verify the IP addresses, Subnet mask, and Gateway IP addresses are correctly entered. Ping other devices on the same subnet as the PC. If the Xgig chassis is on a different subnet, ping other devices on the same subnet as the Xgig chassis. This will ensure that your network is still functional. As an alternate solution, setup the PC and the Xgig chassis as Standalone configuration. See PATH 3: Setting Up the Xgig Chassis in a Standalone Environment on page 36 in the Installation chapter for instructions. Try booting the Xgig chassis with the backup image. See Restarting the Xgig Chassis with the Backup System Image on page 68 in this chapter for instructions. If successful, the current image is damaged. You need to replace the current system image. See Updating the FTP Server with Upgrade Images on page 54 for instructions. If all above steps have been performed and you still cannot ping the Xgig chassis, contact JDSU Customer Support.
64
Cannot Connect to the Xgig Chassis Using the Web Browser

The Xgig chassis can be pinged, but the web browser returns an error message. The web application is not responding to the connection request. Make sure you are using the correct version of the browser: IE 6.0 or greater, Netscape 6.0 or greater, Firefox 1.5 or greater. Make sure the correct chassis name or chassis IP address is used. Make sure both the connecting computer and the Xgig chassis are on the same network. Refer to the Installation chapter for information on how to discover the Xgig chassis address settings using the console port. On a rare occasion, a web application file of the current boot image is damaged; use the console port to boot the system with the backup image as described in the Restarting the Xgig Chassis with Backup System Image section. Once the system is booted up with the backup image and the web-based connection is re-established, replace the current systems image by going through the system upgrade process.
Cant find the System or Application upgrade on FTP server

The chassis cannot find the specified image or the system is unable to logon to the FTP server. Make sure the FTP server is on-line and available to the chassis. Make sure the FTP server has the applicable images. Make sure the system image and application image folders are visible at login. Contact network system Administrator for information and refer to Setting Up the FTP Site for Upgrades on page 52 for information on where to place the folders. Verify that the FTP server IP address is correctly entered on the webs Configuration FTP page. Verify that the user name and password information on the webs Configuration FTP page are correct. User name and password are case sensitive.
65
The system is rebooting repeatedly

The chassis is triggered to reboot. With system image upgrading, the chassis will be rebooted twice as a normal operation. Dont refresh the web browser as the system is rebooting. If the chassis keeps on rebooting after all necessary steps are observed, turn off the power switch and contact JDSU Customer Support.
The Cascade Port LEDs do not blink after initiating Sync Discovery
Indicates that no Sync Discovery sequence is taking place. Check to make sure all cables are correct and in good working order. Straight -through CAT-5 cables are required. Check to make sure that all connections are secure. Check to make sure that the cabling between the cascade ports is correct. A cable should exist from the Cascade OUT port of the master (first) chassis in the sequence to the IN Cascade port of the second chassis. This Cascade OUT to Cascade IN cabling must be repeated for additional chassis in the chain. The last chassis in the chain only requires a cable to its Cascade IN port.
Sync Discovery Will Not Complete

The Cascade Port LEDs continue to blink and Sync Discovery will not complete. Check to make sure all cables are correct and in good working order. Straight -through CAT-5 cables are required. Use of cross-over cables between chassis may result in the Sync Discovery being unable to complete.
66
Cannot Find an Xgig Chassis Using the Discover Button in the Port Selection Window
You are attempting to find a single Xgig chassis or cascaded Xgig chassis on the network using the discovery operation in Xgig application software. You cannot discover the Sync Group or the discovery process is taking an extremely long time. The discovery operation may take an extremely long time if you have moved the Sync Group to a different subnet. After moving an Xgig chassis to another subnet, it is recommended that you use the IP address the first time you attempt to discover it. This prevents a potential Domain Name Server (DNS) issue. Check to make sure you have the correct name of the Xgig chassis. If the Xgig chassis cannot be found by name, use the IP address. For cascaded chassis, the IP address of any of the chassis in the cascade should result in the Sync Group being discovered. Attempt to discover another Sync Group on the same subnet as the Sync Group you are trying to discover. This operation should discover all Sync Groups on the same subnet. If you still cannot discover the Sync Group, use the Ping operation to see if the Sync Group is on the network. If the Ping operation fails, see Cannot Ping the Xgig Chassis on page 64. You can also connect to the console port on the Xgig chassis to verify its IP address. See PATH 2: Setting Up the Xgig Chassis with a Static IP Address in a non-DHCP Network on page 32, steps 1 through 7, for information on getting the IP address through the console port.
Auto Link Speed Detection Problems for SAS/SATA

You are having problems with failed captures using SAS/SATA ports when the link speed is set or changed to Auto. Xgig ports may not always be able to auto detect the link speed that is running on the wire, thus using the Auto link speed setting for SAS captures may result in captures at an incorrect link speed. If the Xgig chassis does not see the link initialization (for example, during an Xgig reboot), then it may not be able to auto detect the link speed. Rebooting or resetting the host device (detaching and reattaching the cable) connected to Xgig ports can fix this problem, but this is not usually advisable as it is disruptive and may cause loss of connectivity for the host and/or target.
67
The simple solution is to set a fixed link speed rather than use the Auto setting.
Restarting the Xgig Chassis with the Backup System Image

If you cannot connect to the Xgig chassis, you may be able to reestablish operations by booting the Xgig chassis with the alternate version of the Xgig operating system. This operation can fix problems where the operating system has been corrupted or where you have installed a version of the Xgig operating system that is incompatible with your hardware. To reboot the Xgig chassis using the alternate version of the operating system, perform the following steps:
1 2
Power down the Xgig chassis. Connect the DB-9 Null Modem cable supplied with the Xgig chassis from the Console port on the Xgig chassis to a VT-100 Terminal or to a COM port on PC with terminal emulation software. Configure the terminal or terminal emulation software to communicate with Xgig chassis. The terminal device must be connected to the Xgig console serial port with the following settings: 57600 Baud, 8 Data Bits, 1 Stop Bit, No Parity Flow control = none
4 5
Turn on the power to the Xgig chassis. From the terminal emulation program you will see a boot message.
Please select the operating system to start: Current System Backup System
If the boot selection message does not appear, check the cable between the PC or terminal and the Xgig chassis. If it appears to be correctly cabled and you still do not see the Xgig Command Line Options menu, contact Customer Support.
6 7
Use the arrow keys to highlight the Backup System. Press Enter. After the Xgig chassis has started, re-check your communications between the application client software and Xgig server. If you still cannot get a connection, call Customer Support.
68
Tips
Pinging the Xgig Chassis
To ping the Xgig chassis, click on the Start menu, select Run, and type in CMD. From the Command prompt, type the ping command with the new IP address as the argument. For example: > ping 10.10.4.34
Naming the Xgig Chassis

The default name of the Xgig server is the serial number on the bottom of the chassis. The format for the serial number is Xgignnnnnn where nnnnnnnn is a eight-digit number. When changing the name for the Xgig server, make sure you choose a name not used elsewhere in your network.
Using Wireless Connections

For operation of client applications, is not recommended that wireless connections be used as the type of Ethernet connection between the PC running Xgig client software and the network. The software can require bursts of high bandwidth which can cause dropped connections and performance degradation when using a wireless connection. However, this is totally dependent on the capabilities and robustness of the wireless network; there is nothing to prohibit the use of wireless connections with Xgig chassis.
Network Bandwidth Considerations

High bandwidth demands during some Xgig operations may cause unacceptable loads on the network. It may be necessary to configure instrument usage on a special sub-net to circumvent this problem. It is also possible to use a 1Gb/s dedicated link or switch for peak performance.
69
Recommended System for more than 16 ports

Please follow the recommended system requirements listed in the Xgig Analyzer Software Installation Guide for using cascaded Xgig chassis (more than 16 ports). Pentium 4 multicore and/or multi process: clock speed 2 GHz 2GB RAM (8GB RAM is recommended for use with Traffic Summary View) If the Xgig blades have the (optional) larger memory modules installed, additional RAM helps optimize trace processing. When Traffic Summary View processing is employed in standard work flow, we recommend 4GB to 8GB of RAM installed. At least 80GB SAS, SATA II, SCSI U320 storage If .NET Framework is not installed on your system, 80MB disk space is required for this installation. Also, Microsoft Visual C++ Redistributable software requires additional 10MB of disk space. Gigabit Ethernet network - 1000 Mbps data rate
Client systems without enough power will show performance degradation as more ports are added.
70
Problems with Xgig Blade Memory

Memory modules on the Xgig blade can become loose, resulting in a variety of symptoms. Some of these symptoms are: Inability to open a trace Inability to save a trace Opened or saved traces may contain invalid data
If you are having problems like those above or other intermittent problems with particular ports, improperly seated memory on a blade may be the cause. This section outlines the procedure to check if this is the problem and then correct the problem by re-seating the memory.
Running Blade Diagnostics:

Important: CONTACT JDSU TECHNICAL SUPPORT BEFORE RUNNING THIS PROCEDURE. Running diagnostics will reset all ports and require a reboot of the Xgig Chassis. The Xgig Server Debug Page buttons will launch debug processes that can interfere with the normal operation of the Xgig chassis.
If there is problem with improperly seated memory, the memory diagnostics test for the blade will fail. To run this test perform the following steps
1 2
Ensure that power is supplied to the chassis and that you can reach the chassis from a PC through a network connection. Using TraceControl, make sure you set the function for all ports on all blades in the Xgig chassis to the analyzer function. This is required only if you have a license for blades that allows the ports to function as Jammer or BERT ports. If you do not set all ports to the analyzer function you will get an error message when you run the diagnostic program.
Important: Only blades that are licensed for the analyzer function
can use this diagnostic. You cannot run the blade diagnostic procedure if ports on the blade are only licensed for Jammer, Generator, Target Emulator, Load Tester and/or BERT.
71
Chapter 4, Tips and Troubleshooting 3
Log on to the chassis containing the suspect blade using the debug option. Use the chassis name and /debug/ as the URL. For example, https://xgig-3/debug/ The log in dialog appears. Enter the user name and password you normally use to log on to the Xgig chassis.
The page with the menu for Xgig Diagnostics will display. Press the Diagnostic button.
72
The Xgig Server Blade Diagnostic page appears. The page shows the characteristics of all the blades in the Xgig chassis.
Note that if a port function is not set to analyzer, you will see Unknown for the memory size on the Xgig Server Blade Diagnostic page and you will not be able to run the diagnostic.
Press Start Diagnostics. A confirmation message appears to confirm running the routine.
73
Press OK. Diagnostics will be run on all blades in the Xgig chassis and all other connections to the chassis will be severed. The diagnostic routine will run a check of the blade memory as part of its process.The diagnostics take about 10 minutes to run on a chassis with 4 blades. When you launch the diagnostic routine, the Xgig Server Start Diagnostic page appears.
Press Show Status. The Xgig Server Blade Diagnostic page appears showing status. The diagnostics page does not refresh automatically. Press the F5 button to refresh the page and view the progress of the diagnostics.
74
Chapter 4, Tips and Troubleshooting 10 When the diagnostic routine has finished, all tests should say Passed
or Complete.
If tests do not pass, the error is clearly displayed on the Xgig Server Blade Diagnostic page. An example is shown below:
75
Chapter 4, Tips and Troubleshooting 11 If not all memory regions pass the diagnostics for a blade, the memory
on the blade may need re-seating. Identify the Blade by number that did not pass diagnostics and note its slot position within the Xgig Chassis. If diagnostics pass, reboot your chassis and look for re-occurrences of your symptoms. If symptoms still occur, contact customer support.
Caution: Do not attempt to re-seat the memory for Xgig fixed-port
systems. Opening the chassis will void the product warranty and could damage the product. If your memory needs to be reseated, contact Technical Services for assistance.
Memory Re-Seating Instructions

To re-seat your memory you will need the following:
1
An ESD (Electro Static Dissipative) work space Proper personal grounding (ESD heel straps and an ESD wrist strap) Tweezers (if necessary) Power down the Xgig Chassis and remove the blade. The number of the Xgig slot on the chassis corresponds to the number of the blade that did not pass the blade diagnostic. Be sure to follow the proper Xgig Chassis Shutdown Sequence as described in Chapter 2. See the Xgig Blade Hardware Guide for complete instructions for blade removal, and make sure you are properly grounded for this entire procedure. You will notice Memory Module(s) on both sides of the blade. There are two, four, or eight memory modules per side, depending on the blade type. The Memory Modules lie flat against the blade. The Memory Modules are going to be removed and re-inserted into the socket. Any Memory Module can be used in any socket on the blade. With the connection end of the blade towards you, unlock the Memory Modules from one side of the blade. Release the mechanical lock holding the memory by gently pulling out on the clips near the top of the Memory Module. Use tweezers if necessary. The Memory Module pops-up at a slight angle. Note that the number of memory modules on one side of the blade depends on the type of blade. A narrow blade with two memory modules is shown in the following page.
76
.
Mechanical Lock
Memory Module Gently Pull Out to Disengage Lock Second Module is Only Present for the 4-Port Blade Fan Side of Blade
Re-seat the Memory Module by pushing the module straight into the socket.
With Memory in the Tilted Position, Push Memory In to Re-seat
Memory Modules
After re-seating the memory, push down gently on the memory until it engages the mechanical lock. The memory lies flat against the blade when the lock is engaged. If the lock does not engage, do not force. Check to make sure the memory is all the way in the socket and try
77
again. The Memory Modules should click into place in the mechanical lock, the contacts firmly seated in the slot.
5
Flip the blade over and repeat the re-seating memory on the other side. For 2-port blades, there is memory in the right slot only.
Memory Modules
Second Side of Blade
Your Xgig Blade memory has been re-seated.
Validating the Xgig Blade Memory

Once the memory has been re-seated, verify that the blade now passes diagnostics.
1 2 3 4
Insert the upgraded blade into an un-powered Xgig chassis. Apply power to the chassis and establish communication with the chassis. Repeat all steps in the previous section on Running Blade Diagnostics. If the diagnostics now pass, you have corrected any memory contact problems on the blade. If diagnostics still do not pass, contact JDSU Technical Support.
78

X Gig Family Hardware

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

X Gig Family Hardware

Uploaded by

Copyright:

Available Formats

Xgig Family Hardware Guide