| |
NOTE: |
When this topic is opened from the CD-ROM, the links from this topic to other help topics will not work. Links within the topic will work and once you've installed NetSight Console, you can launch the help system and access help for all topics.
|
This document provides instructions for installing NetSight Console. The most recent version of this file is located on the NetSight Documentation web page: http://www.enterasys.com/support/manuals/netsight.html.
General Installation Information
NetSight Console lets you monitor device status, define network configuration, and automate troubleshooting tasks. Two versions of NetSight Console are available:
- NetSight Console Standalone - provides a NetSight Server and a local Console Client installed on a single workstation and allows sharing the NetSight Database with the suite of NetSight Plugin applications on the same system.
- NetSight Console Client/Server - provides a NetSight Server and a local Console Client installed on a single workstation and allows sharing the NetSight Database with Remote Console Clients and the suite of NetSight Plugin applications.
NetSight Console may be installed on the Windows XP®, Windows 2003 Server® 4.0, or Windows® 2000 platform, or Linux Red Hat version 9, Linux Enterprise WS, ES, SuSE Linux, or the UNIX® Solaris®
2.8, 2.9, or 2.10 platform. Before you install Console, it is recommended that you read the NetSight Console Release Notes. You can also access the release notes for Console from the CD with a web browser by opening the relnotes.htm file for NetSight Console. The most recent version of the release notes can be found on the NetSight Documentation web page: http://www.enterasys.com/support/manuals/netsight.html
The following tasks comprise the NetSight Console installation process:
- Installing any required operating system patches (UNIX only).
- Preparing your system for installation.
- Installing NetSight Console.
| |
NOTE: |
When re-installing Console, the installation program saves copies of any FlexViews that you have created/modified in the <install area>\Enterasys Networks\NetSight Console\backup\FlexViews folder.
|
| |
CAUTION: |
When re-installing Console, MIBs that you have added to the <install area>\Enterasys Networks\NetSight Console\client\etc\mibs directory will be removed during installation. You should always add MIBs
to the <install area>\Enterasys Networks\NetSight Console\client\etc\mibs\MyMIBs directory. The MyMIBs directory is saved and restored during re-installation. Refer to How to Add MIBs for more information.
|
System Requirements
The system requirements for operating NetSight Console are listed here.
- Windows 2000, Windows 2003 Server, Windows XP Professional w/Service Pack 2 (qualified on the English version of the operating systems), Linux Red Hat Version 9, Linux Enterprise v3 ES, Linux SuSE
- Recommended P4-2.4 GHz, 1GB RAM
- Free Disk Space - 600MB
- Solaris 2.8, 2.9, 2.10 (with latest operating system patches installed.)
- Recommended Sun® Ultra 30/60 (or equivalent), 900MHz, 1GB RAM
- Free Disk Space - 600MB
When you install NetSight Console, you can select to install a 90-day Evaluation Copy.
To upgrade from an evaluation copy of Console to a purchased copy, contact your
Enterasys Networks Representative to purchase the software and receive a License
Key. You do not need to reinstall the software to perform the conversion.
If your Evaluation copy has not expired:
-
In the Console main window, select Tools > Server Information.
-
In the Server Information window, click the License tab.
- Select Console from the table and click Change License.
- Read and accept the License and click OK.
- Enter the License Key and click Update.
If you have let your Evaluation Copy expire, when you launch NetSight Console a window opens where you can enter the License key.
Converting a Database
If you are upgrading from Console release 1.5.1, you can convert your Console 1.5.1 database to preserve most of your network information. However, some elements in the earlier version cannot be converted to Console 2.1. Refer to
How to Convert a Database for more specific information on converting your Console 1.5.1 database.
If you are upgrading from Console release 2.0.x to Console 2.1, your data will
be automatically migrated.
Upgrading a Console License
It is possible to update Console to change from a Standalone to a Client/Server configuration. However, on Windows systems, this requires re-installing Console 2.1 using the Client/Server license key. This update can be done on
Solaris and Linux systems without re-installing.
| |
NOTE: |
It is not possible to upgrade from a Client-Only configuration to either a Standalone or Client/Server configuration without re-installing with the upgraded license key.
|
Upgrading your Console license on a Linux or Solaris system:
- Navigate to the /var/Enterasys_Networks
- Edit the run_conf.sh file using your favorite text editor.
- To change from a Standalone to a Client/Server configuration, modify the hostname line to read:
JBOSS_HOSTNAME=
- In Console, select Tools > Server Information from the menu bar. The Server Information window opens.
- Select the License tab.
- Select the license that you want to change and click Change License. The Change License window opens.
- Read and accept the terms of the license agreement and click OK.
- Enter the License Key and click Update. The license file will be updated with the new license number.
- Restart the server:
- Navigate to the <installdir>/server
- Start the server using the command: stopserver.sh
- Start the server using the command: startserver.sh
| |
NOTE: |
You can set a Console licensed for a Client/Server configuration to allow only a local host to connect to the server by editing the hostname line to read: JBOSS_HOSTNAME="127.0.0.1". Restart the server after editing the run_conf.sh file.
|
Console Release 2.1 can be installed and co-exist with Console Release 1.5. However, some precautions must be taken to prevent loosing information or features in this environment or when either version is uninstalled.
- Prior to installing Console 2.1 on a system with Console 1.5, preserve a copy of the .nsaservrc file in the <Console 1.5 install area>\Enterasys Networks\NetSight Atlas Shared\Users\AllUsers directory.
- If you have selections that were added to the device-level right-click menu, you should
preserve a copy of the ThirdPartyDeviceMenu.txt file from
Console 1.5 (in the <Console 1.5 install area>\Enterasys
Networks\NetSight Console\backupshared) prior to installing Console 2.1. You will need to
restore the 1.5 version of this file or copy portions of the prior version into the one created by
the Console 2.1 installation.
- If you uninstall Console 2.1 while retaining Console 1.5, you must restore your saved copy of the .nsaservrc file to the <Console 1.5 install area>\Enterasys Networks\NetSight Atlas Shared\Users\AllUsers directory.
- If you later uninstall Console 1.5 while retaining Console 2.1, you will need to re-install Console 2.1.
| |
CAUTION: |
If
NetSight Console 2.x (licensed version or evaluation copy) is installed on a
system with a 1.x version of Console that is integrated with HP OpenView, the
1.x version of Console will no longer be accessible from the HPOV menus.
|
During the installation of NetSight Console, you have the option of
enabling (configuring to launch automatically) NetSight Services. The
services offered depend on whether your platform is Windows, Solaris, or Linux.
- SNMPTrap Service (Windows, Solaris, and Linux) - Enables SNMP trap messages to be received
and logged when problems or irregularities are detected on network devices. Only
one trap service may be running at a time on a machine. If you are also running
a network management system on the Console machine, you may wish
to use the network management trap service.
When properly configured, NetSight Console supports SNMP Informs (trap messages that require an
acknowledgement of receipt). Refer to Configuring
SNMPtrap Service for SNMPv3 Inform Support to learn how to perform this configuration.
Windows Users: Windows users should check for and stop any other SNMP
trap service before enabling the NetSight version (see
Check For and Stop Other Services).
- TFTP (Windows, Solaris, and Linux) - Enables you to upload and download configuration files, and download firmware to devices. Only one TFTP service may be running at a time on a machine.
Windows Users: Windows users should check for and stop any other TFTP service before enabling the NetSight version (see Check For and Stop Other Services).
Solaris Users: You may use the TFTP service that exists in UNIX; however, the NetSight version of TFTP provides additional features for Console, so you may wish to enable the NetSight version. If you elect to enable the NetSight version on the Solaris platform, you must stop the UNIX TFTP service and perform some configuration steps in order for it to work properly, as follows:
- Edit your /etc/inetd.conf file. Comment out any existing TFTP entries.
- Execute the command:
/etc/rc2.d/S72inetsvc stop
- Execute the command:
/etc/rc2.d/S72inetsvc start
- Execute the command:
/etc/rc2.d/S99NsTftp start
Linux Users: Typically, the TFTP service that exists in Linux is disabled; however, if it is enabled, you may wish to disable it and enable the NetSight version of TFTP which provides additional features for Console. If you elect to enable the NetSight version on the Linux platform, you must first disable the Linux TFTP service and perform some configuration as follows:
- Using a text editor, edit the file /etc/xinetd.d/tftp
- Set disable = yes
Sample file:
service tftp
{
flags = REUSE
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.tftp
disable = yes
}
- Then run : /etc/rc3.d/S56xinetd restart
- BOOTP (Windows only) - Enables the Console workstation to also be a
BOOTP server. This allows the workstation to supply devices with firmware images
(or other basic identity information) in the event the device's current firmware
image becomes corrupt. Only one BOOTP service can be
running at a time on a machine. If you elect to enable this
service, you will need to
create a Bootptab file for the
BOOTP service to read.
Solaris Users: Use the UNIX BOOTP
service if you wish to take advantage of BOOTP. Refer to the UNIX BOOTP
"man pages" for more information.
- Syslog (Windows only) - Console maintains a record of syslog messages in the Syslog tab of the Alarm & Events panel. A Syslog Pattern Configuration window lets you define a pattern to specify how the information from a non-standard syslog file is presented in a tab in the Alarm and Events view.
When you enable a NetSight service, it runs in the background on the workstation.
The service starts automatically by default, and if you shut down and restart
the workstation, the service is restarted automatically.
After you've installed Console, you can use the Tools >
Options
Services for NetSight Server window to enable or disable the automatic startup of these
services. For example, if you do not enable the TFTP service when you
install, you can use the Service Launcher window to enable the automatic
startup of the TFTP service. In addition, there may be times when you want
to stop or restart the services manually; for information see How to Stop and Start
NetSight Services.
NetSight Plugin Applications can be integrated and launched from the Console's Applications menu. When you install a NetSight Plugin application, the installer adds the path and name for the plugin to the NetSight.properties file.
| |
TIP: |
You can also configure this menu to launch your own applications. You can edit the NetSight.properties file to customize this menu to allow you to launch your own applications from the Console Applications menu. Refer to How to Add Applications to the Applications Menu for more information.
|
During the installation process,
you will be asked if you want to integrate NetSight Console with
Hewlett-Packard's HP OpenView Network Node Manager (NNM) software.
Answering Yes to this question enables you to access NetSight
Console and NetSight Device Manager from NNM.
Installing the Integration Piece
If you want to install the integration piece, it is
suggested that you shut down NNM when you install Console.
(It is all right to leave NNM processes running.) During the HP
OpenView portion of the Console installation, you will be
asked to provide the location in which to install the integration
components, and an HP OpenView integration script will run.
(Note: The installer looks for the path
\bin\ovw.exe directory in your HPOV installation area.
If it doesn't find the expected path, you will see a message informing you
that the path is incorrect.)
Lastly, you will receive a reminder that you can also run a manual
script to load Enterasys Networks MIBs and trap definitions into NNM.
Running the MIBs Script
Once NetSight Console is installed, you can go to the top level of your
NetSight Console installation area and run the loadmibs file
to load the Enterasys Networks MIBs and trap definitions into your NNM database. This takes approximately 45 minutes to an hour, which
is why it is not an automated part of the NetSight Console installation
process.
Accessing NetSight Applications from NNM
- To access NetSight Console from NNM, select My Apps > NetSight
Console from the menu.
- To access NetSight Device Manager from a device in NNM, right-click
the device and select NetSight Device Manager from the menu. This
menu option is
only available on Enterasys Networks devices
.
The following instructions can be used for installing NetSight Console on a Windows 2003 Server, Windows XP, or
Windows 2000 system. Before you can install Console on a Windows platform system, you need to:
Once your system is properly configured, you can proceed with:
Following are instructions for configuring the environment on Windows 2003 Server,
Windows 2000, and Windows XP platforms.
| |
NOTE: |
Some of the operations in the following instructions may generate
a message prompting you to reboot your system. It is not necessary to
reboot your system until you have completed the
configuration process.
|
Windows 2000
- Open your system's Control Panel (Start > Settings > Control
Panel) and double-click the System icon. The System Properties window opens.
- Select the Advanced tab and click the Performance options button. The Performance Options window opens.
- Verify that the "Application response" section has Optimize performance for: Applications selected.
- Click the Change button in the "Virtual Memory" section of the Performance
Options window. The Virtual Memory window opens.
- Enter the following settings in the "Paging file size for selected drive" section:
Initial size (MB) -- set to a minimum of 128 MB or equivalent to your system RAM.
Maximum size (MB) -- typically set to twice the Initial size. For example, if your Initial size is set to 128 MB, your maximum size would be set to 256 MB.
- Click Set and OK to close the
window.
- Click OK to close the Performance Options window.
- Click OK to close the System Properties window.
- With the cursor in an open area of the desktop, right click and select Properties from the drop-down menu.
The Display Properties window opens.
- Select the Settings tab, and set Colors to High Color (16 bit) and Screen area to 1024 by 768 pixels (recommended minimum).
The Color setting affects the appearance of Console windows. Certain
window features, such as table rows that appear with a color gradient can only
be enabled with color settings of 24 bit (16777216 colors) and above. Setting
the palette lower than 24 bit (16 bit - 65,536 colors) does not support
gradients.
- Click OK to close the Display Properties window.
- Reboot your system.
Windows XP and Windows 2003 Server
- Open your system's Control Panel (Start > Settings > Control
Panel) and double-click the System icon. The System Properties window opens.
- Select the Advanced tab and click the Settings button
in the "Performance" section. The Performance Options window opens.
- Select the Advanced tab and
verify that the "Processor scheduling" and "Memory usage" sections have Adjust for best performance of: programs selected.
- Click the Change button in the "Virtual Memory" section of the Performance
Options window. The Virtual Memory window opens.
- In the "Paging file size for selected drive" section, select the Custom size option and enter the following settings:
Initial size (MB) -- set to a minimum of 128 MB or equivalent to your system RAM.
Maximum size (MB) -- typically set to twice the Initial size. For example, if your Initial size is set to 128 MB, your maximum size would be set to 256 MB.
- Click Set and OK to close the window.
- Click OK to close the Performance Options window.
- Click OK to close the System Properties window.
- With the cursor in an open area of the desktop, right click and select Properties from the drop-down menu.
The Display Properties window opens.
- Select the Settings tab, and set the Screen resolution to 1024 by 768 pixels
(recommended minimum), and the Color quality to Medium (16 bit). The Color
setting affects the appearance of Console windows. Certain window
features, such as table rows that appear with a color gradient can only be
enabled with color settings of 24 bit (16777216 colors) and above. Setting the
palette lower than 24 bit (16 bit - 65,536 colors) does not support gradients.
- Click OK to close the Display Properties window.
- Reboot your system.
If you will be using the NetSight version of SNMPtrap and/or TFTP service, you cannot be running another version of that service on your
system. If you are running one of these non-NetSight services on your
system, you must shut it down before installing Console, as follows:
- Open the Services window on your system (on Windows 2000
systems - Control Panel > Services -- on Windows XP and Windows 2003 Server - Control Panel
> Administrative Tools > Services).
- Scroll down to find the service in the list.
- Right click on the service and select Stop from the popup menu.
- Right click on the service again and select Properties from the popup
menu.
- In the Properties window, set the Startup Type for the service to
Manual.
- Repeat for any other services, if necessary.
- Close the Services windows and Control Panel.
- Open the Task Manager and check to be sure that the process is not running.
- Close the Task Manager.
Now that you have configured your system, you are ready to install NetSight Console.
- Log onto your system as Administrator.
- Insert the NetSight Console CD into your system's CD
drive.
- In Windows Explorer, navigate to the CD drive and
open the Windows folder where the
install.exe application
resides.
- Double-click the
install.exe application.
- The NetSight Console Installer leads you through a series of windows that ask you for
all the information required in order to install Console. You will need the following information to complete the
Installer Program:
- License -- This is a unique number assigned to your copy of NetSight Console and are located on a label on your CD holder. Or you may choose to
install the NetSight Console Evaluation Copy.
- Destination Directory -- This is the path to your NetSight Console
Installation Directory. In the Destination Directory window, click Choose to
navigate to the directory, or type the path in manually.
When you have finished with this
series of windows, NetSight Console will be installed according to your
specifications.
On the Solaris platform, NetSight Console supports the Sun Solaris 2.8, 2.9, and
2.10 operating systems. Before installing Console, be sure to install
the latest patches for your operating system. You can download the most recent
operating system patches from http://sunsolve.sun.com.
Before installing NetSight Console on a Solaris platform, you need to:
Once your system is properly configured, you can proceed with:
The following procedures assume that the CD drive from which
you are installing is physically attached to the system where NetSight Console is being installed.
The user performing the installation must have privileges to create, read,
write, and execute within the installation
directory.
- Insert the NetSight Console CD into the CD drive.
- Use an xterm where you are logged in as root using the
su - command.
| |
NOTE: |
You may encounter a Java exception during the install when becoming the root user with the su - command. Be sure that your system's root environment has a proper DISPLAY variable setting. The Installation program will report a Java exception (InvocationTargetException) if the DISPLAY variable is undefined.
If this occurs:
|
- Using the
cd command, cd to the /cdrom/cdrom0 (where
0 is zero) directory. If it does not exist, make the directory using the mkdir -p command,
then cd to the newly created directory.
- Using the
ls command, check to see if the CD drive is mounted.
If no files are listed, issue the following commands:
cd /
mount -r -F hsfs /dev/sr0 /cdrom/cdrom0
(where 0 is zero).
- You can now launch the NetSight Console Installer (see Installing
NetSight Console (Solaris)).
Now that you have prepared your Solaris system for installation, you are ready to install Console.
- Use an xterm where you are logged in as root. (Be sure that your system's
root environment has a proper DISPLAY variable setting. For more information see
the above note.)
- Start the Installer by issuing the appropriate command:
/cdrom/cdrom0/Solaris/install.bin
- The NetSight Console Installer leads you through a series of windows that ask you for
all the information required in order to install Console. You will need the following information to complete the
Installer Program:
- License -- This is a unique number assigned to your copy of NetSight Console. It is located on a label on your CD holder. Or you may choose to
install the NetSight Console Evaluation Copy.
- Destination Directory -- This is the path to your NetSight Console
Installation Directory. In the Destination Directory window, click Choose to
navigate to the directory, or type the path in manually.
When you have finished with this
series of windows, Console will be installed according to your
specifications.
On the Linux platform, NetSight Console supports Red Hat Version 9, Enterprise
WS, ES v3, and SuSE Linux operating systems.
| |
NOTE: |
Prior to beginning installation, verify that your /etc/hosts file has the local host name specified. It should
have an entry that looks like:
127.0.0.1 localhost
|
Before installing NetSight Console on a Linux platform, you need to:
Once your system is properly configured, you can proceed with:
The following procedures assume that the CD drive from which
you are installing is physically attached to the system where NetSight Console is being installed.
The user performing the installation must have privileges to create, read, write, and execute within the installation directory.
- Insert the NetSight Console CD into the CD drive.
- Use an xterm where you are logged in as root.
| |
NOTE: |
If you do not have a DISPLAY variable defined for your root user environment, you will encounter a Java exception during the install upon becoming the root user. Be sure that your system's root environment has a proper DISPLAY variable setting.
|
- Using the
cd command, cd to the /mnt/cdrom directory.
- Using the
ls command, check to see if the CD drive is mounted.
If no files are listed, issue the following commands:
mount /mnt/cdrom
- You can now launch the NetSight Console Installer (see Installing
NetSight Console (Linux)).
Now that you have prepared your Linux system for installation, you are ready to install Console.
- Use an xterm where you are logged in as root. (Be sure that your system's
root environment has a proper DISPLAY variable setting.)
- Start the Installer by issuing the appropriate command:
/mnt/cdrom/linux/install.bin
- The NetSight Console Installer leads you through a series of windows that ask you for
all the information required in order to install Console. You will need the following information to complete the
Installer Program:
- License -- This is a unique number assigned to your copy of NetSight Console. It is located on a label on your CD holder. Or you may choose to
install the NetSight Console Evaluation Copy.
- Destination Directory -- This is the path to your NetSight Console
Installation Directory. In the Destination Directory window, click Choose to
navigate to the directory, or type the path in manually.
When you have finished with this
series of windows, Console will be installed according to your
specifications.
Now that you've installed Console, you can launch it.
After you've launched Console for the first time, it is highly recommended that you select Help > Help Topics from the menu and
read the Welcome topic to review the Help system features and learn more about how to use NetSight Console.
You must start the NetSight Server and database prior to launching a Console Client.
The NetSight Server can be started using scripts in the <installdir>/server/ directory.
Start the server with the command:
<installdir>/server/startserver.sh
This starts the database, then starts the NetSight Server.
Then, you can launch the Console client:
- Use the
cd command to navigate to the NetSight Console Installation Directory.
- Issue the NetSight Console startup command:
./console
You must start the NetSight Server and
database prior to launching a Console Client.
The NetSight Server can be started using scripts in the <installdir>/server/ directory.
Start the server with the command:
<installdir>/server/startserver.sh
This starts the database, then starts the NetSight Server.
Then, you can launch the Console client:
- Use the
cd command to navigate to the NetSight Console Installation Directory.
- Issue the NetSight Console startup command:
./console
From the Start menu, select Programs > Enterasys Networks > NetSight Console > Console
Client. Evaluation Copy users only will see a
message indicating that this is an evaluation copy, and informing you
of the expiration date (90 days from date of installation). Click OK to continue.
Use the procedures below to uninstall Console. When you uninstall, only the files which were distributed with NetSight Console will be uninstalled. Files you generate (such as logs, FlexViews, device lists, and data files) will not be automatically uninstalled. Click here for a complete list of directories removed by uninstall.
If you have multiple versions of Console installed and are uninstalling, refer to the Co-existing Versions of Console section in the Release Notes for information and cautions.
You must stop NetSight Services, the NetSight Server and the NetSight database prior to uninstalling Console.
- Go to the Taskbar Notification Area of your desktop (on the lower right of your screen, unless you've relocated your Taskbar).
- Right-click the Services Manager icon (
) and select Stop running services to stop all NetSight Services that are currently running.
- Right-click again on the Services Manager icon and select Exit to shut down the Services Manager.
You can now uninstall Console:
From the Start menu, select Programs > Enterasys Networks > NetSight
Console > Uninstall NetSight Console.
You must stop NetSight Services, the NetSight Server and the NetSight database prior to uninstalling Console.
- Stop the NetSight Server and database:
- On the server system, navigate to the <installdir>/server
- Stop the server and database using the command: stopserver.sh
- Stop the NetSight Services:
- Navigate to the
etc/rc2.d directory.
- Stop the SNMP trap service using the command:
S99NsSnmptrapd stop
- Stop the TFTP service using the command:
S99NsTftp stop
- Uninstall Console.
- Navigate to the NetSight Console Installation Directory (top level).
- Start the Uninstaller by issuing the command:
./uninstallconsole
You must stop NetSight Services, the NetSight Server and the NetSight database prior to uninstalling Console.
When installed as a service on Red Hat Linux, the NetSight Server and database can be controlled using tools such as the
Red Hat Service Configuration Tool. Otherwise, use the following steps to stop the NetSight Services, Server and Database:
- Stop the NetSight Server and database:
- On the server system, navigate to the <installdir>/server
- Stop the server and database using the command: stopserver.sh
- Stop Services on all Linux systems except SuSE:
- Navigate to the
etc/rc2.d directory.
- Stop the SNMP trap service using the command:
S99NsSnmptrapd stop
- Stop the TFTP service using the command:
S99NsTftp stop
- Stop Services on SuSE Linux:
- Navigate to the
etc/init.d directory.
- Stop the SNMP trap service using the command:
NsSnmptrapd stop
- Stop the TFTP service using the command:
NsTftp stop
- Uninstall Console.
- Navigate to the NetSight Console Installation Directory (top level).
- Start the Uninstaller by issuing the command:
./uninstallconsole
Use the cd command to navigate to the NetSight Console
Installation Directory (top level). Start the Uninstaller by issuing the command:
./uninstallconsole
To locate product specific information, refer to the Enterasys website:
http://www.enterasys.com
After you have installed Console on your system, the full Help system is available
from the Help menu option on the Console windows, and from any window that has a Help
button on it. The online Help system is also available as a PDF file in the Help directory located in your NetSight Console installation directory.
If you need technical support related to NetSight Console,
contact the Enterasys Global Call Center:
Phone: (800) 872-8440 (24 hours a day, 365 days a year)
Email: support@enterasys.com
Mail:
Enterasys Networks, Inc.
Technical Support
50 Minuteman Rd.
Andover, MA 01810
FTP: ftp.enterasys.com
Login: anonymous
Password: [your email address]
BBS: 603-335-3358
Modem Setting: 8N1: 8 data bits, 1 stop bit, No parity
For the latest Enterasys documentation on the web, see http://www.enterasys.com/support/manuals/netsight.html.
For training on this and other Enterasys products, see http://www.enterasys.com/training.
Related Information
For release information: