04-06-2009
The error is pretty obvious.
ce1 interface went down and came up. Could be a network fluctuation or a cable defect(in which case these messages are bound to repeat).
If you are repeatedly getting this,try changing the network cable. If it persists even after that,try changing the network port in the switch.
Thanks
HG
9 More Discussions You Might Find Interesting
1. Solaris
i have ce0 and ce1 online, on 2 different networks. im getting a message that says one nic is trying to assume the others IP or something to thta effect.
I do ifconfig -a and i see they have the same mac.
How do i deal with this?
Solaris 9 i beleive 04/04
Thanks,
Brian (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
2. Solaris
Dear ALL,
my server give me messages like below:
Apr 20 21:33:09 TAISERVER in.routed: interface bge3 to 192.168.11.22 turned off
I check with ifconfig,but nothing error that,how can make it solve...thanks for your help. (7 Replies)
Discussion started by: fredginting
7 Replies
3. Solaris
Hi there. My first time posting so apologies for any indescretions in advance. :o I've got two SunFire V440 servers running Solaris 5v10. Both have a quad Gigabit ethernet card fitted, both have the same symptom; that is, I can't get the first port ce1 to run Gigabit. Motherboard ports are ce0 and... (10 Replies)
Discussion started by: fixit9660
10 Replies
4. Solaris
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies
5. SCO
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies
6. IP Networking
This is my situation
DOS pc serial cable (sl0) Linux Pc eth1
192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router)
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
... (3 Replies)
Discussion started by: mghis
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
How to check whether a Interface has a single port or dual port.Thanks in advance. (5 Replies)
Discussion started by: rama krishna
5 Replies
8. UNIX for Dummies Questions & Answers
Just wanted to understand what is the logic being used by Solaris(kernel) to transmit data/traffic on physical interfaces.
I have seen most of the time traffic is being sent to interface ce0 and sometime to ce1.
I have removed ip address from below command for some reason.
netstat -rn
... (3 Replies)
Discussion started by: nadeemahmed
3 Replies
9. UNIX for Dummies Questions & Answers
I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without... (1 Reply)
Discussion started by: westmoreland
1 Replies
DE(4) Kernel Interfaces Manual DE(4)
NAME
de - DEC DEUNA 10 Mb/s Ethernet interface
SYNOPSIS
/sys/conf/SYSTEM:
NDE de_controllers # DEUNA
DESCRIPTION
The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA).
Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The de interface employs the address resolution
protocol described in arp(4P) to dynamically map between Internet and Ethernet addresses on the local network.
The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is nego-
tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS
ioctl.
DIAGNOSTICS
de%d: hardware address %s. This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter.
de%d: oerror, flags=%b tdrerr=%b (len=%d). The hardware indicated an error in transmitting a packet to the cable. The status and error
flags are reported.
de%d: ierror, flags=%b lenerr=%b (len=%d). The hardware indicated an error in reading a packet from the cable. The status and error flags
are reported.
de%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
de%d: buffer unavailable. The interface received more packets than it had buffers allocated to receive them.
de%d: address change failed, csr0=%b csr1=%b. The interface was unable to reprogram its physical ethernet address. This may happen with
very early models of the interface. This facility is used only when the controller is not the first network interface configured for XNS.
The following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization.
The two control and status registers should indicate the nature of the failure. See the hardware manual for details.
de%d: reset failed, csr0=%b csr1=%b.
de%d: ppcb failed, csr0=%b csr1=%b.
de%d: read addr failed, csr0=%b csr1=%b.
de%d: wtring failed, csr0=%b csr1=%b.
de%d: wtmode failed, csr0=%b csr1=%b.
SEE ALSO
intro(4N), inet(4F), arp(4P)
3rd Berkeley Distribution August 20, 1987 DE(4)