Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

do not shunning a network and hostname with sensor v3.01

i configured director 2.2.3 and sensor v3.01,i have managed router ,I clicked shunning enable ,it was succeed,when i click shun network or shun hostname ,i entered ip address with shunning ,it was display "timeout on waiting for respones",i clicked network device(security menu),it was display

disable shunning

success

configuring termial

error :timeout on waiting for respones

exiting the termial configure

error :timeout on waiting for respones

success

applying netranger acls with logging enable

success

3 REPLIES
Cisco Employee

Re: do not shunning a network and hostname with sensor v3.01

What do you see when you do a Security->Show->Deamons->Status?? Is managed running??

If not, have you configured it using security->Configure, select the sensor, go to Device management...set up the router(s) then System files->daemons and enable managed there??

New Member

Re: do not shunning a network and hostname with sensor v3.01

when i do a security->show->demons->status,managed is running,I have configured the sensor ,when i do shunning ->enable ,it is success. but

i can not shunning a network or hostname ,it is display "timeout on waiting for respones"

Cisco Employee

Re: do not shunning a network and hostname with sensor v3.01

Nr.managed receives a shun request message when a host or

network shun is performed from the Director. Nr.managed should

respond immediately, with success if it was a valid shun request,

or with failure if the request was invalid. It will send this response

before it actually attempts the shun. It should never happen that

managed will respond to some requests (e.g. ShunEnable) but

time out on others. There is probably a configuration problem,

or perhaps I don't completely understand your description.

In order to investigate and solve this, can you open a TAC case?

If the TAC engineer can not immediately find a solution, ask them

to assign stleary@cisco.com as the DE, and I will take a look.

95
Views
0
Helpful
3
Replies
CreatePlease login to create content