no snmp-server host (does not remove the statement???)

[neo_christina]

Appreciate help on the following:

On a cisco WS-C4507R, Version 12.2(25)EWA1,

I tried to remove 3 existing snmp-server host configuration and add 2 snmp-server host statements:

no snmp-server host 1.1.1.1 public

no snmp-server host 2.2.2.2 public

no snmp-server host 3.3.3.3 public

snmp-server host 4.4.4.4 private

snmp-server host 5.5.5.5 private

However, the 3 existing configuration of the following cannot be removed as they can be viewed in the "sh run"

snmp-server host 1.1.1.1 public

snmp-server host 2.2.2.2 public

snmp-server host 3.3.3.3 public

snmp-server host 4.4.4.4 private

snmp-server host 5.5.5.5 private

When I removed all the snmp-server host using "no snmp-server host", all snmp-server host configuration is gone.

When I add back

snmp-server host 4.4.4.4 private

snmp-server host 5.5.5.5 private

it will still show all the following 5 configuration:

snmp-server host 1.1.1.1 public

snmp-server host 2.2.2.2 public

snmp-server host 3.3.3.3 public

snmp-server host 4.4.4.4 private

snmp-server host 5.5.5.5 private

Please advise if you have encountered this before and what should be done.

Thanks!

Christina

[neo_christina]

Hi,

appreciate some help. thanks!

christina

[sourabhagarwal]

try this config ....

no snmp-server host 1.1.1.1

no snmp-server host 2.2.2.2

no snmp-server host 3.3.3.3

snmp-server host 4.4.4.4 private

snmp-server host 5.5.5.5 private

now check config using "show running-config" command, do you still see old snmp-server host statements.

[neo_christina]

Hi,

it says incomplete command. thanks.

[sarbjeet-dhillon]

Hi Christina,

You may want to look at the link below.

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddd1c38/1#selected_message

The chap is also facing a similar problem to you.

A Cisco Engineer responded with the following....

The problem with the lingering trap host is most likely due to the fact that there is a still a notification wedged in the output queue. Unfortunately, you will have to reboot to clear this problem.

Try rebooting and let us know the outcome.

Kind Regards

SD