Data Plane Software Suite 1.1.
|
Netra Data Plane Software Suite 1.1 Release Notes |
The Netra Data Plane Software Suite 1.1 Release Notes contain last minute information about the Netra Data Plane Software Suite 1.1.
Compilation fails if a function within an application returns a structure. This situation is due in part to private functions missing from libc.
The workaround is for the function to return a pointer to the structure.
The ldm stop-domain -f command is disabled if the domain has any PCI-Express I/O buses bound to it. This is currently the case with all the platforms supported by Logical Domains 1.0 software. In this case, an error message of the following form is returned: LDom ldg1 stop notification failed
Due to this restriction, if an I/O domain is unresponsive to console or network input, and is unable to process a domain service shutdown request from the Logical Domains Manager, then there is no way to perform an isolated stop of that domain.
Workaround: Shut down all the other domains, and power cycle the server.
The NDPS requires a base RA <= 246M. This can be accomplished through judicious allocation of memory to a previously created domain.
The workaround is to create the NDPS domain first, after the primary domain is configured, and allocate X MB of memory to the primary domain where X is
0 < ((128 MB + X MB) mod 256 MB)
Reasonable values for a primary domain memory size that meets this restriction include anything in the following ranges:
516MB-628MB
772MB-884MB
1028MB-1140MB
1284MB-1396MB
and so on, adding 256MB to each value above to define additional ranges.
When a domain that uses an IPC channel is reset, there is no method to reestablish the channels without also rebooting the link partner domain. You can only use the tnsmctl command to reconfigure the channels after both the LWRTE and the Solaris domains have been rebooted.
| Note - This only applies to channels that have been configured using the tnsmctl command. The global control channel is not affected by this bug and reestablishes automatically. |
The RLP reference application does not work on CP3060 even when ARP is enabled. Currently, the ipge driver puts the device in promiscuous mode and captures all traffic for RLP application.
Workaround: Break the link between the two switches that connect the extended network fabric ports. Use the telnet utility to access one of the switches and shut down the interconnecting port.
Currently, printf does not support %f in a format string.
Chaining of messages using the b_next field in the mblk_t structure is not supported in this release. ipc_tx() must be called once for every message.
The ipc_connect() call in the Solaris kernel does not return a valid IPC handle. For this reason, the kernel interface cannot be used by entities outside the tnsm driver.
Support for the CP3060 platform in the RLP application can be enabled by making the following changes:
Add the -DDEVID_1060 string to the TEJACC_CFLAGS line.
In RLP/src/app/rlp_config.h, change the RLP agent count to 1.
In RLP/src/app/rlp.c, make the following changes in _main_split_rxtx(void) function.
Move up the #ifdef RLP_RUN_ALL_THDS by one line after the switch (thdidx) statement. This is similar to the following code on the next page:
The rcon utility does not support ctrl+c in this release. The terminal hangs when a ctrl+c is sent to the terminal that connects to the Solaris domain.
You must have a license file to use the software. When you invoke an ARC International product, the FLEXlm license manager reads the license file. The license manager allows you to invoke the software based on the information in the license file. ARC International issues two kinds of licenses:
A node-locked license, or uncounted license, is a license that runs on a single machine. The license file contains permission to run various tools for one user only.
To obtain a license file, email the following information to license@arc.com:
You can find the host ID by running the FLEXlm utility, lmhostid (located in the bin subdirectory of your Teja installation).
When you receive the license file (for example, licfile.lic), place it in the following folder: /opt/ARC/license. After your license file is installed, use one of the following methods to make FLEXlm aware of the license:
Set LM_LICENSE_FILE environment variable to C: ARC license/arc.lic. To set the LM_LICENSE_FILE environment variable in Windows, consult the help utility for your version of Windows. For Windows, the location of the arc.lic file is stored in the following Windows registry entry:
My Computer\textbackslash HKEY\_LOCAL\_MACHINE\textbackslash SOFTWARE\textbackslash FLEXlm License Manage\textbackslash ARCD\_LICENSE\_FILE |
This entry is automatically updated if a successful checkout occurs from a license file that was not previously listed in the registry file. You can change or delete the registry entry using the Windows regedit utility.
Set LM_LICENSE_FILE environment variable to /opt/ARC/license/arc.lic.
To set the environment variable for UNIX or Linux, use the setenv command from within a C shell; for example:
A floating license, or counted license, is a network license for a specified number of seats. It allows multiple users to use a single license file to be shared between a specified number of computers. A floating license requires that the lmgrd license daemon process be running on a license server machine. The number of seats specified in the license file is the number of concurrent users that can use the products.
To obtain a floating license file, email the following information to license@arc.com:
You can find the host ID by running the FLEXlm utility, lmhostid (located in the bin subdirectory of your Teja installation). The host name of the FLEXlm license server (where the license manager is installed). Use the hostname (or uname -a) command to find the server name for a UNIX or Linux server. On a Windows machine, run the lmtools.exe utility on the server and select the System Settings tab on a Windows machine. As an option, you can include a specific port to be used on your server. The default port is 7434.
After you have obtained the license file, you must set up the license file on the server and set an environment variable on each client machine that runs the tools. The server that runs the FLEXlm utilities and contains the license file does not need to have the ARC International products installed. However, it does need to have the FLEXlm utilities and license file installed. You can obtain the FLEXlm utilities for your platform from the bin subdirectory in the Teja installation directory.
Copy the FLEXlm utilities and the license daemon to the license server. Copy the license file (typically arc.lic) into the FLEXlm utilities directory. Start the license manager daemon by entering the following command syntax:
Where /path/to/arc.lic is the directory to the license files location, and /path/to/arcflex.log is the location and file name of the FLEXlm log file. The following example points to the license file in the FLEXlm directory, and also places the log file in the FLEXlm directory:
The license manager should now be enabled and running. If you have difficulties setting up your floating license, see the FLEXlm End Users Guide. Setting up UNIX or Linux workstations to use the floating license To run the toolset on a machine (including the license server), set the environment variable LM_LICENSE_FILE to port@servername. For the port, use the port number located in the first line of the license file. The default port number is 7434. For the server name, use the server name located in the first line of the license file. In a Bourne or Korn Shell, use the following command:
In a C Shell, use the following command syntax:
For example, if your server name is Server1 with port 7434, use the following command in a C shell: setenv LM_LICENSE_FILE 7434@Server1
Copy the license utilities from the license directory of your installation to the directory on your server (for example C:\ARCiicense). Also, copy the license file (arc.lic) that you received from ARC to the same directory. You can also obtain the FLEXlm utilities from the bin directory in the Teja installation.
Use lmtools.exe to a open a window that displays the Service/License File tab.
Check Configuration Using Services by clicking the Configure Services tab. Enter a new name for this service (for example, ARC License Manager). Enter the path to lmgrd.exe (for example, c:\ARCiicense
inimgrd.exe), the new permanent floating license file (for example, c:\ARCiicense\arc.lic), and, optionally, create a debug log file.
To run lmgrd.exe as a service,
1. Select Use Services from the Service/License tab.
2. Select Start Server at Power Up.
This starts the service automatically when you start your computer.
4. Click the Start/Stop/Reread tab.
The entry, ARC License Manager, is highlighted in the list box.
You may have to wait for several seconds for the lmgrd process to start.
The license manager should now be enabled and running. If you have difficulties setting up your floating license, see the FLEXlm End User's Guide.
Set up Windows workstations to use the floating license. After your license file is installed, make FLEXlm aware of the license by setting the environment variable LM_LICENSE_FILE to include the location of the new license file. To set the LM_LICENSE_FILE environment variable in Windows, consult the help utility for your version of Windows. For example, if your server name is Server1 with port 7434, use the following syntax: 7434@Server
This section provides example configuration procedures for running remote command-line interface (CLI) support. The remote CLI supports applications using the Logical Domain Channel driver (LDC) in the Logical Domains (LDoms) framework.
You need to install the following files to your Solaris LDom domain. You can get these files after you install the SUNWndps package and make the binary under src/apps/remotecli/rconsole/ldc_so:
Here is the example for setup in the Solaris domain:
cp cdum* /usr/kernel/drv
cp remc* /usr/kernel/drv
cd /usr/kernel/drv/
ln -s /usr/kernel/drv/remc.conf remc.conf
ln -s /usr/kernel/drv/cdum.conf cdum.conf
cd /usr/kernel/drv/sparcv9
ln -s /usr/kernel/drv/remc remc
ln -s /usr/kernel/drv/cdum cdum
rem_drv cdum
add_drv cdum
rem_drv remc
add_drv remc
cp -f rcon /usr/bin
chmod ugo+xr /usr/bin/rcon
echo ¡°rcon 6000/tcp¡ >> /etc/services
cp -f rcon.xml /var/svc/manifest/network/rcon.xml
svccfg import /var/svc/manifest/network/rcon.xml
svcadm enable svc:/network/rcon:rcon
From any remote system, telnet to the Solaris domain port number 6000. Type ifconfig -a to get the IP or host name for the Solaris domain.
Now compile the remotecli application for NDPS.
From your SUNWndps package src/apps/remotecli/, do the following:
Run gmake and then enter cd code/main. Then do gmake again. You then have the remotecli application binary. Boot that application binary in your Lightweight Runtime Environment (LWRTE) domain.
Once the application is running in your LWRTE domain, then you can do a debug/core dump and profile remotely. This is a reference application showcasing the use of the remote CLI.
1 of channels solaris-cli found channel ids = [ 0x4 ] the channel 5 is for CLI! 1 of channels solaris-cored found channel ids = [ 0x5 ] ndps> connect 4 |
Select the RCLI channel 4 to connect to the LWRTE domain after the message says the link is UP.
In remote CLI, do same as the local CLI for debugging.
To quit the Debugger, simply type c or cont commands.
You can set the dump channel and dump directory (optional) before going into the debugger:
1 of channels solaris-cli found channel ids = [ 0x4 ] the channel 5 is for CLI! 1 of channels solaris-cored found channel ids = [ 0x5 ] ndps> setdump 5 [-d /tmp] |
This picks the channel for coredump and /tmp will store the coredump file.
Coredump is supported under Debugger. You need to get into Debugger by sending the ¡°send break dbg¡ command.
ndps> send break dbg dbg> show-ldc 1 of channels ndps-cli found channel ids = [ 0x5 ] the channel 5 is for CLI! 1 of channels ndps-cored found channel ids = [ 0x6 ] |
The program then tells you which LDC channel ID to use (for example,
ndps-cored).
where ldcid# is obtained from show-ldc in the Debugger.
The program will start to dump the core and transfer the core dump file to the Solaris domain You can then obtain the coredump file from the directory you specified under the Solaris domain and use the gdb tool to analyze it (make sure you have the NDPS binary image ELF format with the coredump file).
| Note - You need to do stumped <id> [-d <dump dir>] in your telnet terminal in the Solaris domain before doing setdump <id> [-d <dump dir>] in the LWRTE domain. |
Type connect <ldc> to get to the NDPS domain. All of the output is diverted to the remote console. You can therefore capture all profile output remotely.
| Note - This feature requires the LDoms 1.0 release; download and follow LDoms 1.0 official release instructions. |
The following instructions assume that you have installed the necessary Ldom 1.0 software and firmware. You simply just follow the instruction below to create the ldoms you need to run remote CLI.
For the LWRTE domain, you need to do the following ldm configuration for ldg1:
/opt/SUNWldm/bin/ldm add-vdpcs ndps-cli ldg1
/opt/SUNWldm/bin/ldm add-vdpcs ndps-cored ldg1
For NDPS domain, you need to do the following ldm configuration for ldg2:
/opt/SUNWldm/bin/ldm add-vdpcc solaris-cli ndps-cli ldg2
/opt/SUNWldm/bin/ldm add-vdpcc solaris-cored ndps-cored ldg2
The following are detailed configuration examples:
Configuring the Primary Domain
/opt/SUNWldm/bin/ldm remove-mau 8 primary
/opt/SUNWldm/bin/ldm remove-vcpu 28 primary
/opt/SUNWldm/bin/ldm remove-mem 31G primary
/opt/SUNWldm/bin/ldm add-vdiskserver primary-vds0 primary
/opt/SUNWldm/bin/ldm add-vconscon port-range=5000-5100 primaryvcc0 primary
/opt/SUNWldm/bin/ldm add-vswitch net-dev=e1000g0 primary-vsw0 primary
/opt/SUNWldm/bin/ldm list-config
/opt/SUNWldm/bin/ldm add-config remotecli-config
Reboot the system to activate remotecli-config.
Configuring LDoms Running NDPS
/opt/SUNWldm/bin/ldm add-vcpu 16 ldg1
/opt/SUNWldm/bin/ldm add-mem 4G ldg1
/opt/SUNWldm/bin/ldm add-vnet vnet1 primary-vsw0 ldg1
/opt/SUNWldm/bin/ldm add-vdsdev /dev/lofi/1 vol1@primary-vds0
/opt/SUNWldm/bin/ldm add-vdisk vdisk1 vol1@primary-vds0 ldg1
/opt/SUNWldm/bin/ldm add-vdpcs ndps-cli ldg1
/opt/SUNWldm/bin/ldm add-vdpcs ndps-cored ldg1
/opt/SUNWldm/bin/ldm bind ldg1
/usr/openwin/bin/xterm -sb -sl 5000 -T ¡°Console: ldg1¡ geometry 80x12+98+193 -bg black -fg white -e /usr/bin/telnet localhost 5000 &
/opt/SUNWldm/bin/ldm start ldg1
Configuring LDoms Running Solaris
/opt/SUNWldm/bin/ldm add-domain ldg2
/opt/SUNWldm/bin/ldm add-vcpu 12 ldg2
/opt/SUNWldm/bin/ldm add-mem 8G ldg2
/opt/SUNWldm/bin/ldm add-vnet vnet2 primary-vsw0 ldg2
/opt/SUNWldm/bin/ldm add-vdsdev /dev/lofi/2 vol2@primary-vds0
/opt/SUNWldm/bin/ldm add-vdisk vdisk2 vol2@primary-vds0 ldg2
/opt/SUNWldm/bin/ldm add-vdpcc solaris-cli ndps-cli ldg2
/opt/SUNWldm/bin/ldm add-vdpcc solaris-cored ndps-cored ldg2
/opt/SUNWldm/bin/ldm bind ldg2
/usr/openwin/bin/xterm -sb -sl 5000 -T ¡°Console: ldg2¡ -geometry 80x12+98+193 -bg black -fg cyan -e /usr/bin/telnet localhost 5001 &
/opt/SUWldm/bin/ldm start ldg2
You can request Sun support and provide feedback to Sun at the following email address:
|
Copyright |
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, Netra, docs.sun.com, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agreements.
U.S. Government Rights--Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, États-Unis. Tous droits réservés.
Sun Microsystems, Inc. possède les droits de propriété intellectuels relatifs à la technologie décrite dans ce document. En particulier, et sans limitation, ces droits de propriété intellectuels peuvent inclure un ou plusieurs des brevets américains listés sur le site http://www.sun.com/patents, un ou les plusieurs brevets supplémentaires ainsi que les demandes de brevet en attente aux les États-Unis et dans d'autres pays.
Ce document et le produit auquel il se rapporte sont protégés par un copyright et distribués sous licences, celles-ci en restreignent l'utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l'autorisation préalable et écrite de Sun et de ses bailleurs de licence, s'il y en a.
Tout logiciel tiers, sa technologie relative aux polices de caractères, comprise, est protégé par un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produit peuvent dériver des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX est une marque déposée aux États-Unis et dans d'autres pays, licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, Java, AnswerBook2, Netra, docs.sun.com, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux États-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux États-Unis et dans d'autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.
L'interface utilisateur graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox dans la recherche et le développement du concept des interfaces utilisateur visuelles ou graphiques pour l'industrie informatique. Sun détient une license non exclusive de Xerox sur l'interface utilisateur graphique Xerox, cette licence couvrant également les licenciés de Sun implémentant les interfaces utilisateur graphiques OPEN LOOK et se conforment en outre aux licences écrites de Sun.
LA DOCUMENTATION EST FOURNIE "EN L'ÉTAT" ET TOUTES AUTRES CONDITIONS, DÉCLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA LIMITE DE LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L'APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L'ABSENCE DE CONTREFAÇON.