Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 32

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 306
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 31
Avaya Media Processing Server Series System Reference Manual
Page 32 # P0602477 Ver: 3.1.11
System LAN Interface
The TMS interfaces with the system Local Area Network (LAN) via Ethernets using
TCP/IP. The chassis Ethernet is connected via the VRC backplane to separate hubs on
the chassis NIC or Hub-NIC (see VRC Rear View on page 24). If there is a failure on
the master Ethernet (controlled by the first NIC), the secondary NIC takes control of
all Ethernet A, system clocking, and ATM functions. The switchover is virtually
instantaneous and the inherent error correction of TCP/IP prevents loss of data.
The redundant Ethernet is only for backup of the primary Ethernet. Ethernet A
is the ONLY Ethernet supported between the chassis and the Application
Processor. There is no support for dual redundant Ethernet.
Field Programmable Gate Arrays (FPGA) and the Boot ROM
The TMS and the modules that plug into it (i.e., DCC, MDM, and ALI) contain
FPGAs. An FPGA is a generic microchip that has no inherent functionality. It
contains arrays of generic logic elements (e.g., gates) that are software configurable.
The software that configures the FPGA is called an image, and the image typically
commands the FPGA to assume the functionality of a designed logic circuit. A
hardware architecture based on FPGAs is very powerful and flexible because:
A greater degree of complex logic functionality can be achieved in a
relatively smaller board space with fewer circuit components than if dedicated
circuit components and hard board wiring were used. This also provides
greater circuit reliability.
Functionality can be enhanced without hardware redesign or even removal
and replacement. Upgrades can be done in the field by loading a new image
definition.
FPGAs are dynamic devices in that they do not retain their image definition when
power is removed. The image definition for each device is loaded from an image
definition file (*.idf) during the system boot sequence. The TMS contains a boot
ROM that statically stores the names of the .idf files for the devices contained on its
motherboard and the modules that are plugged in.
Whenever a new system is installed, has components added or replaced, or the system
is upgraded, the boot ROM should be verified and, if necessary, modified by Certified
Avaya Support Personnel. Details concerning boot ROM verification can be found at
Verifying/Modifying Boot ROM Settings on page 252.
Vista de pagina 31
1 2 ... 27 28 29 30 31 32 33 34 35 36 37 ... 305 306

Comentarios a estos manuales

Sin comentarios