date:20111001

Re: [c-nsp] switch with 2x 10GBASE-T interfaces

2011-10-01 Thread Martin T

Nikolay,
I'm afraid you are confusing this with C3KX-NM-10G module. Check the
table 3. C3KX-NM-10GT module is strictly 2x 10GBASE-T RJ45 ports(image
of the C3KX-NM-10GT: http://mcaf.ee/0bjty).

In general, "WS-C3750X-24S-S + C3KX-NM-10GT" seems to be a perfect
solution. WS-C3750X-24S-S has an "IP Base" image, which is enough
because I don't need advanced L3 features like EIGRP, OSPF, BGP and
IPv6 routing provided by "IP Services". WS-C3750X-24S-S is easily
upgradable thanks to StackWise Plus and StackPower technologies.
Supports dual redundant power supplies and in overall is a nice 1U
feature-rich switch according to specifications.

Just one hesitation with WS-C3750X-24S-S..is it possible to insert
1000BASE-T SFP's to first 22 ports(I would use last two SFP ports for
1000BASE-LX10 SFP's)? I mean 1000BASE-T SFP's have RJ45 connector
which is bit bulky and I'm not sure if it's possible to physically
insert 1000BASE-LX10 SFP's besides each other? Any experience with
this?

In addition, as I checked the 4900 series as well, do built in X2
ports(the ones in the chassis http://mcaf.ee/us1dt) in 4900M support
"TwinGig Converter Module"? According to documentation they don't. Any
experience with this?

regards,
martin

2011/10/1 Nikolay Shopik :
> Martin,
>
> C3KX-NM-10GT allow you to install only two 10Gb SFP+ or 4 1Gbit SFP, or just
> ony 10Gbit SFP+ plus 2 1Gbit SFP. You can take look here
> http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6406/data_sheet_c78-584733.html
> at table 4.
>
>
>
> On 30.09.2011 23:44, Martin T wrote:
>>
>> Alan, Arne:
>>
>> WS-C3750X-24S-E + C3KX-NM-10GT seems to be a perfect solution!
>>
>> WS-C3750X-24S-E has 24 SFP ports so one could use 12 1000BASE-T SFP's
>> + 2 1000BASTE-LX10 SFP's and C3KX-NM-10GT module provides two
>> 10GBASE-T ports so all the requirements seems to be fulfilled.
>>
>>
>> Jim,
>> I'm afraid WS-C4928-10GE would not suite because two 10GBASE-T ports
>> are must-have. If there would be 10GBASE-T X2 modules available, this
>> switch would be a nice option.
>>
>>
>> Kevin,
>> if possible, I would prefer Cisco.
>>
>>
>>
>> What do you think about "WS-C3750X-24S-E + C3KX-NM-10GT" solution? In
>> addition, are there 10GBASE-T SFP+ modules available on the
>> market(Cisco or third-party)?
>>
>>
>> regards,
>> martin
>>
>>
>> 2011/9/30 Kevin Loch:
>>>
>>> Martin T wrote:

 Is there a Cisco switch(non-modular preferably) which fulfils those
 requirements:

 1) 12 or more 1000BASE-T ports
 2) 2x SFP port for 1000BASE-LX10 SFP's
 3) 2x 10GBASE-T ports(for IBM 10Gb iSCSI Host Interface Card 81Y9613,
 which has two 10GBASE-T interfaces)
>>>
>>> It's not Cisco but Dell 6248 does have a 2 port 10Gbase-T module
>>> option.  The onboard SFP ports will accept any generic 1G SFP's
>>> (for your LX10 optics).
>>>
>>> - Kevin
>>>
>>> ___
>>> cisco-nsp mailing list  cisco-nsp@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@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Tim Stevenson

Interface e1/27 on n7k12 appears to be connected 
to g2/2 on the 6500. I rest my case. ;)

Tim

At 12:40 PM 10/1/2011, Antonio Soares contended:

Hello Tim,

Very simple setup:

N7K11===CAT6500===N7K12

