Characters allowed within SNMP v.2 Community Strings
A collegue of mine and I were discussing characters that were eligible for use within SNMP v.2 Community Strings this morning. We have some older Cisco devices which we have some difficulty modeling in our Network Management system.
Is there any issue using special characters (for instance #$%^&*!) within SNMP v.2 Community strings on older routers and switches running antequated code??
Re: Characters allowed within SNMP v.2 Community Strings
The only characters that should not be in Cisco community strings are '@' and ':'. The '@' is used for community string indexing, and the ':' is often used as a field delimiter in management applications. Recently, a parser bug was found with '$' in community strings in which a string containing '$' cannot be unconfigured, but it does not affect SNMP polling.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...