IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability.

IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability of NCIM - v3.8 Sparkler Presenters: Krishna Kodali Paul Stroud

IBM Tivoli Network Manager IP © 2010 IBM Corporation 3Presenters: Krishna Kodali & Paul Stroud March 8th, 2010 Agenda  What is an agent  What are the required parts of an agent  How to register an agent  Agent Example –Modules and Globals –Init –Mediation Filter –Mediation –Processing –Infinite Loop –The map –Parsing the map –The results IBM Presentation Template Full Version

IBM Tivoli Network Manager IP © 2010 IBM Corporation 4Presenters: Krishna Kodali & Paul Stroud March 8th, 2010 What is an agent  Written in perl  Uses a customized perl interpreter(ncp_disco_perl_agent)  Queries information from network entities  Can manipulate or transform the data  Information can easily be stored in ExtraInfo, but can also be added to the schema  OQL Functions –Reads from AgentName.despatch table –Writes to AgentName.returns table  Information passed via a perl object  Run in an infinite loop

IBM Tivoli Network Manager IP © 2010 IBM Corporation 5Presenters: Krishna Kodali & Paul Stroud March 8th, 2010 What are the required parts of an agent  The agent must be initialized  It must read in the record from the despatch table  It must write the record back to the returns table  We will see these in context shortly

IBM Tivoli Network Manager IP © 2010 IBM Corporation 6Presenters: Krishna Kodali & Paul Stroud March 8th, 2010 How to register an agent  Must create a.agnt file($NCHOME/precision/disco/agents)  $NCHOME/precision/bin/ncp_agent_registrar  Stores agent registration information in –$NCHOME/etc/precision/DiscoAgents.DOMAIN.cfg  Fields in.agnt registration file: –DiscoAgentDescription Brief description of what the agent does Html –DiscoAgentGUILocked –DiscoAgentClass –DiscoAgentIsIndirect –DiscoAgentPrecedence –DiscoAgentEnabledByDefaultOnPartial(0/1 off/on) –DiscoAgentEnabledByDefault(0/1 off/on)  For reference use the disco.agents table  http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.itnetmantip.doc_3.7/7957/xF2310633.html#xF86 4353088 http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.itnetmantip.doc_3.7/7957/xF2310633.html#xF86 4353088

IBM Tivoli Network Manager IP © 2010 IBM Corporation 13Presenters: Krishna Kodali & Paul Stroud March 8th, 2010 Discovery Agent Example (The map)  BLDG1:John Doe:Raleigh:Frank Smith  BLDG1:Mike Jones:Raleigh:Steve Thomas  BLDG3:John Doe:Richmond:Avery Allen  BLDG2:Joe Johnson:Seattle:Mark Kane  sysLocation  SysContact  m_City  m_AssetOwner

IBM Tivoli Network Manager IP © 2010 IBM Corporation 17Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Agenda  Show the 4 steps to configure NATed domain including an example configuration: 1Enable NAT 2Define NAT Gateway 3Enable NAT agents 4Define Scope for NATed domain  Discuss known issues

IBM Tivoli Network Manager IP © 2010 IBM Corporation 20Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  Step 3: Enable NAT Agents as per customer environment: –If you are running a NetScreen Firewall or a Cisco Router as a NAT gateway, you must use either the CiscoNATTelnet agent or the NATNetScreen agent. –If you are using a NAT gateway other than a NetScreen Firewall or a Cisco Router, you must use the Perl agent “NATTextFileAgent.pl” for unsupported NAT gateway devices. –When the NAT gateway is not in the public address space, you can enable the NATGateway agent to correct the potential problem of incorrect connectivity. (NATGateways.txt) Configure NAT discovery (continued)

