I'm getting confused because during the install the interface was configured automatically with DHCP, then the eri0 get a DHCP address too (I want both interfaces UP and in diferent networks, the eri will be the management interface and the ge will the interface the clienst will access it) and after that the ge interface stopped working.
Last edited by pxb368@motorola; 06-15-2012 at 02:09 PM..
I am trying to change an IP address on a machine running HPUX10
After I change it I can ping it from the outside but it completely locks the console. After a reboot it returns back to its previous IP. Any ideas??
Thanks
Brian (7 Replies)
I know that I could use the
#ifconfig hme0 plumb
to activate the network interface.
However, how can I know the name of the interface e.g. hme0 before I could use the ifconfig to plumb it up?
I know there is a command (but I forgot it) to use in the Sparc version when you are in the... (7 Replies)
why the ifconfig command is not working in my machine?
it says "-bash: ifconfig: command not found"
why its says that?
actually i m looking for "how can I know the Network Interface Card physical address?"
Requesting u all for help.
thanks (3 Replies)
Hello everyone.
Im using last redhat enterprise edition and in my working environment, i'm always reconfiguring both interfaces , eth0 and eth1, everytime i change any interface, (i use ifconfig to change ip, and after i execute "/etc/init.d/network restart") my "/etc/hosts" file... (9 Replies)
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Hi All,
I need some info on ifconfig.
ifconfig is available in Linux and Solaris. However the options available in Solaris is not there in Linux.
1. ifconfig -a == output is different in both OS. I am somewhat able to compare the output. But one thing I am not getting is after the flags... (2 Replies)
Unable to run the ifconfig in my home dir..
I did add adding /sbin and /usr/sbin in th PATH
But still unable to get that ..
Am using red hat linux
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.3 (Tikanga) (3 Replies)
What would be the command to remove the IP address from an interface?
I want to remove the ip from this interface:
ce3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
inet 155.216.13.74 netmask fffffff0 broadcast 155.216.13.79
ether 0:3:ba:da:a6:96 (3 Replies)
Hiii folks,,
I am unable to configure NIC using hme0 command. I am getting an error message as "hme0: File or directory not found.."
can someone help me...
Bhagi... (9 Replies)
Discussion started by: bhargav90
9 Replies
LEARN ABOUT V7
dhcp
dhcp(5) Standards, Environments, and Macros dhcp(5)NAME
dhcp - Dynamic Host Configuration Protocol
DESCRIPTION
Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
boot. DHCP uses a client/server mechanism: servers store configuration information for clients, and provide that information upon a
client's request. The information can include the client's IP address and information about network services available to the client.
This manual page provides a brief summary of the Solaris DHCP implementation.
Solaris DHCP Client
The Solaris DHCP client is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
during boot. Network parameters needed for system configuration during bootup are extracted from the information recieved by the daemon
through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the /etc/default/dhc-
pagent file. The daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
commands.
Solaris DHCP Server
The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration information to
either BOOTP or DHCP clients. The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
fig(1M), dhtadm(1M), and pntadm(1M).
DHCP Configuration Tables
The Solaris DHCP server stores client configuration information in the following two types of tables:
dhcptab tables Contain macros and options (also known as symbols), used to construct a package of configuration information to
send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about the
syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.
DHCP network tables DHCP network tables, which contain mappings of client IDs to IP addresses and parameters associated with those
addresses. Network tables are named with the IP address of the network, and can be created, viewed, and modified
using the pntadm command or dhcpmgr graphical utility. See dhcp_network(4) for more information about network
tables.
SEE ALSO dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M), dhtadm(1M), ifconfig(1M), in.dhcpd(1M), netstat(1M), pntadm(1M), syslog(3C),
dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)
Solaris DHCP Service Developer's Guide
Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.
Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell University. March 1997.
Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.
SunOS 5.10 13 Mar 2001 dhcp(5)