Sun Trunking 1.& kern Warning Hardware address trying to be our IP addresse

Using Sun Trunking 1.3 on a solaris 10 11/06 V490 server.
setenv local-mac-address? is set to true
Obviously server Aggregate MAC address corresponds to first NIC local MAC address. Second NIC has its specific MAC address.
Aggregate seams OK (traffic continues undisrupted when unplugging a card)
but :
1) Should I worry kernel is logging from toime to time messages such as :
WARNING: IP: Hardware address '00:14:4f:3b:60:f4' trying to be our address IP_address !
2) There is no load balancing between the 2 NIC interfaces as reported by nettr -stats 0 interval=2
Traffic always flows using NIC 2.
Appreciated,
Lor.

That depends on the switch.
SunTrunking 1.3 is compatible with Cisco EtherChannel for example. I believe there's a manual configuration on the switch to say that these two ports are participating in an etherchannel linkage. SunTrunking is an 802.11ad protocol. If they haven't done that, then the switch is just assuming the two ports are normal and have separate hosts behind them.
If instead of SunTrunking you were using Solaris 10 Link Aggregation, then you'd ask the networking guys to turn on LACP, which sets up a communication so the devices can describe their trunk/network setup. SunTrunking doesn't let you do that.
What interfaces do you have on the Solaris box?
Darren

