18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix F: Basic Troubleshooting<br />

Troubleshooting NTP<br />

Troubleshooting<br />

NTP<br />

666<br />

Interface configuration issues with HA<br />

If you modify your interface configuration, your HA configuration will not<br />

function until you update the HA Interfaces table (in the Admin Console, select<br />

High Availability > Common Parameters tab) to match the modified interface<br />

configuration. When you are finished updating the interface information, reboot<br />

the <strong>Sidewinder</strong> <strong>G2</strong>s.<br />

Troubleshooting remote interface test failover for peer-topeer<br />

HA<br />

If you have a peer-to-peer HA cluster configured and the remote host used for<br />

interface testing becomes unavailable, the primary will report an interface<br />

failure (after the specified number <strong>of</strong> failed ping attempts is reached) and<br />

failover will occur. When this happens, the new primary will receive the<br />

interface failure status from the former primary, and interface failure testing will<br />

be disabled. In this state, the standby will take over for the primary only if the<br />

primary becomes unavailable.<br />

Once the remote host is restored, you will need to issue the cf failover<br />

reset command on the standby, and then on the primary to reset and reenable<br />

the interface failover indicators.<br />

If you have NTP properly configured and enabled, you should be able to<br />

monitor NTP packets being sent/received on the appropriate <strong>Sidewinder</strong> <strong>G2</strong><br />

interfaces. To do so, enter the following command:<br />

tcpdump -npi ext_interface# port 123<br />

where: ext_interface# is the external interface and number (for example<br />

em0, em1, etc.)<br />

NTP packets should be sent/received every 15-30 seconds.<br />

To check the exact time, enter the date command and compare it to a known<br />

good clock source (for example, www.time.gov).<br />

Note: An NTP proxy and an NTP server cannot run in the same burb. Therefore, if<br />

you have a proxy enabled and running in the same burb as the NTP server, the<br />

NTP server will not start.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!