cap_100hdx man page on Solaris

Man page or keyword search:  
man Server   20652 pages
apropos Keyword Search (all sections)
Output format
Solaris logo
[printable version]

ieee802.3(5)	      Standards, Environments, and Macros	  ieee802.3(5)

NAME
       ieee802.3,    cap_autoneg,    cap_1000fdx,   cap_1000hdx,   cap_100fdx,
       cap_100hdx, cap_10fdx, cap_10hdx,  cap_rem_fault,  cap_pause,  cap_asm‐
       pause,	   adv_cap_autoneg,	 adv_cap_1000fdx,     adv_cap_1000hdx,
       adv_cap_100fdx,	  adv_cap_100hdx,    adv_cap_10fdx,	adv_cap_10hdx,
       adv_cap_pause,	 adv_cap_asmpause,    adv_rem_fault,   lp_cap_autoneg,
       lp_cap_1000fdx,	  lp_cap_1000hdx,    lp_cap_100fdx,	lp_cap_100hdx,
       lp_cap_10fdx,	  lp_cap_10hdx,	    lp_cap_pause,     lp_cap_asmpause,
       lp_rem_fault, xcvr_addr,	 xcvr_id,  xcvr_inuse,	link_up,  link_duplex,
       link_pause, link_asmpause - Ethernet mii kstat and ndd parameters

