Operating System - Tru64 Unix
1753774 Members
7017 Online
108799 Solutions
New Discussion юеВ

Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

 
Thor Thorvaldsen
Occasional Advisor

Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

After changing to LAG our XWINDOWS console does not function properly. The CDE does not come up as usual. Changing back to NetRAIN does fix the problem with the console.

What is happening here? Should this work
"out of the box"?

Sincerely,
Thor
10 REPLIES 10
Vladimir Fabecic
Honored Contributor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

This should work OK.
I used LAG on Tru64 5.1b PK-5 and it worked OK. Had to change to NetRAIN because of network infrastructure change.
Are you sure you did everything right?
In vino veritas, in VMS cluster
Thor Thorvaldsen
Occasional Advisor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Yes, i do think so. Then lag interface functionproperly regarding communication.
But the CDE/Xwindows console does not.

I register that the console switches to graphical modus but the X/CDE does not appear as expected.

Any suggestion on the X config?
Vladimir Fabecic
Honored Contributor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

I would like to see more details.
How did you configure LAG?
What did you put in rc.config?
In vino veritas, in VMS cluster
Thor Thorvaldsen
Occasional Advisor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Ok,
I didnt touch rc.config for lag, i only removed NetRain config.
I put lagconfig into inet.local:

lagconfig -c lag=lag0,key=1,dist=port
ifconfig alt0 down
lagconfig -p alt0 lag=lag0
ifconfig alt1 down
lagconfig -p alt1 lag=lag0
ifconfig lag0 192.168.10.10/24 up

Was this the sound think to do?
Vladimir Fabecic
Honored Contributor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Looks OK
My idetd.local was:
echo "Starting Ethernet LAG."
ifconfig ee0 down speed 200
ifconfig ee2 down speed 200
lagconfig -c lag=lag0
lagconfig -c dist=roundrobin
lagconfig -p ee0 key=1
lagconfig -p ee2 key=1
ifconfig ee0 up
ifconfig ee2 up
ifconfig lag0 10.0.0.1 netmask 255.255.255.0

Network interfaces has to be unconfigured (no entry in rc.config).
Please describe console problem with more details. Does X console start and you can not login or what?
In vino veritas, in VMS cluster
Thor Thorvaldsen
Occasional Advisor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Thank for confirming lag configuration!

No i cannot login to the CDE. It seems to me that X is trying to start. I observe the console switching to graphical mode. (The fonts changes). But there is no Xwindows/CDE interface opening up. We have disabled telnet protocol and are running on SSH for remote access. Could this be part of problem?

Vladimir Fabecic
Honored Contributor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

I do not think that disabling telnet should be a problem.
Pleblem is somewhere in network settings.
Any messages in log?
Idea:
Prevent X from startup at boot and catch error messages.
In vino veritas, in VMS cluster
Al Licause
Trusted Contributor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Try posting an error message or two if you are getting any and/or the results...timeouts, etc.

Try running tcpdump on both interfaces in the lag set to see if you can determine what may be happening to the packets.
Thor Thorvaldsen
Occasional Advisor

Re: Link aggregation protocol on Tru64 5.1b PK-5 & Xwindows

Thanx for the suggestion, but it's not the X external which is malfunctioning. It's the direct connected console. We have graphic cards and usb mouse/keyboard attached.

And i do not have any error messages, only X does not appear. It's a bummer, i must return to netrain and only 1Gb comm.