emc voyencecontrol device services support (dsr)emc ® voyencecontrol device services support (dsr)...

EMC®

VoyenceControlDevice Services

Support (DSr)version 11.0.0 Hotfix 2

DEVICE SERVICESSUPPORT GUIDE

P/N 300-008-915Rev A01

EMC CorporationCorporate Headquarters

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

Device Services Support (DSr) 11.0.0 Hotfix 2

Device Services Support (DSR) Version 11.0.0 Hotfix 2

COPYRIGHT

Copyright © 2009 EMC Corporation. All rights reserved.

Published April 2009

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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

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



TABLE OF CONTENTS

COPYRIGHT.................................................................................................. 2

PREFACE..................................................................................................... 16 Who Should Read this Document? ............................................................................ 16 Related Publication ................................................................................................ 16

INTRODUCTION.......................................................................................... 17 What is VoyenceControl? ........................................................................................ 17 About this Manual .................................................................................................. 17 Compatibility......................................................................................................... 17

DEVICE DRIVER INFORMATION.................................................................. 18 New Device Drivers................................................................................................ 18 Modified Device Drivers .......................................................................................... 18 Enabling Inactive Device Classes.............................................................................. 19 Viewing Installed Device Driver Packages .................................................................. 19

3COM DEVICES........................................................................................... 20 3Com Netbuilder II Router ...................................................................................... 20

Features Available ............................................................................................................... 20 Discovery/Identify Methods................................................................................................... 20 Configuration Capture .......................................................................................................... 21 Configuration Deploy............................................................................................................ 21 Multi-Config Files ................................................................................................................. 21 Device Data ........................................................................................................................ 21

3Com Switch 5500................................................................................................. 22 Features Available ............................................................................................................... 22 Discovery/Identify Methods................................................................................................... 22 Configuration Capture .......................................................................................................... 22 Configuration Deploy............................................................................................................ 23 Device Commands ............................................................................................................... 23 Multi-Config Files ................................................................................................................. 24 Device Data ........................................................................................................................ 24 Known Issues...................................................................................................................... 24

ADTRAN DEVICES....................................................................................... 25 Adtran Netvanta .................................................................................................... 25

Features Available ............................................................................................................... 25 Discovery/Identify Methods................................................................................................... 25 Configuration Capture .......................................................................................................... 25 Multi-Config Files ................................................................................................................. 26 Device Data ........................................................................................................................ 26 Known Issues...................................................................................................................... 27

Adtran Netvanta Switch .......................................................................................... 28 Features Available ............................................................................................................... 28 Discovery/Identify Methods................................................................................................... 28 Configuration Capture .......................................................................................................... 29 Multi-Config Files ................................................................................................................. 29 Device Data ........................................................................................................................ 29 Known Issues...................................................................................................................... 29



AIRESPACE DEVICES .................................................................................. 30 Airespace Switch ................................................................................................... 30

Features Available ............................................................................................................... 30 Discovery/Identify Methods................................................................................................... 30 Configuration Capture .......................................................................................................... 30 Configuration Deploy............................................................................................................ 31 Multi-Config Files ................................................................................................................. 31 Device Data ........................................................................................................................ 31 Known Issues...................................................................................................................... 31

ALCATEL DEVICES ...................................................................................... 32 Alcatel OmniCore................................................................................................... 32

Features Available ............................................................................................................... 32 Discovery/Identify Methods................................................................................................... 32 Configuration Capture .......................................................................................................... 33 Configuration Deploy............................................................................................................ 33 Multi-Config Files ................................................................................................................. 33 Device Data ........................................................................................................................ 33

Alcatel Omnistack .................................................................................................. 34 Features Available ............................................................................................................... 34 Discovery/Identify Methods................................................................................................... 34 Configuration Capture .......................................................................................................... 35 Configuration Deploy............................................................................................................ 35 Device Commands ............................................................................................................... 35 Multi-Config Files ................................................................................................................. 36 Device Data ........................................................................................................................ 36 Known Issues...................................................................................................................... 36

Alcatel Omniswitch................................................................................................. 37 Features Available ............................................................................................................... 37 Discovery/Identify Methods................................................................................................... 37 Configuration Capture .......................................................................................................... 38 Configuration Deploy............................................................................................................ 38 Device Commands ............................................................................................................... 38 Multi-Config Files ................................................................................................................. 39 Device Data ........................................................................................................................ 39 Known Issues...................................................................................................................... 40

Alcatel Service Router and Ethernet Service Switch..................................................... 41 Features Available ............................................................................................................... 41 Discovery/Identify Methods................................................................................................... 41 Configuration Capture .......................................................................................................... 42 Configuration Deploy............................................................................................................ 42 Configuration Activations ...................................................................................................... 42 Multi-Config Files ................................................................................................................. 42 Device Data ........................................................................................................................ 43 Known Issues...................................................................................................................... 43

ALVARION DEVICES ................................................................................... 44 Alvarion Breeze AP................................................................................................. 44

Features Available ............................................................................................................... 44 Discovery/Identify Methods................................................................................................... 44 Configuration Capture .......................................................................................................... 44 Device Commands ............................................................................................................... 44 Multi-Config Files ................................................................................................................. 45 Device Data ........................................................................................................................ 45 Known Issues...................................................................................................................... 45

ARUBA DEVICES ......................................................................................... 46 Aruba Wireless Switch ............................................................................................ 46

Features Available ............................................................................................................... 46 Discovery/Identify Methods................................................................................................... 46 Configuration Capture .......................................................................................................... 47



Configuration Deploy............................................................................................................ 47 Multi-Config Files ................................................................................................................. 47 Device Data ........................................................................................................................ 47

BLUECOAT DEVICES ................................................................................... 48 BlueCoat SG ......................................................................................................... 48


BROCADE DEVICES..................................................................................... 51 Brocade 7500........................................................................................................ 51

Features Available ............................................................................................................... 51 Discovery/Identify Methods................................................................................................... 51 Configuration Capture .......................................................................................................... 51 Device Commands ............................................................................................................... 51 Multi-Config Files ................................................................................................................. 52 Device Data ........................................................................................................................ 52 Known Issues...................................................................................................................... 52

Brocade McData .................................................................................................... 53 Features Available ............................................................................................................... 53 Discovery/Identify Methods................................................................................................... 53 Configuration Capture .......................................................................................................... 54 Device Commands ............................................................................................................... 54 Known Issues...................................................................................................................... 54

CHECKPOINT DEVICES ............................................................................... 55 Checkpoint Firewall-1 ............................................................................................. 55


CIENA DEVICES.......................................................................................... 59 Ciena Router......................................................................................................... 59


CISCO DEVICES .......................................................................................... 62 Cisco Aironet AP VXWorks....................................................................................... 62

Features Available ............................................................................................................... 62 Discovery/Identify Methods................................................................................................... 62 Configuration Capture .......................................................................................................... 62 Multi-Config Files ................................................................................................................. 62 Device Data ........................................................................................................................ 63

Cisco PIX Firewall .................................................................................................. 64 Features Available ............................................................................................................... 64 Discovery/Identify Methods................................................................................................... 65 Configuration Capture .......................................................................................................... 65



Configuration Deploy............................................................................................................ 65 Device Commands ............................................................................................................... 65 Multi-Config Files ................................................................................................................. 67 Device Data ........................................................................................................................ 67 Known Issues...................................................................................................................... 68

Cisco VPN 3000 ..................................................................................................... 69 Features Available ............................................................................................................... 69 Discovery/Identify Methods................................................................................................... 69 Configuration Capture .......................................................................................................... 69 Configuration Deploy............................................................................................................ 70 Multi-Config Files ................................................................................................................. 70 Device Data ........................................................................................................................ 70

Cisco Aironet AP Package........................................................................................ 71 Features Available ............................................................................................................... 71 Discovery/Identify Methods................................................................................................... 72 Configuration Capture .......................................................................................................... 72 Configuration Deploy............................................................................................................ 72 Multi-Config Files ................................................................................................................. 73 Device Data ........................................................................................................................ 73

Cisco Aironet Bridge Package................................................................................... 74 Features Available ............................................................................................................... 74 Discovery/Identify Methods................................................................................................... 74 Configuration Capture .......................................................................................................... 75 Configuration Deploy............................................................................................................ 75 Multi-Config Files ................................................................................................................. 75 Device Data ........................................................................................................................ 76

Cisco Application Control Engine .............................................................................. 77 Features Available ............................................................................................................... 77 Discovery/Identify Methods................................................................................................... 77 Configuration Capture .......................................................................................................... 78 Configuration Deploy............................................................................................................ 78 Multi-Config Files ................................................................................................................. 78 Device Data ........................................................................................................................ 79 Known Issues...................................................................................................................... 79

Cisco BPX ............................................................................................................. 80 Features Available ............................................................................................................... 80 Discovery/Identify Methods................................................................................................... 80 Configuration Capture .......................................................................................................... 81 Configuration Deploy............................................................................................................ 81 Device Commands ............................................................................................................... 81 Known Issues...................................................................................................................... 82

Cisco CatOS Switch Package.................................................................................... 83 Features Available ............................................................................................................... 84 Discovery/Identify Methods................................................................................................... 84 Configuration Capture .......................................................................................................... 84 Configuration Deploy............................................................................................................ 85 Device Commands ............................................................................................................... 85 Multi-Config Files ................................................................................................................. 87 Device Data ........................................................................................................................ 88 Known Issues...................................................................................................................... 88

Cisco Content Appliance.......................................................................................... 89 Features Available ............................................................................................................... 89 Discovery/Identify Methods................................................................................................... 89 Configuration Capture .......................................................................................................... 90 Configuration Deploy............................................................................................................ 90 Multi-Config Files ................................................................................................................. 90 Device Data ........................................................................................................................ 91 Known Issues...................................................................................................................... 91

Cisco Content Services Switch ................................................................................. 92 Features Available ............................................................................................................... 92 Discovery/Identify Methods................................................................................................... 92 Configuration Capture .......................................................................................................... 92 Configuration Deploy............................................................................................................ 93



Multi-Config Files ................................................................................................................. 93 Device Data ........................................................................................................................ 93

Cisco Router ......................................................................................................... 94 Features Available ............................................................................................................... 96 Discovery/Identify Methods................................................................................................... 96 Configuration Capture .......................................................................................................... 96 Configuration Deploy............................................................................................................ 96 Device Commands ............................................................................................................... 97 Multi-Config Files ................................................................................................................. 99 Device Data ........................................................................................................................ 99 Known Issues.................................................................................................................... 100

Cisco IOS Switch Package ..................................................................................... 101 Features Available ............................................................................................................. 102 Discovery/Identify Methods................................................................................................. 102 Configuration Capture ........................................................................................................ 102 Configuration Deploy.......................................................................................................... 103 Device Commands ............................................................................................................. 103 Multi-Config Files ............................................................................................................... 105 Device Data ...................................................................................................................... 106 Known Issues.................................................................................................................... 106

Cisco IOS XR....................................................................................................... 108 Features Available ............................................................................................................. 108 Discovery/Identify Methods................................................................................................. 109 Configuration Capture ........................................................................................................ 109 Configuration Deploy.......................................................................................................... 109 OS Upgrade ...................................................................................................................... 109 Multi-Config Files ............................................................................................................... 109 Device Data ...................................................................................................................... 110 Known Issues.................................................................................................................... 110

Cisco Intrusion Prevention System (IPS) ................................................................. 112 Features Available ............................................................................................................. 112 Discovery/Identify Methods................................................................................................. 112 Configuration Capture ........................................................................................................ 113 Configuration Deploy.......................................................................................................... 113 Multi-Config Files ............................................................................................................... 113 Device Data ...................................................................................................................... 113 Known Issues.................................................................................................................... 113

Cisco Lightstream Package.................................................................................... 114 Features Available ............................................................................................................. 114 Discovery/Identify Methods................................................................................................. 114 Configuration Capture ........................................................................................................ 115 Configuration Deploy.......................................................................................................... 115 Multi-Config Files ............................................................................................................... 115 Device Data ...................................................................................................................... 116

