Allied Telesis AT-8900 Series manual Following up theories

Page 3

show ip count

show pim route

show pim count

show pim neighbour

and other commands relevant to the hardware forwarding of multicast in the particular models of switch you are working with.

Once this initial survey is complete, you can start following up your theories about what is going on.

Following up theories

Starting from the symptoms of problem, you can work back through the steps in the networking process to think of various points where something could have gone wrong, and follow up on each of those in turn.

For example, if the symptom is that a certain client never receives multicast streams, then the problem could be:

zthe client is failing to send the IGMP report; or

zthe client is sending the report, but it is being dropped by a switch between the client and the device running PIM; or

zthe IGMP report is reaching the PIM router, but a multicast route is not being created; or….

So, the approach is to follow each of these possibilities—capturing counters, enable debug outputs, ethereal traces, etc to confirm or deny each one. When a particular possibility looks fruitful, then dig deeper into it to try and narrow down more accurately what is not happening correctly. For example, if you see that the IGMP report is not being seen by a particular switch in the chain, you might be able to find that an error counter in the show switch port count output increments every time you try sending the IGMP report, indicating that the reports are being corrupted.

Concrete piece of advice #3: Type your thoughts and actions.

It is important to always keep in mind that it is quite likely that your debug capture will be analysed by someone else later on (or, in fact, you might need to go back through it later yourself). Therefore, it is necessary to record your thinking and actions as you were going along, to give context to all the debugging that was captured.

This achieves two main aims:

zit makes it clear why you were looking at particular counters etc

zit makes it clear how the captures relate to external events. So often it is vital to know whether a particular state change or counter change seen in the debug capture happened before or after a particular external event. For example, 'did that switch port on blade 6 go into STP blocking state before or after port 24 on blade 5 was unplugged..'.

3

Image 3
Contents Introduction Best Practice On-Site DebuggingConcrete piece of advice #1 Capture everything Concrete piece of advice #2 Capture the initial stateStarting off Following up theories Concrete piece of advice #3 Type your thoughts and actionsWhat counters are changing? Annotating afterwards Providing a convincing case

AT-8900 Series specifications

The Allied Telesis AT-8900 Series represents a cutting-edge solution in the realm of networking, designed to meet the demands of modern enterprises that require high-performance, reliable, and flexible networking options. This series encompasses a range of intelligent Layer 2 managed switches that cater to various applications, from small offices to large data center environments, offering a robust blend of performance, features, and advanced technologies.

One of the key features of the AT-8900 Series is its comprehensive support for Layer 2 switching protocols. These switches enable efficient data handling and traffic management, ensuring that businesses can maintain high data throughput without sacrificing reliability. This is particularly important for organizations that depend on stable network performance for mission-critical applications.

Another significant characteristic of the AT-8900 Series is its advanced Quality of Service (QoS) capabilities. With multiple queue scheduling options, the switches can prioritize essential data traffic intelligently. This ensures that latency-sensitive applications, such as VoIP and video conferencing, receive the bandwidth they require for optimal performance. The QoS features help to create a seamless user experience across various devices and applications.

Additionally, the AT-8900 Series incorporates cutting-edge security measures that are vital in today’s increasingly sophisticated network environment. Features such as IEEE 802.1X port-based authentication, dynamic VLAN assignment, and secure management protocols contribute to the prevention of unauthorized access. These security protocols give network administrators the tools they need to protect sensitive data and maintain compliance with regulatory standards.

The AT-8900 Series switches also support stacking technology, allowing multiple units to operate as a single logical switch. This simplifies management and increases redundancy, ensuring that network uptime is maximized. Stacking enables easy scalability, allowing organizations to expand their network infrastructure seamlessly as their needs grow.

Energy efficiency is another hallmark of the AT-8900 Series. These switches boast low power consumption modes that help organizations reduce their carbon footprint while saving on energy costs. With features such as Energy Efficient Ethernet (EEE), the AT-8900 Series aligns with modern sustainability initiatives.

In conclusion, the Allied Telesis AT-8900 Series is a powerful and versatile choice for organizations seeking advanced network solutions. With its rich feature set, robust security, efficient traffic management, and scalability, this series stands out as an ideal option for enterprises looking to enhance their network infrastructure in a rapidly evolving digital landscape.