Sponsored Content
Special Forums Hardware Sunfire x4600 M2 NIC replacement Post 302908617 by DukeNuke2 on Wednesday 9th of July 2014 06:32:08 AM
Old 07-09-2014
Instance 2 of e1000g is the one that is not working. This is the first network port on the motherboard assembly of your server... So, you need to check the cable and the switch port which is running to the net0 port on the server (not PCI slot), should be the bottom left! If everything is ok and the port is still not working, the port might be dead and you need to replace the servers mainboard.
 

9 More Discussions You Might Find Interesting

1. Solaris

console for x4600

Hi, I ;ve a SUN x4600 running solaris 10. I want to connect to the system remotely form console like we can connect to sparc sc or alom .. (9 Replies)
Discussion started by: fugitive
9 Replies

2. Solaris

x4600 iLOM issue

I need to configure the iLOM for x4600 server. before I can set the IP details and commit, I need to set network state should be enabled. However my firmware is already the latest and I need not upgrade. I am not able to set the /SP/network state to enable. pls assist. i BELIEVE the bug was fixed... (5 Replies)
Discussion started by: incredible
5 Replies

3. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

I couldn't install my nic in solaris 10. I compiled and added the driver but failed to attach the driver and ifconfig output shows only loopback dev. Please see the following output and tell me whether my nic has been detected and why the driver failed to attach? My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies

4. Solaris

Sunfire X4600 Errors on Bootup

Hi Folks, Has anyone seen these errors on bootup. Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 Replies

5. IP Networking

squid proxy: one NIC for inbound & one NIC for outbound?

I am new in squid proxy. My question is how to (and if it's necessary) to set one NIC for inbound traffic (http requests) and one NIC for outbound traffic (http answers)? Thank you in advance! (4 Replies)
Discussion started by: aixlover
4 Replies

6. Red Hat

I want to tune NIC's rps, rfs and xps value. which NIC device should I modify.

Dear All I want tune my NIC's rps, rfs and xps value. In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1). Here is the question? Which device should I modify ? eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0) Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies

7. Solaris

SunFire V240 CPU Heat Sink Replacement

I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies

8. Hardware

Sun X4600 M2 enable Hyperthreading

Booting and checking BIOS there is no option to enable-disable hyperthreading. I have 8 Dual-Core AMD Opteron(tm) Processor 8220 and I see 16 cores. Enable hyperthreading I should have 32 cores. I have red hat 5.4 installed. Anyone know how can enable hypethreading ? I have last BIOS/Firmware... (2 Replies)
Discussion started by: laxtnog
2 Replies

9. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

Hello Admins, My ask is how can I add two different subnet IPs to same box with two different gateways? The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware. How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
AUSCOPE(1)						      General Commands Manual							AUSCOPE(1)

NAME
auscope - Network Audio System Protocol Filter SYNOPSIS
auscope [ option ] ... DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio server. auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or, you can invoke auscope as perl auscope [ option ] ... assuming the Perl executable is in your path. To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati- cally biased by 8000. The output port defaults to 0 and the input port defaults to 1. ARGUMENTS
-i<input-port> Specify the port that auscope will use to take requests from clients. -o<output-port> Determines the port that auscope will use to connect to the audio server. -h<audio server name> Determines the desktop machine name that auscope will use to find the audio server. -v<print-level> Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater output detail. EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect to the audio server on port 8000. Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the audio server via the TCP/IP network host tcphost and port 8001: auscope -i1 -o0 -hmcxterm auplay -audio tcp/tcphost:8001 dial.snd In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the network host tcphost, while displaying its graphical interface on another server labmcx: auscope -i1 -o0 -hmcxterm -v1 autool -audio tcp/tcphost:8001 -display labmcx:0.0 SEE ALSO
nas(1), perl(1) COPYRIGHT
Copyright 1994 Network Computing Devices, Inc. AUTHOR
Greg Renda, Network Computing Devices, Inc. 1.9.3 AUSCOPE(1)
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy