Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Uploading running configs to TFTP

Hello.

Can anybody tell me what string I should write into the following variable to upload running configuration from the router to tftp server.

Name: writeNet

Type: OBJECT-TYPE

OID: 1.3.6.1.4.1.9.2.1.55

Numerical syntax: Octets

Base syntax: OCTET STRING

Composed syntax: DisplayString

Status: mandatory

Max access: write-only

Description: Write configuration to host using TFTP.

Thanks in advance.

2 ACCEPTED SOLUTIONS

Accepted Solutions
New Member

Re: Uploading running configs to TFTP

Hi, the octet string is the name of the network file.

For more Info:

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008009463e.shtml#task

New syntax is:

***************************************************************************************

copy the running-config to a TFTP-server

***************************************************************************************

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 6 # delete temp. entry

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 5 # create temp. entry

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.2. integer 1 # use tftp

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.3. integer 4 # source is running-config

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.4. integer 1 # destination is network file

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.5. ipAddress # TFTP-server IP

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.6. Displaystring test # name of the networkfie

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 1 # do it

snmpget -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.10. # read status of the action

***************************************************************************************

"ccCopyEntryRowStatus" "1.3.6.1.4.1.9.9.96.1.1.1.1.14"

ccCopyEntryRowStatus OBJECT-TYPE

SYNTAX RowStatus

-- Rsyntax INTEGER {

-- active(1),

-- notInService(2),

-- notReady(3),

-- createAndGo(4),

-- createAndWait(5),

-- destroy(6)

"ccCopyProtocol" "1.3.6.1.4.1.9.9.96.1.1.1.1.2"

ConfigCopyProtocol ::= INTEGER {

tftp(1),

ftp(2),

rcp(3) }

"ccCopySourceFileType" "1.3.6.1.4.1.9.9.96.1.1.1.1.3"

ccCopySourceFileType OBJECT-TYPE

SYNTAX ConfigFileType

-- Rsyntax INTEGER {

-- networkFile(1),

-- iosFile(2),

-- startupConfig(3),

-- runningConfig(4),

-- terminal(5)

"ccCopyDestFileType" "1.3.6.1.4.1.9.9.96.1.1.1.1.4"

ccCopyDestFileType OBJECT-TYPE

SYNTAX ConfigFileType

-- Rsyntax INTEGER {

-- networkFile(1),

-- iosFile(2),

-- startupConfig(3),

-- runningConfig(4),

-- terminal(5)

"ccCopyServerAddress" "1.3.6.1.4.1.9.9.96.1.1.1.1.5"

ccCopyServerAddress OBJECT-TYPE

SYNTAX IpAddress

"ccCopyFileName" "1.3.6.1.4.1.9.9.96.1.1.1.1.6"

ccCopyFileName OBJECT-TYPE

SYNTAX DisplayString

"ccCopyState" "1.3.6.1.4.1.9.9.96.1.1.1.1.10"

ConfigCopyState ::= INTEGER {

waiting(1),

running(2),

successful(3),

failed(4)

"ccCopyFailCause" "1.3.6.1.4.1.9.9.96.1.1.1.1.13"

ConfigCopyFailCause ::= INTEGER {

unknown(1),

badFileName(2),

timeout(3),

noMem(4),

noConfig(5)

regards Ulrich Marzoli

Blue

Re: Uploading running configs to TFTP

3 REPLIES
New Member

Re: Uploading running configs to TFTP

Hi, the octet string is the name of the network file.

For more Info:

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008009463e.shtml#task

New syntax is:

***************************************************************************************

copy the running-config to a TFTP-server

***************************************************************************************

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 6 # delete temp. entry

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 5 # create temp. entry

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.2. integer 1 # use tftp

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.3. integer 4 # source is running-config

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.4. integer 1 # destination is network file

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.5. ipAddress # TFTP-server IP

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.6. Displaystring test # name of the networkfie

snmpset -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.14. integer 1 # do it

snmpget -c private 1.3.6.1.4.1.9.9.96.1.1.1.1.10. # read status of the action

***************************************************************************************

"ccCopyEntryRowStatus" "1.3.6.1.4.1.9.9.96.1.1.1.1.14"

ccCopyEntryRowStatus OBJECT-TYPE

SYNTAX RowStatus

-- Rsyntax INTEGER {

-- active(1),

-- notInService(2),

-- notReady(3),

-- createAndGo(4),

-- createAndWait(5),

-- destroy(6)

"ccCopyProtocol" "1.3.6.1.4.1.9.9.96.1.1.1.1.2"

ConfigCopyProtocol ::= INTEGER {

tftp(1),

ftp(2),

rcp(3) }

"ccCopySourceFileType" "1.3.6.1.4.1.9.9.96.1.1.1.1.3"

ccCopySourceFileType OBJECT-TYPE

SYNTAX ConfigFileType

-- Rsyntax INTEGER {

-- networkFile(1),

-- iosFile(2),

-- startupConfig(3),

-- runningConfig(4),

-- terminal(5)

"ccCopyDestFileType" "1.3.6.1.4.1.9.9.96.1.1.1.1.4"

ccCopyDestFileType OBJECT-TYPE

SYNTAX ConfigFileType

-- Rsyntax INTEGER {

-- networkFile(1),

-- iosFile(2),

-- startupConfig(3),

-- runningConfig(4),

-- terminal(5)

"ccCopyServerAddress" "1.3.6.1.4.1.9.9.96.1.1.1.1.5"

ccCopyServerAddress OBJECT-TYPE

SYNTAX IpAddress

"ccCopyFileName" "1.3.6.1.4.1.9.9.96.1.1.1.1.6"

ccCopyFileName OBJECT-TYPE

SYNTAX DisplayString

"ccCopyState" "1.3.6.1.4.1.9.9.96.1.1.1.1.10"

ConfigCopyState ::= INTEGER {

waiting(1),

running(2),

successful(3),

failed(4)

"ccCopyFailCause" "1.3.6.1.4.1.9.9.96.1.1.1.1.13"

ConfigCopyFailCause ::= INTEGER {

unknown(1),

badFileName(2),

timeout(3),

noMem(4),

noConfig(5)

regards Ulrich Marzoli

Blue

Re: Uploading running configs to TFTP

New Member

Re: Uploading running configs to TFTP

Thank you for help. I used obsolete MIB, that, proposed by you is much more convenient.

145
Views
0
Helpful
3
Replies
CreatePlease login to create content