IBM 9077 SP Switch Router: Get Connected to the SP Switch Hajo Kitzhöfer, Steffen Eisenblätter, Uwe Untermarzoner International Technical Support Organization http://www.redbooks.ibm.
SG24-5157-00 International Technical Support Organization IBM 9077 SP Switch Router: Get Connected to the SP Switch November 1998
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 305. First Edition (November 1998) This edition applies to PSSP Version 2, Release 4 for use with AIX 4.3.1 and Ascend Embedded/OS Version 1.4.6.4. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept.
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Comments Welcome . . . . . . . . . . . . . . . . . . . . .
2.4.1 SDR Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 2.4.2 New Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 2.4.3 Enhanced Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 2.4.4 Hardware Perspectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 2.4.5 SP Extension Node SNMP Manager . . . . . . . . . . . . . . . . . . . . . . 58 2.4.6 Dependent Node MIB . . . . . . . . . . . . . .
3.14.2 Check Media Card Status Using grcard . . . . . . . . . 3.14.3 Reset Media Card Using grreset . . . . . . . . . . . . . . . 3.14.4 Using grstat to Display GRF Statistics . . . . . . . . . . 3.15 Bringing the SP Switch Router Adapter Card Online with 3.15.1 Checking Connectivity to the SP System . . . . . . . . . . . . . . . . . 98 . . . . . . . . . 99 . . . . . . . . . 99 the SP . . 100 . . . . . . . . 101 Chapter 4. Configuration of IP-Forwarding Media Cards . . . . . . . . . . 105 4.
4.5.3 Physical and Logical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 139 4.5.4 Configuration Files and Profiles . . . . . . . . . . . . . . . . . . . . . . . . 140 4.5.5 Installing Configurations or Changes . . . . . . . . . . . . . . . . . . . . 141 4.5.6 Some maint Commands for the HIPPI Media Card . . . . . . . . . . 141 4.6 Configuring Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 4.6.1 GRF Bridging Implementation . . . . . . . . . . . . . . . .
Appendix A. Laboratory Hardware and Software Configuration . . . . 233 A.1 Node and Control Workstation Configuration . . . . . . . . . . . . . . . . . . . . . 233 A.1.1 Hard Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 A.1.2 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 A.1.3 Network Options and Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 A.2 SP Switch Pool Size Settings . . . . . .
Appendix D. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Appendix E. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 E.1 International Technical Support Organization Publications . . . . . . . . . . 309 E.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 E.3 Other Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. SP Switch Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Functional Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Typical Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Table-Based Routing . . . . . . . . .
41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. x Master/Slave Connectors for SAS Interfaces . . . . . . . . . . . . . . . . . . . . . 122 A/B Connectors for DAS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Allowed SAS and DAS Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Optical Bypass Switch Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. Memory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 DependentNode Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 DependentAdapter Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Additional SDR Attributes . . . . . . . . . . .
41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. xii Software Levels on CWS and All Nodes Part 10 of14 . . . . . . . . . . . . . . . 248 Software Levels on CWS and All Nodes Part 11 of 14 . . . . . . . . . . . . . . 249 Software Levels on CWS and All Nodes Part 12 of 14 . . . . . . . . . . . . . . 250 Software Levels on CWS and All Nodes Part 13 of 14 . . . . . . . . . . . . . . 251 Software Levels on CWS and All Nodes Part 14 of 14 . . . . . . . . . . . . . .
Preface The GRF is a high-performance switched IP Router which provides high-speed data communication links between IBM RS/6000 SP and external networks or hosts. It acts as a special-purpose SP node that routes IP traffic between SP nodes on the SP Switch and the outside world. Connected directly to the SP Switch, the router offers significantly improved SP I/O performance. When packaged with an IBM SP system, the GRF router is referred to as the SP Switch Router.
for eight years. His areas of expertise include RS/6000 SP, SMP, and Benchmarks. He now specializes in SP System Management, SP Performance Tuning and SP hardware. Dr Steffen Eisenblätter is an AIX Software Specialist in the RS/6000 SP Software Support Center, Germany. He holds a Ph.D. degree in physics from the University of Leipzig. He joined IBM in 1997 and has focused on RS/6000 SP products and TCP/IP. Uwe Untermarzoner is an RS/6000 SP Technical Support Specialist with IBM Germany. He joined IBM 1989.
Comments Welcome Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other redbooks in one of the following ways: • Fax the evaluation form found in “ITSO Redbook Evaluation” on page 323 to the fax number shown on the form. • Use the electronic evaluation form found on the Redbooks Web sites: For Internet users http://www.redbooks.ibm.com For IBM Intranet users http://w3.itso.ibm.
xvi IBM 9077 SP Switch Router: Get Connected to the SP Switch
Part 1. Introducing and Installing the GRF © Copyright IBM Corp.
2 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Chapter 1. Dependent Node This chapter provides an overview of a dependent node in RS/6000 SP. We start by defining the dependent node and the rationale behind its design. 1.1 Dependent Node Architecture The Dependent Node Architecture refers to a processor or node, possibly not provided by IBM, for use with the RS/6000 SP. Since a dependent node may not be a regular RS/6000 SP node, not all the functions of a node can be performed on it, which is why it is called "dependent".
• The fault service daemon runs on all switch nodes in the RS/6000 SP, but not on the dependent node. Therefore, the dependent node does not have the full functionality of a normal RS/6000 SP Switch node. • The dependent node requires the SP Switch’s primary node to compute its switch routes. Therefore, the primary node must have at least PSSP 2.3 installed, otherwise the dependent node cannot work with the RS/6000 SP.
Chapter 2. Router Node The first dependent node is actually a new SP Switch Router Adapter in a router. This chapter offers more details about the implementation. Section 2.1, “Overview” on page 5 gives you an overview of SP Switch Router. This is probably the best to get an impression what the GRF is good for. Also a functional- and a price-comparison between using an RS/6000 SP node and the SP Switch Router is included. More details about the underlaying Software and Hardware can be found in Section 2.
IBM 9570 Disk Array Subsystem SP Switch HIPPI Adapter Adapter HIPPI Adapter SP Switch ATM OC-12c ATM SP Switch OC-3c Adapter Processor Nodes ATM Switch 8-port E-net 10/100 SP Switch Adapter 4-port FDDI SP System SP Switch Router Figure 1. SP Switch Router The RS/6000 SP software treats this adapter as an extension node. It is a node because it takes up one port in the SP Switch and is assigned a node number.
packet size. This would only enable a wide node to handle approximately 7.5 MB/s of IP traffic. Since Ascend’s business depends on keeping pace with networking technology, they already support the major interfaces today. The 9077 will be able to take advantage of any new interfaces that are developed in the future as well, with no further development time or money expended. With some interfaces requiring up to 5 slots, even a wide node can run out of available slots.
2.1.2 Design Objectives Because the dependent node is part of the RS/6000 SP, it had to be packaged and assigned some roles consistent with other RS/6000 SP nodes. Changes were made to the RS/6000 SP to incorporate management requirements for the dependent node. Ease of design and implementation were important objectives in the design. These were accomplished by limiting the amount of switchcontrol protocol for the dependent node.
Network 1 Network 3 Router Network 2 Network n Figure 3. Typical Router Configuration Routers help to reduce the amount of processing required on local systems, since they perform the computation of routes to remote systems. For example, a system can communicate with a remote system by passing the message (or packets) to the router. The router works out how to get to the remote system and forwards the message appropriately. Storing routes on the system takes up memory.
• Minimal routing A network completely isolated from all other TCP/IP networks requires only minimal routing. A minimal routing table is usually built by ifconfig when the network interfaces are configured. If your network does not have direct access to other TCP/IP networks, and if you are not using subnetting, this may be the only routing table you require. • Static routing A network with a limited number of gateways to other TCP/IP networks can be configured with static routing.
situations more quickly and accurately than a system administrator can do. Routing protocols are designed not only to switch to a backup route when the primary route becomes inoperable; they are also designed to decide which is the "best" route to a destination. On any network where there are multiple paths to the same destination, a dynamic routing protocol should be used. 2.1.
The second case has proven to be very expensive as well. The RS/6000 SP node was not designed for routing. It is not a cost-effective way to route traffic for the following reasons: • It takes many CPU cycles to process routing. The CPU is not a dedicated router and is very inefficient when used to route IP traffic (this processing can result in usage of up to 90%). • It takes a lot of memory to store route tables. The memory on the RS/6000 SP node is typically more expensive than router memory.
The GRF uses a crosspoint switch (see Figure 7) instead of an I/O bus to interconnect its adapters. This switch is capable of 4 or 16 Gbit/s (model dependent) and gives better performance than the MCA bus. IP Switch Control Board Route Manager 4Gb/s Crosspoint Switch 1 Gb/s to each Media Card Switch Engine Interface Route Table and Lookup I/O Buffering IP Packet Forwarding T3-OC12 LAN/WAN LAN/WAN Interfaces Media Cards Figure 7.
Unswitched Data Switched Data 5 2 Router 4 1 Router 3 Router Disadvantages: Shared data paths All processing done on Layer 3 Slow softwarebased processing Process Packets ...... .... ..... .... ...... .... Layer 2 Router Process Packets ........ .... Layer 3 Router ..... Figure 8. Conventional Routers The SP Switch Router provides near wire-speed packet forwarding while using standard routing protocols.
Unswitched Data Switched Data 5 2 Examples: Router Ascend GRF, SP Switch Router Cisco 12000 4 1 Router 3 Router Disadvantages: Hardware can be hard to upgrade * Reduced routing functions * Layer 3 Layer 2 Switch Switch Process Route Process Route Advantages: ..... ..... ......... ..... ..... Behave like traditional router Not dependent on a network architecture Interoperability Figure 9.
MulticastIP Multicast and OSPF Multicast EGPExterior Gateway Protocol BGPBorder Gateway Protocol Version 3 or 4 (BGP 3 or 4) More details about the various protocols are in Section 2.2.2, “Supported Routing Protocols” on page 20. 2.1.7 Media Adapters At-a-Glance Available IP forwarding media cards are: • 1-port 100 Mbyte/s Switch Adapter • 8-port 10/100 Mbit/s Ethernet cards • 2-port 155 Mbit/s OC-3 ATM (Asynchronous Transfer Mode UNI 3.0/3.
adapter. As a result, other network adapters are brought down as well. Bringing down the router will impact all the networks in the location. Each RS/6000 SP is allowed to connect to multiple SP Switch Router Adapters, and it does not matter if these adapters are on different GRFs. Connecting multiple SP Switch Router adapters to either different partitions in an RS/6000 SP or to different RS/6000 SPs allows them to communicate with each other and with the other GRF media adapters via the SP Switch.
9077-04S with one SP Switch Router Adapter HIPPI Adapter 9077-04S with one SP Switch Router Adapter HIPPI Adapter 135 MHz Wide Node 9077-04S $ 53,000 13,500 66,500 $ 53,000 48,000 3,200 64 MB memory with one SP Switch Router Adapter 1,950 4.5 GB Disk HIPPI Adapter 595 Ethernet 135 MHz Wide Node 10,000 64 MB memory SP Switch Adapter 17,500 4.5 GB Disk HIPPI Adapter 135 MHz Wide Node Ethernet 81,245 64 MB memory SP Switch Adapter 4.
Manager updates the system routing tables and performs other administrative functions, the intelligent processors on each media card perform all routing functions. This design supports efficient distributed processing of router operations. 2.2.1 IP Protocol The GRF supports IP datagram routing between major types of standard media. The implementation conforms with IP Version 4 and routing specifications described in Internet RFCs.
Subnet Masking/Supernetting Variable length subnet masking is a classless addressing scheme for interdomain IP packet routing. It is a way to more efficiently manage the current 32-bit IP addressing method. Subnet masks let sites configure the size of their subnets based on the site needs, not on the arbitrary Class A, B, and C structure originally used in the Internet addressing.
information for the autonomous system. Here is the list of interior protocols supported by the GRF: • RIP The Routing Information Protocol (RIP), as delivered with most UNIX systems, is run by the routing deamon routed. During the startup of routed a request for routing updates is issued. After that, the daemon listens for responses to the request. Systems that are configured to supply RIP information hear this request and respond with update packets based on the information in the system’s routing table.
Every area must connect to the backbone, because the backbone is responsible for the distribution of routing information between areas. The backbone itself has all the properties of an area. Its topology is separate from that of other areas. • Subarea A subarea has only one area border router, which means that there is only one route out of the area. In this case, the area border router does not need to advertise external routes to the other routers within the subarea.
Host extensions for IP multicasting as described in RFC 1112 are also provided. The Router Manager acts as a host and uses the Internet Group Management Protocol (IGMP), version 2, to add and delete its membership in multicast groups. Accordingly, the Route Manager "joins" the appropriate routing protocol host groups for OSPF and RIP. • IS-IS Intermediate System to Intermediate System (an OSI gateway protocol) is a protocol similar to OSPF: it also uses a Link State, Shortest Path First algorithm.
• Source address • Destination address • Protocol port number (single number, or range, or ranges) for TCP and UDP • Established TCP connections 2.2.4 System Management The GRF currently supports the Simple Network Management Protocol (SNMP) Version 1, which provides a mechanism for remote query or setting operational parameters for the device. Media cards collect network statistics, which can be reported to network management packages via the Router Manager on the IP Switch Control Board.
19" Cooling Fan Drawer 5.
Power SupplyThe left side of the chassis is reserved for the two power supplies that are required for redundancy. The failed power supply can be hot-swapped out of the GRF chassis. GRF 1600 Part Description Cooling FansThese are located at the top of the chassis, and can be accessed separately from the other parts of the GRF. The fan tray contains redundant fans and is hot-swappable. Media CardsThere are 16 media card slots on this chassis. They are slotted vertically.
If the temperature exceeds 57.5 °C (137 °F), the GRF does an automatic system shutdown. • Hot-swappable fan For the GRF 16S model, the cooling fan can be replaced while the GRF is in operation. • Hot-swappable adapters There are two types of adapters on the GRF: the media adapters and the IP Switch Control Board. The media adapters are independent of each other and can be replaced or removed without affecting any other adapter or the operation of the GRF.
1. Normally, all media cards have a 4 MB send buffer and a 4 MB receive buffer, except the SP Switch Adapter card, which has a 16 MB buffer size for each buffer. See also Section 2.3.5, “Characteristics of GRF Media Cards” on page 36 and Figure 19 on page 37. 2. Quick Branch Routing Technology (QBRT) is a hardware-assisted route table lookup. Route lookup times range from 1 - 2.5 µs with up to 150,000 next-hop routes in the table. Not all media cards use QBRT.
External Interface External Interface Internal Interface CPU QBRT DMA Internal Interface Rx Buffer DMA Tx Buffer CPU QBRT DMA Rx Buffer Tx Buffer DMA Switch Control Board Dynamic Route Manager Figure 13. Data Packet Transfer The routing can be divided into the following steps: 1. A data packet is received by the media card. 2. The packet is transferred to the receive buffer by the DMA engine. 3. The CPU examines the header and gives the destination address to the route lookup hardware. 4.
10.The header is examined by the CPU, which uses the information to build a new header that will deliver the data across the media interface. 11.The DMA engine transfers the packet to the media interface. 12.The packet is transferred across the media. 2.3.2.2 Routing Packet Processing The processing of packets with routing information is a little bit different from the data packet processing procedure as you can see in Figure 14.
6. The packet is then transferred to the Combus interface by the DMA engine. 7. The packet is sent to the IP Switch Control Board’s Router Manager across the Combus. 8. The Route Manager receives the packet and passes it to the dynamic routing software. 9. The packet is processed and global routing information is determined. 10.Route updates are broadcast across the Combus to all media cards simultaneously. 11.Each card receives the update packet and makes changes to its route tables. 12.
Backplane 66 IP Switch Control Board 3 2 1 0 Slot numbers in decimal for media cards Figure 15. Side View of GRF 400 Chassis with Slots Numbered The GRF 1600 has 16 media slots. The control board is located in slot 66, as shown in Figure 16. Backplane Media cards Slot numbers 0 1 2 3 4 5 6 7 Control board 66 8 9 10 11 12 13 14 15 Switch board Figure 16.
2.3.3.1 Route Manager As already mentioned, the router management takes place on the IP Switch Control Board. Specific functions of the Route Manager are: • It processes all dynamic routing packets. • It synchronizes the route tables on the media cards. • It controls the media cards: issues interrupts and resets to individual media cards and downloads executable programs and connection information. 2.3.3.2 IP Switch Control Board Components Let us examine the IP Switch Control Board in more detail.
ItemDescription MemoryThe IP Switch Control Board comes standard with 128 MB of memory (the four shaded blocks of 32 MB of memory in the upper left corner). The memory can be upgraded to 256 MB, in increments of 64 MB (the four white blocks of memory). The system uses the first 32 MB of memory for file system storage. The top half is used for applications such as the SNMP agent, the gated daemon, and for the operating system.
Additionally, the RS232 port (which is not shown in the figure) allows you to connect the VT100 console by using an RS232 null modem cable. The console and cable must be supplied by the user. 2.3.4 Memory Guidelines for the IP Switch Control Board As already mentioned, the GRF base system comes with 128 MB of memory. In all GRF memory configurations, 32 MB are used for the file system and the remainder is used for system operations.
64MB RAM 64MB RAM 64MB RAM - System software 32MB (fixed size) 20MB 8-12MB (fixed size) - Config files 64MB RAM - Gated binary - Route table - Kernel runs - Gated runs = expandable area of RAM Figure 18. System RAM 2.3.5 Characteristics of GRF Media Cards All GRF media cards (media adapters) are self-contained and independent of other media adapters. Each media card has an onboard processor that is responsible for IP forwarding on the media adapter.
Crosspoint Switch Media Board 7 3 6 2 5 1 4 0 Receive TBIC 16MB Buffer(1) FIFO (1) Receive Proc & C Send Proc & C Send TBIC SP Switch 16MB Buffer(2) FIFO (2) Serial Daughter Card Figure 19. SP Switch Router Adapter The SP Switch Router Adapter is made up of two parts: the media board and a serial daughter card. The serial daughter card is an interface for the media board into the crosspoint switch. This switch is the medium by which the GRF (media) adapters talk to each other.
Receive Controller and ProcessorThis component recognizes the SP Switch segments and assembles them into IP packets in the 16 MB buffer. Up to 256 IP datagrams can be handled simultaneously. When a complete IP packet has been received, the Receive Controller sends the packet to the FIFO (1) queue for transfer to the serial daughter card. Buffer (1)This component is segmented into 256 64 KB IP packet buffers.
• It is able to transfer up to 30,000 packets per second. At 20,000 packets per second, each packet needs to be at 5 KB in order to achieve the 100 MB per second transfer rate mentioned. • As previously mentioned, each adapter stores its own route tables in memory. Therefore, route table lookup is very fast, that is, less than 2.5 µs. • Finally, each media adapter has a 1 Gbit per second dedicated link into the crosspoint switch.
IP/SONETThe IP/SONET OC-3c is a single-ported card that allows the user to connect to a digital network using a transmission format known as Synchronous Optical Network protocol (SONET). This standard is increasingly popular in the telecommunications industry. 2.3.9 GRF Operating Environment As previously mentioned, the operating temperature should not exceed 53 °C (128 °F).
The attributes of the DependentNode class are described in detail as follows: AttributeDescription node_numberThis user-supplied node number represents the node position of an unused SP Switch port used for the SP Switch router adapter. extension_node_identifierThis is a 2-digit slot number that the SP Switch router adapter occupies on the GRF. Its range is from 00 to 15. reliable_hostnameThe hostname of the administrative Ethernet, de0, is the GRF’s hostname.
2.4.1.2 DependentAdapter Attributes The attributes of the DependentAdapter class are described in Table 3: Table 3. DependentAdapter Attributes User Defined System Defined node_number - netaddr - netmask - The attributes of the DependentAdapter class are described in detail as follows: AttributeDescription node_numberThis user-supplied node number represents the node position of an unused SP Switch port to be used by the SP Switch router adapter.
AttributeDescription node_typeThis attribute is set to dependent for GRF and to standard for all other RS/6000 SP nodes. switch_max_ltuThis specifies the maximum packet length of data on the SP Switch; the default is 1024. Do not change this value for any reason . switch_link_delaySpecifies the delay for a message to be sent between the two furthest points on the switch; the default is 31. Do not change this value for any reason. 2.4.
The enadmin command is used to change the administrative state of a dependent node in the GRF; it has the following characteristics: • It is part of the ssp.spmgr fileset. • It must only be executed on the Control Workstation. • It can only be executed by the root user. • The -r option from endefnode and endefadapter triggers enadmin -a reconfigure, while the -r option from enrmnode triggers enadmin -a reset. • The return code is 0 if successful, 1 if failed.
Table 7. endefnode Command Options Flags SMIT Option Description -a Administrative hostname This is the hostname of the GRF, and the IP name of the GRF’s administrative Ethernet, de0. Use long names if DNS is used in the network. -c SNMP community name This field contains the SNMP community name that the SP extension node SNMP Manager and the GRF’s SNMP agent send in the corresponding field of the SNMP messages. This value must match the value specified in the /etc/snmpd.conf file on the GRF.
Attention Note that this command only affects the SDR, unless the -r option is used. The -r option should be issued only if endefadapter has been executed for the extension node. When the GRF is properly configured and powered on, with the SP Switch Router Adapter inside, it periodically polls the Control Workstation for configuration data. The -r option or enadmin command is not required to activate the polling here. 2.4.2.
2.4.2.3 The endefadapter Command The endefadapter command is used to add or change the extension node adapter IP information in the SDR DependentAdapter object, and can be executed using smit. The fast path for smit is enter_extadapter. The command options are shown in Table 9. Table 9. endefadapter Command Options Flags SMIT Option Description -a Network address Specifies the IP address of the extension node. -m Network netmask Specifies the netmask for the extension node.
2.4.2.5 The enadmin Command The enadmin command is used to change the status of the SP Switch router adapter in the GRF and can also be executed using smit. The fast path for smit is manage_extnode. The command options are shown in Table 10. Table 10. enadmin Command Options 48 Flags SMIT Option Description -a Actions to be performed on the extension node Either reset or reconfigure.
2.4.2.6 The splstnodes Command The splstnodes command is used to list the node attributes of all nodes in the SDR, and can also be executed using smit. The fast path for smit is list_extnode. See all command options in Table 11. Table 11. splstnode Command Options Flags Description -h Outputs usage information. -G Ignores partition boundaries for that output. -x Inhibits header record in the output. -d Uses the between its attributes in the output.
2.4.2.7 The splstadapters Command The splstadapers command is used to list the adapter attributes of all nodes in the SDR, and can also be executed using smit. The fast path for smit is list_extadapter. See all command options in Table 12. Table 12. splstadapter Command Options 50 Flags Description -h Outputs usage information. -G Ignores partition boundaries for its output. -x Inhibits header record in the output. -d Uses the between its attributes in the output.
2.4.3 Enhanced Commands The following commands (see Table 13) have been modified due to the introduction of the dependent node: Table 13. Enhanced Commands Command Comment Eprimary The dependent node cannot be the Primary node. Estart The dependent Node depends on the Primary node to calculate the routes. Efence Enhanced for dependent node support. Eunfence Enhanced for dependent node support.
2.4.4 Hardware Perspectives In Perspectives IP Node is used as a convenient and short descriptive term easily displayed in the GUI. It conveys the role and functions of the dependent node. Currently, this is the only dependent node. In Figure 20 we show the changes made to Perspectives because of the introduction of the IP Node. The changes are restricted to the Hardware and System Partition Aid Perspectives. 1 2 3 4 Figure 20.
3. Nodes pane (Frame or Icon View) 4. Information area The most obvious change is the addition of the IP Node icon as seen in the Nodes pane. (The figure above shows the Frame View.) The default label for this icon is IP Node . The IP Node icon is also located on the side of the frame, where a standard node with that node number would be. In this figure the IP Nodes are 7, 14 and 15. When switch_responds is monitored, it shows the IP Node in two states: • Green when working with the SP Switch.
1 2 3 4 Figure 21. Action Menu • View This will bring up the IP Node’s hardware notebook, shown in the next figure. • Fence/Unfence... This will bring up another window to allow us to either fence or unfence an IP Node. If we are fencing the IP Node, we can use the option of autojoin. • Create Node Group... This will bring up another window to allow us to add the RS/6000 SP nodes to a Node Group. This action does not affect the IP Node, even though it is selectable.
This will bring up a window to show the three-digit display of all RS/6000 SP standard nodes in the current partition. This action does not apply to the IP Node, even though it is selectable. • Open Administrative Session... This action will open a window that is a Telnet session to the GRF, using the reliable_hostname attribute specified in the DependentNode class. In addition, the Nodes pane in this figure shows the Icon View.
These are the attributes listed in the Configuration tab: • Node number • Hostname • Management agent hostname • SNMP community name • System partition • Extension node identifier • Dependent node IP address • Dependent node netmask • Switch port number • Switch number • Switch chip • Switch chip port • Switch partition number • Switch responds The All Dynamic Resource Variables tab only shows the state of the Switch Responds, and the Monitored Conditions tab only shows the value of the Switch Responds if i
1 2 3 4 Figure 23. System Partition Aid Perspectives The IP Nodes can only be assigned to a partition here. This is done either by using the Assign icon in the toolbar (2), or by selecting Action->Nodes->Assign Nodes to System Partition on the menu bar (1). Except for the System Partition Notebook, discussed in the next figure, all other actions, though selectable, do not apply to the IP Node. 2.4.4.4 System Partition Aid Notebook Figure 24 on page 58 shows the IP Node System Partition Aid Notebook.
Figure 24. System Partition Aid Notebook These attributes are listed in the Node Information tab: • Node number • Switch port number • Assigned to system partition 2.4.5 SP Extension Node SNMP Manager The SP Extension Node SNMP manager is contained in the ssp.spmgr file set of PSSP. This file set must be installed on the Control Workstation in order for the GRF to function as an extension node. The SP Extension Node SNMP manager is an SNMP manager administered by the System Resource Controller.
•stopsrc •lssrc •traceson •tracesoff 2.4.6 Dependent Node MIB IBM has defined a dependent node SNMP Management Information Base (MIB) called ibmSPDepNode. This MIB contains definitions of objects representing configuration attributes of each dependent node and its state. The GRF Agent maintains the state and configuration data for each dependent node using the MIB as a conceptual database. The MIB defines a single table of up to 16 entries representing the adapter slots in the GRF.
ibmSPDepSwTokenA combination of switch_number, switch_chip and switch_chip_port attributes from the DependentNode class. ibmSPDepSwArpThe arp_enabled attribute in the Switch_partition class. ibmSPDepSwNodeNumberThe switch_node_number attribute in the DependentNode class. ibmSPDepIPaddrThe netaddr attribute in the DependentAdapter class. ibmSPDepNetMaskThe netmask attribute in the DependentAdapter class. ibmSPDepIPMaxLinkPktThe switch_max_ltu attribute in the Switch_partition class.
PSSP 2.4 to represent coexistence. Also, note that Node 16 is empty, because the SP Switch port for this node is used by the SP Switch router adapter in the GRF. 15 13 11 9 7 5 3 1 PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP 2.4 16 14 12 10 8 6 4 2 PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP *.* PSSP 2.4 PSSP 2.4 or PSSP2.3 and IX70649 on CWS Primary switch node Backup switch node PTFs for all other nodes for PSSP2.1 IX71246 for PSSP2.2 IX71245 ssp.
• All RS/6000 SP nodes with a version less than PSSP 2.3 in the partition need to maintain the right level of fixes (PTFs) in order for coexistence with PSSP 2.4 to take place. • The ssp.spmgr file set must be installed on the Control Workstation. • Because the SP Switch router adapter will only work with the 8-port or 16-port SP Switch, make sure that the switch used in the RS/6000 SP is not a High Performance Switch (HiPS).
Cross-partition communication through the SP Switch IP Switch Control Board SP Switch Crosspoint Switch SP Switch Partition B 4-port FDDI GRF 1600/400 Partition A Partition A Partition B SDR Switch Frame Ethernet Cable CWS RS232 Cable PSSP 2.4 Figure 26. Partitioning Normally, RS/6000 SP nodes in different partitions cannot communicate with each other through the SP Switch.
Next, ensure that the following parameters are defined: ParametersDescriptions GRF IP addressThe IP address for the GRF administrative Ethernet. GRF netmaskThe Netmask for the GRF administrative Ethernet. GRF Default routeThe default route of the GRF. SNMP community nameThis attribute describes the SNMP community name that the SP Extension Node SNMP Manager and the GRF’s SNMP Agent will send in the corresponding field of the SNMP messages.
2.6 Planning for the Dependent Node Next, for each dependent node on the RS/6000 SP, define the following: ParametersDescriptions Node #A user-supplied dependent node number representing the node position of an unused SP Switch port to be used by the SP Switch Router Adapter. Slot #The slot number on which the SP Switch Router Adapter is located in the GRF. GRF hostnameThe hostname for the GRF administrative Ethernet. A long hostname is recommended if the domain name service (DNS) is used in the network.
2.7 Conclusion The SP Switch Router 9077-04S has an aggregate bandwidth of 800 MB/s. An SP wide node by contrast is capable of no more than about 65 MB/s of sustained throughput. A wide node’s CPU hits a wall at about 5000 packets/second, whereas the 9077 is capable of an aggregate of 2.8 million packets/second. All this is achieved in part because of the non-blocking crosspoint switch with four 100 MB/s, full duplex connection points. This enables multiple paths to operate at full speed simultaneously.
Part 2. Scenarios This part presents some sample configurations of an RS/6000 SP system with an SP Switch Router. It is beyond the scope of this book to represent all possible applications of an SP Switch Router. Nevertheless, the basic configurations shown are building blocks for more complex networking topologies that include the SP Switch Router and may inspire more complex configurations. All following sample scenarios were carefully chosen to match frequently occurring customer situations.
68 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Chapter 3. Installation and Configuration The SP Switch Router functions as an IP router to provide high-speed data communication links between SP processor nodes and external networks or hosts. The SP Switch Router Adapter media card connects to the SP Switch board in an SP system as shown in Figure 28.
The intent of this chapter is to provide, or refer you to, the necessary information to enable you to attach an SP Switch Router to an IBM SP system. Coverage is provided as follows: • Information to configure the SP Switch Router Adapter card as required for SP Switch Router functionality is complete in this chapter. • Information to physically connect the two independent systems across cables is complete in this chapter.
UNIX systems. On most of the UNIX systems you are working on the shell layer after you logged onto the system. Many system management and configuration commands are now available. Enter a question mark (?) to retrieve a list of CLI commands. To edit configuration files, you must be in the UNIX shell. The sh command opens the UNIX shell you use to modify configurations. The following screen shows how to do this.
system and enter these basic configuration parameters. Procedures for starting and setting up the SP Switch Router are found in GRF 400/1600 Getting Started V.14, GA22-7368. Ignore the prompts for network logging, since we will configure logging to a PCMCIA device; just press Enter when asked to enter the remote logging host name or its IP address. • Remote Telnet access is working.
Ethernet Cable RS232 Cable CWS Standard Switch Cable of 10m Other Switch Cables 5m (f/c 9305) 10 m (f/c 9310) 15 m (f/c 9315) 20 m (f/c 9320) PSSP 2.4 10BaseT SP Switch Cable IP Switch Control Board SP Switch Crosspoint Switch Grounding Cable Figure 29. Connecting the GRF to the Frame • You are ready to configure media cards. Procedures to configure media cards are in this redbook; complete information is in the GRF Configuration Guide 1.4, GA22-7367.
Admin Ethernet (de0) IP Switch cws Terminal Settings 9600 baud GRF 400 No parity Eight data bits One stop bit Crosspoint Switch Control Board SP Switch RS232 (Null Modem Cable) VT100 terminal GRF Console (optional) Figure 30. Connecting the GRF Console • The IBM SP system is up and operating.
4. Methods to determine node number and SP Switch port for an SP Switch Router Adapter card 5. A step-by-step configuration of an SP Switch Router Adapter card 6. A list of ways to verify that the SP Switch Router Adapter card is correctly installed in the SP Switch Router 7. A description of what needs to occur to bring the card online to the SP system 3.
4. Route the Ethernet twisted-pair cable between the SP Switch Router unit and the Ethernet hub, then connect the cable to the SP Switch Router control board and the Ethernet hub. 5. Verify that the SP CWS has a connection to this same Ethernet hub. If the SP CWS Ethernet adapter is configured by the system administrator, then a ping test from the SP CWS to the configured SP Switch Router Ethernet address should be done to test Ethernet connectivity.
prompt> sh # # cd / # iflash -A May 29 15:54:18 grf16 kernel: wd2: no disk label # mountf -A -w -m /mnt Device /dev/wd3a mounted on /mnt # mkdir /mnt/crash # mkdir /mnt/portcards # cd /var # mv crash crash.orig # mv portcards portcards.orig # ln -s /var/log/portcards /var/portcards # ln -s /var/log/crash /var/crash # grsite --perm portcards crash Device /dev/wd0a mounted on /flash. Device /dev/wd0a unmounted. # # cd /var/log # pax -rw -pe -v . /mnt /mnt/. /mnt/./cron /mnt/./daemon.log /mnt/./lastlog /mnt/.
5. Edit the file /etc/syslog.conf to specify the location where the logs will be kept. Uncomment the local log configuration lines in the “Log messages to Disk” section by removing #disk# from each line, and specify /var/log as the directory for each log. The entries should now look like the following: *.err;*.notice;kern.debug;lpr,auth.info;mail.crit /var/log/messages cron.info /var/log/cron local0.info /var/log/gritd.packets local1.info /var/log/gr.console local2.* /var/log/gr.boot local3.
*********************************************************************** * Log files that used to be archived by the /etc/{daily|weekly|monthly} * scripts. *********************************************************************** size=150000 logfile=/var/log/gr.console size=11000 logfile=/var/log/gr.boot 7. Save all changes and reboot: # grwrite -v # reboot 8. After the SP Switch Router is up and running again, use csconfig -a to verify that the PCMCIA interface is available and the PCMCIA disk are up.
SP Control Workstation Hub SP Switch Router Administrative Ethernet network Control board Figure 31. SP System Administrative Ethernet Connections 3.4.2 SP Switch Cable The SP Switch Router Adapter card provides one full-duplex attachment and requires a specific cable with 50-pin connector ends, obtainable from IBM. The cable has a unique signal wiring map, and is not replaceable by a 50-pin HSSI cable, for example.
2. Using appropriate frame entry and exit holes for cable management, route the SP Switch cable between the SP Switch Router unit and the SP Switch. 3. Connect the SP Switch cable to both the media card and the correct SP Switch port, as follows: • Connection to media card The EMI shielding fitted inside the connector end can make insertion difficult, so be sure to insert the connector end as perpendicular as possible. (Pins can be damaged when the connector is inserted at too much of an angle.
3.5.1 Determining the Switch Connection for a Dependent Node The SP Switch Router Adapter connection replaces an SP node connection to the SP Switch. Each SP Switch Router Adapter media card is referred to as a dependent node, and is assigned a node number that corresponds to its specific connection on the SP Switch.
14 12 10 8 6 4 15 13 11 9 7 5 2 3 1 0 Switch Frame n 14 12 10 8 6 4 15 13 11 9 7 5 Switch No Switch Frame n Frame n+1 2 0 14 12 10 8 6 4 3 1 13 14 9 10 5 6 2 0 1 2 Switch No Switch No Switch Frame n Frame n+1 Frame n+2 12 13 15 14 8 9 11 10 4 5 7 6 0 1 3 2 Switch No Switch No Switch No Switch Frame n Frame n+1 Frame n+2 Frame n+3 Figure 32.
15 16 13 11 9 14 12 10 8 6 4 7 31 29 27 25 23 21 5 3 1 2 Switch 1 17 Switch 2 Frame 1 Frame 2 19 47 45 61 43 41 39 57 53 37 35 33 49 Switch 3 Frame 3 Frame 4 Figure 33. Node Numbering for an SP System 3.5.2 Procedure to Get the Jack Number Following are the steps required to get the jack number: 1. From the SP control workstation, determine the dependent node’s number by entering SDRGetObjects DependentNode node_number.
# splstdata -s | grep -p primary switch_part topology primary arp switch_node number filename name enabled nos._used ------------------------------------------------------------------------1 expected.top.an sp21n07 yes no # In this case, the primary node host name is sp21n01. 4. Log into the primary node by entering telnet node_hostname, where node_hostname is the host name of the primary node. 5. From the primary node, enter pg /var/adm/SPlogs/css/out.top. 6. In the out.
• The SP Switch Router card connected to port J31 of SP Switch A2 is node number 25. • The SP Switch Router card connected to port J31 of SP Switch A3 is node number 41. • The SP Switch Router card connected to port J15 of SP Switch A1 is node number 16. SP system A Frame 1 Frame 2 J7 J23 J7 J15 J31 SP Switch A1 J31 gt000 Node 9 Frame 3 J23 J7 J15 J31 SP Switch A2 gt010 Node 16 gt020 Node 25 J23 SP Switch A3 J15 gt030 Node 41 SP Switch Router Figure 34.
3.7.1.1 Overview of the Steps to Configure a Media Card A detailed discussion of these steps follows this overview. 1. Edit the SNMP configuration file and start the SNMP daemon on the SP Switch Router. 2. Assign an IP address and other parameters to the SP Switch Router Adapter interface. There are two ways to configure these parameters: • We recommend using the procedures documented in the "Managing Extension Nodes" chapter of the RS/6000 SP: Administration Guide Version 2 Release 4, GC23-3897.
• As an alternative, you can log on to the SP Switch Router and use a UNIX editor to enter the parameters in the /etc/grdev1.conf file. 5. Reboot the SP Switch Router unit so that the altered configuration files are installed and used. Remember that you must use grwrite -v to preserve the modifications of files in /etc, before a reboot. Details about each step are provided in the next sections. 3.8 Step 1. Check SNMP in the SP Switch Router System Check the /etc/snmpd.
3.9 Put SNMP Changes into Effect To have changes to /etc/snmpd.conf take effect, kill snmpd. It will be automatically restarted. Log in as root, find the snmpd PID (process ID), and then kill the SNMP daemon, as follows: # ps -ax | grep snmpd 326 00- S 0:00.17 snmpd /etc/snmpd.conf /var/run/snmpd.NOV # kill 326 # Jun 13 16:13:18 grf16 mib2d[397]: mib2d: terminated by master agent Jun 13 16:13:18 grf16 root: grstart: snmpd exited status 143; restarting.
Enter Extension Node Information Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] [grf16.msc.itso.ibm.com] [spenmgmt] [03] [grf16.msc.itso.ibm.
COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. The endefadapter command has completed successfully. • Command: smitty annotator Topology File Annotator Type or select values in entry fields. Press Enter AFTER making all desired changes. Input Topology File Name Output Topology File Name Save Output File to SDR [Entry Fields] [/etc/SP/expected.top.1nsb.0isb.0] [/etc/SP/expected.top.annotated] [yes] + /etc/SP/expected.top.
• Command: smitty manage_extnode Extension Node Management Type or select values in entry fields. Press Enter AFTER making all desired changes. Action to be performed on the extension node * Node Number [Entry Fields] reconfigure [4] + # COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below.
3.10.2 Method 2: Edit /etc/grifconfig.conf - Optional Edit the /etc/grifconfig.conf file to assign an IP address to each logical SP Switch Router interface. You can also provide other information about the logical IP network to which that interface is physically attached. Each logical interface is identified in /etc/grifconfig.
Internet address The Internet address is the 32-bit IP address for the specified logical interface. The address is in standard dotted-decimal (octet) notation: xxx.xxx.xxx.xxx. Netmask Netmask is the 32-bit address for the logical IP network on the physical network to which the specific SP Switch Router or media card physical interface is attached. The netmask is entered in standard dotted-decimal (octet) notation. If no destination/broadcast address is supplied, a netmask is required.
Default MTUs for framing protocols are: • Frame Relay: 4352 bytes • HDLC: 4352 bytes • Point-to-Point Protocol: 1496 bytes MTU discovery facility MTU sizes are generally selected at the host end of the route. This is accomplished by turning on the host’s MTU discovery facility and allowing the host to send packets. The MTU discovery facility operates by default on the SP Switch Router. AIX4.3.1 provides MTU discovery; however, you have to enable it with the /etc/no command.
Nevertheless, check the file /etc/grdev1.conf. It must contain an entry for the slot in which the media card is installed. As we have our card in slot 3, the entry looks as follows: # CARD 3 Interface 0 # 2.21.4.1.1.1 "03" # Node Name 2.21.4.1.1.2 4 # Node Number 2.21.4.1.1.3 "00:00:00:01:00:00:00:06:00:01" # Switch Token 2.21.4.1.1.4 2 # Switch ARP 2.21.4.1.1.5 3 # Switch Node Number 2.21.4.1.1.6 x192.168.14.4 # IP Address 2.21.4.1.1.7 x255.255.255.0 # Net Mask 2.21.4.1.1.8 1024 # Max Link Pckt Len.
To save an alternate configuration on the internal flash based upon the currently running configuration on the internal flash device, use grsnapshot -si -di=revision,version. For more information about these commands, see GRF Reference Guide 1.4, GA22-7367. 3.14 Verify an SP Switch Router Adapter Card on the Router This section describes tools available with the SP Switch Router system software to check out newly installed media cards.
2. Enter a ping command. Specify the appropriate media card by its chassis slot number; for example, to act on the SP Switch Router Adapter media card in slot 3, enter ping -c4 -P grid 3. This is what you see when the media card responds: # ping -c4 -P grid 3 GRID ECHO 3 (0:0x3:0): 68 bytes from 0:0x3:0: 68 bytes from 0:0x3:0: 68 bytes from 0:0x3:0: 68 bytes from 0:0x3:0: 64 data bytes, 3 packets time=0.619 ms time=0.498 ms time=0.640 ms time=0.
3.14.3 Reset Media Card Using grreset Use the grreset command to reset a media card from the UNIX prompt: 1. Log in as root on the SP Switch Router. 2. Enter the grreset command. Specify the appropriate media card by its chassis slot number. To reset all the media cards, enter grreset all; to reset the media cards in slot 0, enter grreset 0; to reset the card in slot 4 and dump its memory, use grreset -D 4; to reset the card in slot 4 and return debug information, enter grreset -d 4.
Below is an actual example: # grstat -w70 all gt030 gt030 ipstat count description 11095886 total packets received 51 packets dropped 3678330 packets forwarded normally 4 packets forwarded locally to card 1214 packets handled by the card ipdrop last last count source addr dest addr reason 3 192.168.14.6 192.168.13.15 TTL expired 48 192.168.14.15 192.168.13.
one of the following actions to bring the SP Switch Router Adapter card online: • A switch initialization • An unfencing sequence • Another Switch management sequence The appropriate action depends on what state the SP system is in with respect to the dependent node. For example, if no Estart command has been issued to reinitialize the SP Switch since the dependent node (the SP Switch Router Adapter) was installed, then an Estart command is needed.
Each SP Switch Router Adapter media card is considered a dependent node for the SP System. Each dependent node has a node_number and other configuration and status information that is unique to that dependent node. 3.15.1.1 Procedure The following steps might give you guidance in solving some of the most common connectivity problems: 1. Check the SP Switch cable for obvious problems such as a loose or disconnected connector, missing shielding or bent pins. 2.
Maintenance Information Manual Dependent Node MAP, return to that procedure. For more information about configuration as related to the SP, see RS/6000 SP: Administration Guide Version 2 Release 4, GC23-3897 and RS/6000 SP: Command and Technical Reference Version 2 Release 4, GC23-3900. For additional information on troubleshooting your configuration, see RS/ 6000 SP: Diagnosis and Messages Guide Version 2 Release 4, GC23-3899.
Installation and Configuration 104
Chapter 4. Configuration of IP-Forwarding Media Cards This chapter covers the installation and configuration of selected IP Forwarding media cards in an SP Switch Router. For detailed information refer to GRF Configuration Guide 1.4, GA22-7366. 4.1 Ethernet 10/100Base-T Configuration This section provides the information needed to configure the Ethernet 10/100Base-T media card. It comes in two flavors, one with four ports and the other with eight ports available.
g e 0 x y 1st: always "g" for GRF 2nd: media type, e (Ethernet) 3rd: chassis number, always "0" (zero) 4th: 5th: slot number in hex logical interface number in hex Figure 36. Components of the Ethernet Interface Name The interface name is used in the /etc/grifconfig.conf file to specify an IP interface. Interface 7 on the Ethernet card in slot 3, for example, would be added to this file as: #name ge037 address netmask xxx.xxx.xxx.xxx 255.255.255.
• Change run-time binaries • Change dump variables 3. Load profile Global executable binaries are set in the Load profile in the hw-table field. These only change when you want to execute new run-time code in every Ethernet card. If you want to change the run-time code in one Ethernet card (per interface), make the change in the Card profile, in the load field. 4. Dump profile Global dump settings are in the Dump profile. These settings are usually changed only for debug purposes.
#name ge070 #ge071 #ge072 #ge073 #ge074 #ge075 #ge076 #ge077 address 10.20.30.1 10.20.30.1 10.20.30.1 10.20.30.1 10.20.30.1 10.20.30.1 10.20.30.1 10.20.30.1 netmask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 broad_dest - arguments mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 mtu 1500 4.1.5 Specify Ethernet Card Parameters As already mentioned, modifying the following profiles is optional.
if-config: Ethernet interface configuration. Enumerated field, values: autonegotiate: autonegotiate 10-half: 10 BaseT Half Duplex 10-full: 10 BaseT Full Duplex 100-half: 100 BaseT Half Duplex 100-full: 100 BaseT Full Duplex super> set if-config = 100-full super> write CARD2/ written super> quit # The configuration of the Ethernet card is now completed. Issue grwrite -v and grreset . Communication between the GRF’s Ethernet card and attached devices should work now.
you see the output for all eight. The input port side is reported on first. maint 5 -to return GRF switch statistics. maint 7 -to clear the current collected statistics. maint 8 -to display the ARP table for one interface or, if no interface is specified, for all interfaces. 4.2 ATM OC-3c Configuration This section provides information needed to configure the ATM OC-3c media card. The GRF can be configured in point-to-point or point-to-multipoint ATM topologies with either switches or hosts.
See Figure 38 for the naming conventions of an ATM interface. g a 0 x yz 1st: always "g" for GRF 2nd: 3rd: media type, a (ATM) chassis number, always "0" (zero) 4th: slot number in hex 5th-6th: logical interface number in hex Figure 38. Components in the ATM OC-3c Interface Name Virtual Circuits A virtual circuit (VC) exists between two ATM devices. It is the point-to-point connection between them and is of no significance to other ATM devices.
VPIs 0 through 15 are available for configuration use. VPIs are assigned in the /etc/gratm.conf file with regard to their VCI. VCIs VCIs name VCs. VCIs are also assigned in the /etc/gratm.conf file. On VPI 0, VCI 0 through VCI 32767 can be used; on VPIs 1-15, VCI 0 through VCI 511 can be used. Note: Virtual circuits 0-31 on each VPI are reserved for signaling. Permanent Virtual Circuits Permanent virtual circuits (PVCs) are created statically. PVCs are configured in /etc/gratm.conf.
4.2.2 Installing Configurations or Changes In the command line interface (CLI), use set and write commands to install configuration parameters. To save the /etc configuration directory, use grwrite -v. Additionally, when you enter configuration information or make changes, you must also reset the media card with the command grreset for the change to take place. 4.2.3 Configuration Files and Profiles Following are the steps to configure an ATM card.
Traffic_Shape name=high_speed_high_quality \ peak=155000 sustain=155000 burst=2048 qos=high Traffic_Shape name=low_speed_high_quality \ peak=15500 qos=high Interface ga010 traffic_shape=high_speed_high_quality Interface ga0180 traffic_shape=low_speed_high_quality PVC ga010 0/132 proto=ip traffic_shape=high_speed_high_quality PVC ga0180 0/134 proto=ip traffic_shape=low_speed_high_quality 4. Load profile (optional). Global executable binaries are set in the Load profile in the hw-table field.
interface basis. This field is also used to specify ISO when an ISO address is being added to an interface’s IP address. Specify the MTU value as mtu xxxx. Leave the arguments field blank if you are not using it. The following excerpt from our /etc/grifconf.conf file shows the format of an entry: # name ga010 ga0180 address 10.1.1.1 10.1.2.1 netmask 255.255.255.0 255.255.255.0 broad_dest 10.1.2.
• Interface section Define the traffic shaping profile for the logical interface to which the media card’s PVCs are assigned. • PVC section Specify characteristics for each PVC, including: • Assigned logical interface name • VPI/VCI • Protocol supported • Whether AAL is used • Assigned traffic shaping profile (only if it would be different from the profile given previously to the logical interface in the Interface section) Templates of these configuration files are in GRF Reference Guide 1.
The following message is returned along with the changed prompt: Current port card is 3 GR 3> . • To leave any maint prompt and return to the shell, enter quit. Following are just a few maint commands we have found useful; of course, your experiences may vary. To see the list of maint commands for the receive side, enter maint 1; to see the list of maint commands for the transmit side, enter maint 101. The maint 3 command gives you useful options for looking at a variety of active interfaces.
4.2.8 Using grrt to Display the Route Table Use the grrt -S -p command to display the current contents of the ATM OC-3c card’s route table. The following is an actual screen shot: # grrt -S -p1 default 0.0.0.0 10.1.1.0 10.1.1.1 10.1.1.255 10.1.2.1 10.10.1.0 10.10.1.13 10.10.1.255 127.0.0.0 127.0.0.1 192.168.4.0 192.168.13.0 192.168.14.0 192.168.14.4 192.168.14.255 224.0.0.0 224.0.0.0 224.0.0.0 255.255.255.255 # 118 255.255.255.255 255.255.255.0 255.255.255.255 255.255.255.255 255.255.255.255 255.
4.2.9 Using grstat to Display GRF Statistics Use the grstat -w70 all command to display the current statistics of the ATM OC-3c card’s IP stack.
Logical Interfaces Physical Interface 0 (center) 0-ff (range) VPI 0 1-3 VCI Total # of active VCs 0-1024 0-127 1408 Figure 40. ATM OC-12c Physical and Logical Interfaces Physical Interfaces The ATM OC-12c media card supports one physical interface. It supports the assignment of 220 logical interfaces out of a range of 256. Virtual Circuits The ATM OC-12c media card supports up to 1408 active VCs. Virtual Paths VPIs 0 through 3 are available for configuration use.
1. Identify each logical interface. Edit /etc/grifconfig.conf, to identify each logical interface by assigning: • • • • • An IP address The GRF interface name A netmask, as required A destination or broadcast address, as required An MTU, if needed 2. Configure PVCs and SVCs in /etc/gratm.conf. Edit the file /etc/gratm.
It might be useful to give a short overview of possible FDDI connection options, namely SAS, DAS, optical bypass and dual homing, and show a picture explaining these scenarios. Single Attach (SAS) Single attach FDDI interfaces can be either master (M) ports or slave (S) ports. They require a cable with a corresponding master or slave connector. Single attach cables have an M connector on one end and an S connector on the other. With no key installed, both M and S connectors fit the FDDI interface.
A0 A Station 1 A FDDI B0 B Station 2 B B A A B B A A B Logical ring A1 B1 A A Station N... B ... B A Station 3 A B B Figure 42. A/B Connectors for DAS Interfaces Configuring SAS versus DAS Only the top or bottom pair of FDDI interfaces can be set to dual attach. Interfaces 1 and 2, for example, must not be paired. It is recommended to set unused FDDI interfaces to single in the Card profiles (which is the default anyway).
super> list ports 0 port_num = 0 cisco-hdlc = { off on 10 3 } fddi = { single off } sonet = { "" "" 1 sonet internal-oscillator 0 207 } hssi = { 0 16-bit } ether = { autonegotiate } hippi = { 1 32 no-mode 999999 4 incremental 5 300 10 10 03:00:0f:c0 disabled super> super> list fddi single-dual = single optical-bypass = off super> As you can see, the single-dual field is preset to single and the optical-bypass is preset to off.
super> write CARD/0 written super> Optical bypass Optical bypass capability has to be provided externally. The FDDI face plate has a six-pin DIN connector to directly attach a single bypass switch. As shown in Figure 44, two bypass switches can be attached with the an Y-cable adapter. The Y-cable is required to reconcile control pin assignments between the GRF and the external switch module.
Configure the FDDI media card for dual attach, but use two single attach (SAS) cables to connect to two M ports. As shown in Figure 45, the M ports can be on either one or two FDDI concentrators on the ring. A0 FDDI B0 M A1 M Concentrator Ring B1 A0 M Concentrator 2 B0 FDDI Ring A1 B1 M Concentrator 1 Figure 45. Dual Homing Configurations 4.4.
• By a logical interface number assigned after the SAS/DAS settings are numbered (used in the /etc/grifconfig.conf file) • By a unique IP address assigned to each logical interface Figure 46 shows files where various numbers are used to configure the interfaces on an FDDI media card. Card face plate numbers SAS/DAS options in Card profile Logical interface numbers in grifconfig.
Port FDDI media card SNMP A0 0 1 A1 1 2 B0 2 3 B1 3 4 Figure 47. Physical Interface Numbering on the FDDI Media Card The diagram shows physical interface numbering to be 0-based (0–3), whereas SNMP numbering is 1-based (1–4). 4.4.4 GRF Interface Name The GRF interface name has five components that describe an individual FDDI interface in terms of its place on the media card and in the GRF router.
Edit /etc/grifconfig.conf to identify each logical interface by assigning: • An IP address • The GRF interface name • A netmask, as required • A destination or broadcast address, as required • An MTU, if needed 2. Specify FDDI card parameters in the Card profile. All but the first two are optional and default to the most common settings, so normally you should be just fine omitting this step. • Specify SAS and DAS settings as single or dual, with single being the default.
The arguments field is also used to specify ISO when an ISO address is being added to an interface’s IP address. Specify the MTU value as mtu xxxx. Leave the arguments field blank if you are not using it. The following excerpt from our /etc/grifconf.conf file shows the format of an entry: #name gf000 gf001 gf002 address 10.2.1.15 10.3.1.16 10.4.1.17 netmask 255.255.255.0 255.255.255.0 255.255.255.
This completes the procedure to configure FDDI cards, and as with the ATM card, we would like to introduce some of the maint commands we found to be useful. 4.4.9 Some maint Commands for the FDDI Media Card The maint commands display a range of information about the FDDI media card. The FDDI card has an individual processor for the transmit and receive side, and two sets of maint commands.
4.4.10 Using grrt to Display the Route Table Use the grrt -S -p command to display the current contents of the FDDI card’s route table, as follows: # grrt -S -p0 default 0.0.0.0 10.1.1.0 10.1.1.1 10.1.1.255 10.1.2.1 10.10.1.0 10.10.1.13 10.10.1.255 127.0.0.0 127.0.0.1 192.168.4.0 192.168.13.0 192.168.14.0 192.168.14.4 192.168.14.255 224.0.0.0 224.0.0.0 224.0.0.0 255.255.255.255 132 255.255.255.255 255.255.255.0 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.0 255.255.255.255 255.255.
4.4.11 Using grstat to Display GRF Statistics Use the grstat -w70 all command to display the current statistics of the FDDI card’s IP stack. The following is an actual screen shot: # grstat all gf001 ipstat count 2958246 3 2958226 17 ipdrop gf001 description total packets received packets dropped packets forwarded normally packets handled by the card count 3 icmperr last source addr 10.10.1.10 last count type icmpin count icmpout count 3 last code last dest addr reason 192.168.14.
these modes. Hosts must pass on the appropriate information for the GRF media cards and other HIPPI devices to operate in the desired way. HIPPI offers many configuration options. The ANSI HIPPI standards and RFCs describe implementation details, that support source routing, logical addressing, IP routing, and raw (switch) mode operations. 4.5.1.1 Connection Processing The GRF processes connections; it does not process data. It accepts data and establishes a connection point to which it can transfer data.
header. The media card reads the header only if told to do so by information in the HIPPI I-field. If the I-field tells the card to read the IP header, then an IP connection is established. 4.5.1.3 How the I-field is Used The I-field tells the GRF how to process the connection, and where to send the data. Figure 49 shows the basic structure of a HIPPI I-field. Connection control information is in the leftmost 8 bits, addressing takes up the other 24 bits.
01 Logical Address When PS is set to 01, that is, logical address, the host does not know or want to specify the actual physical route to the target endpoint. The host supplies a logical address for the endpoint host. In this case, all switches and the GRF must be programmed to route the connection. The structure of the I-field is different when logical addressing is used. The 24-bit destination addresses are divided into two 12-bit fields.
4.5.1.6 Direction Bit HIPPI hosts set the direction bit (D). This bit determines how a switch or router reads the 24-bits of destination address information. Figure 49 on page 135 and the previous descriptions of source routing and logical addressing have the destination address information organized as if the host has set the destination bit to 0.
of this address to slot 64 in the file /etc/grlamap.conf indicates the IP connection to the receiving media card and causes it to read the IP header. The logical address 0xfc0 is preset as a default in the logical address table. This logical address maps to the nonexistent slot 64. HIPPI cards are programmed to accept a connection and extract the destination IP address from the first datagram’s header when they look up an address that points to slot 64.
Section 7.3, “HIPPI Backbone Connection” on page 227, describes the steps to configure the GRF’s HIPPI media card to do IP forwarding, so you have to refer to the Ascend documentation if you need to set up a different configuration. 4.5.3 Physical and Logical Interfaces The HIPPI media card provides a single duplex attachment and operates at a speed of 100 MB/s. It requires a pair of 100-pin copper cables to connect to another HIPPI device.
4.5.4 Configuration Files and Profiles The following are the steps to configure HIPPI cards. For detailed information, see GRF Configuration Guide 1.4, GA22-7366. 1. Identify each logical interface. Edit the /etc/grifconfig.conf to identify each logical interface by assigning: • An IP address • The GRF interface name • A netmask, as required • A destination or broadcast address, as required • An MTU, if needed 2. Check the I-field shift in the System profile.
4.5.5 Installing Configurations or Changes In the command line interface (CLI), which is the working environment on the GRF with the super> prompt, use the set and write commands to install configuration parameters onto the media card. If you apply changes to files in the /etc directory, do not forget to issue grwrite -v to have these changes written to flash, so that they are still in effect after a reboot of the GRF.
4.6 Configuring Bridging This Chapter describes the GRF bridging implementation and provides configuration information. 4.6.1 GRF Bridging Implementation The GRF implements IEEE 802.1d transparent bridging on GRF Ethernet and FDDI interfaces, and on ATM OC-3c interfaces using RFC-1483 encapsulated bridging over PVCs. Transparent bridging provides a mechanism for interconnecting stations attached to physically separate Local Area Networks (LANs) as if they are attached to a single LAN.
4.6.2 Simultaneous Routing and Bridging Ascend’s transparent bridging does not preclude the use of IP packet routing on the same physical interface. Bridging as well as IP version 4 (IPv4) routing can both be enabled on the same physical interface. In this circumstance, the GRF exchanges traffic between bridging domains and routing domains that exist on the same physical media. A GRF interface may simultaneously bridge layer-2 frames and route layer-3 packets.
4.6.4 Interoperability The following table gives an overview of the GRFs interoperability features. FDDI Frame forwarding is compatible with any station sending and receiving FDDI LLC frames. Ethernet Frame forwarding is compatible with any station using either DIX Ethernet or IEEE 802.3 frames. ATM OC-3c Frame forwarding is compatible with any remote bridge using RFC-1483 bridging encapsulation.
A frame may be too large for the maximum transmission unit (MTU) of the sending GRF interface. One example is when forwarding a 4500-byte frame from FDDI to an Ethernet interface with an MTU of 1500 bytes. The GRF bridge will attempt to break such a frame into fragments that will fit the sending interface. This is possible if the frame contains an IP datagram; then the GRF may use the fragmentation rules of IP to split the frame. Otherwise, the GRF must drop the frame. 4.6.
4.6.9.3 Editing Utility – Bredit The bredit utility is used to access and edit the /etc/bridged.conf configuration file. At this point, bredit runs a script in which you are asked if you want to make the changes permanent. The script also gives you the option of signaling bridged to reread the updated file immediately. When this option is taken, bridged restarts as if it were stopped and restarted for the first time.
Interface Port ID Con State Cost Cost --------- ------- --- ---------- ----- ----gf000 128 1 Yes Forwarding 10 0 gf001 128 2 Yes Forwarding 10 0 gf002 128 3 Yes Forwarding 10 0 gf003 128 4 Yes Forwarding 10 0 Bridge Group bg1 Spanning Tree: Enabled Designated Root: 32768 00:c0:80:84:8c:eb Bridge ID: 32768 00:c0:80:96:38:68 Bridge ----------------------[me] [me] [me] [me] Port ------128 1 128 2 128 3 128 4 Root Port: ga010, Root Path Cost: 10 Topology Change Detected: No Root Max Age: 20, Hello Time: 2, F
Flags: 0xb043 up broadcast running link0 link1 multicast Bridging media: fddi bpdu MAC address: 0:c0:80:89:2d:f5 Bridge group name: bg1 Flags:(0x43) up broadcast running Ports: 2 Port ga010: State (0x1) Running Flags: 0xa043 up broadcast running link1 multicast Bridging media: ethernet fddi bpdu Max MTU: 4352 MAC address: 0:c0:80:f8:43:0 Port ga0180: State (0xf) Blocking Flags: 0xa043 up broadcast running link1 multicast Bridging media: ethernet fddi bpdu Max MTU: 4352 MAC address: 0:c0:80:f8:44:80 4.6.
If you are going to configure an encapsulated bridge on an ATM circuit, edit the /etc/gratm.conf file to create a PVC on the ATM OC-3c logical interface. 5. Specify ARP service in the /etc/grarp.conf file, if needed. 4.6.11.1 Starting Bridged The grstart program regularly checks for the presence of /etc/bridged.conf and starts the bridged daemon when the file is found. In the UNIX shell, copy the template for the bridging configuration file to /etc/bridged.conf: # cp /etc/bridged.conf.template /etc/bridged.
4.6.11.2 Creating Bridge Groups in bridged.conf The only required parameter is the list of FDDI, ATM or Ethernet interfaces you are assigning to the group. The format of the group list is: bridge_group bgA { port interface_name; }; where interface_name is in the standard GRF interface name format gx0yz that uniquely describes a logical FDDI, Ethernet, and ATM OC-3c interface (see Figure 51).
• VC-Based Multiplexing (RFC 1483, section 5) When LLC Encapsulation is used, a single PVC is configured to carry all bridged traffic. The same PVC can also carry nonbridged traffic such as routed IP datagrams. When VC-Based Multiplexing is used, multiple PVCs are defined for the logical interface. Each PVC carries a specific type of traffic. For example, one PVC carries Ethernet while another carries FDDI. Configuration in gratm.
A bridging PVC is assigned a protocol value. This value must be consistent with the bridging method defined for the logical interface. Bridging PVCs are assigned either of the following protocol values: 1. proto=llc,bridging,xxxx This type of PVC is used for logical interfaces defined with bridge_method=llc_encapsulated, as well as logical interfaces not used for bridging. This PVC uses LLC encapsulation for each Protocol Data Unit (PDU).
Following are some PVC configuration examples: LLC Encapsulated: # Traffic shape Traffic_Shape name=high_speed_high_quality peak=155000 sustain=155000 \ burst=2048 qos=high # Logical interface Interface ga030 traffic_shape=high_speed_high_quality \ bridge_method=llc_multiplexed # PVC PVC ga030 0/32 proto=llc,bridging Note: The single PVC defined here can carry any kind of bridged frame, as well as routed IP traffic.
PVC ga030 0/32 proto=vcmux_bridge,ether PVC ga030 0/33 proto=vcmux_bridge,ether_fcs PVC ga030 0/34 proto=vcmux_bridge,bpdu # PVC for IP (RFC 1577) PVC ga030 0/35 proto=llc Note: IP routed traffic is transmitted on its own PVC. If the separate IP PVC were not defined, then routed IP datagrams would be encapsulated as Ethernet frames. 4.6.11.5 Configuration for ARP Service - grarp.conf If needed, supply IP-to-physical address mapping information for ARP service. Put an entry into /etc/grarp.
4.6.13 Bridging FDDI Transparent bridging is especially useful for day-to-day customer environments, where several FDDI backbones meet in the computing center and must be connected to an SP. Up to now, the SP was connected to the FDDI switch or router with one or two FDDI adapters, thus causing a bottleneck. Now, with the GRF connecting directly to the SP Switch, the FDDI backbones can deliver their data at maximum speed. See Section 5.1.4.
156 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Chapter 5. Single RS/6000 SP and Single SP Switch Router This section provides several sample configurations that are possible with a single RS/6000 SP and a single SP Switch Router. Sample configurations range from using the SP Switch Router as a conventional high performance router up to the connection of two SP partitions, allowing high-speed Switch communication between the partitions. 5.
Configuration assumptions: • The SP Switch Router Ethernet media card has been installed according to Section 4.1, “Ethernet 10/100Base-T Configuration” on page 105 and works properly. • The SP Switch Router Adapter card has been installed according to Section 3.7, “Step-by-Step Media Card Configuration” on page 86 and works properly. • The SP Switch Router Adapter card and SP processor node Switch adapters are in the same IP subnet.
Table 14. Configuration of SP Switch - Ethernet Connection Adapter IP Address Ethernet interface in F50 (en0 on ent0) 10.20.30.50 SP Switch Router Ethernet media card (port 1) 10.20.30.1 SP Switch Router Adapter card 1 192.168.14.4 SP processor nodes in SP21 192.168.14.1 - 192.168.14.15 To successfully run this configuration, no routes need to be set on the SP Switch Router. The F50 and the processor nodes in SP21 require attention, though.
-mtu 1500 10.20.30.1 2. Check for correct routing entry: (0)f50:/ 26$ netstat -rn Routing tables Destination Gateway Flags Refs Use If Route Tree for Protocol Family 2 (Internet): default 9.12.1.30 UG 4 288844 9.12.1/24 9.12.1.50 U 24 41728 10.1.1/24 10.1.1.3 U 0 0 10.20.30/24 10.20.30.50 U 1 0 127/8 127.0.0.1 U 5 753 192.168.14/24 10.20.30.1 UG 0 2889408 Route Tree for Protocol Family 24 (Internet v6): ::1 ::1 UH 0 (0)f50:/ 27$ PMTU Exp Groups tr0 tr0 at1 en0 lo0 en0 1500 - 0 lo0 16896 - 3.
(0)f50:/ 29$ ping 192.168.14.15 PING 192.168.14.15: (192.168.14.15): 56 data bytes 64 bytes from 192.168.14.15: icmp_seq=0 ttl=254 time=0 ms 64 bytes from 192.168.14.15: icmp_seq=1 ttl=254 time=0 ms 64 bytes from 192.168.14.15: icmp_seq=2 ttl=254 time=0 ms ^C ----192.168.14.15 PING Statistics---3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms (0)f50:/ 30$ On the chosen nodes in SP21, ping the ATM interface of the F50: root@sp21n01:/ ping f50 PING f50: (10.20.30.
0)f50:/itso/space 32$ ftp 192.168.14.1 Connected to 192.168.14.1. 220 sp21n01 FTP server (Version 4.1 Tue Mar 17 14:00:13 CST 1998) ready. Name (192.168.14.1:root): root 331 Password required for root. Password: 230 User root logged in. ftp> bin 200 Type set to I. ftp> put bos.obj.ssp.itso /dev/null 200 PORT command successful. 150 Opening data connection for /dev/null. 226 Transfer complete. 299878400 bytes sent in 31.95 seconds (9166 Kbytes/s) local: bos.obj.ssp.
• If ARP is disabled on the SP Switch network, the IP addresses assigned to the nodes must be determined by the Switch node numbers. Refer to PSSP Planning, Volume 2, Control Workstation and Software Environment for details. Note: The SP Switch Router Adapter card will not properly forward IP data to nodes assigned with an IP address that is in another subnet. Configuration: To establish this scenario, the FDDI interface of node 10 in SP21 was connected to the SP Switch Router FDDI media card, port A0.
though. To add the needed routing information and check for proper work, follow these steps: 1. On node 10 in SP21, add the following route to the switch network of SP2: route add -net 192.168.13 -netmask 255.255.255.0 -mtu 4352 10.2.1.2 2. Check for correct routing entry: root@sp21n10:/ netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2 (Internet): default 192.168.4.137 UG 0 482 en0 10.2.1/24 10.2.1.1 U 1 22 fi0 127/8 127.0.0.
6. On the CWS of SP2 check if the SP Switch Router Adapter card is configured. See if the SP Switch Router Adapter card shows up green in perspectives or enter SDRGetObjects switch_responds. Use Eunfence if needed. 7. Issue some ping commands to check the connection: On the chosen SP2 nodes, ping the FDDI interface of node 10 in SP21, for example: root@sp2n09:/ ping 10.2.1.1 PING 10.2.1.1: (10.2.1.1): 56 data bytes 64 bytes from 10.2.1.1: icmp_seq=0 ttl=255 time=0 ms 64 bytes from 10.2.1.
BRL, and ported to AIX by Prof. Peter Haas, University of Stuttgart). tsock is a program that uses the UltraNet socket emulation library to perform numerous network exercises, among them to measure the pure network performance by eliminating any hard disk or processor load influence on the data transfer rate by sending data packets directly from memory to memory.
5.1.3 SP Switch - ATM Connection This scenario might be used quite often to attach a single computer with an ATM interface to the SP Switch of an SP system. This could, for example, be an RS/6000 model S70 acting as an ADSM server or as a database server in an SAP or BAAN environment. It could, as well, be a connection to another already existing ATM Switch. Configuration assumptions: • An SP Switch Router ATM media card has been installed according to Section 4.
F 50 80 ATM SP Switc h Router Adapter card 1 SP Switch GRF 1600 SP node SP node SP node SP21 Figure 55. SP Switch - ATM Connection Table 16 shows the IP addresses used in our configuration. Table 16. Configuration of SP Switch - ATM Connection Adapter IP Address ATM interface in F50 (at0 on atm0) 10.1.2.3 SP Switch Router ATM media card (port 80) 10.1.2.1 SP Switch Router Adapter card 1 192.168.14.4 SP processor nodes in SP21 192.168.14.1 - 192.168.14.
of the lack of an ARP server; signaling protocols should only matter with SVCs and not with PVCs. 3. On the F50, use smitty chg_atm, select the ATM device and change the field SVC UNI Version from auto_detect to uni3.0: Change / Show Characteristics of an ATM Adapter Type or select values in entry fields. Press Enter AFTER making all desired changes.
5. Have smitty carry out its work, exit smitty and then run smitty mkatmpvc: Add a PVC for IP over an ATM Network Type or select values in entry fields. Press Enter AFTER making all desired changes. PVC Description (Optional) * VPI:VCI Network Interface Destination IP Address Automatically Discover Destination IP Address LLC Encapsulation [Entry Fields] [F50toGRF] [0:134] [at0] [] yes yes + + In the optional PVC Description field, do not use blanks or underscores.
(0)f50:/ 15$ ping 10.1.2.1 PING 10.1.2.1: (10.1.2.1): 56 data bytes 64 bytes from 10.1.2.1: icmp_seq=0 ttl=255 64 bytes from 10.1.2.1: icmp_seq=1 ttl=255 64 bytes from 10.1.2.1: icmp_seq=2 ttl=255 ^C ----10.1.2.1 PING Statistics---3 packets transmitted, 3 packets received, round-trip min/avg/max = 0/0/0 ms (0)f50:/ 16$ time=0 ms time=0 ms time=0 ms 0% packet loss To add the needed routing information, follow these steps: 1. On the F50, add the following route to the nodes in SP21: route add -net 192.168.
root@sp21n01:/ netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2 (Internet): default 192.168.4.137 UG 1 7410 en0 10.1.2/24 192.168.14.4 UG 0 3449576 css0 9180 127/8 127.0.0.1 U 8 757 lo0 192.168.4/24 192.168.4.1 U 13 1132000 en0 192.168.13/24 192.168.14.4 UG 1 13501009 css0 9180 192.168.14/24 192.168.14.
If these ping commands fail, check routing settings again. If everything is as it should be, try to ping the SP Switch Router ATM media card or the SP Switch Router Adapter card to which part is failing: ping 192.168.14.4 (on chosen SP21 processor nodes) ping 10.1.2.1 (on F50) If any errors occur, check cabling, the configuration of SP Switch Router media cards (See Section 3.7, “Step-by-Step Media Card Configuration” on page 86 and Section 4.
An ATM adapter establishes a duplex connection to its partner, so the 16.5 MB/s write throughput should be accompanied by another 16.5 MB/s read throughput. To prove this, we started two ftp put commands from the same SP21 node. At the same time we started two ftp put commands an the F50 and observed an aggregate throughput over the ATM adapter of up to 28 MB/s, with the CPU of the SP node nearly 80% busy and the F50 100% busy. 5.1.4 SP Switch - FDDI Connection (Distinct FDDI Networks) 5.1.4.
page 175 and Table 17 on page 175. The netmask for all interfaces is 255.255.255.0. node 9 node 10 A0 A1 B0 node 11 FDDI SP Switch Router Adapter c ard 1 B1 SP Switch GRF 1600 SP node SP node SP node node 12 SP21 Figure 56. SP Switch - FDDI Connection Table 17 shows the IP addresses used in our configuration. Table 17. Configuration of SP Switch - FDDI Connection Adapter IP Address FDDI interface in node 9 10.5.1.9 FDDI interface in node 10 10.3.1.10 FDDI interface in node 11 10.4.1.
To successfully run this configuration, all four ports of the SP Switch Router FDDI media card have to be assigned IP addresses in different subnets. Otherwise, only port A0 will be activated. Note: Every port of the SP Switch Router FDDI media card has to be assigned to a different subnet when bridging is not configured (see Section 5.1.4.2, “SP Switch - FDDI Connection with Bridging” on page 179). In this sample configuration no routes need to be set on the SP Switch Router.
3. On the nodes in SP21 that are supposed to communicate with the different FDDI backbones, add the necessary routes: route route route route add add add add -net -net -net -net 10.2.1 10.3.1 10.4.1 10.5.1 -netmask -netmask -netmask -netmask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 -mtu -mtu -mtu -mtu 4352 4352 4352 4352 192.168.14.4 192.168.14.4 192.168.14.4 192.168.14.4 The -mtu parameter is optional but should be set to ensure optimal packet size on this route. 4.
/root netstat -in Name Mtu Network de0 1500 de0 1500 de0 1500 192.168.4 rmb0 616 rmb0 616 lo0 1536 lo0 1536 127 lo0 1536 gf000 4352 gf000 4352 10.2.1/24 gf001 4352 gf001 4352 10.3.1/24 gf002 4352 gf002 4352 10.4.1/24 gf003 4352 gf003 4352 10.5.1/24 Address 00:c0:80:96:38:68 00:c0:80:96:38:68 192.168.4.4 00:00:00:00:00:00 0:0x40:0 127.0.0.1 0:0x48:0 00:c0:80:89:2d:f2 10.2.1.15 00:c0:80:89:2d:f3 10.3.1.16 00:c0:80:89:2d:f4 10.
If these ping commands fail, check routing settings and IP address assignment again. If everything is as it should be, try to ping the GRF FDDI media card ports or the GRF SP Switch media card to find the failing part: ping ping ping ping ping 10.2.1.15 (on node 12in SP2) 10.3.1.16 (on node 10 in SP2) 10.4.1.17 (on node 11 in SP2) 10.5.1.18 (on node 9 in SP2) 192.168.14.4 (on nodes in SP21) If any errors occur, check cabling, the configuration of the SP Switch Router media cards (See Section 3.
Configuration assumptions: • An SP Switch Router FDDI media card has been installed according to Section 4.4, “FDDI Configuration” on page 121 and works properly. • The SP Switch Router Adapter card has been installed according to Section 3.7, “Step-by-Step Media Card Configuration” on page 86, and works properly. • The SP Switch Router Adapter card and SP processor node Switch adapters are in the same IP subnet.
Table 18 shows the IP addresses used in our configuration. Table 18. Configuration of SP Switch - FDDI Connection (Bridging) Adapter IP Address FDDI interface in node 9 10.10.1.9 FDDI interface in node 10 10.10.1.10 FDDI interface in node 11 10.10.1.11 FDDI interface in node 12 10.10.1.12 Bridge Group bg0 10.10.1.13 SP Switch Router Adapter card 1 192.168.14.4 SP processor nodes in SP21 192.168.14.1 - 192.168.14.
bridge_group bg0 { port gf000 gf001 gf002 gf003; }; This is the simplest bridge definition that worked in our scenario. Many additional parameters can be set. See Section 4.6.9.3, “Editing Utility – Bredit” on page 146 for further details. • Assign an IP address: Open /etc/grifconfig.conf. Comment out all former FDDI interface definitions by inserting a # at the beginning of the respective lines.
3. Add the route to the Switch network of SP21 on all four nodes of SP2 with an FDDI interface. On node 9-12 in SP2, add the following route: route add -net 192.168.14 -netmask 255.255.255.0 -mtu 4352 10.10.1.13 4. Check for correct routing entries on all four nodes, for example: root@sp2n09:/ netstat -rn Routing tables Destination Gateway Flags Refs Route Tree for Protocol Family 2 (Internet): default 192.168.3.37 UG 1 10.10.1/24 10.10.1.9 U 1 127/8 127.0.0.1 U 8 192.168.3/24 192.168.3.9 U 8 192.168.
7. On the CWS of SP21, check if the SP Switch Router Adapter card is configured. To perform this check, look if the SP Switch Router Adapter card shows up green in perspectives or enter SDRGetObjects switch_responds. Use Eunfence if needed. 8. Issue some ping commands to check the connection: On the chosen SP21 nodes, ping all four FDDI interfaces of nodes in SP2, for example: root@sp21n01:/ ping 10.10.1.9 PING 10.10.1.9: (10.10.1.9): 56 data bytes 64 bytes from 10.10.1.
vice versa. We sent these files to /dev/null to eliminate any hard disk influence on the receiver side. The hardware requisites for this test are the same as described in Section 5.1.4.1, “SP Switch - FDDI Connection without Bridging” on page 174. The slow internal SCSI disks in two of our four nodes in SP2 would not allow the transfer rate to exceed 4.5 MB/s. Both remaining nodes in SP2 contain faster SSA hard disks that allow a transfer rate of 7.5 MB/s.
Configuration assumptions: • The SP Switch Router FDDI media card has been installed according to Section 4.4, “FDDI Configuration” on page 121, and works properly. • The SP Switch Router Adapter card has been installed according to Section 3.7, “Step-by-Step Media Card Configuration” on page 86, and works properly. • The SP Switch Router Adapter card and SP processor node Switch adapters are in the same IP subnet.
5.2 Single SP Partition and Multiple SP Switch Router Adapter Cards It is frequently necessary to maintain the data transfer even when an SP Switch Router Adapter fails. This scenario describes how to setup a dual, not truly redundant, connection between SP Switch Router and SP Switch (see Figure 59) and how to recover from an adapter or cable failure. 5.2.
1. Each SP Switch Router Adapter card interface has to be in a different subnet. 2. Netmasks have to be used to create different subnets on the router side. 3. Logical subnetting is only required on the router. The SP switch sees a single network. 4. Each SP Switch Router Adapter card must have a unique IP address. An alias IP address cannot be used on two active cards on the same router system. Note: Be careful that the subnet mask does not, in effect, create a single subnet.
If the SP Switch Router Adapter cards work, the can both be used to route IP traffic from the SP Switch. Add the following routes to the SP nodes of SP21: route add -net xxx.xxx.xxx.xxx -netmask yyy.yyy.yyy.yyy -mtu \ zzz 192.168.14.4 to route outgoing traffic (coming from the SP node) via SP Switch Router Adapter card 1 and: route add -net xxx.xxx.xxx.xxx -netmask yyy.yyy.yyy.yyy -mtu \ zzz 192.168.14.129 to route outgoing traffic (coming from the SP node) via SP Switch Router Adapter card 2. xxx.xxx.
5.2.2 Complex Configuration In this section, we describe the setup of a complete scenario with a dual SP Switch Router connection, and explain why node 8 in SP21 in this setup is able to route IP traffic via IP address 192.168.14.129 (Figure 60 and Table 20 on page 191), although the way back apparently does not exist.
Table 20. Configuration of a Dual SP Switch Router - SP Switch Connection Adapter IP Address Netmask SP Switch Router Adapter card 1 192.168.14.4 255.255.255.128 SP Switch Router Adapter card 2 192.168.14.129 255.255.255.128 SP Switch Router Adapter card 3 192.168.13.4 255.255.255.0 Node 1 in SP2 192.168.13.1 255.255.255.0 Node 6 in SP21 192.168.14.6 255.255.255.0 Node 8 in SP21 192.168.14.8 255.255.255.0 Node 10 in SP21 192.168.14.130 255.255.255.
3. On node 6 in SP21, add the following route to the Switch network of SP2: route add -net 192.168.13 -netmask 255.255.255.0 -mtu 65280 \ 192.168.14.4 The -mtu parameter is again optional but should be set to ensure optimal packet size on this route. 4. Check for correct routing entry: root@sp21n06:/ netstat -rn Routing tables Destination Gateway Flags Refs Route Tree for Protocol Family 2 (Internet): default 192.168.4.137 UG 0 127/8 127.0.0.1 U 8 192.168.4/24 192.168.4.6 U 6 192.168.13/24 192.168.14.
8. Check for correct routing entry: root@sp21n10:/ netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2 (Internet): default 192.168.4.137 UG 0 19 en0 - 10.2.1/24 10.2.1.1 U 0 8 fi0 - 127/8 127.0.0.1 U 8 414 lo0 - 192.168.4/24 192.168.4.10 U 6 101692 en0 - 192.168.13/24 192.168.14.129 UG 0 0 css0 65280 192.168.14/24 192.168.14.10 U 3 10936 css0 - Route Tree for Protocol Family 24 (Internet v6): ::1 ::1 UH 0 0 lo0 16896 - 9.
On node 1 in SP2, ping the SP Switch interfaces of the chosen nodes in SP21, for example: root@sp2n01:/ ping 192.168.14.6 PING 192.168.14.6: (192.168.14.6): 56 data bytes 64 bytes from 192.168.14.6: icmp_seq=0 ttl=253 time=1 ms 64 bytes from 192.168.14.6: icmp_seq=1 ttl=253 time=1 ms ^C ----192.168.14.6 PING Statistics---2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 1/1/1 ms If these ping commands fail, check routing settings again.
node 1 SP Switch GRF 400 SP Switch Adapter HIPPI GRF 1600 SP Switch Adapter HIPPI SP Switch Adapter 192.168.13.1 255.255.255.0 SP Switch 192.168.14.4 255.255.255.128 node 6 192.168.14.6 255.255.255.0 192.168.14.129 255.255.255.128 Figure 61. IP Traffic Flow When Issuing ping 192.168.13.1 on Node 6 Figure 63 on page 196 shows the IP traffic flow when issuing the ping 192.168.13.1 on node 10 in SP21. All packets are first forwarded to the SP Switch Adapter card with IP address 192.168.14.
Figure 63 shows the IP traffic flow when issuing ping 192.168.13.1 on node 8 in SP21. All packets are first forwarded to the SP Switch Adapter card with IP address 192.168.14.129 corresponding to the routing settings. From this SP Switch Adapter card all packets are forwarded via HIPPI connection to the only SP Switch Adapter card in GRF 400, which forwards the traffic to node 1 in SP2. The way back follows first the same route.
To recover from a failing SP Switch Adapter card, you have to define an alias IP address for the surviving card. Follow these steps when gt030 fails: 1. Login as root to the SP Switch Router. 2. Remove the interface of gt030 from active status: ifconfig gt030 delete 3. Assign the alias IP address to gt050: ifconfig gt050 alias 192.168.14.4 netmask 255.255.255.128 Follow these steps, when gt050 fails: 1. Login as root to SP Switch Router. 2.
Configuration assumptions: • The RS/6000 SP is partitioned in to two or more partitions (two partitions for this scenario). Note: Be careful when choosing the partition layout. In every partition, a free Switch chip port to connect the SP Switch Router Adapter card is necessary. • Every partition establishes a single subnet. Note: Be careful when subnetting your SP partitions.
Table 21 shows the IP addresses used in our configuration. Table 21. Configuration of a Partition - Partition Connection Adapter IP Address Netmask SP Switch Router Adapter card 1 192.168.13.4 255.255.255.128 SP Switch Router Adapter card 2 192.168.13.129 255.255.255.128 Node 11 in SP2 192.168.13.130 255.255.255.128 Node 12 in SP2 192.168.13.131 255.255.255.128 Node 15 in SP2 192.168.13.132 255.255.255.128 All other processor nodes in SP2 192.168.13.1 192.168.13.15 255.255.255.
The -mtu parameter is again optional but should be set to ensure optimal packet size on this route. 4. Check for correct routing entry: root@sp2n01:/ netstat -rn Routing tables Destination Gateway Flags Refs Route Tree for Protocol Family 2 (Internet): default 192.168.3.37 UG 0 127/8 127.0.0.1 U 8 192.168.3/24 192.168.3.1 U 8 192.168.13/25 192.168.13.1 U 1 192.168.13.128/25 192.168.13.
root@sp2n01:/ ping 192.168.13.132 PING 192.168.13.132: (192.168.13.132): 56 data bytes 64 bytes from 192.168.13.132: icmp_seq=0 ttl=254 time=1 ms 64 bytes from 192.168.13.132: icmp_seq=1 ttl=254 time=1 ms ^C ----192.168.13.132 PING Statistics---2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 1/1/1 ms If these ping commands fail, check routing settings again. If everything is as it should be try to ping the SP Switch Router Adapter cards to find the failing part: ping 192.
202 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Chapter 6. Multiple RS/6000 SPs and One SP Switch Router In this configuration, two RS/6000 SP systems are connected to a single SP Switch Router. This enables both SPs to communicate deploying the SP Switch data transfer rate and/or to share other network resources. See Figure 65 for an overview.
/etc/snmpd.conf on the GRF 1600. To check, open this file and look for a stanza similar to the following: MANAGER 192.168.4.137 SEND ALL TRAPS TO PORT 162 WITH COMMUNITY spenmgmt This stanza is needed twice, one for each CWS. Otherwise, the SP Switch Router Adapter card will hang in state loading. Additionally, when you assign an IP address to the second SP Switch Router Adapter card using SMIT, ensure that this IP address can be resolved by name service, be it DNS or /etc/hosts based.
route add -net 192.168.13 -netmask 255.255.255.0 -mtu 65280 \ 192.168.14.4 2. Check for correct routing entry: root@sp21n01:/ netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2 (Internet): default 192.168.4.137 UG 0 515 en0 10.1.1/24 192.168.14.4 UG 0 65 css0 10.10.1/24 192.168.14.4 UG 0 2 css0 4352 10.50.1/24 192.168.14.4 UG 0 37 css0 127/8 127.0.0.1 U 8 518 lo0 192.168.4/24 192.168.4.1 U 10 345052 en0 192.168.13/24 192.168.14.
cards shows up green in perspectives or enter SDRGetObjects switch_responds. Use Eunfence if needed. 7. Issue some ping commands to check the connection: On the SP2 nodes, ping the SP Switch interface of any node in SP21: root@sp2n01:/ ping 192.168.14.1 PING 192.168.14.1: (192.168.14.1): 56 data bytes 64 bytes from 192.168.14.1: icmp_seq=0 ttl=254 time=1 ms 64 bytes from 192.168.14.1: icmp_seq=1 ttl=254 time=1 ms ^C ----192.168.14.
With this scenario and without further tuning (refer to Appendix A, “Laboratory Hardware and Software Configuration” on page 233 for actual no parameters), we measured a stable cumulative transfer rate of up to 83 MB/s (observed with the freeware tool monitor). This was the maximum transfer rate achievable in our environment. We are confident that further tuning and faster nodes can achieve higher transfer rates up to the maximum of GRFs crosspoint switch which is 100 MB/s. 6.
interference between data transfers from each SP to different SP Switch Router Adapter media cards except the one caused by limited bandwidth of the different network types (FDDI, ATM).
Chapter 7. Multiple RS/6000 SPs and Multiple GRFs In this section, sample configurations with two SP systems connected with two SP Switch Routers are presented. The routers, in turn, are connected by any kind of high speed network supported by the GRF. Preferable selections are dedicated high performance networks such as FDDI, ATM or HIPPI. Figure 67 on page 209 will help to understand the setup.
fast network. (The spare second port might be in use for example for a connection to an ATM attached device that needs a fast path to the SP Switch network). To make use of both ports, four possible solutions come to mind: 1. Break up your already existing network topology (nodes of the SP) and create different subnets, which in turn can be routed over the different ATM subnets on the two ports. We do not expect that any customer will do this, but the solution is mentioned here for the sake of completeness.
• If ARP is disabled on the SP Switch network, the IP addresses assigned to the nodes must be determined by the switch node numbers. Note: The SP Switch Router Adapter card will not properly forward IP data to nodes assigned with an IP address that is in another subnet. Configuration: In this scenario, we have the SP Switch of SP21 connected to the GRF 1600. The GRF 1600 has its ATM OC-3c media card’s port 00 connected to the GRF 400 ATM OC-3c media card’s port 00.
Table 23. Configuration of SP Switch - ATM - SP Switch Adapter IP Address SP Switch Router Adapter card 1 192.168.13.4 SP Switch Router ATM media card (port 00) in GRF 400 10.1.1.2 SP Switch Router ATM media card (port 00) in GRF 1600 10.1.1.1 SP Switch Router Adapter card 2 192.168.14.4 To successfully run this configuration, a route to the distant SP Switch network has to be set on every SP Switch Router.
1. The file /etc/gratm.conf needs the configuration statements for the port used: Traffic_Shape name=high_speed_high_quality \ peak=155000 sustain=155000 burst=2048 qos=high Interface ga020 traffic_shape=high_speed_high_quality PVC ga020 0/132 proto=ip traffic_shape=high_speed_high_quality 2. The file /etc/grifconfig.conf has the following entries: gt010 ga020 192.168.13.4 10.1.1.2 255.255.255.0 255.255.255.0 - mtu 65520 mtu 9180 3. The file /etc/grroute.conf has the following line: 192.168.14.0 255.
root@sp21cw0:/ dsh -a netstat -rn | grep 192.168.13 sp21n01: 192.168.13/24 192.168.14.4 UG 1 1020086 css0 9180 sp21n05: 192.168.13/24 192.168.14.4 UG 0 12456 css0 9180 sp21n06: 192.168.13/24 192.168.14.4 UG 0 15 css0 9180 sp21n07: 192.168.13/24 192.168.14.4 UG 0 731470 css0 9180 sp21n08: 192.168.13/24 192.168.14.4 UG 0 0 css0 9180 sp21n09: 192.168.13/24 192.168.14.4 UG 0 1533484 css0 9180 sp21n10: 192.168.13/24 192.168.14.4 UG 0 643863 css0 9180 sp21n11: 192.168.13/24 192.168.14.
Performance: To get a rough overview of the data transfer rates that can be achieved in this scenario, the following test was performed: 1. We used ftp to conduct several file transfers of a 300 MB file from the nodes in SP2 to one chosen node in SP21, and at the same time used ftp to conduct several file transfers of a 300 MB file from the nodes in SP21 to a chosen node in SP2. We sent the files to /dev/null on the receiving node to eliminate any hard disk influence. We saw up to about 14.
Table 24 shows the IP addresses used in our configuration. Table 24. Configuration of SP Switch - ATM Bridged - SP Switch Adapter IP Address SP Switch Router Adapter card 1 192.168.13.4 SP Switch Router ATM media card (port 00) in GRF 400 10.1.1.2 SP Switch Router ATM media card (port 00) in GRF 1600 10.1.1.1 SP Switch Router Adapter card 2 192.168.14.
Router, so there was no technical reason for it. The :wq! in the screen shot is there to remind you how to end editing of the file, and we give an n (no) as answer to the last question, as the ATM ports are already in use and therefore cannot be modified. So we need to reboot the GRF, and this takes care of the relevant settings anyway. See Section 4.6.9.3, “Editing Utility – Bredit” on page 146 for more information. 2. The following changes need to be applied to /etc/grifconfig.conf: #ga010 10.1.1.
Now it is time to look at the GRF 400: 1. The following screen shot gives you the minimum required data to be put into /etc/bridged.conf: # bredit Could not find default config file ’/etc/bridged.conf’. This seems to be the first time bridged is being configured. Do you want to use the template configuration file ? [y/n] [n] y G bridge_group bg1 ( port ga020 ga0280; }; :wq! /tmp/bridged.conf.2371: 7 lines, 101 characters. Update /etc/bridged.conf with these changes? [y/n] [n] y Parsed file "/tmp/bridged.
This two lines were changed from the basic configuration! PVC ga020 0/132 proto=llc,bridging PVC ga0280 0/134 proto=llc,bridging Because the GRF supports InATMARP, there is no need to have any entries in /etc/grarp.conf. The file /etc/grroute.conf also remains unchanged: 192.168.14.0 255.255.255.0 10.1.1.1 If there is no such entry in /etc/grroute.conf, the following command must be run on GRF 400 after every reboot: route add -net 192.168.14.0 -netmask 255.255.255.0 -mtu 9180 10.1.1.
root@sp2cw0:/ dsh -a netstat -rn | grep 192.168.14 sp2n01: 192.168.14/24 192.168.13.4 UG 0 1099887 css0 9180 sp2n05: 192.168.14/24 192.168.13.4 UG 0 1299484 css0 9180 sp2n06: 192.168.14/24 192.168.13.4 UG 0 352513 css0 9180 sp2n07: 192.168.14/24 192.168.13.4 UG 0 999147 css0 9180 sp2n08: 192.168.14/24 192.168.13.4 UG 0 146784 css0 9180 sp2n09: 192.168.14/24 192.168.13.4 UG 0 355671 css0 9180 sp2n10: 192.168.14/24 192.168.13.4 UG 0 879759 css0 9180 sp2n11: 192.168.14/24 192.168.13.
So what happened to the expected doubling of the aggregate throughput? As it turns out, even with bridging activated, only one ATM port is allowed to send and receive data.
grf16:/root brstat Bridge Group bg1 Spanning Tree: Enabled Designated Root: 32768 00:c0:80:84:8c:eb Bridge ID: 32768 00:c0:80:96:38:68 Root Port: ga0180, Root Path Cost: 10 Topology Change Detected: No Root Max Age: 20, Hello Time: 2, Forward Delay: 15 Bridge Max Age: 20, Hello Time: 2, Forward Delay: 15, Hold Time: 1 Interface --------ga010 *ga0180 Port ID ------128 1 128 2 Con --No Yes State ---------Disabled Forwarding Path Cost ----10 10 Desig Desig Desig Cost Bridge Port ----- -------------------
Configuration assumptions: • The SP Switch Router ATM media card has been installed according to Section 4.3, “ATM OC-12c Configuration” on page 119 on both GRF routers and works properly. • The SP Switch Router Adapter card has been installed according to Section 3.7, “Step-by-Step Media Card Configuration” on page 86 on both GRF routers and works properly. • The SP Switch Router Adapter card and SP processor node Switch adapters are in the same IP subnet on the respective SP.
Table 25 shows the IP addresses used in our configuration. Table 25. Configuration of SP Switch - ATM OC-12c - SP Switch Adapter IP Address SP Switch Router Adapter card 1 192.168.13.4 SP Switch Router ATM media card (port 00) in GRF 400 10.20.30.2 SP Switch Router ATM media card (port 00) in GRF 1600 10.20.30.1 SP Switch Router Adapter card 2 192.168.14.4 To successfully run this configuration, on every SP Switch Router a route to the distant SP Switch network has to be set.
1. The file /etc/gratm.conf needs the configuration statements for the port used: Traffic_Shape name=bigg_speed_high_quality \ peak=622000 sustain=622000 burst=2048 qos=high Interface ga010 traffic_shape=bigg_speed_high_quality PVC ga010 0/132 proto=ip traffic_shape=bigg_speed_high_quality 2. The file /etc/grifconfig.conf has the following entries: gt030 ga010 192.168.13.4 10.20.30.2 255.255.255.0 255.255.255.0 - mtu 65520 mtu 9180 3. The file /etc/grroute.conf has the following line: 192.168.14.
root@sp21cw0:/ dsh -a netstat -rn | grep 192.168.13 sp21n01: 192.168.13/24 192.168.14.4 UG 1 1020086 css0 9180 sp21n05: 192.168.13/24 192.168.14.4 UG 0 12456 css0 9180 sp21n06: 192.168.13/24 192.168.14.4 UG 0 15 css0 9180 sp21n07: 192.168.13/24 192.168.14.4 UG 0 731470 css0 9180 sp21n08: 192.168.13/24 192.168.14.4 UG 0 0 css0 9180 sp21n09: 192.168.13/24 192.168.14.4 UG 0 1533484 css0 9180 sp21n10: 192.168.13/24 192.168.14.4 UG 0 643863 css0 9180 sp21n11: 192.168.13/24 192.168.14.
Performance: To get a rough overview of the data transfer rates that can be achieved in this scenario, the following test was performed: 1. We used ftp to conduct several file transfers of a 300 MB file from the nodes in SP2 to one chosen node in SP21, and at the same time used ftp to conduct several file transfers of a 300 MB file from the nodes in SP21 to a chosen node in SP2. We sent the files to /dev/null on the receiving node to eliminate any hard disk influence. We saw up to about 44.
Configuration: In this scenario, we have the SP Switch of SP21 connected to an GRF 1600. The GRF 1600 has its HIPPI media card’s ports cross-connected to the GRF 400 HIPPI media card’s ports. That means that on both sides DESTINATION is cabled to SOURCE. The GRF 400 in turn is attached to the SP Switch of SP2, as shown in Figure 71 and Table 26. The netmask for all interfaces is 255.255.255.0. Net 10.50.1.2 HIPPI Adapter card SP Switch Router 1 Net 192.168.13.0 IP 192.168.13.
The media card adapters on the GRF routers should already be up and running (according to Section 3.7, “Step-by-Step Media Card Configuration” on page 86 and Section 4.5, “HIPPI Configuration” on page 133). Important settings are repeated here, nevertheless, to be on the safe side: On the GRF 1600 (HIPPI card is in slot 8, SP Switch card is in slot 3) check for the following: 1. The file /etc/grifconfig.conf has the following entries: gh080 gt030 10.50.1.1 192.168.14.4 255.255.255.0 255.255.255.
5. The SP Switch Router Adapter card is connected to the SP Switch and configured. Check with SDRGetObjects switch_responds on the CWS and use Eunfence if needed. The following tasks are performed on the respective SP nodes: 1. On the nodes in SP21, the following route needs to be set: route add -net 192.168.13 -netmask 255.255.255.0 -mtu 65280 10.50.1.2 2. On the nodes in SP2, the following route needs to be set: route add -net 192.168.14 -netmask 255.255.255.0 -mtu 65280 10.50.1.
root@sp2en0:/ dsh netstat -rn | grep 192.168.14 sp2n01: 192.168.14/24 192.168.13.4 UG sp2n05: 192.168.14/24 192.168.13.4 UG sp2n06: 192.168.14/24 192.168.13.4 UG sp2n07: 192.168.14/24 192.168.13.4 UG sp2n08: 192.168.14/24 192.168.13.4 UG sp2n09: 192.168.14/24 192.168.13.4 UG sp2n10: 192.168.14/24 192.168.13.4 UG sp2n11: 192.168.14/24 192.168.13.4 UG sp2n12: 192.168.14/24 192.168.13.4 UG sp2n13: 192.168.14/24 192.168.13.4 UG sp2n14: 192.168.14/24 192.168.13.4 UG sp2n15: 192.168.14/24 192.168.13.
We saw up to about 48 MB/s with just one side sending data. With all nodes sending and receiving, we achieved a duplex throughput of about 54 MB/s on the HIPPI port.
Appendix A. Laboratory Hardware and Software Configuration This appendix contains a detailed description of the hardware and software configuration used to test scenarios described in the second part of this redbook. All hostnames, IP addresses, adapters and other configuration information mentioned there refer to the following section if no other information is given. A.1 Node and Control Workstation Configuration This section describes the basic node and CWS configuration used to establish the scenarios.
Table 27. Configuration of SP 21 234 Node Node Type Hostname Adapter IP address Node0 (CWS) RS/6000 570 sp21en0 ent0 tok0 192.168.4.137 9.12.1.137 Node 1 high node 112 Mhz,6 proc. sp21n01 ent0 css0 192.168.4.1 192.168.14.1 Node 5 thin node 66 MHz sp21n05 ent0 css0 192.168.4.5 192.168.14.5 Node 6 thin node 66 MHz sp21n06 ent0 css0 192.168.4.6 192.168.14.6 Node 7 thin node 66 MHz sp21n07 ent0 css0 192.168.4.7 192.168.14.7 Node 8 thin node 66 MHz sp21n08 ent0 css0 192.168.4.
Table 28. Configuration of SP 2 Node Node Type Hostname Adapter IP address Node0 (CWS) RS/6000 590 sp2en0 ent0 tok0 192.168.3.37 9.12.1.37 Node1 high node 112 MHz, 8 proc. sp2n01 ent0 css0 192.168.3.1 192.168.13.1 Node5 thin node 66 MHz sp2n05 ent0 css0 192.168.3.5 192.168.13.5 Node6 thin node 66 MHz sp2n06 ent0 css0 192.168.3.6 192.168.13.6 Node7 thin node 66 MHz sp2n07 ent0 css0 192.168.3.7 192.168.13.7 Node8 thin node 66 MHz sp2n08 ent0 css0 192.168.3.8 192.168.13.
selected nodes. Refer to the scenario descriptions in second part of this redbook to see which disks were used. Table 29. Hard Disk Equipment of SP 21 236 Node Disks Description Node (CWS) hdisk0 hdisk1 hdisk2 hdisk3 1.2 GB 1.2 GB 1.0 GB 1.0 GB Node 1 hdisk0 hdisk1 2.2 GB SCSI Disk Drive 2.2 GB SCSI Disk Drive Node 5 hdisk0 1.0 GB SCSI Disk Drive Node 6 hdisk0 1.0 GB SCSI Disk Drive Node 7 hdisk0 1.0 GB SCSI Disk Drive Node 8 hdisk0 1.0 GB SCSI Disk Drive Node 9 hdisk0 hdisk1 1.
Table 30. Hard Disk Equipment of SP 2 Part 1 of 2 Node Disks Description Node0 (CWS) hdisk0 hdisk1 hdisk2 hdisk3 hdisk4 hdisk5 2.0 GB 2.0 GB 2.0 GB 2.0 GB 1.0 GB 1.0 GB Node1 hdisk0 hdisk1 2.2 GB SCSI Disk Drive 2.2 GB SCSI Disk Drive Node5 hdisk0 hdisk1 hdisk2 hdisk3 hdisk4 hdisk5 hdisk6 1.0 GB SCSI Disk Drive 1.0 GB SCSI Disk Drive 7135 Disk Array Device 7135 Disk Array Device 7135 Disk Array Device 7135 Disk Array Device 7135 Disk Array Device Node6 hdisk0 hdisk1 1.0 GB SCSI Disk Drive 1.
Table 31. Hard Disk Equipment of SP 2 Part 2 of 2 238 Node Disks Description Node13 hdisk0 hdisk1 hdisk2 hdisk3 hdisk4 hdisk5 1.0 GB SCSI Disk Drive 1.0 GB SCSI Disk Drive SSA Logical Disk Drive SSA Logical Disk Drive SSA Logical Disk Drive SSA Logical Disk Drive Node14 hdisk0 hdisk1 hdisk2 hdisk3 hdisk4 hdisk5 hdisk6 hdisk7 hdisk8 1.0 GB SCSI Disk Drive 1.
A.1.2 Software Configuration Both CWSs and every SP node are installed with AIX 4.3.1, including all fixes available on May 20th, 1998, and PSSP 2.4 PTF Set 1 (See Table 32). Table 32. Software Levels on CWS and All Nodes Part 1 of 14 Fileset Level Description Java.rte.bin 1.1.4.0 Java Runtime Environment Executables Java.rte.classes 1.1.4.0 Java Runtime Environment Classes Java.rte.lib 1.1.4.0 Java Runtime Environment Libraries X11.Dt.ToolTalk 4.3.1.0 AIX CDE ToolTalk Support X11.Dt.
Table 33. Software Levels on CWS and All Nodes Part 2 of 14 240 Fileset Level Description X11.compat.lib.X11R3 4.3.0.0 AIXwindows X11R3 Libraries Compatibility X11.compat.lib.X11R4 4.3.0.0 AIXwindows X11R4 Libraries Compatibility X11.compat.lib.X11R5 4.3.1.1 AIXwindows X11R5 Compatibility Libraries X11.fnt.coreX 4.3.0.0 AIXwindows X Consortium Fonts X11.fnt.defaultFonts 4.3.0.0 AIXwindows Default Fonts X11.fnt.iso1 4.3.0.0 AIXwindows Latin 1 Fonts X11.fnt.iso_T1 4.3.0.
Table 34. Software Levels on CWS and All Nodes Part 3 of 14 Fileset Level Description bos.adt.include 4.3.1.1 Base Application Development Include Files bos.adt.lib 4.3.1.0 Base Application Development Libraries bos.adt.libm 4.3.1.0 Base Application Development Math Library bos.adt.prof 4.3.1.1 Base Profiling Support bos.adt.prt_tools 4.3.0.0 Printer Support Development Toolkit bos.adt.samples 4.3.1.0 Base Operating System Samples bos.adt.sccs 4.3.1.
Table 35. Software Levels on CWS and All Nodes Part 4 of 14 242 Fileset Level Description bos.loc.iso.en_US 4.3.1.0 Base System Locale ISO Code Set - U.S. English bos.mh 4.3.1.1 Mail Handler bos.msg.en_US.alt_disk_install.rte 4.3.0.0 Alternate Disk Install Msgs - U.S. English bos.msg.en_US.diag.rte 4.3.1.0 Hardware Diagnostics Messages - U.S. English bos.msg.en_US.net.tcp.client 4.3.1.0 TCP/IP Messages - U.S. English bos.msg.en_US.rte 4.3.1.0 Base Operating System Runtime Msgs - U.S.
Table 36. Software Levels on CWS and All Nodes Part 5 of 14 Fileset Level Description bos.rte.bind_cmds 4.3.1.1 Binder and Loader Commands bos.rte.boot 4.3.1.0 Boot Commands bos.rte.bosinst 4.3.1.0 Base OS Install Commands bos.rte.commands 4.3.1.1 Commands bos.rte.compare 4.3.1.0 File Compare Commands bos.rte.console 4.3.1.0 Console bos.rte.control 4.3.1.1 System Control Commands bos.rte.cron 4.3.1.1 Batch Operations bos.rte.date 4.3.1.0 Date Control Commands bos.rte.
Table 37. Software Levels on CWS and All Nodes Part 6 of 14 244 Fileset Level Description bos.rte.methods 4.3.1.0 Device Config Methods bos.rte.misc_cmds 4.3.1.0 Miscellaneous Commands bos.rte.net 4.3.1.0 Network bos.rte.odm 4.3.1.0 Object Data Manager bos.rte.printers 4.3.1.0 Front End Printer Support bos.rte.security 4.3.1.0 Base Security Function bos.rte.serv_aid 4.3.1.0 Error Log Service Aids bos.rte.shell 4.3.1.1 Shells (bsh, ksh, csh) bos.rte.streams 4.3.1.
Table 38. Software Levels on CWS and All Nodes Part 7 of 14 Fileset Level Description bos.txt.spell 4.3.1.0 Writer’s Tools Commands bos.txt.spell.data 4.3.0.0 Writer’s Tools Data bos.txt.tfs 4.3.1.0 Text Formatting Services Commands bos.txt.tfs.data 4.3.0.0 Text Formatting Services Data bos.txt.ts 4.3.1.0 TranScript Tools bos.up 4.3.1.1 Base Operating System Uniprocessor Runtime devices.base.diag 4.3.1.0 Base System Diagnostics devices.base.rte 4.3.1.
Table 39. Software Levels on CWS and All Nodes Part 8 of 14 246 Fileset Level Description devices.common.rspcbase.rte 4.3.1.0 RISC PC Common Base System Device Software devices.graphics.com 4.3.1.1 Graphics Adapter Common Software devices.mca.0200.diag 4.3.0.0 Wide SCSI Adapter Diagnostics devices.mca.0200.rte 4.3.0.0 Wide SCSI Adapter devices.mca.61fd.diag 4.3.0.0 64-Port Asynchronous Adapter Diagnostics devices.mca.61fd.rte 4.3.1.0 64-Port Asynchronous Adapter Software devices.mca.
Table 40. Software Levels on CWS and All Nodes Part 9 of 14 Fileset Level Description devices.mca.8f67.com 4.3.1.0 Common Turboways ATM Software devices.mca.8f67.diag 4.3.0.0 155 Mbps ATM Adapter (8f67) Diagnostics devices.mca.8f67.diag.com 4.3.1.0 Common ATM 155 Mbps ATM Adapter Diagnostics devices.mca.8f67.rte 4.3.0.0 Turboways 155 MCA ATM Adapter (8f67) Software devices.mca.8f67.ucode 4.3.1.0 Turboways 155 MCA ATM Adapter (8f67) Microcode devices.mca.8f7f.diag 4.3.0.
Table 41. Software Levels on CWS and All Nodes Part 10 of14 248 Fileset Level Description devices.msg.en_US.base.com 4.3.0.0 Base System Device Software Msgs - U.S. English devices.msg.en_US.diag.rte 4.3.1.0 Device Diagnostics Messages - U.S. English devices.msg.en_US.rspc.base.com 4.3.0.0 RISC PC Software Messages - U.S. English devices.msg.en_US.sys.mca.rte 4.3.1.0 Micro Channel Bus Software Messages - U.S. English devices.rs6ksmp.base.rte 4.3.1.
Table 42. Software Levels on CWS and All Nodes Part 11 of 14 Fileset Level Description devices.ssa.network_agent.rte 4.3.1.0 SSA Network Agent Support devices.ssa.tm.rte 4.3.1.0 Target Mode SSA Support devices.sys.mca.rte 4.3.1.0 Micro Channel Bus Software devices.sys.slc.diag 4.3.1.0 Serial Optical Link Diagnostics devices.sys.slc.rte 4.3.1.0 Serial Optical Link Software devices.tty.rte 4.3.1.0 TTY Device Driver Support Software ifor_ls.base.cli 4.3.1.
Table 43. Software Levels on CWS and All Nodes Part 12 of 14 250 Fileset Level Description printers.hplj-c.rte 4.3.0.0 Hewlett-Packard LaserJet Color printers.ibm2380.rte 4.3.0.0 IBM 2380 Personal Printer II printers.ibm2381.rte 4.3.0.0 IBM 2381 Personal Printer II printers.ibm2390.rte 4.3.0.0 IBM 2390 Personal Printer II printers.ibm3130.rte 4.3.0.0 IBM 3130 LaserPrinter printers.ibm4019.rte 4.3.0.0 IBM 4019 LaserPrinter printers.ibm4029.rte 4.3.0.0 IBM 4029 LaserPrinter printers.
Table 44. Software Levels on CWS and All Nodes Part 13 of 14 Fileset Level Description printers.lexOptraE.rte 4.3.0.0 Lexmark Optra E Laser Printer printers.lexOptraEp.rte 4.3.0.0 Lexmark Optra Ep Laser Printer printers.lexOptraN.rte 4.3.0.0 Lexmark Optra N Laser Printer printers.lexOptraS.rte 4.3.0.0 Lexmark Optra S Laser Printer printers.lexOptraSC.rte 4.3.0.0 Lexmark Optra SC Color Laser Printer printers.msg.en_US.rte 4.3.1.0 Printer Backend Messages - U.S. English printers.qms100.
Table 45. Software Levels on CWS and All Nodes Part 14 of 14 252 Fileset Level Description sysmgt.sguide.rte 4.3.1.0 TaskGuide Runtime Environment sysmgt.websm.apps 4.3.1.1 Web-based System Manager Applications sysmgt.websm.framework 4.3.1.1 Web-based System Manager Client/Server Support sysmgt.websm.icons 4.3.1.0 Web-based System Manager Icons sysmgt.websm.rte 4.3.1.1 Web-based System Manager Runtime Environment sysmgt.websm.ucf 4.3.1.
A.1.3 Network Options and Tuning Table 46 shows the network options on the CWS and all participating SP nodes. Options can be changed with the /etc/no command. Table 46.
Table 47.
Table 48. Network Options of CWS and All Nodes Part 3 of 3 Parameters Value ipignoreredirects 0 ipsrcroutesend 1 ipsrcrouterecv 1 ipsrcrouteforward 1 ip6srcrouteforward 1 ip6_defttl 64 ndpt_keep 120 ndpt_reachable 30 ndpt_retrans 1 ndpt_probe 5 ndpt_down 3 ndp_umaxtries 3 ndp_mmaxtries 3 ip6_prune 2 tcp_timewait 1 tcp_ephemeral_low 32768 tcp_ephemeral_high 65535 udp_ephemeral_low 32768 udp_ephemeral_high 65535 A.
A.3 7025-F50 Configuration A 7025-F50 was used for some ATM and Ethernet network tests. This machine is equipped with two166 MHz-604e processors, three 4500 MB 16-bit SCSI Disk Drives, an IBM 155 Mbps ATM PCI Adapter and an IBM 100/10 Mbps Ethernet PCI Adapter. AIX 4.3.1.1 is installed. For detailed software-level information, refer to Table 32 on page 239, but note that no PSSP file sets are installed. Table 49 contains the network options applied for the sample configurations. Table 49.
Table 50.
Table 51. Network Options of 7025-F50 Part 3 of 3 Parameter ipqmaxlen Value 100 directed_broadcast 1 ipignoreredirects 0 ipsrcroutesend 1 ipsrcrouterecv 0 ipsrcrouteforward 1 ip6srcrouteforward 1 ip6_defttl 64 ndpt_keep 120 ndpt_reachable 30 ndpt_retrans 1 ndpt_probe 5 ndpt_down 3 ndp_umaxtries 3 ndp_mmaxtries 3 ip6_prune 2 tcp_timewait 1 tcp_ephemeral_low 32768 tcp_ephemeral_high 65535 udp_ephemeral_low 32768 udp_ephemeral_high 65535 A.
The applied IP addresses vary with the scenario and are specified in the corresponding chapter. For specific SP Switch Router sample configuration files, refer to Appendix B, “GRF Configuration Files” on page 261.
260 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Appendix B. GRF Configuration Files This appendix contains relevant SP Switch Router configuration files. Some of them are here just for information, some of them were worked out manually during setup of hardware or software and some of them were created using Ascend-supplied tools. If you need up to date information about these files, look on the SP Switch Router in directory /etc. Most of the files mentioned in this appendix come as a *.conf.
# # # that we may consider enhancing it in future software releases to support your needs. # # GRF systems require /usr/nbin in the path. # PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/contrib/bin:/usr/nbin export PATH echo ’erase ^H, kill ^U, intr ^C status ^T’ stty crt erase kill - intr status umask 022 HOME=/root export HOME BLOCKSIZE=1k export BLOCKSIZE # # Enable "vi"-style ksh editing, to be consistent with GR 4.x releases.
# if [ -t 0 ] then # # Ask for a terminal type; the default is the canonical "vt100". # if [ X${TERM} = X ] then TERM=vt100 fi eval ‘tset -s -m ?$TERM‘ export TERM # # # # # # # # It’s interactive, so exec the new CLI shell for the GRF. # from here on commented out the next 15 lines as 99.99999% of work is from the shell prompt, and if you exit from CLI, .profile is not obeyed, sigh. you have to call ncli, to get the super> prompt.
B.3 /etc/bridged.conf This file holds the configuration data for transparent bridging. It is created using the utility bredit. # # NetStar $Id$ # # Configuration file for Bridge Daemon (bridged). # # Note: bridged will not start if it finds an error while # trying to parse this file. Use the "-d" option on the # command line with bridged to find proximity of the offending # line.
# to be a lead or at least low in the spanning tree. # The closer a LAN is to being a leaf in the tree, the # less through traffic it will be asked to carry. A # LAN would be a candidate for having a large path # cost if it has a lower bandwidth ot if someone wants # to minimize unnecessary traffic on it. A better # description is possibly link cost or port cost. # # root_path_cost 5; # # Forward packets with the following destination addresses # through this port.
# # # # # # # # turned on. Setting the forward delay too small would result in temporary loops as the spannign tree algorithm converges. Setting this value too large results in longer partitions after the spanning tree reconfigures. The recommended value is 15 sec. #forward_delay 15 seconds; # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # maximum_age: This is the time value advertised by this bridge for deciding whether to discard spanning tree frames based on message age.
# For ATM - ATM two ports Test Chap.7.1.2 bridge_group bg1 { port ga010 ga0180; # spanning_tree disabled; }; B.4 /etc/fstab This file holds the filesystem mount information. This file was changed when adding a PCMCIA hard disk in Section 3.3.2, “Installing the PCMCIA Spinning Disk” on page 76. # # Filesystem mount table information. See the fstab(5) man page # and the /etc/fstab.sample file for more information and examples.
# following formats: # # 48-bit MAC address for # Ethernet or FDDI: xx:xx:xx:xx:xx:xx # where ’xx’ are hexadecimal digits. # # 32-bit I-field for # HIPPI: C-language syntax for a 32-bit constant # Example: 0x03000555 for logical address x’555. # # 20-byte NSAP address or VPI/VCI for # ATM: vp/vc VPI/VCI for PVCs # where ’vp’ and ’vc’ are decimal integers # xx.xx.xx. . .xx.xx.xx.xx NSAP address # where ’xx’ are hexadecimal digits.
# The PVC section is where Permanent Virtual Circuits are defined, # using traffic shapes defined in the Traffic Shaping section, # along with other parameters specific to PVC configuration. # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Notes on the format of this file: Comments follow the Bourne Shell style (all characters following a # on a line are ignored). Statements in this file are separated by newlines.
#Service name=bc0 type=bcast addr=198.174.20.1 addr=198.174.22.1 \ # addr=198.174.21.1 # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Traffic shaping parameters Lines beginning with the keyword "Traffic_Shape" define traffic shapes which may be used to configure the performance characteristics of ATM Virtual Circuits. The Traffic_Shape’s defined here are to be referenced by name when to assign traffic shapes to PVC’s or Interfaces later in this configuration file.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # [mode=SDH|SONET] [clock=Ext|Int] The ’card’ and ’connector’ specification are mandatory. The card should be identified by a hexidecimal digit representing the slot number of the card in the GigaRouter chassis. The connector should be either ’top’ or ’bottom’. The ’protocol’ parameter defines the signalling protocol to be used in the setup of Switched Virtual Circuits (SVC’s) on this physical interface. This parameter is optional.
# # # # # # # # # # # # # # # # # # # # # # # # # the protocol vc_multiplexed - Use a separate PVC for each protocol LLC encapsulated bridging allows any LAN frame type to be transmitted, and also allows IP datagrams to be sent directly on the VC. The optional ’restriction’ parameter can limit how IP datagrams are routed to the interface, and on what kind of LAN frames are transmitted on it.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # (except for RFC 1483 bridging) any LLC-encapsulated protocol, including RFC 1483 bridging [This is the PVC type for an interface using bridge_method=llc_encapsulated.] ’vcmux_bridge’ bridged packets [This is a PVC type for an interface using bridge_method=vc_multiplexed.
peak=622000 sustain=622000 burst=2048 qos=high Signalling card=1 connector=top protocol=NONE Signalling card=1 connector=bottom protocol=NONE # Interface ga010 traffic_shape=high_speed_high_quality # PVC ga010 0/132 proto=ip traffic_shape=high_speed_high_quality Interface ga010 traffic_shape=high_speed_high_quality \ bridge_method=vc_multiplexed PVC ga010 0/132 proto=vcmux_bridge,bpdu PVC ga010 0/133 proto=vcmux_bridge,ether_nofcs PVC ga010 0/134 proto=vcmux_bridge,fddi_nofcs PVC ga010 0/135 proto=llc #PVC
# DEFAULTS sets all of the above keywords to the above defaults. ################################################################################ ################################################################################ # log files. ################################################################################ include=/etc/grclean.logs.
# Log files that used to be archived by the /etc/{daily|weekly|monthly} # scripts. ################################################################################ size=10000 logfile=/var/account/acct size=10000 logfile=/var/log/maillog size=150000 logfile=/var/log/messages size=10000 logfile=/var/log/daemon.log size=10000 logfile=/var/log/cron size=10000 logfile=/var/log/xferlog size=10000 logfile=/var/log/httpd/access_log size=10000 logfile=/var/log/httpd/error_log size=10000 logfile=/var/log/ftp.
DEFAULTS hold=2 local=y size=10000 logfile=/var/log/grclean.log B.9 /etc/grdev1.conf This file normally gets updated automatically by the SNMP daemon running on the CWS. ############################################################################ # DEV1 Configuration ########################################################################### # # There are several variables that an SP Adapter card needs at start up.
2.21.2.1.1.12 2.21.2.1.1.13 2.21.2.1.1.14 2.21.2.1.1.15 # # CARD 2 Interface # 2.21.3.1.1.1 2.21.3.1.1.2 2.21.3.1.1.3 2.21.3.1.1.4 2.21.3.1.1.5 2.21.3.1.1.6 2.21.3.1.1.7 2.21.3.1.1.8 2.21.3.1.1.9 2.21.3.1.1.10 2.21.3.1.1.11 2.21.3.1.1.12 2.21.3.1.1.13 2.21.3.1.1.14 2.21.3.1.1.15 # # CARD 3 Interface # 2.21.4.1.1.1 2.21.4.1.1.2 2.21.4.1.1.3 2.21.4.1.1.4 2.21.4.1.1.5 2.21.4.1.1.6 2.21.4.1.1.7 2.21.4.1.1.8 2.21.4.1.1.9 2.21.4.1.1.10 2.21.4.1.1.11 2.21.4.1.1.12 2.21.4.1.1.13 2.21.4.1.1.14 2.21.4.1.1.
2.21.6.1.1.3 "00:00:00:01:00:00:00:07:00:03" # Switch Token 2.21.6.1.1.4 2 # Switch ARP 2.21.6.1.1.5 15 # Switch Node Number 2.21.6.1.1.6 x192.168.14.129 # IP Address 2.21.6.1.1.7 x255.255.255.128 # Net Mask 2.21.6.1.1.8 1024 # Max Link Pckt Len.(bytes) 2.21.6.1.1.9 -14 # IP Host Offset 2.21.6.1.1.10 1 # Configuration State 2.21.6.1.1.11 sp21en0 # System Name 2.21.6.1.1.12 2 # Node State 2.21.6.1.1.13 3 # Switch Chip Link 2.21.6.1.1.14 31 # Node Delay 2.21.6.1.1.
2.21.9.1.1.12 2.21.9.1.1.13 2.21.9.1.1.14 2.21.9.1.1.15 # # CARD 9 Interface # 2.21.10.1.1.1 2.21.10.1.1.2 2.21.10.1.1.3 2.21.10.1.1.4 2.21.10.1.1.5 2.21.10.1.1.6 2.21.10.1.1.7 2.21.10.1.1.8 2.21.10.1.1.9 2.21.10.1.1.10 2.21.10.1.1.11 2.21.10.1.1.12 2.21.10.1.1.13 2.21.10.1.1.14 2.21.10.1.1.15 # # CARD 10 Interface # 2.21.11.1.1.1 2.21.11.1.1.2 2.21.11.1.1.3 2.21.11.1.1.4 2.21.11.1.1.5 2.21.11.1.1.6 2.21.11.1.1.7 2.21.11.1.1.8 2.21.11.1.1.9 2.21.11.1.1.10 2.21.11.1.1.11 2.21.11.1.1.12 2.21.11.1.1.13 2.21.
2.21.13.1.1.3 "00:00:00:00:00:00:00:00:00:00" # Switch Token 2.21.13.1.1.4 2 # Switch ARP 2.21.13.1.1.5 0 # Switch Node Number 2.21.13.1.1.6 x0.0.0.0 # IP Address 2.21.13.1.1.7 x0.0.0.0 # Net Mask 2.21.13.1.1.8 1024 # Max Link Pckt Len.(bytes) 2.21.13.1.1.9 0 # IP Host Offset 2.21.13.1.1.10 1 # Configuration State 2.21.13.1.1.11 "no name" # System Name 2.21.13.1.1.12 2 # Node State 2.21.13.1.1.13 0 # Switch Chip Link 2.21.13.1.1.14 64 # Node Delay (cycles) 2.21.13.1.1.
2.21.16.1.1.12 2.21.16.1.1.13 2.21.16.1.1.14 2.21.16.1.1.15 2 0 64 1 # # # # Node State Switch Chip Link Node Delay (cycles) Admin Status B.10 /etc/grifconfig.conf This file documents the correlation of the logical interfaces on the media cards in the GRF to IP addresses, together with some other information, like MTU. # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 282 NetStar $Id: grifconfig.conf,v 1.10.2.
# FDDI card. NOTE: The logical interface number # may be different from the physical interface on # the card, depending on the single- or dual# attachedness of the various interfaces. Examples: # "gf073" specifies the bottom-most connector # on the FDDI card in slot 7; "gf020" specifies # top-most connector on the FDDI card in slot 2, # or the top TWO connectors on that card if they’re # configured dual-attached.
#gt020 0.0.0.0 255.255.255.0 mtu 65520 gt030 192.168.14.4 255.255.255.128 mtu 65520 #gt040 192.168.14.129 255.255.255.128 mtu 65520 gt050 192.168.14.129 255.255.255.128 mtu 65520 #gt060 0.0.0.0 255.255.255.0 mtu 65520 #gt070 0.0.0.0 255.255.255.0 mtu 65520 #gt080 0.0.0.0 255.255.255.0 mtu 65520 #gt090 0.0.0.0 255.255.255.0 mtu 65520 #gt0a0 0.0.0.0 255.255.255.0 mtu 65520 #gt0b0 0.0.0.0 255.255.255.0 mtu 65520 #gt0c0 0.0.0.0 255.255.255.0 mtu 65520 #gt0d0 192.168.13.16 255.255.255.0 mtu 65520 #gt0e0 0.0.0.
# exit. # If only 3 values are designated, the first value will be repeated as the # fourth value. # # No whitespace is allowed in any field. # # ie. # 5,6 997,998 1,0x4,8,15 # When port cards 5 & 6 receive an IP packet with a logical address of 997 or # 998, it will then attempt to randomly forward the packet to one of the # mapped ports 1, 4, 8 or 15. # ################################################################################ #* #5 * * 5 6 # default mapping for all LAs for all portcards.
# A netmask is required for all entries in this configuration file. # # The netmask is normally the mask of the remote network: # # 192.0.2.0 255.255.255.0 123.45.67.89 # # For remote host routes, specify a netmask of 255.255.255.255: # # 192.0.2.1 255.255.255.255 123.45.67.89 # # In the case of the default route (0.0.0.0), the netmask is ignored, # but some value must be present for the file to parse correctly. # # # # destination netmask gateway/next hop # #0.0.0.0 0.0.0.0 192.0.2.2 default 0.0.0.0 192.
#uucpd stream tcp nowait root /usr/libexec/tcpd uucpd #finger stream tcp nowait nobody /usr/libexec/tcpd fingerd #tftp dgram udp wait nobody /usr/libexec/tcpd tftpd #comsat dgram udp wait root /usr/libexec/tcpd comsat #ntalk dgram udp wait root /usr/libexec/tcpd ntalkd #pop stream tcp nowait root /usr/libexec/tcpd popper #ident stream tcp nowait sys /usr/libexec/identd identd -l #bootp dgram udp wait root /usr/libexec/tcpd bootpd -t 1 #echo stream tcp nowait root internal #discard stream tcp nowait root int
#c and is protected by U.S. and other copyright laws and the #c laws protecting trade secret and confidential information. #c #c This product contains trade secret and confidential #c information, and its unauthorized disclosure is prohibited. #c #c Reproduction, utilization and transfer of rights to this #c product, whether in source or binary form, is permitted #c only pursuant to a written agreement signed by an authorized #c officer of NetStar, Inc. #c # # NetStar $Id: rc.local,v 1.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # [SNMP | SMUX] [OVER [UNIX | UDP | TCP] [SOCKET | TLI]] [AT ] MANAGER [ON TRANSPORT ] [SEND [ALL | NO | traplist] TRAPS [TO PORT <#> ] [WITH COMMUNITY ]] COMMUNITY ALLOW op [,op]* [OPERATIONS] [AS ] [USE encrypt ENCRYPTION] [MEMBERS [,] ] ALLOW [ON ] WITH [] [] DENY
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 290 UNSPECIFIED SUBAGENTS ::= HOST | UNSPECIFIED HOST[S] ::= PASSWORD UNSPECIFIED PASSWORDS entitySpec ::= AS ENTITY ::= USING TIMEOUT ::= SECOND[S] | NO addr ::= ip-kind ::= | | | | hostid ::= portid ::= | where: hostname is def
B.18 /etc/syslog.conf Use this file to specify the type of logging in the system. If no additional hard disk is installed, logging can be directed to another network attached system; otherwise local files are used. Stanzas in /etc/grcons.log.conf determine how large the respective files may grow and how many versions are kept of them. # NetStar $Id: syslog.conf,v 1.6.4.
#net#cron.info #net#local0.info #net#local1.info #net#local2.* #net#local3.* #net#local4.* #net#local5.* #net#local6.* # # # # # # # # # # # # # # # # @server.domain.com @server.domain.com @server.domain.com @server.domain.com @server.domain.com @server.domain.com @server.domain.com @server.domain.
# Changes to the order of entries or number of ttys should only be made in # single-user mode.
ttyr9 ttyra ttyrb ttyrc ttyrd ttyre ttyrf ttys0 ttys1 ttys2 ttys3 ttys4 ttys5 ttys6 ttys7 ttys8 ttys9 ttysa ttysb ttysc ttysd ttyse ttysf 294 none none none none none none none none none none none none none none none none none none none none none none none network network network network network network network network network network network network network network network network network network network network network network network IBM 9077 SP Switch Router: Get Connected to the SP Switch
Appendix C. Hardware and Software Information Appendix C gives an overview of the LEDs on the front panel of the SP Switch Adapter card and shows tables with the meaning of the LEDs’ blinking patterns. A diagram of the chip interconnections on a TBS Switch Board is provided for a quick reference in helping you to find out the correct Switch port numbers or the correct jack. You will get some information about updating the IBM 9077 software and how to get updates. C.
C.2 SP Switch Router Adapter Media Card LEDs LED activities during operations are listed in Table 52 on page 296 and Table 53 on page 296. LED activities during bootup are described in Table 54 on page 297. Table 52. SP Switch Router Adapter Media Card LEDs LED Description PWR ON This green LED is on when 5 volts are present. 3V This green LED is on when 3 volts are present. RX HB This green LED blinks to show the heartbeat pattern for the receiver.
C.3 SP Switch Router Adapter Media Card - Bootup Table 54 shows the settings for the Switch Router Adapter Media Card LEDs during bootup. Table 54. SP Switch Router Adapter Media Card LEDs During Bootup RX/TX HB (green) RX/TX ST0 (green) RX/TX ST1 (amber) RX/TX ERR (amber) Description on on on on All LEDs are lit for 0.5 seconds during reset as part of onboard diagnostics. off off off on Error condition: checksum error is detected in flash memory.
C.4 Connectors and Receptacles for Different Media Table 55 gives you a comprehensive overview of all the supported cables and connectors for the various media cards. Table 55. Media Card Cables and Connectors Media Card Cable Support Connector SP Switch SP Switch Cable (5, 10, 15, 20m) 2-row, 50-pin shielded tab connector ATM OC-3c Multimode Two 62.
Figure 73. The SP Switch Board C.6 Updating Router Software This part provides general information about obtaining and installing new operating software (hereafter referred to as machine code) for the SP Switch Router. C.6.1 The SP Switch Router as an IBM Product As is noted in this Redbook, the SP Switch Router is based on a product from Ascend Communications, Inc. IBM customers order and receive the SP Switch Router from IBM. IBM provides all support for this product for IBM customers.
SP Switch Routers are delivered with the current level of machine code already installed. Customers who wish to upgrade to new releases of the machine code should contact their IBM representative. C.6.2 Obtaining New Machine Code New releases of the machine code must be obtained from the IBM FTP server: service2.boulder.ibm.com. You are prompted for the SP Switch Router customer ID and password when you ftp to this server.
ftp> ftp> ftp> ftp> cd cd cd cd releases A1_4_6 patches A1_4_6_4 4. Set the file format and download the files: ftp> ftp> ftp> ftp> ftp> # bin get grf_update get RN1_4_6_4.pdf get RN1_4_6_4.txt quit 5. Change the script permissions: # chmod 755 grf_update 6. Install the script: # grsite --perm grf_update 7. Read the documentation with an appropriate reader command ( acroread for the pdf file, more or vi for the txt file)! 8. Run the script: # .
- Ftp access to service2.boulder.ibm.com from testbox.site.com. - Approximately 30MB of disk space in /flash. Please be aware: - testbox.site.com will be REBOOTED if any system software and/or patch file is installed. Please take a moment to ensure that the requirement(s) are met and that testbox.site.com can be rebooted at this time. Continue with upgrade? (y/n): y Release: currently running A_1_4_6,boston. Upgrade needed to 1.4.6.ibm,default Checking for 1.4.6.ibm system release files. testbox.site.
To temporarily disable the directed bcast setting later on, use: # sysctl -w net.inet.ip.fwdirbcast=0 To verify that the bcast setting is one of the sysctl executables, use: # sysctl net.inet.ip.fwdirbcast IBM GRF upgrade: testbox.site.com is up-to-date testbox.site.com will be upgraded to: Next Revision: 1.4.6.ibm Version: default Patch Revision: 1.4.6.4.ibm WARNING: testbox.site.com will now be REBOOTED to complete the upgrade. 10 9 8 7 6 5 4 3 2 1 Continuing ...
304 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Appendix D. Special Notices This publication is intended to help IBM customers, Business Partners, IBM System Engineers and other RS/6000 SP specialist who are involved in SP Switch Router (IBM 9077) projects, including education of RS/6000 SP professionals responsible for installing, configuring, and administering SP Switch Router. The information in this publication is not intended as the specification of any programming interfaces that are provided by POWERparallel System Support Programs.
information or the implementation of any of these techniques is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names may be trademarks or service marks of others.
308 IBM 9077 SP Switch Router: Get Connected to the SP Switch
Appendix E. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. E.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 311. • Technical Presentation for PSSP 2.3, SG24-2080 • Technical Presentation for PSSP 2.4 , SG24-5173 • RS/6000 SP: Problem Determination Guide, SG24-4778 E.
• RS/6000 SP: Diagnosis and Messages Guide Version 2 Release 4, GC23-3899 • RS/6000 SP: Command and Technical Reference Version 2 Release 4 , GC23-3900 • RS/6000 SP: Maintenance Information Volume 1 Installation and Customer Engineer Operations, GC23-3903 • RS/6000 SP: Maintenance Information Volume 2, Volume 3, GC23-3904 • RS/6000 SP Planning Volume 1 Hardware and Physical Environment , GA22-7280 • GRF Configuration Guide 1.4, GA22-7366 • GRF Reference Guide 1.
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at http://www.redbooks.ibm.com/.
How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: • Online Orders – send orders to: In United States In Canada Outside North America IBMMAIL usib6fpl at ibmmail caibmbkz at ibmmail dkibmbsh at ibmmail Internet usib6fpl@ibmmail.com lmannix@vnet.ibm.com bookshop@dk.ibm.
IBM Redbook Order Form Please send me the following: Title First name Order Number Quantity Last name Company Address City Postal code Country Telephone number Telefax number VAT number Card issued to Signature Invoice to customer number Credit card number Credit card expiration date We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment.
314 IBM 9077 SP Switch Router: Get Connected to the SP Switch
EPROM Erasable Programmable Read-Only Memory FIFO First-In First-Out GB Gigabytes GL Group Leader GPFS Abstract Notation Syntax General Purposes File System GRF Goes Real Fast APA All Points Addressable GS Group Services API Application Programming Interface GSAPI ARP Address Resolution Protocol Group Services Application Programming Interface GVG Global Volume Group hb heart beat HiPS High Performance Switch List of Abbreviations ACL Access Control List AIX Advanced Interact
LRU Last Recently Used RCP Remote Copy Protocol LSC Link Switch Chip RM Resource Monitor LVM Logical Volume Manager RMAPI MB Megabytes Resource Monitor Application Programming Interface MIB Management Information Base RPQ Request for Product Quotation MPI Message Passing Interface RSI Remote Statistics Interface MPL Message Passing Library RVSD Recoverable Virtual Shared Disk MPP Massive Parallel Processors SAS Single Attach Station SBS Structure Byte String MTU Maximum Tran
Index Symbols /etc/bridged.conf 144, 145, 146, 148, 149, 181, 216, 218, 264 /etc/fstab 77, 267 /etc/grarp.conf 112, 115, 138, 149, 154, 217, 219, 229, 267 /etc/gratm.conf 111, 112, 113, 115, 121, 151, 212, 217, 218, 224, 225, 268 /etc/grclean.conf 78, 274 /etc/grclean.logs.conf 78, 275 /etc/grdev1.conf 86, 87, 88, 96, 277 /etc/grifconf.conf 130 /etc/grifconfig.conf 86, 87, 93, 95, 105 , 106, 107, 110, 115, 121, 127, 128, 129, 138, 139, 140, 150, 182, 193, 200, 205, 213, 218, 225, 229, 282 /etc/grlamap.
config_netstat 70 csconfig 79 dev1config 87, 95 Eannotator 82 Efence 51, 99 Efence -autojoin 99 Eprimary 51 Estart 51, 99, 101 Eunfence 51, 99, 101 gratm 116, 121 grcard 97, 98, 101, 109 grconslog 79 grf_update 301 grifconfig 94 grreset 95, 97, 99, 109 grrmb 109 grrt 118, 132 grsite 96 grsite --perm 77, 96 grsnapshot 97 grstat 99, 119, 133 grwrite 79, 107, 109 grwrite -vn 96 ifconfig 10, 94 iflash 77 lsdev 168 maint 116, 131 no 95 pax 77 perspectives 3, 52 ping 97, 160 ping -P grid 97, 98 reboot 79 route 10
F fault service daemon 4 FDDI 6, 16, 18, 39, 66, 69, 121 , 122, 125, 129, 142, 157, 163, 174, 209 backbone 126, 155, 174, 177, 179, 181 concentrator 126 dual attached station 121 dual homing 125 interface 128 media card 162, 165, 176 single attached stations 121 FDX 105, 108 Fiber Distributed Data Interchange see FDDI fiber optic attachment 127 FIFO 38 filtering table 144 fragmented 95 Frame Relay 95 G gateway 10, 13 gr.conferrs 76 gr.
33, 34, 36 slot 66 31 IP traffic 7, 8, 11, 12, 15, 194 IPv4 142, 143 IS-IS 15, 23 J jack 82 Jack Number 84 K media statistics 109 MIB 59 mib2d 100 microchannel 6 microchannel bus 16 microcode lookup 28 mrouted 22 MTU 95, 113, 114, 115, 121, 129, 130, 138, 140, 145, 148, 191, 213 default 94 discovery 95 size 19, 87 keep-count 107 N L Layer 2 14 Layer 3 14, 19 LLC 142, 144, 150, 151 load profile 107, 108 log files gr.boot 76 gr.conferr 76 gr.console 76 grinchd.log 76 gritd.packets 76 mib2d.
disk 75, 76, 79 interface 79 modem card 34 slot 34 performance limitation 7 Permanent virtual circuits 112 perspectives 52, 56 physical interface 112, 127 physical interface number 127 point-to-multipoint 119 point-to-point 115, 119 point-to-point connection 111 Primary Backup 51, 61 primary node 61, 69, 84, 85 primary router 66 Protocol Data Unit 152 protocol layer 143 PVC 112, 113, 116, 121, 151, 153, 154, 169 Q QBRT 28, 29 , 30 Quick Branch Routing Technology see QBRT R receive buffer 19, 28 Receive
16-port 3 8-port 3 adapter card 28 cable 81 network 12 port 41, 63, 75, 81 router 5, 25, 66 router adapter 5, 12, 36, 37, 41, 48, 58, 59, 61, 64, 65, 69, 70, 74, 75, 76, 79, 80, 81, 85, 87, 88, 89, 94, 95, 96, 98, 100, 101, 102, 158, 162, 165, 167, 174, 189, 194, 203, 211, 212, 227 router adapters 17 spamming 145 spanning tree 144 Spanning Tree Algorithm 144 spanning tree controls 144 state machine 100 subarea 22 subnet 9, 20, 210 subnet masking 19, 20 subnetting 9, 10, 198 supernetting 20 SVC 112, 113, 121
ITSO Redbook Evaluation IBM 9077 SP Switch Router: Get Connected to the SP Switch SG24-5157-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: • Use the online evaluation form found at http://www.redbooks.ibm.com • Fax this form to: USA International Access Code + 1 914 432 8264 • Send your comments in an Internet note to redbook@us.ibm.
SG24-5157-00 Printed in the U.S.A.
