FCA Basic Setup

8/11/2019 FCA Basic Setup

1/15

Finisar Analyzer Config Instructions

Finisar Analyzer Config Instructions ...................................................................................................................... 1

Finisar Analyzer setup ............................................................................................................................................ 2

Section A ............................................................................................................................................................. 2Setting up ........................................................................................................................................................ 2

Section B ............................................................................................................................................................. 3

Selecting the analyzer ..................................................................................................................................... 3

Configuring the analyzer..................................................................................................................................... 5Finisar Cascading Setup .......................................................................................................................................... 9

Connecting/Disconnecting PC from analyzer while analyzer running ................................................................. 12Default Triggers: ................................................................................................................................................... 12

Note: Some time ago JDSU bought the network tools division of Finisar. As a result JDSU now owns Xgig

analyzer and other Finisar Tools. For the time being, we continue to use the word Finisar instead of

JDSU.

This document is intended to be a quick guide to installing and setting up the Finisar Xgig analyzer. The

screen shots in this document use screen captures from Finisar Software version 5.0 or later. If using

software version earlier than 5.0, some of the GUI screen will appear different.

For more detailed explanations of the analyzer and software, refer to the Users Guide and other

pertinent documents in the directory: C:\Program Files (x86)\JDSU\Xgig Analyzer\XgigDocs.

This assumes you have installed Xgig Software on your system.


2/15

Finisar Analyzer setup

The following diagram depicts the typical setup we recommend:

Materials included:

See checklist provided

Section A

Setting up

1. Remove the analyzer and the laptop and other supplies from the container.

2. Connect your network cable from your LAN to the first port on the Router/Switch.3. Connect one of the supplied network cable from the management port on the analyzer to the second port

on the Router/Switch

4.

Connect the other supplied network cables from the laptop to the third port on the Router/Switch.5. Connect the RS232, DB9 connector, serial cable to the COM port on the laptop and the other end to the

console port on the analyzer

6. Connect the Router/Switch power supply 12 V DC plug to the Router/Switch where it is labeled 12VDC.

7. Connect the other end of the power supply to your 120V AC outlet. The switch will now be on showing

the green LEDs on.8. Connect the laptop power supply cable DC plug to the DC input of the laptop and plug the other end into

your 120V AC outlet.

9. Connect the AC power cord to the analyzer and plug it into your 120V AC outlet

10.Turn on the laptop


3/15

11.Turn on the analyzer. The power switch for the analyzer is located at the bottom right corner at the front

of the chassis.12.The username for the laptop is: admin1 and the password is also: admin1

13.To start the analyzer click on the Xgig trace controller link shortcut on the desktop See figure 1 below.

Figure 1

14.When the analyzer application is loaded, the GUI from application shall be used to select and configure

the analyzer (see Section B below for more details).15.At this point, you can connect the analyzer into the SAN. Note, when connecting up, it is always useful

to try to have consistency when connecting ports. For instance, if connecting the analyzer between the

switch and 4 ports of an array, it is good to use all even ports (or odd) connecting to the switch ports andthe opposite going to the Array ports. When the person analyzing the trace knows that all even ports (or

odd) are connected to the switch, it makes it easier to follow. Also, remember to connect things in port

pairs. For instance, if connecting the analyzer between the HBA and a switch. If you connect the HBA

to port 1 on a blade, then you MUST connect the switch port (which the HBA was previously connected

to) to port 2 on the same blade and so on...

Note: If international shipment, use appropriate power converters/plugs for steps above that deal withapplying power.

Section B

Selecting the analyzer

1. When the application is loaded, select the blue chassis button that is displayed in the upper left hand

corner of the GUI. The button is left of the wrench symbol as shown here (see area circled in RED):

2.

The discovery page will be displayed. Click on discover, this should bring up your analyzer with all theblades (if not already present in the Sync Group(s) window). If the analyzer is not visible, then you

need to put in the IP address of the analyzer and click Discover. The screen should look like this (with

Discover and Sync Group(s) circled in RED):


4/15

3. The IP address of the analyzer can be determined by starting a Hyper-Term session. There should be a

Hyper-Term configuration file already saved for the Xgig chassis. The name of the file is xgig. If you

cant get the file to work, configure the same com port on the laptop to which the RS232 cable isconnected using the following: speed=57600, data=8 bits, parity=none, stop bits=1, Flow control=none

4. Once you complete the above step, you should be able to get a console display of the analyzer menu. In

the menu, you should see the ip address. Put that IP address in the address bar of the analyzer asmentioned in step 2 Section B

5. After entering the IP address click discover, the analyzer ports should be displayed.

6. The ports can be selected by clicking on them. They will all be displayed with white background but

once selected will have blue background.7. The analyzer has some multifunction blades so you have to specify the mode of operation of the ports.

Point to each port and right click while the pointer is on the port. You will be presented with the

statement use port as

8.

Move the mouse pointer over the statement use port as. If you are presented with the following:a. Analyzer Fibre Channel

