EMC VoyenceControl Device Services Support (DSr) - Support ...

EMC Corporation Corporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000 www.EMC.com

EMC® VoyenceControlDevice Services Support (DSr)

Version 12.0.0 Hotfix 6

Support MatrixP/N 300-010-546

REV A01

EMC VoyenceControl Device Services Support Version 12.0.0 Hotfix 6 Support Matrix2

Copyright © 2010 EMC Corporation. All rights reserved.

Published February, 2010

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Contents

Preface

IntroductionOverview................................................................................................................... 26

What is VoyenceControl? ................................................................................ 26Compatibility .................................................................................................... 26

Device Driver InformationNew device drivers.................................................................................................. 28Modified device drivers.......................................................................................... 29Enabling inactive device classes ............................................................................ 30Viewing installed device driver packages............................................................ 31Configuring FTP Transfer Service ......................................................................... 32

3COM Devices3Com Netbuilder II Router..................................................................................... 34

Features available ............................................................................................. 34Discovery/identify methods .......................................................................... 34Configuration capture...................................................................................... 34Configuration deploy....................................................................................... 35Multi-config files............................................................................................... 35Device data ........................................................................................................ 35

3Com Switch 5500.................................................................................................... 36Features available ............................................................................................. 36Discovery/identify methods .......................................................................... 36Configuration capture...................................................................................... 36Configuration deploy....................................................................................... 37Device commands ............................................................................................ 37Multi-config files............................................................................................... 38Device data ........................................................................................................ 38Known issues .................................................................................................... 38

ACME DevicesACME NetNet SBC.................................................................................................. 42

Features available ............................................................................................. 42Discovery/identify methods .......................................................................... 42Configuration capture...................................................................................... 43

Contents 3

Contents

Configuration deploy ....................................................................................... 43Multi-config files ............................................................................................... 43Device data......................................................................................................... 43Known issues..................................................................................................... 45

Adtran DevicesAdtran NetVanta ...................................................................................................... 48

Features available.............................................................................................. 48Discovery/identify methods........................................................................... 48Configuration capture ...................................................................................... 49Multi-config files ............................................................................................... 49Device data......................................................................................................... 49Known issues..................................................................................................... 50

Adtran NetVanta Switch ......................................................................................... 51Features available.............................................................................................. 51Discovery/identify methods........................................................................... 51Configuration capture ...................................................................................... 52Multi-config files ............................................................................................... 52Device data......................................................................................................... 53Known issues..................................................................................................... 53

Adva DevicesAdva FSP150CC ....................................................................................................... 56

Features available.............................................................................................. 56Discovery/identify methods........................................................................... 56Configuration capture ...................................................................................... 57Configuration deploy ....................................................................................... 57Multi-config files ............................................................................................... 57Device data......................................................................................................... 58Known issues..................................................................................................... 58

Airespace DevicesAirespace Switch ...................................................................................................... 60


Alcatel DevicesAlcatel OmniAccess ................................................................................................. 64


Alcatel OmniCore..................................................................................................... 68Features available.............................................................................................. 68


Contents

Discovery/identify methods .......................................................................... 68Configuration capture...................................................................................... 69Configuration deploy....................................................................................... 69Multi-config files............................................................................................... 69Device data ........................................................................................................ 69

Alcatel Omnistack.................................................................................................... 71Features available ............................................................................................. 71Discovery/identify methods .......................................................................... 71Configuration capture...................................................................................... 72Configuration deploy....................................................................................... 72Device commands ............................................................................................ 72Multi-config files............................................................................................... 73Device data ........................................................................................................ 73Known issues .................................................................................................... 74

Alcatel Omniswitch ................................................................................................. 75Features available ............................................................................................. 75Discovery/identify methods .......................................................................... 76Configuration capture...................................................................................... 76Configuration deploy....................................................................................... 76Additional Driver Functionality..................................................................... 76Device commands ............................................................................................ 77Multi-config files............................................................................................... 79Device data ........................................................................................................ 79Known issues .................................................................................................... 80

Alcatel Service Router and Ethernet Service Switch .......................................... 81Features available ............................................................................................. 81Discovery/identify methods .......................................................................... 81Configuration capture...................................................................................... 82Configuration deploy....................................................................................... 82Configuration activations................................................................................ 82Multi-config files............................................................................................... 82Device data ........................................................................................................ 83Known issues .................................................................................................... 84

Alvarion DevicesAlvarion Breeze AP ................................................................................................. 86

Features available ............................................................................................. 86Discovery/identify methods .......................................................................... 86Configuration capture...................................................................................... 86Device commands ............................................................................................ 87Multi-config files............................................................................................... 87Device data ........................................................................................................ 87Known issues .................................................................................................... 88

Aruba DevicesAruba Wireless Switch ............................................................................................ 90

Features available ............................................................................................. 90Discovery/identify methods .......................................................................... 90Configuration capture...................................................................................... 90Configuration deploy....................................................................................... 91Multi-config files............................................................................................... 91Device data ........................................................................................................ 92

Contents 5

Contents

AudioCodes DevicesAudioCodes MediaPack.......................................................................................... 94


BlueCoat DevicesBlueCoat SG ............................................................................................................ 100

Features available............................................................................................ 100Discovery/identify methods......................................................................... 100Configuration capture .................................................................................... 101Configuration deploy ..................................................................................... 101Multi-config files ............................................................................................. 101Device data....................................................................................................... 101Known issues................................................................................................... 102

Brocade DevicesBrocade 7500 ........................................................................................................... 104

Features available............................................................................................ 104Discovery/identify methods......................................................................... 104Configuration capture .................................................................................... 104Device commands........................................................................................... 105Multi-config files ............................................................................................. 105Device data....................................................................................................... 105Known issues................................................................................................... 106

Brocade McData ..................................................................................................... 107Features available............................................................................................ 107Discovery/identify methods......................................................................... 107Configuration capture .................................................................................... 108Device commands........................................................................................... 108Known issues................................................................................................... 108

Checkpoint DevicesCheckpoint Firewall-1 ........................................................................................... 110


Ciena DevicesCiena Router ........................................................................................................... 116

Features available............................................................................................ 116Discovery/identify methods......................................................................... 116Configuration capture .................................................................................... 117


Contents

Configuration deploy..................................................................................... 117Multi-config files............................................................................................. 117Device data ...................................................................................................... 117Known issues .................................................................................................. 118

Cisco DevicesCisco Aironet AP VXWorks.................................................................................. 120

Features available ........................................................................................... 120Discovery/identify methods ........................................................................ 120Configuration capture.................................................................................... 120Multi-config files............................................................................................. 121Device data ...................................................................................................... 121

Cisco PIX Firewall.................................................................................................. 122Features available ........................................................................................... 122Discovery/identify methods ........................................................................ 123Configuration capture.................................................................................... 123Configuration deploy..................................................................................... 123Device commands .......................................................................................... 123Multi-config files............................................................................................. 125Device data ...................................................................................................... 125Known issues .................................................................................................. 126

Cisco VPN 3000 ...................................................................................................... 128Features available ........................................................................................... 128Discovery/identify methods ........................................................................ 128Configuration capture.................................................................................... 129Configuration deploy..................................................................................... 129Multi-config files............................................................................................. 129Device data ...................................................................................................... 129Known issues .................................................................................................. 130

Cisco Aironet AP Package .................................................................................... 131Features available ........................................................................................... 131Discovery/identify methods ........................................................................ 131Configuration capture.................................................................................... 132Configuration deploy..................................................................................... 132Multi-config files............................................................................................. 133Device data ...................................................................................................... 133Known issues .................................................................................................. 134

Cisco Aironet Bridge Package.............................................................................. 135Features available ........................................................................................... 135Discovery/identify methods ........................................................................ 135Configuration capture.................................................................................... 136Configuration deploy..................................................................................... 136Multi-config files............................................................................................. 136Device data ...................................................................................................... 137

Cisco Application Control Engine....................................................................... 138Features available ........................................................................................... 138Discovery/identify methods ........................................................................ 138Configuration capture.................................................................................... 139Configuration deploy..................................................................................... 139Multi-config files............................................................................................. 139Device data ...................................................................................................... 139Known issues .................................................................................................. 140

Cisco BPX ................................................................................................................ 141Features available ........................................................................................... 141

Contents 7

Contents

Discovery/identify methods......................................................................... 141Configuration capture .................................................................................... 142Configuration deploy ..................................................................................... 143Device commands........................................................................................... 143Known issues................................................................................................... 144

Cisco CatOS Switch Package ................................................................................ 145Features available............................................................................................ 146Discovery/identify methods......................................................................... 146Configuration capture .................................................................................... 146Configuration deploy ..................................................................................... 147Device commands........................................................................................... 147Multi-config files ............................................................................................. 149Device data....................................................................................................... 150Known issues................................................................................................... 150

Cisco Content Appliance....................................................................................... 152Features available............................................................................................ 152Discovery/identify methods......................................................................... 153Configuration capture .................................................................................... 153Configuration deploy ..................................................................................... 153Multi-config files ............................................................................................. 153Device data....................................................................................................... 155Known issues................................................................................................... 155

Cisco Content Services Switch ............................................................................. 156Features available............................................................................................ 156Discovery/identify methods......................................................................... 156Configuration capture .................................................................................... 157Configuration deploy ..................................................................................... 157Multi-config files ............................................................................................. 157Device data....................................................................................................... 158

Cisco Router ............................................................................................................ 159Features available............................................................................................ 160Discovery/identify methods......................................................................... 160Configuration capture .................................................................................... 161Configuration deploy ..................................................................................... 161Device commands........................................................................................... 162Multi-config files ............................................................................................. 164Device data....................................................................................................... 164Known issues................................................................................................... 165

Cisco IOS Switch Package..................................................................................... 167Features available............................................................................................ 168Discovery/identify methods......................................................................... 168Configuration capture .................................................................................... 168Configuration deploy ..................................................................................... 169Multi-config files ............................................................................................. 171Device data....................................................................................................... 172Known issues................................................................................................... 172

Cisco IOS XR ........................................................................................................... 174Features available............................................................................................ 174Discovery/identify methods......................................................................... 174Configuration capture .................................................................................... 175Configuration deploy ..................................................................................... 175Operating System Management ................................................................... 175Multi-config files ............................................................................................. 175Device data....................................................................................................... 176Known issues................................................................................................... 176


Contents

Cisco Intrusion Prevention System (IPS)............................................................ 178Features available ........................................................................................... 178Discovery/identify methods ........................................................................ 178Configuration capture.................................................................................... 179Configuration deploy..................................................................................... 179Multi-config files............................................................................................. 179Device data ...................................................................................................... 179Known issues .................................................................................................. 180

Cisco Lightstream Package................................................................................... 181Features available ........................................................................................... 181Discovery/identify methods ........................................................................ 181Configuration capture.................................................................................... 182Configuration deploy..................................................................................... 182Multi-config files............................................................................................. 182Device data ...................................................................................................... 183

Cisco Nexus ............................................................................................................ 184Features available ........................................................................................... 184Discovery/identify methods ........................................................................ 184Configuration capture.................................................................................... 185Configuration deploy..................................................................................... 185Device commands .......................................................................................... 185Multi-config files............................................................................................. 186Device data ...................................................................................................... 187Known issues .................................................................................................. 188

Cisco MGX .............................................................................................................. 189Features available ........................................................................................... 189Discovery/identify methods ........................................................................ 189Configuration capture.................................................................................... 190Configuration deploy..................................................................................... 190Device commands .......................................................................................... 191Known issues .................................................................................................. 192

Cisco MDS............................................................................................................... 194Features available ........................................................................................... 194Discovery/identify methods ........................................................................ 194Configuration capture.................................................................................... 195Configuration deploy..................................................................................... 195Device commands .......................................................................................... 195Multi-config files............................................................................................. 196Device data ...................................................................................................... 196Known Issues .................................................................................................. 196

Cisco Wide Area Application Services (WAAS)................................................ 197Features available ........................................................................................... 197Discovery/identify methods ........................................................................ 198Configuration capture.................................................................................... 198Configuration deploy..................................................................................... 198Multi-config files............................................................................................. 199Device data ...................................................................................................... 199

Cisco Wireless LAN Controller............................................................................ 200Features available ........................................................................................... 200Discovery/identify methods ........................................................................ 200Configuration capture.................................................................................... 201Configuration deploy..................................................................................... 201Multi-config files............................................................................................. 201Device data ...................................................................................................... 201Known issues .................................................................................................. 202

Contents 9

Contents

Citrix DevicesCitrix Netscaler LoadBalancer.............................................................................. 204

Features available............................................................................................ 204Discovery/identify methods......................................................................... 204Configuration capture .................................................................................... 205Configuration deploy ..................................................................................... 205Multi-config files ............................................................................................. 205Device data....................................................................................................... 205

D-Link DevicesD-Link xStack.......................................................................................................... 208


Edgewater DevicesEdgewater EdgeMarc Router ............................................................................... 212


Enterasys DevicesEnterasys Smartswitch Router ............................................................................. 216

Features available............................................................................................ 216Discovery/identify methods......................................................................... 216Configuration capture .................................................................................... 217Configuration deploy ..................................................................................... 217Device commands........................................................................................... 217Multi-config files ............................................................................................. 218Device data....................................................................................................... 218Known issues................................................................................................... 219

Ericsson DevicesEricsson ECN Switch ............................................................................................. 222


Ericsson MSED ....................................................................................................... 225Features available............................................................................................ 225Discovery/identify methods......................................................................... 225


Contents

Configuration capture.................................................................................... 226Configuration deploy..................................................................................... 226Multi-config files............................................................................................. 226Device data ...................................................................................................... 226

Extreme DevicesExtreme.................................................................................................................... 230

Features available ........................................................................................... 230Discovery/identify methods ........................................................................ 231Multi-config files............................................................................................. 231Device data ...................................................................................................... 231Known issues .................................................................................................. 232

ExtremeWare XOS.................................................................................................. 233Features available ........................................................................................... 233Discovery/identify methods ........................................................................ 233Configuration capture.................................................................................... 233Configuration deploy..................................................................................... 234Multi-config files............................................................................................. 234Device data ...................................................................................................... 234Known issues .................................................................................................. 235

F5 DevicesF5 Load Balancer Rev 3......................................................................................... 238

Features available ........................................................................................... 238Discovery/identify methods ........................................................................ 238Configuration capture.................................................................................... 239Configuration deploy..................................................................................... 239Device commands .......................................................................................... 239Multi-config files............................................................................................. 240Device data ...................................................................................................... 241

F5 Load Balancer Rev 4......................................................................................... 242Features available ........................................................................................... 242Discovery/identify methods ........................................................................ 242Configuration capture.................................................................................... 242Configuration deploy..................................................................................... 243Multi-config files............................................................................................. 243Device data ...................................................................................................... 244

F5 Load Balancer Rev 9......................................................................................... 245Features available ........................................................................................... 245Discovery/identify methods ........................................................................ 246Configuration capture.................................................................................... 246Configuration deploy..................................................................................... 246Device commands .......................................................................................... 246Multi-config files............................................................................................. 247Device data ...................................................................................................... 249

Force10 DevicesForce10 C-Series Router ........................................................................................ 252

Features available ........................................................................................... 252Discovery/identify methods ........................................................................ 252Configuration capture.................................................................................... 253Configuration deploy..................................................................................... 253Multi-config files............................................................................................. 253

Contents 11

Contents

Device data....................................................................................................... 253Force10 E-Series Router......................................................................................... 255


Force10 S-Series Router ......................................................................................... 258Features available............................................................................................ 258Discovery/identify methods......................................................................... 258Configuration capture .................................................................................... 259Configuration deploy ..................................................................................... 259Multi-config files ............................................................................................. 259Device data....................................................................................................... 260

Fortinet DevicesFortinet Fortigate Router....................................................................................... 262


Foundry DevicesFoundry EdgeIron.................................................................................................. 266

Features available............................................................................................ 266Discovery/identify methods......................................................................... 266Configuration capture .................................................................................... 267Multi-config files ............................................................................................. 267Device data....................................................................................................... 267Known issues................................................................................................... 268

Foundry Package.................................................................................................... 269Features available............................................................................................ 269Discovery/identify device............................................................................. 269Configuration capture .................................................................................... 270Configuration deploy ..................................................................................... 270Device commands........................................................................................... 270Multi-config files ............................................................................................. 271Device data....................................................................................................... 271

Gigamon DevicesGigamon Switch ..................................................................................................... 274



Contents

HP DevicesHP ProCurve Switch ............................................................................................. 280

Features available ........................................................................................... 281Discovery/identify methods ........................................................................ 281Configuration capture.................................................................................... 281Configuration deploy..................................................................................... 281Device commands .......................................................................................... 281Multi-config files............................................................................................. 282Device data ...................................................................................................... 282Known issues .................................................................................................. 283

HUAWEI DevicesSmartAX .................................................................................................................. 286

Features available ........................................................................................... 286Discovery/identify methods ........................................................................ 286Configuration capture.................................................................................... 287Configuration deploy..................................................................................... 287Device commands .......................................................................................... 287Multi-config files............................................................................................. 288Device data ...................................................................................................... 288Known issues .................................................................................................. 289

Intermec DevicesIntermec MobileLAN ............................................................................................ 292

Features available ........................................................................................... 292Discovery/identify methods ........................................................................ 292Configuration capture.................................................................................... 293Multi-config files............................................................................................. 293Device data ...................................................................................................... 293Known issues .................................................................................................. 294

Juniper DevicesJuniper ERX (E Series) ........................................................................................... 296

Features available ........................................................................................... 296Discovery/identify methods ........................................................................ 297Configuration capture.................................................................................... 297Configuration deploy..................................................................................... 298Operating System Management................................................................... 298Multi-config files............................................................................................. 299Device data ...................................................................................................... 299Known issues .................................................................................................. 299

Juniper Router ........................................................................................................ 300Features available ........................................................................................... 300Discovery/identify methods ........................................................................ 301Configuration capture.................................................................................... 301Configuration deploy..................................................................................... 301Multi-config files............................................................................................. 302Device data ...................................................................................................... 302Known issues .................................................................................................. 303

Juniper Switch (EX Series) .................................................................................... 304Features available ........................................................................................... 304Discovery/identify methods ........................................................................ 305

Contents 13

Contents

Configuration capture .................................................................................... 305Configuration deploy ..................................................................................... 305Multi-config files ............................................................................................. 306Device data....................................................................................................... 306Known issues................................................................................................... 307

Juniper EX2500 Switch .......................................................................................... 308Features available............................................................................................ 308Discovery/identify methods......................................................................... 309Configuration capture .................................................................................... 309Configuration deploy ..................................................................................... 309Multi-config files ............................................................................................. 309Device data....................................................................................................... 310Known issues................................................................................................... 311

Laurel DevicesLaurel ST Router..................................................................................................... 314


Lucent DevicesLucent Access Point ............................................................................................... 318


Marconi DevicesMarconi ASX ........................................................................................................... 322


McAfee DevicesMcAfee IntruShield................................................................................................ 326

Features available............................................................................................ 326Discovery/identify methods......................................................................... 326Configuration capture .................................................................................... 326Multi-config files ............................................................................................. 327Device data....................................................................................................... 327Known issues................................................................................................... 328


Contents

Milan DevicesSM801P Managed Switch ..................................................................................... 330

Features available ........................................................................................... 330Discovery/identify methods ........................................................................ 330Multi-config files............................................................................................. 331Device data ...................................................................................................... 331

Motorola BSRMotorola BSR Router............................................................................................. 334

Features available ........................................................................................... 334Discovery/identify methods ........................................................................ 334Configuration capture.................................................................................... 335Configuration deploy..................................................................................... 335Device commands .......................................................................................... 335Multi-config files............................................................................................. 336Device data ...................................................................................................... 336

MRV DevicesMRV LX Terminal Server ...................................................................................... 340

Features available ........................................................................................... 340Discovery/identify methods ........................................................................ 340Configuration capture.................................................................................... 341Configuration deploy..................................................................................... 341Multi-config files............................................................................................. 341Device data ...................................................................................................... 341

NetCache DevicesNetCache................................................................................................................. 344

Features available ........................................................................................... 344Multi-config files............................................................................................. 344Device data ...................................................................................................... 345

Netopia DevicesNetopia R7000 Series ............................................................................................. 348

Features available ........................................................................................... 348Discovery/identify methods ........................................................................ 348Configuration capture.................................................................................... 348Configuration deploy..................................................................................... 349Multi-config files............................................................................................. 349Device data ...................................................................................................... 349

NetScreen DevicesNetScreen Firewall................................................................................................. 352

Features available ........................................................................................... 352Discovery/identify methods ........................................................................ 353Configuration capture.................................................................................... 353Configuration deploy..................................................................................... 353Multi-config files............................................................................................. 353Device data ...................................................................................................... 353Known issues .................................................................................................. 354

Contents 15

Contents

Nokia DevicesNokia IP ................................................................................................................... 356

Features available............................................................................................ 356Discovery/identify methods......................................................................... 357Configuration capture .................................................................................... 357Configuration deploy ..................................................................................... 357Device commands........................................................................................... 357Multi-config files ............................................................................................. 358Device data....................................................................................................... 359

Nortel DevicesNortel Alteon .......................................................................................................... 362


Nortel Alteon 2400 ................................................................................................. 365Features available............................................................................................ 365Discovery/identify methods......................................................................... 365Configuration capture .................................................................................... 365Configuration deploy ..................................................................................... 366Known issues................................................................................................... 366

Nortel Router .......................................................................................................... 367Features available............................................................................................ 367Discovery/identify methods......................................................................... 367Configuration capture .................................................................................... 368Configuration deploy ..................................................................................... 368Multi-config files ............................................................................................. 368Device data....................................................................................................... 368Known issues................................................................................................... 369

Nortel Baystack....................................................................................................... 370Features available............................................................................................ 370Discovery/identify methods......................................................................... 370Multi-config files ............................................................................................. 371Device data....................................................................................................... 371

Nortel BoSS Switch ................................................................................................ 372Features available............................................................................................ 372Discovery/identify methods......................................................................... 372Configuration capture .................................................................................... 373Configuration deploy ..................................................................................... 373Multi-config files ............................................................................................. 373Device data....................................................................................................... 373

Nortel Contivity ..................................................................................................... 375Features available............................................................................................ 375Discovery/identify methods......................................................................... 375Multi-config files ............................................................................................. 376Device data....................................................................................................... 376

Nortel Multi-Service Switch ................................................................................. 377Features available............................................................................................ 377Discovery/identify methods......................................................................... 378Multi-config files ............................................................................................. 378


Contents

Device data ...................................................................................................... 378Known issues .................................................................................................. 379

Nortel Passport....................................................................................................... 380Features available ........................................................................................... 380Discovery/identify methods ........................................................................ 380Configuration capture.................................................................................... 380Configuration deploy..................................................................................... 381Multi-config files............................................................................................. 381Device data ...................................................................................................... 381

Nortel Passport 8600.............................................................................................. 382Features available ........................................................................................... 382Discovery/identify methods ........................................................................ 383Configuration capture.................................................................................... 383Configuration deploy..................................................................................... 383Multi-config files............................................................................................. 383Device data ...................................................................................................... 383Known issues .................................................................................................. 384

Nortel 4500 Switch................................................................................................. 385Features available ........................................................................................... 385Discovery/identify methods ........................................................................ 386Configuration capture.................................................................................... 386Configuration deploy..................................................................................... 386Device commands .......................................................................................... 387Multi-config files............................................................................................. 387Device data ...................................................................................................... 387Known issues .................................................................................................. 388

Overture DevicesOverture NC ........................................................................................................... 390

Features available ........................................................................................... 390Discovery/identify methods ........................................................................ 390Configuration capture.................................................................................... 391Configuration deploy..................................................................................... 391Device commands .......................................................................................... 391Device data ...................................................................................................... 391Known issues .................................................................................................. 392

Overture NG........................................................................................................... 393Features available ........................................................................................... 393Discovery/identify methods ........................................................................ 394Configuration capture.................................................................................... 394Configuration deploy..................................................................................... 394Operating System Management................................................................... 394Device data ...................................................................................................... 395Known issues .................................................................................................. 395

Overture NP ........................................................................................................... 396Features available ........................................................................................... 396Discovery/identify methods ........................................................................ 396Configuration capture.................................................................................... 397Configuration deploy..................................................................................... 397Device commands .......................................................................................... 397Multi-config files............................................................................................. 398Device data ...................................................................................................... 398Known issues .................................................................................................. 399

Contents 17

Contents

Packeteer DevicesPacketeer PacketShaper......................................................................................... 402


Paradyne DevicesParadyne 9100......................................................................................................... 406

Features available............................................................................................ 406Discovery/identify methods......................................................................... 406Device commands........................................................................................... 406Known issues................................................................................................... 407

Patton DevicesSmartNode Router ................................................................................................. 410


Radware DevicesRadware WSD Load Balancer .............................................................................. 414


Riverbed DevicesRiverbed Steelhead ................................................................................................ 418


Riverstone DevicesRiverstone Router................................................................................................... 424

Features available............................................................................................ 424Discovery/identify methods......................................................................... 424Configuration capture .................................................................................... 424


Contents

Configuration deploy..................................................................................... 425Config files....................................................................................................... 425Device data ...................................................................................................... 425

Siemens DevicesSiemens.................................................................................................................... 428

Features available ........................................................................................... 428Multi-config files............................................................................................. 429Device data ...................................................................................................... 429

Siemens hiX56xx DSLAM..................................................................................... 430Features available ........................................................................................... 430Discovery/identify methods ........................................................................ 430Configuration capture.................................................................................... 431Configuration deploy..................................................................................... 431Multi-config files............................................................................................. 431Device data ...................................................................................................... 432Known issues .................................................................................................. 432

SourceFire DevicesSourcefire 3D Sensor.............................................................................................. 436

Features available ........................................................................................... 436Discovery/identify methods ........................................................................ 436Configuration capture.................................................................................... 437Configuration deploy..................................................................................... 437Device data ...................................................................................................... 437Known issues .................................................................................................. 438

Starent DevicesStarent PDSN.......................................................................................................... 440

Features available ........................................................................................... 440Discovery/identify methods ........................................................................ 440Configuration capture.................................................................................... 441Configuration deploy..................................................................................... 441Multi-config files............................................................................................. 441Device data ...................................................................................................... 441Known issues .................................................................................................. 442

Symbol DevicesSymbol WS-2000 .................................................................................................... 444

Features available ........................................................................................... 444Discovery/identify methods ........................................................................ 445Configuration capture.................................................................................... 445Configuration deploy..................................................................................... 446Operating System Management notes ........................................................ 446Multi-config files............................................................................................. 447Device data ...................................................................................................... 447

Tasman DevicesTasman Router........................................................................................................ 450

Features available ........................................................................................... 450Discovery/identify methods ........................................................................ 450

Contents 19

Contents

Multi-config files ............................................................................................. 451Device data....................................................................................................... 451Known issues................................................................................................... 451

Telco DevicesTelco Switch............................................................................................................. 454

Features available............................................................................................ 454Discovery/identify methods......................................................................... 454Configuration capture .................................................................................... 455Configuration Deploy .................................................................................... 455Multi-config files ............................................................................................. 455Device data....................................................................................................... 455Known issues................................................................................................... 456

Telco T-Metro .......................................................................................................... 457Features available............................................................................................ 457Discovery/identify methods......................................................................... 457Configuration capture .................................................................................... 458Configuration deploy ..................................................................................... 458Multi-config files ............................................................................................. 458Device data....................................................................................................... 458Known issues................................................................................................... 459

Vanguard DevicesVanguard Router .................................................................................................... 462


Index


Preface

. As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information about product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Audience This document is part of the EMC VoyenceControl Device Services Support (DSr) documentation set, and is intended for use by individuals who have the responsibility of installing and deploying devices and device drivers.

Readers of this document are expected to be familiar with the following topics:

◆ Windows®, Solaris, and Linux® operating systems

◆ Database architecture and concepts

◆ Security management

◆ Internet protocols, including HTTP, TCP/IP, File Transfer Protocol (FTP), and Telnet

◆ Lightweight Directory Access Protocol (LDAP) and directory services

◆ Authentication and authorization

Related documentation

Related documents include:

◆ EMC VoyenceControl Device Services Support (DSr) 12.0.0 Hotfix 4 - Patch Read Me

◆ EMC VoyenceControl Device Server 12.0.0 - Configuration Guide

Conventions used in this document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

Preface 21

Preface

IMPORTANT!An important notice contains information essential to software or hardware operation.

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning.

DANGER

A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the message.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal• Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, functions, utilities• URLs, pathnames, filenames, directory names, computer names, filenames, links,

groups, service keys, file systems, notifications

Bold• Names of commands, daemons, options, programs, processes, services,

applications, utilities, kernels, notifications, system calls, man pages

• Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus)

• What user specifically selects, clicks, presses, or types

Italic• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier

• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of

running text

Courier bold

• Specific user input (such as commands)

Courier italic

• Variables on command line• User input variables

< >

[ ]

|

{ }

...

Used in running (nonprocedural) text for:

Used in running (nonprocedural) text for:

Used in procedures for:

Used in all text (including procedures) for:

Used for:

Used for:

Used in procedures for:

Angle brackets enclose parameter or variable values supplied by the user

Square brackets enclose optional values

Vertical bar indicates alternate selections - the bar means “or”

Braces indicate content that you must specify (that is, x or y or z)

Ellipses indicate nonessential information omitted from the example


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to Powerlink and choose Support. On the Support page, you will see several options, including one for making a service request. Note that to open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.

23

http://Powerlink.EMC.com

Preface


1

Introduction

This chapter contains the following topics:

◆ Overview ........................................................................................................................ 26

Introduction 25

Introduction

OverviewThe following information is included in this Support Matrix document.

◆ Device Driver Features and Information

◆ Additions to Existing Device Drivers

◆ Known Device Driver Issues

◆ Additional Device Driver Support Information

What is VoyenceControl?◆ An automated compliance, change and configuration management solution that

delivers industry-recognized best practices.

◆ A collaborative network infrastructure design, controlled change processes, network device and service configuration transparency, and compliance with corporate and regulatory requirements—to enable you to ensure the security, availability, and operational efficiency of your network.

◆ An automated support for all facets of the network infrastructure lifecycle, seamlessly integrating critical design, change, and compliance management requirements.

Compatibility

This release is certified to work with VoyenceControl 4.1.0 Hotfix 3, on the following environments:

◆ Red Hat Enterprise Linux 4 and 5

◆ Microsoft Windows Server 2003 with Service Pack 1

◆ Solaris 10


2

Device Driver Information


◆ New device drivers ....................................................................................................... 28◆ Modified device drivers ............................................................................................... 29◆ Enabling inactive device classes ................................................................................. 30◆ Viewing installed device driver packages ................................................................. 31◆ Configuring FTP Transfer Service............................................................................... 32

Device Driver Information 27


New device drivers The following are new device drivers included with this release:

◆ Alcatel OmniAccess

• New Models: Alcatel OmniAccess 4324

• New Operating Systems: AOS-W 3.4, AOS-W 3.3.2.10

◆ Cisco Wide Area Application Services (WAAS)

• New Models: 512, 612, 674, 7371

• New Operating Systems: 4.8.0-12

◆ Intermec

• New Models: WA21, WA22

• New Operating Systems: 2.30

◆ Juniper EX2500 Switch

• New Models: EX2500

• New Operating Systems: EX2500 OS v3.0+

◆ Sourcefire 3D Sensor

• New Models: 3D Sensor 2100

• New Operating Systems: 4.8.0-12



Modified device driversThe following are device drivers that have been updated with this release

◆ Alcatel Service Router and Ethernet Service Switch

• New Operating Systems: TiMOS-6.1.R9

◆ Cisco Content Appliance

• New Models: 674, 7341

◆ Cisco Content Service Switch

◆ Cisco IOS Switch Package

• New Models: WS-C2960G-24TC-L

• New Operating Systems: 12.2(44)SE LAYER_2

◆ Cisco IOS XR

◆ Cisco Router

• New Models: ASR 1004

◆ Force10 E-Series Router

◆ Juniper Router

Modified device drivers 29


Enabling inactive device classesTo enable a device class that is not enabled by default, follow these steps.

Step Action

Note: Changes to device classes may affect the underlying Auto Discovery device classes' configuration.

1 Select Tools > System Administration from the VoyenceControl menu bar.

2 Select Global > Device Classes to open the Global Managed Device Classes window.

3 Click the Manage List button.

4 Highlight the Supported Device Class you want to enable, and click the Add button. Repeat this step for all device classes you are enabling.

5 Click Ok.

6 Click Apply.

7 Click Yes to confirm the changes.

8 Click Ok.

9 Click Close.



Viewing installed device driver packagesTo view a list of installed device driver packages, follow these steps.

Step Action

Note: This command can be run on either the Application Server or the Device Server. The versiondb.pl tool reports information based on the server where it is run.

1 Log into the server as a user with administrator privileges.

2 Navigate to the [Product Home]/bin directory.

3 Run the perl versiondb.pl --query command.

Viewing installed device driver packages 31


Configuring FTP Transfer ServiceTo support FTP transfers for configuration management on some devices, an FTP service must be configured on the device server(s). Refer to the individual driver documentation to determine if this service must be configured for your device.

As a minimum, the following characteristics must be present; any additional security precautions are the responsibility of the end-user.

◆ An anonymous FTP user (typically user anonymous) must be enabled.

◆ The anonymous FTP user’s home directory must be set to $TFTPHOMEDIR/ftp, and cannot be world-writeable.

◆ The path $TFTPHOMEDIR/ftp/backup must exist and the backup directory must be world-writeable.

◆ The FTP user must be able to create subdirectories under $TFTPHOMEDIR/ftp/backup. This may require additional settings for the FTP service employed.


3

3COM Devices


◆ 3Com Netbuilder II Router .......................................................................................... 34◆ 3Com Switch 5500 ......................................................................................................... 36

3COM Devices 33

3COM Devices

3Com Netbuilder II Router

Device Type

Specific Model(s)

Documentation/Information

Enabled By Default

Configuration Change Notification (Events)

Configuration Files

Configuration Content

Configuration Protocols

User Interface

Discovery/Identify Methods

Password Management

Configuration Capture

Configuration Deploy

Cut-Through Access

Quick Commands

Hardware Information

Features available ◆ Discover/Identify (SNMP)

◆ Configuration Capture (Pull running configs)

◆ Configuration Deploy (Push Configlets, TERMlets)

◆ Device Access (Cut-Through, TERMlets, etc.)

◆ Configuration Change Notification (SNMP Trap and Syslog Processing)

Discovery/identify methods

The following are used to provide information about your device (Host Name, Type, Vendor, Model, Operating System, and Serial Number).

◆ Discovery Mechanism:

• Look for SW/NBII in sysDescr

• Look for 1.3.6.1.4.1.43.1.4.(2|11|12|22|23) in sysObjectID

◆ Operating System from sysDescr

◆ Model from lookup table based on sysObjectID

Configuration capture

The following are the commands, or processes that are used to "pull" a configuration from your device.

◆ Get the boot directory using the sf 4 command

◆ Get a list of files in the boot directory excluding the BOOT.??K file

Router

All Netbuilder II Models

