- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Tset problem
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
тАО10-10-2005 11:20 PM
тАО10-10-2005 11:20 PM
Tset problem
I have very strange problem. On customer site I installed some RPM packages from freeware CD (lsof, zsh, ncftp, syd, top, monitor, vmubc, xfsm). I did it on two DS15 (single machines) and on Cluster (2 X ES47 + EVA3000). Also rebuilt kernels to include packetdriver. OS version is V5.1b PK5.
Everything is OK with both DS15, but on cluster machines there is a problem. When user logins, gets message: Type dtterm (or vt100) unknown.
It is still in test condition, so there is enough time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2005 11:24 PM
тАО10-10-2005 11:24 PM
Re: Tset problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2005 11:53 PM
тАО10-10-2005 11:53 PM
Re: Tset problem
Sounds like your termcap file ( /usr/share/lib/termcap ) is broken, or maybe there is something wrong with the softlink /etc/termcap whcih should point back to it?
The termcap file (man termcap) should have entries for vt220 and vt240 pointing on to vt200 for which the capabilities are defined on top of the vt100 stuff which is where the buck stops.
xterm has its own complete definition.
fwiw,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2005 11:56 PM
тАО10-10-2005 11:56 PM
Re: Tset problem
I wrote "The message probably comes from the 'setup' program. (or possible 'resize')."
And then after the submit I noticed the title!
At first observation I had thought that 'tset' was a misspelling of test like I do myself. Now it is obvious it was simple a reference to the tool that reports the error. Sorry 'bout that.
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2005 12:18 AM
тАО10-11-2005 12:18 AM
Re: Tset problem
And why is second node working so slow? Is there a bug?
Should I recreate the cluster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2005 01:06 AM
тАО10-11-2005 01:06 AM
Re: Tset problem
Are you using Lan Interconnect or memory channel interconnect?
Check your lan interconnect, switch configuration, network adapter speed (set manually in the adapter and the switch), use lan_config, etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2005 02:42 AM
тАО10-11-2005 02:42 AM
Re: Tset problem
I also thought it was cluster interconnect. It is LAN (gigabit) interconnect (it is DEGXA-SB and fibre crossover cable, ant it worked OK till nowdays).
But "netstat -a -I bcm0" shows:
# netstat -a -I bcm0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
bcm0 1500 00:10:18:10:01:20 293079 0 293011 0 0
09:00:2b:02:01:04
09:00:2b:00:00:0f
01:00:5e:00:00:01
cf:00:00:00:00:00
bcm0 1500 DLI none 293079 0 293011 0 0
bcm0 1500 192.168.8 member2-icstcp0 293079 0 293011 0 0
all-systems.mcast.n
# netstat -a -I bcm0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
bcm0 1500 00:10:18:10:01:20 293795 0 293740 0 0
09:00:2b:02:01:04
09:00:2b:00:00:0f
01:00:5e:00:00:01
cf:00:00:00:00:00
bcm0 1500 DLI none 293795 0 293740 0 0
bcm0 1500 192.168.8 member2-icstcp0 293795 0 293740 0 0
all-systems.mcast.n
So there are no errors or am I wrong?
These card are set to 1000mbps fullduplex by console.
Did your nodes also work slow, not just booted slow?
I will change the crossover cable tomorow but I am not sure this would help.
Something cunfused me very much: how could termcap file get corrupted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2005 09:20 PM
тАО10-11-2005 09:20 PM
Re: Tset problem
When I boot a node first (no matter what node), it boots fast and works fast. And when I boot other node, boot is extremely slow and works slow. When I shutdown first booted node, second starts to work fast. I changed cluster interconnect cable, but no change. Looks like cluster interconnect is working OK.
I was wrong when I said it is EVA3000. It is EVA4000 (sorry, sintax error). Both nodes have netrain interfaces for corporate network.
Any idea?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2005 10:41 PM
тАО10-11-2005 10:41 PM
Re: Tset problem
I do not know what happened. This should not have anything to cfs.
Does anyone know is there a bug or PK5 has some strange behavior?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2005 12:54 AM
тАО10-14-2005 12:54 AM