Welcome to the AVC Technical Support Forum http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id= 2013-06-19T19:49:45Z 2013-06-19T19:49:45Z Hong Yu http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14788948 2013-04-30T03:25:24Z 2013-04-30T03:25:24Z

All ISR-G2 platforms will have the same support of AVC.

Hong Yu 2013-04-30T03:25:24Z Hong Yu http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14788922 2013-04-30T03:23:02Z 2013-04-30T03:23:02Z

Hi Tim, What configuration are  you refering to when you say source/destination address? Is it ASR or ISR?  Tina  

Hong Yu 2013-04-30T03:23:02Z Hong Yu http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14788756 2013-04-30T02:58:08Z 2013-04-30T02:58:08Z

[color=#525252]Hi Tim,[/color] sys-uptime first/last is not supported in MACE, but it is on the roadmap of AVC. In PI23, we will have sys-uptime supported as part of AVC implimentation on ISR-G2 similar to ASR. [color=#525252]Thanks,[/color] [color=#525252]TIna[/color] [color=#525252] [/color]

Hong Yu 2013-04-30T02:58:08Z Tim Ruhl http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14700094 2013-04-26T14:56:18Z 2013-04-26T14:56:18Z

Hello, What is the best way to determine the time period that each record generated by the performance monitor represents?  Currently there doesn't seem to be any time-related field available in the mace type flow record (e.g., no timestamp sys-uptime first/last, no flowStartMilliseconds/flowEndMilliseconds).  We're currently using the timestamp from the NetFlow header (i.e., system uptime), but this raises two concerns: * What happens if sending the NetFlow records is delayed for some reason, up to the point where the timestamp in the header (which represents the time the NetFlow ticket is sent) starts to differ significantly from the period used by the performance monitor to calculate the metrics * It does not provide any information on the interval that is configured for the performance monitor.  We would like to know when processing the PA NetFlow for what time interval the records have been generated.   Thanks,   Tim  

Tim Ruhl 2013-04-26T14:56:18Z Tim Ruhl http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14700017 2013-04-26T14:46:11Z 2013-04-26T14:45:50Z

Hello, Is it correct that the source address reported in the Performance Agent NetFlow record is always related to the initiator of the session (i.e., the client) that is being measured? If so, what would be the best way to clasify the direction of the session?  With Flexible NetFlow we have the Direction field (61) which provides the direction of a specific flow with respect to the router sending the NetFlow record, but in the MACE flow record this field type is not available.  Is there a way to determine where the source or the destination addess is located with regard to the interface on which the flow monitor is configured?  If not, would adding a Direction field to the mace type flow record be an option? Thanks,    Tim

Tim Ruhl 2013-04-26T14:45:50Z Tim Ruhl http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14698524 2013-04-26T13:27:34Z 2013-04-26T13:25:32Z

Hello, According to the Cisco feature navigator the 1900 series support the feature Performance Monitor (Phase 1) with recent IOS versions.  However, currently there is no IOS version for the 1900 series that supports the Performance Monitor (Phase 2) feature.  Will the 1900 series support this feature in the future, or will it only be available from the 2900 series and higher? Thanks,   Tim

Tim Ruhl 2013-04-26T13:25:32Z Brett Tiller http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14284960 2013-04-15T21:12:51Z 2013-04-15T21:12:51Z

Dear IVT Partners, We'd like to thank our partners who have already completed the IVT process for AVC.  Based upon partner feedback we've reduced the number of required testcases in sections 6.1 and 6.2.  We've also added a 'testing' page to our technical center that provides more information about the IVT process.  This page is located at http://developer.cisco.com/web/avc/testing .   Thanks, Brett Tiller

Brett Tiller 2013-04-15T21:12:51Z Brett Tiller http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14024464 2013-04-09T00:02:17Z 2013-04-09T00:02:17Z

Hi Simon,   ART Count Responses does not include late responses.  As you know the late responses represent a timeout of the response.  Therefore if you are calculating availability percentage based upon the response your formula would be ART Count Responses/Total Number of Requests . Thanks, Brett

Brett Tiller 2013-04-09T00:02:17Z Simon Dansette http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13988614 2013-04-30T00:33:41Z 2013-04-08T12:27:49Z

Hi, It is not clearly confirmed in the documentation if the field 42060 "ART Count Responses" includes the number of late responses (42068). If we want to have the total number of responses to calculate a percentage of availability, do we need to sum "ART Count Responses" and "ART Count Late Responses"?   Thanks, Simon

Simon Dansette 2013-04-08T12:27:49Z Brett Tiller http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13356403 2013-03-21T18:17:58Z 2013-03-21T18:17:05Z

Please post your technical questions in this forum.  Our team will respond to your questions as quickly as we can.

Brett Tiller 2013-03-21T18:17:05Z