Re: FR-ATM provisioning using CWM SNMP Agent?

jbocanegra · ‎08-18-2005

Hi all,

I'm having trouble on creating a atmfr circuit using SNMP Agent on CWM 15.0.

Following the examples on the documentation, I'm able to create an atm-atm cbr1 connection (intra BPX8620), a fr-fr fr connection (inter IGX8410); I do it like this:

snmpset -p 8161 -c private_comm a.b.c.d \

atmEndPointRowStatus.7.116.101.115.116.45.66.49.0.3.8.200.200 i 4 \

atmEndPointRowStatus.7.116.101.115.116.45.66.49.0.3.1.201.201 i 4 \

svConnLocalEndPt.0 o atmEndPointNodeName.7.116.101.115.116.45.66.49.0.3.1.201.201 \

svConnRemoteEndPt.0 o atmEndPointNodeName.7.116.101.115.116.45.66.49.0.3.8.200.200 \

svConnSubType.0 i 1 \

svConnRowStatus.0 i 4

snmpset -p 8161 -c private_comm a.b.c.d \

frEndPointRowStatus.7.116.101.115.116.45.73.49.0.5.1.1.123 i 4 \

frEndPointRowStatus.7.116.101.115.116.45.73.51.0.8.1.1.123 i 4 \

svConnLocalEndPt.0 o frEndPointEntry.1.7.116.101.115.116.45.73.49.0.5.1.1.123 \

svConnRemoteEndPt.0 o frEndPointEntry.1.7.116.101.115.116.45.73.51.0.8.1.1.123 \

svConnSubType.0 i 7 \

svConnRowStatus.0 i 4

So far so good. But when it comes to atm-fr vbr3 I get a generic error message:

snmpset -d -p 8161 -c private_comm a.b.c.d \

frEndPointRowStatus.7.116.101.115.116.45.73.51.0.8.1.1.123 i 4 \

atmEndPointRowStatus.7.116.101.115.116.45.66.49.0.3.8.200.200 i 4 \

svConnRemoteEndPt.0 o frEndPointEntry.1.7.116.101.115.116.45.73.51.0.8.1.1.123 \

svConnLocalEndPt.0 o atmEndPointNodeName.7.116.101.115.116.45.66.49.0.3.8.200.200 \

svConnSubType.0 i 4 \

svConnRowStatus.0 i 4

Error in packet.

Reason: (genError) A general failure occured

Nevertheless, the connection is created! What troubles me is that I can't catch the return value, for I would think there has been a problem. The snmp agent should return no error insted (if actually everything's ok as it seems at the node CLI).

Am I doing anything wrong?

Plus, according to the docs, svConnLocalEndPt should be fr and svConnRemoteEndPt atm, but I have to do it the other way around, or else the conn would be created.

Thanks for your time,

JM

a-vazquez · ‎08-23-2005

I think the failure is due to RPM-PR in the slot did not register the SNMP IPC port; that resulted in the provisioning thru SNMP failure.

The workaround is to switch the card back.

jbocanegra · ‎08-25-2005

Thanks, Anthony.

I may have misexplained myself, on two points:

1. It's an IGX not an MGX what seems to be causing trouble, so no RPM around.

2. Provisioning actually works, I get a genError message BUT I actually create a connection. This is what troubles me: why genError if things went OK on the node????