Similar Messages

  • Hardware address trying to be our address

    We get this kern.warning approximately every 3/4 of an hour.
    WARNING: IP: Hardware address '08:00:20:c4:1f:e8' trying to be our address 192.168.001.001
    I found a description on sunsolve. What confuses me with this is the fact, that not only 192.168.001.001 is our address but 08:00:20:c4:1f:e8 is our hardware address too.
    Has anyone made some experiences with this?
    Thanks in advance
    Frank

    If you are trying to use SunTrunking or link aggregation, yes, the switch or network device must be configured to support it as well.
    Otherwise one link sends a packet, the switch doesn't realize the links are to the same logical interface and returns the packet on the other link. The host sees the return packet and complains about an IP conflict.
    For SunTrunking you probabaly have to configure etherchannel (or the equivalent) manually. For link aggregation you probably want to configure LACP to get the link correct.
    Darren

  • WARNING: IP: Hardware address '08:00:20:c4:1f:e8' trying to be our address

    ""ERROR""
    WARNING: IP: Hardware address '08:00:20:c4:1f:e8' trying to be our address 192.168.001.001
    I have 2nodes of Sun solaris9 and both are configured in Veritas Cluster. The cluster nodes have 2 heartbeats connected cross.
    The cross cables are connected with the below IP's
    LAN1 of node1 192.168.2.1
    LAN2 of node1 192.168.2.2
    LAN1 of node2 192.168.1.1
    LAN2 of node2 192.168.1.2
    All the above LAN are connected with cross but still there is ip conflict message in the dmesg. The error is mention above

    Ok, my mistake.
    So that PC is also trying to use 192.168.0.1.
    And it must be doing arp broadcasts on the LAN.
    Solaris should probably be ignoring them since it has an 10.x.x.x address on the lan. So it shouldnt care about 192.168.0.x addresses on the LAN.
    Only on the crossover network.
    But apparently it cares anyway.
    So I suggest you change the cluster heartbeat addresses to something else thats less likely to be chosen by random computers on your lan.
    Or figure out why the PC is trying to use 192.168.0.1. It could be someone running vmware or virtual box.
    Or vlan you lan, so your critical servers arent sharing a network with random poorly configured PC's.

  • WARNING:IP: Hardware address '02:bf:0a:d0:00:2a' trying to be our address

    Hi,
    When my system boots up the following error message is prompted:
    WARNING:IP: Hardware address '02:bf:0a:d0:00:2a' trying to be our address
    I perused documentation and it states that this occurrs when the ATM lane device is set to promiscuous mode by running snoop -d lane0. The corrective action to be taken should be to not ket the ATM lane device rin in promiscuous mode & not to ignore the warning.
    What I want to know is how to implement the resolution?
    Thanks!

    Ok, my mistake.
    So that PC is also trying to use 192.168.0.1.
    And it must be doing arp broadcasts on the LAN.
    Solaris should probably be ignoring them since it has an 10.x.x.x address on the lan. So it shouldnt care about 192.168.0.x addresses on the LAN.
    Only on the crossover network.
    But apparently it cares anyway.
    So I suggest you change the cluster heartbeat addresses to something else thats less likely to be chosen by random computers on your lan.
    Or figure out why the PC is trying to use 192.168.0.1. It could be someone running vmware or virtual box.
    Or vlan you lan, so your critical servers arent sharing a network with random poorly configured PC's.

  • Nettr: ioctl failed: I/O error  - when configuring sun trunking

    Hello,
    I'm having a problem while trying to get sun trunking 1.3 configured. I'm getting the error, "/etc/opt/SUNWconn/bin/nettr: ioctl failed: I/O error" when executing the command, " /etc/opt/SUNWconn/bin/nettr -setup 0 device=qfe members=0,1,2,3 policy=1 lacp=p ptimer=1".
    I have an Ultra 80 with an installed qfe card. I can see the instances of the qfe in /etc/path_to_inst, and the card is currently unplumbed.
    The installation of Sun trunking 1.3 was fine and I rebooted the system prior to running the nettr command.
    Anyone seen this problem before. Any help would be appreciated.

    "If I guess correctly you are saying that in order for this to work the switch needs to support aggregation as well?"
    Yes. I had to have the four ports on my Cisco setup to accept aggregation. I believe it is because they are being presented with the same MAC address. Here are what my ports look like:
    CoreB#show run int gi5/17
    Building configuration...
    Current configuration : 190 bytes
    interface GigabitEthernet5/17
    switchport access vlan 10
    switchport trunk encapsulation dot1q
    switchport mode dynamic desirable
    spanning-tree portfast
    channel-group 6 mode active
    end
    CoreB#show run int gi5/18
    Building configuration...
    Current configuration : 190 bytes
    interface GigabitEthernet5/18
    switchport access vlan 10
    switchport trunk encapsulation dot1q
    switchport mode dynamic desirable
    spanning-tree portfast
    channel-group 6 mode active
    end
    CoreB#show run int gi6/17
    Building configuration...
    Current configuration : 190 bytes
    interface GigabitEthernet6/17
    switchport access vlan 10
    switchport trunk encapsulation dot1q
    switchport mode dynamic desirable
    spanning-tree portfast
    channel-group 6 mode active
    end
    CoreB#show run int gi6/18
    Building configuration...
    Current configuration : 190 bytes
    interface GigabitEthernet6/18
    switchport access vlan 10
    switchport trunk encapsulation dot1q
    switchport mode dynamic desirable
    spanning-tree portfast
    channel-group 6 mode active
    end

  • Scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):

    ug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
    Aug 12 14:00:36 gtcerp1      Connected command timeout for Target 6.0
    Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
    Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: Connected command timeout for Target 6.0
    Aug 12 14:00:36 gtcerp1 glm: [ID 280919 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6017]
    Aug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
    Aug 12 14:00:36 gtcerp1      got SCSI bus reset
    Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
    Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
    Aug 12 14:02:47 gtcerp1 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@1 (glm0):
    we are geting this errror since from last two week, can anyone suggest us how to remove this error. we have tried by removing scsi card and rebooted, intially the error is removed but now its again come on console.

    Hi.
    Unfortunetly you not write what server you have.
    */pci@8,700000/scsi@1* look like Internal SCSI controller in Sun Fire V880.
    For this server Target 6.0 is CD-ROM (DVD-ROM).
    So it's look like problem with device.
    For check you can use:
    ls -la /dev/rdsk/*s2 | grep "/pci@8,700000/scsi@1"
    iostat -EnCheck internal cable to CD-ROM. Replace or disconnect CDROM.
    Regards.

  • Sun-Java-System-SMTP-Warning

    Customers using our company's products have been finding the following error message when sending messages with image attachments from our devices:
    "Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and truncated"
    RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies http://www.faqs.org/rfcs/rfc2045.html
    states:
    (5)   Encoded lines must not be longer than 76 characters,
              not counting the trailing CRLF. If longer lines are
              found in incoming, encoded data, a robust
              implementation might nevertheless decode the lines, and
              might report the erroneous encoding to the user.Our devices comply with this RFC to the letter.
    Can anyone explain why the Sun Java System SMTP server is rejecting these messages?
    If necessary, I can provide network capture files from the connection between our device and an SMTP server.
    A sample successful SMTP connection with a Postfix SMTP server follows:
    220 doc.doc.pixord.com ESMTP Postfix
    EHLO pixord.com
    250-doc.doc.pixord.com
    250-PIPELINING
    250-SIZE 20480000
    250-VRFY
    250-ETRN
    250 8BITMIME
    MAIL FROM:
    250 Ok
    RCPT TO:
    250 Ok
    DATA
    354 End data with <CR><LF>.<CR><LF>
    from:
    to:
    subject: This is just test.
    date: Thu, 05 May 2005 08:10:09 +0800
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
    .boundary="--=_iMaIl_BoUnDrY_1"
    ----=_iMaIl_BoUnDrY_1
    Content-Type: text/plain;
    This is just a test.
    ----=_iMaIl_BoUnDrY_1
    Content-Type: image/jpeg;
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment;
    .filename="test.jpg"
    /9j/2wCEABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19i
    Z2hnPk1xeXBkeFxlZ2MBERISGBUYLxoaL2NCOEJjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2Nj
    Y2NjY2NjY2NjY2NjY2NjY2NjY2NjY//EAaIAAAEFAQEBAQEBAAAAAAAAAAABAgMEBQYHCAkKCwEA
    ----SNIPPED BY ME----
    Skz7VZIFMKj0oAgJHoaaSPepyi+lNMYoAhOPWm8eoqYximmP3oA//9k=
    ----=_iMaIl_BoUnDrY_1--
    250 Ok: queued as 5AC3815763F
    RSET
    250 Ok
    QUIT
    221 ByeMIME message was snipped by me in order to shorten the message.
    I also removed the E-mail addresses.

    I'm sorry.
    1. The max line length is 998 characters, plus cr/lf
    2. If you're getting the error message, then whatever that message was composed with is broken, and emitting lines longer than that.
    Messaging Server has configurable choices. By default, it simply truncates the lines. You can choose to "wrap" them.
    See channel keyword, "wrapsmtp"

  • [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st ack for

    Hi All,
    I have two Sunfire V880 server with Solaris 5.9 , in solaris cluster 3.1. Oracle 10g Database installed in both srver with RAC. last day i got the following error Swap error from one of the cluster node. In both server 14GB device swap and 14GB file system swap also.. please see the log and give me a solution.. Thanks in advance for all
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21901 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21998 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21391 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21901 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21387 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 5155 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20732 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 5155 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20930 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 19016 (oracle)
    Jul 24 17:04:28 server last message repeated 3 times
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20015 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 22143 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20817 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21884 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 19990 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:30 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20107 (oracle)
    Jul 24 17:04:30 server last message repeated 3 times
    Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10365 (oracle)
    Jul 24 17:48:29 server last message repeated 3 times
    Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10258 (oracle)
    Jul 24 17:48:29 server last message repeated 3 times
    Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 15862 (oracle)
    Jul 24 17:53:32 server last message repeated 3 times
    Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10335 (oracle)
    Jul 24 17:53:32 server last message repeated 3 times
    Jul 24 18:45:13 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 9847 (oracle)
    Jul 24 18:45:13 server last message repeated 3 times
    Jul 24 18:46:57 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10883 (oracle)
    Jul 24 18:46:57 server last message repeated 6 times
    Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
    Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
    Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
    Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
    Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 111=>fp(2)::GPN_ID for D_ID=20600
    failed
    Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 112=>fp(2)::N_x Port with D_ID=206
    00, PWWN=100000e0022201be disappeared from fabric
    Jul 25 00:41:36 server fctl: [ID 517869 kern.warning] WARNING: 126=>fp(2)::N_x Port with D_ID=206
    00, PWWN=100000e0022201be reappeared in fabric
    bash-2.05$

    Note: This thread was originally posted in the [Servers - General Discussion|http://forums.sun.com/forum.jspa?forumID=830] forum, but moved to this forum for closer topic alignment.

  • [ID 107833 kern.warning] ... /scsi_vhci/....

    Hi there,
    Have noticed these errors in dmesg log and seems like during this period of errors we had our systems have a very low transfer rate.
    I have 3 sets of erros to dig into.
    [1] I did some search and found a similar error and had a patch for the specific device ...(reference http://sunsolve.sun.com/search/document.do?assetkey=1-26-101771-1). Errors are attached below
    [2] SAM-FS critical device error. Not sure on if this is critical, and how to go about finding the source of the problem.
    [3] output of iostat -En ....showing 2 hard errors. is this the source of all problems above ???
    Thanks for any help you can provide!!!
    ~a2@sunsolve
    [1] =============================================
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
    Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
    Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
    Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
    Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
    Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    [2] ===================================================
    Nov 23 04:13:10 suseme genu-50[2704]: [ID 559880 local7.crit] crit Device 53: State set to DOWN by SAM-FS. Check device log.
    Nov 23 04:13:10 suseme genu-50[2704]: [ID 694869 local7.alert] Volume (50:8) is in drive 53 that is off or down.
    [3] ==================================================
    iostat -En | more
    c0t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
    Vendor: TOSHIBA Product: DVD-ROM SD-M1712 Revision: 1004 Serial No:
    Size: 0.00GB <0 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 2 Predictive Failure Analysis: 0
    c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
    Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1TJ
    Size: 73.40GB <73400057856 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 0 Predictive Failure Analysis: 0
    c1t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
    Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1T7
    Size: 73.40GB <73400057856 bytes>
    ==============================================

    can you help me how to fix scsi warnning ?
    ov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
    Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
    Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
    Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
    Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
    Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
    Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    [2] ===================================================

  • Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000

    Hi,
    I need help regarding below kernel warning message :
    Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000
    I am new to solaris, and am unable to understand this.I want to know,
    1) What this warning exactly means.
    2) Is this warning important or can be negated.
    3) what causes this warning to generate again and again.
    Please let me know if you want any further information regarding this.
    Thanks & Regards,
    Girish

    That error message is something to do with a storage device. But its cut off, /pci indicates a pci card, and 1e,6000 is a partial address to the card. You need to post the next few lines as well.
    .7/M.

  • HT201303 I tried to change my email address on the apple ID but now when I try to buy an app or film it still comes up with my old email address and won't accept  my password to buy anything. My old email address is no longer in use  and can not be access

    I tried to change my email address ID , but now when I try to buy an app or music it still shows my old email address  and won't accept my password which I did not change. What can I do as I can't download anything ?

    What id shows in Settings > iTunes & App Store ? If it's the old one then tap on it and log out of it and then log in with the updated version

  • I am trying to change the email address associated with my existing account to free up my university email address for use in obtaining Creative Cloud.

    I am trying to change the email address associated with my existing account to free up my university email address for use in obtaining Creative Cloud.  Every time I go to the account settings of my existing account (which currently uses my university email, as I set it up years ago and had no idea it'd eventually cause problems), I enter a different email to use for that account but I continuously receive an error message saying "account changes cannot be saved."  It makes me think that it's because the email isn't verified (funny, it actually is verified since it has been the alternate email on the old account for years), but when I click the "send verification email" nothing happens (that is, no email is sent to that other email address).
    Anyway, my university is now requiring that faculty create new accounts using our university email addresses in order to register/use Creative Cloud.  Am I able to delete my old account, or can anyone help me actually change the email address associated with my old account without getting a "changes can't be saved" error?

    This is an open forum, not Adobe support... you need Adobe support to help
    Adobe contact information - http://helpx.adobe.com/contact.html
    -Select your product and what you need help with
    -Click on the blue box "Still need help? Contact us"
    or
    Make sure that EVERY DETAIL is the same in every place you enter your information
    -right down to how you spell and punctuate the parts of your name and address
    Change/Verify Account https://forums.adobe.com/thread/1465499 may help
    -Credit card https://helpx.adobe.com/utilities/credit-card.html
    -email address https://forums.adobe.com/thread/1446019
    -http://helpx.adobe.com/x-productkb/global/didn-t-receive-expected-email.html

  • When trying to verify the email address, I get the following message. Please help. This email address is already in use or you may already have an Apple ID associated with this email address. Please try again or sign in using your existing Apple ID.

    When trying to verify the email address, I get the following message. Please help. This email address is already in use or you may already have an Apple ID associated with this email address. Please try again or sign in using your existing Apple ID.

    Me too. I try to verify and i get the same message.
    I've created 3 alternate e-mail addresses and tried creating new accounts.
    Same Result!
    This is bullsh!t. How the **** can all 4 of my attempts result in the same freakin error???

  • Hello. I am trying to create an email address for my iPod touch 5G. It will verify for awhile ask me the SSl question, and fails all the verifications please help!

    I am trying to create an Email address on my iPod and always fails. can anyone give me some solutions?

    Bt SSI do you mean your security question answers?
    Forgotten Security Questions/Answers
    You need to contact Apple by:
    1 - Use the Express lane and start here:
    https://expresslane.apple.com
    then click More Products and Services>Apple ID>Other Apple ID Topics>Forgotten Apple ID security questions.
    or
    Apple - Support -form iTunes Store - Contact Us
    2 - Call Apple in your country by getting the number from here:
    http://support.apple.com/kb/HE57
    or           
    Apple ID: Contacting Apple for help with Apple ID account security
    3 - Use your rescue email address if you set one up
    Rescue email address and how to reset Apple ID security questions
    For general  information see:
    Apple ID: All about Apple ID security questions

  • I am trying to change my email address for an Apple ID and it is saying that it is already in use. I then sign in with that Apple ID and it says that the account is not set up yet, I don't want to set up the account, but I do want to use the email address

    I am trying to change my email address for an Apple ID and it is saying that it is already in use. I then sign in with that Apple ID and it says that the account is not set up yet, I don't want to set up the account, but I do want to use the email address in my original Apple ID! HELP!

    Welcome to the Apple community.
    Once you have created a rescue address, you cannot delete it, nor can you change it to the same address as used by your ID. There are numerous providers you can get additional email addresses from, such as Hotmail, Yahoo, Google etc etc.

Maybe you are looking for

  • Display issues on Satellite M70

    I am using Satellite M 70 notebook, purchased about more than one year back and really like it ( Pentium M70, 512MB Ram, 40 GB HD). So far it has been without major issues. The only problem now I face is that some times the screen for a second or a f

  • Availability Check : Confirmed Date in Sales Order.

    Hello Gurus, I have an issue with the availability check. Scenario : Customer has created an order for quantity 800 on 26th of Feb and accordingly when created the order go confirmed for 17th of March. The specific quanity(batch) of 800 was released

  • Moved itunes library to external HD  now major issues

    I moved my itunes library (6080 songs) to a external (mybook 160 gig) hard drive now when I startuo Itunes- it tries to "determine gapless payback" and freezes about 1/2 through and i have to force quit -try 2- when I start up Itunes and stop the "de

  • Solaris 10 64 bit for x86

    When i typed isainfo -kv the output is 64-bit amd64 kernel modules. I think this means its a 32-bit OS anybody help when can i download 64bit?

  • No trusted/login RFC connection for system BCP in TA SMSY

    Hi, i got this error  Early Watch Report  for only production System. No trusted/login RFC connection for system BCP in TA SMSY Amit