Sponsored Content
Operating Systems Solaris Interface e1000g0 not showing in running state Post 302778087 by rajjat2 on Saturday 9th of March 2013 01:49:31 PM
Old 03-09-2013
see the other interface o/p:
ossuser@PNR1RAD01 # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 2
inet 10.200.2.73 netmask fffffff8 broadcast 10.200.2.79
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.200.3.58 netmask ffffffc0 broadcast 10.200.3.63

And one more observation:



root@PNR1RAD01 # dladm show-dev
e1000g0 link: down speed: 0 Mbps duplex: half
e1000g1 link: up speed: 1000 Mbps duplex: full
e1000g2 link: unknown speed: 0 Mbps duplex: half
e1000g3 link: unknown speed: 0 Mbps duplex: half

This link shows down in this command o/p although in ifconfig o/p it shows up but noot the running state as e1000g1 interface.
 

10 More Discussions You Might Find Interesting

1. Solaris

Interface not showing : Xview error

Hi I'm having a big trouble running a configuration tool (ftamtool) which uses xview on sunos 5.8, it refuses to start and says: XView error: could not load font 'FONT_FAMILY_SANS_SERIF... How to force the program to use installed fonts and where are fonts installed available to use ? ... (0 Replies)
Discussion started by: andryk
0 Replies

2. IP Networking

Solaris 9 new pumbed interface will not enter a RUNNING state

I'm trying to plumb a new interface bge1 on my machine: root@obms2-com-indianapolis-in:/root# ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet... (3 Replies)
Discussion started by: R37ribution
3 Replies

3. Shell Programming and Scripting

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies

4. Programming

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies

5. Solaris

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies

6. Solaris

how to force e1000g0 interface in solaris 10

Hi all, I encounter some problem with my e1000g interface running on sol 10. I can't permanently change the auto-nego to disable, if i use ndd commands, it will only stay until the next reboot. But i can't change the link speed either is set to /etc/init.d/nddconfig or using ndd commands. ... (1 Reply)
Discussion started by: mailbox80
1 Replies

7. Solaris

Not showing n/w interface name in Solaris with ifconfig -a

hi frineds in sunfire 6800 server for one domain when ever i am giving ifconfig -a interface names like hme0,hme1.......are not showing.Actually in the server hme0,hme1,qfe are showing .when i was tried with the cat /etc/path_to_intstshowing tphysical interfcace names . after giving the... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

8. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

9. Solaris

Network interface showing wrong configuratoin

on both of my T2000 I am seeing same values of 100Mbps for e1000g0 ethernet port. i know all four ethernet ports on T2000 are gigabit ports so why is my first link showing as 100Mbps and how can i correct it? # dladm show-dev e1000g0 link: up speed: 100 Mbps ... (1 Reply)
Discussion started by: aliyesami
1 Replies

10. Solaris

How to increase the e1000g0 interface speed in Solaris?

Hi All, Please let me know the step by step process to set the e1000g0 interface speed to 1000mbps with full duplex from 100fdx and how to disable the auto negotiation with switch?. Thanks and Regards, Ganesh. (7 Replies)
Discussion started by: gsrungav
7 Replies
dmfe(7D)							      Devices								  dmfe(7D)

NAME
dmfe - Davicom Fast Ethernet driver for Davicom DM9102A SYNOPSIS
/platform/sun4u/kernel/drv/sparcv9/dmfe DESCRIPTION
The dmfe Ethernet device provides 100Base-TX networking interfaces using the Davicom DM9102A chip, which incorporates its own internal transceiver. The dmfe driver is a multithreaded, loadable, clonable, GLD-based STREAMS driver. Multiple controllers installed within the system are supported by the driver. The dmfe driver functions include controller initialization, frame transmit and receive, promiscuous and multicast support, and error recovery and reporting. The 100Base-TX standard specifies an auto-negotiation protocol to automatically select the mode and speed of operation. The internal trans- ceiver is capable of performing autonegotiation with the remote-end of the link (link partner) and receives the capabilities of the remote end. It selects the highest common denominator mode of operation based on the priorities. The internal transceiver also supports a forced-mode of operation under which the driver selects the operational mode. APPLICATION PROGRAMMING INTERFACE
The /dev/dmfe cloning character-special device is used to access all Davicom DM9102A devices installed in the system. The dmfe driver is dependent on /kernel/misc/gld, a loadable kernel module that provides the dmfe driver with the DLPI and STREAMS func- tionality required of a LAN driver. See gld(7D) for more details on the primitives supported by the driver. 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. If the ppa field value does not correspond to a valid device instance number for this system, an error (DL_ERROR_ACK) is returned. The device is initialized on first attach and de-ini- tialized (stopped) at last detach. The values returned by the driver in the DL_INFO_ACK primitive in response to a DL_INFO_REQ are as follows: o Maximum SDU is 1500 (ETHERMTU - defined in sys/ethernet.h). o Minimum SDU is 0. o DLSAP address length is 8. o MAC type is DL_ETHER. o The sap length value is -2, meaning the physical address component is followed immediately by a 2-byte sap component within the DLSAP address. o The 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 dmfe driver performs auto-negotiation to select the speed and mode of the link. Link speed and mode can be 100 Mbps (full or half-duplex) or 10 Mbps (full or half-duplex) as described in the 100Base-TX standard. The auto-negotiation protocol automatically selects speed mode (either 100 Mbps or 10 Mbps) and operation mode (either full-duplex or half- duplex) as the highest common denominator supported by both link partners. Because the dmfe device supports all modes, this effectively selects the highest-throughput mode supported by the other device. Alternatively, you can explicitly specify the link parameters by adding entries to the dmfe driver configuration file (/platform/sun4u/ker- nel/drv/dmfe.conf). You can set the speed parameter to 10 or 100 to force dmfe devices to operate at the specified speed. Additionally, you can set the full-duplex parameter to 0 or 1 to disable or force full-duplex operation, respectively. Note that specifying either "speed" or "full-duplex" explicitly disables auto-negotiation. To enable the driver to determine the appropri- ate setting for each parameter, you should always set both parameters. If it is necessary to force either speed or duplex setting (for example, because the dmfe device is connected to an ancient device or hub that does not support auto-negotiation), both parameters should be explicitly specified to match the requirements of the external device. FILES
/dev/dmfe Character special device /platform/sun4u/kernel/drv/dmfe.conf dmfe configuration file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5), gld(7D), dlpi(7P), streamio(7I) Writing Device Drivers STREAMS Programming Guide Network Interfaces Programmer's Guide SunOS 5.10 23 July 2003 dmfe(7D)
All times are GMT -4. The time now is 03:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy