Welcome to Infoblox NetMRI Community Sign in | Join | Help
in Search

Applied Infrastructure

Config Policy and Operational Data

I've written before in Subsystem Configuration Policy Check about incorporating operational data with configurations for performing configuration compliance validation.  Another example, with a different twist to it, occurred last week while creating an NTP policy check on a customer's network.  The NTP design is three layers.  There are two stratum 1 clocks, one per data center.  Within each data center is a core 6500 that uses the master clock within the data center as its clock source.  There is a large set of distribution layer devices that reference the core 6500s as ntp servers using the following configuration:

ntp server 10.1.1.1  ! Datacenter 1 6500
ntp server 10.1.2.1  ! Datacenter 2 6500

 Validating the configurations of the distribution layer devices is pretty easy.  Create a device group of all core and distribution devices, exclude the two core 6500s, and check that the configurations include the above commands.  It is good practice to make sure that there are no other NTP configuration statements in the configs.

The catch comes with the edge devices.  The network is running MPLS and the CE devices may not have a route to the core 6500s.  So the CE devices are configured to use their neighboring PE devices (the distribution layer), as their clock source.  The IP address in the NTP configuration statement depends on the address of the neighbor.  The configuration policy validation system needs to run some commands on the CE device to determine the PE's address (e.g., show cdp neigh detail), then check the configuration for the NTP statement that uses that address.  This is a simple case of configuration compliance; I envision some configuration checks that might need the output and merger of multiple commands in order to determine the required configuration statements.

The important concept with this example is that configuration policy checking isn't just about looking for a few commands in the configuration.  The policy compliance system needs the ability to incorporate operational and as-built data into its compliance checks.

  -Terry

 

Comments

No Comments

About tslattery

Terry Slattery, CCIE #1026, is a senior network engineer with decades of experience in the internetworking industry. Prior to joining Chesapeake NetCraftsmen as a full time consultant, Terry was the founder and CTO of Netcordia, and inventor of NetMRI, a suite of network management products. Terry started Netcordia as a consulting company in 2000 and transitioned to a network management product company in 2003. During the consulting days, he used his network design and implementation skills to lead a team in the design and implementation of a high availability network at a brokerage clearing house. Terry is the former President and founder of Chesapeake Computer Consultants, Inc., a networking and computer systems training and consulting company. He co-invented and patented the vLab(tm) internet-based remote lab system. He is co-author of the McGraw Hill text Advanced IP Routing in Cisco Networks. Terry led the team that developed the current Cisco IOS user interface under contract to Cisco Systems. Terry is experienced in the design and installation of large TCP/IP based networks and is a successful network protocol instructor. He is the second Cisco Certified Internetworking Expert (CCIE) #1026 and the first outside of Cisco. He enjoys membership on the Vanderbilt University Engineering School’s Industrial Advisory Board and the IEEE.

This Blog

Syndication