tiger woods pga tour 07 crack downloadvirtual pc windows 8 download 64 bitwindows server 2003 r2 sp2 32 bit iso downloadsuperantispyware download definitions
Sun Trunking 1.3 Installation and Users Guide
Installing Sun Trunking 1.3 Software
This chapter describes the best way to prepare for and install the Sun Trunking 1.3 software applications using the automated installation script. This chapter includes these sections:
Note - Sun Trunking Utility 1.3 Software for Solaris 10 can be obtained under the Network Connectivity section for the Sun Download Center:
Before installing the Sun Trunking 1.3 software, you will have already installed a number of of the subsequent adapters:
Refer on your product documentation for installation instructions.
Installing the Sun Trunking 1.3 Software
Sun Trunking 1.3 offers an automated installation script. In most cases, you are able to use these procedure and execute not hard to install script. If you could have any problems, see Appendix A for manual installation procedures.
1. At it console, become superuser root.
2. Change to the directory is important where the install script resides:
if that you are installing on the Trunking 1.3 CD-ROM
if you happen to be installing at a download file.
3. Execute the install script:
The install script verifies which the Trunking software programs are current or has to be removed before installation will start, installs the Trunking software programs, verifies the present driver software and patch if required. Nothing will likely be installed until that you are prompted to
4. When prompted from the script, press Return to continue, or q as well as Return to relinquish.
CODE EXAMPLE 2-1 shows the output through the Solaris 10 Sun Trunking installation script.
Sun Trunking 1.3 Utility for sparc Installation.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is governed by license terms.
Install Sun Trunking 1.3 Utility for sparc packages.
Press get back to continue, or Q and then a go back to quit:
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is be subject to license terms.
Please create entries for QFE trunk heads.
Please create entries for GEM trunk heads.
Please create entries for CE trunk heads.
Installation of SUNWtrku was successful.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is susceptible to license terms.
Installation of SUNWtrkm was successful.
CODE EXAMPLE 2-2 shows the output on the Solaris 9 Sun Trunking installation script.
Sun Trunking 1.3 Utility for sparc Installation.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is be subject to license terms.
Install Sun Trunking 1.3 Utility for sparc packages.
Press come back to continue, or Q accompanied by a go back to quit:
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is susceptible to license terms.
Please create entries for QFE trunk heads.
Please create entries for GEM trunk heads.
Please create entries for CE trunk heads.
Installation of SUNWtrku was successful.
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is be subject to license terms.
Installation of SUNWtrkm was successful.
1. Verify the presence with the driver:
If the command responds with packaging information, the packages are installed. If the packages usually are not installed, make reference to Appendix A.
As superuser, change to your directory where the trunking packages reside and take off them:
Note, this script DOES NOT remove Network Ethernet Driver patches.
This mustn't be necessary.
Trunking 1.3 package removal script, please select a possibility:
1 Remove Sun Trunking 1.3 Software
Remove Sun Trunking 1.3 Sofware
Press q followed with the return key to give up, or press some other key then
Removal of SUNWtrku was successful.
Removal of SUNWtrkm was successful.
Sun Trunking 1.3 Installation and Users Guide
Sun Trunking 1.3 Installation and Users Guide
Installing Sun Trunking 1.3 Software
This chapter describes how you can prepare for and install the Sun Trunking 1.3 software programs using the automated installation script. This chapter includes the subsequent sections:
Note - Sun Trunking Utility 1.3 Software for Solaris 10 is obtainable under the Network Connectivity section on the Sun Download Center:
Before installing the Sun Trunking 1.3 software, you will have already installed several of these adapters:
Refer in your product documentation for installation instructions.
Installing the Sun Trunking 1.3 Software
Sun Trunking 1.3 offers automated installation script. In most cases, you may use this procedure and execute set up . script. If you might have any problems, see Appendix A for manual installation procedures.
1. At the device console, become superuser root.
2. Change to the directory is important where the install script resides:
if that you are installing in the Trunking 1.3 CD-ROM
if you happen to be installing at a download file.
3. Execute the install script:
The install script verifies how the Trunking software programs are current or has to be removed before installation start, installs the Trunking software products, verifies the actual driver software and patch when necessary. Nothing are going to be installed until that you are prompted to
4. When prompted from the script, press Return to continue, or q and then Return to give up.
Sun Trunking 1.3 Utility for sparc Installation.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is be subject to license terms.
Install Sun Trunking 1.3 Utility for sparc packages.
Press get back to continue, or Q then a come back to quit:
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is be subject to license terms.
Please create entries for QFE trunk heads.
Please create entries for GEM trunk heads.
Please create entries for CE trunk heads.
Installation of SUNWtrku was successful.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is susceptible to license terms.
Installation of SUNWtrkm was successful.
Sun Trunking 1.3 Utility for sparc Installation.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is at the mercy of license terms.
Install Sun Trunking 1.3 Utility for sparc packages.
Press come back to continue, or Q and then a resume quit:
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is governed by license terms.
Please create entries for QFE trunk heads.
Please create entries for GEM trunk heads.
Please create entries for CE trunk heads.
Installation of SUNWtrku was successful.
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is governed by license terms.
Installation of SUNWtrkm was successful.
1. Verify the presence in the driver:
If the command responds with packaging information, the packages are installed. If the packages usually are not installed, talk about Appendix A.
As superuser, change to your directory where the trunking packages reside and take away them:
Note, this script DOES NOT remove Network Ethernet Driver patches.
This shouldn't be necessary.
Trunking 1.3 package removal script, please select a solution:
Press q followed from the return key to relinquish, or press another key as well as
Removal of SUNWtrku was successful.
Removal of SUNWtrkm was successful.
Sun Trunking 1.3 Installation and Users Guide
Solaris The Solaris Operating System, usually known simply as Solaris, is usually a Unix-based computer introduced by Sun Microsystems. The Solaris OS is owned by Oracle.
Last Activity: 12 November 2007, 10:16 AM EST
Does anyone know where I can download Sun Trunking for Solaris 8? Sun gives this away for Solaris 10 however, you have to pay correctly for Solaris 8? Seems type of bass ackwards in case you ask
Last Activity: 8 January 2008, 6:50 PM EST
Last Activity: 12 December 2015, 3:10 PM EST
Location: Berlin, Germany
Does anyone know where I can download Sun Trunking for Solaris 8? Sun gives this away for Solaris 10 however you have to pay for doing this for Solaris 8? Seems style of bass ackwards in the event you ask
in the event you have the right interfaces it's not necessary suntrunking software with sol10. nic aggregation is build-in in sol10 man dladm. this dont assist older interfaces so trunking cost nothing for sol10 although not for 8 and 9.
Last Activity: 12 November 2007, 10:16 AM EST
Unfortunetely, upgrading is just not an
All times are GMT - 4. The time will be 07:22 PM.
News, reviews, and reference information for users of Oracles Sun hardware and software products
Posted by Bill Bradford on Sep 22, 2005
It appears like Sun Trunking has become a free download for Solaris 10. Previously it turned out an extra-cost add-on towards the Solaris OE.
Sun Trunking 1.3 Installation and Users Guide
Configuring the Sun Trunking 1.3 Software
This chapter describes the best way to edit that will create the Sun Trunking 1.3 configuration files. This chapter includes these sections:
Before rebooting the body, it is possible to edit and build configuration files to define how you will will link the Ethernet network interfaces. To configure these files, you should know these for each Ethernet adapter:
The device instance variety of each Ethernet network interface.
The device instance number for that trunk head.
The trunking policy you need to use: MAC, Round Robin, IP Destination, or IP Source/IP Destination. See Trunking Policies.
Always check to be certain the link mode is scheduled to run full-duplex.
command to substantiate link mode. If the data returned points too your trunking device just isn't running at full-duplex, refer for your networking device product documentation for info on setting the connection mode.
Once you could have installed the trunking software and connected the Ethernet interfaces to some switch that's configured for trunking, you are unable to use that interface to boot in the network.
Each network interface by using an Ethernet adapter includes a corresponding instance number. You must know these devices instance numbers per network interface before you may configure the Sun Trunking software files.
The file provides the physical name, the instance number, and driver name for every device for the system. By searching this file, you are able to find the instance numbers which will be used together with the Sun Trunking 1.3 software.
Note - The following examples are for the GigaSwift Ethernet adapter. If you happen to be using a new adapter, the output will likely be similar. For user input, replace
to the Gigabit Ethernet adapter. The Dual FastEthernet and Dual SCSI adapter uses the
In the last example, instances
are GigaSwift Ethernet adapters. Your information are going to be similar if you might be using some other adapter. TABLE 3-1 lists the network interface number, physical name, and instance number for every GigaSwift Ethernet instance about this example system.
You will have to know the instance numbers in the GigaSwift Ethernet network interfaces to be able to configure the Sun Trunking software.
Note - You cannot trunk an interface that is certainly already plumbed. To display a summary of all plumbed interfaces, execute
1. Before trunking ensure how the links can be obtained:
lo0: flags1000849 UP, LOOPBACK, RUNNING, MULTICAST, IPv4 mtu 8232 index 1
ce0: flags1000843 UP, BROADCAST, RUNNING, MULTICAST, IPv4 mtu 1500 index 942
inet 199.99.10.10 netmask ffffff00 broadcast 199.99.10.255
is already plumbed, and thus, can't be aggregated.
2. Unplumb the interface as follows:
lo0: flags1000849 UP, LOOPBACK, RUNNING, MULTICAST, IPv4 mtu 8232 index 1
3. Setup a corner and plumb the interface:
nettr - setup 10 devicece members0, 1, 2, 3 policy2
ifconfig ce0 plumb 199.99.10.10 up
devices the main element can be a range from 0 to 4096. On
devices the back head represents the aggregation identifier. Therefore on
devices the real key must be a corner head.
Trunk members is usually accessed only through the back head. Since trunking appears on the system to be a single fat pipe, the back head could be the single access point. Other links in a aggregation usually are not plumbed beneath TCP/IP and aren't visible. Networking commands for instance
work only around the head instance.
You can't do a DLPI attach over a non-head member. The following error message was returned for a
can be a member of your trunk. The trunk head for the trunk is
command, for instance, when this happens, these would become the correct usage:
command on all trunk member instances. But in case you run the snoop command over a trunk member instance you will observe duplicated packets. For best results, look on the aggregation traffic utilizing the trunk head instance virtual link and
Networking commands including
work on any member instance.
adapter may be linked as follows.
adapter may be linked as follows.
adapter might be linked in several ways, depending about the needs of your respective network. All four in the network ports may be linked into one trunk, or two network ports might be linked into one trunk. FIGURE 3-3 shows four different common linking possibilities.
The configuration with the Sun Trunking 1.3 software files depends on how we want to organize the Ethernet network. You must also configure the Ethernet switch software to get symmetrical while using way you configured the Sun Trunking 1.3 software. Refer for a Ethernet switch documentation to the switch configuration instructions.
Each Ethernet adapter may be assigned a distinctive Media Access Control MAC address, which represents the 48-bit Ethernet address for the network interface. Each host system also comes with a single global MAC address. For historical reasons, the default MAC address per interface is that on the single global host MAC address instead of the MAC address of each one individual Ethernet adapter. This has to be modified for trunking. You can set the OpenBoot firmware
used for booting the device. To start with all the MAC addresses assigned towards the network interface on the Ethernet adapter, set the NVRAM configuration variable
setenv local-mac-address? true
After seeking the instance numbers with the Ethernet network interfaces, and deciding the method that you want to organize your network, you can start to configure the Sun Trunking 1.3 software.
The main configuration file from the Sun Trunking 1.3 software programs are the
file. You will define each trunk with the addition of information for this file. Before you edit the
file, you must realise how many Ethernet network interfaces you wish to link in to a trunk, the trunking policy along with the
mode of operation. You may also add newbies to an active trunk or delete a current member in the trunk.
Using a text editor, add commands for the
file to define your trunking network.
trunk. Use the next format to put together a trunk:
trunk. Use these format to create a trunk:
In the last command, the main element is the aggregation identifier for
devices. The device represents the adapter type
for GigaSwift Ethernet adapter, or
for Gigabit Ethernet. The member options used to select members of the trunk. The
option either can be the default worth of 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. For the
mode of operation. It might be Active Aa, Passive P p, or Off O o. For the
option, specify a short0 or long1
Note - The following examples make use of the instance numbers present in TABLE 3-1. The instance numbers on the body will be different. See Determining Instance Numbers for more info.
If you wish to use the MAC trunking policy and 2 links for any trunk, add the next line for the
nettr - setup 10 devicece members0, 1 policy1 lacpp ptimer1
For two trunks, containing two network interfaces each while using the MAC policy, you'd probably add these lines:
nettr - setup 10 devicece members0, 1 policy1 lacpp ptimer1
nettr - setup 20 devicece members2, 3 policy1 lacpp ptimer1
Note - The command syntax of Sun Trunking 1.3 is fully works with Trunking 1.2.1. Existing
files don't require any modifications.
To verify whether you've got set up the trunking configuration file correctly, run the
command. You should see information similar to the subsequent:
command to determine the configuration.
Before you need to use these trunked Ethernet network interfaces, you will need to create an
file, where corresponds on the instance number used as the back head.
For example, should you had two trunks using two network interfaces each, you should have to generate two files containing the host name with the trunk as seen by network. The extensions of such files might need to correspond with a corner head interface numbers on the trunks.
file must contain the right host name for that trunk.
The host name must be different from any host name of some other interface, by way of example:
cannot share a similar host name.
Using the example in TABLE 3-3, these example shows the three
Note - Make sure you configure the switch software to become symmetrical with all the Sun Trunking 1.3 software. Refer on your Ethernet switch documentation for instructions.
command, where ipaddress corresponds on the system IP address.
129.144.10.57 proboscis loghost
129.144.11.83 proboscis-11
Note - Make sure you configure the switch software to become symmetrical together with the Sun Trunking 1.3 software. Refer on your Ethernet switch documentation for instructions.
you will likely need to reboot the body to make these trunked networks active. If you did use the earlier
instructions, you may ignore it.
setenv local-mac-address? true
command to list the addressing information for each and every interface about the system.
lo0: flags849 UP, LOOPBACK, RUNNING, MULTICAST mtu 8232
hme0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 129.144.131.27 netmask ffffff00 broadcast 129.144.131.255
ce0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 199.100.2.10 netmask ffffff00 broadcast 199.100.2.255
Even though a trunk could possibly be composed of two linked GigaSwift Ethernet network interfaces, the
command. This command prints out a list with the trunked
command will even show the policy of every trunk around the system, and also listing the initial MAC address of every interface.
device command to watch the network statistics of every interface around the system.
This command are listed each interface as well as the network performance statistics, on the specified trunk. See Configuring Trunking while using nettr Utility to learn more.
You may also monitor the network statistics of any trunk at regular intervals. The full usage from the command is
key intervalsec, with sec being the amount of seconds between monitoring the trunks interfaces. In the example below, a corner is monitored once every second.
command to watch the network statistics. Refer towards the
pages to find out more.
To permanently disable the trunking interface, comment out the
file. You should reconfigure the
files should you want to makes use of the Ethernet network interfaces separately. Refer towards the product documentation for additional information.
utility to configure trunking. Use
The key may be the aggregation identifier and could be any number you end up picking. It will not have to get tied to some member instance. The device represents the adapter type
The member options used to select members of your trunk. The
option may be the default valuation on 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. For the
mode of operation. It might be ActiveAa, PassiveP p, or OffO o. For the
option, specify a short0 or long1
In the earlier command, the top instance could be the instance number with the first linked network interface on the trunk. The device represents the adapter type
for GigabitEthernet adapter. The member choice is used to select members of your trunk. The
option may be the default valuation on 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. If you wish to use the MAC trunking policy and a couple of links for any trunk, execute the subsequent line:
nettr - setup 0 devicege members0, 1 policy1
command to print the addressing information for each and every interface about the system.
lo0: flags849 UP, LOOPBACK, RUNNING, MULTICAST mtu 8232
hme0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 129.144.131.27 netmask ffffff00 broadcast 129.144.131.255
ce0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 199.100.2.10 netmask ffffff00 broadcast 199.100.2.255
Even though a trunk may be composed of two linked GigaSwift Ethernet network interfaces, the
In the first sort example, the
interface could be the key for just a two-network interface trunk, composed on the
command also shows the policy of every trunk about the system and lists the initial MAC address of the interface.
device command to observe the network statistics of each and every interface within the system.
command are listed each interface plus the network performance statistics, summarized in TABLE 3-4, on the specified trunk.
The amount of Ethernet packets inputted to the interface.
The amount of errors that occurred while inputting these Ethernet packages.
The variety of Ethernet packets outputted throughout the interface.
The variety of errors that occurred while outputting these Ethernet packages.
The amount of collisions detected for the interface.
The variety of cyclic redundancy check CRC errors detected for the interface.
The percent of Ethernet packets input towards the interface.
The percent of Ethernet packets output from the interface.
You may also monitor the network statistics of the trunk at regular intervals. For a Sun GigaSwift Ethernet driver, the entire usage from the command is
key devicece intervalsec, with sec being the amount of seconds between monitoring the trunks interfaces. In the example below, the back is monitored once every second.
To monitor the network statistics of an trunk for any Sun Gigabit Ethernet driver or possibly a Sun Quad FastEthernet driver, the whole usage in the command is
trunkhead devicegeqfe intervalsec, with sec being how many seconds between monitoring the trunks interfaces. In the example below, the back is monitored once every second.
command to check the network statistics. Refer for the
pages to find out more.
If you'll want to add a new member on the trunk, use
With the fellow member added to your trunk, the output through the
If you must remove a member from your trunk, use
on the trunk. The output in the
If you'll want to disable a trunk, utilize the
key command, with key being the spine identifier.
automatically unplumbs IPv4 and IPv6 stacks. If any application for example VLAN are plumbed, be sure you manually unplumb the applying.
The four supported trunking policies utilised in the Sun Trunking 1.3 software are MAC, Round Robin, IP Destination, and IP SourceDestination. With these policies, when a link fails, the traffic failsover for the next available link. The policies are defined below.
Is the default policy used through the Sun Trunking 1.3 software. MAC would be the preferred policy to make use of with switches. Most trunking-capable switches require while using MAC-hashing policy, but look at switch documentation.
Uses the final three bits on the MAC address of both source and destination. For two ports, the MAC address in the source and destination are first XORed: Result 00, 01, which selects the port.
Favors a substantial population of clients. For example, this makes certain that 50 percent on the client connections goes through 1 of 2 ports inside a two-port trunk.
Is essental to most trunking-capable switches.
Note - Do not use MAC-hashing to get in touch two servers consecutive.
Is the most well-liked policy which has a Back to Back connection, used between your output of any transmitting device, as well as the input connected with an associated receiving device.
Uses each network interface in the trunk consequently, to be a method of distributing packets on the assigned amount of trunking interfaces.
May affect performance considering that the temporal ordering of packets isn't observed.
Uses a few bytes in the IP Destination address to discover the transmission path.
Is preferred policy to use in case a trunking interface host has one IP source address, and it's also necessary to communicate to multiple IP clients connected for the same router.
Connects the original source server to your destination, based on the place that the connection originated or terminated.
Uses several bytes from the source and destination IP addresses to discover the transmission path.
The primary use on the IP Source/IP Destination Address policy occurs where you make use of the IP virtual address feature to supply multiple IP addresses to your single physical interface. For example, you've got a cluster of servers providing network services, through which each service is associated having a virtual IP address over the given interface. If a service of an interface fails, the virtual IP address migrates to some physical interface on another machine inside cluster. In such an arrangement, the IP Source Address/IP Destination Address policy provides you with a greater probability of using more, different links within the back than would the IP Destination Address policy.
command allows you to determine over which link a certain packet will travel. The following section describes hashing in greater detail.
Note - Sun Trunking 1.3, as with any server trunking software, load balances the outgoing traffic, not the incoming packets. Trunking 1.3 software relies on the hyperlink partner switch or server to load balance the incoming packets.
Note - Trunking interfaces has to be set up previous to using hashing features. If, one example is, one trunk, the url to transmit is 0, with the subsequent hash command input, the protection IP Source and Destination Address would read as follows:
etc/opt/SUNWconn/bin/nettr - hash 0 devicece ip199.100.1.29/199.100.1.3
command lets you determine over which link a particular packet will travel. For example, should you use the Destination IP Address policy, you may supply an IP address with a
command to find out over which link a packet using the specified IP address will travel.
Sun Trunking 1.3 operates as being a virtual network adapter that is certainly visible to your system throughout the head or key instance. Applications work transparently that they are using a single link, yet go through the benefits of increased bandwidth and automatic failover. On applications that deal using a physical NIC, like DR, you need to simply unaggregate a corner prior to performing those functions, then reaggregate a corner when you're finished.
Sun Trunking 1.3 works inside static mode with 802.3ad switches. For a link for being part associated with an aggregation it should be running at full-duplex and in the same speed. The endpoints in the links need to be terminated with the same switch or system.
Sun Trunking 1.3 also supports dynamic mode providing a completely compliant IEEE 802.3ad implementation. This includes the LACP protocol and associated Marker Responder. For more information about the LACP protocol, see Appendix B.
IP Multipathing IPMP works transparently with Sun Trunking 1.3. Configure two aggregations two trunk-heads and group those two aggregations into one IPMP group.
Note - IPMP failover might not happen if one with the links in a aggregation fails because Sun Trunking 1.3 software will failover for the next available link inside the aggregation.
Dynamic Reconfiguration DR works transparently with Sun Trunking 1.3. Here is how it functions:
1. Unconfigure the aggregation:
2. Unconfigure the Ethernet adapter:
3. Change the Ethernet adapter.
4. Configure the Ethernet adapter:
5. Reconfigure the aggregation:
Sun Trunking 1.3 works transparently with 802.1q, but it is accessible only on Sun GigaSwift Ethernet adapters. For more info on configuring VLANs, reference Configuring VLANs, inside Sun GigaSwift Ethernet Adapter Installation and Users Guide, part number 816-1702-11.
When configuring VLANs with an aggregation trunk, make sure how the link partner or switch has VLAN enabled on every one of the ports belonging this aggregation.
The SunVTS software executes multiple diagnostic hardware tests and it is used to substantiate the configuration and functionality on most hardware controllers and devices.
Since trunking aggregates many network adapters behind just one head instance, these tests may well not provide the data intended. Unaggregate all trunking interfaces to become tested before you run SunVTS.
option by using an aggregated link, utilize the Round Robin policy option and then utilize
option to make sure test visitors flowing over everything interfaces inside the aggregation.
diagnostic, you should have the SunVTS software installed on the body. Refer to your Solaris Sun Hardware Platform Guide, which has been shipped using the Solaris Supplement CD, for instructions on the best way to install the SunVTS software.
when links are aggregated. This test is not going to make sense on aggregated links as the packets are distributed to multiple links based for the load balancing policy.
Refer to your Solaris operating environment user documentation to learn more.
For maximum performance, network traffic needs to be evenly distributed along the aggregation. Use
command to make sure that packets are evenly distributed. See Load Balancing Methods to get a full description of load balancing policies.
running at 1000Mbps, install each adapter in numerous PCI or Sbus slot. Note that some slots utilize the identical PCI bus. Refer in your system documentation to learn more.
For optimum performance, use 2 MHz of CPU speed for each and every 1 Mbps of NIC bandwidth capability. Any variety of aggregations is supported with this guideline.
To progress throughput above the TCP/IP stack, execute the subsequent at the command line:
The default behavior for Sun Trunking 1.3 isn't going to expose trunk members to upper layers like IP. However, for performance sake, you may need to plumb multiple IP streams on member instances with some other subnets for the trunk members to derive multiple connections to IP. You can accomplish that by setting the
2. Repeat for everyone member instances within the back
You can configure the back now and plumb using one or all member instances.
device drivers. When enabling this feature, remember that certain Layer 3 protocols like IPMP or Routing would possibly not work properly. It is best employed in local LAN setup. This feature is disabled for VLAN streams. So, VLAN streams is only able to be plumbed for the key instance.
nettr - setup 2 devicece members2, 3
ifconfig ce123003 plumb 199.99.23.102 up
ifconfig ce123002 plumb 199.99.23.102 up
If you might have problems with Sun Trunking 1.3, use the subsequent commands to accumulate information that might help resolve the difficulties.
command to evaluate whether network packets are showing in each trunk instance. In the next example, 1 represents a corner head instance being monitored.
If you make use of MAC policy, you might not see packets on certain interfaces, as shown within the example. This occurs because a couple of clients might have MAC addresses while using last two bits identical. See Trunking Policies for additional information.
command to capture and inspect network packets. This command allows you to troubleshoot network problems on the packet level, allowing examination in the contents of an packet. The following shows example output for ce0.
199.100.1.10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391268307 Len1460 Win8760
199.100.1.10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391269767 Len1460 Win8760
199.100.1.10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391271227 Len1460 Win8760
In it, if there are packets created for hostname
but none showed inside the output on the
command, you'll know a challenge existed. In that case, you should check your host file, network connection, or perhaps your ethernet switch setup. Refer on the
man page to find out more.
Because in the trunk head concept as virtual link in Sun Trunking 1.3, you would possibly expect the
command around the trunk head instance to evaluate the aggregation traffic. While Sun offers a feature in
drivers that lets you snoop the spine member instance to evaluate the running traffic on that instance, while using
command on trunk member instance can present confusing results.
command around the trunk member instance. For example, if
you will observe some duplicated packets appear for the
output for both instances. That is because the many packets to the present aggregation link will probably be seen through the
which appears to be a fat pipe presenting this aggregation link, and for the same time, the packets physical with all the trunk member port may also be seen because of the
1M focus on any member instance.
command to substantiate your trunking configuration.
Make sure the Ethernet switch software along with the Sun Trunking 1.3 software are configured symmetrically. For example, both Sun Trunking and also the switch really should be configured using the same amount of links per trunk.
Once you might have configured Sun Trunking 1.3 software, you'll want to re-configure your plunge to match the trunking configuration.
See your console for error messages when configuring a Sun GigaSwift Ethernet adapter or maybe a Sun Dual FastEthernet and Dual SCSI/P adapter for trunking. It is best to aggregate and unaggregate links about the console because error messages through the console and
Note - If you might be configuring a Sun Gigabit Ethernet adapter or even a Sun Quad FastEthernet adapter, error messages are returned by
but might not appear inside the console.
If you are trying to configure a trunk which has already been configured, you will see these error message from
nettr - setup 0 devicece members0, 1, 2
nettr: ioctl failed: Invalid argument
Jul 8 15:36:55 proboscis trslm: NOTICE: trunk0: Aggregation exists.
If you are attempting to configure a trunk member that is certainly part of another aggregation, you will see the subsequent message from
nettr - setup 4 devicece members0, 4
nettr: ioctl failed: Invalid argument
If you attempt to configure a non-existent member as part connected with an aggregation,
nettr - setup 7 devicece members7, 8
trslm: NOTICE: trunk link ce7: DLERRORACK for DLATTACHREQ11,
If the policy is determined out of range, you will note an error message and trunk will probably be setup with default policy1MACSD.
nettr - setup 1 devicece members0, 1, 2, 3 policy
within supported range1 - 4, Using default Policy 1
If you plumb trunk member, you will observe following message. The following example shows, a shot to plumb ce2, that is already aggregated and is really a trunk member. Plumbing is allowed only about the trunk-head.
After aggregating site, be sure how the head instance is plumbed using
operation. You must unplumb all VLANs and applications running about the head instance manually.
in SunVTS fails when site are aggregated. If you would like to run
while on an interface, unconfigure trunking on that interface.
If you can't resolve problems and you've a SunService contract, send the info gathered out there commands for your SunService representative. You must have these information ready:
Product name and release number Sun Trunking 1.3
Sun Trunking 1.3 Installation and Users Guide
Sun Trunking 1.3 Installation and Users Guide
This chapter describes the way to edit and make the Sun Trunking 1.3 configuration files. This chapter includes this sections:
Before rebooting one's body, you'll be able to edit and make configuration files to define how you will will link the Ethernet network interfaces. To configure these files, you have to know the subsequent for each Ethernet adapter:
The device instance variety of each Ethernet network interface.
The device instance number to the trunk head.
The trunking policy you need to use: MAC, Round Robin, IP Destination, or IP Source/IP Destination. See Trunking Policies.
Always check to be certain the link mode is defined to run full-duplex.
command to ensure link mode. If the info returned shows that your trunking device is just not running at full-duplex, refer on your networking device product documentation for info on setting the connection mode.
Once you could have installed the trunking software and connected the Ethernet interfaces with a switch that may be configured for trunking, you are unable to use that interface to boot on the network.
Each network interface by using an Ethernet adapter includes a corresponding instance number. You must know it instance numbers per network interface before it is possible to configure the Sun Trunking software files.
The file has the physical name, the instance number, and driver name per device about the system. By searching this file, it is possible to find the instance numbers which will be used while using Sun Trunking 1.3 software.
Note - The following examples are for any GigaSwift Ethernet adapter. If you might be using a new adapter, the output will probably be similar. For user input, replace
for your Gigabit Ethernet adapter. The Dual FastEthernet and Dual SCSI adapter uses the
In the earlier example, instances
are GigaSwift Ethernet adapters. Your information will likely be similar if that you are using some other adapter. TABLE 3-1 lists the network interface number, physical name, and instance number for each and every GigaSwift Ethernet instance with this example system.
You will have to know the instance numbers in the GigaSwift Ethernet network interfaces as a way to configure the Sun Trunking software.
Note - You cannot trunk an interface that is certainly already plumbed. To display an index of all plumbed interfaces, execute
1. Before trunking ensure the links can be obtained:
lo0: flags1000849 UP, LOOPBACK, RUNNING, MULTICAST, IPv4 mtu 8232 index 1
ce0: flags1000843 UP, BROADCAST, RUNNING, MULTICAST, IPv4 mtu 1500 index 942
is already plumbed, and so, are not aggregated.
2. Unplumb the interface as follows:
lo0: flags1000849 UP, LOOPBACK, RUNNING, MULTICAST, IPv4 mtu 8232 index 1
3. Setup a corner and plumb the interface:
nettr - setup 10 devicece members0, 1, 2, 3 policy2
devices the real key can be numerous from 0 to 4096. On
devices the spine head represents the aggregation identifier. Therefore on
devices the real key must be the back head.
Trunk members is usually accessed only through a corner head. Since trunking appears to your system being a single fat pipe, the back head may be the single access point. Other links inside an aggregation will not be plumbed beneath TCP/IP and usually are not visible. Networking commands including
work only within the head instance.
You can't do a DLPI attach with a non-head member. The following error message was returned for a
is usually a member of an trunk. The trunk head for the trunk is
command, one example is, when this happens, the next would become the correct usage:
command on all trunk member instances. But should you run the snoop command on the trunk member instance you will note duplicated packets. For best results, look for the aggregation traffic while using the trunk head instance virtual link and
Networking commands for example
work on any member instance.
adapter is usually linked as follows.
adapter may be linked as follows.
adapter might be linked in many ways, depending for the needs of the network. All four in the network ports is usually linked into one trunk, or two network ports could be linked into one trunk. FIGURE 3-3 shows four different common linking possibilities.
The configuration in the Sun Trunking 1.3 software files depends on how you will want to organize the Ethernet network. You must also configure the Ethernet switch software being symmetrical while using way you configured the Sun Trunking 1.3 software. Refer for your Ethernet switch documentation for your switch configuration instructions.
Each Ethernet adapter is assigned a distinctive Media Access Control MAC address, which represents the 48-bit Ethernet address to the network interface. Each host system also comes with a single global MAC address. For historical reasons, the default MAC address per interface is that in the single global host MAC address instead of the MAC address of each and every individual Ethernet adapter. This should be modified for trunking. You can set the OpenBoot firmware
used for booting the computer. To start while using MAC addresses assigned on the network interface on the Ethernet adapter, set the NVRAM configuration variable
setenv local-mac-address? true
After choosing the instance numbers on the Ethernet network interfaces, and deciding the method that you want to organize your network, you can start to configure the Sun Trunking 1.3 software.
This section describes the minimum list of instructions to configure trunking. For more details, see Configuring Trunking while using nettr Utility.
The main configuration file with the Sun Trunking 1.3 software program is the
file. You will define each trunk with the addition of information for this file. Before you edit the
file, you must realise how many Ethernet network interfaces you intend to link to a trunk, the trunking policy along with the
mode of operation. You may add newbies to an active trunk or delete a preexisting member on the trunk.
Using a text editor, add commands towards the
file to define your trunking network.
trunk. Use the subsequent format to create a trunk:
trunk. Use this format to create a trunk:
In the earlier command, the real key is the aggregation identifier for
devices. The device represents the adapter type
for GigaSwift Ethernet adapter, or
for Gigabit Ethernet. The member choices used to select members of your trunk. The
option may either be the default price of 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. For the
mode of operation. It could be Active Aa, Passive P p, or Off O o. For the
option, specify a short0 or long1
Note - The following examples utilize the instance numbers seen in TABLE 3-1. The instance numbers on your whole body will be different. See Determining Instance Numbers for more info.
If you need to use the MAC trunking policy and a couple links for just a trunk, add the subsequent line towards the
nettr - setup 10 devicece members0, 1 policy1 lacpp ptimer1
For two trunks, containing two network interfaces each utilizing the MAC policy, you should add these lines:
nettr - setup 10 devicece members0, 1 policy1 lacpp ptimer1
nettr - setup 20 devicece members2, 3 policy1 lacpp ptimer1
Note - The command syntax of Sun Trunking 1.3 is fully that will work with Trunking 1.2.1. Existing
files don't require any modifications.
To verify whether you could have set up the trunking configuration file correctly, run the
command. You should see information similar to the subsequent:
command to determine the configuration.
Before you need to use these trunked Ethernet network interfaces, you need to create an
file, where corresponds for the instance number used as the back head.
For example, in the event you had two trunks using two network interfaces each, you'd probably have to generate two files containing the host name on the trunk as seen by network. The extensions these files would need to correspond with a corner head interface numbers on the trunks.
file must contain a suitable host name for that trunk.
The host name needs to be different from any host name of any interface, for instance:
cannot share the identical host name.
Using the example in TABLE 3-3, these example shows the three
Note - Make sure you configure the switch software for being symmetrical together with the Sun Trunking 1.3 software. Refer for a Ethernet switch documentation for instructions.
command, where ipaddress corresponds towards the system IP address.
129.144.11.83 proboscis-11
Note - Make sure you configure the switch software for being symmetrical together with the Sun Trunking 1.3 software. Refer for your Ethernet switch documentation for instructions.
you will likely need to reboot your body to make these trunked networks active. If you did use the earlier
instructions, you'll be able to ignore this.
setenv local-mac-address? true
command to use the addressing information for each and every interface within the system.
lo0: flags849 UP, LOOPBACK, RUNNING, MULTICAST mtu 8232
hme0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 129.144.131.27 netmask ffffff00 broadcast 129.144.131.255
ce0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 199.100.2. 10 netmask ffffff00 broadcast 199.100.2.255
Even though a trunk could possibly be composed of two linked GigaSwift Ethernet network interfaces, the
command. This command prints out a list from the trunked
command will likely show the policy of every trunk within the system, along with listing an original MAC address of every interface.
device command to watch the network statistics of each one interface within the system.
This command are listed each interface plus the network performance statistics, in the specified trunk. See Configuring Trunking while using nettr Utility to learn more.
You could also monitor the network statistics of your trunk at regular intervals. The full usage with the command is
key intervalsec, with sec being the amount of seconds between monitoring the trunks interfaces. In the example below, the spine is monitored once every second.
command to check the network statistics. Refer towards the
pages for more info.
To permanently disable the trunking interface, comment out the
file. You will likely need to reconfigure the
files in the event you want to utilize Ethernet network interfaces separately. Refer towards the product documentation to learn more.
utility to configure trunking. Use
The key will be the aggregation identifier and could be any number you decide on. It isn't going to have being tied to your member instance. The device represents the adapter type
The member choices are used to select members of the trunk. The
option may either be the default valuation on 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. For the
mode of operation. It is usually ActiveAa, PassiveP p, or OffO o. For the
option, specify a short0 or long1
In the prior command, your head instance will be the instance number with the first linked network interface on the trunk. The device represents the adapter type
for GigabitEthernet adapter. The member choices are used to select members of your trunk. The
option may either be the default worth of 1 for MAC or 2 for round robin, 3 for IP Destination, or 4 for IP Source/IP Destination. If you intend to use the MAC trunking policy and 2 links for the trunk, execute the next line:
nettr - setup 0 devicege members0, 1 policy1
command to print the addressing information for every interface within the system.
lo0: flags849 UP, LOOPBACK, RUNNING, MULTICAST mtu 8232
hme0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 129.144.131.27 netmask ffffff00 broadcast 129.144.131.255
ce0: flags863 UP, BROADCAST, NOTRAILERS, RUNNING, MULTICAST mtu 1500
inet 199.100.2. 10 netmask ffffff00 broadcast 199.100.2.255
Even though a trunk is usually composed of two linked GigaSwift Ethernet network interfaces, the
In the earlier example, the
interface could be the key for the two-network interface trunk, composed on the
command also shows the policy of the trunk around the system and lists an original MAC address of each one interface.
device command to observe the network statistics of every interface about the system.
command are listed each interface plus the network performance statistics, summarized in TABLE 3-4, on the specified trunk.
The variety of Ethernet packets inputted into your interface.
The variety of errors that occurred while inputting these Ethernet packages.
The quantity of Ethernet packets outputted throughout the interface.
The variety of errors that occurred while outputting these Ethernet packages.
The volume of collisions detected within the interface.
The amount of cyclic redundancy check CRC errors detected within the interface.
The percent of Ethernet packets input for the interface.
The percent of Ethernet packets output with the interface.
You may also monitor the network statistics of your trunk at regular intervals. For a Sun GigaSwift Ethernet driver, the total usage with the command is
key devicece intervalsec, with sec being the volume of seconds between monitoring the trunks interfaces. In the example below, a corner is monitored once every second.
To monitor the network statistics of any trunk for just a Sun Gigabit Ethernet driver or perhaps a Sun Quad FastEthernet driver, the complete usage on the command is
trunkhead devicegeqfe intervalsec, with sec being the amount of seconds between monitoring the trunks interfaces. In the example below, a corner is monitored once every second.
command to evaluate the network statistics. Refer on the
pages for additional information.
If you should add a new member on the trunk, use
With the participant added for the trunk, the output in the
If you have to remove a member through the trunk, use
on the trunk. The output through the
If you have to disable a trunk, make use of the
key command, with key being the back identifier.
automatically unplumbs IPv4 and IPv6 stacks. If every other application for example VLAN are plumbed, don't forget to manually unplumb the appliance.
The four supported trunking policies found in the Sun Trunking 1.3 software are MAC, Round Robin, IP Destination, and IP SourceDestination. With these policies, if the link fails, the traffic failsover towards the next available link. The policies are defined below.
Is the default policy used from the Sun Trunking 1.3 software. MAC will be the preferred policy to make use of with switches. Most trunking - capable switches require while using the MAC-hashing policy, but look at switch documentation.
Uses the final three bits from the MAC address of the two source and destination. For two ports, the MAC address on the source and destination are first XORed: Result 00, 01, which selects the port.
Favors a sizable population of clients. For example, this helps to ensure that 50 percent on the client connections should go through a couple of ports within a two-port trunk.
Is necessary for most trunking - capable switches.
Note - Do not use MAC-hashing allowing you to connect two servers continual.
Is the most well-liked policy that has a Back to Back connection, used between output of an transmitting device, as well as the input associated with an associated receiving device.
Uses each network interface with the trunk consequently, being a method of distributing packets above the assigned quantity of trunking interfaces.
May change performance because the temporal ordering of packets is just not observed.
Uses several bytes with the IP Destination address to look for the transmission path.
Is preferred policy to use in case a trunking interface host has one IP source address, and it's necessary to communicate to multiple IP clients connected to your same router.
Connects the origin server towards the destination, based on the place that the connection originated or terminated.
Uses a few bytes on the source and destination IP addresses to discover the transmission path.
The primary use with the IP Source/IP Destination Address policy occurs where you utilize IP virtual address feature to supply multiple IP addresses to some single physical interface. For example, it's likely you have a cluster of servers providing network services, through which each service is associated having a virtual IP address more than a given interface. If a service connected with an interface fails, the virtual IP address migrates to some physical interface on some other machine from the cluster. In such an arrangement, the IP Source Address/IP Destination Address policy will give you a greater potential for using more, different links within a corner than would the IP Destination Address policy.
command means that you can determine over which link confirmed packet will travel. The following section describes hashing in greater detail.
Note - Sun Trunking 1.3, like all server trunking software, load balances the outgoing traffic, not the incoming packets. Trunking 1.3 software relies on the hyperlink partner switch or server to load balance the incoming packets.
Note - Trunking interfaces should be set up before using hashing features. If, as an example, during one trunk, the url to transmit is 0, with these hash command input, a policy IP Source and Destination Address would read as follows:
etc/opt/SUNWconn/bin/nettr - hash 0 devicece ip199.100.1.29/199.100.1.3
command allows you to determine over which link confirmed packet will travel. For example, when you use the Destination IP Address policy, you may supply an IP address with a
command to view over which link a packet while using specified IP address will travel.
Sun Trunking 1.3 operates like a virtual network adapter that may be visible on the system from the head or key instance. Applications is fine transparently like they are on the single link, yet see the benefits of increased bandwidth and automatic failover. On applications that deal using a physical NIC, like DR, you need to simply unaggregate the back prior to performing those functions, then reaggregate the back when you happen to be finished.
Sun Trunking 1.3 works inside static mode with 802.3ad switches. For a link to get part of your aggregation it need to be running at full-duplex and in the same speed. The endpoints on the links need to be terminated in the same switch or system.
Sun Trunking 1.3 also supports dynamic mode providing a completely compliant IEEE 802.3ad implementation. This includes the LACP protocol and associated Marker Responder. For more information about the LACP protocol, see Appendix B.
IP Multipathing IPMP works transparently with Sun Trunking 1.3. Configure two aggregations two trunk-heads and group both of these aggregations into one IPMP group.
Note - IPMP failover might not exactly happen if one in the links in the aggregation fails because Sun Trunking 1.3 software will failover towards the next available link inside the aggregation.
Dynamic Reconfiguration DR works transparently with Sun Trunking 1.3. Here is how it truly does work:
1. Unconfigure the aggregation:
2. Unconfigure the Ethernet adapter:
3. Change the Ethernet adapter.
4. Configure the Ethernet adapter:
5. Reconfigure the aggregation:
Sun Trunking 1.3 works transparently with 802.1q, but it is accessible only on Sun GigaSwift Ethernet adapters. For more home elevators configuring VLANs, reference Configuring VLANs, inside Sun GigaSwift Ethernet Adapter Installation and Users Guide, part number 816-1702-11.
When configuring VLANs by using an aggregation trunk, make sure that this link partner or switch has VLAN enabled on every one of the ports belonging this aggregation.
The SunVTS software executes multiple diagnostic hardware tests and is also used to ensure the configuration and functionality of the majority of hardware controllers and devices.
Since trunking aggregates many network adapters behind just one head instance, these tests might not provide the knowledge intended. Unaggregate all trunking interfaces to get tested before you run SunVTS.
option upon an aggregated link, utilize the Round Robin policy option and then utilize
option to make certain that test readers are flowing overall interfaces inside the aggregation.
diagnostic, you will need to have the SunVTS software installed on your whole body. Refer towards the Solaris Sun Hardware Platform Guide, which had been shipped together with the Solaris Supplement CD, for instructions on the way to install the SunVTS software.
when links are aggregated. This test won't make sense on aggregated links considering that the packets are distributed to multiple links based about the load balancing policy.
Refer to your Solaris operating environment user documentation for additional information.
For maximum performance, network traffic must be evenly distributed through the aggregation. Use
command to make certain that packets are increasingly being evenly distributed. See Load Balancing Methods for any full description of load balancing policies.
running at 1000Mbps, install each adapter in various PCI or Sbus slot. Note that some slots utilize exactly the same PCI bus. Refer for your system documentation for more info.
For optimum performance, use 2 MHz of CPU speed for any 1 Mbps of NIC bandwidth capability. Any volume of aggregations is supported with this guideline.
To advance throughput in the TCP/IP stack, execute the next at the command line:
The default behavior for Sun Trunking 1.3 doesn't expose trunk members to upper layers like IP. However, for performance sake, you may would like to plumb multiple IP streams on member instances with various subnets within the trunk members to derive multiple connections to IP. You can do this by setting the
2. Repeat for those member instances within a corner
You can configure a corner now and plumb on a single or all member instances.
device drivers. When enabling this feature, bear in mind that certain Layer 3 protocols like IPMP or Routing may well not work properly. It is best found in local LAN setup. This feature is disabled for VLAN streams. So, VLAN streams could only be plumbed around the key instance.
nettr - setup 2 devicece members2, 3
ifconfig ce123003 plumb 199.99.23.102 up
ifconfig ce123002 plumb 199.99.23.102 up
If you've got problems with Sun Trunking 1.3, use these commands to assemble information that might help resolve the issues.
command to confirm whether network packets are showing in each trunk instance. In this example, 1 represents the back head instance being monitored.
If you employ MAC policy, you may well not see packets on certain interfaces, as shown inside the example. This occurs because a couple of clients could have MAC addresses with all the last two bits identical. See Trunking Policies to find out more.
command to capture and inspect network packets. This command means that you can troubleshoot network problems for the packet level, allowing examination from the contents of your packet. The following shows example output for ce0.
199.100.1. 10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391268307 Len1460 Win8760
199.100.1. 10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391269767 Len1460 Win8760
199.100.1. 10 - 199.100.1.11 TCP D5100 S59412 Ack2577009842 Seq391271227 Len1460 Win8760
In it, if there have been packets intended for hostname
but none showed from the output through the
command, you'd know problems existed. In that case, you'd probably check your host file, network connection, or maybe your ethernet switch setup. Refer for the
man page for more info.
Because in the trunk head concept as virtual link in Sun Trunking 1.3, you could possibly expect the
command about the trunk head instance to watch the aggregation traffic. While Sun offers a feature in
drivers that lets you snoop the back member instance to evaluate the running traffic on that instance, while using the
command on trunk member instance can present confusing results.
command for the trunk member instance. For example, if
you will notice some duplicated packets appear about the
output for both instances. That is because every one of the packets to the present aggregation link will likely be seen from the
which appears as being a fat pipe presenting this aggregation link, and with the same time, the packets physical while using the trunk member port will even be seen because of the
1M work with any member instance.
command to ensure your trunking configuration.
Make sure the Ethernet switch software plus the Sun Trunking 1.3 software are configured symmetrically. For example, both Sun Trunking plus the switch ought to be configured with all the same volume of links per trunk.
Once you could have configured Sun Trunking 1.3 software, make sure you re-configure your change to match the trunking configuration.
See your console for error messages when configuring a Sun GigaSwift Ethernet adapter or even a Sun Dual FastEthernet and Dual SCSI/P adapter for trunking. It is best to aggregate and unaggregate links about the console because error messages on the console and
Note - If you happen to be configuring a Sun Gigabit Ethernet adapter or possibly a Sun Quad FastEthernet adapter, error messages are returned by
but might not appear inside the console.
If you attempt to configure a trunk that's already been configured, you will see the subsequent error message from
nettr - setup 0 devicece members0, 1, 2
nettr: ioctl failed: Invalid argument
Jul 8 15:36:55 proboscis trslm: NOTICE: trunk0: Aggregation exists.
If you attempt to configure a trunk member which is part of another aggregation, you will see the subsequent message from
nettr - setup 4 devicece members0, 4
nettr: ioctl failed: Invalid argument
If you are attempting to configure a non-existent member as part associated with an aggregation,
nettr - setup 7 devicece members7, 8
trslm: NOTICE: trunk link ce7: DLERRORACK for DLATTACHREQ11,
If the policy is determined out of range, you will notice an error message and trunk are going to be setup with default policy1MACSD.
nettr - setup 1 devicece members0, 1, 2, 3 policy
within supported range1 - 4, Using default Policy 1
If you plumb trunk member, you'll see following message. The following example shows, an endeavor to plumb ce2, and that is already aggregated and is usually a trunk member. Plumbing is allowed only around the trunk-head.
After aggregating all the backlinks, be sure how the head instance is plumbed using
operation. You must unplumb all the VLANs and applications running about the head instance manually.
in SunVTS fails when the hyperlinks are aggregated. If you need to run
with an interface, unconfigure trunking on that interface.
If you can not resolve the down sides and you've got a SunService contract, send the knowledge gathered out there commands for your SunService representative. You must have the subsequent information ready:
Product name and release number Sun Trunking 1.3
Sun Trunking 1.3 Installation and Users Guide
The very first thing you should do before even begin their day on trunking on the Solaris 10 machine is to create sure they have latest patches.
Next, check what style of Ethernet driver do you might have. There are several ways you'll be able to find out. Here is the best way:
Look for your first word for every line. If you see any of the next driver types, then you may use Nemo drivers: bge, e1000g, xge, nge, rge, ixgb
Lets say that you've got Nemo supported drivers, then listed here are the steps to create link aggregation:
1. Identify which ports you intend to aggregate. dladm show-link should provide you with an idea what can be purchased. Ill assume you need to aggregate bge0 and bge1.
2. Run the next command to produce an aggregation interface:
If you get a mistake, it can be most likly you can either attempting make use of Nemo drivers with a not supported Ethernet driver or else you do not have the most up-to-date patches for Solaris 10.
3. Plumb the interface. See example below:
ifconfig aggr1 plub 192.168.1.200 up
4. Check the configuration:
If you made the choice that Sun Trunking 1.3 is exactly what you need, then stick to the steps below:
3. After unzip the binary from the first step, follow mobile phone steps stated in page 46 printed within the left corner within the page or page 56 according on your Acrobat reader within the Installation guide.
4. Install the appripriate patches for the driving force you use. See page 44 printed within the page or 54 as outlined by Acrobat reader within the Installation Guide.
5. Set local-mac-address as root about the command-line:
eeprom local-mac-address?true
7. Make sure the interfacs that you would like aggregate isnt plumb. If not, use the next command to unplumb:
etc/opt/SUNWconn/bin/nettr - setup 0 device ce members0, 1
This should create an aggregated interface in order to use with switches MAC based policy If you intend to use Round Robin for continual connection, use these command instead:
etc/opt/SUNWconn/bin/nettr - setup 0 device ce members0, 1 policy2
See Page 29 and 32 for even more information about other policies.
ifconfig ce0 plumb 192.168.1.200 up
Copyright 2015 Matthews Technical Reference Site. All Rights Reserved.
The right off the bat you should do before even take effect on trunking on the Solaris 10 machine is to create sure it's got latest patches.
Next, check what style of Ethernet driver do you could have. There are several ways it is possible to find out. Here is one of the ways:
Look to the first word for each and every line. If you see any of the subsequent driver types, then you can utilize Nemo drivers: bge, e1000g, xge, nge, rge, ixgb
Lets say that you could have Nemo supported drivers, then listed below are the steps to create link aggregation:
1. Identify which ports you wish to aggregate. dladm show-link should provide you with an idea what can be purchased. Ill assume you need to aggregate bge0 and bge1.
2. Run the next command to build an aggregation interface:
If you get one, it truly is most likly either attempting make use of Nemo drivers with a not supported Ethernet driver or maybe you do not have the newest patches for Solaris 10.
3. Plumb the interface. See example below:
ifconfig aggr1 plub 192.168.1.200 up
4. Check the configuration:
If you opted that Sun Trunking 1.3 is exactly what you need, then adhere to the steps below:
3. After unzip the binary from 1, follow not hard to install steps stated in page 46 printed about the left corner within the page or page 56 according on your Acrobat reader inside the Installation guide.
4. Install the appripriate patches for the motorist you use. See page 44 printed within the page or 54 based on Acrobat reader inside the Installation Guide.
5. Set local-mac-address as root around the command-line:
eeprom local-mac-address?true
7. Make sure the interfacs that you might want aggregate isnt plumb. If not, use these command to unplumb:
etc/opt/SUNWconn/bin/nettr - setup 0 device ce members0, 1
This should create an aggregated interface in order to use with switches MAC based policy If you need to use Round Robin for continual connection, use the subsequent command instead:
etc/opt/SUNWconn/bin/nettr - setup 0 device ce members0, 1 policy2
See Page 29 and 32 for more information about other policies.
ifconfig ce0 plumb 192.168.1.200 up
Copyright 2015 Matthews Technical Reference Site. All Rights Reserved.
For SunTM GigabitEthernet, SunFastEthernetTM and Sun Quad FastEthernetTM Adapters
Sun Trunkingtm 1.3 Software Supports Solaristm 7.8. 9 OS on Sun GigabitEthernettm, Sun FastEthernettm and Sun Quad FastEthernettm Adapters Announcing the supply of Sun Trunkingtm 1.3 link aggregation software. This new software includes support with the Solaristm 7, 8 and 9 Operating Environment on Sun GigabitEthernettm, Sun FastEthernettm and Sun Quad FastEthernettm Adapters. Sun Trunkingtm 1.3 software allows customers to aggregate as much as four Sun GigabitEthernet ports or approximately sixteen 10/100 Sun FastEthernet ports in to a single virtual link trunk. Once aggregated, these point-to-point links act as being a single fat pipe to deliver increased bandwidth and high availability allowing customers to transport higher aggregated data rates than any single GigabitEthernet or FastEthernet link. NEW FEATURES Key features in Sun Trunkingtm 1.3 include the subsequent: - Bandwidth aggregation bundled GigabitEthernet links and bundled FastEthernet links - Load balancing between ports depending on policy round robin, MAC or IP address hashing - Automatic Failure recovery - CLI Backward Compatibility Sun Trunkingtm 1.3 extends the functionality in Sun Trunkingtm 1.2.1 with the addition of support to this products: - Sun Gigabit Ethernet Network Interface Card Part X1150A- for good performance Category 5 UTP and PCI applications with full IEEE 802.3 compliance - Sun Gigabit Ethernet Network Interface Card Part X1151A- for good performance MMF fiber and PCI applications with full IEEE 802.3 compliance - Sun Dual FastEthernet and SCSI Network Interface Card Part X2222A as well as continued support for the subsequent products: - Sun Quad FastEthernet PCI Card QFE: Part X1034A - Installed base of Sun GigabitEthernet/PCI Card 2.0 Part X1141A: EOLed and Sun GigabitEthernet/Sbus Card 2.0 Part X1140A - Installed base of Sun Quad FastEthernet/Sbus Card 2.0 Part X1049A INTENDED AUDIENCES Sun Trunkingtm 1.3 applications are a logical solution for customers seeking to add bandwidth and high availability to systems using Sun GigabitEthernet or Sun Quad FastEthernet Adapters with a single, logical port for the existing cable. It operates between 2 Sun servers or from a Sun server plus a trunking-capable switch. Target industries/customers: - Scientific modeling, medical imaging, engineering, desktop publishing, digital content creating: sharing and transferring large files requires increased network bandwidth that's provided by Sun Trunkingtm 1.3 software - Data warehousing: Search and access of gigabits to terabytes of files requires increased bandwidth. Faster data transfer rate allows more users to reach data from various servers - Internet/intranet: Networks made up of high volume records and anticipated increased sizes of video/audio files take advantage of scalable, high bandwidth networking technology - Financial services: Data backup needs may be better accomplished using Sun Trunkingtm 1.3 software - Customers seeking maximum performance on his or her systems can make use of the load balancing functionality between ports that distributes traffic evenly over the aggregated links - Users with mission-critical data communication needs: recovery from failure ensures maximum usage of available bandwidth if any link fails MARKET VALUE PROPOSITION As the amount of users and applications over a network increases, companies face an essential problem of insufficient network capacity. Sun Trunkingtm 1.3 software provides bandwidth-enhancing technology that offers the power demanded by complex technical and commercial applications, nevertheless preserves investments in network technology. It allows customers to leverage their existing infrastructure, adds bandwidth and high availability from suppliers. PRODUCT DETAILS - KEY FEATURES AND BENEFITS: - FEATURE: Bundled Gigabit Ethernet links - FUNCTION: Support for Gigabit Ethernet Network Interface Cards NICs enables Bandwidth aggregation - BENEFIT: Scalable Bandwidth: Fat pipe aggregation of four years old 1 Gbps ports - FEATURE: Bundled Fast Ethernet links - FUNCTION: Bandwidth aggregation: The Sun QuadFastEthernet cards deliver scalable bandwidth with nearly eight 10/100 auto-negotiating Ethernet ports. Support for Dual FastEthernet/SCSI NICs can be included in this product - BENEFIT: Scalable Bandwidth: Fat pipe aggregation of sixteen 100 Mbps ports - FEATURE: Load Balancing - FUNCTION: Load balancing determined by policy round robin, MAC or IP address hashing. Static load balancing and failure recovery inside a trunk is sustained by distributing traffic, including unicast, broadcast, and multicast traffic over the aggregated links, based around the selected policy - BENEFIT: Traffic is distributed evenly along the aggregated links - FEATURE: Failure recovery - FUNCTION: Automatic link level failover - BENEFIT: Loads are automatically redistributed over the remaining links within the event of the link failure - PRODUCT SYSTEM REQUIREMENTS: - Hardware: Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00, E450 or Sun Enterprise 10000 system - OpenBoot PROM: Revision 3.x - Software: Solaris 7, 8 and 9 operating environment The following switches are tested to interoperate with Sun Trunkingtm 1.3 Software and Sun Quad FastEthernet Adapters: Vendor Name Software Revision Model Name Bay Networks 2.0.0 or compatible Accelar 1200 Cabletron Systems 2.0 or compatible SSR 2000, SSR 8000, SSR 16000 Cisco Systems 4.2 or compatible Catalyst 5000 Extreme Networks 2.1.7 or compatible Summit 4 Foundry Networks 4.6 or compatible TurboIron 8 3Com Corporation 3.0.0 or compatible 3900 CPU Requirement: Trunking QuadFastEthernet links with an Ultra Enterprise server requires CPUs of 248 MHz or faster. The server need to have an aggregate CPU speed approximately 500 MHz per Quad FastEthernet card. Two 248 MHz CPUs satisfies this requirement. - SUPPORTED PLATFORMS: - Sun Gigabit Ethernet Network Interface Cards Part X1150A and X1151A: - Sun Ultra 5, 10, 60, 80 - Sun Enterprise 220R, 250, 450, 3000/3500, 4000/4500, - Sun Enterprise 5000/5500, 6000/6500/6800, 10000, 15000 - Sun Fire 280R, V480, V880 - Sun Blade 1000 - Sun Quad FastEthernet PCI Card Part X1034A: - Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00, E450 - Sun Enterprise 10000 - Sun GigabitEthernet PCI Adapter Card 2.0 Part X1141A and Sun Gigabit Ethernet/Sbus Card 2.0 Part X1140A: - Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00 - E450, Sun Enterprise 10000 - Sun Dual FastEthernet/SCSI Network Interface Card Part X2222A: - Sun Ultra 5, 10, 60, 80 - Sun Enterprise 220R, 250, 450, 10000 - Sun Blade 100, 1000 - Sun Fire 280R, 880R, 3800, 4800, 6800, 15K - SUPPORTED OPERATING SYSTEMS: Solaris 7, 8 and 9 - LICENSING REQUIREMENTS: One Sun Trunkingtm 1.3 CD per server/system - RELEVANT STANDARDS SUPPORTED: - IEEE 802.3ad Link Aggregation - IEEE 802.3u FastEthernet - IEEE 802.3ab Gigabit Ethernet UTP - IEEE 802.3z Gigabit Ethernet Fiber - VLAN 802.3q - UPGRADE PLAN: Sun Trunkingtm 1.3 replaces Sun Trunkingtm 1.2.1, that may transition per these schedule: EOL: October 14, 2003 Last order: January 14, 2004 Last shipment: April 14, 2004 Existing users of Sun Trunkingtm 1.2.1 can upgrade to Sun Trunkingtm 1.3 by installing the newest software. For more information about ordering, please section on part and ordering - WARRANTY LENGTH: - ninety day Media replacement and telephone install support - Documentation and userguide replacement QUESTIONS AND ANSWERS Q. What is trunking? A. Sun Trunkingtm 1.3 enables aggregation of multiple Gigabit Ethernet, Quad FastEthernet or FastEthernet links in to a single virtual link for higher performance and resiliency. Q. What is Sun Trunking Software 1.3? A. Sun Trunkingtm 1.3 extends the functionality in Sun Trunkingtm 1.2.1 by building support to this products: - Sun Gigabit Ethernet Network Interface Card Part X1150A- for top rated Category 5 UTP and PCI applications with full IEEE 802.3 compliance - Sun Gigabit Ethernet Network Interface Card Part X1151A- for high end MMF fiber and PCI applications with full IEEE 802.3 compliance - Sun Dual FastEthernet and SCSI Network Interface Card Part X2222A together with continued support for the subsequent products: - Sun Quad FastEthernet PCI Card QFE: Part X1034A - Installed base of Sun Gigabit Ethernet/PCI Card 2.0 Part X1141A: EOLed and Sun Gigabit Ethernet/Sbus Card 2.0 Part X1140A - Installed base of Sun Quad FastEthernet/Sbus Card 2.0 Part X1049A Q. What would be the maximum quantity of links that might be aggregated per trunk and what number of trunks are allowed per server? A. Number of links per trunk: - Up to 16 ports of Fast Ethernet for Sun Quad FastEthernet PCI Card part X1034A - Up to 4 ports of Fast Ethernet for Sun Dual Fast Ethernet and SCSI Network Interface Card part X2222A - Up to 4 ports of Gigabit Ethernet for Sun Gigabit Ethernet Network Interface Card Part X1150A- top rated Category 5 TP/PCI applications with full IEEE 802.3 compliance - Up to 4 ports of Gigabit Ethernet for Sun Gigabit Ethernet Network Interface Card Part X1151A- good performance MMF fiber and PCI applications with full IEEE 802.3 compliance - Up to 4 ports of Gigabit Ethernet for installed base of Sun Gigabit Ethernet/P 2.0 part x1141A: EOLed Multiple trunks may be configured per server. However the total amount of links aggregated depends for the server capability. A general guideline is 1.25 MHz CPU speed for every single 1 Mbps of NIC bandwidth capability. Any quantity of aggregations might be supported in this particular guideline. Q. Is support for Ethernet ports included for the subsequent EOLed products? - 10/100 BaseT F/W UltraSCSI PCI Adapter 1.0 - 10/100 Base Fast Ethernet PCI Adapter 2.0 with MII interface to back up external peripheral devices A. The products mentioned above are certainly not supported in Sun Trunkingtm 1.3. Q. Is there support for built-in Gigabit ports in different platform? A. Sun Trunkingtm 1.3 supports built-in Gigabit ethernet ports inside V480R and V880. Q. Can the Gigabit Ethernet and FastEthernet ports from different products be mixed for linking? A. Only the next combinations are supported limitation is in the different software drivers to the chips - Combination 1: Sun Quad Fast Ethernet PCI Part x1034A - Combination 2: Sun Dual Fast Ethernet and SCSI Network Interface Card Part x2222A - Combination 3: Ports of the next products: - Sun Gigabit Ethernet NIC for high-performance Category 5 UTP and PCI applications with full IEEE 802.3 compliance Part X1150A - Sun Gigabit Ethernet NIC for high-performance MMF Fiber and PCI applications with full IEEE 802.3 compliance Part X1151A and - Built-in port of V480R - Combination 4: Ports of following products: - Sun Gigabit Ethernet/P 2.0 Part X1141: EOLed - Built-in port of V880 - Links/ports in the combination group might be aggregated - Links/ports along the combination groups are not aggregated For example, links from combination group 1 are not aggregated with links combined group 4 - All links need to be full duplex. half duplex links are not aggregated. The 802.3ad standard won't allow half duplex links to get aggregated Q. What are the supported OS versions? A. Solaris 7, 8 and 9. Q. Are the subsequent protocols supported for communication with switches? - 802.1Q - 802.3ad A. Sun Trunkingtm 1.3 will not be fully 802.3ad compliant, nonetheless it does interoperate with 802.3 compliant switches/systems within the administratively configured static mode. LACP and Marker functionality might be included in future versions that could be fully 802.3ad compliant. Note: 802.1A VLAN is supported only with the subsequent products: - Gigabit Ethernet NIC for high-performance Category 5 UTP and PCI applications with full IEEE 802.3 compliance part : X1150A - Gigabit Ethernet NIC for high-performance MMF fiber and PCI applications with full IEEE 802.3 compliance part : X1151A - PCI Adapter with two Fast Ethernet interfaces and 2 SCSI interfaces part : x2222A Q. Can Trunking 1.3 co-exist with IPMP IP Multi Pathing? A. Yes. Q. Can Trunking 1.3 co-exist with Trunking 1.2.1? A. No. Sun Trunkingtm 1.3 replaces Sun Trunkingtm 1.2.1. Q. Is trunking license per card or per system? A. Licensing model for Sun Trunkingtm 1.3 is using a per system/server basis. Q. When does Trunking 2.0 ship with 802.3ad support? A. The timeframe for Sun Trunkingtm 2.0 isn't available at this time around. Support for 802.3ad can be included in the merchandise roadmap. Q. Is Sun Trunking compatible to Cisco EtherChannel? A. Sun Trunkingtm 1.3 is works with Cisco EtherChannel and 802.3ad within the static mode. Q. Can virtual interfaces be utilized on trunking interfaces? A. Yes. The interface behaves as being a single DLPI provider, and virtual interfaces may be configured the same as those on the non-trunked interface. Q. Is Sun Trunking 1.3 supported with Sun Cluster? A. Sun Trunkingtm 1.3 will not be qualified instead of supported with Sun Cluster. Q. Does Sun Trunking 1.3 include the 802.3ad LACP Link Aggregation Protocol? A. LACP is just not currently supported in Sun Trunkingtm 1.3. LACP support could be included in future product roadmaps.
News and Solutions for Users of Solaris, Java and Oracles Sun hardware products
30, 000 Members 30, 000 Articles Published since 1998
Copyright 1998-2015 System News, Inc.
For Sun TM GigabitEthernet, SunFastEthernetTM and Sun Quad FastEthernetTM Adapters
Sun Trunking tm 1.3 Software Supports Solaris tm 7.8. 9 OS on Sun GigabitEthernettm, Sun FastEthernettm and Sun Quad FastEthernettm Adapters Announcing the supply of Sun Trunking tm 1.3 link aggregation software. This new software includes support with the Solaris tm 7, 8 and 9 Operating Environment on Sun GigabitEthernettm, Sun FastEthernettm and Sun Quad FastEthernettm Adapters. Sun Trunking tm 1.3 software allows customers to aggregate around four Sun GigabitEthernet ports or nearly sixteen 10/100 Sun FastEthernet ports in a single virtual link trunk. Once aggregated, these point-to-point links act to be a single fat pipe to produce increased bandwidth and high availability allowing customers to cart higher aggregated data rates than any single GigabitEthernet or FastEthernet link. NEW FEATURES Key features in Sun Trunking tm 1.3 include these: - Bandwidth aggregation bundled GigabitEthernet links and bundled FastEthernet links - Load balancing between ports according to policy round robin, MAC or IP address hashing - Automatic Failure recovery - CLI Backward Compatibility Sun Trunking tm 1.3 extends the functionality in Sun Trunking tm 1.2.1 by having support to the next products: - Sun Gigabit Ethernet Network Interface Card Part X1150A- for top rated Category 5 UTP and PCI applications with full IEEE 802.3 compliance - Sun Gigabit Ethernet Network Interface Card Part X1151A- for powerful MMF fiber and PCI applications with full IEEE 802.3 compliance - Sun Dual FastEthernet and SCSI Network Interface Card Part X2222A along with continued support for this products: - Sun Quad FastEthernet PCI Card QFE: Part X1034A - Installed base of Sun GigabitEthernet/PCI Card 2.0 Part X1141A: EOLed and Sun GigabitEthernet/Sbus Card 2.0 Part X1140A - Installed base of Sun Quad FastEthernet/Sbus Card 2.0 Part X1049A INTENDED AUDIENCES Sun Trunking tm 1.3 applications are a logical solution for customers trying to add bandwidth and high availability to systems using Sun GigabitEthernet or Sun Quad FastEthernet Adapters over a single, logical port around the existing cable. It operates between 2 Sun servers or coming from a Sun server plus a trunking - capable switch. Target industries/customers: - Scientific modeling, medical imaging, engineering, desktop publishing, digital content creating: sharing and transferring large files requires increased network bandwidth that's provided by Sun Trunking tm 1.3 software - Data warehousing: Search and access of gigabits to terabytes of files requires increased bandwidth. Faster data transfer rate allows more users gain access to data from various servers - Internet/intranet: Networks comprising high volume data and anticipated increased sizes of video/audio files reap the benefits of scalable, high bandwidth networking technology - Financial services: Data backup needs might be better accomplished using Sun Trunking tm 1.3 software - Customers in search of maximum performance for their systems can makes use of the load balancing functionality between ports that distributes traffic evenly along the aggregated links - Users with mission-critical data communication needs: recovery from failure ensures maximum by using available bandwidth if any link fails MARKET VALUE PROPOSITION As the amount of users and applications with a network increases, companies face a vital problem of insufficient network capacity. Sun Trunking tm 1.3 software provides bandwidth-enhancing technology that offers the power demanded by complex technical and commercial applications, but preserves investments in network technology. It allows customers to leverage their existing infrastructure, adds bandwidth and supplies high availability low cost. PRODUCT DETAILS - KEY FEATURES AND BENEFITS: - FEATURE: Bundled Gigabit Ethernet links - FUNCTION: Support for Gigabit Ethernet Network Interface Cards NICs enables Bandwidth aggregation - BENEFIT: Scalable Bandwidth: Fat pipe aggregation of four years old 1 Gbps ports - FEATURE: Bundled Fast Ethernet links - FUNCTION: Bandwidth aggregation: The Sun QuadFastEthernet cards deliver scalable bandwidth with around eight 10/100 auto-negotiating Ethernet ports. Support for Dual FastEthernet/SCSI NICs is additionally included in this product - BENEFIT: Scalable Bandwidth: Fat pipe aggregation of sixteen 100 Mbps ports - FEATURE: Load Balancing - FUNCTION: Load balancing depending on policy round robin, MAC or IP address hashing. Static load balancing and failure recovery inside a trunk is held by distributing traffic, including unicast, broadcast, and multicast traffic over the aggregated links, based about the selected policy - BENEFIT: Traffic is distributed evenly throughout the aggregated links - FEATURE: Failure recovery - FUNCTION: Automatic link level failover - BENEFIT: Loads are automatically redistributed along the remaining links inside the event of an link failure - PRODUCT SYSTEM REQUIREMENTS: - Hardware: Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00, E450 or Sun Enterprise 10000 system - OpenBoot PROM: Revision 3.x - Software: Solaris 7, 8 and 9 operating environment The following switches are tested to interoperate with Sun Trunking tm 1.3 Software and Sun Quad FastEthernet Adapters: Vendor Name Software Revision Model Name Bay Networks 2.0.0 or compatible Accelar 1200 Cabletron Systems 2.0 or compatible SSR 2000, SSR 8000, SSR 16000 Cisco Systems 4.2 or compatible Catalyst 5000 Extreme Networks 2.1.7 or compatible Summit 4 Foundry Networks 4.6 or compatible TurboIron 8 3Com Corporation 3.0.0 or compatible 3900 CPU Requirement: Trunking QuadFastEthernet links while on an Ultra Enterprise server requires CPUs of 248 MHz or faster. The server will need to have an aggregate CPU speed approximately 500 MHz per Quad FastEthernet card. Two 248 MHz CPUs satisfies this requirement. - SUPPORTED PLATFORMS: - Sun Gigabit Ethernet Network Interface Cards Part X1150A and X1151A: - Sun Ultra 5, 10, 60, 80 - Sun Enterprise 220R, 250, 450, 3000/3500, 4000/4500, - Sun Enterprise 5000/5500, 6000/6500/6800, 10000, 15000 - Sun Fire 280R, V480, V880 - Sun Blade 1000 - Sun Quad FastEthernet PCI Card Part X1034A: - Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00, E450 - Sun Enterprise 10000 - Sun GigabitEthernet PCI Adapter Card 2.0 Part X1141A and Sun Gigabit Ethernet/Sbus Card 2.0 Part X1140A: - Sun Ultra Enterprise 3x00, 4x00, 5x00, 6x00 - E450, Sun Enterprise 10000 - Sun Dual FastEthernet/SCSI Network Interface Card Part X2222A: - Sun Ultra 5, 10, 60, 80 - Sun Enterprise 220R, 250, 450, 10000 - Sun Blade 100, 1000 - Sun Fire 280R, 880R, 3800, 4800, 6800, 15K - SUPPORTED OPERATING SYSTEMS: Solaris 7, 8 and 9 - LICENSING REQUIREMENTS: One Sun Trunking tm 1.3 CD per server/system - RELEVANT STANDARDS SUPPORTED: - IEEE 802.3ad Link Aggregation - IEEE 802.3u FastEthernet - IEEE 802.3ab Gigabit Ethernet UTP - IEEE 802.3z Gigabit Ethernet Fiber - VLAN 802.3q - UPGRADE PLAN: Sun Trunking tm 1.3 replaces Sun Trunking tm 1.2.1, that may transition per the subsequent schedule: EOL: October 14, 2003 Last order: January 14, 2004 Last shipment: April 14, 2004 Existing users of Sun Trunking tm 1.2.1 can upgrade to Sun Trunking tm 1.3 by installing the brand new software. For more facts about ordering, please section on part and ordering - WARRANTY LENGTH: - 90-day Media replacement and telephone install support - Documentation and userguide replacement QUESTIONS AND ANSWERS Q. What is trunking? A. Sun Trunking tm 1.3 enables aggregation of multiple Gigabit Ethernet, Quad FastEthernet or FastEthernet links in to a single virtual link for higher performance and resiliency. Q. What is Sun Trunking Software 1.3? A. Sun Trunking tm 1.3 extends the functionality in Sun Trunking tm 1.2.1 with the help of support to the subsequent products: - Sun Gigabit Ethernet Network Interface Card Part X1150A- for powerful Category 5 UTP and PCI applications with full IEEE 802.3 compliance - Sun Gigabit Ethernet Network Interface Card Part X1151A- for top rated MMF fiber and PCI applications with full IEEE 802.3 compliance - Sun Dual FastEthernet and SCSI Network Interface Card Part X2222A as well as continued support for this products: - Sun Quad FastEthernet PCI Card QFE: Part X1034A - Installed base of Sun Gigabit Ethernet/PCI Card 2.0 Part X1141A: EOLed and Sun Gigabit Ethernet/Sbus Card 2.0 Part X1140A - Installed base of Sun Quad FastEthernet/Sbus Card 2.0 Part X1049A Q. What may be the maximum variety of links that is usually aggregated per trunk and what number of trunks are allowed per server? A. Number of links per trunk: - Up to 16 ports of Fast Ethernet for Sun Quad FastEthernet PCI Card part X1034A - Up to 4 ports of Fast Ethernet for Sun Dual Fast Ethernet and SCSI Network Interface Card part X2222A - Up to 4 ports of Gigabit Ethernet for Sun Gigabit Ethernet Network Interface Card Part X1150A- high end Category 5 TP/PCI applications with full IEEE 802.3 compliance - Up to 4 ports of Gigabit Ethernet for Sun Gigabit Ethernet Network Interface Card Part X1151A- good performance MMF fiber and PCI applications with full IEEE 802.3 compliance - Up to 4 ports of Gigabit Ethernet for installed base of Sun Gigabit Ethernet/P 2.0 part x1141A: EOLed Multiple trunks might be configured per server. However the total volume of links aggregated depends for the server capability. A general guideline is 1.25 MHz CPU speed for every single 1 Mbps of NIC bandwidth capability. Any variety of aggregations might be supported in this guideline. Q. Is support for Ethernet ports included for these EOLed products? - 10/100 BaseT F/W UltraSCSI PCI Adapter 1.0 - 10/100 Base Fast Ethernet PCI Adapter 2.0 with MII interface to aid external peripheral devices A. The products mentioned above usually are not supported in Sun Trunking tm 1.3. Q. Is there support for built-in Gigabit ports in every platform? A. Sun Trunking tm 1.3 supports built-in Gigabit ethernet ports inside V480R and V880. Q. Can the Gigabit Ethernet and FastEthernet ports from different products be mixed for linking? A. Only the next combinations are supported limitation is from your different software drivers to the chips - Combination 1: Sun Quad Fast Ethernet PCI Part x1034A - Combination 2: Sun Dual Fast Ethernet and SCSI Network Interface Card Part x2222A - Combination 3: Ports of the next products: - Sun Gigabit Ethernet NIC for high-performance Category 5 UTP and PCI applications with full IEEE 802.3 compliance Part X1150A - Sun Gigabit Ethernet NIC for high-performance MMF Fiber and PCI applications with full IEEE 802.3 compliance Part X1151A and - Built-in port of V480R - Combination 4: Ports of following products: - Sun Gigabit Ethernet/P 2.0 Part X1141: EOLed - Built-in port of V880 - Links/ports inside the combination group may be aggregated - Links/ports throughout the combination groups is not aggregated For example, links from combination group 1 are not aggregated with links combined group 4 - All links have to be full duplex. half duplex links can't be aggregated. The 802.3ad standard doesn't allow half duplex links for being aggregated Q. What are the supported OS versions? A. Solaris 7, 8 and 9. Q. Are this protocols supported for communication with switches? - 802.1Q - 802.3ad A. Sun Trunking tm 1.3 isn't fully 802.3ad compliant, but it surely does interoperate with 802.3 compliant switches/systems from the administratively configured static mode. LACP and Marker functionality could be included in future versions that could be fully 802.3ad compliant. Note: 802.1A VLAN is supported only with the next products: - Gigabit Ethernet NIC for high-performance Category 5 UTP and PCI applications with full IEEE 802.3 compliance part : X1150A - Gigabit Ethernet NIC for high-performance MMF fiber and PCI applications with full IEEE 802.3 compliance part : X1151A - PCI Adapter with two Fast Ethernet interfaces as well as SCSI interfaces part : x2222A Q. Can Trunking 1.3 co-exist with IPMP IP Multi Pathing? A. Yes. Q. Can Trunking 1.3 co-exist with Trunking 1.2.1? A. No. Sun Trunking tm 1.3 replaces Sun Trunking tm 1.2.1. Q. Is trunking license per card or per system? A. Licensing model for Sun Trunking tm 1.3 is using a per system/server basis. Q. When does Trunking 2.0 ship with 802.3ad support? A. The timeframe for Sun Trunking tm 2.0 just isn't available at now. Support for 802.3ad might be included in the item roadmap. Q. Is Sun Trunking compatible to Cisco EtherChannel? A. Sun Trunking tm 1.3 is works with Cisco EtherChannel and 802.3ad inside the static mode. Q. Can virtual interfaces be utilized on trunking interfaces? A. Yes. The interface behaves being a single DLPI provider, and virtual interfaces could be configured similar to those using a non-trunked interface. Q. Is Sun Trunking 1.3 supported with Sun Cluster? A. Sun Trunking tm 1.3 just isn't qualified but not supported with Sun Cluster. Q. Does Sun Trunking 1.3 offer the 802.3ad LACP Link Aggregation Protocol? A. LACP isn't currently supported in Sun Trunking tm 1.3. LACP support could be included in future product roadmaps.
News and Solutions for Users of Solaris, Java and Oracles Sun hardware products
30, 000 Members 30, 000 Articles Published since 1998
Copyright 1998-2015 System News, Inc.