Sponsored Content
Full Discussion: Solaris - Assign Static IP
Operating Systems Solaris Solaris - Assign Static IP Post 302420748 by angshuman_ag on Wednesday 12th of May 2010 10:46:12 AM
Old 05-12-2010
Quote:
Originally Posted by pupp
basically yes.

however, you may have communication issues if you do not configure other network specific files such as what jlliagre said.

1. Can you please provide me a detail on that too ?
2. Also, I would like to change my hostname too ?

And, all settings should be preserved once I reboot the system.
 

10 More Discussions You Might Find Interesting

1. Solaris

Setting up static ip-adresses, Solaris 10

Hello, Iam having problems getting more then one ip to work here is my setup! Hostname: nexus NIC: e000g1 (example ips) My ips 80.80.80.15 to 80.80.80.20 Defaultrouter 80.80.80.1 nameservers 80.80.80.100 and 80.80.80.200 How would i do this? Any help would be mutch appriciated!... (7 Replies)
Discussion started by: empty
7 Replies

2. Solaris

Basic Solaris static routing

Hi All, :(:confused: I have scoured the web and can't find this anywhere. What I am trying to do is set up a static route through an available gateway on a server, and then test connectivity through TELNET. I have done this on AIX (I already had this procedure). On AIX I would use SMIT. ... (7 Replies)
Discussion started by: jeffpas
7 Replies

3. Solaris

how to assign the rights to groups in solaris

Hi, how to assign the rights(admin,..) to groups . I can create group using groupadd. but i don't know how to assign rights and adding members please tell me how to do that Thank you (2 Replies)
Discussion started by: S_venkatesh
2 Replies

4. Solaris

How to assign MAC address to N/W interface in solaris

I m having interface ce0 ce1 and its sub interfaces for that. I want to give MAC addresses for the same. How will I assign it. Please give solution for the same (4 Replies)
Discussion started by: sunray
4 Replies

5. IP Networking

I need HELP to Set up Coyote Linux router with 1 static IP & 64 internal static IP

hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first. ... (0 Replies)
Discussion started by: dlwoaud
0 Replies

6. UNIX for Dummies Questions & Answers

Static IP address for solaris 10 virtual machine

Hi All I am having a solaris 10 virtual machine on vista (using vmware 7) laptop. Now i want to access virtual machine from vista using putty. Problem is that i insalled the solaris machine as dhcp. and whenever i connect to internet or reboot my system the IP address of solaris... (1 Reply)
Discussion started by: ankurk
1 Replies

7. Solaris

How to assign static ip address to the server having solaris 10. i.e. nge0

hi, how to assign static ip address to the server having solaris 10. assign static ip to nge0 which will sustain across reboots which will include all settings including gateway setting etc.. (2 Replies)
Discussion started by: pankajd
2 Replies

8. Programming

Even the Static cURL Library Isn't Static

I'm writing a program which uses curl to be run on Linux PCs which will be used by a number of different users. I cannot make the users all install curl on their individual machines, so I have tried to link curl in statically, rather than using libcurl.so. I downloaded the source and created a... (8 Replies)
Discussion started by: BrandonShw
8 Replies

9. Solaris

Solaris 11 problem with static ip

I have installed Solaris 11.2 in VMware Player, networked in bridged mode. When Solaris uses DHCP everything is OK, I can reach internet, as well as other systems on my LAN. When I switch to static, I have connections to my LAN, but can not get to internet, the DNS resolution is somehow not... (2 Replies)
Discussion started by: migurus
2 Replies

10. Solaris

Solaris static IP changed (non DHCP)

We have 2 solaris 10 t5240 servers with static IP addresses on nxge0 I/F which were rebooted a few days back with a known good config that has been in place for years (for /etc/hosts, /etc/hostname.nxge0, /etc/netmasks, etc) They are not using dhcp. About the same time today, both of their... (7 Replies)
Discussion started by: hdatontodo
7 Replies
set_parms(1M)															     set_parms(1M)

NAME
set_parms - set system initial identity parameters: hostname, date/time, root password, and networking SYNOPSIS
DESCRIPTION
The command is an interactive system set-up command that allows you to specify various "initial identity parameters" when first booting a newly installed operating system (whether preinstalled, or installed locally from media or an install server), and to revise these parame- ters later on a running system. Initial identity parameters are a minimal set of values required to bring a system to an initially useful state. They include the following: o system hostname o timezone for the system's location o date and time o root password o IP address, netmask o routemask, routing gateway, DNS, and NIS information o local language In a first-boot situation, is invoked automatically by For purposes, "first-boot" is defined as having no hostname set when the system starts up. This causes to step through all of its sub-areas to help you set all of the initial identity parameters. After the system has booted and is running, may also be called directly from the command line to step through all areas (via similar to how it works at first-boot, or to finish setting up a particular sub-area (the latter forms above). There are certain limitations to its actions when it's run after first-boot, as described see below. Note: The command only sets the root (superuser) password during "initial" processing, and then only if it is not already set. If so, it uses the command, so the effect is immediate. See the passwd(1) manpage. The command is also DHCP-aware. If you attempt to change DHCP-supplied data such as the hostname or IP address, issues a warning. If you continue with the changes, relinquishes the DHCP lease. On first-boot, asks if you would like to try getting set-up data from a DHCP server. However invoked, the command often knows and provides default values for many of the initial identity parameters, based on values specified to Ignite-UX in a previous or recent installation of the system or found in system configuration files. The command can be run only by the user with appropriate privilege. Options Each sub-area of is described below. In a first-boot situation all of the sub-areas are run sequentially. Special first-boot behavior is noted below if applicable, along with any special cases when invoking on a running system. When calling a sub-area directly, only a unique portion of the sub-area name is required to be given; for example, This allows the user to sequentially invoke all the sub-areas mentioned below. The user can configure multiple interfaces which are physically connected to the network using the Termi- nal User Interface (TUI). A in the user interface field indicates a lan which is not physically connected to the network. If lan interfaces are configured as DHCP, the options and are skipped. Set the system hostname: Validates a user-supplied hostname according to host-naming conventions and sets various system initialization variables to operate with that hostname. Particularly, edits to associate the new hostname with the current IP address of the system, if that can be determined. Note: It does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. WARNING: When changing the hostname, does not know about optionally-installed software. If any such software remembers the previous hostname, it might not work properly after the hostname is changed. A mechanism is provided that helps generalize the hostname changing function. The command calls, in sorted order, any exe- cutable commands found in the directory This occurs for both first-boot and non-first-boot calls. HP may in the future sup- ply special commands in this location. The system administrator may also supply custom commands (programs or scripts) for site installations using, for example, Ignite-UX. The system must be rebooted for any change to take full effect. Select a timezone based on your country of location. Also allows you to set a user-supplied timezone. The system must be rebooted for any change to take effect. Set the system date and time interactively: This is similar to calling as a privileged user, but without having to format a time specification string. The change takes effect immediately. Set or change the IP address and subnet mask for the system. This function edits the file to associate the new IP address with the current hostname. Note: it does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. If multiple lan interfaces are present, the user can select each LAN interface (network interface card or NIC) separately to configure it. The system must be rebooted for any change to take effect. Set the route mask (which defines the network and local subnet portions of a network address), set the routing gateway, and define access to the Domain Name System (DNS) and Network Information Service (NIS). First-boot: These changes take effect immediately, without a reboot, because starts networking after setting the parameters. Non-first-boot: A reboot is required for all of these changes to take effect. Allow the user to set the local language settings. The user can either select one of the languages from the menu or they can set new valid language. will verify whether the new language is installed. If it is not installed, the user must install the language before executing this option. set_parms, Ignite-UX or Cold Install After "cold-installing" HP-UX from tape, CD-ROM, or DVD, or using Ignite-UX to install HP-UX from any source including an install server, the file is generally left on the system. This file is used to communicate to and other tools the hostname, networking, and other informa- tion that was used during the installation, to make it easier to use any of these values as final system parameters. In particular, uses as defaults the shell-style variables in this file that begin with For example, indicates which LAN interface was used during a network cold install. This is the LAN interface that configures. In general, first looks in for default information, then in the system configuration files in the directory. If any parameter is defined in both locations, the latter takes precedence. If Ignite-UX is installed on your system, see the manpage entries for ignite(5) and instl_adm(4). In particular, read instl_adm(4) for descriptions of the and variables. Interaction with auto_parms During the boot-up sequence, always invokes which in turn detects the first-boot situation and it calls if either or both of these condi- tions are true. The starts its interface and, based on user input, might call back into to obtain and set up the management of a DHCP lease. After completes this and other system set-up tasks, control passes back to which completes the boot-up sequence using the newly- created system initial identity parameters. See the rc(1M) manpage for information about for invocation context in the first-boot case. If the system has multiple lan interfaces and the user wishes to configure some with DHCP and others with static IP, the user must invoke first to configure all the lan interfaces which they wish to configure as DHCP. The user should not allow the system to be rebooted while doing this configuration. Then the user should invoke to configure the remaining lan interfaces. also allows the user to specify the DHCP server from which to get hostname and networking parameters and Class ID. If multiple interfaces are configured with DHCP, there is a chance that multiple hostnames will be returned through different DHCP enabled lan interfaces. If hostname is not set in and none of the interfaces are configured with addresses, then the hostname returned by the interface is updated in FILES
The command itself. Common subroutines used by and the sub-area commands. Directory holding all of sub-area commands called by which runs them in sorted order. Directory containing any hostname-change commands defined by the user. These are standalone commands run, in sorted order, by when setting or changing the hostname. File set by Ignite-UX or Cold Install that contains networking and other system information used during the installation. System configuration files modified by AUTHOR The command was developed by HP. SEE ALSO
passwd(1), auto_parms(1M), dhcpdb2conf(1M), rc(1M), instl_adm(4), ignite(5). set_parms(1M)
All times are GMT -4. The time now is 03:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy