IPM on CiscoWorks

Unanswered Question
Feb 4th, 2008
User Badges:

Installing and configuring IPM2.6.0 , on the installation guide it is clear on what to perform on the router but need help on what to do from CiscoWorks. I have already installed it. What configurations are needed on source and target…..?

Thank You and Kind Regards,

Genet T.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Tue, 02/05/2008 - 00:00
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

In general, all you need is SNMP read-write credentials configured on the device. IPM will perform the rest of the configuration. For devices that will act as IP SLA responders (target devices for jitter and advanced UDP probes), you should also enable the IP SLA responder:


ip sla responder


Or:


ip sla monitor responder


Or:


rtr responder


The actual command will depend on your IOS version.

itssnsu07 Tue, 02/05/2008 - 00:32
User Badges:

Thank You so much for the prompt assisatance.... that will really help.

what i am confused is how to select my source and tagrets....

We have a Hierarchal layout where we do have Access ----- Distribution------Core ----Edge which connects to the Router through the Firewall...

i am assuming the targets to be Access Devices, but not sure.

Please assist on how to proceed in the such layout.


Thank You Again and Regards,

Genet T.




Joe Clarke Tue, 02/05/2008 - 08:38
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Where are you concerned with latency? With what latency are you concerned? That is, do you want to check for jitter in your internal voice/video network, or do you want to verify your end users have good Internet connectivity? There are no hard and fast rules as to where you stick your collectors. It depends on what you want to monitor.


For example, if you want to test for jitter, putting your collectors in the core, and having the access layer devices act as responders would work. Of course, this means you need to add overhead onto your core switches. To alleviate this, a leading practice is to use a "shadow router" which is basically a small router (e.g. 1800, 2600, etc.) with the latest IOS loaded which acts as an end station (i.e. no IP routing). This router will be located as close to the real source as possible (e.g. directly connected to a core switch). Instead of configuring your collectors on the core device, you configure them on the shadow router. This reduces the risk to the network since it doesn't matter if this router crashes due to something in IP SLA.

itssnsu07 Thu, 02/07/2008 - 03:43
User Badges:

Thank You very much in deed, yes this greatly helps.

Mainly I am concerned with the end users Internet connectivity. But as you suggested, I will use a shadow router which I understand will be the source and the access devices as target and see the out put. But then what if I need to verify end users' internet connectivity, What do I require? what do i need to configure? and what is the best practice?


Thank You again for your valuable time and assistance,

Genet T.


Joe Clarke Thu, 02/07/2008 - 08:46
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

For verifying end users connectivity, you would either user the access-layer switches (assuming they are IOS), or shadow routers in the access closets. Since a router per closet can get kind of expensive, deploying one collector per access switch is probably not going to cause any damage, and it will give you a clear idea of (I'm assuming) HTTP latency for the users on that switch.

itssnsu07 Thu, 02/07/2008 - 23:42
User Badges:

Thank You so much.........

I will try to put all in place and get back with my success and any doubts if any!


Thank You again and Have a Great Day!

Genet T.



Actions

This Discussion