In my setup I use vendor||model (in some cases vendor&&model) specific config files for different service plans. For example I use TLVs 43.9.1 and 43.9.3 only for Cisco CMs and not others (each Cisco-specific config file for all of my 4 plans has 0x80000000 in them). My "automatic upgrade procedure" also uses different config files for different vendors&&models. Vendor/model resolution is done by ISC DHCP and works pretty well. "SNMP access" is configured within CM config file with ordinary docsDevNmAccessXXX MIB objects. Can't see any reason why not to use it this way. ... Or am I not getting your question right?
Through the CMTS it will be very difficult, I only see the possibility to perform that blocking/filtering SNMP packets by ACL on bundle interface but it will need you define a specific subnet (CM) for the targeted modems. By Config file it's easy to disable the SNMP access.
disabled SNMP is a bad sign. Most likely Service provider isn't very confident of his tech abilities, their network is old / unreliable, or the quality of their service is just weak.. So probably it's time to change service provider. SNMP must be enabled, as it's specifically intended to manage and improve service quality.
SNMP access can be disabled via CM config file (by using per vendor/per model specific config file). I don't know any simple way to do it from CMTS.
Config files differs only by service plans. What can cause the SNMP is not responding for specific model? (though it worked before)
In my setup I use vendor||model (in some cases vendor&&model) specific config files for different service plans. For example I use TLVs 43.9.1 and 43.9.3 only for Cisco CMs and not others (each Cisco-specific config file for all of my 4 plans has 0x80000000 in them). My "automatic upgrade procedure" also uses different config files for different vendors&&models. Vendor/model resolution is done by ISC DHCP and works pretty well. "SNMP access" is configured within CM config file with ordinary docsDevNmAccessXXX MIB objects. Can't see any reason why not to use it this way. ... Or am I not getting your question right?
yes, you understand right.
Through the CMTS it will be very difficult, I only see the possibility to perform that blocking/filtering SNMP packets by ACL on bundle interface but it will need you define a specific subnet (CM) for the targeted modems. By Config file it's easy to disable the SNMP access.
disabled SNMP is a bad sign. Most likely Service provider isn't very confident of his tech abilities, their network is old / unreliable, or the quality of their service is just weak.. So probably it's time to change service provider. SNMP must be enabled, as it's specifically intended to manage and improve service quality.