web-archive-net.com » NET » I » ITRANSFORMERS.NET

Total: 226

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • expect4java | iTransformers.net
    Java projects is that it supports nested java closures The nested closures allow the developer to expect nested statements For example if you have a Router configuration with a running config with Interface statements like that one interface GigabitEthernet0 0 description ETH LAN ETH SW LAUNCH INTF INFO GE 0 0 ip address 10 10 10 1 255 255 255 248 duplex auto speed auto interface GigabitEthernet0 0 17 encapsulation

    Original URL path: http://itransformers.net/expect4java (2016-04-25)
    Open archived version from archive

  • snmp2xml4j | iTransformers.net
    able to do snmpget snmptset snmpwalk and to transform the results through xslt It provides a bridge between MIBs and raw data received from the SNMP enabled devices Liecense Snmp2xml4j is distributed under a dual software license GPL 2 for non commercial use and a commercial software license if you would like to embed it in your commercial application Repository The primary repository is in https github com iTransformers snmp2xml4j Distribution The library has been distributed over maven central An example usage snmp walk bat Walk md SNMP2XML4J mibs a 10 10 10 10 161 c public v 2c t 1000 r 1 m 100 f output xml o system An example ouput xml xml version 1 0 root iso oid 1 org oid 1 3 dod oid 1 3 6 internet oid 1 3 6 1 mgmt oid 1 3 6 1 2 mib 2 oid 1 3 6 1 2 1 system oid 1 3 6 1 2 1 1 sysDescr oid 1 3 6 1 2 1 1 1 adult playground sysDescr sysObjectID oid 1 3 6 1 2 1 1 2 1 2 3 4 sysObjectID sysUpTime oid 1 3 6 1 2 1 1 3

    Original URL path: http://itransformers.net/snmp2xml4j (2016-04-25)
    Open archived version from archive

  • Documentation overview | iTransformers.net
    iTransformers net Empowering iTransformation Search form Search Documentation overview Here you will find the documentation guides of our products netTransformer user guide is available here User guide If you are an iTransformer user please visit the Getting Started Guide If you want to understand more about how to configure iTransformer please have a look on Configuration Guide If you want to understand more about how to configure bgpPeeringMap please have

    Original URL path: http://itransformers.net/wiki/documentation (2016-04-25)
    Open archived version from archive

  • netTransformer documentation | iTransformers.net
    netTransformer UserGuide Pirin Release Discovery Methods Impl Guide Developer s Guide netTransformer on dynamips bgpPeeringMap Education Graduation projects Trainings Cloud Solutions Intro to OpenStack Networks Security DDOS RTBH Self Protection Forum Contact iTransformers net Empowering iTransformation Search form Search You

    Original URL path: http://itransformers.net/node/90 (2016-04-25)
    Open archived version from archive

  • UserGuide - Pirin Release | iTransformers.net
    covers the Pirin edition of netTransformer netTransformer is a network transformation manager able to Discover current network infrastructure Capture its state Build a graph data model out of it Provide ability to review and reason about L2 L3 OSPF ISIS and BGP topology Automate device configuration process through simplified template interface Capture various other data during the discovery process Track the network evolution process Transform a network from one state

    Original URL path: http://itransformers.net/netTransformer/07/user-guide (2016-04-25)
    Open archived version from archive

  • Discovery Methods Implementation Guide | iTransformers.net
    discovery method Step 5 Transform raw data to a structured device xml To process them further the new data has to be accomodated in transformator xslt file for the specified device type The transformator xslt aims to build from the unstructured raw data a structured hierarchical object oriented xml database file for each of the discovered devices That means There is one device It has certain number of parameters It contains certain number of objects Each object also has some parameters And may contain other objects Figure 1 Device model generated from deviceXML through Altova XML Spy Each interface has ifIndex so it will be most appropriate to place the neighbors from ipCidrRouteTable as objects under the interface objects Step 6 Determine Neighbor objects and objects parameters object name HOSTNAME name objectType Discovered Neighbor objectType parameters parameter name Discovery Method name value c IPCIDRROUTEPROTO value parameter parameter name Neighbor IP Address name value X X X X value parameter parameter name Neighbor hostname name value HOSTNAME value parameter parameter name Neighbor Device Type name value DeviceType value parameter parameters object Step 7 Determine Neighbor objects and objects parameters Next task is to prepare xpath query to determine which cidr next hop is determined under which interface The best option is to open the raw data file and using something like Altova xml spy to try finding the correct xpath Figure 2 Xpathing Device XML xsl variable name ipCidrRouteTable select root iso org dod internet mgmt mib 2 ip ipForward ipCidrRouteTable ipCidrRouteEntry ipCidrRouteIfIndex ifIndex Since there might be many routes with different next hops pointing towards this interface will be usefull to get only the unique values of it xsl variable name next hop ips select distinct values ipCidrRouteTable ipCidrRouteEntry ipCidrRouteNextHop So this will extract us the ipCidrRouteEntry values for the interface with the current ifIndex Foreach nexthop we have to check if it is not 0 0 0 0 or a loopback xsl for each select next hop ips xsl variable name next hop ip select xsl if test next hop ip 0 0 0 0 and not contains next hop ip 127 0 0 And to determine its neighbor id e g try to get through snmp its sysName xsl variable name neighID xsl call template name return hostname xsl with param name hostname unformated select SnmpGetNameForXslt getName next hop ip comm xsl call template xsl variable If we are able to connect to the remote device and to get the sysName we will use it as an object Name xsl if test neighID sysName object xsl choose xsl when test neighID name xsl value of select neighID name xsl when xsl otherwise Else we will use the ip address name xsl value of select next hop ip name xsl otherwise xsl choose Object Type of Discovered Neighbors has always to be Discovered Neighbor objectType Discovered Neighbor objectType parameters Discovery Method c Protocol Names separated by a comma parameter name Discovery Method name value xsl for each select distinct

    Original URL path: http://itransformers.net/wiki/discovery-methods-implementation-guide (2016-04-25)
    Open archived version from archive

  • Developer's Guide | iTransformers.net
    xslt transformation process so knowing the deviceType we can determine the type of the request towards the device Then this request is used for obtaining the raw device data The Definition of the different discovery helper factories is done in the discoveryManager xml configuration file If there is a new DiscoveryHelperFactory it has to be added here discovery manager discovery helper class com discovery discoveryhelpers xml XmlDiscoveryHelperFactory parameters param name fileName discovery manager conf xml discoveryParameters xml param parameters discovery helper discovery manager DiscoveryListener Discovery listner is an event handling class that is registerd in DiscoveryManager main process and listens for newly discovered device events The design rational behid the evet mechanism is to achieve flexibility towards integrating iDiscover with various third party inventory systems public interface DiscoveryListener void handleDevice String deviceName RawDeviceData rawData DiscoveredDeviceType discoveredDeviceType Resource resource handeDevice is a method handler that is invoked by the discovery algorithm each time a new device is discovered Initially has been implemented the following handlers com discovery discoverylisteners DeviceFileLogger logs device data xml files into the filesystem com discovery discoverylisteners TopologyDeviceLogger java based logger that generates graphml files for visualization of this device into the network graph not used com discovery discoverylisteners XmlTopologyDeviceLogger xslt based logger that generates graphml giles for visualization of this device into t network graph DiscoveryListeners are registerd in iDiscover main process with the help of DiscoveryHelperFactory com discovery discoveryhelpers xml XmlDiscoveryHelperFactory The factory config is part of the discoveryManager xml The standard way of adding a new listener is to create a new class that implements discoveryListener interface and to add the class to the configuraiton file discovery manager discovery manager listeners discovery manager listener class com discovery discoverylisteners DeviceFileLogger param name path devices and models lab param discovery manager listener discovery manager listener class com discovery discoverylisteners XmlTopologyDeviceLogger param name xslt discovery manager conf xslt transformator undirected2 xslt param param name path devices and models lab undirected param discovery manager listener discovery manager listener class com discovery discoverylisteners XmlTopologyDeviceLogger param name xslt discovery manager conf xslt transformator directed xslt param param name path devices and models lab directed param discovery manager listener discovery manager listeners discovery manager iDiscover Resource Management iDiscover has an internal resource class that is used by the discoverer interface implementatation but also utilizes the ResourceManager module Initially iDiscover has been using only its internal class The algorithm works the following way During process initiation are passed as an input parameter the initial IP address and the discoveryManager xml file Into discoveryManager xml is declared discoveryResource xml config file From the intial IP address and the default currently SNMP management protocol parametersis formed a Discovery Resource that is used for the discovery of the initial device Then for any other discovered device the procedure is repeted the internal Resource is formed by the device IP address and a lookup in the resources defined in discoveryResource xml config file The design rational behind having both resources is the integration between the initial internal

    Original URL path: http://itransformers.net/wiki/developers-guide (2016-04-25)
    Open archived version from archive

  • netTransformer on dynamips | iTransformers.net
    out netTransformer with a virtual network topology If you want just to try netTransformer and to do it not inside your own network you can try to do a dynamips network discovery Here is a topology that is suitable for the purpose It has been built in GNS3 with dynamios and dynagen as underlying technologies You can download it from here http www itransformers net nets netTransformer 200 63 network lab zip Note that you have to find your own IOS images for cisco 3725 routers and you have to bridge and change the IP address 10 10 12 5 in the initial configuration of interface FastEthernet0 1 on R1 to your own network interface card of your PC Once you are done with this you will have to point the host on which netTransformer will be run on how to reach the routers part of our virtual lab For the purpose add those a similar kind of static routes route add 172 16 0 0 mask 255 255 0 0 10 10 12 5 route add 192 168 0 0 mask 255 255 0 0 10 10 12 5 Replace 10 10 12 5 with the IP address of

    Original URL path: http://itransformers.net/dynamips (2016-04-25)
    Open archived version from archive



  •