Cisco MGX .......................................................................................................... 117 Features Available ............................................................................................................. 117 Discovery/Identify Methods................................................................................................. 118 Configuration Capture ........................................................................................................ 118 Configuration Deploy.......................................................................................................... 118 Device Commands ............................................................................................................. 119 Known Issues.................................................................................................................... 120

Cisco MDS .......................................................................................................... 121 Features Available ............................................................................................................. 121 Discovery/Identify Methods................................................................................................. 121 Configuration Capture ........................................................................................................ 122 Configuration Deploy.......................................................................................................... 122 Device Commands ............................................................................................................. 122 Multi-Config Files ............................................................................................................... 122 Device Data ...................................................................................................................... 123

Cisco Wireless LAN Controller ................................................................................ 124 Features Available ............................................................................................................. 124 Discovery/Identify Methods................................................................................................. 124 Configuration Capture ........................................................................................................ 125



Configuration Deploy.......................................................................................................... 125 Multi-Config Files ............................................................................................................... 125 Device Data ...................................................................................................................... 126 Known Issues.................................................................................................................... 126

CITRIX DEVICES....................................................................................... 127 Citrix Netscaler LoadBalancer ................................................................................ 127

Features Available ............................................................................................................. 127 Discovery/Identify Methods................................................................................................. 127 Configuration Capture ........................................................................................................ 127 Configuration Deploy.......................................................................................................... 128 Multi-Config Files ............................................................................................................... 128 Device Data ...................................................................................................................... 128

D-LINK DEVICES ...................................................................................... 129 D-Link xStack ..................................................................................................... 129

Features Available ............................................................................................................. 129 Discovery/Identify Methods................................................................................................. 129 Configuration Capture ........................................................................................................ 129 Configuration Deploy.......................................................................................................... 130 Multi-Config Files ............................................................................................................... 130 Device Data ...................................................................................................................... 130 Known Issues.................................................................................................................... 130

EDGEWATER DEVICES .............................................................................. 131 Edgewater EdgeMarc Router.................................................................................. 131


ENTERASYS DEVICES ............................................................................... 133 Enterasys Smartswitch Router ............................................................................... 133

Features Available ............................................................................................................. 133 Discovery/Identify Methods................................................................................................. 133 Configuration Capture ........................................................................................................ 134 Configuration Deploy.......................................................................................................... 134 Device Commands ............................................................................................................. 134 Multi-Config Files ............................................................................................................... 135 Device Data ...................................................................................................................... 135 Known Issues.................................................................................................................... 135

ERICSSON DEVICES.................................................................................. 136 Ericsson MSED .................................................................................................... 136


EXTREME DEVICES ................................................................................... 138 Extreme ............................................................................................................. 138

Features Available ............................................................................................................. 139 Discovery/Identify Methods................................................................................................. 139 Multi-Config Files ............................................................................................................... 139 Device Data ...................................................................................................................... 139 Known Issues.................................................................................................................... 140



ExtremeWare XOS ............................................................................................... 141 Features Available ............................................................................................................. 141 Discovery/Identify Methods................................................................................................. 141 Configuration Capture ........................................................................................................ 141 Configuration Deploy.......................................................................................................... 142 Multi-Config Files ............................................................................................................... 142 Device Data ...................................................................................................................... 142 Known Issues.................................................................................................................... 142

F5 DEVICES .............................................................................................. 143 F5 Load Balancer Rev 3 ........................................................................................ 143

Features Available ............................................................................................................. 143 Discovery/Identify Methods................................................................................................. 143 Configuration Capture ........................................................................................................ 144 Configuration Deploy.......................................................................................................... 144 Device Commands ............................................................................................................. 144 Multi-Config Files ............................................................................................................... 145 Device Data ...................................................................................................................... 146

F5 Load Balancer Rev 4 ........................................................................................ 147 Features Available ............................................................................................................. 147 Discovery/Identify Methods................................................................................................. 147 Configuration Capture ........................................................................................................ 147 Configuration Deploy.......................................................................................................... 148 Multi-Config Files ............................................................................................................... 148 Device Data ...................................................................................................................... 149

F5 Load Balancer Rev 9 ........................................................................................ 150 Features Available ............................................................................................................. 150 Discovery/Identify Methods................................................................................................. 150 Configuration Capture ........................................................................................................ 151 Configuration Deploy.......................................................................................................... 151 Device Commands ............................................................................................................. 151 Multi-Config Files ............................................................................................................... 152 Device Data ...................................................................................................................... 154

FORCE10 DEVICES.................................................................................... 155 Force10 C-Series Router ....................................................................................... 155


Force10 E-Series Router ....................................................................................... 158 Features Available ............................................................................................................. 158 Discovery/Identify Methods................................................................................................. 158 Configuration Capture ........................................................................................................ 159 Configuration Deploy.......................................................................................................... 159 Multi-Config Files ............................................................................................................... 159 Device Data ...................................................................................................................... 160

FOUNDRY DEVICES................................................................................... 161 Foundry EdgeIron ................................................................................................ 161

Features Available ............................................................................................................. 161 Discovery/Identify Methods................................................................................................. 161 Configuration Capture ........................................................................................................ 161 Multi-Config Files ............................................................................................................... 162 Device Data ...................................................................................................................... 162 Known Issues.................................................................................................................... 162

Foundry Package ................................................................................................. 163 Features Available ............................................................................................................. 163 Discovery/Identify Device ................................................................................................... 163 Configuration Capture ........................................................................................................ 164



Configuration Deploy.......................................................................................................... 164 Device Commands ............................................................................................................. 164 Multi-Config Files ............................................................................................................... 165 Device Data ...................................................................................................................... 165

HP DEVICES ............................................................................................. 166 HP ProCurve Switch ............................................................................................. 166


JUNIPER DEVICES .................................................................................... 171 Juniper ERX (E Series).......................................................................................... 171


Juniper Router Package ........................................................................................ 174 Features Available ............................................................................................................. 174 Discovery/Identify Methods................................................................................................. 175 Configuration Capture ........................................................................................................ 175 Configuration Deploy.......................................................................................................... 175 Multi-Config Files ............................................................................................................... 175 Device Data ...................................................................................................................... 176 Known Issues.................................................................................................................... 176

Juniper Switch (EX Series) .................................................................................... 177 Features Available ............................................................................................................. 177 Discovery/Identify Methods................................................................................................. 178 Configuration Capture ........................................................................................................ 178 Configuration Deploy.......................................................................................................... 178 Multi-Config Files ............................................................................................................... 178 Device Data ...................................................................................................................... 179 Known Issues.................................................................................................................... 179

LAUREL DEVICES...................................................................................... 180 Laurel ST Router.................................................................................................. 180


LUCENT DEVICES...................................................................................... 183 Lucent Access Point ............................................................................................. 183




MARCONI DEVICES................................................................................... 185 Marconi ASX ....................................................................................................... 185


MCAFEE DEVICES ..................................................................................... 188 McAfee IntruShield............................................................................................... 188

Features Available ............................................................................................................. 188 Discovery/Identify Methods................................................................................................. 188 Configuration Capture ........................................................................................................ 188 Multi-Config Files ............................................................................................................... 189 Device Data ...................................................................................................................... 189 Known Issues.................................................................................................................... 189

MILAN DEVICES ....................................................................................... 190 SM801P Managed Switch ...................................................................................... 190

Features Available ............................................................................................................. 190 Discovery/Identify Methods................................................................................................. 191 Multi-Config Files ............................................................................................................... 191 Device Data ...................................................................................................................... 191

MOTOROLA BSR........................................................................................ 192 Motorola BSR Router ............................................................................................ 192


MRV DEVICES........................................................................................... 195 MRV LX Terminal Server ....................................................................................... 195


NETCACHE DEVICES ................................................................................. 197 NetCache ........................................................................................................... 197

Features Available ............................................................................................................. 197 Multi-Config Files ............................................................................................................... 198 Device Data ...................................................................................................................... 198

NETOPIA DEVICES.................................................................................... 199 Netopia R7000 Series........................................................................................... 199




NETSCREEN DEVICES ............................................................................... 201 Netscreen Firewall ............................................................................................... 201


NOKIA DEVICES ....................................................................................... 204 Nokia IP ............................................................................................................. 204


NORTEL DEVICES ..................................................................................... 208 Nortel Alteon....................................................................................................... 208


Nortel Alteon 2400............................................................................................... 211 Features Available ............................................................................................................. 211 Discovery/Identify Methods................................................................................................. 211 Configuration Capture ........................................................................................................ 211 Configuration Deploy.......................................................................................................... 212 Known Issues.................................................................................................................... 212

Nortel Router ...................................................................................................... 213 Features Available ............................................................................................................. 213 Discovery/Identify Methods................................................................................................. 214 Configuration Capture ........................................................................................................ 214 Configuration Deploy.......................................................................................................... 214 Multi-Config Files ............................................................................................................... 214 Device Data ...................................................................................................................... 215 Known Issues.................................................................................................................... 215

Nortel Baystack ................................................................................................... 216 Features Available ............................................................................................................. 216 Discovery/Identify Methods................................................................................................. 216 Multi-Config Files ............................................................................................................... 217 Device Data ...................................................................................................................... 217

Nortel BoSS Switch .............................................................................................. 218 Features Available ............................................................................................................. 218 Discovery/Identify Methods................................................................................................. 218 Configuration Capture ........................................................................................................ 218 Configuration Deploy.......................................................................................................... 219 Multi-Config Files ............................................................................................................... 219 Device Data ...................................................................................................................... 219

Nortel Contivity ................................................................................................... 220 Features Available ............................................................................................................. 220 Discovery/Identify Methods................................................................................................. 220 Multi-Config Files ............................................................................................................... 221 Device Data ...................................................................................................................... 221

Nortel Multi-Service Switch ................................................................................... 222




Nortel Passport.................................................................................................... 225 Features Available ............................................................................................................. 225 Discovery/Identify Methods................................................................................................. 225 Configuration Capture ........................................................................................................ 225 Configuration Deploy.......................................................................................................... 225 Multi-Config Files ............................................................................................................... 226 Device Data ...................................................................................................................... 226

Nortel Passport 8600............................................................................................ 227 Features Available ............................................................................................................. 227 Discovery/Identify Methods................................................................................................. 227 Configuration Capture ........................................................................................................ 228 Configuration Deploy.......................................................................................................... 228 Multi-Config Files ............................................................................................................... 228 Device Data ...................................................................................................................... 228 Known Issues.................................................................................................................... 229

PACKETEER DEVICES................................................................................ 230 Packeteer PacketShaper ....................................................................................... 230


PARADYNE DEVICES................................................................................. 233 Paradyne 9100.................................................................................................... 233

Features Available ............................................................................................................. 233 Discovery/Identify Methods................................................................................................. 233 Device Commands ............................................................................................................. 233 Known Issues.................................................................................................................... 233

RADWARE DEVICES.................................................................................. 234 Radware WSD Load Balancer................................................................................. 234


RIVERBED DEVICES.................................................................................. 237 Riverbed Steelhead.............................................................................................. 237


RIVERSTONE DEVICES ............................................................................. 240 Riverstone Router ................................................................................................ 240

Features Available ............................................................................................................. 240 Discovery/Identify Methods................................................................................................. 240



Configuration Capture ........................................................................................................ 240 Configuration Deploy.......................................................................................................... 241 Config Files ....................................................................................................................... 241 Device Data ...................................................................................................................... 241

SIEMENS DEVICES.................................................................................... 242 Siemens 5940 ..................................................................................................... 242

Features Available ............................................................................................................. 242 Multi-Config Files ............................................................................................................... 243 Device Data ...................................................................................................................... 243

STARENT DEVICES.................................................................................... 244 Starent PDSN...................................................................................................... 244


SYMBOL DEVICES..................................................................................... 246 Symbol WS-2000................................................................................................. 246

Features Available ............................................................................................................. 246 Discovery/Identify Methods................................................................................................. 247 Configuration Capture ........................................................................................................ 247 Configuration Deploy.......................................................................................................... 247 OS Management Notes ....................................................................................................... 248 Multi-Config Files ............................................................................................................... 248 Device Data ...................................................................................................................... 249

