Avaya BCM Management Betriebsanweisung PDF herunterladen (Seite 104)

100 Chapter 2 Fault Management System

P0609330 2.0

Component ID/SNMP Trap Error Interpretation

Use the information in this section to interpret the message displayed in the message field for all

the Component ID / SNMP Traps.

Some error strings are specific to certain Component IDs and hence, the descriptions are more

specific. Other descriptions are generic and the description can be applied across all instances

regardless of the Component ID/ SNMP Trap error.

SNMP traps received from Business Communications Manager contain descriptions of the alarms

that occurred in the system. These SNMP traps consist of the following Business Communications

Manager-specific parameters in addition to the generic parameters. Refer to the IETF RFCs on

SNMP traps for descriptions of these generic parameters. Additionally, SNMP generic traps such

as coldStart, linkDown, linkUp, authenticationFailure, are also generated from the Business

Communications Manager according to the user's configuration. For details of these SNMP

generic traps, refer to the relevant IETF RFCs.

Message (error string) Description

<error string provided by CFS> All those errors match internal CFS errors. If they occur, there is something

wrong internally (i.e. no memory to allocate buffers, etc.). When those

occur, that means there is usually something else wrong with the system.

Contact your support organization for help.

%1, %2, etc. Placeholders for values passed to the event message. This is the syntax

used by the Event Log APIs in order to pass values into the string. If they

appear without the correct text, then there is something wrong with how

that value is passed.

Established IPsec SAs on

<local IP Addr> with <remote

IP Addr>: AH

outbound SPI <Hex Number>,

AH inbound SPI <Hex

Number>.

The Inbound and Outbound SPI (Security Policy Index) is a unique number

that is assigned to each IPSec QuickMode connection.

BCM has no IP Address on the

IPSec Client private network:

IP Address: %1 IP Mask: %2.

IP Addresses and masks in hexadecimal format. The example is the IP

Address and subnet mask of the IP Address that will be given to the VPN

client when they connect

Error notification (%d) received

on <local IP Addr> from

<remote IP Addr

These are the error notification messages as specified in the IPSec RFC

2401 - 2412.

Established IPsec SAs on

<local IP Addr> with <remote

IP Addr>: AH

outbound SPI <Hex Number>,

AH inbound SPI <Hex

Number>.

The Inbound and Outbound SPI (Security Policy Index) is a unique number

that is assigned to each IPSec QuickMode connection.

Oakley %d Mode proposal

accepted on <local IP Addr>

from <remote IP Addr>.

The %d should either display the text "Main" or "Aggressive" Main is for

Branch Office connections and Aggressive is for VPN client connections. If

it doesn't display one of these then it's an error.

1 2 ... 99 100 101 102 103 104 105 106 107 108 109 ... 487 488

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya BCM Management Betriebsanweisung Seite 104

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Gateways / Controller Avaya BCM Management