The RP is the CAT6500. The relevant configs bellow:

CAT6500 (The RP):

ip multicast-routing
!
interface Loopback0
ip address 3.3.3.3 255.255.255.255
ip pim sparse-mode
!
interface GigabitEthernet2/1
ip address 10.12.1.2 255.255.255.0
ip pim sparse-mode
!
interface GigabitEthernet2/2
ip address 10.12.2.2 255.255.255.0
ip pim sparse-mode
no ip mroute-cache
!
ip pim rp-address 3.3.3.3
!

N7K11 (The source):

feature ospf
feature pim

interface Ethernet1/27
  ip address 10.12.1.1/24
  ip router ospf 1 area 0.0.0.0
  ip pim sparse-mode
  no shutdown

ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4
ip pim ssm range 232.0.0.0/8

N7K12 (The destination)

feature ospf
feature pim

interface Ethernet1/27
  ip address 10.12.2.1/24
  ip router ospf 1 area 0.0.0.0
  ip pim sparse-mode
  ip igmp join-group 239.1.2.3
  no shutdown

ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4
ip pim ssm range 232.0.0.0/8

It works if the ip igmp join is moved to the loopback interface on the N7K12.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoa...@netcabo.pt
http://www.ccie18473.net

From: Tim Stevenson [mailto:tstev...@cisco.com]
Sent: sábado, 1 de Outubro de 2011 16:06
To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

Hi Antonio,

Can you please describe the exact topology here? 
Which interfaces you're using, what they're connected to, and where is the RP?

One thing to be aware of with NXOS is that 
things only show up in sh ip mroute if the 
client protocol/process (eg IGMP in this case) 
has reason to feed them there. sh ip mroute is 
basically looking at the MRIB view of the world and nothing else.

WRT the ip igmp join-group command, it does two 
things: one is it causes that interface to send 
IGMP joins for that group out that interface as 
if it were a host. The other is that, if the 
router is PIM DR on that interface, it feeds the 
*G & the OIF to the MRIB. It's only at that 
point you'll see the entry in sh ip mroute. 
Otherwise, you'll only see it in the IGMP group 
membership table, ie, sh ip igmp group.

My guess here is you're not DR on this 
interface, so I assume there's another router on 
the segment that IS the DR. If you check the 
mrouting there I suspect you'll see the *G entry 
joined to the RPT (driven by the IGMP joins sent 
on that segment from the router w/the join-group command).

WRT the loopback "working", what you're seeing 
is that this router is now the only means by 
which to reach that 'network segment' (ie, it's 
obviously going to be DR on its own loopback) so 
it will report the *G & OIF to the MRIB and then 
you'll see the entry in sh ip mroute.

Hope that helps,
Tim

At 03:24 AM 10/1/2011, Antonio Soares contended:

This is lab environment, I'm just testing basic multicast features with
nexus.

The command reference says the following:

"When you enter this command, the traffic generated is handled by the device
CPU, not the hardware."

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c 

ommand/reference/mcr_cmds_i.html#wp1230243

The "ip igmp static-group" was replaced by the command:

ip igmp static-oif

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c 

ommand/reference/mcr_cmds_i.html#wp1034808

When I have the igmp joing on the physical interface, the (*,G) entry is
created then it disappears. But I see the (*,G) entry on the RP and I
verified that the traffic is actually sent to the nexus.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoa...@netcabo.pt
http://www.ccie18473.net

