[Mpls-agent-devel] mpls-agent project help

[<kis...@wi...>]

=20
=20
=20
=20
Sir
        Thanks a lot. I need to develop a SNMP agent for the MIB defined =
for objects like=20
       mplsLspName                 =20
        mplsLspAge                     =20
        mplsLspTimeUp               =20
        mplsLspFrom                    =20
        mplsLspTo                        =20
        mplsPathName                  =20
        mplsPathBandwidth          =20
        mplsPathJitter                    =20
        mplsPathDelay                  =20
        mplsPathLosses                 =20
        mplsPathLatency  =20
=20
Where should I modify the SNMP agent code you developed one to suite to =
the MIB above?.. How to fetch bandwidth,delay ,jitter info from the =
kernel?
=20
Regards,
Kishor
=20
=20
=20
=20
-----Original Message-----
From: Josdeyvi Russi [mailto:jr...@uo...]=20
Sent: Friday, February 24, 2006 2:13 AM
To: Kishor Krishna
Cc: mpl...@li...
Subject: Re: Re: [mpls-linux-general] command help
=20
Hi Kishor,
=20
For the label table the MIB MPLS-LSR have 3 major tables: =
mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable. To populate these =
tables, your SNMP Agent must read the ilm, nhlfe and xc internal tables =
from MPLS for Linux and put the things in the correct place.
=20
For example, if I do a set of commands like:
=20
=20
# mpls labelspace add dev eth1 labelspace 0
# mpls ilm add label gen 100 labelspace 0
I will get the following ILM table:
[root@MPLSCORE~]# mpls ilm sh
ILM entry label gen 100 labelspace 0 proto ipv4=20
pop forward key 0x00000002 (385664 bytes, 6026 pkts, 0 dropped)
And my Labelspace will be:
[root@MPLSCORE~]# mpls labelspace sh
LABELSPACE entry dev eth1 labelspace 0
The SNMP agent then must READ this output in somehow. You can directly =
acess the kernel using RTNetlink protocol (hack the mpls command of MPLS =
for Linux to learn how to do it) ou simple read and scan the output =
lines in your program. Doing it you must have the following at your MIB =
browser:
[root@MPLSCORE~]# snmpwalk -v2c -c public -O T -O S -O n localhost =
MPLSLSRSTDMIB::mplsInSegmentTable
.1.3.6.1.2.1.10.166.2.1.4.1.2.4.0.0.0.1 =3D INTEGER: 0
.1.3.6.1.2.1.10.166.2.1.4.1.3.4.0.0.0.1 =3D Gauge32: 100
.1.3.6.1.2.1.10.166.2.1.4.1.4.4.0.0.0.1 =3D OID: .0.0
.1.3.6.1.2.1.10.166.2.1.4.1.5.4.0.0.0.1 =3D INTEGER: 1
.1.3.6.1.2.1.10.166.2.1.4.1.6.4.0.0.0.1 =3D INTEGER: ipV4(1)
.1.3.6.1.2.1.10.166.2.1.4.1.7.4.0.0.0.1 =3D HexSTRING:
34 2E 30 2E 30 2E 30 2E 32 00 FF BF AA D8 EB 43 [4.0.0.0.2......C]=20
.1.3.6.1.2.1.10.166.2.1.4.1.8.4.0.0.0.1 =3D INTEGER: other(2)
.1.3.6.1.2.1.10.166.2.1.4.1.9.4.0.0.0.1 =3D OID: .0.0
.1.3.6.1.2.1.10.166.2.1.4.1.10.4.0.0.0.1 =3D INTEGER: active(1)
.1.3.6.1.2.1.10.166.2.1.4.1.11.4.0.0.0.1 =3D INTEGER: volatile(2)
=20
I recommend you to read the following book:
=20
Nadeu, Thomas D., "MPLS Network Management", 2003, Morgan Kaufmann =
Publishers.
=20
Good luck!
=20
Josdeyvi Russi
=20
=20
----------------------------------------------
The scope stuff is not mpls-linux specific, read the iproute2 documents
for info about 'scope'.

There is a SF project that implements a SNMP agent for mpls-linux.  Do
a search on the SF site for mpls and it will be one of the matches.

BTW SF =3D3D=3D3D sourceforge.net

On Wed, Feb 22, 2006 at 10:24:27AM +0530, kis...@wi... =
wrote:
> Hii
> =3D20
> =3D20
> I didn't get what do mean scope link in
> "
>    10.200.19.1 via 10.200.19.1 dev eth0 spec_nh 0x8847 0x2
>    192.168.2.9/24 dev eth0 scope link
>    10.200.19.1/24 dev eth0 proto kernel scope link src =
10.200.19,.1=3D20
>    127.0.0.0/8 dev lo scope link"
> =3D20
> One more thing how can I access label table from SNMP agent? =
Specifically=3D
 are there any functions or commands for this?. Help me
> =3D20
> Thanks and Regards,
> =3D20
> Kishor
> =3D20

--=3D20
James R. Leu
jl...@mi...


The information contained in this electronic message and any attachments =
to this message are intended for the exclusive use of the addressee(s) =
and may contain proprietary, confidential or privileged information. If =
you are not the intended recipient, you should not disseminate, =
distribute or copy this e-mail. Please notify the sender immediately and =
destroy all copies of this message and any attachments.=20

WARNING: Computer viruses can be transmitted via email. The recipient =
should check this email and any attachments for the presence of viruses. =
The company accepts no liability for any damage caused by any virus =
transmitted by this email.

www.wipro.com
=20