b. Analyzer Gigabit EthernetThen select Analyzer as Fibre Channel.

Note the two choices are only for multifunction blades, by default the other blades only choice is Fibre

Channel9. After selecting all the ports click on Create and Lock. This will lock these ports for use by you and

then bring you back to the main menu. See the screen capture below for what the screen should look like

after you click on the ports interested in:


5/15

Configuring the analyzer

1. On the analyzer main menu you should see: My Domain, the analyzer name along with the number of

analyzer ports the analyzer has in a tree structure formation

2. You configure the ports by first selecting the open ended wrench which will bring you to theconfiguration page. This information can be seen here:

3. On the configuration page (see screen capture below) click once on My Domain entry. At this pointyou will select the necessary configuration for the ports you will be using on the analyzer.


6/15

Here is a sample config setup:

o As you can see in screen capture above, this screen gives you a high level view of some key

information and how ports are configured. On this screen you can change the Trace Size,Frame/Payload size, Signal Regeneration and Link Speed by clicking on each pull down. Our default

recommendation is to set these as specified here (again, make sure you have select My Domain as

this will allow you to set items once and will be applied to each port unless you want different

settings on individual ports in which case you would select the specific ports): Set the Trace Size to MAX allowed (this is dependent on which analyzer you have). Set Payload Size to 128 (or whatever you prefer depending on trace planning to capture).

Note, do not set lower than 64 bytes as this could be insufficient. Signal regeneration should be: Analog Passthough

Clock should be appropriate speed for customer config (1, 2, 4 or 8Gb) for each port.o

Now, in order to setup triggers, you must select the Trigger Setup Tab (near top left). This willbring up another screen (see screen capture below) that will allow you to configure the current port

as needed. First thing you want to do is select the Trigger Mode using the pull-down menu. Select

Trigger from this menu (see item 1 on screen capture below). Next, you need to click on the Pre-Triggered window (see item 2 on screen capture). Here you want to make sure that the Capture

These window contains Any Traffic (see item 3 on screen capture). If not, delete what is there byselecting and hitting delete key on keyboard. Then drag over from the Finisar library to the left Any

Traffic into the Capture These window. This will ensure analyzer captures all traffic. Next, youwant to click on the if section of the GUI (see item 4 in screen capture). Here you will setup the

triggers (note, you will see similar screen to one below). All you need to do is find the following

default triggers (or other agreed upon triggers) from the available templates window in the middle ofthe screen (similar to what was done for dragging over Any Traffic above) but this time each of

these triggers will be dragged into Wait for any of these box in the window that comes up when

you click on if section of the GUI (item 4 in screen capture below):

Any Error this is in Finisar Library under Bit Error Triggers

ABTS Abort Sequence this is in Finisar Library under FC Basic Link Services LR this is in Finisar Library under Ordered Sets (1-8Gig)

OLS this is in Finisar Library under Ordered Sets (1-8Gig)

Note: there is a maximum of 4 triggers per channel and each channel can have different triggers ifdesired.

o Next, click on the TRG: Triggered section of the GUI (see item 5 in screen capture) and set Post

Fill to 15% (or whatever you prefer depending on trace planning to capture).


7/15

o The click Apply to all port pairs (item 6 in screen capture) to apply current port settings to all port

pairs. Obviously, if you wanted to have different settings for different ports, you would not want todo this. Again, we are just identifying a default setup.

o When done with this, your screen should look like the following screen capture. If it does, click

OK or correct anything needing correction.

4. When you are finished with the above, you can verify that all the ports have the same configuration by

selecting the other port pairs and making sure they are in fact the same.5. Once you select OK, you return to the top level analyzer Trace Controller Screen. On this screen, you

need to now select the icon that is to the right of the lock on the menu bar to apply the configuration

changes. This can be seen here (see icon circled in RED):


8/15

Note, you may be prompted with an alert message about configuration mismatch hardware setting. Thisis normally a change in the fibre channel speed rate of the port. If you are doing 2 Gbps and the port is

switching from 4 Gps to 2 Gps then accept the changes. Basically you want to ensure that all the ports

are running at the appropriate FC link speed.6. If you want, you can now rename the ports as you wish. To rename the port right click on the port name,

select rename port then type in the name that you want to use.

7. Note: To switch back and forth between the configuration page and the main menu always click on the

open-ended wrench.8. You can save your configuration by selecting file, then save configuration as, (select a directory and a

file name that you want to use for your configuration file) use whatever name you want to use.

9. At this point, you are ready to start the analyzer. The analyzer is started by clicking the green triangleicon in top middle of GUI. Once you select this, the red stop sign icon to the right of it will light up. This

is letting you know you can stop it manually if you want by pressing this button. The analyzer is now

running and capturing traffic. If you setup a trigger, you should see the State field indicatingPostfilling (Running) message. If the analyzer detects a trigger, it will stop the analyzer automatically

and the green triangle for starting the analyzer will be lit up again. Also, the State field will change