-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[ mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Phil Mayers
Sent: sábado, 1 de Outubro de 2011 10:49
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

On 10/01/2011 01:31 AM, Antonio Soares wrote:
> Hello group,
>
> Anyone knows why the "ip igmp join-group" does not work on a physical
> interface but it works fine on a loopback interface ?

"ip igmp join-group" is a CPU command; it makes the CPU join the group
and receive the packets. I imagine this might not work on a hardware
platform, with an interface which will be processed in hardware.

Are you sure you don't want "ip igmp static-group"?

What's your use case?
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at

Re: [c-nsp] Max IPv6 route entries for Cisco 4948E

2011-10-01 Thread Tóth András

Hi Jose,

The 57000 is shared between IPv4 and IPv6.

Best regards,
Andras

On Fri, Sep 30, 2011 at 4:39 PM, Lobo  wrote:
> Hey everyone.  We're looking at the 4948E as a possible replacement for our
> aging 3550-12Ts and we were wondering if anyone has any information with
> regards to the maximum number of ipv6 routes that it will be able to hold.
>  The only information I've found is that the device has 57,000 routes
> maximum but it doesn't say if that number also applies for ipv6.  Based on
> other platforms, I'm thinking that maybe it will be half of that?
>
> Thanks for any info you guys can provide.
>
> Jose
> ___
> cisco-nsp mailing list  cisco-nsp@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Antonio Soares

Hello Tim,

Very simple setup:

N7K11===CAT6500===N7K12

The RP is the CAT6500. The relevant configs bellow:

CAT6500 (The RP):

ip multicast-routing

!

interface Loopback0

ip address 3.3.3.3 255.255.255.255

ip pim sparse-mode

!

interface GigabitEthernet2/1

ip address 10.12.1.2 255.255.255.0

ip pim sparse-mode

!

interface GigabitEthernet2/2

ip address 10.12.2.2 255.255.255.0

ip pim sparse-mode

no ip mroute-cache

!

ip pim rp-address 3.3.3.3

!

N7K11 (The source):

feature ospf

feature pim

interface Ethernet1/27

  ip address 10.12.1.1/24

  ip router ospf 1 area 0.0.0.0

  ip pim sparse-mode

  no shutdown

ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4

ip pim ssm range 232.0.0.0/8

N7K12 (The destination)

feature ospf

feature pim

interface Ethernet1/27

  ip address 10.12.2.1/24

  ip router ospf 1 area 0.0.0.0

  ip pim sparse-mode

  ip igmp join-group 239.1.2.3

  no shutdown

ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4

ip pim ssm range 232.0.0.0/8

It works if the ip igmp join is moved to the loopback interface on the
N7K12.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
  amsoa...@netcabo.pt

  http://www.ccie18473.net

From: Tim Stevenson [mailto:tstev...@cisco.com] 
Sent: sábado, 1 de Outubro de 2011 16:06
To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

Hi Antonio, 

Can you please describe the exact topology here? Which interfaces you're
using, what they're connected to, and where is the RP?

One thing to be aware of with NXOS is that things only show up in sh ip
mroute if the client protocol/process (eg IGMP in this case) has reason to
feed them there. sh ip mroute is basically looking at the MRIB view of the
world and nothing else. 

WRT the ip igmp join-group command, it does two things: one is it causes
that interface to send IGMP joins for that group out that interface as if it
were a host. The other is that, if the router is PIM DR on that interface,
it feeds the *G & the OIF to the MRIB. It's only at that point you'll see
the entry in sh ip mroute. Otherwise, you'll only see it in the IGMP group
membership table, ie, sh ip igmp group.

My guess here is you're not DR on this interface, so I assume there's
another router on the segment that IS the DR. If you check the mrouting
there I suspect you'll see the *G entry joined to the RPT (driven by the
IGMP joins sent on that segment from the router w/the join-group command).

WRT the loopback "working", what you're seeing is that this router is now
the only means by which to reach that 'network segment' (ie, it's obviously
going to be DR on its own loopback) so it will report the *G & OIF to the
MRIB and then you'll see the entry in sh ip mroute.

Hope that helps,
Tim

At 03:24 AM 10/1/2011, Antonio Soares contended:

This is lab environment, I'm just testing basic multicast features with
nexus.

The command reference says the following:

"When you enter this command, the traffic generated is handled by the device
CPU, not the hardware."

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c

ommand/reference/mcr_cmds_i.html#wp1230243

The "ip igmp static-group" was replaced by the command:

ip igmp static-oif

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c

ommand/reference/mcr_cmds_i.html#wp1034808