TASMAN DEVICES..................................................................................... 250 Tasman Router.................................................................................................... 250


TELCO DEVICES........................................................................................ 252 Telco Switch ....................................................................................................... 252


Telco T-Metro...................................................................................................... 255 Features Available ............................................................................................................. 255 Discovery/Identify Methods................................................................................................. 255 Configuration Capture ........................................................................................................ 256 Configuration Deploy.......................................................................................................... 256 Multi-Config Files ............................................................................................................... 256 Device Data ...................................................................................................................... 257 Known Issues.................................................................................................................... 257

VANGUARD DEVICES ................................................................................ 258 Vanguard Router ................................................................................................. 258

Features Available ............................................................................................................. 258 Discovery/Identify Methods................................................................................................. 258



Configuration Capture ........................................................................................................ 258 Configuration Deploy.......................................................................................................... 259 Multi-Config Files ............................................................................................................... 259 Device Data ...................................................................................................................... 259 Known Issues.................................................................................................................... 259

WHERE TO GET HELP................................................................................ 260 Where to get help ................................................................................................ 260

GLOSSARY................................................................................................ 261

INDEX ...................................................................................................... 262



PREFACE

Who Should Read this Document?

The information and procedures contained within this document are intended for those individuals who have the responsibility of installing and deploying devices and device drivers.

Readers should be familiar with the following:

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 Publication

EMC VoyenceControl Device Services Support (DSr) 11.0.0 Hotfix 2 - Patch Read Me

EMC VoyenceControl Device Server 11.0.0 - Configuration Guide



INTRODUCTION

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.

About this Manual

The following information is included in this Device Services Support document.

Device Driver Information

Device Driver Features and Information

Additions to Existing Device Drivers

Additional Device Driver Support

Device Issues

Additional Device Information

Compatibility

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

Red Hat Enterprise Linux 4

Microsoft Windows Server 2003 with Service Pack 1

Solaris 10



DEVICE DRIVER INFORMATION

New Device Drivers

The following are new Device Drivers included with this release:

Alcatel SR/ESS

Ciena Router

Cisco Intrusion Prevention System (IPS)

Force 10 – C-Series

Brocade McData

Modified Device Drivers

The following are Device Drivers that have been updated with this release:

Cisco IOS Switch Package

Cisco IOS XR

Juniper Router Package

Netscreen Firewall



Enabling Inactive Device Classes

To enable a device class that is not enabled by default, follow these steps.

Step Action 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.

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

7 Click Yes to confirm the changes.

8 Click Ok.

9 Click Close.

Viewing Installed Device Driver Packages

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

Step Action 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.

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.



3COM DEVICES

3Com Netbuilder II Router

Device Type Router

Specific Model(s) All Netbuilder II Models

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

Enabled By Default No

Configuration Change Notification (Events) Syslogs, SNMP Trap

Configuration Files running

Configuration Content ARP, Routes, Interfaces, Identity, System Properties

Configuration Protocols Telnet/TFTP, SSH/TFTP

User Interface CLI, SNMP

Discovery/Identify Methods SNMP

Password Management In-Band

Configuration Capture Telnet/TFTP, SSH/TFTP

Configuration Deploy Telnet/TFTP, SSH/TFTP

Cut-Through Access In-Band

Router Quick Commands Ping

Hardware Information Model, OS

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

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

running √

Device Data

The following data represents device data per device class.

Attributed Data Support

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 Switch 5500

Device Type Switch

Specific Model(s) 5500

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


Configuration Files Single ASCII

Configuration Content Quick Commands, Termlet Merge, Command, Configlet, Config

Configuration Protocols Telnet, SSH, Telnet/TFTP, SSH/TFTP

User Interface Command-Line Interface


Password Management In-band, SNMP

Operating System 3.02

Configuration Capture Telnet, SSH, Telnet/TFTP, SSH/TFTP


Cut-Through Access Telnet, SSH

Router Quick Commands Ping, Traceroute, View Routes, View Arp, View Interfaces

Hardware Information Memory, Serial Number, OS Version, Inventory

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



startup configuration can only be transferred via 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



Multi-Config Files



Running √

Startup √

Device Data




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


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.

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.

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.



ADTRAN DEVICES

Adtran Netvanta

Device Type Adtran Netvanta

Specific Model(s) 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

Documentation/Information -

Operating System 04.02.00, 05.02.00, 05.03.00, 06.01.00

Enabled By Default Yes

Configuration Files Single Text, Running, Startup

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

Configuration Protocols Telnet/TFTP, SSH Only, Telnet Only

User Interface IOS like

Discovery/Identify Methods SNMP, Telnet, SNMP

Password Management Enable, In-Band, SNMP

Configuration Capture Terminal, SSH, TFTP

Configuration Deploy Terminal, SSH, TFTP

Cut-Through Access Terminal

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

Features Available

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

Configuration Capture (Revision Configuration, Rollback, Basic Diagramming)

Configuration Deploy (Push Configurations, Configlets)


OS Upgrade


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

sysObjectID

1.3.6.1.4.1.664


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



Telnet/TFTP

copy startup-config tftp

copy running-config tftp

Telnet/SSH

show startup

show running

copy running-config startup-config

Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No

File System Information Yes

Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No

Physical Hardware Yes

Routes Yes



VLANs No



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.

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.



Adtran Netvanta Switch

Device Type Adtran Netvanta Switch

Specific Model(s) NetVanta 1224, NetVanta 1224R, NetVanta 1224 STR


Operating System 06.01.03


Configuration Files Single Text

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








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

Features Available



Configuration Deploy (Push Configurations, Configlets)


OS Upgrade



sysObjectID

1.3.6.1.4.1.664

adtranIfNumber

.1.3.6.1.2.1.2.1.0

Should be greater than 4





Telnet/TFTP



Telnet/SSH

show startup

show running


Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

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.



AIRESPACE DEVICES

Airespace Switch

Device Type Wireless Switch

Specific Model(s) Airespace Switch AS-4101



Configuration Files Binary Image

Configuration Content Binary

Configuration Protocols Telnet, TFTP, SSH

User Interface CLI

Discovery/Identify Methods SNMP Only

Password Management Account, SNMP

Operating System 2.0.152.3

Configuration Capture Terminal/TFTP, SSH/TFTP

Configuration Deploy Terminal/TFTP, SSH/TFTP, Terminal


Hardware Information For SNMP: Memory, Interfaces, Serial Number

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



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



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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.



ALCATEL DEVICES

Alcatel OmniCore

Device Type Alcatel Omnicore Routing Switch

Specific Model(s) 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




Configuration Content Termlet Merge, Privilege Mode Termlet, User Mode Termlet

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

User Interface Command Line


Password Management In-Band, SNMP




Hardware Information For SNMP: Memory, Interfaces

Features Available








SysObjectID

1.3.6.1.3.3003 or 1.3.6.1.4.1.3003

sysDesc

contains “Switch





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 Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Alcatel Omnistack

Device Type Switch

Specific Model(s) 6624, 6246, 8008

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



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





Operating System 1.0.0.47, 1.7.0.13


Configuration Deploy Telnet, SSH, Telnet/TFTP, SSH/TFTP


Switch Quick Commands Ping, Traceroute, View Interfaces, View Arp

Hardware Information Memory, Interfaces, Serial Number, OS Version, Inventory

Features Available


Configuration Capture (Revision Config, Basic Diagramming)

Device Access (Cut-Through, Termlets)

Credential Management (In-band, SNMP)



sysObjectId

contains 1.3.6.1.4.1.6486.800.1.1.2.2.4.1.1

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





Telnet, SSH:

show running-config

show startup-config

Telnet, SSH with TFTP:





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 Commands

Following 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

Password Management

(no) snmp-server community

(no) username

enable password level 15



Multi-Config Files



running √

startup √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes No



VLANs No

Known Issues


Alcatel Omnistack

Push-to-Start via Telnet/SSH not supported.

No volatile memory support via SNMP or command-line interface

Blank values are displayed in the client.



Alcatel Omniswitch

Device Type Switch

Specific Model(s) 6602-48, 6624

Documentation/Information CD-ROM Copy


Operating System 5.1.6.243.R01 GA, 5.1.6.393.R01 GA, 5.1.5.83.R04



Discovery/Identify Methods SNMP, SSH, Telnet

Password Management Account, SNMP

OS Management SSH/FTP, Telnet/FTP

Configuration Capture Telnet Only, SSH Only, Telnet/FTP, SSH/FTP

Configuration Deploy Telnet Only, SSH Only, Telnet/FTP, SSH/FTP

Cut-Through Access Terminal, SSH

Router Quick Commands View Interfaces, View Routes, View ARP, Ping, Traceroute

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

Features Available




Configuration Change Notification (SNMP Trap)

Credentials Management (Change or Roll passwords and SNMP Communities)

OS Management (Upgrade OS)

Dynamically Handled Sync (Stacked Devices)



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





For Terminal:

show configuration snapshot

For File Transfer:

Configuration is pulled using FTP



For Terminal:

Device commands are issued interactively from the stored configuration

Device Commands



show system

show running-directory

no more

ping

reload working no rollback-timeout

show arp

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



delete

freespace

ftp

hash

ls

Password Management

[no] snmp community map

[no] user

password

show snmp community map

show user

show user password-size

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No



Known Issues


Alcatel Omniswitch

Full configuration pushes require FTP to be enabled. Configlets use terminal mode only.

The running (RAM) configuration is always synced with the working (/flash/working/boot.cfg) configuration.

Copy to start must be performed manually.

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.

Full configuration files are currently distinguished from configlets in the driver by the presence of the filename header shown below.

!========================================!

! File: /flash/working/boot.cfg !

!========================================!



Alcatel Service Router and Ethernet Service Switch

Device Type Alcatel SR Router

Specific Model(s) 7750 SR-1, 7750 SR-7, 7750 SR-12 and 7450 ESS-1, 7450 ESS-7

Documentation/Information http://www.alcatel-lucent.com


Configuration Files Boot Options, Startup, Running

Configuration Content Quick Commands, Configlet, Termlet, Command, Config

Configuration Protocols SSH, Telnet, SSH/FTP, Telnet/FTP


Discovery/Identify Methods SNMP, Terminal

Password Management In-Band, SNMP v1, SNMP v2c

Operating System SR OS Release 5 (B-5.0.R8, C-5.0.R8)

Configuration Capture SSH, Telnet, SSH/FTP, Telnet/FTP

Configuration Deploy SSH, Telnet, SSH/FTP, Telnet/FTP


Router Quick Commands Traceroute

Hardware Information Chassis, Power

Features Available



Configuration Deploy (Push Configs)

Credential Roll (In-Band, SNMP)

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



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

Interface table via SNMP or Command-Line Interface





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 via 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 via FTP.

Configuration Activations

Following 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.

Multi-Config Files



Startup √

Running √

Boot-options-file √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes No



VLANs No

Known Issues


Alcatel Service Router and Ethernet Service Switch

The serial number can not be obtained via 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.



ALVARION DEVICES

Alvarion Breeze AP

Device Type Wireless Access Point

Specific Model(s) BreezeACCESS SU-A/E-BD

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


Configuration Files ASCII Capture (no push)

Configuration Content Config

Configuration Protocols Telnet

User Interface Menu


Password Management In-band


Configuration Capture Telnet

Cut-Through Access Telnet

Router Quick Commands Test Credentials

Hardware Information Chassis inventory

Features Available






sysName OID

sysServices: bit 3 set

brzAccUnitType (from Breeze-Access-MIB)



Main > Info > Advanced Configuration

Device Commands

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


Advanced Configuration



Password Management

Unit Control

Multi-Config Files



running √

Device Data




ARP Table No

CAM Table No

Device Identity Yes


Hardware Information No

Interfaces Yes

Keys No

Memory Yes


Static Routes No


VLANs No


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.



ARUBA DEVICES

Aruba Wireless Switch

Device Type Aruba Switch

Specific Model(s) a52, a50, a800, a2400, a5000, Alcatel OAW-6000



Configuration Change Notification (Events) Syslog, SNMP Traps


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

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



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



