A community Strings ( also known as SNMP Community Strings) are the IDs that are used to access the statistics from routers or devices on a network. Collecting this data can help your IT team to keep an eye on the managed devices and applications. The SNMP talks to our network to find out information related to this network device activity: for example, bytes, packets, and errors transmitted and received on a router, the connection speed between devices, or the number of hits a web server receives. Using the correct community string, a device can access data within other devices.
Below is the list of communities and examples. If you have any concerns or questions, please feel free to get in touch with our support department.
Community list for psychz customers
- 6939 = Hurricane Electric
- 3491 = PCCW
- 19174 = China Unicom
- 1299 = Telia
- 7922 = Comcast
- 3257 = Tinet
- 6461 = Zayo
- 4134 = China Telecom
Communities
Prepend Communities- prepend your ASN to a specific peer
65001:n Prepend your asn outbound to N asn 1 time
65002:n Prepend your asn outbound to N asn 2 times
65003:n Prepend your asn outbound to N asn 3 times
65004:n Prepend your asn outbound to N asn 4 times
65005:n Prepend your asn outbound to N asn 5 times
No export communities - set no export to a specific peer
600:n where is the specific ASN where 'no-export' will be set and advertised
No advertise communities - don't advertise at all to a specific peer
666:n where is the ASN of the peer your route will not be advertised to at all
For example
Combo Examples:
Setting community 65502:7922 600:6461 666:4134 65001:3491
This would prepend your ASN twice to comcast, set no-export to Zayo, not advertise at all to CT, and prepend once to PCCW
By default, routes are advertised to all carriers unless influenced by the above
BlackHole - for /32 routes
40676:666
Tagging this will flag a host route you own to blackhole on upstream providers