10/100 dmfe Fast Ethernet The dmfe interface is a another Ethernet system interface applied to the UltraSPARC rack-mounted Netra™ X1 and Sun Fire™ V100 server systems. This interface is much like the others in that its architecture supports a single transmit and receive descriptor run. The number of elements in its descriptor ring is fixed to 32 elements. The physical layer of dmfe is fully configurable using the driver.conf file and ndd command. Table 5-40. Driver Parameters and StatusParameter | Type | Description |
---|
adv_autoneg_cap | Read and Write | Operational mode parameters | adv_100T4_cap | Read and Write | Operational mode parameters | adv_100fdx_cap | Read and Write | Operational mode parameters | adv_100hdx_cap | Read and Write | Operational mode parameters | adv_10fdx_cap | Read and Write | Operational mode parameters | adv_10hdx_cap | Read and Write | Operational mode parameters | autoneg_cap | Read only | Local transceiver auto-negotiation capability | 100T4_cap | Read only | Local transceiver auto-negotiation capability | 100fdx_cap | Read only | Local transceiver auto-negotiation capability | 100hdx_cap | Read only | Local transceiver auto-negotiation capability | 10fdx_cap | Read only | Local transceiver auto-negotiation capability | 10hdx_cap | Read only | Local transceiver auto-negotiation capability | lp_autoneg_cap | Read only | Link partner capability | lp_100T4_cap | Read only | Link partner capability | lp_100fdx_cap | Read only | Link partner capability | lp_100hdx_cap | Read only | Link partner capability | lp_10fdx_cap | Read only | Link partner capability | lp_10hdx_cap | Read only | Link partner capability | link_status | Read only | Current physical layer status | link_speed | Read only | Current physical layer status | link_mode | Read only | Current physical layer status |
Operational Mode Parameters The operational mode parameters adjust the MII capabilities that are used for auto-negotiation. When auto-negotiation is disabled, the highest priority value is taken as the mode of operation. See "Ethernet Physical Layer" on page 152 regarding MII. Table 5-41. Operational Mode ParametersParameter | Values | Description |
---|
adv_autoneg_cap | 0-1 | Local interface capability of auto-negotiation signaling is advertised by the hardware. 0 = Forced mode 1 = Auto-negotiation Default is set to the autoneg_cap parameter. | adv_100T4_cap | 0-1 | Local interface capability of 100-T4 is advertised by the hardware. 0 = Not 100 Mbit/sec T4 capable 1 = 100 Mbit/sec T4 capable Default is set to the 100T4_cap parameter. | adv_100fdx_cap | 0-1 | Local interface capability of 100 full duplex is advertised by the hardware. 0 = Not 100 Mbit/sec full-duplex capable 1 = 100 Mbit/sec full-duplex capable Default is set based on the 100fdx_cap parameter. | adv_100hdx_cap | 0-1 | Local interface capability of 100 half duplex is advertised by the hardware. 0 = Not 100 Mbit/sec half-duplex capable 1 = 100 Mbit/sec half-duplex capable Default is set based on the 100hdx_cap parameter. | adv_10fdx_cap | 0-1 | Local interface capability of 10 full duplex is advertised by the hardware. 0 = Not 10 Mbit/sec full-duplex capable 1 = 10 Mbit/sec full-duplex capable Default is set based on the 10fdx_cap parameter. | adv_10hdx_cap | 0-1 | Local interface capability of 10 half duplex is advertised by the hardware. 0 = Not 10 Mbit/sec half-duplex capable 1 = 10 Mbit/sec half-duplex capable Default is set based on the 10hdx_cap parameter. |
If you are using the interactive mode of ndd with this device to alter the adv_100fdx_cap parameter to adv_10hdx_cap, the changes applied to those parameters are not actually applied to the hardware until the adv_autoneg_cap is changed to its alternative value and then back again. Local Transceiver Auto-negotiation Capability The local transceiver auto-negotiation capability parameters are read-only parameters and represent the fixed set of capabilities associated with the current PHY that is in use. This device allows an external MII PHY device to be attached to the external MII port. Therefore, the capabilities presented in these statistics might vary according to the capabilities of the external MII physical layer device that is attached. Table 5-42. Local Transceiver Auto-negotiation Capability ParametersParameter | Values | Description |
---|
autoneg_cap | 0-1 | Local interface is capable of auto-negotiation signaling. 0 = Can only operate in Forced mode 1 = Capable of auto-negotiation | 100T4_cap | 0-1 | Local interface is capable of 100-T4 operation. 0 = Not 100 Mbit/sec T4 capable 1 = 100 Mbit/sec T4 capable | 100fdx_cap | 0-1 | Local interface is capable of 100 full-duplex operation. 0 = Not 100 Mbit/sec full-duplex capable 1 = 100 Mbit/sec full-duplex capable | 100hdx_cap | 0-1 | Local interface is capable of 100 half-duplex operation. 0 = Not 100 Mbit/sec half-duplex capable 1 = 100 Mbit/sec half-duplex capable | 10fdx_cap | 0-1 | Local interface is capable of 10 full-duplex operation. 0 = Not 10 Mbit/sec full-duplex capable 1 = 10 Mbit/sec full-duplex capable | 10hdx_cap | 0-1 | Local interface is capable of 10 half-duplex operation. 0 = Not 10 Mbit/sec half-duplex capable 1 = 10 Mbit/sec half-duplex capable |
Link Partner Capability The link partner capability parameters are read-only parameters and represent the fixed set of capabilities associated with the attached link partner set of advertised auto-negotiation parameters. These parameters are only meaningful when auto-negotiation is enabled and can be used in conjunction with the operation parameters to establish why there might be problems bringing up the link. Table 5-43. Link Partner Capability ParametersParameter | Values | Description |
---|
lp_autoneg_cap | 0-1 | Link partner interface is capable of auto-negotiation signaling. 0 = Can only operate in forced mode 1 = Capable of auto-negotiation | lp_100T4_cap | 0-1 | Link partner interface is capable of 100-T4 operation. 0 = Not 100 Mbit/sec T4 capable 1 = 100 Mbit/sec T4 capable | lp_100fdx_cap | 0-1 | Link partner interface is capable of 100 full-duplex operation. 0 = Not 100 Mbit/sec full-duplex capable 1 = 100 Mbit/sec full-duplex capable | lp_100hdx_cap | 0-1 | Link partner interface is capable of 100 half-duplex operation. 0 = Not 100 Mbit/sec half-duplex capable 1 = 100 Mbit/sec half-duplex capable | lp_10fdx_cap | 0-1 | Link partner interface is capable of 10 full-duplex operation. 0 = Not 10 Mbit/sec full-duplex capable 1 = 10 Mbit/sec full-duplex capable | lp_10hdx_cap | 0-1 | Link partner interface is capable of 10 half-duplex operation. 0 = Not 10 Mbit/sec half-duplex capable 1 = 10 Mbit/sec half-duplex capable |
Current Physical Layer Status The current physical layer status gives an indication of the state of the link, whether it's up or down, or what speed and duplex it's operating at. These parameters are derived based on the result of establishing the highest priority shared speed and duplex capability when auto-negotiation is enabled or can be pre-configured with Forced mode. Table 5-44. Current Physical Layer Status ParametersParameter | Values | Description |
---|
link_status | 0-1 | Current link status 0 = Link down 1 = Link up | link_speed | 0-1 | This parameter provides the link speed and is only valid if the link is up. 0 = Not 100 Mbit/sec half-duplex capable 1 = 100 Mbit/sec half-duplex capable | link_mode | 0-1 | This parameter provides the link duplex and is only valid if the link is up. 0 = Half duplex 1 = Half duplex |
|