Hardware Information Memory, Interfaces, Serial Number, OS Version

Features Available








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





Telnet


Term

show startup

show run



TFTP



Term

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

Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



BLUECOAT DEVICES

BlueCoat SG

Device Type Content Cache

Specific Model(s) Web Proxy

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




Configuration Protocols SSH, Telnet, SSH/TFTP, Telnet/TFTP





Configuration Capture SSH, Telnet, SSH/TFTP, Telnet/TFTP

Configuration Deploy SSH, Telnet, SSH/TFTP, Telnet/TFTP


Quick Commands Traceroute, View Interfaces, View Arp, View Routes

Hardware Information Serial Number, OS Version, Inventory

Features Available




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

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

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





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”

Multi-Config Files



running √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No



Known Issues


BlueCoat SG

No volatile or non-volatile storage information is available via 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



BROCADE DEVICES

Brocade 7500

Device Type Router


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



Configuration Content Privilege Mode Termlet, User Mode Termlet, Configlet

Configuration Protocols SSH, Telnet





Configuration Capture Telnet, SSH


Hardware Information Interfaces, Serial Number, OS Version, Hardware Inventory

Features Available




Credential Management (In-Band, SNMP)



sysObjectID

1.3.6.1.4.1.1588.2.1.1.1



configShow

Device Commands

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

Device Configuration

configShow

switchShow



Password Management

snmpConfig --show snmpv1

snmpConfig --set snmpv1

passwd

userConfig --add

userConfig --delete

Multi-Config Files



running √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

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 via SNMP for this device class.



Brocade McData

Device Type Switch

Specific Model(s) 010000, 004500, 006064, 006140


Configuration Files ASCII Capture (no push)

Configuration Content Config

Configuration Protocols Telnet, SSH



Operating System 9.6.1.5, 9.2.0.8, 09.02.01, 05.01.00



Router Quick Commands Test Credentials

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

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





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 Issues

The 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.



CHECKPOINT DEVICES

Checkpoint Firewall-1

Device Type Checkpoint Firewall-1 Only

Specific Model(s) Various

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


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

Configuration Files Multiple Text, Multiple/Complex

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

Configuration Protocols SSH/SCP, SSH Only




Configuration Capture Terminal, SSH, FTP, SCP

Configuration Deploy SSH, FTP, SCP


Firewall Quick Commands 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

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

Features Available









OID 1.3.6.1.4.1.2620.1.1.10.0

FireWall-1



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

The files listed in the Multi-Config Files section for this device are pushed via 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 via 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 via 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

$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

$base_dir/conf/sic_policy.conf √ Text Yes

