Seed file example for v1/v2c candidate systems

The following three seed entries are examples of how to present the same seed entry as a hostname, as an IPv4 address, and as an IPv6 address. A dual-stack discovery candidate system could be presented in any of these three ways. Each seed entry spans multiple lines and specifies the SNMP version and the read community string:

Core-ROUTER-1 SNMPVERSION=V1 
      COMMUNITY=xxxxyyyy#%@*&^)(:"=|\][}{
192.35.144.12 SNMPVERSION=V1 
      COMMUNITY=xxxxyyyy#%@*&^)(:"=|\][}{
3FFE:80C0:22C:101:219:56FF:FE3F:8A50 SNMPVERSION=V1 
      COMMUNITY=xxxxyyyy#%@*&^)(:"=|\][}{

The following three seed entries specify the SNMP port (2161) that the IP Manager should use to access the system. Notice that the seed entry with the hostname system identifier includes a v6 IP version suffix, and that the seed entry with the IPv6 system identifier encloses the IPv6 address in square brackets.

ROUTER2:v6:2161 SNMPVERSION=V2C COMMUNITY=public1
192.35.144.12:2161 SNMPVERSION=V2C COMMUNITY=public1
[3FFE:80C0:22C:109:203:BAFF:FEE5:7BE1]:2161 SNMPVERSION=V2C 
      COMMUNITY=public1

The following seed entry requires the keyword COMMUNITY because the first character of the read community string is a pound sign (#):

router-2.example.com COMMUNITY=#abcdefg SNMPPORT=2222

The following seed entry can be specified without using keywords. The only two fields are the system identifier and the read community string. The COMMUNITY keyword is not required, even though the first character of the community string is the equal sign (=).

192.168.2.2  =abcdefg

The following seed entry assumes that NameFormat is set to TM_USEAUTONAME in the name-resolver.conf file:

Core-ROUTER-1 NAMEFORMAT=TM_USELOOPBACK SNMPVERSION=V1 
      COMMUNITY=xxxxyyyy#%@*&^)(:"=|\][}{

The following seed entry assumes that NameFormat is set to TM_USESEEDNAME in the name-resolver.conf file:

Core-ROUTER-1 NAMEFORMAT=TM_USEAUTONAME SNMPVERSION=V1 
      COMMUNITY=xxxxyyyy#%@*&^)(:"=|\][}{