Groups | Search | Server Info | Login | Register

Groups > comp.protocols.snmp > #147

Re: Context engine ID for proxying requests when there is a middleman acting as both proxy & agent

Show all headers | View raw

On Tuesday, October 15, 2013 5:04:47 PM UTC+5:30, vive...@gmail.com wrote:
> Topology:
> 
> NMS <------>  E1(Proxy & Agent1) <----------> E2(Agent2)
> 
> E1 hosts both a Proxy and an Agent(Agent1)
> 
> E2 hosts only Agent(Agent2)
> 
> 
> 
> Requirement: NMS's V3 requests to be served by E2's Agent(Agent2).
> 
> 
> 
> How can an NMS know about E2's engine ID so that it fills the contextEngineID appropriately with this?
> 
> 
> 
> If it is not possible, then NMS would know only E1's engine ID by discovery and it might tend to fill this as contextEngineID in its request. Will this not make the E1's engine to think that this request should be locally served by its Agent application(Agent1)?
> 
> 
> 
> Thanks,
> 
> Vivek


Experts,

Any thoughts on this?

Thanks,
Vivek

Back to comp.protocols.snmp | Previous | Next — Previous in thread | Find similar

Thread

Context engine ID for proxying requests when there is a middleman acting as both proxy & agent viveknitt@gmail.com - 2013-10-15 04:34 -0700
  Re: Context engine ID for proxying requests when there is a middleman acting as both proxy & agent viveknitt@gmail.com - 2013-11-18 01:41 -0800

csiph-web