When I have the igmp joing on the physical interface, the (*,G) entry is
created then it disappears. But I see the (*,G) entry on the RP and I
verified that the traffic is actually sent to the nexus.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoa...@netcabo.pt
http://www.ccie18473.net

-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[ mailto:cisco-nsp-boun...@puck.nether.net
 ] On Behalf Of Phil Mayers
Sent: sábado, 1 de Outubro de 2011 10:49
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

On 10/01/2011 01:31 AM, Antonio Soares wrote:
> Hello group,
>
> Anyone knows why the "ip igmp join-group" does not work on a physical
> interface but it works fine on a loopback interface ?

"ip igmp join-group" is a CPU command; it makes the CPU join the group
and receive the packets. I imagine this might not work on a hardware
platform, with an interface which will be processed in hardware.

Are you sure you don't want "ip igmp static-group"?

What's your use case?
___
cisco-nsp mailing list  cisco-nsp@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Tim S

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Tim Stevenson

Hi Antonio,

Can you please describe the exact topology here? 
Which interfaces you're using, what they're connected to, and where is the RP?

One thing to be aware of with NXOS is that things 
only show up in sh ip mroute if the client 
protocol/process (eg IGMP in this case) has 
reason to feed them there. sh ip mroute is 
basically looking at the MRIB view of the world and nothing else.

WRT the ip igmp join-group command, it does two 
things: one is it causes that interface to send 
IGMP joins for that group out that interface as 
if it were a host. The other is that, if the 
router is PIM DR on that interface, it feeds the 
*G & the OIF to the MRIB. It's only at that point 
you'll see the entry in sh ip mroute. Otherwise, 
you'll only see it in the IGMP group membership table, ie, sh ip igmp group.

My guess here is you're not DR on this interface, 
so I assume there's another router on the segment 
that IS the DR. If you check the mrouting there I 
suspect you'll see the *G entry joined to the RPT 
(driven by the IGMP joins sent on that segment 
from the router w/the join-group command).

WRT the loopback "working", what you're seeing is 
that this router is now the only means by which 
to reach that 'network segment' (ie, it's 
obviously going to be DR on its own loopback) so 
it will report the *G & OIF to the MRIB and then 
you'll see the entry in sh ip mroute.

Hope that helps,
Tim

At 03:24 AM 10/1/2011, Antonio Soares contended:

This is lab environment, I'm just testing basic multicast features with
nexus.

The command reference says the following:

"When you enter this command, the traffic generated is handled by the device
CPU, not the hardware."

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c
ommand/reference/mcr_cmds_i.html#wp1230243

The "ip igmp static-group" was replaced by the command:

ip igmp static-oif

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c
ommand/reference/mcr_cmds_i.html#wp1034808

When I have the igmp joing on the physical interface, the (*,G) entry is
created then it disappears. But I see the (*,G) entry on the RP and I
verified that the traffic is actually sent to the nexus.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoa...@netcabo.pt
http://www.ccie18473.net

-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] 
On Behalf Of Phil Mayers

Sent: sábado, 1 de Outubro de 2011 10:49
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

On 10/01/2011 01:31 AM, Antonio Soares wrote:
> Hello group,
>
> Anyone knows why the "ip igmp join-group" does not work on a physical
> interface but it works fine on a loopback interface ?

"ip igmp join-group" is a CPU command; it makes the CPU join the group
and receive the packets. I imagine this might not work on a hardware
platform, with an interface which will be processed in hardware.

Are you sure you don't want "ip igmp static-group"?

What's your use case?
___
cisco-nsp mailing list  cisco-nsp@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at 
http://puck.nether.net/pipermail/cisco-nsp/

Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759

The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Phil Mayers


On 10/01/2011 11:24 AM, Antonio Soares wrote:

This is lab environment, I'm just testing basic multicast features with
nexus.

The command reference says the following:

"When you enter this command, the traffic generated is handled by the device
CPU, not the hardware."

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c
ommand/reference/mcr_cmds_i.html#wp1230243


Shrug. Then it's a bug and you should ask TAC I guess.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Antonio Soares

