Driver Support Document

Cisco ONS 15454 and 15600, OS versions 6.x - 10.x

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.3607.1.20.10.10 ciscoONS15454 6.02.02, 7.02.02, 7.02.03, 8.05.01, 9.02.03
 1.3.6.1.4.1.3607.1.20.10.70 ciscoONS15454 10.5.24

Driver Features Support Grid

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

General Access

Release Notes

Cisco ONS 15454 SONET driver limited functionlity

The Cisco ONS SONET driver is limited in functionality due to several practical reasons:

    1. The complex configurations that are possible given the plethora of cards that can be installed in a given chassis.

    2. The limited availability of a fully, or typically, configured chassis with provisioned cards, facilites, services, circuits, tunnels, etc.

    3. The usual manner of configuring and managing the device is via a proprietary GUI.

This release note summarizes the supported functions of this driver.

1. Snapshot and configuration parsing
    Network Information
    Equipment Inventory Information
    Users Information
    Cross Connects Information
    Facilities Information
    Protocol Information
2. Custom Actions
    Custom TL1 scripts and diagnostics
3. Module inventory
    Card slot, model, hardware and software versions, part number
4. Discovery
    SNMP and CLI

Using the TL1 Interface

The TL1 Interface listens on a specific Telnet port to connect to the TL1 Shell. The connection to the TL1 Shell is done through Telnet port 3083. As a result, the "Telnet port" variable must be set to the appropriate value (3083).

To set the Telnet port variable, login to NA, under Devices click Inventory and select the device. In the Actions field, click the Edit option. The Edit Device page opens. Scroll down to the Device Access Settings section. This section should be visible when using device-specific passwords.

return to top

Password Management

Release Notes

Changing passwords for logged-in users

The TL1 console does not support changing passwords for users that are currently logged-in to the device. As a result, the Deploy Password task will fail unless the user is not logged-in to the device.

return to top

Custom Scripts and Diagnostics

Release Notes

TL1 interface result handling

Since the TL1 interface doesn't indicate failure in a proper way, we leave it to the user to decide when a command has failed.

return to top