DESCRIPTION
       This page describes the kernel statistics and the ndd(1M) configuration
       parameters used to monitor and configure the Ethernet physical layer.

       The cap_* parameters exist in the kernel	 statistics  for  an  Ethernet
       device.	The  parameters	 describe  the maximum capability of a device.
       When the value of a statistic is	 1,  the  device  has  the  capability
       described.  When	 the value is 0, the device does not have the capabil‐
       ity.

       The exceptions to this rule are the cap_asmpause and cap_pause  parame‐
       ters which are explained later in the page.

       cap_autoneg	       Capable of auto-negotiation

       cap_1000fdx	       Capable of 1000 full duplex operation

       cap_1000hdx	       Capable of 1000 half duplex operation

       cap_100fdx	       Capable of 100 full duplex operation

       cap_100hdx	       Capable of 100 half duplex operation

       cap_10fdx	       Capable of 10 full duplex operation

       cap_10hdx	       Capable of 10 half duplex operation

       cap_rem_fault	       Capable of reporting locally detected faults to
			       link partner

       The adv_cap_* parameters exist in the kernel statistics and represent a
       mirror  image  of  the  ndd  adv_*_cap  parameter  list for an Ethernet
       device. The ndd adv_*_cap tuning parameters allow fine grain control of
       the Ethernet device physical layer. The parameters are also a subset of
       the cap_* statistics. If	 the  cap_*  value  is	0,  the	 corresponding
       adv_cap_*  must	also  be  0.  The  exceptions  to  this	 rule  are the
       adv_cap_asmpause and adv_cap_pause parameters.

       When auto-negotiation is enabled, the adv_*_cap statistics  show	 which
       capabilities  are advertised to the link partner. When auto-negotiation
       is disabled in forced mode, the statistics precisely show  how  a  link
       should  function	 and  that  it	must be matched on the link partner to
       achieve a valid link up.

       Statistics with values other than 0 and 1 are  also  described  in  the
       following.

       adv_cap_autoneg	       Advertise auto-negotiation capability

       adv_cap_1000fdx	       Advertise 1000 full duplex capability

       adv_cap_1000hdx	       Advertise 1000 half duplex capability

       adv_cap_100fdx	       Advertise 100 full duplex capability

       adv_cap_100hdx	       Advertise 100 half duplex capability

       adv_cap_10fdx	       Advertise 10 full duplex capability

       adv_cap_10hdxv	       Advertise 10 half duplex capability

       adv_rem_fault	       Fault value reported by the local system to the
			       peer

			       0	Link is good

			       1	Off line

			       2	Link failure

			       3	Auto-negotiation failure

       The lp_cap_* parameters exist as	 kernel	 statistics  for  an  Ethernet
       device.	The statistics are the advertised capabilities provided by the
       link partner on completion of  auto-negotiation.	 If  the  capabilities
       match  the  capabilities	 provided in the local advertisement, the link
       can proceed to a link up state. If no match is found, the link  remains
       down. In two other instances, lp_cap_* values might all be zero: when a
       cable is not present, when forced mode is enabled.

       lp_cap_autoneg	       Link partner advertises auto-negotiation	 capa‐
			       bility

       lp_cap_1000fdx	       Link  partner advertises 1000 full duplex capa‐
			       bility

       lp_cap_1000hdx	       Link partner advertises 1000 half duplex	 capa‐
			       bility

       lp_cap_100fdx	       Link  partner  advertises 100 full duplex capa‐
			       bility

       lp_cap_100hdx	       Link partner advertises 100 half	 duplex	 capa‐
			       bility

       lp_cap_10fdx	       Link partner advertises 10 full duplex capabil‐
			       ity

       lp_cap_10hdx	       Link partner advertises 10 half duplex capabil‐
			       ity

       lp_rem_fault	       Fault value the remote system reports

			       0	Link is good

			       1	Off line

			       2	Link failure

			       3	Auto-negotiation failure

       The  xcvr_*  kernel  statistics	provide information about the physical
       layer device that is in use.

       xcvr_addr	       MII address in the 0 to 31 range of the	physi‐
			       cal  layer  device  in use for a given Ethernet
			       device

       xcvr_id		       MII transceiver manufacturer and device ID

       xcvr_inuse	       MII transceiver type, based  on	the  following
			       list:

			       0 other	       Undefined

			       1 none	       MII  present,  but nothing con‐
					       nected

			       2 10Mb/s	       10Mb/s Manchester encoding

			       3 100BaseT4     100 Mb/s 8B/6T

			       4 100BaseX      100 Mb/s 4B/5B

			       5 100BaseT2     100 Mb/s PAM5X5

			       6 1000BaseX     1000 Mb/s 8B/10B

			       7 1000BaseT     1000 Mb/s 4D-PAM5

			       The above values define maximum capability.  In
			       many  cases,  lower speeds can occur. The cap_*
			       statistics must	be  viewed  to	establish  the
			       range of capability.

       The  link_*  kernel  statistics show the link state at the local end of
       the connection.

       link_up		      1	       Link is up
			      0	       Link is down
       link_duplex	      2	       Full duplex link
			      1	       Half duplex link
			      0	       Unknown

       The cap_asmpause, cap_pause, adv_cap_asmpause, and adv_cap_pause param‐
       eters  do  not  follow the rules of other cap_* and adv_cap_* kstats or
       parameters.

       cap_pause	       The meaning of this statistic  depends  on  the
			       value provided by cap_asmpause.

			       if cap_asmpause = 1, pause one direction

			       1	Send   pause   frames  when  there  is
					receive congestion.

			       0	Pause transmission when a pause	 frame
					is received.

			       if cap_asmpause = 0, pause in either direction

			       1	Send   pause   frames  when  there  is
					receive congestion, and	 pause	trans‐
					mission	  when	 a   pause   frame  is
					received.

			       0	Pause capability is not	 available  in
					either direction.

       cap_asmpause	       Asymmetric pause capability

       The  adv_cap_pause  and	adv_cap_asmpause statistics are limited by the
       available settings for cap_pause and cap_asmpause. For a device that is
       fully  capable  of  pausing  both Rx (receive) and Tx (transmit) opera‐
       tions, the settings available are defined in the truth table that  fol‐
       lows  the  adv_cap_pause	 and  adv_cap_asmpause	parameter descriptions
       below.

       adv_cap_pause	       The meaning of this statistic  depends  on  the
			       value provided by adv_cap_asmpause.

			       if adv_cap_asmpause = 1

			       1	Send   pause   frames  when  there  is
					receive congestion.

			       0	Pause transmission when a pause	 frame
					is received.

			       if adv_cap_asmpause = 0

			       1	Send   pause   frames  when  there  is
					receive congestion, and	 pause	trans‐
					mission	  when	 a   pause   frame  is
					received.

			       0	Pause capability is not	 available  in
					either direction.

       adv_cap_asmpause	       Asymmetric pause capability

       The  cap_asmpause  and  cap_pause  statistics  show the capability of a
       device and also	limit  the  legal  setting  for	 adv_cap_asmpause  and
       adv_cap_pause.  The  following  truth  table  describes	the  available
       adv_cap_asmpause and adv_cap_pause settings limited by cap_asmpause and
       cap_pause statistics. The abbreviations below are used in the table.

       CA	       cap_asmpause

       CP	       cap_pause

       AA	       adv_cap_asmpause

       AP	       adv_cap_pause

       CP     CA       AP      AA      Description
       0      0	       0       0       No pause in use
       0      0	       x       x       Device  not  pause  capable, cannot
				       set
       0      1	       0       0       Asymmetric Rx  pause  capable,  but
				       not advertised
       0      1	       0       1       Asymmetric  Rx  pause  capable  and
				       advertised
       0      1	       1       0       Asymmetric Rx pause capable, making
				       it  impossible  advertise symmetric
				       pause
       0      1	       1       1       Asymmetric Rx pause capable, making
				       it  impossible advertise asymmetric
				       Tx pause
       1      0	       0       0       Symmetric pause	capable,  but  not
				       advertised
       1      0	       0       1       Symmetric  pause capable, advertis‐
				       ing asymmetric Rx pause only
       1      0	       1       0       Symmetric pause capable,	 advertis‐
				       ing symmetric Rx and Tx pause capa‐
				       bility
       1      0	       1       1       Symmetric pause capable,	 advertis‐
				       ing asymmetric Tx pause only
       1      1	       0       0       Asymmetric  Tx  pause  capable, but
				       not advertised
       1      1	       0       1       Asymmetric Tx pause capable, making
				       it impossible to advertise Asymmet‐
				       ric Rx pause
       1      1	       1       0       Asymmetric Tx pause capable, making
				       it  impossible  advertise symmetric
				       pause
       1      1	       1       1       Asymmetric  Tx  pause  capable  and
				       advertised

       In  the	cases  above,  an  error is posted when a device driver cannot
       advertise.  A new setting is ignored and values revert to the  previous
       setting.

       The  lp_cap_pause  and the lp_cap_asmpause provide the advertised capa‐
       bilities of the link partners.

       lp_cap_pause	       The meaning of this statistic  depends  on  the
			       value provided by lp_cap_asmpause.

			       if lp_cap_asmpause = 1

			       1	Send   pause   frames  when  there  is
					receive congestion.

			       0	Pause transmission when a pause	 frame
					is received.

			       if lp_cap_asmpause = 0

			       1	Send   pause   frames  when  there  is
					receive congestion, and	 pause	trans‐
					mission	  when	 a   pause   frame  is
					received.

			       0	Pause capability is not	 available  in
					either direction.

       lp_cap_asmpause	       Asymmetric pause capability

       When  adv_*pause_cap  and  lp_*pause_cap	 are compared on completion of
       auto-negotiation, the  chosen  flow  control  mechanism	for  the  link
       depends on what is most meaningful.

       link_asmpause	       1 indicates flow control in one direction.

			       0  indicates  flow  control  in both directions
			       when link_pause is set to one.

       link_pause	       if link_asmpause = 0

			       1	Flow control in both Rx and Tx	direc‐
					tions is available.

			       0	No flow control available on the link.

			       if link_asmpause = 1

			       1	The  local station will honor received
					pause frames by temporarily suspending
					transmit of further frames.

			       0	In  the	 event	of receive congestion,
					the  local  station  will  transmit  a
					pause frame to the peer.

       lp_cap_asmpause	       Asymmetric pause capability

       The  following truth table illustrates the meaningful flow control com‐
       binations related to local and link partner configurations.  The abbre‐
       viations below are used in the table.

       AA		       adv_cap_asmpause

       AP		       adv_cap_pause

       LAC		       lp_cap_asmpause

       LPC		       lp_cap_pause

       LA		       link_asmpause

       LP		       link_pause

       AA    AP	    LAC	   LPC	 LA	LP    Description
       1     0	    1	   1	 1	0     Local  station  will  Tx	a pause
					      when Rx is congested.
       0     1	    0	   1	 0	1     Flow control in both  Rx	and  Tx
					      directions.
       x     1	    1	   0	 1	1     Local station will honor received
					      Pause frames by temporarily  sus‐
					      pending Transmit.
       x     x	    x	   x	 0	0     All other combinations: Flow con‐
					      trol not avilable on the link

       When forced mode is enabled, the current	 setting  of  adv_cap_asmpause
       and  adv_cap_pause  are	used  for  the	link.  The  link_asmpause  and
       link_pause  become  equal   to	the   current	adv_cap_asmpause   and
       adv_cap_pause  settings.	 The  above table also applies in forced mode,
       but the link partner configuration must be checked to verify that  flow
       control is operating on the link.

SEE ALSO
       ndd(1M),	 driver.conf(4),  bge(7D),  ce(7D), dlpi(7P), eri(7D), ge(7D),
       gld(7D), hme(7D), qfe(7D)

NOTES
       When adv_cap_autoneg is set to 0, the highest priority speed and duplex
       is used for forced mode.

       The  highest  priority  is the highest speed at full duplex. The lowest
       priority is the lowest speed at half duplex.

       MII transceivers can exist internally to a system or can	 be  connected
       to an external MII connector. Typically, an internal transceiver has an
       xcvr_addr of 1, while an external connection has an xcvr_addr of 0.

SunOS 5.10			  13 Sep 2004			  ieee802.3(5)
[top]

List of man pages available for Solaris

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net