[c-nsp] Nexus equipment in corporate networks

[quinn snyder]

been using n7k deployed with vdc to have a physical collapsed core in a 
logical two-tier (distribution, core) model.  we've used this to keep 
used features to a minimum within each context (i.e. i'm not going to 
run vpc within my core context).

also deployed vdc to create isolation between production and test/dev 
server environments.

my pitch/reasoning is anytime you want consolidation of airgapped 
chassis into a single device -- you can use vdc.

q.

--
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

On 03/12/2011 12:26 PM, Chris Evans wrote:
> Can anyone provide their reasoning for using VDC? Everytime we review it
> there is no compelling reason for us to use it over a vrf.
>
> Interested in seeing others opinions.
>
> Thanks
> On Mar 12, 2011 1:14 PM, "Federico Cossu"<federico.cossu at gmail.com>  wrote:
>> 1) yes we do
>> 2) no management vdc, but yes we do that as well.
>>
>> bye
>>
>>
>> 2011/3/12 chris stand<cstand141 at gmail.com>:
>>> Hello,
>>>
>>>    Is anyone here using Nexus 7Ks in their corporate networks ?
>>> Other than the management vDC are you breaking up your networks into
>>> multiple vDCs ?
>>>
>>>
>>> thank you.
>>>
>>> Chris
>>> _______________________________________________
>>> 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/
>>>
>>
>>
>>
>> --
>> Lo hai detto hermano. No se escherza con Jesus! (Jesus Quintana)
>>
>> _______________________________________________
>> 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/