In order to leverage IP Instances functionality, a Generic Network Driver (GLD) version 3 interface must be used.To determine if a particular network interface is using GLDv3, use the dladm(1M) command:
If a particular interface reports its type as legacy, then it is not using the GLDv3 framework and therefore cannot be used by IP Instances.
Mine shows:
So I don't know whether or not it is using the GLDv3 framework or not.
okay people i need some help:
i was able to configure zones on my solaris 10 server, the problem is I can't ssh into the zones!!! I can zlogin -C zone2 successfully for both zones. Am I missing something? I can ping the zones, but can't ssh. From the zones, I can ping my global server. (7 Replies)
Hi All,
I am getting zone error
# /usr/sbin/zoneadm -z asflxpoc1 boot -s
could not verify net address=169.185.246.229 physical=ce0: No such device or address
could not verify net address=169.185.246.230 physical=ce0: No such device or address
Any ideas for this error message.
The... (13 Replies)
Hello All,
I have a list of Local Zones in my list. I want to find out their Global Zone names exactly....I know the command "arp ..."But I dont know how to filter it correctly and find it out.
Thanks in advance,
Jacky (9 Replies)
I have a Solaris 10 box configured with a global zone and 3 non-global zones. All of the zones need to be configured so they can access and run an application in the global zone located at /export/home. How do i make this application and all of its accompanying files available to the 3 non-global... (3 Replies)
Hi Every,
I would like to know some questions on Zones???
1.what are types of zones we can install in global zone???
2.Exact difference between sparce root and whole root???
3.can we change the ip address of a running zone???
4.how to find our in which zone we are running and how many... (8 Replies)
Hi,
I created a zone with separate /usr for the zone.
when I do ping to newly created zone it showing alive, I am able to login through zone console zlogin -C -E <zone name>
I created a test account on zone which is already existing under global zone and try to ssh, it is working fine but... (1 Reply)
Hi friends,
Actually I faced problem in solaris zone. i was created 4 zones on my server. but one of them is not working ?
so, where i wll get the error logs, and how to troubleshoot the problem.
i have some kind of urgency.
Please reply. (2 Replies)
Hi there
when setting my zone config file up, I would naturally set 'set ip-type=exclusive' but I wanted to know, whether on the 'set physical=' line whether I could use a virtual interface that ive created in the global zone such as bge0:1.
for example
create -b
set... (5 Replies)
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
I'm trying to migrate a Solaris 10 flar archive from a Sun M3000 to a T4-1. When I first created the zone I followed the Oracle instructions here: Transitioning an Oracle Solaris 10 Instance to an Oracle Solaris 11 System - Transitioning From Oracle Solaris 10 to Oracle Solaris 11 That worked... (6 Replies)
Discussion started by: Michele31416
6 Replies
LEARN ABOUT OPENSOLARIS
igb
igb(7D) Devices igb(7D)NAME
igb - Intel 82575 1Gb PCI Express NIC Driver
SYNOPSIS
/dev/igb*
DESCRIPTION
The igb Gigabit Ethernet driver is a multi-threaded, loadable, clonable, GLD-based STREAMS driver supporting the Data Link Provider
Interface, dlpi(7P), on Intel 82575 Gigabit Ethernet controllers.
The igb driver functions include controller initialization, frame transmit and receive, promiscuous and multicast support, and error
recovery and reporting.
The igb 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
igb 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/igb, is used to access all Intel 82575 Gigabit devices installed within the system.
The igb driver is managed by the dladm(1M) command line utility, which allows VLANs to be defined on top of igb instances and for igb
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 your DL_INFO_REQ are:
o Maximum SDU is 9000.
o Minimum SDU is 0.
o DLSAP address length is 8.
o MAC type is DL_ETHER.
o SAP (Service Access Point) 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 SAP with the stream.
CONFIGURATION
By default, the igb 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):
1000 Mbps, full-duplex.
100 Mbps, full-duplex.
100 Mbps, half-duplex.
10 Mbps, full-duplex.
10 Mbps, half-duplex.
The auto-negotiation protocol automatically selects speed (1000 Mbps, 100 Mbps, or 10 Mbps) and operation mode (full-duplex or half-duplex)
as the highest common denominator supported by both link partners.
Alternatively, you can set the capabilities advertised by the igb device using ndd(1M). The driver supports a number of parameters whose
names begin with adv_ (see below). Each of these parameters contains a boolean value that determines if the device advertises that mode of
operation. For example, the adv_1000fdx_cap parameter indicates if 1000M full duplex is advertised to link partner. The adv_autoneg cap
parameter controls whether auto-negotiation is performed. If adv_autoneg_cap is set to 0, the driver forces the mode of operation
selected by the first non-zero parameter in priority order as shown below:
(highest priority/greatest throughput)
adv_1000fdx_cap 1000Mbps full duplex
adv_100fdx_cap 100Mpbs full duplex
adv_100hdx_cap 100Mbps half duplex
adv_10fdx_cap 10Mpbs full duplex
adv_10hdx_cap 10Mpbs half duplex
(lowest priority/least throughput)
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.
FILES
/dev/igb* Special character device.
/kernel/drv/igb 32-bit device driver (x86).
/kernel/drv/amd64/igb 64-bit device driver (x86).
/kernel/drv/sparcv9/igb 64-bit device driver (SPARC).
/kernel/drv/igb.conf Configuration file.
SEE ALSO dladm(1M), ndd(1M), netstat(1M), driver.conf(4), attributes(5), streamio(7I), dlpi(7P),
Writing Device Drivers
STREAMS Programming Guide
Network Interfaces Programmer's Guide
SunOS 5.11 20 Jul 2007 igb(7D)