Unsolved
This post is more than 5 years old
2 Posts
0
12527
May 23rd, 2012 14:00
cannot add new management ip address to same community string.
hey guys i have two different server, running different monitoring softwares.
i have PC8024F and want to add both of those systems as management stations which can snmpwalk this switch.
this is what i have in config
snmp-server community "XXXXX" ro ipaddress 10.1.1.1
then when i add the other server, switch gives me following error
Error:That community already exists.
Is there a way i can have both of the ips configured to use same community string. or we have to add different community string for each ip :P
Thanks
-- MIK


DELL-Willy M
802 Posts
0
May 23rd, 2012 15:00
I would try the command without specifying a specific IP address and see how it responds. Based on the information below.
Configuring Communities
Beginning in Privileged EXEC mode, use the following commands to
configure access rights for SNMPv1 and SNMPv2.
Command Purpose
configure Enter Global Configuration mode
snmp-server community
string [ro | rw | su]
[view view-name]
[ipaddress ip_address]
Configure the community string and specify access criteria
for the community.
• community-string — Acts as a password and is used to
authenticate the SNMP management station to the
switch. The string must also be defined on the NMS in
order for the NMS to access the SNMP agent on the
switch (Range: 1-20 characters)
• ro — Indicates read-only access
• rw — Indicates read-write access.
• view-name — Specifies the name of a previously defined
MIB view.
• ip_address — Specifies the IP address of the management
station. If no IP address is specified, all management
stations are permitted
I pulled this out of the User Guide page 325
support.dell.com/.../ucg.pdf
Hope this helps,
Keep us updated if you can.
imrankh
2 Posts
0
May 23rd, 2012 16:00
yes, if we dont specify anything it will allow all ips. this is what i dont want . i want specific ip to be addded.
it is allowing me to add one. but not the second one.
Thanks
DELL-Willy M
802 Posts
1
May 23rd, 2012 17:00
MIK,
It looks like the options are
1. Create another Community and specify the second Management Station IP.
2. Use same Community and leave IP on command blank then create an ACL that only allows SNMP from those 2 hosts