$base_dir/database/cprid/cprid_keys/*

√ Binary

$base_dir/database/cprid/cprid_util_keys/*

√ Binary



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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.



CIENA DEVICES

Ciena Router

Device Type Router


Documentation/Information ciena.com


Configuration Files ASCII/Binary

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

Configuration Protocols Telnet, SSH, Telnet/FTP, SSH/FTP

User Interface Command line

Discovery/Identify Methods Non-SNMP


Configuration Capture Telnet/FTP, SSH/FTP

Configuration Deploy Telnet/FTP, SSH/FTP

Cut-Through Access In-band

Quick Commands Standard

Hardware Information Identity, System Properties, Interfaces, Inventory

Features Available


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





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



running √

change log √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No



Known Issues


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.



CISCO DEVICES

Cisco Aironet AP VXWorks

Device Type Cisco Aironet AP VXWorks

Specific Model(s) 340 VXWork, 1200 AP




Configuration Protocols HTTP/TFTP



Configuration Capture Terminal



Features Available





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.

Multi-Config Files



running √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Cisco PIX Firewall

Device Type Cisco Pix Firewall

Specific Model(s) 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

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





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


Discovery/Identify Methods SNMP (not available for FWSM and ASA models), Terminal


Operating System 6.3, 7.0, 7.2


Configuration Deploy Terminal, SSH


OS Management TFTP

Firewall Quick Commands SetTrapDest, Test Credentials, Setup Diagnostics, View Diagnostics Setup, Setup NAT, View NAT Setup

Hardware Information For SNMP: Memory, Interfaces For Non-SNMP: Memory, Interfaces, Serial Number, OS Version

Features Available










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 via 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 via Terminal. Enter enable mode, enter configuration mode, and send one configuration line at a time.

Device Commands



show checksum

show version

show pager

show config

show start

show run

show snmp contact

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

Password Management

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"

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 √

Device Data



ARP Table Yes

Access Control Lists Yes

CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Known Issues


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.

OS Upgrade for PIX 515 (version 6.x)

This IOS series does not support commands for listing flash size or contents; the user must ensure sufficient space exists before scheduling the upgrade. Upgrading from version 6.x to version 7.x 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 via 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.

Cisco PIX – SNMP Discovery

SNMP discovery is not available for FWSM and ASA models.



Cisco VPN 3000

Device Type VPN concentrator


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




Configuration Content Command, Config

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




Operating System OS Upgrade

Configuration Capture FTP, SCP

Configuration Deploy FTP, SCP


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

Features Available








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



A terminal session is used to navigate the following menu

Administration



File Management

Export XML File

Exported file name 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



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No



Cisco Aironet AP Package

Device Type Cisco Aironet Access Point

Specific Model(s) 1100, 1130, 1200, 1210, 1240, 1310, 350IOS

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




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

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

User Interface IOS, SNMP Only


Password Management AAA, In-Band, SNMP

Configuration Capture Terminal, TFTP

Configuration Deploy Terminal, TFTP



Features Available






http://www.cisco.com/





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

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



show start for startup configuration

show run for running configuration

SNMP for the running configuration only

set oid .1.3.6.1.4.1.9.2.1.55.IP to the TFTP server’s file name

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 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


.1.3.6.1.4.1.9.2.1.50.IP = file name 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

Copy running-config startup-config



Multi-Config Files



running √

startup √

Device Data



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



VLANs No



Cisco Aironet Bridge Package

Device Type Cisco Aironet Wireless Bridge

Specific Model(s) 1300, 1410

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





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








Features Available








SysObjectIDs

1.3.6.1.4.1.9.1.533

SysDescription Contains IOS










set oid .1.3.6.1.4.1.9.2.1.55.IP to the TFTP server’s file name


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.

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.

SNMP for the running configuration only:



To copy run to start from command line:


Multi-Config Files



running √

startup √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Cisco Application Control Engine

Device Type Cisco Application Control Engine

Specific Model(s) ACE20-MOD-K9

Documentation/Information www.cisco.com

Enabled By Default -


Configuration Files running, startup

Configuration Content Quick Commands, Termlet, Command, Configlet, Config






Configuration Capture SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only

Configuration Deploy SSH/TFTP, Telnet/TFTP, SSH Only, Telnet Only


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

Hardware Information Hardware Inventory, Memory, Interfaces, Serial Number

Features Available








Model, Serial Number, MAC and OS version via SNMP or command-line interface.

Filesystem and Memory via command-line interface.

Interface table via SNMP or command-line interface.





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 √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes

Known Issues


Cisco ACE

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



Cisco BPX

Device Type Multi-Service Switch

Specific Model(s) BPX 8620

Documentation/Information Cisco Provided


Configuration Files Binary capture to file system only

Configuration Content Binary, Command-Line Interface



Discovery/Identify Methods SNMP or Telnet

Configuration Capture Binary file set via TFTP

Configuration Deploy Configuration via Configlet only

Cut-Through Access Telnet only

OS Management Not currently supported

Router Quick Commands 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 Information Hardware provided via Terminal commands

Features Available

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

Incremental Updates (via Configlet or Device Commands)

Hardware and Interface Information

Backup to Archive File

SSH and Telnet Support

Device Access (Cut-Through, Device Commands)

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

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.



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.

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 via Cut-Through

Issue: The BPX in a split screen VT100 interface. Screen painting and redrawing issues may occur via 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 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









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







OS 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 Number For Non-SNMP: Hardware Inventory, Memory, Interfaces, Serial Number

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





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.


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


enable

disable

conf term

clear boot auto-config

set boot auto-config bootflash:

show ip

show snmp group

show snmp contact

show snmp hostname

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: ...

OS Management

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

Password Management

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 ...

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"

Multi-Config Files



running √



Device Data



ARP Table Yes


CAM Table Yes


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes

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.

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 Content Appliance

Device Type Cisco Content Appliance

Specific Model(s) 507, 511, 512, 560, 565, 566, 590, 611, 612, 7305, 7320, 7326





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

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

User Interface IOS-like



Configuration Capture Telnet, SSH, TFTP

Configuration Deploy Telnet, SSH, TFTP


Router Quick Commands View Interfaces, View ARP, Ping, TraceRoute, Resync, View CDP Neighbors, Resync,

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

Features Available

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






SNMP: the model name is obtained from the following oids (in the order tried):

.1.3.6.1.4.1.9.9.368.1.34.3.0 or .1.3.6.1.4.1.2467.1.34.3.0 (based on availability)

Part number column of the ENTITY-MIB for the chassis entry

Terminal: the model name is parsed for the non-blank field following ModelNum (text): in the show hardware output

The result must begin with CE, CD, or CT





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



running √

startup √



Device Data



ARP Table Yes


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes Yes



VLANs No

Known Issues


Cisco Content Appliance

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.



Cisco Content Services Switch

Device Type Cisco Content Services Switch

Specific Model(s) 11050, 11501, 11503, 11506













Router Quick Commands View Interfaces, View ARP, Ping, TraceRoute, Resync, View Interfaces, View CDP Neighbors, Resync,

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

Features Available







sysDescription

Search for Content Switch or Application and Content Networking



show startup-config for startup configuration

show running-config for running configuration

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.

For Telnet/TFTP user the following command:

copy tftp SERVERIPADDR localFile startup-config



Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Cisco Router

Device Type Cisco Router

Specific Model(s) 1700, 1711, 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 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 3000, 3825, 3101, 3102, 3103, 3104, 3202, 3204, 3845, 3620, 3640, 3251, 3660, 3661Ac, 3661Dc, 3662Ac, 3662Dc, 3662AcCo, 3662DcCo, 3631, 3745, 3725, 3220 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 AIR-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



Configuration Change Notification (Events)

Syslog, SNMP Traps



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




Operating System Boot Upgrade, OS Upgrade

Configuration Capture SSH/Terminal, TFTP

Configuration Deploy SSH/Terminal, TFTP


Router 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 Number For Non-SNMP: Memory, Interfaces, Serial Number, Hardware Inventory



Features Available




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





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

show version response contains Internetwork Operating System or Cisco IOS



For Terminal:

startup configuration : show start

running configuration: show run

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)

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

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





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


OS Management

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:...

Password Management

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

show logging

show cdp neighbors detail

show frame-relay map

show diag

Multi-Config Files



running √

Startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs No



Known Issues


Cisco IOS - Out-of-Sync

When a SNMP/TFTP mechanism is used with only a Community String credential, the Running vs. 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 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.

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:

1. Copy the file VOYENCE_HOME/package/stdfuncs to

VOYENCE_HOME/custompackage/stdfuncs.inc (the main one).

2. Next, follow these steps:

• 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 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, 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, 9009 WS-C3750-48TS



Configuration Change Notification (Events)

Syslog, SNMP Traps

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




Operating System Boot Upgrade, OS Upgrade






OS Management Terminal, TFTP

Router Quick Commands View 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 Number For Non-SNMP: Hardware Inventory, Memory, Interfaces, Serial Number

Features Available


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:

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

.1.3.6.1.4.1.9.2.1.55.ipAdress -> remoteFilename

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



show run

show start

show version

show config

show interfaces

configure term

terminal length 0

exit

write memory

reload







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


OS Management

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:...

Password Management

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"

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

Multi-Config Files



running √

Startup √

Vlan.dat √

Vlan text √



Device Data



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

Known Issues


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.

Cisco IOS - Out-of-Sync

When a SNMP/TFTP mechanism is used with only a Community String credential, the Running vs. 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:

1. Copy the file VOYENCE_HOME/package/stdfuncs to

VOYENCE_HOME/custompackage/stdfuncs.inc (the main one).

2. Next, follow these steps:

• 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 IOS XR

Device Type Cisco IOS XR Network Operating System

Specific Model(s) CRS-1, 12000XR Series


Configuration Change Notification (Events) Syslog, SNMP Traps (disabled by default)

Configuration Files Text based running config and admin config






Operating System Version 3.4 and higher




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

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

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

Features Available




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



For SSH/TFTP and Telnet/TFTP:

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

For SSH and Telnet

show running-config




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.

OS Upgrade

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.

Multi-Config Files



Running √

Admin √

Packages √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No

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.



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.




Device Type Cisco Intrusion Prevention System

Specific Model(s) IPS-4255-K9




Configuration Files Running







Configuration Capture SSH, Telnet

Configuration Deploy SSH, Telnet


OS Management Yes

Router Quick Commands Ping, Traceroute, Show diag


Features Available






OS Management System (Used to update signature files)



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

Memory via Command-Line Interface

Interface table via SNMP or Command-Line Interface





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 √

Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Known Issues



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 Lightstream Package

Device Type Cisco Lightstream ATM Switch

Specific Model(s) LS 1010, LS 1015

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





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








Features Available








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









set OID .1.3.6.1.4.1.9.2.1.55.IP to the TFTP server’s file name







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.





To copy run to start from command line


Multi-Config Files



running √

Startup √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Cisco MGX


Specific Model(s) 8850 Wide Area Switch - MGX 8850 PXM-45 and MGX 8250 PXM-1

Documentation/Information Cisco Provided


Configuration Files Binary backup to file system of compressed archive

Configuration Content Binary, Command-Line Interface

Configuration Protocols SSH or Telnet


Discovery/Identify Methods SNMP, Telnet, or SSH

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


Configuration Capture Compressed Tar Archive via FTP

Configuration Deploy Compressed Tar Archive via FTP, Device Commands, Configlets

Cut-Through Access Telnet on PXM-1, SSH on PXM-45

Router Quick Commands 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 Information Hardware provided via SNMP using Entity MIB or Terminal

Features Available

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

Incremental Updates (via Configlet or Device Commands)

Hardware and Interface Information

Backup and Restore from Archive File

SSH and Telnet Support

Device Access (Cut-Through, Device Commands)

Quick Commands





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 via 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.



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 SRM Slot Number (optional) of type Integer.

Display IMA Groups- Runs the dspimagrps command.


Display IMA Group Counters – Runs the dspimagrpcnt supplying the bay.group and interval.


• 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 Interface Number of type Integer.

• Parameter IMA Member Link of type Integer.

Display Alarms – Runs the dspalms command.


Display Hardware Alarms – Runs the dsphwalm command.


Display Software Alarms – Runs the dspswalm command.


Display Port Counters – Runs the dspportcnt command providing the interface number and interval.


• 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 Interface Number of type Integer.

Display Ports – Runs the dspports command.


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 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.

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 MDS

Device Type Cisco MDS

Specific Model(s) 9124, 9134, 9216, 9216A, 9216i, 9509, 9513

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







Password Management Command-Line Interface

Operating System San-OS 3.0, 3.2, 3.3

Configuration Capture Terminal, file transfer

Configuration Deploy Terminal, file transfer


Router Quick Commands Yes

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

Features Available

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


Configuration Deploy (Push Configs, Configlets, Termlets)

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





For Terminal:

show running-config

show startup-config

For File Transfer:

copy running-config tftp: (unverified)

copy startup-config tftp: (unverified)



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

Password Management

[no] snmp-server community

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

username

Multi-Config Files



running √

startup √



Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No



Cisco Wireless LAN Controller

Device Type Cisco Wireless LAN Controller

Specific Model(s) AirWlc2106K9




Configuration Files running, readable







Configuration Capture Running via tftp Readable via terminal

Configuration Deploy Running via tftp


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


Features Available








Model, Serial Number, MAC and OS version via SNMP or the command-line interface.

Filesystem and Memory via the command-line interface.

Interface table via SNMP or the command-line interface.





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

Running config is retrieved via 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 via the devices transfer download command.

Multi-Config Files



Running √

Readable √



Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Known Issues


Cisco Wireless LAN Controller

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 via the configlet mechanism.



CITRIX DEVICES

Citrix Netscaler LoadBalancer

Device Type Citrix Netscaler LoadBalancer

Specific Model(s) 7000, 9000, 10000, 12000

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



Configuration Files Multiple Text and Binary


Configuration Protocols SSH/SCP, SSH, Telnet




Operating System 6.0 or greater

Configuration Capture SSH/SCP, SSH, Telnet

Configuration Deploy SSH/SCP, SSH, Telnet


Router Quick Commands Ping, Resync

Hardware Information For SNMP: Interfaces

Features Available








SysObjectIDs: 1.3.6.1.4.1.5951.1.*

OS version in sysDescr at least v6.0

Interface table from MIB-2



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



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



D-LINK DEVICES

D-Link xStack

Device Type Switch


Documentation/Information ftp://ftp.dlink.com/Switch/des3550/Manual/



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






Configuration Capture SSH, Telnet

Configuration Deploy SSH, Telnet


Switch Quick Commands View Interfaces, View ARP, View Routes, Ping

Hardware Information Memory, Interfaces, Serial Number OS Version

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

ftp://ftp.dlink.com/Switch/des3550/Manual/





Telnet/SSH:

Commands are issued to the command-line interface.

Results are scanned for errors.

Multi-Config Files



running √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

Known Issues


D-Link xStack

No volatile or non-volatile storage information is available via SNMP, for this device class.

User accounts are defined at administrator level.



EDGEWATER DEVICES

Edgewater EdgeMarc Router

Device Type Edgewater EdgeMarc Router

Specific Model(s) 4200, 4300T, 4500, 5300, 6400

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






User Interface CLI, SNMP Only


Password Management Enable, In-Band




Router Quick Commands View Routes, View ARP, Ping, TraceRoute, Reboot, View Interfaces


Features Available








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






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 √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No



ENTERASYS DEVICES

Enterasys Smartswitch Router

Device Type Router

Specific Model(s) XP 2400

Documentation/Information http://secure.enterasys.com/support/manuals/


Operating System E10.0.0.3A

Configuration Change Notification (Events) SysLog, Trap



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




Configuration Capture Telnet Only, SSH Only, Telnet/TFTP, SSH/TFTP

Configuration Deploy Telnet only, SSH only, Telnet/TFTP, SSH/TFTP


Quick Commands Standard

Hardware Information Serial Number, OS Version, Memory, Inventory

Features Available

Discover/Identify (Autoo Discovery, Identify, Appear in Product)



Configuration Change Notification (Syslog, SNMP Trap)



For SNMP:

sysDescr contains Enterasys






For Telnet and SSH:

Running:

• system show active

Startup:

• system show startup


Running:

• copy active to tftp://ipAddress/remoteFilename

Startup:

• copy active to tftp://ipAddress/remoteFilename



For Telnet and SSH:

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

Device Commands



cli set command completion off

cli terminal monitor off

cli set terminal rows 0

system show active

system show startup

copy scratchpad to active

copy scratchpad to startup

enable

exit

copy active to startup

configure



reboot

Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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 via Telnet or SSH.

The presence of the last modified comment is used to distinguish full configurations from configlets.



ERICSSON DEVICES

Ericsson MSED

Device Type Router/Edge Device

Specific Model(s) MSED/HL950

Documentation/Information www.ericsson.com



Configuration Files Binary Running Config, Text Running Config

Configuration Content ARP, Routes, Interfaces, Identity, System Properties

Configuration Protocols Telnet/TFTP, SSH/TFTP








Hardware Information Model, Operating System, Serial Number

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





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

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No



EXTREME DEVICES

Extreme

Device Type Extreme Switch

Specific Model(s) 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 24E3 Summit 7iSX, Summit 7iTX, Summit 1iTX, Summit 5i, , Summit 1iSX, Summit 5iLX, Summit 5iTX, , Summit 48SI, Summit PX1, Summit 24E2TX, Summit 24E2SX

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


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

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





Configuration Capture TFTP, Terminal

Configuration Deploy TFTP, Terminal


OS Management TFTP

Router Quick Commands Ping, TraceRoute




Features Available








sysObjectID

contains 1.3.6.1.4.1.1916.2

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



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 via Telnet to Extreme Switch - Unsuccessful

Issue: Pushing an entire configuration to the Extreme Switch should not be executed via 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 via a text editor.

You can push a full configuration via 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 can not be the configuration using this mechanism.



ExtremeWare XOS

Device Type Switch

Specific Model(s) BlackDiamond 10808, 12804

Documentation/Information www.extremenetworks.com


Configuration Files Single XML


Configuration Protocols SSH, Telnet, Telnet/TFTP, SSH/TFTP



Password Management SNMP, Account





Hardware Information Memory, Interfaces, Serial number, OS version, Inventory

Features Available




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

http://www.extremenetworks.com/





tftp ipAddress –g –l localFilename –r remoteFilename

Multi-Config Files



running √

startup √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory Yes



Static Routes No



VLANs No

Known Issues


ExtremeWare XOS

Configuration management is not supported if TFTP is not enabled for the device class.

Configuration pushes have not been certified.



F5 DEVICES

F5 Load Balancer Rev 3

Device Type Load Balancer

Specific Model(s) Big-IP-HA, Big-IP-LB, Big-IP-3-DNS, Big-IP-FLB, Big-IP-CLB, Big-IP-XLB, Big-IP-SSL

Documentation/Information www.askf5.com (registration required)


Configuration Change Notification (Events) Syslog, Trap

Configuration Files Multiple Complex (Linux based)

Configuration Content Termlet Merge, Privilege Mode Termlet, Configlet

Configuration Protocols Telnet, SSH, Telnet/FTP, SSH/FTP, SSH/SCP

User Interface CLI


Password Management Telnet, SSH

Operating System 3.x

Configuration Capture Telnet/FTP, SSH/FTP, SSH/SCP

Configuration Deploy Telnet/FTP, SSH/FTP, SSH/SCP


Router Quick Commands Test Credentials, Ping, Traceroute, View Routes, View Arp, View Interfaces, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup, Clear Cache

Features Available


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

Configuration Deploy (Push Configs, Configlets, Termlets)




sysObjectID: .1.3.6.1.4.1.3375.1.1

http://www.askf5.com/





The configuration file units in the package/pkgxml/F5_30/F5_R9.xml file are retrieved via a combination of SSH and SCP commands.




The configuration file units in the package/pkgxml/F5_9x/F5_R9.xml file are transferred via a combination of SSH and SCP commands.


Device Commands



df

mount

ls

ifconfig

ping

traceroute

arp

netstat

File Management

cd

cp

md5sum

Password Management

grep

passwd

cat

bigstart restart snmpd



Multi-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



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No




Device Type F5

Specific Model(s) BigIP HA, BigIP LB, BigIP 3-DNS, BigIP FLB, BigIP CLB, BigIP XLB, BigIP SSL

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


Configuration Change Notification (Events) Syslog, Traps



Configuration Protocols SSH/SCP, SSH/FTP, Telnet/FTP




Configuration Capture SSH/SCP, Telnet/FTP

Configuration Deploy SSH/SCP, Telnet/FTP

Cut-Through Access SSH


Features Available








sysObjectID

1.3.6.1.4.1.3375.1.1








SCP or FTP is used to put the pulled files back into place.


Multi-Config Files



Pull Only


/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

/config/ssh/ssh_host_key √ Binary Yes

/config/user.db √ Binary Yes

/config/ipfw.filt √ Binary Yes



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No





Specific Model(s) BIG-IP 1500, BIG-IP 3400

Documentation/Information www.askf5.com (registration required)


Configuration Change Notification (Events) Syslog, Traps

Configuration Files Multiple Complex (Linux based)




Discovery/Identify Methods SNMP, SNMP/Terminal

Password Management 1st Level ID, SNMP Read-Only, SNMP Read-Write, Terminal Only, SSH, Telnet

Operating System 9.1.2 40.2

Configuration Capture Non-SNMP

Configuration Deploy SCP

Cut-Through Access SNMP, SSH

OS Management SSH/FTP

Router Quick Commands View Interfaces, View Routes, View ARP, View Diagnostic, Resync, diffRunStart

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

Features Available








Standard MIB II System Values

http://www.askf5.com/



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.


Device Commands



df

mount

ls

ifconfig

ping

traceroute

apr

netstat

im

local-install

File Management



cd

cp

md5sum

Password Management

grep

passwd

cat

bigstart restart snmpd

Multi-Config Files



Pull Only


/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

/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

/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



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



FORCE10 DEVICES

Force10 C-Series Router

Device Type Force10 C-Series Router

Specific Model(s) C150, C300

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



Configuration Files Startup, Running






Operating System FTOS v7.9




Router Quick Commands Ping, Traceroute, View Routes, View ARP, Resync

Hardware Information Chassis, Card, Port, FanTray, Power, Processor, RPMs, SFModules

Features Available




Credential Roll (In-Band)







Model, Serial Number and Operating System version via SNMP or command-line interface

Filesystem and Memory via command-line interface

Interface table via SNMP or command-line interface



For SSH or Telnet:

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.



For SSH or Telnet:

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.

Multi-Config Files



Startup √

Running √



Device Data



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

Device Type Force10 E-Series Router

Specific Model(s) E150, E300, E600, E610, E1200

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






User Interface FTOS, SNMP Only





Router Quick Commands View Routes, View ARP, Ping, TraceRoute, Resync, View Interfaces

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

Features Available








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.*)






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



running √

startup √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



FOUNDRY DEVICES

Foundry EdgeIron

Device Type Switch

Specific Model(s) EdgeIron 48G

Documentation/Information www.foundrynetworks.com


Configuration Files ASCII










Router Quick Commands Ping, View Interfaces

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

Features Available


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



show running-config

show startup-config


copy startup-config-tftp

http://www.foundrynetworks.com/



Multi-Config Files



running √

running √

Device Data




ARP Table No

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory No


Static Routes No


VLANs No


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 via 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 via the command-line interface.

Certain configuration commands do not merge, and issue Failed to set warnings.



Foundry Package

Device Type Foundry Router

Specific Model(s) BigIron 4000, ServerIron, IronWare, FastIron 400, FastIron 15000, FastIron 800

Documentation/Information www.foundrynetworks.com



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


User Interface IOS like, Command-Line Interface






Router Quick Commands ping


Features Available



Configuration Deploy (Push Config)

Configuration Updates (Push Configlet, TERMlets Merges)




Discovery/Identify Device


SysObjectID

Layer 3 device

1.3.6.1.4.1.1991

SysDescription contains Foundry Networks






copy running-config tftp ipAddress remoteFilename

copy startup-config tftp ipAddress remoteFilename

For Telnet and SSH:

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

For Telnet and SSH:

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)

Device Commands



configure terminal

copy run

copy start

disable

enable

page

ping

reload

show configuration

show run

skip-page

username



write memory

File Management

tftp

copy tftp

Password Management

[no] enable super-user-password


[no] username oldUser

Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No



HP DEVICES

HP ProCurve Switch

Device Type HP ProCurve Switch

Specific Model(s) 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



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





Configuration Capture Terminal, SSH, SCP

Configuration Deploy Terminal, SSH, TFTP, SCP




OS Management FTP, TFTP, SCP

Hardware Information For SNMP: Hardware Inventory, Memory, Interfaces

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

show running

show ver



show version

terminal width

write memory

reload

ping

traceroute

File Management

copy tftp

Password Management

password


[no] snmpv3 group

[no] snmpv3 user

Multi-Config Files



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys Yes

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs Yes



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, via the terminal protocol, provides a warning but can not 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, via 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

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 via 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 via 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.



JUNIPER DEVICES

Juniper ERX (E Series)

Device Type Juniper ERX Series

Specific Model(s) ERX-310

Documentation/Information http://www.juniper.net/techpubs/software/erx/



Configuration Files Binary and Text


Configuration Protocols SSH, Telnet, SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP



Operating System JunOSe v8.2 and 9.1

Configuration Capture Text via SSH, Telnet, SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP Binary via SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP

Configuration Deploy Text via SSH, Telnet Binary via SSH/TFTP, Telnet/TFTP, SSH/FTP, Telnet/FTP


Router Quick Commands Ping, Traceroute, View Routes, View ARP, View Interfaces, View Processes, View Diagnostic, Show SNMP Delta

Hardware Information Chassis, Slot/Card Inventory, Interfaces, Power, Fans, FileSystems

Features Available



Configuration Deploy (Push Configurations)







Model, Serial Number, MAC and OS version via SNMP or Command-Line Interface

Filesystem and Memory via the Command-Line Interface

Interface table via 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 via 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 via Telnet or SSH alone.



For a Binary configuration:

The configuration file will be transferred to either the root or /incoming directory via 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.



Multi-Config Files



Text √

Binary √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No

Known Issues


Juniper ERX

The Binary config cannot be pushed or pulled via Telnet or SSH alone.

When entering a Text config via 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



Juniper Router Package

Device Type Juniper Router

Specific Model(s) J2300, J4300, J6300, M40, M20, M160, M10, M5, M40e, M320, M7i, M10i, M120, MX960, TX, T640, T320,

Documentation/Information http://www.juniper.net/





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





Configuration Capture Terminal, FTP, SCP

Configuration Deploy Terminal, FTP, SCP


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

Features Available










sysObjectID

Contains 1.3.6.1.4.1.2636

Or

ShowVerion contains (JUNOS)



set more paging off with set cli screen-length 0

Then do show configuration

For Telnet/FTP or Telnet/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 TFTP or SCP to attach and retrieve configuration file voyence.cfg



For Term/FTP or SCP

FTP or SCP file to device from pull

Use the command load merge voyence.cfg to restore the configuration

Multi-Config Files



running √

xml-config √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys Yes

Memory Yes


OSPF Settings Yes


Routes Yes



VLANs Yes

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 Switch (EX Series)

Device Type Juniper EX Series

Specific Model(s) EX3200, EX4200

Documentation/Information http://www.juniper.net/techpubs/en_US/release-independent/junos/ information-products/pathway-pages/ex-series/product



Configuration Files Text and XML


Configuration Protocols SSH, Telnet, SSH/FTP, Telnet/FTP SSH/SCP




Operating System JunOS v9.2 and 9.3

Configuration Capture Text via SSH, Telnet, SSH/FTP, Telnet/FTP, SSH/SCP XML via SSH, Telnet

Configuration Deploy Text via SSH, Telnet, SSH/FTP, Telnet/FTP, SSH/SCP


OS Management Not supported

Router Quick Commands Ping, Traceroute, View Routes, View ARP, View Interfaces, View Processor, View Diagnostic, Clear Cache

Hardware Information Chassis, FPCs, PICs, Power, Fans, Interfaces, Memory, FileSystems

Features Available










Model, Serial Number, MAC and OS version via SNMP or the Command-Line Interface

Filesystem and Memory via the Command-Line Interface

Interface table via SNMP or the Command-Line Interface



For Text (running) config via 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 via Telnet or SSH:

Using the command-line interface, issue the show configuration command.

Capture the command-line interface output.

For XML config via Telnet or SSH:

Using the command-line interface, issue the show configuration | display xml command.

Capture the command-line interface output.



Via FTP or SCP:

The configuration is transferred to the switch via FTP or SCP.

Using the command-line interface, issue the load merge [filename] command.

Via Telnet or SSH:

Using the command-line interface in configuration mode, issue the load mege terminal command.

The config is sent to the command-line interface session as one text block.

Following the file merge, the commit or commit synchronize commands can be used. This is optional.

Multi-Config Files



Text √

XML √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Known Issues


Juniper EX

When managing a stack of EX4200s, the system properties and hardware are shown for the master switch only.



LAUREL DEVICES

Laurel ST Router

Device Type Router

Specific Model(s) ST200





Configuration Protocols SSH/SCP




Operating System 3.1.1R2.1

Configuration Capture SSH/SCP

Configuration Deploy SSH/SCP


Hardware Information Interfaces, Serial Number, OS Version, Inventory

Features Available


Configuration Management (Revision Config, Basic Diagramming)





sysObjectId

Contains 1.3.6.1.4.1.5395.1.1.1.1.1

sysDescr

Contains Laurel



show configuration | save vc-running.txt

File vc-running.txt is transferred via SCP to the server.

file delete vc-running.txt





File push-configType-deviceId.cmd is transferred via 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 √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



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 via SNMP for this device class.



LUCENT DEVICES

Lucent Access Point

Device Type Lucent Access Point

Specific Model(s) 300, 450, 600, 1000 (only 300 and 450 have been tested)

Documentation/Information www.alcatel-lucent.com



Configuration Content Termlet Merge, Privilege Mode Termlet, User Mode Termlet

Configuration Protocols SSH Only, Telnet Only




Configuration Capture Terminal, SSH, SSH/SCP, Terminal/FTP




Features Available








sysDescr

contains Lucent Access Point



gen-script all

Add system file–transfer-info.8 source dest NVRAM





Configs can be pushed using SSH/Telnet, SCP, or TFTP

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



MARCONI DEVICES

Marconi ASX

Device Type Switch

Specific Model(s) ASX-1000

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


Configuration Change Notification (Events) SNMP Traps, Syslog

Configuration Files ASCII (Config Representation), Binary (Backup/Restore)


Configuration Protocols Telnet/TFTP





Configuration Capture Telnet/TFTP

Configuration Deploy Telnet/TFTP


Quick Commands Ping, View Routes, View ATM ARP, View LEC ARP, View Interfaces

Hardware Information Interfaces, Serial Number, OS Version

Features Available







sysObjectId

.1.3.6.1.4.1.326.2.2

sysServices

Bit 2 set





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



system cdb [ backup | restore ]

system ping

interfaces ip show

interfaces ip route show

services atmarp show

interfaces lec arp show

Password Management

security login [ new | delete | password ]

password

Multi-Config Files



readable √

running √



Device Data




ARP Table No

CAM Table No

Device Identity Yes



Interfaces Yes

Keys No

Memory No


Static Routes No


VLANs No


Known Issues


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.



MCAFEE DEVICES

McAfee IntruShield

Device Type Other

Specific Model(s) I4000

Documentation/Information www.mcafee.com


Configuration Content Configlet, Termlet Merge, Termlet Privilege Mode









Hardware Information Serial Number, OS Version, Interfaces, Inventory

Features Available




Credential Management (In-Band)



sysObjectId

Contains 1.3.6.1.4.1.8072.3.2.10



show

show ssl config

show tacacs



Multi-Config Files



running √

Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

Known Issues


McAfee IntruShield

There is no volatile or non-volatile storage information available via 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



MILAN DEVICES

SM801P Managed Switch

Device Type Milan

Specific Model(s) SM801P, SME801P

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


Configuration Files Single, Binary

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

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

User Interface Menu Driven, Web Based


Password Management In-Band, Terminal

Operating System SM801P-V117, SM801P-V118, SME801P-V200

Configuration Capture Terminal, SNMP

Configuration Deploy Terminal, SNMP

Cut-Through Access Telnet Only

OS Management HTTP/TFTP

Switch Quick Commands View VLAN, Device Uptime, Device Info

Hardware Information For SNMP: Hardware Inventory, Serial Number, Model, OS Version For Non-SNMP: Serial Number, Model, OS Version For HTTP: Supplemental, Serial Number, Model, OS Version

Features Available











System Object ID

enterprises.835.25.1.1.1.1

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes Yes



VLANs No



MOTOROLA BSR

Motorola BSR Router

Device Type Router

Specific Model(s) BSR64000 (BSR1000 and OSR2000 may be supported; unverified)

Documentation/Information Customer Supplied


Configuration Files running, startup

Configuration Content ASCII

Configuration Protocols Telnet, SSH, TFTP

User Interface Command-Line



Operating System 3.1.1.14P03C.KRCU 4.2.0.08P07.H20.KRCU


Configuration Deploy Terminal


OS Management TFTP

Router Quick Commands View Interfaces, View Routes, Ping, Traceroute, View ARP, Clear Interface Counters, View Processor CPU, Resync

Hardware Information Memory, Non-Volatile Storage, Card Inventory

Features Available




Credentials Management (In-Band, SNMP)

OS Management (TFTP)



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.




The following are the commands, or processes that are used to “pull” a configuration from your device (enable/privileged mode required).

Via Terminal:

show running-config

show startup-config

Via file transfer (untested):

copy running-config tftp:

copy startup-config tftp:



Via Terminal (Telnet/SSH):

Configuration commands are issued interactively.

Via 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

show interface brief

traceroute



File Management

copy [tftp:]

delete

dir

Password Management

[no] snmp-server

[no] username

password telnet

Multi-Config Files



running √

startup √

Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No



MRV DEVICES

MRV LX Terminal Server

Device Type MRV LX Terminal Server

Specific Model(s) All LX Series Models

Documentation/Information http://service.mrv.com/support/index.cfm



Configuration Files Text (running config only)

Configuration Content Quick Commands, Configlet Termlet, Command, Config

Configuration Protocols SSH/TFTP, Telnet/TFTP




Configuration Capture SSH/TFTP, Telnet/TFTP

Configuration Deploy SSH/TFTP, Telnet/TFTP



Hardware Information Power Supplies, Character Ports, Ethernet Ports, Interfaces

Features Available








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






save configuration network [filename] [serverIP]




load configuration from network [filename] [serverIP]

Multi-Config Files



running √

Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory No


OSPF Settings No


Routes No



VLANs No



NETCACHE DEVICES

NetCache

Device Type NetCache

Specific Model(s) C1200

Documentation/Information www.netapp.com





Configuration Protocols SSH Only, Telnet Only

User Interface CLI

Discovery/Identify Methods SNMP Only


Configuration Capture Text Capture via show config

Configuration Deploy Text CLI via Telnet or SSH


Router Quick Commands System Config

Hardware Information Hardware Inventory, Interfaces, Serial Number, Model, OS Version, Hardware Information

Features Available







Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



NETOPIA DEVICES

Netopia R7000 Series

Device Type Netopia Router

Specific Model(s) R7000 series

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


Configuration Files Binary

Configuration Content Termlet Merge

Configuration Protocols Telnet/TFTP, Telnet Only

User Interface Menu Driven



Configuration Capture TFTP

Configuration Deploy TFTP

Cut-Through Access Terminal, ANSI

Router Quick Commands Ping, TraceRoute


Features Available







sysDescr

Contains Netopia and one of the following: R7200, R7220, or R7231



Utilities and Diagnostics

Trivial File Transfer protocol (TFTP)

SEND CONFIG TO SERVER





Utilities and Diagnostics

Trivial File Transfer protocol (TFTP)

GET CONFIG FROM SERVER

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



NETSCREEN DEVICES

Netscreen Firewall

Device Type NetScreen

Specific Model(s) HARDWARESECURITYCLIENT ISG2000, ISG1000 NETSCREENGENERIC, NS5, NS10, NS100, NS1000, NS500, NS50, NS25, NS204, NS208, NS5XT, NS5XP, NS5000, NS5GT, NS5GT-ADSL-ANNEXA, NS5GT-ADSL-ANNEXB, NS5GT-WLAN, NS5GT-ADSL-ANNEXA-WLAN, NS5GT-ADSL-ANNEXA-WLAN SSG5, SSG5-ISDN, SSG5-V92, SSG5-WLAN, SSG5-ISDN-WLAN, SSG5-V92-WLAN, SSG20, SSG20-WLAN, SSG-320M, SSG-520, SSG-550, SSG-220, SSG-250

Documentation/Information www.juniper.net





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

User Interface Command Line, Web-Based

Discovery/Identify Methods SNMP, Terminal, SSH









Features Available









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

Multi-Config Files



running √

startup √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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.



NOKIA DEVICES

Nokia IP

Device Type Nokia IPSO Firewall

Specific Model(s) IP260, IP265, IP350, IP355, IP380, IP385, IP390, IP45, IP560, IP1220, IP1260, IP2255,

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



Other Unique Information Unix like operating system


Configuration Content Command, Config, Privilege Mode Termlet, Termlet Merge, Operating System, Device Setting





Configuration Capture Terminal, SSH, FTP, SCP

Configuration Deploy Terminal, SSH, FTP, SCP

Cut-Through Access Terminal, SSH, In-Band

Firewall Quick Commands Test Credentials, Setup Diagnostic, View Diagnostic Setup, Ping, Traceroute, View Interfaces, View ARP, View Routes, Setup NAT, View NAT Setup


Features Available











Custom or Vendor Specific OIDs

.1.3.6.1.4.1.94.1.21.1.1.1.0

• 7H055101054

• Discovery is done via 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






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


Device Commands



clish –c ‘add snmp community …’

clish –c `copy …’

reboot

ifconfig

ping

traceroute

arp

netstat

File Management

mkdir

cp

ls

Password Management

dbpasswd



Multi-Config Files



Pull Only


$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

$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

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



NORTEL DEVICES

Nortel Alteon


Specific Model(s) 184, 180e, 2208, 2216, 2216 E, 2424, 2424 SSL, 3408 AD3, AD4, ASF-5009-x305, iSD SSL

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


Configuration Files Startup, Running Text


Configuration Protocols SSH/TFTP, Telnet/FTP, SSH, Telnet, SNMP/TFTP



Configuration Capture SSH/TFTP, Telnet/FTP, SSH, Telnet, SNMP/TFTP

Configuration Deploy SSH/TFTP, Telnet/FTP, SSH, Telnet, SNMP/TFTP


Router Quick Commands Ping, Traceroute, View Interfaces, View ARP, View Routes

Hardware Information Memory, Interfaces, Serial Number, OS Version

Features Available







Discovery via SNMP

SysDecr contains one of the following:

Alteon

Nortel Application Switch





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.

Multi-Config Files



running √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Known Issues


Nortel Alteon

No restrictions are enforced on password length.

For terminal pushes, the script configuration line is skipped.

Configuration management via 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 via terminal.

tnet ena

/cfg/sys/sshd/ena

/cfg/sys/sshd/on



Nortel Alteon 2400

Device Type Load Balancer, Firewall




Configuration Files Startup, Running Text

Configuration Content Termlet Merge, User Mode Termlet

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

User Interface CLI



Configuration Deploy Telnet, SSH


Router Quick Commands Test Credentials, Diagnostics, NAT Configuration, View Interfaces, View ARP, View Routes


Features Available

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






Discovery via 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





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 via 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 via Terminal.

tnet ena

/cfg/sys/sshd/ena

/cfg/sys/sshd/on

Restrictions on password length are not enforced.



Nortel Router

Device Type Router

Specific Model(s) AN, ARN, BCN, BLN, BLN, ASN, Passport 2430 Router 5580, Router 5430



Configuration Files Single Text, Binary

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

Configuration Protocols Telnet/FTP, Telnet Only

User Interface Command Line, Menu Driven



Operating System 15.4.0.1, 15.4.0.2, 15.4.2.6

Configuration Capture Terminal, FTP

Configuration Deploy Terminal, FTP


OS Management OS Upgrade

Router Quick Commands Test Credentials, Ping, View ARP, View Memory, View Routes, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup


Features Available










Model OID

.1.3.6.1.4.1.18.3.1.1.1.0

OS Version

retrieved from sysDescr



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

Multi-Config Files



binary config √

text config √

config report √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

Known Issues


Nortel ARN - Pushing Command via Configlet

Issue: Pushing Command via 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 via Telnet.

An ARN config pulled via Telnet, can be edited, and will not have binary data displayed at the bottom of the configuration.

A configuration pulled via 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.



Nortel Baystack

Device Type Nortel Baystack Switch

Specific Model(s) 450, 410 350, 350-12T, 380-24F





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


User Interface Menu Driven








Router Quick Commands Test Credentials, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup


Features Available








OS version

Retrieved from sysDescr

Serial number OID

.1.3.6.1.4.1.45.1.6.3.1.6.0



Multi-Config Files



binary config √

text config √

snmp config √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes



Nortel BoSS Switch

Device Type Nortel Baystack BPS 2000 Switch

Specific Model(s) BPS 2000 and Baystack 470





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


User Interface Command Line, Menu Driven



Operating System 3.1.4.11, 3.6.03, 3.5.0.58







Features Available








OS Version

From sysDescr



Copy config tftp address <server ip> filename <pull file name>





Copy tftp config address <server ip> filename <pull file name>

Multi-Config Files



binary config √

text config √

snmp config √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs Yes



Nortel Contivity

Device Type Nortel VPN

Specific Model(s) 600 1000, 1010, 1050, 1100, 15XX 1600, 1700, 1740 2000, 2500, 2600, 2700 4500, 4600




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

Configuration Protocols SSH/FTP, Telnet/FTP, SSH Only, Telnet Only




Operating System 4_70.119

Configuration Capture Terminal, FTP

Configuration Deploy Terminal, FTP




Features Available







sysObjectID is used to determine the various models



Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Nortel Multi-Service Switch


Specific Model(s) 7480 15000 20000 Nortel Carrier Passport



Configuration Change Notification (Events) SNMP Traps, Syslog

Configuration Files Multiple Text, Binary


Configuration Protocols Telnet/FTP

User Interface CLI



Configuration Capture Telnet/FTP

Configuration Deploy Telnet/FTP



Router Quick Commands Test Credentials, Diagnostics, Ping, OS Update, Acknowledge Prov, Confirm Prov, Save Prov, Commit Prov, NAT Configuration

Hardware Information SNMP, Terminal: Hardware Inventory, Memory, Interfaces, Serial Number, Hardware Information

Features Available










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



running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Known Issues


Nortel Multi-Service Switch

Chassis serial number via 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 via 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 via terminal depends on the base_ naming convention of the software distribution in the output of the display –noTabular Sw avl command



Nortel Passport

Device Type Nortel Router, Nortel Switch

Specific Model(s) 1648T





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

Configuration Protocols Telnet/TFTP








Features Available







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>



download configuration <server IP> <filename>



Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Nortel Passport 8600

Device Type Routing Switch

Specific Model(s) 1050, 1200, 1250 8106, 8110, 8310, 8603, 8606, 8610





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










Router Quick Commands Test Credentials, Ping, Traceroute, View Sys Info, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup


Features Available








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



running √

startup √

boot.cfg √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



Known Issues


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 via 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.



PACKETEER DEVICES

Packeteer PacketShaper

Device Type Packeteer PacketShaper LoadBalancer

Specific Model(s) Packetshaper 1000 Packetshaper 1400 Packetshaper 1500 Packetshaper 1550 Packetshaper 1700 Packetshaper 2000 Packetshaper 2500 Packetshaper 2550 Packetshaper 3500 Packetshaper 4000 Packetshaper 4500 Packetshaper 6500 Packetshaper 7500 Packetshaper 8500 Packetshaper 9500 Packetshaper 10000

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



Configuration Files Multiple Text and Binary


Configuration Protocols SSH/FTP, Telnet/FTP




Configuration Capture FTP

Configuration Deploy FTP




Features Available










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, via 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.

Multi-Config Files



running √

startup √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



PARADYNE DEVICES

Paradyne 9100

Device Type Router


Documentation/Information http://search.zhone.com/query.html



User Interface Menu





Router Quick Commands Test Credentials, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NatIP Setup

Features Available


Credential Management (In-band/SNMP)




sysDescription contains Paradyne iMarc (case-insensitive)

serial number and system name are valid

Device Commands


Password Management

Main > Load Config > Current > Configuration Edit > Management/Communication

Main > Control > Administer Logins

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.



RADWARE DEVICES

Radware WSD Load Balancer

Device Type Radware WSD Load Balancer

Specific Model(s) All Web Server Director models

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



Configuration Files Text – running config only









Router Quick Commands Ping, Traceroute, Interfaces, Routes, ARP, CPU Procs, Resync, Reboot


Features Available










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






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]

For SSH and Telnet:

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 √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



RIVERBED DEVICES

Riverbed Steelhead


Specific Model(s) Steelhead 100

Documentation/Information Customer Supplied


Configuration Files running/startup

Configuration Content Ascii

Configuration Protocols SSH

User Interface Command-Line



Configuration Capture SSH

Configuration Deploy SSH


Supported Quick Commands View interfaces, View routes, Ping, Traceroute, View ARP

Hardware Information Interfaces, Memory, Serial Number, OS Version, Inventory

Features Available




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



Via terminal:

show configuration running

show configuration





Via 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

Password Management

username

snmp-server community

Multi-Config Files



running √

startup √



Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes No



VLANs No

Known Issues


Riverbed Steelhead

There is no support for sysServices (standard MIB scalar). An edit to package/mibs.inc (changing <snmpcached> to <snmp>) is required.

The sysObjectID represents a vendor, not the model identification.

Configuration management via file transfer is not currently supported, since the results are a binary database.

There is no known support for configuration changes via 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.



RIVERSTONE DEVICES

Riverstone Router

Device Type Router

Specific Model(s) RS 500, 1000, 2000, 2100, 3000, 8000, 8600, 32000, 38000 RSLA 1100, 1200, 1500

Documentation/Information See vendor


Configuration Files running

Configuration Content Text

Configuration Protocols SSH

User Interface CLI


Password Management Accounts and SNMP

Configuration Capture SSH

Configuration Deploy SSH


Router Quick Commands Ping, Traceroute, View Routes, NAT

Hardware Information Basic hardware (memory, serial number information)

Features Available







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





config terminal

configuration write

Config Files

Following are the files used when storing and revisioning configuration files.


running √

startup √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



SIEMENS DEVICES

Siemens 5940

Device Type Router

Specific Model(s) 5851, 5871, 5940

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


Configuration Change Notification (Events) -


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

Configuration Protocols Telnet/TFTP, SSH/TFTP, Telnet only, SSH only


Discovery/Identify Methods Terminal, SNMP







Hardware Information For Terminal: Hardware Inventory, Memory, Interfaces, Serial Number, Hardware Information

Features Available








Multi-Config Files


Multi-Config Files Push/Pull Pull Only .* √

.*\.(TXT|MFG|HTM) √

config √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



STARENT DEVICES

Starent PDSN

Device Type Starent Packet Data Serving Node

Specific Model(s) ST16

Documentation/Information https://support.starentnetworks.com/



Configuration Files Text (running config only)









Router Quick Commands Ping, View Routes, Traceroute, View_interfaces

Hardware Information Slot/Card Inventory, Interfaces

Features Available








SNMP SysDescr

Model from SysObjectIDs: 1.3.6.1.4.1.8164.*

OS, Filesystem and Memory from CLI








save configuration tftp://[serverIP]/[filename] -noconfirm verbose

For SSH and Telnet:

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.

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



SYMBOL DEVICES

Symbol WS-2000

Device Type Wireless Switch WS-2000

Specific Model(s) Symbol WS-2000

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


Configuration Change Notification (Events) Traps


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


User Interface Command Line, Menu Driver, Web Based



Operating System 1.5.0, 1.5.1, 2.0.0, 2.0.1, 2.0.2

Configuration Capture Terminal, SNMP, Non-SNMP

Configuration Deploy Terminal, SNMP

Cut-Through Access SNMP, Telnet, SSH, Non-SNMP

OS Management Telnet/TFTP, Telnet/FTP

Switch Quick Commands View NAT, Test Credentials, Device Uptime, Interface Summary, Setup Diagnostic, View Diagnostic Setup, Setup NAT, View NAT Setup

Hardware Information For SNMP: Hardware Inventory, Memory, Interfaces, Serial Number, Model, OS Version For Non-SNMP: Interfaces, Serial Number, Model, OS Version

Features Available











System Description

Symbol WS2000 HW=E SW=0.0-035R MIB=08c12

System Object ID

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;

File Name

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



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 via 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



OS 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 OS upgrade/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.

Multi-Config Files



running √



Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No



TASMAN DEVICES

Tasman Router

Device Type Tasman Router

Specific Model(s) 1004E, 1001, 1002, 1002E, 1200, 1200C, 1200E, 1200EC, 1250, 1400, 1400E, 1450 4100, 4102 6300

Documentation/Information www.tasman.com






Discovery/Identify Methods Terminal, SNMP


Configuration Capture Terminal

Configuration Deploy Terminal

Cut-Through Access Telnet/TFTP, Telnet Only, SSH Only

OS Management Telnet/TFTP, SSH/TFTP

Router Quick Commands Resync, diffRunStart


Features Available









System Object ID

1.3.6.1.4.1.3174.1

SysDecr

Contains Tasman



Multi-Config Files



running √

startup √

Device Data



ARP Table No


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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.



TELCO DEVICES

Telco Switch

Device Type Switch

Specific Model(s) T5CL3-24G 256M, T-Marc-250, T-Marc-254

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








Operating System T5CL3-24G 256M: BinOS 6.5.5, T-Marc-250: BinOS 6.6.3.4, T-Marc-254: BinOS 6.6.3.4




Router Quick Commands View Interfaces, View Routes, Ping, Traceroute

Hardware Information Serial number, OS version, Interfaces

Features Available




Credential Management (In-Band)



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

http://www.telco.com/





Telnet, SSH:

show running-config

show startup-config

Telnet/TFTP, SSH/TFTP:

copy running-config upload-to serverIpAddress remoteFilename

copy startup-config upload-to serverIpAddress remoteFilename



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 √



Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

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.



Telco T-Metro

Device Type Switch

Specific Model(s) T-Metro 256M

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








Operating System 7.0.R2




Router Quick Commands Serial number, OS version, Interfaces

Features Available







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

http://www.telco.com/





Telnet, SSH:

show running-config

show startup-config


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 √



Device Data



ARP Table No


CAM Table No


Device Identity Yes

Interfaces Yes

Keys No

Memory No



Static Routes No



VLANs No

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.



VANGUARD DEVICES

Vanguard Router

Device Type Router


Documentation/Information www.vanguardnetworks.com/ support/documentation/ user_manuals/








Operating System V7.1.R00A_@Seven_3400




Router Quick Commands Memory, Interfaces, Serial number, OS version, Inventory

Features Available


Configuration Management (Revision Config, Basic Diagramming)





sysObjectID

Contains 1.3.6.1.4.1.449.2.1.3410



tftp getscript remoteFilename serverIpAddress





tftp setscript remoteFilename serverIpAddress

Multi-Config Files



running √

Device Data



ARP Table Yes


CAM Table No


Identity Yes

Interfaces Yes

Keys No

Memory Yes


OSPF Settings No


Routes Yes



VLANs No

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.

The username must be defined as ATDS, and is case-insensitive. The username cannot be changed, as it is part of the connection procedure.



WHERE TO GET HELP

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 EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Sales and customer service contacts — For the list of EMC sales locations, please access the EMC home page at:

http://EMC.com/contact

http://powerlink.emc.com/

http://emc.com/contact



GLOSSARY

Following are acronyms found within this document.

DASL

Device Access Scripting Language

DSR

Device Support Release

GUI

Graphical User Interface

IP

Internet Protocol. This is a network layer protocol in the Internet protocol suite and is encapsulated in a data link layer protocol (e.g., Ethernet).

OS

Operating System

RegEx

Regular Expression

RME

Resource Manager Essentials (CISCO)

UNIX

A multi-user, multitasking computer operating system

VPN

Virtual Private Network

XML

eXtensible Markup Language: a simplified version of SGML that can be used, esp. on the World Wide Web, to create a tagging scheme that allows elements of a document to be marked according to their content rather than their format.



INDEX

3 3com Devices, 20 3Com Netbuilder II Router, 20 3Com Switch 5500, 22

A About this Manual, 17 Adtran Devices, 25 Adtran Netvanta, 25 Adtran Netvanta Switch, 28 Airespace Devices, 30 Airespace Switch, 30 Alcatel Devices, 32 Alcatel Omnicore, 32 Alcatel Omnistack, 34 Alcatel Omniswitch, 37 Alcatel Service Router and Ethernet Service

Switch, 41 Alvarion Breeze AP, 44 Alvarion Devices, 44 Aruba Devices, 46 Aruba Wireless Switch, 46

B BlueCoat Devices, 48 BlueCoat SG, 48 Brocade 7500, 51 Brocade Devices, 51 Brocade McData, 53

C Checkpoint Devices, 55 Checkpoint Firewall-1, 55 Ciena Devices, 59 Ciena Router, 59 Cisco Aironet AP Package, 71 Cisco Aironet AP VXWorks, 62 Cisco Aironet Bridge Package, 74 Cisco Application Control Engine, 77 Cisco BPX, 80 Cisco CatOS Switch Package, 83 Cisco Content Appliance, 89 Cisco Content Services Switch, 92 Cisco Devices, 62 Cisco IOS Switch Package, 101 Cisco IOS XR, 108 Cisco MDS, 121 Cisco MGX, 117 Cisco PIX Firewall, 64 Cisco Router, 94

Cisco VPN 3000, 69 Cisco Wireless LAN Controller, 124 Citrix Devices, 127 Citrix Netscaler LoadBalancer, 127 Compatibility, 17 copyright, 2

D Device Driver, 18 Device Drivers, 18 D-Link Devices, 129 D-Link xStack, 129

E Edgewater Devices, 131 Edgewater EdgeMarc Router, 131 Enabling Inactive Device Classes, 19 Enterasys Devices, 133 Enterasys Smartswitch Router, 133 Ericsson Devices, 136 Ericsson MSED, 136 Extreme, 138 Extreme Devices, 138 ExtremeWare XOS, 141

F F5 Devices, 143 F5 Load Balancer Rev 3, 143 F5 Load Balancer Rev 4, 147 F5 Load Balancer Rev 9, 150 Force10 Devices, 155 Force10 E-Series Router, 158 Foundry Devices, 161 Foundry EdgeIron, 161 Foundry Package, 163

G glossary, 261

H HP Devices, 166 HP ProCurve Switch, 166

I Introduction, 17

J Juniper Devices, 171



Juniper ERX (E Series), 171 Juniper Router Package, 174 Juniper Switch (EX Series), 177

L Laurel Devices, 180 Laurel ST Router, 180 Lucent Access Point, 183 Lucent Devices, 183

M Marconi Devices, 185 McAfee Devices, 188 McAfee IntruShield, 188 Milan Devices, 190 Motorola BSR Router, 192 Motorola Devices, 192 MRV Devices, 195 MRV LX Terminal Server, 195

N NetCache, 197 NetCache Devices, 197 Netopia Devices, 199 Netopia R7000 Series, 199 Netscreen Devices, 201 Netscreen Firewall, 201 Nokia Devices, 204 Nokia IP, 204 Nortel Alteon, 208 Nortel Alteon 2400, 211 Nortel Baystack, 216 Nortel BoSS Switch, 218 Nortel Contivity, 220 Nortel Devices, 208 Nortel MSS, 222 Nortel Multi-Service Switch, 222 Nortel Passport, 225 Nortel Passport 1648T, 225 Nortel Passport 8600, 227 Nortel Router, 213

P Packeteer Devices, 230 Packeteer PacketShaper, 230 Paradyne 9100, 233 Paradyne Devices, 233

R Radware Devices, 234 Radware WSD Load Balancer, 234 Related Publications, 16 Riverbed Devices, 237 Riverbed Steelhead, 237 Riverstone Devices, 240 Riverstone Router, 240

S Siemens 5940, 242 Siemens Devices, 242 SM801P Managed Switch, 190 Starent Devices, 244 Starent PDSN, 244 Support, 260 SYmbol Devices, 246 Symbol WS-2000, 246

T Tasman Devices, 250 Tasman Router, 250 Telco Devices, 252 Telco Switch, 252 Telco T-Metro, 255

V Vanguard Devices, 258 Vanguard Router, 258 Viewing Installed Device Driver Packages,

19 Voyence SUpport, 16

W Who Should Read this Document, 16

emc voyencecontrol device services support (dsr)emc ® voyencecontrol device services support (dsr)...

Documents