cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
1386
Views
5
Helpful
2
Replies

Alarm after upgrade WAE from 4.1.5(b) to 4.1.5(c)

Tomasz Mowinski
Level 1
Level 1

Hi

After upgrade few WAEs I've this alarm on two devices:

The Flow Monitor control connection to the  tcpstat-v1 console could not be (re)established after multiple attempts.

The rest upgraded devices don't have this alarm.

Do somebody know where I should look for the reason ?

thanks in advance

James

1 Accepted Solution

Accepted Solutions

James,

This message indicates your WAE can not communicate with the flow collector configured (e.g. NAM).

For example on my lab WAE I have the following two config lines:

flow monitor tcpstat-v1 host 14.110.3.116

flow monitor tcpstat-v1 enable

14.110.3.116 is my lab NAM.  If this WAE could not communicate with that IP I would receive the same alarm you are seeing.

Are you using NAM in your WAAS environment?  Make sure all WAEs can reach it if they have these config lines.

Also, are you running NAM as a VB on one of the WAEs?  If so, check the status of the VB to ensure it's running (maybe it was on one of the WAEs that was recently rebooted for the upgrade and the VB isn't configured for auto start).

Hope this helps,

Mike Korenbaum

Cisco WAAS PDI Help Desk

http://www.cisco.com/go/pdihelpdesk

View solution in original post

2 Replies 2

James,

This message indicates your WAE can not communicate with the flow collector configured (e.g. NAM).

For example on my lab WAE I have the following two config lines:

flow monitor tcpstat-v1 host 14.110.3.116

flow monitor tcpstat-v1 enable

14.110.3.116 is my lab NAM.  If this WAE could not communicate with that IP I would receive the same alarm you are seeing.

Are you using NAM in your WAAS environment?  Make sure all WAEs can reach it if they have these config lines.

Also, are you running NAM as a VB on one of the WAEs?  If so, check the status of the VB to ensure it's running (maybe it was on one of the WAEs that was recently rebooted for the upgrade and the VB isn't configured for auto start).

Hope this helps,

Mike Korenbaum

Cisco WAAS PDI Help Desk

http://www.cisco.com/go/pdihelpdesk

Hi

NAM is installed on VB and was't running after reboot. And only two WAEs ware configured to communicate with this NAM so I've seen these alarms only on these two. Thanks a lot !

best

James Taiwo

Review Cisco Networking for a $25 gift card