[c-nsp] IOS - how do I use vlanTrunkPortSetSerialNo when changing allowed vlans on a trunk via SNMP?

[BRIDGSTOCK, Jonathon]

I've worked it out - for the record:

snmpget -v2c -c <snmpread string> <ip address>  1.3.6.1.4.1.9.9.46.1.6.1.1.4.<ifindex> 1.3.6.1.4.1.9.9.46.1.6.2.0
Will get me the values of the first 1000ish vlans along with the serial number.

Then when I commit the change:

snmpset -v2c -c <snmpwritestring> <ip address> 1.3.6.1.4.1.9.9.46.1.6.1.1.4.<ifindex> x <octet stream> 1.3.6.1.4.1.9.9.46.1.6.2.0 i <value returned from get>

Need to also write the other snmp oids for the 1000-4000ish vlan ranges at the same time.

I was testing using a 3750, and I think the 0 in 1.3.6.1.4.1.9.9.46.1.6.2.0 relates to the stack member – I didn’t have that in before so it was erroring.

Cheers,

Jon

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of BRIDGSTOCK, Jonathon
Sent: Wednesday, 24 July 2013 8:38 AM
To: 'cisco-nsp at puck.nether.net'
Subject: [c-nsp] IOS - how do I use vlanTrunkPortSetSerialNo when changing allowed vlans on a trunk via SNMP?

Hi,

I’ve been asked to automate a bunch of stuff, including the ability to trunk vlans through a network; I’ve been told I have to use SNMP for the IOS devices.

I’ve got working scripts which will pull the allowed vlans via the OID vlanTrunkPortVlansEnabled and do all the unpacking, bit changing and re-packing, but I have no idea when it comes to using the vlanTrunkPortSetSerialNo “spinner lock”.

Does anyone have any examples of how this would work?  I’ve done some searching, but I cannot find an example or good description of the steps required to use the TestandIncr syntax.

Cheers,

Jon.

________________________________

This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp".
Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au.
The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system.
　
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

________________________________

This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp".
Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au.
The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system.
　

________________________________

This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp".
Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au.
The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system.