|
|||||||
| Forums | Search Forums | Register | Forum Rules | Man Pages | Albums | FAQ | Members | Calendar | Search | Today's Posts | Mark Forums Read |
| Solaris The Solaris Operating System, usually known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle. |
|
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
NIC - how to check card type and available speed
I have a few servers - some running solaris 9 and others solaris 10.
The nic cards installed are all running 100 Full Mb on the interfaces currently. I would assume that all the cards are capable of running Gigabit as the are relatively new servers (under 18 months) - sun fire v490s or v440s but how can I check what NIC cards they are and what they are capable of ? |
| Sponsored Links | ||
|
|
#2
|
||||
|
||||
|
on solaris 10 you can use: Code:
dladm show-dev dladm show-link also have a look at the server documentation. you can find it at: http://docs.sun.com |
| Sponsored Links | ||
|
|
#3
|
|||
|
|||
|
Do you get what you need out of prtconf -D ??
|
|
#4
|
|||
|
|||
|
Doesnt dladm just show me what current settings are?
I need to check to see what NIC is actually capable of... here is the output of the dladm command on my solaris 10 box... can I do same on solaris 9? Is it possible that even though its set at 1000mb - that the NIC is not capable of this speed? (I am particularly interested in ce4) # dladm show-dev ce0 link: unknown speed: 1000 Mbps duplex: full ce1 link: unknown speed: 1000 Mbps duplex: full ce2 link: unknown speed: 0 Mbps duplex: unknown ce3 link: unknown speed: 0 Mbps duplex: unknown ce4 link: unknown speed: 100 Mbps duplex: full ce5 link: unknown speed: 0 Mbps duplex: unknown # dladm show-link ce0 type: legacy mtu: 1500 device: ce0 ce1 type: legacy mtu: 1500 device: ce1 ce2 type: legacy mtu: 1500 device: ce2 ce3 type: legacy mtu: 1500 device: ce3 ce4 type: legacy mtu: 1500 device: ce4 ce5 type: legacy mtu: 1500 device: ce5 Also - output of prtconf -D below SUNW,Sun-Fire-V490 (driver name: rootnex) scsi_vhci, instance #0 (driver name: scsi_vhci) packages SUNW,builtin-drivers deblocker disk-label terminal-emulator SUNW,debug dropins obp-tftp kbd-translator SUNW,i2c-ram-device SUNW,fru-device ufs-file-system chosen openprom client-services options, instance #0 (driver name: options) aliases memory virtual-memory cmp cpu cpu memory-controller, instance #0 (driver name: mc-us3) cmp cpu cpu memory-controller, instance #1 (driver name: mc-us3) pci, instance #0 (driver name: pcisch) pci, instance #0 (driver name: pci_pci) network, instance #0 (driver name: ce) network, instance #1 (driver name: ce) network, instance #2 (driver name: ce) network, instance #3 (driver name: ce) scsi, instance #0 (driver name: mpt) disk (driver name: sd) tape (driver name: st) st, instance #2 (driver name: st) scsi, instance #1 (driver name: mpt) disk (driver name: sd) tape (driver name: st) sd, instance #13 (driver name: sd) sd, instance #15 (driver name: sd) ses, instance #11 (driver name: ses) ide, instance #0 (driver name: uata) disk (driver name: dad) cdrom (driver name: sd) sd, instance #3 (driver name: sd) pci, instance #1 (driver name: pcisch) pci, instance #2 (driver name: pcisch) ebus, instance #0 (driver name: ebus) flashprom bbc power (driver name: power) i2c, instance #0 (driver name: pcf8584) fru, instance #0 (driver name: seeprom) fru, instance #1 (driver name: seeprom) fru, instance #2 (driver name: seeprom) fru, instance #3 (driver name: seeprom) fru, instance #4 (driver name: seeprom) fru, instance #5 (driver name: seeprom) fru, instance #6 (driver name: seeprom) fru, instance #7 (driver name: seeprom) fru, instance #8 (driver name: seeprom) fru, instance #9 (driver name: seeprom) fru, instance #10 (driver name: seeprom) fru, instance #11 (driver name: seeprom) fru, instance #12 (driver name: seeprom) fru, instance #13 (driver name: seeprom) fru, instance #14 (driver name: seeprom) fru, instance #15 (driver name: seeprom) fru, instance #16 (driver name: seeprom) nvram, instance #17 (driver name: seeprom) idprom fru, instance #18 (driver name: seeprom) fru, instance #19 (driver name: seeprom) i2c, instance #1 (driver name: pcf8584) temperature, instance #0 (driver name: max1617) ioexp, instance #0 (driver name: pcf8574) ioexp, instance #1 (driver name: pcf8574) ioexp, instance #2 (driver name: pcf8574) temperature, instance #1 (driver name: max1617) ioexp, instance #3 (driver name: pcf8574) ioexp, instance #4 (driver name: pcf8574) ioexp, instance #0 (driver name: ssc050) ioexp, instance #1 (driver name: ssc050) temperature-sensor, instance #0 (driver name: lm75) fru, instance #20 (driver name: seeprom) fru, instance #21 (driver name: seeprom) fru, instance #22 (driver name: seeprom) fru, instance #23 (driver name: seeprom) fru, instance #24 (driver name: seeprom) rscrtc rtc, instance #0 (driver name: todds1287) gpio, instance #0 (driver name: gpio_87317) pmc, instance #0 (driver name: pmc) rsc-control, instance #0 (driver name: su) rsc-console, instance #1 (driver name: su) serial, instance #0 (driver name: se) usb, instance #0 (driver name: ohci) network, instance #4 (driver name: ce) pci, instance #3 (driver name: pcisch) network, instance #5 (driver name: ce) SUNW,qlc, instance #0 (driver name: qlc) fp (driver name: fp) disk (driver name: ssd) fp, instance #1 (driver name: fp) ssd, instance #1 (driver name: ssd) ssd, instance #0 (driver name: ssd) iscsi, instance #0 (driver name: iscsi) pseudo, instance #0 (driver name: pseudo) |
| Sponsored Links | |
|
|
#5
|
||||
|
||||
|
you can try the following Code:
# kstat ce0 --- lots of output here --- and get a list of attributes about the interface. # kstat -p bge:0::link* bge:0:mii:link_asmpause 0 bge:0:mii:link_duplex 2 bge:0:mii:link_pause 0 bge:0:mii:link_up 1 bge:0:parameters:link_autoneg 1 bge:0:parameters:link_duplex 2 bge:0:parameters:link_rx_pause 0 bge:0:parameters:link_speed 1000 bge:0:parameters:link_status 1 bge:0:parameters:link_tx_pause 0 # ndd -get /dev/bge0 link_speed 1000 if you are trying to auto-neg, sometimes solaris is a pain with that. you may have to just hard set it to what you want. so force it to 1000fdx or whatever you want. example: Code:
ndd -set /dev/ce instance 0 ndd -set /dev/ce adv_1000fdx_cap 0 ndd -set /dev/ce adv_1000hdx_cap 0 ndd -set /dev/ce adv_100fdx_cap 1 ndd -set /dev/ce adv_100hdx_cap 0 ndd -set /dev/ce adv_10fdx_cap 0 ndd -set /dev/ce adv_10hdx_cap 0 ndd -set /dev/ce adv_autoneg_cap 0 this should force 100fdx for ce0 or you can always do the equiv in /etc/system with sets. just change according to what you want. |
| Sponsored Links | |
|
|
#6
|
||||
|
||||
|
Sun provides a nice script to do network tunig... just follow the instructions in the file header! Code:
#!/sbin/sh
# /etc/rc2.d/S68net-tune /etc/init.d/net-tune
# Copyright (c) 2000 by Sun Microsystems, Inc.
# All rights reserved.
#
#ident "@(#)net-tune 1.6.4 030416 SMI ES-PTS-NET/Lor"
#
# Edit the following example code to suit your needs.
# Depending on your changes, this script overwrites the Sun recommended default
# values (To use the default values, you do not need this script). See Product
# Documentation and SunSolve Infodocs for proper use first (e.g. Infodocs 17416,
# 23041, 41665). Most parameters must be set on both sides to have effect
# (e.g. check switch and IP partner settings).
# To install:
# 1) cp S68net-tune to /etc/rc2.d
# 2) perform edits on the sript as required
# 3) chmod 744 /etc/rc2.d/S68net-tune
# 4) chown root:sys /etc/rc2.d/S68net-tune
# 5) ln /etc/rc2.d/S68net-tune /etc/init.d/net-tune
PATH=/usr/bin:/usr/sbin
case "$1" in
'start')
echo "Implementing Solaris Network Tuning."
# hme-Interfaces
# hme0
#ndd -set /dev/hme instance 0
#ndd -set /dev/hme adv_100T4_cap 0
#ndd -set /dev/hme adv_100fdx_cap 1
#ndd -set /dev/hme adv_100hdx_cap 0
#ndd -set /dev/hme adv_10fdx_cap 0
#ndd -set /dev/hme adv_10hdx_cap 0
#ndd -set /dev/hme adv_autoneg_cap 0
# hme1
#ndd -set /dev/hme instance 1
#ndd -set /dev/hme adv_100T4_cap 0
#ndd -set /dev/hme adv_100fdx_cap 1
#ndd -set /dev/hme adv_100hdx_cap 0
#ndd -set /dev/hme adv_10fdx_cap 0
#ndd -set /dev/hme adv_10hdx_cap 0
#ndd -set /dev/hme adv_autoneg_cap 0
# eri-Interfaces
# eri0
#ndd -set /dev/eri instance 0
#ndd -set /dev/eri adv_100T4_cap 0
#ndd -set /dev/eri adv_100fdx_cap 1
#ndd -set /dev/eri adv_100hdx_cap 0
#ndd -set /dev/eri adv_10fdx_cap 0
#ndd -set /dev/eri adv_10hdx_cap 0
#ndd -set /dev/eri adv_autoneg_cap 0
# qfe-Interfaces
# qfe0
#ndd -set /dev/qfe instance 0
#ndd -set /dev/qfe adv_100T4_cap 0
#ndd -set /dev/qfe adv_100fdx_cap 1
#ndd -set /dev/qfe adv_100hdx_cap 0
#ndd -set /dev/qfe adv_10fdx_cap 0
#ndd -set /dev/qfe adv_10hdx_cap 0
#ndd -set /dev/qfe adv_autoneg_cap 0
# qfe1
#ndd -set /dev/qfe instance 1
#ndd -set /dev/qfe adv_100T4_cap 0
#ndd -set /dev/qfe adv_100fdx_cap 1
#ndd -set /dev/qfe adv_100hdx_cap 0
#ndd -set /dev/qfe adv_10fdx_cap 0
#ndd -set /dev/qfe adv_10hdx_cap 0
#ndd -set /dev/qfe adv_autoneg_cap 0
# dmfe-Interfaces (Netra X1)
# dmfe0
#ndd -set /dev/dmfe0 adv_100fdx_cap 1
#ndd -set /dev/dmfe0 adv_100hdx_cap 0
#ndd -set /dev/dmfe0 adv_10fdx_cap 0
#ndd -set /dev/dmfe0 adv_10hdx_cap 0
#ndd -set /dev/dmfe0 adv_autoneg_cap 0
# dmfe1
#ndd -set /dev/dmfe1 adv_100fdx_cap 1
#ndd -set /dev/dmfe1 adv_100hdx_cap 0
#ndd -set /dev/dmfe1 adv_10fdx_cap 0
#ndd -set /dev/dmfe1 adv_10hdx_cap 0
#ndd -set /dev/dmfe1 adv_autoneg_cap 0
# vge-Interfaces (Gigabit 1.x)
# vge0
#ndd -set /dev/vge instance 0
#ndd -set /dev/vge fdr_filter 1
#ndd -set /dev/vge link_negotiation 0
# vge1
#ndd -set /dev/vge instance 1
#ndd -set /dev/vge fdr_filter 1
#ndd -set /dev/vge link_negotiation 0
# ge-Interfaces (Gigabit 2.x and 3.x)
# example: forced 1000 Mbit/s, 802.3x Flow Control send and receive
# check if your NIC is 802.3x capable (ndd parameter pause_cap, asm_dir_cap)
# ge0
#ndd -set /dev/ge instance 0
#ndd -set /dev/ge adv_1000fdx_cap 1
#ndd -set /dev/ge adv_1000hdx_cap 0
#ndd -set /dev/ge adv_pauseTX 1
#ndd -set /dev/ge adv_pauseRX 1
#ndd -set /dev/ge adv_1000autoneg_cap 0
# ge1
#ndd -set /dev/ge instance 1
#ndd -set /dev/ge adv_1000fdx_cap 1
#ndd -set /dev/ge adv_1000hdx_cap 0
#ndd -set /dev/ge adv_pauseTX 1
#ndd -set /dev/ge adv_pauseRX 1
#ndd -set /dev/ge adv_1000autoneg_cap 0
# ce-Interfaces (GigaSwift 1.0 UTP)
# example: forced 1000 Mbit/s, 802.3x Flow Control send and receive
# ce0
#ndd -set /dev/ce instance 0
# Master values, change in forced 1000 Mbit/s back-to-back config only:
#ndd -set /dev/ce link_master 0 # one link partner 1, the other 0 (ce <=1.118)
#ndd -set /dev/ce master_cfg_enable 1 # enable usage of master_cfg_value (ce >1.118)
#ndd -set /dev/ce master_cfg_value 0 # one link partner 1, the other 0 (ce >1.118)
# Speed/Mode values, set the desired to 1, all other to 0:
#ndd -set /dev/ce adv_1000fdx_cap 1
#ndd -set /dev/ce adv_1000hdx_cap 0
#ndd -set /dev/ce adv_100fdx_cap 0
#ndd -set /dev/ce adv_100hdx_cap 0
#ndd -set /dev/ce adv_10fdx_cap 0
#ndd -set /dev/ce adv_10hdx_cap 0
#ndd -set /dev/ce adv_asmpause_cap 0
#ndd -set /dev/ce adv_pause_cap 1
#ndd -set /dev/ce adv_autoneg_cap 0
# ce1
#ndd -set /dev/ce instance 1
# Master values, change in forced 1000 Mbit/s back-to-back config only:
#ndd -set /dev/ce link_master 0 # one link partner 1, the other 0 (ce <=1.118)
#ndd -set /dev/ce master_cfg_enable 1 # enable usage of master_cfg_value (ce >1.118)
#ndd -set /dev/ce master_cfg_value 0 # one link partner 1, the other 0 (ce >1.118)
# Speed/Mode values, set the desired to 1, all other to 0:
#ndd -set /dev/ce adv_1000fdx_cap 1
#ndd -set /dev/ce adv_1000hdx_cap 0
#ndd -set /dev/ce adv_100fdx_cap 0
#ndd -set /dev/ce adv_100hdx_cap 0
#ndd -set /dev/ce adv_10fdx_cap 0
#ndd -set /dev/ce adv_10hdx_cap 0
#ndd -set /dev/ce adv_asmpause_cap 0
#ndd -set /dev/ce adv_pause_cap 1
#ndd -set /dev/ce adv_autoneg_cap 0
# switch MTU path discovery off
#ndd -set /dev/ip ip_path_mtu_discovery 0
# TCP/UDP buffer tunings
#ndd -set /dev/tcp tcp_xmit_hiwat 65536
#ndd -set /dev/tcp tcp_recv_hiwat 65536
#ndd -set /dev/udp udp_xmit_hiwat 65536
#ndd -set /dev/udp udp_recv_hiwat 65536
# TCP congestion window size, for Solaris <= 2.5, only
#ndd -set /dev/tcp tcp_cwnd_max 65535
# Change TCP maximum retransmission interval, for Solaris <= 7, only
#ndd -set /dev/tcp tcp_rexmit_interval_max 60000
# Change number of TCP slow start initial packets to work arround
# slow start bug in BSD stack and Windows. For Solaris <= 7, only
#ndd -set /dev/tcp tcp_slow_start_initial 2
;;
'stop')
echo "No kernel parameters changed."
;;
*)
echo "Usage: $0 {start|stop}"
;;
esac
exit 0 |
| Sponsored Links | |
|
|
#7
|
||||
|
||||
|
Getting conflicting information when I try and see what my Duplex settings are: Code:
# dladm show-dev bge0 link: up speed: 100 Mbps duplex: half bge1 link: unknown speed: 0 Mbps duplex: unknown ce0 link: unknown speed: 0 Mbps duplex: unknown bge2 link: up speed: 100 Mbps duplex: half bge3 link: up speed: 100 Mbps duplex: half ce1 link: unknown speed: 0 Mbps duplex: unknown # kstat -p bge:0::link_duplex bge:0:mac:link_duplex 1 bge:0:mii:link_duplex 1 bge:0:parameters:link_duplex 1 # kstat -p bge:2::link_duplex bge:2:mac:link_duplex 1 bge:2:mii:link_duplex 1 bge:2:parameters:link_duplex 1 # kstat -p bge:3::link_duplex bge:3:mac:link_duplex 1 bge:3:mii:link_duplex 1 bge:3:parameters:link_duplex 1 As you can see the dladm command shows my bge0, bge2, and bge3 interfaces are HALF-duplex and the Kstat shows them to be FULL. Can someone show me the correct way to view what my settings really are? I have had a hard time googling useful info on bge interfaces. They seem to not play well with conventional commands. Last edited by DukeNuke2; 02-03-2009 at 03:05 PM.. |
| Sponsored Links | ||
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Determine the ethernet (NIC) card speed. | devtakh | UNIX for Advanced & Expert Users | 3 | 04-19-2011 04:53 AM |
| changing speed of NIC Card in linux | manoj.solaris | Linux | 3 | 11-04-2009 10:16 AM |
| how can i see ethernet card speed in solars | nag.mi2000 | UNIX for Dummies Questions & Answers | 4 | 05-29-2008 10:41 AM |
| Change speed on network card | hshapiro | Solaris | 7 | 03-13-2008 08:57 AM |
| How to check Virtual NIC card speed on solaris | pray44u | Solaris | 3 | 07-06-2006 08:14 PM |
|
|