Operating System - OpenVMS
1752790 Members
5816 Online
108789 Solutions
New Discussion юеВ

Re: openVMS boot strap failure

 
SOLVED
Go to solution
Joseph Huber_1
Honored Contributor

Re: openVMS boot strap failure

The message
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).
http://www.mpp.mpg.de/~huber
nipun_2
Regular Advisor

Re: openVMS boot strap failure

Hi Joseph,
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





nipun_2
Regular Advisor

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

Terry Beales
Occasional Contributor

Re: openVMS boot strap failure

Hi,
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?
nipun_2
Regular Advisor

Re: openVMS boot strap failure

Thanks for the reply Terry,

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


Antoniov.
Honored Contributor

Re: openVMS boot strap failure

Nipun,
>>> 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
Antonio Maria Vigliotti
comarow
Trusted Contributor

Re: openVMS boot strap failure

Using lancp you can set the characteristics of the port.

If you use a Cisco switch the command show tech will diplay all the setting ( and nothing confidential).