Routing; Service Functions; Diagnostics; Diagnostic Environment - IBM 3534-F08 Installation And User Manual

Routing

The embedded processor maintains two routing tables, one for unicast and one for
multicast. The unicast routing tables are constructed during fabric initialization. The
multicast tables are initially empty, except for broadcast. After the tables have been
constructed, they are loaded into each ASIC.
The unicast tables change if ports or links come online or go offline, or if some
other topology changes occur. When new paths become available, the embedded
processor can change some routes in order to share the traffic load. The multicast
tables change as ports register with the alias server to create, join, or leave a
multicast group. Each time a table changes, it must be reloaded into the ASICs.

Service functions

The ASIC interrupts the embedded processor when a frame arrives that has an
error (for example, incorrect source ID), when a frame times out, or when a frame
arrives for a destination that is not in its routing tables. In the latter case, the frame
might be addressed to an illegal destination ID, or it might be addressed to one of
the service functions that the embedded processor provides, such as SNMP, name
server, or alias server.
SNMP
Simple Network Management Protocol (SNMP) allows network devices to be
monitored, controlled, and configured remotely from a network management station
running a network manager program.
SNMP agent code in the network device allows management by transferring data
that is specified by a management information base (MIB).
The 3534 Model F08 agent supports the following functions:
v SNMPv1 manager
v Command-line utilities to access and command the agent
v MIB-II system group, interface group, and SNMP group
v Fabric-element MIB
v IBM-specific MIBs
v Standard generic traps
v IBM-specific traps

Diagnostics

The 3534 Model F08 supports a set of POSTs, as well as tests that you can run by
using Telnet commands. These diagnostics are used during the manufacturing
process as well as for fault isolation of the product in your installation.
For more information, see the Brocade Diagnostic and System Error Message
Reference.

Diagnostic environment

Most diagnostics are written to run in the VxWorks environment. However, as
VxWorks does not run without a working SDRAM, a SDRAM/boot EEPROM test is
run as part of the pre-VxWorks startup code to verify that the basic
processor-connected memories are functioning properly.
11
Chapter 1. Introduction