V210 BGE0@1000FDX (Adam Tomkinson)

From: Bongumusa Mnguni [ MTN - Innovation Centre ] (Mnguni_Bo_at_mtn.co.za)
Date: 10/26/05

  • Next message: daryl.mitchell_at_us.o-i.com: "local root mail getting relayed externally"
    Date: Wed, 26 Oct 2005 19:26:09 +0200
    To: <adam.tomkinson@rtel.com>
    
    

    -----Original Message-----
    From: Bongumusa Mnguni [ MTN - Innovation Centre ]
    Sent: Wednesday, 26 October 2005 07:22 PM
    To: 'adam.tomkinson@rtel.com'
    Cc: 'sunmanagers@sunmanagers.org'
    Subject: RE: sunmanagers Digest, Vol 31, Issue 28

    Hi,

    When connecting a server to a Gig interface you need to enable autoneg
    on the server. It will pick up the correct speed automatically. It
    becomes a problem when trying to force it especially if using Cisco
    switches.

    Normally I run the following script commands

    ndd -set /dev/bge0 adv_autoneg_cap 1
    ndd -set /dev/bge0 adv_1000fdx_cap 1
    ndd -set /dev/bge0 adv_1000hdx_cap 0
    ndd -set /dev/bge0 adv_100fdx_cap 0
    ndd -set /dev/bge0 adv_100hdx_cap 0
    ndd -set /dev/bge0 adv_10fdx_cap 0
    ndd -set /dev/bge0 adv_10hdx_cap 0

    Hope that it resolves your problem.

    Regards
    Musa

    -----Original Message-----
    From: sunmanagers-bounces@sunmanagers.org
    [mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of
    sunmanagers-request@sunmanagers.org
    Sent: Wednesday, 26 October 2005 05:31 PM
    To: sunmanagers@sunmanagers.org
    Subject: sunmanagers Digest, Vol 31, Issue 28

    Send sunmanagers mailing list submissions to
            sunmanagers@sunmanagers.org

    To subscribe or unsubscribe via the World Wide Web, visit
            http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    or, via email, send a message with subject or body 'help' to
            sunmanagers-request@sunmanagers.org

    You can reach the person managing the list at
            sunmanagers-owner@sunmanagers.org

    When replying, please edit your Subject line so it is more specific
    than "Re: Contents of sunmanagers digest..."

    Today's Topics:

       1. V210 BGE0@1000FDX (Adam Tomkinson)
       2. System Crash... (giridhar.reddyk@wipro.com)
       3. System Crash... (giridhar.reddyk@wipro.com)
       4. NFS oddity (for me at least) (Paveza, Gary)
       5. Blocked port after process kill (Andreas H?schler)
       6. Solaris 9 vs Solaris 10 comparisons (Hirchert, Dale L)
       7. SUMMARY: NFS oddity (for me at least) (Paveza, Gary)
       8. question about ufsrestore inode number (sara sodagar)
       9. how to reset SunSAI/P port (B Bong)

    ----------------------------------------------------------------------

    Message: 1
    Date: Wed, 26 Oct 2005 12:12:24 +0100
    From: "Adam Tomkinson" <adam.tomkinson@rtel.com>
    Subject: V210 BGE0@1000FDX
    To: <sunmanagers@sunmanagers.org>
    Message-ID: <6E021612E9D8E64CAEA7FBB4DDD614BD4AC78C@rtmail.rtel.com>
    Content-Type: text/plain; charset="us-ascii"

    Hi Folks,

    I've had no problem getting the interface up at 100FDX but when I try to
    shift
    to 1000FDX the interface goes down. It makes no difference if I modify
    /platform/sun4u/kernel/drv/bge.conf and reboot, also:

    ndd -set /dev/bge0 adv_autoneg_cap 0
    ndd -set /dev/bge0 adv_1000fdx_cap 1
    ndd -set /dev/bge0 adv_100fdx_cap 0

    The nic is plugged directly into the 1Gbit switch and have also tried it
    in
    the hub but to no avail. Running at 100FDX I'm only getting approx 30k/s
    via
    ftp.

    Any ideas?

    Adam Tomkinson
    Unix (Solaris) Engineer/Consultant
    Realtime Engineering Ltd
    Academy House
    Academy Pk
    Gower Street
    Glasgow
    G51 1PR
    Tel. +44 141 427 4246

    ------------------------------

    Message: 2
    Date: Wed, 26 Oct 2005 17:13:17 +0530
    From: <giridhar.reddyk@wipro.com>
    Subject: System Crash...
    To: <sunmanagers@sunmanagers.org>
    Message-ID:
            <E58D594F8055B34E99C45D14DC0884C01CBEB5@HYD-MKD-MBX01.wipro.com>
    Content-Type: text/plain; charset="us-ascii"

    Hi Experts,

    I have a E 250 machine which has crashed. The error message is as
    follows from /var/adm/messages.

    Oct 26 08:40:52 wecdserver ^Mpanic[cpu0]/thread=3000d1e9d00:
    Oct 26 08:40:52 wecdserver unix: [ID 816072 kern.notice]
    vmem_xalloc(30000012ec8, 16785408, 8192, 0, 16777216, c0000000, 1000
    00000, 1): overconstrained allocation
    Oct 26 08:40:52 wecdserver unix: [ID 100000 kern.notice]
    Oct 26 08:40:52 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1ce80 genunix:vmem_xalloc+fc (30000012ec8, 1002000, 20
    00, 0, 1000000, c0000000)
    Oct 26 08:40:52 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000003000d8d0b38 0000000000000000 0000030000012ec8 00000
    00001002000
    Oct 26 08:40:52 wecdserver %l4-7: 0000000000000000 0000000000000000
    ffffffffffffffff 00000000fedba004
    Oct 26 08:40:52 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1cfb0 pcipsy:pci_dma_map_impl+8e4 (801, 1, 1, 550, 300
    0d8d0a48, 30000163dd8)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000002a101c1d250 0000000000000801 0000030000a49e08 00000
    00000000801
    Oct 26 08:40:53 wecdserver %l4-7: 0000000000000000 000003000d8d0b38
    000000000000000f 0000000000000000
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d0e0 pcipsy:pci_dma_bindhdl+38 (30000165dd0, 30000163
    dd8, 3000d8d0a48, 2a101c1d250, 3000d8316a8, 3000d8316c0)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    0000030000165dd0 000000000000007e 0000030013fe1430 00000
    3000b2e1ba0
    Oct 26 08:40:53 wecdserver %l4-7: 000002a100f8b4d8 0000000000000000
    000003000e2daf88 000002a100f8bba0
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d1a0 genunix:ddi_dma_buf_bind_handle+e8 (3000d8d0a48,
     3000247fce8, 12, 0, 0, 3000d8316a8)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000300002c4380 000003000ec2c780 0000000078106b58 00000
    3000b5c8c70
    Oct 26 08:40:53 wecdserver %l4-7: 0000002100000089 000000007810665c
    0000000000000000 000003000df12a00
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d290 glm:glm_scsi_init_pkt+1ec (3000d831698, 3000d831
    6a8, 0, 0, 0, 0)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000003000247fce8 000003000ceb0dc8 000003000d8317c8 00000
    30000a3c000
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000000101234c8 0000000000002000 000003000d41b378 00000
    3000e7fc778
    Oct 26 08:40:54 wecdserver %l4-7: 000002a101c1d7a8 0000000000000000
    000003000d42ad20 0000000000000000
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d810 st:st_rw+13c (3000ab9f690, 2a101c1d978, 40, 2100
    000089, 40, 8000000)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000000100c244c 0000000000000000 0000000000000040 00000
    00000000000
    Oct 26 08:40:54 wecdserver %l4-7: 000000000810a000 000002a101c1d978
    000003000d41b378 000002a101c1daf0
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d8c0 genunix:read+25c (0, 0, 2001, 3000d51c2d8, 3, 80
    00000)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000000001014be44 0000000008000000 000003000d927838 00000
    30002361ea0
    Oct 26 08:40:54 wecdserver %l4-7: 0000000000000001 00000300023ca000
    0000000000000000 000002a101c1d910
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1da40 genunix:read32+30 (3, 10c550, 8000000, 0, 0, 0)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000000000001a33c 0000000000000000 000003000e5c6a90 00000
    00000000000
    Oct 26 08:40:54 wecdserver %l4-7: 0000000000010031 000003000ec2c780
    0000000000000000 0000000000000002
    Oct 26 08:40:54 wecdserver unix: [ID 100000 kern.notice]
    Oct 26 08:40:54 wecdserver genunix: [ID 672855 kern.notice] syncing file
    systems...
    Oct 26 08:40:55 wecdserver genunix: [ID 733762 kern.notice] 258
    Oct 26 08:40:57 wecdserver genunix: [ID 733762 kern.notice] 204
    Oct 26 08:40:58 wecdserver genunix: [ID 904073 kern.notice] done
    Oct 26 08:40:59 wecdserver genunix: [ID 353387 kern.notice] dumping to
    /dev/dsk/c0t0d0s1, offset 419495936
    Oct 26 08:41:34 wecdserver genunix: [ID 409368 kern.notice] ^M100% done:
    53360 pages dumped, compression ratio 2.85,
    Oct 26 08:41:34 wecdserver genunix: [ID 851671 kern.notice] dump
    succeeded
    Oct 26 08:43:14 wecdserver genunix: [ID 540533 kern.notice] ^MSunOS
    Release 5.8 Version Generic_108528-13 64-bit

    Has anybody gone through this problem? If so suggest me.
    Can you give me the reason why it got crashed? Is the problem with RAM?

    Thanks and Regards,
    Giridhar.

    Confidentiality Notice

    The information contained in this electronic message and any attachments
    to
    this message are intended
    for the exclusive use of the addressee(s) and may contain confidential
    or
    privileged information. If
    you are not the intended recipient, please notify the sender at Wipro or
    Mailadmin@wipro.com immediately
    and destroy all copies of this message and any attachments.

    ------------------------------

    Message: 3
    Date: Wed, 26 Oct 2005 17:33:54 +0530
    From: <giridhar.reddyk@wipro.com>
    Subject: System Crash...
    To: <sunmanagers@sunmanagers.org>
    Message-ID:
            <E58D594F8055B34E99C45D14DC0884C01CBEB6@HYD-MKD-MBX01.wipro.com>
    Content-Type: text/plain; charset="us-ascii"

    Hi Experts,

    I have a E 250 machine which has crashed. The error message is as
    follows from /var/adm/messages.

    Oct 26 08:40:52 wecdserver ^Mpanic[cpu0]/thread=3000d1e9d00:
    Oct 26 08:40:52 wecdserver unix: [ID 816072 kern.notice]
    vmem_xalloc(30000012ec8, 16785408, 8192, 0, 16777216, c0000000, 1000
    00000, 1): overconstrained allocation
    Oct 26 08:40:52 wecdserver unix: [ID 100000 kern.notice]
    Oct 26 08:40:52 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1ce80 genunix:vmem_xalloc+fc (30000012ec8, 1002000, 20
    00, 0, 1000000, c0000000)
    Oct 26 08:40:52 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000003000d8d0b38 0000000000000000 0000030000012ec8 00000
    00001002000
    Oct 26 08:40:52 wecdserver %l4-7: 0000000000000000 0000000000000000
    ffffffffffffffff 00000000fedba004
    Oct 26 08:40:52 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1cfb0 pcipsy:pci_dma_map_impl+8e4 (801, 1, 1, 550, 300
    0d8d0a48, 30000163dd8)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000002a101c1d250 0000000000000801 0000030000a49e08 00000
    00000000801
    Oct 26 08:40:53 wecdserver %l4-7: 0000000000000000 000003000d8d0b38
    000000000000000f 0000000000000000
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d0e0 pcipsy:pci_dma_bindhdl+38 (30000165dd0, 30000163
    dd8, 3000d8d0a48, 2a101c1d250, 3000d8316a8, 3000d8316c0)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    0000030000165dd0 000000000000007e 0000030013fe1430 00000
    3000b2e1ba0
    Oct 26 08:40:53 wecdserver %l4-7: 000002a100f8b4d8 0000000000000000
    000003000e2daf88 000002a100f8bba0
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d1a0 genunix:ddi_dma_buf_bind_handle+e8 (3000d8d0a48,
     3000247fce8, 12, 0, 0, 3000d8316a8)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000300002c4380 000003000ec2c780 0000000078106b58 00000
    3000b5c8c70
    Oct 26 08:40:53 wecdserver %l4-7: 0000002100000089 000000007810665c
    0000000000000000 000003000df12a00
    Oct 26 08:40:53 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d290 glm:glm_scsi_init_pkt+1ec (3000d831698, 3000d831
    6a8, 0, 0, 0, 0)
    Oct 26 08:40:53 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000003000247fce8 000003000ceb0dc8 000003000d8317c8 00000
    30000a3c000
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000000101234c8 0000000000002000 000003000d41b378 00000
    3000e7fc778
    Oct 26 08:40:54 wecdserver %l4-7: 000002a101c1d7a8 0000000000000000
    000003000d42ad20 0000000000000000
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d810 st:st_rw+13c (3000ab9f690, 2a101c1d978, 40, 2100
    000089, 40, 8000000)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    00000000100c244c 0000000000000000 0000000000000040 00000
    00000000000
    Oct 26 08:40:54 wecdserver %l4-7: 000000000810a000 000002a101c1d978
    000003000d41b378 000002a101c1daf0
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1d8c0 genunix:read+25c (0, 0, 2001, 3000d51c2d8, 3, 80
    00000)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000000001014be44 0000000008000000 000003000d927838 00000
    30002361ea0
    Oct 26 08:40:54 wecdserver %l4-7: 0000000000000001 00000300023ca000
    0000000000000000 000002a101c1d910
    Oct 26 08:40:54 wecdserver genunix: [ID 723222 kern.notice]
    000002a101c1da40 genunix:read32+30 (3, 10c550, 8000000, 0, 0, 0)
    Oct 26 08:40:54 wecdserver genunix: [ID 179002 kern.notice] %l0-3:
    000000000001a33c 0000000000000000 000003000e5c6a90 00000
    00000000000
    Oct 26 08:40:54 wecdserver %l4-7: 0000000000010031 000003000ec2c780
    0000000000000000 0000000000000002
    Oct 26 08:40:54 wecdserver unix: [ID 100000 kern.notice]
    Oct 26 08:40:54 wecdserver genunix: [ID 672855 kern.notice] syncing file
    systems...
    Oct 26 08:40:55 wecdserver genunix: [ID 733762 kern.notice] 258
    Oct 26 08:40:57 wecdserver genunix: [ID 733762 kern.notice] 204
    Oct 26 08:40:58 wecdserver genunix: [ID 904073 kern.notice] done
    Oct 26 08:40:59 wecdserver genunix: [ID 353387 kern.notice] dumping to
    /dev/dsk/c0t0d0s1, offset 419495936
    Oct 26 08:41:34 wecdserver genunix: [ID 409368 kern.notice] ^M100% done:
    53360 pages dumped, compression ratio 2.85,
    Oct 26 08:41:34 wecdserver genunix: [ID 851671 kern.notice] dump
    succeeded
    Oct 26 08:43:14 wecdserver genunix: [ID 540533 kern.notice] ^MSunOS
    Release 5.8 Version Generic_108528-13 64-bit

    Has anybody gone through this problem? If so suggest me.
    Can you give me the reason why it got crashed? Is the problem with RAM?

    Thanks and Regards,
    Giridhar.

    Confidentiality Notice

    The information contained in this electronic message and any attachments
    to
    this message are intended
    for the exclusive use of the addressee(s) and may contain confidential
    or
    privileged information. If
    you are not the intended recipient, please notify the sender at Wipro or
    Mailadmin@wipro.com immediately
    and destroy all copies of this message and any attachments.

    ------------------------------

    Message: 4
    Date: Wed, 26 Oct 2005 09:11:28 -0500
    From: "Paveza, Gary" <gary.paveza@AIG.COM>
    Subject: NFS oddity (for me at least)
    To: "'sunmanagers@sunmanagers.org'" <sunmanagers@sunmanagers.org>
    Message-ID:
            <011075EF5ED23844A1CAA16F7DE7F7D702E4785D@xwilmbx10.aigm.com>
    Content-Type: text/plain

    I'm trying to export an NFS share with read/write permissions to just
    one
    host.

    On the NFS server, if I use the line:

    share -F nfs -o rw=<hostname> <share>

    where hostname is the name of the NFS client which will automount the
    filesystem (using the automountd daemon) and <share> is the directory to
    be
    shared.

    This results in a access denied when I try to access this directory on
    the
    client

    If I change the NFS server entry to :

    share -F nfs -o rw <share>

    It works just fine (of course, everyone can mount it then)

    Using Solaris 9 for both server and client. Any ideas?

    ---------------------------------------------------------
    Gary Paveza, Jr.
    Senior Systems Administrator - HP-UX CSE
    (302) 252-4831 - phone

    ------------------------------

    Message: 5
    Date: Wed, 26 Oct 2005 16:40:44 +0200
    From: Andreas H?schler <ahoesch@smartsoft.de>
    Subject: Blocked port after process kill
    To: sunmanagers@sunmanagers.org
    Message-ID: <7D743BD4-462E-11DA-88A0-003065CCA582@smartsoft.de>
    Content-Type: text/plain; charset=US-ASCII; format=flowed

    Dear managers,

    I have a process that opens a socket (port 61000). Sometimes this
    process stops working (we already have a clue why, still
    investigating...). If we kill the process and try to restart it we get
    an error message telling us that socket 61000 could not be bound. After
    waiting 4-6 minutes it works again. Is this normal? It seems that the
    port is freed by the OS after some timeout, but not immediately as a
    result of the process kill. Question: Can we force the OS to free the
    port explicitly or how can we make sure that the OS frees it
    immediately when the corresponding process is killed?

    Thanks a lot!

    Regards,

       Andreas

    ------------------------------

    Message: 6
    Date: Wed, 26 Oct 2005 10:39:09 -0400
    From: "Hirchert, Dale L" <Dale.Hirchert-1@ksc.nasa.gov>
    Subject: Solaris 9 vs Solaris 10 comparisons
    To: <sunmanagers@sunmanagers.org>
    Message-ID:

    <1FFCF939CEB47140898A1076C54AF2B10880581A@kscems004.ksc.nasa.gov>
    Content-Type: text/plain; charset="iso-8859-1"

    Hi folks:

    I'm looking for a document or link that shows a comparison of Sol. 9 RC
    scripts to Sol. 10 services. Does any know if such information exists?

    Thanks!

    Dale

    ------------------------------

    Message: 7
    Date: Wed, 26 Oct 2005 10:47:55 -0400
    From: "Paveza, Gary" <gary.paveza@AIG.COM>
    Subject: SUMMARY: NFS oddity (for me at least)
    To: "'sunmanagers@sunmanagers.org'" <sunmanagers@sunmanagers.org>
    Message-ID:
            <011075EF5ED23844A1CAA16F7DE7F7D702E47889@xwilmbx10.aigm.com>
    Content-Type: text/plain

    The problem was with the hostname. For some reason, it wanted the FQDN
    instead of the short name. Once I put that in, it worked like a charm.

    Thanks to everyone that helped (and those nice enough to tell me they
    were
    out of the office having a good time).

    Mike Newton [jmnewton@duke.edu]
    John Birtley [john@nemean.com]
    Stan.Pietkiewicz@statcan.ca
    Chris Ruhnke [ruhnke@us.ibm.com]
    Horton, William M \(I75\) [I75@bechteljacobs.org]
    Andrew Williams [snowman@ican.net]

    ---------------------------------------------------------
    Gary Paveza, Jr.
    Senior Systems Administrator - HP-UX CSE
    (302) 252-4831 - phone

    -----Original Message-----
    From: sunmanagers-bounces@sunmanagers.org
    [mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of Paveza, Gary
    Sent: Wednesday, October 26, 2005 10:11 AM
    To: 'sunmanagers@sunmanagers.org'
    Subject: NFS oddity (for me at least)

    I'm trying to export an NFS share with read/write permissions to just
    one
    host.

    On the NFS server, if I use the line:

    share -F nfs -o rw=<hostname> <share>

    where hostname is the name of the NFS client which will automount the
    filesystem (using the automountd daemon) and <share> is the directory to
    be
    shared.

    This results in a access denied when I try to access this directory on
    the
    client

    If I change the NFS server entry to :

    share -F nfs -o rw <share>

    It works just fine (of course, everyone can mount it then)

    Using Solaris 9 for both server and client. Any ideas?

    ---------------------------------------------------------
    Gary Paveza, Jr.
    Senior Systems Administrator - HP-UX CSE
    (302) 252-4831 - phone
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

    ------------------------------

    Message: 8
    Date: Wed, 26 Oct 2005 07:52:38 -0700 (PDT)
    From: sara sodagar <sara_sodagar@yahoo.com>
    Subject: question about ufsrestore inode number
    To: sunmanagers@sunmanagers.org
    Message-ID: <20051026145239.17350.qmail@web31804.mail.mud.yahoo.com>
    Content-Type: text/plain; charset=iso-8859-1

    Hi
    I would like to know after performing ufsrestore
    inodes are allocated such that the inode numbers after
    the restore are identical to the inode numbers
    recorded on tape,or are they independent of the inode
    numbers recorded to tape?

    Thanks in advance
    Sara

    __________________________________
    Yahoo! FareChase: Search multiple travel sites in one click.
    http://farechase.yahoo.com

    ------------------------------

    Message: 9
    Date: Wed, 26 Oct 2005 08:27:53 -0700 (PDT)
    From: B Bong <sunmoon208@yahoo.com>
    Subject: how to reset SunSAI/P port
    To: sunmanagers@sunmanagers.org
    Message-ID: <20051026152754.82806.qmail@web32010.mail.mud.yahoo.com>
    Content-Type: text/plain; charset=iso-8859-1

    Dear Sun Managers,

    I've a V210 with Solaris 8 having a Multi Port Serial
    Cards SunSAI/P, one of the port is hung and how can I
    reset that particular serial port of Multi Port Serial
    Cards. Anyone knows of what command to reset that port
    as rebooting the server could be not possible as other
    port is still working fine.

    Thanks in advance for your help.

    Regards,
    Nick

    __________________________________
    Yahoo! Mail - PC Magazine Editors' Choice 2005
    http://mail.yahoo.com

    ------------------------------

    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

    End of sunmanagers Digest, Vol 31, Issue 28
    *******************************************

    NOTE: This e-mail message is subject to the MTN Group disclaimer see
    http://www.mtn.co.za/disclaimer
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: daryl.mitchell_at_us.o-i.com: "local root mail getting relayed externally"

    Relevant Pages

    • V210 BGE0@1000FDX
      ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ... where hostname is the name of the NFS client which will automount the ...
      (SunManagers)
    • Re: FC8 and NFS service
      ... The NFS server is doing some kind of evil security check which was ... Since the port works against the FC1 server, ... Changing clients isn't going to happen, ...
      (Fedora)
    • 7.0 RC1 dump hangs - sometimes
      ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
      (freebsd-current)
    • RC1 dump hangs - sometimes
      ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
      (freebsd-current)
    • Re: Gianfar driver failing on MPC8641D based board
      ... The boot process grinds to a halt not long after the first access of the ... NFS root and I receive multiple "nfs: server 192.168.0.1 not responding, ... at which point the gianfar network driver fails to compile (I have tried ...
      (Linux-Kernel)