Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Instrukcja Naprawy Pobierz pdf (Strona 16)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

 scripting errors.

 configuration manager.

Cause – Scripting Errors

One of the initialization/engineering/health monitoring scripts has errors, causing the SPF to

crash.

Resolution – Verifying Scripts

You need to correct the faulty script.

Note: Usually you can access the scripts (SDC Life Cycle; Health Monitoring, Engineering)

from the Web UI. However, because FEP/CPF are not running, they cannot accept any

configuration changes

 To correct the scripts:

1. Shut down all SDC processes (including config manager).

2. Locate and correct the script errors in the most recent flowManager.xml file (of

each FEP/CPF).

3. Check the scripts in the following XML hierarchy:

- FlowManagerMgmt/Administration/PostSystemInit

- FlowManagerMgmt/Administration/StatusCheck/Condition+CheckStatus

Cause – Configuration Manager

The SDC component (CPF) is unable to retrieve its configurations from the config manager.

By default, the connection between each SDC component and the config manager is done

using a multicast auto discovery mechanism.

When this occurs the following message is the last message in the log file after the component

was started:

2013-12-15 09:19:17,123 INFO [] Starting beans in phase 2147483647 [main_1]

[DefaultLifecycleProcessor$LifecycleGroup.start()]

Resolution – Configuration Manager

 Check that the configuration files are configured to use multicast

1 2 ... 11 12 13 14 15 16 17 18 19 20 21 ... 41 42

Brak uwag

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Instrukcja Naprawy Strona 16