i'm guessing whoever upgraded the NX-OS on these did so using scp/ftp/tftp and thus needed to assign an ip-address to do so.
you could verify either way by looking at the output from "show accounting log" which saves all config commands and is persistent across power-loss and based on the date/time recorded there or order-of-events will likely give you an indication of whether it was your guys or the partner. the only reason i replied is that i've never heard of us ever doing such a thing, because it would be an incredibly dumb thing to do. setting a default ip-address might work for a home gateway router / switch, but for something in the data center - no. :) cheers, lincoln. On 20/07/2010, at 1:19 PM, Church, Charles wrote: > Lincoln, > > I did leave out one detail. These were originally 4.1(3)N2(1), but our > installation guys did bump them up to 4.2 individually prior to installing > them. They tell me they used that pre-configured address, not knowing any > better. But the attached file is a 5020 I took out of a box personally, and > fired up. I guess it's possible our reseller put that on there. I've seen > that same IP address on three other 5020s, and a half dozen 5010s, all bought > about the same time from the same reseller. I'll bounce it off them, sorry > about the finger pointing. > > Chuck > > -----Original Message----- > From: Lincoln Dale [mailto:[email protected]] > Sent: Monday, July 19, 2010 11:06 PM > To: Church, Charles > Cc: Manu Chao; Peter Rathlev; [email protected] > Subject: Re: [c-nsp] NX-OS - Fabric Path > > > 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: [email protected] >> [mailto:[email protected]] On Behalf Of Manu Chao >> Sent: Monday, July 19, 2010 7:17 PM >> To: Peter Rathlev >> Cc: Lincoln Dale; [email protected] >> 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 <[email protected]> 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 [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/ > > <5020 boot.TXT> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
