Hey Hugo:
Thanks for your reply. I have tried renaming the cluster interfaces to
match the node interfaces but i still have the same problem. However, i have
noticed that if i specify "Any" as the install on option for any of my QoS
rules, those QoS rules are being displayed properly in SmartView Monitor.
All other rules which have the specific interface defined are now being
logged as no-match rules. Eg:
Source Destination Service Action Track
Install On
PC1 External HTTP Weight=30 Log Any
This rule is being correctly displayed in SmartView Monitor
Source Destination Service Action Track
Install On
PC1 External FTP Weight=30 Log Test:
Eth7
This rule is being displayed as a no-match rule, if the above rule is also
used. If this rule is my only QoS rule, it is being displayed as the Default
Rule in SmartView Monitor.
I hope that i am being clear.
You mentioned that you have come accross similar problems to this with R55
and R60. Were you able to resolve those problems? Any ideas?
Thanks for your help.
On 10/29/06, Hugo van der Kooij <hvdkooij AT vanderkooij DOT org> wrote:
On Sun, 29 Oct 2006, Satyam Mathura wrote:
> I have 3 NGX R61 clusters all managed by a single R61 SmartCenter
> Server. All cluster gateways are running FloodGate. I have ensured that
my
> cluster interface names exactly match the interface names on the nodes
as
> outlined in SK#30895. eg: cluster interface: eth0 , Node1: eth0 , Node2:
> eth0. The problem i'm experiencing is that the Top QoS rules in
SmartView
> Monitor only shows traffic passing as the Default Rule. None of my other
QoS
> rules are shown in SmartView Monitor. I know that FloodGate is working
as if
> i change the bandwidth setting on the interface or on a rule, users
> experience a change. My QoS rules, other than my Default rule, are not
being
> shown in SmartView monitor.
With other versions (R55 and R60) I have seen problems when the cluster
object is using the same names for the interfaces as the individual nodes.
Which would mean you would use eth0 on both cluster members but another
name, say if0, for the cluster object itself.
Wether or not you need to do this in your case is something you have to
find out the hard way. I do have a case open where a R61 gateway is not
able to provide SmartView with any interface details at all. But it is not
even on a cluster but it may indicate there might be a flaw in R61 in this
regard.
Hugo.
--
hvdkooij AT vanderkooij DOT org http://hvdkooij.xs4all.nl/
This message is using 100% recycled electrons.
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to LISTSERV AT amadeus.us.checkpoint DOT com
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
fw-1-owner AT ts.checkpoint DOT com
=================================================
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to LISTSERV AT amadeus.us.checkpoint DOT com
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
fw-1-owner AT ts.checkpoint DOT com
=================================================
|
