Snmp community strings, Adding an snmp community string – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 106

74
Network OS NETCONF Operations Guide
53-1003231-02
SNMP community strings
7
SNMP community strings
SNMP versions 1 and 2c use community strings to restrict access to the switch. There are six
default community strings: three read-write strings and three read-only strings. There is support for
a total of 256 SNMP communities, all user-configurable.
The following default community strings are read-write:
•
Secret C0de
•
OrigEquipMfr
•
private
The following default community strings are read-only:
•
public
•
common
•
ConvergedNetwork
Adding an SNMP community string
To add an SNMP community string, perform the following steps.
1. Issue the <edit-config> RPC to configure the <snmp-server> node in the
urn:brocade.com:mgmt:brocade-snmp namespace.
2. Under the <snmp-server> node, specify the <community> node element.
3. Under the <community> node element, specify the <community> leaf element, and set its
value to the community string to be added.
4. Optionally, under the <community> node element, include the <access> leaf element and set
its value to “rw” for read-write access, or to “ro” for read-only access.
The default value is “ro”.
The following example adds a community string named “private” to the SNMP configuration and
sets its access permission to read-write.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1001" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<snmp-server xmlns="urn:brocade.com:mgmt:brocade-snmp" >
<community>
<community>private</community>
<access>rw</access>
</community>
</snmp-server>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1001" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>