- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: openVMS boot strap failure
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
тАО06-05-2005 04:11 AM
тАО06-05-2005 04:11 AM
Re: openVMS boot strap failure
ewa0: link failed: Using 100BaseTX:full duplex.
clearly indicates the ethernet link is not working.
Now this not necessarily means the interface or cable broken, it may just be a protocol mismatch between the ewa0 interface and the gigaswitch.
Is the 100mbit full duplex set in the ewa0_mode variable or the result of autonegotiation ?
Do a SHOW ewa0* to see, and then try the variations
set ewa0_mode auto / fast / fast_fdx
(I'm not quite sure about the syntax, SRM should tell You the options if they are wrong).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-06-2005 02:26 AM
тАО06-06-2005 02:26 AM
Re: openVMS boot strap failure
You are right I think it is more of a network problem. Does the info I pasted before (again pasting it for convenience)
Also I have been using
2608 (Gigabit Ethernet switch) which has TWO green (indicating Gb data transfer) blinking leds however for the Sat 2 cable only ONE amber colored (indicating 100 Mb data transfer?)
So looks like this
SPD/LNK/ACT Green(blinks) Green(blinks) Amber (blinks)
FDX/HDX Green(blinks) Green(blinks) NO LIGHT
Thus (I think) it clearly indicates that Main server has no link with Sat2
Regardig ewa0 mode
I did sh ewa0* and it displayed
ewa0_mode Auto Negotiate
I did set ewa0_mode Fast
but it did not make a difference
when I again did
set ewa0_mode Auto
It negotiated and then gave
Auto-Negotiate and 100 Mbps full
Note: The above mode has been working perfectly fine to date, so I don't think changing it would make any difference. But if you feel it might please let me know.
The following modes are available
Twisted-Pair
Full Duplex, Twisted-Pair
AVI
BNC
Fast
Fast FD (Full Duplex)
Auto-Negotiate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-06-2005 02:37 AM
тАО06-06-2005 02:37 AM
Re: openVMS boot strap failure
Hi,
I think the description of the led lights I gave before is confusing. Please have a look at the attached txt file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-06-2005 09:09 PM
тАО06-06-2005 09:09 PM
Re: openVMS boot strap failure
I run a large cluster with _many_ satellite nodes & have occasionally had similar symptoms to yours on the odd node - one cause has been too many satellite nodes attempting to boot simultaneously (obviously not the cause in your case), another seems to be a poor quality network connection - setting EWA0_MODE to twisted pair will often 'fix' this - albeit with reduced performance. Otherwise, if I still can't get a MOP load, I call in the network tech. to test the connections with a fluke - this often identifies a dodgy cable or connection.
Incidentally - are both your satellites identical hardware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2005 01:02 AM
тАО06-07-2005 01:02 AM
Re: openVMS boot strap failure
My Main Server is DS25
Sat1 - EV 68 (DS 25)
Sat2 - XP1000 (few years old)
I can provide more specifications if you need.
I tried to boot with Twisted Pair
set ewa0 Twisted-Pair
The light FDX/HDX still did not come to life.
What is the reason for the FDX/HDX light to go off?
Does it show error on the side of the Sat2 node or error on the side of the server node or the switch itself.
If anyone has any idea please let me know
Nipun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2005 03:55 AM
тАО06-07-2005 03:55 AM
Re: openVMS boot strap failure
>>> set ewa0 twisted_pair
set network device to 10mbs, half-duplex on my machine.
I guess you have to set auto mode; you can type
>>> set ewa0
and see the various options you can type.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2005 03:33 PM
тАО06-08-2005 03:33 PM
Re: openVMS boot strap failure
If you use a Cisco switch the command show tech will diplay all the setting ( and nothing confidential).
- « Previous
-
- 1
- 2
- Next »