Netra t1 105: Solaris 8 & 9 install failures

Hi Everyone,
I have two (2) Sun Netra T1 105 machines, each with a single 360MHz Ultra SPARC IIi and 256MB RAM. Both have 18.2GB drives that have been wiped clean.
I am connecting using Winblows 2000 and Hyperterminal, serial port B, 9600,8,n,1.
I want to install a fresh copy of Solaris 9 on these systems, but I am having absolutely no luck. I boot from the Solaris 9 install CD and the systems just hang. I've also tried to do network installs, and they hang as well.
I thought it might be my Solaris 9 install media, so I tried to install Solaris 8 using several different releases - 4/01, 10/01 & 2/02. Each time, I get the same result - the boxes just hang.
I make it this far (serial, MAC, and hostid x'ed out to keep our security folks happy):
Netra t1 (UltraSPARC-IIi 360MHz), No Keyboard
OpenBoot 3.10.25 ME, 256 MB memory installed, Serial #XXXXXXXX.
Ethernet address 8:0:20:XX:XX:XX, Host ID: XXXXXXXX.
ok boot cdrom
Boot device: /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f File and args:
SunOS Release 5.9 Version Generic 64-bit
Copyright 1983-2002 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
And then it hangs forever. In the OBP, I've set the input and output ttys to ttyb to eliminate LOM interference.
Here is a snapshot of the printenv output:
ok printenv
Variable Name Value Default Value
tpe-link-test? true true
scsi-initiator-id 7 7
keyboard-click? false false
keymap
watchdog-timeout 65535 65535
watchdog-enable? false false
ttyb-rts-dtr-off false false
ttyb-ignore-cd false true
ttya-rts-dtr-off false false
ttya-ignore-cd false true
ttyb-mode 9600,8,n,1,- 9600,8,n,1,-
ttya-mode 9600,8,n,1,- 9600,8,n,1,-
cpci-probe-list 0,1,2,3,4,5,6,7,8,9,a,b, ... 0,1,2,3,4,5,6,7,8,9,a,b, ..
pcia-probe-list 1 1
pcib-probe-list 1,2,3 1,2,3
mfg-mode off off
diag-level min max
d7s-flipped? false false
#power-cycles 67
system-board-serial#
system-board-date
last-poweroff-cause 0 0
env-monitor disabled enabled
shutdown-temperature 74 72
warning-temperature 69 67
fcode-debug? false false
output-device ttyb ttya
input-device ttyb ttya
load-base 16384 16384
auto-boot-retry? false false
use-boot-table? false false
boot-command boot boot
auto-boot? false true
watchdog-reboot? false false
diag-file
diag-device net net
boot-file
boot-device disk net disk net
local-mac-address? true false
net-timeout 0 0
ansi-terminal? true true
screen-#columns 80 80
screen-#rows 34 34
silent-mode? false false
use-nvramrc? false false
nvramrc
security-mode none
security-password
security-#badlogins 21
oem-logo
oem-logo? false false
oem-banner
oem-banner? false false
hardware-revision
last-hardware-update
diag-switch? false false
I have the feeling I am missing something very simple, but I am at a loss. Any assistance is greatly appreciated!
Chad E. Carlson
Skandia Technology Center, Inc.
Shelton, CT USA

This could be part of the problem. How exactly did you wipe the disks in the other machine, and what type of machine was it?I installed the disks into a Sun Netra T1125, partioned (using format) and newfs'd them to create basic file systems.
How about a "boot cdrom -s"? If it boots this way, does "format" see the disks ok?Tried this, same result. The systems don't make it past the licensing terms message.
As for the mini tests - I ran them against every device, and everything seems OK. The floppy test threw an error because I didn't have a floppy drive installed.
I have a 4 port QFE card installed in the machine - all of the loopback tests passed, but the transceiver tests failed. None of the ports are connected (no cables). The two built in Ethernet ports also passed loopback, and 1 passed the transceiver test (the other failed) - the transceiver that passed has a network cable installed.
Testing /pci@1f,0/pci@1/pci@1/pci@f/SUNW,qfe@3,1
Internal loopback test -- succeeded.
Transceiver check -- failed
Selftest failed. Return code = -1
Testing /pci@1f,0/pci@1/pci@1/pci@f/SUNW,qfe@2,1
Internal loopback test -- succeeded.
Transceiver check -- failed
Selftest failed. Return code = -1
Testing /pci@1f,0/pci@1/pci@1/pci@f/SUNW,qfe@1,1
Internal loopback test -- succeeded.
Internal loopback test -- succeeded.
Transceiver check -- failed
Selftest failed. Return code = -1
Testing /pci@1f,0/pci@1/pci@1/pci@f/SUNW,qfe@0,1
Internal loopback test -- succeeded.
Transceiver check -- failed
Selftest failed. Return code = -1
Testing /pci@1f,0/pci@1,1/network@3,1
Internal loopback test -- succeeded.
Transceiver check -- failed
Selftest failed. Return code = -1
Testing /pci@1f,0/pci@1,1/scsi@2
Testing /pci@1f,0/pci@1,1/network@1,1
Internal loopback test -- succeeded.
Transceiver check -- passed
Could I be experiencing problems because of the QFE card?? Doesn't seem logical, but.... perhaps I will yank it out and try again....

Similar Messages

Netra T1 105 Solaris 10

Hi there,
I sucessfully installed Solaris 10 on my Netra T1 105, but when booting from the Jumpstart-Server, I saw that the machine tries to use old informations that seem to be stored on the hostid-chip. So, I wated to ask, if there's a documentation how to erase or modify this information (hostname, ip-addresses...).
Also I wated to know, if anybody has an idea of updating the installed LLOMLite Software?
Thanks for an answers
Thorsten

Well, the SPARC machines only stores one thing; their hostid and ethernet address (ok, thats two things). When you jumpstart a SPARC machine, it makes an ARP request with its ethernet address, and then the jumpstart server responds with a hostname, the client then uses the hostname to find its IP address.
So you probably got an old IP/Hostname on your jumpstart server, if you don't there is probably another server on your network which has old information.
As to LOM; there used to be a patch for it, cant remember which one though.

Netra t1 with solaris 9 fresh install on/standby switch

Hi,
I recently installed solaris 9 onto my Netra 105 box. For the likes off me I can't figure out why the on/standby switch simply does not work since reinstalling. The only way I can power down the box is by literally unplugging it from the wall. I am a total newbie to Sun boxes (& solaris for that matter) & have had zero luck in finding any info specific info relating to this. Can some kind soul put me on the right track?

I have down precisely what you have recommended & the thing still won't go into standby. After executing poweroff from the LOM prompt It just sits there continually humming away. Yet it worked fine prior to the installation off solaris 9 from solaris 8. I have even reinstalled again, this time making sure to include the power management options. All reinstalls were done with the "initial installation" option.
Here is a screen dump off the unit booting & me executing the poweroff commnd:
lom>reset
LOM event: host reset
Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard
OpenBoot 3.10.25 ME, 512 MB memory installed, Serial #14315586.
Ethernet address 8:0:20:da:70:42, Host ID: 80da7042.
Boot device: disk File and args:
SunOS Release 5.9 Version Generic_112233-05 64-bit
Copyright 1983-2002 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
configuring IPv4 interfaces: hme0.
configuring IPv6 interfaces: hme0.
starting DHCP on primary interface hme0
Hostname: unknown
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c0t0d0s7: is stable.
Starting IPv6 neighbor discovery.
Setting default IPv6 interface for multicast: add net ff00::/8: gateway fe80::a00:20ff:feda:7042
starting rpc services: rpcbind done.
Setting default IPv4 interface for multicast: add net 224.0/4: gateway 192.168.0.125
syslog service starting.
syslogd: line 24: WARNING: loghost could not be resolved
Jun 27 19:19:36 unknown /usr/lib/power/powerd: powerd: failed to get idle time for console mouse
volume management starting.
The system is ready.
unknown console login: root
Password:
Last login: Fri Jun 27 19:00:09 on console
Jun 27 19:19:55 unknown login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
# #.lom>poweroff
lom>
This problem is annoying the hell out off me. Everyone I have spoken to hasn't even heard off this problem.
Any other advice you can give would be very much appreciated.

Solaris 10 v440 install failure.

Hi,
Have a v440 which passes full diag routine. with brand new solaris 10 dvd received from sun, with a freshly formatted 9gb hdd.
When trying to bbot from the dvd, "boot cdrom", i get the following cycling through.
Hardware watchdog enabled
svc.configd: smf(5) database integrity check of:
/etc/svc/repository.db
failed. The database might be damaged or a media error might have
prevented it from being verified. Additional information useful to
your service provider is in:
/etc/svc/volatile/db_errors
The system will not be able to boot until you have restored a working
database. svc.startd(1M) will provide a sulogin(1M) prompt for recovery
purposes. The command:
/lib/svc/bin/restore_repository
can be run to restore a backup version of your repository. See
http://sun.com/msg/SMF-8000-MY for more information.
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
svc.configd exited with status 102 (database initialization failure)
svc.startd: Could not exec() sulogin: No such file or directory.
i have tried other dvd rom drives and other installtion media but am getting nowwhere.
Am newbie to solaris, Can anyone HELP!
Many Thanks.

many thanks those that looked, eventually found an obscure notice about date and time, corrected these and all is well.
Cheers

Solaris 10 clean Install failure

Downloaded Solaris 10, burned to CD, disc at once/96 and the CD was not recognised. Erased/burned disc at once, the install process started and continued about half way then froze as though caught in a loop. I attempted re-installing but it was a repeat performance!

Hi,
I have download the 4 cd for the Sparcversion, burn the iso image with Nero and all was good.
Are you sure of your download ??
Regards

Installing solaris 10 on netra t1 105

im need to sun computer system....i have got to the point of hyperterm lom> and booting the system, but it has no software installed.. im trying to install solaris on a sun netra t1 105 256 mb ram and 19gb hd and NO CDROM im trying to "network install" from a windows 2003 server.. is this possibly or do i have to a sun workstation to install as boot/install server... or could i connect the hard drive to a windows 2003 server and format and install solaris on it using virual pc.... i haveit networked to my wireless router as well a x86 computer...
Edited by: lebaronman on Feb 28, 2008 2:01 AM

I have no really good answer here..
I guess you are using a Netra T1 AC200, right?
Some futher questions;
Are you using an internal CD-Rom?
Have you tried the CD-Rom before so you know it works?
What happens if you try "boot cdrom" without inserting any CD? I think the bootpath to the cd-rom looks a bit strange, and testing that would be the easiest way of verifying if its correct or not. If the path is correct you should get a different error if you attemt to boot from a non-existing CD.
Last question; which Solaris 10 version did you download?
7/M.

Solaris 8 in Netra t1 105

Hi, all.
I get a couple of netra t1 105, and I'thinking about install Solaris 8 02/02.
Does the netra support that release?.
If so, need I patch them?.
Where can I get information about hardware platforms witch support Solaris 8. I didn�t find any about this in sunsolve.com
Any info is welcome.
Thanks all.

The SunSolve System Handbook will show you minimum OS requirements for any Sun machine. The sun4u architecture (includes Netra t1 105) is in no danger of going End Of Life any time soon as it is supported in Solaris 9 and future Solaris 10. The support for sun4d architecture (SPARC Center 1000 & 2000) got dropped in Solaris 9. sun4m architecture (SPARC 5, 10 & 20) may get dropped in Solaris 10 but the sun4u architecture will be around for a while. There hasn't been a new architecture released since sun4u so there's nothing to worry about for quite a while.See:
http://sunsolve.Sun.COM/handbook_pub/Systems/Netra_t1_105/Netra_t1_105.html

Netra t1 105 install solaris9 from terminal session

I have quite a problem, I am using a windows box hyper terminal into a netra t1 105 box and am able to boot up and log into the system, however as i am on a windows box i dont have the stop-a button to press when i power it down so as to boot from cdrom, I am trying to do a clean install of solaris 9 onto this box. It seems the more searching I do on this topic the more I hit my head against a brick wall....any help would be appreciated

I believe you're looking for the STOP+A equivalent on a serial line: send a BREAK signal on the serial line.
On some (but definitely not on all) windows versions, the bundled hyperterm can send a BREAK signal by
pressing "control + break". Last I've looked into this I tried Win95 and Win NT 4.0 (?), one hyperterm could
send a BREAK the other doesn't. But I don't remeber the details any more.
I just googled a bit, and this page suggest to upgrade hyperterm to some 5.0 revision, to enable the BREAK
signal:
http://accuratedatasystems.com/configure-9180-HyperTerm.htm

Clean install on Netra T1 105 using terminal service

Im using a windows hyper terminal session onto a Netra T1 105 and am able to boot and login as normal, however my problem lies with being able to do a fresh install from this terminal, on a normal sun box I shutdown and get the ok prompt and from there type boot cdrom, from the terminal i cant do this, how do i go about booting from a cdrom from the terminal
thanks in advance

Found that when terminalling into a box to execute the STOP-A command you must use Ctrl-Break

Netra T1 105, Unresponsive after installing LOM 2.0

I recently purchased a used Netra T1 105, which is running SunOS 5.9. After purchasing the server, I attempted to install the "Lights Out Management 2.0" software.
I then proceeded to attempt to upgrade the LOM firmware, by running "lom -G default". However, running the command produced the output "Image Checksum", then locked the system up. At which point, the system no longer responded via the network, or via console.
After waiting a while, hoping that it would prompt me to confirm the firmware update, I decided to power-cycle the server. (I was unable to escape to LOM at the console.) After the power-cycle, the console no longer responds, nor outputs anything. I am also unable to access the system via network, which I suspect may be caused by the system wanting to perform an fsck.
Any ideas on what could be wrong, and how to fix it? Thank You!

On second read Bill i see that as well.
This is going to be unrelated but your boot-device looks a bit strange as well. You are referencing different slices on the same disk, and then referencing the disk itself and then net.
boot-device=disk:b disk:a disk net
You would be ok with referencing disk and then net if the server is not mirrored. If the system is mirrored then you would want to reference that disk as well.
either :boot-device=disk net
or: boot-device=disk disk<number> net
But the next time it does it, you could try trying sync and trying to create a crash file. Once you have the crash files you can get these analysed.
As well as this pass the server through diagnostics 3 or 4 times and check the console outputs fro details.

Netra T1 105, issue with LOM prompt

Hello all,
I am having issue in accessing OK prompt from LOM menu. When I do the poweron, it sits on LOM event: power on. When I do, console it shows stand by. Please help me out here as I am working on making this server to respond. Thanks.

Hi. Could you tell me if patches 108620-04 or higher & 108673-02 or higher are already installed on the Netra t1 105?
*How to determine if the Netra[TM]T1 model 105 server PROM patches are current [ID 1010561.1]*
Description
How to determine if patches 108620-04 or higher & 108673-02 or higher are already installed on the Netra t1 105.
Steps to Follow
These two patches have to do with OBP(OpenBoot PROM) and the user prom.
108620-04 Hardware/PROM: Netra t1 Standalone User PROM Update
108673-02 Hardware/PROM: Netra t1 System PROM Update
108673-02 delivers OBP 3.10.27.
This can be checked via the OBP with the .version command.
OBP Example:
ok .version
Release 3.10.27 ME created 2000/06/22 16:45
OBP 3.10.27 2000/06/22 16:45
POST 1.17.0 2000/03/06 12:18
This can be checked via Solaris[TM] with: prtconf -V
Solaris[TM] Example:
# prtconf -V
OBP 3.10.27 2000/06/22 16:45
If you see Release 3.10.27 you do not need to install this patch.
108620-04 delivers the dropins
These can be checked at the ok prompt with the show-dropins command.
Example:
ok show-dropins
Dropins for Flash device: /pci@1f,0/pci@1,1/ebus@1/flashprom@10,0
Dropin name Size Checksum Date Date Version Vendor
created flashed
OBP 4a1bc cc30 06/22/2000 3.10.27
keyboards bf0 dd75
fonts af6 6b86
obdiag bd34 aec5
pci1002,5654 d34 7190
pci1002,4755 cb0 c382
pci1002,4750 1794 3f65
class060400 44e 17cc
userprom 246 b3ba
pci108e,1001 32a4 d714
pci1011,22 47e 69c9
pci1000,3 2824 feb4
class010100 1210 ce35
i2c 1fe 5a8f
i2c-cs2 1f4 bd2a
nvinit- 172 0 10/08/1999 00/00/0 0.0
POST 45340 519 03/06/2000 1.17.0
PROM size = 100000 bytes Available for Use = 3d958 bytes
Dropins for Flash device: /pci@1f,0/pci@1,1/ebus@1/flashprom@10,400000
Dropin name Size Checksum Date Date Version Vendor
created flashed
ebus-14.400000 b0 9fa6 06/09/1999 06/09/1999 1.0
SUNW,flapjack
probe+ 250 c2b5 01/06/2000 01/06/2000 2.0
SUNW,flapjack
banner- 1aa 6f35 12/10/1999 12/10/1999 1.0
SUNW,flapjack
tty-control 150 a863 12/01/1999 12/01/1999 1.0
SUNW,Flapjack
PROM size = 200000 bytes Available for Use = 1ff984 bytes
Dropins for Flash device: /pci@1f,0/pci@1,1/ebus@1/flashprom@10,800000
Dropin name Size Checksum Date Date Version Vendor
created flashed
PROM size = 200000 bytes Available for Use = 200000 bytes
ok
The part that is of interest is about two thirds of the way down to do
with ebus-14.400000, probe+, banner- and tty-control.
If the Checksum matches you you don't need to install this patch.
On the other hand it won't cause any problems to reinstall both patches.

Netra t1 105 keeps going into init 0 everynight without reason

I have Solaris 9 installed on a netra t1 105 which goes into half every night. I have turned off the power management and the logs in /var/adm/messages does not show anything unusual.
<div class="pre"><pre>Oct 19 14:16:25 dev-sol9 pseudo: [ID 129642 kern.info] pseudo-device: vol0
Oct 19 14:16:25 dev-sol9 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Oct 19 14:17:22 dev-sol9 sendmail[184]: [ID 702911 mail.alert] unable to qualify my own domain name (dev-sol9) -- using short name
Oct 19 14:17:22 dev-sol9 sendmail[183]: [ID 702911 mail.alert] unable to qualify my own domain name (dev-sol9) -- using short name
Oct 20 09:21:30 dev-sol9 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Version Generic_118558-14 64-bit
Oct 20 09:21:30 dev-sol9 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.</pre></div>
<div class="pre"><pre>bash-2.05# eeprom
tpe-link-test?=true
scsi-initiator-id=7
keyboard-click?=false
keymap: data not available.
watchdog-timeout=65535
watchdog-enable?=false
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
cpci-probe-list=0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f
pcia-probe-list=1
pcib-probe-list=1,2,3
mfg-mode=off
diag-level=max
d7s-flipped?=false
#power-cycles=332
system-board-serial#: data not available.
system-board-date: data not available.
last-poweroff-cause=0
env-monitor=enabled
shutdown-temperature=72
warning-temperature=67
fcode-debug?=false
output-device=ttya
input-device=ttya
load-base=16384
auto-boot-retry?=false
use-boot-table?=false
boot-command=boot
auto-boot?=true
watchdog-reboot?=false
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=disk:b disk:a disk net
local-mac-address?=false
net-timeout=0
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
silent-mode?=false
use-nvramrc?=true
nvramrc=devalias ide-cdrom /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f
security-mode=none
security-password: data not available.
security-#badlogins=1074790400
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
hardware-revision: data not available.
last-hardware-update: data not available.
diag-switch?=false</pre></div>

On second read Bill i see that as well.
This is going to be unrelated but your boot-device looks a bit strange as well. You are referencing different slices on the same disk, and then referencing the disk itself and then net.
boot-device=disk:b disk:a disk net
You would be ok with referencing disk and then net if the server is not mirrored. If the system is mirrored then you would want to reference that disk as well.
either :boot-device=disk net
or: boot-device=disk disk<number> net
But the next time it does it, you could try trying sync and trying to create a crash file. Once you have the crash files you can get these analysed.
As well as this pass the server through diagnostics 3 or 4 times and check the console outputs fro details.

D130 multihosted with 2 Netra t1 105

Hi Guru's,
I want to setup an Sun Cluster for testing purposes and have the following
hardware to use :
- 2xNetra t1 105 1GB/2x18GB/1Gigabit Adapter (for Interconnect)
- Netra st d130 Storage (3x18GB). (just one)
When I try to setup the d130 I get an SCSI-Error.
I have changed the scsi-initiator-id from one host from 7 to 6 to avooid
conflicts, but still it fails.
I did the same with 2 220R and a MultiPack as Storage and with this
configuration it worked.
So, now here are my questions :
Is the configuration working with the 220R because the 220R has 2 channels on the SCSI bus and therefore it can handle such configueation. Unfortunatelly i am not very familiar with SCSI.
It looks like the internal drives (SCSI 0 and 1) are causing the Problem with the Netras. I think it has to do with the fact that the Netras does not have 2 SCSI channels - pls correct me if i am wrong!
Can you image that such a configuration (2x105 + d130) works?
Do you think I need another SCSI-Adapter (to have 2 channels)?
Is it possible to change the SCSI-ID of the internal drives (maybe this would avoud the conflict of the ID's) ?????
Every hint is verya, very welcome!!!
Please let me know what information you need to be abele to help me further - I will provide this information asap!
Thanks in advance for your valueable feedback!
Rainer
NOKIA

Hi!
Thanks for your reply!
The d130 is currently set to assign SCSI-ID's 10,11,12!
When I just connect one Server to the d130 and so a probe-scsi-all the System can find 2 internal (Netra t1 105) and 3 external (d130) disks on the SAME controller. When I do the same on the other node, I also get 5 disks (2+3) on the SAME controller.
The internal disks always have SCSI-Id 0 and 1.
That worries me since when I connect both Servers on the d130, the other node can not boot - which is imho because SCSI.-ID 0 and 1 (the internal disks) are assigned twice and the scsi-chain gets confused.
Normally a system distinguishes between the internal SCSI-chain and the external chain - pls. correct me if i am wrong!
It looks like an Netra t1 105 has all on one chain and therefore it conflicts with the internal disks ???
Am i talking bullshit or can it be that my assumption is right ??
Is there a way to change the SCSI-ID of the internal disks??
Di I have to install another SCSI-Adapter to be able to distinguish between internal end external drives and to avoid conflicts???
Please let me know if you need futher information about setp and/or configuration ...
Rainer

D130 multi hosted on Netra t1 105

Hi Guru's,
I want to setup an Sun Cluster for testing purposes and have the following
hardware to use :
- 2xNetra t1 105 1GB/2x18GB/1Gigabit Adapter (for Interconnect)
- Netra st d130 Storage (3x18GB). (just one)
When I try to setup the d130 I get an SCSI-Error.
I have changed the scsi-initiator-id from one host from 7 to 6 to avooid
conflicts, but still it fails.
I did the same with 2 220R and a MultiPack as Storage and with this
configuration it worked.
So, now here are my questions :
Is the configuration working with the 220R because the 220R has 2 channels on the SCSI bus and therefore it can handle such configueation. Unfortunatelly i am not very familiar with SCSI.
It looks like the internal drives (SCSI 0 and 1) are causing the Problem with the Netras. I think it has to do with the fact that the Netras does not have 2 SCSI channels - pls correct me if i am wrong!
Can you image that such a configuration (2x105 + d130) works?
Do you think I need another SCSI-Adapter (to have 2 channels)?
Is it possible to change the SCSI-ID of the internal drives (maybe this would avoud the conflict of the ID's) ?????
Every hint is verya, very welcome!!!
Please let me know what information you need to be abele to help me further - I will provide this information asap!
Thanks in advance for your valueable feedback!
Rainer
NOKIA

Hi!
Thanks for your reply!
The d130 is currently set to assign SCSI-ID's 10,11,12!
When I just connect one Server to the d130 and so a probe-scsi-all the System can find 2 internal (Netra t1 105) and 3 external (d130) disks on the SAME controller. When I do the same on the other node, I also get 5 disks (2+3) on the SAME controller.
The internal disks always have SCSI-Id 0 and 1.
That worries me since when I connect both Servers on the d130, the other node can not boot - which is imho because SCSI.-ID 0 and 1 (the internal disks) are assigned twice and the scsi-chain gets confused.
Normally a system distinguishes between the internal SCSI-chain and the external chain - pls. correct me if i am wrong!
It looks like an Netra t1 105 has all on one chain and therefore it conflicts with the internal disks ???
Am i talking bullshit or can it be that my assumption is right ??
Is there a way to change the SCSI-ID of the internal disks??
Di I have to install another SCSI-Adapter to be able to distinguish between internal end external drives and to avoid conflicts???
Please let me know if you need futher information about setp and/or configuration ...
Rainer

Setting up a netra t1 105

all, i've got a netra t1 105 and am having trouble setting it up. i understand from the documentation that i can connect another sun box to it using the serial port. so i am doing just that with an ultra5 i have. i am using a null modem cable with db9 connectors, a straight-through cat-5 cable, and a db9-rj45 adapter to connect the two boxes. i have edited the /etc/remote file on the ultra5, changing the 'hardwire' line to use /dev/term/a like it says in the documentation for the netra. when i use "tip hardwire" on the ultra5, i get nothing. it says "connected" but there is nothing i can do except exit out of tip. i have also used /dev/term/b in /etc/remote). is there a flaw in my procedure? or is the netra dead? or something else? thanks.

Regardless your method to connect,
serial or bi-directional parallel or network,
for whatever task you might be doing,
on whatever hardware,
a direct cable will need to be a cross-over in some form
if you hope for two systems to be able to communicate.
Send from A must go to Receive on B.
Send on B must return to Receive on A.
If you choose to use a CAT5 cable, it needs to be a cross-over cable,
else you go through a hub or switch, which will do the "crossing" for you.
As to your other question...
If you hope to connect to ANY functional OS on a system by using networking protocols through network capable circuitry (Solaris or not Solaris), you can telnet or SSH to it and just log in as a proper pre-existing user. That's a capability of an OS, even an embedded one such as is on a LOM or RSC or System Controller.
=====
The Sun system described in the original question will default its console to TTYa and not to its Ethernet port. It expects to communicate through proven (generic?) serial 9600,n,8,1 methodology. You'd be welcome to try the network connection but I don't think it'll work until you somehow reconfigure it to be your console, (but you would need to make a connection if you hope to reconfigure something).
My supposition with the original poster is that they somehow crossed their crossover and gave themselves a straight connection. Perhaps their RJ45-DB9 adapter was also a crossover device.
They haven't returned to update us with information on their progress.

Netra t1 105: Solaris 8 & 9 install failures

Similar Messages

Maybe you are looking for