| Platform Notes: SunFDDI Adapter |
|
| Platform Notes: SunFDDI Adapter |
|
| C H A P T E R 3 |
SunFDDI 6.0 on the Sun Enterprise 10000 Server |
Before detaching a system board, you must kill the SNMP daemons and unload the SMT driver from the kernel when using Solaris 2.5.1 and Solaris 2.6 operating environments.
To do this execute the following command from the host window command line:
The Station Management (SMT) daemon starts two agents that collect and return FDDI statistics to a SunNet Manager
(SNM) console. Without the SNMP daemons, network data will not be available for monitoring.
After you have detached the system board and have at least one FDDI adapter plumbed and up, you can restart the SNMP daemons and reload the SMT driver into the kernel. Type the following command from the host window command line:
When you remove a system board that is part of a FDDI configuration, no data will travel through the FDDI adapters once the detach is completed.
To restore the configuration, attach the system board and plumb ( ifconfig ) the FDDI adapters. This allows the data to travel through the FDDI adapters.
The FDDI adapter must have the inet (IP address), netmask, and broadcast values set to be in an active state. The implications of having a FDDI adapter that does not pass data will vary with your specific topology.
|
Note Note - Check the SunSolve database for any patches that may be issued against DR and FDDI 6.0. |
When using AP with FDDI, you must specify an unique MACID for the metanetwork. To ensure that the MACID is set properly at boot time, place ifconfig commands in the /etc/rcS.d/S30rootusr.sh startup script. For more information, refer to the Alternate Pathing User Guide for your version of the AP software.
Before detaching a system board that has an active metanetwork, the FDDI path group must be switched or DR will not allow the system board to be detached.
By switching the path group, the system board is detachable and the data being transmitted/received by the metanetwork continues uninterrupted. All AP devices, whether primary or secondary, are part of the ring. Detaching any FDDI device may constitute breaking the FDDI ring, depending on your specific topology.
The SunFDDI SBus adapters (SAS and DAS) with SunFDDI 6.0 software were verified on the Sun Enterprise 10000 against Solaris 2.5.1, Solaris 2.6 and Solaris 7 operating environments. This verification establishes the maximum number of SunFDDI adapters that can be supported per domain on the Sun Enterprise 10000.
The following sections describe the configurations used in testing SunFDDI SAS adapters.
FDDI SAS adapters in one domain are directly connected to FDDI SAS adapters in another domain and must have the same subnet address. For example, the FDDI SAS adapter in domain A with an IP address of 10.10.1.80 and the FDDI SAS adapter in domain B with an IP address of 10.10.1.81 constitute a valid configuration because both have the same subnet address (10.10.1).
A maximum of two domains can be part of this configuration.
Only two FDDI SAS adapters can communicate with each other. If one fails then the connection is lost.
Does not support alternate pathing (AP).
The FDDI concentrator connects one or more FDDI SAS adapters from multiple domains to the FDDI concentrator, via the M port(s). The FDDI concentrator must have multiple M ports as well as one A and one B port. The FDDI Concentrator used must be smart enough to know the subnet address for each FDDI SAS adapters.
As with Point to Point, the FDDI SAS adapters must have the same subnet address to communicate to one another.
This configuration is AP capable when a domain has two or more FDDI SAS adapters connect to the FDDI concentrator.
Can communicate with multiple domains and multiple FDDI SAS adapters.
The FDDI concentrator is now part of the equation and must be smart enough to know subnet addresses for each of the FDDI SAS adapters connected to the FDDI concentrator.
The following sections describe the configurations used in testing SunFDDI DAS adapters.
The ring configuration consists of connecting the A port of one FDDI DAS adapter to the B port of another FDDI DAS adapter and continuing this process until you have created a ring that encompasses the desired number of FDDI DAS adapters.
This configuration can go across domains. As with SAS, the subnet addresses must be the same in order for FDDI DAS adapters to communicate. The ring configuration is AP capable when two or more FDDI DAS adapters are installed into the ring and are configured in the same domain.
For example, two domains, A and B, connected in a ring configuration with NO FDDI concentrator or any other devices or HUBs involved.
Domain A consists of two system boards. Each system board has one FDDI DAS adapter. System board one has FDDI DAS adapter nf0 and system board two has FDDI DAS adapter nf1.
Domain B consists of one system board with one FDDI DAS adapter nf2.
Based on this information, the cables should be connected as follows to create a ring configuration:
FDDI does not support optical bypass. Therefore, if a FDDI DAS adapter within the ring is not configured, the data will not be allowed to pass through that FDDI DAS adapter, thus breaking that part of the ring.
Tolerates only a single failure in ring.
If you have two FDDI concentrators, you can create a dual homing topology when the B port of a FDDI DAS adapter is connected to the M port of first FDDI concentrator and the A port of the same FDDI DAS adapter is connected to the M port of the second FDDI concentrator. You can repeat this process for as many M ports as exist on the FDDI concentrators.
Do not connect A and B ports of the same FDDI DAS adapter to the same FDDI concentrator.
As with SAS, the subnets address must be the same in order for FDDI adapters to communicate.
This configuration is AP capable when a domain has two or more FDDI DAS adapters connect to the FDDI concentrators.
Two FDDI rings - active and standby.
Tolerates multiple points of failure.
The FDDI concentrator is now part of the equation and must be smart enough to know the subnet addresses for each of the FDDI DAS adapters connected to the FDDI concentrator.
The following sections describe how the DAS and SAS FDDI adapters can be configured together.
Basically follow the same process as with SAS Point to Point, having the FDDI DAS adapter act like a FDDI SAS adapter by using only one port (A or B). Thus you connect the port of the FDDI SAS adapter to the selected port of the FDDI DAS adapter.
A maximum of two domains can be part of this configuration.
Only two FDDI SAS adapters can communicate with each other. If one fails then the connection is lost.
Does not support Alternate Pathing (AP).
There are two FDDI concentrator configurations available for DAS adapters to communicate with SAS adapters; one uses a ring, the other does not. The following sections describe both.
First, connect the FDDI SAS adapters into the M ports of the FDDI concentrator. Second, determine where in the FDDI DAS ring configuration you want the FDDI concentrator to enter.
In the example below, the FDDI concentrator will be connected between FDDI DAS adapters nf1 and nf2. The A port of FDDI DAS adapter nf1 is connected into the B port of the FDDI concentrator, then the A port of the FDDI concentrator is connected into the B port of the FDDI DAS adapter nf2 to complete the ring.
Ring Configuration before FDDI concentrator
Ring Configuration with FDDI Concentrator
Can communicate with multiple domains and multiple FDDI adapters, both DAS and SAS.
The FDDI concentrator is now part of the equation and must be smart enough to know what the subnet addresses are for each of the FDDI adapters.
Treat the FDDI DAS adapter like a FDDI SAS adapter by connecting either the A or B port into the M port of the concentrator. Then, from another domain, connect the FDDI SAS adapter port into the M port of the same concentrator.
Do not connect both A and B ports of the same DAS adapter to the same concentrator.
The A and B port of a concentrator can also be used to connect multiple concentrators together.
Can communicate with multiple domains and multiple FDDI adapters, Both DAS and SAS.
The FDDI concentrator is now part of the equation and must be smart enough to know the subnet addresses for each of the FDDI adapters connected to the FDDI concentrator.
The following sections describe outstanding issues with SAS and DAS adapters.
This feature is not supported by FDDI DAS or SAS adapters. To bypass a shutdown DAS adapter in a ring without a concentrator, you need an optical bypass (a device that allows you to connect incoming and outgoing fibers). There is no need to bypass a station if you use an FDDI concentrator. The FDDI concentrator provides the bypass.
When running heavy I/O load between domains using Solaris 2.6 software, you may experience broken pipes. Check the value of tcp_rexmit_interval_max :
If the return value is not 60000, use the following command to reset the parameter:
To avoid losing this change between system reboots, you can create a script and put it in /etc/rc2.d directory.
| Platform Notes: SunFDDI Adapter | 816-2350-10 |
|
Copyright © 2002, Sun Microsystems, Inc. All rights reserved.