indicating you have a capture available. If we do get a trigger make sure you SAVE TRACE (below)

before hitting start again otherwise trace will be lost.

10.Saving trace.Once the analyzer is triggered or stopped manually, you can save the trace by clicking on

File (top left corner) then Save Trace in the Trace Controller GUI. You will be prompted for whereto save the trace. You can create a directory and store it there. It is good to put a date or timestamp or

something unique in the trace in case we start to capture a lot of them. Then save it. Once done, if you

bring up windows explorer and go into that directory you created, you will see 17 files that make up thetrace (for 16 channel analyzer). There are 16 .trc files (one for each port on analyzer) and a .tgp file

which is the file you would click on to bring up the trace. Zip all 17 files (or 9 file for 8 channel

analyzer) into a zip file and provide traces to appropriate person.

As mentioned, at any time you can stop the

analyzer simply by hitting the stop button.

11.When providing a trace, the following information can be very helpful in getting to root cause quickly:o Identify what analyzer ports are connected to what

Note, ports are labeled as follows: Chassis = 1 (if cascading Chassis, next one would be 2 and so on), Blade # is

written on analyzer (1 4 for 16 channel) and port number is written on Blade (1

4). So, if an HBA is connected to Port 1 of Blade 1, chassis 1, you would simply

indicate HBA is connected to 1,1,1. Then if port 2 was connected to the switch

that the HBA was previously connected to, you would say 1,1,2 is connected tothe switch that the HBA was previously connected to, etc.

o Identify what was done during trace captureo

Provide useful information about problem. For example, if path loss issue, try to specify 24 bitaddress (port ID) of the HBA that lost the path and the Port ID of the Array that the path was lost

to. If it was a data corruption, provide failing LBA, Lun, Expected Data, Actual Data, location in

LBA where the corruption is (e.g. offset is 0 for start of the block, etc.).o Provide supportShow from root (if Brocade switches involved

o Provide a SAN diagram if possible. Ideally showing location of analyzer.

Note: While the above is not always necessary, it can save a LOT of time root causing the trace.

12.Again, if using a smaller Xgig analyzer, setup is virtually the same.


9/15

Finisar Cascading Setup

Cascading Xgig analyzers allows the ability to capture a single trace across more than one Xgig analyzer. All

trace events in the trace are time synchronized (i.e. looks like a single trace and everything in trace is timesynchronized). This is preferable to having two separate analyzers capture two separate traces (which would

NOT be time synchronized making it much more difficult to correlate events and determine what is going on).

Figure 2 Cascading Connection

For cascading, both analyzers must be connected as shown in figure 2 above. The com port connection betweenthe laptop and analyzer is optional. The connection is necessary only if the IP address of the analyzer is not

known or cant be discovered as explained in Section B above.It is critical that the same version of FinisarSoftware / Firmware is being run on both analyzers otherwise this is unlikely to work.

Note that Cascade Out is connected to Cascade In with the network cable (RJ45). Do NOT use a cross-over

cable for this connection. A standard RJ45 cable is needed for this.

If you do not have a Router / Switch, simply connect each analyzer and laptop to the LAN directly and you

should be able to discover the analyzer through the Trace Controller. If configured properly, you will see image

of two Xgigs on top of each other reflecting cascading in effect.


10/15

It is important that the cabling is done before the analyzers are powered up. This allows for both

analyzers to synchronize for cascading operation.

If you encounter problems, you will need to connect laptop to Com port and validate IP settings, etc. For ease of

connectivity, the analyzers can be configured as DHCP (using Com port). Determine the DHCP generated IPaddress and then type that address into Discover window (within Create Domain window). Then you should

see the Cascaded analyzers.

Here are two snippets providing some additional information (and show graphically how a cascadedconfiguration would look within GUI):


11/15


12/15

Connecting/Disconnecting PC from analyzer while analyzer running

To disconnect and reconnect to a domain:

1. Once you have the TraceController configuration setup the way you want and analyzer running, etc.You can disconnect from the analyzer domain you setup by shutting down the TraceControl application

or by selecting another domain within TraceControl that has no ports in common with the first domain.

At this point you can remove your laptop or PC from the hub or analyzer. The analyzer will continue torun if you left it running.

2. You can reconnect to the domain from the same client laptop or PC or from another client PC running

TraceControl (note, make sure running same version).

Reconnect using the Select Ports for Domain Creationdialog box. Press the Create Domain

button to bring up the dialog and select the name of the domain from theDomain(s)list. Press theReconnectbutton to reconnect to the domain.

Default Triggers:

Any Error this is in Finisar Library under Bit Error Triggers

ABTS Abort Sequence this is in Finisar Library under FC Basic Link Services

LR this is in Finisar Library under Ordered Sets (1-4Gig)

OLS this is in Finisar Library under Ordered Sets (1-4Gig)


13/15

In case capturing should be restarted automatically after trigger:

Tools Automated Options


14/15


15/15

Documents

FCA Basic Setup