Avaya Configuring SNMP, RMON, BOOTP, DHCP, and RARP Services Uživatelský manuál Strana 56

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 148
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 55
Configuring SNMP, RMON, BOOTP, DHCP, and RARP Services
2-24 114070 Rev. B
Alarm and Event Groups
When you enable the Ethernet DCM, the router does not create default Alarm or
Event entries. We recommend that you create Alarm and Event entries using a
network management application.
You can create as many Alarm or Event entries as memory permits, up to the
RMON limit of 65,535 entries. The memory limitation for Alarm and Event
groups is based on the memory resources allocated on the router base module
rather than the Ethernet DCM memory resources. The RMON Alarm and Event
groups are maintained by the router base module. All other RMON groups are
supported on the Ethernet DCM.
Each Alarm entry requires 232 bytes. Each Event entry requires 542 bytes.
The Log Table can accommodate up to 65,535 entries. Each entry in the Log Table
requires 267 bytes. You cannot delete log entry rows. Therefore, as events are
triggered and the event type specifies logging, the Log Table increases in size.
Although there is no way to delete a specific log entry, all log entries in the Log
Table corresponding to a single event entry are deleted when the event entry is
deleted.
BOOTP Relay Agent Overview
BOOTP is built on the client-server model and allows a diskless client to boot
remotely from a server on the same network or on a different physical network.
The client broadcasts a request to boot from a remote server. When a suitable
server receives the BOOTREQUEST packet, it responds to the client by issuing a
BOOTREPLY packet, which includes the client’s IP address, the address of the
gateway, and the address of a server. The server then transmits the boot file to the
client via a transfer protocol, such as Trivial File Transfer Protocol (TFTP).
Figure 2-4 illustrates how BOOTP works when the client and the server are on the
same network. The client transmits a BOOTREQUEST packet to the IP broadcast
address (255.255.255.255). The server sends a BOOTREPLY packet to the client.
Depending on the server’s implementation, the server addresses the packet to
either the broadcast or the client’s IP address.
Zobrazit stránku 55
1 2 ... 51 52 53 54 55 56 57 58 59 60 61 ... 147 148

Komentáře k této Příručce

Žádné komentáře