Mailing List Archive: CLID via SNMP from AS5300

CLID via SNMP from AS5300

Feb 23, 2005, 1:33 PM

Post #1 of 4 (1470 views)

I used the following link to get the OIDs to extract from my AS5300's useful
information for my support organization:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/nmswhole/nmshavs/gmibapp.htm

However.. the OID for CLID (1.3.6.1.4.1.9.10.19.1.3.1.1.2) appears to return
nothing at all. Not an error, just no data. I'm using 12.2(27) but couldn't
find anything interesting mentioning that perhaps this information does not
apply to that version of IOS. Anyone run into this before?

--
Jason T. Nelson <jtn@jtn.cx> http://www.jtn.cx/~jtn/
BOFH Extraordiaire & Sysadmin Ombudsman GPG key 0xFF676C9E
GPG key fingerprint = 6272 5482 EDDD D0A3 FED2 262A FABB 599D FF67 6C9E
disclaimer: My opinions are my own. Don't bother my employer about them.

Re: CLID via SNMP from AS5300 [ In reply to ]

gk at ax

Feb 24, 2005, 2:03 AM

Post #2 of 4 (1416 views)

Permalink

On Wednesday 23 February 2005 21:33, Jason T. Nelson wrote:
> http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/nmswhole/
>nmshavs/gmibapp.htm
>
> However.. the OID for CLID (1.3.6.1.4.1.9.10.19.1.3.1.1.2)
> appears to return nothing at all. Not an error, just no data.

Same to me with 12.2(15)T9 but there seems to be an error within the
documentation the link provided because the SNMP navigator shows
this:
(http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en)

1.3.6.1.4.1.9.10.19.1.3.1.1.2:
Arbitrary small integer to distinguish calls that occured
at the same time tick.

1.3.6.1.4.1.9.10.19.1.3.1.1.12:
The remote telephone number. For a call into the device,
this is the originating number. For a call out of the
device, this is the dialed number. If not available the
string length is zero.

--
Gerald

()
/\ ASCII RIBBON AGAINST HTML MAILS

Re: CLID via SNMP from AS5300 [ In reply to ]

achatz at forthnet

Feb 24, 2005, 9:09 AM

Post #3 of 4 (1415 views)

Permalink

Using 12.2(15)T14 is working fine for me:

$ snmpwalk -v2c -c COMMUNITY ROUTER .1.3.6.1.4.1.9.10.19.1.3.1.1.12
enterprises.9.10.19.1.3.1.1.12.790179440.0 = "XXXXX98197"
enterprises.9.10.19.1.3.1.1.12.803547534.0 = "XXXXX17573"
enterprises.9.10.19.1.3.1.1.12.804000025.0 = "XXXXX69009"
enterprises.9.10.19.1.3.1.1.12.804038138.0 = "XXXXX84429"
enterprises.9.10.19.1.3.1.1.12.804329468.0 = "XXXXX26201"
enterprises.9.10.19.1.3.1.1.12.804390170.0 = "XXXXX98226"
enterprises.9.10.19.1.3.1.1.12.804474882.0 = "XXXXX75044"
enterprises.9.10.19.1.3.1.1.12.804874587.0 = "XXXXX28231"
.....

gk@ax.tc wrote on 24/2/2005 11:03:

> On Wednesday 23 February 2005 21:33, Jason T. Nelson wrote:
>
>>http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/nmswhole/
>>nmshavs/gmibapp.htm
>>
>>However.. the OID for CLID (1.3.6.1.4.1.9.10.19.1.3.1.1.2)
>>appears to return nothing at all. Not an error, just no data.
>
>
> Same to me with 12.2(15)T9 but there seems to be an error within the
> documentation the link provided because the SNMP navigator shows
> this:
> (http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en)
>
> 1.3.6.1.4.1.9.10.19.1.3.1.1.2:
> Arbitrary small integer to distinguish calls that occured
> at the same time tick.
>
> 1.3.6.1.4.1.9.10.19.1.3.1.1.12:
> The remote telephone number. For a call into the device,
> this is the originating number. For a call out of the
> device, this is the dialed number. If not available the
> string length is zero.
>
>

Re: CLID via SNMP from AS5300 [ In reply to ]

jtn at jtn

Feb 24, 2005, 9:17 AM

Post #4 of 4 (1429 views)

Permalink

In our last exciting episode, Tassos Chatzithomaoglou (achatz@forthnet.gr) said:
> Using 12.2(15)T14 is working fine for me:
>
> $ snmpwalk -v2c -c COMMUNITY ROUTER .1.3.6.1.4.1.9.10.19.1.3.1.1.12
> enterprises.9.10.19.1.3.1.1.12.790179440.0 = "XXXXX98197"
> enterprises.9.10.19.1.3.1.1.12.803547534.0 = "XXXXX17573"
> enterprises.9.10.19.1.3.1.1.12.804000025.0 = "XXXXX69009"
> enterprises.9.10.19.1.3.1.1.12.804038138.0 = "XXXXX84429"
> enterprises.9.10.19.1.3.1.1.12.804329468.0 = "XXXXX26201"
> enterprises.9.10.19.1.3.1.1.12.804390170.0 = "XXXXX98226"
> enterprises.9.10.19.1.3.1.1.12.804474882.0 = "XXXXX75044"
> enterprises.9.10.19.1.3.1.1.12.804874587.0 = "XXXXX28231"
> .....

gk@ax.tc wrote on 24/2/2005 11:03:
> >
> >1.3.6.1.4.1.9.10.19.1.3.1.1.2:
> >Arbitrary small integer to distinguish calls that occured
> >at the same time tick.
> >
> >1.3.6.1.4.1.9.10.19.1.3.1.1.12:
> >The remote telephone number. For a call into the device,
> >this is the originating number. For a call out of the
> >device, this is the dialed number. If not available the
> >string length is zero.

Yep, that was it.. documentation mistake. Thanks a bunch :)

--
Jason T. Nelson <jtn@jtn.cx> http://www.jtn.cx/~jtn/
BOFH Extraordiaire & Sysadmin Ombudsman GPG key 0xFF676C9E
GPG key fingerprint = 6272 5482 EDDD D0A3 FED2 262A FABB 599D FF67 6C9E
disclaimer: My opinions are my own. Don't bother my employer about them.