Cisco Multiservice Access Concentrator

Network Configuration Manager helps you manage the device configuration of Cisco Multiservice Access Concentrator. With the help of our Cisco Multiservice Access Concentrator device template, you can easily discover your devices and start managing their configurations. Import the Cisco Multiservice Access Concentrator template into Network Configuration Manager to gain complete control and visibility over your devices. For any networking devices such as Cisco Multiservice Access Concentrator, Network Configuration Manager performs configuration operations that are configured in the form of device templates. And whenever we initiate any config operations, Network Configuration Manager connects to the device (here, Cisco Multiservice Access Concentrator), executes set of commands that are configured in the device template into the device CLI based on the operation and protocol used while applying credentials (e.g., SSH/Telnet/SSH-TFTP), and finally processes the results and records/stores the necessary details.

Cisco Multiservice Access Concentrator

Download Template

Back to list

Cisco Multiservice Access Concentrator configuration commands

Below are the commands that will be executed for the respective operation in Cisco Multiservice Access Concentrator

Cisco Multiservice Access Concentrator - Backup Running Configuration (SSH/TELNET)

1. terminal length 0
2. show running-config - [This is the actual command executed for Backup Running Configuration]

Cisco Multiservice Access Concentrator - Backup Startup Configuration (SSH/TELNET)

1. terminal length 0
2. show startup-config - [This is the actual command executed for Backup Startup Configuration]

Cisco Multiservice Access Concentrator - Get Interface Details (SSH/TELNET)

1. terminal length 0
2. show running-config

Cisco Multiservice Access Concentrator - Enable Syslog Change Detection (SSH/TELNET)

1. configure terminal
2. logging on
3. logging ${UserInput:HostIpAddress}
4. logging trap ${UserInput:LoggingLevel}
5. end

Cisco Multiservice Access Concentrator - Disable Syslog Change Detection (SSH/TELNET)

1. configure terminal
2. no logging ${UserInput:HostIpAddress}
3. end

Cisco Multiservice Access Concentrator - Sync Configuration (SSH/TELNET)

1. write mem

Cisco Multiservice Access Concentrator - Backup Running Configuration (SSH/TELNET - TFTP)

1. copy running-config tftp
2. ${UserInput:tftp_server_address}
3. ${UserInput:file_name}

Cisco Multiservice Access Concentrator - Backup Startup Configuration (SSH/TELNET - TFTP)

1. copy startup-config tftp
2. ${UserInput:tftp_server_address}
3. ${UserInput:file_name}

Cisco Multiservice Access Concentrator - Get Interface Details (SSH/TELNET - TFTP)

1. terminal length 0
2. show running-config

Cisco Multiservice Access Concentrator - Upload Running Configuration (SSH/TELNET - TFTP)

1. copy tftp running-config
2. ${UserInput:tftp_server_address}
3. ${UserInput:file_name}

Cisco Multiservice Access Concentrator - Upload Startup Configuration (SSH/TELNET - TFTP)

1. copy tftp startup-config
2. ${UserInput:tftp_server_address}
3. ${UserInput:file_name}

Cisco Multiservice Access Concentrator - Enable Syslog Change Detection (SSH/TELNET - TFTP)

1. configure terminal
2. logging on
3. logging ${UserInput:HostIpAddress}
4. logging trap ${UserInput:LoggingLevel}
5. end

Cisco Multiservice Access Concentrator - Disable Syslog Change Detection (SSH/TELNET - TFTP)

1. configure terminal
2. no logging ${UserInput:HostIpAddress}
3. end

Cisco Multiservice Access Concentrator - Sync Configuration (SSH/TELNET - TFTP)

1. copy running-config startup-config

Cisco Multiservice Access Concentrator - Backup Running Configuration (SSH - SCP)

1. copy running-config scp://${UserInput:scp_username}@${UserInput:scp_server_address}/${UserInput:file_name}
2. ${UserInput:scp_password}

