> That's it. Step 1, buy the equipment at full price. Step 2, pay for the cloud
> management license, yearly. Step 3, no extended warranty option, so pay full
> price if equipment from step one fails.
As long as you're doing step 2 (which you *have* to, otherwise it's a brick),
isn't step 3 "repo
Hi,
Someone has positive or negative experience running
Checkpoint IPS cluster over ``long distance'' synch.
network? Real life limitations? Alternatives? Timers?
Cheers,
mh
Nanog,
I would like to poll the collective for experiences both positive and negative
with the Nexus line. More specifically I am interested in hearing about FEX
with N2K at the ToR and if this has indeed made any impact on Opex as well as
non-obvious shortcomings to using the fabric extenders.
The biggest thing we ran into was no support of spanning-tree on the FEX's. The
way we are setup, being STATE government, our agency controls the network up to
the FEX port. Beyond that, the agency's were in control of what they plugged
into our FEX ports.
-Original Message-
From: NANO
The n2k ToR is not a great design for user or storage interfaces if most of
your traffic is east/west. It is great as a low cost ilo/drac/choose your oob
port, or if most of your traffic is north/south. Biggest thing to remember is
that it is not a switch, and has limitations such as not conne
I think it depends on what the upstream product from the FEX is and what
your requirements are. Last I checked, eVPC was not supported on the N7K,
but it was supported as an option on the N5K platform. eVPC being the dual
homed FEX to two a pair of N7K's running a VPC cluster. I know this is an
o
I wasn't the implementing engineer but I've been at two places that did that, a
larger game company and a network gear manufacturer in their engineering
support computational hubs. I was there during planning and rollout at the
game company, very early in the Nexus lifespan.
Both sites brough
There are some unfortunate limitations in classifying incoming traffic.
It's been a while, but I think the rule is that Nexus 2000 devices can only
classify based on incoming 802.1p cos values.
It's a pretty strange and disappointing limitation for an edge device where
you're less likely to have
Hello folks,
We (Fastly) are seeing some funny performance issues with the recursive
resolvers inside Free from the vantage point of our customers and atlas
probes embedded in the network. I'd love to talk to somebody with the
ability to look, about what's going on.
Thanks
joel
signature.asc
D
On Mon, Feb 02, 2015 at 12:51:04PM -0600, David Bass wrote:
> The n2k ToR is not a great design for user or storage interfaces if most of
> your traffic is east/west. It is great as a low cost ilo/drac/choose your
> oob port, or if most of your traffic is north/south. Biggest thing to
> rememb
On Mon, 2 Feb 2015, Brandon Ewing wrote:
On Mon, Feb 02, 2015 at 12:51:04PM -0600, David Bass wrote:
The n2k ToR is not a great design for user or storage interfaces if most of
your traffic is east/west. It is great as a low cost ilo/drac/choose your oob
port, or if most of your traffic is n
> Brandon Ewing wrote:
>
>> David Bass wrote:
>> The n2k ToR is not a great design for user or storage interfaces if most of
>> your traffic is east/west. It is great as a low cost ilo/drac/choose your
>> oob port, or if most of your traffic is north/south. Biggest thing to
>> remember i
12 matches
Mail list logo
