
130 Chapter 2 Fault Management System
P0609330 2.0
IPXRouterManager
Event ID: 35 Message: BCM interface that IPSec client is trying to connect to (%1) is on the
private network (%2).
User action: PC IPSec Client should connect to a different interface on the BCM.
Alarm severity: Critical
Trap-type: Error
Logs: None
Event ID: 36 Message: The IP Address of the PC running the IPSec client (%1) is on the
private network (%2).
User action: PC IPSec Client is not on the correct network.
Alarm severity: Critical
Trap-type: Error
Logs: None
Event ID: 37 Message: IPSec Client connection request on %1 from %2 Rejected. BCM only
supports IPSec Client connection requests from PCs on a different
subnet that come in over the Interface connected to the Next Hop
Router.
User action: If there is a router between the PC running IPSec client and the
interface you are trying to connect to on the BCM, then the
NetLinkManager needs to be defined to use this interface in order to
support IPSec Client.
Alarm severity: Critical
Trap-type: Error
Logs: None
IPXRoutManager Return to table: Component ID (alarm)/eventSource (trap) summary
Return to table: Component ID alarms/eventSource (Trap) by event ID
Service: Routing and remote access service
Event ID: 20133 Message: IPX Routing failed to start because IPX forwarder driver could not be
loaded.
User action: Refer to Microsoft article Q180602. If the solutions provided in the
article do not work, please re-install IPX. Contact Support.
Alarm severity: Critical
Trap-type: Error
Logs: None
IPSecIKE
(Internet
protocol
security -
Internet key
exchange)
Return to table: Component ID (alarm)/eventSource (trap) summary
Comentários a estes Manuais