18.07.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Troubleshooting NTP<br />

Troubleshooting<br />

NTP<br />

F-34 Basic Troubleshooting<br />

Interface configuration issues with HA<br />

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

not function until you update the HA Interfaces table (in the Admin<br />

Console, select High Availability -> Common Parameters tab) to match<br />

the modified interface configuration. When you are finished updating<br />

the interface information, reboot the <strong>Sidewinder</strong> <strong>G2</strong>s.<br />

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

HA<br />

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

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

an interface failure (after the specified number <strong>of</strong> failed ping attempts<br />

is reached) and failover will occur. When this happens, the new<br />

primary will receive the interface failure status from the former<br />

primary, and interface failure testing will be disabled. In this state, the<br />

standby will take over for the primary only if the primary becomes<br />

unavailable.<br />

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

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

to reset and re-enable the interface failover indicators.<br />

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

to monitor NTP packets being sent/received on the appropriate<br />

<strong>Sidewinder</strong> <strong>G2</strong> 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<br />

example 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<br />

known 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 you<br />

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

not start.

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

Saved successfully!

Ooh no, something went wrong!