http://support.3com.com/infodeli/tools/bridrout/u_guides/html/index.htm

No

Syslogs, SNMP Trap

running

ARP, Routes, Interfaces, Identity, System Properties

Telnet/TFTP, SSH/TFTP

CLI, SNMP

SNMP

In-Band



Terminal

Ping

Model, OS


3COM Devices

• copy [FILENAME] [SERVERIPADDR]:[FILENAME]

Configuration deploy

The following are the commands, or processes that are used to "push" a configuration to your device.

◆ For each file backup above:

• copy [SERVERIPADDR]:[FILENAME] [FILENAME]

Multi-config files Following are the files used when storing and revisioning multiple configuration files for multi-config support.

Multi-config files Push/pull Pull only

Device data The following data represents device data per device class.

Attributed data Support

running

ARP Table Yes

Access Control Lists No

CAM Table No

File System Information No

Identity Yes

Interfaces Yes

Keys No

Memory No

Access Control Lists Match Counts No

OSPF Settings No

Physical Hardware No

Routes Yes

System Properties Yes

VLAN Trunk Protocol No

VLANs No

3Com Netbuilder II Router 35

3COM Devices

3Com Switch 5500

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available

◆ Discover/Identify (Auto Discovery, Identify, Appear in Product)

◆ Configuration Capture (Revision Config, Rollback, Basic Diagramming)

◆ Configuration Deploy (Push Configs, Configlets)




◆ sysDescription contains Switch 5500 (case-insensitive)



◆ display current-configuration

◆ display saved-configuration

◆ display startup

◆ tftp deviceServerAddress put filename filename

Switch

5500

http://www.3com.com

No

Single ASCII

Quick Commands, Termlet Merge, Command, Configlet, Config

Telnet, SSH, Telnet/TFTP, SSH/TFTP

Command Line Interface

SNMP

In-band, SNMP

3.02



Terminal

Ping, Traceroute, View Routes, View Arp, View Interfaces

Memory, Serial Number, OS Version, Inventory


3COM Devices



◆ startup configuration can only be transferred using TFTP

◆ tftp deviceServerAddress get filename filename

Device commands

The following device command sets must be enabled to allow VoyenceControl NG to manage this device class.

◆ Device Configuration and Monitoring

display current-configuration

display saved-configuration

display startup

tftp deviceServerAddress [ get | put | localFilename remoteFilename

copy sourceFilename destFilename

save filename

delete filename

ping ipAddress

tracert ipAddress

display ip interface

display ip routing-table

display arp

◆ Password Management

display password-control

local-user userName

level 2

service-type terminal telnet ssh

password [ simple | cipher ] password

quit

undo local-user oldUsername

super password [ simple | cipher ] newPrivPass

snmp-agent community [ read | write ] newString

undo snmp-agent community oldString

3Com Switch 5500 37

3COM Devices

Multi-config files

Following are the files used when storing and revisioning multiple configuration files for multi-config support.


Device data

The following data represents device data per device class.


Known issuesThe following details existing device issues that have been discovered with other releases. In most cases, a resolution is included to address the issue.

3Com Switch 5500

◆ Editing comments generated by the device when capturing the configuration causes device warnings during push operations.

◆ Inconsistencies in command behavior for configuration and credential management appear in software version 3.01, but not later versions.

• Startup configurations are the only file types retrieved.

Running

Startup


ARP Table No

CAM Table No

Device Identity Yes


Hardware Information Yes

Interfaces Yes

Keys No

Memory Yes

OSPF Routing Configuration No

Static Routes No


VLANs No



3COM Devices

• User credentials cannot be removed during password rolls, due to the session use count. The error message User access number not 0 is displayed. Manual removal of the user credentials is untested but might be successful.

3Com Switch 5500 39

3COM Devices


4

ACME Devices


◆ ACME NetNet SBC ....................................................................................................... 42

ACME Devices 41

ACME Devices

ACME NetNet SBC

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available


◆ Configuration Capture (Revision Configuration, Rollback, Basic Diagramming)

◆ Configuration Deploy (Push Configurations)

◆ Device Access (Cut-Through, Device Commands)

◆ Configuration Change Notification (SNMP Trap, Syslog Processing)

Discovery/identify methodsThe following items are used to provide information about your device (Host Name, Type, Vendor, Model, Operating System, and Serial Number).

◆ Model, Serial Number, and Operating System version using SNMP or command line interface

◆ Memory using command line interface

◆ File Systems using command line interface

◆ Interface table using SNMP or command line interface

Session Border Controller

4250

www.acmepacket.com

Yes

Syslog, SNMP Traps

Running, Startup, Text

Quick Commands, Termlet, Command, Configlet, Config

SSH, Telnet, SSH/FTP and Telnet/FTP

Command Line Interface

SNMP, Terminal

In-Band

6.1

SSH, Telnet, SSH/FTP, Telnet/FTP

SSH/FTP, Telnet/FTP

Terminal

Ping, View ARP, View Routes, View Interfaces, Resync, Reboot

Hardware Inventory (SNMP Only), Memory, File Systems, Interfaces, Serial Number


ACME Devices


Following are the commands or processes used to "pull" a configuration from your device.

◆ From a command line interface session, the output of show running-config is captured as the text config.

◆ From a command line interface session, the command backup-config [filename] is issued. That file is then transferred from the SBC using FTP and stored in binary form as the startup config.

◆ From a command line interface session, the command backup-config [filename] running is issued. That file is then transferred from the SBC using FTP and stored in binary form as the runnning config.

Configuration deployFollowing are the commands or processes used to "push" a configuration to your device.

◆ The text config , as captured, cannot be pushed to the device. Configlets must use the text config for the destination.

◆ A stored startup or running config is pushed to the system by transferring it to the system using FTP and issuing the command-line interface command restore-backup-config [filename].

◆ After successfully pushing a config or configlet, the default action is to issue a save-config command followed by an activate-config command. Optionally, this can be changed at push time to save-config (without an activate-config) or save-config followed by a reboot activate command.

Multi-config files



Device dataThe following data represents device data per device class.

Running

Startup

Text


ARP Table Yes


CAM Table No

ACME NetNet SBC 43

ACME Devices

File System Information Yes

Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No

Physical Hardware Yes

Routes Yes



VLANs No



ACME Devices

Known issues

The following information details existing device issues that have been discovered within other releases. In most cases, a resolution is included to address the issue.

ACME NetNet SBC

◆ The ACME NetNet SBC driver is known not to work with pre-v6.1 systems, due to substantial differences in the way that configuration backups work.

◆ Models other than the 4250 may need to be manually added to the driver's models file, due to ACME Packet not supplying a comprehensive list of SNMP Model OIDs.

◆ Pushing configlets to these systems may be problematic due to the way ACME's configuration editing works. In order to edit many configuration items, such as SNMP communities, the user must select an existing item to edit, which this driver cannot do. If you have advance knowledge of the system's configuration you may be able to create a configlet that works, but VoyenceControl does not support the concept of selecting a configuration item to edit.

◆ Configlets always use the text config for the destination.

◆ A configlet is processed in the device's configuration mode. Ensure not to exit completely out of config mode, as this causes the job to fail.

◆ Selection prompts are considered valid config prompts. The following configlet is now valid:

system

snmp-community

sel

public

1

ip-addresses (1.1.1.1 2.2.2.2)

done

exit

exit

ACME NetNet SBC 45

ACME Devices


5

Adtran Devices


◆ Adtran NetVanta ........................................................................................................... 48◆ Adtran NetVanta Switch .............................................................................................. 51

Adtran Devices 47

Adtran Devices

Adtran NetVanta

Device Type

Specific Model(s)


Operating System

Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access


Features available

◆ Discover/Identify (Quto Discovery, Identify, Appear in Product)


◆ Configuration Deploy (Push Configurations, Configlets)


◆ Operating System Management


◆ sysObjectID

• 1.3.6.1.4.1.664

Adtran NetVanta

NetVanta 3120, NetVanta 3200, NetVanta 3305, NetVanta 3205, NetVanta 5305, NetVanta 4305, Atlas 800, Atlas Generic, Atlas 800 Plus, Atlas 810, Atlas 550, Total Access 916e

-

04.02.00, 05.02.00, 05.03.00, 06.01.00

Yes

Single Text, Running, Startup

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet

Telnet/TFTP, SSH Only, Telnet Only

IOS like

SNMP, Telnet, SNMP

Enable, In-Band, SNMP

Terminal, SSH, TFTP

Terminal, SSH, TFTP

Terminal

For SNMP: Memory, Interfaces, Serial Number, Hardware Inventory (Terminal Only)


Adtran Devices



◆ Telnet/TFTP

• copy startup-config tftp

• copy running-config tftp

◆ Telnet/SSH

• show startup

• show running

• copy running-config startup-config

Multi-config files



Device data


running

startup

Attributed Data Support

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes

Adtran NetVanta 49

Adtran Devices

Known issues


Adtran NetVanta drivers

◆ Adtran NetVanta and Adtran NetVanta Switch drivers may experience problems if configured with the message of the day banner.

Adtran NetVanta Router - Serial Numbers not Displaying

◆ The Adtran NetVanta Router does not show the serial number when using SNMP.



VLANs No



Adtran Devices

Adtran NetVanta Switch

Device Type

Specific Model(s)


Operating System

Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access


Features available



◆ Configuration Deploy (Push Configurations, Configlets)




◆ sysObjectID

• 1.3.6.1.4.1.664

◆ adtranIfNumber

• .1.3.6.1.2.1.2.1.0

• Should be greater than 4

Adtran NetVanta Switch

NetVanta 1224, NetVanta 1224R, NetVanta 1224 STR

-

06.01.03

Yes

Single Text

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Configlet


IOS like

SNMP


Terminal, SSH, TFTP

Terminal, SSH, TFTP

Terminal

Memory, Interfaces, Serial Number, Software Version, Hardware Inventory

Adtran NetVanta Switch 51

Adtran Devices



◆ Telnet/TFTP



◆ Telnet/SSH

• show startup

• show running


Multi-config files



running

startup


Adtran Devices

Device data



Known issues


Adtran NetVanta Switch drivers

◆ Adtran NetVanta and Adtran NetVanta Switch drivers may experience problems if configured with the message of the day banner.

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Adtran NetVanta Switch 53

Adtran Devices


6

Adva Devices


◆ Adva FSP150CC ............................................................................................................ 56

Adva Devices 55

Adva Devices

Adva FSP150CC

Device Type

Specific Model(s)


Operating System

Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands

Features available◆ Discover/Identify (Auto Discovery, Identify, Appear in Product)



◆ Credential Roll

◆ Device Access (Cut-Through, Device Commands, etc.)


• Model, serial number, and operating system version using SNMP or command-line interface

• Interface table using SNMP or command-line interface

Switch

FSP150CC-825,FSP150CCD-410

http://www.advaoptical.com/

2.1, 7.0

No

Running, Startup

Quick Commands, Configlet, Termlet, Command, Config


Command-Line Interface

SNMP, Terminal

In-Band



Terminal

Ping, Traceroute, View Routes, View ARP, View Interfaces


Adva Devices



◆ Running configuration using SSH or Telnet:

• show running-config command is issued in the command-line interface, and the file captured directly from the command-line interface output.

◆ Startup configuration using SSH/FTP or Telnet/FTP:

• The command database backup is issued.

• The command database copy ftp put [serverip] [username] [password] [filename] is issued in the command-line interface to transfer the file to an FTP server running on the device server.


Following are the commands or processes used to "push" a configuration from your device.


• A command-line interface session is started in config mode. The config is entered line by line while monitoring responses for error messages.

• By default, the running config is copied to the startup by issuing the database save command. This can be disabled when the job is scheduled.

◆ Startup configuration using SSH/FTP or Telnet/FTP:

• The command database copy ftp get [serverip] [username] [password] [filename] is issued in the command-line interface to transfer the file from an FTP server running on the device server, to the device.

• The command database restore active none is issued.

• By default, the system is rebooted. This can be disabled when the job is scheduled.

Multi-config files



running

startup

Adva FSP150CC 57

Adva Devices

Device data



Known issues


Adva FSP150CC

◆ This device can only transfer binary files using an external FTP server located on the device server. It is the customer’s responsibility to setup and maintain a correctly configured FTP daemon on the appropriate device server.

◆ The driver will default to using the FTP credentials: anonymous / [email protected]. The defaults can be changed on a device by device basis using the quick command named Set_FTP_Credentials.

◆ Some lines in the text (running) config cannot be sent back to the device using terminal input.

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No


7

Airespace Devices


◆ Airespace Switch ........................................................................................................... 60

Airespace Devices 59

Airespace Devices

Airespace Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Features available◆ Discover/Identify (auto discovery, identify, appear in product)

◆ Configuration Capture (revision config, rollback, basic diagramming)




◆ sysObjectID

• 1.3.6.1.4.1.14179

◆ sysDescr, Switch

• Contains Airespace Switch

Wireless Switch

Airespace Switch AS-4101,AIR-WLC4404-100-K9,WS-SVC-WISM-1-K9

-

Yes

Binary Image

Binary

Telnet, TFTP, SSH

CLI

SNMP Only

Account, SNMP

2.0.152.3

Terminal/TFTP, SSH/TFTP

Terminal/TFTP, SSH/TFTP, Terminal

Terminal

For SNMP: Memory, Interfaces, Serial Number


Airespace Devices



◆ transfer upload


Following are the commands or processes used to "push" a configuration to your device.

◆ Transfer download

◆ Terminal, one line at a time

Multi-config files



Device data



running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Airespace Switch 61

Airespace Devices

Known issues


Airespace 4400

◆ Issue: Over time, a client Out of Memory message may be displayed when opening or searching Checkpoint Firewall or Airespace device configurations that contain large binary files.

◆ Resolution: If a client Out of Memory message is displayed, first close, and then re-open the application.


8

Alcatel Devices


◆ Alcatel OmniAccess ...................................................................................................... 64◆ Alcatel OmniCore.......................................................................................................... 68◆ Alcatel Omnistack ......................................................................................................... 71◆ Alcatel Omniswitch ...................................................................................................... 75◆ Alcatel Service Router and Ethernet Service Switch................................................ 81

Alcatel Devices 63

Alcatel Devices

Alcatel OmniAccess

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available

◆ Discover/Identify (Auto Discovery, Identify, Appears in Product)


◆ Configuration Deploy (Push Configs, Configlets, Termlets)

◆ Credential Roll (Enable Password, SNMP Credentials, Account Password)



◆ For SNMP:

• Sys Object Id

– 1.3.6.1.4.1.6486.800.1.1.2.2.2.1.1.2◆ For Terminal:

• show version includes manufacturer and model information

• show running-config includes hostname information

Alcatel OmniAccess Switch

Alcatel OmniAccess 4324

http://enterprise.alcatel-lucent.com/

Yes

Startup, Running

Config, Quick Commands, Configlet, Termlet, Command

SNMP, SSH, Telnet


SNMP, Terminal

Enable, SNMP, Account

AOS-W 3.4, AOS-W 3.3.2.10

SSH, Telnet

SSH, Telnet

Terminal

Setup Diagnostic, View Diagnostic, Setup NAT, View NAT

Terminal


Alcatel Devices



◆ For Telnet or SSH:

• The configuration is pulled using the show running-config or show startup-config command.

◆ For Telnet/TFTP or SSH/TFTP:

• The configuration is pulled using the copy startup-config tftp and copy running-config tftp commands.



◆ Push Running using Telnet, SSH:

• A command-line interface session is started in config mode.

• The configuration is pushed line by line while checking responses for error codes.

◆ Push Startup using Telnet/TFTP, or SSH/TFTP:


• The configuration is pushed via TFTP as a file using copy tftp and copy flash commands

Multi-config files



running

startup


Alcatel Devices



Known issues The following details existing device issues that have been discovered with other releases. In most cases, a resolution is included to address the issue.

Alcatel OmniAccess

◆ The configuration information obtained from a running config pull cannot be pushed back to the device. The running config push is done on a line by line basis through the command-line interface in config mode,due to there being no way to push an entire config file to running.

◆ Some commands are not accepted and must be removed from the configuration before pushing a full configuration. A few examples of lines that must be removed are:

• version 3.3

• enable secret "******"

• end

◆ Some commands are not valid and should be removed or replaced with valid commands before pushing a full configuration. A few examples of lines that must be removed or replaced are:

• mms config 0

• controller config 0

• ip access-list eth validuserethacl

permit any

• ip access-list session validuser

any any any permit

ARP Table Yes


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes Yes



VLANs No


Alcatel Devices

• vpn-dialer default-dialer

ike authentication PRE-SHARE ******

• user-role ap-role

• user-role denyall

session-acl denyall

• user-role cpbase

session-acl cpbase

• user-role guest-logon

• user-role guest

• user-role stateful-dot1x

• user-role logon

• aaa pubcookie-authentication

• no crypto isakmp psk-caching

• no crypto-local isakmp permit-invalid-cert

• crypto isakmp groupname changeme

• crypto-local isakmp dpd idle-timeout 22 retry-timeout 2 retry-attempts 3

• crypto-local isakmp xauth

• vpdn group l2tp

ppp authentication PAP

• vpdn group pptp

ppp authentication MSCHAPv2

• mgmt-user admin root 9bf216ef01dc8a58fdecefdd48e9482a5ef57ed326a34ffd75

• country US

◆ Some commands can only be pushed to the master switch and are not valid for a local switch. These commands are displayed in the configs pulled from the device, but must be removed from the configs before pushing. See the AOS-W User Guide for more information.


Alcatel Devices

Alcatel OmniCore

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access


Features available

◆ Discover/Identify (auto discovery, identify, appear in product)






◆ SysObjectID

• 1.3.6.1.3.3003 or 1.3.6.1.4.1.3003

◆ sysDesc

• contains "Switch"

Alcatel Omnicore Routing Switch

OmniCore 5052, OmniCore 5022 OmniCore 5010, OmniCore 13 OmniSwitch 5, OmniSwitch 9, OmniCell 5, OmniCell 9, OmniStack 1024, OmniStack 6024, OmniStack 8008, OmniAccess 408, OmniAccess 512

-

Yes

Single Text

Termlet Merge, Privilege Mode Termlet, User Mode Termlet

SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only

Command Line

SNMP

In-Band, SNMP

Terminal, SSH, TFTP

Terminal, SSH, TFTP

Terminal

For SNMP: Memory, Interfaces


Alcatel Devices



◆ Term

• write-config

◆ TFTP

• write-config tftp://"+SERVERIPADDR+"/"+tftpFile(configFile.filename)



◆ Copy to start

• write mem

◆ TFTP

• copy tftp:…

◆ Term

• Push is done by pushing one line at a time after connecting to a terminal session

Multi-config filesFollowing are the files used when storing and revisioning multiple configuration files for multi-config support.

Multi-Config files Push/pull Pull only

Device data


running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes

Alcatel OmniCore 69

Alcatel Devices


OSPF Settings No


Routes Yes



VLANs No



Alcatel Devices

Alcatel Omnistack

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System

Operating System Management



Cut-Through Access

Switch Quick Commands



◆ Configuration Capture (Revision Config, Basic Diagramming)

◆ Device Access (Cut-Through, Termlets)

◆ Credential Management (In-band, SNMP)

◆ Operating System Management (OS Upgrade)


◆ sysObjectId

• contains 1.3.6.1.4.1.6486.800.1.1.2.2.4.1

◆ Serial Number retrieved successfully from ENTITY-MIB for row with class chassis (3)

Switch

6624, 6246, 8008, LS6224U

http://service.esd.alcatel-lucent.com/

No

Single ASCII

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config



SNMP

In-band, SNMP

1.0.0.47, 1.7.0.13For LS6224U Models: 1.5.1.7

SSH/TFTP, Telnet/TFTP



Terminal

Ping, Traceroute, View Interfaces, View Arp

Memory, Interfaces, Serial Number, OS Version, Inventory

Alcatel Omnistack 71

Alcatel Devices



◆ Telnet, SSH:

• show running-config

• show startup-config

◆ Telnet, SSH with TFTP:



Configuration deployThe following are the commands, or processes that are used to "push" a configuration to your device.

◆ Telnet, SSH:

• Commands are issued to the command line interface in Non-TFTP mode

◆ Telnet, SSH with TFTP:

• copy tftp running-config

• copy tftp startup-config

Device commandsFollowing are the device command sets you must enable to allow VoyenceControl NG to manage this device class.


config

enable

disable

(no) terminal datadump

show running-config

show startup-config

ping

traceroute

show ip interface

show arp


(no) snmp-server community

(no) username

enable password level 15


Alcatel Devices

◆ OS Management

show bootvar

boot system name





running

startup

ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes No



VLANs No

Alcatel Omnistack 73

Alcatel Devices

Known issues

The following details existing device issues that have been discovered with other releases. In most cases, a resolution is included to address the issue.

Alcatel Omnistack

◆ Push-to-Start using Telnet/SSH not supported.

◆ No volatile memory support using SNMP or command line interface

• Blank values are displayed in the client.

◆ Image files are listed in the file system information. Image files cannot be selected and backed up by name due to a limitation of the device. The active image can be backed up as an upgrade option.

◆ Boot file upgrades are not supported.


Alcatel Devices

Alcatel Omniswitch

Device Type

Specific Model(s)


Enabled By Default

Operating System

Configuration Files

User Interface


Password Management




Cut-Through Access

Quick Commands


Features available




◆ Configuration Change Notification (SNMP Trap)

◆ Credentials Management (Change or Roll passwords and SNMP Communities)

◆ Operating System Management (Upgrade OS)

◆ Dynamically Handled Sync (Stacked Devices)

Switch

6602-48, 6624, 6850, OS6850-P48, 7700,9700, OS9616/OS9716-CFM2

CD-ROM Copy

Yes

Operating systems for 6602-48 models: 5.1.6.243.R02 GA, 5.1.6.393.R01 GAOperating systems for 6850 models: 6.3.1.999.R01Operating systems for 7700 and 9700 models: 6.3.1.1023.R01Operating systems for other models: 5.1.5.83.R04, 6.3.4.378.R01 GA, 6.4.1.394.S01 GA

Single Text


SNMP, SSH, Telnet

Account, SNMP

SSH/FTP, Telnet/FTP

Telnet, SSH, Telnet/FTP, SSH/FTP


Terminal

View Interfaces, View Routes, View ARP, Ping, Traceroute

Memory, Interfaces, Serial Number, Software Version, Inventory

Alcatel Omniswitch 75

Alcatel Devices


The following items are used to provide information about your device (Host Name, Type, Vendor, Model, Operating System, and Serial Number).

◆ For SNMP:

• sysObjectID value contains 1.3.6.1.4.1.6486.800.1.1.2.1

• Serial number is found in row (chassis class) of entPhysicalTable in ENTITY-MIB

◆ For Terminal:

• sysObjectID is present in show system output

• Value contains 1.3.6.1.4.1.6486.800.1.1.2.1

Configuration captureThe following are the commands, or processes that are used to "pull" a configuration from your device.

◆ For Terminal:

• show configuration snapshot

◆ For File Transfer:

• Configuration is pulled using FTP



◆ For Terminal:

• Device commands are issued interactively from the stored configuration (configlet only); each command is sent line-by-line as long as the device returns to a prompt afterwards. The results are scanned for warnings and errors.

◆ For File Transfer:

• Configuration is pushed using FTP

Additional Driver Functionality

The Omniswitch driver now manages all three configurations for the device class (running/RAM, working/warm-boot, and certified/cold-boot).

The following post-operations are available based on the destination configuration for the push:

◆ running - the volatile configuration changed from the command line.

• Copy to Working

– Syncs the volatile and warm-boot configurations.◆ working - the non-volatile configuration in /flash/working/boot.cfg.

• Made active with “reload working no rollback-timeout”.

• Copy to Certified


Alcatel Devices

– Syncs the cold-boot from the warm-boot configuration.• Reboot from Working

– Boots from /flash/working/boot.cfg.– See the Known Issues for more information.

◆ certified - the non-volatile configuration in /flash/certified/boot.cfg.

• Made active with “reload”or a cold boot.

• Copy to Working

– Syncs the warm-boot from the cold-boot configuration.• Reboot

– Boots from /flash/certified/boot.cfg.

Resync InformationThe Resync menu command can alter both working and certified configurations. The Omniswitch provides no direct command to write from running to certified. If any configuration pairs are out-of-sync, the following scenarios apply:

◆ running and working out-of-sync:

• copy running working

– Changes the working configuration if successful• copy working certified

– May change the software version on the next cold start.– See the Known Issues for more information.

◆ running and working configurations in-sync, working and certified configurations out-of-sync:

• copy working certified

• Issued to change the certified configuration.

• May change the software version on the next cold start.

• See the Known Issues for more information.

Note: Unlike previous versions of the driver, it is possible for the running and working configurations to be different. In practice, copying to the certified configuration should only be done once operation of the working configuration is satisfactory, as it is the fallback provisioning for the device. The “Copy Working to Certified” and “Copy Certified to Working” post operations are not default choices in the user interface.

Device commands

Following are the device command sets you must enable to allow VoyenceControl NG to manage this device class.


show system

show running-directory

no more

ping

reload working no rollback-timeout

show arp


Alcatel Devices

show chassis

show cmm

show configuration snapshot

show hardware info

show health

show interfaces

show ip interface

show ip protocols

show ip route

show module long

show running-directory

show system

traceroute

◆ File Management

cd

copy running-config working

copy working certified [flash-synchro]

copy certffied working

delete

freespace

ftp

hash

ls


[no] snmp community map

[no] user

password

show snmp community map

show user

show user password-size


Alcatel Devices

Multi-config files



Device data



running

working

certified

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No


Alcatel Devices

Known issues


Alcatel Omniswitch

◆ Full configuration pushes for the working and certified files require FTP to be enabled. Configlets and the running configuration use terminal mode only.

◆ Cold booting the device will use the configuration stored in /flash/certified/boot.cfg unless it is identical to /flash/working/boot.cfg. If these files differ, the reload working no-rollback timeout command must be issued or configuration changes will fail. This can be done using cut-through.

◆ The Reboot from Working post-operation on configuration pushes does not warn the user about service interruption.

◆ Post operations on working and certified configurations may potentially change the operating system version of the device if it is rebooted afterwards. This is due to the use of “copy working certified” and “copy certified working” commands for these operations. It is the user’s responsibility to ensure that configuration content is compatible if the software images in the working and certified directories differ.

◆ SNMP credential rolls are not written to the certified (startup) configuration, which is a device limitation in the copy command syntax (as detailed in the previous bullet). The commit operation used after account and SNMP rolls uses “copy running working” to avoid copying software images as part of SNMP credential changes.

◆ The model name is reported differently through SNMP than through terminal: SNMP uses the chassis entry of ENTITY-MIB, while the terminal query uses the “Model Name:” field in the “show system” response, which corresponds to the CMM model.


Alcatel Devices

Alcatel Service Router and Ethernet Service Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands




◆ Configuration Deploy (Push Configs)

◆ Credential Roll (In-Band, SNMP)

◆ Device Access (Cut Thru, Device Commands, etc.)

◆ Operating System Management (TFTP)



◆ Model, Serial Number and Operating System version using SNMP or Command-Line Interface

◆ Interface table using SNMP or Command-Line Interface

Alcatel SR Router

7450 ESS-1, 7450 ESS-6, 7450 ESS-7, 7450 ESS-12,7750 SR-1, 7750 SR-12

http://www.alcatel-lucent.com

No

Boot Options, Startup, Running




SNMP, Terminal

Account, SNMPv1/2

SR OS Release 5 (B-5.0.R8, C-5.0.R8), TiMOS-6.1.R9Untested: 7.0.R9



Telnet, SSH

TFTPUntested: FTP

Traceroute

Identity, Serial Number, Software Version, Memory, Filesystem, Inventory

Alcatel Service Router and Ethernet Service Switch 81

Alcatel Devices



◆ For SSH or Telnet

• The admin display-config command is issued in the command line interface, and the file captured directly from the command line interface output.

◆ For SSH/FTP or Telnet/FTP

• The startup-config (config.cfg) or boot-options-file (bof.cg) is copied using FTP.



◆ For SSH or Telnet

• The command configuration file contents are entered line-by-line directly into the CLI.

◆ For SSH/TFTP or Telnet/TFTP

• The startup-config (config.cfg) or boot-options-file (bof.cfg) is copied to the device using FTP.

Configuration activationsFollowing are the commands or processes used to "activate" a configuration deployed to the device.

◆ For SSH or Telnet:

• These commands are immediately active on the device. The Save post operation allows for saving the running configuration to the startup (config.cfg) file using the admin save command.

◆ For SSH/FTP or Telnet/FTP

• Files are directly copied to the default destinations. For the config.cfg file the Load post operation loads the file using the exec command. For the bof.cfg file the Reboot post operation will reboot and restart the device thereby activating the boot-options-file.



Startup

Running

Boot-options-file


Alcatel Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Alcatel Service Router and Ethernet Service Switch 83

Alcatel Devices

Known issues


Alcatel Service Router and Ethernet Service Switch

◆ The serial number can not be obtained using SNMP. A serial number of Unknown will be displayed if the correct account credentials are not supplied.

◆ A user cannot delete their own account due to device limititations.

◆ Any attempt to roll credentials to a new user account will leave the existing account in place. The account must be deleted using a configlet or cut-through to the device. Attempts to roll user names may result in a warning with the message: CLI Users cannot delete themselves. Old user name must be removed manually.

◆ OS upgrade:

• Standard upgrade is supported

• In-Service upgrade and AA Signature upgrades are not supported.

• Service Router upgrade capability is unverified.

• The operating system repository must use a path for the images, since the files themselves do not have versioning information in the names. The path must be only one level deep. Support for creating nested directories on the supported devices has not been implemented.

– It is advisable that the operating system version be used for the directory in which the images reside, since this is used for the device image directory and the primary-image boot option setting.

– If only one set of images is present in the repository, and no path is specified, the name SW_UPGRADE will be used.

• The upgrade fails in the scheduler if the following conditions are not present:

– The boot.ldr file must be part of the selected images.– For a one-slot chassis, the both.tim file must be included along with the boot

loader.– For a redundant SFM/CPM device, both CPM and IOM image files must

be included along with the boot loader.


9

Alvarion Devices

This chapter contains the following topic:

◆ Alvarion Breeze AP....................................................................................................... 86

Alvarion Devices 85

Alvarion Devices

Alvarion Breeze AP

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System


Cut-Through Access

Quick Commands







◆ sysName OID

◆ sysServices: bit 3 set

◆ brzAccUnitType (from Breeze-Access-MIB)


◆ Main > Info > Advanced Configuration

Wireless Access Point

BreezeACCESS SU-A/E-BD

http://www.alvarion.com

No

ASCII Capture (no push)

Config

Telnet

Menu

SNMP

In-band

4.5.17

Telnet

Terminal

Test Credentials

Chassis inventory


Alvarion Devices

Device commands

The following device menus must be enabled to allow VoyenceControl NG to manage this device class.


Advanced Configuration


Unit Control





running


ARP Table No

CAM Table No

Device Identity Yes


Hardware Information No

Interfaces Yes

Keys No

Memory Yes


Static Routes No


VLANs No


Alvarion Breeze AP 87

Alvarion Devices

Known issues


Alvarion Wireless Access Point

◆ Incorrect password specification leaves the login screen in an unusable state. If this occurs, the user must manually login to the device and clear the prompt.

◆ SNMP credentials are mapped to user accounts; the corresponding read/write SNMP community change must be saved (not pushed) in the UI prior to initiating the corresponding admin credential roll.

◆ Device settings are distributed among several menus. The driver displays their contents, but the results cannot be pushed.


10

Aruba Devices


◆ Aruba Wireless Switch.................................................................................................. 90

Aruba Devices 89

Aruba Devices

Aruba Wireless Switch

Device Type

Specific Model(s)


Enabled By Default


Configuration Files




Password Management



Cut-Through Access








◆ SysObjectID contains one of the following:

• 1.3.6.1.4.1.14823

• 1.3.6.1.4.1.6486.800.1.1.2.2.2.1.1.4

Configuration captureFollowing are the commands or processes used to "pull" a configuration from your device.

◆ Telnet


Aruba Switch

a52, a50, a800, a2400, a5000, Alcatel OAW-6000

-

Yes

Syslog, SNMP Traps

Single Text

Quick Commands, Termlet Merge, Privilege Mode Termlet, Configlet, Config

SSH/TFTP, Telnet/TFTP, Out of Band, SSH, Telnet

SNMP

In-Band, SNMP

Telnet, SSH, Out of Band, Telnet/TFTP, SSH/TFTP


Terminal

Memory, Interfaces, Serial Number, OS Version


Aruba Devices

◆ Term

• show startup

• show run



◆ TFTP

• copy tftp running-config


◆ Term

• Connect to configuration mode and send one line at a time to the device

Multi-config files



running

startup

Aruba Wireless Switch 91

Aruba Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


11

AudioCodes Devices


◆ AudioCodes MediaPack............................................................................................... 94

AudioCodes Devices 93

AudioCodes Devices

AudioCodes MediaPack

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands

Features available




◆ Credential Roll



• Model, serial number, and operating system version using SNMP or command-line interface

• Interface table using command-line interface

Switch

MP-118FXS

http://www.audiocodes.com/

No

Running


SSH, Telnet


SNMP, Terminal

In-Band

5.6

SSH, Telnet

SSH, Telnet

Terminal

Ping, View Routes, View Interfaces


AudioCodes Devices




• /conf/cf get command is issued in the command-line interface.

• The file is captured directly from the command-line interface output.



◆ Full configuration using SSH or Telnet:

• A command-line interface session is started and the command /conf/cf set is entered.

• The system waits for the Type a . on an empty line prompt.

• The config is sent to the command-line interface session all at once followed by a period on an empty line.

• The system waits for the INI file replaced message.

• By default, following a successful push, the command /conf/sar is sent to the device to save the changes and reload the system. This can be disabled when the job is scheduled.

◆ Configlet using SSH or Telnet:

• A command-line interface session is started. Each line of the configlet is sent, one by one, preceded by the text /conf/scp.

• The responses are monitored for any error messages, and the job is stopped if an error is encountered.

• Following a successful push, the command /conf/sar is sent to the device to save the changes and reload the system. This default setting can be disabled when the job is scheduled

Multi-config files




running

AudioCodes MediaPack 95

AudioCodes Devices


ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


AudioCodes Devices

Known issues


AudioCodes MediaPack

◆ Full configs MUST use the INI file format.

◆ Configlets may be in either INI file format (parameter=value) or SetConfigParam format (parameter value). Do not include the /conf/scp command in configlet lines.

◆ If credential roll is used to add or change community strings, the new string will always be stored in string one.

AudioCodes MediaPack 97

AudioCodes Devices


12

BlueCoat Devices


◆ BlueCoat SG ................................................................................................................. 100

BlueCoat Devices 99

BlueCoat Devices

BlueCoat SG

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands





◆ Credential Management (In-band)


◆ sysObjectID

• Contains 1.3.6.1.4.1.3417.1.1

◆ sysDescr

• Contains Blue Coat SG

◆ sysObjectID

◆ Maps to model in BlueCoatSGModels.xml

Content Cache

Web Proxy

http://www.bluecoat.com/support/manuals

No

Single ASCII


SSH, Telnet, SSH/TFTP, Telnet/TFTP


SNMP

In-band

6.0.0



Terminal

Traceroute, View Interfaces, View Arp, View Routes

Serial Number, OS Version, Inventory


BlueCoat Devices



◆ Telnet/SSH:

◆ show configuration expanded noprompts

◆ Telnet/SSH (with TFTP):

◆ archive-configuration protocol tftp

◆ archive-configuration host ipAddress

◆ archive-configuration path ""

◆ archive-configuration filename-prefix remoteFilename

◆ upload configuration



◆ Telnet/SSH:

• commands are issued to the CLI and the results scanned for errors

◆ Telnet/SSH (with TFTP):

• configure network "tftp://ipAddress/remoteFilename"



Device data


running


ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

BlueCoat SG 101

BlueCoat Devices


BlueCoat SG

◆ No volatile or non-volatile storage information is available using SNMP for this device class.

◆ Account password rolls are performed on a device-wide account. Content is the responsibility of the user.

◆ Configuration pushes using terminal protocols (Telnet/SSH) may experience timeout problems when content includes nested inline commands. The first occurrence of end-*-inline causes the driver to expect a command prompt. This does not occur when TFTP is used for configuration management.

For example:

inline exceptions end-383770416-inline

additional content...

inline exceptions end-383770416-inline


)

