[c-nsp] NX-OS - Fabric Path

[Church, Charles]

Hmmm.  When I looked at the 'show accounting log' on one of mine, I did see
a couple other 10.1.1.x addresses other than the .50 when mine arrived.  I
didn't capture it, but they did have early dates which I believe were before
we received them.  Does seem like some test addresses.  I have the same
10.1.1.1 VRF 0/0 route as well.

Chuck 


-----Original Message-----
From: Charles Spurgeon [mailto:c.spurgeon at mail.utexas.edu] 
Sent: Saturday, July 24, 2010 6:57 PM
To: Church, Charles
Cc: Manu Chao; Peter Rathlev; Lincoln Dale; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] NX-OS - Fabric Path


Thanks for posting this. I am seeing the same thing and since I know
that I am the only person with access to the switches I was wondering
where those addrs had come from. I am building the lab config and no
one else knows which console TS lines I was using or which ints.

I have two new 5020s running 4.2(1)N1(1) that were unboxed a week and
a half ago and set up in the lab area.  I got a chance to work on them
today and when looking at the config one of them had mgmt0 configured
with 10.1.1.61 and the other had mgmt0 configured with 10.1.1.63. Both
of them had the management vrf default route pointed to 10.1.1.1.

I am the only person working on these switches and I bypassed the
setup config when they were powered up. I did NOT configure them with
these addrs. Nor were they connected to any live network that had
access to any DHCP server. I have no idea where they got this
config. Probably a leftover from mfg testing?

Their mgmt0 ints were not connected to the same VLAN and I didn't see
an ARP storm.

-Charles

Charles E. Spurgeon / UTnet
UT Austin ITS / Networking
c.spurgeon at its.utexas.edu / 512.475.9265

On Mon, Jul 19, 2010 at 10:35:56PM -0400, Church, Charles wrote:
> Just be careful about connecting the mgmt0 interfaces to anything prior to
> configuring them.  The default IP address of 10.1.1.50 on them (at least
on
> the 4.2 5000s) will cause a spectacular ARP storm when they conflict with
> each other, like when you attach several unconfigured ones to the same
> network.  Several thousand PPS, eventual reloads, etc.  Our installation
> guys got ahead of the config guys in our new DC, nice little mess it made.
> Not sure why they put a default address on them, hope it's something they
> correct in the future. 
> 
> Chuck 
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Manu Chao
> Sent: Monday, July 19, 2010 7:17 PM
> To: Peter Rathlev
> Cc: Lincoln Dale; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] NX-OS - Fabric Path
> 
> 
> Yes, but Nexus hardware is the right platform if you don't want to loose
any
> packet in your DC ;)
> 
> On Tue, Jul 20, 2010 at 12:56 AM, Peter Rathlev <peter at rathlev.dk> wrote:
> 
> > On Tue, 2010-07-20 at 08:29 +1000, Lincoln Dale wrote:
> > > right now the hardware is using a frame format that is not that of
> > > what TRILL uses (and as such we're using a Cisco-defined ethertype),
> > > however the hardware is capable of supporting standards-based TRILL as
> > > and when the standard is finalised & ratified.
> >
> > Would that hardware happen be the EARL8? And would there be any chance
> > that us "old skool" Cat6500 guys get to share to thrill of TRILL (or
> > similar)? :-)
> >
> > --
> > Peter
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6514 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20100725/da6dea6d/attachment.bin>