IBM Tivoli Network Manager IP © 2010 IBM Corporation 24Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  Step 4 continued... –We have defined first four subnets i.e. two NATGateways and two NATed pingable subnets(public IP), but no private address space. As an example, the first NATGateway and associated subnet as: 201.201.201.201/32 (NATGateway) 61.61.61.0/29 - Public IP Subnet associated to 201.201.201.201. –Restriction: You can only define a scope zone for a private NAT address space where the subnet and netmask combination of the private subnet is unique within the discovery configuration. This excludes the first and second private subnet. –You could add private Subnet and associated AddressSpaceId for 3rd NATGateway i.e. 192.168.3.0/29. –Advantages of adding private subnets to scope: 1Discovery will identify NATed devices which are with in that AddressSpace so it ignores other subnets for feedback. 2If the NATGateway/NATed devices are routers, then defining scope of private address spaces would help to limit download of routing tables from devices with in that address space. –Since the private subnets are not pingable, you must uncheck "Add to Ping Seed List". –You should NOT define 'AddressSpace' for either NATGateway or for Public Subnets associated to the NATGateway(i.e. they should be defined as NULL AddressSpace). AddresSpace can be defined for only for private subnets. Else discovery stalls if you have such configuration in place and won't get to Phase1. Configure NAT discovery (continued)

