Agilent System Protocol Test Release Note

Transcription

1 Agilent System Protocol Test Release Note Release 6.0, Build October 2006 This document provides information on fixes and known problems for the software released with this version. This version includes enhancements over the generally available 5.5 release ( ). This release note contains updates for FcPerformance (SanTester).

2 FcPerformance (SAN Tester) This section contains the following information: New Product Features Known Problems Problems Resolved 1. New Product Features The new release software now supports the 1733L SAN Director Test system. The 1733L consists of 32 modules (or 128 ports) of 2/4Gbps ports, with the capability to generate full line rate I/O simultaneously. Through the support of multiple traffic streams with multiple exchanges and tracking of sequence numbers, Agilent SAN tester adds the ability to ensure that switches deliver frames in the same exchange in order. 2. Known Problems AgtResetSession doesn t fully reset the session parameters. Some session parameters such as state change notification (enabled/disabled) needs to be reset manually. GUI updates of port state machine states are not always correct. For example, when a Name Server registration has succeeded, the text for the LED status will show Enabled, but the LED remains yellow. In these cases, the text has the right state, not the LED. This mostly occurs with large numbers of loop devices on one port. With certain operating systems, after selecting ports to use, the ports do not show up in the main GUI. This is due to the higher security settings on certain operating systems. To overcome this problem, use the setup recommended in the appendix. Modules do not reboot correctly. Instead they scroll "FLSH NB [] Unable to download boot rom", or stuck in the BAPP state. This is due to the FTP service not started correctly. See Appendix 2 on how the FTP service can be started. 3. Problems Resolved GUI SAD The maximum number of GUIs connected to one session was not shown correctly on the dialog. When the user changed this value, it was in fact updated correctly in the system, but the GUI still showed the max number of GUI connections allowed was one. Software SAD Running multiple sessions through a single chassis to chassis connection cable causes the sessions to close unexpectedly. SAD S_ID & D_ID values does not reflect user values. When the values are set to a non-default value, the system used to still use the default instead of user defined values. SAD GetStreamDetails doesn t return the correct information regarding the stream source and destination

3 SAD When changing the WWN value in PLOGI frame, this is not reflected by the PLOGI sent out by the hardware SAD When a link is turn off and on quickly (turn laser off and on quickly) there are some instances where the traffic continues sending before the FLOGI is completed SAD Once E_D_TOV value set manually, could not switch back to auto SAD On very large scale systems (128 ports at the same time) and running for long periods of time (overnight tests), there were cases when the latency reported took on very large values in the order of tens of seconds SAD R_RDY delay generated was not the exact value the user set, it was off by a factor of 2 Loop Mode Operation SAD /SAD If the SanTester port is set to 4G, and NL mode, traffic could not be sent from this port. This was due to a problem with the OPN message on the port state machine. SAD When two ports on the SanTester are configured as NL mode, and connected back to back, there were cases when the traffic load could not reach 100% of line rate. SAD Some emulated devices would not register with name server Scripting & API SAD Self Test Diagnostics did not work correctly. The script reported an error with the modules in the system when the modules were in fact in working order. SAD FrameTransmitter & FrameSequenceTransmitter does not load the GPB correctly. This was due to a missing file in the installation process. SAD PlotLogFile script could not be launched. This script can now be launched from the main GUI, or from the Quicktest browser. SAD Error in launching the SCN Log. SAD Quicktest cloning of test failover recovery would not work SAD Diagnostics does not exit on all operating systems cleanly brings up a error dialog before exiting.

4 Appendix 1 DCOM settings for client mode access Some operating systems have tigher security settings which do not allow applications to remotely access local processes. This causes problems when trying to operate in client mode. In these cases, it is necessary to manually change the security settings to allow client mode to work. To set up a DCOM server You must configure the tester PC s DCOM security to allow remote computers to access AgtResourceManager. If you are using Windows XP with Service Pack 2 onwards, you must manually enable access privileges that are blocked by the Service Pack. Important: Each time you install a new version of the N2X platform software, you must reconfigure the DCOM permissions as described below. Windows 2003/XP 1. From the Windows Start menu, select Run. The Run 2. Type dcomcnfg. The Component Services 3. In the left pane, select Console Root > Component Services > Computers > My Computer > DCOM Config. 4. In the right pane, right-click AgtResourceManager and select Properties. The AgtResourceManager Properties 5. Click the Security tab. 6. Under Access Permissions, select Customize; then click Edit. The Access Permission 7. Click Add. The Select Users, Computers, or Groups 8. Under Enter the object names to select, type Everyone. 9. Click OK to close the Select Users or Groups dialog box. If the Multiple Names Found dialog box is displayed, select Everyone and click OK. 10.Click OK to close the Access Permission dialog box. 11.On the Security tab of the AgtResourceManager Properties dialog box, under Launch and Activation Permissions, if you are using: Windows 2003/XP/XP SP1 select Use Default and click OK. Windows XP SP2 and later follow all the instructions under Windows XP SP2 and later 12. Restart the PC. Windows XP SP2 and later You must also complete the following to allow remote, anonymous users to access and activate AgtResourceManager and COM: 1. On the Security tab of the AgtResourceManager Properties dialog box, under Launch and Activation Permissions, select Customize and click Edit. The Launch Permission 2. Click Add. The Select Users or Groups Under Enter the object names to select, type ANONYMOUS LOGON. Click OK. 3. On the Launch Permission dialog box, under Group or user names, select ANONYMOUS LOGON. Under Permissions select Allow in the Remote Activation row. Clear all other check boxes.

