Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Config files with Gigamon switches

I have a couple of Gigamon switches I am monitoring with SW. I noticed that I couldn't back up the config files. Support said it was an issue with the SSH cypher not support and it would be fixed in a future release. Has anybody found a workaround? Thanks.

Find more posts tagged with

Accepted answers

saw10

Settings
All Settings
Under Node and Group Management
Manage Device Templates
Add New
Using xml Editor
Fill in the Template Name (Something Like "Gigamon"
Fill in system OID '1.3.6.1.4.1.26866'
Copy the Device Template I posted here

<Configuration-Management Device="Gigamon" SystemOID="1.3.6.1.4.1.26866" AutoDetectType="BySystemOid">
<Commands>
<Command Name="RESET" Value="no cli session paging enable" />
<Command Name="Reboot" Value="reload${CRLF}y${CRLF}y" />
<Command Name="EnterConfigMode" Value="configure terminal" />
<Command Name="ExitConfigMode" Value="end" />
<Command Name="Startup" Value="configuration" />
<Command Name="Running" Value="running-config" />
<Command Name="DownloadConfig" Value="show ${ConfigType}" />
<Command Name="UploadConfig" Value="${EnterConfigMode}${CRLF}${ConfigText}${CRLF}${ExitConfigMode}" />
<Command Name="Version" Value="show version" />
</Commands>
</Configuration-Management>

Then assign the Template and Connection profile to the required device
You should then test,

All comments

saw10

Not sure about Gigamon switch- we use Gigamon as our Packet Broker environment - TAXX and HC2.
If these are the type of devices that you are talking about, then yes we backup these devices.

1) Connection Profile
a) Command line access (enable prompt)
2) A device Template for the Gigamon Environment
This is the one that we use - I think I got it from the NCM Content Exchange.
<Configuration-Management Device="Gigamon" SystemOID="1.3.6.1.4.1.26866" AutoDetectType="BySystemOid">
<Commands>
<Command Name="RESET" Value="no cli session paging enable" />
<Command Name="Reboot" Value="reload${CRLF}y${CRLF}y" />
<Command Name="EnterConfigMode" Value="configure terminal" />
<Command Name="ExitConfigMode" Value="end" />
<Command Name="Startup" Value="configuration" />
<Command Name="Running" Value="running-config" />
<Command Name="DownloadConfig" Value="show ${ConfigType}" />
<Command Name="UploadConfig" Value="${EnterConfigMode}${CRLF}${ConfigText}${CRLF}${ExitConfigMode}" />
<Command Name="Version" Value="show version" />
</Commands>
</Configuration-Management>

Hope this helps -

emunizaga

Thanks for your reply. I have a HC2 and a TA-200 in our environment. How do i create a device template for the items above? Thanks.

saw10

Then assign the Template and Connection profile to the required device
You should then test,

emunizaga

Done and NCM is now able to backup the Gigamon switches. Thanks for your help.