IBM Tivoli Network Manager IP © 2010 IBM Corporation 25Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  KNOWN ISSUES:  IZ65289 – Documentation improvement will be covered in v3.9  IZ67446 - NATGATEWAY RESPONDS WITH IT'S NAT TRANSLATED IPS FROM IPTABLE IT DOESN'T OWN CAUSES INCORRECT DISCOVERY OF NATGATEWAY (Fixed in v3.8-FP3 and is due end of March'10) –The NATGateway (an example - Linux server acting as NATgateway) responds with NAT tranlated IPs from its IP table which it doesn't own results inaccurate discovery of NATGateway.  IZ66357 - POLLER POLLS PRIVATE IPADDRESSES INSTEAD OF GLOBAL ADDRESSES IN A NATED ENVIRONMENT WHICH CAUSES FLOOD OF INCORRECT ICMP EVENTS (Fixed in FP10(v3.7) & FP3(v3.8) – both FPs are due end of March'10)  IZ68880 - POLLER GENERATES PING FAILURE EVENTS FOR THE NATED DEVICE INTERFACES WHICH DOESN'T HAVE NAT TRANSLATION (no fix available yet) –Workaround for IZ68880 – Disable 'Interface Ping' policy and use 'SNMPLinkState' policy. Configure NAT discovery (continued)

IBM Tivoli Network Manager IP © 2010 IBM Corporation 27Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Agenda  Architecture of v3.5 to v3.8 Sparkler  Virtualdomain with NCIM Failover –configuring NCIM failover –Verifying failover functionality  Failover functionality walk through –troubleshooting tips  Known facts & Limitations  Reference Links

IBM Tivoli Network Manager IP © 2010 IBM Corporation 31Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg27015615http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg27015615 - unsupported by IBMSupport.

IBM Tivoli Network Manager IP © 2010 IBM Corporation 33Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  Virtualdomain with NCIM failover – new functionality with Sparkler.  Steps involved for the NCIM failover functionality: –Failover ncp_model should use new parameter “- primaryDomain” instead of “-backup” ncp_model is responsible to push the topology updates to its own NCIM instance. –Failover Poller should always have “-readsnmpconfig” unless you intend to run ncp_dh_snmp process on backup server. ncp_virtualdomain copies $NCHOME/etc/precision/SnmpStackSecurityInfo.cfg from Primary to Backup server. Any new/updated/deleted passwords stored in SnmpStackSecurityInfo.cfg will be in kept in sync from Primary to Backup by ncp_virtualdomain. Virtualdomain with NCIM Failover

IBM Tivoli Network Manager IP © 2010 IBM Corporation 34Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  How to verify the functionality failover: –There are two set of channel communication in failover Socket communication i.e. Topology updates from Primary to Backup –$NCHOME/var/precision –Polling Policies - $NCHOME/var/precision/MonitorPolicies.PRIMARY.xml –$NCHOME/etc/precision/SnmpStackSecurityInfo.cfg synchronization. Healthcheck Communication via HealthCheck Events. –The health check events are raised by ncp_virtualdomain component to know the health of Primary & Backup servers. Virtualdomain with NCIM Failover (continued)

IBM Tivoli Network Manager IP © 2010 IBM Corporation 35Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Failover functionality walk through  Example Configuration: –Socket Communication between Primary & Backup –Primary, Backup & Virtual domains are RTP_P, RTP_B & RTP_V –From Primary: –Healthcheck Communication – ensure both primary and backup domains are connecting to same Object Server i.e. nco_p_ncpmonitor, ncp_ncogate under CtrlServices.cfg From Standby:

IBM Tivoli Network Manager IP © 2010 IBM Corporation 36Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Failover functionality walk through (continued)  Example Configuration (Cont'd): –Tracking SnmpStackSchmaInfo.cfg changes from Primary virtualdomain log

IBM Tivoli Network Manager IP © 2010 IBM Corporation 37Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Failover functionality walk through (continued)  Example Configuration (Cont'd): –Tracking SnmpStackSchmaInfo.cfg changes from Backup virtualdomain log

IBM Tivoli Network Manager IP © 2010 IBM Corporation 38Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Failover functionality walk through (continued)  Example Configuration (Cont'd): –HealthCheck tracking from Primary or Backup based on debug 4 trace: 1# grep "update state.domains" $NCHOME/log/precision/ncp_virtualdomain.RTP_P.trace 2Receiving query: update state.domains set m_HealthStatus=1 where m_Domain='RTP_B'; 3Receiving query: update state.domains set m_HealthStatus=1 where m_Domain='RTP_P'; 4Receiving query: update state.domains set m_HealthStatus=1 where m_Domain='RTP_B'; 5Receiving query: update state.domains set m_HealthStatus=1 where m_Domain='RTP_P'; 6Receiving query: update state.domains set m_HealthStatus=0 where m_Domain='RTP_B'; 7Receiving query: update state.domains set m_HealthStatus=1 where m_Domain='RTP_P';  Checking Healthcheck via ncp_oql

IBM Tivoli Network Manager IP © 2010 IBM Corporation 39Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Known Facts & Limitations  Known Facts: –ncp_virtualdomain keeps in sync the polling policies created on primary to backup via MonitorPolicies.RPIMARY.xml Do not enable new polling policies or update/delete existing policies while Backup acting as primary. Such changes will be reverted upon failback. –New/Updated/Deleted community strings stored in SnmpStackSecurityInfo.cfg from Primary are copied to Backup automatically via ncp_virtualdomain but not vice-versa. –No failover support for additional pollers – this will be addressed in v3.9 (Enhancement reference – MR0810094924). –Do not try to pair the failover using different versions of ITNM on Primary & Backup. Below is excerpt from virtualdomain log of such scenario: 1ncp_virtualdomain[26297] Becoming Primary for tier 1 2Connection made to primary domain: RTP_B 3Tue Jan 26 15:36:39 2010 Warning:A generic non-fatal error has occurred 4found in file CVirtDomProtocol.cc at line 207 5CVirtDomProtocol::ProcessRequest: Unexpected record format 6Updating topology in backup domain

IBM Tivoli Network Manager IP © 2010 IBM Corporation 40Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010  Limitations:  NCPGUI database is isolated between Primary & Backup –No replication of 'ncpgui' schema i.e. NetworkViews are not in sync between Primary and Backup –NCPGUI limitation will be addressed in v3.9  Workaround for 'ncpgui'  Use $NCHOME/precision/scripts/upgrade/ITNMExportNetworkViews.pl script to export NetworkViews from primary to backup –Limitations of ITNMExportNetworkViews.pl script The backup ncpgui database always need to be dropped before importing new set from Primary after very first import. If the views are customized i.e. such as 'background image' of the view, those images are not migrated by the script. Known Facts & Limitations (continued)

IBM Tivoli Network Manager IP © 2010 IBM Corporation 41Presenters: Krishna Kodali & Paul StroudMarch 8th, 2010 Reference Material  V3.7 – High Availability : –http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg27015615http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg27015615  v3.8 – NCIM Failover : –http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/ com.ibm.networkmanagerip.doc_3.8/itnm/ip/wip/install/concept/nmip_i ns_backupinstallationwithncimbackup.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/ com.ibm.networkmanagerip.doc_3.8/itnm/ip/wip/install/concept/nmip_i ns_backupinstallationwithncimbackup.html

IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability.

Similar presentations

Presentation on theme: "IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability.

Similar presentations

Presentation on theme: "IBM Tivoli Network Manager IP © 2010 IBM Corporation How to Create and Integrate New Discovery Agent How to Configure NATed domain discovery High Availability."— Presentation transcript:

Similar presentations

About project

Feedback