- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- cu -l/dev/cul2a2 plt3
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2013 12:26 PM
03-27-2013 12:26 PM
cu -l/dev/cul2a2 plt3
Hi,
All of sudden our dialing string is no longer working:
cu -l/dev/cul2a2 plt3
I am receiving the error:
Autodialing - Please wait
Connect failed: line problem
I checked the device /dev/cul2a2 with 'lssf' and get:
pci_mux0 card instance 2 port a2 callout at address ??? /dev/cul2a2
It seems the system is no longer recognize the mux card.
Executing ioscan with
# ioscan -funC tty
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
tty 1 0/0/4/0 func0 CLAIMED INTERFACE PCI BaseSystem (103c128d)
tty 0 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/mux0
/dev/diag/mux0 /dev/tty0p1
Can someone point me to the direction?
thanks
hugh
- Tags:
- modem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2013 11:40 PM
03-27-2013 11:40 PM
Re: cu -l/dev/cul2a2 plt3
Is the "ioscan -fnC tty" output any different from the "ioscan -funC tty" you already posted?
Is there anything in the /var/adm/syslog/syslog.log file or in the "dmesg" command ouput that might be relevant to the mux card?
What is your hardware model and OS version? (please post the output of "model; uname -a")
Has the system been changed in any way recently? (any patches installed, kernel configuration changed, etc?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2013 05:53 AM
03-28-2013 05:53 AM
Re: cu -l/dev/cul2a2 plt3
Matti,
Our os is: B.11.11
model: Rp2430 (9000/800/A400)
1) Syslog shows
Asio0_init: unexpected SAS subsystem ID (1283)
2) dmesg:
asio0_init: unexpected SAS subsystem ID (1283)
scsi tape: dev = 0xcd020000 I/O error during close.
3) I also get a generated mail (elm) about:
a. Tape at hardware path 0/0/2/0.0.0 : hardware failure
b. Disk at hardware path 0/0/1/1.15.0 : a smart event has ocurred
The drive has predicted that it will fail in the near future. Contact your HP support rep as soon as possible.
3) ioscan -fnc tty and ioscan -funC tty produced same result.
I'm thinking that either my boot (root) hard drive may have gone bad or a mux card.
thanks,
hugh