Mngmt API: acceptUnauthenticatedPackets() call

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: Brian Anderson on 11-01-2011 11:41:24 PM
The Management API for the v1.2 toolkit introduces a new API called
energywise_acceptUnauthenticatedPackets().
The draft API Guide describes this as
¿This function is useful only when MAPI connects to a mixed network of switches running EnergyWise versions 2 and 2.5. When MAPI is connected to a version 2 switch, replies from version v2.5 switches cannot be authenticated unless you use this function.¿
 
The name seems at odds with the explanation. The explanation seems to say that replies from 2.5 switches WILL be authenticated if this function is called. Can you tell us more about what this function does?
 
Since a Management API client does not necessarily know which version of EW is running on its management switch or if it is running in a mixed environment, it seems that Orchestrator should call this function to provide the most flexibility. Then Orchestrator can be used in both mixed and non-mixed environments.
 
Is there a downside to Orchestrator calling this function no matter what environment it is in?

Subject: RE: Mngmt API: acceptUnauthenticatedPackets() call
Replied by: Brock Miller on 12-01-2011 02:16:42 AM
The Management API for the v1.2 toolkit introduces a new API called
energywise_acceptUnauthenticatedPackets().
The draft API Guide describes this as
¿This function is useful only when MAPI connects to a mixed network of switches running EnergyWise versions 2 and 2.5. When MAPI is connected to a version 2 switch, replies from version v2.5 switches cannot be authenticated unless you use this function.¿
 
The name seems at odds with the explanation. The explanation seems to say that replies from 2.5 switches WILL be authenticated if this function is called. Can you tell us more about what this function does?
 
Since a Management API client does not necessarily know which version of EW is running on its management switch or if it is running in a mixed environment, it seems that Orchestrator should call this function to provide the most flexibility. Then Orchestrator can be used in both mixed and non-mixed environments.
 
Is there a downside to Orchestrator calling this function no matter what environment it is in?

 
Hi Brian,
 
Great question.
 
EnergyWise 2.5 introduces a new enhancement where domain member switches actually send query responses directly back to the management station (if query is from the MAPI) rather than always channelling the responses through the connected management switch.  This enhancement is only supported with new toolkit version and corresponding EW 2.5 image.  However, it is still possible for EW 2.0 IOS images to co-exist with EW 2.5 images as part of a mixed domain.
 
This new method, acceptUnauthenticatedPackets(), will only come into play if your management application is connecting to an EW 2.0 switch as the management switch and also has EW 2.5 switches in the domain.  The EW 2.5 domain members will actually go ahead and send their responses directly to the management station, however, the management station cannot fully authenticate them due to the fact that the API connected to the EW 2.0 switch as the management switch.  Enabling this method provides your application flexibility and allows it to accept the EW 2.5 responses in this case.  This situation will only happen if the management switch is an EW 2.0 image in a mixed domain of 2.0 and 2.5.  You would not need this setting if your application instead connects to one of the EW 2.5 switches in the domain, as they are able to properly enable the authentication needed.

Attachments

    Outcomes