Between 15.3(3)S1 and S1a, yes just a naming change. I as upgrading from 15.3(1)S1.

-- Stephen

On 13/11/2013 8:03 AM, Adam Vitkovsky wrote:
So there actually is a difference between .S1 and .S1a?
I thought it's the same code and that just a naming changed.

adam

-----Original Message-----
From: cisco-nsp [mailto:[email protected]] On Behalf Of
Stephen Fulton
Sent: Wednesday, November 13, 2013 1:22 PM
To: [email protected]
Subject: Re: [c-nsp] ME3600 BFD session to A9K breaks after upgrade to
15.3(3)S1a

I upgraded an ME3600 to 15.3(3)S1a an hour ago from 15.3(1)s1, which had a
working BFD session with a directly connected 6500.  After the upgrade, BFD
stopped working.

Noticed that ISIS was also done (had previously been up).  Had to explicitly
define the CLNS MTU on the ME3600X interface (was defined on the 6500
opposite) and ISIS came back up.  BFD came up on that interface at the time
as well.

On 12/11/2013 2:09 PM, Jason Lixfeld wrote:
No, it's not the same, but it's not the same on a working interface
either.

The 15.3(3)S1a ME3600 has a CLNS MTU of 9213.
The 15.3(3)S ME3600 has a CLNS MTU of 1497.
The 4.3.1 ASR9000 has a CLNS MTU of 9199.

15.3(3)S1a ME3600 is directly connected to the 15.3(3)S ME3600 and has an
ISIS adjacency and BFD session.
The 15.3(3)S1a ME3600 is directly connected to the 4.3.1 ASR9K and does
not have an ISIS adjacency or BFD session.

If it was a CLNS MTU issue, I'd suspect the 15.3(3)S1a and 15.3(3)S ME3600
ISIS and BFD session would be down as well, but it's not.

That notwithstanding, the BFD session between the 9K and 15.3(3)S1a ME3600
is down as well.  ISIS CLNS issue or not, that's not going to work unless
BFD works, no?

On Nov 12, 2013, at 10:20 AM, Adam Vitkovsky <[email protected]>
wrote:

Hi Jason,

Is the CLNS MTU equal at both ends please?
It appears this is again one of the conditions to form ISIS session
in
15.3(3)S1

adam



_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to