Skip to main content

Cisco ACI - NTP Configuration

Time and tide wait for none.. definitely not for your Application Centric Infrastructure (ACI)!!

NTP configuration should always be at the top of your list of configuration items, after you un-box your appliance. I won't delve into the reasons for doing this (imagine carrying your cell phone with wrong time).

Disclaimer: The NTP configuration for ACI(just like other configuration in ACI), is not a simple affair, as you would see it below:

  1. Login to APIC (obviously)
  2. Under Fabric >> Select Fabric Policies >> Quickstart >> Configure an NTP policy.
  3. Name the policy and click Next

  • Under NTP Servers, click on the "+" icon and select the NTP server.. can be FQDN or an IP address.. Here I am using
  • Use "Management EPG" only if the NTP server is outside the fabric. Click OK and then finish. The NTP policy should now be visible under "Pod Policies".

It's not over yet.. There is more work to be done! The ACI policy configuration requires stitching of the policy and the pod-profile, So let's do that.. (Policy usage in a particular profile can be checked from that policy using "Show usage")

Creating POD policy:

  1. Under Fabric >> Fabric Policies >> Pod Policies >> Policy Groups
  2. Click on Actions and create a new pod policy group. Select the aforementioned NTP policy under "Data Time Policy".
  3. Create a new Pod Profile and reference the pod policy group created above, and Submit.


"show ntp" from APIC CLI to see if the APIC has synchronized with NTP server


Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o

Tejas Jain - GCP Constraints & Random Facts

1.  Google Cloud Interconnect Security Cloud Interconnect does not encrypt the connection between your on-premises network and Google's network. Cloud VPN cannot be used with Dedicated Interconnect For additional security, use application-level encryption or your own VPN 2. While using Cloud CDN, the default time-to-live (TTL) for content caching is 3600 seconds = 60 mins 3. Cloud NAT sends only the translation logs and error logs to Cloud Logging service. 4. GCP Dedicated Interconnect - On Premises network device requirements:     10-Gbps circuits, single mode fiber or 100-Gbps circuits, single mode fiber     IPv4 link local addressing     LACP, even if you are using single circuit     EBGP-4 with multi-hop     802.1Q VLANs 5. While using Cloud VPN, the recommended MTU to be configured on the peer VPN  gateway = 1460 bytes 6. Each instance must have at least one network interface. The maximum number of network instances per instance is 8, depending on the instance's machine

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s