06-19-2018
Quote:
Originally Posted by
goya
no support since its older. just a company that swaps parts. I did try the power on each domain and same result , did no reset fault, what command does that? I will try and find it.
From the XSCF use the command
version -c xcp and send the output. Depending on the version you might not be able to reset the error...
This User Gave Thanks to DukeNuke2 For This Post:
9 More Discussions You Might Find Interesting
1. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
2. Solaris
Hi,
I 've a fully loaded M5000 which i would like to partition in 4 domains but i have a concern that since we have only 4 internal disks how can we partition the box in for domains with 2 disks ( mirrored ) in each domain. Should i go ahead with 1 Lun from SAN and 1 internal disk for each of 4... (3 Replies)
Discussion started by: fugitive
3 Replies
3. Solaris
Hi i 've a M5000 running 2 domains in my Lab with following hardconf
SPARC Enterprise M5000; Memory_Size:128 GB;
+-----------------------------------+------------+
| FRU | Quantity |
+-----------------------------------+------------+
| MBU_B... (3 Replies)
Discussion started by: fugitive
3 Replies
4. Solaris
Please advise. Thank you
bash-3.00# cd /usr/sunvts/bin/
bash-3.00# ls
bios.bin iobushangscript.sh stopsunvts vtsprobe
cmos.bin javabridge.jar sunlink vtsreportgenerate
dispatcher loadVtsServer svmVolDiskList vtstalk
env6test... (6 Replies)
Discussion started by: incredible
6 Replies
5. Hardware
I have an M5K with disk issues I'm trying to troubleshoot, and it's causing me some confusion. I know the host has four on-board HDDs, but the format command's output shows c0t0d0, c0t1d0, c3t0d0, and c3t1d0. cfgadm -al shows c0t3d0 as the DVD-ROM drive, and c1 and c2 as SAN disks. Confused yet?
... (2 Replies)
Discussion started by: desertdenizen
2 Replies
6. IP Networking
I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip.
it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out.
so my question is,
any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 Replies
7. Solaris
I have an m5000 that Is down.
I have access to XSCF>
and was able to get to the ok prompt.
However, on
>ok boot
it failed to boot.
erred with :
svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL.
Nov 29... (3 Replies)
Discussion started by: goya
3 Replies
8. AIX
A team member installed the wrong version of License Code on a Power 740 system used in our Development environment.
The system will no longer boot.
Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies
9. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
HY(4) Kernel Interfaces Manual HY(4)
NAME
hy - Network Systems Hyperchannel interface
SYNOPSIS
/sys/conf/SYSTEM:
NHY hy_controllers # Hyperchannel
DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.
The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by
reading the adapter status register. The interface will not transmit or receive packets until the network number is known.
DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
an 11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware.
hy%d: BAR overflow. Bus address register overflow error returned from hardware.
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut
down the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored.
SEE ALSO
intro(4N), inet(4F)
BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to
recognize it.
The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has
failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on
some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these
``bogus powerfails''. They don't seem to cause any real problems so they have been ignored.
3rd Berkeley Distribution August 20, 1987 HY(4)