Thanks Jared. Yes it is SSM. I will try to flip PIM priority and align HSRP
active.
My initial thought was keeping everything as it is. Can I simply flip PIM
assert winner to PE1. Same way we can manually select STP root. Looks like
this is probably not an option. Didn't find relevant doc on how t
You can likely set "ip pim dr-priority" to get what you want
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipmulti/command/imc-cr-book/imc_i3.html#wp1384657000
- Jared
On Thu, Apr 07, 2022 at 09:07:34AM +1000, Roman Islam wrote:
> Thanks Jared. Yes it is SSM. I will try to fl
If this is ASM, what device is the RP? You may want to configure MSDP between
PE1/PE2 to help if that’s the case, or is this SSM or something else you may
want to just flip the PIM priority to make it pick what you want and see if you
can tie it to your HSRP (Cisco, might I suggest VRRP so you
Hi Everyone,
Has anyone experienced a TETRA Radio application issue if underlying IP
multicast transport sends persistent duplicate packets?
Here is my scenario as below:
PIM is running on the MPLS L3 VPN environment. C multicast is running on a
single VRF (TETRA) only. Source is running behind
On Mon, 22 Sep 2008 19:54:17 PDT, John Jensen said:
> She'd have to actually specify -b to ping a broadcast address,
Only true if you're pinging the broadcast address of a network that you
have an interface on, or the system has other knowledge of the netmask/etc.
If you're pinging a remote addre
At least I think that's how it works. :)
On Mon, Sep 22, 2008 at 7:54 PM, John Jensen <[EMAIL PROTECTED]> wrote:
> She'd have to actually specify -b to ping a broadcast address, and if
> she did, she would only get replies back from the hosts on that
> subnet, not duplicate replies from the same I
She'd have to actually specify -b to ping a broadcast address, and if
she did, she would only get replies back from the hosts on that
subnet, not duplicate replies from the same IP.
On Wed, Sep 10, 2008 at 5:11 AM, Sebastian Abt <[EMAIL PROTECTED]> wrote:
> * chloe K wrote:
>> When I ping the ip,
Sebastian Abt wrote:
* chloe K wrote:
When I ping the ip, I get the duplicate
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!)
What's your netmask? Is 192.168.0.95 your net's broadcast
From: Jon Lewis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 10, 2008 8:11 AM
To: chloe K
Cc: nanog@nanog.org
Subject: Re: duplicate packet
On Wed, 10 Sep 2008, chloe K wrote:
> When I ping the ip, I get the duplicate
>
> I check the ip is just one. Why it happens?
>
* chloe K wrote:
> When I ping the ip, I get the duplicate
>
> 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms
> 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!)
What's your netmask? Is 192.168.0.95 your net's broadcast address?
sebasti
On Wed, 10 Sep 2008, chloe K wrote:
When I ping the ip, I get the duplicate
I check the ip is just one. Why it happens?
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!)
Not enough information has been given.
Just
> -Original Message-
> From: chloe K [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 10, 2008 6:46 AM
> To: nanog@nanog.org
> Subject: duplicate packet
>
> Hi all
>
> When I ping the ip, I get the duplicate
>
> I check the ip is just one. Why it ha
.org
Subject: duplicate packet
Hi all
When I ping the ip, I get the duplicate
I check the ip is just one. Why it happens?
Thank you
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!)
64 bytes from 192.168.0.95: icmp_s
* chloe K.:
> When I ping the ip, I get the duplicate
>
> I check the ip is just one. Why it happens?
Are the source and target on the same subnet? Have you checked the
source MAC address of the response?
--
Florian Weimer<[EMAIL PROTECTED]>
BFK edv-consulting GmbH http:
Hi all
When I ping the ip, I get the duplicate
I check the ip is just one. Why it happens?
Thank you
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms
64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!)
64 bytes from 192.168.0.95: icmp_seq=2 ttl=63 time=0.296 ms
64 byt
15 matches
Mail list logo