Mailing List Archive

CER - Creating VLANs via SNMP - cant set name?
Hi everyone,

Im writing some scripts that create VLANs and assigns ports to them via
SNMP, and so far everything is working pretty good, except that when I
create the VLAN, it doesnt seem to save the name that I supply along with
it. For example, when I execute the following command:

snmpset -v2c -c.... x.x.x.x .1.3.6.1.2.1.17.7.1.4.3.1.1.123 s TEST
.1.3.6.1.2.1.17.7.1.4.3.1.2.123 x 0x00 .1.3.6.1.2.1.17.7.1.4.3.1.4.123 x
0x00 .1.3.6.1.2.1.17.7.1.4.3.1.5.123 i 4

VLAN 123 is created, but the name TEST is not applied:

#sh vlan brief

Configured PORT-VLAN entries: 5
Maximum PORT-VLAN entries: 4095
Default PORT-VLAN id: 1

VLAN Name Encap ESI Ve Pri Ports

---- ---- ----- --- ----- --- -----

1 DEFAULT-VL - - Untagged
Ports : e 1/1 to 1/24 e 2/1 to 2/4
123 [None] - - Statically
tagged Ports : e 1/10 to 1/11

FWIW the above command works fine on other switches that I am testing
against, they all save the name as expected.

Attempting to set the name afterwards via a separate snmpset doesnt yeild
any better results.

Does anyone know what Im doing wrong here? Should I be poking a different
OID perhaps?

Running:

