[j-nsp] Failing VRRP on EX Switches
Hello All, I would like to know how we can fail VRRP from master to backup in case where physical ports are still up but the remote device has failed to secondary device. Scenario is like this: EX-SW-1 ISG-FW-1 || Trunk HA || EX-SW-2 ISG-FW-2 Here if for VLAN 30 EX-SW-1 is master and SW-2 is backup and in case FW1 has failed to FW2 but still physical link between SW-1 and FW-1 is still up VRRP is not failovering and routes are still active through that link. How we can resolve this issue? Track-IP might be one of option but I am also looking for other solutions. Your response will be highly appreciated. -- Regards, Rehan Rafi * * ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Destination Class Accounting: counters are zero
Hello List,
I have MX240 router (10.0 R4.7) with two peering links and two upstream links.
I need separate accounting of customer's traffic: to/from upstreams and
to/from peerings.
I configured an SCU input accounting on peering and upstream links,
DCU and SCU output accounting on customer's link:
minot...@br1-gdr.ki# show interfaces ae0 unit 753
vlan-id 753;
family inet {
accounting {
source-class-usage {
output;
}
destination-class-usage;
}
no-redirects;
filter {
output bw-100M-U;
}
address 109.68.41.133/30;
}
Then I applied export policy to forwarding table, now every route
has an assigned class, for example:
minot...@br1-gdr.ki# run show route juniper.net table Salt extensive | match
class
Destination class: to-Upstream
Source class: from-Upstream
Now let's check extensive information about customer's interface:
minot...@br1-gdr.ki# run show interfaces ae0.753 extensive
Logical interface ae0.753 (Index 97) (SNMP ifIndex 197) (Generation 168)
Description: Downstream: Digital Screens Kurenevka
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.753 ] Encapsulation: ENET2
StatisticsPacketspps Bytes bps
Bundle:
Input :1355645712 10824 1744298393787125788672
Output: 676249013 3535 50730352637 1954232
Link:
ge-2/0/5.753
Input :1355645712 10824 1744298393787125788672
Output: 676249013 3535 50730352637 1954232
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-2/0/5.753 0 000
Protocol inet, MTU: 1500, Generation: 198, Route table: 6
Flags: No-Redirects, DCU, SCU-out
PacketsBytes
Destination class(packet-per-second)(bits-per-second)
to-Other 1966210997515326
( 9) ( 4129)
to-Peering 904424 1216778711
( 2932) ( 32529971)
to-Upstream00
( 0) ( 0)
PacketsBytes
Source class (packet-per-second)(bits-per-second)
from-Other88128 5568059
( 0) (53)
from-Peering 534506 37189579
( 1136) (664770)
from-Upstream16017 1066310
( 97) ( 49421)
Output Filters: bw-100M-U-ae0.753-o,
Addresses, Flags: Is-Preferred Is-Primary
Destination: 109.68.41.132/30, Local: 109.68.41.133, Broadcast:
109.68.41.135, Generation: 177
Protocol multiservice, MTU: Unlimited, Generation: 199, Route table: 6
Policer: Input: __default_arp_policer__
Why 'to-Upstream' counters are zeroes?
Thanks in advance!
--
MINO-RIPE
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Failing VRRP on EX Switches
You can try to connect the EX-SW-1 to ISG-FW-2, and also EX-SW-2 to ISG-FW-1. Cheers, HuXu From: Rehan Rafi Date: 2012-05-15 16:40 To: juniper-nsp Subject: [j-nsp] Failing VRRP on EX Switches Hello All, I would like to know how we can fail VRRP from master to backup in case where physical ports are still up but the remote device has failed to secondary device. Scenario is like this: EX-SW-1 ISG-FW-1 || Trunk HA || EX-SW-2 ISG-FW-2 Here if for VLAN 30 EX-SW-1 is master and SW-2 is backup and in case FW1 has failed to FW2 but still physical link between SW-1 and FW-1 is still up VRRP is not failovering and routes are still active through that link. How we can resolve this issue? Track-IP might be one of option but I am also looking for other solutions. Your response will be highly appreciated. -- Regards, Rehan Rafi * * ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Destination Class Accounting: counters are zero
Hello there,
This might help
http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/source-class-usage-guidelines-solution.html
quote
A source or destination class is applied to a packet only once during the
routing table lookup. When a network prefix matches a class-usage policy,
SCU is assigned to packets first; DCU is assigned only if SCU has not been
assigned. Be careful when using both class types, since misconfiguration can
result in uncounted packets.
/quote
Rgds
Alex
- Original Message -
From: Alexander Shikoff minot...@crete.org.ua
To: juniper-nsp@puck.nether.net
Sent: Tuesday, May 15, 2012 9:25 AM
Subject: [j-nsp] Destination Class Accounting: counters are zero
Hello List,
I have MX240 router (10.0 R4.7) with two peering links and two upstream
links.
I need separate accounting of customer's traffic: to/from upstreams and
to/from peerings.
I configured an SCU input accounting on peering and upstream links,
DCU and SCU output accounting on customer's link:
minot...@br1-gdr.ki# show interfaces ae0 unit 753
vlan-id 753;
family inet {
accounting {
source-class-usage {
output;
}
destination-class-usage;
}
no-redirects;
filter {
output bw-100M-U;
}
address 109.68.41.133/30;
}
Then I applied export policy to forwarding table, now every route
has an assigned class, for example:
minot...@br1-gdr.ki# run show route juniper.net table Salt extensive |
match class
Destination class: to-Upstream
Source class: from-Upstream
Now let's check extensive information about customer's interface:
minot...@br1-gdr.ki# run show interfaces ae0.753 extensive
Logical interface ae0.753 (Index 97) (SNMP ifIndex 197) (Generation 168)
Description: Downstream: Digital Screens Kurenevka
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.753 ] Encapsulation: ENET2
StatisticsPacketspps Bytes bps
Bundle:
Input :1355645712 10824 1744298393787125788672
Output: 676249013 3535 50730352637 1954232
Link:
ge-2/0/5.753
Input :1355645712 10824 1744298393787125788672
Output: 676249013 3535 50730352637 1954232
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-2/0/5.753 0 000
Protocol inet, MTU: 1500, Generation: 198, Route table: 6
Flags: No-Redirects, DCU, SCU-out
PacketsBytes
Destination class(packet-per-second)(bits-per-second)
to-Other 1966210997515326
( 9) (
4129)
to-Peering 904424 1216778711
( 2932) (
32529971)
to-Upstream00
( 0) (
0)
PacketsBytes
Source class (packet-per-second)(bits-per-second)
from-Other88128 5568059
( 0) (
53)
from-Peering 534506 37189579
( 1136) (
664770)
from-Upstream16017 1066310
( 97) (
49421)
Output Filters: bw-100M-U-ae0.753-o,
Addresses, Flags: Is-Preferred Is-Primary
Destination: 109.68.41.132/30, Local: 109.68.41.133, Broadcast:
109.68.41.135, Generation: 177
Protocol multiservice, MTU: Unlimited, Generation: 199, Route table: 6
Policer: Input: __default_arp_policer__
Why 'to-Upstream' counters are zeroes?
Thanks in advance!
--
MINO-RIPE
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Destination Class Accounting: counters are zero
Hello!
On Tue, May 15, 2012 at 03:17:36PM +0100, Alex Arseniev wrote:
Hello there,
This might help
http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/source-class-usage-guidelines-solution.html
quote
A source or destination class is applied to a packet only once during the
routing table lookup. When a network prefix matches a class-usage policy,
SCU is assigned to packets first; DCU is assigned only if SCU has not been
assigned. Be careful when using both class types, since misconfiguration can
result in uncounted packets.
/quote
Rgds
Alex
I believe that there is no misconfiguration.
http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/source-class-usage-options-junos-nm.html
Source class usage (SCU) counts packets sent to customers by performing
lookups on the IP source address and the IP destination address. SCU makes it
possible to track traffic originating from specific prefixes on the provider
core and destined for specific prefixes on the customer edge. You must enable
SCU accounting on both the inbound and outbound physical interfaces.
Destination class usage (DCU) counts packets from customers by performing
lookups of the IP destination address. DCU makes it possible to track traffic
originating from the customer edge and destined for specific prefixes on the
provider core router.
Thus I configured SCU input on upstream's interface:
minot...@br1-gdr.ki# show interfaces ge-2/0/0 unit 200 family inet accounting
source-class-usage {
input;
}
... and SCU output and DCU on customer's interface:
minot...@br1-gdr.ki# show interfaces ae0 unit 753 family inet accounting
source-class-usage {
output;
}
destination-class-usage;
I tried to remove source-class-usage output from customer's interface
but this does not help, counters are zeroes:
minot...@br1-gdr.ki# run show interfaces ae0.753 extensive
Logical interface ae0.753 (Index 97) (SNMP ifIndex 197) (Generation 168)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.753 ] Encapsulation: ENET2
StatisticsPacketspps Bytes bps
Bundle:
Input :2130221797 20055 2875832668346232302248
Output: 911861056 7149 65210099204 3518416
Link:
ge-2/0/5.753
Input :2130221797 20055 2875832668346232302248
Output: 911861056 7149 65210099204 3518416
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-2/0/5.753 0 000
Protocol inet, MTU: 1500, Generation: 198, Route table: 6
Flags: No-Redirects, DCU
PacketsBytes
Destination class(packet-per-second)(bits-per-second)
to-Other17433 1679155
( 19) ( 9556)
to-Peering 20064858 29583263192
( 24066) ( 282133926)
to-Upstream00
( 0) ( 0)
Output Filters: bw-100M-U-ae0.753-o,
Addresses, Flags: Is-Preferred Is-Primary
Destination: 109.68.41.132/30, Local: 109.68.41.133, Broadcast:
109.68.41.135, Generation: 177
Protocol multiservice, MTU: Unlimited, Generation: 199, Route table: 6
Policer: Input: __default_arp_policer__
--
MINO-RIPE
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