5 Click OK to close Launch Permission and AgtResourceManager dialog boxes. 4. On the Component Services dialog box, left pane, select Console Root > Component Services > Computers. Right-click My Computer and select Properties. The My Computer Properties 5. Click the COM Security tab. In the: Access Permissions area click Edit Limits. The Access Permission Under Group or user names, select ANONYMOUS LOGON. Under Permissions select Allow in the Remote Access row. Click OK. Launch and Activation Permissions area click Edit Limits. The Launch Permission Click Add. Under Enter the object names to select, type ANONYMOUS LOGON. Click OK. Under Group or user names, select ANONYMOUS LOGON. Under Permissions select Allow in the Remote Activation row. 6. Click OK to close all dialog boxes. 7. From the Start menu, select Control Panel > Windows Firewall. The Windows Firewall On the: General tab select On (recommended). Exceptions tab click Add Program. The Add a Program Click Browse. Navigate to and select the program C:\Program Files\Agilent\SystemProtocolTester\bin\resourcemanager.exe Click OK. In the Windows Firewall dialog box, under Programs and Services, ensure that the check box next to resourcemanager.exe is selected. 8. Click OK. Windows From the Windows Start menu, select Run. The Run 2. Type dcomcnfg. The Distributed COM Configuration Properties 3. On the Applications tab, select AgtResourceManager; then click Properties. The AgtResourceManager Properties 4. On the Security tab, select Use custom access permissions; then click Edit. The Registry Value Permissions 5. Click Add. The Add Users, Computers, and Groups 6. From the list of names, select Everyone; then click Add. Click OK to close the Add Users and Groups dialog box and the Registry value permissions dialog box. 7. On the Security tab of the AgtResourceManager Properties dialog box, select Use default launch permission; then click OK. 8. Click OK. To set up a DCOM client You must configure the client PC s DCOM security to allow remote computers to access AgtResourceManager. If you are using Windows XP with Service Pack 2 onwards, you must manually enable access privileges that are blocked by the Service Pack. Important: Each time you install a new version of the N2X platform software, you must reconfigure the DCOM permissions as described below. 1. Launch the Component Services dialog box (Start --> Control Panel --> Administrative tools

6 --> Component services ) 2. On the Component Services dialog box, left pane, select Console Root > Component Services > Computers. Right-click My Computer and select Properties. The My Computer Properties 3. Click the COM Security tab. In the: Access Permissions area click Edit Limits. The Access Permission Under Group or user names, select ANONYMOUS LOGON. Under Permissions select Allow in the Remote Access row. Click OK.

7 Appendix 2 Restarting the FTP server PCs with IIS installed Right click on My Computer, and select Manage. In the window that pops up, select services. Check to see if the FTP Publishing service is running. If it is not running, select the service manually and click on the start button at the top of the dialog. PCs with no IIS installed PCs not running the IIS service is running the WarFtp installed by Agilent. Right click on My Computer, and select Manage. In the window that pops up, select services. Check to see if the WarFtp service is running. If it is not running, select the service manually and click on the start button at the top of the dialog. Any edits to the WarFtp can be made using the configuration tool. NOTE: These edits can affect the connectivity between the controller and the chassis, and you may not be able to re-establish control without a re-install. The configuration files for the WarFtp can be found at: C:\Program Files\Agilent\SystemProtocolTester\war-ftpd o To launch the GUI, double click on StartManager.wdm, or drag and drop it onto the WDM.exe icon o To log the activity to a file: In the GUI go to Server/Advanced server properties Select log_logfile Copy and paste Log/%Y-%m-%d.log at the bottom into the Value text box.