02-25-2012
Are you using Solaris 10 or 11?
Have you tried assigning a different IP to the NIC? Are you sure that the IP configurations are persistent over a reboot? I am asking this as you may setup NIC using ifconfig. But the changes are not written on files. So when network/physical service tries to read the files, it does not get the updated info. Meanwhile, you can ping, etc. without any issue.
---------- Post updated at 02:56 PM ---------- Previous update was at 02:54 PM ----------
By the way, the other services will automatically start to run (if they are already enabled) once the network/physical service gets online.
9 More Discussions You Might Find Interesting
1. Cybersecurity
Hi all
I am facing some problem with network card
i am using solaris8 and on sunultra10 .As it is my firewal machine i have got on backup harddisk for any emergency.
In one hardidsk while installation only hme0 interface was configured and in the backup hard disk qfe0/hme0 both are... (0 Replies)
Discussion started by: Prafulla
0 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I need explanations about physical disks and physical volumes. What is the difference between these 2 things?
In fact, i am trying to understand what the AIX lspv2command does.
Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies
3. Solaris
How do you test the physical network connection of an interface in solaris. I know that if you have an active connection and the cable gets yanked, you can look in the messages file to check for link failure messages. But is there any better way to see if you have good layer 2 connectivity? (1 Reply)
Discussion started by: tjlst15
1 Replies
4. UNIX for Dummies Questions & Answers
I was in smit, checking on disc space, etc. and it appears that one of our physical volumes that is part of a large volume group, has no free physical partitions. The server is running AIX 5.1. What would be the advisable step to take in this instance? (9 Replies)
Discussion started by: markper
9 Replies
5. AIX
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Discussion started by: jenish_shah
1 Replies
6. Solaris
Hello Friends,
I need to change network filesystem status as online but it always seems in maintenance mode, I appreciate your any suggestion to change its state as online.
shell>svcadm enable svc:/system/filesystem/local
shell>svcs -l svc:/system/filesystem/local
fmri ... (4 Replies)
Discussion started by: EAGL€
4 Replies
7. Solaris
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies
8. Solaris
Dear All,
http:apache2 service on my node is continuously in maintenance mode.
I have tried to enable and disable the service but nothing works.
root@ops # svcs -a | grep apache2
maintenance 15:46:37 svc:/network/http:apache2
When I reboot the system, I get the following error:
... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
9. Solaris
All I'm running an OpenSolaris system (Nexenta). When doing a svcs I see that/network/smb/server is in maintenance mode.
I have run a clear on the service and restarted. I see the same service show online* for a bit but then, enters maintenance every time.
In the service log I... (2 Replies)
Discussion started by: dcpatriot
2 Replies
LEARN ABOUT NETBSD
eshconfig
ESHCONFIG(8) BSD System Manager's Manual ESHCONFIG(8)
NAME
eshconfig -- configure Essential Communications' HIPPI network interface
SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface]
DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI
network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to
achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update
that firmware.
Available operands for eshconfig:
-b bytes
Adjust the burst size for read (by NIC of host memory) DMA.
-c bytes
Adjust the burst size for write (by NIC of host memory) DMA.
-d filename
Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every
line, and a tag line at the end indicating the characteristics of the firmware file.
-e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter
ensures that the changes will be written to EEPROM.
-i usecs
Interrupt delay in microseconds.
-m bytes
Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents
one direction from dominating the flow of bytes, and artificially throttling the NIC.
-r bytes
Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are
requested, the DMA will not begin.
-s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics.
-t Show current tuning parameters on the host.
-u filename
Name of file to which the NIC firmware should be uploaded. Not currently supported.
-w bytes
Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will
not start.
-x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter-
faces goes up and down.
Only the super-user may modify the configuration of a network interface.
DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration.
SEE ALSO
esh(4), ifconfig(8)
HISTORY
The eshconfig command first appeared in NetBSD 1.4.
BSD
June 17, 2005 BSD