System: NetIron CER (Serial #: ...., Part #: ....)
Boot : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
Communications Systems, Inc.
Monitor : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
Communications Systems, Inc.
IronWare : Version 5.6.0dT183 Copyright (c) 1996-2013 Brocade
Communications Systems, Inc.

Software might be a bit old, could probably try a new version if people
think that might help.

Cheers
Tom
Re: CER - Creating VLANs via SNMP - cant set name? [ In reply to ]
Hi,

1.3.6.1.2.1.17.7.1.4.3 is read-only. Have a look at
1.3.6.1.4.1.1991.1.1.3.2.7.1.21 instead.

snmpwalk -v2c -c $COMMUNITY $IP 1.3.6.1.4.1.1991.1.1.3.2.7.1.21
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 = STRING: "TEST2"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.124 = STRING: "VLAN124"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.125 = STRING: "VLAN125"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.126 = STRING: "VLAN126"

snmpset -v2c -c $COMMUNITY $IP iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 s
HELLOMYFRIEND
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 = STRING: "HELLOMYFRIEND"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.124 = STRING: "VLAN124"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.125 = STRING: "VLAN125"
iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.126 = STRING: "VLAN126"


You can also take a look at some other tools than can configure advanced
things via ssh or telnet or can inject whole configurations.

Some people use

Netmikto
https://github.com/ktbyers/netmiko

and there is also kind of official brocade client called clicrud
https://github.com/DavidJohnGee/clicrud

I did my own injection client a while ago to escape the python world.
https://github.com/ipcjk/brocadecli

Regards

Jörg

On 22 Jun 2017, at 10:58, Tom Storey wrote:

> Hi everyone,
>
> Im writing some scripts that create VLANs and assigns ports to them
> via
> SNMP, and so far everything is working pretty good, except that when I
> create the VLAN, it doesnt seem to save the name that I supply along
> with
> it. For example, when I execute the following command:
>
> snmpset -v2c -c.... x.x.x.x .1.3.6.1.2.1.17.7.1.4.3.1.1.123 s TEST
> .1.3.6.1.2.1.17.7.1.4.3.1.2.123 x 0x00 .1.3.6.1.2.1.17.7.1.4.3.1.4.123
> x
> 0x00 .1.3.6.1.2.1.17.7.1.4.3.1.5.123 i 4
>
> VLAN 123 is created, but the name TEST is not applied:
>
> #sh vlan brief
>
> Configured PORT-VLAN entries: 5
> Maximum PORT-VLAN entries: 4095
> Default PORT-VLAN id: 1
>
> VLAN Name Encap ESI Ve Pri
> Ports
>
> ---- ---- ----- --- ----- ---
> -----
>
> 1 DEFAULT-VL - -
> Untagged
> Ports : e 1/1 to 1/24 e 2/1 to 2/4
> 123 [None] - -
> Statically
> tagged Ports : e 1/10 to 1/11
>
> FWIW the above command works fine on other switches that I am testing
> against, they all save the name as expected.
>
> Attempting to set the name afterwards via a separate snmpset doesnt
> yeild
> any better results.
>
> Does anyone know what Im doing wrong here? Should I be poking a
> different
> OID perhaps?
>
> Running:
>
> System: NetIron CER (Serial #: ...., Part #: ....)
> Boot : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
> Communications Systems, Inc.
> Monitor : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
> Communications Systems, Inc.
> IronWare : Version 5.6.0dT183 Copyright (c) 1996-2013 Brocade
> Communications Systems, Inc.
>
> Software might be a bit old, could probably try a new version if
> people
> think that might help.
>
> Cheers
> Tom
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: CER - Creating VLANs via SNMP - cant set name? [ In reply to ]
Hi Jörg,

Much appreciated! I am back in business with this OID. I still cant seem to
create and set the VLAN name in one operation, but with this OID I can
create and then set its name afterwards in a two step operation which is
fine.

Maybe I can if I play around using only OIDs from this MIB some more...

Tom

On 22 June 2017 at 20:15, Jörg Kost <jk@ip-clear.de> wrote:

> Hi,
>
> 1.3.6.1.2.1.17.7.1.4.3 is read-only. Have a look at
> 1.3.6.1.4.1.1991.1.1.3.2.7.1.21 instead.
>
> snmpwalk -v2c -c $COMMUNITY $IP 1.3.6.1.4.1.1991.1.1.3.2.7.1.21
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 = STRING: "TEST2"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.124 = STRING: "VLAN124"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.125 = STRING: "VLAN125"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.126 = STRING: "VLAN126"
>
> snmpset -v2c -c $COMMUNITY $IP iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 s
> HELLOMYFRIEND
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.123 = STRING: "HELLOMYFRIEND"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.124 = STRING: "VLAN124"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.125 = STRING: "VLAN125"
> iso.3.6.1.4.1.1991.1.1.3.2.7.1.21.126 = STRING: "VLAN126"
>
>
> You can also take a look at some other tools than can configure advanced
> things via ssh or telnet or can inject whole configurations.
>
> Some people use
>
> Netmikto
> https://github.com/ktbyers/netmiko
>
> and there is also kind of official brocade client called clicrud
> https://github.com/DavidJohnGee/clicrud
>
> I did my own injection client a while ago to escape the python world.
> https://github.com/ipcjk/brocadecli
>
> Regards
>
> Jörg
>
>
> On 22 Jun 2017, at 10:58, Tom Storey wrote:
>
> Hi everyone,
>>
>> Im writing some scripts that create VLANs and assigns ports to them via
>> SNMP, and so far everything is working pretty good, except that when I
>> create the VLAN, it doesnt seem to save the name that I supply along with
>> it. For example, when I execute the following command:
>>
>> snmpset -v2c -c.... x.x.x.x .1.3.6.1.2.1.17.7.1.4.3.1.1.123 s TEST
>> .1.3.6.1.2.1.17.7.1.4.3.1.2.123 x 0x00 .1.3.6.1.2.1.17.7.1.4.3.1.4.123 x
>> 0x00 .1.3.6.1.2.1.17.7.1.4.3.1.5.123 i 4
>>
>> VLAN 123 is created, but the name TEST is not applied:
>>
>> #sh vlan brief
>>
>> Configured PORT-VLAN entries: 5
>> Maximum PORT-VLAN entries: 4095
>> Default PORT-VLAN id: 1
>>
>> VLAN Name Encap ESI Ve Pri Ports
>>
>> ---- ---- ----- --- ----- --- -----
>>
>> 1 DEFAULT-VL - - Untagged
>> Ports : e 1/1 to 1/24 e 2/1 to 2/4
>> 123 [None] - -
>> Statically
>> tagged Ports : e 1/10 to 1/11
>>
>> FWIW the above command works fine on other switches that I am testing
>> against, they all save the name as expected.
>>
>> Attempting to set the name afterwards via a separate snmpset doesnt yeild
>> any better results.
>>
>> Does anyone know what Im doing wrong here? Should I be poking a different
>> OID perhaps?
>>
>> Running:
>>
>> System: NetIron CER (Serial #: ...., Part #: ....)
>> Boot : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
>> Communications Systems, Inc.
>> Monitor : Version 5.6.0cT185 Copyright (c) 1996-2013 Brocade
>> Communications Systems, Inc.
>> IronWare : Version 5.6.0dT183 Copyright (c) 1996-2013 Brocade
>> Communications Systems, Inc.
>>
>> Software might be a bit old, could probably try a new version if people
>> think that might help.
>>
>> Cheers
>> Tom
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>