end-383770416-inline


)

end-383770416-inline

Memory No



Static Routes No



VLANs No



13

Brocade Devices


◆ Brocade 7500 ................................................................................................................ 104◆ Brocade McData .......................................................................................................... 107

Brocade Devices 103

Brocade Devices

Brocade 7500

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System


Cut-Through Access





◆ Credential Management (In-Band, SNMP)


◆ sysObjectID

• 1.3.6.1.4.1.1588.2.1.1.1



◆ configShow

Router

7500

http://www.brocade.com/support/resources.jsp

No

Single ASCII

Privilege Mode Termlet, User Mode Termlet, Configlet

SSH, Telnet


SNMP

In-Band, SNMP

6.0.0

Telnet, SSH

Terminal

Interfaces, Serial Number, OS Version, Hardware Inventory


Brocade Devices

Device commands

The following device menus must be enabled to allow VoyenceControl NG to manage this device class.

◆ Device Configuration

configShow

switchShow


snmpConfig --show snmpv1

snmpConfig --set snmpv1

passwd

userConfig --add

userConfig --delete



Device data


running


ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No

Brocade 7500 105

Brocade Devices

Known issues


Brocade 7500 Router

◆ Configurations cannot be pushed in this version of the driver. The configuration displayed in response to showConfig from the command line interface does not have the same form as the commands used to configure the device.

◆ Although configuration files can be pushed and pulled by the device acting as a client using FTP/SCP, the necessary credential and server support for VoyenceControl is not implemented.

◆ No volatile or non-volatile storage information is available using SNMP for this device class.



VLANs No



Brocade Devices

Brocade McData

Device Type

Specific Model(s)


Configuration Files



User Interface


Operating System


Cut-Through Access

Quick Commands


Features available


◆ Configuration Capture (revision config, FRU list)

◆ Device Access (Cut-Through)


◆ For SNMP:

• sysDescr

– Value contains Fibre Channel Switch

• sysObjectID value contains one of the following:

– 1.3.6.1.4.1.289.2.1.1.2

– 1.3.6.1.4.1.289.2.2.1.2.2

◆ For Terminal:

• sysObjectID can be mapped to a model in McDataModels.xml

Switch

010000, 004500, 006064, 006140

-

ASCII Capture (no push)

Config

Telnet, SSH


SNMP, Terminal

9.6.1.5, 9.2.0.8, 09.02.01, 05.01.00

Telnet, SSH

Terminal

Test Credentials

Model, Serial Number, Software Version, FRU List (Non-SNMP only)

Brocade McData 107

Brocade Devices



◆ This device class uses a set of configurable commands in the [Product Home]/package/pkgxml/McData/McDataDeviceCommands.xml file for displaying various settings in a user-defined order.

◆ The comments in the above file include directions on changing this order, adding future model command support as software versions, and new supported products in the family.

Device commands

Following are the device command sets you must enable to allow VoyenceControl to manage this device class.

◆ This device class uses a set of configurable commands in the [Product Home]/package/pkgxml/McData/McDataDeviceCommands.xml file for obtaining configuration, hardware, and other device information in a user-defined order.

◆ The comments in the above file include directions on changing this order, adding future model command support as software versions, and new supported products in the family.

Known issuesThe following details existing device issues that have been discovered with other releases.

Brocade McData

◆ Memory and flash are not available from SNMP or command line interface access.

◆ The device type number is used in place of the model for both SNMP and Terminal access, as some models only report "-" for the model number in the results of show system.

◆ Some hardware detail lines show partial part numbers in the command line interface which are reported verbatim.

◆ A test using 10000 devices and running OS version 9.2.0.8 have exhibited the following behavior:

• The device does not appear to support system show at operator level access. In this case, no configuration will be shown.

• IP-related details do not appear to be available from SNMP.


14

Checkpoint Devices


◆ Checkpoint Firewall-1 ................................................................................................. 110

Checkpoint Devices 109

Checkpoint Devices

Checkpoint Firewall-1

Device Type

Specific Model(s)


Enabled By Default

Other Unique Information

Configuration Files



User Interface


Password Management



Cut-Through Access

Firewall Quick Commands







◆ OID 1.3.6.1.4.1.2620.1.1.10.0

• FireWall-1

Firewall

Firewall-1

http://www.checkpoint.com

Yes

Can run on NG with Application Intelligence R55W or stand-alone. Unix like operating system.

Multiple Text, Multiple/Complex

Command, Config, Privilege Mode Termlet, Termlet Merge

SSH/SCP, SSH Only

Command Line

SNMP

In-Band, SNMP

Terminal, SSH, FTP, SCP

SSH, FTP, SCP

Terminal

Test Credentials, Setup Diagnostic, View Diagnostic Setup, Ping, Traceroute, View Interfaces, View ARP, View Routes, Setup NAT, View NAT Setup, View Processor CPU, View Network Management Events, View Interface Counters

For SNMP: Hardware Inventory, Memory, Interfaces, Serial Number


http://www.checkpoint.com

Checkpoint Devices



◆ Use the expert command to get to a Unix prompt. Requires the super user password. All files are transferred using FTP or SCP.

◆ The files listed in the Multi-Config Files section for this device are pushed using a combination of SSH and SCP commands.



◆ Use the expert command to get to a Unix prompt. Requires the super user password. All files are transferred back using FTP or SCP.

◆ Use the Unix file commands to put the files back into place.

◆ The files listed in the Multi-Config Files section for this device are retrieved using a combination of SSH and SCP commands.

Multi-config files


Multi-config files Push/pull Pull only Type Editable Required

$base_dir/conf/netso.C Text Yes

$base_dir/conf/objects.C Text Yes Yes

$base_dir/conf/InternalCA.C Text Yes Yes

$base_dir/conf/snmp.C Text Yes Yes

$base_dir/conf/SDS_objects.C Text Yes

$base_dir/conf/classes.C Text Yes Yes

$base_dir/conf/lea_server_unification_scheme.C Text Yes Yes

$base_dir/conf/log_unification_scheme.C Text Yes Yes

$base_dir/conf/newobjects.C Text Yes Yes

$base_dir/conf/refs.C Text Yes Yes

$base_dir/conf/tables.C Text Yes Yes

$base_dir/conf/userdef.C Text Yes Yes

$base_dir/conf/cpha.conf Text Yes Yes

Checkpoint Firewall-1 111

Checkpoint Devices

$base_dir/conf/cphaprob.conf Text Yes Yes

$base_dir/conf/cpmap_config.conf Text Yes

$base_dir/conf/cpmap_opsec.conf Text Yes

$base_dir/conf/cpmap_rulebase.conf Text Yes

$base_dir/conf/cp.lf Text Yes Yes

$base_dir/conf/product.conf Text Yes

$base_dir/conf/fwauthd.conf Text Yes Yes

$base_dir/conf/fwopsec.conf Text Yes Yes

$base_dir/conf/slapd.conf Text Yes

$base_dir/conf/smtp.conf Text Yes Yes

$base_dir/conf/omi.conf Text Yes

$base_dir/conf/thresholds.conf Text Yes

$base_dir/conf/fwmusers Text Yes Yes

$base_dir/conf/gui-clients Text Yes Yes

$base_dir/conf/external.if Text Yes

$base_dir/conf/cp.license Text Yes

$base_dir/conf/masters Text Yes

