bnx1 link : unknown


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users bnx1 link : unknown
# 1  
Old 09-24-2009
bnx1 link : unknown

Hi,

Please could someone advise, how to enable device bnx1 to become up (online). See below for details :

dladm show-dev
e1000g0 link: up speed: 1000 Mbps duplex: full
e1000g1 link: up speed: 1000 Mbps duplex: full
e1000g2 link: up speed: 1000 Mbps duplex: full
e1000g3 link: up speed: 1000 Mbps duplex: full
e1000g4 link: up speed: 1000 Mbps duplex: full
e1000g5 link: unknown speed: 0 Mbps duplex: half
bnx0 link: unknown speed: 100 Mbps duplex: unknown
bnx1 link: unknown speed: 1000 Mbps duplex: unknown

This is system is a HP x86 solaris box, I have checked the bnx.conf file and it is set to :

0 : AutoNegotiate

see below :

speed=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;


regards,

Tek
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

/var/adm/messages (insterface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies

2. Solaris

/var/adm/messages (interface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# cat /var/adm//messages Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies

3. UNIX for Dummies Questions & Answers

[Solved] Symbolic link not allowed or link target not accessible

Hi everybody, I read about treads realted to this issue but they did not resovle issue given below. Please help me resolve issue given below I have html file under /srv/www/htdocs/actual_folder ls actual_folder/ test.html and following link works... (0 Replies)
Discussion started by: newbielgn
0 Replies

4. Programming

g++ fails to link to static library when compilation and link in single command

Hello All, I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it: I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable Approach 1 works... (0 Replies)
Discussion started by: magelord
0 Replies

5. IP Networking

bnx1 link : unknown ?

Hi, Please could someone advise, how to enable device bnx1 to become up (online). See below for details : dladm show-dev e1000g0 link: up speed: 1000 Mbps duplex: full e1000g1 link: up speed: 1000 Mbps duplex: full e1000g2 link: up speed: 1000 Mbps duplex: full e1000g3 link: up speed:... (0 Replies)
Discussion started by: venhart
0 Replies

6. UNIX for Dummies Questions & Answers

Difference between hard link and soft link

Hi Experts, Please help me out to find out difference between a hard link and a soft link. I am new in unix plz help me with some example commands ( for creating such links). Regards S.Kamakshi :) (2 Replies)
Discussion started by: kamakshi s
2 Replies

7. Solaris

PING - Unknown host 127.0.0.1, Unknown host localhost - Solaris 10

Hello, I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems: 1. When I execute the command ping, I get weird results: bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies

8. UNIX for Dummies Questions & Answers

need some info about symbolic link and hard link

hello folks how y'all doin well i have some questions about symbolic link and hard link hope some one answer me i open terminal and join as root and i wrote ln -s blah blah then i wrote ls i see red file called blah blah but didn't understand what is this can some one explain and... (2 Replies)
Discussion started by: detective linux
2 Replies

9. UNIX for Dummies Questions & Answers

Difference between hard link and soft link in unix

Hi All, Can any one please explain me what is the difference between hard link and soft link in UNIX. Thanks in advance Raja Chokalingam. (2 Replies)
Discussion started by: RAJACHOKALINGAM
2 Replies

10. UNIX for Advanced & Expert Users

Differences between hard link and soft link

Hi all! I'd like to know the differences between hard links and soft links. I've already read the ln manpage, but i'm not quite sure of what i understood. Does a hard link sort of copy the file to a new name, give it the same inode number and same rights? What exactly should I do to do this:... (3 Replies)
Discussion started by: penguin-friend
3 Replies
Login or Register to Ask a Question
bge(7D) 							      Devices								   bge(7D)

NAME
bge - SUNW,bge Gigabit Ethernet driver for Broadcom BCM57xx SYNOPSIS
/dev/bge* DESCRIPTION
The bge Gigabit Ethernet driver is a multi-threaded, loadable, clonable, GLD-based STREAMS driver supporting the Data Link Provider Inter- face, dlpi(7P), on Broadcom BCM57xx (BCM5700/5701/5703/5704/5705/5705M/5714/5721/5751/5751M/5782/5788 on x86) Gigabit Ethernet controllers fitted to the system motherboard. With the exception of BCM5700/BCM5701/BCM5704S, these devices incorporate both MAC and PHY functions and provide three-speed (copper) Ethernet operation on the RJ-45 connectors. (BCM5700/BCM5701/BCM5704S do not have a PHY integrated into the MAC chipset.) The bge driver functions include controller initialization, frame transmit and receive, promiscuous and multicast support, and error recov- ery and reporting. The bge driver and hardware support auto-negotiation, a protocol specified by the 1000 Base-T standard. Auto-negotiation allows each device to advertise its capabilities and discover those of its peer (link partner). The highest common denominator supported by both link partners is automatically selected, yielding the greatest available throughput, while requiring no manual configuration. The bge driver also allows you to configure the advertised capabilities to less than the maximum (where the full speed of the interface is not required), or to force a specific mode of operation, irrespective of the link partner's advertised capabilities. APPLICATION PROGRAMMING INTERFACE
The cloning character-special device, /dev/bge, is used to access all BCM57xx devices ( (BCM5700/5701/5703/5704, 5705/5714/5721/5751/5751M/5782 on x86) fitted to the system motherboard. The bge driver is managed by the dladm(1M) command line utility, which allows VLANs to be defined on top of bge instances and for bge instances to be aggregated. See dladm(1M) for more details. You must send an explicit DL_ATTACH_REQ message to associate the opened stream with a particular device (PPA). The PPA ID is interpreted as an unsigned integer data type and indicates the corresponding device instance (unit) number. The driver returns an error (DL_ERROR_ACK) if the PPA field value does not correspond to a valid device instance number for the system. The device is initialized on first attach and de- initialized (stopped) at last detach. The values returned by the driver in the DL_INFO_ACK primitive in response to a DL_INFO_REQ are: o Maximum SDU (default 1500). o Minimum SDU (default 0). o DLSAP address length is 8. o MAC type is DL_ETHER. o SAP length value is -2, meaning the physical address component is followed immediately by a 2-byte SAP component within the DLSAP address. o Broadcast address value is the Ethernet/IEEE broadcast address (FF:FF:FF:FF:FF:FF). Once in the DL_ATTACHED state, you must send a DL_BIND_REQ to associate a particular Service Access Point (SAP) with the stream. CONFIGURATION
By default, the bge driver performs auto-negotiation to select the link speed and mode. Link speed and mode can be any one of the follow- ing, (as described in the IEEE803.2 standard): o 1000 Mbps, full-duplex o 1000 Mbps, half-duplex o 100 Mbps, full-duplex o 100 Mbps, half-duplex o 10 Mbps, full-duplex o 10 Mbps, half-duplex The auto-negotiation protocol automatically selects: o Speed (1000 Mbps, 100 Mbps, or 10 Mbps) o Operation mode (full-duplex or half-duplex) as the highest common denominator supported by both link partners. Because the bge device supports all modes, the effect is to select the highest throughput mode supported by the other device. Alternatively, you can set the capabilities advertised by the bge device using dladm(1M). The driver supports a number of parameters whose names begin with en_ (see below). Each of these parameters contains a boolean value that determines whether the device advertises that mode of operation. If en_autoneg_cap is set to 0, the driver forces the mode of operation selected by the first non-zero parameter in priority order as listed below: (highest priority/greatest throughput) en_1000fdx_cap 1000Mbps full duplex en_1000hdx_cap 1000Mpbs half duplex en_100fdx_cap 100Mpbs full duplex en_100hdx_cap 100Mpbs half duplex en_10fdx_cap 10Mpbs full duplex en_10hdx_cap 10Mpbs half duplex (lowest priority/least throughput) For example, to prevent the device 'bge2' from advertising gigabit capabilities, enter (as super-user): # dladm set-linkprop -p enable_1000hdx_cap=0 bge2 # dladm set-linkprop -p enable_1000fdx_cap=0 bge2 All capabilities default to enabled. Note that changing any capability parameter causes the link to go down while the link partners renego- tiate the link speed/duplex using the newly changed capabilities. The current settings of the parameters may be found using dladm show-ether. In addition, the driver exports the current state, speed, duplex setting, and working mode of the link via kstat parameters (these are read only and may not be changed). For example, to check link state of device bge0: # dladm show-ether -x bge0 LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE bge0 current up yes 1G-f bi -- capable -- yes 1G-fh,100M-fh,10M-fh bi -- adv -- yes 1G-fh bi -- peeradv -- yes 1G-f bi The output above indicates that the link is up and running at 1Gbps full-duplex with its rx/tx direction pause capability. To extract link state information for the same link using kstat: # kstat bge:0:mac:link_state module: bge instance: 0 name: mac class: net link_state The default MTU is 1500. To enable Jumbo Frames support, you can configure the bge driver by defining the default_mtu property via dladm(1M) or in driver.conf(4) to greater than 1500 bytes (for example: default_mtu=9000). Note that the largest jumbo size supported by bge is 9000 bytes. Additionally, not all bge-derived devices currently support Jumbo Frames. The following devices support Jumbo Frames up to 9KB: BCM5700, 5701, 5702, 5703C, 5703S, 5704C, 5704S, 5714C, 5714S, 5715C and 5715S. Other devices currently do not support Jumbo Frames. FILES
/kernel/drv/bge* 32-bit ELF kernel module. (x86) /kernel/drv/amd64/bge 64-bit ELF kernel module (x86). /kernel/drv/sparcv9/bge 64-bit ELF kernel module (SPARC). ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC, x86 | +-----------------------------+-----------------------------+ SEE ALSO
dladm(1M), driver.conf(4), attributes(5), streamio(7I), dlpi(7P) Writing Device Drivers STREAMS Programming Guide Network Interfaces Programmer's Guide SunOS 5.11 9 Apr 2008 bge(7D)