Driver Support Document

Arris Cadant CMTS C4 & E6000, CMTS version 1.x, 4.x, 7.x, 8.x (OBSOLETE, PLEASE REDISCOVER)

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.4115.1.9.1 E6000 1.0
 1.3.6.1.4.1.4998.2.1 Cadant CMTS C4 4.02, 7.02, 8.00

Driver Features Support Grid

Driver FeaturesAccess Methods
(X signifies feature support)CLISNMPTFTPCLI+TFTPSNMP+TFTPFTPCLI+FTPSNMP+FTPCLI+SFTPSCPCLI+SCPSNMP+SCPHTTP/HTTPS
  Driver Discovery                            
X General Access  
(CLI protocols: telnet, ssh1, ssh2, console)
X     X     X            
Configuration
X Retrieve Running Configuration release notes X     X     X            
X Retrieve Startup Configuration   X     X     X            
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running release notes X     X                  
X Configuration Deployment to Startup (with reboot)         X                  
  Binary Configuration Deployment                            
Diagnostics
X Routing Table   X                        
X OSPF Neighbors   X                        
X Interfaces   X                        
X Modules and Inventory   X                        
  Flash Storage Space                            
X File System   X                        
X Uptime     X                      
X ICMP Test   X                        
X Topology Parsing   X                        
X Duplex Parsing   X                        
  Enhanced VLAN Parsing  
Features
X Software Center release notes       X                  
  Software Image Synchronization release notes                          
X Password Management  
(Can modify: limited password, full password, read-only community strings, read/write community strings)
X                        
X Syslog Configuration and Change Detection   Syslog patterns X                        
X Custom Scripts and Diagnostics  
X                        
X ACL Parsing  
X ACL Provisioning   X                        
  VLAN Provisioning                            
X Configlet Parsing  
  QoS Parsing  
  VRF Parsing  
  Context Management                            

Retrieve Running Configuration

Release Notes

Retrieving the full or verbose configuration

Cadant devices support the reporting of both a "full" and "verbose" configuration, in addition to the regular configuration. When the "full_config" or "verbose_config" access variable is set to 'true', NA will capture the full or verbose configuration by adding the respective keywords to the 'show running config' and 'copy running-config tftp:' commands. If the variable full_verbose_config is set to 'true', then both arguments will be used. Since the device does not support these arguments in collecting its startup configuration, this will cause the running and startup configurations to be reported as no longer in sync.

return to top

Configuration Deployment to Running

Release Notes

Banner deployment is not supported

Banner deployment requires special handling that cannot be automated. As a result, the driver does not support banner deployment when running the "Deploy to running configuration" task through the CLI.

return to top

Software Center

Release Notes

Can't reload with new image after Image upgrade on this device

The device requires specifying the image to reload after an image upgrade to /update partition. No boot variable to specify new image location can be found. Current implementation can only send "reload" command to do a simple reload with whatever image in /active partition.

Workaround:

1 Reload the device manually through a telnet/ssh session with the path to the new image deployed through image upgrade. After boot, issue "reload commit" to make it in active. No action on NAS is required.

2 Write a new command script to reload the device with new image. This is an example of multi-line commands "reload /update/CMTS_V04.02.10.14.img\ry\r". Task may fail due to loss of connection after reload. Verify image after reload is correct and issue "reload commit".

return to top

Syslog Triggering

return to top