Hello everybody,
Although I have “no hello padding” configured, the adjacency won't come up
until I limit the CLNS MTU on some link in my network (there is an MTU
issue on that link, it's not 1500).
As far as I remember, Cisco IOS implementation of IS-IS will *still send
out first* IIHs
Hi,
Can you please advise me what could be the reason for the below output as
iam getting minor alarms highlighted in colour for cisco crs.
RP/0/RP0/CPU0:CP-CRS1-SHQ-01-02#show env leds
Tue Nov 25 11:20:09.955 KSA
0/0/*: Module (host) LED status says: OK
0/0/*: Module (plimasic) LED status
Hi Jason,
I'm actually working on a rollout of one setup where I'm trying to combine
Rosen mLDP with oldschool Rosen mGRE.
Though my setup is easy as the m-cast is going to be introduced only via one
POP -so I don't need to do the RPF selection on nodes capable of Rosen mLDP.
In theory it's
For us the reason we want to use Netflow in the core is mainly to do simplify
troubleshooting in the core especially in the cases of congested links or in
the event of unbalanced core links. A lot of services are passing from the core
including multicast TV, VOICE, Internet etc, and it will be
Hi Guys,
Actually I would like to know if you guys can provide me the solution on
below issue.
we are providing internet to one of our customer. our Connection is
connected on customer onsite 3 com switch. on 3com switch, his two ASA
firewalls are connected, Primary/Secondary as
In my setup, each ASA has a different IP. When the failover becomes
active, it assumes the IP of the active unit, and when the primary comes
back online, it assumes the IP of the failover unit. The documentation for
this setup can also be found here:
25.11.2014, 18:50, Ahsan Rasheed wrote:
Any other solution is possible, can we(ISP) use on our side to clear his
arp automatically when his primary ASA firewall drops the connection and
try to connect the secondary firewall same public IP but different Mac
address.
Hi,
I would use separate
On 25/11/2014 17:27, Scott Miller wrote:
In my setup, each ASA has a different IP.
which means that active / failover will not operate on a /30. The OP will
need /29 or larger.
Nick
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
Dell - Internal Use - Confidential
The first five IS-IS hellos are still padded to the full MTU size and
subsequent hellos are not once the adjacency is formed... this is to detect MTU
mismatches. If you cannot fix the MTU mismatch for some reason, you can also
work around it by setting the
Le 25/11/2014 18:48, Nick Hilliard a écrit :
On 25/11/2014 17:27, Scott Miller wrote:
In my setup, each ASA has a different IP.
which means that active / failover will not operate on a /30. The OP will
need /29 or larger.
Yes you can use one /30 ip for master and nothing for secondary, this
Hi alex,
If you use 'no hello padding always', the first IIH's are not padded.
On 25 Nov 2014, at 06:51, Alex K. nsp.li...@gmail.com wrote:
Hello everybody,
Although I have “no hello padding” configured, the adjacency won't come up
until I limit the CLNS MTU on some link in my network
no hello padding always. The Always keyword has been hidden for a long
time and was unhidden somewhat recently (I can't remember where). With
always none of the hellos are padded.
On Tue, Nov 25, 2014 at 12:51 AM, Alex K. nsp.li...@gmail.com wrote:
Hello everybody,
Although I have “no hello
Hi Ahsan,
The customer cannot configure the 'same' IP address on both ASAs in an
Active/Standby pair.
Each ASA's outside interface must have it's own IP (or the Standby could
be configured without an IP - but in that case the physical interface
would not be monitored for all failures).
When the
Interesting I never heard of the always option one learns something new every
day.
Though there's still this IIH padding madness when it gets to the actual size
of the IIH datagram and the allowed offset between CLNS MTU and the actual IIH
size.
adam
-Original Message-
From:
Hi David, Fabien all who replies ,
First I would like to say thank you so much for helping me on this issue.
I would like to clear few things. Customer is using /30 IP on Active
Firewall and Standby configured as no IP on its outside interface. Whenever
fail-over occurs, the issue is having
Hello,
A tunnel, on a DMVPN hub on a 7600/3BXL [1], doesn't get MPLS tagged
packets flowing in.
MPLS traceroute shows a DownStream Map mismatch at the tunnel entrance hop,
followed by looping packets until TTL 30 on the same IP.
0 10.0.52.22 MRU 9050 [Labels: 712848 Exp: 0]
L 1 10.0.55.32
Did you ever get this working Adam?
Cheers,
James.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
IOS-XE mtu values are consistent with IOS. (IOS-XR is different to IOS/XE with
regards to the different L2/L3 values).
Brad
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
vinny_abe...@dell.com
Sent: Wednesday, 26 November 2014 04:58
To:
On 25 Nov 2014, at 6:44, SECURITY @ CYTANET wrote:
For us the reason we want to use Netflow in the core is mainly to do
simplify troubleshooting in the core especially in the cases of
congested links or in the event of unbalanced core links. A lot of
services are passing from the core
Colleagues,
We have found a very interesting problem.
There are a dozen routers connected to a common 10.65.127.224/27 L2
backbone. All are running OSPF area 0. Any router which has the IP
address 10.65.127.246 cannot establish OSPF adjacency with some other
routers, showing them forever in
20 matches
Mail list logo
