"IP Address" for agent under Orchestrator

Document created by cdnadmin on Jan 24, 2014
Version 1Show Document
  • View in full screen mode
This document was generated from CDN thread

Created by: Christopher Verges on 01-09-2010 04:22:50 PM
In Cisco EnergyWise Orchestrator, the "IP Address" column for an agent device is blank, while that same column for a domain member device is populated.  I don't see any attribute for EW_ATTRIBUTE_TYPE_IP_ADDRESS (or something like it.)  How should an agent control that field to ensure the proper address gets used?
 
Thanks,
Chris

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Christopher Verges on 02-09-2010 01:41:07 AM

Hi Chris, the IP Address column is feeding in from the EW_ATTRIBUTE_TYPE_REPLY_TO from the query results.  This attribute is automatically replied with on every query and is populated based on the information that you pass into the SDK (local ip, port).
 
Can you confirm that your ip address properly shows up on the output of a CLI query:  energywise query importance 100 name PDU_name collect usage (under the 'Host' column)?  If it's showing up fine there, then you are probably ok and most likely this is hitting some issue between the alpha SDK and the Orchestrator version.
 

 
Hi Brock,
 
Yes, the IP address shows up properly in the CLI query.  It's only in the Orchestrator interface that it is incorrect.  This occurs with both the SDK and SDK+ agents.
 
How should I go about filing a bug with the Orchestrator team?
 
Thanks for the help!
Chris

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Christopher Verges on 02-09-2010 03:18:17 AM
For clarification, what usage category are you registering your device as that's having this issue?
 
For now, I'm going to hold off on filing a bug against Orchestrator team as we are still investigating a similar issue where the API is dropping some results from the SDK (orchestrator uses the API).  This could be due to the same root cause as you are hitting, and can hopefully be fixed in a subsequent SDK release.  Will keep you updated as we find out more.

 
With the SDK+, we're currently using ENERGYWISE_USAGE_CATEGORY_CONSUMER so that the values appear in the IOS query output.  (Existing bug reported to Brad regarding use of METER.)  I'd like to have 1 entity use CONSUMER and the rest use METER, though.
 
With the SDK, we're using ENERGYWISE_USAGE_CATEGORY_METER.
 
Chris

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Brock Miller on 02-09-2010 12:57:12 AM
In Cisco EnergyWise Orchestrator, the "IP Address" column for an agent device is blank, while that same column for a domain member device is populated.  I don't see any attribute for EW_ATTRIBUTE_TYPE_IP_ADDRESS (or something like it.)  How should an agent control that field to ensure the proper address gets used?
 
Thanks,
Chris

Hi Chris, the IP Address column is feeding in from the EW_ATTRIBUTE_TYPE_REPLY_TO from the query results.  This attribute is automatically replied with on every query and is populated based on the information that you pass into the SDK (local ip, port).
 
Can you confirm that your ip address properly shows up on the output of a CLI query:  energywise query importance 100 name PDU_name collect usage (under the 'Host' column)?  If it's showing up fine there, then you are probably ok and most likely this is hitting some issue between the alpha SDK and the Orchestrator version.
 
Let me know, thanks!
 
 

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Brock Miller on 02-09-2010 02:48:37 AM


Hi Brock,

 
Yes, the IP address shows up properly in the CLI query.  It's only in the Orchestrator interface that it is incorrect.  This occurs with both the SDK and SDK+ agents.
 
How should I go about filing a bug with the Orchestrator team?
 
Thanks for the help!
Chris

 
For clarification, what usage category are you registering your device as that's having this issue?
 
For now, I'm going to hold off on filing a bug against Orchestrator team as we are still investigating a similar issue where the API is dropping some results from the SDK (orchestrator uses the API).  This could be due to the same root cause as you are hitting, and can hopefully be fixed in a subsequent SDK release.  Will keep you updated as we find out more.
 
Thanks!!

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Christopher Verges on 28-09-2010 01:48:43 AM
For now, I'm going to hold off on filing a bug against Orchestrator team as we are still investigating a similar issue where the API is dropping some results from the SDK (orchestrator uses the API).  This could be due to the same root cause as you are hitting, and can hopefully be fixed in a subsequent SDK release.  Will keep you updated as we find out more.

 
Hi Brock,
 
Any more word on this?
 
Thanks,
Chris

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Brock Miller on 29-09-2010 12:22:25 AM


For now, I'm going to hold off on filing a bug against Orchestrator team as we are still investigating a similar issue where the API is dropping some results from the SDK (orchestrator uses the API).  This could be due to the same root cause as you are hitting, and can hopefully be fixed in a subsequent SDK release.  Will keep you updated as we find out more.


 
Hi Brock,
 
Any more word on this?
 
Thanks,
Chris

 
Hey Chris,
 
Actually, I have a feeling that this issue could be caused by a previous version of the API (running in Orchestrator) dropping index=0 endpoint results.  This would clearly cause your SDK+ parent entity's results to be dropped if it is in fact the issue.  This should be getting changed in the API (if not done already) and would be reflected in a new release to you.  I believe that Brad is working to get this fixed in your API or delivering you a new drop with this change.
 
Have you started running any of the API example/test code against your test network?  Once this change is put in place, we can run this to verify that the API is receiving all of your device's information properly (and that it was not previously).
 
Thanks,
 
Brock

Subject: RE: "IP Address" for agent under Orchestrator
Replied by: Christopher Verges on 29-09-2010 04:36:39 AM
Actually, I have a feeling that this issue could be caused by a previous version of the API (running in Orchestrator) dropping index=0 endpoint results.  This would clearly cause your SDK+ parent entity's results to be dropped if it is in fact the issue.  This should be getting changed in the API (if not done already) and would be reflected in a new release to you.  I believe that Brad is working to get this fixed in your API or delivering you a new drop with this change.
 
Have you started running any of the API example/test code against your test network?  Once this change is put in place, we can run this to verify that the API is receiving all of your device's information properly (and that it was not previously).

 
Hi Brock,
 
I'm still using the SDK+ rev released back on 08/30/2010, modified with patches sent to Brad in the interim.  The switch is running 12.2(250.16)EW.
 
Let me know what specific tests you'd like me to perform.  I'd be happy to run what is needed.
 
Thanks,
Chris

Attachments

    Outcomes