IxNetwork FAQ Guide
Release 7.00 EA Part No. 913-1626 Rev A December 2012
Copyright and Disclaimer
Copyright © 2012 Ixia. All rights reserved. This publication may not be copied, in whole or in part, without Ixia’s consent. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to the restric- tions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. Ixia, the Ixia logo, and all Ixia brand names and product names in this document are either trademarks or registered trademarks of Ixia in the United States and/or other countries. All other trademarks belong to their respective owners.
Corporate 26601 W. Agoura Rd. Web site: www.ixiacom.com Headquarter Calabasas, CA 91302 General: [email protected] USA Investor Relations: [email protected] +1 (877) FOR IXIA (877-367-4942) Training: [email protected] +1 (818) 871 1800 (International) Support: [email protected] (FAX) +1 (818) 871-1805 (877) 367 4942 [email protected]
EMEA Ixia Europe Limited Support: [email protected] Avonbury Business Park, Unit 5 +44 1869 356370 (Option 5) Howes Lane Bicester, Oxfordshire, OX26 2UA United Kingdom +44 1869 356370 (FAX) +44 1869 356371 [email protected] Asia Pacific Asia Pacific Representative Office Support: [email protected] New Shangai International Tower, Suite 26E (877) 367 4942 360 Pudong Nan Rd Shanghai 200120 China +86 21 50543439 [email protected]
Japan Ixia KK Support: [email protected] Aioi Sampo Shinjuku Building, 16th Floor (877) 367 4942 3-25-3 Yoyogi Shibuya-Ku Tokyo 151-0053 Japan +81-3-5365-4690 (FAX) +81-3-3299-6263 [email protected]
India IXIA Technologies Pvt. Ltd. Support: [email protected] Tower 1, 7th Floor, UMIYA Business Bay +91 80 49396400 Cessna Business Park Online Support Form: Survey No. 10/1A, 10/2, 11 & 13/2 http://www.ixiacom.com/support/inquiry/?location=india Outer Ring Road, Varthur Hobli Kadubeesanahalli Village Bangalore East Taluk Bangalore-560 037, Karnataka, India +91 80 42862600
For viewing the FAQs related to the product, go to Ixia Technical Support Online: https://ebsoprod.ixiacom.com/OA_HTML/jtflogin.jsp
Contents
Introduction ...... 1
Installation/Upgrade...... 2
Licensing ...... 13
Procedure...... 14
Version Compatibility ...... 17
Definition ...... 30
Troubleshooting ...... 32
Error Messages ...... 41
Other ...... 48
IxNetwork FAQ
Introduction
This document comprises the Frequently Asked Questions (FAQs) regarding IxNetwork. The FAQs exist for IxNetwork version 6.10 or earlier. These issues are faced by external as well as internal users of IxNetwork. We have categorized the frequently asked question in the following manner:
Installation / Upgrade Licensing Procedure Version Compatibility Definition Troubleshooting Error Messages Others Resolutions of these problems have been provided by the IXIA engineers. For more up-to-date information on existing FAQs, visit https://ebsoprod.ixiacom.com/OA_HTML/jtflogin.jsp.
1
IxNetwork FAQ Installation/Upgrade
The installation/upgrade related questions are as follows:
1. Installing IxOS on Windows 2003 Server Terminal Service gets a few unexpected dialog boxes 2. IxNetwork\IxAutomate installation failed with Error "Microsoft SQL Server Express 2005 SP2 setup failed" along with MSXML install error 3. IxNetwork 5.40 installation failed. 4. Large installer packages like IxLoad 4.30 and IxNetwork 5.40 may fail while trying to extract the files during installation. 5. Sample IxNetwork Fast Reroute (FRR) configuration 6. IxNetwork 5.30 SP5 Patch1 install on VM windows 2003 server failing SQL setup 7. IxNetwork 5.30sp3 patch1 Installation "hang" without any error messages in bootstrapper.log 8. Unable to install application due to Error: Windows cannot access the specified device, path, or file. 9. IxNetwork Help files Installation along-with IxNetwork 10. IxNetwork Installation on Windows Client. 11. SQL Express 2005 error when installing Ixia software on an Ixia chassis 12. Installing IxNetwork-FT 5.60EA with IxOS 5.60GApatch1 on client pc - FT does not show up 13. 'IxNetwork installation is not supported on this platform 6.0.0 64-bit. Please check the release notes for the list of supported platforms' message is shown when trying to install IxNetwork 6.0 EA on Win 7 64 bit machine. 14. Installing IxOS on Windows 2003 Server Terminal Service gets a few unexpected dialogue boxes 15. IxNetwork 5.40 installation failed...why? 16. IxNetwork 5.30 EA SP5 compatibility issue with the IxOS 5.20 GA P2 17. I have been trying to upgrade the IxNetwork software on the XM12 chassis this morning and it keeps hanging at the installation window. The window that says ‘this may take a few minutes’ has a status bar. I waited 45 mins and the status bar never change so I killed the process and attempted to back out the install. Now I am trying to re-install the software and it appears to be hung again. 18. Install IxNetwork Help files along with IxNetwork 19. Installation limitation of IxNetwork in Windows 2003 with non-English locales 20. Error 1920-IxNetwork.Reporting service fails to initialize 21. Error 27506 when installing Aptixia Application (Sql Error) 22. Installation error of SQL 2008 while installing IxNetwork
1. Installing IxOS on Windows 2003 Server Terminal Service gets a few unexpected dialog boxes
Description
2
IxNetwork FAQ
The user sees one or two popped up box during the installation. The message reads something like this, ‘When the installation has ended (successfully or not), please click the Finish button or the Cancel button. Do not click the buttons before installation has ended!’
Resolution
This happens when the server is not in the "installation mode" with Terminal Service on Windows 2003 server. In order to avoid this nuisance, you have to open a command shell, disable logins and put the server into installation mode. More details can be found at
http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.terminal_services/2006- 11/msg00440.html
Before installing applications on a Terminal Server, you must put the server into "install mode". In this mode, all changes made to the registry and to ini-files will be monitored and copied to the shadow area in the registry. This process ensures that all users will receive their personal copy of those registry keys and ini-files. You can put a Terminal Server in Install mode by using the Add/Remove Programs tool in Control Panel, but this method does not work when you install applications directly from the web.
A method which gives you more control over the process is to put the server into install mode from the command prompt:
I. Open a command window (Start - Run - cmd) II. Type ‘change logon /disable’ (without the quotes). This does not allow new connections to the server III. Use Terminal Services Manager to verify that there are no user sessions; send a message to connected users, requesting them to log off IV. Type ‘change user /install’ (without the quotes) to put the server into install mode V. Install your application VI. When the installation is completely finished, type ‘change user /execute’ to put the server back into its normal execute mode VII. Type ‘change logon /enable’ to allow users to connect again Further reading:
Checklist: Installing applications
http://technet2.microsoft.com/WindowsServer/en/Library/8ef377c7-3815-4b1c-9cd5- b7950120c0c21033.mspx
2. IxNetwork\IxAutomate installation failed with Error "Microsoft SQL Server Express 2005 SP2 setup failed" along with MSXML install error.
Resolution
MSXML and SQL database setup failed during IxNetwork installation
I. Run the Windows Installer CleanUp utility. (attached)
3
IxNetwork FAQ II. Select MSXML6 Service Pack 2 (KB954459) [6.20.1099.0] in the list, and then click Remove.
3. IxNetwork 5.40 installation failed.
Resolution:
Recently one of our SE ran into a problem with IxNetwork 5.40 installation. While running the installer, it was failing with error 1721
SE first tried to install IxNetwork + Test Conductor package. He was running into some problem with IxNetwork, so he tried to 'repair' the IxNetwork at this point he was getting these errors (see snapshot). After troubleshooting we learned that IxNetwork + TC and IxNetwork standalone installer they both are separate. In this case, for some reason IxNetwork installer got confused with IxN +TC installer, hence it generated error.
According to engineering DO NOT try to run install IxN +TC and IxN installer on a same client PC. You may run into unexpected error.
4. Large installer packages like IxLoad 4.30 and IxNetwork 5.40 may fail while trying to extract the files during installation
Resolution
IxLoad 4.30 and IxNetwork 5.40 EA combo installer (IxNetwork 5.40 EA + TC 2.20.10.38.EA.Patch1) may fail with following error:
‘Windows cannot access the specified device, path or file. You may not have appropriate permissions’
or
‘There is not enough space on drive c:\ to extract this package’
This error may occur with other Ixia packages if the installer is large (more than 700MB in size).
IxNetwork (5.40 EA + TC 2.20.10.38.EA.Patch1) combo installer is about 1GB and IxLoad 4.30 is about 800MB.
5. Sample IxNetwork Fast Reroute (FRR) configuration
Resolution
Herewith attaching sample configuration of RSVP Fast Reroute (FRR) feature. This configuration is saved using IxNetwork 5.30 SP5 build
4
IxNetwork FAQ
6. IxNetwork 5.30 SP5 Patch1 install on VM windows 2003 server failing SQL setup
Resolution
The ‘IxNet 5.30 SP5 Patch1’ install fails SQL setup, on a VM running Windows 2003 Server 32bit.
The issue occurs when installing using Remote Desktop as the administrator. The installer fails during the SQL setup ’SQL Server Database Services’, and then the install is aborted (see error1 attached). I get error2 (attached) after aborting the install.
Error1 seen:
Verify that the file exists and that you can access it (manifest file)
Error2 seen:
An attempt has been made to operate on an impersonation token
The issue was resolved by doing the following.
When the install failed, we rolled back the install. Then directly from the console, all SQL components were removed. Then the install was repeated from the console.
***Removing all SQL and repeating the install from RD, did not resolve the issue. It had to be done from the console directly.
7. IxNetwork 5.30sp3 patch1 Installation "hang" without any error messages in bootstrapper.log
Resolution
We encountered a very strange installation issues. IxNetwork did not proceed.
There was no progress bar. Bootstrapper and IxNetwork_xxx_instal_normal.log did not show any error message.
This was a brand new HP laptop from the customer. Microsoft Office was installed. We found out that scrrun.dll was not registered on the system.
Use:
regsvr32 c:\windows\system32\scrrun.dll
5
IxNetwork FAQ 8. Unable to install application due to Error: Windows cannot access the specified device, path, or file.
Resolution
When trying to install/launch application you may receive this error: “Windows cannot access the specified device, path, or file”.
To resolve this, go to add/remove windows components, and then uninstall the Internet Explorer Enhanced Security component.
This will mostly occur on Windows 2003.
9. IxNetwork Help files Installation along-with IxNetwork
Resolution
Follow the steps given below:
Double-click the IxNetwork.exe file from the Installation CD. Follow the instructions to automatically install IxNetwork Help files along with IxNetwork on Windows Client.
NOTE: Refer to the video AIM-Defining the IxNetwork document structure.mcmovie and Getting_Started_with_IxNetwork.mcmovie for further information.
10. IxNetwork Installation on Windows Client.
Resolution
Double-click the IxNetwork.exe file from the Installation CD. Follow the instructions to automatically install IxNetwork in Windows Client.
NOTE: Refer to the video Getting_Started_with_IxNetwork.mcmovie for further information.
11. SQL Express 2005 error when installing Ixia software on an Ixia chassis
Description
How can you fix SQL Express 2005 server error when installing Ixia software on an Ixia chassis?
Resolution
If you are getting the error below when installing any Ixia software on an Ixia chassis:
‘This product requires that your computer is running Microsoft SQL Express 2005. SQL may not have been installed because its installation was cancelled. Please ensure that the installation of SQL Express 2005 was successful.’
6
IxNetwork FAQ
Another error that has been seen when installing IxLoad on an Ixia chassis:
MSI log: Type=Error ID=10005 Event=Product: Aptixia IxLoad Chassis 5.10.151.76 – This product requires that your computer is running Microsoft SQL Server 2005Express with Ixia2005 instance. It may not have been installed because its installation was cancelled. Please ensure that the installation of SQL2005Express (Ixia2005 instance) was successful. SQL2005 requires that your computer is running the windows service named ‘SQL Server (IXIA2005)’. Ensure that the ‘SQL Server (IXIA2005)’ service is running before you install this product. To enable the ‘SQL Server (IXIA2005)’ service, you must first install File and Printer Sharing for Microsoft Networks. For more information about how to enable File and Printer Sharing, see Microsoft Knowledge Base item # 325860
Check both of the following on the Ixia chassis:
Environment Variable.
Close out the window and exit installation. Go to Start --> Control Panel --> System --> Advanced and choose Environment Variables. Check that there is a System variable with the value of ‘ChassisSN’ that is appropriate for your chassis. For example:
Variable name: ChassisSN
Variable value: XM12-1260040
If this variable doesn't exist, click on ‘New’ under System Variables at the bottom of the Environment Variables screen and create it.
Missing oeminfo.ini file.
Check if the file oeminfo.ini exists under C:\Windows\System 32\. If you do not have it, please create an oeminfo.ini file with the information as shown below. You can also download the file with the content from this KB. Remember to substitute Ixia 250 with the appropriate model for your chassis.
***Start below***Do not include this line
[General] Manufacturer = Ixia Model = Ixia 250 SupportURL = http://
[OEMSpecific] SubModel = 4002k SerialNo = 12345678.
[ICW] Product = Ixia 250
[Support Information] Line1 = For technical support:
7
IxNetwork FAQ Line2 = In the USA, call 1-877-FOR-IXIA for software and hardware support. Line3 = Line4 = International, call 1-818-871-1800 Line5 =
***End above***Do not include this line
Restart the Ixia software installation. The installation will complete this time. After it is completed, remove oeminfo.ini file.
12. Installing IxNetwork-FT 5.60EA with IxOS 5.60GApatch1 on client pc - FT does not show up
Description
Installing IxNetwork-FT 5.60EA with IxOS 5.60GApatch1 on client pc - FT does not show up When installed this version of IxNetwork-FT with this version of IxOS on a client PC, the user will not be able to launch IxN. They will only see the IxR icon and no protocols will be accessible. This appears to happen even if a full IxNetwork install is done or if the IxNetwork-FT feature installer is used. The install did work as intended on the chassis using the same builds.
Resolution
To fix the issue, try the following: Case 1: boost_thread-vc80-mt-1_33_1.dll file is missing from IxN-Protocols install location on client. Please copy boost_thread-vc80-mt-1_33_1.dll file from chassis installed location to the client IxN- Protocols install location. (If it is absent from client install location.) Restart the Network-FT. It should work.
13. 'IxNetwork installation is not supported on this platform 6.0.0 64-bit. Please check the release notes for the list of supported platforms' message is shown when trying to install IxNetwork 6.0 EA on Win 7 64 bit machine.
Description
The cause of this error is that, on Win 7 64 bit, IxNetwork Self Extracting Installer is run in compatibility mode with Win 2008 or Win Vista whereas the IxNetwork installer is compatible with a higher version of these operating systems.
Resolution
This message comes towards the beginning of the IxNetwork 6.0 EA installation on Win 7 64 bit machine. There is a check in IxNetwork installer to prevent its installation on unsupported operating systems. To work around the problem, please try to install IxNetwork 6.0 EA by executing C:\Program Files (x86)\IxiaInstallerCache\IxNetwork\6.0.400.14\setup.exe file.
8
IxNetwork FAQ
14. Installing IxOS on Windows 2003 Server Terminal Service gets a few unexpected dialogue boxes
Description
The user sees one or two popped up box during the installation. The message reads something like this, ‘When the installation has ended (successfully or not), please click the Finish button to the Cancel button. DO NOT CLICK THE BUTTONS BEFORE INSTALLATION HAS ENDED!’
Resolution
This happens when the server is not in the "installation mode" with Terminal Service on Windows 2003 server. In order to avoid this nuisance, you have to open a command shell, disable logins and put the server into installation mode. More details can be found at
http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.terminal_services/2006- 11/msg00440.htmlLicensing
15. IxNetwork 5.40 installation failed...why?
Description
Recently one of our SE ran into a problem with IxNetwork 5.40 installation. While running the installer, it was failing with error 1721
SE first tried to install IxNetwork + Test Conductor package. He was running into some problem with IxNetwork, so he tried to 'repair' the IxNetwork at this point he was getting these errors (see snapshot). After troubleshooting we learned that IxNetwork + TC and IxNetwork standalone installer they both are separate. In this case, for some reason IxNetwork installer got confused with IxN +TC installer, hence it generated error.
Resolution
According to engineering DO NOT try to run install IxN +TC and IxN installer on a same client PC. You may run into unexpected error.
16. IxNetwork 5.30 EA SP5 compatibility issue with the IxOS 5.20 GA P2
Description
While installing IxNetwork 5.30 SP5 with IxOS 5.20 GA P2, an error will be displayed complaining that a non-compatible version of IxOS is installed even though you have IxOS5.20 GA P2 installed and it is compatible per release notes and compatibility matrix.
Resolution
Unfortunately there have been two versions of IxNetwork 5.30 EA SP5 installer package released. The first package (without -a) has a bad version checker and erroneously fails assuming it is not compatible with 5.20 GA P2.It is likely that you are using the bad installer. The issue was corrected
9
IxNetwork FAQ in 5.30 EA SP5a installer package. The ‘a’ version of installer package is the only one available to be downloaded from the website.
17. I have been trying to upgrade the IxNetwork software on the XM12 chassis this morning and it keeps hanging at the installation window. The window that says ‘this may take a few minutes’ has a status bar. I waited 45 mins and the status bar never change so I killed the process and attempted to back out the install. Now I am trying to re-install the software and it appears to be hung again.
Resolution
This was caused by a previous stalled installation instance. Open task manager and end the msiexec.exe process (es) that are owned by the user. Do not end the one owned by ‘system’.
Another possibility was system security policy is preventing a successful installation. This could be either be managed by system security MMC or other software such as McAfee or Symantec. The best practice is advice customers to check with their IT department.
18. Install IxNetwork Help files along with IxNetwork.
Resolution
1. Double-click the IxNetwork.exe file from the Installation CD. 2. Follow the instructions to automatically install IxNetwork Help files along with IxNetwork on Windows Client. NOTE: Refer to the video AIM-Defining the IxNetwork document structure.mcmovie and Getting_Started_with_IxNetwork.mcmovie for further information.
19. Installation limitation of IxNetwork in Windows 2003 with non-English locales
Description
During installation of IxNetwork 6.20 EA and above builds on Windows 2003, the installation may exit with a prompt, 'The OS is Microsoft Windows Server 2003r2 and the locale is 00000804. IxNetwork cannot be installed on windows 2003 having locale other than English (United State).'
There is a check added in IxNetwork installer to prevent installation on windows 2003 having locale other than English (United State). This check is added to prevent IxNetwork crash on such platforms.
Resolution
To resolve the issue, follow the steps given below:
1. Click Control Panel 2. Click on Regional and Language Options. 3. Set the Language for non-Unicode programs to English (United States) 10
IxNetwork FAQ
20. While installing IxNetwork, new reporter (ReportDesigner.msi) might fail to install with an error “Error 1920.Service xNetwork.Reporting (IxNetwork.Reporting) failed to start
Description
While installing IxNetwork, new reporter (ReportDesigner.msi) might fail to install with an error “Error 1920.Service IxNetwork.Reporting (IxNetwork.Reporting) failed to start. Verify that you have sufficient privileges to start system services.” The issue may be caused because Dot Net 3.5 SP1 was installed but there were several other .Net compact versions that may also have been installed on the machine that may be creating conflicts on the machine.
Resolution
Uninstall all .Net versions from the machine and then install .Net 3.5 SP1.
21. Error 27506 when installing Aptixia Application (Sql Error)
Resolution
After un-installing the application, there is no need to change the registry keys. If you have other Applications installed, do not remove all folders. Only rename C:/program files/ixia/
22. Installation error of SQL 2008 while installing IxNetwork
Description
During installation of a Ixia product SQL 2008 installation may fail with an error in the log 'Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC. Access is denied'. This error is seen when the user account is lacking some of the privileges mentioned below.
Local Policy Object Display Name User Right Backup files and directories SeBackupPrivilege Debug Programs SeDebugPrivilege Manage auditing and security log SeSecurityPrivilege
Resolution
Follow the steps to add rights as a local administrator account: 1. Log on to the computer as a user who has administrative credentials. 2. Click Start, and then click Run. 3. Type Control admintools, and then click OK. 4. Double-click Local Security Policy.
11
IxNetwork FAQ
5. In the Local Security Settings dialog box, click Local Policies, double-click User Rights Assignment, and then double-click Backup Files and Directories. 6. In the Backup Files and Directories Properties dialog box, click Add User or Group. 7. In the Select User or Groups dialog box type the user account being used for setup, and then click OK two times. 8. Repeat the procedure for the other two policies mentioned in the Cause section 9. On the File menu, click Exit to close the Local Security Settings dialog box. 10. Restart the installation of Ixia product to install SQL 2008 NOTE: For more information, please refer http://support.microsoft.com/kb/2000257
Another cause of this issue could be that the computer name and the user name are the same. In this case to resolve this issue, create another user with administrator rights and install under it.
12
IxNetwork FAQ
Licensing
The licensing related questions are as follows:
1. I have been trying to upgrade the IxNetwork software on the XM12 chassis this morning and it keeps hanging at the installation window. The window that says ‘this may take a few minute’ and has a status bar. I waited 45 mins and the status bar never change so I killed the process and attempted to back out the install. Now I am trying to re-install the software and it appears to be hung again. 2. Centralizing licenses for IxNetwork is not supported 3. Licensing issue with an error message, 'No IxNetwork base software found on 192.168.187.73'.
1. I have been trying to upgrade the IxNetwork software on the XM12 chassis this morning and it keeps hanging at the installation window. The window that says ‘this may take a few minute’ and has a status bar. I waited 45 mins and the status bar never change so I killed the process and attempted to back out the install. Now I am trying to re-install the software and it appears to be hung again.
Resolution
This was caused by a previous stalled installation instance. Open task manager and end the msiexec.exe process (es) that are owned by the user. Do not end the one owned by system”.
Another possibility was system security policy is preventing a successful installation. This could be either be managed by system security MMC or other software such as McAfee or Symantec. The best practice is advice customers to check with their IT department.
2. Centralizing licenses for IxNetwork is not supported
Resolution
The IxNetwork GUI has an option to specify to look for license on a central license server. This is not supported as of IxNetwork 5.30 SP5.The License location dialogue, invoked by Help/Licensing menu, showed that we can run licensing server on another server other than the chassis. The release note has the same information.
However, this information is misleading. It is NOT supported. Bug 505781 has submitted to request the removal of the option.
13
IxNetwork FAQ 3. Licensing issue with an error message, 'No IxNetwork base software found on 192.168.187.73'.
Resolution
Refer to the attached document for details.
Licensing Issue in IxNetwork.doc
Procedure
The procedure related questions are as follows:
1. Centralizing licenses for IxNetwork is not supported 2. How to configure machine authentication with 802.1x? 3. IxNetwork 5.40 -- How to use BGP Route import function 4. Why IxNetwork can't advertise more than 30-35K ISIS v4 or v6 routes? 5. Configuring IP in IP Traffic using IxNetwork 6. Diagnostic Log collection in IxNetwork 7. Configuring multicast on IxNetwork 8. Capturing packets in IxNetwork 9. Restoring IxNetwork configuration on different chassis
1. Centralizing licenses for IxNetwork is not supported
Resolution
The IxNetwork GUI has an option to specify to look for license on a central license server. This is not supported as of IxNetwork 5.30 SP5.
The License location dialogue, invoked by Help/Licensing menu, showed that we can run licensing server on another server other than the chassis. The release note has the same information.
However, this information is misleading. It is NOT supported. Bug 505781 has submitted to request the removal of the option.
2. How to config machine authentication with 802.1x?
Resolution
How to configure machine authentication with 802.1x?
14
IxNetwork FAQ
To make Machine Authentication work, you must manually add the host and user to be authenticated to Windows Active Directory. You can use either of two methods:
1. Active Directory's Administrative Interface 2. The ADSI_GUI.exe tool provided with IxLoad
If you choose to use the Active Directory interface to add the host and user, you will still have to use the ADSI_GUI.exe tool to set the password, because the Active Directory Administrative Interface does not allow you to set the password.
Note:
1. You must use the ADSI_GUI.exe tool on a PC that is using either Windows 2000 or Windows 2003 Server; otherwise it may not set the password. 2. Active Directory Server must have NTLMv1 enabled, as the tool uses this protocol to create accounts and to set passwords. 3. The host and user IDs must be in the following formats:
Host ID
User ID
3. IxNetwork 5.40 -- How to use BGP Route import function
Resolution
Attached PDF file demonstrates how to use BGP route import function available in IxNetwork 5.40.
BGProuteImportSETr aining.pdf
4. Why IxNetwork can't advertise more than 30-35K ISIS v4 or v6 routes?
Resolution
The limitation stems from the fact that LSP fragment id is a 8 bit field which means that there can be max 255 LSPs originated by a single node. So depending on type of routes being advertised + other data , the maximum number of routes which can be sent by one emulated ISIS routers varies from 30-35K . Please use Network Range or multiple routers to achieve your objective.
Also note that there is a way to get a single ISIS router to transmit up to 190,000 routes which is using Jumbo Frame feature without Wide Metric and TE enabled:
15
IxNetwork FAQ
1. Set Interface MTU to maximum possible of 9126 2. Set ISIS Router -> Advanced -> Max LSP Size to 9118 (need it to be little lesser than MTU to accommodate the header) Now RR can be set to upto 190,000 and all routes will get flooded to DUT. Of course, DUT MTU also needs to be set to matching MTU and DUT should support ISIS jumbo frame
5. Configuring IP in IP Traffic using IxNetwork
Resolution
Refer to the attached document for further details.
IP in IP Traffic Configuration Using IxNetwork.pdf
6. Diagnostic Log collection in IxNetwork
Resolution
Refer to the attached document for further details.
IxNetDiaglogs Documentation.doc
7. Configuring multicast on IxNetwork
Resolution
Refer to the attached document for further details.
IxNetwork_Mulicast. docx
8. Capturing packets in IxNetwork
Resolution
Refer to the attached document for further details.
Support_Documentat ion_ Packet capture in IxNetwork.doc
16
IxNetwork FAQ
9. Restoring IxNetwork configuration on different chassis
Resolution
Refer to the attached document for further details.
Support_Documentat ion_ Restoring configurations in IxNetwork.doc
Version Compatibility
The version compatibility related questions are as follows:
1. How to configure Microsoft IAS 2003 to work with 802.1x in IxNetwork or IxLoad? 2. IxNetwork 5.30 EA SP5 compatibility issue with the IxOS 5.20 GA P2 3. IxOS 5.30 GA build 30 compatibility issue
1. How to configure Microsoft IAS 2003 to work with 802.1x in IxNetwork or ixLoad?
Resolution:
The resolution is available in the following section:
Testing 802.1x protocol with IAS 2003 Server
Describe the steps required for testing 802.1x protocol from IxAuthenticate, IxNetwork and IxLoad product lines. This document is only for Microsoft IAS Server 2003.
I. Configure Active Directory for accounts and groups. II. Add Users and Machines III. Obtain certificates IV. Convert certificates V. Additional checks
1. Configure Active Directory for accounts and groups. This implies the following three steps:
Modify Domain Password policies
17
IxNetwork FAQ
Make sure you permit NTLM connection to the ActiveDirectory Controller PC.
18
IxNetwork FAQ
Close “Group Policy Object Editor” window, Select Apply from “yourdomain.com Properties” window and then click OK from same window. Enforce the new rules by opening a command prompt and type: gpupdate /force.
DH: In order to add MD5 or PEAP authentication for the remote access users, right click “Connections to other access servers” from IAS management control, “Remote Access Policies” branch. Choose properties. Click “Edit Profile…” Please watch video “IAS-remote-access-config-forEAP.avi” for further configuration details.
2. Add Users and Machines (Computers)
Locate ADSI_GUI.exe and start it. This utility is installed in same place where the client side of the application resides. Just perform a search for it, as the location might be different across Ixia application. This application must be run from a different computer than the ActiveDirectoryController. For users, choose between these formats for name: username or [email protected] . For computers, choose between computername$ and computername.domain.com .For the FQDN of computer format, you must use latest version of IxNetwork/IxLoad. Use passwords that are at least 4 in length as a recommendation. Remember that these passwords will be tied to the account and also will be used for protecting associated certificates (where applicable).
Davidh: After the user is created, make sure the user has remote access allow. This is configured in AD. Alternatively, create another “Remote Access Policies” in IAS so that “allow dial-in” access is not required.
3. Obtain certificates
3.1 Obtain the Self signed certificate of the Certificate Authority (CA). Save it in base64 format, and name it root.pem. You need to put this root.pem file on the client pc, where application resides. Default value for the folder where certificates are stored is C:\Program Files\ixia\authfiles on client pc.
19
IxNetwork FAQ
3.2 Requirements for certificates are explained here: http://support.microsoft.com/kb/814394 Client certificates are required to include:
- SubjectAlternativeName extension in the certificate contains the user principal name (UPN) of the user. - The user or the computer certificate on the client includes the “Client Authentication” or/and “Server Authentication” purpose (EKU 1.3.6.1.5.5.7.3.2; 1.3.6.1.5.5.7.3.1).
Computer certificates are required to include: - SubjectAlternativeName extension in the certificate contains the FQDN of computer.
- The user or the computer certificate on the client includes the “Client Authentication” or/and “Server Authentication” purpose (EKU 1.3.6.1.5.5.7.3.2; 1.3.6.1.5.5.7.3.1). Obtaining certificates is a manual process and depends on the type of the CA (stand alone vs. enterprise) and on the OS version (normal vs. enterprise Server 2003)
First, execute these commands on the CA machine: Run the following commands to allow the Certificate Authority to issue Alternate Names.
1. certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2 2. net stop certsvc 3. net start certsvc
Case: 20
IxNetwork FAQ
1. If you have a 2003 Stand Alone CA:
a. Go to the Web Page of the CA: http://localhost/certsrv b. Chose "Request certificate" c. Choose "submit an advanced certificate request" d. Choose "Create and submit a request to this CA" e. Enter the Enter the name of the client/computer in the Name Field f. Chose Other in the Certificate Request Type g. Enter the OID 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2 h. Chose Microsoft RSA Schannel CSP i. Check "Mark keys as exportable" j. Check "Store certificate in the local computer certificate store" k. Enter the following in Attributes: l. For user account (what follows DNS= must be identical to the name set in the CN field) {DavidH: This might be incorrect. Please see text in red the previous page. The User Principal Name(UPN) is critical in user’s certificate.) SAN:DNS=USERNAME or SAN:[email protected] For computer account: SAN:DNS=FQDN OF THE COMPUTER or SAN:DNS=computername$
m. Enter a Friendly Name of certificate n. Click "Submit"
21
IxNetwork FAQ
22
IxNetwork FAQ
4. If you have a 2003 Enterprise Edition, Enterprise CA:
Notice the addition of Certificate Templates folder, for an Enterprise CA.
a. Create a Duplicate of the Computer template. b. Select the "Supply in request" option under the Subject Name tab. c. Select the "Allow private key to be exported" option under the Request Handling tab. d. Publish the new template. e. Request the certificate on the CA pc by going to the Web Page of the CA: http://localhost/certsrv f. Chose request certificate. g. Choose "submit an advanced certificate request". h. Choose "Create and submit a request to this CA". i. Select the template you just created and published. j. Enter the name of the client/computer in the Name Field k. Check "Mark keys as exportable" l. Check "Store certificate in the local computer certificate store" m. Enter the following in Attributes: n. For user account (what follows DNS= must be identical to the name set in the CN field) SAN:DNS=USERNAME or SAN:[email protected] For computer account: SAN:DNS=FQDN OF THE COMPUTER or SAN:DNS=computername$
o. Enter a Friendly Name of certificate. p. Click "Submit".
23
IxNetwork FAQ
DavidH: Note: Working with a customer, we were able to generate a correct certificate by going to http://localhost/certsrv. When prompted for user name and password, enter the user name and password that was configured in AD. Select the client certificate template. In the name field, enter the same user name that is configured in IxNetwork GUI. This will generate the certificate with UPN=username.
Certificates will be placed on the CA computer, in the Computer Certificate Store. Open it by Run->mmc- >File->Add/Remove Snap-in->Add->Certificates->Computer Account->Next->Finish.
From the Personal->Certificates select the certificates for users/computers and export them. Choose to Export the private key:
24
IxNetwork FAQ
And make sure next page looks like this:
Type the password for this pfx container (it should match the password that you set for the account through ADSI_GUI utility) and then select where to be saved.
Tip for naming the saved containers: for [email protected], save like this: [email protected].
The files obtained are password protected .pfx files that must be converted in an Ixia suitable format( base 64).
4. Converting certificates
Use OpenSSL to convert .pfx to .pem files. Ixia uses .pem suffix to designate base64 encoded files and .cer to designate binary encoded files.
If you have a user named [email protected] , the corresponding pfx file is [email protected]. Open ssl pkcs12 –in [email protected] –out [email protected].
You should use for all the password prompts the same value, the one that you used when you configured accounts in ActiveDirectory through ADSI_GUI Ixia tool. Pay attention to the name of the file, as it must match the name of the client/machine in the application GUI.
25
IxNetwork FAQ
For machines:
machine1$.pfx -> machine1$.pem machine1.ixiacom.com.pfx -> machine1.ixiacom.com.pem
IMPORTANT: The password to encrypt the private key is the same configured in the GUI. You can also use “-nodes” option as well.
5. Additional checks
5.1 Always ensure that the passwords are set correctly on ActiveDirectory. Use a MD5 test for this, instead TLS or PEAP-MsChapv2.
5.2 Always make sure that time on the chassis is correct. It must be same clock across all the machines involved in test, otherwise, checks for certificates might fail (certificates are invalid due to time being skewed).
5.3 Remember that Ixia uses .pem suffix to designate base64 encoded files and .cer to designate binary encoded files. A base64 encoding can be recognized by the presence of such strings in the file:
-----BEGIN RSA PRIVATE KEY-----
/vO6KTi7GnTO1eCrxvO8rqFLhrn65tfxIQLHsdhApRIXvusOghc+wtfjIdYTndQ2
ydunkjMTwXHLgiaRMRqHuKW6YXJ1xyz2kuAyT/WnEmhjZOZj1/Q40COrUI1DXcl1
JDgI6rnSIx7/rAIE9AxFJXHTBOdCmP+uEbTvDWjDs1X/rTagcRwJ6Fn4LkVTI6GK
fKWeW/zq7gtYKdkIUi/6CflEqoG7HT89Sd9TXVQuKj9uqsIpCiGPzqes147ZB9az aJLvMaGIUOEXW10JlvSUWcgc2TiHl8jgmwexOPmXzMS3SU86e1q+YOSVhRX7Hw9k
6. Machine authentication Key points to make this work.
Two authentication format 1. Use machine auth prefix “host/”
26
IxNetwork FAQ
The certificate name should be machne.pem.
2. Use $ style Machine auth prefix is null.
27
IxNetwork FAQ
The machine name should have a $ at the end.
28
IxNetwork FAQ
The certificate name should be machine$.pem.
7. Miscellaneous tricks (DH)
***For windows to display .pem certificate content, open the pem file with wordpad and delete everything until “ ------END OF RSA PRIVATE KEY ------“. Save the file with .cer extension. Now you can double click to display its content in Windows.
*** DH: IF “Send CA Certificate Only” is NOT checked for PEAP0. You have to have client certificates and private keys. If this is the case MSCEP is strongly suggested.
For example, the certificate has a UPN of [email protected]. I have to name the certificate [email protected]. The user name in IxNetwork was also configured as [email protected]. Enterprise CA is used.
*** DH: Important, use PEAPv0 for IAS. Use PEAPv1 for ACS.
2. IxNetwork 5.30 EA SP5 compatibility issue with the IxOS 5.20 GA P2
Resolution:
While installing IxNetwork 5.30 SP5 with IxOS 5.20 GA P2, an error will be displayed complaining that a non-compatible version of IxOS is installed even though you have IxOS5.20 GA P2 installed and it is compatible per release notes and compatibility matrix. Unfortunately there have been two versions of IxNetwork 5.30 EA SP5 installer package released .The first package (without -a) has a bad version checker and erroneously fails assuming it is not compatible with 5.20 GA P2.It is likely that you are using the bad installer . The issue was corrected in 5.30 EA SP5a installer package. The “a” version of installer package is the only one available to be downloaded from the website.
29
IxNetwork FAQ 3. IxOS 5.30 GA build 30 compatibility issue
Resolution:
IxOS 5.30 GA build 30 has compatibility issue with other application and prevent the installer to install other applications in the chassis.
This issue reported when the customer was trying to install the IxNetwork 5.30 GA in the chassis with the IxOS 5.30GA build 30. The error message says: "Incompatible IxOS version. Please install IxOS 5.30 GA9or later 5.30 version) or IxOS 5.50 EA SP1 (or later 5.50 version). Dependencies checking failed (see log file)! Installation aborted."
After this error the installation will be terminated.
Install the IxOS 5.30GA build 31.
Definition
The following are the definitions of difficult terms:
1. IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT) 2. High-level comparison between IxTclNetwork and IxTclProtocol APIs for IxNetwork and IxNetwork-FT
1. IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT)
Definition:
IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT)
PTP time is relative to the time when timestamps were cleared. There is no automatic conversion from PTP time to UTC.
GPS is not used in PTP protocol. With two chassis, either they are connected as Master slave, where GPS is not required. If the two chassis are both master, then GPS would be needed. Regardless GPS is NOT used by PTP protocol. GPS would be used to synchronize ports on two chassis for timestamps, start transmit...etc.
2. High-level comparison between IxTclNetwork and IxTclProtocol APIs for IxNetwork and IxNetwork-FT
Definition:
The topic of automation with IxNetwork's products is pretty straightforward when you look at the IxNetwork product offering as two distinct (but similar) applications: IxNetwork and IxNetwork-FT. Here is a summary of the high-level differences between the two applications:
30
IxNetwork FAQ
IxNetwork - this is the classic IxNetwork GUI (uses .ixncfg) - foundation for all new development of protocols (future roadmap, not necessarily to be included in IxNetwork-FT) - all IxAccess/IxAuthenticate functions (Auth/Access Hosts/DCB) integrated into IxNetwork (not available via IxNetwork-FT) - automation based on IxTclNetwork API - different client requirements (e.g. IxNetwork Tcl Server not on chassis) and approach than IxNetwork-FT automation - automation documentation can be found in "IxNetwork Tcl API Guide" (filename called DataModelAPI.pdf)
IxNetwork-FT - this is the replacement to IxRouter, which is integrated into IxExplorer - functional testing based - does not scale as well (esp. from a traffic perspective) - NOTE: non-CPU modules will not have same functionality as previous IxRouter releases (protocol emulation support not included) - automation based on legacy IxTclProtocol API - integrated with IxTclHal and fully backwards compatible with previous releases - automation documentation can be found in "IxNetwork Tcl Development Guide (Legacy API)"
General Statements - both applications and API packages are included in the IxNetwork installation - IxNetwork-FT has to be included as an install option for the IxTclProtocol API to be installed - concurrent usage of the APIs are supported on the same client/chassis, however not on the same port- existing IxTclProtocol scripts do not have to be converted to IxTclNetwork tests (IxTclProtocol scripts will run as is with no modifications) - there is no conversion method available (test approach and libraries are completely different).
31
IxNetwork FAQ Troubleshooting
The troubleshooting related questions are listed below:
1. How can I start IxNetwork Tcl Server for multiple accounts on Windows startup? 2. IxNetwork : User can create but not enable more than 100 protocol interfaces 3. The card is a reduced feature set card. For Example - LSM1000XMVR16-01 type cards can only do 100 protocol interfaces per port. 4. IxNetwork 5.40 -- StatViewer doesn't support endpoint filtering using wild card character 5. SQL server service failed to start 6. IxExplorer shows multiple IxNetwork-FT icons in menu bar 7. IxNetwork -- What happens when you hit 'Clear statistics' button in StatViewer? 8. IxNetwork 5.30 -- Traffic Wizard doesn't show all PPPoEv6 sessions...why? 9. IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT) 10. How to config MS 2008 CA server to work with IxVPN/IxLoad/IxNetwork 11. IxNetwork - PPP or L2TP traffic does not go thru the DUT if the frame size is set to anything other than Fixed 12. Ixia PIM router not sending correct upstream neighbor's router IP address 13. IxN2X Fusion system switch requirement 14. How can I start IxNetwork Tcl Server for multiple accounts on Windows startup? 15. Client PC Memory and Performance monitoring utility 16. Restarting HW Manager doesn't fix the IxNetwork client failing to connect to IxNetwork server processes on the chassis 17. In IxNetwork, Increment By is disabled 18. Ixia Application selector fails to open on the chassis 19. In IxNetwork, Clear Statistics button in the Home ribbon does not clear protocol statistics 20. Unable to establish chassis connection from IxNetwork client even though we can ping chassis from client 21. Cannot connect to chassis 22. Location of recovered files and logs in IxNetwork after a crash 23. In the event of a crash, storage of recovered files in IxNetwork
1. How can I start IxNetwork Tcl Server for multiple accounts on Windows startup?
Resolution
In order to run multiple instances of IxNetwork Tcl Server in the same desktop session, IxNetwork must run as separate users. There is an option to "Run as separate user..." in the right-click dialog of the shortcut. However this cannot be automated at user login.
32
IxNetwork FAQ
One option is to use a freely available utility called psexec, provided by Microsoft - http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx. A good reference can be found at http://ss64.com/nt/psexec.html.
2. IxNetwork: User can create but not enable more than 100 protocol interfaces
Resolution
This behavior can be caused by a couple of conditions
3. The card is a reduced feature set card. For Example - LSM1000XMVR16- 01 type cards can only do 100 protocol interfaces per port.
The user does not have unique mac addresses for the additional protocol interfaces they are trying to enable. The can occur at more or less than 100 protocol interfaces on a standard card.
4. IxNetwork 5.40 -- StatViewer doesn't support endpoint filtering using wild card character
Resolution
If user try to filter endpoint stats using wild card character the GUI crash will occur. According to engineering we don't support wild card character; however they agree that the GUI should not crash. This will be addressed in IxNetwork 5.40 SP1 build.
5. SQL server service failed to start
Resolution
The error shows during IxNetwork installation. When it reaches the point to install SQL Server Database Services it will error out and stop the installation. If you try to start the service manually it will also fail. This error will follow by another Error "Microsoft SQL Server Express 2005 SP2 setup failed"! The system cannot find the file specified.
6. IxExplorer shows multiple IxNetwork-FT icons in menu bar
Resolution
This issue is caused by corrupt registry settings. To resolve, follow these instructions:
1. Close IxExplorer 2. Start/Run/regedit 3. Go to HKEY_CURRENT_USER/Software/Ixia Communications 4. Export IxExplorer registry tree 5. Delete IxExplorer registry tree 6. Restart IxExplorer 33
IxNetwork FAQ
Once IxExplorer has restarted, the icons should be back to normal.
7. IxNetwork -- What happens when you hit 'Clear statistics' button in StatViewer?
Resolution
Few customers have enquired about the 'Clear Stats' button. While running the traffic, customers have seen initial packet loss or high latency due to the packet learning. So to get clean results, customer clicked the 'Clear Stats' button but they noticed strange results, instead of getting rid of high latency numbers or packet loss, they saw packet loss and high latency # again. Later we found from engineering that when user hit 'Clear stats' button the traffic engine briefly stops transmitting traffic and then restart the traffic. Some DUTs can't handle the initial burstiness (traffic sent by Ixia) and that resulted in such behavior. If we use IxExplorer then this problem doesn't occur. We have advised engineering to change this behavior, clear stats should not stop the transmit engine it should rather just clear the counters.
Engineering is planning to fix this in 5.60 version.
8. IxNetwork 5.30 -- Traffic Wizard doesn't show all PPPoEv6 sessions...why?
Resolution
We have seen an issue with IxNetwork 5.30 release with PPPoEv6 sessions. After all 4000 PPPoEv6 came up when customer tried to create up/down stream traffic the traffic wizard was showing only 1000 sessions (instead of showing all 4000).
This issue is fixed in the 5.40 release. The following explanation will help to understand the issue.
IPv6CP, the PPP protocol, only negotiates interface identifiers, so it requires a separate mechanism in order to also fetch prefix information (since the interface identifier supplies the 64 bits at the end, you need a prefix for the first 64 in order to make a full address). Our implementation in both IxNetwork 5.30 and 5.40 uses stateless auto-configuration (RFC2462) for this. In 5.30 we would declare sessions as negotiated after negotiating IPv6CP, which is too early – at this point we only have a link-local IPv6 address, not usable for traffic; also, we’ve seen significant lags between our router solicitations and the DUT’s router advertisements with Cisco routers, so it’s likely that after all sessions have negotiated IPv6CP there’s quite a few waiting for router advertisements. Also, sending of router solicitations wasn’t governed by the max outstanding / setup rate mechanism, since we’d consider those sessions negotiated – maybe that was also stressing the DUT.
In IxNetwork 5.40 we’ve solved this problem by only declaring sessions negotiated after the first valid router advertisement (carrying a valid prefix) comes. So the original problem shouldn’t happen – you should always see the same number of sessions in traffic wizard as the number reported beforehand. Now, the IPv6 stateless auto-configuration per-session stat was a suggestion so Cisco could get measurements of the latencies that their DUT exhibits. Our QA uses Cisco for testing PPP / L2TP with IPv6 and have always seen big delays for router advertisements. In the beginning we were using a timer of 10 seconds, but even that wasn’t enough – now it’s 30 seconds. If we expose those numbers it would be easier to prove them that the latencies are significant, and maybe help them with profiling.
34
IxNetwork FAQ
9. IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT)
Resolution
IxOS/IxNetwork: how to calculate PTP time to UTC time (PST, day light saving time, Tijuana or GMT) PTP time is relative to the time when timestamps were cleared. There is no automatic conversion from PTP time to UTC.
GPS is not used in PTP protocol.
With two chassis, either they are connected as Master slave, where GPS is not required. If the two chassis are both master, then GPS would be needed. Regardless GPS is NOT used by PTP protocol. GPS would be used to synchronize ports on two chassis for timestamps, start transmit...etc.
10. How to configure MS 2008 CA server to work with IxVPN/IxLoad/IxNetwork
Resolution
To configure MS 2008 CA server to work with IxVPN/IxLoad/IxNetwork with standalone CA server installation, go to regedit, and then click HKEY_LOCAL_MACHINE>software>Microsoft>Cryptogrophy>MSCEP>enforcepassword, change the value to 0.
Make sure to reboot the CA server.
11. IxNetwork - PPP or L2TP traffic does not go thru the DUT if the frame size is set to anything other than Fixed
Resolution
In IxNetwork 5.30 SP5, PPP and L2TP traffic for ipv4/ ipv6 only works if the frame size is set to Fixed. Random, Increment, IMIX, Weight Pairs, Quad Gaussian and Auto Frame Size will not work. In IxAccess, this used to work.
In IxNetwork 5.30 SP5 & GA: only fixed frame sizes are supported for traffic on PPP/L2TP endpoints with IPCPv4/v6 over Eth/ATM.
There is feature request FEA480013 for this in IxOS 5.60.
The basic problem is this: IxOS is not aware of the PPP protocol and has no idea that it needs to insert a length into the packet. In IxAccess, the data inside PPP was essentially static and IxAccess took care of any changes to packets required. In IxNetwork, full instrumentation is added (inserted into the payload) and there is reliance on IxOS to be able to generate and parse “real” PPP frames. From an IxOS perspective this is a new feature (and not a trivial feature).
35
IxNetwork FAQ 12. Ixia PIM router not sending correct upstream neighbor's router IP address
Resolution
Ixia PIM router not sending correct upstream neighbor's router IP address
Customers seeing Ixia PIM router do not send the right upstream neighbor's IP address. By checking the configuration, they have to verify that the "auto pick neighbor" parameter is enabled. This should be enabled by default. If enabled, the Upstream Neighbor address used in the Join/Prune message is determined automatically from received Hello messages. The first time a Hello message is received – containing a Source (linklocal) address that does not belong to this interface, that source address will be used as the Upstream Neighbor address. If unchecked, the user can type in the linklocal address in the Upstream Neighbor IP field – to be used for the upstream neighbor address field in the Join/Prune message.so you can disable this option and put the right IP address in the neighbor IP filed.
13. IxN2X Fusion system switch requirement
Resolution
Add Fusion ports fails - need to use Ixia certified system switch
Some models of switches do no perform adequately with multicast packet forwarding leading to packet loss and failures during N2X port selection. As a result we will only support switches that have been specifically qualified by QA.
We have fully qualified the following switches:
SMC SMC8508T (8-port) SMC SMCGS24 (24-port) Cisco SD2008 (8-port) Cisco SD2008T (8-port) Cisco SG 100D-08 (8-port)
The SMC switches are the units we sell as PN: 971-0403 (24-port) and PN: 971-0402 (8-port).
Any other models are not supported, and may lead to intermittent failures. For example, we have confirmed that the following switches do not work reliably with IxN2X and will lead to intermittent port selection failures due to dropped multicast packets:
Netgear JGS524NA (24-port) Cisco SR2024C (24-port)
36
IxNetwork FAQ
14. How can I start IxNetwork Tcl Server for multiple accounts on Windows startup?
Description
In order to run multiple instances of IxNetwork Tcl Server in the same desktop session, IxNetwork must run as separate users. There is an option to ‘Run as separate user...’ in the right-click dialog of the shortcut; however this cannot be automated at user login.
Resolution
One option is to use a freely available utility called psexec, provided by Microsoft - http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx. A good reference can be found at http://ss64.com/nt/psexec.html.
Examples batch files using the utility are attached. These examples worked in a Windows 2003 environment.
8020.renamebat (Example using psexec to launch on port 8020)
ixnet_run.renamebat (Main batch file - to be included in startup folder)
8021.renamebat (Example using psexec to launch on port 8021)
15. Client PC Memory and Performance monitoring utility
Resolution
Please use attached utility to monitor client PC's memory and performance. This utility will help to troubleshoot OOM issues we have seen with client PC.
Util.zip (Memory Monitoring utility)
16. Restarting HW Manager doesn't fix the IxNetwork client failing to connect to IxNetwork server processes on the chassis
Resolution
The IxNetwork client fails to connect to the IxNetwork server processes on the chassis – and just restarting Hardware Manager wasn’t enough to clear up the problem.
The symptoms are as follows…
1. In the Port Selector screen, we can see that IxNetwork keeps retrying but continually fails. In the above cases, we noticed that… 2. IxExplorer can connect from the remote client, but not IxNetwork. 3. IxOS, IxNetwork, and IxProtocol versions all matched between client and server.
37
IxNetwork FAQ
4. No failure messages or core dumps in the IxServer log. 5. Restarting IxServer did not fix the issue. Normally, restarting the IxiaHardwareManager service on the chassis is enough to clear this up, but, in these particular cases, restarting HW Mgr wasn’t enough. We also had to restart the Ixia Proxy Server, and the Ixia Service Manager processes (in addition to the IxiaHardwareManager process). After restarting those three processes the IxNetwork client could connect.
For those of you unfamiliar with Windows internals, go to the chassis’ Windows “Start” icon select “Settings” “Control Panel” “Administrative Tools” “Services”. Then look for the Ixia services that are running for that particular version of IxOS software. Right click on the IxiaHardwareManager, Ixia Proxy Server, and the Ixia Service Manager services (highlighted in red, below) and select “restart” for each of them. They do not need to be restarted in any particular order.
Another symptom you may see (if you dig into the logs), is that the hwmgr.log file will display the following error message (highlighted in yellow) indicating that it is having a problem connecting to the Proxy Server process. (The hwmgr.log file can be found in the C:\Program Files\Ixia\IxOS\
2012-05-14 10:17:27,703[WARN]: 0878: CHID: DeleteChassis: Chassis 10.193.183.51 is not in the map. 2012-05-14 10:17:27,703[DEBUG]: 0878: CHID: Current ChainedChassisInfo map: 2012-05-14 10:17:27,703[DEBUG]: 0878: CHID: Current sequence id cache: 2012-05-14 10:17:27,703[DEBUG]: 0878: testAddChassis: add failed 2012-05-14 10:17:27,703[DEBUG]: 0878: testAddChassis failed 2012-05-14 10:17:27,703[ERROR]: 0d78: statusid Aptixia.NetManagerProxy.IxServerDown 2012-05-14 10:17:27,703[DEBUG]: 0d78: exception #### 2012-05-14 10:17:27,703[DEBUG]: 0878: Calling testAddChassis for chassis , master chassis localhost 2012-05-14 10:17:27,703[DEBUG]: 0878: deleteAllChassis
17. In IxNetwork, Increment By is disabled
Description
In an IxNetwork MME/eNB S11/S1-U wireless configuration, the "Increment By" grid operation is disabled if you have a validation error in the first range. For example, if you have multiple User Equipement ranges and you change the Count value (on the Basic tab) to 20 for all of them, the validation for the IMSI, IMEI, and MSISDN fields on the Identification tab fails. At this point, you cannot use the grid operations to correct the values for those three columns.
Resolution
IxNetwork will not re-enable the grid operation until you resolve the validation error in the first range, for each of the parameters. Rather than changing each value manually, use the following work- around:
1. Change the IMSI, IMEI, and MSISDN values in the first range such that the values are valid. For exmaple, change IMSI to 206041000000001 (from the default value of 226041000000001) to clear the validation error in that cell. 2. For each these columns use the Increment By grid operation to create valid values for the entire column. These will be temporary values.
38
IxNetwork FAQ
3. Set the desired values in the first range, and then use the Increment By operation to create the desired values for the entire column. For example, you can now restore the IMSI value to 226041000000001 in the first range and then increment the values in the column by 20.
18. Ixia Application selector fails to open on the chassis
Description
Each time when trying to start Ixia Application selector, it fails to open and points me to the app_selector.exe.log
Versions installed on the chassis: IxOS 6.10 SP2 Patch 1/IxN 6.10 EA / IxLoad 5.30 EA. I did reinstall the Ixia application selector, renamed the folder installation but without any luck.
Resolution
Provided private fix - new appinfo_StatenginePCPU.xml copied in the data folder of the AppInfo install path, e.g.: C:\Program Files\Ixia\AppInfo\data
This is almost certainly a duplicate of a bug fixed recently, related to a machines that have bogus/broken registry entries. (app_selector sees the entry and tries to decode dependencies for a package that is not fully multiversion, which causes problems. It is unclear how the machines get the broken registry entry in the first place.)
There are several ways to fix it prior to the next release of IxOS/IxNetwork/IxLoad:
1. Install appinfo 1.0.0.257 or above. This is probably not possible at a customer site. 2. The likely culprit is Statengine PCPU. Rename the registry node HKEY_LOCAL_MACHINE\SOFTWARE\Ixia Communications\Statengine PCPU\InstallInfo (Just call it something else, like “_InstallInfo”). You could also just remove the entry, but renaming makes the change easily reversible. 3. Replace the file C:\Program Files\Ixia\appinfo\data\appinfo_Statengine CPU.xml with the attached file.
19. In IxNetwork, Clear Statistics button in the Home ribbon does not clear protocol statistics
Resolution
The Clear Statistics button in the Home ribbon does not clear protocol statistics (such as FCoE and DCBX).
To resolve the issue, do the following:
1. Select that protocol node in the Protocols tree. 2. Right click to display the context menu. 3. Select Clear Stats NOTE: This option clears the statistics for the selected protocol.
39
IxNetwork FAQ 20. Unable to establish chassis connection from IxNetwork client even though we can ping chassis from client
Description
We have seen several instances where IxNetwork client was unable to establish communication with the chassis even though chassis can be reached via ping.
When this happens, you will notice no logs on IxServer giving indication that IxNetwork client is trying to establish connection. Restarting HW manager service or disabling firewall service won't help.
This problem normally happens when Chassis IP address is changed and HW manager service is not bounded to newly configured IP address. In this situation you can clearly notice from HW manager log that the service is trying to bind with local management IP address instead of new IP address.
There's a file call 'IxiaChassisIPEntry.txt' located under IxOS directory, this file maintains Chassis IP and HW manager service keeps track of that.
Resolution
Try following steps to resolve this problem:
1. Stop IxServer 2. Delete/Rename or modify this file (IxiaChassisIPEntry.txt) with correct IP 3. Restart HW manager service 4. Restart IxServer 5. Try to connect it through IxNetwork client it should work
21. Cannot connect to chassis
Resolution
Refer to the attached document for details.
Not able to connect to chassis through IxNetwork.docx
22. In the event of a crash, where does IxNetwork save the recovered files and error logs?
Resolution
Following a crash, the recovered files are saved in the following locations:
C:\Users\
40
IxNetwork FAQ
The error logs (on crashes) are saved in the following location:
C:\Users\
23. In the event of a crash, where does IxNetwork save the recovered files?
Resolution
In the event of a crash, the files are saved in the following location:
C:\Users\...\AppData\Local\Ixia\IxNetwork\ErrorDumps
Error Messages
The error messages related questions are as follows:
1. Error while installing SQL Server 2005 – Native Client cannot be found 2. IxNetwork client seeing download of package ixpgid failed error 3. IxNetwork Tcl Proxy Server - error "Cannot (re)start a backend new process." 4. IxNetwork Tcl Proxy Server - no files matched glob pattern "/*/Ixia/IxNetwork/5.40.*/IxNetwork.exe" 5. Solaris - IxNetwork API - fatal: libstdc++.so.5: open failed: No such file or directory 6. Error 1625 received during installation: “This installation is forbidden by system policy” 7. Error while installing IxNetwork on Windows 7 64-bit 8. IxNet diagram logs collection error - Validation error path to file no found - IxLoad_DiagManifest.xml 9. Show Composer Initialization failed. Specified argument was out of range of valid values. Parameter name: port 10. IxNetwork\IxAutomate installation failed with Error ‘Microsoft SQL Server Express 2005 SP2 setup failed’ along with MSXML installation error 11. Error while installing SQL Server 2005 – Native Client cannot be found 12. Microsoft Bug: Input string was not in a correct format 13. Error while installing IxNetwork on Windows 7 64-bit 14. Installation error of SQL 2008 while installing IxNetwork
1. Error while installing SQL Server 2005 – Native Client cannot be found
Resolution
When installing Ixia Application you may encounter “An installation package for the product Microsoft SQL Server Native client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'" 41
IxNetwork FAQ
Error
When installing Ixia Application you may encounter "An installation package for the product Microsoft SQL Server Native client cannot be found”. Try the installation again using a valid copy of the installation package 'sqlncli.msi'" Error.
The actual issue appears to be as simple as an inability to upgrade an old Native Client edition.
To resolve, use the Add / Remove Programs panel to uninstall an existing SQL Server Native Client installation and you should be good to roll.
Note that this appears to be common for other editions of SQL Server 2005 too.
2. IxNetwork client seeing download of package ixpgid failed error
Resolution
Download of package ixpgid failed error
IxNetwork client seeing this error:
Exception data:
Exception type: Ixia.RpFramework.Client.RemoteException Message: A fatal error occured in statistics. Please save if desired and restart IxNetwork. For assistance, please contact Ixia support. Download of package(s) ixpgid failed on one or more ports belonging to chassis 10.81.97.155 Source: IxNetwork.Main
Void expandTextAndThrow(aptixia._Error);file
Solution: reboot the port resolved the problem.
42
IxNetwork FAQ
3. IxNetwork Tcl Proxy Server - error "Cannot (re)start a backend new process ..."
Resolution
Error received when starting IxNetwork Tcl Server Proxy -
Cannot (re)start a backend new process 'C:/Program Files/Ixia/IxNetwork/5.40.68.469- EB/IxNetwork.exe -nosplash -maxinstances 10000 -tclport 8010' for the client:user=cmgruser0 domain=. password=cmgrpasswd/0 execstr=C:/Program
Files/Ixia/IxNetwork/5.40.68.469-EB/IxNetwork.exe -nosplash -maxinstances 10000 -tclport 8010 error in CreateProcessAsUser error: For 'A required privilege is not held by the client' errors You probably need to elevate the rights of the user account calling this command 'Replace a process level token' right. To do so, open the Control Panel / Administrative Tools / Local Security Policy and add the user account to the 'Replace a process level token' right. You may have to logout (or even reboot) to have this change take effect.
4. IxNetwork Tcl Proxy Server - no files matched glob pattern "/*/Ixia/IxNetwork/5.40.*/IxNetwork.exe"
Resolution
Issue is caused by invalid configuration in IxNetwork Tcl Server Proxy config file. To resolve perform the following:
- pen cmgr.cmgrcfg in editor
- change -ixnetwork-path-glob option from "{/*/Ixia/IxNetwork/5.40.*/IxNetwork.exe}" to "{/*/Ixia/IxNetwork/5.40*/IxNetwork.exe}" (note: only item missing is ".")
- restart IxNetwork Tcl Server Proxy
5. Solaris - IxNetwork API - fatal: libstdc++.so.5: open failed: No such file or directory
Resolution
When trying to perform "package req IxTclNetwork", the following error is received:
couldn't load file "/export/ixos510sp3/lib/IxTclNetwork/libIxTclNetwork.so": ld.so.1: /export/ixos510sp3/bin/tclsh8.4: fatal: libstdc++.so.5: open failed: No such file or directory
This error is caused by missing components provided by the Solaris Tcl client installation.
This can be verified by executing the command "file $IXIA_HOME/lib/IxTclNetwork/libIxTclNetwork.so" from the shell prompt:
bash-2.03$ ldd libIxTclNetwork.so warning: ldd: libIxTclNetwork.so: is not executable
43
IxNetwork FAQ libstdc++.so.5 => (file not found) librt.so.1 => /usr/lib/librt.so.1 libpthread.so.1 => /usr/lib/libpthread.so.1 libtcl8.4.so => (file not found) libdl.so.1 => /usr/lib/libdl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libm.so.1 => /usr/lib/libm.so.1 libc.so.1 => /usr/lib/libc.so.1 libgcc_s.so.1 => (file not found) libaio.so.1 => /usr/lib/libaio.so.1 libmp.so.2 => /usr/lib/libmp.so.2 libthread.so.1 => /usr/lib/libthread.so.1 /usr/platform/SUNW,Sun-Blade-100/lib/libc_psr.so.1
Note that the library dependencies libstdc++.so.5 and libgcc_s.so.1 could not be found.
To resolve, re-install the IxOS and IxTclNetwork API client packages and verify that libstdc++.so.5 and libcc_s.so.1 can be found in
If libstdc++.so.5 and libcc_s.so.1 are located in the Ixia installation directory, verify that the system environment variable LD_LIBRARY_PATH contains
6. Error 1625 received during installation: “This installation is forbidden by system policy”
Resolution
To resolve, perform the following:
1. Start / Run / control admintools / OK 2. Double-click Local Security Policy. 3. Expand Software Restriction Policies. If no software restrictions are displayed, right-click Software Restriction Policies and then click Create New Policy. 4. Double-click the Enforcement Object Type in the right hand pane. 5. Click the All users except local administrator’s radial button and then click OK. 6. Shut down and restart your server.
7. Error while installing IxNetwork on Windows 7 64-bit
Resolution
This message is displayed at the beginning of IxNetwork installation on a Win 7 machine. There is a check in IxNetwork installer to prevent its installation on unsupported operating systems.
To resolve this issue, users need to delete the registry value related to the application from ‘HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers’ registry key and retry the installation.
NOTE: If the above solution does not work, work around the problem by executing %ProgramFiles%\IxiaInstallerCache\IxNetwork\
44
IxNetwork FAQ
8. IxNet diag logs collection error - Validation error path to file no found - IxLoad_DiagManifest.xml
Description
IxNet diagram logs collection error - Validation error path to file no found - IxLoad_DiagManifest.xml
When the IxNetwork diagnostics are run, then they see this error.
Validation error path to file no found - IxLoad_DiagManifest.xml
Resolution
When a repair install on IxNetwork was attempted to fix the error, it was noticed that the disk space on the C: drive was low. Free up disk space by deleting temp files or unneeded installers. Then try to run diagrams again. If unsuccessful, repair the IxNetwork install and try again.
9. Show Composer Initialization failed. Specified argument was out of range of valid values. Parameter name: port
Description
When started from within the IxNetwork GUI, TestComposer fails to initialize correctly, and displays an error message.
Resolution
To prevent this from happening, before starting TestComposer ensure the following:
- The Windows Firewall is disabled, or at least these ports required by IxNetwork are not blocked: 5768, 26000, 27001, 7700-9099, 33001-33099. - DNS is enabled on the IxNetwork computer and the computer name can be resolved in DNS.
More specifically, when running IxNetwork 5.50SP1 on Windows 2003 Server with the aforementioned configuration enabled and you still encounter this condition, you need to start IxNetwork in Tcl Server mode for TestComposer to initialize correctly.
45
IxNetwork FAQ
10. IxNetwork\IxAutomate installation failed with Error "Microsoft SQL Server Express 2005 SP2 setup failed" along with MSXML installation error
Description
MSXML and SQL database setup failed during IxNetwork installation.
Resolution
Follow the steps given below:
1. Run the Windows Installer CleanUp utility. (Given link below)
2. Select MSXML6 Service Pack 2 (KB954459) [6.20.1099.0] in the list, and then click remove.
Then run IxNetwork installer again.
msicuu2.exe
11. Error while installing SQL Server 2005 – Native Client cannot be found
Description
When installing Ixia Application you may encounter "An installation package for the product Microsoft SQL Server Native client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi' Error.
Resolution
The actual issue appears to be as simple as an inability to upgrade an old Native Client edition.
To resolve, use the Add / Remove Programs panel to uninstall an existing SQL Server Native Client installation and you should be good to roll.
Note that this appears to be common for other editions of SQL Server 2005 too.
12. Microsoft Bug: Input string was not in a correct format
Description
46
IxNetwork FAQ
After a successful installation of IxNetwork, the application would not start, and I get an error message: ‘Microsoft Bug: Input string was not in a correct format’. Input string was not in a correct format. There is a problem in your windows environment, and the application does not run.
Resolution
In order to fix this issue please refer to this document: https://connect.microsoft.com/feedback/viewfeedback.aspx?FeedbackID=253265&wa=wsignin1.0&sit eid=210
The problem is that the KEY_CURRENT_USER\Control Panel\International\sPositiveSign in the registry is completely empty. You get this from the Microsoft document. Editing this and changing it to an empty string solves the problem.
13. Error while installing IxNetwork on Windows 7 64-bit
Description
Error while installing IxNetwork in Windows 7 64-bit. The issue may be caused while installing IxNetwork on Win 7 in compatibility mode.
Resolution
This message is displayed at the beginning of IxNetwork installation on a Win 7 machine. There is a check in IxNetwork installer to prevent its installation on unsupported operating systems.
To resolve this issue, users need to delete the registry value related to the application from “HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers” registry key and retry the installation.
NOTE: If the above solution does not work, work around the problem by executing %ProgramFiles%\IxiaInstallerCache\IxNetwork\
14. Installation error of SQL 2008 while installing IxNetwork
Description
During installation of a Ixia product SQL 2008 installation may fail with an error in the log 'Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC. Access is denied'
This error is seen when the user account is lacking some/below privileges.
Local Policy Object Display Name User Right
Backup files and directories SeBackupPrivilege
Debug Programs SeDebugPrivilege
Manage auditing and security log SeSecurityPrivilege
47
IxNetwork FAQ Resolution
Follow the steps to add rights as a local administrator account:
Log on to the computer as a user who has administrative credentials. Click Start, click Run, type Control admintools, and then click OK. Double-click Local Security Policy. In the Local Security Settings dialog box, click Local Policies, double-click User Rights Assignment, and then double-click Backup Files and Directories. In the Backup Files and Directories Properties dialog box, click Add User or Group. In the Select User or Groups dialog box type the user account being used for setup, and then click OK two times. Repeat the procedure for the other two policies mentioned in the Cause section On the File menu, click Exit to close the Local Security Settings dialog box. Restart the installation of Ixia product to install SQL 2008
NOTE: For more information, please refer http://support.microsoft.com/kb/2000257
Other
Other frequently asked questions are listed as follows:
1. Client PC Memory and Performance monitoring utility 2. Is it possible to copy port configurations in IxNetwork 3. IxNetwork 5.40 ViperCore feature set comparison with Load Modules 4. IxOS/IxNetwork PTP max supported sync frames per second 5. IxNetwork ISIS NSF (no stop forwarding, as known as graceful restart) 6. Does IxNetwork 5.30 support RFC4983 7. In IxNetwork, Increment By is disabled 8. How to configure Microsoft IAS 2003 to work with 802.1x in IxNetwork or IxLoad 9. What result do we report for per port binary search? 10. Is it possible to copy port configurations in IxNetwork? 11. Link down on traffic flows in IxNetwork
1. Client PC Memory and Performance monitoring utility
Resolution
Please use attached utility to monitor client PC's memory and performance. This utility will help to troubleshoot OOM issues we have seen with client PC.
48
IxNetwork FAQ
2. Is it possible to copy port configurations in IxNetwork
Resolution
Is it possible to copy port configurations in IxNetwork? This is not possible in IxNetwork 5.30 or prior but a partial work-around may help.
Copying or duplicating port configurations is not supported in IxNetwork 5.30. A feature request, FRA001362, was submitted. For a work-around, the customer can create protocol interface configurations in IxExplorer/IxNetwork-FT and export the port file. Then he/she can import the legacy port file into IxNetwork. Please note that one cannot export the interface configuration configured in IxNetwork using the port files.
3. IxNetwork 5.40 ViperCore feature set comparision with Load Modules
Resolution
Attached PDF shows ViperCore feature comparison on different load modules
ViperCore_featureSe t_comparison.pdf 4. IxOS/IxNetwork PTP max supported sync frames per second
Resolution
IxOS/IxNetwork PTP max supported sync frames per second
Max rate supported is 32 fps (frames per second)
5. IxNetwork ISIS NSF (no stop forwarding, as known as graceful restart)
Resolution
IxNetwork ISIS NSF (no stop forwarding, as known as graceful restart)
Restart mode:
Normal – it means Ixia emulated router does not join restart process, it acts like a normal router without restart feature enabled
Restarting and starting – means Ixia emulated router starts the restart process. It will need route updates from DUT. The difference is the SA bit and RA bit sent in the packets to DUT.
49
IxNetwork FAQ Helper – it means DUT will be the one start the restart process. Ixia emulated router will be the router that sends routes to the DUT after the restart.
6. Does IxNetwork 5.30 support RFC4983?
Resolution
I have a Cisco customer asking if we support RFC4893 attribute,
- AS4_PATH
- AS4_AGGREGATOR
Are these being supported right now in 5.30 IxNetwork release?
The Answer is Yes, IxNetwork 5.30 does support 4-Byte AS# and new attributes.
7. In IxNetwork, Increment By is disabled
Description
In an IxNetwork MME/eNB S11/S1-U wireless configuration, the ‘Increment By’ grid operation is disabled if you have a validation error in the first range. For example, if you have multiple User Equipment ranges and you change the Count value (on the Basic tab) to 20 for all of them, the validation for the IMSI, IMEI, and MSISDN fields on the Identification tab fails. At this point, you cannot use the grid operations to correct the values for those three columns.
Resolution
IxNetwork will not re-enable the grid operation until you resolve the validation error in the first range, for each of the parameters. Rather than changing each value manually, use the following work- around:
Change the IMSI, IMEI, and MSISDN values in the first range such that the values are valid. For example, change IMSI to 206041000000001 (from the default value of 226041000000001) to clear the validation error in that cell. For each these columns use the Increment By grid operation to create valid values for the entire column. These will be temporary values. Set the desired values in the first range, and then use the Increment By operation to create the desired values for the entire column. For example, you can now restore the IMSI value to 226041000000001 in the first range and then increment the values in the column by 20.
8. How to configure Microsoft IAS 2003 to work with 802.1x in IxNetwork or IxLoad
Resolution
Microsoft IAS 2003 is customized to work in the Microsoft environment. It presents unique challenges for the Ixia application to ‘understand’ what it is asking for.
802 1x_IAS_Server2003 (2).docx (revised document 9/10/10) 50
IxNetwork FAQ
IAS-remote-access-config-forEAP.avi (a video on configuring IAS)
9. What result do we report for per port binary search?
Resolution
The test result of per port binary search may seem counter intuitive when pairs does not arrived the best iteration at the same time. I am attaching a scenario that was tested on a firewall device. We don't always report NDR as the result.
In results.csv we are reporting results from the best iteration (if exists) or the last iteration (if the best iteration doesn’t exist). In the current case, because the port pairs reach the best rate in different iterations there is no one best iteration in which all port pairs transmit at best rate. Because there is no best iteration we show in results.csv the results in the last iteration.
marketing-ip1280-tput.tcl (test script)
rfc2544-logFile.txt (Customer's test result in question)
10. Is it possible to copy port configurations in IxNetwork?
Description
Is it possible to copy port configurations in IxNetwork? This is not possible in IxNetwork 5.30 or prior but a partial work-around may help.
Resolution
Copying or duplicating port configurations is not supported in IxNetwork 5.30. A feature request, FRA001362, was submitted. For a work-around, the customer can create protocol interface configurations in IxExplorer/IxNetwork-FT and export the port file. Then he/she can import the legacy port file into IxNetwork. Please note that one cannot export the interface configuration configured in IxNetwork using the port files.
11. Link down on traffic flows in IxNetwork
Description
Link down on traffic flows in IxNetwork - To measure how many packets will be lost and how long exactly takes to recover data plane after reset their router.
Resolution
If you shut down a link on the DUT (connected to an Ixia endpoint), then the Ixia port shows as red (link down), and statistics collection stops almost immediately. When this occurs, you cannot measure how many packets will be lost and how long it takes to recover the data plane after resetting the DUT. The issue can be resolved by following the step given below: Under the IxNetwork Port Manager, enable Transmit Ignore Link Status for each port. With this setting, statistics will continue to be generated when the link is down (number of packets transmitted, packet loss, and so forth).
51
IxNetwork FAQ
52