[rbak-nsp] Subscriber bulkstats
Ian Calderbank
ian at calderbankconsulting.co.uk
Wed Mar 3 03:34:58 EST 2010
Jim,
I've had this working. The main difference is , the bulkstats policy was
defined in context local. I don't know if it works with non-local as the
context for that.
The subscriber default in non-local context then references this. I have no
problem with the bulkstats schema not appearing under sub default.
context local
bulkstats policy "sample-test"
localdir /flash
transfer-interval 120
sample-interval 5
limit 10000
remotefile format "%s_%s_%s" hostname date timeofday
receiver 192.168.99.1 primary mechanism ftp login bulkstats encrypted
xxxxxxxxxxxxx
context subscribers
subscriber default
bulkstats schema stats-per-sub policy sample-test local
ta
Ian
-----Original Message-----
From: redback-nsp-bounces at puck.nether.net
[mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of
redback-nsp-request at puck.nether.net
Sent: 02 March 2010 11:33
To: redback-nsp at puck.nether.net
Subject: redback-nsp Digest, Vol 27, Issue 2
Send redback-nsp mailing list submissions to
redback-nsp at puck.nether.net
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/redback-nsp
or, via email, send a message with subject or body 'help' to
redback-nsp-request at puck.nether.net
You can reach the person managing the list at
redback-nsp-owner at puck.nether.net
When replying, please edit your Subject line so it is more specific than
"Re: Contents of redback-nsp digest..."
Today's Topics:
1. Re: Subscriber bulkstats (jim at scusting.com)
2. Re: CLIPS on link-aggregated ports. (Vladislav Vasilev)
----------------------------------------------------------------------
Message: 1
Date: Tue, 02 Mar 2010 10:30:51 +0000
From: "jim at scusting.com" <jim at scusting.com>
To: redback-nsp at puck.nether.net
Subject: Re: [rbak-nsp] Subscriber bulkstats
Message-ID: <4B8CE8DB.9000003 at scusting.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Has anyone used Bulkstats for subscriber data collection? If so do you have
an example config I can try?
I'm still just getting "Data not yet available for Subscriber on circuit"
although the subscriber has now been connected for days and generating
traffic.
Thanks.
Jim.
> Hi,
>
> I'm just trying to enable some bulkstats data collection to retrieve
> in/out bytes for users connections etc but I'm not getting data for
> the subscribers. Here is what I have setup:
> ---------
> bulkstats schema profile subscriber subbulk format "%s %s %s %u %u"
> user_name session_id context_name inoctets outoctets
>
> context test
> bulkstats policy subbulk
> localdir /md/bulkstat
> sample-interval 5
> transfer-interval 5
> limit 2048
> remotefile format "%s_%s_%s_%s" context policy date timeofday header
> format "Collection file from host %s, Context:%s, Policy: %s"
> hostname context policy
> receiver 192.168.0.1 primary mechanism ftp login ftpbulk encrypted
> 2156606480B4B34C collection
>
> subscriber default
> bulkstats schema subbulk policy subbulk
> ---------
>
> (I dont actually see the bulkstats config under the subscriber default
> even though I have configured it there). I am getting files
> transferred every 5 minutes but all I get is:
>
> example
> Collection file from host blah, Context:test, Policy: subbulk
> subbulk: <Data not yet available for Subscriber on circuit:
> 255/16:1023:63/5/2/213250, sysup:62034306, epoch:1267200357>
>
> example:
> Collection file from host blah, Context:test, Policy: subbulk
> subbulk: <Data not yet available for Subscriber on circuit:
> 255/16:1023:63/5/2/213250, sysup:62035506, epoch:1267201557>
>
> All my files are reporting Data not yet available? Am I missing
> something? This is a test context with 1 valid active user.
>
> Thanks.
>
> Jim.
>
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
------------------------------
Message: 2
Date: Tue, 2 Mar 2010 11:33:31 +0000
From: Vladislav Vasilev <vvasilev at vvasilev.net>
To: ???? ????? <savin at orn.ru>
Cc: redback-nsp at puck.nether.net
Subject: Re: [rbak-nsp] CLIPS on link-aggregated ports.
Message-ID:
<353e59af1003020333v6171c95bu58aabadb3926558e at mail.gmail.com>
Content-Type: text/plain; charset="koi8-r"
That's the way economical mode works. You cannot have two active ports on a
subscribers facing link-group with SE100.
Regards,
Vladislav Vasilev
2010/3/2 ???? ????? <savin at orn.ru>
> Thanks, Vladislav.
>
>
>
> I've tried to use "access economical" link-group, both ports
> successfully added to link-group, but now here is another problem.
>
> One port in link-group always in standby state:
>
>
>
> [local]Redback#sh la actor
>
> Port Port Oper Recv Seln
>
> Lg-id Port State Priority key State State
>
> ----------------------------------------------------------------------
>
> 276 2/1 0x3f 32767 276 exchg active
>
> 276 2/2 0x3f 32767 276 exchg active
>
> 34 2/3 0x3f 32767 34 exchg active
>
> 34 2/4 0x7 32767 34 exchg actor-stdby
>
>
>
> In other link-group (link-group uplinks dot1q) both ports are active,
> but in access economical link-group one port is in standby state.
>
>
>
> Here is the full link-group config:
>
>
>
> [local]Redback#sh conf link-group
>
> Building configuration...
>
>
>
> Current configuration:
>
> !
>
> link-group clients access economical
>
> encapsulation dot1q
>
> qos hierarchical mode strict
>
> dot1q pvc 11
>
> bind interface test test
>
> lacp active
>
> !
>
> link-group uplinks dot1q
>
> bind interface mgmt local
>
> lacp active
>
> !
>
> !
>
> card carrier 2
>
> mic 1 ge-2-port
>
> mic 2 ge-2-port
>
> port ethernet 2/1
>
> link-group uplinks
>
> !
>
> !
>
> card carrier 2
>
> mic 1 ge-2-port
>
> mic 2 ge-2-port
>
> port ethernet 2/2
>
> link-group uplinks
>
> !
>
> !
>
> card carrier 2
>
> mic 1 ge-2-port
>
> mic 2 ge-2-port
>
> port ethernet 2/3
>
> link-group clients
>
> !
>
> !
>
> card carrier 2
>
> mic 1 ge-2-port
>
> mic 2 ge-2-port
>
> port ethernet 2/4
>
> link-group clients
>
> !
>
>
>
> WBR,
>
> Ilya Savin.
>
>
> ------------------------------
>
> *From:* Vladislav Vasilev [mailto:vvasilev at vvasilev.net]
> *Sent:* Tuesday, March 02, 2010 12:07 PM
> *To:* ???? ?????
> *Cc:* redback-nsp at puck.nether.net
> *Subject:* Re: [rbak-nsp] CLIPS on link-aggregated ports.
>
>
>
> There is a limitation with SE100 which basically prevents you from
> having an access link-group with more than 1 port. You must have
> noticed that all your ports begin with "2/x" which means they are on the
same slot - 2.
>
> With SE100 use economical mode instead.
>
> Regards,
> Vladislav Vasilev
>
>
> 2010/3/2 ???? ????? <savin at orn.ru>
>
> Hi.
>
>
>
> I have SE100 with ge-2-port card. SEOS-6.1.5.1-Release.
>
> I want to use two link-aggregated ports for CLIPS with dot1q pvc. I
> find out that is must be Access Link Group. I am trying to use this
> configuration:
>
>
>
> link-group test1 access
>
> encapsulation dot1q
>
> qos hierarchical mode strict
>
> dot1q pvc 10
>
>
>
> port ethernet 2/15
>
> no shutdown
>
> encapsulation dot1q
>
> link-group test1
>
>
>
> port ethernet 2/16
>
> no shutdown
>
> encapsulation dot1q
>
> link-group test1
>
>
>
>
>
> But when I trying to add second port to link-group, I see that message:
>
>
>
> [local]Redback(config-port)#link-group test1
>
> % Cannot add more than one link from same slot in the link-group
>
>
>
> Please, could anyone help me to resolve this problem?
>
>
>
> WBR,
>
> Ilya Savin.
>
>
>
>
>
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/redback-nsp/attachments/20100302/cab926ad
/attachment.html>
------------------------------
_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp
End of redback-nsp Digest, Vol 27, Issue 2
******************************************
More information about the redback-nsp
mailing list