- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIC #lanadmin status "up", why #linkloop "FAILED"?
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
Forums
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
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
07-14-2005 05:40 PM
07-14-2005 05:40 PM
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/16/6 0x080009B8D933 2 UP lan2 snap2 1 ETHER Yes 119
8/12/2/0 0x001083F92F56 1 UP lan1 snap1 2 ETHER Yes 119
8/12/1/0 0x001083F92F55 0 UP lan0 snap0 3 ETHER Yes 119
qh_scp1#linkloop 0x001083F92F56
Link connectivity to LAN station: 0x001083F92F56
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1
qh_scp1#netstat -in
Name Mtu Network Address Ipkts Opkts
lan2 1500 192.1.1.0 192.1.1.1 7186 7762
lan1 1500 10.188.220.0 10.188.220.201 11 12
lan0 1500 10.188.220.0 10.188.220.211 18 18
lo0 4136 127.0.0.0 127.0.0.1 970 970
qh_scp1#ioscan -fnuClan
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 0 8/12/1/0 btlan4 CLAIMED INTERFACE HP J3516A#001 HSC 10/100Base-TX D-Class 2 port
/dev/diag/lan0 /dev/ether0 /dev/lan0
lan 1 8/12/2/0 btlan4 CLAIMED INTERFACE HP J3516A#001 HSC 10/100Base-TX D-Class 2 port
/dev/diag/lan1 /dev/ether1 /dev/lan1
lan 2 8/16/6 lan2 CLAIMED INTERFACE Built-in LAN
/dev/diag/lan2 /dev/ether2
qh_scp1#lanadmin
PPA Number = 1
Description = lan1 Hewlett-Packard 10/100 TX Full-Duplex TT = 1500
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x1083f92f56
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2005 05:53 PM
07-14-2005 05:53 PM
Re: NIC #lanadmin status "up", why #linkloop "FAILED"?
e.g.
linkloop -i loacl_nic_ppa linked_nic_mac_addr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2005 06:34 PM
07-14-2005 06:34 PM
Solutiontry this though without the -i option it should take the first PPA (in your case 0):
# linkloop -i 0 0x001083F92F56
using lan0 to test lan1
# linkloop -i 1 0x001083F92F55
using lan1 to test lan0
if both fails, there may be some problem with the cable.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2005 01:14 PM
07-15-2005 01:14 PM
Re: NIC #lanadmin status "up", why #linkloop "FAILED"?
linkloop is failing because it is a mac address level of connectivity check and since you are not specifying any options, we dont know how the box is trying to get to this mac address
Try this and it should come back OK
linkloop -i 1 0x001083F92F56
thanks
DP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2005 05:03 PM
07-16-2005 05:03 PM
Re: NIC #lanadmin status "up", why #linkloop "FAILED"?
What is output of lanscan in other two network cards??
Regards
Mahesh