Juniper STRM 2008-2 - TECHNICAL NOTE CHANGING NETWORK SETTING 6-2008 Manual
Changing network settings
Hide thumbs
Also See for STRM 2008-2 - TECHNICAL NOTE CHANGING NETWORK SETTING 6-2008:
- Troubleshooting tips (6 pages) ,
- Upgrade manual (5 pages) ,
- Using (4 pages)
Advertisement
Quick Links
Changing Network
Settings in an
All-in-One Console
Step 1
Step 2
Release 2008.2
J
N
UNIPER
T
ECHNICAL
C
N
HANGING
ETWORK
J
2008
UNE
This document provides information on changing network settings for the Console
and non-Console systems when using Trustix or CentOS-4 operating systems in
your deployment including:
•
Changing Network Settings in an All-in-One Console
•
Changing the Network Settings of a Console in a Multi-System Deployment
Changing the Network Settings of a Non-Console in a Multi-System
•
Deployment
Note: This Technical Note applies to systems running STRM 2008.2 and above.
You can change the network settings in your All-In-One system. An All-In-One
system has all STRM components, including the Administration Console, installed
on one system.
To change the settings on the STRM Console:
Note: You must have a local connection to your Console before executing the
script.
Log in to the Console, as root.
Enter the following command:
qchange_netsetup
The Configure STRM window appears.
ETWORKS
N
OTE
S
ETTINGS
STRM
Advertisement
Related Manuals for Juniper STRM 2008-2 - TECHNICAL NOTE CHANGING NETWORK SETTING 6-2008
Summary of Contents for Juniper STRM 2008-2 - TECHNICAL NOTE CHANGING NETWORK SETTING 6-2008
- Page 1 STRM UNIPER ETWORKS ECHNICAL HANGING ETWORK ETTINGS 2008 This document provides information on changing network settings for the Console and non-Console systems when using Trustix or CentOS-4 operating systems in your deployment including: • Changing Network Settings in an All-in-One Console •...
- Page 2 Using the up/down arrow keys to navigate the fields, change the necessary Step 3 parameters: • Hostname — Specify a fully qualified domain name as the system hostname. Note: If you change the hostname and you are using Offense Resolution, we recommend you also update the Resolver Agent name, if a Resolver Agent is assigned to the host.
- Page 3 Changing the Network Settings of a Console in a Multi-System Deployment Where is the IP address of the STRM system. <IP Address> Username: admin Password: <root password> Where is the password assigned to STRM during the <root password> installation process. In the main STRM Interface, click Config.
- Page 4 Public IP address is often configured using Network Address Translation (NAT) services on your network or firewall settings on your network. NAT translates an IP address in one network to a different IP address in another network. • Email Server - Specify the email server. If you do not have an email server, specify localhost in this field.
- Page 5 Changing the Network Settings of a Non-Console in a Multi-System Deployment Click Finish. Repeat for each non-Console managed host until all hosts are re-added and Step 8 re-assigned. From the Administrative Console menu, select Configurations > Deploy Step 9 Configuration Changes. Changes are deployed.
- Page 6 Note: If the Administration Console is still active on your system tray, use the right-mouse button (right-click) to access the menu and select Exit. Changes are deployed. Changing the To change the network settings, you must: Network Settings Log in to the non-Console as root. Step 1 Enter the following command: Step 2...
- Page 7 Changing the Network Settings of a Non-Console in a Multi-System Deployment Re-Adding the To re-add the managed host and re-assign component(s), you must: Managed Host and Re-Assigning the Components Log in to STRM and access the System View in the Deployment Editor, as defined Step 1 Step Removing the Non-Console Managed...
- Page 8 Copyright Notice Copyright © 2008 Juniper Networks, Inc. All rights reserved. Juniper Networks and the Juniper Networks logo are registered trademarks of Juniper Networks Inc. in the United States and other countries. All other trademarks, service marks, registered trademarks, or registered service marks in this document are the property of Juniper Networks or their respective owners.