12-20-2012
When we had physical servers, we had the same error and it ended up being caused by our switch being configured to 1000 full and our adapter was set to auto/auto. Once we changed our adapter settings, the error went away.
Also, look in your rc.net and rc.tcpip for any special customizations. We had one server with an "/usr/sbin/ifconfig..." line in it that should not have been there.
10 More Discussions You Might Find Interesting
1. Linux
Hi,
I try to unmount :
smbumount /mnt/directory
But I receive :
Could not umount /mnt/directory: Device or resource busy
Any idea ?
Many thanks. (4 Replies)
Discussion started by: big123456
4 Replies
2. Filesystems, Disks and Memory
Hi...
Is it possible to re-export a exported NFS file system? If no, Why?
Let me know, if any further details are required about the question.
Thanks in advance
Adams:) (5 Replies)
Discussion started by: Adams Nave
5 Replies
3. AIX
I create a NFS file system. I can read this system from client, however, I cannot write anything in this folder. Why? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
4. AIX
Hello,
Can someone please point to an easy document or steps how to export AIX file system /whatever to Windows O/S
Basically Windows should see this filesystem / directory and should be able to write in this filesystem / directory
Thanks (2 Replies)
Discussion started by: filosophizer
2 Replies
5. AIX
Hi,
I want to change the values for shared file system in aix for that I have run the command smitty chnfsexp but I am not getting the all the values which I have seen while adding the file system while exporting
example
smitty chnfsexp
but after selecting shared file system using F4... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
6. UNIX for Dummies Questions & Answers
Hi, suppose I have file system path say /foo/bar/baz then how would I find out whether it is local file system or NFS? If it is NFS then I want to find out the host where file system is located.
Thanks,
Paresh (5 Replies)
Discussion started by: masaniparesh
5 Replies
7. AIX
hello,
i am trying to export a file system so that i can mount it on NIM server and make mksysb backup of the server on that fs.
i get this message:
mount: 1831-011 access denied for s_semdev:/dr_s_zeus/mksysb/dr_s_zeus
mount: 1831-008 giving up on:
s_semdev:/dr_s_zeus/mksysb/dr_s_zeus ... (5 Replies)
Discussion started by: omonoiatis9
5 Replies
8. UNIX for Dummies Questions & Answers
Hi,
as title says
what happens if i unmount local file system when is mounted to a diffrent server ? (2 Replies)
Discussion started by: galuzan
2 Replies
9. AIX
Hello Guru's
We are trying to save some data for 10 -15 yrs. so we created a NFS share file system and mounted on AIX 5.3 servers, keeping in mind that we might need to replace the expired disk/bad disk every 2 yrs or 4 yrs.
Now we are trying to solve. How to protect it from getting deleted... (6 Replies)
Discussion started by: Beginner123
6 Replies
10. AIX
Right, now that I've finally worked out this website, I'll ask my question!
I am having an absolute nightmare with NFS on AIX. I have used it many times, and I know what I'm doing, however I cannot fathom what is going on here. I have 2 LPARs, sitting on the same physical host. They are... (12 Replies)
Discussion started by: tmooredba
12 Replies
fza(4) Kernel Interfaces Manual fza(4)
Name
fza - DEFZA FDDI Network Interface
Syntax
device fza0 at ibus? vector fzaintr
Description
The interface is a high speed TURBOchannel bus to a 100 Mbit/second Fiber Distributed Data Interface (FDDI) timed token ring network
adapter. The interface allows the host system to be an FDDI single attachment station.
The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The interface employs the address resolution protocol
described in to map dynamically between Internet and FDDI addresses on the local network.
The maximum frame size for the interface is 4500 bytes, which is substantially larger that the 1500 bytes maximum packet size of the Ether-
net interfaces. The interface does not support the BSD trailer encapsulation, which is specific to the VAX architecture.
The SIOCRPHYSADDR ioctl can be used to read the physical address of the DEFZA adapter. The physical address of the DEFZA adapter can not be
changed.
The SIOCADDMULTI and SIOCDELMULTI ioctls can be used to add or delete multicast addresses. The DEFZA supports up to 64 multicast
addresses.
The SIOCRDCTRS ioctl can be used to read the FDDI driver counters. The DEFZA adapter status and characteristics can also be read through
this ioctl by providing a FDDI_STATUS flag . The argument to this ioctl is a pointer to a counter or status structure, found in <net/if.h>.
The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode, respectively.
The SIOCEEUPDATE ioctl can be used to update the adapter's firmware.
The SIOCIFRESET ioctl can be used to reset the adapter.
Diagnostics
Diagnostic error messages contain information provided by the driver. For example:
fza%d: fzaprobe selftest failed
The DEFZA adapter did not pass the power-up selftest during autoconfiguration.
fza%d: port init failed
The DEFZA adapter cannot be initialized.
fza%d: port in the Halt State -> CNS hardware fault
The DEFZA adapter went to the Halt state because of an adapter firmware fault.
fza%d: LINK unavailable
The network link went down which means that the station is not on the FDDI ring.
fza%d: Ring Init Received
A Ring Initialization unsolicited event has been received from the fza%d interface.
See Also
arp(4p), inet(4f), intro(4n)
fza(4)