Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Anleitung zur Fehlerbehebung PDF herunterladen (Seite 18)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

- FlowManagerMgmt/Administration/PostSystemInit

- FlowManagerMgmt/Administration/StatusCheck/Condition+CheckStatus

Cause – Configuration Manager

The SDC component (FEP) 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.

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

 Check that the problem is related to the config manager

For more information, contact F5 Technical Support.

4.5.2 Virtual Server Unable to Bind Address

Virtual server does not succeed to bind to address that it is configured to listen to. This is

relevant to both TCP and SCTP.

Note: This problem was found in a SDC running on a Redhat 6.3 installation.

Causes

 The machine is not listening on the selected port. There is another process,

possibly another SDC virtual server that already binds to the same IP and port.

 Failure happens when at least one TCP connection was in an Established or

Time Wait state, suggesting an OS configuration issue.

Symptoms

The following error message appears in the FEP logs:

 “Virtual Server {0} bind attempt failed. Cause: {1}. Verify that the port is not

used by any other Virtual Server”.

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 41 42

Keine Kommentare

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Anleitung zur Fehlerbehebung Seite 18