This is lab environment, I'm just testing basic multicast features with
nexus.

The command reference says the following:

"When you enter this command, the traffic generated is handled by the device
CPU, not the hardware."

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c
ommand/reference/mcr_cmds_i.html#wp1230243

The "ip igmp static-group" was replaced by the command:

ip igmp static-oif

http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c
ommand/reference/mcr_cmds_i.html#wp1034808

When I have the igmp joing on the physical interface, the (*,G) entry is
created then it disappears. But I see the (*,G) entry on the RP and I
verified that the traffic is actually sent to the nexus.

Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoa...@netcabo.pt
http://www.ccie18473.net

-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Phil Mayers
Sent: sábado, 1 de Outubro de 2011 10:49
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 7K - Multicast Question

On 10/01/2011 01:31 AM, Antonio Soares wrote:
> Hello group,
>
> Anyone knows why the "ip igmp join-group" does not work on a physical
> interface but it works fine on a loopback interface ?

"ip igmp join-group" is a CPU command; it makes the CPU join the group 
and receive the packets. I imagine this might not work on a hardware 
platform, with an interface which will be processed in hardware.

Are you sure you don't want "ip igmp static-group"?

What's your use case?
___
cisco-nsp mailing list  cisco-nsp@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] Nexus 7K - Multicast Question

2011-10-01 Thread Phil Mayers


On 10/01/2011 01:31 AM, Antonio Soares wrote:

Hello group,

Anyone knows why the "ip igmp join-group" does not work on a physical
interface but it works fine on a loopback interface ?


"ip igmp join-group" is a CPU command; it makes the CPU join the group 
and receive the packets. I imagine this might not work on a hardware 
platform, with an interface which will be processed in hardware.


Are you sure you don't want "ip igmp static-group"?

What's your use case?
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] switch with 2x 10GBASE-T interfaces

2011-10-01 Thread Nikolay Shopik


Martin,

C3KX-NM-10GT allow you to install only two 10Gb SFP+ or 4 1Gbit SFP, or 
just ony 10Gbit SFP+ plus 2 1Gbit SFP. You can take look here 
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6406/data_sheet_c78-584733.html 
at table 4.




On 30.09.2011 23:44, Martin T wrote:

Alan, Arne:

WS-C3750X-24S-E + C3KX-NM-10GT seems to be a perfect solution!

WS-C3750X-24S-E has 24 SFP ports so one could use 12 1000BASE-T SFP's
+ 2 1000BASTE-LX10 SFP's and C3KX-NM-10GT module provides two
10GBASE-T ports so all the requirements seems to be fulfilled.


Jim,
I'm afraid WS-C4928-10GE would not suite because two 10GBASE-T ports
are must-have. If there would be 10GBASE-T X2 modules available, this
switch would be a nice option.


Kevin,
if possible, I would prefer Cisco.



What do you think about "WS-C3750X-24S-E + C3KX-NM-10GT" solution? In
addition, are there 10GBASE-T SFP+ modules available on the
market(Cisco or third-party)?


regards,
martin


2011/9/30 Kevin Loch:

Martin T wrote:


Is there a Cisco switch(non-modular preferably) which fulfils those
requirements:

1) 12 or more 1000BASE-T ports
2) 2x SFP port for 1000BASE-LX10 SFP's
3) 2x 10GBASE-T ports(for IBM 10Gb iSCSI Host Interface Card 81Y9613,
which has two 10GBASE-T interfaces)


It's not Cisco but Dell 6248 does have a 2 port 10Gbase-T module
option.  The onboard SFP ports will accept any generic 1G SFP's
(for your LX10 optics).

- Kevin

___
cisco-nsp mailing list  cisco-nsp@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@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] switch with 2x 10GBASE-T interfaces

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] Max IPv6 route entries for Cisco 4948E

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] Nexus 7K - Multicast Question

Re: [c-nsp] switch with 2x 10GBASE-T interfaces

9 matches

Site Navigation

Mail list logo

Footer information