Rsh disconnect problems in Solaris 10

My company uses rsh to transmit data to proprietary cards, from Ultra 25's running Solaris 10. We're experiencing random timeouts. The error is rsh connection timeout.
We never had this problem on Solaris 8 or Solaris 7.
Has anyone run across this before? It's to random to run snoop on. Thanks Mark

type passwd mgcusr as root. then you'll need to type new password for that user.

Similar Messages

Content Server 6.0 Installation problem on Solaris

When I installed Content_Server_6.0_SP1_solaris_oracle on Solaris 10 ,I get the following error in log file.
dbg Bundled JRE is not binary compatible with host OS/Arch or it is corrupt. Testing bundled JRE failed.
How can I resolve it
please help me.
Regards
Sandeep

If I installed any installer for sparc Machine on x86.is there any problem.My Solaris machine is x86.
thanx.
Regards
Sandeep.

Focus Problem on Solaris with jdk 1.3.1

Hi all,
We are having a focus problem on Solaris. The same code works fine on Windows without any problem.
I am sending the test code and run steps below which you can compile and repeat the problem.
NOTE: When we put a comment on the line "f1.requestFocus();" in TestFocus.java it works OK.
Run Steps :
1. Run TestFocus.class
2. A JFrame appears with 2 text field and a button
3. Try to write something on the text fields. It works OK.
4. Click the button to open a new JFrame
5. A new JFrame opens with a single text field and a button.
6. Click the button to close the second frame
7. You are now on the main JFrame
8. Try to write something on the text fields. It works OK.
9. Repeat the steps 4-7
10. Try to write something on the text fields. You are able to focus and write on the first field. BUT you cannot select or write the second Field!
JAVA SOURCE FILES :
PenHesapListener.java :
public interface PenHesapListener extends java.util.EventListener {
void tamam_actionPerformed(java.util.EventObject newEvent);
void iptal_actionPerformed(java.util.EventObject newEvent);
------PenHesapLisEventMulticaster.java----------------------------------
public class PenHesapLisEventMulticaster extends java.awt.AWTEventMulticaster implements PenHesapListener {
* Constructor to support multicast events.
* @param a java.util.EventListener
* @param b java.util.EventListener
protected PenHesapLisEventMulticaster(java.util.EventListener a, java.util.EventListener b) {
     super(a, b);
* Add new listener to support multicast events.
* @return muhasebe.HesappenListener
* @param a muhasebe.HesappenListener
* @param b muhasebe.HesappenListener
public static PenHesapListener add(PenHesapListener a, PenHesapListener b) {
     return (PenHesapListener)addInternal(a, b);
* Add new listener to support multicast events.
* @return java.util.EventListener
* @param a java.util.EventListener
* @param b java.util.EventListener
protected static java.util.EventListener addInternal(java.util.EventListener a, java.util.EventListener b) {
     if (a == null) return b;
     if (b == null) return a;
     return new PenHesapLisEventMulticaster(a, b);
* @return java.util.EventListener
* @param oldl muhasebe.HesappenListener
protected java.util.EventListener remove(PenHesapListener oldl) {
     if (oldl == a) return b;
     if (oldl == b) return a;
     java.util.EventListener a2 = removeInternal(a, oldl);
     java.util.EventListener b2 = removeInternal(b, oldl);
     if (a2 == a && b2 == b)
          return this;
     return addInternal(a2, b2);
* Remove listener to support multicast events.
* @return muhasebe.HesappenListener
* @param l muhasebe.HesappenListener
* @param oldl muhasebe.HesappenListener
public static PenHesapListener remove(PenHesapListener l, PenHesapListener oldl) {
     if (l == oldl || l == null)
          return null;
     if(l instanceof PenHesapLisEventMulticaster)
          return (PenHesapListener)((PenHesapLisEventMulticaster) l).remove(oldl);
     return l;
public void tamam_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).tamam_actionPerformed(newEvent);
     ((PenHesapListener)b).tamam_actionPerformed(newEvent);
public void iptal_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).iptal_actionPerformed(newEvent);
     ((PenHesapListener)b).iptal_actionPerformed(newEvent);
---------TestFocus2.java-----------------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
public class TestFocus2 extends JFrame implements ActionListener
     protected transient PenHesapListener PenhListener = null ;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus2()
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               fireTamam_actionPerformed(e);
     public void addPenHesapListener(PenHesapListener newListener)
          PenhListener = PenHesapLisEventMulticaster.add(PenhListener, newListener);
          return;
     protected void fireTamam_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.tamam_actionPerformed(newEvent);
          this.setVisible(false);
     protected void fireiptal_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.iptal_actionPerformed(newEvent);
     public static void main(String x[])
          TestFocus2 gen01 = new TestFocus2();
--------TestFocus.java-----------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
import java.awt.Container;
public class TestFocus extends JFrame implements ActionListener
     PenKreKart aPenKreKart = null ;
     Container ctn = null;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JTextField f2 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus()
          //aPenKreKart = new PenKreKart(true);
          //aPenKreKart.aTemelPencere.setVisible(false);
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(f2);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               pencere_islemi();
     // pencere koyma k?sm? .. begin
     public void pencere_islemi() {
          ctn = this;
          ctn.setEnabled(false);
          TestFocus2 fpen = new TestFocus2();
          //aPenKreKart.aTemelPencere.setVisible(true); //buras?
          //aPenKreKart.aTemelPencere.addPenHesapListener(new PenHesapListener() {
          fpen.addPenHesapListener(new PenHesapListener() {
                    // metod      tamam_actionPerformed begin...
                    public void tamam_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         // Problem is when we comment the below line it works .....
                         f1.requestFocus();
                         System.out.println("tamam");
                    // metod      tamam_actionPerformed end...
                    // metod      iptal_actionPerformed begin...
                    public void iptal_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         System.out.println("iptal");
                    // metod      iptal_actionPerformed begin...
     // pencere koyma k?sm? .. end
     public static void main(String x[])
          TestFocus gen01 = new TestFocus();

Hi all,
We are having a focus problem on Solaris. The same code works fine on Windows without any problem.
I am sending the test code and run steps below which you can compile and repeat the problem.
NOTE: When we put a comment on the line "f1.requestFocus();" in TestFocus.java it works OK.
Run Steps :
1. Run TestFocus.class
2. A JFrame appears with 2 text field and a button
3. Try to write something on the text fields. It works OK.
4. Click the button to open a new JFrame
5. A new JFrame opens with a single text field and a button.
6. Click the button to close the second frame
7. You are now on the main JFrame
8. Try to write something on the text fields. It works OK.
9. Repeat the steps 4-7
10. Try to write something on the text fields. You are able to focus and write on the first field. BUT you cannot select or write the second Field!
JAVA SOURCE FILES :
PenHesapListener.java :
public interface PenHesapListener extends java.util.EventListener {
void tamam_actionPerformed(java.util.EventObject newEvent);
void iptal_actionPerformed(java.util.EventObject newEvent);
------PenHesapLisEventMulticaster.java----------------------------------
public class PenHesapLisEventMulticaster extends java.awt.AWTEventMulticaster implements PenHesapListener {
* Constructor to support multicast events.
* @param a java.util.EventListener
* @param b java.util.EventListener
protected PenHesapLisEventMulticaster(java.util.EventListener a, java.util.EventListener b) {
     super(a, b);
* Add new listener to support multicast events.
* @return muhasebe.HesappenListener
* @param a muhasebe.HesappenListener
* @param b muhasebe.HesappenListener
public static PenHesapListener add(PenHesapListener a, PenHesapListener b) {
     return (PenHesapListener)addInternal(a, b);
* Add new listener to support multicast events.
* @return java.util.EventListener
* @param a java.util.EventListener
* @param b java.util.EventListener
protected static java.util.EventListener addInternal(java.util.EventListener a, java.util.EventListener b) {
     if (a == null) return b;
     if (b == null) return a;
     return new PenHesapLisEventMulticaster(a, b);
* @return java.util.EventListener
* @param oldl muhasebe.HesappenListener
protected java.util.EventListener remove(PenHesapListener oldl) {
     if (oldl == a) return b;
     if (oldl == b) return a;
     java.util.EventListener a2 = removeInternal(a, oldl);
     java.util.EventListener b2 = removeInternal(b, oldl);
     if (a2 == a && b2 == b)
          return this;
     return addInternal(a2, b2);
* Remove listener to support multicast events.
* @return muhasebe.HesappenListener
* @param l muhasebe.HesappenListener
* @param oldl muhasebe.HesappenListener
public static PenHesapListener remove(PenHesapListener l, PenHesapListener oldl) {
     if (l == oldl || l == null)
          return null;
     if(l instanceof PenHesapLisEventMulticaster)
          return (PenHesapListener)((PenHesapLisEventMulticaster) l).remove(oldl);
     return l;
public void tamam_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).tamam_actionPerformed(newEvent);
     ((PenHesapListener)b).tamam_actionPerformed(newEvent);
public void iptal_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).iptal_actionPerformed(newEvent);
     ((PenHesapListener)b).iptal_actionPerformed(newEvent);
---------TestFocus2.java-----------------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
public class TestFocus2 extends JFrame implements ActionListener
     protected transient PenHesapListener PenhListener = null ;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus2()
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               fireTamam_actionPerformed(e);
     public void addPenHesapListener(PenHesapListener newListener)
          PenhListener = PenHesapLisEventMulticaster.add(PenhListener, newListener);
          return;
     protected void fireTamam_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.tamam_actionPerformed(newEvent);
          this.setVisible(false);
     protected void fireiptal_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.iptal_actionPerformed(newEvent);
     public static void main(String x[])
          TestFocus2 gen01 = new TestFocus2();
--------TestFocus.java-----------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
import java.awt.Container;
public class TestFocus extends JFrame implements ActionListener
     PenKreKart aPenKreKart = null ;
     Container ctn = null;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JTextField f2 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus()
          //aPenKreKart = new PenKreKart(true);
          //aPenKreKart.aTemelPencere.setVisible(false);
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(f2);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               pencere_islemi();
     // pencere koyma k?sm? .. begin
     public void pencere_islemi() {
          ctn = this;
          ctn.setEnabled(false);
          TestFocus2 fpen = new TestFocus2();
          //aPenKreKart.aTemelPencere.setVisible(true); //buras?
          //aPenKreKart.aTemelPencere.addPenHesapListener(new PenHesapListener() {
          fpen.addPenHesapListener(new PenHesapListener() {
                    // metod      tamam_actionPerformed begin...
                    public void tamam_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         // Problem is when we comment the below line it works .....
                         f1.requestFocus();
                         System.out.println("tamam");
                    // metod      tamam_actionPerformed end...
                    // metod      iptal_actionPerformed begin...
                    public void iptal_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         System.out.println("iptal");
                    // metod      iptal_actionPerformed begin...
     // pencere koyma k?sm? .. end
     public static void main(String x[])
          TestFocus gen01 = new TestFocus();

Metainit/striping problem on Solaris 9

We are trying to deploy the Apple XServe RAIDS to customers running Solaris 9. The issue is that Solaris 9 will not recognize a device/LUN that is > 2TB. (No problem with Solaris 10) In trying to solve this problem, we sliced a 7 disk (4.09 TB) RAID into 3 slices. This presents three 1.36TB disks to the Solaris system. Basically, we have 6 disks being presented across both controllers to Solaris. They are direct connected from the XServe to a dual port QLogic HBA. The problem comes in when you try to create a stripe/concatenation across the logical devices being presented. (The disks are being presented on C4 and C5)
Results from a format AFTER I split both 7 disk RAID5s into 3 slices.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@3,0
4. c4t600039300001F461d0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,0
5. c4t600039300001F461d1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,1
6. c4t600039300001F461d2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,2
7. c5t600039300001F2ECd0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,0
8. c5t600039300001F2ECd1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,1
9. c5t600039300001F2ECd2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,2
Specify disk (enter its number):
Results of the cfgadm command. You will see there three logical devices presented to each controller. Six disks.
cfgadm -al -o showFCPdev
Ap_Id Type Receptacle Occupant Condition
c4 fc-private connected configured unknown
c4::600039300001f461,0 disk connected configured unknown
c4::600039300001f461,1 disk connected configured unknown
c4::600039300001f461,2 disk connected configured unknown
c5 fc-private connected configured unknown
c5::600039300001f2ec,0 disk connected configured unknown
c5::600039300001f2ec,1 disk connected configured unknown
c5::600039300001f2ec,2 disk connected configured unknown
Trying to initialize a 6 device stripe via Solaris Volume Manager (AKA disksuite)
metainit -f d77 6 1 c4t600039300001F461d0s0 1 c4t600039300001F461d1s0 1 c4t600039300001F461d2s0 1 c5t600039300001F2ECd0s0 1 c5t600039300001F2ECd1s0 1 c5t600039300001F2ECd2s0
I receive the following error:
metainit: hostname: c4t600039300001F461d1s0: overlaps with device in d77
I tried to do a work around where I create three striped devices then concatenate them:
Creating the first 2 device stripe across controllers c4 and c5 (1 device each)
metainit -f d77 2 1 c4t600039300001F461d0s0 1 c5t600039300001F2ECd0s0
I was able to create the first metadevice d77 using one logical LUN from each controller.
When I tried to create a second metadevice across the controllers: (Using d1 from each controller)
metainit -f d78 2 1 c4t600039300001F461d1s0 1 c5t600039300001F2ECd1s0
metainit: hostneme: c4t600039300001F461d1s0: overlaps with device in d77
I received the same error.
In doing some reaearch, it seems the problem is due to a problem with the disk duplication process, disk device IDs stored on the disks are not unique. I was curious if this is the problem that Apple presents the split disks with the SAME diskid? Has anybody else successfully created stripes (due to a LUN size limit) across the disk successfully on a Solaris system?

I contacted Sun and here is an explination from them. I also noticed when I queried the Xserver RAIDS, there were no serial numbers.
Solaris 9 can support a 16Tb filesystem, but there is a scsi limitation on the device of 2Tb. So you are stuck with striping together several smaller devices if you want a single filesystem above 2Tb.
The problem you are having when metainit reports an overlap comes from the way Solaris Volume Manager identifies devices. The portion of the scsi inquiry that is returned is always unique when Sun firmware is involved, but in your case is not unique.
You may be able to make use of the appended infodoc to avoid this problem. I see no evidence of our having tested this with your particular scenario, but it has been successful in similar cases.
You might also inquire of whoever supports your storage device whether a mode is supported whereby the device's inquiry strings can be made unique.
Here is the steps he wanted me to take and the results. I still can not get the Xserve RAIDS to generate a unique device id:
Step 1
Determine the vendor and product strings. You can run these commands:
# netstat -k | grep -i vendor
# netstat -k | grep -i product
netstat -k | grep -i vendor
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
grep -i product
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
or you can run
# format -e
then select scsi, then inquiry.
scsi> inq
Inquiry:
00 00 05 12 5b 00 00 02 41 50 50 4c 45 20 20 20 ....[...APPLE
58 73 65 72 76 65 20 52 41 49 44 20 20 20 20 20 Xserve RAID
31 2e 35 31 63 00 00 00 00 00 00 00 00 00 00 00 1.51c...........
00 00 00 00 00 00 00 00 00 00 0d 40 0d a0 0e 20 ...........@...
0d 80 09 00 0a 00 00 20 00 00 00 20 20 20 20 20 ....... ...
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
Vendor: APPLE
Product: Xserve RAID
Revision: 1.51
Removable media: no
Device type: 0
ISO version: 0
ECMA version: 0
ANSI version: 5
Async event notification: no
Terminate i/o process msg: no
Response data format: 2
Additional length: 91
Relative addressing: no
32 bit transfers: no
16 bit transfers: no
Synchronous transfers: no
Linked commands: no
Command queueing: yes
Soft reset option: no
Step 2
Add an entry in the file '/kernel/drv/sd.conf'.
sd-config-list=
"APPLE Xserve RAID ", "AppleRAID";
AppleRAID=1,0x8,0,0,0,0,0;
Step 3 Reboot.
Step 4 Check with SUNWexplo.
[email protected]:[/opt/SUNWexplo/bin] (8)# ./diskinfo.sparc
/dev/rdsk/c0t0d0s2: Device busy
AVAILABLE SCSI DEVICES:
Location Vendor Product Rev Serial #
c1t0d0 COMPAQ BD036863AC HPB5 B2FT4HMM
c1t1d0 SEAGATE ST336607LSUN36G 0507 0349A66VKQ
c1t2d0 SEAGATE ST373307LSUN72G 0507 0417B7C9ZC
c1t3d0 SEAGATE ST373307LSUN72G 0507 0425B7LV5Q
c4t600039300001F461d0 APPLE Xserve RAID 151 c
c4t600039300001F461d1 APPLE Xserve RAID 151 c
c4t600039300001F461d2 APPLE Xserve RAID 151 c
c5t600039300001F2ECd0 APPLE Xserve RAID 151 c
c5t600039300001F2ECd1 APPLE Xserve RAID 151 c
As you will notice, there are no serial numbers in this command or netstat -k | grep -i product commands.

FXO to FXO disconnect problem - Part1

Hi,
I have 2 sites connected through an hdlc leased line. Each site has router 1750 with one VIC - 2FXO.
Once a call is placed both FXO are stuck in the off hook state. So there is no way to make another call unless I shut down and turn on the ViC again.
I read the "famous" fxo disconnect problem file from Cisco but it didn't help.
I need to know:
1) Is this problem a bug on the FXO ports ?
2) Is this problem from the analog PBX side ?
3) How to solve this problem?
Thanks

Hi,
you can use FXS cards......you don't have any problem......
Problem is in disconnect reason....FXO card no detect disconnect tone from PBX....
Czech firm 2N sell special "disconnect module" fot these card......
(I'm sorry for my English...:o)

Problems with Solaris 11 11/11

Hi,
I need your help because I have problems with Solaris 11 11/11 installed in a Dell Latitude E4310.
Here, there are the problems:
1- No it power off with shutdown or init 5 or init 0 only work well the reboot.
2- It can not connect to the wifi with wpa, no receive ip by dhcp, the driver of the card is "iwp"
Thanks.
Jorge
Edited by: jdangelo on Nov 16, 2011 1:49 PM
Edited by: jdangelo on Nov 17, 2011 2:51 PM

Here is the info of my laptop;
Manufacture name:Dell Inc.
Manufacture model:Latitude E4310
64 Bit:True
OS version:SunOS solaris 5.11 11.0 i86pc i386 i86pc
CPU Type:Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
CPU Number:1
Number Of Cores Per Processor:2
Number Of Threads Per Processor:4
Bios/Firmware Maker:Dell Inc. Version:A05 Release Date:11/20/2010
prtconf -pv:
System Configuration: Oracle Corporation i86pc
Memory size: 3958 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00c21000.00000000.02bc6001.00000000
name: 'ramdisk'
Node 0x000003
acpi-namespace: '\_SB_.PCI0'
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000004
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci8086,44.1028.410.2' + 'pci8086,44.1028.410' + 'pci1028,410' + 'pci8086,44.2' + 'pci8086,44' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00060000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000044
name: 'pci1028,410'
Node 0x000005
acpi-namespace: '\_SB_.PCI0.VID_'
assigned-addresses: 83001010.00000000.f0000000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.000060b0.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
compatible: 'pci8086,46.1028.410.2' + 'pci8086,46.1028.410' + 'pci1028,410' + 'pci8086,46.2' + 'pci8086,46' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
device_type: 'display'
unit-address: '2'
class-code: 00030000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000046
name: 'display'
Node 0x000006
acpi-namespace: '\_SB_.PCI0.GLAN'
assigned-addresses: 8200c810.00000000.f5400000.00000000.00020000.8200c814.00000000.f5480000.00000000.00001000.8100c818.00000000.00006040.00000000.00000020
reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
compatible: 'pci8086,10ea.1028.410.5' + 'pci8086,10ea.1028.410' + 'pci1028,410' + 'pci8086,10ea.5' + 'pci8086,10ea' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '19'
class-code: 00020000
revision-id: 00000005
vendor-id: 00008086
device-id: 000010ea
name: 'pci1028,410'
Node 0x000007
acpi-namespace: '\_SB_.PCI0.EHC2'
assigned-addresses: 8200d010.00000000.f5470000.00000000.00000400
reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b3c.1028.410.5' + 'pci8086,3b3c.1028.410' + 'pci1028,410' + 'pci8086,3b3c.5' + 'pci8086,3b3c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1a'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b3c
name: 'pci1028,410'
Node 0x000008
acpi-namespace: '\_SB_.PCI0.HDEF'
assigned-addresses: 8300d810.00000000.f5460000.00000000.00004000
reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
compatible: 'pciex8086,3b57.1028.410.5' + 'pciex8086,3b57.1028.410' + 'pciex8086,3b57.5' + 'pciex8086,3b57' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,3b57.1028.410.5' + 'pci8086,3b57.1028.410' + 'pci1028,410' + 'pci8086,3b57.5' + 'pci8086,3b57' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1b'
class-code: 00040300
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b57
name: 'pci1028,410'
Node 0x000009
acpi-namespace: '\_SB_.PCI0.RP01'
slot-names: 00000001.746f6c53.00003333
reg: 0000e000.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b42.5' + 'pciex8086,3b42' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b42.5' + 'pci8086,3b42' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00005000.81000000.00000000.00005000.00000000.00001000.82000000.00000000.f4000000.82000000.00000000.f4000000.00000000.01400000
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000000
devsel-speed: 00000000
interrupts: 00000001
unit-address: '1c'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b42
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b42'
Node 0x00000a
acpi-namespace: '\_SB_.PCI0.RP02'
slot-names: 00000001.746f6c53.00003433
reg: 0000e100.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b44.5' + 'pciex8086,3b44' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b44.5' + 'pci8086,3b44' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00004000.81000000.00000000.00004000.00000000.00001000.82000000.00000000.f2c00000.82000000.00000000.f2c00000.00000000.01400000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000002
unit-address: '1c,1'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b44
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b44'
Node 0x000013
acpi-namespace: '\_SB_.PCI0.RP02.PXSX'
assigned-addresses: 83020010.00000000.f2c00000.00000000.00002000
reg: 00020000.00000000.00000000.00000000.00000000.03020010.00000000.00000000.00000000.00002000
compatible: 'pciex8086,422c.8086.1321.35' + 'pciex8086,422c.8086.1321' + 'pciex8086,422c.35' + 'pciex8086,422c' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,422c.8086.1321.35' + 'pci8086,422c.8086.1321' + 'pci8086,1321' + 'pci8086,422c.35' + 'pci8086,422c' + 'pciclass,028000' + 'pciclass,0280'
model: 'Network controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00008086
subsystem-id: 00001321
unit-address: '0'
class-code: 00028000
revision-id: 00000035
vendor-id: 00008086
device-id: 0000422c
name: 'pci8086,1321'
Node 0x00000b
acpi-namespace: '\_SB_.PCI0.RP03'
slot-names: 00000001.746f6c53.00000038
reg: 0000e200.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b46.5' + 'pciex8086,3b46' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b46.5' + 'pci8086,3b46' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00003000.81000000.00000000.00003000.00000000.00001000.82000000.00000000.f1800000.82000000.00000000.f1800000.00000000.01400000
bus-range: 00000003.00000003
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000002
devsel-speed: 00000000
interrupts: 00000003
unit-address: '1c,2'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b46
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b46'
Node 0x000014
acpi-namespace: '\_SB_.PCI0.RP03.PXSX'
assigned-addresses: 82030010.00000000.f1830000.00000000.00000100
reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00000100
compatible: 'pciex1180,e822.1028.410.1' + 'pciex1180,e822.1028.410' + 'pciex1180,e822.1' + 'pciex1180,e822' + 'pciexclass,080500' + 'pciexclass,0805' + 'pci1180,e822.1028.410.1' + 'pci1180,e822.1028.410' + 'pci1028,410' + 'pci1180,e822.1' + 'pci1180,e822' + 'pciclass,080500' + 'pciclass,0805'
model: 'SD Host controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00080500
revision-id: 00000001
vendor-id: 00001180
device-id: 0000e822
name: 'pci1028,410'
Node 0x00000c
acpi-namespace: '\_SB_.PCI0.RP04'
slot-names: 00000001.746f6c53.00000039
reg: 0000e300.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b48.5' + 'pciex8086,3b48' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b48.5' + 'pci8086,3b48' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00002000.81000000.00000000.00002000.00000000.00001000.82000000.00000000.f0400000.82000000.00000000.f0400000.00000000.01400000
bus-range: 00000004.00000009
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000004
unit-address: '1c,3'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b48
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b48'
Node 0x00000d
acpi-namespace: '\_SB_.PCI0.EHCI'
assigned-addresses: 8200e810.00000000.f5450000.00000000.00000400
reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b34.1028.410.5' + 'pci8086,3b34.1028.410' + 'pci1028,410' + 'pci8086,3b34.5' + 'pci8086,3b34' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1d'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b34
name: 'pci1028,410'
Node 0x00000e
acpi-namespace: '\_SB_.PCI0.P0P1'
slot-names: 0000002f.746f6c53.6c530031.0032746f.746f6c53.6c530033.0034746f.746f6c53.00000032
reg: 0000f000.00000000.00000000.00000000.00000000
compatible: 'pci8086,2448.a5' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
bus-range: 0000000a.0000000a
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
devsel-speed: 00000000
unit-address: '1e'
class-code: 00060401
revision-id: 000000a5
vendor-id: 00008086
device-id: 00002448
name: 'pci8086,2448'
Node 0x00000f
#size-cells: 00000001
#address-cells: 00000002
ranges: 00000001.00000000.81000000.00000000.00000000.00000022.00000001.00000024.81000000.00000000.00000024.00000002.00000001.00000028.81000000.00000000.00000028.00000002.00000001.0000002c.81000000.00000000.0000002c.00000006.00000001.00000034.81000000.00000000.00000034.00000002.00000001.00000038.81000000.00000000.00000038.00000002.00000001.0000003c.81000000.00000000.0000003c.00000002.00000001.00000040.81000000.00000000.00000040.00000004.00000001.0000004e.81000000.00000000.0000004e.00000006.00000001.00000060.81000000.00000000.00000060.00000002.00000001.00000063.81000000.00000000.00000063.00000003.00000001.00000067.81000000.00000000.00000067.00000001.00000001.00000070.81000000.00000000.00000070.00000008.00000001.00000070.81000000.00000000.00000070.00000001.00000001.00000080.81000000.00000000.00000080.00000022.00000001.000000a4.81000000.00000000.000000a4.00000002.00000001.000000a8.81000000.00000000.000000a8.00000002.00000001.000000ac.81000000.00000000.000000ac.00000002.00000001.000000b0.81000000.00000000.000000b0.00000006.00000001.000000b8.81000000.00000000.000000b8.00000002.00000001.000000bc.81000000.00000000.000000bc.00000002.00000001.000000c0.81000000.00000000.000000c0.00000020.00000001.000000f0.81000000.00000000.000000f0.00000001.00000001.00000400.81000000.00000000.00000400.00000080.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000680.81000000.00000000.00000680.00000020.00000001.00000930.81000000.00000000.00000930.00000001.00000001.00000934.81000000.00000000.00000934.00000001.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001000.81000000.00000000.00001000.00000014.00000001.0000164e.81000000.00000000.0000164e.00000002.00000001.0000ffff.81000000.00000000.0000ffff.00000001.00000000.f54c0000.82000000.00000000.f54c0000.00001000.00000000.f8000000.82000000.00000000.f8000000.04000000.00000000.fed00000.82000000.00000000.fed00000.00000400.00000000.fed10000.82000000.00000000.fed10000.00004000.00000000.fed18000.82000000.00000000.fed18000.00002000.00000000.fed1c000.82000000.00000000.fed1c000.00024000.00000000.fed45000.82000000.00000000.fed45000.0004b000.00000000.fee00000.82000000.00000000.fee00000.00100000.00000000.ff000000.82000000.00000000.ff000000.01000000.00000000.ff000000.82000000.00000000.ff000000.01000000
acpi-namespace: '\_SB_.PCI0.LPCB'
device_type: 'isa'
reg: 0000f800.00000000.00000000.00000000.00000000
compatible: 'pci8086,3b0f.1028.410.5' + 'pci8086,3b0f.1028.410' + 'pci1028,410' + 'pci8086,3b0f.5' + 'pci8086,3b0f' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f'
class-code: 00060100
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b0f
name: 'isa'
Node 0x00001c
unit-address: '1,60'
interrupts: 00000001.0000000c
reg: 00000001.00000060.00000001.00000001.00000064.00000001
name: 'i8042'
Node 0x00001d
compatible: 'pnpPNP,303'
device-type: 'keyboard'
interrupts: 00000001.0000000c
reg: 00000000
acpi-namespace: '\_SB_.PCI0.LPCB.PS2K'
model: 'System keyboard'
name: 'keyboard'
Node 0x00001e
compatible: 'pnpPNP,f03'
device-type: 'mouse'
reg: 00000001
interrupts: 0000000c
acpi-namespace: '\_SB_.PCI0.LPCB.PS2M'
model: 'PS/2 Port for PS/2-style Mice'
name: 'mouse'
Node 0x00001f
interrupts: 00000004
reg: 00000001.000003f8.00000008
model: 'Standard serial port'
compatible: 'PNP0500'
name: 'asy'
Node 0x000010
acpi-namespace: '\_SB_.PCI0.SAT0'
assigned-addresses: 8100fa10.00000000.00006090.00000000.00000008.8100fa14.00000000.00006080.00000000.00000004.8100fa18.00000000.00006070.00000000.00000008.8100fa1c.00000000.00006060.00000000.00000004.8100fa20.00000000.00006020.00000000.00000020.8200fa24.00000000.f5440000.00000000.00000800
reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
compatible: 'pci8086,3b2f.1028.410.5' + 'pci8086,3b2f.1028.410' + 'pci1028,410' + 'pci8086,3b2f.5' + 'pci8086,3b2f' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,2'
class-code: 00010601
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b2f
name: 'pci1028,410'
Node 0x000011
acpi-namespace: '\_SB_.PCI0.SBUS'
assigned-addresses: 8300fb10.00000000.f5430000.00000000.00000100.8100fb20.00000000.00006000.00000000.00000020
reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
compatible: 'pci8086,3b30.1028.410.5' + 'pci8086,3b30.1028.410' + 'pci1028,410' + 'pci8086,3b30.5' + 'pci8086,3b30' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,3'
class-code: 000c0500
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b30
name: 'pci1028,410'
Node 0x000012
assigned-addresses: 8300fe10.00000000.f5420000.00000000.00001000
reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000
compatible: 'pci8086,3b32.1028.410.5' + 'pci8086,3b32.1028.410' + 'pci1028,410' + 'pci8086,3b32.5' + 'pci8086,3b32' + 'pciclass,118000' + 'pciclass,1180'
model: 'DSP/DAP controllers'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,6'
class-code: 00118000
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b32
name: 'pci1028,410'
Node 0x000015
device_type: 'acpirootnex'
compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\'
name: 'fw'
Node 0x000016
unit-address: '1'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000000
acpi-processor-id: 00000001
acpi-namespace: '\_PR_.CPU0'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000017
unit-address: '2'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000004
acpi-processor-id: 00000002
acpi-namespace: '\_PR_.CPU1'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000018
unit-address: '3'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000001
acpi-processor-id: 00000003
acpi-namespace: '\_PR_.CPU2'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000019
unit-address: '4'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000005
acpi-processor-id: 00000004
acpi-namespace: '\_PR_.CPU3'
device_type: 'acpicpu'
name: 'cpu'
Node 0x00001a
unit-address: '0'
compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\_SB_'
device_type: 'acpidevice'
name: 'sb'
Node 0x00001b
io-space: 00000000.00000020.00000020.00000002.00000024.00000002.00000028.00000002.0000002c.00000002.0000002e.00000002.00000030.00000002.00000034.00000002.00000038.00000002.0000003c.00000002.00000040.00000004.0000004e.00000002.00000050.00000004.00000060.00000001.00000061.00000001.00000063.00000001.00000064.00000001.00000065.00000001.00000067.00000001.00000070.00000008.00000070.00000001.00000080.00000001.00000081.00000011.00000092.00000001.00000093.0000000d.000000a0.00000002.000000a4.00000002.000000a8.00000002.000000ac.00000002.000000b0.00000002.000000b2.00000002.000000b4.00000002.000000b8.00000002.000000bc.00000002.000000c0.00000020.000000f0.00000001.00000400.00000080.000004d0.00000002.00000500.00000080.00000680.00000020.00000930.00000001.00000934.00000001.00000cf8.00000008.00001000.00000004.00001004.00000010.0000164e.00000002.0000ffff.00000001
device-memory: f54c0000.00001000.f8000000.04000000.fed00000.00000400.fed10000.00004000.fed18000.00001000.fed19000.00001000.fed1c000.00004000.fed20000.00020000.fed45000.0004b000.fee00000.00100000.ff000000.01000000.ff000000.01000000
dma-channels: 00000004
interrupts: 00000000.00000001.00000002.00000008.0000000c.0000000d
name: 'used-resources'
prtdiag:
System Configuration: Dell Inc. Latitude E4310
BIOS Configuration: Dell Inc. A05 11/20/2010
==== Processor Sockets ====================================
Version Location Tag
Intel(R) Core(TM) i5 CPU M 560 @ 2.67GH CPU 1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
Unknown in use 0 DIMM_A BANK 0
unknown empty 0 DIMM_B BANK 2
==== On-Board Devices =====================================
"Intel GM45 Graphics"
NETWORK_NAME_STRING
==== Upgradeable Slots ====================================
ID Status Type Description
0 available PCI Express x16 J5C1
1 available PCI Express J6C2
2 in use PCI Express J6D2
3 in use PCI Express J7C1
4 available PCI Express J7D2
System Information:
Manufacturer:Dell Inc.
Product:Latitude E4310
BIOS Information:
Vendor:Dell Inc.
Version:A05
Release Date:11/20/2010
BIOS Revision: BIOS Revision:4.6
Firmware Revision:
MotherBoard Information:
Product:0D8H24
Manufacturer:Dell Inc.
Version:A00
Onboard Devices:[Video,Disabled]"Intel GM45 Graphics"
CPU Information:
Processor 0:
Processor Socket Type:CPU 1
Processor Manufacturer:Intel
Current Voltage:0.0V
External Clock:533MHZ
Max Speed:4000MHZ
Current Speed:2666MHZ
Memory Information:
Physical Memory: 4G (4G)
Maximum Memory Support: 4096G
Memory Subsystem 0:
Array Used Function:System memory
Memory Error Correction Supported:None
Maximum Array Capacity:8G
Number of Memory Devices:2
Memory Device 0:
Memory Device Locator:DIMM_A
Total Width:64
Data Width:64
Installed Size:4096M
Memory Device Type:Unknown
Speed:1067MHZ
Memory Device 1:
[Not Installed]

Openwindows dt libs problems in Solaris 2.8

Hello
My Motif Apps work fine with solaris 2.6
Now, we are moving to solaris 2.8.
I compiled the SAME source code in solaris 2.8 - this App have a different look and feel - like fonts being different, bgcolor, etc.
however, if i compile with solaris 2.6 /usr/dt/lib and /usr/openwin/lib - all looks similar
can anyone point the problems with solaris 2.8
/usr/dt/lib and /usr/openwin/lib
Thanks,
venkat

Are you using the same dot files, from the same
login account in each case? This sounds like some
local settings are different. Using different
monitors can make a difference, too. There are two
different systems with the same monitor which you
are using from the same home dir?

FXO Disconnect Problem

Hello,
I just would like to ask some ideas on FXO disconnect problem having a setup of FXO to FXO termination on both sites. I am using a VIC-2FXO-M2 on both Cisco 1760-V Router and these fxo ports are terminated to the PABX local.The voice port will disconnect 30minutes (approximately) after the call is terminated or it remainded off-hook although the call is already done.
We tried some fine tunings like enabling "battery-reversal" command, setting the timeout call disconnect to 5sec, timeout wait-release to 5sec. But the problem is still the same.
What is really the ideal fxo disconnect solution that we can do to lessen the 30minutes delay from off-hook to on-hook.
Looking forward for your great ideas.
Thank you.
Vivira Alastra

Dear Vivira,
The disconnection issue of FXO ports can really produce some gray hairs...
I have worked integrated to some cheap Panasonic PBX's in Nigeria where documentation is really scarce.
The solution that worked - but don't ask me how - was to try different combinations of CPTone on the Voice Ports. That did the job in our case.
You can also try the tedious job of measuring the disconnect tones ans analyse it e.g. in CoolEdit and then set up a Voice Class where you define the tones.
But try the CPTone settings first.
Good luck.
Peter

Disconnect problems on FXO Groundstart lines

Hello all,
I have a CCME customer, IOS 12.3-11T2. with 6 FXO ground-start lines on a 2821 platform. They are using PVDM2-32s and two 4Port FXO cards. The call flow goes as follows.
Incoming call from PSTN, hits fxo port which has a connection plar to a number which calls a script in CUE. From the script if you press 0 it calls the reception.
All the above works fine.
If the reception hangs up the call and the PSTN party does not right away, the PSTN party hears a repeating click. If the PSTN then hangs up and you do a show voice port summary it shows as follows
IN OUT
PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC
========= == ============ ===== ==== ======== ======== ==
0/1/0 -- fxo-gs up up idle on-hook y
Note that the OPER stat shows up and the out status shows on-hook
Until that OPER status changes to DORM every call after the first one will get answered by this port and the PSTN party will hear the repeating click in their ear. It takes up to 30-40 seconds for the call to clear.
If the PSTN party hangs up first the OPER stat will go to DORM almost immediately.
Any thoughts?
Ryan

use the following commands to shorten the time the router waits before determining that the call needs to be dropped due to disconnect tones.
on the voice port
voice-port 1/1/0
timeouts call-disconnect 5
timeouts wait-release 5
these will shorten the IOS default times of 30 sec & 60 sec down to 5 seconds.
use the following link for more info on the FXO disconnect problem.
http://www.cisco.com/en/US/customer/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml

Cisco Solution for FXO Disconnect Problem

I have Panasonic PBX-->FXO-->1751V------WAN-----1751V-->FXO--Panasonic PBX. I am facing a serious problem with FXO on both ends becoming busy after some few initial calls.
What is the exact Cisco solution for this FXO disconnect problem? I have read and applied some Netpro tips for similar case but none could help.
Can we have Cisco expert explain this??

Hello, I think this url may be helpful:
http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml
Regards.

Cisco FXO Disconnect Problem

we have 2801 router that connected with 2 anloga lines (FXO Card), but now we have a problem with disconnect problem, the phone still connected after the PSTN Caller Disconnect, and our policy tell that the agents shouldn't end the call, so we want when the PSTN caller end the call we need the phone to return to idle state.
and according for the below link, i configure the custom disconnect tone, and in the attachment you can find tow disconnect tones.
http://ciscoflair.blogspot.com/2009/05/cisco-fxo-disconnect-issue.html
the configuration of the custom disconnect tone
voice class dualtone-detect-params 1
cadence-variation 3
voice class custom-cptone Custom1
dualtone disconnect
frequency 420
cadence 245 255 245 255 245 255
and the below you can find the configuration of the voice port, and you can find the debug vpm port 0/3/0, debug vpm signal, for a call that disconnected immediately, and for a call the take long time to disconnected.
this is the configuration of the voice port:
voice-port 0/3/0
supervisory disconnect dualtone mid-call
supervisory custom-cptone Custom1
supervisory dualtone-detect-params 1
no battery-reversal
cptone NL
timeouts call-disconnect 5
timeouts wait-release 5
timing hookflash-out 50
timing guard-out 300
caller-id enable
caller-id alerting line-reversal
caller-id alerting dsp-pre-allocate
this is the debug of a call that is disconnected immediately:
Jan 25 11:48:32.262: [0/3/0] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE_SM_CALLERID_RX
Jan 25 11:48:32.262: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_HTSP_CALLERID_RX_DONE]
Jan 25 11:48:32.262: [0/3/0] htsp_stop_caller_id_rx. message length 11
Jan 25 11:48:32.262: [0/3/0] htsp_dsm_close_done
Jan 25 11:48:34.026: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
Jan 25 11:48:34.026: htsp_timer - 125 msec
Jan 25 11:48:34.154: htsp_process_event: [0/3/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
Jan 25 11:48:34.154: htsp_timer - 10000 msec
Jan 25 11:48:35.305: htsp_process_event: [0/3/0, FXOLS_RINGING, E_DSP_SIG_0100]
Jan 25 11:48:35.305: fxols_ringing_not
Jan 25 11:48:35.305: htsp_timer_stop
Jan 25 11:48:35.305: htsp_timer_stop3 htsp_setup_ind
Jan 25 11:48:35.305: [0/3/0] get_fxo_caller_id:Caller ID received. Message type=129 length=11 checksum=00
Jan 25 11:48:35.309: [0/3/0] Caller ID String 44 30 36 35 36 37 39 31 34 31
Jan 25 11:48:35.309: [0/3/0] get_fxo_caller_id calling num=065679141 calling name= calling time=01/25 13:48
Jan 25 11:48:35.313: htsp_process_event: [0/3/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
Jan 25 11:48:35.313: fxols_wait_setup_ack:
Jan 25 11:48:35.313: [0/3/0] set signal state = 0xC timestamp = 0fxols_check_auto_call
Jan 25 11:48:35.321: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc
Jan 25 11:48:35.321: htsp_timer - 120000 msechtsp_alert_notify
Jan 25 11:48:35.389: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)
Jan 25 11:48:35.509: htsp_call_bridged invokedhtsp_call_service_msghtsp_call_service_msg not EFXS (2)
Jan 25 11:48:35.513: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect
Jan 25 11:48:35.513: htsp_timer_stop
Jan 25 11:48:35.521: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
Jan 25 11:48:35.585: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_DSP_SIG_0110]fxols_rvs_battery
Jan 25 11:48:35.585: htsp_timer_stop2
sh voice po su
                                           IN       OUT
PORT            CH   SIG-TYPE   ADMIN OPER STATUS   STATUS   EC
=============== == ============ ===== ==== ======== ======== ==
0/3/0           -- fxo-ls      up    up   idle     off-hook y
0/3/1           -- fxo-ls      up    dorm idle     on-hook y
50/0/1          1      efxs     up    up   on-hook idle     y
50/0/1          2      efxs     up    up   on-hook idle     y
PWR FAILOVER PORT        PSTN FAILOVER PORT
=================        ==================
Jan 25 11:48:43.857: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_DSP_SUP_DISCONNECT]fxols_conn_sup_disc
Jan 25 11:48:43.857: htsp_timer2 - 5000 msec
Madaba_Maint#
Jan 25 11:48:48.856: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_HTSP_EVENT_TIMER2]fxols_disc_confirm
Jan 25 11:48:48.856: htsp_timer_stop
Jan 25 11:48:48.856: htsp_timer_stop2
Jan 25 11:48:48.856: htsp_timer_stop3
Jan 25 11:48:48.860: htsp_timer_stop3
Jan 25 11:48:48.876: htsp_process_event: [0/3/0, FXOLS_REMOTE_RELEASE, E_HTSP_RELEASE_REQ]fxols_offhook_release
Jan 25 11:48:48.876: htsp_timer_stop
Jan 25 11:48:48.876: htsp_timer_stop2
Jan 25 11:48:48.876: htsp_timer_stop3
Jan 25 11:48:48.876: [0/3/0] set signal state = 0x4 timestamp = 0
Jan 25 11:48:48.876: htsp_timer - 300 msec
Jan 25 11:48:49.148: htsp_process_event: [0/3/0, FXOLS_GUARD_OUT, E_DSP_SIG_0110]
Jan 25 11:48:49.176: htsp_process_event: [0/3/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout
Jan 25 11:48:49.176: fxols_dsp_prealloc_clid_wait. Line reversal alerting DSP preallocation done
Jan 25 11:48:49.176: [0/3/0] htsp_start_caller_id_rx:ETSI_DTMF
Jan 25 11:48:49.176: htsp_start_caller_id_rx create dsp_stream_manager
Jan 25 11:48:49.176: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_DSP_SIG_0100]
Jan 25 11:48:49.176: [0/3/0] htsp_dsm_create_success returns 1
Madaba_Maint#sh voice po su
                                           IN       OUT
PORT            CH   SIG-TYPE   ADMIN OPER STATUS   STATUS   EC
=============== == ============ ===== ==== ======== ======== ==
0/3/0           -- fxo-ls      up    dorm idle     on-hook y
0/3/1           -- fxo-ls      up    dorm idle     on-hook y
50/0/1          1      efxs     up    up   on-hook idle     y
50/0/1          2      efxs     up    up   on-hook idle     y
this is a debug for a call that is take a long time to disconnected:
Jan 25 11:49:42.267: [0/3/0] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE_SM_CALLERID_RX
Jan 25 11:49:42.267: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_HTSP_CALLERID_RX_DONE]
Jan 25 11:49:42.267: [0/3/0] htsp_stop_caller_id_rx. message length 11
Jan 25 11:49:42.271: [0/3/0] htsp_dsm_close_done
Jan 25 11:49:43.999: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
Jan 25 11:49:43.999: htsp_timer - 125 msec
Jan 25 11:49:44.127: htsp_process_event: [0/3/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
Jan 25 11:49:44.127: htsp_timer - 10000 msec
Jan 25 11:49:45.279: htsp_process_event: [0/3/0, FXOLS_RINGING, E_DSP_SIG_0100]
Jan 25 11:49:45.279: fxols_ringing_not
Jan 25 11:49:45.279: htsp_timer_stop
Jan 25 11:49:45.279: htsp_timer_stop3 htsp_setup_ind
Jan 25 11:49:45.279: [0/3/0] get_fxo_caller_id:Caller ID received. Message type=129 length=11 checksum=00
Jan 25 11:49:45.279: [0/3/0] Caller ID String 44 30 36 35 36 37 39 31 34 31
Jan 25 11:49:45.279: [0/3/0] get_fxo_caller_id calling num=065679141 calling name= calling time=01/25 13:49
Jan 25 11:49:45.283: htsp_process_event: [0/3/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
Jan 25 11:49:45.283: fxols_wait_setup_ack:
Jan 25 11:49:45.287: [0/3/0] set signal state = 0xC timestamp = 0fxols_check_auto_call
Jan 25 11:49:45.291: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc
Jan 25 11:49:45.291: htsp_timer - 120000 msechtsp_alert_notify
Jan 25 11:49:45.379: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)
Jan 25 11:49:45.495: htsp_call_bridged invokedhtsp_call_service_msghtsp_call_service_msg not EFXS (2)
Jan 25 11:49:45.503: htsp_process_event: [0/3/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect
Jan 25 11:49:45.503: htsp_timer_stop
Jan 25 11:49:45.507: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
Jan 25 11:49:45.559: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_DSP_SIG_0110]fxols_rvs_battery
Jan 25 11:49:45.559: htsp_timer_stop2
sh voice po su
                                           IN       OUT
PORT            CH   SIG-TYPE   ADMIN OPER STATUS   STATUS   EC
=============== == ============ ===== ==== ======== ======== ==
0/3/0           -- fxo-ls      up    up   idle     off-hook y
0/3/1           -- fxo-ls      up    dorm idle     on-hook y
50/0/1          1      efxs     up    up   on-hook idle     y
50/0/1          2      efxs     up    up   on-hook idle     y
Jan 25 11:50:30.387: htsp_timer_stop3
Jan 25 11:50:30.399: htsp_process_event: [0/3/0, FXOLS_CONNECT, E_HTSP_RELEASE_REQ]fxols_offhook_release
Jan 25 11:50:30.399: htsp_timer_stop
Jan 25 11:50:30.399: htsp_timer_stop2
Jan 25 11:50:30.399: htsp_timer_stop3
Jan 25 11:50:30.399: [0/3/0] set signal state = 0x4 timestamp = 0
Jan 25 11:50:30.399: htsp_timer - 300 msec
Jan 25 11:50:30.671: htsp_process_event: [0/3/0, FXOLS_GUARD_OUT, E_DSP_SIG_0110]
Jan 25 11:50:30.699: htsp_process_event: [0/3/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout
Jan 25 11:50:30.699: fxols_dsp_prealloc_clid_wait. Line reversal alerting DSP preallocation done
Jan 25 11:50:30.699: [0/3/0] htsp_start_caller_id_rx:ETSI_DTMF
Jan 25 11:50:30.699: htsp_start_caller_id_rx create dsp_stream_manager
Jan 25 11:50:30.699: htsp_process_event: [0/3/0, FXOLS_ONHOOK, E_DSP_SIG_0100]
Jan 25 11:50:30.699: [0/3/0] htsp_dsm_create_success returns 1
So what can we do? what is the wronge of my configuration?

anyone can help?

WRT54G disconnect problem

I have been a loyal Linksys (CISCO) user since buying my 1st Wireless Access Point router/4-port Switch (BEFW1154 v2) in 08/2002. I upgraded to a Linksys Wireless-G Broadband Router (WRT54G v8.00.2) in 11/2007. My home wireless network supports; IBM Thinkpad (Windows XP) and Lenovo Ideapad (Windows VISTA Home Premium). About a month ago I started having disconnect issues with the WRT54G. Both laptops experienced the disconnects. Initially, I unplugged the WRT54G power for about 1 minute then plugged it back in. This did not resolve the disconnect problem. I then tried to unplug the cable modem and WRT54G power. Wait about 1 minute then plug in the cable modem allowing it to reset and sync up. Then I plugged in the WRT54G. This temporarily resolved the problem for a few minutes but the disconnect problem returned eventually. I reset the WRT54G to the factory default configuration and reconfigured it for my home network. The disconnect problem was not resolved by taking this action. I contacted Cablevision who provides my broadband Internet access. They could not identify a root cause for the disconnect problem. To determine if the root cause was something other than the WRT54G, I reinstalled the BEFW1154. I have not had a disconnect problem since taking this action leading me to believe that the WRT54G is bad. I would appreciate any suggestions that might resolve the disconnect problem except for a suggestion to purchase a new router. THANKS
Solved!
Go to Solution.

I too have had the disconnect problem. I am thinking now that my problem started when I moved the Router next to the printer. I think when the printer is on my router disconnects. I have the printer off this morning and have no problems. Last night the printer was on and both my wife's and my Pc's would lose connection to the router until I unplugged it and plugged it back in.
Is it possible for a printer to throw off the connection? I know my cell phone causes a lot of noise in the speakers if I have it next to the PC.

DNS PRoblem in SOLARIS 9.0

Hi
can any one help me on this
I am facing dns problem in solaris sparc 9.0. I am not able to see
" /etc/named.conf" .If i type in.named -v it is showing BIND version .is it required to install bind seprately.
I downloaded BIND from sunfreeware i tried to compile but it is throghing the error something like "make cannot build" after running "./confiugre"
One more query is it possible to install dns and nis server in same solaris box .
could any one guide me how to setup the DNS server and how to configure
Thanks
SolarisTeam

Hi
Thanks for the reply,
It is working fine with the upgraded version of Weblogic 9.0 from weblogic 8.1. But not with the fresh installation of Weblogic 9.0.
Thanks,
Raj

I have a lot of disconnection problems with my bluetooth apple keyboard

can you recommand a bluetooth dongle?
I have disconnection problems with my bluetooth apple keyboard & trackpad. I use windows 7. my pc is ~ 5 meters frpm my keyboard.
BTW - my microsoft mouse works great!
thanks,
gil

Here is an apple article about redeeming digital copies: http://support.apple.com/kb/ht1539

Iomega Hard Drive Disconnecting Problems / iMac Freezing on shutdown/restart!

I had noticed in the past week that when my iMac is in sleep mode that sometimes it is unresponsive when I try to wake it up to use it again, and then after a few minutes of trying, I have to manually power the computer on, like it randomly will shut itself down if it's in sleep mode for a longer time, but like I said, this is random.
The BIGGER problem I've encountered in the past two days is that when I go to eject my Iomega eGo Blue 1tb hard drive, the drive will not disconnect, the name on the sidebar of my finder just changes from black to grey underneath the devices row and on the desktop the Iomega icon turns lighter to indicate that it is not in use, but I cannot eject the drive, so it's still somewhat connected to the computer. I've had this drive for over a year with no complaints as I use it on both my MacBook (2009) and iMac (which I purchased new in October '11).
Instead of just turning off my hard drive or unplugging it, I try to restart my computer; however when I do that, the restart get stuck and nothing ends up working. I also have tried to shut it down with no luck, I then go to holding down the power button until it manually shuts down.
I also plugged in the hard drive to my MacBook and am not experiencing any mounting or disconnecting problems with it. I am very afraid that this may cause my Iomega to crash before I can get another hard drive to back everything up with!
I'm concerned that this could be a problem with both the hard drive and my Mac; does anyone have any input on this? I will probably end up taking it into the store or calling AppleCare, but I wanted to see if anyone else has had a similar problem.
Thank you!

First reset the SMC, you may need to do this 2-3x. Also reset the PRAM, again 2-3x. Finally restart the computer in Safe Mode to reset some of the caches, it's possible one is corrupt. When resetting the SMC & PRAM please carefully follow the instructions below:
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.

Rsh disconnect problems in Solaris 10

Similar Messages

Maybe you are looking for