- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Process trouble network
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
05-29-2002 05:21 AM
05-29-2002 05:21 AM
Process trouble network
May 29 15:22:06 grenat vmunix: btlan4: NOTE: Link Partner does not support Auto
Negotiation
May 29 15:22:06 grenat vmunix: btlan4: NOTE: MII link down, try AUI at 10/12/1/0
....
May 29 15:22:12 grenat vmunix: btlan4: timeout: DMA timeout occurred at 10/12/1/
0
May 29 15:22:12 grenat vmunix: btlan4: reset state is 226 at 10/12/1/0....
May 29 15:22:12 grenat vmunix: btlan4: WARNING: AUI Loopback Failed at 10/12/1/0
....
May 29 15:22:12 grenat vmunix: btlan4: NOTE: Retry Reset at 10/12/1/0....
May 29 15:22:12 grenat vmunix: btlan4: Hardware Reset Started on 10/12/1/0....Th
is will take approximately 11 seconds
This message is put in the syslog.log every time.
What's the solution to abort this message
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 05:27 AM
05-29-2002 05:27 AM
Re: Process trouble network
was the other lan card working fine earlier ?? If so then you can try a RESET of the lan card using landiag.
You can also check for the loose connections, cable connections and the switch settings to which it is connected. The lan card and switch speed should be the same.
ioscan -fn |grep lan....what is the output for btlan4.
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 05:33 AM
05-29-2002 05:33 AM
Re: Process trouble network
Also check and make sure your card and your switch are set at the right speed. I prefer 100FD and AutoNeg OFF. Make sure both are set the same.
Just a thought,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 05:40 AM
05-29-2002 05:40 AM
Re: Process trouble network
To change the speed settings
lanadmin -X 100FD ppa # or NMID # for lan 0
lanadmin -x ppa # show you current speed on the card
netstat -in
would show you ppa# or NMID # for btlan4.
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 09:23 PM
06-03-2002 09:23 PM
Re: Process trouble network
Do you need to plug/unplug an AUI device
all the time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 04:17 AM
06-04-2002 04:17 AM
Re: Process trouble network
the message series you are seeing here are logical result of speed sensing and duplex negotiation mismatch , to clarify this
speed sensing :
in this case the card itself will go onto the physical cable and 'sense' the speed it runs , either 10 or 100Mb by analysing the hqartbeat signal provided by the other side (if that doesn't exist it will de-activate the card and retry after a fixed (small) interval to re-activate the card)it will force the cards speed at that setting
Duplex Negotiation :
In this case we get into a peer-to-peer negotiation sequence meaning that the card itself will send a packet to the other side requesting negotiation , the other side should do the same , if both reply correctly they then decide on the highest possible setting being FULL-DUPLEX .. if negotiation fails (several reasons are possible)several states of he card can be possible , this negotiation ask that not only the HP is capable of doing so but also the switch/router the system is connected to , if that isn't the case the negotiation will fail and depending on the driver version (make sure the latest arpa transport and lancard patch is installed) this could hang the card or more often result in factory default setting being 100HalfDuplex or 10HalfDuplex depending on the speed sensing
If duplex is completely mismatched then we can have any number of performanceor communication problems so the general rule is
HP9000 switch/router
AUTO ok AUTO
Fixed FD ok Fixed HD
Fixed FD ok Fixed FD
AUTO nok fixed
fixed nok AUTO
in the 2 last cases you will either fall back to 100MB/HD or get a card hang (with older unpacthed card software versions) , the message in your log indicates that the negotiation does fail so make sure you use the correct setting , take note that if you have a HUB it isn't capable of negotiating and is most probably HalfDuplex , fixing the speed at the HP9000 happens in the /etc/rc.conf/d subdir in a file specifically for tyour lancard , these fales have the same naming policy and that policy = hp...conf
e.g hpeisa100btconf
in there one can change the cards mac-address but also put speed and duplex for the card , the correct options to do so are :
100FD
100HD
10FD
10HD
AUTO
(by default the cards are in AUTO)
If you later to a fixed setting make sure the port on the switch/router is set in exactly the same way , finally the message could be coming from the disactivated card if that is also a 100mb type of card , it can give that signal atr startup because even if no configuring happens it will poll the network to see if it is connected to a hub, switch or router