[c-nsp] NX-OS - Fabric Path

Lincoln Dale ltd at cisco.com
Mon Jul 19 23:05:56 EDT 2010


there is no "default configuration" or pre-coded 10.1.1.50 ip-address on mgmt0.
first time you boot a switch it starts the setup dialog with a serial console port.

<http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/fundamentals/421_n1_1/Cisco_Nexus_5000_Series_NX-OS_Fundamentals_Configuration_Guide_Release_4_2_1_N1_1_chapter3.html#con_1073243>

if you had a switch with a configuration then either they were shipped from manufacturing incorrectly (i guess its a possibility), or your installation guys thought it was a good idea to configure it that way.

as i can find no examples of the former listed in bug searches internal to cisco, i'd say it points at the latter.



cheers,

lincoln.


On 20/07/2010, at 12:36 PM, 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/




More information about the cisco-nsp mailing list