Cisco Multiservice Access Concentrator - Backup Startup Configuration (SSH - SCP)

1. copy startup-config scp://${UserInput:scp_username}@${UserInput:scp_server_address}/${UserInput:file_name}
2. ${UserInput:scp_password}

Cisco Multiservice Access Concentrator - Get Interface Details (SSH - SCP)

1. terminal length 0
2. show running-config

Cisco Multiservice Access Concentrator - Upload Running Configuration (SSH - SCP)

1. copy scp://${UserInput:scp_username}@${UserInput:scp_server_address}/${UserInput:file_name} running-config
2. ${UserInput:scp_password}

Cisco Multiservice Access Concentrator - Upload Startup Configuration (SSH - SCP)

1. copy scp://${UserInput:scp_username}@${UserInput:scp_server_address}/${UserInput:file_name} startup-config
2. ${UserInput:scp_password}

Cisco Multiservice Access Concentrator - Enable Syslog Change Detection (SSH - SCP)

1. configure terminal
2. logging on
3. logging ${UserInput:HostIpAddress}
4. logging trap ${UserInput:LoggingLevel}
5. end

Cisco Multiservice Access Concentrator - Disable Syslog Change Detection (SSH - SCP)

1. configure terminal
2. no logging ${UserInput:HostIpAddress}
3. end

Cisco Multiservice Access Concentrator - Sync Configuration (SSH - SCP)

1. copy running-config startup-config

Configuration Operations Supported in Network Configuration Managers' Device Template

As of now, the following config operations are supported in Network Configuration Managers' device templates

Configuration Backup

1. Configurations files will be read from the end device and will be stored in Network Configuration Manager
2. If there is any change between the configurations that are backedup already and the new one, then new configuration will be saved as different version and the user will be notified on the change.

Configuration Upload

1. The configuration file or configuration draft created by the user that was backedup previously will be uploaded from Network Configuration Manager to the device
2. The configuration file that is going to be uploaded is user specific and it can also be edited and uploaded as a draft
3. To perform upload operation, device must support TFTP/SCP and device should be associated with either SSH/Telnet-TFTP or SSH-SCP credentials in Network Configuration Manager.

Sync Configuration

1. It copies Running Configuration to the Startup Configuration, so that Running and Startup configuration can be in Sync.
2. The changes made in the Running Configuration is saved in Startup Configuration to avoid config loss in case of unexpected device reboot or power failure etc

Automatic Change Detection

1. Configures Network Configuration Manager server as Syslog server in the networking device, which enables forwarding of syslog messages from Device to Network Configuration Manager
2. Syslog messages carrying the details on who made a change in the device configuration acts as a key for the Automatic Change detection feature

Update Hardware Details

1. Interface details of the device will be processed and get listed under Interface details Tab on device snapshot of the respective device
2. Additional to the above configuration operations that are configured in device template, the commands to fetch hardware details like OSVersion, Model, Series, Serial Number, etc., will also be configured;

Variables Supported in NCM Device Templates

We use a few variables to make the commands generic in Device Tempaltes

Network Configuration Manager Server IP can be found under Settings -> Server Settings.

Network Configuration Manager SCP Server credential details can be found under Settings -> SSH Settings -> SCP Server.

S.No	Variable	Values
1	${UserInput:tftp_server_address}	NCM Server IP - Eg : 10.10.190.5
2	${UserInput:file_name}	will be created based on deviceId to make the file name unique
3	${UserInput:HostIpAddress}	NCM Server IP - Eg : 10.10.190.5
4	${UserInput:LoggingLevel}	notification/info that is choosen while enabling change detection will be used
5	${UserInput:scp_server_address}	NCM Server IP - Eg : 10.10.190.5
6	${UserInput:scp_username}	NCM SCP Server UserName - Eg : admin
7	${UserInput:scp_password}	NCM SCP Server password - Eg : admin

Disclaimer:This web page is intended to provide you information about new Device Templates to manage your network. The information is provided "As Is" without warranty of any kind.