- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- %EWA0 possible duplex mode mismatch condition dete...
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
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
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-14-2007 01:17 AM
тАО03-14-2007 01:17 AM
%EWA0 possible duplex mode mismatch condition detected
I just loaded update 900 and a few other patches on some of my Alpha's running openVMS 7.3-2 and we are getting this message occasionally on the consoles (%EWA0 possible duplex mode mismatch condition detected). There does not seem to be any performance issue or strange counter numbers on the Nic cards in question. Is this possibly a condition that was always there and is just being logged now with the new patches. The Alpha's in question are on different networks and in differnet data centers. I looked around for this error but have yet to find anything specific.
Thanks
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 01:37 AM
тАО03-14-2007 01:37 AM
Re: %EWA0 possible duplex mode mismatch condition detected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 01:44 AM
тАО03-14-2007 01:44 AM
Re: %EWA0 possible duplex mode mismatch condition detected
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 01:44 AM
тАО03-14-2007 01:44 AM
Re: %EWA0 possible duplex mode mismatch condition detected
I'd be inclined to look at the output of MC LANCP SHOW DEV/COUNT. If you've looked already and the counters look clean, that's odd.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 01:55 AM
тАО03-14-2007 01:55 AM
Re: %EWA0 possible duplex mode mismatch condition detected
This message and this detection is a V8.2 feature, and it looks like it's been backported.
I'd check the settings on the switch and on the card at a start, and verify that they match. LANCP can show the NIC settings.
Certain of the older cards don't negotiate all that well -- the FAQ has the matrix of DE500, and the DE500 series uses EW driver. Some of the cards auto-detect speed, and some auto-negotiate duplex, and some DE500 NICs manage both. And then there can be manual settings on the switch or the NIC which can override this, which can be at the switch, or most any NIC around.
The DE500 rated its own section in the OpenVMS FAQ because of auto-detect and auto-negotiate.
You can use LANCP to set and show the NIC settings, and you can use SRM console environment variables to select the NIC behavior.
Check the NIC and the switch.
Stephen Hoffman
HoffmanLabs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 02:18 AM
тАО03-14-2007 02:18 AM
Re: %EWA0 possible duplex mode mismatch condition detected
I cannot get into the alpha at my other site at this time.
AUG$ mc lancp
LANCP> show dev/param ewa0
Device Characteristics EWA0:
Value Characteristic
----- --------------
1500 Device buffer size
Normal Controller mode
External Internal loopback mode
00-16-35-3E-0B-FB Hardware LAN address
Multicast address list
CSMA/CD Communication medium
FF-FF-FF-FF-FF-FF Current LAN address
128 Minimum receive buffers
256 Maximum receive buffers
Yes Full duplex enable
Yes Full duplex operational
TwistedPair Line media type
100 Line speed (mbps)
Disabled/No Failset Logical LAN state
0 Failover priority
Device Counters EWA0:
Value Counter
----- -------
742319 Seconds since last zeroed
632755804 Bytes received
1026765093 Bytes sent
6668058 Packets received
4533370 Packets sent
163935213 Multicast bytes received
4308653 Multicast bytes sent
2429933 Multicast packets received
75139 Multicast packets sent
2 Unrecognized unicast destination packets
371463 Unrecognized multicast destination packets
0 Unavailable station buffers
0 Unavailable user buffers
245 Alignment errors
11122 Frame check errors (14-MAR-2007 10:00:16.22)
0 Frame size errors
0 Frame status errors
0 Frame length errors
0 Frame too long errors
0 Data overruns
0 Send data length errors
0 Receive data length errors
0 Transmit underrun errors
0 Transmit failures
0 Carrier check failures
0 Station failures
0 Initially deferred packets sent
0 Single collision packets sent
0 Multiple collision packets sent
0 Excessive collisions
0 Late collisions
0 Collision detect check failures
1 Link up transitions ( 5-MAR-2007 19:42:17.52)
0 Link down transitions
None Time of last generic transmit error
None Time of last generic receive error
LANCP> exit
AUG$ sho sys/noproc
OpenVMS V7.3-2 on node AUG 14-MAR-2007 10:05:30.43 Uptime 8 14:23:23
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 02:46 AM
тАО03-14-2007 02:46 AM
Re: %EWA0 possible duplex mode mismatch condition detected
Lancp> sho dev/params shows that it is 100 full duplex and does not say anything about Auto so I am assuming ega0_mode is hard set to 100mbs full duplex.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 05:06 AM
тАО03-14-2007 05:06 AM
Re: %EWA0 possible duplex mode mismatch condition detected
network flakiness which is being
misinterpreted. Around here:
14914392 Seconds since last zeroed
26756338092 Bytes received
36475621960 Bytes sent
107439829 Packets received
163219332 Packets sent
846741906 Multicast bytes received
852344449 Multicast bytes sent
15530177 Multicast packets received
6960234 Multicast packets sent
[...]
0 Alignment errors
0 Frame check errors
[...]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 05:08 AM
тАО03-14-2007 05:08 AM
Re: %EWA0 possible duplex mode mismatch condition detected
the LAN drivers keep the most recent messages issued on OPA0: in memory for you to look at with:
$ MC LANCP SHOW DEV/INTERNAL ewa
This information should indicate, whether the NIC was set to auto-negotiate at console level. It also shows the auto-negotiation settings at the NIC level.
The NIC is seeing FC and alignment errors, so there seems to be something wrong...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2007 05:30 AM
тАО03-14-2007 05:30 AM
Re: %EWA0 possible duplex mode mismatch condition detected
If there's a mismatch it's going to be because the switch end is set half-duplex or autonegotiate.
I would be half inclined to set the Alpha briefly to autonegotiate with LANCP, and see if it succeeds. Or get someone to double check the equivalent configuration and statistics at the far end.