Can you fully describe your procedure - the steps you configure in SNMP exactly? 

To use this table you must use the "rowstatus" mechanism to "create" a row in this table.  You can't just set the parameters in the row to any index until you create it.  You must either use the "create&wait" mechanism which allows you to create the row then setup the parameters then activate the row or you must use "create&go" which requires you to setup everything in a single varbind.  This mechanism for "rowstatus" is a common standard mechanism used in SNMP - please review information available online (try google search) if you are not familiar with this mechanism.

Cuong.

At the moment, I'm just trying to make sure that I can find and manipulate the correct parameters, so I'm using the MIB browser from NuDesign.  I've sucesfully created entries in the dot1qVlanStaticTable using the mib browser.  Once I put in the index, and OK it, the row is created for the VLAN, and I get a pop-up with the values that need to be filled in for the table.  When I try it with the rlCopyTable, no pou-up appears.(I've tried an index of 0 and 1)   It's like there is a mismatch somewhere.  Is  1.3.6.1.4.1.674.10895.5000.2.89.87.2 the correct OID for the table?

That's not the correct OID for the 3448 MIB.  Please reload the correct MIB for this switch and try again.  The base for this MIB should be .1.3.6.1.4.1.674.3000.....

Cuong.

Here's the part from dell_Vendor.mib that looks like a problem

 

powerConnect3000MIB         OBJECT IDENTIFIER ::= { dellLan 3000 }
dell-VendorMIBObjects       OBJECT IDENTIFIER ::= { powerConnect3000MIB 1 }
dellVendorNotifications     OBJECT IDENTIFIER ::= { powerConnect3000MIB 2 }
dellStandard OBJECT IDENTIFIER ::= { dellLan 5000 }
-- Dell common and device independent MIB objects.
dellCommon OBJECT IDENTIFIER ::= { dellStandard 1 }
-- Dell extension MIB objects for specific technology or device.
dellExtension OBJECT IDENTIFIER ::= { dellStandard 2 }
rndMib        OBJECT IDENTIFIER ::= { dellExtension 89 }

 

and from apollo.txt

 

-- Some MIB compilers require that the following 7 lines which define the path
-- to RND MIB are commented out:

-- mib            OBJECT IDENTIFIER ::= { mgmt 1  }
-- directory      OBJECT IDENTIFIER ::= { internet 1  }
-- experimental   OBJECT IDENTIFIER ::= { internet 3  }
-- private        OBJECT IDENTIFIER ::= { internet 4  }
-- enterprises    OBJECT IDENTIFIER ::= { private 1  }
 rnd            OBJECT IDENTIFIER ::= { dellExtension 89  }

 

with RLcopy mapping to rnd

Oops...I got the wrong OID.  It should be .1.3.6.1.4.1.674.10895.3000...  I also got my MIB from the web and it is correct for me.  Make sure you downloaded the one for 34xx switches.

cuong.

I just looked at the MIB again and you are correct about the OID.  My mistake.  The top of the rlCopyTable is .1.3.6.1.4.1.674.10895.5000.2.89.87.2.

I also just re-run my test script for downloading the running-config file from the switch to a remote TFTP server and also to copy the active image to a remote server using SNMP and it works for me.

This is basically what my script does - it use a single SNMP set request using the "rowstatus" create&go method.  The script specifies all the following parameters in the request (there are a few others which I didn't use in this script - see the MIB for more info on the other variables):

• set rlCopySourceLocation = set this to the source type (e.g. I set source to local for my testing - see MIB for more info).
• set rlCopySourceUnitNumber = set this to the unit # of the switch in the stack or set to 1 if you are not running stacking.
• set rlCopySourceFileType = set this to the type of file to copy (e.g. running-config or image - see MIB for more info).
• set rlCopyDestinationLocation = set this to the destination type (e.g. I set destination to tftp).
• set rlCopyDestinationIpAddress = set this to the IP address of the TFTP server if you are doing TFTP copy.
• set rlCopyDestinationFileName = set this to the name of the destination file.
• set rlCopyHistoryIndex = set this if you want the history of the copy to be retained (you need a unique history index so use the next free index variable - see MIB).
• set rlCopyRowStatus = set this to "create&go" (value = 4) to create the row in the table and start the copy.

Note that the copy succeed really fast when copying a configuration file and when it completes the row is removed so if you want history save it in the history table.  If you copy an image then the row may stay around awhile so you can poll status while the copy executes.

Anyway, my script works so this table is fine.  The OID you had was correct - my mistake - I was hand creating the OID (I don't use browser - hand scripting using shell scripts :-)) manually and made a mistake in the encoding.

Cuong.

Thanks.  My problem was that I was trying to create the row, then populate it.  I guess that for that table you have to create and populate all at once.(create&go)

I take it I need to compile the mibs in order to work with them via snmpset?

Cuong,


Could you post an example on how to do this via snmpset for either the 3348 or 3448 series switches, I've had no luck getting either to work?


Thanks

Anybody?