XMLbased Network Management Rob Enns rpejuniper net Introduction

XML-based Network Management Rob Enns rpe@juniper. net

Introduction u Routers are complex devices that are hard to manage remotely v Traditional management methods are SNMP and expect, their strengths and weaknesses are well-known Operators and network management software vendors demand a secure, stable method to manage routers u Want network-oriented solutions, not single-box ones u XML is an alternative with exciting possibilities u

XML Extensible Markup Language u XML is a generally self-describing data format u v u Application reads data, parses it, and knows exactly what each constituent part of the data means An XML document is a “text file with structure” Easy to understand v Easy to parse v Easy to debug v u Widely implemented standard v http: //www. w 3 c. org/xml

Why XML? u Network devices are good at generating large amounts of hierarchical data v Device configurations v Routing tables v Interface hierarchies v Billing records u XML is good at describing hierarchical data in a standard way

XML Elements u Six main constructs v v v Open tags: <tag> Close tags: </tag> Data: <tag>data</tag> Empty tags: <tag/> Attributes: <tag foo=“bar” goo=“gar”/> Namespaces: <home> <address>123 Main Street</address> <network xmlns: ns 2=“my. identifying. string”> <ns 2: address>10. 0. 0. 1</ns 2: address> </network> </home>

XML Example <? xml version="1. 0" encoding="UTF-8"? > <route> <destination>10. 3. 1. 1/32</destination> <route-entry> <current-active/> <protocol-name>BGP</protocol-name> <preference>170</preference> <age seconds="1749">00: 29: 09</age> <local-preference>100</local-preference> <learned-from>10. 17. 136. 2</learned-from> <as-path>1403 170 39 I</as-path> <nh> <selected-next-hop/> <to>192. 168. 1. 254</to> <via>ge-0/0/0. 0</via> </nh> </route-entry> </route>

Advantages of XML u Handles forward and backward compatibility u Widely available tools u Widely implemented standard v http: //www. w 3 c. org/xml

DTDs and XML Schemas u XML data definition tools v Document Type Definitions (DTDs) u Lists the elements that may appear in an XML document and their relationships to one another v XML Schemas u Defines content and semantics in addition to element relationships u Simple and complex data types, value ranges, match expressions, documentation

XSL u XML Stylesheet Language Originally intended for rendering XML v Powerful enough for generic transformations v Two branches of the technology v u XSLT – XSL Transformations XML->XML transformations v Add additional information v Remove uninteresting elements or attributes v Rearrange hierarchies, sort elements, lots of party tricks v u XSL-FO v – XSL Formating Objects Render XML into XHTML or PDF

XSL Functionality XSLT Stylesheet <TD> MTU: <xsl: value-of=“. ”/> </TD> XML Input Document <mtu> 1500 </mtu> XML Output Document XSLT Processor <TD> MTU: 1500 </TD> XSLT can make: XML, XHTML, Text, SVG, XSLT

XPath u u u A standard for describing parts of XML documents Uses “Unix-like” path expressions Basic expression and function support Used by XSL Select the serial number of every chassis component v u Select every chassis component with a temperature attribute greater than 40 degrees v u /chassis-inventory/chassis-module/serial-number chassis-module[@temperature > 40] Get the status of power supply B v chassis-module[name="Power Supply B"]/status

Using XML for Network Management u Network Monitoring u Device Configuration u Network Provisioning u Fault diagnosis

Network Monitoring Applications periodically fetch operational content u Compare against historical data using XML diff tools, or transform data into a more appropriate format using XSLT u Use XSL to render output u Web page (XSLT) v Email (XSLT) v Report PDF (XSL-FO) v u Example: Collecting hardware inventory

Hardware Inventory. . . . u Router A Retrieve inventory data from network Router Z XSL Transformation Transform data into format required by inventory DB u u Inventory DB Add data to inventory DB

Device Configuration u Configuration is exposed in XML elements v For example: <configuration> <protocols> <bgp> <group> <name>local</name> <neighbor> <name>10. 0. 0. 1</name> <local-address>10. 0. 0. 2</local-address> </neighbor> </group> </bgp> </protocols> </configuration>

Device Configuration u Represent device configurations in XML u Configurations become malleable data, can be manipulated using standard tools v Add/delete/change configuration using XSL transformations v Store and retrieve configuration from an XML database

Network Provisioning Avoid writing multiple vendor-specific configuration parsers u Use XSLT to translate from vendor-neutral configuration to a vendor-specific configuration for each device u XML Schemas can provide data types, value ranges, regex matches, help information for vendor configuration u v Enables provisioning tools to partially validate configuration before uploading to device

Network Provisioning Customer DB Vendorindependent configuration Device-specific Configuration XSL Transformation Interface DB Policy DB Router(s)

Diagnosing Faults Everyone has “ 5 commands” to run when logging on to a sick router u Diagnose problems with network by running XSL scripts over XML output u v v v XSL is a powerful tool Inspect results from multiple commands Discard normal output Focus on abnormal situations Use SVG (Scalable Vector Graphics (XML)) to graph historical values for data visualization Target multiple routers

Summary u Choosing XML simplifies application development Widely available tools and information v Easy to understand text format v Larger talent pool of engineers v u Offers a reliable alternative to Expect scripts v u XML’s self-describing nature prevents problems with variations in CLI output Enhances Interoperability XML is a standard method of exchanging information between programs v Adopted by many industries – e. Commerce, databases, networking, etc. v

Thank you! http: //www. juniper. net