$base_dir/conf/*.W Text Yes Yes

/config/active Text Yes

$base_dir/state/* Binary

Yes

$base_dir/conf/serverkeys.* Binary

$base_dir/database/* Binary

Yes

$base_dir/conf/fwauth.NDB Binary

Yes

$base_dir/conf/fwauth.keys Binary

$base_dir/conf/rulebases.fws Binary

$base_dir/conf/inst.conf Text Yes



Checkpoint Devices

Device data



Known issues


3.6 Regression - Credentials (Account, Privilege and SNMP) change failed

◆ When changing Checkpoint Credentials do not change the enable password from the device communications settings. This may result in the login password being modified and subsequently, you will be denied access to the system.

Changing Checkpoint Credentials

◆ When changing Checkpoint credentials do not schedule a change of the enable password from the device communications settings. This may result in the login password being modified and subsequent denial of access to the system.

$base_dir/conf/sic_policy.conf Text Yes

$base_dir/database/cprid/cprid_keys/* Binary

$base_dir/database/cprid/cprid_util_keys/* Binary


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Checkpoint Firewall-1 113

Checkpoint Devices


15

Ciena Devices


◆ Ciena Router ................................................................................................................. 116

Ciena Devices 115

Ciena Devices

Ciena Router

Device Type

Specific Model(s)


Operating System

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands



◆ Configuration Capture (revision config, FRU list)




◆ Vendor is Ciena in response to 'show system'

◆ Serial number is retrievable

◆ sysObjectId

• Maps to model using CienaRouter/CienaRouterModels.xml

• Contains 1.3.6.1.4.1.7737.5.2.2.6

Router

4200

ciena.com

6.2.0

ASCII/Binary

Termlet Merge, User Mode Termlet, Command, Configlet, Config


Command line

Non-SNMP

In-Band

Telnet/FTP, SSH/FTP

Telnet/FTP, SSH/FTP

Terminal

Standard

Identity, System Properties, Interfaces, Inventory


Ciena Devices



◆ Change log:

• show log dbchg

◆ Device backup

• configure terminal

• maint-state enter

• save

• maint-state exit

• copy configuration to address ipAddress remoteFilePath user ftp overwrite yes



◆ Device restore:

• copy configuration from address ipAddress remoteFilePath user ftp

Multi-config files



Device data


running

change log


ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No

Ciena Router 117

Ciena Devices

Known issues


Ciena Router

◆ The enable priv and enable admin passwords must be set to the same value to manage the device.

◆ Only SNMP credential rolls are supported.

◆ On configuration pushes (restore), the push may fail to get a verification message due to the device responding with (Destination already exists). The cause for this is not yet identified.

◆ Change logs show a revision on every pull due to entering configuration mode in order to put the device into maintenance mode to save prior to transfer.

◆ In order to generate a configuration backup, the device is briefly placed into maintenance mode; the effects of this on the managed device have not been investigated.

◆ An FTP transfer service must be configured for this device. See “Configuring FTP Transfer Service” on page 32 for more information.



Static Routes No



VLANs No



16

Cisco Devices


◆ Cisco Aironet AP VXWorks ....................................................................................... 120◆ Cisco PIX Firewall ....................................................................................................... 122◆ Cisco VPN 3000 ........................................................................................................... 128◆ Cisco Aironet AP Package ......................................................................................... 131◆ Cisco Aironet Bridge Package ................................................................................... 135◆ Cisco Application Control Engine ............................................................................ 138◆ Cisco BPX...................................................................................................................... 141◆ Cisco CatOS Switch Package ..................................................................................... 145◆ Cisco Content Appliance............................................................................................ 152◆ Cisco Content Services Switch .................................................................................. 156◆ Cisco Router ................................................................................................................. 159◆ Cisco IOS Switch Package.......................................................................................... 167◆ Cisco IOS XR ................................................................................................................ 174◆ Cisco Intrusion Prevention System (IPS) ................................................................. 178◆ Cisco Lightstream Package ........................................................................................ 181◆ Cisco Nexus.................................................................................................................. 184◆ Cisco MGX.................................................................................................................... 189◆ Cisco MDS .................................................................................................................... 194◆ Cisco Wide Area Application Services (WAAS) ..................................................... 197◆ Cisco Wireless LAN Controller ................................................................................. 200

Cisco Devices 119

Cisco Devices

Cisco Aironet AP VXWorks

Device Type

Specific Model(s)


Enabled By Default

Configuration Files


User Interface



Cut-Through Access






◆ sysDescr

• Cisco AP340

◆ sysObjectID

• .9.1.379 or .9.1.474


◆ Term:

• GET /cgi-bin/cgiConfigDownloadAll?detailLevel=40 HTTP/1.1\n" ……

Note: Termlets are not supported on Cisco Aironet AP VXWorks.

Cisco Aironet AP VXWorks

340 VXWork, 1200 AP

-

Yes

Single Text

HTTP/TFTP

Command Line

SNMP

Terminal

Terminal



Cisco Devices

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Cisco Aironet AP VXWorks 121

Cisco Devices

Cisco PIX Firewall

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access









Cisco Pix Firewall

501, 506, 506E, 515, 515E, 520, 525, 515Esc, 515Esy, 515sc, 515sy, 525sc, 525sy, 535, 535sc, 535sy, FWSM-6000, ASA5510, ASA5510-K8, ASA5520, ASA5520sc, ASA5520sy ASA5540, ASA5540sc, ASA5540sy

http://www.cisco.com

Yes

Syslog, SNMP Traps

ASCII


SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, Non-SNMP


SNMP (not available for FWSM and ASA models), Terminal

Account, Privilege, SNMPv1/2

Operating systems for 501 models: 6.11, 6.22, 6.24, 6.35Operating systems for all other models: 6.3, 7.0, 7.2, 8.0

Terminal, SSH, TFTP

Terminal, SSH

Terminal

TFTP

SetTrapDest, Test Credentials, Setup Diagnostics, View Diagnostics Setup, Setup NAT, View NAT Setup

For SNMP: Memory, InterfacesFor Non-SNMP: Memory, Interfaces, Serial Number, OS Version, Inventory


Cisco Devices



◆ For SNMP (not available for FWSM and ASA models):

• sysObjectID value contains 1.3.6.1.4.1.9

• sysDescr value contains PIX

◆ For Non-SNMP:

• show version response contains PIX, FWSM, or Adaptive Security Appliance



For devices in multi-context mode, both admin and system (running and startup) configurations are pulled if discovery using non-SNMP is successful. Other contexts discovered at their respective addresses are limited to single running and startup configurations.

◆ For Telnet and SSH:

• running: show run (show config if show run fails)

• startup: show config (show start if show config fails)

◆ For Telnet/TFTP and SSH/TFTP:

• running: write net ipAddress filename

• startup: same approach as startup for Telnet and SSH above


◆ PIX only supports push using Terminal. Enter enable mode, enter configuration mode, and send one configuration line at a time.

Device commandsFollowing are the device command sets you must enable to allow VoyenceControl to manage this device class.


show checksum

show version

show pager

show config

show start

show run

show snmp contact

Cisco PIX Firewall 123

Cisco Devices

show snmp location

show interface | include is

show interface ifName

show memory

show memory summary

show flash

show ip

show arp

show priv

enable

conf term

write mem

write net ip-addr ...

no pager

page 0

term length 0

exit

snmp-server enable traps

snmp-server host ip-addr

logging history notifications

logging on

enable

disable


aaa authentication telnet console LOCAL

aaa authentication ssh console LOCAL

aaa authentication serial console LOCAL

no username "oldName"

username "userName" password "password"

no aaa authentication telnet console LOCAL

no aaa authentication ssh console LOCAL

no aaa authentication serial console LOCAL

passwd "password"

no enable password "newPrivPass" level "level"

enable password "newPrivPass" level

snmp-server community "newSnmpROCommunity"

snmp-server host inside "ip-addr" community "community-string"


Cisco Devices

disable

enable "level"

◆ FWSM Commands (Pix 7.0)

show host

show mode

show context

change context system

change context "contextName"

◆ OS Upgrade

copy tftp flash

Multi-config files




runningAdmin

runningSystem

startupAdmin

startupSystem


ARP Table Yes

Access Control Lists Yes

CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No



Cisco Devices

Known issuesThe following information details existing device issues that have been discovered within other releases. In most cases, a resolution is included to address the issue.

SNMP Credential Change for PIX 515 (version 7.0)

◆ When rolling Credentials (for example, using the application's System Administration -> Networks -> Roll feature), only the credential entry relating to the application's IP address changes.


◆ This device class does not currently support listing flash contents; the user must ensure sufficient space exists before scheduling the upgrade. Upgrading from version 6.x to later versions is not supported by this device class because memory and flash requirements cannot be verified by the driver.

Physical Hardware

◆ Inventory is displayed for supported devices discovered using Non-SNMP protocols for single context devices and the admin context of multi-context devices.

◆ The system context does not support hardware inventory.

Autodiscovery of spared units

◆ When discovering non-admin contexts operating in a spared configuration, the newly discovered non-admin context will replace the previous version. This is due to the non-unique combination of hostname/context, IP address, and serial number for this equipment.

◆ To avoid duplicate devices in the UI, devices in multi-context mode currently use hostname for the serial number to maintain backward-compatibility with previously discovered units for VoyenceControl upgrade scenarios.

Autodiscovery of Multiple Context

◆ Devices configured to contain multiple virtual firewall context, such as an ASA or PIX 7, must be discovered using terminal credentials. There is not enough unique information from the SNMP agent to accurately determine a unique chassis on these devices.

Routes Yes



VLANs No



Cisco Devices

Cisco PIX - SNMP Discovery

◆ SNMP discovery is not available for FWSM and ASA models.

Device Naming

◆ For devices operating in multiple context mode, the device name is constructed as hostname/context.

• Hostname is initially taken from the show host response.

• Context is taken from the show context response, active context detail is listed on the line ending in *.

• When these values are identical, the hardware name shown in the show version response is used for the hostname. For example, ciscoasa up 4 days 3 hours.

Configuration Management

◆ runningSystem and startupSystem configuration files can only be pulled for the admin-equivalent context. All other contexts will pull only runningAdmin and startupAdmin configurations.


Cisco Devices

Cisco VPN 3000

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access








◆ sysObjectID

• contains 1.3.6.1.4.1.1.3076 or 1.3.6.1.4.1.3076

◆ sysDescr

• contains VPN

◆ Sys Services Layer

• 3, 4, and 7

VPN concentrator

3000

http://www.cisco.com/

Yes

Syslog, SNMP Traps

Single Text

Command, Config

SSH/SCP, SSH/FTP, Telnet/FTP, SSH Only, Telnet Only, Non-SNMP

Command Line

SNMP

In-Band, SNMP

4.1.7.G, 4.7.2.L , 4.7.2.N

FTP, SCP

FTP, SCP

Terminal

For SNMP: Hardware Inventory, VLANs, Memory, Interfaces, Serial Number, Model, OS Version


Cisco Devices



◆ A terminal session is used to navigate the following menu

• Administration

• File Management

• Export XML File

◆ Exported filename is CFGXML

◆ FTP or SCP used to pull file CFGXML from device


◆ SCP or FTP the file CFGXML to the device

◆ A terminal session is used to navigate the following menu

• Administration

• File Management

• Import XML File (name CFGXML)

• Save changes to the configuration file

Multi-config files



Device data


running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Cisco VPN 3000 129

Cisco Devices

Known issues


Cisco VPN 3000

◆ For the listed software versions, the VPN Concentrator can fail pulls and pushes if an FTP session to the device is changed to a different directory than the default / directory.

• Push/pull failures due to the above problem can be verified with manual FTP sessions to the device being unable to list or transfer files. The pwd command reports the correct directory.

• The above failures will show up as failed pull or push jobs in the Scheduler, with a failed credentials error. The credentials will succeed for a Test Credentials job.

• To correct this condition, access the device with an FTP client, login, and issue cd /. After logging out, retry the failed operation.

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No



Cisco Devices

Cisco Aironet AP Package

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access



Features available







◆ SysObjectIDs

• 1.3.6.1.4.1.9.1.507 and 1.3.6.1.4.1.9.1.565

• 1.3.6.1.4.1.9.1.525

◆ SysDescription Contains IOS

Cisco Aironet Access Point

1100, 1130, 1200, 1210, 1240, 1310, 350IOS, AIR-AP1230A-A-K9, AP1200

http://www.cisco.com/en/US/products/hw/wireless/ps430/index.html

Yes

Syslog, SNMP Traps

Single Text

Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP, Non-SNMP

IOS, SNMP Only

SNMP, Terminal

AAA, In-Band, SNMP

12.2(13)JA, 12.3(8)JEC3

Terminal, TFTP

Terminal, TFTP

Terminal

TFTP


Cisco Aironet AP Package 131

Cisco Devices

◆ SysServices Layer 2 Only

◆ Valid Cisco Rom ID

• .1.3.6.1.4.1.9.2.1.1.0

◆ Non-SNMP discovery

• must contain Cisco IOS or Internetwork Operating System in the results of show version

• the show vtp counters command must execute

• Cisco Enterprise ID must match models list and not be in the list of 164, 107, 533



◆ For Terminal:

• show start for startup configuration

• show run for running configuration

• set oid .1.3.6.1.4.1.9.2.1.55.IP to the TFTP server's filename

• Fall back to Telnet/TFTP for startup configuration

• For Telnet/TFTP use the following commands:

– copy running-config tftp– copy startup-config tftp

◆ For SNMP/TFTP:

• Devices using OLD-CISCO-SYSTEM-MIB (running configuration only):

– .1.3.6.1.4.1.9.2.1.55.ipAdress -> remoteFilename• Devices using CISCO-CONFIG-COPY-MIB (id is a unique integer):

– .1.3.6.1.4.1.9.9.96.1.1.1.1.2.id -> 1 (TFTP)– .1.3.6.1.4.1.9.9.96.1.1.1.1.3.id -> 1 (network file)– .1.3.6.1.4.1.9.9.96.1.1.1.1.4.id -> type (4: running, 3: startup)– .1.3.6.1.4.1.9.9.96.1.1.1.1.5.id -> serverIpAddress– .1.3.6.1.4.1.9.9.96.1.1.1.114.id -> 1 (start transfer)

• SNMP for the running configuration only




◆ From the console prompts, the device is brought to the enable mode using enable 15 then to the configure mode using conf t after which the configuration is entered line-by-line with checks for banners and for Invalid Input.

◆ If a banner is entered using banner motd X, the termination banner character X is stored, and there are no prompt checks until the final banner line is entered or a new prompt is detected.

◆ For SNMP/TFTP:


Cisco Devices




◆ Commit config:

• SNMP:

– .1.3.6.1.4.1.9.2.1.54.0 -> 1◆ To copy run to start from command line

• Copy running-config startup-config

Multi-config files



Device data


running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes

Access Control Lists Match Counts Yes

OSPF Settings No


Routes Yes

Cisco Aironet AP Package 133

Cisco Devices

Known issues


Cisco Aironet AP

◆ If the device supports CISCO-CONFIG-COPY-MIB, then SNMP/TFTP can be used to pull and push both the running and startup configurations, otherwise only running configurations are supported.



VLANs No



Cisco Devices

Cisco Aironet Bridge Package

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access








◆ SysObjectIDs

• 1.3.6.1.4.1.9.1.533

◆ SysDescription Contains IOS


Cisco Aironet Wireless Bridge

1300, 1410

http://www.cisco.com/en/US/products/hw/wireless/ps430/index.html

Yes

Syslog, SNMP Traps

Single Text

Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP

IOS, SNMP Only

SNMP

AAA, In-Band, SNMP

Terminal, TFTP

Terminal, TFTP

Terminal


Cisco Aironet Bridge Package 135

Cisco Devices



◆ show start for startup configuration

◆ show run for running configuration

◆ SNMP for the running configuration only


◆ Fall back to Telnet/TFTP for startup configuration

◆ For Telnet/TFTP use the following command:





◆ From the console prompts, the device is brought to the enable mode using enable 1 then to the configure mode using conf t after which the configuration is entered line-by-line with checks for banners and for Invalid Input.


◆ SNMP for the running configuration only:

• .1.3.6.1.4.1.9.2.1.50.IP = filename on tftp server

• .1.3.6.1.4.1.9.2.1.54.0 = 1 to copy run to start

◆ To copy run to start from command line:




running --

startup --


Cisco Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Cisco Aironet Bridge Package 137

Cisco Devices

Cisco Application Control Engine

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available







◆ Model, Serial Number, MAC and OS version using SNMP or command line interface.

◆ Filesystem and Memory using command line interface.

◆ Interface table using SNMP or command line interface.

Cisco Application Control Engine

ACE20-MOD-K9

www.cisco.com

-

Syslog, SNMP Traps

running, startup




SNMP, Terminal

In-Band

3.0



Terminal

View Routes, View ARP, Ping, Resync, Clear counters, Show diag, sh ip interface brief

Hardware Inventory, Memory, Interfaces, Serial Number


Cisco Devices



◆ For TFTP protocols:

• copy running-config tftp://[serverip]/[filename]

• copy startup-config tftp://[serverip]/[filename]

◆ For non-TFTP protocols:

• A command line interface session is started and the output of either show run or show start is captured.



◆ For TFTP protocols:

• copy tftp://[serverip]/[filename] running-config

• copy tftp://[serverip]/[filename] startup-config

◆ For non-TFTP protocols:

• A command line interface session is started, config mode is entered, and the configuration is entered line-by-line.

Multi-config files




Running --

Startup --


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Cisco Application Control Engine 139

Cisco Devices

Known issues


Cisco ACE

◆ Pushing directly to the startup config using SSH only or Telnet only is not supported. To push to startup, push to the running config and then copy runnng to startup.

Virtual Contexts

◆ The Administrative context configuration is the only configuration pulled and stored from the ACE. Virtual context created on the Cisco ACE are not stored for baselines or history.

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes



Cisco Devices

Cisco BPX

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface




Cut-Through Access


Quick Commands


Features available◆ Discover/Identify using SNMP and Terminal (Auto-Discovery, Identify, Appear

in Product)

◆ Incremental Updates (Configlet or Device Commands)

◆ Hardware and Interface Information

◆ Backup to Archive File

◆ SSH and Telnet Support


◆ Quick Commands


◆ Both SNMP and Telnet access are required to properly discover and manage the BPX.

◆ Name of device is taken from SNMP sysName.

◆ Model name is determined by the SNMP system description set by the vendor.

• Wide Area Switch = BPX 8620

Multi-Service Switch

BPX 8620

Cisco Provided

No

Binary capture to file system only

Binary, Command-Line Interface

Telnet


SNMP or Telnet

Binary file set by means of TFTP

Configuration by means of Configlet only

Terminal

Not currently supported

Test Credentials, Enable Automatic Backups, Disable Automatic Backups, Display Cards, Display Card, Display Port, Display Ports, Display Connection, Display Connections, Display Lines, Setup NAT, View NAT Setup

Hardware provided using Terminal commands

Cisco BPX 141

Cisco Devices

◆ OS Version is determined by dspcd 7 Ram Id Field.

◆ Chassis serial number is reported as the Serial Number reported by dspcd 7.


◆ savecnf <ID> <Node> * <IP> t /

Where <ID> is the backup id, Node is the name of the node, and IP is the IP address of the VoyenceControl device server.

◆ A saved configuration file set is saved in the /tftpboot directory of the device server. This configuration set contains three files needed to restore the device configuration state. The ID of the save determines the name of the subdirectory containing the saved files. The ID is VC<DDD><YY> where DDD represents the 3 digit day of the year and YY is the two digit year. For example the ID for a backup on March 2nd 2008 would be VC06208. The subdirectory containing the configuration files for restoration is named <ID>_Cfgdir as in /tftpboot/VC06208_Cfgdir for a backup on March 2nd 2008.

For Example:

-bash-3.00# ls -l /tftpboot/

drwxr-x--- 2 nobody root 4096 Mar 3 22:59 VC06308_Cfgdir

-bash-3.00# ls -l /tftpboot/VC06308_Cfgdir/

total 4984

-rw-rw-rw- 1 root root 256 Mar 3 20:14 D1.ALX1_BPX.000

-rw-rw-rw- 1 root root 2536663 Mar 3 20:35 D1.ALX1_BPX.001

-rw-rw-rw- 1 root root 800 Mar 3 20:14 D1.ALX1_BPX.cfg

-rw-rw-rw- 1 root root 256 Mar 3 22:59 D1.Madi_BPX.000

-rw-rw-rw- 1 root root 2536663 Mar 3 23:21 D1.Madi_BPX.001

-rw-rw-rw- 1 root root 800 Mar 3 22:59 D1.Madi_BPX.cfg

Note: Automatic backups will be disabled after every configuration capture.

◆ You can save a configuration if both of the following are true:

• No save or restore process is currently running.

• No configuration changes are in progress.

Configuration captures for the device have an enable and disable feature. The quick commands Disable Automatic Backups and Enable Automatic Backups are provided to prevent VoyenceControl from automatically issuing the saveallcnf after every device change. It is advisable to disable automatic backups unless the device is currently not provisioned.


Cisco Devices



◆ loadcnf <ID> <Node> * <IP> t /

Where <ID> is the backup id, Node is the name of the node, and IP is the IP address of the VoyenceControl device server.

Device commands


◆ Quick Commands

The following quick commands are provided to allow quick diagnostic commands on the device from the workspace right-click menus. Where a card number parameter is required the quick command will use the cc command to redirect the session to the appropriate card before executing the command.

• Test Credentials - Validates and tests read-only community string and login management credentials.

• Enable Automatic Backups - Enables the driver for saveallcnf operation.

• Disable Automatic Backups - Disables the driver for saveallcnf operation.

• Display Cards - Runs the dspcds command.

• Display Card - Runs the dspcd command against the given card number.

– Parameter Card Number of type Integer.• Display Port - Runs the dspport command, optionally supplying the slot

number.

– Parameter Slot.Port (optional) of type String.• Display Ports - Runs the dspports command, optionally supplying the slot

number.

– Parameter Slot.Port (optional) of type String.• Display Connection - Runs the dspcon command, optionall supplying the

channel and DLCI number.

– Channel (slot.port or slot.channel) of type String.– DLCI of type String.

• Display Connections - Runs the dspcons command.

• Display Lines - Runs dsplns which lists all the lines configured.

• Setup NAT - Configures the NAT IP address of the individual device.

– Parameter Device Server NAT IP of type IpAddress.• View NAT Setup - Displays the NAT IP configuration for the individual

device.

Cisco BPX 143

Cisco Devices

Known issues


Cisco BPX - Restore Causes Device Reset and Loss of Service

◆ Issue: Restoring the device may cause a device reset and loss of service.

◆ Resolution: This feature has not been implemented and should not be done until tested against a non-production system. The device server contains the necessary files to manually restore the device.

Cisco BPX - SNMP MIB-II shows only two interfaces

◆ Issue: BPX SNMP MIB-II shows only two interfaces.

◆ Resolution: The device SNMP agent only reports two interfaces. This is a limitation of the network device.

Cisco BPX - No SSH support

◆ Issue: No SSH support for Cisco BPX.

◆ Resolution: The Cisco BPX does not support SSH.

Cisco BPX - Screen Painting and Re-drawing Issues occur when using Cut-Through

◆ Issue: The BPX in a split screen VT100 interface. Screen painting and redrawing issues may occur when using Cut-Through.

◆ Resolution: The clrscrn command can be used to re-draw and refresh any screen issues. In addition, terminal commands will show multiple snapshots of the screen progression. This information is shown with dividers to aid in distinguishing the screen updates and associated commands.


Cisco Devices

Cisco CatOS Switch Package

Device Type Cisco CatOS Switch

Specific Model(s) CAT2900XL-ATM, CAT2940, CAT2950, CAT2950LRE, CAT2955, CAT2960, CAT2970, CAT2970,CAT3550, CAT3550, CAT3560, CAT3560E, CAT3750, CAT3750, CAT3750E, CAT3750-METRO,CAT4000-AGM, CAT4000-SUP4, CAT4224, CAT4500-AGM, CAT4500-AGM, CAT4500E-SUP6E, CAT4500-SUP2-PLUS, CAT4500-SUP2-PLUS, CAT4500-SUP2-PLUS-10GE, CAT4500-SUP2-PLUS-TS, CAT4500-SUP3, CAT4500-SUP3, CAT4500-SUP4, CAT4500-SUP4, CAT4500-SUP5, CAT4500-SUP5-10GE, CAT4900M, CAT4948, CAT4948-10GE,CAT5000-ATM, CAT5000-RSFC, CAT5000-RSM, CAT5000-RSM,CAT6000-ATM, CAT6000-CMM, CAT6000-MSFC, CAT6000-MSFC2, CAT6000-MSFC2, CAT6000-MSFC2A, CAT6000-MSFC3, CAT6000-MWAM, CAT6000-SUP1/MSFC1, CAT6000-SUP1/MSFC2, CAT6000-SUP2/MSFC2, CAT6000-SUP2/MSFC2, CAT6000-SUP32/MSFC2A, CAT6000-SUP32/PISA, CAT6000-SUP720/MSFC3, CAT6000-VS-S720-10G/MSFC3, CATEXPRESS500, CATEXPRESS520,WS-C2948G-GE-TX, WS-C2948G

Documentation/Information http://www.cisco.com/

Enabled By Default Yes

Configuration Change Notification (Events) Syslog, SNMP Traps

Configuration Files Single Text

Configuration Content Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

Configuration ProtocolsSSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP

User Interface IOS, SNMP Only

Discovery/Identify Methods SNMP

Password Management AAA, Out-of-Band, Enable, In-Band, SNMP

Operating System OS Upgrade

Configuration Capture Terminal, TFTP

Configuration Deploy Terminal, TFTP

Cut-Through Access Terminal

Cisco CatOS Switch Package 145

Cisco Devices

Features available








◆ For SNMP:

• SysDescr must contain Catalyst and Cisco Systems WS-C5

• SysServices value shows only Layer 2 support

◆ For Terminal (Non-CatOS 1900 Devices):

• Disable paging using set length 0

• show version response contains Cisco Systems, but not IOS identifiers Cisco IOS or Internetwork Operating System

• Model information extracted from show version, response indicates a CatOS switch


◆ For Terminal:

• show config all, for configuration

• show run, if show config all fails

◆ For SNMP (devices supporting CISCO-STACK-MIB, running configuration only):

• .1.3.6.1.4.1.9.5.1.5.1.0 -> serverIpAddress

• .1.3.6.1.4.1.9.5.1.5.2.0 -> remoteFilename

• .1.3.6.1.4.1.9.5.1.5.3.0 -> id (integer representing Supervisor module)

• .1.3.6.1.4.1.9.5.1.5.4.0 -> 3 (pull config from device)

◆ For Telnet/TFTP:

• write IP file all

Operating System Management Telnet/TFTP, Telnet/FTP, SSH/SCP

Switch Quick Commands View Trunk, View Neighbors, View VLAN, Ping, TraceRoute, Test Credentials, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup

Hardware Information For SNMP: Hardware Inventory, Memory, Interfaces, Serial NumberFor Non-SNMP: Hardware Inventory, Memory, Interfaces, Serial Number


Cisco Devices



◆ For Terminal:

• From the console prompts, the device is brought to the enable mode using enable then to the configure mode using conf t after which the configuration is entered line-by-line with checks for banners and for invalid input.

• If a banner is entered using banner motd X, the termination banner character X is stored, and there are no prompt checks until the final banner line is entered or a new prompt is detected.

◆ For SNMP (Devices supporting CISCO-STACK-MIB, running configuration only):

• .1.3.6.1.4.1.9.5.1.5.1.0 -> serverIpAddress

• .1.3.6.1.4.1.9.5.1.5.2.0 -> remoteFilename

• .1.3.6.1.4.1.9.5.1.5.3.0 -> id (integer representing Supervisor module)

• .1.3.6.1.4.1.9.5.1.5.4.0 -> 2 (push config to device)

◆ For Term/TFTP/SNMP:

• copy tftp config IP file

Device commands



set length 0

term length 0

show boot

show run

show config

term length 0

show version

copy running-config startup-config

enable

disable

conf term

clear boot auto-config

set boot auto-config bootflash:

show ip

show snmp group

show snmp contact

show snmp hostname


Cisco Devices

show snmp location

show snmp ifalias

show cdp neighbors detail

show port status

show interfaces

write memory

write "ip-addr"

exit

tftp server "ip-addr"

copy tftp: ...


show module "moduleNum"

dir "partition"

reset

reset "moduleNum"

clear boot system all

set boot system flash ...

set boot config-register 0x2102

boot bootldr "imageName"

boot system flash "imageName"

copy ...

session 15

session 16


show snmp access

show snmp group

set password

enable secret 0 "newPrivPw"

no enable secret

enable password level 15

no enable password level 15

set enablepass

no snmp-server community "commString"

snmp-server community "commString"

set snmp community read-only

set snmp community read-write

set snmp user ...


Cisco Devices

set snmp view "viewName" ...

set snmp group "groupName" ...

set snmp access ...

clear snmp access ...

clear snmp user ...

◆ File Commands

copy tftp ...

copy scp ...

copy ftp ...

verify ...

verify ?

delete ...

squeeze ...

dir "partition"

dir bootflash:

dir slot0:

dir slot1:

show flash

◆ Quick Commands

ping "ip-addr"

traceroute "ip-addr"

show vlan

show trunk A

show trunk B

show trunk

show CDP neighbors detail

show cam "mac-addr"



running


Cisco Devices

Device data



Known issues


Cisco Catalyst OS Switches - Auto Discovery SNMP

◆ Issue: Auto Discovery with SNMP Credentials and Accounts, and Privilege Passwords may hang if the devices do not have names. For example: no name set on CAT OS Switches. Note that this may be prevalent in the CAT OS devices, due to the no name default setting on CAT OS Switches.

◆ Resolution: Set the Name on the device. On CAT OS, use the set system name command in Enable mode.

Cisco Catalyst 1900 - Serial Numbers not Displayed

◆ Serial numbers for the CAT OS 1900 devices are not being displayed.

Catalyst OS Switch 1900

◆ After a hardware pull, using either SNMP or non-SNMP mechanisms, the Non-Volatile Memory information will not display. The device does not support the display of Non-Volatile Memory. This is a device limitation. Other memory information can be accessed using the SNMP mechanism.

ARP Table Yes


CAM Table Yes


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes


Cisco Devices

Cisco Catalyst 4000 Series

◆ The OS version for 12.2(18)EW4 for the CAT 4000 series switch displays UNKNOWN for the feature set in the application.

The device responds with UNKNOWN during an SNMP-GET.

• For example:

SNMP-GET(.1.3.6.1.4.1.9.9.25.1.1.1.2.4)->CW_FEATURE$UNKNOWN$


Cisco Devices

Cisco Content Appliance

Device Type

Specific Model(s)

Operating System


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


Features available◆ Discover/Identify (Auto Discovery, Identify, Appears in Product)





507, 511, 512, 560, 565, 566, 590, 611, 612, 674, 7305, 7320, 7341

5.4.3.17


No

Single Text

Quick Commands, Termlet Merge, User Mode Termlet, Command, Configlet, Config

Telnet, SSH, SSH/TFTP, Telnet/TFTP


SNMP, Terminal

Account, Privilege Mode, SNMPv1/2



Telnet, SSH

View Interfaces, View ARP, Ping, TraceRoute, Resync, View CDP Neighbors, Resync,

Memory, Interfaces, Serial Number, Model, OS Version, Inventory


Cisco Devices



◆ For SNMP:

• sysDescr value must contain Application Content Networking

• Model name is obtained from the following OIDs (in order):

– 1.3.6.1.4.1.9.9.368.1.34.3.0– 1.3.6.1.4.1.2467.1.34.3.0

• Part number column of the CISCO-ENTITY-ASSET-MIB for the chassis entry

◆ For Terminal:

• Show version output must contain Application Content Networking

• sysObjectId value is mapped from the model name, which is parsed from the output of show hardware for a non-blank field, in the following order:

– ModelNum (raw)– ModelNum, where (text) optionally precedes the model name– ExtModel



◆ show startup-config for startup configuration

◆ show running-config for running configuration


• copy startup-config tftp serverAddress localFilename

• copy running-config tftp serverAddress localFilename


◆ From the console prompts, the device is brought to the enable mode using enable. Next, more is turned off using the no terminal more or terminal length 0 command. The device is placed into configure mode using configure terminal after which the configuration is entered line-by-line.

◆ For Telnet/TFTP user the following command:

• copy tftp <serverAddress> < localFilename> startup-config



Multi-config files


Cisco Content Appliance 153

Cisco Devices


running

startup


Cisco Devices

Device data





◆ Privilege level access is controlled by the administrator account password. The administrator account cannot be rolled since it is used for the privilege password.

◆ Although users of level 0 or 15 can be created, use of a level 15 account will not prompt for an enable password even when dropping back to user level.

ARP Table Yes


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes Yes



VLANs No

Cisco Content Appliance 155

Cisco Devices

Cisco Content Services Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







◆ sysDescription

• Search for Content Switch or Application and Content Networking

Cisco Content Services Switch

11050, 11501, 11503, 11506


Yes

Single Text



IOS like

SNMP

In-Band, SNMP

OS Upgrade

Terminal, SSH, TFTP

Terminal, SSH, TFTP

Terminal

View Interfaces, View ARP, Ping, TraceRoute, Resync, View Interfaces, View CDP Neighbors, Resync,

For SNMP: Memory, Interfaces, Serial Number, Model, OS Version


Cisco Devices





◆ For telnet/tftp use the following command:

• copy startup-config tftp SERVERIPADDR localFile

• copy running-config tftp SERVERIPADDR localFile


◆ From the console prompts, the device is brought to the enable mode using enable 15. Next, more is turned off using no terminal more command. The device is placed into configure mode using conf t after which the configuration is entered line by line.


• copy tftp SERVERIPADDR localFile startup-config



Multi-config files



running

startup

Cisco Content Services Switch 157

Cisco Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Cisco Devices

Cisco Router

Device Type Cisco Router

Specific Model(s) 1700, 1711, 1801, 1801W, 1811, 1841, 1000, 1003, 1020, 1004, 1005, 1601, 1602, 1603, 1604, 1605, 12012, 12004, 12008, 1710, 1720, 1401, 1750, 1407, 1417, 12416, 12406, 12410, 1760,12404, 1721, 1751, 12010, 10400, 12016, 10720, 1701, 1720VPN, 1941/K9, 1941W-A/K9, 2000, 2500, 2102, 2202, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2801, 2821, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2516, 2610, 2611, 2612, 2613, 2620, 2621, 2501FRADFX, 2501LANFRADFX, 2502LANFRADFX, 2610M, 2611M, 2610XM, 2611XM, 2620XM, 2621XM, 2650XM, 2651XM, 2691, 2650, 2651, 2811, 2851, 2901/K9, 2911/K9, 2921/K9, 2951, 2951/K9, 3000, 3825, 3101, 3102, 3103, 3104, 3202, 3204, 3220, 3845, 3620, 3640, 3251, 3660, 3661Ac, 3661Dc, 3662Ac, 3662Dc, 3662AcCo, 3662DcCo, 3631, 3745, 3725, 3825, 3845, 3925, 3945,4000, 4500,6000, 6100, 6130, 6260, 6400, 6400Nrp, 677i, 674, 6400UAC,761, 762, 765, 766, 771, 772, 775, 776, 751, 752, 753, 7000, 7010, 7507, 7513, 7505, 4700, 7206, 7576, 7204, 7202, 7206VXR, 7204VXR, 7507z, 7513z, 7507mx, 7513mx, 7120At3, 7120Ae3, 7120Smi3, 7140Dualt3, 7140Duale3, 7140Dualat3, 7140Dualae3, 7140Dualmm3, 7750Mrp200, 7120Quadt1, 7120T3, 7120E3, 7140Octt1, 7140Dualfe, 7750Ssp80, 7609OSR, 7750, 7603, 7606, 7606-S, 7304, 7609, 7613,801, 802, 803, 804, 805, 828, 806, 811, 8110, 813, 8510, 8515, 826QuadV, 826, 827QuadV, 811, 827, 831837,827H, 836,AS5200, AS2509RJ, AS2511RJ, AS5300, AS5800, AS5400, AS5350,ASR 1000, ASR 1004AIR-AP1120B-A-K95,Cat6000,CS500,Catalyst6kMsfc2, Catalyst5kRsfc, Catalyst6kMsfc, Catalyst295024GDC, Catalyst3200, Catalyst3100, Catalyst1800, Catalyst1601, Catalyst3001,CE7305, CE510,DPA7630,GSS,IAD2430, IAD2431, IAD2432, IAD2431-8FXS, IAD2431-16FXS, IAD2431-1T1E1, IAD2432-24FXS,MC3810, Mc3810V3,ONS15540ESPx,Pro1003, Pro1004, Pro1005, Pro2500PCE, Pro2501, Pro2503, Pro2505, Pro2507, Pro2509, Pro2511, Pro2514, Pro2516, Pro2519, Pro4500, Pro751, Pro752, Pro753, Pro765, Pro766, Pro2520, Pro2522, Pro2524, Pro1601, Pro1602, Pro1603, Pro1604, Pro2502, Pro2504, Pro2506, Pro2508, Pro2510, Pro2512, Pro2513, Pro2515, Pro2517, Pro2518, Pro2523, Pro2525, Pro4700,SOHO77, SOHO76, SOHO97, SOHO91, SOHO96,UBR7246, UBR904, UBR7223, UBR924, UBR7246VXR,UBR912C, UBR912S, UBR914, UBR925, UBR10012, UBR7111, UBR7111E, UBR7114, UBR7114E, UBR905, WSX5302, WS-C6506-E




Syslog, SNMP Traps

Cisco Router 159

Cisco Devices

Features available








◆ For SNMP:


• sysDescription value contains IOS or Internetwork Operating System

• sysServices value indicates a Layer 3 device

• Cisco Rom ID (.1.3.6.1.4.1.9.2.1.1.0) is retrievable

◆ For Terminal:

• Device responds with an error to show vtp counters


Configuration ContentQuick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

Configuration ProtocolsSSH/SCP, SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP, Non-SNMP


Discovery/Identify Methods SNMP, Terminal


Operating System Boot Upgrade, OS UpgradeFor 1801W Models: 12.4(4)XC3, 12.4(24)T1For 1941/K9, 941W-A/K9, 2901/K9, 2911/K9, 2921/K9, 2951/K9, 3925, and 3945 Models: 12.4(24.6)For 2951 Models: 12.4(23.15.8), 12.4(24.6)

Configuration Capture SSH/Terminal, TFTP

Configuration Deploy SSH/Terminal, TFTP


Quick Commands View Routes, View ARP, Ping, TraceRoute, Resync, show frame-relay map, Clear counters, Show diag, Show process cpu, Show management event, sh ip interface brief

Hardware Information For SNMP: Hardware Inventory, VLANs, Memory, Interfaces, Serial NumberFor Non-SNMP: Memory, Interfaces, Serial Number, Hardware Inventory


Cisco Devices

• show version response contains Internetwork Operating System or Cisco IOS


◆ For Terminal:

• startup configuration : show start

• running configuration: show run

◆ For SNMP/TFTP:




◆ For Terminal/TFTP:




◆ From the console prompts, the device is put into configuration mode using enable 15 and configure terminal, and if successful, the configuration is issued line-by-line with checks for banner content and invalid input messages.


◆ SNMP/TFTP:

• Devices supporting OLD-CISCO-SYSTEM-MIB (running configuration only):

– .1.3.6.1.4.1.9.2.1.50.ipAddress -> remoteFilename• Devices supporting CISCO-CONFIG-COPY-MIB (id is a unique integer):

– .1.3.6.1.4.1.9.9.96.1.1.1.1.2.id -> 1 (TFTP)– .1.3.6.1.4.1.9.9.96.1.1.1.1.3.id -> type (4: running, 3: startup)– .1.3.6.1.4.1.9.9.96.1.1.1.1.4.id -> 1 (network file)– .1.3.6.1.4.1.9.9.96.1.1.1.1.5.id -> serverIpAddress– .1.3.6.1.4.1.9.9.96.1.1.1.114.id -> 1 (start transfer)

◆ Commit config:

• SNMP:

– .1.3.6.1.4.1.9.2.1.54.0 -> 1

Cisco Router 161

Cisco Devices

• Terminal:

– copy running-config startup-config

Device commands



show run

show start

show version

show config

show interfaces

configure term

terminal length 0

exit

write memory

reload

copy running-config tftp

copy startup-config tftp


copy tftp running-config

show file systems

show module

show vtp counters

show memory summary

dir

dir nvram:

dir flash:

squeeze flash:

show priv

show bootvar

show snmp contact

show snmp location



config-register 0x2102

show file systems

reload


Cisco Devices

hw-module module "moduleNum"

hw-module standby reload

archive download-sw /overwrite tftp:...

archive download-sw /safe tftp:...


show snmp group

snmp-server user ...

snmp-server engineID local

snmp-server context ...

snmp-server view ...

snmp-server group ...

snmp-server community ...

aaa new-model

no aaa new-model

line console 0

line vty 0

login

password

exit

line aux 0

no username ...

username "userName" privilege "userLevel" password "password"

no enable secret level

no enable password level

enable secret level

enable password level

◆ Quick Commands

ping "ip-addr"

show ip route

show arp

show ip interface brief

clear counters

show process cpu

show management event

copy run start


show vlan

Cisco Router 163

Cisco Devices

show logging

show cdp neighbors detail

show frame-relay map

show diag

Multi-config files



Device data



running

Startup

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs No


Cisco Devices

Known issues


Cisco IOS - Out-of-Sync

◆ When a SNMP/TFTP mechanism is used with only a Community String credential, the Running against Startup Configuration Out-of-Sync icon is not displayed. A valid Account and/or Privilege Password credential is needed to pull the Startup configuration on Cisco IOS devices.

Cisco IOS Update

◆ Issue: An issue exists where the OS image resided in bootflash, but was not the boot loader image. Additionally, the system image file was not in the show version command. In this case, the application could not free space in the target location. Manual intervention is needed to free space.

When there is insufficient space in the target location for an OS update on Cisco IOS devices with Class A file systems, the system attempts to free up additional space by deleting and squeezing the system image name displayed in the show version command.

◆ For example:

r2621-vpn uptime is 6 weeks, 5 days, 1 hour, 0 minutes

System returned to ROM by reload

System image file is "flash:c2600-ik9o3s3-mz.122-15.T9.bin"

◆ Resolution: Manually, complete a delete and squeeze on that filename before beginning the OS update.

Cisco 3845

◆ Memory is not currently supported for the Cisco 3845.

Cisco 7206

◆ Issue: Cisco Model 7206 does not correctly display the Hardware Controller I/O Controller version. It incorrectly displays the version as 0.0. This issue is present with IOS Version 12.0(4)XE2, and not in Version 12.2(25)S2.

◆ Resolution: Cisco Model 7206 should be upgraded to a new IOS version.

TFTP Pushes May Fail Silently

◆ Silent configuration command failures may occur when using any of the TFTP transfer methods (snmp/tftp, ssh/tftp, or telnet/tftp). Error status, if any, is being missed from the device following the transfer.

Cisco Router 165

Cisco Devices

TACACS+ Implementation

◆ Issue: Some versions of IOS have a TACACS+ implementation issue that causes additional characters to be added to the login User Name. When this occurs, it may cause occasional login failures.

◆ Resolution: Modify a custom version of the stdlib/stdterm.inc file to issue a backspace character before the username as shown below.

1. Make a directory named $VOYENCE_HOME/custompackage/stdlib

2. Copy the file $VOYENCE_HOME/package/stdlib/stdterm.inc to $VOYENCE_HOME/custompackage/stdlib/stdterm.inc

3. Change the termLogin() function in this new file:

• Search for: send(session,userId+stdEOL,true);

• Change to: send(session,asc(0x08)+userId+stdEOL,true);

• After making the change, restart the device server services.


Cisco Devices

Cisco IOS Switch Package

Device Type Cisco IOS Switch

Specific Model(s) Catalyst Models: 1000, 1100, 1116, 116C, 116T, 1200, 1220, 1220c, 1220i, 1400, 1420, 1600, 1601, 1800, 1900, 1900c, 1900i, 1900 Lite Fx, 1912C,2200, 2820, 2900, 2908ga, 2908xl, 2912MfXL, 2912XL, 2916, 2924CXL, 2924CXLv, 2924MXL, 2924XL, 2924XLv, 2926, 2940 8TF, 2940 8TT, 2948g, 2950-12, 2950-24, 2950-24C, 2950 24GDC, 295024LREG, 295048T, 2950 St24LRE997, 2950 t24, 2955C12, 2955T12, 297024, 297024TS, 2980g,3000, 3001, 3100, 3200, 3201 WMIC, 3500, 3508GXL, 3512XL, 3524XL, 3550-12T, 3550-24, 3550-48, 3560-24PS, 3560-24TS, 3560-48PS, 3560-48TS, 3560G-24PS, 3560G-24TS, 3560G-48TS, 375024, 375024ME, 375024T, 375024TS, 375048, 3750G16TD, 3750Ge12Sfp, 37xxStack, 3900, 3920,4000NAM, 4003, 4006, 4503, 4506, 4507, 4510, 4912g, 4948, 4948-10G, 4k Gateway,5000, 5002, 5500, 5505, 5509, 5k Rsfc,6006, 6009, 6506, 6509, 6509neb, 6513, 6k Msfc, 6k Msfc2, 6knam,8510 msr, 8515 msr, 8540csr, 8540msr,9006, 9009IE3000, IE-3000-4TC,ME3400,WS-CBS3120G-S, WS-C2960G-24TC-L, WS-C3750-48TS, WS-C6509




Configuration Files Single Text, Binary

Configuration Content Quick Commands, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

Configuration Protocols SSH/SCP, SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP, Non-SNMP


Discovery/Identify Methods SNMP, Terminal


Operating System Boot Upgrade, OS UpgradeFor IE-3000-4TC Models: 12.2(0.0.109)EXFor WS-C2960G-24TC-L Models: 12.2(44)SE LAYER_2




Operating System Management Terminal, TFTP

Cisco IOS Switch Package 167

Cisco Devices


◆ Configuration Capture (Revision Config, Rollback, Basic diagramming)







◆ For SNMP:

• sysObjectID value contains 1.3.6.1.4.1.9 or 1.3.6.1.4.1.11

• sysDescription value contains IOS or Internetwork Operating System

• sysService value indicates Layer 2 or non-Layer-3 device

• Valid Cisco ROM ID (.1.3.6.1.4.1.9.2.1.1.0) value

◆ For Non-SNMP

• show version output contains Internetwork Operating System or Cisco IOS

• Device gives a positive reponse to show vtp counters

• Model name (from show version output) corresponds to CatOS family of products


◆ For Terminal:

• startup configuration : show start

• running configuration: show run

◆ For SNMP/TFTP:


• .1.3.6.1.4.1.9.2.1.55.ipAdress -> remoteFilename

Quick CommandsView Interfaces, View ARP, Resync, show cdp neighbors detail

Switch Quick Commands View VLAN, Ping, TraceRoute, view logs using "show logging", Resync, View CDP Neighbors, View Interfaces, View ARP

Hardware Information For SNMP: Hardware Inventory, VLANs, Memory, Interfaces, Serial NumberFor Non-SNMP: Hardware Inventory, Memory, Interfaces, Serial Number


Cisco Devices

◆ For Terminal/TFTP:



◆ For VLAN Database:

• VLAN Text:

– vlan database– show current

• Binary VLAN Database

– dir partitionName:– copy partitionName:/vlan.dat tftp://serverip/filename


◆ From the console prompts, the device is put into configuration mode using enable 15 and configure terminal, and if successful, the configuration is issued line-by-line with checks for banner content and invalid input messages.


◆ SNMP/TFTP:

• Devices supporting OLD-CISCO-SYSTEM-MIB (running configuration only):

– .1.3.6.1.4.1.9.2.1.50.ipAddress -> remoteFilename◆ Commit config:

• SNMP:

– .1.3.6.1.4.1.9.2.1.54.0 -> 1 • Terminal:

– copy running-config startup-config◆ For Binary vlan database:

• copy tftp://serverip/file medium:vlan.dat

Device commands Following are the device command sets you must enable to allow VoyenceControl NG to manage this device class.


show run

show start

show version

show config

show interfaces

configure term

terminal length 0

exit


Cisco Devices

write memory

reload

copy running-config tftp

copy startup-config tftp


copy tftp running-config

show file systems

show module

show vtp counters

show memory summary

dir

dir nvram:

dir flash:

squeeze flash:

show priv

show bootvar

show snmp contact

show snmp location



config-register 0x2102

show file systems

reload

hw-module module "moduleNum"

hw-module standby reload

archive download-sw /overwrite tftp:...

archive download-sw /safe tftp:...


show snmp group

snmp-server user...

snmp-server engineID local

snmp-server context ...

snmp-server view ...

snmp-server group ...

snmp-server community ...

aaa new-model

no aaa new-model


Cisco Devices

line console 0

line vty 0

login

password

exit

line aux 0

no username ...

username "userName" privilege "userLevel" password "password"

no enable secret level

no enable password level

enable secret level

enable password level

◆ Quick Commands

ping "ip-addr"

view ip route

view arp

view ip interface brief

clear counters

view process cpu

view management event

copy run start


view vlan

view logging

view cdp neighbors detail

view frame-relay map

view diag



running

Startup

Vlan.dat

Vlan text


Cisco Devices

Device data



Known issues


Cisco IOS Switches - Missing VLAN Database Command

◆ The ME3400 does not return VLAN text, due to lack of support for the vlan database command. This will appear in the scheduler with a message of the form: Dialog getVLANs failed: Warning, can not resolve input value (ConfigFile:vlan text.Content)

Cisco IOS Switches - VLAN Databases

◆ To pull VLAN Databases successfully, the device must be discovered as a Cisco IOS Switch.

◆ If it is not discovered as a Cisco IOS switch, you must edit the IOSModels.XML in $VOYENCE_HOME/custompackage /pkgxml, and then re-discover the device.

Cisco IOS Switches - Missing Hardware Information

◆ Issue: Cisco IOS Switches with OS version 12.0 (5.2) XU do not display device OS information correctly in the Device Hardware tab.

◆ Resolution: Disable all SNMP Credentials, and then Pull the Hardware using Non-SNMP. Doing this ensures the memory size is pulled correctly, and is then populated using the terminal commands. This must be completed before beginning an OS Upgrade.

ARP Table Yes


CAM Table Yes


Identity Yes

Interfaces Yes

Keys No

Memory Yes

Access Control List Match Counts Yes

OSPF Settings No


Routes Yes


VLAN Trunk Protocol Yes

VLANs Yes


Cisco Devices

Cisco IOS - Out-of-Sync

◆ When a SNMP/TFTP mechanism is used with only a Community String credential, the Running against Startup Configuration Out-of-Sync icon is not displayed. A valid Account and/or Privilege Password credential is needed to pull the Startup configuration on Cisco IOS devices.

Cisco IOS Upgrade - SNMP Information

◆ There is no available OS install target for the 3524 Switch.

• Issue: SNMP information is not present for this model. The information must be retrieved from the IOS CLI.

• Resolution: Remove all SNMP community strings from the communication settings of the device, and re-pull the hardware specification. This provides the needed memory information to allow for an OS upgrade.

Cisco IOS Update

◆ Issue: An issue exists where the OS image resided in bootflash, but was not the boot loader image. Additionally, the system image file was not in the show version command. In this case, the application could not free space in the target location. Manual intervention is needed to free space.

When there is insufficient space in the target location for an OS update on Cisco IOS devices with Class A file systems, the system attempts to free up additional space by deleting and squeezing the system image name displayed in the show version command.

◆ For example:

r2621-vpn uptime is 6 weeks, 5 days, 1 hour, 0 minutes

System returned to ROM by reload

System image file is "flash:c2600-ik9o3s3-mz.122-15.T9.bin"

◆ Resolution: Manually, complete a delete and squeeze on the filename before beginning the OS update.

TFTP Pushes May Fail Silently

◆ Silent configuration command failures may occur when using any of the TFTP transfer methods (SNMP/TFTP, SSH/TFTP, or Telnet/TFTP). Error status, if any, is being missed from the device following the transfer.

TACACS+ Implementation

◆ Issue: Some versions of IOS have a TACACS+ implementation issue that causes additional characters to be added to the login User Name. When this occurs, it may cause occasional login failures.

◆ Resolution: Modify a custom version of the stdlib/stdterm.inc file to issue a backspace character before the username as shown below.

1. Make a directory named $VOYENCE_HOME/custompackage/stdlib

2. Copy the file $VOYENCE_HOME/package/stdlib/stdterm.inc to

$VOYENCE_HOME/custompackage/stdlib/stdterm.inc

3. Change the termLogin() function in this new file:

• Search for: send(session,userId+stdEOL,true);

• Change to: send(session,asc(0x08)+userId+stdEOL,true);

• After making the change, restart the device server services.


Cisco Devices

Cisco IOS XR

Device Type

Specific Model(s)



Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands





◆ Device Access (Cut Thru, Device Commands)


◆ Operating System Upgrade (Upgrade Operating System Files and Activate



◆ Model, Serial Number, MAC and OS version from the command line interface

◆ Filesystem and Memory from the command line interface

◆ Interface table from the command line interface

Cisco IOS XR Network Operating System

CRS-1, 12000XR Series


Syslog, SNMP Traps (disabled by default)

Text based running config and admin config




SNMP, Terminal

In-Band

Version 3.4 and higher



Terminal

SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP (FTP protocols require external FTP server)

Ping, Traceroute, View NAT Setup, View Routes, View ARP, View Interfaces, Clear Interface Counters, View Diagnostic

Chassis, Slot/Card Inventory, Interfaces, Power, Fans, Memory, FileSystems


Cisco Devices



◆ For SSH/TFTP and Telnet/TFTP:

• copy running-config tftp://[server_ip]/[filename]

◆ For SSH and Telnet





• copy tftp://[server_ip]/[filename] running-config

◆ For SSH and Telnet

• The device is brought to a shell prompt in config mode.

• The configuration is entered line-by-line with checks for invalid input.


The following are the commands that are used to do an operating system upgrade.

◆ install remove inactive sync

• This command is optional.

◆ install add [proto]://[serverip]/[osfile] sync

• This command is executed once for each upgrade file in the job.

◆ install activate [filelist] sync

• This command is executed once, with a list of all files added in the previous step.

◆ install commit sync

• This command is optional.



Running

Admin

Packages

Cisco IOS XR 175

Cisco Devices



Known issues


Cisco IOS XR Network Operating System

◆ The Cisco IOS XR - Secure Domain Router functionality is not supported.

◆ This device driver does not interface with the Cisco IOS XR's configuration store and commit lists.

Cisco IOS XR - Login Credentials

◆ It is advisable to use login credentials that belong to the root-system group, for this driver. All credentials created by this driver will belong to the root-system group.

◆ When rolling a login credential, an attempt to place the new user in the same user groups with the old user is made.

◆ Login credentials cannot be rolled if TACACS or Radius authentication is in use.

• To identify if TACACS/Radius is in use, the show [tacacs|radius] server-groups command is used.

• Login credentials will not be rolled if the output of the show [tacacs|radius] server-groups command has a global list of servers indicating external authentication is in use.

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No


Cisco Devices

Cisco IOS XR - SNMP Communities

◆ It is advisable to use SNMP communities that belong to the SystemOwner attribute set, with this driver. All communities created by this driver will belong to the SystemOwner attribute set.

Cisco IOS XR - Conifguration Changes

◆ When pushing config changes, If a commit fails when pushing configuration changes to the device, the show configuration failed command is issued. The results for the show configuration failed command is included in the output of the jobs result text.

◆ Push to the user mode config is currently the only capture command supported

Cisco IOS XR 177

Cisco Devices

Cisco Intrusion Prevention System (IPS)

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands







◆ Operating System Management System (Used to update signature files)



◆ Model, Serial Number, and OS version using SNMP or Command-Line Interface

◆ Memory using Command-Line Interface


Cisco Intrusion Prevention System

IPS-4255-K9

www.cisco.com

No

Syslog, SNMP Traps

Running


SSH, Telnet


SNMP, Terminal

In-Band

6.1

SSH, Telnet

SSH, Telnet

Terminal

Yes

Ping, Traceroute, Show diag



Cisco Devices



◆ A command line interface session is started and the output of show configuration is captured.



◆ A command line interface session is started, config mode is entered, and the configuration is entered line-by-line.

Multi-config files





Running

ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Cisco Intrusion Prevention System (IPS) 179

Cisco Devices

Known issues


Cisco Intrusion Prevention System (IPS)

◆ Banner input is error prone. Do not put the word exit on a line by itself in a banner.

◆ This driver was built on an IPS-4255 but should manage any Cisco IPS/IDS 42xx system.


Cisco Devices

Cisco Lightstream Package

Device Type Cisco Lightstream ATM Switch







◆ SysObjectIDs

• 1.3.6.1.4.1.9.1.164

• 1.3.6.1.4.1.9.1.107


◆ Valid Cisco ROM ID in SNMP

Specific Model(s) LS 1010, LS 1015

Documentation/Information http://www.cisco.com/en/US/products/hw/switches/ps1893/index.html




Configuration Content Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet, Config

Configuration Protocols SSH/SCP, SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP


Discovery/Identify Methods SNMP

Password Management AAA, In-Band, SNMP




Hardware Information For SNMP: Memory, Interfaces, Serial Number

Cisco Lightstream Package 181

Cisco Devices



◆ show start for startup configuration

◆ show run for running configuration


• set OID .1.3.6.1.4.1.9.2.1.55.IP to the TFTP server's filename

• Fall back to Telnet/TFTP for startup configuration






◆ From the console prompts, the device is brought to the enable mode using enable 15 then to the configure mode using conf t after which the configuration is entered line by line with checks for banners and for Invalid Input.



• .1.3.6.1.4.1.9.2.1.50.IP = filename on tftp server

• .1.3.6.1.4.1.9.2.1.54.0 = 1 to copy run to start

◆ To copy run to start from command line




running ¸

Startup


Cisco Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Cisco Lightstream Package 183

Cisco Devices

Cisco Nexus

Device Type

Specific Model(s)


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands



◆ Configuration Management (Revision Config, Basic Diagramming)


◆ Credential Management (In-Band)

Discovery/identify methodsThe following are used to provide information about your device (Host Name, Type, Vendor, Model, Operating System, and Serial Number).

◆ Device model must be accessible from ENTITY-MIB's chassis entry (SNMP) or appear as Cisco NexusNNNN Chassis in response to 'show inventory' (terminal).

◆ Interface information must be obtainable from IF-MIB (SNMP) or parsed from show interface.

◆ sysObjectID value must be readable from SNMPv2-MIB (SNMP) or mapped by model name from CiscoModels.xml.

Switch

1000V,5010, 5020,C7010, C7018,MDS 9222i

www.cisco.com

Single Text




SNMP, Terminal

SNMP, Account

4.0(1a)N1(1a)For MDS 9222i Models: 4.1(3a)For 1000V Models: 4.0(4)SV1(1)



Terminal

In-Band

Memory, Serial number, Software Version, Inventory, File System


Cisco Devices







• copy running-config /tftp://remoteIpAddress/remoteFilename

• copy startup-config /tftp://remoteIpAddress/remoteFilename



• Active configuration command are replayed using the command line, and the results are checked for fatal errors


• copy tftp://remoteIpAddress/remoteFilename running-config

• copy tftp://remoteIpAddress/remoteFilename startup-config



terminal length 0

show version

show inventory

show snmp

show hostname

show running-config

show startup-config

configure terminal


copy (runnig-config|startup-config) tftp://address/path

reboot

copy ? (to determine filesystem name)

delete ?

format ?

dir (?|name)

Cisco Nexus 185

Cisco Devices

ping

traceroute

show ip interface vrf all

show route vrf all

show arp vrf all


[no] snmp community token (ro|rw)

show aaa authentication

show users

username token password secret role network-admin

[no] username token



Running

Startup


Cisco Devices

Device data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes Yes



VLANs No

Cisco Nexus 187

Cisco Devices

Known issues The following details existing device issues that have been discovered with other releases. In most cases, a resolution is included to address the issue.

Cisco Nexus

◆ The driver supports the MDS series running NX-OS if Nexus or NX-OS appears in the show version response, and the driver is successful in determining the identity, system properties, and interfaces for the device.

◆ The management VRF must have a default route configured or file transfers will fail.

◆ If the command system default switchport appears literally in the configuration, it must be removed or commented out before pushing with terminal, or the resulting % Incomplete command message will be treated as a failure, although the push content will be accepted.

◆ Privilege account rolls are not supported because accounts are role based, and VoyenceControl credentials are give network-admin privileges. Any attempt to execute a job including privilege credential changes will fail.

◆ IP addresses and ARP table entries are not reported using SNMP.

◆ Config Change Detection is only supported using syslog monitoring.

◆ Switches running 4.0(4)SV1(1) have been observed to intermittently fail account credential rolls when both the account and password are changed.

• A failsafe in the device prevents deletion of the original account, if the account is logged in.

• The driver executes a show users command if this message is detected, but the account does not appear in the response.

• Currently, only the account password can be successfully changed. This behavior is not observed on the hardware products.

Cisco Nexus 1000V

◆ Push to start is not supported.

• The copy tftp startup command is deprecated.

• The config content is silently ignored, although the job shows as successful in the scheduler.

• The recommended Cisco procedure of write erase, reload, copy tftp running cannot be implemented due to a high probability of the application and managed device being located on different subnets.

◆ The Nexus 1000V virtual switch running 4.0(4)SV1(1) has been found to include commands that cannot be pushed back to the device from the command-line interface. Such content must be commented out or removed prior to scheduling a full configuration push or the job will fail (though other changes will effectively succeed). This behavior has not been observed for pushes using TFTP. An example of these commands is included below; other forms may occur as well.

• limit-resource u4route-mem minimum 32 maximum 80

• limit-resource u6route-mem minimum 16 maximum 48


Cisco Devices

Cisco MGX

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available

◆ Discover/Identify using SNMP and Terminal (Auto-Discovery, Identify, Appear in Product)

◆ Incremental Updates (Configlet or Device Commands)

◆ Hardware and Interface Information

◆ Backup and Restore from Archive File

◆ SSH and Telnet Support


◆ Quick Commands




8850 Wide Area Switch - MGX 8850 PXM-45 and MGX 8250 PXM-1

Cisco Provided

No

Binary backup to file system of compressed archive

Binary, Command-Line Interface

SSH or Telnet


SNMP, Telnet, or SSH

Single Account Credential Password only, SNMP Read and Read-Write

5.2

Compressed Tar Archive by means of FTP

Compressed Tar Archive by means of FTP, Device Commands, Configlets

Terminal

Enable Automatic Backups, Disable Automatic Backups, Display Cards, Display Card, Display IMA Groups, Display IMA Group Counters, Display IMA Link Counters, Display Alarms, Display Hardware Alarms, Display Software Alarms, Display Port Counters, Display Port, Display Ports, Display Connection, Display Lines, Display PNNI Node, Display PNNI Node List, Display PNNI Neighbor, Display PNNI Link, Display PNNI Routing Policy, Setup NAT, View NAT Setup

Hardware provided by means of SNMP using Entity MIB or Terminal

Cisco MGX 189

Cisco Devices

Both SNMP and Telnet or SSH access are required to properly discover and manage the MGX.

◆ Name of device is taken from dspcds NodeName field.

◆ Model name is determined by the SNMP system description set by the vendor.

◆ Model Cisco MGX 8850 Wide Area Switch = 8850 PXM-45

◆ Wan Edge Switch = 8250 PXM-1

◆ OS Version is determined by dspcds either from the System Rev or PXM firmware version depending on the PXM version.

◆ Chassis serial number is determined by the dsplicnodeid command on the PXM-45 and the dspcds BkplnSerialNum on the PXM-1.



◆ saveallcnf -f

A saved configuration file is named using the switch name and the current date as follows:

switchname_dateCode<N|O>. The saved configuration file will reside in the /tftpboot directory of the device server. The device driver will report the saveallcnf results along with the name of the file stored as a result of the capture operation.

Note: Automatic backups will be disabled after every configuration capture.

◆ You can save a configuration if both of the following are true:

• No save or restore process is currently running.

• No configuration changes are in progress.

Configuration captures for the device have an enable and disable feature. The quick commands Disable Automatic Backups and Enable Automatic Backups are provided to prevent VoyenceControl from automatically issuing the saveallcnf after every device change. This feature should remain disabled unless a backup is required.



◆ restoreallcnf -f

This command is issued after a backup capture is transferred to the machine using FTP. This backup is named in the revision history as "FILE: <BackupName> SAVED: <Date>" Sending the string as described shown in VoyenceControl will initiate the transfer and restoreallcnf command.

If these files are needed for manual restore procedures they can be found in the /tftpboot directory of the VoyenceControl device server.


Cisco Devices

Device commands


◆ Quick Commands

The following quick commands are provided to allow quick diagnostic commands on the device from the workspace right-click menus. Where a card number parameter is required the quick command will use the "cc" command to redirect the session to the appropriate card before executing the command.

• Test Credentials - Validates and tests read-only community string and login management credentials.

• Enable Automatic Backups - Enables the driver for saveallcnf operation.

• Disable Automatic Backups - Disables the driver for saveallcnf operation.

• Display Cards - Runs the dspcds command.

• Display Card - Runs the dspcd command, optionally supplying the SRM slot number.

– Parameter Card Number of type Integer.– Parameter SRM Slot Number (optional) of type Integer.

• Display IMA Groups- Runs the dspimagrps command.

– Parameter Card Number of type Integer.• Display IMA Group Counters - Runs the dspimagrpcnt supplying the

bay.group and interval.

– Parameter Card Number of type Integer.– Parameter Bay Number 1-2 of type Integer.– Parameter Group Number 1-16 of type Integer.– Parameter Interval 0-96 of type Integer.

• Display IMA Link Counters - Runs the dspimalncnt and/or dspimalnkcnt commands depending on the PXM version.

– Parameter Card Number of type Integer.– Parameter Interface Number of type Integer.– Parameter IMA Member Link of type Integer.

• Display Alarms - Runs the dspalms command.

– Parameter Card Number of type Integer.• Display Hardware Alarms - Runs the dsphwalm command.

– Parameter Card Number of type Integer.• Display Software Alarms - Runs the dspswalm command.

– Parameter Card Number of type Integer.• Display Port Counters - Runs the dspportcnt command providing the

interface number and interval.

– Parameter Card Number of type Integer.– Parameter Interface Number 1-31 of type Integer.– Parameter Interval (optional) of type Integer.

• Display Port - Runs the dspport command providing the interface number.

– Parameter Card Number of type Integer.– Parameter Interface Number of type Integer.

Cisco MGX 191

Cisco Devices

• Display Ports - Runs the dspports command.

– Parameter Card Number of type Integer.• Display Connection - Runs the dspcon command.

– Parameter Card or Interface Number of type Integer.– Parameter Port ID of type Integer.– Parameter vpi range of type Integer.– Parameter vci range of type Integer.– Parameter DLCI (optional FRSM only) of type Integer.

• Display Lines - Runs the dsplns command.

– Parameter Card Number of type Integer.– Parameter SRM Slot Number (optional) of type Integer.

• Display PNNI Node - Runs dsppnni-node

• Display PNNI Node List - Runs dsppnni-node-list

• Display PNNI Neighbor - Runs dsppnni-neighbor

• Display PNNI Link - Runs dsppnni-link

• Display PNNI Routing Policy - Runs dsppnni-routing-policy

• Setup NAT - Configures the NAT IP address of the individual device.

– Parameter Device Server NAT IP of type IpAddress.• View NAT Setup - Displays the NAT IP configuration for the individual

device.

Known issues


Cisco MGX - Restore Causes Device Reset and Loss of Service

◆ Issue: Restoring the device capture causes a device reset and loss of service.

◆ Resolution: Testing shows the loss of service is in the range of 2 to 5 minutes.

Cisco MGX - PXM-1 Card Shows Only Two Interfaces

◆ Issue: PXM-1 cards show only two interfaces.

◆ Resolution: The device SNMP agent only reports two interfaces. This is a limitation of the network device.

Cisco PXM-1 Cards - MIB not entirely Supported

◆ Issue: PXM-1 cards do not support the Entity MIB and hardware information is displayed differently than a PXM-45 card.

◆ Resolution: The models having PXM-1 cards require terminal access to collect hardware information.

Cisco PXM-1 Cards - No SSH support

◆ Issue: No SSH support for Cisco PXM-1 cards.

◆ Resolution: The Cisco PXM-1 cards does not support SSH.

Cisco PXM-1 Cards - Not Responding After saveallcnf Command

◆ Issue: PXM-1 cards can sometimes not respond after a saveallcnf command.


Cisco Devices

◆ Resolution: Device capture operations will not succeed if the device does not respond with the success status of the command.

Cisco RPM Cards - Cards not Reported in Hardware Output

◆ Issue: RPM Cards are not fully reported in the MGX hardware output.

◆ Resolution: RPM cards are reported under the RPM IOS hardware inventory and do not provide dspcd information at the terminal.

Cisco MGX 193

Cisco Devices

Cisco MDS

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available◆ Discover/Identify (Auto Discover, Identify, Appear in Product)



◆ Credential Management (Including SNMPv3)


◆ sysObjectID

• SNMP scalar checks for Cisco enterprise ID

◆ sysServices

• SNMP scalar checks for layer 2 and 3 flags (0x06 value)

◆ sysDescription

• Checks for SAN-OS

Switch

9124, 9134, 9216, 9216A, 9216i, 9509, 9513

http://www.cisco.com

Yes

Single Text


Telnet, SSH


SNMP

SNMP, Account

San-OS 3.0, 3.2, 3.3

Telnet, SSH

Telnet, SSH

Terminal

Ping, Trace Route, ARP, Interface, VLANs, CDP Neighbors

For SNMP: Hardware Inventory, Memory, Interfaces, Serial Number, Model, Software Version


Cisco Devices



◆ For Terminal:





◆ Configuration commands are issued interactively to the device

Device commands



enable

configure terminal

show running-config

show startup-config

terminal length

ping

traceroute

show arp

show interface brief

show logging

show system resources


[no] snmp-server community

[no] snmp-server user securityName (auth authProto authPhase (priv privProtocol privPhrse))

username

Cisco MDS 195

Cisco Devices

Multi-config files



Device data



Known Issues


Cisco MDS

◆ If the device is upgraded to run NX-OS, it will not appear as a Cisco Nexus device class until it is re-discovered. It is not necessary to drop the device, but pre-Nexus config pushes may fail, depending on the content.

running

startup

ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No


Cisco Devices

Cisco Wide Area Application Services

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


(WAAS)




◆ Device Access (Cut Through, TERMlets, etc.)

Switch

512, 612, 674, 7371

www.cisco.com

Yes

Syslog

ASCII


Telnet, SSH, SSH/TFTP, Tenlet/TFTP


SNMP, Terminal

Account, Privilege Mode, SNMPv1/2

4.8.0-12



Telnet, SSH

View Routes, View ARP, Ping, TraceRoute, Resync, View CDP Neighbors

Memory, Interfaces, Serial Number, Model, OS Version, Inventory

Cisco Wide Area Application Services (WAAS) 197

Cisco Devices



◆ For SNMP:

• sysDescr value must contain Wide Area Application Services

• Model name is obtained from the following oids (in order):

– 1.3.6.1.4.1.9.9.368.1.34.3.0– 1.3.6.1.4.1.2467.1.34.3.0– Part number column of the CISCO-ENTITY-ASSET-MIB for the chassis

entry◆ For Terminal:

• Show version output must contain Wide Area Application Services

• sysObjectId value is mapped from the model name which is parsed from the output of show hardware for a non-blank field, in the following order:

– ModelNum (raw)– ModelNum, where (text) optionally precedes the model name– ExtModel





◆ For Telnet/TFTP use the following commands:

• copy startup-config tftp serverAddress localFilename

• copy running-config tftp serverAddress localFilename


◆ From the console prompts the device is brought to the enable mode using enable.

• Device paging is disabled using the no terminal more or terminal length 0 command.

• The configuration is entered line by line after the device is placed into configuration mode using configure terminal.


• copy tftp <serverAddress> < localFilename> startup-config

◆ To copy run to start from the command line:



Cisco Devices

Multi-config files



Device data



Running

Startup

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Cisco Wide Area Application Services (WAAS) 199

Cisco Devices

Cisco Wireless LAN Controller

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands









◆ Model, Serial Number, MAC and OS version using SNMP or the command line interface.

◆ Filesystem and Memory using the command line interface.

◆ Interface table using SNMP or the command line interface.


2100 series, 4400 series

www.cisco.com

No

Syslog, SNMP Traps

running, readable




SNMP, Terminal

In-Band

4.0

Running by means of TFTPReadable by means of Terminal

Running by means of TFTP

Terminal

View Routes, View ARP, Ping, Resync, Clear counters, Show diag, ship interface brief



Cisco Devices



◆ Readable config is captured from a terminal session using the show run-config command

◆ Running config is retrieved using the devices transfer upload command.



◆ Configlets are pushed to the device by opening a command line interface session, entering configuration mode, and sending the content line-by-line.

◆ Running config is pushed using the devices transfer download command.




Running

Readable


ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No

Cisco Wireless LAN Controller 201

Cisco Devices

Known issues



◆ The Cisco Wireless LAN Controller does not have a readable configuration. The running config is either binary or xml, depending on the operating system version. A running config can be pushed back to the device for rollback. Incremental changes can be pushed using the configlet mechanism.



VLANs No



17

Citrix Devices


◆ Citrix Netscaler LoadBalancer................................................................................... 204

Citrix Devices 203

Citrix Devices

Citrix Netscaler LoadBalancer

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands









◆ SysObjectIDs: 1.3.6.1.4.1.5951.1.*

◆ OS version in sysDescr at least v6.0

◆ Interface table from MIB-2

Citrix Netscaler LoadBalancer

7000, 9000, 10000, 12000

http://www.citrix.com/

No

Syslog, SNMP Traps

Multiple Text and Binary


SSH/SCP, SSH, Telnet

CLI, SNMP

SNMP, Terminal

In-Band

6.0 or greater



Terminal

Ping, Resync

For SNMP: Interfaces


Citrix Devices



◆ For SSH/SCP:

• SCP /flash/nsconfig/ns.conf to device server

• SCP is only used for the start configuration

◆ For SSH and telnet capture output from the following commands:

• show ns runningconfig (for running configuration)

• show ns ns.conf (for start configuration)


◆ For SSH/SCP (used for start configuration):

• SCP config file to /tmp/ns.conf

• cp /tmp/ns.conf /flash/nsconfig/ns.conf

• chmod 0644 /flash/nsconfig/ns.conf

◆ For SSH and telnet (used for running configuration):

• The device is brought to a shell prompt and the configuration is entered line by line with checks for invalid input.

Multi-config files



Device data


running --

startup --


ARP Table Yes


CAM Table No


Identity Yes

Citrix Netscaler LoadBalancer 205

Citrix Devices

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



18

D-Link Devices


◆ D-Link xStack............................................................................................................... 208

D-Link Devices 207

D-Link Devices

D-Link xStack

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access



Features available




◆ Credential Management (In-band, SNMP)



◆ sysObjectID

• Contains 1.3.6.1.4.1.171.10.64.2


◆ Telnet/SSH:

• show config current_config

• show config config_in_nvram

Switch

3550

ftp://ftp.dlink.com/Switch/des3550/Manual/

No

Single ASCII

Config, Configlet, Termlet Merge, Termlet Privilege Mode

SSH, Telnet


SNMP

In-band, SNMP

4.01

SSH, Telnet

SSH, Telnet

Terminal

View Interfaces, View ARP, View Routes, Ping

Memory, Interfaces, Serial Number OS Version


ftp://ftp.dlink.com/Switch/des3550/Manual/

D-Link Devices



◆ Telnet/SSH:

• Commands are issued to the command line interface.

• Results are scanned for errors.

Multi-config files





running

ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

D-Link xStack 209

D-Link Devices

Known issues


D-Link xStack

◆ No volatile or non-volatile storage information is available using SNMP, for this device class.

◆ User accounts are defined at administrator level.


19

Edgewater Devices

This chapter contains the following topic.

◆ Edgewater EdgeMarc Router .................................................................................... 212

Edgewater Devices 211

Edgewater Devices

Edgewater EdgeMarc Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands








◆ SysObjectIDs: 1.3.6.1.4.1.8072.3.2.10.* or 1.3.6.1.4.1.19139.*

◆ Compiler Options at OID .1.3.6.1.4.1.2021.100.6.0


Edgewater EdgeMarc Router

4200, 4300T, 4500, 5300, 6400

http://www.edgewaternetworks.com/

No

Syslog, SNMP Traps

Single Text



CLI, SNMP Only

SNMP, Terminal

Enable, In-Band

SSH/Terminal, TFTP

SSH/Terminal, TFTP

Terminal

View Routes, View ARP, Ping, TraceRoute, Reboot, View Interfaces



Edgewater Devices



◆ For SSH/TFTP and Telnet/TFTP use the following commands:

• ewn save [temp_filename]

• tftp -p -l /etc/config/[temp_filename] -r [temp_filename] [device_server_ip]

◆ For SSH and Telnet capture output from the following commands:

• ewn save [temp_filename]

• cat /etc/config/[temp_filename]


◆ For SSH/TFTP and Telnet/TFTP use the following commands:

• tftp -g -l /etc/config/[temp_filename] -r [temp_filename] [device_server_ip]

• ewn load [temp_filename]

◆ For SSH and Telnet deployment of the configuration, the device is brought to a shell prompt and the configuration is entered line-by-line with checks for invalid input.

Multi-config files




running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No

Edgewater EdgeMarc Router 213

Edgewater Devices


OSPF Settings No


Routes Yes



VLANs No



20

Enterasys Devices


◆ Enterasys Smartswitch Router .................................................................................. 216

Enterasys Devices 215

Enterasys Devices

Enterasys Smartswitch Router

Device Type

Specific Model(s)


Enabled By Default

Operating System


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


Features available◆ Discover/Identify (Autoo Discovery, Identify, Appear in Product)



◆ Configuration Change Notification (Syslog, SNMP Trap)


◆ For SNMP:

• sysDescr contains Enterasys


Router

XP 2400

http://secure.enterasys.com/support/manuals/

No

E10.0.0.3A

SysLog, Trap

Single ASCII


Telnet Only, SSH Only, Telnet/TFTP, SSH/TFTP


SNMP

In-Band

Telnet Only, SSH Only, Telnet/TFTP, SSH/TFTP

Telnet only, SSH only, Telnet/TFTP, SSH/TFTP

Terminal

Standard

Serial Number, OS Version, Memory, Inventory


Enterasys Devices




• Running:

– system show active • Startup:

– system show startup◆ For Telnet/TFTP and SSH/TFTP:

• Running:

– copy active to tftp://ipAddress/remoteFilename • Startup:

– copy active to tftp://ipAddress/remoteFilename




• The device is placed in configure mode and commands are issued interactively from the command line interface.

• The results are scanned for errors. If no errors are found, the scratchpad configuration is copied to the active or startup configuration, depending on the push type.


• Running:

– copy tftp://ipAddress/remoteFilename to scratchpad– copy scratchpad to active

• Startup:

– copy tftp://ipAddress/remoteFilename to active



cli set command completion off

cli terminal monitor off

cli set terminal rows 0

system show active

system show startup

copy scratchpad to active

Enterasys Smartswitch Router 217

Enterasys Devices

copy scratchpad to startup

enable

exit

copy active to startup

configure

reboot

Multi-config files



Device data



running

startup

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Enterasys Devices

Known issues


Enterasys SSR

◆ Credential management is not supported.

◆ Comment characters are not ignored by the device class and are skipped when the configuration is pushed using Telnet or SSH.

◆ The presence of the last modified comment is used to distinguish full configurations from configlets.

Enterasys Smartswitch Router 219

Enterasys Devices


21

Ericsson Devices


◆ Ericsson ECN Switch .................................................................................................. 222◆ Ericsson MSED ............................................................................................................ 225

Ericsson Devices 221

Ericsson Devices

Ericsson ECN Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Operating System



Cut-Through Access

Quick Commands


Features available







◆ Model, Serial Number, and Operating System version using SNMP or command line interface.

◆ File Systems using command line interface.

◆ Interface table using SNMP or command line interface.


◆ From a command line interface session, the output of show running-config or show startup-config is captured as the running or startup configuration.

Ethernet Switch

320, 330

www.ericsson.com

Yes

Running, Startup


SSH, Telnet


SNMP and Terminal

1.2

SSH, Telnet

SSH, Telnet

Terminal

Ping, View ARP, View Routes, View Interfaces, Resync

Hardware Inventory (SNMP Only), File Systems, Interfaces, Serial Number


Ericsson Devices



◆ A stored configuration is pushed to the systems running config by opening a command line interface session, entering configuration mode, and sending the config line-by-line to the command line interface session.

◆ After pushing a running configuration, the configuration can optionally be copied to the startup configuration by issuing the command line interface command copy running-config startup-config.

◆ After pushing a running configuration, the system can optionally be restarted by issuing the command line interface command reload.




Running

Startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes

Ericsson ECN Switch 223

Ericsson Devices

Known issues


Ericsson ECN Switch

◆ Ericsson ECN configs cannot be re-entered at a config prompt, because they do not properly exit from sub-config modes. This driver will attempt to send an exit command anytime the config parser receives a comment line in the configuration while the system is at a sub-config prompt.

◆ On some Ericsson ECN models, the output of show running-config or show startup-config is not a valid config, in that it cannot be re-entered at a config prompt without causing %invalid input errors. Invalid configurations will cause push jobs to fail, and the offending lines must be edited out before sending the configuration to the device.



VLANs No



Ericsson Devices

Ericsson MSED

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


Features available

◆ Discover/Identify (SNMP)

◆ Configuration Capture (Pull running configs)

◆ Configuration Deploy (Push Configlets, TERMlets)




◆ Discovery Mechanism:

• Look for Ericsson MSED in sysDescr

◆ Model from sysDescr

◆ Operating System from show system info output

◆ Serial Number from show system info output

Router/Edge Device

MSED/HL950

www.ericsson.com

No

Syslog, SNMP Traps

Binary Running Config, Text Running Config

ARP, Routes, Interfaces, Identity, System Properties


CLI, SNMP

SNMP

In-band



Terminal

Ping

Model, Operating System, Serial Number

Ericsson MSED 225

Ericsson Devices



◆ config export /[TEXT_FILENAME]

◆ config backup /[BINARY_FILENAME]



◆ For push to start:

• config restore [BINARY_FILENAME]

◆ For push to run:

• The text version of the configuration is entered line by line at a CLI prompt



Device data


running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes


Ericsson Devices



VLANs No


Ericsson MSED 227

Ericsson Devices


22

Extreme Devices


◆ Extreme ......................................................................................................................... 230◆ ExtremeWare XOS ....................................................................................................... 233

Extreme Devices 229

Extreme Devices

Extreme

Device Type

Specific Model(s)


Enabled By Default



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands


Features available






Extreme Switch

Alpine 3802, Alpine 3804, Alpine 3808,Black Diamond 6804, Black Diamond 6800, Black Diamond 6808, Black Diamond 6816, Enet Switch 24 Port,Summit 1, Summit 2, Summit 3, Summit 4, Summit 4fx, Summit 48, Summit 48i Summit 24, Summit 24E3Summit 7iSX, Summit 7iTX, Summit 1iTX, Summit 5i, Summit 1iSX, Summit 5iLX, Summit 5iTX, Summit 48SI, Summit PX1, Summit 24E2TX, Summit 24E2SX

http://www. extremenetworks.com

Yes

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Configlet, Config

Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP

Command Line

SNMP

In-Band, SNMP

OS Upgrade

TFTP, Terminal

TFTP, Terminal

Terminal

TFTP

Ping, TraceRoute



Extreme Devices



◆ sysObjectID

• contains 1.3.6.1.4.1.1916.2

Multi-config files



Device data



running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Extreme 231

Extreme Devices

Known issues


Extreme Summit (Model Summit iTx)

◆ When working with the Extreme Summit device switch, the configuration text lines containing "delete" may cause connectivity loss if used in a Configuration Roll Back. Remove the "delete lines" before the Push to avoid loss of connectivity with the device during a Roll Back, or when using Restore to restore an old revision.

Extreme Device - Configuration not changing after Push

◆ Issue: For Extreme Summit Software Version 6.1.5, configuration changes (pushes) will not take on the device using the SNMP/TFTP mechanism.

◆ Resolution: Ensure you use the Telnet or Telnet/TFTP mechanisms for Extreme Summit configuration pushes.

Config Push using Telnet to Extreme Switch - Unsuccessful

◆ Issue: Pushing an entire configuration to the Extreme Switch should not be executed using Telnet unless disable commands (which can potentially stop the management interface) are removed before pushing the config.

• For example, for a configuration entry such as, disable ipforwarding vlan Default.

– A disable command in the device configuration takes the form disable string (where string may be an interface).

– All disable commands can easily be removed from the device configuration using a text editor.

You can push a full configuration using the SNMP/TFTP mechanism as a work around. Additionally, you can push configlets to the device.

◆ Resolution: Use configlets when making changes to the Extreme Summit with Telnet or SSH.

Note: SNMP/TFTP can be used for configuration pulls; however, changes cannot be the configuration using this mechanism.


Extreme Devices

ExtremeWare XOS

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access





◆ Credential Management


◆ sysObjectID

• OID contains 1.3.6.1.4.1.1916.2

◆ sysDescr

• OID contains ExtremeWare XOS


◆ tftp ipAddress -p -l localFilename -r remoteFilename

Switch

BlackDiamond 10808, 12804

www.extremenetworks.com

No

Single XML


SSH, Telnet, Telnet/TFTP, SSH/TFTP


SNMP

SNMP, Account

11.3.4.5



Terminal

Memory, Interfaces, Serial number, OS version, Inventory

ExtremeWare XOS 233

http://www.extremenetworks.com

Extreme Devices



◆ tftp ipAddress -g -l localFilename -r remoteFilename

Multi-config files



Device data



running

startup

ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes No



VLANs No


Extreme Devices

Known issues


ExtremeWare XOS

◆ Configuration management is not supported if TFTP is not enabled for the device class.

◆ Configuration pushes have not been certified.

ExtremeWare XOS 235

Extreme Devices


23

F5 Devices


◆ F5 Load Balancer Rev 3 .............................................................................................. 238◆ F5 Load Balancer Rev 4 .............................................................................................. 242◆ F5 Load Balancer Rev 9 .............................................................................................. 245

F5 Devices 237

F5 Devices

F5 Load Balancer Rev 3

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands

Features available


◆ Configuration Capture (revision config, rollback, basic diagramming, multi config)





◆ sysObjectID: .1.3.6.1.4.1.3375.1.1

Load Balancer

Big-IP-HA, Big-IP-LB, Big-IP-3-DNS, Big-IP-FLB, Big-IP-CLB, Big-IP-XLB, Big-IP-SSL

www.askf5.com (registration required)

Yes

Syslog, Trap

Multiple Complex (Linux based)

Termlet Merge, Privilege Mode Termlet, Configlet

Telnet, SSH, Telnet/FTP, SSH/FTP, SSH/SCP

CLI

SNMP

Telnet, SSH

3.x

Telnet/FTP, SSH/FTP, SSH/SCP

Telnet/FTP, SSH/FTP, SSH/SCP

Terminal

Test Credentials, Ping, Traceroute, View Routes, View Arp, View Interfaces, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup, Clear Cache


http://www.askf5.com

F5 Devices



◆ The configuration file units in the package/pkgxml/F5_30/F5_R9.xml file are retrieved using a combination of SSH and SCP commands.




◆ The configuration file units in the package/pkgxml/F5_9x/F5_R9.xml file are transferred using a combination of SSH and SCP commands.




df

mount

ls

ifconfig

ping

traceroute

arp

netstat

◆ File Management

cd

cp

md5sum


grep

passwd

cat

bigstart restart snmpd

F5 Load Balancer Rev 3 239

240

F5 D
evicesMulti-config files

Multi-config files Push/ pull Pull only Type Editable Required

/etc/bigip.conf Text Yes Yes

/etc/bigd.conf Text Yes Yes

/etc/ipfw.conf Text Yes Yes

/etc/bigip.license Text Yes Yes

/etc/routes Text Yes Yes

/etc/bigconfig/openssl.conf Text Yes Yes

/etc/bigconfig/users Text Yes Yes

/etc/bigconf.conf Text Yes Yes

/etc/passwd Text Yes Yes

/etc/hosts Text Yes Yes

/etc/hosts.allow Text Yes Yes

/etc/rateclass.conf Text Yes Yes

/etc/ipfwrate.conf Text Yes Yes

/etc/snmpd.conf Text Yes Yes

/etc/snmptrap.conf Text Yes Yes

/etc/sshd_config Text Yes Yes

/etc/ssh_config Text Yes Yes

/etc/ssh_host_dsa_key Text Yes Yes

/etc/ssh_host_dsa_key.pub Text Yes Yes

/etc/ssh_host_key.pub Text Yes Yes

/etc/ssh_host_key Binary Yes

/etc/user.db Binary Yes

/etc/ipfw.filt Binary Yes

EMC VoyenceControl Device Services Support Version 12.0.0 Hotfix 6 Support Matrix

F5 Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


F5 Devices


Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access


Features available







◆ sysObjectID

• 1.3.6.1.4.1.3375.1.1



F5

BigIP HA, BigIP LB, BigIP 3-DNS, BigIP FLB, BigIP CLB, BigIP XLB, BigIP SSL

http://www.f5.com

Yes

Syslog, Traps



SSH/SCP, SSH/FTP, Telnet/FTP

Command Line

SNMP

In-Band

SSH/SCP, Telnet/FTP

SSH/SCP, Telnet/FTP

Terminal



F5 Devices



◆ SCP or FTP is used to put the pulled files back into place.


Multi-config files



/config/bigip.conf Text Yes Yes

/config/bigip_base.conf Text Yes Yes

/config/ipfw.conf Text Yes Yes

/config/bigip.license Text Yes Yes

/config/routes Text Yes Yes

/config/bigconfig/openssl.conf Text Yes Yes

/config/bigconfig/users Text Yes Yes

/etc/bigconf.conf Text Yes Yes


/etc/hosts Text Yes Yes


/etc/rateclass.conf Text Yes Yes

/etc/ipfwrate.conf Text Yes Yes

/etc/snmpd.conf Text Yes Yes

/etc/snmptrap.conf Text Yes Yes

/config/ssh/sshd_config Text Yes Yes

/config/ssh/ssh_config Text Yes Yes

/config/ssh/ssh_host_dsa_key Text Yes Yes

/config/ssh/ssh_host_dsa_key.pub Text Yes Yes

/config/ssh/ssh_host_key.pub Text Yes Yes


F5 Devices

Device data



/config/ssh/ssh_host_key Binary Yes

/config/user.db Binary Yes

/config/ipfw.filt Binary Yes


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


F5 Devices


Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands


Features available






Load Balancer

BIG-IP 1500, BIG-IP 3400

www.askf5.com (registration required)

Yes

Syslog, Traps

Multiple Complex (Linux based)


SSH, SSH/SCP

Command Line

SNMP, Terminal

1st Level ID, SNMP Read-Only, SNMP Read-Write, Terminal Only, SSH, Telnet

Operating systems for BIG-IP 1500 models: 9.1.2.40.6, 9.2.0.167.4, 9.2.4.13.1, 9.4.0.517.5Operating systems for all other models: 9.1.2 40.2

Non-SNMP

SCP

SNMP, SSH

SSH/FTP

View Interfaces, View Routes, View ARP, View Diagnostic, Resync, diffRunStart

For SNMP: Memory, Interfaces, Serial Number, Device Inventory


http://www.askf5.com

F5 Devices



◆ Standard MIB II System Values

• System Description .1.3.6.1.2.1.1.1.0 = STRING: Linux f5version9.powerupnetworks.com 2.4.21-9.1.2.37.0smp #2 SMP Tue Apr 25 15:38:38 PDT 2006 i686

• System Object ID .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.3375.2.1.3.4.4

• System Contact .1.3.6.1.2.1.1.4.0 = STRING: Richardson

◆ Custom or Vendor Specific OIDs

• Model Name .1.3.6.1.4.1.3375.2.1.3.3.1.0 = STRING: "C36"

• Model Number .1.3.6.1.4.1.3375.2.1.3.3.2.0 = STRING: "1500"

◆ For SNMP:

• sysObjectID

– 1.3.6.1.4.1.3375.2.1.3.4◆ For Terminal:

• OS version is checked using bigpipe version


The following are the commands, or processes that are used to "pull" a configuration from your device (enable/privileged mode required).

◆ The configuration files in the package/pkgxml/F5_9x/F5_R9.xml file are pulled using a combination of SSH and SCP commands.



◆ The configuration files in the package/pkgxml/F5_9x/F5_R9.xml file are pushed using a combination of SSH and SCP commands.




df

mount

ls


F5 Devices

ifconfig

ping

traceroute

apr

netstat

im

local-install

◆ File Management

cd

cp

md5sum


grep

passwd

cat

bigstart restart snmpd

Multi-config files



/config/bigip.conf Text Yes Yes

/etc/adjtime Text Yes Yes

/etc/host.conf Text Yes Yes


/etc/hosts.deny Text Yes Yes

/etc/libuser.conf Text Yes Yes

/etc/nsswitch.conf Text Yes Yes


/etc/pwdb.conf Text Yes Yes

/etc/resolv.conf Text Yes Yes

/etc/shadow Text Yes Yes

/etc/sysctl.conf Text Yes Yes


F5 Devices

/etc/security/time.conf Text Yes Yes

/etc/security/pam_env.conf Text Yes Yes

/etc/security/limits.conf Text Yes Yes

/etc/security/group.conf Text Yes Yes

/etc/security/console.perms Text Yes Yes

/etc/security/chroot.conf Text Yes Yes

/etc/security/access.conf Text Yes Yes

/var/named/config/named.conf Text Yes Yes

/var/named/config/rndc.key Text Yes Yes

/config/ucs_version Text Yes Yes

/config/ssl/ssl.crt/default.crt Text Yes Yes

/config/ssl/ssl.crt/ca-bundle.crt Text Yes Yes

/config/ssl/ssl.csr/default.csr Text Yes Yes

/config/bigip/auth/pam.d/ldap/system-auth.conf

Text Yes Yes

/config/bigip/auth/pam.d/local/system-auth

Text Yes Yes

/config/bigip/auth/pam.d/radius/system-auth.conf

Text Yes Yes

/config/bigip/auth/pam.d/other Text Yes Yes

/config/bigip/auth/pam.d/su Text Yes Yes

/config/bigip/auth/pam.d/login Text Yes Yes

/config/bigip/auth/pam.d/httpd Text Yes Yes

/config/bigip/auth/pam.d/sshd Text Yes Yes

/config/bigip/auth/pam.d/passwd Text Yes Yes

/config/bigip/auth/localusers Text Yes Yes

/config/bigip/auth/userroles Text Yes Yes

/config/ssh/ssh_config Text Yes Yes

/config/ssh/moduli Text Yes Yes

/config/ssh/sshd_config Text Yes Yes



F5 Devices


/config/httpd/conf.d/mod_auth_pam.conf

Text Yes Yes

/config/httpd/conf/workers2.properties

Text Yes Yes

/config/net-snmp/snmpd.conf Text Yes Yes

/config/snmp/subagents.conf Text Yes Yes

/config/snmp/snmpd.conf Text Yes Yes

/config/big3d/big3d.crt Text Yes Yes

/config/big3d/big3d.key Text Yes Yes

/config/big3d/big3d.pem Text Yes Yes

/config/big3d/big3d.req Text Yes Yes

/config/lcd/portinfo.txt Text Yes Yes

/config/lcd/lcdinfo.txt Text Yes Yes

/config/lcd/ledinfo.txt Text Yes Yes

/config/lcd/menus Text Yes Yes

/config/lcd/serialinfo.txt Text Yes Yes

/config/lcd/screens Text Yes Yes

/config/ntp.conf Text Yes Yes

/config/eventd.xml Text Yes Yes

/config/RegKey.license Text Yes Yes



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No


F5 Devices

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



24

Force10 Devices


◆ Force10 C-Series Router ............................................................................................. 252◆ Force10 E-Series Router.............................................................................................. 255◆ Force10 S-Series Router .............................................................................................. 258

Force10 Devices 251

Force10 Devices

Force10 C-Series Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands





◆ Credential Roll (In-Band)





◆ Model, Serial Number and Operating System version using SNMP or command line interface

◆ Filesystem and Memory using command line interface


Force10 C-Series Router

C150, C300

http://www.force10networks.com/

No

Syslog, SNMP Traps

Startup, Running




SNMP, Terminal

In-Band

FTOS v7.9



Terminal

Ping, Traceroute, View Routes, View ARP, Resync

Chassis, Card, Port, FanTray, Power, Processor, RPMs, SFModules


Force10 Devices




• show run or show start command is issued in the command line interface, and the file captured directly from the command line interface output.


• The command copy start-config tftp://[serverip]/[filename] or copy running-config tftp://[serverip]/[filename] is issued in the command line interface to transfer the file to the VoyenceControl device server.




• The command copy tftp://[serverip]/[filename] start-config or copy tftp://[serverip]/[filename] running-config are used to transfer the file directly into the device's filesystem.


• The command copy start-config tftp://[serverip]/[filename] or copy running-config tftp://[serverip]/[filename] is issued in the command line interface to transfer the file to the VoyenceControl device server.




Startup

Running


ARP Table Yes


CAM Table No


Identity Yes

Force10 C-Series Router 253

Force10 Devices

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Force10 Devices

Force10 E-Series Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Quick Commands








◆ SysObjectIDs: 1.3.6.1.4.1.6027.1.*

◆ SysDescription Contains Force10 Networks Real Time Operating System Software

◆ Force10 Enterprise MIB (1.3.6.1.4.1.6027.*)

Force10 E-Series Router

E150, E300, E600, E610, E1200


Yes

Syslog, SNMP Traps

Single Text



FTOS, SNMP Only

SNMP, Terminal

Enable, In-Band

SSH/Terminal, TFTP

SSH/Terminal, TFTP

View Routes, View ARP, Ping, TraceRoute, Resync, View Interfaces

For SNMP: Hardware Inventory, Memory, Filesystem, Interfaces, Serial Number

Force10 E-Series Router 255

Force10 Devices




• copy running-config tftp:// [device_server_ip]/[temp_filename]

• copy startup-config tftp:// [device_server_ip]/[temp_filename]

◆ For SSH and Telnet:

• show run

• show start



• copy tftp:// [device_server_ip]/[temp_filename] running-config

• copy tftp:// [device_server_ip]/[temp_filename] startup-config

◆ For SSH and Telnet deployment of the running configuration, the device is brought to the enable mode and then to configure mode, after which the configuration is entered line-by-line with checks for invalid input.

◆ The device does not support entry of a startup configuration directly from a command shell, so the driver will attempt to fallback to one of the TFTP methods listed above.

◆ To copy run to start (synchronize) the following command is executed from a shell prompt in enable mode:


Multi-config files



Device data


running

startup


Force10 Devices


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Force10 E-Series Router 257

Force10 Devices

Force10 S-Series Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands










◆ Model, serial number, and operating system version using SNMP or command-line interface.

Force10 S-Series Router

S2410CP, S2410P,S25, S25V, S25N, S25P-AC,S50, S50E, S50V, S50N-AC, S50N-DC, S50P-DC


Yes

Syslog, SNMP Traps

Startup, Running


SSH, Telnet, SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP


SNMP, Terminal

In-Band

FTOS v7.9



Terminal

Ping, Traceroute, View Routes, View ARP, Resync

Chassis, Card, Port, FanTray, Power, Processor, RPMs, SFModules


Force10 Devices

◆ Filesystem and Memory using command-line interface.

◆ Interface table using SNMP or command-line interface.



• show run or show start command is issued in the command-line interface, and the file captured directly from the command-line interface output.

◆ For SSH/TFTP or Telnet/TFTP:

• The command copy startup-config tftp://[serverip]/[filename] or copy running-config tftp://[serverip]/[filename] is issued in the command-line interface to transfer the file to the device server.

◆ For SSH/FTP or Telnet/FTP:

• The config is copied to the filesystem using copy startup-config [filename] or copy running-config [filename] and [filename] is then transferred to the device server using the router’s internal FTP server.




• A command-line interface session is started in config mode, and the config is entered line-by-line while monitoring responses for error messages.


• The command copy tftp://[serverip]/[filename] startup-config or copy tftp://[serverip]/[filename] running-config is issued in the command-line interface to transfer the config to the device from the device server.

◆ For SSH/FTP or Telnet/FTP:

• The config is copied to [filename] in the filesystem using FTP, then from a command-line interface prompt the command copy [filename] startup-config or copy [filename] running-config is entered.

Multi-config files



running

startup

Force10 S-Series Router 259

Force10 Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


25

Fortinet Devices


◆ Fortinet Fortigate Router............................................................................................ 262

Fortinet Devices 261

Fortinet Devices

Fortinet Fortigate Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands



◆ Configuration Deploy (Push Configuration)

◆ Credential Roll



◆ Model, serial number and operating system version via SNMP or command-line interface.

◆ Memory via command-line interface.

◆ Interface table via SNMP or command-line interface.

Fortinet Fortigate

300A

http://www.fortinet.com

Yes

SNMP trap, syslog

Running


SH, Telnet, SSH/TFTP, Telnet/TFTP


SNMP, Terminal

In-Band

4.0.3



Terminal

Ping, Traceroute, View Routes, View ARP, View Interfaces, exec_cfg_save


Fortinet Devices



◆ SSH or Telnet:

• show full-configuration

– The command is issued in the command-line interface.– The file is captured directly from the command-line interface output.

◆ SSH/TFTP or Telnet/TFTP

• execute backup full-config tftp [filename] [serverip]

– The command is issued in the command-line interface to transfer the file to the device server.



◆ SSH or Telnet:


• The config is entered line by line while monitoring responses for error messages.

◆ SSH/TFTP or Telnet/TFTP

• execute restore config tftp [filename] [serverip]

– The command is issued in the command-line interface to transfer the config to the device from the device server.



running

Fortinet Fortigate Router 263

Fortinet Devices

Device data




Fortinet Fortigate Router

◆ This driver was built using a model 300A appliance. Fortinet indicates that it should work with most Fortigate models (as of 9/2009).


ARP Table Yes

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory Yes


Static Routes Yes


VLANs No



26

Foundry Devices


◆ Foundry EdgeIron....................................................................................................... 266◆ Foundry Package......................................................................................................... 269

Foundry Devices 265

Foundry Devices

Foundry EdgeIron

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands



◆ Configuration Management (Revision Configuration, Basic Diagramming)




◆ sysObjectId value contains 1.3.6.1.4.1.1991.1.5.1.1.4.5.1

◆ sysDescr value contains EdgeIron

Switch

EdgeIron 48G

www.foundrynetworks.com

No

ASCII




SNMP

In-Band, SNMP

2.2.7.29



Terminal

Ping, View Interfaces

Interfaces, Serial Number, Software Version, Hardware Inventory


http://www.foundrynetworks.com

Foundry Devices



◆ show running-config

◆ show startup-config

◆ copy running-config tftp

◆ copy startup-config-tftp

Multi-config files



Device data



running

running


ARP Table No

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory No


Static Routes No


VLANs No


Foundry EdgeIron 267

Foundry Devices

Known issues


Foundry EdgeIron Switch


◆ Configuration pushes are not supported, and can crash the device used for development. The following behavior persists through firmware upgrades:

• When pushing commands using the command line interface, the device locks after a number of Invalid Syntax messages, due to a lack of exit commands (VLAN, Interface, and similar commands) for ASCII configurations.

• For TFTP, transfer is reported as successful, but the device fails to respond to any communication protocols.

• Comment characters, such as !, in the configuration cause warnings when issued using the command line interface.

• Certain configuration commands do not merge, and issue Failed to set warnings.


Foundry Devices

Foundry Package

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands




◆ Configuration Deploy (Push Config)

◆ Configuration Updates (Push Configlet, TERMlets Merges)




Discovery/identify deviceThe following items are used to provide information about your device (Host Name, Type, Vendor, Model, Operating System, and Serial Number).

◆ SysObjectID

• Layer 3 device

• 1.3.6.1.4.1.1991

Foundry Router

BigIron 4000, BigIron RX-4 Router,FastIron 400, FastIron 15000, FastIron 800, FastIron SuperX-PREM, FastIron SX 1600-PREM,IronWare,NetIron MLX Router, NetIron MLX Router, ServerIron

www.foundrynetworks.com

Yes

Single Text

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Configlet


IOS like, Command-Line Interface

SNMP


Terminal, TFTP

Terminal, TFTP

Terminal

ping


Foundry Package 269

Foundry Devices

◆ SysDescription contains Foundry Networks



• copy running-config tftp ipAddress remoteFilename

• copy startup-config tftp ipAddress remoteFilename


• skip-page

• show run or show configuration

◆ For SNMP/TFTP:

• .1.3.6.1.4.1.1991.1.1.2.1.5.0: ipAddress

• .1.3.6.1.4.1.1991.1.1.2.1.8.0: remoteFilename

• .1.3.6.1.4.1.1991.1.1.2.1.9.0: 20 (start config) or 22 (run config)




• copy tftp running-config ipAddress remoteFilename

• copy tftp startup-config ipAddress remoteFilename


• enable

• configure terminal

• commands are entered line-by-line

◆ For SNMP/TFTP:

• .1.3.6.1.4.1.1991.1.1.2.1.5.0: ipAddress

• .1.3.6.1.4.1.1991.1.1.2.1.8.0: remoteFilename

• .1.3.6.1.4.1.1991.1.1.2.1.9.0: 21 (start config) or 23 (run config)



configure terminal

copy run

copy start

disable

enable


Foundry Devices

page

ping

reload

show configuration

show run

skip-page

username

write memory

◆ File Management

tftp

copy tftp


[no] enable super-user-password


[no] username oldUser

Multi-config files




running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


Foundry Package 271

Foundry Devices

OSPF Settings No


Routes Yes



VLANs No



27

Gigamon Devices


◆ Gigamon Switch .......................................................................................................... 274

Gigamon Devices 273

Gigamon Devices

Gigamon Switch

Device Type

Specific Model(s)


Enabled By Default

Operating System

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands



◆ Configuration Management (Revision Configuration, Basic Diagramming)




◆ For SNMP:

• sysObjectID must contain 1.3.6.1.4.1.26866.

• Model must map to sysObjectID in GigamonModels.xml.

• Hostname, device properties, and interfaces must be successfully retrieved or discovery is aborted.

◆ For Terminal:

• System properties must be parsed successfully from the output of show SNMPsystem.

Switch

GigaVUE-MP

-

No

5.0.17

ASCII, Binary

Quick Commands, Termlet Merge, Privilege Mode Termlet, Command, Config

SSH/TFTP, Telnet/TFTP, Telnet, SSH


SNMP, Terminal

In-Band

SSH/TFTP, Telnet/TFTP, Telnet, SSH


Terminal

Ping, View Interfaces

Serial Number, Model, Interfaces, Inventory (Terminal Only)


Gigamon Devices

• Hostname, device properties, and interfaces must be successfully retrieved or discovery is aborted.


◆ Text:

• report running:

– config save filename– show file filename– delete filename

• report startup:

– file show (entry with nb flag is identified)– show file filename

◆ Binary:

• running:

– config save filename– upload –cfg filename– delete filename

• startup:

– file show (entry with nb flag is identified)– upload –cfg filename


◆ running:

• install –cfg filename

• config restore filename (prompt to apply: y, prompt to set nb: n)

◆ startup:

• install –cfg filename

• config file filename nb

Gigamon Switch 275

Gigamon Devices

Multi-config files





report running

report startup

running

startup


ARP Table No

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory No


Static Routes No


VLANs No



Gigamon Devices

Known issues


Gigamon Switch

◆ The following hardware information is not reported by the device; memory and file system information are disabled in the device package:

• Memory

• File system information

• Inventory (SNMP)

• IP addresses (SNMP)

◆ The model name is obtained from the device banner. If the banner is customized, this may prevent mapping to a sysObjectID value in the GigamonModels.xml, and fail device discovery via terminal protocols.

◆ If the device is completely unmanaged and later rediscovered, the startup file set for the current management instance will change. The previous file must be deleted manually after a successful push to startup following rediscovery, since the Device ID (which is part of the filename) will have changed. This approach is required due to the lack of vendor support for specifying the source and destination filenames for the install –cfg command.

◆ Configlets and remediation are not supported by this device class, since the text representation of the configuration cannot be pushed to the device, which is a preprequisite for configlet pushes.

◆ The managed device model(s) appear to only support a single read-only community string.

◆ The show diag command has been observed to disconnect communication sessions with the device after partial output. As a result, some diagnostic information that may assist with resolving missing hardware information is currently unavailable to the driver.

Gigamon Switch 277

Gigamon Devices


28

HP Devices


◆ HP ProCurve Switch................................................................................................... 280

HP Devices 279

HP Devices

HP ProCurve Switch

Device Type

Specific Model(s)


Enabled By Default

Operating System



User Interface


Password Management



Cut-Through Access



HP ProCurve Switch

J3245A ProCurve Switch 800T, J3245A ProCurve Switch 200, J4850A ProCurve Switch 5304XL, J3288A ProCurve 10/100 Hub 12M, J4865A ProCurve Switch 4108GL,J3245A ProCurve Switch 212M, J3299A, J4899A ProCurve Switch 4874A, J4899A ProCurve Switch 2650,J4120A ProCurve Switch 1600M, J4122A ProCurve Switch 2400M,J4093A ProCurve Switch 2424M, J4812A ProCurve Switch 2512, J4813A. J4899B ProCurve Switch 2650, J4900 ProCurve Switch 2626, ProCurve Switch Unknown, ProCurve Switch 2000, ProCurve Switch 2000B, ProCurve Switch 2524, ProCurve Switch A6713A, ProCurve Switch A6716A, ProCurve Switch A6717A, ProCurve Switch 4104GL, ProCurve Switch 224M, ProCurve Switch J4902, ProCurve Switch J4903A, ProCurve Switch J4904A, ProCurve Switch Proliant, ProCurve Switch J4900A, ProCurve Switch J8165A, ProCurve Switch J8164A, ProCurve Switch J8130A, ProCurve Switch J8133A, ProCurve Switch J8153A, ProCurve Switch J8154A, ProCurve Switch J8155A, ProCurve Switch J4905A, ProCurve Switch J4906A, ProCurve Switch J8718A, ProCurve Switch J8719A, ProCurve Switch J8433A, ProCurve Switch J8474A, 9308 Routing Switch, 9304 Routing Switch, 5308 Routing Switch, 6208 Routing Switch,5308XL ProCurve Switch HP Ether Switch

-

Yes

Operating systems for 2600 series models: H.10.31, H.10.35, H.10.43Operating systems for 3500-YLseries models: K.11.69, K.12.02, K.12.05Operating systems for 5300-XL series models: E.10.55, E.10.61

Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Command, Configlet


Command Line

SNMP

In-Band, SNMP

Terminal, SSH, SCP

Terminal, SSH, TFTP, SCP

Terminal

FTP, TFTP, SCP

For SNMP: Hardware Inventory, Memory, Interfaces


HP Devices

Features available








◆ SysObjectID

• 1.3.6.1.4.1.11.2.3.7.11

◆ SysDescription

• Contains ProCurve


◆ show run

◆ show config



◆ TFTP to Start (Device Reboots)


◆ Term

• Send one config line at a time

Device commands



banner

boot system flash destFlash

configure terminal

no page

show config

show flash

HP ProCurve Switch 281

HP Devices

show running

show ver

show version

terminal width

write memory

reload

ping

traceroute

◆ File Management

copy tftp


password


[no] snmpv3 group

[no] snmpv3 user

Multi-config files




running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys Yes

Memory Yes



HP Devices

Known issues


HP ProCurve 2650 - Invalid Command ip proxy-arp

◆ The configuration command for the default VLAN does not process correctly. This is an issue for all push types. A Push, using the terminal protocol, provides a warning but cannot be used for Push to Start.

This error has been ignored for pushes to the running configuration but can not be ignored for a Push to Start, using TFTP.

• HP 2650# sh ver

Image stamp: /sw/code/build/fish(ts_08_5)

May 26 2005 17:11:52

H.08.69

973

Boot Image: Primary

VLAN 1

name "DEFAULT_VLAN" untagged 1-47,50-Trk1 ip address 172.18.1.1 255.255.255.0 ip proxy-arp exit

Failed during execution

Line=exit

Error In Configuration File On Line #21

Invalid input: proxy-arp

Error: Push Failed, Pull Succeeded

HP 2650# copy start tftp 192.168.1.1 hp1

HP 2650# copy tftp start 192.168.1.1 hp1

OSPF Settings Yes


Routes Yes



VLANs Yes


HP ProCurve Switch 283

HP Devices

Device may be rebooted, do you want to continue [y/n]? y

line: 22. Invalid input: proxy-arp

HP ProCurve 2650 - Push to Start causes Reboot

◆ The device can reboot after a Push to Start.

• HP 2650# copy tftp start 192.168.1.1 hp1

Device may be rebooted, do you want to continue [y/n]? y

Rebooting switch...

The ProCurve 2650 switch may reboot after a Push to Start.

HP ProCurve

◆ The HP Switch does not support Non-SNMP Management. For manageability, ensure that SNMP is turned On.

HP Switch - Configuration Pushes

◆ Issue: Configuration pushes executed to the HP switch using the push types Push to Run and Push to Run Copy Start may fail, due to line entries within the device configuration which contain the delete command.

◆ Resolution: Remove lines from the configuration that may issue delete commands before pushing the configuration.

◆ RollBack

• When pushing a configuration to the HP switch, to remove lines from the configuration, that line must be prefixed with the word no.

• For example:

ip default-gateway 172.17.0.1

snmp-server community "public" Operator Unrestricted

snmp-server community "Cust3"

• To remove "public" you need to push the following:

ip default-gateway 172.17.0.1

no snmp-server community "public" Operator Unrestricted

snmp-server community "Cust3"

Note that the second line snmp-server community "public", Operator Unrestricted is removed by prefixing the line with no, and then pushing the configuration. For lines which contain delete, follow the same procedure.

HP ProCurve 2626 and 3500-ly

◆ Configuration management using SCP

• This capability is OS-dependent. Consult the applicable device documentation for details. For certain versions, SFTP (currently unsupported) is available, but SCP is not.

◆ OS Upgrades using SCP

• Image transfers generally succeed, but the devices fail to acknowledge the end-of-file sequence, leaving subsequent terminal sessions unable to complete the reload procedure. This can take the form of unresponsive SSH sessions or an indication that a transfer is still in progress. In some cases, the image file may also be truncated. A cold boot is the only current workaround.


29

HUAWEI Devices


◆ SmartAX ....................................................................................................................... 286

HUAWEI Devices 285

HUAWEI Devices

SmartAX

Device Type

Specific Model(s)


Operating System

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


Features available


◆ Configuration Management (revision config, basic diagramming)





◆ Model OS version and Hostname using command line interface

◆ File Systems using command line interface


Switch

MA5300

www.huawei.com

V3R000M03

Running, Startup




SNMP, Terminal

In-Band



Terminal

Ping, Traceroute, Show Routes, Show Interfaces, Show ARP

Identity, Model, Software Version


HUAWEI Devices




• running: show running-config

• startup: show startup-config'


• startup: tftp put flash:/vrpcfg.txt //remoteIpAddress/remoteFilename




• running: full configuration push is not supported (see Known Issues), but configlets are


• startup: tftp get //remoteIpAddress/remoteFilename flash:/vrpcfg.txt

Device commands



enable

disable

terminal length 0

configure terminal

write

show running-config

show startup-config

tftp put flash:/vrpcfg.txt //remoteIpAddress/remoteFilename

tftp get //remoteIpAddress/remoteFilename flash:/vrpcfg.txt

show version

ping

tracert

show ip interface

show arp all

show ip route static

reboot system

SmartAX 287

HUAWEI Devices


snmp-server community secret type [ro|rw]

no snmp-server community secret

terminal user password





Running

Startup

ARP Table Yes


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes Yes



VLANs No


HUAWEI Devices

Known issues


Huawei SmartAX

◆ Until a command line interface command is identified to determine the name of the startup configuration file, the literal name vrpcfg.txt is currently used in the driver. This will result in startup file management errors in the event Huawei changes the name of the startup file in later software releases.

◆ There does not appear to be a way to query the system for serial number or memory information.

◆ Full configuration pushes using terminal are not supported due to the content of the configuration not merging correctly from the command line interface when issued line-by-line. Some commands result in sub-levels of config prompts without corresponding exit commands, and the comment character ! does not serve this purpose. This leaves the device in a state where normally legal commands are not recognized, and the resulting errors fail the push.

◆ The concept of privilege mode with password authorization does not exist for this device class, so privilege password jobs are failed with change not supported.

SmartAX 289

HUAWEI Devices


30

Intermec Devices


◆ Intermec MobileLAN.................................................................................................. 292

Intermec Devices 291

Intermec Devices

Intermec MobileLAN

Device Type

Specific Model(s)


Operating System

Configuration Files



User Interface


Password Management


Cut-Through Access

Quick Commands




◆ Credential Management (Change Account Password, SNMP Communities)


◆ For SNMP:

• sysDescr value contains Intermec Technologies AP

◆ For Terminal:

• Banner contains Access Point Configuration

• Main menu contains About entry

• Summary screen listing WA2n as model

Wireless Access Point/Bridge

Tested: WA21Untested: WA22

www.intermec.com

2.30

ASCII (see known issues)

Quick Commands, Config

Telnet

Menu driven

SNMP

SNMP, Account

Telnet

Terminal

Standard

Model, Serial Number, Memory, Inventory


Intermec Devices



◆ Maintenance > About This Access Point

• The resulting pages are captured as a read-only information configuration.

◆ The binary configuration of the device cannot currently be retrieved.

• See the Known Issues section for this device, for more information.

Multi-config files



Device data



information

ARP Table Yes


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes Yes



VLANs No

Intermec MobileLAN 293

Intermec Devices

Known issues


Intermec MobileLAN

◆ Configlets and termlets are not supported, since the device is menu oriented with almost no command-line interface. The lack of configlets and termlets results in no remediation and diagnostic support.

◆ This device supports only one session at a time. Any session established to the device while a pull or credential roll is attempted, will cause the job to fail with a message referencing the inability to establish a session.

◆ All configuration changes, including credential rolls, require a save and reboot of the device. The current driver does this for each credential roll, as a current limitation.

◆ The TFTP PUT command fails with the message File not found, making file transfer of the binary configuration to the server unworkable. This prevents normal pull/push configuration management.

◆ ARP and Static Routes are only available using SNMP.

◆ Memory and Hardware Inventory are only available using Terminal.


31

Juniper Devices


◆ Juniper ERX (E Series) ................................................................................................ 296◆ Juniper Router ............................................................................................................. 300◆ Juniper Switch (EX Series) ......................................................................................... 304◆ Juniper EX2500 Switch ............................................................................................... 308

Juniper Devices 295

Juniper Devices

Juniper ERX (E Series)

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Operating System



Cut-Through Access


Quick Commands







Juniper ERX Series

E120, E320, ERX-310, ERX-700, ERX-705, ERX-1400, ERX-1440

http://www.juniper.net/techpubs/software/erx/

-

Syslog, SNMP Traps

Binary and Text




SNMP, Terminal

JunOSe v8.2 and 9.1

Text by means of SSH, Telnet, SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTPBinary by means of SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP

Text by means of SSH, TelnetBinary by means of SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP

Terminal

OS Upgrade using FTP

Ping, Traceroute, View Routes, View ARP, View Interfaces, View Processes, View Diagnostic, Show SNMP Delta

Chassis, Slot/Card Inventory, Interfaces, Power, Fans, FileSystems


Juniper Devices



◆ Model, Serial Number, MAC and OS version using SNMP or Command-Line Interface

◆ Filesystem and Memory using the Command-Line Interface

◆ Interface table using SNMP or the Command-Line Interface


◆ For Text config:

• show configuration

• show running-configuration

◆ For Binary config

• copy running-configuration

• copy startup-configuration

◆ The system will issue the proper command above, depending on the following.

• If the system is in manual or auto commit mode.

• If a request for the text or binary configuration is made.

◆ For TFTP and FTP protocols:

• The output of the command will be placed in a file in either the root or /outgoing directory.

• The output file is transferred using the appropriate protocol to the device server.

◆ For Telnet or SSH protocols:

• Only the first command is issued.

• The output is captured directly from the command line interface output.

◆ The Binary configuration cannot be pulled using Telnet or SSH alone.

Juniper ERX (E Series) 297

Juniper Devices



◆ For a Binary configuration:

• The configuration file will be transferred to either the root or /incoming directory using FTP or TFTP.

• The configuration file is either copied or renamed to a unique filename in the root directory and the command boot config [unique filename] is issued from the command line interface.

• The system may optionally be rebooted afterwards.

◆ For a Text configuration:

• The system will start a command line interface session, enter configuration mode, and send the file line-by-line to the command line interface session.

• Committing the configuration or restarting the device is optional, using the configuration input.


Juniper ERX systems use a rel file for operating system upgrades. The rel file contains a manifest of the additional files that make up the full operating system upgrade. During operating system upgrades the rel file is transferred to the device by the user, and the device selects which additional files are needed to complete the upgrade and automatically transfers them from the same source the rel file came from. Following are the steps for Juniper ERX operating system upgrades:

◆ Retrieve the operating system upgrade file(s) from Juniper. These files are normally distributed as a single zip file.

◆ Unzip the files and place them in a dedicated subdirectory on the operating system repository server. For example in /ERX-10-1-1.

◆ Create an operating system inventory item for the upgrade just as you normally would, with the following two exceptions:

• In Image Name, enter the subdirectory you created above, plus the name of the appropriate rel file for your model. For example, erx_10-1-1.rel, so the Image Name would be ERX-10-1-1/erx_10-1-1.rel.

• For Image Size, do not enter the size of the rel file. Enter the amount of storage that the upgrade will occupy after it is installed on the device. This number can vary depending on the exact model and options that are installed on it. You might have to estimate this number. It is advisable that you over estimate. The update will not proceed if the device does not have at least the above storage space available.

◆ Continue following normal operating system upgrade procedures.

Note: The operating system update files are pulled from the server one by one, resulting in a full operating system update taking two hours or more to complete depending on the speed and latency of the FTP link.


Juniper Devices

Multi-config files



Device data



Known issues


Juniper ERX

◆ The Binary config cannot be pushed or pulled using Telnet or SSH alone.

◆ When entering a Text config using the command line interface, any line that matches the following pattern is not sent, otherwise the command line interface session is dropped.

• no neighbor * rib-out disable

Text

Binary

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No

Juniper ERX (E Series) 299

Juniper Devices

Juniper Router

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System




Cut-Through Access







Juniper Router

A20, A40,J2300, J2320, J2350,J4300, J4320, J4350,J6300, J6350,M10, M10i, M120, M160, M20, M320, M40, M40e, M5, M7i,MX240, MX480, MX960,SRX210, SRX240, SRX3400, SRX3600, SRX5600, SRX5800, SRX650,T320, T640, T1600, TX

http://www.juniper.net/

Yes

Syslog, SNMP Traps

Formatted Text


SSH/FTP, SSH/SCP, Telnet/FTP, SSH Only, Telnet Only

JunOS Command-line Interface

SNMP, Terminal

In-Band Password, SNMP Community

v8+

Supported using FTP or SCP

Terminal, FTP, SCP

Terminal, FTP, SCP

Terminal

For SNMP: Hardware Inventory, Memory, Interfaces, Serial NumberFor Non-SNMP: Memory, Interfaces, Serial Number


Juniper Devices



◆ sysObjectID

• Must contain 1.3.6.1.4.1.2636 or show version output must contain 'JUNOS'



◆ set more paging off with set cli screen-length 0

◆ Then do show configuration

◆ For Telnet/FTP or SSH/SCP use the following command:

• Delete file using file delete voyence.cfg

• Enter configuration mode using configure command

• Save a configuration using save voyence.cfg

• Use FTP or SCP to attach and retrieve configuration file voyence.cfg



The method used to push a change to the device varies based on the content and protocol, as follows.

Content Mechanism Command Semantics

◆ Unsuccessful pushes will automatically be followed by a 'rollback 0' command.

◆ Successful pushes will, by default, automatically be followed by a commit command. This can be disabled when the job is scheduled.

◆ Optionally, a commit synchronize command may be issued following a successful push.

Configlet SSH/SCP, SSH/FTP, orTelnet/FTP

load replace(replaces based on content as issued using the editor)

With replace keyword in first line of content the configlet replaces the configuration.Without the keyword replace the content merges with the configuration.

Configlet SSH or Telnet Line-by-line Merge

Full Configuration SSH/SCP, SSH/FTP, Telnet/FTP

Load Override Override

Full Configuration SSH,Telnet Load Override Terminal Override

Juniper Router 301

Juniper Devices

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys Yes

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs Yes


Juniper Devices

Known issues


Juniper J Series

◆ In a Juniper device, the SNMP Contact and SNMP Location values must be set as alphabetical. If the SNMP Contact and SNMP Location are set with special wild card characters (such as hyphen or slash ( - , \, and others), only the information before the wild card character is displayed within the General Tab of the Device Properties.

◆ For OS Upgrade:

• During the OS upgrade process, Juniper does not allow the deletion of some files within the Temp Folder (/var/tmp). To clean the Temp Folder, manually delete any unneeded files to free up additional system space.

Juniper Router

◆ OS Upgrade:

• OS Upgrade will not upgrade a Juniper Router that has more than one routing engine.

◆ Configlets may contain config mode command-line interface commands, such as:

set snmp contact EMCcontact

set snmp location EMClocation

or formatted config snippets, such as:

snmp{

contact EMCcontact

location EMClocation

}

but must not contain both formats.

Juniper Router 303

Juniper Devices

Juniper Switch (EX Series)

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands







Juniper EX Series

EX3200, EX3200-24T, EX3200-24T-DC, EX3200-24P, EX3200-48T, EX3200-48T-DC, EX3200-48P,EX4200, EX4200-24T, EX4200-24T-DC, EX4200-24P, EX4200-24F, EX4200-24F-DC, EX4200-48T, EX4200-48T-DC, EX4200-48P, EX8208, EX8216


No

Syslog, SNMP Traps

Text


SSH, Telnet, SSH/FTP, Telnet/FTP, SSH/SCP

JunOS Command-Line Interface

SNMP, Terminal

In-Band Password, SNMP Community

JunOS v9.2 and 9.3

Text by SSH, Telnet, SSH/FTP, Telnet/FTP, SSH/SCP, Telnet

Text by SSH, Telnet, SSH/FTP, Telnet/FTP, SSH/SCP

Terminal

Supported using FTP or SCP

Ping, Traceroute, View Routes, View ARP, View Interfaces, View Processor, View Diagnostic, Clear Cache

For SNMP: Hardware Inventory, Memory, Interfaces, Serial NumberFor Non-SNMP: Memory, Interfaces, Serial Number


Juniper Devices



◆ Model, Serial Number, MAC and OS version using SNMP or the Command-Line Interface

◆ Filesystem and Memory using the Command-Line Interface

◆ Interface table using SNMP or the Command-Line Interface


◆ For Text (running) config using FTP or SCP:

• Using the command line interface configuration mode, issue the save [filename] command.

• Use FTP to transfer the configuration to the server.

◆ For Text (running) config using Telnet or SSH:

• Using the command line interface, issue the show configuration command.

• Capture the command line interface output.



◆ Using FTP or SCP:

• The configuration is transferred to the switch using FTP or SCP.

• Using the command line interface, issue the load [mode] [filename] command, where [mode] is replace for configlets and override for full configurations.

◆ Using Telnet or SSH:

• From the command-line interface in config mode, send one of the following:

– for a full config: load override terminal– for a configlet: load replace terminal– for a batch of set commands: load set terminal

• The configuration is then sent to the command-line interface session as one large text block.

• A Ctrl-D is sent to complete loading.

◆ Unsuccessful pushes will automatically be followed by a 'rollback 0' command.

◆ Successful pushes will, by default, automatically be followed by a commit command. This can be disabled when the job is scheduled.

◆ Optionally, a commit synchronize command may be issued following a successful push.

Juniper Switch (EX Series) 305

Juniper Devices

Multi-config files





Text

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys Yes

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs Yes


Juniper Devices

Known issues


Juniper EX

◆ When managing a stack of EX4200s, the system properties and hardware are shown for the master switch only.

◆ Configlets may contain config mode command-line interface commands, such as:

set snmp contact EMCcontact

set snmp location EMClocation

or formatted config snippets, such as:

snmp{

contact EMCcontact

location EMClocation

}

but must not contain both formats.

Juniper Switch (EX Series) 307

Juniper Devices

Juniper EX2500 Switch

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







Swtich

EX2500


Yes

Syslog, SNMP Traps

Running, Active, Backup


SSH, Telnet, SSH/TFTP, Telnet/TFTP, SSH/SCP


SNMP, Terminal

Account, SNMP

EX2500 OS v3.0+



Terminal

Ping, Traceroute, View Routes, View ARP, View Interfaces, View Processor, View Diagnostic, Clear Cache

Memory, Interfaces


Juniper Devices



◆ Model, Serial Number, MAC, OS version, Memory, and Interfaces using SNMP or the Command-Line Interface




• The command show (running|active|backup)-config is entered in the command-line interface, and the output is captured.

◆ Using Telnet/TFTP or SSH/TFTP:

• To transfer the file to the device server, enter the command copy (running|active|backup)-config tftp://[serverip]/[filename] in the command-line interface.




• A command-line interface session is started and brought to config mode

• The configuration is sent to the command-line interface session line by line and each response is checked for error responses.

• The running config can only be deployed using Telnet or SSH.

◆ Using Telnet/TFTP or SSH/TFTP:

• To transfer the config from the device server directly to the selected config, tThe command copy tftp (running|active|backup)-config://[serverip]/[filename] is entered in the command-line interface.

• The running config cannot be deployed using Telnet/TFTP or SSH/TFTP.

◆ The command copy running-config active-config can optionally be issued following the configuration deployment.

Multi-config files



Running

Active

Backup

Juniper EX2500 Switch 309

Juniper Devices

Device data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Juniper Devices

Known issues


Juniper EX2500 Switch

◆ When sending a config line by line using Telnet or SSH, sending an ip-mgmt interface address command causes the immediate dropping of the terminal session.

• The driver intentionally filters out any configuration line that starts with ip-mgmt interface address when sending in line by line mode.

◆ When sending a config line by line using Telnet or SSH, it is unknown whether commands that change passwords are processed correctly, since password commands in the command-line interface are normally interactive.

• Any job that sends a password command in line by line mode will receive a warning message. The command is sent, but the job result will note that the command may not process correctly. This is a known Juniper issue.

◆ The Juniper EX2500 local AAA system only supports 10 user accounts. If the new user does not already exist when rolling users and passwords, the driver will attempt to reuse the old user account if it exists. If the old user account does not exist, the driver will look for an available user account. If there are no available user accounts, no changes will be made and the job will fail.

◆ The Juniper EX2500 has console logging enabled by default. It is advisable to permanently turn off console logging on any Juniper EX2500 devices that will be managed by this application, since the device sends console messages during the login procedure. During testing, the driver managed to login despite these console messages, but the messages slow down the login procedure dramatically. For best performance, turn off console logging permanently using the following commands:

configure terminal

no logging console

end

save running-config startup-config

Juniper EX2500 Switch 311

Juniper Devices


32

Laurel Devices


◆ Laurel ST Router.......................................................................................................... 314

Laurel Devices 313

Laurel Devices

Laurel ST Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access







◆ sysObjectId

• Contains 1.3.6.1.4.1.5395.1.1.1.1.1

◆ sysDescr

• Contains Laurel

Router

ST200

-

No

Single ASCII


SSH/SCP


SNMP

In-Band, SNMP

3.1.1R2.1

SSH/SCP

SSH/SCP

Terminal

Interfaces, Serial Number, OS Version, Inventory


Laurel Devices



◆ show configuration | save vc-running.txt

• File vc-running.txt is transferred using SCP to the server.

◆ file delete vc-running.txt



◆ File push-configType-deviceId.cmd is transferred using SCP to the device

◆ configure

◆ run test configuration push-configType-deviceId.cmd

◆ If no errors occur, load merge push-configType-deviceId.cmd

◆ If successful, commit confirm

◆ file delete push-configType-deviceId.cmd

◆ commit

Multi-config files




running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


Laurel ST Router 315

Laurel Devices

Known issues


Laurel ST Router

◆ Config mode intentionally displays an error if any other session is in configuration mode. This avoids unrelated commits when multiple users are provisioning.

◆ Push to running with copy to start is the only push type, as commits must always be completed otherwise the changes are rolled back after 10 minutes.

◆ Configlets cannot contain {}'s in their content, as this distinguishes them from full configs in the driver.

• Configlets are sent line-by-line to the command line interface.

• Full configurations are copied, checked, and then applied using load merge filename.

◆ Account credential rolls change only the password, not the user.

◆ There is no volatile or non-volatile storage information available using SNMP for this device class.

OSPF Settings No


Routes Yes



VLANs No



33

Lucent Devices


◆ Lucent Access Point .................................................................................................... 318

Lucent Devices 317

Lucent Devices

Lucent Access Point

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access








◆ sysDescr

• contains Lucent Access Point



◆ gen-script all

◆ Add system file-transfer-info.8 source dest NVRAM

Lucent Access Point

300, 450, 600, 1000 (only 300 and 450 have been tested)

www.alcatel-lucent.com

No

Single Text

Termlet Merge, Privilege Mode Termlet, User Mode Termlet

SSH Only, Telnet Only

Command Line

SNMP

In-Band, SNMP

Terminal, SSH, SSH/SCP, Terminal/FTP

Terminal, SSH

Terminal



Lucent Devices



◆ Configs can be pushed using SSH/Telnet, SCP, or TFTP

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Lucent Access Point 319

Lucent Devices


34

Marconi Devices


◆ Marconi ASX ................................................................................................................ 322

Marconi Devices 321

Marconi Devices

Marconi ASX

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands


Features available







◆ sysObjectId

• .1.3.6.1.4.1.326.2.2

◆ sysServices

• Bit 2 set

Switch

ASX-1000

http://www.marconi.com/

No

SNMP Traps, Syslog

ASCII (Config Representation), Binary (Backup/Restore)


Telnet/TFTP


SNMP

In-band, SNMP

7.0.0

Telnet/TFTP

Telnet/TFTP

Telnet

Ping, View Routes, View ATM ARP, View LEC ARP, View Interfaces

Interfaces, Serial Number, OS Version


Marconi Devices



◆ Running

• system cdb backup -url tftp:// deviceServerAddr/remoteFilename

◆ Readable

• batch create -url tftp:// deviceServerAddr/remoteFilename



◆ Backup and Restore are only available for full configs.

◆ Binary

• system cdb restore -url tftp:// deviceServerAddr/remoteFilename

Device commands

The following device command sets must be enabled to allow VoyenceControl NG to manage this device class.


system cdb [ backup | restore ]

system ping

interfaces ip show

interfaces ip route show

services atmarp show

interfaces lec arp show


security login [ new | delete | password ]

password



readable

running

Marconi ASX 323

Marconi Devices

Device data




Marconi ASX


◆ Serial number falls uses the primary MAC address if the envMgmtBoardSerialNumber OID in the Fore-SWITCH-MIB is unavailable.

◆ The binary configuration is represented as base64-encoded data in the Config Editor, allowing support for configlet pushes for this destination.

◆ The read/write community string is given the Admin profile during creation.


ARP Table No

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory No


Static Routes No


VLANs No



35

McAfee Devices


◆ McAfee IntruShield..................................................................................................... 326

McAfee Devices 325

McAfee Devices

McAfee IntruShield

Device Type

Specific Model(s)


Enabled By Default




User Interface


Password Management

Operating System


Cut-Through Access







◆ sysObjectId

• Contains 1.3.6.1.4.1.8072.3.2.10



◆ show

◆ show ssl config

◆ show tacacs

Other

I4000

www.mcafee.com

No

Configlet, Termlet Merge, Termlet Privilege Mode

Telnet, SSH

Telnet, SSH


SNMP

In-Band

4.1.1.49

Telnet, SSH

Terminal

Serial Number, OS Version, Interfaces, Inventory


McAfee Devices

Multi-config files





running

ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

McAfee IntruShield 327

McAfee Devices

Known issues


McAfee IntruShield

◆ There is no volatile or non-volatile storage information available using SNMP for this device class.

◆ SNMP credential management must be performed with McAfee's ISM server. An error message will display if credential management is attempted through VoyenceControl.

◆ The device class does not support the concept of configuration push. The output for the following commands contains all the data and cannot be edited:

◆ show

◆ show ssl config

◆ show tacacs


36

Milan Devices


◆ SM801P Managed Switch........................................................................................... 330

Milan Devices 329

Milan Devices

SM801P Managed Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access




Features available








◆ System Object ID

• enterprises.835.25.1.1.1.1

Milan

SM801P, SME801P

http://www.milan.com

No

Single, Binary

Quick Commands, Termlet Merge, Privilege Mode Termlet, User Mode Termlet, Config

HTTP/TFTP, SSH Only, Telnet Only, SNMP/TFTP, Non-SNMP

Menu Driven, Web Based

SNMP

In-Band, Terminal

SM801P-V117, SM801P-V118, SME801P-V200

Terminal, SNMP

Terminal, SNMP

Telnet Only

HTTP/TFTP

View VLAN, Device Uptime, Device Info

For SNMP: Hardware Inventory, Serial Number, Model, OS VersionFor Non-SNMP: Serial Number, Model, OS VersionFor HTTP: Supplemental, Serial Number, Model, OS Version


Milan Devices

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No

SM801P Managed Switch 331

Milan Devices


37

Motorola BSR


◆ Motorola BSR Router .................................................................................................. 334

Motorola BSR 333

Motorola BSR

Motorola BSR Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands


Features available




◆ Credentials Management (In-Band, SNMP)



◆ sysObjectID MIB scalar is retrieved and checked for the RiverDeltaNetworks enterprise value (4981):

• The value is used as an enumeration to identify the product, documented in $VOYENCE_HOME/package/pkgxml/ MotoBSRChassisTypes.xml.

• If the resulting product name is longer than one character, and sysServices MIB scalar has bit 3 set, discovery is successful.

Router

BSR64000 (BSR1000 and OSR2000 may be supported; unverified)

Customer Supplied

No

running, startup

ASCII

Telnet, SSH, TFTP

Command-Line

SNMP

In-Band, SNMP

3.1.1.14P03C.KRCU4.2.0.08P07.H20.KRCU

Terminal, TFTP

Terminal

Terminal

TFTP

View Interfaces, View Routes, Ping, Traceroute, View ARP, Clear Interface Counters, View Processor CPU, Resync

Memory, Non-Volatile Storage, Card Inventory


Motorola BSR


The following are the commands, or processes that are used to "pull" a configuration from your device (enable/privileged mode required).

◆ Using Terminal:



◆ Using file transfer (untested):

• copy running-config tftp:

• copy startup-config tftp:


◆ Using Terminal (Telnet/SSH):

• Configuration commands are issued interactively.

◆ Using File Transfer:

• Configuration is pushed to running or startup.

Device commands



boot system

enable [secret]

configure

page [off|on]

show running-config

show startup-config

show boot

show chassis

show process

show update

show version

update chassis

ping

traceroute

show arp

show ip route

Motorola BSR Router 335

Motorola BSR

show interface brief

traceroute

◆ File Management

copy [tftp:]

delete

dir


[no] snmp-server

[no] username

password telnet

Multi-config files



Device data


running

startup


ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No


Motorola BSR



VLANs No


Motorola BSR Router 337

Motorola BSR


38

MRV Devices


◆ MRV LX Terminal Server ........................................................................................... 340

MRV Devices 339

MRV Devices

MRV LX Terminal Server

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands









◆ SNMP SysDescr

◆ Model from SysObjectIDs: 1.3.6.1.4.1.33.100.1.2.1.*

◆ S/N at .1.3.6.1.2.1.2.2.1.6.1

◆ OS at .1.3.6.1.4.1.33.100.1.1.4.0


◆ Enterprise MIB at .1.3.6.1.4.1.133

MRV LX Terminal Server

All LX Series Models

http://service.mrv.com/support/index.cfm

No

Syslog, SNMP Traps

Text (running config only)

Quick Commands, Configlet Termlet, Command, Config


CLI, SNMP

SNMP

In-Band



Terminal

Ping

Power Supplies, Character Ports, Ethernet Ports, Interfaces


MRV Devices




• save configuration network [filename] [serverIP]




• load configuration from network [filename] [serverIP]



Device data


running


ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes No

MRV LX Terminal Server 341

MRV Devices



VLANs No



39

NetCache Devices


◆ NetCache ...................................................................................................................... 344

NetCache Devices 343

NetCache Devices

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


NetCache







NetCache

C1200

www.netapp.com

No

Syslog, SNMP Traps

Single Text


SSH Only, Telnet Only

CLI

SNMP Only

In-Band, SNMP

Text Capture by means of show config

Text CLI by means of Telnet or SSH

Terminal

System Config

Hardware Inventory, Interfaces, Serial Number, Model, OS Version, Hardware Information

running


NetCache Devices

Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

NetCache 345

NetCache Devices


40

Netopia Devices


◆ Netopia R7000 Series .................................................................................................. 348

Netopia Devices 347

Netopia Devices

Netopia R7000 Series

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands







◆ sysDescr

• Contains Netopia and one of the following: R7200, R7220, or R7231


◆ Utilities and Diagnostics

◆ Trivial File Transfer protocol (TFTP)

◆ SEND CONFIG TO SERVER

Netopia Router

R7000 series

http://www..netopia.com/

Yes

Binary

Termlet Merge

Telnet/TFTP, Telnet Only

Menu Driven

SNMP

In-Band, SNMP

TFTP

TFTP

Terminal, ANSI

Ping, TraceRoute



Netopia Devices



◆ Utilities and Diagnostics

◆ Trivial File Transfer protocol (TFTP)

◆ GET CONFIG FROM SERVER



Device data



running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Netopia R7000 Series 349

Netopia Devices


41

NetScreen Devices


◆ NetScreen Firewall ...................................................................................................... 352

NetScreen Devices 351

NetScreen Devices

NetScreen Firewall

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access








NetScreen

NS5, NS10, NS100, NS1000, NS500, NS50, NS25, NS204, NS208, NS5XT, NS5XP, NS5000, NS5GT, HARDWARESECURITYCLIENT ISG2000, NS5GT-ADSL-ANNEXA, NS5GT-ADSL-ANNEXB, NS5GT-WLAN, NS5GT-ADSL-ANNEXA-WLAN, NS5GT-ADSL-ANNEXB-WLAN, ISG1000,SSG5, SSG5-ISDN, SSG5-V92, SSG5-WLAN, SSG5-ISDN-WLAN, SSG5-V92-WLAN, SSG20, SSG20-WLAN, SSG-520, SSG-550, SSG-140, SSG-250, SSG-320M, SSG-350

www.juniper.net

Yes

Syslog, SNMP Traps

Single Text


SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, Non-SNMP

Command Line, Web-Based

SNMP, Terminal, SSH

In-Band, SNMP

OS Upgrade

Terminal, SSH, TFTP

Terminal, SSH

Terminal



NetScreen Devices



◆ SysObjectID

• 1.3.6.1.4.1.3224.1.*



◆ TFTP:

• get config > tftp ") SERVERIPADDR tftpFile(configFile.filename)+"\n")

◆ NetScreen Pull only supports Term/TFTP



◆ NetScreen supports Terminal Pushes, one config line at a time

◆ NetScreen also supports TFTP push using the command: save config from tftp




running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

NetScreen Firewall 353

NetScreen Devices

Known issues


NetScreen ScreenOS - Variable Names

◆ In NetScreen ScreenOS version 5.0, the SNMP sysName variable may not display the actual system hostname on the device. In version 5.0, the SNMP sysNAME variable is not updated when the value is changed on the device. This issue does not apply to NetScreen ScreenOS version 4.0.

◆ For the SNMP to display the correct system hostname, the configuration line must be set correctly with the following syntax: set snmp name "<hostname>".

◆ Get OS Quick Command

• This View Processor CPU command is not supported in the NetScreen ScreenOS versions, up to and including, version 4.X.

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



42

Nokia Devices


◆ Nokia IP ........................................................................................................................ 356

Nokia Devices 355

Nokia Devices

Nokia IP

Device Type

Specific Model(s)


Enabled By Default


Other Unique Information

Configuration Files



User Interface


Password Management



Cut-Through Access



Features available







Nokia IPSO Firewall

IP260, IP265, IP350, IP355, IP380, IP385, IP390, IP45, IP560, IP1220, IP1260, IP2255

http://www.nokia.com

Yes

Syslog, SNMP Traps

Unix like operating system


Command, Config, Privilege Mode Termlet, Termlet Merge, Operating System, Device Setting

SSH/SCP, SSH/FTP, Telnet/FTP

Command Line

SNMP

In-Band, SNMP



Terminal

Test Credentials, Setup Diagnostic, View Diagnostic Setup, Ping, Traceroute, View Interfaces, View ARP, View Routes, Setup NAT, View NAT Setup



Nokia Devices



◆ Custom or Vendor Specific OIDs

• .1.3.6.1.4.1.94.1.21.1.1.1.0

– 7H055101054– Discovery is done using SNMP using the string 'IPSO' in MIB-11's sysDescr

scalar– Chassis Serial Number is obtained first from ENTITY-MIB, and if it fails,

the IPSO Chassis is the Serial Number in NOKIA-IPSO-SYSTEM-MIB• 1.3.6.1.4.1.2620.1.1.10.0

– FireWall-1


◆ The files listed in the Multi-Config Files section for this device are pushed usingusing a combination of SSH and SCP commands.


◆ Use the Unix file commands to put the files back into place.




clish -c 'add snmp community …'

clish -c `copy …'

reboot

ifconfig

ping

traceroute

arp

netstat

◆ File Management

mkdir

Nokia IP 357

Nokia Devices

cp

ls


dbpasswd



$base_dir/conf/netso.C Text Yes

$base_dir/conf/objects.C Text Yes Yes

$base_dir/conf/InternalCA.C Text Yes Yes

$base_dir/conf/snmp.C Text Yes Yes

$base_dir/conf/SDS_objects.C Text Yes

$base_dir/conf/classes.C Text Yes Yes

$base_dir/conf/lea_server_unification_scheme.C

Text Yes Yes

$base_dir/conf/log_unification_scheme.C Text Yes

$base_dir/conf/newobjects.C Text Yes

$base_dir/conf/refs.C Text Yes Yes

$base_dir/conf/tables.C Text Yes Yes

$base_dir/conf/userdef.C Text Yes Yes

$base_dir/conf/cpha.conf Text Yes Yes

$base_dir/conf/cphaprob.conf Text Yes Yes

$base_dir/conf/cpmap_config.conf Text Yes

$base_dir/conf/cpmap_opsec.conf Text Yes

$base_dir/conf/cpmap_rulebase.conf Text Yes

$base_dir/conf/cp.lf Text Yes Yes

$base_dir/conf/product.conf Text Yes Yes

$base_dir/conf/fwauthd.conf Text Yes Yes

$base_dir/conf/fwopsec.conf Text Yes Yes


Nokia Devices


$base_dir/conf/slapd.conf Text Yes

$base_dir/conf/smtp.conf Text Yes Yes

$base_dir/conf/omi.conf Text Yes

$base_dir/conf/thresholds.conf Text Yes

$base_dir/conf/fwmusers Text Yes Yes

$base_dir/conf/gui-clients Text Yes Yes

$base_dir/conf/external.if Text Yes

$base_dir/conf/cp.license Text Yes

$base_dir/conf/masters Text Yes Yes

$base_dir/conf/*.W Text Yes Yes

/config/active Text Yes Yes

$base_dir/state/* Binary Yes

$base_dir/conf/serverkeys.* Binary

$base_dir/database/* Binary Yes

$base_dir/conf/fwauth.NDB Binary Yes

$base_dir/conf/fwauth.keys Binary

$base_dir/conf/rulebases.fws Binary

$base_dir/conf/cp.license Text Yes Yes

$base_dir/conf/sic_policy.conf Text Yes Yes

$base_dir/database/cprid/cprid_keys/* Binary

$base_dir/database/cprid/cprid_util_keys/* Binary



ARP Table Yes


CAM Table No


Nokia IP 359

Nokia Devices

Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



43

Nortel Devices


◆ Nortel Alteon ............................................................................................................... 362◆ Nortel Alteon 2400 ...................................................................................................... 365◆ Nortel Router ............................................................................................................... 367◆ Nortel Baystack............................................................................................................ 370◆ Nortel BoSS Switch ..................................................................................................... 372◆ Nortel Contivity .......................................................................................................... 375◆ Nortel Multi-Service Switch ...................................................................................... 377◆ Nortel Passport ............................................................................................................ 380◆ Nortel Passport 8600 ................................................................................................... 382◆ Nortel 4500 Switch ...................................................................................................... 385

Nortel Devices 361

Nortel Devices

Nortel Alteon

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface




Cut-Through Access

Quick Commands


Features available







◆ Discovery using SNMP

◆ SysDecr contains one of the following:

• Alteon

• Nortel Application Switch

Load Balancer

184, 180e, 2208, 2216, 2216 E, 2424, 2424 SSL, 3408 AD3, AD4, ASF-5009-x305, iSD SSL

http://www.nortel.com/

Yes

Startup, Running Text


SSH/TFTP, Telnet/FTP, SSH, Telnet, SNMP/TFTP


SNMP



Terminal

Ping, Traceroute, View Interfaces, View ARP, View Routes

Memory, Interfaces, Serial Number, OS Version


Nortel Devices



◆ Telnet/SSH:

• /cfg/dump

◆ Telnet/TFTP and SSH/TFTP:

• /cfg/ptcfg tftpIpAddress remoteFilename -tftp -mgmt

◆ SNMP/TFTP:

• The driver tests for ALTEEON-TIGON- or ALTEON-CHEETAH-MIB support and uses corresponding MIB values to pull the configuration.



◆ Telnet/SSH:

• Commands are issued to the command line interface and the results are scanned for errors.


• /cfg/gtcfg tftpIpAddress remoteFilename -tftp -mgmt

◆ SNMP/TFTP:

• The driver tests for ALTEEON-TIGON- or ALTEON-CHEETAH-MIB support and uses corresponding MIB values to push the configuration.



Device data


running


ARP Table Yes


CAM Table No


Identity Yes

Nortel Alteon 363

Nortel Devices


Nortel Alteon

◆ No restrictions are enforced on password length.

◆ For terminal pushes, the script configuration line is skipped.

◆ Configuration management using SSH/TFTP or Telnet/TFTP exhibits problems for push, depending on OS version.

• For example, the Main menu is displayed and Error: Successful is reported, but the configuration changes are ignored.

◆ Depending on the running software version, the following commands generate errors and must be removed or commented out for a push to be successful using terminal.

• tnet ena

• /cfg/sys/sshd/ena

• /cfg/sys/sshd/on

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Nortel Devices

Nortel Alteon 2400

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface




Cut-Through Access

Quick Commands







◆ Discovery using SNMP

• sysDescr contains Alteon or Nortel, followed by Application Switch 24


◆ Telnet/SSH

• /cfg/dump

◆ Telnet/TFTP and SSH/TFTP

• /cfg/ptcfg tftpIpAddress remoteFilename -tftp -mgmt

Load Balancer, Firewall

2424


Yes

Startup, Running Text

Termlet Merge, User Mode Termlet

SSH/TFTP, Telnet/FTP, SSH Only, Telnet Only, SNMP/TFTP

CLI

SNMP

Telnet, SSH

Telnet, SSH

Terminal

Test Credentials, Diagnostics, NAT Configuration, View Interfaces, View ARP, View Routes


Nortel Alteon 2400 365

Nortel Devices



◆ Telnet/SSH:

• Commands are issued to the CLI and the results scanned for errors


• /cfg/gtcfg tftpIpAddress remoteFilename -tftp -mgmt

Known issues


Nortel Alteon 2400

◆ Configuration management using TFTP has shown problems for push, and is currently disabled. Configuration changes are ignored, even if the main menu is displayed and an Error: Successful message is displayed.

◆ The script configuration line is skipped in terminal pushes.

◆ The following commands have been observed to generate errors, and must be removed or commented-out for a push to be successful using Terminal.

• tnet ena

• /cfg/sys/sshd/ena

• /cfg/sys/sshd/on

◆ Restrictions on password length are not enforced.


Nortel Devices

Nortel Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands









◆ Model OID

• .1.3.6.1.4.1.18.3.1.1.1.0

◆ OS Version

• retrieved from sysDescr

Router

AN, ARN, BCN, BLN, BLN, ASN, Passport 2430, Router 5580, Router 5430


Yes

Single Text, Binary

Command, Config, Configlet, Privilege Mode Termlet, Termlet Merge, User Mode Termlet

Telnet/FTP, Telnet Only

Command Line, Menu Driven

SNMP

In-Band, SNMP

15.4.0.1, 15.4.0.2, 15.4.2.6

Terminal, FTP

Terminal, FTP

Terminal

OS Upgrade

Test Credentials, Ping, View ARP, View Memory, View Routes, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup


Nortel Router 367

Nortel Devices



◆ Term pull

• more off

• show config -all

◆ FTP pull

• Term login and determine directory

• Standard FTP using the directory number


◆ Term push

• Pushes the config one line by line

◆ FTP push

• Term login and determine directory

• Standard FTP put using directory number




binary config

text config

config report


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes


Nortel Devices

Known issues


Nortel ARN - Pushing Command using Configlet

◆ Issue: Pushing Command using Configlet is displaying as completed with a warning message when the Push type is Push to Run.

◆ Resolution: Config pushes to the ARN must be executed using the Telnet mechanism. The configuration, which is modified and pushed, must be a configuration pulled using Telnet.

An ARN config pulled using Telnet, can be edited, and will not have binary data displayed at the bottom of the configuration.

A configuration pulled using Telnet/TFTP, will have the text string <VoyenceControl_Config_file><FilePath>Text Config</FilePath><humanReadable editable="false"<>![CDATA[ displayed at the top of the configuration, and will have binary data present at the end of the configuration.

This configuration can not be edited, as indicated by the humanReadable editable="false" string.

The Telnet/TFTP config should be pushed back to the ARN device for rollback only.

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Nortel Router 369

Nortel Devices

Nortel Baystack

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands


Features available







◆ OS version

• Retrieved from sysDescr

Nortel Baystack Switch

Tested: 450, 410 350, 350-12T, 380-24FUntested: 2550T, 2550T-PWR,3510-24T, 4524GT, 4526FX, 4526GTX, 4526GTX-PWR, 5650TD


Yes

Syslog, SNMP Traps

Binary

Command, Config, Privilege Mode Termlet, Termlet Merge, User Mode Termlet


Menu Driven

SNMP

In-Band, SNMP

4.0.2.2, 4.4.0.6, 4.5.1.1

Terminal, TFTP

Terminal, TFTP

Terminal

OS Upgrade

Test Credentials, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup



Nortel Devices

◆ Serial number OID

• .1.3.6.1.4.1.45.1.6.3.1.6.0



Device data



binary config

text config

snmp config

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes

Nortel Baystack 371

Nortel Devices

Nortel BoSS Switch

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands









◆ OS Version

• From sysDescr

Nortel Baystack BPS 2000 Switch

BPS 2000 and Baystack 470


Yes

Syslog, SNMP Traps

Binary

Command, Config, Privilege Mode Termlet, Termlet Merge


Command Line, Menu Driven

SNMP

In-Band, SNMP

3.1.4.11, 3.6.03, 3.5.0.58

TFTP

TFTP

Terminal

OS Upgrade




Nortel Devices



◆ Copy config tftp address <server ip> filename <pull filename>



◆ Copy tftp config address <server ip> filename <pull filename>

Multi-config files



Device data


binary config

text config

snmp config

Atributed data Support

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes

Nortel BoSS Switch 373

Nortel Devices



VLANs Yes



Nortel Devices

Nortel Contivity

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







◆ sysObjectID is used to determine the various models

Nortel VPN

6001000, 1010, 1050, 1100, 15XX 1600, 1700, 1740, 1750,2000, 2500, 2600, 2700, 4500, 4600


Yes

Binary

Command, Config, Configlet, Privilege Mode Termlet, Termlet Merge, User Mode Termlet

SSH/FTP, Telnet/FTP, SSH Only, Telnet Only

Command Line

SNMP

In-Band, SNMP

4_70.119

Terminal, FTP

Terminal, FTP

Terminal



Nortel Contivity 375

Nortel Devices

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Nortel Devices

Nortel Multi-Service Switch

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access


Quick Commands








74801500020000Nortel Carrier Passport


Yes

SNMP Traps, Syslog

Multiple Text, Binary


Telnet/FTP

CLI

SNMP, Terminal

In-Band, SNMP

Telnet/FTP

Telnet/FTP

Terminal

OS Upgrade

Test Credentials, Diagnostics, Ping, OS Update, Acknowledge Prov, Confirm Prov, Save Prov, Commit Prov, NAT Configuration

SNMP, Terminal: Hardware Inventory, Memory, Interfaces, Serial Number, Hardware Information

Nortel Multi-Service Switch 377

Nortel Devices



◆ SNMP:

• SysDescr contains Carrier Passport

• SysObjectID matches 1.3.6.1.4.1.562

• SysServices Layer 2 and Layer 3

◆ Terminal:

• system name is extracted from display -noTabular Mod Nodename: must have nodename = name content

• chassis serial number is derived from display -noTabular Vr/ Ip If/: must have hardwareAddress = value; the : characters are removed and the remaining content is used as-is

Multi-config files



Device data


running

startup


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes


Nortel Devices

Known issues


Nortel Multi-Service Switch

◆ Chassis serial number using terminal may change based on hot-sparing behavior for control processor switchover, since it is based on the hardwareAddress information of the active CP

◆ Model information using terminal is based on the following criteria:

• display -noTabular Shelf shelfType is fabricBasedShelf for Passport 15000 and 20000, and busBasedShelf for Passport 7400

• display -noTabular Shelf slotConfiguration is 40G for Passport 15000

◆ O/S version using terminal depends on the base_ naming convention of the software distribution in the output of the display -noTabular Sw avl command



VLANs No


Nortel Multi-Service Switch 379

Nortel Devices

Nortel Passport

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface




Cut-Through Access

Quick Commands







◆ The OSI layer 3 bit (0x04) is set in sysServices

◆ sysObjectID

• Contains 1.3.6.1.4.1.2272.43.


◆ upload configuration <server IP> <filename>

Nortel Router, Nortel Switch

1648T


Yes

Syslog, SNMP Traps

Binary

Command, Config, Privilege Mode Termlet, Termlet Merge, User Mode Termlet

Telnet/TFTP

Command Line

SNMP

TFTP

TFTP

Terminal




Nortel Devices



◆ download configuration <server IP> <filename>

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Nortel Passport 381

Nortel Devices

Nortel Passport 8600

Device Type

Specific Model(s)8106, 8110, 8310, 8603, 8606, 8610


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands


Features available






Routing Switch

1050, 1200, 1250


Yes

Syslog, SNMP Traps

Single Text

Command, Config, Configlet, Privilege Mode Termlet, Termlet Merge


Command Line

SNMP

In-Band, SNMP

3.5.1.0, 3.5.3.0, 3.7.2.0

Terminal, TFTP

Terminal, TFTP

Terminal

OS Upgrade

Test Credentials, Ping, Traceroute, View Sys Info, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup



Nortel Devices



◆ OS Version: From sysDescr

◆ Serial number OID: .1.3.6.1.4.1.2272.1.4.2.0

◆ Model: Retrieved from sysObjectID


Terminal mode uses show config.

TFTP pull is possible using the copy command.


◆ Terminal mode pushes the config one line-by-line.

◆ TFTP push is possible using the copy command.

Multi-config files



Device data


running

startup

boot.cfg


ARP Table Yes


CAM Table No


Identity Yes

Nortel Passport 8600 383

Nortel Devices


Nortel Passport 8600 - Syntax/Constraint Violations

◆ Passport configurations may contain syntax or other constraint violations that prevent the configuration from being pushed to the device. These syntax constraint violations are part of the configuration retrieved from the device. Be aware you may have to correct the constraint violations when configuration pushes occur.

The Schedule Manager shows the last ten lines of the configuration push, including the devices response to aid in this effort.

Nortel Passport 8600 - Unable to Config Push to Nortel Passport 8600

◆ Some of the commands in the Nortel Passport 8600 device require privileged permission to modify. Access using the RWA (Read Write All) account is required. If one attempts to push the running config with a lower privileged account (e.g. Manager) the push will fail.

For example the mac-flap-time-limit is a privileged command and attempting to push it causes the Nortel Passport 8600 device to give a Permission Denied error.

Nortel Passport 8100 - Config Push fails

◆ Issue: When executing a configuration push to the Nortel Passport 8000 Series device, the configuration push may not be successful due to lines present in the device configuration that are not valid configuration commands for the device.

◆ Resolution: Determine the correct device configuration command for that particular configuration entry, and then push this command using the Configlet Editor.

◆

◆

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Nortel Devices

Nortel 4500 Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands





◆ Credentials Management (Change Passwords, Roll Passwords, SNMP Communities)

Switch

Tested: 4550TUntested: 2526T, 2526T-PWR, 4526T-PWR, 4550T-PWR, 4548GT, 4548GT-PWR


Yes

ASCII, Binary

Quick Commands, Termlet Merge, Privilege Mode Termlet, Command, Configlet, Config


Command-line Interface

SNMP, Terminal

Account, SNMP

5.1.2.004



Terminal

Ping, View Interfaces, Vioew Routes, View ARP

Identity, Model, Software Version, Serial Number, Interfaces, Inventory

Nortel 4500 Switch 385

Nortel Devices



◆ SNMP:

• sysDescr and sysObjectID oind must be accessible from the device agent

• sysDescr must contain Ethernet Routing Switch

• sysObjectID must map to a model in NortelSwitch4500.models

• IF-MIB and optionally IP-MIB must be supported by the device agent

◆ Terminal:

• the session banner must contain the model name as well as Ethernet Routing Switch

– Model name must map to a sysObjectID fragment in NortelSwitchModels.xml

• the show ip and show interfaces verbose commands must return usable output



◆ ASCII:

• copy running-config tftp address remoteIpAddr filename remoteName

◆ Binary:

• copy config tftp address remoteIpAddr filename remoteName



◆ ASCII:

• configure network address remoteIpAddr filename remoteName

◆ Binary:

• copy tftp config address remoteIpAddr filename remoteName


Nortel Devices

Device commands



• terminal length 0

• terminal width 132

• show system verbose

• show tech

• show ip

• show interfaces verbose


• copy running-config tftp address remoteIpAddr filename remoteName

• copy config tftp address remoteIpAddr filename remoteName

• configure network address remoteIpAddr filename remoteName

• copy tftp config address remoteIpAddr filename remoteName

• write memory

• show ip default-gateway

• show arp-table


• show radius-server

• snmp-server community secret [ro|rw]

• username name password rw

Multi-config files


Multi-config files Push/pull Pull only Post Operations

Device data


running-ascii copy to start

running-binary reboots automatically


ARP Table Yes


CAM Table No


Nortel 4500 Switch 387

Nortel Devices


Nortel 4500 Switch

◆ The read-only account (typically RO) cannot be used for device management since it cannot be promoted to read-write status. Most commands will fail with Invalid input as a result.

◆ The device driver supports one set of account and SNMP credentials per device. This is a limitation of the device architecture.

◆ The delay in pulling and pushing binary configurations appears to be directly related to the number of switches in the stack.

◆ Pushing a binary configuration is service-affecting: other connected sessions will hang during the file transfer, and the device will reboot without any confirmation.

Identity Yes

Interfaces Yes

Keys No

Memory Yes

OSPF Settings No


Routes Yes



VLANs Yes



44

Overture Devices


◆ Overture NC ................................................................................................................ 390◆ Overture NG ................................................................................................................ 393◆ Overture NP................................................................................................................. 396

Overture Devices 389

Overture Devices

Overture NC

Device Type

Specific Model(s)


Enabled By Default

Operating System


Configuration Files




Password Management




System Properties

Hardware Properties

Quick Commands


Features available◆ Discover/Identify (SNMP, Identify)

◆ System Properties (Model, Software Version, Contact Information, etc.)

◆ Configuration Capture

◆ Configuration Deploy

◆ Credential Management (SNMP)



◆ For SNMP:

• The sysObjectID OID must be accessible from the device agent.

• The serial number must be available at 1.3.6.1.4.1.7950.2.10.1.2

Overture NC

ISG 45+, 34, 45, 140, 180, 140V, 180V

http://www.overturenetworks.com/

No

8.1.0.22.6, 9.1.0.9

Traps

SNMP/FTP

Binary

SNMP/FTP

SNMP

SNMP

SNMP/FTP

SNMP/FTP

SNMP/FTP

Model, Software Version, Contact, Location, Serial Number

Software Version, Serial Number, Manufacture Date, Hardware Revision

View Interfaces

Serial Number, Manufacture Date, Software Version, Hardware Version


Overture Devices



◆ Text config:

• Configuration display only

◆ Binary config:

• Requires anonymous FTP access to the managing Device Server.



◆ Binary config:

• Requires anonymous FTP access to the managing Device Server.

◆ Text

• Text configuration data can be pushed using the Config or Configlet editor using SNMP set messages.

• User must have knowledge of what SNMP oids are writeable and can be pushed. User must adhere to the format of the pulled text config lines.

Device commands



Device data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No

OSPF Settings No


Overture NC 391

Overture Devices


Overture NC

◆ SNMP/TFTP is displayed in the user interface for communication, configuration capture, configuration deploy, and software upgrades, although the device driver actually uses SNMP/FTP.

◆ The get ARP command can return a warning message for an unavailable MAC address due to incomplete MAC address entries.

◆ During text configuration pulls, errors or warnings can display for the SNMP OIDs due to the SNMP OIDs not being populated for that device.

◆ The device file system is unavailable, resulting in a temporary file-system being used for OS upgrades.

Routes No



VLANs No



Overture Devices

Overture NG

Device Type

Specific Model(s)


Enabled By Default

Operating System


Configuration Files


User Interface



Password Management





Features available◆ Discover/Identify (SNMP, SSH, Telnet, Identify)

◆ System Properties (Model, Software Version, Serial Number, etc.)



◆ Credential Management (SNMP, SSH/Telnet)

◆ Hardware Properties (Pull Hardware Inventory)


Overture NG

ISG6000

http://www.overturenetworks.com/

No

9.1.0.80.1

Syslog, Traps

SSH/FTP, Telnet/FTP

Text

SSH, Telnet, FTP/SCP, SNMPv2, Syslog


SNMP, SSH, Telnet

SNMP, SSH, Telnet



FTP, SCP

Serial Number, Manufacture Date, Software Version, Hardware Version, Cards, Memory, Power Supply, MAC Adress, Model Description

Overture NG 393

Overture Devices



◆ Using SSH/Telnet:

• Description or hostname must contain the model information as a string ISG6000.

• Serial number must be available through information command.

◆ Using SNMP:


• The serial number must be available at 1.3.6.1.4.1.7950.2.11.1.2.3.1.8.


◆ Text config:

• Configuration parameters that are stored by the device



◆ Text:

• Text configuration data can be pushed using config or configlet editor using command-line interface commands or using FTP and command-line interface.


The following are the commands that are used to do an operating system upgrade.

◆ The device can download images to its flash using SSH/Telnet and FTP/SCP. The device must be rebooted to activate the flash image.

• The device provides a FTP server but an FTP client is not supported for the device, to start a FTP session. The FTP session must be started from the device server.

• The image should be copied into the $TFTPHOMEDIR directory on the device server. The image path should be relative to the $TFTPHOMEDIR directory. For example, if the image is in /tftpboot/ftp/image/isg6k_app.ovn.9.1.0.80.1 then the path for the image name in the operating system inventory should be ftp/image/ isg6k_app.ovn.9.1.0.80.1.

• While using the server for the operating system update, only the mechanism is used. The ftp username and password must be the same as the device account credentials.


Overture Devices

Device data




Overture NG

◆ No command exists to show the model information using term. When discovering using term, System Description or Hostname should contain the string ISG6000.

◆ The device does not disclose file system information. Adummy file-system is used for operating system upgrades.

◆ Physical Hardware using SNMP is not supported.

◆ Determination of VLAN support is not supported.

◆ ARP table using Term is not supported.

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes

OSPF Settings No


Routes No



VLANs No

Overture NG 395

Overture Devices

Overture NP

Device Type

Specific Model(s)


Enabled By Default

Operating System

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands





◆ Configuration Change Notification (SNMP Trap)

◆ Credential Management (Change or Roll Password, SNMP Communities)



◆ SNMP:


• The model must be available using the OID at .1.3.6.1.4.1.7950.2.1.3.2.1.4.1.

• The serial number must be available at .1.3.6.1.4.1.7950.2.1.3.2.1.3.1.

• The ipTable (.1.3.6.1.2.1.4.20) must be supported by the device agent.

◆ Terminal:

• The information command must list the following non-blank information:

Router

2200, 5100

http://overture.icentera.com/portals/

Yes

8.1.0.22

ASCII, Binary


Telnet/FTP, SSH/FTP, Telnet, SSH


SNMP, Terminal

In-Band

Telnet/FTP, SSH/FTP (Binary), Telnet, SSH (ASCII)

Telnet/FTP, SSH/FTP (Binary), Telnet, SSH (ASCII)

Terminal

Ping, Traceroute, View Interfaces, View Routes, View ARP

Identity, Model, Software Version, Inventory


Overture Devices

– Model Name under Board Type .– Serial Number under Main Board ESN.

• The System Object ID must map to the model name in OvertureModels.xml.

• The following commands must return valid interface information:

– port show all status– interface show ifall– interface show ifName


◆ ASCII:

• configuration display

◆ Binary:

• configuration save-remote

– Requires anonymous FTP access to the managing Device Server.


◆ ASCII:

• Commands are issued interactively at the command line, and the results are scanned for warnings and errors.

◆ Binary:

• configuration restore-remote

– Requires anonymous FTP access to the managing Device Server.



mgmt cli-output set off

configuration display

mgmt-config-server show

mgmt-config-server change ipAddress name secret file-location directory

configuration save-remote

configuration restore-remote

port show all status

interface show ifall

interface show if name

Overture NP 397

Overture Devices

information

slot show cards

mgmt name show

mgmt description show

mgmt location show

mgmt contact show

iproute show

arp show

ping

traceroute


mgmt snmp v2only community-list show

mgmt snmp v2only community-list create name access-level type

mgmt snmp v2only community-list delete entry-name name

account show

account password name secret secret

account create name accessLevel level pass

account delete oldUser


Multi-config files Push/Pull Pull only


running

binary


ARP Table Yes


CAM Table No

File System Information Yes (See Known Issues)

Identity Yes

Interfaces Yes


Overture Devices

Known issues


Overture NP

◆ Non-volatile storage and filesystem information are not obtainable using SNMP or the command line interface for the 8.1.0.22 software version. A placeholder is returned with the flash partition name, but size and usage are not listed.

◆ The configuration restore-defaults command is not used as part of pushing a text configuration, since in almost all cases the managing Device Server will not be on the same subnet as the device. This command clears all settings except for the in-band IP address, which can result in loss of connectivity. As a result, some configuration commands may be listed with warnings in the job results, since these settings are already present.

◆ Certain commands in the mgmt category are listed with a # prefix in the resulting text configuration, although these commands are legal from the command line interface when the prefix is omitted. These commands are skipped during a configuration push because the device treats this character as an invalid command.


◆ The binary configuration push is service-affecting, since the configuration restore-remote command reboots the device after receiving the configuration from the Device Server.

◆ The managing account for the device must have an access-level of security or SNMP/Account Rolls cannot be performed.

◆ Account rolls transfer the access level of the original account to the new one when the names change.

◆ Default accounts cannot be removed. This impacts account credential rolls in the following ways:

• Jobs that define new, equivalent accounts will show a message in the scheduler that the old account cannot be removed.

• Jobs that use a default account as the new account name will simply change the password of this account before removing the non-default account.

Keys No

Memory Yes (See Known Issues)

OSPF Settings No


Routes Yes



VLANs No


Overture NP 399

Overture Devices


45

Packeteer Devices


◆ Packeteer PacketShaper.............................................................................................. 402

Packeteer Devices 401

Packeteer Devices

Packeteer PacketShaper

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands







Packeteer PacketShaper LoadBalancer

Packetshaper 1000 Packetshaper 1400Packetshaper 1500Packetshaper 1550Packetshaper 1700Packetshaper 2000Packetshaper 2500Packetshaper 2550Packetshaper 3500Packetshaper 4000Packetshaper 4500Packetshaper 6500Packetshaper 7500Packetshaper 8500Packetshaper 9500Packetshaper 10000

http://www.packeteer.com/

Yes

Syslog, SNMP Traps

Multiple Text and Binary


SSH/FTP, Telnet/FTP

CLI, SNMP

SNMP, Terminal

Enable, In-Band

FTP

FTP

Terminal

Ping



Packeteer Devices



◆ SysObjectIDs: 1.3.6.1.4.1.2334.*




◆ The following commands are executed from a command prompt:

• mkdir 9.258/VOYENCE (if needed)

• setup capture complete 9.258/VOYENCE/ASCIICFG.CMD

• config save 9.258/VOYENCE/CONFIG.LDI

• cp 9.256/CFG/SETTINGS.CFG 9.258/VOYENCE/SETTINGS.CFG

• zip -rq 9.258/voyence/PLG.ZIP 9.256/PLG

◆ The above files are then transferred, using the device's built-in FTP server, from the 9.258/VOYENCE/ directory to the VoyenceControl device server.

◆ The files are then base64 encoded (if binary) and merged into a single XML document for storage in the configuration database.



◆ The XML document is retrieved from the configuration database and separated into four discrete files.

◆ The ASCIICFG.CMD file is a human-readable version of the binary configuration, and can not be restored, so it is discarded.

◆ The remaining three files are transferred to the 9.258/VOYENCE/ directory.

◆ The following commands are run:

• cp 9.258/VOYENCE/CONFIG.LDI 9.256/CFG/CONFIG.LDI

• setup load 9.258/VOYENCE/SETTINGS.CFG

◆ The device prompts for a reboot after loading SETTINGS.CFG, and the driver answers yes to the prompt.

◆ The PLG.ZIP file, which is a zipped archive of the plug-ins directory is left in the 9.258/VOYENCE/ directory, and not processed in any way. The system administrator can select to restore this file manually if needed.

Packeteer PacketShaper 403

Packeteer Devices

Multi-config files



Device data



running

startup

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


46

Paradyne Devices


◆ Paradyne 9100.............................................................................................................. 406

Paradyne Devices 405

Paradyne Devices

Paradyne 9100

Device Type

Specific Model(s)


Enabled By Default


User Interface


Password Management

Operating System

Cut-Through Access

Quick Commands


◆ Credential Management (In-band/SNMP)




◆ sysDescription contains Paradyne iMarc (case-insensitive)

◆ serial number and system name are valid

Device commandsThe following device command sets must be enabled to allow VoyenceControl NG to manage this device class.


Main > Load Config > Current > Configuration Edit > Management/Communication

Main > Control > Administer Logins

Router

9100

http://search.zhone.com/query.html

No

Telnet

Menu

SNMP

In-band, SNMP

02.02.03

Terminal

Test Credentials, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NatIP Setup


Paradyne Devices

Known issues


◆ Memory and non-volatile information are not supported by the device SNMP agent. These values are defaulted to 0.

◆ The text ## no configuration support ## is listed in place of the device configuration.

◆ SNMP credentials cannot be changed if SNMP is disabled.

Paradyne 9100 407

Paradyne Devices


47

Patton Devices


◆ SmartNode Router ...................................................................................................... 410

Patton Devices 409

Patton Devices

SmartNode Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access


Quick Commands





Patton SmartNode

SN1200, SN1400,SN2300, SN2400,SN2802, SN2805, SN2821, SN2835, SN4112-JS, SN4112-JO, SN4114-JS, SN4114-JO, SN4116-JS, SN4116-JO, SN4118-JS, SN4118-JO, SN4524-SN4834-JS, SN4522-SN4832-JS, SN4526-SN4836-JS, SN4528-SN4838-JS,, SN4524-SN4834-2JS2JO, SN4526-SN4836-4JS2JO, SN4528-SN4838-4JS4JO, SN4114-2JS2JO, SN4116-4JS2JO, SN4118-4JS4JO, SN4522-SN4832-JO, SN4524-SN4834-JO, SN4526-JO, SN4528-JO, SN4552, SN4562,SN4554, SN4564, SN4908-JS, SN4912-JS, SN4916-JS, SN4924-JS, SN4932-JS, SN4634, SN4638, SN46385BIS, SN4654-C, SN4658-C, SN4654-D, SN4658-D, SN4654-T, SN4658-T, SN4654-K, SN4658-K, SN4654-AA, SN4658-AA, SN4654-AB, SN4658-AB, SN4654-G, SN4658-G, SN4635, SN4639, SN4655-AA, SN4659-AA, SN4655-AB, SN4659-AB, SN4655-G, SN4659-G, SN4960-1E15V, SN4960-1E24V, SN4960-1E30V, SN4960-4E15V, SN4960-4E24V, SN4960-4E30V, SN4960-4E48V, SN4960-4E60V, SN4960-4E96V, SN4960-4E120V, SN4961-1E15V, SN4961-1E24V, SN4961-1E30V, SN4961-4E15V, SN4961-4E24V, SN4961-4E30V, SN4961-4E48V, SN4961-4E60V, SN4961-4E96V, SN4961-4E120V, SN4908-JO, SN4912-JO, SN4916-JO, SN4924-JO, SN4932-JO,SDTA

http://www.patton.com/

No

Startup, Running




SNMP, Terminal

In-band

R5.2



Terminal

Supported

Ping, Traceroute, View Routes, View ARP, View Interfaces, Resync


Patton Devices




◆ Model, serial number, and operating system version using SNMP or command-line interface.

◆ Memory using command-line interface.

◆ Interface table using SNMP or command-line interface.




• The show running-config or show startup-config command is issued in the command-line interface, and the file captured directly from the command-line interface output.


• The copy startup-config tftp://[serverip]/[filename] or copy running-config tftp://[serverip]/[filename] command is issued in the command-line interface to transfer the file to the device server.



• A command-line interface session is started in config mode, and the configuration is entered line-by-line while monitoring responses for error messages.


• The copy tftp://[serverip]/[filename] startup-config or copy tftp://[serverip]/[filename] running-config command is issued in the command-line interface to transfer the configuration to the device from the device server.

SmartNode Router 411

Patton Devices

Multi-config files



Device data



startup

running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


48

Radware Devices


◆ Radware WSD Load Balancer ................................................................................... 414

Radware Devices 413

Radware Devices

Radware WSD Load Balancer

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands









◆ SysObjectIDs: .1.3.6.1.4.1.89.1.1.62.(2|3|4)

◆ OS v8.14+ at .1.3.6.1.4.1.89.2.4.0



Radware WSD Load Balancer

All Web Server Director models

http://www.radware.com/

No

Syslog, SNMP Traps

Text – running config only



CLI, SNMP

SNMP

In-Band



Terminal

Ping, Traceroute, Interfaces, Routes, ARP, CPU Procs, Resync, Reboot



Radware Devices




• manage tftp file-type set cli

• manage tftp config-file put [temp_filename] [devserver_ip]

◆ For SSH and Telnet capture output from the following commands:

• system config immediate




• manage tftp file-type set cli

• manage tftp config-file get [temp_filename] [devserver_ip]


• The device is brought to a shell prompt

• Issue command: system paste-config start

• The configuration is entered line by line with checks for invalid input.

• Issue command: system paste-config stop

Multi-config files




running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Radware WSD Load Balancer 415

Radware Devices

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



49

Riverbed Devices


◆ Riverbed Steelhead ..................................................................................................... 418

Riverbed Devices 417

Riverbed Devices

Riverbed Steelhead

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Supported Quick Commands





◆ Credentials Management (In-band, SNMP)


◆ sysObjectID

• Retrieved and compared to 1.3.6.1.4.1.17163

• If a match is found, the chassis serial number is pulled (defaults to hostname if unavailable) and the discovery is successful

Load Balancer

Steelhead 100

Customer Supplied

No

running/startup

Ascii

SSH

Command-Line

SNMP

In-band, SNMP

SSH

SSH

SSH

View interfaces, View routes, Ping, Traceroute, View ARP

Interfaces, Memory, Serial Number, OS Version, Inventory


Riverbed Devices



◆ Using terminal:

• show configuration running

• show configuration



◆ Using terminal:

• Device commands are issued interactively from the stored configuration

Device commands



enable

disable

show configuration running

show configuration

reload

configure terminal

no cli session paging enable

configuration write

ping

traceroute

show interfaces brief

show ip route

show arp


username

snmp-server community

Riverbed Steelhead 419

Riverbed Devices

Multi-config files



Device data



running

startup

ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No


Riverbed Devices

Known issues


Riverbed Steelhead

◆ There is no support for sysServices (standard MIB scalar). The sysServices variable must be edited in stdlib/stdmib.inc and be made a standard snmp type instead of a snmpcached type.

◆ The sysObjectID represents a vendor, not the model identification.

◆ Configuration management using file transfer is not currently supported, since the results are a binary database.

◆ There is no known support for configuration changes using SNMP traps or syslog facility.

◆ There is no SNMP support for hardware inventory, for example ENTITY-MIB. Information is taken from the HOST-RESOURCES-MIB, which does not support parent/child relationships.

◆ The device family does not currently support creation or management of individual accounts.

Riverbed Steelhead 421

Riverbed Devices


50

Riverstone Devices


◆ Riverstone Router........................................................................................................ 424

Riverstone Devices 423

Riverstone Devices

Riverstone Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands







◆ SysObjectID 1.3.6.1.4.1.17163

◆ Serial Number .1.3.6.1.4.1.17163.1.1.1.2.0


◆ no cli session paging enable

◆ show configuration

Router

RS 500, 1000, 2000, 2100, 3000, 8000, 8600, 32000, 38000RSLA 1100, 1200, 1500

See vendor

No

running

Text

SSH

CLI

SNMP

Accounts and SNMP

SSH

SSH

Terminal

Ping, Traceroute, View Routes, NAT

Basic hardware (memory, serial number information)


Riverstone Devices



◆ config terminal

◆ configuration write

Config files

Following are the files used when storing and revisioning configuration files.


Device data



running

startup

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Riverstone Router 425

Riverstone Devices


51

Siemens Devices


◆ Siemens ......................................................................................................................... 428◆ Siemens hiX56xx DSLAM .......................................................................................... 430

Siemens Devices 427

Siemens Devices

Siemens

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







Router

5851, 5871, 5940

http://www.siemens.com

Yes


Command, Config, Configlet, Privilege Mode Termlet, Termlet Merge

Telnet/TFTP, SSH/TFTP, Telnet only, SSH only

Command Line

Terminal, SNMP

In-Band

6.1.064

Terminal, TFTP

Terminal, TFTP

Terminal


For Terminal: Hardware Inventory, Memory, Interfaces, Serial Number, Hardware Information


Siemens Devices

Multi-config files



Device data



.*

.*\.(TXT|MFG|HTM)

config

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Siemens 429

Siemens Devices

Siemens hiX56xx DSLAM

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands





◆ Credential Roll (Enable Password, SNMP Credentials)

◆ Device Access (Cut-Through, Device Commands, Etc.)


◆ Model, Serial Number, and Operating System version using SNMP or Command-Line Interface

◆ Filesystem and Memory using Command-Line Interface



hiX5635

http://www.siemens.com/

Yes

Startup, Running


SSH, Telnet


SNMP, Terminal

In-Band

R1.5

SSH, Telnet

SSH, Telnet

Terminal

Ping, View Interfaces, View Routes, View ARP, Resync

SNMP Entity MIB


Siemens Devices



◆ show running-config

• Command is issued in the command line interface, and the file captured directly from the command line interface output.

◆ show starting-config

• Command is issued in the command line interface, and the file captured directly from the command line interface output.



◆ A command line interface session is started in config mode and the configuration is entered line-by-line while checking responses for error codes.

Multi-config files



Startup

Running

Siemens hiX56xx DSLAM 431

Siemens Devices

Device data



Known issues



◆ As of system version R1.5, the configuration that is output from a show running-config or show startup-config cannot be pushed back to the device without significant editing, due to the following:

• Commands that enter a subconfiguration editor, but do not exit from the subsection appropriately.

• Commands that exit too many times from a subsection, ending configuration mode entirely, and thereby causing subsequent commands to fail.

– Too many exit commands example:

ip dhcp option82 policy drop

!

!End of DHCP daemon's configuration

!

! --- eqm - BEGIN ------------------

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No


Siemens Devices

configure terminal

rack alarm-severity-profile 1

...

card alarm-severity-profile 17 1

exit <<< Exit Config Mode

! --- eqm - END---------------------

!

no debug red-mgr

sw-keepalive

...

!

End <<< Exit Config Mode, too many times.

• Use of EXEC mode syntax in configuration mode commands. For example, our test device produces the following (abridged) config:

– EXEC mode command example:

!configdb_version 1

hostname SG1-ARC146-VIL

terminal length 0 <<<This is an EXEC mode command.

login accounting-mode none

bridge

! start> --- tracelevel submodules swchd ---

debug switch vlan 3

Siemens hiX56xx DSLAM 433

Siemens Devices


52

SourceFire Devices


◆ Sourcefire 3D Sensor ................................................................................................... 436

SourceFire Devices 435

SourceFire Devices

Sourcefire 3D Sensor

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







◆ Using SSH:

• /etc/sf/model.conf file must contain the model information as a string 3D Sensor 2100.

• Serial number must be available through hostid command.

Intrusion Prevention Sensor

3D Sensor 2100

http://www.sourcefire.com/

Yes

Syslog

Text, Binary

SSH

SSH

SSH, SCP

SSH

SSH

4.8.0 -12

SCP

SCP

SSH

Ping, View Description, View Model, View OS Version, View Serial No., Up Time, View Interfaces, View Routes, View ARP Table, View Memory Information, View File Sysytem Information, View hardware Inventory

Capabilities, Control, Description, Status, Subsystem, Latency


SourceFire Devices



◆ Text config

• Configuration parameters stored by the device

◆ Binary config

• Configuration parameters stored by the device



◆ Text

• Configuration data can be pushed using the config editor or the command editor.



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Sourcefire 3D Sensor 437

SourceFire Devices

Known issues


Sourcefire 3D Sensor 2100

◆ SNMP is not supported.


53

Starent Devices


◆ Starent PDSN ............................................................................................................... 440

Starent Devices 439

Starent Devices

Starent PDSN

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management



Cut-Through Access

Quick Commands


Features available







◆ SNMP SysDescr

◆ Model from SysObjectIDs: 1.3.6.1.4.1.8164.*

◆ OS, Filesystem and Memory from CLI



Starent Packet Data Serving Node

ST16

https://support.starentnetworks.com/

No

Syslog, SNMP Traps

Text (running config only)



CLI, SNMP

SNMP

In-Band



Terminal

Ping, View Routes, Traceroute, View_interfaces

Slot/Card Inventory, Interfaces


Starent Devices




• save configuration tftp://[serverIP]/[filename] -noconfirm verbose


• save configuration /flash/[filename] -noconfirm verbose

• show file url /flash/[filename]



◆ For all protocols:

• The device is brought to a shell prompt in admin mode.

• The configuration is entered line-by-line with checks for invalid input.

• By default, the running config is copied to the startup file after a successful push to running. This step can, optionally, be skipped when the push job is scheduled.



Device data


running


ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


Starent PDSN 441

Starent Devices

Known issues


Starent PDSN

◆ The copyToStart post-operation does the following:

• Sends the show boot initial-config command to find the startup config file.

• Copies the current contents of the above file to [startfile].bak.1.

• Sends the command copy configuration [startfile] -noconfirm.

OSPF Settings No


Routes Yes



VLANs No



54

Symbol Devices


◆ Symbol WS-2000.......................................................................................................... 444

Symbol Devices 443

Symbol Devices

Symbol WS-2000

Device Type

Specific Model(s)


Enabled By Default


Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access










Wireless Switch WS-2000

Symbol WS-2000

http://www.symbol.com/

Yes

Traps

Single Text

Termlet Merge, User Mode Termlet, Command, Configlet, Config

SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only, SNMP/TFTP

Command Line, Menu Driver, Web Based

SNMP

In-Band, SNMP

1.5.0, 1.5.1, 2.0.0, 2.0.1, 2.0.2

Terminal, SNMP, Non-SNMP

Terminal, SNMP

SNMP, Terminal, Non-SNMP

Telnet/TFTP, Telnet/FTP

View NAT, Test Credentials, Device Uptime, Interface Summary, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup

For SNMP: Hardware Inventory, Memory, Interfaces, Serial Number, Model, OS VersionFor Non-SNMP: Interfaces, Serial Number, Model, OS Version


Symbol Devices



◆ System Description

• Symbol WS2000 HW=E SW=0.0-035R MIB=08c12


• SNMPv2-SMI::enterprises.388.11.1.1



◆ Server IP Host (a.b.c.d)

• 1.3.6.1.4.1.388.11.2.2.6.1.0

◆ TFTP Operation

• 1.3.6.1.4.1.388.11.2.2.4.1.0

– unspecified;– ftpSrvToSwitch;– ftpSwitchToSrv;– tftpSrvToSwitch;– tftpSwitchToSrv;

◆ Filename

• 1.3.6.1.4.1.388.11.2.2.4.3.0

◆ Start the transfer

• 1.3.6.1.4.1.388.11.2.2.4.4.0

◆ Operation count

• 1.3.6.1.4.1.388.11.2.2.4.5.0

◆ Operation result string

• 1.3.6.1.4.1.388.11.2.2.4.6.0

◆ Operation success string

• 1.3.6.1.4.1.388.11.2.2.4.7.0

Symbol WS-2000 445

Symbol Devices



◆ Most of the sub-menus are located within the system sub-menu which is entered as follows:

• Admin>system

• Admin(system)>

◆ A configuration file can be transferred to the device using FTP or TFTP. This is available in the config sub-menu as follows:

• Admin>system

• Admin(system)>config

• Admin(system.config)>import ftp: import config from ftp server

• Admin(system.config)>import tftp: import config from tftp server

Operating System Management notes

The Symbol Device Driver supports OS upgrade and downgrade using telnet and SSH login protocols and FTP/TFTP file transfer mechanisms.

The Symbol firmware releases 1.5.0, 1.5.1, 2.0.0, and 2.1.0 have all been qualified and tested with the upgrade/downgrade process. One issue was found when completing an upgrade or downgrade between the 2.0.0 and 2.1.0 releases using the SSH protocol.

The Symbol device 2.0.0 and 2.1.0 firmware returns different fingerprints for the RSA key. Therefore, after the upgrade/downgrade, attempts to login using SSH will fail, due to the key exchange.

From the application, the per/downgrade will show Failed, based on failure to login following the device reboot, due to SSH host key verification. Suggestions for managing this issue are as follows.

◆ If possible at your site, using telnet for the OS upgrade/downgrade between 2.0.0 and 2.1.0 allows the process to proceed normally and return status of the state of the device.

◆ If using SSH for OS upgrade, check the error status looking for a successful upload, followed by an SSH failure to connect. This is the failure signature indicating the RSA key mismatch between firmware releases.

◆ In either case, you need to update the SSH host key database on the HP device server to regain access to the device.

• For Linux and Solaris Servers: The SSH key database is located in the ~root/.ssh/sshhostkeys file. Edit the sshhostkeys file, and remove the entry associated with the Symbol device based on IP address.

• For Windows Servers: The host key database is maintained in the Registry, in the HKEY_LOCAL_MACHINE\SOFTWARE\Voyence\Control\SshHostKeys folder. Using the regedit utility, remove the entry associated with the Symbol device based on IP address.


Symbol Devices

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Symbol WS-2000 447

Symbol Devices


55

Tasman Devices


◆ Tasman Router ............................................................................................................. 450

Tasman Devices 449

Tasman Devices

Tasman Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management



Cut-Through Access


Quick Commands


Features available









• 1.3.6.1.4.1.3174.1

◆ SysDecr

• Contains Tasman

Tasman Router

1004E, 1001, 1002, 1002E, 1200, 1200C, 1200E, 1200EC, 1250, 1400, 1400E, 1450 4100, 4102 6300

www.tasman.com

Yes

Single Text



Command Line

Terminal, SNMP

In-Band, SNMP

Terminal

Terminal

Telnet/TFTP, Terminal


Resync, diffRunStart



Tasman Devices

Multi-config files



Device data



Known issues


Tasman Family of Devices

◆ Tasman uses the concept of account levels. Currently, devices get Auto Discovered with low level accounts, but can not successfully complete a Pull. To Pull devices, you must ensure the devices are setup with Level 1 accounts.

Tasman TIOS

◆ Tasman TIOS does not allow changing the Admin Name using SSH. You must use TELNET.

running

startup

ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Tasman Router 451

Tasman Devices


56

Telco Devices


◆ Telco Switch.................................................................................................................. 454◆ Telco T-Metro ............................................................................................................... 457

Telco Devices 453

Telco Devices

Telco Switch

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands







◆ sysObjectID

• OID contains either 1.3.6.1.4.1.738.1.5.100.1.1.10 or 1.3.6.1.4.1.738.1.5.100.1.1.17

◆ Serial number successfully retrieved

• OID .1.3.6.1.4.1.738.1.5.100.1.3.1.0

Switch

T5CL3-24G 256M, T-Marc-250, T-Marc-254

http://www.telco.com

No

Single Text




SNMP

In-Band

T5CL3-24G 256M: BinOS 6.5.5, T-Marc-250: BinOS 6.6.3.4, T-Marc-254: BinOS 6.6.3.4



Terminal

View Interfaces, View Routes, Ping, Traceroute

Serial number, OS version, Interfaces



Telco Devices



◆ Telnet, SSH:



◆ Telnet/TFTP, SSH/TFTP:

• copy running-config upload-to serverIpAddress remoteFilename

• copy startup-config upload-to serverIpAddress remoteFilename

Configuration DeployFollowing are the commands or processes used to "push" a configuration to your device.

◆ Telnet, SSH:



• Full configuration pushes are not supported with these protocols.


• copy running-config download-from serverIpAddress remoteFilename

• copy startup-config download-from serverIpAddress remoteFilename

Multi-config files




running

startup


ARP Table No


CAM Table No


Device Identity Yes

Telco Switch 455

Telco Devices

Known issues


Telco Switch


◆ Either Telnet/TFTP or SSH/TFTP must be enabled to push configurations. Commands issued to the CLI do not merge with the running configuration.

◆ The Configuration Editor in VoyenceControl does not analyze the content for the type of line termination. To insert blank lines in banner pages, at least one space-character must be present.

◆ Account and privilege password management is present but unverified.

◆ SNMP credential rolls require non-blank credentials.

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No



Telco Devices

Telco T-Metro

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands






◆ sysObjectID

• OIS contains 1.3.6.1.4.1.738.1.5.100.1.1.16

◆ Serial number successfully retrieved

• OID .1.3.6.1.4.1.738.1.5.100.1.3.1.0

Switch

T-Metro 256M


No

Single Text




SNMP

In-Band, SNMP

7.0.R2



Terminal

Serial number, OS version, Interfaces

Telco T-Metro 457


Telco Devices



◆ Telnet, SSH:




• copy running-config tftp://serverIpAddress/remotePathname

• copy startup-config tftp://serverIpAddress/remotePathname


◆ Telnet, SSH:



• Full configuration pushes are not supported with these protocols.


• copy tftp://serverIpAddress/remotePathname running-config

• copy tftp://serverIpAddress/remotePathname startup-config

Multi-config files




running

startup


ARP Table No


CAM Table No


Device Identity Yes


Telco Devices

Known issues


Telco T-Metro Switch


◆ Either Telnet/TFTP or SSH/TFTP must be enabled to push configurations. Commands issued to the CLI do not merge with the running configuration.

◆ The Configuration Editor in VoyenceControl does not analyze the content for the type of line termination. To insert blank lines in banner pages, at least one space-character must be present.

◆ Account and privilege password management is present but unverified.

◆ SNMP credential rolls require non-blank credentials.

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No


Telco T-Metro 459

Telco Devices


57

Vanguard Devices


◆ Vanguard Router ......................................................................................................... 462

Vanguard Devices 461

Vanguard Devices

Vanguard Router

Device Type

Specific Model(s)


Enabled By Default

Configuration Files



User Interface


Password Management

Operating System



Cut-Through Access

Quick Commands

Features available







◆ sysObjectID

• Contains 1.3.6.1.4.1.449.2.1.3410


◆ tftp getscript remoteFilename serverIpAddress

Router

3410

www.vanguardnetworks.com/ support/documentation/ user_manuals/

No

Single Text




SNMP

In-Band, SNMP

V7.1.R00A_@Seven_3400



Terminal

Memory, Interfaces, Serial number, OS version, Inventory


Vanguard Devices



◆ tftp setscript remoteFilename serverIpAddress

Multi-config files





running

ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Vanguard Router 463

Vanguard Devices

Known issues


Vanguard Router

◆ Only one session can be logged into the device at a time.

◆ SNMP community string changes require a reboot per credential to take effect.


Revised: January 29, 2010 12:00 pmVC_DSS_IX.fm(Publication Template Lg Book v4.3)

EMC CONFIDENTIALDRAFT

Index

Numerics3COM Devices 333Com Netbuilder II Router 343Com Switch 5500 36

AACME Devices 41ACME NetNet SBC 42Adtran Devices 47, 55Adtran Netvanta 48, 56Adtran Netvanta Switch 51Adva FSP150CC 56Airespace Devices 59, 93Airespace Switch 60, 94Alcatel Devices 63Alcatel OmniCore 68Alcatel Omnistack 71Alcatel Omniswitch 75Alcatel Service Router and Ethernet Service Switch 81Alvarion Breeze AP 86Alvarion Devices 85Aruba Devices 89Aruba Wireless Switch 90AudioCodes MediaPack 94

BBlueCoat Devices 99BlueCoat SG 100Brocade 7500 104Brocade Devices 103Brocade McData 107

CCheckpoint Devices 109Checkpoint Firewall-1 110Ciena Devices 115Ciena Router 116Cisco Aironet AP Package 131Cisco Aironet AP VXWorks 120Cisco Aironet Bridge Package 135Cisco Application Control Engine 138Cisco BPX 141

Cisco CatOS Switch Package 145Cisco Content Appliance 152Cisco Content Services Switch 156Cisco Devices 119Cisco Intrusion Prevention System (IPS) 178Cisco IOS Switch Package 167Cisco IOS XR 174Cisco Lightstream Package 181Cisco MDS 194Cisco MGX 189Cisco Nexus 184Cisco PIX Firewall 122Cisco Router 159Cisco VPN 3000 128Cisco Wireless LAN Controller 200Citrix Devices 203Citrix Netscaler LoadBalancer 204Configuring FTP Transfer Service 32

DDevice Drivers 28D-Link Devices 207D-Link xStack 208

EEdgewater EdgeMarc Router 212Enabling Inactive Device Classes 30Enterasys Smartswitch Router 216Ericsson ECN Switch 222Ericsson MSED 225Extreme 230ExtremeWare XOS 233

FF5 Load Balancer Rev 3 238F5 Load Balancer Rev 4 242F5 Load Balancer Rev 9 245Force10 C-Series Router 252Force10 E-Series Router 255Foundry EdgeIron 262, 266, 274Foundry Package 269

Index 465

DRAFT Revised: January 29, 2010 12:00 pm VC_DSS_IX.fm

Index

EMC CONFIDENTIAL

HHP ProCurve Switch 280

IIntroduction 25

JJuniper ERX (E Series) 296Juniper Router Package 300Juniper Switch (EX Series) 304

LLaurel ST Router 314Lucent Access Point 318

MMarconi ASX 322McAfee IntruShield 326Motorola BSR Router 334MRV LX Terminal Server 340

NNetCache 344Netopia R7000 Series 348Netscreen Firewall 352Nokia IP 356Nortel 4500 Switch 385Nortel Alteon 362, 390Nortel Alteon 2400 365Nortel Baystack 370Nortel BoSS Switch 372Nortel Contivity 375Nortel Multi-Service Switch 377Nortel Passport 380Nortel Passport 8600 382Nortel Router 367

OOverture NG 393

PPacketeer PacketShaper 402Paradyne 9100 406, 410

RRadware WSD Load Balancer 414Riverbed Steelhead 418Riverstone Router 424

SSiemens 5940 428, 430Siemens Devices 427SM801P Managed Switch 330SmartAX 286, 292Sourcefire 436

Starent 440Starent Devices 439Starent PDSN 436, 440Symbol Devices 443Symbol WS-2000 444

TTasman Devices 449Tasman Route 450Tasman Router 450Telco Devices 453Telco Switch 454Telco T-Metro 457

VVanguard Devices 461Vanguard Router 462Viewing Installed Device Driver Packages 31


Date post:	29-Nov-2021
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

EMC VoyenceControl Device Services Support (DSr) - Support ...

Documents