2.Isolate any new modules that have logical ports on the ring (logical is a port which cannot be disabled such as TRMM or bridge).

3.If the source or destination address in the packet is external to the hub, wait for up to 5 seconds to check if the beaconing can be disabled externally.

4.If the source or destination address in the packet is external to the hub, disable all external trunks.

5.Disable any enabled ports on fiber repeater (these ports may show as external if both sets of trunks on the fiber repeater are enabled).

6.Disable any enabled ports that are between the source and destination addresses contained in the beaconing packet.

7.Isolate any modules that are between the source and destination addresses contained in the beaconing packet.

8.If both addresses are internal to the hub and there are enabled trunks in between, disable the trunks.

9.Disable port corresponding to destination address.

10.If the destination in beaconing packet is external, shut down all external trunks *.

11.Disable the port corresponding to the source address.

12.If the source of beaconing packet is external, shut down all external trunks *.

13.If any MAC-less devices are present on the ring, disable the

ports corresponding to these devices.

14.Disable external trunks again to test for condition where beaconing was fixed temporarily externally *.

15.Isolate modules one at a time until beaconing is detected to be gone. If beaconing goes away put module back on network and disable ports on that module until beaconing goes away. When beaconing ends, the correct port has been found.

16.Isolate the TRMM if all else fails.

*When external trunks are disabled and the disabling fixes the beaconing problem perform the following:

∙

∙

∙

Re-enable all trunks with external beacon recovery non_exists.

If no beaconing, re-enable trunks with external beacon recovery exists.

If beaconing now detected, shut down all trunks with external beacon recovery exists. Re-enable trunks one at a time until source of beaconing is detected and then disable that trunk.

∙If beaconing when trunks with external beacon recovery non_exists are re-enabled, then disable all these trunks. Re-enable trunks with external beacon recovery exists.

In case the NAUN of the station issuing Beacon MAC frame is the TRMM itself, the TRMM will take itself off the ring to perform the self-test as any other station. If there is no problem with TRMM, it re-enters the ring. However, if a problem is found in TRMM, it will stay off the ring and isolated. In this case the beacon problem is resolved, but the ring is now operating without TRMM and if another station causes a beacon condition that requires TRMM intervention the operation of the ring will be disrupted.

Chapter 8. 8260 Token-Ring Support 153

Page 174 Page 176
Page 175
Image 175
IBM 8260 manual Token-Ring Support
Page 174 Page 176

8260 specifications

The IBM 8260 is a significant entry in the realm of enterprise servers, recognized for its performance, scalability, and robust features designed to cater to demanding business environments. It primarily serves as a high-capacity server for large organizations, capable of handling extensive workloads and complex applications without compromising speed or efficiency.

One of the standout features of the IBM 8260 is its powerful processing capabilities. It typically comes equipped with multiple processor units based on the IBM POWER architecture, which is renowned for its high-performance computing. This architecture allows the server to execute numerous simultaneous tasks, making it ideal for environments that require multitasking and high throughput.

Memory capacity is another key characteristic of the IBM 8260. Depending on the specific configuration, it can support substantial amounts of RAM, ensuring that applications can run effectively without the bottlenecks often associated with data-intensive tasks. This is crucial for enterprises that rely on real-time data analytics, large database management, and resource-heavy applications.

In terms of storage, the IBM 8260 offers flexible options. It supports a variety of storage solutions, including solid-state drives (SSDs) and traditional hard drives, catering to different performance and capacity needs. This scalability in storage helps organizations manage their data effectively while ensuring quick access and retrieval times.

Connectivity is also a prominent feature of the IBM 8260. The server includes advanced networking capabilities, supporting various protocols and technologies that facilitate fast data transfer and communication between devices. This enhances overall network performance, essential for businesses that depend on cloud computing and distributed computing environments.

Additionally, the IBM 8260 is designed with a focus on reliability and availability. It incorporates redundant components, such as power supplies and cooling systems, minimizing the risk of downtime. This is critically important for enterprises that require continuous availability of services.

The server’s management features are also noteworthy. IBM provides a suite of management tools that allow IT administrators to monitor performance, configure hardware settings, and troubleshoot issues seamlessly. This ease of management is bolstered by automation capabilities, enabling organizations to enhance operational efficiency.

In conclusion, the IBM 8260 stands out in the competitive server landscape due to its high processing power, extensive memory and storage options, advanced connectivity, reliability features, and robust management tools. Such attributes make it a viable choice for organizations seeking to enhance their IT infrastructure and streamline their operations effectively.
Top Page Image Contents